From 885da5b3d3c39a7145130fbd1c882c6eac41ba89 Mon Sep 17 00:00:00 2001
From: "James M. Greene" <JamesMGreene@github.com>
Date: Tue, 18 May 2021 10:07:05 -0500
Subject: [PATCH] Local run of Translations patching process over batch
 (#19360)

* New Crowdin translations by Github Action

* Reset broken translated files to English

* Ran script/i18n/homogenize-frontmatter.js

* Ran script/fix-translation-errors.js

* Reverted translated files with parsing and rendering errors

* fix malformed liquid

* add next directory to exclude list

* currentversion -> currentVersion

* fix liquid errors

* fix liquid errors

* Reset broken translated files to English

* Ran script/i18n/homogenize-frontmatter.js

* Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on

* Reset known broken translation files LAST

* Run script/i18n/homogenize-frontmatter.js

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
Co-authored-by: Rachael Sewell <rachmari@github.com>
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
---
 tests/meta/repository-references.js           |    1 +
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   26 +-
 .../metadata-syntax-for-github-actions.md     |    8 +-
 .../guides/about-continuous-integration.md    |   28 +-
 .../about-packaging-with-github-actions.md    |   33 +-
 .../actions/guides/adding-labels-to-issues.md |    8 +-
 .../guides/building-and-testing-net.md        |  109 +-
 .../guides/building-and-testing-nodejs.md     |   38 +-
 .../guides/building-and-testing-powershell.md |   98 +-
 .../guides/building-and-testing-python.md     |  148 +-
 .../guides/building-and-testing-ruby.md       |  145 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   54 +-
 .../actions/guides/closing-inactive-issues.md |   10 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |   96 +-
 ...ing-to-amazon-elastic-container-service.md |   12 +-
 .../de-DE/content/actions/guides/index.md     |    3 +
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   28 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  131 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 ...us-integration-using-workflow-templates.md |    3 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 .../removing-self-hosted-runners.md           |    2 +-
 translations/de-DE/content/actions/index.md   |   25 -
 ...grating-from-circleci-to-github-actions.md |    4 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   36 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../reference/authentication-in-a-workflow.md |  111 +-
 ...nd-expression-syntax-for-github-actions.md |   20 +-
 .../actions/reference/encrypted-secrets.md    |   25 +-
 .../reference/environment-variables.md        |   13 +-
 .../content/actions/reference/environments.md |   11 +-
 .../events-that-trigger-workflows.md          |   26 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  210 ++-
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   23 +
 .../de-DE/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    6 +-
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    7 +-
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    5 +
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   14 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    4 +-
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    7 +
 .../configuration/site-admin-dashboard.md     |    2 +
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   19 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    3 +
 .../monitoring-cluster-nodes.md               |    6 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |    3 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |   33 +-
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    5 +-
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   21 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   48 +-
 translations/de-DE/content/admin/guides.md    |  105 ++
 translations/de-DE/content/admin/index.md     |   67 +-
 .../de-DE/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    6 +-
 .../overview/about-enterprise-accounts.md     |    3 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    4 +-
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    7 +-
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |    3 +
 ...or-advanced-security-in-your-enterprise.md |    7 +
 ...-management-policies-in-your-enterprise.md |    3 +
 .../de-DE/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../de-DE/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |   15 +-
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    7 +-
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    8 +-
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    3 +
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    3 +
 .../managing-global-webhooks.md               |    2 +
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    4 +-
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    5 +-
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |    6 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 ...g-secret-scanning-for-your-repositories.md |   16 +-
 .../managing-alerts-from-secret-scanning.md   |   10 +-
 .../secure-coding/about-code-scanning.md      |   13 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  152 ++-
 ...iguring-codeql-runner-in-your-ci-system.md |  203 +++
 ...-codeql-workflow-for-compiled-languages.md |    2 +
 .../code-security/secure-coding/index.md      |   10 +-
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   27 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   37 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  308 ++++-
 ...tting-up-code-scanning-for-a-repository.md |    2 +
 ...g-code-scanning-alerts-in-pull-requests.md |   16 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   62 +
 .../troubleshooting-the-codeql-workflow.md    |   45 +-
 .../uploading-a-sarif-file-to-github.md       |   69 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../security-advisories/index.md              |    1 -
 ...bout-alerts-for-vulnerable-dependencies.md |   38 +-
 .../about-dependabot-version-updates.md       |    1 +
 ...guration-options-for-dependency-updates.md |   42 +-
 ...tifications-for-vulnerable-dependencies.md |   25 +-
 .../enabling-and-disabling-version-updates.md |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   19 +-
 .../supply-chain-security/index.md            |    1 +
 ...he-detection-of-vulnerable-dependencies.md |   20 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   30 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../de-DE/content/codespaces/guides.md        |   28 +
 .../de-DE/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../de-DE/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  142 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../blocking-a-user-from-your-organization.md |    4 +-
 .../reporting-abuse-or-spam.md                |    2 +-
 ...nblocking-a-user-from-your-organization.md |    4 +-
 ...-who-are-blocked-from-your-organization.md |    4 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 .../locking-conversations.md                  |    2 +-
 .../tracking-changes-in-a-comment.md          |    2 +-
 ...reating-a-default-community-health-file.md |   10 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../creating-a-github-app-from-a-manifest.md  |    2 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 .../making-a-github-app-public-or-private.md  |    6 +-
 .../developers/apps/scopes-for-oauth-apps.md  |    2 +-
 ...ment-environment-to-create-a-github-app.md |    4 +-
 .../apps/using-content-attachments.md         |   11 +-
 ...sher-verification-for-your-organization.md |    6 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../developers/overview/secret-scanning.md    |   88 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../webhooks-and-events/github-event-types.md |    2 +-
 .../webhook-events-and-payloads.md            |   16 +-
 .../participating-in-a-discussion.md          |    2 +-
 .../de-DE/content/discussions/index.md        |   25 +-
 ...fications-for-pushes-to-your-repository.md |    2 +-
 .../about-protected-branches.md               |   10 +
 .../about-releases.md                         |    2 +-
 .../changing-the-default-branch.md            |    2 +-
 ...classifying-your-repository-with-topics.md |    6 +-
 ...imiting-github-actions-for-a-repository.md |   18 +
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 ...d-analysis-settings-for-your-repository.md |   13 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 ...-the-forking-policy-for-your-repository.md |    4 +-
 .../renaming-a-branch.md                      |    8 +
 .../restoring-a-deleted-repository.md         |    4 +-
 .../transferring-a-repository.md              |    2 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-commit-signature-verification.md    |   34 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |   11 +-
 .../associating-an-email-with-your-gpg-key.md |    2 +-
 .../checking-for-existing-gpg-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../creating-a-personal-access-token.md       |   10 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-permission-denied-publickey.md      |    2 +-
 .../error-unknown-key-type.md                 |   35 +
 .../generating-a-new-gpg-key.md               |    4 +-
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../github/authenticating-to-github/index.md  |    4 +-
 .../managing-commit-signature-verification.md |    2 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    2 +-
 .../reviewing-your-security-log.md            |  101 +-
 ...updating-your-github-access-credentials.md |    2 +-
 .../using-ssh-over-the-https-port.md          |    2 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-forks.md                            |    4 +-
 .../about-pull-request-reviews.md             |    4 +-
 .../about-status-checks.md                    |   12 +-
 .../changing-the-stage-of-a-pull-request.md   |   10 +-
 .../checking-out-pull-requests-locally.md     |   10 +-
 .../commenting-on-a-pull-request.md           |    4 +-
 .../creating-a-pull-request.md                |   16 +-
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 .../index.md                                  |    7 +-
 .../merging-a-pull-request.md                 |    8 +
 .../quickstart-for-communicating-on-github.md |  149 +++
 .../requesting-a-pull-request-review.md       |    2 +-
 .../resolving-a-merge-conflict-on-github.md   |    2 +-
 .../about-code-owners.md                      |    2 +-
 .../about-readmes.md                          |   14 +-
 .../backing-up-a-repository.md                |    4 +-
 .../creating-a-new-repository.md              |    4 +-
 .../creating-a-repository-from-a-template.md  |    2 +-
 .../creating-a-template-repository.md         |    4 +-
 .../licensing-a-repository.md                 |    6 +-
 .../about-code-scanning.md                    |   35 +-
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 ...-codeql-code-scanning-in-your-ci-system.md |    6 +-
 ...-codeql-workflow-for-compiled-languages.md |    8 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   62 +-
 ...ing-codeql-code-scanning-in-a-container.md |   31 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   14 +-
 .../sarif-support-for-code-scanning.md        |    2 +
 ...tting-up-code-scanning-for-a-repository.md |    8 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   24 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    2 +
 .../troubleshooting-the-codeql-workflow.md    |   49 +-
 .../uploading-a-sarif-file-to-github.md       |   57 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../about-git-subtree-merges.md               |    2 +
 .../access-permissions-on-github.md           |    2 +-
 .../getting-started-with-github/be-social.md  |   12 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |    4 +-
 .../following-people.md                       |    4 +-
 .../fork-a-repo.md                            |    7 +-
 ...etting-changes-from-a-remote-repository.md |    2 +
 .../git-workflows.md                          |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../learning-about-github.md                  |    2 +-
 .../getting-started-with-github/set-up-git.md |    2 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 .../types-of-github-accounts.md               |    4 +-
 .../using-git-rebase-on-the-command-line.md   |    2 +
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 translations/de-DE/content/github/index.md    |    2 -
 .../deleting-files-in-a-repository.md         |    2 +-
 .../navigating-code-on-github.md              |    2 +
 ...oving-files-from-git-large-file-storage.md |    4 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   55 +-
 ...tifications-for-vulnerable-dependencies.md |   18 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   10 +-
 .../configuring-notifications.md              |   28 +-
 .../managing-your-subscriptions.md            |   20 +-
 .../viewing-your-subscriptions.md             |   11 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 .../about-automation-for-project-boards.md    |    2 +-
 .../about-issues.md                           |    4 +-
 .../about-project-boards.md                   |    2 +-
 .../creating-a-project-board.md               |    2 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   22 +-
 .../filtering-cards-on-a-project-board.md     |    2 +-
 .../linking-a-pull-request-to-an-issue.md     |    4 +-
 .../managing-labels.md                        |   24 +-
 .../sorting-issues-and-pull-requests.md       |    4 +-
 ...arch-to-filter-issues-and-pull-requests.md |    2 +-
 ...ng-all-of-your-issues-and-pull-requests.md |    2 +-
 .../searching-code.md                         |    5 +-
 .../searching-issues-and-pull-requests.md     |    2 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   26 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 ...unted-subscriptions-for-github-accounts.md |    4 +-
 .../downgrading-git-large-file-storage.md     |    9 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   28 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   14 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    7 +-
 ...ing-your-github-advanced-security-usage.md |   14 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 ...n-azure-subscription-to-your-enterprise.md |    2 +-
 ...ons-policies-in-your-enterprise-account.md |   16 +
 .../index.md                                  |    4 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |    9 +
 .../about-your-organizations-profile.md       |    2 +-
 .../about-your-profile.md                     |    2 +-
 .../personalizing-your-profile.md             |   92 +-
 .../about-your-personal-dashboard.md          |    2 +-
 .../changing-your-github-username.md          |    4 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../converting-a-user-into-an-organization.md |    4 +-
 .../deleting-your-user-account.md             |    6 +-
 ...-collaborators-to-a-personal-repository.md |    4 +-
 .../managing-your-theme-settings.md           |   15 +-
 ...on-levels-for-a-user-account-repository.md |    4 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 .../setting-your-commit-email-address.md      |    4 +-
 .../github-corporate-terms-of-service.md      |    4 +-
 .../site-policy/github-privacy-statement.md   |    2 +-
 .../about-repository-graphs.md                |    2 +-
 .../about-the-dependency-graph.md             |   68 +-
 .../accessing-basic-repository-data.md        |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   68 +-
 ...anding-connections-between-repositories.md |    2 +-
 .../viewing-a-projects-contributors.md        |    4 +-
 ...ium-support-for-github-enterprise-cloud.md |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |    8 +-
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    2 +-
 .../graphql/reference/input-objects.md        |    5 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 ...tting-your-timezone-for-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    1 -
 .../managing-available-metrics-and-reports.md |    1 -
 .../managing-contributors-and-teams.md        |    3 +-
 .../managing-events.md                        |    3 +-
 .../managing-goals.md                         |    1 -
 .../managing-organizations.md                 |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../managing-repositories.md                  |    1 -
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../accessing-your-organizations-settings.md  |    3 +-
 .../about-team-discussions.md                 |    2 +-
 .../keeping-your-organization-secure/index.md |    2 +-
 ...owed-ip-addresses-for-your-organization.md |   12 +-
 ...analysis-settings-for-your-organization.md |   45 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ing-the-audit-log-for-your-organization.md |  100 +-
 ...ur-organizations-installed-integrations.md |    3 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...access-to-an-organization-project-board.md |    2 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...ganizations-ssh-certificate-authorities.md |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    3 +-
 ...-your-organizations-dependency-insights.md |    3 +-
 .../deleting-an-organization-account.md       |    3 +-
 ...ng-github-actions-for-your-organization.md |   31 +-
 .../managing-organization-settings/index.md   |    2 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    3 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...ithub-pages-sites-for-your-organization.md |    3 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    3 +-
 ...epository-creation-in-your-organization.md |    3 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 ...r-deleting-or-transferring-repositories.md |    3 +-
 ...eation-permissions-in-your-organization.md |    3 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...ership-continuity-for-your-organization.md |    6 +
 .../permission-levels-for-an-organization.md  |    6 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...ms-to-improved-organization-permissions.md |    3 +-
 ...-team-discussions-for-your-organization.md |    3 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 translations/de-DE/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   85 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../packages/learn-github-packages/index.md   |   10 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  133 ++
 .../publishing-a-package.md                   |    8 +-
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  455 +++++++
 .../de-DE/content/packages/quickstart.md      |   15 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  124 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  262 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  218 +++
 .../working-with-the-nuget-registry.md        |  237 ++++
 .../working-with-the-rubygems-registry.md     |  151 +++
 ...ustom-domain-for-your-github-pages-site.md |    4 +-
 .../about-github-pages.md                     |    8 -
 ...reating-a-github-pages-site-with-jekyll.md |    7 +-
 .../getting-started-with-the-rest-api.md      |   12 +-
 .../de-DE/content/rest/overview/libraries.md  |    2 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../overview/resources-in-the-rest-api.md     |   30 +-
 .../de-DE/content/rest/reference/activity.md  |   10 +-
 .../rest/reference/enterprise-admin.md        |   13 -
 .../de-DE/content/rest/reference/git.md       |    2 +-
 .../permissions-required-for-github-apps.md   |   29 +-
 .../de-DE/content/rest/reference/repos.md     |    3 +-
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/de-DE/content/sponsors/guides.md |   18 +
 translations/de-DE/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../de-DE/data/glossaries/external.yml        |    8 +-
 .../de-DE/data/glossaries/internal.yml        |    6 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../de-DE/data/learning-tracks/README.md      |   29 +-
 .../de-DE/data/learning-tracks/actions.yml    |    1 +
 .../de-DE/data/learning-tracks/admin.yml      |   72 +
 .../de-DE/data/release-notes/2-21/19.yml      |   18 +
 .../de-DE/data/release-notes/2-21/20.yml      |   19 +
 .../de-DE/data/release-notes/2-21/21.yml      |   15 +
 .../de-DE/data/release-notes/2-22/11.yml      |   19 +
 .../de-DE/data/release-notes/2-22/12.yml      |   22 +
 .../de-DE/data/release-notes/2-22/13.yml      |   20 +
 .../de-DE/data/release-notes/3-0/0.yml        |    1 +
 .../de-DE/data/release-notes/3-0/1.yml        |    1 +
 .../de-DE/data/release-notes/3-0/2.yml        |    1 +
 .../de-DE/data/release-notes/3-0/3.yml        |    1 +
 .../de-DE/data/release-notes/3-0/4.yml        |    1 +
 .../de-DE/data/release-notes/3-0/5.yml        |   27 +
 .../de-DE/data/release-notes/3-0/6.yml        |   30 +
 .../de-DE/data/release-notes/3-0/7.yml        |   23 +
 .../de-DE/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../de-DE/data/reusables/cli/cli-auth.md      |    1 +
 .../de-DE/data/reusables/cli/cli-manual.md    |    1 +
 .../de-DE/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    4 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../gated-features/actions-shared.md          |    2 +-
 .../reusables/gated-features/code-scanning.md |    4 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../de-DE/data/reusables/gpg/x-509-key.md     |    2 +-
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   30 +
 .../authenticate-packages-github-token.md     |    1 +
 .../package_registry/authenticate-packages.md |   17 +-
 ...uthenticate-to-container-registry-steps.md |    2 +-
 ...nticate_with_pat_for_container_registry.md |    4 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 .../data/reusables/secret-scanning/beta.md    |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../link-browsing-advisory-db.md              |    5 +
 .../security/displayed-information.md         |    4 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../keeping_your_email_address_private.md     |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../code_scanning_alert_event_properties.md   |   12 +-
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 translations/de-DE/data/ui.yml                |   46 +-
 .../variables/codespaces_code_examples.yml    |   43 +
 .../de-DE/data/variables/migrations.yml       |    2 +-
 translations/de-DE/data/variables/product.yml |    9 +-
 .../data/variables/release_candidate.yml      |    2 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   16 +-
 .../metadata-syntax-for-github-actions.md     |   18 +-
 .../guides/about-continuous-integration.md    |    3 +
 .../about-packaging-with-github-actions.md    |   34 +-
 .../actions/guides/adding-labels-to-issues.md |   10 +-
 .../building-and-testing-java-with-ant.md     |    2 +-
 .../building-and-testing-java-with-gradle.md  |    2 +-
 .../building-and-testing-java-with-maven.md   |    2 +-
 .../guides/building-and-testing-net.md        |  109 +-
 .../guides/building-and-testing-nodejs.md     |   38 +-
 .../guides/building-and-testing-powershell.md |   98 +-
 .../guides/building-and-testing-python.md     |  146 +-
 .../guides/building-and-testing-ruby.md       |  145 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   50 +-
 .../actions/guides/closing-inactive-issues.md |   12 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |  124 +-
 ...ing-to-amazon-elastic-container-service.md |   12 +-
 .../es-ES/content/actions/guides/index.md     |    3 +
 ...-on-macos-runners-for-xcode-development.md |   52 +-
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   28 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  131 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 .../about-self-hosted-runners.md              |  142 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 ...and-troubleshooting-self-hosted-runners.md |   84 +-
 .../removing-self-hosted-runners.md           |    2 +-
 translations/es-ES/content/actions/index.md   |   25 -
 ...grating-from-circleci-to-github-actions.md |    4 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   62 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../reference/authentication-in-a-workflow.md |  113 +-
 ...nd-expression-syntax-for-github-actions.md |   24 +-
 .../actions/reference/encrypted-secrets.md    |   21 +-
 .../reference/environment-variables.md        |   15 +-
 .../content/actions/reference/environments.md |   13 +-
 .../events-that-trigger-workflows.md          |   24 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  212 ++-
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   23 +
 .../es-ES/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    4 +
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    5 +
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    4 +
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   14 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    2 +
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    7 +
 .../configuration/site-admin-dashboard.md     |  239 ++--
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   19 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    2 +
 .../monitoring-cluster-nodes.md               |    6 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |   23 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |    2 +
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    5 +-
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   27 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   50 +-
 translations/es-ES/content/admin/guides.md    |  105 ++
 translations/es-ES/content/admin/index.md     |   67 +-
 .../es-ES/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    4 +
 .../overview/about-enterprise-accounts.md     |    3 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    2 +
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    5 +
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |    3 +
 ...or-advanced-security-in-your-enterprise.md |    7 +
 ...-management-policies-in-your-enterprise.md |    3 +
 .../es-ES/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../es-ES/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |    3 +
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    5 +
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    4 +
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    5 +-
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    3 +
 .../managing-global-webhooks.md               |    2 +
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    2 +
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    3 +
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |    6 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 .../secret-security/about-secret-scanning.md  |    2 +-
 ...g-secret-scanning-for-your-repositories.md |   16 +-
 .../managing-alerts-from-secret-scanning.md   |   10 +-
 .../secure-coding/about-code-scanning.md      |   46 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  260 ++--
 ...iguring-codeql-runner-in-your-ci-system.md |  203 +++
 ...-codeql-workflow-for-compiled-languages.md |    2 +
 .../code-security/secure-coding/index.md      |   12 +-
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   29 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   37 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  308 ++++-
 ...g-code-scanning-alerts-in-pull-requests.md |   16 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   62 +
 .../troubleshooting-the-codeql-workflow.md    |   45 +-
 .../uploading-a-sarif-file-to-github.md       |   69 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../editing-a-security-advisory.md            |    2 +-
 .../security-advisories/index.md              |    1 -
 .../exploring-security-alerts.md              |  132 +-
 .../code-security/security-overview/index.md  |    6 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   42 +-
 .../about-dependabot-version-updates.md       |    1 +
 .../about-the-dependency-graph.md             |   96 +-
 ...guration-options-for-dependency-updates.md |   58 +-
 ...configuring-dependabot-security-updates.md |    2 +-
 ...tifications-for-vulnerable-dependencies.md |   47 +-
 .../enabling-and-disabling-version-updates.md |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   21 +-
 .../supply-chain-security/index.md            |    1 +
 ...he-detection-of-vulnerable-dependencies.md |   20 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   30 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../es-ES/content/codespaces/guides.md        |   28 +
 .../es-ES/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../es-ES/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  141 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../index.md                                  |    2 +-
 .../es-ES/content/communities/index.md        |    2 +-
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...cking-a-user-from-your-personal-account.md |    2 +-
 .../index.md                                  |    2 +-
 ...nblocking-a-user-from-your-organization.md |    6 +-
 ...cking-a-user-from-your-personal-account.md |    2 +-
 ...-who-are-blocked-from-your-organization.md |    6 +-
 .../index.md                                  |    2 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 ...reating-a-default-community-health-file.md |   10 +-
 .../index.md                                  |    2 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../index.md                                  |    2 +-
 .../cherry-picking-a-commit.md                |   18 +-
 .../creating-a-github-app-from-a-manifest.md  |    8 +-
 ...ating-a-github-app-using-url-parameters.md |    8 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 .../making-a-github-app-public-or-private.md  |    6 +-
 .../developers/apps/scopes-for-oauth-apps.md  |    2 +-
 ...ment-environment-to-create-a-github-app.md |    4 +-
 .../apps/using-content-attachments.md         |   11 +-
 ...sher-verification-for-your-organization.md |    6 +-
 .../github-marketplace-overview.md            |    5 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../overview/managing-deploy-keys.md          |   36 +-
 .../developers/overview/secret-scanning.md    |   95 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../webhooks-and-events/github-event-types.md |   12 +-
 .../securing-your-webhooks.md                 |    2 +-
 .../webhook-events-and-payloads.md            |   40 +-
 .../participating-in-a-discussion.md          |    2 +-
 .../about-github-campus-program.md            |   12 +-
 ...-github-at-your-educational-institution.md |    4 +-
 .../use-github-for-your-schoolwork.md         |    4 +-
 ...n-for-a-student-developer-pack-approved.md |    4 +-
 .../create-a-group-assignment.md              |    2 +-
 .../about-protected-branches.md               |   10 +
 .../changing-the-default-branch.md            |    2 +-
 ...imiting-github-actions-for-a-repository.md |   22 +-
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 ...ge-for-pull-requests-in-your-repository.md |    4 +-
 .../managing-releases-in-a-repository.md      |    2 +-
 ...d-analysis-settings-for-your-repository.md |   13 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 .../renaming-a-branch.md                      |   12 +-
 .../renaming-a-repository.md                  |    2 +-
 .../restoring-a-deleted-repository.md         |    4 +-
 .../setting-repository-visibility.md          |    2 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-authentication-to-github.md         |   18 +-
 ...authentication-with-saml-single-sign-on.md |    2 +-
 .../about-commit-signature-verification.md    |   30 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |    9 +
 .../checking-for-existing-gpg-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../creating-a-personal-access-token.md       |   18 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-unknown-key-type.md                 |   35 +
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../github/authenticating-to-github/index.md  |    4 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    2 +-
 .../telling-git-about-your-signing-key.md     |    6 +-
 .../testing-your-ssh-connection.md            |   38 +-
 .../using-ssh-over-the-https-port.md          |    2 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-status-checks.md                    |   12 +-
 .../automatically-merging-a-pull-request.md   |    4 +-
 .../changing-the-stage-of-a-pull-request.md   |    8 +
 .../checking-out-pull-requests-locally.md     |    8 +
 .../commenting-on-a-pull-request.md           |    2 +-
 .../creating-a-pull-request.md                |   14 +
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 .../index.md                                  |    7 +-
 .../merging-a-pull-request.md                 |    8 +
 .../quickstart-for-communicating-on-github.md |  149 +++
 ...sitory-is-deleted-or-changes-visibility.md |    2 +-
 .../about-readmes.md                          |   14 +-
 .../creating-a-repository-from-a-template.md  |    2 +-
 .../creating-a-template-repository.md         |    2 +-
 .../error-repository-not-found.md             |    2 +-
 .../licensing-a-repository.md                 |    4 +-
 .../about-code-scanning.md                    |   47 +-
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  254 ++--
 ...-codeql-code-scanning-in-your-ci-system.md |    6 +-
 ...-codeql-workflow-for-compiled-languages.md |    8 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   62 +-
 ...ing-codeql-code-scanning-in-a-container.md |   31 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   14 +-
 .../sarif-support-for-code-scanning.md        |  161 ++-
 ...g-code-scanning-alerts-in-pull-requests.md |   24 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    2 +
 .../troubleshooting-the-codeql-workflow.md    |   49 +-
 .../uploading-a-sarif-file-to-github.md       |   57 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../about-git-subtree-merges.md               |    2 +
 .../about-github-advanced-security.md         |    4 +-
 .../getting-started-with-github/be-social.md  |   12 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |    4 +-
 .../fork-a-repo.md                            |    5 +-
 ...etting-changes-from-a-remote-repository.md |    2 +
 .../git-workflows.md                          |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../keyboard-shortcuts.md                     |    8 +-
 .../learning-about-github.md                  |    2 +-
 .../getting-started-with-github/set-up-git.md |    2 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 .../using-git-rebase-on-the-command-line.md   |    2 +
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 translations/es-ES/content/github/index.md    |    2 -
 .../deleting-files-in-a-repository.md         |    2 +-
 .../navigating-code-on-github.md              |    2 +
 ...oving-files-from-git-large-file-storage.md |    2 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   55 +-
 ...tifications-for-vulnerable-dependencies.md |   48 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   10 +-
 .../configuring-notifications.md              |   32 +-
 .../managing-your-subscriptions.md            |   20 +-
 .../viewing-your-subscriptions.md             |   11 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   22 +-
 .../managing-labels.md                        |    2 +
 .../sorting-issues-and-pull-requests.md       |    4 +-
 .../searching-code.md                         |    3 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   26 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 ...unted-subscriptions-for-github-accounts.md |   24 +-
 .../downgrading-git-large-file-storage.md     |   18 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   26 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   12 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    7 +-
 ...ing-your-github-advanced-security-usage.md |   14 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 ...-management-for-your-enterprise-account.md |    4 +-
 ...n-azure-subscription-to-your-enterprise.md |    2 +-
 ...ons-policies-in-your-enterprise-account.md |   16 +
 .../index.md                                  |    4 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |    9 +
 .../about-your-organizations-profile.md       |    2 +-
 .../personalizing-your-profile.md             |   92 +-
 ...tributions-not-showing-up-on-my-profile.md |    4 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../managing-your-theme-settings.md           |   15 +-
 ...on-levels-for-a-user-account-repository.md |    6 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 .../github-corporate-terms-of-service.md      |    6 +-
 ...tion-agreement-non-enterprise-customers.md |   12 +-
 ...d-data-protection-for-your-organization.md |    3 -
 .../site-policy/github-privacy-statement.md   |    2 +-
 .../github-subprocessors-and-cookies.md       |    2 +-
 .../about-the-dependency-graph.md             |   94 +-
 ...loring-the-dependencies-of-a-repository.md |   70 +-
 ...ium-support-for-github-enterprise-cloud.md |    2 +-
 .../submitting-a-ticket.md                    |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |    6 +-
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../writing-on-github/creating-gists.md       |    8 +-
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    2 +-
 .../graphql/reference/input-objects.md        |    5 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 ...tting-your-timezone-for-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    1 -
 .../managing-available-metrics-and-reports.md |    1 -
 .../managing-contributors-and-teams.md        |    3 +-
 .../managing-events.md                        |    3 +-
 .../managing-goals.md                         |    1 -
 .../managing-organizations.md                 |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../managing-repositories.md                  |    1 -
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../accessing-your-organizations-settings.md  |    3 +-
 .../about-team-discussions.md                 |    2 +-
 .../keeping-your-organization-secure/index.md |    2 +-
 ...owed-ip-addresses-for-your-organization.md |   12 +-
 ...analysis-settings-for-your-organization.md |   49 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ing-the-audit-log-for-your-organization.md |  102 +-
 ...ur-organizations-installed-integrations.md |    3 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...access-to-an-organization-project-board.md |    2 +-
 ...-collaborator-to-an-organization-member.md |    2 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...ganizations-ssh-certificate-authorities.md |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    3 +-
 ...-your-organizations-dependency-insights.md |    3 +-
 .../deleting-an-organization-account.md       |    3 +-
 ...ng-github-actions-for-your-organization.md |   31 +-
 .../managing-organization-settings/index.md   |    2 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    3 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...ithub-pages-sites-for-your-organization.md |    7 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    7 +-
 ...epository-creation-in-your-organization.md |    3 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 ...r-deleting-or-transferring-repositories.md |    3 +-
 ...eation-permissions-in-your-organization.md |    3 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...ership-continuity-for-your-organization.md |    6 +
 .../permission-levels-for-an-organization.md  |    6 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...ms-to-improved-organization-permissions.md |    3 +-
 ...-team-discussions-for-your-organization.md |    3 +-
 ...-a-team-with-an-identity-provider-group.md |   10 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 translations/es-ES/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   85 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../packages/learn-github-packages/index.md   |   10 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  133 ++
 .../publishing-a-package.md                   |    8 +-
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  450 +++++++
 .../es-ES/content/packages/quickstart.md      |   13 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  124 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  274 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  218 +++
 .../working-with-the-nuget-registry.md        |  237 ++++
 .../working-with-the-rubygems-registry.md     |  152 +++
 .../about-custom-domains-and-github-pages.md  |    8 +-
 ...ustom-domain-for-your-github-pages-site.md |   26 +-
 ...hooting-custom-domains-and-github-pages.md |    6 +-
 .../about-github-pages.md                     |   10 +-
 ...he-visibility-of-your-github-pages-site.md |    2 +-
 ...shing-source-for-your-github-pages-site.md |    2 +-
 .../unpublishing-a-github-pages-site.md       |    2 +-
 translations/es-ES/content/pages/index.md     |    2 +-
 .../about-github-pages-and-jekyll.md          |    2 +-
 ...reating-a-github-pages-site-with-jekyll.md |    7 +-
 ...r-github-pages-site-locally-with-jekyll.md |    2 +-
 .../getting-started-with-the-rest-api.md      |   12 +-
 .../es-ES/content/rest/overview/libraries.md  |    2 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../overview/resources-in-the-rest-api.md     |   30 +-
 .../es-ES/content/rest/reference/activity.md  |   10 +-
 .../es-ES/content/rest/reference/git.md       |    2 +-
 .../content/rest/reference/migrations.md      |    2 +-
 .../permissions-required-for-github-apps.md   |   13 +
 .../es-ES/content/rest/reference/repos.md     |    3 +-
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/es-ES/content/sponsors/guides.md |   18 +
 translations/es-ES/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../es-ES/data/glossaries/external.yml        |   10 +-
 .../es-ES/data/glossaries/internal.yml        |    6 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../es-ES/data/learning-tracks/README.md      |   29 +-
 .../es-ES/data/learning-tracks/actions.yml    |    1 +
 .../es-ES/data/learning-tracks/admin.yml      |   72 +
 .../es-ES/data/release-notes/2-20/15.yml      |  Bin 5369 -> 4546 bytes
 .../es-ES/data/release-notes/2-21/17.yml      |   10 +-
 .../es-ES/data/release-notes/2-21/18.yml      |    6 +-
 .../es-ES/data/release-notes/2-21/19.yml      |   17 +
 .../es-ES/data/release-notes/2-21/20.yml      |   18 +
 .../es-ES/data/release-notes/2-21/21.yml      |   14 +
 .../es-ES/data/release-notes/2-22/10.yml      |    8 +-
 .../es-ES/data/release-notes/2-22/11.yml      |   18 +
 .../es-ES/data/release-notes/2-22/12.yml      |   21 +
 .../es-ES/data/release-notes/2-22/13.yml      |   19 +
 .../es-ES/data/release-notes/2-22/9.yml       |   10 +-
 .../es-ES/data/release-notes/3-0/0.yml        |    5 +-
 .../es-ES/data/release-notes/3-0/1.yml        |    5 +-
 .../es-ES/data/release-notes/3-0/2.yml        |    5 +-
 .../es-ES/data/release-notes/3-0/3.yml        |   15 +-
 .../es-ES/data/release-notes/3-0/4.yml        |   23 +-
 .../es-ES/data/release-notes/3-0/5.yml        |   26 +
 .../es-ES/data/release-notes/3-0/6.yml        |   29 +
 .../es-ES/data/release-notes/3-0/7.yml        |   22 +
 .../es-ES/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../actions/actions-audit-events-workflow.md  |    4 +-
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../reusables/branches/set-default-branch.md  |    2 +-
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../es-ES/data/reusables/cli/cli-auth.md      |    1 +
 .../es-ES/data/reusables/cli/cli-manual.md    |    1 +
 .../es-ES/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/coupon-expires.md          |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    2 +-
 .../enterprise_installation/replica-limit.md  |    2 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../reusables/gated-features/code-scanning.md |    4 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../gated-features/security-center.md         |    4 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../github-actions/java-jvm-architecture.md   |    2 +-
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../es-ES/data/reusables/gpg/x-509-key.md     |    2 +-
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/filter-security-overview.md |    2 +-
 .../organizations/security-overview.md        |    2 +-
 .../organizations/team-security-overview.md   |    2 +-
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   31 +
 .../authenticate-packages-github-token.md     |    1 +
 ...uthenticate-to-container-registry-steps.md |    4 +-
 ...nticate_with_pat_for_container_registry.md |    6 +-
 .../package_registry/checksum-maven-plugin.md |    2 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../pages/private_pages_are_public_warning.md |    2 +-
 .../data/reusables/pages/sidebar-pages.md     |    2 +-
 .../www-and-apex-domain-recommendation.md     |    2 +-
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    2 +-
 ...forks_from_private_repositories_warning.md |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 .../data/reusables/secret-scanning/beta.md    |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../link-browsing-advisory-db.md              |    5 +
 .../data/reusables/security-center/beta.md    |    2 +-
 .../security/displayed-information.md         |    4 +-
 .../data/reusables/sponsors/choose-updates.md |    2 +-
 .../data/reusables/sponsors/click-add-tier.md |    2 +-
 .../sponsors/enable-custom-amounts.md         |    4 +-
 .../es-ES/data/reusables/sponsors/feedback.md |    2 +-
 .../reusables/sponsors/pay-prorated-amount.md |    2 +-
 .../sponsors/prorated-sponsorship.md          |    2 +-
 .../sponsors/review-and-publish-tier.md       |    2 +-
 .../sponsors/review-tiers-to-select.md        |    2 +-
 .../data/reusables/sponsors/select-a-tier.md  |    2 +-
 .../reusables/sponsors/sponsorship-details.md |    2 +-
 .../data/reusables/sponsors/tier-details.md   |    4 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../reusables/user_settings/billing_plans.md  |    2 +-
 .../keeping_your_email_address_private.md     |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../code_scanning_alert_event_properties.md   |   12 +-
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../reusables/webhooks/discussion_desc.md     |    2 +-
 .../webhooks/discussions-webhooks-beta.md     |    2 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 translations/es-ES/data/ui.yml                |   46 +-
 .../variables/codespaces_code_examples.yml    |   43 +
 .../es-ES/data/variables/migrations.yml       |    2 +-
 translations/es-ES/data/variables/product.yml |    7 +-
 .../data/variables/release_candidate.yml      |    2 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 ...or-users-outside-your-identity-provider.md |    3 +
 .../changing-authentication-methods.md        |    3 +
 .../disabling-unauthenticated-sign-ups.md     |    2 +
 .../using-built-in-authentication.md          |    3 +
 .../content/admin/authentication/using-cas.md |    4 +
 .../admin/authentication/using-ldap.md        |    3 +
 .../admin/authentication/using-saml.md        |    4 +
 .../accessing-the-administrative-shell-ssh.md |    2 +
 .../accessing-the-management-console.md       |    1 +
 .../configuration/command-line-utilities.md   |    1 +
 .../configuration/configuring-a-hostname.md   |    2 +
 ...onfiguring-an-outbound-web-proxy-server.md |    3 +
 .../configuration/configuring-applications.md |    1 +
 .../configuring-backups-on-your-appliance.md  |    3 +
 .../configuring-built-in-firewall-rules.md    |    3 +
 .../configuring-dns-nameservers.md            |    3 +
 .../configuration/configuring-rate-limits.md  |    2 +
 ...dress-using-the-virtual-machine-console.md |    3 +
 .../configuring-time-synchronization.md       |    3 +
 .../admin/configuration/configuring-tls.md    |    4 +
 ...prise-server-to-github-enterprise-cloud.md |    3 +
 ...ependencies-on-github-enterprise-server.md |    1 +
 ...nabling-and-scheduling-maintenance-mode.md |    3 +
 ...rise-server-and-github-enterprise-cloud.md |    2 +
 .../configuration/enabling-private-mode.md    |    7 +
 .../enabling-subdomain-isolation.md           |    4 +
 ...-github-enterprise-server-and-githubcom.md |    1 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../admin/configuration/network-ports.md      |    3 +
 .../configuration/site-admin-dashboard.md     |    1 +
 .../troubleshooting-ssl-errors.md             |    5 +
 ...-enterprise-server-with-a-load-balancer.md |    3 +
 .../validating-your-domain-settings.md        |    3 +
 .../about-cluster-nodes.md                    |    1 +
 .../enterprise-management/about-clustering.md |    1 +
 .../about-geo-replication.md                  |    1 +
 .../about-high-availability-configuration.md  |    2 +
 .../accessing-the-monitor-dashboard.md        |    4 +
 .../cluster-network-configuration.md          |    3 +
 .../configuring-collectd.md                   |    4 +
 ...-availability-replication-for-a-cluster.md |    3 +
 .../creating-a-high-availability-replica.md   |    2 +
 ...een-clustering-and-high-availability-ha.md |    3 +
 .../enabling-automatic-update-checks.md       |    1 +
 .../evacuating-a-cluster-node.md              |    1 +
 .../increasing-cpu-or-memory-resources.md     |    2 +
 .../increasing-storage-capacity.md            |    3 +
 .../initializing-the-cluster.md               |    1 +
 ...ng-a-failover-to-your-replica-appliance.md |    2 +
 ...ting-a-failover-to-your-replica-cluster.md |    3 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    2 +
 .../monitoring-cluster-nodes.md               |    5 +
 .../monitoring-using-snmp.md                  |    3 +
 .../recommended-alert-thresholds.md           |    4 +
 ...ering-a-high-availability-configuration.md |    2 +
 .../removing-a-high-availability-replica.md   |    3 +
 .../replacing-a-cluster-node.md               |    2 +
 .../setting-up-external-monitoring.md         |    3 +
 .../upgrade-requirements.md                   |    1 +
 .../upgrading-a-cluster.md                    |    2 +
 .../upgrading-github-enterprise-server.md     |    1 +
 .../about-github-enterprise-support.md        |    1 +
 ...um-support-for-github-enterprise-server.md |    1 +
 ...b-premium-support-for-github-enterprise.md |    1 +
 .../about-support-for-advanced-security.md    |    1 +
 .../preparing-to-submit-a-ticket.md           |    1 +
 .../providing-data-to-github-support.md       |    1 +
 .../reaching-github-support.md                |    1 +
 .../enterprise-support/submitting-a-ticket.md |    1 +
 ...-githubcom-actions-using-github-connect.md |    2 +
 ...ub-actions-policies-for-your-enterprise.md |    2 +
 .../es-XL/content/admin/installation/index.md |    2 +
 .../setting-up-a-staging-instance.md          |    2 +
 .../overview/about-enterprise-accounts.md     |    2 +
 .../content/admin/overview/system-overview.md |    4 +
 .../admin/policies/about-pre-receive-hooks.md |    2 +
 ...creating-a-pre-receive-hook-environment.md |    2 +
 .../creating-a-pre-receive-hook-script.md     |    2 +
 ...-management-policies-in-your-enterprise.md |    2 +
 ...-the-github-enterprise-server-appliance.md |    2 +
 .../admin/user-management/about-migrations.md |    1 +
 .../user-management/adding-people-to-teams.md |    3 +
 .../admin/user-management/audit-logging.md    |    3 +
 .../admin/user-management/audited-actions.md  |    2 +
 .../user-management/auditing-ssh-keys.md      |    3 +
 .../best-practices-for-user-security.md       |    2 +
 ...-large-file-storage-for-your-enterprise.md |    3 +
 ...-visibility-for-organization-membership.md |    2 +
 .../continuous-integration-using-jenkins.md   |    1 +
 .../admin/user-management/creating-teams.md   |    3 +
 ...exporting-migration-data-from-githubcom.md |    2 +
 ...ing-migration-data-from-your-enterprise.md |    2 +
 ...rom-third-party-version-control-systems.md |    1 +
 .../user-management/managing-dormant-users.md |    2 +
 .../managing-global-webhooks.md               |    1 +
 .../managing-projects-using-jira.md           |    1 +
 .../migrating-data-to-your-enterprise.md      |    1 +
 .../migrating-to-internal-repositories.md     |    3 +
 ...-a-legal-hold-on-a-user-or-organization.md |    4 +
 ...ring-to-migrate-data-to-your-enterprise.md |    1 +
 ...nting-users-from-creating-organizations.md |    2 +
 ...moting-or-demoting-a-site-administrator.md |    3 +
 .../rebuilding-contributions-data.md          |    2 +
 ...ving-users-from-teams-and-organizations.md |    3 +
 ...ctor-authentication-for-an-organization.md |    4 +
 .../searching-the-audit-log.md                |    2 +
 .../suspending-and-unsuspending-users.md      |    3 +
 .../user-management/viewing-push-logs.md      |    3 +
 .../pushing-changes-to-github.md              |    2 +-
 ...tting-your-timezone-for-github-insights.md |    2 +-
 .../viewing-key-metrics-and-reports.md        |    4 +-
 .../managing-available-metrics-and-reports.md |    2 +-
 .../managing-organizations.md                 |    2 +-
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   36 +-
 .../metadata-syntax-for-github-actions.md     |   14 +-
 .../setting-exit-codes-for-actions.md         |    8 +-
 .../guides/about-continuous-integration.md    |    3 +
 .../about-packaging-with-github-actions.md    |   34 +-
 .../actions/guides/adding-labels-to-issues.md |    8 +-
 .../guides/building-and-testing-net.md        |  111 +-
 .../guides/building-and-testing-nodejs.md     |   38 +-
 .../guides/building-and-testing-powershell.md |   98 +-
 .../guides/building-and-testing-python.md     |  146 +-
 .../guides/building-and-testing-ruby.md       |  147 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   50 +-
 .../actions/guides/closing-inactive-issues.md |   10 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |   98 +-
 ...ing-to-amazon-elastic-container-service.md |   34 +-
 .../ja-JP/content/actions/guides/index.md     |    3 +
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   28 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  131 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 ...and-troubleshooting-self-hosted-runners.md |    2 +
 .../removing-self-hosted-runners.md           |    2 +-
 translations/ja-JP/content/actions/index.md   |   25 -
 ...grating-from-circleci-to-github-actions.md |    6 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   36 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../ja-JP/content/actions/quickstart.md       |    2 +-
 .../reference/authentication-in-a-workflow.md |  115 +-
 ...nd-expression-syntax-for-github-actions.md |   20 +-
 .../reference/environment-variables.md        |   13 +-
 .../content/actions/reference/environments.md |   11 +-
 .../events-that-trigger-workflows.md          |   24 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  188 ++-
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   27 +
 .../ja-JP/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    4 +
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    5 +
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    9 +-
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   16 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    2 +
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    7 +
 .../configuration/site-admin-dashboard.md     |    2 +
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   19 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    3 +
 .../monitoring-cluster-nodes.md               |    5 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |    3 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |    2 +
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    5 +-
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   21 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   48 +-
 translations/ja-JP/content/admin/guides.md    |  105 ++
 translations/ja-JP/content/admin/index.md     |   67 +-
 .../ja-JP/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    4 +
 .../overview/about-enterprise-accounts.md     |    3 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    2 +
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    5 +
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |    3 +
 ...or-advanced-security-in-your-enterprise.md |    9 +-
 ...-management-policies-in-your-enterprise.md |    3 +
 .../ja-JP/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../ja-JP/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |    3 +
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    5 +
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    4 +
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    3 +
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    3 +
 .../managing-global-webhooks.md               |    2 +
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    2 +
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    3 +
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |   24 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 .../secret-security/about-secret-scanning.md  |   10 +-
 ...g-secret-scanning-for-your-repositories.md |   34 +-
 .../managing-alerts-from-secret-scanning.md   |   18 +-
 .../secure-coding/about-code-scanning.md      |   19 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |   18 +-
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  222 +--
 ...iguring-codeql-runner-in-your-ci-system.md |  204 +++
 ...-codeql-workflow-for-compiled-languages.md |   38 +-
 .../code-security/secure-coding/index.md      |   10 +-
 .../integrating-with-code-scanning.md         |    7 +-
 ...ode-scanning-alerts-for-your-repository.md |   71 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   51 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  358 ++++-
 ...tting-up-code-scanning-for-a-repository.md |   99 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   50 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   63 +
 .../troubleshooting-the-codeql-workflow.md    |   97 +-
 .../uploading-a-sarif-file-to-github.md       |   83 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../security-advisories/index.md              |    1 -
 .../about-dependabot-version-updates.md       |    1 +
 .../about-managing-vulnerable-dependencies.md |    2 +-
 .../about-the-dependency-graph.md             |    4 +-
 ...ilities-in-the-github-advisory-database.md |    2 +-
 ...guration-options-for-dependency-updates.md |  172 ++-
 ...configuring-dependabot-security-updates.md |    2 +-
 ...tifications-for-vulnerable-dependencies.md |   25 +-
 .../enabling-and-disabling-version-updates.md |   20 +-
 ...loring-the-dependencies-of-a-repository.md |   25 +-
 .../supply-chain-security/index.md            |    1 +
 ...your-actions-up-to-date-with-dependabot.md |    2 +-
 ...naging-encrypted-secrets-for-dependabot.md |   38 +-
 ...ng-pull-requests-for-dependency-updates.md |    2 +-
 .../troubleshooting-dependabot-errors.md      |   80 +-
 ...he-detection-of-vulnerable-dependencies.md |  104 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   32 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../ja-JP/content/codespaces/guides.md        |   28 +
 .../ja-JP/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../ja-JP/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  142 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...nblocking-a-user-from-your-organization.md |    4 +-
 ...-who-are-blocked-from-your-organization.md |    4 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../creating-a-github-app-from-a-manifest.md  |    2 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 .../making-a-github-app-public-or-private.md  |    6 +-
 .../developers/apps/scopes-for-oauth-apps.md  |    2 +-
 ...ment-environment-to-create-a-github-app.md |    6 +-
 .../apps/using-content-attachments.md         |   15 +-
 ...sher-verification-for-your-organization.md |    6 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../developers/overview/secret-scanning.md    |   61 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../webhooks-and-events/github-event-types.md |    4 +-
 .../webhook-events-and-payloads.md            |   36 +-
 .../participating-in-a-discussion.md          |    2 +-
 ...iscussions-across-multiple-repositories.md |    4 +-
 .../ja-JP/content/discussions/index.md        |   21 -
 .../about-protected-branches.md               |   12 +-
 .../changing-the-default-branch.md            |   28 +-
 ...classifying-your-repository-with-topics.md |    8 +-
 ...imiting-github-actions-for-a-repository.md |   30 +-
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 ...nymous-git-read-access-for-a-repository.md |    2 +-
 ...ing-github-discussions-for-a-repository.md |   12 +-
 .../managing-a-branch-protection-rule.md      |   52 +-
 ...ge-for-pull-requests-in-your-repository.md |   10 +-
 ...-objects-in-archives-of-your-repository.md |    4 +-
 .../managing-releases-in-a-repository.md      |    6 +-
 .../managing-repository-settings.md           |    2 +-
 ...d-analysis-settings-for-your-repository.md |   39 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 ...-the-forking-policy-for-your-repository.md |    4 +-
 .../renaming-a-branch.md                      |   34 +-
 .../restoring-a-deleted-repository.md         |    6 +-
 .../transferring-a-repository.md              |    8 +-
 .../troubleshooting-required-status-checks.md |   10 +-
 .../viewing-branches-in-your-repository.md    |    2 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 ...wing-your-repositorys-releases-and-tags.md |    2 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-authentication-to-github.md         |   20 +-
 .../about-commit-signature-verification.md    |   30 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |   11 +-
 .../checking-for-existing-gpg-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../creating-a-personal-access-token.md       |   18 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-unknown-key-type.md                 |   35 +
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../github/authenticating-to-github/index.md  |    4 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    2 +-
 .../reviewing-your-security-log.md            |   63 +-
 .../reviewing-your-ssh-keys.md                |   55 +-
 .../telling-git-about-your-signing-key.md     |    6 +-
 .../using-ssh-over-the-https-port.md          |    4 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 .../about-branches.md                         |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-status-checks.md                    |   12 +-
 .../automatically-merging-a-pull-request.md   |    4 +-
 .../changing-the-stage-of-a-pull-request.md   |    8 +
 .../checking-out-pull-requests-locally.md     |    8 +
 .../commenting-on-a-pull-request.md           |    2 +-
 .../creating-a-pull-request.md                |    8 +
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 .../index.md                                  |    7 +-
 .../merging-a-pull-request.md                 |    8 +
 .../quickstart-for-communicating-on-github.md |  149 +++
 ...ng-dependency-changes-in-a-pull-request.md |    2 +-
 .../syncing-a-fork.md                         |    2 +-
 ...sitory-is-deleted-or-changes-visibility.md |    2 +-
 .../about-readmes.md                          |   14 +-
 .../creating-a-repository-from-a-template.md  |    2 +-
 .../creating-a-template-repository.md         |    2 +-
 .../about-code-scanning.md                    |   47 +-
 .../about-integration-with-code-scanning.md   |   18 +-
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  233 ++--
 ...-codeql-code-scanning-in-your-ci-system.md |  167 +--
 ...-codeql-workflow-for-compiled-languages.md |   47 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    7 +-
 ...ode-scanning-alerts-for-your-repository.md |  108 +-
 ...ing-codeql-code-scanning-in-a-container.md |   47 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   86 +-
 .../sarif-support-for-code-scanning.md        |   54 +-
 ...tting-up-code-scanning-for-a-repository.md |   95 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   60 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   37 +-
 .../troubleshooting-the-codeql-workflow.md    |  101 +-
 .../uploading-a-sarif-file-to-github.md       |   83 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../about-git-subtree-merges.md               |    4 +-
 .../about-remote-repositories.md              |   12 +-
 .../getting-started-with-github/be-social.md  |   10 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |    4 +-
 .../fork-a-repo.md                            |    5 +-
 ...etting-changes-from-a-remote-repository.md |    4 +-
 .../git-workflows.md                          |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../keyboard-shortcuts.md                     |    6 +-
 .../learning-about-github.md                  |    2 +-
 .../managing-remote-repositories.md           |    2 +-
 .../pushing-commits-to-a-remote-repository.md |    2 +-
 .../getting-started-with-github/set-up-git.md |    2 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 ...g-a-subfolder-out-into-a-new-repository.md |    2 +-
 ...ing-credentials-from-the-macos-keychain.md |   10 +-
 .../using-git-rebase-on-the-command-line.md   |    6 +-
 ...hy-is-git-always-asking-for-my-password.md |    4 +-
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 translations/ja-JP/content/github/index.md    |    2 -
 .../navigating-code-on-github.md              |    2 +
 ...oving-files-from-git-large-file-storage.md |    2 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   79 +-
 ...tifications-for-vulnerable-dependencies.md |   18 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   10 +-
 .../managing-your-subscriptions.md            |   16 +-
 .../viewing-your-subscriptions.md             |   81 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   22 +-
 .../managing-labels.md                        |    2 +
 .../sorting-issues-and-pull-requests.md       |    4 +-
 .../searching-code.md                         |    3 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   26 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 .../downgrading-git-large-file-storage.md     |    9 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   26 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   12 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    7 +-
 ...ing-your-github-advanced-security-usage.md |    2 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 .../about-enterprise-accounts.md              |    6 +-
 ...-management-for-your-enterprise-account.md |   34 +-
 ...rganizations-in-your-enterprise-account.md |    6 +-
 ...rganizations-to-your-enterprise-account.md |    2 +-
 ...-management-for-your-enterprise-account.md |    4 +-
 ...n-azure-subscription-to-your-enterprise.md |   32 +-
 ...rganizations-in-your-enterprise-account.md |   14 +-
 ...ons-policies-in-your-enterprise-account.md |   20 +-
 ...ced-security-in-your-enterprise-account.md |    6 +-
 ...ent-policies-in-your-enterprise-account.md |    2 +-
 ...ity-settings-in-your-enterprise-account.md |    2 +-
 .../index.md                                  |    8 +-
 ...viting-people-to-manage-your-enterprise.md |    4 +-
 ...dio-subscription-with-github-enterprise.md |   14 +-
 ...rganizations-in-your-enterprise-account.md |    8 +-
 ...rganizations-in-your-enterprise-account.md |    2 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 .../roles-in-an-enterprise.md                 |   30 +-
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |   11 +-
 ...n-and-usage-for-your-enterprise-account.md |   20 +-
 .../about-your-organizations-profile.md       |    2 +-
 .../personalizing-your-profile.md             |   92 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../managing-your-theme-settings.md           |   15 +-
 ...on-levels-for-a-user-account-repository.md |    4 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 .../site-policy/github-and-trade-controls.md  |   38 +-
 .../github-community-guidelines.md            |    6 +-
 .../github-corporate-terms-of-service.md      |    8 +-
 ...tion-agreement-non-enterprise-customers.md |  190 +--
 ...d-data-protection-for-your-organization.md |    3 -
 .../site-policy/github-pre-release-program.md |    4 +-
 .../site-policy/github-privacy-statement.md   |    4 +-
 .../github-registered-developer-agreement.md  |    8 +-
 ...se-settings-for-your-private-repository.md |    4 +-
 .../about-repository-graphs.md                |    2 +-
 .../about-the-dependency-graph.md             |   97 +-
 .../accessing-basic-repository-data.md        |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   76 +-
 ...anding-connections-between-repositories.md |    2 +-
 .../viewing-a-projects-contributors.md        |   10 +-
 ...iewing-the-dependencies-of-a-repository.md |   10 +-
 .../viewing-traffic-to-a-repository.md        |    2 +-
 ...ium-support-for-github-enterprise-cloud.md |    4 +-
 .../about-github-support.md                   |    4 +-
 .../submitting-a-ticket.md                    |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |   12 +-
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../writing-on-github/creating-gists.md       |   26 +-
 .../forking-and-cloning-gists.md              |    2 +-
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    2 +-
 .../content/graphql/overview/explorer.md      |    2 +-
 .../graphql/reference/input-objects.md        |    5 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    3 +-
 .../managing-goals.md                         |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../accessing-your-organizations-settings.md  |    3 +-
 .../keeping-your-organization-secure/index.md |    2 +-
 ...owed-ip-addresses-for-your-organization.md |   12 +-
 ...analysis-settings-for-your-organization.md |   45 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ing-the-audit-log-for-your-organization.md |  366 ++---
 ...ur-organizations-installed-integrations.md |    3 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...access-to-an-organization-project-board.md |    2 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...ganizations-ssh-certificate-authorities.md |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    3 +-
 ...-your-organizations-dependency-insights.md |    3 +-
 .../deleting-an-organization-account.md       |    3 +-
 ...ng-github-actions-for-your-organization.md |   37 +-
 .../managing-organization-settings/index.md   |    2 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    7 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    3 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...ithub-pages-sites-for-your-organization.md |    3 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    3 +-
 ...epository-creation-in-your-organization.md |    3 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 ...r-deleting-or-transferring-repositories.md |    3 +-
 ...eation-permissions-in-your-organization.md |    3 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...ership-continuity-for-your-organization.md |    6 +
 .../permission-levels-for-an-organization.md  |    6 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...ms-to-improved-organization-permissions.md |    3 +-
 ...-team-discussions-for-your-organization.md |    3 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 translations/ja-JP/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   83 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../packages/learn-github-packages/index.md   |   10 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  131 ++
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  455 +++++++
 .../ja-JP/content/packages/quickstart.md      |   13 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  126 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  272 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  218 +++
 .../working-with-the-nuget-registry.md        |  238 ++++
 .../working-with-the-rubygems-registry.md     |  151 +++
 .../about-custom-domains-and-github-pages.md  |    2 +-
 ...ustom-domain-for-your-github-pages-site.md |   14 +-
 ...hooting-custom-domains-and-github-pages.md |    4 +-
 .../about-github-pages.md                     |   38 +-
 ...ithub-pages-site-with-the-theme-chooser.md |    2 +-
 ...he-visibility-of-your-github-pages-site.md |   24 +-
 ...shing-source-for-your-github-pages-site.md |    6 +-
 .../creating-a-github-pages-site.md           |    4 +-
 .../unpublishing-a-github-pages-site.md       |    4 +-
 .../about-github-pages-and-jekyll.md          |    4 +-
 ...yll-build-errors-for-github-pages-sites.md |    4 +-
 ...-to-your-github-pages-site-using-jekyll.md |    4 +-
 ...-to-your-github-pages-site-using-jekyll.md |    2 +-
 ...reating-a-github-pages-site-with-jekyll.md |   23 +-
 ...for-your-github-pages-site-using-jekyll.md |    2 +-
 ...r-github-pages-site-locally-with-jekyll.md |    2 +-
 ...yll-build-errors-for-github-pages-sites.md |   12 +-
 .../rest/guides/basics-of-authentication.md   |    2 +-
 .../discovering-resources-for-a-user.md       |    6 +-
 .../getting-started-with-the-rest-api.md      |   22 +-
 .../ja-JP/content/rest/overview/libraries.md  |   12 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../overview/other-authentication-methods.md  |    2 +-
 .../overview/resources-in-the-rest-api.md     |   62 +-
 .../ja-JP/content/rest/reference/activity.md  |   14 +-
 .../content/rest/reference/code-scanning.md   |   10 +-
 .../rest/reference/enterprise-admin.md        |   25 +-
 .../ja-JP/content/rest/reference/git.md       |    2 +-
 .../ja-JP/content/rest/reference/markdown.md  |    2 +-
 .../content/rest/reference/migrations.md      |    2 +-
 .../ja-JP/content/rest/reference/packages.md  |   22 +-
 .../permissions-required-for-github-apps.md   |   15 +-
 .../ja-JP/content/rest/reference/repos.md     |    9 +-
 .../ja-JP/content/rest/reference/teams.md     |    4 +-
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/ja-JP/content/sponsors/guides.md |   18 +
 translations/ja-JP/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../ja-JP/data/glossaries/external.yml        |    8 +-
 .../ja-JP/data/glossaries/internal.yml        |    6 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../ja-JP/data/learning-tracks/README.md      |   29 +-
 .../ja-JP/data/learning-tracks/actions.yml    |    1 +
 .../ja-JP/data/learning-tracks/admin.yml      |   72 +
 .../ja-JP/data/release-notes/2-21/19.yml      |   18 +
 .../ja-JP/data/release-notes/2-21/20.yml      |   19 +
 .../ja-JP/data/release-notes/2-21/21.yml      |   15 +
 .../ja-JP/data/release-notes/2-22/11.yml      |   19 +
 .../ja-JP/data/release-notes/2-22/12.yml      |   22 +
 .../ja-JP/data/release-notes/2-22/13.yml      |   20 +
 .../ja-JP/data/release-notes/3-0/0.yml        |    1 +
 .../ja-JP/data/release-notes/3-0/1.yml        |    1 +
 .../ja-JP/data/release-notes/3-0/2.yml        |    1 +
 .../ja-JP/data/release-notes/3-0/3.yml        |    1 +
 .../ja-JP/data/release-notes/3-0/4.yml        |    1 +
 .../ja-JP/data/release-notes/3-0/5.yml        |   27 +
 .../ja-JP/data/release-notes/3-0/6.yml        |   30 +
 .../ja-JP/data/release-notes/3-0/7.yml        |   23 +
 .../ja-JP/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../actions/actions-audit-events-workflow.md  |    4 +-
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../reusables/branches/set-default-branch.md  |    2 +-
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../ja-JP/data/reusables/cli/cli-auth.md      |    1 +
 .../ja-JP/data/reusables/cli/cli-manual.md    |    1 +
 .../ja-JP/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    2 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../gated-features/actions-shared.md          |    2 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   30 +
 .../authenticate-packages-github-token.md     |    1 +
 .../package_registry/authenticate-packages.md |   17 +-
 ...uthenticate-to-container-registry-steps.md |    2 +-
 ...nticate_with_pat_for_container_registry.md |    4 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../data/reusables/pages/sidebar-pages.md     |    2 +-
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    4 +-
 ...forks_from_private_repositories_warning.md |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../request-security-advisory-cve-id.md       |    6 +-
 .../repositories/return-to-source-diff.md     |    4 +-
 .../review-policy-overlapping-commits.md      |    2 +-
 .../security-advisory-edit-cwe-cve.md         |    4 +-
 .../security-advisory-edit-details.md         |    2 +-
 .../security-advisory-edit-severity.md        |    2 +-
 .../security-alert-delivery-options.md        |    4 +-
 .../security-alerts-x-github-severity.md      |    2 +-
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/select-marketplace-apps.md   |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 ...quash-and-rebase-linear-commit-hisitory.md |    2 +-
 .../repositories/start-line-comment.md        |    2 +-
 .../reusables/repositories/suggest-changes.md |    2 +-
 .../repositories/tracks-vulnerabilities.md    |    6 +-
 .../repositories/transfer-repository-steps.md |    2 +-
 .../two-dot-diff-comparison-example-urls.md   |    2 +-
 .../view-failed-job-results-superlinter.md    |    6 +-
 .../repositories/view-run-superlinter.md      |    2 +-
 .../data/reusables/repositories/view-run.md   |    2 +-
 .../view-specific-line-superlinter.md         |    4 +-
 .../repositories/workflow-notifications.md    |    6 +-
 .../reusables/repositories/you-can-fork.md    |    4 +-
 ...ut-user-provisioning-enterprise-account.md |    2 +-
 ...ae-enable-saml-sso-during-bootstrapping.md |    2 +-
 .../data/reusables/saml/ae-uses-saml-sso.md   |    2 +-
 .../assert-the-administrator-attribute.md     |    2 +-
 .../reusables/saml/assign-yourself-to-okta.md |    2 +-
 .../click-enterprise-account-application.md   |    2 +-
 ...tact-support-if-your-idp-is-unavailable.md |    2 +-
 .../reusables/saml/create-a-machine-user.md   |    2 +-
 .../reusables/saml/dotcom-saml-explanation.md |    2 +-
 .../data/reusables/saml/okta-admin-button.md  |    2 +-
 .../reusables/saml/okta-provisioning-tab.md   |    2 +-
 .../data/reusables/saml/okta-sign-on-tab.md   |    2 +-
 .../data/reusables/saml/use-classic-ui.md     |    2 +-
 .../you-must-periodically-authenticate.md     |    2 +-
 .../scim/after-you-configure-saml.md          |    2 +-
 .../reusables/scim/enterprise-account-scim.md |    2 +-
 .../data/reusables/scim/supported-idps.md     |    2 +-
 .../ja-JP/data/reusables/search/date_gt_lt.md |    2 +-
 .../data/reusables/search/required_login.md   |    2 +-
 .../data/reusables/search/syntax_tips.md      |    2 +-
 .../secret-scanning/about-secret-scanning.md  |    2 +-
 .../reusables/secret-scanning/api-beta.md     |    2 +-
 .../data/reusables/secret-scanning/beta.md    |    4 +-
 .../enterprise-enable-secret-scanning.md      |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../disclosing-vulnerabilities.md             |    2 +-
 .../link-browsing-advisory-db.md              |    3 +
 .../security-advisory-overview.md             |    2 +-
 ...urity-researcher-cannot-create-advisory.md |    2 +-
 .../data/reusables/security-center/beta.md    |    2 +-
 .../security/displayed-information.md         |   12 +-
 ...-and-analysis-features-enable-read-only.md |    4 +-
 .../shortdesc/authenticating_github_app.md    |    2 +-
 .../authenticating_with_github_apps.md        |    2 +-
 .../shortdesc/authorizing_oauth_apps.md       |    2 +-
 .../creating_custom_badges_github_apps.md     |    2 +-
 .../creating_custom_badges_oauth_apps.md      |    2 +-
 .../shortdesc/creating_github_apps.md         |    2 +-
 .../shortdesc/creating_oauth_apps.md          |    2 +-
 .../shortdesc/deleting_github_apps.md         |    2 +-
 .../shortdesc/deleting_oauth_apps.md          |    2 +-
 .../editing_permissions_for_github_apps.md    |    2 +-
 ...identifying_and_authorizing_github_apps.md |    2 +-
 .../making-a-github-app-public-or-private.md  |    2 +-
 .../shortdesc/modifying_github_apps.md        |    2 +-
 .../shortdesc/modifying_oauth_apps.md         |    2 +-
 .../shortdesc/permissions_github_apps.md      |    2 +-
 .../shortdesc/rate_limits_github_apps.md      |    2 +-
 .../shortdesc/suspending_a_github_app.md      |    2 +-
 .../transferring_ownership_of_github_apps.md  |    2 +-
 .../transferring_ownership_of_oauth_apps.md   |    2 +-
 ...g_access_token_reques_errors_oauth_apps.md |    2 +-
 ...authorization_request_errors_oauth_apps.md |    2 +-
 .../understanding_scopes_for_oauth_apps.md    |    2 +-
 .../reusables/sponsors/billing-switcher.md    |    2 +-
 .../data/reusables/sponsors/change-tier.md    |    2 +-
 .../data/reusables/sponsors/choose-updates.md |    2 +-
 .../data/reusables/sponsors/click-add-tier.md |    2 +-
 .../sponsors/enable-custom-amounts.md         |    4 +-
 .../ja-JP/data/reusables/sponsors/feedback.md |    2 +-
 .../reusables/sponsors/manage-sponsorship.md  |    2 +-
 .../sponsors/manage-updates-for-orgs.md       |    2 +-
 .../sponsors/matching-fund-eligible.md        |    2 +-
 .../sponsors/navigate-to-sponsored-account.md |    2 +-
 .../navigate-to-sponsors-dashboard.md         |    2 +-
 .../ja-JP/data/reusables/sponsors/no-fees.md  |    2 +-
 .../sponsors/org-sponsors-release-phase.md    |    2 +-
 .../reusables/sponsors/pay-prorated-amount.md |    2 +-
 .../sponsors/prorated-sponsorship.md          |    2 +-
 .../sponsors/review-and-publish-tier.md       |    2 +-
 .../sponsors/review-tiers-to-select.md        |    2 +-
 .../data/reusables/sponsors/select-a-tier.md  |    2 +-
 .../reusables/sponsors/sponsor-account.md     |    2 +-
 .../sponsors/sponsorship-dashboard.md         |    6 +-
 .../reusables/sponsors/sponsorship-details.md |    2 +-
 .../data/reusables/sponsors/tier-details.md   |    4 +-
 .../you-can-be-a-sponsored-developer.md       |    2 +-
 .../you-can-be-a-sponsored-organization.md    |    2 +-
 .../reusables/ssh/add-ssh-key-to-ssh-agent.md |    2 +-
 .../ja-JP/data/reusables/ssh/dsa-support.md   |    2 +-
 ...nterprise-resolving-and-closing-tickets.md |    4 +-
 .../data/reusables/support/ghae-priorities.md |   12 +-
 .../premium-resolving-and-closing-tickets.md  |    2 +-
 .../reusables/support/receiving-credits.md    |    2 +-
 .../reusables/support/scope-of-support.md     |    2 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../ja-JP/data/reusables/two_fa/about-2fa.md  |    2 +-
 .../two_fa/after-2fa-add-security-key.md      |    2 +-
 .../user-settings/edit_marketplace_listing.md |    2 +-
 .../reusables/user-settings/github_apps.md    |    2 +-
 .../user-settings/github_apps_advanced.md     |    2 +-
 .../user-settings/marketplace_apps.md         |    2 +-
 .../user-settings/modify_github_app.md        |    2 +-
 .../reusables/user-settings/oauth_apps.md     |    2 +-
 .../user-settings/update_oauth_app.md         |    2 +-
 .../about-commit-email-addresses.md           |    2 +-
 .../reusables/user_settings/billing_plans.md  |    2 +-
 .../codespaces-secret-repository-access.md    |    2 +-
 .../user_settings/codespaces-secret-value.md  |    2 +-
 .../reusables/user_settings/codespaces-tab.md |    2 +-
 .../reusables/user_settings/export-data.md    |    4 +-
 .../keeping_your_email_address_private.md     |    2 +-
 .../link_email_with_your_account.md           |    4 +-
 ...word-authentication-deprecation-desktop.md |    2 +-
 .../password-authentication-deprecation.md    |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../user_settings/personal_dashboard.md       |    2 +-
 .../user_settings/review_oauth_tokens_tip.md  |    2 +-
 .../user_settings/security-analysis.md        |    2 +-
 .../data/reusables/user_settings/security.md  |    6 +-
 .../set_your_email_address_in_git.md          |    2 +-
 .../reusables/webhooks/action_type_desc.md    |    2 +-
 .../reusables/webhooks/app_always_desc.md     |    2 +-
 .../ja-JP/data/reusables/webhooks/app_desc.md |    2 +-
 .../reusables/webhooks/authorization_event.md |    2 +-
 .../webhooks/check_run_properties.md          |   24 +-
 .../webhooks/check_run_short_desc.md          |    2 +-
 .../webhooks/check_suite_properties.md        |   20 +-
 .../webhooks/check_suite_short_desc.md        |    2 +-
 .../code_scanning_alert_event_properties.md   |   12 +-
 .../code_scanning_alert_event_short_desc.md   |    2 +-
 .../webhooks/commit_comment_short_desc.md     |    2 +-
 .../webhooks/content_reference_short_desc.md  |    2 +-
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../reusables/webhooks/create_short_desc.md   |    2 +-
 .../reusables/webhooks/delete_properties.md   |    8 +-
 .../reusables/webhooks/delete_short_desc.md   |    2 +-
 .../webhooks/deploy_key_properties.md         |    8 +-
 .../webhooks/deploy_key_short_desc.md         |    2 +-
 .../webhooks/deployment_short_desc.md         |    2 +-
 .../webhooks/deployment_status_short_desc.md  |    2 +-
 .../reusables/webhooks/discussion_desc.md     |    2 +-
 .../webhooks/discussions-webhooks-beta.md     |    2 +-
 .../webhooks/enterprise_short_desc.md         |    2 +-
 .../reusables/webhooks/events_api_payload.md  |    2 +-
 .../reusables/webhooks/fork_properties.md     |    6 +-
 .../reusables/webhooks/fork_short_desc.md     |    2 +-
 .../reusables/webhooks/gollum_properties.md   |   16 +-
 .../reusables/webhooks/gollum_short_desc.md   |    2 +-
 .../webhooks/installation_properties.md       |    8 +-
 .../installation_repositories_properties.md   |   12 +-
 .../installation_repositories_short_desc.md   |    2 +-
 .../webhooks/installation_short_desc.md       |    2 +-
 .../webhooks/issue_comment_properties.md      |    2 +-
 .../webhooks/issue_comment_short_desc.md      |    2 +-
 .../issue_comment_webhook_properties.md       |    6 +-
 .../webhooks/issue_event_api_properties.md    |    6 +-
 .../reusables/webhooks/issue_properties.md    |    2 +-
 .../webhooks/issue_webhook_properties.md      |    6 +-
 .../reusables/webhooks/issues_short_desc.md   |    2 +-
 .../reusables/webhooks/label_short_desc.md    |    2 +-
 .../webhooks/member_event_api_properties.md   |    6 +-
 .../reusables/webhooks/member_properties.md   |    2 +-
 .../reusables/webhooks/member_short_desc.md   |    2 +-
 .../webhooks/member_webhook_properties.md     |    2 +-
 .../webhooks/membership_properties.md         |   12 +-
 .../webhooks/membership_short_desc.md         |    2 +-
 .../webhooks/milestone_properties.md          |   16 +-
 .../webhooks/milestone_short_desc.md          |    2 +-
 .../webhooks/org_block_short_desc.md          |    2 +-
 .../ja-JP/data/reusables/webhooks/org_desc.md |    2 +-
 .../reusables/webhooks/org_desc_graphql.md    |    2 +-
 .../webhooks/organization_short_desc.md       |    2 +-
 .../reusables/webhooks/package_properties.md  |    8 +-
 .../webhooks/page_build_short_desc.md         |    2 +-
 .../data/reusables/webhooks/payload_url.md    |    2 +-
 .../reusables/webhooks/ping_short_desc.md     |    2 +-
 .../webhooks/project_card_properties.md       |   14 +-
 .../webhooks/project_card_short_desc.md       |    2 +-
 .../webhooks/project_column_properties.md     |   14 +-
 .../webhooks/project_column_short_desc.md     |    2 +-
 .../reusables/webhooks/project_properties.md  |   14 +-
 .../reusables/webhooks/project_short_desc.md  |    2 +-
 .../reusables/webhooks/public_short_desc.md   |    2 +-
 .../pull_request_event_api_properties.md      |    6 +-
 .../webhooks/pull_request_properties.md       |    2 +-
 ...est_review_comment_event_api_properties.md |    6 +-
 .../pull_request_review_comment_properties.md |    2 +-
 .../pull_request_review_comment_short_desc.md |    2 +-
 ...quest_review_comment_webhook_properties.md |    6 +-
 .../pull_request_review_properties.md         |   12 +-
 .../pull_request_review_short_desc.md         |    2 +-
 .../webhooks/pull_request_short_desc.md       |    2 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../reusables/webhooks/push_short_desc.md     |    2 +-
 .../reusables/webhooks/pusher_type_desc.md    |    2 +-
 .../webhooks/release_event_api_properties.md  |    6 +-
 .../reusables/webhooks/release_short_desc.md  |    2 +-
 .../webhooks/release_webhook_properties.md    |    2 +-
 .../data/reusables/webhooks/repo_desc.md      |    2 +-
 .../reusables/webhooks/repo_desc_graphql.md   |    2 +-
 .../webhooks/repository_import_properties.md  |    6 +-
 .../webhooks/repository_import_short_desc.md  |    2 +-
 .../webhooks/repository_short_desc.md         |    2 +-
 ...pository_vulnerability_alert_properties.md |    8 +-
 ...pository_vulnerability_alert_short_desc.md |    2 +-
 .../ja-JP/data/reusables/webhooks/secret.md   |    2 +-
 .../secret_scanning_alert_event_properties.md |    8 +-
 .../secret_scanning_alert_event_short_desc.md |    2 +-
 .../data/reusables/webhooks/sender_desc.md    |    2 +-
 .../sponsorship_event_api_properties.md       |    6 +-
 .../webhooks/sponsorship_properties.md        |    2 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 .../sponsorship_webhook_properties.md         |    6 +-
 .../reusables/webhooks/star_properties.md     |    8 +-
 .../reusables/webhooks/star_short_desc.md     |    2 +-
 .../reusables/webhooks/status_short_desc.md   |    2 +-
 .../reusables/webhooks/team_short_desc.md     |    2 +-
 .../reusables/webhooks/watch_properties.md    |    6 +-
 .../reusables/webhooks/watch_short_desc.md    |    2 +-
 .../webhooks/webhooks-rest-api-links.md       |    8 +-
 .../data/reusables/webhooks/webhooks_intro.md |    2 +-
 .../data/reusables/webhooks/webhooks_ssl.md   |    2 +-
 .../data/reusables/webhooks/workflow_desc.md  |    2 +-
 .../reusables/webhooks/workflow_run_desc.md   |    6 +-
 .../webhooks/workflow_run_properties.md       |    8 +-
 translations/ja-JP/data/ui.yml                |  100 +-
 translations/ja-JP/data/variables/actions.yml |    2 +-
 .../data/variables/actions_code_examples.yml  |  186 +--
 .../variables/codespaces_code_examples.yml    |   43 +
 translations/ja-JP/data/variables/contact.yml |   14 +-
 translations/ja-JP/data/variables/desktop.yml |    2 +-
 .../discussions_community_examples.yml        |   22 +-
 translations/ja-JP/data/variables/explore.yml |    6 +-
 translations/ja-JP/data/variables/gists.yml   |    6 +-
 .../ja-JP/data/variables/migrations.yml       |    6 +-
 .../ja-JP/data/variables/notifications.yml    |    4 +-
 translations/ja-JP/data/variables/product.yml |   33 +-
 .../data/variables/release_candidate.yml      |    2 +-
 translations/ja-JP/data/variables/search.yml  |    4 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   16 +-
 .../metadata-syntax-for-github-actions.md     |    8 +-
 .../guides/about-continuous-integration.md    |    3 +
 .../about-packaging-with-github-actions.md    |   34 +-
 .../actions/guides/adding-labels-to-issues.md |    8 +-
 .../guides/building-and-testing-net.md        |  109 +-
 .../guides/building-and-testing-nodejs.md     |   38 +-
 .../guides/building-and-testing-powershell.md |   98 +-
 .../guides/building-and-testing-python.md     |  146 +-
 .../guides/building-and-testing-ruby.md       |  145 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   50 +-
 .../actions/guides/closing-inactive-issues.md |   10 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |   38 +-
 ...ing-to-amazon-elastic-container-service.md |   12 +-
 .../ko-KR/content/actions/guides/index.md     |    3 +
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   28 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  131 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 .../removing-self-hosted-runners.md           |    2 +-
 translations/ko-KR/content/actions/index.md   |   25 -
 ...grating-from-circleci-to-github-actions.md |    4 +-
 .../security-hardening-for-github-actions.md  |   99 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   36 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../reference/authentication-in-a-workflow.md |  111 +-
 ...nd-expression-syntax-for-github-actions.md |   20 +-
 .../actions/reference/encrypted-secrets.md    |   19 +-
 .../reference/environment-variables.md        |    7 +-
 .../content/actions/reference/environments.md |   11 +-
 .../events-that-trigger-workflows.md          |   24 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  182 ++-
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   23 +
 .../ko-KR/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    4 +
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    5 +
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    5 +
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   12 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    2 +
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    7 +
 .../configuration/site-admin-dashboard.md     |    2 +
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   19 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    3 +
 .../monitoring-cluster-nodes.md               |    6 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |    3 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |    2 +
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    5 +-
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   21 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   48 +-
 translations/ko-KR/content/admin/guides.md    |  105 ++
 translations/ko-KR/content/admin/index.md     |   67 +-
 .../ko-KR/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    6 +-
 .../overview/about-enterprise-accounts.md     |    3 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    2 +
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    5 +
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |    3 +
 ...or-advanced-security-in-your-enterprise.md |    7 +
 ...-management-policies-in-your-enterprise.md |    3 +
 .../ko-KR/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../ko-KR/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |    3 +
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    5 +
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    4 +
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    3 +
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    3 +
 .../managing-global-webhooks.md               |    2 +
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    2 +
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    3 +
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |    6 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 ...g-secret-scanning-for-your-repositories.md |   16 +-
 .../managing-alerts-from-secret-scanning.md   |   10 +-
 .../secure-coding/about-code-scanning.md      |   13 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |   92 +-
 ...iguring-codeql-runner-in-your-ci-system.md |  203 +++
 ...-codeql-workflow-for-compiled-languages.md |    2 +
 .../code-security/secure-coding/index.md      |   10 +-
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   27 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   37 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  308 ++++-
 ...tting-up-code-scanning-for-a-repository.md |    2 +
 ...g-code-scanning-alerts-in-pull-requests.md |   16 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   62 +
 .../troubleshooting-the-codeql-workflow.md    |   45 +-
 .../uploading-a-sarif-file-to-github.md       |   69 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../security-advisories/index.md              |    1 -
 ...bout-alerts-for-vulnerable-dependencies.md |   38 +-
 .../about-dependabot-version-updates.md       |    1 +
 .../about-the-dependency-graph.md             |    9 +-
 ...guration-options-for-dependency-updates.md |   42 +-
 ...tifications-for-vulnerable-dependencies.md |   25 +-
 .../enabling-and-disabling-version-updates.md |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   19 +-
 .../supply-chain-security/index.md            |    1 +
 ...he-detection-of-vulnerable-dependencies.md |   20 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   30 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../ko-KR/content/codespaces/guides.md        |   28 +
 .../ko-KR/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../ko-KR/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  142 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...nblocking-a-user-from-your-organization.md |    4 +-
 ...-who-are-blocked-from-your-organization.md |    4 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 ...reating-a-default-community-health-file.md |   10 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../creating-a-github-app-from-a-manifest.md  |    2 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 .../making-a-github-app-public-or-private.md  |    6 +-
 .../developers/apps/scopes-for-oauth-apps.md  |    2 +-
 ...ment-environment-to-create-a-github-app.md |    4 +-
 .../apps/using-content-attachments.md         |   11 +-
 ...sher-verification-for-your-organization.md |    6 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../developers/overview/secret-scanning.md    |   51 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../webhooks-and-events/github-event-types.md |    2 +-
 .../webhook-events-and-payloads.md            |   14 +-
 .../participating-in-a-discussion.md          |    2 +-
 .../ko-KR/content/discussions/index.md        |   21 -
 .../about-protected-branches.md               |   10 +
 .../changing-the-default-branch.md            |    2 +-
 ...imiting-github-actions-for-a-repository.md |   18 +
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 ...d-analysis-settings-for-your-repository.md |   13 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 .../renaming-a-branch.md                      |   10 +-
 .../restoring-a-deleted-repository.md         |    4 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-commit-signature-verification.md    |   28 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |    9 +
 .../checking-for-existing-gpg-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../creating-a-personal-access-token.md       |   10 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-unknown-key-type.md                 |   35 +
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../github/authenticating-to-github/index.md  |    4 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    2 +-
 .../reviewing-your-security-log.md            |   61 +-
 .../using-ssh-over-the-https-port.md          |    2 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-status-checks.md                    |   12 +-
 .../changing-the-stage-of-a-pull-request.md   |    8 +
 .../checking-out-pull-requests-locally.md     |    8 +
 .../commenting-on-a-pull-request.md           |    2 +-
 .../creating-a-pull-request.md                |    8 +
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 .../index.md                                  |    7 +-
 .../merging-a-pull-request.md                 |    8 +
 .../quickstart-for-communicating-on-github.md |  149 +++
 .../about-readmes.md                          |   14 +-
 .../creating-a-repository-from-a-template.md  |    2 +-
 .../creating-a-template-repository.md         |    2 +-
 .../licensing-a-repository.md                 |    4 +-
 .../about-code-scanning.md                    |   14 +-
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |   68 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    6 +-
 ...-codeql-workflow-for-compiled-languages.md |    8 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   62 +-
 ...ing-codeql-code-scanning-in-a-container.md |   31 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   14 +-
 .../sarif-support-for-code-scanning.md        |    2 +
 ...tting-up-code-scanning-for-a-repository.md |    8 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   24 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    2 +
 .../troubleshooting-the-codeql-workflow.md    |   49 +-
 .../uploading-a-sarif-file-to-github.md       |   57 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../about-git-subtree-merges.md               |    2 +
 .../getting-started-with-github/be-social.md  |   10 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |    4 +-
 .../fork-a-repo.md                            |    5 +-
 ...etting-changes-from-a-remote-repository.md |    2 +
 .../git-workflows.md                          |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../keyboard-shortcuts.md                     |    6 +-
 .../learning-about-github.md                  |    2 +-
 .../getting-started-with-github/set-up-git.md |    2 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 .../using-git-rebase-on-the-command-line.md   |    2 +
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 translations/ko-KR/content/github/index.md    |    2 -
 .../deleting-files-in-a-repository.md         |    2 +-
 .../navigating-code-on-github.md              |    2 +
 ...oving-files-from-git-large-file-storage.md |    2 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   55 +-
 ...tifications-for-vulnerable-dependencies.md |   18 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   10 +-
 .../configuring-notifications.md              |   24 +-
 .../managing-your-subscriptions.md            |   20 +-
 .../viewing-your-subscriptions.md             |   11 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   22 +-
 .../managing-labels.md                        |    2 +
 .../sorting-issues-and-pull-requests.md       |    4 +-
 .../searching-code.md                         |    3 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   26 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 .../downgrading-git-large-file-storage.md     |    9 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   26 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   12 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    7 +-
 ...ing-your-github-advanced-security-usage.md |   14 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 ...n-azure-subscription-to-your-enterprise.md |    2 +-
 ...ons-policies-in-your-enterprise-account.md |   16 +
 .../index.md                                  |    4 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |    9 +
 .../about-your-organizations-profile.md       |    2 +-
 .../personalizing-your-profile.md             |   92 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../managing-your-theme-settings.md           |   15 +-
 ...on-levels-for-a-user-account-repository.md |    4 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 .../github-candidate-privacy-policy.md        |    4 +-
 .../github-corporate-terms-of-service.md      |    2 +
 ...d-data-protection-for-your-organization.md |    3 -
 .../site-policy/github-privacy-statement.md   |    2 +-
 ...out-the-california-consumer-privacy-act.md |    4 +-
 .../about-the-dependency-graph.md             |   46 +-
 ...loring-the-dependencies-of-a-repository.md |   68 +-
 ...ium-support-for-github-enterprise-cloud.md |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |    6 +-
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    2 +-
 .../content/graphql/overview/explorer.md      |    2 +-
 .../graphql/reference/input-objects.md        |    5 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 ...tting-your-timezone-for-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    1 -
 .../managing-available-metrics-and-reports.md |    1 -
 .../managing-contributors-and-teams.md        |    3 +-
 .../managing-events.md                        |    3 +-
 .../managing-goals.md                         |    1 -
 .../managing-organizations.md                 |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../managing-repositories.md                  |    1 -
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../accessing-your-organizations-settings.md  |    3 +-
 .../about-team-discussions.md                 |    2 +-
 .../keeping-your-organization-secure/index.md |    2 +-
 ...owed-ip-addresses-for-your-organization.md |   12 +-
 ...analysis-settings-for-your-organization.md |   45 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ing-the-audit-log-for-your-organization.md |   84 +-
 ...ur-organizations-installed-integrations.md |    3 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...access-to-an-organization-project-board.md |    2 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...ganizations-ssh-certificate-authorities.md |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    3 +-
 ...-your-organizations-dependency-insights.md |    3 +-
 .../deleting-an-organization-account.md       |    3 +-
 ...ng-github-actions-for-your-organization.md |   31 +-
 .../managing-organization-settings/index.md   |    2 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    3 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...ithub-pages-sites-for-your-organization.md |    3 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    3 +-
 ...epository-creation-in-your-organization.md |    3 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 ...r-deleting-or-transferring-repositories.md |    3 +-
 ...eation-permissions-in-your-organization.md |    3 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...ership-continuity-for-your-organization.md |    6 +
 .../permission-levels-for-an-organization.md  |    6 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...ms-to-improved-organization-permissions.md |    3 +-
 ...-team-discussions-for-your-organization.md |    3 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 translations/ko-KR/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   85 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../packages/learn-github-packages/index.md   |   10 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  133 ++
 .../publishing-a-package.md                   |    8 +-
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  450 +++++++
 .../ko-KR/content/packages/quickstart.md      |   13 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  124 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  262 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  215 +++
 .../working-with-the-nuget-registry.md        |  236 ++++
 .../working-with-the-rubygems-registry.md     |  152 +++
 ...ustom-domain-for-your-github-pages-site.md |    4 +-
 .../about-github-pages.md                     |    8 -
 ...reating-a-github-pages-site-with-jekyll.md |    7 +-
 .../getting-started-with-the-rest-api.md      |   12 +-
 .../ko-KR/content/rest/overview/libraries.md  |    2 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../overview/resources-in-the-rest-api.md     |   30 +-
 .../ko-KR/content/rest/reference/activity.md  |   10 +-
 .../ko-KR/content/rest/reference/emojis.md    |    2 +-
 .../rest/reference/enterprise-admin.md        |   13 -
 .../ko-KR/content/rest/reference/git.md       |    2 +-
 .../ko-KR/content/rest/reference/markdown.md  |    2 +-
 .../ko-KR/content/rest/reference/meta.md      |    2 +-
 .../ko-KR/content/rest/reference/packages.md  |    2 +-
 .../permissions-required-for-github-apps.md   |   13 +
 .../ko-KR/content/rest/reference/repos.md     |    3 +-
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/ko-KR/content/sponsors/guides.md |   18 +
 translations/ko-KR/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../ko-KR/data/glossaries/external.yml        |    6 +-
 .../ko-KR/data/glossaries/internal.yml        |    6 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../ko-KR/data/learning-tracks/README.md      |   29 +-
 .../ko-KR/data/learning-tracks/actions.yml    |    1 +
 .../ko-KR/data/learning-tracks/admin.yml      |   72 +
 .../ko-KR/data/release-notes/2-21/19.yml      |   18 +
 .../ko-KR/data/release-notes/2-21/20.yml      |   19 +
 .../ko-KR/data/release-notes/2-21/21.yml      |   15 +
 .../ko-KR/data/release-notes/2-21/6.yml       |  Bin 4573 -> 4674 bytes
 .../ko-KR/data/release-notes/2-22/11.yml      |   19 +
 .../ko-KR/data/release-notes/2-22/12.yml      |   22 +
 .../ko-KR/data/release-notes/2-22/13.yml      |   20 +
 .../ko-KR/data/release-notes/3-0/0.yml        |    1 +
 .../ko-KR/data/release-notes/3-0/1.yml        |    1 +
 .../ko-KR/data/release-notes/3-0/2.yml        |    1 +
 .../ko-KR/data/release-notes/3-0/3.yml        |    1 +
 .../ko-KR/data/release-notes/3-0/4.yml        |    1 +
 .../ko-KR/data/release-notes/3-0/5.yml        |   27 +
 .../ko-KR/data/release-notes/3-0/6.yml        |   30 +
 .../ko-KR/data/release-notes/3-0/7.yml        |   23 +
 .../ko-KR/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../ko-KR/data/reusables/cli/cli-auth.md      |    1 +
 .../ko-KR/data/reusables/cli/cli-manual.md    |    1 +
 .../ko-KR/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    2 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../gated-features/actions-shared.md          |    2 +-
 .../reusables/gated-features/code-scanning.md |    4 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../ko-KR/data/reusables/gpg/x-509-key.md     |    2 +-
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   31 +
 .../authenticate-packages-github-token.md     |    1 +
 .../package_registry/authenticate-packages.md |   17 +-
 ...uthenticate-to-container-registry-steps.md |    2 +-
 ...nticate_with_pat_for_container_registry.md |    4 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 .../data/reusables/secret-scanning/beta.md    |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../link-browsing-advisory-db.md              |    5 +
 .../security/displayed-information.md         |    4 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../keeping_your_email_address_private.md     |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../code_scanning_alert_event_properties.md   |   12 +-
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 translations/ko-KR/data/ui.yml                |   46 +-
 .../variables/codespaces_code_examples.yml    |   43 +
 .../ko-KR/data/variables/migrations.yml       |    2 +-
 translations/ko-KR/data/variables/product.yml |    5 +-
 .../data/variables/release_candidate.yml      |    2 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   26 +-
 .../metadata-syntax-for-github-actions.md     |   12 +-
 .../guides/about-continuous-integration.md    |    3 +
 .../about-packaging-with-github-actions.md    |   33 +-
 .../actions/guides/adding-labels-to-issues.md |    8 +-
 .../guides/building-and-testing-net.md        |  109 +-
 .../guides/building-and-testing-nodejs.md     |   38 +-
 .../guides/building-and-testing-powershell.md |   98 +-
 .../guides/building-and-testing-python.md     |  180 +--
 .../guides/building-and-testing-ruby.md       |  145 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   60 +-
 .../actions/guides/closing-inactive-issues.md |   10 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |  180 +--
 ...ing-to-amazon-elastic-container-service.md |   12 +-
 .../pt-BR/content/actions/guides/index.md     |    3 +
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   90 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  145 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 .../adding-self-hosted-runners.md             |   20 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 .../removing-self-hosted-runners.md           |    2 +-
 translations/pt-BR/content/actions/index.md   |   25 -
 .../managing-complex-workflows.md             |   89 +-
 ...grating-from-circleci-to-github-actions.md |    4 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   36 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../pt-BR/content/actions/quickstart.md       |   22 +-
 .../reference/authentication-in-a-workflow.md |  113 +-
 ...nd-expression-syntax-for-github-actions.md |   20 +-
 .../actions/reference/encrypted-secrets.md    |   19 +-
 .../reference/environment-variables.md        |   13 +-
 .../content/actions/reference/environments.md |   11 +-
 .../events-that-trigger-workflows.md          |   24 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  866 +++++++-----
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   23 +
 .../pt-BR/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    4 +
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    5 +
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    9 +-
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   14 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    2 +
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    7 +
 .../configuration/site-admin-dashboard.md     |    2 +
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   19 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    3 +
 .../monitoring-cluster-nodes.md               |    6 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |    3 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |    2 +
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    5 +-
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   27 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   48 +-
 translations/pt-BR/content/admin/guides.md    |  105 ++
 translations/pt-BR/content/admin/index.md     |   67 +-
 .../pt-BR/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    4 +
 .../overview/about-enterprise-accounts.md     |    3 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    2 +
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    5 +
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |   39 +-
 ...or-advanced-security-in-your-enterprise.md |    9 +-
 ...-management-policies-in-your-enterprise.md |    3 +
 .../pt-BR/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../pt-BR/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |    3 +
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    5 +
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    4 +
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    3 +
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    3 +
 .../managing-global-webhooks.md               |    2 +
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    2 +
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    3 +
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |    6 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 .../secret-security/about-secret-scanning.md  |    2 +-
 ...g-secret-scanning-for-your-repositories.md |   16 +-
 .../managing-alerts-from-secret-scanning.md   |   10 +-
 .../secure-coding/about-code-scanning.md      |   13 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |   98 +-
 ...iguring-codeql-runner-in-your-ci-system.md |  203 +++
 ...-codeql-workflow-for-compiled-languages.md |    2 +
 .../code-security/secure-coding/index.md      |   12 +-
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   27 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   37 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  308 ++++-
 ...tting-up-code-scanning-for-a-repository.md |    2 +
 ...g-code-scanning-alerts-in-pull-requests.md |   16 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   62 +
 .../troubleshooting-the-codeql-workflow.md    |   45 +-
 .../uploading-a-sarif-file-to-github.md       |   69 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../security-advisories/index.md              |    1 -
 .../exploring-security-alerts.md              |   44 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   42 +-
 .../about-dependabot-version-updates.md       |    1 +
 .../about-the-dependency-graph.md             |    9 +-
 ...guration-options-for-dependency-updates.md |   58 +-
 ...configuring-dependabot-security-updates.md |    2 +-
 ...tifications-for-vulnerable-dependencies.md |   25 +-
 .../enabling-and-disabling-version-updates.md |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   21 +-
 .../supply-chain-security/index.md            |    1 +
 ...he-detection-of-vulnerable-dependencies.md |   20 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   30 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../pt-BR/content/codespaces/guides.md        |   28 +
 .../pt-BR/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../pt-BR/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  142 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../pt-BR/content/communities/index.md        |    2 +-
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...nblocking-a-user-from-your-organization.md |    4 +-
 ...-who-are-blocked-from-your-organization.md |    4 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 ...reating-a-default-community-health-file.md |   12 +-
 .../index.md                                  |    2 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../index.md                                  |    2 +-
 .../cherry-picking-a-commit.md                |    2 +-
 .../about-connections-to-github.md            |    2 +-
 ...r-first-repository-using-github-desktop.md |    2 +-
 .../getting-started-with-github-desktop.md    |    2 +-
 .../creating-a-github-app-from-a-manifest.md  |   26 +-
 ...ating-a-github-app-using-url-parameters.md |   10 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 ...g-and-authorizing-users-for-github-apps.md |    2 +-
 .../making-a-github-app-public-or-private.md  |    6 +-
 ...ment-environment-to-create-a-github-app.md |    6 +-
 .../apps/using-content-attachments.md         |   13 +-
 .../about-marketplace-badges.md               |    8 +-
 ...sher-verification-for-your-organization.md |    6 +-
 ...icing-plans-for-github-marketplace-apps.md |    2 +-
 .../requirements-for-listing-an-app.md        |    2 +-
 .../setting-pricing-plans-for-your-listing.md |    4 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../overview/managing-deploy-keys.md          |   36 +-
 .../developers/overview/secret-scanning.md    |  101 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../webhooks-and-events/about-webhooks.md     |   20 +-
 ...iguring-your-server-to-receive-payloads.md |    6 +-
 .../webhooks-and-events/creating-webhooks.md  |   24 +-
 .../webhooks-and-events/github-event-types.md |    4 +-
 .../securing-your-webhooks.md                 |   47 +-
 .../webhook-events-and-payloads.md            | 1187 ++++++++++-------
 .../participating-in-a-discussion.md          |    2 +-
 .../pt-BR/content/discussions/index.md        |   21 -
 .../about-github-campus-program.md            |   12 +-
 ...n-for-a-student-developer-pack-approved.md |    6 +-
 .../create-a-group-assignment.md              |    4 +-
 .../create-an-individual-assignment.md        |    2 +-
 .../about-protected-branches.md               |  132 +-
 .../changing-the-default-branch.md            |    2 +-
 ...imiting-github-actions-for-a-repository.md |   26 +-
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 ...ge-for-pull-requests-in-your-repository.md |    4 +-
 .../managing-releases-in-a-repository.md      |    2 +-
 ...d-analysis-settings-for-your-repository.md |   13 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 ...-the-forking-policy-for-your-repository.md |    2 +-
 .../renaming-a-branch.md                      |   12 +-
 .../renaming-a-repository.md                  |    4 +-
 .../restoring-a-deleted-repository.md         |    4 +-
 .../transferring-a-repository.md              |    2 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-authentication-to-github.md         |   20 +-
 ...authentication-with-saml-single-sign-on.md |    2 +-
 .../about-commit-signature-verification.md    |   30 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |   11 +-
 .../checking-for-existing-gpg-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../creating-a-personal-access-token.md       |   18 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-unknown-key-type.md                 |   35 +
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../github/authenticating-to-github/index.md  |   12 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    2 +-
 .../reviewing-your-security-log.md            |   63 +-
 .../telling-git-about-your-signing-key.md     |    6 +-
 ...updating-your-github-access-credentials.md |   44 +-
 .../using-ssh-over-the-https-port.md          |    4 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 ...reating-a-default-community-health-file.md |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-status-checks.md                    |   12 +-
 .../automatically-merging-a-pull-request.md   |    4 +-
 .../changing-the-stage-of-a-pull-request.md   |    8 +
 .../checking-out-pull-requests-locally.md     |    8 +
 .../commenting-on-a-pull-request.md           |    2 +-
 .../creating-a-pull-request.md                |    8 +
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 .../index.md                                  |    7 +-
 .../merging-a-pull-request.md                 |   13 +-
 .../quickstart-for-communicating-on-github.md |  149 +++
 ...ng-dependency-changes-in-a-pull-request.md |    2 +-
 .../syncing-a-fork.md                         |    2 +-
 ...sitory-is-deleted-or-changes-visibility.md |    2 +-
 ...are-my-commits-linked-to-the-wrong-user.md |   42 +-
 .../about-readmes.md                          |   14 +-
 .../cloning-a-repository.md                   |    2 +-
 .../creating-a-repository-from-a-template.md  |    2 +-
 .../creating-a-template-repository.md         |    2 +-
 .../error-repository-not-found.md             |    4 +-
 .../https-cloning-errors.md                   |    2 +-
 .../licensing-a-repository.md                 |    4 +-
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  130 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    6 +-
 ...-codeql-workflow-for-compiled-languages.md |    8 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   62 +-
 ...ing-codeql-code-scanning-in-a-container.md |   33 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   14 +-
 .../sarif-support-for-code-scanning.md        |    4 +-
 ...tting-up-code-scanning-for-a-repository.md |    8 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   26 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    2 +
 .../troubleshooting-the-codeql-workflow.md    |   49 +-
 .../uploading-a-sarif-file-to-github.md       |   63 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../about-git-subtree-merges.md               |    2 +
 .../about-github-advanced-security.md         |    8 +-
 .../about-remote-repositories.md              |   10 +-
 .../getting-started-with-github/be-social.md  |   10 +-
 .../caching-your-github-credentials-in-git.md |    2 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |    4 +-
 .../fork-a-repo.md                            |    5 +-
 ...etting-changes-from-a-remote-repository.md |    6 +-
 .../getting-started-with-git.md               |    2 +-
 .../git-workflows.md                          |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../keyboard-shortcuts.md                     |  299 +++--
 .../learning-about-github.md                  |    2 +-
 .../managing-remote-repositories.md           |   36 +-
 .../getting-started-with-github/set-up-git.md |    2 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 ...g-a-subfolder-out-into-a-new-repository.md |    2 +-
 .../using-git-rebase-on-the-command-line.md   |    2 +
 ...hy-is-git-always-asking-for-my-password.md |    2 +-
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 ...-differences-between-subversion-and-git.md |    2 +-
 .../deleting-files-in-a-repository.md         |    2 +-
 .../navigating-code-on-github.md              |    2 +
 .../conditions-for-large-files.md             |   12 +-
 ...oving-files-from-git-large-file-storage.md |    2 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   84 +-
 ...tifications-for-vulnerable-dependencies.md |   18 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   10 +-
 .../configuring-notifications.md              |   32 +-
 .../managing-notifications-from-your-inbox.md |  171 +--
 .../managing-your-subscriptions.md            |   20 +-
 .../viewing-your-subscriptions.md             |   11 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 .../about-issues.md                           |   36 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   22 +-
 .../linking-a-pull-request-to-an-issue.md     |   54 +-
 .../sorting-issues-and-pull-requests.md       |    4 +-
 .../searching-code.md                         |    3 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   30 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 .../downgrading-git-large-file-storage.md     |    9 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   26 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   12 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    9 +-
 ...ing-your-github-advanced-security-usage.md |   14 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 ...rganizations-to-your-enterprise-account.md |    2 +-
 ...n-azure-subscription-to-your-enterprise.md |    2 +-
 ...ons-policies-in-your-enterprise-account.md |   18 +
 ...ced-security-in-your-enterprise-account.md |    6 +-
 .../index.md                                  |    4 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |    9 +
 .../about-your-organizations-profile.md       |    2 +-
 .../about-your-profile.md                     |   30 +-
 .../personalizing-your-profile.md             |   92 +-
 .../viewing-contributions-on-your-profile.md  |   87 +-
 ...tributions-not-showing-up-on-my-profile.md |    4 +-
 .../about-your-personal-dashboard.md          |   50 +-
 .../changing-your-github-username.md          |    2 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../index.md                                  |    8 +-
 .../managing-your-theme-settings.md           |   15 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 .../setting-a-backup-email-address.md         |   15 +-
 .../github-additional-product-terms.md        |   16 +-
 .../site-policy/github-and-trade-controls.md  |   16 +-
 .../github-candidate-privacy-policy.md        |    2 +-
 .../github-corporate-terms-of-service.md      |    6 +-
 ...tion-agreement-non-enterprise-customers.md |   10 +-
 ...d-data-protection-for-your-organization.md |    3 -
 .../site-policy/github-privacy-statement.md   |    2 +-
 ...thub-private-information-removal-policy.md |   30 +-
 .../github-sponsors-additional-terms.md       |    6 +-
 .../about-the-dependency-graph.md             |   99 +-
 ...loring-the-dependencies-of-a-repository.md |   68 +-
 ...ium-support-for-github-enterprise-cloud.md |    2 +-
 .../submitting-a-ticket.md                    |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |  218 +--
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    2 +-
 .../graphql/reference/input-objects.md        |    5 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 ...tting-your-timezone-for-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    1 -
 .../managing-available-metrics-and-reports.md |    1 -
 .../managing-contributors-and-teams.md        |    3 +-
 .../managing-events.md                        |    3 +-
 .../managing-goals.md                         |    1 -
 .../managing-organizations.md                 |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../managing-repositories.md                  |    1 -
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../accessing-your-organizations-settings.md  |    3 +-
 .../about-team-discussions.md                 |    2 +-
 .../keeping-your-organization-secure/index.md |    2 +-
 ...owed-ip-addresses-for-your-organization.md |   12 +-
 ...analysis-settings-for-your-organization.md |   49 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ur-organizations-installed-integrations.md |    3 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...access-to-an-organization-project-board.md |    2 +-
 ...-collaborator-to-an-organization-member.md |    2 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...ganizations-ssh-certificate-authorities.md |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    3 +-
 ...-your-organizations-dependency-insights.md |    3 +-
 .../deleting-an-organization-account.md       |    3 +-
 ...ng-github-actions-for-your-organization.md |   35 +-
 .../managing-organization-settings/index.md   |    2 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    3 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...ithub-pages-sites-for-your-organization.md |    7 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    9 +-
 ...epository-creation-in-your-organization.md |    3 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 ...r-deleting-or-transferring-repositories.md |    3 +-
 ...eation-permissions-in-your-organization.md |    3 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...ership-continuity-for-your-organization.md |    6 +
 .../permission-levels-for-an-organization.md  |    6 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...ms-to-improved-organization-permissions.md |    3 +-
 ...-team-discussions-for-your-organization.md |    3 +-
 ...-a-team-with-an-identity-provider-group.md |   10 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 translations/pt-BR/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   85 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../deleting-and-restoring-a-package.md       |    4 +-
 .../packages/learn-github-packages/index.md   |   10 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  133 ++
 .../publishing-a-package.md                   |    8 +-
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  450 +++++++
 .../pt-BR/content/packages/quickstart.md      |   13 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  124 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  263 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  218 +++
 .../working-with-the-nuget-registry.md        |  236 ++++
 .../working-with-the-rubygems-registry.md     |  151 +++
 .../about-custom-domains-and-github-pages.md  |    8 +-
 ...ustom-domain-for-your-github-pages-site.md |   26 +-
 ...hooting-custom-domains-and-github-pages.md |    6 +-
 .../about-github-pages.md                     |   10 +-
 ...he-visibility-of-your-github-pages-site.md |    2 +-
 .../unpublishing-a-github-pages-site.md       |    2 +-
 translations/pt-BR/content/pages/index.md     |    2 +-
 .../about-github-pages-and-jekyll.md          |    2 +-
 ...reating-a-github-pages-site-with-jekyll.md |    7 +-
 ...r-github-pages-site-locally-with-jekyll.md |    2 +-
 .../getting-started-with-the-rest-api.md      |   12 +-
 .../pt-BR/content/rest/overview/libraries.md  |    2 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../overview/resources-in-the-rest-api.md     |   30 +-
 .../pt-BR/content/rest/reference/activity.md  |   10 +-
 .../pt-BR/content/rest/reference/emojis.md    |    2 +-
 .../rest/reference/enterprise-admin.md        |   45 +-
 .../pt-BR/content/rest/reference/gists.md     |   26 +-
 .../pt-BR/content/rest/reference/git.md       |    2 +-
 .../pt-BR/content/rest/reference/meta.md      |    2 +-
 .../permissions-required-for-github-apps.md   |   21 +-
 .../pt-BR/content/rest/reference/repos.md     |  229 ++--
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/pt-BR/content/sponsors/guides.md |   18 +
 translations/pt-BR/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../pt-BR/data/glossaries/external.yml        |    8 +-
 .../pt-BR/data/glossaries/internal.yml        |    6 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../pt-BR/data/learning-tracks/README.md      |   29 +-
 .../pt-BR/data/learning-tracks/actions.yml    |    1 +
 .../pt-BR/data/learning-tracks/admin.yml      |   72 +
 .../pt-BR/data/release-notes/2-21/19.yml      |   18 +
 .../pt-BR/data/release-notes/2-21/20.yml      |   19 +
 .../pt-BR/data/release-notes/2-21/21.yml      |   15 +
 .../pt-BR/data/release-notes/2-22/11.yml      |   19 +
 .../pt-BR/data/release-notes/2-22/12.yml      |   22 +
 .../pt-BR/data/release-notes/2-22/13.yml      |   20 +
 .../pt-BR/data/release-notes/3-0/0.yml        |    1 +
 .../pt-BR/data/release-notes/3-0/1.yml        |    1 +
 .../pt-BR/data/release-notes/3-0/2.yml        |    1 +
 .../pt-BR/data/release-notes/3-0/3.yml        |    1 +
 .../pt-BR/data/release-notes/3-0/4.yml        |    1 +
 .../pt-BR/data/release-notes/3-0/5.yml        |   27 +
 .../pt-BR/data/release-notes/3-0/6.yml        |   30 +
 .../pt-BR/data/release-notes/3-0/7.yml        |   23 +
 .../pt-BR/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../deprecating_auth_with_query_parameters.md |    4 +-
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../pt-BR/data/reusables/cli/cli-auth.md      |    1 +
 .../pt-BR/data/reusables/cli/cli-manual.md    |    1 +
 .../pt-BR/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    2 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../business.md                               |    3 +-
 .../gated-features/actions-shared.md          |    2 +-
 .../reusables/gated-features/code-scanning.md |    4 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 ...-runner-management-permissions-required.md |   14 +-
 ...-runner-navigate-to-repo-org-enterprise.md |   24 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../pt-BR/data/reusables/gpg/x-509-key.md     |    2 +-
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   30 +
 .../authenticate-packages-github-token.md     |    1 +
 .../package_registry/authenticate-packages.md |   17 +-
 ...uthenticate-to-container-registry-steps.md |    2 +-
 ...nticate_with_pat_for_container_registry.md |    4 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../security-alerts-x-github-severity.md      |    2 +-
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 ...quash-and-rebase-linear-commit-hisitory.md |    2 +-
 .../reusables/repositories/suggest-changes.md |    3 +-
 .../data/reusables/secret-scanning/beta.md    |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../link-browsing-advisory-db.md              |    5 +
 .../security/displayed-information.md         |    4 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../keeping_your_email_address_private.md     |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../code_scanning_alert_event_properties.md   |   12 +-
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 translations/pt-BR/data/ui.yml                |   46 +-
 .../variables/codespaces_code_examples.yml    |   43 +
 .../pt-BR/data/variables/migrations.yml       |    2 +-
 translations/pt-BR/data/variables/product.yml |    5 +-
 .../data/variables/release_candidate.yml      |    2 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   16 +-
 .../metadata-syntax-for-github-actions.md     |    8 +-
 .../guides/about-continuous-integration.md    |    3 +
 .../about-packaging-with-github-actions.md    |   34 +-
 .../actions/guides/adding-labels-to-issues.md |    8 +-
 .../guides/building-and-testing-net.md        |  109 +-
 .../guides/building-and-testing-nodejs.md     |   38 +-
 .../guides/building-and-testing-powershell.md |   98 +-
 .../guides/building-and-testing-python.md     |  146 +-
 .../guides/building-and-testing-ruby.md       |  145 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   50 +-
 .../actions/guides/closing-inactive-issues.md |   10 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |   38 +-
 ...ing-to-amazon-elastic-container-service.md |   12 +-
 .../ru-RU/content/actions/guides/index.md     |    3 +
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   28 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  131 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 .../removing-self-hosted-runners.md           |    2 +-
 translations/ru-RU/content/actions/index.md   |   31 +-
 ...grating-from-circleci-to-github-actions.md |    4 +-
 .../security-hardening-for-github-actions.md  |   99 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   36 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../reference/authentication-in-a-workflow.md |  111 +-
 ...nd-expression-syntax-for-github-actions.md |   20 +-
 .../actions/reference/encrypted-secrets.md    |   19 +-
 .../reference/environment-variables.md        |    7 +-
 .../content/actions/reference/environments.md |   11 +-
 .../events-that-trigger-workflows.md          |   24 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  182 ++-
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...s-to-manage-access-to-ae-hosted-runners.md |    2 +-
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   23 +
 .../ru-RU/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    4 +
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    5 +
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    5 +
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   12 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    2 +
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    9 +-
 .../configuration/site-admin-dashboard.md     |    2 +
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   19 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    3 +
 .../monitoring-cluster-nodes.md               |    6 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |    3 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |    2 +
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    5 +-
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   21 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   48 +-
 translations/ru-RU/content/admin/guides.md    |  105 ++
 translations/ru-RU/content/admin/index.md     |   69 +-
 .../ru-RU/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    6 +-
 .../overview/about-enterprise-accounts.md     |    3 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    2 +
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    5 +
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |    3 +
 ...or-advanced-security-in-your-enterprise.md |    7 +
 ...-management-policies-in-your-enterprise.md |    3 +
 .../ru-RU/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../ru-RU/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |    3 +
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    5 +
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    4 +
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    3 +
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    3 +
 .../managing-global-webhooks.md               |    2 +
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    2 +
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    3 +
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |    8 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 ...g-secret-scanning-for-your-repositories.md |   16 +-
 .../code-security/secret-security/index.md    |    2 +-
 .../managing-alerts-from-secret-scanning.md   |   12 +-
 .../secure-coding/about-code-scanning.md      |   13 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |   92 +-
 ...iguring-codeql-runner-in-your-ci-system.md |  203 +++
 ...-codeql-workflow-for-compiled-languages.md |    2 +
 .../code-security/secure-coding/index.md      |   10 +-
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   27 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   37 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  308 ++++-
 ...tting-up-code-scanning-for-a-repository.md |    2 +
 ...g-code-scanning-alerts-in-pull-requests.md |   16 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   62 +
 .../troubleshooting-the-codeql-workflow.md    |   45 +-
 .../uploading-a-sarif-file-to-github.md       |   69 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    6 +-
 .../security-advisories/index.md              |    1 -
 ...bout-alerts-for-vulnerable-dependencies.md |   38 +-
 .../about-dependabot-version-updates.md       |    3 +-
 .../about-dependency-review.md                |    2 +-
 .../about-the-dependency-graph.md             |    9 +-
 ...guration-options-for-dependency-updates.md |   42 +-
 ...tifications-for-vulnerable-dependencies.md |   25 +-
 .../customizing-dependency-updates.md         |    2 +-
 .../enabling-and-disabling-version-updates.md |    4 +-
 ...loring-the-dependencies-of-a-repository.md |   19 +-
 .../supply-chain-security/index.md            |    1 +
 ...your-dependencies-updated-automatically.md |    2 +-
 ...ndencies-configured-for-version-updates.md |    2 +-
 ...ng-pull-requests-for-dependency-updates.md |    2 +-
 ...he-detection-of-vulnerable-dependencies.md |   20 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   30 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../ru-RU/content/codespaces/guides.md        |   28 +
 .../ru-RU/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../ru-RU/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  142 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...nblocking-a-user-from-your-organization.md |    4 +-
 ...-who-are-blocked-from-your-organization.md |    4 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 ...reating-a-default-community-health-file.md |   10 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../content/developers/apps/about-apps.md     |    2 +-
 .../activating-optional-features-for-apps.md  |    2 +-
 .../apps/authenticating-with-github-apps.md   |    2 +-
 .../developers/apps/building-github-apps.md   |    2 +-
 .../developers/apps/building-oauth-apps.md    |    2 +-
 .../creating-a-github-app-from-a-manifest.md  |    2 +-
 .../developers/apps/creating-a-github-app.md  |    2 +-
 .../developers/apps/creating-an-oauth-app.md  |    2 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 .../developers/apps/deleting-a-github-app.md  |    2 +-
 .../developers/apps/deleting-an-oauth-app.md  |    2 +-
 .../apps/editing-a-github-apps-permissions.md |    2 +-
 .../apps/getting-started-with-apps.md         |    2 +-
 .../developers/apps/installing-github-apps.md |    2 +-
 .../making-a-github-app-public-or-private.md  |    8 +-
 .../developers/apps/managing-github-apps.md   |    2 +-
 .../developers/apps/managing-oauth-apps.md    |    2 +-
 .../developers/apps/modifying-a-github-app.md |    2 +-
 .../developers/apps/modifying-an-oauth-app.md |    2 +-
 .../apps/rate-limits-for-github-apps.md       |    2 +-
 .../developers/apps/scopes-for-oauth-apps.md  |    2 +-
 .../setting-permissions-for-github-apps.md    |    2 +-
 ...ment-environment-to-create-a-github-app.md |    4 +-
 .../suspending-a-github-app-installation.md   |    2 +-
 .../transferring-ownership-of-a-github-app.md |    2 +-
 .../transferring-ownership-of-an-oauth-app.md |    2 +-
 ...leshooting-authorization-request-errors.md |    2 +-
 ...g-oauth-app-access-token-request-errors.md |    2 +-
 .../apps/using-content-attachments.md         |   11 +-
 ...sher-verification-for-your-organization.md |    6 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../developers/overview/about-githubs-apis.md |    2 +-
 .../overview/github-developer-program.md      |    2 +-
 .../overview/replacing-github-services.md     |    2 +-
 .../developers/overview/secret-scanning.md    |   53 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../overview/viewing-deployment-history.md    |    2 +-
 .../webhooks-and-events/github-event-types.md |    2 +-
 .../webhook-events-and-payloads.md            |   28 +-
 .../participating-in-a-discussion.md          |    2 +-
 .../ru-RU/content/discussions/index.md        |   21 -
 .../integrate-github-classroom-with-an-ide.md |    2 +-
 .../learn-with-github-classroom.md            |    2 +-
 .../about-merge-methods-on-github.md          |    2 +-
 .../about-protected-branches.md               |   12 +-
 .../about-releases.md                         |    2 +-
 .../changing-the-default-branch.md            |    2 +-
 ...classifying-your-repository-with-topics.md |    2 +-
 .../comparing-releases.md                     |    2 +-
 ...tolinks-to-reference-external-resources.md |    2 +-
 ...uring-commit-rebasing-for-pull-requests.md |    2 +-
 .../configuring-pull-request-merges.md        |    2 +-
 ...s-artifacts-and-logs-in-your-repository.md |    2 +-
 ...g-your-repositorys-social-media-preview.md |    2 +-
 ...ining-the-mergeability-of-pull-requests.md |    2 +-
 .../deleting-a-repository.md                  |    2 +-
 ...imiting-github-actions-for-a-repository.md |   20 +-
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 .../linking-to-releases.md                    |    2 +-
 .../managing-a-branch-protection-rule.md      |    2 +-
 ...ge-for-pull-requests-in-your-repository.md |    2 +-
 .../managing-branches-in-your-repository.md   |    2 +-
 ...-objects-in-archives-of-your-repository.md |    2 +-
 .../managing-repository-settings.md           |    2 +-
 ...d-analysis-settings-for-your-repository.md |   13 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 .../releasing-projects-on-github.md           |    2 +-
 .../renaming-a-branch.md                      |   10 +-
 .../restoring-a-deleted-repository.md         |    4 +-
 .../securing-your-repository.md               |    2 +-
 .../transferring-a-repository.md              |    2 +-
 .../troubleshooting-required-status-checks.md |    2 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-commit-signature-verification.md    |   28 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |    9 +
 ...authenticating-with-saml-single-sign-on.md |    2 +-
 .../checking-for-existing-gpg-keys.md         |    2 +-
 .../checking-for-existing-ssh-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../connecting-to-github-with-ssh.md          |    2 +-
 .../creating-a-personal-access-token.md       |   10 +-
 .../deleted-or-missing-ssh-keys.md            |    2 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-agent-admitted-failure-to-sign.md   |    2 +-
 .../error-key-already-in-use.md               |    2 +-
 .../error-permission-denied-publickey.md      |    2 +-
 ...ission-to-userrepo-denied-to-other-user.md |    2 +-
 ...on-to-userrepo-denied-to-userother-repo.md |    2 +-
 ...e-problem-verify-that-the-ca-cert-is-ok.md |    2 +-
 .../error-unknown-key-type.md                 |   35 +
 .../error-were-doing-an-ssh-key-audit.md      |    2 +-
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../githubs-ssh-key-fingerprints.md           |    4 +-
 .../github/authenticating-to-github/index.md  |   12 +-
 .../keeping-your-account-and-data-secure.md   |    4 +-
 .../managing-commit-signature-verification.md |    4 +-
 .../preventing-unauthorized-access.md         |    4 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    4 +-
 .../reviewing-your-deploy-keys.md             |    4 +-
 .../reviewing-your-security-log.md            |   61 +-
 .../testing-your-ssh-connection.md            |    2 +-
 ...eshooting-commit-signature-verification.md |    4 +-
 .../troubleshooting-ssh.md                    |    2 +-
 ...updating-your-github-access-credentials.md |    4 +-
 .../using-ssh-over-the-https-port.md          |    4 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-status-checks.md                    |   14 +-
 .../addressing-merge-conflicts.md             |    2 +-
 .../automatically-merging-a-pull-request.md   |    2 +-
 .../changing-the-stage-of-a-pull-request.md   |    8 +
 .../checking-out-pull-requests-locally.md     |   10 +-
 .../closing-a-pull-request.md                 |    2 +-
 ...repositories-with-code-quality-features.md |    2 +-
 .../commenting-on-a-pull-request.md           |    2 +-
 .../configuring-a-remote-for-a-fork.md        |    2 +-
 .../creating-a-pull-request.md                |    8 +
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 ...corporating-changes-from-a-pull-request.md |    2 +-
 .../index.md                                  |    9 +-
 .../merging-a-pull-request.md                 |    8 +
 ...g-an-upstream-repository-into-your-fork.md |    2 +-
 ...changes-to-your-work-with-pull-requests.md |    2 +-
 .../quickstart-for-communicating-on-github.md |  149 +++
 .../reverting-a-pull-request.md               |    2 +-
 .../reviewing-changes-in-pull-requests.md     |    2 +-
 ...ng-dependency-changes-in-a-pull-request.md |    2 +-
 .../syncing-a-fork.md                         |    2 +-
 .../working-with-forks.md                     |    2 +-
 ...ut-archiving-content-and-data-on-github.md |    2 +-
 .../about-readmes.md                          |   14 +-
 .../about-repository-languages.md             |    2 +-
 .../about-repository-visibility.md            |    2 +-
 .../archiving-a-github-repository.md          |    2 +-
 .../cloning-a-repository-from-github.md       |    2 +-
 .../creating-a-repository-from-a-template.md  |    4 +-
 .../creating-a-repository-on-github.md        |    2 +-
 .../creating-a-template-repository.md         |    4 +-
 .../creating-an-issues-only-repository.md     |    2 +-
 .../duplicating-a-repository.md               |    2 +-
 ...s-to-nonexistent-ref-unable-to-checkout.md |    2 +-
 .../error-repository-not-found.md             |    2 +-
 .../https-cloning-errors.md                   |    2 +-
 .../index.md                                  |    2 +-
 .../licensing-a-repository.md                 |    4 +-
 ...ewing-content-and-diffs-in-a-repository.md |    2 +-
 .../about-code-scanning.md                    |   14 +-
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |   68 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    6 +-
 ...-codeql-workflow-for-compiled-languages.md |    8 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   62 +-
 ...ing-codeql-code-scanning-in-a-container.md |   31 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   14 +-
 .../sarif-support-for-code-scanning.md        |    2 +
 ...tting-up-code-scanning-for-a-repository.md |    8 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   24 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    2 +
 .../troubleshooting-the-codeql-workflow.md    |   49 +-
 .../uploading-a-sarif-file-to-github.md       |   57 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../finding-talent-with-github-jobs/index.md  |    2 +-
 .../about-git-subtree-merges.md               |    2 +
 .../getting-started-with-github/be-social.md  |   10 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |   12 +-
 .../exploring-projects-on-github.md           |    2 +-
 .../faq-about-changes-to-githubs-plans.md     |    2 +-
 .../fork-a-repo.md                            |    5 +-
 ...etting-changes-from-a-remote-repository.md |    2 +
 .../git-workflows.md                          |    2 +-
 .../getting-started-with-github/github-cli.md |    2 +-
 .../github-desktop.md                         |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../keyboard-shortcuts.md                     |    6 +-
 .../learning-about-github.md                  |    2 +-
 .../getting-started-with-github/quickstart.md |    8 +-
 .../getting-started-with-github/set-up-git.md |   10 +-
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 .../signing-up-for-github.md                  |    2 +-
 .../using-git-rebase-on-the-command-line.md   |    2 +
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 translations/ru-RU/content/github/index.md    |    2 -
 .../deleting-files-in-a-repository.md         |    4 +-
 .../managing-files-in-a-repository/index.md   |    2 +-
 .../managing-files-on-github.md               |    2 +-
 .../managing-files-using-the-command-line.md  |    2 +-
 .../moving-a-file-to-a-new-location.md        |    2 +-
 .../navigating-code-on-github.md              |    2 +
 .../renaming-a-file.md                        |    2 +-
 .../rendering-and-diffing-images.md           |    2 +-
 .../rendering-csv-and-tsv-data.md             |    2 +-
 ...endering-differences-in-prose-documents.md |    2 +-
 .../rendering-pdf-documents.md                |    2 +-
 .../tracking-changes-in-a-file.md             |    2 +-
 .../working-with-non-code-files.md            |    2 +-
 ...oving-files-from-git-large-file-storage.md |    2 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   55 +-
 ...tifications-for-vulnerable-dependencies.md |   18 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   12 +-
 .../configuring-notifications.md              |   24 +-
 ...orkflow-for-triaging-your-notifications.md |    2 +-
 .../index.md                                  |    2 +-
 ...ng-subscriptions-for-activity-on-github.md |    2 +-
 .../managing-your-subscriptions.md            |   22 +-
 .../setting-up-notifications.md               |    2 +-
 .../triaging-a-single-notification.md         |    2 +-
 .../viewing-and-triaging-notifications.md     |    2 +-
 .../viewing-your-subscriptions.md             |   11 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 ...bout-duplicate-issues-and-pull-requests.md |    2 +-
 .../archiving-cards-on-a-project-board.md     |    2 +-
 .../changing-project-board-visibility.md      |    2 +-
 .../copying-a-project-board.md                |    2 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 .../disabling-issues.md                       |    2 +-
 ...isabling-project-boards-in-a-repository.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   24 +-
 .../finding-information-in-a-repository.md    |    2 +-
 .../managing-your-work-on-github/index.md     |    2 +-
 .../managing-labels.md                        |    2 +
 .../managing-project-boards.md                |    2 +-
 ...your-work-with-issues-and-pull-requests.md |    2 +-
 .../pinning-an-issue-to-your-repository.md    |    2 +-
 .../sorting-issues-and-pull-requests.md       |    4 +-
 ...tracking-progress-on-your-project-board.md |    2 +-
 ...e-progress-of-your-work-with-milestones.md |    2 +-
 ...ogress-of-your-work-with-project-boards.md |    2 +-
 ...tory-search-in-github-enterprise-server.md |    2 +-
 ...etting-started-with-searching-on-github.md |    2 +-
 .../index.md                                  |    2 +-
 .../searching-code.md                         |    3 +-
 .../searching-on-github.md                    |    2 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   26 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 .../downgrading-git-large-file-storage.md     |    9 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   26 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   12 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    7 +-
 ...ing-your-github-advanced-security-usage.md |   14 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 ...n-azure-subscription-to-your-enterprise.md |    2 +-
 ...ons-policies-in-your-enterprise-account.md |   16 +
 .../index.md                                  |    4 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |    9 +
 .../about-your-organizations-profile.md       |    2 +-
 .../customizing-your-profile.md               |    2 +-
 .../index.md                                  |    2 +-
 ...ing-contribution-graphs-on-your-profile.md |    2 +-
 .../personalizing-your-profile.md             |   92 +-
 ...erview-of-your-activity-on-your-profile.md |    2 +-
 .../accessing-an-organization.md              |    2 +-
 ...best-practices-for-leaving-your-company.md |    2 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../index.md                                  |    2 +-
 ...uity-of-your-user-accounts-repositories.md |    4 +-
 ...ng-access-to-your-personal-repositories.md |    4 +-
 ...ss-to-your-user-accounts-project-boards.md |    2 +-
 .../managing-email-preferences.md             |    4 +-
 .../managing-user-account-settings.md         |    2 +-
 ...naging-your-membership-in-organizations.md |    2 +-
 .../managing-your-theme-settings.md           |   15 +-
 ...on-levels-for-a-user-account-repository.md |    4 +-
 ...izing-or-hiding-organization-membership.md |    2 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 ...ourself-from-a-collaborators-repository.md |    4 +-
 .../removing-yourself-from-an-organization.md |    2 +-
 .../setting-your-commit-email-address.md      |    4 +-
 .../types-of-emails-github-sends.md           |    4 +-
 ...iewing-peoples-roles-in-an-organization.md |    2 +-
 ...does-the-available-for-hire-checkbox-do.md |    2 +-
 .../site-policy/dmca-takedown-policy.md       |    4 +-
 ...ub-bug-bounty-program-legal-safe-harbor.md |    4 +-
 .../github-candidate-privacy-policy.md        |    4 +-
 .../github-community-forum-code-of-conduct.md |    4 +-
 .../github-community-guidelines.md            |    4 +-
 .../github-corporate-terms-of-service.md      |    2 +
 .../github/site-policy/github-event-terms.md  |    4 +-
 .../github-gifts-and-entertainment-policy.md  |    4 +-
 .../github-government-takedown-policy.md      |    4 +-
 ...d-data-protection-for-your-organization.md |    7 +-
 .../github/site-policy/github-logo-policy.md  |    4 +-
 .../github-marketplace-terms-of-service.md    |    4 +-
 .../site-policy/github-privacy-statement.md   |    2 +-
 ...thub-private-information-removal-policy.md |    4 +-
 .../github-registered-developer-agreement.md  |    4 +-
 ...-against-modern-slavery-and-child-labor.md |    4 +-
 .../site-policy/github-trademark-policy.md    |    4 +-
 .../site-policy/github-username-policy.md     |    4 +-
 ...out-the-california-consumer-privacy-act.md |    4 +-
 ...de-to-submitting-a-dmca-takedown-notice.md |    4 +-
 ...delines-for-legal-requests-of-user-data.md |    4 +-
 .../ru-RU/content/github/site-policy/index.md |    4 +-
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../submitting-content-removal-requests.md    |    4 +-
 .../about-githubs-use-of-your-data.md         |    4 +-
 ...-archive-of-your-personal-accounts-data.md |    4 +-
 .../about-the-dependency-graph.md             |   46 +-
 .../accessing-basic-repository-data.md        |    2 +-
 ...lyzing-changes-to-a-repositorys-content.md |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   68 +-
 .../index.md                                  |    2 +-
 .../listing-the-forks-of-a-repository.md      |    2 +-
 ...anding-connections-between-repositories.md |    2 +-
 .../viewing-a-projects-contributors.md        |    2 +-
 .../viewing-a-repositorys-network.md          |    2 +-
 ...iewing-a-summary-of-repository-activity.md |    2 +-
 .../viewing-traffic-to-a-repository.md        |    2 +-
 .../visualizing-commits-in-a-repository.md    |    2 +-
 ...ium-support-for-github-enterprise-cloud.md |    2 +-
 .../about-github-support.md                   |    2 +-
 .../github-enterprise-cloud-support.md        |    2 +-
 .../working-with-github-support/index.md      |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |    6 +-
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../graphql/guides/introduction-to-graphql.md |    2 +-
 .../guides/migrating-from-rest-to-graphql.md  |    2 +-
 .../graphql/guides/using-global-node-ids.md   |    2 +-
 .../graphql/guides/using-the-explorer.md      |    2 +-
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    4 +-
 .../content/graphql/overview/changelog.md     |    2 +-
 .../content/graphql/overview/public-schema.md |    2 +-
 .../graphql/overview/resource-limitations.md  |    2 +-
 .../graphql/overview/schema-previews.md       |    2 +-
 .../ru-RU/content/graphql/reference/enums.md  |    2 +-
 .../graphql/reference/input-objects.md        |    7 +-
 .../content/graphql/reference/interfaces.md   |    2 +-
 .../content/graphql/reference/mutations.md    |    2 +-
 .../content/graphql/reference/objects.md      |    2 +-
 .../content/graphql/reference/scalars.md      |    2 +-
 .../ru-RU/content/graphql/reference/unions.md |    2 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 ...tting-your-timezone-for-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    1 -
 .../managing-available-metrics-and-reports.md |    1 -
 .../managing-contributors-and-teams.md        |    3 +-
 .../managing-events.md                        |    3 +-
 .../managing-goals.md                         |    1 -
 .../managing-organizations.md                 |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../managing-repositories.md                  |    3 +-
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../about-organizations.md                    |    4 +-
 .../about-your-organization-dashboard.md      |    4 +-
 .../about-your-organizations-news-feed.md     |    4 +-
 .../accessing-your-organizations-settings.md  |    7 +-
 .../index.md                                  |    6 +-
 .../about-team-discussions.md                 |    2 +-
 .../index.md                                  |    6 +-
 .../ru-RU/content/organizations/index.md      |    4 +-
 .../keeping-your-organization-secure/index.md |    8 +-
 ...owed-ip-addresses-for-your-organization.md |   16 +-
 ...analysis-settings-for-your-organization.md |   45 +-
 ...tor-authentication-in-your-organization.md |    4 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ing-the-audit-log-for-your-organization.md |   84 +-
 ...ur-organizations-installed-integrations.md |    7 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 .../index.md                                  |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...to-a-project-board-in-your-organization.md |    4 +-
 .../index.md                                  |    6 +-
 ...access-to-an-organization-project-board.md |    6 +-
 ...ator-from-an-organization-project-board.md |    4 +-
 ...tside-collaborator-in-your-organization.md |    4 +-
 .../index.md                                  |    6 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...g-people-with-access-to-your-repository.md |    4 +-
 .../about-ssh-certificate-authorities.md      |    4 +-
 .../index.md                                  |    6 +-
 ...ganizations-ssh-certificate-authorities.md |   10 +-
 ...-accounts-for-people-in-my-organization.md |    4 +-
 .../index.md                                  |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    7 +-
 ...-your-organizations-dependency-insights.md |    7 +-
 ...artifacts-and-logs-in-your-organization.md |    4 +-
 .../converting-an-organization-into-a-user.md |    4 +-
 .../deleting-an-organization-account.md       |    7 +-
 ...ng-github-actions-for-your-organization.md |   35 +-
 .../managing-organization-settings/index.md   |    6 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    7 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...ithub-pages-sites-for-your-organization.md |    3 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    3 +-
 ...epository-creation-in-your-organization.md |    7 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    7 +-
 ...r-deleting-or-transferring-repositories.md |    7 +-
 ...eation-permissions-in-your-organization.md |    7 +-
 .../transferring-organization-ownership.md    |    4 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...r-permissions-to-an-organization-member.md |    4 +-
 .../index.md                                  |    6 +-
 ...ership-continuity-for-your-organization.md |   11 +-
 .../permission-levels-for-an-organization.md  |    6 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 .../index.md                                  |    6 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...am-to-improved-organization-permissions.md |    4 +-
 .../index.md                                  |    6 +-
 ...ms-to-improved-organization-permissions.md |    7 +-
 .../changing-team-visibility.md               |    4 +-
 .../deleting-a-team.md                        |    4 +-
 ...-team-discussions-for-your-organization.md |    7 +-
 .../organizing-members-into-teams/index.md    |    6 +-
 ...ng-code-review-assignment-for-your-team.md |    4 +-
 ...moving-organization-members-from-a-team.md |    4 +-
 .../renaming-a-team.md                        |    4 +-
 .../setting-your-teams-profile-picture.md     |    4 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    7 +-
 ...cess-restrictions-for-your-organization.md |    7 +-
 ...cess-restrictions-for-your-organization.md |    7 +-
 .../index.md                                  |    6 +-
 translations/ru-RU/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   85 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../packages/learn-github-packages/index.md   |   14 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  133 ++
 .../publishing-a-package.md                   |    8 +-
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  450 +++++++
 .../ru-RU/content/packages/quickstart.md      |   13 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  124 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  262 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  215 +++
 .../working-with-the-nuget-registry.md        |  236 ++++
 .../working-with-the-rubygems-registry.md     |  152 +++
 .../index.md                                  |    4 +-
 ...ustom-domain-for-your-github-pages-site.md |    4 +-
 ...hooting-custom-domains-and-github-pages.md |    2 +-
 .../about-github-pages.md                     |    8 -
 ...he-visibility-of-your-github-pages-site.md |    4 +-
 ...shing-source-for-your-github-pages-site.md |    2 +-
 .../index.md                                  |    4 +-
 ...uring-your-github-pages-site-with-https.md |    2 +-
 .../unpublishing-a-github-pages-site.md       |    2 +-
 .../about-github-pages-and-jekyll.md          |    2 +-
 ...yll-build-errors-for-github-pages-sites.md |    2 +-
 ...reating-a-github-pages-site-with-jekyll.md |    7 +-
 .../index.md                                  |    4 +-
 ...yll-build-errors-for-github-pages-sites.md |    2 +-
 .../guides/best-practices-for-integrators.md  |    2 +-
 .../getting-started-with-the-rest-api.md      |   12 +-
 .../rest/guides/rendering-data-as-graphs.md   |    2 +-
 .../rest/guides/traversing-with-pagination.md |    2 +-
 .../rest/guides/working-with-comments.md      |    2 +-
 .../ru-RU/content/rest/overview/libraries.md  |    4 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../rest/overview/openapi-description.md      |    2 +-
 .../overview/other-authentication-methods.md  |    2 +-
 .../overview/resources-in-the-rest-api.md     |   30 +-
 .../ru-RU/content/rest/reference/activity.md  |   10 +-
 .../ru-RU/content/rest/reference/billing.md   |    2 +-
 .../content/rest/reference/code-scanning.md   |    2 +-
 .../rest/reference/codes-of-conduct.md        |    2 +-
 .../ru-RU/content/rest/reference/emojis.md    |    2 +-
 .../rest/reference/enterprise-admin.md        |   13 -
 .../ru-RU/content/rest/reference/git.md       |    4 +-
 .../ru-RU/content/rest/reference/gitignore.md |    2 +-
 .../ru-RU/content/rest/reference/index.md     |    2 +-
 .../ru-RU/content/rest/reference/licenses.md  |    2 +-
 .../ru-RU/content/rest/reference/markdown.md  |    2 +-
 .../ru-RU/content/rest/reference/meta.md      |    2 +-
 .../ru-RU/content/rest/reference/orgs.md      |    2 +-
 .../ru-RU/content/rest/reference/packages.md  |    2 +-
 .../permissions-required-for-github-apps.md   |   13 +
 .../ru-RU/content/rest/reference/projects.md  |    2 +-
 .../content/rest/reference/rate-limit.md      |    2 +-
 .../ru-RU/content/rest/reference/reactions.md |    2 +-
 .../ru-RU/content/rest/reference/repos.md     |    3 +-
 .../ru-RU/content/rest/reference/teams.md     |    2 +-
 .../ru-RU/content/rest/reference/users.md     |    2 +-
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/ru-RU/content/sponsors/guides.md |   18 +
 translations/ru-RU/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../ru-RU/data/glossaries/external.yml        |    8 +-
 .../ru-RU/data/glossaries/internal.yml        |    8 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../ru-RU/data/learning-tracks/README.md      |   29 +-
 .../ru-RU/data/learning-tracks/actions.yml    |    1 +
 .../ru-RU/data/learning-tracks/admin.yml      |   72 +
 .../ru-RU/data/release-notes/2-21/19.yml      |   18 +
 .../ru-RU/data/release-notes/2-21/20.yml      |   19 +
 .../ru-RU/data/release-notes/2-21/21.yml      |   15 +
 .../ru-RU/data/release-notes/2-22/11.yml      |   19 +
 .../ru-RU/data/release-notes/2-22/12.yml      |   22 +
 .../ru-RU/data/release-notes/2-22/13.yml      |   20 +
 .../ru-RU/data/release-notes/3-0/0.yml        |    1 +
 .../ru-RU/data/release-notes/3-0/1.yml        |    1 +
 .../ru-RU/data/release-notes/3-0/2.yml        |    1 +
 .../ru-RU/data/release-notes/3-0/3.yml        |    1 +
 .../ru-RU/data/release-notes/3-0/4.yml        |    1 +
 .../ru-RU/data/release-notes/3-0/5.yml        |   27 +
 .../ru-RU/data/release-notes/3-0/6.yml        |   30 +
 .../ru-RU/data/release-notes/3-0/7.yml        |   23 +
 .../ru-RU/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../ru-RU/data/reusables/cli/cli-auth.md      |    1 +
 .../ru-RU/data/reusables/cli/cli-manual.md    |    1 +
 .../ru-RU/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    2 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../gated-features/actions-shared.md          |    2 +-
 .../reusables/gated-features/code-scanning.md |    4 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../ru-RU/data/reusables/gpg/x-509-key.md     |    2 +-
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   31 +
 .../authenticate-packages-github-token.md     |    1 +
 .../package_registry/authenticate-packages.md |   17 +-
 ...uthenticate-to-container-registry-steps.md |    2 +-
 ...nticate_with_pat_for_container_registry.md |    4 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 .../data/reusables/secret-scanning/beta.md    |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../link-browsing-advisory-db.md              |    5 +
 .../security/displayed-information.md         |    4 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../keeping_your_email_address_private.md     |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../code_scanning_alert_event_properties.md   |   12 +-
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 translations/ru-RU/data/ui.yml                |   46 +-
 .../variables/codespaces_code_examples.yml    |   43 +
 .../ru-RU/data/variables/migrations.yml       |    2 +-
 translations/ru-RU/data/variables/product.yml |    5 +-
 .../data/variables/release_candidate.yml      |    2 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 .../creating-a-composite-run-steps-action.md  |   14 +-
 .../creating-a-docker-container-action.md     |   16 +-
 .../creating-a-javascript-action.md           |   16 +-
 .../metadata-syntax-for-github-actions.md     |    8 +-
 .../guides/about-continuous-integration.md    |    3 +
 .../about-packaging-with-github-actions.md    |   33 +-
 .../actions/guides/adding-labels-to-issues.md |    8 +-
 .../building-and-testing-java-with-ant.md     |    2 +-
 .../building-and-testing-java-with-gradle.md  |    2 +-
 .../building-and-testing-java-with-maven.md   |    2 +-
 .../guides/building-and-testing-net.md        |  111 +-
 .../guides/building-and-testing-nodejs.md     |   40 +-
 .../guides/building-and-testing-powershell.md |  100 +-
 .../guides/building-and-testing-python.md     |  148 +-
 .../guides/building-and-testing-ruby.md       |  145 +-
 .../guides/building-and-testing-swift.md      |  127 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 ...hing-dependencies-to-speed-up-workflows.md |   50 +-
 .../actions/guides/closing-inactive-issues.md |   10 +-
 ...nting-on-an-issue-when-a-label-is-added.md |    9 +-
 .../creating-postgresql-service-containers.md |   38 +-
 ...ing-to-amazon-elastic-container-service.md |   12 +-
 .../zh-CN/content/actions/guides/index.md     |    3 +
 ...managing-github-actions-with-github-cli.md |   37 +
 .../guides/publishing-docker-images.md        |   28 +-
 .../publishing-java-packages-with-gradle.md   |   28 +-
 .../publishing-java-packages-with-maven.md    |   26 +-
 .../guides/publishing-nodejs-packages.md      |  131 +-
 ...card-is-added-to-a-project-board-column.md |    9 +-
 .../guides/scheduling-issue-creation.md       |    9 +-
 .../adding-self-hosted-runners.md             |   14 +-
 ...ess-to-self-hosted-runners-using-groups.md |    4 +-
 ...and-troubleshooting-self-hosted-runners.md |    2 +
 .../removing-self-hosted-runners.md           |    2 +-
 translations/zh-CN/content/actions/index.md   |   25 -
 ...-from-azure-pipelines-to-github-actions.md |  239 ++--
 ...grating-from-circleci-to-github-actions.md |    6 +-
 ...igrating-from-jenkins-to-github-actions.md |    2 +-
 ...haring-workflows-with-your-organization.md |    8 +-
 ...proving-workflow-runs-from-public-forks.md |   19 +
 .../disabling-and-enabling-a-workflow.md      |   30 +-
 .../downloading-workflow-artifacts.md         |   32 +
 .../actions/managing-workflow-runs/index.md   |    1 +
 .../manually-running-a-workflow.md            |   36 +-
 .../re-running-a-workflow.md                  |   18 +
 .../removing-workflow-artifacts.md            |    2 +-
 .../using-workflow-run-logs.md                |   28 +
 .../viewing-workflow-run-history.md           |   58 +
 .../zh-CN/content/actions/quickstart.md       |   28 +-
 .../reference/authentication-in-a-workflow.md |  111 +-
 ...nd-expression-syntax-for-github-actions.md |   20 +-
 .../actions/reference/encrypted-secrets.md    |  143 +-
 .../reference/environment-variables.md        |   13 +-
 .../events-that-trigger-workflows.md          |   24 +-
 .../zh-CN/content/actions/reference/index.md  |   32 +-
 .../workflow-commands-for-github-actions.md   |   10 +-
 .../workflow-syntax-for-github-actions.md     |  184 ++-
 .../about-github-hosted-runners.md            |    5 +-
 .../customizing-github-hosted-runners.md      |   90 ++
 .../using-github-hosted-runners/index.md      |    1 +
 ...-licensing-for-github-advanced-security.md |   37 +
 ...guring-code-scanning-for-your-appliance.md |   79 ++
 ...ring-secret-scanning-for-your-appliance.md |   75 ++
 ...b-advanced-security-for-your-enterprise.md |   88 ++
 .../content/admin/advanced-security/index.md  |   21 +
 ...ing-your-github-advanced-security-usage.md |   23 +
 .../zh-CN/content/admin/all-releases.md       |   37 +
 ...d-access-management-for-your-enterprise.md |    7 +
 ...or-users-outside-your-identity-provider.md |    4 +
 .../changing-authentication-methods.md        |    4 +
 ...ning-for-your-enterprise-using-azure-ad.md |    7 +
 ...saml-single-sign-on-for-your-enterprise.md |    7 +
 ...g-user-provisioning-for-your-enterprise.md |    7 +
 .../disabling-unauthenticated-sign-ups.md     |    3 +
 .../using-built-in-authentication.md          |    4 +
 .../content/admin/authentication/using-cas.md |    5 +
 .../admin/authentication/using-ldap.md        |    4 +
 .../admin/authentication/using-saml.md        |    5 +
 .../about-enterprise-configuration.md         |    7 +-
 .../accessing-the-administrative-shell-ssh.md |    3 +
 .../accessing-the-management-console.md       |    2 +
 .../configuration/command-line-utilities.md   |   16 +-
 .../configuration/configuring-a-hostname.md   |    3 +
 ...onfiguring-an-outbound-web-proxy-server.md |    4 +
 .../configuration/configuring-applications.md |    2 +
 .../configuring-backups-on-your-appliance.md  |    5 +
 .../configuring-built-in-firewall-rules.md    |    4 +
 ...ing-data-encryption-for-your-enterprise.md |   59 +-
 .../configuring-dns-nameservers.md            |    4 +
 .../configuring-email-for-notifications.md    |    4 +
 ...guring-github-pages-for-your-enterprise.md |    2 +
 .../configuration/configuring-rate-limits.md  |    3 +
 ...dress-using-the-virtual-machine-console.md |    4 +
 .../configuring-time-synchronization.md       |    4 +
 .../admin/configuration/configuring-tls.md    |    5 +
 ...prise-server-to-github-enterprise-cloud.md |    4 +
 ...ependencies-on-github-enterprise-server.md |    2 +
 ...nabling-and-scheduling-maintenance-mode.md |    4 +
 ...rise-server-and-github-enterprise-cloud.md |    3 +
 .../configuration/enabling-private-mode.md    |    8 +
 .../enabling-subdomain-isolation.md           |    7 +-
 ...-github-enterprise-server-and-githubcom.md |    2 +
 ...-github-enterprise-server-and-githubcom.md |    2 +
 .../content/admin/configuration/index.md      |    4 +-
 .../configuration/initializing-github-ae.md   |   13 +-
 ...g-github-for-mobile-for-your-enterprise.md |    2 +
 .../admin/configuration/network-ports.md      |    4 +
 ...ting-network-traffic-to-your-enterprise.md |    7 +
 .../configuration/site-admin-dashboard.md     |    2 +
 .../troubleshooting-ssl-errors.md             |    6 +
 ...-enterprise-server-with-a-load-balancer.md |    4 +
 .../validating-your-domain-settings.md        |    4 +
 ...-approving-a-domain-for-your-enterprise.md |   34 +
 .../about-cluster-nodes.md                    |    2 +
 .../enterprise-management/about-clustering.md |    2 +
 .../about-geo-replication.md                  |    2 +
 .../about-high-availability-configuration.md  |    3 +
 .../accessing-the-monitor-dashboard.md        |    5 +
 .../cluster-network-configuration.md          |    4 +
 .../configuring-collectd.md                   |    5 +
 ...-availability-replication-for-a-cluster.md |    6 +-
 .../creating-a-high-availability-replica.md   |    3 +
 ...een-clustering-and-high-availability-ha.md |    4 +
 .../enabling-automatic-update-checks.md       |    2 +
 .../evacuating-a-cluster-node.md              |    2 +
 .../increasing-cpu-or-memory-resources.md     |    3 +
 .../increasing-storage-capacity.md            |   17 +-
 .../initializing-the-cluster.md               |    2 +
 ...ng-a-failover-to-your-replica-appliance.md |    3 +
 ...ting-a-failover-to-your-replica-cluster.md |    4 +
 ...ng-from-github-enterprise-1110x-to-2123.md |    3 +
 .../monitoring-cluster-nodes.md               |    6 +
 .../monitoring-using-snmp.md                  |    4 +
 .../recommended-alert-thresholds.md           |    5 +
 ...ering-a-high-availability-configuration.md |    3 +
 .../removing-a-high-availability-replica.md   |    4 +
 .../replacing-a-cluster-node.md               |    3 +
 .../setting-up-external-monitoring.md         |    4 +
 .../upgrade-requirements.md                   |    6 +
 .../upgrading-a-cluster.md                    |    3 +
 .../upgrading-github-enterprise-server.md     |   37 +-
 .../about-github-enterprise-support.md        |    2 +
 ...um-support-for-github-enterprise-server.md |    2 +
 ...b-premium-support-for-github-enterprise.md |    2 +
 .../about-support-for-advanced-security.md    |    2 +
 .../preparing-to-submit-a-ticket.md           |    2 +
 .../providing-data-to-github-support.md       |    2 +
 .../reaching-github-support.md                |    2 +
 .../enterprise-support/submitting-a-ticket.md |    2 +
 .../about-using-actions-in-your-enterprise.md |   45 +
 ...rise-server-with-github-actions-enabled.md |    4 +
 ...-githubcom-actions-using-github-connect.md |   13 +-
 ...g-github-actions-with-amazon-s3-storage.md |    2 +-
 ...ions-with-minio-gateway-for-nas-storage.md |    2 +-
 ...ub-actions-policies-for-your-enterprise.md |    3 +
 ...arted-with-github-actions-for-github-ae.md |    5 +
 ...ub-actions-for-github-enterprise-server.md |    1 +
 .../high-availability-for-github-actions.md   |    5 +
 .../content/admin/github-actions/index.md     |    2 +-
 ...manually-syncing-actions-from-githubcom.md |   27 +-
 ...-hosted-runners-without-internet-access.md |    3 +-
 .../using-a-staging-environment.md            |    4 +
 ...version-of-the-official-bundled-actions.md |   48 +-
 translations/zh-CN/content/admin/guides.md    |  105 ++
 translations/zh-CN/content/admin/index.md     |   67 +-
 .../zh-CN/content/admin/installation/index.md |    3 +
 .../setting-up-a-staging-instance.md          |    3 +
 .../admin/overview/about-data-residency.md    |    4 +
 .../overview/about-enterprise-accounts.md     |    2 +
 .../content/admin/overview/about-github-ae.md |    6 +-
 .../about-upgrades-to-new-releases.md         |    6 +-
 .../managing-billing-for-your-enterprise.md   |    4 +-
 ...managing-your-github-enterprise-license.md |    2 +-
 .../content/admin/overview/system-overview.md |    5 +
 ...e-ecosystem-support-for-your-enterprise.md |    2 +
 ...ith-github-packages-for-your-enterprise.md |    3 +
 ...inio-storage-bucket-for-github-packages.md |    3 +
 .../admin/policies/about-pre-receive-hooks.md |    3 +
 ...creating-a-pre-receive-hook-environment.md |    3 +
 .../creating-a-pre-receive-hook-script.md     |    3 +
 ...or-advanced-security-in-your-enterprise.md |    7 +
 ...-management-policies-in-your-enterprise.md |    3 +
 .../zh-CN/content/admin/policies/index.md     |    1 +
 ...-the-github-enterprise-server-appliance.md |    3 +
 ...email-notifications-for-your-enterprise.md |   22 +
 .../zh-CN/content/admin/release-notes.md      |    1 +
 .../admin/user-management/about-migrations.md |    2 +
 .../user-management/adding-people-to-teams.md |    4 +
 .../admin/user-management/audit-logging.md    |    4 +
 .../admin/user-management/audited-actions.md  |    3 +
 .../user-management/auditing-ssh-keys.md      |    4 +
 .../auditing-users-across-your-enterprise.md  |    5 +
 .../best-practices-for-user-security.md       |    3 +
 ...-large-file-storage-for-your-enterprise.md |    4 +
 ...-visibility-for-organization-membership.md |    3 +
 .../continuous-integration-using-jenkins.md   |    2 +
 .../admin/user-management/creating-teams.md   |    4 +
 ...izing-user-messages-for-your-enterprise.md |    3 +
 ...bling-git-ssh-access-on-your-enterprise.md |    4 +
 ...exporting-migration-data-from-githubcom.md |    3 +
 ...ing-migration-data-from-your-enterprise.md |    3 +
 ...rom-third-party-version-control-systems.md |    2 +
 .../admin/user-management/log-forwarding.md   |    4 +
 .../user-management/managing-dormant-users.md |    5 +-
 .../managing-global-webhooks.md               |    2 +
 ...naging-organizations-in-your-enterprise.md |    2 +-
 .../managing-projects-using-jira.md           |   74 +-
 .../migrating-data-to-your-enterprise.md      |    2 +
 .../migrating-to-internal-repositories.md     |   11 +
 ...-a-legal-hold-on-a-user-or-organization.md |    5 +
 ...ring-to-migrate-data-to-your-enterprise.md |    2 +
 ...nting-users-from-creating-organizations.md |    3 +
 ...moting-or-demoting-a-site-administrator.md |    4 +
 .../rebuilding-contributions-data.md          |    3 +
 ...ving-users-from-teams-and-organizations.md |    4 +
 ...ctor-authentication-for-an-organization.md |    5 +
 .../searching-the-audit-log.md                |    3 +
 .../suspending-and-unsuspending-users.md      |    4 +
 .../user-management/viewing-push-logs.md      |    4 +
 .../about-securing-your-repository.md         |    8 +-
 ...ng-a-security-policy-to-your-repository.md |   57 +
 .../code-security/getting-started/index.md    |    1 +
 .../secret-security/about-secret-scanning.md  |    2 +-
 ...g-secret-scanning-for-your-repositories.md |   16 +-
 .../managing-alerts-from-secret-scanning.md   |   10 +-
 .../secure-coding/about-code-scanning.md      |   13 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   62 +
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  262 ++--
 ...iguring-codeql-runner-in-your-ci-system.md |  204 +++
 ...-codeql-workflow-for-compiled-languages.md |    4 +-
 .../code-security/secure-coding/index.md      |   12 +-
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   27 +-
 .../running-codeql-cli-in-your-ci-system.md   |  458 +++++++
 ...ing-codeql-code-scanning-in-a-container.md |   37 +-
 ...running-codeql-runner-in-your-ci-system.md |  161 +++
 .../sarif-support-for-code-scanning.md        |  308 ++++-
 ...tting-up-code-scanning-for-a-repository.md |    4 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   16 +-
 ...hooting-codeql-runner-in-your-ci-system.md |   63 +
 .../uploading-a-sarif-file-to-github.md       |   69 +-
 ...e-scanning-with-your-existing-ci-system.md |    2 +
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 .../security-advisories/index.md              |    1 -
 ...bout-alerts-for-vulnerable-dependencies.md |    4 +-
 .../about-dependabot-version-updates.md       |    1 +
 .../about-the-dependency-graph.md             |    4 +-
 ...guration-options-for-dependency-updates.md |   42 +-
 ...configuring-dependabot-security-updates.md |    2 +-
 ...tifications-for-vulnerable-dependencies.md |    4 +-
 .../enabling-and-disabling-version-updates.md |    2 +-
 ...loring-the-dependencies-of-a-repository.md |   21 +-
 .../supply-chain-security/index.md            |    1 +
 ...he-detection-of-vulnerable-dependencies.md |   20 +-
 ...pendabotcom-to-github-native-dependabot.md |   47 +
 ...nerable-dependencies-in-your-repository.md |   30 +-
 .../content/codespaces/about-codespaces.md    |   67 +
 .../about-billing-for-codespaces.md           |   18 +
 ...pace-to-access-a-private-image-registry.md |   29 +
 .../codespaces/codespaces-reference/index.md  |   14 +
 .../troubleshooting-your-codespace.md         |   68 +
 .../creating-a-codespace.md                   |   61 +
 .../deleting-a-codespace.md                   |   29 +
 .../developing-in-a-codespace.md              |   55 +
 .../forwarding-ports-in-your-codespace.md     |   61 +
 .../developing-in-codespaces/index.md         |   22 +
 .../using-codespaces-in-visual-studio-code.md |   76 ++
 .../using-source-control-in-your-codespace.md |   81 ++
 ...etting-started-with-your-dotnet-project.md |  216 +++
 ...ed-with-your-java-project-in-codespaces.md |  188 +++
 ...-with-your-nodejs-project-in-codespaces.md |  174 +++
 ...-with-your-python-project-in-codespaces.md |  207 +++
 .../getting-started-with-codespaces/index.md  |   17 +
 .../zh-CN/content/codespaces/guides.md        |   28 +
 .../zh-CN/content/codespaces/index.md         |   42 +
 .../index.md                                  |   20 +
 ...urity-for-your-organizations-codespaces.md |   30 +
 ...ository-and-organization-for-codespaces.md |   71 +
 ...-user-permissions-for-your-organization.md |   35 +
 ...organizations-audit-logs-for-codespaces.md |   20 +
 .../managing-your-codespaces/index.md         |   20 +
 ...access-and-security-for-your-codespaces.md |   17 +
 ...g-encrypted-secrets-for-your-codespaces.md |   72 +
 ...anaging-gpg-verification-for-codespaces.md |   23 +
 ...ewing-your-security-logs-for-codespaces.md |   21 +
 .../zh-CN/content/codespaces/quickstart.md    |   84 ++
 ...configuring-codespaces-for-your-project.md |  142 ++
 .../setting-up-your-codespace/index.md        |   14 +
 ...rsonalizing-codespaces-for-your-account.md |   71 +
 .../about-wikis.md                            |    6 +
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...nblocking-a-user-from-your-organization.md |    4 +-
 ...-who-are-blocked-from-your-organization.md |    4 +-
 ...iting-interactions-in-your-organization.md |    4 +-
 ...reating-a-default-community-health-file.md |   10 +-
 ...-guidelines-for-repository-contributors.md |    6 +-
 .../content/developers/apps/about-apps.md     |    2 +-
 .../creating-a-github-app-from-a-manifest.md  |    2 +-
 .../creating-ci-tests-with-the-checks-api.md  |  218 ++-
 .../developers/apps/installing-github-apps.md |    2 +-
 .../making-a-github-app-public-or-private.md  |    6 +-
 .../developers/apps/scopes-for-oauth-apps.md  |    2 +-
 ...ment-environment-to-create-a-github-app.md |    4 +-
 .../apps/using-content-attachments.md         |   11 +-
 ...sher-verification-for-your-organization.md |    6 +-
 ...ting-a-listing-description-for-your-app.md |    2 +-
 .../developers/overview/secret-scanning.md    |   90 +-
 .../overview/using-ssh-agent-forwarding.md    |    2 +-
 .../webhooks-and-events/github-event-types.md |    2 +-
 .../webhook-events-and-payloads.md            |   14 +-
 .../participating-in-a-discussion.md          |    2 +-
 .../zh-CN/content/discussions/index.md        |   21 -
 .../create-a-group-assignment.md              |    2 +-
 .../about-protected-branches.md               |   10 +
 .../changing-the-default-branch.md            |    2 +-
 ...g-your-repositorys-social-media-preview.md |    2 +-
 .../deleting-a-repository.md                  |    2 +-
 ...imiting-github-actions-for-a-repository.md |   22 +-
 ...ing-a-sponsor-button-in-your-repository.md |    4 +-
 .../managing-releases-in-a-repository.md      |    2 +-
 ...d-analysis-settings-for-your-repository.md |   13 +-
 ...d-people-with-access-to-your-repository.md |    2 +-
 .../renaming-a-branch.md                      |    8 +
 .../restoring-a-deleted-repository.md         |    4 +-
 .../setting-repository-visibility.md          |    4 +-
 ...deployment-activity-for-your-repository.md |    3 +-
 .../about-anonymized-urls.md                  |   98 ++
 .../about-authentication-to-github.md         |    2 +-
 ...authentication-with-saml-single-sign-on.md |   36 +-
 .../about-commit-signature-verification.md    |   26 +-
 .../authenticating-to-github/about-ssh.md     |   12 +-
 ...ng-a-new-ssh-key-to-your-github-account.md |    9 +
 .../checking-for-existing-gpg-keys.md         |    2 +-
 ...t-and-tag-signature-verification-status.md |   10 +-
 .../creating-a-personal-access-token.md       |   10 +-
 ...cation-statuses-for-all-of-your-commits.md |   36 +
 .../error-unknown-key-type.md                 |   35 +
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  105 +-
 .../github/authenticating-to-github/index.md  |    4 +-
 ...ccount-if-you-lose-your-2fa-credentials.md |    2 +-
 .../recovering-your-ssh-key-passphrase.md     |    2 +-
 .../reviewing-your-security-log.md            |   61 +-
 .../using-ssh-over-the-https-port.md          |    2 +-
 .../working-with-ssh-key-passphrases.md       |    2 +-
 .../about-collaborative-development-models.md |   10 +-
 .../about-status-checks.md                    |   12 +-
 .../automatically-merging-a-pull-request.md   |    2 +-
 .../changing-the-stage-of-a-pull-request.md   |    8 +
 .../checking-out-pull-requests-locally.md     |    8 +
 .../commenting-on-a-pull-request.md           |    2 +-
 .../creating-a-pull-request.md                |    8 +
 ...eleting-branches-within-your-repository.md |    2 +-
 .../getting-started.md                        |   18 +
 .../index.md                                  |    7 +-
 .../merging-a-pull-request.md                 |    8 +
 .../quickstart-for-communicating-on-github.md |  149 +++
 ...sitory-is-deleted-or-changes-visibility.md |    4 +-
 .../about-readmes.md                          |   14 +-
 .../about-repository-visibility.md            |    4 +-
 .../creating-a-repository-from-a-template.md  |    2 +-
 .../creating-a-template-repository.md         |    2 +-
 .../error-repository-not-found.md             |    4 +-
 .../licensing-a-repository.md                 |    4 +-
 .../about-code-scanning.md                    |    3 +-
 .../about-integration-with-code-scanning.md   |    2 +
 ...our-code-for-vulnerabilities-and-errors.md |    1 +
 .../configuring-code-scanning.md              |  259 ++--
 ...-codeql-code-scanning-in-your-ci-system.md |    6 +-
 ...-codeql-workflow-for-compiled-languages.md |    8 +-
 .../index.md                                  |    2 +
 .../integrating-with-code-scanning.md         |    1 +
 ...ode-scanning-alerts-for-your-repository.md |   62 +-
 ...ing-codeql-code-scanning-in-a-container.md |   31 +-
 ...-codeql-code-scanning-in-your-ci-system.md |   14 +-
 .../sarif-support-for-code-scanning.md        |    2 +
 ...tting-up-code-scanning-for-a-repository.md |    8 +-
 ...g-code-scanning-alerts-in-pull-requests.md |   24 +-
 ...-codeql-code-scanning-in-your-ci-system.md |    2 +
 .../troubleshooting-the-codeql-workflow.md    |  152 +--
 .../uploading-a-sarif-file-to-github.md       |   57 +-
 ...e-scanning-with-your-existing-ci-system.md |    1 +
 .../about-git-subtree-merges.md               |    2 +
 .../about-github-advanced-security.md         |    4 +-
 .../getting-started-with-github/be-social.md  |   10 +-
 .../configuring-git-to-handle-line-endings.md |    6 +-
 .../create-a-repo.md                          |    4 +-
 .../fork-a-repo.md                            |    5 +-
 ...etting-changes-from-a-remote-repository.md |    2 +
 .../git-workflows.md                          |    2 +-
 .../github-flow.md                            |   99 ++
 .../github-for-mobile.md                      |    2 +-
 .../github-language-support.md                |   39 +
 .../githubs-products.md                       |   13 +-
 .../getting-started-with-github/index.md      |    3 +-
 .../keyboard-shortcuts.md                     |    6 +-
 .../learning-about-github.md                  |    2 +-
 .../getting-started-with-github/set-up-git.md |    2 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |    6 +-
 .../using-git-rebase-on-the-command-line.md   |    2 +
 .../about-github-importer.md                  |   14 +-
 .../source-code-migration-tools.md            |    9 +-
 translations/zh-CN/content/github/index.md    |    2 -
 .../deleting-files-in-a-repository.md         |    2 +-
 .../navigating-code-on-github.md              |    2 +
 .../conditions-for-large-files.md             |   12 +-
 ...oving-files-from-git-large-file-storage.md |    2 +-
 ...bout-alerts-for-vulnerable-dependencies.md |   84 +-
 ...tifications-for-vulnerable-dependencies.md |    3 +-
 .../index.md                                  |    1 +
 ...abilities-in-your-projects-dependencies.md |    1 +
 .../about-notifications.md                    |   10 +-
 .../configuring-notifications.md              |    2 +-
 .../managing-your-subscriptions.md            |   16 +-
 .../viewing-your-subscriptions.md             |   11 +-
 ...and-pull-requests-with-query-parameters.md |    2 +-
 ...milestones-for-issues-and-pull-requests.md |    2 +-
 ...ing-project-boards-in-your-organization.md |    4 +-
 ...attachments-on-issues-and-pull-requests.md |   22 +-
 .../managing-labels.md                        |    2 +
 .../sorting-issues-and-pull-requests.md       |    4 +-
 ...sferring-an-issue-to-another-repository.md |    2 +-
 .../searching-code.md                         |    3 +-
 .../about-billing-for-github-packages.md      |    6 +-
 .../about-billing-for-github-sponsors.md      |    4 +-
 ...-licensing-for-github-advanced-security.md |   26 +-
 .../adding-information-to-your-receipts.md    |   12 +-
 .../adding-or-editing-a-payment-method.md     |   10 +-
 .../canceling-a-github-marketplace-app.md     |   20 +-
 ...ging-the-duration-of-your-billing-cycle.md |    6 +-
 ...r-an-organization-on-behalf-of-a-client.md |   16 +-
 ...unted-subscriptions-for-github-accounts.md |    4 +-
 .../downgrading-git-large-file-storage.md     |    9 +-
 ...lling-plan-for-a-github-marketplace-app.md |    7 +-
 .../downgrading-your-github-subscription.md   |   26 +-
 ...-your-spending-limit-for-github-actions.md |   17 +-
 ...your-spending-limit-for-github-packages.md |   17 +-
 .../removing-a-payment-method.md              |   11 +-
 ...renewing-your-clients-paid-organization.md |    9 +-
 .../setting-your-billing-email.md             |   17 +-
 .../upgrading-git-large-file-storage.md       |    9 +-
 ...ngrading-your-clients-paid-organization.md |   12 +-
 ...lling-plan-for-a-github-marketplace-app.md |    9 +-
 .../upgrading-your-github-subscription.md     |   25 +-
 ...ng-pending-changes-to-your-subscription.md |    9 +-
 ...ewing-your-git-large-file-storage-usage.md |    9 +-
 .../viewing-your-github-actions-usage.md      |    7 +-
 ...ing-your-github-advanced-security-usage.md |   14 +-
 .../viewing-your-github-packages-usage.md     |    7 +-
 ...ewing-your-payment-history-and-receipts.md |    7 +-
 ...ing-your-subscriptions-and-billing-date.md |    7 +-
 ...analysis-settings-for-your-organization.md |    2 +-
 .../permission-levels-for-an-organization.md  |    2 +-
 ...-a-team-with-an-identity-provider-group.md |   10 +-
 ...n-azure-subscription-to-your-enterprise.md |    2 +-
 ...ons-policies-in-your-enterprise-account.md |   16 +
 .../index.md                                  |    4 +-
 ...tifications-for-your-enterprise-account.md |   23 +
 ...ng-a-domain-for-your-enterprise-account.md |   38 +
 ...-a-users-saml-access-to-your-enterprise.md |    9 +
 .../about-your-organizations-profile.md       |    2 +-
 .../personalizing-your-profile.md             |   92 +-
 .../changing-your-primary-email-address.md    |    2 +-
 .../converting-a-user-into-an-organization.md |    2 +-
 ...fault-branch-name-for-your-repositories.md |    2 +-
 .../managing-your-theme-settings.md           |   13 +-
 ...on-levels-for-a-user-account-repository.md |    4 +-
 ...collaborator-from-a-personal-repository.md |    2 +-
 .../github-corporate-terms-of-service.md      |    2 +
 ...d-data-protection-for-your-organization.md |    3 -
 .../site-policy/github-privacy-statement.md   |    2 +-
 .../github-subprocessors-and-cookies.md       |    2 +-
 .../about-the-dependency-graph.md             |   99 +-
 ...loring-the-dependencies-of-a-repository.md |   68 +-
 ...ium-support-for-github-enterprise-cloud.md |    2 +-
 .../autolinked-references-and-urls.md         |    2 +-
 .../basic-writing-and-formatting-syntax.md    |    6 +-
 .../creating-and-highlighting-code-blocks.md  |    1 +
 .../using-the-graphql-api-for-discussions.md  |    2 +-
 .../graphql/overview/breaking-changes.md      |    2 +-
 .../content/graphql/overview/explorer.md      |    2 +-
 .../graphql/reference/input-objects.md        |    5 +-
 .../metrics-available-with-github-insights.md |    1 -
 ...n-github-enterprise-and-github-insights.md |    1 -
 ...tting-your-timezone-for-github-insights.md |    1 -
 .../viewing-key-metrics-and-reports.md        |    1 -
 .../about-data-in-github-insights.md          |    1 -
 .../about-github-insights.md                  |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 ...n-github-insights-and-github-enterprise.md |    1 -
 .../installing-github-insights.md             |    1 -
 .../managing-available-metrics-and-reports.md |    1 -
 .../managing-contributors-and-teams.md        |    3 +-
 .../managing-events.md                        |    3 +-
 .../managing-goals.md                         |    1 -
 .../managing-organizations.md                 |    1 -
 ...managing-permissions-in-github-insights.md |    1 -
 .../managing-repositories.md                  |    1 -
 .../system-overview-for-github-insights.md    |    1 -
 .../updating-github-insights.md               |    1 -
 .../accessing-your-organizations-settings.md  |    3 +-
 .../about-team-discussions.md                 |    2 +-
 .../keeping-your-organization-secure/index.md |    2 +-
 ...owed-ip-addresses-for-your-organization.md |   12 +-
 ...analysis-settings-for-your-organization.md |   51 +-
 ...tor-authentication-in-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |   46 +
 ...ing-the-audit-log-for-your-organization.md |    4 +-
 ...ur-organizations-installed-integrations.md |    3 +-
 ...ithub-app-managers-in-your-organization.md |    6 +-
 ...hub-app-managers-from-your-organization.md |    6 +-
 ...access-to-an-organization-project-board.md |    2 +-
 ...-collaborator-to-an-organization-member.md |    4 +-
 ...y-permission-levels-for-an-organization.md |   18 +-
 ...ng-base-permissions-for-an-organization.md |    3 +-
 ...ganizations-ssh-certificate-authorities.md |    6 +-
 ...e-to-delete-issues-in-your-organization.md |    3 +-
 ...-your-organizations-dependency-insights.md |    3 +-
 .../deleting-an-organization-account.md       |    3 +-
 ...ng-github-actions-for-your-organization.md |   31 +-
 .../managing-organization-settings/index.md   |    2 +-
 ...s-for-repositories-in-your-organization.md |    9 +-
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...heduled-reminders-for-your-organization.md |    9 +-
 ...e-for-repositories-in-your-organization.md |    3 +-
 ...ay-of-member-names-in-your-organization.md |    3 +-
 ...he-forking-policy-for-your-organization.md |    3 +-
 ...rom-accounts-your-organization-sponsors.md |    7 +-
 .../renaming-an-organization.md               |    7 +-
 ...epository-creation-in-your-organization.md |    3 +-
 ...visibility-changes-in-your-organization.md |    3 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 ...r-deleting-or-transferring-repositories.md |    3 +-
 ...eation-permissions-in-your-organization.md |    3 +-
 ...pproving-a-domain-for-your-organization.md |   82 ++
 ...-a-billing-manager-to-your-organization.md |    7 +-
 ...ership-continuity-for-your-organization.md |    6 +
 .../permission-levels-for-an-organization.md  |   10 +-
 ...-billing-manager-from-your-organization.md |    7 +-
 ...ions-saml-single-sign-on-recovery-codes.md |    3 +-
 ...ml-single-sign-on-for-your-organization.md |    3 +-
 ...m-synchronization-for-your-organization.md |    9 +-
 ...ms-to-improved-organization-permissions.md |    3 +-
 ...-team-discussions-for-your-organization.md |    3 +-
 ...-a-team-with-an-identity-provider-group.md |   20 +-
 ...roving-oauth-apps-for-your-organization.md |    3 +-
 ...pproved-oauth-app-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 ...cess-restrictions-for-your-organization.md |    3 +-
 translations/zh-CN/content/packages/index.md  |    5 +-
 .../about-permissions-for-github-packages.md  |   83 ++
 ...-packages-access-control-and-visibility.md |  135 ++
 .../connecting-a-repository-to-a-package.md   |   76 ++
 .../packages/learn-github-packages/index.md   |   10 +-
 .../installing-a-package.md                   |   32 +
 .../introduction-to-github-packages.md        |  133 ++
 .../publishing-a-package.md                   |    8 +-
 .../learn-github-packages/viewing-packages.md |   56 +
 ...bout-github-packages-and-github-actions.md |   13 +
 ...mple-workflows-for-publishing-a-package.md |   18 +
 .../index.md                                  |   16 +
 ...nstalling-a-package-with-github-actions.md |  455 +++++++
 .../zh-CN/content/packages/quickstart.md      |   15 +-
 ...ner-support-with-the-container-registry.md |   41 +
 .../index.md                                  |   40 +
 ...ainer-registry-from-the-docker-registry.md |  124 ++
 .../working-with-the-apache-maven-registry.md |  192 +++
 .../working-with-the-container-registry.md    |  121 ++
 .../working-with-the-docker-registry.md       |  262 ++++
 .../working-with-the-gradle-registry.md       |  211 +++
 .../working-with-the-npm-registry.md          |  218 +++
 .../working-with-the-nuget-registry.md        |  237 ++++
 .../working-with-the-rubygems-registry.md     |  151 +++
 .../about-custom-domains-and-github-pages.md  |    6 +-
 ...ustom-domain-for-your-github-pages-site.md |   20 +-
 ...shing-source-for-your-github-pages-site.md |    2 +-
 ...reating-a-github-pages-site-with-jekyll.md |    7 +-
 .../getting-started-with-the-rest-api.md      |   14 +-
 .../zh-CN/content/rest/overview/libraries.md  |    2 +-
 .../content/rest/overview/media-types.md      |    6 +-
 .../zh-CN/content/rest/reference/activity.md  |   10 +-
 .../rest/reference/enterprise-admin.md        |   15 +-
 .../zh-CN/content/rest/reference/git.md       |    2 +-
 .../zh-CN/content/rest/reference/markdown.md  |    2 +-
 .../content/rest/reference/migrations.md      |    2 +-
 .../permissions-required-for-github-apps.md   |   13 +
 .../zh-CN/content/rest/reference/repos.md     |    3 +-
 .../about-github-sponsors.md                  |   50 +
 .../index.md                                  |   10 +
 ...art-for-finding-contributors-to-sponsor.md |   51 +
 translations/zh-CN/content/sponsors/guides.md |   18 +
 translations/zh-CN/content/sponsors/index.md  |   35 +
 ...ks-for-events-in-your-sponsored-account.md |   29 +
 ...g-started-with-the-sponsors-graphql-api.md |   14 +
 .../integrating-with-github-sponsors/index.md |    9 +
 ...b-sponsors-for-open-source-contributors.md |   46 +
 .../contacting-your-sponsors.md               |   28 +
 .../disabling-your-github-sponsors-account.md |   24 +
 ...our-profile-details-for-github-sponsors.md |   31 +
 .../index.md                                  |   24 +
 ...aging-your-payouts-from-github-sponsors.md |   25 +
 .../managing-your-sponsorship-goal.md         |   46 +
 .../managing-your-sponsorship-tiers.md        |   48 +
 ...p-github-sponsors-for-your-organization.md |   91 ++
 ...p-github-sponsors-for-your-user-account.md |   84 ++
 .../tax-information-for-github-sponsors.md    |   25 +
 ...publishing-your-github-sponsors-profile.md |   21 +
 .../viewing-your-sponsors-and-sponsorships.md |   36 +
 ...uting-sponsorships-to-your-organization.md |   20 +
 .../index.md                                  |   14 +
 .../managing-your-sponsorship.md              |   41 +
 .../sponsoring-an-open-source-contributor.md  |   66 +
 .../zh-CN/data/glossaries/external.yml        |    6 +-
 .../zh-CN/data/glossaries/internal.yml        |    6 +-
 .../ghes-3.1/graphql_previews.enterprise.yml  |  134 ++
 ...hql_upcoming_changes.public-enterprise.yml |  114 ++
 .../zh-CN/data/learning-tracks/README.md      |   29 +-
 .../zh-CN/data/learning-tracks/actions.yml    |    1 +
 .../zh-CN/data/learning-tracks/admin.yml      |   72 +
 .../zh-CN/data/release-notes/2-21/19.yml      |   18 +
 .../zh-CN/data/release-notes/2-21/20.yml      |   19 +
 .../zh-CN/data/release-notes/2-21/21.yml      |   15 +
 .../zh-CN/data/release-notes/2-22/11.yml      |   19 +
 .../zh-CN/data/release-notes/2-22/12.yml      |   22 +
 .../zh-CN/data/release-notes/2-22/13.yml      |   20 +
 .../zh-CN/data/release-notes/3-0/0.yml        |    1 +
 .../zh-CN/data/release-notes/3-0/1.yml        |    1 +
 .../zh-CN/data/release-notes/3-0/2.yml        |    1 +
 .../zh-CN/data/release-notes/3-0/3.yml        |    1 +
 .../zh-CN/data/release-notes/3-0/4.yml        |    1 +
 .../zh-CN/data/release-notes/3-0/5.yml        |   27 +
 .../zh-CN/data/release-notes/3-0/6.yml        |   30 +
 .../zh-CN/data/release-notes/3-0/7.yml        |   23 +
 .../zh-CN/data/release-notes/3-1/0-rc1.yml    |  130 ++
 .../data/reusables/actions/actions-cli.md     |    1 +
 .../actions/actions-group-concurrency.md      |   25 +
 .../reusables/actions/concurrency-beta.md     |    5 +
 .../enterprise-github-connect-warning.md      |    7 +
 .../actions/enterprise-no-internet-actions.md |    2 +-
 .../data/reusables/actions/forked-secrets.md  |    2 +-
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    1 +
 .../about-ghas-organization-policy.md         |    2 +-
 .../getting-the-most-from-your-license.md     |    6 +
 .../ghas-helps-developers.md                  |    3 +-
 .../managing-license-usage-ghec-ghes.md       |    5 +
 .../deprecating_auth_with_query_parameters.md |    4 +-
 .../reusables/branches/set-default-branch.md  |    2 +-
 .../data/reusables/cli/actions-cli-version.md |    1 +
 .../zh-CN/data/reusables/cli/cli-auth.md      |    1 +
 .../zh-CN/data/reusables/cli/cli-manual.md    |    1 +
 .../zh-CN/data/reusables/cli/cli-repo.md      |    1 +
 .../data/reusables/cli/download-update-cli.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |    7 +
 .../codeql-languages-keywords.md              |    1 +
 .../code-scanning/enabling-options.md         |   21 +-
 .../code-scanning/upload-sarif-alert-limit.md |    2 +-
 .../code-scanning/upload-sarif-ghas.md        |    9 +
 .../code-scanning/what-is-codeql-cli.md       |    3 +
 .../codespaces/about-personalization.md       |    2 +-
 .../codespaces/about-port-forwarding.md       |    1 +
 .../codespaces/apply-devcontainer-changes.md  |    1 +
 .../click-remote-explorer-icon-vscode.md      |    2 +-
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../committing-link-to-procedure.md           |    3 +
 .../codespaces/navigate-to-ports-tab.md       |    1 +
 .../reusables/codespaces/rebuild-command.md   |    1 +
 .../reusables/codespaces/recovery-mode.md     |    1 +
 .../reusables/codespaces/release-stage.md     |    2 +-
 .../reusables/codespaces/secret-precedence.md |    1 +
 .../reusables/codespaces/secrets-naming.md    |    7 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/source-control-display-dark.md |    1 +
 .../codespaces/source-control-display.md      |    3 +
 .../reusables/codespaces/type-port-label.md   |    1 +
 .../you-can-see-all-your-codespaces.md        |    2 +-
 .../your-codespaces-procedure-step.md         |    3 +
 .../dependabot/supported-package-managers.md  |    2 +-
 .../pull_request_forked_repos_link.md         |    4 +
 .../actions-packages-report-download.md       |    2 +-
 .../dotcom_billing/change_plan_duration.md    |    2 +-
 .../dotcom_billing/choose_org_plan.md         |    2 +-
 .../dotcom_billing/enter-payment-info.md      |    2 +-
 .../reusables/dotcom_billing/lfs-add-data.md  |    2 +-
 .../dotcom_billing/manage-spending-limit.md   |    1 +
 .../dotcom_billing/next_billing_date.md       |    2 +-
 .../dotcom_billing/review-pending-changes.md  |    2 +-
 .../dotcom_billing/update_payment_method.md   |    2 +-
 .../reusables/dotcom_billing/upgrade_org.md   |    2 +-
 .../dotcom_billing/view-payment-history.md    |    2 +-
 .../enterprise-accounts/add-a-domain.md       |    1 +
 .../approved-domains-about.md                 |    1 +
 .../approved-domains-beta-note.md             |    9 +
 .../domains-about-approval.md                 |   13 +
 .../domains-about-verification.md             |   11 +
 .../enterprise-accounts/domains-approving.md  |    9 +
 .../enterprise-accounts/domains-removing.md   |    4 +
 .../enterprise-accounts/domains-verifying.md  |   15 +
 .../email-restrictions-about.md               |    9 +
 .../email-restrictions-restricting.md         |    7 +
 .../enterprise-administrators.md              |    2 +-
 .../verified-domains-tab.md                   |    2 +-
 .../deprecation_details.md                    |    2 +-
 .../hardware-considerations-all-platforms.md  |    2 +-
 .../upgrade-hardware-requirements.md          |   25 +
 .../enable-disable-security-features.md       |    2 +-
 .../gated-features/actions-shared.md          |    2 +-
 .../reusables/gated-features/code-scanning.md |    2 +-
 .../data/reusables/gated-features/ghas.md     |    2 +-
 .../gated-features/github-insights.md         |    2 +-
 .../data/reusables/gated-features/packages.md |    4 +-
 .../data/reusables/gated-features/pages.md    |    2 +-
 .../gated-features/secret-scanning.md         |   11 +-
 .../github-actions/forked-write-permission.md |    1 +
 .../github-token-available-permissions.md     |   23 +
 .../github-token-permissions.md               |    1 +
 .../publish-to-packages-workflow-step.md      |    2 +-
 ...ed-runner-configure-runner-group-access.md |    2 +-
 .../supported-github-runners.md               |    8 +-
 .../workflow-permissions-intro.md             |    1 +
 .../workflow-permissions-modifying.md         |    1 +
 .../verification-status-check.md              |    1 +
 .../vigilant-mode-beta-note.md                |    5 +
 .../vigilant-mode-verification-statuses.md    |    5 +
 .../cancel-app-billing-settings.md            |    2 +-
 .../cancel-free-trial-billing-settings.md     |    2 +-
 .../downgrade-app-billing-settings.md         |    2 +-
 .../upgrade-app-billing-settings.md           |    2 +-
 .../custom-notification-types.md              |    2 +
 .../email-restrictions-verification.md        |    1 +
 ...ification-delivery-method-customization.md |   10 +-
 .../reusables/organizations/add-a-domain.md   |    1 +
 .../reusables/organizations/billing_plans.md  |    1 +
 .../continue-verifying-domain.md              |    2 +-
 .../organizations/domains-approve-domain.md   |    1 +
 .../domains-approve-it-instead.md             |    1 +
 .../organizations/verified-domains.md         |    2 +-
 .../about-packaging-and-actions.md            |   30 +
 .../authenticate-packages-github-token.md     |    1 +
 .../package_registry/authenticate-packages.md |   17 +-
 ...uthenticate-to-container-registry-steps.md |    2 +-
 ...nticate_with_pat_for_container_registry.md |    4 +-
 .../container-registry-beta.md                |    2 +-
 .../docker-vs-container-registry.md           |    9 +
 .../docker_registry_deprecation_status.md     |    2 +-
 .../feature-preview-for-container-registry.md |    4 +-
 .../github-token-security-over-pat.md         |    4 +-
 ...coped-and-granular-permissions-packages.md |   12 +
 .../visibility-and-access-permissions.md      |   13 +
 .../reusables/pages/new-or-existing-repo.md   |    2 +-
 .../data/reusables/pages/sidebar-pages.md     |    2 +-
 .../data/reusables/profile/access_org.md      |    2 +-
 .../data/reusables/profile/org_settings.md    |    1 +
 .../user_profile_page_block_or_report.md      |    2 +-
 .../actions-scheduled-workflow-example.md     |    2 +-
 ...forks_from_private_repositories_warning.md |    2 +-
 .../repositories/request-changes-tips.md      |    1 +
 .../repositories/security-guidelines.md       |    4 +-
 .../repositories/sidebar-dependabot-alerts.md |    2 +-
 .../reusables/repositories/you-can-fork.md    |    2 +-
 .../you-must-periodically-authenticate.md     |    2 +-
 .../data/reusables/secret-scanning/beta.md    |    2 +-
 .../partner-secret-list-private-repo.md       |  250 ++--
 .../partner-secret-list-public-repo.md        |  150 ++-
 .../link-browsing-advisory-db.md              |    5 +
 .../security/displayed-information.md         |    4 +-
 .../data/reusables/sponsors/choose-updates.md |    2 +-
 .../data/reusables/sponsors/click-add-tier.md |    2 +-
 .../sponsors/enable-custom-amounts.md         |    4 +-
 .../zh-CN/data/reusables/sponsors/feedback.md |    2 +-
 .../reusables/sponsors/pay-prorated-amount.md |    2 +-
 .../sponsors/prorated-sponsorship.md          |    2 +-
 .../sponsors/review-and-publish-tier.md       |    2 +-
 .../sponsors/review-tiers-to-select.md        |    2 +-
 .../data/reusables/sponsors/select-a-tier.md  |    2 +-
 .../reusables/sponsors/sponsorship-details.md |    2 +-
 .../data/reusables/sponsors/tier-details.md   |    4 +-
 .../data/reusables/supported-languages/C.md   |    1 +
 .../data/reusables/supported-languages/Cpp.md |    1 +
 .../data/reusables/supported-languages/Cs.md  |    1 +
 .../data/reusables/supported-languages/go.md  |    1 +
 .../reusables/supported-languages/java.md     |    1 +
 .../supported-languages/javascript.md         |    1 +
 .../data/reusables/supported-languages/php.md |    1 +
 .../products-table-header.md                  |    2 +
 .../reusables/supported-languages/python.md   |    1 +
 .../reusables/supported-languages/ruby.md     |    1 +
 .../reusables/supported-languages/scala.md    |    1 +
 .../supported-languages/typescript.md         |    1 +
 .../reusables/user_settings/billing_plans.md  |    2 +-
 .../keeping_your_email_address_private.md     |    2 +-
 .../user_settings/payment-info-link.md        |    1 +
 .../reusables/webhooks/create_properties.md   |   12 +-
 .../pull_request_webhook_properties.md        |    6 +-
 .../webhooks/sponsorship_short_desc.md        |    2 +-
 translations/zh-CN/data/ui.yml                |   46 +-
 .../variables/codespaces_code_examples.yml    |   43 +
 .../zh-CN/data/variables/migrations.yml       |    2 +-
 translations/zh-CN/data/variables/product.yml |    5 +-
 .../data/variables/release_candidate.yml      |    2 +-
 .../data/variables/sponsors_user_examples.yml |   20 +
 6208 files changed, 100845 insertions(+), 25077 deletions(-)
 create mode 100644 translations/de-DE/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/de-DE/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/de-DE/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/de-DE/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/de-DE/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/advanced-security/index.md
 create mode 100644 translations/de-DE/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/de-DE/content/admin/all-releases.md
 create mode 100644 translations/de-DE/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/guides.md
 create mode 100644 translations/de-DE/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/de-DE/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/de-DE/content/codespaces/about-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/guides.md
 create mode 100644 translations/de-DE/content/codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/quickstart.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/de-DE/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/de-DE/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/de-DE/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/de-DE/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/de-DE/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/de-DE/content/sponsors/guides.md
 create mode 100644 translations/de-DE/content/sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/de-DE/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/de-DE/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/de-DE/data/learning-tracks/admin.yml
 create mode 100644 translations/de-DE/data/release-notes/2-21/19.yml
 create mode 100644 translations/de-DE/data/release-notes/2-21/20.yml
 create mode 100644 translations/de-DE/data/release-notes/2-21/21.yml
 create mode 100644 translations/de-DE/data/release-notes/2-22/11.yml
 create mode 100644 translations/de-DE/data/release-notes/2-22/12.yml
 create mode 100644 translations/de-DE/data/release-notes/2-22/13.yml
 create mode 100644 translations/de-DE/data/release-notes/3-0/5.yml
 create mode 100644 translations/de-DE/data/release-notes/3-0/6.yml
 create mode 100644 translations/de-DE/data/release-notes/3-0/7.yml
 create mode 100644 translations/de-DE/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/de-DE/data/reusables/actions/actions-cli.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/de-DE/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/de-DE/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-auth.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-manual.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-repo.md
 create mode 100644 translations/de-DE/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/de-DE/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/de-DE/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/de-DE/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/de-DE/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/de-DE/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/de-DE/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/de-DE/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/de-DE/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/de-DE/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/de-DE/data/reusables/profile/org_settings.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/C.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/go.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/java.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/php.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/python.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/scala.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/de-DE/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/de-DE/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/de-DE/data/variables/sponsors_user_examples.yml
 create mode 100644 translations/es-ES/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/es-ES/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/es-ES/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/es-ES/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/es-ES/content/admin/advanced-security/index.md
 create mode 100644 translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/es-ES/content/admin/all-releases.md
 create mode 100644 translations/es-ES/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/es-ES/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/es-ES/content/admin/guides.md
 create mode 100644 translations/es-ES/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/es-ES/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/es-ES/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/es-ES/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/es-ES/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/es-ES/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/es-ES/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/es-ES/content/codespaces/about-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/es-ES/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/es-ES/content/codespaces/guides.md
 create mode 100644 translations/es-ES/content/codespaces/index.md
 create mode 100644 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/es-ES/content/codespaces/quickstart.md
 create mode 100644 translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/es-ES/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/es-ES/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/es-ES/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/es-ES/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/es-ES/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/es-ES/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/es-ES/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/es-ES/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/es-ES/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/es-ES/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/es-ES/content/sponsors/guides.md
 create mode 100644 translations/es-ES/content/sponsors/index.md
 create mode 100644 translations/es-ES/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/es-ES/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/es-ES/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/es-ES/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/es-ES/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/es-ES/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/es-ES/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/es-ES/data/learning-tracks/admin.yml
 create mode 100644 translations/es-ES/data/release-notes/2-21/19.yml
 create mode 100644 translations/es-ES/data/release-notes/2-21/20.yml
 create mode 100644 translations/es-ES/data/release-notes/2-21/21.yml
 create mode 100644 translations/es-ES/data/release-notes/2-22/11.yml
 create mode 100644 translations/es-ES/data/release-notes/2-22/12.yml
 create mode 100644 translations/es-ES/data/release-notes/2-22/13.yml
 create mode 100644 translations/es-ES/data/release-notes/3-0/5.yml
 create mode 100644 translations/es-ES/data/release-notes/3-0/6.yml
 create mode 100644 translations/es-ES/data/release-notes/3-0/7.yml
 create mode 100644 translations/es-ES/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/es-ES/data/reusables/actions/actions-cli.md
 create mode 100644 translations/es-ES/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/es-ES/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/es-ES/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/es-ES/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/es-ES/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/es-ES/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/es-ES/data/reusables/cli/cli-auth.md
 create mode 100644 translations/es-ES/data/reusables/cli/cli-manual.md
 create mode 100644 translations/es-ES/data/reusables/cli/cli-repo.md
 create mode 100644 translations/es-ES/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/es-ES/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/es-ES/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/es-ES/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/es-ES/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/es-ES/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/es-ES/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/es-ES/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/es-ES/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/es-ES/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/es-ES/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/es-ES/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/es-ES/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/es-ES/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/es-ES/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/es-ES/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/es-ES/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/es-ES/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/es-ES/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/es-ES/data/reusables/profile/org_settings.md
 create mode 100644 translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/C.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/go.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/java.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/php.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/python.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/scala.md
 create mode 100644 translations/es-ES/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/es-ES/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/es-ES/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/es-ES/data/variables/sponsors_user_examples.yml
 create mode 100644 translations/ja-JP/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/ja-JP/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/ja-JP/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/ja-JP/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/ja-JP/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/ja-JP/content/admin/advanced-security/index.md
 create mode 100644 translations/ja-JP/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/ja-JP/content/admin/all-releases.md
 create mode 100644 translations/ja-JP/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/ja-JP/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/ja-JP/content/admin/guides.md
 create mode 100644 translations/ja-JP/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/ja-JP/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/ja-JP/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ja-JP/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/ja-JP/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ja-JP/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ja-JP/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/ja-JP/content/codespaces/about-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/ja-JP/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/ja-JP/content/codespaces/guides.md
 create mode 100644 translations/ja-JP/content/codespaces/index.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/ja-JP/content/codespaces/quickstart.md
 create mode 100644 translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/ja-JP/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/ja-JP/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/ja-JP/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/ja-JP/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/ja-JP/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/ja-JP/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/ja-JP/content/sponsors/guides.md
 create mode 100644 translations/ja-JP/content/sponsors/index.md
 create mode 100644 translations/ja-JP/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/ja-JP/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/ja-JP/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/ja-JP/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/ja-JP/data/learning-tracks/admin.yml
 create mode 100644 translations/ja-JP/data/release-notes/2-21/19.yml
 create mode 100644 translations/ja-JP/data/release-notes/2-21/20.yml
 create mode 100644 translations/ja-JP/data/release-notes/2-21/21.yml
 create mode 100644 translations/ja-JP/data/release-notes/2-22/11.yml
 create mode 100644 translations/ja-JP/data/release-notes/2-22/12.yml
 create mode 100644 translations/ja-JP/data/release-notes/2-22/13.yml
 create mode 100644 translations/ja-JP/data/release-notes/3-0/5.yml
 create mode 100644 translations/ja-JP/data/release-notes/3-0/6.yml
 create mode 100644 translations/ja-JP/data/release-notes/3-0/7.yml
 create mode 100644 translations/ja-JP/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/ja-JP/data/reusables/actions/actions-cli.md
 create mode 100644 translations/ja-JP/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/ja-JP/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/ja-JP/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/ja-JP/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/ja-JP/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/ja-JP/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/ja-JP/data/reusables/cli/cli-auth.md
 create mode 100644 translations/ja-JP/data/reusables/cli/cli-manual.md
 create mode 100644 translations/ja-JP/data/reusables/cli/cli-repo.md
 create mode 100644 translations/ja-JP/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/ja-JP/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/ja-JP/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/ja-JP/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/ja-JP/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/ja-JP/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/ja-JP/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/ja-JP/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/ja-JP/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/ja-JP/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/ja-JP/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/ja-JP/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/ja-JP/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/ja-JP/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/ja-JP/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/ja-JP/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/ja-JP/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/ja-JP/data/reusables/profile/org_settings.md
 create mode 100644 translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/C.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/go.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/java.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/php.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/python.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/scala.md
 create mode 100644 translations/ja-JP/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/ja-JP/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/ja-JP/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/ja-JP/data/variables/sponsors_user_examples.yml
 create mode 100644 translations/ko-KR/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/ko-KR/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/ko-KR/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/ko-KR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/ko-KR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/ko-KR/content/admin/advanced-security/index.md
 create mode 100644 translations/ko-KR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/ko-KR/content/admin/all-releases.md
 create mode 100644 translations/ko-KR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/ko-KR/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/ko-KR/content/admin/guides.md
 create mode 100644 translations/ko-KR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/ko-KR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/ko-KR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/ko-KR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ko-KR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/ko-KR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ko-KR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ko-KR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/ko-KR/content/codespaces/about-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/ko-KR/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/ko-KR/content/codespaces/guides.md
 create mode 100644 translations/ko-KR/content/codespaces/index.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/ko-KR/content/codespaces/quickstart.md
 create mode 100644 translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/ko-KR/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/ko-KR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/ko-KR/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/ko-KR/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/ko-KR/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/ko-KR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/ko-KR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/ko-KR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/ko-KR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/ko-KR/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/ko-KR/content/sponsors/guides.md
 create mode 100644 translations/ko-KR/content/sponsors/index.md
 create mode 100644 translations/ko-KR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/ko-KR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/ko-KR/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/ko-KR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/ko-KR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/ko-KR/data/learning-tracks/admin.yml
 create mode 100644 translations/ko-KR/data/release-notes/2-21/19.yml
 create mode 100644 translations/ko-KR/data/release-notes/2-21/20.yml
 create mode 100644 translations/ko-KR/data/release-notes/2-21/21.yml
 create mode 100644 translations/ko-KR/data/release-notes/2-22/11.yml
 create mode 100644 translations/ko-KR/data/release-notes/2-22/12.yml
 create mode 100644 translations/ko-KR/data/release-notes/2-22/13.yml
 create mode 100644 translations/ko-KR/data/release-notes/3-0/5.yml
 create mode 100644 translations/ko-KR/data/release-notes/3-0/6.yml
 create mode 100644 translations/ko-KR/data/release-notes/3-0/7.yml
 create mode 100644 translations/ko-KR/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/ko-KR/data/reusables/actions/actions-cli.md
 create mode 100644 translations/ko-KR/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/ko-KR/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/ko-KR/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/ko-KR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/ko-KR/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/ko-KR/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/ko-KR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/ko-KR/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/ko-KR/data/reusables/cli/cli-auth.md
 create mode 100644 translations/ko-KR/data/reusables/cli/cli-manual.md
 create mode 100644 translations/ko-KR/data/reusables/cli/cli-repo.md
 create mode 100644 translations/ko-KR/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/ko-KR/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/ko-KR/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/ko-KR/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/ko-KR/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/ko-KR/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/ko-KR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/ko-KR/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/ko-KR/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/ko-KR/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/ko-KR/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/ko-KR/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/ko-KR/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/ko-KR/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/ko-KR/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/ko-KR/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/ko-KR/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/ko-KR/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/ko-KR/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/ko-KR/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/ko-KR/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/ko-KR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/ko-KR/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/ko-KR/data/reusables/profile/org_settings.md
 create mode 100644 translations/ko-KR/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/C.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/go.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/java.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/php.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/python.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/scala.md
 create mode 100644 translations/ko-KR/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/ko-KR/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/ko-KR/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/ko-KR/data/variables/sponsors_user_examples.yml
 create mode 100644 translations/pt-BR/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/pt-BR/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/pt-BR/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/pt-BR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/pt-BR/content/admin/advanced-security/index.md
 create mode 100644 translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/pt-BR/content/admin/all-releases.md
 create mode 100644 translations/pt-BR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/pt-BR/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/pt-BR/content/admin/guides.md
 create mode 100644 translations/pt-BR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/pt-BR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/pt-BR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/pt-BR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/pt-BR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/pt-BR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/pt-BR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/pt-BR/content/codespaces/about-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/pt-BR/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/pt-BR/content/codespaces/guides.md
 create mode 100644 translations/pt-BR/content/codespaces/index.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/pt-BR/content/codespaces/quickstart.md
 create mode 100644 translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/pt-BR/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/pt-BR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/pt-BR/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/pt-BR/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/pt-BR/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/pt-BR/content/sponsors/guides.md
 create mode 100644 translations/pt-BR/content/sponsors/index.md
 create mode 100644 translations/pt-BR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/pt-BR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/pt-BR/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/pt-BR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/pt-BR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/pt-BR/data/learning-tracks/admin.yml
 create mode 100644 translations/pt-BR/data/release-notes/2-21/19.yml
 create mode 100644 translations/pt-BR/data/release-notes/2-21/20.yml
 create mode 100644 translations/pt-BR/data/release-notes/2-21/21.yml
 create mode 100644 translations/pt-BR/data/release-notes/2-22/11.yml
 create mode 100644 translations/pt-BR/data/release-notes/2-22/12.yml
 create mode 100644 translations/pt-BR/data/release-notes/2-22/13.yml
 create mode 100644 translations/pt-BR/data/release-notes/3-0/5.yml
 create mode 100644 translations/pt-BR/data/release-notes/3-0/6.yml
 create mode 100644 translations/pt-BR/data/release-notes/3-0/7.yml
 create mode 100644 translations/pt-BR/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/pt-BR/data/reusables/actions/actions-cli.md
 create mode 100644 translations/pt-BR/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/pt-BR/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/pt-BR/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/pt-BR/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/pt-BR/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/pt-BR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/pt-BR/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/pt-BR/data/reusables/cli/cli-auth.md
 create mode 100644 translations/pt-BR/data/reusables/cli/cli-manual.md
 create mode 100644 translations/pt-BR/data/reusables/cli/cli-repo.md
 create mode 100644 translations/pt-BR/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/pt-BR/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/pt-BR/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/pt-BR/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/pt-BR/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/pt-BR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/pt-BR/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/pt-BR/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/pt-BR/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/pt-BR/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/pt-BR/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/pt-BR/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/pt-BR/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/pt-BR/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/pt-BR/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/pt-BR/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/pt-BR/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/pt-BR/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/pt-BR/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/pt-BR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/pt-BR/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/pt-BR/data/reusables/profile/org_settings.md
 create mode 100644 translations/pt-BR/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/C.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/go.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/java.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/php.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/python.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/scala.md
 create mode 100644 translations/pt-BR/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/pt-BR/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/pt-BR/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/pt-BR/data/variables/sponsors_user_examples.yml
 create mode 100644 translations/ru-RU/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/ru-RU/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/ru-RU/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/ru-RU/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/ru-RU/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/ru-RU/content/admin/advanced-security/index.md
 create mode 100644 translations/ru-RU/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/ru-RU/content/admin/all-releases.md
 create mode 100644 translations/ru-RU/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/ru-RU/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/ru-RU/content/admin/guides.md
 create mode 100644 translations/ru-RU/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/ru-RU/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/ru-RU/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/ru-RU/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ru-RU/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/ru-RU/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ru-RU/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/ru-RU/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/ru-RU/content/codespaces/about-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/ru-RU/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/ru-RU/content/codespaces/guides.md
 create mode 100644 translations/ru-RU/content/codespaces/index.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/ru-RU/content/codespaces/quickstart.md
 create mode 100644 translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/ru-RU/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/ru-RU/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/ru-RU/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/ru-RU/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/ru-RU/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/ru-RU/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/ru-RU/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/ru-RU/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/ru-RU/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/ru-RU/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/ru-RU/content/sponsors/guides.md
 create mode 100644 translations/ru-RU/content/sponsors/index.md
 create mode 100644 translations/ru-RU/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/ru-RU/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/ru-RU/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/ru-RU/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/ru-RU/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/ru-RU/data/learning-tracks/admin.yml
 create mode 100644 translations/ru-RU/data/release-notes/2-21/19.yml
 create mode 100644 translations/ru-RU/data/release-notes/2-21/20.yml
 create mode 100644 translations/ru-RU/data/release-notes/2-21/21.yml
 create mode 100644 translations/ru-RU/data/release-notes/2-22/11.yml
 create mode 100644 translations/ru-RU/data/release-notes/2-22/12.yml
 create mode 100644 translations/ru-RU/data/release-notes/2-22/13.yml
 create mode 100644 translations/ru-RU/data/release-notes/3-0/5.yml
 create mode 100644 translations/ru-RU/data/release-notes/3-0/6.yml
 create mode 100644 translations/ru-RU/data/release-notes/3-0/7.yml
 create mode 100644 translations/ru-RU/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/ru-RU/data/reusables/actions/actions-cli.md
 create mode 100644 translations/ru-RU/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/ru-RU/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/ru-RU/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/ru-RU/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/ru-RU/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/ru-RU/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/ru-RU/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/ru-RU/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/ru-RU/data/reusables/cli/cli-auth.md
 create mode 100644 translations/ru-RU/data/reusables/cli/cli-manual.md
 create mode 100644 translations/ru-RU/data/reusables/cli/cli-repo.md
 create mode 100644 translations/ru-RU/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/ru-RU/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/ru-RU/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/ru-RU/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/ru-RU/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/ru-RU/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/ru-RU/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/ru-RU/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/ru-RU/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/ru-RU/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/ru-RU/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/ru-RU/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/ru-RU/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/ru-RU/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/ru-RU/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/ru-RU/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/ru-RU/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/ru-RU/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/ru-RU/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/ru-RU/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/ru-RU/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/ru-RU/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/ru-RU/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/ru-RU/data/reusables/profile/org_settings.md
 create mode 100644 translations/ru-RU/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/C.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/go.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/java.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/php.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/python.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/scala.md
 create mode 100644 translations/ru-RU/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/ru-RU/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/ru-RU/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/ru-RU/data/variables/sponsors_user_examples.yml
 create mode 100644 translations/zh-CN/content/actions/guides/building-and-testing-swift.md
 create mode 100644 translations/zh-CN/content/actions/guides/building-and-testing-xamarin-applications.md
 create mode 100644 translations/zh-CN/content/actions/guides/managing-github-actions-with-github-cli.md
 create mode 100644 translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/zh-CN/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
 create mode 100644 translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/zh-CN/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/advanced-security/index.md
 create mode 100644 translations/zh-CN/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/zh-CN/content/admin/all-releases.md
 create mode 100644 translations/zh-CN/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/github-actions/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/guides.md
 create mode 100644 translations/zh-CN/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/zh-CN/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/zh-CN/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/zh-CN/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/zh-CN/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/zh-CN/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/zh-CN/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
 create mode 100644 translations/zh-CN/content/codespaces/about-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/zh-CN/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
 create mode 100644 translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
 create mode 100644 translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md
 create mode 100644 translations/zh-CN/content/codespaces/guides.md
 create mode 100644 translations/zh-CN/content/codespaces/index.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
 create mode 100644 translations/zh-CN/content/codespaces/quickstart.md
 create mode 100644 translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
 create mode 100644 translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md
 create mode 100644 translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
 create mode 100644 translations/zh-CN/content/github/authenticating-to-github/about-anonymized-urls.md
 create mode 100644 translations/zh-CN/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/zh-CN/content/github/authenticating-to-github/error-unknown-key-type.md
 create mode 100644 translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
 create mode 100644 translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
 create mode 100644 translations/zh-CN/content/github/getting-started-with-github/github-flow.md
 create mode 100644 translations/zh-CN/content/github/getting-started-with-github/github-language-support.md
 create mode 100644 translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
 create mode 100644 translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
 create mode 100644 translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/zh-CN/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/zh-CN/content/sponsors/guides.md
 create mode 100644 translations/zh-CN/content/sponsors/index.md
 create mode 100644 translations/zh-CN/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/zh-CN/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/zh-CN/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
 create mode 100644 translations/zh-CN/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
 create mode 100644 translations/zh-CN/data/learning-tracks/admin.yml
 create mode 100644 translations/zh-CN/data/release-notes/2-21/19.yml
 create mode 100644 translations/zh-CN/data/release-notes/2-21/20.yml
 create mode 100644 translations/zh-CN/data/release-notes/2-21/21.yml
 create mode 100644 translations/zh-CN/data/release-notes/2-22/11.yml
 create mode 100644 translations/zh-CN/data/release-notes/2-22/12.yml
 create mode 100644 translations/zh-CN/data/release-notes/2-22/13.yml
 create mode 100644 translations/zh-CN/data/release-notes/3-0/5.yml
 create mode 100644 translations/zh-CN/data/release-notes/3-0/6.yml
 create mode 100644 translations/zh-CN/data/release-notes/3-0/7.yml
 create mode 100644 translations/zh-CN/data/release-notes/3-1/0-rc1.yml
 create mode 100644 translations/zh-CN/data/reusables/actions/actions-cli.md
 create mode 100644 translations/zh-CN/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/zh-CN/data/reusables/actions/concurrency-beta.md
 create mode 100644 translations/zh-CN/data/reusables/actions/enterprise-github-connect-warning.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/zh-CN/data/reusables/cli/actions-cli-version.md
 create mode 100644 translations/zh-CN/data/reusables/cli/cli-auth.md
 create mode 100644 translations/zh-CN/data/reusables/cli/cli-manual.md
 create mode 100644 translations/zh-CN/data/reusables/cli/cli-repo.md
 create mode 100644 translations/zh-CN/data/reusables/cli/download-update-cli.md
 create mode 100644 translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/zh-CN/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/domains-about-approval.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/domains-about-verification.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/domains-approving.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/domains-removing.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/domains-verifying.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-about.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-restricting.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
 create mode 100644 translations/zh-CN/data/reusables/github-actions/forked-write-permission.md
 create mode 100644 translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
 create mode 100644 translations/zh-CN/data/reusables/github-actions/github-token-permissions.md
 create mode 100644 translations/zh-CN/data/reusables/github-actions/workflow-permissions-intro.md
 create mode 100644 translations/zh-CN/data/reusables/github-actions/workflow-permissions-modifying.md
 create mode 100644 translations/zh-CN/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/zh-CN/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/zh-CN/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/zh-CN/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/zh-CN/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/zh-CN/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/zh-CN/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/zh-CN/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/zh-CN/data/reusables/package_registry/docker-vs-container-registry.md
 create mode 100644 translations/zh-CN/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
 create mode 100644 translations/zh-CN/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/zh-CN/data/reusables/profile/org_settings.md
 create mode 100644 translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/C.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/go.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/java.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/php.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/python.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/scala.md
 create mode 100644 translations/zh-CN/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/zh-CN/data/reusables/user_settings/payment-info-link.md
 create mode 100644 translations/zh-CN/data/variables/codespaces_code_examples.yml
 create mode 100644 translations/zh-CN/data/variables/sponsors_user_examples.yml

diff --git a/tests/meta/repository-references.js b/tests/meta/repository-references.js
index f1d58cc36e..9ac6b87558 100644
--- a/tests/meta/repository-references.js
+++ b/tests/meta/repository-references.js
@@ -50,6 +50,7 @@ describe('check for repository references', () => {
       '.git',
       '.github/actions-scripts/enterprise-server-issue-templates/*.md',
       '.github/review-template.md',
+      '.next',
       'dist',
       'node_modules',
       'translations',
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index 18f2ea0eb3..b16f59184d 100644
--- a/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md
index a8d238ab1f..8129eaf6d8 100644
--- a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Verwenden Sie die Ausgabe aus dem „hello“-Schritt.
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
index c425abfea6..ced53e8f98 100644
--- a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
@@ -215,21 +215,21 @@ Der folgende Workflow-Code verwendet die vervollständigte Aktion „hello world
 {% raw %}
 **.github/workflows/main.yml**
 ```yaml
-zu: [push]
+on: [push]
 
-Jobs:
+jobs:
   hello_world_job:
-    läuft auf: ubuntu-latest
-    Name: Ein Job, um Hallo zu sagen
-    Schritte:
-    - Name: Hallo Welt Aktion Schritt
-      ID: hallo
-      verwendet: aktionen/hello-world-javascript-action@v1.1
-      mit:
-        who-to-greet: 'Mona the Octocat'
-    ' Use the output from the 'hello' step
-    - name: Get the output time{{ steps.hello.outputs.time }}
-
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 0b2206ca3b..a206166a5b 100644
--- a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -171,7 +171,7 @@ In diesem Beispiel läuft `cleanup.js` nur auf Linux-basierten Runnern:
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 #### `Beitrag`
@@ -197,7 +197,7 @@ In diesem Beispiel läuft `cleanup.js` nur auf Linux-basierten Runnern:
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 ### `runs` for composite run steps actions
@@ -295,7 +295,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
@@ -323,7 +323,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/de-DE/content/actions/guides/about-continuous-integration.md b/translations/de-DE/content/actions/guides/about-continuous-integration.md
index 6dee241e2e..6e6c233387 100644
--- a/translations/de-DE/content/actions/guides/about-continuous-integration.md
+++ b/translations/de-DE/content/actions/guides/about-continuous-integration.md
@@ -19,6 +19,7 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### Informationen zur fortlaufenden Integration
 
@@ -30,7 +31,9 @@ Zum Erstellen und Testen des Codes ist ein Server erforderlich. Sie können Aktu
 
 ### Informationen zur kontinuierlichen Integration mit {% data variables.product.prodname_actions %}
 
-CI mit {% data variables.product.prodname_actions %} bietet Workflows, die den Code in Ihrem Repository erstellen und Ihre Tests ausführen können. Workflows können auf {% data variables.product.prodname_dotcom %}gehosteten virtuellen Maschinen oder auf Computern ausgeführt werden, die Sie selbst hosten. For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+{% if currentVersion == "github-ae@latest" %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on virtual machines hosted by {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)."
+{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows können auf {% data variables.product.prodname_dotcom %}gehosteten virtuellen Maschinen oder auf Computern ausgeführt werden, die Sie selbst hosten. For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+{% endif %}
 
 Sie können Ihren CI-Workflow so konfigurieren, dass er ausgeführt wird, wenn ein {% data variables.product.product_name %} Ereignis auftritt (z. B. wenn neuer Code an Ihr Repository übertragen wird), nach einem festgelegten Zeitplan oder wenn ein externes Ereignis mithilfe des Repository-Dispatch-Webhooks auftritt.
 
@@ -45,11 +48,34 @@ Sie können nicht nur ci-Workflows für Ihr Projekt einrichten, sondern auch {%
 Eine Definition von gebräuchliche Begriffe finden Sie unter "[Kernkonzepte für {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)".
 
 ### Unterstützte Sprachen
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} bietet CI-Workflowvorlagen für eine Vielzahl von Sprachen und Frameworks.
 
 Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### Skipping workflow runs
+
+If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any any of the following strings to the commit message in a push, or the HEAD commit of a pull request:
+
+* `[skip ci]`
+* `[ci skip]`
+* `[no ci]`
+* `[skip actions]`
+* `[actions skip]`
+
+Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`.
+
+You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message.
+
+{% note %}
+
+**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running.
+
+{% endnote %}
+{% endif %}
+
 ### Benachrichtigungen für Workflow-Läufe
 
 {% data reusables.repositories.workflow-notifications %}
diff --git a/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md b/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md
index 7336fbaa69..603b968704 100644
--- a/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/de-DE/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,38 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### Informationen zu Paketierungsschritten
-
-Die Paket-Erstellung ist ein üblicher Bestandteil des Workflows bei der kontinuierlichen Integration oder bei der kontinuierlichen Auslieferung. Nach dem Erstellen und Testen der Anwendung wird ein lauf- oder bereitstellungsfähiges Artefakt als Paket erstellt. Beispielsweise kann ein Workflow zur kontinuierlichen Integration für ein Java-Projekt `mvn package` ausführen, um eine JAR-Datei zu erstellen. Oder ein CI-Workflow für eine Node.js-Anwendung kann einen Docker-Container erzeugen.
-
-Je nach Art der Anwendung, die Du erstellst, kann dieses Paket für manuelle Tests lokal heruntergeladen, Benutzern zum Herunterladen zur Verfügung gestellt oder in einer Staging- oder Produktionsumgebung bereitgestellt werden.
-
-### Paket-Erstellung in Workflows zur kontinuierlichen Integration
-
-Das Erstellen eines Pakets am Ende eines Workflows zur kontinuierlichen Integration kann während des Code-Reviews bei einem Pull-Request hilfreich sein. Nach dem Erstellen und Testen Deines Codes kann ein Paketierungsschritt ein lauf- oder bereitstellungsfähiges Artefakt erzeugen. Dein Workflow kann dieses Artefakt dann übernehmen und als Teil des Workflows hochladen.
-
-Wenn Du nun einen Pull-Request überprüfst, kannst Du Dir den Ablauf des Workflows ansehen und das erzeugte Artefakt herunterladen.
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-Dadurch kannst Du den Code im Pull-Request auf Deinem Rechner ausführen, was beim Debuggen oder Testen des Pull-Requests helfen kann.
-
-### Workflows zum Veröffentlichen von Paketen
-
-Außer Paket-Artefakte zum Testen in einem Workflow zur kontinuierlichen Integration zum Testen hochzuladen, kannst Du auch Workflows erstellen, die Dein Projekt bauen und Pakete in einer Paket-Registry veröffentlichen.
-
-* **Publish packages to {% data variables.product.prodname_registry %}**
-  {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. Du kannst Deine Pakete entweder mit allen {% data variables.product.prodname_dotcom %} oder private Pakete nur mit Mitarbeitern oder einer Organisation teilen. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)“.
-
-  You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. Auf diese Weise können Entwickler in Deinem Projekt immer den neuesten Build aus Master ausführen und testen, indem sie ihn von {% data variables.product.prodname_registry %} installieren.
-
-* **Pakete in einer Paket-Registry veröffentlichen** Bei vielen Projekten werden neue Versionen immer in einer Paket-Registry veröffentlicht. Beispielsweise kann ein Projekt, das eine JAR-Datei erstellt, neue Versionen in das Zentral-Repository von Maven hochladen. Oder ein .NET-Projekt kann ein NuGet-Paket erzeugen und es in die NuGet-Galerie hochladen.
-
-  Du kannst dies automatisieren, indem Du einen Workflow erstellst, der bei jeder Release-Erstellung Pakete in einer Paket-Registry veröffentlicht. Weitere Informationen findest Du unter „[Releases erstellen](/github/administering-a-repository/creating-releases)“.
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/actions/guides/adding-labels-to-issues.md b/translations/de-DE/content/actions/guides/adding-labels-to-issues.md
index 2b8e074a18..d627fcaebf 100644
--- a/translations/de-DE/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/de-DE/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,14 +38,17 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `add-labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
 5. {% data reusables.actions.commit-workflow %}
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-net.md b/translations/de-DE/content/actions/guides/building-and-testing-net.md
index a730c9395a..568fa7a18e 100644
--- a/translations/de-DE/content/actions/guides/building-and-testing-net.md
+++ b/translations/de-DE/content/actions/guides/building-and-testing-net.md
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,7 +139,7 @@ Weitere Informationen findest Du unter „[Abhängigkeiten zur Beschleunigung vo
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
@@ -171,7 +171,7 @@ Du kannst die gleichen Befehle verwenden, die Du auch lokal verwendest, um Deine
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`.
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md
index 994c0f6d83..bf67e877af 100644
--- a/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ Wir empfehlen, dass Du ein grundlegendes Verständnis von Node.js, YAML, Workflo
 
 {% data variables.product.prodname_dotcom %} bietet eine Node.js-Workflow-Vorlage, die für die meisten Node.js-basierten Projekte funktionieren wird. Diese Anleitung enthält npm und Yarn Beispiele, mit denen Du die Vorlage anpassen kannst. Weitere Informationen findest Du in der [Node.js-Workflow-Vorlage](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein.
+Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,14 +119,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 If you don't specify a Node.js version,
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md
index a1529e3cc8..3b4565a412 100644
--- a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1`
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-python.md b/translations/de-DE/content/actions/guides/building-and-testing-python.md
index 13b0a6c38e..c09db16412 100644
--- a/translations/de-DE/content/actions/guides/building-and-testing-python.md
+++ b/translations/de-DE/content/actions/guides/building-and-testing-python.md
@@ -39,7 +39,7 @@ Du solltest ein grundlegendes Verständnis von Python, PyPy und pip haben. Weite
 
 ### Einstieg mit der Python-Workflow-Vorlage
 
-{% data variables.product.prodname_dotcom %} bietet eine Python-Workflow-Vorlage, die für die meisten Python-Projekte funktionieren sollte. Diese Anleitung enthält Beispiele, mit denen Du die Vorlage anpassen kannst. For more information, see the [Python workflow template](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
+{% data variables.product.prodname_dotcom %} bietet eine Python-Workflow-Vorlage, die für die meisten Python-Projekte funktionieren sollte. Diese Anleitung enthält Beispiele, mit denen Du die Vorlage anpassen kannst. Weitere Informationen findest Du in der [Python-Workflow-Vorlage](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
 
 Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein.
 
@@ -58,25 +58,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Lint with flake8
-      run: |
-        # stop the build if there are Python syntax errors or undefined names
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zero behandelt alle Fehler als Warnungen. Der GitHub-Editor ist 127 Zeichen breit
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - name: Test with pytest
-      run: |
-        pytest
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -117,14 +117,14 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Du kannst Deine Matrix durch Ausgabe der aktuellen Python-Version testen
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -144,17 +144,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # Semantic version range syntax or exact version of a Python version
-        python-version: '3.x'
-        # Optional - x64 or x86 architecture, defaults to x64
-        architecture: 'x64'
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -373,25 +373,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Install pip and pytest
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # Use always() to always run this step to publish test results when there are test failures
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -413,22 +413,22 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 {% endraw %}
 
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md
index cf6ad1d9a3..b858e641f4 100644
--- a/translations/de-DE/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/de-DE/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ We recommend that you have a basic understanding of Ruby, YAML, workflow configu
 
 {% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein.
+Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,7 +264,6 @@ You can configure your workflow to publish your Ruby package to any package regi
 
 You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`.
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
@@ -272,46 +271,48 @@ name: Ruby Gem
 on:
   # Manually publish
   workflow_dispatch:
-  # Alternatively, publish whenever changes are merged to the default branch.
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-swift.md b/translations/de-DE/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..4c039bb7e2
--- /dev/null
+++ b/translations/de-DE/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Building and testing Swift
+intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Einführung
+
+This guide shows you how to build and test a Swift package.
+
+{% if currentVersion == "github-ae@latest" %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
+{% else %}{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swift packages. For a full list of up-to-date software and the preinstalled versions of Swift and Xcode, see "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### Vorrausetzungen
+
+You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)“.
+
+We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
+
+### Starting with the Swift workflow template
+
+{% data variables.product.prodname_dotcom %} provides a Swift workflow template that should work for most Swift projects, and this guide includes examples that show you how to customize this template. For more information, see the [Swift workflow template](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Specifying a Swift version
+
+To use a specific preinstalled version of Swift on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `fwal/setup-swift` action. This action finds a specific version of Swift from the tools cache on the runner and adds the necessary binaries to `PATH`. These changes will persist for the remainder of a job. For more information, see the [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) action.
+
+If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+
+The examples below demonstrate using the `fwal/setup-swift` action.
+
+#### Using multiple Swift versions
+
+You can configure your job to use a multiple versions of Swift in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Using a single specific Swift version
+
+You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### Deinen Code bauen und testen
+
+You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/de-DE/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/de-DE/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..90f5355c48
--- /dev/null
+++ b/translations/de-DE/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Building and testing Xamarin applications
+intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Xamarin application.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Einführung
+
+This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. Der Workflow, den Du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass Dein Code immer brauchbar ist.
+
+{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### Vorrausetzungen
+
+We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML, workflow configuration options, and how to create a workflow file. Weitere Informationen findest Du unter:
+
+- „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)“
+- "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
+- "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Bulding Xamarin.iOS apps
+
+The example below demonstrates how to change the default Xamarin bundle and build  a Xamarin.iOS application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Bulding Xamarin.Android apps
+
+The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### Specifying a .NET version
+
+To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job.
+
+The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action.
diff --git a/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index b69dc2e9d5..831795f649 100644
--- a/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/de-DE/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ Weitere Informationen findest Du unter [`Aktionen/Cache`](https://github.com/act
 
 - `key`: **Erforderlich** Der Schlüssel, der beim Speichern eines Caches erstellt wurde, und der Schlüssel, der zum Suchen nach einem Cache verwendet wird. Kann eine beliebige Kombination von Variablen, Kontextwerten, statischen Strings und Funktionen sein. Schlüssel haben eine maximale Länge von 512 Zeichen und Schlüssel, die die maximale Länge überschreiten, lassen die Aktion fehlschlagen.
 - `path`: **Erforderlich** Der Dateipfad auf dem Runner zum Anlegen oder Wiederherstellen des Caches. Der Pfad kann ein absoluter Pfad oder relativ zum Arbeitsverzeichnis sein.
-  - Mit `v2-` der `-Cache-` -Aktion können Sie einen einzelnen Pfad oder mehrere Pfade als Liste angeben. Pfade können entweder Verzeichnisse oder einzelne Dateien sein, und Glob-Muster werden unterstützt.
+  - Pfade können entweder Verzeichnisse oder einzelne Dateien sein, und Glob-Muster werden unterstützt.
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. Ein Beispiel:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - Bei `v1-` der `-Cache-` -Aktion wird nur ein einzelner Pfad unterstützt, und es muss sich um ein Verzeichnis handeln. Eine einzelne Datei kannst Du nicht cachen.
 - `restore-keys`: **Optional** Eine geordnete Liste der alternativen Schlüssel, die zum Finden des Caches verwendet werden sollen, falls `key` keinen Treffer gebracht hat.
 
@@ -73,7 +82,7 @@ Dieses Beispiel erzeugt einen neuen Cache, wenn sich die Pakete in `package-lock
 
 {% raw %}
 ```yaml{:copy}
-name: Caching mit npm
+name: Caching with npm
 
 on: push
 
@@ -81,31 +90,30 @@ jobs:
   build:
     runs-on: ubuntu-latest
 
-    schritte:
-    - verwendet: actions/checkout@v2
+    steps:
+      - uses: actions/checkout@v2
 
-    - name: Cache node modules
-      uses: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        -npm-Cache-Dateien werden in ''/.npm' auf dem Linux/macOS-
-        -Pfad gespeichert: '/.npm
-        -Schlüssel: '{{ runner.os }}-build-'{{ env.cache-name }}-' hashFiles('**/package-lock.json') '
-        Restore-Keys: |
-          -{{ runner.os }}-build--{{ env.cache-name }}-
-          -{{ runner.os }}-build-
-          -{{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - Name: Installieren sie abhängigkeiten
-      ausführen: npm install
+      - name: Install Dependencies
+        run: npm install
 
-    - Name: Build
-      ausführen: npm build
-
-    - Name: Test
-      -Test: npm-Test
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/de-DE/content/actions/guides/closing-inactive-issues.md b/translations/de-DE/content/actions/guides/closing-inactive-issues.md
index 96c076ea90..500c5edd28 100644
--- a/translations/de-DE/content/actions/guides/closing-inactive-issues.md
+++ b/translations/de-DE/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,9 +51,9 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every day at 1:30 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `days-before-issue-stale` to the number of days without activity before the `actions/stale` action labels an issue. If you never want this action to label issues, set this value to `-1`.
diff --git a/translations/de-DE/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/de-DE/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index 1c05edfd73..e76e9d7690 100644
--- a/translations/de-DE/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/de-DE/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **Make sure to reference this issue in your pull request.** :sparkles: Thank you for your contribution! :sparkles:
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Replace `help-wanted` in `if: github.event.label.name == 'help-wanted'` with the label that you want to act on. If you want to act on more than one label, separate the conditions with `||`. For example, `if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` will comment whenever the `bug` or `fix me` labels are added to an issue.
    - Change the value for `body` to the comment that you want to add. GitHub flavored markdown is supported. For more information about markdown, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
diff --git a/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md b/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md
index c5c98771fe..8d23e8e06b 100644
--- a/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/de-DE/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### Einführung
 
-Diese Anleitung zeigt Dir Workflow-Beispiele, die einen Service-Container mit dem `postgres`-Bild vom Docker-Hub konfigurieren. Der Workflow führt ein Skript aus, um einen PostgreSQL-Client zu erstellen und den Client mit Daten zu füllen. Um zu testen, ob der Workflow den PostgreSQL-Client erstellt und mit Daten füllt, gibt das Skript die Daten des Clients in der Konsole aus.
+Diese Anleitung zeigt Dir Workflow-Beispiele, die einen Service-Container mit dem `postgres`-Bild vom Docker-Hub konfigurieren. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -47,23 +47,23 @@ name: PostgreSQL service example
 on: push
 
 jobs:
-  # Label des Container-Jobs
+  # Label of the container job
   container-job:
-    # Container muessen auf Linux-basierten Betriebssystemen laufen
+    # Containers must run in Linux based operating systems
     runs-on: ubuntu-latest
-    # Docker-Hub-Image, welches `container-job` in
-    container: node:10.18-jessie ausfuehrt
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
 
-    # Service-Containers, der mit Diensten von `container-job`
-    laufen soll:
-      # Label fuer den Zugrieff auf den Service-Container
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
       postgres:
-        # Docker-Hub-Image
+        # Docker Hub image
         image: postgres
-        # Das Passwort fuer Postgres bereitstellen
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # health checks (Gesundheitstests) so einstellen, dass sie warten, bis Postgres gestarted ist
+        # Set health checks to wait until postgres has started
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
@@ -71,20 +71,20 @@ jobs:
           --health-retries 5
 
     steps:
-      # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI-Tests starten
+      # Downloads a copy of the code in your repository before running CI tests
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Fuehrt eine saubere Installation aller Abhaengigkeiten in der Datei `package.json` durch
-      # Weitere Information findest Du unter https://docs.npmjs.com/cli/ci.html
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Startet ein Skript, das einen PostgreSQL-Client erzeugt, 
-        # Den Client mit Daten befuellt, und Daten abruft
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
         run: node client.js
-        # Umgebungsvariable, die vom Skript `client.js` benutzt wird, um einen neuen PostgreSQL-Client zu erzeugen.
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # Der Name des Hosts fuer die Kommunikation mit dem PostgreSQL-Servicecontainer
           POSTGRES_HOST: postgres
@@ -131,18 +131,18 @@ jobs:
 
 ```yaml{:copy}
 steps:
-  # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI-Tests starten
+  # Downloads a copy of the code in your repository before running CI tests
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Fuehrt eine saubere Installation aller Anhängigkeiten in der Datei `package.json` durch
-  # Weitere Informationen findest Du unter https://docs.npmjs.com/cli/ci.html
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Startet ein Skript, das einen PostgreSQL-Client erzeugt,
-    # den Client mit Daten befuellt und Daten abruft
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
     run: node client.js
     # Environment variable used by the `client.js` script to create
     # a new PostgreSQL client.
@@ -169,21 +169,21 @@ name: PostgreSQL Service Example
 on: push
 
 jobs:
-  # Label des Runner-Jobs
+  # Label of the runner job
   runner-job:
-    # Du musst fuer Service-Container oder Container-Jobs eine Linux-Umgebung verwenden
+    # You must use a Linux environment when using service containers or container jobs
     runs-on: ubuntu-latest
 
-    # Service-Container zum Betrieb mit `runner-job`
+    # Service containers to run with `runner-job`
     services:
-      # Label fuer den Zugriff auf den Service-Container
+      # Label used to access the service container
       postgres:
-        # Docker-Hub-Image
+        # Docker Hub image
         image: postgres
-        # Das Passwort fuer Postgres bereitstellen
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # Health checks einstellen, dass sie warten, bis Postgres gestarted ist
+        # Set health checks to wait until postgres has started
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
@@ -194,21 +194,21 @@ jobs:
           - 5432:5432
 
     steps:
-      # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI tests laufen
+      # Downloads a copy of the code in your repository before running CI tests
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Fuehrt eine saubere Installation aller Abhaengigkeiten in der Datei `package.json` durch
-      # Weitere Information finsest Du unter https://docs.npmjs.com/cli/ci.html
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Startet ein Skript, das einen PostgreSQL-Client erzeugt,
-        # den client mit Daten befuellt und Daten abruft
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
         run: node client.js
-        # Umgebungsvariable, die das Skript `client.js` benutzt, um
-        # einen neuen PostgreSQL-Client zu erzeugen.
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # Der Hostname fuer die Kommunikation mit dem PostgreSQL-Service-Container
           POSTGRES_HOST: localhost
@@ -258,21 +258,21 @@ jobs:
 
 ```yaml{:copy}
 steps:
-  # Laedt eine Kopie des Codes in Dein Repository herunter, bevor CI-Tests starten
+  # Downloads a copy of the code in your repository before running CI tests
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Fuehrt eine saubere Installation aller Anhängigkeiten in der Datei `package.json` durch
-  # Weitere Informationen findest Du unter https://docs.npmjs.com/cli/ci.html
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Startet ein Skript, das einen PostgreSQL-Client erzeugt,
-    # den Client mit Daten befuellt und Daten abruft
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new PostgreSQL client.
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # Der Hostname zur Kommunikation with the PostgreSQL-Service-Container
       POSTGRES_HOST: localhost
@@ -286,9 +286,9 @@ steps:
 
 ### Den PostgreSQL-Service-Container testen
 
-Du kannst Deinen Workflow mit dem folgenden Skript testen, das einen PostgreSQL-Client erstellt und eine neue Tabelle mit Platzhalter-Daten hinzufügt. Das Skript gibt dann die im PostgreSQL-Client gespeicherten Werte auf dem Terminal aus. Dein Skript kann jede beliebige Sprache verwenden, aber in diesem Beispiel wird Node.js mit dem npm-Modul `pg` genutzt. Weitere Informationen findest Du unter [npm-Modul pg](https://www.npmjs.com/package/pg).
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. Dein Skript kann jede beliebige Sprache verwenden, aber in diesem Beispiel wird Node.js mit dem npm-Modul `pg` genutzt. Weitere Informationen findest Du unter [npm-Modul pg](https://www.npmjs.com/package/pg).
 
-Du kannst *client.js* anpassen, um alle PostgreSQL-Vorgänge einzuschließen, die für Deinen Workflow erforderlich sind. In diesem Beispiel erstellt das Skript die Instanz des PostgreSQL-Clients, erstellt eine Tabelle, fügt Platzhalter-Daten hinzu und ruft dann die Daten ab.
+Du kannst *client.js* anpassen, um alle PostgreSQL-Vorgänge einzuschließen, die für Deinen Workflow erforderlich sind. In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-Das Skript erstellt einen neuen PostgreSQL-`Client`, der einen `host`- und einen `port`-Parameter akzeptiert. Das Skript verwendet die Umgebungsvariablen `POSTGRES_HOST` und `POSTGRES_PORT`, um die IP-Adresse und den Port des Clients festzulegen. Wenn `host` Und `port` nicht definiert sind, ist der Standard-Host `localhost` und der Standard-Port 5432.
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. Wenn `host` Und `port` nicht definiert sind, ist der Standard-Host `localhost` und der Standard-Port 5432.
 
-Das Skript erstellt eine Tabelle und füllt sie mit Platzhalterdaten auf. Um zu testen, ob die PostgreSQL-Datenbank die Daten enthält, gibt das Skript den Inhalt der Tabelle in das Konsolenprotokoll aus.
+Das Skript erstellt eine Tabelle und füllt sie mit Platzhalterdaten auf. To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-Wenn Du diesen Workflow ausführst, solltest Du im Schritt „Mit PostgreSQL verbinden“ die folgende Ausgabe sehen, welche zeigt, dass Du den PostgreSQL-Client erstellt und Daten hinzugefügt hast:
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index 7640312d27..900f30aa25 100644
--- a/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/de-DE/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ The following example workflow demonstrates how to build a container image and p
 
 Ensure that you provide your own values for all the variables in the `env` key of the workflow.
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### Additional resources
 
diff --git a/translations/de-DE/content/actions/guides/index.md b/translations/de-DE/content/actions/guides/index.md
index aa43ba5bfa..beeb1141cf 100644
--- a/translations/de-DE/content/actions/guides/index.md
+++ b/translations/de-DE/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/de-DE/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/de-DE/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..1daae0dfa4
--- /dev/null
+++ b/translations/de-DE/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Managing GitHub Actions with GitHub CLI
+intro: 'You can use {% data variables.product.prodname_cli %} to interact with {% data variables.product.prodname_actions %}.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### {% data variables.product.prodname_cli %} einrichten
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### Managing {% data variables.product.prodname_actions %} with {% data variables.product.prodname_cli %}
+
+To view all available commands related to {% data variables.product.prodname_actions %}, run `gh actions`.
+
+For more information on using commands in specific scenarios, see the following procedures:
+
+- "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)"
+- "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/de-DE/content/actions/guides/publishing-docker-images.md b/translations/de-DE/content/actions/guides/publishing-docker-images.md
index 9b73f7a712..f9f888c790 100644
--- a/translations/de-DE/content/actions/guides/publishing-docker-images.md
+++ b/translations/de-DE/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ Vielleicht findest Du es auch hilfreich, ein grundlegendes Verständnis von Folg
 
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
-- „[Docker für den Einsatz mit {% data variables.product.prodname_registry %} konfigurieren](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)“
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### Informationen zur Image-Konfiguration
 
@@ -98,7 +98,6 @@ Die für {% data variables.product.prodname_registry %} erforderlichen `build-pu
 * `registry`: Muss auf `docker.pkg.github.com` gesetzt werden.
 * `repository`: Muss im Format `OWNER/REPOSITORY/IMAGE_NAME` gesetzt werden. Beispiel: Für ein Bild namens `octo-image` auf {% data variables.product.prodname_dotcom %} unter `http://github. om/octo-org/octo-repo` sollte die Option `repository` auf `octo-org/octo-repo/octo-image` gesetzt werden.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -107,21 +106,23 @@ on:
 jobs:
   push_to_registry:
     name: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,7 +132,6 @@ In einem einzigen Workflow kannst Du Dein Docker-Image in mehreren Registries ve
 
 Der folgende Beispiel-Workflow verwendet die Schritte der `build-push-action` aus den vorherigen Abschnitten („[Veröffentlichung von Bildern auf ‚Docker Hub‘](#publishing-images-to-docker-hub)“ und „[Veröffentlichung von Bildern in {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)“), um einen einzigen Workflow zu erstellen, der in beide Registries pusht.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -140,26 +140,28 @@ on:
 jobs:
   push_to_registries:
     name: Push Docker image to multiple registries
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to Docker Hub
         uses: docker/build-push-action@v1
         with:
-          username: ${{ secrets.DOCKER_USERNAME }}
-          password: ${{ secrets.DOCKER_PASSWORD }}
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
           repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 Der obige Workflow checkt das {% data variables.product.prodname_dotcom %}-Repository aus und verwendet die Aktion `build-push-action` zweimal, um das Docker-Image zu erstellen und sowohl auf den „Docker Hub“ als auch in die {% data variables.product.prodname_registry %} zu übertragen. Für beide Schritte, setzt er die Option `build-push-action` auf [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) um das gebaute Docker-Image automatisch mit der Git-Referenz des Workflow-Ereignisses zu kennzeichnen. Dieser Workflow wird bei der Veröffentlichung eines {% data variables.product.prodname_dotcom %}-Releases ausgelöst, so dass die Referenz für beide Registries das Git-Tag des Releases ist.
diff --git a/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md
index 05df902ae2..25df15b986 100644
--- a/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/de-DE/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ Weitere Informationen zum Erstellen eines CI-Workflows für Dein Java-Projekt mi
 
 Vielleicht findest Du es auch hilfreich, ein grundlegendes Verständnis von Folgendem zu haben:
 
-- „[Konfiguration von npm für die Verwendung mit {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)“
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -108,7 +108,7 @@ Jedes Mal, wenn Du ein neues Release erstellst, kannst Du einen Workflow anstoß
 
 Du kannst ein neues Maven-Repository im Block `publishing` Deiner Datei _build.gradle_ definieren, das auf {% data variables.product.prodname_registry %} verweist.  In dieser Repository-Konfiguration kannst Du auch die in Deinem CI-Workflow-Lauf eingestellten Umgebungsvariablen nutzen.  Du kannst die Umgebungsvariable `GITHUB_ACTOR` als Benutzernamen verwenden und die Umgebungsvariable `GITHUB_TOKEN` auf Dein `GITHUB_TOKEN`-Geheimnis setzen.
 
-Der `GITHUB_TOKEN` existiert standardmäßig in Deinem Repository und hat Lese- und Schreibrechte für Pakete in dem Repository, in dem der Workflow läuft. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.github-token-permissions %}
 
 Wenn beispielsweise Deine Organisation „octocat“ und Dein Repository „hello-world“ heißt, sieht die {% data variables.product.prodname_registry %}-Konfiguration in _build.gradle_ so ähnlich wie im folgenden Beispiel aus.
 
@@ -133,7 +133,6 @@ publishing {
 
 Mit dieser Konfiguration kannst Du einen Workflow erstellen, der mithilfe des Befehls `gradle publish` Dein Paket im „Maven Central Repository“ veröffentlicht.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Führt den Befehl `gradle publish` aus, um in {% data variables.product.prodname_registry %} zu veröffentlichen. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gefüllt.
+1. Führt den Befehl `gradle publish` aus, um in {% data variables.product.prodname_registry %} zu veröffentlichen. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gefüllt. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    Weitere Informationen zur Verwendung von Geheimnissen in Deinem Workflow findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
 
@@ -199,7 +200,6 @@ publishing {
 
 Mit dieser Konfiguration kannst Du einen Workflow erstellen, der mithilfe des Befehls `gradle publish` Dein Paket sowohl im „Maven Central Repository“ als auch in der {% data variables.product.prodname_registry %} veröffentlicht.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Führt den Befehl `gradle publish` aus, um im Maven-Repository `OSSRH` und in der {% data variables.product.prodname_registry %} zu veröffentlichen. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt Deines Geheimnisses `OSSRH_USERNAME` gefüllt, und die Umgebungsvariable `MAVEN_PASSWORD` wird mit dem Inhalt Deines Geheimnisses `OSSRH_TOKEN` gefüllt. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gefüllt.
+1. Führt den Befehl `gradle publish` aus, um im Maven-Repository `OSSRH` und in der {% data variables.product.prodname_registry %} zu veröffentlichen. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt Deines Geheimnisses `OSSRH_USERNAME` gefüllt, und die Umgebungsvariable `MAVEN_PASSWORD` wird mit dem Inhalt Deines Geheimnisses `OSSRH_TOKEN` gefüllt. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gefüllt. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    Weitere Informationen zur Verwendung von Geheimnissen in Deinem Workflow findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
diff --git a/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md b/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md
index 2c15d9ce13..d3fba8afd3 100644
--- a/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/de-DE/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ Weitere Informationen zum Erstellen eines CI-Workflows für Dein Java-Projekt mi
 
 Vielleicht findest Du es auch hilfreich, ein grundlegendes Verständnis von Folgendem zu haben:
 
-- „[Konfiguration von npm für die Verwendung mit {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)“
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -112,9 +112,9 @@ Dieser Workflow führt die folgenden Schritte aus:
 
 Jedes Mal, wenn Du ein neues Release erstellst, kannst Du einen Workflow anstoßen, um Dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel wird von dem Ereignis `release` vom Typ `created` angestoßen. Der Workflow veröffentlicht das Paket in {% data variables.product.prodname_registry %} , wenn die CI-Tests bestanden wurden. Weitere Informationen zum Ereignis `release` findest Du unter „[Ereignisse, die Workflows anstoßen](/actions/reference/events-that-trigger-workflows#release)“.
 
-In diesem Workflow kannst Du die Aktion `setup-java` verwenden. Diese Aktion installiert die angegebene JDK-Version in den `PATH` und stellt auch Maven- _settings.xml_ ein, um Paket in der {% data variables.product.prodname_registry %} zu veröffentlichen. Die generierte _settings.xml_ definiert die Authentifizierung für einen Server mit einer `id` von `github` und verwendet die Umgebungsvariable `GITHUB_ACTOR` als Benutzername und die Umgebungsvariable `GITHUB_TOKEN` als Passwort.
+In diesem Workflow kannst Du die Aktion `setup-java` verwenden. Diese Aktion installiert die angegebene JDK-Version in den `PATH` und stellt auch Maven- _settings.xml_ ein, um Paket in der {% data variables.product.prodname_registry %} zu veröffentlichen. Die generierte _settings.xml_ definiert die Authentifizierung für einen Server mit einer `id` von `github` und verwendet die Umgebungsvariable `GITHUB_ACTOR` als Benutzername und die Umgebungsvariable `GITHUB_TOKEN` als Passwort. The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
 
-Der `GITHUB_TOKEN` existiert standardmäßig in Deinem Repository und hat Lese- und Schreibrechte für Pakete in dem Repository, in dem der Workflow läuft. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.github-token-permissions %}
 
 Für ein Maven-basiertes Projekt kannst Du diese Einstellungen nutzen, indem Du ein Distributions-Repository in Deiner Datei _pom.xml_ mit einer `id` von `Github` erstellst, das auf Deinen {% data variables.product.prodname_registry %}-Endpunkt zeigt.
 
@@ -137,7 +137,6 @@ Wenn beispielsweise Deine Organisation „octocat“ und Dein Repository „hell
 
 Mit dieser Konfiguration kannst Du einen Workflow erstellen, der Dein Paket in der {% data variables.product.prodname_registry %} veröffentlicht, indem Du die automatisch generierte _settings.xml_ verwendest.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Dieser Workflow führt die folgenden Schritte aus:
 
@@ -173,7 +174,6 @@ Du kannst Deine Pakete sowohl im Maven Central Repository als auch in der {% dat
 
 Stelle sicher, dass Deine Datei _pom.xml_ ein Distributionsmanagement-Repository sowohl für Dein {% data variables.product.prodname_dotcom %}-Repository als auch Deinen „Maven Central Repository“-Provider enthält. Wenn Du z.B. über das Hosting-Projekt OSSRH in das Central Repository deployst, solltest Du es vielleicht in einem Distributionsverwaltungs-Repository mit `ossrh` als `id` angeben, und Du solltest {% data variables.product.prodname_registry %} in einem Distributionsverwaltungs-Repository mit `github` als `id` setzen.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Dieser Workflow ruft die Aktion `setup-java` zweimal auf.  Jedes Mal, wenn die Aktion `setup-java` ausgeführt wird, überschriebt sie die Maven-Datei _settings.xml_ zum Publizieren von Paketen.  Für die Authentifizierung im Repository verweist die Datei _settings.xml_ auf die `id` des Distributionsverwaltungs-Repositorys sowie den Benutzernamen und das Kennwort.
 
diff --git a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md
index aaac5a2a55..95ed4a2126 100644
--- a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ Weitere Informationen zum Erstellen eines CI-Workflows für Dein Node.js-Projekt
 
 Vielleicht findest Du es auch hilfreich, ein grundlegendes Verständnis von Folgendem zu haben:
 
-- „[Konfiguration von npm für die Verwendung mit {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)“
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ However, if you do provide the `repository` key, then the repository in that key
 
 #### Authenticating to the destination repository
 
-To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)."
+Um authentifizierte Vorgänge für die Registry {% data variables.product.prodname_registry %} in Deinem Workflow kannst Du den `GITHUB_TOKEN` verwenden. {% data reusables.github-actions.github-token-permissions %}
 
 If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 
@@ -120,7 +120,6 @@ If you want to publish your package to a different repository, you must use a pe
 
 Dieses Beispiel speichert das Geheimnis `GITHUB_TOKEN` in der Umgebungsvariablen `NODE_AUTH_TOKEN`. Wenn die Aktion `setup-node` eine Datei *.npmrc* erzeugt, referenziert sie das Token aus der Umgebungsvariable `NODE_AUTH_TOKEN`.
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Die Aktion `setup-node` erzeugt eine Datei *.npmrc* auf dem Runner. Wenn Du für die Aktion `setup-node` die Eingabe `scope` verwendest, enthält die Datei *.npmrc* das Präfix „scope“. Standardmäßig legt die Aktion `setup-node` den „Scope“ (Geltungsbereich) in der Datei *.npmrc* auf das Konto fest, das diese Workflow-Datei enthält.
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,13 +197,13 @@ Wenn Du ein Paket in beiden Registries veröffentlichst, musst Du sicherstellen,
 
 Stelle sicher, dass in Deiner Datei *package.json* den Geltungsbereich Deines {% data variables.product.prodname_dotcom %}-Repositorys und der npm-Registry angegeben ist. Wenn Du beispielsweise ein Paket im Repository `octocat/npm-hello-world-test` auf {% data variables.product.prodname_dotcom %} und https://www.npmjs.com/package/@octocat/npm-hello-world-test veröffentlichen willst, dann sollte in Deiner Datei *package.json* der Name `"name": "@octocat/npm-hello-world-test"` stehen.
 
-Um authentifizierte Vorgänge für die Registry {% data variables.product.prodname_registry %} in Deinem Workflow kannst Du den `GITHUB_TOKEN` verwenden. Der `GITHUB_TOKEN` existiert standardmäßig in Deinem Repository und hat Lese- und Schreibrechte für Pakete in dem Repository, in dem der Workflow läuft. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
+Um authentifizierte Vorgänge für die Registry {% data variables.product.prodname_registry %} in Deinem Workflow kannst Du den `GITHUB_TOKEN` verwenden. {% data reusables.github-actions.github-token-permissions %}
 
 Wenn Du für die Aktion `setup-node` die Eingabe `scope` verwendest, erstellt die Aktion eine Datei *.npmrc* mit dem Präfix „scope“. Standardmäßig legt die Aktion `setup-node` den Geltungsbereich in der Datei *.npmrc* auf den Benutzer oder die Organisation fest, der die Workflow-Datei gehört.
 
 Dieser Workflow ruft die Aktion `setup-node` zweimal auf. Jedes Mal, wenn die Aktion `setup-node` ausgeführt wird, überschreibt sie die Datei *.npmrc*. Die Datei *.npmrc* referenziert den Token, mit dem Du authentifizierte Operationen in der Paket-Registry durchführen kannst, durch die Umgebungsvariable `NODE_AUTH_TOKEN`. Der Workflow setzt die Umgebungsvariable `NODE_AUTH_TOKEN` jedes Mal, wenn der Befehl `npm publish` ausgeführt wird; zuerst mit einem Token zum Veröffentlichen auf npm (`NPM_TOKEN`) und dann mit einem Token zum Veröffentlichen in der {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
 
-{% raw %}
+
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -210,28 +211,30 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v1
-      with:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    # Publish to npm
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v1
-      with:
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    # Publish to GitHub Packages
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/de-DE/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/de-DE/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index 40ce971249..53748018e3 100644
--- a/translations/de-DE/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/de-DE/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 3. {% data reusables.actions.make-workflow-file %}
 4. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. Customize the parameters in your workflow file:
    - In `github.event.project_card.column_id == '12345678'`, replace `12345678` with the ID of the column where you want to un-label issues and pull requests that are moved there.
 
diff --git a/translations/de-DE/content/actions/guides/scheduling-issue-creation.md b/translations/de-DE/content/actions/guides/scheduling-issue-creation.md
index e74d34f86d..5651d952e5 100644
--- a/translations/de-DE/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/de-DE/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:20 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `assignees` to the list of {% data variables.product.prodname_dotcom %} usernames that you want to assign to the issue.
diff --git a/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md
index ecfdcf8520..2b55d4f6f8 100644
--- a/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md
+++ b/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md
@@ -20,6 +20,7 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 Jeder Benutzer mit Schreibberechtigung für ein Repository kann mit {% data variables.product.prodname_actions %} eine fortlaufende Integration (CI) einrichten.
 
@@ -33,7 +34,7 @@ Nach der Einrichtung der CI können Sie den Workflow an Ihre Bedürfnisse anpass
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-Sobald ein Push an Ihr Repository erfolgt ist, können Sie den Status und die detaillierten Protokolle Ihres fortlaufenden Integrationsworkflows verfolgen, der auf {% data variables.product.prodname_dotcom %} ausgeführt wird, und angepasste Benachrichtigungen erhalten. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)“ und „[Workflowausführung verwalten](/articles/managing-a-workflow-run)“.
+Sobald ein Push an Dein Repository erfolgt ist, kannst Du den Status und die detaillierten Protokolle Deines fortlaufenden Integrationsworkflows verfolgen, der auf {% data variables.product.prodname_dotcom %} ausgeführt wird, und angepasste Benachrichtigungen erhalten. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)“ und „[Workflowausführung verwalten](/articles/managing-a-workflow-run)“.
 
 {% data reusables.repositories.actions-workflow-status-badge-into %}
 
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 4fd71ea569..54bb8ab90a 100644
--- a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -53,7 +53,7 @@ When creating a group, you must choose a policy that defines which repositories
 
    **Warnung**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“.
 
@@ -85,7 +85,7 @@ When creating a group, you must choose a policy that defines which organizations
 
    **Warnung**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“.
 
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index afa042ef08..2de4ba6800 100644
--- a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -66,7 +66,7 @@ Um einen selbst-gehosteten Runner aus einer Organisation zu entfernen, musst Du
 
 {% if currentVersion == "free-pro-team@latest" %}
 To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 To remove a self-hosted runner at the enterprise level of
 {% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine.
 {% endif %}
diff --git a/translations/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md
index 3a4018869e..52d7a5ec0b 100644
--- a/translations/de-DE/content/actions/index.md
+++ b/translations/de-DE/content/actions/index.md
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Code examples</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Search code examples" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Show more {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Sorry, there is no result for <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Learn how to add a code example {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index 79d7f8fbdc..9b78f37bbc 100644
--- a/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/de-DE/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index ca354f62d8..0b3875c20b 100644
--- a/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ If you need to share workflows and other {% data variables.product.prodname_acti
 
 ### Erstellen einer Workflowvorlage
 
-Workflowvorlagen können von Benutzern mit Schreibzugriff auf die `.github` Repository der Organisation erstellt werden. Die Vorlagen können dann von Organisationsmitgliedern verwendet werden, die über die Berechtigung zum Erstellen von Workflows verfügen. Workflowvorlagen können verwendet werden, um neue Workflows in öffentlichen Repositorys einer Organisation zu erstellen. Um Vorlagen zum Erstellen von Workflows in privaten Repositorys zu verwenden, muss die Organisation Teil eines Unternehmens- oder GitHub One-Plans sein.
+Workflowvorlagen können von Benutzern mit Schreibzugriff auf die `.github` Repository der Organisation erstellt werden. Die Vorlagen können dann von Organisationsmitgliedern verwendet werden, die über die Berechtigung zum Erstellen von Workflows verfügen. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise plan.
 
 In diesem Verfahren wird veranschaulicht, wie eine Workflowvorlage und eine Metadatendatei erstellt werden. Die Metadatendatei beschreibt, wie die Vorlage benutzern beim Erstellen eines neuen Workflows angezeigt wird.
 
 1. Wenn es noch nicht vorhanden ist, erstellen Sie ein neues öffentliches Repository mit dem Namen `.github` in Ihrer Organisation.
-1. Erstellen Sie ein Verzeichnis mit dem Namen `Workflowvorlagen`.
-1. Erstellen Sie Ihre neue Workflowdatei im `Workflow-Vorlagen` Verzeichnis.
+2. Erstellen Sie ein Verzeichnis mit dem Namen `Workflowvorlagen`.
+3. Erstellen Sie Ihre neue Workflowdatei im `Workflow-Vorlagen` Verzeichnis.
 
    Wenn Sie auf den Standardzweig eines Repositorys verweisen müssen, können Sie den `$default-branch` Platzhalter verwenden. Wenn ein Workflow mit Ihrer Vorlage erstellt wird, wird der Platzhalter automatisch durch den Namen der Standardverzweigung des Repositorys ersetzt.
 
@@ -52,7 +52,7 @@ In diesem Verfahren wird veranschaulicht, wie eine Workflowvorlage und eine Meta
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. Erstellen Sie eine Metadatendatei im `Workflow-Vorlagen` Verzeichnis. Die Metadatendatei muss denselben Namen wie die Workflowdatei haben, aber anstelle der Erweiterung `.yml` muss sie mit `.properties.json`angehängt werden. Diese Datei mit dem Namen `octo-organization-ci.properties.json enthält` beispielsweise die Metadaten für eine Workflowdatei mit dem Namen `octo-organization-ci.yml`:
+4. Erstellen Sie eine Metadatendatei im `Workflow-Vorlagen` Verzeichnis. Die Metadatendatei muss denselben Namen wie die Workflowdatei haben, aber anstelle der Erweiterung `.yml` muss sie mit `.properties.json`angehängt werden. Diese Datei mit dem Namen `octo-organization-ci.properties.json enthält` beispielsweise die Metadaten für eine Workflowdatei mit dem Namen `octo-organization-ci.yml`:
    ```yaml
    •
        "Name": "Octo Organization Workflow",
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..a41d459b53
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: Approving workflow runs from public forks
+intro: 'When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve any workflow runs.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+Forks of public repositories can submit pull requests that propose changes to a repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests are not run automatically if they are received from first-time contributors, and must be approved first.
+
+Maintainers with write access to the repository can use the following procedure to review and run workflows on pull requests from first-time contributors. After a contributor has at least one pull request merged into a project's repository, any future pull requests from that contributor's fork will automatically run workflows.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
+1. If you are comfortable with running workflows on the pull request branch, return to the {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
+
+   ![Approve and run workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index 508c80e933..71a4a8c1e9 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Disabling and enabling a workflow
-intro: 'You can disable and re-enable a workflow using {% data variables.product.prodname_dotcom %} or the REST API.'
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}. You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
 
 Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
 
@@ -27,7 +27,9 @@ Temporarily disabling a workflow can be useful in many scenarios. These are a fe
 
 {% endwarning %}
 
-### Disabling a workflow
+### Disabling and enabling workflows with the {% data variables.product.prodname_dotcom %} UI
+
+#### Disabling a workflow
 
 You can manually disable a workflow so that it won't execute any workflow runs. A disabled workflow is not deleted, and can be re-enabled.
 
@@ -37,7 +39,7 @@ You can manually disable a workflow so that it won't execute any workflow runs.
 1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. Click **Disable workflow**. ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png) The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status. ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### Enabling a workflow
+#### Enabling a workflow
 
 You can re-enable a workflow that was previously disabled.
 
@@ -45,3 +47,23 @@ You can re-enable a workflow that was previously disabled.
 {% data reusables.repositories.actions-tab %}
 1. In the left sidebar, click the workflow you want to enable. ![actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. Click **Enable workflow**. ![actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+
+### Disabling and enabling workflows with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### Disabling and enabling workflows through the REST API
+
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 6d5d5c15e5..df1708dc20 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Configuring the retention period for GitHub Actions artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %}
 
+### Download artifacts with the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### Download artifacts with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+{% data variables.product.prodname_cli %} will download each artifact into separate directories based on the artifact name. If only a single artifact is specified, it will be extracted into the current directory.
+
+To download all artifacts generated by a workflow run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run download <em>run-id</em>
+```
+
+To download a specific artifact from a run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. Replace `artifact-name` with the name of the artifact that you want to download.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+You can specify more than one artifact.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+To download specific artifacts across all runs in a repository, use the `run download` subcommand.
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/index.md b/translations/de-DE/content/actions/managing-workflow-runs/index.md
index 2606df2f97..2e9d581196 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/index.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index 3cf3da2c3f..b62458f906 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Manuelle Ausführung eines Workflows
-intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the REST API or from the Actions tab on {% data variables.product.prodname_dotcom %}.'
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -28,6 +28,40 @@ To trigger the `workflow_dispatch` event on {% data variables.product.prodname_d
 1. Wählen Sie über der Liste der Workflowausführungen **Workflow ausführen**. ![Aktionsworkflow-Dispatch](/assets/images/actions-workflow-dispatch.png)
 1. Wählen Sie die Verzweigung aus, in der der Workflow ausgeführt wird, und geben Sie die Eingabeparameter ein, die vom Workflow verwendet werden. Klicken Sie auf **Workflow ausführen**. ![Aktionen manuell ausgeführt Workflow](/assets/images/actions-manually-run-workflow.png)
 
+### Running a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+You can also pass inputs as JSON by using standard input.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
+
 ### Running a workflow using the REST API
 
 Wenn Sie die REST-API verwenden, konfigurieren Sie die `eingaben` und `ref` als Anforderungstextparameter. Wenn die Eingaben weggelassen werden, werden die in der Workflowdatei definierten Standardwerte verwendet.
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md
index f72ee39863..171c1397f3 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Re-run a workflow using the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### Re-run a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run.  If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 400c2c35d6..8ac1d9fbe6 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. Under **Artifacts**, click
-{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove.
+{% octicon "trash" aria-label="The trash icon" %} next to the artifact you want to remove.
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![Dropdown-Menü zum Löschen von Artefakten](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index 62601850d3..a6ae769374 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ After deleting logs, the **Delete all logs** button is removed to indicate that
 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. Um die Logdateien zu löschen, klicke auf **Delete all logs** (Alle Logs löschen) und überprüfe die Bestätigungsanfrage. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) After the logs have been deleted, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
 {% endif %}
+
+### Viewing logs with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To view the log for a specific job, use the `run view` subcommand. Replace `run-id` with the ID of run that you want to view logs for. {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a job from the run. If you don't specify `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run, and then returns another interactive menu for you to choose a job from the run.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+You can also use the `--job` flag to specify a job ID. Replace `job-id` with the ID of the job that you want to view logs for.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+You can use `grep` to search the log. For example, this command will return all log entries that contain the word `error`.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+To filter the logs for any failed steps, use `--log-failed` instead of `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/de-DE/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index 284bd3fcd9..a5281b4577 100644
--- a/translations/de-DE/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/de-DE/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Viewing workflow run history on {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### Viewing workflow run history with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+#### Viewing recent workflow runs
+
+To list the recent workflow runs, use the `run list` subcommand.
+
+```shell
+gh run list
+```
+
+To specify the maximum number of runs to return, you can use the `-L` or `--limit` flag . The default is `10`.
+
+```shell
+gh run list --limit 5
+```
+
+To only return runs for the specified workflow, you can use the `-w` or `--workflow` flag.  Replace `workflow` with either the workflow name, workflow ID, or workflow file name. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### Viewing details for a specific workflow run
+
+To display details for a specific workflow run, use the `run view` subcommand. Replace `run-id` with the ID of the run that you want to view. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+To include job steps in the output, use the `-v` or `--verbose` flag.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+To view details for a specific job in the run, use the `-j` or `--job` flag.  Replace `job-id` with the ID of the job that you want to view.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+To view the full log for a job, use the `--log` flag.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Use the `--exit-status` flag to exit with a non-zero status if the run failed. Ein Beispiel:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md b/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md
index d4775ea63d..bdc6414821 100644
--- a/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/de-DE/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ Das Token ist auch im `github.token`-Kontext verfügbar. Weitere Informationen f
 
 ### Das `GITHUB_TOKEN` in einem Workflow verwenden
 
-Um das `GITHUB_TOKEN`-Geheimnis zu verwenden, musst Du es in Deiner Workflow-Datei referenzieren. Hierbei müssen Sie das Token ggf. als Eingabe für eine Aktion übergeben, für die dieses Token erforderlich ist, oder authentifizierte {% data variables.product.prodname_dotcom %}-API-Aufrufe ausführen.
+You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% data variables.product.prodname_dotcom %} API request.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. Weitere Informationen findest Du unter "[Berechtigungen für das `GITHUB_TOKEN`](#permissions-for-the-github_token)."
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### Beispiel: Das `GITHUB_TOKEN` als Eingabe übergeben
+#### Example 1: passing the `GITHUB_TOKEN` as an input
 
 Dieser Beispielworkflow verwendet die [Labeler-Aktion](https://github.com/actions/labeler), wofür das `GITHUB_TOKEN` als Wert für den Eingabeparameter `repo-token` benötigt wird:
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### Beispiel zum Aufrufen der REST-API
+#### Example 2: calling the REST API
 
 Du kannst das `GITHUB_TOKEN` verwenden, um authentifizierte API-Aufrufe durchzuführen. Dieser Beispiel-Workflow erzeugt eine Lieferung („issue“) mittels der {% data variables.product.prodname_dotcom %}-REST-API:
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,15 +88,31 @@ Du kannst das `GITHUB_TOKEN` verwenden, um authentifizierte API-Aufrufe durchzuf
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n Der Commit-Hash lautete: _'{{ github.sha }}_."
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### Berechtigungen für das `GITHUB_TOKEN`
 
 For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)."
 
-| Berechtigung             | Zugriffstyp     | Zugriff durch geforktes Repository |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an enterprise, organization, or repository 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 {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-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 "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
+
+| Scope                    | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
+| ------------------------ | ------------------------------------ | ------------------------------------ | --------------------------------------- |
+| actions                  | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| checks (Prüfungen)       | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| contents (Inhalte)       | Lesen/Schreiben                      | Lesen                                | Lesen                                   |
+| deployments              | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| Issues (Lieferungen)     | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| Metadaten                | Lesen                                | Lesen                                | Lesen                                   |
+| Pakete                   | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| pull requests            | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| repository projects      | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| security events          | Lesen/Schreiben                      | none                                 | Lesen                                   |
+| statuses (Statusangaben) | Lesen/Schreiben                      | none                                 | Lesen                                   |
+{% else %}
+| Scope                    | Zugriffstyp     | Zugriff durch geforktes Repository |
 | ------------------------ | --------------- | ---------------------------------- |
 | actions                  | Lesen/Schreiben | Lesen                              |
 | checks (Prüfungen)       | Lesen/Schreiben | Lesen                              |
@@ -94,9 +124,32 @@ For information about the API endpoints {% data variables.product.prodname_githu
 | pull requests            | Lesen/Schreiben | Lesen                              |
 | repository projects      | Lesen/Schreiben | Lesen                              |
 | statuses (Statusangaben) | Lesen/Schreiben | Lesen                              |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### Modifying the permissions for the `GITHUB_TOKEN`
+
+You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access.
+
+You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "Set up job" section of the workflow run log. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+
+You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
+
+{% data reusables.github-actions.forked-write-permission %}
+
+The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
+
+For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+
+##### How the permissions are calculated for a workflow job
+
+The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
+
+#### Granting additional permissions
+{% endif %}
+
 Wenn Du ein Token benötigst, für das Berechtigungen erforderlich sind, die nicht im `GITHUB_TOKEN`-Geheimnis vorhanden sind, kannst Du ein persönliches Zugangstoken erstellen und als Geheimnis im Repository festlegen:
 
 1. Verwende oder erstelle ein Token mit den entsprechenden Berechtigungen für dieses Repository. Weitere Informationen finden Sie unter "[Erstellen eines persönlichen Zugriffstokens](/github/authenticating-to-github/creating-a-personal-access-token)."
diff --git a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index 19d2cc7a3b..bf424d4569 100644
--- a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ Kontexte sind eine Möglichkeit, auf Informationen zu Workflow-Läufen, Runner-U
 | Kontextname | Typ      | Beschreibung                                                                                                                                                                                                                                                                                |
 | ----------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `github`    | `Objekt` | Informationen zum Workflow-Lauf. Weitere Informationen findest Du unter „[`github`-Kontext](#github-context)“.                                                                                                                                                                              |
-| `env`       | `Objekt` | Enthält Umgebungsvariablen, die in einem Workflow, Job oder Schritt festgelegt sind. Weitere Informationen findest Du unter [`env`-Kontext](#env-context) .                                                                                                                                 |
+| `env`       | `Objekt` | Enthält Umgebungsvariablen, die in einem Workflow, Job oder Schritt festgelegt sind. Weitere Informationen findest Du unter [`env`-Kontext](#env-context).                                                                                                                                  |
 | `Auftrag`   | `Objekt` | Informationen zum derzeit ausgeführten Job. Weitere Informationen findest Du unter „[`job`-Kontext](#job-context)“.                                                                                                                                                                         |
 | `steps`     | `Objekt` | Informationen zu den Schritten, die bei diesem Job ausgeführt wurden. Weitere Informationen findest Du unter „[`steps`-Kontext](#steps-context)“.                                                                                                                                           |
 | `runner`    | `Objekt` | Informationen zu dem Runner, der den aktuellen Job ausführt. Weitere Informationen findest Du unter [`runner`-Kontext](#runner-context).                                                                                                                                                    |
@@ -93,11 +93,11 @@ Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereigni
 | `github.action`           | `string` | Der Name der aktuell laufenden Aktion. {% data variables.product.prodname_dotcom %} entfernt Sonderzeichen oder verwendet den Namen `run` wenn der aktuelle Schritt ein Skript ausführt.  Wenn Du dieselbe Aktion mehr als einmal im selben Job verwendest, enthält der Name ein Suffix mit der Sequenznummer.  Zum Beispiel wird das erste Skript, das Du ausführst, den Namen `run1`haben, und das zweite Skript heißt `run2`. Ebenso wird die zweite Anrufung von `actions/checkout` `actionscheckout2` sein. |
 | `github.action_path`      | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite run steps actions.                                                                                                                                                                                                                                                                                                              |
 | `github.actor`            | `string` | Der Anmeldename des Benutzers, der den Workflow-Lauf initiiert hat                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `github.base_ref`         | `string` | Das `base_ref` oder der Ziel-Branch des Pull Requests in einem Workflow-Lauf. Diese Eigenschaft ist nur verfügbar, wenn das Ereignis, das einen Workflow auslöst, ein `pull_request` (Pull Request) ist.                                                                                                                                                                                                                                                                                                         |
+| `github.base_ref`         | `string` | Das `base_ref` oder der Ziel-Branch des Pull Requests in einem Workflow-Lauf. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                                                                                                                                                                                                                     |
 | `github.event`            | `Objekt` | Die vollständige Nutzlast des Ereignis-Webhooks. Weitere Informationen findest Du unter „[Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows)“. You can access individual properties of the event using this context.                                                                                                                                                                                                                                                                   |
 | `github.event_name`       | `string` | Der Name des Ereignisses, das den Workflow-Lauf ausgelöst hat.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | `github.event_path`       | `string` | Der Pfad zur vollständigen Event-Webhook-Nutzlast auf dem Runner.                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| `github.head_ref`         | `string` | Das `head_ref` oder der Quell-Branch des Pull Requests in einem Workflow-Lauf. Diese Eigenschaft ist nur verfügbar, wenn das Ereignis, das einen Workflow auslöst, ein `pull_request` (Pull Request) ist.                                                                                                                                                                                                                                                                                                        |
+| `github.head_ref`         | `string` | Das `head_ref` oder der Quell-Branch des Pull Requests in einem Workflow-Lauf. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                                                                                                                                                                                                                    |
 | `github.job`              | `string` | Die [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) des aktuellen Jobs.                                                                                                                                                                                                                                                                                                                                                                                                             |
 | `github.ref`              | `string` | Das Branch- oder Tag-Ref, das den Workflow-Lauf ausgelöst hat. For branches this in the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                               |
 | `github.repository`       | `string` | Der Inhaber- und Repository-Name, z. B. `Codertocat/Hello-World`.                                                                                                                                                                                                                                                                                                                                                                                                                                                |
@@ -323,7 +323,7 @@ Gibt `true` zurück, wenn der `searchString` mit `searchValue` endet. Bei dieser
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-Ersetzt die Werte im `string` durch die Variable `replaceValueN`. Variablen im `string` werden mit der `{N}`-Syntax festgelegt, wobei `N` eine Ganzzahl ist. Du musst mindestens einen `replaceValue` und `string` festlegen. Du kannst eine unbegrenzte Anzahl an Variablen (`replaceValueN`) verwenden. Maskiere geschweifte Klammern mit doppelten Klammern.
+Ersetzt die Werte im `string` durch die Variable `replaceValueN`. Variablen im `string` werden mit der `{N}`-Syntax festgelegt, wobei `N` eine Ganzzahl ist. Du musst mindestens einen `replaceValue` und `string` festlegen. Du kannst eine unbegrenzte Anzahl an Variablen (`replaceValueN`) verwenden. Escape curly braces using double braces.
 
 ##### Beispiel
 
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
diff --git a/translations/de-DE/content/actions/reference/encrypted-secrets.md b/translations/de-DE/content/actions/reference/encrypted-secrets.md
index f6bf0e3ed8..5d533095fa 100644
--- a/translations/de-DE/content/actions/reference/encrypted-secrets.md
+++ b/translations/de-DE/content/actions/reference/encrypted-secrets.md
@@ -29,21 +29,15 @@ For secrets stored at the environment level, you can enable required reviewers t
 
 #### Benennen Ihrer Geheimnisse
 
-Die folgenden Regeln gelten für geheime Namen:
+{% data reusables.codespaces.secrets-naming %}. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
 
-* Geheime Namen dürfen nur alphanumerische Zeichen (`[a-z]`, `[A-Z]`, `[0-9]`) oder Unterstriche (`_`) enthalten. Leerzeichen sind nicht zulässig.
-* Geheime Namen dürfen nicht mit dem `GITHUB_` -Präfix beginnen.
-* Geheime Namen dürfen nicht mit einer Zahl beginnen.
-* Secret names are not case-sensitive.
-* Geheime Namen müssen auf der Ebene eindeutig sein, auf der sie erstellt werden. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
-
-  If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
+  {% data reusables.codespaces.secret-precedence %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
 
 To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. Vermeide beispielsweise Geheimnisse zu erstellen, die JSON oder codierte Git-Blobs enthalten.
 
 #### Zugriff auf Ihre Geheimnisse
 
-Um ein Geheimnis für eine Aktion verfügbar zu machen, legen Sie das Geheimnis als Eingabe oder Umgebungsvariable in der Workflow-Datei fest. In der README-Datei der Aktion erfahren Sie, welche Eingaben und Umgebungsvariablen die Aktion erwartet. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“.
+Um ein Geheimnis für eine Aktion verfügbar zu machen, legen Sie das Geheimnis als Eingabe oder Umgebungsvariable in der Workflow-Datei fest. In der README-Datei der Aktion erfahren Sie, welche Eingaben und Umgebungsvariablen die Aktion erwartet. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“.
 
 Du kannst verschlüsselte Geheimnisse in einer Workflow-Datei verwenden und lesen, wenn Du auf die Datei Bearbeitungs-Zugriff hast. Weitere Informationen findest Du unter „[Zugriffsberechtigungen auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)“.
 
@@ -83,7 +77,8 @@ If your repository {% if currentVersion == "free-pro-team@latest" or currentVers
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" }
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+
 ### Creating encrypted secrets for an environment
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
@@ -125,7 +120,11 @@ Sie können überprüfen, welche Zugriffsrichtlinien auf einen geheimen Schlüss
 
 ### Verschlüsselte Geheimnisse in einem Workflow verwenden
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
+
+**Note:** {% data reusables.actions.forked-secrets %}
+
+{% endnote %}
 
 Um eine Aktion mit einem Geheimnis als Eingabe- oder Umgebungsvariable zu versehen, kannst Du den `secrets` Kontext verwenden, um auf Geheimnisse zuzugreifen, die Du in Deinem Repository erstellt hast. Weitere Informationen findest Du unter "[Kontext und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" und "[Workflow-Syntax für {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 
@@ -187,11 +186,11 @@ steps:
 
 You can store up to 1,000 secrets per organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, 100 secrets per repository, and 100 secrets per environment{% else %} and 100 secrets per repository{% endif %}. A workflow may use up to 100 organization secrets and 100 repository secrets.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Additionally, a job referencing an environment may use up to 100 environment secrets.{% endif %}
 
-Geheimnisse sind auf 64 KB beschränkt. Um Geheimnisse zu verwenden, die größer als 64 KB sind, kannst Du verschlüsselte Geheimnisse in Deinem Repository speichern und die Passphrase zur Entschlüsselung als Geheimnis auf {% data variables.product.prodname_dotcom %} speichern. Du kannst beispielsweise `gpg` verwenden, um Deine Anmeldeinformationen lokal zu verschlüsseln, bevor Du die Datei in Ihrem Repository auf {% data variables.product.prodname_dotcom %} eincheckst. Weitere Informationen finden Sie auf der „[gpg-Manpage](https://www.gnupg.org/gph/de/manual/r1023.html)“.
+Geheimnisse sind auf 64 KB beschränkt. Um Geheimnisse zu verwenden, die größer als 64 KB sind, können Sie verschlüsselte Geheimnisse in Ihrem Repository speichern und die Passphrase zur Entschlüsselung als Geheimnis auf {% data variables.product.prodname_dotcom %} speichern. Sie können beispielsweise `gpg` verwenden, um Ihre Anmeldeinformationen lokal zu verschlüsseln, bevor Sie die Datei in Ihrem Repository auf {% data variables.product.prodname_dotcom %} einchecken. Weitere Informationen finden Sie auf der „[gpg-Manpage](https://www.gnupg.org/gph/de/manual/r1023.html)“.
 
 {% warning %}
 
-**Warnung**: Achte darauf, dass Deine Geheimnisse nicht gedruckt werden, wenn Deine Aktion ausgeführt wird. Wenn Du diesen Workaround verwendest, redigiert {% data variables.product.prodname_dotcom %} keine Geheimnisse, die in Protokollen gedruckt werden.
+**Warnung**: Achte darauf, dass Deine Geheimnisse nicht gedruckt werden, wenn Deine Aktion ausgeführt wird. Wenn Sie diesen Workaround verwenden, redigiert {% data variables.product.prodname_dotcom %} keine Geheimnisse, die in Protokollen gedruckt werden.
 
 {% endwarning %}
 
diff --git a/translations/de-DE/content/actions/reference/environment-variables.md b/translations/de-DE/content/actions/reference/environment-variables.md
index 9485f42775..43f6a5d937 100644
--- a/translations/de-DE/content/actions/reference/environment-variables.md
+++ b/translations/de-DE/content/actions/reference/environment-variables.md
@@ -58,6 +58,7 @@ Es wird dringend empfohlen, dass Aktionen Umgebungsvariablen verwenden, um auf d
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
 | `GITHUB_JOB`         | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                                                                                                                                     |
 | `GITHUB_ACTION`      | Die eindeutige Kennung (`id`) der Aktion.                                                                                                                                                                                                                                                                                                                                              |
+| `GITHUB_ACTION_PATH` | The path where your action is located. You can use this path to access files located in the same repository as your action. This variable is only supported in composite run steps actions.                                                                                                                                                                                            |
 | `GITHUB_ACTIONS`     | Immer auf `true` gesetzt, wenn {% data variables.product.prodname_actions %} den Workflow ausführt. Du kannst diese Variable verwenden, um zu differenzieren, wann Tests lokal oder von {% data variables.product.prodname_actions %} durchgeführt werden.                                                                                                                           |
 | `GITHUB_ACTOR`       | Name der Person oder App, die den Workflow initiiert hat. Beispiel: `octocat`.                                                                                                                                                                                                                                                                                                         |
 | `GITHUB_REPOSITORY`  | Der Inhaber- und Repository-Name, Beispiel: `octocat/Hello-World`.                                                                                                                                                                                                                                                                                                                     |
@@ -68,9 +69,9 @@ Es wird dringend empfohlen, dass Aktionen Umgebungsvariablen verwenden, um auf d
 | `GITHUB_REF`         | Branch- oder Tag-Ref, das den Workflow ausgelöst hat. Beispiel: `refs/heads/feature-branch-1`. Wenn für den Ereignistyp weder ein Branch noch ein Tag vorliegt, ist die Variable nicht vorhanden.                                                                                                                                                                                      |
 | `GITHUB_HEAD_REF`    | Only set for pull request events. The name of the head branch.                                                                                                                                                                                                                                                                                                                         |
 | `GITHUB_BASE_REF`    | Only set for pull request events. The name of the base branch.                                                                                                                                                                                                                                                                                                                         |
-| `GITHUB_SERVER_URL`  | Returns the URL of the {% data variables.product.product_name %} server. For example: `https://github.com`.                                                                                                                                                                                                                                                                            |
-| `GITHUB_API_URL`     | Gibt die API-URL zurück. For example: `https://api.github.com`.                                                                                                                                                                                                                                                                                                                        |
-| `GITHUB_GRAPHQL_URL` | Gibt die GraphQL-API-URL zurück. For example: `https://api.github.com/graphql`.                                                                                                                                                                                                                                                                                                        |
+| `GITHUB_SERVER_URL`  | Returns the URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`.                                                                                                                                                                                                                                              |
+| `GITHUB_API_URL`     | Gibt die API-URL zurück. For example: `{% data variables.product.api_url_code %}`.                                                                                                                                                                                                                                                                                                     |
+| `GITHUB_GRAPHQL_URL` | Gibt die GraphQL-API-URL zurück. For example: `{% data variables.product.graphql_url_code %}`.                                                                                                                                                                                                                                                                                         |
 
 {% tip %}
 
@@ -84,10 +85,6 @@ Es wird dringend empfohlen, dass Aktionen Umgebungsvariablen verwenden, um auf d
 
 ### Namens-Konventionen für Umgebungsvariablen
 
-{% note %}
-
-**Hinweis:** In {% data variables.product.prodname_dotcom %} ist das Umgebungsvariablen-Präfix `GITHUB_` für den internen Gebrauch durch {% data variables.product.prodname_dotcom %} reserviert. Wenn Sie eine Umgebungsvariable oder ein Geheimnis mit dem Präfix `GITHUB_` anlegen, tritt ein Fehler auf.
-
-{% endnote %}
+When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
 
 Alle neuen Umgebungsvariablen, die auf einen Speicherort im Dateisystem verweisen, müssen das Suffix `_PATH` erhalten. Die Standardvariablen `HOME` und `GITHUB_WORKSPACE` sind von dieser Konvention ausgenommen, da die Bezeichnungen „home“ und „workspace“ bereits einen Speicherort implizieren.
diff --git a/translations/de-DE/content/actions/reference/environments.md b/translations/de-DE/content/actions/reference/environments.md
index d0e0ca0360..c3579762aa 100644
--- a/translations/de-DE/content/actions/reference/environments.md
+++ b/translations/de-DE/content/actions/reference/environments.md
@@ -48,6 +48,12 @@ Use deployment branches to restrict which branches can deploy to the environment
 
 Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 
+{% note %}
+
+**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level as security as repository and organization secrets. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+{% endnote %}
+
 ### Creating an environment
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -71,6 +77,9 @@ For more information on syntax to reference environments in workflows, see "[Wor
 
 When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
+### Using concurrency to serialize deployments in an environment
+You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. Weitere Informationen findest Du unter „[Workflow-Syntax für GitHub-Aktionen](/actions/reference/workflow-syntax-for-github-actions#concurrency)."
+
 ### Deleting an environment
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -80,7 +89,7 @@ Deleting an environment will delete all secrets and protection rules associated
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
+1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
 2. Click **I understand, delete this environment**.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
diff --git a/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md b/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md
index 5f147d1d44..c336253afb 100644
--- a/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md
@@ -19,7 +19,7 @@ versions:
 
 ### Configuring workflow events
 
-You can configure workflows to run for one or more events using the `on` workflow syntax. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)."
+You can configure workflows to run for one or more events using the `on` workflow syntax. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)“.
 
 {% data reusables.github-actions.actions-on-examples %}
 
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        echo "- in{{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          echo "- in{{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ Führt den Workflow aus, wenn das Ereignis `check_run` eintritt. {% data reusabl
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Nutzlast des Webhook-Ereignisses                   | Aktivitätstypen                                                                              | `GITHUB_SHA`                      | `GITHUB_REF`    |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------- | --------------- |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | Letzter Commit im Standard-Branch | Standard-Branch |
+| Nutzlast des Webhook-Ereignisses                   | Aktivitätstypen                                               | `GITHUB_SHA`                      | `GITHUB_REF`    |
+| -------------------------------------------------- | ------------------------------------------------------------- | --------------------------------- | --------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | Letzter Commit im Standard-Branch | Standard-Branch |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-Sie können einen Workflow beispielsweise ausführen, wenn ein Prüflauf erneut angefordert wurde (`rerequested`) oder eine Aktion angefordert hat (`requested_action`).
+For example, you can run a workflow when a check run has been `rerequested` or `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ Sie können einen Workflow beispielsweise ausführen, wenn ein Projektticket ge
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**Note:** The `prereleased` type will not trigger for pre-releases published from draft releases, but the `published` type will trigger. If you want a workflow to run when stable *and* pre-releases publish, subscribe to `published` instead of `released` and `prereleased`.
+
+{% endnote %}
+
 #### `Status`
 
 Führt den Workflow aus, wenn sich der Status eines Git-Commit ändert, wodurch das Ereignis `status` ausgelöst wird. For information about the REST API, see [Statuses](/rest/reference/repos#statuses).
diff --git a/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md b/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md
index 3eaee99a29..f02f8e1967 100644
--- a/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/de-DE/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### Adding a system path
diff --git a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md
index b814f27398..fec99e011d 100644
--- a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -110,8 +110,8 @@ Der folgende Workflow wird bei Push-Vorgängen an `releases/10` oder `releases/b
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
@@ -128,7 +128,7 @@ When all the path names match patterns in `paths-ignore`, the workflow will not
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
 #### Beispiel mit eingeschlossenen Pfaden
@@ -139,7 +139,7 @@ Wenn mindestens ein Pfad zu einem Muster im Filter `paths` passt, wird der Workf
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
 #### Pfade ausschließen
@@ -160,8 +160,8 @@ Dieses Beispiel wird stets ausgeführt, wenn das `push`-Ereignis eine Datei im V
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
 #### Git-Diff-Vergleiche
@@ -187,6 +187,32 @@ Weitere Informationen findest Du unter „[Informationen zum Vergleich von Branc
 
 Weitere Informationen zur Cron-Syntax findest Du unter „[Ereignisse, die Workflows auslösen](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)“.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify.  For more information, see [`jobs.<job_id>.permissions`](#jobsjob_idpermissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Beispiel
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will apply to all jobs in the workflow. All permissions are granted read access.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
+
 ### `env`
 
 A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
@@ -221,6 +247,18 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the `github` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+You can also specify `concurrency` at the job level. For more information, see [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs`
 
 Ein Workflow-Lauf besteht aus mindestens einem Job. Die Aufträge werden standardmäßig parallel ausgeführt. Sollen Jobs sequenziell ausgeführt werden, kannst Du mit dem Schlüsselwort `jobs.<job_id>.needs` eine Abhängigkeit von anderen Jobs definieren.
@@ -339,6 +377,34 @@ runs-on: [self-hosted, linux]
 
 Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)“ und „[Selbst-gehostete Runner in einem Workflow verwenden](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)“.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](#permissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Beispiel
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access.
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 ### `jobs.<job_id>.environment`
 
@@ -347,10 +413,11 @@ The environment that the job references. All environment protection rules must p
 You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
 
 ##### Example using a single environment name
-
+{% raw %}
 ```yaml
 environment: staging_environment
 ```
+{% endraw %}
 
 ##### Example using environment name and URL
 
@@ -372,6 +439,25 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other.
+
+{% endnote %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
 Eine `map` der Ausgaben eines Jobs. Ausgaben eines Jobs stehen allen nachgelagerten Jobs zur Verfügung, die von diesem Job abhängen. Weitere Informationen zur Definition von Abhängigkeiten zwischen Jobs findest Du unter [`Jobs.<job_id>.needs`](#jobsjob_idneeds).
@@ -387,20 +473,20 @@ Um Jobausgaben in einem abhängigen Job zu verwenden, kannst Du den Kontext `nee
 jobs:
   job1:
     runs-on: ubuntu-latest
-    # Die Ausgabe eines Schrittes der Ausgabe eines Jobs zuordnen
+    # Map a step output to a job output
     outputs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
@@ -470,14 +556,14 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
@@ -609,11 +695,11 @@ jobs:
 ```
 
 {% if currentVersion == "free-pro-team@latest" %}
-##### Example using the {% data variables.product.prodname_github_container_registry %}
+##### Example using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in the {% data variables.product.prodname_github_container_registry %}.
+A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
 
 ```yaml
 jobs:
@@ -639,7 +725,9 @@ jobs:
 
 #### Example using action inside a different private repository than the workflow
 
-Your workflow must checkout the private repository and reference the action locally.
+Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
 
 {% raw %}
 ```yaml
@@ -651,7 +739,7 @@ jobs:
         with:
           repository: octocat/my-private-repo
           ref: v1.0
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
           path: ./.github/actions/my-private-repo
       - name: Run my action
         uses: ./.github/actions/my-private-repo/my-action
@@ -692,7 +780,7 @@ Mit dem Schlüsselwort`working-directory` gibst Du das Arbeitsverzeichnis an, in
 
 #### Bestimmte Shell verwenden
 
-Du kannst die Einstellungen zur Standard-Shell im Betriebssystem des Läufers mit dem Schlüsselwort `shell` überschreiben. Sie können die integrierten `shell`-Stichwörter verwenden oder eine benutzerdefinierte Reihe von Shell-Optionen definieren.
+Du kannst die Einstellungen zur Standard-Shell im Betriebssystem des Läufers mit dem Schlüsselwort `shell` überschreiben. Du kannst die integrierten `shell`-Schlüsselwörter verwenden oder eine benutzerdefinierte Menge von Shell-Optionen festlegen.
 
 | Unterstützte Plattform | Parameter `shell` | Beschreibung                                                                                                                                                                                                                                                                                               | Intern ausgeführter Befehl                      |
 | ---------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
@@ -753,7 +841,7 @@ steps:
 
 #### Benutzerdefinierte Shell
 
-Mit `command […options] {0} [..more_options]` können Sie einen Vorlagen-String für den `shell`-Wert festlegen. {% data variables.product.prodname_dotcom %} interpretiert das erste Wort im String, nach dem ein „Whitespace“ (Zwischenraum-Zeichen) steht, als Befehl, und der Dateiname für das temporäre Skript wird in `{0}` eingefügt.
+Mit `command […options] {0} [..more_options]` kannst Du einen Vorlagen-String für den Wert `shell` festlegen. {% data variables.product.prodname_dotcom %} interpretiert das erste Wort im String, nach dem ein Leerzeichen steht, als Befehl, und der Dateiname für das temporäre Skript wird in `{0}` eingefügt.
 
 Ein Beispiel:
 
@@ -775,7 +863,7 @@ For information about the software included on GitHub-hosted runners, see "[Spec
 
 #### Exit-Codes und Voreinstellung für Fehleraktionen
 
-Für integrierte Shell-Schlüsselwörter gelten die folgenden Standards, die durch auf {% data variables.product.prodname_dotcom %} gehostete Runner ausgeführt werden. Beachte diese Richtlinien beim Ausführen von Shell-Skripts.
+Für integrierte Shell-Stichwörter gelten die folgenden Standards, die durch auf {% data variables.product.prodname_dotcom %} gehostete Runner ausgeführt werden. Beachte diese Richtlinien beim Ausführen von Shell-Skripts.
 
 - `bash`/`sh`:
   - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. Dies ist außerdem der Standard, wenn Du eine Option für eine Plattform außer Windows angibst.
@@ -852,7 +940,7 @@ The `entrypoint` keyword is meant to be used with Docker container actions, but
 
 ### `jobs.<job_id>.steps[*].env`
 
-Legt Umgebungsvariablen für Schritte fest, die in der Runner-Umgebung verwendet werden sollen. Darüber hinaus können Sie Umgebungsvariablen für den gesamten Workflow oder für einen Auftrag festlegen. Weitere Informationen finden Sie unter [`env`](#env) und [`jobs.<job_id>.env`](#jobsjob_idenv).
+Legt Umgebungsvariablen für Schritte fest, die in der Runner-Umgebung verwendet werden sollen. Darüber hinaus kannst Du Umgebungsvariablen für den gesamten Workflow oder für einen Auftrag festlegen. Weitere Informationen findest Du unter [`env`](#env) und [`jobs.<job_id>.env`](#jobsjob_idenv).
 
 {% data reusables.repositories.actions-env-var-note %}
 
@@ -899,7 +987,7 @@ Die Reihenfolge, in der Du eine `Matrix` definierst, ist wichtig. Die erste Opti
 
 #### Beispiel für die Ausführung mit mehreren Versionen von Node.js
 
-Zum Erstellen einer Matrix geben Sie ein Array für die Konfigurationsoptionen an. Wenn der Runner beispielsweise die Node.js-Versionen 6, 8 und 10 unterstützt, kannst Du ein Array dieser Versionen in der `matrix` festlegen.
+Zum Erstellen einer Matrix geben Sie ein Array für die Konfigurationsoptionen an. Wenn der Runner beispielsweise die Node.js-Versionen 10, 12 und 14 unterstützt, kannst Du ein Array dieser Versionen in der `matrix` festlegen.
 
 Dieses Beispiel erzeugt eine Matrix von drei Jobs, indem der Schlüssel `node` auf ein Array von drei Node.js-Versionen gesetzt wird. Um die Matrix zu verwenden, setzt das Beispiel die Kontexteigenschaft `matrix.node` als Wert des Eingabeparameters `node-version` der Aktion `setup-node`. Daher werden drei Jobs ausgeführt, die jeweils eine andere Version von Node.js verwenden.
 
@@ -907,12 +995,12 @@ Dieses Beispiel erzeugt eine Matrix von drei Jobs, indem der Schlüssel `node` a
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
-  # Konfiguriert die auf GitHub-gehosteten Runnern genutzte Node-Version
-  - uses: actions/setup-node@v1
+  # Configures the node version used on GitHub-hosted runners
+  - uses: actions/setup-node@v2
     with:
-      # Die zu konfigurierenden Version von Node.js
+      # The Node.js version to configure
       node-version: ${{ matrix.node }}
 ```
 {% endraw %}
@@ -933,10 +1021,10 @@ Du kannst eine Matrix erstellen, um Workflows auf mehreren Runner-Betriebssystem
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
@@ -948,7 +1036,7 @@ steps:
 
 #### Beispiel mit kombinierten zusätzlichen Werten
 
-Sie können zusätzliche Konfigurationsoptionen hinzufügen, um einen bereits vorhandenen Matrixauftrag zu erstellen. Wenn Du beispielsweise eine bestimmte Version von `npm` verwenden willst, wenn der Auftrag mit `windows-latest` und Version 4 von `node` ausgeführt wird, kannst Du `include` verwenden, um diese zusätzliche Option anzugeben.
+Zu einem bereits vorhandenen Job mit Buildmatrix kannst Du weitere Konfigurationsoptionen hinzufügen. Wenn Du beispielsweise eine bestimmte Version von `npm` verwenden willst, wenn der Auftrag mit `windows-latest` und Version 8 von `node` ausgeführt wird, kannst Du `include` verwenden, um diese zusätzliche Option anzugeben.
 
 {% raw %}
 ```yaml
@@ -956,29 +1044,29 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # bezieht eine neue Variable npm mit dem Wert 2 ein
-      # und zwar fuer das zum Betriebssystem und zur Version passende Matrix-Bein
+      # includes a new variable of npm with a value of 6
+      # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
 #### Beispiel zum Einbeziehen neuer Kombinationen
 
-Du kannst `include` verwenden, um neue Jobs zu einer Build-Matrix hinzuzufügen. Alle Include-Konfigurationen, die nicht passen, werden zur Matrix hinzugefügt. Wenn Du beispielsweise `node` Version 12 verwenden willst, um auf mehreren Betriebssystemen zu bauen, aber Du willst einen zusätzlichen experimentellen Job mit Node Version 13 auf Ubuntu, kannst Du `include` verwenden, um diesen zusätzlichen Job anzugeben.
+Du kannst `include` verwenden, um neue Jobs zu einer Build-Matrix hinzuzufügen. Alle Include-Konfigurationen, die nicht passen, werden zur Matrix hinzugefügt. Wenn Du beispielsweise `node` Version 14 verwenden willst, um auf mehreren Betriebssystemen zu bauen, aber Du willst einen zusätzlichen experimentellen Job mit Node Version 15 auf Ubuntu, kannst Du `include` verwenden, um diesen zusätzlichen Job anzugeben.
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -986,7 +1074,7 @@ strategy:
 
 #### Beispiel zum Ausschließen von Konfigurationen aus einer Matrix
 
-Mit der Option `exclude` können Sie bestimmte in der Build-Matrix definierte Konfigurationen entfernen. Durch die Verwendung von `exclude` wird ein durch die Build-Matrix definierter Auftrag entfernt. Die Anzahl der Aufträge ist das Kreuzprodukt der Anzahl der Betriebssysteme (`os`), die in den von Ihnen bereitgestellten Arrays enthalten sind, abzüglich etwaiger Subtraktionen (`exclude`).
+Mit der Option `exclude` kannst Du bestimmte in der Build-Matrix definierte Konfigurationen entfernen. Durch die Verwendung von `exclude` wird ein durch die Build-Matrix definierter Job entfernt. Die Anzahl der Jobs ist das Kreuzprodukt der Anzahl der Betriebssysteme (`os`), die in den von Dir bereitgestellten Arrays enthalten sind, abzüglich etwaiger Subtraktionen (`exclude`).
 
 {% raw %}
 ```yaml
@@ -994,11 +1082,11 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # Schliesst Node 4 auf macOS aus
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
@@ -1016,7 +1104,7 @@ You can add custom environment variables for each test combination by using the
 
 ### `jobs.<job_id>.strategy.fail-fast`
 
-Wenn diese Option auf `true` gesetzt ist, bricht {% data variables.product.prodname_dotcom %} alle laufenden Jobs ab, sobald ein Job der `matrix` fehlschlägt. Standard: `true`
+Wenn diese Option auf `true` gesetzt ist, bricht {% data variables.product.prodname_dotcom %} alle laufenden Aufträge ab, sobald ein `matrix`-Auftrag fehlschlägt. Standard: `true`
 
 ### `jobs.<job_id>.strategy.max-parallel`
 
@@ -1033,7 +1121,7 @@ Verhindert, dass ein Workflow scheitert, wenn ein Job scheitert. Setze es auf `t
 
 #### Beispiel zum Verhindern, dass ein bestimmter scheiternder Job in der Matrix einen Workflow-Lauf scheitern lässt
 
-Du kannst zulassen, dass bestimmte Jobs in einer Jobmatrix scheitert, ohne dass der Workflow-Lauf scheitert. Das gilt beispielsweise, wenn Du nur einem experimentellen Job, bei dem `node` auf `13` gesetzt wurde, das Scheitern erlauben willst, ohne dass dadurch der Workflow-Lauf scheitert.
+Du kannst zulassen, dass bestimmte Jobs in einer Jobmatrix scheitert, ohne dass der Workflow-Lauf scheitert. Das gilt beispielsweise, wenn Du nur einem experimentellen Job, bei dem `node` auf `15` gesetzt wurde, das Scheitern erlauben willst, ohne dass dadurch der Workflow-Lauf scheitert.
 
 {% raw %}
 ```yaml
@@ -1042,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -1056,7 +1144,7 @@ strategy:
 
 Container, in dem alle Schritte eines Auftrags ausgeführt werden, für die kein Container explizit angegeben ist. Wenn ein Schritt sowohl Skript- als auch Container-Aktionen umfasst, werden die Container-Aktionen als nebengeordnete Container in demselben Netzwerk mit denselben Volume-Mounts ausgeführt.
 
-Wenn Sie keinen `container` festlegen, werden alle Schritte direkt auf dem Host ausgeführt, der mit `runs-on` angegeben wird, außer wenn ein Schritt auf eine Aktion verweist, die für die Ausführung in einem Container konfiguriert ist.
+Wenn Du keinen `container` festlegst, werden alle Schritte direkt auf dem Host ausgeführt, der mit `runs-on` angegeben ist, außer wenn ein Schritt auf eine Aktion verweist, die für die Ausführung in einem Container konfiguriert ist.
 
 #### Beispiel
 
@@ -1064,7 +1152,7 @@ Wenn Sie keinen `container` festlegen, werden alle Schritte direkt auf dem Host
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -1079,7 +1167,7 @@ Wenn Sie nur ein Container-Image angeben, können Sie das Stichwort `image` wegl
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
@@ -1181,7 +1269,7 @@ Docker-Image, das beim Ausführen der Aktion als Dienstcontainer herangezogen wi
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
@@ -1228,7 +1316,7 @@ Zusätzliche Optionen für die Docker-Containerressource. Eine Liste der Optione
 
 ### Merkzettel zu Filtermustern
 
-Die Pfad-, Branch- und Tag-Filter können bestimmte Sonderzeichen umfassen.
+In Pfad-, Branch- und Tag-Filtern kannst Du Sonderzeichen benutzen.
 
 - `*`Steht für kein Zeichen oder mehrere Zeichen, nicht jedoch für den Schrägstrich (`/`). Zum Beispiel passt `Okto*` auf `Oktocat`.
 - `**`: Steht für kein Zeichen oder mehrere beliebige Zeichen.
@@ -1237,7 +1325,7 @@ Die Pfad-, Branch- und Tag-Filter können bestimmte Sonderzeichen umfassen.
 - `[]` Steht für irgend ein Zeichen, das in den Klammern aufgelistet ist oder das in einen in den Klammern enthalten Bereich fällt. Mögliche Bereiche sind ausschließlich `a-z`, `A-Z` und `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. Zum Beispiel passt `[CB]at` sowohl zu `Cat` als auch zu `Bat` und `[1-2]00` passt sowohl zu `100` als auch zu `200`.
 - `!`: Am Anfang eines Musters stehend negiert es das Muster in sein Gegenteil. Es hat keine besondere Bedeutung, wenn es nicht das erste Zeichen ist.
 
-Die Zeichen `*`, `[` und `!` sind Sonderzeichen in YAML. Wenn ein Muster mit `*`, `[` oder `!` beginnen soll, schließen Sie das Muster in Anführungszeichen ein.
+Die Zeichen `*`, `[` und `!` sind Sonderzeichen in YAML. Wenn ein Muster mit `*`, `[` oder `!` beginnen soll, schließe das Muster in Anführungszeichen ein.
 
 ```yaml
 # Gueltig
@@ -1248,7 +1336,7 @@ Die Zeichen `*`, `[` und `!` sind Sonderzeichen in YAML. Wenn ein Muster mit `*`
 - **/README.md
 ```
 
-Weitere Informationen zur Syntax für Branch-, Tag- und Pfadfilter finden Sie unter „[`on.<push|pull_request>.<branches|tags>`](#onpushpull_requestbranchestags)“ und „[`on.<push|pull_request>.paths`](#onpushpull_requestpaths)“.
+Weitere Informationen zur Syntax für Branch-, Tag- und Pfadfilter findest Du unter „[`on.<push|pull_request>.<branches|tags>`](#onpushpull_requestbranchestags)“ und „[`on.<push|pull_request>.paths`](#onpushpull_requestpaths)“.
 
 #### Muster für den Abgleich von Branches und Tags
 
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 394b6a1e75..d4ac787c1e 100644
--- a/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ For the overall list of included tools for each runner operating system, see the
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ We recommend using actions to interact with the software installed on runners. T
 
 Wenn Sie ein bestimmtes Tool anfordern möchten, öffnen Sie bitte einen Issue unter [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners.
 
+#### Installing additional software
+
+You can install additional software on {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Customizing GitHub-hosted runners](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
 ### IP addresses
 
 {% note %}
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..fa8b92c9d6
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Customizing GitHub-hosted runners
+intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow.
+
+To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+
+This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner.
+
+### Installing software on Ubuntu runners
+
+The following example demonstrates how to install an `apt` package as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**Note:** Always run `sudo apt-get update` before installing a package. In case the `apt` index is stale, this command fetches and re-indexes any available packages, which helps prevent package installation failures.
+
+{% endnote %}
+
+### Installing software on macOS runners
+
+The following example demonstrates how to install Brew packages and casks as part of a job.
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### Installing software on Windows runners
+
+The following example demonstrates how to use [Chocolatey](https://community.chocolatey.org/packages) to install the {% data variables.product.prodname_dotcom %} CLI as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/index.md b/translations/de-DE/content/actions/using-github-hosted-runners/index.md
index 681269a253..fb91ee9e64 100644
--- a/translations/de-DE/content/actions/using-github-hosted-runners/index.md
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% link_in_list /about-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/de-DE/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/de-DE/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..9793d2f7e2
--- /dev/null
+++ b/translations/de-DE/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: About licensing for GitHub Advanced Security
+intro: 'You need a license to use {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### About licensing for {% data variables.product.prodname_GH_advanced_security %}
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% data reusables.advanced-security.license-overview %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for {% data variables.product.product_name %}, contact {% data variables.contact.contact_enterprise_sales %}. To enable {% data variables.product.prodname_GH_advanced_security %}, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your appliance](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### Managing your license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+
+For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+
+### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..ccd323bfed
--- /dev/null
+++ b/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: Configuring code scanning for your appliance
+shortTitle: Configuring code scanning
+intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### Informationen zu {% data variables.product.prodname_code_scanning %}
+
+With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors.
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+### Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
+
+#### Setting up a self-hosted runner
+
+{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions.
+
+#### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+
+You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
+
+#### Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access
+If the server on which you are running {% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} action sync tool to copy the {% data variables.product.prodname_codeql %} analysis bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/).
+
+If you set up the {% data variables.product.prodname_codeql %} action sync tool, you can use it to sync the latest releases of the {% data variables.product.prodname_codeql %} action and associated {% data variables.product.prodname_codeql %} analysis bundle. These are compatible with {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways.
+
+- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)."
+- If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer.
+- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases.
+{% endif %}
+
+#### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}
+1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)."
+2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
+3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
+4. Add a self-hosted runner to your repository, organization, or enterprise account. Weitere Informationen findest Du unter "[selbst-gehostete Runner hinzufügen](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}
+If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}.
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
diff --git a/translations/de-DE/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/de-DE/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..1c16b0dc7e
--- /dev/null
+++ b/translations/de-DE/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: Configuring secret scanning for your appliance
+shortTitle: Configuring secret scanning
+intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### Informationen zu {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+
+### Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+
+- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}.
+
+- A license for {% data variables.product.prodname_GH_advanced_security %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### Checking support for the SSSE3 flag on your vCPUs
+
+The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance.
+
+1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. Weitere Informationen findest Du unter "[Auf die administrative Shell (SSH) zugreifen](/admin/configuration/accessing-the-administrative-shell-ssh)."
+2. Enter the following command:
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs.
+
+#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### {% data variables.product.prodname_secret_scanning %} aktivieren
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. ![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### Disabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_secret_scanning_caps %}**. ![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..af865445eb
--- /dev/null
+++ b/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% if currentVersion == "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+{% endif %}
+
+### Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} For information about licensing, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
+2. Upload the new license to {% data variables.product.product_location %}. For more information, see "[Managing your GitHub Enterprise license](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Under "{% data variables.product.prodname_advanced_security %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+
+### Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} via the administrative shell (SSH)
+
+You can enable or disable features programmatically on {% data variables.product.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)."
+
+For example, you can enable {% data variables.product.prodname_code_scanning %} with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
+
+1. Stellen Sie eine SSH-Verbindung zu {% data variables.product.product_location %} her.
+1. Enable {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. Optionally, disable {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. Apply the configuration.
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}To enable and disable {% data variables.product.prodname_secret_scanning %} in the same way, set: `ghe-config app.secret-scanning.enabled` true or false and apply the configuration.{% endif %}
diff --git a/translations/de-DE/content/admin/advanced-security/index.md b/translations/de-DE/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..5c6025b2cc
--- /dev/null
+++ b/translations/de-DE/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing GitHub Advanced Security for your enterprise
+shortTitle: Managing GitHub Advanced Security
+intro: 'You can configure {% data variables.product.prodname_advanced_security %} and manage use by your enterprise to suit your organization''s needs.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### Inhaltsverzeichnis
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/de-DE/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/de-DE/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..670d420947
--- /dev/null
+++ b/translations/de-DE/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,23 @@
+---
+title: Viewing your GitHub Advanced Security usage
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."
+
+### Viewing license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+You can check how many seats your license includes and how many seats are currently in use.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[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/de-DE/content/admin/all-releases.md b/translations/de-DE/content/admin/all-releases.md
new file mode 100644
index 0000000000..4205448568
--- /dev/null
+++ b/translations/de-DE/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Enterprise Server releases
+intro: 'Documentation for the currently supported and previously deprecated versions of {{ site.data.variables.product.prodname_ghe_server }}.'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## Currently supported
+
+See [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) for information about the latest release.
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## Deprecated
+
+Documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## Deprecated developer documentation
+
+Developer documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/de-DE/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/de-DE/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index 9e477b1438..7100920319 100644
--- a/translations/de-DE/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: 'You can use {% if enterpriseServerVersions contains currentVersion %}{%
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### About identity and access management for your enterprise
diff --git a/translations/de-DE/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/de-DE/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index fab9608054..58a9d6d1a1 100644
--- a/translations/de-DE/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/de-DE/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### Informationen zur integrierten Authentifizierung für Benutzer außerhalb Ihres Identity Providers
diff --git a/translations/de-DE/content/admin/authentication/changing-authentication-methods.md b/translations/de-DE/content/admin/authentication/changing-authentication-methods.md
index 683e20086d..6c01eb269b 100644
--- a/translations/de-DE/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/de-DE/content/admin/authentication/changing-authentication-methods.md
@@ -6,13 +6,17 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Wenn Sie die Authentifizierungsmethode ändern, werden die Benutzerkonten auf {% data variables.product.product_location %} beibehalten, und Benutzer melden sich weiterhin beim selben Konto an, sofern ihr Benutzername nicht geändert wird.
 
-Wenn bei der neuen Authentifizierungsmethode Benutzernamen geändert werden, werden neue Konten erstellt. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user).
+Wenn bei der neuen Authentifizierungsmethode Benutzernamen geändert werden, werden neue Konten erstellt. Als Administrator können Sie Benutzer über die Einstellungen des Websiteadministrators oder mithilfe der [API für die Benutzerverwaltung](/rest/reference/enterprise-admin#update-the-username-for-a-user) umbenennen.
 
 Zudem sollten Sie die folgenden Issues in Betracht ziehen:
 
diff --git a/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 57ebe58d1a..df81e4d80d 100644
--- a/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About authentication and user provisioning with Azure AD
diff --git a/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index b4b7e7fcc3..f9e15b2747 100644
--- a/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Informationen zu SAML SSO
diff --git a/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index 693d182b9b..d2ceb08dab 100644
--- a/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About user provisioning for your enterprise
diff --git a/translations/de-DE/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/de-DE/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index 40fcbfa6b7..962e082545 100644
--- a/translations/de-DE/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/de-DE/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: 'Wenn Sie die integrierte Authentifizierung verwenden, können Sie nicht authentifizierte Personen mittels Blockierung daran hindern, ein Konto zu erstellen.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/authentication/using-built-in-authentication.md b/translations/de-DE/content/admin/authentication/using-built-in-authentication.md
index 0e0372f609..2d9cf31c5f 100644
--- a/translations/de-DE/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/de-DE/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Du kannst frei definierbare Nachrichten erstellen, die Benutzern auf den Anmelde- und Abmeldeseiten angezeigt werden. Weitere Informationen finden Sie unter „[Benutzermeldungen auf Ihrer Instanz anpassen](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)“.
diff --git a/translations/de-DE/content/admin/authentication/using-cas.md b/translations/de-DE/content/admin/authentication/using-cas.md
index e2af25021d..adf9310e5a 100644
--- a/translations/de-DE/content/admin/authentication/using-cas.md
+++ b/translations/de-DE/content/admin/authentication/using-cas.md
@@ -5,11 +5,16 @@ redirect_from:
   - /enterprise/admin/articles/about-cas-authentication/
   - /enterprise/admin/user-management/using-cas
   - /enterprise/admin/authentication/using-cas
-intro: 'CAS ist ein Single Sign-On-Protokoll (SSO) für mehrere Webanwendungen. A CAS user account does not take up a {% if currentVersion ver_gt "enterprise-server@2.16" %}user license{% else %}seat{% endif %} until the user signs in.'
+intro: 'CAS ist ein Single Sign-On-Protokoll (SSO) für mehrere Webanwendungen. Ein CAS-Benutzerkonto übernimmt eine(n) {% if currentVersion ver_gt "enterprise-server@2.16" %}Benutzerlizenz{% else %}Benutzer{% endif %} erst nach Anmeldung des Benutzers.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/de-DE/content/admin/authentication/using-ldap.md b/translations/de-DE/content/admin/authentication/using-ldap.md
index 323dcf43ae..04cf71310b 100644
--- a/translations/de-DE/content/admin/authentication/using-ldap.md
+++ b/translations/de-DE/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: 'Mithilfe von LDAP können Sie {% data variables.product.prodname_ghe_server %} bei Ihren vorhandenen Konten authentifizieren und den Zugriff auf Repositorys zentral verwalten. LDAP ist ein beliebtes Anwendungsprotokoll für den Zugriff auf und die Verwaltung von Verzeichnisinformationsdiensten. Zudem ist es eines der gängigsten Protokolle zur Integration von Drittanbietersoftware in große Benutzerverzeichnisse von Unternehmen.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/de-DE/content/admin/authentication/using-saml.md b/translations/de-DE/content/admin/authentication/using-saml.md
index 416b04e4f1..3a6579644c 100644
--- a/translations/de-DE/content/admin/authentication/using-saml.md
+++ b/translations/de-DE/content/admin/authentication/using-saml.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'SAML ist ein XML-basierter Standard für die Authentifizierung und Autorisierung. {% data variables.product.prodname_ghe_server %} kann als ein Service Provider (SP) mit Ihrem internen SAML Identity Provider (IdP) funktionieren.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/de-DE/content/admin/configuration/about-enterprise-configuration.md b/translations/de-DE/content/admin/configuration/about-enterprise-configuration.md
index 01c0c16a1c..c3c5037850 100644
--- a/translations/de-DE/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/de-DE/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: 'You can use the site admin dashboard{% if enterpriseServerVersions conta
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 The first time you access your enterprise, you will complete an initial configuration to get
-{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an idP, authenticating with SAML SSO, and configuring policies for repositories and organizations in your enterprise. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-
-For users to receive any emails from {% data variables.product.product_name %} after the initial configuration, you must ask {% data variables.contact.github_support %} to configure outbound email support with your SMTP server. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)."
+{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an identity provider (IdP), authenticating with SAML SSO, configuring policies for repositories and organizations in your enterprise, and configuring SMTP for outbound email. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
 
 Later, you can use the site admin dashboard and enterprise settings to further configure your enterprise, manage users, organizations and repositories, and set policies that reduce risk and increase quality.
 
diff --git a/translations/de-DE/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/de-DE/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index e14faa2bb8..7e7ad7b31e 100644
--- a/translations/de-DE/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/de-DE/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### Informationen zum Verwaltungsshellzugriff
diff --git a/translations/de-DE/content/admin/configuration/accessing-the-management-console.md b/translations/de-DE/content/admin/configuration/accessing-the-management-console.md
index 1cb4b47a1a..b8a93a9f5d 100644
--- a/translations/de-DE/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/de-DE/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Informationen zur {% data variables.enterprise.management_console %}
diff --git a/translations/de-DE/content/admin/configuration/command-line-utilities.md b/translations/de-DE/content/admin/configuration/command-line-utilities.md
index f1fe01edcd..8b9f6bcf11 100644
--- a/translations/de-DE/content/admin/configuration/command-line-utilities.md
+++ b/translations/de-DE/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 Sie können diese Befehle überall in der VM ausführen, nachdem Sie sich als ein SSH-Administratorbenutzer angemeldet haben. Weitere Informationen finden Sie unter „[Auf die Verwaltungsshell (SSH) zugreifen](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)“.
@@ -483,15 +485,21 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 Um die vollständige Hook-Nutzlast, das Ergebnis und alle Ausnahmen für die Lieferung anzuzeigen:
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### Clustering
 
 #### ghe-cluster-status
 
-Mit diesem Dienstprogramm kannst Du den verteilten {% data variables.product.prodname_pages %} -Server verwalten.
+Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
 
 ```shell
 $ ghe-cluster-status
@@ -644,14 +652,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-Dieses Hilfsprogramm importiert von Team Foundation Version Control. Weitere Informationen findest Du unter „[Daten aus Versionskontroll-Systemen von Drittanbietern importieren](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)“.
+This utility imports from Team Foundation Version Control (TFVC). Weitere Informationen findest Du unter „[Daten aus Versionskontroll-Systemen von Drittanbietern importieren](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)“.
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-Dieses Dienstprogramm schreibt das importierte Repository erneut. Dies gibt Dir die Möglichkeit, Autoren umzubenennen, und erzeugt für Subversion und TFS auf Ordnern basierende Git-Branches. Weitere Informationen findest Du unter „[Daten aus Versionskontroll-Systemen von Drittanbietern importieren](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)“.
+Dieses Dienstprogramm schreibt das importierte Repository erneut. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. Weitere Informationen findest Du unter „[Daten aus Versionskontroll-Systemen von Drittanbietern importieren](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)“.
 ```shell
 git-import-rewrite
 ```
diff --git a/translations/de-DE/content/admin/configuration/configuring-a-hostname.md b/translations/de-DE/content/admin/configuration/configuring-a-hostname.md
index 6c16be3981..7a1060cc48 100644
--- a/translations/de-DE/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/de-DE/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 Wenn Sie einen Hostnamen konfigurieren, anstatt eine hartcodierte IP-Adresse zu verwenden, können Sie die physische Hardware ändern, auf der {% data variables.product.product_location %} ausgeführt wird, ohne dass sich dies auf die Benutzer oder auf die Clientsoftware auswirkt.
diff --git a/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 20ca9c6ba4..069e5602d1 100644
--- a/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/de-DE/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Wenn ein Proxyserver für {% data variables.product.product_location %} aktiviert wird, werden ausgehende Nachrichten, die von {% data variables.product.prodname_ghe_server %} gesendet wurden, zunächst über den Proxyserver gesendet, sofern der Zielhost nicht als HTTP-Proxyausschluss hinzugefügt wurde. Zu den Typen ausgehender Nachrichten zählen ausgehende Webhooks, das Hochladen von Bundles und das Abrufen von veralteten Avataren. Die URL des Proxyservers ist das Protokoll, die Domain oder IP-Adresse plus die Portnummer, also beispielsweise `http://127.0.0.1:8123`.
diff --git a/translations/de-DE/content/admin/configuration/configuring-applications.md b/translations/de-DE/content/admin/configuration/configuring-applications.md
index a9a093cb44..36e24e0d85 100644
--- a/translations/de-DE/content/admin/configuration/configuring-applications.md
+++ b/translations/de-DE/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Bildzwischenspeicherung anpassen
diff --git a/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md
index 02e3e230a8..cd296e160e 100644
--- a/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/de-DE/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: Backups auf Ihrer Appliance konfigurieren
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: 'Im Rahmen eines Disaster Recovery-Plans können Sie die Produktionsdaten auf {% data variables.product.product_location %} schützen, indem Sie automatisierte Backups konfigurieren.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### Informationen zu {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/de-DE/content/admin/configuration/configuring-built-in-firewall-rules.md
index 39eaf86f0f..2b537bb223 100644
--- a/translations/de-DE/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/de-DE/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Informationen zur Firewall der {% data variables.product.product_location %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index 4fa4fbf0f0..19c11b2328 100644
--- a/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: Configuring data encryption
 intro: 'For encryption at rest, you can provide your own encryption key to encrypt your data under your encryption policies.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 To provide a high level of security, {% data variables.product.product_name %} encrypts your data while at rest in the data centers and while your data is in transit between users' machines and the data centers.
 
-For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. After you've initialized your enterprise, you can choose to provide your own key instead. Your key should be a 2048 bit RSA private key in PEM format.
-
-The key that you provide is stored in a FIPS 140-2 compliant hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages.
-
-To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
-
-### Adding or updating an encryption key
-
-You can add a new encryption key as often as you need. When you add a new key, the old key is discarded. Your enterprise won't experience downtime when you update the key.
-
-Your 2048 bit RSA private key should be in PEM format, for example in a file called _private-key.pem_.
-
-   ```
-   -----BEGIN RSA PRIVATE KEY-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----END RSA PRIVATE KEY-----
-   ```
-
-1. To add your key, use the `PATCH /enterprise/encryption` endpoint, replacing *~/private-key.pem* with the path to your private key.
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. Optionally, check the status of the update operation.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### Disabling your encryption key
-
-To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
-
-1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
-
-### Weiterführende Informationen
-
-- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation 
+For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. 
diff --git a/translations/de-DE/content/admin/configuration/configuring-dns-nameservers.md b/translations/de-DE/content/admin/configuration/configuring-dns-nameservers.md
index cda99217e7..4890ad75db 100644
--- a/translations/de-DE/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/de-DE/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Die von Ihnen angegebenen Nameserver müssen den Hostnamen Ihrer {% data variables.product.product_location %} auflösen.
diff --git a/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md b/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md
index 306ae68cdc..c5378e4572 100644
--- a/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/de-DE/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index ab53b96870..bd8f3abf09 100644
--- a/translations/de-DE/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### Enabling public sites for {% data variables.product.prodname_pages %}
@@ -43,7 +45,7 @@ topics:
 
 {% if enterpriseServerVersions contains currentVersion %}
 If subdomain isolation is disabled for your enterprise, you should also disable
-{% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. For more information, see "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)."
+{% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. Weitere Informationen finden Sie unter „[Subdomain-Isolation aktivieren](/admin/configuration/enabling-subdomain-isolation)“.
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-rate-limits.md b/translations/de-DE/content/admin/configuration/configuring-rate-limits.md
index e7004fcd78..948753c53e 100644
--- a/translations/de-DE/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/de-DE/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### Begrenzungen für {% data variables.product.prodname_enterprise_api %} aktivieren
diff --git a/translations/de-DE/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/de-DE/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index ae1852eae4..91167271de 100644
--- a/translations/de-DE/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/de-DE/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-time-synchronization.md b/translations/de-DE/content/admin/configuration/configuring-time-synchronization.md
index d4ea8cea3e..6286046a9a 100644
--- a/translations/de-DE/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/de-DE/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### NTP-Standardserver ändern
diff --git a/translations/de-DE/content/admin/configuration/configuring-tls.md b/translations/de-DE/content/admin/configuration/configuring-tls.md
index aed9dd9998..f87d598c23 100644
--- a/translations/de-DE/content/admin/configuration/configuring-tls.md
+++ b/translations/de-DE/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Informationen zu Transport Layer Security
diff --git a/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 9b87c4bdd3..4709bf3a02 100644
--- a/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/de-DE/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### Informationen zu {% data variables.product.prodname_github_connect %}
diff --git a/translations/de-DE/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/de-DE/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index 31a0c18687..5ff476bf9f 100644
--- a/translations/de-DE/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/de-DE/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}
diff --git a/translations/de-DE/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/de-DE/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index 7636723a39..655cfe023d 100644
--- a/translations/de-DE/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/de-DE/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### Informationen zum Wartungsmodus
diff --git a/translations/de-DE/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/de-DE/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index fe162e0a45..06503ae70d 100644
--- a/translations/de-DE/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/de-DE/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### Informationen zur Lizenzsynchronisierung
diff --git a/translations/de-DE/content/admin/configuration/enabling-private-mode.md b/translations/de-DE/content/admin/configuration/enabling-private-mode.md
index 7e5f510c2c..be1115020e 100644
--- a/translations/de-DE/content/admin/configuration/enabling-private-mode.md
+++ b/translations/de-DE/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 Sie müssen den privaten Modus aktivieren, wenn {% data variables.product.product_location %} über das Internet öffentlich zugänglich ist. Im privaten Modus ist es Benutzern nicht möglich, Repositorys anonym über `git://` zu klonen. Wenn die integrierte Authentifizierung aktiviert ist, muss ein Administrator neue Benutzer einladen, um ein Konto auf der Instanz zu erstellen. Weitere Informationen finden Sie unter „[Integrierte Authentifizierung verwenden](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)“.
diff --git a/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md b/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md
index 5f821dd94f..0a440c9b5b 100644
--- a/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/de-DE/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Informationen zur Subdomain-Isolation
@@ -19,7 +24,7 @@ Bei aktivierter Subdomain-Isolation ersetzt {% data variables.product.prodname_g
 
 {% if currentVersion == "enterprise-server@2.22" %}
 To use Docker with
-{% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)."
+{% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/de-DE/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/de-DE/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index 68e11f8ec6..122d0b2a9d 100644
--- a/translations/de-DE/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/de-DE/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 Als Websiteadministrator können Sie zulassen, dass Endbenutzer anonymisierte Beitragsanzahlen für ihre Arbeit auf {% data variables.product.prodname_ghe_server %} an ihr {% data variables.product.prodname_dotcom_the_website %}-Beteiligungsdiagramm senden können.
diff --git a/translations/de-DE/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/de-DE/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 08e19d8f2f..a9f1ef6e43 100644
--- a/translations/de-DE/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/de-DE/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 Wenn Sie die gemeinsame Suche aktivieren, können Benutzer Suchergebnisse von öffentlichen und privaten Inhalten auf {% data variables.product.prodname_dotcom_the_website %} anzeigen, wenn sie auf {% data variables.product.product_location_enterprise %} suchen.
diff --git a/translations/de-DE/content/admin/configuration/index.md b/translations/de-DE/content/admin/configuration/index.md
index 3559044ebd..c45187865a 100644
--- a/translations/de-DE/content/admin/configuration/index.md
+++ b/translations/de-DE/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/de-DE/content/admin/configuration/initializing-github-ae.md b/translations/de-DE/content/admin/configuration/initializing-github-ae.md
index 11703fe41f..83fb560f48 100644
--- a/translations/de-DE/content/admin/configuration/initializing-github-ae.md
+++ b/translations/de-DE/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: Initializing GitHub AE
 intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### About initialization
@@ -79,11 +82,11 @@ Once this is initialized, you can reconfigure any settings after the initializat
 1. To the right of "Configure email settings", click **Configure**. !["Configure" button for email settings configuration](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. Wählen Sie **Enable email** (E-Mail aktivieren) aus. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Complete your email server settings:
-  - Geben Sie im Feld **Server address** (Serveradresse) die Adresse Ihres SMTP-Servers ein.
-  - Geben Sie im Feld **Port** den Port ein, der von Ihrem SMTP-Server zum Senden von E-Mails verwendet wird.
-  - Geben Sie im Feld **Domain** den Domain-Namen ein, der ggf. von Ihrem SMTP-Server mit einer HELO-Antwort gesendet wird.
-  - Wählen Sie im Dropdownmenü **Authentication** (Authentifizierung) den von Ihrem SMTP-Server verwendeten Verschlüsselungstyp aus.
-  - Geben Sie im Feld **No-reply email address** („no-reply“-E-Mail-Adresse) die E-Mail-Adresse ein, die für alle Benachrichtigungs-E-Mails in den Feldern „From“ (Von) und „To“ (An) verwendet werden soll.
+    - Geben Sie im Feld **Server address** (Serveradresse) die Adresse Ihres SMTP-Servers ein.
+    - Geben Sie im Feld **Port** den Port ein, der von Ihrem SMTP-Server zum Senden von E-Mails verwendet wird.
+    - Geben Sie im Feld **Domain** den Domain-Namen ein, der ggf. von Ihrem SMTP-Server mit einer HELO-Antwort gesendet wird.
+    - Wählen Sie im Dropdownmenü **Authentication** (Authentifizierung) den von Ihrem SMTP-Server verwendeten Verschlüsselungstyp aus.
+    - Geben Sie im Feld **No-reply email address** („no-reply“-E-Mail-Adresse) die E-Mail-Adresse ein, die für alle Benachrichtigungs-E-Mails in den Feldern „From“ (Von) und „To“ (An) verwendet werden soll.
 
 4. Wenn Sie alle eingehenden E-Mails verwerfen möchten, die an die „no-reply“-E-Mail-Adresse adressiert sind, sollten Sie **Discard email addressed to the no-reply email address** (An die „no-reply“-E-Mail-Adresse adressierte E-Mails verwerfen) aktivieren. !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. Click **Test email settings**. !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 6347133182..788a83c43a 100644
--- a/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: 'You can decide whether authenticated users can connect to {% data variab
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/de-DE/content/admin/configuration/network-ports.md b/translations/de-DE/content/admin/configuration/network-ports.md
index 8ee207e490..6351084dc4 100644
--- a/translations/de-DE/content/admin/configuration/network-ports.md
+++ b/translations/de-DE/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Öffnen Sie Netzwerkports anhand dessen, welche Netzwerkdienste Sie für Administratoren, Endbenutzer und für die E-Mail-Unterstützung bereitstellen müssen.'
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Verwaltungsports
diff --git a/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index f28a58775a..f3d0384e97 100644
--- a/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -4,6 +4,13 @@ shortTitle: Restricting network traffic
 intro: You can use an IP allow list to restrict access to your enterprise to connections from specified IP addresses.
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### About IP allow lists
diff --git a/translations/de-DE/content/admin/configuration/site-admin-dashboard.md b/translations/de-DE/content/admin/configuration/site-admin-dashboard.md
index 22790439d0..6bf0dce03f 100644
--- a/translations/de-DE/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/de-DE/content/admin/configuration/site-admin-dashboard.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 Klicken Sie in der oberen rechten Ecke einer beliebigen Seite auf {% octicon "rocket" aria-label="The rocket ship" %}, um auf das Dashboard zuzugreifen.![Rocket ship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/de-DE/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/de-DE/content/admin/configuration/troubleshooting-ssl-errors.md
index a8baeeeed4..a05ec7ed9c 100644
--- a/translations/de-DE/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/de-DE/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### Passphrase aus Ihrer Schlüsseldatei entfernen
diff --git a/translations/de-DE/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/de-DE/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index 972b3a7e79..f3f671971a 100644
--- a/translations/de-DE/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/de-DE/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/de-DE/content/admin/configuration/validating-your-domain-settings.md b/translations/de-DE/content/admin/configuration/validating-your-domain-settings.md
index 548b232333..f271f112d3 100644
--- a/translations/de-DE/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/de-DE/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/de-DE/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/de-DE/content/admin/enterprise-management/about-cluster-nodes.md b/translations/de-DE/content/admin/enterprise-management/about-cluster-nodes.md
index ee9d2a59f5..e092a5f549 100644
--- a/translations/de-DE/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/de-DE/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/enterprise-management/about-clustering.md b/translations/de-DE/content/admin/enterprise-management/about-clustering.md
index 9592ae6885..4e41717105 100644
--- a/translations/de-DE/content/admin/enterprise-management/about-clustering.md
+++ b/translations/de-DE/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/enterprise-management/about-geo-replication.md b/translations/de-DE/content/admin/enterprise-management/about-geo-replication.md
index 4000d043f9..2237fff408 100644
--- a/translations/de-DE/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/de-DE/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 Mehrere aktive Replikate können eine kürzere Entfernung zum nächstgelegenen Replikat ermöglichen. Beispielsweise kann eine Organisation mit Niederlassungen in San Francisco, New York und London die primäre Appliance in einem Rechenzentrum in der Nähe von New York und zwei Replikate in Rechenzentren nahe San Francisco und London betreiben. Mittels Geolocation-fähigem DNS können Benutzer an den nächstgelegenen verfügbaren Server weitergeleitet werden und schneller auf Repository-Daten zugreifen. Wenn die Appliance nahe New York als die primäre Instanz festgelegt wird, ist die Latenz zwischen den Hosts niedriger, als dies der Fall wäre, wenn die Appliance nahe San Francisco als die primäre Instanz festgelegt werden würde, deren Verbindung nach London wiederum eine höhere Latenz aufweist.
diff --git a/translations/de-DE/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/de-DE/content/admin/enterprise-management/about-high-availability-configuration.md
index 8a8a27706e..2665719b9d 100644
--- a/translations/de-DE/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/de-DE/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Beim Konfigurieren der Hochverfügbarkeit gibt es eine automatisierte Einrichtung einer unidirektionalen asynchronen Replikation sämtlicher Datenspeicher (Git-Repositorys, MySQL, Redis und ElasticSearch) von der primären zur Replikat-Appliance.
diff --git a/translations/de-DE/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/de-DE/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index dbf53cf1d7..85128a8e55 100644
--- a/translations/de-DE/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/de-DE/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Auf das Überwachungs-Dashboard zugreifen
diff --git a/translations/de-DE/content/admin/enterprise-management/cluster-network-configuration.md b/translations/de-DE/content/admin/enterprise-management/cluster-network-configuration.md
index 0d1ff509f2..5e1edde858 100644
--- a/translations/de-DE/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/de-DE/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### Grundlegendes zu Netzwerken
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md b/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md
index 902f0712a7..a83735fff6 100644
--- a/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Externen `collectd`-Server einrichten
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index ef559e7c97..aabff61c5a 100644
--- a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About high availability replication for clusters
@@ -22,7 +26,7 @@ We recommend configuring high availability as a part of a comprehensive disaster
 
 #### Hardware and software
 
-For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 64 GB of RAM, and 750 GB of attached storage.
+For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage.
 
 On each new virtual machine, install the same version of {% data variables.product.prodname_ghe_server %} that runs on the nodes in your active cluster. You don't need to upload a license or perform any additional configuration. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %}-Instanz einrichten](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)“.
 
diff --git a/translations/de-DE/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/de-DE/content/admin/enterprise-management/creating-a-high-availability-replica.md
index 472a3331d7..3b41f5f8e8 100644
--- a/translations/de-DE/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/de-DE/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/de-DE/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/de-DE/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index 45ff1abe30..7f77c706f1 100644
--- a/translations/de-DE/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/de-DE/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Fehlerszenarien
diff --git a/translations/de-DE/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/de-DE/content/admin/enterprise-management/enabling-automatic-update-checks.md
index 846517cf08..d9de5038a1 100644
--- a/translations/de-DE/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/de-DE/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 Wenn ein Upgrade-Pakete für {% data variables.product.product_location %} automatisch heruntergeladen wird, wird in einer Meldung angezeigt, dass Sie ein Upgrade von {% data variables.product.prodname_ghe_server %} durchführen können. Pakete werden auf {% data variables.product.product_location %} in das Verzeichnis `/var/lib/ghe-updates` heruntergeladen. Weitere Informationen finden Sie unter „[Upgrade von {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)“.
diff --git a/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md
index df7eeaa51b..80addc145e 100644
--- a/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/de-DE/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/de-DE/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index 8eba016c48..db078b1538 100644
--- a/translations/de-DE/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/de-DE/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/de-DE/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/de-DE/content/admin/enterprise-management/increasing-storage-capacity.md
index 4a27f28f7d..6b1db1b662 100644
--- a/translations/de-DE/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/de-DE/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -31,7 +35,10 @@ Wenn sich mehr Benutzer {% data variables.product.product_location %} anschließ
 1. Passen Sie die Größe der vorhandenen Benutzer-Volume-Disk mithilfe der Tools Ihrer Virtualisierungsplattform an.
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. Versetzen Sie die Appliance in den Wartungsmodus. Weitere Informationen finden Sie unter „[Wartungsmodus aktivieren und planen](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)“.
-4. Starten Sie die Appliance neu, um die neue Storage-Zuordnung zu ermitteln.
+4. Starten Sie die Appliance neu, um die neue Storage-Zuordnung zu ermitteln:
+  ```shell
+  $ sudo reboot
+  ```
 5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ Wenn sich mehr Benutzer {% data variables.product.product_location %} anschließ
 ### Größe der Root-Partition mit einer neuen Appliance erhöhen
 
 1. Richten Sie eine neue {% data variables.product.prodname_ghe_server %}-Instanz mit einer größeren Root-Disk ein. Verwenden Sie dazu dieselbe Version wie Ihre aktuelle Appliance. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %}-Instanz einrichten](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)“.
-2. Fahren Sie die aktuelle Appliance herunter.
+2. Fahren Sie die aktuelle Appliance herunter:
+  ```shell
+  $ sudo poweroff
+  ```
 3. Trennen Sie mithilfe der Tools Ihrer Virtualisierungsplattform die Daten-Disk von der aktuellen Appliance.
 4. Fügen Sie die Daten-Disk an die neue Appliance mit der größeren Root-Disk an.
 
@@ -57,6 +67,9 @@ Wenn sich mehr Benutzer {% data variables.product.product_location %} anschließ
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. Fahren Sie die Appliance herunter.
+4. Fahren Sie die Appliance herunter:
+  ```shell
+  $ sudo poweroff
+  ```
 5. Entfernen Sie auf dem Hypervisor die alte Root-Disk, und fügen Sie die neue Root-Disk am selben Ort als die alte Root-Disk an.
 6. Starten Sie die Appliance.
diff --git a/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md b/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md
index a76392d75a..e23466c6b8 100644
--- a/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/de-DE/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 0d53aa3654..9b67d8fd6f 100644
--- a/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Die für das Failover erforderliche Zeit hängt davon ab, wie lange es dauert, das Replikat manuell hochzustufen und den Traffic weiterzuleiten. Die Durchschnittszeit beträgt zwischen 2 und 10 Minuten.
diff --git a/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index 359ef8cf9a..7e0c9f975f 100644
--- a/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About failover to your replica cluster
diff --git a/translations/de-DE/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/de-DE/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index ac4f57b4a4..8896c9c62d 100644
--- a/translations/de-DE/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/de-DE/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -12,8 +12,11 @@ redirect_from:
 intro: 'Um {% data variables.product.prodname_enterprise %} von 11.10.x zu 2.1.23 zu migrieren, müssen Sie eine neue Appliance-Instanz einrichten und Daten aus der vorherigen Instanz migrieren.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 Migrationen von {% data variables.product.prodname_enterprise %} 11.10.348 und höher werden unterstützt. Migrationen von {% data variables.product.prodname_enterprise %} 11.10.348 und früher werden nicht unterstützt. Sie müssen zunächst in verschiedenen Upgrades ein Upgrade auf die Version 11.10.348 durchführen. Weitere Informationen finden Sie in der 11.10.348-Upgrade-Prozedur „[Upgrade auf die neueste Version durchführen](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)“.
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/de-DE/content/admin/enterprise-management/monitoring-cluster-nodes.md
index cfe515a57a..f08f91be53 100644
--- a/translations/de-DE/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -6,8 +6,14 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Clusterstatus manuell überprüfen
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/de-DE/content/admin/enterprise-management/monitoring-using-snmp.md
index 19faca402c..0b0de7f0be 100644
--- a/translations/de-DE/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP ist ein allgemeiner Standard zum Überwachen von Geräten über ein Netzwerk. Es wird dringend empfohlen, SNMP zu aktivieren, damit Sie den Zustand von {% data variables.product.product_location %} überwachen können und wissen, wann Sie der Host-Maschine Arbeitsspeicher, Storage oder Prozessorleistung hinzufügen müssen.
diff --git a/translations/de-DE/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/de-DE/content/admin/enterprise-management/recommended-alert-thresholds.md
index 782a0120a1..4aaa2a623e 100644
--- a/translations/de-DE/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/de-DE/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### Speicher überwachen
diff --git a/translations/de-DE/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/de-DE/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index ac38b8cb26..982f2569c2 100644
--- a/translations/de-DE/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/de-DE/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Sie können die vorherige primäre Appliance als neue Replikat-Appliance verwenden, sofern das Failover geplant war oder nicht mit dem Appliance-Zustand in Zusammenhang stand. Wenn das Failover mit einem Problem an der primären Appliance zusammenhing, sollten Sie ggf. eine neue Replikat-Appliance erstellen. Weitere Informationen finden Sie unter „[Hochverfügbarkeitsreplikat erstellen](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)“.
diff --git a/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md
index 3f6e11e93d..973eb79729 100644
--- a/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/de-DE/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### Temporäres Stoppen der Replikation
diff --git a/translations/de-DE/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/de-DE/content/admin/enterprise-management/replacing-a-cluster-node.md
index 6c6e9f82d3..52c7cc4ddd 100644
--- a/translations/de-DE/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/de-DE/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/de-DE/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/de-DE/content/admin/enterprise-management/setting-up-external-monitoring.md
index f356a2d921..d0ef3e8671 100644
--- a/translations/de-DE/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/de-DE/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Informationen zu SNMP
diff --git a/translations/de-DE/content/admin/enterprise-management/upgrade-requirements.md b/translations/de-DE/content/admin/enterprise-management/upgrade-requirements.md
index 12136fca4e..1df5d8928f 100644
--- a/translations/de-DE/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/de-DE/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 Anhand der Zahl können Sie schätzen, wie viel Speicherplatz die MySQL-Auditprotokolle benötigen werden. Darüber hinaus überwacht das Skript den freien Speicherplatz, während der Import ausgeführt wird. Die Überwachung dieser Zahl ist besonders nützlich, wenn der freie Speicherplatz dem für die Migration erforderlichen Speicherplatz nahekommt.
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### Nächste Schritte:
+
 Nachdem Sie diese Empfehlungen und Anforderungen gelesen haben, können Sie {% data variables.product.prodname_ghe_server %} upgraden. Weitere Informationen finden Sie unter „[Upgrade von {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)“.
diff --git a/translations/de-DE/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/de-DE/content/admin/enterprise-management/upgrading-a-cluster.md
index 0bdd635dee..256452ffa2 100644
--- a/translations/de-DE/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/de-DE/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### Upgrade mit einem Hotpatch
diff --git a/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index 49b82d757c..a20ff84bbf 100644
--- a/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### Upgrade vorbereiten
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
-
-Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
-
-Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
-
-| Benutzerlizenzen                                           |                           vCPUs |                         Arbeitsspeicher |                        Attached-Storage | Root-Storage |
-|:---------------------------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
-| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
-| 10–3000                                                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
-| 3000–5000                                                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
-| 5000–8000                                                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
-| 8000–10000+                                                | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### Snapshot erstellen
 
@@ -81,7 +59,7 @@ Es gibt zwei Snapshot-Typen:
 | Hyper-V               | VM               | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | Disk             | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM               | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM               | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM               | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### Upgrade mit einem Hotpatch
 
@@ -89,7 +67,12 @@ Es gibt zwei Snapshot-Typen:
 
 {% note %}
 
-**Hinweis:** In Clusterumgebungen ist die Installation eines Hotpatches mittels {% data variables.enterprise.management_console %} nicht verfügbar. Informationen zum Installieren eines Hotpatches in einer Clusterumgebung finden Sie unter „[Cluster-Upgrade](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)“.
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}Notes{% else %}Note{% endif %}**:
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+
+- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. Informationen zum Installieren eines Hotpatches in einer Clusterumgebung finden Sie unter „[Cluster-Upgrade](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)“.
 
 {% endnote %}
 
diff --git a/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md
index fabd375b84..0e1ebd410b 100644
--- a/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
@@ -18,32 +20,24 @@ topics:
 
 ### Informationen zum {% data variables.contact.enterprise_support %}
 
-{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %}.
+{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% if enterpriseServerVersions contains currentVersion %} and Japanese{% endif %}.
 
 {% if enterpriseServerVersions contains currentVersion %}
 You can contact
 {% data variables.contact.enterprise_support %} through {% data variables.contact.contact_enterprise_portal %} for help with:
  - Installation und Verwendung von {% data variables.product.product_name %}
  - Identifizierung und Überprüfung der Ursachen von vermuteten Fehlern
-{% endif %}
 
-In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.premium_support %}{% else %}support for {% data variables.product.product_name %}{% endif %} offers:
+In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} support for {% data variables.product.product_name %} offers:
   - Schriftlicher Support rund um die Uhr über unser Supportportal
   - Telefonischer Support rund um die Uhr
-  - A{% if currentVersion == "github-ae@latest" %}n enhanced{% endif %} Service Level Agreement (SLA) {% if enterpriseServerVersions contains currentVersion %}with guaranteed initial response times{% endif %}
-{% if currentVersion == "github-ae@latest" %}
-  - An assigned Technical Service Account Manager
-  - Quarterly support reviews
-  - Managed Admin services
-{% else if enterpriseServerVersions contains currentVersion %}
+  - Service Level Agreement (SLA) mit garantierten Antwortzeiten
   - Technical account managers
   - Zugriff auf Premium-Inhalte
   - Geplante Zustandsprüfungen
   - Managed Admin hours
 {% endif %}
 
-{% data reusables.support.government-response-times-may-vary %}
-
 {% if enterpriseServerVersions contains currentVersion %}
 Weitere Informationen finden Sie unter „[Informationen zum {{ site.data.variables.contact.premium_support }} für {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)“.
 {% endif %}
@@ -54,34 +48,28 @@ Weitere Informationen finden Sie unter „[Informationen zum {{ site.data.variab
 
 You can contact {% data variables.contact.enterprise_support %} through {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} the {% data variables.contact.ae_azure_portal %}{% endif %} to report issues in writing. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
 
+{% if enterpriseServerVersions contains currentVersion %}
 ### Geschäftszeiten
 
-{% if enterpriseServerVersions contains currentVersion %}
 #### Support auf Englisch
-{% endif %}
 
-{% if enterpriseServerVersions contains currentVersion %}
 Bei nicht dringenden herkömmlichen Probleme bieten wir 24 Stunden am Tag, 5 Tage die Woche, außer an Wochenenden und nationalen Feiertagen in den USA, Support in englischer Sprache. holidays. Die Antwortdauer beträgt in der Regel 24 Stunden.
 
-For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 days per week, even during national U.S. holidays.
+Für dringende Probleme stehen wir 24 Stunden am Tag, 7 Tage die Woche zur Verfügung, sogar während der nationalen US-Feiertage. holidays.
 
-{% data reusables.support.government-response-times-may-vary %}
-
-{% if enterpriseServerVersions contains currentVersion  %}
 #### Support auf Japanisch
 
 Bei nicht dringenden Problemen ist der Support auf Japanisch von Montag bis Freitag von 9:00 bis 17:00 Uhr JST verfügbar, außer an nationalen Feiertagen in Japan. For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
 
-For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."{% endif %}
+For a complete list of U.S. Eine vollständige Liste der vom {% data variables.contact.enterprise_support %} wahrgenommenen nationalen Feiertage in den USA und Japan finden Sie unter „[Feiertagsübersicht](#holiday-schedules)“.
 
-{% if enterpriseServerVersions contains currentVersion %}
 ### Feiertagsübersicht
 
-For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. {% if enterpriseServerVersions contains currentVersion  %}and Japanese{% endif %} holidays.
+For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. and Japanese holidays.
 
 #### Feiertage in den USA
 
-{% data variables.contact.enterprise_support %} beobachtet diese Feiertage in den USA. holidays{% if enterpriseServerVersions contains currentVersion  %}, although our global support team is available to answer urgent tickets{% endif %}.
+{% data variables.contact.enterprise_support %} beobachtet diese Feiertage in den USA. dessen ungeachtet steht unser Support-Team zur Verfügung, um dringende Tickets zu beantworten.
 
 | U.S. Weihnachtsfeiertag | Date observed                  |
 | ----------------------- | ------------------------------ |
@@ -125,7 +113,6 @@ Wenn Du den {% data variables.contact.enterprise_support %} kontaktierst, kannst
 ### Weiterführende Informationen
 
 {% if enterpriseServerVersions contains currentVersion %}
-- [Häufig gestellte Fragen zu {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq)
 - Section 10 on Support in the "[{% data variables.product.prodname_ghe_server %} License Agreement](https://enterprise.github.com/license)"{% endif %}
 - "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %}
 - "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %}
diff --git a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index 3feafff435..21ecd6ff14 100644
--- a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index b0bbb4427f..c8a54b9c25 100644
--- a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/de-DE/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/de-DE/content/admin/enterprise-support/about-support-for-advanced-security.md
index 917cd58e5a..8b6127205a 100644
--- a/translations/de-DE/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/de-DE/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/de-DE/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/de-DE/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index 95726c2eca..07dd9fe6dd 100644
--- a/translations/de-DE/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/de-DE/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 Bevor Sie ein Ticket absenden, sollten Sie folgende Schritte durchführen:
diff --git a/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md
index 818081e87e..11aef6f5fa 100644
--- a/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/de-DE/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Diagnosedateien erstellen und freigeben
diff --git a/translations/de-DE/content/admin/enterprise-support/reaching-github-support.md b/translations/de-DE/content/admin/enterprise-support/reaching-github-support.md
index 8149a40cf4..9d61ab4ee3 100644
--- a/translations/de-DE/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/de-DE/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Automatisierte Ticketsysteme nutzen
diff --git a/translations/de-DE/content/admin/enterprise-support/submitting-a-ticket.md b/translations/de-DE/content/admin/enterprise-support/submitting-a-ticket.md
index 3c99ee49b0..7a26a6acbf 100644
--- a/translations/de-DE/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/de-DE/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Informationen zum Absenden eines Tickets
diff --git a/translations/de-DE/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/de-DE/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..341f73ba73
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: About using actions in your enterprise
+intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community.
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### Official actions bundled with your enterprise instance
+
+Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}.
+
+The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: <code>https://<em>HOSTNAME</em>/actions</code>.
+
+Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)."
+
+{% note %}
+
+**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)."
+
+{% endnote %}
+
+### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
+
+If users in your enterprise need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options.
+
+The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %}
+
+Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)."
diff --git a/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 782191e0e5..9afbe3c827 100644
--- a/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/de-DE/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: Backing up and restoring
 intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index 9820de8565..c293deee90 100644
--- a/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/de-DE/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: Enabling automatic access to GitHub.com actions using GitHub Connect
-intro: 'To allow {% data variables.product.prodname_actions %} on your enterprise instance to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %}.'
+intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)."
+To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
 
-Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location_enterprise %}, you must connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %}. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %} mit {% data variables.product.prodname_ghe_cloud %} verbinden](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)“.
+Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %} mit {% data variables.product.prodname_ghe_cloud %} verbinden](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)“.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index e23d688925..25bc00d6d5 100644
--- a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 
-* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index 8fd6e3c23e..948c3932eb 100644
--- a/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 
 * To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}.
-* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 9a35874248..48959da8e5 100644
--- a/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index ef72ddb56e..04ded0e7ff 100644
--- a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: Getting started with GitHub Actions for GitHub AE
+shortTitle: Erste Schritte mit GitHub Actions
 intro: 'Learn configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index 08566af48b..49821e79e3 100644
--- a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,5 +1,6 @@
 ---
 title: Getting started with GitHub Actions for GitHub Enterprise Server
+shortTitle: Erste Schritte mit GitHub Actions
 intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
@@ -7,7 +8,9 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
+  - Actions
   - Enterprise
 ---
 
@@ -116,7 +119,7 @@ To run {% data variables.product.prodname_actions %} workflows, you need to add
 
 You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}.
 
-For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)."
+For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### General security hardening for {% data variables.product.prodname_actions %}
 
diff --git a/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md b/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md
index 9d2e46a932..b9ca5b47bf 100644
--- a/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/de-DE/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: High availability for GitHub Actions
 intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### Replication or redundancy of your {% data variables.product.prodname_actions %} data
diff --git a/translations/de-DE/content/admin/github-actions/index.md b/translations/de-DE/content/admin/github-actions/index.md
index 2171f496f8..28aa0eb1ab 100644
--- a/translations/de-DE/content/admin/github-actions/index.md
+++ b/translations/de-DE/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index b0861fcf10..1fefd8790b 100644
--- a/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/de-DE/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: Manually syncing actions from GitHub.com
-intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your {% data variables.product.prodname_ghe_server %} instance.'
+intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance.
+However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise.
 
 ### About the `actions-sync` tool
 
-The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API. The machine doesn't need to be connected to both at the same time.
+The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time.
 
 If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands.
 
@@ -29,8 +30,8 @@ The `actions-sync` tool can only download actions from {% data variables.product
 
 ### Vorrausetzungen
 
-* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
-* You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. Weitere Informationen finden Sie unter "[Erstellen eines persönlichen Zugriffstokens](/github/authenticating-to-github/creating-a-personal-access-token)."
+* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. Weitere Informationen finden Sie unter "[Erstellen eines persönlichen Zugriffstokens](/github/authenticating-to-github/creating-a-personal-access-token)."
 * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
 
   {% note %}
@@ -51,7 +52,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
 
 {% note %}
 
-**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
+**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
    * `--destination-url`: The URL of the destination enterprise instance.
    * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`.
 
-     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination {% data variables.product.prodname_ghe_server %} instance. You must create the organization named `synced-actions` on your enterprise instance before running the above command.
-     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise instance. Before running the command, you must create a new organization on your instance that matches the owner name of the action. Consider using a central organization to store the synced actions on your instance, as this means you will not need to  create multiple new organizations if you sync actions from different owners.
+     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command.
+     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners.
      * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync).
-1. After the action repository is created on your enterprise instance, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
+1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 6ac39238e2..e393fe5eb0 100644
--- a/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### About the included setup actions and the runner tool cache
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}. However, self-hosted runners without internet access  will require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
+Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}. However, self-hosted runners without internet access require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
 
 The `actions/setup-LANGUAGE` actions normally need internet access to download the required environment binaries into the runner's tool cache. Self-hosted runners without internet access can't download the binaries, so you must manually populate the tool cache on the runner.
 
diff --git a/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md b/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md
index 6c6a2e1e3a..77a8aec9ea 100644
--- a/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/de-DE/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: Using a staging environment
 intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment.
diff --git a/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 3e0191625c..40b77ea7ad 100644
--- a/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
 title: Using the latest version of the official bundled actions
-intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)."
 
-These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
+These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.
 
-Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
+### Using `actions-sync` to update the bundled actions
 
-- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
-- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
+To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
 
-These options are described in more detail in the following sections.
+### Using {% data variables.product.prodname_github_connect %} to access the latest actions
 
-### Using actions-sync to update a bundled action
+You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
 
-To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
+Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}:
 
-### Using actions from {% data variables.product.prodname_dotcom_the_website %}
+1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." Ein Beispiel:
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
-
-### Using the latest version by removing the specific action's tag
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
-
-For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
-
-1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
-1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
-
-When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)."
+1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)."
+1. Configure your workflow's YAML to use `actions/checkout@v2`.
+1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/de-DE/content/admin/guides.md b/translations/de-DE/content/admin/guides.md
new file mode 100644
index 0000000000..7664da2fe3
--- /dev/null
+++ b/translations/de-DE/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: GitHub Enterprise guides
+shortTitle: Leitfäden
+intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/de-DE/content/admin/index.md b/translations/de-DE/content/admin/index.md
index 543eca374d..2c141854a9 100644
--- a/translations/de-DE/content/admin/index.md
+++ b/translations/de-DE/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: Enterprise Administrators
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
+title: GitHub Enterprise Documentation
+shortTitle: GitHub Enterprise
 intro: 'Documentation and guides for enterprise administrators, system administrators, and security specialists who {% if enterpriseServerVersions contains currentVersion %}deploy, {% endif %}configure{% if enterpriseServerVersions contains currentVersion %},{% endif %} and manage {% data variables.product.product_name %}.'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/de-DE/content/admin/installation/index.md b/translations/de-DE/content/admin/installation/index.md
index 29146384c4..e42466092b 100644
--- a/translations/de-DE/content/admin/installation/index.md
+++ b/translations/de-DE/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 Weitere Informationen zu oder zum Kauf von {% data variables.product.prodname_enterprise %} finden Sie unter [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md b/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md
index 725ce0bb6e..f35b89290a 100644
--- a/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/de-DE/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/de-DE/content/admin/overview/about-data-residency.md b/translations/de-DE/content/admin/overview/about-data-residency.md
index a83066177e..08df5703dc 100644
--- a/translations/de-DE/content/admin/overview/about-data-residency.md
+++ b/translations/de-DE/content/admin/overview/about-data-residency.md
@@ -1,8 +1,12 @@
 ---
 title: About data residency
-intro: You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.
+intro: 'You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %} You can choose the geography where you store all the customer data for {% data variables.product.product_location %}, and members of your enterprise can access {% data variables.product.product_name %} from anywhere in the world.
diff --git a/translations/de-DE/content/admin/overview/about-enterprise-accounts.md b/translations/de-DE/content/admin/overview/about-enterprise-accounts.md
index daff133bba..4f4425b621 100644
--- a/translations/de-DE/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/de-DE/content/admin/overview/about-enterprise-accounts.md
@@ -7,8 +7,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
+type: overview
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### Informationen zu Unternehmenskonten auf {% data variables.product.product_name %}
diff --git a/translations/de-DE/content/admin/overview/about-github-ae.md b/translations/de-DE/content/admin/overview/about-github-ae.md
index 562f4b7e6a..650217c2a5 100644
--- a/translations/de-DE/content/admin/overview/about-github-ae.md
+++ b/translations/de-DE/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: About GitHub AE
 intro: '{% data variables.product.prodname_ghe_managed %} is a security-enhanced and compliant way to use {% data variables.product.prodname_dotcom %} in the cloud.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### Informationen zu {% data variables.product.prodname_ghe_managed %}
@@ -21,7 +25,7 @@ All of your data is stored within the geographic region of your choosing. You ca
 
 ### Encryption on your terms
 
-All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
+All customer data is encrypted at rest. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
 
 ### Isolated accounts
 
diff --git a/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md
index 578313e51f..b4423c7231 100644
--- a/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,8 +5,10 @@ intro: '{% if currentVersion == "github-ae@latest" %}Your {% data variables.prod
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
@@ -17,7 +19,7 @@ Major releases include new functionality and feature upgrades and typically occu
 
 Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}.
 
-You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)."
+You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. Weitere Informationen finden Sie unter „[Upgrade-Anforderungen](/admin/enterprise-management/upgrade-requirements)“.
 
 Release candidates should be deployed on test or staging environments. As you test a release candidate, please provide feedback by contacting support. For more information, see "[Working with {% data variables.contact.github_support %}](/admin/enterprise-support)."
 
diff --git a/translations/de-DE/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/de-DE/content/admin/overview/managing-billing-for-your-enterprise.md
index d1ce14f2a7..cabc4e8001 100644
--- a/translations/de-DE/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ For example, here are the costs for users with licenses on different dates.
 | Benutzer  | License dates                                           | Counted days | Cost   |
 | --------- | ------------------------------------------------------- | ------------ | ------ |
 | @octocat  | January 1 - January 31                                  | 31           | $39    |
-| @robocat  | February 1 - February 28                                | 29           | $35.23 |
+| @robocat  | February 1 - February 28                                | 28           | $35.23 |
 | @devtocat | January 15 - January 31                                 | 17           | $21.39 |
 | @doctocat | January 1 - January 15                                  | 31           | $39    |
 | @prodocat | January 7 - January 15                                  | 25           | $31.45 |
 | @monalisa | January 1 - January 7,<br>January 15 - January 31 | 31           | $39    |
 
-Your enterprise can include one or more instances. {% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
+{% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
 
 You can see your current usage in your [Azure account portal](https://portal.azure.com).
 
diff --git a/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md b/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md
index e54dc37986..0aad40acaf 100644
--- a/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/de-DE/content/admin/overview/managing-your-github-enterprise-license.md
@@ -56,7 +56,7 @@ Wenn Du Benutzerlizenzen erneuern oder zu {% data variables.product.prodname_ent
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
 3. Klicke in der linken Seitenleiste auf **Enterprise licensing** (Enterprise-Lizenzierung). !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-4. Überprüfe Deine aktuelle {% data variables.product.prodname_enterprise %}-Lizenz sowie verbrauchte und verfügbare Benutzerlizenzen.
+4. Überprüfe Deine aktuelle {% data variables.product.prodname_enterprise %}-Lizenz sowie verbrauchte und verfügbare Benutzerlizenzen. {% if currentVersion ver_gt "enterprise-server@3.0" %}If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
 
 ### Nutzung der Benutzerlizenzen mit {% data variables.product.prodname_ghe_cloud %} automatisch synchronisieren
 
diff --git a/translations/de-DE/content/admin/overview/system-overview.md b/translations/de-DE/content/admin/overview/system-overview.md
index f411a190af..b0d493db53 100644
--- a/translations/de-DE/content/admin/overview/system-overview.md
+++ b/translations/de-DE/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### Speicherarchitektur
@@ -110,7 +115,7 @@ Weitere Informationen zu den Benutzerberechtigungen in {% data variables.product
 
 #### Audit- und Zugriffsprotokollierung
 
-{% data variables.product.prodname_ghe_server %} speichert sowohl herkömmliche Betriebssystem- als auch Anwendungsprotokolle. Die Anwendung führt außerdem detaillierte Audit- und Sicherheitsprotokolle, die {% data variables.product.prodname_ghe_server %} dauerhaft speichert. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. For more information, see "[Log forwarding](/admin/user-management/log-forwarding)."
+{% data variables.product.prodname_ghe_server %} speichert sowohl herkömmliche Betriebssystem- als auch Anwendungsprotokolle. Die Anwendung führt außerdem detaillierte Audit- und Sicherheitsprotokolle, die {% data variables.product.prodname_ghe_server %} dauerhaft speichert. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. Weitere Informationen finden Sie unter „[Protokollweiterleitung](/admin/user-management/log-forwarding)“.
 
 Zugriffs- und Auditprotokolle enthalten beispielsweise die folgenden Informationen.
 
diff --git a/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index 09069535c3..feea5d1dc2 100644
--- a/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 398ccc528c..ca1bd427f3 100644
--- a/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: Getting started with GitHub Packages for your enterprise
+shortTitle: Getting started with GitHub Packages
 intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index 37210e06c3..603a9648a2 100644
--- a/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: Quickstart for configuring your MinIO storage bucket for GitHub Packages
 intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/de-DE/content/admin/policies/about-pre-receive-hooks.md b/translations/de-DE/content/admin/policies/about-pre-receive-hooks.md
index 04a875519a..f541bde7e5 100644
--- a/translations/de-DE/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/de-DE/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Wenn ein Push vorgenommen wird, wird jedes Skript in einer isolierten Umgebung ausgeführt und kann den Inhalt der Pushs überprüfen. Die Skripts sorgen dafür, dass der Push bei dem Beendigungsstatus 0 akzeptiert und bei einem Beendigungsstatus ungleich 0 abgelehnt wird.
diff --git a/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-environment.md
index 9e9b937a82..3c7a25d4aa 100644
--- a/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Eine Pre-Receive-Umgebung für {% data variables.product.prodname_ghe_server %} ist eine Linux-chroot</code>-Umgebung. Da Pre-Receive-Hooks bei jedem Push-Ereignis ausgeführt werden, sollten sie schnell und kompakt sein. Die für solche Überprüfungen benötigte Umgebung ist in der Regel minimal.</p> 
diff --git a/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md
index f3601ee954..d3f983f9a5 100644
--- a/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/de-DE/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Im [`github/platform-samples`-Repository](https://github.com/github/platform-samples/tree/master/pre-receive-hooks) finden Sie Beispiele von Pre-Receive-Hooks für {% data variables.product.prodname_ghe_server %}.
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index c9e51c7dc3..298ac792b6 100644
--- a/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,6 +5,13 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### Informationen zu {% data variables.product.prodname_GH_advanced_security %}
diff --git a/translations/de-DE/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 5647cb42cd..10b938f6b2 100644
--- a/translations/de-DE/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/de-DE/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Configuring the default visibility of new repositories in your enterprise
diff --git a/translations/de-DE/content/admin/policies/index.md b/translations/de-DE/content/admin/policies/index.md
index 83ddff4378..a8653ea673 100644
--- a/translations/de-DE/content/admin/policies/index.md
+++ b/translations/de-DE/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/de-DE/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/de-DE/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 11f188bef4..532e7a8d96 100644
--- a/translations/de-DE/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/de-DE/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### Pre-Receive-Hooks erstellen
diff --git a/translations/de-DE/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/de-DE/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..03b083ea40
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About email restrictions for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restricting email notifications for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/de-DE/content/admin/release-notes.md b/translations/de-DE/content/admin/release-notes.md
index 1af66701b5..7dfc63a71c 100644
--- a/translations/de-DE/content/admin/release-notes.md
+++ b/translations/de-DE/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/de-DE/content/admin/user-management/about-migrations.md b/translations/de-DE/content/admin/user-management/about-migrations.md
index 9e31bd5f1e..7cd09aa93d 100644
--- a/translations/de-DE/content/admin/user-management/about-migrations.md
+++ b/translations/de-DE/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Migrationstypen
diff --git a/translations/de-DE/content/admin/user-management/adding-people-to-teams.md b/translations/de-DE/content/admin/user-management/adding-people-to-teams.md
index 439536f0cf..5716b87ae0 100644
--- a/translations/de-DE/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/de-DE/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: 'Nach der Erstellung eines Teams können Organisationsadministratoren Benutzer von {% data variables.product.product_location %} zum Team hinzufügen und festlegen, auf welche Repositorys sie zugreifen dürfen.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Jedes Team besitzt seine eigenen individuell festgelegten [Zugriffsberechtigungen für Repositorys, die Ihrer Organisation gehören](/articles/permission-levels-for-an-organization).
diff --git a/translations/de-DE/content/admin/user-management/audit-logging.md b/translations/de-DE/content/admin/user-management/audit-logging.md
index 4935dd99d5..7fdf916554 100644
--- a/translations/de-DE/content/admin/user-management/audit-logging.md
+++ b/translations/de-DE/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 For a full list, see "[Audited actions](/admin/user-management/audited-actions)." For more information on finding a particular action, see "[Searching the audit log](/admin/user-management/searching-the-audit-log)."
diff --git a/translations/de-DE/content/admin/user-management/audited-actions.md b/translations/de-DE/content/admin/user-management/audited-actions.md
index a8b6f607e0..8da4792b7b 100644
--- a/translations/de-DE/content/admin/user-management/audited-actions.md
+++ b/translations/de-DE/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### Authentifizierung
@@ -72,12 +75,12 @@ topics:
 
 #### Issues und Pull Requests
 
-| Aktion                               | Beschreibung                                                                                                                                          |
-| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `issue.update`                       | Der Text eines Issues (erster Kommentar) wurde geändert.                                                                                              |
-| `issue_comment.update`               | Ein Kommentar zu einem Issue (nicht der ursprüngliche) wurde geändert.                                                                                |
-| `pull_request_review_comment.delete` | A comment on a pull request was deleted.                                                                                                              |
-| `issue.destroy`                      | Ein Issue wurde aus dem Repository gelöscht. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)." |
+| Aktion                               | Beschreibung                                                                                                                                                   |
+| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `issue.update`                       | Der Text eines Issues (erster Kommentar) wurde geändert.                                                                                                       |
+| `issue_comment.update`               | Ein Kommentar zu einem Issue (nicht der ursprüngliche) wurde geändert.                                                                                         |
+| `pull_request_review_comment.delete` | A comment on a pull request was deleted.                                                                                                                       |
+| `issue.destroy`                      | Ein Issue wurde aus dem Repository gelöscht. Weitere Informationen finden Sie unter „[Issue löschen](/github/managing-your-work-on-github/deleting-an-issue)“. |
 
 #### Organisationen
 
diff --git a/translations/de-DE/content/admin/user-management/auditing-ssh-keys.md b/translations/de-DE/content/admin/user-management/auditing-ssh-keys.md
index 30b8fbf2a7..6a25f00533 100644
--- a/translations/de-DE/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/de-DE/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 Sobald das Audit initiiert ist, werden alle vorhandenen SSH-Schlüssel deaktiviert und Benutzer gezwungen, sie zu genehmigen oder abzulehnen, bevor sie diese klonen, abrufen oder per Push-Vorgang an Repositorys übertragen können. Ein Audit eignet sich in Situationen, in denen ein Mitarbeiter oder Vertragsnehmer das Unternehmen verlässt und Sie sicherstellen müssen, dass alle Schlüssel verifiziert sind.
diff --git a/translations/de-DE/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/de-DE/content/admin/user-management/auditing-users-across-your-enterprise.md
index ba5a5e7147..303798e923 100644
--- a/translations/de-DE/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### Zugriff auf das Auditprotokoll
@@ -74,7 +79,7 @@ Der Kennzeichner `org` begrenzt Aktionen auf eine bestimmte Organisation. Ein Be
 
 #### Suche nach der Art der durchgeführten Aktion
 
-Der Kennzeichner `action` sucht nach bestimmten Ereignissen, gruppiert in Kategorien. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)".
+Der Kennzeichner `action` sucht nach bestimmten Ereignissen, gruppiert in Kategorien. Weitere Informationen zu diesen Kategorien zugeordneten Ereignissen finden Sie unter „[Überwachte Aktionen](/admin/user-management/audited-actions)“.
 
 | Kategoriename | Beschreibung                                                                              |
 | ------------- | ----------------------------------------------------------------------------------------- |
diff --git a/translations/de-DE/content/admin/user-management/best-practices-for-user-security.md b/translations/de-DE/content/admin/user-management/best-practices-for-user-security.md
index 6e00686d3a..6dccf97455 100644
--- a/translations/de-DE/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/de-DE/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/de-DE/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index 3ac16f1ba8..7c939c7437 100644
--- a/translations/de-DE/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### Informationen zu {% data variables.large_files.product_name_long %}
@@ -97,11 +101,11 @@ Weitere Informationen finden Sie unter „[Informationen zu {% data variables.la
   $ git add .lfsconfig
   $ git commit -m "Adding LFS config file"
   ```
-3. Migrieren Sie vorhandene {% data variables.large_files.product_name_short %}-Assets. For more information, see "[Migrating to a different {% data variables.large_files.product_name_long %} server](#migrating-to-a-different-git-large-file-storage-server)."
+3. Migrieren Sie vorhandene {% data variables.large_files.product_name_short %}-Assets. Weitere Informationen finden Sie unter „[Zu einem anderen {% data variables.large_files.product_name_long %}-Server migrieren](#migrating-to-a-different-git-large-file-storage-server)“.
 
 ### Zu einem anderen Git Large File Storage-Server migrieren
 
-Bevor Sie eine Migration zu einem anderen {% data variables.large_files.product_name_long %}-Server durchführen, müssen Sie {% data variables.large_files.product_name_short %} für die Verwendung eines Drittanbieterservers konfigurieren. For more information, see "[Configuring {% data variables.large_files.product_name_long %} to use a third party server](#configuring-git-large-file-storage-to-use-a-third-party-server)."
+Bevor Sie eine Migration zu einem anderen {% data variables.large_files.product_name_long %}-Server durchführen, müssen Sie {% data variables.large_files.product_name_short %} für die Verwendung eines Drittanbieterservers konfigurieren. Weitere Informationen finden Sie unter „[{% data variables.large_files.product_name_long %} zur Verwendung eines Drittanbieterservers konfigurieren](#configuring-git-large-file-storage-to-use-a-third-party-server)“.
 
 1. Konfigurieren Sie das Repository mit einer zweiten Remote-Instanz.
   ```shell
diff --git a/translations/de-DE/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/de-DE/content/admin/user-management/configuring-visibility-for-organization-membership.md
index 3b5132366a..b949903f14 100644
--- a/translations/de-DE/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/de-DE/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/de-DE/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/de-DE/content/admin/user-management/continuous-integration-using-jenkins.md
index 31c6d6c7a4..48652110d3 100644
--- a/translations/de-DE/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/de-DE/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/user-management/creating-teams.md b/translations/de-DE/content/admin/user-management/creating-teams.md
index 24325660b7..55c1fd555c 100644
--- a/translations/de-DE/content/admin/user-management/creating-teams.md
+++ b/translations/de-DE/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Teams sind zentral für viele gemeinschaftliche Features von {% data variables.product.prodname_dotcom %}, beispielsweise Team-@Erwähnungen, um die entsprechenden Teilnehmer dahingehend zu informieren, dass Sie deren Beiträge oder Aufmerksamkeit anfordern möchten. Weitere Informationen finden Sie unter „[Berechtigungsebenen für die Repositorys einer Organisation](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)“.
diff --git a/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index 5e0b489b75..f91889e911 100644
--- a/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: Customizing user messages for your enterprise
+shortTitle: Customizing user messages
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: 'You can create custom messages that users will see on {% data variables.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### About user messages
diff --git a/translations/de-DE/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/de-DE/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index 733dfb475d..674fb5e5d3 100644
--- a/translations/de-DE/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: You can prevent people from using Git over SSH for certain or all reposit
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### Git-SSH-Zugriff auf ein bestimmtes Repository deaktivieren
diff --git a/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md
index edc21ce23b..2a87d996d9 100644
--- a/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/de-DE/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the source organization on {% data variables.product.prodname_dotcom %}
diff --git a/translations/de-DE/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/de-DE/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index 656f07f5db..0d3b5ab9da 100644
--- a/translations/de-DE/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the {% data variables.product.prodname_ghe_server %} source instance
diff --git a/translations/de-DE/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/de-DE/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 9c39b0f4fa..c05ee097ec 100644
--- a/translations/de-DE/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/de-DE/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Projekte aus Mercurial importieren
diff --git a/translations/de-DE/content/admin/user-management/log-forwarding.md b/translations/de-DE/content/admin/user-management/log-forwarding.md
index 428d44691b..222232cb06 100644
--- a/translations/de-DE/content/admin/user-management/log-forwarding.md
+++ b/translations/de-DE/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Unterstützt werden Protokollsammlungssysteme, die Protokollstreams im Syslog-Stil unterstützen (z. B. [Logstash](http://logstash.net/) und [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
diff --git a/translations/de-DE/content/admin/user-management/managing-dormant-users.md b/translations/de-DE/content/admin/user-management/managing-dormant-users.md
index d4edc04743..d8744254e5 100644
--- a/translations/de-DE/content/admin/user-management/managing-dormant-users.md
+++ b/translations/de-DE/content/admin/user-management/managing-dormant-users.md
@@ -9,8 +9,11 @@ intro: 'A user account is considered to be dormant if it has not been active for
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 Zu den „Aktivitäten“ zählen u. a.
diff --git a/translations/de-DE/content/admin/user-management/managing-global-webhooks.md b/translations/de-DE/content/admin/user-management/managing-global-webhooks.md
index ff202802a9..072e3d2a5b 100644
--- a/translations/de-DE/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/de-DE/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### Informationen zu globalen Webhooks
diff --git a/translations/de-DE/content/admin/user-management/managing-projects-using-jira.md b/translations/de-DE/content/admin/user-management/managing-projects-using-jira.md
index 98e2c78db6..4fba2e116d 100644
--- a/translations/de-DE/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/de-DE/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: Projekte mit JIRA verwalten
-intro: 'Sie können JIRA in {% data variables.product.prodname_enterprise %} zur Projektverwaltung integrieren.'
+title: Managing projects using Jira
+intro: 'You can integrate Jira with {% data variables.product.prodname_enterprise %} for project management.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### JIRA mit einer {% data variables.product.prodname_enterprise %}-Organisation verbinden
+### Connecting Jira to a {% data variables.product.prodname_enterprise %} organization
 
-1. Melden Sie sich unter „http[s]://[hostname]/login“ bei Ihrem {% data variables.product.prodname_enterprise %}-Konto an.
-1. Klicken Sie in der oberen rechten Ecke einer beliebigen Seite auf das Symbol (Zahnrad) mit den Kontoeinstellungen.
-1. Klicken Sie auf der linken Seitenleiste auf den Namen Ihrer Organisation.
-1. Klicke in der linken Seitenleiste auf **Applications** (Anwendungen).
-1. Klicken Sie in der oberen rechten Ecke des Felds **Organization applications** (Organisationsanwendungen) auf **Register new application** (Neue Anwendung registrieren).
-1. Tragen Sie die Anwendungseinstellungen ein:
-    - Geben Sie „JIRA“ im Feld **Application name** (Anwendungsname) ein.
-    - Geben Sie die vollständige URL Ihrer JIRA-Instanz im Feld **Homepage URL** (URL für Startseite) ein.
-    - Geben Sie die vollständige URL Ihrer JIRA-Instanz im Feld **Authorization callback URL** (Autorisierungsrückruf-URL) ein.
-1. Klicke auf **Register application** (Anwendung registrieren).
-1. Beachten Sie oben auf der Seite die **Client-ID** und das **Clientgeheimnis**. Sie benötigen diese Angaben zum Konfigurieren Ihrer JIRA-Instanz.
+1. Melden Sie sich unter „http[s]://[hostname]/login“ bei Ihrem {% data variables.product.prodname_enterprise %}-Konto an. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
+2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira.
 
-### Konfiguration der JIRA-Instanz
+  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. Melden Sie sich auf Ihrer JIRA-Instanz mit administrativem Zugriff bei einem Konto an.
-1. Klicken Sie im oberen Bereich der Seite auf das Symbol (Zahnrad) für Einstellungen.
-1. Wählen Sie im Dropdownmenü für die Einstellungen **Add-Ons** aus.
-1. Klicken Sie auf der linken Seitenleiste unter **Source control** (Quellcodeverwaltung) auf **DVCS accounts** (DVCS-Konto).
-1. Klicken Sie auf **Link Bitbucket or GitHub account** (Bitbucket oder GitHub-Konto verknüpfen).
-1. Tragen Sie im Modalfenster **Add New Account** (Neues Konto hinzufügen) Ihre {% data variables.product.prodname_enterprise %}-Einstellungen ein:
-    - Wählen Sie **GitHub Enterprise** im Dropdownmenü **Host** aus.
+3. Click on the **Edit _organization name_ settings** link.
+
+  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
+
+  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Click on the **Register new application** button.
+
+  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. Tragen Sie die Anwendungseinstellungen ein:
+    - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance.
+    - In the **Homepage URL** field, type the full URL of your Jira instance.
+    - In the **Authorization callback URL** field, type the full URL of your Jira instance.
+7. Klicke auf **Register application** (Anwendung registrieren).
+8. Beachten Sie oben auf der Seite die **Client-ID** und das **Clientgeheimnis**. You will need these for configuring your Jira instance.
+
+### Jira instance configuration
+
+1. On your Jira instance, log into an account with administrative access.
+2. At the top of the page, click the settings (gear) icon and choose **Applications**.
+
+  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
+
+  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
+
+  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. Tragen Sie im Modalfenster **Add New Account** (Neues Konto hinzufügen) Ihre {% data variables.product.prodname_enterprise %}-Einstellungen ein:
+    - From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**.
     - Geben Sie im Feld **Team or User Account** den Namen Ihrer {% data variables.product.prodname_enterprise %}-Organisation oder Ihres persönlichen Kontos ein.
     - Geben Sie im Feld **OAuth Key** (OAuth-Schlüssel) die Client-ID Ihrer {% data variables.product.prodname_enterprise %}-Entwickleranwendung ein.
     - Geben Sie im Feld **OAuth Secret** (OAuth-Geheimnis) das Clientgeheimnis für Ihre {% data variables.product.prodname_enterprise %}-Entwickleranwendung ein.
-    - Deaktivieren Sie **Auto Link New Repositories** (Neue Repositorys automatisch verknüpfen), wenn die Ihrer {% data variables.product.prodname_enterprise %}-Organisation oder Ihrem persönlichen Konto zugehörigen neuen Repositorys nicht verknüpft werden sollen.
-    - Deaktivieren Sie **Enable Smart Commits** (Intelligente Commits aktivieren), wenn Sie intelligente Commits nicht aktivieren möchten.
+    - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, deselect **Auto Link New Repositories**.
+    - If you don't want to enable smart commits, deselect **Enable Smart Commits**.
     - Klicke auf **Add** (Hinzufügen).
-1. Überprüfen Sie die Berechtigungen, die Sie Ihrem {% data variables.product.prodname_enterprise %}-Konto erteilen, und klicken Sie auf **Authorize application** (Anwendung autorisieren).
-1. Geben Sie zum Fortfahren ggf. Ihr Passwort ein.
+6. Überprüfen Sie die Berechtigungen, die Sie Ihrem {% data variables.product.prodname_enterprise %}-Konto erteilen, und klicken Sie auf **Authorize application** (Anwendung autorisieren).
+7. Geben Sie zum Fortfahren ggf. Ihr Passwort ein.
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md
index ddded268af..3ea003c916 100644
--- a/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Applying the imported data on {% data variables.product.prodname_ghe_server %}
@@ -135,7 +137,7 @@ curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
 
 #### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
 
-After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). Sie benötigen Ihr Zugriffstoken für die Authentifizierung:
+Nachdem Sie die Repositorys der {% data variables.product.prodname_dotcom_the_website %}-Organisation entsperrt haben, sollten Sie mithilfe des [Endpunkts zum Löschen des Repositorys](/rest/reference/repos/#delete-a-repository) jedes Repository löschen, das Sie zuvor migriert haben. Sie benötigen Ihr Zugriffstoken für die Authentifizierung:
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   https://api.github.com/repos/<em>orgname</em>/<em>repo_name</em>
diff --git a/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md b/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md
index ed841ffe0b..77b39e57b6 100644
--- a/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/de-DE/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### Informationen zu internen Repositorys
@@ -34,6 +38,12 @@ Wenn Du den private Modus nicht aktiviert hast, hat das Migrationsskript keine A
 ### Die Migration durchführen
 
 1. Stellen Sie eine Verbindung zur Verwaltungsshell her. Weitere Informationen findest Du unter "[Auf die administrative Shell (SSH) zugreifen](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)."
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. Führe den Migrationsbefehl aus.
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. Navigiere zum Verzeichnis `/data/github/current`.
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ Wenn Du den private Modus nicht aktiviert hast, hat das Migrationsskript keine A
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 Die Log-Ausgabe erscheint im Terminal und `/tmp/convert_public_ghes_repos_to_internal.log`.
 
diff --git a/translations/de-DE/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/de-DE/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index 0080e80493..1db73e8528 100644
--- a/translations/de-DE/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/de-DE/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 Wenn ein Repository gelöscht wird, bleibt es in der Regel 90 Tage lang weiterhin auf der Disk und kann über das Websiteadministrator-Dashboard wiederhergestellt werden. Nach 90 Tagen wird das Repository bereinigt und dauerhaft gelöscht. Wenn Sie eine gesetzliche Aufbewahrungspflicht für einen Benutzer oder für eine Organisation festlegen, können die ihm oder ihr gehörenden Repositorys auf unbestimmte Zeit wiederhergestellt werden.
diff --git a/translations/de-DE/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index b87c5641f7..4ecb655e7a 100644
--- a/translations/de-DE/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/de-DE/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
diff --git a/translations/de-DE/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/de-DE/content/admin/user-management/preventing-users-from-creating-organizations.md
index bfe7c261c9..91b5f5efcb 100644
--- a/translations/de-DE/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/de-DE/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: You can prevent users from creating organizations in your enterprise.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/de-DE/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/de-DE/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index bd6d3962ed..0d125700de 100644
--- a/translations/de-DE/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/de-DE/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: Websiteadministratoren können normale Benutzerkonten auf einen Websiteadministrator hochstufen und andere Websiteadministratoren auf normale Benutzer zurückstufen.
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/de-DE/content/admin/user-management/rebuilding-contributions-data.md b/translations/de-DE/content/admin/user-management/rebuilding-contributions-data.md
index 24e8db12c4..adf2f611c1 100644
--- a/translations/de-DE/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/de-DE/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 Wenn ein Commit per Push-Vorgang an {% data variables.product.prodname_enterprise %} übertragen wird, wird er mit einem Benutzerkonto verknüpft, sofern sie beide derselben E-Mail-Adresse zugeordnet sind. Vorhandene Commits werden jedoch *nicht* retroaktiv verknüpft, wenn ein Benutzer eine neue E-Mail-Adresse registriert oder ein neues Konto erstellt.
diff --git a/translations/de-DE/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/de-DE/content/admin/user-management/removing-users-from-teams-and-organizations.md
index e21d102b16..931ae91aba 100644
--- a/translations/de-DE/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/de-DE/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Nur Inhaber oder Teamadministratoren können Organisationsmitglieder entfernen. Wenn ein Benutzer aus einem Team oder aus einer Organisation entfernt wird, bleiben seine Issues, Pull Requests und Kommentare in den Repositorys der Organisation erhalten und sind ihm weiterhin zugeordnet.
diff --git a/translations/de-DE/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/de-DE/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index bf1924e552..7569d92b51 100644
--- a/translations/de-DE/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/de-DE/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.product.product_location %}. Organisationsadministratoren können festlegen, dass Mitglieder die Zwei-Faktor-Authentifizierung aktivieren müssen.
diff --git a/translations/de-DE/content/admin/user-management/searching-the-audit-log.md b/translations/de-DE/content/admin/user-management/searching-the-audit-log.md
index 89ab0b6136..9cb0570cb0 100644
--- a/translations/de-DE/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/de-DE/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### Suchabfragesyntax
@@ -37,7 +40,7 @@ So können Sie beispielsweise alle Aktionen anzeigen, die sich seit Anfang 2017
 
   `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]`
 
-For a full list of actions, see "[Audited actions](/admin/user-management/audited-actions)."
+Eine vollständige Liste der Aktionen finden Sie unter „[Überwachte Aktionen](/admin/user-management/audited-actions)“.
 
 ### Auditprotokoll durchsuchen
 
diff --git a/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md
index 710a45bcc8..6425ed9788 100644
--- a/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/de-DE/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Wenn ein Benutzer das Unternehmen verlässt oder in eine andere Abteilung wechselt, sollten Sie dessen Zugriffsmöglichkeit auf {% data variables.product.product_location %} entfernen oder ändern.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 Wenn Mitarbeiter das Unternehmen verlassen, kannst Du ihre {% data variables.product.prodname_ghe_server %}-Konten sperren, um Benutzerlizenzen in Deiner {% data variables.product.prodname_enterprise %}-Lizenz freizugeben und gleichzeitig die von ihnen erstellten Problemtickets, Kommentare, Repositorys, „Gists“ (Ideen) und anderen Daten beizubehalten. Gesperrte Benutzer können sich weder bei Ihrer Instanz anmelden noch Code per Push-Vorgang übertragen oder abrufen.
diff --git a/translations/de-DE/content/admin/user-management/viewing-push-logs.md b/translations/de-DE/content/admin/user-management/viewing-push-logs.md
index ed58ce2a37..2745a87ecb 100644
--- a/translations/de-DE/content/admin/user-management/viewing-push-logs.md
+++ b/translations/de-DE/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 Push-Protokolleinträge zeigen:
diff --git a/translations/de-DE/content/code-security/getting-started/about-securing-your-repository.md b/translations/de-DE/content/code-security/getting-started/about-securing-your-repository.md
index f60e732f1c..d6c5b43b48 100644
--- a/translations/de-DE/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/de-DE/content/code-security/getting-started/about-securing-your-repository.md
@@ -22,11 +22,13 @@ The first step to securing a repository is to set up who can see and modify your
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 #### Available for all repositories
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **Security policy**
 
-  Make it easy for people to confidentially report security vulnerabilities they've found in your repository. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zum Repository hinzufügen](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)“.
+  Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zum Repository hinzufügen](/code-security/getting-started/adding-a-security-policy-to-your-repository)“.
+{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **Security advisories**
 
   Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage them to upgrade. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
diff --git a/translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..0f6fc4f4c6
--- /dev/null
+++ b/translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: Eine Sicherheitsrichtlinie zum Repository hinzufügen
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### Informationen zu Sicherheitsrichtlinien
+
+To give people instructions for reporting security vulnerabilities in your project,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+Du kannst eine Standard-Sicherheitsrichtlinie für Deine Organisation oder Dein Benutzerkonto erstellen. Weitere Informationen findest Du unter „[Eine Standard-Community-Unterstützungsdatei erstellen](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+{% endif %}
+
+{% tip %}
+
+**Tipp:** Um den Benutzern das Auffinden Deiner Sicherheitsrichtlinie zu erleichtern, kannst Du an anderen Stellen in Deinem Repository, z. B. in der README-Datei, auf die Datei _SECURITY.md_ verknüpfen. Weitere Informationen finden Sie unter „[Informationen zu README-Dateien](/articles/about-readmes/)“.
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+Nachdem jemand eine Sicherheitslücke in Deinem Projekt gemeldet hat, kannst Du {% data variables.product.prodname_security_advisories %} verwenden, um die Verwundbarkeit offen zu legen, sie zu korrigieren und entsprechende Informationen darüber zu veröffentlichen. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about {% data variables.product.prodname_security_advisories %}, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+### Eine Sicherheitsrichtlinie zum Repository hinzufügen
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**. ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Klicke auf **Start setup** (Einrichtung starten). ![Schaltfläche „Start setup“ (Einrichtung starten)](/assets/images/help/security/start-setup-security-policy-button.png)
+5. Füge in der neuen _SECURITY.md_-Datei Informationen zu den unterstützten Versionen Deines Projekts und Anweisungen zum Melden einer Schwachstelle hinzu.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### Weiterführende Informationen
+
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/de-DE/content/code-security/getting-started/index.md b/translations/de-DE/content/code-security/getting-started/index.md
index 0d6a630fe7..7411757dcf 100644
--- a/translations/de-DE/content/code-security/getting-started/index.md
+++ b/translations/de-DE/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### Inhaltsverzeichnis
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index e67e357a15..cf1ba8bf52 100644
--- a/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -27,13 +27,19 @@ topics:
 
 ### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories
 
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization.
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. You may need to enable {% data variables.product.prodname_GH_advanced_security %} to activate the button for "{% data variables.product.prodname_secret_scanning_caps %}". To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% if currentVersion == "free-pro-team@latest" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
 7. To the right of "{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
@@ -66,7 +72,7 @@ Du kannst eine *secret_scanning.yml*-Datei verwenden, um Verzeichnisse von {% da
 
     {% endnote %}
 
-Du kannst auch einzelne Warnungen von {% data variables.product.prodname_secret_scanning %} ignorieren. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)."
+Du kannst auch einzelne Warnungen von {% data variables.product.prodname_secret_scanning %} ignorieren. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)."
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/de-DE/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index 7932e3667b..463e287171 100644
--- a/translations/de-DE/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/de-DE/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -14,7 +14,7 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-### Warnungen verwalten
+### Managing {% data variables.product.prodname_secret_scanning %} alerts
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
@@ -49,3 +49,11 @@ Sobald ein Geheimnis an ein Repository übergeben wurde, solltest Du das Geheimn
 
 - Bei einem kompromittierten, persönlichen {% data variables.product.prodname_dotcom %}-Zugriffstoken, lösche das kompromittierte Token, erstelle ein neues Token und aktualisiere alle Dienste, die das alte Token verwenden. Weitere Informationen findest Du unter „[Ein persönliches Zugriffstoken für die Befehlszeile erstellen](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line).“
 - Für alle anderen Geheimnisse überprüfe zuerst, dass das zu {% data variables.product.product_name %} übergebene Geheimnis gültig ist. Falls ja, erstelle ein neues Geheimnis, aktualisiere alle Dienste, die das alte Geheimnis nutzen und lösche dann das alte Geheimnis.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.prodname_dotcom %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
diff --git a/translations/de-DE/content/code-security/secure-coding/about-code-scanning.md b/translations/de-DE/content/code-security/secure-coding/about-code-scanning.md
index a20f3aaa40..12b8f09d20 100644
--- a/translations/de-DE/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/de-DE/content/code-security/secure-coding/about-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -36,7 +38,7 @@ To get started with {% data variables.product.prodname_code_scanning %}, see "[S
 
 For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see  "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)."
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
 
@@ -48,17 +50,14 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 {% endif %}
 
-### About third-party code scanning tools
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### About third-party {% data variables.product.prodname_code_scanning %} tools
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+You can run third-party analysis tools within {% data variables.product.product_name %} using actions or within an external CI system. For more information, see "[Setting up code scanning for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
 
 ### Weiterführende Informationen
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/translations/de-DE/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..3a04b180a9
--- /dev/null
+++ b/translations/de-DE/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using actions. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case.
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Codebases with a compiled language that can be built with a single command or by running a single script.
+
+For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to:
+- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis.
+- Analyze more than one language in a repository.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
diff --git a/translations/de-DE/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/de-DE/content/code-security/secure-coding/about-integration-with-code-scanning.md
index 7cc8dda543..d4fe508d7e 100644
--- a/translations/de-DE/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/de-DE/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/de-DE/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/de-DE/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 0acaf09af0..b42e5d5acf 100644
--- a/translations/de-DE/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/de-DE/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md b/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md
index 81c0d0c9af..4717ec4ff8 100644
--- a/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md
@@ -14,42 +14,55 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
 ### About {% data variables.product.prodname_code_scanning %} configuration
 
-You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+{%- else %}
+"[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}.
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
 
 Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+You can write a configuration file for {% data variables.product.prodname_code_scanning %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. You can find a workflow you have added by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. Navigiere in Deinem Repository zu der Workflow-Datei, die Du bearbeiten möchtest.
+1. Um den Workflow-Editor zu öffnen, klickst Du in der oberen rechten Ecke der Dateiansicht auf {% octicon "pencil" aria-label="The edit icon" %}. ![Schaltfläche zum Editieren der Workflow-Datei](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. ![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
 
 For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
 ### Configuring frequency
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+You can scan code on a schedule or when specific events occur in a repository.
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+Scanning code on every push to the repository, and every time a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
 
 #### Scanning on push
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+If you use the default workflow, {% data variables.product.prodname_code_scanning %} will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)“.
+
+If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+{% note %}
+
+**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below.
+
+{% endnote %}
 
 #### Scanning pull requests
 
@@ -57,6 +70,8 @@ The default {% data variables.product.prodname_codeql_workflow %} uses the `pull
 
 For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
 
+If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
 #### Avoiding unnecessary scans of pull requests
 
 You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
@@ -74,7 +89,7 @@ on:
 
 {% note %}
 
-**Notes**
+**Hinweise:**
 
 * `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
 * For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
@@ -85,7 +100,7 @@ For more information about using `on:pull_request:paths-ignore` and `on:pull_req
 
 #### Scanning on a schedule
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+The default {% data variables.product.prodname_code_scanning %} workflow uses the `pull_request` event to trigger a code scan on the `HEAD` commit of a pull request. To adjust this schedule, edit the `cron` value in the workflow. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)“.
 
 {% note %}
 
@@ -93,7 +108,7 @@ If you use the default {% data variables.product.prodname_codeql_workflow %}, th
 
 {% endnote %}
 
-#### Example
+#### Beispiel
 
 The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
 
@@ -114,7 +129,7 @@ This workflow scans:
 
 ### Specifying an operating system
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
+If your code requires a specific operating system to compile, you can configure this in your workflow. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
 
 If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
 
@@ -127,7 +142,7 @@ jobs:
 
 {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+{% data variables.product.prodname_code_scanning_capc %} supports the latest versions of macOS, Ubuntu, and Windows. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
 
@@ -135,11 +150,11 @@ jobs:
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
-{% data reusables.code-scanning.specify-language-to-analyze %}
+{% data variables.product.prodname_code_scanning_capc %} automatically detects and scans code written in the supported languages.
 
 If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix.
 
@@ -176,39 +191,71 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. Ein Beispiel:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)."
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
 ### Running additional queries
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
+To add one or more query suites, add a `queries` section to your configuration file. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
 
 {% raw %}
 ``` yaml
@@ -220,11 +267,11 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 ```
 {% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+You can also run additional query suites by specifying these in a configuration file. Query suites are collections of queries, usually grouped by purpose or language.
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+You can run additional queries by specifying these in a configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For examples of configuration files, see "[Example configuration files](#example-configuration-files)."
 
 In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
 
@@ -238,7 +285,7 @@ In the following example, the `+` symbol ensures that the specified additional q
 ```
 {% endraw %}
 
-### Using a custom configuration file
+### Using a third-party code scanning tool
 
 As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
 
@@ -281,7 +328,7 @@ For more information about additional queries, see "[Running additional queries]
 
 #### Disabling the default queries
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+If you only want to run custom queries, you can disable the default security queries by adding `disable-default-queries: true` to your configuration file.
 
 #### Specifying directories to scan
 
@@ -299,14 +346,15 @@ paths-ignore:
 
 **Note**:
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)“.
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
 
 For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow file.
 
 #### Example configuration files
 
@@ -320,4 +368,4 @@ You can quickly analyze small portions of a monorepo when you modify code in spe
 
 ### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
+You can display code analysis from a third-party tool in {% data variables.product.prodname_dotcom %} by adding the `upload-sarif` action to your workflow. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
diff --git a/translations/de-DE/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..8da1e1c1d2
--- /dev/null
+++ b/translations/de-DE/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,203 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configuring CodeQL runner
+intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows.
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively.
+
+To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
+
+### Scanning pull requests
+
+Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code.
+
+To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch.
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`.
+
+{% endnote %}
+
+### Overriding automatic language detection
+
+The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data variables.product.prodname_code_scanning_capc %} automatically detects and scans code written in the supported languages.
+
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### Running additional queries
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
+
+If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file. If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to <nobr>`--queries`</nobr> with the `+` symbol. For examples of configuration files, see "[Example configuration files](#example-configuration-files)."
+
+In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### Using a third-party code scanning tool
+
+Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file.
+
+The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)“.
+
+Use the `--config-file` flag of the `init` command to specify the configuration file. The value of <nobr>`--config-file`</nobr> is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### Example configuration files
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+
+For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+
+For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first.
+
+The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command.
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)."
+
+### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+
+By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
+
+Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository.
+- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+### {% data variables.product.prodname_codeql_runner %} command reference
+
+The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags.
+
+#### `init`
+
+Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
+
+| Flag                             | Erforderlich | Input value                                                                                                                                                                         |
+| -------------------------------- |:------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                   |      ✓       | Name of the repository to initialize.                                                                                                                                               |
+| `--github-url`                   |      ✓       | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                   |
+| `--github-auth`                  |      ✓       | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                               |
+| `--languages`                    |              | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. |
+| `--queries`                      |              | Comma-separated list of additional queries to run, in addition to the default suite of security queries.                                                                            |
+| `--config-file`                  |              | Path to custom configuration file.                                                                                                                                                  |
+| `--codeql-path`                  |              | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy.   |
+| `--temp-dir`                     |              | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                       |
+| `--tools-dir`                    |              | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory.                    |
+| <nobr>`--checkout-path`</nobr> |              | The path to the checkout of your repository. The default is the current working directory.                                                                                          |
+| `--debug`                        |              | None. Prints more verbose output.                                                                                                                                                   |
+| `-h`, `--help`                   |              | None. Displays help for the command.                                                                                                                                                |
+
+#### `autobuild`
+
+Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps.
+
+| Flag                        | Erforderlich | Input value                                                                                                                                    |
+| --------------------------- |:------------:| ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--language`                |              | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. |
+| <nobr>`--temp-dir`</nobr> |              | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                  |
+| `--debug`                   |              | None. Prints more verbose output.                                                                                                              |
+| `-h`, `--help`              |              | None. Displays help for the command.                                                                                                           |
+
+#### `analyze`
+
+Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}.
+
+| Flag                               | Erforderlich | Input value                                                                                                                                                                                                                                                                                                                         |
+| ---------------------------------- |:------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     |      ✓       | Name of the repository to analyze.                                                                                                                                                                                                                                                                                                  |
+| `--commit`                         |      ✓       | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                                                                                                                     |
+| `--ref`                            |      ✓       | Name of the reference to analyze, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`.                                                                                              |
+| `--github-url`                     |      ✓       | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                                                                                                                   |
+| `--github-auth`                    |      ✓       | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                                                                                                               |
+| <nobr>`--checkout-path`</nobr>   |              | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                                                                                                          |
+| `--no-upload`                      |              | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}.                                                                                                                                                                                      |
+| `--output-dir`                     |              | Directory where the output SARIF files are stored. The default is in the directory of temporary files.                                                                                                                                                                                                                              |
+| `--ram`                            |              | Amount of memory to use when running queries. The default is to use all available memory.                                                                                                                                                                                                                                           |
+| <nobr>`--no-add-snippets`</nobr> |              | None. Excludes code snippets from the SARIF output. |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |              | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |              | Number of threads to use when running queries. The default is to use all available cores.                                                                                                                                                                                                                                           |
+| `--temp-dir`                       |              | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                                                                                                                                                                       |
+| `--debug`                          |              | None. Prints more verbose output.                                                                                                                                                                                                                                                                                                   |
+| `-h`, `--help`                     |              | None. Displays help for the command.                                                                                                                                                                                                                                                                                                |
+
+#### `hochladen`
+
+Uploads SARIF files to {% data variables.product.product_name %}.
+
+{% note %}
+
+**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools.
+
+{% endnote %}
+
+| Flag                             | Erforderlich | Input value                                                                                                                                                                                                                                   |
+| -------------------------------- |:------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   |      ✓       | SARIF file to upload, or a directory containing multiple SARIF files.                                                                                                                                                                         |
+| `--repository`                   |      ✓       | Name of the repository that was analyzed.                                                                                                                                                                                                     |
+| `--commit`                       |      ✓       | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                        |
+| `--ref`                          |      ✓       | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
+| `--github-url`                   |      ✓       | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                             |
+| `--github-auth`                  |      ✓       | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                         |
+| <nobr>`--checkout-path`</nobr> |              | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                    |
+| `--debug`                        |              | None. Prints more verbose output.                                                                                                                                                                                                             |
+| `-h`, `--help`                   |              | None. Displays help for the command.                                                                                                                                                                                                          |
diff --git a/translations/de-DE/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/de-DE/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index f446afa8e6..b578231a6d 100644
--- a/translations/de-DE/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/de-DE/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/de-DE/content/code-security/secure-coding/index.md b/translations/de-DE/content/code-security/secure-coding/index.md
index 88f3bd8f44..689c15108a 100644
--- a/translations/de-DE/content/code-security/secure-coding/index.md
+++ b/translations/de-DE/content/code-security/secure-coding/index.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### Inhaltsverzeichnis
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% link_in_list /running-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-the-codeql-action-for-compiled-languages %}
-    {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/de-DE/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/de-DE/content/code-security/secure-coding/integrating-with-code-scanning.md
index 88ab7921b4..cde681b9f8 100644
--- a/translations/de-DE/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/de-DE/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index cb650d0ed6..c165474931 100644
--- a/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
 title: Managing code scanning alerts for your repository
 shortTitle: Warnungen verwalten
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About alerts from {% data variables.product.prodname_code_scanning %}
@@ -60,7 +62,7 @@ You need write permission to view a summary of all the alerts for a repository o
 
 Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
 
 Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
 
@@ -70,14 +72,6 @@ Alerts may be fixed in one branch but not in another. You can use the "Branch" d
 ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### Closing an alert
-
-Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### Dismissing or deleting alerts
 
 There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
@@ -101,20 +95,9 @@ When you delete an alert:
 
 To dismiss or delete alerts:
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. Select the **Close** drop-down menu and click a reason for closing the alert.    
-   ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
 
    ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,8 +128,6 @@ To dismiss or delete alerts:
 
 If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
 
-{% endif %}
-
 ### Weiterführende Informationen
 
 - "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/de-DE/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/de-DE/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..0917d46d48
--- /dev/null
+++ b/translations/de-DE/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Running CodeQL CLI in your CI system
+shortTitle: Running CodeQL CLI
+intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Informationen zu {% data variables.product.prodname_codeql_cli %}
+
+You can use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_codeql_runner %} in your CI system, or {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% note %}
+
+**Note:** {% if currentVersion == "free-pro-team@latest" %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% endnote %}
+
+### Downloading the {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. Ein Beispiel:
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      Erforderlich
+    </th>
+    
+    <th>
+      Beispiel
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      Erforderlich
+    </th>
+    
+    <th>
+      Beispiel
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. For more information, see "<a href="/code-security/secure-coding/sarif-support-for-code-scanning">SARIF support for {% data variables.product.prodname_code_scanning %}</a>."
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      Erforderlich
+    </th>
+    
+    <th>
+      Beispiel
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. For more information, see "<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">Managing security and analysis settings for your repository</a>."
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### Weiterführende Informationen
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/de-DE/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/de-DE/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index 712e5472dd..a4014ec8c8 100644
--- a/translations/de-DE/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/de-DE/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -13,13 +13,19 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} with a containerized build
 
 If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.
 
-You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% else %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% endif %}
 
 ### Dependencies
 
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/de-DE/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..3124883202
--- /dev/null
+++ b/translations/de-DE/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Running CodeQL runner in your CI system
+shortTitle: Running CodeQL runner
+intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Informationen zu {% data variables.product.prodname_codeql_runner %}
+
+The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. The runner is more complex and less forgiving to set up than the CLI, and is recommended only if you need its capability to analyze multiple compiled languages with a single build, or to integrate with complex build processes. For more information, see "[About CodeQL code scanning in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
+
+{% note %}
+
+**Hinweis:**
+{% if currentVersion == "free-pro-team@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{% else %}
+* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)“.
+{% endif %}
+{% endnote %}
+
+### Downloading the {% data variables.product.prodname_codeql_runner %}
+
+You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+
+On Linux:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+Unter macOS:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
+
+### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system
+
+Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+In addition to this, each CI server also needs:
+
+- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+
+The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+
+1. Allow the CI servers access to https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
+
+### Calling the {% data variables.product.prodname_codeql_runner %}
+
+You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+
+1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
+1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
+
+For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
+
+You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
+
+To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### Basic example
+
+This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
+
+In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
+
+1. Check out the repository to analyze.
+1. Move into the directory where the repository is checked out.
+1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### Compiled language example
+
+This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
+
+1. Check out the repository to analyze.
+1. Move into the directory where the repository is checked out.
+1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place.
+
+{% endnote %}
+
+### Weiterführende Informationen
+
+- "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
diff --git a/translations/de-DE/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/de-DE/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index 2231facdec..915d2059f3 100644
--- a/translations/de-DE/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/de-DE/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: SARIF support for code scanning
 shortTitle: SARIF support
 intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for code scanning. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About SARIF support
@@ -22,7 +25,15 @@ SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https:
 
 To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-If your SARIF file doesn't include `partialFingerprints`, the `partialFingerprints` field will be calculated when you upload the SARIF file using {% data variables.product.prodname_actions %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+If your SARIF file doesn't include `partialFingerprints`, the `partialFingerprints` field will be calculated when you upload the SARIF file using {% data variables.product.prodname_actions %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
 
 {% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
@@ -122,6 +133,45 @@ A location within a programming artifact, such as a file in the repository or a
 | `region.endLine`       | **Required.** The line number of the last character in the region.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | `region.endColumn`     | **Required.** The column number of the character following the end of the region.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| Name | Beschreibung                                                                                                                                                                                                                          |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id` | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | kategorie         | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
+
 ### SARIF output file examples
 
 These example SARIF output files show supported properties and example values.
@@ -130,7 +180,6 @@ These example SARIF output files show supported properties and example values.
 
 This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties or don't include values, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}.
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ This SARIF output file has example values to show the minimum required propertie
 
 This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}.
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ This SARIF output file has example values to show all supported SARIF properties
   ]
 }
 ```
+{% endif %}
diff --git a/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
index 59ce037f25..ed1f02181f 100644
--- a/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
+++ b/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
@@ -17,6 +17,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/de-DE/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/de-DE/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index 5f9fb07186..d09e32ac45 100644
--- a/translations/de-DE/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/de-DE/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -14,13 +14,15 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} results on pull requests
 
 In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“
+If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or dismiss all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“
 
 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -44,18 +46,10 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
 
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Fixing an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 ### Dismissing an alert on your pull request
 
 An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
@@ -67,5 +61,3 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/de-DE/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..0cdbfc9d1d
--- /dev/null
+++ b/translations/de-DE/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshooting CodeQL runner
+intro: 'If you''re having problems with the {% data variables.product.prodname_codeql_runner %}, you can troubleshoot by using these tips.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### The `init` command takes too long
+
+Before the {% data variables.product.prodname_codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries.
+
+When you use the {% data variables.product.prodname_codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes. The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.product.prodname_codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again.
+
+To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command.
+
+### No code found during the build
+
+If the `analyze` command for the {% data variables.product.prodname_codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure.
+
+1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)."
+
+1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the build process. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command.
+   - On macOS and Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - On Windows, using the Command shell (`cmd`) or a batch file (`.bat`):
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - On Windows, using PowerShell:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead.
+
+   {% note %}
+
+   **Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different.
+
+   {% endnote %}
+
+1. You're analyzing a compiled language on macOS without using the `autobuild` command and you run the build steps yourself after the `init` step. If SIP (System Integrity Protection) is enabled, which is the default on recent versions of OSX, analysis might fail. To fix this, prefix the build command with the `$CODEQL_RUNNER` environment variable. For example, if your build command is `cmd arg1 arg2`, you should run `$CODEQL_RUNNER cmd arg1 arg2`.
+
+1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.product.prodname_codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
diff --git a/translations/de-DE/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/de-DE/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
index 8dfde8f279..f441a6173c 100644
--- a/translations/de-DE/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
+++ b/translations/de-DE/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -33,19 +35,22 @@ If an automatic build of code for a compiled language within your project fails,
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
         matrix:
           language: ['csharp', 'cpp', 'javascript']
 
+      steps:
       ...
-
-      - name: Initialize {% data variables.product.prodname_codeql %}
-        uses: github/codeql-action/init@v1
-        with:
-          languages: {% raw %}${{ matrix.language }}{% endraw %}
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: github/codeql-action/init@v1
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
   For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
@@ -150,29 +155,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/de-DE/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/de-DE/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index 13de289206..33dd50d648 100644
--- a/translations/de-DE/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/de-DE/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -24,18 +26,19 @@ If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` act
 
 You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. To upload results from third-party tools, you must use the Static Analysis Results Interchange Format (SARIF) 2.1.0 format. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
 
 - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
-- „[Einen Workflow-Lauf verwalten](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)“
-- {% data variables.product.prodname_dotcom %} will display {% data variables.product.prodname_code_scanning %} alerts from the uploaded SARIF file in your repository. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)").
+- „[Einen Workflow-Lauf verwalten](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)“ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- {% data variables.product.prodname_dotcom %} will display {% data variables.product.prodname_code_scanning %} alerts from the uploaded SARIF file in your repository. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").
 - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
 
 ### Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
 
-To upload a third-party SARIF file to {% data variables.product.prodname_dotcom %}, you'll need a {% data variables.product.prodname_actions %} workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+To upload a third-party SARIF file to {% data variables.product.prodname_dotcom %}, you'll need a {% data variables.product.prodname_actions %} workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
 Your workflow will need to use the `upload-sarif` action, which has input parameters that you can use to configure the upload. It has input parameters that you can use to configure the upload. The main input parameter you'll use is `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository. For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/HEAD/upload-sarif).
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Example workflow that runs the ESLint analysis tool
@@ -87,7 +92,7 @@ This example workflow runs anytime commits are pushed to the repository. The act
 
 The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Weiterführende Informationen
 
 - „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)“
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
+- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
 - "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
diff --git a/translations/de-DE/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/de-DE/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index 1610e347ef..1f2e2e0164 100644
--- a/translations/de-DE/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/de-DE/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/de-DE/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/de-DE/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 697ced0a12..5f4e612f47 100644
--- a/translations/de-DE/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/de-DE/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -43,7 +43,7 @@ Publishing the details of a security vulnerability doesn't make maintainers look
 
 The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
 
- If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
+ If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
 
  If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
 
@@ -55,7 +55,7 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
 
- If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
+ If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
 
  As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
diff --git a/translations/de-DE/content/code-security/security-advisories/index.md b/translations/de-DE/content/code-security/security-advisories/index.md
index 8a47a5e99e..fd9c530f82 100644
--- a/translations/de-DE/content/code-security/security-advisories/index.md
+++ b/translations/de-DE/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### Inhaltsverzeichnis
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
index 46e39a99f7..a814da66d3 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
 title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
+intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository.'
 redirect_from:
   - /articles/about-security-alerts-for-vulnerable-dependencies
   - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
@@ -12,6 +12,7 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
 
 ### About vulnerable dependencies
@@ -22,12 +23,12 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 ### Detection of vulnerable dependencies
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %}
+- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)."
 
 {% data reusables.repositories.dependency-review %}
 
@@ -39,11 +40,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
 ### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
-{% else %}
-### Sicherheitsmeldungen für angreifbare Abhängigkeiten
-{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
@@ -56,41 +53,28 @@ For information about permission requirements for actions related to {% data var
 {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
-{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
-{% endif %}
-
 {% warning %}
 
 **Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. Diese Funktionen ersetzen nicht die menschliche Überprüfung jeder Abhängigkeit auf potenzielle Sicherheitsrisiken oder andere Probleme. Daher empfehlen wir, einen Sicherheitsdienst zu konsultieren oder bei Bedarf eine gründliche Überprüfung der Sicherheitsrisiken durchzuführen.
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Access to {% data variables.product.prodname_dependabot %} alerts
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Standardmäßig senden wir Sicherheitsmeldungen an Personen mit Administratorrechten in den betroffenen Repositorys. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
-{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
-{% endif %}
+You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Weiterführende Informationen
diff --git a/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index 7f67174916..8ec1f62916 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -35,6 +35,7 @@ You specify how often to check each ecosystem for new versions in the configurat
 If you've enabled security updates, you'll sometimes see extra pull requests for security updates. These are triggered by a {% data variables.product.prodname_dependabot %} alert for a dependency on your default branch. {% data variables.product.prodname_dependabot %} automatically raises a pull request to update the vulnerable dependency.
 
 ### Supported repositories and ecosystems
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)."
 
diff --git a/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index 23244a1fe2..a897ba49a1 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -164,7 +164,7 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Use the `allow` option to customize which dependencies are updated. This has no impact on security updates for vulnerable dependencies. You can use the following options:
+Use the `allow` option to customize which dependencies are updated. This applies to both version and security updates. You can use the following options:
 
 - `dependency-name`—use to allow updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId`, for example: `org.kohsuke:github-api`.
 - `dependency-type`—use to allow updates for dependencies of specific types.
@@ -445,12 +445,12 @@ updates:
 
 #### `rebase-strategy`
 
-By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects conflicts. Use `rebase-strategy` to disable this behavior.
+By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. Use `rebase-strategy` to disable this behavior.
 
 Available rebase strategies
 
 - `disabled` to disable automatic rebasing.
-- `auto` to use the default behavior and rebase open pull requests when conflicts are detected.
+- `auto` to use the default behavior and rebase open pull requests when changes are detected.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -473,11 +473,11 @@ To allow {% data variables.product.prodname_dependabot %} to access a private pa
 
 To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution).
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -493,11 +493,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -716,7 +716,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
@@ -730,6 +730,7 @@ You use the following options to specify access settings. Registry settings must
 | `url`                                                                                                  | The URL to use to access the dependencies in this registry. The protocol is optional. If not specified, `https://` is assumed. {% data variables.product.prodname_dependabot %} adds or ignores trailing slashes as required.                                                   |
 | `Benutzername`                                                                                         | The username that {% data variables.product.prodname_dependabot %} uses to access the registry.                                                                                                                                                                                 |
 | `Passwort`                                                                                             | A reference to a {% data variables.product.prodname_dependabot %} secret containing the password for the specified user. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)." |
+| `Schlüssel`                                                                                            | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access key for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."     |
 | `Token`                                                                                                | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access token for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."   |
 | `replaces-base`                                                                                        | For registries with `type: python-index`, if the boolean value is `true`, pip resolves dependencies by using the specified URL rather than the base URL of the Python Package Index (by default `https://pypi.org/simple`).                                                     |
 
@@ -766,6 +767,19 @@ registries:
 ```
 {% endraw %}
 
+The `docker-registry` type can also be used to pull from Amazon ECR using static AWS credentials.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 The `git` type supports username and password.
@@ -781,6 +795,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+The `hex-organization` type supports organization and key.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 The `maven-repository` type supports username and password, or token.
diff --git a/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index ad62dc6ad8..7f20829106 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
 title: Configuring notifications for vulnerable dependencies
 shortTitle: Benachrichtigungen konfigurieren
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+intro: 'Optimize how you receive notifications about {% data variables.product.prodname_dependabot %} alerts.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
@@ -11,48 +11,41 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
+
 ### About notifications for vulnerable dependencies
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
+When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %}
+By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.{% endif %}
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
 
 You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
-{% else %}
-  ![Optionen für Sicherheitswarnungen](/assets/images/help/notifications-v2/security-alerts-options.png)
-{% endif %}
 
 {% note %}
 
-**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. Weitere Informationen findest Du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} alerts. Weitere Informationen findest Du unter „[Benachrichtigungen über Deinen Posteingang verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications).“
 
 ### How to reduce the noise from notifications for vulnerable dependencies
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index 2a87332ce3..fde9bd044d 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -18,7 +18,7 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c
 
 {% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)."
 
-{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
+{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
 
 ### Enabling {% data variables.product.prodname_dependabot_version_updates %}
 
diff --git a/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index 56b264e3e1..3dd4a79eb3 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -15,6 +15,8 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
@@ -50,19 +52,6 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
-
-![Abhängigkeitsdiagramm](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view.
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### Dependents view
 
@@ -113,8 +102,8 @@ If a manifest or lock file is not processed, its dependencies are omitted from t
 
 ### Weiterführende Informationen
 
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“{% if currentVersion == "free-pro-team@latest" %}
 - „[Einblicke für Ihre Organisation anzeigen ](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)“
-- „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“
 - „[Grundlegendes zur Verwendung und zum Schutz Ihrer Daten durch {% data variables.product.product_name %}](/github/understanding-how-github-uses-and-protects-your-data)“
 {% endif %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/index.md b/translations/de-DE/content/code-security/supply-chain-security/index.md
index c62ac967a8..642ad099f8 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/index.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 53748403ac..06ae9893a9 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -17,18 +17,18 @@ The results of dependency detection reported by {% data variables.product.produc
 
 {% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following:
 
-*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 *   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
-*   {% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
 
-    {% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is discovered and added to the advisory database.
+    {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% if currentVersion ver_gt "enterprise-server@2.22" %} and synchronized to {% data variables.product.prodname_ghe_server %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." |
 
 ### Why don't I get vulnerability alerts for some ecosystems?
 
-{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot %} security updates are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot %} alerts are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
 
-It's worth noting that [{% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems.
+It's worth noting that {% data variables.product.prodname_dotcom %} Security Advisories may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}
 
 **Check**: Does the uncaught vulnerability apply to an unsupported ecosystem?
 
@@ -36,9 +36,9 @@ It's worth noting that [{% data variables.product.prodname_dotcom %} Security Ad
 
 The dependency graph includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
 
-{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% data variables.product.prodname_dependabot %} security updates only suggests a change where it can directly "fix" the dependency, that is, when these are:
+{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
 * Direct dependencies explicitly declared in a manifest or lockfile
-* Transitive dependencies declared in a lockfile
+* Transitive dependencies declared in a lockfile{% endif %}
 
 The dependency graph doesn't include “loose” dependencies. “Loose” dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile.
 
@@ -84,6 +84,7 @@ Some third-party tools use uncurated CVE data that isn't checked or filtered by
 
 Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant.
 
+{% if currentVersion == "free-pro-team@latest" %}
 ### 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.
@@ -97,10 +98,11 @@ When you click to display the alert details, you can see how many vulnerabilitie
 ![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
 **Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers.
+{% endif %}
 
 ### Weiterführende Informationen
 
 - "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“
-- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/de-DE/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..7c186aac17
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Upgrading from Dependabot.com to GitHub-native Dependabot
+intro: You can upgrade to GitHub-native Dependabot by merging a pull request that will allow your dependencies to continue being updated.
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot before then.
+
+After that date, any open pull requests from Dependabot Preview will remain open, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations.
+
+{% endwarning %}
+
+### About upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Dependabot Preview has been built directly into {% data variables.product.prodname_dotcom %}, so you can use {% data variables.product.prodname_dependabot %} alongside all the other functionality in {% data variables.product.prodname_dotcom %} without having to install and use a separate application. By migrating to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, we can also focus on bringing lots of exciting new features to {% data variables.product.prodname_dependabot %}, including more [ecosystem updates](https://github.com/github/roadmap/issues/150), [improved notifications](https://github.com/github/roadmap/issues/133), and {% data variables.product.prodname_dependabot %} support for [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) and [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Differences between Dependabot Preview and {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+While most of the Dependabot Preview features exist in {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, a few remain unavailable:
+- **Live updates:** We hope to bring these back in the future. For now, you can run {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} daily to catch new packages within one day of release.
+- **PHP environment variable registries:** For now, you can use {% data variables.product.prodname_actions %} to fetch dependencies from these registries.
+- **Auto-merge:** We always recommend verifying your dependencies before merging them; therefore, auto-merge will not be supported for the foreseeable future. For those of you who have vetted your dependencies, or are only using internal dependencies, we recommend adding third-party auto-merge apps, or setting up GitHub Actions to merge.
+
+In {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, you can configure all version updates using the configuration file. This file is similar to the Dependabot Preview configuration file with a few changes and improvements that will be automatically included in your upgrade pull request. For more information about the upgrade pull request, see "[Upgrading to GitHub-native Dependabot](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+To see update logs for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} that were previously on the Dependabot.com dashboard:
+
+  1. Navigate to your repository’s **Insights** page.
+  2. Click **Dependency graph** to the left.
+  3. Click **{% data variables.product.prodname_dependabot %}**.
+
+For more information about version updates with {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, see "[About Dependabot version updates](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+### Upgrading to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} requires you to merge the *Upgrade to GitHub-native Dependabot* pull request in your repository. This pull request includes the updated configuration file needed for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}.
+
+If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
+
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
+
+If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/de-DE/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/de-DE/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index 1ae859690c..93816905de 100644
--- a/translations/de-DE/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/de-DE/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}. Mithilfe des Dropdownmenü kannst Du die Liste der Warnungen sortieren, und Du kannst auf bestimmte Warnungen klicken, um weitere Details anzuzeigen. 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 %}{% if currentVersion == "free-pro-team@latest" %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. Mithilfe des Dropdownmenü kannst Du die Liste der Warnungen sortieren, und Du kannst auf bestimmte Warnungen klicken, um weitere Details anzuzeigen. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
 
+{% if currentVersion == "free-pro-team@latest" %}
 You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ 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.
+{% endif %}
 
 ### Viewing and updating vulnerable dependencies
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ You can enable automatic security updates for any repository that uses {% data v
 1. Wenn Sie zum Aktualisieren Ihrer Abhängigkeit und zum Beheben Ihrer Schwachstelle bereit sind, mergen Sie den 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](/github/administering-a-repository/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, use 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 currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Klicke auf die Warnung, die angezeigt werden soll. ![In der Liste ausgewählte Warnung](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency.
+1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, click the **Dismiss** drop-down, and select a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. Click the version number of the vulnerable dependency to display detailed information. ![Detailed information on the vulnerable dependency](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert.
+1. The banner at the top of the **Dependencies** tab is displayed until all the vulnerable dependencies are resolved or you dismiss it. Click **Dismiss** in the top right corner of the banner and select a reason for dismissing the alert. ![Dismiss security banner](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### Weiterführende Informationen
 
-- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"
+- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
 - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/de-DE/content/codespaces/about-codespaces.md b/translations/de-DE/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..fdab6d75d8
--- /dev/null
+++ b/translations/de-DE/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: Über Codespaces
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Informationen zu {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![Ein Open-Codespace](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Entwickler können von überall her einen Beitrag leisten, von jedem Rechner aus, einschließlich Tablets oder Chromebooks, und es besteht keine Notwendigkeit, lokale Kopien des geistigen Eigentums zu verwalten. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### Informationen zur Abrechnung für {% data variables.product.prodname_codespaces %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %} Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)“.
+
+### Der Beta-Phase beitreten
+
+Eine begrenzte Anzahl von Personen wird eingeladen, der Beta-Phase beizutreten. Weitere Informationen zum Beitritt zur Warteliste findest Du unter „[Für Codespaces-Beta anmelden](https://github.com/features/codespaces/signup)".
+
+### Kontaktiere uns zu {% data variables.product.prodname_codespaces %}
+
+Wenn Du bei der Verwendung von {% data variables.product.prodname_codespaces %} Probleme entdeckst, lies bitte „[Fehlerbehebung Deines Codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
+
+If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the [Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) discussion.
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..f621a80494
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: About billing for Codespaces
+intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..75be9e6f73
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Allowing your codespace to access a private image registry
+intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry.
+
+When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)."
+
+For example, if you had a private image registry in Azure, you could create the following secrets:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/index.md b/translations/de-DE/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..fec23831a3
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: Referenz
+intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..acea2d4a85
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: Fehlerbehebung Deines Codespace
+intro: Use this guide to help you troubleshoot common issues with your codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Known Limitations
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### {% data variables.product.prodname_vscode %} troubleshooting
+
+Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.
+
+
+### Configuration troubleshooting
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+This codespace is currently running in recovery mode due to a container error.
+```
+
+Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
+
+### dotfiles troubleshooting
+
+- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles.
+- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned.
+  - If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
+  - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
+- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**.
+
+
+### Browser troubleshooting
+
+Wenn Du bei der Verwendung eines nicht Chromium-basierten Browsers auf Probleme stößt, versuche auf einen Chromium-basierenden Browser zu wechseln oder suche nach bekannten Issues für Deinen Browser im `microsoft/vscode`-Repository, indem Du nach Problemen suchst, die mit dem Namen Deines Browsers gekennzeichnet sind, wie etwa [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) oder [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari).
+
+Wenn Du bei der Verwendung eines Chromium-basierten Browsers auf Probleme stößt, kannst Du im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues)-Repository.prüfen, ob du ein anderes bekanntes Problem mit {% data variables.product.prodname_vscode %} erlebst.
+
+### Container storage troubleshooting
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.
+
+- Remove packages that are no longer by using `sudo apt autoremove`
+- Clean the apt cache by using `sudo apt clean`
+- Delete unneeded files like build artifacts and logs (these are very project-dependent)
+- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10`
+
+More destructive options:
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes)
+- Remove untracked files from working tree: `git clean -i`
+
+### Kontakt
+
+Wenn Du immer noch Hilfe benötigst, kannst Du uns kontaktieren. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)."
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..75ed888220
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Erstellen eines Codespace
+intro: 'Du kannst einen Codespace in einem Repository-Branch erstellen, um Online zu entwickeln.'
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Über die Codespace Erstellung
+
+You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)."
+
+
+When you create a codespace, a number of steps happen to enable full access to your development environment.
+
+- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
+- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
+- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+- Your Docker container, `docker-compose`, or other initialization is run.
+- At this point, the codespace is marked as available and you can connect.
+- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up.
+  - The codespace shares ports added in the `devcontainer.json` file.
+  - The codespace runs anything specified in `postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Finally, the codespace does a full clone of the repo so you have full access to it.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### Erstellen eines Codespace
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Benutze das „Branch"-Dropdownmenü unterhalb des Repository-Namens und wähle den Branch, für den Du einen Codespace erstellen willst.
+
+  ![Dropdownmenü „Branch"](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. Benutze das {% octicon "download" aria-label="The download icon" %} **Code**-Dropdownmenü unterhalb des Repository-Namens und wähle **Open with Codespaces** (Eröffnen mit Codespaces).
+
+  ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..dd74d3eecc
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: Einen Codespace löschen
+intro: 'Du kannst einen Codespace löschen, wenn Du ihn nicht länger benötigst.'
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+
+2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** ![Schaltfläche „Delete" (Löschen)](/assets/images/help/codespaces/delete-codespace.png)
+
+### Deleting a codespace in {% data variables.product.prodname_vscode %}
+
+For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)."
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..51fca79f66
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: In einem Codespace entwickeln
+intro: 'Du kannst einen Codespace auf {% data variables.product.product_name %} eröffnen und dann mithilfe der {% data variables.product.prodname_vscode %}-Funktionen entwickeln.'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About development with {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Side Bar - By default, this area shows your project files in the Explorer.
+2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
+3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
+4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
+5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
+
+For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} Weitere Informationen findest Du unter „[Fehlerbehebung Deines Codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
+
+#### Personalizing your codespace
+
+{% data reusables.codespaces.about-personalization %} Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Konto personalisieren](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)."
+
+{% data reusables.codespaces.apply-devcontainer-changes %} Weitere Informationen findest du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
+
+#### Running your app from a codespace
+{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)."
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Navigating to an existing codespace
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. Klicke auf den Namen des Codespace, in dem Du entwickeln möchtest. ![Name des Codespace](/assets/images/help/codespaces/click-name-codespace.png)
+
+Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..63e2a73681
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Forwarding ports in your codespace
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About forwarded ports
+
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application.
+
+When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. For example, if an application outputs `http://127.0.0.1:4000` or `http://localhost:4000` to the console, the log would automatically convert the output to a clickable URL for port 4000.
+
+![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration.
+
+### Forwarding a port
+
+You can manually forward a port that wasn't forwarded automatically.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png)
+1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
+
+### Labeling a port
+
+You can label a port to make the port more easily identifiable in a list.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### Sharing a port
+
+If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png)
+1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Send the copied URL to the person you want to share the port with.
+
+### Adding a port to the codespace configuration
+
+You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..c8c9d3738f
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: In einem Codespace entwickeln
+intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..406824a7cf
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: Using Codespaces in Visual Studio Code
+intro: 'Du kannst über {% data variables.product.prodname_vscode %} direkt in Deinem Codespace entwickeln, indem Du die {% data variables.product.prodname_github_codespaces %}-Erweiterung mit Deinem Konto auf {% data variables.product.product_name %} verbindest.'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Vorrausetzungen
+
+To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later.
+
+Du kannst {% data variables.product.prodname_vs %}-Marketplace verwenden, um die [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)-Erweiterung zu installieren. Weitere Informationen findest Du unter „[Marketplace-Erweiterung](https://code.visualstudio.com/docs/editor/extension-gallery)" in der {% data variables.product.prodname_vscode %}-Dokumentation.
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Klicke auf **Sign in to view {% data variables.product.prodname_dotcom %}...** (Anmelden zur Anzeige von...). ![Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen).
+4. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![Die {% data variables.product.prodname_codespaces %}-Kopfzeile](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. Klicke auf **Sign in to view {% data variables.product.prodname_codespaces %}...** (Anmelden zur Anzeige von...). ![Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen).
+5. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen.
+
+{% endwindows %}
+
+### Creating a codespace in {% data variables.product.prodname_vscode %}
+
+After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_github_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Click the machine type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png)
+### Einen Codespace in {% data variables.product.prodname_vscode %} eröffnen
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Under "Codespaces", click the codespace you want to develop in.
+3. Klicke auf das Symbol „Connect to Codespace" (Verbinde zu Codespace). ![Symbol „Connect to Codespace" (Verbinde mit Codespace) in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### Changing the machine type in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+You can change the machine type of your codespace at any time.
+
+1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`).
+2. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. Click the codespace that you want to change. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. Choose the machine type you want to use. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts.
+
+### Deleting a codespace in {% data variables.product.prodname_vscode %}
+
+1. Under "Codespaces", right-click the codespace you want to delete.
+2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..11d7279d92
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About source control in {% data variables.product.prodname_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+### Creating or switching branches
+
+1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**.
+1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace.
+
+{% endtip %}
+
+### Pulling changes from the remote repository
+
+You can pull changes from the remote repository into your codespace at any time.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. In the drop-down menu, click **Pull**.
+
+If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+### Setting your codespace to automatically fetch new changes
+
+You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
+
+If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
+
+1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Klicke auf **Create** (Erstellen).
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..0355417f9b
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Getting started with your C# (.NET) project in Codespaces
+shortTitle: Getting started with your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Einführung
+
+This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Vorrausetzungen
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Nächste Schritte:
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..55c1c30565
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Getting started with your Java project in Codespaces
+shortTitle: Getting started with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Einführung
+
+This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Vorrausetzungen
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Nächste Schritte:
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..1117c53786
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Getting started with your Node.js project in Codespaces
+shortTitle: Getting started with your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Einführung
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Vorrausetzungen
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Nächste Schritte:
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..d3ee56ad84
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Getting started with your Python project in Codespaces
+shortTitle: Getting started with your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Einführung
+
+This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Vorrausetzungen
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Nächste Schritte:
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..013f96d508
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: Getting Started with {% data variables.product.prodname_codespaces %}
+intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/de-DE/content/codespaces/guides.md b/translations/de-DE/content/codespaces/guides.md
new file mode 100644
index 0000000000..b719006750
--- /dev/null
+++ b/translations/de-DE/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: Leitfäden
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/de-DE/content/codespaces/index.md b/translations/de-DE/content/codespaces/index.md
new file mode 100644
index 0000000000..428d92acb6
--- /dev/null
+++ b/translations/de-DE/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc'
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..1034377b45
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing Codespaces for your organization
+intro: 'You can manange and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..f3d0f9eb29
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Managing access and security for your organization's codespaces
+shortTitle: Managing access and security for your organization
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Organization owners can manage which repositories a codespace can access.
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.
+
+To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
new file mode 100644
index 0000000000..846a64b7e1
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Managing encrypted secrets for your repository and organization for Codespaces
+shortTitle: Managing secrets for your repository and organization
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Einschränkungen für Geheimnisse
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+Geheimnisse sind auf 64 KB beschränkt.
+
+### Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. At the top of the page, click **New repository secret**.
+1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein.
+1. Geben Sie den Wert für Ihr Geheimnis ein.
+1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen).
+
+### Adding secrets for an organization
+
+Beim Erstellen eines geheimen Schlüssels in einer Organisation können Sie eine Richtlinie verwenden, um einzuschränken, welche Repositorys auf diesen geheimen Schlüssel zugreifen können. Sie können z. B. Zugriff auf alle Repositorys gewähren oder den Zugriff auf nur private Repositorys oder eine angegebene Liste von Repositorys beschränken.
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. At the top of the page, click **New organization secret**.
+1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein.
+1. Geben Sie den **Value** für Ihr Geheimnis ein.
+1. Wählen Sie im **Repository-Zugriff** Dropdownliste eine Zugriffsrichtlinie aus. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen).
+
+### Überprüfen des Zugriffs auf Geheimnisse auf Organisationsebene
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Die Liste der Geheimnisse enthält alle konfigurierten Berechtigungen und Richtlinien. Ein Beispiel: ![Geheimliste](/assets/images/help/settings/actions-org-secrets-list.png)
+1. Weitere Informationen zu den konfigurierten Berechtigungen für jeden geheimen Schlüssel finden Sie unter **Aktualisieren**.
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..f8c2c9ac71
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.
+permissions: To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..c438a70311
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing your organization's audit logs for Codespaces
+shortTitle: Reviewing your organization's audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)."
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/index.md b/translations/de-DE/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..2241dd5ecf
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..9e34c2e376
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### About encrypted secrets for {% data variables.product.prodname_codespaces %}
+
+You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets.
+
+- Personal access tokens to cloud services
+- Service principals
+- Subscription identifiers
+- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Einschränkungen für Geheimnisse
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+Geheimnisse sind auf 64 KB beschränkt.
+
+### Adding a secret
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. Under "Name", type a name for your secret. !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen).
+
+### Editing a secret
+
+You can update the value of an existing secret, and you can change which repositories can access a secret.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. Klicke auf **Save changes** (Änderungen speichern).
+
+### Deleting a secret
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. Lies die Warnung, dann klicke auf **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..c9492f1760
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: Managing GPG verification for Codespaces
+intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)."
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..f7e213e258
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)."
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
diff --git a/translations/de-DE/content/codespaces/quickstart.md b/translations/de-DE/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..ce704597cf
--- /dev/null
+++ b/translations/de-DE/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Einführung
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. Benutze das {% octicon "download" aria-label="The download icon" %} **Code**-Dropdownmenü unterhalb des Repository-Namens und wähle **Open with Codespaces** (Eröffnen mit Codespaces).
+
+  ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..c2e18a3030
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,142 @@
+---
+title: Codespace für Dein Projekt konfigurieren
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### Dockerfile
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Follow the prompts to customize your definition.
+1. Klicke auf **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### Erstellen einer benutzerdefinierten Codespace-Konfiguration
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+Du kannst die Standard-Editor-Einstellungen für {% data variables.product.prodname_vscode %} an zwei Orten festlegen.
+
+* Editor-Einstellungen, die in `.vscode/settings.json` definiert sind, werden als _Workspace_-bezogene Einstellungen im Codespace angewendet.
+* Editor--Einstellungen, die im `settings`-Schlüssel in der `devcontainer.json`-Datei definiert sind, werden als as _Remote [Codespaces]_-bezogene Einstellungen im Codespace angewendet.
+
+After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)."
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### Applying changes to your configuration
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}
+!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - To diagnose the error by reviewing the creation logs, click **View creation log**.
+   - To fix the errors identified in the logs, update your `devcontainer.json` file.
+   - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/de-DE/content/codespaces/setting-up-your-codespace/index.md b/translations/de-DE/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..5e2f53075a
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: Codespaces für Dein Konto personalisieren
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+Projektbetreuer können auch eine Standardkonfiguration definieren, die für jeden Codespace eines Repositorys gilt, egal wer ihn erstellt. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+'Dotfiles' sind Dateien und Verzeichnisse auf Unix-ähnlichen Systemen, die mit `.` beginnen und die die Konfiguration von Anwendungen und Shells auf Deinem System kontrollieren. Du kannst Deine 'dotfiles' in einem Repository auf {% data variables.product.prodname_dotcom %} speichern und verwalten. Für Ratschläge und Tutorials dazu, was Du in Deinem `dotfiles`-Repository hinzufügen solltest, siehe [GitHub does dotfiles](https://dotfiles.github.io/) (GitHub benutzt 'dotfiles').
+
+Wenn Dein Benutzerkonto auf {% data variables.product.prodname_dotcom %} ein öffentliches Repository mit Namen `dotfiles` besitzt, wird {% data variables.product.prodname_dotcom %} dieses Repository automatisch nutzen, um Deine Codespace-Umgebung zu personalisieren. Private `dotfiles`-Repositorys sind momentan nicht unterstützt.
+
+Dein `dotfiles`-Repository könnte Deine Shell-Aliase und -Voreinstellungen beinhalten, sämtliche Werkzeuge, die Du installieren möchtest, oder jede andere Codespace-Personalisierung, die Du machen willst.
+
+Wenn Du einen neuen Codespace erstellst, klont {% data variables.product.prodname_dotcom %} Dein `dotfiles`-Repository in die Codespace-Umgebung und sucht nach einer der folgenden Dateien, um die Umgebung einzurichten.
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+Wenn keine dieser Dateien gefunden wird, werden Dateien oder Ordner in `dotfiles`, die mit einem `.` beginnen, symbolisch zum `~`- or `$HOME`-Verzeichnis des Codespace verknüpft.
+
+Änderungen an Deinem `dotfiles`-Repository gelten nur für neue Codespaces und verändern bestehende Codespaces nicht.
+
+{% note %}
+
+**Hinweis:** Derzeit unterstützt {% data variables.product.prodname_codespaces %} kein personalisieren der _Benutzer_ Einstellungen für den {% data variables.product.prodname_vscode %}-Editor mit Deinem `dotfiles`-Repository. Du kannst Standardeinstellungen für den _Arbeitsbereich _ und die _Remote [Codespaces]_ für ein bestimmtes Projekt in einem Projekt-Repository festlegen. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)."
+
+{% endnote %}
+
+You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)."
+
+### Weiterführende Informationen
+
+* „[Ein neues Repository erstellen](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md
index b3b2aba1fb..f16e1ce3f0 100644
--- a/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ Mit Wikis können Sie Inhalte wie überall sonst auf {% data variables.product.p
 
 Sie können Wikis direkt auf {% data variables.product.product_name %} bearbeiten, oder Sie können Wiki-Dateien lokal bearbeiten. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository. Weitere Informationen findest Du unter „[Zugriffsberechtigungen für Wikis ändern](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)“.
 
+{% note %}
+
+**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository.
+
+{% endnote %}
+
 ### Weiterführende Informationen
 
 - „[Wiki-Seiten hinzufügen oder bearbeiten](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)“
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index 53db68ecb9..b29ad751ae 100644
--- a/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ Außerdem können blockierte Benutzer in den Repositorys Deiner Organisation nic
 ### Benutzer in den Einstellungen der Organisation blockieren
 
 1. Um ein Mitglied einer Organisation zu blockieren, [entferne den Benutzer](/articles/removing-a-member-from-your-organization) zunächst aus der Organisation.
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. Gib unter „Block a user“ (Einen Benutzer blockieren) den Benutzernamen der Person ein, die Du blockieren möchtest. ![Feld für Benutzernamen](/assets/images/help/organizations/org-block-username-field.png)
 7. Wenn Du die Sperre zeitlich beschränken möchtest, wähle aus dem Dropdownmenü mit den Sperr-Optionen den Zeitraum aus, für den Du den Benutzer blockieren möchtest. ![Dropdownmenü „Block options“ (Optionen für das Blockieren)](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
index 0f7cbe60ae..53b4cdb5e5 100644
--- a/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -57,7 +57,7 @@ Wenn „gemeldeter Inhalt" für ein öffentliches Repository aktiviert ist, kann
 
 - „[Dein Projekt für sinnvolle Beiträge einrichten](/communities/setting-up-your-project-for-healthy-contributions)“
 - „[Vorlagen benutzen, um hilfreiche Issues und Pull Requests zu ermutigen](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)"
-- "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %}
+- „[Störende Kommentare verwalten](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %}
 - „[Deine Sicherheit auf {% data variables.product.prodname_dotcom %} aufrechterhalten](/communities/maintaining-your-safety-on-github)"
 - „[Interaktionen in Deinem Repository einschränken](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)“{% endif %}
 - „[Änderungen an einem Kommentar verfolgen](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)“
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index 83effdc7ef..8acf51c7e2 100644
--- a/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,9 +28,9 @@ Wenn Du beim blockieren des Benutzers einen bestimmten Zeitraum für die Sperre
 
 ### Sperre eines Benutzers in den Organisationseinstellungen aufheben
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Klicke unter „Blocked users“ (Blockierte Benutzer) neben dem Benutzer, dessen Sperre Du aufheben möchtest, auf **Unblock** (Entsperren). ![Schaltfläche „Unblock User" (Sperre des Benutzers aufheben)](/assets/images/help/organizations/org-unblock-user-button.png)
 
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index 668578a717..15175263f5 100644
--- a/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,9 +10,9 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Überprüfe unter „Blocked users“ (Blockierte Benutzer) die Liste der Benutzer, die in Deiner Organisation gesperrt sind. ![Liste der gesperrten Benutzer](/assets/images/help/settings/list-of-blocked-users-for-org.png)
 
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index d3ec2461ca..6ece08ff13 100644
--- a/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -28,9 +28,9 @@ Organization owners can also block users for a specific amount of time. Wenn die
 
 ### Interaktionen in Deiner Organisation begrenzen
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the organization settings sidebar, click **Moderation settings**. !["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. Under "Moderation settings", click **Interaction limits**. !["Interaction limits" in the organization settings sidebar](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md
index f6b737daa5..51e5865289 100644
--- a/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md
@@ -32,7 +32,7 @@ Um nach gesperrten Unterhaltungen in einem nicht archivierten Repository zu such
 
 - „[Dein Projekt für sinnvolle Beiträge einrichten](/communities/setting-up-your-project-for-healthy-contributions)“
 - „[Vorlagen benutzen, um hilfreiche Issues und Pull Requests zu ermutigen](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)"
-- "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %}
+- „[Störende Kommentare verwalten](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %}
 - „[Deine Sicherheit auf {% data variables.product.prodname_dotcom %} aufrechterhalten](/communities/maintaining-your-safety-on-github)"
 - „[Missbrauch oder Spam melden](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)“
 - „[Interaktionen in Deinem Repository einschränken](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md
index f4a965b1a9..b3649070f2 100644
--- a/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md
@@ -32,5 +32,5 @@ Wenn Du sensible Informationen aus dem Änderungsverlauf eines Kommentars lösch
 
 ### Weiterführende Informationen
 
-{% if currentVersion == "free-pro-team@latest" %}- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}- „[Missbrauch oder Spam melden](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)“{% endif %}
 - „[Kommentar bearbeiten](/articles/editing-a-comment)“
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 4eaa73bebd..03dd1857bb 100644
--- a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -29,14 +29,14 @@ Standarddateien sind nicht in Klonen, Paketen oder Downloads von einzelnen Repos
 
 You can create defaults in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} for the following community health files:
 
-| Community-Unterstützungsdatei                                                                                                                                                                           | Beschreibung                                                                                                                                                                                                                                                                                                                                                                            |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| Community-Unterstützungsdatei                                                                                                                                                                           | Beschreibung                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
 | *CODE_OF_CONDUCT.md*                                                                                                                                                                                  | Eine CODE_OF_CONDUCT-Datei legt die Standards für die Interaktion in einer Community fest. Weitere Informationen findest Du unter „[Deinem Projekt einen Verhaltenskodex hinzufügen](/articles/adding-a-code-of-conduct-to-your-project/)“.{% endif %}
 | *CONTRIBUTING.md*                                                                                                                                                                                       | Eine CONTRIBUTING-Datei erläutert, wie zu Deinem Projekt beigetragen werden soll. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% if currentVersion == "free-pro-team@latest" %}
 | *FUNDING.yml*                                                                                                                                                                                           | Eine FUNDING-Datei zeigt eine Sponsorenschaltfläche in Deinem Repository an, um die Sichtbarkeit von Finanzierungsoptionen für Dein Open-Source-Projekt zu erhöhen. Weitere Informationen findest Du unter „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“{% endif %}
-| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Mit den Vorlagen für Issues und Pull Requests kannst Du die Informationen anpassen und standardisieren, die Mitarbeiter beim Öffnen von Issues und Pull Requests in Deinem Repository berücksichtigen sollen. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" %}
-| *SECURITY.md*                                                                                                                                                                                           | Eine SECURITY-Datei enthält Anweisungen zum verantwortungsvollen Melden einer Sicherheitslücke in Ihrem Projekt. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zum Repository hinzufügen](/articles/adding-a-security-policy-to-your-repository)“.{% endif %}
-| *SUPPORT.md*                                                                                                                                                                                            | Mit einer SUPPORT-Datei kannst Du anderen mitteilen, wie sie Unterstützung bei Deinem Projekt erhalten können. Weitere Informationen findest Du unter „[Support-Ressourcen zu Deinem Projekt hinzufügen](/articles/adding-support-resources-to-your-project/).“                                                                                                                         |
+| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Mit den Vorlagen für Issues und Pull Requests kannst Du die Informationen anpassen und standardisieren, die Mitarbeiter beim Öffnen von Issues und Pull Requests in Deinem Repository berücksichtigen sollen. Weitere Informationen findest Du unter „[Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates/)“.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| *SECURITY.md*                                                                                                                                                                                           | A SECURITY file gives instructions for how to report a security vulnerability in your project. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zum Repository hinzufügen](/code-security/getting-started/adding-a-security-policy-to-your-repository)“.{% endif %}
+| *SUPPORT.md*                                                                                                                                                                                            | Mit einer SUPPORT-Datei kannst Du anderen mitteilen, wie sie Unterstützung bei Deinem Projekt erhalten können. Weitere Informationen findest Du unter „[Support-Ressourcen zu Deinem Projekt hinzufügen](/articles/adding-support-resources-to-your-project/).“                                                                                                                                                                                                       |
 
 Du kannst keine Standard-Lizenzdatei erstellen. Lizenzdateien müssen zu individuellen Repositorys hinzugefügt werden, damit die Datei bei Klonen, Paketieren und Herunterladen des Projekts enthalten ist.
 
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index b3f2940e1b..4f200a85e7 100644
--- a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-Um die Beiträge Deiner Projektmitarbeiter zu optimieren, kannst Du ein Dokument mit Beitragsrichtlinien in das Stammverzeichnis, in das Verzeichnis `docs` oder in das Verzeichnis `.github` Deines Projekt-Repositorys hinzufügen. Bei der Eröffnung eines Pull-Requests oder der Erstellung eines Issues wird dem betreffenden Mitarbeiter dann ein Link zu dieser Datei angezeigt.
+### About contributing guidelines
+Um die Beiträge Deiner Projektmitarbeiter zu optimieren, kannst Du ein Dokument mit Beitragsrichtlinien in das Stammverzeichnis, in das Verzeichnis `docs` oder in das Verzeichnis `.github` Deines Projekt-Repositorys hinzufügen. Bei der Eröffnung eines Pull-Requests oder der Erstellung eines Issues wird dem betreffenden Mitarbeiter dann ein Link zu dieser Datei angezeigt. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![Beitragsrichtlinien](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ You can create default contribution guidelines for your organization{% if curren
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. Entscheide, ob die Beitragsrichtlinien im Stammverzeichnis, im Verzeichnis `docs` oder im Verzeichnis `.github` Deines Repositorys gespeichert werden sollen. Gib danach im Feld „Filename“ (Dateiname) den Namen und die Erweiterung der Datei ein. In Dateinamen von Beitragsrichtlinien wird die Groß-/Kleinschreibung ignoriert, und die Dateien können die Erweiterung *.md* oder *.txt* haben. ![Neuer Dateiname](/assets/images/help/repository/new-file-name.png)
+3. Entscheide, ob die Beitragsrichtlinien im Stammverzeichnis, im Verzeichnis `docs` oder im Verzeichnis `.github` Deines Repositorys gespeichert werden sollen. Gib danach im Feld „Filename“ (Dateiname) den Namen und die Erweiterung der Datei ein. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![Neuer Dateiname](/assets/images/help/repository/new-file-name.png)
     - Wenn Deine Beitragsrichtlinien im Stammverzeichnis Deines Repositorys erscheinen sollen, gib *CONTRIBUTING* ein.
     - Wenn Deine Beitragsrichtlinien im Verzeichnis `docs` Deines Repositorys erscheinen sollen, gib zur Erstellung des neuen Verzeichnisses *docs/* ein und anschließend *CONTRIBUTING*.
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. Füge der neuen Datei Beitragsrichtlinien hinzu. Diese könnten beinhalten:
     - Schritte zur Erstellung korrekt formulierter Issues oder Pull Requests.
     - Links zu externer Dokumentation, zu Verteilerlisten oder zu einem Verhaltenskodex.
diff --git a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md
index bd2bd2d3dd..b7d472573d 100644
--- a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -179,7 +179,7 @@ You must complete this step of the GitHub App Manifest flow within one hour.
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest).
 
diff --git a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index e87b560b13..319a595b7b 100644
--- a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method.
+This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
 
 To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run.
 
@@ -240,31 +235,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -276,40 +262,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created.
+The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created.
 
-Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
+Here's what this code is doing. First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
 
 You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`.
 
@@ -613,29 +589,23 @@ Now you've got all the information you need to update your check run. In the [fi
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -645,51 +615,45 @@ You'll need to update that code to use the `conclusion` variable you set based o
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/de-DE/content/developers/apps/making-a-github-app-public-or-private.md b/translations/de-DE/content/developers/apps/making-a-github-app-public-or-private.md
index a3938ed702..86e6d04355 100644
--- a/translations/de-DE/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/de-DE/content/developers/apps/making-a-github-app-public-or-private.md
@@ -23,7 +23,7 @@ Public installation flows have a landing page to enable other people besides the
 
 ### Private installation flow
 
-Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private, or internal, GitHub Apps can only be installed on the user or organization account of the owner.
+Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### Changing who can install your GitHub App
 
@@ -34,5 +34,5 @@ To change who can install the GitHub App:
 {% data reusables.user-settings.github_apps %}
 3. Select the GitHub App whose installation option you want to change. ![App selection](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. Depending on the installation option of your GitHub App, click either **Make public** or **Make internal**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
-6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App internal**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md
index 5f2b43413e..46ab744178 100644
--- a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md
+++ b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md
@@ -30,7 +30,7 @@ Check headers to see what OAuth scopes you have, and what the API action accepts
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
-HTTP/1.1 200 OK
+HTTP/2 200
 X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
diff --git a/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 71143d19b1..305f67758c 100644
--- a/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -370,10 +370,10 @@ After you click **Install**, look at the output in your Terminal. You should see
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 This is good news! It means your app received a notification that it was installed on your GitHub account. If you see something like this, your app is running on the server as expected. 🙌
diff --git a/translations/de-DE/content/developers/apps/using-content-attachments.md b/translations/de-DE/content/developers/apps/using-content-attachments.md
index ee41878eb5..6f4ced0aee 100644
--- a/translations/de-DE/content/developers/apps/using-content-attachments.md
+++ b/translations/de-DE/content/developers/apps/using-content-attachments.md
@@ -130,9 +130,8 @@ To create a Probot App, follow these steps:
 2. Open the project you created, and customize the settings in the `app.yml` file. Subscribe to the `content_reference` event and enable `content_references` write permissions:
 
    ``` yml
-
     default_events:
-    - content_reference
+      - content_reference
     # The set of permissions needed by the GitHub App. The format of the object uses
     # the permission name for the key (for example, issues) and the access type for
     # the value (for example, write).
@@ -141,10 +140,10 @@ To create a Probot App, follow these steps:
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
diff --git a/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index e08acf79dd..169d665871 100644
--- a/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ To offer paid plans for your app, the app must be owned by an organization and y
 
 ### Requesting publisher verification
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Klicke auf der linken Seitenleiste auf **Developer settings** (Entwicklereinstellungen). ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. Under "Publisher Verification", complete the information in the checklist:
    - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
    - Ensure that Two-factor authentication is enabled for your organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)“.
-   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/de-DE/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/de-DE/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index 198473681f..e5450f2b79 100644
--- a/translations/de-DE/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/de-DE/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ Here are guidelines about the fields you'll need to fill out in the **Listing de
 
 #### Listing name
 
-Your app's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters.
+Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing {% data variables.product.product_name %} user, unless the name is your own user or organization name.
 
 #### Very short description
 
diff --git a/translations/de-DE/content/developers/overview/secret-scanning.md b/translations/de-DE/content/developers/overview/secret-scanning.md
index f839299f39..1ba8e85435 100644
--- a/translations/de-DE/content/developers/overview/secret-scanning.md
+++ b/translations/de-DE/content/developers/overview/secret-scanning.md
@@ -15,9 +15,9 @@ topics:
 
 When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice.
 
-When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
+When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
 
-This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program.
+This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program.
 
 ### The {% data variables.product.prodname_secret_scanning %} process
 
@@ -54,26 +54,20 @@ Send this information to <a href="mailto:secret-scanning@github.com">secret-scan
 
 #### Create a secret alert service
 
-Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send a HTTP `POST` message to your endpoint.
+Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint.
 
 ##### Example POST sent to your endpoint
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %}  may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out.
@@ -88,19 +82,31 @@ We strongly recommend you implement signature validation in your secret alert se
 
 You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm.
 
-Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set.
+{% note %}
+
+**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
+
+{% endnote %}
+
+Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code snippets assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens) to avoid hitting rate limits. The PAT does not need any scopes/permissions.
+
+{% note %}
+
+**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
+
+{% endnote %}
 
 **Sample message sent to verify endpoint**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Validation sample in Go**
@@ -123,14 +129,14 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
   // Fetch the list of GitHub Public Keys
-  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
     fmt.Printf("Error preparing request: %s\n", err)
     os.Exit(1)
@@ -226,43 +232,6 @@ type GitHubSigningKeys struct {
   } `json:"public_keys"`
 }
 
-// asn1Signature is a struct for ASN.1 serializing/parsing signatures.
-    os.Exit(7)
-  }
-
-  // Parse the Webhook Signature
-  parsedSig := asn1Signature{}
-  asnSig, err := base64.StdEncoding.DecodeString(kSig)
-  if err != nil {
-    fmt.Printf("unable to base64 decode signature: %s\n", err)
-    os.Exit(8)
-  }
-  rest, err := asn1.Unmarshal(asnSig, &parsedSig)
-  if err != nil || len(rest) != 0 {
-    fmt.Printf("Error unmarshalling asn.1 signature: %s\n", err)
-    os.Exit(9)
-  }
-
-  // Verify the SHA256 encoded payload against the signature with GitHub's Key
-  digest := sha256.Sum256([]byte(payload))
-  keyOk := ecdsa.Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S)
-
-  if keyOk {
-    fmt.Println("THE PAYLOAD IS GOOD!!")
-  } else {
-    fmt.Println("the payload is invalid :(")
-    os.Exit(10)
-  }
-}
-
-type GitHubSigningKeys struct {
-  PublicKeys []struct {
-    KeyIdentifier string `json:"key_identifier"`
-    Key           string `json:"key"`
-    IsCurrent     bool   `json:"is_current"`
-  } `json:"public_keys"`
-}
-
 // asn1Signature is a struct for ASN.1 serializing/parsing signatures.
 type asn1Signature struct {
   R *big.Int
@@ -279,16 +248,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -394,4 +363,3 @@ A few important points:
 **Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
 {% endnote %}
-
diff --git a/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md b/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md
index 030b2a7855..45574b6bcc 100644
--- a/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-On Mac OS X, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
+On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md b/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md
index 2f91f1596c..445af20c10 100644
--- a/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ The event objects returned from the Events API endpoints have the same structure
 This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events).
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index 8dbbbbeeb7..2a777c8e8a 100644
--- a/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -61,7 +61,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 #### Example delivery
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -200,7 +200,9 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment.
 
-Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event.
+#### Availability
+
+- {% data variables.product.prodname_github_app %}s with the `content_references:write` permission
 
 #### Webhook payload example
 
@@ -509,7 +511,7 @@ When someone revokes their authorization of a {% data variables.product.prodname
 
 {% note %}
 
-`repository` property when the event occurs from activity in a repository.
+**Note:** This event replaces the deprecated `integration_installation_repositories` event.
 
 {% endnote %}
 
@@ -1010,12 +1012,6 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% endnote %}
 
-{% tip %}
-
-**Note**: The webhook payload example following the table differs significantly from the Events API payload described in the table. Among other differences, the webhook payload includes both `sender` and `pusher` objects. Sender and pusher are the same user who initiated the `push` event, but the `sender` object contains more detail.
-
-{% endtip %}
-
 #### Availability
 
 - Repository webhooks
@@ -1206,7 +1202,7 @@ Activity related to a security advisory. A security advisory provides informatio
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
+You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
 
 #### Availability
 
diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index c911b46ded..0fdca43801 100644
--- a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
 
-In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)."
+In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji.
 
 You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."
 
diff --git a/translations/de-DE/content/discussions/index.md b/translations/de-DE/content/discussions/index.md
index 8e9b868165..3c52fee2cf 100644
--- a/translations/de-DE/content/discussions/index.md
+++ b/translations/de-DE/content/discussions/index.md
@@ -23,8 +23,8 @@ featuredLinks:
     - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions
     - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
 changelog:
-  label: discussions
-product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk'
+  label: 'discussions'
+product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk
 layout: product-landing
 versions:
   free-pro-team: '*'
@@ -34,24 +34,3 @@ versions:
 <!-- {% link_with_intro /discussions-guides %} -->
 <!-- {% link_with_intro /collaborating-with-your-community-using-discussions %} -->
 <!-- {% link_with_intro /managing-discussions-for-your-community %} -->
-
-<!-- Community examples -->
-{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %}
-{% if discussionsCommunityExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Communities using discussions</h2>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render discussions-community-card for discussionsCommunityExamples as example %}
-  </div>
-  {% if discussionsCommunityExamples.length > 6 %}
-    <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Show more {% octicon "arrow-right" %}</button>
-  {% endif %}
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Sorry, there is no result for <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/discussions_community_examples.yml">Add your community {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md
index c997919604..05a04a605f 100644
--- a/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md
@@ -27,7 +27,7 @@ In jeder E-Mail-Benachrichtigung für einen Push an ein Repository werden die ne
 - Die Dateien, die im Rahmen des Commits geändert wurden
 - Die Commit-Mitteilung
 
-Du kannst E-Mail-Benachrichtigungen filtern, die Du für Pushes an ein Repository erhältst. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About notification emails](/github/receiving-notifications-about-activity-on-github/about-email-notifications)." Du kannst auch E-Mail-Benachrichtigungen für Pushes ausschalten. Weitere Informationen findest Du unter „[Auslieferungsmethode für Deine Benachrichtigungen wählen](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}.“
+Du kannst E-Mail-Benachrichtigungen filtern, die Du für Pushes an ein Repository erhältst. Weitere Informationen findest Du unter {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}„[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}„[Über E-Mail-Benachrichtigungen](/github/receiving-notifications-about-activity-on-github/about-email-notifications)." Du kannst auch E-Mail-Benachrichtigungen für Pushes ausschalten. Weitere Informationen findest Du unter „[Auslieferungsmethode für Deine Benachrichtigungen wählen](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}.“
 
 ### E-Mail-Benachrichtigungen für Pushes in Dein Repository aktivieren
 
diff --git a/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md b/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md
index 79c1a5f075..8d23d25414 100644
--- a/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md
@@ -47,6 +47,8 @@ For each branch protection rule, you can choose to enable or disable the followi
 - [Allow force pushes](#allow-force-pushes)
 - [Allow deletions](#allow-deletions)
 
+For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+
 #### Require pull request reviews before merging
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
@@ -100,7 +102,15 @@ When you enable required commit signing on a branch, contributors {% if currentV
 
 {% note %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+**Hinweise:**
+
+* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+
+{% else %}
 **Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+{% endif %}
 
 {% endnote %}
 
diff --git a/translations/de-DE/content/github/administering-a-repository/about-releases.md b/translations/de-DE/content/github/administering-a-repository/about-releases.md
index 28d82866c1..cc11ad87f6 100644
--- a/translations/de-DE/content/github/administering-a-repository/about-releases.md
+++ b/translations/de-DE/content/github/administering-a-repository/about-releases.md
@@ -23,7 +23,7 @@ Releases sind einsetzbare Software-Iterationen, die Du paketieren und für ein b
 
 Releases basieren auf [Git-Tags](https://git-scm.com/book/en/Git-Basics-Tagging), die einen bestimmten Punkt im Verlauf Deines Repositorys kennzeichnen. Ein Tag kann ein anderes Datum haben als ein Release, da sie zu unterschiedlichen Zeiten erstellt wurden. Weitere Informationen zum Anzeigen Deiner vorhandenen Tags findest Du unter „[Anzeigen der Releases und Tags Deines Repositorys](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)."
 
-Du kannst Benachrichtigungen erhalten, wenn neue Releases in einem Repository verfügbar sind, ohne Benachrichtigungen über andere Updates des gleichen Repositorys zu erhalten. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching releases for a repository](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}."
+Du kannst Benachrichtigungen erhalten, wenn neue Releases in einem Repository verfügbar sind, ohne Benachrichtigungen über andere Updates des gleichen Repositorys zu erhalten. Weitere Informationen findest Du unter {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}„[Anzeigen Deiner Abonnements](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}„[Anzeige von Releases für ein Repository aktivieren oder deaktivieren](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}."
 
 Alle Personen mit Lesezugriff auf ein Repository können Releases anzeigen und vergleichen, aber nur Personen mit Schreibberechtigungen für ein Repository können Releases verwalten. Weitere Informationen findest Du unter „[Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository)."
 
diff --git a/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md b/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md
index 849a5d19ec..1528f3e499 100644
--- a/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/de-DE/content/github/administering-a-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ You can choose the default branch for a repository. The default branch is the ba
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
 You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
 
diff --git a/translations/de-DE/content/github/administering-a-repository/classifying-your-repository-with-topics.md b/translations/de-DE/content/github/administering-a-repository/classifying-your-repository-with-topics.md
index ed3806920e..6ac61e7a5b 100644
--- a/translations/de-DE/content/github/administering-a-repository/classifying-your-repository-with-topics.md
+++ b/translations/de-DE/content/github/administering-a-repository/classifying-your-repository-with-topics.md
@@ -14,15 +14,15 @@ topics:
 
 ### Informationen zu Themen
 
-Mithilfe von Themen kannst Du Repositorys zu einem bestimmten Themenbereich erkunden, Projekte finden, zu denen Du einen Beitrag leisten kannst, und neue Lösungen für ein bestimmtes Problem entdecken. Themen werden auf der Hauptseite eines Repositorys angezeigt. You can click a topic name to {% if currentVersion == "free-pro-team@latest" %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+Mithilfe von Themen kannst Du Repositorys zu einem bestimmten Themenbereich erkunden, Projekte finden, zu denen Du einen Beitrag leisten kannst, und neue Lösungen für ein bestimmtes Problem entdecken. Themen werden auf der Hauptseite eines Repositorys angezeigt. Du kannst auf den Namen eines Themas klicken, um {% if currentVersion == "free-pro-team@latest" %}ähnliche Themen und eine Liste anderer Repositorys mit demselben Thema anzuzeigen{% else %}nach anderen Repositorys mit demselben Thema zu suchen{% endif %}.
 
 ![Hauptseite des Test-Repositorys, auf der Themen angezeigt werden](/assets/images/help/repository/os-repo-with-topics.png)
 
 Rufe https://github.com/topics/ auf, um die am häufigsten verwendeten Themen zu durchsuchen.
 
-{% if currentVersion == "free-pro-team@latest" %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Sie können Beiträge zum Satz an den enthaltenen Themen von {% data variables.product.product_name %} im Repository [github/explore](https://github.com/github/explore) leisten. {% endif %}
 
-Repository-Administratoren können beliebige Themen zu einem Repository hinzufügen. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% if currentVersion == "free-pro-team@latest" %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Die Inhalte privater Repositorys werden nicht analysiert, und es gibt keine Themenvorschläge für private Repositorys.{% endif %}
+Repository-Administratoren können beliebige Themen zu einem Repository hinzufügen. Hilfreiche Themen, mit denen Sie ein Repository klassifizieren können, sind beispielsweise der beabsichtigte Zweck, der Themenbereich, die Community oder die Sprache des Repositorys.{% if currentVersion == "free-pro-team@latest" %} Zusätzlich analysiert {% data variables.product.product_name %} Inhalte öffentlicher Repositorys und erzeugt Themenvorschläge, die Repository-Administratoren annehmen oder ablehnen können. Die Inhalte privater Repositorys werden nicht analysiert, und es gibt keine Themenvorschläge für private Repositorys.{% endif %}
 
 {% if currentVersion == "github-ae@latest" %}Internal {% else %}Public, internal, {% endif %}and private repositories can have topics, although you will only see private repositories that you have access to in topic search results.
 
diff --git a/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index d72a42e601..f0ac5517a8 100644
--- a/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -82,3 +82,21 @@ You can disable all workflows for a repository or set a policy that configures w
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your repository
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. Click **Save** to apply the settings.
+{% endif %}
diff --git a/translations/de-DE/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/de-DE/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index fbee4aec9f..aa38453cd4 100644
--- a/translations/de-DE/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### Informationen zu FUNDING-Dateien
 
-Du kannst Deine Sponsorenschaltfläche konfigurieren, indem Du die Datei _FUNDING.yml_ im `.github`-Ordner auf dem Standardbranch Deines Repositorys bearbeitest. Die Schaltfläche kann so konfiguriert werden, dass sie unterstützte Entwickler in {% data variables.product.prodname_sponsors %}, externen Finanzierungsplattformen oder einer benutzerdefinierten Sponsoring-URL enthält. Weitere Informationen zu {% data variables.product.prodname_sponsors %} findest Du unter „[Informationen zu GitHub-Sponsoren](/articles/about-github-sponsors).“
+Du kannst Deine Sponsorenschaltfläche konfigurieren, indem Du die Datei _FUNDING.yml_ im `.github`-Ordner auf dem Standardbranch Deines Repositorys bearbeitest. Die Schaltfläche kann so konfiguriert werden, dass sie unterstützte Entwickler in {% data variables.product.prodname_sponsors %}, externen Finanzierungsplattformen oder einer benutzerdefinierten Sponsoring-URL enthält. Weitere Informationen zu {% data variables.product.prodname_sponsors %} findest Du unter „[Informationen zu GitHub-Sponsoren](/sponsors/getting-started-with-github-sponsors/about-github-sponsors).“
 
 Du kannst einen Benutzernamen, Paketnamen oder Projektnamen pro externer Finanzierungsplattform und bis zu vier benutzerdefinierte URLs hinzufügen. Du kannst bis zu vier unterstützten Entwickler oder Organisationen in {% data variables.product.prodname_sponsors %} hinzufügen. Füge jede Plattform auf einer neuen Zeile hinzu, und verwende dabei die folgende Syntax:
 
@@ -76,5 +76,5 @@ Jeder, der über Administratorberechtigungen verfügt, kann eine Sponsorenschalt
 {% data reusables.files.propose_new_file %}
 
 ### Weiterführende Informationen
-- „[Über {% data variables.product.prodname_sponsors %} für Open-Source-Mitarbeiter](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- „[Über {% data variables.product.prodname_sponsors %} für Open-Source-Mitarbeiter](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
 - „[Häufig gestellte Fragen mit dem {% data variables.product.prodname_sponsors %}-Team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)“ auf {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index f61fcb2853..5d42cc4e48 100644
--- a/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -35,10 +35,11 @@ You can manage the security and analysis features for your {% if currentVersion
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. The control for "
+{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% if currentVersion == "free-pro-team@latest" %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
 **Note:** If you disable
 
@@ -46,11 +47,11 @@ You can manage the security and analysis features for your {% if currentVersion
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
 4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. Before you can enable "
-{% data variables.product.prodname_secret_scanning %}" for your repository, you need to enable {% data variables.product.prodname_GH_advanced_security %}.
+{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.
    ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
diff --git a/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index c63498fa94..c9398aa6e8 100644
--- a/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ Weitere Informationen zu Repository-Berechtigungsstufen findest Du unter „[Ber
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. Finde unter „Manage access" (Zugriffe verwalten) das Team oder die Person, deren Zugriff Du entfernen willst, dann klicke auf {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Trashcan-Symbol zum Entfernen des Zugriffs](/assets/images/help/repository/manage-access-remove.png)
+4. Finde unter „Manage access" (Zugriffe verwalten) das Team oder die Person, deren Zugriff Du entfernen willst, dann klicke auf {% octicon "trash" aria-label="The trash icon" %}. ![trash icon for removing access](/assets/images/help/repository/manage-access-remove.png)
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
index d6bb7f5e94..c98b099e05 100644
--- a/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Verwalten der Forking-Richtlinie für Dein Repository
-intro: 'You can allow or prevent the forking of a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or internal{% endif %} repository owned by an organization.'
+intro: 'Du kannst das Forken eines bestimmten privaten{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} oder internen{% endif %} Repositorys einer Organisation erlauben oder verhindern.'
 redirect_from:
   - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization
   - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization
@@ -13,7 +13,7 @@ topics:
   - Repositories
 ---
 
-An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. Weitere Informationen findest Du unter „[Die Forking-Richtlinie für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
+Ein Organisationsinhaber muss Forks von privaten{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} und internen{% endif %} Repositorys auf der Organisationsebene erlauben, bevor Du Forks für ein bestimmtes Repository erlauben oder verbieten kannst. Weitere Informationen findest Du unter „[Die Forking-Richtlinie für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
diff --git a/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md b/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md
index 4b22add6cd..9f56a37283 100644
--- a/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/de-DE/content/github/administering-a-repository/renaming-a-branch.md
@@ -17,6 +17,8 @@ When you rename a branch on {% data variables.product.product_location %}, any U
 
 Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
 
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+
 ### Renaming a branch
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -35,4 +37,10 @@ From the local clone of the repository on a computer, run the following commands
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+Optionally, run the following command to remove tracking references to the old branch name.
+```
+$ git remote prune origin
 ```
diff --git a/translations/de-DE/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/de-DE/content/github/administering-a-repository/restoring-a-deleted-repository.md
index 8bf6f99acd..a367540518 100644
--- a/translations/de-DE/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -31,9 +31,9 @@ Beim Wiederherstellen eines Repositorys werden etwaige Releaseanhänge oder Team
 
 ### Gelöschtes Repository einer Organisation wiederherstellen
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/de-DE/content/github/administering-a-repository/transferring-a-repository.md b/translations/de-DE/content/github/administering-a-repository/transferring-a-repository.md
index d79851e240..8a4b71fdff 100644
--- a/translations/de-DE/content/github/administering-a-repository/transferring-a-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/transferring-a-repository.md
@@ -31,7 +31,7 @@ Prerequisites for repository transfers: {% if currentVersion == "free-pro-team@l
 - Der ursprüngliche Inhaber des Repositorys wird dem übertragenen Repository als Mitarbeiter hinzugefügt. Andere Mitarbeiter des übertragenen Repositorys bleiben unverändert.
 - Private Forks können nicht übertragen werden.
 
-{% if currentVersion == "free-pro-team@latest" %}If you transfer a private repository to a {% data variables.product.prodname_free_user %} user or organization account, the repository will lose access to features like protected branches and {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Wenn Du ein privates Repository auf ein {% data variables.product.prodname_free_user %}-Benutzer- oder -Organisationskonto überträgst, verliert das Repository den Zugriff auf Funktionen wie beispielsweise geschützte Branches und {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %}
 
 #### Was wird mit einem Repository übertragen?
 
diff --git a/translations/de-DE/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/de-DE/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index 8ffb969559..c5af836eb1 100644
--- a/translations/de-DE/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/de-DE/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ Darüber hinaus können Bereitstellungsinformationen auf der Registerkarte „Co
 ### Dashboard für Bereitstellungen anzeigen
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Klicke oberhalb der Liste der Dateien auf **Environments** (Umgebungen). ![Umgebungen auf der Repository-Seite](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### Weiterführende Informationen
  - „[Informationen zu Pull Requests](/articles/about-pull-requests)“
diff --git a/translations/de-DE/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/de-DE/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..22edcdc82e
--- /dev/null
+++ b/translations/de-DE/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+Zum Hosten Ihrer Bilder verwendet {% data variables.product.product_name %} den [Open-Source-Projekt-Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Probleme mit Camo beheben
+
+In seltenen Fällen erscheinen Bilder, die mit Camo verarbeitet werden, möglicherweise nicht auf {% data variables.product.prodname_dotcom %}. Nachfolgend findest Du einige Schritte, mit denen Du feststellen kannst, wo das Problem liegt.
+
+{% windows %}
+
+{% tip %}
+
+Windows-Benutzer müssen entweder Git Powershell verwenden (neben [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) installiert) oder [curl für Windows](http://curl.haxx.se/download.html) herunterladen.
+
+{% endtip %}
+
+{% endwindows %}
+
+#### Ein Bild wird nicht angezeigt
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Fordern Sie die Bildheader mit `curl` an.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. Überprüfe den Wert von `Content-Type`. In diesem Fall ist er `image/x-png`.
+4. Überprüfe diesen Inhaltstyp gegen die [Liste der von Camo unterstützten Typen](https://github.com/atmos/camo/blob/master/mime-types.json).
+
+Wenn Dein Inhaltstyp von Camo nicht unterstützt wird, kannst Du mehrere Aktionen versuchen:
+  * Wenn Du der Besitzer des Servers bist, der das Bild verwaltet, ändere die Einstellungen so, dass er einen korrekten Inhaltstyp für Bilder zurückgibt.
+  * Wenn Du einen externen Dienst zum Verwalten von Bildern verwendest, wende Dich an den Support für diesen Dienst.
+  * Stelle einen Pull Request an Camo, um Deinen Inhaltstyp zur Liste hinzuzufügen.
+
+#### Ein kürzlich geändertes Bild wird nicht aktualisiert
+
+Wenn Du ein Bild kürzlich geändert hast und die Änderung in Deinem Browser angezeigt wird, aber nicht auf {% data variables.product.prodname_dotcom %}, kannst Du versuchen, den Zwischenspeicher des Bildes zurückzusetzen.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Fordern Sie die Bildheader mit `curl` an.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+Überprüfe den Wert von `Cache-Control`. In diesem Beispiel gibt es kein `Cache-Control`. Gehe in diesem Fall folgendermaßen vor:
+  * Wenn Du Besitzer des Servers bist, der das Bild verwaltet, ändere die Einstellungen so, dass er für Bilder einen `Cache-Control` von `no-cache` zurückgibt.
+  * Wenn Du einen externen Dienst zum Verwalten von Bildern verwendest, wende Dich an den Support für diesen Dienst.
+
+ Wenn `Cache-Control` auf `no-cache` gesetzt *ist*, kontaktiere {% data variables.contact.contact_support %} oder durchsuche das {% data variables.contact.community_support_forum %}.
+
+#### Ein Bild aus dem Zwischenspeicher von Camo entfernen
+
+Durch das Bereinigen des Zwischenspeichers wird jeder {% data variables.product.prodname_dotcom %}-Benutzer dazu gezwungen, das Bild erneut anzufordern. Daher solltest Du diesen Vorgang selten und nur dann durchführen, wenn die oben genannten Schritte nicht funktioniert haben.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Bereinige das Bild, indem Du `curl -X PURGE` auf die Camo-URL anwendest.
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### Bilder in privaten Netzwerken anzeigen
+
+Wenn ein Bild von einem privaten Netzwerk oder von einem Server bereitgestellt wird, der eine Authentifizierung erfordert, kann es nicht von {% data variables.product.prodname_dotcom %} angezeigt werden. Tatsächlich kann es von keinem Benutzer eingesehen werden, ohne dass er dazu aufgefordert wird, sich am Server anzumelden.
+
+Um dieses Problem zu beheben, verschiebe das Bild bitte auf einen öffentlich zugänglichen Dienst.
+
+### Weiterführende Informationen
+
+- „[Proxying user images](https://github.com/blog/1766-proxying-user-images)“ (Proxyvorgang von Benutzerbildern) auf {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md
index 221c4b36b5..c949635b34 100644
--- a/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/de-DE/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: Informationen zur Verifizierung einer Commit-Signatur
-intro: 'Using GPG or S/MIME, you can sign tags and commits locally. Diese Tags oder Commits werden auf {% data variables.product.product_name %} als verifiziert gekennzeichnet, sodass andere Personen darauf vertrauen können, dass die Änderungen aus einer vertrauenswürdigen Quelle stammen.'
+intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures/
   - /articles/about-gpg/
@@ -16,15 +16,35 @@ topics:
 
 ### Informationen zur Verifizierung einer Commit-Signatur
 
-Du kannst Commits und Tags lokal signieren, sodass andere Personen überprüfen können, dass Deine Arbeit von einer vertrauenswürdigen Quelle stammt. Wenn ein Commit oder Tag eine GPG- oder S/MIME-Signatur hat, die kryptografisch verifiziert werden kann, wird der Commit oder das Tag von {% data variables.product.product_name %} als verifiziert gekennzeichnet.
+You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% if currentVersion == "free-pro-team@latest" %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
 
 ![Verifizierter Commit](/assets/images/help/commits/verified-commit.png)
 
-Wenn ein Commit oder Tag eine Signatur hat, die nicht verifiziert werden kann, wird der Commit oder das Tag von {% data variables.product.product_name %} als nicht verifiziert gekennzeichnet.
+{% if currentVersion == "free-pro-team@latest" %}
+Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+#### Default statuses
+
+| Status                 | Beschreibung                                                      |
+| ---------------------- | ----------------------------------------------------------------- |
+| **Verified**           | The commit is signed and the signature was successfully verified. |
+| **Unverified**         | The commit is signed but the signature could not be verified.     |
+| No verification status | The commit is not signed.                                         |
+
+#### Statuses with vigilant mode enabled
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+If a commit or tag has a signature that can't be verified,
+{% data variables.product.product_name %} marks the commit or tag "Unverified."
+{% endif %}
 
 Repository-Administratoren können die obligatorische Commit-Signatur auf einem Branch erzwingen, um alle Commits zu blockieren, die nicht signiert und verifiziert sind. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-signed-commits).“
 
-Du kannst den Verifizierungsstatus Deines signierten Commits oder Tags auf {% data variables.product.product_name %} überprüfen und sehen, warum Deine Commit-Signaturen möglicherweise nicht verifiziert sind. Weitere Informationen findest Du unter „[Verifizierungsstatus Deiner Commit- und Tag-Signaturen überprüfen](/articles/checking-your-commit-and-tag-signature-verification-status).“
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits, die von {% data variables.product.product_name %} signiert sind, werden auf {% data variables.product.product_name %} einen verifizierten Status haben. Sie können die Signatur lokal mit dem unter https://github.com/web-flow.gpg verfügbaren öffentlichen Schlüssel verifizieren. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."
@@ -49,17 +69,17 @@ Um Commits mit GPG zu signieren und diese Commits auf {% data variables.product.
 
 Sie können S/MIME verwenden, um Commits mit einem von Ihrer Organisation ausgegebenen X.509-Schlüssel zu signieren.
 
-{% data variables.product.product_name %} verwendet [das Debian-CA-Zertifikatpaket](https://packages.debian.org/hu/jessie/ca-certificates), den gleichen Trust Store, der auch von Mozilla-Browsern verwendet wird, um zu bestätigen, dass Ihre lokal signierten Commits und Tags kryptographisch mit einem öffentlichen Schlüssel in einem vertrauenswürdigen Stammzertifikat verifizierbar sind.
+{% data variables.product.product_name %} verwendet [das Debian-CA-Zertifikatspaket](https://packages.debian.org/hu/jessie/ca-certificates), den gleichen Trust Store, der auch von Mozilla-Browsern verwendet wird, um zu bestätigen, dass Deine lokal signierten Commits und Tags kryptographisch mit einem öffentlichen Schlüssel in einem vertrauenswürdigen Stammzertifikat verifizierbar sind.
 
 {% data reusables.gpg.smime-git-version %}
 
-Um Commits mit S/MIME zu signieren und diese Commits auf {% data variables.product.product_name %} verifizieren zu lassen, führen Sie die folgenden Schritte aus:
+Um Commits mit S/MIME zu signieren und diese Commits auf {% data variables.product.product_name %} verifizieren zu lassen, führe die folgenden Schritte aus:
 
 1. [Informiere Git über Deinen Signaturschlüssel](/articles/telling-git-about-your-signing-key)
 2. [Signiere Commits](/articles/signing-commits)
 3. [Signiere Tags](/articles/signing-tags)
 
-Sie müssen Ihren öffentlichen Schlüssel nicht auf {% data variables.product.product_name %} hochladen.
+Du musst Deinen öffentlichen Schlüssel nicht auf {% data variables.product.product_name %} hochladen.
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Signaturverifizierung für Bots
diff --git a/translations/de-DE/content/github/authenticating-to-github/about-ssh.md b/translations/de-DE/content/github/authenticating-to-github/about-ssh.md
index 2db98d7a3d..ac4e172f03 100644
--- a/translations/de-DE/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/de-DE/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-Wenn Sie die SSH einrichten, [generieren Sie einen SSH-Schlüssel und fügen ihn zu ssh-agent hinzu](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). Dann [fügen Sie den Schlüssel zu Ihrem {% data variables.product.product_name %}-Konto hinzu](/articles/adding-a-new-ssh-key-to-your-github-account). Durch das Hinzufügen des SSH-Schlüssels zum SSH-Agenten wird sichergestellt, dass Dein SSH-Schlüssel durch die Verwendung einer Passphrase eine zusätzliche Sicherheitsebene hat. Weitere Informationen findest Du unter „[SSH-Schlüssel-Passphrasen verwenden](/articles/working-with-ssh-key-passphrases).“
+When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
-{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you'll need to authorize it first. Weitere Informationen findest Du unter „[Einen SSH-Schlüssel für die Verwendung in einer Organisation mit SAML Single Sign-On autorisieren](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)“.{% endif %}
+You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. Weitere Informationen findest Du unter „[SSH-Schlüssel-Passphrasen verwenden](/github/authenticating-to-github/working-with-ssh-key-passphrases).“
 
-Du solltest regelmäßig [Deine Liste mit SSH-Schlüsseln überprüfen](/articles/reviewing-your-ssh-keys) und ungültige oder kompromittierte Schlüssel widerrufen.
+{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. Weitere Informationen findest Du unter „[Einen SSH-Schlüssel für die Verwendung in einer Organisation mit SAML Single Sign-On autorisieren](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)“.{% endif %}
+
+To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. Weitere Informationen findest Du unter „[SSH-Schlüssel überprüfen](/github/authenticating-to-github/reviewing-your-ssh-keys).“
 
 {% if currentVersion == "free-pro-team@latest" %}
 If you haven't used your SSH key for a year, then
@@ -28,8 +30,4 @@ Wenn Sie Mitglied einer Organisation sind, die SSH-Zertifikate bereitstellt, kö
 
 - „[Nach vorhandenen SSH-Schlüsseln suchen](/articles/checking-for-existing-ssh-keys)“
 - „[SSH-Verbindung testen](/articles/testing-your-ssh-connection)“
-- „[Mit SSH-Schlüssel-Passphrasen arbeiten](/articles/working-with-ssh-key-passphrases)“
 - „[Fehlerbehebung bei SSH](/articles/troubleshooting-ssh)“
-{%- if currentVersion == "free-pro-team@latest" %}
-- „[Einen SSH-Schlüssel für die Verwendung in einer Organisation mit SAML Single-Sign-On autorisieren](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)“
-{%- endif %}
diff --git a/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index 50d817337b..73734a571c 100644
--- a/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ Nachdem Sie einen neuen SSH-Schlüssel zu Ihrem {% data variables.product.produc
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also add an SSH key using the {% data variables.product.prodname_cli %}. For more information, see "[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. Copy the SSH public key to your clipboard.
@@ -80,8 +88,9 @@ Nachdem Sie einen neuen SSH-Schlüssel zu Ihrem {% data variables.product.produc
   If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen.
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
-  # Herunterladen und installieren von xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
+  # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
 
   $ xclip -selection clipboard &lt; ~/.ssh/id_ed25519.pub
   # Copies the contents of the id_ed25519.pub file to your clipboard
diff --git a/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md
index eb441e95a0..d345884807 100644
--- a/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md
+++ b/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md
@@ -29,7 +29,7 @@ Wenn Sie einen GPG-Schlüssel verwenden, der mit Ihrer Beitragenderidentität un
   ```shell
   $ gpg> adduid
   ```
-6. Folge den Aufforderungen, Deinen echten Namen, Deine E-Mail-Adresse und allenfalls Kommentare anzugeben. Du kannst Deine Einträge ändern, indem Du `N`, `C` oder `E` auswählst. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %}
+6. Folge den Aufforderungen, Deinen echten Namen, Deine E-Mail-Adresse und allenfalls Kommentare anzugeben. Du kannst Deine Einträge ändern, indem Du `N`, `C` oder `E` auswählst. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} Weitere Informationen findest Du unter „[Deine Commit-E-Mail-Adresse festlegen](/articles/setting-your-commit-email-address)“.{% endif %}
   ```shell
   Real Name: <em>Octocat</em>
   Email address: <em>octocat@github.com</em>
diff --git a/translations/de-DE/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/de-DE/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index d74242084b..3858d22c9c 100644
--- a/translations/de-DE/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/de-DE/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**Hinweis:** GPG ist bei OS X und Windows nicht standardmäßig installiert. Informationen zum Installieren der GPG-Befehlszeilentools findest Du auf der [Download-Seite von GnuPG](https://www.gnupg.org/download/).
+**Note:** GPG does not come installed by default on macOS or Windows. Informationen zum Installieren der GPG-Befehlszeilentools findest Du auf der [Download-Seite von GnuPG](https://www.gnupg.org/download/).
 
 {% endnote %}
 
diff --git a/translations/de-DE/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/de-DE/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index 13ee49b915..3e4fd9c73d 100644
--- a/translations/de-DE/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/de-DE/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %}, navigate to your pull request.
 {% data reusables.repositories.review-pr-commits %}
-3. Das Feld neben dem verkürzten Commit-Hash Deines Commits zeigt, ob die Commit-Signatur verifiziert ist oder nicht. ![Signierter Commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. Um detailliertere Informationen zur Commit-Signatur anzuzeigen, klicke auf **Verified** (Verifiziert) oder **Unverified** (Nicht verifiziert). ![Verifizierter signierter Commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-Wenn Deine Commit-Signatur nicht verifiziert ist, kannst Du mehr darüber erfahren, indem Du auf das Feld **Unverified** (Nicht verifiziert) klickst. ![Nicht verifizierter signierter Commit](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![Signierter Commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. To view more detailed information about the commit signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Verifizierter signierter Commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### Den Verifizierungsstatus Deiner Tag-Signatur überprüfen
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. Klicke oben auf der Releases-Seite auf **Tags**. ![Tags-Seite](/assets/images/help/releases/tags-list.png)
-3. Das Feld neben der Tag-Beschreibung zeigt, ob die Tag-Signatur verifiziert ist oder nicht. ![Verifizierte Tag-Signatur](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. Um detailliertere Informationen zur Tag-Signatur anzuzeigen, klicke auf **Verified** (Verifiziert) oder **Unverified** (Nicht verifiziert). Wenn die Tag-Signatur nicht verifiziert ist, kannst Du mehr darüber erfahren, indem Du auf das Feld **Unverified** (Nicht verifiziert) klickst. ![Verifizierter signierter Tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. Next to your tag description, there is a box that shows whether your tag signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![Verifizierte Tag-Signatur](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. To view more detailed information about the tag signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Verifizierter signierter Tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md
index 0e016e9c0d..1fb3a84fe4 100644
--- a/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
 
-{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. Weitere Informationen findest Du unter[„Authentifizierung mit SAML Single Sign-On](/articles/about-authentication-with-saml-single-sign-on)" und[„Autorisieren eines persönlichen Zugriffstokens für die Verwendung mit SAML Single Sign-On](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. Weitere Informationen findest Du unter[„Authentifizierung mit SAML Single Sign-On](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" und[„Autorisieren eines persönlichen Zugriffstokens für die Verwendung mit SAML Single Sign-On](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### Ein Token erstellen
 
-{% if currentVersion == "free-pro-team@latest" %}1. [Überprüfe Deine E-Mail-Adresse](/articles/verifying-your-email-address), falls Du dies noch nicht getan hast.{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. [Überprüfe Deine E-Mail-Adresse](/github/getting-started-with-github/verifying-your-email-address), falls Du dies noch nicht getan hast.{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -45,13 +45,13 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
    {% else %}
    ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **Warnung:** Behandeln Deine Tokens wie Passwörter und halte sie geheim. Wenn Du mit der API arbeitest, verwende Tokens als Umgebungsvariablen, anstatt sie in Deinen Programmen fix zu kodieren.
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. Um Dein Token für die Authentifizierung bei einer Organisation zu verwenden, die SAML SSO nutzt, [autorisiere das Token für die Nutzung in einer SAML-SSO-Organisation](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. Um Ihren Token für die Authentifizierung bei einer Organisation zu verwenden, die SAML SSO nutzt, [autorisieren Sie den Token für die Nutzung einer SAML-SSO-Organisation](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
 
 ### Ein Token in der Befehlszeile verwenden
 
@@ -59,7 +59,7 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
 
 Persönliche Zugriffstoken können nur für HTTPS-Git-Vorgänge verwendet werden. Wenn Ihr Repository eine SSH-Remote-URL verwendet, müssen Sie [das Remote-Repository von SSH auf HTTPS umstellen](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
 
-Wenn Sie nicht nach einem Benutzernamen und einem Passwort gefragt werden, wurden Ihre Anmeldeinformationen möglicherweise auf Ihrem Computer zwischengespeichert. Sie können [Ihre Anmeldeinformationen in der Keychain aktualisieren](/articles/updating-credentials-from-the-osx-keychain), um das alte Passwort durch den Token zu ersetzen.
+Wenn Sie nicht nach einem Benutzernamen und einem Passwort gefragt werden, wurden Ihre Anmeldeinformationen möglicherweise auf Ihrem Computer zwischengespeichert. Sie können [Ihre Anmeldeinformationen in der Keychain aktualisieren](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain), um das alte Passwort durch den Token zu ersetzen.
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/de-DE/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..47895a80cd
--- /dev/null
+++ b/translations/de-DE/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
+
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### Enabling vigilant mode
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/de-DE/content/github/authenticating-to-github/error-permission-denied-publickey.md b/translations/de-DE/content/github/authenticating-to-github/error-permission-denied-publickey.md
index d1cc9d42ef..7fce4ec47f 100644
--- a/translations/de-DE/content/github/authenticating-to-github/error-permission-denied-publickey.md
+++ b/translations/de-DE/content/github/authenticating-to-github/error-permission-denied-publickey.md
@@ -30,7 +30,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 > debug1: Connecting to {% data variables.command_line.codeblock %} port 22.
 ```
 
-The connection should be made on port 22{% if currentVersion == "free-pro-team@latest" %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}.
+Die Verbindung sollte über Port 22 hergestellt werden{% if currentVersion == "free-pro-team@latest" %}, es sei denn, Du überschreibst die Einstellungen, um [SSH über HTTPS](/articles/using-ssh-over-the-https-port) zu verwenden{% endif %}.
 
 ### Immer den „git“-Benutzer verwenden
 
diff --git a/translations/de-DE/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/de-DE/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..ce8198c669
--- /dev/null
+++ b/translations/de-DE/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### Vorrausetzungen
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### Das Problem beheben
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. Öffne das Terminal.
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/de-DE/content/github/authenticating-to-github/generating-a-new-gpg-key.md b/translations/de-DE/content/github/authenticating-to-github/generating-a-new-gpg-key.md
index 5ec4aaaa84..114e6691be 100644
--- a/translations/de-DE/content/github/authenticating-to-github/generating-a-new-gpg-key.md
+++ b/translations/de-DE/content/github/authenticating-to-github/generating-a-new-gpg-key.md
@@ -18,7 +18,7 @@ topics:
 
 {% note %}
 
-**Hinweis:** Bevor Du einen neuen GPG-Schlüssel erzeugst, musst Du unbedingt Deine E-Mail-Adresse verifizieren. If you haven't verified your email address, you won't be able to sign commits and tags with GPG.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
+**Hinweis:** Bevor Du einen neuen GPG-Schlüssel erzeugst, musst Du unbedingt Deine E-Mail-Adresse verifizieren. Wenn Du Deine E-Mail-Adresse noch nicht verifiziert hast, kannst Du keine Commits und Tags mit GPG signieren.{% if currentVersion == "free-pro-team@latest" %} Weitere Informationen findest Du unter „[E-Mail-Adresse verifizieren](/articles/verifying-your-email-address)“.{% endif %}
 
 {% endnote %}
 
@@ -41,7 +41,7 @@ topics:
 
   {% note %}
 
-  **Hinweis:** Wenn Du zur Eingabe Deiner E-Mail-Adresse aufgefordert wirst, stelle sicher, dass Du die verifizierte E-Mail-Adresse für Dein GitHub-Konto eingibst. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %}  For more information, see "[Verifying your email address](/articles/verifying-your-email-address)" and "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %}
+  **Hinweis:** Wenn Du zur Eingabe Deiner E-Mail-Adresse aufgefordert wirst, stelle sicher, dass Du die verifizierte E-Mail-Adresse für Dein GitHub-Konto eingibst. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} Weitere Informationen findest Du unter „[Deine E-Mail-Adresse verifizieren](/articles/verifying-your-email-address)“ und „[Deine Commit-E-Mail-Adresse festlegen](/articles/setting-your-commit-email-address)“.{% endif %}
 
   {% endnote %}
 
diff --git a/translations/de-DE/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/de-DE/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 5d2f64327b..7bbccf1dd2 100644
--- a/translations/de-DE/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/de-DE/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-Wenn Du noch keinen SSH-Schlüssel besitzt, musst Du [einen neuen SSH-Schlüssel erzeugen](#generating-a-new-ssh-key). Wenn Du unsicher bist, ob Du bereits einen SSH-Schlüssel besitzt, suche nach [vorhandenen Schlüssel](/articles/checking-for-existing-ssh-keys).
+### About SSH key generation
 
-Wenn Du bei der Verwendung Deines SSH-Schlüssels Deine Passphrase nicht jedes mal erneut eingeben möchtest, kannst Du [den Schlüssel zum SSH-Agenten hinzufügen](#adding-your-ssh-key-to-the-ssh-agent), der Deine SSH-Schlüssel verwaltet und Deine Passphrase speichert.
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
 
 ### Einen neuen SSH-Schlüssel erzeugen
 
@@ -62,7 +69,7 @@ Wenn Du bei der Verwendung Deines SSH-Schlüssels Deine Passphrase nicht jedes m
 
   {% endlinux %}
 
-4. Gib bei der Eingabeaufforderung eine sichere Passphrase ein. Weitere Informationen findest Du unter „[SSH-Schlüssel-Passphrasen verwenden](/articles/working-with-ssh-key-passphrases)“.
+4. Gib bei der Eingabeaufforderung eine sichere Passphrase ein. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ Wenn Du bei der Verwendung Deines SSH-Schlüssels Deine Passphrase nicht jedes m
 
 ### Deinen SSH-Schlüssel zum SSH-Agenten hinzufügen
 
-Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner Schlüssel hinzufügst, musst Du [überprüft haben, ob bereits SSH-Schlüssel vorhanden sind](/articles/checking-for-existing-ssh-keys), und [einen neuen SSH-Schlüssel erzeugt haben](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). <span class="platform-mac">Wenn Du Deinen SSH-Schlüssel zum Agenten hinzufügst, verwende den standardmäßigen macOS-Befehl 'ssh-add‘ und nicht eine Anwendung, die von [macports](https://www.macports.org/), [homebrew](http://brew.sh/) oder einer anderen externen Quelle installiert wurde.</span>
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">Wenn Du Deinen SSH-Schlüssel zum Agenten hinzufügst, verwende den standardmäßigen macOS-Befehl 'ssh-add‘ und nicht eine Anwendung, die von [macports](https://www.macports.org/), [homebrew](http://brew.sh/) oder einer anderen externen Quelle installiert wurde.</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner S
       $ touch ~/.ssh/config
       ```
 
-    * Open your `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` if you are not using the default location and name for your `id_ed25519` key.
+    * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
 
       ```
       Host *
@@ -106,6 +113,25 @@ Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner S
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **Note:** If you see an error like this
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      add an additional config line to your `Host *` section:
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. Fügen Sie Ihren privaten SSH-Schlüssel zu ssh-agent hinzu, und speichern Sie Ihre Passphrase in der Keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner S
 
   {% endnote %}
 
-4. [Fügen Sie den SSH-Schlüssel zu Ihrem GitHub-Konto hinzu](/articles/adding-a-new-ssh-key-to-your-github-account).
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner S
 2. Fügen Sie Ihren privaten SSH-Schlüssel zu ssh-agent hinzu. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Fügen Sie den SSH-Schlüssel zu Ihrem GitHub-Konto hinzu](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner S
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  In some Linux environments, you need root access to run the command:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. Fügen Sie Ihren privaten SSH-Schlüssel zu ssh-agent hinzu. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Fügen Sie den SSH-Schlüssel zu Ihrem GitHub-Konto hinzu](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endif %}
+
 ### Weiterführende Informationen
 
 - „[Informationen zu SSH](/articles/about-ssh)“
diff --git a/translations/de-DE/content/github/authenticating-to-github/index.md b/translations/de-DE/content/github/authenticating-to-github/index.md
index cf52517b0a..09c9662b2d 100644
--- a/translations/de-DE/content/github/authenticating-to-github/index.md
+++ b/translations/de-DE/content/github/authenticating-to-github/index.md
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/de-DE/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/de-DE/content/github/authenticating-to-github/managing-commit-signature-verification.md
index 2c7f1b7138..c1f3f15801 100644
--- a/translations/de-DE/content/github/authenticating-to-github/managing-commit-signature-verification.md
+++ b/translations/de-DE/content/github/authenticating-to-github/managing-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: Verifizierung einer Commit-Signatur verwalten
-intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} will verify these signatures so other people will know that your commits come from a trusted source.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}'
+intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} verifiziert diese Signaturen, damit andere Personen wissen, dass Ihre Commits von einer vertrauenswürdigen Quelle stammen.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} signiert automatisch Commits, die Sie über die {% data variables.product.product_name %}-Weboberfläche erstellt haben.{% endif %}'
 redirect_from:
   - /articles/generating-a-gpg-key/
   - /articles/signing-commits-with-gpg/
diff --git a/translations/de-DE/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/de-DE/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index c9beac4385..d8ad9c9691 100644
--- a/translations/de-DE/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/de-DE/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ Sie kannst die Anmeldeinformationen oder die Wiederherstellungscodes Deiner Zwei
 5. Gib unter „One-time password" (Einmal gültiges Passwort) das temporäre Passwort aus dem Wiederherstellungs-E-Mail von {% data variables.product.prodname_dotcom %} ein. ![Feld „One-time password" (Einmal gültiges Passwort)](/assets/images/help/2fa/one-time-password-field.png)
 6. Klicke auf **Verify email address** (Verifiziere die E-Mail-Adresse).
 7. Wähle einen alternativen Verifizierungsfaktor.
-    - Wenn Du Dein aktuelles Gerät bereits früher für die Anmeldung an dieses Konto verwendet hast und dieses Gerät zur Verifizierung verwenden möchtest, klicke auf **Verify this device** (Dieses Gerät überprüfen).
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - Wenn Du bereits früher einen SSH-Schlüssel für dieses Konto eingerichtet hast und den SSH-Schlüssel zur Verifizierung verwenden möchtest, klicke auf **SSH key** (SSH-Schlüssel).
     - Wenn Du bereits früher ein persönliches Zugriffstoken eingerichtet hast und das persönliche Zugriffstoken zur Verifizierung verwenden möchtest, klicke auf **Personal access token** (Persönliches Zugriffstoken). ![Schaltfläche „Alternative verification" (Alternative Verifizierung)](/assets/images/help/2fa/alt-verifications.png)
 8. Ein Mitarbeiter von {% data variables.contact.github_support %} wird Deine Anfrage prüfen und Dir innerhalb von 3-5 Werktagen eine E-Mail senden. Wenn Deine Anfrage genehmigt wurde, wirst Du einen Link erhalten, um Deinen Konto-Wiederherstellungsprozess abzuschließen. Wenn Deine Anfrage abgelehnt wurde, enthält die E-Mail eine Möglichkeit, den Support für alle weiteren Fragen zu kontaktieren.
diff --git a/translations/de-DE/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/de-DE/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index 4d6ebee334..7a812de330 100644
--- a/translations/de-DE/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/de-DE/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -15,7 +15,7 @@ topics:
 
 {% mac %}
 
-Wenn Du [Deine SSH-Passphrase mit der OS X Keychain konfiguriert hast](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), kannst Du sie vielleicht wiederherstellen.
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
 
 1. Suche im Finder die App **Keychain Access**. ![ Suchleiste von Spotlight](/assets/images/help/setup/keychain-access.png)
 2. Suche in Keychain Access nach **SSH**.
diff --git a/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md
index ecfaaf9548..c0b69191d7 100644
--- a/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md
+++ b/translations/de-DE/content/github/authenticating-to-github/reviewing-your-security-log.md
@@ -15,7 +15,7 @@ topics:
 
 ### Zugriff auf Dein Sicherheitsprotokoll
 
-The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}.
+Das Sicherheitsprotokoll listet alle in den letzten 90 Tagen durchgeführten Aktionen auf{% if currentVersion ver_lt "enterprise-server@2.20" %}, maximal 50{% endif %}.
 
 {% data reusables.user_settings.access_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
@@ -38,23 +38,23 @@ The security log lists all actions performed within the last 90 days{% if curren
 
 The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
 
-| Kategoriename                                                                                                                    | Beschreibung                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %}
-| [`account_recovery_token`](#account_recovery_token-category-actions)                                                             | Umfasst alle Aktivitäten in Verbindung mit dem [Hinzufügen eines Wiederherstellungstokens](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                  |
-| [`Abrechnung`](#billing-category-actions)                                                                                        | Umfasst alle Aktivitäten in Verbindung mit Ihren Abrechnungsinformationen.                                                                                                                                                                                                                                                                                                                                                     |
-| [`codespaces`](#codespaces-category-actions)                                                                                     | Contains all activities related to {% data variables.product.prodname_codespaces %}. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."                                                                                                                                                                             |
-| [`marketplace_agreement_signature (Unterzeichnung Marketplace-Vereinbarung)`](#marketplace_agreement_signature-category-actions) | Umfasst alle Aktivitäten in Verbindung mit der Signierung der {% data variables.product.prodname_marketplace %}-Entwicklervereinbarung.                                                                                                                                                                                                                                                                                        |
+| Kategoriename                                                                                                                    | Beschreibung                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| [`account_recovery_token`](#account_recovery_token-category-actions)                                                             | Umfasst alle Aktivitäten in Verbindung mit dem [Hinzufügen eines Wiederherstellungstokens](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                       |
+| [`Abrechnung`](#billing-category-actions)                                                                                        | Umfasst alle Aktivitäten in Verbindung mit Ihren Abrechnungsinformationen.                                                                                                                                                                                                                                                                                                                                                                                          |
+| [`codespaces`](#codespaces-category-actions)                                                                                     | Contains all activities related to {% data variables.product.prodname_codespaces %}. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."                                                                                                                                                                                                                  |
+| [`marketplace_agreement_signature (Unterzeichnung Marketplace-Vereinbarung)`](#marketplace_agreement_signature-category-actions) | Umfasst alle Aktivitäten in Verbindung mit der Signierung der {% data variables.product.prodname_marketplace %}-Entwicklervereinbarung.                                                                                                                                                                                                                                                                                                                             |
 | [`marketplace_listing (Eintrag auf Marketplace)`](#marketplace_listing-category-actions)                                         | Umfasst alle Aktivitäten in Verbindung mit dem Eintragen von Apps auf {% data variables.product.prodname_marketplace %}.{% endif %}
-| [`oauth_access`](#oauth_access-category-actions)                                                                                 | Contains all activities related to [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) you've connected with.{% if currentVersion == "free-pro-team@latest" %}
+| [`oauth_access`](#oauth_access-category-actions)                                                                                 | Umfasst alle Aktivitäten in Verbindung mit [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps), zu denen Du eine Verbindung hergestellt hast.{% if currentVersion == "free-pro-team@latest" %}
 | [`payment_method`](#payment_method-category-actions)                                                                             | Umfasst alle Aktivitäten in Verbindung mit der Bezahlung Deines {% data variables.product.prodname_dotcom %}-Abonnements.{% endif %}
-| [`profile_picture`](#profile_picture-category-actions)                                                                           | Umfasst alle Aktivitäten in Verbindung mit Deinem Profilbild.                                                                                                                                                                                                                                                                                                                                                                  |
-| [`project (Projekt)`](#project-category-actions)                                                                                 | Umfasst alle Aktivitäten in Verbindung mit Projektboards.                                                                                                                                                                                                                                                                                                                                                                      |
-| [`public_key`](#public_key-category-actions)                                                                                     | Umfasst alle Aktivitäten in Verbindung mit [Deinen öffentlichen SSH-Schlüsseln](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                        |
-| [`repo`](#repo-category-actions)                                                                                                 | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %}
-| [`sponsors`](#sponsors-category-actions)                                                                                         | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+| [`profile_picture`](#profile_picture-category-actions)                                                                           | Umfasst alle Aktivitäten in Verbindung mit Deinem Profilbild.                                                                                                                                                                                                                                                                                                                                                                                                       |
+| [`project (Projekt)`](#project-category-actions)                                                                                 | Umfasst alle Aktivitäten in Verbindung mit Projektboards.                                                                                                                                                                                                                                                                                                                                                                                                           |
+| [`public_key`](#public_key-category-actions)                                                                                     | Umfasst alle Aktivitäten in Verbindung mit [Deinen öffentlichen SSH-Schlüsseln](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                                             |
+| [`repo`](#repo-category-actions)                                                                                                 | Umfasst alle Aktivitäten in Verbindung mit den Repositorys, deren Inhaber Du bist.{% if currentVersion == "free-pro-team@latest" %}
+| [`sponsors`](#sponsors-category-actions)                                                                                         | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 | [`Team`](#team-category-actions)                                                                                                 | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %}
 | [`two_factor_authentication`](#two_factor_authentication-category-actions)                                                       | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
-| [`Benutzer`](#user-category-actions)                                                                                             | Umfasst alle Aktivitäten in Verbindung mit Deinem Konto.                                                                                                                                                                                                                                                                                                                                                                       |
+| [`Benutzer`](#user-category-actions)                                                                                             | Umfasst alle Aktivitäten in Verbindung mit Deinem Konto.                                                                                                                                                                                                                                                                                                                                                                                                            |
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -90,6 +90,10 @@ An overview of some of the most common actions that are recorded as events in th
 
 | Aktion                               | Beschreibung                                                                                                                                                                                                             |
 | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create`                             | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                 |
+| `resume`                             | Triggered when you resume a suspended codespace.                                                                                                                                                                         |
+| `delete`                             | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                 |
+| `manage_access_and_security`         | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                           |
 | `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). |
 
 #### `marketplace_agreement_signature` category actions
@@ -157,46 +161,48 @@ An overview of some of the most common actions that are recorded as events in th
 
 #### `repo` category actions
 
-| Aktion                                | Beschreibung                                                                                                                                                                                                                                                                                                                                       |
-| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `access`                              | Wird ausgelöst, wenn die Sichtbarkeit eines Repositorys, dessen Inhaber Du bist, [von „privat“ auf „öffentlich“ gesetzt wird](/articles/making-a-private-repository-public) (oder umgekehrt).                                                                                                                                                      |
-| `add_member`                          | Triggered when a {% data variables.product.product_name %} user is {% if currentVersion == "free-pro-team@latest" %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository. |
-| `add_topic`                           | Wird ausgelöst, wenn ein Repository-Inhaber einem Repository [ein Thema hinzufügt](/articles/classifying-your-repository-with-topics).                                                                                                                                                                                                             |
+| Aktion                                | Beschreibung                                                                                                                                                                                                                                                                                                                                                              |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                              | Wird ausgelöst, wenn die Sichtbarkeit eines Repositorys, dessen Inhaber Du bist, [von „privat“ auf „öffentlich“ gesetzt wird](/articles/making-a-private-repository-public) (oder umgekehrt).                                                                                                                                                                             |
+| `add_member`                          | Wird ausgelöst, wenn ein {% data variables.product.product_name %}-Benutzer für ein Repository {% if currentVersion == "free-pro-team@latest" %}[zum Zugriff als Mitarbeiter eingeladen wird](/articles/inviting-collaborators-to-a-personal-repository){% else %}[Zugriff als Mitarbeiter erhält](/articles/inviting-collaborators-to-a-personal-repository){% endif %}. |
+| `add_topic`                           | Wird ausgelöst, wenn ein Repository-Inhaber einem Repository [ein Thema hinzufügt](/articles/classifying-your-repository-with-topics).                                                                                                                                                                                                                                    |
 | `archived`                            | Wird ausgelöst, wenn ein Repository-Inhaber ein [Repository archiviert](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %}
-| `config.disable_anonymous_git_access` | Wird ausgelöst, wenn für ein öffentliches Repository der [anonyme Git-Lesezugriff deaktiviert](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) wird.                                                                                                                                           |
-| `config.enable_anonymous_git_access`  | Wird ausgelöst, wenn für ein öffentliches Repository der [anonyme Git-Lesezugriff aktiviert](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) wird.                                                                                                                                             |
-| `config.lock_anonymous_git_access`    | Wird ausgelöst, wenn für ein Repository die [Einstellung für den anonymen Git-Lesezugriff gesperrt](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access) wird.                                                                                                                  |
+| `config.disable_anonymous_git_access` | Wird ausgelöst, wenn für ein öffentliches Repository der [anonyme Git-Lesezugriff deaktiviert](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) wird.                                                                                                                                                                  |
+| `config.enable_anonymous_git_access`  | Wird ausgelöst, wenn für ein öffentliches Repository der [anonyme Git-Lesezugriff aktiviert](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) wird.                                                                                                                                                                    |
+| `config.lock_anonymous_git_access`    | Wird ausgelöst, wenn für ein Repository die [Einstellung für den anonymen Git-Lesezugriff gesperrt](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access) wird.                                                                                                                                         |
 | `config.unlock_anonymous_git_access`  | Wird ausgelöst, wenn für ein Repository die [Einstellungssperre für den anonymen Git-Lesezugriff aufgehoben](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access) wird.{% endif %}
-| `create`                              | Wird bei der [Erstellung eines neuen Repositorys](/articles/creating-a-new-repository) ausgelöst.                                                                                                                                                                                                                                                  |
-| `destroy`                             | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %}
-| `deaktivieren`                        | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| `create`                              | Wird bei der [Erstellung eines neuen Repositorys](/articles/creating-a-new-repository) ausgelöst.                                                                                                                                                                                                                                                                         |
+| `destroy`                             | Wird ausgelöst, wenn ein [Repository gelöscht](/articles/deleting-a-repository) wird.{% if currentVersion == "free-pro-team@latest" %}
+| `deaktivieren`                        | Wird ausgelöst, wenn ein Repository deaktiviert wird (zum Beispiel aufgrund [unzureichender Deckung](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %}
 | `aktivieren`                          | Wird ausgelöst, wenn ein Repository wieder aktiviert wird.{% endif %}
-| `remove_member`                       | Wird ausgelöst, wenn ein {% data variables.product.product_name %}-Benutzer [als Mitarbeiter aus einem Repository entfernt wird](/articles/removing-a-collaborator-from-a-personal-repository).                                                                                                                                                    |
-| `remove_topic`                        | Wird ausgelöst, wenn ein Repository-Inhaber ein Thema aus einem Repository entfernt.                                                                                                                                                                                                                                                               |
-| `rename`                              | Wird ausgelöst, wenn ein [Repository umbenannt](/articles/renaming-a-repository) wird.                                                                                                                                                                                                                                                             |
-| `übertragen`                          | Wird ausgelöst, wenn ein [Repository übertragen](/articles/how-to-transfer-a-repository) wird.                                                                                                                                                                                                                                                     |
-| `transfer_start`                      | Wird ausgelöst, wenn die Übertragung eines Repositorys initiiert wurde.                                                                                                                                                                                                                                                                            |
-| `unarchived`                          | Wird ausgelöst, wenn ein Repository-Inhaber die Archivierung eines Repositorys aufhebt.                                                                                                                                                                                                                                                            |
+| `remove_member`                       | Wird ausgelöst, wenn ein {% data variables.product.product_name %}-Benutzer [als Mitarbeiter aus einem Repository entfernt wird](/articles/removing-a-collaborator-from-a-personal-repository).                                                                                                                                                                           |
+| `remove_topic`                        | Wird ausgelöst, wenn ein Repository-Inhaber ein Thema aus einem Repository entfernt.                                                                                                                                                                                                                                                                                      |
+| `rename`                              | Wird ausgelöst, wenn ein [Repository umbenannt](/articles/renaming-a-repository) wird.                                                                                                                                                                                                                                                                                    |
+| `übertragen`                          | Wird ausgelöst, wenn ein [Repository übertragen](/articles/how-to-transfer-a-repository) wird.                                                                                                                                                                                                                                                                            |
+| `transfer_start`                      | Wird ausgelöst, wenn die Übertragung eines Repositorys initiiert wurde.                                                                                                                                                                                                                                                                                                   |
+| `unarchived`                          | Wird ausgelöst, wenn ein Repository-Inhaber die Archivierung eines Repositorys aufhebt.                                                                                                                                                                                                                                                                                   |
 
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` category actions
 
-| Aktion                                        | Beschreibung                                                                                                                                                                                                                                                                                                                                |
-| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo_funding_link_button_toggle`             | Wird ausgelöst, wenn Du eine Sponsorenschaltfläche in Deinem Repository aktivierst oder deaktivierst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“)                                                                                                              |
-| `repo_funding_links_file_action`              | Wird ausgelöst, wenn Du die FUNDING-Datei in Deinem Repository änderst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“)                                                                                                                                            |
-| `sponsor_sponsorship_cancel`                  | Wird ausgelöst, wenn Sie ein Sponsoring beenden (siehe „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                                                                                                                                    |
-| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                                              |
-| `sponsor_sponsorship_preference_change`       | Wird ausgelöst, wenn Sie Ihre Einstellung zum Empfangen von E-Mail-Aktualisierungen von einem gesponserten Entwickler ändern (siehe „[Sponsoring verwalten](/articles/managing-your-sponsorship)“).                                                                                                                                         |
-| `sponsor_sponsorship_tier_change`             | Wird ausgelöst, wenn Sie Ihr Sponsoring upgraden oder herabstufen (siehe „[Sponsoring upgraden](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                                                   |
-| `sponsored_developer_approve`                 | Wird ausgelöst, wenn Dein {% data variables.product.prodname_sponsors %}-Konto genehmigt ist (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                |
-| `sponsored_developer_create`                  | Wird aufgelöst, wenn Dein {% data variables.product.prodname_sponsors %}-Konto erstellt wird (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                |
-| `sponsored_developer_profile_update`          | Wird ausgelöst, wenn Du Dein „unterstützter Benutzer"-Profil veränderst (siehe „[Deine Profildetails für {% data variables.product.prodname_sponsors %} verändern](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                    |
-| `sponsored_developer_request_approval`        | Wird ausgelöst, wenn Du Deine Bewerbung für {% data variables.product.prodname_sponsors %} für die Bewilligung einreichst (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")   |
-| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                                               |
-| `sponsored_developer_update_newsletter_send`  | Wird ausgelöst, wenn Sie Ihren Sponsoren eine E-Mail-Aktualisierung senden (siehe „[Sponsoren kontaktieren](/articles/contacting-your-sponsors)“).                                                                                                                                                                                          |
-| `waitlist_invite_sponsored_developer`         | Wird ausgelöst, wenn Du eingeladen wirst, {% data variables.product.prodname_sponsors %} von der Warteliste her beizutreten (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
-| `waitlist_join`                               | Wird ausgelöst, wenn Du der Warteliste beitrittst, um ein „unterstützter Entwickler" zu werden (siehe [{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                               |
+| Aktion                                        | Beschreibung                                                                                                                                                                                                                                                                                                    |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                |
+| `repo_funding_links_file_action`              | Wird ausgelöst, wenn Du die FUNDING-Datei in Deinem Repository änderst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“)                                                                                                                |
+| `sponsor_sponsorship_cancel`                  | Wird ausgelöst, wenn Sie ein Sponsoring beenden (siehe „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                                                                                                        |
+| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                             |
+| `sponsor_sponsorship_tier_change`             | Wird ausgelöst, wenn Sie Ihr Sponsoring upgraden oder herabstufen (siehe „[Sponsoring upgraden](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                       |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                      |
+| `sponsored_developer_disable`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled                                                                                                                                                                                                                          |
+| `sponsored_developer_redraft`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                   |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
+| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                                  |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                       |
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -258,4 +264,3 @@ An overview of some of the most common actions that are recorded as events in th
 | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `aktualisieren` | Wird ausgelöst, wenn Sie den Status Ihres Profils festlegen oder ändern. Weitere Informationen findest Du unter „[Status festlegen](/articles/personalizing-your-profile/#setting-a-status).“ |
 | `destroy`       | Wird ausgelöst, wenn Sie den Status Ihres Profils löschen.                                                                                                                                    |
-
diff --git a/translations/de-DE/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/de-DE/content/github/authenticating-to-github/updating-your-github-access-credentials.md
index 836fa0d37b..ad9b9b194d 100644
--- a/translations/de-DE/content/github/authenticating-to-github/updating-your-github-access-credentials.md
+++ b/translations/de-DE/content/github/authenticating-to-github/updating-your-github-access-credentials.md
@@ -17,7 +17,7 @@ topics:
 {% if currentVersion != "github-ae@latest" %}
 ### Neues Passwort anfordern
 
-1. To request a new password, visit {% if currentVersion == "free-pro-team@latest" %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
+1. Rufen Sie zur Anforderung eines neuen Passworts {% if currentVersion == "free-pro-team@latest" %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %} auf.
 2. Gib die Deinem persönlichen {% data variables.product.product_name %}-Konto zugeordnete E-Mail-Adresse ein, und klicke auf **Send password reset email** (E-Mail für Passwortzurücksetzung anfordern). Die E-Mail wird an die Backup-E-Mail-Adresse gesendet, sofern Du diese konfiguriert hast. ![Dialogfeld zum Anfordern einer E-Mail für die Passwortzurücksetzung](/assets/images/help/settings/password-recovery-email-request.png)
 3. Die E-Mail enthält einen Link, über den Du Dein Passwort zurücksetzen kannst. Auf diesen Link musst Du innerhalb von drei Stunden nach Erhalt der E-Mail klicken. Falls Du keine E-Mail von uns erhalten hast, siehe in Deinem Spam-Ordner nach.
 4. Nach dem Klicken auf den Link in Deiner E-Mail wirst Du zur Eingabe eines neuen Passworts aufgefordert. ![Feld für Passwortwiederherstellung](/assets/images/help/settings/password_recovery_page.png)
diff --git a/translations/de-DE/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/de-DE/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index 1172c98589..e13421580f 100644
--- a/translations/de-DE/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/de-DE/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -11,7 +11,7 @@ topics:
 
 {% tip %}
 
-**GitHub Enterprise-Benutzer**: Der Zugriff auf GitHub Enterprise über SSH über den HTTPS-Port wird derzeit nicht unterstützt.
+**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
 
 {% endtip %}
 
diff --git a/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index 48d3438023..563ff8b768 100644
--- a/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/de-DE/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -104,7 +104,7 @@ Die Ausführung des `ssh-agent`-Prozesses wird fortgesetzt, bis Du Dich abmeldes
 
 ### Deine Passphrase in Keychain speichern
 
-In OS X Leopard bis OS X El Capitan werden folgende standardmäßigen Privatschlüssel-Dateien automatisch verarbeitet:
+On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index 075a4ebc44..a66493f7df 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: Informationen zu gemeinschaftlichen Entwicklungsmodellen
-intro: 'Die Art und Weise, wie Du Pull Requests verwendest, hängt von der Art des Entwicklungsmodells in Deinem Projekt ab.'
+intro: 'Die Art und Weise, wie Du Pull Requests verwendest, hängt von der Art des Entwicklungsmodells in Deinem Projekt ab. You can use the fork and pull model or the shared repository model.'
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-Es gibt zwei Hauptarten von Entwicklungsmodellen, mit denen Du Pull Requests verwenden würdest. Mit dem *fork and pull model* (forken und abrufen Modell) kann jeder ein bestehendes Repository forken und Veränderungen an seine persönlichen Forks übertragen. Du benötigst keine Berechtigungen zum Quell-Repository, um an eine benutzereigene Fork zu übertragen. Die Änderungen können vom Projektbetreuer in das Quell-Repository gezogen werden. Wenn Du einen Pull Request öffnest, der Änderungen von Deiner benutzereigenen Fork zu einem Branch im Quell- (vorgelagerten) Repository vorschlägt, kannst Du allen Personen mit Push Zugriff auf das vorgelagerte Repository erlauben, Änderungen an Deinen Pull Requests zu machen.  Dieses Modell ist bei Open-Source-Projekten beliebt, da es Probleme für neue Mitarbeiter reduziert und Benutzern ermöglicht, unabhängig und ohne vorherige Koordination zu arbeiten.
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. Du benötigst keine Berechtigungen zum Quell-Repository, um an eine benutzereigene Fork zu übertragen. Die Änderungen können vom Projektbetreuer in das Quell-Repository gezogen werden. Wenn Du einen Pull Request öffnest, der Änderungen von Deiner benutzereigenen Fork zu einem Branch im Quell- (vorgelagerten) Repository vorschlägt, kannst Du allen Personen mit Push Zugriff auf das vorgelagerte Repository erlauben, Änderungen an Deinen Pull Requests zu machen.  Dieses Modell ist bei Open-Source-Projekten beliebt, da es Probleme für neue Mitarbeiter reduziert und Benutzern ermöglicht, unabhängig und ohne vorherige Koordination zu arbeiten.
 
 {% tip %}
 
@@ -20,7 +22,9 @@ Es gibt zwei Hauptarten von Entwicklungsmodellen, mit denen Du Pull Requests ver
 
 {% endtip %}
 
-Beim *shared repository model* (Modell mit gemeinsamen Repositorys) erhalten Mitarbeiter Push-Zugriff auf ein einzelnes gemeinsames Repository, und Themen-Branches werden erstellt, wenn Änderungen vorgenommen werden müssen. Pull Requests sind in diesem Modell nützlich, da sie einen Code-Review und eine allgemeine Diskussion über eine Reihe von Änderungen initiieren, bevor die Änderungen in den Hauptentwicklungs-Branch integriert werden. Dieses Modell kommt häufiger bei kleinen Teams und Organisationen zur Anwendung, die an privaten Projekten zusammenarbeiten.
+### Shared repository model
+
+Beim Modell für freigegebene Repositorys erhalten Mitarbeiter Push-Zugriff auf ein einzelnes freigegebenes Repository, und Themen-Branches werden erstellt, wenn Änderungen vorgenommen werden müssen. Pull Requests sind in diesem Modell nützlich, da sie einen Code-Review und eine allgemeine Diskussion über eine Reihe von Änderungen initiieren, bevor die Änderungen in den Hauptentwicklungs-Branch integriert werden. Dieses Modell kommt häufiger bei kleinen Teams und Organisationen zur Anwendung, die an privaten Projekten zusammenarbeiten.
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-forks.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-forks.md
index e655351b3f..bf740f5738 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-forks.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-forks.md
@@ -20,7 +20,7 @@ Das Forking eines Repositorys ist ähnlich wie das Kopieren eines Repositorys, m
 
 {% data reusables.repositories.desktop-fork %}
 
-Das Löschen eines Forks wird das ursprüngliche vorgelagerte Repository nicht löschen. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% if currentVersion == "free-pro-team@latest" %} You cannot restore a deleted forked repository. Weitere Informationen findest Du unter „[Ein gelöschtes Repository wiederherstellen](/articles/restoring-a-deleted-repository)“.{% endif %}
+Das Löschen eines Forks wird das ursprüngliche vorgelagerte Repository nicht löschen. Du kannst beliebige Änderungen an Deiner Fork vornehmen – Mitarbeiter hinzufügen, Dateien umbenennen, {% data variables.product.prodname_pages %} generieren –, ohne Auswirkungen auf das Original.{% if currentVersion == "free-pro-team@latest" %} Du kannst ein geforktes Repository nach dem Löschen nicht wiederherstellen. Weitere Informationen findest Du unter „[Ein gelöschtes Repository wiederherstellen](/articles/restoring-a-deleted-repository)“.{% endif %}
 
 In Open-Source-Projekten werden Forks oft verwendet, um mehrfach Ideen oder Änderungen durchzuspielen, bevor sie an das vorgelagerte Repository zurückgesendet werden. Wenn Du Änderungen in Deiner benutzereigenen Fork vornimmst und einen Pull Request öffnest, die Deine Arbeit mit dem vorgelagerten Repository vergleicht, kannst Du jedem mit Push-Zugriff auf das vorgelagerte Repository die Erlaubnis geben, Änderungen in deinen Pull-Request-Branch zu übertragen. Dies beschleunigt die Zusammenarbeit, indem es den Repository-Betreuern erlaubt, Commits zu erstellen oder Tests vor dem Zusammenführen lokal aus einer benutzereigenen Fork zu Deinem Pull-Request-Branch auszuführen. Du kannst keine Push-Berechtigungen an eine Fork geben, die einer Organisation gehört.
 
@@ -32,5 +32,5 @@ If you want to create a new repository from the contents of an existing reposito
 
 - „[Informationen zu gemeinschaftlichen Entwicklungsmodellen](/articles/about-collaborative-development-models)“
 - „[Einen Pull Request von einem Fork erstellen](/articles/creating-a-pull-request-from-a-fork)“
-- [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %}
+- [Open-Source-Leitfäden](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md
index 410b0fecc1..d35032991a 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews.md
@@ -15,11 +15,11 @@ topics:
 
 Nachdem ein Pull-Request geöffnet wurde, kann jeder mit *Lese*-Zugriff die vorgeschlagenen Änderungen überprüfen und kommentieren. Du kannst auch spezifische Änderungen an Codezeilen vorschlagen, die der Autor direkt aus dem Pull-Request anwenden kann. Weitere Informationen findest Du unter „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/articles/reviewing-proposed-changes-in-a-pull-request).“
 
-Repository-Inhaber und -Mitarbeiter können von einer bestimmten Person einen Review des Pull Requests anfordern. Organisationsmitglieder können auch einen Review eines Pull Requests von einem Team mit Lesezugriff auf das Repository anfordern. Weitere Informationen findest Du unter „[Einen Pull-Request-Review anfordern](/articles/requesting-a-pull-request-review).“ {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
+Repository-Inhaber und -Mitarbeiter können von einer bestimmten Person einen Review des Pull Requests anfordern. Organisationsmitglieder können auch einen Review eines Pull Requests von einem Team mit Lesezugriff auf das Repository anfordern. Weitere Informationen findest Du unter „[Einen Pull-Request-Review anfordern](/articles/requesting-a-pull-request-review).“ {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Du kannst anstelle des gesamten Teams auch nur eine Teilmenge von Teammitgliedern angeben, die automatisch zugewiesen werden sollen. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
 
 Reviews ermöglichen eine Diskussion der vorgeschlagenen Änderungen und tragen dazu bei, dass die Änderungen den Beitragsrichtlinien des Repositorys wie auch anderen Qualitätsstandards entsprechen. Du kannst definieren, welche Personen oder Teams bestimmte Codetypen oder -bereiche in einer CODEOWNERS-Datei besitzen. Wenn durch einen Pull Request Code mit einem definierten Inhaber geändert wird, wird diese Person oder dieses Team automatisch als Reviewer angefordert. Weitere Informationen finden Sie unter „[Informationen zu Codeinhabern](/articles/about-code-owners/)“.
 
-{% if currentVersion == "free-pro-team@latest" %}You can schedule reminders for pull requests that need to be reviewed. Weitere Informationen findest Du unter „[Geplante Erinnerungen für Pull-Requests verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Du kannst Erinnerungen für Pull Requests planen, die überprüft werden müssen. Weitere Informationen findest Du unter „[Geplante Erinnerungen für Pull-Requests verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)."{% endif %}
 
 ![Header eines Reviews, der Änderungen mit Zeilenkommentaren anfordert](/assets/images/help/pull_requests/review-header-with-line-comment.png)
 
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index fb7e7aa4c9..072f7633c6 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -53,18 +53,18 @@ Wenn ein Repository so konfiguriert ist, dass es automatisch Prüfungen für Pus
 
 Um Prüfungen für Deinen Commit zu überspringen oder anzufordern, füge eine der folgenden Trailerzeilen an das Ende Deiner Commit-Mitteilung an:
 
-- Um Prüfungen für einen Commit zu _überspringen_, gib Deine Commit-Mitteilung und eine kurze, aussagekräftige Beschreibung Deiner Änderungen ein. Füge nach Deiner Commit-Beschreibung anstelle eines abschließenden Anführungszeichens zwei leere Zeilen hinzu, gefolgt von `skip-checks: true`:
+- Um Prüfungen für einen Commit zu _überspringen_, gib Deine Commit-Mitteilung und eine kurze, aussagekräftige Beschreibung Deiner Änderungen ein. After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - Um Prüfungen für einen Commit _anzufordern_, gib Deine Commit-Mitteilung und eine kurze, aussagekräftige Beschreibung Deiner Änderungen ein. Füge nach Deiner Commit-Beschreibung anstelle eines abschließenden Anführungszeichens zwei leere Zeilen hinzu, gefolgt von `request-checks: true`:
+- Um Prüfungen für einen Commit _anzufordern_, gib Deine Commit-Mitteilung und eine kurze, aussagekräftige Beschreibung Deiner Änderungen ein. After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 4542627a56..9f17e64f20 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
 title: Die Zustand eines Pull Requests ändern
-intro: 'You can mark a draft pull request as ready for review{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} or convert a pull request to a draft{% endif %}.'
+intro: 'Du kannst einen Pull-Request-Review als bereit zur Überprüfung markieren{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} oder einen Pull Request in einen Entwurf umwandeln{% endif %}.'
 permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request.
 product: '{% data reusables.gated-features.draft-prs %}'
 redirect_from:
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. Klicke in der Liste „Pull Requests“ auf den Pull Request, den Du als „Ready for review“ (Bereit zur Überprüfung) markieren möchtest.
 3. Klicke im Merge-Feld **Ready for review** (Bereit zur Überprüfung). ![Schaltfläche „Ready for review“ (Bereit für Review)](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index 32987a9e64..c83dc79035 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -18,10 +18,18 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Einen aktiven Pull Request lokal ändern
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request you'd like to modify.{% if currentVersion == "free-pro-team@latest" %}
+2. Klicke in der Liste der Pull-Requests auf die Pull-Requests, die Du ändern möchtest.{% if currentVersion == "free-pro-team@latest" %}
 3. Um auszuwählen, wo Du den Pull Request öffnen willst, wähle das Dropdownmenü „**Open with {% octicon "triangle-down" aria-label="The down triangle icon" %}**" und klicke auf eine der Registerkarten. ![Link um auf die Pull-Request-Anweisungen in der Befehlszeile zuzugreifen](/assets/images/help/pull_requests/open-with-button.png){% else %}
 3. Klicke im Merge-Feld auf **Befehlszeilenanweisungen**. Führen Sie nacheinander die Schritte durch, um den vorgeschlagenen Pull Request herunterzuladen. ![Links zum Zugriff auf Anleitungen zu Befehlszeilen-Pull-Requests](/assets/images/help/pull_requests/pull_request_show_command_line_merge.png)
 4. Klicke optional zur Ansicht der vorgeschlagenen Änderungen mit {% data variables.product.prodname_desktop %} auf **öffne dies mit {% data variables.product.prodname_desktop %}**. ![Link to open a pull request locally in Desktop](/assets/images/help/desktop/open-pr-in-desktop.png){% endif %}
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index 9fb088f91d..fd6b1a3280 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ Um auf einen vorhandenen Zeilenkommentar zu antworten, navigiere auf der Registe
 
 **Tipps:**
 - Pull-Request-Kommentare unterstützen dieselbe [Formatierung](/categories/writing-on-github) wie reguläre Kommentare auf {% data variables.product.product_name %}, z. B. @Erwähnungen, Emojis und Verweise.
-- Du kannst auf der Registerkarte **Files changed** (Dateien geändert) [Reaktionen](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) zu Kommentaren in Pull Requests hinzufügen.
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
@@ -57,5 +57,5 @@ Alle, die den Pull Request oder das Repository beobachten, erhalten eine Benachr
 ### Weiterführende Informationen
 
 - „[Einen Permalink zu einem Code-Ausschnitt erstellen](/articles/creating-a-permanent-link-to-a-code-snippet/)“
-{% if currentVersion == "free-pro-team@latest" %}- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+{% if currentVersion == "free-pro-team@latest" %}- „[Missbrauch oder Spam melden](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)“
 {% endif %}
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index 5c012a6498..f739d2d6c7 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -20,6 +20,20 @@ Du kannst festlegen, in welchen Branch Du Deine Änderungen zusammenführen möc
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+
+
+
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+
+
+
+{% endif %}
+
 
 
 ### Branch-Bereich und Ziel-Repository ändern
@@ -71,7 +85,7 @@ Wenn Du Informationen im Branch-Bereich änderst, werden die Vorschauen für „
 
 {% data reusables.repositories.asking-for-review %}
 
-Nachdem Dein Pull Request geprüft wurde, kann er [in das Repository zusammengeführt werden](/articles/merging-a-pull-request).
+Nachdem Ihr Pull Request geprüft wurde, können Sie ihn [in das Repository mergen](/articles/merging-a-pull-request).
 
 
 
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index c4670b767d..6f01e6cddd 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ If the branch you want to delete is associated with an open pull request, you mu
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. Scrolle zum Branch, den Du löschen möchtest, und klicke auf {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![Branch löschen](/assets/images/help/branches/branches-delete.png)
+1. Scrolle zum Branch, den Du löschen möchtest, und klicke auf {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![Branch löschen](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..e4f39653d7
--- /dev/null
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: Erste Schritte
+shortTitle: Erste Schritte
+intro: 'Erfahre mehr über den {% data variables.product.prodname_dotcom %}-Fluss und die verschiedenen Möglichkeiten, an Deinen Projekten mitzuwirken und sie zu diskutieren.'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md
index 2e2d77ff3f..9c33e6daf0 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Mithilfe von Issues und Pull Requests zusammenarbeiten
-intro: 'Mit dem {% data variables.product.prodname_dotcom %}-Flow können Sie Issues nachverfolgen und Änderungen diskutieren sowie Änderungen vorschlagen und in Pull Requests überprüfen.'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -18,10 +18,9 @@ topics:
 
 ### Inhaltsverzeichnis
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index 61701b38c6..be2852d152 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ Pull-Request-Entwürfe kannst du nicht zusammenführen. Weitere Informationen zu
 
 Wenn Sie die Änderungen in einem Themen-Branch nicht in den vorgelagerten Branch mergen möchten, können Sie [den Pull Request schließen](/articles/closing-a-pull-request), ohne ihn zu mergen.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Einen Pull Request auf {% data variables.product.prodname_dotcom %} zusammenführen
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..8abd7c5abb
--- /dev/null
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### Einführung
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### Issues
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### Pull Requests
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### Teamdiskussionen,
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Anstatt einen Issue in einem Repository zu öffnen, um eine Idee zu diskutieren, kannst Du das gesamte Team einbeziehen, indem Du eine Unterhaltung in einer Teamdiskussion führst.
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### Nächste Schritte:
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests).“
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“.
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md
index 598453115a..7329fe709c 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md
@@ -13,7 +13,7 @@ topics:
 
 Inhaber und Mitarbeiter eines Repositorys, das einem Benutzerkonto angehört, können Pull Requests zuweisen. Organisationsmitglieder mit Triage-Berechtigungen für ein Repository können einen Pull-Request-Review zuweisen.
 
-Inhaber oder Mitarbeiter können jeder Person, der explizit [Lesezugriff](/articles/access-permissions-on-github) auf ein benutzereigenes Repository gewährt wurde, einen Pull-Request-Review zuweisen. Organisationsmitglieder können jeder Person oder jedem Team mit Lesezugriff auf das Repository einen Pull-Request-Review zuweisen. Der angeforderte Reviewer respektive das angeforderte Team erhält eine Benachrichtigung, dass Du einen Pull-Request-Review von ihm angefordert hast. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
+Inhaber oder Mitarbeiter können jeder Person, der explizit [Lesezugriff](/articles/access-permissions-on-github) auf ein benutzereigenes Repository gewährt wurde, einen Pull-Request-Review zuweisen. Organisationsmitglieder können jeder Person oder jedem Team mit Lesezugriff auf das Repository einen Pull-Request-Review zuweisen. Der angeforderte Reviewer respektive das angeforderte Team erhält eine Benachrichtigung, dass Du einen Pull-Request-Review von ihm angefordert hast. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Wenn Du einen Review von einem Team angefordert hast und wenn Code-Review-Zuweisung aktiviert ist, werden spezifische Mitglieder angefordert und das Team wird als Reviewer entfernt werden. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
 
 {% note %}
 
diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md
index 100a2216cf..10b4f6bd07 100644
--- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md
+++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github.md
@@ -36,7 +36,7 @@ If a site administrator disables the merge conflict editor for pull requests bet
 
  {% tip %}
 
- **Tip:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. Du musst den Mergekonflikt mit einem alternativen Git-Client auflösen, oder durch Verwendung von Git auf der Befehlszeile. Weitere Informationen findest Du unter „[Mergekonflikt in der Befehlszeile beheben](/articles/resolving-a-merge-conflict-using-the-command-line).“
+ **Tipp:** Wenn die Schaltfläche **Resolve conflicts** (Konflikte beheben) deaktiviert ist, ist der Mergekonflikt Deines Pull Requests für eine Behebung auf {% data variables.product.product_name %} zu komplex{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} oder der Konflikteditor wurde vom Websiteadministrator für Pull Requests zwischen Repositorys deaktiviert{% endif %}. Du musst den Mergekonflikt mit einem alternativen Git-Client auflösen, oder durch Verwendung von Git auf der Befehlszeile. Weitere Informationen findest Du unter „[Mergekonflikt in der Befehlszeile beheben](/articles/resolving-a-merge-conflict-using-the-command-line).“
 
  {% endtip %}
 {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md
index 7350ff3940..c7ee731472 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md
@@ -23,7 +23,7 @@ Code-Besitzer werden automatisch zur Überprüfung aufgefordert, wenn jemand ein
 
 Wenn ein Benutzer mit Administrator- oder Inhaberberechtigungen die erforderlichen Reviews aktiviert hat, kann er optional auch die Genehmigung von einem Codeinhaber anfordern, bevor der Autor einen Pull Request im Repository zusammenführen kann. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging).“
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Wenn ein Team die Zuweisung zur Code-Überprüfung aktiviert hat, werden die individuellen Genehmigungen alleine nicht die Anforderung für die Genehmigung des Codeinhabers in einem geschützten Zweig erfüllen. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 Wenn eine Datei einen Codeinhaber hat, kannst Du sehen, wer der Codeinhaber ist, bevor Du einen Pull Request öffnest. In the repository, you can browse to the file and hover over
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index adc004551e..8e010d2b0a 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ Wenn Sie Ihre README-Datei im Stammverzeichnis, im Ordner `docs` oder im verborg
 
 {% endif %}
 
+### Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+The auto-generated table of contents is enabled by default for all Markdown files in a repository, but you can disable this feature for your repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under "Features", deselect **Table of contents**. ![Automatic TOC setting for repositories](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### Links zu Abschnitten in README-Dateien und auf Blob-Seiten
 
-Bei vielen Projekten gibt es zu Beginn einer README-Datei ein Inhaltsverzeichnis, mit dem Benutzer zu verschiedenen Abschnitten der Datei navigieren können. {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### Relative Links und Bildpfade in README-Dateien
 
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md
index c5dde3dcfd..40fde55f41 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Sicherung eines Repositorys durchführen
-intro: 'You can use{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git and{% endif %} the API {% if currentVersion == "free-pro-team@latest" %}or a third-party tool {% endif %}to back up your repository.'
+intro: 'Du kannst{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git und{% endif %} die API {% if currentVersion == "free-pro-team@latest" %}oder ein Drittanbieter-Werkzeug {% endif %}für die Sicherung Deines Repositorys verwenden.'
 redirect_from:
   - /articles/backing-up-a-repository
 versions:
@@ -34,7 +34,7 @@ Wenn Du ein Repository oder Wiki klonst, werden nur Git-Daten wie Projektdateien
 - [Projekte](/rest/reference/projects#list-repository-projects)
 {% endif %}
 
-Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/).
+Sobald Sie {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}eine lokale Version aller Inhalte haben, die Sie sichern möchten, können Sie ein ZIP-Archiv erstellen und {% else %}Ihr Archiv heruntergeladen haben, können Sie {% endif %}es auf eine externe Festplatte kopieren und/oder auf einen Cloud-basierten Dienst wie [Google Drive](https://www.google.com/drive/) oder [Dropbox](https://www.dropbox.com/) hochladen.
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Backup-Tools (Sicherungswerkzeuge) von Drittanbietern
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md
index 337fb82731..0974892399 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md
@@ -39,7 +39,7 @@ topics:
 {% data reusables.repositories.choose-repo-visibility %}
 6. If you're not using a template, there are a number of optional items you can pre-populate your repository with. Wenn Du ein vorhandenes Repository in {% data variables.product.product_name %} importierst, wähle keine dieser Optionen aus, da dies zu Mergekonflikten führen könnte. Sie können neue Dateien über die Benutzeroberfläche hinzufügen oder erstellen oder neue Dateien später über die Befehlszeile hinzufügen. Weitere Informationen findest Du unter „[Ein Git-Repository über die Befehlszeile importieren](/articles/importing-a-git-repository-using-the-command-line/)“, „[Eine Datei über die Befehlszeile zu einem Repository hinzufügen](/articles/adding-a-file-to-a-repository-using-the-command-line)“ und „[Mergekonflikte beheben](/articles/addressing-merge-conflicts/).“
     - Sie kannst eine README-Datei erstellen, die eine Beschreibung Deines Projekts enthält. Weitere Informationen findest Du unter „[Informationen zu README-Dateien](/articles/about-readmes/).“
-    - Du kannst eine *.gitignore*-Datei erstellen, die einen Satz an Regeln für das Ignorieren enthält. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."{% if currentVersion == "free-pro-team@latest" %}
+    - Du kannst eine *.gitignore*-Datei erstellen, die einen Satz an Regeln für das Ignorieren enthält. Weitere Informationen finden Sie unter „[Dateien ignorieren](/github/getting-started-with-github/ignoring-files)“.{% if currentVersion == "free-pro-team@latest" %}
     - Du kannst bei Bedarf eine Softwarelizenz zu Deinem Projekt hinzufügen. Weitere Informationen findest Du unter „[Ein Repository lizenzieren](/articles/licensing-a-repository)“.{% endif %}
 {% data reusables.repositories.select-marketplace-apps %}
 {% data reusables.repositories.create-repo %}
@@ -50,5 +50,5 @@ topics:
 ### Weiterführende Informationen
 
 - „[Zugriff auf die Repositorys Deiner Organisation verwalten](/articles/managing-access-to-your-organization-s-repositories)“
-- [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %}
+- [Open-Source-Leitfäden](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index 63355280e1..79f647b535 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -24,7 +24,7 @@ Jeder, der über Leseberechtigung auf eine Repository-Vorlage verfügt, kann ein
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-Du kannst die Verzeichnisstruktur und die Dateien nur aus dem Standard-Branch des Vorlagen-Repositorys einbinden oder alle Branches einbinden.
+Du kannst die Verzeichnisstruktur und die Dateien nur aus dem Standard-Branch des Vorlagen-Repositorys einbinden oder alle Branches einbinden. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 Das Erstellen eines Repositorys anhand einer Vorlage ähnelt dem Vorgang zum Forken eines Repositorys, aber es gibt entscheidende Unterschiede:
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index 9906a5a2bc..5cb6088067 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Eine Repository-Vorlage erstellen
-intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}, branches,{% endif %} and files.'
+intro: 'Du kannst ein vorhandenes Repository zu einer Vorlage machen, sodass Du wie auch andere Personen neue Repositorys mit derselben Verzeichnisstruktur{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}, Branches{% endif %} und Dateien generieren können.'
 permissions: Anyone with admin permissions to a repository can make the repository a template.
 redirect_from:
   - /articles/creating-a-template-repository
@@ -20,7 +20,7 @@ topics:
 
 Um eine Repository-Vorlage zu erstellen, musst Du ein Repository erstellen und es anschließend zu einer Vorlage machen. Weitere Informationen zum Erstellen eines Repositorys findest Du unter „[Ein neues Repository erstellen](/articles/creating-a-new-repository).“
 
-After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
index f535af2fe6..2a6f1b3df9 100644
--- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
+++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### Die richtige Lizenz auswählen
 
-Wir haben [choosealicense.com](http://choosealicense.com) erstellt, um Dich bei der Lizenzierung Deines Codes zu unterstützen. Eine Softwarelizenz informiert andere Benutzer darüber, was sie mit Deinem Quellcode machen dürfen und was nicht. Eine durchdachte Entscheidung ist also sehr wichtig.
+Wir haben [choosealicense.com](https://choosealicense.com) erstellt, um Dich bei der Lizenzierung Deines Codes zu unterstützen. Eine Softwarelizenz informiert andere Benutzer darüber, was sie mit Deinem Quellcode machen dürfen und was nicht. Eine durchdachte Entscheidung ist also sehr wichtig.
 
 Du bist nicht dazu verpflichtet, eine Lizenz auszuwählen. Bedenke jedoch, dass ohne Lizenz das standardmäßige Urheberrecht gilt – Du behältst also alle Rechte an Deinem Quellcode, und niemand darf den Code reproduzieren, verteilen oder abgeleitete Werke davon erstellen. Wenn Du ein Open-Source-Projekt erstellst, empfehlen wir Dir, eine Open-Source-Lizenz anzuwenden. Der [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) bietet zusätzliche Hilfestellung bei der Auswahl der richtigen Lizenz für Ihr Projekt.
 
@@ -76,7 +76,7 @@ Wenn Du nach einer Lizenz einer Familie suchst, enthalten die Suchergebnisse all
 
 ### Eine Lizenz erkennen
 
-[Das Open-Source-Ruby-Gem Licensee](https://github.com/licensee/licensee) vergleicht die *LICENSE*-Datei des Repositorys mit einer kurzen Liste bekannter Lizenzen. Licensee stellt außerdem die [Licenses-API](/rest/reference/licenses) bereit und [bietet Einblicke in die Lizenzierung von Repositorys auf {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Wenn Dein Repository eine Lizenz verwendet, die nicht auf der [Website „Choose a License“](http://choosealicense.com/appendix/) (eine Lizenz auswählen) aufgeführt ist, kannst Du [das Hinzufügen einer Lizenz fordern](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+[Das Open-Source-Ruby-Gem Licensee](https://github.com/licensee/licensee) vergleicht die *LICENSE*-Datei des Repositorys mit einer kurzen Liste bekannter Lizenzen. Licensee stellt außerdem die [Licenses-API](/rest/reference/licenses) bereit und [bietet Einblicke in die Lizenzierung von Repositorys auf {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Wenn Dein Repository eine Lizenz verwendet, die nicht auf der [Website „Choose a License“](https://choosealicense.com/appendix/) (eine Lizenz auswählen) aufgeführt ist, kannst Du [das Hinzufügen einer Lizenz fordern](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
 
 Wenn Dein Repository eine Lizenz verwendet, die auf der Website „Choose a License“ (Wähle eine Lizenz) aufgeführt ist, und die Lizenz nicht deutlich sichtbar oben auf der Repository-Seite angezeigt wird, enthält das Repository möglicherweise mehrere Lizenzen oder es liegt eine andere Komplexität vor. Damit Deine Lizenz erkannt wird, vereinfache Deine *LICENSE*-Datei und notiere die Komplexität an anderer Stelle, beispielsweise in der *README*-Datei Deines Repositorys.
 
@@ -92,5 +92,5 @@ Das Ziel der Bemühungen von GitHub zur Open-Source-Lizenzierung ist es, Dir ein
 
 ### Weiterführende Informationen
 
-- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% if currentVersion == "free-pro-team@latest" %}
+- Der Abschnitt „[The Legal Side of Open Source](https://opensource.guide/legal/)“ (Die rechtlichen Aspekte von Open Source) in den Open-Source-Leitfäden{% if currentVersion == "free-pro-team@latest" %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
index 2ca9c762b7..0985ee558a 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
@@ -2,49 +2,40 @@
 title: About code scanning
 intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
-redirect_from:
-  - /github/managing-security-vulnerabilities/about-automated-code-scanning
 versions:
   enterprise-server: '2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-### About {% data variables.product.prodname_code_scanning %}
+### Informationen zu {% data variables.product.prodname_code_scanning %}
 
-{% data reusables.code-scanning.about-code-scanning %}
+With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors.
 
 You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
 
-If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
 
-To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see 
-"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see  "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." 
+To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see  "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)."
 
 To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
 
-### About {% data variables.product.prodname_codeql %}
+### Informationen zu {% data variables.product.prodname_codeql %}
 
-You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. 
+{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
 
 {% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website.
 
-{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
+For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see  "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)."
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation.
-
-{% if currentVersion == "free-pro-team@latest" %}
-
-### About billing for {% data variables.product.prodname_code_scanning %}
-
-{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
-
-{% endif %}
+You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
 
 ### About third-party code scanning tools
 
@@ -54,9 +45,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 {% data reusables.code-scanning.get-started-uploading-third-party-data %}
 
-### Further reading
+### Weiterführende Informationen
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index e2a4c9f580..15f8131f40 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index c1901ad8b7..9849e9435b 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index ce01b00fb6..c2dd801c41 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -48,11 +50,11 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data variables.product.prodname_code_scanning_capc %} automatically detects and scans code written in the supported languages.
 
-To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are `cpp`, `csharp`, `go`, `java`, `javascript`, and `python`.
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index 0915cbbec3..b274f25165 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -31,11 +33,7 @@ If your workflow uses a `language` matrix, `autobuild` attempts to build each of
 
 {% note %}
 
-{% if currentVersion == "github-ae@latest" %}**Note**: For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
-{% else %}
-**Note**: If you use self-hosted runners for
-{% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
-{% endif %}
+**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 
 {% endnote %}
 
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index 8af145cb48..6ba64a919f 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### Inhaltsverzeichnis
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 25fb7e862d..7ffac959cb 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index 20c685092f..7b17f018f6 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,13 +1,15 @@
 ---
 title: Managing code scanning alerts for your repository
 shortTitle: Warnungen verwalten
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, or close alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About alerts from {% data variables.product.prodname_code_scanning %}
@@ -45,81 +47,25 @@ You need write permission to view a summary of all the alerts for a repository o
 
 Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have closed.
 
 Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
 
 ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 ### Closing an alert
 
 Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
 
-{% else %}
-
-### Dismissing or deleting alerts
-
-There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
-
-Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
-
-When you dismiss an alert:
-
-- It's dismissed in all branches.
-- The alert is removed from the number of current alerts for your project.
-- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required.
-- The reason why you closed the alert is recorded.
-- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert.
-
-When you delete an alert:
-
-- It's deleted in all branches.
-- The alert is removed from the number of current alerts for your project.
-- It is _not_ added to the "Closed" list in the summary of alerts.
-- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.
-
-To dismiss or delete alerts:
-
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
 1. Select the **Close** drop-down menu and click a reason for closing the alert.    
    ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
-
-   ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   Optionally, you can use the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
-
-  ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
-
-  ![Open an alert from the summary list](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### Dismissing multiple alerts at once
-
-If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
-
-{% endif %}
-
 ### Weiterführende Informationen
 
 - "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index ed7fdcc034..bf216d96b2 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} with a containerized build
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index 0db16c970e..8117963c5c 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
@@ -30,17 +31,13 @@ The {% data variables.product.prodname_codeql_runner %} is a command-line tool t
 {% note %}
 
 **Hinweise:**
-{% if currentVersion == "free-pro-team@latest" %}
-* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
-{% else %}
 * The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
-{% endif %}
 * The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
 {% endnote %}
 
 ### Downloading the {% data variables.product.prodname_codeql_runner %}
 
-You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+You can download the {% data variables.product.prodname_codeql_runner %} from https://github.com/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
 
 On Linux:
 
@@ -62,7 +59,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi
 Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
@@ -73,9 +70,8 @@ In addition to this, each CI server also needs:
 
 The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
 
-1. Allow the CI servers access to https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
-{% if currentVersion == "enterprise-server@2.22" %}
-1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
+1. Allow the CI servers access to https://github.com/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.
 1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
 
 ### Calling the {% data variables.product.prodname_codeql_runner %}
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index f751f6b0db..1d1b87ef53 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About SARIF support
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
index f7f7c84a41..f490ba13f9 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -21,12 +23,10 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a
 
 ### Setting up {% data variables.product.prodname_code_scanning %} using actions
 
-{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
+3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
 
    Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index f37930f8da..dc5a056df8 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -10,13 +10,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} results on pull requests
 
 In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“
+If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or close all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“
 
 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -40,28 +42,10 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
 
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Resolving an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### Dismissing an alert on your pull request
-
-An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
-
-![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index 33145fa730..e0eb0f2d3b 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index 6f77f719ba..a865027f43 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -28,7 +30,10 @@ If an automatic build of code for a compiled language within your project fails,
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -113,25 +118,13 @@ If you split your analysis into multiple workflows as described above, we still
 
 If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Results differ between analysis platforms
-
-If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
-
-On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)."
-
-{% endif %}
-
 ### Error: "Server error"
 
 If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
 
 ### Error: "Out of disk" or "Out of memory"
-On very large projects,
 
-{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the hosted {% data variables.product.prodname_actions %} runner. If you encounter this issue, try increasing the memory on the runner.
 
 ### Warning: "git checkout HEAD^2 is no longer necessary"
 
@@ -146,29 +139,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index a2fcb12970..71e1aa304e 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -19,7 +21,7 @@ If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` act
 
 You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. To upload results from third-party tools, you must use the Static Analysis Results Interchange Format (SARIF) 2.1.0 format. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)."
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %} (available if your organization is taking part in the beta program), the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
 
 - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
 - „[Einen Workflow-Lauf verwalten](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)“
@@ -58,20 +60,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Example workflow that runs the ESLint analysis tool
@@ -82,7 +86,7 @@ This example workflow runs anytime commits are pushed to the repository. The act
 
 The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -90,23 +94,26 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Weiterführende Informationen
diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index 8ae5b92b6c..4b6edc962b 100644
--- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/de-DE/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/de-DE/content/github/getting-started-with-github/about-git-subtree-merges.md
index 55d2102aec..fcdb54abd0 100644
--- a/translations/de-DE/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/de-DE/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 Typischerweise wird eine Unterstruktur zusammengeführt, um ein Repository innerhalb eines anderen Repositorys einzubinden. Das „Unterrepository“ wird in einem Ordner des Haupt-Repositorys gespeichert.
 
 Das Zusammenführen von Unterstrukturen lässt sich am besten anhand eines Beispiels erläutern. Dabei sind folgende Schritte notwendig:
diff --git a/translations/de-DE/content/github/getting-started-with-github/access-permissions-on-github.md b/translations/de-DE/content/github/getting-started-with-github/access-permissions-on-github.md
index fd892f6ae0..6a4c058e17 100644
--- a/translations/de-DE/content/github/getting-started-with-github/access-permissions-on-github.md
+++ b/translations/de-DE/content/github/getting-started-with-github/access-permissions-on-github.md
@@ -21,7 +21,7 @@ Ein Repository, das einem Benutzerkonto gehört, hat zwei Berechtigungsebenen: d
 
 ### Organisations-Konten
 
-Organization members can have *owner*{% if currentVersion == "free-pro-team@latest" %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% if currentVersion == "free-pro-team@latest" %}, while billing managers can manage billing settings{% endif %}. Die Standardrolle für alle übrigen Personen lautet „Mitglied“. Du kannst die Zugriffsberechtigungen für mehrere Mitglieder gleichzeitig in Teams verwalten. Weitere Informationen findest Du unter:
+Organisationsmitglieder können folgende Rollen haben: *Inhaber*{% if currentVersion == "free-pro-team@latest" %}, *Abrechnungsmanager*,{% endif %} oder *Mitglied*. Inhaber haben vollständigen administrativen Zugriff auf Deine Organisation{% if currentVersion == "free-pro-team@latest" %}, wohingegen Abrechnungsmanager die Abrechnungseinstellungen verwalten können{% endif %}. Die Standardrolle für alle übrigen Personen lautet „Mitglied“. Du kannst die Zugriffsberechtigungen für mehrere Mitglieder gleichzeitig in Teams verwalten. Weitere Informationen findest Du unter:
 - „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization)"
 - „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“
 - „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“
diff --git a/translations/de-DE/content/github/getting-started-with-github/be-social.md b/translations/de-DE/content/github/getting-started-with-github/be-social.md
index db31d76a33..4354262a0d 100644
--- a/translations/de-DE/content/github/getting-started-with-github/be-social.md
+++ b/translations/de-DE/content/github/getting-started-with-github/be-social.md
@@ -28,7 +28,7 @@ Klicke auf der Profilseite einer Person auf **Follow** (Folgen), um ihr zu folge
 
 ### Ein Repository beobachten
 
-Du kannst ein Repository beobachten, um über neue Pull Requests und Issues benachrichtigt zu werden. Wenn der Inhaber das Repository aktualisiert, siehst Du die Änderungen auf Deinem persönlichen Dashboard. For more information see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}."
+Du kannst ein Repository beobachten, um über neue Pull Requests und Issues benachrichtigt zu werden. Wenn der Inhaber das Repository aktualisiert, siehst Du die Änderungen auf Deinem persönlichen Dashboard. Weitere Informationen findest Du auf {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}„[Deine Abonnements ansehen](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}[Benachrichtigungen von Repositorys aktivieren und deaktivieren](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}."
 
 Klicke oben bei einem Repository, das Du beobachten möchtest, auf **Watch** (Beobachten).
 
@@ -38,6 +38,10 @@ Klicke oben bei einem Repository, das Du beobachten möchtest, auf **Watch** (Be
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### Weitere Möglichkeiten
 
 #### Pull Requests erstellen
@@ -68,8 +72,8 @@ Sie sind jetzt mit der {% data variables.product.product_name %}-Community verbu
 
 ![Ein Projekt mit Stern markieren](/assets/images/help/stars/star-a-project.png)
 
-- [Git einrichten](/articles/set-up-git)
-- [Ein Repository erstellen](/articles/create-a-repo)
-- [Ein Repository forken](/articles/fork-a-repo)
+- „[Git einrichten](/articles/set-up-git)“
+- „[Repository erstellen](/articles/create-a-repo)“
+- „[Ein Repository forken](/articles/fork-a-repo)“
 - **Soziale Interaktion**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/de-DE/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/de-DE/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index 8ed99a2041..f89ff0014b 100644
--- a/translations/de-DE/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/de-DE/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 Jedes Mal, wenn Du auf der Tastatur die <kbd>Eingabetaste</kbd> drückst, fügst Du ein unsichtbares Zeichen ein, nämlich einen Zeilenabschluss. Verschiedene Betriebssysteme handhaben Zeilenenden unterschiedlich.
 
-Wenn Du mit Git und {% data variables.product.product_name %} an Projekten zusammenarbeitest, könnte Git unerwartete Ergebnisse produzieren, wenn Du beispielsweise an einem Windows-PC arbeitest und Dein Mitarbeiter eine Änderungen unter OS X vorgenommen hat.
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 Du kannst Git so konfigurieren, dass es Zeilenenden automatisch setzt, so dass Du effektiv mit Leuten zusammenarbeiten kannst, die verschiedene Betriebssysteme verwenden.
 
@@ -25,11 +25,11 @@ Mit dem Befehl `git config core.autocrlf` kannst Du anpassen, wie Git Zeilenabsc
 
 {% mac %}
 
-Unter OS X übergib einfach `input` an die Konfiguration. Ein Beispiel:
+On macOS, you simply pass `input` to the configuration. Ein Beispiel:
 
 ```shell
 $ git config --global core.autocrlf input
-# Konfiguriere Git, damit Zeilenenden in Dateien, die Du auscheckst, für OS X korrekt sind
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/de-DE/content/github/getting-started-with-github/create-a-repo.md b/translations/de-DE/content/github/getting-started-with-github/create-a-repo.md
index 6360dc45f8..528d4ebfb4 100644
--- a/translations/de-DE/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/de-DE/content/github/getting-started-with-github/create-a-repo.md
@@ -15,6 +15,8 @@ topics:
   - Accounts
 ---
 
+### Ein Repository erstellen
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 Sie können die unterschiedlichsten Projekte in {% data variables.product.product_name %}-Repositorys speichern, darunter auch Open-Source-Projekte. Mit [Open-Source-Projekten](http://opensource.org/about) kannst Du Code leichter für andere zugänglich machen, um eine bessere, zuverlässigere Software zu entwickeln.
@@ -29,7 +31,7 @@ You can store a variety of projects in {% data variables.product.product_name %}
 
 {% note %}
 
-**Hinweis:** Du kannst öffentliche Repositorys für ein Open-Source-Projekt erstellen. Wenn Du ein öffentliches Repository erstellst, musst du unbedingt eine [Lizenzdatei](http://choosealicense.com/) hinzufügen, die bestimmt, wie Dein Projekt für andere Personen freigegeben wird. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
+**Hinweis:** Du kannst öffentliche Repositorys für ein Open-Source-Projekt erstellen. Wenn Du ein öffentliches Repository erstellst, musst du unbedingt eine [Lizenzdatei](https://choosealicense.com/) hinzufügen, die bestimmt, wie Dein Projekt für andere Personen freigegeben wird. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/de-DE/content/github/getting-started-with-github/following-people.md b/translations/de-DE/content/github/getting-started-with-github/following-people.md
index f9f1900722..60232bd991 100644
--- a/translations/de-DE/content/github/getting-started-with-github/following-people.md
+++ b/translations/de-DE/content/github/getting-started-with-github/following-people.md
@@ -1,6 +1,6 @@
 ---
 title: Personen folgen
-intro: 'You can follow people on {% data variables.product.product_name %} to receive notifications about their activity{% if currentVersion == "free-pro-team@latest" %} and discover projects in their communities{% endif %}.'
+intro: 'Sie können Personen auf {% data variables.product.product_name %} folgen, um Benachrichtigungen über ihre Aktivitäten zu erhalten{% if currentVersion == "free-pro-team@latest" %} und Projekte in ihren Communitys zu entdecken{% endif %}.'
 redirect_from:
   - /articles/following-people
 versions:
@@ -11,7 +11,7 @@ topics:
   - Profile
 ---
 
-When you follow people, you'll see their public activity in the activity view of your news feed.{% if currentVersion == "free-pro-team@latest" %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you in the discovery view of your news feed.{% endif %} To follow someone, visit their profile page and click **Follow** under their profile image.
+Wenn Du Personen folgst, siehst Du deren öffentliche Aktivitäten in der Aktivitätsansicht Deines News-Feeds.{% if currentVersion == "free-pro-team@latest" %} Wenn jemand, dem Du folgst, ein öffentliches Repository mit einem Stern markiert, empfiehlt Dir {% data variables.product.product_name %} möglicherweise dieses Repository in der Entdecken-Ansicht Deines Newsfeed.{% endif %} Um einem Benutzer zu folgen, rufe seine Profilseite auf und klicke unter dem Profilbild auf **Follow** (Folgen).
 
 ![Schaltfläche „Follow user" (Benutzer folgen)](/assets/images/help/profile/follow-user-button.png)
 
diff --git a/translations/de-DE/content/github/getting-started-with-github/fork-a-repo.md b/translations/de-DE/content/github/getting-started-with-github/fork-a-repo.md
index 121d8f3153..3e3d253fb2 100644
--- a/translations/de-DE/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/de-DE/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### Informationen zu Forks
+
 Üblicherweise werden Forks genutzt, um Änderungen für ein Projekt eines anderes Benutzers vorzuschlagen oder ein Projekt eines anderen Benutzers als Ausgangspunkt für eigene Ideen zu verwenden.
 
 #### Änderungen für ein Projekt eines anderen Benutzers vorschlagen
@@ -34,7 +36,7 @@ For more information about applying open source principles to your organization'
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-Wenn Du ein öffentliches Repository von einem Fork eines Projekts eines anderen Benutzers erstellst, musst Du unbedingt eine Lizenzdatei hinzufügen, die bestimmt, wie Dein Projekt für andere Personen freigegeben wird. For more information, see "[Choose an open source license](http://choosealicense.com/)" at choosealicense.com.
+Wenn Du ein öffentliches Repository von einem Fork eines Projekts eines anderen Benutzers erstellst, musst Du unbedingt eine Lizenzdatei hinzufügen, die bestimmt, wie Dein Projekt für andere Personen freigegeben wird. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com.
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
@@ -144,7 +146,7 @@ Du kannst nun jede Änderung am Fork vornehmen, einschließlich:
 
 Forken Sie ein Repository, um an einem Projekt mitzuarbeiten. {% data reusables.repositories.you-can-fork %}
 
-{% if currentVersion == "free-pro-team@latest" %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. Weitere Informationen findest du unter „[Möglichkeiten finden, Beiträge an Open-Source auf {% data variables.product.prodname_dotcom %} zu leisten](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
+{% if currentVersion == "free-pro-team@latest" %}Sie können [Explore](https://github.com/explore) durchsuchen, um Projekte zu finden und an Open-Source-Repositorys mitzuarbeiten. Weitere Informationen findest du unter „[Möglichkeiten finden, Beiträge an Open-Source auf {% data variables.product.prodname_dotcom %} zu leisten](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
 
 {% endif %}
 
@@ -154,5 +156,6 @@ Sie haben jetzt ein Repository geforkt, das Klonen Ihres Forks geübt und ein vo
 
 - „[Git einrichten](/articles/set-up-git)“
 - „[Repository erstellen](/articles/create-a-repo)“
+- **Ein Repository forken**
 - „[Soziale Interaktion](/articles/be-social)“
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/de-DE/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/de-DE/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index cd88d0cec3..3bd8d30dbe 100644
--- a/translations/de-DE/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/de-DE/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 Diese Befehle sind bei der Interaktion mit einem [Remote-Repository](/github/getting-started-with-github/about-remote-repositories) sehr hilfreich. Mit `clone` und `fetch` kannst Du Remote-Code von der Remote-URL eines Repositorys auf Deinen lokalen Computer herunterladen. Der Befehl `merge` dient zum Zusammenführen der Arbeit verschiedener Benutzer mit Deiner eigenen Arbeit, und `pull` ist eine Kombination aus `fetch` und `merge`.
 
 ### Ein Repository klonen
diff --git a/translations/de-DE/content/github/getting-started-with-github/git-workflows.md b/translations/de-DE/content/github/getting-started-with-github/git-workflows.md
index f8165892b8..77bc50d780 100644
--- a/translations/de-DE/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/de-DE/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-Du kannst die {% data variables.product.prodname_dotcom %}-Flow-Methode übernehmen, um zu standardisieren, wie Dein Team auf {% data variables.product.prodname_dotcom %} zusammenarbeitet. Weitere Informationen findest Du unter „[GitHub-Flow](/github/collaborating-with-issues-and-pull-requests/github-flow)" und „[GitHub-Flow verstehen](http://guides.github.com/overviews/flow/)" in den {% data variables.product.prodname_dotcom %}-Anleitungen.
+Du kannst die {% data variables.product.prodname_dotcom %}-Flow-Methode übernehmen, um zu standardisieren, wie Dein Team auf {% data variables.product.prodname_dotcom %} zusammenarbeitet. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/de-DE/content/github/getting-started-with-github/github-flow.md b/translations/de-DE/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..863658f7ec
--- /dev/null
+++ b/translations/de-DE/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: GitHub-Flow
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### Einführung
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### Vorrausetzungen
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. Weitere Informationen findest Du unter „[Branches in Deinem Repository erstellen und löschen](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository).“
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### Create a pull request
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. Weitere Informationen findest Du unter „[Einen Pull Request erstellen](/articles/creating-a-pull-request).“
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. Weitere Informationen findest Du unter „[Über Statuschecks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. Dein Pull Request wird automatisch aktualisiert werden.
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. Weitere Informationen findest Du unter „[Einen Pull Request zusammenführen](/articles/merging-a-pull-request).“
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. For more information, see "[Addressing merge conflicts](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)."
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).“
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md b/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md
index 711df249a3..608a96d53a 100644
--- a/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/de-DE/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ You can be simultaneously signed into mobile with one user account on {% data va
 
 You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}.
 
-To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
+To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}.
 
diff --git a/translations/de-DE/content/github/getting-started-with-github/github-language-support.md b/translations/de-DE/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/de-DE/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/de-DE/content/github/getting-started-with-github/githubs-products.md b/translations/de-DE/content/github/getting-started-with-github/githubs-products.md
index bd068fc761..c4c3911a37 100644
--- a/translations/de-DE/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/de-DE/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 {% data variables.product.prodname_dotcom %} bietet kostenlose und kostenpflichtige Produkte an. Die Preise und eine vollständige Liste der Features für jedes Produkt findest Du unter {% data variables.product.pricing_url %}. {% data reusables.products.product-roadmap %}
 
 ### {% data variables.product.prodname_free_user %} für Benutzerkonten
@@ -99,14 +101,3 @@ Zusätzlich zu den mit {% data variables.product.prodname_team %} verfügbaren F
 Du kannst eine Testversion einrichten, um {% data variables.product.prodname_ghe_cloud %} zu testen. Weitere Informationen findest Du unter „<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">Eine Testversion von {% data variables.product.prodname_ghe_cloud %} einrichten</a>.“
 
 Um weitere Informationen über das Hosten Deiner eigenen [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com)-Instanz zu erhalten, kontaktiere bitte {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-{% data variables.product.prodname_ghe_one %} enthält [{% data variables.product.prodname_enterprise %}](#github-enterprise) sowie:
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %}
-- [{% data variables.product.prodname_learning %} für Organisationen](https://lab.github.com/organizations)
-
-For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/content/github/getting-started-with-github/index.md b/translations/de-DE/content/github/getting-started-with-github/index.md
index 61fb13fb07..0812b17e14 100644
--- a/translations/de-DE/content/github/getting-started-with-github/index.md
+++ b/translations/de-DE/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/de-DE/content/github/getting-started-with-github/learning-about-github.md b/translations/de-DE/content/github/getting-started-with-github/learning-about-github.md
index 64da022da9..16dbae7890 100644
--- a/translations/de-DE/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/de-DE/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: Informationen zu GitHub
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/de-DE/content/github/getting-started-with-github/set-up-git.md b/translations/de-DE/content/github/getting-started-with-github/set-up-git.md
index 73ff092c6c..9102f996df 100644
--- a/translations/de-DE/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/de-DE/content/github/getting-started-with-github/set-up-git.md
@@ -22,6 +22,8 @@ topics:
   - Accounts
 ---
 
+### Git verwenden
+
 Um Git in der Befehlszeile verwenden zu können, musst Du es auf Deinem Computer herunterladen und dort installieren und konfigurieren. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. For more information on {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation.{% endif %}
 
 Möchtest Du Git lokal, aber ohne Befehlszeile verwenden, kannst Du stattdessen den [{% data variables.product.prodname_desktop %}-Client]({% data variables.product.desktop_link %}) herunterladen und installieren.  For more information, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)."
diff --git a/translations/de-DE/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/de-DE/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 67c6f4c366..1e5b7948c5 100644
--- a/translations/de-DE/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/de-DE/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ Wenn Du {% data variables.product.prodname_enterprise %} oder {% data variables.
 
 Das Herunterstufen auf {% data variables.product.prodname_free_team %} für Organisationen deaktiviert auch alle SAML-Einstellungen, die während der Testperiode konfiguriert wurden. Sobald Sie {% data variables.product.prodname_enterprise %} oder {% data variables.product.prodname_team %} erwerben, werden Ihre SAML-Einstellungen wieder für die Benutzer in Ihrer Organisation zur Authentifizierung aktiviert.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Klicke unter „{% data variables.product.prodname_ghe_cloud %} Free Trial“ (Kostenlose Testversion) auf **Buy Enterprise** (Enterprise kaufen) oder **Downgrade to Team** (Herunterstufen auf Team). ![Schaltfläche „Buy Enterprise“ (Enterprise kaufen) oder „Downgrade to Team“ (Herunterstufen auf Team)](/assets/images/help/organizations/finish-trial-buttons.png)
 6. Befolge die Anweisungen zur Eingabe Deiner Zahlungsmethode, und klicke dann auf **Submit** (Absenden).
 
diff --git a/translations/de-DE/content/github/getting-started-with-github/types-of-github-accounts.md b/translations/de-DE/content/github/getting-started-with-github/types-of-github-accounts.md
index 3890a37576..3c941c1716 100644
--- a/translations/de-DE/content/github/getting-started-with-github/types-of-github-accounts.md
+++ b/translations/de-DE/content/github/getting-started-with-github/types-of-github-accounts.md
@@ -1,6 +1,6 @@
 ---
 title: Arten von GitHub-Konten
-intro: 'Ihr Benutzerkonto ist Ihre Identität auf {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% if currentVersion == "free-pro-team@latest" %} Organizations can belong to enterprise accounts.{% endif %}'
+intro: 'Ihr Benutzerkonto ist Ihre Identität auf {% data variables.product.product_location %}. Dein Benutzerkonto kann Mitglied einer beliebigen Anzahl von Organisationen sein.{% if currentVersion == "free-pro-team@latest" %} Organisationen können zu Enterprise-Konten gehören.{% endif %}'
 redirect_from:
   - /manage-multiple-clients/
   - /managing-clients/
@@ -79,6 +79,6 @@ Mit Enterprise-Konten können Sie die Richtlinien und Abrechnungen mehrerer {% d
 
 ### Weiterführende Informationen
 
-{% if currentVersion == "free-pro-team@latest" %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"
+{% if currentVersion == "free-pro-team@latest" %}- „[Für ein neues {% data variables.product.prodname_dotcom %}-Konto anmelden](/articles/signing-up-for-a-new-github-account)“
 - „[Produkte von {% data variables.product.prodname_dotcom %}](/articles/githubs-products)"{% endif %}
 - „[Neues Organisationskonto erstellen](/articles/creating-a-new-organization-account)“
diff --git a/translations/de-DE/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/de-DE/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index e027137cb6..1a348f8c62 100644
--- a/translations/de-DE/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/de-DE/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 In diesem Beispiel werden mit Ausnahme von `exec` alle verfügbaren `git rebase`-Befehle vorgestellt.
 
 Wir geben zunächst am Terminal `git rebase --interactive HEAD~7` ein, um den Rebase-Vorgang zu starten. Unser bevorzugter Texteditor zeigt die folgenden Zeilen an:
diff --git a/translations/de-DE/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/de-DE/content/github/importing-your-projects-to-github/about-github-importer.md
index ab6ae87def..6e5964c8db 100644
--- a/translations/de-DE/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/de-DE/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: Informationen zu GitHub Importer
-intro: 'Wenn Du Quellcode in Subversion, Mercurial, Team Foundation Server oder einem anderen Git-Repository hast, kannst Du ihn mit dem GitHub Importer nach GitHub verschieben.'
+intro: 'If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer.'
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ GitHub Importer ist ein Tool, das Quellcode-Repositorys, einschließlich Commits
 
 Während eines Imports kannst Du je nach dem Versionskontrollsystem, aus dem Du importierst, mit Deinem Remote-Repository authentifizieren, die Zuordnung von Commit-Autoren aktualisieren und Repositorys mit großen Dateien importieren (oder große Dateien entfernen, wenn du Git Large File Storage (Git Große Dateien Speicher) nicht verwenden möchtest).
 
-| Importaktion                                                                                                    | Subversion | Mercurial | Team Foundation Server |  Git  |
-|:--------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:|
-| Mit Remote-Repository authentifizieren                                                                          |   **X**    |   **X**   |         **X**          | **X** |
-| [Zuordnung von Commit-Autoren aktualisieren](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   |         **X**          |       |
-| Große Dateien in [Git Large File Storage](/articles/about-git-large-file-storage) verschieben                   |   **X**    |   **X**   |         **X**          |       |
-| Große Dateien aus Deinem Repository entfernen                                                                   |   **X**    |   **X**   |         **X**          |       |
+| Importaktion                                                                                                    | Subversion | Mercurial | TFVC  |  Git  |
+|:--------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:-----:|:-----:|
+| Mit Remote-Repository authentifizieren                                                                          |   **X**    |   **X**   | **X** | **X** |
+| [Zuordnung von Commit-Autoren aktualisieren](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   | **X** |       |
+| Große Dateien in [Git Large File Storage](/articles/about-git-large-file-storage) verschieben                   |   **X**    |   **X**   | **X** |       |
+| Große Dateien aus Deinem Repository entfernen                                                                   |   **X**    |   **X**   | **X** |       |
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/de-DE/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index 4ce5c3653e..1b33255cac 100644
--- a/translations/de-DE/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/de-DE/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-Wir empfehlen [GitHub Importer](/articles/about-github-importer) für den Import von Projekten aus Subversion, Mercurial, Team Foundation Server oder einem anderen Git-Repository. Auch diese externen Werkzeuge können für die Konvertierung Deines Projekts für Git verwendet werden.
+We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. Auch diese externen Werkzeuge können für die Konvertierung Deines Projekts für Git verwendet werden.
 
 {% endif %}
 
@@ -32,12 +32,9 @@ Für die Konvertierung von Subversion-Repositorys nach Git empfehlen wir folgend
 
 Für die Konvertierung von Mercurial-Repositorys in Git empfehlen wir [hg-fast-export](https://github.com/frej/fast-export).
 
-### Import aus Team Foundation Server
+### Importing from TFVC
 
-Für die Verschiebung von Änderungen zwischen Team Foundation Server und Git empfehlen wir folgende Werkzeuge:
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
 
 {% tip %}
 
diff --git a/translations/de-DE/content/github/index.md b/translations/de-DE/content/github/index.md
index 4ede7bb06a..cb2d8d58de 100644
--- a/translations/de-DE/content/github/index.md
+++ b/translations/de-DE/content/github/index.md
@@ -36,7 +36,6 @@ versions:
 {% link_in_list /collaborating-with-issues-and-pull-requests %}
 
 {% link_in_list /managing-your-work-on-github %}
-{% link_in_list /developing-online-with-codespaces %}
 
 {% link_in_list /searching-for-information-on-github %}
 
@@ -57,7 +56,6 @@ versions:
 
 {% link_in_list /extending-github %}
 
-{% link_in_list /supporting-the-open-source-community-with-github-sponsors %}
 {% link_in_list /finding-talent-with-github-jobs %}
 {% link_in_list /working-with-github-support %}
 {% link_in_list /understanding-how-github-uses-and-protects-your-data %}
diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
index 9e0233989f..a893e0c50f 100644
--- a/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
+++ b/translations/de-DE/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
@@ -26,7 +26,7 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_
 
 1. Navigiere zu der Datei in Deinem Repository, die Du löschen möchtest.
 2. At the top of the file, click
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index 82e61c24d2..a3d7847427 100644
--- a/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/de-DE/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### Über Code-Navigation auf {% data variables.product.prodname_dotcom %}
 
 Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). Die folgenden Sprachen werden unterstützt:
diff --git a/translations/de-DE/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/de-DE/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index 262b7fa986..15b21dfaa5 100644
--- a/translations/de-DE/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/de-DE/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -36,9 +36,9 @@ versions:
 
 ### {% data variables.large_files.product_name_short %}-Objekte in Ihrem Repository
 
-After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}.
+Die {% data variables.large_files.product_name_short %}-Objekte von Dateien, die Du aus {% data variables.large_files.product_name_short %} entfernt hast, sind nach wie vor im Remote-Speicher vorhanden{% if currentVersion == "free-pro-team@latest" %} und werden Deinem {% data variables.large_files.product_name_short %}-Speicher-Kontingent weiterhin angerechnet{% endif %}.
 
-To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. Wenn Du ein Repository löschst, werden alle zugehörigen Issues, Sterne und Forks ebenfalls gelöscht. Weitere Informationen findest Du unter "[Löschen eines Repositories](/github/administering-a-repository/deleting-a-repository)."{% else %}kontaktiere Deinen {% data variables.product.prodname_enterprise %}-Administrator, um die Objekte zu archivieren. Archivierte Objekte werden nach drei Monaten gelöscht.{% endif %}
+Um {% data variables.large_files.product_name_short %}-Objekte aus einem Repository zu entfernen, {% if currentVersion == "free-pro-team@latest" %}lösche und erstelle das Repository erneut. Wenn Du ein Repository löschst, werden alle zugehörigen Issues, Sterne und Forks ebenfalls gelöscht. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archivierte Objekte werden nach drei Monaten gelöscht.{% endif %}
 
 {% note %}
 
diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index 1a70b0e7bf..c8b4888466 100644
--- a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,12 +1,14 @@
 ---
 title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
+intro: '{% data variables.product.product_name %} sends {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
 versions:
   enterprise-server: <=2.22
 topics:
   - Security
 ---
- 
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
 ### About vulnerable dependencies
 
 {% data reusables.repositories.a-vulnerability-is %}
@@ -15,12 +17,10 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 ### Detection of vulnerable dependencies
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
 
-{% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
+- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
 {% data reusables.repositories.dependency-review %}
 
@@ -32,7 +32,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
 ### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
 {% else %}
 ### Sicherheitsmeldungen für angreifbare Abhängigkeiten
@@ -40,25 +40,11 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% 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.
-
-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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
-
-{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 When
 {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-For repositories where
-{% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 When
 {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
@@ -70,30 +56,17 @@ When
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Access to {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+You can see all of the alerts that affect a particular project in the repository's dependency graph.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 By default, we notify people with admin permissions in the affected repositories about new
-{% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
-{% endif %}
+{% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 Standardmäßig senden wir Sicherheitsmeldungen an Personen mit Administratorrechten in den betroffenen Repositorys.
 {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-You can also see all the
-{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Weiterführende Informationen
-
-- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- „[Angreifbare Abhängigkeiten in Deinem Repository anzeigen und aktualisieren](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)“
-- „[Grundlegendes zur Verwendung und zum Schutz Deiner Daten in {% data variables.product.product_name %}](/categories/understanding-how-github-uses-and-protects-your-data)“{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index eb790b5886..59c9d86b4b 100644
--- a/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/de-DE/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,20 +1,18 @@
 ---
 title: Configuring notifications for vulnerable dependencies
 shortTitle: Benachrichtigungen konfigurieren
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+intro: 'Optimize how you receive notifications about  {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
 versions:
   enterprise-server: '>=2.21 <=2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies for the current version of this article -->
+
 ### About notifications for vulnerable dependencies
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
 Your site administrator needs to enable security alerts for vulnerable dependencies for
@@ -28,14 +26,14 @@ By default, if your site administrator has configured email for notifications on
 
 {% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configuring notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
 
 You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 {% else %}
   ![Optionen für Sicherheitswarnungen](/assets/images/help/notifications-v2/security-alerts-options.png)
@@ -47,11 +45,11 @@ You can configure notification settings for yourself or your organization from t
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications).“
 
 ### How to reduce the noise from notifications for vulnerable dependencies
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+If you are concerned about receiving too many notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/index.md b/translations/de-DE/content/github/managing-security-vulnerabilities/index.md
index 5869923767..63fa30727e 100644
--- a/translations/de-DE/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/de-DE/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### Inhaltsverzeichnis
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index 11db0fb323..fa925ab0b9 100644
--- a/translations/de-DE/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/de-DE/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index f199159aa6..3984a8bf0f 100644
--- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -26,13 +26,9 @@ topics:
 Du kannst Benachrichtigungen abonnieren für:
 - Eine Unterhaltung in einem spezifischen Issue, Pull Request oder Gist.
 - Alle Aktivitäten in einem Repository oder in einer Team-Diskussion.
-- CI-Aktivität wie beispielsweise der Status von Workflows in Repositorys, die mit {% data variables.product.prodname_actions %} aufgesetzt wurden.
-{% if currentVersion == "free-pro-team@latest" %}
-- Issues, pulls requests, releases and discussions (if enabled) in a repository.
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- Releases in einem Repository.
-{% endif %}
+- CI-Aktivität wie beispielsweise der Status von Workflows in Repositorys, die mit {% data variables.product.prodname_actions %} aufgesetzt wurden. {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 Du kannst auch automatisch alle Repositorys überwachen, auf die Du Push-Zugriff hast, mit Ausnahme von Forks. Du kannst jedes andere Repository, auf das Du Zugriff hast, manuell verfolgen durch klicken auf **Watch** (Beobachten).
 
diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
index 7571773f1e..be95693679 100644
--- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
+++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
@@ -58,7 +58,7 @@ In addition, you can receive and triage notifications on your mobile device with
 
 #### Vorteile beim Benutzen eines E-Mail-Client für Benachrichtigungen
 
-Ein Vorteil der Verwendung eines E-Mail-Clients ist, dass alle Deine Benachrichtigungen unbegrenzt aufbewahrt werden können, abhängig von der Speicherkapazität Deines E-Mail-Clients. In Deinem Posteingang für Benachrichtigungen hingegen werden Benachrichtigungen nur für 5 Monate aufbewahrt, außer wenn du sie mit **Saved** (Gesichert) markiert hast. Mit **Saved** (Gesichert) markierte Benachrichtigungen werden unbegrenzt gespeichert. Weitere Informationen zur Aufbewahrungsrichtlinie Deines Posteingangs findest Du unter „[Über Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
+Ein Vorteil der Verwendung eines E-Mail-Clients ist, dass alle Deine Benachrichtigungen unbegrenzt aufbewahrt werden können, abhängig von der Speicherkapazität Deines E-Mail-Clients. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. Mit **Saved** (Gesichert) markierte Benachrichtigungen werden unbegrenzt gespeichert. Weitere Informationen zur Aufbewahrungsrichtlinie Deines Posteingangs findest Du unter „[Über Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
 
 Benachrichtigungen an Deinen E-Mail-Client zu senden erlaubt Dir auch, Deinen Posteingang mit allen Einstellungen deines E-Mail-Clients anzupassen, welche allenfalls benutzerdefinierte oder farbcodierte Kennzeichnungen beinhalten.
 
@@ -69,15 +69,16 @@ E-Mail-Benachrichtigungen ermöglichen auch Flexibilität bei der Art von Benach
 Wenn Du ein Repository beobachtest, abonnierst Du Aktualisierungen für Aktivitäten in diesem Repository. Ebenfalls, wenn Du die Diskussionen eines bestimmten Teams verfolgst, abonnierst Du alle Aktualisierungen der Unterhaltung auf der Seite dieses Teams. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“.
 
 To see repositories that you're watching, go to your [watching page](https://github.com/watching). Weitere Informationen findest Du unter „[Abonnements und Benachrichtigungen auf GitHub verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
 #### Benachrichtigungen konfigurieren
 {% endif %}
 You can configure notifications for a repository on the repository page, or on your watching page.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 #### About custom notifications
-{% data reusables.notifications-v2.custom-notifications-beta %}
-You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository.
+You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events (
+{% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository.
 {% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
 
 #### Participating in conversations
@@ -131,7 +132,7 @@ E-Mail-Benachrichtigungen von {% data variables.product.product_name %} enthalte
 
 | Header                   | Informationen                                                                                                                                                                                                                                                                                                                                                                  |
 | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `From`-Adresse           | This address will always be {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}.                                                                                                                                                                              |
+| `From`-Adresse           | Diese Adresse entspricht immer {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'der von Deinem Websiteadministrator konfigurierten no-reply-E-Mail-Adresse'{% endif %}.                                                                                                                                                                 |
 | `To`-Feld                | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %}
 | `Cc`-Adresse             | {% data variables.product.product_name %} fügt Sie zu `Cc` hinzu, wenn Sie eine Unterhaltung abonniert haben. Die zweite E-Mail-Adresse in `Cc` entspricht dem Benachrichtigungsgrund. Das Suffix für diese Benachrichtigungsgründe lautet {% data variables.notifications.cc_address %}. Zu den möglichen Benachrichtigungsgründen gehören folgende: <ul><li>`assign`: Dir wurde ein Issue oder Pull Request zugewiesen.</li><li>`author`: Du hast einen Issue oder Pull Request erstellt.</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}<li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li>{% endif %}<li>`comment`: Du hast einen Issue oder Pull Request kommentiert.</li><li>`manual`: Ein Issue oder Pull Request, den Du manuell abonniert hast, wurde aktualisiert.</li><li>`mention`: Du wurdest in einem Issue oder Pull Request erwähnt.</li><li>`push`: Jemand hat einen Commit für einen Pull Request erstellt, den Du abonniert hast.</li><li>`review_requested`: Du oder ein Team, dem Du angehörst, wurdest/wurde gebeten, einen Review für einen Pull Request durchzuführen.</li>{% if currentVersion != "github-ae@latest" %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} hat eine Schwachstelle in einem Repository erkannt, für das Du Sicherheitswarnungen erhältst.</li>{% endif %}<li>`state_change`: Ein Issue oder Pull Request, den Du abonniert hast, wurde entweder geschlossen oder geöffnet.</li><li>`subscribed`: Es gab eine Aktualisierung in einem Repository, das Du beobachtest.</li><li>`team_mention`: Ein Team, dem Du angehörst, wurde in einem Issue oder Pull Request erwähnt.</li><li>`your_activity`: Du hast einen Issue oder Pull Request geöffnet, kommentiert oder geschlossen.</li></ul> |
 | `mailing list`-Feld      | In diesem Feld werden der Name des Repositorys und sein Inhaber identifiziert. Das Format dieser Adresse lautet immer `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
@@ -159,19 +160,22 @@ Wenn "Automatisch Repositories beobachten" deaktiviert ist, wirst Du auch nicht
 
 ### Konfiguration der Beobachtungseinstellungen für ein einzelnes Repository
 
-Du kannst wählen, ob Du ein einzelnes Repository ansehen möchtest oder nicht mehr. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
+Du kannst wählen, ob Du ein einzelnes Repository ansehen möchtest oder nicht mehr. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 2. Klicke in der oberen rechten Ecke auf das Dropdownmenü „Watch" (Beobachten), um eine der Beobachtungsoptionen zu wählen.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Beobachtungsoptionen in einem Dropdownmenü für ein Repository](/assets/images/help/notifications-v2/watch-repository-options.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
    ![Beobachtungsoptionen in einem Dropdownmenü für ein Repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
-{% data reusables.notifications-v2.custom-notifications-beta %}
+
 The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
 
+{% if currentVersion == "free-pro-team@latest" %}
+   ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png)
+{% else %}
    ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2.png)
+{% endif %}
 
 If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
 
@@ -220,7 +224,7 @@ For more information about the notification delivery methods available to you, a
 
 Wähle, wie Du Aktualisierungen für Workflow-Ausführungen erhalten willst für Repositorys, die Du beobachtest und die mit {% data variables.product.prodname_actions %} aufgesetzt sind. Du kannst auch wählen, nur Benachrichtigungen für fehlgeschlagene Workflow-Ausführungen zu erhalten.
 
-  ![Notification options for GitHub Actions](/assets/images/help/notifications-v2/github-actions-notification-options.png)
+  ![Notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png)
 
 {% endif %}
 
diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index 2e8d68e955..9467249163 100644
--- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -57,13 +57,13 @@ Wenn Du ein Repository nicht mehr beobachtest, meldest Du Dich von zukünftigen
 {% data reusables.notifications.access_notifications %}
 1. Verwende in der linken Seitenleiste, unterhalb der Liste der Repositorys, das Dropdownmenü „Manage Notifications" (Benachrichtigungen verwalten) und klicke auf **Watched repositories** (beobachtete Repositorys). ![Dropdownmenü-Optionen „Manage Notifications" (Benachrichtigungen verwalten)](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Nimm auf der Seite der beobachteten Repositorys eine Bewertung dieser Repositorys vor und wähle dann aus:
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-    - ein Repository nicht mehr beobachten
-    - nur Releases für ein Repository beobachten
-    - ignoriere alle Benachrichtigungen für ein Repository
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-    - ein Repository nicht mehr beobachten
-    - ignoriere alle Benachrichtigungen für ein Repository
-    - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled)
-{% endif %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
+    - Ein Repository nicht mehr beobachten
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    - Ein Repository nicht mehr beobachten
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index 867821edb4..5c92fd119e 100644
--- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -35,10 +35,10 @@ Wenn Dein Posteingang zu viele Benachrichtigungen zum Verwalten hat, überlege D
 Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
 
 Eine Übersicht Deiner Repository-Abonnements findest Du unter „[Repositorys überprüfen, die Du beobachtest](#reviewing-repositories-that-youre-watching).
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
 
 {% endtip %}
 {% endif %}
@@ -67,16 +67,15 @@ Viele Personen vergessen Repositorys, die sie in der Vergangenheit beobachtet ha
 
 1. Verwende in der linken Seitenleiste, unterhalb der Liste der Repositorys, das Dropdownmenü „Manage Notifications" (Benachrichtigungen verwalten) und klicke auf **Watched repositories** (beobachtete Repositorys). ![Dropdownmenü-Optionen „Manage Notifications" (Benachrichtigungen verwalten)](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Evaluiere die von Dir beobachteten Repositorys und entscheide, ob deren Aktualisierungen für Dich immer noch relevant und hilfreich sind. Wenn Du ein Repository beobachtest, wirst Du über alle Unterhaltungen für dieses Repository benachrichtigt.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Seite der beobachteten Benachrichtigungen](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
   ![Seite der beobachteten Benachrichtigungen](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" %}when there are updates to issues, pull requests, releases or discussions (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
 
   Wenn Du ein Repository nicht mehr beobachtest, kannst du immer noch benachrichtigt werden, wenn Du @erwähnt wirst oder in einem Thread teilnimmst. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
 
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index 672be59037..599fe583b3 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ Abfrageparameter sind optionale Bestandteile einer URL, die Sie anpassen können
 
 Du musst die erforderlichen Berechtigungen für jede Aktion haben, um den entsprechenden Abfrageparameter zu verwenden. Beispielsweise benötigst Du die Berechtigung, einem Issue eine Kennzeichnung hinzuzufügen, um den Abfrageparameter `labels` (Kennzeichnung) zu verwenden.
 
-Wenn Du eine ungültige URL mithilfe von Suchparametern erstellst oder wenn Du nicht über die erforderlichen Berechtigungen verfügst, gibt die URL eine 404-Fehlerseite zurück.
+If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page.
 
 ### Unterstützte Abfrageparameter
 
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-project-boards.md b/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-project-boards.md
index 6c709bade8..7646dc47db 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-project-boards.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/about-automation-for-project-boards.md
@@ -38,5 +38,5 @@ You can track the progress on your project board. Cards in the "To do", "In prog
 For more information, see "[Tracking progress on your project board](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)."
 
 ### Weiterführende Informationen
-- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)"{% if currentVersion == "free-pro-team@latest" %}
+- „[Automatisierung für Projektboards konfigurieren](/articles/configuring-automation-for-project-boards)“{% if currentVersion == "free-pro-team@latest" %}
 - „[Ein Projektboard kopieren](/articles/copying-a-project-board)“{% endif %}
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md b/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md
index cd24764880..ea335efb64 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md
@@ -24,7 +24,7 @@ Other conversations are more suitable for discussions. {% data reusables.discuss
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
-Um über die neuesten Kommentare in einem Issue auf dem Laufenden zu bleiben, können Sie einen Issue beobachten, um Benachrichtigungen über die neuesten Kommentare zu erhalten. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
+Um über die neuesten Kommentare in einem Issue auf dem Laufenden zu bleiben, können Sie einen Issue beobachten, um Benachrichtigungen über die neuesten Kommentare zu erhalten. Weitere Informationen findest Du unter {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}„[Über Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}„[Über Benachrichtigungen](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
 
 Um schnell Links zu kürzlich aktualisierten Issues zu finden, besuche Dein Dashboard. Weitere Informationen findest Du unter „[Informationen zum persönlichen Dashboard](/articles/about-your-personal-dashboard).“
 
@@ -36,7 +36,7 @@ Issues ermöglichen Ihnen Folgendes:
 - Erstelle Issue-Vorlagen, um Mitarbeitern zu helfen, aussagekräftige Issues zu erstellen. Weitere Informationen findest Du unter „[Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)“
 - Übertrage offene Issues in andere Repositorys. Weitere Informationen finden Sie unter „[Einen Issue in ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“.
 - Hefte wichtige Issues an, um sie leichter auffindbar zu machen, doppelte Issues zu vermeiden und Störungen zu unterdrücken. Weitere Informationen findest Du unter „[Einen Issue an Dein Repository anheften](/articles/pinning-an-issue-to-your-repository).“
-- Verfolge doppelte Issues anhand gespeicherter Antworten. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %}
+- Verfolge doppelte Issues anhand gespeicherter Antworten. Weitere Informationen findest Du unter „[Informationen zu gespeicherten Antworten](/articles/about-saved-replies)“.{% if currentVersion == "free-pro-team@latest" %}
 - Melden Sie Kommentare, die gegen die [Community-Richtlinien](/articles/github-community-guidelines) von {% data variables.product.prodname_dotcom %} verstoßen. Weitere Informationen findest Du unter „[Missbrauch oder Spam melden](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)“.{% endif %}
 
 Issues können außerdem [anderen Benutzern zugewiesen](/articles/assigning-issues-and-pull-requests-to-other-github-users), [mit Kennzeichnungen für eine schnellere Suche versehen](/articles/applying-labels-to-issues-and-pull-requests) und [mit Meilensteinen gruppiert](/articles/creating-and-editing-milestones-for-issues-and-pull-requests) werden.
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/about-project-boards.md b/translations/de-DE/content/github/managing-your-work-on-github/about-project-boards.md
index 3eda1ead2d..34a4c3ad29 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/about-project-boards.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/about-project-boards.md
@@ -62,7 +62,7 @@ Weitere Informationen zur Automatisierung von Projektboards findest Du unter „
 ### Weiterführende Informationen
 
 - „[Ein Projektboard erstellen](/articles/creating-a-project-board)“
-- "[Editing a project board](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %}
+- „[Ein Projektboard bearbeiten](/articles/editing-a-project-board)“{% if currentVersion == "free-pro-team@latest" %}
 - „[Ein Projektboard kopieren](/articles/copying-a-project-board)“{% endif %}
 - „[Issues und Pull Requests zu einem Projektboard hinzufügen](/articles/adding-issues-and-pull-requests-to-a-project-board)“
 - „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md b/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md
index 8f3a449c00..6dd4158bad 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/creating-a-project-board.md
@@ -87,7 +87,7 @@ Du kannst auch Workflows automatisieren, um Dein Projektboard mit dem Status der
 ### Weiterführende Informationen
 
 - „[Informationen zu Projektboards](/articles/about-project-boards)“
-- "[Editing a project board](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %}
+- „[Ein Projektboard bearbeiten](/articles/editing-a-project-board)“{% if currentVersion == "free-pro-team@latest" %}
 - „[Ein Projektboard kopieren](/articles/copying-a-project-board)“{% endif %}
 - „[Ein Projektboard schließen](/articles/closing-a-project-board)“
 - „[Informationen zur Automatisierung für Projektboards](/articles/about-automation-for-project-boards)“
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index 4da20f55f6..eb0d43f890 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. Wähle eine der folgenden Optionen aus:
     - Um einen neuen Meilenstein zu erstellen, klicke auf **New Milestone** (Neuer Meilenstein). ![Schaltfläche „New milestone“ (Neuer Meilenstein)](/assets/images/help/repository/new-milestone.png)
     - Um einen Meilenstein zu bearbeiten, klicke neben dem Meilenstein, den Du bearbeiten möchtest, auf **Edit** (Bearbeiten). ![Option „Edit“ (Bearbeiten) zum Bearbeiten des Meilensteins](/assets/images/help/repository/edit-milestone.png)
-5. Gib einen Titel und eine Beschreibung für den Meilenstein oder sonstige Änderungen ein, und klicke dann auf **Create milestone** (Meilenstein erstellen) oder **Save changes** (Änderungen speichern).
+5. Gib einen Titel und eine Beschreibung für den Meilenstein oder sonstige Änderungen ein, und klicke dann auf **Create milestone** (Meilenstein erstellen) oder **Save changes** (Änderungen speichern). Milestones will render Markdown syntax. For more information about Markdown syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
 
 ### Meilensteine löschen
 
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/de-DE/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index 93f2142085..9b12b52dfe 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ Wenn Du Repository-Projektboards in einer Organisation deaktiviert hast, kannst
 
 Wenn Du Projektboards deaktivierst, kannst du keine Projektboard-Informationen mehr in Zeitleisten oder [Auditprotokollen](/articles/reviewing-the-audit-log-for-your-organization/) sehen.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Lege fest, ob Du organisationsweite Projektboards oder Repository-Projektboards in der Organisation oder beide Optionen deaktivieren möchtest. Führe anschließend unter „Projects“ (Projekte) Folgendes aus:
     - Um organisationsweite Projektboards zu deaktivieren, deaktiviere die Auswahl von **Enable projects for the organization** (Projekte für die Organisation aktivieren).
     - Um Repository-Projektboards in der Organisation zu deaktivieren, deaktiviere die Auswahl von **Enable projects for all repositories** (Projekte für alle Repositorys aktivieren) auf. ![Kontrollkästchen, um Projekte für eine Organisation oder für alle Repositorys einer Organisation zu deaktivieren](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index bd5992408a..21ee73808b 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: Dateianhänge für Issues und Pull Requests
-intro: 'Wenn Du einen Issue öffnest oder einen Pull Request aktualisierst, kannst Du mithilfe von Issue-Anhängen Bilder von vorgeschlagenen Funktionen oder Screenshots von Fehlern hochladen.'
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -14,7 +14,7 @@ topics:
 
 {% warning %}
 
-**Warnung:** Wenn Du ein Bild zu einem Pull-Request- oder Issue-Kommentar hinzufügst, kann jeder die anonymisierte Bild-URL ohne Authentifizierung anzeigen, selbst wenn sich der Pull Request in einem privaten Repository befindet{% if enterpriseServerVersions contains currentVersion %} oder der private Modus aktiviert ist{% endif %}. Um vertraulicher Bilder zu schützen, stelle sie über ein privates Netzwerk oder einen Server bereit, der eine Authentifizierung vorschreibt. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized image URLs](/articles/about-anonymized-image-urls)".{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ Um eine Datei an eine Issue- oder eine Pull-Request-Unterhaltung anzuhängen, zi
 
 {% endtip %}
 
-Die Größe der Anhänge ist bei Dateien auf 25 MB und bei Bildern auf 10 MB beschränkt.
-{% if currentVersion == "free-pro-team@latest" %}
-Videos can be up to 100 MB in size if the repository is owned by a user or organization on a paid GitHub plan.
-
-{% note %}
-
-**Note:** Support for video attachments is currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 Wir unterstützen die folgenden Dateiformate:
 
@@ -49,7 +43,7 @@ Wir unterstützen die folgenden Dateiformate:
 * Microsoft Word-Dokumente (*.docx*), Powerpoint-Dokumente (*.pptx*) und Excel-Dokumente (*.xlsx*)
 * Textdateien (*.txt*)
 * PDF-Dateien (*.pdf*)
-* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" %}
+* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * Video (*.mp4*, *.mov*){% endif %}
 
 ![Animiertes GIF zu Anhängen](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md b/translations/de-DE/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md
index 40f75798bb..d773793615 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/filtering-cards-on-a-project-board.md
@@ -24,7 +24,7 @@ Du kannst Tickets auch über die Suchleiste „Filter cards“ (Tickets filtern)
 - Tickets nach Prüfstatus filtern – mit `status:pending`, `status:success` oder `status:failure`
 - Tickets nach Typ filtern – mit `type:issue`, `type:pr` oder `type:note`
 - Tickets nach Status und Typ filtern – mit `is:open`, `is:closed` oder `is:merged` und `is:issue`, `is:pr` oder `is:note`
-- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- Tickets nach Issues filtern, die mit einer abschließenden Referenz zu einem Pull Request verbunden sind – mit `linked:pr`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
 - Tickets nach Repository in einem organisationsweiten Projektboard filtern – mit `repo:ORGANIZATION/REPOSITORY`{% endif %}
 
 1. Navigiere zu dem Projektboard, das die Tickets enthält, nach denen Du filtern möchtest.
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/de-DE/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md
index 2512d62533..91062d9ca3 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md
@@ -22,9 +22,9 @@ topics:
 
 ### Über verknüpfte Issues und Pull Requests
 
-You can link an issue to a pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}manually or {% endif %}using a supported keyword in the pull request description.
+Du kannst einen Issue mit einem Pull-Request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}manuell oder {% endif %}mit einem unterstützten Schlüsselwort in der Pull-Request Beschreibung verknüpfen.
 
-Wenn Du einen Pull Request mit dem Issue verknüpfst, der vom Pull Request adressiert wird, dann können Mitarbeiter sehen, dass jemand am Issue arbeitet. {% if currentVersion ver_lt "enterprise-server@2.21" %}If the pull request and the issue are in different repositories, {% data variables.product.product_name %} will display the link after the pull request is merged, if the person who merges the pull request also has permission to close the issue.{% endif %}
+Wenn Du einen Pull Request mit dem Issue verknüpfst, der vom Pull Request adressiert wird, dann können Mitarbeiter sehen, dass jemand am Issue arbeitet. {% if currentVersion ver_lt "enterprise-server@2.21" %}Wenn der Pull Request und der Issue in unterschiedlichen Repositorys sind, wird {% data variables.product.product_name %} nach dem Zusammenführen des Pull Request den Link anzeigen, wenn die Person, die den Pull Request zusammenführt, auch die Berechtigung zum Schließen des Issue hat.{% endif %}
 
 Wenn Du einen verknüpften Pull Request in den Standard-Branch eines Repository zusammenführst, werden seine verknüpften Issues automatisch geschlossen. For more information about the default branch, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
 
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md b/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md
index 7445561ac7..b6e7da34d1 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/managing-labels.md
@@ -35,20 +35,22 @@ Alle Benutzer mit Lesezugriff auf ein Repository können die Kennzeichnungen des
 
 {% data variables.product.product_name %} bietet in jedem neuen Repository Standardkennzeichnungen. Mithilfe dieser Standardkennzeichnungen kannst Du einen Standardworkflow in einem Repository erstellen.
 
-| Kennzeichnung      | Beschreibung                                                                                                                                              |
-| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `bug`              | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}
+| Kennzeichnung      | Beschreibung                                                                                                                                                             |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `bug`              | Kennzeichnet ein unerwartetes Problem oder unbeabsichtigtes Verhalten{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}
 | `documentation`    | Kennzeichnet die Notwendigkeit für Verbesserungen oder Ergänzungen der Dokumentation{% endif %}
-| `duplicate`        | Kennzeichnet ähnliche Issues oder Pull Requests                                                                                                           |
-| `enhancement`      | Kennzeichnet neue Funktionsanfragen                                                                                                                       |
-| `good first issue` | Kennzeichnet einen geeigneten Issue für erstmalig Mitwirkende                                                                                             |
-| `help wanted`      | Kennzeichnet, dass ein Betreuer Hilfe bei einem Issue oder Pull Request benötigt                                                                          |
-| `invalid`          | Kennzeichnet, dass ein Issue oder Pull Request nicht mehr relevant ist                                                                                    |
-| `question`         | Kennzeichnet, dass ein Issue oder Pull Request weitere Informationen benötigt                                                                             |
-| `wontfix`          | Kennzeichnet, dass die Arbeit an einem Issue oder Pull Request nicht fortgesetzt wird                                                                     |
+| `duplicate`        | Kennzeichnet ähnliche Issues oder Pull Requests                                                                                                                          |
+| `enhancement`      | Kennzeichnet neue Funktionsanfragen                                                                                                                                      |
+| `good first issue` | Kennzeichnet einen geeigneten Issue für erstmalig Mitwirkende                                                                                                            |
+| `help wanted`      | Kennzeichnet, dass ein Betreuer Hilfe bei einem Issue oder Pull Request benötigt                                                                                         |
+| `invalid`          | Kennzeichnet, dass ein Issue oder Pull Request nicht mehr relevant ist                                                                                                   |
+| `question`         | Kennzeichnet, dass ein Issue oder Pull Request weitere Informationen benötigt                                                                                            |
+| `wontfix`          | Kennzeichnet, dass die Arbeit an einem Issue oder Pull Request nicht fortgesetzt wird                                                                                    |
 
 Standardkennzeichnungen sind in jedem neuen Repository beinhaltet, wenn das Repository erstellt wird, aber Du kannst die Kennzeichnungen später bearbeiten oder löschen.
 
+Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 Organisationsinhaber können die Standardkennzeichnungen für Repositories in ihrer Organisation anpassen. Weitere Informationen findest Du unter „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)."
 {% endif %}
@@ -93,6 +95,6 @@ Deleting a label will remove the label from issues and pull requests.
 {% data reusables.project-management.delete-label %}
 
 ### Weiterführende Informationen
-- "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
+- „[Issues und Pull Requests nach Kennzeichnungen filtern](/articles/filtering-issues-and-pull-requests-by-labels)“{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 - "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
 - "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %}
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index 80f4ab7427..32472a0737 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ Du kannst jede gefilterte Ansicht nach folgenden Aspekten sortieren:
 * Die Issues oder Pull Requests mit den wenigsten Kommentaren
 * Die neuesten Issues oder Pull Requests (nach Änderungsdatum)
 * Die ältesten Issues oder Pull Requests (nach Änderungsdatum)
-* Die am häufigsten zu Issues oder Pull Requests hinzugefügte [Reaktion](/articles/about-conversations-on-github#reacting-to-ideas-in-comments)
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. Wähle oben rechts im Dropdownmenü „Sort“ (Sortieren) eine Option aus. ![Verwenden des Dropdownmenüs „Sort“ (Sortieren)](/assets/images/help/issues/issues_sort_dropdown.png)
+1. Wähle oben rechts im Dropdownmenü „Sort“ (Sortieren) eine Option aus. ![Verwenden des Dropdownmenüs „Sort“ (Sortieren)](/assets/images/help/issues/issues_sort_dropdown.png)
 
 Zum Aufheben der Sortierung klicke auf **Sort** > **Newest** (Sortieren > Neueste).
 
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md
index 2de3451175..573bed3886 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md
@@ -43,7 +43,7 @@ Bei Pull Requests kannst Du die Suche auch verwenden, um:
 - Pull Requests zu filtern, in denen ein Reviewer um Änderungen gebeten hat: `state:open type:pr review:changes_requested`
 - Pull Requests nach [Reviewer](/articles/about-pull-request-reviews/) zu filtern: `state:open type:pr reviewed-by:octocat`
 - Pull Requests nach dem bestimmten Benutzer zu filtern, der für den [Review angefordert](/articles/requesting-a-pull-request-review) wurde: `state:open type:pr review-requested:octocat`
-- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- Pull Requests nach einem Team filtern, das für dein Review angefordert wurde: `state:open type:pr team-review-requested:github/atom`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
 - Nach Pull Requests filtern, die zu einem Issue verknüpft sind, die der Pull Request schließen könnte: `linked:issue`{% endif %}
 
 ### Weiterführende Informationen
diff --git a/translations/de-DE/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md
index 4392776b01..265b8740c7 100644
--- a/translations/de-DE/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md
+++ b/translations/de-DE/content/github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests.md
@@ -18,4 +18,4 @@ Deine Dashboards für Issues und Pull Requests sind im oberen Bereich jeder Seit
 
 ### Weiterführende Informationen
 
-- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}”[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 %}"
+- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}„[Deine Abonnements ansehen](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}„[Liste der von Dir beobachteten Repositorys](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-code.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-code.md
index ddb7a981aa..809b3686fb 100644
--- a/translations/de-DE/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ Mit dem Kennzeichner `path` können Sie nach Quellcode unter einem bestimmten Pf
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) sucht JavaScript-Dateien mit dem Wort „console“ im Verzeichnis <em>app/public</em> oder in dessen Unterverzeichnissen (auch im Verzeichnis <em>app/public/js/form-validators</em>). |
 
 ### Suche nach Sprache
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-Sie können Code auch in Abhängigkeit der Programmiersprache suchen.
+Du kannst Code auch in Abhängigkeit der Programmiersprache suchen. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | Qualifizierer              | Beispiel                                                                                                                                                                                                        |
 | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -105,5 +106,5 @@ Der Kennzeichner `extension` sucht Codedateien mit einer bestimmten Dateierweite
 ### Weiterführende Informationen
 
 - „[Suchergebnisse sortieren](/articles/sorting-search-results/)“
-- "[Searching in forks](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %}
+- „[Durchsuchen von Forks](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %}
 - „[Navigieren von Code auf {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %}
diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md
index 1dda93d974..03df9160c4 100644
--- a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md
+++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md
@@ -230,7 +230,7 @@ Mit dem Kennzeichner `reactions` können Sie Issues und Pull Requests nach der A
 ### Suche nach Pull-Request-Entwürfen
 Sie können nach Pull-Request-Entwürfen suchen. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/articles/about-pull-requests#draft-pull-requests).“
 
-| Qualifier        | Example | ------------- | -------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) findet Pull Requests, die bereit sind für den Review.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) findet Pull-Request-Entwürfe.{% endif %}
+| Qualifizierer    | Beispiel | ------------- | -------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) findet Pull-Request-Entwürfe. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) findet Pull Requests, die bereit sind für den Review.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) findet Pull-Request-Entwürfe.{% endif %}
 
 ### Suche nach Review-Status und Reviewer eines Pull-Requests
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 0563cbaaed..ab2e99a4fb 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)."
+
+{% endnote %}
 
 If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index d4823b231e..e5fcc9e1d1 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### Weiterführende Informationen
 
-- „[Informationen zu {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)“
-- „[Unterstützung von Open-Source-Mitarbeitern](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)"
+- „[Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)“
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index 86893eac64..f7fc24aa7a 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,26 +16,11 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %}
 
 ### About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
 
-We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_dotcom_the_website %}:
-
-- **Committers** is the number of committers who contributed to at least one private repository in an organization and who use a seat in your license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
-- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
-
-If there are no unique committers, this means that all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
-
-{% note %}
-
-**Note:** The total number of seats used in your license is not the sum of either the committers or the unique committers to each repository or organization. This is because there are people who contribute to multiple repositories or organizations. The number of seats used is measured across the whole enterprise account to ensure that each person is counted only once regardless of how many repositories or organizations they contribute to.
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### Managing your license usage for {% data variables.product.prodname_GH_advanced_security %}
 
-When you enable {% data variables.product.prodname_GH_advanced_security %} for a single repository, or for all repositories in an organization, {% data variables.product.company_short %} shows how many extra seats this will use and prompts you for confirmation. If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up. This makes it easy to understand the impact of your changes on the use of your license.
-
-If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available. If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.
-
-As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal.
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
 You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)."
 
@@ -43,9 +28,4 @@ For more information on viewing license usage, see "[Viewing your {% data variab
 
 ### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license
 
-When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify:
-
-- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company.
-- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced.
-
-When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index 82dcb67b85..2eee764a7b 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ Ihre Quittungen enthalten Ihr {% data variables.product.prodname_dotcom %}-Abonn
 ### Informationen zu den Quittungen Deines persönlichen Kontos hinzufügen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### Informationen zu den Quittungen Deiner Organisation hinzufügen
@@ -40,9 +40,9 @@ Ihre Quittungen enthalten Ihr {% data variables.product.prodname_dotcom %}-Abonn
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index 44672ee9e5..f034f61b4a 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ Wir bieten keine Abrechnung und unterstützen keine Bestellungen für persönlic
 ### Die Zahlungsmethode für Dein persönliches Konto aktualisieren
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### Die Zahlungsmethode für Deine Organisation aktualisieren
@@ -38,9 +39,10 @@ Wir bieten keine Abrechnung und unterstützen keine Bestellungen für persönlic
 
 Wenn sich Deine Organisation außerhalb der USA befindet oder Du zum Bezahlen von {% data variables.product.product_name %} ein Firmenkonto verwendest, bietet sich PayPal als Zahlungsmethode an.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index 6f7e4e1f4b..4ed8b0418d 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ Wenn Du eine kostenlose Testperiode auf einem kostenpflichtigen Plan kündigst,
 ### Eine App für Dein persönliches Konto kündigen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### Eine kostenlose Testperiode einer App für Dein persönliches Konto kündigen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ Wenn Du eine kostenlose Testperiode auf einem kostenpflichtigen Plan kündigst,
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ Wenn Du eine kostenlose Testperiode auf einem kostenpflichtigen Plan kündigst,
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index b656bef9ed..9ff1881917 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ Wenn Sie die Dauer Ihres Abrechnungszeitraums ändern, werden Ihr {% data variab
 ### Die Dauer des Abrechnungszeitraums Deines persönlichen Kontos ändern
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ Wenn Sie die Dauer Ihres Abrechnungszeitraums ändern, werden Ihr {% data variab
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ Wenn Sie die Dauer Ihres Abrechnungszeitraums ändern, werden Ihr {% data variab
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. Klicke unter „Billing overview“ (Abrechnungsübersicht) auf **Change plan** (Plan ändern). ![Schaltfläche zum Ändern des Plans in der Abrechnungsübersicht](/assets/images/help/billing/billing_overview_change_plan.png)
 5. Klicke in der oberen rechten Ecke auf **Switch to monthly billing** (Auf monatliche Abrechnung umstellen) oder **Switch to yearly billing** (Auf jährliche Abrechnung umstellen). ![Abschnitt zu Abrechnungsinformationen](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index b504008550..768a33f05d 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ Wenn Du bereits ein persönliches {% data variables.product.prodname_dotcom %}-B
 
 ### Schritt 3: Die Organisation auf ein jährlich bezahltes Abonnement hochstufen
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (Im nächsten Schritt kannst Du weitere Benutzer in die Organisation aufnehmen.)
 6. Wähle unter „Upgrade summary“ (Übersicht der Aktualisierung) **Pay yearly** (Jährlich bezahlen) aus, um jährlich für die Organisation zu zahlen. ![Optionsfeld für jährliche Abrechnung](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. Gib unter „Pay with“ (Zahlung mit) Deine Kreditkartendaten ein. ![Formular zum Eingeben der Kreditkartendaten](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. Klicke auf **Update credit card** (Kreditkarte aktualisieren).
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### Schritt 4: Die Anzahl an bezahlten Benutzern in der Organisation hochstufen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
index e18f055207..6828c50405 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
@@ -20,11 +20,11 @@ topics:
 
 ### Rabatte für persönliche Konten
 
-Neben den unbegrenzten öffentlichen und privaten Repositorys für Studenten und Universitätsmitarbeiter mit {% data variables.product.prodname_free_user %} können verifizierte Studenten das {% data variables.product.prodname_student_pack %} beantragen, um zusätzliche Vorteile von {% data variables.product.prodname_dotcom %}-Partnern zu erhalten. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)."
+Neben den unbegrenzten öffentlichen und privaten Repositorys für Studenten und Universitätsmitarbeiter mit {% data variables.product.prodname_free_user %} können verifizierte Studenten das {% data variables.product.prodname_student_pack %} beantragen, um zusätzliche Vorteile von {% data variables.product.prodname_dotcom %}-Partnern zu erhalten. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)."
 
 ### Rabatte für Schulen und Universitäten
 
-Verifizierte akademische Fakultäten können {% data variables.product.prodname_team %} für den Unterricht oder die akademische Forschung beantragen. For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)." Weitere Informationen findest Du unter „[{{ site.data.variables.product.prodname_dotcom }} für Lehre und Forschung nutzen](/articles/using-github-in-your-classroom-and-research)“. Weitere Informationen findest Du unter [{% data variables.product.prodname_education %}](https://education.github.com/).
+Verifizierte akademische Fakultäten können {% data variables.product.prodname_team %} für den Unterricht oder die akademische Forschung beantragen. For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)." Weitere Informationen findest Du unter „[{{ site.data.variables.product.prodname_dotcom }} für Lehre und Forschung nutzen](/articles/using-github-in-your-classroom-and-research)“. Weitere Informationen findest Du unter [{% data variables.product.prodname_education %}](https://education.github.com/).
 
 ### Rabatte für gemeinnützige Organisationen und Bibliotheken
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index 06c04c1610..83c6d34fd3 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -16,8 +16,7 @@ Wenn Du die Anzahl Deiner Datenpakete herabstufst, werden Deine Änderungen zum
 ### Speicher und Bandbreite für ein persönliches Konto herabstufen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
@@ -25,10 +24,8 @@ Wenn Du die Anzahl Deiner Datenpakete herabstufst, werden Deine Änderungen zum
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 96c3b4ecef..d93e436a0a 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ Wenn Du eine App herabstufst, bleibt Dein Abonnement bis zum Ende des aktuellen
 ### Eine App für Dein persönliches Konto herabstufen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ Wenn Du eine App herabstufst, bleibt Dein Abonnement bis zum Ende des aktuellen
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index 36268cc7b0..468fdf7b4b 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ Wenn Du das Abonnement Deines Benutzerkonto oder Deiner Organisation herabstufst
 Wenn Du Dein Benutzerkonto von {% data variables.product.prodname_pro %} nach {% data variables.product.prodname_free_user %} herunterstufst, wird Dein Konto den Zugriff auf die erweiterten Code-Prüfwerkzeuge auf privaten Repositorys verlieren. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Verwende das Dropdownmenü **Edit** (Bearbeiten) und klicke auf **Downgrade to Free** (Herunterstufen auf Kostenlos). ![Schaltfläche „Downgrade to free" (Herabstufen auf Kostenlos)](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![Schaltfläche „Downgrade to free" (Herabstufen auf Kostenlos)](/assets/images/help/billing/downgrade-to-free.png)
 5. Lies die Informationen zu den Features, auf die Dein Benutzerkonto ab dem nächsten Abrechnungsdatum nicht mehr zugreifen kann, und klicke dann auf **I understand. Continue with downgrade** (Ich verstehe, mit Herabstufen fortfahren). ![Schaltfläche „Continue with downgrade" (Mit Herunterstufen fortfahren)](/assets/images/help/billing/continue-with-downgrade.png)
 
 Wenn Du eine {% data variables.product.prodname_pages %}-Website in einem privaten Repository veröffentlicht und eine benutzerdefinierte Domäne hinzugefügt hast, entferne oder aktualisiere Deine DNS-Einträge vor dem Herabstufen von {% data variables.product.prodname_pro %} nach {% data variables.product.prodname_free_user %}, um das Risiko einer Domänenübernahme zu verhindern. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“
@@ -45,12 +44,10 @@ Wenn du Deine Organisation von {% data variables.product.prodname_team %} nach {
 
 Wenn Du Deine Organisation von {% data variables.product.prodname_ghe_cloud %} nach {% data variables.product.prodname_team %} oder {% data variables.product.prodname_free_team %} herabstufst, wird das Konto den Zugriff auf erweiterte Sicherheits-, Compliance- und Bereitstellungskontrollen verlieren. {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Benutze das **Edit ** (Bearbeiten) Dropdownmenü und klicke auf die Herabstufungs-Option, die Du willst. ![Schaltfläche „Downgrade“ (Herabstufen)](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![Schaltfläche „Downgrade“ (Herabstufen)](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### Abonnement einer Organisation mit älteren Repository-abhängiger Preisgestaltung herabstufen
@@ -59,27 +56,24 @@ Wenn Du Deine Organisation von {% data variables.product.prodname_ghe_cloud %} n
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} Weitere Informationen findest Du auf „[Deine Organisation von Repository-abhängige auf benutzerabhängige Preisgestaltung wechseln](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**. ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png)
 1. Klicke unter "Abrechnung/Pläne" neben dem Plan, den Du ändern möchtest, auf **Downgrade** (Herabstufen). ![Schaltfläche „Downgrade“ (Herabstufen)](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. Enter the reason you're downgrading your account, then click **Downgrade plan**. ![Text box for downgrade reason and downgrade button](/assets/images/help/billing/downgrade-plan-button.png)
 
 ### Bezahlte Benutzer aus Deiner Organisation entfernen
 
-Um die Anzahl an bezahlten Benutzern, die Deine Organisation verwendet, zu reduzieren, kannst Du Mitglieder aus Deiner Organisation entfernen oder Mitglieder in externe Mitarbeiter umwandeln und ihnen nur den Zugriff auf öffentliche Repositorys gewähren. Weitere Informationen findest Du unter:
+Um die Anzahl an bezahlten Benutzern, die Ihre Organisation verwendet, zu reduzieren, können Sie Mitglieder aus Ihrer Organisation entfernen oder Mitglieder in externe Mitarbeiter umwandeln und ihnen nur den Zugriff auf öffentliche Repositorys gewähren. Weitere Informationen findest Du unter:
 - „[Ein Mitglied aus Deiner Organisation entfernen](/articles/removing-a-member-from-your-organization)“
 - „[Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln](/articles/converting-an-organization-member-to-an-outside-collaborator)“
 - „[Den Zugriff einer Person auf ein Repository einer Organisation verwalten](/articles/managing-an-individual-s-access-to-an-organization-repository)“
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Verwende das Dropdownmenü **Edit** (Bearbeiten) und klicke auf **Remove seats** (Benutzer entfernen). ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
 1. Wählen Sie unter „Remove seats“ (Benutzer entfernen) die Anzahl an Benutzern aus, auf die Sie reduzieren möchten. ![remove seats option](/assets/images/help/billing/remove-seats-amount.png)
 1. Lies die Informationen zur neuen Preisgestaltung an Deinem nächsten Abrechnungsdatum durch, und klicke dann auf **Remove seats** (Benutzer entfernen). ![remove seats button](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index 1cec704b84..7d55f63568 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ Because you have not enabled overages, your next attempt to create a workflow ar
 Jeder kann das Ausgabenlimit für {% data variables.product.prodname_actions %} für sein eigenes Benutzerkonto verwalten.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Jeder kann das Ausgabenlimit für {% data variables.product.prodname_actions %}
 
 Organisationsinhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_actions %} für eine Organisation verwalten.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise-Inhaber und Abrechnungsmanager können das Ausgabenlimit von {% data
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "
-{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**.
-  ![Registerkarte „Cost Management" (Kostenverwaltung)](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index 7d8e2782bc..69455976d8 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ Da Du keine Überschreitungen zugelassen hast, wird Dein nächster Versuch, eine
 Jeder kann das Ausgabenlimit für {% data variables.product.prodname_registry %} für sein eigenes Benutzerkonto verwalten.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Jeder kann das Ausgabenlimit für {% data variables.product.prodname_registry %}
 
 Organisationsinhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_registry %} für eine Organisation verwalten.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise-Inhaber und Abrechnungsmanager können das Ausgabenlimit von {% data
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "
-{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**.
-  ![Registerkarte „Cost Management" (Kostenverwaltung)](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index a5cbde0be5..8e9c5dfbf4 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ Wenn Sie Ihr {% data variables.product.product_name %}-Abonnement mit einem Guts
 ### Zahlungsmethode Deines persönlichen Kontos entfernen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ Wenn Sie Ihr {% data variables.product.product_name %}-Abonnement mit einem Guts
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index 276e4c52cd..84933cafcd 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### Kreditkarteninformationen Deiner Organisation ändern
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. Gib Deine neuen Kreditkarteninformationen in das sichere Formular ein. ![Formular für Kreditkarteninformationen](/assets/images/help/settings/creditcard-billing-form.png)
-1. Klicke auf **Update credit card** (Kreditkarte aktualisieren) oder auf **Save credit card** (Kreditkarte speichern).
+1. Under "Payment method", click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index e45e949821..f4280cec87 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ Informationen zur Änderung Deiner E-Mail-Adresse für die Abrechnung findest Du
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Gib unter **Billing email** (E-Mail-Adresse für die Abrechnung) eine gültige E-Mail-Adresse ein. Diese Adresse kann innerhalb Deiner Organisation auch für weitere Zwecke eingesetzt werden. ![Textfeld für E-Mail-Adresse für die Abrechnung](/assets/images/help/settings/org-billing-email.png)
 5. Klicke zur Bestätigung Deiner Änderungen auf **Update profile** (Profil aktualisieren). ![Schaltfläche „Update profile" (Aktualisieren des Profils)](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ If you have users that want to receive billing reports, you can add their email
 #### Adding a recipient for billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Billing management", to the right of "Email recipients", click **Add**. ![Add recipient](/assets/images/help/billing/billing-add-email-recipient.png)
 1. Type the email address of the recipient, then click **Add**. ![Add recipient modal](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ If you have users that want to receive billing reports, you can add their email
 One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected.
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Billing management", find the email address you want to set as the primary recipient.
 1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**. ![Mark primary recipient](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### Removing a recipient from billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Email recipients", find the email address you want to remove.
 1. For the user's entry in the list, click **Edit**. ![Edit recipient](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. To the right of the email address, use the "Edit" drop-down menu, and click *Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. Review the confirmation prompt, then click **Remove**.
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index f404ffa3d8..b4aa01701a 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### Zusätzlichen Speicher und Bandbreite für ein persönliches Konto kaufen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index 9553ceee29..7f8e365a74 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,23 +22,19 @@ topics:
 
 ### Anzahl der bezahlten Benutzer einer Organisation heraufstufen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
 
-Nachdem Du Benutzer hinzugefügt hast, wird der für die Organisation hinterlegten Zahlungsmethode ein anteiliger Betrag in Rechnung gestellt, der auf der Anzahl der hinzugefügten Benutzer und der verbleibenden Zeit in Deinem Abrechnungszeitraum basiert.
+Nachdem Sie Benutzer hinzugefügt haben, wird der für die Organisation hinterlegten Zahlungsmethode ein anteiliger Betrag in Rechnung gestellt, der auf der Anzahl der Benutzer, die Sie hinzufügen, und der verbleibenden Zeit in Ihrem Abrechnungszeitraum basiert.
 
 ### Anzahl der bezahlten Benutzer einer Organisation auf kostenlos herabstufen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 6119be325b..93c6652008 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ Wenn Du eine App heraufstufst, wird basierend auf der verbleibenden Zeit bis zu
 ### Eine App für Dein persönliches Konto heraufstufen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ Wenn Du eine App heraufstufst, wird basierend auf der verbleibenden Zeit bis zu
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index ad80739a70..d352dc7875 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 Du kannst Dein persönliches Konto von {% data variables.product.prodname_free_user %} auf {% data variables.product.prodname_pro %} heraufstufen, um erweiterte Code-Review-Werkzeuge für private Repositorys zu erhalten. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Next to "
-{% data variables.product.prodname_free_user %}", click **Upgrade**.
-  ![Schaltfläche „Upgrade“](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![Schaltfläche „Upgrade“](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ Du kannst Deine Organisation von {% data variables.product.prodname_free_team %}
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ Wenn Du ein Enterprise-Konto mit {% data variables.product.prodname_ghe_cloud %}
 
 Wenn Du zusätzlichen Benutzern den Zugriff auf die privaten Repositorys Deiner {% data variables.product.prodname_team %}-Organisation geben möchtest, kannst Du jederzeit zusätzliche Benutzer erwerben.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ Wenn Du zusätzlichen Benutzern den Zugriff auf die privaten Repositorys Deiner
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} Weitere Informationen findest Du unter „[Über benutzerabhängige Preise](/articles/about-per-user-pricing)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Benutze rechts neben dem Plannamen das Dropdowmenü **Edit** (Bearbeiten) und wähle **Edit plan** (Plan bearbeiten). ![Dropdownmenü „Edit" (Bearbeiten)](/assets/images/help/billing/per-user-upgrade-button.png)
 6. Klicke rechts von „Advanced tools for teams" (Erweiterte Werkzeuge für Teams) auf **Upgrade now** (jetzt heraufstufen). ![Schaltfläche „Upgrade now" (jetzt heraufstufen)](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index efeb510ef3..d47b7a4833 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ Wenn Du eine ausstehende Änderung stornierst, wird Dein Abonnement bei Deinem n
 ### Ausstehende Änderungen am Abonnement Deines persönlichen Kontos anzeigen und verwalten
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### Ausstehende Änderungen am Abonnement Deiner Organisation anzeigen und verwalten
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index e0ba36f539..eeb40b7568 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### Speicher- und Bandbreitennutzung für ein persönliches Konto
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Speicher- und Bandbreitennutzung für eine Organisation
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Weiterführende Informationen
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index 32abd1bd9f..eb73a91f01 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ Du kannst auch die verrechenbaren Auftrags-Ausführungsminuten für eine einzeln
 Jeder kann die Nutzung von {% data variables.product.prodname_actions %} für sein eigenes Benutzerkonto anzeigen.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ Jeder kann die Nutzung von {% data variables.product.prodname_actions %} für se
 
 Organization owners and billing managers can view {% data variables.product.prodname_actions %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_actions %} usage in the organization billing page.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index 151c1b0164..27b5e7d242 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,24 +1,24 @@
 ---
 title: Viewing your GitHub Advanced Security usage
-intro: 'You can view and manage usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
-permissions: 'Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
   free-pro-team: '*'
 ---
 
-Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Periodically you should check that your use is within your license capacity. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
 
-### Viewing and managing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
+### Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
 
-You can check how many seats your license includes and how many of them are currently used on the "Enterprise licensing" page.
+You can check how many seats your license includes and how many of them are currently used.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
-4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png)
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
 5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
 6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[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/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index 676e2516e2..1b2355954b 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 Jeder kann die Nutzung von {% data variables.product.prodname_registry %} für sein eigenes Benutzerkonto anzeigen.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ Jeder kann die Nutzung von {% data variables.product.prodname_registry %} für s
 
 Organization owners and billing managers can view {% data variables.product.prodname_registry %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_registry %} usage in the organization billing page.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index be6c7785b9..0b65912d53 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### Quittungen für Dein persönliches Konto anzeigen
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index 3b5f4e39aa..b118fc29d1 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### Nächstes Abrechnungsdatum Deines persönlichen Kontos finden
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Nächstes Abrechnungsdatum Deiner Organisation finden
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Weiterführende Informationen
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index ea9b3d4b19..791e958b09 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -36,5 +36,5 @@ After you disconnect your Azure subscription from your enterprise account, your
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
+1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**.
 1. Review the prompt, then click **Remove**.
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index 7fad090bb3..622b4fdbd3 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -48,3 +48,19 @@ You can disable all workflows for an enterprise or set a policy that configures
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### Setting the permissions of the `GITHUB_TOKEN` for your enterprise
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. Click **Save** to apply the settings.
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md
index f31116143d..4d99e6ad30 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..39850b1dd2
--- /dev/null
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: Restricting email notifications for your enterprise account
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### About email restrictions for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restricting email notifications for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..fa4be47e6b
--- /dev/null
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About domain verification
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index c6141a24d4..5b60d154c3 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -20,6 +20,15 @@ Wenn Du SAML Single Sign-On für Dein Enterprise-Konto aktivierst, kann jedes En
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index f5e880370c..747f147fb9 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 Du kannst optional eine Beschreibung, einen Standort, eine Website und eine E-Mail-Adresse für Deine Organisation hinzufügen und wichtige Repositorys am Anfang der Seite anheften.
 
-{% if currentVersion == "free-pro-team@latest" %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. Weitere Informationen findest Du unter „[Domänen Deiner Organisation überprüfen](/organizations/managing-organization-settings/verifying-your-organizations-domain).“
+{% if currentVersion == "free-pro-team@latest" %}Um die Identität Ihrer Organisation zu bestätigen und einen „Verifiziert“-Badge auf der Profilseite Ihrer Organisation anzuzeigen, müssen Sie die Domains Ihrer Organisation mit {% data variables.product.product_name %} verifizieren. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![Beispiel einer verifizierten Profilseite einer Organisation](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md
index 191d134c6a..b39b580084 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md
@@ -29,7 +29,7 @@ People who visit your profile can also see the following information.
 
 - Repositories and gists you own or contribute to. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can showcase your best work by pinning repositories and gists to your profile. For more information, see "[Pinning items to your profile](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)."{% endif %}
 - Repositorys, die Sie mit einem Stern versehen haben. For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)."
-- Eine Übersicht über Deine Aktivitäten in den Organisationen, Repositorys und Teams, in denen Du am meisten aktiv bist. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% if currentVersion == "free-pro-team@latest" %}
+- Eine Übersicht über Deine Aktivitäten in den Organisationen, Repositorys und Teams, in denen Du am meisten aktiv bist. Weitere Informationen findest Du unter „[Übersicht über Deine Aktivitäten in Deinem Profil anzeigen](/articles/showing-an-overview-of-your-activity-on-your-profile)“.{% if currentVersion == "free-pro-team@latest" %}
 - Badges that show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. Weitere Informationen findest Du unter „[Dein Profil personalisieren](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)“.{% endif %}
 
 Sie können auch einen Status auf Ihrem Profil einstellen, um Angaben zu Ihrer Verfügbarkeit zu machen. Weitere Informationen findest Du unter „[Status festlegen](/articles/personalizing-your-profile/#setting-a-status).“
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index 23a4fca4af..680197891a 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ Wenn Sie die Option „Busy“ (Beschäftigt) auswählen, wird ein entsprechende
 
 When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
 
-| Badge                                                           | Program                                                              | Beschreibung                                                                                                                                                                                                                                                                                                                                               |
-| --------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **Developer Program Member**                                         | If you're a registered member of the GitHub Developer Program, building an app with the GitHub API, you'll get a Developer Program Member badge on your profile. For more information on the GitHub Developer Program, see [GitHub Developer](/program/).                                                                                                  |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **GitHub Sponsor**                                                   | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a GitHub Sponsor badge on your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)."                            |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                              | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. Weitere Informationen zu {% data variables.product.prodname_pro %} finden Sie unter „[Produkte von {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)“.                                         |
+| Badge                                                                                                                    | Program                                                              | Beschreibung                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter Contributor badge icon](/assets/images/help/profile/badge-mars-2020-small.png)                    | **Mars 2020 Helicopter Contributor**                                 | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
+| ![Arctic Code Vault Contributor badge icon](/assets/images/help/profile/badge-arctic-code-vault-small.png)               | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were part of the program. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com).                                                                                                                                                                                      |
+| ![{% data variables.product.prodname_dotcom %} Sponsor badge icon](/assets/images/help/profile/badge-sponsors-small.png) | **{% data variables.product.prodname_dotcom %} Sponsor**             | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)."                                                                                                                                                                                                                 |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                              | **Developer Program Member**                                         | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% data variables.product.prodname_dotcom %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/).                                                                                                                                                                                                                                                                                   |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                                     | **Pro**                                                              | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. Weitere Informationen zu {% data variables.product.prodname_pro %} findest Du unter „[Produkte von {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro).“                                                                                                                                                                                                                                                                                                                                              |
 
 ### Disabling badges on your profile
 
-You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO and {% data variables.product.prodname_arctic_vault %} badges.
+You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
 
 {% data reusables.user_settings.access_settings %}
-2. Under "Profile settings", deselect the badge you want you disable. ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. Under "Profile settings", deselect the badge you want you disable. ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/profile-badge-settings.png)
 3. Klicke auf **Update preferences** (Voreinstellungen aktualisieren).
 
 {% endif %}
 
+### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
+
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+
+| {% data variables.product.prodname_dotcom %} Repository                       | Version   | Tag                                                                                                        |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.3.3     | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### Weiterführende Informationen
 
 - „[Informationen zu Ihrem Profil](/articles/about-your-profile)“
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md
index 8745d7036c..036f670376 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md
@@ -51,7 +51,7 @@ Weitere Informationen zu Sternen für Repositorys und zum Folgen von Personen fi
 
 ### Empfohlene Repositorys erkunden
 
-Im Abschnitt "Explore repositories" (Repositories erkunden) auf der rechten Seite Deines Dashboards kannst Du empfohlene Repositorys in Deinen Communities erkunden. Recommendations are based on repositories you've starred or visited, the people you follow, and activity within repositories that you have access to.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+Im Abschnitt "Explore repositories" (Repositories erkunden) auf der rechten Seite Deines Dashboards kannst Du empfohlene Repositorys in Deinen Communities erkunden. Empfehlungen basieren auf den von Dir markierten oder besuchten Repositorys, auf den Personen, denen Du folgst und auf den Aktivitäten innerhalb der Repositorys, auf die Du Zugriff hast.{% if currentVersion == "free-pro-team@latest" %} Weitere Informationen findest Du unter „[Möglichkeiten zum Beitragen an Open Source auf {% data variables.product.prodname_dotcom %} finden](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md
index e9308d63e9..bd6dcd5b8c 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md
@@ -16,7 +16,7 @@ topics:
 
 ### Informationen zu Änderungen des Benutzernamens
 
-You can change your username to another username that is not currently in use.{% if currentVersion == "free-pro-team@latest" %} If the username you want is not available, you'll see information about whether you can request the username to be released when you type in the desired username.
+Du kannst Deinen Benutzernamen in einen aktuell nicht verwendeten Benutzernamen ändern.{% if currentVersion == "free-pro-team@latest" %} Falls der gewünschte Benutzername nicht verfügbar ist, wird angezeigt, ob Du verlangen kannst, dass der Benutzername freigegeben wird, wenn Du den gewünschten Benutzernamen eingibst.
 
 Falls der Benutzername nicht freigegeben werden kann und Du für den Benutzernamen keine Handelsmarke führst, kannst Du einen anderen Benutzernamen auswählen oder Deinen aktuellen Benutzernamen beibehalten. {% data variables.contact.github_support %} kann den für Sie nicht verfügbaren Benutzernamen nicht freigeben. Weitere Informationen findest Du unter „[Benutzernamen ändern](#changing-your-username)“.{% endif %}
 
@@ -36,7 +36,7 @@ Wenn der neue Inhaber Deines alten Benutzernamens ein Repository mit demselben N
 
 ### Links zu früheren Profilseiten
 
-Nach dem Ändern Deines Benutzernamens lösen Links zu Deinen früheren Profilseiten, z. B. `https://{% data variables.command_line.backticks %}/previoususername`, eine 404-Fehlermeldung aus. We recommend updating any links to your {% data variables.product.product_name %} account from elsewhere{% if currentVersion == "free-pro-team@latest" %}, such as your LinkedIn or Twitter profile{% endif %}.
+Nach dem Ändern Deines Benutzernamens lösen Links zu Deinen früheren Profilseiten, z. B. `https://{% data variables.command_line.backticks %}/previoususername`, eine 404-Fehlermeldung aus. Wir empfehlen Dir, alle Links zu Deinem {% data variables.product.product_name %}-Konto an anderen Stellen zu aktualisieren{% if currentVersion == "free-pro-team@latest" %}, z. B. in Deinem LinkedIn- oder Twitter-Profil{% endif %}.
 
 ### Deine Git-Commits
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index f328a637da..c5da1956f0 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. Wenn Du eine neue E-Mail-Adresse hinzufügen und als primäre E-Mail-Adresse festlegen möchtest, gib unter „Add email address“ (E-Mail-Adresse hinzufügen) eine neue E-Mail-Adresse ein. Klicke dann auf **Add** (Hinzufügen). ![Schaltfläche zum Hinzufügen einer anderen E-Mail-Adresse](/assets/images/help/settings/add_another_email_address.png)
 4. Klicke im Dropdownmenü unter „Primary email address“ (Primäre E-Mail-Adresse) auf die E-Mail-Adresse, die Du als primäre E-Mail-Adresse festlegen möchtest, und klicke dann auf **Save** (Speichern). ![Schaltfläche zum Festlegen als primäre Adresse](/assets/images/help/settings/set_as_primary_email.png)
 5. To remove the old email address from your account, next to the old email, click
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}.
 {% if currentVersion == "free-pro-team@latest" %}
 6. Verifiziere Deine neue primäre E-Mail-Adresse. Without a verified email address, you won't be able to use all of
 {% data variables.product.product_name %}'s features. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/articles/verifying-your-email-address).“
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md
index bd4d880b69..1bd06eb425 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md
@@ -37,7 +37,7 @@ Wenn Du möchtest, dass Deine Organisation denselben Namen aufweist, den Du aktu
 Du kannst Dein persönliches Benutzerkonto auch direkt in eine Organisation umwandeln. Beim Umwandeln Deines Kontos geschieht Folgendes:
  - Die Repositorys werden so beibehalten, wie sie sind, ohne dass Du sie manuell an ein anderes Konto übertragen musst
  - Es werden automatisch Mitarbeiter zu Teams eingeladen, wobei die Berechtigungen den bisherigen Berechtigungen entsprechen.
- {% if currentVersion == "free-pro-team@latest" %}- For user accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
+ {% if currentVersion == "free-pro-team@latest" %}– Bei Benutzerkonten auf {% data variables.product.prodname_pro %} wird die Abrechnung automatisch auf [das bezahlte {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) umgestellt, ohne dass Du die Zahlungsinformationen erneut eingeben, Deinen Abrechnungszeitraum anpassen oder doppelt bezahlen musst.{% endif %}
 
 1. Erstelle ein neues persönliches Konto, mit dem Du Dich nach der Umwandlung bei GitHub anmelden und auf die Organisation und Deine Repositorys zugreifst.
 2.  [Verlasse alle Organisationen](/articles/removing-yourself-from-an-organization), denen das Benutzerkonto angehört, das Du gerade umwandelst.
@@ -58,5 +58,5 @@ Du kannst Dein persönliches Benutzerkonto auch direkt in eine Organisation umwa
 
 ### Weiterführende Informationen
 - „[Teams einrichten](/articles/setting-up-teams)“
-{% if currentVersion == "free-pro-team@latest" %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}- „[Benutzer zum Beitritt zu Deiner Organisation einladen](/articles/inviting-users-to-join-your-organization)“{% endif %}
 - „[Auf eine Organisation zugreifen](/articles/accessing-an-organization)“
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md
index b0414d749e..17366f0b44 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md
@@ -11,9 +11,9 @@ topics:
   - Accounts
 ---
 
-Wenn Du Dein Benutzerkonto löschst, werden alle dazugehörigen Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten Deines Kontos ebenfalls gelöscht. {% if currentVersion == "free-pro-team@latest" %} Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted - instead, they'll be associated with our [Ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}
+Wenn Du Dein Benutzerkonto löschst, werden alle dazugehörigen Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten Deines Kontos ebenfalls gelöscht. {% if currentVersion == "free-pro-team@latest" %} Deine Issues, Pull Requests und Kommentare in Repositorys von anderen Benutzern werden nicht gelöscht, sondern mit unserem [Ghost user](https://github.com/ghost) (Geisterbenutzer) verknüpft.{% else %}Deine Issues, Pull Requests und Kommentare in Repositorys von anderen Benutzern werden nicht gelöscht.{% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %} The account name also becomes available to anyone else to use on a new account, and we stop billing you. Die mit dem Konto verknüpfte E-Mail-Adresse wird für die Nutzung mit einem anderen {% data variables.product.product_name %}-Konto frei. {% endif %}
+{% if currentVersion == "free-pro-team@latest" %} Außerdem steht der Name Deines Kontos wieder für andere Benutzer zur Verfügung, und Deine Abrechnung wird beendet. Die mit dem Konto verknüpfte E-Mail-Adresse wird für die Nutzung mit einem anderen {% data variables.product.product_name %}-Konto frei. {% endif %}
 
 Wenn Du der alleinige Inhaber einer Organisation bist, musst Du die Inhaberschaft auf eine andere Person übertragen oder die Organisation löschen, bevor Du Dein Benutzerkonto löschen kannst. Wenn es noch weitere Inhaber Deiner Organisation gibt, musst Du Dich selbst aus der Organisation löschen, bevor Du Dein Benutzerkonto löschen kannst.
 
@@ -40,7 +40,7 @@ Bevor Du Dein Benutzerkonto löschst, erstelle Kopien aller Repositorys, private
     - Wenn Du der alleinige Inhaber einer Organisation bist, musst Du die Inhaberschaft auf eine andere Person übertragen oder die Organisation löschen.
     - Wenn es andere Inhaber der Organisation gibt, musst Du Dich selbst aus der Organisation entfernen. ![Schaltfläche zum Löschen des Kontos](/assets/images/help/settings/settings-account-delete.png)
 4. Fülle das Dialogfeld „Are you sure you want to do this?“ (Möchtest Du das wirklich tun?) aus, um zu bestätigen, dass Du die Folgen der Kontolöschung verstanden hast: ![Dialogfeld zum Bestätigen der Kontolöschung](/assets/images/help/settings/settings-account-deleteconfirm.png)
-  {% if currentVersion == "free-pro-team@latest" %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, your billing will end, and your username will be available to anyone for use on {% data variables.product.product_name %}.
+  {% if currentVersion == "free-pro-team@latest" %}– Denke daran, dass alle Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten von Deinem Konto ebenfalls gelöscht werden, dass Deine Abrechnung beendet wird und Dein Benutzername wieder für die Verwendung auf {% data variables.product.product_name %} freigegeben wird.
   {% else %}– Denke daran, dass alle Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten von Deinem Konto ebenfalls gelöscht werden und Dein Benutzername wieder für die Verwendung auf {% data variables.product.product_name %} freigegeben wird.
   {% endif %}– Gib im ersten Feld Deinen {% data variables.product.product_name %}-Benutzernamen oder Deine E-Mail-Adresse ein.
     - Gib im zweiten Feld den Text von der Aufforderung ein.
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md
index 037f7a7fb3..34813ce66f 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Mitarbeiter zu einem persönlichen Repository einladen
-intro: 'You can {% if currentVersion == "free-pro-team@latest" %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+intro: 'Du kannst {% if currentVersion == "free-pro-team@latest" %}Benutzer als Mitarbeiter zu Deinem persönlichen Repository einladen{% else %}Benutzer als Mitarbeiter zu Deinem persönlichen Repository hinzufügen{% endif %}.'
 redirect_from:
   - /articles/how-do-i-add-a-collaborator/
   - /articles/adding-collaborators-to-a-personal-repository/
@@ -33,7 +33,7 @@ Repositorys, die einer Organisation gehören, können feiner abgestufte Zugriffs
 
 1. Frage nach dem Benutzernamen der Person, die Du als Mitarbeiter einlädst.
 
-{% if currentVersion == "free-pro-team@latest" %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %}
+{% if currentVersion == "free-pro-team@latest" %} Wenn die Person noch keinen Benutzernamen besitzt, kann sie sich für {% data variables.product.prodname_dotcom %} anmelden. Weitere Informationen findest Du unter „[Für ein neues {% data variables.product.prodname_dotcom %}-Konto anmelden](/articles/signing-up-for-a-new-github-account)“.{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% if currentVersion == "free-pro-team@latest" %}
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index f454edfcf7..e26f8666ad 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -1,23 +1,20 @@
 ---
 title: Managing your theme settings
-intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode.'
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
 versions:
   free-pro-team: '*'
 topics:
   - Accounts
 ---
 
-{% note %}
-
-**Note:** Theme settings is currently in beta and subject to change.
-
-{% endnote %}
-
-For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions.
+For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
 
 {% data reusables.user_settings.access_settings %}
 1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
-1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. Under "Theme mode", select the drop-down menu, then click a theme preference. ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Klicke auf das gewünschte Design.
+    - If you chose a single theme, click a theme. ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - If you chose to follow your system settings, click a day theme and a night theme. ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### Weiterführende Informationen
 
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
index b1db445cff..e84041e491 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
@@ -32,7 +32,7 @@ Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository.
 | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %}                                                                                                                  |                                                                                                                                                                                                                                                                                                                                |
 | „[Mitarbeiter in ein persönliches Repository einladen](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)“                                                            |                                                                                                                                                                                                                                                                                                                                |
 | Change the visibility of the repository                                                                                                                                                                                      | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %}
-| Limit interactions with the repository                                                                                                                                                                                       | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Limit interactions with the repository                                                                                                                                                                                       | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename a branch, including the default branch                                                                                                                                                                                | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Einen Pull Request auf einem geschützten Branch zusammenführen, selbst ohne genehmigende Reviews                                                                                                                             | „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches)“                                                                                                                                                                                                                         |
@@ -70,7 +70,7 @@ Collaborators can also perform the following actions.
 
 | Aktion                                                                                    | Weitere Informationen                                                                                                                                                                                                                                                                                    |
 |:----------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Fork the repository                                                                       | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Fork the repository                                                                       | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename a branch other than the default branch                                             | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                                                                |
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index 2d36d90e1d..a2bd64e63a 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ Beim Entfernen eines Mitarbeiters werden zwar dessen Forks privater Repositorys
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. To the right of the collaborator you want to remove, click
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
   ![Schaltfläche „Remove collaborator" (Entfernen des Mitarbeiters)](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. Klicke auf der linken Seitenleiste auf **Collaborators & teams** (Mitarbeiter und Teams). ![Registerkarte „Collaborators" (Mitarbeiter)](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md
index 2af8979100..f9dc56fb57 100644
--- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md
+++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md
@@ -25,7 +25,7 @@ topics:
 
 Für webbasierte Git-Operationen legst Du die E-Mail-Adresse für Commits auf {% data variables.product.product_name %} fest. Für Commits, die Du per Push über die Befehlszeile überträgst, legst Du die E-Mail-Adresse für Commits in Git fest.
 
-{% if currentVersion == "free-pro-team@latest" %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Alle Commits, die Du vor der Änderung Deiner Commit-E-Mail-Adresse durchgeführt hast, bleiben mit Deiner früheren E-Mail-Adresse verbunden.{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Alle Commits, die Sie vor der Änderung Ihrer E-Mail-Adresse für Commits durchgeführt haben, bleiben mit Ihrer früheren E-Mail-Adresse verbunden.{% else %}Nach der Änderung Ihrer E-Mail-Adresse für Commits auf {% data variables.product.product_name %} wird die neue E-Mail-Adresse standardmäßig allen zukünftigen webbasierten Git-Operationen zugeordnet. Alle Commits, die Du vor der Änderung Deiner Commit-E-Mail-Adresse durchgeführt hast, bleiben mit Deiner früheren E-Mail-Adresse verbunden.{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -37,7 +37,7 @@ Für webbasierte Git-Operationen legst Du die E-Mail-Adresse für Commits auf {%
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}If you'd like to keep your personal email address private, you can use a {% data variables.product.product_name %}-provided `no-reply` email address as your commit email address. Wenn Du eine `no-reply`-E-Mail-Adresse für Commits verwenden möchtest, die Du über die Befehlszeile überträgst, gib diese E-Mail-Adresse bei der Festlegung Deiner Commit-E-Mail-Adresse in Git an. Wenn Du eine `no-reply`-E-Mail-Adresse für webbasierte Git-Operationen verwenden möchtest, lege Deine Commit-E-Mail-Adresse auf GitHub fest, und wähle dabei **Keep my email address private** (E-Mail-Adresse privat halten) aus.
+{% if currentVersion == "free-pro-team@latest" %}Wenn Sie Ihre persönliche E-Mail-Adresse privat halten möchten, können Sie als Ihre E-Mail-Adresse für Commits eine von {% data variables.product.product_name %} bereitgestellte `no-reply`-E-Mail-Adresse verwenden. Wenn Du eine `no-reply`-E-Mail-Adresse für Commits verwenden möchtest, die Du über die Befehlszeile überträgst, gib diese E-Mail-Adresse bei der Festlegung Deiner Commit-E-Mail-Adresse in Git an. Wenn Du eine `no-reply`-E-Mail-Adresse für webbasierte Git-Operationen verwenden möchtest, lege Deine Commit-E-Mail-Adresse auf GitHub fest, und wähle dabei **Keep my email address private** (E-Mail-Adresse privat halten) aus.
 
 Du kannst auch festlegen, dass Commits, die Du über die Befehlszeile überträgst, blockiert werden, wenn diese Deine persönliche E-Mail-Adresse offenlegen. Weitere Informationen findest Du unter „[Pushes über die Befehlszeile blockieren, die Deine private E-Mail-Adresse offenlegen](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)“.{% endif %}
 
diff --git a/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md b/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md
index 98dfc810db..c92dda930e 100644
--- a/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,6 +9,8 @@ topics:
   - Legal
 ---
 
+_These terms apply to 1) GitHub.com (non-Enterprise) customers who have accepted the Corporate Terms of Service, and 2) Enterprise customers who licensed the Service prior to January 4, 2021. Enterprise customers who purchase Products or Services after that date are directed to https://github.com/enterprise-legal for current terms._
+
 VIELEN DANK, DASS SIE SICH FÜR GITHUB ENTSCHIEDEN HABEN, UM DIE ANFORDERUNGEN IHRES UNTERNEHMENS ZU ERFÜLLEN. BITTE LESEN SIE DIESE VEREINBARUNG SORGFÄLTIG DURCH; SIE REGELT DIE VERWENDUNG DER PRODUKTE (WIE UNTEN DEFINIERT), ES SEI DENN, GITHUB HAT ZU DIESEM ZWECK EINE SEPARATE SCHRIFTLICHE VEREINBARUNG MIT DEM KUNDEN ABGESCHLOSSEN. WENN DER KUNDE AUF „I AGREE“ („ICH STIMME ZU“) ODER EINE ÄHNLICHE SCHALTFLÄCHE KLICKT ODER EINES DER PRODUKTE VERWENDET, AKZEPTIERT ER ALLE GESCHÄFTSBEDINGUNGEN DIESER VEREINBARUNG. WENN DER KUNDE DIESE VEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON ABSCHLIESST, SICHERT ER ZU, DASS ER RECHTLICH DAZU BEFUGT IST, DIESE VEREINBARUNG FÜR DAS UNTERNEHMEN ODER DIE JURISTISCHE PERSON ZU SCHLIESSEN.
 
 ### Unternehmensnutzungsbedingungen für GitHub
@@ -24,7 +26,7 @@ Diese Vereinbarung gilt für die folgenden Angebote von GitHub, die nachfolgend
 
 Ein **„verbundenes Unternehmen“** ist ein Unternehmen, das direkt oder indirekt eine Partei kontrolliert, von einer Partei kontrolliert wird oder unter gemeinsamer Kontrolle mit einer Partei steht, wobei „Kontrolle“ über fünfzig Prozent (50 %) der Anteile oder Rechte zur Steuerung der Unternehmensführung bedeutet.
 
-**„Vereinbarung"** bedeutet zusammenfassend alle Bestimmungen, Bedingungen, Hinweise, die in diesem Dokument enthalten sind oder auf die darin verwiesen wird, sowie alle anderen Betriebsregeln, Richtlinien und Verfahren, die GitHub von Zeit zu Zeit auf dem Dienst veröffentlichen kann. Die Website-Richtlinien von GitHub sind unter [https://docs.github.com/categories/site-policy](/categories/site-policy) verfügbar.
+**„Vereinbarung"** bedeutet zusammenfassend alle Bestimmungen, Bedingungen, Hinweise, die in diesem Dokument enthalten sind oder auf die darin verwiesen wird, sowie alle anderen Betriebsregeln, Richtlinien und Verfahren, die GitHub von Zeit zu Zeit auf dem Dienst veröffentlichen kann. GitHub's site policies are available at [https://docs.github.com/categories/site-policy](/categories/site-policy).
 
 **„Alle Benutzer“** sind zusammenfassend die Benutzer des Kunden und externen Benutzer, die den Dienst nutzen.
 
diff --git a/translations/de-DE/content/github/site-policy/github-privacy-statement.md b/translations/de-DE/content/github/site-policy/github-privacy-statement.md
index 3feebcfc03..d7cd7fd2a6 100644
--- a/translations/de-DE/content/github/site-policy/github-privacy-statement.md
+++ b/translations/de-DE/content/github/site-policy/github-privacy-statement.md
@@ -64,7 +64,7 @@ Wir benötigen zum Zeitpunkt der Kontoerstellung bestimmte allgemeine Informatio
 ##### Payment information
 Wenn Sie sich bei uns bei einem kostenpflichtigen Konto anmelden, Geld über das GitHub-Sponsorenprogramm senden oder eine Anwendung im GitHub Marketplace kaufen, erfassen wir Ihren vollständigen Namen, Ihre Adresse und Kreditkarteninformationen oder PayPal-Informationen. Bitte beachten Sie, dass GitHub Ihre Kreditkarteninformationen oder PayPal-Informationen nicht verarbeitet oder speichert, aber unser Zahlungsabwickler von Drittanbietern dies tut.
 
-Wenn Sie eine Anwendung auf [GitHub Marketplace](https://github.com/marketplace) auflisten und verkaufen, benötigen wir Ihre Bankinformationen. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
+Wenn Sie eine Anwendung auf [GitHub Marketplace](https://github.com/marketplace) auflisten und verkaufen, benötigen wir Ihre Bankinformationen. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
 
 ##### Profile information
 Sie können uns weitere Informationen zu Ihrem Kontoprofil übermitteln, z. B. Ihren vollständigen Namen, einen Avatar mit einem Foto, Ihre Biographie, Ihren Standort, Ihr Unternehmen und eine URL zu einer Drittanbieter-Website. Diese Informationen können personenbezogene Benutzerdaten enthalten. Bitte beachten Sie, dass Ihre Profilinformationen für andere Benutzer unseres Dienstes sichtbar sein können.
diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md
index a65564f510..807f4d8d67 100644
--- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md
+++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md
@@ -12,7 +12,7 @@ topics:
   - Repositories
 ---
 
-A repository's graphs give you information on {% if currentVersion == "free-pro-team@latest" %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. Wenn Du ein Repository verwaltest, kannst Du diese Daten verwenden, um besser zu verstehen, wer Dein Repository verwendet und warum es verwendet wird.
+Die Diagramme eines Repositorys geben Dir Informationen über {% if currentVersion == "free-pro-team@latest" %}Traffic, vom Repository abhängige Projekte, {% endif %}Mitarbeiter und Commits des Repositorys sowie die Forks und das Netzwerk eines Repositorys. Wenn Du ein Repository verwaltest, kannst Du diese Daten verwenden, um besser zu verstehen, wer Dein Repository verwendet und warum es verwendet wird.
 
 {% if currentVersion == "free-pro-team@latest" %}
 
diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index f79f64937f..96bbf10111 100644
--- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -1,5 +1,5 @@
 ---
-title: About the dependency graph
+title: Informationen zum Abhängigkeitsdiagramm
 intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.'
 versions:
   enterprise-server: <=2.22
@@ -7,24 +7,19 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
+
 ### Dependency graph availability
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+The dependency graph is available for every repository that defines dependencies in a supported package ecosystem using a supported file format.
 
 {% data reusables.repositories.enable-security-alerts %}
 
-### About the dependency graph
+### Informationen zum Abhängigkeitsdiagramm
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
-
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
-
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated. For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
 
 ### Dependencies included
 
@@ -33,47 +28,41 @@ The dependency graph includes all the dependencies of a repository that are deta
 - Direct dependencies, that are explicitly defined in a manifest or lock file
 - Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
-
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+The dependency graph identifies indirect dependencies.
 
 ### Using the dependency graph
 
 You can use the dependency graph to:
 
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
+- Explore the repositories your code depends on. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."
+- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |
 
 ### Enabling the dependency graph
 
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository.
 
-### Supported package ecosystems
+### Unterstützte Paket-Ökosysteme
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.
 
-| Package manager | Languages | Recommended formats | All supported formats |
-| --- | --- | --- | ---|
-| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| 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.lock`, `setup.py`* |
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+The ecosystems listed below are supported for the dependency graph and {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
+
+| Paketmanager | Sprachen                        | Empfohlene Formate                                     | All supported formats                                                     |
+| ------------ | ------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
+| Composer     | PHP                             | `composer.lock`                                        | `composer.json`, `composer.lock`                                          |
+| `dotnet` CLI | .NET-Sprachen (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+| 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`*                |
+| RubyGems     | Ruby                            | `Gemfile.lock`                                         | `Gemfile.lock`, `Gemfile`, `*.gemspec`                                    |
+| Yarn         | JavaScript                      | `yarn.lock`                                            | `package.json`, `yarn.lock`                                               |
 
 {% note %}
 
@@ -81,10 +70,7 @@ The recommended formats explicitly define which versions are used for all direct
 
 {% endnote %}
 
-### Further reading
+### Weiterführende Informationen
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
index a090e233d3..aa4562affd 100644
--- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
+++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
@@ -1,6 +1,6 @@
 ---
 title: Auf grundlegende Daten des Repositorys zugreifen
-intro: 'You can view basic information about a repository, such as the repository''s activity{% if currentVersion == "free-pro-team@latest" %}, traffic,{% endif %} and contribution activity.'
+intro: 'Du kannst grundlegende Informationen über ein Repository anzeigen, beispielsweise über die Aktivität{% if currentVersion == "free-pro-team@latest" %}, den Datenverkehr{% endif %} und die Beitragsaktivitäten des Repositorys.'
 mapTopic: true
 redirect_from:
   - /articles/accessing-basic-repository-data
diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index d68c9e8c81..6275ba80b2 100644
--- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -7,29 +7,20 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
 
-The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+The dependency graph shows the dependencies of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. Optionally, under "Dependency graph", click **Dependents**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### Dependencies view
 
-{% if currentVersion == "free-pro-team@latest" %}
-Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies on public repositories hosted on
-{% data variables.product.product_name %}, you can also click a dependency to view the repository. Dependencies on private repositories, private packages, or unrecognized files are shown in plain text.
-
-If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}.
-
-![Abhängigkeitsdiagramm](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
 Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to
 {% data variables.product.prodname_dependabot_alerts %}.
@@ -57,59 +48,8 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### Dependents view
-
-For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
-
-![Abhängigkeitsdiagramm](/assets/images/help/graphs/dependents_graph.png)
-
-### Enabling and disabling the dependency graph for a private repository
-
-Repository administrators can enable or disable the dependency graph for private repositories.
-
-You can also enable or disable the dependency graph 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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
-
-### Changing the "Used by" package
-
-If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
-
-The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
-
-!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png)
-
-Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
-
-The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### Fehler beim Abhängigkeitsdiagramm beheben
 
 If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.
 
-{% if currentVersion == "free-pro-team@latest" %}
-If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a
-{% data variables.product.prodname_enterprise %} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %}
-
 If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.
-
-### Weiterführende Informationen
-
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- „[Einblicke für Ihre Organisation anzeigen ](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)“
-- „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“
-- „[Grundlegendes zur Verwendung und zum Schutz Ihrer Daten durch {% data variables.product.product_name %}](/github/understanding-how-github-uses-and-protects-your-data)“
-{% endif %}
diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
index 09c5cc365f..be6f83511b 100644
--- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
+++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
 ---
 title: Verbindungen zwischen Repositorys verstehen
-intro: 'You can better understand the connections that exist between repositories by viewing a repository''s network{% if currentVersion == "free-pro-team@latest" %}, projects that depend on the repository,{% endif %} and its forks.'
+intro: 'Die Verbindungen zwischen Repositorys kannst Du besser verstehen, wenn Du Dir das Netzwerk{% if currentVersion == "free-pro-team@latest" %}, die vom Repository abhängigen Projekte{% endif %} und die Repository-Forks ansiehst.'
 mapTopic: true
 redirect_from:
   - /articles/understanding-connections-between-repositories
diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
index 00309744e4..3a45744fc5 100644
--- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
+++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
@@ -1,6 +1,6 @@
 ---
 title: Mitwirkende eines Projekts anzeigen
-intro: 'You can see who contributed commits to a repository{% if currentVersion == "free-pro-team@latest" %} and its dependencies{% endif %}.'
+intro: 'Du kannst anzeigen, wer Commits zu einem Repository{% if currentVersion == "free-pro-team@latest" %} und seinen Abhängigkeiten{% endif %} beigetragen hat.'
 redirect_from:
   - /articles/i-don-t-see-myself-in-the-contributions-graph/
   - /articles/viewing-contribution-activity-in-a-repository/
@@ -16,7 +16,7 @@ topics:
 
 ### Informationen zu Mitarbeitern
 
-You can view the top 100 contributors to a repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, including commit co-authors,{% endif %} in the contributors graph. Merge- und leere Commits werden für dieses Diagramm nicht als Beiträge gezählt.
+Im Mitarbeiterdiagramm kannst Du die Top 100 der Mitarbeiter an einem Repository anzeigen{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, darunter auch die Commit-Co-Autoren{% endif %}. Merge- und leere Commits werden für dieses Diagramm nicht als Beiträge gezählt.
 
 {% if currentVersion == "free-pro-team@latest" %}
 Darüber hinaus kannst Du eine Liste der Personen anzeigen, die Beiträge zu den Python-Abhängigkeiten des Projekts geliefert haben. Rufe `https://github.com/REPO-OWNER/REPO-NAME/community_contributors` auf, um auf diese Liste der Community-Mitarbeiter zuzugreifen.
diff --git a/translations/de-DE/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/de-DE/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index 78b487fb09..dd97d2628a 100644
--- a/translations/de-DE/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/de-DE/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: Informationen zu GitHub Premium-Support für GitHub Enterprise Cloud
-intro: '{% data variables.contact.premium_support %} ist ein kostenpflichtiges, zusätzliches Supportangebot für {% data variables.product.prodname_ghe_cloud %}- und {% data variables.product.prodname_ghe_one %}-Kunden.'
+intro: '{% data variables.contact.premium_support %} ist ein kostenpflichtiges, ergänzendes Supportangebot für {% data variables.product.prodname_ghe_cloud %}-Kunden.'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
diff --git a/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md
index a51a002952..bbe150e5dd 100644
--- a/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/de-DE/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ Weitere Informationen zum Erstellen von Links findest Du unter „[Grundlegende
 
 ### Issues und Pull Requests
 
-In Unterhaltungen auf {% data variables.product.product_name %} werden Verweise auf Issues und Pull Requests automatisch in verkürzte Links umgewandelt. Weitere Informationen findest Du unter „[Informationen zu Unterhaltungen auf {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github).“
+In Unterhaltungen auf {% data variables.product.product_name %} werden Verweise auf Issues und Pull Requests automatisch in verkürzte Links umgewandelt.
 
 {% note %}
 
diff --git a/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index 9817fd4c08..7694aea0c3 100644
--- a/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/de-DE/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -23,7 +23,7 @@ Um eine Überschrift zu erstellen, füge bis zu sechs Rautenzeichen (`#`) vor de
 
 ### Textstil
 
-Um Text hervorzuheben, kannst Du die Fett- und/oder Kursivschrift verwenden oder den Text durchstreichen.
+You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files.
 
 | Stil                          | Syntax               | Tastenkürzel          | Beispiel                                 | Ausgabe                                |
 | ----------------------------- | -------------------- | --------------------- | ---------------------------------------- | -------------------------------------- |
@@ -205,6 +205,10 @@ Für URLs, die Teil eines Markdown-Links sind, werden keine Inhaltsanhänge ange
 
 For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."
 
+### Uploading assets
+
+You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and `.md` files in your repository.
+
 ### Emojis verwenden
 
 Du kannst Emojis einfügen, indem Du `:EMOJICODE:` eingeben.
@@ -223,7 +227,7 @@ Um einen neuen Absatz zu erstellen, lasse eine Zeile zwischen den Textzeilen lee
 
 ### Markdown-Formatierung ignorieren
 
-Sie können {% data variables.product.product_name %} anweisen, die Markdown-Formatierung zu ignorieren, indem Sie das Markdown-Zeichen mit `\` maskieren.
+Du kannst {% data variables.product.product_name %} anweisen, die Markdown-Formatierung zu ignorieren (oder zu verlassen), indem Du das Markdown-Zeichen mit `\` maskierst.
 
 `Wir benennen \*unser-neues-Projekt\* in \*unser-altes-Projekt\* um.`
 
diff --git a/translations/de-DE/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/de-DE/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index 659e1ea5b7..4881a8848f 100644
--- a/translations/de-DE/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/de-DE/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### Syntaxmarkierung
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 Du kannst einen optionalen Sprachkennzeichner hinzufügen, um die Syntaxmarkierung im Fenced-Code-Block zu aktivieren.
 
diff --git a/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 39c4ce7a00..b56f757233 100644
--- a/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ Return type fields:
 
 ## Suche
 
-Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see ["Queries](/graphql/reference/queries#searchresultitemconnection)."
+Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/de-DE/content/graphql/overview/breaking-changes.md b/translations/de-DE/content/graphql/overview/breaking-changes.md
index 60e198a093..30ae5ee702 100644
--- a/translations/de-DE/content/graphql/overview/breaking-changes.md
+++ b/translations/de-DE/content/graphql/overview/breaking-changes.md
@@ -27,7 +27,7 @@ We'll announce upcoming breaking changes at least three months before making cha
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> A change will be made to <code>{{ change.location }}</code>.
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> A change will be made to <code>{{ change.location }}</code>.
 
 <p><b>Description:</b> {{ change.description }}</p>
 
diff --git a/translations/de-DE/content/graphql/reference/input-objects.md b/translations/de-DE/content/graphql/reference/input-objects.md
index 944e9c0f8b..72fe36ae79 100644
--- a/translations/de-DE/content/graphql/reference/input-objects.md
+++ b/translations/de-DE/content/graphql/reference/input-objects.md
@@ -19,6 +19,5 @@ For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) tak
 
 For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index c788c97454..5c03956087 100644
--- a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: Metrics available with GitHub Insights
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %} includes a variety of metrics to give you visibility into your team''s software delivery process.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index 1d4e6eb413..aee7193685 100644
--- a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Navigating between GitHub Enterprise and GitHub Insights
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index b8f8cfd53d..7c5c5ea881 100644
--- a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Setting your timezone for GitHub Insights
 intro: 'You can set the timezone for metrics you view in {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
diff --git a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 27df3bdb64..9951fbc5fc 100644
--- a/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/de-DE/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing key metrics and reports
 intro: You can view and filter key metrics and reports to help you understand and improve your software delivery process through data.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index a02218c8c3..0279c695cd 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: About data in GitHub Insights
 intro: 'The data included in {% data variables.product.prodname_insights %} metrics is highly customizable.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index 4ec3f459a3..30badef36e 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: About GitHub Insights
 intro: '{% data variables.product.prodname_insights %} provides metrics and analytical reports to help engineering teams understand and improve their software delivery process.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
index ebe26c13c4..ffa93a5b0f 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring the connection between GitHub Insights and GitHub Enterprise
 intro: 'You can manage how {% data variables.product.prodname_insights %} connects to {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can configure the connection to {% data variables.product.prodname_enterprise %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index b679ad2a3e..32f989ca39 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Enabling a link between GitHub Insights and GitHub Enterprise
 intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index 1ce327eedd..7e752f195e 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Installing GitHub Insights
 intro: 'You can install {% data variables.product.prodname_insights %} and connect the standalone application to {% data variables.product.prodname_ghe_server %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index f6344ccd82..b2deeb9d34 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Managing available metrics and reports
 intro: 'You can enable and disable specific metrics across {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
index d0a6b12541..ed70f39c30 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
@@ -1,7 +1,6 @@
 ---
 title: Managing contributors and teams
 intro: You can manage the people and teams included in metrics and reports.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage contributors and teams.'
@@ -98,7 +97,7 @@ You can create and manage custom teams in {% data variables.product.prodname_ins
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.teams-tab %}
 {% data reusables.github-insights.edit-team %}
-3. To the right of the contributor you'd like to remove, click {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Trashcan button](/assets/images/help/insights/contributor-trashcan.png)
+3. To the right of the contributor you'd like to remove, click {% octicon "trash" aria-label="The trash icon" %}. ![trash button](/assets/images/help/insights/contributor-trashcan.png)
 
 #### Renaming a custom team
 
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-events.md
index a429ba8329..885f0cd123 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-events.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-events.md
@@ -1,7 +1,6 @@
 ---
 title: Managing events
 intro: '{% data reusables.github-insights.events %}'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-events
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage events.'
@@ -29,5 +28,5 @@ After you create an event in {% data variables.product.prodname_insights %}, any
 
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.events-tab %}
-3. To the right of the event you want to delete, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Trash can button](/assets/images/help/insights/trashcan-button.png)
+3. To the right of the event you want to delete, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Trash can button](/assets/images/help/insights/trashcan-button.png)
 4. Click **Confirm**.
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-goals.md
index 9fd0da88d9..df94d64d05 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: Managing goals
 intro: You can use goals to set targets for key metrics and measure success reaching those targets.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 0a1b9fbca6..41f64500c2 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -1,7 +1,6 @@
 ---
 title: Managing organizations
 intro: 'You can manage the {% data variables.product.prodname_enterprise %} organizations that are included in metrics.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index f747452514..8bf8c4d001 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Managing permissions in GitHub Insights
 intro: 'You can update a user''s permissions in {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-repositories.md
index d9e469675c..0e50e97474 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-repositories.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/managing-repositories.md
@@ -1,7 +1,6 @@
 ---
 title: Managing repositories
 intro: 'You can manage the repositories connected to {% data variables.product.prodname_insights %} and the data included in metrics for each repository.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-repositories
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories. '
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index f130f5aa02..d562649d01 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: System overview for GitHub Insights
 intro: '{% data variables.product.prodname_insights %} is a standalone application which interfaces with {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/de-DE/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/de-DE/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index ac825bff24..59a162aabd 100644
--- a/translations/de-DE/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/de-DE/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Updating GitHub Insights
 intro: 'You can update to the latest version of {% data variables.product.prodname_insights %} to benefit from improvements and bug fixes.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index e10332c408..c91db65e99 100644
--- a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md
index 5692509d77..4ef75af740 100644
--- a/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -43,7 +43,7 @@ For more information, see {% if currentVersion == "free-pro-team@latest" or curr
 
 ### Weiterführende Informationen
 
-- „[Informationen zu Unterhaltungen auf {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)“
+- "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
 - „[Informationen zu Teams](/articles/about-teams)“
 - „[Eine Teamdiskussion erstellen](/organizations/collaborating-with-your-team/creating-a-team-discussion)“
 - „[Eine Teamdiskussion bearbeiten oder löschen](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)“
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md
index e8478952b0..4bebc818ee 100644
--- a/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
 {% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index 63de6350de..c1522a31c0 100644
--- a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -26,9 +26,8 @@ Du kannst erlaubte IP-Adressen auch für die Organisationen in einem Enterprise-
 
 ### Eine zulässige IP-Adresse hinzufügen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ Du kannst erlaubte IP-Adressen auch für die Organisationen in einem Enterprise-
 
 ### Zulässige IP-Adressen aktivieren
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. Wähle unter „IP allow list“ (Liste der zulässigen IP-Adressen) **Enable IP allow list** (Liste der zulässigen IP-Adressen aktivieren) aus. ![Kontrollkästchen, um IP-Adressen zuzulassen](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. Klicke auf **Save** (Speichern).
 
 ### Eine zulässige IP-Adresse bearbeiten
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ Du kannst erlaubte IP-Adressen auch für die Organisationen in einem Enterprise-
 
 ### Eine zulässige IP-Adresse löschen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index 6cdada88ce..6e0585de37 100644
--- a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### Displaying the security and analysis settings
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
@@ -50,33 +49,38 @@ You can enable or disable features for all repositories. {% if currentVersion ==
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
 2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. Optionally, enable the feature by default for new repositories in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Enable by default" option for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -85,11 +89,14 @@ You can enable or disable features for all repositories. {% if currentVersion ==
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
 2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -122,7 +129,7 @@ To allow {% data variables.product.prodname_dependabot %} to access a private {%
 You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
-1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. The size of your license is shown for organization-level licenses. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
+1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}.
 1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}.
 
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index 2135c6286b..bf437c8041 100644
--- a/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ Before you require use of two-factor authentication, we recommend notifying {% i
 
 ### Zwei-Faktor-Authentifizierung in Deiner Organisation erzwingen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..e4442f2627
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About email restrictions
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. Weitere Informationen zu den Berechtigungen externer Mitarbeiter findest Du unter „[Berechtigungsebenen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators).“
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index d06756f2de..b531e300b6 100644
--- a/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 The audit log lists events triggered by activities that affect your organization within the last 90 days. Nur Organisationsinhaber können auf das Auditprotokoll einer Organisation zugreifen.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
 
 ### Auditprotokoll durchsuchen
@@ -36,6 +35,7 @@ Zur Suche nach bestimmten Ereignissen verwende in Deiner Abfrage den Qualifizier
 | [`Konto`](#account-category-actions)                                                                                                                                                                                                                                                                                                                                        | Contains all activities related to your organization account.                                                                                                                                                                                                                                                                                                                                                 |
 | [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                                                                                                                                                                      | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."                                                                        |
 | [`Abrechnung`](#billing-category-actions)                                                                                                                                                                                                                                                                                                                                   | Contains all activities related to your organization's billing.                                                                                                                                                                                                                                                                                                                                               |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                                                                                                                | Contains all activities related to your organization's codespaces.                                                                                                                                                                                                                                                                                                                                            |
 | [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                                                                                                                  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |                                                                                                      |
 | [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                                                                                                                                                              | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization.                                                                                                                                                                                                                                             |
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                                                                                                              | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."                                                      |
@@ -191,6 +191,20 @@ An overview of some of the most common actions that are recorded as events in th
 | `change_billing_type` | Wird ausgelöst, wenn Deine Organisation ihre [Zahlungsmethode für {% data variables.product.prodname_dotcom %} ändert](/articles/adding-or-editing-a-payment-method). |
 | `change_email`        | Wird ausgelöst, wenn Ihre Organisation ihre [E-Mail-Adresse für Abrechnungen](/articles/setting-your-billing-email) ändert.                                           |
 
+#### `codespaces` category actions
+
+| Aktion                       | Beschreibung                                                                                                                                                                                                                                   |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                     | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                   |
+| `resume`                     | Triggered when a user resumes a suspended codespace.                                                                                                                                                                                           |
+| `delete`                     | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                   |
+| `create_an_org_secret`       | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)  |
+| `update_an_org_secret`       | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `remove_an_org_secret`       | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+
+
+
 #### `dependabot_alerts` category actions
 
 | Aktion         | Beschreibung                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -370,8 +384,8 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `remove_member`                                                                                                                          | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Wird auch ausgelöst, wenn ein [Organisationsmitglied sich selbst aus einer Organisation entfernt](/articles/removing-yourself-from-an-organization/). |
 | `remove_outside_collaborator`                                                                                                            | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | `remove_self_hosted_runner`                                                                                                              | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)."                                                                                                                                                                                                                                                                                                          |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
-| `revoke_external_identity`                                                                                                               | Wird ausgelöst, wenn ein Organisationsinhaber die verknüpfte Identität eines Mitarbeiters widerruft. Weitere Informationen findest Du unter „[SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)"                                                                                                                        |
-| `revoke_sso_session`                                                                                                                     | Wird ausgelöst, wenn ein Organisationsinhaber die SAML-Sitzung eines Mitglieds widerruft. Weitere Informationen findest Du unter „[SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)"                                                                                                                                   |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `revoke_external_identity`                                                                                                               | Wird ausgelöst, wenn ein Organisationsinhaber die verknüpfte Identität eines Mitarbeiters widerruft. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."                                                                                                                                             |
+| `revoke_sso_session`                                                                                                                     | Wird ausgelöst, wenn ein Organisationsinhaber die SAML-Sitzung eines Mitglieds widerruft. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."                                                                                                                                                        |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | `runner_group_created`                                                                                                                   | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."                                                                                                                                                                                                                                           |
 | `runner_group_removed`                                                                                                                   | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."                                                                                                                                                                                                                                                                                   |
 | `runner_group_updated`                                                                                                                   | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."                                                                                                                                                                                                                    |
@@ -391,11 +405,11 @@ For more information, see "[Managing the publication of {% data variables.produc
 {% if currentVersion == "free-pro-team@latest" %}
 #### `org_credential_authorization` category actions
 
-| Aktion         | Beschreibung                                                                                                                                                                                                                  |
-| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `grant`        | Wird ausgelöst, wenn ein Mitglied [Anmeldeinformationen zur Verwendung mit SAML Single Sign-On](/github/authenticating-to-github/authenticating-with-saml-single-sign-on) autorisiert.                                        |
-| `deauthorized` | Wird ausgelöst, wenn ein Mitglied [die Autorisierung von Anmeldeinformationen zur Verwendung mit SAML Single Sign-On zurückzieht](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                  |
-| `revoke`       | Wird ausgelöst, wenn ein Inhaber [autorisierte Anmeldeinformationen widerruft](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). |
+| Aktion         | Beschreibung                                                                                                                                                                                                 |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `grant`        | Wird ausgelöst, wenn ein Mitglied [Anmeldeinformationen zur Verwendung mit SAML Single Sign-On](/github/authenticating-to-github/authenticating-with-saml-single-sign-on) autorisiert.                       |
+| `deauthorized` | Wird ausgelöst, wenn ein Mitglied [die Autorisierung von Anmeldeinformationen zur Verwendung mit SAML Single Sign-On zurückzieht](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). |
+| `revoke`       | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization).      |
 
 {% endif %}
 
@@ -484,6 +498,38 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_linear_history_requirement_enforcement_level` | Wird ausgelöst, wenn der erforderliche lineare Commit-Verlauf für einen geschützten Branch aktiviert oder deaktiviert wird.                                                                                                            |
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `pull_request` category actions
+
+| Aktion                  | Beschreibung                                                                                               |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `create`                | Triggered when a pull request is created.                                                                  |
+| `close (schließen)`     | Triggered when a pull request is closed without being merged.                                              |
+| `reopen`                | Triggered when a pull request is reopened after previously being closed.                                   |
+| `Merge`                 | Triggered when a pull request is merged.                                                                   |
+| `indirect_merge`        | Triggered when a pull request is considered merged because its commits were merged into the target branch. |
+| `ready_for_review`      | Triggered when a pull request is marked as ready for review.                                               |
+| `converted_to_draft`    | Triggered when a pull request is converted to a draft.                                                     |
+| `create_review_request` | Triggered when a review is requested.                                                                      |
+| `remove_review_request` | Triggered when a review request is removed.                                                                |
+
+#### `pull_request_review` category actions
+
+| Aktion      | Beschreibung                          |
+| ----------- | ------------------------------------- |
+| `absenden`  | Triggered when a review is submitted. |
+| `verwerfen` | Triggered when a review is dismissed. |
+| `delete`    | Triggered when a review is deleted.   |
+
+#### `pull_request_review_comment` category actions
+
+| Aktion          | Beschreibung                                |
+| --------------- | ------------------------------------------- |
+| `create`        | Triggered when a review comment is added.   |
+| `aktualisieren` | Triggered when a review comment is changed. |
+| `delete`        | Triggered when a review comment is deleted. |
+{% endif %}
+
 #### `repo` category actions
 
 | Aktion                                | Beschreibung                                                                                                                                                                                                                                                                                                                                       |
@@ -501,7 +547,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `config.unlock_anonymous_git_access`  | Wird ausgelöst, wenn für ein Repository die [Einstellungssperre für den anonymen Git-Lesezugriff aufgehoben](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access) wird.{% endif %}
 | `create`                              | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | `create_actions_secret`               | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %}
-| `destroy`                             | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %}
+| `destroy`                             | Wird ausgelöst, wenn ein [Repository gelöscht](/articles/deleting-a-repository) wird.{% if currentVersion == "free-pro-team@latest" %}
 | `deaktivieren`                        | Wird ausgelöst, wenn ein Repository deaktiviert wird (z. B. aufgrund [unzureichender Deckung](/articles/unlocking-a-locked-account)).{% endif %}
 | `aktivieren`                          | Triggered when a repository is reenabled.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | `remove_actions_secret`               | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}
@@ -593,22 +639,24 @@ For more information, see "[Managing the publication of {% data variables.produc
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` category actions
 
-| Aktion                                         | Beschreibung                                                                                                                                                                                                                                                                                                             |
-| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`              | Wird ausgelöst, wenn Du eine Sponsorenschaltfläche in Deinem Repository aktivierst oder deaktivierst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“)                                                                                           |
-| `repo_funding_links_file_action`               | Wird ausgelöst, wenn Du die FUNDING-Datei in Deinem Repository änderst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“)                                                                                                                         |
-| `sponsor_sponsorship_cancel`                   | Wird ausgelöst, wenn Sie ein Sponsoring beenden (siehe „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                                                                                                                 |
-| `sponsor_sponsorship_create`                   | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                           |
-| `sponsor_sponsorship_preference_change`        | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/articles/managing-your-sponsorship)")                                                                                                                                                            |
-| `sponsor_sponsorship_tier_change`              | Wird ausgelöst, wenn Sie Ihr Sponsoring upgraden oder herabstufen (siehe „[Sponsoring upgraden](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                                |
-| `sponsored_developer_approve`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
-| `sponsored_developer_create`                   | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
-| `sponsored_developer_profile_update`           | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
-| `sponsored_developer_request_approval`         | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
-| `sponsored_developer_tier_description_update`  | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
-| sponsored_developer_update_newsletter_send | Wird ausgelöst, wenn Sie Ihren Sponsoren eine E-Mail-Aktualisierung senden (siehe „[Sponsoren kontaktieren](/articles/contacting-your-sponsors)“).                                                                                                                                                                       |
-| `waitlist_invite_sponsored_developer`          | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
-| `waitlist_join`                                | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
+| Aktion                                        | Beschreibung                                                                                                                                                                                                                                                                                                    |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                |
+| `repo_funding_links_file_action`              | Wird ausgelöst, wenn Du die FUNDING-Datei in Deinem Repository änderst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“)                                                                                                                |
+| `sponsor_sponsorship_cancel`                  | Wird ausgelöst, wenn Sie ein Sponsoring beenden (siehe „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                                                                                                        |
+| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                               |
+| `sponsor_sponsorship_tier_change`             | Wird ausgelöst, wenn Sie Ihr Sponsoring upgraden oder herabstufen (siehe „[Sponsoring upgraden](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“).                                                                                                       |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
+| `sponsored_developer_disable`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled                                                                                                                                                                                                                          |
+| `sponsored_developer_redraft`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
+| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                                  |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
 {% endif %}
 
 #### `team` category actions
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index f1a5bca3a7..273e02c133 100644
--- a/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -14,9 +14,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Klicke in der linken Seitenleiste auf **Installed {% data variables.product.prodname_github_app %}s** (Installierte Apps). ![Registerkarte „Installed {% data variables.product.prodname_github_app %}s“ (Installierte Apps) in der Seitenleiste mit den Organisationseinstellungen](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. Klicke neben der {% data variables.product.prodname_github_app %}, die Du überprüfen möchtest, auf **Configure** (Konfigurieren). ![Schaltfläche „Configure“ (Konfigurieren)](/assets/images/help/organizations/configure-installed-integration-button.png)
 6. Überprüfe die Berechtigungen und den Repository-Zugriff der {% data variables.product.prodname_github_app %}s. ![Option zur Festlegung des Zugriffs der {% data variables.product.prodname_github_app %} auf alle oder ausgewählte Repositorys](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index a42c55f485..e9ea95d48f 100644
--- a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ Weitere Informationen zu den Berechtigungen für {% data variables.product.prodn
 
 ### Jemandem die Berechtigung zur Verwaltung aller {% data variables.product.prodname_github_app %}s der Organisation erteilen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Gib unter „Management“ (Verwaltung) den Benutzernamen der Person ein, die Du als {% data variables.product.prodname_github_app %}-Manager in der Organisation festlegen möchtest. Klicke anschließend auf **Grant** (Erteilen). ![Einen {% data variables.product.prodname_github_app %}-Manager hinzufügen](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### Jemandem die Berechtigung zur Verwaltung einer einzelnen {% data variables.product.prodname_github_app %} erteilen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Klicken Sie unter „{% data variables.product.prodname_github_app %}s“ auf den Avatar der App, zu der Sie einen {% data variables.product.prodname_github_app %}-Manager hinzufügen möchten. ![{% data variables.product.prodname_github_app %} auswählen](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index bab9ce8b39..8587b53306 100644
--- a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ Weitere Informationen zu den Berechtigungen für {% data variables.product.prodn
 
 ### Berechtigungen eines {% data variables.product.prodname_github_app %}-Managers für die gesamte Organisation entfernen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Suche unter „Management“ (Verwaltung) den Benutzernamen der Person, deren {% data variables.product.prodname_github_app %}-Managerberechtigungen Du entziehen möchtest, und klicke auf **Revoke** (Entziehen). ![{% data variables.product.prodname_github_app %}-Managerberechtigungen entziehen](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### Berechtigungen eines {% data variables.product.prodname_github_app %}-Managers für eine einzelne {% data variables.product.prodname_github_app %} entfernen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Klicken Sie unter „{% data variables.product.prodname_github_app %}s“ auf den Avatar der App, für die Sie einen {% data variables.product.prodname_github_app %}-Manager entfernen möchten. ![{% data variables.product.prodname_github_app %} auswählen](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index fbba79efd9..dc457a298a 100644
--- a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -49,4 +49,4 @@ Wenn der Zugriff eines Teams auf ein Projektboard von einem übergeordneten Team
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Klicke oberhalb der Unterhaltungen des Teams auf {% octicon "project" aria-label="The Projects icon" %} **Projects** (Projekte). ![Registerkarte mit Team-Repositorys](/assets/images/help/organizations/team-project-board-button.png)
-5. Um die Berechtigungsstufen für ein Projektboard anzupassen, benutze das Dropdownmenü rechts neben dem anzupassenden Projektboard. Um ein Projektboard zu entfernen, klicke **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Mülleimer-Schaltfläche zum Entfernen eines Projektboards aus dem Team](/assets/images/help/organizations/trash-button.png)
+5. Um die Berechtigungsstufen für ein Projektboard anzupassen, benutze das Dropdownmenü rechts neben dem anzupassenden Projektboard. Um ein Projektboard zu entfernen, klicke **{% octicon "trash" aria-label="The trash icon" %}**. ![Mülleimer-Schaltfläche zum Entfernen eines Projektboards aus dem Team](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index a6f343e991..9bc8c49dc2 100644
--- a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben
 | Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“)                                                                                                                                                                                                                                                    |                |          |           |          |                                                                       **X**                                                                        |
 | Ändern der Einstellungen eines Repositorys                                                                                                                                                                                                                                                                                                                                         |                |          |           |          |                                                                       **X**                                                                        |
 | Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository                                                                                                                                                                                                                                                                                                                     |                |          |           |          |                                                                       **X**                                                                        |
-| Bearbeiten des Standardbranch eines Repositorys                                                                                                                                                                                                                                                                                                                                    |                |          |           |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Bearbeiten des Standardbranch eines Repositorys                                                                                                                                                                                                                                                                                                                                    |                |          |           |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                                           |                |          |           |          |                                                                       **X**                                                                        |
 | Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                       |                |          |   **X**   |  **X**   |                                                                 **X** 
 {% endif %}
@@ -142,7 +142,8 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben
 | [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                         |                |  **X**   |   **X**   |  **X**   |                                                                       **X**                                                                        |
 | [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                          |                |  **X**   |   **X**   |  **X**   |                                                                       **X**                                                                        |
 | [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                       |     **X**      |  **X**   |   **X**   |  **X**   |                                                                       **X**                                                                        |
-| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                          |                |          |           |  **X**   |                                                                 **X** 
+| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                          |                |          |           |  **X**   |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                  |                |          |   **X**   |  **X**   |                                                                 **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ In this section, you can find the repository permission levels required for secu
 
 | Repository-Aktion                                                                                                                                                                                                                                                             | Read (Gelesen) | bewerten |      Schreiben      |      Betreuen       |                                                                           Verwalten                                                                           |
 |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                                                                             |                |          |                     |                     |                                                                                                                                                               |
-| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository                                                                           |                |          |                     |                     |                                                                             **X**                                                                             |
-| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                |                |          |                     |                     |                                                                             **X**                                                                             |
-| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies    |                |          |                     |                     |                                                                             **X**                                                                             |
-| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen                                                                                                                                                                   |                |          |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |                |          |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                                                                           |                |          |                     |                     |                                                                                                                                                               |
+| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository                                                                                |                |          |                     |                     |                                                                             **X**                                                                             |
+| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                     |                |          |                     |                     |                                                                             **X**                                                                             |
+| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies    |                |          |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| [Sicherheitshinweise](/code-security/security-advisories/about-github-security-advisories) erstellen                                                                                                                                                                          |                |          |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |                |          |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | [Aktivieren des Abhängigkeitsdiagramms](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) für ein privates Repository                                                                                                                          |                |          |                     |                     |                                                                             **X**                                                                             |
 | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                       |     **X**      |  **X**   |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                                                                         |     **X**      |  **X**   |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index 4af9a81546..677f737bde 100644
--- a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ Wenn jemand mit Administratorberechtigungen auf die Repositorys einer Organisati
 
 ### Basisberechtigungen festlegen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Wähle unter „Base permissions" (Basisberechtigungen) das Dropdownmenü, um neue Basisberechtigungen auszuwählen. ![Neue Berechtigungsstufe aus der Dropdownliste der Basisberechtigungen auswählen](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. Überprüfen Sie die Änderungen. Klicke zur Bestätigung auf **Change default permission to PERMISSION** (Ändere die Basisberechtigungen in BERECHTIGUNG). ![Überprüfen und Bestätigen der Änderung der Basisberechtigungen](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index f86bc5c8da..56c44ba77e 100644
--- a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -22,17 +22,15 @@ Du kannst festlegen, dass Mitglieder mithilfe der von Dir bereitgestellten SSH-Z
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### Eine SSH-Zertifizierungsstelle löschen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index a39024caae..61a4a27626 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -17,9 +17,8 @@ Standardmäßig können Issues in den Repositorys einer Organisation nicht gelö
 
 Nach der Aktivierung können Organisationsinhaber und Personen mit Administratorberechtigungen für ein Repository der Organisation Issues löschen. Zu den Personen mit Administratorberechtigungen für ein Repository gehören Organisationsmitglieder und externe Mitarbeiter mit Administratorberechtigungen. Weitere Informationen findest Du unter „[Repository-Berechtigungsebenen für eine Organisation](/articles/repository-permission-levels-for-an-organization/)“ und „[Einen Issue löschen](/articles/deleting-an-issue).“
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Wähle unter „Issue deletion“ (Issue-Löschung) die Option **Allow members to delete issues for this organization** (Mitgliedern das Löschen von Issues für diese Organisation erlauben) aus. ![Kontrollkästchen, um Personen das Löschen von Issues zu erlauben](/assets/images/help/settings/issue-deletion.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index cc681573e9..9d57738f60 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,9 +16,8 @@ Organisationsinhaber können Einschränkungen für die Anzeige der Abhängigkeit
 
 Enterprise-Inhaber können Einschränkungen für die Anzeige der Abhängigkeiten-Einblicke aller Organisationen im Enterprise-Konto festlegen. Weitere Informationen findest Du unter „[Eine Richtlinie für Abhängigkeiten-Einblicke in Deinem Enterprise-Konto erzwingen](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account).“
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Aktiviere oder deaktiviere unter „Member organization permissions“ (Berechtigungen für Organisationsmitglieder) die Option **Allow members to view dependency insights** (Mitgliedern die Anzeige von Abhängigkeiten-Einblicke erlauben). ![Kontrollkästchen, um Mitgliedern die Anzeige von Einblicken zu gestatten](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index e0e0996328..9f1536e3fa 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -28,7 +28,6 @@ Wenn Du eine Organisation gelöscht hast, kann GitHub **Deine Inhalte nicht wied
 
 ### 2. Lösche die Organisation
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Klicke fast am Ende der Seite mit den Einstellungen der Organisation auf **Delete this organization** (Diese Organisation löschen). ![Schaltfläche „Delete this organization“ (Diese Organisation löschen)](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index dedfb461a8..a2b8264fb0 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -27,9 +27,8 @@ Alternativ kannst Du {% data variables.product.prodname_actions %} für alle Rep
 
 ### {% data variables.product.prodname_actions %}-Berechtigungen für Deine Organisation verwalten
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Local and third-party Actions**, select an option. ![Aktiviere, deaktiviere oder limitiere die Aktionen für diese Organisation](/assets/images/help/repository/enable-org-actions.png)
 1. Klicke auf **Save** (Speichern).
@@ -50,9 +49,8 @@ You can disable all workflows for an organization or set a policy that configure
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Policies**, select an option. ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png)
 1. Klicke auf **Save** (Speichern).
@@ -61,9 +59,8 @@ You can disable all workflows for an organization or set a policy that configure
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. Klicke auf **Save** (Speichern).
@@ -77,9 +74,27 @@ You can disable all workflows for an organization or set a policy that configure
 
 #### Configuring the private fork policy for an organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your organization
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you choose the restricted option as the default in your organization settings, the same option is auto-selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and the more restricted default has been selected in the enterprise settings, you won't be able to choose the more permissive default in your organization settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. Click **Save** to apply the settings.
+{% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/index.md b/translations/de-DE/content/organizations/managing-organization-settings/index.md
index 377ea5d808..cb5ff1760e 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/index.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/index.md
@@ -13,7 +13,7 @@ topics:
   - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index 2398ddfff2..d093941942 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ Standardkennzeichnungen sind in jedem neuen Repository Deiner Organisation beinh
 
 ### Eine Standardkennzeichnung erstellen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ Standardkennzeichnungen sind in jedem neuen Repository Deiner Organisation beinh
 
 ### Eine Standardkennzeichnung bearbeiten
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ Standardkennzeichnungen sind in jedem neuen Repository Deiner Organisation beinh
 
 ### Eine Standardkennzeichnung löschen
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 93b37b2356..dee6f62c53 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. Klicke auf **Save** (Speichern). !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index 163f663f81..ac787c3b68 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ Organisationsinhaber können Erinnerungen für eines oder mehrere Teams in ihrer
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### Eine geplante Erinnerung für eine Organisation erstellen
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ Organisationsinhaber können Erinnerungen für eines oder mehrere Teams in ihrer
 {% data reusables.reminders.create-reminder %}
 
 ### Geplante Erinnerungen für eine Organisation verwalten
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ Organisationsinhaber können Erinnerungen für eines oder mehrere Teams in ihrer
 {% data reusables.reminders.update-buttons %}
 
 ### Geplante Erinnerungen für eine Organisation löschen
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index 8d8160a0a5..2e955eb304 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ If an enterprise owner has enforced a policy for the default branch name for you
 
 ### Setting the default branch name
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. Under "Repository default branch", click **Change default branch name now**. ![Override button](/assets/images/help/organizations/repo-default-name-button.png)
 4. Type the default name that you would like to use for new branches. ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 02ab203eb8..7ab82a72bc 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -20,9 +20,8 @@ Organisationsinhaber können die Anzeige der Mitgliedsnamen in einer Organisatio
 
 Jedes Organisationsmitglied kann seinen eigenen Profilnamen in seinen Einstellungen wählen. Weitere Informationen findest Du unter „[Dein Profil personalisieren](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name).“
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Aktiviere oder deaktiviere unter „Admin repository permissions“ (Repository-Administratorberechtigungen) die Option **Allow members to see comment author's profile name in private repositories** (Mitgliedern erlauben, den Profilnamen des Kommentarverfassers in privaten Repositorys anzuzeigen). ![Kontrollkästchen zum Festlegen, dass Mitglieder den vollständigen Namen des Kommentarverfassers in privaten Repositorys anzeigen können](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index a09c01c4a4..af8b808c9b 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ If you allow forking of private{% if currentVersion == "free-pro-team@latest" or
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Wähle unter „Repository forking" (Forken eines Repositorys) die Option **Allow forking of private repositories** (das Forken von privaten Repositorys zulassen) oder die Option **Allow forking of private and internal repositories** (Forking von privaten und internen Repositorys zulassen). ![Kontrollkästchen, um das Forking in der Organisation zu erlauben oder zu verbieten](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
index 86cc2113da..ed4ef07488 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -21,9 +21,8 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
 
 If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
 1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
 1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index 16279cb86d..df27fee3c2 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates.
 
-You can also disable updates from accounts your organization sponsors. Weitere Informationen finden Sie unter „[Sponsoring verwalten](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)“.
+You can also disable updates from accounts your organization sponsors. Weitere Informationen finden Sie unter „[Sponsoring verwalten](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)“.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. Klicke auf **Update profile** (Profil aktualisieren). ![Schaltfläche „Update profile" (Aktualisieren des Profils)](/assets/images/help/organizations/update-profile-button.png)
 
 ### Weiterführende Informationen
 
-- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)"
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md
index e1717b709c..18c83a94c7 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -40,9 +40,8 @@ Nach der Änderung Deines Organisationsnamens können folgende Probleme auftrete
 
 ### Namen Deiner Organisation ändern
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Klicke nahe am Ende der Einstellungsseite unter „Rename organization“ (Organisation umbenennen) auf **Rename Organization** (Organisation umbenennen). ![Schaltfläche „Rename Organization“ (Organisation umbenennen)](/assets/images/help/settings/settings-rename-organization.png)
 
 ### Weiterführende Informationen
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index 4d344a024b..104e15f028 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -27,9 +27,8 @@ Organisationsinhaber können immer jede Art von Repository erstellen.
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository creation", select one or more options. ![Optionen für die Repository-Erstellung](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index ade7e254c4..2d35b6c1f9 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ You can restrict the ability to change repository visibility to organization own
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Deaktiviere unter „Repository visibility change“ (Änderung der Sichtbarkeit von Repositorys) das Kontrollkästchen **Allow members to change repository visibilities for this organization** (Mitgliedern die Änderung der Sichtbarkeit von Repositorys für diese Organisation erlauben). ![Kontrollkästchen zur Erlaubnis der Änderung der Sichtbarkeit von Repositorys durch Mitglieder](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index 5720912439..2935248ffe 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -19,9 +19,8 @@ Organisationsinhaber und Mitglieder mit Administratorberechtigungen für ein Rep
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 62b4264f4d..ef5b2fb253 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -16,9 +16,8 @@ topics:
 
 Inhaber können die Berechtigungen zum Löschen oder Übertragen von Repositorys innerhalb einer Organisation festlegen.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Aktiviere oder deaktiviere unter „Repository deletion and transfer“ (Löschen und Übertragen von Repositorys) das Kontrollkästchen **Allow members to delete or transfer repositories for this organization** (Mitgliedern das Löschen oder Übertragen von Repositorys für diese Organisation erlauben). ![Kontrollkästchen zur Erlaubnis des Löschens von Repositorys durch Mitglieder](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index ffc8dfbc83..7ad0c623af 100644
--- a/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -17,9 +17,8 @@ Organisationsinhaber können die Berechtigungen für die Teamerstellung festlege
 
 Wenn Du keine Berechtigungen für die Teamerstellung festlegst, dürfen standardmäßig alle Organisationsmitglieder Teams erstellen.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Aktiviere oder deaktiviere unter „Team creation rules“ (Regeln für die Teamerstellung) das Kontrollkästchen **Allow members to create teams** (Mitgliedern die Erstellung von Teams erlauben). ![Kontrollkästchen zur Erlaubnis der Teamerstellung durch Mitglieder](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..56443c85b3
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About domain verification
+
+Nachdem Du die Inhaberschaft der Domains Deiner Organisation verifiziert hast, wird im Profil der Organisation der Badge „Verified“ (Verifiziert) angezeigt. Wenn Ihre Organisation in {% data variables.product.prodname_ghe_cloud %} vorhanden ist und den Unternehmensnutzungsbedingungen zugestimmt hat, können Organisationsinhaber die Identität der Organisationsmitglieder verifizieren, indem sie die E-Mail-Adresse der jeweiligen Mitglieder in der verifizierten Domain anzeigen. Weitere Informationen findest Du unter „[Informationen zum Profil Deiner Organisation](/articles/about-your-organization-s-profile/)“ und „[Auf Unternehmensnutzungsbedingungen umsteigen](/articles/upgrading-to-the-corporate-terms-of-service).“
+
+If your organization is owned by an enterprise account, a "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+Auf {% data variables.product.prodname_ghe_cloud %} können Sie nach dem Verifizieren der Inhaberschaft der Domain Ihrer Organisation E-Mail-Benachrichtigungen für die Organisation auf diese Domain beschränken. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. In der Befehlsausgabe sollte Ihr neuer TXT-Eintrag aufgelistet werden.
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. Sobald der Badge „Verified“ (Verifiziert) auf der Profilseite Ihrer Organisation sichtbar ist, können Sie den TXT-Eintrag im Domain-Hosting-Dienst optional aus dem DNS-Eintrag löschen.![Badge „Verified“ (Verifiziert)](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index 7ae90d7b0c..9e823eaefd 100644
--- a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ Abrechnungsmanager können **nicht**
 
 Der eingeladene Benutzer erhält eine Einladungs-E-Mail, in der er darum gebeten wird, Abrechnungsmanager für Deine Organisation zu werden. Wenn der eingeladene Benutzer in der E-Mail auf den Link zum Annehmen der Einladung klickt, wird er automatisch als Abrechnungsmanager zur Organisation hinzugefügt. Wenn er noch kein GitHub-Konto besitzt, wird er auf eine Seite umgeleitet, auf der er ein Konto erstellen kann. Nach der Erstellung des Kontos wird er automatisch als Abrechnungsmanager zur Organisation hinzugefügt.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Klicke neben den Abrechnungsmanagern auf **Add a billing manager** (Einen Abrechnungsmanager hinzufügen). ![Abrechnungsmanager einladen](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![Abrechnungsmanager einladen](/assets/images/help/billing/settings_billing_managers_list.png)
 6. Gib den Benutzernamen oder die E-Mail-Adresse des Benutzers ein, den Du hinzufügen möchtest, und klicke auf **Send invitation** (Einladung versenden). ![Seite zum Einladen eines Abrechnungsmanagers](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index e311e2ebd5..febe7f8a71 100644
--- a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -23,6 +23,12 @@ topics:
 
 Organisationsinhaber haben vollen administrativen Zugriff auf die Organisation. {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**Note**: As an organization owner, you can change the role of other organization members and owners. You can't change your own role.
+
+{% endnote %}
+
 ### Einen Organisationsinhaber ernennen
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index df8bd604ca..51e50eff2e 100644
--- a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
 | Auf das Auditprotokoll der Organisation zugreifen                                                                                                                                                                                                                                                                                                               |  **X**  |            |                    |
 | Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“)                                                                                                                                                                                                                |  **X**  |            |                    |
 | Die Domänen der Organisation überprüfen (siehe „[Domänen Deiner Organisation überprüfen](/articles/verifying-your-organization-s-domain)“)                                                                                                                                                                                                                      |  **X**  |            |                    |
-| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" for details)                                                                                                                             |  **X**  |            |                    |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)                                                                                                                 |  **X**  |            |                    |
 | **Alle Teams** löschen                                                                                                                                                                                                                                                                                                                                          |  **X**  |            |                    |
 | Das Organisationskonto einschließlich aller Repositorys löschen                                                                                                                                                                                                                                                                                                 |  **X**  |            |                    |
 | Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“)                                                                                                                                                                                             |  **X**  |   **X**    |                    |
@@ -60,9 +60,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
 | Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“)                                                                                                                                                                          |  **X**  |            |                    |
 | Die Anzeige von Einblicken zu den Abhängigkeiten einer Organisation verwalten (siehe „[Die Sichtbarkeit der Einblicke zu den Abhängigkeiten Ihrer Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“)                                                                                                           |  **X**  |            |                    |
 | Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“)                                                                                                                                                                                                                  |  **X**  |            |                    |
-| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details)                                                                                                                                    |  **X**  |   **X**    |                    |
+| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)" for details)                                                                                                                                                                                            |  **X**  |   **X**    |                    |
 | Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" for details)                                                                                                                         |  **X**  |            |                    |
-| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details )                                                                                                                       |  **X**  |            |                    |
+| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details )                                                                                                                                           |  **X**  |            |                    |
 | Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) |  **X**  |            |                    |
 | Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details)                                                                                                                        |  **X**  |            |                    |
 | [SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on) aktivieren und erzwingen                                                                                                                                                                                                                                         |  **X**  |            |                    |
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index 68d8c81936..c1be34de2e 100644
--- a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Klicke in der Liste der Abrechnungsmanager neben dem Namen der Person, die Du entfernen möchtest, auf {% octicon "x" aria-label="X symbol" %}. ![Abrechnungsmanager entfernen](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![Abrechnungsmanager entfernen](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index c3bb2daf2d..c55efaaeab 100644
--- a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 Wiederherstellungscode sollten nicht öffentlich gemacht und nicht weitergegeben werden. Wir empfehlen, sie mit einem Passwort-Manager wie [LastPass](https://lastpass.com/), [1Password](https://1password.com/) oder [Keeper](https://keepersecurity.com/) zu speichern.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Klicke im Hinweis zu Wiederherstellungscodes unter „SAML single sign-on“ (SAML Single Sign-On) auf **Save your recovery codes** (Deine Wiederherstellungscodes speichern). ![Link zum Anzeigen und Speichern Deiner Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_codes.png)
 6. Speichere Deine Wiederherstellungscodes, indem Du auf **Download** (Herunterladen), **Print** (Drucken) oder **Copy** (Kopieren) klickst. ![Schaltflächen zum Herunterladen, Drucken oder Kopieren Deiner Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index 3227681077..a6f1bc951a 100644
--- a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ Wenn Du SAML SSO aktivierst, aber nicht erzwingst, können Organisationsmitglied
 
 Bevor Du SAML SSO in Deiner Organisation erzwingst, stelle sicher, dass Du den Identitätsanbieter (IdP Identity Provider) eingerichtet hast. Weitere Informationen findest Du unter „[Auf die Erzwingung von SAML Single Sign-On in Deiner Organisation vorbereiten](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization).“
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Wähle unter „SAML single sign-on“ (SAML Single Sign-On) **Enable SAML authentication** (SAML-Authentifizierung aktivieren) aus. ![Kontrollkästchen zum Aktivieren von SAML SSO](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index 528f79a0ee..2c5b0776a5 100644
--- a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ Du musst Dich für Deine Organisation mittels SAML SSO und dem unterstützten Id
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ Du musst Dich für Deine Organisation mittels SAML SSO und dem unterstützten Id
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ Du musst Dich für Deine Organisation mittels SAML SSO und dem unterstützten Id
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Klicke unter „Team synchronization“ (Teamsynchronisierung) auf **Disable team synchronization** (Teamsynchronisierung deaktivieren). ![Deaktivieren der Teamsynchronisierung](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index 996d7a0f8d..9da69bb9d2 100644
--- a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -29,9 +29,8 @@ Weitere Informationen finden Sie unter„[Berechtigungsebenen für die Repositor
 
 ### Alle früheren Administratorenteams der Organisation migrieren
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Überprüfe die früheren Administratorenteams Deiner Organisation, und klicke dann auf **Migrate all teams** (Alle Teams migrieren). ![Schaltfläche „Migrate all teams" (Migration aller Teams)](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. Lies die Informationen zu den Änderungen, die sich für die Berechtigungen der Mitglieder dieser Teams möglicherweise ergeben, und klicke dann auf **Migrate all teams** (Alle Teams migrieren). ![Schaltfläche „Confirm migration" (Migration bestätigen)](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index 4e4a9faf83..b7078a9397 100644
--- a/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -15,9 +15,8 @@ topics:
 
 {% data reusables.organizations.team-discussions-default %} Weitere Informationen zu Teamdiskussionen findest Du unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).“
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. Hebe unter „Team discussions“ (Teamdiskussionen) die Auswahl von **Enable team discussions for this organization** (Teamdiskussionen für diese Organisation aktivieren) auf. ![Kontrollkästchen zum Aktivieren oder Deaktivieren von Teamdiskussionen für eine Organisation](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index bf71eaca5d..1d0938d894 100644
--- a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 Wenn Einschränkungen für den {% data variables.product.prodname_oauth_app %}-Zugriff aktiviert sind, müssen Organisationsmitglieder [die Genehmigung von einem Organisationsinhaber anfordern](/articles/requesting-organization-approval-for-oauth-apps), bevor sie eine {% data variables.product.prodname_oauth_app %} autorisieren können, die Zugriff auf die Ressourcen der Organisation hat.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Klicke neben der Anwendung, die Du genehmigen möchtest, auf **Review** (Review). ![Link zum Anfordern eines Reviews](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. Wenn Du die Informationen zur angeforderten Anwendung überprüft hast, klicke auf **Grant access** (Zugriff gewähren). ![Schaltfläche „Grant access“ (Zugriff gewähren)](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index 1ee86fb3d7..f3b6c0af21 100644
--- a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -12,9 +12,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Klicken Sie neben der Anwendung, die Sie deaktivieren möchten, auf {% octicon "pencil" aria-label="The edit icon" %}. ![Symbol für Bearbeiten](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. Klicke auf **Deny access** (Zugriff verweigern). ![Schaltfläche „Deny confirmation" (Bestätigen der Verweigerung)](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index f37811956e..239edee456 100644
--- a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Klicke auf **Remove restrictions** (Einschränkungen entfernen). ![Schaltfläche „Remove restrictions“ (Beschränkungen entfernen)](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. Wenn Du die Informationen zum Deaktivieren der Beschränkungen von Drittanbieter-Anwendungen gelesen hast, klicke auf **Yes, remove application restrictions** (Ja, Anwendungsbeschränkungen entfernen). ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index 53e9d22196..213f7ad063 100644
--- a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Klicke unter „Third-party application access policy“ (Zugriffsrichtlinie für Drittanbieter-Anwendungen) auf **Setup application access restrictions** (Zugriffsbeschränkungen für Anwendungen einrichten). ![Schaltfläche „Set up restrictions" (Einrichten von Beschränkungen)](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. Wenn Du die Informationen zu Drittanbieter-Zugriffsbeschränkungen gelesen hast, klicke auf **Restrict third-party application access** (Zugriff von Drittanbieter-Anwendungen beschränken). ![Schaltfläche „Restriction confirmation" (Beschränkungen bestätigen)](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/de-DE/content/packages/index.md b/translations/de-DE/content/packages/index.md
index 0d7b1e5e13..5f693358ee 100644
--- a/translations/de-DE/content/packages/index.md
+++ b/translations/de-DE/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..e735bf683b
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,85 @@
+---
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### About scopes and permissions for package registries
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+Ein Beispiel:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted.{% elsif currentVersion == "github-ae@latest" %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+
+| Scope                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Beschreibung                                                                      | Required permission |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------- |
+| `read:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Download and install packages from {% data variables.product.prodname_registry %} | Lesen               |
+| `write:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Upload and publish packages to {% data variables.product.prodname_registry %}     | schreiben           |
+| `delete:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                                   |                     |
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Delete packages from {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} |                                                                                   |                     |
+| verwalten                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |                                                                                   |                     |
+| `repo`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Upload and delete packages (along with `write:packages`, or `delete:packages`)    | write or admin      |
+
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..26b5e55a8a
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: Configuring a package's access control and visibility
+intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### Configuring access to container images for your personal account
+
+If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users will automatically be given access and don't need to accept an invitation first.
+
+### Configuring access to container images for an organization
+
+If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users or teams will automatically be given access and don't need to accept an invitation first.
+
+### Inheriting access for a container image from a repository
+
+To simplify package management through {% data variables.product.prodname_actions %} workflows, you can enable a container image to inherit the access permissions of a repository by default.
+
+If you inherit the access permissions of the repository where your package's workflows are stored, then you can adjust access to your package through the repository's permissions.
+
+Once a repository is synced, you can't access the package's granular access settings. To customize the package's permissions through the granular package access settings, you must remove the synced repository first.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. Under "Repository source", select **Inherit access from repository (recommended)**. ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### Ensuring workflow access to your package
+
+To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored.
+
+The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package.
+
+{% note %}
+
+**Note:** Syncing your container image with a repository through the **Actions access** menu option is different than connecting your container to a repository. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+#### {% data variables.product.prodname_actions %} access for user-account-owned container images
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+#### {% data variables.product.prodname_actions %} access for organization-owned container images
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like repository members to have to your container image. Outside collaborators will not be included. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for an organization](#configuring-access-to-container-images-for-an-organization)."
+
+### Configuring visibility of container images for your personal account
+
+When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
+
+### Container creation visibility for organization members
+
+You can choose the visibility of containers that organization members can publish by default.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, click **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images.
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, click **Internal**. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### Configuring visibility of container images for an organization
+
+When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..384fa27a00
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+### Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to a container image using the command line
+
+1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details:
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile:
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository.
+
+2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`.
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. Optionally, review details for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Tag your Docker image with your desired image name and hosting destination.
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  Ein Beispiel:
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  Ein Beispiel:
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/de-DE/content/packages/learn-github-packages/index.md b/translations/de-DE/content/packages/learn-github-packages/index.md
index c30d5e485e..01dcc26748 100644
--- a/translations/de-DE/content/packages/learn-github-packages/index.md
+++ b/translations/de-DE/content/packages/learn-github-packages/index.md
@@ -1,7 +1,7 @@
 ---
 title: Learn GitHub Packages
 shortTitle: Learn GitHub Packages
-intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.'
+intro: 'You can find out more about using packages in GitHub, including publishing new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
   - /github/managing-packages-with-github-packages/publishing-and-managing-packages
@@ -17,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md b/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..874b239fe9
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: Ein Paket installieren
+intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About package installation
+
+You can search {% data variables.product.prodname_dotcom %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)."
+
+After you find a package, you can read the package's description and installation and usage instructions on the package page.
+
+### Ein Paket installieren
+
+You can install a package from {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+
+1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. Install the package using the instructions for your package client.
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..34fc1ca794
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,133 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately {% if currentVersion == "github-ae@latest" %} for specified users or internally for your enterprise{% else %}or publicly{% endif %} and use packages as dependencies in your projects.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Informationen zu {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} is a package hosting service, fully integrated with {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% if currentVersion != "github-ae@latest" %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
+
+You can integrate {% data variables.product.prodname_registry %} with {% data variables.product.product_name %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. Weitere Informationen findest Du unter „[Anzeigen von Paketen](/packages/manage-packages/viewing-packages)."
+
+#### Overview of package permissions and visibility
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| Permissions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                  |
+| {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |                                                                  |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| Visibility                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | {% data reusables.package_registry.public-or-private-packages %}
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Informationen zur Abrechnung für {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+{% endif %}
+
+### Unterstützte Clients und Formate
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
+#### Support for package registries
+
+| Sprache    | Beschreibung                                           | Paketformat                            | Paketclient  |
+| ---------- | ------------------------------------------------------ | -------------------------------------- | ------------ |
+| JavaScript | Node package manager                                   | `package.json`                         | `npm`        |
+| Ruby       | RubyGems package manager                               | `Gemfile`                              | `gem`        |
+| Java       | Apache Maven project management and comprehension tool | `pom.xml`                              | `mvn`        |
+| Java       | Gradle-Tool für die Build-Automatisierung für Java     | `build.gradle` oder `build.gradle.kts` | `gradle`     |
+| .NET       | NuGet-Paketmanagement für .NET                         | `nupkg`                                | `dotnet` CLI |
+| N/A        | Docker container management                            | `Dockerfile`                           | `Docker`     |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**Note:** Docker is not supported when subdomain isolation is disabled.
+
+{% endnote %}
+
+For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)."
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Managing packages
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. Or for repo-scoped packages, you can delete a version of a private package using GraphQL.
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
+
+### Support kontaktieren
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use the [feedback form for {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages).
+
+Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if:
+
+* You experience anything that contradicts the documentation
+* You encounter vague or unclear errors
+* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information
+
+{% else %}
+If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators.
+
+{% endif %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md b/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md
index e0823dbc02..20c84228d0 100644
--- a/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md
+++ b/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md
@@ -19,7 +19,7 @@ versions:
 
 You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. GitHub provides metadata for each version, such as the publication date, download activity, and recent versions. Eine Beispiel für eine Paketseite findest Du unter [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
 
-{% data reusables.package_registry.public-or-private-packages %} A repository can contain more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
 
 {% if currentVersion == "free-pro-team@latest" %}
 If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository.
@@ -30,10 +30,10 @@ If a new version of a package fixes a security vulnerability, you should publish
 
 You can publish a package to {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
 
-1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 2. Authenticate to {% data variables.product.prodname_registry %} using your access token and the instructions for your package client.
 3. Publish the package using the instructions for your package client.
 
-For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)."
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
 
-Nachdem Du ein Paket veröffentlicht hast, kannst Du das Paket auf {% data variables.product.prodname_dotcom %} ansehen. For more information, see “[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages).”
+Nachdem Du ein Paket veröffentlicht hast, kannst Du das Paket auf {% data variables.product.prodname_dotcom %} ansehen. Weitere Informationen findest Du unter „[Anzeigen von Paketen](/packages/learn-github-packages/viewing-packages)."
diff --git a/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md b/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..3ef8e5c14e
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: Pakete anzeigen
+intro: 'Du kannst Details zu Paketen sehen, die in einem Repository veröffentlicht wurden, und die Ergebnisse nach Organisation oder Benutzer einschränken.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Pakete eines Repository einsehen
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### Pakete eines Repository einsehen
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Pakete einer Organisation einsehen
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. Klicke unter Deinem Organisationsnamen auf {% octicon "package" aria-label="The package icon" %} **Packages** (Pakete).
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Deine Pakete einsehen
+
+You can find and view any package you've published across all organizations and repositories.
+
+{% data reusables.profile.access_profile %}
+2. Klicke oben auf der Profilseite in der Hauptnavigation auf **Packages** (Pakete). ![Registerkarte „Projects“ (Projekte)](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Weiterführende Informationen
+
+- "[Suche nach Paketen](/github/searching-for-information-on-github/searching-for-packages)"
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..db022b22ec
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: About GitHub Packages and GitHub Actions
+intro: Learn the fundamentals of managing packages through your {% data variables.product.prodname_actions %} workflows.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..714a7a0a81
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: Example workflows for publishing a package
+intro: 'To help you get started with your own custom workflows, review some example workflows for publishing packages.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+You can find example workflows in "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
+
+  - [Node.js-Pakete veröffentlichen](/actions/guides/publishing-nodejs-packages)
+  - [Docker-Images veröffentlichen](/actions/guides/publishing-docker-images)
+  - [Java-Pakete mit Maven veröffentlichen](/actions/guides/publishing-java-packages-with-maven)
+  - [Java-Pakete mit Gradle veröffentlichen](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..790a661916
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: Managing GitHub packages using GitHub Actions workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'You can safely publish and consume packages by building custom workflows that can also build, test, and deploy your code.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..a370519036
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,455 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)."
+
+{% endif %}
+
+#### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+### About permissions and package access for repository-owned packages
+
+{% note %}
+
+**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.
+
+{% endnote %}
+
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
+
+{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About permissions and package access for {% data variables.product.prodname_container_registry %}
+
+The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions.
+
+All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+### Default permissions and access settings for containers modified through workflows
+
+When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
+
+For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
+- The container inherits the visibility and permissions model of the repository where the workflow is run.
+- Repository admins where the workflow is run become the admins of the container once the container is created.
+
+These are more examples of how default permissions work for workflows that manage packages.
+
+| {% data variables.product.prodname_actions %} workflow task | Default permissions and access |
+|----|----|
+| Download an existing container | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br>
+| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.
+| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.
+
+You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publishing a package using an action
+
+You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}:
+
+- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  The relevant settings are explained in the following table:
+
+  <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configures the <code>Create and publish a package</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    This job installs NPM and uses it to build the app.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Creates a new step called <code>Build container image</code>. This step runs as part of the <code>build-and-push-image</code> job. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sends the required parameters to the <code>build-push-action</code> action. This are defined in the subsequent lines.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the password that is used to access {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace <code>YOUR-HOSTNAME</code> with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use <code>ghcr.io</code> as the hostname.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines which repository will host the resulting package, and sets the name of the published package. Replace <code>octo-image</code> with the name you want for your package.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the first seven characters of the commit's SHA. For example, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the git ref. This can be the name of the branch used to create the package.
+  </td>
+  </tr>
+  </table>
+
+- This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
+- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
+
+
+### Installing a package using an action
+
+You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Upgrading a workflow that accesses `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**.
+  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add.
+   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image.
+  ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/content/packages/quickstart.md b/translations/de-DE/content/packages/quickstart.md
index d0986179c4..41b8f7fa3b 100644
--- a/translations/de-DE/content/packages/quickstart.md
+++ b/translations/de-DE/content/packages/quickstart.md
@@ -71,7 +71,10 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -91,11 +94,11 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
     ```
 9.  The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}.
 
-    To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)."
+    To test this out, navigate to the **Code** tab in your repository and create a new release. Weitere Informationen findest Du unter „[Releases in einem Repository verwalten](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)."
 
 ### Viewing your published package
 
-Packages are published at the repository level. You can see all the packages in a repository and search for a specific package.
+You can view all of the packages you have published.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ Packages are published at the repository level. You can see all the packages in
 
 ### Installing a published package
 
-Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)."
+Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
 
 ### Nächste Schritte:
 
-The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
+The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
 
 Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
 
 - "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages
 - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions
-- "[Guides](/packages/guides)" for specific uses cases and examples
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..3397c52972
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: Enabling improved container support with the Container registry
+intro: 'To use the {% data variables.product.prodname_container_registry %}, you must enable it for your user or organization account.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)."
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your personal account
+
+Once the {% data variables.product.prodname_container_registry %} is enabled for your personal user account, you can publish containers to the {% data variables.product.prodname_container_registry %} owned by your user account.
+
+To use the {% data variables.product.prodname_container_registry %} within an organization, the organization owner must enable the feature for organization members.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png)
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your organization account
+
+Before organization owners or members can publish container images to the {% data variables.product.prodname_container_registry %}, an organization owner must enable the feature preview for the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, select **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, select **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, select **Internal**. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..0b0c88e718
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with a GitHub Packages registry
+shortTitle: Working with a GitHub Packages registry
+intro: 'Learn how to use a supported {% data variables.product.prodname_registry %} registry.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### Inhaltsverzeichnis
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..a1941d9324
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,124 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- Store container images within your organization and user account, rather than a repository.
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- Access public container images anonymously.
+
+|                   | Docker registry                                                                                                                                                                                                                                         | {% data variables.product.prodname_container_registry %}
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Hosting locations | You can host multiple Docker images in one repository.                                                                                                                                                                                                  | You can host multiple container images in one organization or user account.                                                                                                            |
+| Permissions       | Each image inherits the permissions of the repository where the image is hosted. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. |
+ Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access    | N/A | You can access public container images anonymously. Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### Billing changes
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. For more information, see "[About  billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+### Domain changes
+
+The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`.
+
+| Registry                                                       | Example URL                                         |
+| -------------------------------------------------------------- | --------------------------------------------------- |
+| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` |
+| {% data variables.product.prodname_container_registry %}     | `ghcr.io/OWNER/IMAGE_NAME`                          |
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}.
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Migrating a Docker image using the Docker CLI
+
+To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine.
+
+1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward.
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization.
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name.
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. Sign in to the new {% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### Updating your {% data variables.product.prodname_actions %} workflow
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers.
+
+1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)."
+
+2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`.
+
+3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und speichern](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)“.
+
+4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}.
+
+#### Example of updated workflow
+
+If part of your workflow accessed a Docker image hosted by the Docker registry like this:
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this:
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..171a135f0a
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Working with the Apache Maven registry
+intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist.
+
+In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token.
+
+In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag.
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### Ein Paket veröffentlichen
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`.
+
+If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `<distributionManagement>` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository.
+
+For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+
+1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+
+  If your instance has subdomain isolation enabled:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. Publish the package.
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Ein Paket installieren
+
+To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package.
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. Installieren Sie das Paket.
+
+  ```shell
+  $ mvn install
+  ```
+
+### Weiterführende Informationen
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..9a377b6213
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://ghcr.io`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About {% data variables.product.prodname_container_registry %} support
+
+To push and pull container images, an organization admin or the owner of a personal account must enable the {% data variables.product.prodname_container_registry %}. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+When installing or publishing a Docker image, the Container registry supports foreign layers, such as Windows images.
+
+The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
+
+* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Pushing container images
+
+This example pushes the latest version of `IMAGE-NAME`.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+This example pushes the `2.5` version of the image.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+### Pulling container images
+
+#### Pull by digest
+
+To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
+
+1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. Remove image locally as needed.
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME.latest
+  ```
+
+3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### Pull by name
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### Pull by name and version
+
+Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### Pull by name and latest version
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### Building container images
+
+This example builds the `hello_docker` image:
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### Tagging container images
+
+1. Find the ID for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. Tag your Docker image using the image ID and your desired image name and hosting destination.
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..f23ca49b2c
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,262 @@
+---
+title: Working with the Docker registry
+intro: 'You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)."
+
+{% endif %}
+
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command.
+
+To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file.
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login docker.HOSTNAME -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation disabled:
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}.
+
+For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)."
+
+### Publishing an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**Note:** Image names must only use lowercase letters.
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} unterstützt mehrere Top-Level-Docker-Images pro Repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. Determine the image name and ID for your docker image using `docker images`.
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  If you haven't already built a docker image for the package, build the image, replacing <em x-id="3">OWNER</em> with the name of the user or organization account that owns the repository, <em x-id="3">REPOSITORY</em> with the name of the repository containing your project, <em x-id="3">IMAGE_NAME</em> with name of the package or image, <em x-id="3">VERSION</em> with package version at build time, and <em x-id="3">PATH</em> to the image if it isn't in the current working directory.
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. Publish the image to {% data variables.product.prodname_registry %}.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+  {% endnote %}
+
+#### Example publishing a Docker image
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+These examples assume your instance has subdomain isolation enabled.
+{% endif %}
+
+You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+You can publish a new Docker image for the first time and name it `monalisa`.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Pusht das Image zu {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### Downloading an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %} and *TAG_NAME* with tag for the image you want to install.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation disabled:
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+{% endnote %}
+
+### Weiterführende Informationen
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..ed0b284e71
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your personal access token. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+Replace *REGISTRY-URL* with the URL for your enterprise's Maven registry, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.
+{% endif %}
+
+Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+{% note %}
+
+**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)."
+
+{% endnote %}
+
+##### Example using Gradle Groovy for a single package in a repository
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### Example using Gradle Groovy for multiple packages in the same repository
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### Example using Kotlin DSL for a single package in the same repository
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### Example using Kotlin DSL for multiple packages in the same repository
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+  password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+  }
+  }
+  }
+  publications {
+  register<MavenPublication>("gpr") {
+  from(components["java"])
+  }
+  }
+  }
+  }
+```
+
+### Ein Paket veröffentlichen
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. After creating your package, you can publish the package.
+
+  ```shell
+   $ gradle publish
+  ```
+
+### Ein Paket installieren
+
+You can install a package by adding the package as a dependency to your project. Weitere Informationen finden Sie unter „[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)“ (Abhängigkeiten festlegen) in der Gradle-Dokumentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Grady Groovy:
+  ```shell
+  dependencies {
+  implementation 'com.example:package'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  dependencies {
+  implementation("com.example:package")
+  }
+  ```
+
+3. Add the maven plugin to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Grady Groovy:
+  ```shell
+  plugins {
+  id 'maven'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  plugins {
+  `maven`
+  }
+  ```
+
+  3. Installieren Sie das Paket.
+
+  ```shell
+  $ gradle install
+  ```
+
+### Weiterführende Informationen
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..6e51e863fe
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,218 @@
+---
+title: Working with the npm registry
+intro: 'Sie können NPM für die Veröffentlichung von Paketen auf {% data variables.product.prodname_registry %} und für die Nutzung von auf {% data variables.product.prodname_registry %} gespeicherten Paketen als Abhängigkeiten in einem NPM-Projekt konfigurieren.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Limits for published npm versions
+
+If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage.
+
+In the future, to improve performance of the service, you won't be able to publish more than 1,000 versions of a package on {% data variables.product.prodname_dotcom %}. Any versions published before hitting this limit will still be readable.
+
+If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
+
+{% endif %}
+
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token.
+
+To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+$ npm login --registry=https://npm.pkg.github.com
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address.
+
+If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### Ein Paket veröffentlichen
+
+{% note %}
+
+**Note:** Package names and scopes must only use lowercase letters.
+
+{% endnote %}
+
+By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. Ein Paket namens `@my-org/test` würde beispielsweise im Repository `my-org/test` auf {% data variables.product.prodname_dotcom %} veröffentlicht. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation.
+
+You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)."
+
+Die Scope-Zuordnung für Ihr Projekt können Sie entweder über die lokale *.npmrc*-Datei im Projekt oder die Option `publishConfig` in der Datei *package.json* festlegen. {% data variables.product.prodname_registry %} only supports scoped npm packages. Pakete mit Scopes weisen Namen im Format `@owner/name` auf. Pakete mit Scopes beginnen immer mit dem Symbol `@`. You may need to update the name in your *package.json* to use the scoped name. Beispiel: `"name": "@codertocat/hello-world-npm"`.
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### Publishing a package using a local *.npmrc* file
+
+You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Überprüfen Sie den Namen Ihres Pakets in der Datei *package.json* Ihres Projekts. Das Feld `name` (Name) muss den Scope und den Namen des Pakets enthalten. Wenn z. B. Ihr Paket „test“ heißt und Sie es in der {% data variables.product.prodname_dotcom %}-Organisation „My-org“ veröffentlichen möchten, muss das Feld `name` (Name) in der Datei *package.json* `@my-org/test` enthalten.
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### Publishing a package using `publishConfig` in the *package.json* file
+
+You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. Weitere Informationen finden Sie unter „[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)“ in der NPM-Dokumentation.
+
+1. Bearbeiten Sie die Datei *package.json* für Ihr Paket, und fügen Sie den Eintrag `publishConfig` hinzu.
+  {% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package.
+
+To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository.
+
+{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name.
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### Ein Paket installieren
+
+You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation.
+
+By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)."
+
+You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. Weitere Informationen finden Sie unter „[npm-scope](https://docs.npmjs.com/misc/scope) in der npm-Dokumentation.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency.
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. Installieren Sie das Paket.
+
+  ```shell
+  $ npm install
+  ```
+
+#### Pakete von anderen Organisationen installieren
+
+Standardmäßig können Sie nur {% data variables.product.prodname_registry %}-Pakete von einer Organisation verwenden. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### Using the official NPM registry
+
+{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
+{% endif %}
+
+### Weiterführende Informationen
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..9f35e85706
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,237 @@
+---
+title: Working with the NuGet registry
+intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client.
+
+You must replace:
+- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}.
+- `TOKEN` with your personal access token.
+- `OWNER` with the name of the user or organization account that owns the repository containing your project.{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %}If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://github.com/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+{% endif %}
+
+### Ein Paket veröffentlichen
+
+You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### Publishing a package using a GitHub PAT as your API key
+
+If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+1. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. Publish the package using your PAT as the API key.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### Publishing a package using a *nuget.config* file
+
+When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. Add your project's specific information to your project's file, which ends in *.csproj*.  You must replace:
+    - `OWNER` with the name of the user or organization account that owns the repository containing your project.
+    - `REPOSITORY` with the name of the repository containing the package you want to publish.
+    - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. Publish the package using the `key` you specified in the *nuget.config* file.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field.
+
+For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository:
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### Ein Paket installieren
+
+Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use:
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. Install the packages with the `restore` command.
+  ```shell
+  dotnet restore
+  ```
+
+### Problemlösungen
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### Weiterführende Informationen
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..d05eb5319b
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,151 @@
+---
+title: Working with the RubyGems registry
+intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Vorrausetzungen
+
+- You must have rubygems 2.4.1 or higher. To find your rubygems version:
+
+  ```shell
+  $ gem --version
+  ```
+
+  - You must have bundler 1.6.4 or higher. To find your Bundler version:
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - Install keycutter to manage multiple credentials. To install keycutter:
+  ```shell
+  $ gem install keycutter
+  ```
+
+### Bei {% data variables.product.prodname_registry %} authentifizieren
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the  *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems.
+
+To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your personal access token.  Create a new *~/.gem/credentials* file if this file doesn't exist.
+
+For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your personal access token.
+
+```shell
+gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" }
+```
+
+To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace:
+  - `USERNAME` with your {% data variables.product.prodname_dotcom %} username.
+  - `TOKEN` with your personal access token.
+  - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.
+{% endif %}
+
+If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example.
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### Ein Paket veröffentlichen
+
+{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. Weitere Informationen zum Erstellen einer Gem finden Sie unter „[Eine eigene Gem erstellen](http://guides.rubygems.org/make-your-own-gem/)“ in der RubyGems-Dokumentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Build the package from the *gemspec* to create the *.gem* package.
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### Publishing multiple packages to the same repository
+
+To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### Ein Paket installieren
+
+You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html).
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. Installieren Sie das Paket:
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### Weiterführende Informationen
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index b93bba8bb9..20c6e987d1 100644
--- a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -46,7 +46,7 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 4. Unter „Custom domain" (Benutzerdefinierte Domäne) gibst Du Deine benutzerdefinierte Domäne ein, dann klicke auf **Save** (Speichern). Dadurch wird eine Commit erzeugt, der eine _CNAME_-Datei im Stammverzeichnis Deiner Veröffentlichungsquelle hinzufügt. ![Schaltfläche „Save custom domain" (Speichere benutzerdefinierte Domäne)](/assets/images/help/pages/save-custom-subdomain.png)
 5. Navigiere zu Deinem DNS-Provider, und erstelle einen `CNAME` Datensatz, welcher Deine Subdomäne auf die Standarddomäne Deiner Website verweist. Soll beispielsweise die Subdomäne `www.example.com` für Deine Benutzer-Website verwendet werden, erstelle einen `CNAME`-Datensatz, mit dem `www.example.com` auf `<user>.github.io` verweist. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. Prüfe die korrekte Konfiguration des DNS-Datensatzes mit dem Befehl `dig`, und ersetze _WWW.EXAMPLE.COM_ dabei durch Deine Subdomäne.
 ```shell
@@ -79,7 +79,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. Prüfe die korrekte Konfiguration des DNS-Datensatzes mit dem Befehl `dig`, und ersetze _EXAMPLE.COM_ dabei durch Deine Apex-Domäne. Prüfe, ob die Ergebnisse mit den obigen IP-Adressen für {% data variables.product.prodname_pages %} übereinstimmen.
   ```shell
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md
index b07733fe0e..05ad95f489 100644
--- a/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -68,14 +68,6 @@ Unter welcher URL Ihre Website erreichbar ist, hängt davon ab, ob die Subdomain
 For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator.
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Repositories using the legacy `<username>.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://<username>.github.com` to `http(s)://<username>.github.io`. If both a `<username>.github.com` and `<username>.github.io` repository exist, only the `<username>.github.io` repository will be published.
-
-{% endnote %}
-{% endif %}
-
 ### Veröffentlichungsquellen für {% data variables.product.prodname_pages %}-Websites
 
 The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored.
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index 33ec0e444c..ce40506bea 100644
--- a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -87,7 +87,12 @@ Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website er
 10. Speichere und schließe das Gemfile.
 11. From the command line, run `bundle update`.
 11. Teste Deine Website optional lokal. Weitere Informationen findest Du unter „[Deine {% data variables.product.prodname_pages %}-Website lokal mit Jekyll testen](/articles/testing-your-github-pages-site-locally-with-jekyll).“
-12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md
index fee03c02d1..a17c7c0b99 100644
--- a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -225,7 +225,7 @@ Next, let's fetch our newly created repository:
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ A project the size of Rails has thousands of issues. We'll need to [paginate][pa
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ A big part of being a good API citizen is respecting rate limits by caching info
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ In addition to the JSON body, take note of the HTTP status code of `200` and the
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 The `304` status indicates that the resource hasn't changed since the last time we asked for it and the response will contain no body. As a bonus, `304` responses don't count against your [rate limit][rate-limiting].
diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md
index 8315a053f7..a87e65016c 100644
--- a/translations/de-DE/content/rest/overview/libraries.md
+++ b/translations/de-DE/content/rest/overview/libraries.md
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
diff --git a/translations/de-DE/content/rest/overview/media-types.md b/translations/de-DE/content/rest/overview/media-types.md
index 387e88954d..33a9eb3cfc 100644
--- a/translations/de-DE/content/rest/overview/media-types.md
+++ b/translations/de-DE/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ You can check the current version through every response's headers.  Look for th
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md
index 1c1785a94a..1d0a595752 100644
--- a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md
@@ -34,7 +34,7 @@ sent and received as JSON.
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: nginx
 > Date: Fri, 12 Oct 2012 23:33:14 GMT
 > Content-Type: application/json; charset=utf-8
@@ -126,7 +126,7 @@ Authenticating with invalid credentials will return `401 Unauthorized`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
-> HTTP/1.1 401 Unauthorized
+> HTTP/2 401
 
 > {
 >   "message": "Bad credentials",
@@ -139,7 +139,7 @@ After detecting several requests with invalid credentials within a short period,
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 -u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > {
 >   "message": "Maximum number of login attempts exceeded. Please try again later.",
 >   "documentation_url": "{% data variables.product.doc_url_pre %}"
@@ -181,7 +181,7 @@ There are three possible types of client errors on API calls that receive reques
 
 1. Sending invalid JSON will result in a `400 Bad Request` response.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 35
        
         {"message":"Problems parsing JSON"}
@@ -189,14 +189,14 @@ There are three possible types of client errors on API calls that receive reques
 2. Sending the wrong type of JSON values will result in a `400 Bad
 Request` response.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 40
        
         {"message":"Body should be a JSON object"}
 
 3. Sending invalid fields will result in a `422 Unprocessable Entity` response.
    
-        HTTP/1.1 422 Unprocessable Entity
+        HTTP/2 422
         Content-Length: 149
        
         {
@@ -328,7 +328,7 @@ The returned HTTP headers of any API request show your current rate limit status
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 56
@@ -351,7 +351,7 @@ new Date(1372700873 * 1000)
 If you exceed the rate limit, an error response returns:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 0
@@ -371,7 +371,7 @@ If your OAuth application needs to make unauthenticated calls with a higher rate
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 5000
 > X-RateLimit-Remaining: 4966
@@ -397,7 +397,7 @@ Abuse rate limits are not intended to interfere with legitimate use of the API.
 If your application triggers this rate limit, you'll receive an informative response:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Content-Type: application/json; charset=utf-8
 > Connection: close
 
@@ -450,7 +450,7 @@ Most responses return an `ETag` header. Many responses also return a `Last-Modif
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/user
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -460,7 +460,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -470,7 +470,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
@@ -487,7 +487,7 @@ Here's a sample request sent from a browser hitting `http://example.com`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
-HTTP/1.1 302 Found
+HTTP/2 302
 Access-Control-Allow-Origin: *
 Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
@@ -496,7 +496,7 @@ This is what the CORS preflight request looks like:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
-HTTP/1.1 204 No Content
+HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
diff --git a/translations/de-DE/content/rest/reference/activity.md b/translations/de-DE/content/rest/reference/activity.md
index d0593dd379..b273a738e4 100644
--- a/translations/de-DE/content/rest/reference/activity.md
+++ b/translations/de-DE/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ Events are optimized for polling with the "ETag" header. If no new events have b
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
 # The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ To get a feed in Atom format, you must specify the `application/atom+xml` type i
 #### Response
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ Notifications are optimized for polling with the `Last-Modified` header.  If the
 ``` shell
 # Add authentication to your requests
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
 # Pass the Last-Modified header exactly
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/de-DE/content/rest/reference/enterprise-admin.md b/translations/de-DE/content/rest/reference/enterprise-admin.md
index 6d88c24880..74467b7aaa 100644
--- a/translations/de-DE/content/rest/reference/enterprise-admin.md
+++ b/translations/de-DE/content/rest/reference/enterprise-admin.md
@@ -151,19 +151,6 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 {% endfor %}
 
 {% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
-
-## Encryption at rest
-
-You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## Admin stats
 
diff --git a/translations/de-DE/content/rest/reference/git.md b/translations/de-DE/content/rest/reference/git.md
index 722105c236..052bf87e08 100644
--- a/translations/de-DE/content/rest/reference/git.md
+++ b/translations/de-DE/content/rest/reference/git.md
@@ -19,7 +19,7 @@ The Git Database API gives you access to read and write raw Git objects to your
 
 ## Blobs
 
-A Git blob (binary large object) is the object type used to store the contents of each file in a repository. The file's SHA-1 hash is computed and stored in the blob object. These endpoints allow you to read and write [blob objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) to your Git database on {% data variables.product.product_name %}. Blobs leverage [these custom media types](#custom-media-types). You can read more about the use of media types in the API [here](/rest/overview/media-types).
+A Git blob (binary large object) is the object type used to store the contents of each file in a repository. The file's SHA-1 hash is computed and stored in the blob object. These endpoints allow you to read and write [blob objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) to your Git database on {% data variables.product.product_name %}. Blobs leverage [these custom media types](#custom-media-types-for-blobs). You can read more about the use of media types in the API [here](/rest/overview/media-types).
 
 ### Custom media types for blobs
 
diff --git a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md
index b4446c7dec..2bb31e6587 100644
--- a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md
@@ -120,6 +120,9 @@ _Suche_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _Suche_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -677,7 +683,10 @@ _Teams_
 - [`GET /repos/:owner/:repo/pages/builds`](/v3/repos/pages/#list-github-pages-builds) (:read)
 - [`POST /repos/:owner/:repo/pages/builds`](/v3/repos/pages/#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/v3/repos/pages/#get-github-pages-build) (:read)
-- [`GET /repos/:owner/:repo/pages/builds/latest`](/v3/repos/pages/#get-latest-pages-build) (:read)
+- [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### Permission on "pull requests"
 
@@ -767,6 +776,10 @@ _Reviews_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### Permission on "profile"
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### Permission on "repository hooks"
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
@@ -780,10 +793,10 @@ _Reviews_
 {% if enterpriseServerVersions contains currentVersion %}
 ### Permission on "repository pre receive hooks"
 
-- [`GET /repos/:owner/:repo/pre-receive-hooks`](/v3/enterprise-admin/repo_pre_receive_hooks/#list-pre-receive-hooks-for-a-repository) (:read)
-- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/v3/enterprise-admin/repo_pre_receive_hooks/#get-a-pre-receive-hook-for-a-repository) (:read)
-- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/v3/enterprise-admin/repo_pre_receive_hooks/#update-pre-receive-hook-enforcement-for-a-repository) (:write)
-- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/v3/enterprise-admin/repo_pre_receive_hooks/#remove-pre-receive-hook-enforcement-for-a-repository) (:write)
+- [`GET /repos/:owner/:repo/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) (:read)
+- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) (:read)
+- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) (:write)
+- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) (:write)
 {% endif %}
 
 ### Permission on "repository projects"
@@ -883,9 +896,9 @@ _Teams_
 
 ### Permission on "starring"
 
-- [`GET /user/starred/:owner/:repo`](/v3/activity/starring/#check-if-a-repository-is-starred-by-the-authenticated-user) (:read)
-- [`PUT /user/starred/:owner/:repo`](/v3/activity/starring/#star-a-repository-for-the-authenticated-user) (:write)
-- [`DELETE /user/starred/:owner/:repo`](/v3/activity/starring/#unstar-a-repository-for-the-authenticated-user) (:write)
+- [`GET /user/starred/:owner/:repo`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) (:read)
+- [`PUT /user/starred/:owner/:repo`](/rest/reference/activity#star-a-repository-for-the-authenticated-user) (:write)
+- [`DELETE /user/starred/:owner/:repo`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) (:write)
 
 ### Permission on "statuses"
 
diff --git a/translations/de-DE/content/rest/reference/repos.md b/translations/de-DE/content/rest/reference/repos.md
index 671c32ee95..42e1b34cf9 100644
--- a/translations/de-DE/content/rest/reference/repos.md
+++ b/translations/de-DE/content/rest/reference/repos.md
@@ -155,7 +155,8 @@ You can communicate that a transient environment no longer exists by setting its
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 ## Environments
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)."
+The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
diff --git a/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..34c91c4e85
--- /dev/null
+++ b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: Informationen zu GitHub Sponsors
+intro: 'Mit {% data variables.product.prodname_sponsors %} kann die Entwickler-Community die Personen und Organisationen, die wichtige Open-Source-Projekte entwerfen, entwickeln und verwalten, direkt auf {% data variables.product.product_name %} finanziell unterstützen.'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Informationen zu {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)“.
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+Wenn du ein unterstützter Entwickler oder eine unterstütze Organisation wirst, gelten zusätzliche Bedingungen für {% data variables.product.prodname_sponsors %}. Weitere Informationen findest Du unter „[GitHub Sponsors Zusätzliche Bedingungen](/github/site-policy/github-sponsors-additional-terms)."
+
+### Informationen zu {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**Note:** {% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+Der {% data variables.product.prodname_matching_fund %} zielt darauf ab, Mitgliedern der {% data variables.product.prodname_dotcom %}-Community zu helfen, die Open-Source-Software entwickeln, welche die [{% data variables.product.prodname_dotcom %}-Community-Richtlinien](/github/site-policy/github-community-guidelines) fördert. Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}.
+
+Um für {% data variables.product.prodname_matching_fund %} berechtigt zu sein, musst Du ein Profil erstellen, das eine Community anzieht, die Dich langfristig unterstützen wird. For more information about creating a strong profile, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."
+
+Donations between sponsored developers will not be matched.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### Feedback zu {% data variables.product.prodname_sponsors %} geben
+
+{% data reusables.sponsors.feedback %}
+
+### Weiterführende Informationen
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
+- „[Häufig gestellte Fragen mit dem {% data variables.product.prodname_sponsors %}-Team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)“ auf {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..70c2c8838c
--- /dev/null
+++ b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: Getting started with GitHub Sponsors
+intro: 'Erfahre mehr über {% data variables.product.prodname_sponsors %} und wie Du Dich als Sponsor oder Open-Source-Mitwirkender einbringen kannst.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..becea06b3b
--- /dev/null
+++ b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: Quickstart for finding contributors to sponsor
+intro: Learn some best practices for finding open source contributors to sponsor.
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### Explore projects you depend on
+
+As you consider where to find open source contributors to sponsor, consider starting at https://github.com/sponsors/community.
+
+If you're logged in, the sponsors results will start with public dependencies that your repositories depend on.
+
+![The Babel open source project with highlighted text that says "4 of your repositories depend on this"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+You can also toggle which of your accounts to view results for and further filter or search.
+
+![Search options on sponsors community search page](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### Explore whom others sponsor
+
+You can see whom a user or organization sponsors on their {% data variables.product.prodname_dotcom %} profile page.
+
+### Consider how you benefit from different contributions
+
+Consider whether you benefit from the work of open source contributions, such as:
+ - Dokumentation
+ - Design
+ - Translation
+ - Newsletters
+ - Code reviews
+ - Anleitungen
+ - Mentoring
+ - Triaging issues and helping with project management
+ - Answering questions
+ - Event planning
+
+For more information on different types of open source contributions, see the [Open source guide](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+You can check if contributors you've benefited from have {% data variables.product.prodname_sponsors %} profiles by using search at https://github.com/sponsors/community.
+
+### Search for a specific project or contributor
+
+At https://github.com/sponsors/community, you can search by ecosystem, most used, recently updated, and more. You can filter search results for your personal user account or for organizations that you're a member of.
+
+### Nächste Schritte:
+
+For more information on starting your sponsorship, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
diff --git a/translations/de-DE/content/sponsors/guides.md b/translations/de-DE/content/sponsors/guides.md
new file mode 100644
index 0000000000..d23fd3e78b
--- /dev/null
+++ b/translations/de-DE/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Sponsors guides
+shortTitle: Leitfäden
+intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/de-DE/content/sponsors/index.md b/translations/de-DE/content/sponsors/index.md
new file mode 100644
index 0000000000..efd1738d8a
--- /dev/null
+++ b/translations/de-DE/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Sponsors Documentation
+shortTitle: GitHub Sponsors
+intro: 'Invest in the open source projects you depend on, support digital infrastructure, and make open source careers possible by sponsoring open source contributors and their projects. Build a {% data variables.product.prodname_sponsors %} profile and receive compensation for your open source work.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: 'sponsors'
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..46dab4011f
--- /dev/null
+++ b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: Webhooks für Ereignisse in deinem unterstützten Konto konfigurieren
+intro: 'Du kannst Webhooks konfigurieren, damit Du benachrichtigt wirst, wenn Du ein neues Sponsoring erhältst, oder wenn bestehende Sponsoren Änderungen an ihren Sponsorings machen.'
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### About webhooks for events in your sponsored account
+
+Damit Du Änderungen wie zum Beispiel die Kündigung eines Sponsorings am Ende der Zahlungsperiode überwachen kannst, kannst Du Webhooks für Deine unterstützten Benutzer- oder Organisations-Konten erstellen. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship).
+
+### Managing webhooks for events in your sponsored account
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..8d05fd7671
--- /dev/null
+++ b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Getting started with the Sponsors GraphQL API
+intro: 'Using the GraphQL API, you can build custom integrations to manage or review your sponsorships.'
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+To get started with the GraphQL API, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+You can find the details about the Sponsors GraphQL API in the reference docs. For more information, see "[GraphQL reference](/graphql/reference)." We recommend using the GraphQL explorer to build your GraphQL calls. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer)."
diff --git a/translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..37e7055360
--- /dev/null
+++ b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: Integrating with GitHub Sponsors
+intro: 'As an open source contributor, you can build custom tools to manage your GitHub sponsorships.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..23a7a382ae
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: Über GitHub Sponsors für Open-Source-Mitwirkende
+intro: 'Wenn Du einen Mehrwert für ein Open-Source-Projekt bietest, kannst Du ein „unterstützter Entwickler" werden, um für Deine Arbeit eine Vergütung zu erhalten.'
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### {% data variables.product.prodname_sponsors %} beitreten
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Weitere Informationen findest Du unter „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto einrichten](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+Nachdem Du {% data variables.product.prodname_sponsors %} beigetreten bist, kannst Du die Sponsorenschaltfläche zum Open-Source-Repository hinzufügen, an dem Du mitwirkst. Dadurch erhöhst Du die Sichtbarkeit Deines {% data variables.product.prodname_sponsors %}-Profils und von anderen Finanzierungsplattformen. Weitere Informationen findest Du unter „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository).“
+
+Du kannst für Dein Sponsoring ein Ziel setzen. Weitere Informationen findest Du unter „[Sponsoring-Ziel verwalten](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal).“
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### Sponsoring-Stufen
+
+{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+
+It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule.
+
+### Sponsoring-Auszahlungen
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)."
+
+### Feedback zu {% data variables.product.prodname_sponsors %} geben
+
+{% data reusables.sponsors.feedback %}
+
+### Weiterführende Informationen
+- „[Häufig gestellte Fragen mit dem {% data variables.product.prodname_sponsors %}-Team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)“ auf {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..3d3f8b0594
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: Deine Sponsoren kontaktieren
+intro: 'Du kannst eine E-Mail an Deine Sponsoren senden, wenn diese den Erhalt von Aktualisierungen zu Deiner Arbeit abonniert haben.'
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### About sponsorship updates
+
+Deine Sponsoren können auswählen, ob sie per E-Mail über Deine Arbeit auf dem Laufenden gehalten werden möchten. Weitere Informationen finden Sie unter „[Sponsoring verwalten](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)“.
+
+For sponsored developer accounts, the update will come from your user account's primary email address. Wenn Du den Datenschutz für E-Mail-Adressen für Dein Benutzerkonto aktiviert hast, wird die E-Mail stattdessen von `noreply@github.com` versendet. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. Weitere Informationen findest Du unter „[Deine Commit-E-Mail-Adresse festlegen](/articles/setting-your-commit-email-address).“
+
+### Deine Sponsoren kontaktieren
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..855bb55b4a
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: Die Details Deines GitHub Sponsors-Profil bearbeiten
+intro: 'Du kannst die Informationen aktualisieren, die potenziellen Sponsoren zu Deiner Arbeit angezeigt werden.'
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### Über Sponsoren-Profile
+
+Dein {% data variables.product.prodname_sponsors %}-Profil informiert potentielle Sponsoren, warum sie Dich unterstützten sollten. People see your sponsor profile when they click the **Sponsor** button on your profile. Wir empfehlen Dir, die folgenden Informationen einzuschließen.
+
+- Open-Source-Arbeit, zu der Du beiträgst
+- Warum Du Dich für Open-Source-Entwicklung einsetzt
+
+### Editing your profile details
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..4b84510f9a
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: Sponsoring über GitHub Sponsors erhalten
+shortTitle: Sponsoring erhalten
+intro: 'Du oder Deine Organisation können unterstützte Open-Source-Mitwirkende werden, um Zahlungen für Eure Arbeit zu erhalten, die Sponsoring-Details zu aktualisieren sowie Eure Sponsoren zu sehen und zu kontaktieren.'
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..4d6aeda457
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Deine Auszahlungen von GitHub Sponsors verwalten
+intro: 'Sie können Informationen zu vergangenen und künftigen Auszahlungen von {% data variables.product.prodname_sponsors %} einsehen und Ihre Bankdaten bearbeiten.'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### Informationen zu Auszahlungen von {% data variables.product.prodname_sponsors %}
+
+Du kannst Deine Auszahlungen von {% data variables.product.prodname_sponsors %} nur dann verwalten, wenn Du über Stripe Connect bezahlt wirst. Wenn Du via ACH-Überweisung oder Banküberweisung auf Dein unterstütztes Benutzerkonto bezahlt wirst, wirst Du die Registerkarte **Auszahlungen** auf Deinem Dashboard als unterstützter Open-Source-Mitwirkenden nicht sehen. Unterstützte Organisationen können nur Stripe Connect für Auszahlungen verwenden. Weitere Informationen findest du unter „[Über {% data variables.product.prodname_sponsors %} für Open-Source-Mitwirkende](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)"
+
+{% data reusables.sponsors.payout-info %}
+
+### Viewing and editing payout information
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..8c6b588a8c
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: Deine Sponsoring-Ziele verwalten
+intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### Über Sponsoring-Ziele
+
+You can set a funding goal for your sponsored account and share the goal with your community. Ziele helfen Dir, die Auswirkungen zu verstehen, die Du in der Open-Source-Community hast, und Deine Präsenz im {% data variables.product.prodname_sponsors %}-Programm zu erweitern.
+
+Du kannst Ziele setzen für die Anzahl der Sponsoren, die Du suchst, oder die finanziellen Beiträge, Du Du jeden Monat erzielen möchtest. Du kannst jeweils nur ein Ziel festlegen. Nachdem du ein Ziel erreicht hast, kannst Du ein neues Ziel setzen.
+
+### Setting a goal
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Ein Ziel bearbeiten
+
+Wenn Du ein Ziel bearbeitest, kannst du kein Ziel wählen, das Du bereits erreicht hast. Wenn Du beispielsweise bereits 5 Sponsoren hast, kannst du Dein Ziel nicht dahingehend bearbeiten, dass Du nur 4 Sponsoren suchst.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Ein Ziel zurückziehen
+
+Wenn Du ein Ziel zurückziehst, kannst Du es nicht mehr reaktivieren. Du musst stattdessen ein neues Ziel erstellen.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..3216a4904a
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: Managing your sponsorship tiers
+intro: 'Du kannst neue Sponsoring-Stufen hinzufügen, oder eine bestehende Stufe bearbeiten oder zurückziehen.'
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### Informationen zu Sponsoring-Stufen
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### Eine Stufe hinzufügen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### Editing or retiring a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### Enabling tiers with custom amounts
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### Disabling tiers with custom amounts
+
+You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired.
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..128e938905
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: GitHub Sponsors für Deine Organisation einrichten
+intro: 'Deine Organisation kann {% data variables.product.prodname_sponsors %} beitreten, um Zahlungen für Eure Arbeit zu erhalten.'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### {% data variables.product.prodname_sponsors %} beitreten
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Nachdem Du für Deine Organisation einen Einladung erhalten hast, um {% data variables.product.prodname_sponsors %} beizutreten, kannst du die unten stehenden Schritte abschließen, um eine unterstützte Organisation zu werden.
+
+Um {% data variables.product.prodname_sponsors %} als ein einzelner Mitwirkender außerhalb einer Organisation beizutreten, siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto einrichten](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. Klicke rechts neben Deiner Organisation auf **Join the waitlist** (Der Warteliste beitreten).
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### Dein Profil als unterstützte Organisation vervollständigen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Sponsoring-Stufen erstellen
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Deine Bankinformationen einreichen
+
+Als unterstützte Organisation musst Du Auszahlungen auf ein dediziertes Bankkonto Deiner Organisation in einer unterstützten Region erhalten. Du kannst ein Unternehmensbankkonto über Dienste wie [Open Collective](https://opencollective.com/) und [Stripe Atlas](https://stripe.com/atlas) erhalten. The region your organization legally operates in and the region of your bank account must match. The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+For more information about setting up Stripe Connect using Open Collective, see [Setting up {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) in the Open Collective Docs.
+
+### Deine Steuerinformationen einreichen
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Zwei-Faktor-Authentifizierung (2FA) für Dein {% data variables.product.prodname_dotcom %}-Konto aktivieren
+
+Bevor Deine Organisation eine unterstütze Organisation werden kann, muss Du 2FA auf Deinem {% data variables.product.product_name %}-Konto aktivieren. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung konfigurieren](/articles/configuring-two-factor-authentication)“.
+
+### Deinen Antrag bei {% data variables.product.prodname_dotcom %} zur Genehmigung einreichen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### Weiterführende Informationen
+- „[Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)“
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..7935d6a736
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: GitHub Sponsors für Dein Benutzerkonto aufsetzen
+intro: 'Um ein unterstützter Entwickler zu werden, musst Du {% data variables.product.prodname_sponsors %} beitreten, Dein Formular für unterstützte Entwickler ausfüllen, Sponsoring-Stufen erstellen, Deine Bank- und Steuerdaten einreichen und die Zwei-Faktor-Authentifizierung für Dein {% data variables.product.prodname_dotcom %}-Konto aktivieren.'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### {% data variables.product.prodname_sponsors %} beitreten
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Um {% data variables.product.prodname_sponsors %} als eine Organisation beizutreten, siehe „[{% data variables.product.prodname_sponsors %} für Deine Organisation aufsetzen](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. Wenn Du ein Organisationsinhaber bist, hast Du mehr als ein qualifizierendes Konto. Klicke auf **View your eligible accounts** (Deine qualifizierenden Konten ansehen) und finde dann Dein Benutzerkonto in der Liste der Konten.
+3. Klicke auf **Join the waitlist** (Der Warteliste beitreten).
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+Wenn Du ein Bankkonto in einer unterstützten Region hast, wird {% data variables.product.prodname_dotcom %} Deine Bewerbung innerhalb von zwei Wochen überprüfen.
+
+### Formular für unterstützte Entwickler ausfüllen
+
+Nachdem {% data variables.product.prodname_dotcom %} Deine Bewerbung überprüft hat, kannst Du Dein Profil als unterstützter Entwickler aufsetzen, damit Personen beginnen können, Dich zu unterstützen.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Sponsoring-Stufen erstellen
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Deine Bankinformationen einreichen
+
+Wenn Du in einer unterstützen Region lebst, kannst Du diesen Anweisungen folgen, um Deine Bankinformationen durch das Erstellen eines Stripe Connect-Kontos einzureichen. Your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### Deine Steuerinformationen einreichen
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Zwei-Faktor-Authentifizierung (2FA) für Dein {% data variables.product.prodname_dotcom %}-Konto aktivieren
+
+Bevor Du ein unterstützter Entwickler werden kannst, musst Du die 2FA für Dein {% data variables.product.product_name %}-Konto aktivieren. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung konfigurieren](/articles/configuring-two-factor-authentication)“.
+
+### Deinen Antrag bei {% data variables.product.prodname_dotcom %} zur Genehmigung einreichen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. Klicke auf **Request approval** (Genehmigung beantragen). ![Schaltfläche „Request approval" (Beantragen der Genehmigung)](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..d57f281bc5
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Steuerinformationen für GitHub Sponsoren
+intro: 'Unterstützte Entwickler und Organisationen müssen Steuerinformationen an {% data variables.product.prodname_dotcom %} einreichen und sind verantwortlich für die Berechnung und Bezahlung ihrer eigenen Steuern.'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+Wenn Du in den USA steuerpflichtig bist, musst du das Formular W-9 einreichen, bevor Du Zahlungen erhalten kannst. Wenn Du in einer anderen Region als den USA steuerpflichtig bist, musst Du ein Formular W-8BEN einreichen, bevor Du Zahlungen erhalten kannst. Weitere Informationen findest du unter „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" und „[{% data variables.product.prodname_sponsors %} für Deine Organisation aufsetzen](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)". {% data variables.product.prodname_dotcom %} wird Dir die notwendigen Formulare zusenden, Dich über deren Fälligkeit informieren und Dir genügend Zeit einräumen, die Formulare zu vervollständigen und einzureichen.
+
+If you are a taxpayer in the United States and earn more than $600 USD in a tax year, {% data variables.product.prodname_dotcom %} will send you a 1099 before January 31 of the next calendar year. Steuerzahlern anderer Länder stellen wir keine Steuerformulare bereit.
+
+{% data variables.product.prodname_dotcom %} behält aus {% data variables.product.prodname_sponsors %}-Zahlungen keine Steuern ein. Unterstützte Entwickler sind für die Steuerermittlung und Zahlung ihrer Steuern selbst verantwortlich.
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### Weiterführende Informationen
+
+- [Sponsoren und Sponsoring anzeigen](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..d646c52ad6
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: Sponsoren und Sponsoring anzeigen
+intro: Du kannst detaillierte Informationen und Analysen zu Deinen Sponsoren und Deinem Sponsoring einsehen und exportieren.
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### About sponsors and sponsorships
+
+Du kannst Analysen zu Deinen aktuellen und vergangenen Sponsorings einsehen, die Zahlungen, die Du von Sponsoren erhalten hast, und Ereignisse, wie beispielsweise Kündigungen oder Sponsoren-Stufenänderungen für Deine Sponsorings. Du kannst auch Aktivitäten wie neue Sponsorings oder geänderte und gekündigte Sponsorings ansehen. Du kannst die Liste der Aktivitäten nach Datum filtern. Du kannst die Sponsoring-Daten Deines Kontos auch im CSV- oder JSON-Format exportieren.
+
+### Sponsoren und Sponsoring anzeigen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. Optional kannst Du Deine Sponsoren nach Stufe filtern. verwende dazu das Dropdownmenü **Filter**, klicke auf **Active tiers** (Aktive Stufen) oder **Retired tiers** (zurückgezogene Stufen), und wähle eine Stufe aus. ![Dropdownmenü zum Filtern nach Stufe](/assets/images/help/sponsors/filter-drop-down.png)
+
+### Letzte Sponsoring-Aktivitäten anzeigen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### Deine Sponsoring-Daten exportieren
+
+You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Schaltfläche „Export"](/assets/images/help/sponsors/export-all.png)
+1. Choose a time frame and a format for the data you'd like to export, then click **Start export**. ![Optionen für den Datenexport](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..1126a8c136
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: Attributing sponsorships to your organization
+intro: You can attribute the sponsorships paid by one of your organizations to another organization.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. Navigate to the organization whose sponsorships you want to attribute to another organization.
+2. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png)
+1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..51e66bb962
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: Open-Source-Mitwirkende unterstützen
+intro: 'Du kannst Mitwirkende unterstützen, Aktualisierungen von Entwicklern und Organisationen erhalten, die Du unterstützt, und auf {% data variables.product.product_name %} durchgängig einen Sponsoren-Badge anzeigen.'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..418c7dc29b
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: Sponsoring verwalten
+intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account.
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Die Datenschutzeinstellung für Ihr Sponsoring verwalten
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Managing email updates for your sponsorship
+
+You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address.
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Weiterführende Informationen
+
+- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)"
+- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)"
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..bf5c436920
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: Einen Open-Source-Mitwirkenden unterstützen
+intro: 'Du kannst monatlich wiederkehrende Zahlungen an einen Entwickler oder eine Organisation machen, welche ein für Dich wichtiges Open-Source-Projekt entwirft, erstellt oder unterhält.'
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### About sponsorships
+
+{% data reusables.sponsors.sponsorship-details %}
+
+You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons.
+- Sustaining specific libraries that your organization's work depends on
+- Investing in the ecosystem you rely on as a organization (such as blockchain)
+- Developing brand awareness as an organization that values open source
+- Thanking open source developers for building libraries that complement the product your organization offers
+
+You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist).
+
+{% data reusables.sponsors.no-fees %} Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)“.
+
+When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. Weitere Informationen finden Sie unter „[Sponsoring heraufstufen](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“.
+
+If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. Weitere Informationen findest Du unter „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" und „[{% data variables.product.prodname_sponsors %} für Deine Organisation aufsetzen](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_dotcom %} ist nicht dafür verantwortlich, wie Entwickler sich selbst darstellen, noch befürwortet {% data variables.product.prodname_dotcom %} irgendwelche unterstützten Open-Source-Projekte. Sämtliche Aussagen liegen in der alleinigen Verantwortung des Entwicklers, welcher die Beiträge erhält. Vergewissere Dich, dass Du einer Person vertrauen kannst, bevor du eine Unterstützung offerierst. Weitere Informationen findest Du unter „[{% data variables.product.prodname_sponsors %} Zusatzbedingungen](/github/site-policy/github-sponsors-additional-terms)".
+
+{% endnote %}
+
+### Sponsoring an account
+
+Before you can sponsor an account, you must have a verified email address. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/github/getting-started-with-github/verifying-your-email-address).“
+
+1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor.
+1. Navigate to your sponsorship dashboard for the account.
+   - To sponsor a developer, under the developer's name, click **Sponsor**. ![Schaltfläche „Sponsor“ (Unterstützen)](/assets/images/help/profile/sponsor-button.png)
+   - To sponsor an organization, to the right of the organization's name, click **Sponsor**. ![Schaltfläche „Sponsor“ (Unterstützen)](/assets/images/help/sponsors/sponsor-org-button.png)
+1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![Schaltfläche „Edit payment" (Bearbeiten der Zahlungsdetails)](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![Optionsfelder, um auszuwählen, wer Dein Sponsoring sehen kann](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/de-DE/data/glossaries/external.yml b/translations/de-DE/data/glossaries/external.yml
index 1c4813764d..9db9803013 100644
--- a/translations/de-DE/data/glossaries/external.yml
+++ b/translations/de-DE/data/glossaries/external.yml
@@ -1,7 +1,7 @@
 ---
 - 
   term: '@erwähnen'
-  description: um eine Person auf GitHub mittels „@“ vor ihrem Benutzernamen zu benachrichtigen. Benutzer in einer Organisation auf GitHub können auch Bestandteil eines Teams sein, das erwähnt werden kann.
+  description: Um eine Person auf GitHub mittels „@“ vor ihrem Benutzernamen zu benachrichtigen. Benutzer in einer Organisation auf GitHub können auch Bestandteil eines Teams sein, das erwähnt werden kann.
 - 
   term: Zugriffstoken
   description: >-
@@ -181,7 +181,7 @@
 - 
   term: Standardbranch
   description: >-
-    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called `main`, and is often the default branch.
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}, and is often the default branch.
 - 
   term: Abhängigkeitsdiagramm
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.{% else %}Name often chosen as an alternative to `master` for the default branch of a repository.{% endif %}
 - 
   term: Master
   description: >-
-    The default branch in many Git repositories. By default, when you create a new Git repository on the command line a branch called `master` is created. Many tools now use an alternative name for the default branch. For example, when you create a new repository on GitHub the default branch is called `main`.
+    The default branch in many Git repositories. By default, when you create a new Git repository on the command line, a branch called `master` is created. Many tools now use an alternative name for the default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} For example, when you create a new repository on GitHub, the default branch is called `main`.{% endif %}
 - 
   term: Mitgliederdiagramm
   description: Ein Repository-Diagramm, in dem alle Forks eines Repositorys gezeigt werden.
diff --git a/translations/de-DE/data/glossaries/internal.yml b/translations/de-DE/data/glossaries/internal.yml
index b382089ff3..ee18a2cdd1 100644
--- a/translations/de-DE/data/glossaries/internal.yml
+++ b/translations/de-DE/data/glossaries/internal.yml
@@ -60,6 +60,10 @@
 - 
   term: Azure
   description: Eine Microsoft-Cloud-Computing-Plattform.
+- 
+  term: Azure DevOps
+  description: >-
+    A Microsoft product offering source code hosting, issues, CI/CD pipelines, and other developer services. The on-premises version was formerly known as Team Foundation Server. The cloud-hosted version was formerly known as Visual Studio Team Services.
 - 
   term: leeres Repository
   description: >-
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    Ein Microsoft-Produkt, das Quellcodeverwaltungs- und andere Teamdienste bereitstellt.
+    The former name of a Microsoft product that provides source code management and other team services. Now known as Azure DevOps Server.
 - 
   term: Textile
   description: >-
diff --git a/translations/de-DE/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/de-DE/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..a48ed204b7
--- /dev/null
+++ b/translations/de-DE/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: Access to package version deletion
+  description: >-
+    This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: Bereitstellungen
+  description: >-
+    This preview adds support for deployments mutations and new deployments features.
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - More detailed information about a pull request's merge state.
+  description: >-
+    This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - Update multiple refs in a single operation.
+  description: This preview adds support for updating multiple refs in a single operation.
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: Project Event Details
+  description: >-
+    This preview adds project, project card, and project column details to project-related issue events.
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: Create content attachments
+  description: This preview adds support for creating content attachments.
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: Labels Preview
+  description: >-
+    This preview adds support for adding, updating, creating and deleting labels.
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: Import Project
+  description: This preview adds support for importing projects.
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Team Review Assignments Preview
+  description: >-
+    This preview adds support for updating the settings for team review assignment.
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/de-DE/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/de-DE/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..3d4deaabeb
--- /dev/null
+++ b/translations/de-DE/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
+    reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user` will be removed. Use the `assignee` field instead.'
+    reason: Assignees can now be mannequins.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
+    reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
+    reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: '`user` will be removed. Use the `assignee` field instead.'
+    reason: Assignees can now be mannequins.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
+    reason: '`Sponsorship.maintainer` will be removed.'
+    date: '2020-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All pending members consume a license
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.'
+    reason: Repository invitations can now be associated with an email, not only an invitee.
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: '`timeline` will be removed. Use Issue.timelineItems instead.'
+    reason: '`timeline` will be removed'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
+    reason: '`timeline` will be removed'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: '`INVITEE_LOGIN` will be removed.'
+    reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.'
+    reason: '`Sponsorship.sponsor` will be removed.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All members consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All outside collaborators consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All pending collaborators consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.'
+    reason: DRAFT state will be removed from this enum and `isDraft` should be used instead
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nplasterer
diff --git a/translations/de-DE/data/learning-tracks/README.md b/translations/de-DE/data/learning-tracks/README.md
index ec0f70309e..d8bd99c5fe 100644
--- a/translations/de-DE/data/learning-tracks/README.md
+++ b/translations/de-DE/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # Learning Tracks (aka Learning Paths)
 
-Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis.
\ No newline at end of file
+Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. For example, see https://docs.github.com/en/actions/guides.
+
+Learning track data for a product is defined in two places:
+
+1. A simple array of learning track names is defined in the product sublanding index page frontmatter.
+
+    For example, in `content/actions/guides/index.md`:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. Additional data for each track is defined in a YAML file named for the **product** in the `data` directory.
+
+    For example, in `data/learning-tracks/actions.yml`, each of the items from the content file's `learningTracks` array is represented with additional data such as `title`, `description`, and an array of `guides` links.
+
+    One learning track in this YAML **per version** must be designated as a "featured" learning track via `featured_track: true`, which will set it to appear at the top of the product sublanding page. A test will fail if this property is missing.
+
+    The `featured_track` property can be a simple boolean (i.e., `featured_track: true`) or it can be a string that includes versioning statements (e.g., `featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`). If you use versioning, you'll have multiple `featured_track`s per YML file, but make sure that only one will render in each currently supported version. A test will fail if there are more or less than one featured link for each version.
+
+Versioning for learning tracks is processed at page render time. The code lives in [`lib/learning-tracks.js`](lib/learning-tracks.js), which is called by `page.render()`. The processed learning tracks are then rendered by `layouts/product-sublanding.html`.
+
+The schema for validating the learning track YAML lives in [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) and is exercised by [`tests/content/lint-files.js`](tests/content/lint-files.js).
diff --git a/translations/de-DE/data/learning-tracks/actions.yml b/translations/de-DE/data/learning-tracks/actions.yml
index b6017eeb75..2b80d93721 100644
--- a/translations/de-DE/data/learning-tracks/actions.yml
+++ b/translations/de-DE/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: 'Build and test code'
   description: 'You can create custom continuous integration (CI) workflows right in your repository.'
diff --git a/translations/de-DE/data/learning-tracks/admin.yml b/translations/de-DE/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..5e06a59c40
--- /dev/null
+++ b/translations/de-DE/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: 'Get started with {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/de-DE/data/release-notes/2-21/19.yml b/translations/de-DE/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..5726fd8bda
--- /dev/null
+++ b/translations/de-DE/data/release-notes/2-21/19.yml
@@ -0,0 +1,18 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - User saw 500 error when executing git operations on an instance configured with LDAP authentication.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/de-DE/data/release-notes/2-21/20.yml b/translations/de-DE/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..4a3d11dfb6
--- /dev/null
+++ b/translations/de-DE/data/release-notes/2-21/20.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/de-DE/data/release-notes/2-21/21.yml b/translations/de-DE/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..2a76183f01
--- /dev/null
+++ b/translations/de-DE/data/release-notes/2-21/21.yml
@@ -0,0 +1,15 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/de-DE/data/release-notes/2-22/11.yml b/translations/de-DE/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..909f09ff83
--- /dev/null
+++ b/translations/de-DE/data/release-notes/2-22/11.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Syntax highlighting could fail due to the Treelights container running out of memory.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/de-DE/data/release-notes/2-22/12.yml b/translations/de-DE/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..bb7d46505d
--- /dev/null
+++ b/translations/de-DE/data/release-notes/2-22/12.yml
@@ -0,0 +1,22 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/de-DE/data/release-notes/2-22/13.yml b/translations/de-DE/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..ef4bbc46f3
--- /dev/null
+++ b/translations/de-DE/data/release-notes/2-22/13.yml
@@ -0,0 +1,20 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/de-DE/data/release-notes/3-0/0.yml b/translations/de-DE/data/release-notes/3-0/0.yml
index 0eca470194..c9d3801bce 100644
--- a/translations/de-DE/data/release-notes/3-0/0.yml
+++ b/translations/de-DE/data/release-notes/3-0/0.yml
@@ -134,6 +134,7 @@ sections:
     - A race condition can cause dependency graph database migrations to appear to fail.
     - Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
   deprecations:
     - 
       heading: Deprecation of GitHub Enterprise Server 2.19
diff --git a/translations/de-DE/data/release-notes/3-0/1.yml b/translations/de-DE/data/release-notes/3-0/1.yml
index 3e7296628a..9df6976efc 100644
--- a/translations/de-DE/data/release-notes/3-0/1.yml
+++ b/translations/de-DE/data/release-notes/3-0/1.yml
@@ -45,6 +45,7 @@ sections:
     - 'Dependency graph fails to parse `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.'
     - 'Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.'
     - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.'
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/de-DE/data/release-notes/3-0/2.yml b/translations/de-DE/data/release-notes/3-0/2.yml
index e38aa78664..52e610b757 100644
--- a/translations/de-DE/data/release-notes/3-0/2.yml
+++ b/translations/de-DE/data/release-notes/3-0/2.yml
@@ -31,6 +31,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/de-DE/data/release-notes/3-0/3.yml b/translations/de-DE/data/release-notes/3-0/3.yml
index 4255a873dc..355b774734 100644
--- a/translations/de-DE/data/release-notes/3-0/3.yml
+++ b/translations/de-DE/data/release-notes/3-0/3.yml
@@ -30,6 +30,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
       To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
diff --git a/translations/de-DE/data/release-notes/3-0/4.yml b/translations/de-DE/data/release-notes/3-0/4.yml
index b3a39c1743..4b70a13ae5 100644
--- a/translations/de-DE/data/release-notes/3-0/4.yml
+++ b/translations/de-DE/data/release-notes/3-0/4.yml
@@ -23,3 +23,4 @@ sections:
     - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/de-DE/data/release-notes/3-0/5.yml b/translations/de-DE/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..1bcc84c956
--- /dev/null
+++ b/translations/de-DE/data/release-notes/3-0/5.yml
@@ -0,0 +1,27 @@
+---
+date: '2021-04-14'
+intro: 'The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Some logs were not included in the log forwarding configuration.
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Pages were not getting published when using custom CA certificate.
+    - Packages related subdomains were not showing up in the "Test domain settings" prompt for subdomain isolation.
+    - The `X-GitHub-Enterprise-Host` header sent with webhooks included a random string, rather than the hostname of the GitHub Enterprise Server instance that sent the HTTP POST payload.
+    - Upgrading from 2.22.x to 3.0.x would fail if GitHub Actions had previously been enabled, but disabled before the upgrade.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - reStructuredText (RST) rendering in the web UI would fail and instead displayed raw RST markup text.
+    - Email notifications for Secret Scanning alerts were not sent to authorized users when the Dependency Graph was not fully enabled.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+    - Jupyter notebooks with non-ASCII characters could fail to render.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/de-DE/data/release-notes/3-0/6.yml b/translations/de-DE/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..83604b5f77
--- /dev/null
+++ b/translations/de-DE/data/release-notes/3-0/6.yml
@@ -0,0 +1,30 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - Upgrades did not include the latest version of Actions runner properly installed.
+    - '`github-env` configuration could result in zombie processes.'
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - The Create Repository button was disabled for users who belonged to more than 50 organizations.
+    - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful.
+    - The `rms-packages` index was shown in the site admin dashboard.
+    - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form.
+    - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+    - Code Scanning backend services did not start up reliably after applying hotpatches.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/de-DE/data/release-notes/3-0/7.yml b/translations/de-DE/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..4c176c0b41
--- /dev/null
+++ b/translations/de-DE/data/release-notes/3-0/7.yml
@@ -0,0 +1,23 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/de-DE/data/release-notes/3-1/0-rc1.yml b/translations/de-DE/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..0682b06933
--- /dev/null
+++ b/translations/de-DE/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security Secret Scanning
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository.
+
+          This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}:
+
+          - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37
+          - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)
+          - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets
+          - Updated the index view to made it easy to triage secrets in bulk
+          - Reduced the false positive rate on many patterns
+
+          Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+    - 
+      heading: GitHub Advanced Security billing improvements
+      notes:
+        - |
+          This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}:
+
+          - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+          - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+    - 
+      heading: Dependabot improvements
+      notes:
+        - |
+          This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}:
+
+          - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
+          - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository).
+          - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."'
+    - 
+      heading: GitHub Actions Workflow Visualization beta
+      notes:
+        - |
+
+          GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can:
+          - View and understand complex workflows
+          - Track progress of workflows in real-time
+          - Troubleshoot runs quickly by easily accessing logs and jobs metadata
+          - Monitor progress of deployment jobs and easily access deployment targets
+
+          For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+    - 
+      heading: OAuth 2.0 Device Authorization Grant
+      notes:
+        - |
+          [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser.
+
+          Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow.
+    - 
+      heading: Pull request auto-merge
+      notes:
+        - |
+          With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+    - 
+      heading: Custom notifications
+      notes:
+        - |
+          You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+  changes:
+    - 
+      heading: Administration Changes
+      notes:
+        - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+        - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+        - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+        - Check annotations older than four months will be archived.
+    - 
+      heading: Security Changes
+      notes:
+        - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).'
+        - SARIF upload support increased to a maximum of 5000 results per upload.
+    - 
+      heading: Developer Changes
+      notes:
+        - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to.
+        - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)."
+        - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."'
+        - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.'
+        - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.'
+    - 
+      heading: API Changes
+      notes:
+        - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning).
+        - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints.
+  known_issues:
+    - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.20
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.21
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of Legacy GitHub App Webhook Events
+      notes:
+        - 'Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).'
+    - 
+      heading: Deprecation of Legacy GitHub Apps Endpoint
+      notes:
+        - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0.  More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).
+    - 
+      heading: Deprecation of OAuth Application API
+      notes:
+        - 'GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).'
+    - 
+      heading: Deprecation of GitHub Actions short SHA support
+      notes:
+        - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/de-DE/data/reusables/actions/actions-cli.md b/translations/de-DE/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..9de328800e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+For information on setting up {% data variables.product.prodname_cli %}, see "[Managing GitHub Actions with GitHub CLI](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)."
diff --git a/translations/de-DE/data/reusables/actions/actions-group-concurrency.md b/translations/de-DE/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..493e81cb45
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.
+
+##### Examples using concurrency and the default behavior
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### Example using concurrency to cancel any in-progress job or run
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/de-DE/data/reusables/actions/concurrency-beta.md b/translations/de-DE/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..c3f2c9a831
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Concurrency is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/enterprise-github-connect-warning.md b/translations/de-DE/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..ce755253ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom %}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md b/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md
index 9f2287cfee..e568edbd05 100644
--- a/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} is designed to work in environments without internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+{% data variables.product.prodname_actions %} on {% data variables.product.product_name %} is designed to work in environments without full internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
diff --git a/translations/de-DE/data/reusables/actions/forked-secrets.md b/translations/de-DE/data/reusables/actions/forked-secrets.md
index b7e069fc1d..08f49e8c8a 100644
--- a/translations/de-DE/data/reusables/actions/forked-secrets.md
+++ b/translations/de-DE/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-Mit Ausnahme von `GITHUB_TOKEN` werden Geheimnisse nicht an den Runner übergeben, wenn ein Workflow von einem geforkten Repository aus ausgelöst wird.
+Mit Ausnahme von `GITHUB_TOKEN` werden Geheimnisse nicht an den Runner übergeben, wenn ein Workflow von einem geforkten Repository aus ausgelöst wird.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..43937ba24a
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.product_location %}:
+
+- **Committers** is the number of committers who contributed to at least one {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
+- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
+
+If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
+
+When you remove a user from your enterprise account, the user's license is freed within 24 hours.
+
+{% note %}
+
+**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..d0ea836b42
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Periodically you should check that your use is within your license capacity.
diff --git a/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md
index b6abfe68c7..1b77a9051e 100644
--- a/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% endif %}
+{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% elsif currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your Enterprise](/admin/advanced-security)."{% endif %}
 
 You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose.
 
diff --git a/translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..ff7d774004
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify:
+
+- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company.
+- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced.
+
+When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md b/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md
index 0d62775b89..e1b69b9a6e 100644
--- a/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)“.
+{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..d447e24e28
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+When you enable or disable {% data variables.product.prodname_advanced_security %} for repositories, {% data variables.product.prodname_dotcom %} displays an overview of changes to the use of your license. If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up.
+
+If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available.{% if currentVersion == "free-pro-team@latest" %} If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.{% endif %}
+
+As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal.
diff --git a/translations/de-DE/data/reusables/cli/actions-cli-version.md b/translations/de-DE/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..83cd5971dd
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+To access all of the {% data variables.product.prodname_actions %}-related commands, you must use version 1.9.0 or greater.
diff --git a/translations/de-DE/data/reusables/cli/cli-auth.md b/translations/de-DE/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..be9a823c3c
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} can authenticate using your {% data variables.product.prodname_dotcom %} account. Before running {% data variables.product.prodname_cli %} commands, you will need to authenticate by running `gh auth login`. For more information on command line authentication, see "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)."
diff --git a/translations/de-DE/data/reusables/cli/cli-manual.md b/translations/de-DE/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..dd2012d873
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+For more information about {% data variables.product.prodname_cli %}, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/cli/cli-repo.md b/translations/de-DE/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..b3394e441a
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} commands must be run within the repository that you want to interact with, so you must first navigate to the directory containing the local copy of your repository. Alternatively, you can specify a repository by passing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY` or `--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY` or `--repo OWNER/REPOSITORY`{% endif %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Replace `HOSTNAME` with the name of {% data variables.product.product_location %}. {% endif %}Replace `OWNER` with owner of the repository. Ersetzen Sie `REPOSITORY` durch den Namen des Repositorys.
diff --git a/translations/de-DE/data/reusables/cli/download-update-cli.md b/translations/de-DE/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..b26363cf45
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+To download or upgrade {% data variables.product.prodname_cli %}, follow the instructions in the [{% data variables.product.prodname_cli %} README](https://github.com/cli/cli#installation).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..a101d1809f
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`, `csharp`, `go`, `java`, `javascript`, and `python`
diff --git a/translations/de-DE/data/reusables/code-scanning/enabling-options.md b/translations/de-DE/data/reusables/code-scanning/enabling-options.md
index 3e78b63452..137dd09d78 100644
--- a/translations/de-DE/data/reusables/code-scanning/enabling-options.md
+++ b/translations/de-DE/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">Running {% data variables.product.prodname_codeql %} code scanning in your CI system</a>").
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      Third&#8209;party
-    </td>
-    
-    <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or generated externally and uploaded to {% data variables.product.product_name %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Uploading a SARIF file to {% data variables.product.prodname_dotcom %}</a>").
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)").
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql %} code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
+{%- endif %}
+| Third&#8209;party | Using
+{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)").|
diff --git a/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md
index c5142332f6..6881be29fa 100644
--- a/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries.
+**Note:** SARIF upload supports a maximum of {% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries.
 
 {% endnote %}
diff --git a/translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..52dda51137
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**Note:** Uploading SARIF data to display as {% data variables.product.prodname_code_scanning %} results in {% data variables.product.product_name %} is supported for organization-owned repositories with {% data variables.product.prodname_GH_advanced_security %} enabled{% if currentVersion == "free-pro-team@latest" %}, and public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..5c772293bc
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.product.product_location %}.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/codespaces/about-personalization.md b/translations/de-DE/data/reusables/codespaces/about-personalization.md
index 850f41d11b..12c6c4dcc7 100644
--- a/translations/de-DE/data/reusables/codespaces/about-personalization.md
+++ b/translations/de-DE/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-Für alle Codespaces, die von Deinem Konto erstellt werden, kannst Du Aspekte der Codespace-Umgebung personalisieren. Die Personalisierung kann Shell-Präferenzen und zusätzliche Werkzeuge beinhalten.
+You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. Die Personalisierung kann Shell-Präferenzen und zusätzliche Werkzeuge beinhalten.
diff --git a/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md b/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..39b29dc4a0
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+You can forward ports in your codespace to test and debug your application.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..8031bfb4af
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index f56c116566..7f3cc83952 100644
--- a/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. Klicke in der linken Seitenleiste von {% data variables.product.prodname_vscode %} auf das „Remote Explorer"-Symbol. ![Das „Remote Explorer"-Symbol in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. Klicke in der linken Seitenleiste von {% data variables.product.prodname_vscode %} auf das „Remote Explorer"-Symbol. ![Das „Remote Explorer"-Symbol in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md b/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..475114c1c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Each of these has a different level of resources and a different billing tier.<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**Note:** {% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types:
+
+* **Basic** for updating a file and raising a pull request
+* **Standard** for editing a website
+* **Premium** for high compute tasks such as data analysis
diff --git a/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md b/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..87bfa539ff
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users.
+
+For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..fed860897b
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/de-DE/data/reusables/codespaces/rebuild-command.md b/translations/de-DE/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..ea9e45b032
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/recovery-mode.md b/translations/de-DE/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..fa4e73d013
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/release-stage.md b/translations/de-DE/data/reusables/codespaces/release-stage.md
index 9cf4d59d9f..4eb00a36b8 100644
--- a/translations/de-DE/data/reusables/codespaces/release-stage.md
+++ b/translations/de-DE/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Hinweis:** {% data variables.product.prodname_codespaces %} befindet sich derzeit in der eingeschränkten Beta-Phase und kann sich jederzeit verändern. Während der Beta-Phase gibt {% data variables.product.prodname_dotcom %} keine Garantie für die Verfügbarkeit von {% data variables.product.prodname_codespaces %} ab. Weitere Informationen zum Beitritt zur Beta-Phase findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
+**Hinweis:** {% data variables.product.prodname_codespaces %} befindet sich derzeit in der eingeschränkten Beta-Phase und kann sich jederzeit verändern. Weitere Informationen zum Beitritt zur Beta-Phase findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
 
 {% endnote %}
diff --git a/translations/de-DE/data/reusables/codespaces/secret-precedence.md b/translations/de-DE/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..582b91c1aa
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/secrets-naming.md b/translations/de-DE/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..f19197f144
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+Die folgenden Regeln gelten für geheime Namen:
+
+* Geheime Namen dürfen nur alphanumerische Zeichen (`[a-z]`, `[A-Z]`, `[0-9]`) oder Unterstriche (`_`) enthalten. Leerzeichen sind nicht zulässig.
+* Geheime Namen dürfen nicht mit dem `GITHUB_` -Präfix beginnen.
+* Geheime Namen dürfen nicht mit einer Zahl beginnen.
+* Secret names are not case-sensitive.
+* Geheime Namen müssen auf der Ebene eindeutig sein, auf der sie erstellt werden.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/secrets-on-start.md b/translations/de-DE/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..c4a5bf3b41
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md b/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..90b3503dcd
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/source-control-display.md b/translations/de-DE/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..09917cd3c8
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. In the Activity Bar, click the **Source Control** view.
+
+  ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/type-port-label.md b/translations/de-DE/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..498c9eb752
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index 2a19d76e20..afb626e71c 100644
--- a/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-Du kannst alle Codespaces Deines Benutzerkontos unter [github.com/codespaces](https://github.com/codespaces) sehen.
+You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..a5e98437c0
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**.
+
+  !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md
index 9a73b1efb0..8291af52d4 100644
--- a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@ The following table shows, for each package manager:
 | Composer       | `composer`       | v1, v2                         |        **✓**         |       **✓**        |           |
 | Docker         | `docker`         | v1                             |        **✓**         |       **✓**        |           |
 | Hex            | `mix`            | v1                             |                      |       **✓**        |           |
-| elm-package    | `elm`            | v0.18, v0.19                   |        **✓**         |       **✓**        |           |
+| elm-package    | `elm`            | v0.19                          |        **✓**         |       **✓**        |           |
 | git submodule  | `gitsubmodule`   | N/A (no version)               |        **✓**         |       **✓**        |           |
 | GitHub Actions | `github-actions` | N/A (no version)               |        **✓**         |       **✓**        |           |
 | Go modules     | `gomod`          | v1                             |        **✓**         |       **✓**        |   **✓**   |
diff --git a/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md
index 3fe4e4585c..27cd562e73 100644
--- a/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@ Wenn Sie einen Pull Request an das Basis-Repository aus einem geforkten Reposito
 
 Workflows werden standardmäßig nicht für geforkte Repositorys ausgeführt. Du musst GitHub Actions auf der Registerkarte **Actions** (Aktionen) im geforkten Repository aktivieren.
 
+{% if currentVersion == "free-pro-team@latest"%}
+When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve running workflows on the pull request. For more information, see "[Approving workflow runs from public forks](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)."
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} The permissions for the `GITHUB_TOKEN` in forked repositories is read-only. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
 
 {% note %}
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md
index 62b5781e5e..aba1e29d39 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. Optional klicke auf **Get usage report** (Nutzungsbericht abrufen) um einen CSV-Bericht zur Speichernutzung für {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} an die primäre E-Mail-Adresse des Kontos zu senden. ![CSV-Bericht herunterladen](/assets/images/help/billing/actions-packages-report-download.png)
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![CSV-Bericht herunterladen](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md b/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md
index fe3e546cad..4c0fadd83b 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. Klicke unter „Billing overview“ (Abrechnungsübersicht) auf **Change to yearly billing** (In jährliche Abrechnung ändern) oder **Change to monthly billing** (In monatliche Abrechnung ändern). ![Schaltfläche zum Ändern des Plans in der Abrechnungsübersicht](/assets/images/help/billing/change-plan-duration-link.png)
+1. Under "Current monthly bill" or "Current yearly bill", click **Switch to yearly billing** or **Switch to monthly billing**. ![Schaltfläche zum Ändern des Plans in der Abrechnungsübersicht](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md b/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md
index 0edc906681..2121e37d1c 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. Wählen Sie bei einem Upgrade von {% data variables.product.prodname_free_team %} ein Produkt unter „Upgrading to“ (Upgrade auf) aus. ![Schaltfläche „Upgrade“](/assets/images/help/billing/upgrade-to-product.png)
+1. Under "Compare plans", you can compare the features of each plan. Depending on your current plan and what plan you have chosen, click either **Upgrade to Team** or **Upgrade to Enterprise**. ![Compare plans and upgrade](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md b/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md
index cc59354dc5..e38f282cf4 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. Unter „Billing information" (Abrechnungsinformationen) wähle die Zahlungsmethode mit Kreditkarte oder PayPal. ![Wechsel der Abrechnungszahlungsmethoden](/assets/images/help/billing/billing_switch_payments.png)
+1. Under "Payment method", choose to pay with a credit card or PayPal. ![Wechsel der Abrechnungszahlungsmethoden](/assets/images/help/billing/billing_switch_payments.png)
 1. Vervollständige das Formular mit den Zahlungsinformationen und klicke auf **Submit** (Einreichen).
diff --git a/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md b/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md
index 7b3c015e96..10b7c1870e 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. Klicken Sie neben „{% data variables.large_files.product_name_short %} Data“ ({% data variables.large_files.product_name_short %}-Daten) auf **Add more data** (Mehr Daten hinzufügen), oder verwenden Sie das Dropdownmenü „Edit“ (Bearbeiten), und klicken Sie auf **Add more data packs** (Mehr Datenpakete hinzufügen). ![Schaltfläche „Add more data" (Hinzufügen weiterer Daten)](/assets/images/help/billing/data-pack-purchase-more.png)
+1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**. ![Schaltfläche „Add more data" (Hinzufügen weiterer Daten)](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..4f2bd7bf2d
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. At the top of the page, under "Payment information", click **Manage spending limit**. ![Manage spending limit link](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md b/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md
index 828b584ab7..40aec809f4 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. Überprüfe unter „Billing overview“ (Abrechnungsübersicht), wann Deine nächste Zahlung fällig ist. ![Nächstes Abrechnungsdatum](/assets/images/help/billing/settings_billing_next_payment.png)
+1. At the top of the page, under "Next payment due", review when your next payment is due. ![Nächstes Abrechnungsdatum](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md b/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md
index 659e3a69cf..faf63f0292 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. Unter „Subscriptions" (Abonnements) überprüfe Deine ausstehenden Änderungen. ![Abschnitt „Subscriptions“ (Abonnements) der Abrechnungseinstellungen mit aufgelisteten ausstehenden Abonnementänderungen](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. Under "Current plan", review your pending changes. ![Abschnitt „Subscriptions“ (Abonnements) der Abrechnungseinstellungen mit aufgelisteten ausstehenden Abonnementänderungen](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md b/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md
index 01da18a726..d6384192fb 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. Klicke unter „Billing overview“ (Abrechnungsübersicht) auf **Update payment method** (Zahlungsmethode aktualisieren). ![Schaltfläche zum Aktualisieren der Zahlungsmethode](/assets/images/help/billing/update_payment_method.png)
+1. At the top of the page, under "Payment information", click **Update payment method**. ![Schaltfläche zum Aktualisieren der Zahlungsmethode](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md b/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md
index 2050a05ba4..aba4840ee5 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. Wenn Du ein Upgrade von {% data variables.product.prodname_free_team %} machst, klicke **Upgrade options** (Upgrade Optionen). Wenn Du ein Upgrade von {% data variables.product.prodname_team %} machst, verwende die **Edit** (Bearbeiten) Dropdownmenü und klicke auf **Upgrade** (Aktualisieren). ![Schaltfläche „Upgrade options" (Upgrade-Optionen)](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. Click **Upgrade** next to "Current plan".
diff --git a/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md b/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md
index 269cfc1efd..642d55da3b 100644
--- a/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. Klicke unter „Billing overview“ (Abrechnungsübersicht) auf **View payment history** (Zahlungsverlauf anzeigen). ![Link zum Anzeigen des Zahlungsverlaufs](/assets/images/help/billing/view-payment-history-link.png)
+1. At the top of the page, under "Next payment due", click **View payment history**. ![Link zum Anzeigen des Zahlungsverlaufs](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md b/translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..fdf80de12d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. Klicke auf **Add a domain** (Domäne hinzufügen). ![Schaltfläche „Add a domain“ (Domäne hinzufügen)](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/de-DE/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..93dbe99eb2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/github/getting-started-with-github/verifying-your-email-address).“
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/de-DE/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..0783f95521
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+You can confirm that the websites and email addresses listed on the profiles of any organization owned by your enterprise account are controlled by your enterprise by verifying the domains. Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %}
+
+Organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain.
+
+After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/domains-approving.md b/translations/de-DE/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/domains-removing.md b/translations/de-DE/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/domains-verifying.md b/translations/de-DE/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..1b6ce1e4a3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. In der Befehlsausgabe sollte Ihr neuer TXT-Eintrag aufgelistet werden.
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. Optionally, after the "Verified" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service. ![Badge „Verified“ (Verifiziert)](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..4087e5cdd0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+The domains can be inherited from the enterprise account or configured for the specific organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..c4a8bd0695
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. Klicke auf **Save** (Speichern).
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md
index 35420a6888..85644af45c 100644
--- a/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. Under "Settings", click **Verified domains**. !["Verified domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md
index 4948c5d8f2..db9b9c0037 100644
--- a/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1,2 +1,2 @@
-Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für eine bessere Leistung, verbesserte Sicherheit und neue Features <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">nimm ein Upgrade auf die neueste Version von GitHub Enterprise vor</a>.
-<a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">Wende Dich an den GitHub Enterprise-Support</a>, um Hilfe beim Upgrade zu erhalten.
+Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für eine bessere Leistung, verbesserte Sicherheit und neue Features <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">nimm ein Upgrade auf die neueste Version von GitHub Enterprise vor</a>.
+<a href="https://enterprise.github.com/support">Wende Dich an den GitHub Enterprise-Support</a>, um Hilfe beim Upgrade zu erhalten.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/de-DE/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..aea0a15c1e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
+
+Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
+
+Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
+
+| Benutzerlizenzen                                           |                           vCPUs |                         Arbeitsspeicher |                        Attached-Storage | Root-Storage |
+|:---------------------------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
+| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
+| 10–3000                                                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
+| 3000–5000                                                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
+| 5000–8000                                                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
+| 8000–10000+                                                | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md
index 4b1379243e..e7d45c6fb3 100644
--- a/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Warning**: Changing this setting will cause {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} to restart. You should time this change carefully, to minimize downtime.
+**Warning**: Changing this setting will cause user-facing services on {% data variables.product.prodname_ghe_server %} to restart. You should time this change carefully, to minimize downtime for users.
 
 {% endwarning %}
diff --git a/translations/de-DE/data/reusables/gated-features/actions-shared.md b/translations/de-DE/data/reusables/gated-features/actions-shared.md
index 2488b4d707..3267a9e91a 100644
--- a/translations/de-DE/data/reusables/gated-features/actions-shared.md
+++ b/translations/de-DE/data/reusables/gated-features/actions-shared.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} ist nicht verfügbar für private Repositorys, die im Besitz von Konten mit älteren Pro-Repository-Plänen sind. 
+{% data variables.product.prodname_actions %} ist verfügbar mit {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} für Organisationen, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, und {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} ist nicht verfügbar für private Repositorys, die im Besitz von Konten mit älteren Pro-Repository-Plänen sind. 
diff --git a/translations/de-DE/data/reusables/gated-features/code-scanning.md b/translations/de-DE/data/reusables/gated-features/code-scanning.md
index 775fa28256..3786dad893 100644
--- a/translations/de-DE/data/reusables/gated-features/code-scanning.md
+++ b/translations/de-DE/data/reusables/gated-features/code-scanning.md
@@ -1,5 +1,5 @@
-{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
-{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository.
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
 {%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_code_scanning_capc %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
 {%- else %}
diff --git a/translations/de-DE/data/reusables/gated-features/ghas.md b/translations/de-DE/data/reusables/gated-features/ghas.md
index fcf1b455c7..166bbffcbe 100644
--- a/translations/de-DE/data/reusables/gated-features/ghas.md
+++ b/translations/de-DE/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_GH_advanced_security %} is also included in {% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %} and in all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
+{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/gated-features/github-insights.md b/translations/de-DE/data/reusables/gated-features/github-insights.md
index 43548d9320..dcdd5fd060 100644
--- a/translations/de-DE/data/reusables/gated-features/github-insights.md
+++ b/translations/de-DE/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %} ist verfügbar mit {% data variables.product.prodname_ghe_one %}. Weitere Informationen findest Du unter „[Produkte von {% data variables.product.prodname_dotcom %}](/articles/githubs-products).“
+{% data variables.product.prodname_insights %} ist verfügbar mit {% data variables.product.prodname_ghe_one %}. Weitere Informationen findest Du unter „[Produkte von {% data variables.product.prodname_dotcom %}](/articles/githubs-products).“
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/gated-features/packages.md b/translations/de-DE/data/reusables/gated-features/packages.md
index 0cdea6d78f..d80ba419a8 100644
--- a/translations/de-DE/data/reusables/gated-features/packages.md
+++ b/translations/de-DE/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}.
+{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}.
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-{% data variables.product.prodname_registry %} ist nicht verfügbar für private Repositorys im Besitz von Konten mit älteren Pro-Repository-Plänen. {% data variables.product.prodname_registry %} ist verfügbar mit {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} für Organisationen, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, und {% data variables.product.prodname_ghe_one %}. {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_registry %} ist nicht verfügbar für private Repositorys im Besitz von Konten mit älteren Pro-Repository-Plänen. Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/secret-scanning.md b/translations/de-DE/data/reusables/gated-features/secret-scanning.md
index f67bcdf4e4..8ae85ccf2f 100644
--- a/translations/de-DE/data/reusables/gated-features/secret-scanning.md
+++ b/translations/de-DE/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_secret_scanning_caps %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
-{% endif %}
\ No newline at end of file
+{%- else %}
+{% data variables.product.prodname_secret_scanning_caps %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/github-actions/forked-write-permission.md b/translations/de-DE/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..3fe9804246
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+You can use the `permissions` key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the **Send write tokens to workflows from pull requests** option in the {% data variables.product.prodname_actions %} settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/github-actions/github-token-available-permissions.md b/translations/de-DE/data/reusables/github-actions/github-token-available-permissions.md
new file mode 100644
index 0000000000..4e5ca65fe7
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+Available scopes and access values:
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
+
+You can use the following syntax to define read or write access for all of the available scopes:
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/github-actions/github-token-permissions.md b/translations/de-DE/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..88604df1dc
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+The `GITHUB_TOKEN` secret is set to an access token for the repository each time a job in a workflow begins. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 0f75ff91a4..5579a7df46 100644
--- a/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. Die `GITHUB_TOKEN`-Umgebungsvariable wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gesetzt.
+Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. Die `GITHUB_TOKEN`-Umgebungsvariable wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gesetzt. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access granted to the `GITHUB_TOKEN`.{% endif %}
diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index b645d2a5ac..9f9310d182 100644
--- a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **Warnung**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“.
 
diff --git a/translations/de-DE/data/reusables/github-actions/supported-github-runners.md b/translations/de-DE/data/reusables/github-actions/supported-github-runners.md
index c0f898698b..72e125445a 100644
--- a/translations/de-DE/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/de-DE/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**Warning**: Ubuntu 16.04 is being deprecated. If any of your workflows use Ubuntu 16.04, migrate to Ubuntu 20.04 or 18.04. For more information, see [the blog post](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021).
+
+{% endwarning %}
+
 | Virtuelle Umgebung   | YAML-Workflow-Kennzeichnung          |
 | -------------------- | ------------------------------------ |
 | Windows Server 2019  | `windows-latest` oder `windows-2019` |
+| Windows Server 2016  | `windows-2016`                       |
 | Ubuntu 20.04         | `ubuntu-latest` oder `ubuntu-20.04`  |
 | Ubuntu 18.04         | `ubuntu-18.04`                       |
-| Ubuntu 16.04         | `ubuntu-16.04`                       |
 | macOS Big Sur 11.0   | `macos-11.0`                         |
 | macOS Catalina 10.15 | `macos-latest` or `macos-10.15`      |
diff --git a/translations/de-DE/data/reusables/github-actions/workflow-permissions-intro.md b/translations/de-DE/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..88382e0d54
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." You can choose between a restricted set of permissions as the default or a permissive setting. 
diff --git a/translations/de-DE/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/de-DE/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..14ee1f9279
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/reference/workflow-syntax-for-github-actions#permissions). 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/gpg/x-509-key.md b/translations/de-DE/data/reusables/gpg/x-509-key.md
index 43318a655b..e8a335d952 100644
--- a/translations/de-DE/data/reusables/gpg/x-509-key.md
+++ b/translations/de-DE/data/reusables/gpg/x-509-key.md
@@ -30,7 +30,7 @@ Du kannst [smimesign](https://github.com/github/smimesign) verwenden, um Commits
   $ git config --local gpg.program smimesign
   ```
   Wenn Du einen X.509-Schlüssel verwendest, der mit Deiner Beitragender-Identität übereinstimmt, kannst Du Commits und Tags signieren.
-4. Wenn Du keinen X.509-Schlüssel verwendest, der mit Deiner Beitragender-Identität übereinstimmt, solltest Du durch Ausführen des Befehls `smimesign --list-keys` die X.509-Schlüssel auflisten, für die Du über ein Zertifikat und über einen privaten Schlüssel verfügst.
+4. If you're not using an X.509 key that matches your committer identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
   ```shell
   $ smimesign --list-keys
   ```
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md b/translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..5054df65bf
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+Du kannst den Verifizierungsstatus Deines signierten Commits oder Tags auf {% data variables.product.product_name %} überprüfen und sehen, warum Deine Commit-Signaturen möglicherweise nicht verifiziert sind. Weitere Informationen finden Sie unter „[Verifizierungsstatus Ihrer Commit- und Tag-Signaturen überprüfen](/articles/checking-your-commit-and-tag-signature-verification-status)“.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..bb9ea14675
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Vigilant mode is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..ab91eef475
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| Status                      | Beschreibung                                                                                                                                                                                                                                                                             |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Verified**                | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.                                                                                                                                                       |
+| **Partially&nbsp;verified** | The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified. |
+| **Unverified**              | Any of the following is true:<br>- The commit is signed but the signature could not be verified.<br>- The commit is not signed and the committer has enabled vigilant mode.<br>- The commit is not signed and an author has enabled vigilant mode.<br>           |
diff --git a/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md
index dc7284910c..372a00863c 100644
--- a/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. Verwende das **Edit** (Bearbeiten) Dropdownmenü drop-down klicke auf **Cancel plan** (Plan kündigen). ![„Cancel" (Kündigen) Link im Abschnitt Marktplatz-Einkäufe in den Abrechnungseinstellungen Deines persönlichen Konto](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to cancel, use the **Edit** drop-down and click **Cancel plan**. ![„Cancel" (Kündigen) Link im Abschnitt Marktplatz-Einkäufe in den Abrechnungseinstellungen Deines persönlichen Konto](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index fc84080f79..b9901ac4a8 100644
--- a/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. Unter „Subscriptions" (Abonnements) verwende das Dropdownmenü Edit (Bearbeiten) neben der kostenlosen Testversion, die Du kündigen möchtest und klicke auf **Cancel plan** (Plan kündigen).
+1. Next to the free trial you'd like to cancel, use the **Edit** drop-down and click **Cancel plan**.
diff --git a/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md
index 44e842dc07..00fe9d916a 100644
--- a/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Verwende unter „Your subscriptions" (Deine Abonnements) neben der App, die Du herabstufen möchtest, das „Edit" (Bearbeiten) Dropdownmenü und klicke **Change plan** (Plan ändern) or **Cancel plan** (Plan kündigen). ![„Edit" (Bearbeiten) Link im Abschnitt Marktplatz-Käufe der Abrechnungseinstellungen Deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you'd like to downgrade, use the **Edit** drop-down and click **Change plan** or **Cancel plan**. ![„Edit" (Bearbeiten) Link im Abschnitt Marktplatz-Käufe der Abrechnungseinstellungen Deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md
index 40542d89be..f064783d69 100644
--- a/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Verwende das **Edit** (Bearbeiten) Dropdownmenü und klicke auf **Change plan** (Plan ändern). ![Dropdownmenü „Edit" (Bearbeiten) im Abschnitt Marktplatz-Käufe der Abrechnungseinstellungen Deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to upgrade, use the **Edit** drop-down and click **Change plan**. ![Dropdownmenü „Edit" (Bearbeiten) im Abschnitt Marktplatz-Käufe der Abrechnungseinstellungen Deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md b/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..e5d59aceea
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}issues, pulls requests, releases, security alerts, or discussions{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}issues, pull requests, releases, or discussions{% endif %}
diff --git a/translations/de-DE/data/reusables/notifications/email-restrictions-verification.md b/translations/de-DE/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..23423fd8d4
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/github/getting-started-with-github/verifying-your-email-address).“
diff --git a/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index 6b3de47d4c..dc6894c3f7 100644
--- a/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-You can choose the delivery method for notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+You can choose the delivery method and frequency of notifications about
+{% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts.
+{% else %}
+You can choose the delivery method for notifications about
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/add-a-domain.md b/translations/de-DE/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..8b77c5aa56
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. Klicke auf **Add a domain** (Domäne hinzufügen). ![Schaltfläche „Add a domain“ (Domäne hinzufügen)](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/billing_plans.md b/translations/de-DE/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..3b5a4c67fb
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. In your organization's Settings sidebar, click **Billing & plans**. ![Abrechungseinstellungen](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md b/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md
index 34652f8455..262b36c879 100644
--- a/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. To the right of the domain that's pending verification, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Continue verifying**. ![Schaltfläche „Continue verifying“ (Verifizierung fortsetzen) für Domain](/assets/images/help/organizations/continue-verifying-domain.png)
-10. Klicke auf **Verify domain** (Domäne verifizieren). ![Schaltfläche „Verify domain“ (Domain verifizieren)](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. Klicke auf **Verify** (Bestätigen). ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/organizations/domains-approve-domain.md b/translations/de-DE/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md b/translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/de-DE/data/reusables/organizations/verified-domains.md b/translations/de-DE/data/reusables/organizations/verified-domains.md
index 9e15ee5e87..9714304429 100644
--- a/translations/de-DE/data/reusables/organizations/verified-domains.md
+++ b/translations/de-DE/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. In der linken Seitenleiste klicke auf **Verified domains** (Überprüfte Domänen). ![Schaltfläche „Verified domains" (Überprüfte Domänen)](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md b/translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..b4e3019d43
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,30 @@
+### Paket-Erstellung in Workflows zur kontinuierlichen Integration
+
+Die Paket-Erstellung ist ein üblicher Bestandteil des Workflows bei der kontinuierlichen Integration oder bei der kontinuierlichen Auslieferung. Das Erstellen eines Pakets am Ende eines Workflows zur kontinuierlichen Integration kann während des Code-Reviews bei einem Pull-Request hilfreich sein.
+
+Nach dem Erstellen und Testen Deines Codes kann ein Paketierungsschritt ein lauf- oder bereitstellungsfähiges Artefakt erzeugen. Je nach Art der Anwendung, die Du erstellst, kann dieses Paket für manuelle Tests lokal heruntergeladen, Benutzern zum Herunterladen zur Verfügung gestellt oder in einer Staging- oder Produktionsumgebung bereitgestellt werden.
+
+Beispielsweise kann ein Workflow zur kontinuierlichen Integration für ein Java-Projekt `mvn package` ausführen, um eine JAR-Datei zu erstellen. Oder ein CI-Workflow für eine Node.js-Anwendung kann einen Docker-Container erzeugen.
+
+Wenn Du nun einen Pull-Request überprüfst, kannst Du Dir den Ablauf des Workflows ansehen und das erzeugte Artefakt herunterladen.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+Dadurch kannst Du den Code im Pull-Request auf Deinem Rechner ausführen, was beim Debuggen oder Testen des Pull-Requests helfen kann.
+
+### Workflows zum Veröffentlichen von Paketen
+
+Außer Paket-Artefakte zum Testen in einem Workflow zur kontinuierlichen Integration zum Testen hochzuladen, kannst Du auch Workflows erstellen, die Dein Projekt bauen und Pakete in einer Paket-Registry veröffentlichen.
+
+* **Publish packages to {% data variables.product.prodname_registry %}**
+  {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. Du kannst Deine Pakete entweder mit allen {% data variables.product.prodname_dotcom %} oder private Pakete nur mit Mitarbeitern oder einer Organisation teilen. For more information, see "[Introduction to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages)."
+
+  You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.
+
+* **Pakete in einer Paket-Registry veröffentlichen** Bei vielen Projekten werden neue Versionen immer in einer Paket-Registry veröffentlicht. Beispielsweise kann ein Projekt, das eine JAR-Datei erstellt, neue Versionen in das Zentral-Repository von Maven hochladen. Oder ein .NET-Projekt kann ein NuGet-Paket erzeugen und es in die NuGet-Galerie hochladen.
+
+  Du kannst dies automatisieren, indem Du einen Workflow erstellst, der bei jeder Release-Erstellung Pakete in einer Paket-Registry veröffentlicht. Weitere Informationen findest Du unter „[Releases erstellen](/github/administering-a-repository/creating-releases)“.
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..a02c0f89d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-packages.md b/translations/de-DE/data/reusables/package_registry/authenticate-packages.md
index a88d891c06..5abadfbc3d 100644
--- a/translations/de-DE/data/reusables/package_registry/authenticate-packages.md
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-packages.md
@@ -1,14 +1,7 @@
-You need an access token to publish, install, and delete packages. Du kannst ein persönliches Zugriffstoken verwenden, um Dich mit Deinem Benutzernamen direkt bei {% data variables.product.prodname_registry %} oder beim {% data variables.product.prodname_dotcom %}-API zu authentifizieren. When you create a personal access token, you can assign the token different scopes depending on your needs.
+You need an access token to publish, install, and delete packages.
 
-{% if currentVersion == "free-pro-team@latest" %}
-To authenticate using a
-{% data variables.product.prodname_actions %}-workflow:
-- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`.
-- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you can use a `GITHUB_TOKEN` or a personal access token. We strongly recommend you use a `GITHUB_TOKEN` to avoid unncessary access to your repositories.
+You can use a personal access token (PAT) to authenticate to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a PAT, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
 
-For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
-
-{% else %}
-To authenticate to
-{% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`.
-{% endif %}
+To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
+- `GITHUB_TOKEN` to publish packages associated with the workflow repository.
+- a PAT to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index 4c00bfc6cd..4773ebe404 100644
--- a/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. Using the CLI for your container type, sign in to the
-{% data variables.product.prodname_github_container_registry %} service at `ghcr.io`.
+{% data variables.product.prodname_container_registry %} service at `ghcr.io`.
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index 666a293400..38994e051e 100644
--- a/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -2,9 +2,9 @@
 
 PATs can grant broad access to your account. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}.
 
-To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
+To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
 
-For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
+For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-beta.md b/translations/de-DE/data/reusables/package_registry/container-registry-beta.md
index 6bd738198e..2b790bdbb1 100644
--- a/translations/de-DE/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)."
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use the {% data variables.product.prodname_container_registry %}, you must enable the feature preview. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" and "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
 {% endnote %}
diff --git a/translations/de-DE/data/reusables/package_registry/docker-vs-container-registry.md b/translations/de-DE/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..60ba872bf2
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**Comparing the Docker registry and the {% data variables.product.prodname_container_registry %}:**
+- The {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) offers improved performance for containers and will supercede the Docker registry in the future.
+- You can migrate your Docker images and workflows from the Docker registry  (`docker.pkg.github.com`)  to the {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) for granular permissions, container storage optimization, and more. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md
index 73a07a040b..67608dc1e2 100644
--- a/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will offer improved container support in a future {% data variables.product.product_name %} release.{% elsif currentVersion == "free-pro-team@latest" %} now offers improved container support. For more information, see "[About GitHub Container Registry](/packages/guides/about-github-container-registry)." To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/guides/migrating-to-github-container-registry-for-docker-images)" and "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)."{% endif %}
+**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will be superseded in a future {% data variables.product.product_name %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif currentVersion == "free-pro-team@latest" %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)." {% endif %}
 
 {% endwarning %}
diff --git a/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md
index 3b74dd6c78..3b8032849e 100644
--- a/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)."
+**Note:** Before you can use the {% data variables.product.prodname_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/package_registry/github-token-security-over-pat.md b/translations/de-DE/data/reusables/package_registry/github-token-security-over-pat.md
index bee4d1039b..ca6ffe0360 100644
--- a/translations/de-DE/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/de-DE/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_github_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
+The {% data variables.product.prodname_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
 
-For more information about `GITHUB_TOKEN`, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
+For more information about `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
diff --git a/translations/de-DE/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/de-DE/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..9bc7ee0d6e
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below use this type of permissions:
+- Docker registry (`docker.pkg.github.com`)
+- npm registry
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+The Container registry (`ghcr.io`) offers granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account.
+{% endif %}
+
+For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)"{% if currentVersion == "free-pro-team@latest" %} or "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."{% endif %}.
diff --git a/translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..1630cd5d98
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+If you have admin permissions to a container image, you can set the access permissions for the container image to private or public. Public images allow anonymous access and can be pulled without authentication or signing in via the CLI.
+
+As an admin, you can also grant access permissions for a container image that are separate from the permissions you've set at the organization and repository levels.
+
+For container images published and owned by a user account, you can give any person an access role. For container images published and owned by an organization, you can give any person or team in the organization an access role.
+
+| Berechtigung | Access description                                                                                                                               |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Lesen        | Can download package. <br> Can read package metadata.                                                                                      |
+| schreiben    | Can upload and download this package. <br> Can read and write package metadata.                                                            |
+| verwalten    | Can upload, download, delete, and manage this package. <br> Can read and write package metadata. <br> Can grant package permissions. |
+{% endif %}
diff --git a/translations/de-DE/data/reusables/profile/access_org.md b/translations/de-DE/data/reusables/profile/access_org.md
index 5493c7fd8c..9356bd4ee8 100644
--- a/translations/de-DE/data/reusables/profile/access_org.md
+++ b/translations/de-DE/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. Klicke auf der linken Seite Deiner Profilseite unter „Organizations" (Organisationen) auf das Symbol für Deine Organisation. ![Organisationssymbole](/assets/images/help/profile/profile_orgs_box.png)
+1. In the top right corner of {% data variables.product.prodname_dotcom %}, click your profile photo, then click **Your organizations**. ![Your organizations in the profile menu](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/profile/org_settings.md b/translations/de-DE/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..4c7f5b7078
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. Click **Settings** next to the organization. ![The settings button](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md b/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md
index 1455b80d18..32f5c49ac1 100644
--- a/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. In the left sidebar, under the user's profile picture, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block or report user**. ![Link „Block or report user" (Blockiere oder melde einen Benutzer)](/assets/images/help/profile/profile-block-or-report-button.png)
+1. In the left sidebar, below the user's profile information, click **Block or Report**. ![Block or report link](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md
index 2b8ba58bd7..41074379f9 100644
--- a/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -6,6 +6,6 @@ This example triggers the workflow every day at 5:30 and 17:30 UTC:
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/de-DE/data/reusables/repositories/request-changes-tips.md b/translations/de-DE/data/reusables/repositories/request-changes-tips.md
index ea5ce96ae2..2fb18a3216 100644
--- a/translations/de-DE/data/reusables/repositories/request-changes-tips.md
+++ b/translations/de-DE/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - Repository-Inhaber und -Administratoren können einen Pull Request sogar dann zusammenführen, wenn er keinen genehmigenden Review erhalten hat oder wenn ein Reviewer, der die Änderungen verlangt hat, die Organisation verlassen hat oder nicht verfügbar ist.
 - Wenn sowohl erforderliche Reviews wie das Verwerfen veralteter Reviews aktiviert sind und ein den Code verändernder Commit an den Branch eines genehmigten Pull Requests übermittelt wird, dann wird die Genehmigung verworfen. Der Pull Request muss erneut überprüft und genehmigt werden, bevor er zusammengeführt werden kann.
 - Wenn verschiedene offene Pull Requests jeweils einen Head-Branch aufweisen, der auf denselben Commit verweist, kannst Du sie nicht zusammenführen, wenn der Review bei einer oder bei beiden ausstehend ist oder abgelehnt wurde.
+- Pull request authors cannot approve their own pull requests.
 
 {% endtip %}
diff --git a/translations/de-DE/data/reusables/repositories/security-guidelines.md b/translations/de-DE/data/reusables/repositories/security-guidelines.md
index 8f484a76d4..3608c414e6 100644
--- a/translations/de-DE/data/reusables/repositories/security-guidelines.md
+++ b/translations/de-DE/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-Du kannst eine Sicherheitsrichtlinie erstellen, um Personen Anweisungen für das verantwortungsvolle Melden von Sicherheitslücken in Deinem Projekt zu geben. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zu Deinem Repository hinzufügen](/articles/adding-a-security-policy-to-your-repository).“
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+You can create a security policy to give people instructions for reporting security vulnerabilities in your project. Weitere Informationen findest Du unter „[Eine Sicherheitsrichtlinie zum Repository hinzufügen](/code-security/getting-started/adding-a-security-policy-to-your-repository)“.
 {% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md
index 58d37a45ad..2b642f5ebf 100644
--- a/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**. ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**.{% if currentVersion == "free-pro-team@latest" %} ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/beta.md b/translations/de-DE/data/reusables/secret-scanning/beta.md
index 714002d52b..6adcb7d57e 100644
--- a/translations/de-DE/data/reusables/secret-scanning/beta.md
+++ b/translations/de-DE/data/reusables/secret-scanning/beta.md
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} is in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of secret scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} was in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of {% data variables.product.prodname_secret_scanning %}, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
 
 
 {% endnote %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 2fb22e8c3c..3e52aeadb6 100644
--- a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| Partner                   | Supported secret                       | API slug                                 |
-| ------------------------- | -------------------------------------- | ---------------------------------------- |
-| –                         | JSON Web Token                         | json_web_token                         |
-| –                         | OAuth Client Credential                | api_credential_assignment              |
-| Adafruit IO               | Adafruit IO Key                        | adafruit_io_key                        |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID            | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Alibaba Cloud Access Key Secret        | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID               | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Amazon AWS Secret Access Key           | aws_secret_access_key                  |
-| Asana                     | Asana Personal Access Token            | asana_personal_access_token            |
-| Atlassian                 | Atlassian API Token                    | atlassian_api_token                    |
-| Atlassian                 | Atlassian JSON Web Token               | atlassian_jwt                            |
-| Azure                     | Azure DevOps Personal Access Token     | azure_devops_personal_access_token   |
-| Azure                     | Azure SAS Token                        | azure_sas_token                        |
-| Azure                     | Azure Service Management Certificate   | azure_management_certificate           |
-| Azure                     | Azure SQL Connection String            | azure_sql_connection_string            |
-| Azure                     | Azure Storage Account Key              | azure_storage_account_key              |
-| Clojars                   | Clojars Deploy Token                   | clojars_deploy_token                   |
-| CloudBees CodeShip        | CloudBees CodeShip Credential          | codeship_credential                      |
-| Databricks                | Databricks Access Token                | databricks_access_token                |
-| Discord                   | Discord Bot Token                      | discord_bot_token                      |
-| Doppler                   | Doppler Personal Token                 | doppler_personal_token                 |
-| Doppler                   | Doppler Service Token                  | doppler_service_token                  |
-| Doppler                   | Doppler CLI Token                      | doppler_cli_token                      |
-| Doppler                   | Doppler SCIM Token                     | doppler_scim_token                     |
-| Dropbox                   | Dropbox Access Token                   | dropbox_access_token                   |
-| Dropbox                   | Dropbox Short Lived Access Token       | dropbox_short_lived_access_token     |
-| Dynatrace                 | Dynatrace Access Token                 | dynatrace_access_token                 |
-| Dynatrace                 | Dynatrace Internal Token               | dynatrace_internal_token               |
-| Facebook                  | Facebook Access Token                  | facebook_access_token                  |
-| Finicity                  | Finicity App Key                       | finicity_app_key                       |
-| Frame.io                  | Frame.io JSON Web Token                | frameio_jwt                              |
-| Frame.io                  | Frame.io Developer Token               | frameio_developer_token                |
-| GitHub                    | GitHub SSH Private Key                 | github_ssh_private_key                 |
-| GitHub                    | GitHub Personal Access Token           | github_personal_access_token           |
-| GitHub                    | GitHub App Installation Access Token   | github_app_installation_access_token |
-| GoCardless                | GoCardless Live Access Token           | gocardless_live_access_token           |
-| GoCardless                | GoCardless Sandbox Access Token        | gocardless_sandbox_access_token        |
-| Google Cloud              | Google API Key                         | google_api_key                         |
-| Google Cloud              | Google Cloud Private Key ID            | google_cloud_private_key_id          |
-| Grafana                   | Grafana API Key                        | grafana_api_key                        |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token | terraform_api_token                    |
-| Hubspot                   | Hubspot API Key                        | hubspot_api_key                        |
-| Intercom                  | Intercom Access Token                  | intercom_access_token                  |
-| Lob                       | Lob Live API Key                       | lob_live_api_key                       |
-| Lob                       | Lob Test API Key                       | lob_test_api_key                       |
-| Mailchimp                 | Mailchimp API Key                      | mailchimp_api_key                      |
-| Mailgun                   | Mailgun API Key                        | mailgun_api_key                        |
-| npm                       | npm Access Token                       | npm_access_token                       |
-| NuGet                     | NuGet API Key                          | nuget_api_key                          |
-| Palantir                  | Palantir JSON Web Token                | palantir_jwt                             |
-| Postman                   | Postman API Key                        | postman_api_key                        |
-| Proctorio                 | Proctorio Consumer Key                 | proctorio_consumer_key                 |
-| Proctorio                 | Proctorio Linkage Key                  | proctorio_linkage_key                  |
-| Proctorio                 | Proctorio Registration Key             | proctorio_registration_key             |
-| Proctorio                 | Proctorio Secret Key                   | proctorio_secret_key                   |
-| Pulumi                    | Pulumi Access Token                    | pulumi_access_token                    |
-| PyPI                      | PyPI API Token                         | pypi_api_token                         |
-| RubyGems                  | RubyGems API Key                       | rubygems_api_key                       |
-| Samsara                   | Samsara API Token                      | samsara_api_token                      |
-| Samsara                   | Samsara OAuth Access Token             | samsara_oauth_access_token             |
-| SendGrid                  | SendGrid API Key                       | sendgrid_api_key                       |
-| Shopify                   | Shopify App Shared Secret              | shopify_app_shared_secret              |
-| Shopify                   | Shopify Access Token                   | shopify_access_token                   |
-| Shopify                   | Shopify Custom App Access Token        | shopify_custom_app_access_token      |
-| Shopify                   | Shopify Private App Password           | shopify_private_app_password           |
-| Slack                     | Slack API Token                        | slack_api_token                        |
-| Slack                     | Slack Incoming Webhook URL             | slack_incoming_webhook_url             |
-| Slack                     | Slack Workflow Webhook URL             | slack_workflow_webhook_url             |
-| SSLMate                   | SSLMate API Key                        | sslmate_api_key                        |
-| SSLMate                   | SSLMate Cluster Secret                 | sslmate_cluster_secret                 |
-| Stripe                    | Stripe API Key                         | stripe_api_key                         |
-| Stripe                    | Stripe Live API Secret Key             | stripe_live_secret_key                 |
-| Stripe                    | Stripe Test API Secret Key             | stripe_test_secret_key                 |
-| Stripe                    | Stripe Live API Restricted Key         | stripe_live_restricted_key             |
-| Stripe                    | Stripe Test API Restricted Key         | stripe_test_restricted_key             |
-| Tencent Cloud             | Tencent Cloud Secret ID                | tencent_cloud_secret_id                |
-| Twilio                    | Twilio Account String Identifier       | twilio_account_sid                     |
-| Twilio                    | Twilio API Key                         | twilio_api_key                         |
+| Partner | Supported secret | API slug |
+| ------- | ---------------- | -------- |
+|         |                  |          |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index ebc268a20d..701b6505b7 100644
--- a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| Partner                   | Supported secret                                                            |
-| ------------------------- | --------------------------------------------------------------------------- |
-| Adafruit IO               | Adafruit IO Key                                                             |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair                      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair                         |
-| Atlassian                 | Atlassian API Token                                                         |
-| Atlassian                 | Atlassian JSON Web Token                                                    |
-| Azure                     | Azure DevOps Personal Access Token | azure_devops_personal_access_token |
-| Azure                     | Azure SAS Token | azure_sas_token                                         |
-| Azure                     | Azure Service Management Certificate | azure_management_certificate       |
-| Azure                     | Azure SQL Connection String | azure_sql_connection_string                 |
-| Azure                     | Azure Storage Account Key | azure_storage_account_key                     |
-| Clojars                   | Clojars Deploy Token                                                        |
-| CloudBees CodeShip        | CloudBees CodeShip Credential                                               |
-| Databricks                | Databricks Access Token                                                     |
-| Datadog                   | Datadog API Key                                                             |
-| Discord                   | Discord Bot Token                                                           |
-| Doppler                   | Doppler Personal Token                                                      |
-| Doppler                   | Doppler Service Token                                                       |
-| Doppler                   | Doppler CLI Token                                                           |
-| Doppler                   | Doppler SCIM Token                                                          |
-| Dropbox                   | Dropbox Access Token                                                        |
-| Dropbox                   | Dropbox Short Lived Access Token                                            |
-| Dynatrace                 | Dynatrace Access Token                                                      |
-| Dynatrace                 | Dynatrace Internal Token                                                    |
-| Finicity                  | Finicity App Key                                                            |
-| Frame.io                  | Frame.io JSON Web Token                                                     |
-| Frame.io                  | Frame.io Developer Token                                                    |
-| GitHub                    | GitHub SSH Private Key                                                      |
-| GitHub                    | GitHub Personal Access Token                                                |
-| GitHub                    | GitHub App Installation Access Token                                        |
-| GoCardless                | GoCardless Live Access Token                                                |
-| GoCardless                | GoCardless Sandbox Access Token                                             |
-| Google Cloud              | Google API Key                                                              |
-| Google Cloud              | Google Cloud Private Key ID                                                 |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                                      |
-| Hubspot                   | Hubspot API Key                                                             |
-| Mailchimp                 | Mailchimp API Key                                                           |
-| Mailchimp                 | Mandrill API Key                                                            |
-| Mailgun                   | Mailgun API Key                                                             |
-| MessageBird               | MessageBird API Key                                                         |
-| npm                       | npm Access Token                                                            |
-| NuGet                     | NuGet API Key                                                               |
-| Palantir                  | Palantir JSON Web Token                                                     |
-| Plivo                     | Plivo Auth Token                                                            |
-| Postman                   | Postman API Key                                                             |
-| Proctorio                 | Proctorio Consumer Key                                                      |
-| Proctorio                 | Proctorio Linkage Key                                                       |
-| Proctorio                 | Proctorio Registration Key                                                  |
-| Proctorio                 | Proctorio Secret Key                                                        |
-| Pulumi                    | Pulumi Access Token                                                         |
-| PyPI                      | PyPI API Token                                                              |
-| RubyGems                  | RubyGems API Key                                                            |
-| Samsara                   | Samsara API Token                                                           |
-| Samsara                   | Samsara OAuth Access Token                                                  |
-| Shopify                   | Shopify App Shared Secret                                                   |
-| Shopify                   | Shopify Access Token                                                        |
-| Shopify                   | Shopify Custom App Access Token                                             |
-| Shopify                   | Shopify Private App Password                                                |
-| Slack                     | Slack API Token                                                             |
-| Slack                     | Slack Incoming Webhook URL                                                  |
-| Slack                     | Slack Workflow Webhook URL                                                  |
-| SSLMate                   | SSLMate API Key                                                             |
-| SSLMate                   | SSLMate Cluster Secret                                                      |
-| Stripe                    | Stripe Live API Secret Key                                                  |
-| Stripe                    | Stripe Test API Secret Key                                                  |
-| Stripe                    | Stripe Live API Restricted Key                                              |
-| Stripe                    | Stripe Test API Restricted Key                                              |
-| Tencent Cloud             | Tencent Cloud Secret ID                                                     |
-| Twilio                    | Twilio Account String Identifier                                            |
-| Twilio                    | Twilio API Key                                                              |
+| Partner                   | Supported secret                                       |
+| ------------------------- | ------------------------------------------------------ |
+| Adafruit IO               | Adafruit IO Key                                        |
+| Adobe                     | Adobe Device Token                                     |
+| Adobe                     | Adobe Service Token                                    |
+| Adobe                     | Adobe Short-Lived Access Token                         |
+| Adobe                     | Adobe JSON Web Token                                   |
+| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair |
+| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair    |
+| Atlassian                 | Atlassian API Token                                    |
+| Atlassian                 | Atlassian JSON Web Token                               |
+| Azure                     | Azure DevOps Personal Access Token                     |
+| Azure                     | Azure SAS Token                                        |
+| Azure                     | Azure Service Management Certificate                   |
+| Azure                     | Azure SQL Connection String                            |
+| Azure                     | Azure Storage Account Key                              |
+| Clojars                   | Clojars Deploy Token                                   |
+| CloudBees CodeShip        | CloudBees CodeShip Credential                          |
+| Databricks                | Databricks Access Token                                |
+| Datadog                   | Datadog API Key                                        |
+| Discord                   | Discord Bot Token                                      |
+| Doppler                   | Doppler Personal Token                                 |
+| Doppler                   | Doppler Service Token                                  |
+| Doppler                   | Doppler CLI Token                                      |
+| Doppler                   | Doppler SCIM Token                                     |
+| Dropbox                   | Dropbox Access Token                                   |
+| Dropbox                   | Dropbox Short Lived Access Token                       |
+| Dynatrace                 | Dynatrace Access Token                                 |
+| Dynatrace                 | Dynatrace Internal Token                               |
+| Finicity                  | Finicity App Key                                       |
+| Frame.io                  | Frame.io JSON Web Token                                |
+| Frame.io                  | Frame.io Developer Token                               |
+| GitHub                    | GitHub Personal Access Token                           |
+| GitHub                    | GitHub OAuth Access Token                              |
+| GitHub                    | GitHub Refresh Token                                   |
+| GitHub                    | GitHub App Installation Access Token                   |
+| GitHub                    | GitHub SSH Private Key                                 |
+| GoCardless                | GoCardless Live Access Token                           |
+| GoCardless                | GoCardless Sandbox Access Token                        |
+| Google Cloud              | Google API Key                                         |
+| Google Cloud              | Google Cloud Private Key ID                            |
+| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                 |
+| Hubspot                   | Hubspot API Key                                        |
+| Mailchimp                 | Mailchimp API Key                                      |
+| Mailchimp                 | Mandrill API Key                                       |
+| Mailgun                   | Mailgun API Key                                        |
+| MessageBird               | MessageBird API Key                                    |
+| npm                       | npm Access Token                                       |
+| NuGet                     | NuGet API Key                                          |
+| OpenAI                    | OpenAI API Key                                         |
+| Palantir                  | Palantir JSON Web Token                                |
+| Plivo                     | Plivo Auth Token                                       |
+| Postman                   | Postman API Key                                        |
+| Proctorio                 | Proctorio Consumer Key                                 |
+| Proctorio                 | Proctorio Linkage Key                                  |
+| Proctorio                 | Proctorio Registration Key                             |
+| Proctorio                 | Proctorio Secret Key                                   |
+| Pulumi                    | Pulumi Access Token                                    |
+| PyPI                      | PyPI API Token                                         |
+| RubyGems                  | RubyGems API Key                                       |
+| Samsara                   | Samsara API Token                                      |
+| Samsara                   | Samsara OAuth Access Token                             |
+| SendGrid                  | SendGrid API Key                                       |
+| Shopify                   | Shopify App Shared Secret                              |
+| Shopify                   | Shopify Access Token                                   |
+| Shopify                   | Shopify Custom App Access Token                        |
+| Shopify                   | Shopify Private App Password                           |
+| Slack                     | Slack API Token                                        |
+| Slack                     | Slack Incoming Webhook URL                             |
+| Slack                     | Slack Workflow Webhook URL                             |
+| SSLMate                   | SSLMate API Key                                        |
+| SSLMate                   | SSLMate Cluster Secret                                 |
+| Stripe                    | Stripe Live API Secret Key                             |
+| Stripe                    | Stripe Test API Secret Key                             |
+| Stripe                    | Stripe Live API Restricted Key                         |
+| Stripe                    | Stripe Test API Restricted Key                         |
+| Tencent Cloud             | Tencent Cloud Secret ID                                |
+| Twilio                    | Twilio Account String Identifier                       |
+| Twilio                    | Twilio API Key                                         |
diff --git a/translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..ecb8f968d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,5 @@
+{% if currentVersion == "free-pro-team@latest" %}
+For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."
+{% else %}
+For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/security/displayed-information.md b/translations/de-DE/data/reusables/security/displayed-information.md
index 02f38c36db..744735db2d 100644
--- a/translations/de-DE/data/reusables/security/displayed-information.md
+++ b/translations/de-DE/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
 When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
 
 - All the existing repositories will have the selected configuration.
-- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" %}
 - We use the permissions to scan for manifest files to apply the relevant services.
 - You'll see information on your dependency graph.
-- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} and raise pull requests{% endif %}. 
+- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} and create pull requests{% endif %}. 
diff --git a/translations/de-DE/data/reusables/supported-languages/C.md b/translations/de-DE/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/Cpp.md b/translations/de-DE/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/Cs.md b/translations/de-DE/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/go.md b/translations/de-DE/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..40bd61946e
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/java.md b/translations/de-DE/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/javascript.md b/translations/de-DE/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/php.md b/translations/de-DE/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/products-table-header.md b/translations/de-DE/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..743339ee69
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/python.md b/translations/de-DE/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/ruby.md b/translations/de-DE/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/scala.md b/translations/de-DE/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/supported-languages/typescript.md b/translations/de-DE/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/de-DE/data/reusables/user_settings/keeping_your_email_address_private.md
index 0e7e6386b3..972553ae13 100644
--- a/translations/de-DE/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/de-DE/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. Um Deine E-Mail-Adresse bei webbasierten Git-Operationen privat zu halten, klicke auf **Keep my email address private** (Meine E-Mail-Adresse privat halten). ![Bild des Kontrollkästchens, um Deine E-Mail-Adresse privat zu halten](/assets/images/help/settings/email_privacy.png)
+5. To keep your email address private when performing web-based Git operations, click **Keep my email addresses private**. ![Bild des Kontrollkästchens, um Deine E-Mail-Adresse privat zu halten](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/de-DE/data/reusables/user_settings/payment-info-link.md b/translations/de-DE/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..8d441f3be4
--- /dev/null
+++ b/translations/de-DE/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. At the top of the page, click **Payment information**. ![Payment information link](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md
index 5733bbbc0e..bd1f099030 100644
--- a/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,6 +1,6 @@
-| Schlüssel    | Typ      | Beschreibung                                                                                                                                                                    |
-| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`     | `string` | die Aktion, die durchgeführt wurde. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                           |
-| `Warnung`    | `Objekt` | The code scanning alert involved in the event.                                                                                                                                  |
-| `ref`        | `string` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty. |
-| `commit_oid` | `string` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty.    |
+| Schlüssel    | Typ      | Beschreibung                                                                                                                                                                   |
+| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `action`     | `string` | die Aktion, die durchgeführt wurde. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                          |
+| `Warnung`    | `Objekt` | The code scanning alert involved in the event.                                                                                                                                 |
+| `ref`        | `string` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty. |
+| `commit_oid` | `string` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty.    |
diff --git a/translations/de-DE/data/reusables/webhooks/create_properties.md b/translations/de-DE/data/reusables/webhooks/create_properties.md
index 5d4e029686..5efe622158 100644
--- a/translations/de-DE/data/reusables/webhooks/create_properties.md
+++ b/translations/de-DE/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| Schlüssel       | Typ      | Beschreibung                                                                                                                                                                                                                          |
-| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                        |
-| `ref_type`      | `string` | The type of Git ref object created in the repository. Can be either `branch` or `tag`.                                                                                                                                                |
-| `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
-| `Beschreibung`  | `string` | The repository's current description.                                                                                                                                                                                                 |
+| Schlüssel       | Typ      | Beschreibung                                                                                                                                                                                                                         |
+| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ref`           | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                       |
+| `ref_type`      | `string` | The type of Git ref object created in the repository. Can be either `branch` or `tag`.                                                                                                                                               |
+| `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
+| `Beschreibung`  | `string` | The repository's current description.                                                                                                                                                                                                |
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md
index d3e3719b0e..98019c071f 100644
--- a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| Schlüssel | Typ      | Beschreibung                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action`  | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. |
+| Schlüssel | Typ      | Beschreibung                                                                |
+| --------- | -------- | --------------------------------------------------------------------------- |
+| `action`  | `string` | die Aktion, die durchgeführt wurde. Can be one of:<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's tracking branch is synchronized with the source branch for the pull request, which happens when the source branch is updated.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md b/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md
index 2f62ffe8d8..bf99f9f71a 100644
--- a/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)".
+Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml
index 04b2b1656f..603504281d 100644
--- a/translations/de-DE/data/ui.yml
+++ b/translations/de-DE/data/ui.yml
@@ -20,7 +20,7 @@ homepage:
   version_picker: Version
 toc:
   getting_started: Erste Schritte
-  popular_articles: Popular
+  popular: Popular
   guides: Leitfäden
   whats_new: What's new
 pages:
@@ -54,14 +54,6 @@ contribution_cta:
   button: Make a contribution
   or: Oder,
   to_guidelines: learn how to contribute.
-enterprise_releases_list:
-  title: Enterprise Server Releases
-  currently_supported: Currently supported
-  currently_supported_message: See <a href="https://github.com/enterprise">GitHub Enterprise</a> for information about the latest release.
-  deprecated: Deprecated
-  deprecated_message: 'These docs remain available but are no longer maintained:'
-  deprecated_developer: Deprecated on developer.github.com
-  deprecated_developer_message: 'These docs remain available on the legacy <a href="https://developer.github.com">developer site</a> but are no longer maintained:'
 products:
   graphql:
     reference:
@@ -127,19 +119,36 @@ footer:
       press: Presse
       shop: Shop
 product_landing:
-  quick_start: Schnellstart
-  reference_guides: Reference guides
+  quickstart: Schnellstart
+  reference: Referenz
   overview: Übersicht
+  guides: Leitfäden
+  code_examples: Code examples
+  search_code_examples: Search code examples
+  show_more: Show more
+  explore_people_and_projects: Explore people and projects
+  sorry: Sorry, there is no result for
+  no_example: It looks like we don't have an example that fits your filter.
+  try_another: Try another filter or add your code example.
+  no_result: Sorry, there is no guide that match your filter.
+  learn: Learn how to add a code example
+  communities_using_discussions: Communities using discussions
+  add_your_community: Add your community
+  sponsor_community: GitHub Sponsors community
+  supported_releases: Supported releases
+  release_notes_for: Release notes for
+  upgrade_from: Upgrade from
+  browse_all_docs: Browse all docs
+  explore_release_notes: Explore release notes
 product_sublanding:
   start: Start
   start_path: Start path
-  learning_paths: '{{ allProducts[currentProduct].name }} learning paths'
+  learning_paths: '{{ productMap[currentProduct].name }} learning paths'
   learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject.
-  guides: '{{ allProducts[currentProduct].name }} guides'
+  guides: '{{ productMap[currentProduct].name }} guides'
   more_guides: more guides
   load_more: Load more guides
-  all_guides: 'All {{ allProducts[currentProduct].name }} guides'
-  no_result: Sorry, there is no guide that match your filter.
+  all_guides: 'All {{ productMap[currentProduct].name }} guides'
   filters:
     type: Typ
     topic: Topic
@@ -154,3 +163,10 @@ learning_track_nav:
   prevGuide: Previous guide
   nextGuide: Next guide
 contributor_callout: This article is contributed and maintained by
+toggle_images:
+  off: Images are off, click to show
+  on: Images are on, click to hide
+  hide_single: Hide image
+  show_single: Show image
+scroll_button:
+  scroll_to_top: Scroll to top
diff --git a/translations/de-DE/data/variables/codespaces_code_examples.yml b/translations/de-DE/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..00958245ab
--- /dev/null
+++ b/translations/de-DE/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.js sample project
+  description: Try a Node.js project with a custom dev container
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - development containers
+- 
+  title: Python sample project
+  description: Try a Python project with a custom dev container
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - development containers
+- 
+  title: Java sample project
+  description: Try a Java project with a custom dev container
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - development containers
+- 
+  title: Go sample project
+  description: Try a Go project with a custom dev container
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - development containers
+- 
+  title: Rust sample project
+  description: Try a Rust project with a custom dev container
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - development containers
+- 
+  title: PHP sample project
+  description: Try a PHP project with a custom dev container
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - development containers
diff --git a/translations/de-DE/data/variables/migrations.yml b/translations/de-DE/data/variables/migrations.yml
index 15201e4a03..61cd8c80be 100644
--- a/translations/de-DE/data/variables/migrations.yml
+++ b/translations/de-DE/data/variables/migrations.yml
@@ -4,4 +4,4 @@ user_migrations_intro: >-
 organization_migrations_intro: >-
   The organization migrations API lets you move a repository from GitHub to {% data variables.product.prodname_ghe_server %}.
 source_imports_intro: >-
-  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Server source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
+  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Version Control source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml
index 7a9e501a7b..7b98cd964f 100644
--- a/translations/de-DE/data/variables/product.yml
+++ b/translations/de-DE/data/variables/product.yml
@@ -56,6 +56,7 @@ prodname_pages: 'GitHub Pages'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'GitHub App'
@@ -77,8 +78,7 @@ prodname_debug: 'GitHub Debug'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
-prodname_github_container_registry: 'GitHub Container Registry'
-prodname_container_registry: 'container registry'
+prodname_container_registry: 'Container registry'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -91,7 +91,6 @@ prodname_advanced_security: 'Advanced Security'
 prodname_security_center: 'Security Center'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Visual Studio Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'GitHub Community Support'
@@ -139,9 +138,9 @@ product_url: >-
   {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %}
 pricing_url: 'https://github.com/pricing'
 signin_link: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Sign in](https://github.com/login){% else %}Sign in (`https://[hostname]/login`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Sign in](https://github.com/login){% else %}Anmelden („https://[hostname]/login“){% endif %}
 signout_link: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Sign out](https://github.com/logout){% else %}Sign out (`https://[hostname]/logout`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Sign out](https://github.com/logout){% else %}Abmelden („https://[hostname]/logout“){% endif %}
 raw_github_com: >-
   {% if currentVersion == "free-pro-team@latest" %}raw.githubusercontent.com{% else %}[hostname]/user/repo/raw{% endif %}
 #GitHub Enterprise Server past versions
diff --git a/translations/de-DE/data/variables/release_candidate.yml b/translations/de-DE/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/de-DE/data/variables/release_candidate.yml
+++ b/translations/de-DE/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/de-DE/data/variables/sponsors_user_examples.yml b/translations/de-DE/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..92800edaf3
--- /dev/null
+++ b/translations/de-DE/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chayn helps women experiencing abuse find the right information and support they need to take control of their lives.
+- 
+  user: foosel
+  description: '👋 I''m Gina, and I''m mostly known for being the creator and main developer of OctoPrint 🐙.'
+- 
+  user: dayhaysoos
+  description: What's up? I'm Nick. I'm an engineer who has a new-found passion for removing friction from the e-commerce developer experience.
+- 
+  user: yyx990803
+  description: I'm working fulltime on Vue.js, a frontend JavaScript framework for building web applications, and Vite, a modern web build tool.
+- 
+  user: calebporzio
+  description: '🚶‍♂️I left my day job in Jan 2019 to pursue open-source. Since then, I''ve built Laravel Livewire, AlpineJS, and a bunch of other stuff.'
+- 
+  user: kjaymiller
+  description: Hi Y'all I'm Jay! 👋 I'm a Marine Corps Veteran turned developer that's been actively coding since 2014. I'm also involved in the productivity space where I can be found helping people with automations for some of their favorite apps and tools.
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index 12365ae0af..f8b71c78df 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
index 071c4f6bd9..3b07930b53 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
index 3019757e0e..1b1ad9b1c7 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md
@@ -222,14 +222,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-javascript-action@v1.1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
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 13951e5ebd..24358a47c9 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
@@ -58,7 +58,7 @@ inputs:
 
 Cuando especificas una entrada para una acción en un archivo de flujo de trabajo o usas un valor de entrada predeterminado, {% data variables.product.prodname_dotcom %} crea una variable de entorno para la entrada con el nombre `INPUT_<VARIABLE_NAME>`. La variable de entorno creada convierte los nombre de entrada en letras mayúscula y reemplaza los espacios con los caracteres `_`.
 
-For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables.
+Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `octocatEyeColor`, el código de acción pudo leer los valores de las entradas utilizando las variables de ambiente `INPUT_NUMOCTOCATS` y `INPUT_OCTOCATEYECOLOR`.
 
 #### `inputs.<input_id>`
 
@@ -78,7 +78,7 @@ For example, if a workflow defined the `numOctocats` and `octocatEyeColor` input
 
 #### `inputs.<input_id>.deprecationMessage`
 
-**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives.
+**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 (salidas)`
 
@@ -151,7 +151,7 @@ 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. The application specified with the [`using`](#runsusing) syntax will execute this file. La acción `pre:` siempre se ejecuta predeterminadamente pero puedes invalidarla utilizando [`pre-if`](#pre-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. La aplicación que se especifica con la sintaxis [`using`](#runsusing) ejecutará este archivo. La acción `pre:` siempre se ejecuta predeterminadamente pero puedes invalidarla utilizando [`pre-if`](#pre-if).
 
 En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`:
 
@@ -171,12 +171,12 @@ En este ejemplo, `cleanup.js` se ejecuta únicamente en los ejecutores basados e
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 #### `publicación`
 
-**Opcional** Te permite ejecutar un script al final de un job, una vez que se haya completado la acción `main:`. Por ejemplo, puedes utilizar `post:` para finalizar algunos procesos o eliminar los archivos innecesarios. The application specified with the [`using`](#runsusing) syntax will execute this file.
+**Opcional** Te permite ejecutar un script al final de un job, una vez que se haya completado la acción `main:`. Por ejemplo, puedes utilizar `post:` para finalizar algunos procesos o eliminar los archivos innecesarios. La aplicación que se especifica con la sintaxis [`using`](#runsusing) ejecutará este archivo.
 
 En este ejemplo, la acción `post:` ejecuta un script llamado `cleanup.js`:
 
@@ -197,7 +197,7 @@ Por ejemplo, este `cleanup.js` únicamente se ejecutará en ejecutores basados e
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 ### `runs` para acciones con pasos de ejecución compuestos
@@ -286,7 +286,7 @@ runs:
 
 **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 la puedes invalidar utilizando [`pre-if`](#pre-if).
 
-The application specified with the [`using`](#runsusing) syntax will execute this file.
+La aplicación que se especifica con la sintaxis [`using`](#runsusing) ejecutará este archivo.
 
 En este ejemplo, la acción `pre.entrypoint:` ejecuta un script llamado `setup.sh`:
 
@@ -295,7 +295,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
@@ -323,7 +323,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/es-ES/content/actions/guides/about-continuous-integration.md b/translations/es-ES/content/actions/guides/about-continuous-integration.md
index 6e11b2d863..149ba1dc79 100644
--- a/translations/es-ES/content/actions/guides/about-continuous-integration.md
+++ b/translations/es-ES/content/actions/guides/about-continuous-integration.md
@@ -48,11 +48,13 @@ Adicionalmente a ayudarte a configurar los flujos de trabajo de IC para tu proye
 Para obtener una definición de términos comunes, consulta "[Conceptos básicos para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)."
 
 ### Lenguajes compatibles
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} ofrece plantillas de flujo de trabajo de IC para varios lenguajes y marcos de trabajo.
 
 Busca en la lista completa de plantillas de flujo de trabajo para IC que ofrece {% data variables.product.product_name %} en el repositorio [actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) de {% if currentVersion == "free-pro-team@latest" %}{% else %} repositorio `actions/starter-workflows` en {% data variables.product.product_location %}{% endif %}.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### Saltarse las ejecuciones de código
 
 Si quieres prevenir temporalmente que un flujo de trabajo se active, puedes agregar una instrucción de salto en el mensaje de la confirmación. Los flujos de trabajo `on: push` o `on: pull_request` que se activarían, pueden no hacerlo si agregas cualquiera de las secuencias siguientes al mensaje de confirmación en una confirmación de subida o de encabezado (HEAD) de una solicitud de cambios:
@@ -72,6 +74,7 @@ No podrás fusionar la solicitud de cambios si tu repositorio se cofiguró para
 **Nota:** Las instrucciones de salto solo aplican para los eventos de `push` y `pull_request`. Por ejemplo, el agregar `[skip ci]` a un mensaje de confirmación no impedirá que se ejecute un flujo de trabajo que se activa con `on: pull_request_target`.
 
 {% endnote %}
+{% endif %}
 
 ### Notificaciones para ejecuciones de flujo de trabajo
 
diff --git a/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md b/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md
index 5fc49ad931..8fab49cab0 100644
--- a/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/es-ES/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,39 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### Acerca de los pasos de empaquetado
-
-Un paso de empaquetado es una parte común de un flujo de trabajo de integración continua o entrega continua. Después de construir y probar tu aplicación, se produce un artefacto ejecutable o desplegable en la forma de un paquete. Por ejemplo, un flujo de trabajo de integración continua para un proyecto Java puede ejecutar `mvn package` para generar un archivo JAR. O un flujo de trabajo de CI para una aplicación Node.js puede crear un contenedor Docker.
-
-Según el tipo de aplicación que estás construyendo, este paquete se puede descargar de forma local para pruebas manuales, disponible para que los usuarios los descarguen o se implementen en un entorno de ensayo o producción.
-
-### Empaquetado en flujos de trabajo de integración continua
-
-Crear un paquete al final de un flujo de trabajo de integración continua puede ayudar durante las revisiones de código en una solicitud de extracción. Después de construir y probar tu código, un paso de empaquetado puede generar un artefacto ejecutable o desplegable. Luego, tu flujo de trabajo puede tomar ese artefacto y cargarlo como parte del flujo de trabajo.
-
-Ahora, cuando revises una solicitud de extracción, podrás ver la ejecución del flujo de trabajo y descargar el artefacto que se produjo.
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-Esto te permitirá ejecutar el código en la solicitud de extracción en tu máquina, lo que puede ayudar con la depuración o la prueba de la solicitud de extracción.
-
-### Flujos de trabajo para publicar paquetes
-
-Además de cargar artefactos de empaquetado para las pruebas en un flujo de trabajo de integración continua, puedes crear flujos de trabajo que construyan tu proyecto y publiquen paquetes en un registro de paquete.
-
-* **Publicar paquetes en el {% data variables.product.prodname_registry %}**
-  El {% data variables.product.prodname_registry %} puede actuar como un servicio de hospedaje para paquetes para varios tipos de éstos. Puedes elegir compartir tus paquetes con todos los {% data variables.product.prodname_dotcom %}, o paquetes privados para compartir con los colaboradores o una organización. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)".
-
-  Es posible que desees publicar paquetes para el {% data variables.product.prodname_registry %} en cada subida a la rama predeterminada. Esto permitirá que los programadores en tu proyecto siempre puedan ejecutar y probar la última construcción fuera del principal fácilmente, instalándolo desde {% data variables.product.prodname_registry %}.
-
-* **Publicar paquetes en un registro de paquetes**  
-  Para muchos proyectos, publicar en un registro de paquete se realiza cada vez que se lanza una nueva versión de un proyecto. Por ejemplo, un proyecto que produce un archivo JAR puede cargar nuevos lanzamientos en el repositorio central de Maven. O bien, un proyecto de .NET puede generar un paquete NuGet y cargarlo en la galería de NuGet.
-
-  Puedes automatizar esto creando un flujo de trabajo que publique paquetes en un registro de paquetes en cada creación de lanzamiento. Para obtener más información, consulta "[Crear lanzamientos](/github/administering-a-repository/creating-releases)."
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### Leer más
 
diff --git a/translations/es-ES/content/actions/guides/adding-labels-to-issues.md b/translations/es-ES/content/actions/guides/adding-labels-to-issues.md
index 29f0a8e621..f60d41474e 100644
--- a/translations/es-ES/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/es-ES/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
 2. {% data reusables.actions.make-workflow-file %}
 3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,15 +38,18 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
-4. Personaliza los parámetros en tu flujo de trabajo:
+
+4. Personaliza los parámetros en tu archivo de flujo de trabajo:
    - Cambia el valor de `add-labels` a la lista de etiquetas que quieras agregar a la propuesta. Separa las etiquetas con comas. Por ejemplo, `"help wanted, good first issue"`. Para obtener más información sobre las etiquetas, consulta la sección "[Administrar etiquetas](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)".
 5. {% data reusables.actions.commit-workflow %}
 
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md
index 1cd6741490..f8a85e2a53 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-ant.md
@@ -71,7 +71,7 @@ jobs:
 Este flujo de trabajo realiza los siguientes pasos:
 
 1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
+2. El paso `setup-java` configura el JDK de Java 11 por Adoptium.
 3. El paso "Build with Ant" (Construir con Ant) ejecuta el objetivo predeterminado en tu `build.xml` en el modo no interactivo.
 
 Las plantillas de flujo de trabajo predeterminadas son excelentes puntos de inicio cuando creas tu flujo de trabajo de construcción y prueba, y puedes personalizar la plantilla para adaptarla a las necesidades de tu proyecto.
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md
index 9e29e53251..538179b7d7 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-gradle.md
@@ -71,7 +71,7 @@ jobs:
 Este flujo de trabajo realiza los siguientes pasos:
 
 1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
+2. El paso `setup-java` configura el JDK de Java 11 por Adoptium.
 3. El paso "Build with Gradle" (construir con Gradle) ejecuta el script contenedor `gradlew` para asegurar que tu código se cree, las pruebas pasen y se pueda crear un paquete.
 
 Las plantillas de flujo de trabajo predeterminadas son excelentes puntos de inicio cuando creas tu flujo de trabajo de construcción y prueba, y puedes personalizar la plantilla para adaptarla a las necesidades de tu proyecto.
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md
index 2b43c58851..586e462bab 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-java-with-maven.md
@@ -71,7 +71,7 @@ jobs:
 Este flujo de trabajo realiza los siguientes pasos:
 
 1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
+2. El paso `setup-java` configura el JDK de Java 11 por Adoptium.
 3. El paso "Build with Maven" (Construir con Maven) ejecuta el `paquete` destino de Maven en modo no interactivo para garantizar que tu código se compile, se superen las pruebas y se pueda crear un paquete.
 
 Las plantillas de flujo de trabajo predeterminadas son excelentes puntos de inicio cuando creas tu flujo de trabajo de construcción y prueba, y puedes personalizar la plantilla para adaptarla a las necesidades de tu proyecto.
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-net.md b/translations/es-ES/content/actions/guides/building-and-testing-net.md
index 3cbbae8d49..4db775339d 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-net.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-net.md
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ Puedes configurar tu job para que utilice una versión específica de .NET, tal
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} cuenta
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,7 +139,7 @@ Para obtener más información, consulta la sección "[Almacenar las dependencia
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
@@ -171,7 +171,7 @@ Puedes usar los mismos comandos que usas de forma local para construir y probar
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 Puedes configurar tu flujo de trabajo para publicar tu paquete de Dotnet a un registro de paquetes cuando pasen tus pruebas de IC. Puedes utilizar secretos de los repositorios para almacenar cualquier token o credenciales que se necesiten para publicar tu binario. El siguiente ejemplo crea y publica un paquete en el {% data variables.product.prodname_registry %} utilizando `dotnet core cli`.
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md b/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md
index 2bdd8aba28..f83ea8bfc2 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ Te recomendamos que tengas una comprensión básica de Node.js, YAML, las opcion
 
 {% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Node.js que funcionará para la mayoría de los proyectos Node.js. Esta guía incluye ejemplos de npm y Yarn que puedes usar para personalizar la plantilla. Para obtener más información, consulta la [Plantilla de flujo de trabajo Node.js](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio.
+Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. El flujo de trabajo que se muestra a continuación asume que la rama predeterminada de tu repositorio es `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,14 +119,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 Si no especificas una versión de Node.js,
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-powershell.md b/translations/es-ES/content/actions/guides/building-and-testing-powershell.md
index d29867246f..829149bee4 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-powershell.md
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ El siguiente ejemplo instala `PSScriptAnalyzer` y lo utiliza para limpiar todos
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-python.md b/translations/es-ES/content/actions/guides/building-and-testing-python.md
index 76567dd519..5f7c54c859 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-python.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-python.md
@@ -58,25 +58,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Lint with flake8
-      run: |
-        # stop the build if there are Python syntax errors or undefined names
-        flake8 . --Count--Select = E9, F63, F7, F82--show-Source--Statistics
-        # exit-zero trata todos los errores como advertencias. El editor de GitHub es 127 chars de ancho
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - name: Test with pytest
-      run: |
-        pytest
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -117,14 +117,14 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -144,17 +144,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # Semantic version range syntax or exact version of a Python version
-        python-version: '3.x'
-        # Optional - x64 or x86 architecture, defaults to x64
-        architecture: 'x64'
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -373,25 +373,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Install pip and pytest
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # Use always() to always run this step to publish test results when there are test failures
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -413,22 +413,22 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 {% endraw %}
 
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-ruby.md b/translations/es-ES/content/actions/guides/building-and-testing-ruby.md
index ea9fb26f76..939a0af37e 100644
--- a/translations/es-ES/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/es-ES/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ Te recomendamos que tengas una comprensión básica de Ruby, YAML, las opciones
 
 {% data variables.product.prodname_dotcom %} proporciona una plantilla de flujo de trabajo de Ruby que funcionará con la mayoría de los proyectos de Ruby. Para obtener más información, consulta la sección [Plantilla de flujo de trabajo de Ruby](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio.
+Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio. El flujo de trabajo que se muestra a continuación asume que la rama predeterminada de tu repositorio es `main`.
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,7 +264,6 @@ Puedes configurar tu flujo de trabajo para publicar tu paquete de Ruby en cualqu
 
 Puedes almacenar todos los tokens de acceso o credenciales necesarios para publicar tu paquete utilizando secretos del repositorio. Elsiguiente ejemplo crea y publica un paquete en el `Registro de Paquetes de Github` y en `RubyGems`.
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
@@ -272,46 +271,48 @@ name: Ruby Gem
 on:
   # Manually publish
   workflow_dispatch:
-  # Alternatively, publish whenever changes are merged to the default branch.
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-swift.md b/translations/es-ES/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..cda07aee06
--- /dev/null
+++ b/translations/es-ES/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Building and testing Swift
+intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introducción
+
+This guide shows you how to build and test a Swift package.
+
+{% if currentVersion == "github-ae@latest" %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. Para obtener las instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tenga instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)".
+{% else %}{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swift packages. For a full list of up-to-date software and the preinstalled versions of Swift and Xcode, see "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### Prerrequisitos
+
+Ya debes estar familiarizado con la sintaxis de YAML y con cómo se utiliza con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
+
+We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
+
+### Starting with the Swift workflow template
+
+{% data variables.product.prodname_dotcom %} provides a Swift workflow template that should work for most Swift projects, and this guide includes examples that show you how to customize this template. For more information, see the [Swift workflow template](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+Para comenzar rápidamente, agrega la plantilla al directorio `.github/workflows` de tu repositorio.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Specifying a Swift version
+
+To use a specific preinstalled version of Swift on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `fwal/setup-swift` action. This action finds a specific version of Swift from the tools cache on the runner and adds the necessary binaries to `PATH`. These changes will persist for the remainder of a job. For more information, see the [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) action.
+
+If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+
+The examples below demonstrate using the `fwal/setup-swift` action.
+
+#### Using multiple Swift versions
+
+You can configure your job to use a multiple versions of Swift in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Using a single specific Swift version
+
+You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### Construir y probar tu código
+
+You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/es-ES/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/es-ES/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..fb5fce60d0
--- /dev/null
+++ b/translations/es-ES/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Building and testing Xamarin applications
+intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Xamarin application.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introducción
+
+This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto.
+
+{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### Prerrequisitos
+
+We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML, workflow configuration options, and how to create a workflow file. Para obtener más información, consulta:
+
+- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
+- "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Bulding Xamarin.iOS apps
+
+The example below demonstrates how to change the default Xamarin bundle and build  a Xamarin.iOS application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Bulding Xamarin.Android apps
+
+The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### Especificar una versión de .NET
+
+Para utilizar una versión preinstalada de .NET Core SDK en un ejecutor hospedado en {% data variables.product.prodname_dotcom %}, utiliza la acción `setup-dotnet`. Esta acción encuentra una versión específica de .NET desde el caché de las herramientas en cada ejecutor y agrega los binarios necesarios a `PATH`. Estos cambios persistirán para el recordatorio del job.
+
+La acción `setup-dotnet` es la forma recomendada de utilizar .NET con las {% data variables.product.prodname_actions %}, porque garantiza el comportamiento consistente a través de diversos ejecutores y diversas versiones de .NET. Si estás utilizando un ejecutor auto-hospedado, debes instalar .NET y agregarlo a `PATH`. Para obtener más información, consulta la acción [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk).
diff --git a/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index 8a34b2d0bd..176043fd52 100644
--- a/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/es-ES/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ Para más información, consulta [`actions/cache`](https://github.com/actions/ca
 
 - `key`: **Obligatorio** La clave que se crea cuando se guarda una memoria caché y la clave utilizada para buscar una caché. Puede ser cualquier combinación de variables, valores de contexto, cadenas estáticas y funciones. Las claves tienen una longitud máxima de 512 caracteres y las claves más largas que la longitud máxima provocarán un error en la acción.
 - `path`: **Obligatorio** La ruta del archivo en el ejecutor para almacenar en caché o restaurar. La ruta debe ser absoluta o relativa al directorio de trabajo.
-  - Con la `v2` de la acción `cache`, puedes especificar una ruta única, o rutas múltiples en forma de lista. Las rutas pueden ser tanto directorios o solo archivos, y los patrones estilo glob son compatibles.
+  - Las rutas pueden ser tanto directorios o solo archivos, y los patrones estilo glob son compatibles.
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. Por ejemplo:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - Con la `v1` de la acción `cache`, solo se puede utilizar una ruta única, la cual debe ser un directorio. No puedes almacenar en caché un archivo único.
 - `restore-keys`: **Opcional** Una lista ordenada de claves alternativas que se usan para encontrar la caché si no se ha producido ningún hit de caché para `key`.
 
@@ -82,30 +91,29 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-    - name: Cache node modules
-      uses: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm` on Linux/macOS
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - name: Install Dependencies
-      run: npm install
+      - name: Install Dependencies
+        run: npm install
 
-    - name: Build
-      run: npm build
-
-    - name: Test
-      run: npm test
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/es-ES/content/actions/guides/closing-inactive-issues.md b/translations/es-ES/content/actions/guides/closing-inactive-issues.md
index 31828bc8d6..359099bb78 100644
--- a/translations/es-ES/content/actions/guides/closing-inactive-issues.md
+++ b/translations/es-ES/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ En el tutorial, prmero crearás un archivo de flujo de trabajo que utilice la [a
 2. {% data reusables.actions.make-workflow-file %}
 3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ En el tutorial, prmero crearás un archivo de flujo de trabajo que utilice la [a
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,10 +51,10 @@ En el tutorial, prmero crearás un archivo de flujo de trabajo que utilice la [a
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
-4. Personaliza los parámetros en tu flujo de trabajo:
+
+4. Personaliza los parámetros en tu archivo de flujo de trabajo:
    - Cambia el valor de `on.schedule` para que dicte cuándo quieres que se ejecute este flujo de trabajo. En el ejemplo anterior, el flujo de trabajo se ejecutará diario a la 1:30 UTC. Para obtener más información sobre los flujos de trabajo que has programado, consulta la sección "[Ejemplos programados](/actions/reference/events-that-trigger-workflows#scheduled-events)".
    - Cambia el valor de `days-before-issue-stale` a la cantidad de días de inactividad para esperar antes de que la acción `actions/stale` etiquete una propuesta. Si quieres que esta acción jamás etiquete las propuestas, configura el valor en `-1`.
    - Cambia el valor de `days-before-issue-close` a la cantidad de días sin actividad a esperar antes de que la acción `actions/stale` cierre una propuesta. Si quieres que esta acción jamás cierre las propuestas, configura el valor en `-1`.
diff --git a/translations/es-ES/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/es-ES/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index 49a64f51f9..09447e6606 100644
--- a/translations/es-ES/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/es-ES/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
 2. {% data reusables.actions.make-workflow-file %}
 3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **Make sure to reference this issue in your pull request.** :sparkles: Thank you for your contribution! :sparkles:
     ```
-    {% endraw %}
+
 4. Personaliza los parámetros en tu archivo de flujo de trabajo:
    - Reemplaza a `help-wanted` en `if: github.event.label.name == 'help-wanted'` con la etiqueta sobre la cual quieres actuar. Si quieres actuar sobre más de una etiqueta, separa las condiciones con `||`. Por ejemplo, `if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` comentará cada que se agreguen las etiquetas `bug` o `fix me` a una propuesta.
    - Cambia el valor de `body` al comentario que quieras agregar. El lenguaje de marcado enriquecido de GitHub es compatible. Para obtener más información sobre el lenguaje de marcado, consulta la sección "[Sintaxis básica de escritura y formato](/github/writing-on-github/basic-writing-and-formatting-syntax)".
diff --git a/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md b/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md
index 9584047c63..71e653c2cd 100644
--- a/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/es-ES/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### Introducción
 
-En esta guía se muestran ejemplos de flujos de trabajo que configuran un contenedor de servicios mediante la imagen `postgres` de Docker Hub. El flujo de trabajo ejecuta un script para crear un cliente de PostgreSQL y rellenarlo con datos. Para probar que el flujo de trabajo crea y rellena el cliente de PostgreSQL, el script imprime los datos del cliente en la consola.
+En esta guía se muestran ejemplos de flujos de trabajo que configuran un contenedor de servicios mediante la imagen `postgres` de Docker Hub. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -46,44 +46,45 @@ También puede ser útil tener un conocimiento básico de YAML, la sintaxis para
 name: PostgreSQL service example
 on: push
 
-Jobs:
-  # Etiqueta del trabajo del contenedor
+jobs:
+  # Label of the container job
   container-job:
-    # Los contenedores deben ejecutarse en sistemas operativos basados en Linux
-    runs-on: Ubuntu-latest
-    # Imagen de Docker Hub que ejecuta 'container-job ' en
-    el contenedor: node:10.18-jessie
+    # Containers must run in Linux based operating systems
+    runs-on: ubuntu-latest
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
 
-    # Contenedores de servicios para ejecutar con servicios de 'container-job ':
-      # Etiqueta usada para acceder al contenedor de servicios
-      Postgres:
-        # Imagen de Docker Hub
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
+      postgres:
+        # Docker Hub image
         image: postgres
-        # Proporciona la contraseña para Postgres
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # Establece chequeos de estado para esperar hasta que postgres inicie las
-        opciones: >-
+        # Set health checks to wait until postgres has started
+        options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
 
-    Steps:
-      # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json'
-      # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Ejecuta un script que crea un cliente de PostgreSQL, rellena
-        # el cliente con datos y recupera datos
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
         run: node client.js
-        # Variable de entorno utilizada por el script 'client.js' para crear un nuevo cliente de PostgreSQL.
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
           POSTGRES_HOST: Postgres
@@ -125,21 +126,21 @@ jobs:
 
 ```yaml{:copy}
 steps:
-  # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
+  # Downloads a copy of the code in your repository before running CI tests
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json'
-  # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Ejecuta un script que crea un cliente de PostgreSQL, rellena
-    # el cliente con datos y recupera datos
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
     run: node client.js
-    # Variable de entorno utilizada por el script 'client.js ' para crear
-    # un nuevo cliente de PostgreSQL.
+    # Environment variable used by the `client.js` script to create
+    # a new PostgreSQL client.
     env:
       # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
       POSTGRES_HOST: Postgres
@@ -162,46 +163,47 @@ Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás as
 name: PostgreSQL Service Example
 on: push
 
-Jobs:
-  # Etiqueta del trabajo del ejecutador
+jobs:
+  # Label of the runner job
   runner-job:
-    # Debes usar un entorno Linux cuando uses contenedores de servicios o trabajos del contenedor
+    # You must use a Linux environment when using service containers or container jobs
     runs-on: ubuntu-latest
 
-    # Contenedores de servicios para ejecutar con servicios de 'runner-job':
-      # Etiqueta usada para acceder al contenedor de servicios
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
       postgres:
-        # Imagen de Docker Hub
+        # Docker Hub image
         image: postgres
-        # Proporciona la contraseña para postgres
+        # Provide the password for postgres
         env:
-          POSTGRES_PASSWORD: Postgres
-        # Establece chequeos de estado para esperar hasta que postgres inicie las
-        opciones: >-
+          POSTGRES_PASSWORD: postgres
+        # Set health checks to wait until postgres has started
+        options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Asigna el puerto tcp 5432 del contenedor de servicios al host
-          -5432:5432
+          # Maps tcp port 5432 on service container to the host
+          - 5432:5432
 
-    Steps:
-      # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json'
-      # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Ejecuta un script que crea un cliente de PostgreSQL, rellena
-        # el cliente con datos y recupera datos
-        Run: node client.js
-        # Variable de entorno utilizada por el script 'client.js' para crear
-        # un nuevo cliente de PostgreSQL.
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
+        run: node client.js
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
           POSTGRES_HOST: localhost
@@ -250,21 +252,21 @@ jobs:
 
 ```yaml{:copy}
 steps:
-  # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
+  # Downloads a copy of the code in your repository before running CI tests
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Realiza una instalación limpia de todas las dependencias en el archivo 'package.json'
-  # Para obtener más información, consulta https://docs.npmjs.com/cli/ci.html
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Ejecuta un script que crea un cliente de PostgreSQL, rellena
-    # el cliente con datos y recupera datos
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
     run: node client.js
-    # Variable de entorno utilizada por el script 'client.js ' para crear
-    # un nuevo cliente de PostgreSQL.
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
       POSTGRES_HOST: localhost
@@ -278,9 +280,9 @@ steps:
 
 ### Probar el contenedor de servicios de PostgreSQL
 
-Puedes probar tu flujo de trabajo usando el siguiente script, que crea un cliente de PostgreSQL y agrega una tabla nueva con algunos datos de marcador de posición. Luego, el script le imprime los valores almacenados en el cliente de PostgreSQL al terminal. Tu script puede usar el lenguaje que quieras, pero este ejemplo usa Node.js y el módulo npm de `pg`. Para obtener más información, consulta el [módulo npm de pg](https://www.npmjs.com/package/pg).
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. Tu script puede usar el lenguaje que quieras, pero este ejemplo usa Node.js y el módulo npm de `pg`. Para obtener más información, consulta el [módulo npm de pg](https://www.npmjs.com/package/pg).
 
-Puedes modificar *client.js* para incluir cualquier operación de PostgreSQL que necesite tu flujo de trabajo. En este ejemplo, el script crea la instancia de cliente de PostgreSQL, crea una tabla, agrega datos de marcador de posición y luego recupera los datos.
+Puedes modificar *client.js* para incluir cualquier operación de PostgreSQL que necesite tu flujo de trabajo. In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -316,11 +318,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-El script crea un nuevo `Client` (cliente) de PostgreSQL, que acepta un `host` y un parámetro de `port` (puerto). El script usa las variables de entorno `POSTGRES_HOST` y `POSTGRES_PORT` para establecer la dirección IP y el puerto del cliente. Si `host` y `port` no están definidos, el host predeterminado es `localhost` y el puerto predeterminado es 5432.
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. Si `host` y `port` no están definidos, el host predeterminado es `localhost` y el puerto predeterminado es 5432.
 
-El script crea una tabla y la rellena con datos de marcador de posición. Para probar que la base de datos de PostgreSQL contenga los datos, el script imprime los contenidos de la tabla en el registro de la consola.
+El script crea una tabla y la rellena con datos de marcador de posición. To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-Cuando ejecutes este flujo de trabajo, debes ver el siguiente resultado en el paso "Connect to PostgreSQL" (Conectar con PostgreSQL) que confirma que creaste el cliente de PostgreSQL y agregaste los datos:
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index 5d3e4228d6..8e7be17e0b 100644
--- a/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/es-ES/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ El siguiente flujo de trabajo de ejemplo demuestra cómo construir una imagen de
 
 Asegúrate de que proporcionas tus propios valores para todas las variables en la clave `env` del flujo de trabajo.
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### Recursos adicionales
 
diff --git a/translations/es-ES/content/actions/guides/index.md b/translations/es-ES/content/actions/guides/index.md
index c7b7453a65..d65bd90126 100644
--- a/translations/es-ES/content/actions/guides/index.md
+++ b/translations/es-ES/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/es-ES/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/es-ES/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
index 7815e8c7db..80697e58b9 100644
--- a/translations/es-ES/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
+++ b/translations/es-ES/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
@@ -1,6 +1,6 @@
 ---
-title: Installing an Apple certificate on macOS runners for Xcode development
-intro: 'You can sign Xcode apps within your continuous integration (CI) workflow by installing an Apple code signing certificate on {% data variables.product.prodname_actions %} runners.'
+title: Instalar un certificado de Apple en ejecutores de macOS para el desarrollo de Xcode
+intro: 'Puedes firmar apps de Xcode dentro de tu flujo de integración continua (IC) si instalas un certificado de firma de código de Apple en los ejecutores de {% data variables.product.prodname_actions %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -18,7 +18,7 @@ topics:
 
 ### Introducción
 
-This guide shows you how to add a step to your continuous integration (CI) workflow that installs an Apple code signing certificate and provisioning profile on {% data variables.product.prodname_actions %} runners. This will allow you to sign your Xcode apps for publishing to the Apple App Store, or distributing it to test groups.
+Esta guía te muestra cómo agregar un paso a tu flujo de trabajo de integración continua (IC), el cual instale un certificado de firma de código de Apple y perfil de aprovisionamiento en los ejecutores de {% data variables.product.prodname_actions %}. Esto te permitirá firmar tus apps de Xcode para publicarlas en la App Store de Apple o distribuirlas a los grupos de prueba.
 
 ### Prerrequisitos
 
@@ -27,49 +27,49 @@ Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.
 - "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 - "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
 
-You should have an understanding of Xcode app building and signing. For more information, see the [Apple developer documentation](https://developer.apple.com/documentation/).
+Debes entender la forma en la que la app de Xcode crea y firma las apps. Para obtener más información, consulta la [Documentación de desarrollador de Apple](https://developer.apple.com/documentation/).
 
-### Creating secrets for your certificate and provisioning profile
+### Crear secretos para tu certificado y perfil de aprovisionamiento
 
-The signing process involves storing certificates and provisioning profiles, transferring them to the runner, importing them to the runner's keychain, and using them in your build.
+El proceso de inicio de sesión involucra almacenar certificados y perfiles de aprovisionamiento, transferirlos al ejecutor, importarlos en el keychain del ejecutor y utilizarlos en tu compilación.
 
-To use your certificate and provisioning profile on a runner, we strongly recommend that you use {% data variables.product.prodname_dotcom %} secrets. For more information on creating secrets and using them in a workflow, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+Para utilizar tu certificado y perfil de aprovisionamiento en un ejecutor, te recomendamos fuertemente que utilices los secretos de {% data variables.product.prodname_dotcom %}. Para obtener más información sobre cómo crear secretos y utilizarlos en un flujo de trabajo, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)".
 
-Create secrets in your repository or organization for the following items:
+Crea secretos en tu repositorio u organización para los siguientes elementos:
 
-* Your Apple signing certificate.
+* Tu certificado de inicio de sesión de Apple.
 
-  - This is your `p12` certificate file. For more information on exporting your signing certificate from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/dev154b28f09).
+  - Este es tu archivo de certificado `p12`. Para obtener más información sobre cómo exportar tu certificado de inicio de sesión desde Xcode, consulta la [documentación de Xcode](https://help.apple.com/xcode/mac/current/#/dev154b28f09).
 
-  - You should convert your certificate to Base64 when saving it as a secret. In this example, the secret is named `BUILD_CERTIFICATE_BASE64`.
+  - Deberías convertir tu certificado en Base64 cuando lo guartes como secreto. En este ejemplo, el secreto se llama `BUILD_CERTIFICATE_BASE64`.
 
-  - Use the following command to convert your certificate to Base64 and copy it to your clipboard:
+  - Utiliza el siguiente comando para convertir tu certificado en Base64 y cópialo a tu portapapeles:
 
     ```shell
     base64 <em>build_certificate</em>.p12 | pbcopy
     ```
-* The password for your Apple signing certificate.
-  - In this example, the secret is named `P12_PASSWORD`.
+* La contraseña de tu certificado de inicio de sesión de Apple.
+  - En este ejemplo, el secreto se llama `P12_PASSWORD`.
 
-* Your Apple provisioning profile.
+* Tu perfil de aprovisionamiento de Apple.
 
-  - For more information on exporting your provisioning profile from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/deva899b4fe5).
+  - Para obtener más información sobre cómo exportar tu perfil de aprovisionamiento desde Xcode, consulta la [documentación de Xcode](https://help.apple.com/xcode/mac/current/#/deva899b4fe5).
 
-  - You should convert your provisioning profile to Base64 when saving it as a secret. In this example, the secret is named `BUILD_PROVISION_PROFILE_BASE64`.
+  - Debes convertir tu perfil de aprovisionamiento a Base64 cuando lo guardas como secreto. En este ejemplo, el secreto se llama `BUILD_PROVISION_PROFILE_BASE64`.
 
-  - Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard:
+  - Utiliza el siguiente comando para convertir tu perfil de aprovisionamiento en Base64 y cópialo a tu portapapeles:
 
     ```shell
     base64 <em>provisioning_profile.mobileprovision</em> | pbcopy
     ```
 
-* A keychain password.
+* Una contraseña de keychain.
 
-  - A new keychain will be created on the runner, so the password for the new keychain can be any new random string. In this example, the secret is named `KEYCHAIN_PASSWORD`.
+  - Se creará una keychain nueva en el ejecutor para que la contraseña de esta pueda ser cualquier secuencia aleatoria. En este ejemplo, el secreto se llama `KEYCHAIN_PASSWORD`.
 
-### Add a step to your workflow
+### Agrega un paso a tu flujo de trabajo
 
-This example workflow includes a step that imports the Apple certificate and provisioning profile from the {% data variables.product.prodname_dotcom %} secrets, and installs them on the runner.
+Este flujo de trabajo de ejemplo incluye un paso que importa el certificado de Apple y perfil de aprovisionamiento desde los secretos de {% data variables.product.prodname_dotcom %} y los instala en el ejecutor.
 
 {% raw %}
 ```yaml{:copy}
@@ -116,13 +116,13 @@ jobs:
 ```
 {% endraw %}
 
-### Required clean-up on self-hosted runners
+### Limpieza requerida en los ejecutores auto-hospedados
 
-{% data variables.product.prodname_dotcom %}-hosted runners are isolated virtual machines that are automatically destroyed at the end of the job execution. This means that the certificates and provisioning profile used on the runner during the job will be destroyed with the runner when the job is completed.
+Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} son máquinas virtuales aisladas que se destruyen automáticamente al final de la ejecución del job. Esto significa que los certificados y prefil de aprovisionamiento que se utiliza en el ejecutor durante el job se destruirán con el ejecutor cuando se complete dicho job.
 
-On self-hosted runners, the `$RUNNER_TEMP` directory is cleaned up at the end of the job execution, but the keychain and provisioning profile might still exist on the runner.
+En los ejecutores auto-hospedados, el directorio `$RUNNER_TEMP` se limpia al final de la ejecución del job, pero la keychain y archivo de aprovisionamiento podrían seguir existiendo en el ejecutor.
 
-If you use self-hosted runners, you should add a final step to your workflow to help ensure that these sensitive files are deleted at the end of the job. The workflow step shown below is an example of how to do this.
+Si utilizas ejecutores auto-programados, deberás agregar un paso final a tu flujo de trabajo para ayudar a asegurarte que estos archivos sensibles se borren al final del job. El paso de flujo de trabajo que se muestra a continuación es un ejemplo de como hacer esto.
 
 {% raw %}
 ```yaml
diff --git a/translations/es-ES/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/es-ES/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..62446f3ef9
--- /dev/null
+++ b/translations/es-ES/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Administrar las GitHub Actions con GitHub CLI
+intro: 'Puedes utilizar el {% data variables.product.prodname_cli %} para interactuar con las {% data variables.product.prodname_actions %}.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Configurar {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### Administrar las {% data variables.product.prodname_actions %} con el {% data variables.product.prodname_cli %}
+
+Para ver todos los comandos disponibles relacionados con las {% data variables.product.prodname_actions %}, ejecuta `gh actions`.
+
+Para obtener más información sobre cómo utilizar los comandos en escenarios específicos, consulta los siguientes procedimientos:
+
+- "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[Ejecutar un flujo de trabajo manualmente](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)"
+- "[Descargar artefactos de flujos de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[Utilizar bitácoras de ejecución de flujos de trabajo](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[Inhabilitar y habilitar un flujo de trabajo](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/es-ES/content/actions/guides/publishing-docker-images.md b/translations/es-ES/content/actions/guides/publishing-docker-images.md
index 1baa626aef..e9a0ef17a5 100644
--- a/translations/es-ES/content/actions/guides/publishing-docker-images.md
+++ b/translations/es-ES/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ También puede que encuentres útil el tener un entendimiento básico de lo sigu
 
 - "[Secretos cifrados](/actions/reference/encrypted-secrets)"
 - "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)"
-- "[Configurar Docker para su uso con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)"
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### Acerca de la configuración de imágenes
 
@@ -98,7 +98,6 @@ Las opciones de `build-push-action` requeridas para {% data variables.product.pr
 * `registry`: Debe configurarse como `docker.pkg.github.com`.
 * `repository`: Debe configurarse en el formato `OWNER/REPOSITORY/IMAGE_NAME`. Por ejemplo, para una imagen nombrada como `octo-image` almacenada en {% data variables.product.prodname_dotcom %} en `http://github.com/octo-org/octo-repo`, la opción de `repository` debe configurarse como `octo-org/octo-repo/octo-image`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -107,21 +106,23 @@ on:
 jobs:
   push_to_registry:
     name: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,7 +132,6 @@ En un solo flujo de trabajo, puedes publicar tu imagen de Docker en varios regis
 
 El siguiente flujo de trabajo de ejemplo utiliza los pasos de `build-push-action` de las secciones anteriores ("[Publicar imágenes en Docker Hub](#publishing-images-to-docker-hub)" y "[Publicar imágenes en {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para crear un solo flujo de trabajo que cargue ambos registros.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -140,26 +140,28 @@ on:
 jobs:
   push_to_registries:
     name: Push Docker image to multiple registries
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to Docker Hub
         uses: docker/build-push-action@v1
         with:
-          username: ${{ secrets.DOCKER_USERNAME }}
-          password: ${{ secrets.DOCKER_PASSWORD }}
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
           repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 El flujo de trabajo anterior revisa el repositorio de {% data variables.product.prodname_dotcom %} y utiliza la acción `build-push-action` dos veces para crear y cargar la imagen de Docker a Docker Hub y {% data variables.product.prodname_registry %}. Para ambos pasos, configura la opción `build-push-action` [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) para etiquetar automáticamente la imagen de Docker con la referencia de Git para el evento del flujo de trabajo. Este flujo de trabajo se desencadena cuando se publica un lanzamiento de {% data variables.product.prodname_dotcom %}, así que la referencia para ambos registros será la etiqueta de Git para el lanzamiento.
diff --git a/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md
index 4731ffcadd..a4bfe6b927 100644
--- a/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/es-ES/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ Para obtener más información acerca de la creación de un flujo de trabajo de
 
 También puede ser útil tener un entendimiento básico de lo siguiente:
 
-- "[Configurar npm para usar con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Variables de ambiente](/actions/reference/environment-variables)"
 - "[Secretos cifrados](/actions/reference/encrypted-secrets)"
 - "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)"
@@ -108,7 +108,7 @@ Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo
 
 Puedes definir un nuevo repositorio de Maven en el bloque de publicación de tu _build.gradle_ que apunte a {% data variables.product.prodname_registry %}.  En esa configuración de repositorio, también puedes aprovechar las variables de entorno establecidas en tu ejecución de flujo de trabajo de CI.  Puedes usar la variable de entorno `GITHUB_ACTOR` como nombre de usuario y puedes establecer la variable de entorno `GITHUB_TOKEN` con tu `GITHUB_TOKEN` secreto.
 
-El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectura y escritura para paquetes en el repositorio donde se ejecuta el flujo de trabajo. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+{% data reusables.github-actions.github-token-permissions %}
 
 Por ejemplo, si tu organización se llama "octocat" y tu repositorio se llama "hello-world", entonces la configuración {% data variables.product.prodname_registry %} en _build.gradle_ tendría un aspecto similar al ejemplo a continuación.
 
@@ -133,7 +133,6 @@ publishing {
 
 Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven al ejecutar el comando `gradle publish`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Ejecuta el comando `gradle publish` comando para publicar en {% data variables.product.prodname_registry %}. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto.
+1. Ejecuta el comando `gradle publish` comando para publicar en {% data variables.product.prodname_registry %}. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% endif %}
 
    Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
@@ -199,7 +200,6 @@ publishing {
 
 Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven y {% data variables.product.prodname_registry %} al ejecutar el comando `gradle publish`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Ejecuta el comando `gradle publish` para publicar en el repositorio Maven `OSSRH` y {% data variables.product.prodname_registry %}. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto.
+1. Ejecuta el comando `gradle publish` para publicar en el repositorio Maven `OSSRH` y {% data variables.product.prodname_registry %}. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. La variable de entorno `GITHUB_TOKEN` se establecerá con el contenido del `GITHUB_TOKEN` secreto. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% endif %}
 
    Para obtener más información acerca del uso de secretos en tu flujo de trabajo, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md b/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md
index dbc009ece4..6ceefe6d16 100644
--- a/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/es-ES/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ Para obtener más información acerca de la creación de un flujo de trabajo de
 
 También puede ser útil tener un entendimiento básico de lo siguiente:
 
-- "[Configurar npm para usar con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Variables de ambiente](/actions/reference/environment-variables)"
 - "[Secretos cifrados](/actions/reference/encrypted-secrets)"
 - "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)"
@@ -112,9 +112,9 @@ Este flujo de trabajo realiza los siguientes pasos:
 
 Cada vez que creas un lanzamiento nuevo, puedes desencadenar un flujo de trabajo para publicar tu paquete. El flujo de trabajo en el ejemplo a continuación se ejecuta cuando el evento `lanzamiento` desencadena con tipo `creado`. El flujo de trabajo publica el paquete en el {% data variables.product.prodname_registry %} si se superan las pruebas de CI. Para obtener más información acerca del evento `release`, consulta "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release)".
 
-En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción instala la versión determinada del JDK en el `PATH` y configura un _settings.xml_ de Maven para publicar el paquete en el {% data variables.product.prodname_registry %}. El _settings.sml_ generado define la autenticación para un servidor con una `id` de `github`, utilizando la variable de entorno `GITHUB_ACTOR` como nombre de usuario y la variable de entorno `GITHUB_TOKEN` como contraseña.
+En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción instala la versión determinada del JDK en el `PATH` y configura un _settings.xml_ de Maven para publicar el paquete en el {% data variables.product.prodname_registry %}. El _settings.sml_ generado define la autenticación para un servidor con una `id` de `github`, utilizando la variable de entorno `GITHUB_ACTOR` como nombre de usuario y la variable de entorno `GITHUB_TOKEN` como contraseña. Se le asigna el valor del secreto especial `GITHUB_TOKEN` a la variable de ambiente `GITHUB_TOKEN`.
 
-El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectura y escritura para paquetes en el repositorio donde se ejecuta el flujo de trabajo. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+{% data reusables.github-actions.github-token-permissions %}
 
 Para un proyecto basado en Maven, puedes hacer uso de estas configuraciones creando un repositorio de distribución en tu archivo _pom.xml_ con una `id` de `github` que apunta a tu extremo {% data variables.product.prodname_registry %}.
 
@@ -137,7 +137,6 @@ Por ejemplo, si tu organización se llama "octocat", y tu repositorio se llama "
 
 Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en {% data variables.product.prodname_registry %} haciendo uso del _settings.xml_ generado automáticamente.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Este flujo de trabajo realiza los siguientes pasos:
 
@@ -173,7 +174,6 @@ Puedes publicar tus paquetes en el repositorio central de Maven y en el {% data
 
 Asegúrate de que tu archivo _pom.xml_ incluya un repositorio de administración de distribución para tu repositorio de {% data variables.product.prodname_dotcom %} y para tu proveedor de repositorios centrales de Maven. Por ejemplo, si implementas el repositorio central a través del proyecto de alojamiento de OSSRH, es posible que desees especificarlo en un repositorio de administración de distribución con la `id` establecida en `ossrh`, y que desees especificar el {% data variables.product.prodname_registry %} en un repositorio de administración de distribución con la `id` establecida en `github`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Este flujo de trabajo llama a la acción `setup-java` dos veces.  Cada vez que la acción `setup-java` se ejecuta, sobrescribe el archivo _settings.xml_ de Maven para publicar paquetes.  Para la autenticación en el repositorio, el archivo _settings.xml_ hace referencia a la `id` del repositorio de administración de distribución y al nombre de usuario y contraseña.
 
diff --git a/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md b/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md
index a4defc878b..8b1978aad4 100644
--- a/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/es-ES/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ Para obtener más información acerca de la creación de un flujo de trabajo de
 
 También puede ser útil tener un entendimiento básico de lo siguiente:
 
-- "[Configurar npm para usar con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Variables de ambiente](/actions/reference/environment-variables)"
 - "[Secretos cifrados](/actions/reference/encrypted-secrets)"
 - "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)"
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ Sin embargo, si no proporcionas la clave del `repository`, entonces el repositor
 
 #### Autenticarse en el repositorio de destino
 
-Para autenticarte en el registro de {% data variables.product.prodname_registry %} en tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN` desde tu repositorio. Este se crea automáticamente y tiene permisos tanto de _lectura_ como de _escritura_ para los paquetes en el repositorio en donde se ejecuta el flujo de trabajo. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)".
+Para realizar operaciones autenticadas en el registro {% data variables.product.prodname_registry %} de tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 Si quieres publicar tu paquete en un repositorio diferente, debes utilizar un token de acceso personal (PAT) que tenga permisos de escritura en los paquetes del repositorio destino. Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)".
 
@@ -120,7 +120,6 @@ Si quieres publicar tu paquete en un repositorio diferente, debes utilizar un to
 
 Este ejemplo almacena el secreto `GITHUB_TOKEN` en la variable de entorno `NODE_AUTH_TOKEN`. Cuando la acción `setup-node` crea un archivo *.npmrc*, hace referencia al token de la variable de entorno `NODE_AUTH_TOKEN`.
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 La acción `setup-node` crea un archivo *.npmrc* en el ejecutor. Cuando utilizas la entrada `scope` a la acción `setup-node`, el archivo *.npmrc* incluye el prefijo de alcance. Por defecto, la acción `setup-node` establece el ámbito en el archivo *.npmrc* en la cuenta que contiene ese archivo de flujo de trabajo.
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,13 +197,13 @@ Si publicas un paquete en ambos registros, tendrás que asegurarte de que tu pre
 
 Asegúrate de que tu archivo *package.json* incluya el ámbito de tu repositorio de {% data variables.product.prodname_dotcom %} y el registro de npm. Por ejemplo, si planeas publicar un paquete en el repositorio `octocat/npm-hello-world-test` en {% data variables.product.prodname_dotcom %} y https://www.npmjs. om/package/@octocat/npm-hello-world-test, el nombre en tu archivo *package.json* debería ser `"name": "@octocat/npm-hello-world-test"`.
 
-Para realizar operaciones autenticadas en el registro {% data variables.product.prodname_registry %} de tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN`. El `GITHUB_TOKEN` existe en tu repositorio por defecto y tiene permisos de lectura y escritura para paquetes en el repositorio donde se ejecuta el flujo de trabajo. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para realizar operaciones autenticadas en el registro {% data variables.product.prodname_registry %} de tu flujo de trabajo, puedes utilizar el `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 Cuando utilizas la entrada `scope` a la acción `setup-node`, la acción crea un archivo *.npmrc* que incluye el prefijo de alcance. Por defecto, la acción `setup-node` establece el ámbito en el archivo *.npmrc* al usuario u organización que posee el archivo de flujo de trabajo.
 
 Este flujo de trabajo llama a la acción `setup-node` dos veces. Cada vez que se ejecuta la acción `setup-node`, sobrescribe el archivo *.npmrc*. El archivo *.npmrc* hace referencia al token que te permite realizar operaciones autenticadas frente al registro del paquete desde la variable de entorno `NODE_AUTH_TOKEN`. El flujo de trabajo establece la variable de entorno `NODE_AUTH_TOKEN` cada vez que se ejecuta el comando `npm publish`, primero con un token para publicar en el (`NPM_TOKEN`) de npm y luego con un token para publicar en el {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
 
-{% raw %}
+
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -210,28 +211,30 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v1
-      with:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    # Publish to npm
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v1
-      with:
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    # Publish to GitHub Packages
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/es-ES/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/es-ES/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index a4e7952af4..5d8e56aac1 100644
--- a/translations/es-ES/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/es-ES/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
 3. {% data reusables.actions.make-workflow-file %}
 4. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [ac
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. Personaliza los parámetros en tu archivo de flujo de trabajo:
    - En `github.event.project_card.column_id == '12345678'`, reemplaza a `12345678` con la ID de la columna en donde quieras desetiquetar las propuestas y solicitudes de cambio que se movieron a ella.
 
diff --git a/translations/es-ES/content/actions/guides/scheduling-issue-creation.md b/translations/es-ES/content/actions/guides/scheduling-issue-creation.md
index 049fd08d77..eb00c4f9db 100644
--- a/translations/es-ES/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/es-ES/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [
 2. {% data reusables.actions.make-workflow-file %}
 3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Personaliza los parámetros en tu archivo de flujo de trabajo:
    - Cambia el valor de `on.schedule` para que dicte cuándo quieres que se ejecute este flujo de trabajo. En el ejemplo anterior, el flujo de trabajo se ejecutará cada lunes a las 7:20 UTC. Para obtener más información sobre los flujos de trabajo que has programado, consulta la sección "[Ejemplos programados](/actions/reference/events-that-trigger-workflows#scheduled-events)".
    - Cambia el valor de `assignees` a la lista de nombres de usuarios de {% data variables.product.prodname_dotcom %} que quieras asignar a la propuesta.
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index 1cda2939fd..5c6e2760c1 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: About self-hosted runners
-intro: 'You can host your own runners and customize the environment used to run jobs in your {% data variables.product.prodname_actions %} workflows.'
+title: Acerca de los ejecutores autoalojados
+intro: 'Puedes alojar tus propios ejecutores y personalizar el entorno utilizado para ejecutar trabajos en tus flujos de trabajo de {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners
   - /actions/automating-your-workflow-with-github-actions/about-self-hosted-runners
@@ -11,74 +11,80 @@ versions:
 type: overview
 ---
 
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### About self-hosted runners
+### Acerca de los ejecutores autoalojados
 
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.github-actions.self-hosted-runner-description %} Los ejecutores auto-hospedados pueden ser físicos, virtuales, estar en un contenedor, en los servidores del usuario, o en la nube.
 
-You can add self-hosted runners at various levels in the management hierarchy:
-- Repository-level runners are dedicated to a single repository.
-- Organization-level runners can process jobs for multiple repositories in an organization.
-- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
+Puedes agregar ejecutores auto-hospedados en varios niveles dentro de la jerarquía de administración:
+- Los ejecutores a nivel de repositorio están dedicados a un solo repositorio.
+- Los ejecutores a nivel de organización pueden procesar jobs para varios repositorios dentro de una organización.
+- Los ejecutores a nivel de empresa puede asignarse a varias organizaciones en una cuenta empresarial.
 
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+La máquina de tu ejecutor se conecta a{% data variables.product.product_name %} utilizando la aplicación para ejecutores auto-hospedados de {% data variables.product.prodname_actions %}. {% data reusables.github-actions.runner-app-open-source %} Cuando se lanza una nueva versión, la aplicación del ejecutor se actualiza automáticamente cuando se asigna un job al ejecutor, o dentro de una semana de lanzamiento si dicho ejecutor no se ha asignado a ningún job.
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
-For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
+Para obtener más información acerca de la instalación y el uso de los ejecutores auto-alojados, consulta la sección "[Agregar ejecutores auto-alojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" y "[Usar ejecutores auto-alojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)".
 
-### Differences between {% data variables.product.prodname_dotcom %}-hosted and self-hosted runners
+### Diferencias entre ejecutores alojados en {% data variables.product.prodname_dotcom %} y autoalojados
 
-{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted runners are a highly configurable way to run workflows in your own custom environment.
+Los ejecutores alojados en {% data variables.product.prodname_dotcom %} ofrecen una manera más rápida y sencilla de ejecutar tus flujos de trabajo, mientras que estos son una manera altamente configurable de ejecutar flujos de trabajo en tu propio entorno personalizado.
 
-**{% data variables.product.prodname_dotcom %}-hosted runners:**
-- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
-- Are managed and maintained by {% data variables.product.prodname_dotcom %}.
-- Provide a clean instance for every job execution.
-- Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes.
+**Ejecutores alojados en {% data variables.product.prodname_dotcom %}:**
+- Reciben actualizaciones automáticas para el sistema operativo, paquetes y herramientas pre-instalados, y la aplicación del ejecutor auto-hospedado.
+- Son administrados y mantenidos por {% data variables.product.prodname_dotcom %}.
+- Proporcionan una instancia limpia para cada ejecución de trabajo.
+- Usan minutos libres en tu plan de {% data variables.product.prodname_dotcom %}, con tarifas por minuto aplicadas después de superar los minutos libres.
 
-**Self-hosted runners:**
-- Receive automatic updates for the self-hosted runner application only. You are responsible updating the operating system and all other software. 
-- Can use cloud services or local machines that you already pay for.
-- Are customizable to your hardware, operating system, software, and security requirements.
-- Don't need to have a clean instance for every job execution.
-- Are free to use with {% data variables.product.prodname_actions %}, but you are responsible for the cost of maintaining your runner machines.
+**Ejecutores auto-hospedados:**
+- Reciben actualizaciones automáticas únicamente para la aplicación del ejecutor auto-hospedado. Eres responsable de actualizar el sistema operativo y el resto del software.
+- Puedes usar los servicios en la nube o las máquinas locales que ya pagas.
+- Son personalizables para tu hardware, sistema operativo, software y requisitos de seguridad.
+- No es necesario tener una instancia limpia para cada ejecución de trabajo.
+- Son de uso gratuito con las {% data variables.product.prodname_actions %}, pero eres responsable del costo de mantener tus máquinas de ejecutores.
 
-### Requirements for self-hosted runner machines
+### Requisitos para máquinas de ejecutores autoalojados
 
-You can use any machine as a self-hosted runner as long at it meets these requirements:
+Puedes usar cualquier máquina como ejecutor autoalojado, siempre que cumpla con estos requisitos:
 
-* You can install and run the self-hosted runner application on the machine. For more information, see "[Supported operating systems for self-hosted runners](#supported-operating-systems-for-self-hosted-runners)."
-* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)."
-* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
-* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
+* Puedes instalar y ejecutar la aplicación del ejecutor autoalojado en la máquina. Para obtener más información, consulta la sección "[Arquitecturas y sistemas operativos compatibles para ejecutores auto-hospedados](#supported-architectures-and-operating-systems-for-self-hosted-runners)".
+* La máquina puede comunicarse con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)."
+* La máquina tiene suficientes recursos de hardware para el tipo de flujos de trabajo que planeas ejecutar. La propia aplicación del ejecutor autoalojado solo requiere unos recursos mínimos.
+* Si quieres ejecutar flujos de trabajo que usan acciones del contenedor Docker o contenedores de servicio, debes usar una máquina Linux y Docker debe estar instalado.
 
-### Usage limits
+### Límites de uso
 
-There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
+Hay algunos límites para el uso de las {% data variables.product.prodname_actions %} cuando se utilizan ejecutores auto-hospedados. Estos límites están sujetos a cambios.
 
 {% data reusables.github-actions.usage-workflow-run-time %}
-- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
+- **Tiempo de cola de espera para el job** - Cada job para ejecutores auto-hospedados puede ponerse en cola de espera por un máximo de 24 horas. Si un ejecutor auto-hospedado no comienza a ejecutar el job dentro de este límite de tiempo, dicho job se terminará y no se podrá completar.
 {% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
+- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %}
 
-### Supported architectures and operating systems for self-hosted runners
+### Continuidad de los flujos de trabajo para los ejecutores auto-hospedados
 
-The following operating systems are supported for the self-hosted runner application.
+{% data reusables.github-actions.runner-workflow-continuity %}
+
+### Sistemas operativos y arquitecturas compatibles para los ejecutores auto-hospedados
+
+Los siguientes sistemas operativos son compatibles con la aplicación del ejecutor auto-hospedado.
 
 #### Linux
 
 - Red Hat Enterprise Linux 7
 - CentOS 7
 - Oracle Linux 7
-- Fedora 29 or later
-- Debian 9 or later
-- Ubuntu 16.04 or later
-- Linux Mint 18 or later
-- openSUSE 15 or later
-- SUSE Enterprise Linux (SLES) 12 SP2 or later
+- Fedora 29 o posterior
+- Debian 9 o posterior
+- Ubuntu 16.04 o posterior
+- Linux Mint 18 o posterior
+- openSUSE 15 o posterior
+- SUSE Enterprise Linux (SLES) 12 SP2 o posterior
 
 #### Windows
 
@@ -91,59 +97,73 @@ The following operating systems are supported for the self-hosted runner applica
 
 #### macOS
 
-- macOS 10.13 (High Sierra) or later
+- macOS 10.13 (High Sierra) o posterior
 
-#### Architectures
+#### Arquitecturas
 
-The following processor architectures are supported for the self-hosted runner application.
+Las siguientes arquitecturas de procesamiento son compatibles para la aplicación del ejecutor auto-hospedado.
 
 - `x64` - Linux, macOS, Windows.
-- `ARM64` - Linux only.
-- `ARM32` - Linux only.
+- `ARM64` - Solo Linux.
+- `ARM32` - Solo Linux.
 
 {% if enterpriseServerVersions contains currentVersion %}
 
-### Supported actions on self-hosted runners
+### La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }}
 
-Some extra configuration might be required to use actions from {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator.
+La máquina puede comunicarse con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)."
 
 {% endif %}
 
-### Communication between self-hosted runners and {% data variables.product.product_name %}
+### La comunicación entre ejecutores autoalojados y {% data variables.product.product_name %}
 
-The self-hosted runner polls {% data variables.product.product_name %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs.
+El ejecutor auto-hospedado sondea a {% data variables.product.product_name %} para solicitar actualizaciones de aplicaciones y para revisar si hay jobs en cola para su procesamiento. El ejecutor auto-hospedado utiliza un _sondeo largo_ de HTTPS que abre una conexión a {% data variables.product.product_name %} por 50 segundos, y si no recibe respuesta alguna, expira y crea un nuevo sondeo largo. La aplicación debe estar ejecutándose en la máquina para aceptar y ejecutar jobs de {% data variables.product.prodname_actions %}.
+
+{% if currentVersion == "github-ae@latest" %}
+Debes asegurarte de que el ejecutor auto-hospedado tenga un acceso adecuado a la red para comunicarse con la
+URL de {% data variables.product.prodname_ghe_managed %}.
+Por ejemplo, si el nombre de tu instancia es `octoghae`, entonces necesitarás permitir que el ejecutor auto-hospedado acceda a `octoghae.github.com`.
+Si utilizas una lista blanca para las direcciones IP para tu
+
+cuenta empresarial u organizacional de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-.hospedado a dicha lista. Para obtener más información, consulta "[Administrar las direcciones IP permitidas en tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)".
+{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below.
+Debes asegurarte de que la máquina tiene el acceso a la red adecuado para comunicarte con las URL de {% data variables.product.prodname_dotcom %} listadas a continuación.
 
 ```
 github.com
 api.github.com
 *.actions.githubusercontent.com
 github-releases.githubusercontent.com
+github-registry-files.githubusercontent.com
 codeload.github.com
+*.pkg.github.com
+pkg-cache.githubusercontent.com
+pkg-containers.githubusercontent.com
+pkg-containers-az.githubusercontent.com
 ```
 
-If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)".
+Si utilizas un listado de direcciones IP permitidas para tu cuenta organizacional o empresarial de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-hospedado a dicha lista. Para obtener más información, consulta "[Administrar las direcciones IP permitidas para tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" o "[Hacer cumplir los parámetros de seguridad en tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)".
 
 {% else %}
 
-You must ensure that the machine has the appropriate network access to communicate with {% data variables.product.product_location %}.
+Debes asegurarte de que la máquina tenga el acceso de red adecuado para comunicarse con {% data variables.product.product_location %}.
 
 {% endif %}
 
-You can also use self-hosted runners with a proxy server. For more information, see "[Using a proxy server with self-hosted runners](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)."
+También puedes usar ejecutores autoalojados con un servidor proxy. Para obtener más información, consulta "[Usar un servidor proxy con ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)."
 
-### Self-hosted runner security with public repositories
+### Seguridad de ejecutores autoalojdados con repositorios públicos
 
 {% data reusables.github-actions.self-hosted-runner-security %}
 
-This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution.
+Este no es un problema con los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, ya que cada uno de ellos siempre constituye una máquina virtual limpia y aislada, la cual se destruya al final de la ejecución del job.
 
-Untrusted workflows running on your self-hosted runner poses significant security risks for your machine and network environment, especially if your machine persists its environment between jobs. Some of the risks include:
+Los flujos de trabajo que no son de confianza y se ejecutan en tu ejecutor autoalojado plantean riesgos de seguridad considerables para tu máquina y entorno de red, en especial si tu máquina se mantiene en su entorno entre trabajos. Algunos de los riesgos incluyen:
 
-* Malicious programs running on the machine.
-* Escaping the machine's runner sandbox.
-* Exposing access to the machine's network environment.
-* Persisting unwanted or dangerous data on the machine.
+* Programas maliciosos que se ejecutan en la máquina.
+* Escapar del entorno Sandbox del ejecutor de la máquina.
+* Exponer el acceso al entorno de red de la máquina.
+* Mantener datos peligrosos o no deseados en la máquina.
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 abd4287452..2cb002efb1 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
@@ -53,7 +53,7 @@ Cuando creas un grupo, debes elegir una política que defina qué repositorios t
 
    **Advertencia**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    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)."
 
@@ -85,7 +85,7 @@ Cuando creas un grupo, debes elegir la política que defina qué organizaciones
 
    **Advertencia**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    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)."
 
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index dcec8367ff..0c81cb2326 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring and troubleshooting self-hosted runners
-intro: You can monitor your self-hosted runners to view their activity and diagnose common issues.
+title: Monitorear y solucionar problemas para los ejecutores auto-hospedados
+intro: Puedes monitorear tus ejecutores auto-hospedados para ver su actividad y diagnosticar problemas comunes.
 redirect_from:
   - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners
   - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners
@@ -13,54 +13,56 @@ type: tutorial
 defaultPlatform: linux
 ---
 
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### Checking the status of a self-hosted runner
+### Comprobar el estado de un ejecutor autoalojado utilizando {{ site.data.variables.product.prodname_dotcom }}
 
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
 {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %}
 {% data reusables.organizations.settings-sidebar-actions %}
-1. Under "Self-hosted runners," you can view a list of registered runners, including the runner's name, labels, and status.
+1. Debajo de "Ejecutores auto-hospedados", puedes ver una lista de ejecutores registrados, incluyendo su nombre, etiquetas y estado.
 
-    ![Runner list](/assets/images/help/settings/actions-runner-list.png)
+    ![Lista de ejecutores](/assets/images/help/settings/actions-runner-list.png)
 
-    The status can be one of the following:
+    El estado puede ser uno de los siguientes:
 
-    * **Idle**: The runner is connected to {% data variables.product.product_name %} and is ready to execute jobs.
-    * **Active**: The runner is currently executing a job.
-    * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}.
+    * **Idle (Inactivo)**: El ejecutor está conectado a {% data variables.product.product_name %} y está listo para ejecutar puestos de trabajo.
+    * **Active (Activo)**: Actualmente, el ejecutor está ejecutando un puesto de trabajo.
+    * **Offline (Sin conexión)**: El ejecutor no está conectado a {% data variables.product.product_name %}. Esto puede deberse a que la máquina está fuera de línea, la aplicación del ejecutor autoalojado no se está ejecutando en la máquina o la aplicación del ejecutor autoalojado no se puede comunicar con {% data variables.product.product_name %}.
 
 
-### Reviewing the self-hosted runner application log files
+### Revisar los archivos de bitácora de la aplicación del ejecutor auto-hospedado
 
-You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory, and a new one is generated each time the application is started. The filename begins with *Runner_*, and is followed by a UTC timestamp of when the application was started.
+Puedes monitorear el estado de la aplicación del ejecutor auto-hospedado y de sus actividades. Los archivos de bitácora se mantienen en el directorio `_diag`, y se genera uno nuevo cada que se inicia la aplicación. El nombre de archivo comienza con *Runner_*, y le sige una marca de tiempo UTC de cuando se inició la aplicación.
 
-For detailed logs on workflow job executions, see the next section describing the *Worker_* files.
+Para obtener registros detallados sobre las ejecuciones de jobs en el flujo de trabajo, consulta la siguiente sección que describe los archivos *Worker_*.
 
-### Reviewing a job's log file
+### Revisar el archivo de bitácora de un job
 
-The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory, and the filename begins with *Worker_*.
+La aplicación del ejecutor auto-hospedado crea un archivo de bitácora detallado para cada job que procesa. Estos archivos se guardan en el directorio `_diag`, y el nombre de archivo comienza con el prefijo *Worker_*.
 
 {% linux %}
 
-### Using journalctl to check the self-hosted runner application service
+### Utilizar journalctl para revisar el servicio de la aplicación del ejecutor auto-hospedado
 
-For Linux-based self-hosted runners running the application using a service, you can use `journalctl` to monitor their real-time activity. The default systemd-based service uses the following naming convention: `actions.runner.<org>-<repo>.<runnerName>.service`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file. For example:
+Para los ejecutores auto-hospedados basados en Linux que se ejecutan en la aplicación utilizando un servicio, puedes utilizar `journalctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en systemd utiliza la siguiente convención de nomenclatura: `actions.runner.<org>-<repo>.<runnerName>.service`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre de un servicio es revisando el archivo _.service_. Por ejemplo:
 
 ```shell
 $ cat ~/actions-runner/.service
 actions.runner.octo-org-octo-repo.runner01.service
 ```
 
-You can use `journalctl` to monitor the real-time activity of the self-hosted runner:
+Puedes utilizar `journalctl` para monitorear la actividad del ejecutor auto-hospedado en tiempo real:
 
 ```shell
 $ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f
 ```
 
-In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status:
+En este ejemplo de salida, puedes ver como inicia `runner01`, recibe un job llamado `testAction`, y luego muestra el estado resultante:
 
 ```shell
 Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service
@@ -72,23 +74,22 @@ Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: test
 Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded
 ```
 
-To view the systemd configuration, you can locate the service file here: `/etc/systemd/system/actions.runner.<org>-<repo>.<runnerName>.service`.
-If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)."
+Para ver la configuración de systemd, puedes ubicar archivo de servicio aquí: `/etc/systemd/system/actions.runner.<org>-<repo>.<runnerName>.service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)".
 
 {% endlinux %}
 
 {% mac %}
 
-### Using launchd to check the self-hosted runner application service
+### Utilizar launchd para revisar el servicio de la aplicación del ejecutor auto-hospedado
 
-For macOS-based self-hosted runners running the application as a service, you can use `launchctl` to monitor their real-time activity. The default launchd-based service uses the following naming convention: `actions.runner.<org>-<repo>.<runnerName>`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file in the runner directory:
+Para los ejecutores auto-hospedados basados en macOS que se ejecutan en la aplicación como un servicio, puedes utilizar `launchctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en launchd utiliza la siguiente convención de nomenclatura: `actions.runner.<org>-<repo>.<runnerName>`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre del servicio es revisando el archivo _.service_ en el directorio del ejecutor:
 
 ```shell
 % cat ~/actions-runner/.service
 /Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist
 ```
 
-The `svc.sh` script uses `launchctl` to check whether the application is running. For example:
+El script `svc.sh` utiliza `launchctl` para revisar si la aplicación se está ejecutando. Por ejemplo:
 
 ```shell
 $ ./svc.sh status
@@ -98,26 +99,25 @@ Started:
 379 0 actions.runner.example.runner01
 ```
 
-The resulting output includes the process ID and the name of the application’s launchd service.
+La salida generada incluye la ID del proceso y el nombre del servicio launchd de la aplicación.
 
-To view the launchd configuration, you can locate the service file here: `/Users/exampleUsername/Library/LaunchAgents/actions.runner.<repoName>.<runnerName>.service`.
-If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)."
+Para ver la configuración de launchd, puedes ubicar el archivo del servicio aquí: `/Users/exampleUsername/Library/LaunchAgents/actions.runner.<repoName>.<runnerName>.service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)".
 
 {% endmac %}
 
 
 {% windows %}
 
-### Using PowerShell to check the self-hosted runner application service
+### Utilizar PowerShell para revisar el servicio de la aplicación del ejecutor auto-hospedado
 
-For Windows-based self-hosted runners running the application as a service, you can use PowerShell to monitor their real-time activity. The service uses the naming convention `GitHub Actions Runner (<org>-<repo>.<runnerName>)`. You can also find the service's name by checking the _.service_ file in the runner directory:
+Para los ejecutores auto-hospedados basados en Windows que se ejecuten en la aplicación como servicio, puedes utilizar PowerShell para monitorear su actividad en tiempo real. El servicio utiliza la convención de nomenclatura `GitHub Actions Runner (<org>-<repo>.<runnerName>)`. También puedes encontrar el nombre del servicio si revisas el archivo _.service_ en el directorio del ejecutor:
 
 ```shell
 PS C:\actions-runner> Get-Content .service
 actions.runner.octo-org-octo-repo.runner01.service
 ```
 
-You can view the status of the runner in the Windows _Services_ application (`services.msc`). You can also use PowerShell to check whether the service is running:
+Puedes ver el estado del ejecutor en la aplicación _Services_ de Windows (`services.msc`). También puedes utilizar PowerShell para revisar si el servicio se está ejecutando:
 
 ```shell
 PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status
@@ -126,7 +126,7 @@ Name                                                  Status
 actions.runner.octo-org-octo-repo.runner01.service    Running
 ```
 
-You can use PowerShell to check the recent activity of the self-hosted runner. In this example output, you can see the application start, receive a job named `testAction`, and then display the resulting status:
+Puedes utilizar PowerShell para revisar la actividad reciente del ejecutor auto-hospedado. En este ejemplo de salida, puedes ver que la aplicación comienza, recibe un job llamado `testAction`, y después muestra el estado resultante:
 
 ```shell
 PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService
@@ -145,34 +145,34 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer
 
 {% endwindows %}
 
-### Monitoring the automatic update process
+### Monitorear el proceso de actualización automática
 
-We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates.
+Te recomendamos que revises el proceso de actualización automático a menudo, ya que el ejecutor auto-hospedado no podrá procesar jobs si cae debajo de cierto umbral de versiones. La aplicación del ejecutor auto-hospedado se actualiza automáticamente, pero nota que este proceso no incluye ninguna actualización al sistema operativo ni a otro tipo de software; necesitarás administrar estas actualizaciones por separado.
 
-You can view the update activities in the *Runner_* log files. For example:
+Puedes ver las actividades de actualización en los archivos de bitácora *Runner_*. Por ejemplo:
 
 ```shell
 [Feb 12 12:37:07 INFO SelfUpdater] An update is available.
 ```
 
-In addition, you can find more information in the _SelfUpdate_ log files located in the `_diag` directory.
+Adicionalmente, puedes encontrar más información en los archivos de bitácora _SelfUpdate_ ubicados en el directorio `_diag`.
 
 {% linux %}
 
-### Troubleshooting containers in self-hosted runners
+### Solucionar problemas en los contenedores de los ejecutores auto-hospedados
 
-#### Checking that Docker is installed
+#### Revisar que se haya instalado Docker
 
-If your jobs require containers, then the self-hosted runner must be Linux-based and needs to have Docker installed. Check that your self-hosted runner has Docker installed and that the service is running.
+Si tus jobs necesitan contenedores, entonces el ejecutor auto-hospedado debe estar basado en Linux y necesita contar con Docker instalado. Revisa que tu ejecutor auto-hospedado tenga Docker instalado y que el servicio se esté ejecutando.
 
-You can use `systemctl` to check the service status:
+Puedes utilizar `systemctl` para revisar el estado del servicio:
 
 ```shell
 $ sudo systemctl is-active docker.service
 active
 ```
 
-If Docker is not installed, then dependent actions will fail with the following errors:
+Si no se ha instalado Docker, entonces las acciones dependientes fallarán con los siguientes errores:
 
 ```shell
 [2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker'
@@ -180,15 +180,15 @@ If Docker is not installed, then dependent actions will fail with the following
 [2020-02-13 16:56:10Z ERR  StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker'
 ```
 
-#### Checking the Docker permissions
+#### Revisar los permisos de Docker
 
-If your job fails with the following error:
+Si tu job falla con el siguiente error:
 
 ```shell
 dial unix /var/run/docker.sock: connect: permission denied
 ```
 
-Check that the self-hosted runner's service account has permission to use the Docker service. You can identify this account by checking the configuration of the self-hosted runner in systemd. For example:
+Revisa que la cuenta de servicio del ejecutor auto-hospedado tenga permiso de utilizar el servicio de Docker. Puedes identificar esta cuenta revisando la configuración del ejecutor auto-hospedado en systemd. Por ejemplo:
 
 ```shell
 $ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service
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 bd1b70475e..ea55ada525 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
@@ -66,7 +66,7 @@ Para eliminar el ejecutor auto-hospedado de una organización, debes ser el prop
 
 {% if currentVersion == "free-pro-team@latest" %}
 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.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 Para eliminar un ejecutor auto-hospedado a nivel empresarial de
 {% data variables.product.product_location %}, debes ser un administrador de sitio. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado.
 {% endif %}
diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md
index e00f084a77..f48243caab 100644
--- a/translations/es-ES/content/actions/index.md
+++ b/translations/es-ES/content/actions/index.md
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Ejemplos de código</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Ejemplos de búsqueda de código" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Mostrar más {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Lo sentimos, no hay respultados para <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">Parece que no tenemos un ejemplo que se adapte a tu filtro.<br>Intenta con otro filtro o agrega tu ejemplo de código</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Aprende cómo agregar un ejemplo de código {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index d1235e9146..1dfabf8940 100644
--- a/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index 25470e206d..cd2d98ed29 100644
--- a/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ Si necesitas compartir flujos de trabajo y otras características de {% data var
 
 ### Crear una plantilla de flujo de trabajo
 
-Los usuarios con acceso de escritura en el repositorio `.github` de la organización pueden crear plantillas de flujo de trabajo. Los miembros de la organización que tengan permisos para crear flujos de trabajo podrán entonces utilizar estas plantillas. Las plantillas de flujo de trabajo pueden utilizarse para crear flujos de trabajo nuevos en los repositorios públicos de una organización; para utilizar estas plantillas para crear flujos de trabajo en repositorios privados, la organización deberá pertenecer a un plan empresarial o a un plan de GitHub One.
+Los usuarios con acceso de escritura en el repositorio `.github` de la organización pueden crear plantillas de flujo de trabajo. Los miembros de la organización que tengan permisos para crear flujos de trabajo podrán entonces utilizar estas plantillas. Las plantillas de flujo de trabajo pueden utilizarse para crear flujos de trabajo nuevos en los repositorios públicos de una organización; para utilizar estas plantillas para crear flujos de trabajo en repositorios privados, la organización deberá pertenecer a un plan empresarial.
 
 Este procedimiento muestra cómo crear una plantilla de flujo de trabajo y un archivo de metadatos. El archivo de metadatos describe cómo se presenta la plantilla a los usuarios cuando están creando un flujo de trabajo nuevo.
 
 1. En caso de que no exista previamente, crea en tu organización un repositorio público nuevo que se llame `.github`.
-1. Crea un directorio que se llame `workflow-templates`.
-1. Crea tu nuevo archivo de flujo de trabajo dentro del directorio `workflow-templates`.
+2. Crea un directorio que se llame `workflow-templates`.
+3. Crea tu nuevo archivo de flujo de trabajo dentro del directorio `workflow-templates`.
 
    Si necesitas referirte a la rama predeterminada de un repositorio, puedes utilizar el marcador de posición `$default-branch`. Cuando se crea un flujo de trabajo utilizando tu plantilla, el marcador de posición se reemplazará automáticamente con el nombre de la rama predeterminada del repositorio.
 
@@ -52,7 +52,7 @@ Este procedimiento muestra cómo crear una plantilla de flujo de trabajo y un ar
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. Crea un archivo de metadatos dentro del directorio `workflow-templates`. El archivo de metadatos debe tener el mismo nombre que el archivo de flujo de trabajo, pero en vez de tener la extensión `.yml`, este deberá encontrarse adjunto en `.properties.json`. Por ejemplo, este archivo que se llama `octo-organization-ci.properties.json` contiene los metadatos para un archivo de flujo de trabajo de nombre `octo-organization-ci.yml`:
+4. Crea un archivo de metadatos dentro del directorio `workflow-templates`. El archivo de metadatos debe tener el mismo nombre que el archivo de flujo de trabajo, pero en vez de tener la extensión `.yml`, este deberá encontrarse adjunto en `.properties.json`. Por ejemplo, este archivo que se llama `octo-organization-ci.properties.json` contiene los metadatos para un archivo de flujo de trabajo de nombre `octo-organization-ci.yml`:
    ```yaml
    {
        "name": "Octo Organization Workflow",
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..c9b44b255c
--- /dev/null
+++ b/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: Aprobar ejecuciones de flujo de trabajo desde bifurcaciones públicas
+intro: 'Cuando un contribuyente primerizo emite una solicitud de cambios a un repositorio público, un mantenedor con acceso de escritura debe aprobar cualquier ejecución de flujo de trabajo.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+Las bifurcaciones de los repositorios públicos pueden emitir solicitudes de cambio que propongan cambios a los flujos de trabajo de las {% data variables.product.prodname_actions %} de un repositorio. Aunque los flujos de trabajo de las bifurcaciones no tienen acceso a datos sensibles tales como los secretos, pueden ser molestos para los mantenedores si se modifican para fines de abuso. Para ayudar a prevenir esto, los flujos de trabajo de las solicitudes de cambio no se ejecutan automáticamente si se reciben de contribuyentes primerizos y debe aprobarse primero.
+
+Los mantenedores con acceso de escritura al repositorio pueden utilizar el siguiente procedimiento para revisar y ejecutar flujos de trabajo en solicitudes de cambio de contribuyentes primerizos. Después de que un contribuyente fusione por lo menos una solicitud de cambios en el repositorio de un proyecto, cualquier solicitud de cambios subsecuente de la bifurcación de dicho contribuyente ejecutará flujos de trabajo automáticamente.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspecciona los cambios propuestos en la solicitud de cambios y asegúrate de que estés de acuerdo para ejecutar tus flujos de trabajo en la rama de la solicitud de cambios. Debes estar especialmente alerta para notar cualquier cambio propuesto en el directorio `.github/workflows/` que afecte a los archivos de flujo de trabajo.
+1. Si no estás de acuerdo en ejecutar los flujos de trabajo en la rama de la solicitud de cambios, regresa a la {% octicon "comment-discussion" aria-label="The discussion icon" %} pestaña de **Conversación** y, debajo de "Flujo(s) de trabajo esperando aprobación", haz clic en **Aprobar y ejecutar**.
+
+   ![Aprueba y ejecuta flujos de trabajo](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index 7f5923238d..90c791fbe8 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Inhabilitar y habilitar un flujo de trabajo
-intro: 'Puedes inhabilitar y volver a habilitar un flujo de trabajo utilizando {% data variables.product.prodname_dotcom %} o la API de REST.'
+intro: 'Puedes inhabilitar y volver a habilitar un flujo de trabajo utilizando la IU de {% data variables.product.prodname_dotcom %}, la API de REST, o el {% data variables.product.prodname_cli %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-Inhabilitar un flujo de trabajo te permite impedir que se active sin tener que borrar el archivo del repositorio. Puedes habilitar el flujo de trabajo de nuevo fácilmente en {% data variables.product.prodname_dotcom %}. También puedes inhabilitar y habilitar un flujo de trabajo utilizando la API de REST. Para obtener más información, consulta la sección "[API de REST de Acciones](/rest/reference/actions#workflows)".
+Inhabilitar un flujo de trabajo te permite impedir que se active sin tener que borrar el archivo del repositorio. Puedes habilitar el flujo de trabajo de nuevo fácilmente en {% data variables.product.prodname_dotcom %}.
 
 Inhabilitar un flujo de trabajo temporalmente puede ser útil en varios escenarios. Estos son algunos cuantos ejemplos en donde inhabilitar un flujo de trabajo podría ser útil:
 
@@ -27,7 +27,9 @@ Inhabilitar un flujo de trabajo temporalmente puede ser útil en varios escenari
 
 {% endwarning %}
 
-### Inhabilitar un flujo de trabajo
+### Inhabilitar y habilitar flujos de trabajo con la IU de {% data variables.product.prodname_dotcom %}
+
+#### Inhabilitar un flujo de trabajo
 
 Puedes inhabilitar un flujo de trabajo manualmente para que no ejecute ninguna ejecución del mismo. Un flujo de trabajo inhabilitado no se borrará y puede volver a habilitarse.
 
@@ -37,7 +39,7 @@ Puedes inhabilitar un flujo de trabajo manualmente para que no ejecute ninguna e
 1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![menú de kebab de las acciones](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. Da clic en **Inhabilitar flujo de trabajo**. ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)El flujo de trabajo inhabilitado se marca con {% octicon "stop" aria-label="The stop icon" %} para indicar su estado. ![lista de acciones del flujo de trabajo inhabilitado](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### Habilitar un flujo de trabajo
+#### Habilitar un flujo de trabajo
 
 Puedes volver a habilitar un flujo de trabajo que se había inhabilitado previamente.
 
@@ -45,3 +47,23 @@ Puedes volver a habilitar un flujo de trabajo que se había inhabilitado previam
 {% data reusables.repositories.actions-tab %}
 1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres habiitar. ![acciones para seleccional el flujo de trabajo inhabilitado](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. Da clic en **Habilitar flujo de trabajo**. ![acciones para habilitar flujo de trabajo](/assets/images/help/repository/actions-enable-workflow.png)
+
+### Inhabilitar y habilitar flujos de trabajo con {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para inhabilitar un flujo de trabajo, utiliza el subcomando `workflow disable`. Reemplaza a `workflow` con ya sea el nombre, ID o nombre de archivo del flujo de trabajo que quieres inhabilitar. Por ejemplo `"Link Checker"`, `1234567`, o `"link-check-test.yml"`. Si no especificas un flujo de trabajo, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas un flujo de trabajo.
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+Para habilitar un flujo de trabajo, utiliza el subcomando `workflow enable`. Reemplaza a `workflow` con ya sea el nombre, ID o nombre de archivo del flujo de trabajo que quieras habilitar. Por ejemplo `"Link Checker"`, `1234567`, o `"link-check-test.yml"`. Si no especificas un flujo de trabajo, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas un flujo de trabajo.
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### Inhabilitar y habilitar flujos de trabajo mediante la API de REST
+
+También puedes inhabilitar y habilitar un flujo de trabajo utilizando la API de REST. Para obtener más información, consulta la sección "[API de REST de Acciones](/rest/reference/actions#workflows)".
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 39cf8e8684..84819093da 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} Predeterminadamente, {% data variables.product.product_name %} almacena bitácoras de compilación y artefactos hasta por 90 días y puedes configurar este periodo de retención dependiendo del tipo de repositorio que tengas. Para obtener más información, consulta la sección "[Configurar el periodo de retención para los artefactos y las bitácoras de las GitHub Actions en tu repositorio](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} Las {% data variables.product.product_name %} almacenan las bitácoras y los artefactos por 90 días.{% endif %}
 
+### Descarga artefactos con la IU de {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### Descarga los artefactos con {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+El {% data variables.product.prodname_cli %} descargará cada artefacto en directorios separados con base en el nombre de dicho artefacto. Si se especifica solo un artefacto individual, este se extraerá en el directorio actual.
+
+Para descargar todos los artefactos que genera una ejecución de flujo de trabajo, utiliza el subcomando `run download`. Reemplaza a `run-id` con la ID de la ejecución de la cual quieres descargar artefactos. Si no especificas una `run-id`, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas una ejecución reciente.
+
+```shell
+gh run download <em>run-id</em>
+```
+
+Para descargar un artefacto específico desde una ejecución, utiliza el subcomando `run download`. Reemplaza a `run-id` con la ID de la ejecución de la cual quieres descargar artefactos. Reemplaza a `artifact-name` con el nombre del artefacto que quieres descargar.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+Puedes especificar más de un artefacto.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+Para descargar los artefactos específicos a lo largo de todas las ejecuciones en un repositorio, utiliza el subcomando `run download`.
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/index.md b/translations/es-ES/content/actions/managing-workflow-runs/index.md
index e6933c05e3..f8bcf62912 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/index.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index c8b40e65a3..586f65998b 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Manually running a workflow
-intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the REST API or from the Actions tab on {% data variables.product.prodname_dotcom %}.'
+title: Ejecutar un flujo de trabajo manualmente
+intro: 'Cuando se configura un flujo de trabajo para que se ejecute en el evento `workflow_dispatch`, puedes ejecutarlo utilizando la pestaña de Acciones en {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, o en la API de REST.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -10,28 +10,60 @@ versions:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### Configuring a workflow to run manually
+### Configurar un flujo de trabajo para que se ejecute manualmente
 
-To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
+Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para ejecutarse en el evento `workflow_dispatch`. Para obtener más información sobre cómo configurar el evento `workflow_dispatch`, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
-### Running a workflow on {% data variables.product.prodname_dotcom %} 
+### Ejecutar un flujo de trabajo en {% data variables.product.prodname_dotcom %}
 
-To trigger the `workflow_dispatch` event on {% data variables.product.prodname_dotcom %}, your workflow must be in the default branch. Follow these steps to manually trigger a workflow run.
+Para activar el evento `workflow_dispatch` en {% data variables.product.prodname_dotcom %}, tu flujo de trabajo deberá estar en la rama predeterminada. Sigue estos pasos para activar una ejecución de flujo de trabajo manualmente.
 
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to run.
-![actions select workflow](/assets/images/actions-select-workflow.png)
-1. Above the list of workflow runs, select **Run workflow**.
-![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
-1. Select the branch where the workflow will run and type the input parameters used by the workflow. Click **Run workflow**.
-![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
+1. En la barra lateral izquierda, da clic ene l flujo de trabajo que quieras ejecutar. ![flujo de trabajo de la selección en las acciones](/assets/images/actions-select-workflow.png)
+1. Sobre la lista de ejecuciones de flujo de trabajo, selecciona **Ejecutar flujo de trabajo**. ![envío del flujo de trabajo de las acciónes](/assets/images/actions-workflow-dispatch.png)
+1. Selecciona la rama en donde el flujo de trabajo se ejecutará y teclea los parámetros de entrada que éste utiliza. Da clic en **Ejecutar flujo de trabajo**. ![flujo de trabajo de la ejecución manual de las acciones](/assets/images/actions-manually-run-workflow.png)
 
-### Running a workflow using the REST API
+### Ejecutar un flujo de trabajo utilizando {% data variables.product.prodname_cli %}
 
-When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used. 
+{% data reusables.actions.actions-cli %}
 
-For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."
+Para ejecutar un flujo de trabajo, utiliza el subcomando `workflow run`. Reemplaza el parámetro `workflow` ya sea con el nombre, ID, o nombre de archivo del flujo de trabajo que quieres ejecutar. Por ejemplo `"Link Checker"`, `1234567`, o `"link-check-test.yml"`. Si no especificas un flujo de trabajo, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas un flujo de trabajo.
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+Si tu flujo de trabajo acepta entradas, {% data variables.product.prodname_cli %} te pedirá que las ingreses. Como alternativa, puedes utilizar `-f` o `-F` para agregar una entrada en formato `key=value`. Utiliza `-F` para leer desde un archivo.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+También puedes pasar las entradas como JSON utilizando una entrada estándar.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+Para ejecutar un flujo de trabajo en una rama del repositorio diferente a la predeterminada, utiliza el marcador `--ref`.
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+Para ver el progreso de la ejecución del flujo de trabajo, utiliza el subcomando `run watch` y selecciona la ejecución de la lista interactiva.
+
+```shell
+gh run watch
+```
+
+### Ejecutar un flujo de trabajo utilizando la API de REST
+
+Para obtener más información acerca de cómo utilizar la API de REST, consulta la sección [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Si omites las entradas, se utilizarán los valores predeterminados que se hayan definido en el flujo de trabajo.
+
+Puedes activar el evento de `workflow_dispatch` desde la pestaña de Acciones en {{ site.data.variables.product.prodname_dotcom }} o utilizar la API de REST.
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md
index fa6199e175..52973ead17 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Vuelve a ejecutar un flujo de trabajo utilizando la IU de {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. En la esquina superior derecha del flujo de trabajo, utiliza el menú desplegable de **Volver a ejecutar los jobs** y selecciona **Volver a ejecutar todos los jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### Volver a ejecutar un flujo de trabajo utilizando {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para volver a ejecutar una ejecución de flujo de trabajo fallida, utiliza el subcomando `run rerun`. Reemplaza a `run-id` con la ID de la ejecución fallida que quieres volver a ejecutar.  Si no especificas una `run-id`, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas una ejecución fallida reciente.
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+Para ver el progreso de la ejecución del flujo de trabajo, utiliza el subcomando `run watch` y selecciona la ejecución de la lista interactiva.
+
+```shell
+gh run watch
+```
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 1dd2f3f641..cf874f8211 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. Debajo de **Artefactos**, da clic en
-el {% octicon "trashcan" aria-label="The trashcan icon" %} junto al artefacto que quieras eliminar.
+el {% octicon "trash" aria-label="The trash icon" %} junto al artefacto que quieras eliminar.
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![Menú desplegable Delete artifact (Eliminar artefacto)](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index 058923efc0..61143b69f1 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ Después de borrar las bitácoras, el botón de **Borrar todas las bitácoras**
 1. En la esquina superior derecha, da clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. Para borrar los archivos de bitácora, da clic en el botón **Borrar todas las bitácoras** y revisa el aviso de confirmación. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) Después de que se hayan borrado las bitácoras, el botón de **Borrar todas las bitácoras** se elimina para indicar que no queda ningún archivo de bitácora en la ejecución del flujo de trabajo.
 {% endif %}
+
+### Visualizar las bitácoras con {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para ver la bitácora de un job específico, utiliza el subcomando `run view`. Reemplaza a `run-id` con la ID de la ejecución de la cual quieres ver las bitácoras. {% data variables.product.prodname_cli %} devuelve un menú interactivo para que elijas un job de la ejecución. Si no especificas una `run-id`, {% data variables.product.prodname_cli %} devuelve un menú interactivo para que elijas una ejecución reciente y luego devuelve otro menú interactivo para que elijas un job de la ejecución.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+También puedes utilizar el marcador `--job` para especificar una ID de job. Reemplaza a `job-id` con la ID del job del cual quieres ver las bitácoras.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Puedes utilizar `grep` para buscar la bitácora. Por ejemplo, este comando devolverá todas las entradas de la bitácora que contenga la palabra `error`.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+Para filtrar las bitácoras para encontrar cualquier tipo de paso fallido, utiliza `--log-failed` en vez de `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index 189ec57e60..a04e25707a 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Visualizar el historial de las ejecuciones de flujo de trabajo en {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### Visualizar el historial de las ejecuciones de flujo de trabajo con {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+#### Visualizar las ejecuciones de flujo de trabajo recientes
+
+Para listar las ejecuciones de flujo de trabajo recientes, utiliza el subcomando `run list`.
+
+```shell
+gh run list
+```
+
+Para especificar la cantidad máxima de ejecuciones a devolver, puedes utilizar el marcador `-L` o `--limit`. Por defecto es `10`.
+
+```shell
+gh run list --limit 5
+```
+
+Para que se devuelvan únicamente las ejecuciones del flujo de trabajo especificado, puedes utilizar el marcador `-w` o `--workflow`.  Reemplaza a `workflow` ya sea con el nombre, ID o nombre de archivo del flujo de trabajo. Por ejemplo `"Link Checker"`, `1234567`, o `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### Visualizar los detalles de una ejecución de flujo de trabajo específica
+
+Para mostrar los detalles de una ejecución de flujo de trabajo específica, utiliza el subcomando `run view`. Reemplaza `run-id` con la ID de la ejecución que quieres ver. Si no especificas una `run-id`, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas una ejecución reciente.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+Par aincluir los pasos del job en la salida, utiliza el marcador `-v` o `--verbose`.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+Para ver los detalles de un job específico en la ejecución, utiliza el marcador `-j` o `--job`.  Reemplaza a `job-id` con la ID del job que quieres ver.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+Para ver la bitácora completa de un job, utiliza el marcador `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Utiliza el marcador `--exit-status` para salir con un estado diferente a cero si la ejecución falló. Por ejemplo:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md b/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md
index d99d69416b..ad88dae37a 100644
--- a/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/es-ES/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ El token también está disponible en el contexto `github.token`. Para obtener m
 
 ### Usar el `GITHUB_TOKEN` en un flujo de trabajo
 
-Para usar el secreto del `GITHUB_TOKEN`, debes hacer referencia a él en tu archivo de flujo de trabajo. Usar un token puede incluir pasar el token como entrada a una acción que lo requiere o hacer llamadas autenticadas de la API {% data variables.product.prodname_dotcom %}.
+Puedes utilizar el `GITHUB_TOKEN` si utilizas la sintaxis estándar para referenciar secretos: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Los ejemplos de uso del `GITHUB_TOKEN` incluyen pasar el token como entrada a una acción o utilizarlo para hacer una solicitud autenticada a la API de {% data variables.product.prodname_dotcom %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**Importante:** Las acciones pueden acceder al `GITHUB_TOKEN` mediante el contexto `github.token` aún si el flujo de trabajo no pasa el `GITHUB_TOKEN` específicamente a la acción. Como buena práctica de seguridad. siempre deberías asegurarte de que las acciones solo tengan el acceso mínimo que necesitan para limitar los permisos que se le otorgan al `GITHUB_TOKEN`. Para obtener más información, consulta "[Permisos para el `GITHUB_TOKEN`](#permissions-for-the-github_token)."
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### Ejemplo de pase de `GITHUB_TOKEN` como una entrada
+#### Ejemplo 1: pasar el `GITHUB_TOKEN` como entrada
 
 Este flujo de trabajo de ejemplo usa la [acción de etiquetadora](https://github.com/actions/labeler), que necesita el `GITHUB_TOKEN` como el valor para el parámetro de entrada `repo-token`:
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### Ejemplo de llamada a la API REST
+#### Ejemplo 2: llamar a la API de REST
 
 Puedes usar el `GITHUB_TOKEN` para realizar llamadas API autenticadas. Este flujo de trabajo de ejemplo crea una propuesta mediante la API REST de {% data variables.product.prodname_dotcom %}:
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,15 +88,31 @@ Puedes usar el `GITHUB_TOKEN` para realizar llamadas API autenticadas. Este fluj
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_."
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### Permisos para el `GITHUB_TOKEN`
 
-Para obtener información sobre los puntos finales de la API a los que {% data variables.product.prodname_github_apps %} puede acceder con cada permiso, consulta la sección "[ Permisos de {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)".
+Para obtener mpas información sobre las terminales de la API a los que pueden acceder las {% data variables.product.prodname_github_apps %} con cada permiso, consulta la sección "[ Permisos de las {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)".
 
-| Permiso                   | Tipo de acceso    | Acceso por repositorios bifurcados |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+La siguiente tabla muestra los permisos que se otorgan al `GITHUB_TOKEN` predeterminadamente. Las personas con permisos administrativos en una empresa, organización o repositorio pueden configurar los permisos predeterminados para que sean permisivos o restringidos. Para obtener más información sobre cómo configurar los permisos predeterminados del `GITHUB_TOKEN` para tu empresa, organización o repositorio, consulta las secciones "[Requerir políticas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)", "[Inhabilitar o limitar a las {% data variables.product.prodname_actions %} en tu organización](/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)" o "[Inhabilitar o limitar a las {% data variables.product.prodname_actions %} en tu repositorio](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)".
+
+| Ámbito                    | Acceso predeterminado<br>(permisivo) | Acceso predeterminado<br>(restringido) | Acceso máximo<br>de los repos bifurcados |
+| ------------------------- | ------------------------------------------ | -------------------------------------------- | ---------------------------------------------- |
+| acciones                  | lectura/escritura                          | ninguno                                      | lectura                                        |
+| verificaciones            | lectura/escritura                          | ninguno                                      | lectura                                        |
+| contenidos                | lectura/escritura                          | lectura                                      | lectura                                        |
+| implementaciones          | lectura/escritura                          | ninguno                                      | lectura                                        |
+| propuestas                | lectura/escritura                          | ninguno                                      | lectura                                        |
+| metadatos                 | lectura                                    | lectura                                      | lectura                                        |
+| paquetes                  | lectura/escritura                          | ninguno                                      | lectura                                        |
+| solicitudes de extracción | lectura/escritura                          | ninguno                                      | lectura                                        |
+| proyectos de repositorio  | lectura/escritura                          | ninguno                                      | lectura                                        |
+| eventos de seguridad      | lectura/escritura                          | ninguno                                      | lectura                                        |
+| estados                   | lectura/escritura                          | ninguno                                      | lectura                                        |
+{% else %}
+| Ámbito                    | Tipo de acceso    | Acceso por repositorios bifurcados |
 | ------------------------- | ----------------- | ---------------------------------- |
 | acciones                  | lectura/escritura | lectura                            |
 | verificaciones            | lectura/escritura | lectura                            |
@@ -94,9 +124,32 @@ Para obtener información sobre los puntos finales de la API a los que {% data v
 | solicitudes de extracción | lectura/escritura | lectura                            |
 | proyectos de repositorio  | lectura/escritura | lectura                            |
 | estados                   | lectura/escritura | lectura                            |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### Modificar los permisos del `GITHUB_TOKEN`
+
+Puedes modificar los permisos del `GITHUB_TOKEN` en archivos de flujo de trabajo individuales. Si los permisos predeterminados del `GITHUB_TOKEN` son restrictivos, podría que necesites elevar los permisos para permitir que las acciones y comandos se ejecuten con éxito. Si los permisos predeterminados son permisivos, puedes editar el archivo de flujo de trabajo para eliminar algunos de ellos del `GITHUB_TOKEN`. Como buena práctica de seguridad, debes otorgar al `GITHUB_TOKEN` el menor acceso requerido.
+
+Puedes ver los permisos que tuvo el `GITHUB_TOKEN` para un job específico en la sección "Configurar job" de la bitácora de la ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Utilizar bitácoras de ejecución de flujos de trabajo](/actions/managing-workflow-runs/using-workflow-run-logs)".
+
+Puedes utilizar la clave `permissions` en tu archivo de flujo de trabajo para modificar los permisos del `GITHUB_TOKEN` para un flujo de trabajo entero o para jobs individuales. Esto te permite configurar los permisos mínimos requeridos para un flujo de trabajo o job. Cuando se utiliza la clave `permissions`, todos los permisos no especificados se configuran como "sin acceso", con la excepción del alcance `metadata`, el cual siempre obtiene acceso de lectura.
+
+{% data reusables.github-actions.forked-write-permission %}
+
+Los dos ejemplos de flujo de trabajo que se mostraron anteriormente en este artículo muestran como se utiliza la clave `permissions` a nivel de flujo de trabajo y de job. En el [Ejemplo 1](#example-1-passing-the-github_token-as-an-input) se especifican los dos permisos para todo el flujo de trabajo. En el [Ejemplo 2](#example-2-calling-the-rest-api) se otorga acceso de escritura para un alcance para un solo job.
+
+Para conocer todos los detalles de la clave `permissions`, consulta la sección "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)".
+
+##### Cómo se calculan los permisos para un job de un flujo de trabajo
+
+Los permisos para el `GITHUB_TOKEN` se configuran inicialmente con los ajustes predeterminados para la empresa, organización o repositorio. Si lo predeterminado se configura para los permisos restringidos en cualquiera de estos niveles, esto aplicará a los repositorios relevantes. Por ejemplo, si eliges las restricciones predeterminadas a nivel organizacional, entonces todos los repositorios de la organización utilizarán estos permisos restringidos como los predeterminados. Entonces, los permisos se ajustarán con base en cualquier configuración dentro del archivo de flujo de trabajo, primero a nivel del flujo de trabajo y luego al nivel de los jobs. Por último, si una solilcitud de cambios activó el flujo de trabajo desde un repositorio bifurcado y no se selecciona el ajuste de **Enviar tokens de escritura a los flujos de trabajo desde las solicitudes de cambios**, los permisos se ajustarán para cambiar cualquier permiso de escritura a solo lectura.
+
+#### Otorgar permisos adicionales
+{% endif %}
+
 Si necesitas un token que requiere permisos que no están disponibles en el `GITHUB_TOKEN`, puedes crear un token de acceso personal y establecerlo como un secreto en tu repositorio:
 
 1. Usa o crea un token con los permisos adecuados para ese repositorio. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
diff --git a/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index ad99f74656..0a578212b0 100644
--- a/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ Los contextos son una manera de acceder a información acerca de las ejecuciones
 | Nombre del contexto | Tipo     | Descripción                                                                                                                                                                                                                                                        |
 | ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `github`            | `objeto` | Información sobre la ejecución del flujo de trabajo. Para obtener más información, consulta [github</code> context](#github-context).                                                                                                                              |
-| `env`               | `objeto` | Contiene variables de entorno establecidas en un flujo de trabajo, trabajo o paso. Para obtener más información, consulta contexto de [`env`](#env-context).                                                                                                       |
+| `env`               | `objeto` | Contiene variables de entorno establecidas en un flujo de trabajo, trabajo o paso. Para obtener más información, consulta el [contexto `env`](#env-context).                                                                                                       |
 | `job`               | `objeto` | Información sobre el trabajo actualmente en ejecución. Para obtener más información, consulta contexto de [`job`](#job-context).                                                                                                                                   |
 | `pasos`             | `objeto` | Información sobre los pasos que se han ejecutado en este trabajo. Para obtener más información, consulta contexto de [`steps`](#steps-context).                                                                                                                    |
 | `runner`            | `objeto` | Incluye información sobre el ejecutor que está realizando el trabajo actual. Para más información, consulta [Contexto del `ejecutador (runner)`](#runner-context).                                                                                                 |
@@ -93,11 +93,11 @@ El contexto de `github` contiene información sobre la ejecución del flujo de t
 | `github.action`           | `secuencia` | El nombre de la acción que se está ejecutando actualmente. {% data variables.product.prodname_dotcom %} elimina caracteres especiales o usa el nombre `run` cuando el paso actual ejecuta un script.  Si usas la misma acción más de una vez en el mismo trabajo, el nombre incluirá un sufijo con el número de secuencia.  Por ejemplo, el primer script que ejecutes tendrá el nombre `run1`, y el segundo script será nombrado `run2`. Del mismo modo, la segunda invocación de `actions/checkout` será `actionscheckout2`. |
 | `github.action_path`      | `secuencia` | La ruta en donde se ubica tu acción. Puedes utilizar esta ruta para acceder fácilmente a los archivos ubicados en el mismo repositorio que tu acción. Este atributo solo es compatible con las acciones de los pasos de ejecución compuestos.                                                                                                                                                                                                                                                                                  |
 | `github.actor`            | `secuencia` | El inicio de sesión del usuario que inició la ejecución del flujo de trabajo.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| `github.base_ref`         | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es una `pull_request`.                                                                                                                                                                                                                                                                                                       |
+| `github.base_ref`         | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`.                                                                                                                                                                                                                                                                            |
 | `github.event`            | `objeto`    | La carga de webhook del evento completo. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/articles/events-that-trigger-workflows/)". "Puedes acceder a propiedades individuales del evento que utiliza este contexto.                                                                                                                                                                                                                                                                      |
 | `github.event_name`       | `secuencia` | El nombre del evento que activó la ejecución del flujo de trabajo.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
 | `github.event_path`       | `secuencia` | La ruta a la carga del webhook del evento completo en el ejecutor.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `github.head_ref`         | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es una `pull_request`.                                                                                                                                                                                                                                                                                                       |
+| `github.head_ref`         | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`.                                                                                                                                                                                                                                                                            |
 | `github.job`              | `secuencia` | El [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual.                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | `github.ref`              | `secuencia` | La rama o ref de etiqueta que activó la ejecución del flujo de trabajo. Para las ramas, está en el formato `refs/heads/<branch_name>`, y para las etiquetas está en `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                        |
 | `github.repository`       | `secuencia` | El nombre del repositorio y del propietario. Por ejemplo, `Codertocat/Hello-World`.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
@@ -323,7 +323,7 @@ Devuelve `verdadero` si `searchString` contiene `searchValue`. Esta función no
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-Reemplaza valores en la `cadena`, con la variable `replaceValueN`. Las variables en la `cadena` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `cadena`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar llaves usando llaves dobles.
+Reemplaza valores en la `cadena`, con la variable `replaceValueN`. Las variables en la `cadena` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `cadena`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar las llaves utilizando llaves dobles.
 
 ##### Ejemplo
 
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
@@ -445,7 +445,7 @@ Arroja `true` cuando no falló ni se canceló ninguno de los pasos anteriores.
 ##### Ejemplo
 
 ```yaml
-Pasos:
+steps:
   ...
   - name: The job has succeeded
     if: {% raw %}${{ success() }}{% endraw %}
@@ -478,7 +478,7 @@ Arroja `true` cuando falla cualquiera de los pasos anteriores de un trabajo.
 ##### Ejemplo
 
 ```yaml
-Pasos:
+steps:
   ...
   - name: The job has failed
     if: {% raw %}${{ failure() }}{% endraw %}
diff --git a/translations/es-ES/content/actions/reference/encrypted-secrets.md b/translations/es-ES/content/actions/reference/encrypted-secrets.md
index 2cacfc87c7..6d0982a2b3 100644
--- a/translations/es-ES/content/actions/reference/encrypted-secrets.md
+++ b/translations/es-ES/content/actions/reference/encrypted-secrets.md
@@ -29,21 +29,15 @@ Para que los secretos se almacenen a nivel de ambiente, puedes habilitar los rev
 
 #### Nombrar tus secretos
 
-Las siguientes reglas aplican a los nombres secretos:
+{% data reusables.codespaces.secrets-naming %}. Por ejemplo, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}un secreto que se creó a nivel de ambiente debe tener un nombre único en este, {% endif %}un secreto que se cree a nivel de repositorio, debe tener un nombre único en dicho repositorio, y un secreto que se cree a nivel de organización debe tener un nombre único en este nivel.
 
-* Los nombres secretos solo contienen caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) o guiones bajos (`_`). No se permiten espacios.
-* Los nombres secretos no deben comenzar con el prefijo `GITHUB_`.
-* Los nombres secretos no deben comenzar con un número.
-* Los nombres de secreto no distinguen entre mayúsculas y minúsculas.
-* Los nombres secretos deben ser únicos en el nivel en el que se hayan creado. Por ejemplo, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}un secreto que se creó a nivel de ambiente debe tener un nombre único en este, {% endif %}un secreto que se cree a nivel de repositorio, debe tener un nombre único en dicho repositorio, y un secreto que se cree a nivel de organización debe tener un nombre único en este nivel.
-
-  Si un secreto con el mismo nombre existe en varios niveles, aquél en el nivel más bajo tomará presedencia. Por ejemplo, si un secreto a nivel de organización tiene el mismo nombre que un secreto a nivel de repositorio, entonces el secreto a nivel de repositorio tomará precedencia.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} De forma similar, si una organización, repositorio y ambiente tienen un secreto con el mismo nombre, el secreto a nivel de ambiente tomará precedencia.{% endif %}
+  {% data reusables.codespaces.secret-precedence %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
 
 Para ayudarte a garantizar que {% data variables.product.prodname_dotcom %} redacta tus secretos en bitácoras, evita utilizar datos estructurados como los valores de los secretos. Por ejemplo, evita crear secretos que contengan JSON o blobs de Git codificados.
 
 #### Acceder a tus secretos
 
-Para hacer que un secreto esté disponible para una acción, debes configurar el secreto como una variable de entrada o de entorno en tu archivo de flujo de trabajo. Revisa el archivo README de la acción para saber qué variables de entrada y de entorno espera la acción. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)".
+Para hacer que un secreto esté disponible para una acción, debes configurar el secreto como una variable de entrada o de entorno en tu archivo de flujo de trabajo. Revisa el archivo README de la acción para saber qué variables de entrada y de entorno espera la acción. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para{% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)".
 
 Puedes usar y leer secretos cifrados en un archivo de flujo de trabajo si tienes acceso para editar el archivo. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
 
@@ -83,7 +77,8 @@ Si tu repositorio {% if currentVersion == "free-pro-team@latest" or currentVersi
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" }
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+
 ### Crear secretos cifrados para un ambiente
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
@@ -125,7 +120,11 @@ Puedes revisar qué políticas de acceso se están aplicando a un secreto en tu
 
 ### Usar secretos cifrados en un flujo de trabajo
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
+
+**Nota:**{% data reusables.actions.forked-secrets %}
+
+{% endnote %}
 
 Para proporcionar una acción con un secreto como variable de entrada o de entorno, puedes usar el contexto de `secrets` para acceder a los secretos que has creado en tu repositorio. Para obtener más información, consulta "[Sintaxis de contexto y de expresiones para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions) y [Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
 
diff --git a/translations/es-ES/content/actions/reference/environment-variables.md b/translations/es-ES/content/actions/reference/environment-variables.md
index 71ea971989..0399a15725 100644
--- a/translations/es-ES/content/actions/reference/environment-variables.md
+++ b/translations/es-ES/content/actions/reference/environment-variables.md
@@ -56,8 +56,9 @@ Te recomendamos encarecidamente que las acciones usen variables de entorno para
 | `GITHUB_WORKFLOW`    | El nombre del flujo de trabajo.                                                                                                                                                                                                                                                                                                                                                                      |
 | `GITHUB_RUN_ID`      | {% data reusables.github-actions.run_id_description %}
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
-| `GITHUB_JOB`         | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                                                                                                                                                   |
+| `GITHUB_JOB`         | La [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual.                                                                                                                                                                                                                                                                                                        |
 | `GITHUB_ACTION`      | El único identificador (`id`) de la acción.                                                                                                                                                                                                                                                                                                                                                          |
+| `GITHUB_ACTION_PATH` | La ruta en donde se ubica tu acción. You can use this path to access files located in the same repository as your action. This variable is only supported in composite run steps actions.                                                                                                                                                                                                            |
 | `GITHUB_ACTIONS`     | Siempre establecido en `true` cuando {% data variables.product.prodname_actions %} está ejecutando el flujo de trabajo. Puedes usar esta variable para diferenciar cuando las pruebas se ejecutan de forma local o mediante {% data variables.product.prodname_actions %}.                                                                                                                         |
 | `GITHUB_ACTOR`       | El nombre de la persona o de la aplicación que inició el flujo de trabajo. Por ejemplo, `octocat`.                                                                                                                                                                                                                                                                                                   |
 | `GITHUB_REPOSITORY`  | El nombre del repositorio y del propietario. Por ejemplo, `octocat/Hello-World`.                                                                                                                                                                                                                                                                                                                     |
@@ -68,9 +69,9 @@ Te recomendamos encarecidamente que las acciones usen variables de entorno para
 | `GITHUB_REF`         | La referencia de etiqueta o rama que activó el flujo de trabajo. Por ejemplo, `refs/heads/feature-branch-1`. Si no hay una rama o una etiqueta disponible para el tipo de evento, la variable no existirá.                                                                                                                                                                                           |
 | `GITHUB_HEAD_REF`    | Solo se configura para eventos de solicitudes de cambio. El nombre de la rama principal.                                                                                                                                                                                                                                                                                                             |
 | `GITHUB_BASE_REF`    | Solo se configura para eventos de solicitudes de cambio. El nombre de la rama base.                                                                                                                                                                                                                                                                                                                  |
-| `GITHUB_SERVER_URL`  | Devuelve la URL del servidor de {% data variables.product.product_name %}. Por ejemplo: `https://github.com`.                                                                                                                                                                                                                                                                                        |
-| `GITHUB_API_URL`     | Devuelve la URL de la API. Por ejemplo: `https://api.github.com`.                                                                                                                                                                                                                                                                                                                                    |
-| `GITHUB_GRAPHQL_URL` | Devuelve la URL de la API de GraphQL. Por ejemplo: `https://api.github.com/graphql`.                                                                                                                                                                                                                                                                                                                 |
+| `GITHUB_SERVER_URL`  | Devuelve la URL del servidor de {% data variables.product.product_name %}. For example: `https://{% data variables.product.product_url %}`.                                                                                                                                                                                                                                                          |
+| `GITHUB_API_URL`     | Devuelve la URL de la API. For example: `{% data variables.product.api_url_code %}`.                                                                                                                                                                                                                                                                                                                 |
+| `GITHUB_GRAPHQL_URL` | Devuelve la URL de la API de GraphQL. For example: `{% data variables.product.graphql_url_code %}`.                                                                                                                                                                                                                                                                                                  |
 
 {% tip %}
 
@@ -84,10 +85,6 @@ Te recomendamos encarecidamente que las acciones usen variables de entorno para
 
 ### Convenciones de nomenclatura para las variables de entorno
 
-{% note %}
-
-**Nota:**{% data variables.product.prodname_dotcom %} reserva el prefijo de la variable de ambiente `GITHUB_` para uso interno de {% data variables.product.prodname_dotcom %}. Configurar una variable de entorno o secreto con el prefijo `GITHUB_` dará como resultado un error.
-
-{% endnote %}
+When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
 
 Toda variable de entorno nueva que configures y que apunte a una ubicación en el sistema de archivos debe tener un sufijo `_PATH`. Las variables predeterminadas `HOME` y `GITHUB_WORKSPACE` son excepciones a esta convención, porque las palabras "inicio" (home) y "espacio de trabajo" (workspace) ya implican una ubicación.
diff --git a/translations/es-ES/content/actions/reference/environments.md b/translations/es-ES/content/actions/reference/environments.md
index e8f03ab97f..56af6a0031 100644
--- a/translations/es-ES/content/actions/reference/environments.md
+++ b/translations/es-ES/content/actions/reference/environments.md
@@ -16,7 +16,7 @@ versions:
 Puedes configurr ambientes con reglas de protección y secretos. Cuando un job de un flujo de trabajo referencia un ambiente, el job no comenzará hasta que todas las reglas de protección del ambiente pasen. Un job tampoco puede acceder a los secretos que se definen en un ambiente sino hasta que todas las reglas de protección de dicho ambiente pasen.
 
 {% if currentVersion == "free-pro-team@latest" %}
-Environment protection rules and environment secrets are only available on public repositories and private repositories on an enterprise plan. If you convert a repository from public to private on a non-enterprise plan, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. Si conviertes tu repositorio en público nuevamente, tendrás acceso a cualquier regla de protección y secreto de ambiente que hubieras configurado previamente.
+Las reglas de protección de ambiente y los secretos de ambiente solo están disponibles en los repositorios públicos y privados de un plan empresarial. Si conviertes a un repositorio de público a privado en un plan no empresarial, cualquier regla de protección o secretos de ambiente configurados se ignorarán y no podrás configurar ningún ambiente. Si conviertes tu repositorio en público nuevamente, tendrás acceso a cualquier regla de protección y secreto de ambiente que hubieras configurado previamente.
 {% endif %}
 
 #### Reglas de protección de ambiente
@@ -48,6 +48,12 @@ Utiliza ramas de despliegue para restringir las ramas que pueden hacer despliegu
 
 Los secretos que se almacenan en un ambiente sólo se encuentran disponibles para los jobs de flujo de trabajo que referencien el ambiente. Si el ambiente requiere aprobación, un job no puede acceder a secretos de ambiente hasta que uno de los revisores requeridos lo apruebe. Para obtener más información sobre los secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)".
 
+{% note %}
+
+**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level as security as repository and organization secrets. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)".
+
+{% endnote %}
+
 ### Crear un ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -71,6 +77,9 @@ Para obtener más información sobre la sintaxis para referenciar ambientes en l
 
 Cuando un flujo de trabajo referencia un ambiente, éste aparecerá en los despliegues del repositorio. Para obtener más información acerca de visualizar los despliegues actuales y previos, consulta la sección "[Visualizar el historial de despliegues](/developers/overview/viewing-deployment-history)".
 
+### Utilizar la concurrencia para serializar los despliegues en un ambiente
+Puedes utilizar la concurrencia para que un ambiente tenga un máximo de un despliegue en progreso y un despliegue pendiente a la vez. Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#concurrency)".
+
 ### Borrar un ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -80,7 +89,7 @@ El borrar un ambiente borrará todos los secretos y reglas de protección asocia
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. Junto al ambiente que quieres borrar, da clic en {% octicon "trashcan" aria-label="The trashcan icon" %}.
+1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
 2. Da clic en **Entiendo, borra este ambiente**.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}También puedes borrar los ambientes a través de la API de REST Para obtener más información, consulta la sección "[Ambientes](/rest/reference/repos#environments)".{% endif %}
diff --git a/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md b/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md
index 1aa56f138d..5d901e00e9 100644
--- a/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/es-ES/content/actions/reference/events-that-trigger-workflows.md
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        echo "- in ${{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          echo "- in ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento `chec
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Carga del evento Webhook                           | Tipos de actividad                                                                           | `GITHUB_SHA`                                  | `GITHUB_REF`     |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------------------- | ---------------- |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | Última confirmación en la rama predeterminada | Rama por defecto |
+| Carga del evento Webhook                           | Tipos de actividad                                            | `GITHUB_SHA`                                  | `GITHUB_REF`     |
+| -------------------------------------------------- | ------------------------------------------------------------- | --------------------------------------------- | ---------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | Última confirmación en la rama predeterminada | Rama por defecto |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-Por ejemplo, puedes ejecutar un flujo de trabajo cuando una comprobación de ejecución ha sido `resolicitada` o `requested_action`.
+Por ejemplo, puedes ejecutar un flujo de trabajo cuando una ejecución de verificación esté como `rerequested` o `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ Por ejemplo, puedes ejecutar un flujo de trabajo cuando un proyecto ha sido `abi
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**Nota:** El tipo `prereleased` no se activará para los pre-lanzamientos publicados desde los borradores de lanzamientos, pero el tipo `published` sí lo hará. Si quieres que se ejecute un flujo de trabajo cuando se publiquen los lanzamientos estables *y* los pre-lanzamientos, mejor suscríbete a `published` en vez de a `released` y `prereleased`.
+
+{% endnote %}
+
 #### `status`
 
 Ejecuta tu flujo de trabajo en cualquier momento en que cambia el estado de una confirmación de Git, lo que activa el evento `status`. Para obtener más información acerca de la API de REST, consulta la sección "[Estados](/rest/reference/repos#statuses)".
diff --git a/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md
index 2ac0b684f2..36556e09a8 100644
--- a/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/es-ES/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### Agregar una ruta de sistema
diff --git a/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md
index 8cf552899d..c14a01a73e 100644
--- a/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -110,8 +110,8 @@ El siguiente flujo de trabajo se ejecutará en las subidas a `releases/10` o `re
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
@@ -122,13 +122,13 @@ Las palabras clave `paths-ignore` y `paths` aceptan los patrones globales que us
 
 #### Ejemplo de ignorar rutas
 
-When all the path names match patterns in `paths-ignore`, the workflow will not run. {% data variables.product.prodname_dotcom %} evalúa los patrones definidos en `paths-ignore` para compararlos con el nombre de ruta. Un flujo de trabajo con el siguiente filtro de ruta solo se ejecutará en los eventos de `subida` que incluyan al menos un archivo externo al directorio `docs` en la raíz del repositorio.
+Cuando todos los nombres de ruta coincidan con los patrones en `paths-ignore`, el flujo de trabajo no se ejecutará. {% data variables.product.prodname_dotcom %} evalúa los patrones definidos en `paths-ignore` para compararlos con el nombre de ruta. Un flujo de trabajo con el siguiente filtro de ruta solo se ejecutará en los eventos de `subida` que incluyan al menos un archivo externo al directorio `docs` en la raíz del repositorio.
 
 ```yaml
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
 #### Ejemplo de incluir rutas
@@ -139,7 +139,7 @@ Si al menos una ruta coincide con un patrón del filtro de `rutas`, se ejecuta e
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
 #### Excluir rutas
@@ -160,8 +160,8 @@ Este ejemplo se ejecuta cada vez que el evento de `subida` incluye un archivo en
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
 #### Comparaciones de diferencias de Git
@@ -187,6 +187,32 @@ Para obtener más información, consulta "[Acerca de comparar ramas en las solic
 
 Para obtener más información acerca de la sintaxis cron, consulta "[Eventos que activan flujos de trabajo](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)."
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `permisos`
+
+Puedes modificar los permisos predeterminados que se otorgaron al `GITHUB_TOKEN` si agregas o eliminas el acceso según se requiera para que solo permitas el acceso mínimo requerido. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
+
+Puedes utilizar los `permissions` ya sea como una clave de nivel superior, para aplicar todos los jobs en el flujo de trabajo, o dentro de jobs específicos. Cuando agregas la clave `permissions` dentro de un job específico, todas las acciones y comandos de ejecución dentro de este que utilicen el `GITHUB_TOKEN` obtendrán los derechos de acceso que especificas.  Para obtener más información, consulta los [`jobs<job_id>permissions`](#jobsjob_idpermissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Ejemplo
+
+Este ejemplo muestra los permisos que se están configurando para el `GITHUB_TOKEN` que aplicará a todos los jobs en el flujo de trabajo. Se otorga acceso de lectura a todos los permisos.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
+
 ### `env`
 
 Un `map` de las variables de ambiente que se encuentran disponibles para los pasos de todos los jobs en el flujo de trabajo. También puedes configurar variables de ambiente que solo estén disponibles para los pasos en un solo job o en un solo paso. Para obtener más información, consulta [`jobs.<job_id>.env`](#jobsjob_idenv) y [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
@@ -221,6 +247,18 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión solo puede utilizar el contexto `github`. Para obtener más información acerca de las expresiones, consulta la sección "[Contexto y sintaxis de expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
+
+También puedes especificar la `concurrency` a nivel del job. Para obtener más información, consulta la [`jobs<job_id>concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `Trabajos`
 
 Una ejecución de flujo de trabajo está compuesta por uno o más trabajos. De forma predeterminada, los trabajos se ejecutan en paralelo. Para ejecutar trabajos de manera secuencial, puedes definir dependencias en otros trabajos utilizando la palabra clave `jobs.<job_id>.needs`.
@@ -339,6 +377,34 @@ runs-on: [self-hosted, linux]
 
 Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" y "[Usar ejecutores autoalojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)".
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
+
+Puedes modificar los permisos predeterminados que se otorgaron al `GITHUB_TOKEN` si agregas o eliminas el acceso según se requiera para que solo permitas el acceso mínimo requerido. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
+
+Si especificas el permiso dentro de una definición de job, puedes configurar un conjunto diferente de permisos para el `GITHUB_TOKEN` de cada job, en caso de que se requiera. Como alternativa, puedes especificar los permisos para todos los jobs en el flujo de trabajo. Para obtener más información sobre los permisos que se definen a nivel del flujo de trabajo, consulta los [`permissions`](#permissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Ejemplo
+
+Este ejemplo muestra los permisos que se están configurando para el `GITHUB_TOKEN`, los cuales solo aplicarán al job que se llama `stale`. Se otorga permiso de escritura a los alcances `issues` y `pull-requests`. El resto de los alcances no tendrán acceso.
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 ### `jobs.<job_id>.environment`
 
@@ -347,10 +413,11 @@ El ambiente que referencia el job. Todas las reglas de protección del ambiente
 Puedes proporcionar el ambiente como solo el `name` de éste, o como un objeto de ambiente con el `name` y `url`. La URL mapea hacia `environment_url` en la API de despliegues. Para obtener más información sobre la API de despliegues, consulta la sección "[Despliegues](/rest/reference/repos#deployments)".
 
 ##### Ejemplo utilizando solo el nombre de un ambiente
-
+{% raw %}
 ```yaml
 environment: staging_environment
 ```
+{% endraw %}
 
 ##### Ejemplo utilizando un nombre y URL del ambiente
 
@@ -372,6 +439,25 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**Nota:** Cuando se especifica la concurrencia a nivel del job, no se garantiza el orden para los jobs o ejecuciones que se ponen en fila a 5 minutos uno del otro.
+
+{% endnote %}
+
+La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión puede utilizar cualquier contexto, con excepción del contexto `secrets`. Para obtener más información acerca de las expresiones, consulta la sección "[Contexto y sintaxis de expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
+
+También puedes especificar la `concurrency` a nivel del flujo de trabajo. Para obtener más información, consulta la [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
 Un `map` de salidas para un job. Las salidas de un job se encuentran disponibles para todos los jobs descendentes que dependan de este job. Para obtener más información sobre la definición de dependencias, consulta [`jobs.<job_id>.needs`](#jobsjob_idneeds).
@@ -392,15 +478,15 @@ jobs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
@@ -470,14 +556,14 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
@@ -609,11 +695,11 @@ jobs:
 ```
 
 {% if currentVersion == "free-pro-team@latest" %}
-##### Ejemplo de uso del {% data variables.product.prodname_github_container_registry %}
+##### Ejemplo de uso del {% data variables.product.prodname_container_registry %} del {% data variables.product.prodname_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-Una imagen de Docker en el {% data variables.product.prodname_github_container_registry %}.
+Una imagen de Docker en el {% data variables.product.prodname_container_registry %} del {% data variables.product.prodname_registry %}.
 
 ```yaml
 jobs:
@@ -639,7 +725,9 @@ jobs:
 
 #### Ejemplo de cómo utilizar una acción dentro de un repositorio privado diferente al flujo de trabajo
 
-Tu flujo de trabajo debe registrar el repositorio privado y referenciar la acción de forma local.
+Tu flujo de trabajo debe registrar el repositorio privado y referenciar la acción de forma local. Genera un token de acceso personal y agrega el token como un secreto cifrado. Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)".
+
+Reemplaza a `PERSONAL_ACCESS_TOKEN` en el ejemplo con el nombre de tu secreto.
 
 {% raw %}
 ```yaml
@@ -651,7 +739,7 @@ jobs:
         with:
           repository: octocat/my-private-repo
           ref: v1.0
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
           path: ./.github/actions/my-private-repo
       - name: Run my action
         uses: ./.github/actions/my-private-repo/my-action
@@ -692,7 +780,7 @@ Usando la palabra clave `working-directory`, puedes especificar el directorio de
 
 #### Uso de un shell específico
 
-Puedes anular los parámetros predeterminados del shell en el sistema operativo del ejecutor utilizando la palabra clave `shell`. Puedes usar palabras clave incorporadas de `shell` keywords, o puedes definir un conjunto personalizado de opciones de shell.
+Puedes anular los parámetros predeterminados del shell en el sistema operativo del ejecutor utilizando la palabra clave `shell`. Puedes usar palabras clave incorporadas de `shell`, o puedes definir un conjunto personalizado de opciones de shell.
 
 | Plataforma compatible | parámetro `shell` | Descripción                                                                                                                                                                                                                                                                                                    | Comando ejecutado interamente                   |
 | --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
@@ -775,7 +863,7 @@ Para obtener más información sobre el software que se incluye en los ejecutore
 
 #### Códigos de salida y preferencia de acción de error
 
-Para palabras clave shell incorporadas, brindamos los siguientes valores predeterminados accionados por los ejecutores alojados {% data variables.product.prodname_dotcom %}. Deberías usar estos lineamientos al ejecutar scripts shell.
+Para palabras clave shell incorporadas, brindamos los siguientes valores predeterminados accionados por los ejecutadores alojados por {% data variables.product.prodname_dotcom %}. Deberías usar estos lineamientos al ejecutar scripts de shell.
 
 - `bash`/`sh`:
   - Comportamiento a prueba de fallos utilizando `set -eo pipefail`: Valor predeterminado para `bash` y `shell` incorporado. También es el valor predeterminado cuando no proporcionas una opción en plataformas que no son de Windows.
@@ -793,11 +881,11 @@ Para palabras clave shell incorporadas, brindamos los siguientes valores predete
 
 ### `jobs.<job_id>.steps[*].with`
 
-Un `mapa` de los parámetros de entrada definidos por la acción. Cada parámetro de entrada es un par clave/valor. Los parámetros de entrada se establecen como variables del entorno. La variable tiene el prefijo `INPUT_` y se convierte en mayúsculas.
+Un `mapa` de los parámetros de entrada definidos por la acción. Cada parámetro de entrada es un par clave/valor. Los parámetros de entrada se establecen como variables de entorno. La variable tiene el prefijo `INPUT_` y se convierte en mayúsculas.
 
 #### Ejemplo
 
-Define los tres parámetros de entrada (`first_name`, `middle_name`, and `last_name`) definidos por la acción `hello_world`. Es posible acceder a estas variables de entrada con la acción `hello-world` como `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` y las variables de entorno `INPUT_LAST_NAME`.
+Define los tres parámetros de entrada (`first_name`, `middle_name` y `last_name`) definidos por la acción `hello_world`. Es posible acceder a estas variables de entrada con la acción `hello-world` como `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` y las variables de entorno `INPUT_LAST_NAME`.
 
 ```yaml
 jobs:
@@ -836,7 +924,7 @@ Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si u
 
 ### `jobs.<job_id>.steps[*].with.entrypoint`
 
-Anula el Docker `ENTRYPOINT` en el `Dockerfile` o lo establece si es que no tiene uno especificado. A diferencia de la instrucción Docker `ENTRYPOINT` que tiene un shell y formulario de ejecución, la palabra clave `entrypoint` acepta solo una cadena que define el ejecutable que se ejecutará.
+Anula el `PUNTO DE ENTRADA` de Docker en el `Dockerfile` o lo establece si es que no tiene uno especificado. A diferencia de la instrucción Docker `ENTRYPOINT` que tiene un shell y formulario de ejecución, la palabra clave `entrypoint` acepta solo una cadena que define el ejecutable que se ejecutará.
 
 #### Ejemplo
 
@@ -873,7 +961,7 @@ steps:
 
 ### `jobs.<job_id>.steps[*].continue-on-error`
 
-Impide que un trabajo falle cuando falla un paso. Se lo debe establecer en `true` para permitir que un trabajo pase cuando falla este paso.
+Impide que un trabajo falle cuando falla un paso. Se lo debe establecer en `verdadero` para permitir que un trabajo pase cuando falla este paso.
 
 ### `jobs.<job_id>.steps[*].timeout-minutes`
 
@@ -899,7 +987,7 @@ El orden en que defines una `matriz` importa. La primera opción que definas ser
 
 #### Ejemplo de ejecución con más de una versión de Node.js
 
-Puedes especificar una matriz proporcionando una variedad de opciones de configuración. Por ejemplo, si el ejecutor admite las versiones 6, 8 y 10 de Node.js, puedes especificar una matriz de esas versiones en la `matriz`.
+Puedes especificar una matriz proporcionando una variedad de opciones de configuración. Por ejemplo, si el ejecutor admite las versiones 10, 12 y 14 de Node.js, puedes especificar una matriz de esas versiones en la `matriz`.
 
 Este ejemplo crea una matriz de tres trabajos estableciendo la clave `node` para una matriz de tres versiones de Node.js. Para usar la matriz, el ejemplo establece la propiedad de contexto `matrix.node` como el valor del parámetro `node-version` de la entrada de la acción `setup-node`. Como resultado, se ejecutarán tres trabajos, cada uno usando una versión diferente de Node.js.
 
@@ -907,12 +995,12 @@ Este ejemplo crea una matriz de tres trabajos estableciendo la clave `node` para
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
-  # Configura la versión del nodo usada en los ejecutores alojados de GitHub
-  - uses: actions/setup-node@v1
+  # Configures the node version used on GitHub-hosted runners
+  - uses: actions/setup-node@v2
     with:
-      # La versión de Node.js a configurar
+      # The Node.js version to configure
       node-version: ${{ matrix.node }}
 ```
 {% endraw %}
@@ -933,10 +1021,10 @@ Puedes crear una matriz para ejecutar flujos de trabajo en más de un sistema op
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
@@ -948,7 +1036,7 @@ steps:
 
 #### Ejemplo que incluye valores adicionales en combinaciones
 
-Puedes agregar más opciones de configuración a un trabajo de una matriz de construcción ya existente. Por ejemplo, si quieres usar una versión específica de `npm` cuando se ejecuta el trabajo que usa `windows-latest` y la versión 4 de `node`, puedes usar `incluir` para especificar esa opción adicional.
+Puedes agregar más opciones de configuración a un trabajo de una matriz de construcción ya existente. Por ejemplo, si quieres usar una versión específica de `npm` cuando se ejecuta el trabajo que usa `windows-latest` y la versión 8 de `node`, puedes usar `incluir` para especificar esa opción adicional.
 
 {% raw %}
 ```yaml
@@ -956,29 +1044,29 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 2
+      # includes a new variable of npm with a value of 6
       # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
 #### Ejemplo que incluye combinaciones nuevas
 
-Puedes utilizar `include` para agregar jobs nuevos a una matriz de compilaciones. Cualquier configuración de "include" sin coincidencia exacta e agregará a la matriz. Por ejemplo, si quieres utilizar `node` versión 12 para compilar en varios sistemas operativos, pero quieres un job experimental extra que utilice node versión 13 en Ubintu, puedes utilizar `include` para especificar este job adicional.
+Puedes utilizar `include` para agregar jobs nuevos a una matriz de compilaciones. Cualquier configuración de "include" sin coincidencia exacta e agregará a la matriz. Por ejemplo, si quieres utilizar `node` versión 14 para compilar en varios sistemas operativos, pero quieres un job experimental extra que utilice node versión 15 en Ubintu, puedes utilizar `include` para especificar este job adicional.
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -986,7 +1074,7 @@ strategy:
 
 #### Ejemplos que excluyen configuraciones de una matriz
 
-Puedes eliminar una configuración específica definida en la matriz de construcción mediante la opción `exclude`. Si usas `exclude`, se elimina un puesto definido por la matriz de construcción. El número de puestos es el producto cruzado de la cantidad de sistemas operativos (`os`) incluidos en las matrices que brindas, menos todas las sustracciones (`exclude`).
+Puedes eliminar una configuración específica definida en la matriz de construcción mediante la opción `excluir`. Si usas `excluir`, se elimina un trabajo definido por la matriz de construcción. El número de puestos es el producto cruzado de la cantidad de sistemas operativos (`os`) incluidos en las matrices que brindas, menos todas las sustracciones (`excluir`).
 
 {% raw %}
 ```yaml
@@ -994,11 +1082,11 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # excluye el nodo 4 en macOS
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
@@ -1016,11 +1104,11 @@ Puedes agregar variables de ambiente personalizadas para cada combinación de pr
 
 ### `jobs.<job_id>.strategy.fail-fast`
 
-Cuando se establece en `verdadero`, {% data variables.product.prodname_dotcom %} cancela todos los trabajos en curso si falla cualquier trabajo de `matriz`. Predeterminado: `true`
+Cuando se establece en `verdadero`, {% data variables.product.prodname_dotcom %} cancela todos los trabajos en curso si falla cualquier trabajo de `matriz`. Predeterminado: `verdadero`
 
 ### `jobs.<job_id>.strategy.max-parallel`
 
-La cantidad máxima de trabajos que se pueden ejecutar de manera simultánea cuando se utiliza una estrategia de trabajo `matrix`. Por defecto, {% data variables.product.prodname_dotcom %} maximizará el número de trabajos ejecutados en paralelo dependiendo de los ejecutores disponibles en las máquinas virtuales alojadas en {% data variables.product.prodname_dotcom %}.
+La cantidad máxima de trabajos que se pueden ejecutar de manera simultánea cuando se utiliza una estrategia de trabajo `matrix`. De manera predeterminada, {% data variables.product.prodname_dotcom %} maximizará el número de trabajos ejecutados en paralelo dependiendo de los ejecutadores disponibles en las máquinas virtuales alojadas en {% data variables.product.prodname_dotcom %}.
 
 ```yaml
 strategy:
@@ -1033,7 +1121,7 @@ Previene que una ejecución de flujo de trabajo falle cuando un job falle. Confi
 
 #### Ejemplo que previene que un job específico de una matiz fallida haga que falle una ejecución de flujo de trabajo
 
-Puedes permitir que ciertos jobs en una matriz de jobs fallen sin que la ejecución de flujo de trabajo falle. Por ejemplo, si querías permitir que fallara únicamente un job experimental con el `node` configurado en `13` sin que fallara la ejecución del flujo de trabajo.
+Puedes permitir que ciertos jobs en una matriz de jobs fallen sin que la ejecución de flujo de trabajo falle. Por ejemplo, si querías permitir que fallara únicamente un job experimental con el `node` configurado en `15` sin que fallara la ejecución del flujo de trabajo.
 
 {% raw %}
 ```yaml
@@ -1042,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -1056,7 +1144,7 @@ strategy:
 
 Un contenedor para ejecutar todos los pasos de un trabajo que aún no especifica un contenedor. Si tienes pasos que usan tanto acciones de script como de contenedor, las acciones de contenedor se ejecutarán como contenedores hermanos en la misma red con los mismos montajes de volumen.
 
-Si no configuras un `container`, todos los pasos se ejecutan directamente en el host especificado por `runs-on` a menos que un paso se refiera a una acción configurada para ejecutarse en un contenedor.
+Si no configuras un `contenedor`, todos los pasos se ejecutan directamente en el host especificado por `runs-on` a menos que un paso se refiera a una acción configurada para ejecutarse en un contenedor.
 
 #### Ejemplo
 
@@ -1064,7 +1152,7 @@ Si no configuras un `container`, todos los pasos se ejecutan directamente en el
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -1079,7 +1167,7 @@ Cuando solo especificas una imagen de contenedor, puedes omitir la palabra clave
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
@@ -1134,7 +1222,7 @@ volumes:
 
 ### `jobs.<job_id>.container.options`
 
-Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)".
+Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta "[`opciones de creación de docker`](https://docs.docker.com/engine/reference/commandline/create/#options)."
 
 ### `jobs.<job_id>.services`
 
@@ -1181,7 +1269,7 @@ La imagen de Docker para usar como el contenedor de servicios para ejecutar la a
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
@@ -1224,7 +1312,7 @@ volumes:
 
 ### `jobs.<job_id>.services.<service_id>.options`
 
-Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)".
+Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta "[`opciones de creación de docker`](https://docs.docker.com/engine/reference/commandline/create/#options)."
 
 ### Hoja de referencia de patrones de filtro
 
diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 0e3d15a941..3ae60bfc66 100644
--- a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ Para encontrar una lista general de las herramientas que se incluyen en cada sis
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ Te recomendamos utilizar acciones para interactuar con el software instalado en
 
 Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments). Este repositorio también contiene anuncios sobre todas las actualizaciones de software principales en los ejecutores.
 
+#### Instalar software adicional
+
+Puedes instalar software adicional en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección [Personalizar los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
 ### Direcciones IP
 
 {% note %}
diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..83fd2ace7e
--- /dev/null
+++ b/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Personalizar los ejecutores hospedados en GitHub
+intro: Puedes instalar software adicional en los ejecutores hospedados en GitHub como parte de tu flujo de trabajo.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+Si requieres paquetes de software adicionales en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes crear un job que instale los paquetes como parte de tu flujo de trabajo.
+
+Para ver los paquetes que ya se instalaron predeterminadamente, consulta la sección "[Software preinstalado](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)".
+
+Esta guía demuestra cómo crear un job que instala software adicional en un ejecutor hospedado en {% data variables.product.prodname_dotcom %}.
+
+### Instalar software en ejecutores Ubuntu
+
+El siguiente ejemplo demuestra cómo instalar un paquete de `apt` como parte de un job.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**Nota:** Ejecuta siempre `sudo apt-get update` antes de instalar un paquete. En caso de que el índice de `apt` esté desactualizado, este comando recupera y re-indiza cualquier paquete disponible, lo cual ayuda a prevenir los fallos en la instalación de paquetes.
+
+{% endnote %}
+
+### Instalar el software en los ejecutores de macOS
+
+El siguiente ejemplo demuestra cómo instalar paquetes y barriles de Brew como parte de un job.
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### Instalar software en ejecutores Windows
+
+El siguiente ejemplo demuestra cómo utilizar [Chocolatey](https://community.chocolatey.org/packages) para instalar el CLI de {% data variables.product.prodname_dotcom %} como parte de un job.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/index.md b/translations/es-ES/content/actions/using-github-hosted-runners/index.md
index 6b20dce496..c7a9d3e87d 100644
--- a/translations/es-ES/content/actions/using-github-hosted-runners/index.md
+++ b/translations/es-ES/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% data reusables. actions. enterprise-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/es-ES/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/es-ES/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..3a9f9a0cf2
--- /dev/null
+++ b/translations/es-ES/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: Acerca del licenciamiento para GitHub Advanced Security
+intro: 'You need a license to use {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### Acerca del licenciamiento para {% data variables.product.prodname_GH_advanced_security %}
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información acerca de {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)".
+
+{% data reusables.advanced-security.license-overview %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for {% data variables.product.product_name %}, contact {% data variables.contact.contact_enterprise_sales %}. To enable {% data variables.product.prodname_GH_advanced_security %}, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your appliance](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### Acerca de los números de confirmante para {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### Administrar tu uso de licencia para {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+Puedes requerir políticas para permitir o dejar de permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen la {% data variables.product.prodname_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
+
+Para obtener más información sobre cómo visualizar el uso de licencia, consulta la sección "[Visualizar tu uso de la {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/viewing-your-github-advanced-security-usage)".
+
+### Obtener el máximo de tu licencia de {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..f86f899b24
--- /dev/null
+++ b/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: Configurar el escaneo de código para tu aplicativo
+shortTitle: Configurar el escaneo de código
+intro: 'Puedes habilitar, configurar e inhabilitar el {% data variables.product.prodname_code_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} permite que los usuarios escaneen el código para encontrar vulnerabilidades y errores.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### Acerca de {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+### Ejecutar el {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_actions %}
+
+#### Configurar un ejecutor auto-hospedado
+
+{% data variables.product.prodname_ghe_server %} puede ejecutar un {% data variables.product.prodname_code_scanning %} utilizando un flujo de trabajo de {% data variables.product.prodname_actions %}. Primero, necesitas aprovisionar uno o más ejecutores auto-hospedados de {% data variables.product.prodname_actions %} en tu ambiente. Puedes aprovisionar ejecutores auto-hospedados a nivel de repositorio, organización o empresa. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
+
+Debes asegurarte de que Git esté en la variable de "PATH" de cualquier ejecutor auto-hospedado que utilices para ejecutar las acciones de {% data variables.product.prodname_codeql %}.
+
+#### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+La acción {% data variables.product.prodname_codeql %} se incluye en tu instalación de {% data variables.product.prodname_ghe_server %}. Si {% data variables.product.prodname_ghe_server %} tiene acceso a internet, la acción descargará automáticamente el paquete de {% data variables.product.prodname_codeql %} que se requiere para realizar el análisis. Como alternativa, puedes utilizar una herramienta de sincronización para hacer disponible el paquete de análisis de {% data variables.product.prodname_codeql %} localmente. Para obtener más información, consulta la sección "[Configurar el análisis de {% data variables.product.prodname_codeql %} en un servidor sin acceso a internet](#configuring-codeql-analysis-on-a-server-without-internet-access)" a continuación.
+
+También puedes hacer que acciones de terceros estén disponibles para el {% data variables.product.prodname_code_scanning %} para los usuarios si configuras {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Configurar a {% data variables.product.prodname_github_connect %} para que se sincronice con {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" más adelante.
+
+#### Configurar el análisis de {% data variables.product.prodname_codeql %} en un servidor sin acceso a internet
+Si el servidor en el que estás ejecutando a {% data variables.product.prodname_ghe_server %} no está conectado a internet y quieres permitir que los usuarios habiliten el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} para sus repositorios, debes utilizar la herramienta de sincronización de la acción de {% data variables.product.prodname_codeql %} para copiar el paquete de análisis de {% data variables.product.prodname_codeql %} desde {% data variables.product.prodname_dotcom_the_website %} hacia tu servidor. La herramienta y los detalles de su uso se encuentran disponibles en [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/).
+
+Si configuras la herramienta de sincronización de la acción de {% data variables.product.prodname_codeql %}, puedes utilizarla para sincronizar los últimos lanzamientos de la acción de {% data variables.product.prodname_codeql %} y el paquete de análisis de {% data variables.product.prodname_codeql %} relacionado. Estos son compatibles con {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+Para ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_ghe_server %} con las {% data variables.product.prodname_actions %}, las acciones adecuadas deben estar disponibles localmente. Puedes hacer que las acciones estén disponibles en tres formas.
+
+- **Recomendada**: Puedes utilizar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para descargar acciones automáticamente desde {% data variables.product.prodname_dotcom_the_website %}. La máquina que hospeda tu instancia debe poder acceder a {% data variables.product.prodname_dotcom_the_website %}. Este enfoque garantiza que obtengas el software más reciente de forma automática. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_github_connect %} para que se sincronice con {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)".
+- Si quieres utilizar el {% data variables.product.prodname_codeql_workflow %}, puedes sincronizar el repositorio de {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.prodname_ghe_server %}, utilizando la herramienta de sincronización de acciones de {% data variables.product.prodname_codeql %} en [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Puedes utilizar esta herramienta sin importar si {% data variables.product.product_location %} o tus ejecutores de {% data variables.product.prodname_actions %} tienen acceso a internet, siempre y cuando puedas acceder tanto a {% data variables.product.product_location %} como a {% data variables.product.prodname_dotcom_the_website %} de forma simultánea en tu computadora.
+- Puedes crear una copia local del repositorio de una accion en tu servidor si clonas el repositorio de {% data variables.product.prodname_dotcom_the_website %} que contiene la acción. Por ejemplo, si quieres utilizar acciones para el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, puedes crear un repositorio en tu instancia, el cual se llame `github/codeql-action`, y luego clonar el [repositorio](https://github.com/github/codeql-action) desde {% data variables.product.prodname_dotcom_the_website %} y posteriormente subir ese repositorio en el de `github/codeql-action` de tu instancia. También necesitarás descargar cualquiera de los lanzamientos del repositorio en {% data variables.product.prodname_dotcom_the_website %} y cargarlos en el repositorio de `github/codeql-action` de tu instancia como lanzamientos.
+{% endif %}
+
+#### Configurar {% data variables.product.prodname_github_connect %} para sincronizarse con {% data variables.product.prodname_actions %}
+1. Si quieres descargar flujos de trabajo de acciones por petición desde {% data variables.product.prodname_dotcom_the_website %}, necesitarás habilitar {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)".
+2. También tendrás que habilitar {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)".
+3. El siguiente paso es configurar el acceso a las acciones en {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+4. Agrega un ejecutor auto-hospedado a tu repositorio, organización, o cuenta empresarial. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+### Ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %}
+Si no quieres utilizar {% data variables.product.prodname_actions %}, puedes ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %}.
+
+El {% data variables.product.prodname_codeql_runner %} es una herramienta de línea de comandos que puedes agregar a tu sistema de IC/CD de terceros. Esta herramienta ejecuta el análisis de {% data variables.product.prodname_codeql %} en un control de un repositorio de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
diff --git a/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..9ca65faacf
--- /dev/null
+++ b/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: Configurar el escaneo de secretos para tu aplicativo
+shortTitle: Configurar el escaneo de secretos
+intro: 'Puedes habilitar, configurar e inhabilitar el {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} permite a los usuarios escanear código para los secretos que se confirmaron por accidente.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### Acerca de {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+
+### Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+
+- Necesitas habilitar el marcador de CPU de las [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extenciones SIMD de Streaming Suplementario 3, por sus siglas en inglés) en el VM/KVM que ejecuta {% data variables.product.product_location %}.
+
+- A license for {% data variables.product.prodname_GH_advanced_security %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### Verificar la compatibilidad del marcador de las SSSE3 en tus vCPU
+
+El conjunto de instrucciones de las SSSE3 se requiere porque el {% data variables.product.prodname_secret_scanning %} impulsa el patrón acelerado de hardware que empata para encontrar las credenciales potenciales que se confirmaron en tus repositorios de {% data variables.product.prodname_dotcom %}. Las SSSE3 se habilitan para la mayoría de los CPU modernos. Puedes verificar si las SSSE3 están habilitadas para los vCPU disponibles para tu instancia de {% data variables.product.prodname_ghe_server %}.
+
+1. Conéctate al shell administrativo para tu instancia de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+2. Ingresa el siguiente comando:
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+Si esto devuelve el valor `0`, esto significa que el marcador de SSSE3 se encuentra disponible y habilitado. Ahora puedes habilitar el {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+Si no se devuelve un `0`, entonces no se ha habilitado las SSSE3 en tu VM/KVM. Necesitarás referirte a la documentación del hardware/hípervisor para encontrar cómo habilitar el marcador o ponerlo disponible como VM invitadas.
+
+#### Verificar si tienes una licencia de {% data variables.product.prodname_advanced_security %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Verifica si hay una entrada de **{% data variables.product.prodname_advanced_security %}** en la barra lateral izquierda. ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### Habilitar las {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Debajo de "{% data variables.product.prodname_advanced_security %}", da clic en **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### Inhabilitar las {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Debajo de "{% data variables.product.prodname_advanced_security %}", deselecciona **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..65b10d4662
--- /dev/null
+++ b/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% if currentVersion == "enterprise-server@3.0" %}Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración y análisis de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+{% endif %}
+
+### Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} For information about licensing, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
+2. Upload the new license to {% data variables.product.product_location %}. For more information, see "[Managing your GitHub Enterprise license](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Under "{% data variables.product.prodname_advanced_security %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %}
+1. Debajo de "{% data variables.product.prodname_advanced_security %}", da clic en **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_code_scanning %} en tu aplicativo](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+
+### Habilitar o inhabilitar el {% data variables.product.prodname_GH_advanced_security %} a través del shell administrativo (SSH)
+
+You can enable or disable features programmatically on {% data variables.product.product_location %}. Para obtener más información acerca de las utilidades del shell administrativo y de la línea de comandos para {% data variables.product.prodname_ghe_server %}, consulta las secciones "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[Utilidades de la línea de comandos](/admin/configuration/command-line-utilities#ghe-config)".
+
+Por ejemplo, puedes habilitar el {% data variables.product.prodname_code_scanning %} con tus herramientas de infraestructura como código cuando despliegas una instancia para pruebas o recuperación de desastres.
+
+1. SSH en {% data variables.product.product_location %}.
+1. Habilitar el {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. Opcionalmente, inhabilita el {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. Aplica la configuración
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}To enable and disable {% data variables.product.prodname_secret_scanning %} in the same way, set: `ghe-config app.secret-scanning.enabled` true or false and apply the configuration.{% endif %}
diff --git a/translations/es-ES/content/admin/advanced-security/index.md b/translations/es-ES/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..f33f1f201b
--- /dev/null
+++ b/translations/es-ES/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing GitHub Advanced Security for your enterprise
+shortTitle: Managing GitHub Advanced Security
+intro: 'You can configure {% data variables.product.prodname_advanced_security %} and manage use by your enterprise to suit your organization''s needs.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### Índice
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..7ecad4ca65
--- /dev/null
+++ b/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,23 @@
+---
+title: Visualizar tu uso de GitHub Advanced Security
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."
+
+### Viewing license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+You can check how many seats your license includes and how many seats are currently in use.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Opcionalmente, haz clic en el nombre de una organización que te pertenezca para mostrar la configuración de seguridad y análisis para la organización. ![Organización que te pertenece en la sección de {% data variables.product.prodname_GH_advanced_security %} de la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
diff --git a/translations/es-ES/content/admin/all-releases.md b/translations/es-ES/content/admin/all-releases.md
new file mode 100644
index 0000000000..0977c4d35e
--- /dev/null
+++ b/translations/es-ES/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Enterprise Server releases
+intro: 'Documentation for the currently supported and previously deprecated versions of {{ site.data.variables.product.prodname_ghe_server }}.'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## Actualmente compatibles
+
+See [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) for information about the latest release.
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## Obsoletizado
+
+Documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## Deprecated developer documentation
+
+Developer documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index 3ef8dd3c64..6170aef9b8 100644
--- a/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: 'Puedes utilizar la autenticación incluida en {% if enterpriseServerVers
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### Acerca de la administración de identidades y de accesos para tu empresa
diff --git a/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index dc66b0ec94..512e39f5fc 100644
--- a/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/es-ES/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### Acerca de la autenticación integrada para usuarios fuera de tu proveedor de identidad
diff --git a/translations/es-ES/content/admin/authentication/changing-authentication-methods.md b/translations/es-ES/content/admin/authentication/changing-authentication-methods.md
index e82c90e390..b16df0621a 100644
--- a/translations/es-ES/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/es-ES/content/admin/authentication/changing-authentication-methods.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Cuando modificas el método de autenticación, las cuentas de usuario en {% data variables.product.product_location %} se conservan y los usuarios seguirán iniciando sesión en la misma cuenta siempre que su nombre de usuario no cambie.
diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index a33957c48d..9ad5ebd06f 100644
--- a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Acerca de la autenticación y el aprovisionamiento de usuarios con Azure AD
diff --git a/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index 236e4f742b..4d87a29242 100644
--- a/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Acerca de SAML SSO
diff --git a/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index c9501268c5..f0d060220c 100644
--- a/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Acerca del aprovisionamiento de usuarios para tu empresa
diff --git a/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index 1dc4449261..143108fda2 100644
--- a/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/es-ES/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: 'Si usas la autenticación integrada, puedes impedir que las personas no autenticadas puedan crear una cuenta.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/authentication/using-built-in-authentication.md b/translations/es-ES/content/admin/authentication/using-built-in-authentication.md
index 9aac0d7e31..6e48070cce 100644
--- a/translations/es-ES/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/es-ES/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Puedes crear mensajes personalizados que los usuarios verán en las páginas de inicio de sesión y de cierre de sesión. Para obtener más información, consulta "[Personalizar mensajes de usuario en tu instancia](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)."
diff --git a/translations/es-ES/content/admin/authentication/using-cas.md b/translations/es-ES/content/admin/authentication/using-cas.md
index 3abd7bf252..634e8579e2 100644
--- a/translations/es-ES/content/admin/authentication/using-cas.md
+++ b/translations/es-ES/content/admin/authentication/using-cas.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'CAS es un protocolo de inicio de sesión único (SSO) para varias aplicaciones web. Una cuenta de usuario de CAS no ocupa una licencia de usuario de {% if currentVersion ver_gt "enterprise-server@2.16" %}{% else %}plaza{% endif %} hasta que el usuario inicie sesión.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/es-ES/content/admin/authentication/using-ldap.md b/translations/es-ES/content/admin/authentication/using-ldap.md
index 834c629e5d..8a1e88def3 100644
--- a/translations/es-ES/content/admin/authentication/using-ldap.md
+++ b/translations/es-ES/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: 'LDAP te permite autenticar el {% data variables.product.prodname_ghe_server %} en tus cuentas existentes y administrar de manera centralizada el acceso a los repositorios. LDAP es un protocolo de aplicación popular para acceder a servicios de información de directorios y mantenerlos, y uno de los protocolos más comunes que se usan para integrar software de terceros con directorios de usuarios de empresas grandes.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/es-ES/content/admin/authentication/using-saml.md b/translations/es-ES/content/admin/authentication/using-saml.md
index a8e54e7dd2..cfe5a78d63 100644
--- a/translations/es-ES/content/admin/authentication/using-saml.md
+++ b/translations/es-ES/content/admin/authentication/using-saml.md
@@ -9,7 +9,11 @@ intro: 'SAML is an XML-based standard for authentication and authorization. {% d
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md b/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md
index 7efb570693..c782df36f8 100644
--- a/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/es-ES/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: 'Puedes utilizar el panel de administrador de sitio{% if enterpriseServer
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 La primera vez que accedes a tu empresa, completarás una configuración inicial para hacer que
-{% data variables.product.product_name %} esté listo para utilizarse. Esta configuración inicial incluye el conectarse a tu empresa con un IdP, autenticarse con el SSO de SAML, y configurar las políticas para los repositorios y organizaciones en tu empresa. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
-
-Para que los usuarios reciban cualquier tipo de correo electrónico de {% data variables.product.product_name %} después de la configuración inicial, debes pedir a {% data variables.contact.github_support %} que configure la compatibilidad con el correo electrónico externo con tu servidor de SMTP. Para obtener más información, consulta la sección "[Configurar las notificaciones de correo electrónico](/admin/configuration/configuring-email-for-notifications)".
+{% data variables.product.product_name %} esté listo para utilizarse. La configuración inicial incluye la conexión de tu empresa con un proveedor de identidad (IdP), autenticarte con el SSO de SAML, configurar políticas para repositorios y organizaciones en tu empresa y configurar el SMTP para el correo electrónico externo. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
 
 Posteriormente, puedes utilizar el panel de administrador de sitio y la configuración empresarial para seguir configurando tu empresa, administrar usuarios, organizaciones y repositorios, y para configurar políticas que reducen los riesgos e incrementan la calidad.
 
diff --git a/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index 206dbaf92c..0e2ba4f3fe 100644
--- a/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/es-ES/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### Acerca del acceso al shell administrativo
diff --git a/translations/es-ES/content/admin/configuration/accessing-the-management-console.md b/translations/es-ES/content/admin/configuration/accessing-the-management-console.md
index a1faf82842..c4d4166c04 100644
--- a/translations/es-ES/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/es-ES/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Acerca de {% data variables.enterprise.management_console %}
diff --git a/translations/es-ES/content/admin/configuration/command-line-utilities.md b/translations/es-ES/content/admin/configuration/command-line-utilities.md
index 61926e935f..d2749e76ab 100644
--- a/translations/es-ES/content/admin/configuration/command-line-utilities.md
+++ b/translations/es-ES/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 Puedes ejecutar estos comandos desde cualquier lugar en la VM después de iniciar sesión como usuario administrador de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
@@ -483,15 +485,21 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 Para mostrar todos los resultados, carga útil y excepciones del gancho para la entrega:
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### Agrupación
 
 #### estado ghe-dpages
 
-Esta utilidad le permite gestionar el servidor {% data variables.product.prodname_pages %} distribuido.
+Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
 
 ```shell
 $ ghe-cluster-status
@@ -644,14 +652,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-Esta utilidad importa desde el Control de Versiones de Team Foundation. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+This utility imports from Team Foundation Version Control (TFVC). Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-Esta utilidad reescribe el repositorio importado. Esto te permite renombrar a los autores y, en el caso de TFS y Subversion, produce ramas de Git basadas en carpetas. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+Esta utilidad reescribe el repositorio importado. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-rewrite
 ```
diff --git a/translations/es-ES/content/admin/configuration/configuring-a-hostname.md b/translations/es-ES/content/admin/configuration/configuring-a-hostname.md
index 582474afa8..b4f745c4a1 100644
--- a/translations/es-ES/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/es-ES/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 Si configuras un nombre del host en lugar de una dirección IP codificada de forma rígida, podrás cambiar el hardware físico que ejecuta {% data variables.product.product_location %} sin afectar a los usuarios o al software del cliente.
diff --git a/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 5a369d3395..cb66e3fda3 100644
--- a/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/es-ES/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Cuando se habilita un servidor proxy para {% data variables.product.product_location %}, primero {% data variables.product.prodname_ghe_server %} envía mensajes fuera de banda a través del servidor proxy, a menos que el host de destino se agregue como una exclusión de servidor proxy HTTP. Los tipos de mensajes fuera de banda incluyen webhooks salientes, carga de paquetes y extracción de avatares heredados. La URL del servidor proxy es el protocolo, dominio o dirección IP más el número de puerto, por ejemplo `http://127.0.0.1:8123`.
diff --git a/translations/es-ES/content/admin/configuration/configuring-applications.md b/translations/es-ES/content/admin/configuration/configuring-applications.md
index 524ac0d948..797396fb28 100644
--- a/translations/es-ES/content/admin/configuration/configuring-applications.md
+++ b/translations/es-ES/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Ajustar el almacenamiento en caché de las imágenes
diff --git a/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md
index 0fbca7ea5e..011fd90158 100644
--- a/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/es-ES/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: Configurar copias de seguridad en tu aparato
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: 'Como parte de un plan de recuperación ante desastres, puedes proteger los datos de producción en {% data variables.product.product_location %} configurando copias de seguridad automáticas.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### Acerca de {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md
index 65285cca82..53b5e7c60a 100644
--- a/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/es-ES/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Acerca del firewell de {% data variables.product.product_location %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index 4a3aae824e..d262c057ff 100644
--- a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: Configurar el cifrado de datos
 intro: 'Para el cifrado estático, puedes proporcionar tu propia llave de cifrado para cifrar tus datos bajo tus políticas de cifrado.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 Para proporcionar un nivel alto de seguridad, {% data variables.product.product_name %} cifra tus datos mientras están estáticos en los centros de datos y mientras tus datos se encuentran en tránsito entre las máquinas de los usuarios y los centros de datos.
 
-Para el cifrado en tránsito, {% data variables.product.product_name %} utiliza la Seguridad de Capas de Transporte (TLS). Para el cifrado estático, {% data variables.product.product_name %} proporciona una llave RSA predeterminada. Después de que hayas inicializado tu empresa, puedes elegir mejor proporcionar tu propia llave. Tu llave debe ser una llave privada de RSA de 2048 bits en formato PEM.
-
-La clave que proporcionas se almacena en un módulo de seguridad de hardware (HSM) que cumple con el FIPS 140-2 en una bóveda de llaves que administra {% data variables.product.company_short %}.
-
-Para configurar tu llave de cifrado, utiliza la API de REST. Hay muchas terminales de la API, por ejemplo, para verificar el estado del cifrado, actualizar tu llave de cifrado, e inhabilitar tu llave de cifrado. Toma en cuenta que el inhabilitar tu llave ocasionará que tu empresa se congele. Para obtener más información acerca de las terminales de la API, consulta la sección "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST.
-
-### Agregar o actualizar una llave de cifrado
-
-Puedes agregar una llave de cifrado nueva tan frecuentemente como lo necesites. Cuando agregas una llave nueva, la llave anterior se descarta. Tu empresa no tendrá ningún tiempo de inactividad cuando actualices la llave.
-
-Tu llave privada de RSA de 2048 bits deberá estar en formato PEM, por ejemplo, en un archivo que se llama _private-key.pem_.
-
-   ```
-   -----BEGIN RSA PRIVATE KEY-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----END RSA PRIVATE KEY-----
-   ```
-
-1. Para agregar tu llave, utiliza la terminal `PATCH /enterprise/encryption`, reemplazando *~/private-key.pem* con la ruta a tu llave privada.
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. Opcionalmente, verifica el estado de la operación de actualización.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### Inhabilitar tu llave de cifrado
-
-Para congelar tu empresa, por ejemplo, en caso de una irrupción, puedes inhabilitar el cifrado estático si marcas tu llave de cifrado como inhabilitada.
-
-1. Para inhabilitar tu llave y cifrado estáticos, utiliza la terminal `DELETE /enterprise/encryption`. Esta operación no borra la llave permanentemente.
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. Opcionalmente, verifica el estado de la operación de borrado. Toma aproximadamente diez minutos el inhabilitar el cifrado estático.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-Para descongelar tu empresa después de que inhabilitaste tu llave de cifrado, contacta a soporte. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)".
-
-### Leer más
-
-- "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST 
+Para el cifrado en tránsito, {% data variables.product.product_name %} utiliza la Seguridad de Capas de Transporte (TLS). Para el cifrado estático, {% data variables.product.product_name %} proporciona una llave RSA predeterminada. 
diff --git a/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md b/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md
index dfc9a8e048..16c91f82d7 100644
--- a/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/es-ES/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Los servidores de nombres que especifiques deben resolver el nombre del host de {% data variables.product.product_location %}.
diff --git a/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md b/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md
index 839f7a1094..2e9a8a5343 100644
--- a/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/es-ES/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index 394d153193..04e9e9c70d 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### Habilitar los sitios públicos para {% data variables.product.prodname_pages %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-rate-limits.md b/translations/es-ES/content/admin/configuration/configuring-rate-limits.md
index a54f2ac4f3..cbd1aa68e6 100644
--- a/translations/es-ES/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/es-ES/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### Habilitar límites de tasa para {% data variables.product.prodname_enterprise_api %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index 285301a274..b2714cd745 100644
--- a/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/es-ES/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md b/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md
index e98d695131..f50e716d13 100644
--- a/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/es-ES/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Cambiar los servidores NTP predeterminados
diff --git a/translations/es-ES/content/admin/configuration/configuring-tls.md b/translations/es-ES/content/admin/configuration/configuring-tls.md
index 785944d01d..4de49394d9 100644
--- a/translations/es-ES/content/admin/configuration/configuring-tls.md
+++ b/translations/es-ES/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Acerca de la Seguridad de la capa de transporte
diff --git a/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 7b80b1c213..bea5235f9a 100644
--- a/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/es-ES/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### Acerca de {% data variables.product.prodname_github_connect %}
diff --git a/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index da27ab28b7..aae33c62c6 100644
--- a/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### Acerca de las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index e421b7d37f..1cabc7909f 100644
--- a/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/es-ES/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### Acerca del modo de mantenimiento
diff --git a/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 952bbd346a..48fb6dafd5 100644
--- a/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/es-ES/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### Acerca de la sincronización de licencias
diff --git a/translations/es-ES/content/admin/configuration/enabling-private-mode.md b/translations/es-ES/content/admin/configuration/enabling-private-mode.md
index 09febe63dc..0cc49f126c 100644
--- a/translations/es-ES/content/admin/configuration/enabling-private-mode.md
+++ b/translations/es-ES/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 Debes habilitar el modo privado si {% data variables.product.product_location %} es de acceso público por internet. En el modo privado, los usuarios no pueden clonar repositorios en forma anónima por `git://`. Si también está habilitada la autenticación incorporada, un administrador debe invitar a los nuevos usuarios para que creen una cuenta en la instancia. Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)."
diff --git a/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md b/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md
index 5620f1b4eb..f7504169d3 100644
--- a/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/es-ES/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Acerca del aislamiento de subdominio
@@ -19,7 +24,7 @@ Cuando el aislamiento de subdominio está habilitado, {% data variables.product.
 
 {% if currentVersion == "enterprise-server@2.22" %}
 Para utilizar docker con
-el {% data variables.product.prodname_registry %}, también debes habilitar el aislamiento de subdominios. Para obtener más información, consulta la sección "[Configurar Docker para utilizarlo con {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)".
+el {% data variables.product.prodname_registry %}, también debes habilitar el aislamiento de subdominios. For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index 158f158dc1..daf97cdb54 100644
--- a/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/es-ES/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 Como un administrador del sitio, puedes habilitar a los usuarios finales para que envíen sus recuentos de contribuciones de manera anónima por sus trabajos desde {% data variables.product.prodname_ghe_server %} a sus gráficos de contribuciones {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 030daf3928..38afacc31e 100644
--- a/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/es-ES/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 Cuando habilitas la búsqueda unificada, los usuarios pueden ver los resultados de la búsqueda desde contenido público y privado en {% data variables.product.prodname_dotcom_the_website %} cuando buscan desde {% data variables.product.product_location_enterprise %}.
diff --git a/translations/es-ES/content/admin/configuration/index.md b/translations/es-ES/content/admin/configuration/index.md
index d0f61c54fa..e8a0da14c4 100644
--- a/translations/es-ES/content/admin/configuration/index.md
+++ b/translations/es-ES/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/es-ES/content/admin/configuration/initializing-github-ae.md b/translations/es-ES/content/admin/configuration/initializing-github-ae.md
index c80d3a702e..7b411db919 100644
--- a/translations/es-ES/content/admin/configuration/initializing-github-ae.md
+++ b/translations/es-ES/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: Inicializar GitHub AE
 intro: 'Para poner a tu empresa lista para operar, puedes completar la configuración inicial de {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### Acerca de la inicialización
@@ -79,11 +82,11 @@ Una vez que se inicialice, puedes reconfigurar cualquier ajuste después del pro
 1. A la derecha de "Configurar ajustes de correo electrónico", haz clic en **Configurar**. ![Botón de "Configurar" para la configuración de ajustes de correo electrónico](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. Selecciona **Activar correo electrónico**. Esto habilitará el correo electrónico tanto entrante como saliente, sin embargo, para que funcione el entrante, también necesitarás configurar tus ajustes de DNS. Para obtener más información, consulta la sección "[Configurar los ajustes de DNS y cortafuegos para permitir los correos electrónicos entrantes](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". ![Casilla de "Habilitar" para la configuración de ajustes de correo electrónico](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Completa tus ajustes de servidor de correo electrónico:
-  - En el campo **Dirección del servidor**, escribe la dirección de tu servidor SMTP.
-  - En el campo **Puerto**, escribe el puerto que usa tu servidor SMTP para enviar correo electrónico.
-  - En el campo **Dominio**, escribe el nombre de dominio que enviará tu servidor SMTP con una respuesta HELO, de ser el caso.
-  - En el desplegable **Autenticación**, elige el tipo de cifrado usado por tu servidor SMTP.
-  - En el campo **Dirección de correo electrónico sin respuesta**, escribe la dirección de correo electrónico para usar en los campos De y Para para todos los correos electrónicos para notificaciones.
+    - En el campo **Dirección del servidor**, escribe la dirección de tu servidor SMTP.
+    - En el campo **Puerto**, escribe el puerto que usa tu servidor SMTP para enviar correo electrónico.
+    - En el campo **Dominio**, escribe el nombre de dominio que enviará tu servidor SMTP con una respuesta HELO, de ser el caso.
+    - En el desplegable **Autenticación**, elige el tipo de cifrado usado por tu servidor SMTP.
+    - En el campo **Dirección de correo electrónico sin respuesta**, escribe la dirección de correo electrónico para usar en los campos De y Para para todos los correos electrónicos para notificaciones.
 
 4. Si quieres descartar todos los correos electrónicos entrantes que estén dirigidos al correo electrónico sin respuesta, selecciona **Descartar correo electrónico dirigido a la dirección de correo electrónico sin respuesta**. ![Casilla de "Descartar" para la configuración de ajustes de correo electrónico](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. Haz clic en **Probar la configuración de correo electrónico**. ![Botón de "Probar la configuración de correo electrónico" para la configuración de ajustes de correo electrónico](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 1d770d3162..3af7a90967 100644
--- a/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: 'Puedes decidir si los usuarios autenticados pueden conectarse a {% data
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/es-ES/content/admin/configuration/network-ports.md b/translations/es-ES/content/admin/configuration/network-ports.md
index 59b9481829..66b4179dec 100644
--- a/translations/es-ES/content/admin/configuration/network-ports.md
+++ b/translations/es-ES/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Abre los puertos de red de forma selectiva en base a los servicios de red que necesitas exponer a los administradores, usuarios finales y apoyo de correo electrónico.'
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Puertos administrativos
diff --git a/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index bebe28586e..ef43b1e700 100644
--- a/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -4,6 +4,13 @@ shortTitle: Restringir el tráfico de red
 intro: Puedes utilizar una lista de IP permitidas para restringir el acceso de conexiones de IP específicas a tu empresa.
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### Acerca de las listas de IP permitidas
diff --git a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md
index 3165fef75d..d7d957e805 100644
--- a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md
@@ -1,5 +1,5 @@
 ---
-title: Site admin dashboard
+title: Tablero de administración del sitio
 intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}'
 redirect_from:
   - /enterprise/admin/articles/site-admin-dashboard/
@@ -7,201 +7,202 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
-To access the dashboard, in the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}.
-![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
+Para acceder al tablero, en la esquina superior derecha de cualquier página, haz clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Icono de cohete para acceder a la configuración de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}
 
-### Search
+### Buscar
 
-Refer to this section of the site admin dashboard to search for users and repositories, and to query the [audit log](#audit-log).
+Aquí puedes iniciar la {{ site.data.variables.enterprise.management_console }} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL.
 
 {% else %}
 
-### License info & search
+### Información de la licencia & buscar
 
-Refer to this section of the site admin dashboard to check your current {% data variables.product.prodname_enterprise %} license; to search for users and repositories; and to query the [audit log](#audit-log).
+Consulta esta sección del tablero de administración del sitio para controlar tu licencia {% data variables.product.prodname_enterprise %} actual, para buscar usuarios y repositorios y para consultar el [registro de auditoría](#audit-log).
 
 {% endif %}
 
 ### {% data variables.enterprise.management_console %}
 
-Here you can launch the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL.
+Aquí puedes iniciar la {% data variables.enterprise.management_console %} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL.
 
-### Explore
+### Explorar
 
-Data for GitHub's [trending page][] is calculated into daily, weekly, and monthly time spans for both repositories and developers. You can see when this data was last cached and queue up new trending calculation jobs from the **Explore** section.
+Los datos para la [página de tendencia][] de GitHub se calculan en lapsos de tiempo diarios, semanales y mensuales para ambos repositorios y programadores. Puedes ver cuándo estos datos fueron almacenados en caché por última vez y poner en cola las tareas nuevas de cálculo de tendencia desde la sección **Explore (Explorar)**.
 
-  [trending page]: https://github.com/blog/1585-explore-what-is-trending-on-github
+### Registro de auditoría
 
-### Audit log
+{% data variables.product.prodname_enterprise %} mantiene un registro continuo de las acciones auditadas que puedes consultar.
 
-{% data variables.product.prodname_enterprise %} keeps a running log of audited actions that you can query.
+Por defecto, el registro de auditoría te muestra una lista de todas las acciones auditadas en orden cronológico reverso. Puedes filtrar esta lista al ingresar pares de valores clave en el casillero de texto de **Query (Consulta)** y después hacer clic en **Search (Buscar)**, como se explicó en "[Buscar el registro de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)."
 
-By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)."
+Para obtener más información acerca de las bitácoras de auditoria en general, consulta "[Bitácoras de Auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". Para encontrar una lista completa de las acciones auditadas, consulta la sección "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)".
 
-For more information on audit logging in general, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." For a full list of audited actions, see "[Audited actions](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)."
+### Informes
 
-### Reports
+Si necesitas obtener información sobre los usuarios, organizaciones y repositorios en {% data variables.product.product_location %}, comúnmente extraerías datos JSON a través de la [API de GitHub](/rest). Lamentablemente, es posible que la API no proporcione todos los datos que deseas y se requiera algo de conocimiento técnico para usarla. Este tablero de administración del sitio ofrece una sección de **Reports (Informes)** como una alternativa, haciendo que sea fácil descargar informes CSV con la mayoría de la información que probablemente necesites para los usuarios, las organizaciones y los repositorios.
 
-If you need to get information on the users, organizations, and repositories in {% data variables.product.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories.
+Específicamente, puedes descargar informes CSV que enumeren a
 
-Specifically, you can download CSV reports that list
+- todos los usuarios
+- todos los usuarios que han estado activos dentro del último mes
+- todos los usuarios que han estado inactivos durante un mes o más
+- todos los usuarios que han sido suspendidos
+- todas las organizaciones
+- todos los repositorios
 
-- all users
-- all users who have been active within the last month
-- all users who have been inactive for one month or more
-- all users who have been suspended
-- all organizations
-- all repositories
+También puedes acceder a estos informes mediante programación a través de una autenticación estándar de HTTP con una cuenta de administrador del sitio. Debes utilizar un token de acceso personal con alcance de `site_admin`. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
 
-You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a personal access token with the `site_admin` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-
-For example, here is how you would download the "all users" report using cURL:
+Por ejemplo, así es como descargarías el informe "todos los usuarios" utilizando cURL:
 
 ```shell
 curl -L -u <em>username</em>:<em>token</em> http(s)://<em>hostname</em>/stafftools/reports/all_users.csv
 ```
 
-To access the other reports programmatically, replace `all_users` with `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, or `all_repositories`.
+Para acceder a otros informes mediante programación, reemplaza `all_users` con `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, o `all_repositories`.
 
 {% note %}
 
-**Note:** The initial `curl` request will return a 202 HTTP response if there are no cached reports available; a report will be generated in the background. You can send a second request to download the report. You can use a password or an OAuth token with the `site_admin` scope in place of a password.
+**Nota:** La solicitud `curl` inicial devolverá una respuesta 202 HTTP si no hay informes en caché disponibles; se generará un informe en segundo plano. Puedes enviar una segunda solicitud para descargar el informe. Puedes utilizar una contraseña o un token de OAuth con el alcance `site_admin` en lugar de la contraseña.
 
 {% endnote %}
 
-#### User reports
+#### Informes del usuario
 
-Key               | Description
------------------:| ------------------------------------------------------------
-`created_at`      | When the user account was created (as an ISO 8601 timestamp)
-`id`              | Account ID for the user or organization
-`login`           | Account's login name
-`email`           | Account's primary email address
-`role`            | Whether the account is an admin or an ordinary user
-`suspended?`      | Whether the account has been suspended
-`last_logged_ip`  | Most recent IP address to log into the account
-`repos`           | Number of repositories owned by the account
-`ssh_keys`        | Number of SSH keys registered to the account
-`org_memberships` | Number of organizations to which the account belongs
-`dormant?`        | Whether the account is dormant
-`last_active`     | When the account was last active (as an ISO 8601 timestamp)
-`raw_login`       | Raw login information (in JSON format)
-`2fa_enabled?`    | Whether the user has enabled two-factor authentication
+|                    Clave | Descripción                                                                       |
+| ------------------------:| --------------------------------------------------------------------------------- |
+| `created_at (creado en)` | Cuándo fue creada la cuenta de usuario (como una marca de tiempo ISO 8601)        |
+|                     `id` | ID de la cuenta para el usuario o la organización                                 |
+|                  `login` | Nombre de inicio de sesión de la cuenta                                           |
+|     `correo electrónico` | Dirección principal de correo electrónico de la cuenta                            |
+|                    `rol` | Si la cuenta es de un usuario administrador o de un usuario común                 |
+|             `suspended?` | Si la cuenta ha sido suspendida                                                   |
+|         `last_logged_ip` | La dirección IP más reciente que se registró en la cuenta                         |
+|                  `repos` | Cantidad de repositorios que posee la cuenta                                      |
+|               `ssh_keys` | Cantidad de claves SSH registradas en la cuenta                                   |
+|        `org_memberships` | Cantidad de organizaciones a las que pertenece la cuenta                          |
+|               `dormant?` | Si la cuenta está inactiva                                                        |
+|            `last_active` | Cuándo la cuenta estuvo activa por última vez (como una marca de tiempo ISO 8601) |
+|              `raw_login` | Información de inicio de sesión sin procesar (en formato JSON)                    |
+|           `2fa_enabled?` | Si el usuario ha habilitado autenticación de dos factores                         |
 
-#### Organization reports
+#### Informes de la organización
 
-Key            | Description
---------------:| ------------------------------------
-`id`           | Organization ID
-`created_at`   | When the organization was created
-`login`        | Organization's login name
-`email`        | Organization's primary email address
-`owners`       | Number of organization owners
-`members`      | Number of organization members
-`teams`        | Number of organization teams
-`repos`        | Number of organization repositories
-`2fa_required?`| Whether the organization requires two-factor authentication
+|                    Clave | Descripción                                                  |
+| ------------------------:| ------------------------------------------------------------ |
+|                     `id` | ID de la organización                                        |
+| `created_at (creado en)` | Cuándo se creó la organización                               |
+|                  `login` | Nombre de inicio de sesión de la organización                |
+|     `correo electrónico` | Dirección principal de correo electrónico de la organización |
+|                 `owners` | Cantidad de propietarios de la organización                  |
+|                `members` | Cantidad de miembros de la organización                      |
+|                `equipos` | Cantidad de equipos de la organización                       |
+|                  `repos` | Cantidad de repositorios de la organización                  |
+|          `2fa_required?` | Si la organización requiere autenticación de dos factores    |
 
-#### Repository reports
+#### Informes del repositorio
 
-Key             | Description
----------------:| ------------------------------------------------------------
-`created_at`    | When the repository was created
-`owner_id`      | ID of the repository's owner
-`owner_type`    | Whether the repository is owned by a user or an organization
-`owner_name`    | Name of the repository's owner
-`id`            | Repository ID
-`name`          | Repository name
-`visibility`    | Whether the repository is public or private
-`readable_size` | Repository's size in a human-readable format
-`raw_size`      | Repository's size as a number
-`collaborators` | Number of repository collaborators
-`fork?`         | Whether the repository is a fork
-`deleted?`      | Whether the repository has been deleted
+|                    Clave | Descripción                                                        |
+| ------------------------:| ------------------------------------------------------------------ |
+| `created_at (creado en)` | Cuándo fue creado el repositorio                                   |
+|               `owner_id` | ID del propietario del repositorio                                 |
+|             `owner_type` | Si el repositorio es propiedad de un usuario o de una organización |
+|             `owner_name` | Nombre del propietario del repositorio                             |
+|                     `id` | ID del repositorio                                                 |
+|          `name (nombre)` | Nombre del repositorio                                             |
+|            `visibilidad` | Si el repositorio es público o privado                             |
+|          `readable_size` | El tamaño del repositorio en un formato legible                    |
+|               `raw_size` | Tamaño del repositorio como un número                              |
+|          `collaborators` | Cantidad de colaboradores del repositorio                          |
+|                  `fork?` | Si el repositorio es una bifurcación                               |
+|               `deleted?` | Si el repositorio ha sido borrado                                  |
 
-### Indexing
+### Indexar
 
-GitHub's [code search][] features are powered by [ElasticSearch][]. This section of the site admin dashboard shows you the current status of your ElasticSearch cluster and provides you with several tools to control the behavior of searching and indexing. These tools are split into the following three categories.
+Las funciones de [búsqueda de código][] de GitHub son propulsadas por [ElasticSearch][]. Esta sección del tablero de administración del sitio muestra el estado actual de tu agrupación de ElasticSearch y brinda diversas herramientas para controlar el comportamiento de búsqueda e indexación. Estas herramientas están separadas en las siguientes tres categorías.
 
-  [Code Search]: https://github.com/blog/1381-a-whole-new-code-search
-  [ElasticSearch]: http://www.elasticsearch.org/
+#### Búsqueda de código
 
-#### Code search
+Esto te permite habilitar o deshabilitar tanto las operaciones de búsqueda como de indexación en el código fuente.
 
-This allows you to enable or disable both search and index operations on source code.
+#### Reparación del índice de búsqueda de código
 
-#### Code search index repair
+Esto controla cómo se repara el índice de búsqueda de código. Puedes
 
-This controls how the code search index is repaired. You can
+- habilitar o inhabilitar tareas de reparación de índices
+- comenzar una nueva tarea de reparación de índice
+- restablecer todos los estados de reparación de índices
 
-- enable or disable index repair jobs
-- start a new index repair job
-- reset all index repair state
+{% data variables.product.prodname_enterprise %} utiliza tareas de reparación para compaginar el estado del índice de búsqueda con los datos almacenados en una base de datos (propuestas, solicitudes de extracción, repositorios y usuarios) y los datos almacenados en los repositorios de Git (código fuente). Esto sucede cuando
 
-{% data variables.product.prodname_enterprise %} uses repair jobs to reconcile the state of the search index with data stored in a database (issues, pull requests, repositories, and users) and data stored in Git repositories (source code). This happens when
+- se crea un nuevo índice de búsqueda;
+- faltan datos que se deben reponer; o
+- los datos de búsqueda antiguos deben ser actualizados.
 
-- a new search index is created;
-- missing data needs to be backfilled; or
-- old search data needs to be updated.
+En otras palabras, las tareas de reparación se inician según se necesiten y se ejecutan en segundo plano, no están programados por los administradores del sitio de ningún modo.
 
-In other words, repair jobs are started as needed and run in the background—they are not scheduled by site admins in any way.
+Además, las tareas de reparación utilizan una "compensación de reparación" para la paralelización. Esto es una compensación dentro de la tabla de base de datos para el registro que se está compaginando. Múltiples tareas en segundo plano pueden sincronizar el trabajo en base a esta compensación.
 
-Furthermore, repair jobs use a "repair offset" for parallelization. This is an offset into the database table for the record being reconciled. Multiple background jobs can synchronize work based on this offset.
+Una barra de progreso muestra el estado actual de la tarea de reparación a través de todos sus trabajadores en segundo plano. Es la diferencia de porcentaje de la compensación de reparación con el ID de registro más alto en la base de datos. No te preocupes sobre el valor que se muestra en la barra de progreso después de que una tarea de reparación se haya completado: ya que muestra la diferencia entre la compensación de reparación y el ID del registro más alto en la base de datos, disminuirá a medida que se agreguen más repositorios a {% data variables.product.product_location %} incluso aquellos repositorios que están de hecho indexados.
 
-A progress bar shows the current status of a repair job across all of its background workers. It is the percentage difference of the repair offset with the highest record ID in the database. Don't worry about the value shown in the progress bar after a repair job has completed: because it shows the difference between the repair offset and the highest record ID in the database, it will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed.
+Puedes comenzar una nueva tarea de reparación de índice de búsqueda de código en cualquier momento. Utilizará una CPU única ya que compagina el índice de búsqueda con la base de datos y los datos del repositorio de Git. Para minimizar los efectos que esto tendrá en el desempeño de I/O y reducir las posibilidades de que las operaciones queden inactivas, trata de ejecutar una tarea de reparación durante las horas valle en primer lugar. Controla las cargas promedio de tu sistema y el uso de tu CPU con una herramienta como `top`; si no notas cambios significativos, debería ser seguro ejecutar una tarea de reparación de índice también durante las horas pico.
 
-You can start a new code-search index repair job at any time. It will use a single CPU as it reconciles the search index with database and Git repository data. To minimize the effects this will have on I/O performance and reduce the chances of operations timing out, try to run a repair job during off-peak hours first. Monitor your system's load averages and CPU usage with a utility like `top`; if you don't notice any significant changes, it should be safe to run an index repair job during peak hours, as well.
+#### Reparación de índice de propuestas
 
-#### Issues index repair
+Esto controla de qué manera se repara el [índice de propuestas][]. Puedes
 
-This controls how the [Issues][] index is repaired. You can
-
-  [Issues]: https://github.com/blog/831-issues-2-0-the-next-generation
-
-- enable or disable index repair jobs
-- start a new index repair job
-- reset all index repair state
+- habilitar o inhabilitar tareas de reparación de índices
+- comenzar una nueva tarea de reparación de índice
+- restablecer todos los estados de reparación de índices
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}
 
-### Enterprise overview
+### Todos los usuarios
 
-Refer to this section of the site admin dashboard to manage organizations, people, policies, and settings.
+Aquí puedes ver todos los usuarios que han sido suspendidos en {{ site.data.variables.product.product_location_enterprise }}, e [iniciar una auditoría clave de SSH](/enterprise/{{ page.version }}/admin/guides/user-management/auditing-ssh-keys).
 
 {% endif %}
 
-### Repositories
+### Repositorios
 
-This is a list of the repositories on {% data variables.product.product_location %}. You can click on a repository name and access functions for administering the repository.
+Es una lista de los repositorios en {% data variables.product.product_location %}. Puedes hacer clic en un nombre de repositorio y acceder a las funciones para administrar el repositorio.
 
-- [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)
-- [Configuring {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository)
-- [Archiving and unarchiving repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/)
+- [Bloquear empujes forzados en un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)
+- [Configurar {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository)
+- [Archivar y desarchivar repositorios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/)
 
-### All users
+### Todos los usuarios
 
-Here you can see all of the users on {% data variables.product.product_location %}—, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys).
+Aquí puedes ver todos los usuarios en {% data variables.product.product_location %}—, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys).
 
-### Site admins
+### Administrador del sitio
 
-Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys).
+Aquí puedes ver todos los administradores en {% data variables.product.product_location %}, e [iniciar una auditoría clave en SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys).
 
-### Dormant users
+### Usuarios inactivos
 
-Here you can see and [suspend](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it:
+Aquí puedes ver y [suspender](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) todos los usuarios inactivos en {% data variables.product.product_location %}. Una cuenta de usuario se considera inactiva ("dormant") cuando:
 
-- Has existed for longer than the dormancy threshold that's set for {% data variables.product.product_location %}.
-- Has not generated any activity within that time period.
-- Is not a site administrator.
+- Ha existido durante más tiempo del umbral de inactividad que está establecido para {% data variables.product.product_location %}.
+- No ha generado ninguna actividad dentro de ese período.
+- No es un administrador del sitio.
 
-{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} For more information, see "[Managing dormant users](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)."
+{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} Para obtener más información, consulta "[Administrar usuarios inactivos](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)."
 
-### Suspended users
+### Usuarios suspendidos
 
-Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys).
+Aquí puedes ver todos los usuarios que han sido suspendidos en {% data variables.product.product_location %}, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys).
+
+  [página de tendencia]: https://github.com/blog/1585-explore-what-is-trending-on-github
+
+  [búsqueda de código]: https://github.com/blog/1381-a-whole-new-code-search
+  [ElasticSearch]: http://www.elasticsearch.org/
+
+  [índice de propuestas]: https://github.com/blog/831-issues-2-0-the-next-generation
diff --git a/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md
index ba04cf349a..d388082095 100644
--- a/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/es-ES/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### Eliminar la contraseña de un archivo clave
diff --git a/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index ae4cb8aad9..6f5592320d 100644
--- a/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/es-ES/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md b/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md
index 52390efd0d..91fcd2ea0e 100644
--- a/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/es-ES/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/es-ES/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/es-ES/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md b/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md
index 1f38bceb94..90e9a4abe4 100644
--- a/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/es-ES/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/enterprise-management/about-clustering.md b/translations/es-ES/content/admin/enterprise-management/about-clustering.md
index 84d2f70557..d7d85b6b2c 100644
--- a/translations/es-ES/content/admin/enterprise-management/about-clustering.md
+++ b/translations/es-ES/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md b/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md
index 36387868d5..712da3b254 100644
--- a/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/es-ES/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 Contar con múltiples réplicas puede permitir una menor distancia a la réplica más cercana. Por ejemplo, una organización con oficinas en San Francisco, Nueva York y Londres podrían ejecutar el aparato principal en un centro de datos cercano a Nueva York y dos réplicas en centros de datos cercanos a San Francisco y Londres. Al usar DNS con información de geolocalización, se puede dirigir a los usuarios al servidor disponible más cercano para que accedan a los datos más rápido. Designar como principal el aparato cercano a Nueva York ayuda a reducir la latencia entre los hosts, a diferencia de si se designa como principal el aparato cercano a San Francisco, que tiene mayor latencia con Londres.
diff --git a/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md
index d2547612b8..927d10e613 100644
--- a/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/es-ES/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Cuando configuras la alta disponibilidad, hay una configuración automática unidireccional, una replicación asincrónica de todos los almacenes de datos (repositorios de Git, MySQL, Redis y Elasticsearch) desde el aparato principal hacia la réplica.
diff --git a/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 783243a9eb..8bd33ae51b 100644
--- a/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/es-ES/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Acceder al tablero del monitor
diff --git a/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md b/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md
index 2d3244abd3..3f16404420 100644
--- a/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/es-ES/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### Consideraciones de red
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md b/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md
index e4ed21302a..023c56ccee 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Configura un servidor `collectd` externo
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index 67a927f590..4a98328da5 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Acerca de la replicación de disponibilidad alta para clústers
@@ -22,7 +26,7 @@ Te recomendamos configurar la disponibilidad alta como parte de un plan integral
 
 #### Hardware y software
 
-Para cada nodo existente en tu clúster activo, necesitarás aprovisionar una segunda máquina virtual con recursos de hardware idénticos. Por ejemplo, si tu clúster tiene 11 nodos y cada nodo tiene 12 vCPUs, 96 GB de RAM, y 750 GB de almacenamiento adjunto, deberás aprovisionar 11 máquinas virtuales en donde cada una tenga 12 vCPUs, 64 GB de RAM, y 750GB de almacenamiento adjunto.
+Para cada nodo existente en tu clúster activo, necesitarás aprovisionar una segunda máquina virtual con recursos de hardware idénticos. Por ejemplo, si tu clúster tiene 11 nodos y cada nodo tiene 12 vCPUs, 96 GB de RAM, y 750 GB de almacenamiento adjunto, deberás aprovisionar 11 máquinas virtuales en donde cada una tenga 12 vCPUs, 96 GB de RAM, y 750GB de almacenamiento adjunto.
 
 En cada máquina virtual, instala la misma versión de {% data variables.product.prodname_ghe_server %} que se ejecuta en los nodos en tu clúster activo. No necesitas cargar una licencia ni realizar alguna configuración adicional. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)."
 
diff --git a/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md
index 07abd4c88b..de90ee65c2 100644
--- a/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/es-ES/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index d953c16667..80678307b5 100644
--- a/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/es-ES/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Escenarios de fallas
diff --git a/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md
index c49da1706a..f006d25ab2 100644
--- a/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/es-ES/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 Cuando un paquete de actualizaciones se descarga automáticamente para {% data variables.product.product_location %}, recibirás un mensaje informándote que puedes actualizar el {% data variables.product.prodname_ghe_server %}. Descarga de paquetes para el directorio `/var/lib/ghe-updates` en {% data variables.product.product_location %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)."
diff --git a/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md
index 41d0f5fb96..cd490791c2 100644
--- a/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/es-ES/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index ba3e7da3b4..306ad5d93b 100644
--- a/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/es-ES/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md
index fc0fa750c5..95f173b14b 100644
--- a/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/es-ES/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -31,7 +35,10 @@ A medida que se suman usuarios {% data variables.product.product_location %}, es
 1. Ajusta el disco de volumen existente del usuario utilizando las herramientas de tu plataforma de virtualización.
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. Pon el aparato en modo mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
-4. Reinicia el aparato para detectar la nueva asignación de almacenamiento.
+4. Reinicia el aparato para detectar la nueva asignación de almacenamiento:
+  ```shell
+  $ sudo reboot
+  ```
 5. Ejecuta el comando `ghe-storage-extend` para expandir el sistema de archivos `/data/user`:
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ A medida que se suman usuarios {% data variables.product.product_location %}, es
 ### Aumentar el tamaño de partición raíz utilizando un nuevo aparato
 
 1. Configura una nueva instancia {% data variables.product.prodname_ghe_server %} con un disco raíz más grande utilizando la misma versión que tu aparato actual. Para obtener más información, consulta "[Configurar una instancia {% data variables.product.prodname_ghe_server %} ](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
-2. Cierra el aparato actual.
+2. Cierra el aparato actual:
+  ```shell
+  $ sudo poweroff
+  ```
 3. Desconecta el disco de datos de tu aparato actual utilizando las herramientas de tu plataforma de virtualización.
 4. Conecta el disco de datos al nuevo aparato con un disco raíz más grande.
 
@@ -57,6 +67,9 @@ A medida que se suman usuarios {% data variables.product.product_location %}, es
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. Cierra el aparato.
+4. Cierra el aparato:
+  ```shell
+  $ sudo poweroff
+  ```
 5. En el hipervisor, quita el disco raíz anterior y agrega el nuevo disco raíz en la misma ubicación del disco raíz anterior.
 6. Inicia el aparato.
diff --git a/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md b/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md
index 07a239c911..2ac5b56ac4 100644
--- a/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/es-ES/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 9ce9c3b9b1..1233665840 100644
--- a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para impulsar la réplica y redireccionar el tráfico de forma manual. El tiempo promedio varía entre 2 y 10 minutos.
diff --git a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index d14cfb4a04..55faa96d6e 100644
--- a/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/es-ES/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Acerca de la conmutación por error a tu clúster de réplica
diff --git a/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index b0e3506d1f..a8f2702a79 100644
--- a/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/es-ES/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -14,6 +14,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 Migrations from {% data variables.product.prodname_enterprise %} 11.10.348 and later are supported. Migrating from {% data variables.product.prodname_enterprise %} 11.10.348 and earlier is not supported. You must first upgrade to 11.10.348 in several upgrades. For more information, see the 11.10.348 upgrading procedure, "[Upgrading to the latest release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)."
diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md
index 02769a7d7e..0cd92e743e 100644
--- a/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/es-ES/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -6,8 +6,14 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Comprobación manual del estado de la agrupación
diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md
index 4d968fdbc2..2926a6908c 100644
--- a/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/es-ES/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP es una norma común para controlar dispositivos en una red. Recomendamos firmemente habilitar SNMP para que puedas controlar la salud de {% data variables.product.product_location %} y saber cuándo agregar más memoria, almacenamiento, o rendimiento del procesador a la máquina del servidor.
diff --git a/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md
index 719b93f4b0..ebd962db85 100644
--- a/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/es-ES/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### Controlar el almacenamiento
diff --git a/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index 5c359da3d7..224f3a8fdc 100644
--- a/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/es-ES/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -1,10 +1,33 @@
 ---
+title: Recuperar una configuración de disponibilidad alta
+intro: 'Después de la conmutación por error de un aparato {% data variables.product.prodname_ghe_server %}, debes recuperar redundancia tan pronto como sea posible en lugar de depender de un aparato único.'
 redirect_from:
   - /enterprise/admin/installation/recovering-a-high-availability-configuration
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
+Puedes utilizar el aparato principal antiguo como el nuevo aparato de réplica si la conmutación por error fue planeada o no estaba relacionada con la salud del aparato. Si la conmutación por error estaba relacionado con un problema con el aparato primario, es posible que prefieras crear un nuevo aparato de réplica. Para obtener más información, consulta "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)."
+
+### Configurar un aparato principal antiguo como una nueva réplica
+
+1. Conéctate a la dirección IP del aparato principal antiguo utilizando SSH.
+  ```shell
+  $ ssh -p 122 admin@<em>FORMER PRIMARY IP</em>
+  ```
+2. En el aparato principal antiguo, ejecuta el comando `ghe-repl-setup` con la dirección IP de la réplica antigua.
+  ```shell
+  $ ghe-repl-setup <em>FORMER REPLICA IP</em>
+  ```
+{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
+4. Para verificar la conexión con el aparato principal nuevo y habilitar el modo réplica para la nueva réplica, ejecuta nuevamente `ghe-repl-setup`.
+  ```shell
+  $ ghe-repl-setup <em>FORMER REPLICA IP</em>
+  ```
+{% data reusables.enterprise_installation.replication-command %}
diff --git a/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md
index 614e77227c..d63cf44cb7 100644
--- a/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/es-ES/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### Detener una replicación de forma temporal
diff --git a/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md
index 1327755f95..9fcf85fc2d 100644
--- a/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/es-ES/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md
index eaf489bf3b..ab9f86686b 100644
--- a/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/es-ES/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Acerca de SNMP
diff --git a/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md b/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md
index 19b9b82547..dcf97ec811 100644
--- a/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/es-ES/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 Utiliza el número para estimar la cantidad de espacio de disco que los registros de auditoría de MySQL necesitarán. El script también controla tu espacio libre en disco mientras la importación está en progreso. Controlar este número es especialmente útil si tu espacio libre en disco está cerca de la cantidad de espacio en disco necesaria para la migración.
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### Pasos siguientes
+
 Después de revisar estas recomendaciones y requisitos, puedes actualizar el {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)."
diff --git a/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md
index b63a76bef8..df2f35856a 100644
--- a/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/es-ES/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### Actualizar con un hotpatch
diff --git a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index 3f6e0a3069..4d43150487 100644
--- a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### Preparar para una actualización
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### Acerca de los requisitos mínimos para {% data variables.product.prodname_ghe_server %} 3.0 y superior
-
-Antes de actualizar a {% data variables.product.prodname_ghe_server %} 3.0 o superior, revisa los recursos de hardware que has aprovisionado para tu instancia. {% data variables.product.prodname_ghe_server %} 3.0 presenta características nuevas tales como {% data variables.product.prodname_actions %} y el {% data variables.product.prodname_registry %}, y requiere más recursos que la versión 2.22 y anteriores. Para obtener más información, consulta la sección de [notas de lanzamiento para {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes).
-
-Los requisitos que incrementan para {% data variables.product.prodname_ghe_server %} 3.0 y posterior se muestran en **negritas** en la siguiente tabla.
-
-| Licencias de usuario                     |                                     vCPU |                                          Memoria |                         Almacenamiento conectado | Almacenamiento raíz |
-|:---------------------------------------- | ----------------------------------------:| ------------------------------------------------:| ------------------------------------------------:| -------------------:|
-| Prueba, Demo o 10 usuarios no frecuentes |   **4**<br/>_Aumentando desde 2_ |   **32 GB**<br/>_Aumentando desde 16 GB_ | **150 GB**<br/>_Aumentando desde 100 GB_ |              200 GB |
-| 10-3000                                  |   **8**<br/>_Aumentando desde 4_ |   **48 GB**<br/>_Aumentando desde 32 GB_ | **300 GB**<br/>_Aumentando desde 250 GB_ |              200 GB |
-| 3000-5000                                |  **12**<br/>_Aumentando desde 8_ |                                            64 GB |                                           500 GB |              200 GB |
-| 5000-8000                                | **16**<br/>_Aumentando desde 12_ |                                            96 GB |                                           750 GB |              200 GB |
-| 8000-10000+                              | **20**<br/>_Aumentando desde 16_ | **160 GB**<br/>_Aumentando desde 128 GB_ |                                          1000 GB |              200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-Para obtener más información acerca de los requisitos de hardware para las {% data variables.product.prodname_actions %}, consulta la sección "[Comenzar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### Tomar una instantánea
 
@@ -81,7 +59,7 @@ Hay dos tipos de instantáneas:
 | Hyper-V               | VM                    | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | Disco                 | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM                    | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM                    | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM                    | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### Actualizar con un hotpatch
 
@@ -89,7 +67,12 @@ Hay dos tipos de instantáneas:
 
 {% note %}
 
-**Note**: instalar un hotpatch utilizando la {% data variables.enterprise.management_console %} no está disponible en los entornos de agrupación. Para instalar un parche en un entorno de agrupación, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}Notas{% else %}Nota{% endif %}**:
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- Si {% data variables.product.product_location %} está ejecutando una compilación candidata a lanzamiento, no puedes actualizarla con un hotpatch.
+
+- {% endif %}No hay disponibilidad para instalar un parche utilizando la {% data variables.enterprise.management_console %} en los ambientes de clúster. Para instalar un parche en un entorno de agrupación, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md
index e20e8bf6aa..90dc282abe 100644
--- a/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/es-ES/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index 70edbdab80..981cb1fb10 100644
--- a/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index b1205c1302..860fa5208c 100644
--- a/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/es-ES/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md
index 76dae989af..955a0c3525 100644
--- a/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/es-ES/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index 52d37ad7b9..1937da75a5 100644
--- a/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/es-ES/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 Antes de enviar un ticket, deberías:
diff --git a/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md
index 40097d4d06..61ffab9d10 100644
--- a/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/es-ES/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Crear y compartir archivos de diagnóstico
diff --git a/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md b/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md
index b81bb5b318..7bd7449cd5 100644
--- a/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/es-ES/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Usar sistemas de tickets automatizado
diff --git a/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md b/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md
index 8a9b6a0ea7..63bbfa8677 100644
--- a/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/es-ES/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Acerca del envío de tickets
diff --git a/translations/es-ES/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/es-ES/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..0be0e9e2cd
--- /dev/null
+++ b/translations/es-ES/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: Acerca de utilizar las acciones en tu empresa
+intro: '{% data variables.product.product_name %} incluye la mayoría de las acciones de autoría de {% data variables.product.prodname_dotcom %}, y tiene opciones para habilitar el acceso a otras acciones de {% data variables.product.prodname_dotcom_the_website %} y de {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+Los flujos de trabajo de {% data variables.product.prodname_actions %} pueden utilizar _acciones_, las cuales son tareas individuales que puedes combinar para crear jobs y personalizar tu flujo de trabajo. Puedes crear tus propias acciones, o utilizar y personalizar a quellas que comparte la comunidad de {% data variables.product.prodname_dotcom %}.
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### Acciones oficiales que se incluyen en tu instancia empresarial
+
+La mayoría de las acciones oficiales de autoría de {% data variables.product.prodname_dotcom %} se agrupan automáticamente con {% data variables.product.product_name %} y se capturan en un punto en el tiempo desde {% data variables.product.prodname_marketplace %}.
+
+Las acciones agrupadas oficiales incluyen a `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, y varias acciones de `actions/setup-`, entre otras. Para ver todas las acciones oficiales que se incluyen en tu instancia empresarial, navega hasta la organización `actions` en tu instancia: <code>https://<em>HOSTNAME</em>/actions</code>.
+
+Cada acción es un repositorio en la organización `actions` y cada repositorio de acción incluye las etiquetas, ramas y SHA de confirmación necesarios que tu flujo de trabajo puede utilizar para referenciar la acción. Para obtener más información sobre cómo actualizar las acciones oficiales empaquetadas, consulta la sección "[Utilizar la versión más reciente de las acciones oficiales incluídas](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)".
+
+{% note %}
+
+**Nota:** Cuando utilices acciones de configuración (tales como `actions/setup-LANGUAGE`) en {% data variables.product.product_name %} con ejecutores auto-hospedados, podrías necesitar configurar el caché de las herramientas en los ejecutores que no tengan acceso a internet. Para obtener más información, consulta la sección "[ Configurar el caché de herramientas en ejecutores auto-hospedados sin acceso a internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)".
+
+{% endnote %}
+
+### Configurar el acceso a las acciones en {% data variables.product.prodname_dotcom_the_website %}
+
+Si los usuarios de tu empresa necesitan acceso a otras acciones desde {% data variables.product.prodname_dotcom_the_website %} o {% data variables.product.prodname_marketplace %}, hay algunas cuantas opciones de configuración.
+
+El acercamiento recomendado es habilitar el acceso automático a todas las acciones desde {% data variables.product.prodname_dotcom_the_website %}. Puedes hacer esto si utilizas {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %}
+
+Como alternativa, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes descargar y sincronizar las acciones manualmente en tu instancia empresarial utilizando la herramienta `actions-sync`. Para obtener más información, consulta la sección "[Sincronizar acciones manualmente desde {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)".
diff --git a/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index c95fc9ee20..eed85c4e25 100644
--- a/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/es-ES/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: Respaldar y restablecer
 intro: 'Los datos de {% data variables.product.prodname_actions %} en tu proveedor de almacenamiento externo no se incluyen en los respaldos normales de {% data variables.product.prodname_ghe_server %} y deben respaldarse por separado.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index 265f670631..bdf3baa5f4 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: Habilitar el acceso automático a las acciones de GitHub.com utilizando GitHub Connect
-intro: 'Para permitir que {% data variables.product.prodname_actions %} utilice acciones de {% data variables.product.prodname_dotcom_the_website %} en tu instancia empresarial, puedes conectar a{% data variables.product.product_location_enterprise %} con {% data variables.product.prodname_ghe_cloud %}.'
+intro: 'Para permitir que las {% data variables.product.prodname_actions %} en tu empresa utilicen acciones de {% data variables.product.prodname_dotcom_the_website %}, puedes conectar tu instancia empresarial a {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-Predeterminadamente, los flujos de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} no pueden utilizar las acciones directamente desde {% data variables.product.prodname_dotcom_the_website %} o desde [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+Predeterminadamente, los flujos de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.product_name %} no pueden utilizar las acciones directamente desde {% data variables.product.prodname_dotcom_the_website %} o desde [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-Para que todas las acciones de {% data variables.product.prodname_dotcom_the_website %} se hagan disponibles para tu instancia empresarial, puedes utilizar {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.prodname_ghe_server %} con {% data variables.product.prodname_ghe_cloud %}. Para encontrar otras formas de acceder a las acciones desde {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Acerca de utilizar las acciones en {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)".
+Para que todas las acciones de {% data variables.product.prodname_dotcom_the_website %} se hagan disponibles para tu instancia empresarial, puedes utilizar {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %}. Para encontrar otras formas de acceder a las acciones desde {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Acerca de utilizar las acciones en tu empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
 
 ### Habilitar el acceso automático a todas las acciones de {% data variables.product.prodname_dotcom_the_website %}
 
-Antes de habilitar el acceso a todas las acciones de {% data variables.product.prodname_dotcom_the_website %} en {% data variables.product.product_location_enterprise %}, debes conectar a {% data variables.product.product_location_enterprise %} con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Antes de habilitar el acceso para todas las acciones desde {% data variables.product.prodname_dotcom_the_website %} en tu instancia empresarial, debes conectar a tu empresa con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index 811c44e019..b8a0712153 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
 
-* Crea tu bucket de Amazon S3 para almacenar artefactos que generan las ejecuciones de flujo de trabajo. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Crea tu bucket de Amazon S3 para almacenar artefactos que generan las ejecuciones de flujo de trabajo. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index 225525d517..5630f774ca 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
 
 * Para evitar la contención de recursos en el aplicativo, te recomendamos que hospedes a MinIO separado de {% data variables.product.product_location %}.
-* Crea tu bucket para almacenar los artefactos del flujo de trabajo. Para configurar tu bucket y clave de acceso, consulta la [Documentación de MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Crea tu bucket para almacenar los artefactos del flujo de trabajo. Para configurar tu bucket y clave de acceso, consulta la [Documentación de MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 7096028b38..9e09af3f20 100644
--- a/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index b29697b19e..5fdc25612a 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: Comenzar con las GitHub Actions para GitHub AE
+shortTitle: Comenzar con Acciones de GitHub
 intro: 'Aprende a configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index e48c8ba284..0fecff95d2 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,5 +1,6 @@
 ---
 title: Iniciar con GitHub Actions para GitHub Enterprise Server
+shortTitle: Comenzar con Acciones de GitHub
 intro: 'Aprende cómo habilitar y configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} por primera vez.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
@@ -7,7 +8,9 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
+  - Actions
   - Enterprise
 ---
 
@@ -116,7 +119,7 @@ Para ejecutar los flujos de trabajo de {% data variables.product.prodname_action
 
 Puedes controlar las acciones que pueden utilizar tus usuarios en tu empresa. Esto incluye el configurar {% data variables.product.prodname_github_connect %} para el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %}, o sincronizar las acciones de {% data variables.product.prodname_dotcom_the_website %} manualmente.
 
-Para obtener más información, consulta la sección "[Acerca de las acciones en {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)".
+Para obtener más información, consulta la sección "[Acerca de utilizar las acciones en tu empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
 
 ### Fortalecimiento de seguridad general para las {% data variables.product.prodname_actions %}
 
diff --git a/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md b/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md
index e5d4bb19c5..ce949fc5eb 100644
--- a/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/es-ES/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: Disponibilidad alta para las GitHub Actions
 intro: 'Existen algunas especificaciones especiales para administrar las {% data variables.product.prodname_actions %} en una configuración de disponibilidad alta.'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### Replicación o redundancia de tus datos de {% data variables.product.prodname_actions %}
diff --git a/translations/es-ES/content/admin/github-actions/index.md b/translations/es-ES/content/admin/github-actions/index.md
index 5e1d45bd7f..3d3a3c8685 100644
--- a/translations/es-ES/content/admin/github-actions/index.md
+++ b/translations/es-ES/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index d39ad5c693..d009e2d615 100644
--- a/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/es-ES/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: Sincronizar manualmente las acciones de GitHub.com
-intro: 'Para los usuarios que necesiten acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar las acciones específicas a tu instancia de {% data variables.product.prodname_ghe_server %}.'
+intro: 'Para los usuarios que necesiten acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar las acciones específicas a tu empresa.'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-El acercamiento recomendado para habilitar el acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %} es habilitar el acceso automático para todas las acciones. Puedes hacerlo utilizando {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.prodname_ghe_server %} con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+El acercamiento recomendado para habilitar el acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %} es habilitar el acceso automático para todas las acciones. Puedes hacer esto si utilizas {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %} . Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-Sin embargo, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes seguir esta guía para utilizar la herramienta de código abierto [`actions-sync`](https://github.com/actions/actions-sync) de {% data variables.product.company_short %} para sincronizar los repositorios de acción individual desde {% data variables.product.prodname_dotcom_the_website %} hacia tu instancia empresarial.
+Sin embargo, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes seguir esta guía para utilizar la herramienta de código abierto [`actions-sync`](https://github.com/actions/actions-sync) de {% data variables.product.company_short %} para sincronizar los repositorios de acción individual desde {% data variables.product.prodname_dotcom_the_website %} hacia tu empresa.
 
 ### Acerca de la herramienta `actions-sync`
 
-La herramienta `actions-sync` debe ejecutarse en una máquina que pueda acceder a la API de {% data variables.product.prodname_dotcom_the_website %} y a la API de tu instancia de {% data variables.product.prodname_ghe_server %}. La máquina no necesita estar conectada a ambas al mismo tiempo.
+La herramienta `actions-sync` debe ejecutarse en una máquina que pueda acceder a la API de {% data variables.product.prodname_dotcom_the_website %} y a la API de tu instancia de {% data variables.product.product_name %}. La máquina no necesita estar conectada a ambas al mismo tiempo.
 
 Si tu máquina tiene acceso a ambos sistemas al mismo tiempo, puedes hacer la sincronización con un simple comando de `actions-sync sync`. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`.
 
@@ -29,17 +30,17 @@ La herramienta `actions-sync` solo puede descargar acciones de {% data variables
 
 ### Prerrequisitos
 
-* Antes de utilizar la herramienta `actions-sync`, debes asegurarte de que todas las organizaciones de destino ya existan en tu instancia empresarial. El siguiente ejemplo demuestra cómo sincronizar acciones a una organización que se llama `synced-actions` en una instancia empresarial. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
-* Debes crear un token de acceso personal (PAT) en tu instancia empresarial que pueda crear y escribir en los repositorios de las organizaciones destino. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
-* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
+* Antes de utilizar la herramienta `actions-sync`, debes asegurarte de que todas las organizaciones de destino ya existan en tu empresa. El siguiente ejemplo demuestra cómo sincronizar acciones a una organización que se llama `synced-actions`. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
+* Debes crear un token de acceso personal (PAT) en tu empresa que pueda crear y escribir en los repositorios de las organizaciones destino. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
+* Si quieresSi quieres sincronizar las acciones incluidas en la organización `actions` en {% data variables.product.product_location %}, debes ser un propietario de la organización `actions`.
 
   {% note %}
 
-  **Note:** By default, even site administrators are not owners of the bundled `actions` organization.
+  **Nota:** Predeterminadamente, incluso los administradores de sitio no son propietarios de la organización empaquetada `actions`.
 
   {% endnote %}
 
-  Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)."
+  Los administradores de sitio pueden utilizar el comando `ghe-org-admin-promote` en el shell administrativo para promover a un usuario para que sea propietario de la organización empaquetada `actions`. Para obtener más información, consulta la sección "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)".
 
   ```shell
   ghe-org-admin-promote -u <em>USERNAME</em> -o actions
@@ -51,7 +52,7 @@ Este ejemplo demuestra el uso de la herramienta `actions-sync` para sincronizar
 
 {% note %}
 
-**Nota:** Este ejemplo utiliza el comando `actions-sync sync`, el cual requiere tener acceso concurrente tanto a la API de {% data variables.product.prodname_dotcom_the_website %} como a la API de tu instancia de {% data variables.product.prodname_ghe_server %} desde tu máquina. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#not-connected-instances).
+**Nota:** Este ejemplo utiliza el comando `actions-sync sync`, el cual requiere tener acceso concurrente tanto a la API de {% data variables.product.prodname_dotcom_the_website %} como a la API de tu instancia empresarial desde tu máquina. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#not-connected-instances).
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ Este ejemplo demuestra el uso de la herramienta `actions-sync` para sincronizar
    * `--destination-url`: La URL de la instancia empresarial de destino.
    * `--repo-name`: El repositorio de acción a sincronizar. Esto adopta el formato de `owner/repository:destination_owner/destination_repository`.
 
-     * El ejemplo anterior sincroniza el repositorio [`docker/build-push-action`](https://github.com/docker/build-push-action) con el repositorio `synced-actions/docker-build-push-action` en la instancia de {% data variables.product.prodname_ghe_server %} de destino. Debes crear la organización llamada `synced-actions` en tu instancia empresarial antes de ejecutar el comando anterior.
-     * Si omites el `:destination_owner/destination_repository`, la herramienta utilizará el nombre de propietario y de repositorio originales para tu instancia empresarial. Antes de ejecutar el comando, debes crear una organización nueva en tu instancia, la cual empate con el nombre de propietario de la acción. Considera utilizar una organización central para almacenar las acciones sincronizadas en tu instancia, ya que esto significa que no necesitarás crear varias organizaciones nuevas si sincronizas las acciones de propietarios diferentes.
+     * El ejemplo anterior sincroniza el repositorio [`docker/build-push-action`](https://github.com/docker/build-push-action) con el repositorio `synced-actions/docker-build-push-action` en la instancia empresarial destino. Debes crear la organización denominada `synced-actions` en tu empresa antes de ejecutar el comando anterior.
+     * Si omites el `:destination_owner/destination_repository`, la herramienta utilizará el nombre de propietario y de repositorio originales para tu empresa. Antes de ejecutar el comando, debes crear una organización nueva en tu empresa, la cual empate con el nombre de propietario de la acción. Considera utilizar una organización central para almacenar las acciones sincronizadas en tu empresa, ya que esto significa que no necesitarás crear varias organizaciones nuevas si sincronizas las acciones de propietarios diferentes.
      * Puedes sincronizar varias acciones si reemplazas el parámetro `--repo-name` con `--repo-name-list` o con `--repo-name-list-file`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#actions-sync).
-1. Después de que se haya creado el repositorio de acción en tu instancia empresarial, las personas en tu empresa pueden utilizar el repositorio de destino para referenciar la acción en sus flujos de trabajo. Para la acción de ejemplo que se muestra a continuación:
+1. Después de que se haya creado el repositorio de acción en tu empresa, las personas en tu empresa pueden utilizar el repositorio de destino para referenciar la acción en sus flujos de trabajo. Para la acción de ejemplo que se muestra a continuación:
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 8be505a206..a787d9e639 100644
--- a/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/es-ES/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### Acerca de las acciones de configuración incluídas y el caché de la herramienta del ejecutor
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-La mayoría de las acciones de autoría de {% data variables.product.prodname_dotcom %} se agrupan automáticamente con {% data variables.product.prodname_ghe_server %}. Sin embargo, los ejecutores auto-hospedados sin acceso a internet requerirán que se les configure un poco antes de que puedan utilizar las acciones de `actions/setup-LANGUAGE` incluídas, tal como `setup-node`.
+La mayoría de las acciones de autoría de {% data variables.product.prodname_dotcom %} se agrupan automáticamente con {% data variables.product.product_name %}. Sin embargo, los ejecutores auto-hospedados sin acceso a internet requieren que se les configure un poco antes de que puedan utilizar las acciones de `actions/setup-LANGUAGE` incluídas, tal como `setup-node`.
 
 Las acciones de `actions/setup-LANGUAGE` habitualmente necesitan acceso a internet para descargar los binarios de ambiente requeridos en el caché de la herramienta del ejecutor. Los ejecutores auto-hospedados sin acceso a internet no pueden descargar los binarios, así que debes poblar el caché de la herramienta manualmente en el ejecutor.
 
diff --git a/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md b/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md
index 7352b1c891..a5ab4529d3 100644
--- a/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/es-ES/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: Utilizar un ambiente de montaje
 intro: 'Aprende sobre cómo utilizar {% data variables.product.prodname_actions %} con los ambientes de montaje de {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 Puede ser útil tener un ambiente de montaje o de pruebas para {% data variables.product.product_location %}, para que así puedas probar las actualizaciones o características nuevas antes de implementarlas en tu ambiente productivo.
diff --git a/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 3e0191625c..e31724affd 100644
--- a/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Using the latest version of the official bundled actions
-intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+title: Utilizar la última versión de las acciones empaquetadas oficiales
+intro: 'Puedes actualizar las acciones que vienen en paquete para tu empresa o utilizarlas directamente desde {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+Tu instancia empresarial incluye varias acciones integradas que puedes utilizar en tus flujos de trabajo. Para obtener más información sobre las acciones en paquete, consulta la sección "[Acciones oficiales que vienen en paquete con tu instancia empresarial](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)".
 
-These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
+Estas acciones que vienen en paquete son una captura de un punto en el tiempo de las acciones oficiales que se encuentran en https://github.com/actions, así que podría haber versiones nuevas disponibles de estas. Puedes utilizar la herramienta de `actions-sync` para actualizar estas acciones o puedes configurar {% data variables.product.prodname_github_connect %} para permitir el acceso a las últimas acciones en {% data variables.product.prodname_dotcom_the_website %}. Estas opciones se describen en las siguietnes secciones.
 
-Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
+### Utilizar `actions-sync` para actualizar las acciones que vienen en paquete
 
-- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
-- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
+Para actualizar las acciones que vienen en paquete, puedes utilizar la herramienta `actions-sync` para actualizar esta captura. Para obtener más información sobre cómo utilizar `actions-sync`, consulta la sección "[Sincronizar manualmente las acciones desde {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)".
 
-These options are described in more detail in the following sections.
+### Utilizar {% data variables.product.prodname_github_connect %} para acceder a las últimas acciones
 
-### Using actions-sync to update a bundled action
+Puedes utilizar {% data variables.product.prodname_github_connect %} para permitir que {% data variables.product.product_name %} utilice acciones desde {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
+Una vez que se configura {% data variables.product.prodname_github_connect %}, puedes utilizar la versión más reciente de una acción si borras su repositorio local en la organización `actions` en tu instancia. Por ejemplo, si tu instancia empresarial está utilizando la acción `actions/checkout@v1` y necesitas utilizar `actions/checkout@v2`, el cual no está disponible en esta, lleva a cabo los siguietnes pasos para que puedas utilizar la acción más reciente de `checkout` desde {% data variables.product.prodname_dotcom_the_website %}:
 
-### Using actions from {% data variables.product.prodname_dotcom_the_website %}
+1. Predeterminadamente, los administradores de sitio no son los propietarios de la organización de acciones incluidas. Para obtener el acceso requerido para borrar el repositorio `checkout`, utiliza el comando `ghe-org-admin-promote` para promover a un usuario como propietario de la organización empaquetada `actions`. Para obtener más información, consulta la sección "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)". Por ejemplo:
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
-
-### Using the latest version by removing the specific action's tag
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
-
-For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
-
-1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
-1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
-
-When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. En tu instancia de {% data variables.product.product_name %}, borra el repositorio `checkout` dentro de la organización `actions`. Para obtener más información sobre cómo borrar un repositorio, consulta la sección "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)".
+1. Se recomienda que salgas de la organización `actions` una vez que ya no requieras acceso administrativo. Para obtener más información, consulta "[Cómo eliminarte de una organización](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)".
+1. Configura el YAML de tu flujo de trabajo para que utilice `actions/checkout@v2`.
+1. Cada vez que se ejecute tu flujo de trabajo, el ejecutor utilizará la versión `v2` de `actions/checkout` desde {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/es-ES/content/admin/guides.md b/translations/es-ES/content/admin/guides.md
new file mode 100644
index 0000000000..93fb37c610
--- /dev/null
+++ b/translations/es-ES/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: GitHub Enterprise guides
+shortTitle: Guías
+intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md
index 45493900a0..dea1a10bfc 100644
--- a/translations/es-ES/content/admin/index.md
+++ b/translations/es-ES/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: Administradores de empresa
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
+title: GitHub Enterprise Documentation
+shortTitle: GitHub Enterprise
 intro: 'La documentación y las guías para los administradores empresariales, administradores de sistema y especialistas de seguridad quienes {% if enterpriseServerVersions contains currentVersion %}despliegan, {% endif %}configuran{% if enterpriseServerVersions contains currentVersion %},{% endif %} y administran {% data variables.product.product_name %}.'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/es-ES/content/admin/installation/index.md b/translations/es-ES/content/admin/installation/index.md
index c0cd873184..1b44abdfbe 100644
--- a/translations/es-ES/content/admin/installation/index.md
+++ b/translations/es-ES/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md b/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md
index ad970a2474..0c293bec26 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/es-ES/content/admin/overview/about-data-residency.md b/translations/es-ES/content/admin/overview/about-data-residency.md
index f8b62ea767..b83d42739f 100644
--- a/translations/es-ES/content/admin/overview/about-data-residency.md
+++ b/translations/es-ES/content/admin/overview/about-data-residency.md
@@ -3,6 +3,10 @@ title: Acerca de la residencia de los datos
 intro: 'Puedes elegir la geografía en donde {% data variables.product.product_name %} almacena todos los datos de los clientes de tu empresa.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %} Puedes elegir la geografía en donde almacenas todos los datos de tus clientes en {% data variables.product.product_location %} y los miembros de tu empresa pueden acceder a {% data variables.product.product_name %} desde cualquier parte del mundo.
diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md
index 11d6e37dcc..9389c15e5f 100644
--- a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md
@@ -7,8 +7,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
+type: overview
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### Acerca de las cuentas empresariales en {% data variables.product.product_name %}
diff --git a/translations/es-ES/content/admin/overview/about-github-ae.md b/translations/es-ES/content/admin/overview/about-github-ae.md
index b51433e63d..59809742cd 100644
--- a/translations/es-ES/content/admin/overview/about-github-ae.md
+++ b/translations/es-ES/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: Acerca de GitHub AE
 intro: '{% data variables.product.prodname_ghe_managed %} es una forma de tener cumplimiento y seguridad ampliada para utilizar {% data variables.product.prodname_dotcom %} en la nube.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### Acerca de {% data variables.product.prodname_ghe_managed %}
@@ -21,7 +25,7 @@ Todos tus datos se almacenan dentro de la región geográfica de tu elección. P
 
 ### Cifrado bajo tus condiciones
 
-Todos los datos del cliente se cifran estáticos y puedes proporcionar tus propias llaves de cifrado para cifrar tus datos bajo tus propias políticas. Tú controlas tu llave y el acceso a todos tus datos. Para obtener más información, consulta la sección "[Configurar el cifrado de datos para tu empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)".
+All customer data is encrypted at rest. Para obtener más información, consulta la sección "[Configurar el cifrado de datos para tu empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)".
 
 ### Cuentas aisladas
 
diff --git a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md
index b3125b1d89..a22ac2a4de 100644
--- a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,8 +5,10 @@ intro: '{% if currentVersion == "github-ae@latest" %}Tu empresa de {% data varia
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_name %} está en mejora contínua, con una funcionalidad nueva y correcciones de errores que se presentan mediante lanzamientos mayores y menores. {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} es un servicio completamente administrado, así que {% data variables.product.company_short %} completa el proceso de mejora para tu empresa.{% endif %}
diff --git a/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md
index 3b36a2a49b..ee24dd7b5f 100644
--- a/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ Por ejemplo, aquí mostramos los costos para los usuarios con licencias en fecha
 | Usuario   | Fechas de licencia                              | Días contados | Costo  |
 | --------- | ----------------------------------------------- | ------------- | ------ |
 | @octocat  | Enero 1 - Enero 31                              | 31            | $39    |
-| @robocat  | Febrero 1 - Febrero 28                          | 29            | $35.23 |
+| @robocat  | Febrero 1 - Febrero 28                          | 28            | $35.23 |
 | @devtocat | Enero 15 - Enero 31                             | 17            | $21.39 |
 | @doctocat | Enero 1 - Enero 15                              | 31            | $39    |
 | @prodocat | Enero 7 - Enero 15                              | 25            | $31.45 |
 | @monalisa | Enero 1 - Enero 7,<br>Enero 15 - Enero 31 | 31            | $39    |
 
-Tu empresa puede incluir una o más instancias. {% data variables.product.prodname_ghe_managed %} tiene un mínimo de 500 usuarios por instancia. {% data variables.product.company_short %} te cobra por un mínimo de 500 usuarios por instancia, aún si hay menos de 500 usuarios con una licencia en ese día.
+{% data variables.product.prodname_ghe_managed %} tiene un mínimo de 500 usuarios por instancia. {% data variables.product.company_short %} te cobra por un mínimo de 500 usuarios por instancia, aún si hay menos de 500 usuarios con una licencia en ese día.
 
 Puedes ver tu uso actual en tu [Portal de cuenta de Azure](https://portal.azure.com).
 
diff --git a/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md b/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md
index 74832ed0ef..bd0b0ecb1a 100644
--- a/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/es-ES/content/admin/overview/managing-your-github-enterprise-license.md
@@ -56,7 +56,7 @@ instancia de {% data variables.product.prodname_ghe_server %} como administrador
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
 3. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-4. Revisa tu licencia actual de {% data variables.product.prodname_enterprise %}, así como las licencias de usuario utilizadas y disponibles.
+4. Revisa tus licencias actuales de {% data variables.product.prodname_enterprise %}, así como las licencias de usuario disponibles y consumidas. {% if currentVersion ver_gt "enterprise-server@3.0" %}If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
 
 ### Sincronizar de forma automática el uso de la licencia de usuario con {% data variables.product.prodname_ghe_cloud %}
 
diff --git a/translations/es-ES/content/admin/overview/system-overview.md b/translations/es-ES/content/admin/overview/system-overview.md
index a966453a5e..1cc0a09266 100644
--- a/translations/es-ES/content/admin/overview/system-overview.md
+++ b/translations/es-ES/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### Arquitectura de almacenamiento
diff --git a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index c827e00821..7d9a16b92e 100644
--- a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 71c276daa7..564e752378 100644
--- a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: Iniciar con GitHub Packages para tu empresa
+shortTitle: Getting started with GitHub Packages
 intro: 'Puedes comenzar a utilizar el {% data variables.product.prodname_registry %} en {% data variables.product.product_location %} si habilitas esta característica, configurando un almacenamiento de terceros, configurando los ecosistemas que quieras que sea compatibles y actualizando tu certificado TLS.'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index c799c73131..e97123d5fa 100644
--- a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: Guía de inicio rápido para configurar tu bucket de almacenamiento de Mi
 intro: 'Configura tu bucket de almacenamiento de MinIO personalizado para utilizarlo con {% data variables.product.prodname_registry %}.'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md b/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md
index 53f9f2df76..ea91548abd 100644
--- a/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/es-ES/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Cuando se produce una subida, cada script se ejecuta en un entorno aislado y puede realizar verificaciones en el contenido que se subió. Los scripts provocarán la aceptación de la subida si el estado de salida es 0, o rechazado si el estado de salida no es cero.
diff --git a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md
index b65c7ac085..8e8573cf3d 100644
--- a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Un entorno de pre-recepción para {% data variables.product.prodname_ghe_server %} es un entorno Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot). Dado que los ganchos de pre-recepción se ejecutan en todos los eventos de extracción, deberían ser rápidos y livianos. Normalmente, el entorno necesario para tales verificaciones será mínimo.
diff --git a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md
index 6a89656b57..ca6a0f65de 100644
--- a/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/es-ES/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Puedes ver los ejemplos de los ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} en el repositorio [`github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks).
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index d47dc22866..cd1e6380e4 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,6 +5,13 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### Acerca de {% data variables.product.prodname_GH_advanced_security %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 7daf12479e..6f02591f1f 100644
--- a/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Configurar la visibilidad predeterminada para los repositorios nuevos en tu empresa
diff --git a/translations/es-ES/content/admin/policies/index.md b/translations/es-ES/content/admin/policies/index.md
index 827dee6567..b492919004 100644
--- a/translations/es-ES/content/admin/policies/index.md
+++ b/translations/es-ES/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 900a9d1032..8b0bee3c31 100644
--- a/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/es-ES/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### Crear ganchos de pre-recepción
diff --git a/translations/es-ES/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/es-ES/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..4cf3fb591b
--- /dev/null
+++ b/translations/es-ES/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Acerca de las restricciones para tu cuenta empresarial
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restringir las notificaciones por correo electrónico para tu cuenta empresarial
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/es-ES/content/admin/release-notes.md b/translations/es-ES/content/admin/release-notes.md
index 0baec21d7f..1a810daa9a 100644
--- a/translations/es-ES/content/admin/release-notes.md
+++ b/translations/es-ES/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/es-ES/content/admin/user-management/about-migrations.md b/translations/es-ES/content/admin/user-management/about-migrations.md
index a3515abe1e..1b8ae4a257 100644
--- a/translations/es-ES/content/admin/user-management/about-migrations.md
+++ b/translations/es-ES/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Tipos de migraciones
diff --git a/translations/es-ES/content/admin/user-management/adding-people-to-teams.md b/translations/es-ES/content/admin/user-management/adding-people-to-teams.md
index 38d3f9382b..c184c6e720 100644
--- a/translations/es-ES/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/es-ES/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: 'Una vez que se ha creado un equipo, los administradores de la organización pueden agregar usuarios desde {% data variables.product.product_location %} al equipo y determinar a qué repositorios tienen acceso.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Cada equipo tiene sus propios premisos de acceso definidos de manera individual [ para repositorios que le pertenecen a tu organización](/articles/permission-levels-for-an-organization).
diff --git a/translations/es-ES/content/admin/user-management/audit-logging.md b/translations/es-ES/content/admin/user-management/audit-logging.md
index 7a4d3087fa..b1a24e9305 100644
--- a/translations/es-ES/content/admin/user-management/audit-logging.md
+++ b/translations/es-ES/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Para encontrar una lista completa, consulta "[Acciones auditadas](/admin/user-management/audited-actions)". Para obtener más información sobre cómo encontrar una acción en particular, consulta la sección "[Buscar la bitácora de auditoría](/admin/user-management/searching-the-audit-log)".
diff --git a/translations/es-ES/content/admin/user-management/audited-actions.md b/translations/es-ES/content/admin/user-management/audited-actions.md
index 8e11bc2f17..2d3a03167c 100644
--- a/translations/es-ES/content/admin/user-management/audited-actions.md
+++ b/translations/es-ES/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### Autenticación
diff --git a/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md b/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md
index 1c402449e2..6e0f314922 100644
--- a/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/es-ES/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 Una vez iniciada, la auditoría desactiva todas las claves SSH existentes y obliga a los usuarios a aprobarlas o rechazarlas antes de que sea posible clonarlas, extraerlas o subirlas a cualquier repositorio. Una auditoría es útil cuando un empleado o contratista se va de la empresa y necesitas asegurarte de que todas las claves estén verificadas.
diff --git a/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md
index 6317ea7b22..5233dad981 100644
--- a/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### Acceder al registro de auditoría
diff --git a/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md b/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md
index 822218303e..275f529444 100644
--- a/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/es-ES/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index 22673ec22a..dd9adf95f3 100644
--- a/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### Acerca de {% data variables.large_files.product_name_long %}
diff --git a/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md
index 3bd72b3942..1a69ca93b5 100644
--- a/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/es-ES/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md
index 4c3f3333c8..e74a099ddd 100644
--- a/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/es-ES/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/user-management/creating-teams.md b/translations/es-ES/content/admin/user-management/creating-teams.md
index 7495e9f0d2..9da606083e 100644
--- a/translations/es-ES/content/admin/user-management/creating-teams.md
+++ b/translations/es-ES/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Los equipos son centrales para muchas de las características colaborativas de {% data variables.product.prodname_dotcom %}, como las @menciones del equipo para notificar a las partes correspondientes que les quieres solicitar su colaboración o atención. Para obtener más información, consulta "[Niveles de permisos para el repositorio de una organizazión](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)".
diff --git a/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index 62f1d31cd0..a730f21027 100644
--- a/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: Personalizar los mensajes de usuario para tu empresa
+shortTitle: Customizing user messages
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: 'Puedes crear mensajes personalizados que los usuarios verán en {% data
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### Acerca de los mensajes de usuario
@@ -72,7 +75,7 @@ Cada vez que un usuario vea un mensaje obligatorio, se crea un evento de bitáco
 
 {% note %}
 
-**Note:** If you change the mandatory message for {% data variables.product.product_location %}, users who have already acknowledged the message will not see the new message.
+**Nota:** Si cambias el mensaje obligatorio de {% data variables.product.product_location %}, los usuarios que ya lo hayan reconocido no verán el mensaje nuevo.
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index 225ffd09d3..cdfe315eb0 100644
--- a/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: Puedes prevenir que las personas utilicen git a través de SSH para ciert
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### Inhabilitar el acceso SSH de Git para un repositorio específico
diff --git a/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md
index b071fcdaa0..30069980cd 100644
--- a/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparar la orgnanización origen en {% data variables.product.prodname_dotcom %}
diff --git a/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index 5bf1684268..285a14b7da 100644
--- a/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparar la instancia origen de {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 63290d9472..27930e76de 100644
--- a/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/es-ES/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Importar proyectos de Mercurial
diff --git a/translations/es-ES/content/admin/user-management/log-forwarding.md b/translations/es-ES/content/admin/user-management/log-forwarding.md
index 5f7a46c936..77a8a35708 100644
--- a/translations/es-ES/content/admin/user-management/log-forwarding.md
+++ b/translations/es-ES/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Es compatible cualquier sistema de recopilación de registro que admita los flujos de registro syslog-style (p. ej., [Logstash](http://logstash.net/) y [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
diff --git a/translations/es-ES/content/admin/user-management/managing-dormant-users.md b/translations/es-ES/content/admin/user-management/managing-dormant-users.md
index db96808451..987b1619e5 100644
--- a/translations/es-ES/content/admin/user-management/managing-dormant-users.md
+++ b/translations/es-ES/content/admin/user-management/managing-dormant-users.md
@@ -9,8 +9,11 @@ intro: 'Se considera una cuenta de usuario como durmiente si no ha tenido activi
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 "Actividad" incluye, entre otros:
diff --git a/translations/es-ES/content/admin/user-management/managing-global-webhooks.md b/translations/es-ES/content/admin/user-management/managing-global-webhooks.md
index 2add816cca..cc4535c4ee 100644
--- a/translations/es-ES/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/es-ES/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### Acerca de los webhooks locales
diff --git a/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md b/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md
index 0356929745..3e24803d1c 100644
--- a/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/es-ES/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: Administrar proyectos mediante JIRA
-intro: 'Puedes integrar JIRA con {% data variables.product.prodname_enterprise %} para la administración de proyectos.'
+title: Administrar proyectos utilizando Jira
+intro: 'Puedes integrar Jura con {% data variables.product.prodname_enterprise %} para la administración de proyectos.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### Conectar JIRA a una organización {% data variables.product.prodname_enterprise %}
+### Conectar a Jira a una organización de {% data variables.product.prodname_enterprise %}
 
-1. Inicia sesión en tu cuenta de {% data variables.product.prodname_enterprise %} en http[s]://[hostname]/login.
-1. En el ángulo superior derecho de cualquier página, haz clic en el icono de ajustes (engranaje) de la cuenta.
-1. En la barra lateral izquierda, haz clic en el nombre de tu organización.
-1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones).
-1. En el ángulo superior derecho del cuadro **Organization applications** (Aplicaciones de la organización), haz clic en **Register new application** (Registrar aplicación nueva)</strong>.
-1. Completa los parámetros de la aplicación:
-    - En el campo **Application name** (Nombre de la aplicación), escribe "JIRA".
-    - En el campo **Homepage URL** (URL de inicio de sesión), escribe la URL completa de tu instancia JIRA.
-    - En el campo **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa de tu instancia JIRA.
-1. Haz clic en **Register application** (Registrar aplicación).
-1. En la parte inferior de la página, observa el **Client ID** (ID de cliente) y **Client Secret** (Secreto de cliente). Necesitarás estos datos para configurar tu instancia JIRA.
+1. Inicia sesión en tu cuenta de {% data variables.product.prodname_enterprise %} en http[s]://[hostname]/login. Si ya iniciaste sesión, haz clic en el logo de {% data variables.product.prodname_dotcom %} en la esquina superior izquierda.
+2. Haz clic en tu icono de perfil debajo del logo de {% data variables.product.prodname_dotcom %} y selecciona la organización con la que te gustaría conectar a Jira.
 
-### Configuración de instancia de JIRA
+  ![Selecciona una organización](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. En tu instancia de JIRA, inicia sesión en una cuenta con acceso administrativo.
-1. En la parte superior de la página, haz clic en el icono de ajustes (engranaje).
-1. En el desplegable de los parámetros, elige **Add-ons** (Adicionales).
-1. En la barra lateral izquierda, debajo de **Source control** (Control de origen), haz clic en **DVCS accounts** (Cuentas de DVCS).
-1. Haz clic en **Link Bitbucket or GitHub account** (Enlazar cuenta de Bitbucket o GitHub).
-1. En el modal **Add New Account** (Agregar nueva cuenta), completa tus parámetros de {% data variables.product.prodname_enterprise %}:
-    - En el menú desplegable **Host**, elige **GitHub Enterprise**.
+3. Haz clic en el enlace de **Editar la configuración de _nombre de organización_**.
+
+  ![Editar la configuración de organización](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. En la barra lateral izquierda, debajo de **Configuración de desarrollador**, haz clic en **Apps de OAuth**.
+
+  ![Selecciona Apps de OAuth](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Haz clic en el botón de **Registrar aplicación nueva**.
+
+  ![Registrar botón de aplicación nueva](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. Completa los parámetros de la aplicación:
+    - En el campo de **Nombre de aplicación**, teclea "Jira" o cualquier nombre que te gustaría utilizar para identificar a la instancia de Jira.
+    - En el campo **URL de página principal**, escribe la URL completa de tu instancia de Jira.
+    - En el campo **URL de rellamado de autorización**, escribe la URL completa de tu instancia de Jira.
+7. Haz clic en **Register application** (Registrar aplicación).
+8. En la parte inferior de la página, observa el **Client ID** (ID de cliente) y **Client Secret** (Secreto de cliente). Necesitarás estos para configurar tu instancia de Jira.
+
+### Configuración de la instancia de Jira
+
+1. En tu instancia de Jira, inicia sesión en una cuenta con acceso administrativo.
+2. En la parte superior de la página, haz clic en el icono de configuración (engrane) y elige **Aplicaciones**.
+
+  ![Seleccionar aplicaciones en la configuración de Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. En la barra lateral izquierda, debajo de **Integraciones**, haz clic en **Cuentas DVCS**.
+
+  ![Menú de integraciones de Jira - Cuentas DVCS](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Haz clic en **Enlazar cuenta de Bitbucket Cloud o de {% data variables.product.prodname_dotcom %}**.
+
+  ![Enlazar cuenta de GitHub a Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. En el modal **Add New Account** (Agregar nueva cuenta), completa tus parámetros de {% data variables.product.prodname_enterprise %}:
+    - Desde el menú desplegable de **Host**, elige **{% data variables.product.prodname_enterprise %}**.
     - En el campo **Team or User Account** (Cuenta de equipo o usuario), escribe el nombre de tu organización {% data variables.product.prodname_enterprise %} o cuenta personal.
     - En el campo **OAuth Key** (Clave OAuth), escribe el ID de cliente de tu aplicación de programador de {% data variables.product.prodname_enterprise %}.
     - En el campo **OAuth Secret** (OAuth secreto), escribe el secreto de cliente para tu aplicación de programador de {% data variables.product.prodname_enterprise %}.
-    - Si no quieres vincular los repositorios nuevos que pertenecen a tu organización o cuenta personal de {% data variables.product.prodname_enterprise %}, quita la marca de selección de **Auto Link New Repositories** (Vincular automáticamente repositorios nuevos).
-    - Si no quieres habilitar las confirmaciones inteligentes, quita la marca de selección **Enable Smart Commits** (Habilitar confirmaciones inteligentes).
+    - Si no quieres enlazar los repositorios nuevos que pertenecen a tu organización o cuenta personal de {% data variables.product.prodname_enterprise %}, quita la marca de selección de **Enlazar los repositorios nuevos automáticamente**.
+    - Si no quieres habilitar las confirmaciones inteligentes, deselecciona **Habilitar las confirmaciones inteligentes**.
     - Da clic en **Agregar**.
-1. Revisa los permisos que concedes a tu cuenta de {% data variables.product.prodname_enterprise %} y haz clic en **Authorize application** (Autorizar aplicación).
-1. Si es necesario, escribe tu contraseña para continuar.
+6. Revisa los permisos que concedes a tu cuenta de {% data variables.product.prodname_enterprise %} y haz clic en **Authorize application** (Autorizar aplicación).
+7. Si es necesario, escribe tu contraseña para continuar.
diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md
index 9832dc7bb1..310ba70c15 100644
--- a/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Aplicar los datos importados en {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md b/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md
index 7c91cb6310..34042ae2c8 100644
--- a/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/es-ES/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### Acerca de los repositorios internos
@@ -34,6 +38,12 @@ El script de migración no tendrá efecto si no tienes el modo privado habilitad
 ### Ejecutar la migración
 
 1. Conecta con el shell administrativo. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)."
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. Ejecuta el comando de migración.
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. Navega hacia el directorio `/data/github/current`.
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ El script de migración no tendrá efecto si no tienes el modo privado habilitad
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 Se mostrará el registro de salida en la terminal y quedará en `/tmp/convert_public_ghes_repos_to_internal.log`.
 
diff --git a/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index fd7b0684d3..f0abbd1564 100644
--- a/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/es-ES/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 Generalmente, si alguien elimina un repositorio, estará disponible en el disco por 90 días y se puede restablecer mediante el tablero de administración del sitio. Después de los 90 días, el repositorio se purga y se elimina para siempre. Si asignas un titular legal a un usuario o una organización, los repositorios que ellos poseen se pueden restablecer indefinidamente.
diff --git a/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index 56ba861abc..1776b240eb 100644
--- a/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Preparar los datos migrados para importarlos a {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md
index 28b1ecee13..200bb4497a 100644
--- a/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/es-ES/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: Puedes prevenir que los usuarios creen organizaciones en tu empresa.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index bb38c9dd7d..08d7d361e0 100644
--- a/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/es-ES/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: 'Los administradores del sitio pueden promover cualquier cuenta de usuarios normales a un administrador del sitio, así como degradar a otros administradores del sitio a usuarios normales.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md b/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md
index 85259e9d74..186f07e2f7 100644
--- a/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/es-ES/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 Siempre que se sube una confirmación de cambios a {% data variables.product.prodname_enterprise %}, se vincula a una cuenta de usuario, si ambas están asociadas con la misma dirección de correo electrónico. Sin embargo, las confirmaciones de cambio existentes *no* se vinculan de forma retroactiva cuando un usuario registra una dirección de correo electrónico nueva o crea una cuenta nueva.
diff --git a/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md
index 7427598a67..5de9c78f1e 100644
--- a/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/es-ES/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Solo los propietarios o los administradores del equipo pueden eliminar miembros de la organización. Cuando se elimina un usuario de un equipo o una organización, sus propuestas, solicitudes de extracción y comentarios en los repositorios de la organización permanecen intactos y siguen siendo atribuidos al usuario.
diff --git a/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index cd6df018d3..b1a2c16400 100644
--- a/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/es-ES/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 Cuando utilizas LDAP o la autenticación integrada, la autenticación bifactorial será compatible en {% data variables.product.product_location %}. Los administradores de la organización le pueden solicitar a los miembros que tengan la autenticación de dos factores activada.
diff --git a/translations/es-ES/content/admin/user-management/searching-the-audit-log.md b/translations/es-ES/content/admin/user-management/searching-the-audit-log.md
index 51757f6a34..fbb4a8957f 100644
--- a/translations/es-ES/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/es-ES/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### Buscar sintaxis de consultas
diff --git a/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md
index 6ffda42017..2a1e7992d7 100644
--- a/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/es-ES/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Si un usuario se va o se traslada a un lugar diferente de la empresa, deberías eliminar o modificar su posibilidad de acceder a {% data variables.product.product_location %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 Puedes suspender las cuentas de usuario de {% data variables.product.prodname_ghe_server %} de aquellos que abandonen la compañía para abrir licencias de usuario en tu licencia de {% data variables.product.prodname_enterprise %} preservando las propuestas, comentarios, repositorios, gists y otros datos que hayan creado. Los usuarios suspendidos no pueden iniciar sesión en tu instancia, y no pueden subir ni extraer un código.
diff --git a/translations/es-ES/content/admin/user-management/viewing-push-logs.md b/translations/es-ES/content/admin/user-management/viewing-push-logs.md
index d4627777f5..8b4b7c7473 100644
--- a/translations/es-ES/content/admin/user-management/viewing-push-logs.md
+++ b/translations/es-ES/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 Las entradas de registro de subida muestran:
diff --git a/translations/es-ES/content/code-security/getting-started/about-securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/about-securing-your-repository.md
index 01a1a914e8..de6e3e831c 100644
--- a/translations/es-ES/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/es-ES/content/code-security/getting-started/about-securing-your-repository.md
@@ -22,11 +22,13 @@ El primer paso para asegurar un repositorio es configurar quién puede ver y mod
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 #### Disponible para todos los repositorios
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **Política de seguridad**
 
-  Facilítale a las personas el poder reportar de forma confidencial las vulnerabilidades de seguridad que hayan encontrado en tu repositorio. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)".
+  Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)".
+{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **Asesorías de seguridad**
 
   Debate en privado y arregla las vulnerabilidades de seguridad en el código de tu repositorio. Puedes entonces publicar la asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad en cuestión y alentarlos a mejorar la versión que tienen actualmente. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
diff --git a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..8f38f69b30
--- /dev/null
+++ b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: Agregar una política de seguridad a tu repositorio
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### Acerca de las políticas de seguridad
+
+To give people instructions for reporting security vulnerabilities in your project,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+Puedes crear una política de seguridad predeterminada para tu cuenta de usuario o de organización. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+{% endif %}
+
+{% tip %}
+
+**Sugerencia:** Para que las demás personas puedan encontrar tu política de seguridad, puedes vincular tu archivo _SECURITY.md_ desde otros lugares en tu repositorio, como un archivo README. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)".
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+Después de que alguien reporte una vulnerabilidad de seguridad en tu proyecto, puedes utilizar {% data variables.product.prodname_security_advisories %} para divulgar, arreglar y publicar información acerca de la misma. Para obtener más información sobre el proceso de reportar y divulgar vulnerabilidades en {% data variables.product.prodname_dotcom %}, consulta la sección "[Acerca de la divulgación coordinada de las vulnerabilidades de seguridad](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para obtener más información acerca de las {% data variables.product.prodname_security_advisories %}, consulta la sección "[Acerca del {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+### Agregar una política de seguridad a tu repositorio
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**. ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Haz clic en **Start setup** (Iniciar configuración). ![Botón Start setup (Iniciar configuración)](/assets/images/help/security/start-setup-security-policy-button.png)
+5. En el archivo _SECURITY.md_ nuevo, agrega información sobre las versiones compatibles de tu proyecto y cómo informar una vulnerabilidad.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### Leer más
+
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/es-ES/content/code-security/getting-started/index.md b/translations/es-ES/content/code-security/getting-started/index.md
index 36a5679547..d59a7d70ab 100644
--- a/translations/es-ES/content/code-security/getting-started/index.md
+++ b/translations/es-ES/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### Índice
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md
index ebf7a04490..db89e0e9d7 100644
--- a/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md
+++ b/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md
@@ -45,7 +45,7 @@ Actualmente, {% data variables.product.product_name %} escanea los repositorios
 El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible en todos los repositorios que pertenezcan a la organización como parte de la {% data variables.product.prodname_GH_advanced_security %}. No se encuentra disponible en repositorios que pertenezcan a usuarios individuales.
 {% endif %}
 
-Si eres un administrador de repositorio o un propietario de organización, puedes habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %} privados{% endif %} que pertenezcan a las organizaciones. You can enable  {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+Si eres un administrador de repositorio o un propietario de organización, puedes habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %} privados{% endif %} que pertenezcan a las organizaciones. Puedes habilitar el {% data variables.product.prodname_secret_scanning %} para todos tus repositorios, o para todos los repositorios nuevos dentro de tu organización.{% if currentVersion == "free-pro-team@latest" %} El {% data variables.product.prodname_secret_scanning_caps %} no se encuentra disponible para los repositorios privados que pertenezcan a los usuarios individuales.{% endif %} para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" y "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
 Cuando subes tus confirmaciones a un repositorio{% if currentVersion == "free-pro-team@latest" %} privado{% endif %} que tenga habilitado el {% data variables.product.prodname_secret_scanning %}, {% data variables.product.prodname_dotcom %} escanea el contenido de las confirmaciones para encontrar secretos.
 
diff --git a/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index a2aa87a7ee..1c92a658fc 100644
--- a/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -27,13 +27,19 @@ topics:
 
 ### Habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}
 
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization.
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. Puede que necesites habilitar la {% data variables.product.prodname_GH_advanced_security %} para activar el botón de "{% data variables.product.prodname_secret_scanning_caps %}". A la derecha de "{% data variables.product.prodname_GH_advanced_security %}", da clic en **Habilitar**. ![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. Da clic en **Habilitar la {% data variables.product.prodname_GH_advanced_security %} para este repositorio** para confirmar la acción. ![Confirmar la habilitación de la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %}, esto podría habilitar automáticamente el {% data variables.product.prodname_secret_scanning %} para el repositorio (esto se controla en la configuración de la organización). Si se muestra "{% data variables.product.prodname_secret_scanning_caps %}" con un botón de **Habilitar**, aún necesitarás habilitar el {% data variables.product.prodname_secret_scanning %} si das clic en **Habilitar**. Si ves un botón de **Inhabilitar**, entonces el {% data variables.product.prodname_secret_scanning %} ya se encuentra habilitado. ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% if currentVersion == "free-pro-team@latest" %}![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. Si se muestra "{% data variables.product.prodname_secret_scanning_caps %}" con un botón de **Habilitar**, aún necesitarás habilitar el {% data variables.product.prodname_secret_scanning %} si das clic en **Habilitar**. Si ves un botón de **Inhabilitar**, entonces el {% data variables.product.prodname_secret_scanning %} ya se encuentra habilitado. ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
 7. A la derecha de "{% data variables.product.prodname_secret_scanning_caps %}", da clic en **Habilitar**. ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
@@ -66,7 +72,7 @@ Puedes utilizar un archivo *secret_scanning.yml* para excluir los directorios de
 
     {% endnote %}
 
-También puedes ignorar alertas individuales de {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)".
+También puedes ignorar alertas individuales de {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)".
 
 ### Leer más
 
diff --git a/translations/es-ES/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/es-ES/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index bd8139f55c..ba6e9933fa 100644
--- a/translations/es-ES/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/es-ES/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -14,7 +14,7 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-### Administrar alertas
+### Managing {% data variables.product.prodname_secret_scanning %} alerts
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
@@ -49,3 +49,11 @@ Cuando un secreto se haya confirmado en un repositorio, deberás considerarlo en
 
 - Para un token de acceso personal de {% data variables.product.prodname_dotcom %} comprometido, elimina el token comprometido, crea un nuevo token y actualiza todo servicio que use el token antiguo. Para obtener más información, consulta la sección "[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)".
 - Para todos los demás secretos, verifica primero que aquellos que se hayan confirmado en {% data variables.product.product_name %} sean válidos. De ser así, crea un secreto nuevo, actualiza cualquier servicio que utilice el secreto anterior, y luego bórralo.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.prodname_dotcom %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
diff --git a/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md
index 49196e6f7a..c8e6b739e3 100644
--- a/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: About code scanning
-intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.'
+title: Acerca del escaneo de código
+intro: 'Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar vulnerabilidades de seguridad y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/managing-security-vulnerabilities/about-automated-code-scanning
@@ -13,53 +13,51 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-### About {% data variables.product.prodname_code_scanning %}
+### Acerca de {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.about-code-scanning %}
 
-You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
+Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar, clasificar y priorizar los arreglos a problemas existentes en tu código. {% data variables.product.prodname_code_scanning_capc %} también previene a los desarrolladores de introducir nuevos problemas. Puedes programar días y horas específicos para los escaneos, o activarlos cuando ocurra un evento específico en el repositorio, tal como una carga de información.
 
-If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+Si {% data variables.product.prodname_code_scanning %} encuentra una vulnerabilidad potencial o un error en tu código, {% data variables.product.prodname_dotcom %} mostrará una alerta en el repositorio. {% data variables.product.prodname_dotcom %} cerrará la alerta una vez que arregles el código que la activó. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
 
-To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see 
-"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see  "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." 
+Para monitorear los resultados del {% data variables.product.prodname_code_scanning %} a lo largo de tus repositorios o de tu organización, puedes utilizar webhooks y la API del {% data variables.product.prodname_code_scanning %}. Para obtener más información sobre los webhooks para el {% data variables.product.prodname_code_scanning %}, consulta la sección [Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". Para obtener más información sobre las terminales de la API, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)".
 
-To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+Para iniciar con el {% data variables.product.prodname_code_scanning %}, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
 
-### About {% data variables.product.prodname_codeql %}
+### Acerca de {% data variables.product.prodname_codeql %}
 
-You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. 
+Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). {% data variables.product.prodname_codeql %} trata el código como datos, lo cual te permite encontrar vulenrabilidades potenciales en tu código con más confianza que en los anallizadores estáticos trandicionales.
 
-{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website.
+{% data variables.product.prodname_ql %}Es el lenguaje de consulta que impulsa a {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} es un lenguaje de programación lógico orientado a objetos. {% data variables.product.company_short %}, los expertos del lenguaje, y los investigadores de seguridad crean las consultas que se utilizan para {% data variables.product.prodname_code_scanning %}, y éstas son de código abierto. La comunidad mantiene y actualiza estas consultas para mejorar el análisis y reducir los falsos positivos. Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) en el sitio web de GitHub Security Lab.
 
-{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
+Para obtener más información acerca de las terminales de la API para {% data variables.product.prodname_code_scanning %}, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)".
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
+Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) en la documentación de {% data variables.product.prodname_codeql %}.
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-### About billing for {% data variables.product.prodname_code_scanning %}
+### Acerca de la facturación para {% data variables.product.prodname_code_scanning %}
 
-{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
+{% data variables.product.prodname_code_scanning_capc %} utiliza {% data variables.product.prodname_actions %}, y cada ejecución de un flujo de trabajo de {% data variables.product.prodname_code_scanning %} consume minutos para {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)".
 
 {% endif %}
 
-### About third-party code scanning tools
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### About third-party {% data variables.product.prodname_code_scanning %} tools
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+You can run third-party analysis tools within {% data variables.product.product_name %} using actions or within an external CI system. For more information, see "[Setting up code scanning for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
 
-### Further reading
+### Leer más
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)"
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
-- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
+- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) en el sitio web del Comité OASIS
diff --git a/translations/es-ES/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..65edbee1ab
--- /dev/null
+++ b/translations/es-ES/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)".
+
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using actions. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case.
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Codebases with a compiled language that can be built with a single command or by running a single script.
+
+Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)".
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to:
+- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis.
+- Analyze more than one language in a repository.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)".
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
diff --git a/translations/es-ES/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/about-integration-with-code-scanning.md
index 62f9542195..74296afdf9 100644
--- a/translations/es-ES/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/es-ES/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 15a3955bca..52f7aa31ff 100644
--- a/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md
index 81c0d0c9af..2e1a84503d 100644
--- a/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring code scanning
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+title: Configurar el escaneo de código
+intro: 'Puedes configurar la forma en que {% data variables.product.prodname_dotcom %} escanea el código en tu proyecto para encontrar vulnerabilidades y errores.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
 miniTocMaxHeadingLevel: 4
@@ -14,52 +14,67 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About {% data variables.product.prodname_code_scanning %} configuration
+### Acerca de la configuración de {% data variables.product.prodname_code_scanning %}
 
-You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+{%- else %}
+"[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}.
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
 
-Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+Antes de que puedas configurar el {% data variables.product.prodname_code_scanning %} para un repositorio, debes configurar el {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a este. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+El análisis de {% data variables.product.prodname_codeql %} es tan solo un tipo de {% data variables.product.prodname_code_scanning %} que puedes hacer en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} en  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contiene otros flujos de trabajo de {% data variables.product.prodname_code_scanning %} que puedes utilizar. {% if currentVersion == "free-pro-team@latest" %}Puedes encontrar una selección de estos en la página de "Iniciar con el {% data variables.product.prodname_code_scanning %}", a la cual puedes acceder desde la pestaña de **{% octicon "shield" aria-label="The shield symbol" %} Seguridad**.{% endif %} Los ejemplos especificos que se muestran en este artículo se relacionan con el archivo del {% data variables.product.prodname_codeql_workflow %}.
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} guarda los archivos de flujo de trabajo en el directorio de _.github/workflows_ de tu repositorio. Puedes encontrar un flujo de trabajo que hayas agregado si buscas su nombre de archivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. En tu repositorio, navega hasta el archivo de flujo de trabajo que deseas editar.
+1. En el ángulo superior derecho de la vista del archivo, para abrir el editor de flujo de trabajo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}.![Botón para editar un archivo de flujo de trabajo](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. Después de que hayas editado el archivo, da clic en **Iniciar confirmación** y completa el formato de "Cambios de la confirmación". Puedes elegir confirmar directamente en la rama actual, o crear una rama nueva e iniciar una solicitud de extracción. ![Confirmar la actualización del flujo de trabajo de codeql.yml](/assets/images/help/repository/code-scanning-workflow-update.png)
 
-For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Para obtener más información acerca de cómo editar los archivos de flujo de trabajo, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
-### Configuring frequency
+### Configurar la frecuencia
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+Puedes escanear código con cierta programación o cuando ocurren eventos específicos en un repositorio.
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+Escanear el código en cada carga al repositorio, y cada vez que se crea una solicitud de extracción, previene que los desarrolladores introduzcan vulnerabilidades y errores nuevos en dicho código. Escanear el código con una programación definida te informará de las últimas vulnerabilidades y errores que {% data variables.product.company_short %}, los investigadores de seguridad, y la comunidad descubren, aún cuando los desarrolladores no estén manteniendo el repositorio activamente.
 
-#### Scanning on push
+#### Escanear cuando se carga información
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+Si utilizas el flujo de trabajo predeterminado, el {% data variables.product.prodname_code_scanning %} escaneará el código en tu repositorio una vez por semana, adicionalmente a los escaneos activados por los eventos. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)".
 
-#### Scanning pull requests
+Si escaneas al subir, entonces los resultados aparecen en la pestaña de **Seguridad** de tu repositorio. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)".
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+{% note %}
 
-For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+**Nota**: Si quieres que las alertas del {% data variables.product.prodname_code_scanning %} aparezcan como verificaciones de solicitudes de cambio, debes utilizar el evento `pull_request` que se describe más adelante.
 
-#### Avoiding unnecessary scans of pull requests
+{% endnote %}
 
-You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+#### Escanear las solicitudes de extracción
+
+El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza el evento `pull_request` para activar un escaneo de código sobre las solilcitudes de cambios que se dirigen a la rama predeterminada. {% if currentVersion ver_gt "enterprise-server@2.21" %}El evento de `pull_request` no se activará si la solicitud de cambios se abrió desde una bifurcación privada.{% else %}Si una solicitud de cambios es de una bifurcación privada, el evento de `pull_request` solo se activará si seleccionaste la opción de "Ejecutar flujos de trabajo desde solicitudes de cambios de la bifurcación" en la configuración del repositorio. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+
+Para obtener más información acerca del evento `pull_request`, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)".
+
+Si escaneas las solicitudes de cambios, entonces los resultados aparecerán como alertas en una verificación de solicitud de cambios. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del escaneo de código en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
+
+#### Evitar escaneos innecesarios en las solicitudes de cambios
+
+Puede que quieras evitar que se active un escaneo de código en solicitudes de cambio específicas que se dirijan a la rama predeterminada, independientemente de los archivos que se hayan cambiado. Puedes configurar esto si especificas `on:pull_request:paths-ignore` o `on:pull_request:paths` en el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. Por ejemplo, si los únicos cambios en una solicitud de cambios se hacen en archivos con las extensiones `.md` o `.txt`, puedes utilizar el siguiente arreglo de `paths-ignore`.
 
 ``` yaml
 on:
@@ -74,28 +89,28 @@ on:
 
 {% note %}
 
-**Notes**
+**Notas**
 
-* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+* `on:pull_request:paths-ignore` y `on:pull_request:paths` configuran condiciones que determinan si una acción en el flujo de trabajo se ejecutará en una solicitud de cambios. No determinan qué archivos se analizarán cuando las acciones _se_ ejecuten. Cuando una solicitud de cambios contiene cualquier archivo que no coincida con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, el flujo de trabajo ejecuta las acciones y escanea todos los archivos que cambiaron en la solicitud de cambios, incluyendo aquellos que coincidieron con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, a menos de que éstos se hayan excluido. Para obtener más información sobre cómo excluir archivos del análisis, consulta la sección "[Especificar directorios para escanear](#specifying-directories-to-scan)".
+* Para los archivos de flujo de trabajo del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, no utilices las palabras clave `paths-ignore` o `paths` con el evento `on:push`, ya que es probable que cause que falten análisis. Para obtener resultados precisos, el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} necesita poder comparar los cambios nuevos con el análisis de la confirmación previa.
 
 {% endnote %}
 
-For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+Para obtener más información acerca de utilizar `on:pull_request:paths-ignore` y `on:pull_request:paths` para determinar cuando se ejecutará un flujo de trabajo para una solicitud de cambios, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)".
 
-#### Scanning on a schedule
+#### Escanear de forma pre-programada
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+El flujo de trabajo del {% data variables.product.prodname_code_scanning %} utiliza el evento `pull_request` para activar un escaneo de código en la confirmación `HEAD` de una solicitud de extracción. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)".
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+**Nota**: {% data variables.product.prodname_dotcom %} solo ejecuta jobs pre-programados que se encuentren en flujos de trabajo de la rama predeterminada. Cambiar la programación en un flujo de trabajo en cualquier otra rama no tendrá efecto hasta que fusiones esta rama con la predeterminada.
 
 {% endnote %}
 
-#### Example
+#### Ejemplo
 
-The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+El siguiente ejemplo muestra un {% data variables.product.prodname_codeql_workflow %} para un repositorio particular que tiene una rama predeterminada que se llama `main` y una protegida que se llama `protected`.
 
 ``` yaml
 on:
@@ -107,16 +122,16 @@ on:
     - cron: '20 14 * * 1'
 ```
 
-This workflow scans:
-* Every push to the default branch and the protected branch
-* Every pull request to the default branch
-* The default branch every Monday at 14:20 UTC
+Este flujo de trabajo escanea:
+* Cada subida a la rama predeterminada y a la rama protegida
+* Cada solicitud de cambios a la rama predeterminada
+* La rama predeterminada cada lunes a las 14:20 UTC
 
-### Specifying an operating system
+### Especificar un sistema operativo
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
+Si tu código requiere un sistema operativo específico para compilar, puedes configurarlo en tu flujo de trabajo. Edita el valor de `jobs.analyze.runs-on` para especificar el sistema operativo para la máquina que ejecuta tus acciones de {% data variables.product.prodname_code_scanning %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}Especificas el sistema operativo utilizando una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% else %}
 
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+Si eliges utilizar une ejecutor auto-hospedado para el escaneo de código, puedes especificar un sistema operativo si utilizas una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% endif %}
 
 ``` yaml
 jobs:
@@ -125,23 +140,23 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+{% data variables.product.prodname_code_scanning_capc %} es compatible con las últimas versiones de macOs, Ubuntu, y Windows. Los valores habituales para esta configuración son por lo tanto: `ubuntu-latest`, `windows-latest`, y `macos-latest`. Para obtener más información, consulta las secciones {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" y "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}".
 
-{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}Debes asegurarte de qeu Git esté en la variable "PATH" en tus ejecutores auto-hospedados.{% else %}Si utilizas el ejecutor auto-hospedado, debes asegurarte de que git esté en la variable "PATH".{% endif %}
 
-### Changing the languages that are analyzed
+### Cambiar los lenguajes que se analizan
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
+El {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} detecta automáticamente el código que se escribe en los lenguajes compatibles.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+El archivo predeterminado del {% data variables.product.prodname_codeql_workflow %} contiene una matriz de compilación que se llama `language`, la cual lista los lenguajes en tu repositorio que se han analizado. El {% data variables.product.prodname_codeql %} llena automáticamente esta matriz cuando agregas el {% data variables.product.prodname_code_scanning %} a un repositorio. Cuando se utiliza la matriz de `language` se optimiza a {% data variables.product.prodname_codeql %} para ejecutar cada análisis en paralelo. Te recomendamos que todos los flujos de trabajo adopten esta configuración debido a los beneficios de rendimiento que implica el paralelizar las compilaciones. Para obtener más información acerca de las matrices de compilación, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix.
+Si tu flujo de trabajo utiliza la matriz `language`, entonces {% data variables.product.prodname_codeql %} se codifica fijamente para analizar únicamente los lenguajes en dicha matriz. Para cambiar los lenguajes que quieres analizar, edita el valor de la variable de la matriz. Puedes eliminar un lenguaje para que no se analice, o puedes agregar alguno que no estuviera presente en el repositorio cuando se configuró el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se configuró el {% data variables.product.prodname_code_scanning %}, y luego quieres agregar código de Python, entonces necesitarás agregar `python` a la matriz.
 
 ```yaml
 jobs:
@@ -154,7 +169,7 @@ jobs:
         language: ['javascript', 'python']
 ```
 
-If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action.
+Si tu flujo de trabajo no contiene una matriz que se llame `language`, entonces {% data variables.product.prodname_codeql %} se configurará para ejecutar un análisis secuencialmente. Si no especificas los lenguajes en los flujos de trabajo, {% data variables.product.prodname_codeql %} detectará e intentará analizar cualquier lenguaje compatible que haya en el repositorio. Si quieres elegir qué lenguajes analizar sin utilizar una matriz, puedes utilizar el parámetro `languages` en la acción de `init`.
 
 ```yaml
 - uses: github/codeql-action/init@v1
@@ -162,53 +177,85 @@ If your workflow does not contain a matrix called `language`, then {% data varia
     languages: cpp, csharp, python
 ```
 {% if currentVersion == "free-pro-team@latest" %}
-### Analyzing Python dependencies
+### Analizar las dependencias de Python
 
-For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
+Para los ejecutores hospedados en GitHub que utilicen solo Linux, el {% data variables.product.prodname_codeql_workflow %} intentarà instalar automàticamente las dependencias de Python para dar màs resultados para el anàlisis de CodeQL. Puedes controlar este comportamiento si especificas el paràmetro `setup-python-dependencies` para la acciòn que el paso "Initialize CodeQL" llama. Predeterminadamente, este paràmetro se configura como `true`:
 
--  If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies.
+-  Si el repositorio contiene còdigo escrito en Python, el paso "Initialize CodeQL" instala las dependencias necesarias en el ejecutor hospedado en GitHub. Si la instalaciòn automàtica es exitosa, la acciòn tambièn configura la variable de ambiente `CODEQL_PYTHON` en el archivo ejecutable de Python que incluye las dependencias.
 
-- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete.
+- Si el repositorio no tiene ninguna dependencia de Python o si las dependencias se especifican en una forma inesperada, obtendràs una advertencia y la acciòn seguirà con los jobs restantes. La acciòn puede ejecutarse exitosamente aùn cuando existan problemas para interpretar las dependencias, pero los resultados podrìan estar incompletos.
 
-Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract:
+Como alternativa, puedes instalar las dependencias de Python manualmente en cualquier sistema operativo. Necesitaràs agregar a `setup-python-dependencies` y configurarlo como `false`, asì como configurar `CODEQL_PYTHON` para el ejecutable de Python que incluye las dependencias, tal como se muestra en este extracto de flujo de trabajo:
 
 ```yaml
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
-### Running additional queries
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. Por ejemplo:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. Para obtener más información, consulta la sección "[Soporte de SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)".
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
+### Ejecutar consultas adicionales
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
+Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. Si las consultas están en un repositorio privado, utiliza el parámetro `external-repository-token` para especificar un token que tenga acceso a este.
 
 {% raw %}
 ``` yaml
@@ -220,13 +267,13 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 ```
 {% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+También puedes ejecutar conjuntos de consultas adicionales si los especificas en un archivo de configuración. Los conjuntos de consultas son colecciones de consultas que a menudo se agrupan por propósito o lenguaje.
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+Puedes ejecutar consultas adicionales si las especificas en un archivo de configuración. So quieres ejecutar el conjunto combinado de consultas adicionales que se especifica aquí y en el archivo de configuración, agrega como prefijo el valor `queries` en el flujo de trabajo con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)".
 
-In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
+En el siguiente ejemplo, el símbolo `+` se asegura de que las consultas adicionales especificadas se utilicen en conjunto con cualquier otra consulta que se especifique en el archivo de configuración referenciado.
 
 {% raw %}
 ``` yaml
@@ -238,11 +285,11 @@ In the following example, the `+` symbol ensures that the specified additional q
 ```
 {% endraw %}
 
-### Using a custom configuration file
+### Utilizar una herramienta de escaneo de código de terceros
 
-As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
+Como alternativa para especificar qué consultas se ejecutarán en un archivo de flujo de trabajo, puedes hacer esto en un archivo de configuración diferente. También puedes utilizar un archivo de configuración para inhabilitar las consultas predeterminadas y para especificar qué directorios escanear durante el análisis.
 
-In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acción `init` para especificar la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _./.github/codeql/codeql-config.yml_.
 
 ``` yaml
 - uses: github/codeql-action/init@v1
@@ -252,7 +299,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp
 
 {% data reusables.code-scanning.custom-configuration-file %}
 
-If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository.
+El archivo de configuración se ubica en un repositorio privado externo, utiliza el parámetro `external-repository-token` de la acción `init` para especificar un token que tenga acceso al repositorio privado.
 
 {% raw %}
 ```yaml
@@ -262,11 +309,11 @@ with:
 ```
 {% endraw %}
 
-The settings in the configuration file are written in YAML format.
+Los ajustes en el archivo de configuración se escriben en formato YAML.
 
-#### Specifying additional queries
+#### Especificar consultas adicionales
 
-You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
+Puedes especificar consultas adicionales en una matriz de `queries`. Cada elemento de la matriz contiene un parámetro de `uses` con un valor que identifica un archivo de consulta simple, un directorio que contiene los archivos de consulta, o un archivo de suite de definiciones de una consulta.
 
 ``` yaml
 queries:
@@ -275,17 +322,17 @@ queries:
   - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls
 ```
 
-Optionally, you can give each array element a name, as shown in the example configuration files below.
+Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración.
 
-For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
+Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)".
 
-#### Disabling the default queries
+#### Inhabilitar las consultas predeterminadas
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+Si solo quieres ejecutar consultas personalizadas, puedes inhabilitar las consultas de seguridad predeterminadas si agregas `disable-default-queries: true` a tu archivo de configuración.
 
-#### Specifying directories to scan
+#### Especificar directorios para escanear
 
-For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
+Para los lenguajes interpretados compatibles con {% data variables.product.prodname_codeql %} (Python y JavaScript/TypeScript), puedes restringir el {% data variables.product.prodname_code_scanning %} para los archivos que estén en directorios específicos si agregas una matriz de `paths` al archivo de configuración. Puedes excluir del análisis los archivos en los directorios específicos si agregas un arreglo de `paths-ignore`.
 
 ``` yaml
 paths:
@@ -297,27 +344,28 @@ paths-ignore:
 
 {% note %}
 
-**Note**:
+**Nota**:
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* Las palabras clave `paths` y `paths-ignore` que se utilizan en el contexto del archivo de configuración del {% data variables.product.prodname_code_scanning %} no deben confundirse con las mismas palabras clave cuando se utilizan para `on.<push|pull_request>.paths` en un flujo de trabajo. Cuando se tulizan para modificar `on.<push|pull_request>` en un flujo de trabajo, éstas determinan si las acciones se ejecutarán cuando alguien modifique el código en los directorios especificados. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)".
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por ejemplo, `foo/**`, `**/foo`, y `foo/**/bar` son todas sintaxis permitidas, pero `**foo` no lo es. Sin embargo, puedes utilizar asteriscos sencillos con otros caracteres, tal como se muestra en el ejemplo. Tendrás que poner entre comillas todo lo que contenga un caracter de `*`.
 
 {% endnote %}
 
-For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+Para los lenguajes compilados, si quieres limitar el {% data variables.product.prodname_code_scanning %} para directorios específicos en tu proyecto, debes especificar los pasos de compilación adecuados en el flujo de trabajo. Los comandos que necesites utilizar para excluir un directorio de la compilación dependerán en tu sistema de compilación. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+Puedes analizar rápidamente partes pequeñas de un monorepo cuando modificas el código en directorios específicos. Necesitarás tanto excluir los directorios en tus pasos de compilación como utilizar las palabras clave `paths-ignore` y `paths` para [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) en tu archivo de flujo de trabajo.
 
-#### Example configuration files
+#### Ejemplos de archivos de configuración
 
 {% data reusables.code-scanning.example-configuration-files %}
 
-### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+### Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados
 
 {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)."
+{% data reusables.code-scanning.autobuild-add-build-steps %} Para obtener más información sobre cómo configurar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} para los lenguajes compilados, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)".
 
-### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}.
 
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
+{% data variables.product.prodname_dotcom %} puede mostrar los datos de análisis de código que se generan externamente con una herramienta de terceros. Puedes mostrar el análisis de código de una herramienta de terceros en {{ site.data.variables.product.prodname_dotcom }} su agregas la acción `upload-sarif` en tu flujo de trabajo. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)".
diff --git a/translations/es-ES/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..d523d19b39
--- /dev/null
+++ b/translations/es-ES/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,203 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configuring CodeQL runner
+intro: 'Puedes configurar la forma en la que {% data variables.product.prodname_codeql_runner %} escanea el código en tu proyecto y en la que carga los resultados a {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Acerca de configurar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC
+
+Para integrar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC, puedes utilizar el {% data variables.product.prodname_codeql_runner %}. Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)".
+
+En general, se invoca el {% data variables.product.prodname_codeql_runner %} de la siguiente manera.
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` depende de si descargaste el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC. `codeql-runner-OS` depende del sistema operativo que utilices. Hay tres versiones del {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, y `codeql-runner-win`, para sistemas Linux, macOS y Windows respectivamente.
+
+Para personalizar la forma en la que el {% data variables.product.prodname_codeql_runner %} escanea tu código, puedes utilizar marcadores, tales como `--languages` y `--queries`,o puedes especificar configuraciones personalizadas en un archivo de configuración por separado.
+
+### Escanear las solicitudes de extracción
+
+El escanear el código cada que se crea una solicitud de cambios previene que los desarrolladores introduzcan vulnerabilidades y errores nuevos a este.
+
+Para escanear una solicitud de cambios, ejecuta el comando `analyze` y utiliza el marcador `--ref` para especificar la solicitud de cambios. La referencia es `refs/pull/<PR-number>/head` o `refs/pull/<PR-number>/merge`, dependiendo de si seleccionaste la confirmación HEAD de la rama de la solicitud de cambios o una confirmación de fusión con la rama base.
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**Nota**: Si analizas código con una herramienta de terceros y quieres que los resultados aparezcan como verificaciones de solicitudes de cambios, debes ejecutar el comando `upload` y utilizar el marcador `--ref` para especificar la solicitud de cambios en vez de la rama. La referencia es `refs/pull/<PR-number>/head` o `refs/pull/<PR-number>/merge`.
+
+{% endnote %}
+
+### Invalidar la detección automática de lenguaje
+
+El {% data variables.product.prodname_codeql_runner %} detecta automáticamente y escanea el código que se ha escrito en los lenguajes compatibles.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+Para anular la detección automática de lenguajes, ejecuta el comando `init` con el marcador `--languages`, seguido de una lista separada por comas de las palabras clave de los lenguajes. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### Ejecutar consultas adicionales
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+Para agregar una o más consultas, pasa una lista separada por comas de las rutas al marcador `--queries` del comando `init`. También puedes especificar consultas adicionales en un archivo de configuración.
+
+Si también estás usando un archivo de configuración para los ajustes personalizados y también estás especificando consultas adicionales con el marcador de `--queries`, el {% data variables.product.prodname_codeql_runner %} utilizará consultas adicionales que se especifican con el marcador <nobr>`--queries`</nobr> en vez de con cualquier otro en el archivo de configuración. Si quieres ejecutar el conjunto combinado de consultas adicionales que se especifican con el marcador y en el archivo de configuración, usa un prefijo en el valor que se pasa a <nobr>`--queries`</nobr> con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)".
+
+En el siguiente ejemplo, el símbolo `+` garantiza que el {% data variables.product.prodname_codeql_runner %} utilizará consultas adicionales junto con cualquier otra consulta que se especifique en el archivo de configuración referenciado.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### Utilizar una herramienta de escaneo de código de terceros
+
+En vez de pasar información adicional a los comandos de {% data variables.product.prodname_codeql_runner %}, puedes especificar ajustes personalizados en un archivo de configuración por separado.
+
+El archivo de configuración es un archivo de YAML. Utiliza una sintaxis similar a aquella del flujo de trabajo para {% data variables.product.prodname_actions %}, de acuerdo como se ilustra en los siguientes ejemplos. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
+
+Utiliza el marcador `--config-file` del comando `init` para especificar el archivo de configuración. El valor de <nobr>`--config-file`</nobr> es la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _.github/codeql/codeql-config.yml_.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### Ejemplos de archivos de configuración
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados
+
+Para los lenguajes C/C++, C#, y Java, {% data variables.product.prodname_codeql %} compila el código antes de analizarlo. {% data reusables.code-scanning.analyze-go %}
+
+Para varios sistemas de compilación comunes, el {% data variables.product.prodname_codeql_runner %} puede compilar el código automáticamente. Para intentar compilar el código automáticamente, ejecuta `autobuild` entre los pasos de `init` y `analyze`. Nota que, si tu repositorio necesita una versión específica de una herramienta de compilación, puede que necesites instalar dicha herramienta manualmente primero.
+
+El proceso de `autobuild` solo intenta siempre compilar _un_ solo lenguaje compilado para un repositorio. El lenguaje que se selecciona automáticamente para su análisis es aquél presente en más archivos. Si quieres elegir un lenguaje explícitamente, utiliza el marcador `--language` del comando `autobuild`.
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+Si el comando `autobuild` no puede compilar tu código, tú mismo puedes ejecutar los pasos de compilación entre los pasos de `init` y `analyze`. Para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)".
+
+### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}.
+
+Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} carga los resultados del {% data variables.product.prodname_code_scanning %} cuando ejecutas el comando `analyze`. También puedes cargar archivos de SARIF por separado si utilizas el comando `upload`.
+
+Una vez que hayas cargado los datos, {% data variables.product.prodname_dotcom %} mostrará las alertas en tu repositorio.
+- Si cargaste algo a una solicitud de cambios, por ejemplo `--ref refs/pull/42/merge` o `--ref refs/pull/42/head`, entonces los resultados aparecerán como alertas en una verificación de solicitud de cambios. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del escaneo de código en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
+- Si cargaste algo a la rama, por ejemplo `--ref refs/heads/my-branch`, entonces los resultados aparecerán en la pestaña de **Seguridad** de tu repositorio. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)".
+
+### Referencia de comandos de {% data variables.product.prodname_codeql_runner %}
+
+El {% data variables.product.prodname_codeql_runner %} es compatible con los siguientes comandos y marcadores.
+
+#### `init`
+
+Inicializa el {% data variables.product.prodname_codeql_runner %} y crea una base de datos de {% data variables.product.prodname_codeql %} para analizar cada lenguaje.
+
+| Marcador                         | Requerido | Valor de entrada                                                                                                                                                                                         |
+| -------------------------------- |:---------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repositorio`                  |     ✓     | Nombre del repositorio a inicializar.                                                                                                                                                                    |
+| `--github-url`                   |     ✓     | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio.                                                                                                     |
+| `--github-auth`                  |     ✓     | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal.                                                                                                           |
+| `--languages`                    |           | Lista separada por comas de los lenguajes a analizar. Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} detecta y analiza todos los lenguajes compatibles en el repositorio. |
+| `--queries`                      |           | Lista separada por comas de las consultas adicionales a ejecutar, adicionalmente a la suite predeterminada de consultas de seguridad.                                                                    |
+| `--config-file`                  |           | Ruta al archivo de configuración personalizado.                                                                                                                                                          |
+| `--codeql-path`                  |           | Ruta a una copia del CLI ejecutable de {% data variables.product.prodname_codeql %} a utilizar. Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} descarga una copia.        |
+| `--temp-dir`                     |           | Directorio donde se almacenan los archivos temporales. El predeterminado es `./codeql-runner`.                                                                                                           |
+| `--tools-dir`                    |           | Directorio donde las herramientas de {% data variables.product.prodname_codeql %} y otros archivos se almacenan entre ejecuciones. El predeterminado es un subdirectorio del directorio principal.       |
+| <nobr>`--checkout-path`</nobr> |           | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo.                                                                                                    |
+| `--debug`                        |           | Ninguno. Imprime una salida más verbosa.                                                                                                                                                                 |
+| `-h`, `--help`                   |           | Ninguno. Muestra la ayuda para el comando.                                                                                                                                                               |
+
+#### `autobuild`
+
+Intenta compilar el código para los lenguajes compilados de C/C++, C#, y Java. Para estos lenguajes, {% data variables.product.prodname_codeql %} compila el código antes de analizarlo. Ejecuta `autobuild` entre los pasos de `init` y `analyze`.
+
+| Marcador                    | Requerido | Valor de entrada                                                                                                                            |
+| --------------------------- |:---------:| ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--language`                |           | El lenguaje a compilar. Predeterminadamente, el {% data variables.product.prodname_codeql_runner %} compila el lenguaje con más archivos. |
+| <nobr>`--temp-dir`</nobr> |           | Directorio donde se almacenan los archivos temporales. El predeterminado es `./codeql-runner`.                                              |
+| `--debug`                   |           | Ninguno. Imprime una salida más verbosa.                                                                                                    |
+| `-h`, `--help`              |           | Ninguno. Muestra la ayuda para el comando.                                                                                                  |
+
+#### `analyze`
+
+Analiza el código en las bases de datos de {% data variables.product.prodname_codeql %} y carga los resultados a {% data variables.product.product_name %}.
+
+| Marcador                           | Requerido | Valor de entrada                                                                                                                                                                                                                                                                                                                    |
+| ---------------------------------- |:---------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repositorio`                    |     ✓     | Nombre del repositorio que se analizará.                                                                                                                                                                                                                                                                                            |
+| `--commit`                         |     ✓     | SHA de la confirmación que se analizará. En Git y en Azure DevOps, este corresponde al valor de `git rev-parse HEAD`. En Jenkins, este corresponde a `$GIT_COMMIT`.                                                                                                                                                                 |
+| `--ref`                            |     ✓     | Nombre de la referencia a analizar, por ejemplo `refs/heads/main` o `refs/pull/42/merge`. Tanto en Git como en Jenkins, esto corresponde al valor de `git symbolic-ref HEAD`. En Azure DevOps, esto corresponde a `$(Build.SourceBranch)`.                                                                                          |
+| `--github-url`                     |     ✓     | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio.                                                                                                                                                                                                                                |
+| `--github-auth`                    |     ✓     | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal.                                                                                                                                                                                                                                      |
+| <nobr>`--checkout-path`</nobr>   |           | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo.                                                                                                                                                                                                                               |
+| `--no-upload`                      |           | Ninguno. Impide que el {% data variables.product.prodname_codeql_runner %} cargue los resultados a {% data variables.product.product_name %}.                                                                                                                                                                                     |
+| `--output-dir`                     |           | Directorio en donde se almacenan los archivos SARIF de salida. El predeterminado está en el directorio de archivos temporales.                                                                                                                                                                                                      |
+| `--ram`                            |           | Cantidad de memoria a utilizar cuando ejecutes consultas. El valor predeterminado es utilizar toda la memoria disponible.                                                                                                                                                                                                           |
+| <nobr>`--no-add-snippets`</nobr> |           | Ninguno. Excluye los fragmentos de código de la salida de SARIF. |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |           | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |           | Cantidad de hilos a utilizar cuando se ejecutan las consultas. El valor predeterminado es utilizar todos los núcleos disponibles.                                                                                                                                                                                                   |
+| `--temp-dir`                       |           | Directorio donde se almacenan los archivos temporales. El predeterminado es `./codeql-runner`.                                                                                                                                                                                                                                      |
+| `--debug`                          |           | Ninguno. Imprime una salida más verbosa.                                                                                                                                                                                                                                                                                            |
+| `-h`, `--help`                     |           | Ninguno. Muestra la ayuda para el comando.                                                                                                                                                                                                                                                                                          |
+
+#### `cargar`
+
+Carga los archivos SARIF a {% data variables.product.product_name %}.
+
+{% note %}
+
+**Nota**: Si analizas el código con el ejecutor de CodeQL, el comando `analyze` carga los resultados de SARIF predeterminadamente. Puedes utilizar el comando `upload` para cargar los resultados SARIF que generaron otras herramientas.
+
+{% endnote %}
+
+| Marcador                         | Requerido | Valor de entrada                                                                                                                                                                                                                                |
+| -------------------------------- |:---------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   |     ✓     | El archivo SARIF a cargar, o un directorio que contiene varios archivos SARIF.                                                                                                                                                                  |
+| `--repositorio`                  |     ✓     | Nombre del repositorio que se analizó.                                                                                                                                                                                                          |
+| `--commit`                       |     ✓     | SHA de la confirmación que se analizó. En Git y en Azure DevOps, este corresponde al valor de `git rev-parse HEAD`. En Jenkins, este corresponde a `$GIT_COMMIT`.                                                                               |
+| `--ref`                          |     ✓     | Nombre de la referencia que se analizó, por ejemplo, `refs/heads/main` o `refs/pull/42/merge`. Tanto en Git como en Jenkins, esto corresponde al valor de `git symbolic-ref HEAD`. En Azure DevOps, esto corresponde a `$(Build.SourceBranch)`. |
+| `--github-url`                   |     ✓     | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio.                                                                                                                                            |
+| `--github-auth`                  |     ✓     | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal.                                                                                                                                                  |
+| <nobr>`--checkout-path`</nobr> |           | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo.                                                                                                                                           |
+| `--debug`                        |           | Ninguno. Imprime una salida más verbosa.                                                                                                                                                                                                        |
+| `-h`, `--help`                   |           | Ninguno. Muestra la ayuda para el comando.                                                                                                                                                                                                      |
diff --git a/translations/es-ES/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index e5e04023d2..06c57d3945 100644
--- a/translations/es-ES/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/es-ES/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/es-ES/content/code-security/secure-coding/index.md b/translations/es-ES/content/code-security/secure-coding/index.md
index bf71f670b6..c8a17da14a 100644
--- a/translations/es-ES/content/code-security/secure-coding/index.md
+++ b/translations/es-ES/content/code-security/secure-coding/index.md
@@ -1,7 +1,7 @@
 ---
 title: Encontrar errores y vulnerabilidades de seguridad en tu código
 shortTitle: Programación segura
-intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.'
+intro: 'Mantén tu código seguro utilizando el {% data variables.product.prodname_code_scanning %} para identificar y arreglar vulnerabilidades de seguridad potenciales y otros errores en tu código.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### Índice
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% topic_link_in_list /using-codeql-code-scanning-with-your-existing-ci-system %}
-    {% link_in_list /running-codeql-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-codeql-code-scanning-in-your-ci-system %}
-    {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md
index 713229cd35..5144cb383b 100644
--- a/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index fc7a85e7c4..c6cddcb366 100644
--- a/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
 title: Administrar las alertas del escaneo de código para tu repositorio
 shortTitle: Administrar alertas
-intro: 'Desde la vista de seguridad, puedes ver, arreglar, {% if currentVersion == "enterprise-server@2.22" %}o cerrar{% else %}descartar, o borrar{% endif %} las alertas para las vulnerabilidades potenciales o para los errores en el código de tus proyectos.'
+intro: 'Desde la vista de seguridad, puedes ver, corregir, descartar o borrar las alertas de las vulnerabilidades o errores potenciales en el código de tu proyecto.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca de las alertas de {% data variables.product.prodname_code_scanning %}
@@ -46,7 +48,7 @@ Necesitas permisos de escritura para ver un resumen de todas las alertas de un r
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
-1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %}
+1. Opcionalmente, utiliza los menús desplegables para filtrar las alertas. Por ejemplo, puedes filtrar por la herramienta que se utilizó para identificar las alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %}
 1. Debajo de "{% data variables.product.prodname_code_scanning_capc %}", da clic en la alerta que quisieras explorar.
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
   ![Resumen de alertas](/assets/images/help/repository/code-scanning-click-alert.png)
@@ -60,7 +62,7 @@ Necesitas permisos de escritura para ver un resumen de todas las alertas de un r
 
 Cualquiera con permisos de escritura en un repositorio puede arreglar una alerta si confirma una corrección en el código. Si el repositorio tiene programado un {% data variables.product.prodname_code_scanning %} para ejecutarse en las solicitudes de cambios, es mejor levantar una solicitud de cambios con tu corrección. Esto activará el análisis del {% data variables.product.prodname_code_scanning %} en los cambios y probará que tu arreglo no introduciría ningún problema nuevo. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" y "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
 
-Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista de "Cerrados" muestra las alertas solucionadas y aquellas que los usuarios {% if currentVersion == "enterprise-server@2.22" %}cerraron{% else %}descartaron{% endif %}.
+Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista de "Cerrado" muestra las alertas arregladas y las que los usuarios han descartado.
 
 Las alertas pueden arreglarse en una rama pero no en alguna otra. Puedes utilizar el menú desplegable de "Rama", en el resumen de las alertas, para verificar si una alerta se arregló en una rama en particular.
 
@@ -70,14 +72,6 @@ Las alertas pueden arreglarse en una rama pero no en alguna otra. Puedes utiliza
 ![Filtrar alertas por rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### Cerrar una alerta
-
-Cerrar una alerta es una forma de resolverla si no crees que necesita un arreglo. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### Descartar o borrar las alertas
 
 Hay dos formas de cerrar una alerta. Puedes arreglar el problema en el código, o puedes descartar la alerta. Como alternativa, si tienes permisos adminsitrativos en el repositorio, puedes borrar las alertas. Borrar las alertas es útil en situaciones en donde configuraste una herramienta del {% data variables.product.prodname_code_scanning %} y luego decidiste eliminarla, o donde configuraste el análisis de {% data variables.product.prodname_codeql %} con un conjunto más grande de consultas que quieres seguir utilizando y después eliminaste algunas de ellas de la herramienta. En ambos casos, el borrar las alertas te permite limpiar tus resultados del {% data variables.product.prodname_code_scanning %}. Puedes borrar las alertas de la lista de resumen dentro de la pestaña de **Seguridad**.
@@ -101,20 +95,9 @@ Cuando borras una alerta:
 
 Para descartar o borrar una alerta:
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. Selecciona el menú desplegable de **Cerrar** y da clic en una razón para cerrar la alerta.    
-   ![Elegir una razón apra cerrar la alerta a través del menú desplegable de "Cerrar"](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. Si tienes permisos administrativos en el repositorio y quieres borrar las alertas para esta herramienta del {% data variables.product.prodname_code_scanning %}, selecciona algunas o todas las casillas de verificación y da clic en **Borrar**.
 
    ![Borrar alertas](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,8 +128,6 @@ Para descartar o borrar una alerta:
 
 Si un proyecto tiene varias alertas que quieras descartar por la misma razón, puedes descartarlas por lote desde el resúmen de las alertas. Habitualmente quieres filtrar la lista y luego descartar todas las alertas coincidentes. Por ejemplo, puede que quieras descartar todas las alertas actuales del proyecto que se hayan etiquetado para una vulnerabilidad de Enumeración de Debilidades (CWE, por sus siglas en inglés) Común en particular.
 
-{% endif %}
-
 ### Leer más
 
 - "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/es-ES/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..ca7c455a46
--- /dev/null
+++ b/translations/es-ES/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Running CodeQL CLI in your CI system
+shortTitle: Running CodeQL CLI
+intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para llevar a cabo el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en un sistema de integración contínua de terceros.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Acerca de {% data variables.product.prodname_codeql_cli %}
+
+Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para ejecutar el {% data variables.product.prodname_code_scanning %} en el código que estás procesando en un sistema de integración continua (IC) de terceros. {% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)".
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_codeql_runner %} in your CI system, or {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% note %}
+
+**Note:** {% if currentVersion == "free-pro-team@latest" %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% endnote %}
+
+### Descargar el {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. Por ejemplo:
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. Para obtener más información, consulta las secciones "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" y "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> opción.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opción
+    </th>
+    
+    <th align="center">
+      Requerido
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Ejemplo básico
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opción
+    </th>
+    
+    <th align="center">
+      Requerido
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. Para obtener más información, consulta la sección "<a href="/code-security/secure-coding/sarif-support-for-code-scanning">Soporte de SARIF para {% data variables.product.prodname_code_scanning %}</a>".
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Ejemplo básico
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opción
+    </th>
+    
+    <th align="center">
+      Requerido
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. Para obtener más información, consulta la sección "<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">Administrar la configuración de seguridad y análisis para tu repositorio</a>".
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Ejemplo básico
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### Leer más
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/es-ES/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index 423819f336..83ef507c2c 100644
--- a/translations/es-ES/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/es-ES/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -13,13 +13,19 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca del {% data variables.product.prodname_code_scanning %} con una compilación en contenedor
 
 Si estás configurando el {% data variables.product.prodname_code_scanning %} para un lenguaje compilado, y estás compilando el código en un ambiente contenido, el análisis podría fallar con el mensaje de error "No source code was seen during the build". Esto indica que {% data variables.product.prodname_codeql %} no fue capaz de monitorear tu código mientras se compilaba.
 
-Debes ejecutar {% data variables.product.prodname_codeql %} en el mismo contenedor en donde compilaste tu código. Esto aplica ya sea que estés utilizando el {% data variables.product.prodname_codeql_runner %} o {% data variables.product.prodname_actions %}. Si estás utilizando el {% data variables.product.prodname_codeql_runner %}, ejecútalo en el contenedor en donde se compila tu código. Para obtener más información acerca del {% data variables.product.prodname_codeql_runner %}, consulta la sección "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)". Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)".
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)".
+{% else %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. Si estás utilizando {% data variables.product.prodname_actions %}, configura tu flujo de trabajo para ejecutar todas las acciones en el mismo contenedor. Para obtener más información, consulta la sección "[Ejemplo de flujo de trabajo](#example-workflow)".
+{% endif %}
 
 ### Dependencias
 
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/es-ES/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..5a69cf22af
--- /dev/null
+++ b/translations/es-ES/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Running CodeQL runner in your CI system
+shortTitle: Running CodeQL runner
+intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_runner %} para llevar a cabo el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en un sistema de integración contínua de terceros.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Acerca de {% data variables.product.prodname_codeql_runner %}
+
+The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)".
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. The runner is more complex and less forgiving to set up than the CLI, and is recommended only if you need its capability to analyze multiple compiled languages with a single build, or to integrate with complex build processes. For more information, see "[About CodeQL code scanning in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
+
+El {% data variables.product.prodname_codeql_runner %} es una herramienta de línea de comandos que ejecuta un análisis de {% data variables.product.prodname_codeql %} en un control de un repositorio de {% data variables.product.prodname_dotcom %}. Agregas el ejecutor a tu sistema de terceros y luego lo llamas para que analice el código y cargue los resultados a {% data variables.product.product_name %}. Estos resultados se muestran como alertas del {% data variables.product.prodname_code_scanning %} en el repositorio.
+
+{% note %}
+
+**Nota:**
+{% if currentVersion == "free-pro-team@latest" %}
+* El {% data variables.product.prodname_codeql_runner %} utiliza el CLI de {% data variables.product.prodname_codeql %} para analizar el código y, por lo tanto, tiene las mismas condiciones de licencia. Se puede utilizar gratuitamente en los repositorios que mantiene {% data variables.product.prodname_dotcom_the_website %}, y está disponible para utilizarse en aquellos que pertenecen a los clientes con una licencia de {% data variables.product.prodname_advanced_security %}. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
+{% else %}
+* El {% data variables.product.prodname_codeql_runner %} se encuentra disponible para los clientes con una licencia de {% data variables.product.prodname_advanced_security %}.
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* El {% data variables.product.prodname_codeql_runner %} no debe confundirse con el CLI de {% data variables.product.prodname_codeql %}. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. Para obtener más información, consulta "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
+{% endif %}
+{% endnote %}
+
+### Descargar el {% data variables.product.prodname_codeql_runner %}
+
+Puedes descargar el {% data variables.product.prodname_codeql_runner %} desde https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. En algunos sistemas operativos, puede que necesites cambiar permisos para el archivo de descarga antes de que lo puedas ejecutar.
+
+En Linux:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+En macOS:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+En Windows, el archivo `codeql-runner-win.exe` habitualmente no necesita que se hagan cambios a los permisos.
+
+### Agregar el {% data variables.product.prodname_codeql_runner %} a tu sistema de IC
+
+Una vez que descargas el {% data variables.product.prodname_codeql_runner %} y verificas que puede ejecutarse, debes poner el ejecutor disponible para cada servidor de IC que pretendas utilizar para el {% data variables.product.prodname_code_scanning %}. Por ejemplo, podrías configurar cada servidor para que copie el ejecutor desde una ubicación interna y central. Como alternativa, puedes utilizar la API de REST para obtener el ejecutor directamente de {% data variables.product.prodname_dotcom %}, por ejemplo:
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+Además, cada servidor de IC necesitará también:
+
+- Un token de acceso personal o de {% data variables.product.prodname_github_app %} para que utilice el {% data variables.product.prodname_codeql_runner %}. Debes utilizar un token de acceso con el alcance `repo`, o una {% data variables.product.prodname_github_app %} con el permiso de escritura `security_events`, y los permisos de lectura `metadata` y `contents`. Para obtener más información, consulta las secciones "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" y "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
+- Acceso al paquete de {% data variables.product.prodname_codeql %} asociado con este lanzamiento del {% data variables.product.prodname_codeql_runner %}. Este paquete contiene consultas y bibliotecas necesarias para el análisis de {% data variables.product.prodname_codeql %}, adicionado con el CLI de {% data variables.product.prodname_codeql %}, el cual utiliza internamente el ejecutor. Para obtener más información, consulta la sección "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
+
+Las opciones para proporcionar acceso al paquete de {% data variables.product.prodname_codeql %} son:
+
+1. Permite que los servidores de IC accedan a https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action para que el {% data variables.product.prodname_codeql_runner %} pueda descargar el paquete automáticamente.
+1. Descarga/extrae manualmente el paquete, almacénalo con otros recursos centrales y utiliza el <nobr>`--codeql-path`</nobr> para especificar la ubicación del paquete en los llamados para inicializar el {% data variables.product.prodname_codeql_runner %}.
+
+### Llamar al {% data variables.product.prodname_codeql_runner %}
+
+Debes llamar al {% data variables.product.prodname_codeql_runner %} desde la ubicación de verificación del repositorio que quieres analizar. Los dos comandos principales son:
+
+1. `init` que se requiere para inicializar el ejecutor y para crear una base de datos de {% data variables.product.prodname_codeql %} para que se analice cada lenguaje. Estas bases de datos se llenan y analizan mediante comandos subsecuentes.
+1. `analyze` que se requiere para llenar las bases de datos de {% data variables.product.prodname_codeql %}, analizarlas y cargar los resultados a {% data variables.product.product_name %}.
+
+Para ambos comandos, debes especificar la URL de {% data variables.product.product_name %}, el *PROPIETARIO/NOMBRE* del repositorio, y el token de {% data variables.product.prodname_github_apps %} o de acceso personal a utilizar para la autenticación. También necesitas especificar la ubicación del paquete de CodeQL, a menos de que el servidor de IC tenga acceso para descargarlo directamente del repositorio de `github/codeql-action`.
+
+Puedes configurar la ubicación en la que {% data variables.product.prodname_codeql_runner %} almacenará el paquete de CodeQL para un análisis futuro un un servidor utilizando el marcador <nobr>`--tools-dir`</nobr> , así como en dónde almacena archivos temporales utilizando el marcador <nobr>`--temp-dir`</nobr>.
+
+Para ver la referencia de línea de comandos para el ejecutor, utiliza el marcador `-h`. Por ejemplo, para listar todos los comandos, ejecuta: `codeql-runner-OS -h`, o para listar todos los marcadores disponibles para el comando `init`, ejecuta: `codeql-runner-OS init -h` (en donde el `OS` variará de acuerdo con el ejecutable que estés utilizando). Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)".
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### Ejemplo básico
+
+Este ejemplo ejecuta un análisis de {% data variables.product.prodname_codeql %} en un servidor de IC con Linux para el repositorio de `octo-org/example-repo` en `{% data variables.command_line.git_url_example %}`. El proceso es muy simple, ya que el repositorio contiene únicamente los lenguajes que puede analizar {% data variables.product.prodname_codeql %} directamente, sin que se tenga que compilar (es decir, Go, JavaScript, Python, y TypeScript).
+
+En este ejemplo, el servidor tiene acceso para descargar el paquete de {% data variables.product.prodname_codeql %} directamente desde el repositorio `github/codeql-action`, así que no hay necesidad de utilizar el marcador `--codeql-path`.
+
+1. Verifica el repositorio a analizar.
+1. Posiciónate en el directorio donde se seleccionó el repositorio.
+1. Inicializa el {% data variables.product.prodname_codeql_runner %} y crea bases de datos de {% data variables.product.prodname_codeql %} para los lenguajes detectados.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### Ejemplo de lenguaje compilado
+
+Este ejemplo es similar al anterior, sin embargo, esta vez el repositorio tiene código en C/C++, C#, o Java. Para crear una base de datos de {% data variables.product.prodname_codeql %} para estos lenguajes, el CLI necesita monitorear la compilación. Al final del proceso de inicialización, el ejecutor reportará el comando que necesitas configurar en el ambiente antes de compilar el código. Necesitas ejecutar este comando antes de llamar al proceso normal de compilación de IC y luego ejecutar el comando `analyze`.
+
+1. Verifica el repositorio a analizar.
+1. Posiciónate en el directorio donde se seleccionó el repositorio.
+1. Inicializa el {% data variables.product.prodname_codeql_runner %} y crea bases de datos de {% data variables.product.prodname_codeql %} para los lenguajes detectados.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. Proporciona el script que generó la acción `init` para configurar el ambiente para monitorear la compilación. Toma en cuenta el primer punto y espacio en el siguiente extracto de código.
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. Compila el código. En macOS, necesitarás agregar un prefijo al comando de la compilación con la variable de ambiente `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**Nota:** Si utilizas una compilación que usa contenedores, necesitarás ejecutar el {% data variables.product.prodname_codeql_runner %} en el contenedor donde toma lugar tu tarea de compilaión.
+
+{% endnote %}
+
+### Leer más
+
+- "[Configurar el {% data variables.product.prodname_codeql_runner %} en tu sistema](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[Solucionar problemas del {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
diff --git a/translations/es-ES/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index d8222ae702..7448305a4e 100644
--- a/translations/es-ES/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/es-ES/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: Soporte de SARIF para escaneo de código
 shortTitle: Soporte de SARIF
 intro: 'Para mostrar los resultados de una herramienta de análisis estático de terceros en tu repositorio en {% data variables.product.prodname_dotcom %}, necesitas que éstos se almacenen en un archivo SARIF que sea compatible con un subconjunto del modelo de JSON para SARIF 2.1.0 para el {% data variables.product.prodname_code_scanning %}. Si utilizas el motor de análisis estático predeterminado de {% data variables.product.prodname_codeql %}, tus resultados se mostrarán automáticamente en tu repositorio de {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca del soporte de SARIF
@@ -22,7 +25,15 @@ SARIF (Formato de Intercambio de Resultados de Análisis Estático, por sus sigl
 
 Para cargar un archivo SARIF desde un motor de análisis estático de código desde un tercero, necesitaras asegurarte de que los archivos cargados utilicen la versión SARIF 2.1.0. {% data variables.product.prodname_dotcom %} analizará el archivo SARIF y mostrará las alertas utilizando los resultados en tu repositorio como parte de la experiencia del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)". Para obtener más información acerca del modelo SARIF 2.1.0, consulta [`sari-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará cuando cargues el archivo SARIF utilizando {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} para un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" o "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)".
+Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará cuando cargues el archivo SARIF utilizando {% data variables.product.prodname_actions %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
 
 {% data variables.product.prodname_dotcom %} utiliza propiedades en el archivo SARIF para mostrar alertas. Por ejemplo, la `shortDescription` y `fullDescription` aparecen hasta arriba de una alerta de {% data variables.product.prodname_code_scanning %}. La `location` permite a {% data variables.product.prodname_dotcom %} mostrar anotaciones en tu archivo de código. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
 
@@ -122,6 +133,45 @@ Una ubicación dentro de un artefacto de programación, tal como un archivo en e
 | `region.endLine`       | **Requerido.** El número de línea de el último caracter en la región.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
 | `region.endColumn`     | **Requerido.** El número de columna del caracter que sigue al final de la región.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| Nombre | Descripción                                                                                                                                                                                                                           |
+| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`   | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | categoría         | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 01-02-2021            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
+
 ### Ejemplos de archivo de salida SARIF
 
 Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles y los valores de ejemplo.
@@ -130,7 +180,6 @@ Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles
 
 Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedades mínimas requeridas para que los resultados de {% data variables.product.prodname_code_scanning %} funcionen como se espera. Si eliminas cualquier propiedad u omites valores, estos datos no se mostrarán correctamente ni se sincronizarán en {% data variables.product.prodname_dotcom %}.
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedad
 
 Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}.
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propie
   ]
 }
 ```
+{% endif %}
diff --git a/translations/es-ES/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index 733859ef9b..b4f2c85801 100644
--- a/translations/es-ES/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/es-ES/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -14,13 +14,15 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca de los resultados del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios
 
 En los repositorios donde se configura el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambios, éste verificará el código en dicha solicitud. Predeterminadamente, esto se limita a solicitudes de cambios que apuntan a la rama predeterminada, pero puedes cambiar esta configuración dentro de {% data variables.product.prodname_actions %} o en un sistema de IC/EC de terceros. Si el fusionar los cambios puede introducir alertas nuevas de {% data variables.product.prodname_code_scanning %} a la rama destino, éstas se reportarán como resultados de verificación en la solicitud de cambios. Las alertas también se muestran como anotaciones en la pestaña de **Archivos que cambiaron** de la solicitud de cambios. Si tienes permisos de escritura para el repositorio, puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} existente en la pestaña de **Seguridad**. Para obtener más información sobre las alertas de los repositorios, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
 
-Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. Si tu solicitud de cambios apunta a una rama protegida que utiliza el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces debes ya sea arreglar o {% if currentVersion == "enterprise-server@2.22" %}cerrar{% else %}descartar{% endif %} todas las alertas de error antes de que se pueda fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
+Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. Si tu solicitud de cambios apunta a una rama protegida que utiliza el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces debes ya sea arreglar o descartar todas las alertas de error antes de que se pueda fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
 
 ![Verificación fallida del {% data variables.product.prodname_code_scanning %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -44,18 +46,10 @@ En la vista detallada de una alerta, algunas herramientas del {% data variables.
 
 ![Descripción de alerta y enlace para mostrar más información](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolver{% else %}Arreglar{% endif %} una alerta en tu solicitud de cambios
+### Arreglar una alerta en tu solicitud de cambios
 
 Cualquiera con acceso de subida a una solicitud de cambios puede arreglar una alerta del {% data variables.product.prodname_code_scanning %}, la cual se identifique en dicha solicitud. Si confirmas cambios en la solicitud de extracción, esto activará una ejecución nueva de las verificaciones de dicha solicitud. Si tus cambios arreglan el problema, la alerta se cierra y la anotación se elimina.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-Si no crees que alguna alerta deba arreglarse, los usuarios con permisos de escritura pueden cerrarla manualmente. {% data reusables.code-scanning.close-alert-examples %} El botón de **Cerrar** se encuentra disponible en las anotaciones y en la vista de alertas si tienes permisos de escritura en el repositorio.
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 ### Descartar una alerta en tu solicitud de cambios
 
 Una forma alterna de cerrar una alerta es descartarla. Puedes descartar una alerta si no crees que necesite arreglarse. {% data reusables.code-scanning.close-alert-examples %} Si tienes permisos de escritura en el repositorio, el botón de **Descartar** está disponible en las anotaciones de código y en el resumen de alertas. Cuando das clic en **Descartar** se te pedirá elegir una razón para cerrar la alerta.
@@ -67,5 +61,3 @@ Una forma alterna de cerrar una alerta es descartarla. Puedes descartar una aler
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 Para obtener más información acerca de descartar alertas, consulta la sección "[Administrar alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)".
-
-{% endif %}
diff --git a/translations/es-ES/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..696b7b62ef
--- /dev/null
+++ b/translations/es-ES/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshooting CodeQL runner
+intro: 'Si estás teniendo problemas con el {% data variables.product.prodname_codeql_runner %}, puedes solucionarlos si utilizas estos tips.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### El comando `init` tarda demasiado
+
+Antes de que el {% data variables.product.prodname_codeql_runner %} pueda compilar y analizar código, necesita tener acceso al paquete de {% data variables.product.prodname_codeql %}, el cual contiene el CLI y las bibliotecas de {% data variables.product.prodname_codeql %}.
+
+Cuando utilizas el {% data variables.product.prodname_codeql_runner %} por primera vez en tu máquina, el comando `init` descargará el paquete de {% data variables.product.prodname_codeql %} a tu máquina. Esta descarga puede demorar algunos minutos. El paquete de {% data variables.product.prodname_codeql %} se guarda en el caché entre las ejecuciones, así que si utilizas el {% data variables.product.prodname_codeql_runner %} nuevamente en la misma máquina, no descargará el paquete de {% data variables.product.prodname_codeql %} nuevamente.
+
+Para evitar esta descarga automática, puedes descargar manualmente el paquete de {% data variables.product.prodname_codeql %} a tu máquina ye specifica la ruta utilizando el marcador de `--codeql-path` del comando `init`.
+
+### No se encontró código durante la compilación
+
+Si el comando `analyze` para el {% data variables.product.prodname_codeql_runner %} falla con un error de `No source code was seen during the build`, esto indica que {% data variables.product.prodname_codeql %} no pudo monitorear tu código. Hay muchas razones que podrían explicar esta falla.
+
+1. La detección automática del lenguaje identificó un lenguaje compatible, pero no hay código analizable en dicho lenguaje dentro del repositorio. Un ejemplo típico es cuando nuestro servicio de detección de lenguaje encuentra un archivo que se asocia con un lenguaje de programación específico como un archivo `.h`, o `.gyp`, pero no existe el código ejecutable correspondiente a dicho lenguaje en el repositorio. Para resolver el problema, puedes definir manualmente los lenguajes que quieres analizar si utilizas el marcador `--languages` del comando `init`. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)".
+
+1. Estás analizando un lenguaje compilado sin utilizar el comando `autobuild` y ejecutaste los pasos de compilación después del paso `init`. For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the build process. El comando `init` genera instrucciones de cómo exportar las variables de ambiente requeridas, así que puedes copiar y ejecutar el script después de que has ejecutado el comando `init`.
+   - En macOS y Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - En Windows, utilizando el shell de comandos (`cmd`) o un archivo de lote (`.bat`):
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - En Windows, utilizando PowerShell:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   Las variables de ambiente también se almacenan en el archivo `codeql-runner/codeql-env.json`. Este archivo contiene solo un objeto de JSON que mapea las claves de variable de ambiente a valores. Si no puedes ejecutar el script que generó el comando `init`, entonces puedes utilizar los datos en formato JSON.
+
+   {% note %}
+
+   **Nota:** Si utilizaste el marcador `--temp-dir` flag del comando `init` para especificar un directorio personalizado para los archivos temporales, la ruta hacia los archivos de `codeql-env` podría ser diferente.
+
+   {% endnote %}
+
+1. Estás analizando un lenguaje compilado en macOS sin utilizar el comando `autobuild` y ejecutas los pasos de compilación tú mismo después del paso `init`. Si está habilitada la SIP (Protección Integral del Sistema, por sus siglas en inglés), que es lo predeterminado en las versiones más recientes de OSX, el análisis podría fallar. Para arreglar esto, usa un prefijo en el comando de la compilación con la variable de ambiente `$CODEQL_RUNNER`. Por ejemplo, si tu comando de compilación es `cmd arg1 arg2`, debes ejecutar `$CODEQL_RUNNER cmd arg1 arg2`.
+
+1. El código se compila en un contenedor o en una máquina independiente. Si utilizas una compilación que ya esté en un contenedor o si terciarizas la compilación a otra máquina, asegúrate de ejecutar el {% data variables.product.prodname_codeql_runner %} en el contenedor o en la máquina en donde toma lugar tu tarea de compilación. Para obtener más información, consulta la sección "[Ejecutar el escaneo de código de CodeQL en un contenedor](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)".
diff --git a/translations/es-ES/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
index e0799438e4..6df7b350f1 100644
--- a/translations/es-ES/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
+++ b/translations/es-ES/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -33,19 +35,22 @@ Si una compilación automática de código para un lenguaje compilado dentro de
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
         matrix:
           language: ['csharp', 'cpp', 'javascript']
 
+      steps:
       ...
-
-      - name: Initialize {% data variables.product.prodname_codeql %}
-        uses: github/codeql-action/init@v1
-        with:
-          languages: {% raw %}${{ matrix.language }}{% endraw %}
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: github/codeql-action/init@v1
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
   Para obtener más información acerca de editar el flujo de trabajo, consulta la sección "[Configurar el escaneo de código](/code-security/secure-coding/configuring-code-scanning)".
@@ -150,29 +155,29 @@ commit for best results.
 Puedes arreglar esto si eliminas las siguientes líneas del flujo de trabajo de {% data variables.product.prodname_codeql %}. Estas líneas se incluyeron en la sección de `steps` del job `Analyze` en las versiones iniciales del flujo de trabajo de {% data variables.product.prodname_codeql %}.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 La sección revisada de `steps` en el flujo de trabajo se deberá ver así:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 Para obtener más información sobre la edición del archivo de flujo de trabajo de {% data variables.product.prodname_codeql %}, consulta la sección "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)".
diff --git a/translations/es-ES/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index 5c3bec6b0c..824be20ba9 100644
--- a/translations/es-ES/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/es-ES/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -24,18 +26,19 @@ topics:
 
 Puedes generar archivos SARIF utilizando muchas herramientas de prueba de seguridad para análisis estático, incluyendo a {% data variables.product.prodname_codeql %}. Para cargar resultados desde herramientas de terceros debes utilizar el Formato de Intercambio para Resultados de Análisis Estático (SARIF) 2.1.0. Para obtener más información, consulta la sección "[Soporte de SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)".
 
-Puedes cargar los resultados utilizando las {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (disponibles si tu organización está participando en el programa del beta){% endif %}, la API del {% data variables.product.prodname_code_scanning %}, o el {% data variables.product.prodname_codeql_runner %}. El mejor método de carga dependerá de cómo generas el archivo SARIF, por ejemplo, si utilizas:
+You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. El mejor método de carga dependerá de cómo generas el archivo SARIF, por ejemplo, si utilizas:
 
 - {% data variables.product.prodname_actions %} para ejecutar la acción de {% data variables.product.prodname_codeql %}, no hay que hacer nada más. La acción de {% data variables.product.prodname_codeql %} carga el archivo de SARIF automáticamente cuando completa el análisis.
-- "[Administrar una ejecución de flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)"
-- {% data variables.product.prodname_dotcom %} mostrará alertas de {% data variables.product.prodname_code_scanning %} desde el archivo SARIF cargado en tu repositorio. Si bloqueas la carga automática, cuando estés listo para cargar los resultados, puedes utilizar el comando `upload` (para obtener más información, consulta la sección "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)").
+- "[Administrar una ejecución de flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- {% data variables.product.prodname_dotcom %} mostrará alertas de {% data variables.product.prodname_code_scanning %} desde el archivo SARIF cargado en tu repositorio. Si bloqueas la carga automática, cuando estés listo para cargar los resultados, puedes utilizar el comando `upload` (para obtener más información, consulta la seción "[Ejecutar el {% data variables.product.prodname_codeql_runner %} en tu sistema de IC](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").
 - Al ser una herramienta que genera resultados como un artefacto fuera de tu repositorio, puedes utilizar la API del {% data variables.product.prodname_code_scanning %} para cargar el archivo (Para encontrar más información, consulta la sección "[Cargar un análisis como datos de SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
 
 ### Cargar un análisis de {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_actions %}
 
-Para cargar un archivo SARIF de terceros a {% data variables.product.prodname_dotcom %}, necesitarás un flujo de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" y "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
+Para cargar un archivo SARIF de terceros a {% data variables.product.prodname_dotcom %}, necesitarás un flujo de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
 Tu flujo de trabajo necesitará utilizar la acción `upload-sarif`, que tiene parámetros de entrada que puedes utilizar para configurar la carga. Tiene parámetros de entrada que puedes utilizar para configurar la carga. El parámetro de entrada principal que utilizarás será `sarif-file`, el cual configura el archivo o directorio de los archivos SARIF a cargar. El directorio o ruta de archivo es relativo a la raíz del repositorio. Para obtener más información, consulta la [acción `upload-sarif`](https://github.com/github/codeql-action/tree/HEAD/upload-sarif).
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Ejemplo de flujo de trabajo que ejecuta la herramienta de análisis ESLint
@@ -87,7 +92,7 @@ Este ejemplo de flujo de trabajo se ejecuta cada que las confirmaciones se carga
 
 El flujo de trabajo muestra un ejemplo de ejecución de la herramienta de análisis estático ESLint como un paso en un flujo de trabajo. El paso `Run ESLint` ejecuta la herramienta ESLint y da como salida el archivo `results.sarif`. El flujo de trabajo entonces carga el archivo `results.sarif` a {% data variables.product.prodname_dotcom %} utilizando la acción `upload-sarif`. Para obtener más información acerca de cómo crear un archivo de flujo de trabajo, consulta la sección "[Introducción a Github Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Leer más
 
 - "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
-- "[Visualizar tu historial de flujos de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
+- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
 - "[Cargar un análisis como datos de SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
diff --git a/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index b8330fbc13..298f777444 100644
--- a/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/es-ES/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/es-ES/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 82f6b3a59a..59b13d8ea7 100644
--- a/translations/es-ES/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/es-ES/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -43,7 +43,7 @@ El publicar los detalles de una vulnerabilidad de seguridad no da una mala image
 
 El proceso para reportar y divulgar vulnerabilidades para los proyectos en {% data variables.product.prodname_dotcom_the_website %} es el siguiente:
 
- Si reportas una vulnerabilidad (por ejemplo, si eres un investigador de seguridad) y te gustaría proceder, revisa primero si existe una política de seguridad para el repositorio en cuestión. Para encontrar más información, consulta la sección "[Acerca de las políticas de seguridad](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)". Si esta existe, síguela para entender el proceso antes de contactar al equipo de seguridad de este repositorio.
+ Si reportas una vulnerabilidad (por ejemplo, si eres un investigador de seguridad) y te gustaría proceder, revisa primero si existe una política de seguridad para el repositorio en cuestión. Para encontrar más información, consulta la sección "[Acerca de las políticas de seguridad](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)". Si esta existe, síguela para entender el proceso antes de contactar al equipo de seguridad de este repositorio.
 
  Si no existe una política de seguridad en vigor, la forma más eficiente de establecer un medio de comunicación privado con los mantenedores es crear una propuesta que solicite un conteacto preferente para asuntos de seguridad. No sirve de nada que la propuesta sea visible al público inmediatamente, así que no debería incluir ningún tipo de información sobre el error. Una vez que se haya establecido la comunicación, puedes sugerir a los mantenedores que definan una política de seguridad para su uso futuro.
 
@@ -55,7 +55,7 @@ El proceso para reportar y divulgar vulnerabilidades para los proyectos en {% da
 
  Si encontraste una vulnerabilidad de seguridad en {% data variables.product.prodname_dotcom_the_website %}, por favor, repórtala a través de nuestro proceso de divulgación coordinada. Para obtener más información, consulta el sitio web de [Recompensa por Errores de Seguridad de {% data variables.product.prodname_dotcom %}](https://bounty.github.com/).
 
- Si eres un mantenedor, puedes tomar la responsabilidad del proceso desde el inicio de la red de comunicación si configuras una política de seguridad para tu repositorio o, de otra forma, poner las instrucciones de reporte de seguridad claramente disponibles, por ejemplo, en el archivo README de tu proyecto. Para obtener más información sobre cómo agregar una política de seguridad, consulta la sección "[Acerca de las políticas de seguridad](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)". Si no hay políticas de seguridad, es probable que alguien que reporta una vulnerabilidad intente enviarte un correo electrónico o contactarte en privado de alguna otra forma. Como alternativa, alguien podría abrir una propuesta (pública) con detalles de un problema de seguridad.
+ Si eres un mantenedor, puedes tomar la responsabilidad del proceso desde el inicio de la red de comunicación si configuras una política de seguridad para tu repositorio o, de otra forma, poner las instrucciones de reporte de seguridad claramente disponibles, por ejemplo, en el archivo README de tu proyecto. Para obtener más información sobre cómo agregar una política de seguridad, consulta la sección "[Acerca de las políticas de seguridad](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)". Si no hay políticas de seguridad, es probable que alguien que reporta una vulnerabilidad intente enviarte un correo electrónico o contactarte en privado de alguna otra forma. Como alternativa, alguien podría abrir una propuesta (pública) con detalles de un problema de seguridad.
 
  Como mantenedor, para divulgar una vulnerabilidad en tu código, primero debes creer un borrador de asesoría de seguridad en el repositorio del paquete en {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
 
diff --git a/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md
index 935aa74579..bd6ec8ff19 100644
--- a/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md
+++ b/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md
@@ -17,7 +17,7 @@ Puedes dar crédito a las personas que ayudaron a descubrir, reportar, o arregla
 
 Si alguien acepta el crédito, el nombre de usuario de la persona aparecerá en la sección "Créditos" de la asesoría de seguridad. Cualquiera con acceso de lectura al repositorio puede ver la asesoría y las personas que aceptaron el crédito por ella.
 
-If you believe you should be credited for a security advisory, please contact the person who created the advisory and ask them to edit the advisory to include your credit. Only the creator of the advisory can credit you, so please don't contact GitHub Support about credits for security advisories.
+Si crees que se te debería dar crédito por alguna asesoría de seguridad, por favor, contacta a la persona que la creó y pídele que edite la asesoría para incluir tu crédito. Solo el creador de la asesoría te puede dar crédito, asi que, por favor, no contactes al Soporte de GitHub pidiendo crédito para alguna asesoría de seguridad.
 
 ### Editar una asesoría de seguridad
 
diff --git a/translations/es-ES/content/code-security/security-advisories/index.md b/translations/es-ES/content/code-security/security-advisories/index.md
index ee610ecafa..a9173618d2 100644
--- a/translations/es-ES/content/code-security/security-advisories/index.md
+++ b/translations/es-ES/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### Índice
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md b/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md
index 15504fe88c..bab3112a69 100644
--- a/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md
+++ b/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md
@@ -1,6 +1,6 @@
 ---
-title: Exploring security alerts
-intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place.'
+title: Explorar las alertas de seguridad
+intro: 'Puedes ver, filtrar y clasificar las alertas de seguridad para los repositorios que pertenezcan a tu organización o equipo en un lugar.'
 product: '{% data reusables.gated-features.security-center %}'
 versions:
   free-pro-team: '*'
@@ -9,44 +9,44 @@ versions:
 
 {% data reusables.security-center.beta %}
 
-### About the security overview
+### Acerca del resumen de seguridad
 
-You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
+Puedes utilizar el resumen de seguirdad para tener una vista de nivel alto del estado de seguridad de tu organización o para identificar repositorios problemáticos que requieren intervención. A nivel organizacional, el resumen de seguridad muestra seguridad agregada y específica del repositorio para aquellos que pertenezcan a tu organización. A nivel de equipo, el resumen de seguridad muestra la información de seguridad específica del repositorio para aquellos en los que el equipo tenga privilegios de administración. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)".
 
-The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)."
+El resumen de seguridad indica si las características de la {% data variables.product.prodname_GH_advanced_security %} se habilitaron para los repositorios que pertenezcan a tu organización y consolida alertas de las características de la {% data variables.product.prodname_advanced_security %}, incluyendo las alertas del {% data variables.product.prodname_code_scanning %}, las {% data variables.product.prodname_dependabot_alerts %}, y las alertas del {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Acerca de asegurar tu repositorio](/code-security/getting-started/about-securing-your-repository)".
 
-In the security overview, you can view, sort, and filter alerts to understand the security risks in your organization and in specific repositories. You can apply multiple filters to focus on areas of interest. For example, you can identify private repositories that have a high number of {% data variables.product.prodname_dependabot_alerts %} or repositories that have no {% data variables.product.prodname_code_scanning %} alerts.
+En el resumen de seguridad, puedes ver, clasificar y filtrar las alertas para entender los riesgos de seguridad en tu organización y en los repositorios específicos. Puedes aplicar varios filtros para enfocarte en áreas de interés. Por ejemplo, puedes identificar repositorios privados que tengan una gran cantidad de {% data variables.product.prodname_dependabot_alerts %} o repositorios que no tengan alertas del {% data variables.product.prodname_code_scanning %}.
 
-![The security overview for an organization](/assets/images/help/organizations/security-overview.png)
+![El resumen de seguridad para una organziación](/assets/images/help/organizations/security-overview.png)
 
-For each repository in the security overview, you will see icons for each type of {% data variables.product.prodname_advanced_security %} feature and how many alerts there are of each type. If an {% data variables.product.prodname_advanced_security %} feature is not enabled for a repository, the icon for that feature will be grayed out.
+Para cada repositorio en el resumen de seguridad, verás iconos de cada tipo de característica de la {% data variables.product.prodname_advanced_security %} y cuántas alertas hay para cada tipo. Si no se habilita una característica de la {% data variables.product.prodname_advanced_security %} para un repositorio, su icono se mostrará en gris.
 
-![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png)
+![Los iconos en el resumen de seguridad](/assets/images/help/organizations/security-overview-icons.png)
 
-| Icon                                                          | Meaning                                                                                                                                                                                                                                                   |
+| Icono                                                         | Significado                                                                                                                                                                                                                                               |
 | ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)".          |
 | {% octicon "key" aria-label="Secret scanning alerts" %}       | alertas del {% data variables.product.prodname_secret_scanning_caps %}. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)". |
 | {% octicon "hubot" aria-label="Dependabot alerts" %}          | {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".  |
-| {% octicon "check" aria-label="Check" %}                      | The {% data variables.product.prodname_advanced_security %} feature is enabled, but does not raise alerts in this repository.                                                                                                                           |
-| {% octicon "x" aria-label="x" %}                              | The {% data variables.product.prodname_advanced_security %} feature is not supported in this repository.                                                                                                                                                |
+| {% octicon "check" aria-label="Check" %}                      | La característica de la {% data variables.product.prodname_advanced_security %} está habilitada, pero no levanta alertas en este repositorio.                                                                                                           |
+| {% octicon "x" aria-label="x" %}                              | La característica de la {% data variables.product.prodname_advanced_security %} no es compatible en este repositorio.                                                                                                                                   |
 
-By default, archived repositories are excluded from the security overview for an organization. You can apply filters to view archived repositories in the security overview. For more information, see "[Filtering the list of alerts](#filtering-the-list-of-alerts)."
+Predeterminadamente, los repositorios archivados se excluyen del resumen de seguridad de una organización. Puedes aplicar filtros para ver los repositorios archivados en el resumen de seguridad. Para obtener más información, consulta la sección "[Filtrar la lista de alertas](#filtering-the-list-of-alerts)".
 
-The security overview displays active alerts raised by {% data variables.product.prodname_GH_advanced_security %} features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
+El resumen de seguridad muestra alertas activas que levantan las características de la {% data variables.product.prodname_GH_advanced_security %}. Si no hay alertas en el resumen de seguridad de un repositorio, las vulnerabilidades de seguridad no detectadas o los errores de código podrían aún existir.
 
-### Viewing the security overview for an organization
+### Visualizar el resumen de seguridad de una organización
 
-Organization owners can view the security overview for an organization.
+Los propietarios de las organizaciones pueden ver el resumen de seguridad de estas.
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.security-overview %}
-1. To view aggregate information about alert types, click **Show more**. ![Show more button](/assets/images/help/organizations/security-overview-show-more-button.png)
+1. Para ver la información agregada sobre los tipos de alerta, haz clic en **Mostrar más**. ![Botón de mostrar más](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
 
-### Viewing the security overview for a team
+### Visualizar el resumen de seguridad de un equipo
 
-Members of a team can see the security overview for repositories that the team has admin privileges for.
+Los miembros de un equipo pueden ver el resumen de seguridad de los repositorios para los cuales dicho equipo tiene privilegios administrativos.
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
@@ -54,66 +54,66 @@ Members of a team can see the security overview for repositories that the team h
 {% data reusables.organizations.team-security-overview %}
 {% data reusables.organizations.filter-security-overview %}
 
-### Filtering the list of alerts
+### Filtrar la lista de alertas
 
-#### Filter by level of risk for repositories
+#### Filtrar por nivel de riesgo para los repositorios
 
-The level of risk for a repository is determined by the number and severity of alerts from {% data variables.product.prodname_advanced_security %} features. If one or more {% data variables.product.prodname_advanced_security %} features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by {% data variables.product.prodname_advanced_security %} features, the repository will have a clear level of risk.
+El nivel de riesgo de un repositorio se determina por la cantidad y severidad de las alertas de las características de {% data variables.product.prodname_advanced_security %}. Si no están habilitadas una o más características de la {% data variables.product.prodname_advanced_security %} para un repositorio, este tendrá un nivel de riesgo desconocido. Si un repositorio no tiene riesgos que detecten las características de la {% data variables.product.prodname_advanced_security %}, este tendrá un nivel de riesgo claro.
 
-| Qualifier      | Descripción                                                |
-| -------------- | ---------------------------------------------------------- |
-| `risk:high`    | Display repositories that are at high risk.                |
-| `risk:medium`  | Display repositories that are at medium risk.              |
-| `risk:low`     | Display repositories that are at low risk.                 |
-| `risk:unknown` | Display repositories that are at an unknown level of risk. |
-| `risk:clear`   | Display repositories that have no detected level of risk.  |
+| Qualifier      | Descripción                                                          |
+| -------------- | -------------------------------------------------------------------- |
+| `risk:high`    | Muestra los repositorios que tienen un riesgo alto.                  |
+| `risk:medium`  | Muestra los repositorios que tienen un riesgo medio.                 |
+| `risk:low`     | Muestra los repositorios que tienen un nivel de riesgo bajo.         |
+| `risk:unknown` | Muestra los repositorios que tienen un nivel de riesgo desconocido.  |
+| `risk:clear`   | Muestra los repositorios que no tienen un nivel de riesgo detectado. |
 
-#### Filter by number of alerts
+#### Filtra por cantidad de alertas
 
-| Qualifier                 | Descripción                                                                                                                                                 |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <code>code-scanning-alerts:<em>n</em></code> | Display repositories that have *n* {% data variables.product.prodname_code_scanning %} alerts. This qualifier can use &gt and &lt comparison operators.   |
-| <code>secret-scanning-alerts:<em>n</em></code> | Display repositories that have *n* {% data variables.product.prodname_secret_scanning %} alerts. This qualifier can use &gt and &lt comparison operators. |
-| <code>dependabot-alerts:<em>n</em></code> | Display repositories that have *n* {% data variables.product.prodname_dependabot_alerts %}. This qualifier can use &gt and &lt comparison operators.      |
+| Qualifier                 | Descripción                                                                                                                                                                           |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>code-scanning-alerts:<em>n</em></code> | Muestra los repositorios que tienen *n* alertas del {% data variables.product.prodname_code_scanning %}. Este calificador puede utilizar los operadores de comparación &gt y &lt.   |
+| <code>secret-scanning-alerts:<em>n</em></code> | Muestra los repositorios que tienen *n* alertas del {% data variables.product.prodname_secret_scanning %}. Este calificador puede utilizar los operadores de comparación &gt y &lt. |
+| <code>dependabot-alerts:<em>n</em></code> | Muestra los repositorios que tienen *n* {% data variables.product.prodname_dependabot_alerts %}. Este calificador puede utilizar los operadores de comparación &gt y &lt.           |
 
-#### Filter by whether {% data variables.product.prodname_advanced_security %} features are enabled
+#### Filtra por si las características de la {% data variables.product.prodname_advanced_security %} están habilitadas
 
-| Qualifier                       | Descripción                                                                                              |
-| ------------------------------- | -------------------------------------------------------------------------------------------------------- |
-| `enabled:code-scanning`         | Display repositories that have {% data variables.product.prodname_code_scanning %} enabled.            |
-| `not-enabled:code-scanning`     | Display repositories that do not have {% data variables.product.prodname_code_scanning %} enabled.     |
-| `enabled:secret-scanning`       | Display repositories that have {% data variables.product.prodname_secret_scanning %} enabled.          |
-| `not-enabled:secret-scanning`   | Display repositories that have {% data variables.product.prodname_secret_scanning %} enabled.          |
-| `enabled:dependabot-alerts`     | Display repositories that have {% data variables.product.prodname_dependabot_alerts %} enabled.        |
-| `not-enabled:dependabot-alerts` | Display repositories that do not have {% data variables.product.prodname_dependabot_alerts %} enabled. |
+| Qualifier                       | Descripción                                                                                                       |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `enabled:code-scanning`         | Muestra los repositorios que tienen habilitado el {% data variables.product.prodname_code_scanning %}.          |
+| `not-enabled:code-scanning`     | Muestra los repositorios que no tienen habilitado el {% data variables.product.prodname_code_scanning %}.       |
+| `enabled:secret-scanning`       | Muestra los repositorios que tienen habilitado el {% data variables.product.prodname_secret_scanning %}.        |
+| `not-enabled:secret-scanning`   | Muestra los repositorios que tienen habilitado el {% data variables.product.prodname_secret_scanning %}.        |
+| `enabled:dependabot-alerts`     | Muestra los repositorios que tienen habilitadas las {% data variables.product.prodname_dependabot_alerts %}.    |
+| `not-enabled:dependabot-alerts` | Muestra los repositorios que no tienen habilitadas las {% data variables.product.prodname_dependabot_alerts %}. |
 
-#### Filter by repository type
+#### Filtrar por tipo de repositorio
 
-| Qualifier       | Descripción                    |
-| --------------- | ------------------------------ |
-| `is:public`     | Display public repositories.   |
-| `is:internal`   | Display internal repositories. |
-| `is:private`    | Display private repositories.  |
-| `archived:true` | Display archived repositories. |
+| Calificador     | Descripción                          |
+| --------------- | ------------------------------------ |
+| `is:public`     | Muestra los repositorios públicos.   |
+| `is:internal`   | Muestra los repositorios internos.   |
+| `is:private`    | Muestra los repositorios privados.   |
+| `archived:true` | Muestra los repositorios archivados. |
 
-#### Filter by team
+#### Filtrar por equipo
 
-| Qualifier                 | Descripción                                                      |
-| ------------------------- | ---------------------------------------------------------------- |
-| <code>team:<em>TEAM-NAME</em></code> | Displays repositories that *TEAM-NAME* has admin privileges for. |
+| Calificador               | Descripción                                                                        |
+| ------------------------- | ---------------------------------------------------------------------------------- |
+| <code>team:<em>TEAM-NAME</em></code> | Muestra los repositorios en los que *TEAM-NAME* tiene privilegios administrativos. |
 
-#### Filter by topic
+#### Filtrar por tema
 
-| Qualifier                 | Descripción                                                  |
+| Calificador               | Descripción                                                  |
 | ------------------------- | ------------------------------------------------------------ |
-| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+| <code>topic:<em>TOPIC-NAME</em></code> | Muestra los repositorios que se clasifican con *TOPIC-NAME*. |
 
-#### Sort the list of alerts
+#### Clasifica la lista de alertas
 
-| Qualifier                     | Descripción                                                                                                                   |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `sort:risk`                   | Sorts the repositories in your security overview by risk.                                                                     |
-| `sort:repos`                  | Sorts the repositories in your security overview alphabetically by name.                                                      |
-| `sort:code-scanning-alerts`   | Sorts the repositories in your security overview by number of {% data variables.product.prodname_code_scanning %} alerts.   |
-| `sort:secret-scanning-alerts` | Sorts the repositories in your security overview by number of {% data variables.product.prodname_secret_scanning %} alerts. |
-| `sort:dependabot-alerts`      | Sorts the repositories in your security overview by number of {% data variables.product.prodname_dependabot_alerts %}.      |
+| Calificador                   | Descripción                                                                                                                                   |
+| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sort:risk`                   | Clasifica los repositorios por riesgo en tu resumen de seguridad.                                                                             |
+| `sort:repos`                  | Clasifica los repositorios en tu resumen de seguridad por órden alfabético de nombre.                                                         |
+| `sort:code-scanning-alerts`   | Clasifica los repositorios en tu resumen de seguridad por la cantidad de alertas del {% data variables.product.prodname_code_scanning %}.   |
+| `sort:secret-scanning-alerts` | Clasifica los repositorios en tu resumen de seguridad por la cantidad de alertas del {% data variables.product.prodname_secret_scanning %}. |
+| `sort:dependabot-alerts`      | Clasifica los repositorios en tu resumen de seguridad por cantidad de {% data variables.product.prodname_dependabot_alerts %}.              |
diff --git a/translations/es-ES/content/code-security/security-overview/index.md b/translations/es-ES/content/code-security/security-overview/index.md
index 2ad465e91c..bb65e805b0 100644
--- a/translations/es-ES/content/code-security/security-overview/index.md
+++ b/translations/es-ES/content/code-security/security-overview/index.md
@@ -1,7 +1,7 @@
 ---
-title: Viewing security alerts for repositories in your organization
-shortTitle: Security overview
-intro: 'View, sort, and filter the security alerts from across your organization in one place.'
+title: Visualizar las alertas de seguridad para los repositorios en tu organización
+shortTitle: Resumen de seguridad
+intro: 'Visualiza, clasifica y filtra las alertas de seguridad desde cualquier parte de tu organización en un solo lugar.'
 product: '{% data reusables.gated-features.security-center %}'
 versions:
   free-pro-team: '*'
diff --git a/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
index 80f5b4439c..289082e669 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
 title: Acerca de las alertas para las dependencias vulnerables
-intro: '{% data variables.product.product_name %} envía {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} cuando detectamos vulnerabilidades que afectan tu repositorio.'
+intro: '{% data variables.product.product_name %} envía {% data variables.product.prodname_dependabot_alerts %} cuando detectamos vulnerabilidades que afectan tu repositorio.'
 redirect_from:
   - /articles/about-security-alerts-for-vulnerable-dependencies
   - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
@@ -12,6 +12,7 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
 
 ### Acerca de las dependencias vulnerables
@@ -22,12 +23,12 @@ Cuando tu código depende de un paquete que tiene una vulnerabilidad de segurida
 
 ### Detección de dependencias vulnerables
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}El {% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables y envía {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detecta dependencias vulnerables y envía alertas de seguridad{% endif %} cuando:
+{% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables y envía {% data variables.product.prodname_dependabot_alerts %} cuando:
 
 {% if currentVersion == "free-pro-team@latest" %}
-- Se agrega una vulnerabilidad nueva a la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)".{% else %}
-- Se sincronizan los datos de las asesorías nuevas en {% data variables.product.prodname_ghe_server %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información acerca de los datos de las asesorías, consulta la sección "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Buscar vulnerabilidades de seguridad en el {% data variables.product.prodname_advisory_database %}</a>".{% endif %}
-- La gráfica de dependencias para los cambios a un repositorio. Por ejemplo, cuando un colaborador sube una confirmación para cambiar los paquetes o versiones de las cuales depende{% if currentVersion == "free-pro-team@latest" %}, o cuando el código de una de las dependencias cambia{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
+- Se agrega una vulnerabilidad nueva a la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta las secciones "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" y [Acerca de las {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)".{% else %}
+- Se sincronizan los datos de las asesorías nuevas en {% data variables.product.prodname_ghe_server %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+- La gráfica de dependencias para los cambios a un repositorio. Por ejemplo, cuando un colaborador sube una confirmación para cambiar los paquetes o versiones de las cuales depende{% if currentVersion == "free-pro-team@latest" %}, o cuando el código de una de las dependencias cambia{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/about-the-dependency-graph)".
 
 {% data reusables.repositories.dependency-review %}
 
@@ -39,58 +40,41 @@ Para encontrar una lista de ecosistemas para las cuales {% data variables.produc
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
 ### Alertas del {% data variables.product.prodname_dependabot %} para dependencias vulnerables
-{% else %}
-### Alertas de seguridad para las dependencias vulnerables
-{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detecta dependencias vulnerables en repositorios _públicos_ y genera {% data variables.product.prodname_dependabot_alerts %} predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios.
 
-También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. 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)."
+También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
-For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
+Para obtener más información sobre los requisitos de permisos para las acciones que se relacionan con las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)".
 
 {% data variables.product.product_name %} comienza a generar la gráfica de dependencias inmediatamente y genera alertas de cualquier dependencia vulnerable tan pronto como las identifique. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)".
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 Cuando {% data variables.product.product_name %} identifica una dependencia vulnerable, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de Seguridad del repositorio. La alerta incluye un enlace al archivo afectado en el proyecto e información acerca de la versión arreglada. {% data variables.product.product_name %} también notifica a los mantenedores de los repositorios afectados sobre la nueva alerta de acuerdo con sus preferencias de notificaciones. Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)".
-{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 Para los repositorios en donde están habilitadas las {% data variables.product.prodname_dependabot_security_updates %}, la alerta también podría contener un enlace a una solicitud de cambios o a una actualización en el archivo de bloqueo o de manifiesto para la versión mínima que resuelva la vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)".
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Cuando {% data variables.product.product_name %} identifica una dependencia vulnerable, enviamos una alerta de seguridad a los mantenedores de los repositorios afectados con los detalles sobre la vulnerabilidad, un enlace para el archivo afectado en el proyecto y la información acerca de una versión corregida.
-{% endif %}
-
 {% warning %}
 
 **Nota**: Las características de seguridad de {% data variables.product.product_name %} no aseguran que se detectarán todas las vulnerabilidades. Aunque siempre estamos tratando de actualizar nuestra base de datos de vulnerabilidades y de generar alertas con nuestra información más actualizada, no podremos atrapar todo o garantizar decirte acerca de las vulnerabilidades conocidas dentro de un periodo de tiempo determinado. Estas características no son sustitutos de la revisión humana de cada dependencia por posibles vulnerabilidades o cualquier otra cuestión. Te recomendamos consultar con un servicio de seguridad o realizar una revisión de vulnerabilidad exhaustiva cuando sea necesario.
 
 {% endwarning %}
 
-### Acceso a las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}
+### Acceso a las alertas del {% data variables.product.prodname_dependabot %}
 
-Puedes ver todas las alertas que afectan un proyecto en particular{% if currentVersion == "free-pro-team@latest" %} en la pestaña de seguridad del repositorio o{% endif %} en la gráfica de dependencias del mismo.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %}
+Puedes ver todas las alertas que afectan un proyecto en particular{% if currentVersion == "free-pro-team@latest" %} en la pestaña de Seguridad del repositorio o{% endif %} en la gráfica de dependencias del repositorio. Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositiorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades identificadas de ningún repositorio. También puedes hacer que las {% data variables.product.prodname_dependabot_alerts %} sean visibles para más personas o equipos que trabajen en los repositorios que te pertenecen o para los cuales tienes permisos administrativos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
+Predeterminadamente, notificamos a las personas con permisos administrativos en los repositorios afectados sobre las {% data variables.product.prodname_dependabot_alerts %} nuevas. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades identificadas de ningún repositorio. También puedes hacer que las {% data variables.product.prodname_dependabot_alerts %} sean visibles para más personas o equipos que trabajen en los repositorios que te pertenecen o para los cuales tienes permisos administrativos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Enviamos alertas de seguridad para las personas con permisos de administrador en los repositorios por defecto afectados. {% data variables.product.product_name %} nunca disemina públicamente las vulnerabilidades identificadas de ningún repositorio.
-{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)".
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obtener más información, consulta la sección "[Elegir el método de entrega para tus notificaciones](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)".{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)".{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-También puedes ver todas las {% data variables.product.prodname_dependabot_alerts %} que corresponden a una vulnerabilidad en particular en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)".
-{% endif %}
+También puedes ver todas las {% data variables.product.prodname_dependabot_alerts %} que corresponden a una vulnerabilidad en particular en la {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Leer más
diff --git a/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index faa7d58bb0..2e09ae4b3f 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -35,6 +35,7 @@ Tú eres quien especifica qué tan a menudo se revisa cada ecosistema para encon
 Si habilitaste las actualizaciones de seguridad, algunas veces verás solicitudes de extracción adicionales para actualizaciones de seguridad. Esto se activa con una alerta del {% data variables.product.prodname_dependabot %} para una dependencia en tu rama predeterminada. El {% data variables.product.prodname_dependabot %} levanta automáticamente una solicitud de extracción para actualizar la dependencia vulnerable.
 
 ### Repositorios y ecosistemas compatibles
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 Puedes configurar las actualizaciones de versión para los repositorios que contengan un manifiesto de dependencias o un archivo fijado para alguno de los administradores de paquetes compatibles. Para algunos administradores de paquetes, también puedes configurar la delegación a proveedores para las dependencias. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)".
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md
index 3251964b21..dcd5820a9c 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md
@@ -1,6 +1,6 @@
 ---
-title: About the dependency graph
-intro: You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems.
+title: Acerca del gráfico de dependencias
+intro: Puedes utilizar la gráfica de dependencias para identificar todas las dependencias de tus proyectos. La gráfica de dependencias es compatible con una variedad de ecosistemas de paquetes populares.
 redirect_from:
   - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph
 versions:
@@ -9,86 +9,84 @@ versions:
 topics:
   - Repositories
 ---
+
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
 <!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
 
-### Dependency graph availability
+### Disponibilidad de la gráfica de dependencias
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+La gráfica de dependencias se encuentra disponible para cada{% if currentVersion == "free-pro-team@latest" %} repositorio público{% endif %} que define las dependencias en un ecosistema de paquetes compatible utilizando un formato de archivo compatible.{% if currentVersion == "free-pro-team@latest" %} Los administradores del repositorio también pueden configurar la gráfica de dependencias para los repositorios privados.{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
-### About the dependency graph
+### Acerca del gráfico de dependencias
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Para cada repositorio, muestra{% if currentVersion == "free-pro-team@latest" %}:
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+- Las dependencias, ecosistemas y paquetes de los cuales depende
+- Los dependientes, repositorios y paquetes que dependen de ella{% else %} dependencias, es decir, los ecosistemas y los paquetes de los cuales depende. {% data variables.product.prodname_ghe_server %} no calcula información alguna sobre los dependientes, repositorios y paquetes que dependen de un repositorio.{% endif %}
 
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+Cuando subes una confirmación a {% data variables.product.product_name %} que cambia o agrega un archivo bloqueado o de manifiesto compatible a la rama predeterminada, la gráfica de dependencias se actualiza automáticamente.{% if currentVersion == "free-pro-team@latest" %} Adicionalmente, la gráfica se actualiza cuando cualquiera carga un cambio al repositorio de una de tus dependencias.{% endif %} Para obtener más información sobre los archivos de manifiesto y ecosistemas compatibles, consulta la sección "[Ecosistemas de paquetes compatibles](#supported-package-ecosystems)" más adelante.
 
 {% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+Cuando creas una solicitud de cambios que contenga los cambios de las dependencias que apuntan a la rama predeterminada, {% data variables.product.prodname_dotcom %} utiliza la gráfica de dependencias para agregar revisiones de dependencia a la solicitud de cambios. Estas indican si las dependencias contendrán vulnerabilidades y, si es el caso, la versión de la dependencia en la cual se arregló la vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)".
 {% endif %}
 
-### Dependencies included
+### Dependencias que se incluyen
 
-The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
+La gráfica de dependencias incluye todas las dependencias de un repositorio que se describan en los archivos de manifiesto y de bloqueo o sus equivalentes para los ecosistemas compatibles. Esto incluye:
 
-- Direct dependencies, that are explicitly defined in a manifest or lock file
-- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+- Las dependencias directas que se definen explícitamente en el archivo de manifiesto o de bloqueo
+- Las dependencias indirectas de estas dependencias directas, también conocidas como dependencias transitorias o sub-dependencias
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+La gráfica de dependencias identifica las dependencias indirectas{% if currentVersion == "free-pro-team@latest" %} ya sea explícitamente desde un archivo bloqueado o mediante la verificación de las dependencias de tus dependencias directas. Para la gráfica más confiable, debes utilizar archivos de bloqueo (o su equivalente), ya que estos definen exactamente qué versiones de las dependencias directas e indirectas estás utilizando actualmente. Si utilizas archivos de bloqueo, también te aseguras de que todos los contribuyentes del repositorio están utilizando las mismas versiones, lo cual te facilitará el probar y depurar el código{% else %} de los archivos de bloqueo{% endif %}.
 
 {% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
+### Dependientes incluídos
 
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+Para los repositorios públicos, únicamente se reportan los repositorios públicos que dependen de éste o de los paquetes que publicas. Esta información no se reporta para los repositorios privados.{% endif %}
 
-### Using the dependency graph
+### Utiizar la gráfica de dependencias
 
-You can use the dependency graph to:
+Puedes utilizar la gráfica de dependencias para:
 
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
+- Explora los repositorios de los cuales depende tu código{% if currentVersion == "free-pro-team@latest" %} y aquellos que dependen de él{% endif %}. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% if currentVersion == "free-pro-team@latest" %}
+- Ver en un solo tablero un resumen de las dependencias que se utilizan en los repositorios de tu organización. Para obtener más información, consulta "[Ver información de tu organización](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %}
+- Ver y actualizar las dependencias vulnerables de tu repositorio. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".{% if currentVersion == "free-pro-team@latest" %}
+- Consulta la información sobre las dependencias vulnerables en las solicitudes de cambios. Para obtener más información, consulta la sección "[Revisar los cambios de dependencia en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)".{% endif %}
 
-### Enabling the dependency graph
+### Habilitar la gráfica de dependencias
 
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Para generar una gráfica de dependencias, {% data variables.product.product_name %} necesita acceso de solo lectura a los archivos bloqueados y de manifiesto de la dependencia para el repositorio en cuestión. La gráfica de dependencias se genera automáticamente para todos los repositorios públicos y puedes elegir habilitarla para los privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}Si la gráfica de dependencias no se encuentra disponible en tu sistema, tu administrador de sitio puede habilitarla junto con las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+Cuando la gráfica de dependencias se habilita por primera vez, cualquier manifiesto y archivo de bloqueo para los ecosistemas compatibles se pasarán de inmediato. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Una vez que se habilite, la gráfica se actualiza automáticamente con cada subida al repositorio{% if currentVersion == "free-pro-team@latest" %} y con cada subida a otros repositorios en la gráfica{% endif %}.
 
-{% endif %}
+### Ecosistemas de paquetes compatibles
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+Los formatos recomendados definen explícitamente qué versiones se utilizan para todas las dependencias directas e indirectas. Si utilizas estos formatos, tu gráfica de dependencias será más precisa. También refleja la configuración actual de la compilación y habilita la gráfica de dependencias para reportar vulnerabilidades tanto en las dependencias directas como en las indirectas.{% if currentVersion == "free-pro-team@latest" %} Las dependencias directas que se infieran de un archivo de manifiesto (o de su equivalente) se excluirán de las verificaciones para las dependencias vulnerables.{% endif %}
 
-### Supported package ecosystems
-
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
-
-| Package manager | Languages | Recommended formats | All supported formats |
-| --- | --- | --- | ---|
-| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| 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`* |
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+| Administración de paquetes | Idiomas                          | Formatos recomendados                                  | Todos los formatos compatibles                                            |
+| -------------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
+| Composer                   | PHP                              | `composer.lock`                                        | `composer.json`, `composer.lock`                                          |
+| `dotnet` CLI               | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+| 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`*                |
+| RubyGems                   | Ruby                             | `Gemfile.lock`                                         | `Gemfile.lock`, `Gemfile`, `*.gemspec`                                    |
+| Yarn                       | JavaScript                       | `yarn.lock`                                            | `package.json`, `yarn.lock`                                               |
 
 {% note %}
 
-**Note:** 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.
+**Nota:** Si listas tus dependencias de Python dentro de un archivo `setup.py`, es probable que no podamos analizar y listar cada una de las dependencias en tu proyecto.
 
 {% endnote %}
 
-### Further reading
+### Leer más
 
-- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Gráfica de dependencias](https://en.wikipedia.org/wiki/Dependency_graph)" en Wikipedia
+- "[Explorando las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}
+- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
+- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index 073e259877..f432ec3c1d 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -164,7 +164,7 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Utiliza la opción `allow` para personalizar qué dependencias se actualizan. Esto no impacta en las actualizaciones de seguridad para las dependencias vulnerables. Puedes utilizar las siguientes opciones:
+Utiliza la opción `allow` para personalizar qué dependencias se actualizan. This applies to both version and security updates. Puedes utilizar las siguientes opciones:
 
 - `dependency-name`—se utiliza para permitir actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId`, por ejemplo: `org.kohsuke:github-api`.
 - `dependency-type`—utilízalo para permitir actualizaciones para dependencias de tipos específicos.
@@ -445,12 +445,12 @@ updates:
 
 #### `rebase-strategy`
 
-Predeterminadamente, el {% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de extracción abiertas cuando detecta conflictos. Utiliza `rebase-strategy` para inhabilitar este comportamiento.
+Predeterminadamente, el{% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de cambios abiertas y detecta cualquier cambio en ellas. Utiliza `rebase-strategy` para inhabilitar este comportamiento.
 
 Estrategias de rebase disponibles
 
 - `disabled` para inhabilitar el rebase automático.
-- `auto` para utilizar el comportamiento predeterminado y rebasar las solicitudes de extracción abiertas cuando se detecten conflictos.
+- `auto` para utilizar el comportamiento predeterminado y rebasar las solicitudes de cambios abiertas cuando se detecten cambios.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -473,11 +473,11 @@ Para permitir que el {% data variables.product.prodname_dependabot %} acceda a u
 
 Para permitir que el {% data variables.product.prodname_dependabot %} utilice los administradores de paquetes `bundler`, `mix`, y `pip` para actualizar dependencias en los registros privados, puedes elegir el permitir la ejecución de código externo. Para obtener más información, consulta [`insecure-external-code-execution`](#insecure-external-code-execution).
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -493,11 +493,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -716,7 +716,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
@@ -724,14 +724,15 @@ updates:
 
 Utilizarás las siguientes opciones para especificar la configuración de acceso. La configuración del registro debe contener un `type` y una `url` y, habitualmente, ya sea una combinación de `username` y `password` o un `token`.
 
-| Opción&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Descripción                                                                                                                                                                                                                                                                                                                |
-|:------------------------------------------------------------------------------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `type`                                                                                                 | Identifica el tipo de registro. Consulta la lista completa de tipos más adelante.                                                                                                                                                                                                                                          |
-| `url`                                                                                                  | La URL a utilizar para acceder a las dependencias en el registro. El protocolo es opcional. Si no se especifica, se asumirá que es `https://`. El {% data variables.product.prodname_dependabot %} agrega o ignora las diagonales iniciales conforme sea necesario.                                                        |
-| `nombre de usuario`                                                                                    | El nombre de usuario que utilizará el {% data variables.product.prodname_dependabot %} para acceder al registro.                                                                                                                                                                                                           |
-| `contraseña`                                                                                           | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga la contraseña del usuario específico. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)".  |
-| `token`                                                                                                | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga un token de acceso para este registro. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". |
-| `replaces-base`                                                                                        | Para los registros con `type: python-index`, si el valor booleano es `true`, pip resuleve las dependencias utilizando la URL especificada en vez de la URL base del Índice de Paquetes de Python (que predeterminadamente es `https://pypi.org/simple`).                                                                   |
+| Opción&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Descripción                                                                                                                                                                                                                                                                                                                 |
+|:------------------------------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type`                                                                                                 | Identifica el tipo de registro. Consulta la lista completa de tipos más adelante.                                                                                                                                                                                                                                           |
+| `url`                                                                                                  | La URL a utilizar para acceder a las dependencias en el registro. El protocolo es opcional. Si no se especifica, se asumirá que es `https://`. El {% data variables.product.prodname_dependabot %} agrega o ignora las diagonales iniciales conforme sea necesario.                                                         |
+| `nombre de usuario`                                                                                    | El nombre de usuario que utilizará el {% data variables.product.prodname_dependabot %} para acceder al registro.                                                                                                                                                                                                            |
+| `contraseña`                                                                                           | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga la contraseña del usuario específico. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)".   |
+| `clave`                                                                                                | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga una clave de acceso para este registro. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". |
+| `token`                                                                                                | Una referencia a un secreto del {% data variables.product.prodname_dependabot %} que contenga un token de acceso para este registro. Para obtener más información, consulta la sección "[Administrar los secretos cifrados del Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)".  |
+| `replaces-base`                                                                                        | Para los registros con `type: python-index`, si el valor booleano es `true`, pip resuleve las dependencias utilizando la URL especificada en vez de la URL base del Índice de Paquetes de Python (que predeterminadamente es `https://pypi.org/simple`).                                                                    |
 
 
 Cada `type` de configuración requiere que proporciones ajustes en particular. Algunos tipos permiten más de una forma de conectarse. Las siguientes secciones proporcionan detalles de las configuraciones que deberías utilizar para cada `type`.
@@ -766,6 +767,19 @@ registries:
 ```
 {% endraw %}
 
+El tipo `docker-registry` también se puede utilizar para extraer información de Amazon ECR utilizando las credenciales estáticas de AWS.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 El tipo `git` es compatible con nombre de usuario y contraseña.
@@ -781,6 +795,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+El tipo `hex-organization` es compatible con organizaciones y claves.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 El tipo `maven-repository` es compatible con nombre de usuario y contraseña, o token.
diff --git a/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
index 9ba67694ba..21350478dc 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
@@ -49,7 +49,7 @@ Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sab
 
 Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual (ver a continuación).
 
-También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. 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)."
+También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
 Las {% data variables.product.prodname_dependabot_security_updates %} requieren de configuraciones de repositorio específicas. Para obtener más información, consulta "[Repositorios soportados](#supported-repositories)".
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index 1695805068..6b743fd54e 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring notifications for vulnerable dependencies
-shortTitle: Configuring notifications
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+title: Configurar las notificaciones para las dependencias vulnerables
+shortTitle: Configurar notificaciones
+intro: 'Optimiza la forma en la que recibes las notificaciones sobre las alertas del {% data variables.product.prodname_dependabot %}.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
@@ -11,50 +11,43 @@ topics:
   - Security
 ---
 
-### About notifications for vulnerable dependencies
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
-{% endif %} 
+### Acerca de las notificaciones para las dependencias vulnerables
 
-{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
+Cuando el {% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables en tus repositorios, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad del repositorio. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con sus preferencias de notificaciones.{% if currentVersion == "free-pro-team@latest" %}El {% data variables.product.prodname_dependabot %} se habilita predeterminadamente en todos los repositorios públicos. En el caso de las {% data variables.product.prodname_dependabot_alerts %}, predeterminadamente, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico, agrupadas por la vulnerabilidad específica.
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Si eres un propietario de organización, puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios en tu organización con un clic. También puedes configurar si se habilitará o inhabilitará la detección de dependencias vulnerables para los repositorios recién creados. Para obtener más información, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)".
+{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %}
+Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para las notificaciones de tu empresa, recibirás {% data variables.product.prodname_dependabot_alerts %} por correo electrónico.{% endif %}
 
-{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}Los administradores de sitio también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+### Configurar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}
 
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
-
-You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
+Puedes configurar los ajustes de notificaciones para ti mismo o para tu organización desde el menú desplegable de administrar notificaciones {% octicon "bell" aria-label="The notifications bell" %} que se muestra en la parte superior de cada página. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)".
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-  ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
-{% else %}
-  ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png)
-{% endif %}
+  ![Opciones de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 
 {% note %}
 
-**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+**Nota:** Puedes filtrar tus notificaciones en {% data variables.product.company_short %} para mostrar las alertas del {% data variables.product.prodname_dependabot %}. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)".
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %}Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
 
-### How to reduce the noise from notifications for vulnerable dependencies
+### Cómo reducir el ruido de las notificaciones para las dependencias vulnerables
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+Si te preocupa recibir demasiadas notificaciones para las {% data variables.product.prodname_dependabot_alerts %}, te recomendamos que te unas al resumen semanal por correo electrónico o que apagues las notificaciones mientras mantienes habilitadas las {% data variables.product.prodname_dependabot_alerts %}. Aún puedes navegar para ver tus {% data variables.product.prodname_dependabot_alerts %} en la pestaña de seguridad de tu repositorio. Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositiorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".
 
-### Further reading
+### Leer más
 
-- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
-- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
+- "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
+- "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
diff --git a/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index ae3ac87e94..ed3567e05d 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -18,7 +18,7 @@ Habilitarás {% data variables.product.prodname_dependabot_version_updates %} me
 
 {% data reusables.dependabot.initial-updates %} Para obtener más información, consulta la sección "[Personalizar las actualizaciones de las dependencias](/github/administering-a-repository/customizing-dependency-updates)".
 
-{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, el {% data variables.product.prodname_dependabot %} no es compatible con dependencias privadas de {% data variables.product.prodname_dotcom %} para todos los administradores de paquetes. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)".
+{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, el {% data variables.product.prodname_dependabot %} no es compatible con dependencias privadas de {% data variables.product.prodname_dotcom %} para todos los administradores de paquetes. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
 
 ### Habilitar las {% data variables.product.prodname_dependabot_version_updates %}
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index f0fe5f8586..2e196f8470 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -15,6 +15,8 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### Visualizar la gráfica de dependencias
 
 {% data reusables.repositories.enable-security-alerts %}
@@ -50,19 +52,6 @@ Se listará cualquier dependencia directa e indirecta que se especifique en los
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. Si se detectan vulnerabilidades en el repositorio, estas se mostrarán en la parte superior de la vista para los usuarios con acceso a las alertas de seguridad.
-
-![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**.
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### Vista de dependientes
 
@@ -74,7 +63,7 @@ Para los repositorios públicos, la vista de dependientes muestra cómo otros re
 
 Los administradores del repositorio pueden habilitar o inhabilitar la gráfica de dependencias para los repositorios privados.
 
-También puedes habilitar o inhabilitar la gráfica de dependencias para todos los repositorios que pertenecen a tu cuenta de usuario u organización. 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)."
+También puedes habilitar o inhabilitar la gráfica de dependencias para todos los repositorios que pertenecen a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -113,9 +102,9 @@ Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omit
 
 ### Leer más
 
-- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
 - "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
 - "
 Entender cómo {% data variables.product.product_name %} utiliza y protege tus datos" </p> 
   
diff --git a/translations/es-ES/content/code-security/supply-chain-security/index.md b/translations/es-ES/content/code-security/supply-chain-security/index.md
index 92545b3c77..ba8c2a29b6 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/index.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index ec6ef4bccf..7b61187e61 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -17,18 +17,18 @@ Los resultados de la detección de dependencias que reporta {% data variables.pr
 
 {% data variables.product.prodname_dotcom %} genera y muestra los datos de las dependencias de forma diferente a otras herramientas. En consecuencia, si has estado utilizando otra herramienta para identificar dependencias, muy probablemente encuentres resultados diferentes. Considera lo sigueinte:
 
-*   {% data variables.product.prodname_advisory_database %} es una de las fuentes de datos que utiliza {% data variables.product.prodname_dotcom %} para identificar las dependencias vulnerables. Es una base de datos de información de vulnerabilidades orgtanizada y gratuita para los ecosistemas de paquetes comunes en {% data variables.product.prodname_dotcom %}. Esta incluye tanto los datos reportados directamente a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_security_advisories %}, así como las fuentes oficiales y las comunitarias. {% data variables.product.prodname_dotcom %} revisa y organiza estos datos para garantizar que la información falsa o inprocesable no se comparta con la comunidad de desarrollo. Para obtener más información, consulta las secciones "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" y [Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
+*   {% data variables.product.prodname_advisory_database %} es una de las fuentes de datos que utiliza {% data variables.product.prodname_dotcom %} para identificar las dependencias vulnerables. Es una base de datos de información de vulnerabilidades orgtanizada y gratuita para los ecosistemas de paquetes comunes en {% data variables.product.prodname_dotcom %}. Esta incluye tanto los datos reportados directamente a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_security_advisories %}, así como las fuentes oficiales y las comunitarias. {% data variables.product.prodname_dotcom %} revisa y organiza estos datos para garantizar que la información falsa o inprocesable no se comparta con la comunidad de desarrollo. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   La gráfica de dependencias analiza todos los archivos de manifiesto de paquetes conocidos en un repositorio de usuario. Por ejemplo, para npm analizará el archivo _package-lock.json_. Construye una gráfica de todas las dependencias del repositorio y de los dependientes públicos. Esto sucede cuando habilitas la gráfica de dependencias y cuando alguien hace cargas a la rama predeterminada, y esto incluye a las confirmaciones que hacen cambios a un formato de manifiesto compatible. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 *   {% data variables.product.prodname_dependabot %} escanea cualquier subida a la rama predeterminada que contenga un archivo de manifiesto. Cuando se agrega un registro de vulnerabilidad nuevo, este escanea todos los repositorios existentes y genera una alerta para cada repositorio vulnerable. Las {% data variables.product.prodname_dependabot_alerts %} se agregan a nivel del repositorio, en vez de crear una alerta por cada vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
-*   Las {% data variables.product.prodname_dependabot_security_updates %} se activan cuando recibes una alerta sobre una dependencia vulnerable en tu repositorio. Cuando sea posible, el {% data variables.product.prodname_dependabot %} creará una solicitud de cambios en tu repositorio para actualizar la dependencia vulnerable a la versión segura mínima posible que se requiere para evitar la vulnerabilidad. Para obtener más información, consulta las secciones "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" y "[Solucionar problemas en los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)".
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} se activa cuando recibes una alerta sobre una dependencia vulnerable en tu repositorio. Cuando sea posible, el {% data variables.product.prodname_dependabot %} creará una solicitud de cambios en tu repositorio para actualizar la dependencia vulnerable a la versión segura mínima posible que se requiere para evitar la vulnerabilidad. Para obtener más información, consulta las secciones "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" y "[Solucionar problemas en los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)".
 
-    El {% data variables.product.prodname_dependabot %} no escanea los repositorios para encontrar dependencias vulnerables bajo ninguna programación, sino cuando algo cambia. Por ejemplo, se activa un escaneo cuando se agrega una dependencia ({% data variables.product.prodname_dotcom %} verifica esto en cada subida), o cuando se descubre una vulnerabilidad nueva y ésta se agrega en la base de datos de asesorías.
+    {% endif %}El {% data variables.product.prodname_dependabot %} no escanea los repositorios para encontrar dependencias vulnerables en horarios específicos, sino cuando algo cambia. Por ejemplo, se activará un escaneo cuando se agregue una dependencia nueva ({% data variables.product.prodname_dotcom %} verifica esto en cada subida) o cuando se agrega una vulnerabilidad a la base de datos de las asesorías {% if currentVersion ver_gt "enterprise-server@2.22" %} y se sincroniza con {% data variables.product.prodname_ghe_server %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)".
 
 ### ¿Por qué no me llegan alertas de vulnerabilidades de algunos ecosistemas?
 
-{% data variables.product.prodname_dotcom %} limita su soporte para alertas de vulnerabilidades a un conjunto de ecosistemas donde podemos proporcionar datos procesables de alta calidad. Las vulnerabilidades que se organizan en la {% data variables.product.prodname_advisory_database %}, la gráfica de dependencias, las alertas de {% data variables.product.prodname_dependabot_alerts %}, y las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} se proporcionan para varios ecosistemas, incluyendo Maven de Java, npm y Yarn de JavaScript, NuGet de .NET, pip de Python, RubyGems de Ruby y Composer de PHP. Seguiremos agregando soporte para más ecosistemas a la larga. Para obtener una vista general de los ecosistemas de paquete que soportamos, consulta la sección "[Acerca del gráfico de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
+{% data variables.product.prodname_dotcom %} limita su soporte para alertas de vulnerabilidades a un conjunto de ecosistemas donde podemos proporcionar datos procesables de alta calidad. Las vulnerabilidades que se seleccionan para la{% data variables.product.prodname_advisory_database %}, la gráfica de dependencias, {% if currentVersion == "free-pro-team@latest" %} las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} {% endif %}y las alertas del {% data variables.product.prodname_dependabot %}, se proporcionan para varios ecosistemas, incluyendo Maven de java, npm y Yarn de JavaScript, NuGet de .NET, pip de Python, RubyGems de Ruby y Composer de PHP. Seguiremos agregando soporte para más ecosistemas a la larga. Para obtener una vista general de los ecosistemas de paquete que soportamos, consulta la sección "[Acerca del gráfico de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
 
-Vale la pena señalar que podrían existir [Asesorías de Seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) para otros ecosistemas. La información en una asesoría de seguridad la porporcionan los mantenedores de un repositorio específico. Estos datos no se organizan de la misma forma que la información para los ecosistemas compatibles.
+No vale de nada que las Asesorías de Seguridad de {% data variables.product.prodname_dotcom %} pudiese existir para otros ecosistemas. La información en una asesoría de seguridad la porporcionan los mantenedores de un repositorio específico. Estos datos no se organizan de la misma forma que la información para los ecosistemas compatibles. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}
 
 **Verifica**: ¿Acaso la vulnerabilidad que no se detectó aplica a algún ecosistema no compatible?
 
@@ -36,9 +36,9 @@ Vale la pena señalar que podrían existir [Asesorías de Seguridad de {% data v
 
 La gráfica de dependencias incluye información sobre las dependencias, la cual se declara explícitamente en tu ambiente. Esto es, dependencias que se especifican en un manifiesto o en un lockfile. La gráfica de dependencias también incluye dependencias transitivas generalmente, aún cuando no se especifican en un lockfile, mediante la revisión de las dependencias de las dependencias en un archivo de manifiesto.
 
-Las {% data variables.product.prodname_dependabot_alerts %} te asesoran sobre las dependencias que debes actualizar, incluyendo aquellas transitivas en donde la versión se puede determinar desde un manifiesto o lockfile. Las alertas de seguridad de {% data variables.product.prodname_dependabot %} solo sugieren un cambio en donde puedan "arreglar" directamente la dependencia, esto es cuando estas son:
+Las {% data variables.product.prodname_dependabot_alerts %} te asesoran sobre las dependencias que debes actualizar, incluyendo aquellas transitivas en donde la versión se puede determinar desde un manifiesto o lockfile. {% if currentVersion == "free-pro-team@latest" %}Las {% data variables.product.prodname_dependabot_security_updates %} solo sugieren un cambio donde el {% data variables.product.prodname_dependabot %} pueda "arreglar" la dependencia directamente, es decir, cuando estas son:
 * Dependencias directas declaradas explícitamente en un manifiesto o lockfile
-* Dependencias transitivas declaradas en un lockfile
+* Dependencias transitorias declaradas en un archivo de bloqueo{% endif %}
 
 La gráfica de dependencias no incluye las dependencias "sueltas". Las dependencias "sueltas" son archivos individuales que se copian de otra fuernte y se revisan directamente en el repositorio o dentro de un archivo (tal como un archivo ZIP o JAR) en ves de que se referencien en un manifiesto de paquete de administrador o en un lockfile.
 
@@ -84,6 +84,7 @@ Algunas herramientas de terceros utilizan datos de CVE sin organizar y no las ve
 
 Ya que {% data variables.product.prodname_dependabot %} utiliza datos organizado en la {% data variables.product.prodname_advisory_database %}, la cantidad de alertas podría ser menor, pero las alertas que sí recibas serán exactas y relevantes.
 
+{% if currentVersion == "free-pro-team@latest" %}
 ### ¿Acaso cada vulnerabilidad de la dependencia genera una alerta separada?
 
 Cuadno una dependencia tiene vulnerabilidades múltiples, solo se genera una alerta agregada para esta dependencia en vez de una por cada vulnerabilidad.
@@ -97,10 +98,11 @@ Cuando das clic para mostrar los detalles de la alerta puedes ver cuántas vulne
 ![Vulnerabilidades múltiples para una alerta de {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
 **Verifica**: Si hay una discrepancia en la cantidad total que ves, verifica si no estás comparando la cantidad de alertas con la cantidad de vulnerabilidades.
+{% endif %}
 
 ### Leer más
 
 - "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Administrar la configuración de seguridad y análisis de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/es-ES/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/es-ES/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..998b618a9a
--- /dev/null
+++ b/translations/es-ES/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Mejorar la versión de Dependabot.com al Dependabot nativo de GitHub
+intro: Puedes mejorar a un Dependabot nativo de GitHub si fusionas una solicitud de cambios que permitirá a tus dependencias seguir actualizándose.
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot before then.
+
+After that date, any open pull requests from Dependabot Preview will remain open, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations.
+
+{% endwarning %}
+
+### Acerca de mejorar de una vista previa del Dependabot a un {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}
+
+La vista previa del Dependabot se creó directamente en {% data variables.product.prodname_dotcom %} para que puedas utilizar el {% data variables.product.prodname_dependabot %} junto con el resto de las funcionalidades en {% data variables.product.prodname_dotcom %} sin tener que instalar y utilizar una aplicación por separado. Al migrarte al {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}, también podemos enfocarnos en traer muchas características emocionantes al {% data variables.product.prodname_dependabot %}, incluyendo más [actualizaciones de ecosistema](https://github.com/github/roadmap/issues/150), [notificaciones mejoradas](https://github.com/github/roadmap/issues/133) y compatibilidad del {% data variables.product.prodname_dependabot %} con [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) y [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Diferencias entre la vista previa del Dependabot y el {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}
+
+Si bien la mayoría de las características de la vista previa del Dependabot existen en el {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}, algunas no están disponibles en él:
+- **Actualizaciones en vivo:** Esperamos tenerlas de vuelta pronto. Por el momento, puedes ejecutar el {% data variables.product.prodname_dependabot %} de {% data variables.product.prodname_dotcom %} diariamente para que atrae paquetes al transcurrir un día de su lanzamiento.
+- **Registros de variable de ambiente PHP:** Por ahora, puedes utilizar las {% data variables.product.prodname_actions %} para recuperar dependencias de estos registros.
+- **Fusión automática:** Siempre recomendamos verificar tus dependencias antes de fusionarlas; por lo tanto, la fusión automática no será compatible en el futuro previsible. Para aquellos que vetaron sus dependencias o que solo utilizan las internas, recomendamos agregar aplicaciones de fusión automática de terceros o configurar GitHub Actions para fusionar.
+
+En el {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}, puedes configurar todas las actualizaciones de versión utilizando el archivo de configuración. Este archivo es similar al archivo de configuración de la vista previa de Dependabot con algunos cambios y mejoras que se incluirán automáticamente en su solicitud de extracción de actualización. Para obtener más información sobre la solicitud de cambios de actualziación, consulta la sección "[Actualizar a un Dependabot nativo de GitHub](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+Para ver las bitácoras de actualización del {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %} que se encontraban anteriormente en el tablero de Dependabot.com:
+
+  1. Navega a la página de **Perspectivas** de tu repositorio.
+  2. Haz clic en la **Gráfica de dependencias** a la izquierda.
+  3. Haz clic en **{% data variables.product.prodname_dependabot %}**.
+
+Para obtener más información acerca de las actualizaciones con un {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}, consulta la sección "[Acerca de las actualizaciones de versión del Dependabot](/code-security/supply-chain-security/about-dependabot-version-updates)".
+
+### Actualizar a un {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}
+
+Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} requires you to merge the *Upgrade to GitHub-native Dependabot* pull request in your repository. Esta solicitud de cambios incluye el archivo de configuración actualizado que se requiere para tener un {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}.
+
+If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
+
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
+
+If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/es-ES/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-ES/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index 4550f04697..20683b8664 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-La pestaña de alertas del {% data variables.product.prodname_dependabot %} de tu repositorio lista todas las {% data variables.product.prodname_dependabot_alerts %} abiertas y cerradas, y las {% data variables.product.prodname_dependabot_security_updates %} correspondientes. Puedes clasificar la lista de alertas utilizando el menú desplegable y hacer clic en alertas específicas para obtener más detalles. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
+La pestaña de alertas del {% data variables.product.prodname_dependabot %} de tu repositorio lista todas las {% data variables.product.prodname_dependabot_alerts %} abiertas y cerradas{% if currentVersion == "free-pro-team@latest" %} y las {% data variables.product.prodname_dependabot_security_updates %} correspondientes{% endif %}. Puedes clasificar la lista de alertas utilizando el menú desplegable y hacer clic en alertas específicas para obtener más detalles. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)".
 
+{% if currentVersion == "free-pro-team@latest" %}
 Puedes habilitar las alertas de seguridad automáticas para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)".
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ Puedes habilitar las alertas de seguridad automáticas para cualquier repositori
 ### Acerca de las actualizaciones para las dependencias vulnerables en tu repositorio
 
 {% data variables.product.product_name %} genera {% data variables.product.prodname_dependabot_alerts %} cuando detectamos que tu base de código está utilizando dependencias con vulnerabilidades conocidas. Para los repositorios en donde se habilitan las {% data variables.product.prodname_dependabot_security_updates %} cuando {% data variables.product.product_name %} detecta una dependencia vulnerable en la rama predeterminada, {% data variables.product.prodname_dependabot %} crea una solicitud de cambios para arreglarla. La solicitud de extracción mejorará la dependencia a la versión segura mínima que sea posible y necesaria para evitar la vulnerabilidad.
+{% endif %}
 
 ### Ver y actualizar las dependencias vulnerables
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ Puedes habilitar las alertas de seguridad automáticas para cualquier repositori
 1. Cuando estés listo para actualizar tu dependencia y resolver la vulnerabilidad, fusiona la solicitud de extracción. Cada solicitud de extracción que levante el {% data variables.product.prodname_dependabot %} incluye información sobre los comandos que puedes utilizar para controlar el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Adminsitrar las solicitudes de extracción para las actualizaciones de las dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)".
 1. Opcionalmente, si se está arreglando la alerta, si es incorrecta o si se ubica en una sección de código sin utilizar, utiliza el menú desplegable de "Descartar" y da clic en una razón para descartar la alerta.![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
+{% elsif currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Haz clic en la alerta que quieres ver. ![Alerta seleccionada en la lista de alertas](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. Revisa los detalles de la vulnerabilidad y determina si necesitas actualizar la dependencia o no.
+1. Cuando fusionas una solicitud de cambios que actualice el archivo de manifiesto o de bloqueo a una versión segura de la dependencia, esto resolverá la alerta. Como alternativa, si decides no actualizar la dependencia, haz clic en el menú desplegable **Descartar** y selecciona una razón para descartar la alerta. ![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. Haz clic en el número de versión de la dependencia vulnerable para mostrar la información detallada. ![Información detallada de la dependencia vulnerable](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. Revisa los detalles de la vulnerabilidad y determina si necesitas actualizar la dependencia o no. Cuando fusionas una solicitud de cambios que actualice el archivo de manifiesto o de bloqueo a una versión segura de la dependencia, esto resolverá la alerta.
+1. El letrero en la parte superior de la pestaña de **Dependencias** se muestra hasta que todas las dependencias vulnerables se resuelven o hasta que lo descartes. Haz clic en **Descartar** en la esquina superior derecha del letrero y selecciona una razón para descartar la alerta. ![Descartar el letrero de seguridad](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### Leer más
 
-- "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-- "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"
+- "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
 - "[Administrar la configuración de seguridad y de análisis para tu organización](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
-- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Solucionar problemas de los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/es-ES/content/codespaces/about-codespaces.md b/translations/es-ES/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..1134b14566
--- /dev/null
+++ b/translations/es-ES/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: Acerca de Codespaces
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Acerca de {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![Un codespace abierto](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)".
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Los desarrolladores pueden contribuir desde donde sea, en cualquier máquina, incluyendo tablets o Chromebooks, y no es necesario mantener copias locales o propiedad intelectual. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### Acerca de la facturación para {% data variables.product.prodname_codespaces %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)".
+
+### Unirse al beta
+
+Se invitará a una cantidad limitada de personas para unirse al beta. Para unirse a la lista de espera, consulta la sección [Registrarse para el beta de Codespaces](https://github.com/features/codespaces/signup).
+
+### Contáctanos para conocer sobre {% data variables.product.prodname_codespaces %}
+
+Si encuentras problemas al utilizar {% data variables.product.prodname_codespaces %}, consulta la sección "[Solución de problemas para tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)".
+
+Si aún necesitas ayuda o tienes algún tipo de retroalimentación sobre los {% data variables.product.prodname_codespaces %}, utiliza el debate de [Retroalimentación de los Codespaces](https://github.com/github/feedback/discussions/categories/codespaces-feedback).
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..df3635a3f3
--- /dev/null
+++ b/translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: Acerca de la facturación para Codespaces
+intro: 'Cuando {% data variables.product.prodname_codespaces %} se hace generalmente disponible, se te cobrará por el almacenamiento y uso del procesamiento.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..ef7a9801a5
--- /dev/null
+++ b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Allowing your codespace to access a private image registry
+intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Un registro es un espacio seguro para almacenar y administrar imágenes privadas de contenedores, tales como el Registro de Contenedores de Azure o DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry.
+
+When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)."
+
+For example, if you had a private image registry in Azure, you could create the following secrets:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![Ejemplo de secreto de registro de imagen](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/index.md b/translations/es-ES/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..189d05d357
--- /dev/null
+++ b/translations/es-ES/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: Referencia
+intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..7316dd565b
--- /dev/null
+++ b/translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: Solucionar problemas de tu codespace
+intro: Use this guide to help you troubleshoot common issues with your codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Known Limitations
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### {% data variables.product.prodname_vscode %} troubleshooting
+
+Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.
+
+
+### Configuration troubleshooting
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+Este codespace se ejecuta acutalmente en modo de recuperación debido a un error del contenedor.
+```
+
+Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)".
+
+### dotfiles troubleshooting
+
+- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles.
+- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned.
+  - If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
+  - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
+- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**.
+
+
+### Browser troubleshooting
+
+Si encuentras problemas al utilizar un buscador que no se base en Chromium, intenta cambiar a uno que sí se base en él, o revisa los problemas conocidos de tu buscador en el repositorio `microsoft/vscode` buscando los problemas etiquetados con el nombre del buscador, tales como [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) o [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari).
+
+Si encuentras problemas al utilizar un buscador basado en Chromium, puedes revisar si estás experimentando otro problema conocido con {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues).
+
+### Container storage troubleshooting
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.
+
+- Remove packages that are no longer by using `sudo apt autoremove`
+- Clean the apt cache by using `sudo apt clean`
+- Delete unneeded files like build artifacts and logs (these are very project-dependent)
+- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10`
+
+More destructive options:
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes)
+- Remove untracked files from working tree: `git clean -i`
+
+### Contáctanos
+
+Si aún necesitas ayuda, puedes contactarnos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)".
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..72ed3583d1
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Crear un codespace
+intro: Puedes crear un codespace para una rama en un repositorio para desarrollar en línea.
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Acerca de la creación de codespaces
+
+You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)."
+
+
+When you create a codespace, a number of steps happen to enable full access to your development environment.
+
+- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
+- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
+- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)".
+- Your Docker container, `docker-compose`, or other initialization is run.
+- At this point, the codespace is marked as available and you can connect.
+- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up.
+  - The codespace shares ports added in the `devcontainer.json` file.
+  - The codespace runs anything specified in `postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Finally, the codespace does a full clone of the repo so you have full access to it.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### Crear un codespace
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Debajo del nombre de repositorio, utiliza el menú desplegable de "Rama" y selecciona aquella en la que quieras crear un codespace.
+
+  ![Menú desplegable de rama](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. Debajo del nombre del repositorio, utiliza el menú desplegable {% octicon "download" aria-label="The download icon" %} **Código**, y selecciona **Abrir con codespaces**.
+
+  ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..fbf332118e
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: Borrar un codespace
+intro: Puedes borrar un codespace que ya no necesites.
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+
+2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** ![Botón de borrar](/assets/images/help/codespaces/delete-codespace.png)
+
+### Borrar un codespace en {% data variables.product.prodname_vscode %}
+
+For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)."
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..701478839c
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: Desarrollar en un codespace
+intro: 'Puedes abrir un codespace en {% data variables.product.product_name %} y después desarrollar utilizando las características de {% data variables.product.prodname_vscode %}.'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Acerca del desarrollo con {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Side Bar - By default, this area shows your project files in the Explorer.
+2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
+3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
+4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
+5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
+
+For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta la sección "[Solucionar problemas de tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)".
+
+#### Personalizing your codespace
+
+{% data reusables.codespaces.about-personalization %} Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)".
+
+{% data reusables.codespaces.apply-devcontainer-changes %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)".
+
+#### Running your app from a codespace
+{% data reusables.codespaces.about-port-forwarding %} Para obtener más información, consulta la sección "[Abrir puertos en tu codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)".
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Navigating to an existing codespace
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. Da clic en el nombre del codespace en el cual quieras desarrollar. ![Nombre del codespace](/assets/images/help/codespaces/click-name-codespace.png)
+
+Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..073026b8f2
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Reenviar puertos en tu codespace
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Acerca de los puertos reenviados
+
+La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. Por ejemplo, si estás ejecutando una aplicación web en el puerto 4000, puedes acceder a esta desde tu buscador para probarla y depurarla.
+
+Cuando una aplicación que se ejecuta en un codespace da salida a la consola a un puerto, el {% data variables.product.prodname_codespaces %} detecta el patrón de URL del host local y reenvía el puerto automáticamente. Puedes hacer clic en la URL de la terminal para abrir el puerto en un buscador. Por ejemplo, si una aplicación da como salida `http://127.0.0.1:4000` o `http://localhost:4000` en la consola, la bitácora convertirá la salida automáticamente en una URL para el puerto 4000 en la que se puede dar clic.
+
+![Reenvío automático de puertos](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+También puedes reenviar un puerto manualmente, etiquetar puertos reenviados, compartir puertos reenviados públicamente y agregar puertos reenviados a la configuración del codespace.
+
+### Reenviar un puerto
+
+Puedes reenviar manualmente a un puerto que no se haya reenviado automáticamente.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Debajo de la lista de puertos, haz clic en **Agregar puerto**. ![Botón de agregar puerto](/assets/images/help/codespaces/add-port-button.png)
+1. Teclea el número de puerto o de dirección y luego presiona enter. ![Botón de caja de texto para teclear el puerto](/assets/images/help/codespaces/port-number-text-box.png)
+
+### Etiquetar un puerto
+
+Puedes etiquetar un puerto para hacerlo más fácil de identificar en una lista.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Pasa el mouse sobre el puerto que quieras etiquetar y luego haz clic en el icono de etiqueta. ![Icono de etiqueta para el puerto](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### Compartir un puerto
+
+Si quieres compartir un puerto reenviado con otros, puedes hacerlo público. Después de que lo haces público, cualquiera con la URL del puerto puede ver la aplicación que se ejecuta sin necesidad de autenticarse.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Haz clic derecho en el puerto que quieres compartir y luego en **Hacer público**. ![Opción para hacer el puerto público en el menú de clic derecho](/assets/images/help/codespaces/make-public-option.png)
+1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar. ![Copiar el icono para la URL del puerto](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Envía la URL copiada a la persona con la que quieras compartir el puerto.
+
+### Agregar el peurto a la configuración del codespace
+
+Puedes agregar un puerto reenviado a la configuración de {% data variables.product.prodname_codespaces %} del repositorio para que este pueda reenviarse automáticamente a todos los codespaces que se crearon desde el repositorio. Después de que actualizas la configuración, cualquier codespace creado debe reconstruirse para que el cambio se aplique. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)".
+
+Puedes configurar manualmente los puertos reenviados en un archivo `.devcontainer.json` utilizando la propiedad `forwardPorts` o puedes utilizar el panel "Puertos" en tu codespace.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Haz clic derecho en el puerto que quieras agregar a la configuración del codespace y luego haz clic en **Configurar etiqueta y actualizar devcontainer.json**. ![Opción para configurar una etiqueta y agregar el puerto a devcntainer.json en el menú de clic derecho](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..dfb066d75a
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: Desarrollar en un codespace
+intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..d0361716eb
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: Utilizar codespaces en Visual Studio Code
+intro: 'Puedes desarrollar tu codespace directamente en {% data variables.product.prodname_vscode %} si conectas la extensión de {% data variables.product.prodname_github_codespaces %} con tu cuenta en {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Prerrequisitos
+
+Para hacer desarrollos en un codespace directamente desde {% data variables.product.prodname_vscode %}, debes ingresar en la extensión de {% data variables.product.prodname_github_codespaces %}. La extensión de {% data variables.product.prodname_github_codespaces %} requiere el lanzamiento 1.51 de octubre de 2020 de {% data variables.product.prodname_vscode %} o superior.
+
+Utiliza {% data variables.product.prodname_vs %} Marketplace para instalar la extensión de [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obtener más información, consulta la sección[Extensión de Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) en la documentación de {% data variables.product.prodname_vscode %}.
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Da clic en **Registrarse para ver {% data variables.product.prodname_dotcom %}...**. ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**.
+4. Regístrate en {% data variables.product.product_name %} para aprobar la extensión.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Utiliza el menú desplegable de "REMOTE EXPLORER" y luego da clic en **{% data variables.product.prodname_github_codespaces %}**. ![El encabezado {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. Da clic en **Registrarse para ver {% data variables.product.prodname_codespaces %}...**. ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**.
+5. Regístrate en {% data variables.product.product_name %} para aprobar la extensión.
+
+{% endwindows %}
+
+### Crear un codespace en {% data variables.product.prodname_vscode %}
+
+Despuès de que conectas tu cuenta de {% data variables.product.product_name %} a la extensiòn de {% data variables.product.prodname_github_codespaces %}, puedes desarrollar en un codespace que hayas creado en {% data variables.product.product_name %} o en {% data variables.product.prodname_vscode %}.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Da clic en el icono de Agregar y luego en **Crear codespace nuevo**. ![La opciòn de crear un codespace nuevo en {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. Teclea y luego da clic en el nombre del repositorio en el que quieras desarrollar. ![Buscar un repositorio para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. Da clic en la rama en la que quieras desarrollar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Click the machine type you want to develop in. ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png)
+### Abrir un codespace en {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Debajo de "Codespaces", da clic en el codespace en el que quieras desarrollar.
+3. Da clic en en el icono de conexión al codespace. ![Icono de conectarse al codespace en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### Cambiar el tipo de máquina en {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+Puedes cambiar el tipo de máquina de tu codespace en cualquier momento.
+
+1. En {% data variables.product.prodname_vscode %}, abre la paleta de comandos (`shift command P` / `shift control P`).
+2. Busca y selecciona "Codespaces: Cambiar mi tipo de máquina". ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. Haz clic en el codespace que quieras cambiar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. Elige el tipo de máquina que quieres utilizar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+Si el codespace se está ejecutando actualmente, se mostrará un mensaje que pregunta si te gustaría reiniciar y reconectarte con tu codespace ahora. Haz clic en **Sí** en caso de que quieras cambiar el tipo de máquina que se utiliza para este codespace inmediatamente. Si haces clic en **No** o si el codespace no se está ejecutando actualmente, el cambio se reflejará la próxima vez que este se reinicie.
+
+### Borrar un codespace en {% data variables.product.prodname_vscode %}
+
+1. Debajo de "Codespaces", da clic derecho en el codespace que quieras borrar.
+2. En el menù desplegable, da clic en **Borrar codespace**. ![Borrar un codespace en {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..d0d366c056
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About source control in {% data variables.product.prodname_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+### Creating or switching branches
+
+1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**.
+1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace.
+
+{% endtip %}
+
+### Pulling changes from the remote repository
+
+You can pull changes from the remote repository into your codespace at any time.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. In the drop-down menu, click **Pull**.
+
+If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+### Setting your codespace to automatically fetch new changes
+
+You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
+
+If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
+
+1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Da clic en **Crear**.
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..e16de53875
--- /dev/null
+++ b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Getting started with your C# (.NET) project in Codespaces
+shortTitle: Getting started with your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introducción
+
+This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Prerrequisitos
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Pasos siguientes
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..64329b99cb
--- /dev/null
+++ b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Getting started with your Java project in Codespaces
+shortTitle: Getting started with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introducción
+
+This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Prerrequisitos
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Pasos siguientes
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..3744823d99
--- /dev/null
+++ b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Getting started with your Node.js project in Codespaces
+shortTitle: Getting started with your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introducción
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Prerrequisitos
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Pasos siguientes
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..16eb70b92d
--- /dev/null
+++ b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Getting started with your Python project in Codespaces
+shortTitle: Getting started with your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introducción
+
+This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Prerrequisitos
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Haz clic en **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Pasos siguientes
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..013f96d508
--- /dev/null
+++ b/translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: Getting Started with {% data variables.product.prodname_codespaces %}
+intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/es-ES/content/codespaces/guides.md b/translations/es-ES/content/codespaces/guides.md
new file mode 100644
index 0000000000..b198b99777
--- /dev/null
+++ b/translations/es-ES/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: Guías
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/es-ES/content/codespaces/index.md b/translations/es-ES/content/codespaces/index.md
new file mode 100644
index 0000000000..ddd1109443
--- /dev/null
+++ b/translations/es-ES/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: Acerca de GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc'
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..1034377b45
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing Codespaces for your organization
+intro: 'You can manange and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..52de580868
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Managing access and security for your organization's codespaces
+shortTitle: Managing access and security for your organization
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Organization owners can manage which repositories a codespace can access.
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes.
+
+To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Debajo de "Acceso y seguridad", selecciona la configuración que quieras para tu organización.![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. Si eliges "Repositorios seleccionados"; entonces selecciona el menú desplegable y da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que pertenecen a tu organización. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de los repositorios. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
new file mode 100644
index 0000000000..c94a25d444
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Managing encrypted secrets for your repository and organization for Codespaces
+shortTitle: Managing secrets for your repository and organization
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Límites para los secretos
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+Los secretos tienen un tamaño máximo de 64 KB.
+
+### Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. At the top of the page, click **New repository secret**.
+1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
+1. Ingresa el valor de tu secreto.
+1. Haz clic en **Agregar secreto** (Agregar secreto).
+
+### Adding secrets for an organization
+
+Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos.
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. At the top of the page, click **New organization secret**.
+1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
+1. Ingresa el **Valor** para tu secreto.
+1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+1. Haz clic en **Agregar secreto** (Agregar secreto).
+
+### Revisar el acceso a los secretos de nivel organizacional
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. La lista de secretos incluye cualquier política y permiso configurado. Por ejemplo: ![Lista de secretos](/assets/images/help/settings/actions-org-secrets-list.png)
+1. Para encontrar más detalles sobre los permisos configurados para cada secreto, da clic en **Actualizar**.
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..fee663a78c
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..80521ebbeb
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing your organization's audit logs for Codespaces
+shortTitle: Reviewing your organization's audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+La bitácora de auditoría incluye detalles tales como quién realizó la acción, qué fue esa acción y cuándo se llevó a cabo. Para obtener información sobre las acciones de los {% data variables.product.prodname_codespaces %}, consulta la sección "[acciones de categoría de los {% data variables.product.prodname_codespaces %}](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)".
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..53228a06cf
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Debajo de "Acceso y seguridad"; selecciona la configuración que quieras para tu cuenta de usurio. ![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. Si eliges "Repositorios seleccionados", selecciona el menú desplegable y luego da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que te pertenecen. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de tus repositorios. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..27f1c1b675
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 'Puedes almacenar información sensible, como los tokens, a la cual quieras acceder en tus codespaces en forma de variables de ambiente.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### Acerca de los secretos cifrados para los {% data variables.product.prodname_codespaces %}
+
+Puedes agregar a tu cuenta de usuario los secretos cifrados que quieras utilizar en tus codespaces. Por ejemplo, puede que quieras almacenar y acceder a la siguiente información sensible en forma de un secreto cifrado.
+
+- Tokens de acceso personal para los servicios en la nube
+- Entidades de servicio
+- Identificadores de suscripción
+- [Credenciales para un registro de imagen privada](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+Puedes elegir qué repositorios deben tener acceso a cada secreto. Posteriormente, puedes utilizar el secreto en cualquier codespace que crees para un repositorio que tenga acceso a él.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Límites para los secretos
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+Los secretos tienen un tamaño máximo de 64 KB.
+
+### Agregar un secreto
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. A la derecha de "Secretos de los codespaces", da clic en **Secreto nuevo**. ![Botón de "Secreto nuevo"](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. Debajo de "Nombre", teclea un nombre para tu secreto. ![Caja de texto de "Nombre"](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Haz clic en **Agregar secreto** (Agregar secreto).
+
+### Editar un secreto
+
+Puedes actualizar el valor de un secreto existente y puedes cambiar qué repositorios pueden acceder a un secreto.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Debajo de "Secretos de los codespaces"; a la derecha del secreto que quieras editar, da clic en **Actualizar**. ![Botón de "Actualizar"](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. Debajo de "Valor", da clic en **Ingresar un valor nuevo**. ![Enlace de "Ingresar un valor nuevo"](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Opcionalmente, para eliminar el acceso del secreto a un repositorio, deselecciona el repositorio. ![Casillas de verificación para eliminar el acceso a los repositorios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. Haz clic en **Guardar cambios**.
+
+### Borrar un secreto
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Debajo de "Secretos de los codespaces", a la derecha del secreto que quieras borrar, da clic en **Borrar**. ![Botón de "Borrar"](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. Lee la advertencia y da clic en **OK**. ![Confirmación para borrar un secreto](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..53853f7633
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: Administrar la verificación de GPG para los Codespaces
+intro: 'Puedes permitir que {% data variables.product.company_short %} utilice automáticamente GPG para firmar las confirmaciones que haces en tus codespaces para que otras personas puedan tener la confianza de que los cambios vienen de una fuente confiable.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Después de que habilitas la verificación de GPG, {% data variables.product.company_short %} firmará automáticamente las confirmaciones que hagas en los {% data variables.product.prodname_codespaces %} y éstas tendrán un estado de verificado en {% data variables.product.product_name %}. Predeterminadamente, la verificación GPG se encuentra inhabilitada para los codespaces que creas. Puedes elegir permitir la verificación de GPG para todos los repositorios o para repositorios específicos. Habilita la verificación GPG únicamente para los repositorios en los cuales confías. Para obtener más información acerca de las confirmaciones firmadas por {% data variables.product.product_name %}, consulta la sección "[Acerca de la verificación de firmas de las confirmaciones](/github/authenticating-to-github/about-commit-signature-verification)".
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Debajo de "verificación GPG", selecciona la configuración que quieras para la verificación de GPG. ![Botones radiales para administrar la verificación GPG](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. Si eliges "Repositorios seleccionados"; selecciona el menú desplegable y luego da clic en el repositorio para el cual quieras habilitar la verificación de GPG. Repite esto para todos los repositorios en los cuales quieras habilitar la verificación GPG. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..f01f139467
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. Para obtener más información sobre acceder a la bitácora, consulta la sección "[Revisar tu bitácora de seguridad](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)".
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+La bitácora de seguridad incluye detalles de qué acción ocurrió y cuándo la realizaste. Para obtener información sobre las acciones de los {% data variables.product.prodname_codespaces %}, consulta la sección "[acciones de categoría de los {% data variables.product.prodname_codespaces %}](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
diff --git a/translations/es-ES/content/codespaces/quickstart.md b/translations/es-ES/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..976db545a0
--- /dev/null
+++ b/translations/es-ES/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introducción
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. Debajo del nombre del repositorio, utiliza el menú desplegable {% octicon "download" aria-label="The download icon" %} **Código**, y selecciona **Abrir con codespaces**.
+
+  ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..31c2022cee
--- /dev/null
+++ b/translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,141 @@
+---
+title: Configurar Codespaces para tu proyecto
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### Dockerfile
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace con una imagen base de Linux. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. Haz clic en la definición que quieras utilizar. ![Lista de definiciones de contenedores predefinidas](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Sigue los mensajes para personalizar tu definición.
+1. Haz clic en **OK** (aceptar). ![Botón de OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. Para aplicar los cambios, en la esquina inferior derecha de la pantalla, haz clic en **Reconstruir ahora**. Para obtener más información sbre reconstruir tu contenedor, consulta la sección "[Acplicar los cambios a tu configuración](#applying-changes-to-your-configuration)". !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### Crear una configuración personalizada para un codespace
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+Puedes definir la configuración predeterminada del editor para {% data variables.product.prodname_vscode %} en dos lugares.
+
+* La configuración del editor que se definió en `.vscode/settings.json` se aplica como una configuración con alcance de _Workspace_- en este codespace.
+* La configuración del editor que se definió en la clave `settings` en `devcontainer.json` se aplica como una configuración con alcance de _Remote [Codespaces]_ en este codespace.
+
+Después de actualizar el archivo `devcontainer.json`, puedes reconstruir el contenedor para que tu codespace aplique los cambios. Para obtener más información, consulta la sección "[Aplicar cambios a tu configuración](#applying-changes-to-your-configuration)".
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### Aplicar cambios a tu configuración
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}!["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} Arreglar los errores en la configuración. ![Mensaje de error sobre el modo de recuperación](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - Para diagnosticar el error revisando la bitácora de creación, haz clic en **Ver bitácora de creación**.
+   - Para arreglar los errores que se identificaron en las bitácoras, actualiza tu archivo `devcontainer.json`.
+   - Para aplicar los cambios, vuelve a crear tu contenedor. {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/es-ES/content/codespaces/setting-up-your-codespace/index.md b/translations/es-ES/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/es-ES/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..4a36bf22b9
--- /dev/null
+++ b/translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: Personalizar Codespaces para tu cuenta
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+Los mantenendores de proyecto también pueden definir una configuración predeterminada que aplique a cada codespace para un repositorio que cree alguien más. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)".
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+Los Dotfiles son archivos y carpetas de sistemas parecidos a Unix que comienzan con `.` y que controlan la configuración de aplicaciones y shells de tu sistema. Puedes alamacenar y administrar tus dotfiles en un repositorio en {% data variables.product.prodname_dotcom %}. Para encontrar consejos y tutoriales sobre qué incluir en tu repositorio de `dotfiles`, consulta la sección [GitHub maneja dotfiles](https://dotfiles.github.io/).
+
+Si tu cuenta de usuario en {% data variables.product.prodname_dotcom %} es propietaria de un repositorio público llamado `dotfiles`, {% data variables.product.prodname_dotcom %} utilizará este repositorio automáticamente para personalizar el ambiente de tu codespace. Actualmente, no son compatibles los repositorios `dotfiles` privados.
+
+Tu repositorio `dotfiles` puede incluir los alias de tu shell y tus preferencias, cualquier herramienta que quieras instalar, o cualquier otra personalización del codespace que quieras hacer.
+
+Cuando creas un codespace nuevo, {% data variables.product.prodname_dotcom %} clona tu repositorio `dotfiles` hacia el ambiente del codespace, y busca uno de los siguientes archivos para configurar el ambiente.
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+Si no encuentra alguno de estos archivos, entonces cualquier archivo o carpeta en `dotfiles` que comience con `.` se enlazará simbólicamente al directorio `~` o `$HOME` del codespace.
+
+Cualquier cambio a tu repositorio `dotfiles` se aplicará únicamente a cada codespace nuevo, y no afectará a ningún codespace existente.
+
+{% note %}
+
+**Nota:** Actualmente, {% data variables.product.prodname_codespaces %} no es compatible con la personalización de la configuración de _Usuario_ para el editor de {% data variables.product.prodname_vscode %} con tu repositorio de `dotfiles`. Puedes configurar ajustes predeterminados de _Workspace_ y _Remote [Codespaces]_ para un proyecto específico en el repositorio de éste. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)".
+
+{% endnote %}
+
+También puedes configurar los ajustes para que tu cuenta de usuario agregue secretos cifrados, habilite la verificación de GPG y permita a tus codespaces acceder a otros repositorios. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Administrar la verificación de GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", y "[Ad,omostrar el acceso y la seguridad para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)".
+
+### Leer más
+
+* "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)".
diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md
index 951ba6f5ae..8f3f32e162 100644
--- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ Con las wikis, puedes escribir contenido como en cualquier otro lado en {% data
 
 Puedes editar las wikis directamente en {% data variables.product.product_name %} o puedes editar los archivos wiki localmente. Predeterminadamente, solo las personas con acceso a tu repositorio podrán hacer cambios a los wikis, aunque podrás permitir que cualquiera en {% data variables.product.product_location %} colabore con un wiki en {% if currentVersion == "github-ae@latest" %}un repositorio interno{% else %}un repositorio público{% endif %}. Para obtener más información, consulta "[Cambiar permisos de acceso para wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)".
 
+{% note %}
+
+**Nota:** Los motores de búsqueda no indizarán el contenido de los wikis. Para que tu contenido se indice en los motores de búsqueda, puedes utilizar [{% data variables.product.prodname_pages %}](/pages) en un repositorio público.
+
+{% endnote %}
+
 ### Leer más
 
 - "[Agregar o eliminar páginas wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/index.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/index.md
index 1ccd7ec451..1a3f2d436e 100644
--- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/index.md
+++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/index.md
@@ -1,6 +1,6 @@
 ---
 title: Documentar tu proyecto con wikis
-shortTitle: Using wikis
+shortTitle: Utilizar wikis
 intro: Puedes usar una wiki para compartir información detallada en forma completa acerca de tu proyecto.
 redirect_from:
   - /categories/49/articles/
diff --git a/translations/es-ES/content/communities/index.md b/translations/es-ES/content/communities/index.md
index 0335bf69f2..a3664f4932 100644
--- a/translations/es-ES/content/communities/index.md
+++ b/translations/es-ES/content/communities/index.md
@@ -1,5 +1,5 @@
 ---
-title: Building communities
+title: Crear comunidades
 intro: 'Más allá de que tu proyecto sea de código abierto o privado, puedes generar un entorno saludable y eficaz para la colaboración.'
 redirect_from:
   - /categories/building-a-strong-community
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index 60d1bd0721..89a6c2f375 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ En los repositorios de tu organización, los usuarios bloqueados tampoco podrán
 ### Bloquear a un usuario en los parámetros de la organización
 
 1. Para bloquear a un miembro de la organización, primero [elimina al usuario](/articles/removing-a-member-from-your-organization) desde la organización.
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. En "Block a user" (Bloquear a un usuario), escribe el nombre de usuario del usuario que deseas bloquear. ![Campo Username (Nombre de usuario)](/assets/images/help/organizations/org-block-username-field.png)
 7. Si deseas establecer un límite de tiempo para el bloqueo, usa el menú desplegable Block options (Bloquear opciones), y selecciona el período que deseas bloquear al usuario. ![Menú desplegable con las opciones de bloqueo](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
index 7fe6118c00..fc593c16f6 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
@@ -74,7 +74,7 @@ Utiliza {% data variables.contact.report_abuse %} para contactarnos si te están
 
 - "[Ver usuarios que has bloqueado de tu cuenta personal](/communities/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account)"
 - "[Desbloquear a un usuario desde tu cuenta personal](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
+- "[Bloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
 - "[Desbloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
 - "[Informar abuso o spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
 - "[Limitar interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)"
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/index.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/index.md
index 7f937f4a89..c9edf97089 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/index.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/index.md
@@ -1,6 +1,6 @@
 ---
 title: Mantener tu seguridad en GitHub
-shortTitle: Maintaining safety
+shortTitle: Mantener la seguridad
 intro: 'Para construir un ambiente seguro y positivo para ti y para la comunidad de tu proyecto en {% data variables.product.prodname_dotcom %}, puedes bloquear y desbloquear a los usuarios y reportar el contenido ofensivo.'
 redirect_from:
   - /articles/encouraging-positive-contributions-in-your-organization
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index 930498dc13..1e42ec520c 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,15 +28,15 @@ Si seleccionaste una cantidad de tiempo específica para bloquear al usuario, se
 
 ### Desbloquear un usuario en los parámetros de la organización
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). ![Botón Unblock user (Desbloquear usuario)](/assets/images/help/organizations/org-unblock-user-button.png)
 
 ### Leer más
 
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
+- "[Bloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
 - "[Bloquear a un usuario desde tu cuenta personal](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
 - "[Desbloquear a un usuario desde tu cuenta personal](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
 - "[Informar abuso o spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
index e69d29a25f..7eb2c55632 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
@@ -37,6 +37,6 @@ Puedes desbloquear un usuario en los parámetros de tu cuenta o desde la página
 ### Leer más
 
 - "[Bloquear a un usuario desde tu cuenta personal](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
+- "[Bloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
 - "[Desbloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
 - "[Informar abuso o spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
diff --git a/translations/es-ES/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/es-ES/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index 33fa38c10b..45fb1a970f 100644
--- a/translations/es-ES/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/es-ES/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,14 +10,14 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que fueron bloqueados de tu organización. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users-for-org.png)
 
 ### Leer más
 
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
+- "[Bloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
 - "[Desbloquear a un usuario de tu organización](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
 - "[Ver usuarios que has bloqueado de tu cuenta personal](/articles/viewing-users-you-ve-blocked-from-your-personal-account)"
diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md
index abe92b379c..d5b04c1921 100644
--- a/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md
+++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md
@@ -1,6 +1,6 @@
 ---
 title: Moderar comentarios y conversaciones
-shortTitle: Moderation
+shortTitle: Moderación
 intro: 'Moderar las conversaciones crea una comunidad amigable para todos los colaboradores de tu proyecto al promover la colaboración saludable y disminuir la intensidad del conflicto. Puedes aplicar el código de conducta de tu comunidad a las discusiones viendo el contenido reportado, editando y eliminando comentarios, y fijando conversaciónes.'
 redirect_from:
   - /articles/moderating-comments-and-conversations
diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index 3efc389313..2ed70beb29 100644
--- a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -28,9 +28,9 @@ Los propietarios de la organización también pueden bloquear a los usuarios por
 
 ### Limitar las interacciones en tu organización
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Enla barra lateral de configuración de la organización, da clic en **Configuración de moderación**. !["Configuración de moderación" en la barra lateral de configuración de la organización](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. Debajo de "Configuración de moderación", da clic en **Límites de interacción**. !["Límites de interacción" en la barra lateral de configuración de la organización](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 2618d2ec1f..db808ed45d 100644
--- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -29,14 +29,14 @@ Los archivos predeterminados no están incluidos en los clones, paquetes ni desc
 
 Puedes crear versiones predeterminadas en tu cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %} para los siguientes archivos de salud de la comunidad:
 
-| Archivo de salud de la comunidad                                                                                                                                                                                      | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| Archivo de salud de la comunidad                                                                                                                                                                                      | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
 | *CODE_OF_CONDUCT.md*                                                                                                                                                                                                | Un archivo CODE_OF_CONDUCT define las normas para participar en una comunidad. Para obtener más información, consulta "[Agregar un código de conducta a tu proyecto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %}
 | *CONTRIBUTING.md*                                                                                                                                                                                                     | Un archivo CONTRIBUTING comunica cómo pueden contribuir las personas con tu proyecto. Para obtener más información, consulta la sección "[Configurar lineamientos para los colaboradores del repositorio](/articles/setting-guidelines-for-repository-contributors/)".{% if currentVersion == "free-pro-team@latest" %}
 | *FUNDING.yml*                                                                                                                                                                                                         | Un archivo FUNDING muestra un botón de patrocinador en tu repositorio para aumentar la visibilidad de las opciones de financiación para tu proyecto de código abierto. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %}
-| Plantillas de propuestas y solicitudes de cambio{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y *config.yml*{% endif %} | Las plantillas de propuestas y solicitudes de extracción personalizan y estandarizan la información que quieres que incluyan los colaboradores cuando abren propuestas y solicitudes de extracción en tu repositorio. Para obtener más información, consulta la sección "[Acerca de las plantillas de propuestas y solicitudes de extración](/articles/about-issue-and-pull-request-templates/)".{% if currentVersion == "free-pro-team@latest" %}
-| *SECURITY.md*                                                                                                                                                                                                         | Un archivo SECURITY da indicaciones para informar responsablemente acerca de una vulnerabilidad de seguridad en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/articles/adding-a-security-policy-to-your-repository)".{% endif %}
-| *SUPPORT.md*                                                                                                                                                                                                          | Un archivo SOPPORT les permite a las personas conocer las formas de obtener ayuda con tu proyecto. Para obtener más información, consulta "[Agregar recursos de soporte a tu proyecto](/articles/adding-support-resources-to-your-project/)."                                                                                                                                                                                                      |
+| Plantillas de propuestas y solicitudes de cambio{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y *config.yml*{% endif %} | Las plantillas de propuestas y solicitudes de extracción personalizan y estandarizan la información que quieres que incluyan los colaboradores cuando abren propuestas y solicitudes de extracción en tu repositorio. Para obtener más información, consulta la sección "[Acerca de las plantillas de propuestas y solicitudes de extración](/articles/about-issue-and-pull-request-templates/)".{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| *SECURITY.md*                                                                                                                                                                                                         | A SECURITY file gives instructions for how to report a security vulnerability in your project. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)".{% endif %}
+| *SUPPORT.md*                                                                                                                                                                                                          | Un archivo SOPPORT les permite a las personas conocer las formas de obtener ayuda con tu proyecto. Para obtener más información, consulta "[Agregar recursos de soporte a tu proyecto](/articles/adding-support-resources-to-your-project/)."                                                                                                                                                                                                                                                       |
 
 No puedes crear un archivo de licencia predeterminado. Los archivos de licencia se deben agregar a repositorios individuales, de manera que el archivo se incluirá cuando el proyecto se clone, se coloque dentro de un paquete o se descargue.
 
diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/index.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/index.md
index f4e7ebecc0..998369a7b3 100644
--- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/index.md
+++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/index.md
@@ -1,6 +1,6 @@
 ---
 title: Configurar tu proyecto para contribuciones saludables
-shortTitle: Healthy contributions
+shortTitle: Contribuciones saludables
 intro: Los mantenedores del repositorio pueden configurar pautas de contribuciones para ayudar a los colaboradores a hacer contribuciones significativas y útiles a tu proyecto.
 redirect_from:
   - /articles/helping-people-contribute-to-your-project/
diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index 447882684a..2ae75e86bc 100644
--- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-Para ayudar a los colaboradores de tu proyecto a realizar un buen trabajo, puedes agregar un archivo con las pautas de colaboración a la raíz del repositorio de tu proyecto, carpeta `docs`, o `.github`. Cuando alguien abre una solicitud de extracción o crea una propuesta, verán un enlace a ese archivo.
+### About contributing guidelines
+Para ayudar a los colaboradores de tu proyecto a realizar un buen trabajo, puedes agregar un archivo con las pautas de colaboración a la raíz del repositorio de tu proyecto, carpeta `docs`, o `.github`. Cuando alguien abre una solicitud de extracción o crea una propuesta, verán un enlace a ese archivo. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ Puedes crear lineamientos de colaboración predeterminados para tu cuenta de org
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. Decide si almacenar tus pautas de contribución en la raíz de tu repositorio, el directorio `docs`, o el directorio `.github`. Después, en el campo nombre de archivo, escribe el nombre y la extensión del archivo. Los nombres de archivos de las pautas de contribución no distinguen entre mayúsculas y minúsculas y pueden tener una extensión *.md* o *.txt*. ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png)
+3. Decide si almacenar tus pautas de contribución en la raíz de tu repositorio, el directorio `docs`, o el directorio `.github`. Después, en el campo nombre de archivo, escribe el nombre y la extensión del archivo. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png)
     - Para hacer visibles tus pautas de contribución en el directorio raíz del repositorio, escribe *CONTRIBUTING*.
     - Para hacer visibles tus pautas de contribución en el directorio `docs` del repositorio, escribe *docs/* para crear el nuevo directorio, y luego *CONTRIBUTING*.
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. En el nuevo archivo, agrega las pautas de contribución. Pueden incluir:
     - Pasos para crear buenas propuestas o solicitudes de extracción.
     - Enlaces a la documentación externa, listas de correos o un código de conducta.
diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
index 642e052ebe..3d454302e8 100644
--- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
+++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles
-shortTitle: Issue & PR templates
+shortTitle: Plantillas de propuestas & solicitudes de cambio
 intro: Los mantenedores del repositorio pueden agregar plantillas en un repositorio para ayudar a los contribuyentes a crear propuestas y solicitudes de extracción de alta calidad.
 redirect_from:
   - /github/building-a-strong-community/using-issue-and-pull-request-templates
diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md
index f21eeaf033..eb64538569 100644
--- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md
+++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md
@@ -1,22 +1,22 @@
 ---
-title: Cherry-picking a commit
-intro: You can pick a specific commit on one branch and copy the commit to another branch.
+title: Escoger una confirmación minuciosamente
+intro: Puedes escoger una confirmación específica en una rama y copiarla a otra rama.
 versions:
   free-pro-team: '*'
 ---
 
-### About Git cherry-pick
+### Acerca de la selección minuciosa de Git
 
-You can cherry-pick a commit on one branch to create a copy of the commit with the same changes on another branch. If you commit changes to the wrong branch or want to make the same changes to another branch, you can cherry-pick the commit to apply the changes to another branch. You can also use cherry-picking to apply specific changes before you are ready to create or merge a pull request. For example, if you commit a bug fix to a feature branch, you can cherry-pick the commit with the bug fix to other branches of your project.
+Puedes elegir minuciosamente una confirmación en una rama para crear una copia de la confirmación con los mismos cambios en otra rama. Si tu confirmación cambia a la rama incorrecta o quiere hacer los mismos cambios en otra rama, puedes elegir minuciosamente la confirmación para aplicar los cambios en otra rama. También puedes utilizar la selección minuciosa para aplicar cambios específicos antes de que estés listo para crear o fusionar la solicitud de cambios,. Por ejemplo, si confirmas una corrección de error en una rama de característica, puedes seleccionar minuciosamente la confirmación con el arreglo del error en otras ramas de tu proyecto.
 
-You can also use cherry-picking when collaborating with a team. Some projects incorporate contributions by cherry-picking commits. For more information, see [Distributed Git - Maintaining a Project](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_rebase_cherry_pick) in the Git documentation.
+También puedes usar la selección minuciosa para colaborar con un equipo. Algunos proyectos incorporan colaboraciones por confirmaciones de selección minuciosa. Para obtener más información, consulta la sección [Git Distribuido - Mantener un Proyecto](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_rebase_cherry_pick) en la documentación de Git.
 
-### Cherry-picking a commit
+### Escoger una confirmación minuciosamente
 
 {% data reusables.desktop.current-branch-menu %}
-2. In the list of branches, click the branch that has the commit that you want to cherry-pick.
+2. En la lista de ramas, haz clic en aquella que tiene la confirmación que quieres seleccionar minuciosamente.
 {% data reusables.desktop.history-tab %}
-4. Drag the commit that you want to cherry-pick to the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** menu and drop the commit on the branch that you want to copy the commit to. ![Dragging a commit to another branch in the Current Branch menu](/assets/images/help/desktop/cherry-picking.png)
+4. Arrastra la confirmación que quieres seleccionar minuciosamente al {% octicon "git-branch" aria-label="The branch icon" %} menú de **Rama Actual** y suelta la confirmación en la rama en la que quieres copiar la confirmación. ![Arrastrar una confirmación a otra rama en el menú de la rama actual](/assets/images/help/desktop/cherry-picking.png)
 
 ### Leer más
-- [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation
+- [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) en la documentación de Git
diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md
index d210c8a419..617920d125 100644
--- a/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/es-ES/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -59,9 +59,9 @@ Se redirigirá al creador de la app a una página de GitHub en donde encontrará
  | `name (nombre)`       | `secuencia`              | El nombre dela GitHub App.                                                                                                                                                                                                                                      |
  | `url`                 | `secuencia`              | **Requerido.** La página principal de tu GitHub App.                                                                                                                                                                                                            |
  | `hook_attributes`     | `objeto`                 | La configuración del webhook de la GitHub App.                                                                                                                                                                                                                  |
- | `redirect_url`        | `secuencia`              | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
- | `callback_urls`       | `conjunto de secuencias` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %}
- | `callback_url`        | `secuencia`              | A full URL to redirect to after someone authorizes an installation.{% endif %}
+ | `redirect_url`        | `secuencia`              | La URL completa a donde se debe redirigir a un usuario cuando inicia la creación de una GitHub App desde un manifiesto.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
+ | `callback_urls`       | `conjunto de secuencias` | Una URL completa a la cual redirigir cuando alguien autorice una instalación. Puedes proporcionar hasta 10 URL de rellamado.{% else %}
+ | `callback_url`        | `secuencia`              | Una URL completa a la cual redirigir cuando alguien autoriza una instalación.{% endif %}
  | `descripción`         | `secuencia`              | Una descripción de la GitHub App.                                                                                                                                                                                                                               |
  | `public`              | `boolean`                | Configúralo como `true` cuando tu GitHub App esté disponible al público o como `false` si solo puede acceder el propietario de la misma.                                                                                                                        |
  | `default_events`      | `arreglo`                | La lista de [eventos](/webhooks/event-payloads) a la cual se suscribe la GitHub App.                                                                                                                                                                            |
@@ -179,7 +179,7 @@ Tienes solo una hora para completar este paso en el flujo del Manifiesto de la G
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 Para obtener más información acerca de la respuesta de la terminal, consulta la sección [Crear una GitHub App desde un manifiesto](/rest/reference/apps#create-a-github-app-from-a-manifest).
 
diff --git a/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md
index 2866f14271..4911a09c3e 100644
--- a/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/es-ES/content/developers/apps/creating-a-github-app-using-url-parameters.md
@@ -16,7 +16,7 @@ topics:
 
 Puedes agregar parámetros de consulta a estas URL para preseleccionar la configuración de una {% data variables.product.prodname_github_app %} en una cuenta organizacional o personal:
 * **Cuenta de usuario:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
-* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+* **Cuenta organizacional:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
 
 El creador de la app puede editar los valores preseleccionados desde la página de registro de la {% data variables.product.prodname_github_app %} antes de emitirla. Si no incluyes los parámetros requeridos en la secuencia de consulta de la URL, como el `name`, el creador de la app necesitará ingresar un valor antes de emitirla.
 
@@ -40,9 +40,9 @@ La lista completa de parámetros de consulta, permisos y eventos disponibles se
  | -------------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | `name (nombre)`            | `secuencia`              | El nombre de la {% data variables.product.prodname_github_app %}. Pónle un nombre claro y breve a tu app. Tu app no puede tener el mismo nombre que un usuario de GitHub, a menos de que sea tu propio nombre de usuario u organización. Una versión simplificada del nombre de tu aplicación se mostrará en la interface de usuario cuando tu integración tome alguna acción.                                                                                                                                                                                                                                             |
  | `descripción`              | `secuencia`              | Una descripción de la {% data variables.product.prodname_github_app %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
- | `url`                      | `secuencia`              | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
- | `callback_urls`            | `conjunto de secuencias` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %}
- | `callback_url`             | `secuencia`              | La URL completa a la cual se redirigirá después de que alguien autorice la instalación. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %}
+ | `url`                      | `secuencia`              | La URL completa de tu página principal del sitio web de la {% data variables.product.prodname_github_app %}.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
+ | `callback_urls`            | `conjunto de secuencias` | Una URL completa a la cual redirigir cuando alguien autorice una instalación. Puedes proporcionar hasta 10 URL de rellamado. Estas URL se utilizan si tu app necesita identificar y autorizar solicitudes de usuario a servidor. Por ejemplo, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %}
+ | `callback_url`             | `secuencia`              | La URL completa a la cual se redirigirá después de que alguien autorice la instalación. Esta URL se utiliza si tu app necesita identificar y autorizar solicitudes de usuario a servidor.{% endif %}
  | `request_oauth_on_install` | `boolean`                | Si tu app autoriza a los usuarios mediante el flujo de OAuth, puedes configurar esta opción como `true` para permitir que las personas autoricen la app cuando la instalen, lo cual te ahorra un paso. Si seleccionas esta opción, la `setup_url` deja de estar disponible y se redirigirá a los usuarios a tu `callback_url` después de que instalen la app.                                                                                                                                                                                                                                                                |
  | `setup_url`                | `secuencia`              | La URL completa a la cual se redirigirá después de que instalen la {% data variables.product.prodname_github_app %} si ésta requiere de alguna configuración adicional después de su instalación.                                                                                                                                                                                                                                                                                                                                                                                                                          |
  | `setup_on_update`          | `boolean`                | Configúralo como `true` para redireccionar a las personas a la URL de ajustes cuando las instalaciones se actualicen, por ejemplo, después de que se agreguen o eliminen repositorios.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
diff --git a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index b07d1fcf51..75e9efc871 100644
--- a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ Agregarás este método nuevo como un [Ayudante de Sinatra](https://github.com/s
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-Este código llama a la terminal "[Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run)" utilizando el [Método HTTP de `publicación`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method) genérico. Este método toma dos parámetros: la URL de la terminal y los parámetros de entrada del método.
+Este código llama a la terminal "[Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run)" utilizando el [método create_check-run](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
 
 Solo se requieren dos parámetros de entrada para crear una ejecución de flujo de trabajo: `name` y `head_sha`. Utilizaremos a [Rubocop](https://rubocop.readthedocs.io/en/latest/) para implementar la prueba de IC más adelante en esta guía de inicio rápido, y esto es por lo que se utiliza el nombre "Octo Rubocop" aquí, pero puedes elegir cualquier nombre que quieras para la ejecución de verificación.
 
@@ -240,31 +235,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -276,40 +262,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-El código anterior llama a la terminal "[Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run)" de la API utilizando el [Método HTTP`patch`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) para actualizar la ejecución de verificación que ya creaste.
+El código anterior llama a la terminal de la API "[Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run)" utilizando el [método del Octokit `update_check_run`](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) para actualizar la ejecución de verificación que ya creaste.
 
-Te explicamos lo que hace este código. Primero, actualiza el estado de la ejecución de verificación a `in_progress` y configura la hora `started_at` de acuerdo con la hora actual. En la [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) de esta guía de inicio rápido, agregarás el código que lanza una prueba de IC real bajo `***** RUN A CI TEST *****`. Por el momento, dejarás esta sección como un marcador de posición para que el código subsecuente simplemente estimule el éxito del proceso de IC y que todas las pruebas pasen. Por último, el código actualiza el estado de la ejecución de verificación nuevamente como `completed`.
+Te explicamos lo que hace este código. Primero, actualiza el estado de la ejecución de verificación a `in_progress` y configura implícitamente la hora `started_at` de acuerdo con la hora actual. En la [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) de esta guía de inicio rápido, agregarás el código que lanza una prueba de IC real bajo `***** RUN A CI TEST *****`. Por el momento, dejarás esta sección como un marcador de posición para que el código subsecuente simplemente estimule el éxito del proceso de IC y que todas las pruebas pasen. Por último, el código actualiza el estado de la ejecución de verificación nuevamente como `completed`.
 
 Notarás en los documentos de "[Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run)" que, cuando proporcionas un estado de `completed`, se requieren los parámetros de `conclusion` y `completed_at`. La `conclusion` resume el resultado de una ejecución de verificación, la cual se puede mostrar como `success`, `failure`, `neutral`, `cancelled`, `timed_out`, o `action_required`. Vas a configurar la conclusión como `success`, la hora de `completed_at` según la hora actual, y el estado como `completed`.
 
@@ -613,29 +589,23 @@ Ahora tienes toda la información que necesitas para actualizar tu ejecución de
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -645,51 +615,45 @@ Necesitarás actualizar este código para utilizar la variable `conclusion` que
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md b/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md
index 2deeb4b899..86841b0780 100644
--- a/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/es-ES/content/developers/apps/making-a-github-app-public-or-private.md
@@ -23,7 +23,7 @@ Los flujos de las instalaciones públicas tienen una página de llegada para hab
 
 ### Flujo de instalación privada
 
-Los flujos de instalación privada permiten que solo el propietario de la GitHub App pueda instalarla. Aún así, existirá información limitada sobre la GitHub App en una página pública, pero el botón de **Instalar** solo estará disponible para los administradores de la organización o para la cuenta de usuario si dicha GitHub App le pertenece a una cuenta individual. Las GitHub Apps privadas o internas solo se pueden instalar en la cuenta de usuario o de organización del propietario.
+Los flujos de instalación privada permiten que solo el propietario de la GitHub App pueda instalarla. Aún así, existirá información limitada sobre la GitHub App en una página pública, pero el botón de **Instalar** solo estará disponible para los administradores de la organización o para la cuenta de usuario si dicha GitHub App le pertenece a una cuenta individual. Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### Cambiar el quién puede instalar tu GitHub App
 
@@ -34,5 +34,5 @@ Para cambiar quién puede instalar una GitHub App:
 {% data reusables.user-settings.github_apps %}
 3. Selecciona la GitHub App cuya opción de instalación quieras cambiar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. Dependiendo de la opción deinstalación de tu GitHub App, da clic ya sea en **Convertir en pública** o en **Convertir en interna**. ![Botón para cambiar la opción de instalación para tu GitHub App](/assets/images/github-apps/github_apps_make_public.png)
-6. Dependiendo de la opción de instalación de tu GitHub App, da clic ya sea en **Sí, convertir esta GitHub App en pública** o en **Sí, convertir esta GitHub App en interna**. ![Botón para confirmar el cambio de tu opción de instalación](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Botón para cambiar la opción de instalación para tu GitHub App](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Botón para confirmar el cambio de tu opción de instalación](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md b/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md
index 4a6bccce56..7617771c64 100644
--- a/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md
+++ b/translations/es-ES/content/developers/apps/scopes-for-oauth-apps.md
@@ -30,7 +30,7 @@ Verifica los encabezados para ver qué alcances de OAuth tienes, y cuáles acept
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
-HTTP/1.1 200 OK
+HTTP/2 200
 X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
diff --git a/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 007cf00e5e..28cf3c5283 100644
--- a/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/es-ES/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -370,10 +370,10 @@ Después de que des clic en **Instalar**, revisa la salida en tu terminal. Deber
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 ¡Estas son buenas noticias! Esto significa que tu app recibió una notificación de que se instaló en tu cuenta de GitHub. Si ves algo como esto, tu app está ejecutándose en el servidor como lo esperabas. 🙌
diff --git a/translations/es-ES/content/developers/apps/using-content-attachments.md b/translations/es-ES/content/developers/apps/using-content-attachments.md
index 00338099e6..0a4da23a40 100644
--- a/translations/es-ES/content/developers/apps/using-content-attachments.md
+++ b/translations/es-ES/content/developers/apps/using-content-attachments.md
@@ -130,9 +130,8 @@ Para crear una App de Probot, sigue estos pasos:
 2. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. Suscríbete al evento `content_reference` y habilita los permisos de escritura de `content_references`:
 
    ``` yml
-
     default_events:
-    - content_reference
+      - content_reference
     # The set of permissions needed by the GitHub App. The format of the object uses
     # the permission name for the key (for example, issues) and the access type for
     # the value (for example, write).
@@ -141,10 +140,10 @@ Para crear una App de Probot, sigue estos pasos:
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. Agrega este código al archivo `index.js` para gestionar los eventos de `content_reference` y llamar a la API de REST:
diff --git a/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index df9528ba36..262567c74b 100644
--- a/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ Para ofrecer planes de pago para tu app, esta debe pertenecer a una organizació
 
 ### Solicitar la verificación de publicador
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![La opción de configuración de desarrollador en la barra lateral de ajustes de la organización](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Debajo de "Ajustes de desarrollador", da clic en **Verificación del publicador**. ![Opción de verificación del publicador en la barra lateral de ajustes de la organización](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. Debajo de "Verificación del publicador", completa la información de la lista de verificación:
    - Asegúrate de que tu información de perfil básica está presente y es correcta. También, asegúrate de que hayas incluido la mejor dirección de correo electrónico para recibir soporte y actualizaciones de {% data variables.product.company_short %}.
    - Asegúrate de que se encuentre habilitada la autenticación bifactorial para tu organización. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)".
-   - Emite un dominio verificado y asegúrate que se muestre la insignia de "Verificado" en el perfil de página de tu organización. Para la información relacionada, consulta la sección "[Verificar el dominio de tu organización](/organizations/managing-organization-settings/verifying-your-organizations-domain)".
+   - Emite un dominio verificado y asegúrate que se muestre la insignia de "Verificado" en el perfil de página de tu organización. For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![Lista de verificación para la verificación del publicador](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md
index c0d9dfb944..c8dd2dc22f 100644
--- a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md
+++ b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md
@@ -1,9 +1,8 @@
 ---
-title: GitHub Marketplace Overview
-intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.'
+title: Resumen de GitHub Marketplace
+intro: 'Aprende cómo puedes compartir tu app o acción con la comunidad de {% data variables.product.company_short %} en {% data variables.product.prodname_marketplace %}.'
 mapTopic: true
 versions:
   free-pro-team: '*'
 ---
 
-
diff --git a/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index 26542b22c5..1a5bd78c73 100644
--- a/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/es-ES/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ Aquí te mostramos los lineamientos de los campos que necesitas llenar en la sec
 
 #### Nombre del listado
 
-El nombre de tu app se mostrará en la [página de inicio de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). El nombre se limita a 255 caracteres.
+El nombre de tu listado aparecerá en la [página inicial de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). El nombre se limita a 255 caracteres y puede ser diferente que aquél de tu app. Tu publicación no puede tener el mismo nombre que un usuario existente de {% data variables.product.product_name %} a menos de que dicho nombre sea el de tu propio usuario u organización.
 
 #### Descripción muy corta
 
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 53f2471b71..cd3d2947c6 100644
--- a/translations/es-ES/content/developers/overview/managing-deploy-keys.md
+++ b/translations/es-ES/content/developers/overview/managing-deploy-keys.md
@@ -112,35 +112,35 @@ Entonces podrás utilizar el alias del nombre de host para que interactúe con e
 $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
 ```
 
-### Server-to-server tokens
+### Tokens de servidor a servidor
 
-If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents.
+Si tu servidor necesita acceder a repositorios a lo largo de una o más organizaciones, puedes utilizar una GitHub app para definir el acceso que necesitas y luego generar tokens de _alcance limitado_ de _servidor a servidor_ desde dicha GitHub App. Se puede ajustar el alcance de los tokens de servidor a servidor para repositorios múltiples y pueden tener permisos específicos. Por ejemplo, puedes generar un token con acceso de solo lectura al contenido de un repositorio.
 
-Since GitHub Apps are a first class actor on  {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps).
+Ya que las GitHub Apps son un actor de primera clase en {% data variables.product.product_name %}, los tokens de servidor a servidor se desacoplan de cualquier usuario de GitHub, lo cual los hace comparables con los "tokens de servicio". Adicionalmente, los tokens de servidor a servidor. tienen límites de tasa dedicados que se escalan de acuerdo con el tamaño de las organizaciones sobre las cuales actúan. Para obtener más información, consulta la sección [Límites de tasa para las GitHub Apps](/developers/apps/rate-limits-for-github-apps).
 
 ##### Pros
 
-- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API).
-- Dedicated rate limits that grow with your organization.
-- Decoupled from GitHub user identities, so they do not consume any licensed seats.
-- Never granted a password, so cannot be directly signed in to.
+- Tokens de alcance muy específico con conjuntos de permisos bien definidos y tiempos de vencimiento (1 hora o menos si se revocan manualmente utilizando la API).
+- Límites de tasa dedicados que crecen con tu organización.
+- Desacoplados de las identidades de los usuariso de GitHub para que no consuman plazas de la licencia.
+- Nunca se les otorga una contraseña, así que no se puede iniciar sesión directamente en ellos.
 
 ##### Contras
 
-- Additional setup is needed to create the GitHub App.
-- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code.
+- Se necesita de una configuración adicional para crear la GitHub App.
+- Los tokens de servidor a servidor vencen después de 1 hora, entonces necesitan volver a generarse habitualmente cuando se necesite, utilizando código.
 
 ##### Configuración
 
-1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private.
-1. Determine the permissions your GitHub App requires, such as read-only access to repository contents.
-1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app).
-1. Note your GitHub App `id`.
-1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
-1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization.
-1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access.  Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
-1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
-1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client.
+1. Determina si tu GitHub App debería ser pública o privada. Si tu GitHub App solo actúa en los repositorios dentro de tu organización, probablemente la quieras como privada.
+1. Determina los permisos que necesita tu GitHub App, tales como el acceso de solo lectura al contenido del repositorio.
+1. Crea tu GitHub App a través de la página de configuración de tu organización. Para obtener más información, consulta la sección [Crear una GitHub App](/developers/apps/creating-a-github-app).
+1. Ten en cuenta la `id` de tu GitHub App.
+1. Genera y descarga la llave privada de tu GitHub App y almacénala de forma segura. Para obtener más información, consulta la sección [Generar una llave privada](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
+1. Instala tu GitHub App en los repositorios sobre los que necesita actuar, opcionalmente, puedes instalarla en todos los repositorios de tu organización.
+1. Identifica la `installation_id` que representa la conexión entre tu GitHub App y los repositorios de tu organización a los que puede acceder.  Cada par de GitHub App y organización tienen por lo mucho una sola `installation_id`. Puedes identificar esta `installation_id` a través de la sección [Obtén una instalación de organización para la app autenticada](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). Esto requiere autenticarse como una GitHub App utilizando un JWT. Para obtener más información, consulta la sección [Autenticarse como una GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
+1. Genera un token de servidor a servidor utilizando la terminal de la API de REST correspondiente, [Crear un token de acceso a la instalación para una app](/rest/reference/apps#create-an-installation-access-token-for-an-app). Esto requiere autenticarse como una GitHub App utilizando un JWT. Para obtener más información, consulta las secciones [Autenticarse como una GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app) y [Autenticarse como una instalación](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
+1. Esto requiere que un token de servidor a servidor interactúe con tus repositorios, ya sea a través de la API de REST o de GraphQL, o mediante el cliente de Git.
 
 ### Usuarios máquina
 
diff --git a/translations/es-ES/content/developers/overview/secret-scanning.md b/translations/es-ES/content/developers/overview/secret-scanning.md
index eb4f93eaaa..fe4decc729 100644
--- a/translations/es-ES/content/developers/overview/secret-scanning.md
+++ b/translations/es-ES/content/developers/overview/secret-scanning.md
@@ -15,9 +15,9 @@ topics:
 
 Cuando se encuentra una coincidencia de tu formato secreto en un repositorio público, se envía una carga útil a una terminal HTTP de tu elección.
 
-Cuando se encuentra una coincidencia con tu formato de secreto en un repositorio privado que se haya configurado para el {% data variables.product.prodname_secret_scanning %}, entonces, se alerta a los administradores de repositorio y éstos pueden ver y administrar los resultados del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)".
+Cuando se encuentra una coincidencia de tu formato de secreto en un repositorio privado, la cual esté configurada para el {% data variables.product.prodname_secret_scanning %}, entonces los administradores del repositorio y el confirmante recibirán una alerta y podrán ver y administrar el resultado del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)".
 
-Este artículo describe cómo puedes asociarte con {% data variables.product.prodname_dotcom %} como un proveedor de servicios y unirte al programa del {% data variables.product.prodname_secret_scanning %}.
+Este artículo describe la forma en la que puedes asociarte con {% data variables.product.prodname_dotcom %} como proveedor de servicios y unirte al programa asociado del {% data variables.product.prodname_secret_scanning %}.
 
 ### El proceso del {% data variables.product.prodname_secret_scanning %}
 
@@ -59,21 +59,15 @@ Crea una terminal HTTP pública y accesible desde la internet en la URL que nos
 ##### Ejemplo del POST que se envía a tu terminal
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 El cuerpo del mensaje es una matriz de JSON que contiene uno o más objetos con el siguiente contenido. Cuando se encuentran coincidencias múltiples, {% data variables.product.prodname_dotcom %} podría enviar un solo mensaje con más de una coincidencia del secreto. Tu terminal deberá poder gestionar las solicitudes con una gran cantidad de coincidencias sin exceder el tiempo.
@@ -88,19 +82,31 @@ Te recomendamos que implementes la validación de firmas en tu servicio de alert
 
 Puedes recuperar la llave pública del escaneo de secretos de {% data variables.product.prodname_dotcom %} desde https://api.github.com/meta/public_keys/secret_scanning y validar el mensaje utilizando el algoritmo `ECDSA-NIST-P256V1-SHA256`.
 
-Asumiendo que recibes el siguiente mensaje, los extractos de código que presentamos a continuación demuestran cómo pudiste realizar la validación de firmas. El código también asume que configuraste una variable de ambiente llamada `GITHUB_PRODUCTION_TOKEN` con un PAT generado (https://github.com/settings/tokens). El token no necesita que se configure ningún permiso.
+{% note %}
+
+**Nota**: Cuando envías una solicitud a la terminal de la llave pública anterior, podrías llegar a los límites de tasa. Para evitar lelgar a estos límites de tasa, puedes utilizar un token de acceso personal (no se necesitan alcances) de acuerdo con lo que se sugiere en los ejemplos siguientes, o bien, utilizar una solicitud condicional. Para obtener más información, consulta la sección "[Comenzar con la API de REST](/rest/guides/getting-started-with-the-rest-api#conditional-requests)".
+
+{% endnote %}
+
+Asumiendo que recibes el siguiente mensaje, los extractos de código que presentamos a continuación demuestran cómo pudiste realizar la validación de firmas. Los fragmentos de código asumen que configuraste una variable de ambiente llamada `GITHUB_PRODUCTION_TOKEN` con un PAT generado (https://github.com/settings/tokens) para evitar llegar a los límites de tasa. Este PAT no necesita alcances/permisos.
+
+{% note %}
+
+**Nota**: La firma se generó utilizando el cuerpo del mensaje sin procesar. Así que es importante que también utilices el cuerpo del mensaje sin procesar para la validación de la firma en vez de interpretar y convertir en secuencias el JSON, para evitar volver a arreglar dicho mensaje o cambiar los espacios.
+
+{% endnote %}
 
 **Mensaje de ejemplo que se envía a tu terminal de verificación**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Ejemplo de validación en Go**
@@ -123,73 +129,73 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
   // Fetch the list of GitHub Public Keys
-  req, err := http. NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
-    fmt. Printf("Error preparing request: %s\n", err)
-    os. Exit(1)
+    fmt.Printf("Error preparing request: %s\n", err)
+    os.Exit(1)
   }
 
   if len(os.Getenv("GITHUB_PRODUCTION_TOKEN")) == 0 {
-    fmt. Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN")
-    os. Exit(1)
+    fmt.Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN")
+    os.Exit(1)
   }
 
-  req. Header.Add("Authorization", "Bearer "+os.Getenv("GITHUB_PRODUCTION_TOKEN"))
+  req.Header.Add("Authorization", "Bearer "+os.Getenv("GITHUB_PRODUCTION_TOKEN"))
 
-  resp, err := http. DefaultClient.Do(req)
+  resp, err := http.DefaultClient.Do(req)
   if err != nil {
-    fmt. Printf("Error requesting GitHub signing keys: %s\n", err)
-    os. Exit(2)
+    fmt.Printf("Error requesting GitHub signing keys: %s\n", err)
+    os.Exit(2)
   }
 
-  decoder := json. NewDecoder(resp.Body)
+  decoder := json.NewDecoder(resp.Body)
   var keys GitHubSigningKeys
-  if err := decoder. Decode(&keys); err != nil {
-    fmt. Printf("Error decoding GitHub signing key request: %s\n", err)
-    os. Exit(3)
+  if err := decoder.Decode(&keys); err != nil {
+    fmt.Printf("Error decoding GitHub signing key request: %s\n", err)
+    os.Exit(3)
   }
 
   // Find the Key used to sign our webhook
   pubKey, err := func() (string, error) {
-    for _, v := range keys. PublicKeys {
-      if v. KeyIdentifier == kID {
-        return v. Key, nil
+    for _, v := range keys.PublicKeys {
+      if v.KeyIdentifier == kID {
+        return v.Key, nil
 
       }
     }
-    return "", errors. New("specified key was not found in GitHub key list")
+    return "", errors.New("specified key was not found in GitHub key list")
   }()
 
   if err != nil {
-    fmt. Printf("Error finding GitHub signing key: %s\n", err)
-    os. Exit(4)
+    fmt.Printf("Error finding GitHub signing key: %s\n", err)
+    os.Exit(4)
   }
 
   // Decode the Public Key
   block, _ := pem.Decode([]byte(pubKey))
   if block == nil {
-    fmt. Println("Error parsing PEM block with GitHub public key")
-    os. Exit(5)
+    fmt.Println("Error parsing PEM block with GitHub public key")
+    os.Exit(5)
   }
 
   // Create our ECDSA Public Key
   key, err := x509.ParsePKIXPublicKey(block.Bytes)
   if err != nil {
-    fmt. Printf("Error parsing DER encoded public key: %s\n", err)
-    os. Exit(6)
+    fmt.Printf("Error parsing DER encoded public key: %s\n", err)
+    os.Exit(6)
   }
 
   // Because of documentation, we know it's a *ecdsa.PublicKey
   ecdsaKey, ok := key.(*ecdsa.PublicKey)
   if !ok {
-    fmt.
+    fmt.Println("GitHub key was not ECDSA, what are they doing?!")
     Exit(7)
   }
 
@@ -241,16 +247,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -356,4 +362,3 @@ Algunos puntos importantes:
 **Nota:** Nuestro tiempo límite se configura para que sea mayor (es decir, 30 segundos) para los socios que proporcionen datos sobre falsos positivos. Si requieres de un tiempo límite mayor a 30 segundos, envíanos un correo electrónico a <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
 {% endnote %}
-
diff --git a/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md b/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md
index cd43e04af9..3fed7ac65c 100644
--- a/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/es-ES/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-En Mac OS X, `ssh-agent` "olvidará" esta llave una vez que se reinicie. Pero puedes importar tus llaves SSH en Keychain si utilizas este comando:
+En macOS, `ssh-agent` "olvidará" esta llave una vez que se reinicie durante el proceso de inicialización. Pero puedes importar tus llaves SSH en Keychain si utilizas este comando:
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md
index 47c2423094..dd276a34a5 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ Los objetos de los eventos que se devuelven de las terminales de la API de Event
 Este ejemplo te muestra el formato de la respuesta de [WatchEvent](#watchevent) cuando utilizas la [API de Eventos](/rest/reference/activity#events).
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
@@ -191,11 +191,11 @@ Este evento devuelve un objeto de `payload` vacío.
 
 #### Objeto de `payload` del evento
 
-| Clave                  | Type        | Descripción                                    |
-| ---------------------- | ----------- | ---------------------------------------------- |
-| `Acción`               | `secuencia` | La acción que se realizó. Puede ser `created`. |
-| `solicitud_extracción` | `objeto`    | The pull request the review pertains to.       |
-| `revisar`              | `objeto`    | La revisión que se afectó.                     |
+| Clave                  | Type        | Descripción                                              |
+| ---------------------- | ----------- | -------------------------------------------------------- |
+| `Acción`               | `secuencia` | La acción que se realizó. Puede ser `created`.           |
+| `solicitud_extracción` | `objeto`    | La solicitud de cambios a la cual pertenece la revisión. |
+| `revisar`              | `objeto`    | La revisión que se afectó.                               |
 
 ### PullRequestReviewCommentEvent
 
diff --git a/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md
index 2ff725816f..13a5392ed8 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/securing-your-webhooks.md
@@ -91,6 +91,6 @@ Tus implementaciones de lenguaje y de servidor pueden diferir de esta muestra de
 
 * Sin importar qué implementación utilices, la firma de hash comienza con {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`sha1=`{% endif %}, utilizando la llave de tu token secreto y el cuerpo de tu carga útil.
 
-* **No se recomienda** utilizar un simple operador de `==`. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators.
+* **No se recomienda** utilizar un simple operador de `==`. Un método como el de [`secure_compare`][secure_compare] lleva a cabo una secuencia de comparación de "tiempo constante" que ayuda a mitigar algunos ataques de temporalidad en contra de las operaciones de igualdad habituales.
 
 [secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare
diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index e33f91ed88..984e041f2e 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -61,7 +61,7 @@ También, el `User-Agent` para las solicitudes tendrá el prefijo `GitHub-Hooksh
 #### Ejemplo de entrega
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -200,7 +200,9 @@ También, el `User-Agent` para las solicitudes tendrá el prefijo `GitHub-Hooksh
 
 Los eventos de webhook se desencadenan basándose en la especificidad del dominio que registres. Por ejemplo, si registras un subdominio (`https://subdomain.example.com`), entonces la única URL para el subdominio activarán este evento. Si registras un dominio (`https://example.com`) entonces las URL para el dominio y todos sus subdominios activarán este evento. Consulta la sección "[Crear un adjunto de contenido](/rest/reference/apps#create-a-content-attachment)" para crear un nuevo adjunto de contenido.
 
-Solo las {% data variables.product.prodname_github_app %}s podrán recibir este evento. Las {% data variables.product.prodname_github_app %}s deben tener el permiso `content_references` `write` para suscribirse a este evento.
+#### Disponibilidad
+
+- {% data variables.product.prodname_github_app %}s con el permiso `content_references:write`
 
 #### Ejemplo de carga útil del webhook
 
@@ -343,18 +345,18 @@ Solo las {% data variables.product.prodname_github_app %}s podrán recibir este
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions](/graphql/guides/using-the-graphql-api-for-discussions)."
+Actividad relacionada con un debate. Para obtener más información, consulta la sección "[Utilizar la API de GraphQL para los debates](/graphql/guides/using-the-graphql-api-for-discussions)".
 #### Disponibilidad
 
 - Webhooks de repositorio
 - Webhooks de organización
-- {% data variables.product.prodname_github_app %}s with the `discussions` permission
+- Las {% data variables.product.prodname_github_app %}s con el permiso de `discussions`
 
 #### Objeto de carga útil del webhook
 
-| Clave    | Type        | Descripción                                                                                                                                                             |
-| -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Acción` | `secuencia` | La acción realizada. Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, or `unanswered`. |
+| Clave    | Type        | Descripción                                                                                                                                                               |
+| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción realizada. Puede ser `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, o `unanswered`. |
 {% data reusables.webhooks.discussion_desc %}
 {% data reusables.webhooks.repo_desc_graphql %}
 {% data reusables.webhooks.org_desc_graphql %}
@@ -368,20 +370,20 @@ Activity related to a discussion. For more information, see the "[Using the Grap
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions](/graphql/guides/using-the-graphql-api-for-discussions)."
+La actividad relacionada con un comentario en un debate. Para obtener más información, consulta la sección "[Utilizar la API de GraphQL para los debates](/graphql/guides/using-the-graphql-api-for-discussions)".
 
 #### Disponibilidad
 
 - Webhooks de repositorio
 - Webhooks de organización
-- {% data variables.product.prodname_github_app %}s with the `discussions` permission
+- Las {% data variables.product.prodname_github_app %}s con el permiso de `discussions`
 
 #### Objeto de carga útil del webhook
 
-| Clave        | Type        | Descripción                                                                                                   |
-| ------------ | ----------- | ------------------------------------------------------------------------------------------------------------- |
-| `Acción`     | `secuencia` | La acción realizada. Puede ser `created`, `edited`, o `deleted`.                                              |
-| `comentario` | `objeto`    | The [`discussion comment`](/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource. |
+| Clave        | Type        | Descripción                                                                                                    |
+| ------------ | ----------- | -------------------------------------------------------------------------------------------------------------- |
+| `Acción`     | `secuencia` | La acción realizada. Puede ser `created`, `edited`, o `deleted`.                                               |
+| `comentario` | `objeto`    | El recurso de [`discussion comment`](/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment). |
 {% data reusables.webhooks.discussion_desc %}
 {% data reusables.webhooks.repo_desc_graphql %}
 {% data reusables.webhooks.org_desc_graphql %}
@@ -485,7 +487,7 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl
 
 {% note %}
 
-**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo.
+**Nota:** Este evento reemplaza al evento obsoletizado de `integration_installation`.
 
 {% endnote %}
 
@@ -509,7 +511,7 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl
 
 {% note %}
 
-`repository` cuando el evento ocurre desde una actividad en un repositorio.
+**Nota:** Este evento remplaza al evento obsoletizado de `integration_installation_repositories`.
 
 {% endnote %}
 
@@ -1010,12 +1012,6 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend
 
 {% endnote %}
 
-{% tip %}
-
-**Nota**: El ejemplo de la carga útil del webhook siguiendo la tabla difiere significativamente de la carga útil de la API de Eventos descrita en la misma. Entre otras diferencias, la carga útil del webhook incluye ambos objetos, `sender` y `pusher`. El remitente y cargador son el mismo usuario que inició el evento `push`, pero el objeto `sender` contiene más detalles.
-
-{% endtip %}
-
 #### Disponibilidad
 
 - Webhooks de repositorio
@@ -1206,7 +1202,7 @@ Actividad relacionada con una asesoría de seguridad. Una asesoría de seguridad
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Configurar webhooks para eventos en tu cuenta patrocinada](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
+Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Configurar webhooks para eventos en tu cuenta patrocinada](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
 
 #### Disponibilidad
 
diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 1602576fcf..d86f0960f8 100644
--- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %} Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 
-Adicionalmente a iniciar o visualizar un debate, puedes comentar como respuesta al comentario original del autor del mismo. También puedes crear un hilo de comentarios si respondes a un comentario individual que otro miembro de la comunidad haya hecho dentro del debate, y reaccionar a los comentarios con emojis. Para obtener más información acerca de las reacciones, consulta la sección "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)".
+Adicionalmente a iniciar o visualizar un debate, puedes comentar como respuesta al comentario original del autor del mismo. También puedes crear un hilo de comentarios si respondes a un comentario individual que otro miembro de la comunidad haya hecho dentro del debate, y reaccionar a los comentarios con emojis.
 
 Puedes bloquear usuarios y reportar el contenido perjudicial para mantener un ambiente placentero y seguro en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)".
 
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md
index 85f7a36a19..389696e73c 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Campus Program
-intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.'
+title: Acerca del Programa del Campus de GitHub
+intro: 'el {% data variables.product.prodname_campus_program %} ofrece {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} gratuitos para las escuelas que quieran sacar el mayor provecho de {% data variables.product.prodname_dotcom %} para su comunidad.'
 redirect_from:
   - /education/teach-and-learn-with-github-education/about-github-education
   - /github/teaching-and-learning-with-github-education/about-github-education
@@ -10,14 +10,14 @@ versions:
   free-pro-team: '*'
 ---
 
-{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes:
+El {% data variables.product.prodname_campus_program %} es un paquete de acceso premium a {% data variables.product.prodname_dotcom %} para instituciones enfocadas en la enseñanza que otorgan certificados, diplomas y nombramientos. El {% data variables.product.prodname_campus_program %} incluye:
 
-- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments
+- Acceso sin costo a {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} para todos tus departamentos técnicos y académicos
 - Capacitación para docentes para el Git principal y {% data variables.product.prodname_dotcom %} con nuestro programa Asesores de campus
-- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners
+- Acceso exclusivo a las características nuevas, swag específico de la Educación de GitHub y herramientas de desarrollo gratuitas de los socios de {% data variables.product.prodname_dotcom %}
 - Acceso automatizado a las funciones premium de {% data variables.product.prodname_education %}, como {% data variables.product.prodname_student_pack %}
 
-Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join.
+Cualquier escuela que acepte las [condiciones del programa](https://education.github.com/schools/terms) puede unirse.
 
 Para obtener más información, consulta la página [oficial {% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
 
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md
index c532b9a6e6..0dea28b751 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md
@@ -1,6 +1,6 @@
 ---
-title: Use GitHub at your educational institution
-intro: 'Maximize the benefits of using {% data variables.product.prodname_dotcom %} at your institution for your students, instructors, and IT staff with {% data variables.product.prodname_education %} and our various training programs for students and instructors.'
+title: Utiliza GitHub en tu institución educativa
+intro: 'Aumenta los beneficios de utilizar {% data variables.product.prodname_dotcom %} en tu institución para los estudiantes, instructores y el personal de TI con {% data variables.product.prodname_education %} y nuestros múltiples programas de capacitación para estudiantes e instructores.'
 mapTopic: true
 redirect_from:
   - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md
index 8512b9b548..4ce455cd6e 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md
@@ -1,6 +1,6 @@
 ---
-title: Use GitHub for your schoolwork
-intro: 'As a student, use {% data variables.product.prodname_dotcom %} to collaborate on your school projects and build real-world experience.'
+title: Utiliza GitHub para tu trabajo escolar
+intro: 'Como estudiante, utiliza {% data variables.product.prodname_dotcom %} para colaborar en tus proyectos escolares y crear experiencias de la vida real.'
 mapTopic: true
 redirect_from:
   - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md
index b03e25afe3..e4e61fbdbc 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md
@@ -59,11 +59,11 @@ Para obtener más información, consulta:
 ### Situación de estudiante inadmisible
 
 No eres apto para un {% data variables.product.prodname_student_pack %} si:
-- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study.
+- Estás inscrito en un programa de aprendizaje informal que no es parte del [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) y no así en un curso de estudio que te otorgue una certificación o diploma.
 - Estás buscando obtener un título que se terminará en la sesión académica actual.
 - Tienes menos de 13 años.
 
-Tu instructor todavía puede solicitar un descuento para uso escolar {% data variables.product.prodname_education %}. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
+Tu instructor todavía puede solicitar un descuento para uso escolar {% data variables.product.prodname_education %}. Si eres alumno en una escuela o curso intensivo de programación, serás elegible para un {% data variables.product.prodname_student_pack %} si tu escuela se une al [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
 
 ### Leer más
 
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
index 18e8d97bbc..9c78f00257 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
@@ -17,7 +17,7 @@ Cuando un alumno acepta una tarea grupal, los alumnos pueden crear un equipo nue
 
 {% data reusables.classroom.about-assignments %}
 
-Puedes decidir cuántos equipos puede tener una tarea y cuántos miembros puede tener cada equipo. Cada equipo que crea un alumno para una tarea constituye un equipo dentro de tu organización en {% data variables.product.product_name %}. La visibilidad del equipo es secreta. Los equipos que crees en {% data variables.product.product_name %} no aparecerán en {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Puedes decidir cuántos equipos puede tener una tarea y cuántos miembros puede tener cada equipo. Cada equipo que crea un alumno para una tarea constituye un equipo dentro de tu organización en {% data variables.product.product_name %}. La visibilidad del equipo es secreta. Los equipos que crees en {% data variables.product.product_name %} no aparecerán en {% data variables.product.prodname_classroom %}. Para obtener más información, consulta la sección "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)".
 
 Para ver un video demostrativo de la creación de una tarea de grupo, consulta la sección "[Conceptos básicos para configurar un {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)".
 
diff --git a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md
index f84a26a3c8..ee938de33f 100644
--- a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md
@@ -47,6 +47,8 @@ Para cada regla de protección de rama, puedes elegir habilitar o inhabilitar la
 - [Permitir las subidas forzadas](#allow-force-pushes)
 - [Permitir el borrado](#allow-deletions)
 
+Para obtener más información sobre cómo configurar la protección de ramas, consulta la sección "[Administrar la regla de protección de ramas](/github/administering-a-repository/managing-a-branch-protection-rule)".
+
 #### Requerir revisiones de solicitudes de cambio antes de fusionarlas
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
@@ -100,7 +102,15 @@ Cuando habilitas el requerir el firmado de confirmaciones en una rama, los colab
 
 {% note %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+**Notas:**
+
+* Si habilitaste el modo vigilante, el cual indica que tus confirmaciones siempre se firmarán, cualquier confirmación que {% data variables.product.prodname_dotcom %} identifique como "Verificada parcialmente" se permitirá en aquellas ramas que requieran confirmaciones firmadas. Para obtener más información sobre el modo vigilante, consulta la sección "[Mostrar los estados de verificación para todas tus confirmaciones](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)".
+* Si un colaborador sube una confirmación sin firmar a una rama que requiere firmas de confirmación, este necesitará rebasar dicha confirmación para incluir una firma verificada y luego subir forzadamente la confirmación reescrita a esta.
+
+{% else %}
 **Nota:** Si un colaborador sube una confirmación sin firmar a una rama que requiere firmas de confirmación, éste necesitará rebasar la confirmación para incluir una firma verificada y luego subir forzadamente la confirmación re-escrita a la rama.
+{% endif %}
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md b/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md
index ce7d52c977..de5681492e 100644
--- a/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/es-ES/content/github/administering-a-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
 También puedes renombrar la rama predeterminada. Para obtener más información, consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)".
 
diff --git a/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index 721f6dd1d3..414b95c284 100644
--- a/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -26,7 +26,7 @@ De manera alterna, puedes habilitar {% data variables.product.prodname_actions %
 
 {% note %}
 
-**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
+**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. Para obtener más información, consulta la sección "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" o {% if currentVersion == "free-pro-team@latest" %}"[Requerir politicas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)".{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Requerir políticas de las {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".{% endif %}
 
 {% endnote %}
 
@@ -47,7 +47,7 @@ Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar
 
 {% note %}
 
-**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. Para obtener más información, consulta la sección "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" o {% if currentVersion == "free-pro-team@latest" %}"[Requerir politicas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)".{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Requerir políticas de las {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
 {% endif %}
 
@@ -82,3 +82,21 @@ Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Configurar los permisos del `GITHUB_TOKEN` para tu repositorio
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+También pueden configurarse los permisos predeterminados en los ajustes de la organización. Si el predeterminado más restringido se seleccionó en la configuración de la organización, la misma opción se autoselecciona en tu configuración de repositorio y la opción permisiva se inhabilita.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. Debajo de **Permisos del flujo de trabajo**, elige si quieres que el `GITHUB_TOKEN` tenga permisos de lectura y escritura para todos los alcances o solo acceso de lectura para el alcance `contents`. ![Configurar los permisos del GITHUB_TOKEN para este repositorio](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. Da clic en **Guardar** para aplicar la configuración.
+{% endif %}
diff --git a/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index e633aa28a6..bf8fdc54ad 100644
--- a/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### Acerca de los archivos FUNDING
 
-Puedes configurar tu botón de patrocinador editando un archivo _FUNDING.yml_ en la carpeta `.github` de tu repositorio, o bien en la rama predeterminada. Puedes configurar el botón para que incluya programadores patrocinados en {% data variables.product.prodname_sponsors %}, plataformas de financiamiento externo o URL de financiamiento personalizadas. Para obtener mas información acerca de {% data variables.product.prodname_sponsors %}, consulta "[Acerca de los patrocinadores de GitHub](/articles/about-github-sponsors)".
+Puedes configurar tu botón de patrocinador editando un archivo _FUNDING.yml_ en la carpeta `.github` de tu repositorio, o bien en la rama predeterminada. Puedes configurar el botón para que incluya programadores patrocinados en {% data variables.product.prodname_sponsors %}, plataformas de financiamiento externo o URL de financiamiento personalizadas. Para obtener mas información acerca de {% data variables.product.prodname_sponsors %}, consulta "[Acerca de los patrocinadores de GitHub](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
 
 Puedes agregar un nombre de usuario, un nombre de paquete o un nombre de proyecto por plataforma de financiamiento externo y hasta cuatro URL personalizadas. Puedes añadir hasta cuatro organizaciones o desarrolladores patrocinadores en {% data variables.product.prodname_sponsors %}. Agrega cada plataforma en una línea nueva, usando la siguiente sintaxis:
 
@@ -76,5 +76,5 @@ Cualquier usuario que cuente con permisos de administración puede habilitar un
 {% data reusables.files.propose_new_file %}
 
 ### Leer más
-- "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
 - "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %}
diff --git a/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
index 6b65fbc64f..ca030f334a 100644
--- a/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -13,9 +13,9 @@ topics:
 
 ### Acerca de la fusión automática
 
-If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+Si permites la fusión automática para las solicitudes de cambio en tu repositorio, las personas con permisos de escritura pueden configurar las solicitudes de extracción individuales en el repositorio para que se fusionen automáticamente cuando se cumplan todos los requisitos de fusión. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}Si alguien que no tiene permisos de escritura sube cambios a una solicitud de cambios que tiene habilitada la fusión automática, esta se inhabilitará para dicha solicitud de cambios. {% endif %}Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)".
 
-### Managing auto-merge
+### Administrar la fusión automática
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md
index e69303356c..5e2464f40c 100644
--- a/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/managing-releases-in-a-repository.md
@@ -48,7 +48,7 @@ los objetos de {% data variables.large_files.product_name_long %} ({% data varia
 7. Opcionalmente, para incluir los archivos binarios tales como programas compilados en tu lanzamiento, arrastra y suelta o selecciona manualmente los archivos en la caja de binarios. ![Proporcionar un DMG con el lanzamiento](/assets/images/help/releases/releases_adding_binary.gif)
 8. Para notificar a los usuarios que el lanzamiento no está listo para producción y puede ser inestable, selecciona **Esto es un pre-lanzamiento**. ![Casilla de verificación para marcar un lanzamiento como prelanzamiento](/assets/images/help/releases/prerelease_checkbox.png)
 {%- if currentVersion == "free-pro-team@latest" %}
-1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png)
+1. Opcionalmente, selecciona **Crear un debate para este lanzamiento** y luego, selecciona el menú desplegable de **Categoría** y haz clic en aquella que describa el debate de dicho lanzamiento. ![Casilla de verificación para crear un debate de lanzamiento y menú desplegable para elegir una categoría](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
 9. Si estás listo para publicitar tu lanzamiento, haz clic en **Publicar lanzamiento**. Para seguir trabajando luego en el lanzamiento, haz clic en **Guardar borrador**. ![Botones Publicar lanzamiento y Borrador de lanzamiento](/assets/images/help/releases/release_buttons.png)
 
diff --git a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index 65569fd11c..17ebadae10 100644
--- a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -35,10 +35,11 @@ Puedes administrar las características de seguridad y análisis para tu reposit
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**.
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}El control para "{% data variables.product.prodname_GH_advanced_security %}" se encuentra inhabilitado si no tienes plazas disponibles en tu licencia de {% data variables.product.prodname_GH_advanced_security %}.
-  ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. El control para "
+{% data variables.product.prodname_GH_advanced_security %}" se inhabilitará si tu empresa no tiene licencias disponibles para la {% data variables.product.prodname_advanced_security %}.{% if currentVersion == "free-pro-team@latest" %}
+  ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
 **Nota:** Si inhabilitas
 
@@ -46,11 +47,11 @@ Puedes administrar las características de seguridad y análisis para tu reposit
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
 4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. Antes de que puedas habilitar el "
-{% data variables.product.prodname_secret_scanning %}" para tu repositorio, necesitas habilitar la {% data variables.product.prodname_GH_advanced_security %}.
+{% data variables.product.prodname_secret_scanning %}" para tu repositorio, es probable que necesites habilitar la {% data variables.product.prodname_GH_advanced_security %}.
    ![Habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} o el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
diff --git a/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index 84a113e8f6..9028e6b7ae 100644
--- a/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ Para obtener más información acerca de los niveles de permiso en los repositor
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. Debajo de "Administrar acceso", encuentra al equipo o persona de quien quieras eliminar el acceso y da clic{% octicon "trashcan" aria-label="The trashcan icon" %}. ![Icono de papelera para eliminar el acceso](/assets/images/help/repository/manage-access-remove.png)
+4. Debajo de "Administrar acceso", encuentra al equipo o persona de quien quieras eliminar el acceso y da clic{% octicon "trash" aria-label="The trash icon" %}. ![icono de cesto de basura para eliminar el acceso](/assets/images/help/repository/manage-access-remove.png)
 
 ### Leer más
 
diff --git a/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md b/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md
index fe058566b0..db4deec1d6 100644
--- a/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/es-ES/content/github/administering-a-repository/renaming-a-branch.md
@@ -13,9 +13,11 @@ topics:
 
 Puedes renombrar una rama en un repositorio de {% data variables.product.product_location %}. Para obtener más información sobre cómo renombrar ramas, consulta la sección "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches)".
 
-When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments.
+Cuando renombras una rama en {% data variables.product.product_location %}, cualquier URL que contega el nombre de la rama antigua se redireccionará automáticamente a la URL equivalente para la rama que se renombró. También se actualizan las políticas de protección de rama, así como la rama base para las solicitudes de cambios abriertas (incluyendo aquellas para las bifurcaciones) y para los borradores de lanzamientos. Después de que se completa el renombramiento, {% data variables.product.prodname_dotcom %} proporciona instrucciones en la página principal del repositorio y dirige a los colaboradores a actualizar sus ambientes locales de Git.
 
-Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
+Aunque las URL de archivo se redirigen automáticamente, las URL de archivo sin procesar no se redirigirán. Además, {% data variables.product.prodname_dotcom %} no realiza ninguna redirección si los usuarios realizan un `git pull` para el nombre de rama anterior.
+
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
 
 ### Renombrar una rama
 
@@ -35,4 +37,10 @@ Desde el clon local del repositorio en una computadora, ejecuta los siguientes c
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+Opcionalmente, ejecuta el siguiente comando para eliminar las referencias de rastreo al nombre de la rama antigua.
+```
+$ git remote prune origin
 ```
diff --git a/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md b/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md
index f5a9a84448..a0f096e015 100644
--- a/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/renaming-a-repository.md
@@ -18,7 +18,7 @@ Cuando cambias el nombre de un repositorio, toda la información existente, a ex
 * Estrellas
 * Seguidores
 
-For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Para obtener más información sobre los sitios de proyecto, consulta la sección "[Acerca de las {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Adicionalmente a redirigir el tráfico web, todas las operaciones de `git clone`, `git fetch`, o`git push` que apunten a la ubicación anterior seguirán funcionando como si se hubieran hecho en la nueva. Sin embargo, para evitar la confusión, recomendamos ampliamente actualizar cualquier clon local para que lleve a la URL del nuevo repositorio. Puedes hacer esto utilizando `git remote` en la línea de comandos:
 
diff --git a/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md
index 621aaab79c..963aa4020b 100644
--- a/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -31,9 +31,9 @@ Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o l
 
 ### Restaurar un repositorio eliminado que le pertenecía a una organización
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md
index 8373f9333b..d6eb7057b0 100644
--- a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md
+++ b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md
@@ -16,7 +16,7 @@ topics:
 
 ### Acerca de los cambios a la visibilidad de un repositorio
 
-Los propietarios de las organizaciones pueden restringir la capacidad de cambiar la visibilidad de un repositorio únicamente para otros propietarios de organizaciones. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+Los propietarios de las organizaciones pueden restringir la capacidad de cambiar la visibilidad de un repositorio únicamente para otros propietarios de organizaciones. Para obtener más información, consulta la sección "[Restringir los cambios a la visibilidad del repositorio en tu organización](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)".
 
 Te recomendamos revisar las siguientes consideraciones antes de que cambies la visibilidad de un repositorio.
 
diff --git a/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index d221a14a5d..7067687bad 100644
--- a/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/es-ES/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ También puedes ver información de implementación en la pestaña "Conversation
 ### Ver el tablero de implementaciones
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Arriba de la lista de archivos, haz clic en **Environments (Entornos)**. ![Entornos por encima de la página del repositorio](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}A la derecha de la lista de archivos, haz clic en **Ambientes**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Sobre la lista de archivos, haz clic en **Ambientes**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### Leer más
  - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)"
diff --git a/translations/es-ES/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/es-ES/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..95c3137bcf
--- /dev/null
+++ b/translations/es-ES/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+Para alojar tus imágenes, {% data variables.product.product_name %} usa el [Camo del proyecto de código abierto](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. La URL inicia a `https://<subdomain>.githubusercontent.com/`, con subdominios diferentes dependiendo de cómo la cargues.
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Solución de problemas con Camo
+
+En circunstancias excepcionales, las imágenes procesadas mediante Camo podrían no aparecer en {% data variables.product.prodname_dotcom %}. Aquí presentamos algunos pasos que puedes tomar para determinar dónde está el problema.
+
+{% windows %}
+
+{% tip %}
+
+Los usuarios de Windows necesitarán usar PowerShell de Git (que está instalado junto a [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) o descargar [curl para Windows](http://curl.haxx.se/download.html).
+
+{% endtip %}
+
+{% endwindows %}
+
+#### Una imagen no aparece
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Solicita los encabezados de la imagen usando `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. Verifica el valor de `Content-Type`. En este caso, es `image/x-png`.
+4. Verifica ese tipo de contenido con [la lista de tipos admitidos por Camo](https://github.com/atmos/camo/blob/master/mime-types.json).
+
+Si Camo no admite tu tipo de contenido, puedes probar varias acciones:
+  * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un tipo de contenido correcto para las imágenes.
+  * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio.
+  * Realiza una solicitud de extracción para que Camo agregue tu tipo de contenido a la lista.
+
+#### Una imagen que cambió recientemente no se está actualizando
+
+Si recientemente modificaste una imagen y aparece en tu navegador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar restablecer la caché de la imagen.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Solicita los encabezados de la imagen usando `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+Verifica el valor de `Cache-Control`. En este ejemplo, no hay `Cache-Control`. En ese caso:
+  * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un `Cache-Control` de `no-cache` para las imágenes.
+  * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio.
+
+ Si `Cache-Control` se *configura* como `no-cache`, contacta a {% data variables.contact.contact_support %} o busca ayuda en el {% data variables.contact.community_support_forum %}.
+
+#### Eliminar una imagen desde la caché de Camo
+
+Purgar la caché fuerza a cada usuario de {% data variables.product.prodname_dotcom %} a volver a solicitar la imagen, por lo que deberías usarla con mucha prudencia y solo en el caso de que los pasos anteriores no hayan funcionado.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Purga la imagen usando `curl -X PURGE` en la URL de Camo.
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### Visualizar imágenes en redes privadas
+
+Si una imagen está siendo proporcionada desde una red privada o desde un servidor que requiere de autenticación, se puede ver mediante {% data variables.product.prodname_dotcom %}. De hecho, no puede ser vista por ningún usuario sin pedirle que se registre en el servidor.
+
+Para solucionar esto, mueva la imagen a un servicio que esté disponible públicamente.
+
+### Leer más
+
+- "[Imágenes de usuarios de conexiones proxy](https://github.com/blog/1766-proxying-user-images)" en {% data variables.product.prodname_blog %}
diff --git a/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md
index cf659bee0b..f5a5169f45 100644
--- a/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md
+++ b/translations/es-ES/content/github/authenticating-to-github/about-authentication-to-github.md
@@ -58,16 +58,16 @@ Puedes acceder a los repositorios en {% data variables.product.product_name %} d
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 
-### {% data variables.product.company_short %}'s token formats
+### Formatos de los tokens de {% data variables.product.company_short %}
 
-{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type.
+{% data variables.product.company_short %} emite tokens que inician con un prefijo para indicar el tipo de los mismos.
 
-| Token type                                                                      | Prefix | Más información                                                                                                                                                   |
-|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Token de acceso personal                                                        | `ghp_` | "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)"                                                          |
-| OAuth access token                                                              | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)"                                                       |
-| User-to-server token for a {% data variables.product.prodname_github_app %}   | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
-| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)"   |
-| Refresh token for a {% data variables.product.prodname_github_app %}          | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)"                                                             |
+| Tipo de token                                                                            | Prefijo | Más información                                                                                                                                                             |
+|:---------------------------------------------------------------------------------------- |:------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Token de acceso personal                                                                 | `ghp_`  | "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)"                                                                    |
+| Token de acceso OAuth                                                                    | `gho_`  | "[Autorizar las {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)"                                                               |
+| Token de usuario a servidor para una {% data variables.product.prodname_github_app %}  | `ghu_`  | "[Identificar y autorizar a los usuarios para las {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
+| Token de servidor a servidor para una {% data variables.product.prodname_github_app %} | `ghs_`  | "[Autenticarse con las {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)"            |
+| Actualizar un token para una {% data variables.product.prodname_github_app %}          | `ghr_`  | "[Actualizar los tokens de acceso de usuario a servidor](/developers/apps/refreshing-user-to-server-access-tokens)"                                                         |
 
 {% endif %}
diff --git a/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
index 1e32ae3afc..881f3b2833 100644
--- a/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
+++ b/translations/es-ES/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
@@ -51,5 +51,5 @@ Después de que un propietario de empresa u organización habilite o requiera el
 
 ### Leer más
 
-{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}- "[Acerca de la administración de identidad y acceso con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
 {% if currentVersion == "github-ae@latest" %}- "[Acerca de la administración de identidad y de acceso para tu empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
diff --git a/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md
index ed23ca083d..e14e6aef26 100644
--- a/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/es-ES/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: Acerca de la verificación de firma de confirmación
-intro: 'Puedes firmar etiquetas y confirmaciones localmente utilizando GPG o S/MIME. Estas etiquetas o confirmaciones se marcan como verificadas en {% data variables.product.product_name %}, para que otras personas puedan confiar en que los cambios vienen de una fuente confiable.'
+intro: 'Puedes firmar etiquetas y confirmaciones localmente utilizando GPG o S/MIME. Estas etiquetas o confirmaciones se marcan como verificadas en {% data variables.product.product_name %} para que otras personas tengan la confianza de que los cambios vienen de una fuente confiable.'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures/
   - /articles/about-gpg/
@@ -16,15 +16,35 @@ topics:
 
 ### Acerca de la verificación de firma de confirmación
 
-Puedes firmar confirmaciones y etiquetas localmente, para que otras personas puedan verificar que tu trabajo viene de una fuente confiable. Si una confirmación o etiqueta tienen una firma GPG o S/MINE que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada.
+Puedes firmar confirmaciones y etiquetas localmente para darles a otras personas la confianza necesaria sobre el origen de un cambio que hayas realizado. Si una confirmación o etiqueta tiene una firma GPG o S/MIME que se pueda verificar criptográficamente, GitHub la marcará como {% if currentVersion == "free-pro-team@latest" %}"Verificada" o "Verificada parcialmente".{% else %}"Verificada".{% endif %}
 
 ![Confirmación verificada](/assets/images/help/commits/verified-commit.png)
 
-Si una confirmación o etiqueta tiene una firma que no puede ser comprobada, {% data variables.product.product_name %} marca la confirmación o la etiqueta como no verificada.
+{% if currentVersion == "free-pro-team@latest" %}
+Las confirmaciones y etiquetas tienen los siguientes estados de verificación dependiendo de si las habilitaste en modo vigilante. Predeterminadamente, el modo vigilante no está habilitado. Para obtener más información sobre cómo habilitar el modo vigilante, consulta la sección "[Mostrar los estados de verificación para todas tus confirmaciones](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)".
 
-Los administradores de repositorios pueden implementar la firma de confirmación requerida en una rama para bloquear todas las confirmaciones que no estén firmadas y verificadas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-signed-commits)".
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
-Puedes comprobar el estado de verificación de tus confirmaciones o etiquetas firmadas en {% data variables.product.product_name %} y ver por qué las firmas de tu confirmación podrían no ser verificadas. Para obtener más información, consulta "[Comprobar la confirmación y el estado de verificación de firma de la etiqueta](/articles/checking-your-commit-and-tag-signature-verification-status)".
+#### Estados predeterminados
+
+| Estado                     | Descripción                                                 |
+| -------------------------- | ----------------------------------------------------------- |
+| **Verificado**             | La confirmación se firmó y la firma se verificó con éxito.  |
+| **Sin verificar**          | La confirmación se firmó pero la firma no pudo verificarse. |
+| Sin estado de verificación | La confirmación no se firmó.                                |
+
+#### Estados con modo vigilante habilitado
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+Si una confirmación o etiqueta tiene una firma que no puede verificarse,
+{% data variables.product.product_name %} marca la confirmación o etiqueta como "Sin verificar".
+{% endif %}
+
+Los administradores de repositorios pueden implementar la firma de confirmación requerida en una rama para bloquear todas las confirmaciones que no estén firmadas y verificadas. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-signed-commits)".
+
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} utilizará GPG automáticamente para firmar las confirmaciones que hagas utilizando la interface web de {% data variables.product.product_name %}, con excepción de cuando combinas y fusionas una solicitud de cambios de la cual no seas autor. Opcionalmente, puedes elegir que {% data variables.product.product_name %} firme las confirmaciones que hagas en {% data variables.product.prodname_codespaces %}. Las confirmaciones que firme {% data variables.product.product_name %} tendrán un estado verificado en {% data variables.product.product_name %}. Puedes verificar la firma localmente usando la clave pública disponible en https://github.com/web-flow.gpg. Para obtener más información sobre cómo habilitar la verificación de GPG para tus codespaces, consulta la sección "[Administrar la verificación de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
diff --git a/translations/es-ES/content/github/authenticating-to-github/about-ssh.md b/translations/es-ES/content/github/authenticating-to-github/about-ssh.md
index d2f5d46b0b..3ba7722f9c 100644
--- a/translations/es-ES/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/es-ES/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-Cuando configuras SSH, [generarás una clave SSH y la agregarás al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) y luego [agregarás la clave a tu cuenta de {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account). Al agregar la clave SSH al ssh-agent te aseguras de que tu clave SSH tiene una capa extra de seguridad mediante el uso de una frase de contraseña. Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)".
+Cuando configures SSH, necesitarás generar una llave SSH nuevo y agregarla al agente ssh. Debes agregar la llave SSH a tu cuenta en {% data variables.product.product_name %} antes de utilizarla para autenticarte. Para obtener más información, consulta las secciones "[Generar una llave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" y "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
-{% if currentVersion == "free-pro-team@latest" %}Para utilizar tu llave SSH con un repositorio que pertenezca a una organización que utiliza el inicio de sesión único de SAML, necesitarás autorizarla primero. Para obtener más información, consulta "[Autorizar una clave SSH para usar con una clave de organización único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %}
+Puedes asegurar tu llave SSH aún más si utilizas una llave de seguridad de hardware, la cual requiere que esta última se conecte físicamente a tu computadora cuando se utilice el par de llaves para autenticarte con SSH. También puedes asegurar tu llave SSH si la agregas al ssh-agent y utiliza una contraseña. Para obtener más información, consulta la sección "[Trabajar con frases de acceso con llave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)".
 
-Te recomendamos que regularmente [revises tu listado de claves SSH](/articles/reviewing-your-ssh-keys) y revoques cualquiera que no sea válida o que se haya visto comprometida.
+{% if currentVersion == "free-pro-team@latest" %}Para utilizar tu llave SSH con un repositorio que pertenece a una organización que utiliza el inicio de sesión único de SAML, debes autorizar dicha llave. Para obtener más información, consulta "[Autorizar una clave SSH para usar con una clave de organización único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %}
+
+Para mantener la seguridad de cuenta, puedes revisar tu lista de llaves SSH frecuentemente y retirar cualquier llave que sea inválida o que se haya puesto en riesgo. Para obtener más información, consulta "[Revisar tus claves SSH](/github/authenticating-to-github/reviewing-your-ssh-keys)".
 
 {% if currentVersion == "free-pro-team@latest" %}
 Si no has utilizado tu llave SSH por un año, entonces
@@ -28,8 +30,4 @@ Si eres miembro de una organización que provee certificados SSH, puedes usar tu
 
 - "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)"
 - "[Probar tu conexión SSH](/articles/testing-your-ssh-connection)"
-- Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)"
 - "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)"
-{%- if currentVersion == "free-pro-team@latest" %}
-- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"
-{%- endif %}
diff --git a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index 5f67b151ed..ccea3dfeb5 100644
--- a/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/es-ES/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: También puedes agregar una llave SSH utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)" en la documentación de {% data variables.product.prodname_cli %}.
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. Copia la llave SSH pública a tu portapapeles.
@@ -80,6 +88,7 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product
   Si tu archivo de llave SSH pública tiene un nombre diferente que en el código de ejemplo, modifica el nombre de archivo para que coincida con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco.
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
   # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
 
diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index 647ec372af..dd3e86261a 100644
--- a/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/es-ES/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**Nota:** GPG no viene instalado por defecto en OS X o Windows. Para instalar las herramientas de la línea de comando, consulta [Página de descarga de GnuPG](https://www.gnupg.org/download/).
+**Nota:** GPG no viene instalado predeterminadamente en macOS ni Windows. Para instalar las herramientas de la línea de comando, consulta [Página de descarga de GnuPG](https://www.gnupg.org/download/).
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index 2c59208604..87d2781603 100644
--- a/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/es-ES/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %}, navega a tu solicitud de cambios.
 {% data reusables.repositories.review-pr-commits %}
-3. Junto al hash de confirmación abreviado de la confirmación, existe un cuadro que muestra si la firma de la confirmación está verificada o no está verificada. ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. Para ver información más detallada sobre la firma de confirmación, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). ![Confirmación firmada verificada](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-Si la firma de tu confirmación no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Confirmación firmada no verificada](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. Junto al hash de confirmación abreviado de tu confirmación, hay una casilla que te muestra si tu firma de confirmación se verificó{% if currentVersion == "free-pro-team@latest" %}, se verificó parcialmente,{% endif %} o si no se verificó. ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. Para ver información más detallada sobre la firma de confirmación, haz clic en **Verificada**{% if currentVersion == "free-pro-team@latest" %}, **Verificada parcialmente**,{% endif %} o **Sin verificar**. ![Confirmación firmada verificada](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### Comprobar el estado de verificación de firma de la etiqueta
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. En la parte superior de la página de lanzamiento, haz clic en **Tags** (Etiqueta). ![Página de etiquetas](/assets/images/help/releases/tags-list.png)
-3. Junto a la descripción de tu etiqueta, hay un cuadro que muestra si la firma de la etiqueta está verificada o no está verificada. ![firma de etiqueta verificada](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. Para ver información más detallada sobre la firma de la etiqueta, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). Si la firma de tu etiqueta no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Etiqueta firmada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. Junto a la descripción de tu etiqueta, hay una caja que muestra si tu firma de etiqueta está verificada{% if currentVersion == "free-pro-team@latest" %}, verificada parcialmente,{% endif %} o sin verificar. ![firma de etiqueta verificada](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. Para ver más información detallada sobre la firma de una etiqueta, haz clic en **Verificada**{% if currentVersion == "free-pro-team@latest" %},**Verificada parcialmente**,{% endif %} o **Sin verificar**. ![Etiqueta firmada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### Leer más
 
diff --git a/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md
index ee78e9a26e..385d6ed0f5 100644
--- a/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/es-ES/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas para la autenticación en {% data variables.product.product_name %} cuando utilizas la [API de GitHub](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) o la [línea de comandos](#using-a-token-on-the-command-line).
 
-{% if currentVersion == "free-pro-team@latest" %}Si quieres utilizar un PAT para acceder a los recursos que pertenecen a una organización que utiliza el SSO de SAML, debes autorizarlo. Para obtener más información, consulta las secciónes "[Acerca de la autenticación, con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Si quieres utilizar un PAT para acceder a los recursos que pertenecen a una organización que utiliza el SSO de SAML, debes autorizarlo. Para obtener más información, consulta las secciónes "[Acerca de la autenticación, con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### Crear un token
 
-{% if currentVersion == "free-pro-team@latest" %}1. [Verifica tu dirección de correo electrónico](/articles/verifying-your-email-address), si aún no ha sido verificada.{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. [Verifica tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address), si aún no ha sido verificada.{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -37,21 +37,21 @@ Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas p
    {% endif %}
 7. Haz clic en **Generar token**. ![Generar un botón para el token](/assets/images/help/settings/generate_token.png)
 8. Da clic en
-{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again.
+{% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar el token a tu portapapeles. Por razones de seguridad, después de navegar fuera de la págna, no podrás ver el token nuevamente.
    {% if currentVersion == "free-pro-team@latest" %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![Token recién creado](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png)
+   ![Token recién creado](/assets/images/help/settings/personal_access_tokens_ghe.png)
    {% else %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
+   ![Token recién creado](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **Advertencia:**Preserva tus tokens de la misma manera que tus contraseñas y no se las reveles a nadie. Cuando trabajes con la API, usa tokens como variables del entorno en lugar de codificarlos de forma rígida en tus programas.
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. Para usar tu token a fin de autenticar a una organización que usa SAML SSO, [autoriza el token para usarlo con una organización con inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. Para usar tu token para autenticar a una organización que usa SAML SSO, [autoriza el token para el uso con una organización con inicio de sesión único SAML.](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% endif %}
 
 ### Usar un token en la línea de comando
 
@@ -59,7 +59,7 @@ Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas p
 
 Los tokens de acceso personal solo se pueden usar para operaciones HTTPS Git. Si tu repositorio usa una URL SSH remota, necesitarás [pasar de la URL SSH remota a HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
 
-Si no se te solicita tu nombre de usuario y contraseña, tus credenciales pueden estar almacenadas en la caché de tu computadora. Puedes [actualizar tus credenciales en la keychain](/articles/updating-credentials-from-the-osx-keychain) para reemplazar tu contraseña anterior con el token.
+Si no se te solicita tu nombre de usuario y contraseña, tus credenciales pueden estar almacenadas en la caché de tu computadora. Puedes [actualizar tus credenciales en la keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) para reemplazar tu contraseña anterior con el token.
 
 ### Leer más
 
diff --git a/translations/es-ES/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/es-ES/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..47895a80cd
--- /dev/null
+++ b/translations/es-ES/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
+
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### Enabling vigilant mode
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/es-ES/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/es-ES/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..ae8e963978
--- /dev/null
+++ b/translations/es-ES/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### Prerrequisitos
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### Resolver el problema
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. Abre Terminal.
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. Para obtener más información, consulta "[Generar una nueva llave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index cf10981e07..37340e8b65 100644
--- a/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/es-ES/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-Si todavía no tienes una clave SSH, debes [generar una nueva clave SSH](#generating-a-new-ssh-key). Si no estás seguro de si ya tienes una clave SSH, comprueba las [claves existentes](/articles/checking-for-existing-ssh-keys).
+### Acerca de la generación de llaves SSH
 
-Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, puedes [agregar tu clave al SSH agent](#adding-your-ssh-key-to-the-ssh-agent), que gestiona tus claves SSH y recuerda tu contraseña.
+Si todavía no tienes una llave SSH, debes generar una nueva para utilizarla para autenticación. Si no estás seguro si ya tienes una llave SSH, puedes verificar si hay llaves existentes. Para obtener más información, consulta la sección "[Verificar si hay llaves SSH existentes](/github/authenticating-to-github/checking-for-existing-ssh-keys)".
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+Si quieres utilizar una llave de seguridad de hardware para autenticarte en {% data variables.product.product_name %}, debes generar una llave SSH nueva para esta. Debes conectar tu llave de seguridad de hardware a tu computadora cuando te autentiques con el par de llaves. Para obtener más información, consulta las[notas de lanzamiento de OpenSSH 8.2](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, puedes agregar tu clave al agente SSH, el cual administrará tus claves SSH y recordará tu contraseña.
 
 ### Generar una nueva clave SSH
 
@@ -62,7 +69,7 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu
 
   {% endlinux %}
 
-4. Donde se indica, escribe una contraseña segura. Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)".
+4. Donde se indica, escribe una contraseña segura. Para obtener más información, consulta la sección ["Trabajar con contraseñas de llaves SSH](/articles/working-with-ssh-key-passphrases)".
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu
 
 ### Agregar tu clave SSH al ssh-agent
 
-Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, debes haber [comprobado las claves SSH existentes](/articles/checking-for-existing-ssh-keys) y [generado una nueva clave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). <span class="platform-mac">Cuando agregues tu clave SSH al agente, usa el comando macOS `ssh-add` y no una aplicación instalada por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) o alguna otra fuente externa.</span>
+Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves, debes haber verificado si habían llaves SSH existentes y haber generado una llave SSH nueva. <span class="platform-mac">Cuando agregues tu clave SSH al agente, usa el comando macOS `ssh-add` y no una aplicación instalada por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) o alguna otra fuente externa.</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, deb
       $ touch ~/.ssh/config
       ```
 
-    * Abre tu archivo `~/.ssh/config` y luego modifícalo reemplazando `~/.ssh/id_ed25519` si no estás utilizando la ubicación y nombre predeterminados para tu llave de `id_ed25519`.
+    * Abre tu archivo `~/.ssh/config` y luego modifícalo para que contenga las siguientes líneas. Si tu llave SSH tiene un nombre o ruta diferentes que el código de ejemplo, modifica el nombre de archivo o ruta para que coincida con tu configuración actual.
 
       ```
       Host *
@@ -106,6 +113,25 @@ Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, deb
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **Nota:** Si ves un error como este
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      y una línea de configuración adicional en tu sección `Host *`:
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. Agrega tu llave privada SSH al ssh-agent y almacena tu contraseña en tu keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, deb
 
   {% endnote %}
 
-4. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)
+4. Agrega la llave SSH a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, deb
 2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)
+3. Agrega la llave SSH a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, deb
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  En algunos ambientes Linux, necesitarás acceso de raíz para ejecutar el comando:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)
+3. Agrega la llave SSH a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generar una llave SSH nueva para una llave de seguridad de hardware
+
+Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SSH o instalar un cliente SSH nuevo antes de generar una llave SSH nueva. Para obtener más información, consulta el "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)"
+
+1. Insterta tu clave de seguridad de hardware en tu computadora.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Pega el siguiente texto, sustitutyendo la dirección de correo electrónico por tu cuenta de {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Agregar una llave SSH nueva a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
+
+{% endif %}
+
 ### Leer más
 
 - "[Acerca de SSH](/articles/about-ssh)"
diff --git a/translations/es-ES/content/github/authenticating-to-github/index.md b/translations/es-ES/content/github/authenticating-to-github/index.md
index e2973fe270..1a7e7754f7 100644
--- a/translations/es-ES/content/github/authenticating-to-github/index.md
+++ b/translations/es-ES/content/github/authenticating-to-github/index.md
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 4790bc4c56..85ccf69d06 100644
--- a/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/es-ES/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ Puedes utilizar tus credenciales de autenticación de dos factores para recobrar
 5. Teclea la contraseña recibida en el correo electrónico de recuperación debajo de "Contraseña de una sola vez"{% 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.
-    - Si has utilizado tu dispositivo actual para ingresar en esta cuenta antes y quieres utilizarlo para verificación, da clic en **Verificar este dispositivo**.
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - 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.
diff --git a/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index f6689e1d19..0956e3442c 100644
--- a/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/es-ES/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -15,7 +15,7 @@ topics:
 
 {% mac %}
 
-Si [configuraste tu contraseña de clave SSH con OS X Keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), quizás puedas recuperarla.
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
 
 1. En Finder (Buscador), busca la aplicación **Keychain Access** (Acceso keychain). ![Barra Spotlight Search (Búsqueda de Spotlight)](/assets/images/help/setup/keychain-access.png)
 2. En Keychain Access (Acceso keychain), busca **SSH**.
diff --git a/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
index ac63096309..058a7656d1 100644
--- a/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
+++ b/translations/es-ES/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
@@ -31,12 +31,12 @@ Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file:
+1. Si no estás utilizando la suite de GPG, ejecuta el siguiente comando en el shell de `zsh` para agregar la llave GPG a tu archivo `.zshrc`, si es que existe, o a tu archivo `.zprofile`:
   ```shell
   $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi
   ```
-  Alternatively, if you use the `bash` shell, run this command:
+  Como alternativa, si utilizas el shell `bash`, ejecuta este comando:
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
@@ -93,7 +93,7 @@ Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. To add your GPG key to your bash profile, run the following command:
+1. Para agregar tu llave GPG a tu perfil bash, ejecuta el siguiente comando:
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
diff --git a/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md b/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md
index 0b23421c06..5b6c8f3d84 100644
--- a/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md
+++ b/translations/es-ES/content/github/authenticating-to-github/testing-your-ssh-connection.md
@@ -1,6 +1,6 @@
 ---
-title: Testing your SSH connection
-intro: 'After you''ve set up your SSH key and added it to your {% data variables.product.product_name %} account, you can test your connection.'
+title: Probar tu conexión SSH
+intro: 'Después de haber configurado tu clave SSH y haberla agregado a tu {% data variables.product.product_name %} cuenta, puedes probar tu conexión.'
 redirect_from:
   - /articles/testing-your-ssh-connection
 versions:
@@ -11,29 +11,29 @@ topics:
   - SSH
 ---
 
-Before testing your SSH connection, you should have:
-- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys)
-- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
-- [Added a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account)
+Antes de probar tu conexión SSH, debes haber hecho lo siguiente:
+- [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys)
+- [Generado una clave SSH nueva](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
+- [Agregado una clave SSH nueva a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)
 
-When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases).
+Cuando pruebes tu conexión, tendrás que autenticar esta acción utilizando tu contraseña, que es la contraseña de clave SSH que ya creaste. Para obtener más información acerca de trabajar con contraseñas de clave SSH, consulta ["Trabajar con contraseñas de clave SSH"](/articles/working-with-ssh-key-passphrases).
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Enter the following:
+2. Ingresa lo siguiente:
   ```shell
   $ ssh -T git@{% data variables.command_line.codeblock %}
   # Attempts to ssh to {% data variables.product.product_name %}
   ```
 
-  You may see a warning like this:
+  Puedes ver una advertencia como la siguiente:
 
   ```shell
-  > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established.
-  > RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
-  > Are you sure you want to continue connecting (yes/no)?
+  > La autenticidad del host '{% data variables.command_line.codeblock %} (DIRECCIÓN IP)' no se puede establecer.
+  > La clave de huella digital RSA es SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
+  > ¿Estás seguro de que quieres continuar conectado (sí/no)?
   ```
 
-3. Verify that the fingerprint in the message you see matches {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %}'s RSA public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`:
+3. Verifica que la huella dactilar en el mensaje que ves empate con % if currentVersion == "free-pro-team@latest" %} [aquella de la llave pública de RSA de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} aquella de la llave pública de tu empresa{% endif %}. Si lo hace, entonces teclea `yes`:
   ```shell
   > Hi <em>username</em>! You've successfully authenticated, but GitHub does not
   > provide shell access.
@@ -41,16 +41,16 @@ When you test your connection, you'll need to authenticate this action using you
 
   {% linux %}
 
-  You may see this error message:
+  Puede que veas el siguiente mensaje de error:
   ```shell
   ...
-  Agent admitted failure to sign using the key.
-  debug1: No more authentication methods to try.
-  Permission denied (publickey).
+  El agente admitió una falla para registrarse utilizando la clave.
+  debug1: No hay más métodos de autenticación para probar.
+  Permiso denegado (publickey).
   ```
 
-  This is a known problem with certain Linux distributions. For more information, see ["Error: Agent admitted failure to sign"](/articles/error-agent-admitted-failure-to-sign).
+  Se trata de un problema conocido con determinadas distribuciones de Linux. Para obtener más información, consulta ["Error: El agente admitió una falla para registrarse"](/articles/error-agent-admitted-failure-to-sign).
 
   {% endlinux %}
 
-4. Verify that the resulting message contains your username. If you receive a "permission denied" message, see ["Error: Permission denied (publickey)"](/articles/error-permission-denied-publickey).
+4. Comprueba que el mensaje resultante contenga tu nombre de usuario. Si recibes un mensaje de "permiso denegado", consulta ["Error: Permiso denegado (publickey)"](/articles/error-permission-denied-publickey).
diff --git a/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index 3394040c0e..f04ab97891 100644
--- a/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/es-ES/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -11,7 +11,7 @@ topics:
 
 {% tip %}
 
-**Usuarios de GitHub Enterprise**: Actualmente, no se puede acceder a GitHub Enterprise por SSH a través del puerto HTTPS.
+**Usuarios de {% data variables.product.prodname_ghe_server %}**: Actualmente no hay compatibilidad para acceder a {% data variables.product.prodname_ghe_server %} por SSH mediante el puerto HTTPS.
 
 {% endtip %}
 
diff --git a/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index e060f73c27..c13b384943 100644
--- a/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/es-ES/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -98,7 +98,7 @@ El proceso de `ssh-agent` continuará funcionando hasta que cierres sesión, apa
 
 ### Guardar tu contraseña en keychain
 
-En OS X Leopard a través de OS X El Capitan, los siguientes archivos de llave privada predeterminada se manejan automáticamente:
+On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index 1dcea1ae18..6bacbbfaaa 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: Acerca de los modelos de desarrollo colaborativo
-intro: El modo en que usas las solicitudes de extracción depende del tipo de modelo de desarrollo que uses en tu proyecto.
+intro: El modo en que usas las solicitudes de extracción depende del tipo de modelo de desarrollo que uses en tu proyecto. You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-Hay dos tipos principales de modelos de desarrollo con los cuales usar las solicitudes de extracción. En el *modelo de bifurcación y extracción*, cualquiera puede bifurcar un repositorio existente y subir los cambios a su bifurcación personal. No necesitas permiso del repositorio fuente para subir información a una bifurcación que sea propiedad del usuario. El mantenedor del proyecto puede extraer los cambios hacia el repositorio de origen. Cuando abres una solicitud de extracción que proponga cambios desde la bifurcación que es propiedad de tu usuario para ramificar en el repositorio fuente (ascendente), puedes permitir que cualquiera con acceso de escritura en éste haga cambios en dicha solicitud.  Este modelo es muy usado con los proyectos de código abierto, ya que reduce la cantidad de fricción para los colaboradores nuevos y le permite a las persona trabajar de forma independiente sin una coordinación inicial.
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. No necesitas permiso del repositorio fuente para subir información a una bifurcación que sea propiedad del usuario. El mantenedor del proyecto puede extraer los cambios hacia el repositorio de origen. Cuando abres una solicitud de extracción que proponga cambios desde la bifurcación que es propiedad de tu usuario para ramificar en el repositorio fuente (ascendente), puedes permitir que cualquiera con acceso de escritura en éste haga cambios en dicha solicitud.  Este modelo es muy usado con los proyectos de código abierto, ya que reduce la cantidad de fricción para los colaboradores nuevos y le permite a las persona trabajar de forma independiente sin una coordinación inicial.
 
 {% tip %}
 
@@ -20,7 +22,9 @@ Hay dos tipos principales de modelos de desarrollo con los cuales usar las solic
 
 {% endtip %}
 
-En el *modelo de repositorio compartido*, se le otorga a los colaboradores acceso de escritura a un único repositorio compartido y las ramas de tema son creadas cuando es necesario hacer cambios. Las solicitudes de extracción son útiles en este modelo ya que inician la revisión de código y el debate general acerca de un conjunto de cambios antes de que los mismos sean fusionados en la rama de desarrollo principal. Este modelo es más frecuente con las organizaciones y los equipos pequeños que colaboran en proyectos privados.
+### Shared repository model
+
+En el modelo de repositorio compartido, se le otorga a los colaboradores acceso de escritura a un único repositorio compartido y las ramas de tema son creadas cuando es necesario hacer cambios. Las solicitudes de extracción son útiles en este modelo ya que inician la revisión de código y el debate general acerca de un conjunto de cambios antes de que los mismos sean fusionados en la rama de desarrollo principal. Este modelo es más frecuente con las organizaciones y los equipos pequeños que colaboran en proyectos privados.
 
 ### Leer más
 
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index f73d82be02..fadcaaedaf 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -53,18 +53,18 @@ Cuando un repositorio se configura para que solicite automáticamente las verifi
 
 Para omitir o solicitar verificaciones para tu confirmación, agrega una de las siguientes lineas de introducción al final de tu mensaje de confirmación:
 
-- Para _omitir verificaciones_ para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. Después de la descripción de tu confirmación, en lugar de una comilla de cierre, agrega dos líneas vacías seguidas de `skip-checks: true`:
+- Para _omitir verificaciones_ para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - Para _solicitar_ verificaciones para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. Después de la descripción de tu confirmación, en lugar de una comilla de cierre, agrega dos líneas vacías seguidas de `request-checks: true`:
+- Para _solicitar_ verificaciones para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
index e3723c8ff7..e3bf7c4062 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
@@ -14,9 +14,9 @@ topics:
 
 Si habilitas la fusión automática para una solicitud de cambios, ésta se fusionará automáticamente cuando se cumplan todas las revisiones requeridas y cuando todas las verificaciones de estado hayan pasado. La fusión automática te evita el esperar a que los requisitos se cumplan para que puedas continuar con otras tareas.
 
-Antes de que utilices la fusión automática con una solicitud de cambios, esta característica se debe habilitar en el repositorio. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
+Antes de que utilices la fusión automática con una solicitud de cambios, esta característica se debe habilitar en el repositorio. Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)".{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
 
-After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %}
+Después de que habilitas la fusión automática para una solicitud de cambios, si alguien que no tiene permisos de escritura en el repositorio sube cambios nuevos a la rama principal o cambia la rama base de la solicitud de cambios, esta se inhabilitará. Por ejemplo, si un mantenedor habilita la fusión automática para una solicitud de cambios desde una bifurcación, esta se inhabilitará después de que el contribuyente suba cambios nuevos a la solicitud de cambios.{% endif %}
 
 Puedes proporcionar retroalimentación sobre la fusión automática si [nos contactas](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
 
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 1ef2fa5051..13e799c472 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. En la lista "Pull requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas marcar como disponibles para revisión.
 3. En la caja de fusión, da clic en **Listo para revisión**. ![Botón Ready for review (Disponible para revisión)](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index f1fe891dbd..3ea544a220 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Modificar una solicitud de extracción activa localmente
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index 6a8032451e..a1c436e724 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ Para responder un comentario en la línea que ya existe, deberás ir hasta el co
 
 **Tips:**
 - Los comentarios de las solicitudes de extracción soportan el mismo [ formato](/categories/writing-on-github) que los comentarios regulares en {% data variables.product.product_name %}, como @menciones, emojis y referencias.
-- Puedes [agregar reacciones](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) a los comentarios en las solicitudes de extracción en la pestaña **Files changed** (Archivos cambiados).
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index b2c98489d9..7afaf29737 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -20,6 +20,20 @@ Puedes especificar en qué rama deseas fusionar tus cambios cuando creas tu soli
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+
+
+
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+
+
+
+{% endif %}
+
 
 
 ### Cambiar el rango de la rama y el repositorio de destino
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index 0cbb6345b9..8a7ebfd2af 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ Si la rama que quieres borrar está asociada con una solicitud de cambios abiert
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. Desplázate hasta la rama que deseas eliminar y luego haz clic en {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![eliminar la rama](/assets/images/help/branches/branches-delete.png)
+1. Desplázate hasta la rama que deseas eliminar y luego haz clic en {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![eliminar la rama](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..90fa7c007f
--- /dev/null
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: Empezar
+shortTitle: Empezar
+intro: 'Aprende sobre el flujo de {% data variables.product.prodname_dotcom %} y las formas diferentes para debatir y colaborar en tus proyectos.'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md
index a5593b4b84..f119a4baca 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Colaborar con propuestas y solicitudes de extracción
-intro: 'Usa el flujo {% data variables.product.prodname_dotcom %} para hacer el seguimiento y debatir los cambios en las propuestas, luego propone y revisa los cambios en las solicitudes de extracción.'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -18,10 +18,9 @@ topics:
 
 ### Índice
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index 119c1fdab3..d5f0ab6454 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ No puedes fusionar un borrador de solicitud de cambios. Para obtener más inform
 
 Si decides que no deseas que los cambios en una rama de tema se fusionen con la rama ascendente, puedes [cerrar la solicitud de extracción](/articles/closing-a-pull-request) sin fusionar.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Fusionar una solicitud de extracción en {% data variables.product.prodname_dotcom %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..0a80a139c0
--- /dev/null
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### Introducción
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### Problemas
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### Solicitudes de cambios
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### Debates de equipo
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. En vez de abrir un informe de problemas en un repositorio para debatir sobre una idea, puedes incluir a todo el equipo si tienes una conversación en un debate de equipo.
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### Pasos siguientes
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. Para obtener más información, consulta [Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)".
diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index a86a7220b6..6fb06e5586 100644
--- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -79,5 +79,5 @@ Si cambias la visibilidad de un repositorio interno y luego lo borras, las bifur
 - "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)"
 - "[Acerca de las bifurcaciones](/articles/about-forks)"
 - "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)"
-- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
+- "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
 - "{% if currentVersion == "free-pro-team@latest" %}[Requerir políticas de administración de repositorios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}"
diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index a5e2d4be51..14f464a07a 100644
--- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ Si colocas tu archivo README en la raíz de tu repositorio, `docs`, o en el dire
 
 {% endif %}
 
+### Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+The auto-generated table of contents is enabled by default for all Markdown files in a repository, but you can disable this feature for your repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under "Features", deselect **Table of contents**. ![Automatic TOC setting for repositories](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### Enlaces de sección en los archivos README y las páginas blob
 
-Muchos proyectos usan un índice al comienzo de un archivo README para dirigir a los usuarios a diferentes secciones del archivo. {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### Enlaces relativos y rutas con imágenes en los archivos README
 
diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index ec82123be3..20e51d482a 100644
--- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -24,7 +24,7 @@ Cualquier usuario con permisos de lectura para un repositorio de plantillas pued
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas.
+Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 Crear un repositorio a partir de una plantilla es similar a bifurcar un repositorio, pero existen algunas diferencias importantes:
diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index 55ed4e6bc5..88fca1f3fe 100644
--- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -20,7 +20,7 @@ topics:
 
 Para crear un repositorio de plantilla, debes crear un repositorio y luego convertirlo en una plantilla. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)."
 
-Después de que conviertas tu repositorio en una plantilla, cualquiera con acceso a éste podrá generar un repositorio nuevo con la misma estructura de directorios y archivos que tu rama predeterminada.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} También podrán elegir incluir el resto de las ramas en tu repositorio.{% endif %} Para obtener más información, consulta la sección "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)".
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
index 0bf77e56c1..3b460c95ca 100644
--- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
+++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
@@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > provide shell access.
 ```
 
-Si el repositorio pertenece a una organización y estás utilizando una llave SSH generada por una OAuth App, puede que algún dueño de la organización haya restringido el acceso OAuth App. For more information, see "<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">About OAuth App access restrictions</a>."
+Si el repositorio pertenece a una organización y estás utilizando una llave SSH generada por una OAuth App, puede que algún dueño de la organización haya restringido el acceso OAuth App. Para obtener más información, consulta la sección "<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">Acerca de las restricciones de acceso a las OAuth Apps</a>".
 
 Para obtener más información, consulta "[Agregar una nueva clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)".
 
diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
index 223c057044..e1d65966f9 100644
--- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
+++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### Elegir la licencia correcta
 
-Creamos [choosealicense.com](http://choosealicense.com), para ayudarte a entender cómo generar una licencia para tu código. Una licencia de software les informa a las demás personas lo que pueden y no pueden hacer con tu código fuente; por lo tanto, es importante tomar una decisión informada.
+Creamos [choosealicense.com](https://choosealicense.com), para ayudarte a entender cómo generar una licencia para tu código. Una licencia de software les informa a las demás personas lo que pueden y no pueden hacer con tu código fuente; por lo tanto, es importante tomar una decisión informada.
 
 No tienes la obligación de elegir una licencia. Sin embargo, sin una licencia, se aplican las leyes de derecho de autor predeterminadas, lo que implica que conservas todos los derechos de tu código fuente, y nadie puede reproducir, distribuir o crear trabajos a partir de tu trabajo. Si estás creando un proyecto de código abierto, te alentamos fuertemente a que incluyas una licencia de código abierto. La [Guía de código abierto](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) brinda más orientación para elegir la licencia correcta para tu proyecto.
 
@@ -76,7 +76,7 @@ Cuando busques por una licencia de familia, los resultados incluirán todas las
 
 ### Detectar una licencia
 
-[El titular de licencia de la gema de código abierto Ruby](https://github.com/licensee/licensee) compara el archivo *LICENSE* (LICENCIA) del repositorio con una lista corta de licencias conocidas. El titular de licencia también proporciona las [API de licencias](/rest/reference/licenses) y [nos da información sobre las licencias que tienen los repositorios de {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Si tu repositorio utiliza una licencia que no está detallada en el [Sitio web Choose a License](http://choosealicense.com/appendix/), puedes[solicitar incluir la licencia](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+[El titular de licencia de la gema de código abierto Ruby](https://github.com/licensee/licensee) compara el archivo *LICENSE* (LICENCIA) del repositorio con una lista corta de licencias conocidas. El titular de licencia también proporciona las [API de licencias](/rest/reference/licenses) y [nos da información sobre las licencias que tienen los repositorios de {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Si tu repositorio utiliza una licencia que no está detallada en el [Sitio web Choose a License](https://choosealicense.com/appendix/), puedes[solicitar incluir la licencia](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
 
 Si tu repositorio utiliza una licencia que está detallada en el sitio web Choose a License y no se muestra claramente en la parte superior de la página del repositorio, puede que contenga múltiples licencias u otra complejidad. Para que se detecten tus licencias, simplifica tu archivo *LICENSE* y anota la complejidad en algún otro lado, como en el archivo *README* de tu repositorio.
 
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
index 44de639e61..0bb5e8f390 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
@@ -1,52 +1,43 @@
 ---
-title: About code scanning
-intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.'
+title: Acerca del escaneo de código
+intro: 'Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar vulnerabilidades de seguridad y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
-redirect_from:
-  - /github/managing-security-vulnerabilities/about-automated-code-scanning
 versions:
   enterprise-server: '2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-### About {% data variables.product.prodname_code_scanning %}
+### Acerca de {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.about-code-scanning %}
 
-You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
+Puedes utilizar {% data variables.product.prodname_code_scanning %} para encontrar, clasificar y priorizar los arreglos a problemas existentes en tu código. {% data variables.product.prodname_code_scanning_capc %} también previene a los desarrolladores de introducir nuevos problemas. Puedes programar días y horas específicos para los escaneos, o activarlos cuando ocurra un evento específico en el repositorio, tal como una carga de información.
 
-If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+Si {% data variables.product.prodname_code_scanning %} encuentra una vulnerabilidad potencial o un error en tu código, {% data variables.product.prodname_dotcom %} mostrará una alerta en el repositorio. {% data variables.product.prodname_dotcom %} cerrará la alerta una vez que arregles el código que la activó. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)".
 
-To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see 
-"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see  "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." 
+Para monitorear los resultados del {% data variables.product.prodname_code_scanning %} a lo largo de tus repositorios o de tu organización, puedes utilizar webhooks y la API del {% data variables.product.prodname_code_scanning %}. Para obtener más información sobre los webhooks para el {% data variables.product.prodname_code_scanning %}, consulta la sección [Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". Para obtener más información sobre las terminales de la API, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)".
 
-To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)."
+Para iniciar con el {% data variables.product.prodname_code_scanning %}, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)".
 
-### About {% data variables.product.prodname_codeql %}
+### Acerca de {% data variables.product.prodname_codeql %}
 
-You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. 
+Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). {% data variables.product.prodname_codeql %} trata el código como datos, lo cual te permite encontrar vulenrabilidades potenciales en tu código con más confianza que en los anallizadores estáticos trandicionales.
 
-{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website.
+{% data variables.product.prodname_ql %}Es el lenguaje de consulta que impulsa a {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} es un lenguaje de programación lógico orientado a objetos. {% data variables.product.company_short %}, los expertos del lenguaje, y los investigadores de seguridad crean las consultas que se utilizan para {% data variables.product.prodname_code_scanning %}, y éstas son de código abierto. La comunidad mantiene y actualiza estas consultas para mejorar el análisis y reducir los falsos positivos. Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) en el sitio web de GitHub Security Lab.
 
-{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
+Para obtener más información acerca de las terminales de la API para {% data variables.product.prodname_code_scanning %}, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)".
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation.
+Puedes ver y contribuir con las consultas para {% data variables.product.prodname_code_scanning %} en el repositorio [`github/codeql`](https://github.com/github/codeql). Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) en la documentación de {% data variables.product.prodname_codeql %}.
 
-{% if currentVersion == "free-pro-team@latest" %}
-
-### About billing for {% data variables.product.prodname_code_scanning %}
-
-{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
-
-{% endif %}
-
-### About third-party code scanning tools
+### Acerca de las herramientas de escaneo de código de terceros
 
 {% data reusables.code-scanning.you-can-upload-third-party-analysis %}
 
@@ -54,9 +45,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 {% data reusables.code-scanning.get-started-uploading-third-party-data %}
 
-### Further reading
+### Leer más
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
-- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
+- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) en el sitio web del Comité OASIS
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index 1e06219c04..4c59c79b17 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 8e7baf62d7..80cc3a24fe 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
index 63ae5d3b4c..9412448624 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring code scanning
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+title: Configurar el escaneo de código
+intro: 'Puedes configurar la forma en que {% data variables.product.prodname_dotcom %} escanea el código en tu proyecto para encontrar vulnerabilidades y errores.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
 miniTocMaxHeadingLevel: 4
@@ -10,52 +10,52 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About {% data variables.product.prodname_code_scanning %} configuration
+### Acerca de la configuración de {% data variables.product.prodname_code_scanning %}
 
-You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %}, utilizando las {% data variables.product.prodname_actions %}, o desde tu sistema de integración contínua (IC), si utilizas el {% data variables.product.prodname_codeql_runner %}. Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". Para obtener más información acerca del {% data variables.product.prodname_codeql_runner %}, consulta la sección [Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
 
-This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}.
+Este artículo se trata de ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %}.
 
-Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)."
+Antes de que puedas configurar el {% data variables.product.prodname_code_scanning %} para un repositorio, debes configurar el {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a este. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)".
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+El análisis de {% data variables.product.prodname_codeql %} es tan solo un tipo de {% data variables.product.prodname_code_scanning %} que puedes hacer en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %} en {% data variables.product.prodname_dotcom_the_website %} contiene otros flujos de trabajo del {% data variables.product.prodname_code_scanning %} que puedes utilizar. Los ejemplos específicos que se muestran en este artículo se relacionan con el archivo de {% data variables.product.prodname_codeql_workflow %}.
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} guarda los archivos de flujo de trabajo en el directorio de _.github/workflows_ de tu repositorio. Puedes encontrar un flujo de trabajo que hayas agregado si buscas su nombre de archivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. En tu repositorio, navega hasta el archivo de flujo de trabajo que deseas editar.
+1. En el ángulo superior derecho de la vista del archivo, para abrir el editor de flujo de trabajo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}.![Botón para editar un archivo de flujo de trabajo](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. Después de que hayas editado el archivo, da clic en **Iniciar confirmación** y completa el formato de "Cambios de la confirmación". Puedes elegir confirmar directamente en la rama actual, o crear una rama nueva e iniciar una solicitud de extracción. ![Confirmar la actualización del flujo de trabajo de codeql.yml](/assets/images/help/repository/code-scanning-workflow-update.png)
 
-For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Para obtener más información acerca de cómo editar los archivos de flujo de trabajo, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
-### Configuring frequency
+### Configurar la frecuencia
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+Puedes escanear código con cierta programación o cuando ocurren eventos específicos en un repositorio.
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+Escanear el código en cada carga al repositorio, y cada vez que se crea una solicitud de extracción, previene que los desarrolladores introduzcan vulnerabilidades y errores nuevos en dicho código. Escanear el código con una programación definida te informará de las últimas vulnerabilidades y errores que {% data variables.product.company_short %}, los investigadores de seguridad, y la comunidad descubren, aún cuando los desarrolladores no estén manteniendo el repositorio activamente.
 
-#### Scanning on push
+#### Escanear cuando se carga información
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+Si utilizas el flujo de trabajo predeterminado, el {% data variables.product.prodname_code_scanning %} escaneará el código en tu repositorio una vez por semana, adicionalmente a los escaneos activados por los eventos. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)".
 
-#### Scanning pull requests
+#### Escanear las solicitudes de extracción
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza el evento `pull_request` para activar un escaneo de código sobre las solilcitudes de cambios que se dirigen a la rama predeterminada. El evento `pull_request` no se activa si se abrió la solicitud de cambios desde una bifurcación privada.
 
-For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+Para obtener más información acerca del evento `pull_request`, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)".
 
-#### Avoiding unnecessary scans of pull requests
+#### Evitar escaneos innecesarios en las solicitudes de cambios
 
-You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+Puede que quieras evitar que se active un escaneo de código en solicitudes de cambio específicas que se dirijan a la rama predeterminada, independientemente de los archivos que se hayan cambiado. Puedes configurar esto si especificas `on:pull_request:paths-ignore` o `on:pull_request:paths` en el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. Por ejemplo, si los únicos cambios en una solicitud de cambios se hacen en archivos con las extensiones `.md` o `.txt`, puedes utilizar el siguiente arreglo de `paths-ignore`.
 
 ``` yaml
 on:
@@ -70,28 +70,28 @@ on:
 
 {% note %}
 
-**Notes**
+**Notas**
 
-* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+* `on:pull_request:paths-ignore` y `on:pull_request:paths` configuran condiciones que determinan si una acción en el flujo de trabajo se ejecutará en una solicitud de cambios. No determinan qué archivos se analizarán cuando las acciones _se_ ejecuten. Cuando una solicitud de cambios contiene cualquier archivo que no coincida con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, el flujo de trabajo ejecuta las acciones y escanea todos los archivos que cambiaron en la solicitud de cambios, incluyendo aquellos que coincidieron con `on:pull_request:paths-ignore` o con `on:pull_request:paths`, a menos de que éstos se hayan excluido. Para obtener más información sobre cómo excluir archivos del análisis, consulta la sección "[Especificar directorios para escanear](#specifying-directories-to-scan)".
+* Para los archivos de flujo de trabajo del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, no utilices las palabras clave `paths-ignore` o `paths` con el evento `on:push`, ya que es probable que cause que falten análisis. Para obtener resultados precisos, el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} necesita poder comparar los cambios nuevos con el análisis de la confirmación previa.
 
 {% endnote %}
 
-For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+Para obtener más información acerca de utilizar `on:pull_request:paths-ignore` y `on:pull_request:paths` para determinar cuando se ejecutará un flujo de trabajo para una solicitud de cambios, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)".
 
-#### Scanning on a schedule
+#### Escanear de forma pre-programada
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+El flujo de trabajo del {% data variables.product.prodname_code_scanning %} utiliza el evento `pull_request` para activar un escaneo de código en la confirmación `HEAD` de una solicitud de extracción. Para ajustar este programa, edita el valor `cron` en el flujo de trabajo. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)".
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+**Nota**: {% data variables.product.prodname_dotcom %} solo ejecuta jobs pre-programados que se encuentren en flujos de trabajo de la rama predeterminada. Cambiar la programación en un flujo de trabajo en cualquier otra rama no tendrá efecto hasta que fusiones esta rama con la predeterminada.
 
 {% endnote %}
 
-#### Example
+#### Ejemplo
 
-The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+El siguiente ejemplo muestra un {% data variables.product.prodname_codeql_workflow %} para un repositorio particular que tiene una rama predeterminada que se llama `main` y una protegida que se llama `protected`.
 
 ``` yaml
 on:
@@ -100,19 +100,17 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 15 * * 0'
+    - cron: '40 7 * * 2'
 ```
 
-This workflow scans:
-* Every push to the default branch and the protected branch
-* Every pull request to the default branch
-* The default branch at 3 P.M. every Sunday
+Este flujo de trabajo escanea:
+* Cada subida a la rama predeterminada y a la rama protegida
+* Cada solicitud de cambios a la rama predeterminada
+* La rama predeterminada cada martes a las 7:40 UTC
 
-### Specifying an operating system
+### Especificar un sistema operativo
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
-
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+Si tu código requiere un sistema operativo específico para compilar, puedes configurarlo en tu flujo de trabajo. Edita el valor de `jobs.analyze.runs-on` para especificar el sistema operativo para la máquina que ejecuta tus acciones de {% data variables.product.prodname_code_scanning %}. Se especifica el sistema operativo usando una etiqueta adecuada como el segundo elemento en una matriz de dos elementos, después de `self-hosted`.
 
 ``` yaml
 jobs:
@@ -121,23 +119,21 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% data variables.product.prodname_code_scanning_capc %} es compatible con las últimas versiones de macOs, Ubuntu, y Windows. Los valores habituales para esta configuración son por lo tanto: `ubuntu-latest`, `windows-latest`, y `macos-latest`. Para obtener más información, consulta las secciones "[Sintaxis de flujos de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" y "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)".
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+Debes asegurarte de que Git esté en la variable PATH en tus ejecutores auto-hospedados.
 
-{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
+### Cambiar los lenguajes que se analizan
 
-### Changing the languages that are analyzed
+El {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} detecta automáticamente el código que se escribe en los lenguajes compatibles.
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-{% data reusables.code-scanning.supported-languages %}
-
-The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+El archivo predeterminado del {% data variables.product.prodname_codeql_workflow %} contiene una matriz de compilación que se llama `language`, la cual lista los lenguajes en tu repositorio que se han analizado. El {% data variables.product.prodname_codeql %} llena automáticamente esta matriz cuando agregas el {% data variables.product.prodname_code_scanning %} a un repositorio. Cuando se utiliza la matriz de `language` se optimiza a {% data variables.product.prodname_codeql %} para ejecutar cada análisis en paralelo. Te recomendamos que todos los flujos de trabajo adopten esta configuración debido a los beneficios de rendimiento que implica el paralelizar las compilaciones. Para obtener más información acerca de las matrices de compilación, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix.
+Si tu flujo de trabajo utiliza la matriz `language`, entonces {% data variables.product.prodname_codeql %} se codifica fijamente para analizar únicamente los lenguajes en dicha matriz. Para cambiar los lenguajes que quieres analizar, edita el valor de la variable de la matriz. Puedes eliminar un lenguaje para que no se analice, o puedes agregar alguno que no estuviera presente en el repositorio cuando se configuró el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se configuró el {% data variables.product.prodname_code_scanning %}, y luego quieres agregar código de Python, entonces necesitarás agregar `python` a la matriz.
 
 ```yaml
 jobs:
@@ -150,7 +146,7 @@ jobs:
         language: ['javascript', 'python']
 ```
 
-If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action.
+Si tu flujo de trabajo no contiene una matriz que se llame `language`, entonces {% data variables.product.prodname_codeql %} se configurará para ejecutar un análisis secuencialmente. Si no especificas los lenguajes en los flujos de trabajo, {% data variables.product.prodname_codeql %} detectará e intentará analizar cualquier lenguaje compatible que haya en el repositorio. Si quieres elegir qué lenguajes analizar sin utilizar una matriz, puedes utilizar el parámetro `languages` en la acción de `init`.
 
 ```yaml
 - uses: github/codeql-action/init@v1
@@ -158,80 +154,90 @@ If your workflow does not contain a matrix called `language`, then {% data varia
     languages: cpp, csharp, python
 ```
 {% if currentVersion == "free-pro-team@latest" %}
-### Analyzing Python dependencies
+### Analizar las dependencias de Python
 
-For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
+Para los ejecutores hospedados en GitHub que utilicen solo Linux, el {% data variables.product.prodname_codeql_workflow %} intentarà instalar automàticamente las dependencias de Python para dar màs resultados para el anàlisis de CodeQL. Puedes controlar este comportamiento si especificas el paràmetro `setup-python-dependencies` para la acciòn que el paso "Initialize CodeQL" llama. Predeterminadamente, este paràmetro se configura como `true`:
 
--  If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies.
+-  Si el repositorio contiene còdigo escrito en Python, el paso "Initialize CodeQL" instala las dependencias necesarias en el ejecutor hospedado en GitHub. Si la instalaciòn automàtica es exitosa, la acciòn tambièn configura la variable de ambiente `CODEQL_PYTHON` en el archivo ejecutable de Python que incluye las dependencias.
 
-- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete.
+- Si el repositorio no tiene ninguna dependencia de Python o si las dependencias se especifican en una forma inesperada, obtendràs una advertencia y la acciòn seguirà con los jobs restantes. La acciòn puede ejecutarse exitosamente aùn cuando existan problemas para interpretar las dependencias, pero los resultados podrìan estar incompletos.
 
-Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract:
+Como alternativa, puedes instalar las dependencias de Python manualmente en cualquier sistema operativo. Necesitaràs agregar a `setup-python-dependencies` y configurarlo como `false`, asì como configurar `CODEQL_PYTHON` para el ejecutable de Python que incluye las dependencias, tal como se muestra en este extracto de flujo de trabajo:
 
 ```yaml
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
-### Running additional queries
+### Ejecutar consultas adicionales
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow.
+Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. Si las consultas están en un repositorio privado, utiliza el parámetro `external-repository-token` para especificar un token que tenga acceso a este.
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     queries: COMMA-SEPARATED LIST OF PATHS
+    # Optional. Provide a token to access private repositories.
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+También puedes ejecutar conjuntos de consultas adicionales si los especificas en un archivo de configuración. Los conjuntos de consultas son colecciones de consultas que a menudo se agrupan por propósito o lenguaje.
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+Puedes ejecutar consultas adicionales si las especificas en un archivo de configuración. So quieres ejecutar el conjunto combinado de consultas adicionales que se especifica aquí y en el archivo de configuración, agrega como prefijo el valor `queries` en el flujo de trabajo con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)".
 
-In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
+En el siguiente ejemplo, el símbolo `+` se asegura de que las consultas adicionales especificadas se utilicen en conjunto con cualquier otra consulta que se especifique en el archivo de configuración referenciado.
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     config-file: ./.github/codeql/codeql-config.yml
     queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
-### Using a custom configuration file
+### Utilizar una herramienta de escaneo de código de terceros
 
-As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
+Como alternativa para especificar qué consultas se ejecutarán en un archivo de flujo de trabajo, puedes hacer esto en un archivo de configuración diferente. También puedes utilizar un archivo de configuración para inhabilitar las consultas predeterminadas y para especificar qué directorios escanear durante el análisis.
 
-In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acción `init` para especificar la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _./.github/codeql/codeql-config.yml_.
 
 ``` yaml
 - uses: github/codeql-action/init@v1
@@ -239,13 +245,23 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp
     config-file: ./.github/codeql/codeql-config.yml
 ```
 
-The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. 
+{% data reusables.code-scanning.custom-configuration-file %}
 
-The settings in the file are written in YAML format.
+El archivo de configuración se ubica en un repositorio privado externo, utiliza el parámetro `external-repository-token` de la acción `init` para especificar un token que tenga acceso al repositorio privado.
 
-#### Specifying additional queries
+{% raw %}
+```yaml
+uses: github/codeql-action/init@v1
+with:
+  external-repository-token: ${{ secrets.ACCESS_TOKEN }}
+```
+{% endraw %}
 
-You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
+Los ajustes en el archivo de configuración se escriben en formato YAML.
+
+#### Especificar consultas adicionales
+
+Puedes especificar consultas adicionales en una matriz de `queries`. Cada elemento de la matriz contiene un parámetro de `uses` con un valor que identifica un archivo de consulta simple, un directorio que contiene los archivos de consulta, o un archivo de suite de definiciones de una consulta.
 
 ``` yaml
 queries:
@@ -254,17 +270,17 @@ queries:
   - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls
 ```
 
-Optionally, you can give each array element a name, as shown in the example configuration files below.
+Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración.
 
-For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
+Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)".
 
-#### Disabling the default queries
+#### Inhabilitar las consultas predeterminadas
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+Si solo quieres ejecutar consultas personalizadas, puedes inhabilitar las consultas de seguridad predeterminadas si agregas `disable-default-queries: true` a tu archivo de configuración.
 
-#### Specifying directories to scan
+#### Especificar directorios para escanear
 
-For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
+Para los lenguajes interpretados compatibles con {% data variables.product.prodname_codeql %} (Python y JavaScript/TypeScript), puedes restringir el {% data variables.product.prodname_code_scanning %} para los archivos que estén en directorios específicos si agregas una matriz de `paths` al archivo de configuración. Puedes excluir del análisis los archivos en los directorios específicos si agregas un arreglo de `paths-ignore`.
 
 ``` yaml
 paths:
@@ -276,46 +292,28 @@ paths-ignore:
 
 {% note %}
 
-**Note**:
+**Nota**:
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* Las palabras clave `paths` y `paths-ignore` que se utilizan en el contexto del archivo de configuración del {% data variables.product.prodname_code_scanning %} no deben confundirse con las mismas palabras clave cuando se utilizan para `on.<push|pull_request>.paths` en un flujo de trabajo. Cuando se tulizan para modificar `on.<push|pull_request>` en un flujo de trabajo, éstas determinan si las acciones se ejecutarán cuando alguien modifique el código en los directorios especificados. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)".
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por ejemplo, `foo/**`, `**/foo`, y `foo/**/bar` son todas sintaxis permitidas, pero `**foo` no lo es. Sin embargo, puedes utilizar asteriscos sencillos con otros caracteres, tal como se muestra en el ejemplo. Tendrás que poner entre comillas todo lo que contenga un caracter de `*`.
 
 {% endnote %}
 
-For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+Para los lenguajes compilados, si quieres limitar el {% data variables.product.prodname_code_scanning %} para directorios específicos en tu proyecto, debes especificar los pasos de compilación adecuados en el flujo de trabajo. Los comandos que necesites utilizar para excluir un directorio de la compilación dependerán en tu sistema de compilación. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+Puedes analizar rápidamente partes pequeñas de un monorepo cuando modificas el código en directorios específicos. Necesitarás tanto excluir los directorios en tus pasos de compilación como utilizar las palabras clave `paths-ignore` y `paths` para [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) en tu archivo de flujo de trabajo.
 
-#### Example configuration files
+#### Ejemplos de archivos de configuración
 
 {% data reusables.code-scanning.example-configuration-files %}
 
-### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+### Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados
 
 {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)."
+{% data reusables.code-scanning.autobuild-add-build-steps %} Para obtener más información acerca de cómo configurar el {% data variables.product.prodname_codeql %} del {% data variables.product.prodname_code_scanning %} para los lenguajes compilados, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)".
 
-### Accessing private repositories
+### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}.
 
-If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs.<job_id>.steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
-
-For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable.
-
-{% raw %}
-```yaml
-steps:
-- name: Configure access to private repositories
-  env:
-    TOKEN: ${{ secrets.ACCESS_TOKEN }}
-  run: |
-    git config --global url."https://${TOKEN}@github.com/ghost/foo".insteadOf "https://github.com/ghost/foo"
-    git config --global url."https://${TOKEN}@github.com/ghost/bar".insteadOf "https://github.com/ghost/bar"
-    git config --global url."https://${TOKEN}@github.com/ghost/baz".insteadOf "https://github.com/ghost/baz"
-```
-{% endraw %}
-
-### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
-
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)."
+{% data variables.product.prodname_dotcom %} puede mostrar los datos de análisis de código que se generan externamente con una herramienta de terceros. Puedes mostrar el análisis de código de una herramienta de terceros en {{ site.data.variables.product.prodname_dotcom }} su agregas la acción `upload-sarif` en tu flujo de trabajo. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)".
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index 798878e7b5..e1364d64ae 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -48,11 +50,11 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 El {% data variables.product.prodname_codeql_runner %} detecta automáticamente y escanea el código que se ha escrito en los lenguajes compatibles.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-Para anular la detección automática de lenguajes, ejecuta el comando `init` con el marcador `--languages`, seguido de una lista separada por comas de las palabras clave de los lenguajes. Las palabras clave para los lenguajes compatibles son `cpp`, `csharp`, `go`, `java`, `javascript`, y `python`.
+Para anular la detección automática de lenguajes, ejecuta el comando `init` con el marcador `--languages`, seguido de una lista separada por comas de las palabras clave de los lenguajes. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index 3f75a18943..1222151005 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -31,11 +33,7 @@ Si tu flujo de trabajo utiliza una matriz de `language`, el `autobuild` intentar
 
 {% note %}
 
-{% if currentVersion == "github-ae@latest" %}**Nota**: Para obtener instrucciones sobre cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tiene instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)".
-{% else %}
-**Nota**: Si usas ejecutores auto-hospedados para
-{% data variables.product.prodname_actions %}, puede que necesites instalar el software adicional para utilizar el proceso `autobuild`. Adicionalmente, si tu repositorio requiere de una versión específica de una herramienta de compilación, tal vez necesites instalarla manualmente. Para obtener más información, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
-{% endif %}
+**Nota**: Si utilizas los ejecutores auto-hospedados para {% data variables.product.prodname_actions %}, tal vez necesites instalar software adicional para utilizar el proceso de `autobuild`. Adicionalmente, si tu repositorio requiere de una versión específica de una herramienta de compilación, tal vez necesites instalarla manualmente. Para obtener más información, consulta la sección "[Especificaciones para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index 123097016c..a3b862d9df 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### Índice
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 0a317d953f..5f02f1bef8 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index 54831ed3c7..dfeb8cffc6 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,13 +1,15 @@
 ---
 title: Administrar las alertas del escaneo de código para tu repositorio
 shortTitle: Administrar alertas
-intro: 'Desde la vista de seguridad, puedes ver, arreglar, {% if currentVersion == "enterprise-server@2.22" %}o cerrar{% else %}descartar, o borrar{% endif %} las alertas para las vulnerabilidades potenciales o para los errores en el código de tus proyectos.'
+intro: 'Desde la vista de seguridad, puedes ver, corregir o cerrar las alertas de vulnerabilidades potenciales o errores en el código de tu proyecto.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca de las alertas de {% data variables.product.prodname_code_scanning %}
@@ -45,81 +47,25 @@ Necesitas permisos de escritura para ver un resumen de todas las alertas de un r
 
 Cualquiera con permisos de escritura en un repositorio puede arreglar una alerta si confirma una corrección en el código. Si el repositorio tiene programado un {% data variables.product.prodname_code_scanning %} para ejecutarse en las solicitudes de cambios, es mejor levantar una solicitud de cambios con tu corrección. Esto activará el análisis del {% data variables.product.prodname_code_scanning %} en los cambios y probará que tu arreglo no introduciría ningún problema nuevo. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" y "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)".
 
-Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista de "Cerrados" muestra las alertas solucionadas y aquellas que los usuarios {% if currentVersion == "enterprise-server@2.22" %}cerraron{% else %}descartaron{% endif %}.
+Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista "Cerrada" muestra las alertas fijas y las que cerraron los usuarios.
 
 Las alertas pueden arreglarse en una rama pero no en alguna otra. Puedes utilizar el menú desplegable de "Rama", en el resumen de las alertas, para verificar si una alerta se arregló en una rama en particular.
 
 ![Filtrar alertas por rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 ### Cerrar una alerta
 
 Cerrar una alerta es una forma de resolverla si no crees que necesita un arreglo. {% data reusables.code-scanning.close-alert-examples %}
 
-{% else %}
-
-### Descartar o borrar las alertas
-
-Hay dos formas de cerrar una alerta. Puedes arreglar el problema en el código, o puedes descartar la alerta. Como alternativa, si tienes permisos adminsitrativos en el repositorio, puedes borrar las alertas. Borrar las alertas es útil en situaciones en donde configuraste una herramienta del {% data variables.product.prodname_code_scanning %} y luego decidiste eliminarla, o donde configuraste el análisis de {% data variables.product.prodname_codeql %} con un conjunto más grande de consultas que quieres seguir utilizando y después eliminaste algunas de ellas de la herramienta. En ambos casos, el borrar las alertas te permite limpiar tus resultados del {% data variables.product.prodname_code_scanning %}. Puedes borrar las alertas de la lista de resumen dentro de la pestaña de **Seguridad**.
-
-El descartar una alerta es una forma de cerrar aquellas que no crees que necesiten arreglo. {% data reusables.code-scanning.close-alert-examples %} Puedes eliminar alertas desde las anotaciones del {% data variables.product.prodname_code_scanning %} en el código, o desde la lista de resumen dentro de la pestaña de **Seguridad**.
-
-Cuando descartas una alerta:
-
-- Se descarta en todas las ramas.
-- La alerta se elimina de la cantidad de alertas actuales para tu proyecto.
-- La alerta se mueve a la lista de "Cerrado" en el resumen de alertas, desde donde puedes volver a abrirla en caso de que lo necesites.
-- La razón por la cual cerraste la alerta se registra.
-- La siguiente vez que se ejecute el {% data variables.product.prodname_code_scanning %}, este código no volverá a generar una alerta.
-
-Cuando borras una alerta:
-
-- Se borra en todas las ramas.
-- La alerta se elimina de la cantidad de alertas actuales para tu proyecto.
-- _No_ seagrega a la lista de "Cerrado" en el resumen de las alertas.
-- Si el código que generó la alerta se mantiene tal cual, y se ejecuta nuevamente la misma herramienta del {% data variables.product.prodname_code_scanning %} sin ningún cambio de configuración, la alerta se mostrará nuevamente en los resultados de tu análisis.
-
-Para descartar o borrar una alerta:
-
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
 1. Selecciona el menú desplegable de **Cerrar** y da clic en una razón para cerrar la alerta.    
    ![Elegir una razón apra cerrar la alerta a través del menú desplegable de "Cerrar"](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. Si tienes permisos administrativos en el repositorio y quieres borrar las alertas para esta herramienta del {% data variables.product.prodname_code_scanning %}, selecciona algunas o todas las casillas de verificación y da clic en **Borrar**.
-
-   ![Borrar alertas](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   Opcionalmente, puedes utilizar los filtros para mostrar un subconjunto de alertas y luego borrar simultáneamente todas las que empaten. Por ejemplo, si eliminaste una consulta desde el análisis de {% data variables.product.prodname_codeql %}, puedes utilizar el filtro de "Regla" para listar solo las alertas para esa consulta y luego seleccionar y borrar todas esas alertas.
-
-  ![Filtrar alertas por regla](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. Si quieres descartar una alerta, es importante explorarla primero para que puedas elegir la razón correcta para descartarla. Da clic en la alerta que quisieras explorar.
-
-  ![Abrir una alerta desde la lista de sumario](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. Revisa la alerta y da clic en **Descartar** y elije una razón para cerrarla. ![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### Descartar varias alertas al mismo tiempo
-
-Si un proyecto tiene varias alertas que quieras descartar por la misma razón, puedes descartarlas por lote desde el resúmen de las alertas. Habitualmente quieres filtrar la lista y luego descartar todas las alertas coincidentes. Por ejemplo, puede que quieras descartar todas las alertas actuales del proyecto que se hayan etiquetado para una vulnerabilidad de Enumeración de Debilidades (CWE, por sus siglas en inglés) Común en particular.
-
-{% endif %}
-
 ### Leer más
 
 - "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index 370a047b53..f33717e29b 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca del {% data variables.product.prodname_code_scanning %} con una compilación en contenedor
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index b46d6a2c06..f3519750e2 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
@@ -30,17 +31,13 @@ El {% data variables.product.prodname_codeql_runner %} es una herramienta de lí
 {% note %}
 
 **Notas:**
-{% if currentVersion == "free-pro-team@latest" %}
-* El {% data variables.product.prodname_codeql_runner %} utiliza el CLI de {% data variables.product.prodname_codeql %} para analizar el código y, por lo tanto, tiene las mismas condiciones de licencia. Se puede utilizar gratuitamente en los repositorios que mantiene {% data variables.product.prodname_dotcom_the_website %}, y está disponible para utilizarse en aquellos que pertenecen a los clientes con una licencia de {% data variables.product.prodname_advanced_security %}. Para obtener información, consulta la sección "[Términos y condiciones del {% data variables.product.prodname_codeql %} de {% data variables.product.product_name %}](https://securitylab.github.com/tools/codeql/license)" y [CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
-{% else %}
 * El {% data variables.product.prodname_codeql_runner %} se encuentra disponible para los clientes con una licencia de {% data variables.product.prodname_advanced_security %}.
-{% endif %}
 * El {% data variables.product.prodname_codeql_runner %} no debe confundirse con el CLI de {% data variables.product.prodname_codeql %}. El CLI de {% data variables.product.prodname_codeql %}es una interface de línea de comandos que te permite crear bases de datos de {% data variables.product.prodname_codeql %} para la investigación de seguridad y ejecutar consultas de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
 {% endnote %}
 
 ### Descargar el {% data variables.product.prodname_codeql_runner %}
 
-Puedes descargar el {% data variables.product.prodname_codeql_runner %} desde https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. En algunos sistemas operativos, puede que necesites cambiar permisos para el archivo de descarga antes de que lo puedas ejecutar.
+Puedes descargar el {% data variables.product.prodname_codeql_runner %} desde https://github.com/github/codeql-action/releases. En algunos sistemas operativos, puede que necesites cambiar permisos para el archivo de descarga antes de que lo puedas ejecutar.
 
 En Linux:
 
@@ -62,7 +59,7 @@ En Windows, el archivo `codeql-runner-win.exe` habitualmente no necesita que se
 Una vez que descargas el {% data variables.product.prodname_codeql_runner %} y verificas que puede ejecutarse, debes poner el ejecutor disponible para cada servidor de IC que pretendas utilizar para el {% data variables.product.prodname_code_scanning %}. Por ejemplo, podrías configurar cada servidor para que copie el ejecutor desde una ubicación interna y central. Como alternativa, puedes utilizar la API de REST para obtener el ejecutor directamente de {% data variables.product.prodname_dotcom %}, por ejemplo:
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
@@ -73,9 +70,8 @@ Además, cada servidor de IC necesitará también:
 
 Las opciones para proporcionar acceso al paquete de {% data variables.product.prodname_codeql %} son:
 
-1. Permite que los servidores de IC accedan a https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action para que el {% data variables.product.prodname_codeql_runner %} pueda descargar el paquete automáticamente.
-{% if currentVersion == "enterprise-server@2.22" %}
-1. Replica el repositorio `github/codeql-action` en {% data variables.product.product_name %}. A menos de que especifiques el marcador de <nobr>`--codeql-path`</nobr> , el ejecutor verificará automáticamente que el paquete esté en esta ubicación y en {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
+1. Permite que los servidores de IC accedan a https://github.com/github/codeql-action para que el {% data variables.product.prodname_codeql_runner %} pueda descargar el paquete automáticamente.
+1. Replica el repositorio `github/codeql-action` en {% data variables.product.product_name %}. A menos de que especifiques el marcador de <nobr>`--codeql-path`</nobr> , el ejecutor verificará automáticamente que el paquete esté en esta ubicación y en {% data variables.product.prodname_dotcom_the_website %}.
 1. Descarga/extrae manualmente el paquete, almacénalo con otros recursos centrales y utiliza el <nobr>`--codeql-path`</nobr> para especificar la ubicación del paquete en los llamados para inicializar el {% data variables.product.prodname_codeql_runner %}.
 
 ### Llamar al {% data variables.product.prodname_codeql_runner %}
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index 1ef0e060b8..457cf41018 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -1,132 +1,131 @@
 ---
-title: SARIF support for code scanning
-shortTitle: SARIF support
-intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for {% data variables.product.prodname_code_scanning %}. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.'
+title: Soporte de SARIF para escaneo de código
+shortTitle: Soporte de SARIF
+intro: 'Para mostrar los resultados de una herramienta de análisis estático de terceros en tu repositorio en {% data variables.product.prodname_dotcom %}, necesitas que éstos se almacenen en un archivo SARIF que sea compatible con un subconjunto del modelo de JSON para SARIF 2.1.0 para el {% data variables.product.prodname_code_scanning %}. Si utilizas el motor de análisis estático predeterminado de {% data variables.product.prodname_codeql %}, tus resultados se mostrarán automáticamente en tu repositorio de {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
-redirect_from:
-  - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
 versions:
   enterprise-server: '2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
-### About SARIF support
+### Acerca del soporte de SARIF
 
-SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) that defines an output file format. The SARIF standard is used to streamline how static analysis tools share their results. {% data variables.product.prodname_code_scanning_capc %} supports a subset of the SARIF 2.1.0 JSON schema.
+SARIF (Formato de Intercambio de Resultados de Análisis Estático, por sus siglas en inglés) es un [Estándar de OASIS](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) que define un formato de archivo de salida. El estándar SARIF se utiliza para optimizar la manera en el que las herramientas de análisis estático comparten sus resultados. {% data variables.product.prodname_code_scanning_capc %} es compatible con un subconjunto del modelo SARIF 2.1.0 JSON.
 
-To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
+Para cargar un archivo SARIF desde un motor de análisis estático de código desde un tercero, necesitaras asegurarte de que los archivos cargados utilicen la versión SARIF 2.1.0. {% data variables.product.prodname_dotcom %} analizará el archivo SARIF y mostrará las alertas utilizando los resultados en tu repositorio como parte de la experiencia del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". Para obtener más información acerca del modelo SARIF 2.1.0, consulta [`sari-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará cuando cargues el archivo SARIF utilizando {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" o "[Ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
 
-{% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+{% data variables.product.prodname_dotcom %} utiliza propiedades en el archivo SARIF para mostrar alertas. Por ejemplo, la `shortDescription` y `fullDescription` aparecen hasta arriba de una alerta de {% data variables.product.prodname_code_scanning %}. La `location` permite a {% data variables.product.prodname_dotcom %} mostrar anotaciones en tu archivo de código. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)".
 
-If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) repository.
+Si SARIF es nuevo para ti y quieres aprender más, consulta el repositorio [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) de Microsoft.
 
-### Preventing duplicate alerts using fingerprints
+### Prevenir alertas duplicadas utilizando huellas dactilares
 
-Each time the results of a new code scan are uploaded, the results are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the right line of code when files are edited.
+Cada vez que el flujo de trabajo de {{ site.data.variables.product.prodname_actions }} ejecuta un nuevo escaneo de código, los resultados de cada ejecución se procesan y se agregan alertas al repositorio. Para prevenir las alertas duplicadas para el mismo problema, {% data variables.product.prodname_code_scanning %} utiliza huellas dactilares para empatara los resultados a través de diversas ejecuciones para que solo aparezcan una vez en la última ejecución para la rama seleccionada. Esto hace posible empatar las alertas con la línea de código correcta cuando se editan los archivos.
 
-{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation.
+{% data variables.product.prodname_dotcom %} utiliza la propiedad `partialFingerprints` en el estándar OASIS para detectar cuando dos resultados son lógicamente idénticos. Para obtener más información, consulta la sección "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" en la documentación de OASIS.
 
-SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)."
+Los archivos SARIF que crea el {% data variables.product.prodname_codeql_workflow %} o los que utilizan el {% data variables.product.prodname_codeql_runner %} incluyen datos de huellas digitales. Si cargas un archivo SARIF utilizando la acción `upload-sarif` y no se encuentran estos datos, {% data variables.product.prodname_dotcom %} intentará poblar el campo `partialFingerprints` desde los archivos de origen. Para obtener más información acerca de cargar los resultados, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)".
 
-If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)."
+Si cargaste un archivo SARIF sin datos de huella digital utilizando la terminal de la API de `/code-scanning/sarifs`, se procesarán y se mostrarán las alertas del {% data variables.product.prodname_code_scanning %}, pero los usuarios podrían ver alertas duplicadas. Para evitar el ver alertas duplicadas, debes calcular los datos de la huella digital y llenar la propiedad de `partialFingerprints` antes de que cargues el archivo SARIF. Puede que el script que utiliza la acción `upload-sarif` te sea útil como punto de inicio: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. Para obtener más información sobre la API, consulta la sección "[Cargar un análisis como datos de SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)".
 
-### Validating your SARIF file
+### Validar tu archivo SARIF
 
 <!--UI-LINK: When code scanning fails, the error banner shown in the Security > Code scanning alerts view links to this anchor.-->
 
-You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/).
+Puedes verificar si un archivo SARIF es compatible con el {% data variables.product.prodname_code_scanning %} si lo pruebas contra las reglas de ingestión de {% data variables.product.prodname_dotcom %}. Para obtener más información, visita el [Validador de archivos SARIF de Microsoft](https://sarifweb.azurewebsites.net/).
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### Supported SARIF output file properties
+### Propiedades compatibles de archivo de salida SARIF
 
-If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}.
+Si utilizas un motor de análisis de código diferente a {% data variables.product.prodname_codeql %}, puedes revisar las propiedades SARIF compatibles para optimizar cómo aparecerán los resultados de tu análisis en {% data variables.product.prodname_dotcom %}.
 
-Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.product.prodname_code_scanning %} will only use the following supported properties.
+Puedes cargar cualquier archivo de salida SARIF 2.1.0 válido, sin embargo, {% data variables.product.prodname_code_scanning %} utilizará únicamente las siguientes propiedades compatibles.
 
-#### `sarifLog` object
+#### Objeto `sarifLog`
 
-| Name | Description |
-|----|----|
-|  `$schema` | **Required.** The URI of the SARIF JSON schema for version 2.1.0. For example, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. |
-| `version` | **Required.** {% data variables.product.prodname_code_scanning_capc %} only supports SARIF version `2.1.0`.
-| `runs[]` | **Required.** A SARIF file contains an array of one or more runs. Each run represents a single run of an analysis tool. For more information about a `run`, see the [`run` object](#run-object).
+| Nombre    | Descripción                                                                                                                                                                                                                                            |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `$schema` | **Requerido.** la URI del modelo SARIF JSON para la versión 2.1.0. Por ejemplo, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`.                                                                      |
+| `version` | **Requerido.**{% data variables.product.prodname_code_scanning_capc %} solo es compatible con la versión `2.1.0` de SARIF.                                                                                                                           |
+| `runs[]`  | **Requerido.** Un archivo SARIF contiene un arreglo de una o más ejecuciones. Cada ejecución representa una sola ejecución de una herramienta de análisis. Para obtener más información acerca de una `run`, consulta el [ objeto `run`](#run-object). |
 
-#### `run` object
+#### Objeto `run`
 
-{% data variables.product.prodname_code_scanning_capc %} uses the `run` object to filter results by tool and provide information about the source of a result. The `run` object contains the `tool.driver` tool component object, which contains information about the tool that generated the results. Each `run` can only have results for one analysis tool.
+{% data variables.product.prodname_code_scanning_capc %} utiliza el objeto `run` para filtrar los resultados por herramienta y proporcionar información acerca del origen de un resultado. El objeto `run` contienen el objeto componente de herramienta `tool.driver`, el cual contiene información acerca de la herramienta que generó el resultado. Cada `run` puede tener únicamente resultados para la herramienta de análisis.
 
-| Name | Description |
-|----|----|
-| `tool.driver.name` | **Required.** The name of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the name on {% data variables.product.prodname_dotcom %} to allow you to filter results by tool. |
-| `tool.driver.version` | **Optional.** The version of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. |
-| `tool.driver.semanticVersion` | **Optional.** The version of the analysis tool, specified by the Semantic Versioning 2.0 format. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. For more information, see "[Semantic Versioning 2.0.0](https://semver.org/)" in the Semantic Versioning documentation. |
-| `tool.driver.rules[]` | **Required.** An array of `reportingDescriptor` objects that represent rules. The analysis tool uses rules to find problems in the code being analyzed. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). |
-| `results[]` | **Required.** The results of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the results on {% data variables.product.prodname_dotcom %}. For more information, see the [`result` object](#result-object).
+| Nombre                        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `tool.driver.name`            | **Requerido.** El nombre de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre en {% data variables.product.prodname_dotcom %} para permitirte filtrar los resultados por herramienta.                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `tool.driver.version`         | **Opcional.** La versión de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`.                                                                                                                                                                                                          |
+| `tool.driver.semanticVersion` | **Opcional.** La versión de la herramienta de análisis, especificada por el formato de Semantic Versioning 2.0. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. Para obtener más información, consulta la sección "[Semantic Versioning 2.0.0](https://semver.org/)" en la documentación de Semantic Versioning. |
+| `tool.driver.rules[]`         | **Requerido.** Un arreglo de objetos `reportingDescriptor` que representen reglas. La herramienta de análisis utiliza reglas para encontrar problemas en el código que se analiza. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object).                                                                                                                                                                                                                                                                                                                                                                        |
+| `results[]`                   | **Requerido.** Los resultados de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra los resultados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta el [objeto `result`](#result-object).                                                                                                                                                                                                                                                                                                                                                                                   |
 
-#### `reportingDescriptor` object
+#### Objeto `reportingDescriptor`
 
-| Name | Description |
-|----|----|
-| `id` |  **Required.** A unique identifier for the rule. The `id` is referenced from other parts of the SARIF file and may be used by {% data variables.product.prodname_code_scanning %} to display URLs on {% data variables.product.prodname_dotcom %}. |
-| `name` | **Optional.** The name of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the name to allow results to be filtered by rule on {% data variables.product.prodname_dotcom %}. |
-| `shortDescription.text` | **Required.** A concise description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the short description on {% data variables.product.prodname_dotcom %} next to the associated results.
-| `fullDescription.text` | **Required.** A description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the full description on {% data variables.product.prodname_dotcom %} next to the associated results. The max number of characters is limited to 1000.
-| `defaultConfiguration.level` | **Optional.** Default severity level of the rule. {% data variables.product.prodname_code_scanning_capc %} uses severity levels to help you understand how critical the result is for a given rule. This value can be overridden by the `level` attribute in the `result` object. For more information, see the [`result` object](#result-object). Default: `warning`.
-| `help.text` | **Required.** Documentation for the rule using text format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results.
-| `help.markdown` | **Recommended.** Documentation for the rule using Markdown format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. When `help.markdown` is available, it is displayed instead of `help.text`.
-| `properties.tags[]` | **Optional.** An array of strings. {% data variables.product.prodname_code_scanning_capc %} uses `tags` to allow you to filter results on {% data variables.product.prodname_dotcom %}. For example, it is possible to filter to all results that have the tag `security`.
-| `properties.precision` | **Recommended.** A string that indicates how often the results indicated by this rule are true. For example, if a rule has a known high false-positive rate, the precision should be `low`. {% data variables.product.prodname_code_scanning_capc %} orders results by precision on {% data variables.product.prodname_dotcom %} so that the results with the highest `level`, and highest `precision` are shown first. Can be one of: `very-high`, `high`, `medium`, or `low`.
+| Nombre                       | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                         | **Requerido.** Un identificador único para la regla. El `id` se referencia de otras partes del archivo SARIF y {% data variables.product.prodname_code_scanning %} puede utilizarlo para mostrar las URL en {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                              |
+| `name (nombre)`              | **Opcional.** El nombre de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre para permitir que se filtren los resultados por regla en {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                                                               |
+| `shortDescription.text`      | **Requerido** Una descripción breve de la acción. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción corta en {% data variables.product.prodname_dotcom %} junto a los resultados asociados.                                                                                                                                                                                                                                                                                                            |
+| `fullDescription.text`       | **Requerido** Una descripción de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción completa en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. La cantidad máxma de caracteres se limita a 1000.                                                                                                                                                                                                                                                              |
+| `defaultConfiguration.level` | **Opcional.** Nivel de severidad predeterminado de la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza niveles de severidad para ayudarte a entender qué tan crítico es el resultado de una regla. El atributo `level` en el objeto `result` anular este valor. Para obtener más información, consulta el [objeto `result`](#result-object). Predeterminado: `warning`.                                                                                                                                         |
+| `help.text`                  | **Requerido.** Documentación para la regla utilizando el formato de texto. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados.                                                                                                                                                                                                                                                                                                                              |
+| `help.markdown`              | **Recomendado.** Documentación para la regla utilizando el formato Markdown. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. Cuando `help.markdown` está disponible, se muestra en vez de `help.text`.                                                                                                                                                                                                                                                  |
+| `properties.tags[]`          | **Opcional.** Un arreglo de secuencias. {% data variables.product.prodname_code_scanning_capc %} utiliza `tags` para permitirte filtrar los resultados en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes filtrar todos los resultados que tengan la etiqueta `security`.                                                                                                                                                                                                                                            |
+| `properties.precision`       | **Recomendado.** una secuencia que indica qué tan frecuentemente son verdaderos los resultados que indica esta regla. Por ejemplo, si una regla tiene una tasa alta de falsos positivos, la precisión debería ser `low`. {% data variables.product.prodname_code_scanning_capc %} ordena los resultados de acuerdo con su precisión en {% data variables.product.prodname_dotcom %} para que aquellos con el `level` y la `precision` más altos se muestren primero. Puede ser uno de entre: `very-high`, `high`, `medium`, o `low`. |
 
 #### `result` object
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-| Name | Description |
-|----|----|
-| `ruleId`| **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}.
-| `ruleIndex`| **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object).
-| `rule`| **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object).
-| `level`| **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}.
-| `message.text`| **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited.
-| `locations[]`| **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored.
-| `partialFingerprints`| **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)."  **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`.
-| `codeFlows[].threadFlows[].locations[]`| **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object).
-| `relatedLocations[]`| A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object).
-| `suppressions[].state`| **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}.
+| Nombre                                  | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ruleId`                                | **Opcional.** El identificador único de la regla (`reportingDescriptor.id`). Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} utiliza el identificador de reglas para filtrar los resultados por regla en {% data variables.product.prodname_dotcom %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `ruleIndex`                             | **Opcional.** El índice de la regla asociada (`reportingDescriptor` object) en el arreglo de `rules` del componente de la herramienta. Para obtener más información, consulta el [objeto `run`](#run-object).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `rule`                                  | **Opcional.** Una referencia que se utiliza para ubicar la regla (descriptor de reporte) para este resultado. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `level`                                 | **Opcional.** La severidad del resultado. Este nivel invalida la severidad predeterminada que se define en la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza el nivel para filtrar los resultados en {% data variables.product.prodname_dotcom %} por severidad.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `message.text`                          | **Requerido.** Un mensaje que describe el resultado. {% data variables.product.prodname_code_scanning_capc %} muestra el texto del mensaje como el título del resultado. Se mostrará únicamente la primera oración del mensaje cuando el espacio visible esté limitado.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `locations[]`                           | **Requerido.** El conjunto de ubicaciones donde se detectó el resultado, con un máximo de 10. Sólo se deberá incluir una ubicación a menos de que el problema solo pueda corregirse realizando un cambio en cada ubicación especificada. **Nota:** Se requiere por lo menos una ubicación para que {% data variables.product.prodname_code_scanning %} muestre el resultado. {% data variables.product.prodname_code_scanning_capc %} utilizará esta propiedad para decidir qué archivo anotar con el resultado. Únicamente si se utiliza el primer valor de este arreglo. Se ignorará al resto de los otros valores.                                                                                                                                                                                                                                                  |
+| `partialFingerprints`                   | **Requerido.** Un conjunto de secuencias utilizadas para rastrear la identidad única del resultado. {% data variables.product.prodname_code_scanning_capc %} utiliza `partialFingerprints` para identificar con exactitud qué resultados son los mismos a través de las confirmaciones y ramas. {% data variables.product.prodname_code_scanning_capc %} intentará utilizar `partialFingerprints` si es que existe. Si estás cargando un archivo SARIF de terceros con el `upload-action`, la acción creará un `partialFingerprints` para ti cuando no se incluya en el archivo SARIF. Para obtener más información, consulta "[Prevenir alertas duplicadas utilizando huellas dactilares](#preventing-duplicate-alerts-using-fingerprints)".  **Nota:** {% data variables.product.prodname_code_scanning_capc %} utilizará únicamente el `primaryLocationLineHash`. |
+| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Un arreglo de objetos de `location` para un objeto de `threadFlow`, el cual describe el progreso de un programa a través de un hilo de ejecución. Un objeto de `codeFlow` describe un patrón de ejecución de código que se utiliza para detectar un resultado. Si se proporcionan flujos de código, {% data variables.product.prodname_code_scanning %} los expandirá en {% data variables.product.prodname_dotcom %} para el resultado relevante. Para obtener más información, consulta el [objeto `location`](#location-object).                                                                                                                                                                                                                                                                                                                        |
+| `relatedLocations[]`                    | Un conjunto de ubicaciones relevantes para el resultado. {% data variables.product.prodname_code_scanning_capc %} vinculará las ubicaciones cuando se incorporen en el mensaje de resultado. Para obtener más información, consulta el [objeto `location`](#location-object).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 
-#### `location` object
+#### Objeto `location`
 
-A location within a programming artifact, such as a file in the repository or a file that was generated during a build.
+Una ubicación dentro de un artefacto de programación, tal como un archivo en el repositorio o un archivo que se generó durante una compilación.
 
-| Name | Description |
-|----|----|
-| `location.id` | **Optional.** A unique identifier that distinguishes this location from all other locations within a single result object.
-| `location.physicalLocation` | **Required.** Identifies the artifact and region. For more information, see the [`physicalLocation`](#physicallocation-object).
-| `location.message.text` | **Optional.** A message relevant to the location.
+| Nombre                      | Descripción                                                                                                                                   |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `location.id`               | **Opcional.** Un identificador único que distingue esta ubicación del resto de las ubicaciones dentro de un objeto de un único resultado.     |
+| `location.physicalLocation` | **requerido.** Identifica el artefacto y la región. Para obtener más información, consulta la [`physicalLocation`](#physicallocation-object). |
+| `location.message.text`     | **Opcional.** Un mensaje relevante para la ubicación.                                                                                         |
 
-#### `physicalLocation` object
+#### Objeto `physicalLocation`
 
-| Name | Description |
-|----|----|
-| `artifactLocation.uri`| **Required.** A URI indicating the location of an artifact, usually a file either in the repository or generated during a build. If the URI is relative, it should be relative to the root of the {% data variables.product.prodname_dotcom %} repository being analyzed. For example, main.js or src/script.js are relative to the root of the repository. If the URI is absolute, {% data variables.product.prodname_code_scanning %} can use the URI to checkout the artifact and match up files in the repository. For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`.
-| `region.startLine` | **Required.** The line number of the first character in the region.
-| `region.startColumn` | **Required.** The column number of the first character in the region.
-| `region.endLine` | **Required.** The line number of the last character in the region.
-| `region.endColumn` | **Required.** The column number of the character following the end of the region.
+| Nombre                 | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `artifactLocation.uri` | **Requerido.** Un URI que indica la ubicación de un artefacto, a menudo un archivo ya sea en el repositorio o generado durante una compilación. Si el URI es relativo, deberá ser relativo a la raíz del repositorio de {% data variables.product.prodname_dotcom %} que se está analizando. Por ejemplo, main.js o src/script.js son relativos a la raíz del repositorio. Si la URI es absoluta, {% data variables.product.prodname_code_scanning %} puede utilizarla para revisar el artefacto y empatar archivos en el repositorio. Por ejemplo, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. |
+| `region.startLine`     | **Requerido.** El número del línea para el primer caracter en la región.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `region.startColumn`   | **Requerido.** El número de columna del primer caracter en la región.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `region.endLine`       | **Requerido.** El número de línea de el último caracter en la región.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `region.endColumn`     | **Requerido.** El número de columna del caracter que sigue al final de la región.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
-### SARIF output file examples
+### Ejemplos de archivo de salida SARIF
 
-These example SARIF output files show supported properties and example values.
+Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles y los valores de ejemplo.
 
-#### Example with minimum required properties
+#### Ejemplo con las propiedades mínimas requeridas
 
-This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties or don't include values, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}.
+Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedades mínimas requeridas para que los resultados de {% data variables.product.prodname_code_scanning %} funcionen como se espera. Si eliminas cualquier propiedad u omites valores, estos datos no se mostrarán correctamente ni se sincronizarán en {% data variables.product.prodname_dotcom %}.
 
 
 ```json
@@ -175,9 +174,9 @@ This SARIF output file has example values to show the minimum required propertie
 }
 ```
 
-#### Example showing all supported SARIF properties
+#### Ejemplo que muestra todas las propiedades compatibles con SARIF
 
-This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}.
+Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}.
 
 ```json
 {
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index ad9ad53ae2..46899e1f9d 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -10,13 +10,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Acerca de los resultados del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios
 
 En los repositorios donde se configura el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambios, éste verificará el código en dicha solicitud. Predeterminadamente, esto se limita a solicitudes de cambios que apuntan a la rama predeterminada, pero puedes cambiar esta configuración dentro de {% data variables.product.prodname_actions %} o en un sistema de IC/EC de terceros. Si el fusionar los cambios puede introducir alertas nuevas de {% data variables.product.prodname_code_scanning %} a la rama destino, éstas se reportarán como resultados de verificación en la solicitud de cambios. Las alertas también se muestran como anotaciones en la pestaña de **Archivos que cambiaron** de la solicitud de cambios. Si tienes permisos de escritura para el repositorio, puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} existente en la pestaña de **Seguridad**. Para obtener más información sobre las alertas de los repositorios, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)".
 
-Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. Si tu solicitud de cambios apunta a una rama protegida que utiliza el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces debes ya sea arreglar o {% if currentVersion == "enterprise-server@2.22" %}cerrar{% else %}descartar{% endif %} todas las alertas de error antes de que se pueda fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
+Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. Si tu solicitud de cambios apunta a una rama protegida que utiliza el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces debes ya sea arreglar o cerrar todas las alertas de error antes de que se pueda fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
 
 ![Verificación fallida del {% data variables.product.prodname_code_scanning %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -40,28 +42,10 @@ En la vista detallada de una alerta, algunas herramientas del {% data variables.
 
 ![Descripción de alerta y enlace para mostrar más información](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolver{% else %}Arreglar{% endif %} una alerta en tu solicitud de cambios
+### Resolver una alerta en tu solicitud de extracción
 
 Cualquiera con acceso de subida a una solicitud de cambios puede arreglar una alerta del {% data variables.product.prodname_code_scanning %}, la cual se identifique en dicha solicitud. Si confirmas cambios en la solicitud de extracción, esto activará una ejecución nueva de las verificaciones de dicha solicitud. Si tus cambios arreglan el problema, la alerta se cierra y la anotación se elimina.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 Si no crees que alguna alerta deba arreglarse, los usuarios con permisos de escritura pueden cerrarla manualmente. {% data reusables.code-scanning.close-alert-examples %} El botón de **Cerrar** se encuentra disponible en las anotaciones y en la vista de alertas si tienes permisos de escritura en el repositorio.
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### Descartar una alerta en tu solicitud de cambios
-
-Una forma alterna de cerrar una alerta es descartarla. Puedes descartar una alerta si no crees que necesite arreglarse. {% data reusables.code-scanning.close-alert-examples %} Si tienes permisos de escritura en el repositorio, el botón de **Descartar** está disponible en las anotaciones de código y en el resumen de alertas. Cuando das clic en **Descartar** se te pedirá elegir una razón para cerrar la alerta.
-
-![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-Para obtener más información acerca de descartar alertas, consulta la sección "[Administrar alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)".
-
-{% endif %}
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index 89058fbd2d..88d1ddff9a 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index 9203c89aaa..5c2a37b0f4 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -28,7 +30,10 @@ Si una compilación automática de código para un lenguaje compilado dentro de
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -113,25 +118,13 @@ Si divides tu análisis en varios flujos de trabajo como se describió anteriorm
 
 Si tu análisis aún es muy lento como para ejecutarse durante eventos de `push` o de `pull_request`, entonces tal vez quieras activar el análisis únicamente en el evento de `schedule`. Para obtener más información, consulta la sección "[Eventos](/actions/learn-github-actions/introduction-to-github-actions#events)".
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Los resultados difieren de acuerdo con la plataforma de análisis
-
-Si estás analizando código escrito en Python, podrías ver resultados diferentes dependiendo de si ejecutas el {% data variables.product.prodname_codeql_workflow %} en Linux, macOS o Windows.
-
-En los ejecutores hospedados en GitHub que utilizan Linux, el {% data variables.product.prodname_codeql_workflow %} intenta instalar y analizar las dependencias de Python, lo cual podría llevar a más resultados. Para inhabilitar la auto instalación, agrega `setup-python-dependencies: false` al paso de "Initialize CodeQL" en el flujo de trabajo. Para obtener más información acerca de la configuración del análisis para las dependencias de Python, consulta la sección "[Analizar las dependencias de Python](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)".
-
-{% endif %}
-
 ### Error: "Error de servidor"
 
 Si la ejecución de un flujo de trabajo para {% data variables.product.prodname_code_scanning %} falla debido a un error de servidor, trata de ejecutar el flujo de trabajo nuevamente. Si el problema persiste, contaca a {% data variables.contact.contact_support %}.
 
 ### Error: "Out of disk" o "Out of memory"
-En proyectos muy grandes,
 
-{% data variables.product.prodname_codeql %} podría quedarse sin memoria de disco en el ejecutor.
-{% if currentVersion == "free-pro-team@latest" %}Si te encuentras con este problema en un ejecutor de {% data variables.product.prodname_actions %}, contacta a {% data variables.contact.contact_support %} para que podamos investigar el problema.
-{% else %}Si llegas a tener este problema, intenta incrementar la memoria en el ejecutor.{% endif %}
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the hosted {% data variables.product.prodname_actions %} runner. Si te encuetnras con este problema, trata de incrementar la memoria del ejecutor.
 
 ### Warning: "git checkout HEAD^2 is no longer necessary"
 
@@ -146,29 +139,29 @@ commit for best results.
 Puedes arreglar esto si eliminas las siguientes líneas del flujo de trabajo de {% data variables.product.prodname_codeql %}. Estas líneas se incluyeron en la sección de `steps` del job `Analyze` en las versiones iniciales del flujo de trabajo de {% data variables.product.prodname_codeql %}.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 La sección revisada de `steps` en el flujo de trabajo se deberá ver así:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 Para obtener más información sobre la edición del archivo de flujo de trabajo de {% data variables.product.prodname_codeql %}, consulta la sección "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)".
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index 659a7746ea..d1332ff721 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -19,7 +21,7 @@ topics:
 
 Puedes generar archivos SARIF utilizando muchas herramientas de prueba de seguridad para análisis estático, incluyendo a {% data variables.product.prodname_codeql %}. Para cargar resultados desde herramientas de terceros debes utilizar el Formato de Intercambio para Resultados de Análisis Estático (SARIF) 2.1.0. Para obtener más información, consulta la sección "[Soporte de SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)".
 
-Puedes cargar los resultados utilizando las {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (disponibles si tu organización está participando en el programa del beta){% endif %}, la API del {% data variables.product.prodname_code_scanning %}, o el {% data variables.product.prodname_codeql_runner %}. El mejor método de carga dependerá de cómo generas el archivo SARIF, por ejemplo, si utilizas:
+Puedes cargar los resultados utilizando {% data variables.product.prodname_actions %} (que está disponible si tu organización participa en el programa beta), la API del {% data variables.product.prodname_code_scanning %} o el {% data variables.product.prodname_codeql_runner %}. El mejor método de carga dependerá de cómo generas el archivo SARIF, por ejemplo, si utilizas:
 
 - {% data variables.product.prodname_actions %} para ejecutar la acción de {% data variables.product.prodname_codeql %}, no hay que hacer nada más. La acción de {% data variables.product.prodname_codeql %} carga el archivo de SARIF automáticamente cuando completa el análisis.
 - "[Administrar una ejecución de flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)"
@@ -58,20 +60,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Ejemplo de flujo de trabajo que ejecuta la herramienta de análisis ESLint
@@ -82,7 +86,7 @@ Este ejemplo de flujo de trabajo se ejecuta cada que las confirmaciones se carga
 
 El flujo de trabajo muestra un ejemplo de ejecución de la herramienta de análisis estático ESLint como un paso en un flujo de trabajo. El paso `Run ESLint` ejecuta la herramienta ESLint y da como salida el archivo `results.sarif`. El flujo de trabajo entonces carga el archivo `results.sarif` a {% data variables.product.prodname_dotcom %} utilizando la acción `upload-sarif`. Para obtener más información acerca de cómo crear un archivo de flujo de trabajo, consulta la sección "[Introducción a Github Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -90,23 +94,26 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Leer más
diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index 02ac3621ca..04aa1aecfd 100644
--- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/es-ES/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/es-ES/content/github/getting-started-with-github/about-git-subtree-merges.md
index 7631c264f2..3d3ab1f6f1 100644
--- a/translations/es-ES/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/es-ES/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 Habitualmente, una fusión de subárbol se usa para contener un repositorio dentro de otro repositorio. El "subrepositorio" se almacena en una carpeta del repositorio principal.
 
 La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Haremos lo siguiente:
diff --git a/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md
index c102ceeedf..3db30878d9 100644
--- a/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md
+++ b/translations/es-ES/content/github/getting-started-with-github/about-github-advanced-security.md
@@ -38,7 +38,7 @@ El administrador de sitio debe habilitar
 la {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de que puedas utilizar estas características. Para obtener más información, consulta la sección "[Configurar las características de la Seguridad Avanzada](/admin/configuration/configuring-advanced-security-features)".
 {% endif %}
 
-Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas características a nivel de organización o de repositorio. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas características a nivel de organización o de repositorio. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".
 
 {% endif %}
 
@@ -47,7 +47,7 @@ Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas
 
 Para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}, estas características se encuentran activas permanentemente y solo se pueden inhabilitar si cambias la visibilidad del proyecto para que el código ya no sea público.
 
-En el caso de otros repositorios, una vez que tengas una licencia para tu cuenta empresarial, puedes habilitar e inhabilitar estas características a nivel de repositorio u organización. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+En el caso de otros repositorios, una vez que tengas una licencia para tu cuenta empresarial, puedes habilitar e inhabilitar estas características a nivel de repositorio u organización. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración y análisis de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
 
 {% endif %}
 
diff --git a/translations/es-ES/content/github/getting-started-with-github/be-social.md b/translations/es-ES/content/github/getting-started-with-github/be-social.md
index a87157b8e7..16d9fa34f9 100644
--- a/translations/es-ES/content/github/getting-started-with-github/be-social.md
+++ b/translations/es-ES/content/github/getting-started-with-github/be-social.md
@@ -38,6 +38,10 @@ Haz clic en **Watch** (Ver) en la parte superior del repositorio que desas ver.
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### Hacer un poco más
 
 #### Crear solicitudes de extracción
@@ -54,7 +58,7 @@ Al colaborar en un repositorio, usa las propuestas para realizar el seguimiento
 
 #### Participación en las organizaciones
 
-Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y administradores pueden establecer equipos con permisos especiales, tener un perfil de organización pública y realizar el seguimiento de la actividad dentro de la organización. Para obtener más información, consulta "[Acerca de las organizaciones](/articles/about-organizations)".
+Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y administradores pueden establecer equipos con permisos especiales, tener un perfil de organización pública y realizar el seguimiento de la actividad dentro de la organización. For more information, see "[About organizations](/articles/about-organizations/)."
 
 ![Desplegable de contexto para cambiar cuenta](/assets/images/help/overview/dashboard-contextswitcher.png)
 
@@ -68,8 +72,8 @@ Ahora estás conectado con la comunidad de {% data variables.product.product_nam
 
 ![Marcar un proyecto con una estrella](/assets/images/help/stars/star-a-project.png)
 
-- [Configurar Git](/articles/set-up-git)
-- [Crear un repositorio](/articles/create-a-repo)
-- [Bifurcar un repositorio](/articles/fork-a-repo)
+- "[Configurar Git](/articles/set-up-git)"
+- "[Crear un repositorio](/articles/create-a-repo)"
+- "[Bifurcar un repositorio](/articles/fork-a-repo)"
 - **Ser social**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/es-ES/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/es-ES/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index e47770a9a5..8358df628e 100644
--- a/translations/es-ES/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/es-ES/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 Cada vez que presionas <kbd>Enter</kbd> en tu teclado, insertas un caracter invisible denominado fin de línea. Esto se maneja de forma diferente en los diferentes sistemas operativos.
 
-Cuando colaboras en proyectos con Git y {% data variables.product.product_name %}, Git puede producir resultados inesperados si, por ejemplo, trabajas en una máquina Windows y tu colaborador hizo un cambio desde OS X.
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 Puedes configurar Git para que maneje los fines de línea automáticamente y así puedas colaborar eficazmente con las personas que utilizan otros sistemas operativos.
 
@@ -25,11 +25,11 @@ El comando `git config core.autocrlf` se usa para cambiar el modo en que Git man
 
 {% mac %}
 
-En OS X, simplemente escribes `input` en la configuración. Por ejemplo:
+On macOS, you simply pass `input` to the configuration. Por ejemplo:
 
 ```shell
 $ git config --global core.autocrlf input
-# Configure Git to ensure line endings in files you checkout are correct for OS X
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md b/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md
index 7f5403ec96..83c490184d 100644
--- a/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/es-ES/content/github/getting-started-with-github/create-a-repo.md
@@ -15,6 +15,8 @@ topics:
   - Accounts
 ---
 
+### Crear un repositorio
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 Puedes almacenar distintos proyectos en los repositorios de {% data variables.product.product_name %}, incluso proyectos de código abierto. Con [proyectos de código abierto](http://opensource.org/about), puedes compartir el código para hacer que el software funcione mejor y sea más confiable.
@@ -29,7 +31,7 @@ Puedes almacenar varios proyectos en los repositorios de {% data variables.produ
 
 {% note %}
 
-**Nota:** Puedes crear repositorios públicos para un proyecto de código abierto. Cuando crees un repositorio público, asegúrate de incluir un [archivo de licencia](http://choosealicense.com/) que determine cómo deseas que se comparta tu proyecto con otros usuarios. {% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %}
+**Nota:** Puedes crear repositorios públicos para un proyecto de código abierto. Cuando crees un repositorio público, asegúrate de incluir un [archivo de licencia](https://choosealicense.com/) que determine cómo deseas que se comparta tu proyecto con otros usuarios. {% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md b/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md
index 4b55a32135..aa8d232918 100644
--- a/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/es-ES/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### Acerca de las bifurcaciones
+
 Casi siempre las bifurcaciones se usan para proponer cambios al proyecto de otra persona o para usar el proyecto de otra persona como inicio de tu propia idea.
 
 #### Proponer cambios para el proyecto de otra persona
@@ -34,7 +36,7 @@ Para obtener más información acerca de aplicar los principios de código abier
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-Cuando creas tu repositorio público desde una ramificación del proyecto de alguien más, asegúrate de incluir el archivo de licencia que determine cómo quieres que se comparta tu proyecto con los demás. Para obtener más información, consulta la sección "[Elegir una licencia de código abierto](http://choosealicense.com/)" en choosealicense.com.
+Cuando creas tu repositorio público desde una ramificación del proyecto de alguien más, asegúrate de incluir el archivo de licencia que determine cómo quieres que se comparta tu proyecto con los demás. Para obtener más información, consulta la sección "[Elegir una licencia de código abierto](https://choosealicense.com/)" en choosealicense.com.
 
 {% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %}
 
@@ -154,5 +156,6 @@ Ahora ya has bifurcado un repositorio, has practicado la clonación de tu bifurc
 
 - "[Configurar Git](/articles/set-up-git)"
 - "[Crear un repositorio](/articles/create-a-repo)"
+- **Bifurcar un repositorio**
 - "[Socializar](/articles/be-social)"
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/es-ES/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/es-ES/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index deea9803c2..e9fc56c2f0 100644
--- a/translations/es-ES/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/es-ES/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 Estos comandos son muy útiles cuando interactúas con [un repositorio remoto](/github/getting-started-with-github/about-remote-repositories). `clone` y `fetch` descargan código remoto de la URL de un repositorio remoto en tu computadora local, `merge` se usa para fusionar el trabajo de diferentes personas con el tuyo, y `pull` es una combinación de `fetch` y `merge`.
 
 ### Clonar un repositorio
diff --git a/translations/es-ES/content/github/getting-started-with-github/git-workflows.md b/translations/es-ES/content/github/getting-started-with-github/git-workflows.md
index d8226e18c9..4a02820424 100644
--- a/translations/es-ES/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/es-ES/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-Puedes adoptar el método de flujo de {% data variables.product.prodname_dotcom %} para estandarizar como funciona tu equipo y como colabora con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Flujo de GitHub](/github/collaborating-with-issues-and-pull-requests/github-flow)" y " [Entender el flujo de GitHub](http://guides.github.com/overviews/flow/)" en las Guías de {% data variables.product.prodname_dotcom %}.
+Puedes adoptar el método de flujo de {% data variables.product.prodname_dotcom %} para estandarizar como funciona tu equipo y como colabora con {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/es-ES/content/github/getting-started-with-github/github-flow.md b/translations/es-ES/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..08dd2348fd
--- /dev/null
+++ b/translations/es-ES/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: Flujo de GitHub
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### Introducción
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### Prerrequisitos
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)".
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### Crear una solicitud de extracción
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. Para obtener más información, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request)".
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/github/collaborating-with-issues-and-pull-requests/about-status-checks)".
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. Tu solicitud de extracción se actualizará de manera automática.
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)".
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. Para obtener más información, consulta "[Abordar conflictos de fusión](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)."
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)".
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. Para obtener más información, consulta la sección "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md b/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md
index fcbb67ff6d..3bc2fcb57c 100644
--- a/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/es-ES/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ Puedes ingresar simultáneamente a la versión móvil con una cuenta de usuario
 
 Debes instalar {% data variables.product.prodname_mobile %} 1.4 o posterior en tu dispositivo para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}.
 
-Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. Para obtener más información, consulta las secciones "[Notas de lanzamiento](/enterprise-server/admin/release-notes)" y "[Administrar {% data variables.product.prodname_mobile %} para tu empresa](/admin/configuration/managing-github-for-mobile-for-your-enterprise)".
+Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 Durante el beta para {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, debes estar firmado con una cuenta de usuario en {% data variables.product.prodname_dotcom_the_website %}.
 
diff --git a/translations/es-ES/content/github/getting-started-with-github/github-language-support.md b/translations/es-ES/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/es-ES/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/es-ES/content/github/getting-started-with-github/githubs-products.md b/translations/es-ES/content/github/getting-started-with-github/githubs-products.md
index fab3729f0f..810a3083d6 100644
--- a/translations/es-ES/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/es-ES/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 {% data variables.product.prodname_dotcom %} ofrece productos gratuitos y pagos. Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %}
 
 ### {% data variables.product.prodname_free_user %} for user accounts
@@ -99,14 +101,3 @@ Adicionalmente a las características disponibles con {% data variables.product.
 Puedes configurar una prueba para evaluar {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}</a>".
 
 Para obtener más información acerca de hospedar tu propia instancia de [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contacta a {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-{% data variables.product.prodname_ghe_one %} incluye [{% data variables.product.prodname_enterprise %}](#github-enterprise), mas:
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)".{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". {% endif %}
-- [{% data variables.product.prodname_learning %} para organizaciones](https://lab.github.com/organizations)
-
-Para obtener más información sobre cómo registrarse para {% data variables.product.prodname_ghe_one %}, contacta a {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/es-ES/content/github/getting-started-with-github/index.md b/translations/es-ES/content/github/getting-started-with-github/index.md
index db8699df4e..2bdbebfd2d 100644
--- a/translations/es-ES/content/github/getting-started-with-github/index.md
+++ b/translations/es-ES/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md
index 6519e45d1a..e2afff54c1 100644
--- a/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md
+++ b/translations/es-ES/content/github/getting-started-with-github/keyboard-shortcuts.md
@@ -36,12 +36,16 @@ A continuación aparece una lista de algunos de los atajos del teclado disponibl
 | <kbd>g</kbd> <kbd>p</kbd> | Dirige a la pestaña **Pull requests** (Solicitudes de extracción). Para obtener más información, consulta la sección "[Acerca de las solicitudes de cambios](/articles/about-pull-requests)".{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | <kbd>g</kbd> <kbd>a</kbd> | Ve a la pestaña de **Acciones**. Para obtener más información, consulta la sección "[Acerca de las acciones](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %}
 | <kbd>g</kbd> <kbd>b</kbd> | Dirige a la pestaña **Projects** (Proyectos). Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)."                                                                                                                                    |
-| <kbd>g</kbd> <kbd>w</kbd> | Dirige a la pestaña **Wiki**. Para obtener más información, consulta "[Acerca de las wikis](/communities/documenting-your-project-with-wikis/about-wikis)".                                                                                                                                      |
+| <kbd>g</kbd> <kbd>w</kbd> | Dirige a la pestaña **Wiki**. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ### Edición del código fuente
 
 | Atajo del teclado                                                 | Descripción                                                                                                  |
 | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| <kbd>control b</kbd> o <kbd>comando b</kbd>                       | Inserta el formato Markdown para el texto en negrita                                                         |
+| <kbd>control i</kbd> o <kbd>comando i</kbd>                       | Inserta el formato Markdown para el texto en cursiva                                                         |
+| <kbd>control k</kbd> o <kbd>comando k</kbd>                       | Inserta el formato Markdown para crear un enlace                                                             |
 | <kbd>e</kbd>                                                      | Abre el archivo de código fuente en la pestaña **Editar archivo**                                            |
 | <kbd>control f</kbd> o <kbd>comando f</kbd>                       | Comienza la búsqueda en el editor de archivos                                                                |
 | <kbd>control g</kbd> o <kbd>comando g</kbd>                       | Busca el siguiente                                                                                           |
@@ -52,7 +56,7 @@ A continuación aparece una lista de algunos de los atajos del teclado disponibl
 | <kbd>control z</kbd> o <kbd>comando z</kbd>                       | Deshace                                                                                                      |
 | <kbd>control y</kbd> o <kbd>comando y</kbd>                       | Rehace                                                                                                       |
 | <kbd>cmd + shift + p</kbd>                                        | Alterna entre las pestañas **Edit file** (Editar comentario) y **Preview changes** (Vista previa de cambios) |
-| <kbd>control s</kbd> or <kbd>command s</kbd>                      | Write a commit message                                                                                       |
+| <kbd>control s</kbd> o <kbd>command s</kbd>                       | Escribir un mensaje de confirmación                                                                          |
 
 Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror](https://codemirror.net/doc/manual.html#commands).
 
diff --git a/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md b/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md
index 82c2bd0e1b..87e4f5725b 100644
--- a/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/es-ES/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: Obtener información sobre GitHub
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/es-ES/content/github/getting-started-with-github/set-up-git.md b/translations/es-ES/content/github/getting-started-with-github/set-up-git.md
index 709817c151..bf4145edf4 100644
--- a/translations/es-ES/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/es-ES/content/github/getting-started-with-github/set-up-git.md
@@ -22,6 +22,8 @@ topics:
   - Accounts
 ---
 
+### Utilizar GitHub
+
 Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} También puedes instalar {% data variables.product.prodname_cli %} para utilizar {% data variables.product.product_name %} desde la línea de comandos. Para obtener más información sobre {% data variables.product.prodname_cli %}, consulta la [documentación de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/).{% endif %}
 
 Si deseas trabajar con Git de forma local, pero no deseas utilizar la línea de comando, puedes descargar e instalar en su lugar el cliente [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}).  Para obtener más información, consulta la sección "[Instalar y configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)".
diff --git a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index a65516996a..6cfe8e0c17 100644
--- a/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/es-ES/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ Si no compras {% data variables.product.prodname_enterprise %} o {% data variabl
 
 El bajar de categoría a {% data variables.product.prodname_free_team %} en organizaciones también inhabilita cualquier configuración de SAML durante el periodo de prueba. Una vez que compras {% data variables.product.prodname_enterprise %} o {% data variables.product.prodname_team %}, tus parámetros de SAML serán activados nuevamente para que los usuarios de tu organización los autentiquen.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Debajo de "{% data variables.product.prodname_ghe_cloud %} Free Trial" (Prueba gratis de {% data variables.product.prodname_ghe_cloud %}), haz clic en **Buy Enterprise** (Comprar empresa) o **Downgrade to Team** (Bajar de categoría a equipo). ![Botones Comprar Enterprise y Bajar de categoría a Team](/assets/images/help/organizations/finish-trial-buttons.png)
 6. Sigue las indicaciones para ingresar tu método de pago, a continuación haz clic en **Enviar**.
 
diff --git a/translations/es-ES/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/es-ES/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index 0d52759962..950c1a7a44 100644
--- a/translations/es-ES/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/es-ES/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 En este ejemplo, abordaremos todos los comandos disponibles de `git rebase`, excepto `exec`.
 
 Comenzaremos nuestra rebase ingresando `git rebase --interactive HEAD~7` en el terminal. Nuestro editor de texto preferido mostrará las siguientes líneas:
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md
index 8e1a45baa8..050ffdc924 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: Acerca de Importador GitHub
-intro: 'Si tienes un código fuente en Subversion, Mercurial, Team Foundation Server u otro repositorio de Git, puedes moverlo a GitHub usando el Importador GitHub.'
+intro: 'If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer.'
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ Importador GitHub es una herramienta que importa de forma rápida repositorios d
 
 Durante una importación, dependiendo del sistema de control de la versión del que estás importando, puedes autenticar con tu repositorio remoto, actualizar la atribución del autor de la confirmación e importar repositorios con archivos grandes (o eliminar archivos grandes si no quieres usar Large File Storage de Git).
 
-| Acción de importación                                                                                                      | Subversion | Mercurial | Team Foundation Server |  Git  |
-|:-------------------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:|
-| Autenticar con repositorio remoto                                                                                          |   **X**    |   **X**   |         **X**          | **X** |
-| [Actualizar la atribución del autor de la confirmación](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   |         **X**          |       |
-| Mover archivos grandes a [Large File Storage de Git](/articles/about-git-large-file-storage)                               |   **X**    |   **X**   |         **X**          |       |
-| Eliminar archivos grandes de tu repositorio                                                                                |   **X**    |   **X**   |         **X**          |       |
+| Acción de importación                                                                                                      | Subversion | Mercurial | TFVC  |  Git  |
+|:-------------------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:-----:|:-----:|
+| Autenticar con repositorio remoto                                                                                          |   **X**    |   **X**   | **X** | **X** |
+| [Actualizar la atribución del autor de la confirmación](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   | **X** |       |
+| Mover archivos grandes a [Large File Storage de Git](/articles/about-git-large-file-storage)                               |   **X**    |   **X**   | **X** |       |
+| Eliminar archivos grandes de tu repositorio                                                                                |   **X**    |   **X**   | **X** |       |
 
 ### Leer más
 
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index 747f5cd1e6..a2f780121e 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-Recomendamos utilizar [GitHub Importer](/articles/about-github-importer) para importar proyectos desde Subversion, Mercurial, Team Foundation Server u otro repositorio de Git. También puedes utilizar estas herramientas externas para convertir tus proyectos a Git.
+We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. También puedes utilizar estas herramientas externas para convertir tus proyectos a Git.
 
 {% endif %}
 
@@ -32,12 +32,9 @@ Recomendamos estas herramientas para convertir repositorio de Subversion a Git:
 
 Recomendamos [hg-fast-export](https://github.com/frej/fast-export) para convertir repositorios de Mercurial a Git.
 
-### Importar desde Team Foundation Server
+### Importing from TFVC
 
-Recomendamos estas herramientas para mover cambios entre Team Foundation Server y Git:
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
 
 {% tip %}
 
diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md
index 94af48a4cf..33441679e1 100644
--- a/translations/es-ES/content/github/index.md
+++ b/translations/es-ES/content/github/index.md
@@ -36,7 +36,6 @@ versions:
 {% link_in_list /collaborating-with-issues-and-pull-requests %}
 
 {% link_in_list /managing-your-work-on-github %}
-{% link_in_list /developing-online-with-codespaces %}
 
 {% link_in_list /searching-for-information-on-github %}
 
@@ -57,7 +56,6 @@ versions:
 
 {% link_in_list /extending-github %}
 
-{% link_in_list /supporting-the-open-source-community-with-github-sponsors %}
 {% link_in_list /finding-talent-with-github-jobs %}
 {% link_in_list /working-with-github-support %}
 {% link_in_list /understanding-how-github-uses-and-protects-your-data %}
diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
index f85148b816..c6d2f63c04 100644
--- a/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
+++ b/translations/es-ES/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
@@ -26,7 +26,7 @@ Si el archivo{% if currentVersion == "free-pro-team@latest" or currentVersion ve
 
 1. Dirígete al archivo que deseas eliminar de tu repositorio.
 2. En la parte superior del archivo, da clic en
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index fc6621cb9d..79ec916361 100644
--- a/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/es-ES/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### Acerca de la navegación de código en {% data variables.product.prodname_dotcom %}
 
 La navegación de código utiliza la biblioteca de código abierto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). Los siguientes idiomas son compatibles:
diff --git a/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index b60efb6855..c5da27794b 100644
--- a/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/es-ES/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -38,7 +38,7 @@ versions:
 
 Después de eliminar los archivos de {% data variables.large_files.product_name_short %}, los objetos de {% data variables.large_files.product_name_short %} aún existirán en el almacenamiento remoto{% if currentVersion == "free-pro-team@latest" %} y seguirán contando en tu cuota de almacenamiento de {% data variables.large_files.product_name_short %}{% endif %}.
 
-Para eliminar los objetos de {% data variables.large_files.product_name_short %} de un repositorio, {% if currentVersion == "free-pro-team@latest" %}borra y vuelve a crear el repositorio. Cuando se borra un repositorio también se borra cualquier informe de problemas, estrellas y bifurcaciones asociados al mismo. Para obtener más información, consulta la sección "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)".{% else %}contacta a tu administrador de {% data variables.product.prodname_enterprise %} para archivar los objetos. Los objetos archivados se purgan después de tres meses.{% endif %}
+Para eliminar los objetos de {% data variables.large_files.product_name_short %} de un repositorio, {% if currentVersion == "free-pro-team@latest" %}borra y vuelve a crear el repositorio. Cuando se borra un repositorio también se borra cualquier informe de problemas, estrellas y bifurcaciones asociados al mismo. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Los objetos archivados se purgan después de tres meses.{% endif %}
 
 {% note %}
 
diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index bd96767bd5..ab3ebdf169 100644
--- a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,12 +1,14 @@
 ---
 title: Acerca de las alertas para las dependencias vulnerables
-intro: '{% data variables.product.product_name %} envía {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} cuando detectamos vulnerabilidades que afectan tu repositorio.'
+intro: '{% data variables.product.product_name %} envía {% if currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} cuando detectamos vulnerabilidades que afectan tu repositorio.'
 versions:
   enterprise-server: <=2.22
 topics:
   - Security
 ---
- 
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
 ### Acerca de las dependencias vulnerables
 
 {% data reusables.repositories.a-vulnerability-is %}
@@ -15,12 +17,10 @@ Cuando tu código depende de un paquete que tiene una vulnerabilidad de segurida
 
 ### Detección de dependencias vulnerables
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}El {% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables y envía {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detecta dependencias vulnerables y envía alertas de seguridad{% endif %} cuando:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}El {% data variables.product.prodname_dependabot %} detecta las dependencias vulnerables y envía {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detecta dependencias vulnerables y envía alertas de seguridad{% endif %} cuando:
 
-{% if currentVersion == "free-pro-team@latest" %}
-- Se agrega una vulnerabilidad nueva a la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)".{% else %}
-- Se sincronizan los datos de las asesorías nuevas en {% data variables.product.prodname_ghe_server %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información acerca de los datos de las asesorías, consulta la sección "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Buscar vulnerabilidades de seguridad en el {% data variables.product.prodname_advisory_database %}</a>".{% endif %}
-- La gráfica de dependencias para los cambios a un repositorio. Por ejemplo, cuando un colaborador sube una confirmación para cambiar los paquetes o versiones de las cuales depende{% if currentVersion == "free-pro-team@latest" %}, o cuando el código de una de las dependencias cambia{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
+- Se sincronizan los datos de las asesorías nuevas en {% data variables.product.prodname_ghe_server %} cada hora desde {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
+- La gráfica de dependencias para los cambios a un repositorio. Por ejemplo, cuando un colaborador sube una confirmación para cambiar los paquetes o versiones de los cuales depende. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 
 {% data reusables.repositories.dependency-review %}
 
@@ -32,7 +32,7 @@ Para encontrar una lista de ecosistemas para las cuales {% data variables.produc
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
 ### Alertas del {% data variables.product.prodname_dependabot %} para dependencias vulnerables
 {% else %}
 ### Alertas de seguridad para las dependencias vulnerables
@@ -40,25 +40,11 @@ Para encontrar una lista de ecosistemas para las cuales {% data variables.produc
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detecta dependencias vulnerables en repositorios _públicos_ y genera {% data variables.product.prodname_dependabot_alerts %} predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios.
-
-También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. 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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
-
-{% data variables.product.product_name %} comienza a generar la gráfica de dependencias inmediatamente y genera alertas de cualquier dependencia vulnerable tan pronto como las identifique. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)".
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 Cuando
 {% data variables.product.product_name %} identifica una dependencia vulnerable, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad para el repositorio. La alerta incluye un enlace al archivo afectado en el proyecto e información acerca de la versión arreglada. {% data variables.product.product_name %} también notifica a los mantenedores de los repositorios afectados sobre la nueva alerta de acuerdo con sus preferencias de notificaciones. Para obtener más información, consulta la sección "[Configurar notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-Para los repositorios en donde
-{% data variables.product.prodname_dependabot_security_updates %} se encuentra habilitado, la alerta también podría contener un enlace a una solicitud de cambios para actualizar el archivo de manifiesto o de bloqueo a la versión mínima que resuelva la vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)".
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 Cuando
 {% data variables.product.product_name %} identifica una dependencia vulnerable, enviamos una alerta de seguridad a los mantenedores de los repositorios afectados con detalles de la vulnerabilidad, un enlace al archivo afectado en el proyecto, e información acerca de una versión arreglada.
@@ -70,30 +56,17 @@ Cuando
 
 {% endwarning %}
 
-### Acceso a las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}
+### Acceso a las alertas de {% if currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}
 
-Puedes ver todas las alertas que afectan un proyecto en particular{% if currentVersion == "free-pro-team@latest" %} en la pestaña de seguridad del repositorio o{% endif %} en la gráfica de dependencias del mismo.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %}
+Puedes ver todas las alertas que afectan a un proyecto en particular en la gráfica de dependencias del repositorio.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 Predeterminadamente, notificamos a las personas con permisos adminsitrativos en los repositorios afectados sobre las
-{% data variables.product.prodname_dependabot_alerts %} nuevas.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga públicamente las vulnerabilidades que se identifican en los repositorios. También puedes hacer que las {% data variables.product.prodname_dependabot_alerts %} sean visibles para más personas o equipos que trabajen en los repositorios que te pertenecen o para los cuales tienes permisos administrativos. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
-{% endif %}
+{% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 Enviamos alertas de seguridad para las personas con permisos de administrador en los repositorios por defecto afectados.
 {% data variables.product.product_name %} nunca disemina públicamente las vulnerabilidades identificadas de ningún repositorio.
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obtener más información, consulta la sección "[Elegir el método de entrega para tus notificaciones](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)".{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-También puedes ver todas las
-{% data variables.product.prodname_dependabot_alerts %} que corresponden a una vulnerabilidad específica en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)".
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Leer más
-
-- "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "Entender cómo {% data variables.product.product_name %} utiliza y protege tus datos"{% endif %}</li> </ul>
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obtener más información, consulta la sección "[Elegir el método de entrega de tus notificaciones](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)".{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".{% endif %}
diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index 0b6b26e3a6..65ef762b03 100644
--- a/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,57 +1,57 @@
 ---
-title: Configuring notifications for vulnerable dependencies
-shortTitle: Configuring notifications
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+title: Configurar las notificaciones para las dependencias vulnerables
+shortTitle: Configurar notificaciones
+intro: 'Optimiza la forma en la que recibes las notificaciones sobre las alertas de  {% if currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}.'
 versions:
   enterprise-server: '>=2.21 <=2.22'
 topics:
   - Security
 ---
 
-### About notifications for vulnerable dependencies
+<!--See /content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies for the current version of this article -->
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
-{% endif %} 
+### Acerca de las notificaciones para las dependencias vulnerables
 
-{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}Cuando el {% data variables.product.prodname_dependabot %} detecta dependencias vulnerables en tus repositorios, generamos una alerta del {% data variables.product.prodname_dependabot %} y la mostramos en la pestaña de seguridad del repositorio. {% data variables.product.product_name %} notifica a los mantenedores de los repositorios afectados sobre la alerta nueva de acuerdo con su preferencias de notificación.{% else %}Cuando {% data variables.product.product_name %} detecta dependencias vulnerables en tus repositoris, este envía alertas de seguridad.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+Tu administrador de sitio necesita habilitar las alertas de seguridad para las dependencias vulnerables de
+{% data variables.product.product_location %} antes de que puedas utilizar la característica. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %}
+Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para notificaciones en tu empresa, recibirás
+{% if currentVersion ver_gt "enterprise-server@2.21" %}Alertas de {% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} por correo electrónico.{% endif %}
 
-{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}Los administradores de sitio también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+{% if currentVersion ver_lt "enterprise-server@2.22" %}Los administradores de sitio también pueden habilitar las alertas de seguridad sin notificaciones. Para obtener más información, consulta la sección "[Habilitar las alertas de seguridad para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configurar notificaciones para las {% if currentVersion ver_gt "enterprise-server@2.21" %}alertas de seguridad del {% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %}
 
-You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
+Puedes configurar los ajustes de notificaciones para ti mismo o para tu organización desde el menú desplegable de administrar notificaciones {% octicon "bell" aria-label="The notifications bell" %} que se muestra en la parte superior de cada página. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)".
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-  ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+  ![Opciones de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 {% else %}
-  ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png)
+  ![Opciones de alertas de seguridad](/assets/images/help/notifications-v2/security-alerts-options.png)
 {% endif %}
 
 {% note %}
 
-**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+**Nota:** Puedes filtrar las notificaciones de {% data variables.product.company_short %} para mostrar las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %}. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)".
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %}Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
 
-### How to reduce the noise from notifications for vulnerable dependencies
+### Cómo reducir el ruido de las notificaciones para las dependencias vulnerables
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+Si te preocupa recibir demasiadas notificaciones para {% if currentVersion ver_gt "enterprise-server@2.21" %}las {% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %}, te recomendamos que decidas ingresar en el resúmen semanal por correo electrónico, o apagar las notificaciones mientras aún tienes {% if currentVersion ver_gt "enterprise-server@2.21" %} las {% else %}alertas de seguridad{% endif %} de las {% data variables.product.prodname_dependabot_alerts %} habilitadas. Aún puedes navegar para ver tus {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %} en la pestaña de Seguridad de tu repositorio.
 
-### Further reading
+### Leer más
 
-- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
-- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
+- "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
+- "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/index.md b/translations/es-ES/content/github/managing-security-vulnerabilities/index.md
index 5887c5bc30..016f9df399 100644
--- a/translations/es-ES/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/es-ES/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### Índice
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index 77cce990b5..e7edf27726 100644
--- a/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index f4e02787e3..07b8e05cd3 100644
--- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -26,13 +26,9 @@ Puedes elegir recibir actualizaciones continuas sobre actividades específicas e
 Puedes elegir suscribirte a las notificaciones de:
 - Una conversación sobre un informe de problemas, solicitud de extracción o gist específico.
 - Todas las actividades en un repositorio o en un debate de equipo.
-- Actividades de CI, tales como el estado de los flujos de trabajo en los repositorios configurados con {% data variables.product.prodname_actions %}.
-{% if currentVersion == "free-pro-team@latest" %}
-- Propuestas, solicitudes de cambios, lanzamientos y debates (si están habilitados) de un repositorio.
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- Lanzamientos en un repositorio.
-{% endif %}
+- Actividades de CI, tales como el estado de los flujos de trabajo en los repositorios configurados con {% data variables.product.prodname_actions %}. {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 También puedes elegir seguir automáticamente todos los repositorios en los que tienes acceso de escritura, con excepción de sus bifurcaciones. Puedes seguir de cerca manualmente a cualquier otro repositorio al que tengas acceso si das clic en **Seguir**.
 
diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
index 95da5b27d2..53987e6752 100644
--- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
+++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
@@ -58,7 +58,7 @@ Adicionalmente, puedes recibir y clasificar las notificaciones en tu dispositivo
 
 #### Beneficios de utilizar un cliente de correo electrónico para las notificaciones
 
-Un beneficio de utilizar un cliente de correo electrónico es que todas tus notificaciones se pueden mantener por tiempo indefinido dependiendo de la capacidad de almacenamiento de éste. Tus notificaciones en bandeja de entrada se mantendrán únicamente por 5 meses a menos de que las hayas marcado como **Guardadas**. Las notificaciones **Guardadas** se mantendrán por tiempo indefinido. Para obtener más información acerca de la política de retención de tu bandeja de entrada, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)".
+Un beneficio de utilizar un cliente de correo electrónico es que todas tus notificaciones se pueden mantener por tiempo indefinido dependiendo de la capacidad de almacenamiento de éste. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. Las notificaciones **Guardadas** se mantendrán por tiempo indefinido. Para obtener más información acerca de la política de retención de tu bandeja de entrada, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)".
 
 Enviar notificaciones a tu cliente de correo electrónico también te permite personalizar tu bandeja de entrada de acuerdo con la configuración del mismo, lo cual puede incluir etiquetas personalizadas o con códigos de color.
 
@@ -69,16 +69,17 @@ Las notificaciones por correo electrónico también permiten la flexibilidad con
 Cuando observas un repositorio, te suscribes a las actualizaciones de la actividad en el mismo. De forma similar, cuando observas las discusiones específicas de un equipo, te suscribes a todas las actualizaciones de la conversación en la página de ese equipo. Para obtener más información, consulta [Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)".
 
 Para ver los repositorios que estás observando, dirígete a tu [página de observados](https://github.com/watching). Para obtener más información, consulta la sección "[Administrar suscricpiones y notificaciones en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)".
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
 #### Configurar notificaciones
 {% endif %}
 Puedes configurar las notificaciones de un repositorio en la página del mismo, o en tu página de observados.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Puedes elegir solo recibir notificaciones para los lanzamientos de un repositorio o ignorar todas las notificaciones del mismo.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %} Puedes elegir solo recibir notificaciones para los lanzamientos de un repositorio o ignorar todas las notificaciones del mismo.{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 #### Acerca de las notificaciones personalizadas
-{% data reusables.notifications-v2.custom-notifications-beta %}
-Puedes personalizar las notificaciones de un repositorio, por ejemplo, puedes elegir que solo se te notifique cuando sucedan actualizaciones en uno o más tipos de eventos (propuestas, solicitudes de cambios, lanzamientos, debates) dentro de un repositorio, o ignorar todas las notificaciones del mismo.
-{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
+You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events (
+{% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository.
+{% endif %} Para obtener más información, consulta la sección "[Configurar tus ajustes de observación para un repositorio individual](#configuring-your-watch-settings-for-an-individual-repository)" a continuación.
 
 #### Participar en conversaciones
 Siempre que comentes en una conversación, o cuando alguien @menciona tu nombre de usuario, estarás _participando_ en una conversación. Predeterminadamente, estás suscrito automáticamente a una conversación cuando participas en ella. Puedes desuscribirte manualmente de una conversación en la que hayas participado si das clic en **Desuscribir** en el informe de problemas o solicitud de extracción, o a través de la opción de **Desuscribir** en la bandeja de notificaciones.
@@ -133,7 +134,7 @@ Las notificaciones por correo electrónico de {% data variables.product.product_
 | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | dirección `De`                          | Esta dirección siempre será {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'aquella dirección de correo electrónico de "no-reply" que configuró tu administrador de sitio'{% endif %}.                                                                                                                                |
 | campo `Para`                            | Este campo se conecta directamente al hilo.{% if currentVersion != "github-ae@latest" %} Si respondes al correo electrónico, agregarás un comentario nuevo a la conversación.{% endif %}
-| dirección `Cc`                          | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son: <ul><li>`assign`: Te asignaron a una propuesta o solicitud de extracción.</li><li>`author`: Creaste una propuesta o solicitud de extracción.</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}<li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li>{% endif %}<li>`comment`: Comentaste una propuesta o solicitud de extracción.</li><li>`manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.</li><li>`mention`: Te mencionaron en una propuesta o solicitud de extracción.</li><li>`push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.</li><li>`review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.</li>{% if currentVersion != "github-ae@latest" %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.</li>{% endif %}<li>`state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.</li><li>`subscribed`: Hubo una actualización en un repositorio que estás mirando.</li><li>`team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.</li><li>`your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.</li></ul> |
+| dirección `Cc`                          | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son: <ul><li>`assign`: Te asignaron a una propuesta o solicitud de extracción.</li><li>`author`: Creaste una propuesta o solicitud de extracción.</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}<li>`ci_activity`: Se completó uya ejecución de flujo de trabajo de {% data variables.product.prodname_actions %} que activaste.</li>{% endif %}<li>`comment`: Comentaste una propuesta o solicitud de extracción.</li><li>`manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.</li><li>`mention`: Te mencionaron en una propuesta o solicitud de extracción.</li><li>`push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.</li><li>`review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.</li>{% if currentVersion != "github-ae@latest" %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.</li>{% endif %}<li>`state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.</li><li>`subscribed`: Hubo una actualización en un repositorio que estás mirando.</li><li>`team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.</li><li>`your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.</li></ul> |
 | Campo `mailing list` (lista de correos) | Este campo identifica el nombre del repositorio y su propietario. El formato de esta dirección siempre es `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 | Campo `X-GitHub-Severity`               | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". 
 {% endif %}
@@ -159,19 +160,22 @@ Si inhabilitas la opción de "Observar los repositorios automáticamente", no po
 
 ### Configurar los ajustes de observación para un repositorio individual
 
-Puedes elegir si quieres observar o dejar de observar un repositorio individual. También puedes elegir que solo se te notifique de {% if currentVersion == "free-pro-team@latest" %}algunos tipos de eventos, tales como propuestas, solicitudes de cambios, debates (si se habilitaron en el repositorio) y {% endif %}lanzamientos nuevos, o puedes ignorar completamente un repositorio específico.
+Puedes elegir si quieres observar o dejar de observar un repositorio individual. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 2. En la esquina superior derecha, da clic en el menú desplegable "Observar" para seleccionar una opción de observación.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
    ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
-{% data reusables.notifications-v2.custom-notifications-beta %}
+
 La opción **Personalizar** te permite personalizar aún más las notificaciones para que solo se te notifique cuando suceden eventos específicos en el repositorio, adicionalmente a participar y tener @menciones.
 
+{% if currentVersion == "free-pro-team@latest" %}
+   ![Opciones de observación personalizada en un menú desplegable de un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png)
+{% else %}
    ![Opciones de observación personalizada en un menú desplegable de un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom2.png)
+{% endif %}
 
 Si seleccionas "propuestas", se te notificará sobre y suscribirá a las actualizaciones de cada propuesta (incluyendo aquellas que existieron antes de que seleccionaras esta opción) del repositorio. Si se te @menciona en una solicitud de cambios de este repositorio, también recibirás notificaciones por este evento y se te suscribirá a las actualizaciones de esa solicitud de cambios específica adicionalmente a las notificaciones que tendrás sobre las propuestas.
 
@@ -220,7 +224,7 @@ Para obtener más información acerca de los métodos de entrega de notificacion
 
 Elige cómo quieres recibir las actualizaciones para las ejecuciones de flujo de trabajo en los repositorios que estás observando y que se configuraron con {% data variables.product.prodname_actions %}. También puedes elegir recibir únicamente las notificaciones para las ejecuciones de flujo de trabajo fallidas.
 
-  ![Opciones de alerta del {% data variables.product.prodname_dependabot_short %}](/assets/images/help/notifications-v2/github-actions-notification-options.png)
+  ![Notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png)
 
 {% endif %}
 
@@ -248,7 +252,7 @@ También puedes programar si {% data variables.product.prodname_mobile %} enviar
 
 1. En el menú inferior, pulsa en **Perfil**.
 2. Para ver tu configuración, toca en {% octicon "gear" aria-label="The Gear icon" %}.
-3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
+3. Para actualizar tu configuración de notificaciones, pulsa en **Configurar Notificaciones** y luego usa los alternadores para habilitar o inhabilitar tus tipos de notificaciones de subida preferidos.
 4. Opcionalmente, para programar cuando {% data variables.product.prodname_mobile %} enviará notificaciones de subida a tu dispositivo móvil, pusla en **Horas laborales**, utiliza el botón para alternar de **Horas laborales personalizadas** y elige entonces cuándo te gustaría recibir notificaciones de subida.
 
 ### Configurar tus ajustes de observación para un repositorio individual con {% data variables.product.prodname_mobile %}
diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index 195c94cd92..3d8df6548d 100644
--- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -57,13 +57,13 @@ Cuando dejas de observar un repositorio, de desuscribes de notificaciones futura
 {% data reusables.notifications.access_notifications %}
 1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable de "Administrar notificaciones" para dar clic en **Repositorios que sigues**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. En la página de repositorios que sigues, después de que hayas evaluado aquellos que estás siguiendo, decide si quieres:
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-    - dejar de seguir un repositorio
-    - únicamente seguir los lanzamientos de un repositorio
-    - ignorar todas las notificaciones de un repositorio
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-    - dejar de seguir un repositorio
-    - ignorar todas las notificaciones de un repositorio
-    - personalizar los tipos de evento para los cuales recibes notificaciones (propuestas, solicitudes de cambio, lanzamientos o debates, si es que están habilitados)
-{% endif %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
+    - Dejar de seguir un repositorio
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    - Dejar de seguir un repositorio
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index 4a89073f6d..c55f4d695c 100644
--- a/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/es-ES/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -35,10 +35,10 @@ Cuando tu bandeja de entrada tiene demasiadas notificaciones como para administr
 Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)".
 
 Para ver un resumen de tus suscripciones a repositorios, consulta la sección "[Revisar los repositorios que estás observando](#reviewing-repositories-that-youre-watching)".
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**Tip:** Puedes seleccionar los tipos de evento para los cuales quieres recibir notificaciones si utilizas la opción **Personalizar** de la lista desplegable **Observar/Dejar de observar** en tu [página de observados](https://github.com/watching) o en cualquier página de repositorio en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
+**Tip:** Puedes seleccionar los tipos de evento para los cuales quieres recibir notificaciones si utilizas la opción **Personalizar** de la lista desplegable **Observar/Dejar de observar** en tu [página de observados](https://github.com/watching) o en cualquier página de repositorio en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
 
 {% endtip %}
 {% endif %}
@@ -67,16 +67,15 @@ Muchas personas se olvidan de los repositorios que han marcado para observar. De
 
 1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" y da clic en **Repositorios que sigues**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Evalúa si los repositorios que estás siguiendo de cerca tienen actualizaciones que aún sean útiles y relevantes. Cuando sigues de cerca un repositorio, se te notificará de todas las conversaciones en el mismo.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
   ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** En vez de observar un repositorio, considera solo recibir notificaciones {% if currentVersion == "free-pro-team@latest" %}cuando existan actualizaciones a las propuestas, solicitudes de cambios, lanzamientos o debates (si se habilitaron en el repositorio), o cualquier combinación de estas opciones,{% else %}para los lanzamientos en un repositorio,{% endif %} o dejar de observar el repositorio completamente.
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
 
   Cuando dejas de seguir un repositorio, aún se te puede notificar cuando te @mencionan o cuando participas en un hilo. Cuando configuras el recibir notificaciones para ciertos tipos de evento, solo se te notificará cuando existan actualizaciones en éstos dentro del repositorio, si estás participando en un hilo, o si tú o un equipo al que perteneces tiene alguna @mención.
 
diff --git a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index fd622bcae9..3e868b9ced 100644
--- a/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/es-ES/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ Los parámetros de consulta son partes opcionales de una URL que puedes personal
 
 Debes tener los permisos adecuados para cualquier acción para usar el parámetro de consulta equivalente. Por ejemplo, debes tener permiso para agregar una etiqueta a una propuesta para usar el parámetro de consulta `labels`.
 
-Si creas una URL no válida usando los parámetros de consulta o si no tienen los permisos adecuados, la URL devolverá una página de error 404.
+Si creas una URL inválida utilizando parámetros de consulta o si no tienes los permisos adecuados, la URL devolverá una página de error `404 Not Found`. Si creas una URL que exceda el límite del servidor, esta devolverá una página de error `414 URI Too Long`.
 
 ### Parámetros de consulta admitidos
 
diff --git a/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index a0aff28e78..15ccf83234 100644
--- a/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/es-ES/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. Elige una de las siguientes opciones:
     - Para crear un nuevo hito, haz clic en **Nuevo hito**. ![Botón Nuevo hito](/assets/images/help/repository/new-milestone.png)
     - Para editar un hito, haz clic en **Editar** junto al hito que deseas editar. ![Opción Editar hito](/assets/images/help/repository/edit-milestone.png)
-5. Escribe el título, la descripción y los demás cambios del hito, y luego haz clic en **Create milestone** (Crear hito) o **Save changes** (Guardar cambios).
+5. Escribe el título, la descripción y los demás cambios del hito, y luego haz clic en **Create milestone** (Crear hito) o **Save changes** (Guardar cambios). Los hitos interpretarán la sintaxis del lenguaje de marcado. Para obtener más información sobre la sintaxis de marcado, consulta la sección "[Sintaxis de marcado y formateado básica](/github/writing-on-github/basic-writing-and-formatting-syntax)".
 
 ### Eliminar hitos
 
diff --git a/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index 39f2f95f4c..5f0c207ddf 100644
--- a/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/es-ES/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ Una vez que inhabilites tableros de proyecto de repositorios en una organizació
 
 Cuando inhabilitas tableros de proyecto, ya no ves su información de manera cronológica o de acuerdo con los [registros de auditoría](/articles/reviewing-your-security-log/).
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 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":
     - Para inhabilitar los tableros de proyecto que se usan en toda la organización, quita la marca de selección de **Habilitar proyectos para la organización**.
     - Para inhabilitar los tableros de proyecto de los repositorios en la organización, quita la marca de selección de **Habilitar proyectos para todos los repositorios**. ![Casillas de verificación para inhabilitar proyectos para una organización o para todos los repositorios de una organización](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index d7b8647f96..3d68429e30 100644
--- a/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/es-ES/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: Adjuntos de archivos en propuestas y solicitudes de extracción
-intro: 'Cuando abres una propuesta o actualizas una solicitud de extracción, puedes usar los adjuntos de propuestas para cargar imágenes de las características propuestas o capturas de pantalla de errores.'
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -14,7 +14,7 @@ topics:
 
 {% warning %}
 
-**Advertencia:** Si agregas una imagen a una solicitud de extracción o un comentario sobre una propuesta, cualquier usuario podrá ver la URL de la imagen anonimizada sin autenticación, aun si la solicitud de extracción se encuentra en un repositorio privado{% if enterpriseServerVersions contains currentVersion %} o si el modo privado se encuentra habilitado{% endif %}. Para mantener las imágenes confidenciales en privado, limítalas a una red privada o a un servidor que requiera de autenticación. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información sobre las URL anonimozadas, consulta la sección "[Acerca de las URL de imagen anonimizadas](/articles/about-anonymized-image-urls)".{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ Para adjuntar un archivo a una propuesta o una conversación de una solicitud de
 
 {% endtip %}
 
-El tamaño máximo de los archivos es de 25 MB y el tamaño máximo de las imágenes es de 10 MB.
-{% if currentVersion == "free-pro-team@latest" %}
-Los videos pueden tener un tamaño de hasta 100 MB si el repositorio pertenece a un usuario u organización que tenga un plan de pago de GitHub.
-
-{% note %}
-
-**Nota:** La compatibilidad con adjuntos de video se encuentra actualmente en beta y está sujeto a cambios.
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 Archivos compatibles:
 
@@ -49,7 +43,7 @@ Archivos compatibles:
 * Documentos de Microsoft Word (*.docx*), Powerpoint (*.pptx*) y Excel (*.xlsx*)
 * Archivos de texto (*.txt*)
 * PDF (*.pdf*)
-* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" %}
+* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * Video (*.mp4*, *.mov*){% endif %}
 
 ![GIF animados adjuntos](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md b/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md
index d63dc9f6a2..95b43a84ff 100644
--- a/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md
+++ b/translations/es-ES/content/github/managing-your-work-on-github/managing-labels.md
@@ -49,6 +49,8 @@ Cualquiera con acceso de lectura a un repositorio puede ver y buscar las etiquet
 
 Las etiquetas predeterminadas se incluyen en todos los repositorios nuevos cuando se crea el repositorio, pero luego puedes editarlas o eliminarlas.
 
+Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 Los propietarios de la organización pueden personalizar las etiquetas predeterminadas para los repositorios de la organización. Para obtener más información, consulta "[Administrar etiquetas predeterminadas para los repositorios en tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)".
 {% endif %}
diff --git a/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index 613b49f929..bc2d893e47 100644
--- a/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/es-ES/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ Puedes clasificar cualquier vista filtrada por:
 * Las propuestas y solicitudes de extracción menos comentadas
 * Las propuestas y solicitudes de extracción actualizadas más recientemente
 * Las propuestas y solicitudes de extracción actualizadas con mayor antigüedad
-* La [reacción](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) más agregada en propuestas o solicitudes de extracción
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. En el ángulo superior derecho, selecciona el menú desplegable de Clasificación. ![Utilizar la pestaña desplegable de Clasificación](/assets/images/help/issues/issues_sort_dropdown.png)
+1. En el ángulo superior derecho, selecciona el menú desplegable de Clasificación. ![Utilizar la pestaña desplegable de Clasificación](/assets/images/help/issues/issues_sort_dropdown.png)
 
 Para borrar tu selección de clasificación, haz clic en **Sort** &#062 (Clasificar); **Newest** (Más reciente).
 
diff --git a/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md b/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md
index 0fdd5573f7..ab1fc9c37d 100644
--- a/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/es-ES/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ Puedes utilizar el calificador `path` (ruta) para buscar el código fuente que a
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) encuentra los archivos JavaScript con la palabra "console" en un directorio <em>app/public</em> o en cualquiera de sus subdirectorios (incluso si se encuentran en <em>app/public/js/form-validators</em>). |
 
 ### Buscar por lenguaje
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-Puedes buscar el código basado en el lenguaje en que está escrito.
+Puedes buscar el código basado en el lenguaje en que está escrito. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | Qualifier                  | Ejemplo                                                                                                                                                                                                              |
 | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 0ef004e0da..279c66db63 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de los límites de gasto](#about-spending-limits)".
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. Para obtener más información, consulta la sección "[Introducción a las {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)".
+
+{% endnote %}
 
 Si compraste {% data variables.product.prodname_enterprise %} mediante un Acuerdo de Microsoft Enterprise, puedes conectar tu ID de Suscripción de Azure a tu cuenta empresarial para habilitar y pagar por el uso de {% data variables.product.prodname_registry %} más allá de las cantidades que se incluyen en tu cuenta. Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)".
 
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index dd5e92db23..b9175acc01 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### Leer más
 
-- "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)"
-- "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)"
+- "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Patrocinar a contribuyentes de código abierto](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index a63787780e..8e1f913d71 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,26 +16,11 @@ Para negociar el licenciamiento de {% data variables.product.prodname_GH_advance
 
 ### Acerca de los números de confirmante para {% data variables.product.prodname_GH_advanced_security %}
 
-Registramos y mostramos dos números de confirmantes para la {% data variables.product.prodname_GH_advanced_security %} en {% data variables.product.prodname_dotcom_the_website %}:
-
-- **Confirmantes** es la cantidad de confirmantes que contribuye con por lo menos un repositorio privado en una organización y que utilizan una plaza de tu licencia. Es decir, también son un miembro de la organización, un colaborador externo, o tienen una invitación pendiente para unirse a una organización en tu empresa.
-- **Únicos para este repositorio/organización** es la cantidad de confirmantes que contribuyen únicamente a este repositorio o a los repositorios en esta organización. Esta cantidad muestra cuántas plazas de la licencia puedes liberar si inhabilitas la {% data variables.product.prodname_GH_advanced_security %} para este repositorio u organización.
-
-Si no hay confirmantes únicos, esto significa que todos los confirmantes activos también contribuyen con otros repositorios u organizaciones que utilizan la {% data variables.product.prodname_GH_advanced_security %}. Inhabilitar la característica para este repositorio u organización no liberará plazas en tu licencia.
-
-{% note %}
-
-**Nota:** La cantidad total de plazas que se utilizan en tu licencia no es la suma de ya sea los confirmantes o los confirmantes únicos en cada repositorio u organización. Esto es porque hay personas que contribuyen con repositorios u organizaciones múltiples. La cantidad de plazas que se utilizan se miden en toda la cuenta empresarial para garantizar que cada persona se cuenta únicamente una vez sin importar en cuántos repositorios u organizaciones contribuyan.
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### Administrar tu uso de licencia para {% data variables.product.prodname_GH_advanced_security %}
 
-Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} para un solo repositorio, o para todos los repositorios en una organización, {% data variables.product.company_short %} te muestra cuántas plazas adicionales se utilizarán y te pedirá que confirmes. Si inhabilitas el acceso a {% data variables.product.prodname_GH_advanced_security %}, se liberará cualquier plaza que utilice un confirmante "único". Esto hace que el impacto de tus cambios sobre el uso de tu licencia sea más fácil de entender.
-
-Si sobrepasas el límite de tu licencia, {% data variables.product.prodname_GH_advanced_security %} seguirá trabajando en todos los repositorios en donde ya se encuentre habilitado. Sin embargo, en las organizaciones en donde se habilita la {% data variables.product.prodname_GH_advanced_security %} para los repositorios nuevos, se crearán repositorios con la característica inhabilitada. Adicionalmente, la opción para habilitar la {% data variables.product.prodname_GH_advanced_security %} para los repositorios existentes no estará disponible. Si cambias la visibilidad de un repositorio público a privado, entonces la {% data variables.product.prodname_GH_advanced_security %} se inhabilitará para dicho repositorio.
-
-Tan pronto como liberes algunas plazas, al inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para algunos repositorios o al incrementar tu tamaño de licencia, las opciones para habilitar la {% data variables.product.prodname_GH_advanced_security %} funcionarán nuevamente como normales.
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
 Puedes requerir políticas para permitir o dejar de permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen la {% data variables.product.prodname_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)".
 
@@ -43,9 +28,4 @@ Para obtener más información sobre cómo visualizar el uso de licencia, consul
 
 ### Obtener el máximo de tu licencia de {% data variables.product.prodname_GH_advanced_security %}
 
-Cuando decides qué repositorios y organizaciones priorizar para la {% data variables.product.prodname_GH_advanced_security %}, debes revisarlas e identificar:
-
-- Las bases de código que son más críticas para el éxito de tu empresa. Estos son los proyectos para los cuales la introducción de código vulnerable, los secretos de código rígido, o las dependencias vulnerables tendrían el mayor impacto en tu empresa.
-- Las bases de código con la frecuencia de confirmación más alta. Estos son los proyectos que se desarrollan de forma más activa y, por consecuencia, hay un riesgo mayor para que se introduzcan problemas de seguridad.
-
-Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} para estas organizaciones o repositorios, debes evaluar qué otras bases de código puedes agregar sin añadir confirmantes únicos adicionales y sin usar más plazas en tu licencia. Después de esto, revisa las siguientes bases de código más ocupadas e importantes. Si quieres incrementar la cantidad de plazas en tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}.
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index 543eaacc9f..2417b093d2 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ Tus recibos incluyen tu suscripción de {% data variables.product.prodname_dotco
 ### Agregar información a tus recibos de cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### Agregar información a los recibos de tu organización
@@ -40,9 +40,9 @@ Tus recibos incluyen tu suscripción de {% data variables.product.prodname_dotco
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index 12f7af4508..134613baf6 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ No entregamos facturas u órdenes de compra de respaldo a cuentas personales. En
 ### Actualizar el método de pago de tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### Actualizar el método de pago de tu organización
@@ -38,9 +39,10 @@ No entregamos facturas u órdenes de compra de respaldo a cuentas personales. En
 
 Si tu organización está fuera de los EE. UU. o si estás usando una cuenta corriente corporativa para pagar {% data variables.product.product_name %}, PayPal puede ser un método de pago útil.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index 259aecb101..43a070fd97 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ Cuando cancelas una prueba gratis de un plan pago, tu suscripción se cancela in
 ### Cancelar una app en tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### Cancelar una prueba gratis para una app en tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ Cuando cancelas una prueba gratis de un plan pago, tu suscripción se cancela in
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ Cuando cancelas una prueba gratis de un plan pago, tu suscripción se cancela in
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index 289661b9c2..3fadde3aab 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ Al cambiar la duración de tu ciclo de facturación, tu suscripción a {% data v
 ### Cambiar la duración del ciclo de facturación de tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ Al cambiar la duración de tu ciclo de facturación, tu suscripción a {% data v
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ Al cambiar la duración de tu ciclo de facturación, tu suscripción a {% data v
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. En "Billing overview" (Resumen de facturación), haz clic en **Change plan** (Cambiar plan). ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/billing_overview_change_plan.png)
 5. En el ángulo superior derecho, haz clic en **Switch to monthly billing** (Cambiar a facturación mensual)</strong> o **Switch to yearly billing** (Cambiar a facturación mensual). ![Sección de información de facturación](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index 1078f16146..13f858d031 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ Si ya posees una cuenta de usuario de {% data variables.product.prodname_dotcom
 
 ### Paso 3: Actualiza la organización para que tenga una suscripción anual paga.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (Puedes agregar más asientos a la organización en el siguiente paso).
 6. En "Actualizar resumen", selecciona **Pago anual** para pagar por la organización de forma anual. ![Botón de selección para la facturación anual](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. En "Pagar con" escribe los datos de tu tarjeta de crédito.![Formulario para ingresar datos de tarjeta de crédito](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. Haz clic en **Actualizar tarjeta de crédito**.
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### Paso 4: Actualiza el número de asientos pagos de la organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
index 3eca13e04e..8b953fb76b 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Discounted subscriptions for GitHub accounts
-intro: '{% data variables.product.product_name %} provides discounts to students, educators, educational institutions, nonprofits, and libraries.'
+title: Suscripciones con descuentos para cuentas GitHub
+intro: '{% data variables.product.product_name %} ofrece descuentos a estudiantes, educadores, instituciones educativas, bibliotecas y organizaciones sin fines de lucro.'
 redirect_from:
   - /articles/discounted-personal-accounts/
   - /articles/discounted-organization-accounts/
@@ -14,24 +14,24 @@ topics:
 
 {% tip %}
 
-**Tip**: Discounts for {% data variables.product.prodname_dotcom %} do not apply to subscriptions for other paid products and features.
+**Sugerencia**: Los descuentos para {% data variables.product.prodname_dotcom %} no se tienen vigencia para las suscripciones de otros productos y características pagos.
 
 {% endtip %}
 
-### Discounts for personal accounts
+### Descuentos para cuentas personales
 
-In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)."
+Además del número ilimitado de repositorios públicos y privados para estudiantes y miembros del cuerpo docente con {% data variables.product.prodname_free_user %}, los estudiantes validados pueden solicitar el {% data variables.product.prodname_student_pack %} para recibir beneficios adicionales ofrecidos por los socios de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Postularse para un paquete de desarrollo para estudiantes](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)".
 
-### Discounts for schools and universities
+### Descuentos para escuelas y universidades
 
-Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/).
+Los miembros del cuerpo docente validados pueden solicitar {% data variables.product.prodname_team %} para la enseñanza y la investigación académica. Para obtener más información, consulta la sección "[Utilizar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)". Para obtener más información, consulta "[Usar {{ site.data.variables.product.prodname_dotcom }} en tu clase y en tu investigación](/articles/using-github-in-your-classroom-and-research)". Para obtener más información, visita [{% data variables.product.prodname_education %}](https://education.github.com/).
 
-### Discounts for nonprofits and libraries
+### Descuentos para bibliotecas y organizaciones sin fines de lucro
 
-{% data variables.product.product_name %} provides free {% data variables.product.prodname_team %} for organizations with unlimited private repositories, unlimited collaborators, and a full feature set to qualifying 501(c)3 (or equivalent) organizations and libraries. You can request a discount for your organization on [our nonprofit page](https://github.com/nonprofit).
+{% data variables.product.product_name %}proporciona {% data variables.product.prodname_team %} gratuito para organizaciones y cuenta con repositorios privados ilimitados, colaboradores ilimitados, y un juego completo de características a organizaciones y bibliotecas que califiquen como 501(c)3 (o equivalentes). Puedes solicitar un descuento para tu organización en [nuestra página de organizaciones sin fines de lucro](https://github.com/nonprofit).
 
-If your organization already has a paid subscription, your organization's last transaction will be refunded once your nonprofit discount has been applied.
+Si tu organización ya tiene una suscripción paga, la última transacción de tu organización se reembolsará una vez que se haya aplicado tu descuento para organizaciones sin fines de lucro.
 
-### Further reading
+### Leer más
 
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
+- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index b1c209bfc0..7b245f6751 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -22,11 +22,7 @@ Si bajas de categoría tu cantidad de paquetes de datos, tu cambio entrará en v
 
 
 
-{% data reusables.user_settings.billing %}
-
-
-
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 
 
 
@@ -42,23 +38,15 @@ Si bajas de categoría tu cantidad de paquetes de datos, tu cambio entrará en v
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
-
-
-
 {% data reusables.profile.access_org %}
 
 
 
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 
 
 
-{% data reusables.organizations.billing %}
-
-
-
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.organizations.billing_plans %}
 
 
 
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 630a2f5eff..e552453247 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ Cuando bajas de categoría una app, tu suscripción permanece activa hasta el fi
 ### Bajar de categoría una app para tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ Cuando bajas de categoría una app, tu suscripción permanece activa hasta el fi
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index 458efd75f3..190dac8a51 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ Cuando bajas de nivel tu suscricpión de cuenta de usuario o de organización, l
 Si bajas tu cuenta de usuario de nivel desde {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, esta perderá acceso a las herramientas avanzadas de revisión de código en los repositorios privados. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Utiliza el menú desplegable **Edit** (Editar) y haz clic en **Downgrade to Free** (Bajar de categoría a Gratis). ![Botón Downgrade to free (Bajar de categoría a gratis)](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![Botón Downgrade to free (Bajar de categoría a gratis)](/assets/images/help/billing/downgrade-to-free.png)
 5. Lee la información sobre de las características a las cuales perderá acceso tu cuenta de usuario en tu siguiente fecha de facturación, y luego da clic en **Entiendo. Bajar de nivel**. ![Botón de proceder con la baja de categoría](/assets/images/help/billing/continue-with-downgrade.png)
 
 Si publicaste un sitio de {% data variables.product.prodname_pages %} en un repositorio privado y añadiste un dominio personalizado, retira o actualiza tus registros de DNS antes de bajarlo de nivel desde {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, para evitar el riesgo de que te ganen el dominio. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
@@ -45,12 +44,10 @@ Si bajas tu organización de nivel desde {% data variables.product.prodname_team
 
 Si bajas a tu organización de nivel desde {% data variables.product.prodname_ghe_cloud %} a {% data variables.product.prodname_team %} o {% data variables.product.prodname_free_team %}, la cuenta perderá acceso a los controles avanzados de seguridad, cumplimiento y despliegue. {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Utiliza el menú desplegable de **Editar** y da clic en la opción a la cual desees bajar. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### Bajar de nivel la suscripción de una organización con precios tradicionales por repositorio
@@ -59,10 +56,9 @@ Si bajas a tu organización de nivel desde {% data variables.product.prodname_gh
 
 {% data reusables.dotcom_billing.switch-legacy-billing %}Para obtener más información, consulta la sección "[Cambiar a tu organización de precios por repositorio a precios por usuario](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Debajo de "Suscripciones", selecciona el menú desplegable de "Editar" y da clic en **Editar plan**. ![Menú desplegable de Editar Plan](/assets/images/help/billing/edit-plan-dropdown.png)
 1. Debajo de "Facturación/Planes", a un costado del plan que quieras cambiar, da clic en **Bajar categoría**. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. Ingresa la razón por la cual estás degradando tu cuenta y luego haz clic en **Degradar plan**. ![Caja de texto para la razón de degradar la versión y botón de degradar](/assets/images/help/billing/downgrade-plan-button.png)
@@ -74,12 +70,10 @@ Para reducir el número de asientos pagos que usa tu organización, puedes elimi
 - "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)"
 - "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Utiliza el menú desplegable **Edit** (Editar) y haz clic en **Remove seats** (Eliminar asientos). ![menú desplegable para eliminar plazas](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![menú desplegable para eliminar plazas](/assets/images/help/billing/remove-seats-dropdown.png)
 1. En "Eliminar asientos" selecciona el número de asientos pagos de la categoría a la que deseas bajar. ![opción de eliminar plazas](/assets/images/help/billing/remove-seats-amount.png)
 1. Revisa la información sobre tu nuevo pago en tu siguiente fecha de facturación, posteriormente, da clic en **Eliminar plazas**. ![botón de eliminar plazas](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index 54c484d069..bd1f1c791d 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ Ya que no has habilitado los excedentes, tu siguiente intento de crear un artefa
 Cualquiera puede administrar el límite de gastos de {% data variables.product.prodname_actions %} para su propia cuenta de usuario.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Cualquiera puede administrar el límite de gastos de {% data variables.product.p
 
 Los propietarios de las organizaciones pueden administrar el límite de gastos de {% data variables.product.prodname_actions %} para una organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Debajo de "
-uso mensual de Paquetes y {% data variables.product.prodname_actions %}", da clic en **Administración de costos**.
-  ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index 90533bc6f8..340da9cf11 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ Ya que no has habilitado los excedentes, tu siguiente intento de publicar una ve
 Cualquiera puede administrar el límite de gastos de {% data variables.product.prodname_registry %} para su propia cuenta de usuario.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Cualquiera puede administrar el límite de gastos de {% data variables.product.p
 
 Los propietarios de las organizaciones pueden administrar el límite de gastos de {% data variables.product.prodname_registry %} para una organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Debajo de "
-uso mensual de Paquetes y {% data variables.product.prodname_actions %}", da clic en **Administración de costos**.
-  ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index 73694450ba..0ec9b86608 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ Si vas a pagar tu {% data variables.product.product_name %} suscripción con un
 ### Eliminar el método de pago de tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ Si vas a pagar tu {% data variables.product.product_name %} suscripción con un
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index 40d6c8359c..d31efbdc56 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### Actualizar la tarjeta de crédito de tu organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. Escribe la información nueva de tu tarjeta de crédito en el formulario seguro. ![Formulario de información de tarjeta de crédito](/assets/images/help/settings/creditcard-billing-form.png)
-1. Haz clic en **Update credit card** (Actualizar tarjeta de crédito) o **Save credit card** (Guardar tarjeta de crédito).
+1. Under "Payment method", click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index 405940a165..69539c3787 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ El correo electrónico de facturación de tu organización es donde {% data vari
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Dentro de **Billing email (Correo electrónico de facturación)**, escribe una dirección de correo electrónico válida. El correo electrónico no necesariamente debe ser único para la cuenta de la organización. ![Casilla de texto para el correo electrónico de facturación](/assets/images/help/settings/org-billing-email.png)
 5. Para confirmar tus cambios, haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ Si tienes usuarios que quieran recibir reportes de facturación, puedes agregar
 #### Agregar un destinatario para las notificaciones de facturación
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Debajo de "Administración de facturación", a la derecha de "Destinatarios de correo electrónico", da clic en **Agregar**. ![Agregar destinatario](/assets/images/help/billing/billing-add-email-recipient.png)
 1. Teclea la dirección de correo electrónico del destinatario y luego da clic en **Agregar**. ![Agregar modal de destinatario](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ Si tienes usuarios que quieran recibir reportes de facturación, puedes agregar
 Siempre debe existir una dirección designada como el destinatario principal. La dirección con esta designación no puede eliminarse hasta que se seleccione un destinatario primario.
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Debajo de "Administración de facturación", encuentra la dirección de correo electrónico que quieras configurar como el destinatario principal.
 1. A la derecha de la dirección de correo electrónico, utiliza el menú desplegable de "Editar", y da clic en **Marcar como principal**. ![Marcar destinatario principal](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### Eliminar un destinatario de las notificaciones de facturación
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Debajo de "Destinatarios de correo electrónico", encuentra la dirección de correo electrónico que quieres eliminar.
 1. Para la entrada del usuario en la lista, da clic en **Editar**. ![Editar destinatario](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. A la derecha de la dirección de correo electrónico, utiliza el menú desplegable de "Editar", y da clic en *Eliminar**. ![Eliminar destinatario](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![Eliminar destinatario](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. Revisa el mensaje de confirmación y luego da clic en **Eliminar**.
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index 9cc14cfb21..78a6bd649a 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### Comprar más almacenamiento y ancho de banda para una cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index 7bab825446..9608564713 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,11 +22,9 @@ topics:
 
 ### Subir de categoría la cantidad de asientos pagos de una organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -35,10 +33,8 @@ Después de agregar asientos, al método de pago archivado para la organización
 
 ### Bajar la categoría de la cantidad de asientos pagos de una organización a gratuita
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index e47aac8681..8e44ea29d4 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ Cuando subes de categoría una app, a tu método de pago se le cobra un monto pr
 ### Subir de categoría una app para tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ Cuando subes de categoría una app, a tu método de pago se le cobra un monto pr
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index d872493165..89b056799b 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 Puedes mejorar tu cuenta personal desde {% data variables.product.prodname_free_user %} a {% data variables.product.prodname_pro %} para obtener herramientas avanzadas de revisión de código en repositorios privados. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Junto a "
-{% data variables.product.prodname_free_user %}", da clic en **Mejorar**.
-  ![Botón para actualizar](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![Botón para actualizar](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ Puedes mejorar a tu organización desde {% data variables.product.prodname_free_
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ Si quisieras utilizar una cuenta empresarial con {% data variables.product.prodn
 
 Si quisieras que usuarios adicionales tengan acceso a los repositorios privados de {% data variables.product.prodname_team %} en tu organización, puedes comprar más plazas en cualquier momento.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ Si quisieras que usuarios adicionales tengan acceso a los repositorios privados
 
 {% data reusables.dotcom_billing.switch-legacy-billing %}Para obtener más información, consulta "[Acerca de los precios por usuario](/articles/about-per-user-pricing)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. A la derecha de tu nombre de plan, utiliza el menú desplegable de **Editar** y selecciona **Editar plan**. ![Menú desplegable de editar](/assets/images/help/billing/per-user-upgrade-button.png)
 6. A la derecha de "Herramientas avanzadas para equipos", da clic en **Mejorar ahora**. ![Botón de mejorar ahora](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index c2dce31e87..a9338f50f1 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ Cuando cancelas un cambio pendiente, tu suscripción no cambiará en tu próxima
 ### Ver y administrar cambios pendientes en tu suscripción de cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### Ver y administrar cambios pendientes en tu suscripción de organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index 5dc859a52a..a062355123 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### Ver el uso del almacenamiento y del ancho de banda para una cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Ver el uso del almacenamiento y del ancho de banda para una organización
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Leer más
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index 72040f576d..d1bf29a35c 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ También puedes ver los minutos de ejecución facturables para los jobs en una e
 Cualquiera puede ver el uso de {% data variables.product.prodname_actions %} para su cuenta de usuario personal.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ Cualquiera puede ver el uso de {% data variables.product.prodname_actions %} par
 
 Los propietarios de la organización y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_actions %} para una organización. Para organizaciones que gestione una cuenta empresarial, únicamente los propietarios de éstas pueden ver el uso de {% data variables.product.prodname_actions %} en la página de facturación de la misma.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index aff8937aec..f7a4c84a8c 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,24 +1,24 @@
 ---
 title: Visualizar tu uso de GitHub Advanced Security
-intro: 'Puedes ver y administrar el uso de tu licencia de {% data variables.product.prodname_GH_advanced_security %}.'
-permissions: 'Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
   free-pro-team: '*'
 ---
 
-Cada licencia de {% data variables.product.prodname_GH_advanced_security %} especifica una cantidad máxima de cuentas o de plazas que pueden utilizar estas características. Debes revisar de vez en cuando que tu uso esté dentro de la capacidad de tu licencia. Para obtener más información, consulta la sección "[Acerca del licenciamiento para la licencia empresarial de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)".
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
 
-### Visualizar y administrar tu uso de licencia de {% data variables.product.prodname_GH_advanced_security %} para tu cuenta empresarial
+### Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
 
-Puedes verificar cuántas plazas incluye tu licencia y cuántas de ellas se usan actualmente en la página de "Licenciamiento empresarial".
+You can check how many seats your license includes and how many of them are currently used.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-   La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Si te quedas sin plazas, la sección estará en rojo. Debes ya sea reducir tu uso de {% data variables.product.prodname_GH_advanced_security %} o comprar más plazas. Para obtener más información, consulta la sección "[Acerca del licenciamiento para la licencia empresarial de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)". ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de licenciamiento empresarial](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
-4. Opcionalmente, para ver un resumen detallado del uso por organización, en la barra lateral izquierda, haz clic en **Facturación**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) En la sección de "{% data variables.product.prodname_GH_advanced_security %}" puedes ver la cantidad de confirmantes y confirmantes únicos de cada organización. ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise.png)
+   La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Si te quedas sin plazas, la sección estará en rojo. Debes ya sea reducir tu uso de {% data variables.product.prodname_GH_advanced_security %} o comprar más plazas. Para obtener más información, consulta la sección "[Acerca de las licencias para {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)". ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de licenciamiento empresarial](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. Opcionalmente, para ver un resumen detallado del uso por organización, en la barra lateral izquierda, haz clic en **Facturación**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) En la sección de "{% data variables.product.prodname_GH_advanced_security %}" puedes ver la cantidad de confirmantes y confirmantes únicos de cada organización. ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
 5. Opcionalmente, haz clic en el nombre de una organización que te pertenezca para mostrar la configuración de seguridad y análisis para la organización. ![Organización que te pertenece en la sección de {% data variables.product.prodname_GH_advanced_security %} de la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
 6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index 4ea1d9a230..396aabf48a 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 Cualquiera puede ver el uso de {% data variables.product.prodname_registry %} para su cuenta de usuario personal.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ Cualquiera puede ver el uso de {% data variables.product.prodname_registry %} pa
 
 Los propietarios de la organización y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_registry %} para una organización. Para organizaciones que gestione una cuenta empresarial, únicamente los propietarios de éstas pueden ver el uso de {% data variables.product.prodname_registry %} en la página de facturación de la misma.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index 990feae26a..852492f2cc 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### Ver los recibos de tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index 5715b41219..aa143ef706 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### Encontrar la próxima fecha de facturación de tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Encontrar la próxima fecha de facturación de tu organización
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Leer más
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md
index 39b05ff309..068bf62fe7 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring identity and access management for your enterprise account
-intro: 'You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise.'
+title: Configurar la administración de accesos e identidades para tu cuenta empresarial
+intro: 'Puedes administrar el inicio de sesión único de SAML, aprovisionamiento de usuarios y sincronización de equipos para tu empresa.'
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 mapTopic: true
 versions:
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index 17e6dc8a54..a49af97bd0 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -36,5 +36,5 @@ Después de que desconectas tu suscripción de Azure de tu cuenta empresarial, t
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Debajo de "Suscripción de Azure", a la derecha de la ID de suscripción que quieres desconectar, haz clic en **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
+1. Debajo de "Suscripción de Azure", a la derecha de la ID de suscripción que quieres desconectar, haz clic en **{% octicon "trash" aria-label="The trash icon" %}**.
 1. Revisa el mensaje emergente y da clic en **Eliminar**.
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index b4df7cdae3..2a499db650 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -48,3 +48,19 @@ Puedes inhabilitar todos los flujos de trabajo de una empresa o configurar una p
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### Cnfigurar los permisos para el `GITHUB_TOKEN` para tu empresa
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+Puedes configurar los permisos predeterminados para del `GITHUB_TOKEN` en la configuración de tu empresa, organización o repositorio. Si eliges la opción restringida como lo predeterminado en la configuración de tu empresa, esto previene que puedas elegir más configuraciones permisivas en la configuración de tu organización o repositorio.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configurar los permisos predeterminados del `GITHUB_TOKEN`
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Debajo de **Permisos del flujo de trabajo**, elige si quieres que el `GITHUB_TOKEN` tenga permisos de lectura y escritura para todos los alcances o solo acceso de lectura para el alcance `contents`. ![Configurar los permisos del GITHUB_TOKEN para esta empresa](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. Da clic en **Guardar** para aplicar la configuración.
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md
index da9c0193ed..e6db787976 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..4e845ad54c
--- /dev/null
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: Restringir las notificaciones por correo electrónico para tu cuenta empresarial
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### Acerca de las restricciones para tu cuenta empresarial
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restringir las notificaciones por correo electrónico para tu cuenta empresarial
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..99e895dadf
--- /dev/null
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Acerca de la verificación de dominios
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index c1bc3fc882..f2f6e330af 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -20,6 +20,15 @@ Cuando habilitas el inicio de sesión único de SAML para tu cuenta empresarial,
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index abafef7f4d..0040b3cdac 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 Opcionalmente, puedes optar por agregar una descripción, una ubicación, un sitio web y una dirección de correo electrónico para tu organización y anclar repositorios importantes en la parte superior de la página.
 
-{% if currentVersion == "free-pro-team@latest" %}Para confirmar la identidad de tu organización y mostrar una insignia de "Verificado" en la página de perfil de la misma, debes verificar sus dominios con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Verificar el dominio de tu organización](/organizations/managing-organization-settings/verifying-your-organizations-domain)".
+{% if currentVersion == "free-pro-team@latest" %}Para confirmar la identidad de tu organización y mostrar una insignia de "Verificado" en la página de perfil de la misma, debes verificar sus dominios con {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![Muestra de página de perfil de una organización verificada](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index e858fdcd75..495b5b4ff1 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ Si seleccionas la opción, "Busy" (Ocupado), cuando las personas mencionan tu no
 
 Cuando participas en algunos programas, {% data variables.product.prodname_dotcom %} muestra automáticamente una insignia en tu perfil.
 
-| Insignia                                                        | Programa                                                             | Descripción                                                                                                                                                                                                                                                                                                                                                                                                            |
-| --------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Si eres el autor de cualquier confirmación en la rama predeterminada de un repositorio que se archivó en el programa del 2020 del Vaúl del Ártico, obtendrás una insignia de colaborador de {% data variables.product.prodname_arctic_vault %} en tu perfil. Para obtener más información sobre el programa, consulta la sección [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **Miembro del Programa de Desarrolladores**                          | Si eres un miembro registrado del Programa de Desarrolladores de GitHub, crear una app con la API de GitHub te otorgará una insignia de Miembro del Programa de Desarrolladores en tu perfil. Para obtener más información sobre el Programa de Desarrolladores de Github, consulta la sección [Desarrolladores de GitHub](/program/).                                                                                 |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **Patrocinador de GitHub**                                           | Si patrocinaste a un colaborador de código abierto a través de {% data variables.product.prodname_sponsors %} obtendrás una insignia de Patrocinador de GitHub en tu perfil. Para obtener más información, consulta la sección "[Patrocinar colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)".                                  |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                              | Si utilizas {% data variables.product.prodname_pro %} obtendrás una insignia de PRO en tu perfil. Para obtener más información acerca de {% data variables.product.prodname_pro %}, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)."                                                                                     |
+| Insignia                                                                                                                                      | Programa                                                             | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Icono de insignia de Contribuyente Helicóptero de Marte 2020](/assets/images/help/profile/badge-mars-2020-small.png)                        | **Contribuyente Helicóptero de Marte 2020**                          | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Al pasar el puntero del mouse sobre la insignia se te muestran varios de los repositorios con los que contribuiste, los cuales se utilizaron en la misión. Para obtener la lista completa de repositorios que te calificarán para la insignia, consulta la sección "[Lista de repositorios de calificación para la insignia de Contribuyente Helicóptero de Marte 2020](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)". |
+| ![Icono de insignia de Contribuyente de Vóbeda Ártica de Código](/assets/images/help/profile/badge-arctic-code-vault-small.png)               | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Si eres el autor de cualquier confirmación en la rama predeterminada de un repositorio que se archivó en el programa del 2020 del Vaúl del Ártico, obtendrás una insignia de colaborador de {% data variables.product.prodname_arctic_vault %} en tu perfil. Al pasar el puntero del mouse sobre la insignia se te muestran varios de los repositorios con los que contribuiste que fueron parte del programa. Para obtener más información sobre el programa, consulta la sección [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com).                                                                                                                                                                                       |
+| ![Icono de la insignia de Patrocinador de {% data variables.product.prodname_dotcom %}](/assets/images/help/profile/badge-sponsors-small.png) | **Patrocinador de {% data variables.product.prodname_dotcom %}**     | Si patrocinaste a un contribuyente de código abierto mediante {% data variables.product.prodname_sponsors %}, obtendrás una insignia de Patrocinador de {% data variables.product.prodname_dotcom %} en tu perfil. Si haces clic en la insignia, se tellevará a la pestaña de **Patrocinio** de tu perfil. Para obtener más información, consulta la sección "[Patrocinar colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)".                                                                                                                                                                                                                                          |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                                                   | **Miembro del Programa de Desarrolladores**                          | Si eres un miembro registrado del Programa de Desarrolladores de {% data variables.product.prodname_dotcom %}, al crear una app con la API de {% data variables.product.prodname_dotcom %}, obtendrás una insignia de Miembro del Programa de Desarrolladores en tu perfil. Para obtener más información sobre el Programa de Desarrolladores de {% data variables.product.prodname_dotcom %}, consulta la sección [Desarrollador de GitHub](/program/).                                                                                                                                                                                                                                                                                                     |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                                                          | **Pro**                                                              | Si utilizas {% data variables.product.prodname_pro %} obtendrás una insignia de PRO en tu perfil. Para obtener más información acerca de {% data variables.product.prodname_pro %}, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)."                                                                                                                                                                                                                                                                                                                                                                                                                             |
 
 ### Inhabilitar las insignias en tu perfil
 
-Puedes inhabilitar algunas de las insignias de los programas de {% data variables.product.prodname_dotcom %} en los cuales participas, incluyendo las insignias de PRO y de {% data variables.product.prodname_arctic_vault %}.
+Puedes inhabilitar algunas de las insignias para los programas de {% data variables.product.prodname_dotcom %} en los que estás participando, incluyendo aquellas de PRO, {% data variables.product.prodname_arctic_vault %} y Contribuyente Helicóptero de Marte 2020.
 
 {% data reusables.user_settings.access_settings %}
-2. Debajo de "Configuración del perfil", deselecciona la insignia que quieres inhabilitar. ![Casilla para dejar de mostrar una insignia en tu perfil](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. Debajo de "Configuración del perfil", deselecciona la insignia que quieres inhabilitar. ![Casilla para dejar de mostrar una insignia en tu perfil](/assets/images/help/profile/profile-badge-settings.png)
 3. Haz clic en **Update preferences (Actualizar preferencias)**.
 
 {% endif %}
 
+### Lista de repositorios que califican para la insignia de Contributente Helicóptero de Marte 2020
+
+Si creaste cualquiera de las confirmaciones presentes en el historial de confirmaciones de la etiqueta listada de uno o más de los repositorios siguientes, recibirás la insignia de contribuyente Helicóptero de Marte 2020 en tu perfil. La confirmación que creaste debe hacerse con una dirección de correo electrónico verificada y asociada con tu cuenta en el momento en que {% data variables.product.prodname_dotcom %} determine las contribuciones elegibles para que se te pueda atribuir. Los cambios futuros a los correos electrónicos verificados no tendrán efecto en la insignia. Creamos la lista con base en la información que recibimos del Laboratorio de Propulsión a Chorro de la NASA.
+
+| Repositorio de {% data variables.product.prodname_dotcom %}                   | Versión   | Etiqueta                                                                                                   |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.2       | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### Leer más
 
 - "[Acerca de tu perfil](/articles/about-your-profile)"
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
index 0044954385..58d90cc2bf 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -25,7 +25,7 @@ Las confirmaciones aparecerán en tu gráfico de contribución si cumplen **toda
   - En la rama predeterminada del repositorio
   - En la rama `gh-pages` (para los repositorios con sitios de proyecto)
 
-For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Para obtener más información sobre los sitios de proyecto, consulta la sección "[Acerca de las {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Asimismo, **al menos una** de las siguientes afirmaciones debe ser verdadera:
 - Eres un colaborador en el repositorio o eres miembro de la organización a la que pertenece el repositorio.
@@ -66,7 +66,7 @@ Las direcciones de correo electrónico generales, tales como `jane@computer.loca
 
 #### La confirmación no se hizo en la rama predeterminada o en la rama `gh-pages`
 
-Las confirmaciones solo se cuentan si se realizan en la rama predeterminada o en la rama `gh-pages` (para los repositorios con sitios de proyecto). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Las confirmaciones solo se cuentan si se realizan en la rama predeterminada o en la rama `gh-pages` (para los repositorios con sitios de proyecto). Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Si tus confirmaciones están en una rama que no es una rama predeterminada ni es la rama `gh-pages` y te gustaría que contaran para tus contribuciones, necesitarás realizar las siguientes acciones:
 - [Abre una solicitud de extracción](/articles/creating-a-pull-request) para obtener la fusión de tus cambios en la rama predeterminada o la rama `gh-pages`.
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index 3a81a014c5..6f227d0f48 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. Si deseas agregar una nueva dirección de correo electrónico para que sea tu dirección principal de correo electrónico, en "Add email address" (Agregar dirección de correo electrónico), escribe una nueva dirección de correo electrónico y haz clic en **Add** (Agregar). ![Botón Add another email address (Agregar otra dirección de correo electrónico)](/assets/images/help/settings/add_another_email_address.png)
 4. En "Primary email address" (dirección principal de correo electrónico), usa el menú desplegable para hacer clic en la dirección de correo electrónico que deseas establecer como tu dirección principal de correo electrónico, y haz clic en **Save** (Guardar). ![Botón Set as primary (Establecer como principal)](/assets/images/help/settings/set_as_primary_email.png)
 5. Para eliminar la dirección de correo electrónico antigua de tu cuenta, junto dicha dirección, da clic en
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}.
 {% if currentVersion == "free-pro-team@latest" %}
 6. Verifica tu nueva dirección principal de correo electrónico. Sin una dirección de correo electrónico verificada, no podrás utilizar todas las
 características de {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index 3f5d5f656f..cce5db816d 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -1,23 +1,20 @@
 ---
 title: Administrar la configuración de tu tema
-intro: 'Puedes administrar la vista que tienes de {% data variables.product.product_name %} si configuras una preferencia de tema que ya sea se acople a la configuración de tu sistema o siempre utilice el modo claro u oscuro.'
+intro: 'Puedes administrar la forma en que {% data variables.product.product_name %} te ve si configuras las preferencias de tema que ya sea siguen la configuración de tu sistema o siempre utilzian un modo claro u oscuro.'
 versions:
   free-pro-team: '*'
 topics:
   - Accounts
 ---
 
-{% note %}
-
-**Nota:** La configuración de tema se encuentra actualmente en beta y está sujeta a cambios.
-
-{% endnote %}
-
-Para obtener elecciones y flexibilidad en la forma y momento de utilizar {% data variables.product.product_name %}, puedes configurar los ajustes de tema para cambiar la forma en la que ves a {% data variables.product.product_name %}. Puedes elegir de entre dos temas, claro y oscuro, o puedes configurar a {% data variables.product.product_name %} para que siga la configuración de tu sistema. Algunos desarrolladores utilizan el tema oscuro por sus preferencias personales, para reducir el consumo de energía en algunos dispositivos, o para reducir el cansancio de los ojos en las condiciones de iluminación baja.
+Para obtener elecciones y flexibilidad en la forma y momento de utilizar {% data variables.product.product_name %}, puedes configurar los ajustes de tema para cambiar la forma en la que ves a {% data variables.product.product_name %}. Puedes elegir de entre los temas claros u oscuros o puedes configurar a {% data variables.product.product_name %} para que siga la configuración de tu sistema. Puede que quieras utilizar un tema oscuro para reducir el consumo de energía en algunos dispositivos, para reducir la fatiga ocular en condiciones de luz baja o porque te gusta más cómo se ve.
 
 {% data reusables.user_settings.access_settings %}
 1. En la barra lateral de configuración de usuario, da clic en **Apariencia**. ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png)
-1. Debajo de "Tema", selecciona una preferencia de tema. ![Botones radiales para la configuración de tema](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. Debajo de "Modo del tema", selecciona el menú desplegable y haz clic en una preferencia de tema. ![Menú desplegable debajo de "Modo del tema" para la selección de las preferencias del tema](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Haz clic en el tema que quieres usar.
+    - Si eliges un tema simple, haz clic en un tema. ![Botones radiales para elegir un tema simple](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - Si eliges seguir tu configuración de sistema, haz clic en un tema de día y de noche. ![Botones para elegir un tema para que se sincronice con la configuración del sistema](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### Leer más
 
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
index dc4babd9d3..fa8e38e6d5 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
@@ -32,7 +32,7 @@ El propietario del repositorio tiene control completo del repositorio. Adicional
 | {% if currentVersion == "free-pro-team@latest" %}Invitar colaboradores{% else %}Agregar colaboradores{% endif %}                                                                                                                        |                                                                                                                                                                                                                                                                                                                                 |
 | "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)"                                                                           |                                                                                                                                                                                                                                                                                                                                 |
 | Cambiar la visibilidad del repositorio                                                                                                                                                                                                  | "[Configurar la visibilidad del repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %}
-| Limitar las interacciones con el repositorio                                                                                                                                                                                            | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Limitar las interacciones con el repositorio                                                                                                                                                                                            | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Renombrar una rama, incluyendo la rama predeterminada                                                                                                                                                                                   | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación                                                                                                                               | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)"                                                                                                                                                                                                                                 |
@@ -70,10 +70,10 @@ Los colaboradores también pueden realizar las siguientes acciones.
 
 | Acción                                                                                                         | Más información                                                                                                                                                                                                                                                                                                |
 |:-------------------------------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Bifurcar el repositorio                                                                                        | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Bifurcar el repositorio                                                                                        | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Renombrar una rama diferente a la predeterminada                                                               | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
-| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio | <ul><li>"[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)"</li><li>"[Comentar en una solilcitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                                                                      |
+| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio | <ul><li>"[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)"</li><li>"[Comentar en una solilcitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Administrar los comentarios perjudiciales](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                                                                      |
 | Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio                                       | "[Administrar tu trabajo con las propuestas](/github/managing-your-work-on-github/managing-your-work-with-issues)"                                                                                                                                                                                             |
 | Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio                       | "[Etiquetar las propuestas y solicitudes de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)"                                                                                                                                                                                  |
 | Administrar hitos para las propuestas y solicitudes de cambios en el repositorio                               | "[Crear y editar hitos para propuestas y solicitudes de extracción](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)"                                                                                                                                        |
diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index fe7c922522..1a53e4e8ce 100644
--- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ Aunque se borren las bifurcaciones de los repositorios privados cuando se elimin
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. A la derecha del colaborador que quieres eliminar, da clic en
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
   ![Botón para eliminar un colaborador](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). ![Pestaña Collaborators (Colaboradores)](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md b/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md
index ffb64ee63f..a9b2b67c83 100644
--- a/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/es-ES/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,6 +9,8 @@ topics:
   - Legal
 ---
 
+_Estos términos aplican a los clientes de 1)GitHub.com (no-empresariales) que hayan aceptado las Condiciones Corporativas de Servicio y 2) los clientes empresariales que licenciaron el servicio antes del 4 de enero de 2021. Los clientes empresariales que compraron productos o servicios posterior a esta fecha se dirigirán a https://github.com/enterprise-legal para encontrar las condiciones actuales._
+
 GRACIAS POR ELEGIR GITHUB PARA CUBRIR LAS NECESIDADES COMERCIALES DE SU EMPRESA. LEE ESTE ACUERDO CUIDADOSAMENTE YA QUE RIGE EL USO DE LOS PRODUCTOS (COMO SE DEFINEN A CONTINUACIÓN), A MENOS QUE GITHUB HAYA CELEBRADO UN ACUERDO POR ESCRITO POR SEPARADO CON EL CLIENTE PARA DICHO PROPÓSITO. AL HACER CLIC EN EL BOTÓN "ACEPTO" O EN UN BOTÓN SIMILAR O AL UTILIZAR CUALQUIERA DE LOS PRODUCTOS, EL CLIENTE ACEPTA TODOS LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO. SI EL CLIENTE ESTÁ CELEBRANDO ESTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA PERSONA MORAL, EL CLIENTE REPRESENTA QUE TIENE LA AUTORIDAD LÉGAL DE VINCULAR A LA EMPRESA U OTRAS PERSONAS MORALES AL PRESENTE ACUERDO.
 
 ### Términos de servicio corporativos de GitHub
@@ -111,7 +113,7 @@ El Cliente es responsable de: (i) todo el Contenido publicado y la actividad que
 En algunas situaciones, pueden aplicarse términos de terceros al uso del Cliente de GitHub. Por ejemplo, el Cliente puede ser miembro de una Organización con sus propios términos o acuerdos de licencia; el Cliente puede descargar una aplicación que se integre con el Servicio; o el Cliente puede usar el Servicio para autenticarse a otro servicio. Aunque este Acuerdo es el acuerdo completo de GitHub con el Cliente, los términos de otras partes rigen sus relaciones con el Cliente.
 
 #### 5. Feriado en Términos del Gobierno federal de los EE.⁰UU
-Si el cliente es una entidad gubernamental de los EE.UU. o accede o utiliza de otra manera el servicio en calidad de gobierno, aplicará la [Enmienda del Gobierno Federal de los EE.UU.](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users), y el cliente acordará con estas disposiciones.
+Si el cliente es una entidad gubernamental de los EE.UU. o accede o utiliza de otra manera el servicio en calidad de gobierno, aplicará la [Enmienda del Gobierno Federal de los EE.UU., ](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users)y el cliente acordará con estas disposiciones.
 
 #### 6. Acuerdo sobre los Niveles de Servicio de Enterprise Cloud
 El compromiso de tiempo activo trimestral de Github para Github Enterprise Cloud se proporciona en el [Acuerdo de Nivel de Servicio Empresarial](/github/site-policy/github-enterprise-service-level-agreement). Si el cliente se registra para GitHub Enterprise Cloud, entonces éste será acreedor a un crédito de servicio en caso de que GitHub no cumpla con sus niveles de servicio.
@@ -125,7 +127,7 @@ El uso del cliente de los Productos no debe violar ninguna ley aplicable, incluy
 El uso que el Cliente dé al servicio deberá cumplir con las [Políticas de Uso Aceptado de GitHub](/articles/github-acceptable-use-policies) y los [Lineamientos de la Comunidad de GitHub](/articles/github-community-guidelines). El Cliente no debe usar el Servicio en ninguna jurisdicción si contiene Contenidos o actividades ilegales, obscenos, ofensivos o fraudulentos, tales como promover o causar daño, vulnerar la integridad o la seguridad de una red o sistema o interferir en ellos, evadir filtros, enviar mensajes no solicitados, abusivos o engañosos, virus o códigos perjudiciales, o socavar los derechos de terceros.
 
 #### 3. Privacidad
-The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Cualquier persona, entidad o servicio que recolecte datos del Servicio debe cumplir con la Declaración de Privacidad de GitHub, en particular en lo que se refiere a la recopilación de datos personales de los usuarios (como se define en la Declaración de Privacidad de GitHub). Si el Cliente recopila cualquier Información personal del usuario proveniente de GitHub, el Cliente solamente la usará para el propósito por el cual el Usuario externo lo autorizó. El Cliente asegurará razonablemente dicha Información personal y el Cliente responderá de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de Usuarios externos.
+La [Declaración de Privacidad de GitHub](/articles/github-privacy-statement) y el [Acuerdo de Protección de Datos de GitHub](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) proporcinan una notificación detallada de las prácticas de datos y privacidad de GitHub, así como de sus obligaciones de seguridad y procesamiento con respecto a los Datos personales de los Clientes. Cualquier persona, entidad o servicio que recolecte datos del Servicio debe cumplir con la Declaración de Privacidad de GitHub, en particular en lo que se refiere a la recopilación de datos personales de los usuarios (como se define en la Declaración de Privacidad de GitHub). Si el Cliente recopila cualquier Información personal del usuario proveniente de GitHub, el Cliente solamente la usará para el propósito por el cual el Usuario externo lo autorizó. El Cliente asegurará razonablemente dicha Información personal y el Cliente responderá de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de Usuarios externos.
 
 ### D. Responsabilidad del Contenido; Propiedad; Derechos de la licencia
 
diff --git a/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
index 07ed70c7b6..e618252756 100644
--- a/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
+++ b/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Data Protection Agreement (Non-Enterprise Customers)
+title: Contrato de protección de datos de GitHub (para clientes no empresariales)
 redirect_from:
   - /github/site-policy/github-data-protection-addendum
   - /github/site-policy-deprecated/github-data-protection-addendum
@@ -7,11 +7,11 @@ versions:
   free-pro-team: '*'
 ---
 
-_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._
+_Estas condiciones aplican a los clientes no empresariales. También aplican a los clientes empresariales que licenciaron ofertas de GitHub antes del 4 de enero de 2021. Los clientes empresariales que compraron las ofertas de GitHub después de esta fecha se redirigirán a https://www.github.com/enterprise-legal para ver las condiciones actuales._
 
 ## INTRODUCCIÓN
 
-The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products.
+Las partes concuerdan en que el Acuerdo de protección de datos de GitHub (para clientes no empresariales) (**"DPA"**) enuncia sus obligaciones con respecto al procesamiento de los Datos Personales del cliente en conexión con el servicio hospedado de GitHub Enterprise Cloud (el**"Servicio"**). GitHub se compromete en este DPA con todos los clientes no empresariales que utilicen el Servicio. Las condiciones por separado, incluyendo las condiciones de privacidad diferentes, rigen el uso del cliente para los productos ajenos a GitHub.
 
 En caso de que exista cualquier conflicto o inconsistencia entre la DPA y cualquier otra condición en el acuerdo del cliente con Github, la DPA deberá prevalecer. Las disposiciones de la DPA sustituyen cualquier disposición que entre en conflicto con la Declaración de Privacidad de GitHub que pudiera aplicarse de otra forma al procesamiento de los Datos Personales del Cliente como se define en el presente documento. Para mayor claridad, en apego a la Cláusula 10 de las Cláusulas Contractuales Estándar en el Adjunto 1, las Cláusulas Contractuales Estándar prevalecerán sobre cualquier otra condición en la DPA.
 
@@ -90,7 +90,7 @@ e.  *Las obligaciones y los derechos del Cliente* están establecidos en el Acue
 Tomando en cuenta las tecnologías más actuales, los costos de implementación, y la naturaleza, alcance, contexto y propósito de procesamiento, así como el riesgo de variar la probabilidad y severidad de los derechos y libertades de las personas naturales, GitHub implementará medidas técnicas y organizacionales adecuadas para garantizar un nivel de seguridad adecuado para los riesgos, tales como aquellas contra la destrucción accidental o ilegal, o contra la pérdida, alteración, o contra el acceso o divulgación no autorizados que se presenten debido al Procesamiento de los Datos. GitHub supervisará regularmente el cumplimiento de estas medidas y continuará tomando las debidas salvaguardias durante la vigencia del Acuerdo.
 
 #### 4.2 Respuesta a Incidentes y Notificación de Filtración.
-GitHub will comply with Applicable Data Protection Laws.
+GitHub cumplirá con las Leyes de Protección de Datos Aplicables.
 
 #### 4.3 Personal de GitHub.
 GitHub representa y garantiza que tomará los pasos razonables para asegurarse de que todo su personal que maneje Datos Protegidos haya acordado mantener dichos datos como confidenciales y haya recibido capacitación adecuada para cumplir con esta Adenda y con las Leyes de Protección de Datos Aplicables.
@@ -326,7 +326,7 @@ Exportador de los datos: El cliente es el exportador de los datos.
 
 Sin embargo, ya que el importador de los dtos proporciona servicios de almacenamiento y no controla las categorías de los datos que almacena, el exportador de los datos podría elegir transferir las categorías especiales de los datos. Por consiguiente, el exportador de los datos es el único responsable de garantizar que cumple con todas las obligaciones impuestas por las leyes y regulaciones aplicables relacionadas con la recolección y procesamiento de cualquier categoría de datos, incluyendo el obtener el consentimiento explícito del titular de los datos antes de procesar datos personales sensibles.
 
-**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontratistas: De acuerdo con la DPA, el importador de los datos podrá contratar a otras compañías para proporcionar servicios limitados en nombre del importador de los datos, tales como proporcionar soporte al cliente. Cualquier subcontratista de este tipo tendrá permiso de obtener los Datos Personales del Cliente únicamente para entregar los servicios para los cuales lo contrató el importador de los mismos, y se les prohibe utilizar los Datos Personales del Cliente para cualquier otro propósito.
+**Operaciones de procesamiento:** Los datos personales transferidos estarán sujetos a las siguientes actividades de procesamiento básico: GitHub utiliza los datos pesonales para los propósitos limitados que se establecen en la Declaración de Privacidad de GitHub, disponible en [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), y en la sección de "Procesamiento de Datos" de la DPA. Subcontratistas: De acuerdo con la DPA, el importador de los datos podrá contratar a otras compañías para proporcionar servicios limitados en nombre del importador de los datos, tales como proporcionar soporte al cliente. Cualquier subcontratista de este tipo tendrá permiso de obtener los Datos Personales del Cliente únicamente para entregar los servicios para los cuales lo contrató el importador de los mismos, y se les prohibe utilizar los Datos Personales del Cliente para cualquier otro propósito.
 
 ### Apéndice 2 para las Cláusulas Contractuales Estándar
 Descripción de las medidas de seguridad técnicas y organizacionales implementadas por el importador de los datos de acuerdo con las Cláusulas 4(d) y 5(c):
@@ -335,7 +335,7 @@ Descripción de las medidas de seguridad técnicas y organizacionales implementa
 
 **2. Contacto de Privacidad de los Datos.** El director de privacidad para el importador de los datos puede contactarse en la siguiente dirección: GitHub, Inc. Atención: Privacidad 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA
 
-**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction.
+**3. Las medidas técnicas y de organización.** El importador de datos implementó y mantendrá las medidas organizacionales y técnicas adecuadas, los controles internos y las rutinas de seguridad informática que se necesitan para proteger los Datos Personales del Cliente contra la pérdida accidental, destrucción, alteración, divulgación o acceso no autorizados, o una destrucción ilegal.
 
 La Firma de GitHub, Inc. se muestra a continuación.
 
diff --git a/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
index 1206982297..6776e9f3bb 100644
--- a/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
+++ b/translations/es-ES/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insights y la protección de datos para tu organización
 intro: '{% data variables.product.prodname_insights %} analiza tus datos de {% data variables.product.prodname_ghe_server %}. Estos datos podrían incluir datos personales de individuos en tu organización quienes podrían tener derecho a entender cómo se utilizan éstos.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
   - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
@@ -14,8 +13,6 @@ topics:
   - Legal
 ---
 
-Para obtener más información acerca de las condiciones normativas de {% data variables.product.prodname_insights %}, consulta tu contrato de suscripción de {% data variables.product.prodname_ghe_one %}.
-
 Para evitar las dudas, ninguna información anterior deberá considerarse como asesoría legal proporcionada por {% data variables.product.prodname_dotcom %}. Eres responsable de asegurar tu propio análisis legal de la información aquí proporcionada y de dar cumplimiento a las leyes de protección de privacidad y datos. Dependerá de ti si quieres utilizar {% data variables.product.prodname_insights %} para procesar los datos de tus usuarios y empleados, y si lo haces, serás el único responsable para ejecutar dicho procesamiento en cumplimiento con las leyes aplicables.
 
 ### Los roles y responsabilidades de la organización
diff --git a/translations/es-ES/content/github/site-policy/github-privacy-statement.md b/translations/es-ES/content/github/site-policy/github-privacy-statement.md
index 0fbdeab56e..246331d98a 100644
--- a/translations/es-ES/content/github/site-policy/github-privacy-statement.md
+++ b/translations/es-ES/content/github/site-policy/github-privacy-statement.md
@@ -64,7 +64,7 @@ Necesitamos cierta información básica al momento de creación de la cuenta. Cu
 ##### Información de Pago
 Si te registras para una Cuenta paga, envías fondos a través del Programa de patrocinadores de GitHub o compras una aplicación en el Mercado GitHub, recopilamos tu nombre completo y la información de la tarjeta de crédito o la información de PayPal. Ten en cuenta que GitHub no procesa ni almacena tu información de tarjeta de crédito o información de PayPal, pero sí lo hace nuestro procesador de pago subcontratado.
 
-Si detallas y vendes una aplicación en el [Mercado GitHub](https://github.com/marketplace), te solicitamos la información de tu banco. Si recabas fondos a través del [Programa de Patrocinadores de GitHub](https://github.com/sponsors), necesitamos algo de [información adicional](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) mediante el proceso de registro para que participes y recibas los fondos a través de estos servicios y para propósitos de cumplimiento.
+Si detallas y vendes una aplicación en el [Mercado GitHub](https://github.com/marketplace), te solicitamos la información de tu banco. Si recabas fondos a través del [Programa de Patrocinadores de GitHub](https://github.com/sponsors), necesitamos algo de [información adicional](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) mediante el proceso de registro para que participes y recibas los fondos a través de estos servicios y para propósitos de cumplimiento.
 
 ##### Información de perfil
 Puedes decidir proporcionarnos más información para tu Perfil de cuenta, como tu nombre completo, un avatar que puede incluir una fotografía, tu biografía, tu ubicación, tu empresa y una URL a un sitio web de terceros. Esta información puede incluir Información personal del usuario. Ten en cuenta que tu información de perfil puede ser visible para otros Usuarios de nuestro Servicio.
diff --git a/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md
index d6ec42e898..01178b32ca 100644
--- a/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md
+++ b/translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md
@@ -13,7 +13,7 @@ topics:
   - Legal
 ---
 
-Effective date: **April 2, 2021**
+Fecha de entrada en vigor: **2 de abril de 2021**
 
 GitHub ofrece una gran cantidad de transparencia en cuanto a cómo usamos tus datos, cómo recopilamos tus datos y con quién los compartimos. Para este propósito, proporcionamos esta página, la cual detalla [nuestros subprocesadores](#github-subprocessors) y cómo utilizamos las [cookies](#cookies-on-github).
 
diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index f79f64937f..38e57cab0f 100644
--- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -1,90 +1,76 @@
 ---
-title: About the dependency graph
-intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.'
+title: Acerca del gráfico de dependencias
+intro: 'Información detallada sobre la gráfica de dependencias, el ecosistema con el que es compatible, y sobre cómo determina de qué paquetes depende un repositorio.'
 versions:
   enterprise-server: <=2.22
 topics:
   - Repositories
 ---
 
-### Dependency graph availability
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+### Disponibilidad de la gráfica de dependencias
+
+La gráfica de dependencias está disponible para cada repositorio que define las dependencias en un ecosistema de paquetes compatible utilizando un formato de archivos compatible.
 
 {% data reusables.repositories.enable-security-alerts %}
 
-### About the dependency graph
+### Acerca del gráfico de dependencias
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+La gráfica de dependencias es un resumen de los archivos de bloqueo y de manifiesto que se almacenan en un repositorio. Este muestra las dependencias, es decir, los paquetes y ecosistemas de los cuales depende, para cada repositorio. {% data variables.product.prodname_ghe_server %} no calcula información alguna sobre los dependientes, repositorios y paquetes que dependen de un repositorio.
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+Cuando cargas una confirmación a {% data variables.product.product_name %}, la cual cambia o agrega un archivo de manifiesto o de bloqueo compatible a la rama predeterminada, la gráfica de dependencias se actualiza automáticamente. Para obtener más información sobre los ecosistemas y archivos de manifiesto compatibles, consulta la sección "[Ecosistemas de paquetes compatibles](#supported-package-ecosystems)" que se encuentra más adelante.
 
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+### Dependencias que se incluyen
 
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+La gráfica de dependencias incluye todas las dependencias de un repositorio que se describan en los archivos de manifiesto y de bloqueo o sus equivalentes para los ecosistemas compatibles. Esto incluye:
 
-### Dependencies included
+- Las dependencias directas que se definen explícitamente en el archivo de manifiesto o de bloqueo
+- Las dependencias indirectas de estas dependencias directas, también conocidas como dependencias transitorias o sub-dependencias
 
-The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
+La gráfica de dependencias identifica las dependencias indirectas.
 
-- Direct dependencies, that are explicitly defined in a manifest or lock file
-- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+### Utiizar la gráfica de dependencias
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+Puedes utilizar la gráfica de dependencias para:
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
+- Explora los repositorios de los cuales depende tu código. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)".
+- Ver y actualizar las dependencias vulnerables de tu repositorio. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".
 
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+### Habilitar la gráfica de dependencias
 
-### Using the dependency graph
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}Si la gráfica de dependencias no se encuentra disponible en tu sistema, tu administrador de sitio puede habilitarla junto con las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-You can use the dependency graph to:
-
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
-
-### Enabling the dependency graph
-
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
-
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Si la gráfica de dependencias no está disponible en tu sistema, tu administrador de sitio puede habilitarla, así como puede habilitar las alertas de seguridad. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+Cuando la gráfica de dependencias se habilita por primera vez, cualquier manifiesto y archivo de bloqueo para los ecosistemas compatibles se pasarán de inmediato. La gráfica se llena en cuestión de minutos habitualmente, pero esto puede tardar más para los repositorios que tengan muchas dependencias. Una vez que se habilitan, la gráfica se actualiza automáticamente con cada subida al repositorio.
 
-### Supported package ecosystems
+### Ecosistemas de paquetes compatibles
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+Los formatos recomendados definen explícitamente qué versiones se utilizan para todas las dependencias directas e indirectas. Si utilizas estos formatos, tu gráfica de dependencias será más precisa. También refleja la configuración de la compilación actual y habilita a la gráfica de dependencias para reportar las vulnerabilidades tanto en las dependencias directas como en las indirectas.
 
-| Package manager | Languages | Recommended formats | All supported formats |
-| --- | --- | --- | ---|
-| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| 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.lock`, `setup.py`* |
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+Los ecosistemas que se listan a continuación son compatibles con la gráfica de dependencias y con {% if currentVersion == "enterprise-server@2.22" %}las {% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %}.
+
+| Administración de paquetes | Idiomas                          | Formatos recomendados                                  | Todos los formatos compatibles                                            |
+| -------------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
+| Composer                   | PHP                              | `composer.lock`                                        | `composer.json`, `composer.lock`                                          |
+| `dotnet` CLI               | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+| 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`*                |
+| RubyGems                   | Ruby                             | `Gemfile.lock`                                         | `Gemfile.lock`, `Gemfile`, `*.gemspec`                                    |
+| Yarn                       | JavaScript                       | `yarn.lock`                                            | `package.json`, `yarn.lock`                                               |
 
 {% note %}
 
-**Note:** 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.
+**Nota:** Si listas tus dependencias de Python dentro de un archivo `setup.py`, es probable que no podamos analizar y listar cada una de las dependencias en tu proyecto.
 
 {% endnote %}
 
-### Further reading
+### Leer más
 
-- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Gráfica de dependencias](https://en.wikipedia.org/wiki/Dependency_graph)" en Wikipedia
+- "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
diff --git a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index 8fd065b78d..ccbabc1bca 100644
--- a/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/es-ES/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -7,29 +7,20 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### Visualizar la gráfica de dependencias
 
 {% data reusables.repositories.enable-security-alerts %}
 
-La gráfica de dependencias muestra las dependencias{% if currentVersion == "free-pro-team@latest" %} y los dependientes{% endif %} de tu repositorio. Para obtener más información acerca de la detección de dependencias y de cuáles ecosistemas son compatibles, consulta la sección [Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
+La gráfica de dependencias muestra las dependencias de tu repositorio. Para obtener más información acerca de la detección de dependencias y de cuáles ecosistemas son compatibles, consulta la sección [Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. Opcionalmente, debajo de "Gráfica de dependencias", da clic en **Dependientes**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### Vista de dependencias
 
-{% if currentVersion == "free-pro-team@latest" %}
-Las dependencias se agrupan por ecosistema. Puedes expandir una dependencia para ver a su vez sus dependencias. Para las dependencias de los repositorios públicos que se hospedan en
-{% data variables.product.product_name %}, también puedes dar clic en la dependencia para ver el repositorio. Las dependencias en los repositorios privados, paquetes privados, o archivos no reconocidos se muestran en texto simple.
-
-Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a {% data variables.product.prodname_dependabot_alerts %}.
-
-![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
 Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a las
 {% data variables.product.prodname_dependabot_alerts %}.
@@ -57,61 +48,8 @@ Se listará cualquier dependencia directa e indirecta que se especifique en los
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### Vista de dependientes
-
-Para los repositorios públicos, la vista de dependientes muestra cómo otros repositorios utilizan este repositorio. Para mostrar únicamente los repositorios que contienen una biblioteca en un administrador de paquetes, da cilc en **CANTIDAD de paquetes** inmediatamente sobre la lista de repositorios dependientes. La cantidad de dependientes es aproximada y podría no siempre empatar con los dependientes listados.
-
-![Gráfica de dependientes](/assets/images/help/graphs/dependents_graph.png)
-
-### Habilitar e inhabilitar la gráfica de dependencias para un repositorio privado
-
-Los administradores del repositorio pueden habilitar o inhabilitar la gráfica de dependencias para los repositorios privados.
-
-También puedes habilitar o inhabilitar la gráfica de dependencias para todos los repositorios que pertenecen a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o la sección "[Administrar la configuración de seguridad y análisis para tu organización](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)".
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Lee los mensajes sobre el otorgar acceso de solo lectura a {% data variables.product.product_name %} para los datos del repositorio para así habilitar la gráfica de dependencias, posteriormente, da clic en **Habilitar** junto a "Gráfica de Dependencias". ![Botón de "Habilitar" para la gráfica de dependencias](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-Puedes inhabilitar la gráfica de dependencias en cualquier momento si das clic en **Inhabilitar** junto a "Gráfica de Dependencias" en la pestaña de Seguridad & análisis.
-
-### Cambiar el paquete "Utilizado por"
-
-Si está habilitada la gráfica de dependencias y tu repositorio contiene un paquete que se publica en un ecosistema de paquetes compatible, {% data variables.product.prodname_dotcom %} muestra una sección de "Utilizado por" en la barra lateral de la pestaña de **Código** de tu repositorio. Para obtener más información sobre los ecosistemas de paquetes compatibles, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
-
-La sección de "Utilizado por" muestra la cantidad de referencias públicas al paquete que se encontró, y muestra los avatares de algunos de los propietarios de los proyectos dependientes.
-
-![Sección de "Utilizado por" en la barra lateral](/assets/images/help/repository/used-by-section.png)
-
-Dar clic en cualquier elemento de esta sección te lleva a la pestaña de **Dependientes** de la gráfica de dependencias.
-
-La sección de "Utilizado por" representa un solo paquete del repositorio. Si tienes permisos de administrador en un repositorio que contenga paquetes múltiples, puedes elegir qué paquete reporesenta la sección de "Utilizado por".
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Debajo de "Configurar las caracetrísticas de análisis y seguridad"; da clic en el menú desplegable dentro de la sección "Contador de utilizado por" y elige un paquete. ![Elige un paquete de "Utilizado por"](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### Solución de problemas del gráfico de dependencias
 
 Si tu gráfica de dependencias está vacía, puede que haya un problema con el archivo que contiene tus dependencias. Revisa el archivo para asegurarte de que tiene el formato correcto para el tipo de archivo.
 
-{% if currentVersion == "free-pro-team@latest" %}
-Si este archivo tiene el formato correcto, entonces revisa su tamaño. La gráfica de dependencias ignora los archivos bloqueados y de manifiesto individuales que tengan más de 0.5 Mb de tamaño, a menos de que seas un
-usuario de {% data variables.product.prodname_enterprise %}. Este procesa hasta 20 archivos de manifiesto o de bloqueo por repositorio predeterminadamente, así que puedes dividir las dependencias en archivos más pequeños en los subdirectorios del repositorio.{% endif %}
-
 Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omiten de la gráfica de dependencias y no podrán verificar si hay dependencias vulnerables.
-
-### Leer más
-
-- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "
-Entender cómo {% data variables.product.product_name %} utiliza y protege tus datos" </p> 
-  
-  {% endif %}</li> </ul>
diff --git a/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index a4ff59b087..6a6d876aa1 100644
--- a/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: Acerca del Soporte prémium de GitHub para GitHub Enterprise Cloud
-intro: '{% data variables.contact.premium_support %} es una oferta de soporte suplementaria y pagada para los clientes de {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_one %}.'
+intro: '{% data variables.contact.premium_support %} es una oferta de soporte remunerado, adicional para clientes de {% data variables.product.prodname_ghe_cloud %}.'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
diff --git a/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md b/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md
index 0bda2e3947..2e3599f55a 100644
--- a/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md
+++ b/translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md
@@ -11,7 +11,7 @@ topics:
 
 Si tu cuenta utiliza un producto pagado de {% data variables.product.prodname_dotcom %}, puedes contactar directamente a {% data variables.contact.github_support %}. Si tu cuenta utiliza {% data variables.product.prodname_free_user %} para cuentas organizacionales y de usuario, puedes contactar a {% data variables.contact.contact_support %} para reportar problemas con la cuenta, seguridad y abuso. Para obtener más informaciónm, consulta la sección "[Acerca de GitHub Support](/github/working-with-github-support/about-github-support)".
 
-If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)."
+Si no tienes una cuenta empresarial, por favor, utiliza el {% data variables.contact.enterprise_portal %} para emitir tickets. Para obtener más información sobre las cuentas empresariales, consulta la sección "[Acerca de las cuentas empresariales](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)".
 
 ### Emitir un ticket utilizando el {% data variables.contact.support_portal %}
 
diff --git a/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md
index 45e2343eb4..58f43639e0 100644
--- a/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/es-ES/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ Para obtener información sobre cómo crear vínculos, consulta "[Sintaxis de es
 
 ### Propuestas y solicitudes de extracción
 
-Dentro de las conversaciones en {% data variables.product.product_name %}, las referencias a las propuestas y solicitudes de extracción se convierten automáticamente en vínculos acortados. Para obtener más información, consulta "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)".
+Dentro de las conversaciones en {% data variables.product.product_name %}, las referencias a las propuestas y solicitudes de extracción se convierten automáticamente en vínculos acortados.
 
 {% note %}
 
diff --git a/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index 3b5f614c8d..cf27a5a9d0 100644
--- a/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/es-ES/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -23,7 +23,7 @@ Para crear un encabezado, agrega uno a seis símbolos `#` antes del encabezado d
 
 ### Estilo de texto
 
-Puedes indicar énfasis con texto en negrita, cursiva o tachado.
+Puedes indicar énfasis con texto en negritas, itálicas o tachadas en los campos de comentario y archivos `.md`.
 
 | Estilo                       | Sintaxis          | Atajo del teclado   | Ejemplo                                         | Resultado                                     |
 | ---------------------------- | ----------------- | ------------------- | ----------------------------------------------- | --------------------------------------------- |
@@ -205,6 +205,10 @@ Los adjuntos de contenido no se mostrarán para las URL que son parte de un enla
 
 Para obtener más información sobre el desarrollo de una {% data variables.product.prodname_github_app %} que utilice adjuntos de contenido, consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments)".
 
+### Cargar activos
+
+Puedes cargar activos como imágenes si las arrastras y sueltas, las seleccionas de un buscador de archivos o si las pegas. Puedes cargar activos a las propuestas, solicitudes de cambios, comentarios y archivos `.md` en tu repositorio.
+
 ### Usar emojis
 
 Puedes agregar emojis a tu escritura al escribir `:EMOJICODE:`.
diff --git a/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index c55711b7de..a43cb5e62b 100644
--- a/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/es-ES/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### Resaltado de la sintaxis
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 Puedes agregar un identificador opcional de idioma para habilitar el resaltado de la sintaxis en tu bloque de código cercado.
 
diff --git a/translations/es-ES/content/github/writing-on-github/creating-gists.md b/translations/es-ES/content/github/writing-on-github/creating-gists.md
index 8bcb104b48..7d92d5a631 100644
--- a/translations/es-ES/content/github/writing-on-github/creating-gists.md
+++ b/translations/es-ES/content/github/writing-on-github/creating-gists.md
@@ -33,7 +33,7 @@ Si el administrador de tu sitio ha inhabilitado el modo privado, también puedes
 Recibirás una notificación si:
 - Seas el autor de un gist.
 - Alguien te mencione en un gist.
-- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
+- Puedes suscribirte a un gist haciendo clic en **Suscribir** en la parte superior de cualquier gist.
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
@@ -55,14 +55,14 @@ Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran co
 
 ### Crear un gist
 
-Follow the steps below to create a gist.
+Sigue estos pasos para crear un gist.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 {% note %}
 
 También puedes crear un gist si utilizas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" en el {% data variables.product.prodname_cli %}.
 
-Alternatively, you can drag and drop a text file from your desktop directly into the editor.
+Como alternativa, puedes arrastrar y soltar un archivo de texto desde tu escritorio directamente en el editor.
 
 {% endnote %}
 {% endif %}
@@ -71,7 +71,7 @@ Alternatively, you can drag and drop a text file from your desktop directly into
 2. Dirígete a tu {% data variables.gists.gist_homepage %}.
 3. Escribe una descripción opcional y un nombre para tu gist. ![Descripción del nombre del gist](/assets/images/help/gist/gist_name_description.png)
 
-4. Type the text of your gist into the gist text box. ![Cuadro de texto para el gist](/assets/images/help/gist/gist_text_box.png)
+4. Teclea el texto de tu gist en la caja de texto de este. ![Cuadro de texto para el gist](/assets/images/help/gist/gist_text_box.png)
 
 5. Opcionalmente, para crear un gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}, da clic en {% octicon "triangle-down" aria-label="The downwards triangle icon" %} y luego en **Crear gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}**. ![Menú desplegable para seleccionar la visibilidad de un gist]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
 
diff --git a/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 7447823706..a457cb2caf 100644
--- a/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ Campos de tipo de retorno:
 
 ## Buscar
 
-El debate puede devolverse desde el campo `search` de nivel superio. Para buscar un debate, especifica el `type` como `DISCUSSION`. El tipo `SearchResultItemConnection` tiene un campo de `discussionCount` para reportar la cantidad de debates devueltos y el tipo `Discussion` se agrega a la unión `SearchResultItem`. Para obtener más información, consulta la sección ["Consultas](/graphql/reference/queries#searchresultitemconnection)".
+El debate puede devolverse desde el campo `search` de nivel superio. Para buscar un debate, especifica el `type` como `DISCUSSION`. El tipo `SearchResultItemConnection` tiene un campo de `discussionCount` para reportar la cantidad de debates devueltos y el tipo `Discussion` se agrega a la unión `SearchResultItem`. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/es-ES/content/graphql/overview/breaking-changes.md b/translations/es-ES/content/graphql/overview/breaking-changes.md
index cd852d2c1c..bdc30f0179 100644
--- a/translations/es-ES/content/graphql/overview/breaking-changes.md
+++ b/translations/es-ES/content/graphql/overview/breaking-changes.md
@@ -27,7 +27,7 @@ Anunciaremos los cambios sustanciales por venir por lo menos tres meses antes de
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}Sustancial{% else %}Peligroso{% endif %}</span>Se hará un cambio a <code>{{ change.location }}</code>.
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}Sustancial{% else %}Peligroso{% endif %}</span>Se hará un cambio a <code>{{ change.location }}</code>.
 
 <p><b>Descripción:</b> {{ change.description }}</p>
 
diff --git a/translations/es-ES/content/graphql/reference/input-objects.md b/translations/es-ES/content/graphql/reference/input-objects.md
index e43612eba2..7974c67226 100644
--- a/translations/es-ES/content/graphql/reference/input-objects.md
+++ b/translations/es-ES/content/graphql/reference/input-objects.md
@@ -19,6 +19,5 @@ Por ejemplo, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) tom
 
 Para obtener más información, consulta la sección "[Acerca de las mutaciones](/graphql/guides/forming-calls-with-graphql#about-mutations)".
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index 71eb86fee1..824c21b23c 100644
--- a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: Métricas disponibles con GitHub Insights
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %} incluye una variedad de métricas para darte visibilidad en el proceso de entrega de software de tu equipo.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index 992bb1f0ba..011df6081c 100644
--- a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Navegar entre GitHub Enterprise y GitHub Insights
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index 3b91f70776..8c051d1679 100644
--- a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Configurando tu zona horaria para GitHub Insights
 intro: 'Puedes establecer la zona horaria para las métricas que ves en {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
diff --git a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 59b451df20..31c2a68dde 100644
--- a/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/es-ES/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Ver métricas e informes clave
 intro: Puedes ver y filtrar métricas e informes clave para ayudarte a comprender y mejorar tu proceso de entrega de software mediante datos.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index 5412a3eead..c62df9d161 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Acerca de los datos en la información de GitHub
 intro: 'Los datos incluidos en las métricas de {% data variables.product.prodname_insights %} son altamente personalizables.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index df24ba153e..88a027fdae 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Acerca de GitHub Insights
 intro: '{% data variables.product.prodname_insights %} proporciona métricas e informes analíticos para ayudar a los equipos de ingeniería a comprender y mejorar su proceso de entrega de software.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
index c81a574abf..6ea013d6bf 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Configurar la conexión entre GitHub Insights y GitHub Enterprise
 intro: 'Puedes administrar de qué manera {% data variables.product.prodname_insights %} se conecta con {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can configure the connection to {% data variables.product.prodname_enterprise %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index f5c042a06e..c09d9fa2db 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Habilitar enlace entre la información de GitHub y GitHub Enterprise
 intro: 'Puedes habilitar un enlace que permitirá a los usuarios navegar desde {% data variables.product.prodname_ghe_server %} hacia {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index a2cd0e57c9..f2a6efaabf 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Instalar la información de GitHub
 intro: 'Puedes instalar {% data variables.product.prodname_insights %} y conectar la aplicación autónoma para {% data variables.product.prodname_ghe_server %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index a82d0cbf76..0aaf3f28db 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Gestión de métricas e informes disponibles
 intro: 'Puedes activar y desactivar métricas específicas en {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
index 86a8cc2022..18e777a2df 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
@@ -1,7 +1,6 @@
 ---
 title: Administrar colaboradores y equipos
 intro: Puedes administrar las personas y los equipos incluidos en las métricas y los informes.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage contributors and teams.'
@@ -98,7 +97,7 @@ Puedes crear y administrar equipos personalizados en {% data variables.product.p
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.teams-tab %}
 {% data reusables.github-insights.edit-team %}
-3. A la derecha del colaborador que deseas eliminar, haz clic en {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Botón papelera](/assets/images/help/insights/contributor-trashcan.png)
+3. A la derecha del colaborador que deseas eliminar, haz clic en {% octicon "trash" aria-label="The trash icon" %}. ![botón de cesto de basura](/assets/images/help/insights/contributor-trashcan.png)
 
 #### Renombrar un equipo personalizado
 
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md
index f82196723d..7e60b55a36 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-events.md
@@ -1,7 +1,6 @@
 ---
 title: Administrar eventos
 intro: '{% data reusables.github-insights.events %}'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-events
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage events.'
@@ -29,5 +28,5 @@ Después de crear un evento en {% data variables.product.prodname_insights %}, c
 
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.events-tab %}
-3. A la derecha del evento que deseas eliminar, haz clic en **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botón papelera](/assets/images/help/insights/trashcan-button.png)
+3. A la derecha del evento que deseas eliminar, haz clic en **{% octicon "trash" aria-label="The trash icon" %}**. ![Botón papelera](/assets/images/help/insights/trashcan-button.png)
 4. Haz clic en **Confirm (Confirmar)**.
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md
index ce72b55870..a954e12e4c 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: Administrar objetivos
 intro: Puedes utilizar objetivos para configurar metas para las métricas clave y medir el éxito al lograr dichas metas.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 78d21a175e..82a2ceb9d5 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -1,7 +1,6 @@
 ---
 title: Administrar organizaciones
 intro: 'Puedes administrar las organizaciones {% data variables.product.prodname_enterprise %} que están incluidas en las métricas.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index 6ac946c9cc..e2d1c6eed9 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Gestionar permisos en GitHub Insights
 intro: 'Puedes actualizar los permisos de un usuario en {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md
index fe54a651f1..96814e06db 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/managing-repositories.md
@@ -1,7 +1,6 @@
 ---
 title: Administrar repositorios
 intro: 'Puedes administrar los repositorios conectados a {% data variables.product.prodname_insights %} y los datos incluidos en las métricas de cada repositorio.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-repositories
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories. '
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index 7f39d8b0a9..0a00479edb 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Descripción general del sistema para la información de GitHub
 intro: '{% data variables.product.prodname_insights %} es una aplicación autónoma que interactúa con {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index 0df45e5c18..1c966ebf1f 100644
--- a/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/es-ES/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Actualizar la información de GitHub
 intro: 'Puedes actualizar a la última versión de {% data variables.product.prodname_insights %} para beneficiarte de las mejoras y correcciones de errores.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index 07ec15a688..8ab068d614 100644
--- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md
index a6311ece76..6ee5fe4737 100644
--- a/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -43,7 +43,7 @@ Para obtener más información, consulta las secciones{% if currentVersion == "f
 
 ### Leer más
 
-- "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)"
+- "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
 - [Acerca de los equipos](/articles/about-teams)"
 - "[Crear un debate de equipo](/organizations/collaborating-with-your-team/creating-a-team-discussion)"
 - "[Editar o eliminar un debate de equipo](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)"
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md
index a008e3bf47..ff1015617f 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
 {% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index ff4b709c59..395434e554 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -26,9 +26,8 @@ También puedes configurar las direcciones IP permitidas para las organizaciones
 
 ### Agregar una dirección IP permitida
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ También puedes configurar las direcciones IP permitidas para las organizaciones
 
 ### Habilitar direcciones IP permitidas
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. En "IP allow list" (Lista de permisos de IP), seleccione **Enable IP allow list** (Habilitar lista de permisos de IP). ![Realizar una marca de verificación para permitir direcciones IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. Haz clic en **Save ** (guardar).
 
 ### Editar una dirección IP permitida
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ También puedes configurar las direcciones IP permitidas para las organizaciones
 
 ### Eliminar una dirección IP permitida
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index 1f8149864e..25698f95d6 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### Mostrar la configuración de seguridad y de análisis
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 La página que se muestra te permite habilitar o inhabilitar todas las características de seguridad y de análisis para los repositorios de tu organización.
@@ -50,33 +49,38 @@ Puedes habilitar o inhabilitar las características para todos los repositorios.
 
 1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
 2. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}El control para "{% data variables.product.prodname_GH_advanced_security %}" se encontrará inhabilitado si no tienes plazas disponibles en tu licencia de {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. Da clic en **Inhabilitar CARACTERÍSTICA** o en **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios en tu organización.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Botón para inhabilitar o habilitar la característica](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Botón para habilitar característica para todos los repositorios elegibles de la organización](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![Botón para habilitar característica para todos los repositorios elegibles de la organización](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -84,12 +88,15 @@ Puedes habilitar o inhabilitar las características para todos los repositorios.
 ### Habilitar o inhabilitar una característica automáticamente cuando se agregan repositorios nuevos
 
 1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
-2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+2. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la características, habilita o inhabilitala predeterminadamente para los repositorios nuevos{% if currentVersion == "free-pro-team@latest" %} o para todos los repositorios privados{% endif %} de tu organización.
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -112,7 +119,7 @@ Para permitir que el {% data variables.product.prodname_dependabot %} acceda a u
 1. Comienza a teclear el nombre del repositorio que quieras permitir. ![Botón para agregar repositorios](/assets/images/help/organizations/dependabot-private-repo-choose.png)
 1. Haz clic en el repositorio que quieras permitir.
 
-1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. ![Botón "X" para eliminar un repositorio](/assets/images/help/organizations/dependabot-private-repository-list.png)
+1. Opcionalmente, para eliminar un repositorio de la lista, a la derecha de este, haz clic en {% octicon "x" aria-label="The X icon" %}. ![Botón "X" para eliminar un repositorio](/assets/images/help/organizations/dependabot-private-repository-list.png)
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
@@ -122,7 +129,7 @@ Para permitir que el {% data variables.product.prodname_dependabot %} acceda a u
 Puedes administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} para un repositorio desde su pestaña de "Configuración". Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". Sin embargo, también puedes inhabilitar las características de la {% data variables.product.prodname_GH_advanced_security %} para un reositorio desde la pestaña de "Configuración" de la organización.
 
 1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)".
-1. Para encontrar una lista de todos los repositorios de tu organización que tengan habilitada la {% data variables.product.prodname_GH_advanced_security %}, desplázate hasta la sección "repositorios con {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) La tabla lista la cantidad de confirmantes únicos para cada repositorio. Esta es la cantidad de plazas que puedes liberar en tus licencias si eliminas el acceso a {% data variables.product.prodname_GH_advanced_security %}. El tamaño de tu licencia se muestra para las licencias a nivel organizacional. Para obtener más información, consulta la sección "[Acerca de las licencias para {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)".
+1. Para encontrar una lista de todos los repositorios de tu organización que tengan habilitada la {% data variables.product.prodname_GH_advanced_security %}, desplázate hasta la sección "repositorios con {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) La tabla lista la cantidad de confirmantes únicos para cada repositorio. Esta es la cantidad de plazas que puedes liberar en tus licencias si eliminas el acceso a {% data variables.product.prodname_GH_advanced_security %}. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. Para eliminar el acceso a la {% data variables.product.prodname_GH_advanced_security %} desde un repositorio y liberar plazas que utilice cualquier confirmante y que son únicas en ese repositorio, haz clic en el {% octicon "x" aria-label="X symbol" %} adyacente.
 1. En el diálogo de confirmación, da clic en **Eliminar repositorio** para eliminar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %}.
 
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index 0e67d4b221..9cc59b4155 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ Antes de que requieras que se utilice la autenticación bifactorial, te recomend
 
 ### Solicitar autenticación de dos factores en tu organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..5a3fc5b9c0
--- /dev/null
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Acerca de las restricciones de correo electrónico
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. For more information about outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)."
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index 1c6e2a721d..2fae4cb2ad 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 La bitácora de auditoría lista los eventos que activan las actividades, los cuales afectan tu organización, dentro de los últimos 90 días. Solo los propietarios pueden acceder al registro de auditoría de una organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
 
 ### Buscar el registro de auditoría
@@ -36,6 +35,7 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta
 | [`cuenta`](#account-category-actions)                                                                                                                                                                                                                                                                                                                                                                          | Contiene todas las actividades relacionadas con tu cuenta de organización.                                                                                                                                                                                                                                                                                                                                                                                        |
 | [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                                                                                                                                                                                                         | Contiene todas las actividades relacionadas con darle crédito a un contribuyente por una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".                                                           |
 | [`facturación`](#billing-category-actions)                                                                                                                                                                                                                                                                                                                                                                     | Contiene todas las actividades relacionadas con la facturación de tu organización.                                                                                                                                                                                                                                                                                                                                                                                |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                                                                                                                                                   | Contiene todas las actividades relacionadas con los codespaces de tu organización.                                                                                                                                                                                                                                                                                                                                                                                |
 | [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                                                                                                                                                     | Contiene las actividades de configuración a nivel de organización para las alertas del {% data variables.product.prodname_dependabot %} en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".                                                                                        |
 | [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                                                                                                                                                                                                 | Contiene las actividades de configuración a nivel de organización para las alertas del {% data variables.product.prodname_dependabot %} en los repositorios nuevos que se crean en la organización.                                                                                                                                                                                                                                                               |
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                                                                                                                                                 | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_security_updates %} en los repositorios existentes. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)".                                                        |
@@ -146,7 +146,7 @@ Por ejemplo, puedes hacer una solicitud de GraphQL para ver todos los miembros n
 
 {% note %}
 
-**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only.
+**Nota:** La API de REST de la bitácora de auditoría se encuentra disponible únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}.
 
 {% endnote %}
 
@@ -156,7 +156,7 @@ Para garantizar una IP segura y mantener el cumplimiento para tu organización,
 
 {% data reusables.audit_log.audit-log-git-events-retention %}
 
-For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+Para obtener más información sobre la API de REST del log de auditoría, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
 
 {% endif %}
 
@@ -191,6 +191,20 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos
 | `change_billing_type (cambiar tipo de facturación)` | Se activa cuando tu organización [cambia la manera en que paga {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). |
 | `change_email (cambiar correo electrónico)`         | Se activa cuando cambia la [dirección de correo electrónico de facturación](/articles/setting-your-billing-email) de tu organización.                       |
 
+#### acciones de la categoría `codespaces`
+
+| Acción                       | Descripción                                                                                                                                                                                                                                                   |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`             | Se activa cuando un usuario [crea un codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                              |
+| `resume`                     | Se activa cuando un usuario reanuda un codesapce suspendido.                                                                                                                                                                                                  |
+| `delete`                     | Se activa cuando un usuario [borra un codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                             |
+| `create_an_org_secret`       | Se activ cuando un usuario crea un [secreto para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel de la organización |
+| `update_an_org_secret`       | Se activa cuando un usuario actualiza un [secreto para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional.  |
+| `remove_an_org_secret`       | Se activa cuando un usuario elimina un [secreto para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) a nivel organizacional.    |
+| `manage_access_and_security` | Se activa cuando un usuario actualiza [a cuáles repositorios puede acceder un codespace](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+
+
+
 #### Acciones de la categoría `dependabot_alerts`
 
 | Acción        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -272,7 +286,7 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos
 
 {% note %}
 
-**Nota:** Para acceder a los eventos de Git en la bitácora de auditoría, debes utilizar la API de la bitácora de auditoría de REST. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+**Nota:** Para acceder a los eventos de Git en la bitácora de auditoría, debes utilizar la API de la bitácora de auditoría de REST. La API de REST de la bitácora de auditoría se encuentra disponible únicamente para los usuarios de {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
 
 {% endnote %}
 
@@ -391,11 +405,11 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 {% if currentVersion == "free-pro-team@latest" %}
 #### acciones de la categoría `org_credential_authorization`
 
-| Acción         | Descripción                                                                                                                                                                                                         |
-| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `grant`        | Se activa cuando un miembro [autoriza credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                                    |
-| `deauthorized` | Se activa cuando un miembro [quita la autorización de credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                    |
-| `revoke`       | Se desencadena cuando un dueño [revoca las credenciales autorizadas](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). |
+| Acción         | Descripción                                                                                                                                                                                                          |
+| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grant`        | Se activa cuando un miembro [autoriza credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                                     |
+| `deauthorized` | Se activa cuando un miembro [quita la autorización de credenciales para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).                     |
+| `revoke`       | Se activa cuando un propietario [revoca las credenciales autorizadas](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). |
 
 {% endif %}
 
@@ -484,6 +498,38 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 | `update_linear_history_requirement_enforcement_level`                                                                       | Se activa cuando se habilita o inhabilita el historial de confirmaciones linear requerido para una rama protegida.                                                                                                                    |
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### Acciones de la categoría `pull_request`
+
+| Acción                  | Descripción                                                                                                                       |
+| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`        | Se activa cuando se crea una solicitud de cambios.                                                                                |
+| `close`                 | Se activa cuando se cierra una solicitud de cambios sin haberse fusionado.                                                        |
+| `reopen`                | Se activa cuando se vuelve a abrir una solicitud de cambios después de haberse cerrado previamente.                               |
+| `fusionar`              | Se activa cuando se fusiona una solicitud de cambios.                                                                             |
+| `indirect_merge`        | Se activa cuando una solicitud de cambios se considera como fusionada porque sus confirmaciones se fusionaron en la rama destino. |
+| `ready_for_review`      | Se activa cuando una solicitud de cambios se marca como lista para revisión.                                                      |
+| `converted_to_draft`    | Se activa cuando una solicitud de cambios se convierte en borrador.                                                               |
+| `create_review_request` | Se activa cuando se solicita una revisión.                                                                                        |
+| `remove_review_request` | Se activa cuando se elimina una solicitud de revisión.                                                                            |
+
+#### Acciones de la categoría `pull_request_review`
+
+| Acción      | Descripción                                |
+| ----------- | ------------------------------------------ |
+| `enviar`    | Se activa cuando se envía una revisión.    |
+| `descartar` | Se activa cuando se descarta una revisión. |
+| `delete`    | Se activa cuando se borra una revisión.    |
+
+#### Acciones de la categoría `pull_request_review_comment`
+
+| Acción           | Descripción                                           |
+| ---------------- | ----------------------------------------------------- |
+| `create (crear)` | Se activa cuando se agrega un comentario de revisión. |
+| `actualización`  | Se activa cuando se cambia un comentario de revisión. |
+| `delete`         | Se activa cuando se borra un comentario de revisión.  |
+{% endif %}
+
 #### acciones de la categoría `repo`
 
 | Acción                                                                                  | Descripción                                                                                                                                                                                                                                                                                                                                                                                            |
@@ -593,22 +639,24 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 {% if currentVersion == "free-pro-team@latest" %}
 #### acciones de la categoría `sponsors`
 
-| Acción                                                                                                            | Descripción                                                                                                                                                                                                                                                                                                                       |
-| ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo_funding_link_button_toggle (alternar botón de enlace al financiamiento del repositorio)`                    | Se activa cuando habilitas o inhabilitas un botón de patrocinador en tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                   |
-| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)`                 | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                         |
-| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)`                                        | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                      |
-| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)`                                          | Se activa cuando patrocinas una cuenta (consulta "[Patrocinar a un contribuyente de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                    |
-| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)`                     | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de una cuenta patrocinada (consulta "[Administrar tu patrocinio](/articles/managing-your-sponsorship)")                                                                                                                                         |
-| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)`                                   | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                          |
-| `sponsored_developer_approve (aprobación de programador patrocinado)`                                             | Se activa cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                          |
-| `sponsored_developer_create (creación de programador patrocinado)`                                                | Se activa cuando la cuenta de {% data variables.product.prodname_sponsors %} se crea (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                 |
-| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)`                        | Se activa cuando editas tu perfil de organización patrocinada (consulta "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
-| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)`                       | Se activa cuando emites tu solicitud para {% data variables.product.prodname_sponsors %} para su aprobación (consulta "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
-| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                                     |
-| sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)    | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta "[Contactar a tus patrocinadores](/articles/contacting-your-sponsors)")                                                                                                                                                            |
-| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)`             | Se activa cuando te invitan a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
-| `waitlist_join (incorporación a la lista de espera)`                                                              | Se activa cuando te unes a la lista de espera para convertirte en una organización patrocinada (consulta "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                   |
+| Acción                                                                                                            | Descripción                                                                                                                                                                                                                                                                                                                             |
+| ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`                                                                                   | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                           |
+| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)`                 | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                               |
+| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)`                                        | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                            |
+| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)`                                          | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                   |
+| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)`                     | Se activa cuando cambias si quieres recibir actualizaciones de una cuenta patrocinada por correo electrónico (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                               |
+| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)`                                   | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                |
+| `sponsored_developer_approve (aprobación de programador patrocinado)`                                             | Se activa cuando se aprueba tu cuenta de {% data variables.product.prodname_sponsors %} (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                              |
+| `sponsored_developer_create (creación de programador patrocinado)`                                                | Se activa cuando se crea la cuenta de {% data variables.product.prodname_sponsors %} (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                |
+| `sponsored_developer_disable`                                                                                     | Se activa cuando se inhabilita tu cuenta de {% data variables.product.prodname_sponsors %}
+| `sponsored_developer_redraft`                                                                                     | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado                                                                                                                                                                                               |
+| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)`                        | Se activa cuando editas tu perfil de organización patrocinada (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                    |
+| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)`                       | Se activa cuando emites tu solicitud para {% data variables.product.prodname_sponsors %} para su aprobación (consulta la sección "[">Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")        |
+| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                             |
+| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)`      | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                        |
+| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)`             | Se activa cuando te invitan a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
+| `waitlist_join (incorporación a la lista de espera)`                                                              | Se activa cuando te unes a la lista de espera para convertirte en una organización patrocinada (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organizacón](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                       |
 {% endif %}
 
 #### acciones de la categoría `team`
@@ -622,7 +670,7 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 | `create (crear)`                            | Se activa cuando se crea un equipo nuevo.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 
-`demote_maintainer` | Se activa cuando se baja de categoría a un usuario de mantenedor de equipo a miembro de equipo. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Se activa cuando un repositorio ya no está bajo el control de un equipo.
+`demote_maintainer` | Se activa cuando se baja de categoría a un usuario de mantenedor de equipo a miembro de equipo. Para obtener más información, consulta la sección "[Dar permisos de "mantenedor de equipo" a un miembro de la organizción](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)".{% endif %}| `destroy` | Se activa cuando se borra a un equipo de la organización.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`team.promote_maintainer` | Se activa cuando se promovió a un usuario de miembro de equipo a mantenedor de equipo. Para obtener más información, consulta la sección "[Otorgar permisos de "mantenedor de equipo" a un miembro de la organización](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Se activa cuando un miembro de una organización se [elimina de un equipo](/articles/removing-organization-members-from-a-team). | `remove_repository` | Se activa cuando un repositorio ya no está bajo el control de un equipo.
 
 #### acciones de la categoría `team_discussions`
 
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index d15764d7f0..97589ad288 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -14,9 +14,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. En la barra lateral izquierda, haz clic en **Installed {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s instaladas). ![Pestaña de {% data variables.product.prodname_github_app %}s instaladas en la barra lateral de parámetros de la organización](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. 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)
 6. Revisa el acceso al repositorio y los permisos de {% data variables.product.prodname_github_app %}. ![Opción para darle acceso a {% data variables.product.prodname_github_app %} a todos los repositorios o a repositorios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index ee9169ce7a..0dc08591d6 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ Para más información sobre los permisos del administrador de {% data variables
 
 ### Brindar a alguien la posibilidad de administrar todos los {% data variables.product.prodname_github_app %} que son propiedad de la organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. En "Management" (Administración), escribe el nombre de usuario de la persona a quien deseas designar como gerente de {% data variables.product.prodname_github_app %} en la organización, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### Brindar a alguien la posibilidad de administrar un {% data variables.product.prodname_github_app %} individual
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Debajo de "{% data variables.product.prodname_github_app %}s", haz clic en el avatar de la app a la que quieres agregarle un administrador de {% data variables.product.prodname_github_app %}. ![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index 8955e6e2a2..2c3b1a255a 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ Para más información sobre los permisos del administrador de {% data variables
 
 ### Eliminar los {% data variables.product.prodname_github_app %} permisos de un administrador para toda la organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. En "Management" (Administración), encuentra el nombre de usuario de la persona para la que quieres eliminar {% data variables.product.prodname_github_app %} los permisos de administrador, luego haz clic en **Revoke** (Revocar). ![Revocar {% data variables.product.prodname_github_app %} permisos de administrador](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### Eliminar los {% data variables.product.prodname_github_app %} permisos de administrador para una persona {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Debajo de "{% data variables.product.prodname_github_app %}s", haz clic en el avatar de la app de la que quieres eliminar un administrador {% data variables.product.prodname_github_app %}. ![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 06aaff8ac3..3fa83a7cbe 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -49,4 +49,4 @@ Si un equipo hereda el acceso a un tablero de proyecto desde un equipo padre, de
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Encima de la conversación del equipo, haz clic en {% octicon "project" aria-label="The Projects icon" %} **Projects (Proyectos)**. ![La pestaña de repositorios del equipo](/assets/images/help/organizations/team-project-board-button.png)
-5. Para cambiar los niveles de permiso, utiliza el menú desplegable que se encuentra al costado derecho del tablero de proyecto que quieres actualizar. Para elminar un tablero de proyecto, da clic en **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botón para eliminar un tablero de proyecto de la papelera del equipo](/assets/images/help/organizations/trash-button.png)
+5. Para cambiar los niveles de permiso, utiliza el menú desplegable que se encuentra al costado derecho del tablero de proyecto que quieres actualizar. Para elminar un tablero de proyecto, da clic en **{% octicon "trash" aria-label="The trash icon" %}**. ![Botón para eliminar un tablero de proyecto de la papelera del equipo](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
index cabda187b8..0ea162e76f 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
@@ -26,7 +26,7 @@ Si tu organización [requiere que los miembros utilicen autenticación bifactori
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
 {% if currentVersion == "free-pro-team@latest" %}
-5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![Invitar colaboradores externos a la organización](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
+5. A la derecha del nombre del colaborador externo que quieres hacer miembro, usa el menú desplegable {% octicon "gear" aria-label="The gear icon" %} y haz clic en **Invitar a la organización**.![Invitar colaboradores externos a la organización](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
 {% else %}
 5. A la derecha del nombre del colaborador externo que quieres hacer miembro, haz clic en **Invite to organization** (Invitar a la organización).![Invitar colaboradores externos a la organización](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
 {% endif %}
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index aa700f8517..b43199cce9 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ Además de administrar los parámetros al nivel de la organización, los propiet
 | Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)")                                                                                                                                                                                                                                                           |       |               |           |               |                                                                       **X**                                                                        |
 | Cambiar los parámetros de un repositorio                                                                                                                                                                                                                                                                                                                                             |       |               |           |               |                                                                       **X**                                                                        |
 | Administrar el acceso de un equipo o colaborador al repositorio                                                                                                                                                                                                                                                                                                                      |       |               |           |               |                                                                       **X**                                                                        |
-| Editar la rama predeterminada del repositorio                                                                                                                                                                                                                                                                                                                                        |       |               |           |               |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Editar la rama predeterminada del repositorio                                                                                                                                                                                                                                                                                                                                        |       |               |           |               |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Renombrar la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                  |       |               |           |               |                                                                       **X**                                                                        |
 | Renombrar una rama diferente a la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                             |       |               |   **X**   |     **X**     |                                                                 **X** 
 {% endif %}
@@ -142,7 +142,8 @@ Además de administrar los parámetros al nivel de la organización, los propiet
 | [Bloquear y desbloquear los debates](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                    |       |     **X**     |   **X**   |     **X**     |                                                                       **X**                                                                        |
 | [Convertir las propuestas en debates individualmente](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                   |       |     **X**     |   **X**   |     **X**     |                                                                       **X**                                                                        |
 | [Crear debates nuevos y comentar sobre los debates existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                       | **X** |     **X**     |   **X**   |     **X**     |                                                                       **X**                                                                        |
-| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                               |       |               |           |     **X**     |                                                                 **X** 
+| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                               |       |               |           |     **X**     |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                    |       |               |   **X**   |     **X**     |                                                                 **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ En esta sección, puedes encontrar los niveles de permisos de los repositorios q
 
 | Acción del repositorio                                                                                                                                                                                                                                                                                                            | Read  | Clasificación |      Escritura      |    Mantenimiento    |                                                                             Admin                                                                             |
 |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                                                                                                                                 |       |               |                     |                     |                                                                                                                                                               |
-| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en un repositorio                                                                                                                      |       |               |                     |                     |                                                                             **X**                                                                             |
-| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                                                                |       |               |                     |                     |                                                                             **X**                                                                             |
-| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para las dependencias vulnerables                                     |       |               |                     |                     |                                                                             **X**                                                                             |
-| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories)                                                                                                                                                                                                                        |       |               |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| Administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} (consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |               |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                                                                                                                               |       |               |                     |                     |                                                                                                                                                               |
+| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) en un repositorio                                                                                                                           |       |               |                     |                     |                                                                             **X**                                                                             |
+| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                                                                     |       |               |                     |                     |                                                                             **X**                                                                             |
+| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para las dependencias vulnerables                                     |       |               |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Crear [asesorías de seguridad](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                                                                                                               |       |               |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| Administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} (consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |               |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | [Habilitar el gráfico de dependencias](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) de un repositorio privado                                                                                                                                                                                 |       |               |                     |                     |                                                                             **X**                                                                             |
 | [Ver las revisiones de las dependencias](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                                                            | **X** |     **X**     |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [Ver las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                                                                                                        | **X** |     **X**     |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index a30e55f514..4ea6cef6c0 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ Si alguien con permisos administrativos en un repositorio de la organización ot
 
 ### Configurar los permisos base
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Debajo de "Permisos Base", utiliza el menú desplegable para seleccionar los nuevos permisos base. ![Selección de nuevo nivel de permiso desde el menú desplegable de "permisos base"](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. Revisa los cambios. Da clic en **Cambiar el permiso predeterminado por PERMISO** para confirmar. ![Revisar y confirmar el cambio de permisos base](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index df5ee06927..48996a2a97 100644
--- a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -22,17 +22,15 @@ Puedes permitir que los miembros accedan a los repositorios d ela organización
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### Eliminar una autoridad de certificado de SSH
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index e7b1ce0520..718bf105e2 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -17,9 +17,8 @@ Por defecto, las propuestas no pueden eliminarse en los repositorios de una orga
 
 Una vez habilitados, los propietarios de la organización y las personas con permisos de administración en un repositorio que es propiedad de la empresa pueden eliminar propuestas. Entre las personas con permisos de administración en un repositorio se incluyen los miembros de la organización y los colaboradores externos con privilegios de administración. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)" y "[Eliminar una propuesta"](/articles/deleting-an-issue)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. En "Issue deletion" (Eliminación de la propuesta), selecciona **Permitir que los miembros eliminen propuestas para esta organización**. ![Casilla de verificación para permitir que las personas eliminen propuestas](/assets/images/help/settings/issue-deletion.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index bd567bc47a..bb65fe2f22 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,9 +16,8 @@ Los propietarios de la organización pueden establecer limitaciones para ver la
 
 Los propietarios de la empresa pueden establecer limitaciones para ver la información de las dependencias de la organización en todas las organizaciones de tu cuenta de empresa. Para obtener más información, consulta "[Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)"
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. En "Member organization permissions" (Permisos para miembros de la organización), selecciona o quita la marca de selección de **Allow members to view dependency insights** (Permitir que los miembros vean información de dependencias). ![Casilla de verificación para permitir que los miembros vean información](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 07ee6f66d6..eb82ab7942 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -28,7 +28,6 @@ Una vez que eliminas una organización, GitHub **no puede restaurar su contenido
 
 ### 2. Elimina la organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Junto a la parte inferior de la página de configuración de la organización, haz clic en **Eliminar esta organización**. ![Botón Eliminar esta organización](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 9f27570fc5..5a5f1a1194 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -27,9 +27,8 @@ De manera alterna, puedes habilitar {% data variables.product.prodname_actions %
 
 ### Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Debajo de **Acciones locales y de terceros**, selecciona una opción. ![Habilitar, inhabilitar o limitar acciones para esta organización](/assets/images/help/repository/enable-org-actions.png)
 1. Haz clic en **Save ** (guardar).
@@ -50,9 +49,8 @@ Puedes inhabilitar todos los flujos de trabajo para una organización o configur
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Debajo de **Políticas**, selecciona una opción. ![Configurar la política de acciones para esta organización](/assets/images/help/organizations/actions-policy.png)
 1. Haz clic en **Save ** (guardar).
@@ -61,9 +59,8 @@ Puedes inhabilitar todos los flujos de trabajo para una organización o configur
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista. ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. Haz clic en **Save ** (guardar).
@@ -77,9 +74,27 @@ Puedes inhabilitar todos los flujos de trabajo para una organización o configur
 
 #### Configurar la política de bifurcaciones privadas para una organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Configurar los permisos del `GITHUB_TOKEN` para tu organización
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+Puedes configurar los permisos predeterminados para el `GITHUB_TOKEN` en la configuración de tu organización o tus repositorios. Si eliges la opción restringida como la predeterminada en tu configuración de organización, la misma opción se auto-seleccionará en la configuración de los repositorios dentro de dicha organización y se inhabilitará la opción permisiva. Si tu organización le pertenece a una cuenta {% data variables.product.prodname_enterprise %} y la configuración predeterminada más restringida se seleccionó en la configuración de dicha empresa, no podrás elegir la opción predeterminada permisiva en la configuración de tu organización.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configurar los permisos predeterminados del `GITHUB_TOKEN`
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. Debajo de **Permisos del flujo de trabajo**, elige si quieres que el `GITHUB_TOKEN` tenga permisos de lectura y escritura para todos los alcances o solo acceso de lectura para el alcance `contents`. ![Configurar los permisos del GITHUB_TOKEN para esta organización](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. Da clic en **Guardar** para aplicar la configuración.
+{% endif %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/index.md b/translations/es-ES/content/organizations/managing-organization-settings/index.md
index b475de98c7..3d424bbbd4 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/index.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/index.md
@@ -13,7 +13,7 @@ topics:
   - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index 3cfcf8eff6..4bdb1c3850 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ Las etiquetas predeterminadas se incluirán en todos los repositorios nuevos de
 
 ### Crear una etiqueta predeterminada
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ Las etiquetas predeterminadas se incluirán en todos los repositorios nuevos de
 
 ### Editar una etiqueta predeterminada
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ Las etiquetas predeterminadas se incluirán en todos los repositorios nuevos de
 
 ### Eliminar una etiqueta predeterminada
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index dbcde1f8a4..1ee5904ed7 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 Predeterminadamente, los miembros de la organización que tengan acceso de lectura pueden crear debates si un administrador de repositorio o propietario de organización habilita los debates en cualquier repositorio que pertenezca a ella.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Debajo de "Debates del repositorio", selecciona o deselecciona **Permitir que los usuarios con acceso de lectura creen debates**. ![Casilla de verificación para permitir que las personas con acceso de lectura creen debates](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración de debates](/assets/images/help/discussions/click-save.png)
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index 4a482f8364..83b50a9d4f 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ Los propietarios de la organización pueden programar un recordatorio para uno m
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### Crear un recordatorio programado para una organización
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ Los propietarios de la organización pueden programar un recordatorio para uno m
 {% data reusables.reminders.create-reminder %}
 
 ### Administrar un recordatorio programado para una organización
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ Los propietarios de la organización pueden programar un recordatorio para uno m
 {% data reusables.reminders.update-buttons %}
 
 ### Borrar un recordatorio programado para una organización
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index fa0bd221fc..8c5aa778c5 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ Si un propietario de la empresa requirió una política para el nombre de la ram
 
 ### Configurar el nombre de la rama predeterminada
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. Debajo de "Rama predeterminada del repositorio", da clic en **Cambiar el nombre de la rama predeterminada ahora**. ![Botón de ignorar](/assets/images/help/organizations/repo-default-name-button.png)
 4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 3b6148bbc5..62f9ed9a18 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -20,9 +20,8 @@ Los propietarios de la organización pueden administrar la visualización de los
 
 Cada miembro de la organización elige su propio nombre de perfil en sus configuraciones. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Dentro de "Admin repository permissions" (Permisos del administrador del repositorio), selecciona o quita la marca de selección **Allow members to see comment author's profile name in private repositories (Permitir que los miembros vean el nombre de perfil del autor del comentario en los repositorios privados)**. ![Casilla de verificación para permitir que los miembros vean el nombre completo del autor del comentario en los repositorios privados](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 501e62e905..a5fac70ebe 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ Si permites que se bifurquen los repositorios privados{% if currentVersion == "f
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Debajo de "Bifurcación de repositorios", selecciona **Permitir la bifurcación de repositorios privados** o **Permitir la bifurcación de repositorios privados e internos**. ![Casilla de verificación para permitir o prohibir la bifurcación en la organización](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
index 520926e7d2..06a94a5692 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -16,14 +16,13 @@ topics:
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
-If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. De lo contrario, puedes elegir permitir o dejar de permitir las publicaciones al público en general. Para obtener más información acerca del control de accesos de los sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)".
+Si tu organización utiliza {% data variables.product.prodname_ghe_cloud %}, puedes elegir el permitir que los miembros de esta creen sitios para el público en general, privados, ambos, o ninguno. De lo contrario, puedes elegir permitir o dejar de permitir las publicaciones al público en general. Para obtener más información acerca del control de accesos de los sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)".
 {% endif %}
 
 Si dejas de permitir la publicación de sitios de {% data variables.product.prodname_pages %}, cualquier sitio que ya se haya publicado permanecerá así. Puedes anular la publicación del sitio manualmente. Para obtener más información, consulta la sección "[Anular la publicación de un sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
 1. Debajo de "Creación de páginas", selecciona las visibilidades que quieras permitir y deselecciona aquellas que quieres dejar de permitir. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
 1. Debajo de "Creación de páginas", selecciona y deselecciona **Permitir a los miembros publicar sitios**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}
@@ -31,4 +30,4 @@ Si dejas de permitir la publicación de sitios de {% data variables.product.prod
 
 ### Leer más
 
-- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)"
+- "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)"
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index 641e5a28a1..6dd4b76027 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 Los desarrolladores y organizaciones que patrocine tu organización pueden enviarte actualizaciones sobre su trabajo. Puedes administrar la dirección de correo electrónico que recibe estas actualizaciones.
 
-También puedes inhabilitar las actualizaciones de las cuentas que tu organización patrocine. Para obtener más información, consulta "[Administar tu patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)".
+También puedes inhabilitar las actualizaciones de las cuentas que tu organización patrocine. Para obtener más información, consulta "[Administar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Debajo de "correo electrónico de actualización de patrocinios (Privado)", teclea la dirección de correo electrónico de la cual deseas recibir actualizaciones sobre las cuentas que patrocina tu organización. ![Casilla de texto para ingresar una dirección de correo electrónico para recibir actualizaciones de las cuentas patrocinadas](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. Haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/organizations/update-profile-button.png)
 
 ### Leer más
 
-- "[Apoyar a la comunidad de código abierto con {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)"
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md
index 94168cedf5..439b99afaf 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -35,14 +35,13 @@ Después de cambiar el nombre de tu organización, el nombre antiguo de tu organ
 Después de cambiar el nombre de tu organización:
 - Los enlaces a la página de perfil de tu organización anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, generarán un error 404. Te recomendamos que actualices los enlaces a tu organización desde otros sitios{% if currentVersion == "free-pro-team@latest" %}, tales como tus perfiles de LinkedIn o Twitter{% endif %}.
 - Las solicitudes API que utilizan el nombre de la organización antiguo generarán un error 404. Recomendamos que actualices el nombre de la organización antiguo en tus solicitudes API.
-- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %}
-- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %}
+- No hay redireccionamientos automáticos de [@mención](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) para los equipos que utilizan el nombre antiguo de la organización.{% if currentVersion == "free-pro-team@latest" %}
+- Si se habilita el inicio de sesión único (SSO) para la organización, debes actualizar el nombre de la misma en la aplicación para {% data variables.product.prodname_ghe_cloud %} en tu proveedor de identidad (IdP). Si no actualizas el nombre de organización en tu IdP, los miembros de esta ya no podrán autenticarse con tu IdP para acceder a los recursos de la organización. Para obtener más información, consulta la sección "[Conectar a tu proveedor de identidad con tu organización](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %}
 
 ### Cambiar el nombre de tu organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Cerca de la parte de abajo de la página de parámetros, en "Rename organization" (Renombrar organización), haz clic en **Rename Organization** (Renombrar organización). ![Botón Rename organization (Renombrar organización)](/assets/images/help/settings/settings-rename-organization.png)
 
 ### Leer más
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 ca99bb265d..f1a11a382b 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
@@ -27,9 +27,8 @@ Los propietarios de la organización siempre pueden crear cualquier tipo de repo
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Debajo de "Creación de repositorios", selecciona una o más opciones. ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index 4e7953a000..0fab5b5aa4 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ Puedes restringir la habilidad de cambiar la visibilidad de un repositorio para
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. En "Repository visibility change" (Cambio en la visibilidad de los repositorios), anula la selección de **Allow members to change repository visibilities for this organization** (Permitir que los miembros cambien las visibilidades de los repositorios para esta organización). ![Casilla para permitir que los miembros cambien la visibilidad de los repositorios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index 507b5d52bd..ba8dc5eda9 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -19,9 +19,8 @@ Los propietarios de la organización y los miembros con privilegios administrati
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Debajo de "Invitaciones al repositorio", selecciona **Permitir que los miembros inviten colaboradores externos a los repositorios de esta organización**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 0af01ee913..cdbb766b4c 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -16,9 +16,8 @@ topics:
 
 Los propietarios pueden configurar permisos para eliminar o transferir repositorios en una organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Dentro de "Repository deletion and transfer" (Eliminación o transferencia de repositorios), selecciona o deselecciona **Allow members to delete or transfer repositories for this organization (Permitir que los miembros puedan eliminar o transferir repositorios para esta organización)**. ![Casilla de verificación para permitir que los miembros eliminen repositorios](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index e619f3c0c0..ec486f937c 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -17,9 +17,8 @@ Los propietarios de la organización pueden establecer permisos de creación de
 
 Si no configuras permisos de creación de equipos, todos los miembros de la organización podrán crear equipos por defecto.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Dentro de "Team creation rules" (Reglas de creación de equipos), selecciona o deselecciona **Allow members to create teams (Permitirle a los miembros crear equipos)**. ![Casilla de verificación para permitir que los miembros creen equipos](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..1a5b8e7c56
--- /dev/null
+++ b/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Acerca de la verificación de dominios
+
+Después de verificar la propiedad de los dominios de tu organización, se mostrará un distintivo "Verified" (Verificado) en el perfil de la organización. Si tu organización está en {% data variables.product.prodname_ghe_cloud %} y ha aceptado los Términos de servicio corporativos, los propietarios de la organización podrán verificar la identidad de los miembros de la organización al ver la dirección de correo electrónico de cada miembro dentro del dominio verificado. Para obtener más información, consulta "[Acerca de la página de perfil de tu organización](/articles/about-your-organization-s-profile/)" y "[Actualizar a los Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)."
+
+Si tu organización le pertenece a una cuenta empresarial, se mostrará una "insignia verificada" en el perfil de tu organización para cualquier dominio verificado en dicha cuenta, adicinalmente a cualquier dominio verificado para la organización. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+En {% data variables.product.prodname_ghe_cloud %}, después de verificar la propiedad del dominio de tu organización, puedes restringir las notificaciones por correo electrónico para la organización a ese dominio. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Espera a que cambie la configuración de tu DNS, lo cual puede llevar hasta 72 horas. Puedes confirmar que tu configuración de DNS cambió si ejecutas el comando `dig` en la línea de comandos, reemplazando `ORGANIZATION` con el nombre de tu organización y `example.com` con el dominio que te gustaría verificar. Deberías ver tu nuevo registro TXT enumerado en el resultado del comando.
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. Como alternativa, una vez que la insignia "Verified" (Verificado) es visible en la página de perfil de tu organización, puedes eliminar la entrada de TXT desde el registro de DNS en tu servicio de alojamiento de dominio. ![Insignia Verificado](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index a02fd75d26..5299497d7c 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ Los gerentes de facturación**no** pueden:
 
 La persona invitada recibirá una invitación por correo electrónico solicitándole que se convierta en gerente de facturación para tu organización. Una vez que la persona invitada hace clic en el enlace de aceptación en el correo electrónico de la invitación, se agregarán automáticamente a la organización como gerentes de facturación. Si todavía no tienen una cuenta GitHub, deberán iniciar sesión para una cuenta, y se agregarán automáticamente a la organización como gerentes de facturación luego de crear una cuenta.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Junto a Billing managers (Gerentes de facturación), haz clic en **Add a billing manager** (Agregar un gerente de facturación). ![Invitar gerente de facturación](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![Invitar gerente de facturación](/assets/images/help/billing/settings_billing_managers_list.png)
 6. Escribe el nombre de usuario o la dirección de correo electrónico de la persona a la que deseas agregar y haz clic en **Send invitation** (Enviar invitación). ![Página Invitar gerente de facturación](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index 1d4b685ef0..dfca9109e8 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -23,6 +23,12 @@ topics:
 
 Los propietarios de una organización tienen acceso administrativo completo a la misma. {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**Nota**: Como propietario de la organización, puedes cambiar el rol de otros miembros de la organización para que sean propietarios. No puedes cambiar tu propio rol.
+
+{% endnote %}
+
 ### Designar un propietario de organización
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index dbaccac0db..ed2f2d9da3 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ Los miembros de la organización pueden tener roles de *propietario*{% if curren
 | Acceder al registro de auditoría de la organización                                                                                                                                                                                                                                                                                                                                                 |    **X**     |          |                         |
 | Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/articles/about-your-organization-s-profile)" para obtener más detalles)                                                                                                                                                                                                                            |    **X**     |          |                         |
 | Verificar los dominios de la organización (consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)" para obtener más detalles)                                                                                                                                                                                                                          |    **X**     |          |                         |
-| Restringir las notificaciones de correo electrónico a los dominios verificados (consulta la sección "[Restringir las notificaciones de correo electrónico a un dominio aprobado](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" para obtener más detalles)                                                                                 |    **X**     |          |                         |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)                                                                                                                                                     |    **X**     |          |                         |
 | Eliminar **todos los equipos**                                                                                                                                                                                                                                                                                                                                                                      |    **X**     |          |                         |
 | Eliminar la cuenta de la organización, incluidos todos los repositorios                                                                                                                                                                                                                                                                                                                             |    **X**     |          |                         |
 | Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles)                                                                                                                                                                                                          |    **X**     |  **X**   |                         |
@@ -60,9 +60,9 @@ Los miembros de la organización pueden tener roles de *propietario*{% if curren
 | Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles)                                                                                                                                                                                         |    **X**     |          |                         |
 | Administrar vistas de la información de las dependencias de la organización (consulta "[Cambiar la visibilidad de la información de las dependencias de tu organización](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para obtener más detalles)                                                                                                                   |    **X**     |          |                         |
 | Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles)                                                                                                                                                                                              |    **X**     |          |                         |
-| Patrocinar cuentas y administrar los patrocionos de la organización (consulta la sección "[Patrocinar contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para obener más detalles)                                                                                                                           |    **X**     |  **X**   |                         |
+| Patrocinar cuentas y administrar los patrocionos de la organización (consulta la sección "[Patrocinar contribuyentes de código abierto](/sponsors/sponsoring-open-source-contributors)" para obener más detalles)                                                                                                                                                                                   |    **X**     |  **X**   |                         |
 | Administrar las actualizaciones de las cuentas patrocinadas (consulta la sección "[Administrar las actualizaciones de los patrocinadores de tu organización](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" para obtener más detalles)                                                                                                   |    **X**     |          |                         |
-| Atribuir tus patrocinios a otra organización (consulta la sección "[Atribuir los patrocionios a tu organización](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obtener más detalles)                                                                                                                                       |    **X**     |          |                         |
+| Atribuir tus patrocinios a otra organización (consulta la sección "[Atribuir los patrocionios a tu organización](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" para obtener más detalles)                                                                                                                                                           |    **X**     |          |                         |
 | Administra la publicación de páginas de {% data variables.product.prodname_pages %} desde los repositorios de la organización (consulta "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" para obtener más detalles) |    **X**     |          |                         |
 | Administrar la configuración de seguridad y de análisis (consulta la sección "[Administrar la configuración de seguridad y de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles)                                                                                           |    **X**     |          |                         |
 | Habilitar y aplicar el [inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                                                                                                                                    |    **X**     |          |                         |
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index 30cac2ca98..fcf62f629e 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. En la lista de Gerentes de facturación, al lado del nombre de la persona que quieres eliminar, haz clic en {% octicon "x" aria-label="X symbol" %}. ![Eliminar gerente de facturación](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![Eliminar gerente de facturación](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index 31ae4c8e3c..0ade1d13b3 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 Los códigos de recuperación no se deben compartir ni distribuir. Te recomendamos guardarlos con un administrador de contraseñas, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/).
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. En "Inicio de sesión único SAML", en la nota acerca de los códigos de recuperación, haz clic en **Guardar tus códigos de recuperación**. ![Enlace para ver y guardar tus códigos de recuperación](/assets/images/help/saml/saml_recovery_codes.png)
 6. Guarda tus códigos de recuperación haciendo clic en **Download** (Descargar), **Print** (Imprimir) o **Copy** (Copiar). ![Botones para descargar, imprimir o copiar tus códigos de recuperación](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index 835ecbb796..6044a5f418 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ Si habilitas pero no exiges SAML SSO, los miembros de la organización que elija
 
 Antes de exigir SAML SSO en tu organización, verifica que ya tengas configurado tu proveedor de identidad (IP). Para obtener más información, consulta "[Preparación para exigir inicio de sesión único SAML en tu organización](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. En "inicio de sesión único SAML", selecciona **Habilitar autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index 7385af28da..10a0a1fb3e 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ Debes autenticarte con tu organización utilizando el SSO de SAML y el IdP compa
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ Debes autenticarte con tu organización utilizando el SSO de SAML y el IdP compa
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ Debes autenticarte con tu organización utilizando el SSO de SAML y el IdP compa
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Dentro de "Team synchronization" (Sincronización de equipo), haz clic en **Disable team synchronization (Inhabilitar la sincronización de equipo)**. ![Inhabilita la sincronización de equipo](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index 4720fa55b3..cfbd658b8d 100644
--- a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -29,9 +29,8 @@ Para obtener más información, consulta "[Niveles de permiso del repositorio pa
 
 ### Migrar todos tus equipos de administradores heredados de tu organización
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Revisa tus equipos de administradores heredados de la organización, después haz clic en **Migrate all teams (Migrar todos los equipos)**. ![Botón Migrar todos los equipos](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. Lee la información sobre los posibles cambios en permisos para los miembros de estos equipos, después haz clic en **Migrate all teams (Migrar todos los equipos).** ![Botón Confirmar migración](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/es-ES/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index 7d23999ffe..1f39603f03 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -15,9 +15,8 @@ topics:
 
 {% data reusables.organizations.team-discussions-default %}Para obtener más información acerca de los debates de equipo, consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. En "Debates de equipo", quita la marca de selección de **Habilitar debates de equipo para esta organización**. ![Casilla de verificación para inhabilitar debates de equipo para una organización](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
index 7433ba04fc..6ada8b80e0 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
@@ -30,7 +30,7 @@ Todos los cambios a la membrecía de equipo que se hagan con tu IdP aparecerán
 {% endif %}
 
 {% if currentVersion == "github-ae@latest" %}
-When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Cualquier solicitud que cambie la membrecía de organización o equipo de {% data variables.product.prodname_dotcom %} se registrará en la bitácora de auditoría como cambios que realizó la cuenta que se utilizó para configurar el aprovisionamiento de usuarios. Para obtener más información sobre esta cuenta, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obtener más información acerca de los itinerarios de solicitudes de SCIM, consulta la sección "[Verificar el estado del aprovisionamiento de usuarios](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" en Microsoft Docs.
+Cuando cambia la membrecía de grupo en tu IdP, este envía una solicitud de SCIM con los cambios a {% data variables.product.product_name %} de acuerdo con la programación que determinó tu IdP. Cualquier solicitud que cambie la membrecía de organización o equipo de {% data variables.product.prodname_dotcom %} se registrará en la bitácora de auditoría como cambios que realizó la cuenta que se utilizó para configurar el aprovisionamiento de usuarios. Para obtener más información sobre esta cuenta, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obtener más información acerca de los itinerarios de solicitudes de SCIM, consulta la sección "[Verificar el estado del aprovisionamiento de usuarios](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" en Microsoft Docs.
 {% endif %}
 
 Los equipos padre no pueden sincronizarse con los grupos de IdP. Si el equipo que quieres conectar a un grupo de IdP es un equipo padre, te recomendamos crear un equipo nuevo o eliminar las relaciones anidadas que hacen de tu equipo un equipo padre. Para obtener más información, consulta las secciónes "[Acerca de los equipos](/articles/about-teams#nested-teams)", "[Crear un equipo](/organizations/organizing-members-into-teams/creating-a-team)", y "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organizations-hierarchy)".
@@ -47,7 +47,7 @@ Después de que conectas un equipo a un grupo de IdP, la sincronización de equi
 - La persona ya ingresó con su cuenta de usuario en {% data variables.product.product_name %} y se autenticó en la cuenta organizacional o empresarial a través del inicio de sesión único de SAML por lo menos una vez.
 - La identidad de SSO de la persona es miembro del grupo de IdP.
 
-Los equipos o miembros del grupo existentes que no cumplan con estos criterios se eliminarán automáticamente del equipo en {% data variables.product.product_name %} y perderán acceso a los repositorios. El revocar la identidad ligada a un usuario también eliminará a dicho usuario de cualquier equipo que se encuentre mapeado en los grupos de IdP. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."
+Los equipos o miembros del grupo existentes que no cumplan con estos criterios se eliminarán automáticamente del equipo en {% data variables.product.product_name %} y perderán acceso a los repositorios. El revocar la identidad ligada a un usuario también eliminará a dicho usuario de cualquier equipo que se encuentre mapeado en los grupos de IdP. Para obtener más información, consulta las secciones "[Visualizar y administrar el acceso SAML de un miembro para tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" y "[Visualizar y administrar el acceso SAML de un usuario para tu empresa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)".
 
 Puedes volver a agregar automáticamente a aquellos miembros del equipo que hayas eliminado una vez que se autentiquen en la cuenta empresarial u organizacional utilizando el SSO y así se migren al grupo de IdP conectado.
 
@@ -60,16 +60,16 @@ Si tu organización pertenece a una cuenta empresarial, habilitar la sincronizac
 ### Prerrequisitos
 
 {% if currentVersion == "free-pro-team@latest" %}
-Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)."
+Antes de que puedas conectar a un equipo de {% data variables.product.product_name %} con un grupo de proveedores de identidad, un propietario de empresa u organización debe habilitar la sincronización de equipos para tu organización o cuenta empresarial. Para obtener más información, consulta las secciones "[Administrar la sincronización de equipos para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" y "[Administrar la sincronización de equipos para las orgnizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)".
 
 Para evitar el eliminar miembros del equipo accidentalmente, visita el protal administrativo para tu IdP y confirma que cada miembro actual del equipo también se encuentre en los grupos de IdP que quieras conectar a este equipo. Si no tienes este acceso a tu proveedor de identidad, puedes comunicarte con tu administrador de IdP.
 
 Debes autenticarte utilizando el SSO de SAML. Para obtener más información, consulta "[Acerca de la autenticación con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)".
 
 {% elsif currentVersion == "github-ae@latest" %}
-Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
+Antes de que puedas conectar a un equipo de {% data variables.product.product_name %} con un grupo de IdP, primero debes configurar el aprovisionamiento de usuarios para {% data variables.product.product_location %} utilizando un sistema compatible para la Administración de Identidad entre Dominios (SCIM). Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
 
-Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. Para obtener más información, consulta la sección de [Configurar el aprovisionamiento automático de usuarios en GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) en los Microsoft Docs.
+Una vez que se configure el aprovisionamiento de usuarios para {% data variables.product.product_name %} utilizando SCIM, puedes asignar la aplicación de {% data variables.product.product_name %} a cada grupo de IdP que quieras utilizar en {% data variables.product.product_name %}. Para obtener más información, consulta la sección de [Configurar el aprovisionamiento automático de usuarios en GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) en los Microsoft Docs.
 {% endif %}
 
 ### Conectar un grupo de IdP a tu equipo
diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index 867a97b8e1..da7b6dfd31 100644
--- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_app %} están habilitadas, los miembros de la organización deben [solicitar la aprobación](/articles/requesting-organization-approval-for-oauth-apps) de un propietario de la organización antes de que puedan autorizar una {% data variables.product.prodname_oauth_app %} que tiene acceso a los recursos de la organización.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Junto a la aplicación que quieres aprobar, haz clic en **Review** (Revisar). ![Enlace de revisión de solicitud](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. Una vez que revises la información sobre la aplicación solicitada, haz clic en **Grant access** (Otorgar acceso). ![Botón para otorgar acceso](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index a3cb9af33a..7548db7737 100644
--- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -12,9 +12,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Junto a la aplicación que deseas inhabilitar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. ![Icono Editar](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. Haz clic en **Denegar acceso**. ![Botón Denegar confirmación](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index d54e7c51a3..d49111fd51 100644
--- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Haz clic en **Eliminar restricciones**. ![Botón Eliminar restricciones](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. Revisa la información acerca de la inhabilitación de las restricciones de las aplicaciones de terceros y luego haz clic en **Sí, eliminar las restricciones de las aplicaciones**. ![Botón de eliminar confirmación](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index 00a6aecffc..7266db8358 100644
--- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. En "Política de acceso de aplicaciones de terceros", haz clic en **Configurar restricciones de acceso de aplicaciones**. ![Botón Configurar restricciones](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. Luego de revisar la información acerca de las restricciones de acceso de las aplicaciones de terceros, haz clic en **Restringir el acceso de aplicaciones de terceros**. ![Botón Confirmar restricciones](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/es-ES/content/packages/index.md b/translations/es-ES/content/packages/index.md
index 7b3933aee3..60daba39b8 100644
--- a/translations/es-ES/content/packages/index.md
+++ b/translations/es-ES/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..e1de3959b1
--- /dev/null
+++ b/translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,85 @@
+---
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Permisos de visibilidad y acceso para las imágenes de contenedor
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Administrar paquetes
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+Por ejemplo:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}Para borrar un paquete en {% data variables.product.product_name %}, tu token deberá tener por lo menos los alcances de `delete:packages` y `read:packages`. El alcance de `repo` también se requiere para los paquetes con dicho alcance.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}Para borrar una versión específica de un paquete privado en {% data variables.product.product_name %}, tu token debe tener el alcance `delete:packages` y `repo`. Los paquetes públicos no se pueden borrar.{% elsif currentVersion == "github-ae@latest" %}Para borrar una versión específica de un paquete en {% data variables.product.product_name %}, tu token debe tener los alcances de `delete:packages` y `repo`.{% endif %} Para obtener más información, consulta la sección "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}".
+
+| Ámbito                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Descripción                                                                          | Permiso requerido |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ----------------- |
+| `read:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Descarga e instala paquetes de {% data variables.product.prodname_registry %}        | lectura           |
+| `write:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Carga y publica paquetes en {% data variables.product.prodname_registry %}           | escritura         |
+| `delete:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |                                                                                      |                   |
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Borrar paquetes de {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Borrar versiones específicas de paquetes privados en el {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Borrar versiones específicas de paquetes en el {% data variables.product.prodname_registry %} {% endif %} |                                                                                      |                   |
+| admin                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                                                      |                   |
+| `repo`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Carga y borra los paquetes (junto con los `write:packages`, o los `delete:packages`) | write or admin    |
+
+Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..990f9d03bc
--- /dev/null
+++ b/translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: Configuring a package's access control and visibility
+intro: 'Elige quién ha leído, escrito, o administrado el acceso a tu imagen de contenedor y la visibilidad de tus imágenes de contenedor en {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+### Permisos de visibilidad y acceso para las imágenes de contenedor
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### Configurar el acceso a las imágenes de contenedor para tu cuenta personal
+
+If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. Para obtener más información acerca de estos roles de permisos, consulta la sección "[Permisos de visibilidad y acceso para las imágenes de contenedor](#visibility-and-access-permissions-for-container-images)".
+
+Si tu paquete es privado o interno y le pertenece a una organización, entonces solo puedes darles acceso a otros miembros o equipos de la misma.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. En la página de configuración del paquete, da clic en **Invitar equipos o personas** e ingresa el nombre real, nombre de usuario, o dirección de correo electrónico de la persona a la que quieras dar acceso. No se puede otorgar acceso a los equipos para aquellas imágenes de contenedor que pertenezcan a una cuenta de usuario. ![Botón de invitación para el acceso al contenedor](/assets/images/help/package-registry/container-access-invite.png)
+1. Junto al equipo o nombre de usuario, utiliza el menú desplegable de "Rol" para seleccionar un nivel de permisos que desees. ![Opciones de acceso al contenedor](/assets/images/help/package-registry/container-access-control-options.png)
+
+Se otorgará acceso automáticamente a los usuarios seleccionados y no necesitarán aceptar una invitación previamente.
+
+### Configurar el acceso a las imágenes de contenedor para una organización
+
+Si tienes permisos administrativos en una imágen de contenedor que pertenezca a una organización, puedes asignar roles de lectura, escritura o administración a otros usuarios y equipos. Para obtener más información acerca de estos roles de permisos, consulta la sección "[Permisos de visibilidad y acceso para las imágenes de contenedor](#visibility-and-access-permissions-for-container-images)".
+
+Si tu paquete es privado o interno y le pertenece a una organización, entonces solo puedes darles acceso a otros miembros o equipos de la misma.
+
+Para los contenedores de imagen de la organizción, los administradores de la organización deben habilitar los paquetes antes de que puedas configurar la visibilidad como pública. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. En la página de configuración del paquete, da clic en **Invitar equipos o personas** e ingresa el nombre real, nombre de usuario, o dirección de correo electrónico de la persona a la que quieras dar acceso. También puedes ingresar un nombre de equipo desde la organización para otorgar acceso a todos los miembros de éste. ![Botón de invitación para el acceso al contenedor](/assets/images/help/package-registry/container-access-invite.png)
+1. Junto al equipo o nombre de usuario, utiliza el menú desplegable de "Rol" para seleccionar un nivel de permisos que desees. ![Opciones de acceso al contenedor](/assets/images/help/package-registry/container-access-control-options.png)
+
+Se otorgará acceso automáticamente a los usuarios o equipos seleccionados y no necesitarán aceptar una invitación previamente.
+
+### Heredar el acceso a una imagen de contenedor desde un repositorio
+
+Para simplificar la administración de paquetes a través de los flujos de trabajo de {% data variables.product.prodname_actions %}, puedes habilitar a una imagen de contenedor para que herede los permisos de acceso de un repositorio predeterminadamente.
+
+Si heredas los permisos de acceso del repositorio en donde se almacenan los flujos de trabajo de tu paquete, entonces puedes ajustar el acceso al mismo a través de los permisos del repositorio.
+
+Una vez que el repositorio se sincronice, no podrás acceder a la configuración de acceso granular del paquete. Para personalizar los permisos de paquete a través de la configuración de acceso granular del paquete, primero debes sincronizar el repositorio.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. Debajo de "Fuente del repositorio", selecciona **Heredar el acceso del repositorio (recomendado)**. ![Casilla de verificación de heredar el acceso del repositorio](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### Garantizar el acceso al flujo de trabajo para tu paquete
+
+Para garantizar que el flujo de trabajo de {% data variables.product.prodname_actions %} tiene acceso a tu paquete, debes otorgar acceso explícito al repositorio en donde se almacena el flujo de trabajo.
+
+El repositorio especificado no necesita ser aquél en donde se mantiene el código fuente del paquete. Puedes dar acceso de flujo de trabajo a un paquete para varios repositorios.
+
+{% note %}
+
+**Nota:** El sincronizar tu imagen de contenedor con un repositorio mediante la opción de menú **Acceso a las acciones** es diferente que conectar tu contenedor a un repositorio. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+#### {% data variables.product.prodname_actions %} access for user-account-owned container images
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. En la barra lateral izquierda, haz clic en **Acceso a las acciones**. ![Opción "Acceso a las acciones" en el menú izquierdo](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Haz clic en **Agregar repositorio** y busca el repositorio que quieres agregar. ![Botón "Agregar repositorio"](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Niveles de acceso de permisos para otorgar a los repositorios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+#### {% data variables.product.prodname_actions %} access for organization-owned container images
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. En la barra lateral izquierda, haz clic en **Acceso a las acciones**. ![Opción "Acceso a las acciones" en el menú izquierdo](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Haz clic en **Agregar repositorio** y busca el repositorio que quieres agregar. ![Botón "Agregar repositorio"](/assets/images/help/package-registry/add-repository-button.png)
+3. Selecciona el nivel de acceso predeterminado que te gustaría que tuvieran los miembros del repositorio en tu imagen de contenedor utilizando el menú desplegable de "rol". No se incluirá a los colaboradores externos. ![Niveles de acceso de permisos para otorgar a los repositorios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+Para personalizar aún más el acceso a tu imagen de contenedor, consulta la sección "[Configurar el acceso a las imágenes de contenedor de una organización](#configuring-access-to-container-images-for-an-organization)".
+
+### Configurar la visibilidad de las imágenes de contenedor para tu cuenta personal
+
+Cuando publicas un paquete por primera vez, la visibilidad predeterminada es privada y solo tú puedes verlo. Puedes modificar el acceso a las imágenes de contenedor públicas si cambias la configuración de acceso.
+
+Se puede acceder anónimamente a un paquete público sin autenticación. Una vez que hagas tu paquete público, no puedes hacerlo privado nuevamente.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. Debajo de "Zona de peligro", elige una configuración de visibilidad:
+    - Para que la imagen del contenedor sea visible para todos, da clic en **Hacer público**.
+    {% warning %}
+
+    **Advertencia:** Una vez que hagas público algún paquete no podrás volverlo a hacer privado.
+
+    {% endwarning %}
+    - Para hacer la la imagen de contenedor sea visible para una selección personalizada de individuos, da clic en **Hacer privada**. ![Opciones de visibilidad del contenedor](/assets/images/help/package-registry/container-visibility-option.png)
+
+### Visibilidad de creación de un contenedor para los miembros de una organización
+
+Puedes elegir la visibilidad de los contenedores que los miembros de las organizaciones pueden publicar predeterminadamente.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. A la izquierda, da clic en **Paquetes**.
+6. Debajo de "Creación de contenedores", elige si quieres habilitar la creación de imágenes de contenedor públicas, privadas o internas.
+    - Para habilitar a los miembros de la organización para que creen imágenes de contenedor, da clic en **Públicas**.
+    - Para habilitar a los miembros de la organización para que creen imágenes de contenedor que solo sean visibles para otros miembros de la organización, da clic en **Privadas**. Puedes personalizar aún más la visibilidad de las imagenes de contenedor privadas.
+    - **Únicamente para {% data variables.product.prodname_ghe_cloud %}:** Para habilitar a los miembros de la organización para que creen imágenes de contenedor internas que solo puedan ver otros miembros organizacionales, haz clic en **Interna**. ![Opciones de visibilidad para las imágenes de contenedor que publican los miembros de la organización](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### Configurar la visibilidad de las imágenes de contenedor para una organización
+
+Cuando publicas un paquete por primera vez, la visibilidad predeterminada es privada y solo tú puedes verlo. Puedes otorgar roles de acceso diferentes a los usuarios o equipos para tu imagen de contenedor a través de la configuración de acceso.
+
+Se puede acceder anónimamente a un paquete público sin autenticación. Una vez que hagas tu paquete público, no puedes hacerlo privado nuevamente.
+
+Para las imágenes de contenedor organizacionales, los administradores de las organizaciones deben habilitar los paquetes públicos antes de que puedas configurar la visibilidad como pública. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. Debajo de "Zona de peligro", elige una configuración de visibilidad:
+    - Para que la imagen del contenedor sea visible para todos, da clic en **Hacer público**.
+    {% warning %}
+
+    **Advertencia:** Una vez que hagas público algún paquete no podrás volverlo a hacer privado.
+
+    {% endwarning %}
+    - Para hacer la la imagen de contenedor sea visible para una selección personalizada de individuos, da clic en **Hacer privada**. ![Opciones de visibilidad del contenedor](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..89d44c5584
--- /dev/null
+++ b/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+### Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to a container image using the command line
+
+1. En tu Dockerfile, agrega esta línea, reemplazando a `OWNER` y `REPO` con tu información:
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ Por ejemplo, si eres el usuario `monalisa` y eres propietario de `my-repo`, agregarías esta línea a tu Dockerfile:
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ Para obtener más información, consulta "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" en la documentación oficial de Docker, y "[Llaves de Anotación Predefinidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" en el repositorio `opencontainers/image-spec`.
+
+2. Crea tu imagen de contenedor. Este ejemplo crea una imagen del Dockerfile en el directorio actual y asigna el nombre de imagen `hello_docker`.
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. Opcionalmente, revisa los detalles para la imagen de Docker que quieres etiquetar.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Etiqueta tu imagen de Docker con el nombre que hayas elegido para la imagen y con el destino del host.
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  Por ejemplo:
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  Por ejemplo:
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/es-ES/content/packages/learn-github-packages/index.md b/translations/es-ES/content/packages/learn-github-packages/index.md
index 1780dc94b9..0157f09e81 100644
--- a/translations/es-ES/content/packages/learn-github-packages/index.md
+++ b/translations/es-ES/content/packages/learn-github-packages/index.md
@@ -1,7 +1,7 @@
 ---
 title: Aprende sobre GitHub Packages
 shortTitle: Aprende sobre GitHub Packages
-intro: 'Puedes encontrar más información sobre GitHub Packages, incluyendo la publicación de paquetes nuevos en el {% data variables.product.prodname_registry %}.'
+intro: 'You can find out more about using packages in GitHub, including publishing new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
   - /github/managing-packages-with-github-packages/publishing-and-managing-packages
@@ -17,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md b/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..eb5d01e6e2
--- /dev/null
+++ b/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: Instalar un paquete
+intro: 'Puedes instalar un paquete desde {% data variables.product.prodname_registry %} y usar el paquete como dependencia en tu propio proyecto.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Acerca de la instalación del paquete
+
+Puedes buscar {% data variables.product.product_name %} para encontrar los paquetes en {% data variables.product.prodname_registry %} que puedes instalar en tu propio proyecto. Para obtener más información, consulta "[Buscar {% data variables.product.prodname_registry %} para paquetes](/github/searching-for-information-on-github/searching-for-packages)".
+
+Una vez que encuentres un paquete, puedes leer las instrucciones de la descripción y la instalación y el uso del paquete en la página del paquete.
+
+### Instalar un paquete
+
+Puedes instalar un paquete desde el {% data variables.product.prodname_registry %} utilizando cualquier {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} cliente de paquetes compatible{% else %} tipo de paquete habilitado para tu instancia{% endif %} si sigues los mismos lineamientos generales.
+
+1. Autenticar para {% data variables.product.prodname_registry %} usando las instrucciones para tu cliente de paquete. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. Instala el paquete usando las instrucciones para tu cliente de paquete.
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..e0ab49ac0e
--- /dev/null
+++ b/translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,133 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} es un paquete de software que hospeda el servicio que te permite hospedar tus paquetes de software de forma privada {% if currentVersion == "github-ae@latest" %} para los usuarios específicos o internamente para tu empresa{% else %}o públicamente{% endif %} y utiliza los paquetes como dependencias en tus proyectos.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Acerca de {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquetes, totalmente integrado con {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combina tu código fuente y paquetes en un solo lugar para proporcionar una administración de permisos {% if currentVersion != "github-ae@latest" %}y facturación {% endif %}integradas, para que puedas centralizar tu desarrollo de software en {% data variables.product.product_name %}.
+
+Puedes integrar {% data variables.product.prodname_registry %} con las API de {% data variables.product.product_name %}, {% data variables.product.prodname_actions %} y webhooks para crear un flujo de trabajo de DevOps de extremo a extremo que incluya tu código, CI y soluciones de implementación.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/manage-packages/viewing-packages)".
+
+#### Overview of package permissions and visibility
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| Permisos                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                                  |
+| {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |                                                                  |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| Visibilidad                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | {% data reusables.package_registry.public-or-private-packages %}
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Acerca de la facturación para {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} Para obtner más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".
+
+{% endif %}
+
+### Formatos y clientes admitidos
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+{% data variables.product.prodname_registry %} usa los comandos de herramientas del paquete nativo con los que ya estás familiarizado para publicar e instalar versiones del paquete.
+#### Soporte para los registros de paquetes
+
+| Lenguaje   | Descripción                                                    | Formato del paquete                 | Cliente del paquete |
+| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- |
+| JavaScript | Gestor de paquetes Node                                        | `package.json`                      | `npm`               |
+| Ruby       | Gestor de paquetes RubyGems                                    | `Gemfile`                           | `gema`              |
+| Java       | Herramienta de administración y comprensión Apache Maven       | `pom.xml`                           | `mvn`               |
+| Java       | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle`            |
+| .NET       | Administración del paquete NuGet para .NET                     | `nupkg`                             | `dotnet` CLI        |
+| N/A        | Plataforma de administración del contenedor Docker             | `Dockerfile`                        | `Docker`            |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**Nota:** Docker no es compatible cuando inhabilitas el aislamiento de subdominios.
+
+{% endnote %}
+
+Para obtener más información acerca del aislamiento de subdominios, consulta la sección "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)".
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Administrar paquetes
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. Para obtener más información, consulta la sección "[API del {% data variables.product.prodname_registry %}](/rest/reference/packages)".
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. O, para los paquetes con alcance de repo, puedes borrar una versión de un paquete privado utilizando GraphQL.
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+Puedes borrar una versión de un paquete privado en la interface de usuario de {% data variables.product.product_name %} o utilizar la API de GraphQL.
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+Cuando usas la API de GraphQL para consultar y eliminar paquetes privados, debes usar el mismo token que usas para autenticarte en {% data variables.product.prodname_registry %}. Para obtener más información, consulta las secciones "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}" y "[Formar llamados con GraphQL](/graphql/guides/forming-calls-with-graphql)".
+
+Puedes configurar webhooks para suscribirte a eventos relacionados con paquetes, como cuando se publica o se actualiza un paquete. Para obtener más información, consulta el "[evento de webhook de `package`](/webhooks/event-payloads/#package)".
+
+### Contactar con soporte técnico
+
+{% if currentVersion == "free-pro-team@latest" %}
+Si tienes comentarios o solicitudes de características para {% data variables.product.prodname_registry %}, usa el formulario de comentarios de [ para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages).
+
+Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si:
+
+* Experimentas alguna cosa que contradice la documentación
+* Encuentras errores vagos o poco claros
+* Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal
+
+{% else %}
+Si necesitas soporte para {% data variables.product.prodname_registry %}, por favor, contacta a tus administradores de sitio.
+
+{% endif %}
diff --git a/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md b/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md
index 5fd02e6d49..30d4e25960 100644
--- a/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md
+++ b/translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md
@@ -19,7 +19,7 @@ versions:
 
 Puedes ayudar a la gente a entender y usar tu paquete proporcionando una descripción y otros detalles como instrucciones de instalación y uso en la página del paquete. GitHub proporciona metadatos para cada versión, como la fecha de publicación, la actividad de descarga y las versiones recientes. Para obtener una página de paquete de ejemplo, consulta [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
 
-{% data reusables.package_registry.public-or-private-packages %} Un repositorio puede contener más de un paquete. Para evitar confusiones, asegúrate de que el archivo README y la descripción proporcionen información clara de cada paquete.
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. Para evitar confusiones, asegúrate de que el archivo README y la descripción proporcionen información clara de cada paquete.
 
 {% if currentVersion == "free-pro-team@latest" %}
 Si una versión nueva de un paquete soluciona una vulnerabilidad de seguridad, deberás publicar una asesoría de seguridad en tu repositorio.
@@ -30,10 +30,10 @@ Si una versión nueva de un paquete soluciona una vulnerabilidad de seguridad, d
 
 Puedes publicar un paquete en el {% data variables.product.prodname_registry %} utilizando cualquier {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}cliente de paquetes compatible{% else %} tipo de paquete habilitado para tu instancia{% endif %} si sigues los mismos lineamientos generales.
 
-1. Crea o usa un token de acceso existente con los ámbitos adecuados para la tarea que deseas realizar. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)".
+1. Crea o usa un token de acceso existente con los ámbitos adecuados para la tarea que deseas realizar. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 2. Autentícate en {% data variables.product.prodname_registry %} mediante tu token de acceso y las instrucciones para tu cliente del paquete.
 3. Publica el paquete siguiendo las instrucciones para el cliente de tu paquete.
 
-Para obtener instrucciones específicas para tu cliente de paquete, consulta "[Usar {% data variables.product.prodname_registry %} con el ecosistema de tu proyecto](/packages/using-github-packages-with-your-projects-ecosystem)".
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
 
-Después de que publiques un paquete, puedes verlo en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Ver paquetes](/packages/publishing-and-managing-packages/viewing-packages)."
+Después de que publiques un paquete, puedes verlo en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/learn-github-packages/viewing-packages)".
diff --git a/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md b/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..0ed85180fd
--- /dev/null
+++ b/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: Visualizar paquetes
+intro: Puedes ver los detalles de los paquetes que se publican en un repositorio y filtrar los resultados por organización o usuario.
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Ver paquetes de un repositorio
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### Visualizar los paquetes de un repositorio
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Visualizar los paquetes de una organización
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. Debajo del nombre de tu organización, haz clic en {% octicon "package" aria-label="The package icon" %} **Packages (Paquetes)**.
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Visualizar tus paquetes
+
+You can find and view any package you've published across all organizations and repositories.
+
+{% data reusables.profile.access_profile %}
+2. En la zona de navegación principal, sobre la página de perfil, da clic en **Paquetes**. ![Pestaña Project (Proyecto)](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Leer más
+
+- "[Buscar paquetes](/github/searching-for-information-on-github/searching-for-packages)"
diff --git a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..db022b22ec
--- /dev/null
+++ b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: About GitHub Packages and GitHub Actions
+intro: Learn the fundamentals of managing packages through your {% data variables.product.prodname_actions %} workflows.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..6bbb1f5ede
--- /dev/null
+++ b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: Example workflows for publishing a package
+intro: 'To help you get started with your own custom workflows, review some example workflows for publishing packages.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+You can find example workflows in "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
+
+  - [Publicar paquetes Node.js](/actions/guides/publishing-nodejs-packages)
+  - [Publicar imágenes de Docker](/actions/guides/publishing-docker-images)
+  - [Publicar paquetes Java con Maven](/actions/guides/publishing-java-packages-with-maven)
+  - [Publicar paquetes Java con Gradle](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..790a661916
--- /dev/null
+++ b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: Managing GitHub packages using GitHub Actions workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'You can safely publish and consume packages by building custom workflows that can also build, test, and deploy your code.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..f030a0d20d
--- /dev/null
+++ b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,450 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'Puedes configurar un flujo de trabajo en {% data variables.product.prodname_actions %} para publicar o instalar automáticamente un paquete desde {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### Acerca de {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+Puedes ampliar las capacidades de CI y CD de tu repositorio publicando o instalando paquetes como parte de tu flujo de trabajo.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+Para ver un ejemplo de autenticación, consulta la sección "[Autenticarse con el {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)".
+
+{% endif %}
+
+#### Autenticarse en los registros de paquetes en {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}Si quieres que tu flujo de trabajo se autentique en {% data variables.product.prodname_registry %} para acceder a un registro de paquetes diferente al {% data variables.product.prodname_container_registry %} en {% data variables.product.product_name %}, entonces{% else %}Para autenticarse en los registros de paquetes de {% data variables.product.product_name %},{% endif %} te recomendamos utilizar el `GITHUB_TOKEN` que {% data variables.product.product_name %} crea automáticamente para tu repositorio cuando habilitas las {% data variables.product.prodname_actions %} en vez de un token de acceso personal para autenticación. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}Debes configurar los permisos para este token de acceso en el archivo del flujo de trabajo para otorgar acceso de lectura para el alcance `contents` y acceso de escritura para el de `packages`. {% else %}Tiene permisos de lectura y escritura para los paquetes del repositorio en donde se ejecuta el flujo de trabajo. {% endif %}Para las bifurcaciones, se otorga acceso de lectura al `GITHUB_TOKEN` en el repositorio padre. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+
+Puedes hacer referencia al `GITHUB_TOKEN` en tu archivo de flujo de trabajo mediante el contexto {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+### Acerca de los permisos y acceso a los paquetes para los paquetes que pertenecen a los repositorios
+
+{% note %}
+
+**Nota:** Los paquetes que pertenecen a los repositorios incluyen paquetes de RubyGems, npm, Apache Maven, NuGet, Gradle, y Docker que utilizan el espacio de nombres `docker.pkg.github.com`.
+
+{% endnote %}
+
+Cuando habilitas las Acciones de GitHub, GitHub instala una App GitHub en tu repositorio. El secreto del `GITHUB_TOKEN` es un token de acceso a la instalación de GitHub App. Puedes utilizar el token de acceso a la instalación para autenticarte en nombre de la GitHub App instalada en tu repositorio. Los permisos del token están limitados al repositorio que contiene tu flujo de trabajo. Para obtener más información, consulta la sección "[Permisos para el GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)".
+
+El {% data variables.product.prodname_registry %} te permite subir y extraer paquetes mediante el `GITHUB_TOKEN` que está disponible para un flujo de trabajo de {% data variables.product.prodname_actions %}.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Acerca de los permisos y el acceso de paquetes para el {% data variables.product.prodname_container_registry %}
+
+El {% data variables.product.prodname_container_registry %} (`ghcr.io`) permite a los usuarios crear y administrar contenedores como recursos independientes a nivel organizacional. Los contenedores pueden pertenecer a una organización o a una cuenta de usuario personal y puedes personalizar el acceso para cada uno de tus contenedores por aparte de los permisos del repositorio.
+
+Todos los flujos de trabajo que accedan al {% data variables.product.prodname_container_registry %} deben utilizar el `GITHUB_TOKEN` en vez de un token de acceso personal. Para obtener más información acerca de las mejores prácticas de seguridad, consulta la sección "[Fortalecimiento de seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)".
+
+### Configuración de acceso y permisos predeterminados para los contenedores que se modifican a través de los flujos de trabajo
+
+Cuando creas, instalas, modificas o borras un contenedor a través de un flujo de trabajo, hay algunos permisos y configuraciones de acceso predeterminados que se utilizan para garantizar que los administradores tengan acceso al fluljo de trabajo. También puedes ajustar esta configuración de acceso.
+
+Por ejemplo, predeterminadamente, si un flujo de trabajo crea un contenedor que utilice el `GITHUB_TOKEN`, entonces:
+- El contenedor hereda la visibilidad el modelo de permisos del repositorio en donde se ejecuta el flujo de trabajo.
+- Los administradores de repositorio donde se ejecuta el flujo de trabajo se convierten en los administradores del contenedor una vez que este se cree.
+
+Estos son más ejemplos de cómo funcionan los permisos predeterminados para los flujos de trabajo que administran paquetes.
+
+| Tarea de flujo de trabajo de {% data variables.product.prodname_actions %} | Acceso y permisos predeterminados                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Descargar un contenedor existente                                          | - Si el contenedor es público, cualquier flujo de trabajo que se ejecute en cualquier repositorio puede descargar el contenedor. <br> - Si el contenedor es interno, entonces todos los flujos de trabajo que se ejecuten en un repositorio que pertenezca a la cuenta empresarial podrá descargarlo. Para las organziaciones que pertenecen a una empresa, puedes leer cualquier repositorio en la empresa <br> - Si el contenedor es privado, solo los flujos de trabajo que se ejecuten en los repositorios a los que se les otorga permiso de lectura en dicho contenedor podrán descargarlo. <br> |
+| Carga una versión nueva a un contenedor existente                          | - Si el contenedor es privado, interno, o público, solo los flujos de trabajo que se ejecuten en repositorios que tengan el permiso de escritura en dicho contenedor podrán cargar versiones nuevas de este.                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Borrar un contenedor o versiones de un contenedor                          | - Si el contenedor es privado, interno o público, solo los flujos de trabajo que se ejecuten en los repositorios a los que se les otorga permiso de borrado podrán borrar las versiones existentes de este.                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+También puedes ajustar el acceso a los contenedores de forma más granular o ajustar el comportamiento de algunos de los permisos predeterminados. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publicar un paquete mediante una acción
+
+Puedes utilizar {% data variables.product.prodname_actions %} para publicar paquetes automáticamente como parte de tu flujo de integración contínua (IC). Este acercamiento a los despliegues contínuos (DC) te permite automatizar la creación de nuevas versiones de los paquetes si el código cumple con tus estándares de calidad. Por ejemplo, podrías crear un flujo de trabajo que ejecute pruebas de IC cada vez que un desarrollador suba código a alguna rama en particular. Si estas pruyebas pasan, el flujo de trabajo puede publicar una versión nueva del paquete en el {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+El siguiente ejemplo ilustra cómo puedes utilizar las {% data variables.product.prodname_actions %} para crear y probar tu app, y luego crear atuomáticamente una imagen de Docker y publicarla en el {% data variables.product.prodname_registry %}:
+
+- Crea un archivo de flujo de trabajo nuevo en tu repositorio (tal como `.github/workflows/deploy-image.yml`), y agrega el siguiente YAML:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  La configuración relevante se explica en la siguiente tabla: <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configura el flujo de trabajo de <code>Create and publish a package</code> para que se ejecute cada que se suba un cambio a la rama que se llama <code>release</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    Este job instala NPM y lo utiliza para crear la app.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Este job utiliza <code>npm test</code> para probar el código. El comando <code>needs: run-npm-build</code> hace que este job dependa del job <code>run-npm-build</code>.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Configura los permisos que se otorgan al <code>GITHUB_TOKEN</code> para las acciones en este job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Crea un paso nuevo que se llama <code>Build container image</code>. Este paso se ejecuta como parte del job <code>build-and-push-image</code>. El comando <code>needs: run-npm-test</code> hace que este job dependa del job <code>run-npm-test</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Utiliza la acción <code>build-push-action</code> de Docker para crear la imagen, basándose en el <code>Dockerfile</code> de tu repositorio. Si la compilación es exitosa, sube la imagen al {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Envía los parámetros requeridas a la acción <code>build-push-action</code>. Este se define en las línas siguientes.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Define la cuenta de usuario que publicará los paquetes. Una vez que se publica, los paquetes pertenecerán a la cuenta que se define aquí.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Define la contraseña que se utiliza para acceder al {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Deifne el registro que hospedará los paquetes resultantes. Este ejemplo utiliza el {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Reemplaza a <code>YOUR-HOSTNAME</code> con el nombre de tu empresa.{% endif %} {% if currentVersion == "free-pro-team@latest" %} Si estás utilizando el {% data variables.product.prodname_container_registry %}, entonces utiliza <code>ghcr.io</code> como nombre de host.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Deifne qué repositorio hospedará el paquete resultante y configura el nombre del paquete publicado. Reemplaza a <code>octo-image</code> con el nombre que quieres para tu paquete.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Etiqueta el paquete publicado con los siete caracteres principales del SHA de la confirmación. Por ejemplo, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Etiqueta el paquete publicado con la referencia de git. Esta puede ser el nombre de la rama que se utilizó para crear el paquete.
+  </td>
+  </tr>
+  </table>
+
+- Este flujo de trabajo nuevo se ejecutará automáticamente cada que subas un cambio a una rama que se llame `release` en el repositorio. Puedes ver el progreso en la pestaña de **Acciones**.
+- Unos minutos después de que se complete el flujo de trabajo, el paquete nuevo podrá visualizarse en tu repositorio. Para encontrar tus paquetes disponibles, consulta la sección "[Visualizar los paquetes de un repositorio](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)".
+
+
+### Instalar un paquete mediante una acción
+
+Puedes instalar paquetes como parte de tu flujo de CI mediante {% data variables.product.prodname_actions %}. Por ejemplo, podrías configurar un flujo de trabajo para que cada vez que un programador suba código a una solicitud de extracción, el flujo de trabajo resuelva las dependencias al descargar e instalar paquetes alojados por el {% data variables.product.prodname_registry %}. Luego, el flujo de trabajo puede ejecutar pruebas de CI que requieran las dependencias.
+
+El instalar los paquetes que hospeda el {% data variables.product.prodname_registry %} a través de las {% data variables.product.prodname_actions %} requiere una configuración mínima o autenticación adicional cuando utilizas un `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} También, la transferencia de datos es gratuita cuando una acción instala un paquete. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Actualizar un flujo de trabajo que tiene acceso a `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+El utilizar el `GITHUB_TOKEN` en vez de un PAT, el cual incluya el alcance de `repo`, incrementa la seguridad de tu repositorio, ya que no necesita sutilizar un PAT de vida extendida que ofrezca acceso innecesario al repositorio en donde se ejecuta tu flujo de trabajo. Para obtener más información acerca de las mejores prácticas de seguridad, consulta la sección "[Fortalecimiento de seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)".
+
+1. Navega a la página de llegada de tu paquete.
+1. En la barra lateral izquierda, haz clic en **Acceso a las acciones**. ![Opción "Acceso a las acciones" en el menú izquierdo](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Para asegurarte de que tu paquete de contenedor tenga acceso a tu flujo de trabajo, debes agregar el repositorio en donde se almacena el flujo de trabajo a tu contenedor. Haz clic en **Agregar repositorio** y busca el repositorio que quieres agregar. ![Botón "Agregar repositorio"](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Nota:** Agregar un repositorio a tu contenedor a través de la opción de menú **Acceso de las acciones** es diferente que conectar tu contenedor a un repositorio. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Opcionalmente, utiliza el menú desplegable de "rol", selecciona el nivel de acceso predeterminado que te gustaría que tuviera el repositorio en tu imagen de contenedor. ![Niveles de acceso de permisos para otorgar a los repositorios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Abre tu archivo de flujo de trabajo. En la línea en donde ingresas a `ghcr.io`, reemplaza tu PAT con {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+Por ejemplo, este flujo de trabajo publica un contenedor de Docker utilizando {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} para autenticarse.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md
index 4b1c6f0287..e9d193771f 100644
--- a/translations/es-ES/content/packages/quickstart.md
+++ b/translations/es-ES/content/packages/quickstart.md
@@ -71,7 +71,10 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -95,7 +98,7 @@ En esta guía, crearás un flujo de trabajo de {% data variables.product.prodnam
 
 ### Visualizar tu paquete publicado
 
-Los paquetes se publican a nivel del repositorio. Puedes ver todos los paquetes en un repositorio y buscar un paquete específico.
+You can view all of the packages you have published.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ Los paquetes se publican a nivel del repositorio. Puedes ver todos los paquetes
 
 ### Instalar un paquete publicado
 
-Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. Para obtener más información, consulta la sección "[Configurar npm para utilizarlo con el {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)".
+Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
 
 ### Pasos siguientes
 
-El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. Pero, este es solo el principio de lo que puedes hacer con {% data variables.product.prodname_registry %}. Puedes publicar tu paquete en varios registros con un solo flujo de trabajo, activar el flujo de trabajo para que se ejecute en eventos diferentes tales como una solicitud de cambios fusionada, administrar contenedores, y más.
+El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. Puedes publicar tu paquete en varios registros con un solo flujo de trabajo, activar el flujo de trabajo para que se ejecute en eventos diferentes tales como una solicitud de cambios fusionada, administrar contenedores, y más.
 
 El combinar el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu proceso de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí hay algunos recursos útiles para llevar a cabo los siguientes pasos con el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_actions %}:
 
 - "[Aprende sobre el {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para un tutorial más a fondo de GitHub Packages
 - "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para un tutorial más a fondo de GitHub Actions
-- "[Guías](/packages/guides)" para los casos de uso y ejemplos específicos
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..1cbb38a25d
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: Enabling improved container support with the Container registry
+intro: 'To use the {% data variables.product.prodname_container_registry %}, you must enable it for your user or organization account.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. Para obtener más información, consulta la sección "[Introducción a las {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)".
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your personal account
+
+Once the {% data variables.product.prodname_container_registry %} is enabled for your personal user account, you can publish containers to the {% data variables.product.prodname_container_registry %} owned by your user account.
+
+To use the {% data variables.product.prodname_container_registry %} within an organization, the organization owner must enable the feature for organization members.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. A la izquierda, selecciona "mejorar el soporte de contenedores" y luego da clic en **Habilitar**. ![Soporte de contenedores mejorado](/assets/images/help/settings/improved-container-support.png)
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your organization account
+
+Before organization owners or members can publish container images to the {% data variables.product.prodname_container_registry %}, an organization owner must enable the feature preview for the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. A la izquierda, da clic en **Paquetes**.
+5. Debajo de "Soporte mejorado para contenedores", selecciona "Habilitar el soporte mejorado para contenedores" y da clic en **Guardar**. ![Opción para habilitar el soporte del registro de contenedores y botón de guardar](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. Debajo de "Creación de contenedores", elige si quieres habilitar la creación de imágenes de contenedor públicas, privadas o internas.
+    - To enable organization members to create public container images, select **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, select **Private**. Puedes personalizar aún más la visibilidad de las imagenes de contenedor privadas. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, select **Internal**. ![Opciones de visibilidad para las imágenes de contenedor que publican los miembros de la organización](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/index.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..2d63b2b150
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with a GitHub Packages registry
+shortTitle: Working with a GitHub Packages registry
+intro: 'Learn how to use a supported {% data variables.product.prodname_registry %} registry.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### Índice
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..8213941bff
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,124 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- Almacenar imágenes de contenedor dentro de tu organización y cuenta de usuario, en vez de en un repositorio.
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- Acceder a imágenes de contenedores públicos anónimamente.
+
+|                          | Docker registry                                                                                                                                                                                                                                                                                           | {% data variables.product.prodname_container_registry %}
+| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Ubicaciones de hospedaje | You can host multiple Docker images in one repository.                                                                                                                                                                                                                                                    | Puedes hospedar imagenes de contenedor múltiples en una cuenta de organización o de usuario.                                                                                                                 |
+| Permisos                 | Each image inherits the permissions of the repository where the image is hosted. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | Para cada imagen de contenedor, puedes elegir el nivel de acceso que tienen los demás. Los permisos para acceso a la imagen de contenedor son independientes de aquellos para tu organización y repositorio. |
+ Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. Solo las personas y equipos a las cuales se les haya otorgado acceso dentro de tu organización podrán ver las imágenes de contenedor privadas. Cualquiera puede ver las imágenes de contenedor públicas. | Anonymous access    | N/A | You can access public container images anonymously. Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### Cambios en la facturación
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".
+
+### Cambios de dominio
+
+El dominio para el {% data variables.product.prodname_container_registry %} es `ghcr.io`.
+
+| Registro                                                               | URL de Ejemplo                                      |
+| ---------------------------------------------------------------------- | --------------------------------------------------- |
+| Registro de Docker para {% data variables.product.prodname_registry %} | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` |
+| {% data variables.product.prodname_container_registry %}             | `ghcr.io/OWNER/IMAGE_NAME`                          |
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+Necesitarás autenticarte en el {% data variables.product.prodname_container_registry %} con la URL base `ghcr.io`. Te recomendamos crear un token de acceso nuevo para utilizar el {% data variables.product.prodname_container_registry %}.
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Migrar la imagen de Docker utilizando el Docker CLI
+
+Para mover las imágenes de Docker que hospedes en el registro de Docker para {% data variables.product.prodname_registry %} debes republicar las imágenes en {% data variables.product.prodname_container_registry %}. Te recomendamos volver a publicar tus imágenes existentes de Docker utilizando la línea de comandos en tu máquina local.
+
+1. Ingresa en el registro de Docker utilizando un PAT temporal con un alcance mínimo de `read:packages`. Este PAT solo se utilizará para ingresar al registro de Docker para extraer imágenes y puede borrarse después.
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. Extrae la imagen que quieres migrar reemplazando OWNER con el nombre de la cuenta de usuario u organización a la que pertenece el repositorio, REPOSITORY con el nombre del repositorio que contiene tu proyecto, IMAGE_NAME con el nombre del paquete o imagen, y VERSION con la etiqueta para la imagen que quieres instalar. Por ejemplo, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` extraerá la última etiqueta de la imagen `octoshift/octoshift` en la organización octo-org.
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. Vuelve a etiquetar la imagen con el dominio nuevo y con un nombre de imagen nuevo. Para obtener más información, consulta "[Etiqueta Docker](https://docs.docker.com/engine/reference/commandline/tag/)" en la documentación de Docker. Utiliza la misma URL que utilizaste en el paso anterior para la SOURCE URL. Reemplaza el TARGET_OWNER con el usuario u organización al cual estás migrando la imagen de contenedor y reemplaza TARGET_IMAGE_NAME con el nombre de imagen para {% data variables.product.prodname_container_registry %} nuevo.
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. Ingresa al nuevo {% data variables.product.prodname_container_registry %}. Te recomendamos crear un PAT limitado nuevo con los alcances de `read:packages` y `write:packages`, dado que ya no necesitas el alcance `repo` y tu PAT anterior podría no tener el alcance `write:packages`.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. Sube tu imagen reetiquetada al {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+Si tienes un flujo de trabajo de {% data variables.product.prodname_actions %} que utiliza una imagen de Docker desde el registro de Docker para {% data variables.product.prodname_registry %}, tal vez quieras actualizarlo al {% data variables.product.prodname_container_registry %} para permitir el acceso anónimo para las imágenes de contenedor públicas, permisos de acceso más específicos, y para tener mejor compatibilidad de almacenamiento y ancho de banda para los contenedores.
+
+1. Migra tus imágenes de Docker al nuevo {% data variables.product.prodname_container_registry %} en `ghcr.io`. Para encontrar un ejemplo, consulta la sección "[Migrar una imagen de Docker utilizando el CLI de Docker](#migrating-a-docker-image-using-the-docker-cli)".
+
+2. En tu archivo de flujo de trabajo de {% data variables.product.prodname_actions %}, actualiza la url del paquete de `https://docker.pkg.github.com` a `ghcr.io`.
+
+3. Agrega tu token de acceso personal (PAT) para autenticación en el {% data variables.product.prodname_container_registry %} como un secreto de GitHub Actions. The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. Para obtener más información, consulta "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
+
+4. En tu archivo de flujo de trabajo de {% data variables.product.prodname_actions %}, actualiza el PAT de autenticación reemplazando tu PAT del registro de Docker ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) con una variable nueva para tu PAT del {% data variables.product.prodname_container_registry %}, tal como {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}.
+
+#### Ejemplo de un flujo de trabajo actualizado
+
+Si parte de tu flujo de trabajo accedió a una imagen de Docker que se hospeda en el registro de Docker de esta forma:
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+Entonces necesitarás actualizar tu flujo de trabajo con la URL de {% data variables.product.prodname_container_registry %} y PAT nuevos de esta forma:
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..c7140bfc3c
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Working with the Apache Maven registry
+intro: 'Puedes configurar Apache Maven para publicar paquetes para {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto Java.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows.
+
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Autenticarte con un token de acceso personal
+
+{% data reusables.package_registry.required-scopes %}
+
+Puedes autenticar en {% data variables.product.prodname_registry %} con Apache Maven editando tu archivo *~/.m2/settings.xml* para incluir tu token de acceso personal. Crear un nuevo archivo *~/.m2/settings.xml* si no existe uno.
+
+En la etiqueta `servidores`, agrega una etiqueta `servidor` hijo con una `Id`, reemplazando *USERNAME* con tu nombre de usuario {% data variables.product.prodname_dotcom %} y *Token* con tu token de acceso personal.
+
+En la etiqueta `repositorios`, configura un repositorio al mapear el `Id` del repositorio a la `Id` que agregaste en la etiqueta `servidor` que contiene tus credenciales. Replace {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Dado que las letras mayúsculas no son compatibles, debes usar minúsculas para el propietario del repositorio si el nombre de usuario o el nombre de la organización de {% data variables.product.prodname_dotcom %} contiene letras mayúsculas.
+
+Si deseas interactuar con múltiples repositorios, puedes agregar cada repositorio para separar hijos del `repositorio` en la etiqueta `repositorios`, asignando la `Id` de cada una a las credenciales en la etiqueta `servidores`.
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### Publicar un paquete
+
+{% data reusables.package_registry.default-name %} Por ejemplo, {% data variables.product.prodname_dotcom %} publicará un paquete denominado `com.example:test` en un repositorio llamado `OWNER/test`.
+
+Si quisieras publicar paquetes múltiples en el mismo repositorio, puedes incluir la URL del mismo en el `<distributionManagement>`elemento del archivo *pom.xml*. {% data variables.product.prodname_dotcom %} coincidirá con el repositorio según ese campo. Dado que el nombre del repositorio también es parte del elemento `distributionManagement`, no hay pasos adicionales para publicar múltiples paquetes en el mismo repositorio.
+
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+
+1. Edita el elemento `distributionManagement` del archivo *pom.xml* que se ubica en tu directorio de paquete, reemplazando {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* con el nombre del host de {% data variables.product.product_location %}, {% endif %}`OWNER` con el nombre de la cuenta organizacional o de usuario a la que pertenece el repositorio y `REPOSITORY` con el nombre del repositorio que contiene tu proyecto.{% if enterpriseServerVersions contains currentVersion %}
+
+  Si tu instancia tiene habilitado el aislamiento de subdominio:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. Publicar el paquete.
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Instalar un paquete
+
+Para instalar un paquete de Apache Maven desde {% data variables.product.prodname_registry %}, edita el *POM. XML* archivo para incluir el paquete como una dependencia. Si deseas instalar paquetes desde más de un repositorio, agrega una etiqueta `repositorio` para cada uno. Para obtener más información acerca del uso de un archivo *pom.xml* en tu proyecto, consulta "[Introducción al POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)"en la documentación de Apache Maven.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Agrega las dependencias del paquete al elemento `dependencias` del archivo *pom.xml* de tu proyecto, reemplazando `com.example:test` con tu paquete.
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. Instala el paquete.
+
+  ```shell
+  $ mvn install
+  ```
+
+### Leer más
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..0ab1488a4d
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://ghcr.io`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About {% data variables.product.prodname_container_registry %} support
+
+To push and pull container images, an organization admin or the owner of a personal account must enable the {% data variables.product.prodname_container_registry %}. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+When installing or publishing a Docker image, the Container registry supports foreign layers, such as Windows images.
+
+El {% data variables.product.prodname_container_registry %} es actualmente compatible con los siguientes formatos de contenedores de imagen:
+
+* [Docker Image Manifest V2, Modelo 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Especificaciones de Open Container Initiavie (OCI)](https://github.com/opencontainers/image-spec)
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Subir imágenes de contenedor
+
+Este ejemplo sube la última versión de `IMAGE-NAME`.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+Este ejemplo sube la versión `2.5` de la imagen.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+Cuando publicas un paquete por primera vez, la visibilidad predeterminada es privada. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+### Extraer imágenes de contenedor
+
+#### Extraer por resúmen
+
+Para garantizar que siempre utilices la misma imagen, puedes especificar la versión exacta de la imagen de contenedor que quieres extraer de acuerdo con su valor de SHA de `digest`.
+
+1. Para encontrar el valor de SHA de resúmen, utiliza `docker inspect` o `docker pull` y copia el valor de SHA después de `Digest:`
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. Elimina la imagen localmente de acuerdo a tus necesidades.
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+3. Extrae la imagen de contenedor con `@YOUR_SHA_VALUE` después del nombre de dicha imagen.
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### Extraer por nombre
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### Extraer por nombre y versión
+
+Ejemplo de CLI de Docker que muestra una imagen que se extrae por su nombre y por la etiqueta de la versión `1.14.1`:
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### Extraer por nombre y última versión
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### Crear imagenes de contenedor
+
+Este ejemplo crea la imagen `hello_docker`:
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### Etiquetar las imágenes de contenedor
+
+1. Encuentra la ID para la imagen de Docker que quieres etiquetar.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. Etiqueta tu imagen de Docker utilizando la ID ed imagen y el nombre que quieras poner a la misma, así como el destino en donde se hospedará ésta.
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..d15044518c
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,274 @@
+---
+title: Working with the Docker registry
+intro: 'You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows.
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+Antes de que puedas utilizar el registro de Docker en el {% data variables.product.prodname_registry %}, el administrador de sitio de {% data variables.product.product_location %} debe habilitar la compatibilidad de Docker y el aislamiento de subdominios para tu instancia. Para obtener más informacón, consulta la sección "[Administrar GitHub Packages para tu empresa](/enterprise/admin/packages)".
+
+{% endif %}
+
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Autenticarte con un token de acceso personal
+
+{% data reusables.package_registry.required-scopes %}
+
+Puedes autenticar a {% data variables.product.prodname_registry %} con Docker usando el comando de inicio de sesión `Docker`.
+
+Para mantener tus credenciales seguras, te recomendamos que guardes tu token de acceso personal en un archivo local de tu computadora y utilices el marcador `--password-stdin` de Docker, el cual lee tu token desde un archivo local.
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+{% endif %}
+{% raw %}
+ ```shell
+ $ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Etiqueta la imagen con <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Sube la imagen a {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+Para utilizar este ejemplo de comando de ingreso, reemplaza `USERNAME` con tu nombre de usuario de {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, `HOSTNAME` con la URL de {% data variables.product.product_location %},{% endif %} y `~/TOKEN.txt` con la ruta de archivo de tu token de acceso personal para {% data variables.product.product_name %}.
+
+Para obtener más información, consulta la sección "[Inicio de sesión de Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)."
+
+### Publicar una imagen
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**Nota:** Los nombres de imagen deben utilizar letras en minúscula únicamente.
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} admite varias imágenes Docker de primer nivel por repositorio. Un repositorio puede tener cualquier cantidad de etiquetas de imagen. Puedes experimentar un servicio de menor calidad al publicar o instalar imágenes de Docker de más de 10 GB, las capas tienen un límite de 5 GB cada una. Para obtener más información, consulta "[Etiqueta Docker](https://docs.docker.com/engine/reference/commandline/tag/)" en la documentación de Docker.
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. Determina el nombre y la ID de la imagen Docker utilizando `imágenes docker`.
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+  {% endif %}
+  ```shell
+  Puedes publicar una nueva imagen de Docker por primera vez y nombrarla <code>monalisa</code>.
+  ```
+.
+</code>
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. Publicar la imagen para {% data variables.product.prodname_registry %}.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **Nota:** Debes subir tu imagen usando `IMAGE_NAME: VERSION` y no utilizar `IMAGE_NAME: SHA`.
+
+  {% endnote %}
+
+#### Ejemplo de publicación de una imagen Docker
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Estos ejemplos asumen que tu instancia tiene habilitado el aislamiento de subdominios.
+{% endif %}
+
+Puedes publicar la versión 1.0 de la imagen `monalisa` en el repositorio `octocat/octo-app` usando una ID de imagen.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Etiqueta la imagen con <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Sube la imagen a {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+Puedes publicar una nueva imagen de Docker por primera vez y nombrarla `monalisa`.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# Construye la imagen con docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Asume que Dockerfile reside en el directorio de trabajo actual (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Sube la imagen a {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### Descargar una imagen
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+Puedes utilizar el comando `docker pull` para instalar una imagen de docker desde el {% data variables.product.prodname_registry %}, reemplazando a *OWNER* con el nombre de la cuenta de usuario u organización a la que pertenece el repositorio, a *REPOSITORY* con el nombre del repositorio que contiene tu proyecto, a *IMAGE_NAME* con el nombre del paquete o imagen,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} a *HOSTNAME* con el nombre de host de {% data variables.product.product_location %}, {% endif %} y a *TAG_NAME* con la etiqueta de la imagen que quieres instalar.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**Nota:** Debes extraer la imagen utilizando `IMAGE_NAME:VERSION` y no así, utilizando `IMAGE_NAME:SHA`.
+
+{% endnote %}
+
+### Leer más
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..f84249b88b
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows.
+
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### Autenticarte con un token de acceso personal
+
+{% data reusables.package_registry.required-scopes %}
+
+Puedes autenticar a {% data variables.product.prodname_registry %} con Gradle usando ya sea Gradle Groovy o Kotlin DSL editando tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL) para incluir tu token de acceso personal. También puedes configurar Gradle Groovy y Kotlin DSL para que reconozcan un paquete único o múltiples paquetes en un repositorio.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Reemplaza *REGISTRY-URL* con la URL para el registro Maven de tu instancia. Si tu instancia tiene habilitado el aislamiento de subdominios, utiliza `maven.HOSTNAME`. Si tu instancia tiene inhabilitado el aislamiento de subdominios, utiliza `HOSTNAME/_registry/maven`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.
+{% elsif currentVersion == "github-ae@latest" %}
+Reemplaza a *REGISTRY-URL* con la URL del registro de MAven de tu empresa, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.
+{% endif %}
+
+Reemplaza *USERNAME* con tu nombre de usuario {% data variables.product.prodname_dotcom %}, *TOKEN* con tu token de acceso personal, *REPOSITORY* con el nombre del repositorio que contiene el paquete que deseas publicar y *OWNER* con el nombre de la cuenta de usuario o de organización en {% data variables.product.prodname_dotcom %} que posee el repositorio. Dado que las letras mayúsculas no son compatibles, debes usar minúsculas para el propietario del repositorio si el nombre de usuario o el nombre de la organización de {% data variables.product.prodname_dotcom %} contiene letras mayúsculas.
+
+{% note %}
+
+**Nota:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Para obtener un ejemplo, consulta "[Configurar Apache Maven para usar con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)."
+
+{% endnote %}
+
+##### Ejemplo de uso de Gradle Groovy para un paquete único en un repositorio
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### Ejemplo usando Gradle Groovy para múltiples paquetes en el mismo repositorio
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### Ejemplo de uso de Kotlin DSL para un paquete único en el mismo repositorio
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### Ejemplo de uso de Kotlin DSL para múltiples paquetes en el mismo repositorio
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            register<MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+### Publicar un paquete
+
+{% data reusables.package_registry.default-name %} Por ejemplo, {% data variables.product.prodname_dotcom %} publicará un paquete denominado `com.example.test` en el repositorio `OWNER/test` {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Después de crear tu paquete, puedes publicar el paquete.
+
+  ```shell
+   $ gradle publish
+  ```
+
+### Instalar un paquete
+
+Puedes instalar un paquete agregando el paquete como una dependencia a tu proyecto. Para obtener más información, consulta "[Declarar dependencias](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" en la documentación de Gradle.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Agrega las dependencias del paquete a tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL).
+
+  Ejemplo utilizando Gradle Groovy:
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  Ejemplo de uso de Kotlin DSL:
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. Agrega el complemento Maven a tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL).
+
+  Ejemplo utilizando Gradle Groovy:
+  ```shell
+  plugins {
+      id 'maven'
+  }
+  ```
+  Ejemplo de uso de Kotlin DSL:
+  ```shell
+  plugins {
+      `maven`
+  }
+  ```
+
+  3. Instala el paquete.
+
+  ```shell
+  $ gradle install
+  ```
+
+### Leer más
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..d22e99563d
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,218 @@
+---
+title: Working with the npm registry
+intro: 'Puedes configurar npm para publicar paquetes en {% data variables.product.prodname_registry %} y para usar los paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto npm.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Límites para las versiónes de npm publicadas
+
+Si estableces más de 1,000 versiones de paquetes de npm en el {% data variables.product.prodname_registry %}, podrías notar que ocurren problemas de rendimiento y de tiempos excedidos durante el uso.
+
+En el futuro, para mejorar el rendimiento del servicio, no podrás publicar más de 1,000 versiones de un paquete en {% data variables.product.prodname_dotcom %}. Cualquier versión que se publique antes de llegar a este límite aún será legible.
+
+Si llegas a este límite, considera borrar las versiones del paquete o contacta a soporte para recibir ayuda. Cuando se aplique este límite, actualizaremos nuestra documentación con una forma de dar soluciones para él. Para obtener más información, consulta la sección "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}" o [Contactar a Soporte](/packages/learn-github-packages/about-github-packages#contacting-support)".
+
+{% endif %}
+
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Autenticarte con un token de acceso personal
+
+{% data reusables.package_registry.required-scopes %}
+
+Puedes autenticarte en {% data variables.product.prodname_registry %} con npm al editar tu archivo *~/.npmrc* por usuario para incluir tu token de acceso personal o al iniciar sesión en npm en la línea de comando por medio tu nombre de usuario y token de acceso personal.
+
+Para autenticarte agregando tu token de acceso personal a tu archivo *~/.npmrc*, edita el archivo *~/.npmrc* para que tu proyecto incluya la siguiente línea, reemplazando a{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* con el nombre de host de {% data variables.product.product_location %} y a {% endif %}*TOKEN* con tu token de acceso personal. Crea un nuevo archivo *~/.npmrc* si no existe uno.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+```shell
+$ npm login --registry=https://npm.pkg.github.com
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+Para autenticarte al iniciar sesión en npm, usa el comando `npm login`, reemplaza *USERNAME* por tu nombre de usuario de {% data variables.product.prodname_dotcom %}, *TOKEN* por tu token de acceso personal y *PUBLIC-EMAIL-ADDRESS* por tu dirección de correo electrónico.
+
+Si el {% data variables.product.prodname_registry %} no es tu registro de paquetes predeterminado para utilizar npm y quieres utilizar el comando `npm audit`, te recomendamos que utilices el marcador `--scope` con el propietario del paquete cuando te autentiques en {% data variables.product.prodname_registry %}.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### Publicar un paquete
+
+{% note %}
+
+**Nota:** Los nombres y alcances de los paquetes deben escribirs exclusivamente en minúscula.
+
+{% endnote %}
+
+De forma predeterminada, {% data variables.product.prodname_registry %} publica un paquete en el repositorio de {% data variables.product.prodname_dotcom %} que especifiques en el campo nombre del archivo *package.json*. Por ejemplo, si publicas un paquete denominado `@my-org/test` en el repositorio de `my-org/test` {% data variables.product.prodname_dotcom %}. Puedes agregar un resumen para la página de descripción del paquete al incluir un archivo *README.md* en el directorio de tu paquete. Para obtener más información, consulta "[Trabajar con package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" y "[Cómo crear módulos Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" en la documentación de npm.
+
+Puedes publicar varios paquetes en el mismo repositorio de {% data variables.product.prodname_dotcom %} al incluir un campo `URL` en el archivo *package.json*. Para obtener más información, consulta "[Publicar varios paquetes en el mismo repositorio](#publishing-multiple-packages-to-the-same-repository)".
+
+Puedes configurar la asignación de alcance de tu proyecto por medio de un archivo *.npmrc* local en el proyecto o mediante la opción `publishConfig` en *package.json*. {% data variables.product.prodname_registry %} solo admite paquetes npm con alcance definido. Los paquetes con alcance definido tienen nombres con el formato de `@owner/name`. Además, siempre comienzan con un símbolo `@`. Es posible que tengas que actualizar el nombre en tu *package.json* para usar el nombre de alcance definido. Por ejemplo, `"name": "@codertocat/hello-world-npm"`.
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### Publicar un paquete por medio de un archivo *.npmrc* local
+
+Puedes usar un archivo *.npmrc* para configurar la asignación del alcance de tu proyecto. En el archivo *.npmrc*, usa la URL y el propietario de la cuenta de {% data variables.product.prodname_registry %} para que {% data variables.product.prodname_registry %} sepa dónde enrutar las solicitudes del paquete. Usar un archivo *.npmrc* impide que otros programadores publiquen accidentalmente el paquete en npmjs.org en lugar de {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Verifica el nombre de tu paquete en el *package.json* de tu proyecto. El campo `name (nombre)` debe contener el alcance y el nombre del paquete. Por ejemplo, si tu paquete se denomina "test" (prueba) y vas a publicar en la organización "My-org" de {% data variables.product.prodname_dotcom %}, el campo `name (nombre)` de tu *package.json* debería ser `@my-org/test`.
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### Publicar un paquete por medio de `publishConfig` en el archivo *package.json*
+
+Puedes usar el elemento `publishConfig` en el archivo *package.json* para especificar el registro en el que deseas que se publique el paquete. Para obtener más información, consulta "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" en la documentación de npm.
+
+1. Edita el archivo *package.json* de tu paquete e incluye una entrada de `publishConfig`.
+  {% if enterpriseServerVersions contains currentVersion %}
+  Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### Publicar varios paquetes en el mismo repositorio
+
+Para publicar varios paquetes en el mismo repositorio, puedes incluir la URL del repositorio de {% data variables.product.prodname_dotcom %} en el campo `repository (repositorio)` del archivo *package.json* para cada paquete.
+
+Para asegurarte de que la URL del repositorio sea correcta, reemplaza REPOSITORY por el nombre del repositorio que contiene el paquete que deseas publicar y OWNER por el nombre de la cuenta de usuario o de organización en {% data variables.product.prodname_dotcom %} que posee el repositorio.
+
+{% data variables.product.prodname_registry %} coincidirá con el repositorio en base a la URL, en lugar de basarse en el nombre del paquete.
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### Instalar un paquete
+
+Puedes instalar paquetes desde {% data variables.product.prodname_registry %} al agregar los paquetes como dependencias en el archivo *package.json* para tu proyecto. Para obtener más información sobre el uso de un *package.json* en tu proyecto, consulta "[Trabajar con package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" en la documentación de npm.
+
+Por defecto, puedes agregar paquetes de una organización. Para obtener más información, consulta la sección "[Instalar paquetes de otras organizaciones](#installing-packages-from-other-organizations)".
+
+También debes agregar el archivo *.npmrc* a tu proyecto por lo que todas las solicitudes de instalación de paquetes pasarán por {% data variables.product.prodname_registry %}. Cuando enrutas todas las solicitudes de paquete a través de {% data variables.product.prodname_registry %}, puedes usar paquetes con alcance definido y sin alcance definido de *npmjs.com*. Para obtener más información, consulta "[npm-scope](https://docs.npmjs.com/misc/scope)" en la documentación de npm.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. Configura *package.json* en tu proyecto para usar el paquete que estás instalando. Para agregar las dependencias de tu paquete al archivo *package.json* para {% data variables.product.prodname_registry %}, especifica el nombre del paquete de alcance completo, como `@my-org/server`. Para paquetes de *npmjs.com*, especifica el nombre completo, como `@babel/core` o `@lodash`. Por ejemplo, el archivo *package.json* a continuación utiliza el paquete `@octo-org/octo-app` como una dependencia.
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. Instala el paquete.
+
+  ```shell
+  $ npm install
+  ```
+
+#### Instalar paquetes de otras organizaciones
+
+Por defecto, solo puedes usar paquetes de {% data variables.product.prodname_registry %} de una organización. Si te gustaría enrutar las solicitudes de paquetes a organizaciones y usuarios múltiples, puedes agregar líneas adicionales a tu archivo de *.npmrc*, reemplazando a {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* con el nombre de host de {% data variables.product.product_location %} y a {% endif %}*OWNER* con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Para obtener más información acerca de cómo crear un paquete, consulta la [documentación maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### Utilizar el registro oficial de NPM
+
+El {% data variables.product.prodname_registry %} te permite acceder al registro oficial de NPM en `registry.npmjs.com`, si tu administrador de {% data variables.product.prodname_ghe_server %} habilitó esta característica. Para obtener más información, consulta la sección [Conectarse al registro oficial de NPM](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
+{% endif %}
+
+### Leer más
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..abe2402fef
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,237 @@
+---
+title: Working with the NuGet registry
+intro: 'Puedes configurar la interfaz de línea de comando (CLI) `dotnet` para publicar paquetes NuGet en {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto de .NET.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows.
+
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Autenticarte con un token de acceso personal
+
+{% data reusables.package_registry.required-scopes %}
+
+Para autenticarte en {% data variables.product.prodname_registry %} con la interfaz de la línea de comando (CLI) `dotnet`, crea un archivo *nuget.config* en el directorio de tu proyecto especificando {% data variables.product.prodname_registry %} como una fuente en `packageSources` para el cliente de la CLI `Dotnet`.
+
+Debes reemplazar:
+- `USERNAME` (nombre de usuario) por el nombre de tu cuenta de usuario en {% data variables.product.prodname_dotcom %}.
+- `TOKEN` por tu token de acceso personal.
+- `OWNER` com el nombre de la cuenta de usuario u organización a la que pertenece el repositorio que contiene tu proyecto.{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- `HOSTNAME` con el nombre de host de {% data variables.product.product_location %}.{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %}Si tu instancia tiene habilitado el aislamiento de subdominio:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+```xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://github.com/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+{% endif %}
+
+### Publicar un paquete
+
+Puedes publicar un paquete en el {% data variables.product.prodname_registry %} si te autenticas con un archivo de *nuget.config*{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%}, o si utilizas la opción de línea de comandos `--api-key` con tu token de acceso personal (PAT) de {% data variables.product.prodname_dotcom %}{% endif %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### Publicar un paquete utilizando el PAT de GitHub como tu clave de la API
+
+Si aún no tienes un PAT para utilizar con tu cuenta de {% data variables.product.prodname_dotcom %}, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
+
+1. Crear un proyecto nuevo.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. Empaquetar el proyecto.
+  ```shell
+  dotnet pack--lanzamiento de configuración
+  ```
+
+3. Publicar el paquete utilizando tu PAT como la clave de la API.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### Publicar un paquete utilizando un archivo *nuget.config*
+
+Al publicar, debes usar el mismo valor para `OWNER` en tu archivo *csproj* que usas en tu archivo de autenticación *nuget.config*. Especifica o incrementa el número de versión en tu archivo *.csproj* y luego usa el comando `dotnet pack` para crear un archivo *.nuspec* para esa versión. Para obtener más información sobre cómo crear tu paquete, consulta la sección "[Crear y publicar un paquete](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" en la documentación de Microsoft.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Crear un proyecto nuevo.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. Agrega la información específica de tu proyecto al archivo de tu proyecto, que finaliza en *.csproj*.  Debes reemplazar:
+    - `OWNER` por el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.
+    - `REPOSITORY` por el nombre del repositorio que contiene el paquete que deseas publicar.
+    - `1.0.0` con el número de versión del paquete.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - `HOSTNAME` con el nombre de host de {% data variables.product.product_location %}.{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. Empaquetar el proyecto.
+  ```shell
+  dotnet pack--lanzamiento de configuración
+  ```
+
+5. Publicar el paquete utilizando la `clave` que especificaste en el archivo *nuget.config*.
+  ```shell
+  dotnet nuget subir "bin/Release/OctocatApp. 1.0.0. nupkg"--Source "GitHub"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publicar varios paquetes en el mismo repositorio
+
+Para publicar varios paquetes en el mismo repositorio, puedes incluir la misma URL del repositorio de {% data variables.product.prodname_dotcom %} en los campos `RepositoryURL` en todos los archivos del proyecto *.csproj*. {% data variables.product.prodname_dotcom %} coincide con el repositorio en base a ese campo.
+
+Por ejemplo, los proyectos *OctodogApp* y *OctocatApp* publicarán en el mismo repositorio:
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### Instalar un paquete
+
+El uso de paquetes desde {% data variables.product.prodname_dotcom %} en tu proyecto es similar al uso de paquetes desde *nuget.org*. Agrega las dependencias de tu paquete a tu archivo *.csproj*, especificando el nombre del paquete y la versión. Para obtener más información sobre cómo utilizar un archivo *.csproj* en tu proyecto, consulta "[Trabajar con paquetes NuGet](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)"en la documentación de Microsoft.
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. Para usar un paquete, agrega `ItemGroup` y configura el campo `PackageReference` en el archivo de proyecto *.csproj*, reemplaza el paquete `OctokittenApp` por la dependencia de tu paquete y `1.0.0` por la versión que deseas usar:
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. Instalar los paquetes con el comando `restore (restaurar)`.
+  ```shell
+  restaurar dotnet
+  ```
+
+### Solución de problemas
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### Leer más
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..69fdeaca4d
--- /dev/null
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,152 @@
+---
+title: Working with the RubyGems registry
+intro: 'Puedes configurar RubyGems para publicar un paquete para {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto Ruby con Bundler.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows.
+
+### Prerrequisitos
+
+- Debes tener RubyGems 2.4.1 o superiores. Para encontrar tu versión de RubyGems:
+
+  ```shell
+  $ gem --version
+  ```
+
+  - Debes tener Bundler 1.6.4 o superiores. Para encontrar tu versión Bundler:
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - Instala keycutter para administrar múltiples credenciales. Para instalar keycutter:
+  ```shell
+  $ gem install keycutter
+  ```
+
+### Autenticarte en {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Autenticarte con un token de acceso personal
+
+{% data reusables.package_registry.required-scopes %}
+
+Puedes autenticar a {% data variables.product.prodname_registry %} con RubyGems editando el archivo *~/.gem/credentials* para publicar gemas, editar el archivo *~/.gemrc*  para instalar una gema única o usar Bundler para rastrear e instalar una o más gemas.
+
+Para publicar gemas nuevas, debes autenticarte para {% data variables.product.prodname_registry %} con RubyGems editando tu archivo *~/.gem/credentials* para incluir tu token de acceso personal.  Crear un nuevo archivo *~/.gem/credentials* si este archivo no existe.
+
+Por ejemplo, crearías o editarías un *~/.gem/credentials* para incluir lo siguiente, reemplazando *TOKEN* con tu token de acceso personal.
+
+```shell
+---
+:github: Bearer <em>TOKEN</em>
+```
+
+Para instalar gemas, necesitas autenticarte en el {% data variables.product.prodname_registry %} mediante la edición del archivo *~/.gemrc* para que tu proyecto incluya `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Debes reemplazar:
+  - `USERNAME` con tu nombre de usuario {% data variables.product.prodname_dotcom %}.
+  - `TOKEN` por tu token de acceso personal.
+  - `OWNER` con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.{% if enterpriseServerVersions contains currentVersion %}
+  - `REGISTRY-URL` con la URL para el registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. Cualquiera que sea el caso, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` con la URL para el registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.
+{% endif %}
+
+Si no tienes un archivo *~/.gemrc*, crea un nuevo archivo *~/.gemrc* usando este ejemplo.
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+Para autenticar con Bundler, configura Bundler para que use tu token de acceso personal, reemplazando *USERNAME* con tu nombre de usuario de {% data variables.product.prodname_dotcom %}, *TOKEN* con tu token de acceso personal y *OWNER* con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### Publicar un paquete
+
+{% data reusables.package_registry.default-name %} Por ejemplo, cuando publicas `octo-gem` a la organización `octo-org`, {% data variables.product.prodname_registry %} publica la gema en el repositorio `octo-org/octo-gem`. Para obtener más información sobre la creación de tu gema, consulta "[Crear tu propia gema](http://guides.rubygems.org/make-your-own-gem/)" en la documentación de RubyGems.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Construye el paquete desde el *gemspec* para crear el paquete *.gem*.
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. Publica un paquete en el {% data variables.product.prodname_registry %}, reemplazando `OWNER` con el nombre de la cuenta de usuario o de organización a la que pertenece el repositorio que contiene tu proyecto y `OCTO-GEM` con el nombre de tu paquete de gemas.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### Publicar varios paquetes en el mismo repositorio
+
+Para publicar múltiples gemas en el mismo repositorio, puedes incluir la URL al repositorio {% data variables.product.prodname_dotcom %} en el campo `github_repo` en `gem.metadata`. Si incluyes este campo, {% data variables.product.prodname_dotcom %} empata el repositorio con base en este valor en vez de utilizar el nombre de la gema.% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Reemplaza a *HOSTNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### Instalar un paquete
+
+Puedes usar gemas desde {% data variables.product.prodname_registry %} al igual que usas gemas de *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. Para Bundler, agrega tu usuario u organización {% data variables.product.prodname_dotcom %} como fuente en tu *Gemfile* para extraer gemas de esta nueva fuente. Por ejemplo, puedes agregar un bloque nuevo de `source` al *Gemfile* que utiliza el {% data variables.product.prodname_registry %} únicamente para los paquetes que especifiques, reemplzando *GEM NAME* con el paquete que quieres instalar desde el {% data variables.product.prodname_registry %} y *OWNER* con el usuario u organización al que pertenece el repositorio que contienen la gema que quieres instalar.{% if enterpriseServerVersions contains currentVersion %} Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia. Si tu instancia cuenta con el aislamiento de subdominios habilitado, utiliza `rubygems.HOSTNAME`. Si tu instancia cuenta con el aislamiento de subdominios inhabilitado, utiliza `HOSTNAME/_registry/rubygems`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. Para las versiones de Bundler anteriores a 1.7.0, debes agregar una nueva `fuente` global. Para obtener más información acerca del uso de Bundler, consulta la [documentación bundler.io](http://bundler.io/v1.5/gemfile.html).
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. Instala el paquete:
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### Leer más
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
index 2c78d1ec84..0428cd1495 100644
--- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
+++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
@@ -24,9 +24,9 @@ topics:
 | Subdominio personalizado                 | `blog.example.com` |
 | Dominio apex                             | `example.com`      |
 
-You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)."
+Puedes configurar cualquiera o ambos de los ajustes de subdominio de apex y de `www` para tu sitio. Para obtener más información sobre los dominios de apex, consulta la sección "[Utilizar un dominio de apex para tu sitio de {% data variables.product.prodname_pages %}](#using-an-apex-domain-for-your-github-pages-site)".
 
-Recomendamos siempre usar un subdominio `www`, incluso si también usas un dominio apex. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
+Recomendamos siempre usar un subdominio `www`, incluso si también usas un dominio apex. Cuando creas un sitio nuevo con un dominio de apex, atuomáticamente intentamos asegurar el subdominio de `www` para utilizarlo cuando sirves el contenido de tu sitio. Si configuras un subdominio de `www`, automáticamente intentamos asegurar el dominio asociado de apex. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
 
 Después de que configuras un dominio personalizado para un usuario o sitio de organización, el dominio personalizado reemplazará a la porción de `<user>.github.io` o `<organization>.github.io` de la URL para cualquier sitio de proyecto que pertenezca a la cuenta que no haya configurado un dominio personalizado. Por ejemplo, si el dominio personalizado para tu sitio de usuario es `www.octocat.com`, y tienes un sitio de proyecto sin un dominio personalizado configurado que se publica desde un repositorio denominado `octo-project`, el sitio {% data variables.product.prodname_pages %} para ese repositorio estará disponible en `www.octocat.com/octo-project`.
 
@@ -44,7 +44,7 @@ Los subdominios `www` son el tipo de dominio personalizado m ás estable porque
 
 #### Subdominios personalizados
 
-A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Los subdominios personalizados se utilizan principalmente cuando se necesitan dos secciones distintas de su sitio. Por ejemplo, puedes crear un sitio llamado `blog.example.com` y personalizar esa sección independientemente de `www.example.com`.
+Un subdominio personalizado es un tipo de subdominio que no utiliza la variante estándar de `www`. Los subdominios personalizados se utilizan principalmente cuando se necesitan dos secciones distintas de su sitio. Por ejemplo, puedes crear un sitio llamado `blog.example.com` y personalizar esa sección independientemente de `www.example.com`.
 
 ### Uso de un dominio apex para tu sitio {% data variables.product.prodname_pages %}
 
@@ -52,7 +52,7 @@ Un dominio apex es un dominio personalizado que no contiene un subdominio, como
 
 Un dominio apex está configurado con un registro `A`, `ALIAS` o `ANAME` a través de su proveedor DNS. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)".
 
-{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)."
+{% data reusables.pages.www-and-apex-domain-recommendation %} Para obtener más información, consulta la sección "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)".
 
 ### Actualizar dominios personalizados cuando tu sitio de {% data variables.product.prodname_pages %} está inhabilitado
 
diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index a818d11461..49f249edb0 100644
--- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -46,7 +46,7 @@ Para configurar un subdominio personalizado o de `www` tal como `www.example.com
 4. Debajo de "Dominio personalizado", teclea tu dominio personalizado y luego da clic en **Guardar**. Esto creará una confirmación que agregará un archivo _CNAME_ en la raíz de tu fuente de publicación. ![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-subdomain.png)
 5. Desplázate hasta tu proveedor DNS y crea un registro `CNAME` que apunte tu subdominio al dominio predeterminado de tu sitio. Por ejemplo, si quieres usar el subdominio `www.example.com` para tu sitio de usuario, crea un registro `CNAME` que apunte `www.example.com` a `<user>.github.io`. Si quieres utilizar el subdominio `www.anotherexample.com` para el sitio de tu organización, crea un registro de `CNAME` que apunte a `www.anotherexample.com` hacia `<organization>.github.io`. El registro `CNAME` siempre deberá apuntar hacia `<user>.github.io` o `<organization>.github.io`, excluyendo el nombre del repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _WW.EXAMPLE.COM_ por tu subdominio.
 ```shell
@@ -61,9 +61,9 @@ Para configurar un subdominio personalizado o de `www` tal como `www.example.com
 
 ### Configurar un dominio apex
 
-To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file  in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
+Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un archivo _CNAME_ en tu repositorio de {% data variables.product.prodname_pages %} y por lo menos un registro de `ALIAS`, `ANAME`, o `A`  con tu proveedor de DNS.
 
-{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
+{% data reusables.pages.www-and-apex-domain-recommendation %} Para obtener más información, consulta la sección "[Configurar un subdominio](#configuring-a-subdomain)".
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -71,7 +71,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 4. Debajo de "Dominio personalizado", teclea tu dominio personalizado y luego da clic en **Guardar**. Esto creará una confirmación que agregará un archivo _CNAME_ en la raíz de tu fuente de publicación. ![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-apex-domain.png)
 5. Desplázate hasta tu proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. {% data reusables.pages.contact-dns-provider %}
     - Para crear un registro `ALIAS` o `ANAME`, apunta tu dominio apex al dominio predeterminado de tu sitio. {% data reusables.pages.default-domain-information %}
-    - To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+    - Para crear registros `A`, apunta tu dominio apex a las direccioens IP de {% data variables.product.prodname_pages %}.
       ```shell
       185.199.108.153
       185.199.109.153
@@ -79,7 +79,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _EXAMPLE.COM_ por tu dominio apex. Confirma que los resultados coincidan con las direcciones IP de las {% data variables.product.prodname_pages %} que aparecen arriba.
   ```shell
@@ -92,16 +92,16 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
 
-### Configuring an apex domain and the `www` subdomain variant
+### Configurar un dominio de apex y la variante de subdominio `www`
 
-When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant.
+Cuando utilizas un dominio apex, te recomendamos configurar tu sitio de {% data variables.product.prodname_pages %} para hospedar contenido tanto en el dominio de apex como en la variante de subdominio `www`.
 
-To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
+Para configurar un subdominio `www` junto con el dominio de apex, primero debes configurar un dominio de apex, el cual creará un `ALIAS`, `NOMBRE` o registro `A` con tu proveedor de DNS. Para obtener más información, consulta la sección [Configurar un dominio de apex](#configuring-an-apex-domain)".
 
-After you configure the apex domain, you must to configure a CNAME record with your DNS provider.
+Después de configurar el domnio apex, debes configurar un registro de CNAME con tu proveedor de DNS.
 
-1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
-2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
+1. Navega a tu proveedor de DNS y crea un registro de `CNAME` que apunte a `www.example.com` al dominio predeterminado de tu sitio: `<user>.github.io` o `<organization>.github.io`. No incluyas el nombre de repositorio. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
+2. Para confirmar que tu registro de DNS se configuró correctamente, utiliza el comando `dig`, reemplazando a _WWW.EXAMPLE.COM_ con tu variante de subdominio `www`.
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -109,12 +109,12 @@ After you configure the apex domain, you must to configure a CNAME record with y
     > <em>YOUR-USERNAME</em>.github.io.      43192   IN      CNAME   <em> GITHUB-PAGES-SERVER </em>.
     > <em> GITHUB-PAGES-SERVER </em>.         22      IN      A       192.0.2.1
 ```
-### Removing a custom domain
+### Eliminar un dominio personalizado
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-4. Under "Custom domain," click **Remove**. ![Botón de guardar dominio personalizado](/assets/images/help/pages/remove-custom-domain.png)
+4. Debajo de "Dominio personalizado", haz clic en **Eliminar**. ![Botón de guardar dominio personalizado](/assets/images/help/pages/remove-custom-domain.png)
 
 ### Leer más
 
diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
index b3cc66224a..50b2585c1a 100644
--- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
+++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -24,8 +24,8 @@ Luego, asegúrate de que el archivo _CNAME_ tenga el formato correcto.
 
 - El nombre de archivo _CNAME_ debe estar todo en mayúsculas.
 - El archivo _CNAME_ puede contener solo un dominio. Para apuntar múltiples dominios a tu sitio, debes configurar un redireccionamiento a través de tu proveedor DNS.
-- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
-- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. Por ejemplo, si el archivo _CNAME_ de otro repositorio contiene `example.com`, no puedes usar `example.com` en el archivo _CNAME_ para tu repositorio.
+- El archivo _CNAME_ debe contener únicamente el nombre del dominio. Por ejemplo, `www.example.com`, `blog.example.com`, o `example.com`.
+- El nombre de dominio debe ser único a lo largo de todos los sitios de {% data variables.product.prodname_pages %}. Por ejemplo, si el archivo _CNAME_ de otro repositorio contiene `example.com`, no puedes usar `example.com` en el archivo _CNAME_ para tu repositorio.
 
 ### Error de configuración DNS
 
@@ -42,7 +42,7 @@ Asegúrate de que en tu sitio no ocurra lo siguiente:
 - Uso de más de un subdominio `www`. Por ejemplo, `www.example.com` y `www.anotherexample.com`.
 - Uso de un dominio apex y de un subdominio personalizado. Por ejemplo, `example.com` y `docs.example.com`.
 
-  The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)".
+  La única exepción es el subdominio `www`. Si se configura correctamente, el subdominio `www` se redirigirá automáticamente al dominio apex. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)".
 
 {% data reusables.pages.wildcard-dns-warning %}
 
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md
index ebc907135d..06edde277b 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -68,14 +68,6 @@ La URL donde tu sitio está disponible depende de si el aislamiento del subdomin
 Para obtener más información, consulta la sección "[Habilitar el aislamiento del subdominio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" o contacta a tu administrador de sitio.
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Nota:** Los repositorios que usan el esquema de nombres `<username>.github.com` tradicional seguirán publicándose, pero los visitantes serán redirigidos desde `http(s)://<username>.github.com` a `http(s)://<username>.github.io`. Si existen tanto un repositorio de `<username>.github.com` como de `<username>.github.io`, solo se publicará el repositorio de `<username>.github.io`.
-
-{% endnote %}
-{% endif %}
-
 ### Publicar fuentes para sitios {% data variables.product.prodname_pages %}
 
 La fuente de publicación para tu sitio de {% data variables.product.prodname_pages %} es la rama y carpeta en donde se almacenan los archivos fuente de tu sitio.
@@ -137,7 +129,7 @@ Si tu sitio excede estas cuotas de uso, es posible que no podamos prestar servic
 
 {% data variables.product.prodname_pages %} no pretende ser un servicio de alojamiento web gratuito ni permite que se use de ese modo para realizar tus negocios en línea, un sitio de comercio electrónico, o cualquier otro sitio web que esté principalmente dirigido a facilitar las operaciones comerciales o brindar software comercial como un servicio (SaaS).
 
-In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. Para encontrar una lista de usos prohibidos, consulta la sección "[Condiciones adicionales de producto de {% data variables.product.prodname_dotcom %} para las {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)".
+Adicionalmente, {% data variables.product.prodname_dotcom %} no permite que se utilicen las {% data variables.product.prodname_pages %} para algunos propósitos o actividades específicos. Para encontrar una lista de usos prohibidos, consulta la sección "[Condiciones adicionales de producto de {% data variables.product.prodname_dotcom %} para las {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)".
 {% endif %}
 
 ### Tipos MIME en {% data variables.product.prodname_pages %}
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index c1a0140c45..58535fe2ad 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -11,7 +11,7 @@ redirect_from:
 
 ### Acerca del control de acceso para los sitios de {% data variables.product.prodname_pages %}
 
-Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. Con el control de acceso puedes elegir publicar el sitio de forma pública para cualquiera en internet o de forma privada para las personas con acceso de lectura en tu repositorio. Un sitio que se publica de forma privada puede utilizarse para compartir tu documentación o base de conocimientos internos con los miembros de tu empresa. No puedes administrar el control de accesos para el sitio de una organización. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. Con el control de acceso puedes elegir publicar el sitio de forma pública para cualquiera en internet o de forma privada para las personas con acceso de lectura en tu repositorio. Un sitio que se publica de forma privada puede utilizarse para compartir tu documentación o base de conocimientos internos con los miembros de tu empresa. No puedes administrar el control de accesos para el sitio de una organización. Para obtener más información sobre los tipos de sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Los sitios que se publican de forma privada se encuentran disponibles en un subdominio diferente que el de aquellos sitios que se publican de forma pública. Esto garantiza que tu sitio de {% data variables.product.prodname_pages %} es seguro desde el momento en el que se publica:
 
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
index 09ef616d33..7af800cb8e 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -19,7 +19,7 @@ Para obtener más información acerca de las fuentes de publicación, consulta "
 
 ### Elegir una fuente de publicación
 
-Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} For example, before you can publish your project site from the `/docs` folder on the `master` branch of your repository, you or a collaborator must create a `/docs` folder on the default `master` branch of your repository.{% endif %}
+Antes de que configures una fuente de publicación, asegúrate de que la rama{% if currentVersion ver_lt "enterprise-server@3.0" %} o carpeta{% endif %} que quieras utilizar como tal ya exista en tu repositorio.{% if currentVersion ver_lt "enterprise-server@3.0" %} Por ejemplo, antes de que puedas publicar tu sitio de proyecto desde la carpeta `/docs` en la rama `master` de tu repositorio, ya sea algún colaborador o tú mismo deberán crear una carpeta de `/docs` en la rama predeterminada `master` de tu repositorio.{% endif %}
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index 4d7a7abf6f..ea5a82f375 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -22,7 +22,7 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 2. Si existe una rama de `gh-pages` en el repositorio, elimina la rama de `gh-pages`. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)".
-3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+3. Si tu fuente de publicación fue la rama `gh-pages`, {% if currentVersion == "free-pro-team@latest" %}pasa al paso 6{% else %}tu sitio ahora se dejó de publicar y puedes saltar al resto de los pasos{% endif %}.
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
 5. Debajo de "{% data variables.product.prodname_pages %}", usa el menú desplegable **Source** (Fuente) y seleccionar **None** (Ninguno). ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png)
diff --git a/translations/es-ES/content/pages/index.md b/translations/es-ES/content/pages/index.md
index 8de6239962..536a42532d 100644
--- a/translations/es-ES/content/pages/index.md
+++ b/translations/es-ES/content/pages/index.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Pages Documentation
+title: Documentación de GitHub Pages
 shortTitle: Páginas de GitHub
 intro: 'Puedes crear un sitio web directamente desde un repositorio de {% data variables.product.product_name %}.'
 redirect_from:
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
index c7cb371377..a3a9cd6a91 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -56,7 +56,7 @@ kramdown:
 
 De manera predeterminada, Jekyll no compila archivos o carpetas que:
 - están situados en una carpeta denominada `/node_modules` o `/vendor`
-- start with `_`, `.`, or `#`
+- comienza con `_`, `.`, o `#`
 - termina con `~`
 - están excluidos por el parámetro `exclude` en tu archivo de configuración
 
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index 9f82d3a6bd..a33c43dffa 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -87,7 +87,12 @@ Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product
 10. Guarda y cierra el Gemfile.
 11. Desde la línea de comandos, ejecuta `bundle update`.
 11. De forma opcional, prueba tu sitio localmente. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)".
-12. Agrega tu repositorio de {% data variables.product.product_name %} como remoto, reemplazando {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ con el nombre de host de tu aplicativo,{% endif %} _USER_ con la cuenta a la que pertenece el repositorio{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} y _REPOSITORY_ con el nombre del repositorio.
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. Agrega tu repositorio de {% data variables.product.product_name %} como remoto, reemplazando {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ con el nombre de host de tu aplicativo,{% endif %} _USER_ con la cuenta a la que pertenece el repositorio{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} y _REPOSITORY_ con el nombre del repositorio.
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
index cca5a02c88..efb913cfd1 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
@@ -31,7 +31,7 @@ Antes de que puedas usar Jekyll para probar un sitio, debes hacer lo siguiente:
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.pages.navigate-publishing-source %}
-3. Run `bundle install`.
+3. Ejecuta `bundle install`.
 3. Ejecuta tu sitio Jekyll de forma local.
   ```shell
   $ bundle exec jekyll serve
diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md
index 1130bae3d6..284d68ebbe 100644
--- a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ Mmmm, sabe a [JSON][json]. Vamos a agregar el marcador `-i` para que incluya los
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -225,7 +225,7 @@ Posteriormente vamos a obtener nuestro repositorio recién creado:
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ Un proyecto con el tamaño de Rails tiene miles de informes de problemas. Necesi
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ Una gran parte de ser un buen ciudadano de la API es respetar los límites de ta
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ Además del cuerpo de JSON, toma nota del código de estado HTTP de `200` y del
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 El estado `304` indica que el recurso no ha cambiado desde la última vez que lo solicitamos y que la respuesta no contendrá ningún cuerpo. Como bonificación, las respuestas `304` no contarán para tu [límite de tasa][rate-limiting].
diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md
index 78d9b2191a..fdfc4faf37 100644
--- a/translations/es-ES/content/rest/overview/libraries.md
+++ b/translations/es-ES/content/rest/overview/libraries.md
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
diff --git a/translations/es-ES/content/rest/overview/media-types.md b/translations/es-ES/content/rest/overview/media-types.md
index d239d53ebc..0ad7cb30ee 100644
--- a/translations/es-ES/content/rest/overview/media-types.md
+++ b/translations/es-ES/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ Puedes verificar la versión actual a través de los encabezados de cada respues
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md
index 3d16171a69..197a5927c0 100644
--- a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md
@@ -34,7 +34,7 @@ envían y reciben como JSON.
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: nginx
 > Date: Fri, 12 Oct 2012 23:33:14 GMT
 > Content-Type: application/json; charset=utf-8
@@ -126,7 +126,7 @@ Autenticarse con credenciales inválidas regresará el mensaje `401 Unauthorized
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
-> HTTP/1.1 401 Unauthorized
+> HTTP/2 401
 
 > {
 >   "message": "Bad credentials",
@@ -139,7 +139,7 @@ Después de detectar varias solicitudes con credenciales inválidas dentro de un
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 -u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > {
 >   "message": "Maximum number of login attempts exceeded. Please try again later.",
 >   "documentation_url": "{% data variables.product.doc_url_pre %}"
@@ -181,7 +181,7 @@ Existen tres posibles tipos de errores de cliente en los llamados a la API que r
 
 1. Enviar un JSON inválido dará como resultado una respuesta de tipo `400 Bad Request`.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 35
        
         {"message":"Problems parsing JSON"}
@@ -189,14 +189,14 @@ Existen tres posibles tipos de errores de cliente en los llamados a la API que r
 2. Enviar el tipo incorrecto de valores de JSON dará como resultado una respuesta de tipo `400 Bad
 Request`.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 40
        
         {"message":"Body should be a JSON object"}
 
 3. Enviar campos inválidos dará como resultado una respuesta de tipo `422 Unprocessable Entity`.
    
-        HTTP/1.1 422 Unprocessable Entity
+        HTTP/2 422
         Content-Length: 149
        
         {
@@ -328,7 +328,7 @@ Los encabezados HTTP recuperados para cualquier solicitud de la API muestran tu
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 56
@@ -351,7 +351,7 @@ new Date(1372700873 * 1000)
 Si excedes el límite de tasa, se regresará una respuesta de error:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 0
@@ -371,7 +371,7 @@ Si tu aplicación de OAuth necesita hacer llamados no autenticados con un límit
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 5000
 > X-RateLimit-Remaining: 4966
@@ -397,7 +397,7 @@ El abuso de límite de tasa no pretende interferir con el uso legítimo de la AP
 Si tu aplicación activa este límite de tasa, recibirás una respuesta informativa:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Content-Type: application/json; charset=utf-8
 > Connection: close
 
@@ -450,7 +450,7 @@ La mayoría de las respuestas regresan un encabezado de `ETag`. Muchas de las re
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/user
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -460,7 +460,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -470,7 +470,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
@@ -487,7 +487,7 @@ Aquí hay una solicitud de ejemplo que se envió desde una consulta de buscador
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
-HTTP/1.1 302 Found
+HTTP/2 302
 Access-Control-Allow-Origin: *
 Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
@@ -496,7 +496,7 @@ Así se ve una solicitud de prevuelo de CORS:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
-HTTP/1.1 204 No Content
+HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
diff --git a/translations/es-ES/content/rest/reference/activity.md b/translations/es-ES/content/rest/reference/activity.md
index 8f5be098fc..bd67ae3b42 100644
--- a/translations/es-ES/content/rest/reference/activity.md
+++ b/translations/es-ES/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ Los eventos se optimizan para el sondeo con el encabezado "ETag". Si no se han d
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
 # The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ Para obtener un canal en formato de Atom, debes especificar el tipo `application
 #### Respuesta
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ Las notificaciones se optimizan para el sondeo con el encabezado `Last-Modified`
 ``` shell
 # Add authentication to your requests
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
 # Pass the Last-Modified header exactly
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/es-ES/content/rest/reference/git.md b/translations/es-ES/content/rest/reference/git.md
index cc2184829a..3a7083d992 100644
--- a/translations/es-ES/content/rest/reference/git.md
+++ b/translations/es-ES/content/rest/reference/git.md
@@ -19,7 +19,7 @@ La API de la Base de datos de Git te da acceso de escritura y lectora para los o
 
 ## Blobs
 
-Un blob (objeto binario grande, por sus siglas en inglés) de Git es el tipo de objeto que se utiliza para almacenar el contenido de cada archivo en un repositorio. El hash SHA-1 del archivo se calcula y almacena en el objeto del blob. Estas terminales te permiten leer y escribir [objetos de blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) en tu base de datos de Git en {% data variables.product.product_name %}. Los blobs aprovechan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
+Un blob (objeto binario grande, por sus siglas en inglés) de Git es el tipo de objeto que se utiliza para almacenar el contenido de cada archivo en un repositorio. El hash SHA-1 del archivo se calcula y almacena en el objeto del blob. Estas terminales te permiten leer y escribir [objetos de blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) en tu base de datos de Git en {% data variables.product.product_name %}. Los blobs aprovechan [estos tipos de medios personalizados](#custom-media-types-for-blobs). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types).
 
 ### Tipos de medios personalizados para los blobs
 
diff --git a/translations/es-ES/content/rest/reference/migrations.md b/translations/es-ES/content/rest/reference/migrations.md
index 1c65ae48d9..b99d9d5819 100644
--- a/translations/es-ES/content/rest/reference/migrations.md
+++ b/translations/es-ES/content/rest/reference/migrations.md
@@ -16,7 +16,7 @@ topics:
 
 ## Organización
 
-La API de Migraciones solo está disponible para los propietarios autenticados de la organización. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)."
+La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[Niveles de permiso para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)." y "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)".
 
 {% data variables.migrations.organization_migrations_intro %}
 
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 ed8492a213..90e694b1bf 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
@@ -120,6 +120,9 @@ _Search_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _Search_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -678,6 +684,9 @@ _Equipos_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### Permiso sobre las "solicitudes de extracción"
 
@@ -767,6 +776,10 @@ _Revisiones_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### Permission on "profile"
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### Permisos sobre los "ganchos del repositorio"
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md
index 13242fed86..a41d41ac1c 100644
--- a/translations/es-ES/content/rest/reference/repos.md
+++ b/translations/es-ES/content/rest/reference/repos.md
@@ -155,7 +155,8 @@ Puedes comunicar que un ambiente transitorio ya no existe si configuras el `stat
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 ## Ambientes
 
-La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener información sobre los ambientes, consulta la sección "[Ambientes](/actions/reference/environments)".
+La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener información sobre los ambientes, consulta la sección "[Ambientes](/actions/reference/environments)". To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
diff --git a/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..dc4f14783e
--- /dev/null
+++ b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: Acerca de los Patrocinadores de GitHub
+intro: '{% data variables.product.prodname_sponsors %}permite a la comunidad de desarrolladores apoyar financieramente al personal y organizaciones que diseñan, construyen y mantienen los proyectos de código abierto de los cuales dependen, directamente en {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Acerca de {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)".
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para obtener más información, consulta las secciones "[Acerca de {% data variables.product.prodname_sponsors %} para los contribuyentes de código abierto](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)".
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".
+
+Cuando te conviertes en un desarrollador patrocinado u organización patrocinada, aplicarán las condiciones adicionales de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta la sección "[Condiciones Adicionales de GitHub Sponsors](/github/site-policy/github-sponsors-additional-terms)".
+
+### Acerca de {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**Nota:**{% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+El {% data variables.product.prodname_matching_fund %} pretende beneficiar a los miembros de la comunidad de {% data variables.product.prodname_dotcom %} quienes desarrollan software de código abierto que promueve los [Lineamientos de la Comunidad de {% data variables.product.prodname_dotcom %}](/github/site-policy/github-community-guidelines). Los pagos desde las organizaciones y hacia las organizaciones patrocinadas no son elegibles para {% data variables.product.prodname_matching_fund %}.
+
+Para ser elegible para el {% data variables.product.prodname_matching_fund %}, debes crear un perfil que atraiga a la comunidad que te mantendrá a largo plazo. Para obtener más información acerca de crear un perfil llamativo, consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)".
+
+Las donaciones entre los desarrolladores patrocinados no se empatarán.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### Intercambiar opiniones acerca de {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### Leer más
+- "[Patrocinar a contribuyentes de código abierto](/sponsors/sponsoring-open-source-contributors)"
+- "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)".
+- "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %}
diff --git a/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..e2f2662abb
--- /dev/null
+++ b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: Iniciar con GitHub Sponsors
+intro: 'Aprende sobre {% data variables.product.prodname_sponsors %} y sobre cómo puedes involucrarte como patrocinador o como colaborador de código abierto.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..3ce7873827
--- /dev/null
+++ b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: Guía rápida para encontrar contribuyentes para patrocinar
+intro: Aprende algunas de las mejores prácticas para encontrar contribuyentes de código abierto para patrocinar.
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### Explora los proyectos de los cuales dependes
+
+En medida que consideres dónde encontrar contribuyentes de código abierto para patrocinar, considera comenzar en https://github.com/sponsors/community.
+
+Si iniciaste sesión, los resultados de los patrocinadores comenzarán con las dependencias públicas de las cuales dependen tus repositorios.
+
+![El proyecto de código abierto Babel con texto resaltado que dice "4 de tus repositorios dependen de esto"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+También puedes alternar entre de cuáles de tus cuentas quieres ver resultados y filtrar o buscar más.
+
+![Opciones de búsqueda de la página de búsqueda de la comunidadde patrocinadores](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### Explora aquién patrocinan los demás
+
+Puedes ver a quién patrocina un usuario u organización en su página de perfil de {% data variables.product.prodname_dotcom %}.
+
+### Considera cómo te beneficias de los diferentes contribuyentes
+
+Considera si te beneficias del trabajo de los contribuyentes de código abierto, tal como:
+ - Documentación
+ - Diseño
+ - Traducción
+ - Boletines informativos
+ - Revisiones de código
+ - Tutoriales
+ - Tutorías
+ - Problemas de capacitación y ayuda con la administración de proyectos
+ - Responder preguntas
+ - Planeación de eventos
+
+Para obtener más información sobre los diferentes tipos de contribuyentes de código abierto, consulta la [Guía de código abierto](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+Puedes verificar si los contribuyentes de los que te has beneficiado tienen perfiles de {% data variables.product.prodname_sponsors %} si utilizas la búsqueda en https://github.com/sponsors/community.
+
+### Busca un proyecto o contribuyente específico
+
+En https://github.com/sponsors/community, puedes buscar por ecosistema, los más utilizados, actualizados recientemente, y más. Puedes filtrar los resultados de búsqueda para tu cuenta de usuario personal o para las organizaciones de las cuales eres miembro.
+
+### Pasos siguientes
+
+Para obtener más información sobre cómo iniciar tu patrocinio, consulta la sección "[Patrocinar un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)".
diff --git a/translations/es-ES/content/sponsors/guides.md b/translations/es-ES/content/sponsors/guides.md
new file mode 100644
index 0000000000..262578140d
--- /dev/null
+++ b/translations/es-ES/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: Guías de GitHub Sponsors
+shortTitle: Guías
+intro: 'Aprende a sacar el mayor provecho de {% data variables.product.prodname_sponsors %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/es-ES/content/sponsors/index.md b/translations/es-ES/content/sponsors/index.md
new file mode 100644
index 0000000000..086b8a038b
--- /dev/null
+++ b/translations/es-ES/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: Documentación de GitHub Sponsors
+shortTitle: Patrocinadores de GitHub
+intro: 'Invierte en los proyectos de código abierto de los cuales dependes, apoya la infraestructura digital y haz posibles las carreras de código abirto patrocinando a los contribuyentes de código abierto y a sus proyectos. Crea un perfil de {% data variables.product.prodname_sponsors %} y recibe una compensación para tu trabajo de código abierto.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: sponsors
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/es-ES/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/es-ES/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..142d685dc4
--- /dev/null
+++ b/translations/es-ES/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: Configurar webhooks para eventos en tu cuenta patrocinada
+intro: Puedes configurar wehbhooks para que te envíen una alerta cuando recibas nuevos patrocinios o cuando los patrocinadores existentes realicen cambios a sus patrocinios.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### Acerca de los webhooks para los eventos en tu cuenta patrocinada
+
+Para monitorear los cambios a tus patrocinios, tales como las cancelaciones al final de un periodo de pago, puedes crear webhooks para tu cuenta patrocinada de usuario u organización. Cuando configuras un webhook para tu cuenta patrocinada, recibirás las actualizaciones cuando los patrocinios se creen, editen o borren. Para obtener más información, consulta el [evento de webhook de `sponsorship`](/webhooks/event-payloads/#sponsorship).
+
+### Administrar los webhooks para los eventos en tu cuenta patrocinada
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/es-ES/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/es-ES/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..57abc55b61
--- /dev/null
+++ b/translations/es-ES/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Comenzar con la API de GraphQL de Patrocinadores
+intro: 'Al utilizar la API de GraphQL, puedes crear integraciones personalizadas para administrar o revisar tus patrocinios.'
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+Para comenzar con la API de GraphQL, consulta la "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)".
+
+Puedes encontrar los detalles sobre la API de GraphQL de patrocinios en los documentos de referencia. Para obtener más información, consulta la "[Referencia de GraphQL](/graphql/reference)". Te recomendamos utilizar el explorador de GraphQL para crear tus llamados de GraphQL. Para obtener más información, consulta la sección "[Utilizar el explorador](/graphql/guides/using-the-explorer)".
diff --git a/translations/es-ES/content/sponsors/integrating-with-github-sponsors/index.md b/translations/es-ES/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..c0c3deaf99
--- /dev/null
+++ b/translations/es-ES/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: Integrarse con GitHub Sponsors
+intro: 'Como contribuyente de código abierto, puedes crear herramientas personalizadas para administrar tus patrocinios de GitHub.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..3d7290b18c
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: Acerca de los patrocinadores para colaboradores de código abierto en GitHub
+intro: 'Si aportas valor a un proyecto de código abierto, puedes convertirte en un colaborador patrocinado para recibir pagos por tu trabajo.'
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Unirte a {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %}Para obtener más información, consulta [Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)".
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".
+
+Una vez que te hayas unido a {% data variables.product.prodname_sponsors %}, puedes añadir un botón de "patrocinar" al repositorio de código abierto en el que contribuyes para incrementar la visibilidad de tu perfil de {% data variables.product.prodname_sponsors %} y de otras plataformas de fondeo. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)".
+
+Puedes configurar una meta para tus patrocinios. Para obtener más información, consulta la sección "[Administrar tu meta de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal)".
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### Niveles de patrocinio
+
+{% data reusables.sponsors.tier-details %} Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario"](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)", "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization) y "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)".
+
+Es mejor mantener una gama de opciones de patrocinio diferentes, incluyendo niveles mensuales y de una sola ocasión, para hacer más fácil que cualquiera apiye tu trabajo. Particularmente, los pagos de una sola ocasión le permiten a la spersonas recompensarte por tu esfuerzo sin preocuparse de que sus finanzas apoyen un programa de pagos constantes.
+
+### Pagos de patrocinios
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+Para obtener más información, consulta la sección "[Administrar tus pagos de {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)".
+
+### Intercambiar opiniones acerca de {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### Leer más
+- "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..047818cb97
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: Comunicarse con tus patrocinadores
+intro: Puedes enviar un correo electrónico a los patrocinadores que optaron por recibir actualizaciones sobre tu trabajo.
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### Acerca de las actualizaciones de los patrocinios
+
+Tus patrocinadores pueden elegir si desean recibir actualizaciones por correo electrónico sobre tu trabajo. Para obtener más información, consulta "[Administar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)".
+
+Para las cuentas de desarrollador patrocinado, la actualización vendrá de la cuenta de correo electrónico primaria de tu cuenta de usuario. Si habilitaste la privacidad de direcciones de correo electrónico en tu cuenta de usuario, la actualización vendrá entonces de `noreply@github.com`. Para las organizaciones patrocinadas, la actualización vendrá de la dirección de correo electrónico de tipo `noreply@github.com` de la organización. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)".
+
+### Comunicarse con tus patrocinadores
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..65a144778a
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: Editar los detalles de tu perfil para los Patrocinadores de GitHub
+intro: Puedes actualizar la información que ven los patrocinadores potenciales acerca de tu trabajo.
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### Acerca de los perfiles de patrocinador
+
+Tu perfil de {% data variables.product.prodname_sponsors %} les dice a los patrocinadores potenciales por qué deberían patrocinarte. Las personas ven tu perfil de patrocinador cuando dan clic en el botón **Patrocinador** de tu perfil. Te recomendamos incluir la información siguiente.
+
+- Trabajo de código abierto al que has contribuido
+- Por qué estás comprometido con el desarrollo de código abierto
+
+### Editar las credenciales de tu perfil
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..206c2360b4
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: Recibir patrocinios a través de patrocinadores de GitHub
+shortTitle: Recibir patrocinios
+intro: 'Tu organización o tú pueden convertirse en un colaborador de código abierto para recibir pagos por su trabajo, actualizar sus detalles de patrocinio y ver y contactar a sus patrocinadores.'
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..1e7714f565
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Administrar tus pagos desde Patrocinadores de GitHub
+intro: 'Puedes ver información sobre pagos pasados y futuros desde {% data variables.product.prodname_sponsors %} y editar tu información bancaria.'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### Acerca de los pagos de {% data variables.product.prodname_sponsors %}
+
+Solo puedes administrar tus pagos de {% data variables.product.prodname_sponsors %} si recibes tu pago a través de Stripe Connect. Si se te paga a través de transferencia ACH o transferencia bancaria en tu cuenta de usuario, no verás la pestaña de **Pagos** en tu tablero de colaborador de código abierto. Las organizaciones patrocinadas solo podrán utilizar Stripe Connect para los pagos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %} para los colaboradores de código abierto](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)".
+
+{% data reusables.sponsors.payout-info %}
+
+### Visualizar y editar la información de pago
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..5378ad69fe
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: Administrar tu meta de patrocinio
+intro: Puedes configurar una meta para tu cuenta de desarrollador u organización patrocinados para ayudar a que la comunidad entienda el impacto de patrocinarte.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### Acerca de las metas de patrocinio
+
+Puedes configurar una meta de financiamiento para tu cuenta patrocinada y compartir la meta con tu comunidad. Las metas te ayudan a entender el impacto que tienes en la comunidad de código abierto y aumentan tu presencia en el programa de {% data variables.product.prodname_sponsors %}.
+
+Tu meta puede configurar un objetivo para la cantidad de patrocinadores que quieres tener o la cantidad de dinero que quieres ganar mensualmente. Solo puedes configurar una meta a la vez. Después de que llegues a tu meta, puedes configurar otra.
+
+### Configurar una meta
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Editar una meta
+
+Cuando editas una meta, no puedes escoger la meta que ya hayas alcanzado. Por ejemplo, si ya tienes 5 patrocinadores, no puedes editar tu meta para que ahora sea de 4 patrocinadores.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Retirar una meta
+
+Después de que retiras una meta, no podrás reactivarla. En vez de esto, debes crear una meta nueva.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..e742747f22
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: Administrar tus niveles de patrocinio
+intro: Puedes agregar un nuevo nivel de patrocinio o editar o retirar un nivel existente.
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### Acerca de los niveles de patrocinio
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### Agregar un nivel
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### Editar o retirar un nivel
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### Habilitar niveles con cantidades personalizadas
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### Inhabilitar niveles con cantidades personalizadas
+
+Puedes inhabilitar los niveles con cantidades personalizadas si deseleccionas la opción **Habilitar cantidades personalizadas** en la pestaña de **Niveles de patrocinio**. Si inhabilitas las cantidades personalizadas, todos los niveles personalizados se reintentarán.
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..cbe52c31ac
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: Configurar los Patrocinadores de GitHub para tu organización
+intro: 'Tu organización puede unirse a {% data variables.product.prodname_sponsors %} para recibir pagos por tu trabajo.'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### Unirte a {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Después de recibir una invitación para que tu organización se una a {% data variables.product.prodname_sponsors %} puedes completar los pasos a continuación para que se convierta en una organización patrocinada.
+
+Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador individual independiente a una organización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)".
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. A la derecha de tu organización, da clic en **Unirse a la lista de espera**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### Completar un perfil de organización patrocinada
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Crear niveles de patrocinio
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Emitir tu información bancaria
+
+Como organización patrocinada, deberás recibir pagos en una cuenta bancaria dedicada a tu organización en una región compatible. Puedes obtener una cuenta bancaria comercial a través de servicios como [Open Collective](https://opencollective.com/) y [Stripe Atlas](https://stripe.com/atlas). La región en la cual opera legalmente tu organización y la región de tu cuenta bancaria deberán coincidir. La persona que configura a {% data variables.product.prodname_sponsors %} para la organización debe vivir en la región compatible también. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+Para obtener más información acerca de cómo configurar Stripe Connect utilizando Open Collective, consulta la sección [Configurar {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) en los documentos de Open Collective.
+
+### Emitir tu información de facturación
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %}
+
+Antes de que tu organización pueda convertirse en patrocinada, deberás habilitar la autenticación de dos factores en tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
+
+### Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### Leer más
+- "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)".
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..1897769db5
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: Configurar a los Patrocinadores de GitHub para tu cuenta de usuario
+intro: 'Puedes convertirte en un programador patrocinado al unirte a {% data variables.product.prodname_sponsors %}, completar tu perfil de programador patrocinado, crear niveles de patrocinio, enviar tu información bancaria y fiscal, y permitir una autenticación de dos factores en tu cuenta de {% data variables.product.prodname_dotcom %}.'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### Unirte a {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Para unirte a {% data variables.product.prodname_sponsors %} comoorganización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. Si eres un propietario de organización, tienes más de una cuenta elegible. Da clic en **Ver tus cuentas elegibles** y, posteriormente, en la lista de cuentas, encuentra tu cuenta de usuario.
+3. Da clic en **Unirse a la lista de espera**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+Si tienes una cuenta bancaria en una región compatible, {% data variables.product.prodname_dotcom %} revisará tu aplicación dentro de dos semanas.
+
+### Completar un perfil de programador patrocinado
+
+Una vez que {% data variables.product.prodname_dotcom %} revise tu aplicación, podrás configurar tu perfil de desarrollador patrocinado para que las personas puedan comenzar a patrocinarte.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Crear niveles de patrocinio
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Emitir tu información bancaria
+
+Si vives en una región compatible, puedes seguir estas instrucciones para emitir tu información bancaria y crear una cuenta de Stripe Connect. La región en la cual resides y aquella en la que está tu cuenta bancaria deben coincidir. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### Emitir tu información de facturación
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %}
+
+Antes de que puedas convertirte en un programador patrocinado, debes habilitar 2FA en tu cuenta {% data variables.product.product_name %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
+
+### Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. Haz clic en **Request approval** (Solicitar aprobación). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..4c6975b77d
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Información de facturación para los Patrocinadores de GitHub
+intro: 'Los desarrolladores y organizaciones patrocinados deben emitir su información fiscal a {% data variables.product.prodname_dotcom %} y son responsables de evaluar y pagar sus propios impuestos.'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+Si eres contribuyente en los Estados Unidos, debes enviar un W-9 antes de poder recibir pagos. Si eres un contribuyente en cualquier otra región de los Estados Unidos, deberás emitir un W-8BEN antes de que puedas recibir pagos. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)". {% data variables.product.prodname_dotcom %}te enviará los formatos adecuados, te notificará cuando vayan a expirar, y te dará una cantidad razonable de tiempo para completarlos y enviarlos.
+
+Si eres contribuyente en los Estados Unidos y ganas más de $600 USD en un año fiscal, {% data variables.product.prodname_dotcom %} te enviará un 1099 antes del 31 de enero del siguiente año calendario. No proporcionamos formularios fiscales para los contribuyentes internacionales.
+
+{% data variables.product.prodname_dotcom %} no retiene impuestos de {% data variables.product.prodname_sponsors %} pagos. Los programadores patrocinados son responsables de estimar y pagar sus propios impuestos.
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### Leer más
+
+- [Ver tus patrocinadores y patrocinios](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..2a61adc426
--- /dev/null
+++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: Ver tus patrocinadores y patrocinios
+intro: Puedes ver y exportar la información detallada y la analítica de tus patrocinadores y patrocinios.
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### Acerca de los patrocinadores y los patrocinios
+
+Puedes ver la analítica de tus patrocinios actuales y pasados, los pagos que has recibido de tus patrocinadores, y los eventos tales como las cancelaciones y cambios de nivel de patrocinio para tus patrocinios. También puedes ver la actividad tal como los nuevos patrocinios, cambios, y cancelaciones de los mismos. Puedes filtrar la lista de actividades por fecha. También puedes exportar datos del patrocinio en formato CSV o JSON para la cuenta que estás viendo.
+
+### Ver tus patrocinadores y patrocinios
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. Como alternativa, para filtrar los patrocinadores por nivel, utiliza el menú desplegable de **Filter** (Filtro), haz clic en **Active tiers** (Niveles activos) o **Retired tiers** (Niveles retirados) y selecciona un nivel. ![Menú desplegable para filtrar por nivel](/assets/images/help/sponsors/filter-drop-down.png)
+
+### Visualizar la actividad de patrocinio reciente
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### Exportar tus datos de patrocinio
+
+Puedes exportar tus transacciones de patrocinio mensualmente. {% data variables.product.company_short %} te enviará un correo electrónico con los datos de las transacciones de todos tus patrocinadores para el mes que selecciones. Después de que se complete la exportación, puedes exportar otor mes de datos. Puedes exportar hasta 10 conjuntos de datos por hora para cualquiera de tus cuentas patrocinadas.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. Da clic en {% octicon "download" aria-label="The download icon" %} **Exportar**. ![Botón de exportar](/assets/images/help/sponsors/export-all.png)
+1. Elige un periodo de tiempo y un formato para los datos que te gustaría exportar y luego haz clic en **Iniciar exportación**. ![Opciones para exportar datos](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..ab949c44e8
--- /dev/null
+++ b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: Atribuir los patrocinios a tu organización
+intro: Puedes atribuir los patrocinios que paga una de tus organizaciones a otra organización.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. Navega a la organización cuyo patrocinio quieras atribuir a otra organización.
+2. Debajo del nombre de tu organización, da clic en {% octicon "heart" aria-label="The heart icon" %}**Patrocinar**. ![Pestaña de "Patrocinar"](/assets/images/help/sponsors/sponsoring-tab.png)
+1. En la esquina superior derecha, da clic en {% octicon "gear" aria-label="The gear icon" %}**Configuración**. ![Botón de "Configuración"](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. Debajo de "Vincular patrocinios con otra cuenta", utiliza el menú desplegable y da clic en la organización a la que quieras atribuir los patrocinios de ésta. ![Menú desplegable para seleccionar una cuenta](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. Da clic en **Vincular cuenta**. ![Botón de "Vincular cuenta"](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..bc11395f7b
--- /dev/null
+++ b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: Patrocinar a colaboradores de código abierto
+intro: 'Puedes patrocinar colaboradores, recibir actualizaciones sobre los programadores y las organizaciones que patrocinas, y mostrar una insignia de patrocinador en todo {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..ccda650359
--- /dev/null
+++ b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: Administrar tu patrocinio
+intro: Puedes administrar quién puede ver tu patrocinio y si recibes actualizaciones por correo electrónico para la cuenta patrocinada.
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Administrar la configuración de privacidad para tu patrocinio
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Administrar las actualizaciones de correo electrónico para tu patrocinio
+
+Puedes elegir si una cuenta que patrocinas puede enviarte actualizaciones por correo electrónico sobre su trabajo o no. La cuenta patrocinada no tendrá acceso a tu dirección de correo electrónico.
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Leer más
+
+- "[Mejorar un patrocinio](/articles/upgrading-a-sponsorship)"
+- "[Degradar un patrocinio](/articles/downgrading-a-sponsorship)"
diff --git a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..9e219b2424
--- /dev/null
+++ b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: Patrocinar a un colaborador de código abierto
+intro: 'Puedes generar un pago mensual recurrente para un desarrollador u organización que diseñe, cree, o mantenga los proyectos de código abierto de los que dependes.'
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Acerca de los patrocinios
+
+{% data reusables.sponsors.sponsorship-details %}
+
+Puedes patrocinar una cuenta en nombre de tu cuenta de usuario para invertir en los proyectos de los cuales te beneficies personalmente. Puedes patrocinar una cuenta en nombre de tu organización por varias razones.
+- Mantener bibliotecas específicas de las cuales dependa el trabajo de tu organización
+- Invertir en el ecosistema del cual dependes como organización (tal como blockchain)
+- Desarrollar una conciencia de marca como una organización que valora el código abierto
+- Agradecer a los desarrolladores de código abierto por crear bibliotecas que complementan el producto que ofrece tu organización
+
+Puedes utilizar una tarjeta de crédito para patrocinar una cuenta en {% data variables.product.product_name %}. Si tu organización quiere pagar por factura, [contáctanos](https://support.github.com/contact/org-sponsors-waitlist).
+
+{% data reusables.sponsors.no-fees %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)".
+
+Cuando patrocinas una cuenta utilizando una tarjeta de crédito, el cargo tomará efecto de inmediato. {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+Si la cuenta patrocinada retira tu nivel, éste permanecerá configurado hasta que elijas uno diferente o hasta que canceles tu suscripción. Para obtener más información, consulta "[Actualizar un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)."
+
+Si la cuenta que quieres patrocinar no tiene un perfil en {% data variables.product.prodname_sponsors %}, puedes alentarla a que se una. Para obtener más información, consulta las secciónes "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**Nota:**{% data variables.product.prodname_dotcom %} no se responzabiliza por cómo se auto-representan los desarrolladores ni tampoco respalda ninguno de los proyectos de código abierto patrocinados. Las alegaciones son responsabilidad total del desarrollador que recibe los fondos. Asegúrate de que confías en una persona antes de ofrecerle un patrocinio. Para obtener más información, consulta la sección de [Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms).
+
+{% endnote %}
+
+### Patrocinar una cuenta
+
+Antes de que puedas patrocinar una cuenta, debes tener una dirección de correo electrónico verificada. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)".
+
+1. En {% data variables.product.product_name %}, navega al perfil del usuario u organización que quieras patrocinar.
+1. Navega a tu panel de patrocinios para la cuenta.
+   - Para patrocinar a un desarrollador, debajo de su nombre, da clic en **Patrocinar**. ![Botón de Patrocinador](/assets/images/help/profile/sponsor-button.png)
+   - Para patrocinar una organización, a la derecha del nombre de esta, haz clic en **Patrocinar**. ![Botón de Patrocinador](/assets/images/help/sponsors/sponsor-org-button.png)
+1. Opcionalmente, a la derecha de la página, para patrocinar una cuenta en nombre de tu organización, utiliza el menú desplegable de **Patrocinar como**, y da clic en la organización. ![Menú desplegable para elegier la cuenta bajo la cual harás el patrocinio](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![Botón de Editar pago](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![Botones radiales para elegir quién puede ver tu patrocinio](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml
index 3a32321016..cb8f3e69a6 100644
--- a/translations/es-ES/data/glossaries/external.yml
+++ b/translations/es-ES/data/glossaries/external.yml
@@ -1,7 +1,7 @@
 ---
 - 
   term: '@mención'
-  description: para notificar a una persona en GitHub usando "@" antes de su nombre de usuario. Los usuarios en una organización en GitHub también pueden ser parte de un equipo que puede ser mencionado.
+  description: Para notificar a una persona en GitHub usando "@" antes de su nombre de usuario. Los usuarios en una organización en GitHub también pueden ser parte de un equipo que puede ser mencionado.
 - 
   term: token de acceso
   description: >-
@@ -88,7 +88,7 @@
 - 
   term: selección minusciosa
   description: >-
-    To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation.
+    Para elegir un subconjunto de cambios de una serie de cambios (habitualmente, confirmaciones) y registrarlos como una serie de cambios nueva en la parte superior de una base de código diferente. En Git, esto se lleva a cabo con el comando `git cherry-pick` para extraer el cambio que introdujo una confirmación existente en otra rama y para registrarlo con base en la punta de la rama actual como una confirmación nueva. Para obtener más información, consulta la sección [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) en la documentación de Git.
 - 
   term: equipo hijo
   description: >-
@@ -181,7 +181,7 @@
 - 
   term: rama predeterminada
   description: >-
-    La rama base para las solicitudes de cambios nuevas y las confirmaciones de código en un repositorio. Cada repositorio tiene por lo menos una rama, la cual crea Git cuando lo inicializas. Habitualmente, la primera rama se llama `main`, y a menudo es la predeterminada.
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}, and is often the default branch.
 - 
   term: Gráfico de dependencias
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    La rama predeterminada de desarrollo. Cuando creas un repositorio de Git, se crea una rama que se llama `main` y se convierte en la rama activa. En la mayoría de los casos, esta contiene el desarrollo local, aunque esto es puramente por convención y no es forzoso.
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.{% else %}Name often chosen as an alternative to `master` for the default branch of a repository.{% endif %}
 - 
   term: principal
   description: >-
-    La rama predeterminada en muchos de los repositorios de Git. Predeterminadamente, cuando creas un repositorio de Git nuevo en la línea de comandos, se crea una rama que se llama `master`. Muchas de las herramientas ahora utilizan un nombre alterno para la rama predeterminada. Por ejemplo, cuando creas un repositorio nuevo en GitHub, la rama predeterminada se llama `main`.
+    The default branch in many Git repositories. By default, when you create a new Git repository on the command line, a branch called `master` is created. Many tools now use an alternative name for the default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} For example, when you create a new repository on GitHub, the default branch is called `main`.{% endif %}
 - 
   term: Gráfico de miembros
   description: Un gráfico del repositorio que muestra todas las bifurcaciones de un repositorio.
diff --git a/translations/es-ES/data/glossaries/internal.yml b/translations/es-ES/data/glossaries/internal.yml
index e6b3d761ca..79946c4e18 100644
--- a/translations/es-ES/data/glossaries/internal.yml
+++ b/translations/es-ES/data/glossaries/internal.yml
@@ -60,6 +60,10 @@
 - 
   term: Azure
   description: Una plataforma de informática en la nube de Microsoft.
+- 
+  term: Azure DevOps
+  description: >-
+    A Microsoft product offering source code hosting, issues, CI/CD pipelines, and other developer services. The on-premises version was formerly known as Team Foundation Server. The cloud-hosted version was formerly known as Visual Studio Team Services.
 - 
   term: repositorio en blanco
   description: >-
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    Un producto de Microsoft que ofrece administración de código fuente y otros servicios de equipo.
+    The former name of a Microsoft product that provides source code management and other team services. Now known as Azure DevOps Server.
 - 
   term: Textile
   description: >-
diff --git a/translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..2dca1436bf
--- /dev/null
+++ b/translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: Acceso al borrado de versiones de paquetes
+  description: >-
+    Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados.
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: Implementaciones
+  description: >-
+    Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue.
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción.
+  description: >-
+    Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción.
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - Actualiza varias refs en una sola operación.
+  description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación.
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: Detalles de Eventos del Proyecto
+  description: >-
+    Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto.
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: Crear adjuntos de contenido
+  description: Esta vista previa agrega soporte para crear adjuntos de contenido.
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: Vista Previa de Etiquetas
+  description: >-
+    Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas.
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: Importar Proyecto
+  description: Esta vista previa agrega soporte para importar proyectos.
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Vista Previa de las Tareas de Revisión del Equipo
+  description: >-
+    Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo.
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/es-ES/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/es-ES/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..26e14af85f
--- /dev/null
+++ b/translations/es-ES/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: 'Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución.'
+    reason: 'Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario.'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.'
+    reason: Los asignados ahora pueden ser maniquíes.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: 'Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución.'
+    reason: 'Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: 'Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución.'
+    reason: 'Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: 'Se eliminará a `user`. Utiliza el campo `assignee` en sustitución.'
+    reason: Los asignados ahora pueden ser maniquíes.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: 'Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución.'
+    reason: 'Se eliminará a `Sponsorship.maintainer`.'
+    date: '2020-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: 'Se eliminará a `isUnlicensed`.'
+    reason: Todos los miembros pendientes consumen una licencia
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: 'se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`.'
+    reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado.
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: 'Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución.'
+    reason: 'Se eliminará a `timeline`'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: 'Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución.'
+    reason: 'Se eliminará a `timeline`'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: 'Se eliminará a `INVITEE_LOGIN`.'
+    reason: '`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: 'Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`.'
+    reason: 'Se eliminará a `Sponsorship.sponsor`.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: 'Se eliminará a `isUnlicensed`.'
+    reason: Todos los miembros consumen una licencia
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: 'Se eliminará a `isUnlicensed`.'
+    reason: Todos los colaboradores externos consumen una licencia
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: 'Se eliminará a `isUnlicensed`.'
+    reason: Todos los colaboradores pendientes consumen una licencia
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: 'El `DRAFT` se eliminará. Utiliza PullRequest.isDraft en su lugar.'
+    reason: El estado del DRAFT se eliminará de esta enumeración y se deberá utilizar `isDraft` en su lugar
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nplasterer
diff --git a/translations/es-ES/data/learning-tracks/README.md b/translations/es-ES/data/learning-tracks/README.md
index 9d3b1c93e4..5cfdb7f064 100644
--- a/translations/es-ES/data/learning-tracks/README.md
+++ b/translations/es-ES/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # Enfoques de Aprendizaje (conocidas como Rutas de Aprendizaje)
 
-Los enfoques de aprendizaje son una recolección de artículos que te ayudan a dominar un tema específico. Los enfoques de aprendizaje se definen por producto.
\ No newline at end of file
+Los enfoques de aprendizaje son una recolección de artículos que te ayudan a dominar un tema específico. Los enfoques de aprendizaje se definen por producto. For example, see https://docs.github.com/en/actions/guides.
+
+Learning track data for a product is defined in two places:
+
+1. A simple array of learning track names is defined in the product sublanding index page frontmatter.
+
+    For example, in `content/actions/guides/index.md`:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. Additional data for each track is defined in a YAML file named for the **product** in the `data` directory.
+
+    For example, in `data/learning-tracks/actions.yml`, each of the items from the content file's `learningTracks` array is represented with additional data such as `title`, `description`, and an array of `guides` links.
+
+    One learning track in this YAML **per version** must be designated as a "featured" learning track via `featured_track: true`, which will set it to appear at the top of the product sublanding page. A test will fail if this property is missing.
+
+    The `featured_track` property can be a simple boolean (i.e., `featured_track: true`) or it can be a string that includes versioning statements (e.g., `featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`). If you use versioning, you'll have multiple `featured_track`s per YML file, but make sure that only one will render in each currently supported version. A test will fail if there are more or less than one featured link for each version.
+
+Versioning for learning tracks is processed at page render time. The code lives in [`lib/learning-tracks.js`](lib/learning-tracks.js), which is called by `page.render()`. The processed learning tracks are then rendered by `layouts/product-sublanding.html`.
+
+The schema for validating the learning track YAML lives in [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) and is exercised by [`tests/content/lint-files.js`](tests/content/lint-files.js).
diff --git a/translations/es-ES/data/learning-tracks/actions.yml b/translations/es-ES/data/learning-tracks/actions.yml
index 69c1fc1d11..6ec8539ae8 100644
--- a/translations/es-ES/data/learning-tracks/actions.yml
+++ b/translations/es-ES/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: 'Crea y prueba tu código'
   description: 'Puedes crear flujos de trabajo de integración contínua (IC) justo en tu repositorio.'
diff --git a/translations/es-ES/data/learning-tracks/admin.yml b/translations/es-ES/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..941e80539c
--- /dev/null
+++ b/translations/es-ES/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: 'Inicia con {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/es-ES/data/release-notes/2-20/15.yml b/translations/es-ES/data/release-notes/2-20/15.yml
index aa3c664487d3ed9e6eec19ea4fa1d5deaa039dd4..ea9c2f763c27eccfae882ab3f05bc6cac0e8155d 100644
GIT binary patch
literal 4546
zcmbtXO>Y}F5bZg?f-n%MF|v|&ZCSE`wg?h83E;Fq+>b+0*xX%e&6G=S`Qcb8`eS<Z
zA*bAO)gS8{?n?59Vpz2R!>bjCoHz64%`i!lM<w^-fc3IrHcW<-B-`sfa-#6kXm{|4
zF+2w={p@5aFGPI9Si-(f@DqK$p-=amu-^9eo5L5cpB-#(vtKo5=Rs*<c`lVKdC5w_
z3ZuO>iXM4U2xpkoyu=y2G&qaNQfM!yvY3B<$`oh#L9s^ITKf4X&Nx%XvETx?5)V9h
zT3*1|(Uvff+Ig-E$?@Hjo#r+gX;bG`#AQ}A#z}AD9*vdf(Ow(c4=+D1w&O(*7Jk8L
z=7M9dUoai&`K85)uFqb`;_Mbi?9#d`=bxES3zXM32MjHBHUFZSmyKD(MQDk`2nNtx
z^RecR{S^e9U@eS3I|R&|@#Rw_4##rlO$if)zjI+7a@hiZDgCREvqO!@05{@&EG$+q
zPH&{4_#nibW&JE;GfId;qMWRBi{{<)-wu;Vm2@~t$A5f#=6&N127}^U^pPVg`o>m+
zqLN82HNDlm7JYpGfgZlQZvLdtj&6a#nS|YTKrBC>UsBc-d)HV~Szc3Wv8FI}BeVlX
ztY*U6=stdGQLcQ;P0)VUucSW<c^_st_wUEZYF&dp?D0Qrfnv2}&^|8yH9@ICI!gB^
z<EQsuJx+J%Afe0ES-n-U98(Q=5FCuNpctjS;mEV^(%{(qi}I4Pe=UtpRH#W*)ctV)
zXqWPA5W!^WWR%^7Wt~Mf*~}tKM?0HYr2E-$Gm8v|Y-o}057*`;57koPdOt-yvZ9jC
zTd+T92D&)@9wHXFMx}z1U}O}r>P#e1iK(m--ZW~)TIqoq_$b~(-#lc9RtcAo$|T~V
z!6pw$V3v;WB;)M_!XjM@oFu(>s8Cc9EudWhmOMA?jFXg-j@jajUYxp_Q>Hp)O+W|?
znuC?7KF#d>vQZ?A1i6&1F<LH!pDT!!lX0K8$kSF(pqg|Xn#P3l^M99SN<1hq+1|#1
z$#%aQm@R0O6+k4YnH11<O%QVqr6Q=@qizv^fQGjS0wk%l)Uc*pDP*2H2nZBKii}A1
z57_BT<5BU&pTe_TRuzQUpK;B4HNQB4q4^-nllJ%CDfzdOkvl|aP2P91bh8o}4)<<L
z*H)A+Vv1&5RY3zc@@*VCH6GhQ09@CeSs7xkL6a^T8q0%2IF_Lp4Tr3j@YsSkU7a9I
zin+qd#>a{QsZe(!fn~J;FFFD5lsntonXJt)TDY!OgAHM$M7G5o>?+@tFbNtHQGCgP
zH8iKG#jU20SPh*SbC7yLN>AOaHf^)7srPCbqkvJPl@?H|jRq9trnWq!G$0v!n=v8X
z-CZx1q#0Y!Do6&ek$q>VXA98TwnG|GJfdGsWN$|tL&e)ste<DUA3q4m{&3Uwm5%S=
zG@7wc$N~*Iag3ZATQ4)Mh!9@H>8w%wBT`Hy9jO@wGLrVq&%eB&>OMYxg?~9sbDX%2
zE|Dv-m|JwYNH&dhvPOY>p0`2cl?@GVxe$Z*@+%YD!$P;eX;+?%*OTB+Z9eD|>0G#3
zLfsU$X4b^yCg+#Xg4i!nVhEFydN~qz^6``+$2~8oJ{AhX3M-%=C?9Gb(94C^@Diz`
zPL18{{|iowVvtTI`)idVHpwGo9+amVN1_W*o==0Qz;sOg&geMI(d><$h9aiohP<IW
zlmJRVNL*_1-dO%1FSAK@o6PNO34uO>KV8FyyBuK=-JM3UqaTmSbr7q)QV900;I@hr
zXpJ@(y^Ixr8D`20!9Iw5HB7g%N>lV8#~d)oa1lr#^oEzoR4R-&7;a`JSQ5+bmL=R1
z3I@mxu^|1E8j%AJFcr+u^y3rF;#fmN$imLtKSZ6{cR3vG?oGbl(0i0b)MNwF`ZiT~
z#Kn^pXwclkRm>_>@NMd-TWLj+pqm{>Hpx+<CnAtj>nAyvt~OVFr}w4N2sMIfG5=x4
z0Uu_#tKfb$8le}WyCB8_SIPVK_Ukay;ds1r$3*vh*-Xyj9UMMv5jB?g=MHur9GoGC
z!3tauDZ5)y;M(u(xzQTgYJ1z2$iad-|CNkUV7vP?v<-o>G$pjffUK)9qi`+ET)<$s
zy1VD|FAkbm#tYucmHUS$ssN4FxXcP&h{1vncg?-T2Cf7uIo9;@a@BcF;P4yBv5ck*
mIf1*<AtD>DgdswNq|ZNTR2~ThcmtsKhjJs+yF2SIE&l;-06wVz

literal 5369
zcmbtY+iu%N5Pi>A3=9-%4O0?n%aRPVMdG-rfd(z&q<IL6WJ#{bMaW%Zmz1m){r8?(
zl5!L&s+{;qmi982GiT0hDr$K}gJ>L$gYhhgE(cGXOloDcyLv)|&y7{}`u#%POaBc~
zKtBceiT_SduV3B1zP*0>+tukQJtZqkQ%g!rDoNgBFCRq9rqI%gSQR*lR>F}=rLNUN
z$&{3)7pnfXiRllKNk?@qY8=oMDaCw9RTx!c-71%w;zkvz(iw^EO%6+j^u|dWBu3ZP
z6a}{6<3eSP72XQ7z}b=-ol0A*`H)Ij>~PdLERNUPN3Numq)kn(Su9kdU~sX9gRZtJ
zVS|KDsT6Qj)l?bhR9r}^P3JcUp)9e+5hB1BcV6D;TH4AgC+SYwrL>5EtA$SBz-!*^
z9mWpjwgY#D8%fl)NIqiI%11~`7*a`FD%{Wa7)q=}O1*VHTKhuv7?XDFAhB2gAsm6C
zAUMD`!^_1NJ%nT1frqsXQteZvVt@q6fa$wFlh48@Xo*doBVY)j#_enGW}REpWcjB-
zzUyF1&zg*$nMMP5l{J|a<&fS=%Ec0SV=Gd+{_`gA@DIn6a5kiWzVoR=zUjMvDX;6w
zU5!SWs`DluBB|ZSQN?f_RZUThqS@^H?8v3_adhm`+5F<@rPJyEE)6nSw)RfP<Fl@U
zkMwUo{@>&KP|Rn?E}f6($1a`C!=snZj*r@G&gqsq<zj6!?&A{B;Pmw6&GXwgFFmno
zQYG+%N+XdZ(skH1!2cm`^IQg;niW?|0~P@5B`D97IS0(saZ=9!Tm-2ExJ#wMB`6v#
zN)!r~HJbMutNzAj(8rRC+)5CSs_`urWoikA#3p4)H>CtkiGpsQJ1)P^$%ImsdUo^H
zZJ*wG2wQ|^#_R4_`+DUd#nPc9nW|d@_g?U5mSC@p<q$-}DDst^qgBKbUJ1}!rs4U!
zt!kbA^?i@uWGRQGs;wLvn~jo81+mg2e9I9W;{Tud!;jnBe`uL$H;3%B<uomo@NT~A
z*n5{x9!!Wm&kP@!0>>XqChexSgu+QUpB*gc&sI;v^BouudK~|Oe&HLd=R6<Hrb;~q
zJ>^O&@Q*{E>p8Qh^y94uD7u~&bu19hCI@M5-;U@YaqRAh!pT9_-Q5w+qk}xQyCcFS
zhlpp-j&MHSn~k{1HUet!lu*|WdGT_HWkzAL41n`8hYKsqC2JW7m_Sq&S{?YuGfys3
zS}3htj^(z|n!6{jmM#ECm;e$2y5n227lnu0$v&^A;a;y<E)H()*>doc_j1$iC4F#f
z2gg6aA&93|^_c{clNCy?vOEw=p^9EQqAUxr8uVkU<-i!FuuuUAkYWjip3Yp>?kS+C
zj;+5v9z~Z2YjDqwFuM3+3{IYlTEqgX&&t3-ws92Tq+o(&r#kN!aF<pP8z4ZE)*5?7
zA6@_-73)55uL4ZKk~w}Jl;Zw<*IwSYzYjiqi_7QH!7jV&@_2l?OFbt&_1tQ5rbJ%h
zwxhK1exhx0?;}u9?{gyX4I(iak6V{f1&oIt+<iG9Oj0`;G`?_LVpUZipW<!Oj4sb-
zdy|zQvJiGW{CMob3E`ngTTn!&%A^Up<oN+(Yuq^7<h5_^uG8%D9s@%uSj1|N*^;Lv
zU-vsTZ-qYI!QJ$rj4vO@Ug5>Xe)i&6oV=9-)UZfXFpq00?vb?Mo(;ZwH4(mNznW-z
z`u1)!)lj{zBs9p^S0V`YvAram9)RU545>?az*cvVLi1~<PN*BD;ZoVnjP2+qQV24I
z$q(Nm0C#u4(#zjpKL@1!#3y(J^P5@<!dSt2QDBTlk-uoC+nY^~?B~9uXdL?HH^yfE
z*d92W?$7W?ZC3hyJDP3K|2w09fvGn~2Xf$_ruwo&Ok1X@y=?UQc6(%P>AjmzIrs}@
zp*wtVJtuq}NLq_W;cSnX->9H#gxZvRqg;V8K`jL+NpvH=uSQfPK#}6P14#qBHWkLj
z^ecNvXH+zcc7eDt3do?}ez_yy3f#_JosD`2o;0|a0s1i5u4LTKy$g}Z2hG`%njcGJ
zG}2LoAvS0a2>fvY1i{)gmYHfZEBxR+S2{7)VwC4O+Shc7@c4f_Ww_b1K0Y-a&2|Bp
zTwKn++!P15-9v!TEP?RelN5#@W7_`SP8`S!FvyP_qEPxH4+w(bEXTvwu!FGwbW8!2
zBCjpL&_yc2PX-Rs1H9gK&S)|r5Iy4lxB}dEE*wv%=LclZTYj=SdE+O&1c(C3*d*`j
zhjVtqcA*R4<p|1;n?4}HPhr<aYh>cAeWQTh(VLl%pPl*#kO!}M0PN9>ycP}P2fNzy
z_^$qT)N)hQk02dipDZddQA!Zps88)7#kYBY5rwq%gKdl`KUn#GS2Zs0)S%ZvEkM`(
W^Ar!|>@L#&h%)>vM;GV&1^It-{!$PC

diff --git a/translations/es-ES/data/release-notes/2-21/17.yml b/translations/es-ES/data/release-notes/2-21/17.yml
index 4afce6d099..a7e7bfa3cb 100644
--- a/translations/es-ES/data/release-notes/2-21/17.yml
+++ b/translations/es-ES/data/release-notes/2-21/17.yml
@@ -1,6 +1,6 @@
 ---
 date: '2021-03-23'
-intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch.
+intro: Se han desactivado las descargas debido a un error importante que afectó a varios clientes. Pronto tendremos una solución en el siguiente parche.
 sections:
   security_fixes:
     - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server, la cual pudo haberse aprovechado al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario que utilizan las GitHub Pages no se restringieron lo suficiente e hicieron posible que se ignoraran las variables de ambiente que llevaron a la ejecución de código en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 3.0.3 y se arregló en la 3.0.3, 2.22.9, y 2.21.17. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub y se le asignó un CVE-2021-22864.'
@@ -17,11 +17,13 @@ sections:
     - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
     - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos.
-    - |
-      Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
-      To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
+    - |2
+      La rotación de bitácoras podrían fallar en señalizar los servicios para transicionar a archivos de bitácora nuevos, lo cual lleva a que los archivos de bitácora antiguos se sigan utilizando y a un agotamiento de espacio en el disco raíz eventuales.
+      Para remediar o prevenir este problema, ejecuta los siguientes comandos en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), o contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) para recibir asistencia:
 
       ```
       printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate
       sudo /usr/sbin/logrotate -f /etc/logrotate.conf
       ```
+       
+      sections -> known_issues -> 6
diff --git a/translations/es-ES/data/release-notes/2-21/18.yml b/translations/es-ES/data/release-notes/2-21/18.yml
index 2412d2d07e..38e7bb7602 100644
--- a/translations/es-ES/data/release-notes/2-21/18.yml
+++ b/translations/es-ES/data/release-notes/2-21/18.yml
@@ -1,11 +1,11 @@
 date: '2021-04-01'
 sections:
   security_fixes:
-    - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App''s [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).'
+    - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuada en GitHub Enterprise Server, la cual permitió que los tokens de acceso generados desde un [flujo de autenticación web](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) de una GitHub App leyera los metadatos de un repositorio privado a través de la API de REST sin que se le hubieran otorgado los permisos adecuados. Para explotar esta vulnerabilidad, el atacante necesitaría crear una GitHub App en la instancia y hacer que un usuario autorice la aplicación mediante el flujo de autenticación web. Los metadatos del repositorio privado que se devolvió estarían limitados a los repositorios que pertenecen al usuario al cual identifica el token. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anterior a la 3.0.4 y se arregló en las versiones 3.0.4, 2.22.10 y 2.21.18. A esta vulnerabilidad se le asignó un CVE-2021-22865 y se reportó mediante el [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).'
     - Los paquetes se actualizaron a las últimas versiones de seguridad.
   bugs:
-    - 'Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage.'
-    - The label on search results for internal repositories was shown as "Private" instead of "Internal".
+    - 'Los servicios no estaban haciendo la transición a los archivos de bitácora nuevos como parte de la rotación de bitácoras, lo cual dio como resultado un uso de disco incrementado.'
+    - La etiqueta de los resultados de la búsqueda para los repositorios internos se mostró como "Privada" en vez de como "Interna".
   known_issues:
     - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
     - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
diff --git a/translations/es-ES/data/release-notes/2-21/19.yml b/translations/es-ES/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..afb266118f
--- /dev/null
+++ b/translations/es-ES/data/release-notes/2-21/19.yml
@@ -0,0 +1,17 @@
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - 'Un mensaje de advertencia de tipo `jq: error (at <stdin>:0): Cannot index number with string "settings"` podría ocurrir durante la promoción de la réplica.'
+    - Visitar la página `/settings/emails` almacenó el estado que pudo haber causado redirecciones inadecuadas al finalizar sesión y volverla a iniciar.
+    - Las alertas de la gráfica de dependencias no se mostraron para algunos componentes cuyas asesorías tienen nombres de paquetes con mayúsculas en `vulnerable_version_ranges`.
+    - Un usuario vio un error 500 al ejecutar operaciones de git en una instancia configurada con autenticación LDAP.
+    - 'Cuando el ghe-migrator encontró errores de importación, algunas veces abortó todo el proceso y las bitácoras no incluyeron suficiente contexto.'
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos.
diff --git a/translations/es-ES/data/release-notes/2-21/20.yml b/translations/es-ES/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..8f1651b1de
--- /dev/null
+++ b/translations/es-ES/data/release-notes/2-21/20.yml
@@ -0,0 +1,18 @@
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos.
diff --git a/translations/es-ES/data/release-notes/2-21/21.yml b/translations/es-ES/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..9d57a5f401
--- /dev/null
+++ b/translations/es-ES/data/release-notes/2-21/21.yml
@@ -0,0 +1,14 @@
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos.
diff --git a/translations/es-ES/data/release-notes/2-22/10.yml b/translations/es-ES/data/release-notes/2-22/10.yml
index 628a6e1cfa..1a8d755236 100644
--- a/translations/es-ES/data/release-notes/2-22/10.yml
+++ b/translations/es-ES/data/release-notes/2-22/10.yml
@@ -1,12 +1,12 @@
 date: '2021-04-01'
 sections:
   security_fixes:
-    - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App''s [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).'
+    - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuada en GitHub Enterprise Server, la cual permitió que los tokens de acceso generados desde un [flujo de autenticación web](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) de una GitHub App leyera los metadatos de un repositorio privado a través de la API de REST sin que se le hubieran otorgado los permisos adecuados. Para explotar esta vulnerabilidad, el atacante necesitaría crear una GitHub App en la instancia y hacer que un usuario autorice la aplicación mediante el flujo de autenticación web. Los metadatos del repositorio privado que se devolvió estarían limitados a los repositorios que pertenecen al usuario al cual identifica el token. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anterior a la 3.0.4 y se arregló en las versiones 3.0.4, 2.22.10 y 2.21.18. A esta vulnerabilidad se le asignó un CVE-2021-22865 y se reportó mediante el [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).'
     - Los paquetes se actualizaron a las últimas versiones de seguridad.
   bugs:
-    - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time.
-    - 'Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage.'
-    - The label on search results for internal repositories was shown as "Private" instead of "Internal".
+    - Algunos servicios que estaban dando un tiempo UTC predetemrinado no estaban tulizando una zona horaria configurada en GitHub Enterprise 11.10.x o anterior.
+    - 'Los servicios no estaban haciendo la transición a los archivos de bitácora nuevos como parte de la rotación de bitácoras, lo cual dio como resultado un uso de disco incrementado.'
+    - La etiqueta de los resultados de la búsqueda para los repositorios internos se mostró como "Privada" en vez de como "Interna".
   known_issues:
     - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
     - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
diff --git a/translations/es-ES/data/release-notes/2-22/11.yml b/translations/es-ES/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..39041dc5e6
--- /dev/null
+++ b/translations/es-ES/data/release-notes/2-22/11.yml
@@ -0,0 +1,18 @@
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - 'Un mensaje de advertencia de tipo `jq: error (at <stdin>:0): Cannot index number with string "settings"` podría ocurrir durante la promoción de la réplica.'
+    - El restablecer respaldos continuamente a un clúster pudo haber fallado debido a que las réplicas de MySQL fallaron en conectarse al primario.
+    - El resaltado de sintaxis pudo haber fallado debido a que el contenedor de Treelights se quedó sin memoria.
+    - Visitar la página `/settings/emails` almacenó el estado que pudo haber causado redirecciones inadecuadas al finalizar sesión y volverla a iniciar.
+    - Las alertas de la gráfica de dependencias no se mostraron para algunos componentes cuyas asesorías tienen nombres de paquetes con mayúsculas en `vulnerable_version_ranges`.
+    - Las apps de integración a GitHub no pudieron notificar a los equipos cuando se les mencionó directamente a través de una @mención en un comentario de una propuesta.
+    - 'Cuando el ghe-migrator encontró errores de importación, algunas veces abortó todo el proceso y las bitácoras no incluyeron suficiente contexto.'
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
diff --git a/translations/es-ES/data/release-notes/2-22/12.yml b/translations/es-ES/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..d591710374
--- /dev/null
+++ b/translations/es-ES/data/release-notes/2-22/12.yml
@@ -0,0 +1,21 @@
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - 'During upgrades, the process would pause indefinitely after `cleanup nomad job`.'
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
diff --git a/translations/es-ES/data/release-notes/2-22/13.yml b/translations/es-ES/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..0fb5369017
--- /dev/null
+++ b/translations/es-ES/data/release-notes/2-22/13.yml
@@ -0,0 +1,19 @@
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - '**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App''s user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/).'
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
diff --git a/translations/es-ES/data/release-notes/2-22/9.yml b/translations/es-ES/data/release-notes/2-22/9.yml
index 0e11194387..491668200c 100644
--- a/translations/es-ES/data/release-notes/2-22/9.yml
+++ b/translations/es-ES/data/release-notes/2-22/9.yml
@@ -1,6 +1,6 @@
 ---
 date: '2021-03-23'
-intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch.
+intro: Se han desactivado las descargas debido a un error importante que afectó a varios clientes. Pronto tendremos una solución en el siguiente parche.
 sections:
   security_fixes:
     - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server, la cual pudo haberse aprovechado al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario que utilizan las GitHub Pages no se restringieron lo suficiente e hicieron posible que se ignoraran las variables de ambiente que llevaron a la ejecución de código en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 3.0.3 y se arregló en la 3.0.3, 2.22.9, y 2.21.17. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub y se le asignó un CVE-2021-22864.'
@@ -23,11 +23,13 @@ sections:
     - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.
     - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
-    - |
-      Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
-      To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
+    - |2
+      La rotación de bitácoras podrían fallar en señalizar los servicios para transicionar a archivos de bitácora nuevos, lo cual lleva a que los archivos de bitácora antiguos se sigan utilizando y a un agotamiento de espacio en el disco raíz eventuales.
+      Para remediar o prevenir este problema, ejecuta los siguientes comandos en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), o contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) para recibir asistencia:
 
       ```
       printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate
       sudo /usr/sbin/logrotate -f /etc/logrotate.conf
       ```
+       
+      sections -> known_issues -> 6
diff --git a/translations/es-ES/data/release-notes/3-0/0.yml b/translations/es-ES/data/release-notes/3-0/0.yml
index 4ca7dae402..6bf78ea67d 100644
--- a/translations/es-ES/data/release-notes/3-0/0.yml
+++ b/translations/es-ES/data/release-notes/3-0/0.yml
@@ -115,12 +115,13 @@ sections:
     - Los usuarios pueden descartar un mensaje obligatorio sin verificar todas las casillas.
     - '[Los scripts de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks) no pueden escribir archivos temporales, los cuales pueden causar que falle la ejecución del script. Los usuarios que utilizan ganchos de pre-recepción deberían hacer pruebas en un ambiente de pruebas para ver si dichos scripts requieren de acceso de escritura.'
     - 'Las [llaves de despliegue] de repositorio(/developers/overview/managing-deploy-keys) no pueden utilizarse con repositorios que contengan objetos LFS.'
-    - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
+    - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8.
     - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.
     - 'La gráfica de dependencias falla en interpretar los archivos de manifiesto de Python `setup.py`, lo cual resultó en errores HTTP 500 en las bitácoras. Esto, en combinación con el problema de bitácoras duplicadas, dio como resultado un incremento en la utilización del volúmen raíz.'
     - Una condición de carrera puede causar que las migraciones de la base de datos de la dependencia parezcan fallar.
     - Las instancias con la zona horaria personalizada que se mejoraron desde un lanzamiento anterior de GitHub Enterprise Server podrían tener marcas de tiempo incorrectas en la IU web.
-    - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`).'
+    - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.'
   deprecations:
     - heading: Obsoletización de GitHub Enterprise Server 2.19
       notes:
diff --git a/translations/es-ES/data/release-notes/3-0/1.yml b/translations/es-ES/data/release-notes/3-0/1.yml
index 842fc68f81..9857ee8d70 100644
--- a/translations/es-ES/data/release-notes/3-0/1.yml
+++ b/translations/es-ES/data/release-notes/3-0/1.yml
@@ -40,11 +40,12 @@ sections:
     - 'Los usuarios pueden descartar un mensaje obligatorio sin verificar todas las casillas.'
     - '[Los scripts de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks) no pueden escribir archivos temporales, los cuales pueden causar que falle la ejecución del script. Los usuarios que utilizan ganchos de pre-recepción deberían hacer pruebas en un ambiente de pruebas para ver si dichos scripts requieren de acceso de escritura.'
     - 'Las [llaves de despliegue] de repositorio(/developers/overview/managing-deploy-keys) no pueden utilizarse con repositorios que contengan objetos LFS.'
-    - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
+    - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8.
     - 'El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.'
     - 'La gráfica de dependencias falla en analizar los archivos del manifiesto de Javascript `yarn.lock`, lo cual da como resultado errores 500 de HTTP en las bitácoras.'
     - 'Las instancias con la zona horaria personalizada que se mejoraron desde un lanzamiento anterior de GitHub Enterprise Server podrían tener marcas de tiempo incorrectas en la IU web.'
-    - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`).'
+    - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.'
     - |
       Los usuarios podrían experimentar que los activos tales como los avatares no carguen, o que hayan fallos en el código de subida/extracción. Esto podría darse por un desajuste de PID en el servicio `haproxy-cluster-proxy`. Para determinar si tienes una instancia afectada:
 
diff --git a/translations/es-ES/data/release-notes/3-0/2.yml b/translations/es-ES/data/release-notes/3-0/2.yml
index a66e5d176c..ec47977ed8 100644
--- a/translations/es-ES/data/release-notes/3-0/2.yml
+++ b/translations/es-ES/data/release-notes/3-0/2.yml
@@ -28,9 +28,10 @@ sections:
     - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
     - Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose como "procesos activos". Se espera que los servicios identificados se ejecuten durante el modo de mantenimiento. Si experimentas este problema y no estás seguro de cómo proceder, contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/).
-    - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
+    - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8.
     - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.
-    - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`).
+    - Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.
     - |
       Los usuarios podrían experimentar que los activos tales como los avatares no carguen, o que hayan fallos en el código de subida/extracción. Esto podría darse por un desajuste de PID en el servicio `haproxy-cluster-proxy`. Para determinar si tienes una instancia afectada:
 
diff --git a/translations/es-ES/data/release-notes/3-0/3.yml b/translations/es-ES/data/release-notes/3-0/3.yml
index 0c6d94c307..d7b0fb4ea2 100644
--- a/translations/es-ES/data/release-notes/3-0/3.yml
+++ b/translations/es-ES/data/release-notes/3-0/3.yml
@@ -1,6 +1,6 @@
 ---
 date: '2021-03-23'
-intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch.
+intro: Se han desactivado las descargas debido a un error importante que afectó a varios clientes. Pronto tendremos una solución en el siguiente parche.
 sections:
   security_fixes:
     - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server, la cual pudo haberse aprovechado al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario que utilizan las GitHub Pages no se restringieron lo suficiente e hicieron posible que se ignoraran las variables de ambiente que llevaron a la ejecución de código en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 3.0.3 y se arregló en la 3.0.3, 2.22.9, y 2.21.17. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub y se le asignó un CVE-2021-22864.'
@@ -27,14 +27,17 @@ sections:
     - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
     - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
     - Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose como "procesos activos". Se espera que los servicios identificados se ejecuten durante el modo de mantenimiento. Si experimentas este problema y no estás seguro de cómo proceder, contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/).
-    - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
+    - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8.
     - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.
-    - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
-    - |
-      Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
-      To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
+    - Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`).
+    - Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.
+    - |2
+      La rotación de bitácoras podrían fallar en señalizar los servicios para transicionar a archivos de bitácora nuevos, lo cual lleva a que los archivos de bitácora antiguos se sigan utilizando y a un agotamiento de espacio en el disco raíz eventuales.
+      Para remediar o prevenir este problema, ejecuta los siguientes comandos en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), o contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) para recibir asistencia:
 
       ```
       printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate
       sudo /usr/sbin/logrotate -f /etc/logrotate.conf
       ```
+       
+      sections -> known_issues -> 6
diff --git a/translations/es-ES/data/release-notes/3-0/4.yml b/translations/es-ES/data/release-notes/3-0/4.yml
index 14c8838931..e3e14992b9 100644
--- a/translations/es-ES/data/release-notes/3-0/4.yml
+++ b/translations/es-ES/data/release-notes/3-0/4.yml
@@ -2,23 +2,24 @@ date: '2021-04-01'
 intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".'
 sections:
   security_fixes:
-    - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App''s [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).'
+    - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuada en GitHub Enterprise Server, la cual permitió que los tokens de acceso generados desde un [flujo de autenticación web](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) de una GitHub App leyera los metadatos de un repositorio privado a través de la API de REST sin que se le hubieran otorgado los permisos adecuados. Para explotar esta vulnerabilidad, el atacante necesitaría crear una GitHub App en la instancia y hacer que un usuario autorice la aplicación mediante el flujo de autenticación web. Los metadatos del repositorio privado que se devolvió estarían limitados a los repositorios que pertenecen al usuario al cual identifica el token. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anterior a la 3.0.4 y se arregló en las versiones 3.0.4, 2.22.10 y 2.21.18. A esta vulnerabilidad se le asignó un CVE-2021-22865 y se reportó mediante el [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).'
     - Los paquetes se actualizaron a las últimas versiones de seguridad.
   bugs:
-    - 'When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed.'
-    - 'After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made.'
-    - Old GitHub Pages builds were not cleaned up leading to increased disk usage.
-    - '`memcached` was not running on active replicas.'
-    - Upgrade failed when updating file permissions when GitHub Actions was enabled.
-    - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time.
-    - 'Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage.'
-    - The `ghe-saml-mapping-csv` command-line utility produced a warning message.
-    - The label on search results for internal repositories was shown as "Private" instead of "Internal".
+    - 'Cuando se habilitó el modo de mantenimiento, algunos servicios se siguieron listando como "procesos activos", aún cuando se esperaba que estuvieran ejecutándose y no debieron haberse listado.'
+    - 'Después de mejorar de una versión 2.22.x a una 3.0.x con GitHub Actions habilitado, la versión del ejecutor auto-hospedado no se actualizó y no se hicieron actualizaciones auto-hospedadas.'
+    - Las compilaciones de las páginas antiguas de GitHub no se limpiaron y esto llevó a un incremento en el uso de disco.
+    - '`memcached` no se estaba ejecutando en las réplicas activas.'
+    - La actualización falló al actualizar los permisos de archivo cuando se habilitó GitHub Actions.
+    - Algunos servicios que estaban dando un tiempo UTC predetemrinado no estaban tulizando una zona horaria configurada en GitHub Enterprise 11.10.x o anterior.
+    - 'Los servicios no estaban haciendo la transición a los archivos de bitácora nuevos como parte de la rotación de bitácoras, lo cual dio como resultado un uso de disco incrementado.'
+    - La utilidad de línea de comando `ghe-saml-mapping-csv` produjo un mensaje de advertencia.
+    - La etiqueta de los resultados de la búsqueda para los repositorios internos se mostró como "Privada" en vez de como "Interna".
   known_issues:
     - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
     - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
     - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
     - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
     - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
-    - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
+    - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8.
     - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.
+    - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.'
diff --git a/translations/es-ES/data/release-notes/3-0/5.yml b/translations/es-ES/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..da9b18b415
--- /dev/null
+++ b/translations/es-ES/data/release-notes/3-0/5.yml
@@ -0,0 +1,26 @@
+date: '2021-04-14'
+intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - Algunas bitácoras no se incluyeron en la configuración de reenvío de bitácoras.
+    - 'Un mensaje de advertencia de tipo `jq: error (at <stdin>:0): Cannot index number with string "settings"` podría ocurrir durante la promoción de la réplica.'
+    - El restablecer respaldos continuamente a un clúster pudo haber fallado debido a que las réplicas de MySQL fallaron en conectarse al primario.
+    - Las páginas mp se estaban publicando cuando se utilizó un certificado CA personalizado.
+    - Los subdominios relacionados con los paquetes no se estaban mostrando en el mensaje de "Configuración de dominio de prueba" para el aislamiento de subdominio.
+    - El encabezado de `X-GitHub-Enterprise-Host` enviado con webhooks incluía una secuencia aleatoria en vez del nombre de host de la instancia de GitHub Enterprise Server que envió la carga útil de HTTP POST.
+    - Actualizar de una versión 2.22.x a una 3.0.x podría fallar si las Acciones de GitHub se habilitaron previamente pero se inhabilitaron antes de la mejora.
+    - Visitar la página `/settings/emails` almacenó el estado que pudo haber causado redirecciones inadecuadas al finalizar sesión y volverla a iniciar.
+    - Las apps de integración a GitHub no pudieron notificar a los equipos cuando se les mencionó directamente a través de una @mención en un comentario de una propuesta.
+    - la interpretación de reStructuredText (RST) en la IU web falló y en vez de esto se mostró un texto de marcado RST sin procesar.
+    - No se enviaron las notificaciones por correo electrónico de las alertas del Escaneo deSecretos a los usuarios autorizados cuando la gráfica de dependencias no se habilitó completamente.
+    - 'Cuando el ghe-migrator encontró errores de importación, algunas veces abortó todo el proceso y las bitácoras no incluyeron suficiente contexto.'
+    - Puede que los blocs de notas de Jupyter con caracteres no ASCII fallaran en interpretarse.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
+    - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.'
diff --git a/translations/es-ES/data/release-notes/3-0/6.yml b/translations/es-ES/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..0d5ea1f0f0
--- /dev/null
+++ b/translations/es-ES/data/release-notes/3-0/6.yml
@@ -0,0 +1,29 @@
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - 'During upgrades, the process would pause indefinitely after `cleanup nomad job`.'
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - Upgrades did not include the latest version of Actions runner properly installed.
+    - '`github-env` configuration could result in zombie processes.'
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - The Create Repository button was disabled for users who belonged to more than 50 organizations.
+    - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful.
+    - The `rms-packages` index was shown in the site admin dashboard.
+    - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form.
+    - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+    - Code Scanning backend services did not start up reliably after applying hotpatches.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
diff --git a/translations/es-ES/data/release-notes/3-0/7.yml b/translations/es-ES/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..e9404ce1e1
--- /dev/null
+++ b/translations/es-ES/data/release-notes/3-0/7.yml
@@ -0,0 +1,22 @@
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - '**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App''s user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/).'
+    - Los paquetes se actualizaron a las últimas versiones de seguridad.
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - 'When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.'
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.'
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.'
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.'
diff --git a/translations/es-ES/data/release-notes/3-1/0-rc1.yml b/translations/es-ES/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..31b0795b0e
--- /dev/null
+++ b/translations/es-ES/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security Secret Scanning
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository.
+
+          This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}:
+
+          - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37
+          - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)
+          - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets
+          - Updated the index view to made it easy to triage secrets in bulk
+          - Reduced the false positive rate on many patterns
+
+          Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+    - 
+      heading: GitHub Advanced Security billing improvements
+      notes:
+        - |
+          This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}:
+
+          - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+          - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+    - 
+      heading: Dependabot improvements
+      notes:
+        - |
+          This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}:
+
+          - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
+          - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository).
+          - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."'
+    - 
+      heading: GitHub Actions Workflow Visualization beta
+      notes:
+        - |
+
+          GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can:
+          - View and understand complex workflows
+          - Track progress of workflows in real-time
+          - Troubleshoot runs quickly by easily accessing logs and jobs metadata
+          - Monitor progress of deployment jobs and easily access deployment targets
+
+          For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+    - 
+      heading: OAuth 2.0 Device Authorization Grant
+      notes:
+        - |
+          [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser.
+
+          Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow.
+    - 
+      heading: Fusión automática de solicitudes de cambio
+      notes:
+        - |
+          With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+    - 
+      heading: Custom notifications
+      notes:
+        - |
+          You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+  changes:
+    - 
+      heading: Cambios en la administración
+      notes:
+        - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+        - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+        - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+        - Check annotations older than four months will be archived.
+    - 
+      heading: Cambios de seguridad
+      notes:
+        - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).'
+        - SARIF upload support increased to a maximum of 5000 results per upload.
+    - 
+      heading: Cambios de desarrollador
+      notes:
+        - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to.
+        - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)."
+        - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."'
+        - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.'
+        - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.'
+    - 
+      heading: Cambios a la API
+      notes:
+        - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning).
+        - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints.
+  known_issues:
+    - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
+    - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.
+    - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.
+    - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.
+    - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.
+    - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.20
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.21
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps
+      notes:
+        - 'Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, dos eventos de webhook relacionados con GitHub Apps se obsoletizaron y eliminaron en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Los eventos obsoletizados de `integration_installation` and `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Puedes encontrar más información en la [publicación del blog acerca de los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).'
+    - 
+      heading: Obsoletización de la terminal tradicional para las GitHub Apps
+      notes:
+        - Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, la terminal tradicional de GitHub Apps para crear tokens de acceso a las instalaciones se obsoletizó y se eliminará en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Puedes encontrar más información disponible en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).
+    - 
+      heading: Obsoletización de la API de aplicaciones OAuth
+      notes:
+        - 'GitHub ya no es compatible con las terminales de la aplicación de OAuth que contengan `access_token` como parámetro de ruta. Hemos incluído terminales nuevas que te permiten administrar los tokens para las apps de OAuth de forma segura al mover a `access_token` al cuerpo de solicitud. Aunque se hayan obsoletizado, aún se puede acceder a las terminales en esta versión. Intentamos eliminar estas terminales en la versión 3.4 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).'
+    - 
+      heading: Deprecation of GitHub Actions short SHA support
+      notes:
+        - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md
index c8788cd168..8bda2ec99d 100644
--- a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md
+++ b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md
@@ -4,7 +4,7 @@
 | `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". |
 | `created_workflow_run`   | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".           |
 | `delete_workflow_run`    | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)".                                                                                                                                                            |
-| `disable_workflow`       | Triggered when a workflow is disabled.                                                                                                                                                                                                                                                                                                                                           |
-| `enable_workflow`        | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.                                                                                                                                                                                                                                                                                     |
+| `disable_workflow`       | Se activa cuando se inhabilita un flujo de trabajo.                                                                                                                                                                                                                                                                                                                              |
+| `enable_workflow`        | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente.                                                                                                                                                                                                                                                                    |
 | `rerun_workflow_run`     | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)".                                                                                                                                                     |
 | `prepared_workflow_job`  | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)".  |
diff --git a/translations/es-ES/data/reusables/actions/actions-cli.md b/translations/es-ES/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..589c03e3f2
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+Para obtener más información sobre cómo configurar {% data variables.product.prodname_cli %}, consulta la sección "[Administrar GitHub Actions con GitHub CLI](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)".
diff --git a/translations/es-ES/data/reusables/actions/actions-group-concurrency.md b/translations/es-ES/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..f6038b0f10
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+Cuando un job o flujo de trabajo concurrente se pone en cola, si otro job o workflow que utilicen el mismo grupo de concurrencia en el repositorio se encuentra en progreso, el job o flujo de trabajo en cola se mostrará como `pending`. Cualquier job o flujo de trabajo pendientes anteriores en el grupo de concurrencia se cancelarán. Para también cancelar cualquier job ejecutándose concurrentemente en el mismo grupo de concurrencia, especifica `cancel-in-progress: true`.
+
+##### Ejemplos que utilizan concurrencia y comportamiento predeterminado
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### Ejemplos que utilizan concurrencia para cancelar cualquier ejecución o job en progreso
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/es-ES/data/reusables/actions/concurrency-beta.md b/translations/es-ES/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..beeac1594b
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Nota:** La concurrencia es actualmente en beta y está sujeta a cambios.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/actions/enterprise-github-connect-warning.md b/translations/es-ES/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..025c979a42
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**Nota:** Con {% data variables.product.prodname_github_connect %} habilitado, las {% data variables.product.prodname_actions %} intentarán encontrar el repositorio en tu instancia de {% data variables.product.prodname_ghe_server %} antes de revertirse a {% data variables.product.prodname_dotcom %}. Si un usuario crea una organización y repositorio en tu empresa, los cuales empaten con un nombre de organzación y repositorio en {% data variables.product.prodname_dotcom %}, el repositorio de tu empresa se utilizará en vez del repositorio de {% data variables.product.prodname_dotcom %}. Un usuario malintencionado podría sacar provecho de este comportamiento para ejecutar código como parte de un flujo de trabajo.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md b/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md
index aa11da1ebe..9c03705d2b 100644
--- a/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/es-ES/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-Las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} se diseñan para funcionar en ambientes sin acceso a internet. Predeterminadamente, los flujos de trabajo no utilizan acciones de {% data variables.product.prodname_dotcom_the_website %} y [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+Las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %} están diseñadas para funcionar como ambientes sin acceso completo a la internet. Predeterminadamente, los flujos de trabajo no utilizan acciones de {% data variables.product.prodname_dotcom_the_website %} y [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
diff --git a/translations/es-ES/data/reusables/actions/forked-secrets.md b/translations/es-ES/data/reusables/actions/forked-secrets.md
index ff5af683b8..b1597cc758 100644
--- a/translations/es-ES/data/reusables/actions/forked-secrets.md
+++ b/translations/es-ES/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-Con la excepción de `GITHUB_TOKEN`, los secretos no se pasan al ejecutador cuando un flujo de trabajo se dispara desde un repositorio bifurcado.
+Con la excepción de `GITHUB_TOKEN`, los secretos no se pasan al ejecutador cuando un flujo de trabajo se dispara desde un repositorio bifurcado.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..82a3294911
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+Registramos y mostramos dos números de confirmantes para la {% data variables.product.prodname_GH_advanced_security %} en {% data variables.product.product_location %}:
+
+- **Committers** is the number of committers who contributed to at least one {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository in an organization and who use a seat in your enterprise license. Es decir, también son un miembro de la organización, un colaborador externo, o tienen una invitación pendiente para unirse a una organización en tu empresa.
+- **Únicos para este repositorio/organización** es la cantidad de confirmantes que contribuyen únicamente a este repositorio o a los repositorios en esta organización. Esta cantidad muestra cuántas plazas de la licencia puedes liberar si inhabilitas la {% data variables.product.prodname_GH_advanced_security %} para este repositorio u organización.
+
+If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Inhabilitar la característica para este repositorio u organización no liberará plazas en tu licencia.
+
+When you remove a user from your enterprise account, the user's license is freed within 24 hours.
+
+{% note %}
+
+**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
+
+{% endnote %}
diff --git a/translations/es-ES/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/es-ES/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..bc96f8d6ac
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+Cada licencia de {% data variables.product.prodname_GH_advanced_security %} especifica una cantidad máxima de cuentas o de plazas que pueden utilizar estas características. Debes revisar de vez en cuando que tu uso esté dentro de la capacidad de tu licencia.
diff --git a/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md
index d3f00a2048..53570cd443 100644
--- a/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %} cobra por la {% data variables.product.prodname_advanced_security %} por cada confirmante. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta "[Administrar el licenciamiento para{% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)".{% endif %}
+{% data variables.product.company_short %} cobra por la {% data variables.product.prodname_advanced_security %} por cada confirmante. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% elsif currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your Enterprise](/admin/advanced-security)."{% endif %}
 
 Puedes requerir una política que controle si se les permite a los administradores de repositorio habilitar características para {% data variables.product.prodname_advanced_security %} en los repositorios de una organización. Puedes configurar una política para todas las organizaciones que le pertenezcan a tu cuenta empresarial o para las organizaciones individuales que elijas.
 
diff --git a/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..67f799a8b3
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+Cuando decides qué repositorios y organizaciones priorizar para la {% data variables.product.prodname_GH_advanced_security %}, debes revisarlas e identificar:
+
+- Las bases de código que son más críticas para el éxito de tu empresa. Estos son los proyectos para los cuales la introducción de código vulnerable, los secretos de código rígido, o las dependencias vulnerables tendrían el mayor impacto en tu empresa.
+- Las bases de código con la frecuencia de confirmación más alta. Estos son los proyectos que se desarrollan de forma más activa y, por consecuencia, hay un riesgo mayor para que se introduzcan problemas de seguridad.
+
+Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} para estas organizaciones o repositorios, debes evaluar qué otras bases de código puedes agregar sin añadir confirmantes únicos adicionales y sin usar más plazas en tu licencia. Después de esto, revisa las siguientes bases de código más ocupadas e importantes. Si quieres incrementar la cantidad de plazas en tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/es-ES/data/reusables/advanced-security/ghas-helps-developers.md b/translations/es-ES/data/reusables/advanced-security/ghas-helps-developers.md
index 7ae149aac0..e1b69b9a6e 100644
--- a/translations/es-ES/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/es-ES/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-La {% data variables.product.prodname_GH_advanced_security %} ayuda a que los desarrolladores mejoren y mantengan la seguridad y la calidad del código. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)".
+{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% endif %}
diff --git a/translations/es-ES/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/es-ES/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..b0cad7b5e8
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+When you enable or disable {% data variables.product.prodname_advanced_security %} for repositories, {% data variables.product.prodname_dotcom %} displays an overview of changes to the use of your license. Si inhabilitas el acceso a {% data variables.product.prodname_GH_advanced_security %}, se liberará cualquier plaza que utilice un confirmante "único".
+
+Si sobrepasas el límite de tu licencia, {% data variables.product.prodname_GH_advanced_security %} seguirá trabajando en todos los repositorios en donde ya se encuentre habilitado. Sin embargo, en las organizaciones en donde se habilita la {% data variables.product.prodname_GH_advanced_security %} para los repositorios nuevos, se crearán repositorios con la característica inhabilitada. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available.{% if currentVersion == "free-pro-team@latest" %} If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.{% endif %}
+
+Tan pronto como liberes algunas plazas, al inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para algunos repositorios o al incrementar tu tamaño de licencia, las opciones para habilitar la {% data variables.product.prodname_GH_advanced_security %} funcionarán nuevamente como normales.
diff --git a/translations/es-ES/data/reusables/branches/set-default-branch.md b/translations/es-ES/data/reusables/branches/set-default-branch.md
index 58297a9caf..2172601be3 100644
--- a/translations/es-ES/data/reusables/branches/set-default-branch.md
+++ b/translations/es-ES/data/reusables/branches/set-default-branch.md
@@ -1 +1 @@
-Puedes configurar el nombre de la rama predeterminada para los repositorios nuevos. For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)," "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)," and {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)."{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)."{% endif %}
+Puedes configurar el nombre de la rama predeterminada para los repositorios nuevos. Para obtener más información, consulta las secciones "[Administrar la rama predeterminada de tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)", "[Administrar el nombre de la rama predeterminada en los repositorios de tu organización](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" y {% if currentVersion == "free-pro-team@latest" %}"[Requerir políticas de administración de repositorios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)".{% else %}"[Requerir políticas de administración de repositorio en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)".{% endif %}
diff --git a/translations/es-ES/data/reusables/cli/actions-cli-version.md b/translations/es-ES/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..fdee3df42c
--- /dev/null
+++ b/translations/es-ES/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+Para acceder a todos los comandos relacionados con {% data variables.product.prodname_actions %}, debes utilizar la versión 1.9.0 o mayor.
diff --git a/translations/es-ES/data/reusables/cli/cli-auth.md b/translations/es-ES/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..eb6acfaab5
--- /dev/null
+++ b/translations/es-ES/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} puede autenticarse utilizando tu cuenta de {% data variables.product.prodname_dotcom %}. Antes de ejecutar los comandos de {% data variables.product.prodname_cli %}, necesitarás autenticarte ejecutando `gh auth login`. Para obtener más información sobre la autenticación de la línea de comandos, consulta "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)".
diff --git a/translations/es-ES/data/reusables/cli/cli-manual.md b/translations/es-ES/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..6e32a0a2a0
--- /dev/null
+++ b/translations/es-ES/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+Para obtener más información acerca de {% data variables.product.prodname_cli %}, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/cli/cli-repo.md b/translations/es-ES/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..ef836d9459
--- /dev/null
+++ b/translations/es-ES/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+Los comandos de {% data variables.product.prodname_cli %} deben ejecutarse dentro del repositorio con el cual quieras interactuar para que primero navegues al directorio que contiene la copia local de tu repositorio. Como alternativa, puedes especificar un repositorio si pasas a {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY` o `--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY` o `--repo OWNER/REPOSITORY`{% endif %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Reemplaza a `HOSTNAME` con el nombre de {% data variables.product.product_location %}. {% endif %}Reemplaza a `OWNER` con el propietario del repositorio. Reemplaza`REPOSITORY` con el nombre del repositorio.
diff --git a/translations/es-ES/data/reusables/cli/download-update-cli.md b/translations/es-ES/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..b8fbcc53a8
--- /dev/null
+++ b/translations/es-ES/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+Para descargar o mejorar {% data variables.product.prodname_cli %}, sigue las instrucciones en el [README de {% data variables.product.prodname_cli %}](https://github.com/cli/cli#installation).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/es-ES/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..a101d1809f
--- /dev/null
+++ b/translations/es-ES/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`, `csharp`, `go`, `java`, `javascript`, and `python`
diff --git a/translations/es-ES/data/reusables/code-scanning/enabling-options.md b/translations/es-ES/data/reusables/code-scanning/enabling-options.md
index 9186ad5f31..a0f48dbcab 100644
--- a/translations/es-ES/data/reusables/code-scanning/enabling-options.md
+++ b/translations/es-ES/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      Utilizar las {% data variables.product.prodname_actions %} (consulta la sección "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Configurar el {% data variables.product.prodname_code_scanning %} utilizando acciones</a>") o utilizando el {% data variables.product.prodname_codeql_runner %} en un sistema de integración continua (IC) de terceros (consulta la sección "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">Ejecutar el escaneo de código de {% data variables.product.prodname_codeql %} en tu sistema de IC</a>").
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      Third&#8209;party
-    </td>
-    
-    <td>
-      Utilizar las {% data variables.product.prodname_actions %} (consulta la sección "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Configurar el {% data variables.product.prodname_code_scanning %} utilizando accionesActions</a>") o generadas externamente y cargadas a {% data variables.product.product_name %} (consulta la sección "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}</a>").
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)").
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql %} code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
+{%- endif %}
+| Third&#8209;party | Using
+{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)").|
diff --git a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md
index e97128727c..1dc61077d4 100644
--- a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Nota:** La carga de SARIF admite un máximo de 1000 resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes.
+**Nota:** La carga de SARIF es compatible con un máximo de {% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %} resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes.
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/es-ES/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..537cbdd588
--- /dev/null
+++ b/translations/es-ES/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**Note:** Uploading SARIF data to display as {% data variables.product.prodname_code_scanning %} results in {% data variables.product.product_name %} is supported for organization-owned repositories with {% data variables.product.prodname_GH_advanced_security %} enabled{% if currentVersion == "free-pro-team@latest" %}, and public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..5c772293bc
--- /dev/null
+++ b/translations/es-ES/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.product.product_location %}.
+{% endif %}
diff --git a/translations/es-ES/data/reusables/codespaces/about-personalization.md b/translations/es-ES/data/reusables/codespaces/about-personalization.md
index fa00ae8118..a8ee5e5255 100644
--- a/translations/es-ES/data/reusables/codespaces/about-personalization.md
+++ b/translations/es-ES/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-También puedes personalizar los aspectos del ambiente de un codespace para cada codespace que tu cuenta cree. La personalización puede incluir preferencias de shell y herramientas adicionales.
+You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. La personalización puede incluir preferencias de shell y herramientas adicionales.
diff --git a/translations/es-ES/data/reusables/codespaces/about-port-forwarding.md b/translations/es-ES/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..b010026461
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+Puedes reenviar los puertos en tu codespace para probar y depurar tu aplicación.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..8ea4f5ec25
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+Después de que cambia la configuración de los {% data variables.product.prodname_codespaces %} para un repositorio, puedes aplicar los cambios a un codespace existente si vuelves a compilar el contenedor para el codespace.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index d2f101906b..f4f8c50435 100644
--- a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. En {% data variables.product.prodname_vscode %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. En {% data variables.product.prodname_vscode %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md b/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..0ee9f8b242
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Cada una de estas tiene un nivel de recursos y de facturación diferentes.<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**Nota:**{% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types:
+
+* **Básico** para actualizar un archivo y levantar una solicitud de cambios
+* **Estándar** para editar un sitio web
+* **Premium** para tareas de cálculos altos tales como análilsis de datos
diff --git a/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md b/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..87bfa539ff
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users.
+
+For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..4203c5929f
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. En tu codespace, debajo del editor de texto, haz clic en "Puertos". ![Pestaña de puertos](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/es-ES/data/reusables/codespaces/rebuild-command.md b/translations/es-ES/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..4c2882e4f1
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+Accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclare "Codespaces: Rebuild Container". Haz clic en **Codespaces: Rebuild Container**. 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/recovery-mode.md b/translations/es-ES/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..0059dc812e
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+Si los cambios a la configuración de tu codespace causan un error de contenedor, este se ejecutará en modo de recuperación y verás un mensaje de error.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/release-stage.md b/translations/es-ES/data/reusables/codespaces/release-stage.md
index fa1a751d6d..f03425ab0c 100644
--- a/translations/es-ES/data/reusables/codespaces/release-stage.md
+++ b/translations/es-ES/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Durante el periodo beta, {% data variables.product.prodname_dotcom %} no garantiza la disponibilidad de {% data variables.product.prodname_codespaces %}. Par obtener más información acerca de unirse al beta, consulta "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)".
+**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Par obtener más información acerca de unirse al beta, consulta "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)".
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/codespaces/secret-precedence.md b/translations/es-ES/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..17ca0627e6
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+Si un secreto con el mismo nombre existe en varios niveles, aquél en el nivel más bajo tomará presedencia. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/secrets-naming.md b/translations/es-ES/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..22f2c730a6
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+Las siguientes reglas aplican a los nombres secretos:
+
+* Los nombres secretos solo contienen caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) o guiones bajos (`_`). No se permiten espacios.
+* Los nombres secretos no deben comenzar con el prefijo `GITHUB_`.
+* Los nombres secretos no deben comenzar con un número.
+* Los nombres de secreto no distinguen entre mayúsculas y minúsculas.
+* Los nombres secretos deben ser únicos en el nivel en el que se hayan creado.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/secrets-on-start.md b/translations/es-ES/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..c4a5bf3b41
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/source-control-display-dark.md b/translations/es-ES/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..90b3503dcd
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/source-control-display.md b/translations/es-ES/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..09917cd3c8
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. In the Activity Bar, click the **Source Control** view.
+
+  ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/type-port-label.md b/translations/es-ES/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..ec2eb93c12
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. Teclea una etiqueta para tu puerto y luego presiona enter. ![Caja de texto para teclear la etiqueta para el puerto](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index c6b843423d..afb626e71c 100644
--- a/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-Puedes ver cada codespace que pertenezca a tu cuenta de usuario en [github.com/codespaces](https://github.com/codespaces).
+You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..a5e98437c0
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**.
+
+  !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md
index 1d04b6d65f..8e78886c20 100644
--- a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@ La siguiente tabla muestra, para cada administrador de paquetes:
 | Composer                   | `composer`       | v1, v2                          |           **✓**           |       **✓**        |                            |
 | Docker                     | `docker`         | v1                              |           **✓**           |       **✓**        |                            |
 | Hex                        | `mix`            | v1                              |                           |       **✓**        |                            |
-| elm-package                | `elm`            | v0.18, v0.19                    |           **✓**           |       **✓**        |                            |
+| elm-package                | `elm`            | v0.19                           |           **✓**           |       **✓**        |                            |
 | submódulo de git           | `gitsubmodule`   | N/A (sin versión)               |           **✓**           |       **✓**        |                            |
 | GitHub Actions             | `github-actions` | N/A (sin versión)               |           **✓**           |       **✓**        |                            |
 | Módulos de Go              | `gomod`          | v1                              |           **✓**           |       **✓**        |           **✓**            |
diff --git a/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md
index 51edf1d608..c7621276a5 100644
--- a/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@ Cuando creas una solicitud de extracción desde un repositorio bifurcado al repo
 
 Los flujos de trabajo no se ejecutan en repositorios bifurcados por defecto. Debes habilitar las Acciones de GitHub en la pestaña **Actions (Acciones)** del repositorio bifurcado.
 
+{% if currentVersion == "free-pro-team@latest"%}
+Cuando un colaborador de primera vez emite una solicitud de cambios a un repositorio púb lico, un mantenedor con acceso de escritura debe aprobar los flujos de trabajo que se estpen ejecutando en la solicitud de cambios. Para obtener más información, consulta la sección "[Aprobar flujos de trabajo desde bifurcaciones públicas](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)".
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} Los permisos para el `GITHUB_TOKEN` en los repositorios bifurcados son de solo lectura. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
 
 {% note %}
diff --git a/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md
index 9e198c5cb7..4e8bc8374d 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. Opcionalmente, da clic en **Obtener reporte de uso** para que se te envíe un archivo CSV por correo electrónico del uso de almacenamiento para {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} a la dirección de correo electrónico principal de la cuenta. ![Descargar reporte en CSV](/assets/images/help/billing/actions-packages-report-download.png)
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![Descargar reporte en CSV](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md b/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md
index 9c980a2fe2..558d725f7b 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. Dentro de "Resumen de facturación", haz clic en **Change to yearly billing (Cambiar a facturación anual)** o **Change to monthly billing (Cambiar a facturación mensual)**. ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/change-plan-duration-link.png)
+1. Under "Current monthly bill" or "Current yearly bill", click **Switch to yearly billing** or **Switch to monthly billing**. ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md b/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md
index 8d9dbac417..2121e37d1c 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. Si estás actualizando desde {% data variables.product.prodname_free_team %}, dentro de "Actualizando a", selecciona un producto. ![Botón para actualizar](/assets/images/help/billing/upgrade-to-product.png)
+1. Under "Compare plans", you can compare the features of each plan. Depending on your current plan and what plan you have chosen, click either **Upgrade to Team** or **Upgrade to Enterprise**. ![Compare plans and upgrade](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md b/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md
index 71beb790aa..8f297745a6 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md
@@ -1 +1 @@
-If you use a coupon to pay for a subscription, when the coupon expires, your payment method will be charged the full cost of your subscription. If you do not have a saved payment method, your account will be downgraded to {% data variables.product.prodname_free_user %} for user accounts or {% data variables.product.prodname_free_team %} for organizations.
+Si utilizas un cupón para pagar una suscripción, cuando este venza, se hará un cobro a tu método de pago por el costo total de tu suscripción. Si no tienes un método de pago guardado, tu cuenta bajará de categoría a {% data variables.product.prodname_free_user %} para cuentas de usuario o a {% data variables.product.prodname_free_team %} para organizaciones.
diff --git a/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md b/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md
index 1d8551ce75..881b26fa1b 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. Debajo de "Información de facturación", elige pagar con una tarjeta de crédito o con PayPal. ![Cambiar métodos de pago de facturación](/assets/images/help/billing/billing_switch_payments.png)
+1. Under "Payment method", choose to pay with a credit card or PayPal. ![Cambiar métodos de pago de facturación](/assets/images/help/billing/billing_switch_payments.png)
 1. Completa el formulario de información de pago. Posteriormente, da clic en **Emitir**.
diff --git a/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md b/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md
index 36bd3d1e36..1a9a722b78 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. Junto a "Datos de {% data variables.large_files.product_name_short %}", haz clic en **Add more data (Añadir más datos)** o utiliza el menú desplegable de edición y haz clic en **Add more data packs (Añadir más paquetes de datos)**. ![Botón Agregar más datos](/assets/images/help/billing/data-pack-purchase-more.png)
+1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**. ![Botón Agregar más datos](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/es-ES/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..4f2bd7bf2d
--- /dev/null
+++ b/translations/es-ES/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. At the top of the page, under "Payment information", click **Manage spending limit**. ![Manage spending limit link](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md b/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md
index 1b1dd5a7e9..48a69739a3 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. Dentro de "Resumen de facturación", revisa cuándo vence tu próximo pago. ![Próxima fecha de facturación](/assets/images/help/billing/settings_billing_next_payment.png)
+1. At the top of the page, under "Next payment due", review when your next payment is due. ![Próxima fecha de facturación](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md b/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md
index 44edfaec51..f5a0d1cf18 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. Dentro de "Suscripciones", revisa tus cambios pendientes. ![Sección de suscripciones de la configuración de facturación listando cualquier cambio pendiente de suscripción](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. Under "Current plan", review your pending changes. ![Sección de suscripciones de la configuración de facturación listando cualquier cambio pendiente de suscripción](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md b/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md
index 17e5ad9cde..35e89db0ce 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. Dentro de "Información de facturación", haz clic en **Update payment method (Actualizar método de pago)**. ![Botón para actualizar método de pago](/assets/images/help/billing/update_payment_method.png)
+1. At the top of the page, under "Payment information", click **Update payment method**. ![Botón para actualizar método de pago](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md b/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md
index 1bcaa79e89..aba4840ee5 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. Si estás mejorando tu producto desde {% data variables.product.prodname_free_team %}, da clic en **Opciones de mejora**. Si estás mejorando tu producto desde {% data variables.product.prodname_team %}, utiliza el menú desplegable de **Editar** y da clic en **Mejorar**. ![Botón de mejorar opciones](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. Click **Upgrade** next to "Current plan".
diff --git a/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md b/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md
index 9ae5e5b66e..be030ab6a6 100644
--- a/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/es-ES/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. Dentro de "Información de facturación", haz clic en **View payment method (Ver método de pago)**. ![Ver enlace de historial de pagos](/assets/images/help/billing/view-payment-history-link.png)
+1. At the top of the page, under "Next payment due", click **View payment history**. ![Ver enlace de historial de pagos](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/add-a-domain.md b/translations/es-ES/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..aa91200e53
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. Haz clic en **Add a domain (Agregar un dominio)**. ![Botón para agregar un dominio](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/es-ES/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/es-ES/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..9230029f77
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)".
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..7c0eb23e43
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+Puedes confirmar que tu empresa controle los sitios web y direcciones de correo electrónico que se listan en los perfiles de cualquier organización que le pertenezca a tu cuenta empresarial si verificas los dominios. Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+Después de que verificas la propiedad de los dominios de tus cuentas empresariales, se mostrará una insignia de "Verificado" en el perfil de cada organización que liste el dominio en su perfil. {% data reusables.organizations.verified-domains-details %}
+
+Los propietarios de las organizaciones podrán verificar la identidad de los miembros de éstas si visualizan la dirección de correo electrónico de cada miembro dentro del dominio verificado.
+
+Después de que verificas los dominios para tu cuenta empresarial, puedes restringir las notificaciones de correo electrónico a los dominios verificados para todas las organizaciones que le pertenezcan a tu cuenta empresarial. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-approving.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-removing.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-verifying.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..0c23acd147
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+Para verificar el dominio de tu cuenta empresarial, debes tener acceso para modificar los registros del dominio con tu servicio de hospedaje de dominios.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Espera a que cambie la configuración de tu DNS, lo cual puede llevar hasta 72 horas. Puedes confirmar que tu configuración de DNS cambió si ejecutas el comando `dig` en la línea de comandos, reemplazando `ENTERPRISE-ACCOUNT` con el nombre de tu cuenta empresarial, y `example.com` con el dominio que te gustaría verificar. Deberías ver tu nuevo registro TXT enumerado en el resultado del comando.
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. Opcionalmente, después de que la insignia de "Verificado" se pueda ver en el perfil de tus organizaciones, borra la entrada de TxT del registro de DNS en tu servicio de hospedaje de dominio. ![Insignia Verificado](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..360792cf73
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+Los dominios se pueden heredar desde la cuenta empresarial, o los puedes configurar una organización específica. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Si se habilitan las restricciones de correo electrónico para una cuenta empresarial, los propietarios de la organización no las pueden inhabilitar para ninguna organización que pertenezca a la cuenta empresarial. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..73df355257
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md
index e4dbf13f79..85644af45c 100644
--- a/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/es-ES/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. Debajo de "Configuración", da clic en **Dominios verificados**. ![Pestaña de "Dominios verificados"](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md
index 1bf0c8547b..dda3ba720a 100644
--- a/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/es-ES/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1 +1 @@
-No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener un mejor desempeño, más seguridad y nuevas características, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">actualiza a la última versión de GitHub Enterprise</a>. Para obtener ayuda con la actualización, <a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">contacta al soporte de GitHub Enterprise</a>.
+No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener un mejor desempeño, más seguridad y nuevas características, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">actualiza a la última versión de GitHub Enterprise</a>. Para obtener ayuda con la actualización, <a href="https://enterprise.github.com/support">contacta al soporte de GitHub Enterprise</a>.
diff --git a/translations/es-ES/data/reusables/enterprise_installation/replica-limit.md b/translations/es-ES/data/reusables/enterprise_installation/replica-limit.md
index 21bd197854..9256d594de 100644
--- a/translations/es-ES/data/reusables/enterprise_installation/replica-limit.md
+++ b/translations/es-ES/data/reusables/enterprise_installation/replica-limit.md
@@ -1,7 +1,7 @@
 {% if  currentVersion ver_gt "enterprise-server@2.21" %}
 {% note %}
 
-**Note:** There is a maximum of 8 high availability replicas (both passive and active/geo replicas) allowed for {% data variables.product.product_name %}.
+**Nota:** Hay un máximo de 8 réplicas de disponibilidad alta (tanto pasivas como activas/geo replicas) que se permiten para {% data variables.product.product_name %}.
 
 {% endnote %}
 
diff --git a/translations/es-ES/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/es-ES/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..81dc20a203
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### Acerca de los requisitos mínimos para {% data variables.product.prodname_ghe_server %} 3.0 y superior
+
+Antes de actualizar a {% data variables.product.prodname_ghe_server %} 3.0 o superior, revisa los recursos de hardware que has aprovisionado para tu instancia. {% data variables.product.prodname_ghe_server %} 3.0 presenta características nuevas tales como {% data variables.product.prodname_actions %} y el {% data variables.product.prodname_registry %}, y requiere más recursos que la versión 2.22 y anteriores. Para obtener más información, consulta la sección de [notas de lanzamiento para {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes).
+
+Los requisitos que incrementan para {% data variables.product.prodname_ghe_server %} 3.0 y posterior se muestran en **negritas** en la siguiente tabla.
+
+| Licencias de usuario                     |                                     vCPU |                                          Memoria |                         Almacenamiento conectado | Almacenamiento raíz |
+|:---------------------------------------- | ----------------------------------------:| ------------------------------------------------:| ------------------------------------------------:| -------------------:|
+| Prueba, Demo o 10 usuarios no frecuentes |   **4**<br/>_Aumentando desde 2_ |   **32 GB**<br/>_Aumentando desde 16 GB_ | **150 GB**<br/>_Aumentando desde 100 GB_ |              200 GB |
+| 10-3000                                  |   **8**<br/>_Aumentando desde 4_ |   **48 GB**<br/>_Aumentando desde 32 GB_ | **300 GB**<br/>_Aumentando desde 250 GB_ |              200 GB |
+| 3000-5000                                |  **12**<br/>_Aumentando desde 8_ |                                            64 GB |                                           500 GB |              200 GB |
+| 5000-8000                                | **16**<br/>_Aumentando desde 12_ |                                            96 GB |                                           750 GB |              200 GB |
+| 8000-10000+                              | **20**<br/>_Aumentando desde 16_ | **160 GB**<br/>_Aumentando desde 128 GB_ |                                          1000 GB |              200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+Para obtener más información acerca de los requisitos de hardware para las {% data variables.product.prodname_actions %}, consulta la sección "[Comenzar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md
index 47f08d9681..e7d45c6fb3 100644
--- a/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/es-ES/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Advertencia**: El cambiar esta configuración ocasionará que {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} se reinicie. Debes calcular este cambio con cuidado para minimizar el tiempo de inactividad.
+**Warning**: Changing this setting will cause user-facing services on {% data variables.product.prodname_ghe_server %} to restart. You should time this change carefully, to minimize downtime for users.
 
 {% endwarning %}
diff --git a/translations/es-ES/data/reusables/gated-features/code-scanning.md b/translations/es-ES/data/reusables/gated-features/code-scanning.md
index 34f9b11d6c..02cd041cdd 100644
--- a/translations/es-ES/data/reusables/gated-features/code-scanning.md
+++ b/translations/es-ES/data/reusables/gated-features/code-scanning.md
@@ -1,5 +1,5 @@
-{% if currentVersion == "free-pro-team@latest" %}El {% data variables.product.prodname_code_scanning_capc %} se encuentra disponible para todos los repositorios públicos y para aquellos privados que pertenezcan a organizaciones en donde la {% data variables.product.prodname_GH_advanced_security %} se encuentra habilitada.
-{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}El {% data variables.product.prodname_code_scanning_capc %} se encuentra disponible si la {% data variables.product.prodname_GH_advanced_security %} se encuentra habiltiada en el repositorio.
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
 {%- elsif currentVersion == "github-ae@latest" %}
 El {% data variables.product.prodname_code_scanning_capc %} se encuentra disponible como parte de la {% data variables.product.prodname_GH_advanced_security %}, la cual es gratuita durante el lanzamiento beta.
 {%- else %}
diff --git a/translations/es-ES/data/reusables/gated-features/ghas.md b/translations/es-ES/data/reusables/gated-features/ghas.md
index a05b1f4401..0434361631 100644
--- a/translations/es-ES/data/reusables/gated-features/ghas.md
+++ b/translations/es-ES/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-Las licencias de {% data variables.product.prodname_GH_advanced_security %} se encuentran disponibles para las cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}. La {% data variables.product.prodname_GH_advanced_security %} también se incluye en {% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %} y en todos los repositorios públicos de {% data variables.product.prodname_dotcom_the_website %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)".
\ No newline at end of file
+Las licencias de {% data variables.product.prodname_GH_advanced_security %} para cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} La {% data variables.product.prodname_GH_advanced_security %} también se incluye en todos los repositorios públicos de {% data variables.product.prodname_dotcom_the_website %}.{% endif %} Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/gated-features/github-insights.md b/translations/es-ES/data/reusables/gated-features/github-insights.md
index 5f07e45586..36b2f9d358 100644
--- a/translations/es-ES/data/reusables/gated-features/github-insights.md
+++ b/translations/es-ES/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %} se encuentra disponible con {% data variables.product.prodname_ghe_one %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)".
+{% data variables.product.prodname_insights %} se encuentra disponible con {% data variables.product.prodname_ghe_one %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/gated-features/packages.md b/translations/es-ES/data/reusables/gated-features/packages.md
index 0ba004086f..d69e1fa573 100644
--- a/translations/es-ES/data/reusables/gated-features/packages.md
+++ b/translations/es-ES/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-El {% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, {% data variables.product.prodname_ghe_one %}, y {% data variables.product.prodname_ghe_managed %}.
+{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}.
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-{% data variables.product.prodname_registry %} no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_one %}. {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_registry %} no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/es-ES/data/reusables/gated-features/secret-scanning.md b/translations/es-ES/data/reusables/gated-features/secret-scanning.md
index bb305c7214..c231456d6e 100644
--- a/translations/es-ES/data/reusables/gated-features/secret-scanning.md
+++ b/translations/es-ES/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible {% if currentVersion == "free-pro-team@latest" %}en los repositorios públicos, y en los repositorios privados que pertenezcan a las organizaciónes con {% else %}si tienes {% endif %}una {% data variables.product.prodname_advanced_security %}licencia. {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion == "github-ae@latest" %}
 El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible como parte de la {% data variables.product.prodname_GH_advanced_security %}, la cual es gratuita durante el lanzamiento beta.
-{% endif %}
\ No newline at end of file
+{%- else %}
+El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible si tienes una licencia de {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/gated-features/security-center.md b/translations/es-ES/data/reusables/gated-features/security-center.md
index 3006b19baa..3a96114f95 100644
--- a/translations/es-ES/data/reusables/gated-features/security-center.md
+++ b/translations/es-ES/data/reusables/gated-features/security-center.md
@@ -1,4 +1,4 @@
 {% if currentVersion == "github-ae@latest" %}
-The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
+El resumen de seguridad de tu organización se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}, la cual es gratuita durante el lanzamiento beta.
 {% else %}
-The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
+El resumen de seguridad de tu organización se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/es-ES/data/reusables/github-actions/forked-write-permission.md b/translations/es-ES/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..74b6c33bab
--- /dev/null
+++ b/translations/es-ES/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+Puedes utilizar la clave `permissions` para agregar y eliminar los permisos de lectura para los repositorios bifurcados pero, habitualmente, no puedes otorgar acceso de escritura. La excepción a este comportamiento es donde un usuario administrador seleccionó la opción de **Enviar tokens a los flujos de trabajo desde las solicitudes de cambios** en la configuración de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} en un repositorio](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)".
\ No newline at end of file
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
new file mode 100644
index 0000000000..af725850c5
--- /dev/null
+++ b/translations/es-ES/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+Alcances y valores de acceso disponibles:
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+Si especificas el acceso para cualquiera de estos alcances, todos aquellos que no se especifiquen se configuran como `none`.
+
+Puedes utilizar la siguiente sintaxis para definir el acceso de lectura o escritura para todos los alcances disponibles:
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-actions/github-token-permissions.md b/translations/es-ES/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..19556a282a
--- /dev/null
+++ b/translations/es-ES/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+El secreto de `GITHUB_TOKEN` se configuro para un token de acceso para el repositorio cada vez que comienza un job en un flujo de trabajo. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}Debes configurar los permisos para este token de acceso en el archivo del flujo de trabajo para otorgar acceso de lectura para el alcance `contents` y acceso de escritura para el de `packages`. {% else %}Tiene permisos de lectura y escritura para los paquetes del repositorio en donde se ejecuta el flujo de trabajo. {% endif %}Para obtener más información, consulta la sección "[Autenticarte con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md
index e17c17aadf..8a5ed8d965 100644
--- a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md
+++ b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md
@@ -2,7 +2,7 @@
 
 La plantilla inicial de flujo de trabajo configura el `PATH` para que contenga OpenJDK 8 para las plataformas x64. Si quieres utilizar una versión diferente de Java, o enfocarte en una arquitectura diferente (`x64` o `x86`), puedes utilizar la acción `setup-java` para elegir un ambiente de ejecución de Java diferente.
 
-For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`.
+Por ejemplo, para utilizar la versión 11 de JDK que se proporciona con Adoptium para la plataforma x64, puedes utilizar la acción `setup-java` y configurar los parámetros `java-version`, `distribution` y `architecture` en `'11'`, `'adopt'` y `x64`.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
index a6b00543d9..01e328391b 100644
--- a/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/es-ES/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`.
+Ejecuta el comando `mvn --batch-mode deploy` para publicar a {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}La clave de `permissions` especifica el acceso otorgado al `GITHUB_TOKEN`.{% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index e64c6a9bd2..91b3a7ef98 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **Advertencia**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    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)."
 
diff --git a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md b/translations/es-ES/data/reusables/github-actions/supported-github-runners.md
index 9bf01e2812..823dc5e8f0 100644
--- a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/es-ES/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**Warning**: Ubuntu 16.04 is being deprecated. If any of your workflows use Ubuntu 16.04, migrate to Ubuntu 20.04 or 18.04. For more information, see [the blog post](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021).
+
+{% endwarning %}
+
 | Entorno virtual      | Etiqueta de flujo de trabajo YAML |
 | -------------------- | --------------------------------- |
 | Windows Server 2019  | `windows-latest` o `windows-2019` |
+| Windows Server 2016  | `windows-2016`                    |
 | Ubuntu 20.04         | `ubuntu-latest` o `ubuntu-20.04`  |
 | Ubuntu 18.04         | `ubuntu-18.04`                    |
-| Ubuntu 16.04         | `ubuntu-16.04`                    |
 | macOS Big Sur 11.0   | `macos-11.0`                      |
 | macOS Catalina 10.15 | `macos-latest` or `macos-10.15`   |
diff --git a/translations/es-ES/data/reusables/github-actions/workflow-permissions-intro.md b/translations/es-ES/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..dbc6a1e941
--- /dev/null
+++ b/translations/es-ES/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+Puedes configurar los permisos predeterminados que se otorgaron al `GITHUB_TOKEN`. Para obtener más información sobre el `GITHUB_TOKEN`, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)". Puedes elegir entre un conjunto restringido de permisos o una configuración permisiva como lo predeterminado. 
diff --git a/translations/es-ES/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/es-ES/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..0e80bf145d
--- /dev/null
+++ b/translations/es-ES/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+Cualquiera con acceso de escritura en un repositorio puede modificar los permisos que se otorgaron al `GITHUB_TOKEN`, agregando o eliminando el acceso conforme se requiera, si editan la clave `permissions` en el archivo de flujo de trabajo. Para obtener más información, consulta los [`permisos`](/actions/reference/workflow-syntax-for-github-actions#permissions). 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/gpg/x-509-key.md b/translations/es-ES/data/reusables/gpg/x-509-key.md
index 49e22d5866..c5db29f649 100644
--- a/translations/es-ES/data/reusables/gpg/x-509-key.md
+++ b/translations/es-ES/data/reusables/gpg/x-509-key.md
@@ -30,7 +30,7 @@ Puedes usar [smimesign](https://github.com/github/smimesign) para firmar confirm
   $ git config --local gpg.program smimesign
   ```
   Si estás utilizando una llave X.509 que coincide con tu identidad de persona que confirma el cambio, puedes comenzar firmando confirmaciones y etiquetas.
-4. Si no estás utilizando una llave X.509 que coincide con tu identidad de persona que confirmar el cambio, enumera las llaves X.509 para las cuales tienes tanto un certificado como una llave privada utilizando el comando `smimesign --list-keys`.
+4. If you're not using an X.509 key that matches your committer identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
   ```shell
   $ smimesign --list-keys
   ```
diff --git a/translations/es-ES/data/reusables/identity-and-permissions/verification-status-check.md b/translations/es-ES/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..ccd2ea2fc9
--- /dev/null
+++ b/translations/es-ES/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+Puedes comprobar el estado de verificación de tus confirmaciones o etiquetas firmadas en {% data variables.product.product_name %} y ver por qué las firmas de tu confirmación podrían no ser verificadas. Para obtener más información, consulta "[Comprobar la confirmación y el estado de verificación de firma de la etiqueta](/articles/checking-your-commit-and-tag-signature-verification-status)".
diff --git a/translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..bb9ea14675
--- /dev/null
+++ b/translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Vigilant mode is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..766d57819f
--- /dev/null
+++ b/translations/es-ES/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| Estado                      | Descripción                                                                                                                                                                                                                                                                              |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Verificado**              | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.                                                                                                                                                       |
+| **Partially&nbsp;verified** | The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified. |
+| **Sin verificar**           | Any of the following is true:<br>- The commit is signed but the signature could not be verified.<br>- The commit is not signed and the committer has enabled vigilant mode.<br>- The commit is not signed and an author has enabled vigilant mode.<br>           |
diff --git a/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md
index aad15ed791..065104a36e 100644
--- a/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/es-ES/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. Utiliza el menú desplegable de **Editar** y da clic en **Cancelar plan**. ![Enlace de cancelación en la sección de Compras de Marketplace de tu configuración de facturación para tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to cancel, use the **Edit** drop-down and click **Cancel plan**. ![Enlace de cancelación en la sección de Compras de Marketplace de tu configuración de facturación para tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index 5ff8eeb3ff..b9901ac4a8 100644
--- a/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/es-ES/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. Debajo de "Suscripciones", a un costado de la prueba gratuita que quieres cancelar, utiliza el menú desplegable de Editar y da clic en **Cancelar Plan**.
+1. Next to the free trial you'd like to cancel, use the **Edit** drop-down and click **Cancel plan**.
diff --git a/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md
index 597ce6e4b0..25563cb37a 100644
--- a/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/es-ES/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Debajo de "Tu suscripción", junto a la aplicación a la cual quieres bajar, utiliza el menú desplegable de Editar y da clic en **Cambiar plan** o **Cancelar plan**. ![Enlace de editar en la sección de Compras de Marketplace para la configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you'd like to downgrade, use the **Edit** drop-down and click **Change plan** or **Cancel plan**. ![Enlace de editar en la sección de Compras de Marketplace para la configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md
index fdda91148f..f54bb6a803 100644
--- a/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/es-ES/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Utiliza el menú desplegable de **Editar** y da clic en **Cambiar plan**. ![Menú desplegable de editar en la sección de compras de Marketplace para tu configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to upgrade, use the **Edit** drop-down and click **Change plan**. ![Menú desplegable de editar en la sección de compras de Marketplace para tu configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md b/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..e5d59aceea
--- /dev/null
+++ b/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}issues, pulls requests, releases, security alerts, or discussions{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}issues, pull requests, releases, or discussions{% endif %}
diff --git a/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md b/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..83331428df
--- /dev/null
+++ b/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)".
diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index d7a164d468..dc6894c3f7 100644
--- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-Puedes elegir el método de entrega para las notificaciones sobre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}las {% else %}alertas de seguridad{% endif %} del {% data variables.product.prodname_dependabot_alerts %} en los repositorios que estés observando, así como la frecuencia en las que se te envían éstas.
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+You can choose the delivery method and frequency of notifications about
+{% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts.
+{% else %}
+You can choose the delivery method for notifications about
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
+{% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/add-a-domain.md b/translations/es-ES/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..58007e1809
--- /dev/null
+++ b/translations/es-ES/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. Haz clic en **Add a domain (Agregar un dominio)**. ![Botón para agregar un dominio](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/es-ES/data/reusables/organizations/billing_plans.md b/translations/es-ES/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..2d929e2b2e
--- /dev/null
+++ b/translations/es-ES/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. In your organization's Settings sidebar, click **Billing & plans**. ![Configuración de facturación](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md b/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md
index b627b7b8e4..79c9db7121 100644
--- a/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/es-ES/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. A la derecha del dominio pendiente de verificar, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Seguir verificando**. ![Botón para continuar verificando](/assets/images/help/organizations/continue-verifying-domain.png)
-10. Haz clic en **Verify domain (Verificar dominio)**. ![Botón para verificar dominio](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. Da clic en **Verificar**. ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/organizations/domains-approve-domain.md b/translations/es-ES/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/es-ES/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/es-ES/data/reusables/organizations/domains-approve-it-instead.md b/translations/es-ES/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/es-ES/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/es-ES/data/reusables/organizations/filter-security-overview.md b/translations/es-ES/data/reusables/organizations/filter-security-overview.md
index f13a2d07cb..131e58a021 100644
--- a/translations/es-ES/data/reusables/organizations/filter-security-overview.md
+++ b/translations/es-ES/data/reusables/organizations/filter-security-overview.md
@@ -1 +1 @@
-1. Optionally, filter the list of alerts. You can click multiple filters in the drop-down filter menus to narrow your search. You can also type search qualifiers in the **Search repositories** field. For more information about the available qualifiers, see "[Filtering the list of alerts](#filtering-the-list-of-alerts)." ![The drop-down filter menus and Search repositories field in the security overview](/assets/images/help/organizations/security-overview-filter-alerts.png)
\ No newline at end of file
+1. Opcionalmente, filtra la lista de alertas. Puedes hacer clic en varios filtros de los menús desplegables de filtros para especificar tu búsqueda. También puedes teclear calificadores de búsqueda en el campo **Buscar repositorios**. Para obtener más información sobre los calificadores disponibles, consulta la sección "[Filtrar la lista de alertas](#filtering-the-list-of-alerts)". ![Los menús desplegables de filtro y el campo de búsqueda de repositorios en el resumen de seguridad](/assets/images/help/organizations/security-overview-filter-alerts.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/organizations/security-overview.md b/translations/es-ES/data/reusables/organizations/security-overview.md
index f900c33c67..a176601969 100644
--- a/translations/es-ES/data/reusables/organizations/security-overview.md
+++ b/translations/es-ES/data/reusables/organizations/security-overview.md
@@ -1 +1 @@
-1. Under your organization name, click {% octicon "shield" aria-label="The Security shield" %} **Security**. ![Organization security button](/assets/images/help/organizations/organization-security-tab.png)
\ No newline at end of file
+1. Debajo del nombre de tu organización, haz clic en {% octicon "shield" aria-label="The Security shield" %} **Seguridad**. ![Botón de seguridad de la organización](/assets/images/help/organizations/organization-security-tab.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/organizations/team-security-overview.md b/translations/es-ES/data/reusables/organizations/team-security-overview.md
index 8e112f5dc3..81982e77be 100644
--- a/translations/es-ES/data/reusables/organizations/team-security-overview.md
+++ b/translations/es-ES/data/reusables/organizations/team-security-overview.md
@@ -1 +1 @@
-1. At the top of the team's page, click {% octicon "shield" aria-label="The security icon" %} **Security**. ![Team security overview](/assets/images/help/teams/org-team-page-security-overview.png)
+1. En la parte superior de la página del equipo, haz clic en {% octicon "shield" aria-label="The security icon" %} **Seguridad**. ![Resumen de seguridad del equipo](/assets/images/help/teams/org-team-page-security-overview.png)
diff --git a/translations/es-ES/data/reusables/organizations/verified-domains.md b/translations/es-ES/data/reusables/organizations/verified-domains.md
index 50ecf2c709..9714304429 100644
--- a/translations/es-ES/data/reusables/organizations/verified-domains.md
+++ b/translations/es-ES/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. En la barra lateral izquierda, da clic en **Dominios verificados**. ![Botón de dominios verificados](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/es-ES/data/reusables/package_registry/about-packaging-and-actions.md b/translations/es-ES/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..ad41d21ef0
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,31 @@
+### Empaquetado en flujos de trabajo de integración continua
+
+Un paso de empaquetado es una parte común de un flujo de trabajo de integración continua o entrega continua. Crear un paquete al final de un flujo de trabajo de integración continua puede ayudar durante las revisiones de código en una solicitud de extracción.
+
+Después de construir y probar tu código, un paso de empaquetado puede generar un artefacto ejecutable o desplegable. Según el tipo de aplicación que estás construyendo, este paquete se puede descargar de forma local para pruebas manuales, disponible para que los usuarios los descarguen o se implementen en un entorno de ensayo o producción.
+
+Por ejemplo, un flujo de trabajo de integración continua para un proyecto Java puede ejecutar `mvn package` para generar un archivo JAR. O un flujo de trabajo de CI para una aplicación Node.js puede crear un contenedor Docker.
+
+Ahora, cuando revises una solicitud de extracción, podrás ver la ejecución del flujo de trabajo y descargar el artefacto que se produjo.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+Esto te permitirá ejecutar el código en la solicitud de extracción en tu máquina, lo que puede ayudar con la depuración o la prueba de la solicitud de extracción.
+
+### Flujos de trabajo para publicar paquetes
+
+Además de cargar artefactos de empaquetado para las pruebas en un flujo de trabajo de integración continua, puedes crear flujos de trabajo que construyan tu proyecto y publiquen paquetes en un registro de paquete.
+
+* **Publicar paquetes en el {% data variables.product.prodname_registry %}**
+  El {% data variables.product.prodname_registry %} puede actuar como un servicio de hospedaje para paquetes para varios tipos de éstos. Puedes elegir compartir tus paquetes con todos los {% data variables.product.prodname_dotcom %}, o paquetes privados para compartir con los colaboradores o una organización. For more information, see "[Introduction to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages)."
+
+  Es posible que desees publicar paquetes para el {% data variables.product.prodname_registry %} en cada subida a la rama predeterminada. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.
+
+* **Publicar paquetes en un registro de paquetes**  
+  Para muchos proyectos, publicar en un registro de paquete se realiza cada vez que se lanza una nueva versión de un proyecto. Por ejemplo, un proyecto que produce un archivo JAR puede cargar nuevos lanzamientos en el repositorio central de Maven. O bien, un proyecto de .NET puede generar un paquete NuGet y cargarlo en la galería de NuGet.
+
+  Puedes automatizar esto creando un flujo de trabajo que publique paquetes en un registro de paquetes en cada creación de lanzamiento. Para obtener más información, consulta "[Crear lanzamientos](/github/administering-a-repository/creating-releases)."
diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/es-ES/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..a02c0f89d8
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index bba75037ea..10490aef74 100644
--- a/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -1,7 +1,7 @@
 1. Crea un token de acceso personal nuevo (PAT) con los alcances adecuados para las tareas que quieres realizar. Si tu organización requiere SSO, debes hablitarlo para tu token nuevo.
   {% warning %}
 
-  **Note:** By default, when you select the `write:packages` scope for your personal access token (PAT) in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for GitHub Actions workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://github.com/settings/tokens/new?scopes=write:packages`.
+  **Nota:** Predeterminadamente, cuando seleccionas el alcance `write:packages` para tu token de acceso personal (PAT) en la interface de usuario, también se seleccionará el alcance `repo`. El alcance `repo` ofrece un acceso amplio e innecesario, el cual te recomendamos no utilices para los flujos de trabajo de GitHub Actions en particualr. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". Como medida alterna, puedes seleccionar solo el alcance de `write:packages` para tu PAT en la interface de usuario con esta url: `https://github.com/settings/tokens/new?scopes=write:packages`.
 
   {% endwarning %}
 
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. Utilizando el CLI para tu tipo de contenedor, ingresa en el
-servicio del {% data variables.product.prodname_github_container_registry %} en `ghcr.io`.
+servicio del {% data variables.product.prodname_container_registry %} en `ghcr.io`.
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index 1f5ec021f1..39784e7bc5 100644
--- a/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -1,10 +1,10 @@
 {% if currentVersion == "free-pro-team@latest" %}
 
-Los PAT pueden otorgar accesos amplios a tu cuenta. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}.
+Los PAT pueden otorgar accesos amplios a tu cuenta. Puedes seleccionar solo el alcance necesario de `read:packages`, `write:packages`, o `delete:packages` cuando creas un PAT para autenticarte en el {% data variables.product.prodname_container_registry %}.
 
-Para autenticarte en el {% data variables.product.prodname_github_container_registry %} dentro de un flujo de trabajo de {% data variables.product.prodname_actions %}, utiliza el `GITHUB_TOKEN` para tener la mejor experiencia y seguridad.
+To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
 
-Para obtener orientación sobre cómo actualizar tus flujos de trabajo que se autentican en `ghcr.io` con un token de acceso personal, consulta la sección "[Mejorar un flujo de trabajo que acceda a `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)".
+Para obtener orientación sobre cómo actualizar tus flujos de trabajo que se autentican en `ghcr.io` con un token de acceso personal, consulta la sección "[Mejorar un flujo de trabajo que acceda a `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)".
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md b/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md
index b89ac62089..d7d94fe43c 100644
--- a/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md
+++ b/translations/es-ES/data/reusables/package_registry/checksum-maven-plugin.md
@@ -1,5 +1,5 @@
 {%- if currentVersion == "github-ae@latest" %}
-1. In the `plugins` element of the *pom.xml* file, add the [checksum-maven-plugin](http://checksum-maven-plugin.nicoulaj.net/index.html) plugin, and configure the plugin to send at least SHA-256 checksums.
+1. En el elemento `plugins` del archivo *pom.xml*, agrega el plugin [checksum-maven-plugin](http://checksum-maven-plugin.nicoulaj.net/index.html) y configúralo para enviar por lo menos comprobaciones SHA-256.
     ```xml
     <plugins>
         <plugin>
diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-beta.md b/translations/es-ES/data/reusables/package_registry/container-registry-beta.md
index ed9e035957..892226449b 100644
--- a/translations/es-ES/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/es-ES/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Nota:** El {% data variables.product.prodname_github_container_registry %} se encuentra actualmente en su fase de beta público y está sujeto a cambios. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. Para utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitar la vista previa de características. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" y [Habilitar el soporte mejorado para los contenedores](/packages/guides/enabling-improved-container-support)".
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. Durante el beta, el almacenamiento y el ancho de banda son gratuitos. To use the {% data variables.product.prodname_container_registry %}, you must enable the feature preview. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" and "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/package_registry/docker-vs-container-registry.md b/translations/es-ES/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..60ba872bf2
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**Comparing the Docker registry and the {% data variables.product.prodname_container_registry %}:**
+- The {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) offers improved performance for containers and will supercede the Docker registry in the future.
+- You can migrate your Docker images and workflows from the Docker registry  (`docker.pkg.github.com`)  to the {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) for granular permissions, container storage optimization, and more. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."
+
+{% endnote %}
+{% endif %}
diff --git a/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md
index 297d3259b9..67608dc1e2 100644
--- a/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/es-ES/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Nota:** El registro de Docker de {% data variables.product.prodname_registry %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} ofrecerá compatibilidad mejorada para contenedores en un lanzamiento subsecuente de {% data variables.product.product_name %}.{% elsif currentVersion == "free-pro-team@latest" %} ahora ofrece una compatibilidad mejorada para los conetenedores. Para obtener más información, consulta la sección "[Acerca del Registro de Contenedores de GitHub](/packages/guides/about-github-container-registry)". Para aprender a migrar tus imágenes existentes de Docker y cualquier flujo de trabajo que las utilice, consulta las secciones "[Migrarse a {% data variables.product.prodname_github_container_registry %} para las imágenes de Docker](/packages/guides/migrating-to-github-container-registry-for-docker-images)" y "[Guías de los contenedores para el {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)".{% endif %}
+**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will be superseded in a future {% data variables.product.product_name %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif currentVersion == "free-pro-team@latest" %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)." {% endif %}
 
 {% endwarning %}
diff --git a/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md
index ac76364a4e..3b8032849e 100644
--- a/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/es-ES/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Nota:** Antes de que puedas utilizar el {% data variables.product.prodname_github_container_registry %}, debes habilitar la característica para tu cuenta. Para obtener más información, consulta la sección "[Habilitar el soporte mejorado para los contenedores](/packages/guides/enabling-improved-container-support)".
+**Note:** Before you can use the {% data variables.product.prodname_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/es-ES/data/reusables/package_registry/github-token-security-over-pat.md b/translations/es-ES/data/reusables/package_registry/github-token-security-over-pat.md
index 2bb99fd72c..14e21fb8d5 100644
--- a/translations/es-ES/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/es-ES/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-El {% data variables.product.prodname_github_container_registry %} ahora es compatible con `GITHUB_TOKEN` para tener una autenticación más fácil y segura en tus flujos de trabajo. Si tu flujo de trabajo está utilizando un token de acceso personal (PAT) para autenticarse en `ghcr.io`, entonces te recomendamos ampliamente que actualices tu flujo de trabajo para utilizar un `GITHUB_TOKEN`.
+The {% data variables.product.prodname_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. Si tu flujo de trabajo está utilizando un token de acceso personal (PAT) para autenticarse en `ghcr.io`, entonces te recomendamos ampliamente que actualices tu flujo de trabajo para utilizar un `GITHUB_TOKEN`.
 
-Para obtener más información acerca del `GITHUB_TOKEN`, consulta las secciones de "[Secretos cifrados"](/actions/reference/encrypted-secrets)" y "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)".
\ No newline at end of file
+For more information about `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
diff --git a/translations/es-ES/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/es-ES/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..9bc7ee0d6e
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below use this type of permissions:
+- Docker registry (`docker.pkg.github.com`)
+- npm registry
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+The Container registry (`ghcr.io`) offers granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account.
+{% endif %}
+
+For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)"{% if currentVersion == "free-pro-team@latest" %} or "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."{% endif %}.
diff --git a/translations/es-ES/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/es-ES/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..b3fcedaa55
--- /dev/null
+++ b/translations/es-ES/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+If you have admin permissions to a container image, you can set the access permissions for the container image to private or public. Las imágenes públicas permiten el acceso anónimo y pueden extraerse sin autenticación o ingresar a ellas através del CLI.
+
+Como administrador, también puedes otorgar permisos de acceso para una imagen de contenedor que esté separada de los permisos que configuraste a nivel de organización y de repositorio.
+
+Puedes otorgar un rol de acceso a cualquier persona en el caso de las imagenes de contenedor que pertenecen a, o que publica una cuenta de usuario. Puedes otorgar un rol de acceso a cualquier persona o equipo en la organización para las imágenes de contenedor que pertenecen a, o que publica una cuenta de usuario.
+
+| Permiso   | Descripción del acceso                                                                                                                                             |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| lectura   | Puede descargar el paquete. <br> Puede leer los metadatos del paquete.                                                                                       |
+| escritura | Puede cargar y descargar este paquete. <br> Puede leer y escribir metadatos del paquete.                                                                     |
+| admin     | Puede cargar, descargar, borrar y administrar este paquete. <br> Puede leer y escribir metadatos del paquete. <br> Puede otorgar permisos del paquete. |
+{% endif %}
diff --git a/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md b/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md
index e030fa91f7..d07a98c30e 100644
--- a/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md
+++ b/translations/es-ES/data/reusables/pages/private_pages_are_public_warning.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Advertencia**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Si tu administrador de sitio habilitó las Páginas Públicas, {% endif %}Los sitios de {% data variables.product.prodname_pages %} estarán disponibles al público general en la internet{% if currentVersion == "free-pro-team@latest" %} predeterminadamente{% endif %}, aún si el repositorio del sitio es privado o interno.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} De otra forma, si {% else %} Si{% endif %} tienes datos sensibles en el repositorio de tu sitio, puede que quieras eliminarlos antes de publicarlos. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %}
+**Advertencia**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Si tu administrador de sitio habilitó las Páginas Públicas, {% endif %}Los sitios de {% data variables.product.prodname_pages %} estarán disponibles al público general en la internet{% if currentVersion == "free-pro-team@latest" %} predeterminadamente{% endif %}, aún si el repositorio del sitio es privado o interno.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} De otra forma, si {% else %} Si{% endif %} tienes datos sensibles en el repositorio de tu sitio, puede que quieras eliminarlos antes de publicarlos. Para obtener más información, consulta las secciones {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}"[Configurar las {% data variables.product.prodname_pages %} en tu empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" y {% endif %} "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" y "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)".{% else %}".{% endif %}
 
 {% endwarning %}
diff --git a/translations/es-ES/data/reusables/pages/sidebar-pages.md b/translations/es-ES/data/reusables/pages/sidebar-pages.md
index fb1c3dcd79..8ed9cd467b 100644
--- a/translations/es-ES/data/reusables/pages/sidebar-pages.md
+++ b/translations/es-ES/data/reusables/pages/sidebar-pages.md
@@ -1,3 +1,3 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
-1. En la barra lateral izquierda, da clic en **Páginas**. ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png)
+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)
 {% endif %}
diff --git a/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md
index 4c0999ddc5..12c2c36bb6 100644
--- a/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md
+++ b/translations/es-ES/data/reusables/pages/www-and-apex-domain-recommendation.md
@@ -1 +1 @@
-Si estás utilizando un dominio apex como tu dominio personalizado, te recomendamos configurar un subdominio `www`. Si configuras los registros correctos para cada dominio, teclea a tu proveedor de DNS, {% data variables.product.prodname_pages %} creará automáticamente redireccionamientos entre los dominios. For example, if you configure `www.example.com` as the custom domain for your site, and you have {% data variables.product.prodname_pages %} DNS records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. Note that automatic redirects only apply to the `www` subdomain. Automatic redirects do not apply to any other subdomains, such as `blog`.
+Si estás utilizando un dominio apex como tu dominio personalizado, te recomendamos configurar un subdominio `www`. Si configuras los registros correctos para cada dominio, teclea a tu proveedor de DNS, {% data variables.product.prodname_pages %} creará automáticamente redireccionamientos entre los dominios. Por ejemplo, sin configuras `www.example.com` como el dominio personalizado de tu sitio y tienes configurados los dominios de DNS de {% data variables.product.prodname_pages %} para los dominios de apex y `www`, entonces, `example.com` te redirigirá a `www.example.com`. Nota que las redirecciones automáticas solo aplican al subdominio `www`. Las redirecciones automáticas no aplican a ningún otro subdominio, tal como `blog`.
diff --git a/translations/es-ES/data/reusables/profile/access_org.md b/translations/es-ES/data/reusables/profile/access_org.md
index 36f9fc193c..9356bd4ee8 100644
--- a/translations/es-ES/data/reusables/profile/access_org.md
+++ b/translations/es-ES/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. En la parte izquierda de tu página de perfil, debajo de "Organizaciones", da clic en el icono de tu organización. ![iconos de organización](/assets/images/help/profile/profile_orgs_box.png)
+1. In the top right corner of {% data variables.product.prodname_dotcom %}, click your profile photo, then click **Your organizations**. ![Your organizations in the profile menu](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/profile/org_settings.md b/translations/es-ES/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..4c7f5b7078
--- /dev/null
+++ b/translations/es-ES/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. Click **Settings** next to the organization. ![The settings button](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md b/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md
index e87269f62d..32f5c49ac1 100644
--- a/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/es-ES/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. En la barra lateral izquierda, debajo de la foto de perfil del usuario, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Bloquear o reportar usuario**. ![Enlace para reportar o bloquear usuario](/assets/images/help/profile/profile-block-or-report-button.png)
+1. In the left sidebar, below the user's profile information, click **Block or Report**. ![Block or report link](/assets/images/help/profile/profile-block-or-report-button.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 78012d1600..b257890f80 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
@@ -6,6 +6,6 @@ Este ejemplo activa el flujo de trabajo diariamente a las 5:30 y 17:30 UTC:
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
index 85efad2b34..78005657fa 100644
--- a/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
+++ b/translations/es-ES/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
@@ -6,6 +6,6 @@
 - Cuando [LDAP Sync esté habilitado](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), si eliminas a una persona de un repositorio, perderá acceso, pero sus bifurcaciones no se eliminarán. Si la persona se agrega a un equipo con acceso al repositorio original de la organización dentro de los tres meses, su acceso a las bifurcaciones se restaurarán de manera automática la próxima vez que ocurra una sincronización.{% endif %}
 - Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual.
 
-- Las personas con permisos administrativos en un repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} pueden dejar de permitir la bifurcación de dicho repositorio, y los propietarios de la organización pueden dejar de permitir la bifurcación de cualquier repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} en una organización. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+- Las personas con permisos administrativos en un repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} pueden dejar de permitir la bifurcación de dicho repositorio, y los propietarios de la organización pueden dejar de permitir la bifurcación de cualquier repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} o interno{% endif %} en una organización. Para obtener más información, consulta las secciones "[Administrar la política de bifurcación para tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" y "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)".
 
 {% endwarning %}
diff --git a/translations/es-ES/data/reusables/repositories/request-changes-tips.md b/translations/es-ES/data/reusables/repositories/request-changes-tips.md
index b68d3eba20..0a63d827b1 100644
--- a/translations/es-ES/data/reusables/repositories/request-changes-tips.md
+++ b/translations/es-ES/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - Los propietarios y administradores del repositorio pueden fusionar una solicitud de extracción, incluso si no recibió una revisión de aprobación o si un revisor que solicitó modificaciones abandonó la organización o no está disponible.
 - Si están habilitadas las revisiones requeridas y el descarte de una revisión en espera, y se sube una confirmación de modificación de código a la rama de una solicitud de extracción aprobada, se descarta la aprobación. La solicitud de extracción se debe volver a revisar y aprobar antes de que se pueda fusionar.
 - Cuando varias solicitudes de extracción abiertas tienen una rama de encabezado que apunta a la misma confirmación, no podrás fusionarlas si una o ambas tienen una revisión pendiente o rechazada.
+- Pull request authors cannot approve their own pull requests.
 
 {% endtip %}
diff --git a/translations/es-ES/data/reusables/repositories/security-guidelines.md b/translations/es-ES/data/reusables/repositories/security-guidelines.md
index cb47dfe5d2..a23d868eb7 100644
--- a/translations/es-ES/data/reusables/repositories/security-guidelines.md
+++ b/translations/es-ES/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-Puedes crear una política de seguridad para dar instrucciones a las personas para reportar las vulnerabilidades de seguridad de manera responsable en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/articles/adding-a-security-policy-to-your-repository)".
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+You can create a security policy to give people instructions for reporting security vulnerabilities in your project. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/code-security/getting-started/adding-a-security-policy-to-your-repository)".
 {% endif %}
diff --git a/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md
index fdd8e95478..f2ce861033 100644
--- a/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/es-ES/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. En la barra lateral de seguridad, da clic en **{% data variables.product.prodname_dependabot_alerts %}**. ![Pestaña {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. En la barra lateral de seguridad, haz clic en **{% data variables.product.prodname_dependabot_alerts %}**.{% if currentVersion == "free-pro-team@latest" %} ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/es-ES/data/reusables/secret-scanning/beta.md b/translations/es-ES/data/reusables/secret-scanning/beta.md
index 6227019cb5..ef2e4ad07a 100644
--- a/translations/es-ES/data/reusables/secret-scanning/beta.md
+++ b/translations/es-ES/data/reusables/secret-scanning/beta.md
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**Nota:** El {% data variables.product.prodname_secret_scanning_caps %} se encuentra en beta dentro de {% data variables.product.prodname_ghe_server %} 3.0. Para encontrar un lanzamiento de disponibilidad general del escaneo de secretos, mejora al último lanzamiento de {% data variables.product.prodname_ghe_server %}.
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} was in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of {% data variables.product.prodname_secret_scanning %}, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
 
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 01fbab29b2..0c57629445 100644
--- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| Socio                     | Secreto compatible                                  | Slug de la API                           |
-| ------------------------- | --------------------------------------------------- | ---------------------------------------- |
-| n/a                       | Token Web de JSON                                   | json_web_token                         |
-| n/a                       | Credencial de Cliente de OAuth                      | api_credential_assignment              |
-| Adafruit IO               | Clave de IO de Adafruit                             | adafruit_io_key                        |
-| Alibaba Cloud             | ID de Clave de Acceso a la Nube de Alibaba          | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Secreto de Clave de Acceso a la Nube de Alibaba     | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | ID de Clave de Acceso de AWS de Amazon              | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Clave de Acceso Secreta de AWS de Amazon            | aws_secret_access_key                  |
-| Asana                     | Asana Personal Access Token                         | asana_personal_access_token            |
-| Atlassian                 | Token de API de Atlassian                           | atlassian_api_token                    |
-| Atlassian                 | Token Web de JSOn de Atlazzian                      | atlassian_jwt                            |
-| Azure                     | Token de Acceso Personal de Azure DevOps            | azure_devops_personal_access_token   |
-| Azure                     | Token de Azure SAS                                  | azure_sas_token                        |
-| Azure                     | Certificado de Administración de Servicios de Azure | azure_management_certificate           |
-| Azure                     | Secuencia de Conexión de Azure SQL                  | azure_sql_connection_string            |
-| Azure                     | Clave de Cuenta de Almacenamiento de Azure          | azure_storage_account_key              |
-| Clojars                   | Token de Despliegue de Clojars                      | clojars_deploy_token                   |
-| CloudBees CodeShip        | Credencial de Codeship de CloudBees                 | codeship_credential                      |
-| Databricks                | Token de Acceso de Databricks                       | databricks_access_token                |
-| Discord                   | Token de Bot de Discord                             | discord_bot_token                      |
-| Doppler                   | Token Personal de Doppler                           | doppler_personal_token                 |
-| Doppler                   | Token de Servicio de Doppler                        | doppler_service_token                  |
-| Doppler                   | Token de CLI de Doppler                             | doppler_cli_token                      |
-| Doppler                   | Token de SCIM de Doppler                            | doppler_scim_token                     |
-| Dropbox                   | Token de Acceso de Dropbox                          | dropbox_access_token                   |
-| Dropbox                   | Token de Acceso de Vida Corta de Dropbox            | dropbox_short_lived_access_token     |
-| Dynatrace                 | Token de Acceso de Dynatrace                        | dynatrace_access_token                 |
-| Dynatrace                 | Token Interno de Dynatrace                          | dynatrace_internal_token               |
-| Facebook                  | Token de Acceso a Facebook                          | facebook_access_token                  |
-| Finicity                  | Clave de App de Finicity                            | finicity_app_key                       |
-| Frame.io                  | Token Web de JSON de Frame.io                       | frameio_jwt                              |
-| Frame.io                  | Token de Desarrollador de Frame.io                  | frameio_developer_token                |
-| GitHub                    | Clave Privada de SSH de GitHub                      | github_ssh_private_key                 |
-| GitHub                    | Token de Acceso Personal de GitHub                  | github_personal_access_token           |
-| GitHub                    | Token de Acceso a la Instalación de GitHub App      | github_app_installation_access_token |
-| GoCardless                | Token de Acceso en Vivo a GoCardless                | gocardless_live_access_token           |
-| GoCardless                | Token de Acceso de GoCardless Sandbox               | gocardless_sandbox_access_token        |
-| Google Cloud              | Clave de API de Google                              | google_api_key                         |
-| Google Cloud              | ID de Clave Privada de Google Cloud                 | google_cloud_private_key_id          |
-| Grafana                   | Grafana API Key                                     | grafana_api_key                        |
-| Hashicorp Terraform       | Token de API de Terraform Cloud / Enterprise        | terraform_api_token                    |
-| Hubspot                   | Clave de API de Hubspot                             | hubspot_api_key                        |
-| Intercom                  | Intercom Access Token                               | intercom_access_token                  |
-| Lob                       | Lob Live API Key                                    | lob_live_api_key                       |
-| Lob                       | Lob Test API Key                                    | lob_test_api_key                       |
-| Mailchimp                 | Clave de API de Mailchimp                           | mailchimp_api_key                      |
-| Mailgun                   | Clave de API de Mailgun                             | mailgun_api_key                        |
-| npm                       | Token de Acceso de npm                              | npm_access_token                       |
-| NuGet                     | Clave de API de NuGet                               | nuget_api_key                          |
-| Palantir                  | Token Web de JSON de Palantir                       | palantir_jwt                             |
-| Postman                   | Clave de API de Postman                             | postman_api_key                        |
-| Proctorio                 | Clave de Consumidor de Proctorio                    | proctorio_consumer_key                 |
-| Proctorio                 | Clave de Enlace de Proctorio                        | proctorio_linkage_key                  |
-| Proctorio                 | Clave de Registro de Proctorio                      | proctorio_registration_key             |
-| Proctorio                 | Clave de Secreto de Proctorio                       | proctorio_secret_key                   |
-| Pulumi                    | Token de Acceso de Pulumi                           | pulumi_access_token                    |
-| PyPI                      | Token de la API de PyPI                             | pypi_api_token                         |
-| RubyGems                  | RubyGems API Key                                    | rubygems_api_key                       |
-| Samsara                   | Token de API de Samsara                             | samsara_api_token                      |
-| Samsara                   | Token de Acceso de OAuth de Samsara                 | samsara_oauth_access_token             |
-| SendGrid                  | Clave de la API de SendGrid                         | sendgrid_api_key                       |
-| Shopify                   | Secreto Compartid de la App de Shopify              | shopify_app_shared_secret              |
-| Shopify                   | Token de Acceso de Shopify                          | shopify_access_token                   |
-| Shopify                   | Token de Acceso de la App Personalizada de Shopify  | shopify_custom_app_access_token      |
-| Shopify                   | Contraseña de la App Privada de Shopify             | shopify_private_app_password           |
-| Slack                     | Token de la API de Slack                            | slack_api_token                        |
-| Slack                     | URL Entrante de Webhook de Slack                    | slack_incoming_webhook_url             |
-| Slack                     | URL de Flujo de Trabajo de Webhook de Slack         | slack_workflow_webhook_url             |
-| SSLMate                   | Clave de API de SSLMate                             | sslmate_api_key                        |
-| SSLMate                   | Secreto de Agrupamiento de SSLMate                  | sslmate_cluster_secret                 |
-| Stripe                    | Clave de API de Stripe                              | stripe_api_key                         |
-| Stripe                    | Clave de Secreto Stripe Live                        | stripe_live_secret_key                 |
-| Stripe                    | Clave Secreta de API de Pruebas de Stripe           | stripe_test_secret_key                 |
-| Stripe                    | Clave Restringida de API de Stripe Live             | stripe_live_restricted_key             |
-| Stripe                    | Clave Restringida de API de Pruebas de Stripe       | stripe_test_restricted_key             |
-| Tencent Cloud             | ID de Secreto de Tencent Cloud                      | tencent_cloud_secret_id                |
-| Twilio                    | Identificador de Secuencia de Cuenta de Twilio      | twilio_account_sid                     |
-| Twilio                    | Clave de API de Twilio                              | twilio_api_key                         |
+| Socio | Secreto compatible | Slug de la API |
+| ----- | ------------------ | -------------- |
+|       |                    |                |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index 8f0841d137..2c79e47097 100644
--- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| Socio                     | Secreto compatible                                                                   |
-| ------------------------- | ------------------------------------------------------------------------------------ |
-| Adafruit IO               | Clave de IO de Adafruit                                                              |
-| Alibaba Cloud             | Par de ID y Secreto de Clave de Acceso a la Nube de Alibaba                          |
-| Amazon Web Services (AWS) | Par de ID y Secreto de Clave de Acceso a AWS de Amazon                               |
-| Atlassian                 | Token de API de Atlassian                                                            |
-| Atlassian                 | Token Web de JSOn de Atlazzian                                                       |
-| Azure                     | Token de Acceso Personal para Azure DevOps | azure_devops_personal_access_token  |
-| Azure                     | Token de Azure SAS | azure_sas_token                                               |
-| Azure                     | Certificado de Administración de Servicios de Azure | azure_management_certificate |
-| Azure                     | Secuencia de Conexión de SQL de Azure | azure_sql_connection_string                |
-| Azure                     | Clave de Cuenta de Almacenamiento de Azure | azure_storage_account_key             |
-| Clojars                   | Token de Despliegue de Clojars                                                       |
-| CloudBees CodeShip        | Credencial de Codeship de CloudBees                                                  |
-| Databricks                | Token de Acceso de Databricks                                                        |
-| Datadog                   | Clave de API de Datadog                                                              |
-| Discord                   | Token de Bot de Discord                                                              |
-| Doppler                   | Token Personal de Doppler                                                            |
-| Doppler                   | Token de Servicio de Doppler                                                         |
-| Doppler                   | Token de CLI de Doppler                                                              |
-| Doppler                   | Token de SCIM de Doppler                                                             |
-| Dropbox                   | Token de Acceso de Dropbox                                                           |
-| Dropbox                   | Token de Acceso de Vida Corta de Dropbox                                             |
-| Dynatrace                 | Token de Acceso de Dynatrace                                                         |
-| Dynatrace                 | Token Interno de Dynatrace                                                           |
-| Finicity                  | Clave de App de Finicity                                                             |
-| Frame.io                  | Token Web de JSON de Frame.io                                                        |
-| Frame.io                  | Token de Desarrollador de Frame.io                                                   |
-| GitHub                    | Clave Privada de SSH de GitHub                                                       |
-| GitHub                    | Token de Acceso Personal de GitHub                                                   |
-| GitHub                    | Token de Acceso a la Instalación de GitHub App                                       |
-| GoCardless                | Token de Acceso en Vivo a GoCardless                                                 |
-| GoCardless                | Token de Acceso de GoCardless Sandbox                                                |
-| Google Cloud              | Clave de API de Google                                                               |
-| Google Cloud              | ID de Clave Privada de Google Cloud                                                  |
-| Hashicorp Terraform       | Token de API de Terraform Cloud / Enterprise                                         |
-| Hubspot                   | Clave de API de Hubspot                                                              |
-| Mailchimp                 | Clave de API de Mailchimp                                                            |
-| Mailchimp                 | Clave de API de Mandrill                                                             |
-| Mailgun                   | Clave de API de Mailgun                                                              |
-| MessageBird               | Clave de API de MessageBird                                                          |
-| npm                       | Token de Acceso de npm                                                               |
-| NuGet                     | Clave de API de NuGet                                                                |
-| Palantir                  | Token Web de JSON de Palantir                                                        |
-| Plivo                     | Token de Plivo Auth                                                                  |
-| Postman                   | Clave de API de Postman                                                              |
-| Proctorio                 | Clave de Consumidor de Proctorio                                                     |
-| Proctorio                 | Clave de Enlace de Proctorio                                                         |
-| Proctorio                 | Clave de Registro de Proctorio                                                       |
-| Proctorio                 | Clave de Secreto de Proctorio                                                        |
-| Pulumi                    | Token de Acceso de Pulumi                                                            |
-| PyPI                      | Token de la API de PyPI                                                              |
-| RubyGems                  | RubyGems API Key                                                                     |
-| Samsara                   | Token de API de Samsara                                                              |
-| Samsara                   | Token de Acceso de OAuth de Samsara                                                  |
-| Shopify                   | Secreto Compartid de la App de Shopify                                               |
-| Shopify                   | Token de Acceso de Shopify                                                           |
-| Shopify                   | Token de Acceso de la App Personalizada de Shopify                                   |
-| Shopify                   | Contraseña de la App Privada de Shopify                                              |
-| Slack                     | Token de la API de Slack                                                             |
-| Slack                     | URL Entrante de Webhook de Slack                                                     |
-| Slack                     | URL de Flujo de Trabajo de Webhook de Slack                                          |
-| SSLMate                   | Clave de API de SSLMate                                                              |
-| SSLMate                   | Secreto de Agrupamiento de SSLMate                                                   |
-| Stripe                    | Clave de Secreto Stripe Live                                                         |
-| Stripe                    | Clave Secreta de API de Pruebas de Stripe                                            |
-| Stripe                    | Clave Restringida de API de Stripe Live                                              |
-| Stripe                    | Clave Restringida de API de Pruebas de Stripe                                        |
-| Tencent Cloud             | ID de Secreto de Tencent Cloud                                                       |
-| Twilio                    | Identificador de Secuencia de Cuenta de Twilio                                       |
-| Twilio                    | Clave de API de Twilio                                                               |
+| Socio                     | Secreto compatible                                          |
+| ------------------------- | ----------------------------------------------------------- |
+| Adafruit IO               | Clave de IO de Adafruit                                     |
+| Adobe                     | Token de Dispositivo de Adobe                               |
+| Adobe                     | Token de Servicio de Adobe                                  |
+| Adobe                     | Token de Acceso de Vida Corta de Adobe                      |
+| Adobe                     | Token Web de JSON de Adobe                                  |
+| Alibaba Cloud             | Par de ID y Secreto de Clave de Acceso a la Nube de Alibaba |
+| Amazon Web Services (AWS) | Par de ID y Secreto de Clave de Acceso a AWS de Amazon      |
+| Atlassian                 | Token de API de Atlassian                                   |
+| Atlassian                 | Token Web de JSOn de Atlazzian                              |
+| Azure                     | Token de Acceso Personal de Azure DevOps                    |
+| Azure                     | Token de Azure SAS                                          |
+| Azure                     | Certificado de Administración de Servicios de Azure         |
+| Azure                     | Secuencia de Conexión de Azure SQL                          |
+| Azure                     | Clave de Cuenta de Almacenamiento de Azure                  |
+| Clojars                   | Token de Despliegue de Clojars                              |
+| CloudBees CodeShip        | Credencial de Codeship de CloudBees                         |
+| Databricks                | Token de Acceso de Databricks                               |
+| Datadog                   | Clave de API de Datadog                                     |
+| Discord                   | Token de Bot de Discord                                     |
+| Doppler                   | Token Personal de Doppler                                   |
+| Doppler                   | Token de Servicio de Doppler                                |
+| Doppler                   | Token de CLI de Doppler                                     |
+| Doppler                   | Token de SCIM de Doppler                                    |
+| Dropbox                   | Token de Acceso de Dropbox                                  |
+| Dropbox                   | Token de Acceso de Vida Corta de Dropbox                    |
+| Dynatrace                 | Token de Acceso de Dynatrace                                |
+| Dynatrace                 | Token Interno de Dynatrace                                  |
+| Finicity                  | Clave de App de Finicity                                    |
+| Frame.io                  | Token Web de JSON de Frame.io                               |
+| Frame.io                  | Token de Desarrollador de Frame.io                          |
+| GitHub                    | Token de Acceso Personal de GitHub                          |
+| GitHub                    | Token de Acceso de OAuth para GitHub                        |
+| GitHub                    | Token de Actualización de GitHub                            |
+| GitHub                    | Token de Acceso a la Instalación de GitHub App              |
+| GitHub                    | Clave Privada de SSH de GitHub                              |
+| GoCardless                | Token de Acceso en Vivo a GoCardless                        |
+| GoCardless                | Token de Acceso de GoCardless Sandbox                       |
+| Google Cloud              | Clave de API de Google                                      |
+| Google Cloud              | ID de Clave Privada de Google Cloud                         |
+| Hashicorp Terraform       | Token de API de Terraform Cloud / Enterprise                |
+| Hubspot                   | Clave de API de Hubspot                                     |
+| Mailchimp                 | Clave de API de Mailchimp                                   |
+| Mailchimp                 | Clave de API de Mandrill                                    |
+| Mailgun                   | Clave de API de Mailgun                                     |
+| MessageBird               | Clave de API de MessageBird                                 |
+| npm                       | Token de Acceso de npm                                      |
+| NuGet                     | Clave de API de NuGet                                       |
+| OpenAI                    | Clave de la API de OpenAI                                   |
+| Palantir                  | Token Web de JSON de Palantir                               |
+| Plivo                     | Token de Plivo Auth                                         |
+| Postman                   | Clave de API de Postman                                     |
+| Proctorio                 | Clave de Consumidor de Proctorio                            |
+| Proctorio                 | Clave de Enlace de Proctorio                                |
+| Proctorio                 | Clave de Registro de Proctorio                              |
+| Proctorio                 | Clave de Secreto de Proctorio                               |
+| Pulumi                    | Token de Acceso de Pulumi                                   |
+| PyPI                      | Token de la API de PyPI                                     |
+| RubyGems                  | Clave de la API de RubyGems                                 |
+| Samsara                   | Token de API de Samsara                                     |
+| Samsara                   | Token de Acceso de OAuth de Samsara                         |
+| SendGrid                  | Clave de la API de SendGrid                                 |
+| Shopify                   | Secreto Compartid de la App de Shopify                      |
+| Shopify                   | Token de Acceso de Shopify                                  |
+| Shopify                   | Token de Acceso de la App Personalizada de Shopify          |
+| Shopify                   | Contraseña de la App Privada de Shopify                     |
+| Slack                     | Token de la API de Slack                                    |
+| Slack                     | URL Entrante de Webhook de Slack                            |
+| Slack                     | URL de Flujo de Trabajo de Webhook de Slack                 |
+| SSLMate                   | Clave de API de SSLMate                                     |
+| SSLMate                   | Secreto de Agrupamiento de SSLMate                          |
+| Stripe                    | Clave de Secreto Stripe Live                                |
+| Stripe                    | Clave Secreta de API de Pruebas de Stripe                   |
+| Stripe                    | Clave Restringida de API de Stripe Live                     |
+| Stripe                    | Clave Restringida de API de Pruebas de Stripe               |
+| Tencent Cloud             | ID de Secreto de Tencent Cloud                              |
+| Twilio                    | Identificador de Secuencia de Cuenta de Twilio              |
+| Twilio                    | Clave de API de Twilio                                      |
diff --git a/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..17b9acc604
--- /dev/null
+++ b/translations/es-ES/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,5 @@
+{% if currentVersion == "free-pro-team@latest" %}
+Para obtener más información, consulta las secciones "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" y "[Acerca de {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)".
+{% else %}
+Para obtener más información sobre los datos de asesoria, consulta la sección "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}</a>".
+{% endif %}
diff --git a/translations/es-ES/data/reusables/security-center/beta.md b/translations/es-ES/data/reusables/security-center/beta.md
index e0074292ba..7ccde5054f 100644
--- a/translations/es-ES/data/reusables/security-center/beta.md
+++ b/translations/es-ES/data/reusables/security-center/beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** The security overview is currently in beta and subject to change.
+**Nota:** El resumen de seguridad se encuentra actualmente en beta y está sujeto a cambios.
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/security/displayed-information.md b/translations/es-ES/data/reusables/security/displayed-information.md
index b410cfb96f..c1119eed25 100644
--- a/translations/es-ES/data/reusables/security/displayed-information.md
+++ b/translations/es-ES/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
 Cuando habilitas una o más características de seguridad y análisis para los repositorios existentes, verás cualquier resultado que se muestra en {% data variables.product.prodname_dotcom %} al cabo de unos pocos minutos:
 
 - Todos los repositorios existentes tendrán la configuración seleccionada.
-- Los repositorios nuevos seguirán la configuración seleccionada si habilitaste la casilla de verificación para los repositorios nuevos.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+- Los repositorios nuevos seguirán la configuración seleccionada si habilitaste la casilla de verificación para los repositorios nuevos.{% if currentVersion == "free-pro-team@latest" %}
 - Utilizamos los permisos para escanear en busca de archivos de manifiesto para aplicar los servicios relevantes.
 - Verás información en tu gráfica de dependencias.
-- {% data variables.product.prodname_dotcom %} generará {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} y levantará solicitudes de cambio{% endif %}. 
+- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} and create pull requests{% endif %}. 
diff --git a/translations/es-ES/data/reusables/sponsors/choose-updates.md b/translations/es-ES/data/reusables/sponsors/choose-updates.md
index 18048b6321..7a897bd0f1 100644
--- a/translations/es-ES/data/reusables/sponsors/choose-updates.md
+++ b/translations/es-ES/data/reusables/sponsors/choose-updates.md
@@ -1 +1 @@
-4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Casilla de verificación para recibir actualizaciones de la cuenta patrocinada](/assets/images/help/sponsors/updates-checkbox-manage.png)
+4. Decide si quieres recibir actualizaciones de la cuenta patrocinada por correo electrónico y luego selecciona o deselecciona "Recibir actualizaciones de _CUENTA_ por correo electrónico". ![Casilla de verificación para recibir actualizaciones de la cuenta patrocinada](/assets/images/help/sponsors/updates-checkbox-manage.png)
diff --git a/translations/es-ES/data/reusables/sponsors/click-add-tier.md b/translations/es-ES/data/reusables/sponsors/click-add-tier.md
index 3f13de06bc..d504a5f62d 100644
--- a/translations/es-ES/data/reusables/sponsors/click-add-tier.md
+++ b/translations/es-ES/data/reusables/sponsors/click-add-tier.md
@@ -1 +1 @@
-1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![Botón de agregar nivel](/assets/images/help/sponsors/add-a-tier-button.png)
+1. Para crear un nivel mensual, haz clic en **Agregar un nivel mensual** a la derecha de la página. Como alternativa, para crear un nivel para pagos de una sola ocasión, haz clic en **Niveles de una sola ocasión** y luego en **Agregar un nivel de una sola ocasión**. ![Botón de agregar nivel](/assets/images/help/sponsors/add-a-tier-button.png)
diff --git a/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md b/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md
index 1889367cb9..673a66daf0 100644
--- a/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md
+++ b/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md
@@ -1,2 +1,2 @@
-1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png)
-1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png)
+1. Cuando tienes por lo menos un nivel, verás una opción para habilitar las cantidades personalizadas sobre los niveles mensuales y de una sola ocasión. Si quieres permitir que los patrocinadores configuren su cantidad de pago, entonces selecciona **Habilitar cantidades personalizadas**. ![Habilitar las cantidades personalizadas](/assets/images/help/sponsors/enable-custom-amounts.png)
+1. Opcionalmente, si habilitas las cantidades personalizadas, puedes configurar una cantidad predeterminada para que se muestre en los niveles personalizados. Especifica una cantidad redonda en dólares y haz clic en **Configurar monto predeterminado**. ![Configurar una cantidad predeterminada](/assets/images/help/sponsors/set-default-amount.png)
diff --git a/translations/es-ES/data/reusables/sponsors/feedback.md b/translations/es-ES/data/reusables/sponsors/feedback.md
index f3fccb232d..785bef3aed 100644
--- a/translations/es-ES/data/reusables/sponsors/feedback.md
+++ b/translations/es-ES/data/reusables/sponsors/feedback.md
@@ -1 +1 @@
-Puedes compartir tu retroalimentación sobre los {% data variables.product.prodname_sponsors %} con {% data variables.product.company_short %}. To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)."
+Puedes compartir tu retroalimentación sobre los {% data variables.product.prodname_sponsors %} con {% data variables.product.company_short %}. Para unirte a la conversación, consulta la sección "[Retroalimentación de patrocinadores](https://github.com/github/feedback/discussions/categories/sponsors-feedback)".
diff --git a/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md b/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md
index 1d03b474df..ae185870fe 100644
--- a/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md
+++ b/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md
@@ -1 +1 @@
-1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Enlace para pagar una cantidad prorrateada](/assets/images/help/sponsors/pay-prorated-amount-link.png)
\ No newline at end of file
+1. Opcionalmente, si estás patrocinando a alguien como organización, para pagar una cantidad prorrateada en vez de hacer el pago mensual completo, debajo de "Total adeudado", haz clic en **Mejor pagar $X.XX prorrateados**. ![Enlace para pagar una cantidad prorrateada](/assets/images/help/sponsors/pay-prorated-amount-link.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md b/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md
index a21ee5edfc..1474ddadbc 100644
--- a/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md
+++ b/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md
@@ -1 +1 @@
-If you're starting a monthly sponsorship on behalf of your user account, you'll immediately be charged a prorated amount for the time until your next regular billing date. Si estás patrocinando a alguien en nombre de una organización, puedes elegir pagar la cantidad prorrateada o hacer un pago completo mensual.
+Si comienzas un patrocinio mensual en nombre de tu cuenta de usuario, inmediatamente se te cobrará una cantidad prorrateada por el tiempo hasta que llegue tu siguiente fecha de facturación habitual. Si estás patrocinando a alguien en nombre de una organización, puedes elegir pagar la cantidad prorrateada o hacer un pago completo mensual.
diff --git a/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md
index a84fd2930a..6f7802d168 100644
--- a/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md
+++ b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md
@@ -1 +1 @@
-1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png)
+1. Revisa tu nivel y luego haz clic en **Publicar _TIPO_ de nivel**. ![Botón de publicar nivel mensual](/assets/images/help/sponsors/publish-tier-button.png)
diff --git a/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md b/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md
index 12da8b2767..1893e6c846 100644
--- a/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md
+++ b/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md
@@ -1 +1 @@
-1. En el lado derecho de la página, debajo de "Selecciona un nivel", revisa los niveles de patrocinio disponibles. If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png)
+1. En el lado derecho de la página, debajo de "Selecciona un nivel", revisa los niveles de patrocinio disponibles. Si hay más de un tipo de nivel disponible, se mostrarán los niveles "Mensuales", haz clic en **Una sola ocasión** para mostrar los niveles de los pagos de una sola ocasión. ![Muestra los niveles de "Una sola vez"](/assets/images/help/sponsors/show-one-time-tiers.png)
diff --git a/translations/es-ES/data/reusables/sponsors/select-a-tier.md b/translations/es-ES/data/reusables/sponsors/select-a-tier.md
index ca2905c799..b4ba436c82 100644
--- a/translations/es-ES/data/reusables/sponsors/select-a-tier.md
+++ b/translations/es-ES/data/reusables/sponsors/select-a-tier.md
@@ -1 +1 @@
-1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![Caja de selección de nivel](/assets/images/help/sponsors/select-a-tier-box.png)
+1. A la derecha dekl nivel que quieres, haz clic en **Seleccionar**. Si quieres seleccionar una cantidad personalizada, ingresa la cantidad de patrocinio antes de hacer clic en "Seleccionar". ![Caja de selección de nivel](/assets/images/help/sponsors/select-a-tier-box.png)
diff --git a/translations/es-ES/data/reusables/sponsors/sponsorship-details.md b/translations/es-ES/data/reusables/sponsors/sponsorship-details.md
index 54ae4f2bd8..52e2ca0e14 100644
--- a/translations/es-ES/data/reusables/sponsors/sponsorship-details.md
+++ b/translations/es-ES/data/reusables/sponsors/sponsorship-details.md
@@ -1 +1 @@
-Puedes patrocinar a cualquiera que tenga un perfil de desarrollador patrocinado o de organización patrocinada en nombre de tu cuenta de usuario o de una organización. You can choose from multiple sponsorship tiers, with one-time or monthly payment amounts and benefits that are set by the sponsored account. Tu patrocinio compartirá la fecha de facturación de tu cuenta, así como el método de pago y recibos.
+Puedes patrocinar a cualquiera que tenga un perfil de desarrollador patrocinado o de organización patrocinada en nombre de tu cuenta de usuario o de una organización. Puedes elegir entre varios niveles de patrocinio, con cantidades de pago mensuales o de una sola ocasión y beneficios que configura la cuenta patrocinada. Tu patrocinio compartirá la fecha de facturación de tu cuenta, así como el método de pago y recibos.
diff --git a/translations/es-ES/data/reusables/sponsors/tier-details.md b/translations/es-ES/data/reusables/sponsors/tier-details.md
index 5ce3b0deee..f2f09469cd 100644
--- a/translations/es-ES/data/reusables/sponsors/tier-details.md
+++ b/translations/es-ES/data/reusables/sponsors/tier-details.md
@@ -1,3 +1,3 @@
-Puedes crear hasta diez niveles de patrocinio que podrán escoger los patrocinadores. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time).
+Puedes crear hasta diez niveles de patrocinio que podrán escoger los patrocinadores. Cada nivel tiene sus propias cantidades de pago mensual o de una sola ocasión en dólares estadounidenses y beneficios, tales como recibir el acceso tempran a versiones nuevas o que se te mencione en el README del proyecto. Adicionalmente, puedes elegir habilitar los niveles para las cantidades personalizadas (mensuales y de única ocasión).
 
-Una vez que hayas publicado un nivel, no podrás editar el precio de este. En vez de eso, deberás retirar el nivel y crear uno nuevo. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires.
+Una vez que hayas publicado un nivel, no podrás editar el precio de este. En vez de eso, deberás retirar el nivel y crear uno nuevo. Los patrocinadores existentes seguirán en el nivel que se retiró hasta que cambian su nivel de patrocinio, cancelen su patrocinio, o venza su periodo de patrocinio de una sola ocasión.
diff --git a/translations/es-ES/data/reusables/supported-languages/C.md b/translations/es-ES/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/Cpp.md b/translations/es-ES/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/Cs.md b/translations/es-ES/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/go.md b/translations/es-ES/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..40bd61946e
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/java.md b/translations/es-ES/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/javascript.md b/translations/es-ES/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/php.md b/translations/es-ES/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/products-table-header.md b/translations/es-ES/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..743339ee69
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/python.md b/translations/es-ES/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/ruby.md b/translations/es-ES/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/scala.md b/translations/es-ES/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/supported-languages/typescript.md b/translations/es-ES/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/es-ES/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/user_settings/billing_plans.md b/translations/es-ES/data/reusables/user_settings/billing_plans.md
index 8d26ab1479..471f9e8da1 100644
--- a/translations/es-ES/data/reusables/user_settings/billing_plans.md
+++ b/translations/es-ES/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. En la barra lateral de configuración de usuario, haz clic en **Facturación & planes**. ![Configuración de facturación & planes](/assets/images/help/settings/settings-sidebar-billing-plans.png)
diff --git a/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md
index 522e297d61..4e0681237b 100644
--- a/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/es-ES/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. Para mantener tu dirección de correo electrónico como privada cuando realices operaciones de Git basadas en la web, da clic en **Mantener mi dirección de correo electrónico como privada**. ![Imagen de casilla para mantener tu dirección de correo electrónico como privada](/assets/images/help/settings/email_privacy.png)
+5. To keep your email address private when performing web-based Git operations, click **Keep my email addresses private**. ![Imagen de casilla para mantener tu dirección de correo electrónico como privada](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/es-ES/data/reusables/user_settings/payment-info-link.md b/translations/es-ES/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..8d441f3be4
--- /dev/null
+++ b/translations/es-ES/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. At the top of the page, click **Payment information**. ![Payment information link](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md
index 9441931186..1e3bdf23c5 100644
--- a/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,6 +1,6 @@
-| Clave        | Type        | Descripción                                                                                                                                                                               |
-| ------------ | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Acción`     | `secuencia` | La acción que se realizó. Este puede ser uno de entre `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, o `reopened`.                                       |
-| `alerta`     | `objeto`    | La alerta de escaneo de código involucrada en el evento.                                                                                                                                  |
-| `ref`        | `secuencia` | La referencia de Git de la alerta de escaneo de código. Cuando la acción es `reopened_by_user` o `closed_by_user`, el `sender` es quien activó el evento y este valor estará vacío.       |
-| `commit_oid` | `secuencia` | El SHA de la confirmación de la alerta del escaneo de código. Cuando la acción es `reopened_by_user` o `closed_by_user`, el `sender` es quien activó el evento y este valor estará vacío. |
+| Clave        | Type        | Descripción                                                                                                                                                                                               |
+| ------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`     | `secuencia` | La acción que se realizó. Este puede ser uno de entre `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, o `reopened`.                                                       |
+| `alerta`     | `objeto`    | La alerta de escaneo de código involucrada en el evento.                                                                                                                                                  |
+| `ref`        | `secuencia` | La referencia de Git de la alerta de escaneo de código. Cuando la acción se muestra como `reopened_by_user` o `closed_by_user`, el evento se activó mediante el `sender` y este valor estará vacío.       |
+| `commit_oid` | `secuencia` | El SHA de la confirmación de la alerta del escaneo de código. Cuando la acción se muestra como `reopened_by_user` o `closed_by_user`, el evento se activó mediante el `sender` y este valor estará vacío. |
diff --git a/translations/es-ES/data/reusables/webhooks/create_properties.md b/translations/es-ES/data/reusables/webhooks/create_properties.md
index 124c847d6a..e7bedc701f 100644
--- a/translations/es-ES/data/reusables/webhooks/create_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| Clave           | Type        | Descripción                                                                                                                                                                                                                                    |
-| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference).                                                                                                                                                                             |
-| `ref_type`      | `secuencia` | El tipo de objeto de Git ref que se creó en el repositorio. Puede ser `branch` o `tag`.                                                                                                                                                        |
-| `master_branch` | `secuencia` | El nombre de la rama predeterminada del repositorio (a menudo {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
-| `descripción`   | `secuencia` | La descripción actual del repositorio.                                                                                                                                                                                                         |
+| Clave           | Type        | Descripción                                                                                                                                                                                                                                   |
+| --------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ref`           | `secuencia` | El recurso de la [`git ref`](/rest/reference/git#get-a-reference).                                                                                                                                                                            |
+| `ref_type`      | `secuencia` | El tipo de objeto de Git ref que se creó en el repositorio. Puede ser `branch` o `tag`.                                                                                                                                                       |
+| `master_branch` | `secuencia` | El nombre de la rama predeterminada del repositorio (a menudo {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
+| `descripción`   | `secuencia` | La descripción actual del repositorio.                                                                                                                                                                                                        |
diff --git a/translations/es-ES/data/reusables/webhooks/discussion_desc.md b/translations/es-ES/data/reusables/webhooks/discussion_desc.md
index 1b221660e0..c9aee7e232 100644
--- a/translations/es-ES/data/reusables/webhooks/discussion_desc.md
+++ b/translations/es-ES/data/reusables/webhooks/discussion_desc.md
@@ -1 +1 @@
-`discussion` | `object` | The [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion) resource.
\ No newline at end of file
+`discussion` | `object` | El recurso [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion).
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/webhooks/discussions-webhooks-beta.md b/translations/es-ES/data/reusables/webhooks/discussions-webhooks-beta.md
index 2033ca20ea..a834cff356 100644
--- a/translations/es-ES/data/reusables/webhooks/discussions-webhooks-beta.md
+++ b/translations/es-ES/data/reusables/webhooks/discussions-webhooks-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Webhook events for {% data variables.product.prodname_discussions %} are currently in beta and subject to change.
+**Nota:** Los eventos de webhook para los {% data variables.product.prodname_discussions %} se encuentran actualmente en beta y están sujetos a cambios.
 
 {% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
index 1901ba33e8..a9409ac9be 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| Clave    | Type        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, o `reopened`. Si la acción se muestra como `closed` y la llave `merged` es `false`, esto significa que la solicitud de extracción se cerró con las confirmaciones sin fusionar. Si la acción se muestra como `closed` y la llave `merged` es `true`, la solicitud de extracción se fusionó. |
+| Clave    | Type        | Descripción                                                                         |
+| -------- | ----------- | ----------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's tracking branch is synchronized with the source branch for the pull request, which happens when the source branch is updated.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md b/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md
index 85ba1b3eaf..d5d0cc6b13 100644
--- a/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/es-ES/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-La actividad relacionada con un listado de patrocinio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta "[Acerca de los Patrocinadores de GitHub](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)".
+La actividad relacionada con un listado de patrocinio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta "[Acerca de los Patrocinadores de GitHub](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index 92134e06d3..d38ecd4bf7 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -20,7 +20,7 @@ homepage:
   version_picker: Versión
 toc:
   getting_started: Empezar
-  popular_articles: Popular
+  popular: Popular
   guides: Guías
   whats_new: Qué hay de nuevo
 pages:
@@ -54,14 +54,6 @@ contribution_cta:
   button: Haz una contribución
   or: O,
   to_guidelines: aprende cómo contribuir.
-enterprise_releases_list:
-  title: Lanzamientos de Enterprise Server
-  currently_supported: Actualmente compatibles
-  currently_supported_message: Consulta la sección de <a href="https://github.com/enterprise">GitHub Enterprise</a> para obtener más información sobre el último lanzamiento.
-  deprecated: Obsoletizado
-  deprecated_message: 'Estos documentos siguen estando disponibles, pero ya no se mantienen:'
-  deprecated_developer: Obsoletizado en developer.github.com
-  deprecated_developer_message: 'Estos documentos siguen estando disponibles en el <a href="https://developer.github.com">sitio de desarrollador</a> tradicional pero ya no se mantienen:'
 products:
   graphql:
     reference:
@@ -127,19 +119,36 @@ footer:
       press: Prensa
       shop: Tienda
 product_landing:
-  quick_start: Inicio Rápido
-  reference_guides: Guías de referencia
+  quickstart: Inicio Rápido
+  reference: Referencia
   overview: Resumen
+  guides: Guías
+  code_examples: Ejemplos de código
+  search_code_examples: Ejemplos de búsqueda de código
+  show_more: Mostrar más
+  explore_people_and_projects: Explorar personas y proyectos
+  sorry: Lo sentimos, no hay respultados para
+  no_example: Parece que no tenemos un ejemplo que se ajuste a tu filtro.
+  try_another: Inténtalo con otro archivo o agrega tu ejemplo de código.
+  no_result: Lo sentimos, no hay una guía que coincida con tu filtro.
+  learn: Aprende cómo agregar un ejemplo de código
+  communities_using_discussions: Comunidades que utilizan debates
+  add_your_community: Agrega tu comunidad
+  sponsor_community: Comunidad de GitHub Sponsors
+  supported_releases: Supported releases
+  release_notes_for: Release notes for
+  upgrade_from: Upgrade from
+  browse_all_docs: Browse all docs
+  explore_release_notes: Explore release notes
 product_sublanding:
   start: Inicio
   start_path: Ruta de inicio
-  learning_paths: '{{ allProducts[currentProduct].name }} learning paths'
+  learning_paths: 'Rutas de aprendizaje de {{ productMap[currentProduct].name }}'
   learning_paths_desc: Las rutas de aprendizaje son una recopilación de guías que te ayudan a dominar un tema en particular.
-  guides: '{{ allProducts[currentProduct].name }} guides'
+  guides: 'Guías de {{ productMap[currentProduct].name }}'
   more_guides: más guías
   load_more: Carga más guías
-  all_guides: 'All {{ allProducts[currentProduct].name }} guides'
-  no_result: Lo sentimos, no hay una guía que coincida con tu filtro.
+  all_guides: 'Todas las guías de {{ productMap[currentProduct].name }}'
   filters:
     type: Type
     topic: Tema
@@ -154,3 +163,10 @@ learning_track_nav:
   prevGuide: Guía previa
   nextGuide: Guía siguiente
 contributor_callout: En este artículo contribuye y lo mantiene
+toggle_images:
+  off: Images are off, click to show
+  on: Images are on, click to hide
+  hide_single: Hide image
+  show_single: Show image
+scroll_button:
+  scroll_to_top: Scroll to top
diff --git a/translations/es-ES/data/variables/codespaces_code_examples.yml b/translations/es-ES/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..00958245ab
--- /dev/null
+++ b/translations/es-ES/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.js sample project
+  description: Try a Node.js project with a custom dev container
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - development containers
+- 
+  title: Python sample project
+  description: Try a Python project with a custom dev container
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - development containers
+- 
+  title: Java sample project
+  description: Try a Java project with a custom dev container
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - development containers
+- 
+  title: Go sample project
+  description: Try a Go project with a custom dev container
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - development containers
+- 
+  title: Rust sample project
+  description: Try a Rust project with a custom dev container
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - development containers
+- 
+  title: PHP sample project
+  description: Try a PHP project with a custom dev container
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - development containers
diff --git a/translations/es-ES/data/variables/migrations.yml b/translations/es-ES/data/variables/migrations.yml
index fd3edd8f1d..586a1196b7 100644
--- a/translations/es-ES/data/variables/migrations.yml
+++ b/translations/es-ES/data/variables/migrations.yml
@@ -4,4 +4,4 @@ user_migrations_intro: >-
 organization_migrations_intro: >-
   La API de migraciones de organización te permite migrar un repositorio de GitHub a {% data variables.product.prodname_ghe_server %}.
 source_imports_intro: >-
-  La API de Importaciones de Código Fuente te permite comenzar una importación desde un repositorio de origen en Git, Subversion, Mercurial o Team Foundation Server. Esta es la misma funcionalidad que tiene el importador de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Importar un repositorio con el importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)".
+  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Version Control source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml
index e87037d3a1..9e5ecf96c1 100644
--- a/translations/es-ES/data/variables/product.yml
+++ b/translations/es-ES/data/variables/product.yml
@@ -56,6 +56,7 @@ prodname_pages: 'Páginas de GitHub'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'GitHub App'
@@ -77,8 +78,7 @@ prodname_debug: 'Depuración de GitHub'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'Registro del paquete de GitHub'
-prodname_github_container_registry: 'Registro de Contenedores de GitHub'
-prodname_container_registry: 'registro de contenedores'
+prodname_container_registry: 'Container registry'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -88,10 +88,9 @@ prodname_matching_fund: 'Fondo Compensatorio para Patrocinios de GitHub'
 prodname_GH_advanced_security: 'GitHub Advanced Security'
 prodname_advanced_security: 'Advanced Security'
 #Security Center
-prodname_security_center: 'Security Center'
+prodname_security_center: 'Centro de seguridad'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Codespaces de Visual Studio'
 prodname_github_codespaces: 'Acerca de GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'Soporte de la Comunidad de GitHub'
diff --git a/translations/es-ES/data/variables/release_candidate.yml b/translations/es-ES/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/es-ES/data/variables/release_candidate.yml
+++ b/translations/es-ES/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/es-ES/data/variables/sponsors_user_examples.yml b/translations/es-ES/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..b6de02efd1
--- /dev/null
+++ b/translations/es-ES/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chayn ayuda a que las mujeres que han sufrido abusos encuentren la información correcta y el apoyo que necesitan para tomar el control de sus vidas.
+- 
+  user: foosel
+  description: '👋 Soy Gina, y se me conoce principalmente por ser la creadora y desarrolladora principal de OctoPrint 🐙.'
+- 
+  user: dayhaysoos
+  description: '¿Qué tal? soy Nick. Soy un ingeniero que recién encotró su pasión por eliminar la fricción de la experiencia de desarrollar comercio electrónico.'
+- 
+  user: yyx990803
+  description: Estoy trabajando de tiempo completo en Vue.js, un marco de trabajo de frontend de JavaScript para crear aplicaciones web, y en Vite, una herramienta moderna de creación web.
+- 
+  user: calebporzio
+  description: '🚶‍♂️Dejé mi trabajo diurno en enero de 2019 para dedicarme al código abierto. Desde entonces, creé Laravel Livewire, AlpineJS y muchas otras cosas.'
+- 
+  user: kjaymiller
+  description: '¡Hola a todos, soy Jay! 👋 Soy un veterano del cuerpo de marinos que se hizo desarrollador y que ha estado desarrollando código activamente desde el 2014. También estoy involucrado en el espacio de productividad en donde pueden encontrarme ayudando a las personas con automatizaciones para algunas de sus apps y herramientas favoritas.'
diff --git a/translations/es-XL/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/es-XL/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index c098af284d..fcc6e5ca2a 100644
--- a/translations/es-XL/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/es-XL/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### Acerca de la autenticación integrada para usuarios fuera de tu proveedor de identidad
diff --git a/translations/es-XL/content/admin/authentication/changing-authentication-methods.md b/translations/es-XL/content/admin/authentication/changing-authentication-methods.md
index f6f1ec7b81..3eb247032e 100644
--- a/translations/es-XL/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/es-XL/content/admin/authentication/changing-authentication-methods.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Cuando modificas el método de autenticación, las cuentas de usuario en {% data variables.product.product_location_enterprise %} se conservan y los usuarios seguirán iniciando sesión en la misma cuenta siempre que su nombre de usuario no cambie.
diff --git a/translations/es-XL/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/es-XL/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index 1dc4449261..4f896e180d 100644
--- a/translations/es-XL/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/es-XL/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -8,6 +8,8 @@ intro: 'Si usas la autenticación integrada, puedes impedir que las personas no
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/authentication/using-built-in-authentication.md b/translations/es-XL/content/admin/authentication/using-built-in-authentication.md
index 1985971331..fabbe6317c 100644
--- a/translations/es-XL/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/es-XL/content/admin/authentication/using-built-in-authentication.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Puedes crear mensajes personalizados que los usuarios verán en las páginas de inicio de sesión y de cierre de sesión. Para obtener más información, consulta "[Personalizar mensajes de usuario en tu instancia](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)."
diff --git a/translations/es-XL/content/admin/authentication/using-cas.md b/translations/es-XL/content/admin/authentication/using-cas.md
index 8d4c9b39f8..26995c7420 100644
--- a/translations/es-XL/content/admin/authentication/using-cas.md
+++ b/translations/es-XL/content/admin/authentication/using-cas.md
@@ -9,7 +9,11 @@ intro: 'CAS es un protocolo de inicio de sesión único (SSO) para varias aplica
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/es-XL/content/admin/authentication/using-ldap.md b/translations/es-XL/content/admin/authentication/using-ldap.md
index b171cff607..48edd53186 100644
--- a/translations/es-XL/content/admin/authentication/using-ldap.md
+++ b/translations/es-XL/content/admin/authentication/using-ldap.md
@@ -12,7 +12,10 @@ intro: 'LDAP te permite autenticar el {% data variables.product.prodname_ghe_ser
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/es-XL/content/admin/authentication/using-saml.md b/translations/es-XL/content/admin/authentication/using-saml.md
index da907821a3..b6f5011b14 100644
--- a/translations/es-XL/content/admin/authentication/using-saml.md
+++ b/translations/es-XL/content/admin/authentication/using-saml.md
@@ -9,7 +9,11 @@ intro: 'SAML es un estándar basado en XML para autenticación y autorización.
 versions:
   enterprise-server: '*'
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/es-XL/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/es-XL/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index a35ab0c8c9..ac844e45ba 100644
--- a/translations/es-XL/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/es-XL/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -15,6 +15,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### Acerca del acceso al shell administrativo
diff --git a/translations/es-XL/content/admin/configuration/accessing-the-management-console.md b/translations/es-XL/content/admin/configuration/accessing-the-management-console.md
index 8eea269f13..992f3f4007 100644
--- a/translations/es-XL/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/es-XL/content/admin/configuration/accessing-the-management-console.md
@@ -14,6 +14,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Acerca de {% data variables.enterprise.management_console %}
diff --git a/translations/es-XL/content/admin/configuration/command-line-utilities.md b/translations/es-XL/content/admin/configuration/command-line-utilities.md
index 533d7fe414..e4ae5f6c13 100644
--- a/translations/es-XL/content/admin/configuration/command-line-utilities.md
+++ b/translations/es-XL/content/admin/configuration/command-line-utilities.md
@@ -11,6 +11,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - SSH
 ---
 
 Puedes ejecutar estos comandos desde cualquier lugar en la VM después de iniciar sesión como usuario administrador de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
diff --git a/translations/es-XL/content/admin/configuration/configuring-a-hostname.md b/translations/es-XL/content/admin/configuration/configuring-a-hostname.md
index 75e9286f3f..1ec64b79ef 100644
--- a/translations/es-XL/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/es-XL/content/admin/configuration/configuring-a-hostname.md
@@ -9,6 +9,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 Si configuras un nombre del host en lugar de una dirección IP codificada de forma rígida, podrás cambiar el hardware físico que ejecuta {% data variables.product.product_location_enterprise %} sin afectar a los usuarios o al software del cliente.
diff --git a/translations/es-XL/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/es-XL/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 87c930c9d0..7ba54553f5 100644
--- a/translations/es-XL/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/es-XL/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -9,6 +9,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Cuando se habilita un servidor proxy para {% data variables.product.product_location_enterprise %}, primero {% data variables.product.prodname_ghe_server %} envía mensajes fuera de banda a través del servidor proxy, a menos que el host de destino se agregue como una exclusión de servidor proxy HTTP. Los tipos de mensajes fuera de banda incluyen webhooks salientes, carga de paquetes y extracción de avatares heredados. La URL del servidor proxy es el protocolo, dominio o dirección IP más el número de puerto, por ejemplo `http://127.0.0.1:8123`.
diff --git a/translations/es-XL/content/admin/configuration/configuring-applications.md b/translations/es-XL/content/admin/configuration/configuring-applications.md
index 906ec94278..650ab00ee5 100644
--- a/translations/es-XL/content/admin/configuration/configuring-applications.md
+++ b/translations/es-XL/content/admin/configuration/configuring-applications.md
@@ -8,6 +8,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Ajustar el almacenamiento en caché de las imágenes
diff --git a/translations/es-XL/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/es-XL/content/admin/configuration/configuring-backups-on-your-appliance.md
index 12469d032b..c57e929ef8 100644
--- a/translations/es-XL/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/es-XL/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -16,7 +16,10 @@ intro: 'Como parte de un plan de recuperación ante desastres, puedes proteger l
 versions:
   enterprise-server: '*'
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### Acerca de {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/es-XL/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/es-XL/content/admin/configuration/configuring-built-in-firewall-rules.md
index 0cd27a89b1..6860c95d1f 100644
--- a/translations/es-XL/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/es-XL/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -9,6 +9,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Acerca del firewell de {% data variables.product.product_location_enterprise %}
diff --git a/translations/es-XL/content/admin/configuration/configuring-dns-nameservers.md b/translations/es-XL/content/admin/configuration/configuring-dns-nameservers.md
index c4fb322e55..256dd58137 100644
--- a/translations/es-XL/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/es-XL/content/admin/configuration/configuring-dns-nameservers.md
@@ -9,6 +9,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Los servidores de nombres que especifiques deben resolver el nombre del host de {% data variables.product.product_location_enterprise %}.
diff --git a/translations/es-XL/content/admin/configuration/configuring-rate-limits.md b/translations/es-XL/content/admin/configuration/configuring-rate-limits.md
index 0c7ec468c5..ff51dd7c26 100644
--- a/translations/es-XL/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/es-XL/content/admin/configuration/configuring-rate-limits.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### Habilitar límites de tasa para {% data variables.product.prodname_enterprise_api %}
diff --git a/translations/es-XL/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/es-XL/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index 06231c8d1d..706fc724c3 100644
--- a/translations/es-XL/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/es-XL/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -8,6 +8,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_installation.open-vm-console-start %}
diff --git a/translations/es-XL/content/admin/configuration/configuring-time-synchronization.md b/translations/es-XL/content/admin/configuration/configuring-time-synchronization.md
index e98d695131..afc99de357 100644
--- a/translations/es-XL/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/es-XL/content/admin/configuration/configuring-time-synchronization.md
@@ -12,6 +12,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Cambiar los servidores NTP predeterminados
diff --git a/translations/es-XL/content/admin/configuration/configuring-tls.md b/translations/es-XL/content/admin/configuration/configuring-tls.md
index 6e67f79cd1..4d2e531959 100644
--- a/translations/es-XL/content/admin/configuration/configuring-tls.md
+++ b/translations/es-XL/content/admin/configuration/configuring-tls.md
@@ -10,6 +10,10 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Acerca de la Seguridad de la capa de transporte
diff --git a/translations/es-XL/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/es-XL/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index c08310a5a5..f8615c6477 100644
--- a/translations/es-XL/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/es-XL/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -12,6 +12,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### Acerca de {% data variables.product.prodname_github_connect %}
diff --git a/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index 15c0b665a1..aa3b7b0656 100644
--- a/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -10,6 +10,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Security
 ---
 
 ### About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-XL/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/es-XL/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index c41b16cd5b..80bfbac934 100644
--- a/translations/es-XL/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/es-XL/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -14,6 +14,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### Acerca del modo de mantenimiento
diff --git a/translations/es-XL/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-XL/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 2caa1d6484..a4c59929c9 100644
--- a/translations/es-XL/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/es-XL/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -9,6 +9,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### Acerca de la sincronización de licencias
diff --git a/translations/es-XL/content/admin/configuration/enabling-private-mode.md b/translations/es-XL/content/admin/configuration/enabling-private-mode.md
index 1bf6bdd15e..fcbea0f6e5 100644
--- a/translations/es-XL/content/admin/configuration/enabling-private-mode.md
+++ b/translations/es-XL/content/admin/configuration/enabling-private-mode.md
@@ -10,7 +10,14 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 Debes habilitar el modo privado si {% data variables.product.product_location_enterprise %} es de acceso público por internet. En el modo privado, los usuarios no pueden clonar repositorios en forma anónima por `git://`. Si también está habilitada la autenticación incorporada, un administrador debe invitar a los nuevos usuarios para que creen una cuenta en la instancia. Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)."
diff --git a/translations/es-XL/content/admin/configuration/enabling-subdomain-isolation.md b/translations/es-XL/content/admin/configuration/enabling-subdomain-isolation.md
index 2b60020e2a..156cb5e98d 100644
--- a/translations/es-XL/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/es-XL/content/admin/configuration/enabling-subdomain-isolation.md
@@ -9,6 +9,10 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Acerca del aislamiento de subdominio
diff --git a/translations/es-XL/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/es-XL/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index 158f158dc1..7960aae60c 100644
--- a/translations/es-XL/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/es-XL/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 Como un administrador del sitio, puedes habilitar a los usuarios finales para que envíen sus recuentos de contribuciones de manera anónima por sus trabajos desde {% data variables.product.prodname_ghe_server %} a sus gráficos de contribuciones {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/es-XL/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/es-XL/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 030daf3928..38afacc31e 100644
--- a/translations/es-XL/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/es-XL/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 Cuando habilitas la búsqueda unificada, los usuarios pueden ver los resultados de la búsqueda desde contenido público y privado en {% data variables.product.prodname_dotcom_the_website %} cuando buscan desde {% data variables.product.product_location_enterprise %}.
diff --git a/translations/es-XL/content/admin/configuration/network-ports.md b/translations/es-XL/content/admin/configuration/network-ports.md
index 2cc32a9c03..e7ed0a1b83 100644
--- a/translations/es-XL/content/admin/configuration/network-ports.md
+++ b/translations/es-XL/content/admin/configuration/network-ports.md
@@ -12,6 +12,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Puertos administrativos
diff --git a/translations/es-XL/content/admin/configuration/site-admin-dashboard.md b/translations/es-XL/content/admin/configuration/site-admin-dashboard.md
index 4bf7972e34..34b35a1e25 100644
--- a/translations/es-XL/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/es-XL/content/admin/configuration/site-admin-dashboard.md
@@ -9,6 +9,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 Para acceder al tablero, en la esquina superior derecha de cualquier página, haz clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/es-XL/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/es-XL/content/admin/configuration/troubleshooting-ssl-errors.md
index 1e3bfb3e03..52006d5b76 100644
--- a/translations/es-XL/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/es-XL/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -10,6 +10,11 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### Eliminar la contraseña de un archivo clave
diff --git a/translations/es-XL/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/es-XL/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index afd8e8279f..13676b033c 100644
--- a/translations/es-XL/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/es-XL/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -9,6 +9,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/es-XL/content/admin/configuration/validating-your-domain-settings.md b/translations/es-XL/content/admin/configuration/validating-your-domain-settings.md
index 1387f40b2c..123ae286e5 100644
--- a/translations/es-XL/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/es-XL/content/admin/configuration/validating-your-domain-settings.md
@@ -8,6 +8,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/es-XL/content/admin/enterprise-management/about-cluster-nodes.md b/translations/es-XL/content/admin/enterprise-management/about-cluster-nodes.md
index 1f38bceb94..c5f83b1038 100644
--- a/translations/es-XL/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/es-XL/content/admin/enterprise-management/about-cluster-nodes.md
@@ -7,6 +7,7 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/enterprise-management/about-clustering.md b/translations/es-XL/content/admin/enterprise-management/about-clustering.md
index 625b42b5e6..519b5ec6cc 100644
--- a/translations/es-XL/content/admin/enterprise-management/about-clustering.md
+++ b/translations/es-XL/content/admin/enterprise-management/about-clustering.md
@@ -9,6 +9,7 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/enterprise-management/about-geo-replication.md b/translations/es-XL/content/admin/enterprise-management/about-geo-replication.md
index 46ee6097f0..dfa9127635 100644
--- a/translations/es-XL/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/es-XL/content/admin/enterprise-management/about-geo-replication.md
@@ -8,6 +8,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - High availability
 ---
 
 Contar con múltiples réplicas puede permitir una menor distancia a la réplica más cercana. Por ejemplo, una organización con oficinas en San Francisco, Nueva York y Londres podrían ejecutar el aparato principal en un centro de datos cercano a Nueva York y dos réplicas en centros de datos cercanos a San Francisco y Londres. Al usar DNS con información de geolocalización, se puede dirigir a los usuarios al servidor disponible más cercano para que accedan a los datos más rápido. Designar como principal el aparato cercano a Nueva York ayuda a reducir la latencia entre los hosts, a diferencia de si se designa como principal el aparato cercano a San Francisco, que tiene mayor latencia con Londres.
diff --git a/translations/es-XL/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/es-XL/content/admin/enterprise-management/about-high-availability-configuration.md
index 5fd50e6db2..c1ad7593b6 100644
--- a/translations/es-XL/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/es-XL/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Cuando configuras la alta disponibilidad, hay una configuración automática unidireccional, una replicación asincrónica de todos los almacenes de datos (repositorios de Git, MySQL, Redis y Elasticsearch) desde el aparato principal hacia la réplica.
diff --git a/translations/es-XL/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/es-XL/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 6c8933af21..a1ba32e31f 100644
--- a/translations/es-XL/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/es-XL/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -8,6 +8,10 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Acceder al tablero del monitor
diff --git a/translations/es-XL/content/admin/enterprise-management/cluster-network-configuration.md b/translations/es-XL/content/admin/enterprise-management/cluster-network-configuration.md
index d41b968cdd..11ded27fc3 100644
--- a/translations/es-XL/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/es-XL/content/admin/enterprise-management/cluster-network-configuration.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### Consideraciones de red
diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-collectd.md b/translations/es-XL/content/admin/enterprise-management/configuring-collectd.md
index b074943fc4..d254aace85 100644
--- a/translations/es-XL/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/es-XL/content/admin/enterprise-management/configuring-collectd.md
@@ -9,6 +9,10 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Configura un servidor `collectd` externo
diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index 6c322e4559..70fda93290 100644
--- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '>2.21'
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About high availability replication for clusters
diff --git a/translations/es-XL/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/es-XL/content/admin/enterprise-management/creating-a-high-availability-replica.md
index b453ccf498..ed4bb5f8c8 100644
--- a/translations/es-XL/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/es-XL/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Crear una réplica de alta disponibilidad
diff --git a/translations/es-XL/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/es-XL/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index b36600b29e..c5dc3829f4 100644
--- a/translations/es-XL/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/es-XL/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Escenarios de fallas
diff --git a/translations/es-XL/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/es-XL/content/admin/enterprise-management/enabling-automatic-update-checks.md
index 2d438cf74d..0ebecdfabf 100644
--- a/translations/es-XL/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/es-XL/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -8,6 +8,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 Cuando un paquete de actualizaciones se descarga automáticamente para {% data variables.product.product_location_enterprise %}, recibirás un mensaje informándote que puedes actualizar el {% data variables.product.prodname_ghe_server %}. Descarga de paquetes para el directorio `/var/lib/ghe-updates` en {% data variables.product.product_location_enterprise %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)."
diff --git a/translations/es-XL/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/es-XL/content/admin/enterprise-management/evacuating-a-cluster-node.md
index 39736afb65..d66a14ae60 100644
--- a/translations/es-XL/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/es-XL/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -7,6 +7,7 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/es-XL/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index cecde49464..3e71d9359d 100644
--- a/translations/es-XL/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/es-XL/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/es-XL/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/es-XL/content/admin/enterprise-management/increasing-storage-capacity.md
index d0672ace12..6c67ce1491 100644
--- a/translations/es-XL/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/es-XL/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -8,6 +8,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/es-XL/content/admin/enterprise-management/initializing-the-cluster.md b/translations/es-XL/content/admin/enterprise-management/initializing-the-cluster.md
index 47b34ba6c9..1577e44d2a 100644
--- a/translations/es-XL/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/es-XL/content/admin/enterprise-management/initializing-the-cluster.md
@@ -7,6 +7,7 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 8348b71d6a..a2d648f9b5 100644
--- a/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para impulsar la réplica y redireccionar el tráfico de forma manual. El tiempo promedio varía entre 2 y 10 minutos.
diff --git a/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index dc6763620f..7e6cd8e86e 100644
--- a/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/es-XL/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -6,7 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '>2.21'
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About failover to your replica cluster
diff --git a/translations/es-XL/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/es-XL/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index 40715168c2..6bb6c7deb4 100644
--- a/translations/es-XL/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/es-XL/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -14,6 +14,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 Se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 y superior. No se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 o inferior. Primero debes actualizar a 11.10.348 en varias actualizaciones. Para obtener más información, consulta el procedimiento de actualización 11.10.348, "[Actualizar al lanzamiento más reciente](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)."
diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/es-XL/content/admin/enterprise-management/monitoring-cluster-nodes.md
index 5ac5c4d7db..9ecca1af40 100644
--- a/translations/es-XL/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/es-XL/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -7,7 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 ### Manually checking cluster status
 
diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/es-XL/content/admin/enterprise-management/monitoring-using-snmp.md
index 52253bbbc7..c7f6e5aeb8 100644
--- a/translations/es-XL/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/es-XL/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -9,6 +9,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP es una norma común para controlar dispositivos en una red. Recomendamos firmemente habilitar SNMP para que puedas controlar la salud de {% data variables.product.product_location_enterprise %} y saber cuándo agregar más memoria, almacenamiento, o rendimiento del procesador a la máquina del servidor.
diff --git a/translations/es-XL/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/es-XL/content/admin/enterprise-management/recommended-alert-thresholds.md
index 0a4fd82c92..307ade5cee 100644
--- a/translations/es-XL/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/es-XL/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -10,6 +10,10 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### Controlar el almacenamiento
diff --git a/translations/es-XL/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/es-XL/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index 20ebd73eb4..ed110ec060 100644
--- a/translations/es-XL/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/es-XL/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Puedes utilizar el aparato principal antiguo como el nuevo aparato de réplica si la conmutación por error fue planeada o no estaba relacionada con la salud del aparato. Si la conmutación por error estaba relacionado con un problema con el aparato primario, es posible que prefieras crear un nuevo aparato de réplica. Para obtener más información, consulta "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)."
diff --git a/translations/es-XL/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/es-XL/content/admin/enterprise-management/removing-a-high-availability-replica.md
index c269743b9a..b656ec799b 100644
--- a/translations/es-XL/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/es-XL/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -7,7 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### Detener una replicación de forma temporal
diff --git a/translations/es-XL/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/es-XL/content/admin/enterprise-management/replacing-a-cluster-node.md
index 1327755f95..18ef4491b0 100644
--- a/translations/es-XL/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/es-XL/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -7,7 +7,9 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/es-XL/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/es-XL/content/admin/enterprise-management/setting-up-external-monitoring.md
index eaf489bf3b..1290ab7dcb 100644
--- a/translations/es-XL/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/es-XL/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -8,6 +8,9 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Acerca de SNMP
diff --git a/translations/es-XL/content/admin/enterprise-management/upgrade-requirements.md b/translations/es-XL/content/admin/enterprise-management/upgrade-requirements.md
index 3ab8def7a4..3b8cdaa685 100644
--- a/translations/es-XL/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/es-XL/content/admin/enterprise-management/upgrade-requirements.md
@@ -9,6 +9,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
diff --git a/translations/es-XL/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/es-XL/content/admin/enterprise-management/upgrading-a-cluster.md
index b63a76bef8..4a572caa46 100644
--- a/translations/es-XL/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/es-XL/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -7,7 +7,9 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### Actualizar con un hotpatch
diff --git a/translations/es-XL/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/es-XL/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index b042e01cac..628bcd6da1 100644
--- a/translations/es-XL/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/es-XL/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -17,6 +17,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### Preparar para una actualización
diff --git a/translations/es-XL/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/es-XL/content/admin/enterprise-support/about-github-enterprise-support.md
index 7553f6e118..63bc188a29 100644
--- a/translations/es-XL/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/es-XL/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -8,6 +8,7 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index ec4df01e57..c28a33dfb3 100644
--- a/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -9,6 +9,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index ad341eab23..4f9b36db39 100644
--- a/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/es-XL/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -7,6 +7,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-XL/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/es-XL/content/admin/enterprise-support/about-support-for-advanced-security.md
index 1fc191da25..23d19f5618 100644
--- a/translations/es-XL/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/es-XL/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -7,6 +7,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/es-XL/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/es-XL/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index 084e951ce3..baca368795 100644
--- a/translations/es-XL/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/es-XL/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -8,6 +8,7 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 Antes de enviar un ticket, deberías:
diff --git a/translations/es-XL/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/es-XL/content/admin/enterprise-support/providing-data-to-github-support.md
index d6a75f67b9..0ddcc1a081 100644
--- a/translations/es-XL/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/es-XL/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -10,6 +10,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Crear y compartir archivos de diagnóstico
diff --git a/translations/es-XL/content/admin/enterprise-support/reaching-github-support.md b/translations/es-XL/content/admin/enterprise-support/reaching-github-support.md
index d16a0610d1..340a2654f7 100644
--- a/translations/es-XL/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/es-XL/content/admin/enterprise-support/reaching-github-support.md
@@ -8,6 +8,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Usar sistemas de tickets automatizado
diff --git a/translations/es-XL/content/admin/enterprise-support/submitting-a-ticket.md b/translations/es-XL/content/admin/enterprise-support/submitting-a-ticket.md
index ff5df177a8..8824b8682d 100644
--- a/translations/es-XL/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/es-XL/content/admin/enterprise-support/submitting-a-ticket.md
@@ -8,6 +8,7 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Acerca del envío de tickets
diff --git a/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index 255169c822..003f24e239 100644
--- a/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -8,7 +8,9 @@ versions:
   enterprise-server: '>=2.22'
   github-ae: next
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index ea077ffdd4..fbf58a6803 100644
--- a/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -7,7 +7,9 @@ versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/es-XL/content/admin/installation/index.md b/translations/es-XL/content/admin/installation/index.md
index c0cd873184..f85fdeae4d 100644
--- a/translations/es-XL/content/admin/installation/index.md
+++ b/translations/es-XL/content/admin/installation/index.md
@@ -13,6 +13,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/es-XL/content/admin/installation/setting-up-a-staging-instance.md b/translations/es-XL/content/admin/installation/setting-up-a-staging-instance.md
index f854896822..822c7f0237 100644
--- a/translations/es-XL/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/es-XL/content/admin/installation/setting-up-a-staging-instance.md
@@ -7,6 +7,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/es-XL/content/admin/overview/about-enterprise-accounts.md b/translations/es-XL/content/admin/overview/about-enterprise-accounts.md
index 8fce1e695a..f2afe39ec8 100644
--- a/translations/es-XL/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/es-XL/content/admin/overview/about-enterprise-accounts.md
@@ -8,7 +8,9 @@ versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### Acerca de las cuentas empresariales en {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-XL/content/admin/overview/system-overview.md b/translations/es-XL/content/admin/overview/system-overview.md
index e537ef525e..b648858c13 100644
--- a/translations/es-XL/content/admin/overview/system-overview.md
+++ b/translations/es-XL/content/admin/overview/system-overview.md
@@ -8,6 +8,10 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### Arquitectura de almancenamiento
diff --git a/translations/es-XL/content/admin/policies/about-pre-receive-hooks.md b/translations/es-XL/content/admin/policies/about-pre-receive-hooks.md
index 48375feea4..cabcbe275c 100644
--- a/translations/es-XL/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/es-XL/content/admin/policies/about-pre-receive-hooks.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Cuando se produce una subida, cada script se ejecuta en un entorno aislado y puede realizar verificaciones en el contenido que se subió. Los scripts provocarán la aceptación de la subida si el estado de salida es 0, o rechazado si el estado de salida no es cero.
diff --git a/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-environment.md
index c2ca419766..8636bae29a 100644
--- a/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Un entorno de pre-recepción para el {% data variables.product.prodname_ghe_server %} es un entorno Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot). Dado que los ganchos de pre-recepción se ejecutan en todos los eventos de extracción, deberían ser rápidos y livianos. Normalmente, el entorno necesario para tales verificaciones será mínimo.
diff --git a/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-script.md
index 5d14b865a4..c79f36c925 100644
--- a/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/es-XL/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -9,6 +9,8 @@ versions:
 miniTocMaxHeadingLevel: 4
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Puedes ver los ejemplos de los ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} en el repositorio [`github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks).
diff --git a/translations/es-XL/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-XL/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 28fffccb82..45a2d49b72 100644
--- a/translations/es-XL/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/es-XL/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -30,6 +30,8 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Configuring the default visibility of new repositories on your appliance
diff --git a/translations/es-XL/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/es-XL/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 49d760de19..f282d1e179 100644
--- a/translations/es-XL/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/es-XL/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -9,6 +9,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### Crear ganchos de pre-recepción
diff --git a/translations/es-XL/content/admin/user-management/about-migrations.md b/translations/es-XL/content/admin/user-management/about-migrations.md
index 198e426b3a..08dfa4f88b 100644
--- a/translations/es-XL/content/admin/user-management/about-migrations.md
+++ b/translations/es-XL/content/admin/user-management/about-migrations.md
@@ -8,6 +8,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Tipos de migraciones
diff --git a/translations/es-XL/content/admin/user-management/adding-people-to-teams.md b/translations/es-XL/content/admin/user-management/adding-people-to-teams.md
index d072c61dd5..6943a115a2 100644
--- a/translations/es-XL/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/es-XL/content/admin/user-management/adding-people-to-teams.md
@@ -9,7 +9,10 @@ intro: 'Una vez que se ha creado un equipo, los administradores de la organizaci
 versions:
   enterprise-server: '*'
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Cada equipo tiene sus propios premisos de acceso definidos de manera individual [ para repositorios que le pertenecen a tu organización](/articles/permission-levels-for-an-organization).
diff --git a/translations/es-XL/content/admin/user-management/audit-logging.md b/translations/es-XL/content/admin/user-management/audit-logging.md
index 0f1d4af36b..6c7585e5a7 100644
--- a/translations/es-XL/content/admin/user-management/audit-logging.md
+++ b/translations/es-XL/content/admin/user-management/audit-logging.md
@@ -9,7 +9,10 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Para encontrar un listado completo, consulta la sección "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". Para obtener más información sobre cómo encontrar una acción en particular, consulta la sección "[Buscar la bitácora de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)".
diff --git a/translations/es-XL/content/admin/user-management/audited-actions.md b/translations/es-XL/content/admin/user-management/audited-actions.md
index 5411d7c598..b2977ae5de 100644
--- a/translations/es-XL/content/admin/user-management/audited-actions.md
+++ b/translations/es-XL/content/admin/user-management/audited-actions.md
@@ -10,7 +10,9 @@ versions:
   github-ae: '*'
 miniTocMaxHeadingLevel: 4
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### Autenticación
diff --git a/translations/es-XL/content/admin/user-management/auditing-ssh-keys.md b/translations/es-XL/content/admin/user-management/auditing-ssh-keys.md
index 1c402449e2..c229a92390 100644
--- a/translations/es-XL/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/es-XL/content/admin/user-management/auditing-ssh-keys.md
@@ -8,7 +8,10 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 Una vez iniciada, la auditoría desactiva todas las claves SSH existentes y obliga a los usuarios a aprobarlas o rechazarlas antes de que sea posible clonarlas, extraerlas o subirlas a cualquier repositorio. Una auditoría es útil cuando un empleado o contratista se va de la empresa y necesitas asegurarte de que todas las claves estén verificadas.
diff --git a/translations/es-XL/content/admin/user-management/best-practices-for-user-security.md b/translations/es-XL/content/admin/user-management/best-practices-for-user-security.md
index 4161c46801..2c8e93fd5d 100644
--- a/translations/es-XL/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/es-XL/content/admin/user-management/best-practices-for-user-security.md
@@ -8,6 +8,8 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 ### Activar autenticación de dos factores
diff --git a/translations/es-XL/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/es-XL/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index 925a4c338e..7352c36dc5 100644
--- a/translations/es-XL/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/es-XL/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -16,7 +16,10 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### Acerca de {% data variables.large_files.product_name_long %}
diff --git a/translations/es-XL/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/es-XL/content/admin/user-management/configuring-visibility-for-organization-membership.md
index f353f00c29..0eef53ff3e 100644
--- a/translations/es-XL/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/es-XL/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -8,6 +8,8 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 También puedes implementar tu configuración por defecto en todos los miembros actuales de la organización en tu instancia usando una utilidad de línea de comandos. Por ejemplo, si quieres solicitar que la visibilidad de cada miembro de la organización sea pública, puedes establecer la configuración predeterminada como pública e implementar la predeterminada para todos los nuevos miembros en los parámetros de administración, y luego usar la utilidad de línea de comandos para implementar la configuración pública en los miembros existentes.
diff --git a/translations/es-XL/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/es-XL/content/admin/user-management/continuous-integration-using-jenkins.md
index fbbc4bd45e..5012f1cdb7 100644
--- a/translations/es-XL/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/es-XL/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -7,6 +7,7 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/user-management/creating-teams.md b/translations/es-XL/content/admin/user-management/creating-teams.md
index d51fa35786..70a304b7f3 100644
--- a/translations/es-XL/content/admin/user-management/creating-teams.md
+++ b/translations/es-XL/content/admin/user-management/creating-teams.md
@@ -6,7 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Los equipos son centrales para muchas de las características colaborativas de {% data variables.product.prodname_dotcom %}, como las @menciones del equipo para notificar a las partes correspondientes que les quieres solicitar su colaboración o atención. Para obtener más información, consulta "[Niveles de permisos para el repositorio de una organizazión](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)".
diff --git a/translations/es-XL/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/es-XL/content/admin/user-management/exporting-migration-data-from-githubcom.md
index a00faf84be..564f182320 100644
--- a/translations/es-XL/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/es-XL/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -12,7 +12,9 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparar la orgnanización origen en {% data variables.product.prodname_dotcom %}
diff --git a/translations/es-XL/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/es-XL/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index d9c1920329..cf00c2abfd 100644
--- a/translations/es-XL/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/es-XL/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -12,7 +12,9 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparar la instancia origen de {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-XL/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/es-XL/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 63290d9472..9c76604cb3 100644
--- a/translations/es-XL/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/es-XL/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -8,6 +8,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Importar proyectos de Mercurial
diff --git a/translations/es-XL/content/admin/user-management/managing-dormant-users.md b/translations/es-XL/content/admin/user-management/managing-dormant-users.md
index 9d1eb14e4b..6b5eadd1c6 100644
--- a/translations/es-XL/content/admin/user-management/managing-dormant-users.md
+++ b/translations/es-XL/content/admin/user-management/managing-dormant-users.md
@@ -10,7 +10,9 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 "Activity" includes, but is not limited to:
diff --git a/translations/es-XL/content/admin/user-management/managing-global-webhooks.md b/translations/es-XL/content/admin/user-management/managing-global-webhooks.md
index e7e9d0fad3..40340941f6 100644
--- a/translations/es-XL/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/es-XL/content/admin/user-management/managing-global-webhooks.md
@@ -9,6 +9,7 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### Acerca de los webhooks locales
diff --git a/translations/es-XL/content/admin/user-management/managing-projects-using-jira.md b/translations/es-XL/content/admin/user-management/managing-projects-using-jira.md
index 0356929745..cfdef67e91 100644
--- a/translations/es-XL/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/es-XL/content/admin/user-management/managing-projects-using-jira.md
@@ -11,6 +11,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Project management
 ---
 
 ### Conectar JIRA a una organización {% data variables.product.prodname_enterprise %}
diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/es-XL/content/admin/user-management/migrating-data-to-your-enterprise.md
index baec17aab6..3ff0184159 100644
--- a/translations/es-XL/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/es-XL/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -15,6 +15,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Aplicar los datos importados en {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-XL/content/admin/user-management/migrating-to-internal-repositories.md b/translations/es-XL/content/admin/user-management/migrating-to-internal-repositories.md
index c905df33d3..1ff765e57c 100644
--- a/translations/es-XL/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/es-XL/content/admin/user-management/migrating-to-internal-repositories.md
@@ -9,6 +9,9 @@ versions:
   enterprise-server: '>=2.20'
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### Acerca de los repositorios internos
diff --git a/translations/es-XL/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/es-XL/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index d2bd05e920..396d4da72a 100644
--- a/translations/es-XL/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/es-XL/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -7,7 +7,11 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 Generalmente, si alguien elimina un repositorio, estará disponible en el disco por 90 días y se puede restablecer mediante el tablero de administración del sitio. Después de los 90 días, el repositorio se purga y se elimina para siempre. Si asignas un titular legal a un usuario o una organización, los repositorios que ellos poseen se pueden restablecer indefinidamente.
diff --git a/translations/es-XL/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/es-XL/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index e020328a99..59b1767bb7 100644
--- a/translations/es-XL/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/es-XL/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -12,6 +12,7 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Preparar los datos migrados para importarlos a {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-XL/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/es-XL/content/admin/user-management/preventing-users-from-creating-organizations.md
index 7fbc7b9d32..f60b7f6253 100644
--- a/translations/es-XL/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/es-XL/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -10,6 +10,8 @@ versions:
   github-ae: '*'
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/es-XL/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/es-XL/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index 380ea007d8..eff92d431c 100644
--- a/translations/es-XL/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/es-XL/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -8,6 +8,9 @@ intro: 'Los administradores del sitio pueden promover cualquier cuenta de usuari
 versions:
   enterprise-server: '*'
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/es-XL/content/admin/user-management/rebuilding-contributions-data.md b/translations/es-XL/content/admin/user-management/rebuilding-contributions-data.md
index b4216d7f08..107d30f8e0 100644
--- a/translations/es-XL/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/es-XL/content/admin/user-management/rebuilding-contributions-data.md
@@ -8,6 +8,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 Siempre que se sube una confirmación de cambios a {% data variables.product.prodname_enterprise %}, se vincula a una cuenta de usuario, si ambas están asociadas con la misma dirección de correo electrónico. Sin embargo, las confirmaciones de cambio existentes *no* se vinculan de forma retroactiva cuando un usuario registra una dirección de correo electrónico nueva o crea una cuenta nueva.
diff --git a/translations/es-XL/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/es-XL/content/admin/user-management/removing-users-from-teams-and-organizations.md
index 4dcae1aa72..b435778b2d 100644
--- a/translations/es-XL/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/es-XL/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -6,7 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Solo los propietarios o los administradores del equipo pueden eliminar miembros de la organización. Cuando se elimina un usuario de un equipo o una organización, sus propuestas, solicitudes de extracción y comentarios en los repositorios de la organización permanecen intactos y siguen siendo atribuidos al usuario.
diff --git a/translations/es-XL/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/es-XL/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index 4cc2179e42..d5a9386f78 100644
--- a/translations/es-XL/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/es-XL/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -6,7 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 Al usar la autenticación integrada o LDAP, el aparato {% data variables.product.prodname_ghe_server %} admite la autenticación de dos factores. Los administradores de la organización le pueden solicitar a los miembros que tengan la autenticación de dos factores activada.
diff --git a/translations/es-XL/content/admin/user-management/searching-the-audit-log.md b/translations/es-XL/content/admin/user-management/searching-the-audit-log.md
index 416dddd4dd..5e5e4fc56b 100644
--- a/translations/es-XL/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/es-XL/content/admin/user-management/searching-the-audit-log.md
@@ -9,7 +9,9 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### Buscar sintaxis de consultas
diff --git a/translations/es-XL/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/es-XL/content/admin/user-management/suspending-and-unsuspending-users.md
index 619a21265e..7a07d71fab 100644
--- a/translations/es-XL/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/es-XL/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -11,7 +11,10 @@ intro: 'Si un usuario se va o se traslada a un lugar diferente de la empresa, de
 versions:
   enterprise-server: '*'
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 Puedes suspender las cuentas de usuario de {% data variables.product.prodname_ghe_server %} de aquellos que abandonen la compañía para abrir licencias de usuario en tu licencia de {% data variables.product.prodname_enterprise %} preservando las propuestas, comentarios, repositorios, gists y otros datos que hayan creado. Los usuarios suspendidos no pueden iniciar sesión en tu instancia, y no pueden subir ni extraer un código.
diff --git a/translations/es-XL/content/admin/user-management/viewing-push-logs.md b/translations/es-XL/content/admin/user-management/viewing-push-logs.md
index c9404b68ad..f9bbe8fe3a 100644
--- a/translations/es-XL/content/admin/user-management/viewing-push-logs.md
+++ b/translations/es-XL/content/admin/user-management/viewing-push-logs.md
@@ -9,7 +9,10 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 Las entradas de registro de subida muestran:
diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md
index 7393543a2a..f9fb386454 100644
--- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md
+++ b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github.md
@@ -2,7 +2,7 @@
 title: Cargar cambios en GitHub
 shortTitle: Cargar cambios
 intro: 'De manera que confirmes cambios localmente en tu proyecto, puedes cargarlos a {% data variables.product.prodname_dotcom %} para que otros puedan acceder a ellos desde el repositorio remoto.'
-permissions: Las personas con permisos de escritura pueden cargar cambios a un repositorio.
+permissions: People with write permissions can push changes to a repository.
 redirect_from:
   - /desktop/contributing-to-projects/pushing-changes-to-github
 versions:
diff --git a/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index eab91447fa..3b91f70776 100644
--- a/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -2,7 +2,7 @@
 title: Configurando tu zona horaria para GitHub Insights
 intro: 'Puedes establecer la zona horaria para las métricas que ves en {% data variables.product.prodname_insights %}.'
 product: '{% data reusables.gated-features.github-insights %}'
-permissions: 'Cualquiera con acceso a {% data variables.product.prodname_insights %} puede establecer su propia zona horaria.'
+permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
 ---
diff --git a/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 6be7acbfd6..59b451df20 100644
--- a/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/es-XL/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -3,8 +3,8 @@ title: Ver métricas e informes clave
 intro: Puedes ver y filtrar métricas e informes clave para ayudarte a comprender y mejorar tu proceso de entrega de software mediante datos.
 product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
-  - /GitHub/Installing-and-Configuring-GitHub-Insights/Viewing-and-Filtering-Key-Metrics-and-Reports
-permissions: 'Cualquier persona con acceso a {% data variables.product.prodname_insights %} puede ver los informes y las métricas clave.'
+  - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
+permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
 versions:
   enterprise-server: '*'
 ---
diff --git a/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index 3e6877fd9c..a82d0cbf76 100644
--- a/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -4,7 +4,7 @@ intro: 'Puedes activar y desactivar métricas específicas en {% data variables.
 product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
-permissions: 'Las personas con permisos de administrador para {% data variables.product.prodname_insights %} pueden administrar las métricas e informes disponibles.'
+permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
 versions:
   enterprise-server: '*'
 ---
diff --git a/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 86c57d66b1..78d21a175e 100644
--- a/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/es-XL/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -4,7 +4,7 @@ intro: 'Puedes administrar las organizaciones {% data variables.product.prodname
 product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
-permissions: 'Las personas con permisos de administrador en {% data variables.product.prodname_insights %} pueden administrar organizaciones.'
+permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
 versions:
   enterprise-server: '*'
 ---
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index 1c44559d17..2ad6bcc268 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md
index 16a8b4862c..da9b31430d 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # `hello` ステップからの出力を使用する
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
index cd8c5858aa..3a31276586 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md
@@ -159,11 +159,11 @@ This action prints "Hello World" or "Hello" + the name of a person to greet to t
 
 挨拶した時間。
 
-##
+## 使用例
 
-使用例: アクション/ハローワールドjavascript-action@v1.1
-:
-  誰が挨拶する:'モナ・ザ・オクトキャット'
+uses: actions/hello-world-javascript-action@v1.1
+with:
+  who-to-greet: 'Mona the Octocat'
 ```
 
 ### アクションの GitHub へのコミットとタグ、プッシュ
@@ -215,21 +215,21 @@ git push --follow-tags
 {% raw %}
 **.github/workflows/main.yml**
 ```yaml
-オン
-  hello_world_job: [push]
+on: [push]
 
-ジョブ:  :  :
-    実行: ubuntu-最新の
-    名: こんにちは
-    ステップを言う仕事:
-    - 名前: こんにちは世界アクションステップ
-      id: こんにちは
-      使用: アクション/hello-world-javascript-action@v1.1
-      :
-        誰が挨拶: 'モナ・ザ・オクトキャット'
-    # 'hello' ステップからの出力を使用
-    - 名前
-      : echo{{ steps.hello.outputs.time }}
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # `hello`ステップからの出力を使用する
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 60137a34f0..d65c846cd6 100644
--- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -58,7 +58,7 @@ inputs:
 
 ワークフローファイル内で、あるいはデフォルトの入力値を使ってアクションに入力を指定すると、{% data variables.product.prodname_dotcom %}はその入力に対応して`INPUT_<VARIABLE_NAME>`という名前の環境変数を生成します。 生成される環境変数では、入力の名前を大文字にして、空白を`_`に変換します。
 
-For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables.
+たとえば、ワークフローで `numOctocats` および `octocatEyeColor` 入力が定義されている場合、アクションコードは `INPUT_NUMOCTOCATS` および `INPUT_OCTOCATEYECOLOR` 環境変数を使用して入力の値を読み取ることができます。
 
 #### `inputs.<input_id>`
 
@@ -78,7 +78,7 @@ For example, if a workflow defined the `numOctocats` and `octocatEyeColor` input
 
 #### `inputs.<input_id>.deprecationMessage`
 
-**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives.
+**オプション** 入力パラメータが使用されている場合、この `string` は警告メッセージとしてログに記録されます。 この警告で入力が非推奨であることをユーザに通知し、その他の方法を知らせることができます。
 
 ### `outputs`
 
@@ -171,7 +171,7 @@ runs:
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 #### `post`
@@ -197,7 +197,7 @@ runs:
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 ### 複合実行ステップアクションのための`runs`
@@ -295,14 +295,14 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
 
 #### `runs.image`
 
-**必須** アクションを実行するためにコンテナとして使われるDockerイメージ。 この値には、Dockerのベースイメージ名、自分のリポジトリ中のローカル`Dockerfile`、Docker Hubあるいはその他のレジストリ中のパブリックなイメージを指定できます。 To reference a `Dockerfile` local to your repository, the file must be named `Dockerfile` and you must use a path relative to your action metadata file. `docker`アプリケーションがこのファイルを実行します。
+**必須** アクションを実行するためにコンテナとして使われるDockerイメージ。 この値には、Dockerのベースイメージ名、自分のリポジトリ中のローカル`Dockerfile`、Docker Hubあるいはその他のレジストリ中のパブリックなイメージを指定できます。 リポジトリのローカルにある `Dockerfile` を参照するには、ファイルに `Dockerfile` という名前を付け、アクションメタデータファイルに相対的なパスを使用する必要があります。 `docker`アプリケーションがこのファイルを実行します。
 
 #### `runs.env`
 
@@ -323,7 +323,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md
index ee57c19757..ba14542ac1 100644
--- a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -20,10 +20,10 @@ type: how_to
 
 {% data variables.product.prodname_dotcom %} は、終了コードを使用して、アクションのチェック実行ステータスを設定します。これは、`success` または`failure` のいずれかです。
 
-| 終了ステータス                           | チェック実行ステータス | 説明                                                                                                                            |
-| --------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `0`                               | `success`   | アクションが正常に完了し、それに依存する他のタスクを開始できます。                                                                                             |
-| Nonzero value (any integer but 0) | `failure`   | その他の終了コードは、アクションの失敗を表します。 アクションが失敗すると、同時に実行されていたアクションはすべてキャンセルされ、今後のアクションはスキップされます。 チェック実行とチェックスイートはどちらも、`failure`ステータスになります。 |
+| 終了ステータス             | チェック実行ステータス | 説明                                                                                                                            |
+| ------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `0`                 | `success`   | アクションが正常に完了し、それに依存する他のタスクを開始できます。                                                                                             |
+| ゼロ以外の値 (0 以外の任意の整数) | `failure`   | その他の終了コードは、アクションの失敗を表します。 アクションが失敗すると、同時に実行されていたアクションはすべてキャンセルされ、今後のアクションはスキップされます。 チェック実行とチェックスイートはどちらも、`failure`ステータスになります。 |
 
 ### JavaScript アクションで失敗終了を設定する
 
diff --git a/translations/ja-JP/content/actions/guides/about-continuous-integration.md b/translations/ja-JP/content/actions/guides/about-continuous-integration.md
index ab15eee6af..19c8a68df6 100644
--- a/translations/ja-JP/content/actions/guides/about-continuous-integration.md
+++ b/translations/ja-JP/content/actions/guides/about-continuous-integration.md
@@ -48,11 +48,13 @@ CI ワークフローは、{% data variables.product.product_name %} イベン
 一般的な用語の定義については「[{% data variables.product.prodname_actions %} の中核的概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)」を参照してください。
 
 ### サポートされている言語
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} では、各種言語およびフレームワークに応じて CI ワークフローテンプレートが提供されます。
 
 {% data variables.product.product_location %} 上の {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) リポジトリ{% else %} `actions/starter-workflows` リポジトリで {% data variables.product.product_name %} が提供する CI ワークフローテンプレートの完全なリストを参照します。{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### ワークフロー実行をスキップする
 
 ワークフローがトリガーされないようにする場合は、コミットメッセージにスキップ命令を追加できます。 `on: push` または `on: pull_request` でトリガーされるワークフローは、プッシュまたはプルリクエストの HEAD コミットで、次の文字列型のいずれかをコミットメッセージに追加した場合トリガーされません。
@@ -72,6 +74,7 @@ CI ワークフローは、{% data variables.product.product_name %} イベン
 **注釈:** スキップ命令は、`push` および `pull_request` イベントにのみ適用されます。 たとえば、コミットメッセージに `[skip ci]` を追加しても、`on: pull_request_target` でトリガーされたワークフロー実行は停止されません。
 
 {% endnote %}
+{% endif %}
 
 ### ワークフロー実行の通知
 
diff --git a/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md b/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md
index a7df8ffcfc..99b723f4b2 100644
--- a/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/ja-JP/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,39 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### パッケージングのステップについて
-
-パッケージングのステップは、継続的インテグレーションあるいは継続的デリバリのワークフローの一般的な部分です。 アプリケーションをビルドしてテストした後、実行もしくはデプロイ可能な成果物がパッケージの形で生成されます。 たとえば、Javaのプロジェクトのための継続的インテグレーションのワークフローは、`mvn package`を実行してJARファイルを生成するかもしれません。 あるいは、Node.jsアプリケーションのためのCIワークフローは、Dockerコンテナを作成するかもしれません。
-
-ビルドしているアプリケーションの種類によって、このパッケージは手動でのテストのためにローカルにダウンロードしたり、ユーザーがダウンロードできるようにしたり、ステージングあるいはプロダクションの環境にデプロイしたりできます。
-
-### 継続的インテグレーションワークフロー内でのパッケージング
-
-継続的インテグレーションワークフローの終わりにパッケージを作成すれば、Pull Requestに対するコードレビューの間に役立つことがあります。 コードをビルドしてテストした後、パッケージングのステップで実行可能な、あるいはデプロイ可能な成果物を生成できます。 そしてワークフローはワークフローの一部として、この成果物をアップロードできます。
-
-そうすれば、Pull Requestをレビューする際には、ワークフローの実行を見て生成された成果物をダウンロードできるでしょう。
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-こうすれば、Pull Request中のコードを自分のマシン上で実行できるので、Pull Requestのデバッグやテストに役立ちます。
-
-### パッケージを公開するためのワークフロー
-
-継続的インテグレーションのワークフロー中で、テストのためにパッケージ化された成果物をアップロードすることに加えて、プロジェクトをビルドして、パッケージをパッケージレジストリに公開するワークフローを作成できます。
-
-* **{% data variables.product.prodname_registry %} へのパッケージの公開**
-  {% data variables.product.prodname_registry %} は、多くの種類のパッケージのパッケージホスティングサービスとして機能します。 パッケージを{% data variables.product.prodname_dotcom %}のすべてと共有することも、パッケージをプライベートにしてコラボレータやOrganizationと共有することもできます。 詳しい情報については「[{% data variables.product.prodname_registry %}について](/github/managing-packages-with-github-packages/about-github-packages)」を参照してください。
-
-  デフォルトブランチへのプッシュごとに、パッケージを {% data variables.product.prodname_registry %} に公開することをお勧めします。 そうすれば、プロジェクトの開発者は常にmasterからの最新のビルドを{% data variables.product.prodname_registry %}からインストールして実行及びテストできるようになります。
-
-* **パッケージレジストリへのパッケージの公開**  
-  多くのプロジェクトで、新しいバージョンのプロジェクトがリリースされたときにパッケージレジストリへの公開が行われます。 たとえば、JARファイルを生成するプロジェクトは、新しいリリースをMaven Centralリポジトリにアップロードするかもしれません。 あるいは、.NETのプロジェクトはnugetのパッケージを生成し、NuGet Galleryへアップロードするかもしれません。
-
-  これは、リリースが作成される度にパッケージをパッケージレジストリに公開するワークフローを作成すれば、自動化できます。 詳しい情報については「[リリースの作成](/github/administering-a-repository/creating-releases)」を参照してください。
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md b/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md
index b1cec68e62..eaf093a41b 100644
--- a/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,14 +38,17 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `add-labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
 5. {% data reusables.actions.commit-workflow %}
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-net.md b/translations/ja-JP/content/actions/guides/building-and-testing-net.md
index c54b4a7f1f..8ca406153d 100644
--- a/translations/ja-JP/content/actions/guides/building-and-testing-net.md
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-net.md
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ jobs:
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ jobs:
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,13 +139,13 @@ steps:
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
   with:
     path: ~/.nuget/packages
-    # 対応する要件ファイルのキャッシュヒットがあるかどうかを確認する
+    # Look to see if there is a cache hit for the corresponding requirements file
     key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
     restore-keys: |
       ${{ runner.os }}-nuget
@@ -171,7 +171,7 @@ steps:
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 CIテストにパスしたら、Dotnetパッケージをパッケージレジストリに公開するようにワークフローを設定できます。 バイナリを公開するのに必要なトークンや認証情報を保存するために、リポジトリシークレットを使うことができます。 以下の例では、`dotnet core cli`を使ってパッケージを作成し、{% data variables.product.prodname_registry %}に公開しています。
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md
index fd9105a6b6..f8332dc9ca 100644
--- a/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ Node.js、YAML、ワークフローの設定オプションと、ワークフロ
 
 {% data variables.product.prodname_dotcom %}は、ほとんどのNode.jsプロジェクトで使えるNode.jsのワークフローテンプレートを提供しています。 このガイドには、カスタマイズして利用できるnpm及びYarnの例が含まれます。 詳しい情報については[Node.jsのワークフローテンプレート](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml)を参照してください。
 
-手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。
+手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。 The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,14 +119,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 Node.js のバージョンを指定しない場合、
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md b/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md
index e299769982..2dfd1a278d 100644
--- a/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-powershell.md
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ steps:
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-python.md b/translations/ja-JP/content/actions/guides/building-and-testing-python.md
index f67344e88f..13c90503ca 100644
--- a/translations/ja-JP/content/actions/guides/building-and-testing-python.md
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-python.md
@@ -58,25 +58,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Lint with flake8
-      run: |
-        # Python 構文エラーまたは未定義の名前がある場合はビルドを停止する
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zeroはすべてのエラーを警告として扱う。 GitHubのエディタの幅は127文字
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - name: Test with pytest
-      run: |
-        pytest
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -117,14 +117,14 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # 現在の Python バージョンを印刷して、マトリックスをテストできます
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -144,17 +144,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # セマンティックバージョン範囲構文もしくは厳密なPythonのバージョン
-        python-version: '3.x'
-        # オプション - x64もしくはx86アーキテクチャ、デフォルトはx64
-        architecture: 'x64'
-    # 現在のPythonのバージョンを出力して、マトリクスをテストできる
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -373,25 +373,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # pip及びpytestのインストール
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # テストに失敗があった場合でもテスト結果が公開されるよう、always()を使って常にこのステップを実行する
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -413,22 +413,22 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 {% endraw %}
 
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md
index c145d56ef5..cc24bdd89e 100644
--- a/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ Ruby、YAML、ワークフローの設定オプションと、ワークフロー
 
 {% data variables.product.prodname_dotcom %}は、ほとんどのRubyプロジェクトで使えるRubyのワークフローテンプレートを提供しています。 詳しい情報については[Rubyワークフローテンプレート](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml)を参照してください。
 
-手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。
+手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。 The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,54 +264,55 @@ CIテストにパスしたなら、Rubyパッケージを任意のパッケー
 
 パッケージを公開するのに必要なアクセストークンやクレデンシャルは、リポジトリシークレットを使って保存できます。 以下の例は、パッケージを作成して`GitHub Package Registry`及び`RubyGems`に公開します。
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
 
 on:
-  # 手動で公開
+  # Manually publish
   workflow_dispatch:
-  # あるいは変更がデフォルトブランチにマージされたときに公開。
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-swift.md b/translations/ja-JP/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..acfa9947a3
--- /dev/null
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Building and testing Swift
+intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### はじめに
+
+This guide shows you how to build and test a Swift package.
+
+{% if currentVersion == "github-ae@latest" %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. {% data variables.actions.hosted_runner %} に必要なソフトウェアがインストールされていることを確認する方法については、「[カスタムイメージの作成](/actions/using-github-hosted-runners/creating-custom-images)」を参照してください。
+{% else %}{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swift packages. For a full list of up-to-date software and the preinstalled versions of Swift and Xcode, see "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### 必要な環境
+
+YAMLの構文と、{% data variables.product.prodname_actions %}でのYAMLの使われ方に馴染んでいる必要があります。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)」を参照してください。
+
+We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
+
+### Starting with the Swift workflow template
+
+{% data variables.product.prodname_dotcom %} provides a Swift workflow template that should work for most Swift projects, and this guide includes examples that show you how to customize this template. For more information, see the [Swift workflow template](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Specifying a Swift version
+
+To use a specific preinstalled version of Swift on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `fwal/setup-swift` action. This action finds a specific version of Swift from the tools cache on the runner and adds the necessary binaries to `PATH`. These changes will persist for the remainder of a job. For more information, see the [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) action.
+
+If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+
+The examples below demonstrate using the `fwal/setup-swift` action.
+
+#### Using multiple Swift versions
+
+You can configure your job to use a multiple versions of Swift in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Using a single specific Swift version
+
+You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### コードのビルドとテスト
+
+You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/ja-JP/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/ja-JP/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..f98c333d1a
--- /dev/null
+++ b/translations/ja-JP/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Building and testing Xamarin applications
+intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Xamarin application.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### はじめに
+
+This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。
+
+{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### 必要な環境
+
+We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML, workflow configuration options, and how to create a workflow file. 詳しい情報については、以下を参照してください。
+
+- [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
+- "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Bulding Xamarin.iOS apps
+
+The example below demonstrates how to change the default Xamarin bundle and build  a Xamarin.iOS application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Bulding Xamarin.Android apps
+
+The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### .NETのバージョンの指定
+
+{% data variables.product.prodname_dotcom %}ホストランナーにプリインストールされたバージョンの.NET Core SDKを使うには、`setup-dotnet`アクションを使ってください。 このアクションは各ランナーのツールキャッシュから指定されたバージョンの.NETを見つけ、必要なバイナリを`PATH`に追加します。 これらの変更は、ジョブの残りの部分で保持されます。
+
+`setup-dotnet`アクションは、{% data variables.product.prodname_actions %}で.NETを使うための推奨される方法です。これは、それによって様々なランナーや様々なバージョンの.NETに渡って一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、.NETをインストールして`PATH`に追加しなければなりません。 詳しい情報については[`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk)アクションを参照してください。
diff --git a/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index 88e90e95e2..861d98a0dc 100644
--- a/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/ja-JP/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ topics:
 
 - `key`: **必須** このキーはキャッシュの保存時に作成され、キャッシュの検索に使われます。 変数、コンテキスト値、静的な文字列、関数の任意の組み合わせが使えます。 キーの長さは最大で512文字であり、キーが最大長よりも長いとアクションは失敗します。
 - `path`: **必須** ランナーがキャッシュあるいはリストアをするファイルパス。 このパスは、絶対パスでも、ワーキングディレクトリからの相対パスでもかまいません。
-  - `cache` アクションの `v2` では、単一のパスまたは複数のパスをリストとして指定できます。 パスはディレクトリまたは単一ファイルのいずれかで、glob パターンがサポートされています。
+  - パスはディレクトリまたは単一ファイルのいずれかで、glob パターンがサポートされています。
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. 例:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - `cache` アクションの `v1` では、単一のパスのみがサポートされ、かつそれがディレクトリである必要があります。 単一のファイルをキャッシュすることはできません。
 - `restore-keys`: **オプション** `key`に対するキャッシュヒットがなかった場合にキャッシュを見つけるために使われる代理キーの順序付きリスト。
 
@@ -82,30 +91,29 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-    - name: Cache node modules
-      uses: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm キャッシュファイルは Linux/macOS の「~/.npm」に保存される
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - name: Install Dependencies
-      run: npm install
+      - name: Install Dependencies
+        run: npm install
 
-    - name: Build
-      run: npm build
-
-    - name: Test
-      run: npm test
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/ja-JP/content/actions/guides/closing-inactive-issues.md b/translations/ja-JP/content/actions/guides/closing-inactive-issues.md
index 1885044096..600985ed3c 100644
--- a/translations/ja-JP/content/actions/guides/closing-inactive-issues.md
+++ b/translations/ja-JP/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,9 +51,9 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every day at 1:30 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `days-before-issue-stale` to the number of days without activity before the `actions/stale` action labels an issue. If you never want this action to label issues, set this value to `-1`.
diff --git a/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index b9fc5e7b64..7817bdf1f2 100644
--- a/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **Make sure to reference this issue in your pull request.** :sparkles: Thank you for your contribution! :sparkles:
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Replace `help-wanted` in `if: github.event.label.name == 'help-wanted'` with the label that you want to act on. If you want to act on more than one label, separate the conditions with `||`. For example, `if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` will comment whenever the `bug` or `fix me` labels are added to an issue.
    - Change the value for `body` to the comment that you want to add. GitHub flavored markdown is supported. For more information about markdown, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
diff --git a/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md b/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md
index bb1a0ca0e2..40db45ddfd 100644
--- a/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/ja-JP/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### はじめに
 
-このガイドでは、Docker Hubの`postgres`イメージを使ってサービスコンテナを設定するワークフローの例を紹介します。 このワークフローは、PostgreSQLのクライアントを作成してクライアントにデータを展開するスクリプトを実行します。 PostgreSQLクライアントを作成して展開するワークフローをテストするために、このスクリプトはクライアントのデータをコンソールに出力します。
+このガイドでは、Docker Hubの`postgres`イメージを使ってサービスコンテナを設定するワークフローの例を紹介します。 The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -47,23 +47,23 @@ name: PostgreSQL service example
 on: push
 
 jobs:
-  # コンテナジョブのラベル
+  # Label of the container job
   container-job:
-    # コンテナはLinuxベースのオペレーティングシステム内で実行しなければならない
+    # Containers must run in Linux based operating systems
     runs-on: ubuntu-latest
-    # `container-job`が実行されるDocker Hubのイメージ
+    # Docker Hub image that `container-job` executes in
     container: node:10.18-jessie
 
-    # `container-job`と実行されるサービスコンテナ
+    # Service containers to run with `container-job`
     services:
-      # サービスコンテナへのアクセスに使われるラベル
+      # Label used to access the service container
       postgres:
-        # Docker Hubのイメージ
+        # Docker Hub image
         image: postgres
-        # postgresのパスワードを提供
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # postgresが起動するまで待つヘルスチェックの設定
+        # Set health checks to wait until postgres has started
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
@@ -71,20 +71,20 @@ jobs:
           --health-retries 5
 
     steps:
-      # CIテストの実行前にリポジトリからコードのコピーをダウンロード
+      # Downloads a copy of the code in your repository before running CI tests
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # `package.json`ファイル内のすべての依存関係のクリーンインストールを実行
-      # 詳しい情報についてはhttps://docs.npmjs.com/cli/ci.htmlを参照
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # PostgreSQLクライアントを作成し、クライアントにデータを展開し、
-        # データを取り出すスクリプトを実行
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
         run: node client.js
-        # `client.js`スクリプトが新しいPostgreSQLクライアントの作成に使う環境変数
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # PostgreSQLサービスコンテナとの通信に使われるホスト名
           POSTGRES_HOST: postgres
@@ -131,21 +131,21 @@ jobs:
 
 ```yaml{:copy}
 steps:
-  # CIテストの実行前にリポジトリのコードのコピーをダウンロード
+  # Downloads a copy of the code in your repository before running CI tests
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # `package.json`ファイル中のすべての依存関係のクリーンインストールを実行
-  # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # PostgreSQLクライアントを作成し、クライアントにデータを展開し、
-    # データを取り出すスクリプトを実行
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
     run: node client.js
-    # `client.js`スクリプトが新しいPostgreSQLクライアントを作成する際に
-    # 利用する環境変数
+    # Environment variable used by the `client.js` script to create
+    # a new PostgreSQL client.
     env:
       # PostgreSQLサービスコンテナとの通信に使われるホスト名
       POSTGRES_HOST: postgres
@@ -169,46 +169,46 @@ name: PostgreSQL Service Example
 on: push
 
 jobs:
-  # ランナージョブのラベル
+  # Label of the runner job
   runner-job:
-    # サービスコンテナもしくはコンテナジョブを使う場合にはLinux環境を使わなければならない
+    # You must use a Linux environment when using service containers or container jobs
     runs-on: ubuntu-latest
 
-    # `runner-job`と実行されるサービスコンテナ
+    # Service containers to run with `runner-job`
     services:
-      # サービスコンテナへのアクセスに使われるラベル
+      # Label used to access the service container
       postgres:
-        # Docker Hubのイメージ
+        # Docker Hub image
         image: postgres
-        # postgresのパスワードを提供
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # posgresが起動するまで待つヘルスチェックの設定
+        # Set health checks to wait until postgres has started
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # サービスコンテナ上のTCPポート5432をホストにマップ
+          # Maps tcp port 5432 on service container to the host
           - 5432:5432
 
     steps:
-      # CIテストの実行前にリポジトリからコードのコピーをダウンロード
+      # Downloads a copy of the code in your repository before running CI tests
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # `package.json`ファイル内のすべての依存関係のクリーンインストールを実行
-      # 詳しい情報についてはhttps://docs.npmjs.com/cli/ci.htmlを参照
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # PostgreSQLクライアントを作成し、クライアントにデータを展開し、
-        # データを取り出すスクリプトを実行
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
         run: node client.js
-        # `client.js`スクリプトが新しいPostgreSQLクライアントの
-        # 作成に使う環境変数
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # PostgreSQLサービスコンテナとの通信に使われるホスト名
           POSTGRES_HOST: localhost
@@ -258,21 +258,21 @@ jobs:
 
 ```yaml{:copy}
 steps:
-  # CIテストの実行前にリポジトリのコードのコピーをダウンロード
+  # Downloads a copy of the code in your repository before running CI tests
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # `package.json`ファイル中のすべての依存関係のクリーンインストールを実行
-  # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # PostgreSQLクライアントを作成し、クライアントにデータを展開し、
-    # データを取り出すスクリプトを実行
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
     run: node client.js
-    # `client.js`スクリプトが新しいPostgreSQLクライアントを作成する際に
-    # 利用する環境変数
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # PostgreSQLサービスコンテナとの通信に使われるホスト名
       POSTGRES_HOST: localhost
@@ -286,9 +286,9 @@ steps:
 
 ### PostgreSQLサービスコンテナのテスト
 
-ワークフローを以下のスクリプトでテストできます。このスクリプトはPostgreSQLクライアントを作成し、いくつかのプレースホルダーデータで新しいテーブルを追加します。 そしてこのスクリプトは、PostgreSQLクライアント内に保存された値をターミナルに出力します。 スクリプトには好きな言語を使えますが、この例ではNode.jsとnpmモジュールの`pg`を使っています。 詳しい情報については[npm pgモジュール](https://www.npmjs.com/package/pg)を参照してください。
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. スクリプトには好きな言語を使えますが、この例ではNode.jsとnpmモジュールの`pg`を使っています。 詳しい情報については[npm pgモジュール](https://www.npmjs.com/package/pg)を参照してください。
 
-*client.js*を修正して、ワークフローで必要なPostgreSQLの操作を含めることができます。 この例では、スクリプトはPostgreSQLクライアントのインスタンスを作成し、テーブルを作成し、プレースホルダーデータを追加し、そしてそのデータを取り出します。
+*client.js*を修正して、ワークフローで必要なPostgreSQLの操作を含めることができます。 In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-このスクリプトは新しいPostgreSQLの`Client`を作成します。これは、パラメーターとして`host`と`port`を受け付けます。 スクリプトは環境変数の`POSTGRES_HOST`と`POSTGRES_PORT`を使って、クライアントのIPアドレスとポートを設定します。 `host`と`port`が定義されていない場合、デフォルトのホストは`localhost`で、デフォルトのポートは5432になります。
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. `host`と`port`が定義されていない場合、デフォルトのホストは`localhost`で、デフォルトのポートは5432になります。
 
-スクリプトはテーブルを作成し、そのテーブルにプレースホルダーデータを展開します。 PostgreSQLデータベースがデータを含んでいることをテストするために、スクリプトはテーブルの内容をコンソールログに出力します。
+スクリプトはテーブルを作成し、そのテーブルにプレースホルダーデータを展開します。 To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-このワークフローを実行すると、"Connect to PostgreSQL"ステップで以下のように出力され、PostgreSQLのクライアントが作成され、データが追加されたことが確認できます。
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index 21294511f8..05319ea834 100644
--- a/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/ja-JP/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ topics:
 
 ワークフローの`env`キー内のすべての変数について、自分の値を渡すようにしてください。
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -80,14 +79,14 @@ on:
     types: [ created ]
 
 env:
-  AWS_REGION: MY_AWS_REGION                   # これをお好みのAWSリージョンに設定します（us-west-1 など）
-  ECR_REPOSITORY: MY_ECR_REPOSITORY           # これを Amazon ECR リポジトリ名に設定します
-  ECS_SERVICE: MY_ECS_SERVICE                 # これを Amazon ECS サービス名に設定します
-  ECS_CLUSTER: MY_ECS_CLUSTER                 # これを Amazon ECS クラスタ名に設定します
-  ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # これを Amazon ECS タスク定義へのパスに設定します
-                                               # ファイル（aws/task-definition.json など）
-  CONTAINER_NAME: MY_CONTAINER_NAME           # これをコンテナの名前に設定します
-                                               # タスク定義の containerDefinitions セクション
+  AWS_REGION: MY_AWS_REGION                   # set this to your preferred AWS region, e.g. us-west-1
+  ECR_REPOSITORY: MY_ECR_REPOSITORY           # set this to your Amazon ECR repository name
+  ECS_SERVICE: MY_ECS_SERVICE                 # set this to your Amazon ECS service name
+  ECS_CLUSTER: MY_ECS_CLUSTER                 # set this to your Amazon ECS cluster name
+  ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # set this to the path to your Amazon ECS task definition
+                                               # file, e.g. .aws/task-definition.json
+  CONTAINER_NAME: MY_CONTAINER_NAME           # set this to the name of the container in the
+                                               # containerDefinitions section of your task definition
 
 defaults:
   run:
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -119,9 +121,9 @@ jobs:
           ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
           IMAGE_TAG: ${{ github.sha }}
         run: |
-          # Docker コンテナを作成し
-          # CR にプッシュして
-          # ECS にデプロイできるようにします。
+          # Build a docker container and
+          # push it to ECR so that it can
+          # be deployed to ECS.
           docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
           docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
           echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG"
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### 追加リソース
 
diff --git a/translations/ja-JP/content/actions/guides/index.md b/translations/ja-JP/content/actions/guides/index.md
index a014cb35fe..bcf8d87999 100644
--- a/translations/ja-JP/content/actions/guides/index.md
+++ b/translations/ja-JP/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/ja-JP/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/ja-JP/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..48b9250ef0
--- /dev/null
+++ b/translations/ja-JP/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Managing GitHub Actions with GitHub CLI
+intro: 'You can use {% data variables.product.prodname_cli %} to interact with {% data variables.product.prodname_actions %}.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### {% data variables.product.prodname_cli %}の設定方法
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### Managing {% data variables.product.prodname_actions %} with {% data variables.product.prodname_cli %}
+
+To view all available commands related to {% data variables.product.prodname_actions %}, run `gh actions`.
+
+For more information on using commands in specific scenarios, see the following procedures:
+
+- "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)"
+- "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/ja-JP/content/actions/guides/publishing-docker-images.md b/translations/ja-JP/content/actions/guides/publishing-docker-images.md
index 6e13ce0175..adac079973 100644
--- a/translations/ja-JP/content/actions/guides/publishing-docker-images.md
+++ b/translations/ja-JP/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ topics:
 
 - 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
 - 「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」
-- [{% data variables.product.prodname_registry %}で利用するためのDockerの設定](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### イメージの設定について
 
@@ -98,7 +98,6 @@ jobs:
 * `registry`: `docker.pkg.github.com`に設定しなければなりません。
 * `repository`: `OWNER/REPOSITORY/IMAGE_NAME`というフォーマットで設定しなければなりません。 たとえば、`http://github.com/octo-org/octo-repo`にある{% data variables.product.prodname_dotcom %}上に保存される`octo-image`という名前のイメージでは、`repository`オプションは`octo-org/octo-repo/octo-image`に設定しなければなりません。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -107,21 +106,23 @@ on:
 jobs:
   push_to_registry:
     name: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,7 +132,6 @@ jobs:
 
 以下のワークフローの例では、以前のセクション（「[Docker Hubへのイメージの公開](#publishing-images-to-docker-hub)」及び「[{% data variables.product.prodname_registry %}へのイメージの公開](#publishing-images-to-github-packages)」）での`build-push-action`ステップを使い、両方のレジストリにプッシュを行う1つのワークフローを作成します。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -140,26 +140,28 @@ on:
 jobs:
   push_to_registries:
     name: Push Docker image to multiple registries
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to Docker Hub
         uses: docker/build-push-action@v1
         with:
-          username: ${{ secrets.DOCKER_USERNAME }}
-          password: ${{ secrets.DOCKER_PASSWORD }}
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
           repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 上のワークフローの例は、{% data variables.product.prodname_dotcom %}リポジトリをチェックアウトし、`build-push-action`アクションを2回使ってDockerイメージをビルドしてDocker Hubと{% data variables.product.prodname_registry %}にプッシュします。 どちらのステップでも、このワークフローは`build-push-action`のオプションの[`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref)を、構築されたDockerイメージをワークフローイベントのGit参照で自動的にタグ付けするように設定します。 このワークフローは{% data variables.product.prodname_dotcom %}リリースの公開で起動されるので、どちらのレジストリの参照も、そのリリースのGitタグになります。
diff --git a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md
index b3f86606a4..a2537dcbcd 100644
--- a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ GradleでのJavaプロジェクトのためのCIワークフローの作成に
 
 また、以下の基本的な理解があれば役立ちます。
 
-- [{% data variables.product.prodname_registry %} で利用するために npm を設定する](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - 「[環境変数](/actions/reference/environment-variables)」
 - 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
 - 「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」
@@ -108,7 +108,7 @@ jobs:
 
 _build.gradle_のpublishingブロックには、{% data variables.product.prodname_registry %}を指す新しいMavenリポジトリを定義できます。  そのリポジトリの設定では、CIワークフローの実行で設定された環境変数を活用することもできます。  環境変数の`GITHUB_ACTOR`はユーザ名として利用でき、環境変数の`GITHUB_TOKEN`には`GITHUB_TOKEN`シークレットを設定できます。
 
-`GITHUB_TOKEN`は、デフォルトでリポジトリ中に存在し、ワークフローが実行されるリポジトリ中のパッケージには読み書きの権限があります。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
+{% data reusables.github-actions.github-token-permissions %}
 
 たとえば、Organizationの名前が"octocat"でリポジトリの名前が"hello-world"なら、_build.gradle_中の{% data variables.product.prodname_registry %}の設定は以下の例のようになるでしょう。
 
@@ -133,7 +133,6 @@ publishing {
 
 この設定で、`gradle publish`コマンドの実行によってパッケージをMaven Central Repositoryに公開するワークフローを作成できます。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. {% data variables.product.prodname_registry %}に公開するために` gradle publish `コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。
+1. {% data variables.product.prodname_registry %}に公開するために` gradle publish `コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
@@ -199,7 +200,6 @@ publishing {
 
 この設定で、`gradle publish`コマンドの実行によってパッケージをMaven Central Repositoryと{% data variables.product.prodname_registry %}の両方に公開するワークフローを作成できます。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. `OSSRH` Mavenリポジトリと{% data variables.product.prodname_registry %}に公開するために` gradle publish`コマンドを実行してください。 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。
+1. `OSSRH` Mavenリポジトリと{% data variables.product.prodname_registry %}に公開するために` gradle publish`コマンドを実行してください。 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md
index 7225aa9c7c..794ef4ea6d 100644
--- a/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/ja-JP/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ MavenでのJavaプロジェクトのためのCIワークフローの作成に関
 
 また、以下の基本的な理解があれば役立ちます。
 
-- [{% data variables.product.prodname_registry %} で利用するために npm を設定する](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - 「[環境変数](/actions/reference/environment-variables)」
 - 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
 - 「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」
@@ -112,9 +112,9 @@ jobs:
 
 新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/actions/reference/events-that-trigger-workflows#release)」を参照してください。
 
-このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールし、{% data variables.product.prodname_registry %}にパッケージを公開するためにMavenの_settings.xml_もセットアップします。 生成された_settings.xml_は、環境変数の`GITHUB_ACTOR`をユーザ名、`GITHUB_TOKEN`をパスワードとして使い、`github`の`id`でサーバーの認証を定義します。
+このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールし、{% data variables.product.prodname_registry %}にパッケージを公開するためにMavenの_settings.xml_もセットアップします。 生成された_settings.xml_は、環境変数の`GITHUB_ACTOR`をユーザ名、`GITHUB_TOKEN`をパスワードとして使い、`github`の`id`でサーバーの認証を定義します。 The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
 
-`GITHUB_TOKEN`は、デフォルトでリポジトリ中に存在し、ワークフローが実行されるリポジトリ中のパッケージには読み書きの権限があります。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
+{% data reusables.github-actions.github-token-permissions %}
 
 Mavenベースのプロジェクトでは、{% data variables.product.prodname_registry %}のエンドポイントを指す`github`の`id`で_pom.xml_ファイル中に配布リポジトリを作成することによって、これらの設定を利用できます。
 
@@ -137,7 +137,6 @@ Mavenベースのプロジェクトでは、{% data variables.product.prodname_r
 
 この設定で、自動的に生成された_settings.xml_を利用して{% data variables.product.prodname_registry %}にパッケージを公開するワークフローを作成できます。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 このワークフローは以下のステップを実行します。
 
@@ -173,7 +174,6 @@ jobs:
 
 _pom.xml_ファイルに、{% data variables.product.prodname_dotcom %}リポジトリとMaven Central Repositoryプロバイダの双方に対する配布管理リポジトリを確実に含めてください。 たとえば、OSSRHホスティングプロジェクトを通じてCentral Repositoryへデプロイするなら、それを`id`を`ossrh`に設定して配布管理リポジトリ内で指定し、`id`を`github`に設定して配布管理リポジトリ内で{% data variables.product.prodname_registry %}を指定することになるかもしれません。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 このワークフローは、`setup-java`アクションを2回呼びます。  実行される度に、`setup-java`アクションはMavenの_settings.xml_をパッケージの公開のために上書きします。  リポジトリの認証については、_settings.xml_ファイルは配布管理リポジトリの`id`、及びユーザ名とパスワードを参照します。
 
diff --git a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md
index e1d0817944..2cfe10d65c 100644
--- a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ Node.jsプロジェクトのためのCIワークフローの作成に関する
 
 また、以下の基本的な理解があれば役立ちます。
 
-- [{% data variables.product.prodname_registry %} で利用するために npm を設定する](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - 「[環境変数](/actions/reference/environment-variables)」
 - 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
 - 「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # npm に公開するように .npmrc ファイルを設定する
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ always-auth=true
 
 #### 宛先リポジトリへの認証
 
-ワークフローで {% data variables.product.prodname_registry %} レジストリに対して認証するには、リポジトリから `GITHUB_TOKEN` を使用できます。 これは自動的に作成され、ワークフローが実行されるリポジトリ内のパッケージに対する_読み取り_および_書き込み_権限があります。 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」を参照してください。
+ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 {% data reusables.github-actions.github-token-permissions %}
 
 パッケージを別のリポジトリに公開する場合は、宛先リポジトリ内のパッケージに書き込む権限を持つ個人アクセストークン (PAT) を使用する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
 
@@ -120,7 +120,6 @@ always-auth=true
 
 以下の例は、`GITHUB_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # .npmrc ファイルをセットアップして GitHub Packages に公開する
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # デフォルトはワークフローファイルを所有するユーザまたは Organization
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 `setup-node`アクションは、ランナー上で*.npmrc*ファイルを作成します。 `setup-node`アクションで`scope`インプットを使うと、*.npmrc*ファイルにはスコーププレフィックスが含まれます。 デフォルトでは、`setup-node`アクションは*.npmrc*ファイルのスコープを、ワークフローファイルを含むアカウントに設定します。
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # npm に公開する .npmrc ファイルを設定する
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # デフォルトはワークフローファイルを所有するユーザまたは Organization
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,13 +197,13 @@ jobs:
 
 *package.json*ファイルに{% data variables.product.prodname_dotcom %}レジストリとnpmレジストリのスコープが含まれていることを確かめてください。 たとえば、`octocat/npm-hello-world-test`リポジトリ内のパッケージを{% data variables.product.prodname_dotcom %}及びhttps://www.npmjs.com/package/@octocat/npm-hello-world-testに公開する計画をしているなら、*package.json*ファイル内の名前は`"name": "@octocat/npm-hello-world-test"`となるでしょう。
 
-ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 `GITHUB_TOKEN`は、デフォルトでリポジトリ中に存在し、ワークフローが実行されるリポジトリ中のパッケージには読み書きの権限があります。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
+ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 {% data reusables.github-actions.github-token-permissions %}
 
 `setup-node`アクションで`scope`インプットを使うと、このアクションはスコーププレフィックスを含む*.npmrc*ファイルを作成します。 デフォルトでは、`setup-node`アクションは*.npmrc*ファイル中のスコープを、ワークフローファイルを所有するユーザもしくはOrganizationに設定します。
 
 このワークフローは、`setup-node`アクションを2回呼びます。 `setup-node`アクションは、実行されるたびに*.npmrc*ファイルを上書きします。 *.npmrc*ファイルは、パッケージレジストリに対する認証を受けた操作を行えるようにしてくれるトークンを、環境変数の`NODE_AUTH_TOKEN`から参照します。 このワークフローは、環境変数の`NODE_AUTH_TOKEN`を`npm publish`コマンドが実行されるたびに設定します。初回はnpmへの公開のためのトークン（`NPM_TOKEN`）が、続いて{% data variables.product.prodname_registry %}への公開のためのトークン（`GITHUB_TOKEN`）が使われます。
 
-{% raw %}
+
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -210,28 +211,30 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # npmに公開する.npmrcファイルを設定する
-    - uses: actions/setup-node@v1
-      with:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    # npmに公開する
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # GitHub パッケージに公開する .npmrc ファイルを設定する
-    - uses: actions/setup-node@v1
-      with:
-        registry-url: 'https://npm.pkg.github.com'
-        # デフォルトはワークフローファイルを所有するユーザまたは Organization
-        scope: '@octocat'
-    # GitHub パッケージに公開する
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index ccc0e8af95..dbd08f9df6 100644
--- a/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 3. {% data reusables.actions.make-workflow-file %}
 4. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. Customize the parameters in your workflow file:
    - In `github.event.project_card.column_id == '12345678'`, replace `12345678` with the ID of the column where you want to un-label issues and pull requests that are moved there.
 
diff --git a/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md b/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md
index 9c6cd8686e..6159249831 100644
--- a/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:20 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `assignees` to the list of {% data variables.product.prodname_dotcom %} usernames that you want to assign to the issue.
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 63e17f8877..c5de56811f 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -53,7 +53,7 @@ Enterprise の管理者が Organization にランナーグループへのアク
 
    **Warning**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
@@ -85,7 +85,7 @@ Enterprise は、セルフホストランナーをグループに追加して、
 
    **Warning**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index 3930a91b98..7078ecf96e 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -13,8 +13,10 @@ type: tutorial
 defaultPlatform: linux
 ---
 
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### {{ site.data.variables.product.prodname_dotcom }}を使ったセルフホストランナーのステータスのチェック
 
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index c1b9982dd3..954bc4b19e 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -66,7 +66,7 @@ Organizationからセルフホストランナーを削除するには、Organiza
 
 {% if currentVersion == "free-pro-team@latest" %}
 セルフホストランナーを Enterprise アカウントから削除するには、Enterprise のオーナーである必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 セルフホストランナーを
 {% data variables.product.product_location %} の Enterprise レベルで削除するには、サイト管理者である必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。
 {% endif %}
diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md
index 81d87042ee..c9bbb51524 100644
--- a/translations/ja-JP/content/actions/index.md
+++ b/translations/ja-JP/content/actions/index.md
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">コード例</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="検索コードの例" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">詳細を表示 {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">検索結果はありません <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">フィルタに適合する例がないようです。<br>別のフィルタを試すか、コード例を追加してください</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">コード例を追加する方法 {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index 852c92e646..98a52d3649 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -430,7 +430,7 @@ jobs:
           POSTGRES_PASSWORD: ""
         ports:
           - 5432:5432
-        # ヘルスチェックを追加
+        # Add a health check
         options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
 
     steps:
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index deef34ef09..0abdf7e6ad 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ type: how_to
 
 ### ワークフロー テンプレートの作成
 
-ワークフローテンプレートは、Organizationの `.github` リポジトリへの書き込みアクセス権を持つユーザが作成できます。 その後、ワークフローを作成する権限を持つOrganizationのメンバーがテンプレートを使用できます。 ワークフロー テンプレートを使用すると、Organizationのパブリック リポジトリに新しいワークフローを作成できます。テンプレートを使用してプライベートリポジトリにワークフローを作成するには、OrganizationがエンタープライズプランまたはGitHub Oneプランの一部である必要があります。
+ワークフローテンプレートは、Organizationの `.github` リポジトリへの書き込みアクセス権を持つユーザが作成できます。 その後、ワークフローを作成する権限を持つOrganizationのメンバーがテンプレートを使用できます。 Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise plan.
 
 この手順では、ワークフロー テンプレートとメタデータ ファイルを作成する方法を示します。 メタデータ ファイルには、ユーザが新しいワークフローを作成するときにテンプレートがどのように表示されるかについて説明します。
 
 1. 存在しない場合は、Organization内で`.github`という名前の新しいパブリック リポジトリを作成します。
-1. `workflow-templates`という名前のディレクトリを作成します。
-1. `workflow-templates` ディレクトリ内に新しいワークフローファイルを作成します。
+2. `workflow-templates`という名前のディレクトリを作成します。
+3. `workflow-templates` ディレクトリ内に新しいワークフローファイルを作成します。
 
    リポジトリのデフォルトブランチを参照する必要がある場合は、 `$default-branch` プレースホルダを使用できます。 テンプレートを使用してワークフローを作成すると、プレースホルダはリポジトリのデフォルトブランチの名前に自動的に置き換えられます。
 
@@ -52,7 +52,7 @@ type: how_to
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. `workflow-templates` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば`octo-organization-ci.properties.json`という名前のこのファイルには 、`octo-organization-ci.yml`という名前のワークフローファイルのメタデータが含まれています。
+4. `workflow-templates` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば`octo-organization-ci.properties.json`という名前のこのファイルには 、`octo-organization-ci.yml`という名前のワークフローファイルのメタデータが含まれています。
    ```yaml
    {
        "name": "Octo Organization Workflow",
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..a41d459b53
--- /dev/null
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: Approving workflow runs from public forks
+intro: 'When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve any workflow runs.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+Forks of public repositories can submit pull requests that propose changes to a repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests are not run automatically if they are received from first-time contributors, and must be approved first.
+
+Maintainers with write access to the repository can use the following procedure to review and run workflows on pull requests from first-time contributors. After a contributor has at least one pull request merged into a project's repository, any future pull requests from that contributor's fork will automatically run workflows.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
+1. If you are comfortable with running workflows on the pull request branch, return to the {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
+
+   ![Approve and run workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index b656bd9247..a27d69a520 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: ワークフローの無効化と有効化
-intro: '{% data variables.product.prodname_dotcom %} または REST API を使用して、ワークフローを無効化したり、再度有効化したりすることができます。'
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。 REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しい情報については、「[Actions REST API](/rest/reference/actions#workflows)」を参照してください。
+ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。
 
 ワークフローを一時的に無効にすると、多くのシナリオで役立つことがあります。 以下は、ワークフローを無効すると便利な場合の例の一部です。
 
@@ -27,7 +27,9 @@ versions:
 
 {% endwarning %}
 
-### ワークフローの無効化
+### Disabling and enabling workflows with the {% data variables.product.prodname_dotcom %} UI
+
+#### ワークフローの無効化
 
 ワークフローを手動で無効にして、ワークフロー実行が行われないようにすることができます。 無効にしたワークフローは削除されず、再度有効にすることができます。
 
@@ -37,7 +39,7 @@ versions:
 1. {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![アクションケバブメニュー](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. [**Disable workflow**] をクリックします。 ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)無効化されたワークフローには、そのステータスを示すために {% octicon "stop" aria-label="The stop icon" %} のマークが付けられます。 ![無効なワークフローをリストするアクション](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### ワークフローの有効化
+#### ワークフローの有効化
 
 以前、無効化したワークフローを再度有効化することができます。
 
@@ -45,3 +47,23 @@ versions:
 {% data reusables.repositories.actions-tab %}
 1. 左サイドバーで、有効にするワークフローをクリックします。 ![無効なワークフローを選択するアクション](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. [**Enable workflow**] をクリックします。 ![ワークフローを有効にするアクション](/assets/images/help/repository/actions-enable-workflow.png)
+
+### Disabling and enabling workflows with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### Disabling and enabling workflows through the REST API
+
+REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しい情報については、「[Actions REST API](/rest/reference/actions#workflows)」を参照してください。
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 8048c2809b..1c847d4c02 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} デフォルトでは、{% data variables.product.product_name %} はビルドログと成果物を 90 日間保存し、リポジトリのタイプに応じてこの保持期間をカスタマイズできます。 詳しい情報については、「[リポジトリ内の GitHub Actionsの成果物とログの保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)」を参照してください。{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} には、完全なビルドログと成果物が 90 日間保存されます。{% endif %}
 
+### Download artifacts with the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### Download artifacts with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+{% data variables.product.prodname_cli %} will download each artifact into separate directories based on the artifact name. If only a single artifact is specified, it will be extracted into the current directory.
+
+To download all artifacts generated by a workflow run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run download <em>run-id</em>
+```
+
+To download a specific artifact from a run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. Replace `artifact-name` with the name of the artifact that you want to download.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+You can specify more than one artifact.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+To download specific artifacts across all runs in a repository, use the `run download` subcommand.
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/index.md b/translations/ja-JP/content/actions/managing-workflow-runs/index.md
index d59d139e14..7976301312 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/index.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index 1c2270791a..d8a9c686e4 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: ワークフローの手動実行
-intro: 'ワークフローが「workflow_dispatch」イベントで実行されるように設定されている場合、REST API を使用するか、{% data variables.product.prodname_dotcom %} の [Actions] タブからワークフローを実行できます。'
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -28,6 +28,40 @@ versions:
 1. ワークフロー実行の一覧の上にある**Run workflow（ワークフローの実行）**を選択します。 ![アクション ワークフローのディスパッチ](/assets/images/actions-workflow-dispatch.png)
 1. ワークフローを実行するブランチを選択し、ワークフローで使用される入力パラメータを入力します。 **Run workflow（ワークフローの実行）**をクリックします。 ![アクションはワークフローを手動で実行します](/assets/images/actions-manually-run-workflow.png)
 
+### Running a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+You can also pass inputs as JSON by using standard input.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
+
 ### REST API を使用してワークフローを実行する
 
 REST API を使用する場合は、 `inputs`と`ref`をリクエストボディのパラメータとして設定してください。 入力を省略すると、ワークフロー ファイルで定義されているデフォルト値が使用されます。
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md
index 5152476aa6..d7918995a4 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Re-run a workflow using the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. ワークフローの右上隅にある [**Re-run jobs**] ドロップダウンメニューを使用して、[**Re-run all jobs**] を選択します。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### Re-run a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run.  If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 76fe8a605c..3b88fcf7b8 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. **Artifacts（成果物）**の下で、
-削除したい成果物の隣の{% octicon "trashcan" aria-label="The trashcan icon" %}をクリックしてください。
+削除したい成果物の隣の{% octicon "trash" aria-label="The trash icon" %}をクリックしてください。
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index 0d90ceba5c..d69580a6d1 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ versions:
 1. 右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。 ![Delete all logs](/assets/images/help/repository/delete-all-logs.png)ログが削除されると、[**Delete all logs**] ボタンが削除され、ワークフローの実行にログファイルが残っていないことを示します。
 {% endif %}
+
+### Viewing logs with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To view the log for a specific job, use the `run view` subcommand. Replace `run-id` with the ID of run that you want to view logs for. {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a job from the run. If you don't specify `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run, and then returns another interactive menu for you to choose a job from the run.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+You can also use the `--job` flag to specify a job ID. Replace `job-id` with the ID of the job that you want to view logs for.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+You can use `grep` to search the log. For example, this command will return all log entries that contain the word `error`.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+To filter the logs for any failed steps, use `--log-failed` instead of `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index e25b103c63..549f6de6a4 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Viewing workflow run history on {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### Viewing workflow run history with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+#### Viewing recent workflow runs
+
+To list the recent workflow runs, use the `run list` subcommand.
+
+```shell
+gh run list
+```
+
+To specify the maximum number of runs to return, you can use the `-L` or `--limit` flag . 省略値は、`10` です。
+
+```shell
+gh run list --limit 5
+```
+
+To only return runs for the specified workflow, you can use the `-w` or `--workflow` flag.  Replace `workflow` with either the workflow name, workflow ID, or workflow file name. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### Viewing details for a specific workflow run
+
+To display details for a specific workflow run, use the `run view` subcommand. Replace `run-id` with the ID of the run that you want to view. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+To include job steps in the output, use the `-v` or `--verbose` flag.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+To view details for a specific job in the run, use the `-j` or `--job` flag.  Replace `job-id` with the ID of the job that you want to view.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+To view the full log for a job, use the `--log` flag.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Use the `--exit-status` flag to exit with a non-zero status if the run failed. 例:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md
index d26f9d99d3..1d8d6b5037 100644
--- a/translations/ja-JP/content/actions/quickstart.md
+++ b/translations/ja-JP/content/actions/quickstart.md
@@ -60,7 +60,7 @@ Committing the workflow file to a branch in your repository triggers the `push`
 1. 左のサイドバーで、表示させたいワークフローをクリックしてください。
 
    ![左サイドバーのワークフローのリスト](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png)
-1. From the list of workflow runs, click the name of the run you want to see.
+1. ワークフローの実行リストから、表示させたい実行の名前をクリックしてください。
 
    ![ワークフローの実行の名前](/assets/images/help/repository/actions-quickstart-run-name.png)
 1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
diff --git a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md
index 3f7ade91bf..2eb020d4a0 100644
--- a/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/ja-JP/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ versions:
 
 ### ワークフロー内での`GITHUB_TOKEN`の利用
 
-`GITHUB_TOKEN`シークレットを利用するためには、ワークフローファイル内で参照しなければなりません。 トークンの利用には、そのトークンを要求するアクションへ入力としてそのトークンを渡すことや、認証を受けた{% data variables.product.prodname_dotcom %} APIコールの発行が含まれます。
+You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% data variables.product.prodname_dotcom %} API request.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. 詳しい情報については「[`GITHUB_TOKEN`の権限](#permissions-for-the-github_token)」を参照してください。
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### `GITHUB_TOKEN`を入力として渡す例
+#### Example 1: passing the `GITHUB_TOKEN` as an input
 
 以下のワークフローの例では[labeler action](https://github.com/actions/labeler)を使用しています。これには、`repo-token`入力パラメータの値として`GITHUB_TOKEN`を渡すことが必要です。
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### REST APIの呼び出しの例
+#### Example 2: calling the REST API
 
 `GITHUB_TOKEN`を使って、認証されたAPIコールを発行できます。 以下のワークフローの例では、{% data variables.product.prodname_dotcom %} REST APIを使ってIssueを作成しています。
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,29 +88,68 @@ versions:
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_."
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### `GITHUB_TOKEN`の権限
 
 {% data variables.product.prodname_github_apps %} が各権限でアクセスできる API エンドポイントについては、「[{% data variables.product.prodname_github_app %} の権限](/rest/reference/permissions-required-for-github-apps)」を参照してください。
 
-| 権限                  | アクセスタイプ   | フォークしたリポジトリからのアクセス |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an enterprise, organization, or repository 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 {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-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 "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
+
+| スコープ                | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
+| ------------------- | ------------------------------------ | ------------------------------------ | --------------------------------------- |
+| actions             | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| checks              | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| contents            | 読み取り/書き込み                            | 読み取り                                 | 読み取り                                    |
+| deployments         | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| issues              | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| メタデータ               | 読み取り                                 | 読み取り                                 | 読み取り                                    |
+| パッケージ               | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| pull requests       | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| repository projects | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| security events     | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+| statuses            | 読み取り/書き込み                            | なし                                   | 読み取り                                    |
+{% else %}
+| スコープ                | アクセスタイプ   | フォークしたリポジトリからのアクセス |
 | ------------------- | --------- | ------------------ |
 | actions             | 読み取り/書き込み | 読み取り               |
 | checks              | 読み取り/書き込み | 読み取り               |
 | contents            | 読み取り/書き込み | 読み取り               |
 | deployments         | 読み取り/書き込み | 読み取り               |
 | issues              | 読み取り/書き込み | 読み取り               |
-| metadata            | 読み取り      | 読み取り               |
-| packages            | 読み取り/書き込み | 読み取り               |
+| メタデータ               | 読み取り      | 読み取り               |
+| パッケージ               | 読み取り/書き込み | 読み取り               |
 | pull requests       | 読み取り/書き込み | 読み取り               |
 | repository projects | 読み取り/書き込み | 読み取り               |
 | statuses            | 読み取り/書き込み | 読み取り               |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### Modifying the permissions for the `GITHUB_TOKEN`
+
+You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access.
+
+You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "Set up job" section of the workflow run log. 詳しい情報については、「[ワークフロー実行ログを使用する](/actions/managing-workflow-runs/using-workflow-run-logs)」を参照してください。
+
+You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
+
+{% data reusables.github-actions.forked-write-permission %}
+
+The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
+
+For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+
+##### How the permissions are calculated for a workflow job
+
+The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
+
+#### Granting additional permissions
+{% endif %}
+
 `GITHUB_TOKEN`で利用できない権限を要求するトークンが必要な場合は、個人アクセストークンを生成して、それをリポジトリのシークレットに設定できます。
 
 1. リポジトリに対して適切な権限を持つトークンを利用もしくは生成してください。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
diff --git a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index 5d15a90421..c106e10254 100644
--- a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ env:
 | コンテキスト名    | 種類       | 説明                                                                                                                                                                     |
 | ---------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `github`   | `オブジェクト` | ワークフロー実行に関する情報。 詳しい情報については、「[`github` コンテキスト](#github-context)」を参照してください。                                                                                              |
-| `env`      | `オブジェクト` | ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 詳しい情報については[`env`コンテキスト](#env-context)を参照してください。                                                                                       |
+| `env`      | `オブジェクト` | ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 For more information, see [`env` context](#env-context).                                                                              |
 | `job`      | `オブジェクト` | 現在実行中のジョブに関する情報。 詳しい情報については、「[`job` コンテキスト](#job-context)」を参照してください。                                                                                                   |
 | `steps`    | `オブジェクト` | このジョブで実行されているステップに関する情報。 詳しい情報については、「[`steps` コンテキスト](#steps-context)」を参照してください。                                                                                       |
 | `runner`   | `オブジェクト` | 現在のジョブを実行しているランナーに関する情報。 詳しい情報については[`runner`コンテキスト](#runner-context)を参照してください。                                                                                         |
@@ -93,11 +93,11 @@ env:
 | `github.action`           | `string` | 現在実行中のアクションの名前。 {% data variables.product.prodname_dotcom %}は、現在のステップがスクリプトを実行する際に、特殊なキャラクターを削除するか、`run`という名前を使います。  同じジョブの中で同じアクションを複数回使う場合、名前には順番に番号が加えられます。  たとえば、実行する最初のスクリプトの名前は`run1`で、2番目のスクリプトの名前は`run2`というようになります。 同様に、`actions/checkout`の2回目の呼び出しは`actionscheckout2`となります。 |
 | `github.action_path`      | `string` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルに簡単にアクセスできます。 この属性は、複合実行ステップアクションでのみサポートされています。                                                                                                                                                                                        |
 | `github.actor`            | `string` | ワークフローの実行を開始したユーザのログイン。                                                                                                                                                                                                                                                              |
-| `github.base_ref`         | `string` | ワークフローの実行における `base_ref` またはPull Requestのターゲットブランチ。 このプロパティは、ワークフローの実行をトリガーしたイベントが `pull_request` の場合のみ使用できます。                                                                                                                                                                       |
+| `github.base_ref`         | `string` | ワークフローの実行における `base_ref` またはPull Requestのターゲットブランチ。 This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                   |
 | `github.event`            | `オブジェクト` | webhook ペイロードの完全なイベント。 詳しい情報については、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows/)」を参照してください。 このコンテキストを使用して、イベントの個々のプロパティにアクセスできます。                                                                                                                                    |
 | `github.event_name`       | `string` | ワークフローの実行をトリガーしたイベントの名前。                                                                                                                                                                                                                                                             |
 | `github.event_path`       | `string` | ランナー上の完全なイベントwebhookペイロードへのパス。                                                                                                                                                                                                                                                       |
-| `github.head_ref`         | `string` | ワークフローの実行における `head_ref` またはPull Requestのソースブランチ。 このプロパティは、ワークフローの実行をトリガーしたイベントが `pull_request` の場合のみ使用できます。                                                                                                                                                                         |
+| `github.head_ref`         | `string` | ワークフローの実行における `head_ref` またはPull Requestのソースブランチ。 This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                     |
 | `github.job`              | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。                                                                                                                                                                                                 |
 | `github.ref`              | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 ブランチの場合は `refs/heads/<branch_name>` の形式で、タグの場合は `refs/tags/<tag_name>` です。                                                                                                                                                                |
 | `github.repository`       | `string` | 所有者およびリポジトリの名前。 `Codertocat/Hello-World`などです。                                                                                                                                                                                                                                        |
@@ -323,7 +323,7 @@ env:
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-`string` の値を、変数 `replaceValueN` で置換します。 `string` の変数は、`{N}` という構文で指定します。ここで `N` は整数です。 少なくとも、`replaceValue` と `string` を 1 つ指定する必要があります。 使用できる変数 (`replaceValueN`) の数に制限はありません。 中括弧はダブルスペースでエスケープします。
+`string` の値を、変数 `replaceValueN` で置換します。 `string` の変数は、`{N}` という構文で指定します。ここで `N` は整数です。 少なくとも、`replaceValue` と `string` を 1 つ指定する必要があります。 使用できる変数 (`replaceValueN`) の数に制限はありません。 Escape curly braces using double braces.
 
 ##### サンプル
 
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
diff --git a/translations/ja-JP/content/actions/reference/environment-variables.md b/translations/ja-JP/content/actions/reference/environment-variables.md
index 9ebd71d378..a0accf9570 100644
--- a/translations/ja-JP/content/actions/reference/environment-variables.md
+++ b/translations/ja-JP/content/actions/reference/environment-variables.md
@@ -58,6 +58,7 @@ jobs:
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
 | `GITHUB_JOB`         | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                              |
 | `GITHUB_ACTION`      | アクションの一意の識別子 (`id`)。                                                                                                                                                                                                                                                            |
+| `GITHUB_ACTION_PATH` | アクションが置かれているパス。 You can use this path to access files located in the same repository as your action. This variable is only supported in composite run steps actions.                                                                                                            |
 | `GITHUB_ACTIONS`     | {% data variables.product.prodname_actions %}がワークフローを実行しているときは常に`true`に設定されます。 この変数は、テストがローカルで実行されているときと、{% data variables.product.prodname_actions %}によって実行されているときを区別するために利用できます。                                                                                              |
 | `GITHUB_ACTOR`       | ワークフローを開始するユーザまたはアプリの名前。 `octocat`などです。                                                                                                                                                                                                                                         |
 | `GITHUB_REPOSITORY`  | 所有者およびリポジトリの名前。 `octocat/Hello-World`などです。                                                                                                                                                                                                                                      |
@@ -68,9 +69,9 @@ jobs:
 | `GITHUB_REF`         | ワークフローをトリガーしたブランチまたはタグref。 たとえば、`refs/heads/feature-branch-1`です。 イベントタイプのブランチもタグも利用できない場合、変数は存在しません。                                                                                                                                                                            |
 | `GITHUB_HEAD_REF`    | Pull Requestのイベントに対してのみ設定されます。 headブランチの名前です。                                                                                                                                                                                                                                   |
 | `GITHUB_BASE_REF`    | Pull Requestのイベントに対してのみ設定されます。 ベースブランチの名前です。                                                                                                                                                                                                                                    |
-| `GITHUB_SERVER_URL`  | {% data variables.product.product_name %} サーバーの URL を返します。 For example: `https://github.com`.                                                                                                                                                                                   |
-| `GITHUB_API_URL`     | API URL を返します。 For example: `https://api.github.com`.                                                                                                                                                                                                                           |
-| `GITHUB_GRAPHQL_URL` | グラフ QL API の URL を返します。 For example: `https://api.github.com/graphql`.                                                                                                                                                                                                          |
+| `GITHUB_SERVER_URL`  | {% data variables.product.product_name %} サーバーの URL を返します。 For example: `https://{% data variables.product.product_url %}`.                                                                                                                                                     |
+| `GITHUB_API_URL`     | API URL を返します。 For example: `{% data variables.product.api_url_code %}`.                                                                                                                                                                                                        |
+| `GITHUB_GRAPHQL_URL` | グラフ QL API の URL を返します。 For example: `{% data variables.product.graphql_url_code %}`.                                                                                                                                                                                           |
 
 {% tip %}
 
@@ -84,10 +85,6 @@ jobs:
 
 ### 環境変数の命名規則
 
-{% note %}
-
-**ノート:** {% data variables.product.prodname_dotcom %}は環境変数のプレフィックスの`GITHUB_`を、{% data variables.product.prodname_dotcom %}の内部的な利用のために予約しています。 `GITHUB_`プレフィックスを使用して環境変数またはシークレットを設定すると、エラーになります。
-
-{% endnote %}
+When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
 
 ファイルシステム上の場所を指すように設定した新しい環境変数がある場合は、`_PATH`サフィックスを指定する必要があります。 デフォルトの変数`HOME`と`GITHUB_WORKSPACE`は、「home」および「workspace」という言葉で最初から場所であることがわかっているため、この規則の例外です。
diff --git a/translations/ja-JP/content/actions/reference/environments.md b/translations/ja-JP/content/actions/reference/environments.md
index 60dda74e8d..0d58eab02a 100644
--- a/translations/ja-JP/content/actions/reference/environments.md
+++ b/translations/ja-JP/content/actions/reference/environments.md
@@ -48,6 +48,12 @@ Environment protection rules and environment secrets are only available on publi
 
 環境に保存されたシークレットは、その環境を参照するワークフロージョブからのみ利用できます。 環境が承認を必要とするなら、ジョブは必須のレビュー担当者の一人が承認するまで環境のシークレットにアクセスできません。 シークレットに関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
 
+{% note %}
+
+**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level as security as repository and organization secrets. 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)」を参照してください。
+
+{% endnote %}
+
 ### 環境の作成
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -71,6 +77,9 @@ Environment protection rules and environment secrets are only available on publi
 
 ワークフローが環境を参照する場合、その環境はリポジトリのデプロイメントに現れます。 現在及び以前のデプロイメントの表示に関する詳細については「[デプロイメント履歴の表示](/developers/overview/viewing-deployment-history)」を参照してください。
 
+### Using concurrency to serialize deployments in an environment
+You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#concurrency)」を参照してください。
+
 ### 環境の削除
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -80,7 +89,7 @@ Environment protection rules and environment secrets are only available on publi
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. 削除したい環境の隣の{% octicon "trashcan" aria-label="The trashcan icon" %}をクリックしてください。
+1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
 2. **I understand, delete this environment（分かりました、この環境を削除してください）**をクリックしてください。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
diff --git a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md
index c11f81780b..13cd6b35de 100644
--- a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        echo "- in ${{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          echo "- in ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ Not all webhook events trigger workflows. For the complete list of available web
 
 {% data reusables.github-actions.branch-requirement %}
 
-| webhook イベントのペイロード                                 | アクティビティタイプ                                                                                   | `GITHUB_SHA`      | `GITHUB_REF` |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ----------------- | ------------ |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
+| webhook イベントのペイロード                                 | アクティビティタイプ                                                    | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------------- | ------------------------------------------------------------- | ----------------- | ------------ |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-たとえば、チェック実行が `rerequested` または `requested_action` だったときにワークフローを実行する例は、次のとおりです。
+For example, you can run a workflow when a check run has been `rerequested` or `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ on:
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**Note:** The `prereleased` type will not trigger for pre-releases published from draft releases, but the `published` type will trigger. If you want a workflow to run when stable *and* pre-releases publish, subscribe to `published` instead of `released` and `prereleased`.
+
+{% endnote %}
+
 #### `status`
 
 Git コミットのステータスが変更された、それによって `status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[ステータス](/rest/reference/repos#statuses)」を参照してください。
diff --git a/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md
index 6f8926dccf..4a04ebe4bd 100644
--- a/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/ja-JP/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### システムパスの追加
diff --git a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md
index d9cb2f9b4e..8c7614d685 100644
--- a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -110,8 +110,8 @@ on:
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
@@ -128,7 +128,7 @@ When all the path names match patterns in `paths-ignore`, the workflow will not
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
 #### パスを含む例
@@ -139,7 +139,7 @@ on:
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
 #### パスの除外
@@ -160,8 +160,8 @@ on:
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
 #### Git diffの比較
@@ -187,6 +187,32 @@ on:
 
 cron構文に関する詳しい情報については、「[ワークフローをトリガーするイベント](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)」を参照してください。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `権限`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。
+
+You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify.  For more information, see [`jobs.<job_id>.permissions`](#jobsjob_idpermissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### サンプル
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will apply to all jobs in the workflow. All permissions are granted read access.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
+
 ### `env`
 
 ワークフロー中のすべてのジョブのステップから利用できる環境変数の`map`です。 1つのジョブのステップ、あるいは1つのステップからだけ利用できる環境変数を設定することもできます。 詳しい情報については「[`jobs.<job_id>.env`](#jobsjob_idenv)」及び「[`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv)を参照してください。
@@ -221,6 +247,18 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the `github` context. 式に関する詳しい情報については「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。
+
+You can also specify `concurrency` at the job level. For more information, see [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs`
 
 1つのワークフロー実行は、1つ以上のジョブからなります。 デフォルトでは、ジョブは並行して実行されます。 ジョブを逐次的に実行するには、`jobs.<job_id>.needs`キーワードを使用して他のジョブに対する依存関係を定義します。
@@ -339,6 +377,34 @@ runs-on: [self-hosted, linux]
 
 詳しい情報については「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)」及び「[ワークフロー内でのセルフホストランナーの利用](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)」を参照してください。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。
+
+By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](#permissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### サンプル
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access.
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 ### `jobs.<job_id>.environment`
 
@@ -347,10 +413,11 @@ runs-on: [self-hosted, linux]
 環境は、環境の`name`だけで、あるいは`name` and `url`を持つenvironmentオブジェクトとして渡すことができます。 デプロイメントAPIでは、このURLは`environment_url`にマップされます。 デプロイメントAPIに関する詳しい情報については「[デプロイメント](/rest/reference/repos#deployments)」を参照してください。
 
 ##### 1つの環境名を使う例
-
+{% raw %}
 ```yaml
 environment: staging_environment
 ```
+{% endraw %}
 
 ##### 環境名とURLを使う例
 
@@ -372,6 +439,25 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other.
+
+{% endnote %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. 式に関する詳しい情報については「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。
+
+You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
 ジョブからの出力の`map`です。 ジョブの出力は、そのジョブに依存しているすべての下流のジョブから利用できます。 ジョブの依存関係の定義に関する詳しい情報については[`jobs.<job_id>.needs`](#jobsjob_idneeds)を参照してください。
@@ -387,20 +473,20 @@ environment:
 jobs:
   job1:
     runs-on: ubuntu-latest
-    # ステップの出力をジョブの出力にマップ
+    # Map a step output to a job output
     outputs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
@@ -470,14 +556,14 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
@@ -609,11 +695,11 @@ jobs:
 ```
 
 {% if currentVersion == "free-pro-team@latest" %}
-##### {% data variables.product.prodname_github_container_registry %} の使用例
+##### Example using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-{% data variables.product.prodname_github_container_registry %} の Docker イメージ。
+A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
 
 ```yaml
 jobs:
@@ -639,7 +725,9 @@ jobs:
 
 #### ワークフローとは異なるプライベートリポジトリ内でのアクションの使用例
 
-ワークフローはプライベートリポジトリをチェックアウトし、アクションをローカルで参照する必要があります。
+ワークフローはプライベートリポジトリをチェックアウトし、アクションをローカルで参照する必要があります。 Generate a personal access token and add the token as an encrypted secret. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
 
 {% raw %}
 ```yaml
@@ -651,7 +739,7 @@ jobs:
         with:
           repository: octocat/my-private-repo
           ref: v1.0
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
           path: ./.github/actions/my-private-repo
       - name: Run my action
         uses: ./.github/actions/my-private-repo/my-action
@@ -899,7 +987,7 @@ strategy (戦略) によって、ジョブのビルドマトリクスが作成
 
 #### 複数のバージョンの Node.js を使用して実行する例
 
-設定オプションに配列を指定すると、マトリクスを指定できます。 たとえばランナーがNode.jsのバージョン6、8、10,をサポートしている場合、これらのバージョンの配列を`matrix`で指定できます。
+設定オプションに配列を指定すると、マトリクスを指定できます。 たとえばランナーがNode.jsのバージョン10、12、14,をサポートしている場合、これらのバージョンの配列を`matrix`で指定できます。
 
 この例では、`node`キーにNode.jsの3つのバージョンの配列を設定することによって、3つのジョブのマトリクスを作成します。 このマトリックスを使用するために、この例では`matrix.node`コンテキストプロパティを`setup-node`アクションの入力パラメータである`node-version`に設定しています。 その結果、3 つのジョブが実行され、それぞれが異なるバージョンのNode.js を使用します。
 
@@ -907,12 +995,12 @@ strategy (戦略) によって、ジョブのビルドマトリクスが作成
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
-  # GitHubホストランナーで使われるnodeのバージョンの設定
-  - uses: actions/setup-node@v1
+  # Configures the node version used on GitHub-hosted runners
+  - uses: actions/setup-node@v2
     with:
-      # 設定するNode.jsのバージョン
+      # The Node.js version to configure
       node-version: ${{ matrix.node }}
 ```
 {% endraw %}
@@ -933,10 +1021,10 @@ steps:
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
@@ -948,7 +1036,7 @@ steps:
 
 #### 組み合わせに追加の値が含まれる例
 
-既存のビルドマトリクスジョブに、設定オプションを追加できます。 たとえば、`windows-latest` を使うジョブで`node` のバージョン 4 を実行しているときに、`npm` の特定のバージョンを使いたい場合は、`include` を使って追加のオプションを指定できます。
+既存のビルドマトリクスジョブに、設定オプションを追加できます。 たとえば、`windows-latest` を使うジョブで`node` のバージョン 8 を実行しているときに、`npm` の特定のバージョンを使いたい場合は、`include` を使って追加のオプションを指定できます。
 
 {% raw %}
 ```yaml
@@ -956,29 +1044,29 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 2
+      # includes a new variable of npm with a value of 6
       # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
 #### 新しい組み合わせを含む例
 
-`include`を使って新しいジョブを追加し、マトリックスを構築できます。 マッチしなかったincludeの設定があれば、マトリックスに追加されます。 たとえば、`node`のバージョン12を使って複数のオペレーティングシステム上でビルドを行い、追加で実験的なジョブをUbuntu上でnodeバージョン13で行いたいなら、`include`を使ってこの追加のジョブを指定できます。
+`include`を使って新しいジョブを追加し、マトリックスを構築できます。 マッチしなかったincludeの設定があれば、マトリックスに追加されます。 たとえば、`node`のバージョン14を使って複数のオペレーティングシステム上でビルドを行い、追加で実験的なジョブをUbuntu上でnodeバージョン15で行いたいなら、`include`を使ってこの追加のジョブを指定できます。
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -994,11 +1082,11 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # excludes node 4 on macOS
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
@@ -1033,7 +1121,7 @@ strategy:
 
 #### 失敗した特定のマトリックスジョブがワークフローの実行を失敗させないようにする例
 
-ジョブマトリックス中の特定のジョブが失敗しても、ワークフローの実行が失敗にならないようにすることができます。 たとえば、`node`が`13`に設定された実験的なジョブが失敗しても、ワークフローの実行を失敗させないようにしたいとしましょう。
+ジョブマトリックス中の特定のジョブが失敗しても、ワークフローの実行が失敗にならないようにすることができます。 たとえば、`node`が`15`に設定された実験的なジョブが失敗しても、ワークフローの実行を失敗させないようにしたいとしましょう。
 
 {% raw %}
 ```yaml
@@ -1042,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -1064,7 +1152,7 @@ strategy:
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -1079,7 +1167,7 @@ jobs:
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
@@ -1181,7 +1269,7 @@ services:
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index d8883d7ad4..fb99fe7abd 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ For the overall list of included tools for each runner operating system, see the
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ For the overall list of included tools for each runner operating system, see the
 
 リクエストしたいツールがある場合、[actions/virtual-environments](https://github.com/actions/virtual-environments) で Issue を開いてください。 このリポジトリには、ランナーに関するすべての主要なソフトウェア更新に関するお知らせも含まれています。
 
+#### Installing additional software
+
+You can install additional software on {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Customizing GitHub-hosted runners](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
 ### IP アドレス
 
 {% note %}
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..fa8b92c9d6
--- /dev/null
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Customizing GitHub-hosted runners
+intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow.
+
+To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+
+This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner.
+
+### Installing software on Ubuntu runners
+
+The following example demonstrates how to install an `apt` package as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**Note:** Always run `sudo apt-get update` before installing a package. In case the `apt` index is stale, this command fetches and re-indexes any available packages, which helps prevent package installation failures.
+
+{% endnote %}
+
+### Installing software on macOS runners
+
+The following example demonstrates how to install Brew packages and casks as part of a job.
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### Installing software on Windows runners
+
+The following example demonstrates how to use [Chocolatey](https://community.chocolatey.org/packages) to install the {% data variables.product.prodname_dotcom %} CLI as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/index.md b/translations/ja-JP/content/actions/using-github-hosted-runners/index.md
index 681269a253..fb91ee9e64 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/index.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% link_in_list /about-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/ja-JP/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/ja-JP/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..ecd175c68c
--- /dev/null
+++ b/translations/ja-JP/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Advanced Security のライセンスについて
+intro: 'You need a license to use {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### {% data variables.product.prodname_GH_advanced_security %} のライセンスについて
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. {% data variables.product.prodname_GH_advanced_security %} に関する詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください。
+
+{% data reusables.advanced-security.license-overview %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for {% data variables.product.product_name %}, contact {% data variables.contact.contact_enterprise_sales %}. To enable {% data variables.product.prodname_GH_advanced_security %}, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your appliance](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### {% data variables.product.prodname_GH_advanced_security %} のコミッター番号について
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### {% data variables.product.prodname_GH_advanced_security %} のライセンス利用を管理する
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+Enterprise アカウントが所有する Organization による {% data variables.product.prodname_advanced_security %} の使用を許可または禁止するポリシーを適用できます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+
+ライセンスの使用状況の表示について詳しくは、「[{% data variables.product.prodname_GH_advanced_security %} の使用状況を表示する](/admin/advanced-security/viewing-your-github-advanced-security-usage)」を参照してください。
+
+### {% data variables.product.prodname_GH_advanced_security %} ライセンスを最大限に活用する
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..f55c19e54e
--- /dev/null
+++ b/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: アプライアンスのコードスキャンを設定する
+shortTitle: コードスキャンを設定する
+intro: '{% data variables.product.product_location %} の {% data variables.product.prodname_code_scanning %} を有効化、設定、および無効化できます。 {% data variables.product.prodname_code_scanning_capc %} を使用すると、コードの脆弱性やエラーをスキャンできます。'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### {% data variables.product.prodname_code_scanning %} について
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+### {% data variables.product.prodname_actions %} を使用して {% data variables.product.prodname_code_scanning %} を実行する
+
+#### セルフホストランナーを設定する
+
+{% data variables.product.prodname_ghe_server %} は、{% data variables.product.prodname_actions %} ワークフローを使用して {% data variables.product.prodname_code_scanning %} を実行できます。 まず、環境内に 1 つ以上のセルフホスト {% data variables.product.prodname_actions %} ランナーをプロビジョニングする必要があります。 セルフホストランナーは、リポジトリ、Organization、または Enterprise アカウントレベルでプロビジョニングできます。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」および「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。
+
+{% data variables.product.prodname_codeql %} アクションを実行するために使用するセルフホストランナーの PATH 変数に Git が含まれていることを確認する必要があります。
+
+#### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+
+You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
+
+#### Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access
+If the server on which you are running {% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} action sync tool to copy the {% data variables.product.prodname_codeql %} analysis bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. ツールおよびツールの使用方法の詳細は、[https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) で確認できます。
+
+If you set up the {% data variables.product.prodname_codeql %} action sync tool, you can use it to sync the latest releases of the {% data variables.product.prodname_codeql %} action and associated {% data variables.product.prodname_codeql %} analysis bundle. These are compatible with {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+{% data variables.product.prodname_actions %} を使用して {% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_code_scanning %} を実行するには、適切なアクションがローカルで使用可能である必要があります。 アクションは 3 つの方法で利用可能にすることができます。
+
+- **推奨**: [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) を使用して、{% data variables.product.prodname_dotcom_the_website %} からアクションを自動的にダウンロードできます。 インスタンスをホストするマシンは、{% data variables.product.prodname_dotcom_the_website %} にアクセス可能である必要があります。 この方法で、最新のソフトウェアを自動的に入手できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)」を参照してください。
+- {% data variables.product.prodname_codeql_workflow %} を使用する場合は、[https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) にある {% data variables.product.prodname_codeql %} Action 同期ツールを使用して、リポジトリを {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.prodname_ghe_server %} に同期できます。 コンピューターで {% data variables.product.product_location %} と {% data variables.product.prodname_dotcom_the_website %} の両方に同時にアクセスできる限り、{% data variables.product.product_location %} または {% data variables.product.prodname_actions %} ランナーがインターネットにアクセスできるかどうかに関係なく、このツールを使用できます。
+- アクションを含む {% data variables.product.prodname_dotcom_the_website %} リポジトリのクローンを作成することにより、サーバー上にアクションのリポジトリのローカルコピーを作成できます。 たとえば、{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} のアクションを使用する場合は、インスタンスに `github/codeql-action` というリポジトリを作成し、{% data variables.product.prodname_dotcom_the_website %} から[リポジトリ](https://github.com/github/codeql-action)のクローンを作成して、そのリポジトリをインスタンスの `github/codeql-action` リポジトリにプッシュできます。 また、{% data variables.product.prodname_dotcom_the_website %} のリポジトリからリリースをダウンロードし、リリースとしてインスタンスの `github/codeql-action` リポジトリにアップロードする必要があります。
+{% endif %}
+
+#### {% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する
+1. {% data variables.product.prodname_dotcom_the_website %} からオンデマンドでアクションワークフローをダウンロードする場合は、{% data variables.product.prodname_github_connect %} を有効にする必要があります。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を有効化する](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)」を参照してください。
+2. また、{% data variables.product.product_location %} に対して {% data variables.product.prodname_actions %} を有効化する必要があります。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} を使ってみる](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)」を参照してください。
+3. 次のステップは、{% data variables.product.prodname_github_connect %} を使用して、{% data variables.product.prodname_dotcom_the_website %} に対するアクションへのアクセスを設定することです。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。
+4. セルフホストランナーをリポジトリ、Organization、または Enterprise アカウントに追加します。 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。
+
+### {% data variables.product.prodname_codeql_runner %} を使用して {% data variables.product.prodname_code_scanning %} を実行する
+{% data variables.product.prodname_actions %} を使用しない場合は、{% data variables.product.prodname_codeql_runner %} を使用して {% data variables.product.prodname_code_scanning %} を実行できます。
+
+{% data variables.product.prodname_codeql_runner %} は、サードパーティの CI/CD システムに追加できるコマンドラインツールです。 このツールは、{% data variables.product.prodname_dotcom %} リポジトリのチェックアウトに対して {% data variables.product.prodname_codeql %} 分析を実行します。 For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
diff --git a/translations/ja-JP/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/ja-JP/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..cb84b01574
--- /dev/null
+++ b/translations/ja-JP/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: アプライアンスのシークレットスキャンを設定する
+shortTitle: シークレットスキャンを設定する
+intro: '{% data variables.product.product_location %} の {% data variables.product.prodname_secret_scanning %} を有効化、設定、無効化できます。 {% data variables.product.prodname_secret_scanning_caps %} を使用すると、ユーザはコードをスキャンして、誤ってコミットされたシークレットを探すことができます。'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### {% data variables.product.prodname_secret_scanning %} について
+
+{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+
+### Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+
+- [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU フラグは、{% data variables.product.product_location %} を実行するVM/KVMで有効にする必要があります。
+
+- A license for {% data variables.product.prodname_GH_advanced_security %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### vCPU での SSSE3 フラグのサポートを確認する
+
+{% data variables.product.prodname_secret_scanning %} はハードウェアアクセラレーションによるパターンマッチングを利用して、{% data variables.product.prodname_dotcom %} リポジトリにコミットされた潜在的な認証情報を見つけるため、SSSE3 の一連の命令が必要です。 SSSE3 は、ほとんどの最新の CPU で有効になっています。 {% data variables.product.prodname_ghe_server %} インスタンスで使用可能な vCPU に対して SSSE3 が有効になっているかどうかを確認できます。
+
+1. {% data variables.product.prodname_ghe_server %} インスタンスの管理シェルに接続します。 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。
+2. 次のコマンドを入力します。
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+これで値 `0` が返される場合は、SSSE3 フラグが使用可能で有効になっていることを示します。 その後、{% data variables.product.product_location %} に対して {% data variables.product.prodname_secret_scanning %} を有効化できます。 For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+これで `0` が返されない場合、SSSE3 は VM/KVM で有効になっていません。 フラグを有効化する方法、またはゲスト VM で使用可能にする方法については、ハードウェア/ハイパーバイザーのドキュメントを参照する必要があります。
+
+#### {% data variables.product.prodname_advanced_security %} ライセンスがあるかどうかを確認する
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. 左のサイドバーに **{% data variables.product.prodname_advanced_security %}** エントリがあるかどうかを確認します。 ![[Advanced Security] サイドバー](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### {% data variables.product.prodname_secret_scanning %} の有効化
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. [{% data variables.product.prodname_advanced_security %}] で、[**{% data variables.product.prodname_secret_scanning_caps %}**] をクリックします。 ![{% data variables.product.prodname_secret_scanning %} を有効化または無効化するチェックボックス](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### {% data variables.product.prodname_secret_scanning %} を無効にする
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. [{% data variables.product.prodname_advanced_security %}] で、[**{% data variables.product.prodname_secret_scanning_caps %}**] を選択解除します。 ![{% data variables.product.prodname_secret_scanning %} を有効化または無効化するチェックボックス](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..fdf80f8b2c
--- /dev/null
+++ b/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% if currentVersion == "enterprise-server@3.0" %}詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」と「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %}
+{% endif %}
+
+### Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} For information about licensing, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
+2. Upload the new license to {% data variables.product.product_location %}. For more information, see "[Managing your GitHub Enterprise license](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![[Advanced Security] サイドバー](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Under "{% data variables.product.prodname_advanced_security %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %}
+1. [{% data variables.product.prodname_advanced_security %}] で、[**{% data variables.product.prodname_code_scanning_capc %}**] をクリックします。 ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. 詳しい情報については「[アプライアンスのための{% data variables.product.prodname_code_scanning %}の設定](/admin/advanced-security/configuring-code-scanning-for-your-appliance)」を参照してください。
+
+### 管理シェル (SSH) を介した {% data variables.product.prodname_GH_advanced_security %} の有効化または無効化
+
+You can enable or disable features programmatically on {% data variables.product.product_location %}. {% data variables.product.prodname_ghe_server %} の管理シェルおよびコマンドラインユーティリティの詳細については、「[管理シェル (SSH) へのアクセス](/admin/configuration/accessing-the-administrative-shell-ssh)」および「[コマンドラインユーティリティ](/admin/configuration/command-line-utilities#ghe-config)」を参照してください。
+
+たとえば、ステージングまたはシステム災害復旧に対してインスタンスをデプロイするときに、infrastructure-as-code ツールを使用して {% data variables.product.prodname_code_scanning %} を有効化できます。
+
+1. {% data variables.product.product_location %}にSSHでアクセスしてください。
+1. {% data variables.product.prodname_code_scanning %} を有効化します。
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. 必要に応じて、{% data variables.product.prodname_code_scanning %} を無効化します。
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. 設定を適用します。
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}To enable and disable {% data variables.product.prodname_secret_scanning %} in the same way, set: `ghe-config app.secret-scanning.enabled` true or false and apply the configuration.{% endif %}
diff --git a/translations/ja-JP/content/admin/advanced-security/index.md b/translations/ja-JP/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..9977306868
--- /dev/null
+++ b/translations/ja-JP/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing GitHub Advanced Security for your enterprise
+shortTitle: Managing GitHub Advanced Security
+intro: 'You can configure {% data variables.product.prodname_advanced_security %} and manage use by your enterprise to suit your organization''s needs.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### 目次
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/ja-JP/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/ja-JP/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..80bc578361
--- /dev/null
+++ b/translations/ja-JP/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,27 @@
+---
+title: Viewing your GitHub Advanced Security usage
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."
+
+### Viewing license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+You can check how many seats your license includes and how many seats are currently in use.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization.
+  ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization.
+  ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization.
+  ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png)
+  For more information, see "[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/ja-JP/content/admin/all-releases.md b/translations/ja-JP/content/admin/all-releases.md
new file mode 100644
index 0000000000..4205448568
--- /dev/null
+++ b/translations/ja-JP/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Enterprise Server releases
+intro: 'Documentation for the currently supported and previously deprecated versions of {{ site.data.variables.product.prodname_ghe_server }}.'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## Currently supported
+
+See [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) for information about the latest release.
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## Deprecated
+
+Documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## Deprecated developer documentation
+
+Developer documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index cf3ffa39d0..e90e5a2bff 100644
--- a/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: '{% if enterpriseServerVersions contains currentVersion %}{% data variabl
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### Enterprise のアイデンティティおよびアクセス管理について
diff --git a/translations/ja-JP/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/ja-JP/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index 50ad007695..dd5ea42384 100644
--- a/translations/ja-JP/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/ja-JP/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### 使用しているアイデンティティプロバイダ外のユーザのためのビルトイン認証について
diff --git a/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md b/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md
index 1d3a54d4f1..cd9dddee47 100644
--- a/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/ja-JP/content/admin/authentication/changing-authentication-methods.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data variables.product.product_location %}のユーザアカウントは、認証方式を変更しても保存され、ユーザはユーザ名が変更されない限り、同じアカウントにログインし続けることができます。
diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 3336fa74b2..8a4bac279c 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Azure AD を使用した認証とユーザプロビジョニングについて
diff --git a/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index cd92115b67..5644a0df69 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### SAML SSO について
diff --git a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index 8fefb06471..372eb5fb1e 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Enterprise 向けのユーザプロビジョニングについて
diff --git a/translations/ja-JP/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/ja-JP/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index e78fd29b52..341f6bd940 100644
--- a/translations/ja-JP/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/ja-JP/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: ビルトイン認証を使っている場合、認証されていない人がアカウントを作成するのをブロックできます。
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/authentication/using-built-in-authentication.md b/translations/ja-JP/content/admin/authentication/using-built-in-authentication.md
index 203c24a087..0ab8143003 100644
--- a/translations/ja-JP/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/ja-JP/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 サインインおよびサインアウトページでユーザに表示されるカスタムメッセージを作成できます。 詳しい情報については「[インスタンス上でのユーザメッセージをカスタマイズする](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)」を参照してください。
diff --git a/translations/ja-JP/content/admin/authentication/using-cas.md b/translations/ja-JP/content/admin/authentication/using-cas.md
index 4607a14cb4..531e2d30a3 100644
--- a/translations/ja-JP/content/admin/authentication/using-cas.md
+++ b/translations/ja-JP/content/admin/authentication/using-cas.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'CAS は、複数の Web アプリケーションのためのシングルサインオン (SSO) プロトコルです。 CAS ユーザアカウントは、ユーザがサインインするまで、{% if currentVersion ver_gt "enterprise-server@2.16" %}ユーザライセンス{% else %}シート{% endif %}の使用を開始しません。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ja-JP/content/admin/authentication/using-ldap.md b/translations/ja-JP/content/admin/authentication/using-ldap.md
index 0a3a03f013..8209dbfc0d 100644
--- a/translations/ja-JP/content/admin/authentication/using-ldap.md
+++ b/translations/ja-JP/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: 'LDAP を使えば、既存のアカウントに対して {% data variables.product.prodname_ghe_server %} を認証させることができ、リポジトリへのアクセスを集中管理できます。 LDAPはディレクトリ情報サービスへのアクセスと管理のための広く使われているアプリケーションプロトコルで、大企業のユーザディレクトリとサードパーティのソフトウェアを統合するために使われている最も一般的なプロトコルの1つです。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ja-JP/content/admin/authentication/using-saml.md b/translations/ja-JP/content/admin/authentication/using-saml.md
index ee364de688..7729adf28c 100644
--- a/translations/ja-JP/content/admin/authentication/using-saml.md
+++ b/translations/ja-JP/content/admin/authentication/using-saml.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'SAML は認証と認可のための XML ベースの標準です。 {% data variables.product.prodname_ghe_server %} は、内部的な SAML アイデンティティプロバイダ (IdP) とサービスプロバイダ (SP) として動作できます。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
@@ -31,7 +36,7 @@ topics:
 
 `NameID`要素は、他の属性が存在する場合でも必須です。
 
-A mapping is created between the `NameID` and the {% data variables.product.prodname_ghe_server %} username, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user.
+`NameID` と {% data variables.product.prodname_ghe_server %} ユーザ名の間にマッピングが作成されるため、`NameID` は永続的で一意でなければならず、ユーザのライフサイクルにおいて変更にさらされないようにする必要があります。
 
 {% note %}
 
@@ -48,7 +53,7 @@ A mapping is created between the `NameID` and the {% data variables.product.prod
 
 ### SAMLのメタデータ
 
-Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`.
+{% data variables.product.prodname_ghe_server %} インスタンスのサービスプロバイダメタデータは、`http(s)://[hostname]/saml/metadata` にあります。
 
 アイデンティティプロバイダを手動で設定するなら、Assertion Consumer Service (ACS) URLは`http(s)://[hostname]/saml/consume`です。 これは`urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`バインディングを利用します。
 
diff --git a/translations/ja-JP/content/admin/configuration/about-enterprise-configuration.md b/translations/ja-JP/content/admin/configuration/about-enterprise-configuration.md
index 42198d0833..930109d976 100644
--- a/translations/ja-JP/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/ja-JP/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: 'サイトアドミンのダッシュボード {% if enterpriseServerVers
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 Enterprise に初めてアクセスするときは、初期設定を完了して、
-{% data variables.product.product_name %} を使用できるようにします。 初期設定では、Enterprise を IdP に接続すること、SAML SSO を使用して認証すること、および Enterprise 内のリポジトリと Organization のポリシーを設定します。 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/admin/configuration/initializing-github-ae)」を参照してください。
-
-ユーザが初期設定後に {% data variables.product.product_name %} からメールを受信するには、SMTP サーバーで送信メールサポートを設定するように {% data variables.contact.github_support %} に依頼する必要があります。 詳しい情報については、「[通知のためのメールを設定する](/admin/configuration/configuring-email-for-notifications)」を参照してください。
+{% data variables.product.product_name %} を使用できるようにします。 The initial configuration includes connecting your enterprise with an identity provider (IdP), authenticating with SAML SSO, configuring policies for repositories and organizations in your enterprise, and configuring SMTP for outbound email. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/admin/configuration/initializing-github-ae)」を参照してください。
 
 後で、サイトアドミンのダッシュボードと Enterprise 設定を使用して、さらに Enterprise の設定を行い、ユーザ、Organization、およびリポジトリを管理し、リスクを軽減して品質を向上させるポリシーを設定できます。
 
diff --git a/translations/ja-JP/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/ja-JP/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index 9c0df2b2d6..4c4f71b768 100644
--- a/translations/ja-JP/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/ja-JP/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### 管理シェルでのアクセスについて
diff --git a/translations/ja-JP/content/admin/configuration/accessing-the-management-console.md b/translations/ja-JP/content/admin/configuration/accessing-the-management-console.md
index 72a9fbd5b5..4074648d7c 100644
--- a/translations/ja-JP/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/ja-JP/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### {% data variables.enterprise.management_console %}について
diff --git a/translations/ja-JP/content/admin/configuration/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/command-line-utilities.md
index 98fb198b00..f339ca35e1 100644
--- a/translations/ja-JP/content/admin/configuration/command-line-utilities.md
+++ b/translations/ja-JP/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 SSH 管理ユーザとしてサインインした後では、VM 上のどこからでもこれらのコマンドを実行できます。 詳しくは、"[管理シェル（SSH）へのアクセス方法](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)を参照してください。"
@@ -247,7 +249,7 @@ $ ghe-reactivate-admin-login
 
 #### ghe-resque-info
 
-このユーティリティは、アクティブでありかつキュー内にある、バックグラウンドジョブに関する情報を表示します。 あらゆるページの上部には、管理統計バーと同じジョブ数が表示されます。
+このユーティリティは、アクティブなものとキュー内にあるもの両方のバックグラウンドジョブに関する情報を表示します。 これは、すべてのページの上部にある管理統計バーと同じジョブ数を表示します。
 
 このユーティリティは、Resque サーバーでバックグラウンドジョブの処理に問題があるかどうかを識別するのに役立ちます。 以下のどのシナリオも Resque の問題を示している可能性があります。
 
@@ -482,15 +484,21 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 フックのペイロードの全体や結果、デリバリーの例外を表示するには、以下のようにします。
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### クラスタリング
 
 #### ghe-cluster-status
 
-このユーティリティを使えば、分散{% data variables.product.prodname_pages %}サーバーを管理できます。
+Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
 
 ```shell
 $ ghe-cluster-status
@@ -643,14 +651,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-このユーティリティは、Team Foundation Version Controlからインポートします。 詳しい情報については「[サードパーティのバージョン管理システムからのデータのインポート](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)」を参照してください。
+This utility imports from Team Foundation Version Control (TFVC). 詳しい情報については「[サードパーティのバージョン管理システムからのデータのインポート](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)」を参照してください。
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-このユーティリティは、インポートされたリポジトリを書き直します。 これにより、作者名を変更したり、SubversionやTFSではフォルダーを基にGitのブランチを生成したりできます。 詳しい情報については「[サードパーティのバージョン管理システムからのデータのインポート](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)」を参照してください。
+このユーティリティは、インポートされたリポジトリを書き直します。 This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. 詳しい情報については「[サードパーティのバージョン管理システムからのデータのインポート](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)」を参照してください。
 ```shell
 git-import-rewrite
 ```
diff --git a/translations/ja-JP/content/admin/configuration/configuring-a-hostname.md b/translations/ja-JP/content/admin/configuration/configuring-a-hostname.md
index 88881d55dc..aeb6e9dc3e 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ハードコードされたIPアドレスの代わりにホスト名を設定すれば、ユーザやクライアントソフトウェアに影響を与えることなく{% data variables.product.product_location %}を動作させる物理ハードウェアを変更できるようになります。
diff --git a/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 88af1f741c..eab49c23fc 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data variables.product.product_location %} に対してプロキシサーバーが有効である場合、送信先ホストが HTTP プロキシ除外として追加されていない限り、{% data variables.product.prodname_ghe_server %} によって送信されたアウトバウンドメッセージがプロキシサーバーを経由してまず最初に送信されます。 アウトバウンドのメッセージの種類には、webhook、Bundleのアップロード、レガシーのアバターのフェッチが含まれます。 プロキシサーバのURLは、たとえば`http://127.0.0.1:8123`といったように、プロトコル、ドメインもしくはIPアドレスにポート番号を加えたものです。
diff --git a/translations/ja-JP/content/admin/configuration/configuring-applications.md b/translations/ja-JP/content/admin/configuration/configuring-applications.md
index 2f97a708a9..f439a436a9 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-applications.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### 画像キャッシュを調整する
diff --git a/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md
index a57b6e67df..e5c38c92a0 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: アプライアンスでのバックアップの設定
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: 'システム災害復旧計画の一部として、自動化バックアップを設定して{% data variables.product.product_location %}のプロダクションデータを保護できます。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### {% data variables.product.prodname_enterprise_backup_utilities %}について
diff --git a/translations/ja-JP/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/ja-JP/content/admin/configuration/configuring-built-in-firewall-rules.md
index 6958124418..a67e59ffbb 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### {% data variables.product.product_location %}のファイアウォールについて
diff --git a/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index 300938643c..e6fd740409 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: データ暗号化を設定する
 intro: 保存時の暗号化時、独自の暗号化キーを提供し、暗号化ポリシーに基づいてデータを暗号化できます。
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 高レベルのセキュリティを提供するため、{% data variables.product.product_name %} は、データセンターでの保存中、およびユーザのマシンとデータセンター間でのデータの転送中にデータを暗号化します。
 
-転送中の暗号化では、{% data variables.product.product_name %} は Transport Layer Security (TLS) を使用します。 保存データの暗号化では、{% data variables.product.product_name %} がデフォルトの RSA キーを提供します。 Enterprise を初期化した後、代わりに独自のキーを提供することができます。 キーは、PEM 形式の 2048 ビット RSA 秘密鍵である必要があります。
-
-指定したキーは、{% data variables.product.company_short %} が管理する Key Vault の FIPS 140-2 準拠のハードウェアセキュリティモジュール (HSM) に保存されます。
-
-暗号鍵を設定するには、REST API を使用します。 暗号のステータスの確認、暗号鍵の更新、暗号鍵の無効化など、多くの API エンドポイントがあります。 キーを無効にすると、Enterprise がフリーズするためご注意ください。 API エンドポイントの詳細については、REST API ドキュメントの「[保存時の暗号化](/rest/reference/enterprise-admin#encryption-at-rest)」を参照してください。
-
-### 暗号鍵の追加または更新
-
-新しい暗号鍵は、必要に応じて何度でも追加できます。 新しい鍵を追加すると、古い鍵は破棄されます。 鍵を更新しても、Enterprise でダウンタイムが発生することはありません。
-
-2048 ビットの RSA 秘密鍵は、PEM 形式である必要があります（たとえば、_private-key.pem_ というファイル）。
-
-   ```
-   -----ここから RSA 秘密鍵-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----ここまで RSA 秘密鍵-----
-   ```
-
-1. キーを追加するには、`PATCH /enterprise/encryption` エンドポイントを使用し、*~/private-key.pem* を秘密鍵へのパスに置き換えます。
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. 必要に応じて、更新作業のステータスを確認します。
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### 暗号鍵を無効化する
-
-たとえば違反が発生した場合に Enterprise を凍結するには、暗号鍵を無効としてマークすることで、保存時の暗号化を無効にすることができます。
-
-1. 保存時に鍵と暗号化を無効にするには、`DELETE /enterprise/encryption` エンドポイントを使用します。 この作業で鍵が完全に削除されるわけではありません。
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. 必要に応じて、削除作業のステータスを確認します。 保存時に暗号化を無効にするには、約 10 分かかります。
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-暗号鍵を無効にした後で Enterprise の凍結を解除するには、サポートにお問い合わせください。 詳しい情報については、「[{% data variables.contact.enterprise_support %} について](/admin/enterprise-support/about-github-enterprise-support)」を参照してください。
-
-### 参考リンク
-
-- REST APIドキュメントの「[保存時の暗号化](/rest/reference/enterprise-admin#encryption-at-rest)」 
+転送中の暗号化では、{% data variables.product.product_name %} は Transport Layer Security (TLS) を使用します。 保存データの暗号化では、{% data variables.product.product_name %} がデフォルトの RSA キーを提供します。 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-dns-nameservers.md b/translations/ja-JP/content/admin/configuration/configuring-dns-nameservers.md
index 8eecb08c5f..9399f6a5d3 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 指定するネームサーバは、{% data variables.product.product_location %}のホスト名を解決できなければなりません。
diff --git a/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md
index eed8b2b06b..861260508e 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index 9b98ab8d8a..14d0760c6b 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### {% data variables.product.prodname_pages %} の公開サイトを有効にする
diff --git a/translations/ja-JP/content/admin/configuration/configuring-rate-limits.md b/translations/ja-JP/content/admin/configuration/configuring-rate-limits.md
index ba3567a6a3..16db615fc2 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### {% data variables.product.prodname_enterprise_api %}のレート制限の有効化
diff --git a/translations/ja-JP/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/ja-JP/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index b8a30801ea..a034a0ab85 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-time-synchronization.md b/translations/ja-JP/content/admin/configuration/configuring-time-synchronization.md
index 12f1459698..047bcc4391 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### デフォルトのNTPサーバの変更
diff --git a/translations/ja-JP/content/admin/configuration/configuring-tls.md b/translations/ja-JP/content/admin/configuration/configuring-tls.md
index a7c767fff2..e4d8005236 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-tls.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Transport Layer Securityについて
diff --git a/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 22fa4e0b30..42a04dea16 100644
--- a/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### {% data variables.product.prodname_github_connect %} について
diff --git a/translations/ja-JP/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/ja-JP/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index 4ca9516f0a..5cc0e91394 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### {% data variables.product.prodname_ghe_server %} 上の脆弱性のある依存関係に対するアラートについて
diff --git a/translations/ja-JP/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/ja-JP/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index c85e8b6ad6..3e2a41fb33 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### メンテナンスモードについて
diff --git a/translations/ja-JP/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ja-JP/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 4f3e8b5730..55017954e5 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### ライセンスの同期について
diff --git a/translations/ja-JP/content/admin/configuration/enabling-private-mode.md b/translations/ja-JP/content/admin/configuration/enabling-private-mode.md
index 5fdc348649..0ac62def4b 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-private-mode.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 {% data variables.product.product_location %}がインターネット経由でパブリックにアクセス可能になっている場合、プライベートモードを有効化しなければなりません。 プライベートモードでは、ユーザは`git://`経由でリポジトリを匿名クローンすることはできません。 ビルトイン認証も有効化されている場合、新しいユーザがインスタンスにアカウントを作成するには管理者が招待しなければなりません。 詳しい情報については"[ビルトイン認証の利用](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)"を参照してください。
diff --git a/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md b/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md
index 92d68f3c97..e11dde029c 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Subdomain Isolationについて
@@ -19,7 +24,7 @@ Subdomain Isolation が有効な場合、{% data variables.product.prodname_ghe_
 
 {% if currentVersion == "enterprise-server@2.22" %}
 Docker を
-{% data variables.product.prodname_registry %} で使用するには、Subdomain Isolation も有効にする必要があります。 詳しい情報については、「[{% data variables.product.prodname_registry %} で使用するために Docker を設定する](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)」を参照してください。
+{% data variables.product.prodname_registry %} で使用するには、Subdomain Isolation も有効にする必要があります。 For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/ja-JP/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/ja-JP/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index 1ceb9b8153..9621eb2f23 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 サイト管理者は、{% data variables.product.prodname_ghe_server %} からの作業に対する匿名のコントリビューション数の {% data variables.product.prodname_dotcom_the_website %} コントリビューショングラフへの送信をエンドユーザに許可できます。
diff --git a/translations/ja-JP/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/ja-JP/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 580783e91c..1630129208 100644
--- a/translations/ja-JP/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/ja-JP/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 Unified Searchを有効化すると、ユーザは{% data variables.product.product_location_enterprise %}から検索をした際に、{% data variables.product.prodname_dotcom_the_website %}上のパブリックおよびプライベートコンテンツからの検索結果を見ることができます。
diff --git a/translations/ja-JP/content/admin/configuration/index.md b/translations/ja-JP/content/admin/configuration/index.md
index db447ae0c8..079104c812 100644
--- a/translations/ja-JP/content/admin/configuration/index.md
+++ b/translations/ja-JP/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/ja-JP/content/admin/configuration/initializing-github-ae.md b/translations/ja-JP/content/admin/configuration/initializing-github-ae.md
index a35a851dfa..d7e903e449 100644
--- a/translations/ja-JP/content/admin/configuration/initializing-github-ae.md
+++ b/translations/ja-JP/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: GitHub AE を初期化する
 intro: '{% data variables.product.product_name %} の初期設定を完了して Enterprise で使用できるようにします。'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### 初期化について
@@ -79,11 +82,11 @@ Enterprise を初期化する前に、{% data variables.product.product_name %}
 1. [Configure email settings] の右側にある [**Configure**] をクリックします。 ![メール設定の [Configure] ボタン](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. **Enable email（メールの有効化）**を選択してください。 これにより、アウトバウンドメールとインバウンドメールの両方が有効になりますが、インバウンドメールが動作するようにするには、DNS 設定を行う必要があります。 詳しい情報については、「[着信メールを許可するよう DNS およびファイアウォールを設定する](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)」を参照してください。 ![メール設定の [Enable] チェックボックス](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. メールサーバーの設定を完了します。
-  - [**Server address**] フィールドに SMTP サーバのアドレスを入力します。
-  - [**Port**] フィールドには、SMTP サーバがメールを送信するのに使用するポートを入力します。
-  - [**Domain**] フィールドには、SMTP サーバが HELO レスポンスを送信するドメイン名があれば入力してください。
-  - [** Authentication（認証）**] ドロップダウンでは、SMTP サーバが利用する暗号化の種類を選択してください。
-  - [**No-reply email address（No-replyメールアドレス）**] フィールドには、すべての通知メールの From および To フィールドに使うメールアドレスを入力してください。
+    - [**Server address**] フィールドに SMTP サーバのアドレスを入力します。
+    - [**Port**] フィールドには、SMTP サーバがメールを送信するのに使用するポートを入力します。
+    - [**Domain**] フィールドには、SMTP サーバが HELO レスポンスを送信するドメイン名があれば入力してください。
+    - [** Authentication（認証）**] ドロップダウンでは、SMTP サーバが利用する暗号化の種類を選択してください。
+    - [**No-reply email address（No-replyメールアドレス）**] フィールドには、すべての通知メールの From および To フィールドに使うメールアドレスを入力してください。
 
 4. no-replyメールアドレスへの着信メールをすべて破棄したい場合には、**Discard email addressed to the no-reply email address（no-replyメールアドレスへのメールの破棄）**を選択してください。 ![メール設定の [Discard] チェックボックス](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. [**Test email settings**] をクリックします。 ![メール設定の [Test email settings] ボタン](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 78784beee1..0cd504060a 100644
--- a/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: '認証されたユーザが {% data variables.product.prodname_mobile %}
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ja-JP/content/admin/configuration/network-ports.md b/translations/ja-JP/content/admin/configuration/network-ports.md
index 53e0f85176..002f84be33 100644
--- a/translations/ja-JP/content/admin/configuration/network-ports.md
+++ b/translations/ja-JP/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: オープンするネットワークポートは、管理者、エンドユーザ、メールサポートへ公開する必要があるネットワークサービスに応じて選択してください。
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### 管理ポート
diff --git a/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index 350e2e1f98..7c355e3ca5 100644
--- a/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -4,6 +4,13 @@ shortTitle: ネットワークトラフィックを制限する
 intro: IP 許可リストを使用して、Enterprise へのアクセスを指定された IP アドレスからの接続に制限できます。
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### IP 許可リストについて
diff --git a/translations/ja-JP/content/admin/configuration/site-admin-dashboard.md b/translations/ja-JP/content/admin/configuration/site-admin-dashboard.md
index 9961174073..4ad097f235 100644
--- a/translations/ja-JP/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/ja-JP/content/admin/configuration/site-admin-dashboard.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ダッシュボードへアクセスするには、ページ右上の隅にある {% octicon "rocket" aria-label="The rocket ship" %}をクリックしてください。 ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/ja-JP/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/ja-JP/content/admin/configuration/troubleshooting-ssl-errors.md
index e2eaf733ef..7424dcd0b8 100644
--- a/translations/ja-JP/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/ja-JP/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### 鍵ファイルからのパスフレーズの除去
diff --git a/translations/ja-JP/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/ja-JP/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index 249b7be3a0..642199116a 100644
--- a/translations/ja-JP/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/ja-JP/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/ja-JP/content/admin/configuration/validating-your-domain-settings.md b/translations/ja-JP/content/admin/configuration/validating-your-domain-settings.md
index 5069d5e230..bbe9f30f82 100644
--- a/translations/ja-JP/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/ja-JP/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/ja-JP/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/about-cluster-nodes.md b/translations/ja-JP/content/admin/enterprise-management/about-cluster-nodes.md
index 254e636379..307fb1ed1c 100644
--- a/translations/ja-JP/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/ja-JP/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/about-clustering.md b/translations/ja-JP/content/admin/enterprise-management/about-clustering.md
index b3030b5d34..1ff035ae5d 100644
--- a/translations/ja-JP/content/admin/enterprise-management/about-clustering.md
+++ b/translations/ja-JP/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md b/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md
index 3ae89ee017..bb121b0c6a 100644
--- a/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/ja-JP/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 アクティブなレプリカが複数あれば、最も近いレプリカへの距離を短くできます。 たとえばサンフランシスコ、ニューヨーク、ロンドンにオフィスを持つ組織は、プライマリのアプライアンスをニューヨークの近くのデータセンター内で動作させ、2つのレプリカをサンフランシスコとロンドンの近くのデータセンターで動作させることができます。 地理的な場所を認識するDNSを利用すれば、ユーザーは利用可能な最も近いサーバへ振り分けられ、リポジトリのデータに高速にアクセスできます。 ニューヨークの近くにあるアプライアンスをプライマリにすれば、ロンドンへのレイテンシが大きいサンフランシスコ近くのアプライアンスをプライマリにする場合に比べ、ホスト間のレイテンシの削減に役立ちます。
diff --git a/translations/ja-JP/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/ja-JP/content/admin/enterprise-management/about-high-availability-configuration.md
index d2b9db7a44..e46fb8fede 100644
--- a/translations/ja-JP/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/ja-JP/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 High Availability設定をする際には、プライマリからレプリカアプライアンスへのすべてのデータストア（Gitリポジトリ、MySQL、Redis、Elasticsearch）の一方方向の非同期レプリケーションが、自動的にセットアップされます。
diff --git a/translations/ja-JP/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/ja-JP/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 43a538e39f..3fed950db2 100644
--- a/translations/ja-JP/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/ja-JP/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### モニターダッシュボードへのアクセス
diff --git a/translations/ja-JP/content/admin/enterprise-management/cluster-network-configuration.md b/translations/ja-JP/content/admin/enterprise-management/cluster-network-configuration.md
index 29212a1f92..a58d1002db 100644
--- a/translations/ja-JP/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/ja-JP/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### ネットワークに関する考慮
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md b/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md
index 806629e749..1f669c60ff 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### 外部 `collectd` サーバーを設置
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index 3d77527687..ff3e516073 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### クラスタの High Availability レプリケーションについて
@@ -22,7 +26,7 @@ High Availability モードでは、各アクティブノードは対応する
 
 #### ハードウェアとソフトウェア
 
-アクティブなクラスタ内の既存のノードごとに、同一のハードウェアリソースを使用して2番目の仮想マシンをプロビジョニングする必要があります。 たとえば、クラスタに 11 個のノードがあり、各ノードに 12 個の vCPU、96GB の RAM、および 750GB の接続ストレージがある場合、それぞれが 12 個の vCPU、64GB の RAM、および 750GB の接続ストレージを備えた 11 個の新しい仮想マシンをプロビジョニングする必要があります。
+アクティブなクラスタ内の既存のノードごとに、同一のハードウェアリソースを使用して2番目の仮想マシンをプロビジョニングする必要があります。 たとえば、クラスタに 11 個のノードがあり、各ノードに 12 個の vCPU、96GB の RAM、および 750GB の接続ストレージがある場合、それぞれが 12 個の vCPU、96GB の RAM、および 750GB の接続ストレージを備えた 11 個の新しい仮想マシンをプロビジョニングする必要があります。
 
 新しい仮想マシンごとに、アクティブクラスタ内のノードで実行されているものと同じバージョンの {% data variables.product.prodname_ghe_server %} をインストールします。 ライセンスをアップロードしたり、追加の設定を実行したりする必要はありません。 詳細は「[{% data variables.product.prodname_ghe_server %}インスタンスをセットアップする](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/creating-a-high-availability-replica.md
index 572e16e177..d6cc52a11b 100644
--- a/translations/ja-JP/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/ja-JP/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/ja-JP/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index c08d6c6780..48f770a297 100644
--- a/translations/ja-JP/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/ja-JP/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### フェイルオーバーのシナリオ
diff --git a/translations/ja-JP/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/ja-JP/content/admin/enterprise-management/enabling-automatic-update-checks.md
index ecebc61751..34bbd4da04 100644
--- a/translations/ja-JP/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/ja-JP/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_location %} のアップグレードパッケージが自動的にダウンロードされると、{% data variables.product.prodname_ghe_server %} をアップグレードできることを知らせるメッセージを受け取ります。 パッケージは{% data variables.product.product_location %}の `/var/lib/ghe-updates`ディレクトリへダウンロードされます。 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)」を参照してください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md
index eaba1ad9d1..a985e87661 100644
--- a/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/ja-JP/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/ja-JP/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index 597f24e433..91430164d2 100644
--- a/translations/ja-JP/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/ja-JP/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/ja-JP/content/admin/enterprise-management/increasing-storage-capacity.md
index cac4c3a85d..fc1be4670d 100644
--- a/translations/ja-JP/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/ja-JP/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -31,7 +35,10 @@ topics:
 1. 仮想化プラットフォームのツールを使用して、既存のユーザーボリュームのディスクのサイズを変更します。
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. アプライアンスをメンテナンスモードにしてください。 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
-4. アプライアンスを再起動して、新しいストレージの割り当てを検出させてください。
+4. Reboot the appliance to detect the new storage allocation:
+  ```shell
+  $ sudo reboot
+  ```
 5. `ghe-storage-extend` コマンドを実行して、`/data/user` のファイルシステムを拡張します。
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ topics:
 ### 新しいアプライアンスを使用したルートパーティションサイズの増加
 
 1. 現在のアプライアンスと同じバージョンを使用して、より大きなルートディスクで新たな {% data variables.product.prodname_ghe_server %} をセットアップします。 詳細は「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
-2. 現在のアプライアンスをシャットダウンします。
+2. Shut down the current appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 3. 使用している仮想化プラットフォームのツールを使い、現在のアプライアンスからデータディスクをデタッチします。
 4. 大きなルートディスクを持つ新しいアプライアンスにデータディスクをアタッチします。
 
@@ -57,6 +67,9 @@ topics:
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. アプライアンスをシャットダウンします。
+4. Shut down the appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 5. ハイパーバイザーで、古いルートディスクを取り外し、古いルートディスクと同じ場所に新しいルートディスクを取り付けます。
 6. アプライアンスを起動します。
diff --git a/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md b/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md
index 2d1881ba16..595da25bde 100644
--- a/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/ja-JP/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 2e326af7dd..b79648feff 100644
--- a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 フェイルオーバーに必要な時間は、レプリカを手動で昇格させてトラフィックをリダイレクトするのにかかる時間によって異なります。 平均的な時間は 2 分から 10 分です。
diff --git a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index ab5d63e698..0f22d56775 100644
--- a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### レプリカクラスタへのフェイルオーバーについて
diff --git a/translations/ja-JP/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/ja-JP/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index 9f9df069f4..473d651524 100644
--- a/translations/ja-JP/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/ja-JP/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -12,8 +12,11 @@ redirect_from:
 intro: '{% data variables.product.prodname_enterprise %}11.10.xから2.1.23へ移行するには、新しいアプライアンスのインスタンスをセットアップし、以前のインスタンスからデータを移行しなければなりません。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 {% data variables.product.prodname_enterprise %}11.10.348以降からの移行がサポートされています。 {% data variables.product.prodname_enterprise %}11.10.348以前からの移行はサポートされていません。 いくつかのアップグレードを経て、まず11.10.348にアップグレードしなければなりません。 詳しい情報については11.10.348のアップグレード手順"[最新リリースへのアップグレード](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)"を参照してください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md
index 64928fab66..3ecdd49662 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -7,7 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### クラスタのステータスの手動でのチェック
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-using-snmp.md
index ac931e0324..6e8d6ea85c 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP とは、ネットワーク経由でデバイスを監視するための一般的基準です。 {% data variables.product.product_location %}のj状態を監視可能にし、いつホストのマシンにメモリやストレージ、処理能力を追加すべきかを知るために、SNMP を有効にすることを強くおすすめします。
diff --git a/translations/ja-JP/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/ja-JP/content/admin/enterprise-management/recommended-alert-thresholds.md
index d62d6d0fed..664537e41b 100644
--- a/translations/ja-JP/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/ja-JP/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### ストレージのモニタリング
diff --git a/translations/ja-JP/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/ja-JP/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index 425c24a0f1..1f56ba6048 100644
--- a/translations/ja-JP/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/ja-JP/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 フェイルオーバーが計画済みのものだったり、アプライアンスの健全性に関係ないものである場合、以前のプライマリアプライアンスを新しいレプリカアプライアンスとして使用できます。 フェイルオーバーがプライマリアプライアンスの問題に関係しているなら、新しいレプリカアプライアンスを作成する方が良いでしょう。 詳しい情報については"[High Availabilityレプリカの作成](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)"を参照してください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md
index c731a9575b..a05e679923 100644
--- a/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/ja-JP/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### 一時的なレプリケーションの停止
diff --git a/translations/ja-JP/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/ja-JP/content/admin/enterprise-management/replacing-a-cluster-node.md
index 6f5965c4c8..f107589b08 100644
--- a/translations/ja-JP/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/ja-JP/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/ja-JP/content/admin/enterprise-management/setting-up-external-monitoring.md
index 61c5f8d90c..e5a4ffb666 100644
--- a/translations/ja-JP/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/ja-JP/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### SNMPについて
diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md b/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md
index 0cd29615f6..60683072ce 100644
--- a/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/ja-JP/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 MySQLの監査ログで必要なディスク容量の概算には、この数字を使用します。 スクリプトは、インポートの進行中に空きディスク容量も監視します。 この数字を監視しておくと、空きディスク容量が、移行に必要なディスク容量に近い場合に特に便利です。
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### 次のステップ
+
 これらの推奨および要求事項をレビューした後で、{% data variables.product.prodname_ghe_server %} をアップグレードできます。 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)」を参照してください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/ja-JP/content/admin/enterprise-management/upgrading-a-cluster.md
index 8ecb0a0221..156408ad48 100644
--- a/translations/ja-JP/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/ja-JP/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### ホットパッチでのアップグレード
diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index 71cfd307f1..643c4d9ce9 100644
--- a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### アップグレードの準備
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### {% data variables.product.prodname_ghe_server %} 3.0 以降の最小要件について
-
-{% data variables.product.prodname_ghe_server %} 3.0 以降にアップグレードする前に、インスタンスにプロビジョニングしたハードウェアリソースを確認してください。 {% data variables.product.prodname_ghe_server %} 3.0 は、{% data variables.product.prodname_actions %} や {% data variables.product.prodname_registry %} などの新機能を導入しているため、バージョン 2.22 以前よりも多くのリソースが必要となります。 詳しい情報については、[{% data variables.product.prodname_ghe_server %} 3.0 のリリースノート](/enterprise-server@3.0/admin/release-notes)を参照してください。
-
-次の表では、{% data variables.product.prodname_ghe_server %} 3.0 以降の要件の増加を**太字**で示しています。
-
-| ユーザライセンス               |                        vCPUs |                                  メモリ |                         アタッチされたストレージ | ルートストレージ |
-|:---------------------- | ----------------------------:| ------------------------------------:| ------------------------------------:| --------:|
-| トライアル、デモ、あるいは10人の軽量ユーザ |   **4**<br/>_2 から増加_ |   **32 GB**<br/>_16 GB から増加_ | **150 GB**<br/>_100 GB から増加_ |   200 GB |
-| 10-3000                |   **8**<br/>_4 から増加_ |   **48 GB**<br/>_32 GB から増加_ | **300 GB**<br/>_250 GB から増加_ |   200 GB |
-| 3000-5000              |  **12**<br/>_8 から増加_ |                                64 GB |                               500 GB |   200 GB |
-| 5000-8000              | **16**<br/>_12 から増加_ |                                96 GB |                               750 GB |   200 GB |
-| 8000-10000+            | **20**<br/>_16 から増加_ | **160 GB**<br/>_128 GB から増加_ |                              1000 GB |   200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### スナップショットの取得
 
@@ -81,7 +59,7 @@ For more information about hardware requirements for {% data variables.product.p
 | Hyper-V               | VM            | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | ディスク          | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM            | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM            | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM            | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### ホットパッチでのアップグレード
 
@@ -89,7 +67,12 @@ For more information about hardware requirements for {% data variables.product.p
 
 {% note %}
 
-**注釈**: クラスタ環境では、{% data variables.enterprise.management_console %} を使ったホットパッチのインストールはできません。 クラスタ環境でホットパッチをインストールするには、「[クラスタをアップグレードする](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)」を参照してください。
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}Notes{% else %}Note{% endif %}**:
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+
+- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. クラスタ環境でホットパッチをインストールするには、「[クラスタをアップグレードする](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)」を参照してください。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md
index b81a75c773..2e9d85e2c5 100644
--- a/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/ja-JP/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index 1ae847aa50..4d46b9d5df 100644
--- a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index 415eb69f60..af4d0ee3fc 100644
--- a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md
index 4564eefa70..2ddf2bedd8 100644
--- a/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/ja-JP/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index fdc023d66c..babb041241 100644
--- a/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/ja-JP/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 チケットをサブミットする前に以下の作業を済ませておいてください。
diff --git a/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md
index 4569cb5183..e4c0e26d9f 100644
--- a/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/ja-JP/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Diagnosticファイルの作成と共有
diff --git a/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md b/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md
index f1c1ac0bfd..7d89d76cd0 100644
--- a/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/ja-JP/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### 自動チケットシステムを使用する
diff --git a/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md b/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md
index 4bd8f27835..f2c6c40c8e 100644
--- a/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/ja-JP/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### チケットのサブミットについて
diff --git a/translations/ja-JP/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..0a272c7a49
--- /dev/null
+++ b/translations/ja-JP/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: About using actions in your enterprise
+intro: '{% data variables.product.product_name %} には、ほとんどの {% data variables.product.prodname_dotcom %} 作成のアクションが含まれ、{% data variables.product.prodname_dotcom_the_website %} および {% data variables.product.prodname_marketplace %} からの他のアクションへのアクセスを有効にするためのオプションがあります。'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+{% data variables.product.prodname_actions %} ワークフローは_アクション_を使用できます。アクションは、ジョブを作成してワークフローをカスタマイズするために組み合わせることができる個々のタスクです。 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### Official actions bundled with your enterprise instance
+
+ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.product_name %} にバンドルされ、{% data variables.product.prodname_marketplace %} からある時点でキャプチャされます。
+
+バンドルされている公式アクションには、`actions/checkout`, `actions/upload-artifact`、`actions/download-artifact`、`actions/labeler`、さまざまな `actions/setup-` などが含まれます。 Enterprise インスタンスに含まれるすべての公式アクションを確認するには、インスタンスの `Actions` Organization である (<code>https://<em>HOSTNAME</em>/actions</code>) を参照します。
+
+各アクションは`actions` Organization 内のリポジトリであり、各アクションリポジトリには、ワークフローがアクションを参照するために使用できる必要なタグ、ブランチ、およびコミット SHA が含まれています。 For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)."
+
+{% note %}
+
+**注釈:** セルフホストランナーを使用して {% data variables.product.product_name %} でセットアップアクション（`actions/setup-LANGUAGE` など）を使用する場合、インターネットにアクセスできないランナーでツールキャッシュをセットアップする必要がある場合があります。 詳しい情報については、「[インターネットアクセスを持たないセルフホストランナー上へのツールキャッシュのセットアップ](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)」を参照してください。
+
+{% endnote %}
+
+### {% data variables.product.prodname_dotcom_the_website %} でアクションへのアクセスを設定する
+
+If users in your enterprise need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options.
+
+推奨されるアプローチは、{% data variables.product.prodname_dotcom_the_website %} からのすべてのアクションへの自動アクセスを有効化することです。 これを行うには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.product_name %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 {% data reusables.actions.enterprise-limit-actions-use %}
+
+または、Enterprise で許可されるアクションをより厳密に制御する場合は、`actions-sync` ツールを使用してアクションを手動でダウンロードして Enterprise インスタンスに同期できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom_the_website %} からのアクションを手動で同期する](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)」を参照してください。
diff --git a/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 620b1cb75f..7c36905842 100644
--- a/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/ja-JP/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: バックアップと復元
 intro: '外部ストレージプロバイダの {% data variables.product.prodname_actions %} データは、通常の {% data variables.product.prodname_ghe_server %} バックアップに含まれていないため、個別にバックアップする必要があります。'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index a2588d81ba..f1a537d249 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: GitHub Connect を使用して GitHub.com アクションへの自動アクセスを有効にする
-intro: 'Enterprise インスタンスの {% data variables.product.prodname_actions %} が {% data variables.product.prodname_dotcom_the_website %} のアクションを使用できるようにするには、{% data variables.product.product_location_enterprise %} を {% data variables.product.prodname_ghe_cloud %} に接続します。'
+intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-デフォルトでは、{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} ワークフローは {% data variables.product.prodname_dotcom_the_website %} または [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) から直接アクションを使用できません。
+デフォルトでは、{% data variables.product.product_name %} の {% data variables.product.prodname_actions %} ワークフローは {% data variables.product.prodname_dotcom_the_website %} または [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) から直接アクションを使用できません。
 
-{% data variables.product.prodname_dotcom_the_website %} のすべてのアクションを Enterprise インスタンスで使用できるようにするには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 {% data variables.product.prodname_dotcom_the_website %} からアクションにアクセスする他の方法については、「[{% data variables.product.prodname_ghe_server %} でのアクションの使用について](/admin/github-actions/about-using-actions-on-github-enterprise-server)」を参照してください。
+{% data variables.product.prodname_dotcom_the_website %} のすべてのアクションを Enterprise インスタンスで使用できるようにするには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.product_name %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### すべての {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する
 
-{% data variables.product.product_location_enterprise %} 上の {% data variables.product.prodname_dotcom_the_website %} からのすべてのアクションへのアクセスを有効にする前に、{% data variables.product.product_location_enterprise %} を {% data variables.product.prodname_dotcom_the_website %} に接続する必要があります。 詳細は、「[{% data variables.product.prodname_ghe_server %}を{% data variables.product.prodname_ghe_cloud %}に接続する](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。
+Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. 詳細は、「[{% data variables.product.prodname_ghe_server %}を{% data variables.product.prodname_ghe_cloud %}に接続する](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index c8a569457e..e4e1b314b0 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 {% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。
 
-* ワークフローの実行によって生成されたアーティファクトを保存するための Amazon S3 バケットを作成します。 {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* ワークフローの実行によって生成されたアーティファクトを保存するための Amazon S3 バケットを作成します。 {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index 5f9fe9b064..f90f869f79 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 {% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。
 
 * アプライアンスでのリソースの競合を回避するために、MinIO を {% data variables.product.product_location %} とは別にホストすることをお勧めします。
-* ワークフローアーティファクトを保存するためのバケットを作成します。 バケットとアクセスキーを設定するには、[MinIO のドキュメント](https://docs.min.io/docs/minio-gateway-for-nas.html)を参照してください。 {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* ワークフローアーティファクトを保存するためのバケットを作成します。 バケットとアクセスキーを設定するには、[MinIO のドキュメント](https://docs.min.io/docs/minio-gateway-for-nas.html)を参照してください。 {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 584f0ae691..09a75ae969 100644
--- a/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index 8bd80b6a14..7f133e3bac 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: GitHub AE の GitHub Actions を使い始める
+shortTitle: GitHub Actionsを使ってみる
 intro: '{% data variables.product.prodname_ghe_managed %} で {% data variables.product.prodname_actions %} を設定する方法を学びます。'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index 16e1ca0eb0..5a0b79bb15 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,5 +1,6 @@
 ---
 title: GitHub Enterprise Server の GitHub Actions を使い始める
+shortTitle: GitHub Actionsを使ってみる
 intro: '{% data variables.product.prodname_ghe_server %} での {% data variables.product.prodname_actions %} の有効化と設定について初めて学びます。'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
@@ -7,7 +8,9 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
+  - Actions
   - Enterprise
 ---
 
@@ -116,7 +119,7 @@ For more information about minimum hardware requirements for {% data variables.p
 
 ユーザーが Enterprise で使用できるアクションを制御できます。 これには、{% data variables.product.prodname_dotcom_the_website %} からのアクションへの自動アクセス用の {% data variables.product.prodname_github_connect %} の設定、または {% data variables.product.prodname_dotcom_the_website %} からのアクションの手動同期が含まれます。
 
-詳しい情報については、「[{% data variables.product.prodname_ghe_server %} でのアクションの使用について](/admin/github-actions/about-using-actions-on-github-enterprise-server)」を参照してください。
+For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### {% data variables.product.prodname_actions %} の一般的なセキュリティ強化
 
diff --git a/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md
index 997557eb05..8dd828ae74 100644
--- a/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/ja-JP/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: GitHub Actions の High Availability
 intro: 'High Availability 設定で {% data variables.product.prodname_actions %} を管理するための特別な留意点がいくつかあります。'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### {% data variables.product.prodname_actions %} データのレプリケーションまたは冗長性
diff --git a/translations/ja-JP/content/admin/github-actions/index.md b/translations/ja-JP/content/admin/github-actions/index.md
index 31e835c5aa..31f6c117bc 100644
--- a/translations/ja-JP/content/admin/github-actions/index.md
+++ b/translations/ja-JP/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index 9a9da0d712..a307b361d8 100644
--- a/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/ja-JP/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub.com からアクションを手動で同期する
-intro: '{% data variables.product.prodname_dotcom_the_website %} からのアクションにアクセスする必要があるユーザは、特定のアクションを {% data variables.product.prodname_ghe_server %} インスタンスに同期できます。'
+intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-{% data variables.product.prodname_dotcom_the_website %} からのアクションへのアクセスを有効化する際に推奨されるアプローチは、すべてのアクションへの自動アクセスを有効化することです。 これを行うには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。
+{% data variables.product.prodname_dotcom_the_website %} からのアクションへのアクセスを有効化する際に推奨されるアプローチは、すべてのアクションへの自動アクセスを有効化することです。 これを行うには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.product_name %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。
 
-ただし、Enterprise で許可されるアクションをより厳密に制御する場合は、このガイドに従って、{% data variables.product.company_short %} のオープンソース [`actions-sync`](https://github.com/actions/actions-sync) ツールを使用して、個々のアクションリポジトリを {% data variables.product.prodname_dotcom_the_website %} から Enterprise インスタンスに同期できます。
+However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise.
 
 ### `actions-sync` ツールについて
 
-`actions-sync` ツールは、{% data variables.product.prodname_dotcom_the_website %} API と {% data variables.product.prodname_ghe_server %} インスタンスの API にアクセスできるマシンで実行する必要があります。 両方のマシンに同時に接続する必要はありません。
+`actions-sync` ツールは、{% data variables.product.prodname_dotcom_the_website %} API と {% data variables.product.product_name %} インスタンスの API にアクセスできるマシンで実行する必要があります。 両方のマシンに同時に接続する必要はありません。
 
 マシンが両方のシステムに同時にアクセスできる場合、1 つの `actions-sync sync` コマンドで同期を実行できます。 一度に 1 つのシステムにのみアクセスできる場合は、`actions-sync pull` および `push` コマンドを使用できます。
 
@@ -29,8 +30,8 @@ topics:
 
 ### 必要な環境
 
-* `actions-sync` ツールを使用する前に、すべての宛先 Organization が Enterprise インスタンスにすでに存在していることを確認する必要があります。 次の例は、Enterprise インスタンスの `synced-actions` という名前の Organization にアクションを同期する方法を示しています。 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。
-* Enterprise インスタンスに、宛先 Organization のリポジトリを作成して書き込むことができる個人アクセストークン (PAT) を作成する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
+* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。
+* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
 * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
 
   {% note %}
@@ -51,7 +52,7 @@ topics:
 
 {% note %}
 
-**注釈:** この例では、`actions-sync sync` コマンドを使用します。これには、マシンから {% data variables.product.prodname_dotcom_the_website %} API と {% data variables.product.prodname_ghe_server %} インスタンスの API の両方への同時アクセスが必要です。 一度に 1 つのシステムにのみアクセスできる場合は、`actions-sync pull` および `push` コマンドを使用できます。 詳しい情報については、「[`actions/cache` README](https://github.com/actions/actions-sync#not-connected-instances)」を参照してください。
+**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. 一度に 1 つのシステムにのみアクセスできる場合は、`actions-sync pull` および `push` コマンドを使用できます。 詳しい情報については、「[`actions/cache` README](https://github.com/actions/actions-sync#not-connected-instances)」を参照してください。
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ topics:
    * `--destination-url`: 宛先 Enterprise インスタンスの URL。
    * `--repo-name`: 同期するアクションリポジトリ。 これは、`owner/repository:destination_owner/destination_repository` の形式を採用しています。
 
-     * 上記の例では、[`docker/build-push-action`](https://github.com/docker/build-push-action) リポジトリを宛先 {% data variables.product.prodname_ghe_server %} インスタンスの `synced-actions/docker-build-push-action` リポジトリに同期します。 上記のコマンドを実行する前に、Enterprise インスタンスで `synced-actions` という名前の Organization を作成する必要があります。
-     * `:destination_owner/destination_repository` を省略すると、ツールは Enterprise インスタンスの元の所有者とリポジトリ名を使用します。 コマンドを実行する前に、アクションの所有者名と一致する新しい Organization をインスタンスに作成する必要があります。 同期されたアクションをインスタンスに保存するために中枢の Organization を使用することを検討してください。これは、異なる所有者からのアクションを同期する場合、複数の新しい Organization を作成する必要がないということです。
+     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command.
+     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners.
      * `--repo-name` パラメータを `--repo-name-list` または `--repo-name-list-file` に置き換えることにより、複数のアクションを同期できます。 詳しい情報については、「[`actions/cache` README](https://github.com/actions/actions-sync#actions-sync)」を参照してください。
-1. Enterprise インスタンスでアクションリポジトリが作成された後、Enterprise 内のユーザは、宛先リポジトリを使用してワークフロー内のアクションを参照できます。 上記のアクション例の場合:
+1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. 上記のアクション例の場合:
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 07486746e2..aa2b01945f 100644
--- a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### 含まれているセットアップアクションとランナーツールキャッシュについて
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.prodname_ghe_server %} にバンドルされます。 ただし、インターネットにアクセスできないセルフホストランナーは、`setup-node` などの含まれている `actions/setup-LANGUAGE` アクションを使用する前に、いくつかの設定が必要になります。
+ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.product_name %} にバンドルされます。 However, self-hosted runners without internet access require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
 
 `actions/setup-LANGUAGE` アクションは通常、必要な環境バイナリをランナーのツールキャッシュにダウンロードするためにインターネットアクセスが必要です。 インターネットにアクセスできないセルフホストのランナーはバイナリをダウンロードできないため、ランナーのツールキャッシュに手動でデータを入力する必要があります。
 
diff --git a/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md b/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md
index 5c2df363de..3c9d6fbe13 100644
--- a/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/ja-JP/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: ステージング環境を使用する
 intro: '{% data variables.product.prodname_actions %} を {% data variables.product.prodname_ghe_server %} ステージング環境で使用する方法について説明します。'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% data variables.product.product_location %} のステージング環境またはテスト環境があると便利な場合があります。これにより、更新または新機能を本番環境に実装する前にテストできます。
diff --git a/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 3e0191625c..1cb8e699e4 100644
--- a/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
 title: Using the latest version of the official bundled actions
-intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)."
 
-These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
+These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.
 
-Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
+### Using `actions-sync` to update the bundled actions
 
-- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
-- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
+To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
 
-These options are described in more detail in the following sections.
+### Using {% data variables.product.prodname_github_connect %} to access the latest actions
 
-### Using actions-sync to update a bundled action
+You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。
 
-To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
+Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}:
 
-### Using actions from {% data variables.product.prodname_dotcom_the_website %}
+1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." 例:
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
-
-### Using the latest version by removing the specific action's tag
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
-
-For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
-
-1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
-1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
-
-When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)."
+1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)."
+1. Configure your workflow's YAML to use `actions/checkout@v2`.
+1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md
new file mode 100644
index 0000000000..a0b7abb740
--- /dev/null
+++ b/translations/ja-JP/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: GitHub Enterprise guides
+shortTitle: ガイド
+intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md
index 6d0f564a05..faa073e0bd 100644
--- a/translations/ja-JP/content/admin/index.md
+++ b/translations/ja-JP/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: Enterprise 管理者
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
+title: GitHub Enterprise Documentation
+shortTitle: GitHub Enterprise
 intro: '{% data variables.product.product_name %} を{% if enterpriseServerVersions contains currentVersion %}デプロイ、{% endif %}設定{% if enterpriseServerVersions contains currentVersion %}、{% endif %}管理する Enterprise 管理者、システム管理者、およびセキュリティスペシャリスト向けのドキュメントとガイドです。'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/ja-JP/content/admin/installation/index.md b/translations/ja-JP/content/admin/installation/index.md
index 13e16e4c47..0713658365 100644
--- a/translations/ja-JP/content/admin/installation/index.md
+++ b/translations/ja-JP/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 詳しい情報または {% data variables.product.prodname_enterprise %} の購入については [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) を参照してください。
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md b/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md
index 5c7f22a67a..59c5195b96 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/ja-JP/content/admin/overview/about-data-residency.md b/translations/ja-JP/content/admin/overview/about-data-residency.md
index 2413448b0e..535be581b3 100644
--- a/translations/ja-JP/content/admin/overview/about-data-residency.md
+++ b/translations/ja-JP/content/admin/overview/about-data-residency.md
@@ -3,6 +3,10 @@ title: データの常駐について
 intro: '{% data variables.product.product_name %} は Enterprise のすべての顧客データを保存する地域を選択できます。'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %}{% data variables.product.product_location %} のすべての顧客データを保存する地域を選択できます。そして、Enterprise のメンバーは世界中のどこからでも {% data variables.product.product_name %} にアクセスできます。
diff --git a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md
index f70a9cc9e3..d64352706b 100644
--- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md
@@ -7,8 +7,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
+type: overview
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### {% data variables.product.product_name %} の Enterprise アカウントについて
diff --git a/translations/ja-JP/content/admin/overview/about-github-ae.md b/translations/ja-JP/content/admin/overview/about-github-ae.md
index 925ffc5123..f1b5848d1a 100644
--- a/translations/ja-JP/content/admin/overview/about-github-ae.md
+++ b/translations/ja-JP/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: GitHub AE について
 intro: '{% data variables.product.prodname_ghe_managed %} は、クラウドで {% data variables.product.prodname_dotcom %} を使用するためにセキュリティが強化された準拠した方法です。'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### {% data variables.product.prodname_ghe_managed %} について
@@ -21,7 +25,7 @@ versions:
 
 ### 指定の条件下での暗号化
 
-すべての顧客データは保存時に暗号化され、暗号化ポリシーに基づいてデータを暗号化するための独自の暗号化キーを提供できます。 キーとすべてのデータへのアクセスを制御できます。 詳しい情報については、「[Enterprise 向けのデータ暗号化を設定する](/admin/configuration/configuring-data-encryption-for-your-enterprise)」を参照してください。
+All customer data is encrypted at rest. 詳しい情報については、「[Enterprise 向けのデータ暗号化を設定する](/admin/configuration/configuring-data-encryption-for-your-enterprise)」を参照してください。
 
 ### 分離されたアカウント
 
diff --git a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md
index ee21bff90c..09eccbfe7e 100644
--- a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,8 +5,10 @@ intro: '{% if currentVersion == "github-ae@latest" %}{% data variables.product.p
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_name %} は常に改善されており、メジャーリリースとマイナーリリースで新機能とバグ修正が導入されています。 {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} はフルマネージドサービスであるため、{% data variables.product.company_short %} が Enterprise のアップグレードプロセスを完了します。{% endif %}
diff --git a/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md
index 761fc2ee84..5bbd2d9a73 100644
--- a/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ topics:
 | ユーザ       | ライセンスされた日                       | カウント日数 | 料金     |
 | --------- | ------------------------------- | ------ | ------ |
 | @octocat  | 1月1日～1月31日                      | 31     | $39    |
-| @robocat  | 2月1日～2月28日                      | 29     | $35.23 |
+| @robocat  | 2月1日～2月28日                      | 28     | $35.23 |
 | @devtocat | 1月15日～1月31日                     | 17     | $21.39 |
 | @doctocat | 1月1日～1月15日                      | 31     | $39    |
 | @prodocat | 1月7日～1月15日                      | 25     | $31.45 |
 | @monalisa | 1月1日～1月7日、<br>1月15日～1月31日 | 31     | $39    |
 
-Enterprise には、1つ以上のインスタンスを含めることができます。 {% data variables.product.prodname_ghe_managed %} のインスタンスごとの最小ユーザ数は 500 です。 {% data variables.product.company_short %} は、同日にライセンスを付与されたユーザが 500 未満の場合でも、インスタンスごとに最低 500 ユーザ分の料金を請求します。
+{% data variables.product.prodname_ghe_managed %} のインスタンスごとの最小ユーザ数は 500 です。 {% data variables.product.company_short %} は、同日にライセンスを付与されたユーザが 500 未満の場合でも、インスタンスごとに最低 500 ユーザ分の料金を請求します。
 
 [Azure アカウントポータル](https://portal.azure.com)で現在の使用状況を確認できます。
 
diff --git a/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md b/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md
index 5efebdf9b7..bd512c316c 100644
--- a/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/ja-JP/content/admin/overview/managing-your-github-enterprise-license.md
@@ -56,7 +56,7 @@ topics:
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
 3. 左のサイドバーで、** Enterprise licensing（Enterpriseライセンス）**をクリックしてください。 ![[Enterprise account settings] サイトバーの "Enterprise licensing"](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-4. 現在の {% data variables.product.prodname_enterprise %} ライセンスと、使用済みで利用可能なユーザライセンスを確認します。
+4. 現在の {% data variables.product.prodname_enterprise %} ライセンスと、使用済みで利用可能なユーザライセンスを確認します。 {% if currentVersion ver_gt "enterprise-server@3.0" %}If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
 
 ### ユーザライセンスの使用状況を自動で{% data variables.product.prodname_ghe_cloud %}と同期する
 
diff --git a/translations/ja-JP/content/admin/overview/system-overview.md b/translations/ja-JP/content/admin/overview/system-overview.md
index ad4bf59eaf..355f31a8e8 100644
--- a/translations/ja-JP/content/admin/overview/system-overview.md
+++ b/translations/ja-JP/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### ストレージアーキテクチャ
diff --git a/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index b1c5a2b531..69e19d7319 100644
--- a/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 3a6756e8a0..138bb29d51 100644
--- a/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: Enterprise 向けの GitHub Packages を使い始める
+shortTitle: Getting started with GitHub Packages
 intro: 'この機能の有効化、サードパーティのストレージの設定、サポートするエコシステムの設定、TLS 証明書の更新を行い、{% data variables.product.product_location %} で {% data variables.product.prodname_registry %} を使用開始します。'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index e7f38a442c..81843484fd 100644
--- a/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: GitHub Packages の MinIO ストレージバケットを設定するた
 intro: '{% data variables.product.prodname_registry %} で使用するためにカスタム MinIO ストレージバケットを設定します。'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/ja-JP/content/admin/policies/about-pre-receive-hooks.md b/translations/ja-JP/content/admin/policies/about-pre-receive-hooks.md
index a36b2ac0bf..d1a72aeeda 100644
--- a/translations/ja-JP/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/ja-JP/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 プッシュが行われると、各スクリプトは分離された環境で実行され、プッシュの内容についてのチェックを実行できます。 このスクリプトの終了ステータスが0ならプッシュは受け付けられ、0以外なら拒否されることになります。
diff --git a/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-environment.md
index 0dfba3fe4f..bbda3a090d 100644
--- a/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 {% data variables.product.prodname_ghe_server %} の pre-receive 環境は、Linux の [`chroot`](https://en.wikipedia.org/wiki/Chroot) 環境です。 pre-receiveフックはプッシュのイベントごとに実行されるので、高速かつ軽量でなければなりません。 こうしたチェックに必要となる環境は、通常最小限のものです。
diff --git a/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md
index 0dc18a5b3c..fc7fbb3885 100644
--- a/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/ja-JP/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 {% data variables.product.prodname_ghe_server %} の pre-receive フックの例は、[`github/platform-samples`リポジトリ](https://github.com/github/platform-samples/tree/master/pre-receive-hooks)で見ることができます。
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index cc136c3c5f..223ac52332 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,13 +5,20 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### {% data variables.product.prodname_GH_advanced_security %} について
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
-### Enforcing a policy for {% data variables.product.prodname_advanced_security %} features
+### {% data variables.product.prodname_advanced_security %} 機能のポリシーを施行する
 
 {% data reusables.advanced-security.about-ghas-organization-policy %}
 
diff --git a/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 74196f9714..4da7b09e19 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Enterprise 内の新しいリポジトリのデフォルトの可視性を設定する
diff --git a/translations/ja-JP/content/admin/policies/index.md b/translations/ja-JP/content/admin/policies/index.md
index 2d25247a95..8f93e954f1 100644
--- a/translations/ja-JP/content/admin/policies/index.md
+++ b/translations/ja-JP/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/ja-JP/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/ja-JP/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 7ac69fa553..631a36d2fa 100644
--- a/translations/ja-JP/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/ja-JP/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### pre-receiveフックの作成
diff --git a/translations/ja-JP/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/ja-JP/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..4d6b5b3d39
--- /dev/null
+++ b/translations/ja-JP/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Enterprise アカウントのメール制限について
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Enterprise アカウントのメール通知を制限する
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/ja-JP/content/admin/release-notes.md b/translations/ja-JP/content/admin/release-notes.md
index 9392f1a854..67a1107264 100644
--- a/translations/ja-JP/content/admin/release-notes.md
+++ b/translations/ja-JP/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/ja-JP/content/admin/user-management/about-migrations.md b/translations/ja-JP/content/admin/user-management/about-migrations.md
index 80d1c1c12e..df735ae4e2 100644
--- a/translations/ja-JP/content/admin/user-management/about-migrations.md
+++ b/translations/ja-JP/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### 移行の種類
diff --git a/translations/ja-JP/content/admin/user-management/adding-people-to-teams.md b/translations/ja-JP/content/admin/user-management/adding-people-to-teams.md
index e8055cda77..731fef16ec 100644
--- a/translations/ja-JP/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/ja-JP/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: 'Team が作成されると、Organization の管理者はユーザを {% data variables.product.product_location %} から Team に追加し、どのリポジトリにアクセスできるようにするかを決定できます。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 各Teamには、それぞれに定義された[Organizatinが所有するリポジトリへのアクセス権限](/articles/permission-levels-for-an-organization)があります。
diff --git a/translations/ja-JP/content/admin/user-management/audit-logging.md b/translations/ja-JP/content/admin/user-management/audit-logging.md
index 6497a97011..81e196253a 100644
--- a/translations/ja-JP/content/admin/user-management/audit-logging.md
+++ b/translations/ja-JP/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 特定のアクションを見つける方法について詳しくは、「[Audit log を検索する](/admin/user-management/searching-the-audit-log)」を参照してください。
diff --git a/translations/ja-JP/content/admin/user-management/audited-actions.md b/translations/ja-JP/content/admin/user-management/audited-actions.md
index 67a0e81cba..a36ecc0932 100644
--- a/translations/ja-JP/content/admin/user-management/audited-actions.md
+++ b/translations/ja-JP/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### 認証
diff --git a/translations/ja-JP/content/admin/user-management/auditing-ssh-keys.md b/translations/ja-JP/content/admin/user-management/auditing-ssh-keys.md
index 824a88e923..e110848bdf 100644
--- a/translations/ja-JP/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/ja-JP/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 監査が開始されると、現在の SSHキーがすべて無効となります。リポジトリのクローン、プル、プッシュといった操作をするためには、ユーザは SSH キーの承認または拒否をしなければなりません。 監査は、従業員の退職時や請負業者の撤収時など、すべてのキーを検証する必要があるときに役立ちます。
diff --git a/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md
index 1190d0e4ee..decae244b0 100644
--- a/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### Audit log にアクセスする
diff --git a/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md b/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md
index 5a66b05100..842e8e2568 100644
--- a/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/ja-JP/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index 3335ee1f09..ed70fc6247 100644
--- a/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### {% data variables.large_files.product_name_long %}について
diff --git a/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md
index 13d5f894ee..4d4cd4ed4f 100644
--- a/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/ja-JP/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ja-JP/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/ja-JP/content/admin/user-management/continuous-integration-using-jenkins.md
index 2111a5a8d5..6909a283f4 100644
--- a/translations/ja-JP/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/ja-JP/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/user-management/creating-teams.md b/translations/ja-JP/content/admin/user-management/creating-teams.md
index 01557bdd45..7d9052e9bb 100644
--- a/translations/ja-JP/content/admin/user-management/creating-teams.md
+++ b/translations/ja-JP/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Teamは、team@メンションのように適切なグループに入力や注目を求めたい場合に通知をするような、{% data variables.product.prodname_dotcom %}のコラボレーションの機能の多くにおいて中心的な役割を果たします。 詳しい情報については[Organizationのリポジトリの権限レベル](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)を参照してください。
diff --git a/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index 99f435d63c..5b54c8248a 100644
--- a/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: Enterprise のユーザメッセージをカスタマイズする
+shortTitle: Customizing user messages
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: '{% data variables.product.product_location %} でユーザに表示さ
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### ユーザメッセージについて
diff --git a/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index 4e4382262f..3c300293cb 100644
--- a/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: Enterprise 内の特定のリポジトリまたはすべてのリポジ
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### 特定のリポジトリへのGit SSHアクセスの無効化
diff --git a/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md
index 12b64881f6..2ddda00167 100644
--- a/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### {% data variables.product.prodname_dotcom %} でソース Organization を準備する
diff --git a/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index 7153a7ca78..32dd92a4b9 100644
--- a/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### {% data variables.product.prodname_ghe_server %} ソースインスタンスを準備する
diff --git a/translations/ja-JP/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/ja-JP/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 21e343c9ef..6f588f97fc 100644
--- a/translations/ja-JP/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/ja-JP/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Mercurialからのプロジェクトのインポート
diff --git a/translations/ja-JP/content/admin/user-management/log-forwarding.md b/translations/ja-JP/content/admin/user-management/log-forwarding.md
index 926b33f8a1..b41849e96c 100644
--- a/translations/ja-JP/content/admin/user-management/log-forwarding.md
+++ b/translations/ja-JP/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 syslog-style 式のログストリームに対応するログ回収システムは、サポートしています。（例えば、[Logstash](http://logstash.net/) や [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)など）
diff --git a/translations/ja-JP/content/admin/user-management/managing-dormant-users.md b/translations/ja-JP/content/admin/user-management/managing-dormant-users.md
index 364eb0bdc9..98d20d6fee 100644
--- a/translations/ja-JP/content/admin/user-management/managing-dormant-users.md
+++ b/translations/ja-JP/content/admin/user-management/managing-dormant-users.md
@@ -9,8 +9,11 @@ intro: 'ユーザアカウントが少なくとも 1 か月間アクティブに
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 「活動」には以下のことが含まれますが、以下に限定はされません:
diff --git a/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md b/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md
index 523c3b9edb..4fb8112c01 100644
--- a/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### グローバルwebhookについて
diff --git a/translations/ja-JP/content/admin/user-management/managing-projects-using-jira.md b/translations/ja-JP/content/admin/user-management/managing-projects-using-jira.md
index d9aafafec1..5f228be5b1 100644
--- a/translations/ja-JP/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/ja-JP/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: JIRA を使用してプロジェクトを管理する
-intro: 'プロジェクト管理用に {% data variables.product.prodname_enterprise %}に JIRA を統合することができます。'
+title: Managing projects using Jira
+intro: 'You can integrate Jira with {% data variables.product.prodname_enterprise %} for project management.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### {% data variables.product.prodname_enterprise %}のOrganizationへの JIRA の繋ぎ方
+### Connecting Jira to a {% data variables.product.prodname_enterprise %} organization
 
-1. http[s]://[hostname]/login で {% data variables.product.prodname_enterprise %}のアカウントにサインインする。
-1. ページ右上にあるアカウント設定のアイコン（歯車）をクリックする。
-1. 左のサイドバーで、あなたのOrganizationの名前をクリックする。
-1. 左のサイドバーで、**Applications（アプリケーション）** をクリックしてください。
-1. **Organization applications** のボックスの右上隅にある、**Register new application** をクリックする。
-1. アプリケーションの設定を次のように記入する。
-    - **Application name** の欄に "JIRA" と入力する。
-    - **Homepage URL** の欄には、JIRA インスタンスの全 URL を入力する。
-    - **Authorization callback URL** の欄には、JIRAインスタンスの全URLを入力する。
-1. **Register application** をクリックする。
-1. ページの上部の [**Client ID**] と [**Client Secret**] をメモしてください。 これらは JIRA のインスタンスの設定に必要です。
+1. http[s]://[hostname]/login で {% data variables.product.prodname_enterprise %}のアカウントにサインインする。 If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
+2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira.
 
-### JIRA インスタンス を設定
+  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. JIRA インスタンス で、管理人権限でアカウントにログインする。
-1. ページ上部の、設定アイコン（歯車）をクリックする。
-1. 設定のドロップダウンで、**Add-ons** を選択する。
-1. 左のサイドバーにある**Source control** で、**DVCS accounts** をクリックする。
-1. **Link Bitbucket or GitHub account** をクリックする。
-1. [**Add New Account**] (新規アカウントを追加) モーダルで、{% data variables.product.prodname_enterprise %} の設定を記入してください。
-    - **Host** のドロップダウンメニューで、**GitHub Enterprise** を選択する。
+3. Click on the **Edit _organization name_ settings** link.
+
+  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
+
+  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Click on the **Register new application** button.
+
+  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. アプリケーションの設定を次のように記入する。
+    - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance.
+    - In the **Homepage URL** field, type the full URL of your Jira instance.
+    - In the **Authorization callback URL** field, type the full URL of your Jira instance.
+7. **Register application** をクリックする。
+8. ページの上部の [**Client ID**] と [**Client Secret**] をメモしてください。 You will need these for configuring your Jira instance.
+
+### Jira instance configuration
+
+1. On your Jira instance, log into an account with administrative access.
+2. At the top of the page, click the settings (gear) icon and choose **Applications**.
+
+  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
+
+  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
+
+  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. [**Add New Account**] (新規アカウントを追加) モーダルで、{% data variables.product.prodname_enterprise %} の設定を記入してください。
+    - From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**.
     - **Team or User Account** の欄には、{% data variables.product.prodname_enterprise %}のOrganization、または個人アカウントの名前を入力する。
     - **OAuth Key** の欄には、{% data variables.product.prodname_enterprise %}のディベロッパーアプリケーションのClient ID を入力する。
     - **OAuth Secret** の欄には、{% data variables.product.prodname_enterprise %}のデベロッパーアプリケーションの Client Secret を入力する。
-    - {% data variables.product.prodname_enterprise %}の Organization、または個人アカウントが所有している新規リポジトリをリンクしたくない場合は、**Auto Link New Repositories** の選択を解除する。
-    - スマートコミットを有効にしたくない場合は、**Enable Smart Commits** の選択を解除する。
+    - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, deselect **Auto Link New Repositories**.
+    - If you don't want to enable smart commits, deselect **Enable Smart Commits**.
     - [**Add**] をクリックします。
-1. {% data variables.product.prodname_enterprise %}に対して与えるアクセス権を確認して、**Authorize application** をクリックする。
-1. 必要であれば、パスワードを入力する。
+6. {% data variables.product.prodname_enterprise %}に対して与えるアクセス権を確認して、**Authorize application** をクリックする。
+7. 必要であれば、パスワードを入力する。
diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md
index 909e1f564c..e67d2e5e77 100644
--- a/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### インポートしたデータを {% data variables.product.prodname_ghe_server %} に適用する
diff --git a/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md
index 7efd1cc7c9..355e15861c 100644
--- a/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### インターナルリポジトリについて
@@ -34,6 +38,12 @@ topics:
 ### 移行の実施
 
 1. 管理シェルに接続します。 詳しい情報については「[管理シェル（SSH）にアクセスする](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)」を参照してください。
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. 移行コマンドを実行してください。
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. `/data/github/current`ディレクトリにアクセスしてください。
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ topics:
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 ログの出力は、ターミナルと`/tmp/convert_public_ghes_repos_to_internal.log`に対して行われます。
 
diff --git a/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index 27ba622519..14e1d8c9fd 100644
--- a/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 通常は、誰かがリポジトリを削除するとそのリポジトリは90日間はディスク上にあり、サイト管理ダッシュボード経由でリストアできます。 90日を過ぎると、そのリポジトリはパージされ、恒久的に削除されます。 ユーザあるいはOrganizationに訴訟ホールドを配置すると、所有しているリポジトリは無期限にリストアできるようになります。
diff --git a/translations/ja-JP/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index b4e6db1bb8..b0d8c7d9e0 100644
--- a/translations/ja-JP/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### 移行したデータを {% data variables.product.prodname_ghe_server %} にインポートするための準備
diff --git a/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md
index 719c1f4f43..45bee5f043 100644
--- a/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: ユーザが Enterprise 内に Organization を作成できないよう
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/ja-JP/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/ja-JP/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index d5fcf9fdb6..826ea0e6c9 100644
--- a/translations/ja-JP/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/ja-JP/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: サイト管理者は、任意の通常ユーザアカウントをサイト管理者に昇格させることや、他のサイト管理者を通常のユーザに降格させることができます。
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/ja-JP/content/admin/user-management/rebuilding-contributions-data.md b/translations/ja-JP/content/admin/user-management/rebuilding-contributions-data.md
index 26859c295c..9075226ad3 100644
--- a/translations/ja-JP/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/ja-JP/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 コミットは、{% data variables.product.prodname_enterprise %}にプッシュされるたびに、プッシュのメールアドレスとユーザのメールアドレスが同じ場合は、ユーザアカウントに関連付けられます。 しかし、ユーザが新規メールアドレスの登録や新規アカウントの作成をした場合、既存のコミットは、遡及的には関連付けられ*ません*。
diff --git a/translations/ja-JP/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/ja-JP/content/admin/user-management/removing-users-from-teams-and-organizations.md
index ded99eda3a..0b3f197aa8 100644
--- a/translations/ja-JP/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/ja-JP/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Organizationのメンバーを削除できるのは、オーナーもしくはTeamの管理者のみです。 ユーザがTeamもしくはOrganizationから削除されても、Organizationのリポジトリ内のそのユーザのIssue、プルリクエスト、コメントはそのまま残り、ユーザのもののままです。
diff --git a/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index 22833b87f9..0476f3a77d 100644
--- a/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 LDAP またはビルトイン認証を使用している場合、{% data variables.product.product_location %} で 2 要素認証がサポートされます。 Organizationの管理者は、メンバーに対して2要素認証の有効化を必須とすることができます。
diff --git a/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md b/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md
index 9f9656033b..f32806a9d9 100644
--- a/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### 検索クエリの構文
diff --git a/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md
index 013a5d8169..0fbc329e73 100644
--- a/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'ユーザが企業を離れたり異動したりした場合には、{% data variables.product.product_location %} に対するそのユーザのアクセス権を削除したり変更したりしなければなりません。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 従業員が企業を退職した場合、その{% data variables.product.prodname_ghe_server %}アカウントをサスペンドすれば、{% data variables.product.prodname_enterprise %}ライセンス中のユーザライセンスを空けながら、Issue、コメント、リポジトリ、Gist、そしてそのユーザが作成した他のデータを保持しておくことができます。 サスペンドされたユーザはインスタンスにサインインすることも、コードをプッシュやプルすることもできません。
diff --git a/translations/ja-JP/content/admin/user-management/viewing-push-logs.md b/translations/ja-JP/content/admin/user-management/viewing-push-logs.md
index 89ca8147c7..85db3b7063 100644
--- a/translations/ja-JP/content/admin/user-management/viewing-push-logs.md
+++ b/translations/ja-JP/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 プッシュログの項目には次の情報が含まれています。
diff --git a/translations/ja-JP/content/code-security/getting-started/about-securing-your-repository.md b/translations/ja-JP/content/code-security/getting-started/about-securing-your-repository.md
index 8163a17409..55fe516a60 100644
--- a/translations/ja-JP/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/ja-JP/content/code-security/getting-started/about-securing-your-repository.md
@@ -20,38 +20,40 @@ topics:
 {% data variables.product.prodname_dotcom %} には、コードを安全に保つために役立つセキュリティ機能が追加されています。 これらは、リポジトリの [**セキュリティ**] タブにあります。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-#### Available for all repositories
+#### すべてのリポジトリで使用可能
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **セキュリティポリシー**
 
-  リポジトリで見つけたセキュリティの脆弱性を内密に報告しやすくします。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)」を参照してください。
+  Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/code-security/getting-started/adding-a-security-policy-to-your-repository)」を参照してください。
+{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **セキュリティアドバイザリ**
 
   リポジトリのコードのセキュリティの脆弱性について、非公開で議論して修正します。 その後、セキュリティアドバイザリを公開して、コミュニティに脆弱性を警告し、アップグレードするように促すことができます。 詳しい情報については「[{% data variables.product.prodname_security_advisories %}について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。
 
-- **{% data variables.product.prodname_dependabot_alerts %} and security updates**
+- **{% data variables.product.prodname_dependabot_alerts %} およびセキュリティアップデート**
 
-  セキュリティの脆弱性を含むことを把握している依存関係に関するアラートを表示し、プルリクエストを自動的に生成してこれらの依存関係を更新するかどうかを選択します。 For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+  セキュリティの脆弱性を含むことを把握している依存関係に関するアラートを表示し、プルリクエストを自動的に生成してこれらの依存関係を更新するかどうかを選択します。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」 および「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。
  {% endif %}
 
 {% if currentVersion ver_gt "enterprise-server@2.22" %}
 - **{% data variables.product.prodname_dependabot_alerts %}**
 
-  View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
+  セキュリティの脆弱性を含むことを把握している依存関係に関するアラートを表示し、それらのアラートを管理します。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
   {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-- **{% data variables.product.prodname_dependabot %} version updates**
+- **{% data variables.product.prodname_dependabot %} バージョンアップデート**
 
-  Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. 詳しい情報については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
+  Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. これは、依存関係の古いバージョンの公開を減らすために役立ちます。 新しいバージョンを使用すると、セキュリティの脆弱性が発見された場合にパッチの適用が容易になり、さらに脆弱性のある依存関係を更新するため {% data variables.product.prodname_dependabot_security_updates %} がプルリクエストを発行することも容易になります。 詳しい情報については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
   {% endif %}
   {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
-#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %}
+#### {% if currentVersion == "free-pro-team@latest" %}パブリックリポジトリおよび{% endif %}{% data variables.product.prodname_advanced_security %} が有効になっているリポジトリで使用可能
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
@@ -63,7 +65,7 @@ These features are available {% if currentVersion == "free-pro-team@latest" %}fo
 
 - **{% data variables.product.prodname_secret_scanning_caps %} アラート**
 
-  {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. リポジトリにチェックインされたトークンまたは資格情報は、侵害されたものとして扱う必要があります。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。
+  {% if currentVersion == "free-pro-team@latest" %}プライベートリポジトリで、{% else %}{% endif %}any secrets that {% data variables.product.prodname_dotcom %} がコードで見つけたシークレットを表示します。 リポジトリにチェックインされたトークンまたは資格情報は、侵害されたものとして扱う必要があります。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。
 
 {% endif %}
 
@@ -78,7 +80,7 @@ These features are available {% if currentVersion == "free-pro-team@latest" %}fo
 * リポジトリが依存しているエコシステムとパッケージ
 * リポジトリに依存しているリポジトリとパッケージ
 
-You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %}
+{% data variables.product.prodname_dotcom %} がセキュリティの脆弱性のある依存関係に対して {% data variables.product.prodname_dependabot_alerts %} を生成する前に、依存関係グラフを有効にする必要があります。 {% if currentVersion == "free-pro-team@latest" %} 依存関係グラフを有効にすると、{% data variables.product.prodname_dotcom %} はプルリクエストの依存関係レビューも実行します。{% endif %}
 
 依存関係グラフは、リポジトリの [**Insights**] タブにあります。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..d05db4c0c0
--- /dev/null
+++ b/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: リポジトリにセキュリティポリシーを追加する
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### セキュリティポリシーについて
+
+To give people instructions for reporting security vulnerabilities in your project,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+所属する Organization またはユーザアカウント用にデフォルトのセキュリティポリシーを作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。
+{% endif %}
+
+{% tip %}
+
+**ヒント:** セキュリティポリシーを見つけやすくするために、README ファイルなど、リポジトリの他の場所から _SECURITY.md_ ファイルへリンクすることができます。 詳細は「[README について](/articles/about-readmes)」を参照してください。
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+プロジェクトのセキュリティの脆弱性が報告された後、{% data variables.product.prodname_security_advisories %} を使用して脆弱性に関する情報を開示、修正、公開できます。 For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." {% data variables.product.prodname_security_advisories %} の詳細については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+### リポジトリにセキュリティポリシーを追加する
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**. ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. [**Start setup**] をクリックします。 ![[Start setup] ボタン](/assets/images/help/security/start-setup-security-policy-button.png)
+5. 新しい _SECURITY.md_ ファイルに、プロジェクトがサポートするバージョンと、脆弱性を報告する方法についての情報を追加します。
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### 参考リンク
+
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/ja-JP/content/code-security/getting-started/index.md b/translations/ja-JP/content/code-security/getting-started/index.md
index 119b4df1bb..7b04c42ce5 100644
--- a/translations/ja-JP/content/code-security/getting-started/index.md
+++ b/translations/ja-JP/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### 目次
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md
index 626ada9248..2300aaf88d 100644
--- a/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md
@@ -53,19 +53,19 @@ Service providers can partner with {% data variables.product.company_short %} to
 
 - {% data variables.product.prodname_dotcom %} は、リポジトリ管理者と Organizationのオーナーにメールアラートを送信します。
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
-- {% data variables.product.prodname_dotcom %} sends an email alert to the contributor who committed the secret to the repository, with a link to the related {% data variables.product.prodname_secret_scanning %} alert. The commit author can then view the alert in the repository, and resolve the alert.
+- {% data variables.product.prodname_dotcom %} は、シークレットをリポジトリにコミットしたコントリビューターに、関連する {% data variables.product.prodname_secret_scanning %} アラートのリンクを記載したメールアラートを送信します。 コミット作者は、リポジトリでこのアラートを表示して、アラートを解決できます。
 {% endif %}
-- {% data variables.product.prodname_dotcom %} displays an alert in the repository.{% if currentVersion == "enterprise-server@3.0" %} For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %}
+- {% data variables.product.prodname_dotcom %} は、リポジトリのアラートを表示します。{% if currentVersion == "enterprise-server@3.0" %}詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 For more information about viewing and resolving {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %}
 
-Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。
+リポジトリ管理者と Organization のオーナーは、ユーザおよび Team に {% data variables.product.prodname_secret_scanning %} アラートへのアクセスを許可できます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %}
+To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. API に関する詳しい情報については、「[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)」を参照してください。{% endif %}
 
-{% data variables.product.prodname_dotcom %}  currently scans{% if currentVersion == "free-pro-team@latest" %} private{% endif %} repositories for secrets issued by the following service providers.
+現在 {% data variables.product.prodname_dotcom %} は、{% if currentVersion == "free-pro-team@latest" %} プライベート{% endif %} リポジトリをスキャンして、次のサービスプロバイダーが発行したシークレットを探します。
 
 {% data reusables.secret-scanning.partner-secret-list-private-repo %}
 
diff --git a/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index 953109822c..0bb3da54b2 100644
--- a/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring secret scanning for your repositories
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets.'
+title: リポジトリのシークレットスキャンを設定する
+intro: '{% data variables.product.prodname_dotcom %} がリポジトリでシークレットをスキャンする方法を設定できます。'
 permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.'
 redirect_from:
   - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories
@@ -20,30 +20,36 @@ topics:
 {% if currentVersion == "free-pro-team@latest" %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} is enabled by default on public repositories and cannot be turned off. You can configure {% data variables.product.prodname_secret_scanning %} for your private repositories only.
+**注釈:** パブリックリポジトリについては、{% data variables.product.prodname_secret_scanning_caps %} はデフォルトで有効であり、これを無効にすることはできません。 {% data variables.product.prodname_secret_scanning %} はプライベートリポジトリに対してのみ設定できます。
 
 {% endnote %}
 {% endif %}
 
-### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories
+### {% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリへの {% data variables.product.prodname_secret_scanning %} を有効化する
+
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization.
+{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. You may need to enable {% data variables.product.prodname_GH_advanced_security %} to activate the button for "{% data variables.product.prodname_secret_scanning_caps %}". To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% if currentVersion == "free-pro-team@latest" %}![リポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効化する](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. [{% data variables.product.prodname_secret_scanning_caps %}] と [**Enable**] ボタンが表示されている場合でも、[**Enable**] をクリックして {% data variables.product.prodname_secret_scanning %} を有効化する必要があります。 [**Disable**] ボタンが表示されている場合、{% data variables.product.prodname_secret_scanning %} はすでに有効化されています。 ![リポジトリに対して {% data variables.product.prodname_secret_scanning %} を有効化する](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
-7. To the right of "{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png)
+7. その場合、[{% data variables.product.prodname_secret_scanning_caps %}] の右にある [**Enable**] をクリックします。 ![リポジトリに対して {% data variables.product.prodname_secret_scanning %} を有効化する](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
 {% if currentVersion == "github-ae@latest" %}
-1. Before you can enable {% data variables.product.prodname_secret_scanning %}, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-ghae.png)
-2. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png)
-3. To the right of "{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-secret-scanning-ghae.png)
+1. {% data variables.product.prodname_secret_scanning %} を有効化する前に、まず {% data variables.product.prodname_GH_advanced_security %} を有効化する必要があります。 その場合、[{% data variables.product.prodname_GH_advanced_security %}] の右にある [**Enable**] をクリックします。 ![リポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効化する](/assets/images/enterprise/github-ae/repository/enable-ghas-ghae.png)
+2. [**Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**] をクリックして、処理を確認します。 ![リポジトリに対する {% data variables.product.prodname_GH_advanced_security %} の有効化を確認する](/assets/images/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png)
+3. その場合、[{% data variables.product.prodname_secret_scanning_caps %}] の右にある [**Enable**] をクリックします。 ![リポジトリに対して {% data variables.product.prodname_secret_scanning %} を有効化する](/assets/images/enterprise/github-ae/repository/enable-secret-scanning-ghae.png)
 {% endif %}
 
-### Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories
+### {% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリで {% data variables.product.prodname_secret_scanning %} からのアラートを除外する
 
 *secret_scanning.yml* ファイルを使用して、{% data variables.product.prodname_secret_scanning %} からディレクトリを除外できます。 たとえば、テストまたはランダムに生成されたコンテンツを含むディレクトリを除外できます。
 
@@ -66,7 +72,7 @@ topics:
 
     {% endnote %}
 
-{% data variables.product.prodname_secret_scanning %} からの個々のアラートを無視することもできます。 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)」を参照してください。
+{% data variables.product.prodname_secret_scanning %} からの個々のアラートを無視することもできます。 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)」を参照してください。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/ja-JP/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index acd6c18c90..bf7f94901b 100644
--- a/translations/ja-JP/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -14,16 +14,16 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-### アラートを管理する
+### Managing {% data variables.product.prodname_secret_scanning %} alerts
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. In the left sidebar, click **Secret scanning alerts**.
+3. 左サイトバーで、[**Secret scanning alerts**] をクリックします。
    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Secret scanning alerts" tab](/assets/images/help/repository/sidebar-secrets.png)
+   ![[Secret scanning alert] タブ](/assets/images/help/repository/sidebar-secrets.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
-   !["Secret scanning alerts" tab](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
+   ![[Secret scanning alert] タブ](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
    {% endif %}
 4. [Secret scanning] の下で、表示するアラートをクリックします。
    {% if currentVersion == "free-pro-team@latest" %}
@@ -35,7 +35,7 @@ topics:
    {% if currentVersion == "github-ae@latest" %}
    ![シークレットスキャンからのアラートのリスト](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
    {% endif %}
-5. Optionally, use the "Mark as" drop-down menu and click a reason for resolving an alert.
+5. 必要に応じて、[Mark as] ドロップダウンメニューを使用して、アラートを解決する理由をクリックします。
    {% if currentVersion == "free-pro-team@latest" %}
    ![シークレットスキャンからのアラートを解決するためのドロップダウンメニュー](/assets/images/help/repository/secret-scanning-resolve-alert.png)
    {% endif %}
@@ -49,3 +49,11 @@ topics:
 
 - 侵害された {% data variables.product.prodname_dotcom %} の個人アクセストークンについては、侵害されたトークンを削除し、新しいトークンを作成し、古いトークンを使っていたサービスを更新してください。 詳しい情報については[コマンドラインのための個人のアクセストークンの作成](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)を参照してください。
 - それ以外のすべてのシークレットについては、最初に {% data variables.product.product_name %} にコミットされたシークレットが有効であることを確認してください。 有効である場合は、新しいシークレットを作成し、古いシークレットを使用するサービスを更新してから、古いシークレットを削除します。
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.prodname_dotcom %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/secure-coding/about-code-scanning.md b/translations/ja-JP/content/code-security/secure-coding/about-code-scanning.md
index 00f8f62e61..fb8a04ac7e 100644
--- a/translations/ja-JP/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/ja-JP/content/code-security/secure-coding/about-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -22,11 +24,11 @@ topics:
 
 {% data variables.product.prodname_code_scanning %} を使用して、コード内の既存の問題の修正を検索し、トリアージして、優先順位を付けることができます。 また、{% data variables.product.prodname_code_scanning_capc %} は、開発者による新しい問題の発生も防ぎます。 スキャンを特定の日時にスケジュールしたり、プッシュなどの特定のイベントがリポジトリで発生したときにスキャンをトリガーしたりすることができます。
 
-{% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+{% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see  "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)."
+リポジトリまたは Organization をまたいで {% data variables.product.prodname_code_scanning %} による結果を監視するには、webhooks や {% data variables.product.prodname_code_scanning %} API を使用できます。 {% data variables.product.prodname_code_scanning %} 用の webhook に関する詳しい情報については、「[Webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)」を参照してください。 API に関する情報については、 「[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)」を参照してください。
 
-To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+{% data variables.product.prodname_code_scanning %} を始めるには、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
 
 ### {% data variables.product.prodname_codeql %} について
 
@@ -36,7 +38,7 @@ To get started with {% data variables.product.prodname_code_scanning %}, see "[S
 
 {% data variables.product.prodname_code_scanning %} の API エンドポイントについての詳細は、「[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)」を参照してください。
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 [`github/codeql`](https://github.com/github/codeql)リポジトリで {% data variables.product.prodname_code_scanning %} のクエリを表示して貢献できます。 詳しい情報については、 {% data variables.product.prodname_codeql %} ドキュメントの「[{% data variables.product.prodname_codeql %} クエリ](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/)」を参照してください。
 
@@ -48,17 +50,14 @@ To get started with {% data variables.product.prodname_code_scanning %}, see "[S
 
 {% endif %}
 
-### サードパーティのコードスキャンツールについて
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### About third-party {% data variables.product.prodname_code_scanning %} tools
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+You can run third-party analysis tools within {% data variables.product.product_name %} using actions or within an external CI system. For more information, see "[Setting up code scanning for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
 
 ### 参考リンク
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- 「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository)」
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - OASIS 委員会 の Web サイトの「[OASIS Static Analysis Results Interchange Format (SARIF) 」TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif)
diff --git a/translations/ja-JP/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..59019d9648
--- /dev/null
+++ b/translations/ja-JP/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %}詳細については、「[{% data variables.product.prodname_code_scanning %} について](/code-security/secure-coding/about-code-scanning)」を参照してください。
+
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using actions. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case.
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Codebases with a compiled language that can be built with a single command or by running a single script.
+
+詳しい情報については、「[{% data variables.product.prodname_codeql_cli %} を CI システムで実行する](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)」を参照してください。
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to:
+- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis.
+- Analyze more than one language in a repository.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+詳しい情報については、「[{% data variables.product.prodname_codeql_runner %} を CI システムで実行する](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください。
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/ja-JP/content/code-security/secure-coding/about-integration-with-code-scanning.md
index 68b91a1031..1e3d6c2af4 100644
--- a/translations/ja-JP/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/ja-JP/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -1,7 +1,7 @@
 ---
-title: About integration with code scanning
-shortTitle: About integration
-intro: 'You can perform {% data variables.product.prodname_code_scanning %} externally and then display the results in {% data variables.product.prodname_dotcom %}, or set up webhooks that listen to {% data variables.product.prodname_code_scanning %} activity in your repository.'
+title: コードスキャンとのインテグレーションについて
+shortTitle: インテグレーションについて
+intro: '{% data variables.product.prodname_code_scanning %} を外部で実行し、その結果を {% data variables.product.prodname_dotcom %} で表示できます。また、リポジトリで {% data variables.product.prodname_code_scanning %} アクティビティを監視する webhook をセットアップすることもできます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning
@@ -13,19 +13,21 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-As an alternative to running {% data variables.product.prodname_code_scanning %} within {% data variables.product.prodname_dotcom %}, you can perform analysis elsewhere and then upload the results. Alerts for {% data variables.product.prodname_code_scanning %} that you run externally are displayed in the same way as those for  {% data variables.product.prodname_code_scanning %} that you run within {% data variables.product.prodname_dotcom %}. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+{% data variables.product.prodname_code_scanning %} を {% data variables.product.prodname_dotcom %} 内で実行する他に、分析を別の場所で実行して、その結果をアップロードすることもできます。 外部で実行した {% data variables.product.prodname_code_scanning %} のアラートは、{% data variables.product.prodname_dotcom %} 内で {% data variables.product.prodname_code_scanning %} を実行した場合と同じように表示されます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-If you use a third-party static analysis tool that can produce results as Static Analysis Results Interchange Format (SARIF) 2.1.0 data, you can upload this to {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/code-security/secure-coding/uploading-a-sarif-file-to-github)」を参照してください。
+Static Analysis Results Interchange Format (SARIF) 2.1.0 データとして結果を生成できるサードパーティの静的解析ツールを使用する場合、そのデータを {% data variables.product.prodname_dotcom %} にアップロードできます。 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/code-security/secure-coding/uploading-a-sarif-file-to-github)」を参照してください。
 
-### Integrations with webhooks
+### webhook とのインテグレーション
 
-You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. For example, you could build an integration that creates an issue on {% data variables.product.product_name %} or sends you a Slack notification when a new {% data variables.product.prodname_code_scanning %} alert is added in your repository. For more information, see "[Creating webhooks](/developers/webhooks-and-events/creating-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)."
+{% data variables.product.prodname_code_scanning %} webhook を使用して、リポジトリの {% data variables.product.prodname_code_scanning %} イベントにサブスクライブする、[{% data variables.product.prodname_github_app %}](/apps/building-github-apps/) や [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/) などのインテグレーションを構築またはセットアップできます。 たとえば、 {% data variables.product.product_name %} で Issue を作成するインテグレーションや、リポジトリに新たな {% data variables.product.prodname_code_scanning %} アラートが追加されたときに Slack 通知を送信するインテグレーションを構築できます。 詳しい情報については、「[webhook を作製すく](/developers/webhooks-and-events/creating-webhooks)」および「[webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)」を参照してください。
 
 ### 参考リンク
 
 * "[About code scanning](/code-security/secure-coding/about-code-scanning)"
-* "[Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system)"
+* 「[既存の CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を使用する](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system)」
 * "[SARIF support for code scanning](/code-security/secure-coding/sarif-support-for-code-scanning)"
diff --git a/translations/ja-JP/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/ja-JP/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index e38940f178..28707e401a 100644
--- a/translations/ja-JP/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/ja-JP/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md b/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md
index 88a106c919..05e28c8df3 100644
--- a/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring code scanning
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+title: コードスキャンを設定する
+intro: '{% data variables.product.prodname_dotcom %} がプロジェクトのコードをスキャンして脆弱性やエラーを検出する方法を設定できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
 miniTocMaxHeadingLevel: 4
@@ -11,55 +11,70 @@ versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
 topics:
-  - security
+  - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About {% data variables.product.prodname_code_scanning %} configuration
+### {% data variables.product.prodname_code_scanning %} の設定について
 
-You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+{%- else %}
+"[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}.
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
 
-Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+リポジトリに {% data variables.product.prodname_code_scanning %} を設定する前に、リポジトリに {% data variables.product.prodname_actions %} ワークフローを追加して {% data variables.product.prodname_code_scanning %} をセットアップする必要があります。 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+{% data variables.product.prodname_codeql %} 解析は、{% data variables.product.prodname_dotcom %} で実行できる {% data variables.product.prodname_code_scanning %} のほんの一例に過ぎません。 {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} は、リポジトリの _.github/workflows_ ディレクトリにワークフローファイルを保存します。 ファイル名を検索して、追加済みのワークフローを見つけることができます。 For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. リポジトリで、編集したいワークフローファイルにアクセスします。
+1. ファイルビューの右上隅の {% octicon "pencil" aria-label="The edit icon" %}をクリックしてワークフローエディタを開きます。 ![ワークフローファイルの編集ボタン](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. ファイルを編集したら、[**Start commit**] をクリックして、[Commit changes] フォームに入力します。 現在のブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択できます。 ![codeql.yml ワークフローの更新をコミットする](/assets/images/help/repository/code-scanning-workflow-update.png)
 
-For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+ワークフローファイルの編集に関する詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-### Configuring frequency
+### 頻度を設定する
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+スケジュール設定されているときや、リポジトリで特定のイベントが発生したときに、コードをスキャンできます。
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+リポジトリへのプッシュごと、およびプルリクエストが作成されるたびにコードをスキャンすることで、開発者がコードに新しい脆弱性やエラーをもたらすことを防ぎます。 スケジュールに従ってコードをスキャンすると、開発者がリポジトリを積極的に維持していない場合でも、{% data variables.product.company_short %}、セキュリティ研究者、コミュニティが発見した最新の脆弱性とエラーが通知されます。
 
-#### Scanning on push
+#### プッシュ時にスキャンする
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+デフォルトのワークフローを使用する場合、{% data variables.product.prodname_code_scanning %} は、イベントによってトリガーされるスキャンに加えて、リポジトリ内のコードを週に1回スキャンします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#on)」を参照してください。
 
-#### Scanning pull requests
+If you scan on push, then the results appear in the **Security** tab for your repository. 詳しい情報については、「[リポジトリの コードスキャンアラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+{% note %}
 
-For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below.
 
-#### Avoiding unnecessary scans of pull requests
+{% endnote %}
 
-You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+#### プルリクエストをスキャンする
+
+デフォルトの {% data variables.product.prodname_codeql_workflow %} は、`pull_request` イベントを使用して、デフォルトブランチに対するプルリクエストのコードスキャンをトリガーします。 {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+
+`pull_request` イベントに関する詳しい情報については、「"[{% data variables.product.prodname_actions %}のためのワークフローの構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。
+
+If you scan pull requests, then the results appear as alerts in a pull request check. 詳しい情報については、「[プルリクエストでコードスキャンアラートをトリアージする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
+
+#### プルリクエストの不要なスキャンを回避する
+
+どのファイルが変更されたかに関わらず、デフォルトブランチに対する特定のプルリクエストにコードスキャンがトリガーされることを避けたい場合もあるでしょう。 これを設定するには、{% data variables.product.prodname_code_scanning %} ワークフローで `on:pull_request:paths-ignore` または `on:pull_request:paths` を指定します。 たとえば、プルリクエストにおける変更が、`.md` または `.txt` のファイル拡張子を持つファイルである場合、次の `paths-ignore` 配列を使用できます。
 
 ``` yaml
 on:
@@ -74,28 +89,28 @@ on:
 
 {% note %}
 
-**Notes**
+**注釈**
 
-* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+* `on:pull_request:paths-ignore` と `on:pull_request:paths` は、ワークフローのアクションがプルリクエストで実行されるかどうかを決定する条件を設定します。 アクションが実行されたときにどのファイルが解析__されるかは決定しません。 プルリクエストに、`on:pull_request:paths-ignore` または `on:pull_request:paths` にマッチしないファイルが含まれている場合、ワークフローはそのアクションを実行し、`on:pull_request:paths-ignore` または `on:pull_request:paths` にマッチするものを含む、プルリクエストにおいて変更されたすべてのファイルをスキャンします。ただし、除外されているファイルは除きます。 ファイルを解析から除外する方法については、「[スキャンするディレクトリを指定する](#specifying-directories-to-scan)」を参照してください。
+* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} ワークフローファイルに対しては、`on:push` イベントで `paths-ignore` や `paths` といったキーワードは使用しないでください。解析に漏れが生じる恐れがあります。 正確な結果を得るには、{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} が新しい変更を前回のコミットの解析と比較できる必要があります。
 
 {% endnote %}
 
-For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+`on:pull_request:paths-ignore` と `on:pull_request:paths` を使用して、プルリクエストに対していつワークフローを実行するかを決定することに関する詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)」を参照してください。
 
-#### Scanning on a schedule
+#### スケジュールに従ってスキャンする
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`pull_request` イベントを使用して、プルリクエストの `HEAD` コミットでコードスキャンをトリガーします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onschedule)」を参照してください。
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+**注釈**: {% data variables.product.prodname_dotcom %} は、デフォルトのブランチのワークフローにあるスケジュール設定されたジョブのみを実行します。 他のブランチのワークフローでスケジュールを変更しても、ブランチをデフォルトブランチにマージするまで影響はありません。
 
 {% endnote %}
 
-#### Example
+#### サンプル
 
-The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+以下の例は、デフォルトブランチの名前が `main` で、`protected` という保護されたブランチがある特定のリポジトリに対する {% data variables.product.prodname_codeql_workflow %} を示しています。
 
 ``` yaml
 on:
@@ -107,14 +122,14 @@ on:
     - cron: '20 14 * * 1'
 ```
 
-This workflow scans:
-* Every push to the default branch and the protected branch
-* Every pull request to the default branch
+このワークフローは、次をスキャンします。
+* デフォルトブランチと保護されたブランチに対する全てのプッシュ
+* デフォルトブランチに対する全てのプルリクエスト
 * The default branch every Monday at 14:20 UTC
 
-### Specifying an operating system
+### オペレーティングシステムを指定する
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
+コードのコンパイルに特定のオペレーティングシステムが必要な場合は、そのオペレーティングシステムを {% data variables.product.prodname_codeql_workflow %} で設定できます。 `jobs.analyze.runs-on` の値を編集して、{% data variables.product.prodname_code_scanning %} のアクションを実行するマシンのオペレーティングシステムを指定します。 {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
 
 If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
 
@@ -127,15 +142,15 @@ jobs:
 
 {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+{% data variables.product.prodname_code_scanning_capc %} は、macOS、Ubuntu、Windows の最新バージョンをサポートしています。 Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
 
-### Changing the languages that are analyzed
+### 解析される言語を変更する
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
@@ -162,7 +177,7 @@ If your workflow does not contain a matrix called `language`, then {% data varia
     languages: cpp, csharp, python
 ```
 {% if currentVersion == "free-pro-team@latest" %}
-### Analyzing Python dependencies
+### 追加のクエリを実行する
 
 For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
 
@@ -176,39 +191,71 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
-### Running additional queries
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. 例:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. 詳しい情報については「[{% data variables.product.prodname_code_scanning %}の SARIF サポート](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)」を参照してください。
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
+### 追加のクエリを実行する
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
+1つ以上のクエリスイートを追加するには、設定ファイルに `queries` セクションを追加します。 If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
 
 {% raw %}
 ``` yaml
@@ -220,11 +267,11 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu
 ```
 {% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+設定ファイルでこれらを指定して、追加のクエリスイートを実行することもできます。 クエリスイートはクエリのコレクションであり、通常は目的または言語ごとにグループ化されています。
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。
 
 In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
 
@@ -238,11 +285,11 @@ In the following example, the `+` symbol ensures that the specified additional q
 ```
 {% endraw %}
 
-### Using a custom configuration file
+### サードパーティのコードスキャンツールを使用する
 
 As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
 
-In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. この例では、設定ファイル _./.github/codeql/codeql-config.yml_ を読み込みます。
 
 ``` yaml
 - uses: github/codeql-action/init@v1
@@ -264,7 +311,7 @@ with:
 
 The settings in the configuration file are written in YAML format.
 
-#### Specifying additional queries
+#### 追加のクエリを指定する
 
 You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
 
@@ -279,11 +326,11 @@ Optionally, you can give each array element a name, as shown in the example conf
 
 For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
 
-#### Disabling the default queries
+#### デフォルトのクエリを無効にする
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+カスタムクエリのみを実行する場合は、構成ファイルに `disable-default-queries: true` を追加して、デフォルトのセキュリティクエリを無効にすることができます。
 
-#### Specifying directories to scan
+#### スキャンするディレクトリを指定する
 
 For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
 
@@ -297,27 +344,28 @@ paths-ignore:
 
 {% note %}
 
-**Note**:
+**ノート**:
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)」を参照してください。
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. たとえば、`foo/**`、`**/foo`、および `foo/**/bar` はすべて使用できる構文ですが、`**foo` は使用できません。 ただし、例に示すように、単一の * を他の文字と一緒に使用できます。 You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
 
-For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. ビルドからディレクトリを除外するために使用するコマンドは、ビルドシステムによって異なります。 詳しい情報については、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+特定のディレクトリのコードを変更すると、monorepo の一部をすばやく分析できます。 ビルドステップでディレクトリを除外し、ワークフローファイルで [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) の`paths-ignore` および `paths` キーワードを使用する必要があります。
 
-#### Example configuration files
+#### 設定ファイルの例
 
 {% data reusables.code-scanning.example-configuration-files %}
 
-### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+### コンパイルされた言語の {% data variables.product.prodname_code_scanning %} を設定する
 
 {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)."
+{% data reusables.code-scanning.autobuild-add-build-steps %}コンパイルされた言語で {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を設定する方法に関する詳しい情報については、「[コンパイルされた言語の {% data variables.product.prodname_codeql %} を設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)」を参照してください。
 
-### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+### {% data variables.product.prodname_code_scanning %} 用の設定ファイルを作成できます。
 
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
+{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. ワークフローに `upload-sarif` アクションを追加することで、{% data variables.product.prodname_dotcom %} のサードパーティツールからのコード分析を表示できます。 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/code-security/secure-coding/uploading-a-sarif-file-to-github)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..c1e5d0feef
--- /dev/null
+++ b/translations/ja-JP/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,204 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configuring CodeQL runner
+intro: '{% data variables.product.prodname_codeql_runner %} がプロジェクトのコードをスキャンして、その結果を {% data variables.product.prodname_dotcom %} にアップロードする方法を設定できます。'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### CI システムにおける {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} の設定について
+
+{% data variables.product.prodname_code_scanning %} をお使いの CI システムに統合するには、{% data variables.product.prodname_codeql_runner %} を使用できます。 詳しい情報については、「[{% data variables.product.prodname_codeql_runner %} を CI システムで実行する](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください。
+
+一般的に、{% data variables.product.prodname_codeql_runner %} は次のように呼び出します。
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` は、{% data variables.product.prodname_codeql_runner %} を CI のどこにダウンロードしたかによって異なります。 `codeql-runner-OS` は、お使いのオペレーティングシステムによって異なります。
+{% data variables.product.prodname_codeql_runner %} には 3 つのバージョンがあり、`codeql-runner-linux`、`codeql-runner-macos`、`codeql-runner-win` がそれぞれ Linux、macOS、Windows のシステムに対応しています。
+
+{% data variables.product.prodname_codeql_runner %} がコードをスキャンする方法をカスタマイズするには、`--languages` や `--queries` などのフラグを用いるか、別の設定ファイルでカスタム設定を指定します。
+
+### プルリクエストをスキャンする
+
+プルリクエストが作成されるたびにコードをスキャンすることで、開発者がコードに新しい脆弱性やエラーを持ち込むことを防げます。
+
+プルリクエストをスキャンするには、 `analyze` コマンドを実行し、 `--ref` フラグを使用してプルリクエストを指定します。 リファレンスは `refs/pull/<PR-number>/head` または `refs/pull/<PR-number>/merge` で、プルリクエストブランチの HEAD コミットまたはベースブランチでマージコミットをチェックアウトしているかにより異なります。
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**注釈**: コードをサードパーティーのツールで解析し、その結果をプルリクエストのチェックで表示したい場合は、`upload` コマンドを実行し、`--ref` フラグでブランチではなくプルリクエストを指定する必要があります。 リファレンスは `refs/pull/<PR-number>/head` または `refs/pull/<PR-number>/merge` です。
+
+{% endnote %}
+
+### 自動言語検出をオーバーライドする
+
+{% data variables.product.prodname_codeql_runner %} は、サポートされている言語で記述されたコードを自動的に検出してスキャンします。
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+自動言語検出をオーバーライドするには、`init` コマンドに `--languages` フラグを付け、その後に言語のキーワードリストをカンマ区切りで追加して、実行します。 The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### 追加のクエリを実行する
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+1 つ以上ののクエリを追加するには、`init` コマンドの `--queries` フラグに、カンマで区切ったパスのリストを渡します。 設定ファイルに、追加のクエリを指定することもできます。
+
+カスタム設定にも設定ファイルを使用し、`--queries` フラグで追加のクエリも指定している場合、{% data variables.product.prodname_codeql_runner %} は、構成ファイルで指定されたものではなく、 <nobr>`--queries`</nobr> フラグで指定された追加クエリを使用します。 フラグで指定された追加クエリと、設定ファイルにある追加クエリを組み合わせて使用する場合、渡す値の前に <nobr>`--queries`</nobr> と `+` の記号をプレフィクスとして付けてください。 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。
+
+次の例では、{% data variables.product.prodname_codeql_runner %} が追加のクエリを、参照されている設定ファイルの中で指定されたあらゆるクエリと共に使用するよう、`+` の記号を用いています。
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### サードパーティのコードスキャンツールを使用する
+
+{% data variables.product.prodname_codeql_runner %} コマンドに追加情報を渡すかわりに、別の設定ファイルでカスタム設定を指定できます。
+
+設定ファイルの形式は YAML ファイルです。 YAML ファイルは、以下の例で示すように、{% data variables.product.prodname_actions %} のワークフロー構文と似た構文を使用します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)」を参照してください。
+
+`init` コマンドの `--config-file` フラグを使用して、設定ファイルを指定します。   <nobr>`--config-file`</nobr> の値は、使用する設定ファイルへのパスです。 この例では、設定ファイル _.github/codeql/codeql-config.yml_ を読み込みます。
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### 設定ファイルの例
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### コンパイルされた言語の {% data variables.product.prodname_code_scanning %} を設定する
+
+コンパイル言語の C/C++、C#、および Java では、{% data variables.product.prodname_codeql %} は解析前にコードをビルドします。 {% data reusables.code-scanning.analyze-go %}
+
+多くの一般的なビルドシステムに対して、{% data variables.product.prodname_codeql_runner %} はコードを自動的にビルドできます。 コードの自動的なビルドを試行するには、`init` と `analyze` のステップの間で `autobuild` を実行します。 リポジトリに特定のバージョンのビルドツールが必要な場合は、まずそのビルドツールを手動でインストールする必要があることにご注意ください。
+
+`autobuild` プロセスは、リポジトリに対して _1 つ_ のコンパイル型言語のみをビルドするよう試行します。 解析のために自動的に選択される言語は、使用されているファイル数が最も多い言語です。 言語を明示的に選択する場合は、`autobuild` コマンドの `--language` フラグを使用します。
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+`autobuild` コマンドがコードをビルドできない場合、`init` と`analyze` のステップの間にビルドのステップを手動で実行できます。 詳しい情報については、「[{% data variables.product.prodname_codeql_runner %} を CI システムで実行する](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)」を参照してください。
+
+### {% data variables.product.prodname_code_scanning %} 用の設定ファイルを作成できます。
+
+デフォルトでは、{% data variables.product.prodname_codeql_runner %} は `analyze` コマンドを実行した際の {% data variables.product.prodname_code_scanning %} による結果をアップロードします。 また、`upload` コマンドを使用して、SARIF ファイルを別にアップロードすることもできます。
+
+データをアップロードすると、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。
+- `--ref refs/pull/42/merge` や `--ref refs/pull/42/head` などのようにプルリクエストにアップロードした場合、結果はプルリクエストのチェックでアラートとして表示されます。 詳しい情報については、「[プルリクエストでコードスキャンアラートをトリアージする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
+- `--ref refs/heads/my-branch` といったようにブランチにアップロードした場合、結果はリポジトリの [**Security**] タブに表示されます。 詳しい情報については、「[リポジトリの コードスキャンアラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。
+
+### {% data variables.product.prodname_codeql_runner %} コマンドのリファレンス
+
+{% data variables.product.prodname_codeql_runner %} は、次のコマンドおよびフラグをサポートしています。
+
+#### `init`
+
+{% data variables.product.prodname_codeql_runner %} を初期化し、解析する各言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
+
+| フラグ                              | 必須 | 入力値                                                                                                                                                |
+| -------------------------------- |:--:| -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                   | ✓  | 初期化するリポジトリの名前。                                                                                                                                     |
+| `--github-url`                   | ✓  | リポジトリがホストされる {% data variables.product.prodname_dotcom %} のインスタンス。                                                                                 |
+| `--github-auth`                  | ✓  | {% data variables.product.prodname_github_apps %} トークンまたは個人アクセストークン。                                                                             |
+| `--languages`                    |    | 解析対象言語のカンマ区切りリスト。 デフォルトでは、{% data variables.product.prodname_codeql_runner %} はリポジトリにあるサポートされている言語をすべて検出し、解析します。                                 |
+| `--queries`                      |    | デフォルトのセキュリティクエリに加えて実行する、追加クエリのカンマ区切りリスト。                                                                                                           |
+| `--config-file`                  |    | カスタム設定ファイルのパス。                                                                                                                                     |
+| `--codeql-path`                  |    | 使用する {% data variables.product.prodname_codeql %} CLI 実行ファイルのコピーのパス。 デフォルトでは、{% data variables.product.prodname_codeql_runner %} はコピーをダウンロードします。 |
+| `--temp-dir`                     |    | 一時ファイルが保存されるディレクトリ。 デフォルトは `./codeql-runner` です。                                                                                                   |
+| `--tools-dir`                    |    | 実行間で {% data variables.product.prodname_codeql %} ツールやその他のファイルが保存されるディレクトリ。 デフォルトはホームディレクトリのサブディレクトリです。                                            |
+| <nobr>`--checkout-path`</nobr> |    | リポジトリをチェックアウトするパス。 デフォルトは現在のワーキングディレクトリです。                                                                                                         |
+| `--debug`                        |    | なし. より詳細な出力を表示します。                                                                                                                                 |
+| `-h`, `--help`                   |    | なし. コマンドのヘルプを表示します。                                                                                                                                |
+
+#### `autobuild`
+
+コンパイル型言語である C/C++、C#、および Java のコードのビルドを試行します。 これらの言語では、{% data variables.product.prodname_codeql %} は解析前にコードをビルドします。 `autobuild` を、`init` と `analyze` のステップの間に実行します。
+
+| フラグ                         | 必須 | 入力値                                                                                                |
+| --------------------------- |:--:| -------------------------------------------------------------------------------------------------- |
+| `--language`                |    | ビルドする言語。 デフォルトでは、{% data variables.product.prodname_codeql_runner %} はファイル数が最も多いコンパイル型言語をビルドします。 |
+| <nobr>`--temp-dir`</nobr> |    | 一時ファイルが保存されるディレクトリ。 デフォルトは `./codeql-runner` です。                                                   |
+| `--debug`                   |    | なし. より詳細な出力を表示します。                                                                                 |
+| `-h`, `--help`              |    | なし. コマンドのヘルプを表示します。                                                                                |
+
+#### `analyze`
+
+{% data variables.product.prodname_codeql %} データベースにあるコードを解析し、結果を {% data variables.product.product_name %} にアップロードします。
+
+| フラグ                                | 必須 | 入力値                                                                                                                                                                                                                                                                                                                                 |
+| ---------------------------------- |:--:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     | ✓  | 解析するリポジトリの名前。                                                                                                                                                                                                                                                                                                                       |
+| `--commit`                         | ✓  | 解析するコミットの SHA。 Git および Azure DevOps では、`git rev-parse HEAD` の値に相当します。 Jenkins では、`$GIT_COMMIT` に相当します。                                                                                                                                                                                                                              |
+| `--ref`                            | ✓  | 解析するレファレンスの名前 (例: `refs/heads/main`、`refs/pull/42/merge`)。 Git や Jenkins では、`git symbolic-ref HEAD` の値に相当します。 Azure DevOps では、`$(Build.SourceBranch)` に相当します。                                                                                                                                                                       |
+| `--github-url`                     | ✓  | リポジトリがホストされる {% data variables.product.prodname_dotcom %} のインスタンス。                                                                                                                                                                                                                                                                  |
+| `--github-auth`                    | ✓  | {% data variables.product.prodname_github_apps %} トークンまたは個人アクセストークン。                                                                                                                                                                                                                                                              |
+| <nobr>`--checkout-path`</nobr>   |    | リポジトリをチェックアウトするパス。 デフォルトは現在のワーキングディレクトリです。                                                                                                                                                                                                                                                                                          |
+| `--no-upload`                      |    | なし. {% data variables.product.prodname_codeql_runner %} が結果を {% data variables.product.product_name %} にアップロードすることを停止します。                                                                                                                                                                                                         |
+| `--output-dir`                     |    | 出力される SARIF ファイルが保存されるディレクトリ。 デフォルトは一時ファイルのディレクトリです。                                                                                                                                                                                                                                                                                |
+| `--ram`                            |    | クエリの実行時に使用するメモリの量。 デフォルトでは、使用できるすべてのメモリを使用します。                                                                                                                                                                                                                                                                                      |
+| <nobr>`--no-add-snippets`</nobr> |    | なし. SARIF 出力からコードスニペットを除外します。 |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |    | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |    | クエリの実行時に使用するスレッドの数。 デフォルトでは、使用できるすべてのコアを使用します。                                                                                                                                                                                                                                                                                      |
+| `--temp-dir`                       |    | 一時ファイルが保存されるディレクトリ。 デフォルトは `./codeql-runner` です。                                                                                                                                                                                                                                                                                    |
+| `--debug`                          |    | なし. より詳細な出力を表示します。                                                                                                                                                                                                                                                                                                                  |
+| `-h`, `--help`                     |    | なし. コマンドのヘルプを表示します。                                                                                                                                                                                                                                                                                                                 |
+
+#### `アップロード`
+
+SARIF ファイルを {% data variables.product.product_name %} にアップロードします。
+
+{% note %}
+
+**注釈**: CodeQL ランナーでコードを解析する場合、`analyze` コマンドはデフォルトで SARIF の結果をアップロードします。 `upload` コマンドを使用して、他のツールで生成された SARIF の結果をアップロードできます。
+
+{% endnote %}
+
+| フラグ                              | 必須 | 入力値                                                                                                                                                           |
+| -------------------------------- |:--:| ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   | ✓  | アップロードする SARIF ファイル、または複数の SARIF ファイルを含むディレクトリ。                                                                                                               |
+| `--repository`                   | ✓  | 解析したリポジトリの名前。                                                                                                                                                 |
+| `--commit`                       | ✓  | 解析したコミットの SHA。 Git および Azure DevOps では、`git rev-parse HEAD` の値に相当します。 Jenkins では、`$GIT_COMMIT` に相当します。                                                        |
+| `--ref`                          | ✓  | 解析したレファレンスの名前 (例: `refs/heads/main`、`refs/pull/42/merge`)。 Git や Jenkins では、`git symbolic-ref HEAD` の値に相当します。 Azure DevOps では、`$(Build.SourceBranch)` に相当します。 |
+| `--github-url`                   | ✓  | リポジトリがホストされる {% data variables.product.prodname_dotcom %} のインスタンス。                                                                                            |
+| `--github-auth`                  | ✓  | {% data variables.product.prodname_github_apps %} トークンまたは個人アクセストークン。                                                                                        |
+| <nobr>`--checkout-path`</nobr> |    | リポジトリをチェックアウトするパス。 デフォルトは現在のワーキングディレクトリです。                                                                                                                    |
+| `--debug`                        |    | なし. より詳細な出力を表示します。                                                                                                                                            |
+| `-h`, `--help`                   |    | なし. コマンドのヘルプを表示します。                                                                                                                                           |
diff --git a/translations/ja-JP/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ja-JP/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index 403ad0adf3..ad6a2e7686 100644
--- a/translations/ja-JP/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ja-JP/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring the CodeQL workflow for compiled languages
+title: コンパイル型言語で用いる CodeQL のワークフローを設定する
 shortTitle: コンパイルされた言語を設定する
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.product.prodname_codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
+intro: '{% data variables.product.prodname_dotcom %} が {% data variables.product.prodname_codeql_workflow %} を使用してコンパイル型言語で記述されたコードの脆弱性やエラーをスキャンする方法を設定できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
 redirect_from:
@@ -16,23 +16,25 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
+### {% data variables.product.prodname_codeql_workflow %} とコンパイル型言語について
 
-You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+{% data variables.product.prodname_dotcom %} がリポジトリに対して {% data variables.product.prodname_code_scanning %} を実行できるようにするには、{% data variables.product.prodname_actions %} ワークフローをリポジトリに追加します。 **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
 
 {% data reusables.code-scanning.edit-workflow %}
 For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and  "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
 ### {% data variables.product.prodname_codeql %} の autobuild について
 
-Code scanning works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository. For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
+コードスキャンは、1 つ以上のデータベースに対してクエリを実行することにより機能します。 各データベースには、リポジトリにあるすべてのコードを 1 つの言語で表わしたものが含まれています。 コンパイル型言語の C/C++、C#、および Java では、このデータベースを生成するプロセスに、コードのビルドとデータの抽出が含まれています。 {% data reusables.code-scanning.analyze-go %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %}
 
-If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
+ワークフローが `language` マトリクスを使用している場合、`autobuild` はマトリクスに列記された各コンパイル型言語のビルドを試行します。 マトリクスがない場合、`autobuild` はリポジトリ内でソースファイルの数が最も多い、サポートされているコンパイル型言語のビルドを試行します。 Go を除いて、明示的にビルドコマンドを使用しない限り、リポジトリにある他のコンパイル型言語の解析は失敗します。
 
 {% note %}
 
@@ -45,15 +47,15 @@ If your workflow uses a `language` matrix, `autobuild` attempts to build each of
 
 #### C/C++
 
-| サポートされているシステムの種類 | システム名                                                                                                                                          |
-| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| オペレーティングシステム     | Windows, macOS, and Linux                                                                                                                      |
-| ビルドシステム          | Windows: MSbuild and build scripts<br/>Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
+| サポートされているシステムの種類 | システム名                                                                                                                       |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| オペレーティングシステム     | Windows、macOS、Linux                                                                                                         |
+| ビルドシステム          | Windows: MSbuild およびビルドスクリプト<br/>Linux および macOS: Autoconf、Make、CMake、qmake、 Meson、Waf、SCons、Linux Kbuild、およびビルドスクリプト |
 
 `autobuild` ステップの動作は、抽出を実行するオペレーティングシステムによって異なります。 On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
 
-1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root. `autobuild` が最上位ディレクトリから同じ（最短）深度で複数のソリューションまたはプロジェクトファイルを検出した場合、それらすべてをビルドしようとします。
-2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
+1. ルートに最も近いソリューション (`.sln`) またはプロジェクト (`.vcxproj`) ファイルで `MSBuild.exe` を呼び出します。 `autobuild` が最上位ディレクトリから同じ（最短）深度で複数のソリューションまたはプロジェクトファイルを検出した場合、それらすべてをビルドしようとします。
+2. ビルドスクリプトのように見えるスクリプト、つまり _build.bat_、_build.cmd_、_および build.exe_ を、この順番で呼び出します。
 
 On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
 
@@ -76,10 +78,10 @@ On Linux and macOS, the `autobuild` step reviews the files present in the reposi
 
 #### Java
 
-| サポートされているシステムの種類 | システム名                                      |
-| ---------------- | ------------------------------------------ |
-| オペレーティングシステム     | Windows, macOS, and Linux (no restriction) |
-| ビルドシステム          | Gradle、Maven、Ant                           |
+| サポートされているシステムの種類 | システム名                      |
+| ---------------- | -------------------------- |
+| オペレーティングシステム     | Windows、macOS、Linux (制限なし) |
+| ビルドシステム          | Gradle、Maven、Ant           |
 
 `autobuild` プロセスは、この戦略を適用して Java コードベースのビルドシステムを決定しようとします。
 
@@ -89,7 +91,7 @@ On Linux and macOS, the `autobuild` step reviews the files present in the reposi
 
 ### コンパイル言語のビルドステップを追加する
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
+{% data reusables.code-scanning.autobuild-add-build-steps %}ワークフローファイルの編集方法については、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。
 
 `autobuild` ステップを削除した後、`run` ステップのコメントを外して、リポジトリに適したビルドコマンドを追加します。 ワークフロー `run` ステップは、オペレーティングシステムのシェルを使用してコマンドラインプログラムを実行します。 これらのコマンドを変更し、さらにコマンドを追加して、ビルドプロセスをカスタマイズできます。
 
@@ -117,6 +119,6 @@ If your repository contains multiple compiled languages, you can specify languag
 
 For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
 
-For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
+`autobuild` がコードをビルドしない理由に関するヒントやビルドの方法については、「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/code-security/secure-coding/troubleshooting-the-codeql-workflow)」を参照してください。
 
 If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
diff --git a/translations/ja-JP/content/code-security/secure-coding/index.md b/translations/ja-JP/content/code-security/secure-coding/index.md
index b777242ab5..90c923211e 100644
--- a/translations/ja-JP/content/code-security/secure-coding/index.md
+++ b/translations/ja-JP/content/code-security/secure-coding/index.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### 目次
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% link_in_list /running-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-the-codeql-action-for-compiled-languages %}
-    {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/ja-JP/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/ja-JP/content/code-security/secure-coding/integrating-with-code-scanning.md
index 88ab7921b4..88071569d9 100644
--- a/translations/ja-JP/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/ja-JP/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -1,7 +1,7 @@
 ---
-title: Integrating with code scanning
-shortTitle: Integration
-intro: 'You can integrate third-party code analysis tools with {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %} by uploading data as SARIF files.'
+title: コードスキャンと統合する
+shortTitle: インテグレーション
+intro: 'データを SARIF ファイルとしてアップロードすることで、サードパーティーのコード解析ツールを{% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %} と統合できます。'
 mapTopic: true
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index 9e30cf8bf6..a7992e7e33 100644
--- a/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
-title: Managing code scanning alerts for your repository
+title: リポジトリのコードスキャンアラートを管理する
 shortTitle: アラートを管理する
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,68 +16,62 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### {% data variables.product.prodname_code_scanning %} からのアラートについて
 
-You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+デフォルトの {% data variables.product.prodname_codeql %} 解析、サードパーティーの解析、または複数のタイプの解析を使用して、リポジトリのコードをチェックするため、{% data variables.product.prodname_code_scanning %} をセットアップできます。 解析が完了すると、解析によるアラートがリポジトリのセキュリティビューに隣り合わせで表示されます。 サードパーティツールまたはカスタムクエリの結果には、{% data variables.product.company_short %} のデフォルト {% data variables.product.prodname_codeql %} 解析により検出されたアラートで表示されるプロパティの一部が含まれていない場合があります。 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
 
-By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+デフォルトでは、{% data variables.product.prodname_code_scanning %} はプルリクエスト中にデフォルトブランチのコードを定期的に解析します。 プルリクエストでアラートを管理する方法については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### About alerts details
+### アラートの詳細について
 
-Each alert highlights a problem with the code and the name of the tool that identified it. アラートをトリガーしたコード行と、アラートのプロパティ（問題の重要度や性質など）を確認できます。 アラートは、問題が最初に発生したときにも通知します。 For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
+各アラートはコードの問題と、それを特定したツールの名前を表示します。 アラートをトリガーしたコード行と、アラートのプロパティ（問題の重要度や性質など）を確認できます。 アラートは、問題が最初に発生したときにも通知します。 {% data variables.product.prodname_codeql %} 解析で特定されたアラートについては、問題を解説する方法についての情報も表示されます。
 
 ![{% data variables.product.prodname_code_scanning %} からのアラートの例](/assets/images/help/repository/code-scanning-alert.png)
 
-If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
+{% data variables.product.prodname_codeql %} を使用して {% data variables.product.prodname_code_scanning %} をセットアップした場合、コード内のデータフロー問題も検出できます。 データフロー解析は、データを安全でない方法で利用する、関数に危険な引数を渡す、機密情報を漏洩するなど、コードにおける潜在的なセキュリティ問題を検出します。
 
-{% data variables.product.prodname_code_scanning %} がデータフローアラートを報告すると、{% data variables.product.prodname_dotcom %} はデータがコードを通してどのように移動するかを示します。 {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
+{% data variables.product.prodname_code_scanning %} がデータフローアラートを報告すると、{% data variables.product.prodname_dotcom %} はデータがコードを通してどのように移動するかを示します。 {% data variables.product.prodname_code_scanning_capc %} を使用すると、機密情報を漏洩し、悪意のあるユーザによる攻撃の入り口になる可能性があるコードの領域を特定できます。
 
-### Viewing the alerts for a repository
+### リポジトリのアラートを表示する
 
-Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+リポジトリへの書き込み権限があるユーザなら誰でも、プルリクエストの {% data variables.product.prodname_code_scanning %} アノテーションを表示できます。 詳しい情報については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
 
-You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch.
+[**Security**] タブでリポジトリのすべてのアラートの概要を表示するには、書き込み権限が必要です。 デフォルトでは、アラートはデフォルトブランチに対して表示されます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
 1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %}
-1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore.
+1. [{% data variables.product.prodname_code_scanning_capc %}] で、調査するアラートをクリックします。
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
-  ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png)
+  ![アラートの概要](/assets/images/help/repository/code-scanning-click-alert.png)
 {% else %}
   ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
 {% endif %}
-1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png)
-1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
+1. アラートでデータフローの問題が強調表示された場合は、必要に応じて [**Show paths**] をクリックし、データソースから、それが使用されているシンクまでのパスを表示します。 ![アラートの [Show paths] リンク](/assets/images/help/repository/code-scanning-show-paths.png)
+1. {% data variables.product.prodname_codeql %} 解析によるアラートには、問題の説明も含まれています。 コードを修正する方法についてのガイダンスを表示するには、[**Show more**] をクリックします。 ![アラートの詳細情報](/assets/images/help/repository/code-scanning-alert-details.png)
 
-### Fixing an alert
+### アラートを解決する
 
-Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+リポジトリへの書き込み権限があるユーザなら誰でも、コードに修正をコミットしてアラートを解決できます。 リポジトリでプルリクエストに対して {% data variables.product.prodname_code_scanning %} が実行されるよう予定されている場合は、修正してプルリクエストを発行するようお勧めします。 これにより、変更の {% data variables.product.prodname_code_scanning %} 解析がトリガーされ、修正で新しい問題が入り込まないようテストされます。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning) を設定する」および「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+リポジトリへの書き込み権限がある場合は、アラートの概要を表示して、[**Closed**] をクリックすることで、解決したアラートを表示できます。 詳しい情報については、「[リポジトリのアラートを表示する](#viewing-the-alerts-for-a-repository)」を参照してください。 The "Closed" list shows fixed alerts and alerts that users have dismissed.
 
-Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
+あるブランチでは解決されたアラートが、別のブランチでは解決されていないことがあります。 アラートの概要で [Branch] ドロップダウンメニューを使用し、特定のブランチでアラートが解決されたかどうか確認できます。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
-![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png)
+![ブランチによるアラートのフィルタリング](/assets/images/help/repository/code-scanning-branch-filter.png)
 {% else %}
-![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
+![ブランチによるアラートのフィルタリング](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### アラートを閉じる
-
-Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### Dismissing or deleting alerts
 
 There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
@@ -101,20 +95,9 @@ When you delete an alert:
 
 To dismiss or delete alerts:
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. Select the **Close** drop-down menu and click a reason for closing the alert.    
-   ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
 
    ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,10 +128,8 @@ To dismiss or delete alerts:
 
 If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
 
-{% endif %}
-
 ### 参考リンク
 
-- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
-- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"
-- "[About integration with {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)"
+- 「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」
+- 「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」
+- 「[{% data variables.product.prodname_code_scanning %} からのアラートを管理する](/code-security/secure-coding/about-integration-with-code-scanning)」
diff --git a/translations/ja-JP/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/ja-JP/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..73e6beb4cd
--- /dev/null
+++ b/translations/ja-JP/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Running CodeQL CLI in your CI system
+shortTitle: Running CodeQL CLI
+intro: '{% data variables.product.prodname_codeql_cli %} を使用して、、サードパーティの継続的インテグレーションシステムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行できます。'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### {% data variables.product.prodname_codeql_cli %} について
+
+{% data variables.product.prodname_codeql_cli %} を使用して、サードパーティ継続的インテグレーション (CI) システムで処理しているコード上で {% data variables.product.prodname_code_scanning %} を実行できます。 {% data reusables.code-scanning.about-code-scanning %}詳細については、「[{% data variables.product.prodname_code_scanning %} について](/code-security/secure-coding/about-code-scanning)」を参照してください。
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_codeql_runner %} in your CI system, or {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% note %}
+
+**Note:** {% if currentVersion == "free-pro-team@latest" %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% endnote %}
+
+### {% data variables.product.prodname_codeql_cli %} をダウンロードする
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. 例:
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. 詳細は「[{% data variables.product.prodname_github_apps %} をビルドする](/developers/apps/building-github-apps)」および「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      必須
+    </th>
+    
+    <th>
+      使い方
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      任意. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### 基本的な例
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      必須
+    </th>
+    
+    <th>
+      使い方
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. 詳しい情報については「<a href="/code-security/secure-coding/sarif-support-for-code-scanning">{% data variables.product.prodname_code_scanning %}の SARIF サポート</a>」を参照してください。
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      任意. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      任意. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### 基本的な例
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      必須
+    </th>
+    
+    <th>
+      使い方
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. 詳しい情報については「<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">リポジトリのセキュリティ及び分析の設定の管理</a>」を参照してください。
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      任意. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### 基本的な例
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### 参考リンク
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/ja-JP/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index 1ef284f3f2..db030525df 100644
--- a/translations/ja-JP/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ja-JP/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -1,7 +1,7 @@
 ---
-title: Running CodeQL code scanning in a container
-shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container'
-intro: 'You can run {% data variables.product.prodname_code_scanning %} in a container by ensuring that all processes run in the same container.'
+title: コンテナで CodeQL コードスキャンを実行する
+shortTitle: 'コンテナで {% data variables.product.prodname_code_scanning_capc %}'
+intro: 'すべてのプロセスが同じコンテナで動作するようにすることで、{% data variables.product.prodname_code_scanning %} を実行できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container
@@ -13,17 +13,23 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
-### About {% data variables.product.prodname_code_scanning %} with a containerized build
+### コンテナ化されたビルドで {% data variables.product.prodname_code_scanning %} を使用することについて
 
-If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.
+コンパイル言語用に {% data variables.product.prodname_code_scanning %} をセットアップし、コンテナ化された環境でコードをビルドしようとすると、解析が失敗し、"No source code was seen during the build." というエラーメッセージが出る場合があります。 これは、コードがコンパイルされているので {% data variables.product.prodname_codeql %} がコードをモニターできなかったことを示しています。
 
-You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. {% data variables.product.prodname_actions %} を使用している場合は、同じコンテナですべてのアクションを実行するようワークフローを設定します。 詳しい情報については「[ワークフローの例](#example-workflow)」を参照してください。
+{% else %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. {% data variables.product.prodname_actions %} を使用している場合は、同じコンテナですべてのアクションを実行するようワークフローを設定します。 詳しい情報については「[ワークフローの例](#example-workflow)」を参照してください。
+{% endif %}
 
 ### 依存関係
 
-You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations:
+使用しているコンテナで特定の依存関係がない場合 (たとえば、Git は PATH 変数にインストールされ、追加されている必要がある)、{% data variables.product.prodname_code_scanning %} を実行する上で困難が生じる場合があります。 依存関係の問題が生じた場合は、{% data variables.product.prodname_dotcom %} の仮想環境に通常含まれているソフトウェアのリストを確認してください。 詳しい情報については、次の場所にある特定のバージョンの `readme` ファイルを参照してください。
 
 * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux
 * macOS: https://github.com/actions/virtual-environments/tree/main/images/macos
@@ -31,7 +37,7 @@ You may have difficulty running {% data variables.product.prodname_code_scanning
 
 ### ワークフローの例
 
-This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。
+このサンプルワークフローでは、{% data variables.product.prodname_actions %} を使用して、コンテナ化された環境において {% data variables.product.prodname_codeql %} 解析を実行します。 `container.image` の値で、使用するコンテナを指定します。 この例では、イメージ名は `codeql-container` で、`f0f91db` のタグが付いています。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。
 
 ``` yaml
 name: "{% data variables.product.prodname_codeql %}"
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/ja-JP/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..45c679dc91
--- /dev/null
+++ b/translations/ja-JP/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Running CodeQL runner in your CI system
+shortTitle: Running CodeQL runner
+intro: '{% data variables.product.prodname_codeql_runner %} を使用して、、サードパーティの継続的インテグレーションシステムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行できます。'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### {% data variables.product.prodname_codeql_runner %} について
+
+The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %}詳細については、「[{% data variables.product.prodname_code_scanning %} について](/code-security/secure-coding/about-code-scanning)」を参照してください。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. The runner is more complex and less forgiving to set up than the CLI, and is recommended only if you need its capability to analyze multiple compiled languages with a single build, or to integrate with complex build processes. For more information, see "[About CodeQL code scanning in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. 詳細については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
+
+{% data variables.product.prodname_codeql_runner %} は、{% data variables.product.prodname_dotcom %} リポジトリのチェックアウト中に {% data variables.product.prodname_codeql %} 解析を実行するコマンドラインツールです。 サードパーティーのシステムにランナーを追加し、ランナーを呼び出してコードを解析し、その結果を {% data variables.product.product_name %} にアップロードします。 この結果は、リポジトリの {% data variables.product.prodname_code_scanning %} アラートとして表示されます。
+
+{% note %}
+
+**注釈:**
+{% if currentVersion == "free-pro-team@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. {% data variables.product.prodname_dotcom_the_website %}上で管理されるパブリックリポジトリでの使用は無料であり、{% data variables.product.prodname_advanced_security %}ライセンスを持つお客様が所有するプライベートリポジトリ上で使用できます。 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+{% else %}
+* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. 詳細は「[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+{% endif %}
+{% endnote %}
+
+### {% data variables.product.prodname_codeql_runner %} をダウンロードする
+
+You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. 一部のオペレーティングシステムでは、ダウンロードしたファイルの実行前に、その権限を変更する必要があります。
+
+Linuxの場合:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+macOS:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
+
+### {% data variables.product.prodname_codeql_runner %} を CI システムに追加する
+
+Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+これに加えて、各 CI サーバーは以下の条件も満たす必要があります。
+
+- {% data variables.product.prodname_codeql_runner %} が使用するための {% data variables.product.prodname_github_app %} または個人アクセストークン。 `repo` スコープのあるアクセストークン、または `security_events` の書き込み権限、ならびに `metadata` および `contents` の読み取り権限を持つ {% data variables.product.prodname_github_app %} を使用する必要があります。 詳細は「[{% data variables.product.prodname_github_apps %} をビルドする](/developers/apps/building-github-apps)」および「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
+- {% data variables.product.prodname_codeql_runner %} のリリースに伴う {% data variables.product.prodname_codeql %} バンドルへのアクセス。 このパッケージには、{% data variables.product.prodname_codeql %} 解析に必要なクエリとライブラリ、さらにランナーによって内部的に使用される {% data variables.product.prodname_codeql %} CLI が含まれています。 詳細は「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+
+{% data variables.product.prodname_codeql %} バンドルにアクセスを与えるオプションは次の通りです。
+
+1. Allow the CI servers access to https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. バンドルを手動でダウンロード/展開し、他の中央リソースに保存して、 <nobr>`--codeql-path`</nobr> フラグで、呼び出しにおいて {% data variables.product.prodname_codeql_runner %} を初期化するバンドルの場所を指定します。
+
+### {% data variables.product.prodname_codeql_runner %} を呼び出す
+
+解析するリポジトリのチェックアウトの場所から、{% data variables.product.prodname_codeql_runner %} を呼び出す必要があります。 主なコマンドは次の 2 つです。
+
+1. `init` は、ランナーを初期化し、解析する各言語に {% data variables.product.prodname_codeql %} データベースを作成するために必要です。 このデータベースは、続くコマンドにより展開、解析されます。
+1. `analyze` は、{% data variables.product.prodname_codeql %} データベースを展開、解析し、結果を {% data variables.product.product_name %} にアップロードするために必要です。
+
+For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
+
+将来の解析のため {% data variables.product.prodname_codeql_runner %} が CodeQL バンドルを保存する場所を  <nobr>`--tools-dir`</nobr>  フラグで設定できます。また、解析中に一時ファイルを保存する場所を、`--temp-dir` で設定できます。 <nobr>`--temp-dir`</nobr>.
+
+ランナーのコマンドラインリファレンスを表示するには、`-h` フラグを使用します。 たとえば、動作するすべてのコマンドを一覧表示するには `codeql-runner-OS -h` と入力し、`init` コマンド実行時に使用できるすべてのコマンドを一覧表示するには `codeql-runner-OS init -h` と入力します (`OS` 変数は使用している実行ファイルによります)。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を CI システムで設定する](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)」を参照してください。
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### 基本的な例
+
+この例では、`{% data variables.command_line.git_url_example %}` にホストされている `octo-org/example-repo` リポジトリに対し、Linux CI サーバーで {% data variables.product.prodname_codeql %} 解析を実行します。 このリポジトリには、{% data variables.product.prodname_codeql %} により直接解析でき、ビルドされていない言語 (Go、JavaScript、Python、TypeScript) のみが含まれているため、プロセスは非常に単純です。
+
+In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
+
+1. 解析するリポジトリをチェックアウトします。
+1. リポジトリがチェックアウトされるディレクトリに移動します。
+1. {% data variables.product.prodname_codeql_runner %} を初期化し、検出された言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### コンパイル型言語の例
+
+この例は前の例と似ていますが、今回のリポジトリには C/C++、C#、または Java のコードがあります。 これらの言語用に {% data variables.product.prodname_codeql %} データベースを作成するには、CLI でビルドをモニターする必要があります。 初期化プロセスの最後に、ランナーはコードをビルドする前に環境をセットアップするために必要なコマンドを報告します。 通常の CI ビルドプロセスを呼び出す前にこのコマンドを実行してから、`analyze` コマンドを実行する必要があります。
+
+1. 解析するリポジトリをチェックアウトします。
+1. リポジトリがチェックアウトされるディレクトリに移動します。
+1. {% data variables.product.prodname_codeql_runner %} を初期化し、検出された言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. `init` アクションによって生成されたスクリプトを入手し、ビルドを監視する環境をセットアップします。 次のコードには、先頭にドットとスペースがあることに注意してください。
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. コードをビルドします。 macOS では、build コマンドのプレフィックスに環境変数 `$CODEQL_RUNNER` を付ける必要があります。 For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**注釈:** コンテナ化されたビルドを使用している場合、ビルドタスクを行うコンテナで {% data variables.product.prodname_codeql_runner %} を実行する必要があります。
+
+{% endnote %}
+
+### 参考リンク
+
+- 「[CI システムで {% data variables.product.prodname_codeql_runner %} を設定する](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)」
+- 「[CI システムにおける {% data variables.product.prodname_codeql_runner %} のトラブルシューティング](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)」
diff --git a/translations/ja-JP/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/ja-JP/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index d8b084a35c..21727e2739 100644
--- a/translations/ja-JP/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/ja-JP/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: コードスキャンの SARIF サポート
 shortTitle: SARIF サポート
 intro: '{% data variables.product.prodname_dotcom %} のリポジトリにあるサードパーティの静的分析ツールからの結果を表示するには、{% data variables.product.prodname_code_scanning %} 用に SARIF 2.1.0 JSON スキーマの特定のサブセットをサポートする SARIF ファイルに結果を保存する必要があります。 デフォルトの {% data variables.product.prodname_codeql %} 静的分析エンジンを使用すると、結果は {% data variables.product.prodname_dotcom %} のリポジトリに自動的に表示されます。'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### SARIF サポートについて
@@ -22,27 +25,35 @@ SARIF（Static Analysis Results Interchange Format）は、出力ファイル形
 
 サードパーティの静的コード分析エンジンから SARIF ファイルをアップロードするには、アップロードされたファイルが SARIF 2.1.0 バージョンを使用していることを確認する必要があります。 {% data variables.product.prodname_dotcom %} は SARIF ファイルを解析し、{% data variables.product.prodname_code_scanning %} エクスペリエンスの一部としてリポジトリの結果を使用してアラートを表示します。 詳しい情報については、「[SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードする](/code-security/secure-coding/uploading-a-sarif-file-to-github)」を参照してください。 SARIF 2.1.0 JSON スキーマの詳細については、「[`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json)」を参照してください。
 
-SARIF ファイルに `partialFingerprints` が含まれていない場合、{% data variables.product.prodname_actions %} を使用して SARIF ファイルをアップロードすると、`partialFingerprints` フィールドが計算されます。 For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+SARIF ファイルに `partialFingerprints` が含まれていない場合、{% data variables.product.prodname_actions %} を使用して SARIF ファイルをアップロードすると、`partialFingerprints` フィールドが計算されます。 For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
 
-{% data variables.product.prodname_dotcom %} は、SARIF ファイルのプロパティを使用してアラートを表示します。 たとえば、`shortDescription` と `fullDescription` は、{% data variables.product.prodname_code_scanning %} アラートの上部に表示されます。 `location` により、{% data variables.product.prodname_dotcom %} がコードファイルに注釈を表示できるようになります。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
+
+{% data variables.product.prodname_dotcom %} は、SARIF ファイルのプロパティを使用してアラートを表示します。 たとえば、`shortDescription` と `fullDescription` は、{% data variables.product.prodname_code_scanning %} アラートの上部に表示されます。 `location` により、{% data variables.product.prodname_dotcom %} がコードファイルに注釈を表示できるようになります。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
 SARIF の使用が初めてで、詳細を確認する必要がある場合は、Microsoft の [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) リポジトリを参照してください。
 
 ### フィンガープリントを使用してアラートの重複を防止する
 
-{% data variables.product.prodname_actions %} ワークフローが新しいコードスキャンを実行するたびに、それぞれの実行結果が処理され、アラートがリポジトリに追加されます。 同じ問題に対するアラートの重複を防ぐために、{% data variables.product.prodname_code_scanning %} はフィンガープリントを使用してさまざまな実行結果を照合し、選択したブランチの最新の実行で 1 回だけ表示されるようにします。 This makes it possible to match alerts to the right line of code when files are edited.
+{% data variables.product.prodname_actions %} ワークフローが新しいコードスキャンを実行するたびに、それぞれの実行結果が処理され、アラートがリポジトリに追加されます。 同じ問題に対するアラートの重複を防ぐために、{% data variables.product.prodname_code_scanning %} はフィンガープリントを使用してさまざまな実行結果を照合し、選択したブランチの最新の実行で 1 回だけ表示されるようにします。 これにより、ファイルが編集されたときに、アラートを適切なコードの行にマッチさせることができます。
 
 {% data variables.product.prodname_dotcom %} は、OASIS 標準の `partialFingerprints` プロパティを使用して、2 つの結果が論理的に同一の場合に検出します。 詳しい情報については、OASIS ドキュメントの「"[partialFingerprints プロパティ](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)」エントリを参照してください。
 
-`id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。 If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)."
+`id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。 `upload-sarif` アクションを使用して SARIF ファイルをアップロードし、このデータが欠落している場合、{% data variables.product.prodname_dotcom %} はソースファイルから `partialFingerprints` フィールドの入力を試みます。 結果のアップロードに関する詳しい情報については、「[SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードする](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)」を参照してください。
 
-If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)."
+`/code-scanning/sarifs` API エンドポイントを使用してフィンガープリントデータなしで SARIF ファイルをアップロードする場合、{% data variables.product.prodname_code_scanning %} アラートが処理され表示されますが、アラートが重複して表示される場合があります。 アラートが重複して表示されないようにするには、フィンガープリントデータを計算し、`partialFingerprints` プロパティを入れてから SARIF ファイルをアップロードする必要があります。 `upload-sarif` アクションが使用しているスクリプト (https://github.com/github/codeql-action/blob/main/src/fingerprints.ts) は、取っ掛かりとして役立つかもしれません。 API に関する詳しい情報については、「[解析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」を参照してください。
 
-### Validating your SARIF file
+### SARIF ファイルを検証する
 
 <!--UI-LINK: When code scanning fails, the error banner shown in the Security > Code scanning alerts view links to this anchor.-->
 
-You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/).
+SARIF ファイルが {% data variables.product.prodname_code_scanning %} と互換性があるかどうかは、{% data variables.product.prodname_dotcom %} 収集ルールと照らし合わせることで確認できます。 詳しい情報については、[Microsoft SARIF validator](https://sarifweb.azurewebsites.net/) にアクセスしてください。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
@@ -74,17 +85,17 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 
 #### `reportingDescriptor` オブジェクト
 
-| 名前                           | 説明                                                                                                                                                                                                                                                                                                                  |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id`                         | **必須。**ルールの一意の識別子。 `id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。                                                                                                                                          |
-| `name`                       | **任意。**ルールの名前。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタできるように名前を表示します。                                                                                                                                                              |
-| `shortDescription.text`      | **必須。**ルールの簡単な説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の簡単な説明を表示します。                                                                                                                                                             |
-| `fullDescription.text`       | **必須。**ルールの説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の説明全体を表示します。 文字数は最大 1000 文字に制限されています。                                                                                                                                        |
-| `defaultConfiguration.level` | **任意。**ルールのデフォルトの重要度レベル。 {% data variables.product.prodname_code_scanning_capc %} は、特定のルールの結果がどの程度重要であるかを理解するために、重要度レベルを使用します。 この値は、`result` オブジェクトの `level` 属性でオーバーライドできます。 詳しい情報については、「[`result` オブジェクト](#result-object)」を参照してください。 デフォルト: `Warning`                                                            |
-| `help.text`                  | **必須。**テキスト形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。                                                                                                                                                                                              |
-| `help.markdown`              | **推奨。**Markdown 形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。 When `help.markdown` is available, it is displayed instead of `help.text`.                                                                                                              |
-| `properties.tags[]`          | **任意。**文字列の配列。 {% data variables.product.prodname_code_scanning_capc %} は、`tags` を使用して、{% data variables.product.prodname_dotcom %} の結果をフィルタできます。 たとえば、`security` タグを含むすべての結果をフィルタすることができます。                                                                                                                      |
-| `properties.precision`       | **推奨。**このルールで示される結果が true である頻度を示す文字列。 たとえば、ルールに既知の高誤検知率がある場合、精度は `low` である必要があります。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} の精度で結果を並べ替えるため、最高 `level` の精度と最高 `precision` の結果が最初に表示されます。 Can be one of: `very-high`, `high`, `medium`, or `low`. |
+| 名前                           | 説明                                                                                                                                                                                                                                                                                                        |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                         | **必須。**ルールの一意の識別子。 `id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。                                                                                                                                |
+| `name`                       | **任意。**ルールの名前。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタできるように名前を表示します。                                                                                                                                                    |
+| `shortDescription.text`      | **必須。**ルールの簡単な説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の簡単な説明を表示します。                                                                                                                                                   |
+| `fullDescription.text`       | **必須。**ルールの説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の説明全体を表示します。 文字数は最大 1000 文字に制限されています。                                                                                                                              |
+| `defaultConfiguration.level` | **任意。**ルールのデフォルトの重要度レベル。 {% data variables.product.prodname_code_scanning_capc %} は、特定のルールの結果がどの程度重要であるかを理解するために、重要度レベルを使用します。 この値は、`result` オブジェクトの `level` 属性でオーバーライドできます。 詳しい情報については、「[`result` オブジェクト](#result-object)」を参照してください。 デフォルト: `Warning`                                                  |
+| `help.text`                  | **必須。**テキスト形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。                                                                                                                                                                                    |
+| `help.markdown`              | **推奨。**Markdown 形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。 `help.markdown` が利用可能な場合は、 `help.text` の代わりに表示されます。                                                                                                                           |
+| `properties.tags[]`          | **任意。**文字列の配列。 {% data variables.product.prodname_code_scanning_capc %} は、`tags` を使用して、{% data variables.product.prodname_dotcom %} の結果をフィルタできます。 たとえば、`security` タグを含むすべての結果をフィルタすることができます。                                                                                                            |
+| `properties.precision`       | **推奨。**このルールで示される結果が true である頻度を示す文字列。 たとえば、ルールに既知の高誤検知率がある場合、精度は `low` である必要があります。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} の精度で結果を並べ替えるため、最高 `level` の精度と最高 `precision` の結果が最初に表示されます。 `very-high`、`high`、`medium`、`low` のいずれかになります。 |
 
 #### `result` オブジェクト
 
@@ -97,7 +108,7 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 | `rule`                                  | **任意。**この結果のルール（レポート記述子）を見つけるために使用される参照。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | `level`                                 | **任意。**結果の重要度。 このレベルは、ルールで定義されているデフォルトの重要度をオーバーライドします。 {% data variables.product.prodname_code_scanning_capc %} は、レベルを使用して、{% data variables.product.prodname_dotcom %} の重要度で結果をフィルタします。                                                                                                                                                                                                                                                                                                                                                                                                       |
 | `message.text`                          | **必須。**結果を説明するメッセージ。 {% data variables.product.prodname_code_scanning_capc %} は、結果のタイトルとしてメッセージテキストを表示します。 表示スペースが限られている場合、メッセージの最初の文のみが表示されます。                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| `locations[]`                           | **Required.** The set of locations where the result was detected up to a maximum of 10. 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。                                                                                                                                                                                                                       |
+| `locations[]`                           | **必須。**結果が検出された場所。最大値は 10 です。 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。                                                                                                                                                                                                                                                                                 |
 | `partialFingerprints`                   | **必須。**結果の一意の ID を追跡するために使用される文字列。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` を使用して、コミットとブランチで同じ結果であるものを正確に識別します。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` がある場合、それを使用しようとします。 `upload-action` を使用してサードパーティの SARIF ファイルをアップロードする場合、SARIF ファイルに含まれていないときに、アクションによって `partialFingerprints` が作成されます。 詳しい情報については、「[フィンガープリントを使用してアラートの重複を防止する](#preventing-duplicate-alerts-using-fingerprints)」を参照してください。  **注釈:** {% data variables.product.prodname_code_scanning_capc %} は、`primaryLocationLineHash` のみを使用します。 |
 | `codeFlows[].threadFlows[].locations[]` | **任意。**`threadFlow` オブジェクトに対する `location` オブジェクトの配列。実行スレッドを通してプログラムの進行状況を記述します。 `codeFlow` オブジェクトは、結果の検出に使用されるコード実行パターンを記述します。 コードフローが入力されている場合、{% data variables.product.prodname_code_scanning %} は、関連する結果の {% data variables.product.prodname_dotcom %} のコードフローを拡張します。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。                                                                                                                                                                                                                                                           |
 | `relatedLocations[]`                    | この結果に関連する場所。 結果メッセージに埋め込まれている場合、{% data variables.product.prodname_code_scanning_capc %} は、関連する場所にリンクします。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -114,13 +125,52 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 
 #### `physicalLocation` オブジェクト
 
-| 名前                     | 説明                                                                                                                                                                                                                                                                                                                                                                                                       |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `artifactLocation.uri` | **必須。**アーティファクトの場所を示す URI（通常はリポジトリ内のファイル、またはビルド中に生成されたファイル）。 URI が相対の場合、分析されている {% data variables.product.prodname_dotcom %} リポジトリのルートに相対である必要があります。 たとえば、main.js または src/script.js は、リポジトリのルートを基準にしています。 URI が絶対の場合、{% data variables.product.prodname_code_scanning %} は URI を使用してアーティファクトをチェックアウトし、リポジトリ内のファイルを照合できます。 For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. |
-| `region.startLine`     | **必須。**リージョンの最初の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                                  |
-| `region.startColumn`   | **必須。**リージョンの最初の文字の列番号。                                                                                                                                                                                                                                                                                                                                                                                  |
-| `region.endLine`       | **必須。**リージョンの最後の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                                  |
-| `region.endColumn`     | **必須。**リージョンの末尾に続く文字の列番号。                                                                                                                                                                                                                                                                                                                                                                                |
+| 名前                     | 説明                                                                                                                                                                                                                                                                                                                                                                                            |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `artifactLocation.uri` | **必須。**アーティファクトの場所を示す URI（通常はリポジトリ内のファイル、またはビルド中に生成されたファイル）。 URI が相対の場合、分析されている {% data variables.product.prodname_dotcom %} リポジトリのルートに相対である必要があります。 たとえば、main.js または src/script.js は、リポジトリのルートを基準にしています。 URI が絶対の場合、{% data variables.product.prodname_code_scanning %} は URI を使用してアーティファクトをチェックアウトし、リポジトリ内のファイルを照合できます。 例: `https://github.com/ghost/example/blob/00/src/promiseUtils.js` |
+| `region.startLine`     | **必須。**リージョンの最初の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                       |
+| `region.startColumn`   | **必須。**リージョンの最初の文字の列番号。                                                                                                                                                                                                                                                                                                                                                                       |
+| `region.endLine`       | **必須。**リージョンの最後の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                       |
+| `region.endColumn`     | **必須。**リージョンの末尾に続く文字の列番号。                                                                                                                                                                                                                                                                                                                                                                     |
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| 名前   | 説明                                                                                                                                                                                                                                    |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id` | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | カテゴリ              | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
 
 ### SARIF 出力ファイルの例
 
@@ -130,7 +180,6 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 
 次の SARIF 出力ファイルには、{% data variables.product.prodname_code_scanning %} の結果が期待どおりに機能するために最低限必要なプロパティを示す値の例が示されています。 プロパティを削除したり、値を含めていない場合、このデータは正しく表示されないか、{% data variables.product.prodname_dotcom %} で同期されません。
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 
 次の SARIF 出力ファイルには、{% data variables.product.prodname_code_scanning %} でサポートされているすべての SARIF プロパティを示す値の例が示されています。
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
   ]
 }
 ```
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
index 12c82b2d41..286df09536 100644
--- a/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up code scanning for a repository
-shortTitle: Setting up code scanning
-intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.'
+title: リポジトリに対するコードスキャンをセットアップする
+shortTitle: コードスキャンを設定する
+intro: 'リポジトリにワークフローを追加することにより、{% data variables.product.prodname_code_scanning %} をセットアップできます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.'
 redirect_from:
@@ -17,113 +17,116 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### Options for setting up {% data variables.product.prodname_code_scanning %}
+### {% data variables.product.prodname_code_scanning %} のセットアップ用オプション
 
-You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. 詳しい情報については「[{% data variables.product.prodname_codeql %}について](/code-security/secure-coding/about-code-scanning#about-codeql)」を参照してください。
+{% data variables.product.prodname_code_scanning %} アラートの生成方法、および使用するツールを、リポジトリレベルで決定できます。 {% data variables.product.product_name %} は、{% data variables.product.prodname_codeql %} 解析のために完全に統合されたサポートを提供すると共に、サードパーティーのツールを使用した解析もサポートします。 詳しい情報については「[{% data variables.product.prodname_codeql %}について](/code-security/secure-coding/about-code-scanning#about-codeql)」を参照してください。
 
 {% data reusables.code-scanning.enabling-options %}
 
-### Setting up {% data variables.product.prodname_code_scanning %} using actions
+### アクションを使用して {% data variables.product.prodname_code_scanning %} をセットアップする
 
-{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)」を参照してください。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}アクションを使用して {% data variables.product.prodname_code_scanning %} を実行すると、分数を消費します。 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)」を参照してください。{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
-5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
+3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} ![セキュリティの概要にある、[{% data variables.product.prodname_code_scanning_capc %}] の右側の [{% data variables.product.prodname_code_scanning %}] ボタン](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. [Get started with {% data variables.product.prodname_code_scanning %}] で、{% data variables.product.prodname_codeql_workflow %} またはサードパーティーのワークフローの [**Set up this workflow**] をクリックします。 !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
+5. {% data variables.product.prodname_code_scanning %} がコードをスキャンする方法をカスタマイズするため、ワークフローを編集します。
 
-   Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
+   通常は、何も変更せずに {% data variables.product.prodname_codeql_workflow %} をコミットできます。 ただし、サードパーティのワークフローは、その多くで追加設定が必要なため、コミットする前にワークフローのコメントをお読みください。
 
    詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning)」を参照してください。
 6. [**Start commit**] ドロップダウンを使用して、コミットメッセージを入力します。 ![コミットを開始する](/assets/images/help/repository/start-commit-commit-new-file.png)
 7. デフォルトブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択します。 ![コミット先を選択する](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
 8. [**Commit new file**] または [**Propose new file**] をクリックします。
 
-In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
+デフォルトの {% data variables.product.prodname_codeql_workflow %} では、{% data variables.product.prodname_code_scanning %} は、デフォルトブランチまたは保護されたブランチに変更をプッシュするたび、あるいはデフォルトブランチにプルリクエストを生成するたびに、コードを解析するよう設定されています。 その結果として、{% data variables.product.prodname_code_scanning %} が開始されます。
 
-### Bulk set up of {% data variables.product.prodname_code_scanning %}
-You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository.
+### {% data variables.product.prodname_code_scanning %} の一括セットアップ
+You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. 複数のリポジトリに {% data variables.product.prodname_actions %} ワークフローを追加するためのプルリクエストを発行するスクリプトの例が、[`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) リポジトリにあります。
 
-### Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+### {% data variables.product.prodname_code_scanning %} からログ出力を表示する
 
 After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
 
 {% data reusables.repositories.actions-tab %}
 
-  You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message.
+  {% data variables.product.prodname_code_scanning %} ワークフローを実行するためのエントリを含むリストが表示されます。 エントリのテキストは、コミットメッセージに付けるタイトルです。
 
-  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+  ![{% data variables.product.prodname_code_scanning %} ワークフローを表示しているアクションのリスト](/assets/images/help/repository/code-scanning-actions-list.png)
 
-1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow.
+1. {% data variables.product.prodname_code_scanning %} ワークフローのエントリをクリックします。
 
-1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+1. 左側のジョブ名をクリックします。 ここでは例として、[**Analyze (言語)**] をクリックします。
 
-  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+  ![{% data variables.product.prodname_code_scanning %} ワークフローからのログ出力](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
 
-1. Review the logging output from the actions in this workflow as they run.
+1. このワークフローの実行時にアクションから出力されるログを確認します。
 
-1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+1. すべてのジョブが完了すると、確認されたすべての {% data variables.product.prodname_code_scanning %} アラートの詳細を表示できます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。
 
 {% note %}
 
-**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page.
+**注釈:** {% data variables.product.prodname_code_scanning %} ワークフローを追加するためのプルリクエストをリポジトリに発行すると、そのプルリクエストからのアラートは、そのプルリクエストがマージされるまで {% data variables.product.prodname_code_scanning_capc %} ページに直接表示されません。 アラートが見つかった場合は、プルリクエストがマージされる前に、{% data variables.product.prodname_code_scanning_capc %} ページのバナーにある [**_(数字)_ alerts found**] をクリックしてそのアラートを表示できます。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
-  ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png)
+  ![[n alerts found] のリンクをクリック](/assets/images/help/repository/code-scanning-alerts-found-link.png)
 {% else %}
-  ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
+  ![[n alerts found] のリンクをクリック](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
 {% endif %}
 
 {% endnote %}
 
-### Understanding the pull request checks
+### プルリクエストのチェックを理解する
 
-Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis.
+Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. ワークフローの解析ジョブごとに 1 つのエントリがあり、最後のエントリは解析結果です。
 
-The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code.
+{% data variables.product.prodname_code_scanning %} 解析チェックの名前は、「ツール名 / ジョブ名 (トリガー)」という形式になります。 たとえば、C++ のコードの {% data variables.product.prodname_codeql %} 解析には、「{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)」のエントリがあります。 {% data variables.product.prodname_code_scanning %} 解析エントリで [**Details**] をクリックして、ログのデータを表示できます。 これにより、解析ジョブが失敗した場合に問題をデバッグできます。 たとえば、コンパイル型言語の {% data variables.product.prodname_code_scanning %} 解析では、アクションがコードをビルドできなかった場合に解析ジョブが失敗します。
 
-  ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png)
+  ![{% data variables.product.prodname_code_scanning %} プルリクエストのチェック](/assets/images/help/repository/code-scanning-pr-checks.png)
 
-When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
+{% data variables.product.prodname_code_scanning %} ジョブが完了すると、
+{% data variables.product.prodname_dotcom %} はプルリクエストにより追加されたアラートがないか確認し、チェックのリストに「{% data variables.product.prodname_code_scanning_capc %} の結果 / ツール名」のエントリを追加します。 {% data variables.product.prodname_code_scanning %} が 1 回でも実行された後は、[**Details**] をクリックして解析結果を表示できます。 プルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した場合、「{% data variables.product.prodname_code_scanning_capc %} 結果 / ツール名」チェックの [**Details**] をクリックすると最初は「Missing analysis」のメッセージが表示されます。
 
-  ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png)
+  ![コミットメッセージの解析がありません](/assets/images/help/repository/code-scanning-missing-analysis.png)
 
-#### Reasons for the "missing analysis" message
+#### 「missing analysis」のメッセージが出る理由
 
-After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" message.
+プルリクエストのコードを解析した後、{% data variables.product.prodname_code_scanning %} はトピックブランチ (プルリクエストを作成するために使用したブランチ) の解析と、ベースブランチ (プルリクエストをマージするブランチ) の解析を比較する必要があります。 これにより、{% data variables.product.prodname_code_scanning %} はプルリクエストにより新しく発生したアラートはどれか、ベースブランチに既に存在していたアラートはどれか、また既存のアラートがプルリクエストの変更により修正されたかを測定できます。 始めにプルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した段階では、ベースブランチはまだ解析されていないので、こうした情報を測定できません。 この場合、プルリクエストの結果チェックをくりっくすると、「Missing analysis for base commit SHA-HASH (ベースコミット SHA-HASH の解析がありません)」というメッセージが表示されます。
 
-There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
+この他にも、プルリクエストのベースブランチに対する直近のコミットで解析結果がないことがあります。 たとえば、次のような場合です。
 
-* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed.
+* プルリクエストがデフォルトブランチ以外のブランチに発行され、このブランチが解析されていない。
 
-  To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch.
+  ブランチがスキャン済みかを確認するには、{% data variables.product.prodname_code_scanning_capc %} ページに移動し、[**Branch**] ドロップダウンをクリックして該当するブランチを選択します。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%}
-  ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png)
+  ![[Branch] ドロップダウンメニューからブランチを選択](/assets/images/help/repository/code-scanning-branch-dropdown.png)
 {% else %}
-  ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png)
+  ![[Branch] ドロップダウンメニューからブランチを選択](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png)
 {% endif %}
 
-  The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
+  この状況における解決策は、そのブランチの {% data variables.product.prodname_code_scanning %} ワークフローにある `on:push` と `on:pull_request` にベースブランチの名前を追加してから、スキャンするオープンなプルリクエストを更新するよう変更することです。
 
-* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available.
+* プルリクエストのベースブランチへの直近のコミットが現在解析中で、解析がまだ利用できない。
 
-  Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+  数分待ってからプルリクエストに変更をプッシュして、{% data variables.product.prodname_code_scanning %} を再トリガーします。
 
-* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available.
+* ベースブランチの直近のコミットを解析中にエラーが発生し、そのコミットの解析ができない。
 
-  Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+  ちょっとした変更をベースブランチにマージして、この最新のコミットで {% data variables.product.prodname_code_scanning %} をトリガーしてから、プルリクエストに変更をプッシュして {% data variables.product.prodname_code_scanning %} を再トリガーします。
 
 ### 次のステップ
 
 After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can:
 
-- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
-- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-- Set up notifications for completed runs. 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)」を参照してください。
-- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
-- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning)」を参照してください。
+- リポジトリに対して生成された {% data variables.product.prodname_code_scanning %} アラートをすべて表示する。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
+- {% data variables.product.prodname_code_scanning %} をセットアップ後にサブミットしたプルリクエストに対して生成されたアラートを表示する。 詳しい情報については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
+- 実行完了の通知を設定する。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)」を参照してください。
+- {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} の初期セットアップで発生した問題を調査する。 詳しい情報については、「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/code-security/secure-coding/troubleshooting-the-codeql-workflow)」を参照してください。
+- {% data variables.product.prodname_code_scanning %} がリポジトリ内のコードをスキャンする方法をカスタマイズする。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index 94714ce915..504245727d 100644
--- a/translations/ja-JP/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ja-JP/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -1,7 +1,7 @@
 ---
-title: Triaging code scanning alerts in pull requests
-shortTitle: Triaging alerts in pull requests
-intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.'
+title: プルリクエストでコードスキャンアラートをトリガーする
+shortTitle: プルリクエストでアラートをトリガーする
+intro: 'プルリクエストで {% data variables.product.prodname_code_scanning %} が問題を特定した場合、強調表示されたコードを確認してアラートを解決できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 redirect_from:
@@ -14,47 +14,41 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
-### About {% data variables.product.prodname_code_scanning %} results on pull requests
+### プルリクエストの {% data variables.product.prodname_code_scanning %} 結果について
 
-In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+プルリクエストのチェック用に {% data variables.product.prodname_code_scanning %} が設定されているリポジトリでは、{% data variables.product.prodname_code_scanning %}がプルリクエストのコードをチェックします。 デフォルトでは、このチェックはデフォルトブランチを対象とするプルリクエストに限定されていますが、この設定は {% data variables.product.prodname_actions %} またはサードパーティの CI/CD システム内で変更できます。 変更をマージすることで、対象となるブランチに新たな {% data variables.product.prodname_code_scanning %} アラートが発生する場合には、そのアラートはプルリクエストのチェック結果として報告されます。 また、アラートではプルリクエストの [**Files changed**] タブでアノテーションとしても表示されます。 リポジトリへの書き込み権限がある場合、既存のすべての {% data variables.product.prodname_code_scanning %} アラートを [**Security**] タブで表示できます。 リポジトリのアラートに関する詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
+{% data variables.product.prodname_code_scanning %} の結果に、重大度が `error` のものがある場合、そのチェックは失敗し、チェック結果でエラーが報告されます。 {% data variables.product.prodname_code_scanning %} で出たすべての結果の重大度が低い場合、アラートは警告または通知として扱われ、チェックは成功となります。 If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or dismiss all error alerts before the pull request can be merged. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
 
-![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
+![プルリクエストの失敗した {% data variables.product.prodname_code_scanning %} チェック](/assets/images/help/repository/code-scanning-check-failure.png)
 
-### About {% data variables.product.prodname_code_scanning %} as a pull request check
+### プルリクエストのチェックとしての {% data variables.product.prodname_code_scanning %} について
 
-There are many options for configuring {% data variables.product.prodname_code_scanning %} as a pull request check, so the exact setup of each repository will vary and some will have more than one check. The check that contains the results of {% data variables.product.prodname_code_scanning %} is: **Code scanning results**.
+{% data variables.product.prodname_code_scanning %} をプルリクエストのチェックとして設定するためのオプションは多いので、正確なセットアップはそれぞれのリポジトリで異なり、複数のチェックを行う場合もあります。 {% data variables.product.prodname_code_scanning %} の結果を含むチェックは、[**Code scanning results**] です。
 
-If the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java). As with other pull request checks, you can see full details of the check failure on the **Checks** tab. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
+リポジトリが {% data variables.product.prodname_codeql_workflow %} を使用している場合、**{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** チェックを各言語で実行してから、結果チェックを実行します。 設定に問題がある場合、解析がコンパイルする必要がある言語 (C/C++、C#、Java など) でプルリクエストがビルドを中断している場合、解析は失敗することがあります。 他のプルリクエストと同様、チェック失敗の詳細内容を [**Checks**] タブで確認できます。 設定およびトラブルシューティングに関する詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning)」または「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/code-security/secure-coding/troubleshooting-the-codeql-workflow)」を参照してください。
 
-### Triaging an alert on your pull request
+### プルリクエストのアラートをトリガーする
 
-When you look at the **Files changed** tab for a pull request, you see annotations for any lines of code that triggered the alert.
+プルリクエストの [**Files changed**] タブを見ると、アラートをトリガーしたコードの行にあるアノテーションがあります。
 
-![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png)
+![プルリクエストの差分にあるアラートのアノテーション](/assets/images/help/repository/code-scanning-pr-annotation.png)
 
-If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)."
+リポジトリへの書き込み権限がある場合、一部のアノテーションにはアラートの追加的な背景を説明するリンクが含まれています。 上の例では、{% data variables.product.prodname_codeql %} 解析から [**user-provided value**] をクリックすると、データフローに信頼されていないデータが入っている場所 (ソース) が表示されます。 この場合、[**Show paths**] をクリックすることで、ソースからデータ (シンク) を使用するコードまでのフルパスを表示することもできます。 これにより、データが信頼されていないかや、ソースとシンクの間のデータサニタイズのステップを解析が認識できなかったかを簡単に確認できます。 {% data variables.product.prodname_codeql %} を使用したデータフローの解析に関する詳しい情報については、「[データフロー解析について](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)」を参照してください。
 
-To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem.
+アラートの詳細情報を表示するには、書き込み権限を持つユーザが、アノテーションに表示されている [**Show more details**] のリンクをクリックします。 これにより、ツールが提供するコンテキストとメタデータのすべてをアラートビューで確認できます。 下の例では、問題の重要度、タイプ、および関連する共通脆弱性タイプ一覧 (CWE) を示すタグが表示されています。 また、どのコミットが問題を引き起したかも表示されています。
 
-In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code.
+アラートの詳細画面において、{% data variables.product.prodname_codeql %} 解析のような一部の {% data variables.product.prodname_code_scanning %} ツールでは、問題の説明や、コードを修正する方法を説明するためる [**Show more**] リンクも含まれています。
 
-![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
+![アラートの説明と、詳細情報を表示するリンク](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Fixing an alert on your pull request
 
-Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
-
-{% if currentVersion == "enterprise-server@2.22" %}
-
-If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
+プルリクエストへのプッシュアクセスがあるユーザなら誰でも、プルリクエストで特定された {% data variables.product.prodname_code_scanning %} アラートを解決できます。 プルリクエストに変更をコミットすると、プルリクエストのチェック実行が新しくトリガーされます。 問題を修正すると、アラートは閉じられ、アノテーションは削除されます。
 
 ### Dismissing an alert on your pull request
 
@@ -67,5 +61,3 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/ja-JP/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..3a8849c1cd
--- /dev/null
+++ b/translations/ja-JP/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,63 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshooting CodeQL runner
+intro: '{% data variables.product.prodname_codeql_runner %} で問題が生じている場合、ここに掲載されているヒントを使ってトラブルを解決できます。'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### `init` コマンドに時間がかかりすぎる
+
+{% data variables.product.prodname_codeql_runner %} は、コードのビルドと解析を行う前に、{% data variables.product.prodname_codeql %} CLI と {% data variables.product.prodname_codeql %} ライブラリを含んでいる {% data variables.product.prodname_codeql %} バンドルへのアクセス権が必要です。
+
+お使いのマシンで {% data variables.product.prodname_codeql_runner %} を初めて使用する際、`init` コマンドは {% data variables.product.prodname_codeql %} バンドルをマシンにダウンロードします。 ダウンロードには数分かかります。
+{% data variables.product.prodname_codeql %} バンドルは次の実行の前にキャッシュされるので、{% data variables.product.prodname_codeql_runner %} を同じマシンで再度使用する際は、{% data variables.product.prodname_codeql %} バンドルを再ダウンロードすることはありません。
+
+この自動ダウンロードを回避するには、{% data variables.product.prodname_codeql %} バンドルをマシンに手動でダウンロードし、`init` コマンドの `--codeql-path` フラグでパスを指定します。
+
+### ビルド中にコードが見つからない
+
+{% data variables.product.prodname_codeql_runner %} の `analyze` コマンドで、`No source code was seen during the build` というエラーが出て失敗する場合、{% data variables.product.prodname_codeql %} がコードをモニターできなかったことを示しています。 このようなエラーが発生する理由として、次のようなものがあります。
+
+1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 この問題を解決するには、`init` コマンドの `--languages` フラグを使用して、解析する言語を手動で定義できます。 詳しい情報については、「[{% data variables.product.prodname_codeql_runner %} を CI システムで設定する](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)」を参照してください。
+
+1. コンパイル型言語を `autobuild` コマンドを使用せずに解析し、`init` ステップの後に自分でビルドステップを実行している。 For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the build process. `init` コマンドは、必要な環境をエクスポートする方法についての説明を生成するので、それをコピーして`init` コマンドの実行後にスクリプトを実行できます。
+   - macOS および Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - Windows で、コマンドシェル (`cmd`) またはバッチファイル (`.bat`) を使用する場合:
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - Windows で、PowerShell を使用する場合:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   環境変数は、`codeql-runner/codeql-env.json` にも保存されています。 このファイルには、環境変数キーを値にマッピングする単一の JSON オブジェクトが含まれています。 `init` コマンドで生成されたスクリプトを実行できない場合、JSON フォーマットのデータを代わりに使用できます。
+
+   {% note %}
+
+   **注釈:** `init` コマンドの`--temp-dir` フラグで一時ファイルのカスタムディレクトリを指定している場合、`codeql-env` ファイルへのパスが異なることがあります。
+
+   {% endnote %}
+
+1. macOS でコンパイル型言語を `autobuild` コマンドを使用せずに解析し、`init` ステップの後に自分でビルドステップを実行している。 SIP (システム整合性保護) が有効になっている場合、解析は失敗することがあります。OSX の最近のバージョンでは、SIP はデフォルトで有効になっています。 この問題を解決するには、ビルドコマンドの前に `$CODEQL_RUNNER` の環境変数を付けてください。 たとえばビルドコマンドが `cmd arg1 arg2` の場合、`$CODEQL_RUNNER cmd arg1 arg2` を実行します。
+
+1. コードがコンテナまたは別のマシンでビルドされている。 コンテナ化されたビルドを使用しているか、ビルドを別のマシンに委託している場合は、必ず {% data variables.product.prodname_codeql_runner %} をコンテナまたはビルドタスクを実行するマシンで実行してください。 詳しい情報については、「[コンテナで CodeQL コードスキャンを実行する](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
index d15b776c04..7e9806411a 100644
--- a/translations/ja-JP/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
+++ b/translations/ja-JP/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting the CodeQL workflow
-shortTitle: Troubleshooting CodeQL
-intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.'
+title: CodeQL ワークフローのトラブルシューティング
+shortTitle: CodeQL のトラブルシューティング
+intro: '{% data variables.product.prodname_code_scanning %} で問題が生じている場合、ここに掲載されている問題解決のためのヒントを使ってトラブルを解決できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning
@@ -14,47 +14,52 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
-### Producing detailed logs for debugging
+### デバッグ用の詳細なログを生成する
 
-To produce more detailed logging output, you can enable step debug logging. 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)」を参照してください。
+詳細なログ出力を生成するため、ステップのデバッグロギングを有効化することができます。 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)」を参照してください。
 
 ### コンパイル言語の自動ビルドの失敗
 
 プロジェクト内のコンパイル言語のコードの自動ビルドが失敗した場合は、次のトラブルシューティングのステップを試してください。
 
-- {% data variables.product.prodname_code_scanning %} ワークフローから `autobuild` ステップを削除し、特定のビルドステップを追加します。 ワークフローの編集に関する詳しい情報は、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。 For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+- {% data variables.product.prodname_code_scanning %} ワークフローから `autobuild` ステップを削除し、特定のビルドステップを追加します。 ワークフローの編集に関する詳しい情報は、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。 `autobuild` ステップの置き換えに関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
-- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
+- ワークフローが解析する言語を明示的に指定していない場合、{% data variables.product.prodname_codeql %} はコードベースでサポートされている言語を暗黙的に検出します。 この設定では、コンパイル型言語である C/C++、C#、Java のうち、{% data variables.product.prodname_codeql %} はソースファイルの数が最も多い言語のみを解析します。 ワークフローを編集し、解析する言語を指定したビルドマトリクスを追加してください。 デフォルトの CodeQL 解析では、こうしたマトリクスを使用しています。
 
-  The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
+  以下はワークフローからの抜粋で、まず言語を指定するジョブ戦略におけるマトリクスの使用法を示し、次に「Initialize {% data variables.product.prodname_codeql %}」のステップで各言語を参照しています。
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
         matrix:
           language: ['csharp', 'cpp', 'javascript']
 
+      steps:
       ...
-
-      - name: Initialize {% data variables.product.prodname_codeql %}
-        uses: github/codeql-action/init@v1
-        with:
-          languages: {% raw %}${{ matrix.language }}{% endraw %}
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: github/codeql-action/init@v1
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
-  For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
+  ワークフローの編集に関する詳しい情報については、「[コードスキャンを設定する](/code-security/secure-coding/configuring-code-scanning)」を参照してください。
 
 ### ビルド中にコードが見つからない
 
-If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. このようなエラーが発生する理由として、次のようなものがあります。
+ワークフローでエラー `No source code was seen during the build` または `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32` が発生した場合、{% data variables.product.prodname_codeql %} がコードを監視できなかったことを示しています。 このようなエラーが発生する理由として、次のようなものがあります。
 
-1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. たとえば、次の設定では Go と JavaScript のみを分析します。
+1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 この問題を解決するには、`language` マトリクスにある言語のリストを更新し、解析する言語を手動で定義します。 たとえば、次の設定では Go と JavaScript のみを分析します。
 
   ```yaml
   strategy:
@@ -65,19 +70,19 @@ If your workflow fails with an error `No source code was seen during the build`
       # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python']
       language: ['go', 'javascript']
   ```
-For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
-1. {% data variables.product.prodname_code_scanning %} ワークフローはコンパイルされた言語（C、C++、C#、または Java）を分析しているが、コードはコンパイルされていない。 デフォルトでは、{% data variables.product.prodname_codeql %} 分析ワークフローには `autobuild` ステップが含まれていますが、このステップはベスト エフォートプロセスを表しており、特定のビルド環境によっては、コードのビルドに失敗する可能性があります。 `autobuild` ステップを削除し、ビルドステップを手動で含めない場合も、コンパイルが失敗する可能性があります。  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
+1. {% data variables.product.prodname_code_scanning %} ワークフローはコンパイルされた言語（C、C++、C#、または Java）を分析しているが、コードはコンパイルされていない。 デフォルトでは、{% data variables.product.prodname_codeql %} 分析ワークフローには `autobuild` ステップが含まれていますが、このステップはベスト エフォートプロセスを表しており、特定のビルド環境によっては、コードのビルドに失敗する可能性があります。 `autobuild` ステップを削除し、ビルドステップを手動で含めない場合も、コンパイルが失敗する可能性があります。  ビルドステップの指定に関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 1. ワークフローはコンパイルされた言語（C、C++、C#、または Java）を分析しているが、パフォーマンスを向上させるためにビルドの一部がキャッシュされている（Gradle や Bazel などのビルドシステムで発生する可能性が最も高い）。 {% data variables.product.prodname_codeql %} はコンパイラのアクティビティを監視してリポジトリ内のデータフローを理解するため、{% data variables.product.prodname_codeql %} は分析を実行するために完全なビルドを実行する必要があります。
 1. ワークフローはコンパイルされた言語（C、C++、C＃、または Java）を分析しているが、ワークフローの `init` ステップと `analyze` ステップの間でコンパイルが行われていない。 {% data variables.product.prodname_codeql %} では、コンパイラのアクティビティを監視して分析を実行するために、これらの 2 つのステップ間でビルドを行う必要があります。
-1. コンパイルされたコード（C、C++、C#、または Java）は正常にコンパイルされたが、{% data variables.product.prodname_codeql %} がコンパイラの呼び出しを検出できない。 The most common causes are:
+1. コンパイルされたコード（C、C++、C#、または Java）は正常にコンパイルされたが、{% data variables.product.prodname_codeql %} がコンパイラの呼び出しを検出できない。 一般的な原因は次のようなものです。
 
-   * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
-   * Building using a distributed build system external to GitHub Actions, using a daemon process.
-   * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
+   * ビルドプロセスを {% data variables.product.prodname_codeql %} とは別のコンテナで実行している。 詳しい情報については、「[コンテナで CodeQL コードスキャンを実行する](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)」を参照してください。
+   * デーモンプロセスを使用して、GitHub Actions の外部で分散ビルドシステムによりビルドしている。
+   * {% data variables.product.prodname_codeql %} は、使用されているコンパイラを認識していない。
 
-  For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. .NET Core 3.0 以降では、`UseSharedCompilation` フラグは必要ありません。
+  .NET Framework プロジェクト、および .NET Core 2 をターゲットとする `dotnet build` または `msbuild` を使用する C# プロジェクトでは、コードをビルドするときに、ワークフローの `run` ステップで `/p:UseSharedCompilation=false` を指定する必要があります。 .NET Core 3.0 以降では、`UseSharedCompilation` フラグは必要ありません。
 
-  For example, the following configuration for C# will pass the flag during the first build step.
+  たとえば、次の C# に対する設定では、最初のビルドステップ中にフラグが渡されます。
 
    ``` yaml
    - run: |
@@ -86,23 +91,23 @@ For more information, see the workflow extract in "[Automatic build for a compil
 
   特定のコンパイラまたは設定で別の問題が発生した場合は、{% data variables.contact.contact_support %} までお問い合わせください。
 
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+ビルドステップの指定に関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
 ### リポジトリの一部が `autobuild` を使用して分析されない
 
-{% data variables.product.prodname_codeql %} の `autobuild` 機能は、ヒューリスティックスを使用してリポジトリにコードをビルドしますが、このアプローチでは、リポジトリの分析が不完全になることがあります。 たとえば、単一のリポジトリに複数の `build.sh` コマンドが存在する場合、`autobuild` ステップはコマンドの 1 つしか実行しないため、分析が完了しない場合があります。 これを解決するには、`autobuild` ステップを、分析するすべてのソースコードをビルドするビルドステップに置き換えます。 For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+{% data variables.product.prodname_codeql %} の `autobuild` 機能は、ヒューリスティックスを使用してリポジトリにコードをビルドしますが、このアプローチでは、リポジトリの分析が不完全になることがあります。 たとえば、単一のリポジトリに複数の `build.sh` コマンドが存在する場合、`autobuild` ステップはコマンドの 1 つしか実行しないため、分析が完了しない場合があります。 これを解決するには、`autobuild` ステップを、分析するすべてのソースコードをビルドするビルドステップに置き換えます。 詳しい情報については、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
 ### ビルドに時間がかかりすぎる
 
 {% data variables.product.prodname_codeql %} 分析でのビルドの実行に時間がかかりすぎる場合は、ビルド時間を短縮するための方法がいくつかあります。
 
-#### Increase the memory or cores
+#### メモリまたはコアを増やす
 
-If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners.
+セルフホストランナーを使用して {% data variables.product.prodname_codeql %} 解析を実行している場合、ランナーのメモリやコア数を増やすことができます。
 
 #### マトリックスビルドを使用して分析を並列化する
 
-The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
+デフォルトの {% data variables.product.prodname_codeql_workflow %} は言語のビルドマトリクスを使用しており、これにより各言語の解析が並列で実行される場合があります。 「Initialize CodeQL」ステップで解析する言語を直接指定している場合、各言語の解析は順次行われます。 複数の言語で解析を高速化するには、マトリクスを使用するようワークフローを変更してください。 詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
 
 #### 1 つのワークフローで分析されるコードの量を減らす
 
@@ -116,7 +121,7 @@ Java、C、C++、C# などのコンパイルされた言語の場合、{% data v
 
 #### `schedule` イベント中にのみ実行する
 
-それでも分析が遅すぎるために、`push` または `pull_request` イベント中に実行できない場合は、`schedule` イベントでのみ分析をトリガーすることをお勧めします。 For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
+それでも分析が遅すぎるために、`push` または `pull_request` イベント中に実行できない場合は、`schedule` イベントでのみ分析をトリガーすることをお勧めします。 詳しい情報については、「[イベント](/actions/learn-github-actions/introduction-to-github-actions#events)」を参照してください。
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Results differ between analysis platforms
@@ -150,29 +155,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
-For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
+{% data variables.product.prodname_codeql %} ワークフローファイルの編集に関する詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を編集する](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/ja-JP/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index f5f47211f2..9deaa48b7a 100644
--- a/translations/ja-JP/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/ja-JP/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,27 +15,30 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
 ### {% data variables.product.prodname_code_scanning %} に対する SARIF ファイルのアップロードについて
 
-SARIF ファイルに `partialFingerprints` が含まれていない場合、`upload-sarif` アクションは、`partialFingerprints` フィールドを計算し、アラートの重複を防止しようと試みます。 {% data variables.product.prodname_dotcom %} は、リポジトリに SARIF ファイルと静的分析で使用されるソースコードの両方が含まれている場合にのみ、`partialFingerprints` を作成できます。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+SARIF ファイルに `partialFingerprints` が含まれていない場合、`upload-sarif` アクションは、`partialFingerprints` フィールドを計算し、アラートの重複を防止しようと試みます。 {% data variables.product.prodname_dotcom %} は、リポジトリに SARIF ファイルと静的分析で使用されるソースコードの両方が含まれている場合にのみ、`partialFingerprints` を作成できます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. 詳しい情報については「[{% data variables.product.prodname_code_scanning %}の SARIF サポート](/code-security/secure-coding/sarif-support-for-code-scanning)」を参照してください。
+SARIF ファイルは、{% data variables.product.prodname_codeql %} を含む多くの静的解析セキュリティテストツールを使用して生成できます。 生成するファイルは、SARIF バージョン 2.1.0 である必要があります。 詳しい情報については「[{% data variables.product.prodname_code_scanning %}の SARIF サポート](/code-security/secure-coding/sarif-support-for-code-scanning)」を参照してください。
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. 最適なアップロード方法は、SARIF ファイルの生成方法によって異なります。以下、例を示します。
 
-- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. SARIF ファイルは、ファイルのアップロードに使用したものと同じ {% data variables.product.prodname_actions %} ワークフローで実行する SARIF 互換の分析ツールから生成できます。
-- "[ワークフロー実行の管理](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)"
-- {% data variables.product.prodname_dotcom %} は、リポジトリにアップロードされた SARIF ファイルからの {% data variables.product.prodname_code_scanning %} アラートを表示します。 If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)").
-- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
+- {% data variables.product.prodname_actions %} を使用して {% data variables.product.prodname_codeql %} アクションを実行している場合、追加のアクションは不要です。 SARIF ファイルは、ファイルのアップロードに使用したものと同じ {% data variables.product.prodname_actions %} ワークフローで実行する SARIF 互換の分析ツールから生成できます。
+- "[ワークフロー実行の管理](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- {% data variables.product.prodname_dotcom %} は、リポジトリにアップロードされた SARIF ファイルからの {% data variables.product.prodname_code_scanning %} アラートを表示します。 If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").
+- 結果をリポジトリ外に成果物として生成するツールの場合、{% data variables.product.prodname_code_scanning %} API を使用してファイルをアップロードできます (詳しい情報については、「[解析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」を参照)。
 
 {% data reusables.code-scanning.not-available %}
 
 ### {% data variables.product.prodname_actions %} での {% data variables.product.prodname_code_scanning %} 分析をアップロードする
 
-サードパーティの SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードするには、{% data variables.product.prodname_actions %} ワークフローが必要です。 For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+サードパーティの SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードするには、{% data variables.product.prodname_actions %} ワークフローが必要です。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
 ワークフローは、`upload-sarif` アクションを使用する必要があります。 これには、アップロードの設定に使用できる入力パラメータがあります。 使用する主な入力パラメータは、アップロードする SARIF ファイルのファイルまたはディレクトリを設定する `sarif-file` です。 ディレクトリまたはファイルのパスは、リポジトリのルートからの相対パスです。 詳しい情報については、「[`upload-sarif` アクション](https://github.com/github/codeql-action/tree/HEAD/upload-sarif)」を参照してください。
 
@@ -51,7 +54,7 @@ SARIF ファイルをリポジトリにコミットした後でアップロー
 
 この例のワークフローは、コミットがリポジトリにプッシュされるたびに実行されます。 アクションは `partialFingerprints` プロパティを使用して、変更が発生したかどうかを判断します。 コミットがプッシュされたときに実行されるだけでなく、ワークフローは週に 1 回実行されるようにスケジュールされます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-このワークフローは、リポジトリのルートにある `results.sarif` ファイルをアップロードします。 For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+このワークフローは、リポジトリのルートにある `results.sarif` ファイルをアップロードします。 ワークフローファイルの作成に関する詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
 または、このワークフローを変更して、SARIF ファイルのディレクトリをアップロードすることもできます。 たとえば、すべての SARIF ファイルをリポジトリのルートにある `sarif-output` というディレクトリに配置し、アクションの入力パラメータ `sarif_file` を `sarif-output` に設定できます。
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # このステップでは、リポジトリのコピーをチェックアウトします。
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # リポジトリのルートに対する SARIF ファイルへの相対パス
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### ESLint 分析ツールを実行するワークフローの例
@@ -85,9 +90,9 @@ jobs:
 
 この例のワークフローは、コミットがリポジトリにプッシュされるたびに実行されます。 アクションは `partialFingerprints` プロパティを使用して、変更が発生したかどうかを判断します。 コミットがプッシュされたときに実行されるだけでなく、ワークフローは週に 1 回実行されるようにスケジュールされます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-ワークフローでは、ESLint 静的分析ツールをワークフローのステップとして実行する例を示しています。 `Run ESLint` ステップは ESLint ツールを実行して、`results.sarif` ファイルを出力します。 次に、ワークフローは `upload-sarif` アクションを使用して、`results.sarif` ファイルを {% data variables.product.prodname_dotcom %} にアップロードします。 For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+ワークフローでは、ESLint 静的分析ツールをワークフローのステップとして実行する例を示しています。 `Run ESLint` ステップは ESLint ツールを実行して、`results.sarif` ファイルを出力します。 次に、ワークフローは `upload-sarif` アクションを使用して、`results.sarif` ファイルを {% data variables.product.prodname_dotcom %} にアップロードします。 ワークフローファイルの作成に関する詳しい情報については、「[GitHub Actions 入門](/actions/learn-github-actions/introduction-to-github-actions)」を参照してください。
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # コードがリポジトリにプッシュされるたびに、スケジュールに従ってワークフローを実行します。
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### 参考リンク
 
 - [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
-- "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
+- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
+- 「[解析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」
diff --git a/translations/ja-JP/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/ja-JP/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index 98c345ad6a..018f98275a 100644
--- a/translations/ja-JP/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/ja-JP/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 0e4fc75ecc..b90460d7af 100644
--- a/translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -43,7 +43,7 @@ Publishing the details of a security vulnerability doesn't make maintainers look
 
 The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
 
- If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
+ If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
 
  If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
 
@@ -55,7 +55,7 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
 
- If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
+ If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
 
  As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。
 
diff --git a/translations/ja-JP/content/code-security/security-advisories/index.md b/translations/ja-JP/content/code-security/security-advisories/index.md
index bfe281adad..9b0993ab89 100644
--- a/translations/ja-JP/content/code-security/security-advisories/index.md
+++ b/translations/ja-JP/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### 目次
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index e75f92a447..7ca6152c33 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -35,6 +35,7 @@ topics:
 セキュリティアップデートを有効にした場合、セキュリティアップデートの追加に対するプルリクエストが表示されることがあります。 これらは、デフォルトブランチへの依存関係に対する {% data variables.product.prodname_dependabot %} アラートによってトリガーされます。 {% data variables.product.prodname_dependabot %} はプルリクエストを自動的に生成し、脆弱性のある依存関係を更新します。
 
 ### サポートされているリポジトリとエコシステム
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 サポートされているパッケージマネージャーのいずれかの依存関係マニフェストまたはロックファイルを含むリポジトリのバージョン更新を設定できます。 一部のパッケージマネージャーでは、依存関係のベンダを設定することもできます。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor) 」を参照してください。
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md
index 9f7f50a549..9c9ea0b6a9 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md
@@ -14,7 +14,7 @@ topics:
 {% data variables.product.prodname_dotcom %} は、脆弱性のある依存関係を削除および回避するための次のツールを提供しています。
 
 #### 依存関係グラフ
-The dependency graph is a summary of the manifest and lock files stored in a repository. コードベースが依存するエコシステムとパッケージ（依存関係）、およびプロジェクトに依存するリポジトリとパッケージ（依存関係）が表示されます。 依存関係グラフの情報は、依存関係のレビューと {% data variables.product.prodname_dependabot %} によって使用されます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
+依存関係グラフは、リポジトリに保存されているマニフェストファイルおよびロックファイルのサマリーです。 コードベースが依存するエコシステムとパッケージ（依存関係）、およびプロジェクトに依存するリポジトリとパッケージ（依存関係）が表示されます。 依存関係グラフの情報は、依存関係のレビューと {% data variables.product.prodname_dependabot %} によって使用されます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
 
 #### 依存関係のレビュー
 プルリクエストの依存関係のレビューを確認することで、依存関係からコードベースに脆弱性が発生するのを防ぐことができます。 プルリクエストが脆弱性のある依存関係を追加したり、依存関係を脆弱性のあるバージョンに変更した場合、これは依存関係のレビューで強調表示されます。 プルリクエストをマージする前に、依存関係をパッチを適用したバージョンに変更できます。 For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md
index 3f516de9cb..3251964b21 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md
@@ -1,13 +1,13 @@
 ---
 title: About the dependency graph
-intro: 'You can use the dependency graph to identify all your project''s dependencies. The dependency graph supports a range of popular package ecosystems.'
+intro: You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems.
 redirect_from:
   - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph
 versions:
   free-pro-team: '*'
   enterprise-server: '>=3.0'
 topics:
-  - repositories
+  - Repositories
 ---
 <!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database.md
index 58b953e136..64b12d3a6f 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database.md
@@ -77,7 +77,7 @@ topics:
 
 1. Https://github.com/advisories にアクセスします。
 2. アドバイザリをクリックします。
-3. アドバイザリページの上部にある [**Dependabot alerts**] をクリックします。 ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+3. アドバイザリページの上部にある [**Dependabot alerts**] をクリックします。 ![Dependabotアラート](/assets/images/help/security/advisory-database-dependabot-alerts.png)
 4. 必要に応じて、リストをフィルタするには、検索バーまたはドロップダウンメニューを使用します。 [Organization] ドロップダウンメニューを使用すると、オーナー（Organization またはユーザ）ごとに {% data variables.product.prodname_dependabot_alerts %} をフィルタできます。 ![アラートをフィルタするための検索バーとドロップダウンメニュー](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
 5. 脆弱性の詳細、および脆弱性のあるリポジトリを修正する方法に関するアドバイスについては、リポジトリ名をクリックしてください。
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index ad6ae72473..13fb1a6d3e 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -17,41 +17,41 @@ topics:
 
 このファイルは、リポジトリの `.github` ディレクトリに保存する必要があります。 *dependabot.yml* ファイルを追加または更新すると、即座にバージョン更新を確認します。 セキュリティアップデートに影響するオプションは、次にセキュリティアラートがセキュリティアップデートのためのプルリクエストをトリガーするときにも使用されます。 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」および「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。
 
-*dependabot.yml* ファイルには、必須の最上位キーに `version` と `updates` の 2 つがあります。 You can, optionally, include a top-level `registries` key. The file must start with `version: 2`.
+*dependabot.yml* ファイルには、必須の最上位キーに `version` と `updates` の 2 つがあります。 必要に応じて、最上位に `registries` キーを含めることができます。 ファイルは、`version: 2` で始まる必要があります。
 
-### Configuration options for updates
+### 更新の設定オプション
 
-The top-level `updates` key is mandatory. You use it to configure how {% data variables.product.prodname_dependabot %} updates the versions or your project's dependencies. Each entry configures the update settings for a particular package manager. You can use the following options.
+最上位の `updates` キーは必須です。 これを使用することで、{% data variables.product.prodname_dependabot %} がバージョンやプロジェクトの依存性を更新する方法を設定できます。 各エントリは、特定のパッケージマネージャーの更新設定を行います。 次のオプションを使用できます。
 
-| Option                                                                     |  必須   | 説明                                                                                  |
-|:-------------------------------------------------------------------------- |:-----:|:----------------------------------------------------------------------------------- |
-| [`package-ecosystem`](#package-ecosystem)                                  | **X** | 使用するパッケージマネージャー                                                                     |
-| [`directory`](#directory)                                                  | **X** | パッケージマニフェストの場所                                                                      |
-| [`schedule.interval`](#scheduleinterval)                                   | **X** | 更新を確認する頻度                                                                           |
-| [`allow`](#allow)                                                          |       | 許可する更新をカスタマイズする                                                                     |
-| [`assignees`](#assignees)                                                  |       | プルリクエストのアサイン担当者                                                                     |
-| [`commit-message`](#commit-message)                                        |       | コミットメッセージの環境設定                                                                      |
-| [`ignore`](#ignore)                                                        |       | 特定の依存関係またはバージョンを無視する                                                                |
-| [`insecure-external-code-execution`](#insecure-external-code-execution)    |       | Allow or deny code execution in manifest files                                      |
-| [`labels`](#labels)                                                        |       | プルリクエストに設定するラベル                                                                     |
-| [`マイルストーン`](#milestone)                                                    |       | プルリクエストに設定するマイルストーン                                                                 |
-| [`open-pull-requests-limit`](#open-pull-requests-limit)                    |       | バージョン更新時のオープンなプルリクエスト数を制限する                                                         |
-| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) |       | プルリクエストブランチ名の区切り文字を変更する                                                             |
-| [`rebase-strategy`](#rebase-strategy)                                      |       | 自動リベースを無効にする                                                                        |
-| [`registries`](#registries)                                                |       | Private registries that {% data variables.product.prodname_dependabot %} can access |
-| [`reviewers`](#reviewers)                                                  |       | プルリクエストのレビュー担当者                                                                     |
-| [`schedule.day`](#scheduleday)                                             |       | 更新を確認する曜日                                                                           |
-| [`schedule.time`](#scheduletime)                                           |       | 更新を確認する時刻 (hh:mm)                                                                   |
-| [`schedule.timezone`](#scheduletimezone)                                   |       | 時刻のタイムゾーン（ゾーン識別子）                                                                   |
-| [`target-branch`](#target-branch)                                          |       | プルリクエストを作成するブランチ                                                                    |
-| [`vendor`](#vendor)                                                        |       | Update vendored or cached dependencies                                              |
-| [`versioning-strategy`](#versioning-strategy)                              |       | マニフェストのバージョン要件の更新方法                                                                 |
+| Option                                                                     |  必須   | 説明                                                                   |
+|:-------------------------------------------------------------------------- |:-----:|:-------------------------------------------------------------------- |
+| [`package-ecosystem`](#package-ecosystem)                                  | **X** | 使用するパッケージマネージャー                                                      |
+| [`directory`](#directory)                                                  | **X** | パッケージマニフェストの場所                                                       |
+| [`schedule.interval`](#scheduleinterval)                                   | **X** | 更新を確認する頻度                                                            |
+| [`allow`](#allow)                                                          |       | 許可する更新をカスタマイズする                                                      |
+| [`assignees`](#assignees)                                                  |       | プルリクエストのアサイン担当者                                                      |
+| [`commit-message`](#commit-message)                                        |       | コミットメッセージの環境設定                                                       |
+| [`ignore`](#ignore)                                                        |       | 特定の依存関係またはバージョンを無視する                                                 |
+| [`insecure-external-code-execution`](#insecure-external-code-execution)    |       | マニフェストファイル内でコードの実行を許可または拒否する                                         |
+| [`labels`](#labels)                                                        |       | プルリクエストに設定するラベル                                                      |
+| [`マイルストーン`](#milestone)                                                    |       | プルリクエストに設定するマイルストーン                                                  |
+| [`open-pull-requests-limit`](#open-pull-requests-limit)                    |       | バージョン更新時のオープンなプルリクエスト数を制限する                                          |
+| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) |       | プルリクエストブランチ名の区切り文字を変更する                                              |
+| [`rebase-strategy`](#rebase-strategy)                                      |       | 自動リベースを無効にする                                                         |
+| [`registries`](#registries)                                                |       | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ |
+| [`reviewers`](#reviewers)                                                  |       | プルリクエストのレビュー担当者                                                      |
+| [`schedule.day`](#scheduleday)                                             |       | 更新を確認する曜日                                                            |
+| [`schedule.time`](#scheduletime)                                           |       | 更新を確認する時刻 (hh:mm)                                                    |
+| [`schedule.timezone`](#scheduletimezone)                                   |       | 時刻のタイムゾーン（ゾーン識別子）                                                    |
+| [`target-branch`](#target-branch)                                          |       | プルリクエストを作成するブランチ                                                     |
+| [`vendor`](#vendor)                                                        |       | ベンダーまたはキャッシュされた依存関係を更新する                                             |
+| [`versioning-strategy`](#versioning-strategy)                              |       | マニフェストのバージョン要件の更新方法                                                  |
 
 これらのオプションは、次のようなカテゴリに幅広く適合しています。
 
 - すべての設定に含める必要がある必須のセットアップオプション: [`package-ecosystem`](#package-ecosystem)、 [`directory`](#directory)、[`schedule.interval`](#scheduleinterval)
 - 更新スケジュールをカスタマイズするためのオプション: [`schedule.time`](#scheduletime)、[`schedule.timezone`](#scheduletimezone)、 [`schedule.day`](#scheduleday)
-- Options to control which dependencies are updated: [`allow`](#allow), [`ignore`](#ignore), [`vendor`](#vendor).
+- 更新する依存関係を制御するオプション: [`allow`](#allow)、[`ignore`](#ignore)、[`vendor`](#vendor)
 - プルリクエストにメタデータを追加するオプション: [`reviewers`](#reviewers)、[`assignees`](#assignees)、[`labels`](#labels)、 [`milestone`](#milestone)
 - プルリクエストの動作を変更するオプション: [`target-branch`](#target-branch)、[`versioning-strategy`](#versioning-strategy)、[`commit-message`](#commit-message)、[`rebase-strategy`](#rebase-strategy)、[`pull-request-branch-name.separator`](#pull-request-branch-nameseparator)
 
@@ -69,7 +69,7 @@ The top-level `updates` key is mandatory. You use it to configure how {% data va
 
 #### `package-ecosystem`
 
-**必須**。 You add one `package-ecosystem` element for each package manager that you want {% data variables.product.prodname_dependabot %} to monitor for new versions. リポジトリには、これらの各パッケージマネージャーの依存関係マニフェストまたはロックファイルも含まれている必要があります。 If you want to enable vendoring for a package manager that supports it, the vendored dependencies must be located in the required directory. For more information, see [`vendor`](#vendor) below.
+**必須**。 {% data variables.product.prodname_dependabot %} で新しいバージョンを監視するパッケージマネージャーごとに、`package-ecosystem` 要素を1つ追加してください。 リポジトリには、これらの各パッケージマネージャーの依存関係マニフェストまたはロックファイルも含まれている必要があります。 サポートするパッケージマネージャーに対してベンダリングを有効にする場合、ベンダリングされた依存関係が必須ディレクトリに存在する必要があります。 詳しい情報については、以下の [`vendor`](#vendor) を参照してください。
 
 {% data reusables.dependabot.supported-package-managers %}
 
@@ -100,7 +100,7 @@ updates:
 
 #### `directory`
 
-**必須**。 You must define the location of the package manifests for each package manager (for example, the *package.json* or *Gemfile*). GitHub Actions 以外のすべてのエコシステムで、リポジトリのルートに対する相対ディレクトリを定義します。 GitHub Actions の場合、ディレクトリを `/` に設定し、`.github/workflows` でワークフローファイルを確認します。
+**必須**。 各パッケージマネージャー (*package.json* や *Gemfile* など) のパッケージマニフェストの場所を定義する必要があります。 GitHub Actions 以外のすべてのエコシステムで、リポジトリのルートに対する相対ディレクトリを定義します。 GitHub Actions の場合、ディレクトリを `/` に設定し、`.github/workflows` でワークフローファイルを確認します。
 
 ```yaml
 # 各パッケージマネージャーのマニフェストファイルの場所を指定する
@@ -129,7 +129,7 @@ updates:
 
 #### `schedule.interval`
 
-**必須**。 You must define how often to check for new versions for each package manager. デフォルトでは、午前 5 時 (UTC) に設定されています。 これを変更するには、[`schedule.time`](#scheduletime) と [`schedule.timezone`](#scheduletimezone) を使用します。
+**必須**。 各パッケージマネージャーに対して、新しいバージョンを確認する頻度を定義する必要があります。 デフォルトでは、午前 5 時 (UTC) に設定されています。 これを変更するには、[`schedule.time`](#scheduletime) と [`schedule.timezone`](#scheduletimezone) を使用します。
 
 - `毎日`: 月曜日～金曜日の平日に実行されます。
 - `毎週`: 毎週 1 回実行されます。 デフォルトでは月曜日に設定されています。 これを変更するには、[`schedule.day`](#scheduleday) を使用します。
@@ -156,7 +156,7 @@ updates:
 
 {% note %}
 
-**Note**: `schedule` defines when {% data variables.product.prodname_dependabot %} attempts a new update. However, it's not the only time you may receive pull requests. Updates can be triggered based on changes to your `dependabot.yml` file, changes to your manifest file(s) after a failed update, or {% data variables.product.prodname_dependabot_security_updates %}. For more information, see "[Frequency of {% data variables.product.prodname_dependabot %} pull requests](/github/administering-a-repository/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+**注釈**: `schedule` は、{% data variables.product.prodname_dependabot %} が新規更新を試行するタイミングを設定します。 ただし、プルリクエストを受け取るタイミングはこれだけではありません。 更新は、 `dependabot.yml` ファイルへの変更、更新失敗後のマニフェストファイルへの変更、または {% data variables.product.prodname_dependabot_security_updates %} に基づいてトリガーされることがあります。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} プルリクエストの頻度](/github/administering-a-repository/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)」および「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。
 
 {% endnote %}
 
@@ -164,7 +164,7 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-更新する依存関係をカスタマイズするには、`allow` オプションを使用します。 これは、脆弱性のある依存関係のセキュリティアップデートに影響しません。 次のオプションを使用できます。
+更新する依存関係をカスタマイズするには、`allow` オプションを使用します。 This applies to both version and security updates. 次のオプションを使用できます。
 
 - `dependency-name`: 名前が一致する依存関係の更新を許可するために使用し、必要に応じて `*` を使用して 0 文字以上の文字と一致させます。 Java の依存関係の場合、`dependency-name` 属性のフォーマットは `groupId:artifactId` です（`org.kohsuke:github-api` など）。
 - `dependency-type`: 特定の種類の依存関係の更新を許可するために使用します。
@@ -321,16 +321,16 @@ updates:
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)."
+**注釈**: 設定ファイルの `ignore` オプションにアクセス不可の依存関係を追加した場合でも、 ファイルの依存関係のすべてにアクセスできる場合には、{% data variables.product.prodname_dependabot %} は、マニフェストまたはロックされたファイルのみにバージョン更新を実行します。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)」および「[{% data variables.product.prodname_dependabot %} エラーのトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)」を参照してください。
 
 
 {% endnote %}
 
 #### `insecure-external-code-execution`
 
-Package managers with the `package-ecosystem` values `bundler`, `mix`, and `pip` may execute external code in the manifest as part of the version update process. This might allow a compromised package to steal credentials or gain access to configured registries. When you add a [`registries`](#registries) setting within an `updates` configuration, {% data variables.product.prodname_dependabot %} automatically prevents external code execution, in which case the version update may fail. You can choose to override this behavior and allow external code execution for `bundler`, `mix`, and `pip` package managers by setting `insecure-external-code-execution` to `allow`.
+`package-ecosystem` の値が `bundler`、`mix`、および`pip` であるパッケージマネージャーは、バージョン更新プロセスの一環として間にファスト内の外部コードを実行できます。 これにより、セキュリティが侵害されたパッケージが認証情報を盗んだり、構成済みのレジストリにアクセスしたりすることが可能になる場合もあります。 `updates` 設定内で [`registries`](#registries) を追加すると、{% data variables.product.prodname_dependabot %} は自動的に外部コードの実行を防ぎ、この場合はバージョン更新が失敗することもあります。 この動作をオーバーライドし、`bundler`、`mix`、および `pip` パッケージマネージャーで外部コードの実行を許可するには、`insecure-external-code-execution` を `allow` に設定します。
 
-You can explicitly deny external code execution, irrespective of whether there is a `registries` setting for this update configuration, by setting `insecure-external-code-execution` to `deny`.
+`insecure-external-code-execution` を `deny` に設定することで、この更新設定に `registries` 設定があるかどうかにかかわらず、明示的に外部コードの実行を拒否できます。
 
 {% raw %}
 ```yaml
@@ -395,7 +395,7 @@ updates:
 
 #### `open-pull-requests-limit`
 
-デフォルトでは、{% data variables.product.prodname_dependabot %} は、バージョン更新に対して最大 5 つのプルリクエストをオープンします。 Once there are five open pull requests, new requests are blocked until you merge or close some of the open requests, after which new pull requests can be opened on subsequent updates. この制限を変更するには、`open-pull-requests-limit` を使用します。 これは、パッケージマネージャーのバージョン更新を一時的に無効にする簡単な方法としても使用できます。
+デフォルトでは、{% data variables.product.prodname_dependabot %} は、バージョン更新に対して最大 5 つのプルリクエストをオープンします。 5 つのプルリクエストがオープンになると、オープンになっているリクエストの一部をマージまたはクローズするまで、新しいリクエストはブロックされます。オープンになっているリクエストの一部をマージまたはクローズしたら、その後の更新で新しいプルリクエストを開くことができます。 この制限を変更するには、`open-pull-requests-limit` を使用します。 これは、パッケージマネージャーのバージョン更新を一時的に無効にする簡単な方法としても使用できます。
 
 このオプションはセキュリティアップデートに影響を与えません。セキュリティアップデートには、10 件のオープンプルリクエストの内部制限があります。
 
@@ -444,12 +444,12 @@ updates:
 
 #### `rebase-strategy`
 
-デフォルトでは、{% data variables.product.prodname_dependabot %} は、競合を検出すると、オープンなプルリクエストを自動的にリベースします。 この動作を無効にするには、`rebase-strategy` を使用します。
+By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. この動作を無効にするには、`rebase-strategy` を使用します。
 
 利用可能なリベース戦略
 
 - `disabled` で自動リベースを無効にします。
-- `auto` をデフォルトの動作に使用し、競合が検出されたときにオープンなプルリクエストをリベースします。
+- `auto` to use the default behavior and rebase open pull requests when changes are detected.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -468,15 +468,15 @@ updates:
 
 #### `registries`
 
-To allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you must include a `registries` setting within the relevant `updates` configuration. You can allow all of the defined registries to be used by setting `registries` to `"*"`. Alternatively, you can list the registries that the update can use. To do this, use the name of the registry as defined in the top-level `registries` section of the _dependabot.yml_ file.
+バージョン更新の実行時に {% data variables.product.prodname_dependabot %} がプライベートパッケージレジストリにアクセスできるようにするには、関係する `updates` 設定に `registries` 設定を含める必要があります。 `registries` を `"*"` に設定することで、定義されたリポジトリをすべて使用できるようにすることができます。 また、更新が使用できるレジストリをリストすることもできます。 これを行うには、_dependabot.yml_ ファイルの最上位の `registries` セクションで定義されているレジストリの名前を使用します。
 
-To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution).
+{% data variables.product.prodname_dependabot %} が `bundler`、`mix`、および `pip` パッケージマネージャーを使用してプライベートレジストリの依存関係を更新できるようにするため、外部コードの実行を許可できます。 詳しい情報については、[`insecure-external-code-execution`](#insecure-external-code-execution) を参照してください。
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -492,11 +492,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -614,7 +614,7 @@ updates:
 
 #### `vendor`
 
-Use the `vendor` option to tell {% data variables.product.prodname_dependabot %} to vendor dependencies when updating them. Don't use this option if you're using `gomod` as {% data variables.product.prodname_dependabot %} automatically detects vendoring for this tool.
+`vendor` オプションは、依存関係を更新する際に、{% data variables.product.prodname_dependabot %} にベンダリングを指示するために使用します。 `gomod` を使用している場合は、{% data variables.product.prodname_dependabot %} がこのツールに対するベンダリングを自動的に検出するため、このオプションを使用しないでください。
 
 ```yaml
 # Configure version updates for both dependencies defined in manifests and vendored dependencies
@@ -629,12 +629,12 @@ updates:
       interval: "weekly"
 ```
 
-{% data variables.product.prodname_dependabot %} only updates the vendored dependencies located in specific directories in a repository.
+{% data variables.product.prodname_dependabot %} は、リポジトリの特定の場所にあるベンダリングされた依存関係のみを更新します。
 
-| パッケージマネージャー | Required file path for vendored dependencies                                                      | 詳細情報                                                                       |
-| ----------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-| `bundler`   | The dependencies must be in the _vendor/cache_ directory.</br>Other file paths are not supported. | [`bundle cache` documentation](https://bundler.io/man/bundle-cache.1.html) |
-| `gomod`     | No path requirement (dependencies are usually located in the _vendor_ directory)                  | [`go mod vendor` documentation](https://golang.org/ref/mod#go-mod-vendor)  |
+| パッケージマネージャー | ベンダリングされた依存関係のための必須パス                                              | 詳細情報                                                                |
+| ----------- | ------------------------------------------------------------------ | ------------------------------------------------------------------- |
+| `bundler`   | 依存関係は _vendor/cache_ ディレクトリにある必要があります。</br>その他のファイルパスはサポートされていません。 | [`bundle cache` ドキュメント](https://bundler.io/man/bundle-cache.1.html) |
+| `gomod`     | パス要件なし (通常、依存関係は _vendor_ ディレクトリ内に存在)                              | [`go mod vendor` ドキュメント](https://golang.org/ref/mod#go-mod-vendor)  |
 
 
 #### `versioning-strategy`
@@ -650,13 +650,13 @@ updates:
 
 利用可能な更新戦略
 
-| Option                  | サポート                                           | アクション                                                                              |
-| ----------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------- |
-| `lockfile-only`         | `bundler`、`cargo`、`composer`、`mix`、`npm`、`pip` | Only create pull requests to update lockfiles. パッケージマニフェストの変更が必要になる新しいバージョンは無視します。 |
-| `auto`                  | `bundler`、`cargo`、`composer`、`mix`、`npm`、`pip` | 前述のデフォルトの戦略に従います。                                                                  |
-| `widen`                 | `composer`、`npm`                               | 可能であれば、バージョン要件を緩和して、新旧両方のバージョンを含めます。                                               |
-| `increase`              | `bundler`、`composer`、`npm`                     | 新しいバージョンに一致するように、常にバージョン要件を増やします。                                                  |
-| `increase-if-necessary` | `bundler`、`composer`、`npm`                     | 新しいバージョンで必要な場合にのみ、バージョン要件を増やします。                                                   |
+| Option                  | サポート                                           | アクション                                                            |
+| ----------------------- | ---------------------------------------------- | ---------------------------------------------------------------- |
+| `lockfile-only`         | `bundler`、`cargo`、`composer`、`mix`、`npm`、`pip` | ロックファイルを更新するプルリクエストのみを作成します。 パッケージマニフェストの変更が必要になる新しいバージョンは無視します。 |
+| `auto`                  | `bundler`、`cargo`、`composer`、`mix`、`npm`、`pip` | 前述のデフォルトの戦略に従います。                                                |
+| `widen`                 | `composer`、`npm`                               | 可能であれば、バージョン要件を緩和して、新旧両方のバージョンを含めます。                             |
+| `increase`              | `bundler`、`composer`、`npm`                     | 新しいバージョンに一致するように、常にバージョン要件を増やします。                                |
+| `increase-if-necessary` | `bundler`、`composer`、`npm`                     | 新しいバージョンで必要な場合にのみ、バージョン要件を増やします。                                 |
 
 ```yaml
 # Customize the manifest version strategy
@@ -688,17 +688,17 @@ updates:
     versioning-strategy: lockfile-only
 ```
 
-### Configuration options for private registries
+### プライベートレジストリの設定オプション
 
-The top-level `registries` key is optional. It allows you to specify authentication details that {% data variables.product.prodname_dependabot %} can use to access private package registries.
+最上位の `registries` キーはオプションです。 このキーでは、{% data variables.product.prodname_dependabot %} がプライベートパッケージレジストリにアクセスするために使用する認証の詳細を指定できます。
 
 {% note %}
 
-**Note:** Private registries behind firewalls on private networks are not supported.
+**注釈:** プライベートネットワークにあるファイアーウォールの内側のプライベートレジストリはサポートされていません。
 
 {% endnote %}
 
-The value of the `registries` key is an associative array, each element of which consists of a key that identifies a particular registry and a value which is an associative array that specifies the settings required to access that registry. The following *dependabot.yml* file, configures a registry identified as `dockerhub` in the `registries` section of the file and then references this in the `updates` section of the file.
+`registries` キーの値は連想配列で、その各要素は、特定のレジストリを指定するキーと、そのレジストリへのアクセスに必要となる設定を指定する連想配列の値により構成されます。 以下の *dependabot.yml* ファイルでは、ファイルの `registries` セクションで `dockerhub` として指定されたレジストリを設定し、次にファイルの `dockerhub` でそれを参照しています。
 
 {% raw %}
 ```yaml
@@ -715,29 +715,30 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
 {% endraw %}
 
-You use the following options to specify access settings. Registry settings must contain a `type` and a `url`, and typically either a `username` and `password` combination or a `token`.
+以下のオプションを使用して、アクセス設定を指定します。 レジストリ設定には `type` と `url`、そして通常は `username` と `password` の組み合わせか `token` を含める必要があります。
 
-| Option&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 説明                                                                                                                                                                                                                                                                              |
-|:------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `type`                                                                                                 | Identifies the type of registry. See the full list of types below.                                                                                                                                                                                                              |
-| `url`                                                                                                  | The URL to use to access the dependencies in this registry. The protocol is optional. If not specified, `https://` is assumed. {% data variables.product.prodname_dependabot %} adds or ignores trailing slashes as required.                                                   |
-| `ユーザ名`                                                                                                 | The username that {% data variables.product.prodname_dependabot %} uses to access the registry.                                                                                                                                                                                 |
-| `パスワード`                                                                                                | A reference to a {% data variables.product.prodname_dependabot %} secret containing the password for the specified user. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)." |
-| `トークン`                                                                                                 | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access token for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."   |
-| `replaces-base`                                                                                        | For registries with `type: python-index`, if the boolean value is `true`, pip resolves dependencies by using the specified URL rather than the base URL of the Python Package Index (by default `https://pypi.org/simple`).                                                     |
+| オプション           | 説明                                                                                                                                                                                                                                                           |
+|:--------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `type`          | レジストリのタイプを指定します。 タイプの一覧については下記をご覧ください。                                                                                                                                                                                                                       |
+| `url`           | このレジストリの依存関係にアクセスするために使用する URL。 プロトコルはオプションです。 指定しない場合には、`https://` が使用されます。 {% data variables.product.prodname_dependabot %} が必要に応じて末尾のスラッシュを追加または無視します。                                                                                                    |
+| `ユーザ名`          | {% data variables.product.prodname_dependabot %} がレジストリにアクセスするために使用するユーザ名。                                                                                                                                                                                   |
+| `パスワード`         | 指定したユーザのパスワードを含む {% data variables.product.prodname_dependabot %} シークレットへのリファレンス。 詳しい情報については、「[Dependabot に対して暗号化されたシークレットを管理する](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)」を参照してください。                                    |
+| `key`           | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access key for this registry. 詳しい情報については、「[Dependabot に対して暗号化されたシークレットを管理する](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)」を参照してください。 |
+| `トークン`          | このレジストリへのアクセストークンを含む {% data variables.product.prodname_dependabot %} シークレットへのリファレンス。 詳しい情報については、「[Dependabot に対して暗号化されたシークレットを管理する](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)」を参照してください。                                |
+| `replaces-base` | `type: python-index` となっているレジストリで、ブール値が `true` の場合、pip は、Python Package Index のベース URL (デフォルトでは `https://pypi.org/simple`) ではなく指定された URL を使用して依存関係を解決します。                                                                                                    |
 
 
-Each configuration `type` requires you to provide particular settings. Some types allow more than one way to connect. The following sections provide details of the settings you should use for each `type`.
+各設定 `type` には、特定の設定を指定する必要があります。 タイプによっては、複数の接続方法を使用できます。 以下のセクションで、各 `type` に使用する設定の詳細を説明します。
 
 #### `composer-repository`
 
-The `composer-repository` type supports username and password.
+`composer-repository` タイプは、ユーザ名とパスワードをサポートします。
 
 {% raw %}
 ```yaml
@@ -765,6 +766,19 @@ registries:
 ```
 {% endraw %}
 
+The `docker-registry` type can also be used to pull from Amazon ECR using static AWS credentials.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 `git` タイプは、ユーザ名とパスワードをサポートします。
@@ -780,6 +794,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+The `hex-organization` type supports organization and key.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 `maven-repository` タイプは、ユーザ名とパスワード、またはトークンをサポートします。
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
index 7f528872f2..9b3d1597c2 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
@@ -49,7 +49,7 @@ topics:
 
 個別のリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にできます（下記参照）。
 
-ユーザアカウントまたは Organization が所有するすべてのリポジトリの {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にすることもできます。 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)."
+ユーザアカウントまたは Organization が所有するすべてのリポジトリの {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にすることもできます。 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)」または「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。
 
 {% data variables.product.prodname_dependabot_security_updates %} には特定のリポジトリ設定が必要です。 詳しい情報については、「[サポートされているリポジトリについて](#supported-repositories)」を参照してください。
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index 653b96fa7d..6e4de2750e 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
 title: 脆弱性のある依存関係の通知を設定する
 shortTitle: 通知を設定する
-intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} セキュリティ{% endif %}アラートに関する通知の受信方法を最適化します。'
+intro: 'Optimize how you receive notifications about {% data variables.product.prodname_dependabot %} alerts.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
@@ -11,48 +11,41 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
+
 ### 脆弱性のある依存関係の通知について
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} がリポジトリ内にある脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。{% else %}{% data variables.product.product_name %} がリポジトリ内の脆弱性のある依存関係を検出すると、セキュリティアラートを送信します。{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} は、すべてのパブリックリポジトリでデフォルト設定で有効になっています。 {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。
+When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)」を参照してください。
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} の脆弱性のある依存関係に関するセキュリティアラートの有効化](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。 {% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %}
+By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.{% endif %}
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}サイト管理者は、通知なしで {% data variables.product.prodname_dependabot_alerts %} を有効にすることもできます。 詳細については、「[{% data variables.product.prodname_ghe_server %} への脆弱性のある依存関係に対する {% data variables.product.prodname_dependabot_alerts %} の有効化](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}サイト管理者は、通知なしでセキュリティアラートを有効にすることもできます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %}の脆弱性のある依存関係に関するセキュリティアラートの有効化](/enterprise/{{ currentVersion }}/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。 {% endif %}
-
-### {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %} セキュリティアラートの通知を設定する{% endif %}
+### Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
 
 各ページの上部に表示される [Manage notifications] ドロップダウン {% octicon "bell" aria-label="The notifications bell" %} から、自分または Organization の通知設定を構成できます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)」を参照してください。
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} オプション](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
-{% else %}
-  ![セキュリティアラートオプション](/assets/images/help/notifications-v2/security-alerts-options.png)
-{% endif %}
 
 {% note %}
 
-**注釈:** {% data variables.product.company_short %} で通知をフィルタして、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} セキュリティ{% endif %}アラートを表示できます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。
+**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} alerts. 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「通知を[設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}」を参照してください。{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」を参照してください。
 
 ### 脆弱性のある依存関係の通知を減らす方法
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}の通知が多すぎる場合は、毎週のメールダイジェストを選択するか、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を有効にしたまま通知をオフにすることをお勧めします。 その場合でも、リポジトリの [Security] タブで{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を表示できます。{% if currentVersion == "free-pro-team@latest" %}詳細については、「[リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。{% endif %}
+If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. 詳細については、「[リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index 0ab616e776..b80c058ef9 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -14,27 +14,27 @@ topics:
 
 ### 依存関係のバージョン更新について
 
-{% data variables.product.prodname_dependabot_version_updates %} を有効にするには、リポジトリの `.github` ディレクトリにある *dependabot.yml* 構成ファイルをチェックします。 {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. 更新するパッケージマネージャーの依存関係ごとに、パッケージマニフェストファイルの場所と、それらのファイルにリストされている依存関係の更新をチェックする頻度を指定する必要があります。 For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+{% data variables.product.prodname_dependabot_version_updates %} を有効にするには、リポジトリの `.github` ディレクトリにある *dependabot.yml* 構成ファイルをチェックします。 すると、{% data variables.product.prodname_dependabot %} は設定した依存関係を最新の状態に保つためにプルリクエストを発行します。 更新するパッケージマネージャーの依存関係ごとに、パッケージマニフェストファイルの場所と、それらのファイルにリストされている依存関係の更新をチェックする頻度を指定する必要があります。 セキュリティ更新の有効化については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。
 
 {% data reusables.dependabot.initial-updates %} 詳しい情報については、「[依存関係の更新をカスタマイズする](/github/administering-a-repository/customizing-dependency-updates)」をご覧ください。
 
-{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
+{% data reusables.dependabot.private-dependencies-note %} さらに、 {% data variables.product.prodname_dependabot %} はすべてのパッケージマネージャーに対して、プライべートな {% data variables.product.prodname_dotcom %} 依存関係をサポートしません。 For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
 
-### Enabling {% data variables.product.prodname_dependabot_version_updates %}
+### {% data variables.product.prodname_dependabot_version_updates %} を有効化する
 
-{% data reusables.dependabot.create-dependabot-yml %} For information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates)."
-1. Add a `version`.
-1. Optionally, if you have dependencies in a private registry, add a `registries` section containing authentication details.
-1. Add an `updates` section, with an entry for each package manager you want {% data variables.product.prodname_dependabot %} to monitor.
+{% data reusables.dependabot.create-dependabot-yml %}詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates)」を参照してください。
+1. `version` を追加します。
+1. プライベートレジストリに依存関係がある場合、必要に応じて認証情報を含む `registries` セクションを追加します。
+1. `updates` セクションを追加し、{% data variables.product.prodname_dependabot %} に監視させるパッケージマネージャーごとにエントリを追加します。
 1. パッケージマネージャーごとに、以下を使用します。
-    - `package-ecosystem` to specify the package manager.
+    - `package-ecosystem`: パッケージマネージャーを指定します。
     - `directory`: マニフェストまたはその他の定義ファイルの場所を指定します。
     - `schedule.interval`: 新しいバージョンをチェックする頻度を指定します。
 {% data reusables.dependabot.check-in-dependabot-yml %}
 
 #### *dependabot.yml*ファイルの例
 
-The example *dependabot.yml* file below configures version updates for two package managers: npm and Docker. このファイルがチェックインされると、{% data variables.product.prodname_dependabot %} が、デフォルトブランチのマニフェストファイルで古い依存関係がないかをチェックします。 古い依存関係が見つかった場合、デフォルトブランチに対してプルリクエストを発行して依存関係を更新します。
+下記のサンプルの *dependabot.yml* ファイルは、2 つのパッケージマネージャー (npm と Docker) のバージョン更新を設定しています。 このファイルがチェックインされると、{% data variables.product.prodname_dependabot %} が、デフォルトブランチのマニフェストファイルで古い依存関係がないかをチェックします。 古い依存関係が見つかった場合、デフォルトブランチに対してプルリクエストを発行して依存関係を更新します。
 
 ```yaml
 # 2 つのパッケージマネージャーの最低限の設定を含む
@@ -75,7 +75,7 @@ updates:
 
 ### バージョン更新のステータスを確認する
 
-バージョン更新を有効にすると、リポジトリの依存関係グラフに新しい **Dependabot** タブが表示されます。 This tab shows which package managers {% data variables.product.prodname_dependabot %} is configured to monitor and when {% data variables.product.prodname_dependabot %} last checked for new versions.
+バージョン更新を有効にすると、リポジトリの依存関係グラフに新しい **Dependabot** タブが表示されます。 このタブには、{% data variables.product.prodname_dependabot %} が監視するように設定されているパッケージマネージャーと、{% data variables.product.prodname_dependabot %} が最後に新しいバージョンをチェックした日時が表示されます。
 
 ![[Repository Insights] タブ、[Dependency graph]、[Dependabot] タブ](/assets/images/help/dependabot/dependabot-tab-view-beta.png)
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index 9bd0c4278c..0f6e828be5 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -1,5 +1,5 @@
 ---
-title: Exploring the dependencies of a repository
+title: リポジトリの依存関係を調べる
 intro: 'You can use the dependency graph to see the packages your project depends on{% if currentVersion == "free-pro-team@latest" %} and the repositories that depend on it{% endif %}. また、その依存関係で脆弱性が検出されると、それも表示されます。'
 redirect_from:
   - /articles/listing-the-packages-that-a-repository-depends-on
@@ -15,11 +15,13 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### 依存関係グラフの表示
 
 {% data reusables.repositories.enable-security-alerts %}
 
-The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. 依存関係の検出とサポートされているエコシステムについては、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
@@ -50,19 +52,6 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
-
-![依存関係グラフ](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view.
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### 依存ビュー
 
@@ -74,7 +63,7 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 リポジトリ管理者は、プライベートリポジトリに対して依存関係グラフを有効または無効にすることができます。
 
-You can also enable or disable the dependency graph 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)."
+You can also enable or disable the dependency graph for all repositories owned by your user account or organization. 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)」または「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -113,8 +102,8 @@ The "Used by" section represents a single package from the repository. If you ha
 
 ### 参考リンク
 
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)
+- [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository){% if currentVersion == "free-pro-team@latest" %}
 - [Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)
-- [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)
 - [{% data variables.product.product_name %} によるデータの利用方法と保護方法を理解する](/github/understanding-how-github-uses-and-protects-your-data)
 {% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/index.md b/translations/ja-JP/content/code-security/supply-chain-security/index.md
index 89a65d7d7a..bb9dbc7d65 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/index.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md
index 09a07b1b55..d3d4643b8a 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md
@@ -12,7 +12,7 @@ topics:
 
 ### {% data variables.product.prodname_dependabot_version_updates %} のアクションについて
 
-多くの場合、アクションはバグ修正と新機能で更新され、自動プロセスの信頼性、速度、安全性が向上しています。 {% data variables.product.prodname_actions %} に対して {% data variables.product.prodname_dependabot_version_updates %} を有効にすると、{% data variables.product.prodname_dependabot %} は、リポジトリの *workflow.yml* ファイル内のアクションへのリファレンスが最新の状態に保たれるようにします。 {% data variables.product.prodname_dependabot %} は、ファイル内のアクションごとに、アクションのリファレンス（通常、アクションに関連付けられているバージョン番号またはコミット ID）を最新バージョンと照合します。 より新しいバージョンのアクションが使用可能な場合、{% data variables.product.prodname_dependabot %} は、ワークフローファイル内のリファレンスを最新バージョンに更新するプルリクエストを送信します。 {% data variables.product.prodname_dependabot_version_updates %} の詳細については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+多くの場合、アクションはバグ修正と新機能で更新され、自動プロセスの信頼性、速度、安全性が向上しています。 {% data variables.product.prodname_actions %} に対して {% data variables.product.prodname_dependabot_version_updates %} を有効にすると、{% data variables.product.prodname_dependabot %} は、リポジトリの *workflow.yml* ファイル内のアクションへのリファレンスが最新の状態に保たれるようにします。 {% data variables.product.prodname_dependabot %} は、ファイル内のアクションごとに、アクションのリファレンス（通常、アクションに関連付けられているバージョン番号またはコミット ID）を最新バージョンと照合します。 より新しいバージョンのアクションが使用可能な場合、{% data variables.product.prodname_dependabot %} は、ワークフローファイル内のリファレンスを最新バージョンに更新するプルリクエストを送信します。 {% data variables.product.prodname_dependabot_version_updates %} の詳細については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 {% data variables.product.prodname_actions %} のワークフロー設定に関する詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot.md
index 0844d7de4d..41d7e13f26 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot.md
@@ -1,18 +1,18 @@
 ---
-title: Managing encrypted secrets for Dependabot
-intro: 'You can store sensitive information, like passwords and access tokens, as encrypted secrets and then reference these in the {% data variables.product.prodname_dependabot %} configuration file.'
+title: Dependabot に対する暗号化されたシークレットを管理する
+intro: 'パスワードアクセストークンなどの機密情報を、暗号化されたシークレットとして保存し、{% data variables.product.prodname_dependabot %} 設定ファイルで参照することができます。'
 redirect_from:
   - /github/administering-a-repository/managing-encrypted-secrets-for-dependabot
 versions:
   free-pro-team: '*'
 ---
 
-### About encrypted secrets for {% data variables.product.prodname_dependabot %}
+### {% data variables.product.prodname_dependabot %} に対する暗号化されたシークレットについて
 
-{% data variables.product.prodname_dependabot %} secrets are encrypted credentials that you create at either the organization level or the repository level.
-When you add a secret at the organization level, you can specify which repositories can access the secret. You can use secrets to allow {% data variables.product.prodname_dependabot %} to update dependencies located in private package registries. When you add a secret it's encrypted before it reaches {% data variables.product.prodname_dotcom %} and it remains encrypted until it's used by {% data variables.product.prodname_dependabot %} to access a private package registry.
+{% data variables.product.prodname_dependabot %} シークレットとは、Organization レベルまたはリポジトリレベルで作成する、暗号化された資格情報のことです。
+シークレットを Organization レベルで追加した場合、そのシークレットにどのリポジトリがアクセスできるかを指定できます。 シークレットを使用して、プライベートパッケージレジストリにある依存関係を {% data variables.product.prodname_dependabot %} が更新できるようにすることができます。 シークレットを追加すると、それが {% data variables.product.prodname_dotcom %} に届く前に暗号化され、それを {% data variables.product.prodname_dependabot %} がプライベートパッケージレジストリにアクセスするために使用するまで暗号化されたままとなります。
 
-After you add a {% data variables.product.prodname_dependabot %} secret, you can reference it in the _dependabot.yml_ configuration file like this: {% raw %}`${{secrets.NAME}}`{% endraw %}, where "NAME" is the name you chose for the secret. 例:
+{% data variables.product.prodname_dependabot %} シークレットを追加後は、_dependabot.yml_ 設定ファイルで {% raw %}`${{secrets.NAME}}`{% endraw %} のように参照できます。「NAME」は、シークレットに付けた名前としてください。 例:
 
 {% raw %}
 ```yaml
@@ -24,12 +24,12 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
 
 #### シークレットに名前を付ける
 
-The name of a {% data variables.product.prodname_dependabot %} secret:
-* Can only contain alphanumeric characters (`[A-Z]`, `[0-9]`) or underscores (`_`). スペースは使用できません。 If you enter lowercase letters these are changed to uppercase.
-* Must not start with the `GITHUB_` prefix.
-* Must not start with a number.
+{% data variables.product.prodname_dependabot %} シークレットの名前には、以下の制限があります。
+* 英数字 (`[A-Z]`, `[0-9]`)、(`_`) のみ含めることができます。 スペースは使用できません。 小文字を入力すると、大文字に変換されます。
+* 名前の最初を `GITHUB_` プレフィックスにすることはできません。
+* 最初を数字にすることはできません。
 
-### Adding a repository secret for {% data variables.product.prodname_dependabot %}
+### {% data variables.product.prodname_dependabot %} にリポジトリシークレットを追加する
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
@@ -42,11 +42,11 @@ The name of a {% data variables.product.prodname_dependabot %} secret:
 1. シークレットの値を入力します。
 1. [**Add secret（シークレットの追加）**] をクリックします。
 
-   The name of the secret is listed on the Dependabot secrets page. You can click **Update** to change the secret value. You can click **Remove** to delete the secret.
+   シークレットの名前が、Dependabot シークレットのページに一覧表示されます。 [**Update**] をクリックすると、シークレットの値を変更できます。 [**Remove**] をクリックすると、シークレットを削除できます。
 
-   ![Update or remove a repository secret](/assets/images/help/dependabot/update-remove-repo-secret.png)
+   ![リポジトリシークレットの更新または削除](/assets/images/help/dependabot/update-remove-repo-secret.png)
 
-### Adding an organization secret for {% data variables.product.prodname_dependabot %}
+### {% data variables.product.prodname_dependabot %} に Organization シークレットを追加する
 
 Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
 
@@ -60,14 +60,14 @@ Organizationでシークレットを作成する場合、ポリシーを使用
 1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
 1. シークレットの **Value（値）** を入力します。
 1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。
-1. If you chose **Selected repositories**:
+1. [**Selected repositories**] を選択した場合、以下の手順に従います。
 
    * {% octicon "gear" aria-label="The Gear icon" %} をクリックします。
-   * Choose the repositories that can access this secret. ![Select repositories for this secret](/assets/images/help/dependabot/secret-repository-access.png)
-   * Click **Update selection**.
+   * このシークレットにアクセスできるリポジトリを選択します。 ![シークレットに対するリポジトリの選択](/assets/images/help/dependabot/secret-repository-access.png)
+   * [**Update selection**] をクリックします。
 
 1. [**Add secret（シークレットの追加）**] をクリックします。
 
-   The name of the secret is listed on the Dependabot secrets page. You can click **Update** to change the secret value or its access policy. You can click **Remove** to delete the secret.
+   シークレットの名前が、Dependabot シークレットのページに一覧表示されます。 [**Update**] をクリックすると、シークレットの値やアクセスポリシーを変更できます。 [**Remove**] をクリックすると、シークレットを削除できます。
 
-   ![Update or remove an organization secret](/assets/images/help/dependabot/update-remove-repo-secret.png)
+   ![Organization シークレットの更新または削除](/assets/images/help/dependabot/update-remove-repo-secret.png)
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md
index 0df9c125dd..eef95fc415 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md
@@ -13,7 +13,7 @@ topics:
 
 {% data reusables.dependabot.pull-request-introduction %}
 
-{% data variables.product.prodname_dependabot %} がプルリクエストを発行すると、リポジトリに対して選択した方法で通知されます。 Each pull request contains detailed information about the proposed change, taken from the package manager. これらのプルリクエストは、リポジトリで定義されている通常のチェックとテストに従います。 また、十分な情報がある場合は、互換性スコアが表示されます。 これは、変更をマージするかどうかを決める際にも役立ちます。 For information about this score, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% data variables.product.prodname_dependabot %} がプルリクエストを発行すると、リポジトリに対して選択した方法で通知されます。 各プルリクエストには、パッケージマネージャーから取得した、提案された変更に関する詳細情報が含まれています。 これらのプルリクエストは、リポジトリで定義されている通常のチェックとテストに従います。 また、十分な情報がある場合は、互換性スコアが表示されます。 これは、変更をマージするかどうかを決める際にも役立ちます。 このスコアについての詳しい情報は、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。
 
 管理する依存関係が多数ある場合は、各パッケージマネージャーの設定をカスタマイズして、プルリクエストに特定のレビュー担当者、アサインされた人、ラベルを付けることができます。 詳しい情報については、「[依存関係の更新をカスタマイズする](/github/administering-a-repository/customizing-dependency-updates)」をご覧ください。
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md
index 6d5dd3c247..2ffbf96c25 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md
@@ -1,6 +1,6 @@
 ---
 title: Dependabot エラーのトラブルシューティング
-intro: 'Sometimes {% data variables.product.prodname_dependabot %} is unable to raise a pull request to update your dependencies. エラーをレビューして {% data variables.product.prodname_dependabot %} をブロック解除できます。'
+intro: '{% data variables.product.prodname_dependabot %} は、依存関係を更新するためのプルリクエストを生成できない場合があります。 エラーをレビューして {% data variables.product.prodname_dependabot %} をブロック解除できます。'
 shortTitle: エラーのトラブルシューティング
 redirect_from:
   - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors
@@ -11,90 +11,90 @@ topics:
   - Security
 ---
 
-### About {% data variables.product.prodname_dependabot %} errors
+### {% data variables.product.prodname_dependabot %} エラーについて
 
 {% data reusables.dependabot.pull-request-introduction %}
 
 何らかが {% data variables.product.prodname_dependabot %} によるプルリクエストの発行を妨げる場合、エラーとして報告されます。
 
-### Investigating errors with {% data variables.product.prodname_dependabot_security_updates %}
+### {% data variables.product.prodname_dependabot_security_updates %} でエラーを調査する
 
-{% data variables.product.prodname_dependabot %} が {% data variables.product.prodname_dependabot %} アラートを修正するためのプルリクエストの作成をブロックされると、アラートにエラーメッセージを投稿します。 {% data variables.product.prodname_dependabot_alerts %} ビューには、未解決のアラートのリストが表示されます。 アラートビューにアクセスするには、リポジトリの [**Security**] タブで [**{% data variables.product.prodname_dependabot_alerts %}**] をクリックします。 Where a pull request that will fix the vulnerable dependency has been generated, the alert includes a link to that pull request.
+{% data variables.product.prodname_dependabot %} が {% data variables.product.prodname_dependabot %} アラートを修正するためのプルリクエストの作成をブロックされると、アラートにエラーメッセージを投稿します。 {% data variables.product.prodname_dependabot_alerts %} ビューには、未解決のアラートのリストが表示されます。 アラートビューにアクセスするには、リポジトリの [**Security**] タブで [**{% data variables.product.prodname_dependabot_alerts %}**] をクリックします。 脆弱性のある依存関係を修正するプルリクエストが生成された場合、アラートにはそのプルリクエストへのリンクが含まれます。
 
-![{% data variables.product.prodname_dependabot_alerts %} view showing a pull request link](/assets/images/help/dependabot/dependabot-alert-pr-link.png)
+![プルリクエストリンクを示す {% data variables.product.prodname_dependabot_alerts %} ビュー](/assets/images/help/dependabot/dependabot-alert-pr-link.png)
 
-There are three reasons why an alert may have no pull request link:
+アラートにプルリクエストリンクがない理由は 3 つあります。
 
-1. {% data variables.product.prodname_dependabot_security_updates %} are not enabled for the repository.
-1. The alert is for an indirect or transitive dependency that is not explicitly defined in a lock file.
+1. {% data variables.product.prodname_dependabot_security_updates %} がリポジトリに対して有効になっていない。
+1. アラートが、ロックファイルで明示的に定義されていない間接的または推移的な依存関係に対するものである。
 1. エラーにより {% data variables.product.prodname_dependabot %} のプルリクエストの作成がブロックされました。
 
 エラーによって {% data variables.product.prodname_dependabot %} によるプルリクエストの作成がブロックされた場合は、アラートをクリックしてエラーの詳細を表示できます。
 
-![{% 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)
+![プルリクエストの作成をブロックしたエラーを示す {% data variables.product.prodname_dependabot %} アラート](/assets/images/help/dependabot/dependabot-security-update-error.png)
 
-### Investigating errors with {% data variables.product.prodname_dependabot_version_updates %}
+### {% data variables.product.prodname_dependabot_version_updates %} でエラーを調査する
 
 {% data variables.product.prodname_dependabot %} がエコシステムの依存関係を更新するためのプルリクエストの作成をブロックされると、マニフェストファイルにエラーアイコンを投稿します。 {% data variables.product.prodname_dependabot %} によって管理されるマニフェストファイルは、[{% data variables.product.prodname_dependabot %}] タブに一覧表示されます。 このタブにアクセスするには、リポジトリの [**Insights**] タブで [**Dependency graph**] をクリックし、[**{% data variables.product.prodname_dependabot %}**] タブをクリックします。
 
-![{% data variables.product.prodname_dependabot %} view showing an error](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png)
+![エラーを示す {% data variables.product.prodname_dependabot %} ビュー](/assets/images/help/dependabot/dependabot-tab-view-error-beta.png)
 
-To see the log file for any manifest file, click the **Last checked TIME ago** link. When you display the log file for a manifest that's shown with an error symbol (for example, Maven in the screenshot above), any errors are also displayed.
+マニフェストファイルのログファイルを表示するには、[**Last checked TIME ago**] リンクをクリックします。 エラー記号（上のスクリーンショットの Maven など）で示されているマニフェストのログファイルを表示すると、エラーも表示されます。
 
-![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png)
+![{% data variables.product.prodname_dependabot %} バージョン更新エラーとログ ](/assets/images/help/dependabot/dependabot-version-update-error-beta.png)
 
 ### {% data variables.product.prodname_dependabot %} エラーを理解する
 
-Pull requests for security updates act to upgrade a vulnerable dependency to the minimum version that includes a fix for the vulnerability. 対照的に、バージョン更新のプルリクエストは、パッケージマニフェストおよび {% data variables.product.prodname_dependabot %} 設定ファイルで許可されている最新バージョンに依存関係をアップグレードするように動作します。 Consequently, some errors are specific to one type of update.
+セキュリティアップデートのプルリクエストは、脆弱性のある依存関係を、脆弱性の修正を含む最小バージョンにアップグレードします。 対照的に、バージョン更新のプルリクエストは、パッケージマニフェストおよび {% data variables.product.prodname_dependabot %} 設定ファイルで許可されている最新バージョンに依存関係をアップグレードするように動作します。 したがって、一部のエラーは 1 つの種類の更新に固有になります。
 
 #### {% data variables.product.prodname_dependabot %} が DEPENDENCY を脆弱でないバージョンに更新できない
 
 **セキュリティアップデートのみ。** {% data variables.product.prodname_dependabot %} は、このリポジトリの依存関係グラフの他の依存関係を壊さずに、脆弱性のある依存関係を安全なバージョンに更新するためのプルリクエストを作成することはできません。
 
-Every application that has dependencies has a dependency graph, that is, a directed acyclic graph of every package version that the application directly or indirectly depends on. Every time a dependency is updated, this graph must resolve otherwise the application won't build. When an ecosystem has a deep and complex dependency graph, for example, npm and RubyGems, it is often impossible to upgrade a single dependency without upgrading the whole ecosystem.
+依存関係を含むすべてのアプリケーションには、依存関係グラフ、つまり、アプリケーションが直接または間接的に依存するすべてのパッケージバージョンの有向非巡回グラフがあります。 依存関係が更新されるたびに、このグラフを解決する必要があります。解決しない場合、アプリケーションがビルドされません。 npm や RubyGems のように、エコシステムに深く複雑な依存関係グラフがある場合、エコシステム全体をアップグレードせずに単一の依存関係をアップグレードすることは不可能な場合があります。
 
-The best way to avoid this problem is to stay up to date with the most recently released versions, for example, by enabling version updates. This increases the likelihood that a vulnerability in one dependency can be resolved by a simple upgrade that doesn't break the dependency graph. 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。
+この問題を回避する最善策としては、たとえばバージョン更新を有効化するなどして、最新のリリースバージョンで最新の状態に保つことです。 これにより、依存関係グラフを壊さない単純なアップグレードで 1 つの依存関係の脆弱性を解決できる可能性が高くなります。 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。
 
-#### {% data variables.product.prodname_dependabot %} cannot update to the required version as there is already an open pull request for the latest version
+#### 最新バージョンのオープンプルリクエストがすでに存在するため、{% data variables.product.prodname_dependabot %} を必要なバージョンに更新できない
 
-**Security updates only.** {% data variables.product.prodname_dependabot %} will not create a pull request to update the vulnerable dependency to a secure version because there is already an open pull request to update this dependency. You will see this error when a vulnerability is detected in a single dependency and there's already an open pull request to update the dependency to the latest version.
+**セキュリティアップデートのみ。** {% data variables.product.prodname_dependabot %} は、このリポジトリの依存関係グラフの他の依存関係を壊さずに、脆弱性のある依存関係を安全なバージョンに更新するためのプルリクエストを作成することはできません。 このエラーは、単一の依存関係で脆弱性が検出され、依存関係を最新バージョンに更新するためのオープンプルリクエストがすでに存在する場合に表示されます。
 
-There are two options: you can review the open pull request and merge it as soon as you are confident that the change is safe, or close that pull request and trigger a new security update pull request. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)."
+オープンプルリクエストを確認して、変更が安全であると確信したらすぐにマージするか、そのプルリクエストをクローズして新しいセキュリティアップデートプルリクエストをトリガーする、という 2 つのオプションがあります。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} のプルリクエストを手動でトリガーする](#triggering-a-dependabot-pull-request-manually)」を参照してください。
 
-#### {% data variables.product.prodname_dependabot %} timed out during its update
+#### {% data variables.product.prodname_dependabot %} が更新中にタイムアウトした
 
-{% data variables.product.prodname_dependabot %} took longer than the maximum time allowed to assess the update required and prepare a pull request. This error is usually seen only for large repositories with many manifest files, for example, npm or yarn monorepo projects with hundreds of *package.json* files. Updates to the Composer ecosystem also take longer to assess and may time out.
+{% data variables.product.prodname_dependabot %} は、必要な更新を評価してプルリクエストを準備するために許可された最大時間よりも長く時間を要しました。 このエラーは通常、多くのマニフェストファイルを含む大規模なリポジトリでのみ発生します。たとえば、数百の *package.json* ファイルを含む npm や yarn monorepo プロジェクトなどです。 Composer エコシステムの更新も評価に時間がかかり、タイムアウトする可能性があります。
 
-This error is difficult to address. If a version update times out, you could specify the most important dependencies to update using the `allow` parameter or, alternatively, use the `ignore` parameter to exclude some dependencies from updates. Updating your configuration might allow {% data variables.product.prodname_dependabot %} to review the version update and generate the pull request in the time available.
+これは対処が難しいエラーです。 バージョン更新がタイムアウトした場合は、`allow` パラメーターを使用して更新する最も重要な依存関係を指定するか、または、`ignore` パラメーターを使用して更新から一部の依存関係を除外できます。 設定を更新すると、{% data variables.product.prodname_dependabot %} がバージョンの更新を確認し、利用可能な時間内にプルリクエストを生成できます。
 
-If a security update times out, you can reduce the chances of this happening by keeping the dependencies updated, for example, by enabling version updates. 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。
+セキュリティアップデートがタイムアウトする場合、たとえばバージョン更新を有効にするなどして依存関係を最新に保つことで、タイムアウトが発生する可能性を減らすことができます。 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。
 
-#### {% data variables.product.prodname_dependabot %} cannot open any more pull requests
+#### {% data variables.product.prodname_dependabot %} で追加のプルリクエストをオープンできない
 
-There's a limit on the number of open pull requests {% data variables.product.prodname_dependabot %} will generate. When this limit is reached, no new pull requests are opened and this error is reported. The best way to resolve this error is to review and merge some of the open pull requests.
+{% data variables.product.prodname_dependabot %} が生成するオープンプルリクエスト数には制限があります。 上限に達すると、新しいプルリクエストはオープンされず、このエラーが報告されます。 エラーを解決する最善策として、複数のオープンプルリクエストを確認してマージします。
 
-There are separate limits for security and version update pull requests, so that open version update pull requests cannot block the creation of a security update pull request. The limit for security update pull requests is 10. By default, the limit for version updates is 5 but you can change this using the `open-pull-requests-limit` parameter in the configuration file. 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit) 」を参照してください。
+セキュリティアップデートとバージョン更新のプルリクエストには個別の制限があるため、オープンなバージョン更新のプルリクエストがセキュリティアップデートのプルリクエストの作成をブロックすることはできません。 セキュリティアップデートのプルリクエストの上限は 10 件です。 デフォルトではバージョン更新の上限は 5 件ですが、設定ファイルの `open-pull-requests-limit` パラメータを使用して変更できます。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit) 」を参照してください。
 
-The best way to resolve this error is to merge or close some of the existing pull requests and trigger a new pull request manually. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)."
+このエラーを解決する最善策として、既存のプルリクエストの一部をマージまたはクローズして、新しいプルリクエストを手動でトリガーします。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} のプルリクエストを手動でトリガーする](#triggering-a-dependabot-pull-request-manually)」を参照してください。
 
-#### {% data variables.product.prodname_dependabot %} can't resolve or access your dependencies
+#### {% data variables.product.prodname_dependabot %} が依存関係を解決またはアクセスできない
 
-If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`.
+{% data variables.product.prodname_dependabot %} がリポジトリで依存関係のリファレンスを更新する必要があるかどうかを確認しようとしたが、1 つ以上のリファレンスファイルにアクセスできない場合、操作は失敗し、「{% data variables.product.prodname_dependabot %} は LANGUAGE 依存関係ファイルを解決できません」というエラーメッセージが表示されます。 API エラータイプは `git_dependencies_not_reachable` です。
 
-Similarly, if {% data variables.product.prodname_dependabot %} can't access a private package registry in which a dependency is located, one of the following errors is generated:
+同様に、{% data variables.product.prodname_dependabot %} が依存関係が存在するプライベートパッケージレジストリにアクセスできない場合、次のエラーのいずれかが生成されます。
 
-*   "Dependabot can't reach a dependency in a private package registry"<br> (API error type: `private_source_not_reachable`)
-*   "Dependabot can't authenticate to a private package registry"<br> (API error type:`private_source_authentication_failure`)
-*   "Dependabot timed out while waiting for a private package registry"<br> (API error type:`private_source_timed_out`)
-*   "Dependabot couldn't validate the certificate for a private package registry"<br> (API error type:`private_source_certificate_failure`)
+*   「Dependabot はプライベートパッケージレジストリの依存関係に到達できません」<br> (API エラータイプ: `private_source_not_reachable`)
+*   「Dependabot はプライベートパッケージレジストリを認証できません」<br> (API エラータイプ: `private_source_authentication_failure`)
+*   「プライベートパッケージレジストリの待機中に Dependabot がタイムアウトしました」<br> (API エラータイプ: `private_source_timed_out`)
+*   「Dependabot はプライベートパッケージレジストリの証明書を検証できませんでした」<br> (API エラータイプ: `private_source_certificate_failure`)
 
-To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations.
+{% data variables.product.prodname_dependabot %} が依存関係のリファレンスを正常に更新できるようにするには、すべての依存関係のリファレンスがアクセス可能な場所でホストされていることを確認してください。
 
-**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
+**バージョンの更新のみ。**{% data reusables.dependabot.private-dependencies-note %}さらに、{% data variables.product.prodname_dependabot %} はすべてのパッケージマネージャーのプライべートな {% data variables.product.prodname_dotcom %} 依存関係をサポートしているわけではありません。 詳しい情報については、「[ Dependabot のバージョン更新について](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)」を参照してください。
 
-### Triggering a {% data variables.product.prodname_dependabot %} pull request manually
+### {% data variables.product.prodname_dependabot %} のプルリクエストを手動でトリガーする
 
-If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request.
+{% data variables.product.prodname_dependabot %} のブロックを解除すると、プルリクエストを作成するための新規の試行を手動でトリガーできます。
 
-- **Security updates**—display the {% data variables.product.prodname_dependabot %} alert that shows the error you have fixed and click **Create {% data variables.product.prodname_dependabot %} security update**.
-- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**.
+- **セキュリティアップデート** — 修正済みのエラーを示す {% data variables.product.prodname_dependabot %} アラートを表示します。[**Create {% data variables.product.prodname_dependabot %} security update**] をクリックします。
+- **バージョン更新** — リポジトリの [**Insights**] タブで、[**Dependency graph**] をクリックし、[**Dependabot**] タブをクリックします。 [**Last checked *TIME* ago**] をクリックして、バージョン更新の最終チェック中に {% data variables.product.prodname_dependabot %} が生成したログファイルを表示します。 [**Check for updates**] をクリックします。
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 2dc668e06c..b0a8270921 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting the detection of vulnerable dependencies
-intro: 'If the dependency information reported by {% data variables.product.product_name %} is not what you expected, there are a number of points to consider, and various things you can check.'
-shortTitle: Troubleshooting detection
+title: 脆弱性のある依存関係の検出のトラブルシューティング
+intro: '{% data variables.product.product_name %} によって報告された依存関係の情報が期待したものと異なる場合、いくつかの考慮するポイントと、様々な確認項目があります。'
+shortTitle: トラブルシューティングの検出
 redirect_from:
   - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies
 versions:
@@ -11,96 +11,98 @@ topics:
   - Security
 ---
 
-The results of dependency detection reported by {% data variables.product.product_name %} may be different from the results returned by other tools. There are good reasons for this and it's helpful to understand how {% data variables.product.prodname_dotcom %} determines dependencies for your project.
+{% data variables.product.product_name %} によって報告された依存関係の検出結果は、他のツールから返される結果とは異なる場合があります。 これには理由があり、{% data variables.product.prodname_dotcom %} がプロジェクトの依存関係をどのように決定するかを理解しておくと便利です。
 
-### Why do some dependencies seem to be missing?
+### 一部の依存関係がないように見えるのはなぜですか？
 
-{% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following:
+{% data variables.product.prodname_dotcom %} は、他のツールとは異なる方法で依存関係データを生成および表示します。 したがって、依存関係を特定するために別のツールを使用している場合は、ほぼ確実に異なる結果が表示されます。 次のことを考慮してください。
 
-*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
-*   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
-*   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
-*   {% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+*   {% data variables.product.prodname_advisory_database %} は、{% data variables.product.prodname_dotcom %} が脆弱性のある依存関係を識別するために使用するデータソースの 1 つです。 これは、{% data variables.product.prodname_dotcom %} の一般的なパッケージエコシステムの脆弱性情報がキュレーションされた無料のデータベースです。 これには、{% data variables.product.prodname_security_advisories %} から {% data variables.product.prodname_dotcom %} に直接報告されたデータと、公式フィードおよびコミュニティソースの両方が含まれます。 このデータは {% data variables.product.prodname_dotcom %} によってレビューおよびキュレーションされ、虚偽または実行不可能な情報が開発コミュニティと共有されないようにします。 {% data reusables.security-advisory.link-browsing-advisory-db %}
+*   依存関係グラフは、ユーザのリポジトリ内のすべての既知のパッケージマニフェストファイルを解析します。 たとえば、npm の場合、_package-lock.json_ ファイルを解析します。 リポジトリのすべての依存関係とパブリック依存関係のグラフを作成します。 これは、依存関係グラフを有効にし、誰かがデフォルトブランチにプッシュしたときに発生します。また、サポートされているマニフェスト形式に変更を加えるコミットが含まれています。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
+*   {% data variables.product.prodname_dependabot %} は、マニフェストファイルを含むデフォルトブランチへのプッシュをスキャンします。 新しい脆弱性レコードが追加されると、既存のすべてのリポジトリがスキャンされ、脆弱性のあるリポジトリごとにアラートが生成されます。 {% data variables.product.prodname_dependabot_alerts %} は、脆弱性ごとに 1 つのアラートを作成するのではなく、リポジトリレベルで集約されます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. 可能な場合、{% data variables.product.prodname_dependabot %} はリポジトリ内でプルリクエストを作成して、脆弱性を回避するために必要な最小限の安全なバージョンに脆弱性のある依存関係をアップグレードします。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」および「[{% data variables.product.prodname_dependabot %} エラーのトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)」を参照してください。
 
-    {% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is discovered and added to the advisory database.
+    {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% if currentVersion ver_gt "enterprise-server@2.22" %} and synchronized to {% data variables.product.prodname_ghe_server %}{% endif %}. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)」を参照してください。
 
-### Why don't I get vulnerability alerts for some ecosystems?
+### 一部のエコシステムの脆弱性アラートが表示されないのはなぜですか？
 
-{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot %} security updates are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+{% data variables.product.prodname_dotcom %} では、脆弱性アラートのサポートを、高品質で実用的なデータを提供できる一連のエコシステムに限定しています。 Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot %} alerts are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. 今後も、より多くのエコシステムのサポートを追加していきます。 サポートされているパッケージエコシステムの概要については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)」を参照してください。
 
-It's worth noting that [{% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems.
+It's worth noting that {% data variables.product.prodname_dotcom %} Security Advisories may exist for other ecosystems. セキュリティアドバイザリの情報は、特定のリポジトリのメンテナによって提供されます。 このデータは、サポートされているエコシステムの情報と同じ方法でキュレーションされていません。 {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}
 
-**Check**: Does the uncaught vulnerability apply to an unsupported ecosystem?
+**チェック**: 未捕捉の脆弱性は、サポートされていないエコシステムに適用されますか？
 
-### Does the dependency graph only find dependencies in manifests and lockfiles?
+### 依存関係グラフは、マニフェストとロックファイルの依存関係のみを検索しますか？
 
-The dependency graph includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
+依存関係グラフには、環境で明示的に宣言されている依存関係に関する情報が含まれています。 つまり、マニフェストまたはロックファイルで指定されている依存関係です。 依存関係グラフには、通常、マニフェストファイル内の依存関係の依存関係を調べることにより、ロックファイルで指定されていない場合でも、推移的な依存関係も含まれます。
 
-{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% data variables.product.prodname_dependabot %} security updates only suggests a change where it can directly "fix" the dependency, that is, when these are:
-* Direct dependencies explicitly declared in a manifest or lockfile
-* Transitive dependencies declared in a lockfile
+{% data variables.product.prodname_dependabot_alerts %} は、推移的な依存関係を含め、更新する必要のある依存関係についてアドバイスします。この場合、バージョンはマニフェストまたはロックファイルから判別できます。 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
+* マニフェストまたはロックファイルで明示的に宣言されている直接依存関係
+* Transitive dependencies declared in a lockfile{% endif %}
 
-The dependency graph doesn't include “loose” dependencies. “Loose” dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile.
+依存関係グラフには、「寛容な」依存関係は含まれていません。 「寛容な」依存関係は、パッケージマネージャーのマニフェストまたはロックファイルで参照されるのではなく、別のソースからコピーされ、リポジトリに直接またはアーカイブ内でチェックインされる個々のファイル（ZIP ファイルや JAR ファイルなど）です。
 
-**Check**: Is the uncaught vulnerability for a component that's not specified in the repository's manifest or lockfile?
+**チェック**: リポジトリのマニフェストまたはロックファイル内で指定されていないコンポーネントに対する未捕捉の脆弱性はありますか？
 
-### Does the dependency graph detect dependencies specified using variables?
+### 依存関係グラフは、変数を使用して指定された依存関係を検出しますか？
 
-The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not be included in the dependency graph.
+依存関係グラフは、マニフェストが {% data variables.product.prodname_dotcom %} にプッシュされるときにマニフェストを分析します。 したがって、依存関係グラフはプロジェクトのビルド環境にアクセスできないため、マニフェスト内で使用される変数を解決できません。 マニフェスト内で変数を使用して名前、またはより一般的には依存関係のバージョンを指定する場合、その依存関係は依存関係グラフに含まれません。
 
-**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version?
+**チェック**: 見つからない依存関係は、名前またはバージョンに変数を使用してマニフェストで宣言されていますか？
 
-### Are there limits which affect the dependency graph data?
+### 依存関係グラフのデータに影響する制限はありますか？
 
-Yes, the dependency graph has two categories of limits:
+はい、依存関係グラフの制限には 2 つのカテゴリがあります。
 
-1. **Processing limits**
+1. **処理制限**
 
-    These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created.
+    これらは {% data variables.product.prodname_dotcom %} 内に表示される依存関係グラフに影響を与え、{% data variables.product.prodname_dependabot_alerts %} が作成されないようにします。
 
-    Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}.
+    サイズが 0.5 MB を超えるマニフェストは、Enterprise アカウントに対してのみ処理されます。 他のアカウントの場合、0.5 MB を超えるマニフェストは無視され、{% data variables.product.prodname_dependabot_alerts %} は作成されません。
 
-    By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not be created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}.
+    デフォルト設定では、{% data variables.product.prodname_dotcom %} はリポジトリごとに 20 個を超えるマニフェストを処理しません。 {% data variables.product.prodname_dependabot_alerts %} は、この制限を超えるマニフェストに対しては作成されません。 制限を増やす必要がある場合は、{% data variables.contact.contact_support %} にお問い合わせください。
 
-2. **Visualization limits**
+2. **表示制限**
 
-    These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created.
+    これらは、{% data variables.product.prodname_dotcom %} 内の依存関係グラフに表示される内容に影響します。 ただし、作成された {% data variables.product.prodname_dependabot_alerts %} には影響しません。
 
-    The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}.
+    リポジトリの依存関係グラフの依存関係ビューには、100 個のマニフェストのみが表示されます。 通常、これは上記の処理制限よりも大幅に高いので十分です。 処理制限が100 個を超える状況でも、{% data variables.product.prodname_dotcom %} 内に表示されていないマニフェストに対して {% data variables.product.prodname_dependabot_alerts %} が作成されます。
 
-**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests?
+**チェック**: 0.5 MB を超えるマニフェストファイル、または多数のマニフェストがあるリポジトリに見つからない依存関係はありませんか？
 
-### Does {% data variables.product.prodname_dependabot %} generate alerts for vulnerabilities that have been known for many years?
+### {% data variables.product.prodname_dependabot %} は、何年も前から知られている脆弱性に対してアラートを生成しますか？
 
-The {% data variables.product.prodname_advisory_database %} was launched in November 2019, and initially back-filled to include vulnerability information for the supported ecosystems, starting from 2017. When adding CVEs to the database, we prioritize curating newer CVEs, and CVEs affecting newer versions of software.
+{% data variables.product.prodname_advisory_database %} は 2019 年 11 月にリリースされ、2017 年からサポートされているエコシステムの脆弱性情報を含めるために当初にバックフィルされました。 データベースに CVE を追加するときは、新しい CVE のキュレーションと、新しいバージョンのソフトウェアに影響を与える CVE を優先します。
 
-Some information on older vulnerabilities is available, especially where these CVEs are particularly widespread, however some old vulnerabilities are not included in the {% data variables.product.prodname_advisory_database %}. If there's a specific old vulnerability that you need to be included in the database, contact {% data variables.contact.contact_support %}.
+古い脆弱性に関するいくつかの情報は、特にこれらの CVE が特に広範囲に及ぶ場合に利用可能ですが、一部の古い脆弱性は {% data variables.product.prodname_advisory_database %} に含まれていません。 データベースに含める必要のある特定の古い脆弱性がある場合は、{% data variables.contact.contact_support %} にお問い合わせください。
 
-**Check**: Does the uncaught vulnerability have a publish date earlier than 2017 in the National Vulnerability Database?
+**チェック**: 未捕捉の脆弱性の公開日は、National Vulnerability Database で 2017 年より前ですか？
 
-### Why does {% data variables.product.prodname_advisory_database %} use a subset of published vulnerability data?
+### {% data variables.product.prodname_advisory_database %} が公開された脆弱性データのサブセットを使用するのはなぜですか？
 
-Some third-party tools use uncurated CVE data that isn't checked or filtered by a human. This means that CVEs with tagging or severity errors, or other quality issues, will cause more frequent, more noisy, and less useful alerts.
+一部のサードパーティツールは、人間によるチェックまたはフィルタが行われていない未キュレートの CVE データを使用しています。 これは、タグ付けや重要度のエラー、またはその他の品質に問題のある CVE により、わずらわしく有用性の低いアラートが頻出するということです。
 
-Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant.
+{% data variables.product.prodname_dependabot %} は {% data variables.product.prodname_advisory_database %} で厳選されたデータを使用するため、アラートの数は少なくなる可能性があります。ただし、受信するアラートは正確で関連性があるものです。
 
-### Does each dependency vulnerability generate a separate alert?
+{% if currentVersion == "free-pro-team@latest" %}
+### 依存関係の脆弱性ごとに個別のアラートが生成されますか？
 
-When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability.
+依存関係に複数の脆弱性がある場合、脆弱性ごとに 1 つのアラートではなく、その依存関係に対して 1 つの集約アラートのみが生成されます。
 
-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.
+{% data variables.product.prodname_dependabot_alerts %} の {% data variables.product.prodname_dotcom %} の数は、アラートの数、つまり脆弱性の数ではなく、脆弱性のある依存関係の合計数を示します。
 
-![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png)
+![{% data variables.product.prodname_dependabot_alerts %} ビュー](/assets/images/help/repository/dependabot-alerts-view.png)
 
-When you click to display the alert details, you can see how many vulnerabilities are included in the alert.
+クリックしてアラートの詳細を表示すると、アラートに含まれている脆弱性の数を確認できます。
 
-![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
+![{% data variables.product.prodname_dependabot %} アラートに対する複数の脆弱性](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
-**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers.
+**チェック**: 表示されている合計に不一致がある場合は、アラート番号と脆弱性番号を比較していないかどうか確認してください。
+{% endif %}
 
 ### 参考リンク
 
 - 「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」
 - [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)
-- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/ja-JP/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..7c186aac17
--- /dev/null
+++ b/translations/ja-JP/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Upgrading from Dependabot.com to GitHub-native Dependabot
+intro: You can upgrade to GitHub-native Dependabot by merging a pull request that will allow your dependencies to continue being updated.
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot before then.
+
+After that date, any open pull requests from Dependabot Preview will remain open, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations.
+
+{% endwarning %}
+
+### About upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Dependabot Preview has been built directly into {% data variables.product.prodname_dotcom %}, so you can use {% data variables.product.prodname_dependabot %} alongside all the other functionality in {% data variables.product.prodname_dotcom %} without having to install and use a separate application. By migrating to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, we can also focus on bringing lots of exciting new features to {% data variables.product.prodname_dependabot %}, including more [ecosystem updates](https://github.com/github/roadmap/issues/150), [improved notifications](https://github.com/github/roadmap/issues/133), and {% data variables.product.prodname_dependabot %} support for [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) and [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Differences between Dependabot Preview and {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+While most of the Dependabot Preview features exist in {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, a few remain unavailable:
+- **Live updates:** We hope to bring these back in the future. For now, you can run {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} daily to catch new packages within one day of release.
+- **PHP environment variable registries:** For now, you can use {% data variables.product.prodname_actions %} to fetch dependencies from these registries.
+- **Auto-merge:** We always recommend verifying your dependencies before merging them; therefore, auto-merge will not be supported for the foreseeable future. For those of you who have vetted your dependencies, or are only using internal dependencies, we recommend adding third-party auto-merge apps, or setting up GitHub Actions to merge.
+
+In {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, you can configure all version updates using the configuration file. This file is similar to the Dependabot Preview configuration file with a few changes and improvements that will be automatically included in your upgrade pull request. For more information about the upgrade pull request, see "[Upgrading to GitHub-native Dependabot](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+To see update logs for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} that were previously on the Dependabot.com dashboard:
+
+  1. Navigate to your repository’s **Insights** page.
+  2. Click **Dependency graph** to the left.
+  3. Click **{% data variables.product.prodname_dependabot %}**.
+
+For more information about version updates with {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, see "[About Dependabot version updates](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+### Upgrading to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} requires you to merge the *Upgrade to GitHub-native Dependabot* pull request in your repository. This pull request includes the updated configuration file needed for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}.
+
+If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
+
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
+
+If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index ee6f780497..721874b4e7 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-リポジトリの {% data variables.product.prodname_dependabot %} アラートタブには、オープンおよびクローズしている {% data variables.product.prodname_dependabot_alerts %}、および対応する {% data variables.product.prodname_dependabot_security_updates %} がすべて一覧表示されます。 ドロップダウンメニューを使用してアラートのリストを並べ替えることができます。また、特定のアラートをクリックしてその詳細を表示することもできます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/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 %}{% if currentVersion == "free-pro-team@latest" %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. ドロップダウンメニューを使用してアラートのリストを並べ替えることができます。また、特定のアラートをクリックしてその詳細を表示することもできます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.prodname_dependabot_alerts %} と依存関係グラフを使用するリポジトリの自動セキュリティ更新を有効にすることができます。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ topics:
 ### リポジトリ内の脆弱性のある依存関係の更新について
 
 コードベースが既知の脆弱性のある依存関係を使用していることを検出すると、{% 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 %} はそれを修正するためのプルリクエストを作成します。 Pull Requestは、脆弱性を回避するために必要最低限の安全なバージョンに依存関係をアップグレードします。
+{% endif %}
 
 ### 脆弱性のある依存関係を表示して更新する
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ topics:
 1. 依存関係を更新して脆弱性を解決する準備ができたら、プルリクエストをマージしてください。 {% data variables.product.prodname_dependabot %} によって発行される各プルリクエストには、{% data variables.product.prodname_dependabot %} の制御に使用できるコマンドの情報が含まれています。 詳しい情報については、「[依存関係の更新に関するプルリクエストを管理する](/github/administering-a-repository/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 currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. 表示したいアラートをクリックします。 ![アラートリストで選択されたアラート](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency.
+1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, click the **Dismiss** drop-down, and select a reason for dismissing the alert. ![[Dismiss] ドロップダウンでアラートを却下する理由を選択する](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. Click the version number of the vulnerable dependency to display detailed information. ![Detailed information on the vulnerable dependency](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert.
+1. The banner at the top of the **Dependencies** tab is displayed until all the vulnerable dependencies are resolved or you dismiss it. Click **Dismiss** in the top right corner of the banner and select a reason for dismissing the alert. ![Dismiss security banner](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### 参考リンク
 
-- 「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」
-- 「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」
-- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- 「[脆弱性のある依存関係の検出のトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)」
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
+- 「[リポジトリのセキュリティおよび分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ja-JP/content/codespaces/about-codespaces.md b/translations/ja-JP/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..9ee90ea65c
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: codespace について
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### {% data variables.product.prodname_codespaces %} について
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![codespace（オープン）](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)」を参照してください。
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. 開発者は、タブレットや Chromebook など、あらゆるマシンでどこからでも貢献でき、知的財産のローカルコピーを保持する必要はありません。 Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### {% data variables.product.prodname_codespaces %}の支払いについて
+
+{% data reusables.codespaces.about-billing-for-codespaces %} 詳細は「[{% data variables.product.prodname_codespaces %} の支払いについて](/github/developing-online-with-codespaces/about-billing-for-codespaces)」を参照してください。
+
+### ベータに参加する
+
+限られたユーザのみがベータ参加のために招待されます。 待ちリストに参加するには、「[Codespaces ベータのサインアップ](https://github.com/features/codespaces/signup)」を参照してください。
+
+### {% data variables.product.prodname_codespaces %} について問い合わせる
+
+{% data variables.product.prodname_codespaces %} の使用時に問題が発生した場合は、「[codespace のトラブルシューティング](/github/developing-online-with-codespaces/troubleshooting-your-codespace)」を参照してください。
+
+さらにサポートをご希望の場合、または {% data variables.product.prodname_codespaces %} に関するフィードバックがある場合は、[Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) ディスカッションをご利用ください。
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..db47ed9a9c
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: Codespaces の支払いについて
+intro: '{% data variables.product.prodname_codespaces %} が一般提供されると、ストレージとコンピューティングの使用量に対して課金されます。'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..75be9e6f73
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Allowing your codespace to access a private image registry
+intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry.
+
+When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)."
+
+For example, if you had a private image registry in Azure, you could create the following secrets:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/index.md b/translations/ja-JP/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..12a70939e8
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: リファレンス
+intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..d3c63a0817
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: codespace のトラブルシューティング
+intro: Use this guide to help you troubleshoot common issues with your codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Known Limitations
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### {% data variables.product.prodname_vscode %} troubleshooting
+
+Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.
+
+
+### Configuration troubleshooting
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+This codespace is currently running in recovery mode due to a container error.
+```
+
+Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)」を参照してください。
+
+### dotfiles troubleshooting
+
+- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles.
+- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned.
+  - If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
+  - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
+- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**.
+
+
+### Browser troubleshooting
+
+Chromium ベースではないブラウザを使用しているときに問題が発生した場合は、Chromium ベースのブラウザに切り替えるか、または、[`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) や [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari) などのブラウザのラベルが付いた問題を検索して、`microsoft/vscode` リポジトリでブラウザの既知の問題を確認します。
+
+Chromium ベースのブラウザの使用中に問題が発生した場合は、[`microsoft/vscode`](https://github.com/microsoft/vscode/issues) リポジトリの {% data variables.product.prodname_vscode %} で別の既知の問題が発生しているかどうかを確認できます。
+
+### Container storage troubleshooting
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.
+
+- Remove packages that are no longer by using `sudo apt autoremove`
+- Clean the apt cache by using `sudo apt clean`
+- Delete unneeded files like build artifacts and logs (these are very project-dependent)
+- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10`
+
+More destructive options:
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes)
+- Remove untracked files from working tree: `git clean -i`
+
+### 弊社にお問い合わせください
+
+さらなるサポートが必要な場合は、お問い合わせください。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)」を参照してください。
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..6b755d6c3a
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: codespace を作成する
+intro: リポジトリのブランチの codespace を作成して、オンラインで開発できます。
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### codespace の作成について
+
+You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)."
+
+
+When you create a codespace, a number of steps happen to enable full access to your development environment.
+
+- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
+- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
+- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)」を参照してください。
+- Your Docker container, `docker-compose`, or other initialization is run.
+- At this point, the codespace is marked as available and you can connect.
+- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up.
+  - The codespace shares ports added in the `devcontainer.json` file.
+  - The codespace runs anything specified in `postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Finally, the codespace does a full clone of the repo so you have full access to it.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### codespace を作成する
+
+{% data reusables.repositories.navigate-to-repo %}
+2. リポジトリ名の下で、[Branch] ドロップダウンメニューを使用して、codespace を作成するブランチを選択します。
+
+  ![[Branch] ドロップダウンメニュー](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. リポジトリ名の下で、{% octicon "download" aria-label="The download icon" %} [**Code**] ドロップダウンメニューを使用して、[**Open with Codespaces**] を選択します。
+
+  ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..e0d10bc664
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: codespace を削除する
+intro: 不要になった codespace を削除することができます。
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+
+2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** ![削除ボタン](/assets/images/help/codespaces/delete-codespace.png)
+
+### {% data variables.product.prodname_vscode %} で Codespaces を削除する
+
+For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)."
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..578df95279
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: codespace で開発する
+intro: '{% data variables.product.product_name %} で codespace を開き、{% data variables.product.prodname_vscode %} の機能を使用して開発できます。'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About development with {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Side Bar - By default, this area shows your project files in the Explorer.
+2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
+3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
+4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
+5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
+
+For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} 詳しい情報については、「[codespace のトラブルシューティング](/github/developing-online-with-codespaces/troubleshooting-your-codespace)」を参照してください。
+
+#### Personalizing your codespace
+
+{% data reusables.codespaces.about-personalization %} 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)」を参照してください。
+
+{% data reusables.codespaces.apply-devcontainer-changes %}詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)」を参照してください。
+
+#### Running your app from a codespace
+{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)."
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Navigating to an existing codespace
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. 開発する codespace の名前をクリックします。 ![codespace の名前](/assets/images/help/codespaces/click-name-codespace.png)
+
+Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..31d6915005
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Forwarding ports in your codespace
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About forwarded ports
+
+ポート転送を使用すると、Codespaces 内で実行されている TCP ポートにアクセスできます。 For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application.
+
+When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. たとえば、アプリケーションが `http://127.0.0.1:4000` または `http://localhost:4000` をコンソールに出力する場合、ログは出力をポート 4000 のクリック可能な URL に自動的に変換します。
+
+![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration.
+
+### Forwarding a port
+
+You can manually forward a port that wasn't forwarded automatically.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png)
+1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
+
+### Labeling a port
+
+You can label a port to make the port more easily identifiable in a list.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### Sharing a port
+
+If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png)
+1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Send the copied URL to the person you want to share the port with.
+
+### Adding a port to the codespace configuration
+
+You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)」を参照してください。
+
+You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..0be9933897
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: codespace で開発する
+intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..ba5c1d5918
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: Visual Studio Code で Codespaces を使用する
+intro: '{% data variables.product.product_name %} のアカウントに {% data variables.product.prodname_github_codespaces %} 機能拡張を接続することにより、{% data variables.product.prodname_vscode %} で codespace を直接開発できます。'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 必要な環境
+
+{% data variables.product.prodname_vscode %} の Codespaces で直接開発するには、{% data variables.product.prodname_github_codespaces %} 機能拡張にサインインする必要があります。 {% data variables.product.prodname_github_codespaces %} 機能拡張には、{% data variables.product.prodname_vscode %} October 2020 Release 1.51 以降が必要です。
+
+{% data variables.product.prodname_vs %} Marketplace を使用して、[{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 機能拡張をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode %} ドキュメントの「[Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)」を参照してください。
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. [**Sign in to view {% data variables.product.prodname_dotcom %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。
+4. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. [REMOTE EXPLORER] ドロップダウンを使用して、[**{% data variables.product.prodname_github_codespaces %}**] をクリックします。 ![{% data variables.product.prodname_codespaces %} ヘッダ](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. [**Sign in to view {% data variables.product.prodname_codespaces %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。
+5. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。
+
+{% endwindows %}
+
+### {% data variables.product.prodname_vscode %} で Codespaces を作成する
+
+{% data variables.product.product_name %} アカウントを {% data variables.product.prodname_github_codespaces %} 機能拡張に接続した後、{% data variables.product.product_name %} または {% data variables.product.prodname_vscode %} で作成した Codespaces で開発できます。
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. [Add] アイコンをクリックしてから、[**Create New Codespace**] をクリックします。 ![{% data variables.product.prodname_codespaces %} の [Create New Codespace] オプション](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. 入力し、開発するリポジトリの名前をクリックします。 ![新しい {% data variables.product.prodname_codespaces %} を作成するためのリポジトリを検索する](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. 開発するブランチをクリックします。 ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Click the machine type you want to develop in. ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png)
+### {% data variables.product.prodname_vscode %} で codespace を開く
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. [Codespaces] で、開発するコードスペースをクリックします。
+3. [Connect to Codespace] アイコンをクリックします。 ![{% data variables.product.prodname_vscode %} の [Connect to Codespace] アイコン](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### Changing the machine type in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+You can change the machine type of your codespace at any time.
+
+1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`).
+2. Search for and select "Codespaces: Change Machine Type." ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. Click the codespace that you want to change. ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. Choose the machine type you want to use. ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts.
+
+### {% data variables.product.prodname_vscode %} で Codespaces を削除する
+
+1. [Codespaces] で、削除するコードスペースを右クリックします。
+2. ドロップダウンメニューで、[**Delete Codespace**] をクリックします。 ![{% data variables.product.prodname_dotcom %} で Codespaces を削除する](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..b6603ff12a
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About source control in {% data variables.product.prodname_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+### Creating or switching branches
+
+1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**.
+1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace.
+
+{% endtip %}
+
+### Pulling changes from the remote repository
+
+You can pull changes from the remote repository into your codespace at any time.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. In the drop-down menu, click **Pull**.
+
+If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+### Setting your codespace to automatically fetch new changes
+
+You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
+
+If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
+
+1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. ** Create（作成）**をクリックしてください。
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..05f3bb6766
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Getting started with your C# (.NET) project in Codespaces
+shortTitle: Getting started with your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### はじめに
+
+This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 必要な環境
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 次のステップ
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..4daa52e258
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Getting started with your Java project in Codespaces
+shortTitle: Getting started with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### はじめに
+
+This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 必要な環境
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 次のステップ
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..2ef0866b92
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Getting started with your Node.js project in Codespaces
+shortTitle: Getting started with your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### はじめに
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 必要な環境
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 次のステップ
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..76e42cb726
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Getting started with your Python project in Codespaces
+shortTitle: Getting started with your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### はじめに
+
+This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 必要な環境
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 次のステップ
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..013f96d508
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: Getting Started with {% data variables.product.prodname_codespaces %}
+intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/ja-JP/content/codespaces/guides.md b/translations/ja-JP/content/codespaces/guides.md
new file mode 100644
index 0000000000..8a154aebe1
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: ガイド
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/ja-JP/content/codespaces/index.md b/translations/ja-JP/content/codespaces/index.md
new file mode 100644
index 0000000000..428d92acb6
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc'
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..1034377b45
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing Codespaces for your organization
+intro: 'You can manange and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..4e31f7fa17
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Managing access and security for your organization's codespaces
+shortTitle: Managing access and security for your organization
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Organization owners can manage which repositories a codespace can access.
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. 信頼するリポジトリに対してのみ、アクセスとセキュリティを有効にしてください。
+
+To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. [Access and security] で、あなたの Organization の設定を選択します。 ![信頼するリポジトリを管理するラジオボタン](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、あなたの Organization が所有するその他のリポジトリにアクセスを許可する、リポジトリのコードスペースをクリックします。 その他のリポジトリにコードスペースによるアクセスを許可したい、すべてのリポジトリについて同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
new file mode 100644
index 0000000000..aac26610da
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Managing encrypted secrets for your repository and organization for Codespaces
+shortTitle: Managing secrets for your repository and organization
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### シークレットの制限
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+シークレットの容量は最大64 KBです。
+
+### Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. At the top of the page, click **New repository secret**.
+1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+1. シークレットの値を入力します。
+1. [**Add secret（シークレットの追加）**] をクリックします。
+
+### Adding secrets for an organization
+
+Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. At the top of the page, click **New organization secret**.
+1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+1. シークレットの **Value（値）** を入力します。
+1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+1. [**Add secret（シークレットの追加）**] をクリックします。
+
+### Organizationレベルのシークレットへのアクセスの確認
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. シークレットのリストには、設定済みのアクセス許可とポリシーが含まれます。 例: ![シークレットリスト](/assets/images/help/settings/actions-org-secrets-list.png)
+1. 各シークレットに設定されているアクセス許可の詳細については、[**Update（更新）**] をクリックしてください。
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..fee663a78c
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..c438a70311
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing your organization's audit logs for Codespaces
+shortTitle: Reviewing your organization's audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)."
diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..8717f53157
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. 信頼するリポジトリに対してのみ、アクセスとセキュリティを有効にしてください。
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. [Access and security] で、あなたのユーザアカウントの設定を選択します。 ![信頼するリポジトリを管理するラジオボタン](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、あなたの所有するその他のリポジトリにアクセスを許可する、リポジトリのコードスペースをクリックします。 所有するその他のリポジトリにコードスペースによるアクセスを許可したい、すべてのリポジトリについて同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..0cbfa2b388
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 環境変数を介してコードスペースにアクセスする、トークンなどの機密情報を保存できます。
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### {% data variables.product.prodname_codespaces %} の暗号化されたシークレットについて
+
+コードスペースで使用するユーザアカウントに、暗号化されたシークレットを追加できます。 たとえば、次のような機密情報を暗号化されたシークレットとして保存しアクセスするとよいでしょう。
+
+- クラウドサービスへの個人アクセストークン
+- サービスプリンシパル
+- プラン識別子
+- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+各シークレットにアクセスできるリポジトリを選択できます。 そして、シークレットへのアクセス権があるリポジトリ用に作成した任意のコードスペースでそのシークレットを使用できます。
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### シークレットの制限
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+シークレットの容量は最大64 KBです。
+
+### シークレットを追加する
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. [Codespaces secrets] の右にある [**New secret**] をクリックします。 ![[New secret] ボタン](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. [Name] で、シークレットの名前を入力します。 ![[Name] テキストボックス](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. [**Add secret（シークレットの追加）**] をクリックします。
+
+### シークレットを編集する
+
+既存のシークレットの値を更新したり、シークレットがアクセスできるリポジトリを変更したりすることができます。
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. [Codespaces secrets] で、編集するシークレットの右にある [**Update**] をクリックします。 ![[Update] ボタン](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. [Value] にある [**enter a new value**] をクリックします。 ![[enter a new value] リンク](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. リポジトリへのシークレットのアクセス権を削除する場合は、リポジトリを選択解除します。 ![リポジトリへのアクセス権を削除するチェックボックス](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. [**Save changes**] をクリックします。
+
+### シークレットを削除する
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. [Codespaces secrets] で、削除するシークレットの右にある [**Delete**] をクリックします。 ![[Delete] ボタン](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. 警告を読んで、**OK**をクリックしてください。 ![シークレットの削除の確認](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..6702951351
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: Codespaces の GPG 検証を管理する
+intro: '変更が信頼できるソースからのものであることを他の人々が確信できるよう、コードスペースで作成したコミットに GPG を自動的に使用して署名するよう {% data variables.product.company_short %} に許可できます。'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+GPG 検証を有効にすると、{% data variables.product.company_short %} は {% data variables.product.prodname_codespaces %} であなたが作成したコミットに自動的に署名し、そのコミットは {% data variables.product.product_name %} で検証済みのステータスとなります。 デフォルトでは、GPG 検証は作成されたコードスペースに対して無効になっています。 GPG 検証を、すべてのリポジトリに対して許可するか特定のリポジトリに対して許可するか選択できます。 GPG 検証は、信頼するリポジトリに対してのみ有効にしてください。 {% data variables.product.product_name %} が署名したコミットに関する詳しい情報については、「[コミット署名の検証について](/github/authenticating-to-github/about-commit-signature-verification)」を参照してください。
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. [GPG verification] で、GPG 検証の設定を選択します。 ![GPG 検証を管理するラジオボタン](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、GPG 検証を有効にするリポジトリをクリックします。 GPG 検証を有効にするすべてのリポジトリについて、同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..f7e213e258
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)."
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
diff --git a/translations/ja-JP/content/codespaces/quickstart.md b/translations/ja-JP/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..825bb68b93
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### はじめに
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. リポジトリ名の下で、{% octicon "download" aria-label="The download icon" %} [**Code**] ドロップダウンメニューを使用して、[**Open with Codespaces**] を選択します。
+
+  ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..57b5f640ad
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,142 @@
+---
+title: プロジェクトの Codespace の設定
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### Dockerfile
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+リポジトリで設定を定義しない場合、{% data variables.product.prodname_dotcom %} はベースの Linux イメージを使用して Codespaces を作成します。 The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Follow the prompts to customize your definition.
+1. [**OK**] をクリックします。 ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### カスタム codespace 設定を作成する
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+2 つの場所で {% data variables.product.prodname_vscode %} のデフォルトのエディタ設定を定義できます。
+
+* `.vscode/settings.json` で定義されたエディタ設定は、_Workspace_ スコープの設定として codespace に適用されます。
+* `devcontainer.json` の`設定`キーで定義されたエディタ設定は、codespace の _リモート [Codespaces]_ スコープ設定として適用されます。
+
+After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)."
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### Applying changes to your configuration
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}
+!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - To diagnose the error by reviewing the creation logs, click **View creation log**.
+   - To fix the errors identified in the logs, update your `devcontainer.json` file.
+   - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md b/translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..cd28fdd4ba
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: アカウントの Codespaces をパーソナライズする
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+プロジェクトのメンテナは、ユーザが作成したリポジトリのすべての codespace に適用されるデフォルト設定を定義することもできます。 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)」を参照してください。
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+ドットファイルは、`.` で始まる Unix ライクなシステム上のファイルとフォルダであり、システム上のアプリケーションとシェルの設定を制御します。 ドットファイルは、{% data variables.product.prodname_dotcom %} のリポジトリに保存して管理できます。 `dotfiles` リポジトリに含める内容に関するアドバイスとチュートリアルについては、「[GitHub does dotfiles](https://dotfiles.github.io/)」をご覧ください。
+
+{% data variables.product.prodname_dotcom %} のユーザアカウントが `dotfiles` というパブリックリポジトリを所有している場合、{% data variables.product.prodname_dotcom %} は自動的にこのリポジトリを使用して、codespace 環境をパーソナライズします。 プライベート `dotfiles` リポジトリは現在サポートされていません。
+
+`dotfiles` リポジトリには、シェルのエイリアスと設定、インストールするツール、またはその他の codespace パーソナライゼーションを含めることができます。
+
+新しいコードスペースを作成すると、{% data variables.product.prodname_dotcom %} は `dotfiles` リポジトリを codespace 環境にクローンし、次のいずれかのファイルを探して環境をセットアップします。
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+これらのファイルがいずれも見つからない場合、`.` で始まる `dotfiles` 内のファイルまたはフォルダは、codespace の `~` または `$HOME` ディレクトリにシンボリックリンクされます。
+
+`dotfiles` リポジトリへの変更は、新しい codespace ごとにのみ適用され、既存の codespace には影響しません。
+
+{% note %}
+
+**注釈:** 現在、{% data variables.product.prodname_codespaces %} は、`dotfiles` リポジトリを使用した {% data variables.product.prodname_vscode %} エディタの_ユーザ_設定のパーソナライズをサポートしていません。 プロジェクトのリポジトリ内の特定のプロジェクトに対して、デフォルトの _ワークスペース_および_リモート [Codespaces]_ を設定できます。 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)」を参照してください。
+
+{% endnote %}
+
+ユーザアカウントに対し、暗号化されたシークレットを追加したり、GPG 検証を有効にしたり、Codespaces が他のリポジトリアクセスできたりするように設定することもできます。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} の暗号化されたシークレットを管理する](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)」、「[{% data variables.product.prodname_codespaces %} の GPG 検証を管理する](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)」、および「[{% data variables.product.prodname_codespaces %} のアクセス権限およびセキュリティを管理する](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)」を参照してください。 "
+
+### 参考リンク
+
+* 「[新しいリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)」
diff --git a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md
index 22129ed994..acf7d853be 100644
--- a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ topics:
 
 ウィキは、{% data variables.product.product_name %} 上で直接編集することも、ウィキのファイルをローカルで編集することもできます。 デフォルトでは、リポジトリへの書き込みアクセス権を持つユーザのみがウィキに変更を加えることができますが、{% data variables.product.product_location %} の全員が{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %}リポジトリのウィキに貢献できるようにすることができます。 詳細は「[ウィキへのアクセス権限を変更する](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)」を参照してください。
 
+{% note %}
+
+**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository.
+
+{% endnote %}
+
 ### 参考リンク
 
 - 「[ウィキページを追加または編集する](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)」
diff --git a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index f02bb5284a..5f2f7eaef2 100644
--- a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ Organization の設定内、もしくはユーザが作成した特定のコメ
 ### Organization 設定でユーザをブロックする
 
 1. Organization のメンバーをブロックするには、まず Organization から[メンバーを削除](/articles/removing-a-member-from-your-organization)します。
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. [Block a user] の下で、ブロックしたいユーザ名を入力します。 ![ユーザ名フィールド](/assets/images/help/organizations/org-block-username-field.png)
 7. ブロックに期限を設定したい場合には、[Block option] ドロップダウンメニューを使い、ユーザをブロックする期間を選択します。 ![ブロックオプションのドロップダウンメニュー](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index 5a0f6dacbb..8eff1e559e 100644
--- a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,9 +28,9 @@ Organization からユーザのブロックを解除すると、そのユーザ
 
 ### Organization 設定でユーザのブロックを解除する
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. [Blocked users] の下で、ブロックを解除したいユーザの横にある [**Unblock**] をクリックします。 ![ユーザブロックの解除ボタン](/assets/images/help/organizations/org-unblock-user-button.png)
 
diff --git a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index 386201f8e5..cfd31da34f 100644
--- a/translations/ja-JP/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/ja-JP/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,9 +10,9 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. [Blocked users] の下で、Organization からブロックしたユーザの一覧を確認します。 ![ブロックされたユーザの一覧](/assets/images/help/settings/list-of-blocked-users-for-org.png)
 
diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index 32cf2be3de..8129fdb12b 100644
--- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -28,9 +28,9 @@ Organization のオーナーは、特定の期間だけユーザをブロック
 
 ### Organization での操作を制限する
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. [organization settings] サイトバーで、[**Moderation settings**] をクリックします。 ![[organization settings] サイトバーの [Moderation settings]](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. [Moderation settings] で、[**Interaction limits**] をクリックします。 ![[organization settings] サイトバーの [Interaction limits] タブ](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index 99fad750db..7dfee9bbd7 100644
--- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-プロジェクトコントリビューターにうまく作業してもらうために、プロジェクトリポジトリのルート、`docs` または `.github` フォルダに、コントリビューションガイドラインについてのファイルを追加できます。 プルリクエストをオープンした場合や Issue を作成した場合、そのファイルへのリンクが表示されます。
+### About contributing guidelines
+プロジェクトコントリビューターにうまく作業してもらうために、プロジェクトリポジトリのルート、`docs` または `.github` フォルダに、コントリビューションガイドラインについてのファイルを追加できます。 プルリクエストをオープンした場合や Issue を作成した場合、そのファイルへのリンクが表示されます。 The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ Organization {% if currentVersion == "free-pro-team@latest" or currentVersion ve
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. コントリビューションガイドラインを、リポジトリの root、`docs`、または `.github` ディレクトリに保管するかどうかを決めます。 そして、ファイル名のフィールドに、ファイルの名前および拡張子を入力します。 コントリビューションガイドラインのファイル名は大文字と小文字が区別されません。拡張子は *.md* や *.txt* などです。 ![新しいファイルの名前](/assets/images/help/repository/new-file-name.png)
+3. コントリビューションガイドラインを、リポジトリの root、`docs`、または `.github` ディレクトリに保管するかどうかを決めます。 そして、ファイル名のフィールドに、ファイルの名前および拡張子を入力します。 Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![新しいファイルの名前](/assets/images/help/repository/new-file-name.png)
     - リポジトリのルートディレクトリでコントリビューションガイドラインを表示するには、*CONTRIBUTING* と入力します。
     - リポジトリの `docs` ディレクトリにコントリビューションガイドラインを表示するには、*docs/* と入力して新しいディレクトリを作成し、次に *CONTRIBUTING* と入力します。
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. 新しいファイルに、コントリビューションガイドラインを追加します。 このガイドラインには、次のことを含めましょう:
     - 有意義な Issue やプルリクエストの作成手順
     - - 外部ドキュメント、メーリングリストや行動規範へのリンク
diff --git a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md
index fcc9d22bfa..fe997d73a4 100644
--- a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -179,7 +179,7 @@ GitHub App Manifest フローのこのステップを、1 時間以内に完了
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 エンドポイントのレスポンスに関する詳しい情報については、[マニフェストから GitHub App を作成する](/rest/reference/apps#create-a-github-app-from-a-manifest)を参照してください。
 
diff --git a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index 7408b6c23e..85e270a82e 100644
--- a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ GitHub が送信する全てのイベントには、`HTTP_X_GITHUB_EVENT` とい
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-このコードは [HTTP `POST` メソッド](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method)を使用して、「[チェック実行の作成](/rest/reference/checks#create-a-check-run)」エンドポイントを呼び出します。 このメソッドは、エンドポイントの URL とメソッドの入力パラメータという 2 つのパラメータを取ります。
+This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
 
 チェック実行を作成するために必要なのは、`name` と `head_sha` の 2 つの入力パラメータのみです。 このクイックスタートでは、後で [Rubocop](https://rubocop.readthedocs.io/en/latest/) を使用して CI テストを実装します。そのため、ここでは「Octo Rubocop」という名前を使っていますが、チェック実行には任意の名前を選ぶことができます。
 
@@ -240,31 +235,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -276,40 +262,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-上記のコードは、ジェネリックな [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method)メソッドを使用して「[チェック実行を更新する](/rest/reference/checks#update-a-check-run)」API エンドポイントを呼び出し、既に作成したチェック実行を更新します。
+The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created.
 
-このコードがしていることを説明しましょう。 まず、チェック実行のステータスを `in_progress` に更新し、`started_at` の時刻を現在の時刻に設定します。 このクイックスタートの[パート 2](#part-2-creating-the-octo-rubocop-ci-test)では、実際の CI テストを開始するコードを `***** RUN A CI TEST *****` の下に追加します。 今はこのセクションをプレースホルダーとして残しておきましょう。そうすると、続くコードが CI のプロセスを成功させ、すべてのテストに合格したことをシミュレートすることになります。 最後に、コードはチェック実行のステータスを再び `completed` に更新します。
+このコードがしていることを説明しましょう。 First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. このクイックスタートの[パート 2](#part-2-creating-the-octo-rubocop-ci-test)では、実際の CI テストを開始するコードを `***** RUN A CI TEST *****` の下に追加します。 今はこのセクションをプレースホルダーとして残しておきましょう。そうすると、続くコードが CI のプロセスを成功させ、すべてのテストに合格したことをシミュレートすることになります。 最後に、コードはチェック実行のステータスを再び `completed` に更新します。
 
 「[チェック実行を更新する](/rest/reference/checks#update-a-check-run)」 ドキュメントに、`completed` のステータスを指定すると、`conclusion` と `completed_at` のパラメータが必須となることが書かれています。 `conclusion` はチェック実行の結果を要約するもので、`success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` のいずれかになります。 この結果 (conclusion) は `success` に、`completed_at` の時刻は現在の時刻に、ステータスは `completed` に設定します。
 
@@ -613,29 +589,23 @@ text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}"
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -645,51 +615,45 @@ RuboCop の結果に基づいて (`success` または `neutral` に) 設定し
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md b/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md
index e6f090392a..b46e506d46 100644
--- a/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md
@@ -23,7 +23,7 @@ Public installation flows have a landing page to enable other people besides the
 
 ### プライベートのインストールフロー
 
-プライベートインストールフローを利用すれば、GitHub Appのオーナーだけがそのアプリケーションをインストールできます。 そのGitHub Appに関する限定的な情報はパブリックなページに存在しますが、**インストール**ボタンはOrganizationの管理者もしくはGitHub Appが個人のアカウントによって所有されている場合はそのユーザアカウントからのみ利用できます。 プライベート、もしくはインターナルのGitHub Appは、オーナーのユーザ、もしくはオーナーのOrganizationアカウントにのみインストールできます。
+プライベートインストールフローを利用すれば、GitHub Appのオーナーだけがそのアプリケーションをインストールできます。 そのGitHub Appに関する限定的な情報はパブリックなページに存在しますが、**インストール**ボタンはOrganizationの管理者もしくはGitHub Appが個人のアカウントによって所有されている場合はそのユーザアカウントからのみ利用できます。 Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### GitHub Appをインストールできるユーザの変更
 
@@ -34,5 +34,5 @@ GitHub Appをインストールできるユーザを変更するには以下の
 {% data reusables.user-settings.github_apps %}
 3. インストールオプションを変更したいGitHub Appを選択してください。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. GitHub Appのインストールオプションに応じて、**Make public（パブリックにする）**もしくは**Make internal（インターナルにする）**をクリックしてください。 ![GitHub Appのインストールオプションを変更するボタン](/assets/images/github-apps/github_apps_make_public.png)
-6. GitHub Appのインストールオプションに応じて、**Yes, make this GitHub App public（はい、このGitHub Appをパブリックにしてください）**もしくは**Yes, make this GitHub App internal（はい、このGitHub Appをインターナルにしてください）**をクリックしてください。 ![インストールオプションの変更の確認ボタン](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![GitHub Appのインストールオプションを変更するボタン](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![インストールオプションの変更の確認ボタン](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md
index fde496608c..66da19ad2f 100644
--- a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md
+++ b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md
@@ -30,7 +30,7 @@ CLIツールなどであり、ブラウザにアクセスできないなら、
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
-HTTP/1.1 200 OK
+HTTP/2 200
 X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
diff --git a/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 0b734bdc00..6dd6804d4f 100644
--- a/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -139,7 +139,7 @@ $ git clone https://github.com/github-developer/github-app-template.git
 
 ### ステップ 4. ランタイム環境の準備
 
-情報を保護するために、アプリケーションに関するすべてのシークレットは、直接コードに埋め込むのではなく、アプリケーションが見つけることができるコンピュータのメモリ中に置いておくことをおすすめします。 [dotenv](https://github.com/bkeepers/dotenv)という便利な開発ツールは、プロジェクトに固有の変数を`.env`ファイルから`ENV`にロードしてくれます。 `.env`ファイルは、決してGitHubにチェックインしないでください。 これは、パブリックなインターネット上にさらしたくない機密情報を保存するローカルファイルです。 The `.env` file is already included in the repository's [`.gitignore`](/github/getting-started-with-github/ignoring-files/) file to prevent that.
+情報を保護するために、アプリケーションに関するすべてのシークレットは、直接コードに埋め込むのではなく、アプリケーションが見つけることができるコンピュータのメモリ中に置いておくことをおすすめします。 [dotenv](https://github.com/bkeepers/dotenv)という便利な開発ツールは、プロジェクトに固有の変数を`.env`ファイルから`ENV`にロードしてくれます。 `.env`ファイルは、決してGitHubにチェックインしないでください。 これは、パブリックなインターネット上にさらしたくない機密情報を保存するローカルファイルです。 そうならないようにするために、すでに`.env`はリポジトリの[`.gitignore`](/github/getting-started-with-github/ignoring-files/)に含まれています。
 
 [必要な環境のセクション](#prerequisites)でダウンロードしたテンプレートコードには、`.env-example`というサンプルのファイルが用意されています。 このサンプルのファイルの名前を`.env-example`から`.env`に変更するか、`.env`というファイルを`.env-example`をコピーして作成してください。 まだdotenvはインストールしていませんが、このクイックスタートで後に`bundle install`を実行する際にインストールします。 **ノート:**このガイドのステップを参照するクイックスタートは、`.env-example`に追加の環境変数を含んでいることがあります。 それらの追加の環境変数を設定するためのガイダンスについては、GitHub上でクローンしたプロジェクトのクイックスタートガイドを参照してください。
 
@@ -370,10 +370,10 @@ $ ruby template_server.rb
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 うまくいっています! これは、GitHubアカウントにアプリケーションがインストールされたという通知をアプリケーションが受信したということです。 このような出力があれば、アプリケーションはサーバー上で期待どおりに動作しています。 🙌
diff --git a/translations/ja-JP/content/developers/apps/using-content-attachments.md b/translations/ja-JP/content/developers/apps/using-content-attachments.md
index d8eb6fd3f4..f3a3003cfd 100644
--- a/translations/ja-JP/content/developers/apps/using-content-attachments.md
+++ b/translations/ja-JP/content/developers/apps/using-content-attachments.md
@@ -130,21 +130,20 @@ Probotアプリケーションを作成するには、以下のステップに
 2. 作成したプロジェクトを開き、 `app.yml` ファイルの設定をカスタマイズします。 `content_reference`イベントをサブスクライブし、`content_references`の書き込み権限を有効化してください。
 
    ``` yml
-
     default_events:
-    - content_reference
-    # GitHub Appが必要とする権限セット。 このオブジェクトのフォーマットは、
+      - content_reference
+    # The set of permissions needed by the GitHub App. このオブジェクトのフォーマットは、
     # キーの権限名（たとえばissues）と値のためのアクセスの
     # 種類（たとえばwrite）を使います。
-    # 取り得る値は `read`、`write`、`none`
+    # Valid values are `read`, `write`, and `none`
     default_permissions:
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. このコードを`index.js` ファイルに追加して、`content_reference`を処理してREST APIを呼ぶようにします。
diff --git a/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index 7fa89e3f82..061c257a0f 100644
--- a/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ To offer paid plans for your app, the app must be owned by an organization and y
 
 ### Requesting publisher verification
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. 左サイドバーで [**Developer settings**] をクリックします。 ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. Under "Publisher Verification", complete the information in the checklist:
    - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
    - Ensure that Two-factor authentication is enabled for your organization. 詳しい情報については [Organization で 2 要素認証を要求する](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)を参照してください。
-   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/ja-JP/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index 83308c1841..574ec3cc30 100644
--- a/translations/ja-JP/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/ja-JP/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ topics:
 
 #### リスト名
 
-アプリケーションの名前は、[{% data variables.product.prodname_marketplace %} ホームページ](https://github.com/marketplace)に表示されます。 名前の上限は 255 文字です。
+Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing {% data variables.product.product_name %} user, unless the name is your own user or organization name.
 
 #### ごく簡単な説明
 
diff --git a/translations/ja-JP/content/developers/overview/secret-scanning.md b/translations/ja-JP/content/developers/overview/secret-scanning.md
index be14bce550..b6ed1d937d 100644
--- a/translations/ja-JP/content/developers/overview/secret-scanning.md
+++ b/translations/ja-JP/content/developers/overview/secret-scanning.md
@@ -15,9 +15,9 @@ topics:
 
 シークレットのフォーマットに対する一致がパブリックリポジトリで見つかった場合、選択したHTTPのエンドポイントにペイロードが送信されます。
 
-When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。
+When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。
 
-This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program.
+This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program.
 
 ### The {% data variables.product.prodname_secret_scanning %} process
 
@@ -54,26 +54,20 @@ Send this information to <a href="mailto:secret-scanning@github.com">secret-scan
 
 #### シークレットアラートサービスの作成
 
-提供したURLに、パブリックでインターネットからアクセスできるHTTPエンドポイントを作成してください。 パブリックリポジトリで正規表現への一致が見つかった場合、{% data variables.product.prodname_dotcom %}はHTTPの`POST`メッセージをエンドポイントに送信します。
+提供したURLに、パブリックでインターネットからアクセスできるHTTPエンドポイントを作成してください。 When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint.
 
 ##### エンドポイントに送信されるPOSTの例
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 メッセージのボディはJSONの配列で、以下の内容を持つ1つ以上のオブジェクトを含みます。 複数の一致が見つかった場合には、{% data variables.product.prodname_dotcom %}は複数のシークレットの一致を含む1つのメッセージを送信することがあります。 エンドポイントは、タイムアウトすることなく大量の一致を含むリクエストを処理できなければなりません。
@@ -88,19 +82,31 @@ Content-Length: 0123
 
 {% data variables.product.prodname_dotcom %}のシークレットスキャンニング公開鍵はhttps://api.github.com/meta/public_keys/secret_scanningから取得でき、`ECDSA-NIST-P256V1-SHA256`アルゴリズムを使ってメッセージを検証できます。
 
-次のメッセージを受信したとして、以下のコードは署名検証の方法を示しています。 このコードはまた、`GITHUB_PRODUCTION_TOKEN`という環境変数に生成されたPATが設定されているものとしています(https://github.com/settings/tokens)。 このトークンには権限が設定されている必要はありません。
+{% note %}
+
+**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
+
+{% endnote %}
+
+次のメッセージを受信したとして、以下のコードは署名検証の方法を示しています。 The code snippets assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens) to avoid hitting rate limits. The PAT does not need any scopes/permissions.
+
+{% note %}
+
+**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
+
+{% endnote %}
 
 **検証エンドポイントに送信されたサンプルのメッセージ**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Goでの検証のサンプル**
@@ -123,14 +129,14 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
-  // GitHub公開鍵のリストをフェッチ
-  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  // Fetch the list of GitHub Public Keys
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
     fmt.Printf("Error preparing request: %s\n", err)
     os.Exit(1)
@@ -156,7 +162,7 @@ func main() {
     os.Exit(3)
   }
 
-  // webhookの署名に使われた鍵を見つける
+  // Find the Key used to sign our webhook
   pubKey, err := func() (string, error) {
     for _, v := range keys.PublicKeys {
       if v.KeyIdentifier == kID {
@@ -172,21 +178,21 @@ func main() {
     os.Exit(4)
   }
 
-  // 公開鍵のデコード
+  // Decode the Public Key
   block, _ := pem.Decode([]byte(pubKey))
   if block == nil {
     fmt.Println("Error parsing PEM block with GitHub public key")
     os.Exit(5)
   }
 
-  // ECDSA公開鍵の生成
+  // Create our ECDSA Public Key
   key, err := x509.ParsePKIXPublicKey(block.Bytes)
   if err != nil {
     fmt.Printf("Error parsing DER encoded public key: %s\n", err)
     os.Exit(6)
   }
 
-  // ドキュメントから、これが*ecdsa.PublicKeyであることは分かっている
+  // Because of documentation, we know it's a *ecdsa.PublicKey
   ecdsaKey, ok := key.(*ecdsa.PublicKey)
   if !ok {
     fmt.Println("GitHub key was not ECDSA, what are they doing?!")
@@ -234,16 +240,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -349,4 +355,3 @@ A few important points:
 **Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
 {% endnote %}
-
diff --git a/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md b/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md
index d3103fddc9..20c3d07374 100644
--- a/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-Mac OS Xでは、再起動時に`ssh-agent`が起動し直されると、キーは「忘れられて」しまいます。 ただし、以下のコマンドでキーチェーンにSSHキーをインポートできます。
+On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. ただし、以下のコマンドでキーチェーンにSSHキーをインポートできます。
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md
index ac6edb518c..5da3744076 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ Events APIエンドポイントから返されるイベントオブジェクト
 この例は、[Events API](/rest/reference/activity#events)を使用する際の[WatchEvent](#watchevent)のレスポンスの形式を示しています。
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
@@ -195,7 +195,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 | -------------- | -------- | ---------------------------------------- |
 | `action`       | `string` | 実行されたアクション. `created `になりうる。             |
 | `pull_request` | `オブジェクト` | The pull request the review pertains to. |
-| `レビュー`         | `オブジェクト` | The review that was affected.            |
+| `レビュー`         | `オブジェクト` | 影響されるレビュー。                               |
 
 ### PullRequestReviewCommentEvent
 
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index 807a7a42e6..189ceec0f0 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -61,7 +61,7 @@ webhook によって設定されている URL エンドポイントに配信さ
 #### デリバリの例
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -200,7 +200,9 @@ webhook によって設定されている URL エンドポイントに配信さ
 
 webhook イベントは、登録したドメインの特異性に基づいてトリガーされます。 たとえば、サブドメイン (`https://subdomain.example.com`) を登録すると、サブドメインの URL のみがこのイベントをトリガーします。 ドメイン (`https://example.com`) を登録すると、ドメインとすべてのサブドメインの URL がこのイベントをトリガーします。 新しいコンテンツ添付ファイルを作成するには、「[コンテンツ添付ファイルの作成](/rest/reference/apps#create-a-content-attachment)」を参照してください。
 
-このイベントを受信できるのは {% data variables.product.prodname_github_app %} のみです。 {% data variables.product.prodname_github_app %} には、このイベントをサブスクライブするための `content_references` `write` 権限が必要です。
+#### 利用の可否
+
+- {% data variables.product.prodname_github_app %}s with the `content_references:write` permission
 
 #### webhook ペイロードの例
 
@@ -509,7 +511,7 @@ Activity related to a comment in a discussion. For more information, see "[Using
 
 {% note %}
 
-`repository` property when the event occurs from activity in a repository.
+**Note:** This event replaces the deprecated `integration_installation_repositories` event.
 
 {% endnote %}
 
@@ -585,13 +587,13 @@ Activity related to a comment in a discussion. For more information, see "[Using
 
 #### webhook ペイロードオブジェクト
 
-| キー                     | 種類       | 説明                                                           |
-| ---------------------- | -------- | ------------------------------------------------------------ |
-| `action`               | `string` | 実行されたアクション. `created`、`edited`、`deleted` のいずれかを指定可。          |
-| `ラベル`                  | `オブジェクト` | ラベルが追加された。                                                   |
-| `変更`                   | `オブジェクト` | アクションが `edited` の場合のラベルへの変更。                                 |
-| `changes[name][from]`  | `string` | The previous version of the name if the action was `edited`. |
-| `changes[color][from]` | `string` | アクションが `edited` の場合の以前のバージョンの色。                              |
+| キー                     | 種類       | 説明                                                  |
+| ---------------------- | -------- | --------------------------------------------------- |
+| `action`               | `string` | 実行されたアクション. `created`、`edited`、`deleted` のいずれかを指定可。 |
+| `ラベル`                  | `オブジェクト` | ラベルが追加された。                                          |
+| `changes`              | `オブジェクト` | アクションが `edited` の場合のラベルへの変更。                        |
+| `changes[name][from]`  | `string` | アクションが`edited`だった場合、以前のバージョンの名前。                    |
+| `changes[color][from]` | `string` | アクションが `edited` の場合の以前のバージョンの色。                     |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
@@ -1010,12 +1012,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus
 
 {% endnote %}
 
-{% tip %}
-
-**注釈**: 表に続く webhook ペイロードの例は、表に記載されているイベント API ペイロードとは大幅に異なります。 違いの中でも、webhook ペイロードには `sender` オブジェクトと `pusher` オブジェクトの両方が含まれています。 送信者とプッシャーは `push` イベントを開始した同じユーザですが、`sender` オブジェクトには詳細が含まれています。
-
-{% endtip %}
-
 #### 利用の可否
 
 - リポジトリ webhook
@@ -1206,7 +1202,7 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-スポンサーシップ webhook は、{% data variables.product.prodname_dotcom %} でのみ作成できます。 詳しい情報については、「[スポンサー付きアカウントのイベントの webhook を設定する](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)」を参照してください。
+スポンサーシップ webhook は、{% data variables.product.prodname_dotcom %} でのみ作成できます。 詳しい情報については、「[スポンサー付きアカウントのイベントの webhook を設定する](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)」を参照してください。
 
 #### 利用の可否
 
@@ -1292,9 +1288,9 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus
 | ----------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `action`                                        | `string`  | 実行されたアクション. `created`、 `deleted`、`edited`、`added_to_repository`、`removed_from_repository` のいずれかを指定可。                                                              |
 | `Team`                                          | `オブジェクト`  | Team 自体。                                                                                                                                                          |
-| `変更`                                            | `オブジェクト`  | アクションが `edited` の場合の Team への変更。                                                                                                                                   |
-| `changes[description][from]`                    | `string`  | The previous version of the description if the action was `edited`.                                                                                               |
-| `changes[name][from]`                           | `string`  | The previous version of the name if the action was `edited`.                                                                                                      |
+| `changes`                                       | `オブジェクト`  | アクションが `edited` の場合の Team への変更。                                                                                                                                   |
+| `changes[description][from]`                    | `string`  | アクションが `edited` の場合、以前のバージョンの説明。                                                                                                                                  |
+| `changes[name][from]`                           | `string`  | アクションが`edited`だった場合、以前のバージョンの名前。                                                                                                                                  |
 | `changes[privacy][from]`                        | `string`  | アクションが `edited` の場合の以前のバージョンのTeam プライバシー。                                                                                                                         |
 | `changes[repository][permissions][from][admin]` | `boolean` | アクションが `edited` の場合の、リポジトリに対する以前のバージョンの Team メンバーの `admin` 権限。                                                                                                    |
 | `changes[repository][permissions][from][pull]`  | `boolean` | アクションが `edited` の場合の、リポジトリに対する以前のバージョンの Team メンバーの `pull` 権限。                                                                                                     |
diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index ab342cfdc4..c22bcc5476 100644
--- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %}詳しい情報については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
 
-ディスカッションの開始または表示に加えて、ディスカッションの作者のコメントに対してコメントすることができます。 また、ディスカッション内で別のコミュニティメンバーが行った個々のコメントに返信してコメントスレッドを作成し、絵文字でコメントにリアクションすることもできます。 リアクションに関する詳しい情報については、「[{% data variables.product.prodname_dotcom %} での会話について](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)」を参照してください。
+ディスカッションの開始または表示に加えて、ディスカッションの作者のコメントに対してコメントすることができます。 また、ディスカッション内で別のコミュニティメンバーが行った個々のコメントに返信してコメントスレッドを作成し、絵文字でコメントにリアクションすることもできます。
 
 {% data variables.product.product_name %} で、ユーザをブロックし、破壊的なコンテンツを報告して、安全で快適な環境を維持できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} での安全を維持する](/communities/maintaining-your-safety-on-github)」を参照してください。
 
diff --git a/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md
index 9a873985d1..f7923361f5 100644
--- a/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md
+++ b/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md
@@ -16,5 +16,5 @@ versions:
 ### 参考リンク
 
 - 「[ディスカッションを検索する](/github/searching-for-information-on-github/searching-discussions)」
-- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
-- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)"
+- 「[Discussions について](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」
+- 「[コミュニティの Discussions を管理する](/discussions/managing-discussions-for-your-community)」
diff --git a/translations/ja-JP/content/discussions/index.md b/translations/ja-JP/content/discussions/index.md
index dd81b9f5db..5a6ed7c6f0 100644
--- a/translations/ja-JP/content/discussions/index.md
+++ b/translations/ja-JP/content/discussions/index.md
@@ -34,24 +34,3 @@ versions:
 <!-- {% link_with_intro /discussions-guides %} -->
 <!-- {% link_with_intro /collaborating-with-your-community-using-discussions %} -->
 <!-- {% link_with_intro /managing-discussions-for-your-community %} -->
-
-<!-- Community examples -->
-{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %}
-{% if discussionsCommunityExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">ディスカッションを使用しているコミュニティ</h2>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render discussions-community-card for discussionsCommunityExamples as example %}
-  </div>
-  {% if discussionsCommunityExamples.length > 6 %}
-    <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">さらに表示 {% octicon "arrow-right" %}</button>
-  {% endif %}
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">検索結果はありません <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">フィルタに適合する例がないようです。<br>別のフィルタを試すか、コード例を追加してください</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/discussions_community_examples.yml">コミュニティを追加 {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md b/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md
index 36fe2a6f71..4f02fc9053 100644
--- a/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md
@@ -47,6 +47,8 @@ topics:
 - [フォースプッシュを許可](#allow-force-pushes)
 - [削除を許可](#allow-deletions)
 
+For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+
 #### マージ前に Pull Request レビュー必須
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
@@ -100,7 +102,15 @@ remote: error: Changes have been requested.
 
 {% note %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+**ノート:**
+
+* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+
+{% else %}
 **注釈:** コラボレータが未署名のコミットをコミット署名必須のブランチにプッシュすると、コラボレータは検証済み署名を含めるためにコミットをリベースしてから、書き直したコミットをブランチにフォースプッシュする必要があります。
+{% endif %}
 
 {% endnote %}
 
@@ -135,7 +145,7 @@ remote: error: Changes have been requested.
 
 フォースプッシュを有効化しても、他のブランチ保護ルールは上書きされません。 たとえば、ブランチに直線状のコミット履歴が必要な場合、そのブランチにマージコミットをフォースプッシュすることはできません。
 
-{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. 詳しい情報については、「[ユーザアカウントもしくはOrganizationが所有するリポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)」を参照してください。
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}サイト管理者がリポジトリ内のすべてのブランチへのフォースプッシュをブロックしている場合、保護されたブランチのフォースプッシュを有効にすることはできません。 詳しい情報については、「[ユーザアカウントもしくはOrganizationが所有するリポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)」を参照してください。
 
 サイト管理者がデフォルトブランチへのフォースプッシュのみをブロックしている場合、他の保護されたブランチに対してフォースプッシュを有効にできます。{% endif %}
 
diff --git a/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md
index c086153407..cc01b6358b 100644
--- a/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/ja-JP/content/github/administering-a-repository/changing-the-default-branch.md
@@ -1,6 +1,6 @@
 ---
-title: Changing the default branch
-intro: 'If you have more than one branch in your repository, you can configure any branch as the default branch.'
+title: デフォルトブランチを変更する
+intro: リポジトリに複数のブランチがある場合、任意のブランチをデフォルトブランチとして設定できます。
 permissions: People with admin permissions to a repository can change the default branch for the repository.
 versions:
   free-pro-team: '*'
@@ -13,21 +13,21 @@ topics:
   - Repositories
 ---
 
-### About changing the default branch
+### デフォルトブランチの変更について
 
-You can choose the default branch for a repository. The default branch is the base branch for pull requests and code commits. デフォルトブランチの詳細については、「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)」を参照してください。
+リポジトリのデフォルトブランチは選択できます。 デフォルトブランチは、プルリクエストやコードのコミットを行う基点となるブランチです。 デフォルトブランチの詳細については、「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)」を参照してください。
 
 {% if currentVersion != "github-ae@latest" %}
 {% note %}
 
-**Note**: If you use the Git-Subversion bridge, changing the default branch will affect your `trunk` branch contents and the `HEAD` you see when you list references for the remote repository. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)" and [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) in the Git documentation.
+**注釈**: Git-Subversion ブリッジを使用している場合、デフォルトブランチを変更すると, changing the default branch will affect your `trunk` ブランチのコンテンツと、リモートリポジトリのリファレンスを一覧表示するときに表示される`HEAD` に影響を与えます。 詳しい情報については、「[Subversion クライアントのサポート](/github/importing-your-projects-to-github/support-for-subversion-clients)」および Git ドキュメンテーション内の [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) を参照してください。
 
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
-You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
+デフォルトブランチの名前は変更することもできます。 詳しい情報については、「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照してください。
 
 {% endif %}
 
@@ -39,26 +39,26 @@ You can also rename the default branch. For more information, see "[Renaming a b
 
 ### 必要な環境
 
-To change the default branch, your repository must have more than one branch. 詳しい情報については[リポジトリ内でのブランチの作成と削除](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)を参照してください。
+デフォルトブランチを変更するには、リポジトリに複数のブランチが存在する必要があります。 詳しい情報については[リポジトリ内でのブランチの作成と削除](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)を参照してください。
 
-### Changing the default branch
+### デフォルトブランチを変更する
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
-1. Under "Default branch", to the right of the default branch name, click {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Switch icon with two arrows to the right of current default branch name](/assets/images/help/repository/repository-options-defaultbranch-change.png)
-1. Use the drop-down, then click a branch name. ![Drop-down to choose new default branch](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png)
-1. [**Update**] をクリックします。 !["Update" button after choosing a new default branch](/assets/images/help/repository/repository-options-defaultbranch-update.png)
-1. Read the warning, then click **I understand, update the default branch.** !["Update" button after choosing a new default branch](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
+1. [Default branch] の下にある、デフォルトブランチ名の右側の、{% octicon "arrow-switch" aria-label="The switch icon with two arrows" %} をクリックします。 ![現在のデフォルトブランチ名の右側にある、2 つの矢印がついた切り替えアイコン](/assets/images/help/repository/repository-options-defaultbranch-change.png)
+1. ドロップダウンメニューで、ブランチ名をクリックします。 ![新しいデフォルトブランチを選択するドロップダウン](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png)
+1. [**Update**] をクリックします。 ![新しいブランチを選択後の [Update] ボタン](/assets/images/help/repository/repository-options-defaultbranch-update.png)
+1. 警告を読んでから、[**I understand, update the default branch.**] (わかりました。デフォルトのブランチを更新してください) をクリックします。 ![新しいブランチを選択後の [Update] ボタン](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
 
 {% else %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
-1. In the default branch drop-down, choose the new default branch. ![デフォルトブランチ ドロップダウン セレクター](/assets/images/help/repository/repository-options-defaultbranch.png)
+1. デフォルトブランチのドロップダウンメニューで、新しいデフォルトブランチを選択します。 ![デフォルトブランチ ドロップダウン セレクター](/assets/images/help/repository/repository-options-defaultbranch.png)
 1. [**Update**] をクリックします。
 
 {% endif %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/classifying-your-repository-with-topics.md b/translations/ja-JP/content/github/administering-a-repository/classifying-your-repository-with-topics.md
index bce2257033..0ebf3ead4d 100644
--- a/translations/ja-JP/content/github/administering-a-repository/classifying-your-repository-with-topics.md
+++ b/translations/ja-JP/content/github/administering-a-repository/classifying-your-repository-with-topics.md
@@ -14,17 +14,17 @@ topics:
 
 ### Topics について
 
-Topics を利用すれば、特定の領域に関するリポジトリを調べたり、コントリビュートするプロジェクトを見つけたり、特定の問題に対する新たなソリューションを見つけ出すことができます。 Topics は、リポジトリのメインページに表示されます。 You can click a topic name to {% if currentVersion == "free-pro-team@latest" %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+Topics を利用すれば、特定の領域に関するリポジトリを調べたり、コントリビュートするプロジェクトを見つけたり、特定の問題に対する新たなソリューションを見つけ出すことができます。 Topics は、リポジトリのメインページに表示されます。 Topics 名をクリックして、{% if currentVersion == "free-pro-team@latest" %}関連する Topics や、その Topics に分類される他のリポジトリのリストを見たりすることができます。{% else %}そのトピックの他のリポジトリを検索することができます。{% endif %}
 
 ![Topics を表示しているテストリポジトリのメインページ](/assets/images/help/repository/os-repo-with-topics.png)
 
 最も利用されているトピックをブラウズするには https://github.com/topics/ にアクセスしてください。
 
-{% if currentVersion == "free-pro-team@latest" %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}[github/explore](https://github.com/github/explore) リポジトリにある {% data variables.product.product_name %}の注目の Topics 集にコントリビュートできます。 {% endif %}
 
-リポジトリの管理者は、リポジトリに好きなトピックを追加できます。 Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% if currentVersion == "free-pro-team@latest" %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. プライベートリポジトリの内容は分析されず、Topics が推奨されることはありません。{% endif %}
+リポジトリの管理者は、リポジトリに好きなトピックを追加できます。 リポジトリを分類するのに役立つトピックには、そのリポジトリの意図する目的、主題の領域、コミュニティ、言語などがあります。{% if currentVersion == "free-pro-team@latest" %}加えて、{% data variables.product.product_name %}はパブリックなリポジトリの内容を分析し、推奨されるトピックを生成します。リポジトリの管理者は、これを受諾することも拒否することもできます。 プライベートリポジトリの内容は分析されず、Topics が推奨されることはありません。{% endif %}
 
-{% if currentVersion == "github-ae@latest" %}Internal {% else %}Public, internal, {% endif %}and private repositories can have topics, although you will only see private repositories that you have access to in topic search results.
+{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック、内部、{% endif %}およびプライベートリポジトリも Topics を持つことができますが、Topics の検索結果で見えるプライベートリポジトリはアクセス権を持っているものだけです。
 
 特定のトピックに関連付けられているリポジトリを検索できます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories#search-by-topic)を参照してください。 また、{% data variables.product.product_name %} 上でトピックのリストを検索することもできます。 詳細は「[トピックを検索する](/articles/searching-topics)」を参照してください。
 
diff --git a/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index 52831432ed..38218fdb08 100644
--- a/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -26,7 +26,7 @@ topics:
 
 {% note %}
 
-**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
+**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 詳しい情報については、「[Organization での {% data variables.product.prodname_actions %} を無効化または制限する](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)」または{% if currentVersion == "free-pro-team@latest" %}「[Enterprise アカウントで {% data variables.product.prodname_actions %} ポリシーを施行する](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)」{% elsif currentVersion ver_gt "enterprise-server@2.21"%}「[Enterprise で {% data variables.product.prodname_actions %} ポリシーを施行する](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。{% endif %}
 
 {% endnote %}
 
@@ -41,13 +41,13 @@ topics:
 
 ### リポジトリの {% data variables.product.prodname_actions %} 権限を管理する
 
-You can disable all workflows for a repository or set a policy that configures which actions can be used in a repository.
+リポジトリに対するワークフローをすべて無効にすることも、リポジトリでどのアクションを使用できるかを設定するポリシーを設定することもできます。
 
 {% data reusables.actions.actions-use-policy-settings %}
 
 {% note %}
 
-**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 詳しい情報については、「[Organization での {% data variables.product.prodname_actions %} を無効化または制限する](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)」または{% if currentVersion == "free-pro-team@latest" %}「[Enterprise アカウントで {% data variables.product.prodname_actions %} ポリシーを施行する](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)」{% elsif currentVersion ver_gt "enterprise-server@2.21" %}「[Enterprise で {% data variables.product.prodname_actions %} ポリシーを施行する](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)」を参照してください。
 
 {% endif %}
 
@@ -56,17 +56,17 @@ You can disable all workflows for a repository or set a policy that configures w
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions %}
-1. Under **Actions permissions**, select an option. ![Set actions policy for this organization](/assets/images/help/repository/actions-policy.png)
+1. [**Actions permissions**] で、オプションを選択します。 ![この Organization に対するアクションポリシーを設定する](/assets/images/help/repository/actions-policy.png)
 1. [**Save**] をクリックします。
 
-### Allowing specific actions to run
+### 特定のアクションの実行を許可する
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions %}
-1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png)
+1. [**Actions permissions**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![許可リストにアクションを追加する](/assets/images/help/repository/actions-policy-allow-list.png)
 2. [**Save**] をクリックします。
 {% endif %}
 
@@ -82,3 +82,21 @@ You can disable all workflows for a repository or set a policy that configures w
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your repository
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. **Save（保存）**をクリックして、設定を適用してください。
+{% endif %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index b567a6e514..ebe92b0404 100644
--- a/translations/ja-JP/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### FUNDING ファイルについて
 
-デフォルトブランチの、リポジトリ内の `.github` フォルダにある _FUNDING.yml_ ファイルを編集することで、スポンサーボタンを設定できます。 ボタンには、{% data variables.product.prodname_sponsors %} のスポンサード開発者、外部の資金獲得プラットフォーム、またはカスタムの資金獲得 URL を含めることができます。 {% data variables.product.prodname_sponsors %} の詳細は、「[GitHub Sponsors について](/articles/about-github-sponsors)」を参照してください。
+デフォルトブランチの、リポジトリ内の `.github` フォルダにある _FUNDING.yml_ ファイルを編集することで、スポンサーボタンを設定できます。 ボタンには、{% data variables.product.prodname_sponsors %} のスポンサード開発者、外部の資金獲得プラットフォーム、またはカスタムの資金獲得 URL を含めることができます。 {% data variables.product.prodname_sponsors %} の詳細は、「[GitHub Sponsors について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」を参照してください。
 
 外部の資金獲得プラットフォームごとに 1 つのユーザ名、パッケージ名、またはプロジェクト名と、最大 4 つのカスタム URL を追加できます。 {% data variables.product.prodname_sponsors %} には、スポンサード開発者または Organization を最大 4 人追加できます。 追加する場合は、プラットフォームごとに改行し、以下の構文に従ってください:
 
@@ -76,5 +76,5 @@ custom: ["https://www.paypal.me/octocat", octocat.com]
 {% data reusables.files.propose_new_file %}
 
 ### 参考リンク
-- 「[オープンソースコントリビューターに対する {% data variables.product.prodname_sponsors %} について](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)」
+- 「[オープンソースコントリビューターに対する {% data variables.product.prodname_sponsors %} について](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)」
 - {% data variables.product.prodname_blog %} の「[{% data variables.product.prodname_sponsors %} Team に関するよくある質問](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)」
diff --git a/translations/ja-JP/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md
index 02f98a7025..99e216744a 100644
--- a/translations/ja-JP/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository.md
@@ -9,7 +9,7 @@ versions:
 
 次の場合に、リポジトリの管理者は、特定のリポジトリに対する匿名 Git 読み取りアクセスの設定を変更できます。
 - サイトの管理者がプライベートモードと匿名 Git 読み取りアクセスを有効化している。
-- The repository is public on the enterprise and is not a fork.
+- リポジトリは Enterprise 上でパブリックであり、フォークではない。
 - サイト管理者がリポジトリで匿名 Git 読み取りアクセスを無効化していない。
 
 {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 9372e7690b..557db48ae9 100644
--- a/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling or disabling GitHub Discussions for a repository
-intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.'
+title: リポジトリの GitHub Discussions を有効化または無効化する
+intro: Issue 内の作業範囲を指定することなく、コミュニティで会話したり、質問したり、回答を投稿したりするための場として、リポジトリで Discussions を使用できます。
 product: '{% data reusables.gated-features.discussions %}'
 permissions: People with admin permissions to a repository can enable discussions for the repository.
 versions:
@@ -11,12 +11,12 @@ topics:
 
 {% data reusables.discussions.beta %}
 
-### Enabling or disabling discussions for your repository
+### リポジトリで Discussions を有効化または無効化する
 
 {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %}
-1. To disable discussions, under "Features", unselect **Discussions**.
+1. Discussions を無効化するには、[Features] で [**Discussions**] の選択を解除します。
 
 ### 参考リンク
 
-- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
-- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)"
+- 「[Discussions について](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」
+- 「[コミュニティの Discussions を管理する](/discussions/managing-discussions-for-your-community)」
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md
index c02cf8d721..fafe51164a 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-a-branch-protection-rule.md
@@ -1,6 +1,6 @@
 ---
-title: Managing a branch protection rule
-intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.'
+title: ブランチ保護ルールを管理する
+intro: 保護されたブランチにマージされる前に、すべてのプルリクエストでレビューへの承認またはステータスチェックへのパスを必須とするなど、1 つ以上のブランチに対して特定のワークフローを強制するため、ブランチ保護ルールを作成できます。
 product: '{% data reusables.gated-features.protected-branches %}'
 redirect_from:
   - /articles/configuring-protected-branches
@@ -29,7 +29,7 @@ topics:
 
 {% data reusables.repositories.branch-rules-example %}
 
-You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. {% data variables.product.company_short %}は、`File.fnmatch` 構文に `File::FNM_PATHNAME` フラグを使用するので、ワイルドカードはディレクトリの区切り文字 (`/`) には一致しません。 たとえば、`qa/*` は、`qa/` で始まり、1 つのスラッシュが含まれるすべてのブランチにマッチします。 You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. ブランチのルールに関する構文オプションの詳しい情報については、 [fnmatch ドキュメンテーション](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)を参照してください。
+ワイルドカード構文 `*` で、リポジトリ内の現在および将来のブランチすべてに対するルールを作成できます。 {% data variables.product.company_short %}は、`File.fnmatch` 構文に `File::FNM_PATHNAME` フラグを使用するので、ワイルドカードはディレクトリの区切り文字 (`/`) には一致しません。 たとえば、`qa/*` は、`qa/` で始まり、1 つのスラッシュが含まれるすべてのブランチにマッチします。 `qa/**/*` とすると、複数のスラッシュにマッチします。また、より多くのブランチにマッチさせるため、`qa` の文字列を `qa**/**/*` とすることもできます。 ブランチのルールに関する構文オプションの詳しい情報については、 [fnmatch ドキュメンテーション](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)を参照してください。
 
 リポジトリが同じブランチに影響する複数の保護されたブランチのルールを持っているなら、特定のブランチ名を含むルールがもっとも高い優先順位を持ちます。 同じ特定のブランチ名を参照する保護されたブランチのルールが複数あるなら、最初に作成されたブランチルールが高い優先順位を持ちます。
 
@@ -37,48 +37,48 @@ You can create a rule for all current and future branches in your repository wit
 
 既存のブランチのルールに例外を作成するため、特定のブランチ名に対するルールなど、優先度の高いブランチ保護ルールを新しく作成できます。
 
-For more information about each of each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+使用できるブランチ保護設定の各ルールに関する詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)」を参照してください。
 
-### Creating a branch protection rule
+### ブランチ保護ルールを作成する
 
-When you create a branch rule, the branch you specify doesn't have to exist yet in the repository.
+ブランチのルールを作成する際に、指定したブランチがリポジトリにしている必要はありません。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
 {% data reusables.repositories.add-branch-protection-rules %}
-1. Optionally, enable required pull request reviews.
-   - Under "Protect matching branches", select **Require pull request reviews before merging**. ![プルリクエストレビューの制限チェックボックス](/assets/images/help/repository/PR-reviews-required.png)
-   - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you'd like to require on the branch. ![必須とするレビュー承認の数を選択するドロップダウンメニュー](/assets/images/help/repository/number-of-required-review-approvals.png)
-   - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**. ![新たなコミットがチェックボックスにプッシュされた際に古いプルリクエストの承認を却下するチェックボックス](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png)
-   - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。 ![コードオーナーのレビューを必要とする](/assets/images/help/repository/PR-review-required-code-owner.png)
-   - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. 詳しい情報については[プルリクエストレビューの却下](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)を参照してください。 ![[Restrict who can dismiss pull request reviews] チェックボックス](/assets/images/help/repository/PR-review-required-dismissals.png)
-1. Optionally, enable required status checks.
+1. 必要に応じて、Pull Requestレビュー必須を有効化します。
+   - [Protect matching branches] で、[**Require pull request reviews before merging**] を選択します。 ![プルリクエストレビューの制限チェックボックス](/assets/images/help/repository/PR-reviews-required.png)
+   - [**Required approving reviews**] ドロップダウンメニューをクリックし、ブランチで必須にする承認レビューの数を選択します。 ![必須とするレビュー承認の数を選択するドロップダウンメニュー](/assets/images/help/repository/number-of-required-review-approvals.png)
+   - コードを変更するコミットがブランチにプッシュされたときにプルリクエストの承認レビューを却下する場合は、[**Dismiss stale pull request approvals when new commits are pushed**] を選択します。 ![新たなコミットがチェックボックスにプッシュされた際に古いプルリクエストの承認を却下するチェックボックス](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png)
+   - 指定されたオーナーのコードにプルリクエストが影響する場合に、コードオーナーからのレビューを必須にする場合は、[**Require review from Code Owners**] を選択します。 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。 ![コードオーナーのレビューを必要とする](/assets/images/help/repository/PR-review-required-code-owner.png)
+   - リポジトリが Organization の一部である場合、[**Restrict who can dismiss pull request reviews**] を選択します。 そして、Pull Requestレビューを却下できるユーザまたは Team を検索して選択します。 詳しい情報については[プルリクエストレビューの却下](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)を参照してください。 ![[Restrict who can dismiss pull request reviews] チェックボックス](/assets/images/help/repository/PR-review-required-dismissals.png)
+1. 必要に応じて、ステータスチェック必須を有効化します。
    - [**Require status checks to pass before merging**] を選択します。 ![必須ステータスチェックのオプション](/assets/images/help/repository/required-status-checks.png)
-   - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**. ![必須ステータスのチェックボックス、ゆるい、または厳格な](/assets/images/help/repository/protecting-branch-loose-status.png)
+   - プルリクエストを保護されたブランチの最新コードで確実にテストしたい場合は、[**Require branches to be up to date before merging**] を選択します。 ![必須ステータスのチェックボックス、ゆるい、または厳格な](/assets/images/help/repository/protecting-branch-loose-status.png)
    - 使用可能なステータスチェックのリストから、必須とするものを選択します。 ![利用可能なステータスチェックの一覧](/assets/images/help/repository/required-statuses-list.png)
-1. Optionally, select **Require signed commits**. ![[Require signed commits] オプション](/assets/images/help/repository/require-signed-commits.png)
-1. Optionally, select **Require linear history**. ![必須の直線状の履歴オプション](/assets/images/help/repository/required-linear-history.png)
+1. 必要に応じて、[**Require signed commits**] を選択します。 ![[Require signed commits] オプション](/assets/images/help/repository/require-signed-commits.png)
+1. 必要に応じて、[**Require linear history**] を選択します。 ![必須の直線状の履歴オプション](/assets/images/help/repository/required-linear-history.png)
 1. オプションとして、[**Include administrators**] を選択します。 ![[Include administrators] チェックボックス](/assets/images/help/repository/include-admins-protected-branches.png)
-1. Optionally,{% if currentVersion == "free-pro-team@latest" %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions.
-   - Select **Restrict who can push to matching branches**. ![ブランチ制限のチェックボックス](/assets/images/help/repository/restrict-branch.png)
-   - Search for and select the people, teams, or apps who will have permission to push to the protected branch. ![ブランチ制限の検索](/assets/images/help/repository/restrict-branch-search.png)
-1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. ![フォースプッシュオプションを許可する](/assets/images/help/repository/allow-force-pushes.png)
-1. Optionally, select **Allow deletions**. ![ブランチ削除オプションを許可する](/assets/images/help/repository/allow-branch-deletions.png)
+1. 必要に応じて、{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_team %} または {% data variables.product.prodname_ghe_cloud %} を使用する Organization がリポジトリを所有している場合には、{% endif %}ブランチ制限を有効化します。
+   - [**Restrict who can push to matching branches**] を選択します。 ![ブランチ制限のチェックボックス](/assets/images/help/repository/restrict-branch.png)
+   - 保護されたブランチにプッシュできる権限を持つユーザ、Team、またはアプリを検索し、選択します。 ![ブランチ制限の検索](/assets/images/help/repository/restrict-branch-search.png)
+1. 必要に応じて、[Rules applied to everyone including administrators] で [**Allow force pushes**] を選択します。 ![フォースプッシュオプションを許可する](/assets/images/help/repository/allow-force-pushes.png)
+1. 必要に応じて、[**Allow deletions**] を選択します。 ![ブランチ削除オプションを許可する](/assets/images/help/repository/allow-branch-deletions.png)
 1. ** Create（作成）**をクリックしてください。
 
-### Editing a branch protection rule
+### ブランチ保護ルールを編集する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
-1. To the right of the branch protection rule you want to edit, click **Edit**. ![編集ボタン](/assets/images/help/repository/edit-branch-protection-rule.png)
-1. Make your desired changes to the branch protection rule.
+1. 編集する保護ルールの右にある [**Edit**] をクリックします。 ![編集ボタン](/assets/images/help/repository/edit-branch-protection-rule.png)
+1. ブランチ保護ルールを自由に変更してください。
 1. [**Save changes**] をクリックします。 ![[Edit message] ボタン](/assets/images/help/repository/save-branch-protection-rule.png)
 
-### Deleting a branch protection rule
+### ブランチ保護ルールを削除する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
-1. To the right of the branch protection rule you want to delete, click **Delete**. ![削除ボタン](/assets/images/help/repository/delete-branch-protection-rule.png)
+1. 削除する保護ルールの右にある [**Delete**] をクリックします。 ![削除ボタン](/assets/images/help/repository/delete-branch-protection-rule.png)
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
index 1b5d652d28..b2af643a59 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing auto-merge for pull requests in your repository
-intro: You can allow or disallow auto-merge for pull requests in your repository.
+title: リポジトリ内のプルリクエストの自動マージを管理する
+intro: リポジトリ内のプルリクエストの自動マージを許可または禁止できます。
 product: '{% data reusables.gated-features.auto-merge %}'
 versions:
   free-pro-team: '*'
@@ -13,10 +13,10 @@ topics:
 
 ### 自動マージについて
 
-If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+リポジトリ内でプルリクエストの自動マージを許可すると、書き込み権限を持つユーザは、マージの要件がすべて満たされた際に、リポジトリ内の個々のプルリクエストを、自動的にマージするよう設定できます。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}書き込み権限を持たないユーザが、自動マージが有効なプルリクエストに変更をプッシュすると、そのプルリクエストに対する自動マージが無効となります。 {% endif %}詳しい情報については、「[プルリクエストを自動的にマージする](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)」を参照してください。
 
-### Managing auto-merge
+### 自動マージを管理する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
+1. [Merge button] の下にある [**Allow auto-merge**] を選択または選択解除します。 ![自動マージを許可または禁止するチェックボックス](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md
index 51caf0f6da..dee9bd0d6e 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md
@@ -16,8 +16,8 @@ topics:
 {% data variables.product.product_name %} は、ZIP ファイルと tarball 形式でリポジトリのソースコードアーカイブを作成します。 これらのアーカイブは、リポジトリのメインページ、またはリリースアセットとしてダウンロードできます。 デフォルトでは、{% data variables.large_files.product_name_short %} オブジェクトはこれらのアーカイブに含まれず、これらのオブジェクトへのポインタファイルのみが含まれます。 代わりに {% data variables.large_files.product_name_short %} オブジェクトを含めて、リポジトリのアーカイブを使いやすくすることもできます。
 
 {% if currentVersion == "free-pro-team@latest" %}
-If you choose to include
-{% data variables.large_files.product_name_short %} objects in archives of your repository, every download of those archives will count towards bandwidth usage for your account. 各アカウントには、毎月無料で {% data variables.large_files.initial_bandwidth_quota %} の帯域幅が付与され、追加使用分に対して支払うことができます。 詳しい情報については、「[ストレージと帯域の利用について](/github/managing-large-files/about-storage-and-bandwidth-usage)」および「[{% data variables.large_files.product_name_long %} の支払いを管理する](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)」を参照してください。
+リポジトリのアーカイブに
+{% data variables.large_files.product_name_short %} オブジェクトを含めるようにした場合、それらのアーカイブをダウンロードするたびに、アカウントの帯域幅の使用量にカウントされます。 各アカウントには、毎月無料で {% data variables.large_files.initial_bandwidth_quota %} の帯域幅が付与され、追加使用分に対して支払うことができます。 詳しい情報については、「[ストレージと帯域の利用について](/github/managing-large-files/about-storage-and-bandwidth-usage)」および「[{% data variables.large_files.product_name_long %} の支払いを管理する](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)」を参照してください。
 {% endif %}
 
 ### アーカイブにある {% data variables.large_files.product_name_short %} オブジェクトを管理する
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md
index ffcfcc1d7a..60123da0c8 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-releases-in-a-repository.md
@@ -22,7 +22,7 @@ topics:
 ### リリース管理について
 
 {% if currentVersion == "free-pro-team@latest" %}
-You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. 詳しい情報については、「<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">アクションを {% data variables.product.prodname_marketplace %} で公開する</a>」を参照してください。
+{% data variables.product.prodname_marketplace %} の特定のリリースからのアクションを公開することもできます。 詳しい情報については、「<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">アクションを {% data variables.product.prodname_marketplace %} で公開する</a>」を参照してください。
 {% endif %}
 リポジトリに対して
 
@@ -32,7 +32,7 @@ You can also publish an action from a specific release in {% data variables.prod
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 {% tip %}
 
-**Tip**: You can also manage releases using the {% data variables.product.prodname_cli %}. For more information, see "[`gh release`](https://cli.github.com/manual/gh_release)" in the {% data variables.product.prodname_cli %} documentation.
+**ヒント**: {% data variables.product.prodname_cli %} を使用してリリースを管理することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh release`](https://cli.github.com/manual/gh_release)」を参照してください。
 
 {% endtip %}
 {% endif %}
@@ -48,7 +48,7 @@ You can also publish an action from a specific release in {% data variables.prod
 7. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif)
 8. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png)
 {%- if currentVersion == "free-pro-team@latest" %}
-1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png)
+1. 必要に応じて、[**Create a discussion for this release**] を選択し、[**Category**] ドロップダウンメニューを選択してリリースディスカッションのカテゴリをクリックします。 ![リリースディスカッションを作成するためのチェックボックスと、カテゴリを選択するドロップダウンメニュー](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
 9. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png)
 
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-repository-settings.md b/translations/ja-JP/content/github/administering-a-repository/managing-repository-settings.md
index 72d65d3b85..a8dff17dcb 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-repository-settings.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-repository-settings.md
@@ -1,6 +1,6 @@
 ---
 title: リポジトリ設定を管理する
-intro: 'Repository administrators and organization owners can change settings for a repository, like the name, ownership, and visibility, or delete the repository.'
+intro: リポジトリの管理者と Organization のオーナーは、名前、所有権、可視性などのリポジトリの設定を変更したり、リポジトリを削除したりすることができます。
 mapTopic: true
 redirect_from:
   - /articles/managing-repository-settings
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index 914bee6199..4cbe33a83b 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -16,58 +16,59 @@ topics:
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
-### Enabling or disabling security and analysis features for public repositories
+### パブリックリポジトリのセキュリティおよび分析機能を有効または無効にする
 
-You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning.
+パブリックリポジトリのセキュリティおよび分析機能の、サブセットを管理できます。 依存関係グラフやシークレットスキャニングなど、その他の機能は常時有効になっています。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png)
+4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 ![パブリックリポジトリ内の、[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-public.png)
 {% endif %}
 
-### Enabling or disabling security and analysis features{% if currentVersion == "free-pro-team@latest" %} for private repositories{% endif %}
+### {% if currentVersion == "free-pro-team@latest" %} プライベートレジストリの{% endif %} セキュリティおよび分析機能を有効または無効にする
 
-You can manage the security and analysis features for your {% if currentVersion == "free-pro-team@latest" %}private or internal {% endif %}repository.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %}{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}プライベートおよび内部{% endif %}リポジトリの、セキュリティおよび分析機能を管理できます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Organization が {% data variables.product.prodname_GH_advanced_security %} のライセンスのある Enterprise に所属している場合、追加オプションが利用可能です。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.
-  ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 The control for "
+{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% if currentVersion == "free-pro-team@latest" %}
+  ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
-**Note:** If you disable
+**注釈:**
 
-  {% data variables.product.prodname_GH_advanced_security %}, {% if currentVersion == "free-pro-team@latest" %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail.
+  {% data variables.product.prodname_GH_advanced_security %}を無効にした場合、{% if currentVersion == "free-pro-team@latest" %}依存関係レビュー、{% endif %}{% data variables.product.prodname_secret_scanning %}、および {% data variables.product.prodname_code_scanning %} が無効になります。 あらゆるワークフロー、SARIF のアップロード、{% data variables.product.prodname_code_scanning %} への API の呼び出しが失敗することになります。
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
-4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 Before you can enable "
-{% data variables.product.prodname_secret_scanning %}" for your repository, you need to enable {% data variables.product.prodname_GH_advanced_security %}.
-   ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
+4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 「
+{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.
+   ![リポジトリに対して {% data variables.product.prodname_GH_advanced_security %} または {% data variables.product.prodname_secret_scanning %} を有効化または無効化](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
 ### セキュリティアラートへのアクセスを許可する
 
-After you enable {% if currentVersion != "github-ae@latest" %}{% data variables.product.prodname_dependabot %} or {% endif %}{% data variables.product.prodname_secret_scanning %} alerts for a repository in an organization, organization owners and repository administrators can view the alerts by default. 追加の Team やユーザに、リポジトリのアラートへのアクセスを付与することができます。
+Organization のリポジトリで {% if currentVersion != "github-ae@latest" %}{% data variables.product.prodname_dependabot %} または {% endif %}{% data variables.product.prodname_secret_scanning %} アラートを有効にすると、Organization のオーナーとリポジトリ管理者はデフォルトでアラートを表示できます。 追加の Team やユーザに、リポジトリのアラートへのアクセスを付与することができます。
 
 {% note %}
 
-Organization owners and repository administrators can only grant access to view security alerts, such as {% data variables.product.prodname_secret_scanning %} alerts, to people or teams who have write access to the repo.
+Organizationのオーナーとリポジトリ管理者は、リポジトリへの書き込みアクセスを持つユーザまたは Team に対して、{% data variables.product.prodname_secret_scanning %} アラートなどのセキュリティアラートを表示する権限のみを付与できます。
 
 {% endnote %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.
+4. [Access to alerts] の検索フィールドで、検索するユーザまたは Team 名の入力を開始し、リストから一致する名前をクリックします。
    {% if currentVersion == "free-pro-team@latest" %}
    ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
@@ -91,7 +92,7 @@ Organization owners and repository administrators can only grant access to view
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click
+4. [Access to alerts] で、アクセスを削除するユーザまたは Team の右側にある
 {% octicon "x" aria-label="X symbol" %}.
    {% if currentVersion == "free-pro-team@latest" %}
    ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index b9c0af50b3..bee1e7fa5b 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ topics:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. [Manage access] でアクセスを削除する Team またはユーザーを探し、{% octicon "trashcan" aria-label="The trashcan icon" %} をクリックします。 ![アクセス削除用のゴミ箱アイコン](/assets/images/help/repository/manage-access-remove.png)
+4. [Manage access] でアクセスを削除する Team またはユーザーを探し、{% octicon "trash" aria-label="The trash icon" %} をクリックします。 ![アクセス削除用のゴミ箱アイコン](/assets/images/help/repository/manage-access-remove.png)
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
index 6f316793e0..d19acc4630 100644
--- a/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
 title: リポジトリのフォークポリシーを管理する
-intro: 'You can allow or prevent the forking of a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or internal{% endif %} repository owned by an organization.'
+intro: 'Organization が所有する、特定のプライベート{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}および内部{% endif %}リポジトリのフォークを許可または禁止できます。'
 redirect_from:
   - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization
   - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization
@@ -13,7 +13,7 @@ topics:
   - Repositories
 ---
 
-An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. 詳細は「[Organization のフォークポリシーを管理する](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」を参照してください。
+Organization のオーナーは、特定のリポジトリのフォークを許可または禁止する前に、Organization レベルでプライベート{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}および内部{% endif %}リポジトリのフォークを許可する必要があります。 詳細は「[Organization のフォークポリシーを管理する](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」を参照してください。
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
diff --git a/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md b/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md
index 4b22add6cd..c98e21c5c8 100644
--- a/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/ja-JP/content/github/administering-a-repository/renaming-a-branch.md
@@ -1,6 +1,6 @@
 ---
-title: Renaming a branch
-intro: You can change the name of a branch in a repository.
+title: ブランチの名前を変更する
+intro: リポジトリにあるブランチの名前を変更できます。
 permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch.
 versions:
   free-pro-team: '*'
@@ -9,30 +9,38 @@ topics:
   - Repositories
 ---
 
-### About renaming branches
+### ブランチの名前変更について
 
-You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)."
+{% data variables.product.product_location %} にあるリポジトリのブランチの名前を変更できます。 ブランチ関する詳しい情報については、「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches)」を参照してください。
 
-When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments.
+{% data variables.product.product_location %} 上のブランチ名を変更すると、古いブランチ名を含む URL は、名前を変更したブランチの URL に自動的にリダイレクトされます。 ブランチ保護ポリシー、オープンなプルリクエストのベースブランチ (フォーク含む) およびドラフトリリースも更新されます。 名前の変更が完了すると、{% data variables.product.prodname_dotcom %} は、リポジトリのホームページに、コントリビューターにローカルの Git 環境を更新するよう指示を掲載します。
 
-Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
+ファイル URL は自動的にリダイレクトされますが、生のファイル URL はリダイレクトされません。 また、ユーザが以前のブランチ名に対して `git pull` を実行した場合、{% data variables.product.prodname_dotcom %} はリダイレクトを行いません。
 
-### Renaming a branch
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+
+### ブランチの名前を変更する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png)
-1. Type a new name for the branch. ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png)
-1. Review the information about local environments, then click **Rename branch**. ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png)
+1. ブランチのリストで、名前を変更するブランチの右にある {% octicon "pencil" aria-label="The edit icon" %} をクリックします。 ![名前を変更するブランチの右にある鉛筆アイコン](/assets/images/help/branch/branch-rename-edit.png)
+1. ブランチの新しい名前を入力します。 ![新しいブランチ名を入力するためのテキストフィールド](/assets/images/help/branch/branch-rename-type.png)
+1. ローカル環境についての情報を確認し、[**Rename branch**] をクリックします。 ![ローカル環境情報と [Rename branch] ボタン](/assets/images/help/branch/branch-rename-rename.png)
 
-### Updating a local clone after a branch name changes
+### ブランチ名の変更後にローカルクローンを更新する
 
-After you rename a branch in a repository on {% data variables.product.product_name %}, any collaborator with a local clone of the repository will need to update the clone.
+{% data variables.product.product_name %} 上のリポジトリにあるブランチ名の変更後、そのリポジトリのローカルクローンのコラボレータは、クローンを更新する必要があります。
 
-From the local clone of the repository on a computer, run the following commands to update the name of the default branch.
+コンピュータ上にあるリポジトリのローカルクローンから、以下のコマンドを実行してデフォルトブランチ名を更新します。
 
 ```shell
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+必要に応じて次のコマンドを実行し、古いブランチ名への追跡参照を削除します。
+```
+$ git remote prune origin
 ```
diff --git a/translations/ja-JP/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/ja-JP/content/github/administering-a-repository/restoring-a-deleted-repository.md
index 1072439cb0..8ad220e331 100644
--- a/translations/ja-JP/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -19,7 +19,7 @@ topics:
 
 削除したリポジトリが復元できるようになるまでには、最大で1時間かかる場合があります。
 
-リポジトリを復元しても、リリース添付ファイルやチーム権限は復元されません。 Issues that are restored will not be labeled.
+リポジトリを復元しても、リリース添付ファイルやチーム権限は復元されません。 復元された Issue はラベル付けされません。
 
 ### ユーザアカウントが所有していて削除したリポジトリを復元する
 
@@ -31,9 +31,9 @@ topics:
 
 ### Organizationが所有していて削除したリポジトリを復元する
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/transferring-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/transferring-a-repository.md
index 21e601852a..965b74ad79 100644
--- a/translations/ja-JP/content/github/administering-a-repository/transferring-a-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/transferring-a-repository.md
@@ -24,14 +24,14 @@ topics:
 
 リポジトリを新たなオーナーに移譲すると、そのオーナーはすぐにリポジトリの内容、Issue、プルリクエスト、リリース、プロジェクトボード、そして設定を管理できるようになります。
 
-Prerequisites for repository transfers: {% if currentVersion == "free-pro-team@latest" %}
+リポジトリを移譲するための必須条件は以下の通りです。{% if currentVersion == "free-pro-team@latest" %}
 - 自分が所有しているリポジトリを他のユーザアカウントに移譲すると、新しい所有者に確認メールが届きます。 確認メールには、移譲を受け入れるための指示が書かれています。 新しいオーナーが移譲を 1 日以内に受け入れなければ、招待は期限切れになります。{% endif %}
 - 自分が所有しているリポジトリを Organization に移譲するには、対象 Organization のリポジトリを作成する権限が必要です。
 - ターゲットのアカウントは、同じ名前のリポジトリを持っていたり、同じネットワーク内にフォークを持っていたりしてはなりません。
 - リポジトリのオリジナルのオーナーは、移譲されたリポジトリにコラボレーターとして追加されます。 他のコラボレーターは、移譲されたリポジトリにそのまま残されます。
 - プライベートフォークは移譲できません。
 
-{% if currentVersion == "free-pro-team@latest" %}If you transfer a private repository to a {% data variables.product.prodname_free_user %} user or organization account, the repository will lose access to features like protected branches and {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}プライベートリポジトリを {% data variables.product.prodname_free_user %} ユーザまたは Organization アカウントに移譲すると、リポジトリは保護されたブランチや {% data variables.product.prodname_pages %} などの機能にアクセスできなくなります。 {% data reusables.gated-features.more-info %}{% endif %}
 
 #### リポジトリと共に移譲されるものは？
 
@@ -39,7 +39,7 @@ Prerequisites for repository transfers: {% if currentVersion == "free-pro-team@l
 
 - 移譲されたリポジトリがフォークである場合、それは上流のリポジトリに関連付けられたままになります。
 - 移譲されたリポジトリにフォークがある場合、それらのフォークは移譲が完了した後リポジトリに関連付けられたままになります。
-- 移譲されたリポジトリが {% data variables.large_files.product_name_long %} を使う場合、すべての {% data variables.large_files.product_name_short %} オブジェクトは自動的に移動します。 This transfer occurs in the background, so if you have a large number of {% data variables.large_files.product_name_short %} objects or if the {% data variables.large_files.product_name_short %} objects themselves are large, it may take some time for the transfer to occur.{% if currentVersion == "free-pro-team@latest" %} Before you transfer a repository that uses {% data variables.large_files.product_name_short %}, make sure the receiving account has enough data packs to store the {% data variables.large_files.product_name_short %} objects you'll be moving over. ユーザアカウントにストレージを追加する方法の詳細については、「[{% data variables.large_files.product_name_long %} をアップグレードする](/articles/upgrading-git-large-file-storage)」を参照してください。{% endif %}
+- 移譲されたリポジトリが {% data variables.large_files.product_name_long %} を使う場合、すべての {% data variables.large_files.product_name_short %} オブジェクトは自動的に移動します。 この移譲はバックグラウンドで行われます。そのため、多数の {% data variables.large_files.product_name_short %} オブジェクトがあるか、{% data variables.large_files.product_name_short %} オブジェクト自体が大容量である場合、移譲には時間がかかることがあります。{% if currentVersion == "free-pro-team@latest" %}{% data variables.large_files.product_name_short %} を利用するリポジトリを移譲する前に、受信側のアカウントが、移動する {% data variables.large_files.product_name_short %} オブジェクトを保存するために十分なデータパックを所有していることを確認してください。 ユーザアカウントにストレージを追加する方法の詳細については、「[{% data variables.large_files.product_name_long %} をアップグレードする](/articles/upgrading-git-large-file-storage)」を参照してください。{% endif %}
 - リポジトリを 2 つのユーザアカウント間で移譲する場合、Issue の割り当てはそのまま残ります。 ユーザアカウントから Organization にリポジトリを移譲する場合、Organization のメンバーにアサインされた Issue はそのまま残ります。そして、すべての他の Issue のアサイニーは消えます。 Organization の中のオーナーだけが、新しい Issue のアサインを作成できます。 Organization からユーザアカウントにリポジトリを移譲する場合、リポジトリのオーナーにアサインされた Issue だけが保管され、すべての他のアサイニーは削除されます。
 - 移譲されたリポジトリが {% data variables.product.prodname_pages %} サイトを含む場合、Web 上の Git リポジトリへのリンクや Git のアクティビティを通じたリンクはリダイレクトされます。 しかし、リポジトリに関連付けられている {% data variables.product.prodname_pages %} はリダイレクトされません。
 - 以前のリポジトリの場所へのすべてのリンクは、新しい場所へ自動的にリダイレクトされます。 移譲されたリポジトリ上で `git clone`、`git fetch`、または `git push` を使う場合には、これらのコマンドは新しいリポジトリの場所あるいは URL にリダイレクトされます。 しかし、混乱を避けるため、既存のローカルクローンは新しいリポジトリの URL を指すよう更新することを強くおすすめします。 それは `git remote` をコマンドライン上で使って行えます。
@@ -60,7 +60,7 @@ Organization にリポジトリが移譲されたら、Organization のデフォ
 
 リポジトリの移譲を受け入れるどのユーザアカウントにも、リポジトリを移譲できます。 ２つのユーザアカウントの間でリポジトリを移譲した場合、当初のリポジトリコードオーナーとコラボレーターは、新しいリポジトリにコラボレーターとして自動的に追加されます。
 
-{% if currentVersion == "free-pro-team@latest" %}If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, before transferring the repository, you may want to remove or update your DNS records to avoid the risk of a domain takeover. 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}プライベートリポジトリに {% data variables.product.prodname_pages %} サイトを公開し、カスタムドメインを追加した場合、ドメイン乗っ取りのリスクを回避するため、DNS レコードを削除するか更新することをおすすめします。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md
index f152009758..db54cbf20c 100644
--- a/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md
+++ b/translations/ja-JP/content/github/administering-a-repository/troubleshooting-required-status-checks.md
@@ -1,6 +1,6 @@
 ---
 title: 必須ステータスチェックのトラブルシューティング
-intro: You can check for common errors and resolve issues with required status checks.
+intro: ステータスチェック必須を使用して、一般的なエラーを調べ、問題を解決できます。
 product: '{% data reusables.gated-features.protected-branches %}'
 versions:
   free-pro-team: '*'
@@ -10,9 +10,9 @@ topics:
   - Repositories
 ---
 
-If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. 詳しい情報については、「[チェック](/rest/reference/checks)」を参照してください。
+同じ名前のチェックとステータスがあり、その名前をステータスチェック必須とするようにした場合、チェックとステータスはどちらも必須になります。 詳しい情報については、「[チェック](/rest/reference/checks)」を参照してください。
 
-After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. これによって、ブランチがベースブランチからの最新のコードでテストされたことが保証されます。 ブランチが古い場合、ベースブランチをブランチにマージする必要があります。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
+ステータスチェック必須を有効にした後、マージする前にブランチをベースブランチに対して最新にする必要がある場合があります。 これによって、ブランチがベースブランチからの最新のコードでテストされたことが保証されます。 ブランチが古い場合、ベースブランチをブランチにマージする必要があります。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
 
 {% note %}
 
@@ -28,13 +28,13 @@ remote: error: Required status check "ci-build" is failing
 ```
 {% note %}
 
-**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. これはマージコミット自体でステータスチェックを実行せずに行えます。
+**注釈:** 最新で必須のステータスチェックをパスしたプルリクエストは、ローカルでマージしてから保護されたブランチにプッシュできます。 これはマージコミット自体でステータスチェックを実行せずに行えます。
 
 {% endnote %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
 
-テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 If the test merge commit has a status, the test merge commit must pass. それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)."
+テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 テストマージコミットにステータスがある場合、そのテストマージコミットは必ずパスする必要があります。 それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 テストマージコミットに関する詳しい情報については、「[プル](/rest/reference/pulls#get-a-pull-request)」を参照してください。
 
 ![マージコミットが競合しているブランチ](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
 {% endif %}
diff --git a/translations/ja-JP/content/github/administering-a-repository/viewing-branches-in-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/viewing-branches-in-your-repository.md
index 86aa5c7ea3..641c7c3675 100644
--- a/translations/ja-JP/content/github/administering-a-repository/viewing-branches-in-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/viewing-branches-in-your-repository.md
@@ -19,7 +19,7 @@ topics:
     - **Stale branches**: [**Stale**] ビューには、過去 3 か月間に誰もコミットしていないブランチが、最も古いコミットがあるブランチから順にすべて表示されます。 このリストを使用して、[どのブランチを削除するか](/articles/creating-and-deleting-branches-within-your-repository)を決定します。
     - **All branches**: [**All**] ビューには、デフォルトブランチが表示され、続いて最新のコミットがあるブランチから順に他のすべてのブランチが表示されます。
 
-4. Optionally, use the search field on the top right. It provides a simple, case-insensitive, sub-string search on the branch name. It does not support any additional query syntax.
+4. 必要に応じて、右上の検索フィールドを使用します。 このフィールドでは単純に、大文字と小文字を区別しない、ブランチ名の部分一致検索を行うことができます。 その他のクエリ構文はサポートしていません。
 
 ![Atom リポジトリのブランチページ](/assets/images/help/branches/branches-overview-atom.png)
 
diff --git a/translations/ja-JP/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index ce35ddba75..28a087607c 100644
--- a/translations/ja-JP/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/ja-JP/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ topics:
 ### デプロイメントダッシュボードを表示する
 
 {% data reusables.repositories.navigate-to-repo %}
-2. ファイルの一覧の上にある [**Environments**] をクリックします。 ![リポジトリページ上部の [Environments]](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### 参考リンク
  - [プルリクエストについて](/articles/about-pull-requests)
diff --git a/translations/ja-JP/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md b/translations/ja-JP/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md
index 1996f28a27..271b741012 100644
--- a/translations/ja-JP/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md
+++ b/translations/ja-JP/content/github/administering-a-repository/viewing-your-repositorys-releases-and-tags.md
@@ -16,7 +16,7 @@ topics:
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 {% tip %}
 
-**Tip**: You can also view a release using the {% data variables.product.prodname_cli %}. For more information, see "[`gh release view`](https://cli.github.com/manual/gh_release_view)" in the {% data variables.product.prodname_cli %} documentation.
+**ヒント**: {% data variables.product.prodname_cli %} を使用してリリースを表示することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh release view`](https://cli.github.com/manual/gh_release_view)」を参照してください。
 
 {% endtip %}
 {% endif %}
diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..155e6fa74c
--- /dev/null
+++ b/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+画像をホストするために、{% data variables.product.product_name %}は[オープンソースプロジェクトの Camo](https://github.com/atmos/camo) を使用します。 Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. URL は `https://<subdomain>.githubusercontent.com/` で始まり、画像のアップロード方法に応じて異なるサブドメインがあります。
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Camoでの問題のトラブルシューティング
+
+まれな状況下において、Camoによって処理された画像が{% data variables.product.prodname_dotcom %}に表示されないことがあります。 問題のありかを判断するために利用できる手順を以下に示します。
+
+{% windows %}
+
+{% tip %}
+
+Windowsユーザは、Git Powershell（これは[{% data variables.product.prodname_desktop %}](https://desktop.github.com/)と共にインストールされます）を使うか、[curl for Windows](http://curl.haxx.se/download.html)をダウンロードする必要があります。
+
+{% endtip %}
+
+{% endwindows %}
+
+#### 画像が表示されない
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. `curl` を使って画像ヘッダをリクエストしてください。
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. `Content-Type` の値を確認してください。 ここでは `image/x-png` です。
+4. コンテントタイプは[Camo がサポートするタイプのリスト](https://github.com/atmos/camo/blob/master/mime-types.json)で確認してください。
+
+コンテントタイプが Camo でサポートされていない場合、試せることがいくつかあります:
+  * 画像をホストしているサーバーを自分で所有しているなら、画像の適切なコンテントタイプを返すように修正してください。
+  * 画像を外部のサービスでホストしているなら、そのサービスのサポートに連絡してください。
+  * Camo にプルリクエストを送り、コンテントタイプをリストに追加してもらってください。
+
+#### 最近変更した画像が更新されない
+
+最近変更した画像がブラウザでは表示され、{% data variables.product.prodname_dotcom %}では表示されない場合、その画像のキャッシュをリセットしてみることができます。
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. `curl` を使って画像ヘッダをリクエストしてください。
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+`Cache-Control`の値を確認してください。 この例では`Cache-Control`はありません。 その場合:
+  * 画像をホストしているサーバを自分で保有しているなら、画像に対する `Cache-Control` に `no-cache` を返すように修正してください。
+  * 画像を外部のサービスでホストしているなら、そのサービスのサポートに連絡してください。
+
+ `Cache-Control` *が* `no-cache` に設定されている場合は、{% data variables.contact.contact_support %} にお問い合わせいただくか、{% data variables.contact.community_support_forum %} を検索してください。
+
+#### Camoのキャッシュから画像を削除する
+
+キャッシュをパージすれば、すべての{% data variables.product.prodname_dotcom %}ユーザは画像をリクエストし直すようになるので、この方法はごく控えめに使うべきであり、これまでに述べたステップがうまく働かなかった場合にかぎるべきです。
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Camo の URL に対して `curl -X PURGE` を使い、画像をパージしてください。
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### プライベートネットワークでの画像の表示
+
+画像がプライベートネットワークや、認証を要求するサーバから提供されている場合、{% data variables.product.prodname_dotcom %}では表示できません。 実際のところ、その画像はユーザにサーバへのログインを求めなければ表示されません。
+
+この問題を修正するには、その画像をパブリックにアクセスできるサービスに移してください。
+
+### 参考リンク
+
+- {% data variables.product.prodname_blog %}の[ユーザの画像のプロキシ処理](https://github.com/blog/1766-proxying-user-images)
diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md
index 5a96ab357e..21dd8a281e 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md
@@ -48,7 +48,7 @@ IdP を使用して、ブラウザ {% if currentVersion == "github-ae@latest" %}
 
 ### コマンドラインで認証する
 
-コマンドラインから {% data variables.product.product_name %} のリポジトリにアクセスするには、HTTPS と SSH の 2 つの方法がありますが、それぞれ認証方法が異なります。 認証方法は、リポジトリのクローンを作成するときに HTTPS または SSH リモート URL を選択したかどうかに基づいて決まります。 For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+コマンドラインから {% data variables.product.product_name %} のリポジトリにアクセスするには、HTTPS と SSH の 2 つの方法がありますが、それぞれ認証方法が異なります。 認証方法は、リポジトリのクローンを作成するときに HTTPS または SSH リモート URL を選択したかどうかに基づいて決まります。 アクセス方法の詳細については、「[リモートリポジトリについて](/github/getting-started-with-github/about-remote-repositories)」を参照してください。
 
 * ファイアウォールまたはプロキシの内側からでも、HTTPS を介して {% data variables.product.product_name %} 上のすべてのリポジトリを操作できます。 Git を使用して {% data variables.product.product_name %} で認証するたびに[認証情報ヘルパー](/github/getting-started-with-github/caching-your-github-credentials-in-git)でキャッシュしない限り、{% data variables.product.product_name %} で認証するための資格情報を入力するように求められます。 {% data reusables.user_settings.password-authentication-deprecation %}
 
@@ -58,16 +58,16 @@ IdP を使用して、ブラウザ {% if currentVersion == "github-ae@latest" %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 
-### {% data variables.product.company_short %}'s token formats
+### {% data variables.product.company_short %} のトークンフォーマット
 
-{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type.
+{% data variables.product.company_short %} は、トークンの種別を示すプレフィックスで始まるトークンを発行します。
 
-| Token type                                                                      | Prefix | 詳細情報                                                                                                                                                              |
-|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 個人アクセストークン                                                                      | `ghp_` | [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)                                                                              |
-| OAuth access token                                                              | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)"                                                       |
-| User-to-server token for a {% data variables.product.prodname_github_app %}   | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
-| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)"   |
-| Refresh token for a {% data variables.product.prodname_github_app %}          | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)"                                                             |
+| トークン種別                                                               | プレフィックス | 詳細情報                                                                                                                                              |
+|:-------------------------------------------------------------------- |:------- |:------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 個人アクセストークン                                                           | `ghp_`  | [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)                                                              |
+| OAuth アクセストークン                                                       | `gho_`  | 「[{% data variables.product.prodname_oauth_apps %} を認可する](/developers/apps/authorizing-oauth-apps)」                                             |
+| {% data variables.product.prodname_github_app %} のユーザからサーバーへのトークン  | `ghu_`  | 「[{% data variables.product.prodname_github_apps %} のユーザの特定と認可](/developers/apps/identifying-and-authorizing-users-for-github-apps)」            |
+| {% data variables.product.prodname_github_app %} のサーバーからサーバーへのトークン | `ghs_`  | 「[{% data variables.product.prodname_github_apps %} で認証する](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)」 |
+| {% data variables.product.prodname_github_app %} のトークンのリフレッシュ      | `ghr_`  | 「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/developers/apps/refreshing-user-to-server-access-tokens)」                                                      |
 
 {% endif %}
diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md
index 5c99bf3a74..36cf437967 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: コミット署名の検証について
-intro: 'GPG または S/MIME を使用して、タグに署名し、ローカルでコミットできます。 それらのタグやコミットは検証済みとして {% data variables.product.product_name %}上でマークされ、他の人々がその変更が信頼できるソースから来たものと信頼できるようになります。'
+intro: 'GPG または S/MIME を使用して、タグに署名し、ローカルでコミットできます。 これらのタグやコミットは {% data variables.product.product_name %} で検証済みとしてマークされているため、他のユーザはその変更が信頼できるソースからのものであると確信できます。'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures/
   - /articles/about-gpg/
@@ -16,15 +16,35 @@ topics:
 
 ### コミット署名の検証について
 
-コミットやタグをローカルで署名して、他の人々がその作業が信頼されるソースから来たことを検証できるようにすることができます。 コミットまたはタグが暗号的に検証可能な GPG または S/MIME 署名を持っている場合、{% data variables.product.product_name %} はそのコミットまたはタグを検証済みとしてマークします。
+コミットとタグにローカルで署名して、行った変更の根拠を他のユーザに信頼してもらうことができます。 コミットまたはタグに暗号で検証可能な GPG または S/MIME 署名がある場合、GitHub はコミットまたはタグに{% if currentVersion == "free-pro-team@latest" %}「Verified」または「Partially verified」{% else %}「Verified」のマークを付けます。{% endif %}
 
 ![検証されたコミット](/assets/images/help/commits/verified-commit.png)
 
-コミットあるいはタグが検証できない署名を持っている場合、{% data variables.product.product_name %} はそのコミットあるいはタグを未検証としてマークします。
+{% if currentVersion == "free-pro-team@latest" %}
+コミットとタグには、警戒モードを有効にしているかどうかによって、次の検証ステータスが含まれます。 デフォルト設定では、警戒モードは有効になっていません。 警戒モードを有効にする方法については、「[すべてのコミットの検証ステータスを表示する](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)」を参照してください。
 
-リポジトリ管理者は、ブランチでコミット署名を必須として、署名および検証されていないすべてのコミットをブロックできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-signed-commits)を参照してください。
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
-{% data variables.product.product_name %}上の署名されたコミットあるいはタグの検証ステータスをチェックして、コミットの署名が検証されない理由を見ることができます。 詳細は「[コミットおよびタグの署名の検証のステータスをチェックする](/articles/checking-your-commit-and-tag-signature-verification-status)」を参照してください。
+#### デフォルトのステータス
+
+| 状況                     | 説明                            |
+| ---------------------- | ----------------------------- |
+| **検証済み**               | コミットが署名され、署名が正常に検証されました。      |
+| **Unverified**         | コミットは署名されていますが、署名を検証できませんでした。 |
+| No verification status | コミットが署名されていません。               |
+
+#### 警戒モードが有効になっているステータス
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+コミットまたはタグに検証できない署名がある場合、
+{% data variables.product.product_name %} はコミットまたはタグに「Unverified」のマークを付けます。
+{% endif %}
+
+リポジトリ管理者は、ブランチでコミット署名を必須として、署名および検証されていないすべてのコミットをブロックできます。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-signed-commits)」を参照してください。
+
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} は GPG を自動的に使用して、{% data variables.product.product_name %} Web インターフェースを使用して行ったコミットに署名します。ただし、作者ではないプルリクエストを squash してマージする場合は除きます。 オプションとして、{% data variables.product.prodname_codespaces %} で行ったコミットを {% data variables.product.product_name %} で署名させることもできます。 {% data variables.product.product_name %}によって署名されたコミットは、{% data variables.product.product_name %}で認証済みのステータスになります。 署名は、https://github.com/web-flow.gpgから利用できる公開鍵を使ってローカルに検証できます。 Codespaces の GPG 検証を有効にする方法については、「[{% data variables.product.prodname_codespaces %} の GPG 検証の管理](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)」を参照してください。
diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md b/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md
index 5372a9b9f4..1ae368aea5 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-SSH をセットアップする際には、[SSH キーを生成し、ssh-agent に追加](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)し、それから [ キーを自分の {% data variables.product.product_name %}アカウントに追加](/articles/adding-a-new-ssh-key-to-your-github-account)します。 SSH キーを ssh-agent に追加することで、パスフレーズの利用を通じて SSH キーに追加のセキュリティのレイヤーを持たせることができます。 詳しい情報については[SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases)を参照してください。
+When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
-{% if currentVersion == "free-pro-team@latest" %} SAML シングルサインオンを利用している Organization が所有するリポジトリで SSH キーを使用するには、まずはそのキーを認証する必要があります。 詳しい情報については、「[SAML シングルサインオンで使うために SSH キーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
+You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. 詳しい情報については[SSH キーのパスフレーズを使う](/github/authenticating-to-github/working-with-ssh-key-passphrases)を参照してください。
 
-定期的に [SSH キーのリストをレビュー](/articles/reviewing-your-ssh-keys)し、不正になったものや悪用されたものを取り除くことをおすすめします。
+{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. 詳しい情報については、「[SAML シングルサインオンで使うために SSH キーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
+
+To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. 詳細は「[SSH キーをレビューする](/github/authenticating-to-github/reviewing-your-ssh-keys)」を参照してください。
 
 {% if currentVersion == "free-pro-team@latest" %}
 SSH キーを 1 年間使用していない場合、
@@ -28,8 +30,4 @@ SSH 証明書を提供する Organization のメンバーである場合、{% da
 
 - [既存の SSH キーのチェック](/articles/checking-for-existing-ssh-keys)
 - [SSH コネクションのテスト](/articles/testing-your-ssh-connection)
-- [SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases)
 - [SSH のトラブルシューティング](/articles/troubleshooting-ssh)
-{%- if currentVersion == "free-pro-team@latest" %}
-- [SAML シングルサインオンで使うためにSSHキーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)
-{%- endif %}
diff --git a/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index f9e7e83e96..eab79a5d65 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ topics:
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**ヒント**: {% data variables.product.prodname_cli %} を使用して SSH キーを追加することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)」を参照してください。
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. SSH 公開鍵をクリップボードにコピーします。
@@ -80,8 +88,9 @@ topics:
   SSH 公開鍵のファイル名がサンプルコードと異なる場合は、現在の設定に一致するようにファイル名を変更してください。 キーをコピーする際には、改行や空白を追加しないでください。
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
-  # xclip をダウンロードしてインストールします。 If you don't have `apt-get`, you might need to use another installer (like `yum`)
+  # xclip をダウンロードしてインストールする。 「apt-get」がない場合は、別のインストーラー (「 yum」など) を使用する必要がある
 
   $ xclip -selection clipboard &lt; ~/.ssh/id_ed25519.pub
   # id_ed25519.pub ファイルの内容をクリップボードにコピーする
diff --git a/translations/ja-JP/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/ja-JP/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index 65312c5560..45bbde6333 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**メモ:** OS X や Windows では、GPG はデフォルトではインストールされていません。 GPG コマンドラインツールをインストールするには、[GnuPG のダウンロードページ](https://www.gnupg.org/download/)を参照してください。
+**注釈:** デフォルト設定では、macOS や Windows に GPG はインストールされていません。 GPG コマンドラインツールをインストールするには、[GnuPG のダウンロードページ](https://www.gnupg.org/download/)を参照してください。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index ecb740a7a6..7015f79eb8 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %} 上で、プルリクエストに移動します。
 {% data reusables.repositories.review-pr-commits %}
-3. コミットの短縮版コミットハッシュの隣に、コミットの署名が検証されているかどうかを示すボックスがあります。 ![署名されたコミット](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. コミットの署名について詳しい情報を表示するには、[**Verified**] または [**Unverified**] をクリックします。 ![検証された署名済みコミット](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-コミットの署名が検証されていない場合、[**Unverified**] のボックスをクリックするとその理由について詳しく知ることができます。 ![検証されていない署名済みコミット](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. コミットの省略されたコミットハッシュの横に、コミット署名が検証済みか{% if currentVersion == "free-pro-team@latest" %}、部分的に検証済みか、{% endif %}未検証かを示すボックスがあります。 ![署名されたコミット](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. コミットシグニチャの詳細情報を表示するには、[**検証済み**]{% if currentVersion == "free-pro-team@latest" %}、[**部分的に検証済み**]、{% endif %}または [**未検証**] をクリックします。 ![検証された署名済みコミット](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### タグの署名検証のステータスの確認
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. [Releases] ページの上部にある [**Tags**] をクリックします。 ![[Tags] ページ](/assets/images/help/releases/tags-list.png)
-3. タグの説明の隣に、タグの署名が検証されているかどうかを示すボックスがあります。 ![検証されたタグ署名](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. タグの署名について詳しい情報を表示するには、[**Verified**] または [**Unverified**] をクリックします。 タグの署名が検証されていない場合、[**Unverified**] のボックスをクリックするとその理由について詳しく知ることができます。 ![検証された署名済みタグ](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. タグの説明の横に、タグの署名が検証済みか{% if currentVersion == "free-pro-team@latest" %}、部分的に検証済みか{% endif %}、未検証かを示すボックスがあります。 ![検証されたタグ署名](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. タグシグニチャの詳細情報を表示するには、[**検証済み**]{% if currentVersion == "free-pro-team@latest" %}、[**部分的に検証済み**]、{% endif %}または [**未検証**] をクリックします。 ![検証された署名済みタグ](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md
index a0b326e606..db4a0e1f35 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 個人アクセストークン（PAT）は、[GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) または[コマンドライン](#using-a-token-on-the-command-line)を使用するときに {% data variables.product.product_name %} への認証でパスワードの代わりに使用できます。
 
-{% if currentVersion == "free-pro-team@latest" %}PAT を使用して、SAML SSO を使用する Organization が所有するリソースにアクセスする場合は、PAT を認証する必要があります。 詳しい情報については「[SAMLシングルサインオンでの認証について](/articles/about-authentication-with-saml-single-sign-on)」及び「[SAMLシングルサインオンで利用する個人アクセストークンの認可](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}PAT を使用して、SAML SSO を使用する Organization が所有するリソースにアクセスする場合は、PAT を認証する必要があります。 詳しい情報については「[SAMLシングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」及び「[SAMLシングルサインオンで利用する個人アクセストークンの認可](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### トークンの作成
 
-{% if currentVersion == "free-pro-team@latest" %}1. まだ検証していない場合は[メールアドレスを検証](/articles/verifying-your-email-address)します。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. まだ検証していない場合は[メールアドレスを検証](/github/getting-started-with-github/verifying-your-email-address)します。{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -36,21 +36,21 @@ topics:
    ![トークンスコープの選択](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
    {% endif %}
 7. [**Generate token**] をクリックします。 ![[Generate token] ボタン](/assets/images/help/settings/generate_token.png)
-8. {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again.
+8. {% octicon "clippy" aria-label="The copy to clipboard icon" %} を使用して、トークンをクリップボードにコピーします。 セキュリティ上の理由から、ページから移動した後は、トークンを再度表示することはできません。
    {% if currentVersion == "free-pro-team@latest" %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![新しく作成されたトークン](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png)
+   ![新しく作成されたトークン](/assets/images/help/settings/personal_access_tokens_ghe.png)
    {% else %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
+   ![新しく作成されたトークン](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **警告:** トークンはパスワードのように扱い、秘密にしてください。 API を操作する場合は、トークンをプログラムにハードコーディングするのではなく、環境変数として使用してください。
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. SAML SSO を使用する Organization への認証にトークンを使用するには、[Organization への SAML シングルサインオンに使用できるようトークンを認証します](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. SAML SSO を使用する Organization への認証にトークンを使用するには、[Organization への SAML シングルサインオンに使用できるようトークンを認証します](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。{% endif %}
 
 ### コマンドラインでトークンを使用する
 
@@ -58,7 +58,7 @@ topics:
 
 個人アクセストークンは HTTPS Git 操作だけにしか使用できません。 SSH リモート URL を使用するリポジトリの場合、[リモートを SSH から HTTPS に切り替える](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https)必要があります。
 
-ユーザ名とパスワードの入力を求められない場合、資格情報がコンピュータにキャッシュされている可能性があります。 古いパスワードをトークンに交換するよう[キーチェーンで資格情報を更新](/articles/updating-credentials-from-the-osx-keychain)できます。
+ユーザ名とパスワードの入力を求められない場合、資格情報がコンピュータにキャッシュされている可能性があります。 古いパスワードをトークンに交換するよう[キーチェーンで資格情報を更新](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain)できます。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/ja-JP/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..c378af750f
--- /dev/null
+++ b/translations/ja-JP/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: すべてのコミットの検証ステータスを表示する
+shortTitle: すべてのコミットの検証を表示
+intro: コミット署名検証の警戒モードを有効にして、すべてのコミットとタグに署名検証ステータスのマークを付けることができます。
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### 警戒モードについて
+
+コンピューターでローカルで作業する場合、Git を使用すると、変更の作者とコミッターのアイデンティティを設定できます。 これにより、他のユーザが、自分が作成したコミットとタグが実際に自分によって作成されたものであると確信することが困難になる可能性があります。 この問題を解決するため、コミットとタグに署名することができます。 詳しい情報については、「[コミットに署名する](/github/authenticating-to-github/signing-commits)」および「[タグに署名する](/github/authenticating-to-github/signing-tags)」を参照してください。 {% data variables.product.prodname_dotcom %} は、署名されたコミットとタグに検証ステータスのマークを付けます。
+
+デフォルトでは、コミットとタグは、正常に検証された GPG または S/MIME キーで署名されている場合、「検証済み」としてマークされます。 コミットまたはタグに検証できない署名がある場合、{% data variables.product.prodname_dotcom %} はコミットまたはタグを「未検証」としてマークします。 それ以外の場合、検証ステータスは表示されません。
+
+ただし、{% data variables.product.prodname_dotcom %} 設定で警戒モードを有効にすることで、他のユーザにコミットとタグに起因するアイデンティティの信頼性を高めることができます。 警戒モードを有効にすると、すべてのコミットとタグに 3 つの検証ステータスのいずれかがマークされます。
+
+![署名の検証ステータス](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+すべてのコミットとタグに署名する場合にのみ、警戒モードを有効にする必要があります。 このモードを有効にすると、ローカルで生成して {% data variables.product.prodname_dotcom %} にプッシュする署名されていないコミットまたはタグは、「未検証」としてマークされます。
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### 警戒モードの有効化
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. [SSH Settings] ページの [Vigilant mode] で、[**Flag unsigned commits as unverified**] を選択します。
+
+   ![署名されていないコミットを未検証のチェックボックスとしてフラグを立てる](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/ja-JP/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/ja-JP/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..19d51b6f01
--- /dev/null
+++ b/translations/ja-JP/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### 必要な環境
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### 問題の解決
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. ターミナルを開きます。
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. 詳しい情報については、「[新しい SSH キーを生成して ssh-agent に追加する](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)」を参照してください。
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 117738e350..20c9f5e87a 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-SSH キーをまだお持ちでない場合は、[新しい SSH キーを生成](#generating-a-new-ssh-key)する必要があります。 SSH キーを持っているかどうかわからない場合は、[既存のキー](/articles/checking-for-existing-ssh-keys)をチェックします。
+### About SSH key generation
 
-SSH キーを使用するたびにパスフレーズを再入力したくない場合は、[キーを SSH エージェントに追加](#adding-your-ssh-key-to-the-ssh-agent)できます。これにより、SSH キーが管理されパスフレーズが記憶されます。
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
 
 ### 新しい SSH キーを生成する
 
@@ -62,7 +69,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
 
   {% endlinux %}
 
-4. プロンプトで、安全なパスフレーズを入力します。 詳細は「[SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases)」を参照してください。
+4. プロンプトで、安全なパスフレーズを入力します。 For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
 
 ### SSH キーを ssh-agent に追加する
 
-キーを管理するために新しい SSH キーを ssh-agent に追加する前に、[既存の SSH キーの確認](/articles/checking-for-existing-ssh-keys)と[新しい SSH キーの生成](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key)を済ませておく必要があります。 <span class="platform-mac">エージェントに SSH キーを追加する際、デフォルトの macOS の `ssh-add` コマンドを使用してください。[macports] macports (https://www.macports.org/)、[homebrew] (http://brew.sh/)、またはその他の外部ソースによってインストールされたアプリケーションは使用しないでください。</span>
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">エージェントに SSH キーを追加する際、デフォルトの macOS の `ssh-add` コマンドを使用してください。[macports] macports (https://www.macports.org/)、[homebrew] (http://brew.sh/)、またはその他の外部ソースによってインストールされたアプリケーションは使用しないでください。</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
       $ touch ~/.ssh/config
       ```
 
-    * `~/.ssh/config` ファイルを開いて修正し、`id_ed25519` キーのデフォルトの場所と名前を使用していない場合は`~/.ssh/id_ed25519` を置き換えます。
+    * `~/.ssh/config` ファイルを開き、以下の行が含まれるようにファイルを変更します。 SSH キーファイルの名前またはパスがサンプルコードと異なる場合は、現在の設定に一致するようにファイル名またはパスを変更してください。
 
       ```
       Host *
@@ -106,6 +113,25 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **Note:** If you see an error like this
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      add an additional config line to your `Host *` section:
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. SSH 秘密鍵を ssh-agent に追加して、パスフレーズをキーチェーンに保存します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
 
   {% endnote %}
 
-4. [SSH キーを GitHub アカウントに追加します](/articles/adding-a-new-ssh-key-to-your-github-account)。
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
 2. SSH プライベートキーを ssh-agent に追加します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [SSH キーを GitHub アカウントに追加します](/articles/adding-a-new-ssh-key-to-your-github-account)。
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ SSH キーを使用するたびにパスフレーズを再入力したくない
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  In some Linux environments, you need root access to run the command:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. SSH プライベートキーを ssh-agent に追加します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [SSH キーを GitHub アカウントに追加します](/articles/adding-a-new-ssh-key-to-your-github-account)。
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endif %}
+
 ### 参考リンク
 
 - 「[SSHについて](/articles/about-ssh)」
diff --git a/translations/ja-JP/content/github/authenticating-to-github/index.md b/translations/ja-JP/content/github/authenticating-to-github/index.md
index 901275eb6c..0b614153d2 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/index.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/index.md
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index fa49bdfbe9..df981fd0af 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ topics:
 5. [One-time password] の下で、送信されたリカバリメール{% data variables.product.prodname_dotcom %}の一時パスワードを入力します。 ![ワンタイムパスワードフィールド](/assets/images/help/2fa/one-time-password-field.png)
 6. [**Verify email address**] をクリックします。
 7. 別の検証要素を選択します。
-    - 以前に現在のデバイスを使用してこのアカウントにログインしたことがあり、検証にそのデバイスを使用する場合は、[**Verify this device**] をクリックします。
+    - 以前に現在のデバイスを使用してこのアカウントにログインしたことがあり、検証にそのデバイスを使用する場合は、[**Verify with this device**] をクリックします。
     - 以前にこのアカウントで SSH キーを設定しており、検証にその SSH キーを使用する場合は、[** SSH key**] をクリックします。
     - 以前に個人アクセストークンを設定しており、検証にその個人アクセストークンを使用する場合は、[**Personal access token**] をクリックします。 ![代替検証ボタン](/assets/images/help/2fa/alt-verifications.png)
 8. {% data variables.contact.github_support %}のメンバーがリクエストをレビューし、3〜5 営業日以内にメールでお知らせします。 リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。
diff --git a/translations/ja-JP/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/ja-JP/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index 92e06e138f..c9489f62bc 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -15,7 +15,7 @@ topics:
 
 {% mac %}
 
-[SSH パスフレーズを OS X Keychain によって設定した](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain)場合、リカバリできる可能性があります。
+[macOS キーチェーンを使用して SSH パスフレーズを設定](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain)した場合、リカバリできる可能性があります。
 
 1. [Finder] で、**Keychain Access** アプリケーションを検索します。 ![スポットライト検索バー](/assets/images/help/setup/keychain-access.png)
 2. [Keychain Access] で、**SSH** を検索します。
diff --git a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md
index 418f8a9b51..eb0e7ed4dc 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-security-log.md
@@ -38,23 +38,23 @@ topics:
 
 セキュリティログにリストされているイベントは、アクションによってトリガーされます。 アクションは次のカテゴリに分類されます。
 
-| カテゴリ名                                                                                  | 説明                                                                                                                                                                                                                                                                                                                                                                       |
-| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %}
-| [`account_recovery_token`](#account_recovery_token-category-actions)                   | | カテゴリ名 | 説明 [リカバリトークンの追加](/articles/configuring-two-factor-authentication-recovery-methods)に関連するすべての活動が対象です。                                                                                                                                                                                                                                                            |
-| [`支払い`](#billing-category-actions)                                                     | 自分の支払い情報に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                                |
-| [`codespaces`](#codespaces-category-actions)                                           | {% data variables.product.prodname_codespaces %} に関連するすべての活動が対象です。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces)」を参照してください。                                                                                                                                                            |
-| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                               |
+| カテゴリ名                                                                                  | 説明                                                                                                                                                                                                                                                                                                                                                                                                            |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| [`account_recovery_token`](#account_recovery_token-category-actions)                   | | カテゴリ名 | 説明 [リカバリトークンの追加](/articles/configuring-two-factor-authentication-recovery-methods)に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                 |
+| [`支払い`](#billing-category-actions)                                                     | 自分の支払い情報に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                                                                     |
+| [`codespaces`](#codespaces-category-actions)                                           | {% data variables.product.prodname_codespaces %} に関連するすべての活動が対象です。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces)」を参照してください。                                                                                                                                                                                                 |
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                    |
 | [`marketplace_listing`](#marketplace_listing-category-actions)                         | {% data variables.product.prodname_marketplace %} に一覧表示しているアプリに関連するすべての活動が対象です。{% endif %}
 | [`oauth_access`](#oauth_access-category-actions)                                       | 接続している [{% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps) に関連するすべてのアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %}
 | [`payment_method`](#payment_method-category-actions)                                   | {% data variables.product.prodname_dotcom %} プランに対する支払いに関連するすべての活動が対象です。{% endif %}
-| [`profile_picture`](#profile_picture-category-actions)                                 | 自分のプロファイル写真に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                             |
-| [`project`](#project-category-actions)                                                 | プロジェクト ボードに関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                              |
-| [`public_key`](#public_key-category-actions)                                           | [公開 SSH キー](/articles/adding-a-new-ssh-key-to-your-github-account)に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                      |
+| [`profile_picture`](#profile_picture-category-actions)                                 | 自分のプロファイル写真に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                                                                  |
+| [`project`](#project-category-actions)                                                 | プロジェクト ボードに関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                                                                   |
+| [`public_key`](#public_key-category-actions)                                           | [公開 SSH キー](/articles/adding-a-new-ssh-key-to-your-github-account)に関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                           |
 | [`repo`](#repo-category-actions)                                                       | 所有するリポジトリに関連するすべてのアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %}
-| [`sponsors`](#sponsors-category-actions)                                               | {% data variables.product.prodname_sponsors %} およびスポンサーボタンに関連するすべてのイベントが対象です (「[{% data variables.product.prodname_sponsors %} について](/articles/about-github-sponsors)」と「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+| [`sponsors`](#sponsors-category-actions)                                               | {% data variables.product.prodname_sponsors %} およびスポンサーボタンに関連するすべてのイベントが対象です (「[{% data variables.product.prodname_sponsors %} について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」と「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 | [`Team`](#team-category-actions)                                                       | 所属する Team に関連するすべてのアクティビティが対象です。{% endif %}{% if currentVersion != "github-ae@latest" %}
 | [`two_factor_authentication`](#two_factor_authentication-category-actions)             | [2 要素認証](/articles/securing-your-account-with-two-factor-authentication-2fa)に関連するすべてのアクティビティが対象です。{% endif %}
-| [`ユーザ`](#user-category-actions)                                                        | アカウントに関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                                   |
+| [`ユーザ`](#user-category-actions)                                                        | アカウントに関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                                                                                        |
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -90,6 +90,10 @@ topics:
 
 | アクション                                | 説明                                                                                                                                                                                   |
 | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create`                             | [コードスペースを作成](/github/developing-online-with-codespaces/creating-a-codespace)するとトリガーされます。                                                                                             |
+| `resume`                             | 中断されたコードスペースを再開するとトリガーされます。                                                                                                                                                          |
+| `delete`                             | [コードスペースを削除](/github/developing-online-with-codespaces/deleting-a-codespace)するとトリガーされます。                                                                                             |
+| `manage_access_and_security`         | [コードスペースがアクセスできるリポジトリ](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)を更新するとトリガーされます。                                                         |
 | `trusted_repositories_access_update` | ユーザーアカウントの [ アクセスと、{% data variables.product.prodname_codespaces %} のセキュリティ設定](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)を変更するとトリガーされます。 |
 
 #### `marketplace_agreement_signature` カテゴリアクション
@@ -181,22 +185,24 @@ topics:
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` カテゴリアクション
 
-| アクション                                         | 説明                                                                                                                                                                                                                                                                      |
-| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo_funding_link_button_toggle`             | リポジトリでスポンサーボタンの表示を有効化または無効化したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                         |
-| `repo_funding_links_file_action`              | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                              |
-| `sponsor_sponsorship_cancel`                  | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                                                            |
-| `sponsor_sponsorship_create`                  | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)」を参照)                                                                                                      |
-| `sponsor_sponsorship_preference_change`       | スポンサード開発者からメールで最新情報を受け取るかどうかを変更したときにトリガーされます (「[スポンサーシップを管理する](/articles/managing-your-sponsorship)」を参照)                                                                                                                                                                |
-| `sponsor_sponsorship_tier_change`             | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                    |
-| `sponsored_developer_approve`                 | {% data variables.product.prodname_sponsors %}アカウントが承認されるとトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照）             |
-| `sponsored_developer_create`                  | {% data variables.product.prodname_sponsors %}アカウントが作成されるとトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照）             |
-| `sponsored_developer_profile_update`          | スポンサード開発者のプロフィールを編集するとトリガーされます（「[{% data variables.product.prodname_sponsors %}のプロフィール詳細を編集する](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)」を参照）                                                 |
-| `sponsored_developer_request_approval`        | 承認のために{% data variables.product.prodname_sponsors %}のアプリケーションをサブミットするとトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照） |
-| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                           |
-| `sponsored_developer_update_newsletter_send`  | スポンサーにメールで最新情報を送信したときにトリガーされます (「[スポンサーに連絡する](/articles/contacting-your-sponsors)」を参照)                                                                                                                                                                                  |
-| `waitlist_invite_sponsored_developer`         | 待ちリストから{% data variables.product.prodname_sponsors %}に参加するよう招待されたときにトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照）   |
-| `waitlist_join`                               | スポンサード開発者になるために待ちリストに参加するとトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照）                                             |
+| アクション                                         | 説明                                                                                                                                                                                                                                                                  |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | カスタム金額を有効または無効にするとき、または提案されたカスタム金額を変更するときにトリガーされます (「[スポンサーシップ層を管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)」を参照)。                                                                                      |
+| `repo_funding_links_file_action`              | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                          |
+| `sponsor_sponsorship_cancel`                  | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                                                        |
+| `sponsor_sponsorship_create`                  | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照)                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | スポンサード開発者からメールで最新情報を受け取るかどうかを変更するとトリガーされます (「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)」を参照)                                                                                                                          |
+| `sponsor_sponsorship_tier_change`             | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                |
+| `sponsored_developer_approve`                 | {% data variables.product.prodname_sponsors %} アカウントが承認されるとトリガーされます (「[ユーザアカウントに{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照)               |
+| `sponsored_developer_create`                  | {% data variables.product.prodname_sponsors %} アカウントが作成されるとトリガーされます (「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照)              |
+| `sponsored_developer_disable`                 | {% data variables.product.prodname_sponsors %} アカウントが無効になるとトリガーされます                                                                                                                                                                                                 |
+| `sponsored_developer_redraft`                 | {% data variables.product.prodname_sponsors %} アカウントが承認済みの状態からドラフト状態に戻るとトリガーされます                                                                                                                                                                                    |
+| `sponsored_developer_profile_update`          | スポンサード開発者のプロフィールを編集するとトリガーされます (「[{% data variables.product.prodname_sponsors %} のプロフィール詳細を編集する](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)」を参照)                                                    |
+| `sponsored_developer_request_approval`        | 承認のために {% data variables.product.prodname_sponsors %} のアプリケーションをサブミットするとトリガーされます (「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照) |
+| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を管理する](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)」を参照)                                                                                                                      |
+| `sponsored_developer_update_newsletter_send`  | スポンサーにメールで最新情報を送信するとトリガーされます (「[スポンサーに連絡する](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)」を参照)                                                                                                                                 |
+| `waitlist_invite_sponsored_developer`         | 待ちリストから {% data variables.product.prodname_sponsors %} に参加するよう招待されたときにトリガーされます (「[ユーザアカウントに{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照)    |
+| `waitlist_join`                               | スポンサード開発者になるために待ちリストに参加するとトリガーされます (「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照)                                               |
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -250,7 +256,7 @@ topics:
 | `login`                                                                                                                                                                                             | {% data variables.product.product_location %} にログインするとトリガーされます。{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 
-`mandatory_message_viewed`   | 必須メッセージを表示するとトリガーされます (詳細は「[ユーザーメッセージのカスタマイズ](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください) | |{% endif %}| | `failed_login` | 正常にログインできなかったときにトリガーされます。 | `remove_email` | メール アドレスを削除するとトリガーされます。 | `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} | `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
+`mandatory_message_viewed`   | 必須メッセージを表示するとトリガーされます (詳細は「[ユーザーメッセージのカスタマイズ](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください) | |{% endif %}| | `failed_login` | 正常にログインできなかったときにトリガーされます。 | `remove_email` | メール アドレスを削除するとトリガーされます。 | `rename` | 自分のアカウント名を変更するとトリガーされます。{% if currentVersion == "free-pro-team@latest" %} | `report_content` | [Issue またはプルリクエスト、または Issue、プルリクエスト、またはコミットにコメントをレポートすると](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)トリガーされます。{% endif %} | `show_private_contributions_count` | [プロフィールでプライベートコントリビューションを公開](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)するとトリガーされます {% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | {% data variables.product.product_name %} が[2要素認証コード](/articles/accessing-github-using-two-factor-authentication)を要求すると{% endif %}トリガーされます。
 
 #### `user_status` カテゴリアクション
 
@@ -258,4 +264,3 @@ topics:
 | --------- | ------------------------------------------------------------------------------------------------------------------------- |
 | `update`  | 自分のプロファイルでステータスを設定または変更するときにトリガーされます。 詳細は「[ステータスを設定する](/articles/personalizing-your-profile/#setting-a-status)」を参照してください。 |
 | `destroy` | 自分のプロファイルでステータスを消去するときにトリガーされます。                                                                                          |
-
diff --git a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md
index f534100ed2..3bc3cafab7 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your SSH keys
-intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your {% data variables.product.product_name %} account.'
+title: SSH キーをレビューする
+intro: '認証情報を安全に保つには、SSH キーを定期的に監査し、キーをデプロイし、自分の {% data variables.product.product_name %} アカウントにアクセスする許可されたアプリケーションをレビューしてください。'
 redirect_from:
   - /articles/keeping-your-application-access-tokens-safe/
   - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/
@@ -14,32 +14,31 @@ topics:
   - Access management
 ---
 
-You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid.
+許可されていない (あるいは侵害された可能性のある) SSH キーを削除することで、攻撃者が以後自分のリポジトリにアクセスすることを防止できます。 有効な既存の SSH キーを承認することもできます。
 
 {% mac %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
-	![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
+3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効な SSH キーがある場合は、[**Approve**] をクリックします。 ![SSH キーのリスト](/assets/images/help/settings/settings-ssh-key-review.png)
 
   {% tip %}
 
-     **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
+     **メモ:** Git 操作が失敗したために SSH キーを監査している場合は、 [SSH キー監査エラー](/articles/error-we-re-doing-an-ssh-key-audit)の原因となった未検証のキーが SSH キーのリストで強調表示されます。
 
   {% endtip %}
 
-4. Open Terminal.
+4. ターミナルを開きます。
 
 5. {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older:
+6. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7 以前を使用している場合:
   ```shell
   $ ssh-add -l
   > 2048 <em>a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-  If you're using OpenSSH 6.8 or newer:
+  OpenSSH 6.8 以降を使用している場合:
   ```shell
   $ ssh-add -l -E md5
   > 2048 <em>MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
@@ -50,7 +49,7 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```{% endif %}
 
-7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致していなければなりません 。
 
 {% endmac %}
 
@@ -58,28 +57,28 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
-	![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
+3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[Delete] をクリックします。 残しておきたい有効な SSH キーがある場合は、[Approve] をクリックします。
+    ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
 
   {% tip %}
 
-     **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
+     **注釈:** Git 操作が失敗したために SSH キーを監査している場合は、[SSH キー監査エラー] (/articles/error-we-re-doing-an-ssh-key-audit) の原因となった未検証のキーが SSH キーのリストで強調表示されます。
 
   {% endtip %}
 
-4. Open Git Bash. If you're using Git Shell, which is included in {% data variables.product.prodname_desktop %}, open Git Shell and skip to step 6.
+4. Git Bash を開きます。 {% data variables.product.prodname_desktop %} に収納されている Git Shell を使用している場合は、Git Shell を開き、ステップ 6 に進みます。
 
 5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %}
 
   {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older:
+6. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7以前を使用している場合:
   ```shell
   $ ssh-add -l
   > 2048 <em>a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-  If you're using OpenSSH 6.8 or newer:
+  OpenSSH 6.8 以降を使用している場合:
   ```shell
   $ ssh-add -l -E md5
   > 2048 <em>MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
@@ -90,7 +89,7 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```{% endif %}
 
-7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致していなければなりません 。
 
 {% endwindows %}
 
@@ -98,42 +97,40 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
-	![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
+3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[Delete] をクリックします。 残しておきたい有効な SSH キーがある場合は、[Approve] をクリックします。
+    ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
 
   {% tip %}
 
-     **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
+     **注釈:** Git 操作が失敗したために SSH キーを監査している場合は、[SSH キー監査エラー] (/articles/error-we-re-doing-an-ssh-key-audit) の原因となった未検証のキーが SSH キーのリストで強調表示されます。
 
   {% endtip %}
 
-4. Open Terminal.
+4. ターミナルを開きます。
 
 5. {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older:
+6. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7以前を使用している場合:
   ```shell
   $ ssh-add -l
   > 2048 <em>a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-  If you're using OpenSSH 6.8 or newer:
+  OpenSSH 6.8 以降を使用している場合:
   ```shell
   $ ssh-add -l -E md5
   > 2048 <em>MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
   {% else %}
-  ```shell
-  $ ssh-add -l -E sha256
-  > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
-  ```{% endif %}
+```shell $ ssh-add -l -E sha256
+> 2048 *SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ* /Users/*USERNAME*/.ssh/id_rsa (RSA) ```{% endif %}
 
-7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致して*いなければなりません* 。
 
 {% endlinux %}
 
 {% warning %}
 
-**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern.
+**警告**: 見慣れない SSH キーが {% data variables.product.product_name %} で見つかった場合は、すぐにそれを削除し、さらに支援が必要な場合は {% data variables.contact.contact_support %} に問い合わせてください。 確認できない公開鍵は、潜在的なセキュリティ上の問題を示している可能性があります。
 
 {% endwarning %}
diff --git a/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
index 729ba0b57d..35d00c8ccf 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
@@ -31,12 +31,12 @@ topics:
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file:
+1. GPG スイートを使用していない場合は、`zsh` シェルで次のコマンドを実行して、GPG キーがある場合に `.zshrc` ファイル、または `.zprofile` ファイルに追加します。
   ```shell
   $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi
   ```
-  Alternatively, if you use the `bash` shell, run this command:
+  または、`bash` シェルを使用する場合は、次のコマンドを実行します。
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
@@ -93,7 +93,7 @@ topics:
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. To add your GPG key to your bash profile, run the following command:
+1. GPG キーを bash プロファイルに追加するには、次のコマンドを実行します。
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
diff --git a/translations/ja-JP/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/ja-JP/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index c6a810a6c0..292cf84d38 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -1,6 +1,6 @@
 ---
 title: HTTPS ポートを介して SSH を使用する
-intro: '時々、ファイアウォールは SSH 接続を完全に許可することを拒否します。  If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port.  ほとんどのファイアウォールルールでこれを許可する必要がありますが、プロキシサーバーが干渉する可能性があります。'
+intro: '時々、ファイアウォールは SSH 接続を完全に許可することを拒否します。  [HTTPS cloning with credential caching] (/github/getting-started-with-github/caching-your-github-credentials-in-git) を使用できない場合は、HTTPS ポートを介して作成された SSH 接続を使用してクローンを試みることができます。  ほとんどのファイアウォールルールでこれを許可する必要がありますが、プロキシサーバーが干渉する可能性があります。'
 redirect_from:
   - /articles/using-ssh-over-the-https-port
 versions:
@@ -11,7 +11,7 @@ topics:
 
 {% tip %}
 
-**GitHub Enterprise ユーザ**: HTTPS ポート上で SSH 経由で GitHub Enterprise にアクセスすることは現在サポートされていません。
+**{% data variables.product.prodname_ghe_server %} ユーザ**: HTTPS ポートを介した SSH 経由での {% data variables.product.prodname_ghe_server %} へのアクセスは現在サポートされていません。
 
 {% endtip %}
 
diff --git a/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index 52e1b200d2..3b8d5c170a 100644
--- a/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -88,7 +88,7 @@ fi
 
 ### パスフレーズをキーチェーンに保存する
 
-OS X El Capitan を介する OS X Leopard では、これらのデフォルトの秘密鍵ファイルは自動的に処理されます:
+OS X El Capitan を介する Mac OS X Leopard では、これらのデフォルトの秘密鍵ファイルは自動的に処理されます。
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md
index 39c64436a1..a2ce36a283 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md
@@ -23,7 +23,7 @@ topics:
 
 ブランチの作成、プルリクエストのオープン、プルリクエスト中でのブランチの削除とリストアを行うためには、リポジトリへの書き込みアクセスを持っていなければなりません。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/github/getting-started-with-github/access-permissions-on-github)」を参照してください。
 
-### About the default branch
+### デフォルトブランチについて
 
 {% data reusables.branches.new-repo-default-branch %} デフォルトブランチは、誰かがあなたのリポジトリにアクセスしたときに {% data variables.product.prodname_dotcom %} が表示されるブランチです。 また、デフォルトブランチは、誰かがリポジトリのクローンを作成したときに Git がローカルでチェックアウトする最初のブランチでもあります。 {% data reusables.branches.default-branch-automatically-base-branch %}
 
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index 33f4325638..77bd6a2314 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: 共同開発モデルについて
-intro: プルリクエストの使い方は、プロジェクトで使う開発モデルのタイプによります。
+intro: プルリクエストの使い方は、プロジェクトで使う開発モデルのタイプによります。 You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-プルリクエストを使う開発モデルには、主に2つのタイプがあります。 *フォークとプルモデル*では、誰でも既存のリポジトリをフォークして、個人のフォークに変更をプッシュできます。 ユーザが所有するフォークにプッシュする際に、ソースリポジトリへのアクセス許可は必要ありません。 プロジェクトのメンテナーは、その変更をソースリポジトリにプルできます。 ユーザが所有するフォークのブランチからソース（上流）のリポジトリのブランチへの変更を提案するプルリクエストをオープンすると、上流のリポジトリへのプッシュアクセスを持つすべてのユーザがプルリクエストに変更を加えられるようにすることができます。  このモデルは、新しいコントリビュータにとって摩擦が減り、事前に調整することなく人々が独立して作業できることから、オープンソースプロジェクトでよく使われます。
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. ユーザが所有するフォークにプッシュする際に、ソースリポジトリへのアクセス許可は必要ありません。 プロジェクトのメンテナーは、その変更をソースリポジトリにプルできます。 ユーザが所有するフォークのブランチからソース（上流）のリポジトリのブランチへの変更を提案するプルリクエストをオープンすると、上流のリポジトリへのプッシュアクセスを持つすべてのユーザがプルリクエストに変更を加えられるようにすることができます。  このモデルは、新しいコントリビュータにとって摩擦が減り、事前に調整することなく人々が独立して作業できることから、オープンソースプロジェクトでよく使われます。
 
 {% tip %}
 
@@ -20,7 +22,9 @@ topics:
 
 {% endtip %}
 
-*共有リポジトリモデル*では、コラボレータは単一の共有リポジトリへのプッシュアクセスが許可され、変更の必要がある場合にはトピックブランチが作成されます。 このモデルでは、メインの開発ブランチに変更がマージされる前に、一連の変更についてコードレビューと一般的な議論を始めることができるので、プルリクエストが役に立ちます。 このモデルは、プライベートなプロジェクトで協力する小さなTeamやOrganizationで普及しています。
+### Shared repository model
+
+共有リポジトリモデルでは、コラボレータは単一の共有リポジトリへのプッシュアクセスが許可され、変更の必要がある場合にはトピックブランチが作成されます。 このモデルでは、メインの開発ブランチに変更がマージされる前に、一連の変更についてコードレビューと一般的な議論を始めることができるので、プルリクエストが役に立ちます。 このモデルは、プライベートなプロジェクトで協力する小さなTeamやOrganizationで普及しています。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index 1ded20c981..2465fbd796 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -53,18 +53,18 @@ Organization オーナー、およびリポジトリにプッシュアクセス
 
 コミットに対するチェックをスキップもしくはリクエストするには、以下の追加行のいずれかをコミットメッセージの末尾に追加します:
 
-- コミットの_チェックをスキップ_には、コミットメッセージと変更の短く意味のある説明を入力してください。 コミットの説明の後に、閉じる引用符の代わりに 2 つの空の行を追加し、その後に `skip-checks: true` と続けます。
+- コミットの_チェックをスキップ_には、コミットメッセージと変更の短く意味のある説明を入力してください。 After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - コミットのチェックを_リクエスト_するには、コミットメッセージと変更の短く意味のある説明を入力してください。 コミットの説明の後に、閉じる引用符の代わりに 2 つの空の行を追加し、その後に `request-checks: true` と続けます:
+- コミットのチェックを_リクエスト_するには、コミットメッセージと変更の短く意味のある説明を入力してください。 After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
index eed3153525..01ec6fb937 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
@@ -14,9 +14,9 @@ topics:
 
 プルリクエストの自動マージを有効にすると、必要なすべてのレビューを満たし、ステータスチェックに合格すると、プルリクエストが自動的にマージされます。 自動マージにより、要件が満たされるのを待つ必要がなくなるため、他のタスクに進むことができます。
 
-プルリクエストで自動マージを使用する前に、リポジトリで自動マージを有効にする必要があります。 For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
+プルリクエストで自動マージを使用する前に、リポジトリで自動マージを有効にする必要があります。 詳しい情報については、「[リポジトリ内のプルリクエストの自動マージを管理する](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)」を参照してください。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
 
-After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %}
+プルリクエストの自動マージを有効にした後、リポジトリへの書き込み権限を持たないユーザがプルリクエストの head ブランチに新しい変更をプッシュするか、プルリクエストのベースブランチを切り替えると、自動マージは無効になります。 たとえば、メンテナがフォークからのプルリクエストの自動マージを有効にした場合、コントリビューターがプルリクエストに新しい変更をプッシュすると、自動マージは無効になります。{% endif %}
 
 自動マージに関するフィードバックがある場合は、[お問い合わせ](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback)にご連絡ください。
 
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 3842ff99c7..aea382fe6a 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. プルリクエストのリストで、レビューの準備ができたことを示すマークを付けたいプルリクエストクリックします。
 3. マージボックスで、[**Ready for review**] をクリックします。 ![[Ready for review] ボタン](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index 36287f5880..f9d0878bc6 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### アクティブなプルリクエストをローカルで修正する
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index dbfdc3c89d..8545963674 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ Pull Request レビューへの行コメント追加に関する 詳しい情報
 
 **参考:**
 - プルリクエストのコメントては、@メンション、絵文字、参照など、{% data variables.product.product_name %}の通常のコメントにおいてサポートされている[フォーマット](/categories/writing-on-github)がサポートされています。
-- [**Files changed**] のプルリクエストには、コメントへの[リアクション](/articles/about-conversations-on-github#reacting-to-ideas-in-comments)を追加できます。
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index 5d385caf94..2a013c99d7 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -19,6 +19,14 @@ topics:
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### ブランチの範囲と宛先リポジトリの変更
 
 デフォルトでは、プルリクエストは親リポジトリの[デフォルトブランチ](/articles/setting-the-default-branch)に基づいています。 詳細は「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)」を参照してください。
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index cdb7b2a52d..51dd52fd84 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. 削除するブランチまでスクロールし、{% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %} をクリックします。 ![ブランチを削除する](/assets/images/help/branches/branches-delete.png)
+1. 削除するブランチまでスクロールし、{% octicon "trash" aria-label="The trash icon to delete the branch" %} をクリックします。 ![ブランチを削除する](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..68b7b8f36b
--- /dev/null
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: はじめましょう
+shortTitle: はじめましょう
+intro: '{% data variables.product.prodname_dotcom %} フローと、プロジェクトのさまざまなコラボレーションおよびディスカッションの方法について学びます。'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md
index 05950b0c63..60e658415a 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Issue とプルリクエストでのコラボレーション
-intro: '{% data variables.product.prodname_dotcom %} フローを使用して Issue の変更を追跡およびディスカッションし、プルリクエストの変更を提案してレビューします。'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -18,10 +18,9 @@ topics:
 
 ### 目次
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index 485d9bff0e..cca6920f97 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ topics:
 
 トピックブランチでの変更を上流ブランチにマージしたくなければ、マージせずに[プルリクエストをクローズする](/articles/closing-a-pull-request)ことができます。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### {% data variables.product.prodname_dotcom %} でプルリクエストをマージする
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..6a3f1b4713
--- /dev/null
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### はじめに
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### 問題
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### プルリクエスト
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### Team ディスカッション
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. アイデアについてディスカッションするためにリポジトリでIssueを開く代わりに、Teamディスカッションで会話することでTeam全体を巻き込めます。
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### 次のステップ
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)を参照してください。
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)を参照してください。
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index 0ed297ed10..0b93b7d3ba 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -19,7 +19,7 @@ topics:
 
 {% data reusables.dependency-review.feature-overview %}
 
-Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+依存関係のレビューでは、「左にシフト」することができます。 提供された予測情報を使用して、本番環境に至る前に脆弱性のある依存関係をキャッチできます。 For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
 
 ### プルリクエスト内の依存関係を確認する
 
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
index d226f26b9a..e1fbe6cad2 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
@@ -51,6 +51,6 @@ topics:
 
 {% tip %}
 
-**参考**: フォークの同期は、リポジトリのローカルコピーだけをアップデートします。 To update your fork on {% data variables.product.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+**参考**: フォークの同期は、リポジトリのローカルコピーだけをアップデートします。 {% data variables.product.product_location %} 上のフォークをアップデートするには、[変更をプッシュする](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)必要があります。
 
 {% endtip %}
diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index aa7e301c85..1e9486911b 100644
--- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -79,5 +79,5 @@ Enterprise のポリシーでフォークが許可されている場合、内部
 - 「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」
 - [フォークについて](/articles/about-forks)
 - 「[リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)」
-- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
+- 「[Organization のフォークポリシーを管理する](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」
 - 「{% if currentVersion == "free-pro-team@latest" %}[Enterprise アカウントでリポジトリ管理ポリシーを施行する](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories)」{% else %}「[Enterprise でリポジトリ管理ポリシーを施行する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}」
diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index b75351d8e5..82395e1fa7 100644
--- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ README ファイルをリポジトリのルート、`docs`、または隠れデ
 
 {% endif %}
 
+### Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+The auto-generated table of contents is enabled by default for all Markdown files in a repository, but you can disable this feature for your repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under "Features", deselect **Table of contents**. ![Automatic TOC setting for repositories](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### READMEファイルのセクションリンクとblobページ
 
-多くのプロジェクトは、README の先頭にある目次を使ってユーザをファイル中のさまざまなセクションへ誘導します。 {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### READMEファイル中の相対リンクと画像パス
 
diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index 77dc5d2f87..2156443a2d 100644
--- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -24,7 +24,7 @@ topics:
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-テンプレートリポジトリのデフォルトブランチのみからディレクトリ構造とファイルを含めるか、すべてのブランチを含めるかを選択できます。
+テンプレートリポジトリのデフォルトブランチのみからディレクトリ構造とファイルを含めるか、すべてのブランチを含めるかを選択できます。 Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 テンプレートからリポジトリを作成することは、リポジトリをフォークすることに似ていますが、以下の点で異なります:
diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index 70bb8edd97..144a537c4a 100644
--- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -20,7 +20,7 @@ topics:
 
 テンプレートリポジトリを作成するには、リポジトリを作成して、そのリポジトリをテンプレート化する必要があります。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。
 
-リポジトリをテンプレートにすると、リポジトリにアクセスできるユーザは誰でも、デフォルトブランチと同じディレクトリ構造とファイルで新しいリポジトリを生成できます。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} また、リポジトリに他のすべてのブランチを含めることもできます。{% endif %} 詳しい情報については、「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
index 2ca9c762b7..72f6a55d28 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
@@ -1,52 +1,43 @@
 ---
-title: About code scanning
-intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.'
+title: コードスキャンニングについて
+intro: '{% data variables.product.prodname_code_scanning %} を使用して、{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードからセキュリティの脆弱性とエラーを見つけることができます。'
 product: '{% data reusables.gated-features.code-scanning %}'
-redirect_from:
-  - /github/managing-security-vulnerabilities/about-automated-code-scanning
 versions:
   enterprise-server: '2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-### About {% data variables.product.prodname_code_scanning %}
+### {% data variables.product.prodname_code_scanning %} について
 
 {% data reusables.code-scanning.about-code-scanning %}
 
-You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
+{% data variables.product.prodname_code_scanning %} を使用して、コード内の既存の問題の修正を検索し、トリアージして、優先順位を付けることができます。 また、{% data variables.product.prodname_code_scanning_capc %} は、開発者による新しい問題の発生も防ぎます。 スキャンを特定の日時にスケジュールしたり、プッシュなどの特定のイベントがリポジトリで発生したときにスキャンをトリガーしたりすることができます。
 
-If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+{% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see 
-"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see  "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." 
+リポジトリまたは Organization をまたいで {% data variables.product.prodname_code_scanning %} による結果を監視するには、webhooks や {% data variables.product.prodname_code_scanning %} API を使用できます。 {% data variables.product.prodname_code_scanning %} 用の webhook に関する詳しい情報については、「[Webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)」を参照してください。 API に関する情報については、 「[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)」を参照してください。
 
-To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
+{% data variables.product.prodname_code_scanning %} を始めるには、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」を参照してください。
 
-### About {% data variables.product.prodname_codeql %}
+### {% data variables.product.prodname_codeql %} について
 
-You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. 
+デフォルトでは、{% data variables.product.prodname_code_scanning %} はセマンティックコード分析エンジンである {% data variables.product.prodname_codeql %} を使用します。 {% data variables.product.prodname_codeql %} はコードをデータとして扱い、コードの潜在的な脆弱性を従来の静的分析よりも高い精度で見つけることができます。
 
-{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website.
+{% data variables.product.prodname_ql %} は {% data variables.product.prodname_codeql %} を動作させるクエリ言語です。 {% data variables.product.prodname_ql %} はオブジェクト指向ロジックプログラミング言語です。 {% data variables.product.company_short %}、言語の専門家、セキュリティ研究者が {% data variables.product.prodname_code_scanning %} に使用するクエリを作成します。クエリはオープンソースです。 コミュニティはクエリを維持および更新して、分析を改善し、誤検出を減らします。 詳しい情報については、GitHub Security Lab Web サイトの「[{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)」を参照してください。
 
-{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
+{% data variables.product.prodname_code_scanning %} の API エンドポイントについての詳細は、「[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)」を参照してください。
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation.
+[`github/codeql`](https://github.com/github/codeql)リポジトリで {% data variables.product.prodname_code_scanning %} のクエリを表示して貢献できます。 詳しい情報については、 {% data variables.product.prodname_codeql %} ドキュメントの「[{% data variables.product.prodname_codeql %} クエリ](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/)」を参照してください。
 
-{% if currentVersion == "free-pro-team@latest" %}
-
-### About billing for {% data variables.product.prodname_code_scanning %}
-
-{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
-
-{% endif %}
-
-### About third-party code scanning tools
+### サードパーティのコードスキャンツールについて
 
 {% data reusables.code-scanning.you-can-upload-third-party-analysis %}
 
@@ -54,9 +45,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 {% data reusables.code-scanning.get-started-uploading-third-party-data %}
 
-### Further reading
+### 参考リンク
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
-- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
+- OASIS 委員会 の Web サイトの「[OASIS Static Analysis Results Interchange Format (SARIF) 」TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif)
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index 7cb9efef3e..9018fa347e 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -1,7 +1,7 @@
 ---
-title: About integration with code scanning
-shortTitle: About integration
-intro: 'You can perform {% data variables.product.prodname_code_scanning %} externally and then display the results in {% data variables.product.prodname_dotcom %}, or set up webhooks that listen to {% data variables.product.prodname_code_scanning %} activity in your repository.'
+title: コードスキャンとのインテグレーションについて
+shortTitle: インテグレーションについて
+intro: '{% data variables.product.prodname_code_scanning %} を外部で実行し、その結果を {% data variables.product.prodname_dotcom %} で表示できます。また、リポジトリで {% data variables.product.prodname_code_scanning %} アクティビティを監視する webhook をセットアップすることもできます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   enterprise-server: '2.22'
@@ -9,19 +9,21 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-As an alternative to running {% data variables.product.prodname_code_scanning %} within {% data variables.product.prodname_dotcom %}, you can perform analysis elsewhere and then upload the results. Alerts for {% data variables.product.prodname_code_scanning %} that you run externally are displayed in the same way as those for  {% data variables.product.prodname_code_scanning %} that you run within {% data variables.product.prodname_dotcom %}. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+{% data variables.product.prodname_code_scanning %} を {% data variables.product.prodname_dotcom %} 内で実行する他に、分析を別の場所で実行して、その結果をアップロードすることもできます。 外部で実行した {% data variables.product.prodname_code_scanning %} のアラートは、{% data variables.product.prodname_dotcom %} 内で {% data variables.product.prodname_code_scanning %} を実行した場合と同じように表示されます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-If you use a third-party static analysis tool that can produce results as Static Analysis Results Interchange Format (SARIF) 2.1.0 data, you can upload this to {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)」を参照してください。
+Static Analysis Results Interchange Format (SARIF) 2.1.0 データとして結果を生成できるサードパーティの静的解析ツールを使用する場合、そのデータを {% data variables.product.prodname_dotcom %} にアップロードできます。 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)」を参照してください。
 
-### Integrations with webhooks
+### webhook とのインテグレーション
 
-You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. For example, you could build an integration that creates an issue on {% data variables.product.product_name %} or sends you a Slack notification when a new {% data variables.product.prodname_code_scanning %} alert is added in your repository. For more information, see "[Creating webhooks](/developers/webhooks-and-events/creating-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)."
+{% data variables.product.prodname_code_scanning %} webhook を使用して、リポジトリの {% data variables.product.prodname_code_scanning %} イベントにサブスクライブする、[{% data variables.product.prodname_github_app %}](/apps/building-github-apps/) や [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/) などのインテグレーションを構築またはセットアップできます。 たとえば、 {% data variables.product.product_name %} で Issue を作成するインテグレーションや、リポジトリに新たな {% data variables.product.prodname_code_scanning %} アラートが追加されたときに Slack 通知を送信するインテグレーションを構築できます。 詳しい情報については、「[webhook を作製すく](/developers/webhooks-and-events/creating-webhooks)」および「[webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)」を参照してください。
 
 ### 参考リンク
 
 * "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)"
-* "[Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system)"
+* 「[既存の CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を使用する](/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system)」
 * "[SARIF support for code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)"
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 6225c4b147..32ea6fa1dd 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
index 612c2f6227..7b52e8df1c 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
@@ -1,60 +1,61 @@
 ---
-title: Configuring code scanning
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+title: コードスキャンを設定する
+intro: '{% data variables.product.prodname_dotcom %} がプロジェクトのコードをスキャンして脆弱性やエラーを検出する方法を設定できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
 miniTocMaxHeadingLevel: 4
 versions:
-  free-pro-team: '*'
-  enterprise-server: '>=2.22'
+  enterprise-server: '2.22'
+topics:
+  - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About {% data variables.product.prodname_code_scanning %} configuration
+### {% data variables.product.prodname_code_scanning %} の設定について
 
-You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+{% data variables.product.prodname_actions %} を使用して、または {% data variables.product.prodname_codeql_runner %} を使用して継続的インテグレーション (CI) システムから {% data variables.product.prodname_code_scanning %} を {% data variables.product.product_name %} 上で実行できます。 {% data variables.product.prodname_actions %} に関する詳しい情報については、「[{% data variables.product.prodname_actions %} について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。 For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)."
 
-This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}.
+この記事は、{% data variables.product.product_name %} 上で {% data variables.product.prodname_code_scanning %} を実行することについて説明しています。
 
-Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)."
+リポジトリに {% data variables.product.prodname_code_scanning %} を設定する前に、リポジトリに {% data variables.product.prodname_actions %} ワークフローを追加して {% data variables.product.prodname_code_scanning %} をセットアップする必要があります。 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」を参照してください。
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+{% data variables.product.prodname_codeql %} 解析は、{% data variables.product.prodname_dotcom %} で実行できる {% data variables.product.prodname_code_scanning %} のほんの一例に過ぎません。 {% data variables.product.prodname_dotcom_the_website %} 上の {% data variables.product.prodname_marketplace %} には、利用可能な別の {% data variables.product.prodname_code_scanning %} ワークフローもあります。 この記事で扱う具体例は、{% data variables.product.prodname_codeql_workflow %} ファイルに関するものです。
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} は、リポジトリの _.github/workflows_ ディレクトリにワークフローファイルを保存します。 ファイル名を検索して、追加済みのワークフローを見つけることができます。 For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. リポジトリで、編集したいワークフローファイルにアクセスします。
+1. ファイルビューの右上隅の {% octicon "pencil" aria-label="The edit icon" %}をクリックしてワークフローエディタを開きます。 ![ワークフローファイルの編集ボタン](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. ファイルを編集したら、[**Start commit**] をクリックして、[Commit changes] フォームに入力します。 現在のブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択できます。 ![codeql.yml ワークフローの更新をコミットする](/assets/images/help/repository/code-scanning-workflow-update.png)
 
-For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+ワークフローファイルの編集に関する詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-### Configuring frequency
+### 頻度を設定する
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+スケジュール設定されているときや、リポジトリで特定のイベントが発生したときに、コードをスキャンできます。
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+リポジトリへのプッシュごと、およびプルリクエストが作成されるたびにコードをスキャンすることで、開発者がコードに新しい脆弱性やエラーをもたらすことを防ぎます。 スケジュールに従ってコードをスキャンすると、開発者がリポジトリを積極的に維持していない場合でも、{% data variables.product.company_short %}、セキュリティ研究者、コミュニティが発見した最新の脆弱性とエラーが通知されます。
 
-#### Scanning on push
+#### プッシュ時にスキャンする
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+デフォルトのワークフローを使用する場合、{% data variables.product.prodname_code_scanning %} は、イベントによってトリガーされるスキャンに加えて、リポジトリ内のコードを週に1回スキャンします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#on)」を参照してください。
 
-#### Scanning pull requests
+#### プルリクエストをスキャンする
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+デフォルトの {% data variables.product.prodname_codeql_workflow %} は、`pull_request` イベントを使用して、デフォルトブランチに対するプルリクエストのコードスキャンをトリガーします。 プルリクエストをプライベートフォークからオープンした場合、`pull_request` イベントはトリガーされません。
 
-For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+`pull_request` イベントに関する詳しい情報については、「"[{% data variables.product.prodname_actions %}のためのワークフローの構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。
 
-#### Avoiding unnecessary scans of pull requests
+#### プルリクエストの不要なスキャンを回避する
 
-You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+どのファイルが変更されたかに関わらず、デフォルトブランチに対する特定のプルリクエストにコードスキャンがトリガーされることを避けたい場合もあるでしょう。 これを設定するには、{% data variables.product.prodname_code_scanning %} ワークフローで `on:pull_request:paths-ignore` または `on:pull_request:paths` を指定します。 たとえば、プルリクエストにおける変更が、`.md` または `.txt` のファイル拡張子を持つファイルである場合、次の `paths-ignore` 配列を使用できます。
 
 ``` yaml
 on:
@@ -69,28 +70,28 @@ on:
 
 {% note %}
 
-**Notes**
+**注釈**
 
-* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+* `on:pull_request:paths-ignore` と `on:pull_request:paths` は、ワークフローのアクションがプルリクエストで実行されるかどうかを決定する条件を設定します。 アクションが実行されたときにどのファイルが解析__されるかは決定しません。 プルリクエストに、`on:pull_request:paths-ignore` または `on:pull_request:paths` にマッチしないファイルが含まれている場合、ワークフローはそのアクションを実行し、`on:pull_request:paths-ignore` または `on:pull_request:paths` にマッチするものを含む、プルリクエストにおいて変更されたすべてのファイルをスキャンします。ただし、除外されているファイルは除きます。 ファイルを解析から除外する方法については、「[スキャンするディレクトリを指定する](#specifying-directories-to-scan)」を参照してください。
+* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} ワークフローファイルに対しては、`on:push` イベントで `paths-ignore` や `paths` といったキーワードは使用しないでください。解析に漏れが生じる恐れがあります。 正確な結果を得るには、{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} が新しい変更を前回のコミットの解析と比較できる必要があります。
 
 {% endnote %}
 
-For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+`on:pull_request:paths-ignore` と `on:pull_request:paths` を使用して、プルリクエストに対していつワークフローを実行するかを決定することに関する詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)」を参照してください。
 
-#### Scanning on a schedule
+#### スケジュールに従ってスキャンする
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`pull_request` イベントを使用して、プルリクエストの `HEAD` コミットでコードスキャンをトリガーします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onschedule)」を参照してください。
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+**注釈**: {% data variables.product.prodname_dotcom %} は、デフォルトのブランチのワークフローにあるスケジュール設定されたジョブのみを実行します。 他のブランチのワークフローでスケジュールを変更しても、ブランチをデフォルトブランチにマージするまで影響はありません。
 
 {% endnote %}
 
-#### Example
+#### サンプル
 
-The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+以下の例は、デフォルトブランチの名前が `main` で、`protected` という保護されたブランチがある特定のリポジトリに対する {% data variables.product.prodname_codeql_workflow %} を示しています。
 
 ``` yaml
 on:
@@ -99,19 +100,17 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 15 * * 0'
+    - cron: '40 7 * * 2'
 ```
 
-This workflow scans:
-* Every push to the default branch and the protected branch
-* Every pull request to the default branch
-* The default branch at 3 P.M. every Sunday
+このワークフローは、次をスキャンします。
+* デフォルトブランチと保護されたブランチに対する全てのプッシュ
+* デフォルトブランチに対する全てのプルリクエスト
+* 毎週火曜日 7:40 (UTC) にデフォルトブランチ
 
-### Specifying an operating system
+### オペレーティングシステムを指定する
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
-
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+コードのコンパイルに特定のオペレーティングシステムが必要な場合は、そのオペレーティングシステムを {% data variables.product.prodname_codeql_workflow %} で設定できます。 `jobs.analyze.runs-on` の値を編集して、{% data variables.product.prodname_code_scanning %} のアクションを実行するマシンのオペレーティングシステムを指定します。 オペレーティングシステムの指定には、`self-hosted` の後に、2 つの要素がある配列の 2 番目の要素として、適切なラベルを使用します。
 
 ``` yaml
 jobs:
@@ -120,23 +119,21 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% data variables.product.prodname_code_scanning_capc %} は、macOS、Ubuntu、Windows の最新バージョンをサポートしています。 Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. 詳しい情報については、「[GitHub Actions のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)」および「[セルフホストランナーでラベルを使用する](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)」を参照してください。
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+セルフホストランナーの PATH 変数に Git が確実に含まれるようにしてください。
 
-{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
-
-### Changing the languages that are analyzed
+### 解析される言語を変更する
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix.
+If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix.
 
 ```yaml
 jobs:
@@ -157,7 +154,7 @@ If your workflow does not contain a matrix called `language`, then {% data varia
     languages: cpp, csharp, python
 ```
 {% if currentVersion == "free-pro-team@latest" %}
-### Analyzing Python dependencies
+### 追加のクエリを実行する
 
 For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
 
@@ -171,66 +168,76 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
-### Running additional queries
+### 追加のクエリを実行する
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow.
+1つ以上のクエリスイートを追加するには、設定ファイルに `queries` セクションを追加します。 If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     queries: COMMA-SEPARATED LIST OF PATHS
+    # Optional. Provide a token to access private repositories.
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+設定ファイルでこれらを指定して、追加のクエリスイートを実行することもできます。 クエリスイートはクエリのコレクションであり、通常は目的または言語ごとにグループ化されています。
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。
 
 In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     config-file: ./.github/codeql/codeql-config.yml
     queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
-### Using a custom configuration file
+### サードパーティのコードスキャンツールを使用する
 
 As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
 
-In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. この例では、設定ファイル _./.github/codeql/codeql-config.yml_ を読み込みます。
 
 ``` yaml
 - uses: github/codeql-action/init@v1
@@ -238,11 +245,21 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp
     config-file: ./.github/codeql/codeql-config.yml
 ```
 
-The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. 
+{% data reusables.code-scanning.custom-configuration-file %}
 
-The settings in the file are written in YAML format.
+If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository.
 
-#### Specifying additional queries
+{% raw %}
+```yaml
+uses: github/codeql-action/init@v1
+with:
+  external-repository-token: ${{ secrets.ACCESS_TOKEN }}
+```
+{% endraw %}
+
+The settings in the configuration file are written in YAML format.
+
+#### 追加のクエリを指定する
 
 You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
 
@@ -257,11 +274,11 @@ Optionally, you can give each array element a name, as shown in the example conf
 
 For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
 
-#### Disabling the default queries
+#### デフォルトのクエリを無効にする
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+カスタムクエリのみを実行する場合は、構成ファイルに `disable-default-queries: true` を追加して、デフォルトのセキュリティクエリを無効にすることができます。
 
-#### Specifying directories to scan
+#### スキャンするディレクトリを指定する
 
 For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
 
@@ -275,46 +292,28 @@ paths-ignore:
 
 {% note %}
 
-**Note**:
+**ノート**:
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)」を参照してください。
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. たとえば、`foo/**`、`**/foo`、および `foo/**/bar` はすべて使用できる構文ですが、`**foo` は使用できません。 ただし、例に示すように、単一の * を他の文字と一緒に使用できます。 You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
 
-For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. ビルドからディレクトリを除外するために使用するコマンドは、ビルドシステムによって異なります。 詳しい情報については、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+特定のディレクトリのコードを変更すると、monorepo の一部をすばやく分析できます。 ビルドステップでディレクトリを除外し、ワークフローファイルで [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) の`paths-ignore` および `paths` キーワードを使用する必要があります。
 
-#### Example configuration files
+#### 設定ファイルの例
 
 {% data reusables.code-scanning.example-configuration-files %}
 
-### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+### コンパイルされた言語の {% data variables.product.prodname_code_scanning %} を設定する
 
 {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)."
+{% data reusables.code-scanning.autobuild-add-build-steps %}コンパイルされた言語で {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を設定する方法に関する詳しい情報については、「[コンパイルされた言語の {% data variables.product.prodname_codeql %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)」を参照してください。
 
-### Accessing private repositories
+### {% data variables.product.prodname_code_scanning %} 用の設定ファイルを作成できます。
 
-If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs.<job_id>.steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
-
-For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable.
-
-{% raw %}
-```yaml
-steps:
-- name: Configure access to private repositories
-  env:
-    TOKEN: ${{ secrets.ACCESS_TOKEN }}
-  run: |
-    git config --global url."https://${TOKEN}@github.com/ghost/foo".insteadOf "https://github.com/ghost/foo"
-    git config --global url."https://${TOKEN}@github.com/ghost/bar".insteadOf "https://github.com/ghost/bar"
-    git config --global url."https://${TOKEN}@github.com/ghost/baz".insteadOf "https://github.com/ghost/baz"
-```
-{% endraw %}
-
-### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
-
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)."
+{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. ワークフローに `upload-sarif` アクションを追加することで、{% data variables.product.prodname_dotcom %} のサードパーティツールからのコード分析を表示できます。 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)」を参照してください。
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index d22d35c882..359c8484db 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring CodeQL code scanning in your CI system
-shortTitle: Configuring in your CI
-intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
+title: CI システムで CodeQL コードスキャンを設定する
+shortTitle: CI での設定
+intro: '{% data variables.product.prodname_codeql_runner %} がプロジェクトのコードをスキャンして、その結果を {% data variables.product.prodname_dotcom %} にアップロードする方法を設定できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 miniTocMaxHeadingLevel: 4
 versions:
@@ -10,29 +10,32 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-### About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+### CI システムにおける {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} の設定について
 
-To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+{% data variables.product.prodname_code_scanning %} をお使いの CI システムに統合するには、{% data variables.product.prodname_codeql_runner %} を使用できます。 詳しい情報については、「[CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」を参照してください。
 
-In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows.
+一般的に、{% data variables.product.prodname_codeql_runner %} は次のように呼び出します。
 
 ```shell
 $ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
 ```
 
-`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively.
+`/path/to-runner/` は、{% data variables.product.prodname_codeql_runner %} を CI のどこにダウンロードしたかによって異なります。 `codeql-runner-OS` は、お使いのオペレーティングシステムによって異なります。
+{% data variables.product.prodname_codeql_runner %} には 3 つのバージョンがあり、`codeql-runner-linux`、`codeql-runner-macos`、`codeql-runner-win` がそれぞれ Linux、macOS、Windows のシステムに対応しています。
 
-To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
+{% data variables.product.prodname_codeql_runner %} がコードをスキャンする方法をカスタマイズするには、`--languages` や `--queries` などのフラグを用いるか、別の設定ファイルでカスタム設定を指定します。
 
 ### プルリクエストをスキャンする
 
-Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code.
+プルリクエストが作成されるたびにコードをスキャンすることで、開発者がコードに新しい脆弱性やエラーを持ち込むことを防げます。
 
-To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch.
+プルリクエストをスキャンするには、 `analyze` コマンドを実行し、 `--ref` フラグを使用してプルリクエストを指定します。 リファレンスは `refs/pull/<PR-number>/head` または `refs/pull/<PR-number>/merge` で、プルリクエストブランチの HEAD コミットまたはベースブランチでマージコミットをチェックアウトしているかにより異なります。
 
 ```shell
 $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
@@ -40,19 +43,19 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 {% note %}
 
-**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`.
+**注釈**: コードをサードパーティーのツールで解析し、その結果をプルリクエストのチェックで表示したい場合は、`upload` コマンドを実行し、`--ref` フラグでブランチではなくプルリクエストを指定する必要があります。 リファレンスは `refs/pull/<PR-number>/head` または `refs/pull/<PR-number>/merge` です。
 
 {% endnote %}
 
 ### 自動言語検出をオーバーライドする
 
-The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
+{% data variables.product.prodname_codeql_runner %} は、サポートされている言語で記述されたコードを自動的に検出してスキャンします。
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. サポートされている言語のキーワードは、`cpp`、`csharp`、`go`、`java`、`JavaScript`、および `python` です。
+自動言語検出をオーバーライドするには、`init` コマンドに `--languages` フラグを付け、その後に言語のキーワードリストをカンマ区切りで追加して、実行します。 The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
@@ -64,11 +67,11 @@ $ /path/to-runner/codeql-runner-linux init --languages cpp,java
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
+1 つ以上ののクエリを追加するには、`init` コマンドの `--queries` フラグに、カンマで区切ったパスのリストを渡します。 設定ファイルに、追加のクエリを指定することもできます。
 
-If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file. If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to <nobr>`--queries`</nobr> with the `+` symbol. 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。
+カスタム設定にも設定ファイルを使用し、`--queries` フラグで追加のクエリも指定している場合、{% data variables.product.prodname_codeql_runner %} は、構成ファイルで指定されたものではなく、 <nobr>`--queries`</nobr> フラグで指定された追加クエリを使用します。 フラグで指定された追加クエリと、設定ファイルにある追加クエリを組み合わせて使用する場合、渡す値の前に <nobr>`--queries`</nobr> と `+` の記号をプレフィクスとして付けてください。 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。
 
-In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
+次の例では、{% data variables.product.prodname_codeql_runner %} が追加のクエリを、参照されている設定ファイルの中で指定されたあらゆるクエリと共に使用するよう、`+` の記号を用いています。
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
@@ -77,11 +80,11 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c
 
 ### サードパーティのコードスキャンツールを使用する
 
-Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file.
+{% data variables.product.prodname_codeql_runner %} コマンドに追加情報を渡すかわりに、別の設定ファイルでカスタム設定を指定できます。
 
-The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)」を参照してください。
+設定ファイルの形式は YAML ファイルです。 YAML ファイルは、以下の例で示すように、{% data variables.product.prodname_actions %} のワークフロー構文と似た構文を使用します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)」を参照してください。
 
-Use the `--config-file` flag of the `init` command to specify the configuration file. The value of <nobr>`--config-file`</nobr> is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_.
+`init` コマンドの `--config-file` フラグを使用して、設定ファイルを指定します。   <nobr>`--config-file`</nobr> の値は、使用する設定ファイルへのパスです。 この例では、設定ファイル _.github/codeql/codeql-config.yml_ を読み込みます。
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
@@ -95,99 +98,99 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c
 
 ### コンパイルされた言語の {% data variables.product.prodname_code_scanning %} を設定する
 
-For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+コンパイル言語の C/C++、C#、および Java では、{% data variables.product.prodname_codeql %} は解析前にコードをビルドします。 {% data reusables.code-scanning.analyze-go %}
 
-For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first.
+多くの一般的なビルドシステムに対して、{% data variables.product.prodname_codeql_runner %} はコードを自動的にビルドできます。 コードの自動的なビルドを試行するには、`init` と `analyze` のステップの間で `autobuild` を実行します。 リポジトリに特定のバージョンのビルドツールが必要な場合は、まずそのビルドツールを手動でインストールする必要があることにご注意ください。
 
-The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command.
+`autobuild` プロセスは、リポジトリに対して _1 つ_ のコンパイル型言語のみをビルドするよう試行します。 解析のために自動的に選択される言語は、使用されているファイル数が最も多い言語です。 言語を明示的に選択する場合は、`autobuild` コマンドの `--language` フラグを使用します。
 
 ```shell
 $ /path/to-runner/codeql-runner-linux autobuild --language csharp
 ```
 
-If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system#compiled-language-example)."
+`autobuild` コマンドがコードをビルドできない場合、`init` と`analyze` のステップの間にビルドのステップを手動で実行できます。 詳しい情報については、「[CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system#compiled-language-example)」を参照してください。
 
 ### {% data variables.product.prodname_code_scanning %} 用の設定ファイルを作成できます。
 
-By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
+デフォルトでは、{% data variables.product.prodname_codeql_runner %} は `analyze` コマンドを実行した際の {% data variables.product.prodname_code_scanning %} による結果をアップロードします。 また、`upload` コマンドを使用して、SARIF ファイルを別にアップロードすることもできます。
 
-Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository.
-- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
-- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+データをアップロードすると、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。
+- `--ref refs/pull/42/merge` や `--ref refs/pull/42/head` などのようにプルリクエストにアップロードした場合、結果はプルリクエストのチェックでアラートとして表示されます。 詳しい情報については、「[プルリクエストでコードスキャンアラートをトリアージする](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
+- `--ref refs/heads/my-branch` といったようにブランチにアップロードした場合、結果はリポジトリの [**Security**] タブに表示されます。 詳しい情報については、「[リポジトリの コードスキャンアラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。
 
-### {% data variables.product.prodname_codeql_runner %} command reference
+### {% data variables.product.prodname_codeql_runner %} コマンドのリファレンス
 
-The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags.
+{% data variables.product.prodname_codeql_runner %} は、次のコマンドおよびフラグをサポートしています。
 
 #### `init`
 
-Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
+{% data variables.product.prodname_codeql_runner %} を初期化し、解析する各言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
 
-| Flag                             | 必須 | Input value                                                                                                                                                                         |
-| -------------------------------- |:--:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--repository`                   | ✓  | Name of the repository to initialize.                                                                                                                                               |
-| `--github-url`                   | ✓  | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                   |
-| `--github-auth`                  | ✓  | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                               |
-| `--languages`                    |    | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. |
-| `--queries`                      |    | Comma-separated list of additional queries to run, in addition to the default suite of security queries.                                                                            |
-| `--config-file`                  |    | Path to custom configuration file.                                                                                                                                                  |
-| `--codeql-path`                  |    | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy.   |
-| `--temp-dir`                     |    | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                       |
-| `--tools-dir`                    |    | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory.                    |
-| <nobr>`--checkout-path`</nobr> |    | The path to the checkout of your repository. The default is the current working directory.                                                                                          |
-| `--debug`                        |    | なし. Prints more verbose output.                                                                                                                                                     |
-| `-h`, `--help`                   |    | なし. Displays help for the command.                                                                                                                                                  |
+| フラグ                              | 必須 | 入力値                                                                                                                                                |
+| -------------------------------- |:--:| -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                   | ✓  | 初期化するリポジトリの名前。                                                                                                                                     |
+| `--github-url`                   | ✓  | リポジトリがホストされる {% data variables.product.prodname_dotcom %} のインスタンス。                                                                                 |
+| `--github-auth`                  | ✓  | {% data variables.product.prodname_github_apps %} トークンまたは個人アクセストークン。                                                                             |
+| `--languages`                    |    | 解析対象言語のカンマ区切りリスト。 デフォルトでは、{% data variables.product.prodname_codeql_runner %} はリポジトリにあるサポートされている言語をすべて検出し、解析します。                                 |
+| `--queries`                      |    | デフォルトのセキュリティクエリに加えて実行する、追加クエリのカンマ区切りリスト。                                                                                                           |
+| `--config-file`                  |    | カスタム設定ファイルのパス。                                                                                                                                     |
+| `--codeql-path`                  |    | 使用する {% data variables.product.prodname_codeql %} CLI 実行ファイルのコピーのパス。 デフォルトでは、{% data variables.product.prodname_codeql_runner %} はコピーをダウンロードします。 |
+| `--temp-dir`                     |    | 一時ファイルが保存されるディレクトリ。 デフォルトは `./codeql-runner` です。                                                                                                   |
+| `--tools-dir`                    |    | 実行間で {% data variables.product.prodname_codeql %} ツールやその他のファイルが保存されるディレクトリ。 デフォルトはホームディレクトリのサブディレクトリです。                                            |
+| <nobr>`--checkout-path`</nobr> |    | リポジトリをチェックアウトするパス。 デフォルトは現在のワーキングディレクトリです。                                                                                                         |
+| `--debug`                        |    | なし. より詳細な出力を表示します。                                                                                                                                 |
+| `-h`, `--help`                   |    | なし. コマンドのヘルプを表示します。                                                                                                                                |
 
 #### `autobuild`
 
-Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps.
+コンパイル型言語である C/C++、C#、および Java のコードのビルドを試行します。 これらの言語では、{% data variables.product.prodname_codeql %} は解析前にコードをビルドします。 `autobuild` を、`init` と `analyze` のステップの間に実行します。
 
-| Flag                        | 必須 | Input value                                                                                                                                    |
-| --------------------------- |:--:| ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--language`                |    | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. |
-| <nobr>`--temp-dir`</nobr> |    | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                  |
-| `--debug`                   |    | なし. Prints more verbose output.                                                                                                                |
-| `-h`, `--help`              |    | なし. Displays help for the command.                                                                                                             |
+| フラグ                         | 必須 | 入力値                                                                                                |
+| --------------------------- |:--:| -------------------------------------------------------------------------------------------------- |
+| `--language`                |    | ビルドする言語。 デフォルトでは、{% data variables.product.prodname_codeql_runner %} はファイル数が最も多いコンパイル型言語をビルドします。 |
+| <nobr>`--temp-dir`</nobr> |    | 一時ファイルが保存されるディレクトリ。 デフォルトは `./codeql-runner` です。                                                   |
+| `--debug`                   |    | なし. より詳細な出力を表示します。                                                                                 |
+| `-h`, `--help`              |    | なし. コマンドのヘルプを表示します。                                                                                |
 
 #### `analyze`
 
-Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}.
+{% data variables.product.prodname_codeql %} データベースにあるコードを解析し、結果を {% data variables.product.product_name %} にアップロードします。
 
-| Flag                               | 必須 | Input value                                                                                                                                                                                                                            |
-| ---------------------------------- |:--:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--repository`                     | ✓  | Name of the repository to analyze.                                                                                                                                                                                                     |
-| `--commit`                         | ✓  | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                        |
-| `--ref`                            | ✓  | Name of the reference to analyze, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
-| `--github-url`                     | ✓  | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                      |
-| `--github-auth`                    | ✓  | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                  |
-| <nobr>`--checkout-path`</nobr>   |    | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                             |
-| `--no-upload`                      |    | なし. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}.                                                                                           |
-| `--output-dir`                     |    | Directory where the output SARIF files are stored. The default is in the directory of temporary files.                                                                                                                                 |
-| `--ram`                            |    | Amount of memory to use when running queries. The default is to use all available memory.                                                                                                                                              |
-| <nobr>`--no-add-snippets`</nobr> |    | なし. Excludes code snippets from the SARIF output.                                                                                                                                                                                      |
-| `--threads`                        |    | Number of threads to use when running queries. The default is to use all available cores.                                                                                                                                              |
-| `--temp-dir`                       |    | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                                                                          |
-| `--debug`                          |    | なし. Prints more verbose output.                                                                                                                                                                                                        |
-| `-h`, `--help`                     |    | なし. Displays help for the command.                                                                                                                                                                                                     |
+| フラグ                                | 必須 | 入力値                                                                                                                                                           |
+| ---------------------------------- |:--:| ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     | ✓  | 解析するリポジトリの名前。                                                                                                                                                 |
+| `--commit`                         | ✓  | 解析するコミットの SHA。 Git および Azure DevOps では、`git rev-parse HEAD` の値に相当します。 Jenkins では、`$GIT_COMMIT` に相当します。                                                        |
+| `--ref`                            | ✓  | 解析するレファレンスの名前 (例: `refs/heads/main`、`refs/pull/42/merge`)。 Git や Jenkins では、`git symbolic-ref HEAD` の値に相当します。 Azure DevOps では、`$(Build.SourceBranch)` に相当します。 |
+| `--github-url`                     | ✓  | リポジトリがホストされる {% data variables.product.prodname_dotcom %} のインスタンス。                                                                                            |
+| `--github-auth`                    | ✓  | {% data variables.product.prodname_github_apps %} トークンまたは個人アクセストークン。                                                                                        |
+| <nobr>`--checkout-path`</nobr>   |    | リポジトリをチェックアウトするパス。 デフォルトは現在のワーキングディレクトリです。                                                                                                                    |
+| `--no-upload`                      |    | なし. {% data variables.product.prodname_codeql_runner %} が結果を {% data variables.product.product_name %} にアップロードすることを停止します。                                   |
+| `--output-dir`                     |    | 出力される SARIF ファイルが保存されるディレクトリ。 デフォルトは一時ファイルのディレクトリです。                                                                                                          |
+| `--ram`                            |    | クエリの実行時に使用するメモリの量。 デフォルトでは、使用できるすべてのメモリを使用します。                                                                                                                |
+| <nobr>`--no-add-snippets`</nobr> |    | なし. SARIF 出力からコードスニペットを除外します。                                                                                                                                 |
+| `--threads`                        |    | クエリの実行時に使用するスレッドの数。 デフォルトでは、使用できるすべてのコアを使用します。                                                                                                                |
+| `--temp-dir`                       |    | 一時ファイルが保存されるディレクトリ。 デフォルトは `./codeql-runner` です。                                                                                                              |
+| `--debug`                          |    | なし. より詳細な出力を表示します。                                                                                                                                            |
+| `-h`, `--help`                     |    | なし. コマンドのヘルプを表示します。                                                                                                                                           |
 
 #### `アップロード`
 
-Uploads SARIF files to {% data variables.product.product_name %}.
+SARIF ファイルを {% data variables.product.product_name %} にアップロードします。
 
 {% note %}
 
-**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools.
+**注釈**: CodeQL ランナーでコードを解析する場合、`analyze` コマンドはデフォルトで SARIF の結果をアップロードします。 `upload` コマンドを使用して、他のツールで生成された SARIF の結果をアップロードできます。
 
 {% endnote %}
 
-| Flag                             | 必須 | Input value                                                                                                                                                                                                                                   |
-| -------------------------------- |:--:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--sarif-file`                   | ✓  | SARIF file to upload, or a directory containing multiple SARIF files.                                                                                                                                                                         |
-| `--repository`                   | ✓  | Name of the repository that was analyzed.                                                                                                                                                                                                     |
-| `--commit`                       | ✓  | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                        |
-| `--ref`                          | ✓  | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
-| `--github-url`                   | ✓  | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                             |
-| `--github-auth`                  | ✓  | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                         |
-| <nobr>`--checkout-path`</nobr> |    | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                    |
-| `--debug`                        |    | なし. Prints more verbose output.                                                                                                                                                                                                               |
-| `-h`, `--help`                   |    | なし. Displays help for the command.                                                                                                                                                                                                            |
+| フラグ                              | 必須 | 入力値                                                                                                                                                           |
+| -------------------------------- |:--:| ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   | ✓  | アップロードする SARIF ファイル、または複数の SARIF ファイルを含むディレクトリ。                                                                                                               |
+| `--repository`                   | ✓  | 解析したリポジトリの名前。                                                                                                                                                 |
+| `--commit`                       | ✓  | 解析したコミットの SHA。 Git および Azure DevOps では、`git rev-parse HEAD` の値に相当します。 Jenkins では、`$GIT_COMMIT` に相当します。                                                        |
+| `--ref`                          | ✓  | 解析したレファレンスの名前 (例: `refs/heads/main`、`refs/pull/42/merge`)。 Git や Jenkins では、`git symbolic-ref HEAD` の値に相当します。 Azure DevOps では、`$(Build.SourceBranch)` に相当します。 |
+| `--github-url`                   | ✓  | リポジトリがホストされる {% data variables.product.prodname_dotcom %} のインスタンス。                                                                                            |
+| `--github-auth`                  | ✓  | {% data variables.product.prodname_github_apps %} トークンまたは個人アクセストークン。                                                                                        |
+| <nobr>`--checkout-path`</nobr> |    | リポジトリをチェックアウトするパス。 デフォルトは現在のワーキングディレクトリです。                                                                                                                    |
+| `--debug`                        |    | なし. より詳細な出力を表示します。                                                                                                                                            |
+| `-h`, `--help`                   |    | なし. コマンドのヘルプを表示します。                                                                                                                                           |
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index e9c68623d0..8758716f31 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring the CodeQL workflow for compiled languages
+title: コンパイル型言語で用いる CodeQL のワークフローを設定する
 shortTitle: コンパイルされた言語を設定する
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.product.prodname_codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.'
+intro: '{% data variables.product.prodname_dotcom %} が {% data variables.product.prodname_codeql_workflow %} を使用してコンパイル型言語で記述されたコードの脆弱性やエラーをスキャンする方法を設定できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
 versions:
@@ -10,46 +10,43 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
+### {% data variables.product.prodname_codeql_workflow %} とコンパイル型言語について
 
-You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
+{% data variables.product.prodname_dotcom %} がリポジトリに対して {% data variables.product.prodname_code_scanning %} を実行できるようにするには、{% data variables.product.prodname_actions %} ワークフローをリポジトリに追加します。 **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」を参照してください。
 
 {% data reusables.code-scanning.edit-workflow %}
-For general information about configuring
-{% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and  "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+{% data variables.product.prodname_code_scanning %} の設定とワークフローファイルの編集に関する一般的な情報については、 「[{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning) を設定する」および「[{% data variables.product.prodname_actions %} について学ぶ](/actions/learn-github-actions)」を参照してください。
 
 ### {% data variables.product.prodname_codeql %} の autobuild について
 
-Code scanning works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository. For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
+コードスキャンは、1 つ以上のデータベースに対してクエリを実行することにより機能します。 各データベースには、リポジトリにあるすべてのコードを 1 つの言語で表わしたものが含まれています。 コンパイル型言語の C/C++、C#、および Java では、このデータベースを生成するプロセスに、コードのビルドとデータの抽出が含まれています。 {% data reusables.code-scanning.analyze-go %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %}
 
-If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands.
+ワークフローが `language` マトリクスを使用している場合、`autobuild` はマトリクスに列記された各コンパイル型言語のビルドを試行します。 マトリクスがない場合、`autobuild` はリポジトリ内でソースファイルの数が最も多い、サポートされているコンパイル型言語のビルドを試行します。 Go を除いて、明示的にビルドコマンドを使用しない限り、リポジトリにある他のコンパイル型言語の解析は失敗します。
 
 {% note %}
 
-{% if currentVersion == "github-ae@latest" %}**Note**: For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
-{% else %}
-**Note**: If you use self-hosted runners for
-{% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. さらに、リポジトリに特定のバージョンのビルドツールが必要な場合は、手動でインストールする必要があります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。
-{% endif %}
+**注釈**: {% data variables.product.prodname_actions %} にセルフホストランナーを使用する場合、`autobuild` プロセスを使用するために追加のソフトウェアをインストールする必要がある場合があります。 さらに、リポジトリに特定のバージョンのビルドツールが必要な場合は、手動でインストールする必要があります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。
 
 {% endnote %}
 
 #### C/C++
 
-| サポートされているシステムの種類 | システム名                                                                                                                                          |
-| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| オペレーティングシステム     | Windows, macOS, and Linux                                                                                                                      |
-| ビルドシステム          | Windows: MSbuild and build scripts<br/>Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
+| サポートされているシステムの種類 | システム名                                                                                                                       |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| オペレーティングシステム     | Windows、macOS、Linux                                                                                                         |
+| ビルドシステム          | Windows: MSbuild およびビルドスクリプト<br/>Linux および macOS: Autoconf、Make、CMake、qmake、 Meson、Waf、SCons、Linux Kbuild、およびビルドスクリプト |
 
 `autobuild` ステップの動作は、抽出を実行するオペレーティングシステムによって異なります。 On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
 
-1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root. `autobuild` が最上位ディレクトリから同じ（最短）深度で複数のソリューションまたはプロジェクトファイルを検出した場合、それらすべてをビルドしようとします。
-2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
+1. ルートに最も近いソリューション (`.sln`) またはプロジェクト (`.vcxproj`) ファイルで `MSBuild.exe` を呼び出します。 `autobuild` が最上位ディレクトリから同じ（最短）深度で複数のソリューションまたはプロジェクトファイルを検出した場合、それらすべてをビルドしようとします。
+2. ビルドスクリプトのように見えるスクリプト、つまり _build.bat_、_build.cmd_、_および build.exe_ を、この順番で呼び出します。
 
 On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
 
@@ -72,10 +69,10 @@ On Linux and macOS, the `autobuild` step reviews the files present in the reposi
 
 #### Java
 
-| サポートされているシステムの種類 | システム名                                      |
-| ---------------- | ------------------------------------------ |
-| オペレーティングシステム     | Windows, macOS, and Linux (no restriction) |
-| ビルドシステム          | Gradle、Maven、Ant                           |
+| サポートされているシステムの種類 | システム名                      |
+| ---------------- | -------------------------- |
+| オペレーティングシステム     | Windows、macOS、Linux (制限なし) |
+| ビルドシステム          | Gradle、Maven、Ant           |
 
 `autobuild` プロセスは、この戦略を適用して Java コードベースのビルドシステムを決定しようとします。
 
@@ -85,7 +82,7 @@ On Linux and macOS, the `autobuild` step reviews the files present in the reposi
 
 ### コンパイル言語のビルドステップを追加する
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
+{% data reusables.code-scanning.autobuild-add-build-steps %}ワークフローファイルの編集方法については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。
 
 `autobuild` ステップを削除した後、`run` ステップのコメントを外して、リポジトリに適したビルドコマンドを追加します。 ワークフロー `run` ステップは、オペレーティングシステムのシェルを使用してコマンドラインプログラムを実行します。 これらのコマンドを変更し、さらにコマンドを追加して、ビルドプロセスをカスタマイズできます。
 
@@ -113,6 +110,6 @@ If your repository contains multiple compiled languages, you can specify languag
 
 For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
 
-For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)."
+`autobuild` がコードをビルドしない理由に関するヒントやビルドの方法については、「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)」を参照してください。
 
 If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}.
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index 3b3edc0142..51b4c3dac8 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### 目次
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 25fb7e862d..481e02806a 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -1,7 +1,7 @@
 ---
-title: Integrating with code scanning
-shortTitle: Integration
-intro: 'You can integrate third-party code analysis tools with {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %} by uploading data as SARIF files.'
+title: コードスキャンと統合する
+shortTitle: インテグレーション
+intro: 'データを SARIF ファイルとしてアップロードすることで、サードパーティーのコード解析ツールを{% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %} と統合できます。'
 mapTopic: true
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index b0cb3e0284..7bfff5e9b6 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,127 +1,73 @@
 ---
-title: Managing code scanning alerts for your repository
+title: リポジトリのコードスキャンアラートを管理する
 shortTitle: アラートを管理する
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: セキュリティビューから、プロジェクトのコードに存在する潜在的な脆弱性やエラーのアラートを表示、修正、および閉じることができます。
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### {% data variables.product.prodname_code_scanning %} からのアラートについて
 
-You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
+デフォルトの {% data variables.product.prodname_codeql %} 解析、サードパーティーの解析、または複数のタイプの解析を使用して、リポジトリのコードをチェックするため、{% data variables.product.prodname_code_scanning %} をセットアップできます。 解析が完了すると、解析によるアラートがリポジトリのセキュリティビューに隣り合わせで表示されます。 サードパーティツールまたはカスタムクエリの結果には、{% data variables.product.company_short %} のデフォルト {% data variables.product.prodname_codeql %} 解析により検出されたアラートで表示されるプロパティの一部が含まれていない場合があります。 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」を参照してください。
 
-By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
+デフォルトでは、{% data variables.product.prodname_code_scanning %} はプルリクエスト中にデフォルトブランチのコードを定期的に解析します。 プルリクエストでアラートを管理する方法については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-### About alerts details
+### アラートの詳細について
 
-Each alert highlights a problem with the code and the name of the tool that identified it. アラートをトリガーしたコード行と、アラートのプロパティ（問題の重要度や性質など）を確認できます。 アラートは、問題が最初に発生したときにも通知します。 For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
+各アラートはコードの問題と、それを特定したツールの名前を表示します。 アラートをトリガーしたコード行と、アラートのプロパティ（問題の重要度や性質など）を確認できます。 アラートは、問題が最初に発生したときにも通知します。 {% data variables.product.prodname_codeql %} 解析で特定されたアラートについては、問題を解説する方法についての情報も表示されます。
 
 ![{% data variables.product.prodname_code_scanning %} からのアラートの例](/assets/images/help/repository/code-scanning-alert.png)
 
-If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
+{% data variables.product.prodname_codeql %} を使用して {% data variables.product.prodname_code_scanning %} をセットアップした場合、コード内のデータフロー問題も検出できます。 データフロー解析は、データを安全でない方法で利用する、関数に危険な引数を渡す、機密情報を漏洩するなど、コードにおける潜在的なセキュリティ問題を検出します。
 
-{% data variables.product.prodname_code_scanning %} がデータフローアラートを報告すると、{% data variables.product.prodname_dotcom %} はデータがコードを通してどのように移動するかを示します。 {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
+{% data variables.product.prodname_code_scanning %} がデータフローアラートを報告すると、{% data variables.product.prodname_dotcom %} はデータがコードを通してどのように移動するかを示します。 {% data variables.product.prodname_code_scanning_capc %} を使用すると、機密情報を漏洩し、悪意のあるユーザによる攻撃の入り口になる可能性があるコードの領域を特定できます。
 
-### Viewing the alerts for a repository
+### リポジトリのアラートを表示する
 
-Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
+リポジトリへの書き込み権限があるユーザなら誰でも、プルリクエストの {% data variables.product.prodname_code_scanning %} アノテーションを表示できます。 詳しい情報については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
 
-You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch.
+[**Security**] タブでリポジトリのすべてのアラートの概要を表示するには、書き込み権限が必要です。 デフォルトでは、アラートはデフォルトブランチに対して表示されます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. ![Summary of alerts](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png)
-1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
+1. [{% data variables.product.prodname_code_scanning_capc %}] で、調査するアラートをクリックします。 ![アラートの概要](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
+1. アラートでデータフローの問題が強調表示された場合は、必要に応じて [**Show paths**] をクリックし、データソースから、それが使用されているシンクまでのパスを表示します。 ![アラートの [Show paths] リンク](/assets/images/help/repository/code-scanning-show-paths.png)
+1. {% data variables.product.prodname_codeql %} 解析によるアラートには、問題の説明も含まれています。 コードを修正する方法についてのガイダンスを表示するには、[**Show more**] をクリックします。 ![アラートの詳細情報](/assets/images/help/repository/code-scanning-alert-details.png)
 
-### Fixing an alert
+### アラートを解決する
 
-Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
+リポジトリへの書き込み権限があるユーザなら誰でも、コードに修正をコミットしてアラートを解決できます。 リポジトリでプルリクエストに対して {% data variables.product.prodname_code_scanning %} が実行されるよう予定されている場合は、修正してプルリクエストを発行するようお勧めします。 これにより、変更の {% data variables.product.prodname_code_scanning %} 解析がトリガーされ、修正で新しい問題が入り込まないようテストされます。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning) を設定する」および「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+リポジトリへの書き込み権限がある場合は、アラートの概要を表示して、[**Closed**] をクリックすることで、解決したアラートを表示できます。 詳しい情報については、「[リポジトリのアラートを表示する](#viewing-the-alerts-for-a-repository)」を参照してください。 [Ｃlosed] リストには、解決されたアラートと、ユーザがクローズしたアラートが表示されます。
 
-Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
+あるブランチでは解決されたアラートが、別のブランチでは解決されていないことがあります。 アラートの概要で [Branch] ドロップダウンメニューを使用し、特定のブランチでアラートが解決されたかどうか確認できます。
 
-![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
-
-{% if currentVersion == "enterprise-server@2.22" %}
+![ブランチによるアラートのフィルタリング](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
 ### アラートを閉じる
 
-Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
-### Dismissing or deleting alerts
-
-There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
-
-Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
-
-When you dismiss an alert:
-
-- It's dismissed in all branches.
-- The alert is removed from the number of current alerts for your project.
-- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required.
-- The reason why you closed the alert is recorded.
-- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert.
-
-When you delete an alert:
-
-- It's deleted in all branches.
-- The alert is removed from the number of current alerts for your project.
-- It is _not_ added to the "Closed" list in the summary of alerts.
-- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.
-
-To dismiss or delete alerts:
-
-{% endif %}
+アラートを閉じることは、修正する必要がないと思われるアラートを解決する方法のひとつです。 {% data reusables.code-scanning.close-alert-examples %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
-1. Select the **Close** drop-down menu and click a reason for closing the alert.    
-   ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
+1. [**Close**] ドロップダウンメニューを選択肢、アラートを閉じる理由をクリックします。    
+   ![[Close] ドロップダウンでアラートを閉じる理由を選択する](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
-
-   ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   Optionally, you can use the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
-
-  ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
-
-  ![Open an alert from the summary list](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### Dismissing multiple alerts at once
-
-If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
-
-{% endif %}
-
 ### 参考リンク
 
-- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
-- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)"
-- "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)"
+- 「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)」
+- 「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」
+- 「[{% data variables.product.prodname_code_scanning %} からのアラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)」
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index 018d5e7687..29670a2eed 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -1,7 +1,7 @@
 ---
-title: Running CodeQL code scanning in a container
-shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container'
-intro: 'You can run {% data variables.product.prodname_code_scanning %} in a container by ensuring that all processes run in the same container.'
+title: コンテナで CodeQL コードスキャンを実行する
+shortTitle: 'コンテナで {% data variables.product.prodname_code_scanning_capc %}'
+intro: 'すべてのプロセスが同じコンテナで動作するようにすることで、{% data variables.product.prodname_code_scanning %} を実行できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   enterprise-server: '2.22'
@@ -9,17 +9,19 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
-### About {% data variables.product.prodname_code_scanning %} with a containerized build
+### コンテナ化されたビルドで {% data variables.product.prodname_code_scanning %} を使用することについて
 
-If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.
+コンパイル言語用に {% data variables.product.prodname_code_scanning %} をセットアップし、コンテナ化された環境でコードをビルドしようとすると、解析が失敗し、"No source code was seen during the build." というエラーメッセージが出る場合があります。 これは、コードがコンパイルされているので {% data variables.product.prodname_codeql %} がコードをモニターできなかったことを示しています。
 
-You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% data variables.product.prodname_codeql %} は、コードをビルドしたのと同じコンテナで実行する必要があります。 これは、使用しているのが {% data variables.product.prodname_codeql_runner %} であれ {% data variables.product.prodname_actions %} であれ同様です。 {% data variables.product.prodname_codeql_runner %} を使用している場合は、コードをビルドするコンテナで実行します。 {% data variables.product.prodname_codeql_runner %} に関する詳しい情報については、「[CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」を参照してください。 {% data variables.product.prodname_actions %} を使用している場合は、同じコンテナですべてのアクションを実行するようワークフローを設定します。 詳しい情報については「[ワークフローの例](#example-workflow)」を参照してください。
 
 ### 依存関係
 
-You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations:
+使用しているコンテナで特定の依存関係がない場合 (たとえば、Git は PATH 変数にインストールされ、追加されている必要がある)、{% data variables.product.prodname_code_scanning %} を実行する上で困難が生じる場合があります。 依存関係の問題が生じた場合は、{% data variables.product.prodname_dotcom %} の仮想環境に通常含まれているソフトウェアのリストを確認してください。 詳しい情報については、次の場所にある特定のバージョンの `readme` ファイルを参照してください。
 
 * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux
 * macOS: https://github.com/actions/virtual-environments/tree/main/images/macos
@@ -27,7 +29,7 @@ You may have difficulty running {% data variables.product.prodname_code_scanning
 
 ### ワークフローの例
 
-This sample workflow uses {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis in a containerized environment. The value of `container.image` identifies the container to use. In this example the image is named `codeql-container`, with a tag of `f0f91db`. 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。
+このサンプルワークフローでは、{% data variables.product.prodname_actions %} を使用して、コンテナ化された環境において {% data variables.product.prodname_codeql %} 解析を実行します。 `container.image` の値で、使用するコンテナを指定します。 この例では、イメージ名は `codeql-container` で、`f0f91db` のタグが付いています。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。
 
 ``` yaml
 name: "{% data variables.product.prodname_codeql %}"
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index 4a4b8bffdb..e4987540b1 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-title: Running CodeQL code scanning in your CI system
-shortTitle: Running in your CI
-intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+title: CI システムで CodeQL コードスキャンを実行する
+shortTitle: CI での実行
+intro: '{% data variables.product.prodname_codeql_runner %} を使用して、、サードパーティの継続的インテグレーションシステムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   enterprise-server: '2.22'
@@ -9,38 +9,35 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-### Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system
+### 既存の CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を使用する
 
-If you use a continuous integration or continuous delivery/deployment (CI/CD) system other than {% data variables.product.prodname_actions %}, you can use your existing system to run {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql %} analysis and upload the results to {% data variables.product.prodname_dotcom %}. To do this, use the {% data variables.product.prodname_codeql_runner %}.
+{% data variables.product.prodname_actions %} 以外の継続的インテグレーションまたは継続的デリバリ/デプロイメント (CI/CD) システムを使用している場合、{% data variables.product.prodname_dotcom %} の {% data variables.product.prodname_codeql %} 解析を実行して、その結果を {% data variables.product.prodname_dotcom %} にアップロードできます。 これを実行するには、{% data variables.product.prodname_codeql_runner %} を使用します。
 
 ### {% data variables.product.prodname_codeql_runner %} について
 
-{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+{% data reusables.code-scanning.about-code-scanning %}詳細については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。
 
-You can use the {% data variables.product.prodname_codeql_runner %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
+{% data variables.product.prodname_codeql_runner %} を使用して、サードパーティ継続的インテグレーション (CI) システムで処理しているコード上で {% data variables.product.prodname_code_scanning %} を実行できます。 また、{% data variables.product.prodname_actions %} を使用して、{% data variables.product.product_name %} 上で {% data variables.product.prodname_code_scanning %} を実行することもできます。 詳細については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」を参照してください。
 
-The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
+{% data variables.product.prodname_codeql_runner %} は、{% data variables.product.prodname_dotcom %} リポジトリのチェックアウト中に {% data variables.product.prodname_codeql %} 解析を実行するコマンドラインツールです。 サードパーティーのシステムにランナーを追加し、ランナーを呼び出してコードを解析し、その結果を {% data variables.product.product_name %} にアップロードします。 この結果は、リポジトリの {% data variables.product.prodname_code_scanning %} アラートとして表示されます。
 
 {% note %}
 
 **ノート:**
-{% if currentVersion == "free-pro-team@latest" %}
-* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. {% data variables.product.prodname_dotcom_the_website %}上で管理されるパブリックリポジトリでの使用は無料であり、{% data variables.product.prodname_advanced_security %}ライセンスを持つお客様が所有するプライベートリポジトリ上で使用できます。 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
-{% else %}
 * The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
-{% endif %}
 * The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
 {% endnote %}
 
-### Downloading the {% data variables.product.prodname_codeql_runner %}
+### {% data variables.product.prodname_codeql_runner %} をダウンロードする
 
-You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+{% data variables.product.prodname_codeql_runner %} は、https://github.com/github/codeql-action/releases からダウンロードできます。 一部のオペレーティングシステムでは、ダウンロードしたファイルの実行前に、その権限を変更する必要があります。
 
 Linuxの場合:
 
@@ -57,51 +54,50 @@ sudo xattr -d com.apple.quarantine codeql-runner-macos
 
 On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
 
-### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system
+### {% data variables.product.prodname_codeql_runner %} を CI システムに追加する
 
 Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
-In addition to this, each CI server also needs:
+これに加えて、各 CI サーバーは以下の条件も満たす必要があります。
 
-- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+- {% data variables.product.prodname_codeql_runner %} が使用するための {% data variables.product.prodname_github_app %} または個人アクセストークン。 `repo` スコープのあるアクセストークン、または `security_events` の書き込み権限、ならびに `metadata` および `contents` の読み取り権限を持つ {% data variables.product.prodname_github_app %} を使用する必要があります。 詳細は「[{% data variables.product.prodname_github_apps %} をビルドする](/developers/apps/building-github-apps)」および「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
+- {% data variables.product.prodname_codeql_runner %} のリリースに伴う {% data variables.product.prodname_codeql %} バンドルへのアクセス。 このパッケージには、{% data variables.product.prodname_codeql %} 解析に必要なクエリとライブラリ、さらにランナーによって内部的に使用される {% data variables.product.prodname_codeql %} CLI が含まれています。 詳細は「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
 
-The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+{% data variables.product.prodname_codeql %} バンドルにアクセスを与えるオプションは次の通りです。
 
-1. Allow the CI servers access to https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
-{% if currentVersion == "enterprise-server@2.22" %}
-1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
-1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
+1. CI サーバーに https://github.com/github/codeql-action へのアクセスを許可し、{% data variables.product.prodname_codeql_runner %} がバンドルを自動的にダウンロードできるようにする。
+1. {% data variables.product.product_name %} に `github/codeql-action` リポジトリをミラーする。   <nobr>`--codeql-path`</nobr> フラグを指定してない限り、ランナーは {% data variables.product.prodname_dotcom_the_website %} のこの場所にバンドルがあるかどうか自動的に確認します。
+1. バンドルを手動でダウンロード/展開し、他の中央リソースに保存して、 <nobr>`--codeql-path`</nobr> フラグで、呼び出しにおいて {% data variables.product.prodname_codeql_runner %} を初期化するバンドルの場所を指定します。
 
-### Calling the {% data variables.product.prodname_codeql_runner %}
+### {% data variables.product.prodname_codeql_runner %} を呼び出す
 
-You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+解析するリポジトリのチェックアウトの場所から、{% data variables.product.prodname_codeql_runner %} を呼び出す必要があります。 主なコマンドは次の 2 つです。
 
-1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
-1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
+1. `init` は、ランナーを初期化し、解析する各言語に {% data variables.product.prodname_codeql %} データベースを作成するために必要です。 このデータベースは、続くコマンドにより展開、解析されます。
+1. `analyze` は、{% data variables.product.prodname_codeql %} データベースを展開、解析し、結果を {% data variables.product.product_name %} にアップロードするために必要です。
 
 For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
 
-You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
+将来の解析のため {% data variables.product.prodname_codeql_runner %} が CodeQL バンドルを保存する場所を  <nobr>`--tools-dir`</nobr>  フラグで設定できます。また、解析中に一時ファイルを保存する場所を、`--temp-dir` で設定できます。 <nobr>`--temp-dir`</nobr>.
 
-To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)."
+ランナーのコマンドラインリファレンスを表示するには、`-h` フラグを使用します。 たとえば、動作するすべてのコマンドを一覧表示するには `codeql-runner-OS -h` と入力し、`init` コマンド実行時に使用できるすべてのコマンドを一覧表示するには `codeql-runner-OS init -h` と入力します (`OS` 変数は使用している実行ファイルによります)。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を CI システムで設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)」を参照してください。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
-#### Basic example
+#### 基本的な例
 
-This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
+この例では、`{% data variables.command_line.git_url_example %}` にホストされている `octo-org/example-repo` リポジトリに対し、Linux CI サーバーで {% data variables.product.prodname_codeql %} 解析を実行します。 このリポジトリには、{% data variables.product.prodname_codeql %} により直接解析でき、ビルドされていない言語 (Go、JavaScript、Python、TypeScript) のみが含まれているため、プロセスは非常に単純です。
 
 In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
 
-1. Check out the repository to analyze.
-1. Move into the directory where the repository is checked out.
-1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+1. 解析するリポジトリをチェックアウトします。
+1. リポジトリがチェックアウトされるディレクトリに移動します。
+1. {% data variables.product.prodname_codeql_runner %} を初期化し、検出された言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
 
     ```shell
     $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
@@ -113,13 +109,13 @@ In this example, the server has access to download the {% data variables.product
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
-#### Compiled language example
+#### コンパイル型言語の例
 
-This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
+この例は前の例と似ていますが、今回のリポジトリには C/C++、C#、または Java のコードがあります。 これらの言語用に {% data variables.product.prodname_codeql %} データベースを作成するには、CLI でビルドをモニターする必要があります。 初期化プロセスの最後に、ランナーはコードをビルドする前に環境をセットアップするために必要なコマンドを報告します。 通常の CI ビルドプロセスを呼び出す前にこのコマンドを実行してから、`analyze` コマンドを実行する必要があります。
 
-1. Check out the repository to analyze.
-1. Move into the directory where the repository is checked out.
-1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+1. 解析するリポジトリをチェックアウトします。
+1. リポジトリがチェックアウトされるディレクトリに移動します。
+1. {% data variables.product.prodname_codeql_runner %} を初期化し、検出された言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
 
     ```shell
     $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
@@ -132,23 +128,23 @@ This example is similar to the previous example, however this time the repositor
       ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
       ```
 
-1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
+1. `init` アクションによって生成されたスクリプトを入手し、ビルドを監視する環境をセットアップします。 次のコードには、先頭にドットとスペースがあることに注意してください。
 
     ```shell
     $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
     ```
 
-1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting CodeQL code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system#no-code-found-during-the-build)."
+1. コードをビルドします。 macOS では、build コマンドのプレフィックスに環境変数 `$CODEQL_RUNNER` を付ける必要があります。 詳しい情報については、「[CI システムにおせるコードスキャンのトラブルシューティング](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system#no-code-found-during-the-build)」を参照してください。
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
 {% note %}
 
-**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place.
+**注釈:** コンテナ化されたビルドを使用している場合、ビルドタスクを行うコンテナで {% data variables.product.prodname_codeql_runner %} を実行する必要があります。
 
 {% endnote %}
 
 ### 参考リンク
 
-- "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)"
-- "[Troubleshooting {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)"
+- 「[CI システムで {% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)」
+- 「[CI システムにおける {% data variables.product.prodname_code_scanning %} のトラブルシューティング](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)」
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index 2806f1f1ac..d97b6d6bbb 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### SARIF サポートについて
@@ -17,27 +19,27 @@ SARIF（Static Analysis Results Interchange Format）は、出力ファイル形
 
 サードパーティの静的コード分析エンジンから SARIF ファイルをアップロードするには、アップロードされたファイルが SARIF 2.1.0 バージョンを使用していることを確認する必要があります。 {% data variables.product.prodname_dotcom %} は SARIF ファイルを解析し、{% data variables.product.prodname_code_scanning %} エクスペリエンスの一部としてリポジトリの結果を使用してアラートを表示します。 詳しい情報については、「[SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)」を参照してください。 SARIF 2.1.0 JSON スキーマの詳細については、「[`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json)」を参照してください。
 
-SARIF ファイルに `partialFingerprints` が含まれていない場合、{% data variables.product.prodname_actions %} を使用して SARIF ファイルをアップロードすると、`partialFingerprints` フィールドが計算されます。 For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+SARIF ファイルに `partialFingerprints` が含まれていない場合、{% data variables.product.prodname_actions %} を使用して SARIF ファイルをアップロードすると、`partialFingerprints` フィールドが計算されます。 詳しい情報については、「[リポジトリに対する {% data variables.product.prodname_code_scanning %} をセットアップする](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)」または「[CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」を参照してください。
 
-{% data variables.product.prodname_dotcom %} は、SARIF ファイルのプロパティを使用してアラートを表示します。 たとえば、`shortDescription` と `fullDescription` は、{% data variables.product.prodname_code_scanning %} アラートの上部に表示されます。 `location` により、{% data variables.product.prodname_dotcom %} がコードファイルに注釈を表示できるようになります。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+{% data variables.product.prodname_dotcom %} は、SARIF ファイルのプロパティを使用してアラートを表示します。 たとえば、`shortDescription` と `fullDescription` は、{% data variables.product.prodname_code_scanning %} アラートの上部に表示されます。 `location` により、{% data variables.product.prodname_dotcom %} がコードファイルに注釈を表示できるようになります。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
 SARIF の使用が初めてで、詳細を確認する必要がある場合は、Microsoft の [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) リポジトリを参照してください。
 
 ### フィンガープリントを使用してアラートの重複を防止する
 
-{% data variables.product.prodname_actions %} ワークフローが新しいコードスキャンを実行するたびに、それぞれの実行結果が処理され、アラートがリポジトリに追加されます。 同じ問題に対するアラートの重複を防ぐために、{% data variables.product.prodname_code_scanning %} はフィンガープリントを使用してさまざまな実行結果を照合し、選択したブランチの最新の実行で 1 回だけ表示されるようにします。 This makes it possible to match alerts to the right line of code when files are edited.
+{% data variables.product.prodname_actions %} ワークフローが新しいコードスキャンを実行するたびに、それぞれの実行結果が処理され、アラートがリポジトリに追加されます。 同じ問題に対するアラートの重複を防ぐために、{% data variables.product.prodname_code_scanning %} はフィンガープリントを使用してさまざまな実行結果を照合し、選択したブランチの最新の実行で 1 回だけ表示されるようにします。 これにより、ファイルが編集されたときに、アラートを適切なコードの行にマッチさせることができます。
 
 {% data variables.product.prodname_dotcom %} は、OASIS 標準の `partialFingerprints` プロパティを使用して、2 つの結果が論理的に同一の場合に検出します。 詳しい情報については、OASIS ドキュメントの「"[partialFingerprints プロパティ](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)」エントリを参照してください。
 
-`id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。 If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)."
+`id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。 `upload-sarif` アクションを使用して SARIF ファイルをアップロードし、このデータが欠落している場合、{% data variables.product.prodname_dotcom %} はソースファイルから `partialFingerprints` フィールドの入力を試みます。 結果のアップロードに関する詳しい情報については、「[SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)」を参照してください。
 
-If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)."
+`/code-scanning/sarifs` API エンドポイントを使用してフィンガープリントデータなしで SARIF ファイルをアップロードする場合、{% data variables.product.prodname_code_scanning %} アラートが処理され表示されますが、アラートが重複して表示される場合があります。 アラートが重複して表示されないようにするには、フィンガープリントデータを計算し、`partialFingerprints` プロパティを入れてから SARIF ファイルをアップロードする必要があります。 `upload-sarif` アクションが使用しているスクリプト (https://github.com/github/codeql-action/blob/main/src/fingerprints.ts) は、取っ掛かりとして役立つかもしれません。 API に関する詳しい情報については、「[解析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」を参照してください。
 
-### Validating your SARIF file
+### SARIF ファイルを検証する
 
 <!--UI-LINK: When code scanning fails, the error banner shown in the Security > Code scanning alerts view links to this anchor.-->
 
-You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/).
+SARIF ファイルが {% data variables.product.prodname_code_scanning %} と互換性があるかどうかは、{% data variables.product.prodname_dotcom %} 収集ルールと照らし合わせることで確認できます。 詳しい情報については、[Microsoft SARIF validator](https://sarifweb.azurewebsites.net/) にアクセスしてください。
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
@@ -69,17 +71,17 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 
 #### `reportingDescriptor` オブジェクト
 
-| 名前                           | 説明                                                                                                                                                                                                                                                                                                                  |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id`                         | **必須。**ルールの一意の識別子。 `id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。                                                                                                                                          |
-| `name`                       | **任意。**ルールの名前。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタできるように名前を表示します。                                                                                                                                                              |
-| `shortDescription.text`      | **必須。**ルールの簡単な説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の簡単な説明を表示します。                                                                                                                                                             |
-| `fullDescription.text`       | **必須。**ルールの説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の説明全体を表示します。 文字数は最大 1000 文字に制限されています。                                                                                                                                        |
-| `defaultConfiguration.level` | **任意。**ルールのデフォルトの重要度レベル。 {% data variables.product.prodname_code_scanning_capc %} は、特定のルールの結果がどの程度重要であるかを理解するために、重要度レベルを使用します。 この値は、`result` オブジェクトの `level` 属性でオーバーライドできます。 詳しい情報については、「[`result` オブジェクト](#result-object)」を参照してください。 デフォルト: `Warning`                                                            |
-| `help.text`                  | **必須。**テキスト形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。                                                                                                                                                                                              |
-| `help.markdown`              | **推奨。**Markdown 形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。 When `help.markdown` is available, it is displayed instead of `help.text`.                                                                                                              |
-| `properties.tags[]`          | **任意。**文字列の配列。 {% data variables.product.prodname_code_scanning_capc %} は、`tags` を使用して、{% data variables.product.prodname_dotcom %} の結果をフィルタできます。 たとえば、`security` タグを含むすべての結果をフィルタすることができます。                                                                                                                      |
-| `properties.precision`       | **推奨。**このルールで示される結果が true である頻度を示す文字列。 たとえば、ルールに既知の高誤検知率がある場合、精度は `low` である必要があります。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} の精度で結果を並べ替えるため、最高 `level` の精度と最高 `precision` の結果が最初に表示されます。 Can be one of: `very-high`, `high`, `medium`, or `low`. |
+| 名前                           | 説明                                                                                                                                                                                                                                                                                                        |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                         | **必須。**ルールの一意の識別子。 `id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。                                                                                                                                |
+| `name`                       | **任意。**ルールの名前。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタできるように名前を表示します。                                                                                                                                                    |
+| `shortDescription.text`      | **必須。**ルールの簡単な説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の簡単な説明を表示します。                                                                                                                                                   |
+| `fullDescription.text`       | **必須。**ルールの説明。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にある {% data variables.product.prodname_dotcom %} の説明全体を表示します。 文字数は最大 1000 文字に制限されています。                                                                                                                              |
+| `defaultConfiguration.level` | **任意。**ルールのデフォルトの重要度レベル。 {% data variables.product.prodname_code_scanning_capc %} は、特定のルールの結果がどの程度重要であるかを理解するために、重要度レベルを使用します。 この値は、`result` オブジェクトの `level` 属性でオーバーライドできます。 詳しい情報については、「[`result` オブジェクト](#result-object)」を参照してください。 デフォルト: `Warning`                                                  |
+| `help.text`                  | **必須。**テキスト形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。                                                                                                                                                                                    |
+| `help.markdown`              | **推奨。**Markdown 形式を使用したルールのドキュメント。 {% data variables.product.prodname_code_scanning_capc %} は、関連する結果の横にこのヘルプドキュメントを表示します。 `help.markdown` が利用可能な場合は、 `help.text` の代わりに表示されます。                                                                                                                           |
+| `properties.tags[]`          | **任意。**文字列の配列。 {% data variables.product.prodname_code_scanning_capc %} は、`tags` を使用して、{% data variables.product.prodname_dotcom %} の結果をフィルタできます。 たとえば、`security` タグを含むすべての結果をフィルタすることができます。                                                                                                            |
+| `properties.precision`       | **推奨。**このルールで示される結果が true である頻度を示す文字列。 たとえば、ルールに既知の高誤検知率がある場合、精度は `low` である必要があります。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom %} の精度で結果を並べ替えるため、最高 `level` の精度と最高 `precision` の結果が最初に表示されます。 `very-high`、`high`、`medium`、`low` のいずれかになります。 |
 
 #### `result` オブジェクト
 
@@ -92,7 +94,7 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 | `rule`                                  | **任意。**この結果のルール（レポート記述子）を見つけるために使用される参照。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
 | `level`                                 | **任意。**結果の重要度。 このレベルは、ルールで定義されているデフォルトの重要度をオーバーライドします。 {% data variables.product.prodname_code_scanning_capc %} は、レベルを使用して、{% data variables.product.prodname_dotcom %} の重要度で結果をフィルタします。                                                                                                                                                                                                                                                                                                                                                                                                       |
 | `message.text`                          | **必須。**結果を説明するメッセージ。 {% data variables.product.prodname_code_scanning_capc %} は、結果のタイトルとしてメッセージテキストを表示します。 表示スペースが限られている場合、メッセージの最初の文のみが表示されます。                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| `locations[]`                           | **Required.** The set of locations where the result was detected up to a maximum of 10. 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。                                                                                                                                                                                                                       |
+| `locations[]`                           | **必須。**結果が検出された場所。最大値は 10 です。 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。                                                                                                                                                                                                                                                                                 |
 | `partialFingerprints`                   | **必須。**結果の一意の ID を追跡するために使用される文字列。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` を使用して、コミットとブランチで同じ結果であるものを正確に識別します。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` がある場合、それを使用しようとします。 `upload-action` を使用してサードパーティの SARIF ファイルをアップロードする場合、SARIF ファイルに含まれていないときに、アクションによって `partialFingerprints` が作成されます。 詳しい情報については、「[フィンガープリントを使用してアラートの重複を防止する](#preventing-duplicate-alerts-using-fingerprints)」を参照してください。  **注釈:** {% data variables.product.prodname_code_scanning_capc %} は、`primaryLocationLineHash` のみを使用します。 |
 | `codeFlows[].threadFlows[].locations[]` | **任意。**`threadFlow` オブジェクトに対する `location` オブジェクトの配列。実行スレッドを通してプログラムの進行状況を記述します。 `codeFlow` オブジェクトは、結果の検出に使用されるコード実行パターンを記述します。 コードフローが入力されている場合、{% data variables.product.prodname_code_scanning %} は、関連する結果の {% data variables.product.prodname_dotcom %} のコードフローを拡張します。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。                                                                                                                                                                                                                                                           |
 | `relatedLocations[]`                    | この結果に関連する場所。 結果メッセージに埋め込まれている場合、{% data variables.product.prodname_code_scanning_capc %} は、関連する場所にリンクします。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。                                                                                                                                                                                                                                                                                                                                                                                                                           |
@@ -109,13 +111,13 @@ You can check a SARIF file is compatible with {% data variables.product.prodname
 
 #### `physicalLocation` オブジェクト
 
-| 名前                     | 説明                                                                                                                                                                                                                                                                                                                                                                                                       |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `artifactLocation.uri` | **必須。**アーティファクトの場所を示す URI（通常はリポジトリ内のファイル、またはビルド中に生成されたファイル）。 URI が相対の場合、分析されている {% data variables.product.prodname_dotcom %} リポジトリのルートに相対である必要があります。 たとえば、main.js または src/script.js は、リポジトリのルートを基準にしています。 URI が絶対の場合、{% data variables.product.prodname_code_scanning %} は URI を使用してアーティファクトをチェックアウトし、リポジトリ内のファイルを照合できます。 For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. |
-| `region.startLine`     | **必須。**リージョンの最初の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                                  |
-| `region.startColumn`   | **必須。**リージョンの最初の文字の列番号。                                                                                                                                                                                                                                                                                                                                                                                  |
-| `region.endLine`       | **必須。**リージョンの最後の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                                  |
-| `region.endColumn`     | **必須。**リージョンの末尾に続く文字の列番号。                                                                                                                                                                                                                                                                                                                                                                                |
+| 名前                     | 説明                                                                                                                                                                                                                                                                                                                                                                                            |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `artifactLocation.uri` | **必須。**アーティファクトの場所を示す URI（通常はリポジトリ内のファイル、またはビルド中に生成されたファイル）。 URI が相対の場合、分析されている {% data variables.product.prodname_dotcom %} リポジトリのルートに相対である必要があります。 たとえば、main.js または src/script.js は、リポジトリのルートを基準にしています。 URI が絶対の場合、{% data variables.product.prodname_code_scanning %} は URI を使用してアーティファクトをチェックアウトし、リポジトリ内のファイルを照合できます。 例: `https://github.com/ghost/example/blob/00/src/promiseUtils.js` |
+| `region.startLine`     | **必須。**リージョンの最初の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                       |
+| `region.startColumn`   | **必須。**リージョンの最初の文字の列番号。                                                                                                                                                                                                                                                                                                                                                                       |
+| `region.endLine`       | **必須。**リージョンの最後の文字の行番号。                                                                                                                                                                                                                                                                                                                                                                       |
+| `region.endColumn`     | **必須。**リージョンの末尾に続く文字の列番号。                                                                                                                                                                                                                                                                                                                                                                     |
 
 ### SARIF 出力ファイルの例
 
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
index e1252e606d..38b69d390b 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up code scanning for a repository
-shortTitle: Setting up code scanning
-intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.'
+title: リポジトリに対するコードスキャンをセットアップする
+shortTitle: コードスキャンを設定する
+intro: 'リポジトリにワークフローを追加することにより、{% data variables.product.prodname_code_scanning %} をセットアップできます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.'
 versions:
@@ -10,105 +10,106 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### Options for setting up {% data variables.product.prodname_code_scanning %}
+### {% data variables.product.prodname_code_scanning %} のセットアップ用オプション
 
-You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. 詳しい情報については、「[{% data variables.product.prodname_codeql %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)」を参照してください。
+{% data variables.product.prodname_code_scanning %} アラートの生成方法、および使用するツールを、リポジトリレベルで決定できます。 {% data variables.product.product_name %} は、{% data variables.product.prodname_codeql %} 解析のために完全に統合されたサポートを提供すると共に、サードパーティーのツールを使用した解析もサポートします。 詳しい情報については、「[{% data variables.product.prodname_codeql %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)」を参照してください。
 
 {% data reusables.code-scanning.enabling-options %}
 
-### Setting up {% data variables.product.prodname_code_scanning %} using actions
-
-{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)」を参照してください。{% endif %}
+### アクションを使用して {% data variables.product.prodname_code_scanning %} をセットアップする
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
-5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
+3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. ![セキュリティの概要にある、[{% data variables.product.prodname_code_scanning_capc %}] の右側の [{% data variables.product.prodname_code_scanning %}] ボタン](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. [Get started with {% data variables.product.prodname_code_scanning %}] で、{% data variables.product.prodname_codeql_workflow %} またはサードパーティーのワークフローの [**Set up this workflow**] をクリックします。 ![[Get started with {% data variables.product.prodname_code_scanning %}] のヘッディングの下にある [Set up this workflow] ボタン](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
+5. {% data variables.product.prodname_code_scanning %} がコードをスキャンする方法をカスタマイズするため、ワークフローを編集します。
 
-   Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
+   通常は、何も変更せずに {% data variables.product.prodname_codeql_workflow %} をコミットできます。 ただし、サードパーティのワークフローは、その多くで追加設定が必要なため、コミットする前にワークフローのコメントをお読みください。
 
    詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。
 6. [**Start commit**] ドロップダウンを使用して、コミットメッセージを入力します。 ![コミットを開始する](/assets/images/help/repository/start-commit-commit-new-file.png)
 7. デフォルトブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択します。 ![コミット先を選択する](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
 8. [**Commit new file**] または [**Propose new file**] をクリックします。
 
-In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
+デフォルトの {% data variables.product.prodname_codeql_workflow %} では、{% data variables.product.prodname_code_scanning %} は、デフォルトブランチまたは保護されたブランチに変更をプッシュするたび、あるいはデフォルトブランチにプルリクエストを生成するたびに、コードを解析するよう設定されています。 その結果として、{% data variables.product.prodname_code_scanning %} が開始されます。
 
-### Bulk set up of {% data variables.product.prodname_code_scanning %}
-You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository.
+### {% data variables.product.prodname_code_scanning %} の一括セットアップ
+You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. 複数のリポジトリに {% data variables.product.prodname_actions %} ワークフローを追加するためのプルリクエストを発行するスクリプトの例が、[`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) リポジトリにあります。
 
-### Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+### {% data variables.product.prodname_code_scanning %} からログ出力を表示する
 
 After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
 
 {% data reusables.repositories.actions-tab %}
 
-  You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message.
+  {% data variables.product.prodname_code_scanning %} ワークフローを実行するためのエントリを含むリストが表示されます。 エントリのテキストは、コミットメッセージに付けるタイトルです。
 
-  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+  ![{% data variables.product.prodname_code_scanning %} ワークフローを表示しているアクションのリスト](/assets/images/help/repository/code-scanning-actions-list.png)
 
-1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow.
+1. {% data variables.product.prodname_code_scanning %} ワークフローのエントリをクリックします。
 
-1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+1. 左側のジョブ名をクリックします。 ここでは例として、[**Analyze (言語)**] をクリックします。
 
-  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+  ![{% data variables.product.prodname_code_scanning %} ワークフローからのログ出力](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
 
-1. Review the logging output from the actions in this workflow as they run.
+1. このワークフローの実行時にアクションから出力されるログを確認します。
 
-1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+1. すべてのジョブが完了すると、確認されたすべての {% data variables.product.prodname_code_scanning %} アラートの詳細を表示できます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。
 
 {% note %}
 
-**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page.
+**注釈:** {% data variables.product.prodname_code_scanning %} ワークフローを追加するためのプルリクエストをリポジトリに発行すると、そのプルリクエストからのアラートは、そのプルリクエストがマージされるまで {% data variables.product.prodname_code_scanning_capc %} ページに直接表示されません。 アラートが見つかった場合は、プルリクエストがマージされる前に、{% data variables.product.prodname_code_scanning_capc %} ページのバナーにある [**_(数字)_ alerts found**] をクリックしてそのアラートを表示できます。
 
-  ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
+  ![[n alerts found] のリンクをクリック](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
 
 {% endnote %}
 
-### Understanding the pull request checks
+### プルリクエストのチェックを理解する
 
-Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis.
+Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. ワークフローの解析ジョブごとに 1 つのエントリがあり、最後のエントリは解析結果です。
 
-The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code.
+{% data variables.product.prodname_code_scanning %} 解析チェックの名前は、「ツール名 / ジョブ名 (トリガー)」という形式になります。 たとえば、C++ のコードの {% data variables.product.prodname_codeql %} 解析には、「{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)」のエントリがあります。 {% data variables.product.prodname_code_scanning %} 解析エントリで [**Details**] をクリックして、ログのデータを表示できます。 これにより、解析ジョブが失敗した場合に問題をデバッグできます。 たとえば、コンパイル型言語の {% data variables.product.prodname_code_scanning %} 解析では、アクションがコードをビルドできなかった場合に解析ジョブが失敗します。
 
-  ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png)
+  ![{% data variables.product.prodname_code_scanning %} プルリクエストのチェック](/assets/images/help/repository/code-scanning-pr-checks.png)
 
-When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
+{% data variables.product.prodname_code_scanning %} ジョブが完了すると、
+{% data variables.product.prodname_dotcom %} はプルリクエストにより追加されたアラートがないか確認し、チェックのリストに「{% data variables.product.prodname_code_scanning_capc %} の結果 / ツール名」のエントリを追加します。 {% data variables.product.prodname_code_scanning %} が 1 回でも実行された後は、[**Details**] をクリックして解析結果を表示できます。 プルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した場合、「{% data variables.product.prodname_code_scanning_capc %} 結果 / ツール名」チェックの [**Details**] をクリックすると最初は「Missing analysis」のメッセージが表示されます。
 
-  ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png)
+  ![コミットメッセージの解析がありません](/assets/images/help/repository/code-scanning-missing-analysis.png)
 
-#### Reasons for the "missing analysis" message
+#### 「missing analysis」のメッセージが出る理由
 
-After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" message.
+プルリクエストのコードを解析した後、{% data variables.product.prodname_code_scanning %} はトピックブランチ (プルリクエストを作成するために使用したブランチ) の解析と、ベースブランチ (プルリクエストをマージするブランチ) の解析を比較する必要があります。 これにより、{% data variables.product.prodname_code_scanning %} はプルリクエストにより新しく発生したアラートはどれか、ベースブランチに既に存在していたアラートはどれか、また既存のアラートがプルリクエストの変更により修正されたかを測定できます。 始めにプルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した段階では、ベースブランチはまだ解析されていないので、こうした情報を測定できません。 この場合、プルリクエストの結果チェックをくりっくすると、「Missing analysis for base commit SHA-HASH (ベースコミット SHA-HASH の解析がありません)」というメッセージが表示されます。
 
-There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
+この他にも、プルリクエストのベースブランチに対する直近のコミットで解析結果がないことがあります。 たとえば、次のような場合です。
 
-* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed.
+* プルリクエストがデフォルトブランチ以外のブランチに発行され、このブランチが解析されていない。
 
-  To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch.
+  ブランチがスキャン済みかを確認するには、{% data variables.product.prodname_code_scanning_capc %} ページに移動し、[**Branch**] ドロップダウンをクリックして該当するブランチを選択します。
 
-  ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png)
+  ![[Branch] ドロップダウンメニューからブランチを選択](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png)
 
-  The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
+  この状況における解決策は、そのブランチの {% data variables.product.prodname_code_scanning %} ワークフローにある `on:push` と `on:pull_request` にベースブランチの名前を追加してから、スキャンするオープンなプルリクエストを更新するよう変更することです。
 
-* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available.
+* プルリクエストのベースブランチへの直近のコミットが現在解析中で、解析がまだ利用できない。
 
-  Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+  数分待ってからプルリクエストに変更をプッシュして、{% data variables.product.prodname_code_scanning %} を再トリガーします。
 
-* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available.
+* ベースブランチの直近のコミットを解析中にエラーが発生し、そのコミットの解析ができない。
 
-  Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+  ちょっとした変更をベースブランチにマージして、この最新のコミットで {% data variables.product.prodname_code_scanning %} をトリガーしてから、プルリクエストに変更をプッシュして {% data variables.product.prodname_code_scanning %} を再トリガーします。
 
 ### 次のステップ
 
 After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can:
 
-- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
-- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
-- Set up notifications for completed runs. 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)」を参照してください。
-- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)."
-- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。
+- リポジトリに対して生成された {% data variables.product.prodname_code_scanning %} アラートをすべて表示する。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)」を参照してください。
+- {% data variables.product.prodname_code_scanning %} をセットアップ後にサブミットしたプルリクエストに対して生成されたアラートを表示する。 詳しい情報については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。
+- 実行完了の通知を設定する。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)」を参照してください。
+- {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} の初期セットアップで発生した問題を調査する。 詳しい情報については、「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)」を参照してください。
+- {% data variables.product.prodname_code_scanning %} がリポジトリ内のコードをスキャンする方法をカスタマイズする。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index 98f20980c9..1f17297ae1 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -1,7 +1,7 @@
 ---
-title: Triaging code scanning alerts in pull requests
-shortTitle: Triaging alerts in pull requests
-intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.'
+title: プルリクエストでコードスキャンアラートをトリガーする
+shortTitle: プルリクエストでアラートをトリガーする
+intro: 'プルリクエストで {% data variables.product.prodname_code_scanning %} が問題を特定した場合、強調表示されたコードを確認してアラートを解決できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -10,58 +10,42 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
-### About {% data variables.product.prodname_code_scanning %} results on pull requests
+### プルリクエストの {% data variables.product.prodname_code_scanning %} 結果について
 
-In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+プルリクエストのチェック用に {% data variables.product.prodname_code_scanning %} が設定されているリポジトリでは、{% data variables.product.prodname_code_scanning %}がプルリクエストのコードをチェックします。 デフォルトでは、このチェックはデフォルトブランチを対象とするプルリクエストに限定されていますが、この設定は {% data variables.product.prodname_actions %} またはサードパーティの CI/CD システム内で変更できます。 変更をマージすることで、対象となるブランチに新たな {% data variables.product.prodname_code_scanning %} アラートが発生する場合には、そのアラートはプルリクエストのチェック結果として報告されます。 また、アラートではプルリクエストの [**Files changed**] タブでアノテーションとしても表示されます。 リポジトリへの書き込み権限がある場合、既存のすべての {% data variables.product.prodname_code_scanning %} アラートを [**Security**] タブで表示できます。 リポジトリのアラートに関する詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
+{% data variables.product.prodname_code_scanning %} の結果に、重大度が `error` のものがある場合、そのチェックは失敗し、チェック結果でエラーが報告されます。 {% data variables.product.prodname_code_scanning %} で出たすべての結果の重大度が低い場合、アラートは警告または通知として扱われ、チェックは成功となります。 プルリクエストのターゲットが {% data variables.product.prodname_code_scanning %} を使用する保護されたブランチで、リポジトリの所有者がステータスチェック必須を設定している場合、すべてのエラーアラートを解決するか閉じない限り、そのプルリクエストはマージできません。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
 
-![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
+![プルリクエストの失敗した {% data variables.product.prodname_code_scanning %} チェック](/assets/images/help/repository/code-scanning-check-failure.png)
 
-### About {% data variables.product.prodname_code_scanning %} as a pull request check
+### プルリクエストのチェックとしての {% data variables.product.prodname_code_scanning %} について
 
-There are many options for configuring {% data variables.product.prodname_code_scanning %} as a pull request check, so the exact setup of each repository will vary and some will have more than one check. The check that contains the results of {% data variables.product.prodname_code_scanning %} is: **Code scanning results**.
+{% data variables.product.prodname_code_scanning %} をプルリクエストのチェックとして設定するためのオプションは多いので、正確なセットアップはそれぞれのリポジトリで異なり、複数のチェックを行う場合もあります。 {% data variables.product.prodname_code_scanning %} の結果を含むチェックは、[**Code scanning results**] です。
 
-If the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java). As with other pull request checks, you can see full details of the check failure on the **Checks** tab. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)."
+リポジトリが {% data variables.product.prodname_codeql_workflow %} を使用している場合、**{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** チェックを各言語で実行してから、結果チェックを実行します。 設定に問題がある場合、解析がコンパイルする必要がある言語 (C/C++、C#、Java など) でプルリクエストがビルドを中断している場合、解析は失敗することがあります。 他のプルリクエストと同様、チェック失敗の詳細内容を [**Checks**] タブで確認できます。 設定およびトラブルシューティングに関する詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」または「[{% data variables.product.prodname_codeql %} ワークフローのトラブルシューティング](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)」を参照してください。
 
-### Triaging an alert on your pull request
+### プルリクエストのアラートをトリガーする
 
-When you look at the **Files changed** tab for a pull request, you see annotations for any lines of code that triggered the alert.
+プルリクエストの [**Files changed**] タブを見ると、アラートをトリガーしたコードの行にあるアノテーションがあります。
 
-![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png)
+![プルリクエストの差分にあるアラートのアノテーション](/assets/images/help/repository/code-scanning-pr-annotation.png)
 
-If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)."
+リポジトリへの書き込み権限がある場合、一部のアノテーションにはアラートの追加的な背景を説明するリンクが含まれています。 上の例では、{% data variables.product.prodname_codeql %} 解析から [**user-provided value**] をクリックすると、データフローに信頼されていないデータが入っている場所 (ソース) が表示されます。 この場合、[**Show paths**] をクリックすることで、ソースからデータ (シンク) を使用するコードまでのフルパスを表示することもできます。 これにより、データが信頼されていないかや、ソースとシンクの間のデータサニタイズのステップを解析が認識できなかったかを簡単に確認できます。 {% data variables.product.prodname_codeql %} を使用したデータフローの解析に関する詳しい情報については、「[データフロー解析について](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)」を参照してください。
 
-To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem.
+アラートの詳細情報を表示するには、書き込み権限を持つユーザが、アノテーションに表示されている [**Show more details**] のリンクをクリックします。 これにより、ツールが提供するコンテキストとメタデータのすべてをアラートビューで確認できます。 下の例では、問題の重要度、タイプ、および関連する共通脆弱性タイプ一覧 (CWE) を示すタグが表示されています。 また、どのコミットが問題を引き起したかも表示されています。
 
-In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code.
+アラートの詳細画面において、{% data variables.product.prodname_codeql %} 解析のような一部の {% data variables.product.prodname_code_scanning %} ツールでは、問題の説明や、コードを修正する方法を説明するためる [**Show more**] リンクも含まれています。
 
-![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
+![アラートの説明と、詳細情報を表示するリンク](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### プルリクエストのアラートを解決する
 
-Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
+プルリクエストへのプッシュアクセスがあるユーザなら誰でも、プルリクエストで特定された {% data variables.product.prodname_code_scanning %} アラートを解決できます。 プルリクエストに変更をコミットすると、プルリクエストのチェック実行が新しくトリガーされます。 問題を修正すると、アラートは閉じられ、アノテーションは削除されます。
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
+アラートを解決する必要がないと思われる場合には、書き込み権限を持つユーザがアラートを手動で閉じることができます。 {% data reusables.code-scanning.close-alert-examples %}リポジトリに対する書き込み権限がある場合、アノテーションおよびアラートビューで [**Close**] ボタンが使用できます。
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### Dismissing an alert on your pull request
-
-An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
-
-![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index dd5b18b598..cac4b14f17 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting CodeQL code scanning in your CI system
-shortTitle: Troubleshooting in your CI
-intro: 'If you''re having problems with the {% data variables.product.prodname_codeql_runner %}, you can troubleshoot by using these tips.'
+title: CI システムにおける CodeQL コードスキャンのトラブルシューティング
+shortTitle: CI におけるトラブルシューティング
+intro: '{% data variables.product.prodname_codeql_runner %} で問題が生じている場合、ここに掲載されているヒントを使ってトラブルを解決できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   enterprise-server: '2.22'
@@ -9,46 +9,49 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
-### The `init` command takes too long
+### `init` コマンドに時間がかかりすぎる
 
-Before the {% data variables.product.prodname_codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries.
+{% data variables.product.prodname_codeql_runner %} は、コードのビルドと解析を行う前に、{% data variables.product.prodname_codeql %} CLI と {% data variables.product.prodname_codeql %} ライブラリを含んでいる {% data variables.product.prodname_codeql %} バンドルへのアクセス権が必要です。
 
-When you use the {% data variables.product.prodname_codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes. The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.product.prodname_codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again.
+お使いのマシンで {% data variables.product.prodname_codeql_runner %} を初めて使用する際、`init` コマンドは {% data variables.product.prodname_codeql %} バンドルをマシンにダウンロードします。 ダウンロードには数分かかります。
+{% data variables.product.prodname_codeql %} バンドルは次の実行の前にキャッシュされるので、{% data variables.product.prodname_codeql_runner %} を同じマシンで再度使用する際は、{% data variables.product.prodname_codeql %} バンドルを再ダウンロードすることはありません。
 
-To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command.
+この自動ダウンロードを回避するには、{% data variables.product.prodname_codeql %} バンドルをマシンに手動でダウンロードし、`init` コマンドの `--codeql-path` フラグでパスを指定します。
 
 ### ビルド中にコードが見つからない
 
-If the `analyze` command for the {% data variables.product.prodname_codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure.
+{% data variables.product.prodname_codeql_runner %} の `analyze` コマンドで、`No source code was seen during the build` というエラーが出て失敗する場合、{% data variables.product.prodname_codeql %} がコードをモニターできなかったことを示しています。 このようなエラーが発生する理由として、次のようなものがあります。
 
-1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)."
+1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 この問題を解決するには、`init` コマンドの `--languages` フラグを使用して、解析する言語を手動で定義できます。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を CI システムで設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)」を参照してください。
 
-1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the code. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command.
-   - On macOS and Linux:
+1. コンパイル型言語を `autobuild` コマンドを使用せずに解析し、`init` ステップの後に自分でビルドステップを実行している。 ビルドが機能するには、{% data variables.product.prodname_codeql_runner %} がコードをモニターできるように環境をセットアップする必要があります。 `init` コマンドは、必要な環境をエクスポートする方法についての説明を生成するので、それをコピーして`init` コマンドの実行後にスクリプトを実行できます。
+   - macOS および Linux:
      ```shell
       $ . codeql-runner/codeql-env.sh
      ```
-   - On Windows, using the Command shell (`cmd`) or a batch file (`.bat`):
+   - Windows で、コマンドシェル (`cmd`) またはバッチファイル (`.bat`) を使用する場合:
      ```shell
      > call codeql-runner\codeql-env.bat
      ```
-   - On Windows, using PowerShell:
+   - Windows で、PowerShell を使用する場合:
      ```shell
      > cat codeql-runner\codeql-env.sh | Invoke-Expression
      ```
 
-   The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead.
+   環境変数は、`codeql-runner/codeql-env.json` にも保存されています。 このファイルには、環境変数キーを値にマッピングする単一の JSON オブジェクトが含まれています。 `init` コマンドで生成されたスクリプトを実行できない場合、JSON フォーマットのデータを代わりに使用できます。
 
    {% note %}
 
-   **Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different.
+   **注釈:** `init` コマンドの`--temp-dir` フラグで一時ファイルのカスタムディレクトリを指定している場合、`codeql-env` ファイルへのパスが異なることがあります。
 
    {% endnote %}
 
-1. You're analyzing a compiled language on macOS without using the `autobuild` command and you run the build steps yourself after the `init` step. If SIP (System Integrity Protection) is enabled, which is the default on recent versions of OSX, analysis might fail. To fix this, prefix the build command with the `$CODEQL_RUNNER` environment variable. For example, if your build command is `cmd arg1 arg2`, you should run `$CODEQL_RUNNER cmd arg1 arg2`.
+1. macOS でコンパイル型言語を `autobuild` コマンドを使用せずに解析し、`init` ステップの後に自分でビルドステップを実行している。 SIP (システム整合性保護) が有効になっている場合、解析は失敗することがあります。OSX の最近のバージョンでは、SIP はデフォルトで有効になっています。 この問題を解決するには、ビルドコマンドの前に `$CODEQL_RUNNER` の環境変数を付けてください。 たとえばビルドコマンドが `cmd arg1 arg2` の場合、`$CODEQL_RUNNER cmd arg1 arg2` を実行します。
 
-1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.product.prodname_codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)."
+1. コードがコンテナまたは別のマシンでビルドされている。 コンテナ化されたビルドを使用しているか、ビルドを別のマシンに委託している場合は、必ず {% data variables.product.prodname_codeql_runner %} をコンテナまたはビルドタスクを実行するマシンで実行してください。 詳しい情報については、「[コンテナで CodeQL コードスキャンを実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)」を参照してください。
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index bc48a01038..e485a736b7 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting the CodeQL workflow
-shortTitle: Troubleshooting CodeQL
-intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.'
+title: CodeQL ワークフローのトラブルシューティング
+shortTitle: CodeQL のトラブルシューティング
+intro: '{% data variables.product.prodname_code_scanning %} で問題が生じている場合、ここに掲載されている問題解決のためのヒントを使ってトラブルを解決できます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   enterprise-server: '2.22'
@@ -9,26 +9,31 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
-### Producing detailed logs for debugging
+### デバッグ用の詳細なログを生成する
 
-To produce more detailed logging output, you can enable step debug logging. 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)」を参照してください。
+詳細なログ出力を生成するため、ステップのデバッグロギングを有効化することができます。 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)」を参照してください。
 
 ### コンパイル言語の自動ビルドの失敗
 
 プロジェクト内のコンパイル言語のコードの自動ビルドが失敗した場合は、次のトラブルシューティングのステップを試してください。
 
-- {% data variables.product.prodname_code_scanning %} ワークフローから `autobuild` ステップを削除し、特定のビルドステップを追加します。 ワークフローの編集に関する詳しい情報は、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。 For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+- {% data variables.product.prodname_code_scanning %} ワークフローから `autobuild` ステップを削除し、特定のビルドステップを追加します。 ワークフローの編集に関する詳しい情報は、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。 `autobuild` ステップの置き換えに関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
-- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
+- ワークフローが解析する言語を明示的に指定していない場合、{% data variables.product.prodname_codeql %} はコードベースでサポートされている言語を暗黙的に検出します。 この設定では、コンパイル型言語である C/C++、C#、Java のうち、{% data variables.product.prodname_codeql %} はソースファイルの数が最も多い言語のみを解析します。 ワークフローを編集し、解析する言語を指定したビルドマトリクスを追加してください。 デフォルトの CodeQL 解析では、こうしたマトリクスを使用しています。
 
-  The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
+  以下はワークフローからの抜粋で、まず言語を指定するジョブ戦略におけるマトリクスの使用法を示し、次に「Initialize {% data variables.product.prodname_codeql %}」のステップで各言語を参照しています。
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -43,13 +48,13 @@ To produce more detailed logging output, you can enable step debug logging. 詳
           languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
-  For more information about editing the workflow, see "[Configuring code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
+  ワークフローの編集に関する詳しい情報については、「[コードスキャンを設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。
 
 ### ビルド中にコードが見つからない
 
-If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. このようなエラーが発生する理由として、次のようなものがあります。
+ワークフローでエラー `No source code was seen during the build` または `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32` が発生した場合、{% data variables.product.prodname_codeql %} がコードを監視できなかったことを示しています。 このようなエラーが発生する理由として、次のようなものがあります。
 
-1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. たとえば、次の設定では Go と JavaScript のみを分析します。
+1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 この問題を解決するには、`language` マトリクスにある言語のリストを更新し、解析する言語を手動で定義します。 たとえば、次の設定では Go と JavaScript のみを分析します。
 
   ```yaml
   strategy:
@@ -60,19 +65,19 @@ If your workflow fails with an error `No source code was seen during the build`
       # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python']
       language: ['go', 'javascript']
   ```
-For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
-1. {% data variables.product.prodname_code_scanning %} ワークフローはコンパイルされた言語（C、C++、C#、または Java）を分析しているが、コードはコンパイルされていない。 デフォルトでは、{% data variables.product.prodname_codeql %} 分析ワークフローには `autobuild` ステップが含まれていますが、このステップはベスト エフォートプロセスを表しており、特定のビルド環境によっては、コードのビルドに失敗する可能性があります。 `autobuild` ステップを削除し、ビルドステップを手動で含めない場合も、コンパイルが失敗する可能性があります。  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
+1. {% data variables.product.prodname_code_scanning %} ワークフローはコンパイルされた言語（C、C++、C#、または Java）を分析しているが、コードはコンパイルされていない。 デフォルトでは、{% data variables.product.prodname_codeql %} 分析ワークフローには `autobuild` ステップが含まれていますが、このステップはベスト エフォートプロセスを表しており、特定のビルド環境によっては、コードのビルドに失敗する可能性があります。 `autobuild` ステップを削除し、ビルドステップを手動で含めない場合も、コンパイルが失敗する可能性があります。  ビルドステップの指定に関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 1. ワークフローはコンパイルされた言語（C、C++、C#、または Java）を分析しているが、パフォーマンスを向上させるためにビルドの一部がキャッシュされている（Gradle や Bazel などのビルドシステムで発生する可能性が最も高い）。 {% data variables.product.prodname_codeql %} はコンパイラのアクティビティを監視してリポジトリ内のデータフローを理解するため、{% data variables.product.prodname_codeql %} は分析を実行するために完全なビルドを実行する必要があります。
 1. ワークフローはコンパイルされた言語（C、C++、C＃、または Java）を分析しているが、ワークフローの `init` ステップと `analyze` ステップの間でコンパイルが行われていない。 {% data variables.product.prodname_codeql %} では、コンパイラのアクティビティを監視して分析を実行するために、これらの 2 つのステップ間でビルドを行う必要があります。
-1. コンパイルされたコード（C、C++、C#、または Java）は正常にコンパイルされたが、{% data variables.product.prodname_codeql %} がコンパイラの呼び出しを検出できない。 The most common causes are:
+1. コンパイルされたコード（C、C++、C#、または Java）は正常にコンパイルされたが、{% data variables.product.prodname_codeql %} がコンパイラの呼び出しを検出できない。 一般的な原因は次のようなものです。
 
-   * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)."
-   * Building using a distributed build system external to GitHub Actions, using a daemon process.
-   * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
+   * ビルドプロセスを {% data variables.product.prodname_codeql %} とは別のコンテナで実行している。 詳しい情報については、「[コンテナで CodeQL コードスキャンを実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)」を参照してください。
+   * デーモンプロセスを使用して、GitHub Actions の外部で分散ビルドシステムによりビルドしている。
+   * {% data variables.product.prodname_codeql %} は、使用されているコンパイラを認識していない。
 
-  For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. .NET Core 3.0 以降では、`UseSharedCompilation` フラグは必要ありません。
+  .NET Framework プロジェクト、および .NET Core 2 をターゲットとする `dotnet build` または `msbuild` を使用する C# プロジェクトでは、コードをビルドするときに、ワークフローの `run` ステップで `/p:UseSharedCompilation=false` を指定する必要があります。 .NET Core 3.0 以降では、`UseSharedCompilation` フラグは必要ありません。
 
-  For example, the following configuration for C# will pass the flag during the first build step.
+  たとえば、次の C# に対する設定では、最初のビルドステップ中にフラグが渡されます。
 
    ``` yaml
    - run: |
@@ -81,23 +86,23 @@ For more information, see the workflow extract in "[Automatic build for a compil
 
   特定のコンパイラまたは設定で別の問題が発生した場合は、{% data variables.contact.contact_support %} までお問い合わせください。
 
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+ビルドステップの指定に関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
 ### リポジトリの一部が `autobuild` を使用して分析されない
 
-{% data variables.product.prodname_codeql %} の `autobuild` 機能は、ヒューリスティックスを使用してリポジトリにコードをビルドしますが、このアプローチでは、リポジトリの分析が不完全になることがあります。 たとえば、単一のリポジトリに複数の `build.sh` コマンドが存在する場合、`autobuild` ステップはコマンドの 1 つしか実行しないため、分析が完了しない場合があります。 これを解決するには、`autobuild` ステップを、分析するすべてのソースコードをビルドするビルドステップに置き換えます。 For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+{% data variables.product.prodname_codeql %} の `autobuild` 機能は、ヒューリスティックスを使用してリポジトリにコードをビルドしますが、このアプローチでは、リポジトリの分析が不完全になることがあります。 たとえば、単一のリポジトリに複数の `build.sh` コマンドが存在する場合、`autobuild` ステップはコマンドの 1 つしか実行しないため、分析が完了しない場合があります。 これを解決するには、`autobuild` ステップを、分析するすべてのソースコードをビルドするビルドステップに置き換えます。 詳しい情報については、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
 ### ビルドに時間がかかりすぎる
 
 {% data variables.product.prodname_codeql %} 分析でのビルドの実行に時間がかかりすぎる場合は、ビルド時間を短縮するための方法がいくつかあります。
 
-#### Increase the memory or cores
+#### メモリまたはコアを増やす
 
-If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners.
+セルフホストランナーを使用して {% data variables.product.prodname_codeql %} 解析を実行している場合、ランナーのメモリやコア数を増やすことができます。
 
 #### マトリックスビルドを使用して分析を並列化する
 
-The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
+デフォルトの {% data variables.product.prodname_codeql_workflow %} は言語のビルドマトリクスを使用しており、これにより各言語の解析が並列で実行される場合があります。 「Initialize CodeQL」ステップで解析する言語を直接指定している場合、各言語の解析は順次行われます。 複数の言語で解析を高速化するには、マトリクスを使用するようワークフローを変更してください。 詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
 
 #### 1 つのワークフローで分析されるコードの量を減らす
 
@@ -111,27 +116,15 @@ Java、C、C++、C# などのコンパイルされた言語の場合、{% data v
 
 #### `schedule` イベント中にのみ実行する
 
-それでも分析が遅すぎるために、`push` または `pull_request` イベント中に実行できない場合は、`schedule` イベントでのみ分析をトリガーすることをお勧めします。 For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Results differ between analysis platforms
-
-If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
-
-On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)."
-
-{% endif %}
+それでも分析が遅すぎるために、`push` または `pull_request` イベント中に実行できない場合は、`schedule` イベントでのみ分析をトリガーすることをお勧めします。 詳しい情報については、「[イベント](/actions/learn-github-actions/introduction-to-github-actions#events)」を参照してください。
 
 ### エラー: 「サーバーエラー」
 
 サーバーエラーにより {% data variables.product.prodname_code_scanning %} のワークフローが実行できない場合は、ワークフローを再実行してください。 問題が解決しない場合は、{% data variables.contact.contact_support %} にお問い合わせください。
 
 ### エラー:「ディスク不足」または「メモリ不足」
-On very large projects,
 
-{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the hosted {% data variables.product.prodname_actions %} runner. この問題が発生した場合は、ランナーのメモリを増やしてみてください。
 
 ### Warning: "git checkout HEAD^2 is no longer necessary"
 
@@ -146,29 +139,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
-For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
+{% data variables.product.prodname_codeql %} ワークフローファイルの編集に関する詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を編集する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index dd2399ed77..bb6caa6ea0 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,27 +10,29 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
 ### {% data variables.product.prodname_code_scanning %} に対する SARIF ファイルのアップロードについて
 
-SARIF ファイルに `partialFingerprints` が含まれていない場合、`upload-sarif` アクションは、`partialFingerprints` フィールドを計算し、アラートの重複を防止しようと試みます。 {% data variables.product.prodname_dotcom %} は、リポジトリに SARIF ファイルと静的分析で使用されるソースコードの両方が含まれている場合にのみ、`partialFingerprints` を作成できます。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
+SARIF ファイルに `partialFingerprints` が含まれていない場合、`upload-sarif` アクションは、`partialFingerprints` フィールドを計算し、アラートの重複を防止しようと試みます。 {% data variables.product.prodname_dotcom %} は、リポジトリに SARIF ファイルと静的分析で使用されるソースコードの両方が含まれている場合にのみ、`partialFingerprints` を作成できます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)」を参照してください。
 
-You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. 詳しい情報については「[{% data variables.product.prodname_code_scanning %}の SARIF サポート](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)」を参照してください。
+SARIF ファイルは、{% data variables.product.prodname_codeql %} を含む多くの静的解析セキュリティテストツールを使用して生成できます。 生成するファイルは、SARIF バージョン 2.1.0 である必要があります。 詳しい情報については「[{% data variables.product.prodname_code_scanning %}の SARIF サポート](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)」を参照してください。
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+解析結果は {% data variables.product.prodname_actions %} (ベータプログラムに参加する Organization が使用可能)、{% data variables.product.prodname_code_scanning %} API、または {% data variables.product.prodname_codeql_runner %} を使用してアップロードできます。 最適なアップロード方法は、SARIF ファイルの生成方法によって異なります。以下、例を示します。
 
-- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. SARIF ファイルは、ファイルのアップロードに使用したものと同じ {% data variables.product.prodname_actions %} ワークフローで実行する SARIF 互換の分析ツールから生成できます。
+- {% data variables.product.prodname_actions %} を使用して {% data variables.product.prodname_codeql %} アクションを実行している場合、追加のアクションは不要です。 SARIF ファイルは、ファイルのアップロードに使用したものと同じ {% data variables.product.prodname_actions %} ワークフローで実行する SARIF 互換の分析ツールから生成できます。
 - "[ワークフロー実行の管理](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)"
-- {% data variables.product.prodname_dotcom %} は、リポジトリにアップロードされた SARIF ファイルからの {% data variables.product.prodname_code_scanning %} アラートを表示します。 If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
-- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
+- {% data variables.product.prodname_dotcom %} は、リポジトリにアップロードされた SARIF ファイルからの {% data variables.product.prodname_code_scanning %} アラートを表示します。 自動的なアップロードをブロックしている場合、結果をアップロードする準備ができたら `upload` コマンドを使用できます (詳しい情報については、「[CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」を参照)。
+- 結果をリポジトリ外に成果物として生成するツールの場合、{% data variables.product.prodname_code_scanning %} API を使用してファイルをアップロードできます (詳しい情報については、「[解析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」を参照)。
 
 {% data reusables.code-scanning.not-available %}
 
 ### {% data variables.product.prodname_actions %} での {% data variables.product.prodname_code_scanning %} 分析をアップロードする
 
-サードパーティの SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードするには、{% data variables.product.prodname_actions %} ワークフローが必要です。 For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+サードパーティの SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードするには、{% data variables.product.prodname_actions %} ワークフローが必要です。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/getting-started-with-github-actions/about-github-actions)」および「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
 ワークフローは、`upload-sarif` アクションを使用する必要があります。 これには、アップロードの設定に使用できる入力パラメータがあります。 使用する主な入力パラメータは、アップロードする SARIF ファイルのファイルまたはディレクトリを設定する `sarif-file` です。 ディレクトリまたはファイルのパスは、リポジトリのルートからの相対パスです。 詳しい情報については、「[`upload-sarif` アクション](https://github.com/github/codeql-action/tree/HEAD/upload-sarif)」を参照してください。
 
@@ -46,7 +48,7 @@ SARIF ファイルをリポジトリにコミットした後でアップロー
 
 この例のワークフローは、コミットがリポジトリにプッシュされるたびに実行されます。 アクションは `partialFingerprints` プロパティを使用して、変更が発生したかどうかを判断します。 コミットがプッシュされたときに実行されるだけでなく、ワークフローは週に 1 回実行されるようにスケジュールされます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-このワークフローは、リポジトリのルートにある `results.sarif` ファイルをアップロードします。 For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+このワークフローは、リポジトリのルートにある `results.sarif` ファイルをアップロードします。 ワークフローファイルの作成に関する詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
 または、このワークフローを変更して、SARIF ファイルのディレクトリをアップロードすることもできます。 たとえば、すべての SARIF ファイルをリポジトリのルートにある `sarif-output` というディレクトリに配置し、アクションの入力パラメータ `sarif_file` を `sarif-output` に設定できます。
 
@@ -54,24 +56,26 @@ SARIF ファイルをリポジトリにコミットした後でアップロー
 name: "Upload SARIF"
 
 # コードがリポジトリにプッシュされるたびに、スケジュールに従ってワークフローを実行します。
-# The scheduled workflow runs every Friday at 15:45 UTC.
+# スケジュールされたワークフローは、毎週金曜日の 15:45（UTC）に実行されます。
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # このステップでは、リポジトリのコピーをチェックアウトします。
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # リポジトリのルートに対する SARIF ファイルへの相対パス
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### ESLint 分析ツールを実行するワークフローの例
@@ -80,38 +84,41 @@ jobs:
 
 この例のワークフローは、コミットがリポジトリにプッシュされるたびに実行されます。 アクションは `partialFingerprints` プロパティを使用して、変更が発生したかどうかを判断します。 コミットがプッシュされたときに実行されるだけでなく、ワークフローは週に 1 回実行されるようにスケジュールされます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-ワークフローでは、ESLint 静的分析ツールをワークフローのステップとして実行する例を示しています。 `Run ESLint` ステップは ESLint ツールを実行して、`results.sarif` ファイルを出力します。 次に、ワークフローは `upload-sarif` アクションを使用して、`results.sarif` ファイルを {% data variables.product.prodname_dotcom %} にアップロードします。 For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+ワークフローでは、ESLint 静的分析ツールをワークフローのステップとして実行する例を示しています。 `Run ESLint` ステップは ESLint ツールを実行して、`results.sarif` ファイルを出力します。 次に、ワークフローは `upload-sarif` アクションを使用して、`results.sarif` ファイルを {% data variables.product.prodname_dotcom %} にアップロードします。 ワークフローファイルの作成に関する詳しい情報については、「[GitHub Actions 入門](/actions/learn-github-actions/introduction-to-github-actions)」を参照してください。
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # コードがリポジトリにプッシュされるたびに、スケジュールに従ってワークフローを実行します。
-# The scheduled workflow runs every Monday at 15:45 UTC.
+# スケジュールされたワークフローは、毎週月曜日の 15:45（UTC）に実行されます。
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### 参考リンク
 
 - [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)"
-- "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
+- 「[ワークフロー履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」
+- 「[CI システムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行する](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」
+- 「[解析を SARIF データとしてアップロードする](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)」
diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index 8dc0a11889..11873c61be 100644
--- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ja-JP/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/ja-JP/content/github/getting-started-with-github/about-git-subtree-merges.md
index 829b72fe92..d007581360 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 通常、サブツリーのマージはリポジトリ内にリポジトリを格納するために使われます。 「サブリポジトリ」はメインのリポジトリのフォルダー内に格納されます。
 
 サブツリーマージは、例で説明するのが最も分かりやすいでしょう。 以下のように進めます:
@@ -106,5 +108,5 @@ $ git pull -s subtree spoon-knife main
 
 ### 参考リンク
 
-- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
+- [_Pro Git_ ブックの「高度なマージ」の章](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
 - [サブツリーマージの戦略の使い方](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)
diff --git a/translations/ja-JP/content/github/getting-started-with-github/about-remote-repositories.md b/translations/ja-JP/content/github/getting-started-with-github/about-remote-repositories.md
index 9ee4143b3d..c7c322e7ba 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/about-remote-repositories.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/about-remote-repositories.md
@@ -46,9 +46,9 @@ git remote add origin <em> &lt;REMOTE_URL> </em>
 
 For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
 
-### Cloning with HTTPS URLs
+### HTTPS URL を使ってクローンを作成する
 
-The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy.
+`https://` は、可視性に関係なく、すべてのリポジトリで使用できます。 `https://` のクローン URL は、ファイアウォールまたはプロキシの内側にいる場合でも機能します。
 
 コマンドラインで、HTTPS URL を使用してリモートリポジトリに `git clone`、`git fetch`、`git pull` または `git push` を行った場合、{% data variables.product.product_name %} のユーザ名とパスワードの入力を求められます。 {% data reusables.user_settings.password-authentication-deprecation %}
 
@@ -62,7 +62,7 @@ The `https://` clone URLs are available on all repositories, regardless of visib
 
 {% endtip %}
 
- {% if currentVersion == "free-pro-team@latest" %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. 詳細は、「[HTTPS ポートを介して SSH を使用する](/github/authenticating-to-github/using-ssh-over-the-https-port)」を参照してください。{% endif %}
+ {% if currentVersion == "free-pro-team@latest" %}SSH を使用したくてもポート 22 で接続できない場合は、HTTPS ポートを介する SSH を使用できる場合があります。 詳細は、「[HTTPS ポートを介して SSH を使用する](/github/authenticating-to-github/using-ssh-over-the-https-port)」を参照してください。{% endif %}
 
 ### SSH URL を使ってクローンする
 
@@ -70,7 +70,7 @@ SSH URL は、SSH (安全なプロトコル) を介した Git リポジトリへ
 
 SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git push` をリモートリポジトリに実行すると、パスワードの入力を求められ、SSH キーパスフレーズを入力する必要があります。 詳しい情報については[SSH キーのパスフレーズを使う](/github/authenticating-to-github/working-with-ssh-key-passphrases)を参照してください。
 
-{% if currentVersion == "free-pro-team@latest" %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. 詳しい情報については「[SAMLシングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」および「[SAML シングルサインオンで使うためにSSHキーを認可する](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}SAML シングルサインオン (SSO) を使用している Organization にアクセスしている場合は、認証を受ける前に Organization にアクセスする SSH キーを認可する必要があります。 詳しい情報については「[SAMLシングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」および「[SAML シングルサインオンで使うためにSSHキーを認可する](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
 
 {% tip %}
 
@@ -80,9 +80,9 @@ SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 
-### Cloning with {% data variables.product.prodname_cli %}
+### {% data variables.product.prodname_cli %} を使ってクローンを作成する
 
-You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation.
+{% data variables.product.prodname_cli %} をインストールして、ターミナルで {% data variables.product.product_name %} ワークフローを使用することもできます。 詳しい情報については、[{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) のドキュメントを参照してください。
 
 {% endif %}
 
diff --git a/translations/ja-JP/content/github/getting-started-with-github/be-social.md b/translations/ja-JP/content/github/getting-started-with-github/be-social.md
index e30cc8c4f7..d240810d4c 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/be-social.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/be-social.md
@@ -38,6 +38,10 @@ topics:
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### さらなる活動
 
 #### プルリクエストを作成する
@@ -68,8 +72,8 @@ Organizationは、企業やオープンソースプロジェクトが多くの
 
 ![プロジェクトに Star を付ける](/assets/images/help/stars/star-a-project.png)
 
-- [Git のセットアップ](/articles/set-up-git)
-- [リポジトリの作成](/articles/create-a-repo)
-- [リポジトリのフォーク](/articles/fork-a-repo)
+- [Git をセットアップする](/articles/set-up-git)
+- 「[リポジトリを作成する](/articles/create-a-repo)」
+- [リポジトリをフォークする](/articles/fork-a-repo)
 - **ソーシャル機能**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/ja-JP/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/ja-JP/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index cd01c1e64a..7de931b78a 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 キーボードで <kbd>return</kbd> を押すたびに、行終端と呼ばれる目に見えない文字が挿入されています。 行終端の処理は、オペレーティングシステムによって異なります。
 
-Git と {% data variables.product.product_name %}でコラボレートしているとき、自分が Windows マシンを使用し、コラボレーターが OS X で変更した場合、Git により予想外の結果が生じる可能性があります。
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 異なるオペレーティングシステムを使用しているユーザとも効果的にコラボレーションができるように、自動的に行終端を処理するよう Git を設定することができます。
 
@@ -25,11 +25,11 @@ Git による行終端の扱い方を変更するには `git config core.autocrl
 
 {% mac %}
 
-OS X では、設定に `input` を渡すだけです。 例:
+On macOS, you simply pass `input` to the configuration. 例:
 
 ```shell
 $ git config --global core.autocrlf input
-# Configure Git to ensure line endings in files you checkout are correct for OS X
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md b/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md
index deb52da0ad..e146473547 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md
@@ -15,6 +15,8 @@ topics:
   - Accounts
 ---
 
+### リポジトリの作成
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 オープンソースプロジェクトを含む、さまざまなプロジェクトを {% data variables.product.product_name %} リポジトリに保存できます。 [オープンソースプロジェクト](http://opensource.org/about)では、より優れた信頼性のあるソフトウェアを作成するためにコードを共有できます。
@@ -29,7 +31,7 @@ topics:
 
 {% note %}
 
-**メモ:** オープンソースプロジェクトのパブリックリポジトリを作成できます。 パブリックリポジトリを作成する際は、他のユーザにどのようにプロジェクトを共有してほしいのかを定義する[ライセンスファイル](http://choosealicense.com/)を含めるようにしてください。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
+**メモ:** オープンソースプロジェクトのパブリックリポジトリを作成できます。 パブリックリポジトリを作成する際は、他のユーザにどのようにプロジェクトを共有してほしいのかを定義する[ライセンスファイル](https://choosealicense.com/)を含めるようにしてください。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md b/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md
index b513d3b793..42f7f2c250 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### フォークについて
+
 一般的にフォークは、他のユーザのプロジェクトへの変更を提案するため、あるいは他のユーザのプロジェクトを自分のアイディアの出発点として活用するために使用します。
 
 #### 他のユーザのプロジェクトへの変更を提案する
@@ -34,7 +36,7 @@ topics:
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-他のユーザのプロジェクトのフォークからパブリックリポジトリを作成する際は、プロジェクトの他者との共有方法を定義するライセンスファイルを必ず含めてください。 詳しい情報については、choosealicense.com の「[オープンソースのライセンスを選択する](http://choosealicense.com/)」を参照してください。
+他のユーザのプロジェクトのフォークからパブリックリポジトリを作成する際は、プロジェクトの他者との共有方法を定義するライセンスファイルを必ず含めてください。 詳しい情報については、choosealicense.com の「[オープンソースのライセンスを選択する](https://choosealicense.com/)」を参照してください。
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
@@ -154,5 +156,6 @@ Spoon-Knife リポジトリのフォークのローカルのコピーができ
 
 - [Git をセットアップする](/articles/set-up-git)
 - 「[リポジトリを作成する](/articles/create-a-repo)」
+- **リポジトリのフォーク**
 - [交流する](/articles/be-social)
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/ja-JP/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/ja-JP/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index 9c1fd97439..a9370a6a22 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 これらのコマンドは[リモートリポジトリ](/github/getting-started-with-github/about-remote-repositories)の操作時に非常に便利です。 `clone` および `fetch` は、リポジトリのリモート URL からお使いのローカルのコンピュータにリモートコードをダウンロードします。`merge` は、他のユーザの作業を自分のものとマージするために使用します。`pull` は、`fetch` と `merge` の組み合わせです。
 
 ### リポジトリをクローンする
@@ -72,5 +74,5 @@ $ git pull <em>remotename</em> <em>branchname</em>
 
 ### 参考リンク
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% if currentVersion == "free-pro-team@latest" %}
+- [_Pro Git_ ブックの「リモートでの作業」](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes){% if currentVersion == "free-pro-team@latest" %}
 - 「[接続の問題のトラブルシューティング](/articles/troubleshooting-connectivity-problems)」{% endif %}
diff --git a/translations/ja-JP/content/github/getting-started-with-github/git-workflows.md b/translations/ja-JP/content/github/getting-started-with-github/git-workflows.md
index f874c6e683..5706d0f2b1 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-{% data variables.product.prodname_dotcom %} フローの手法を使うと、Team の機能と {% data variables.product.prodname_dotcom %} でのコラボレーションを標準化することができます。 詳細は、{% data variables.product.prodname_dotcom %} ガイドで「[GitHub フロー](/github/collaborating-with-issues-and-pull-requests/github-flow)」と「[GitHub のフローを理解する](http://guides.github.com/overviews/flow/)」を参照してください。
+{% data variables.product.prodname_dotcom %} フローの手法を使うと、Team の機能と {% data variables.product.prodname_dotcom %} でのコラボレーションを標準化することができます。 For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-flow.md b/translations/ja-JP/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..1b109cab37
--- /dev/null
+++ b/translations/ja-JP/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: GitHub のフロー
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### はじめに
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### 必要な環境
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. 詳しい情報については[リポジトリ内でのブランチの作成と削除](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)を参照してください。
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### Pull Requestの作成
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. 詳しい情報については[プルリクエストの作成](/articles/creating-a-pull-request)を参照してください。
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. 詳しい情報については、「[ステータスチェックについて](/github/collaborating-with-issues-and-pull-requests/about-status-checks)」を参照してください。
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. プルリクエストは自動的に更新されます。
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. 詳しい情報については[プルリクエストのマージ](/articles/merging-a-pull-request)を参照してください。
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. 詳細は「[マージコンフリクトに対処する](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)」を参照してください。
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)を参照してください。
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md
index b4417222ac..fdddcdcf2d 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ VPN で Enterprise にアクセスする必要がある場合、{% data variable
 
 {% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_mobile %} を使用するには、デバイスに {% data variables.product.prodname_mobile %} 1.4 以降をインストールする必要があります。
 
-{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_mobile %} を使用するには、{% data variables.product.product_location %} がバージョン 3.0 以降であり、Enterprise オーナーが Enterprise に対してモバイルサポートを有効にしている必要があります。 詳しい情報については、「[リリースノート](/enterprise-server/admin/release-notes)」と「[Enterprise 向けに {% data variables.product.prodname_mobile %} を管理する](/admin/configuration/managing-github-for-mobile-for-your-enterprise)」を参照してください。
+{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_mobile %} を使用するには、{% data variables.product.product_location %} がバージョン 3.0 以降であり、Enterprise オーナーが Enterprise に対してモバイルサポートを有効にしている必要があります。 For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 {% data variables.product.prodname_ghe_server %} を使用した {% data variables.product.prodname_mobile %} のベータでは、{% data variables.product.prodname_dotcom_the_website %} のユーザアカウントでサインインする必要があります。
 
diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-language-support.md b/translations/ja-JP/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/ja-JP/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md
index 8d495d1ec6..d545602fe0 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 {% data variables.product.prodname_dotcom %}では無償版と有償版の製品をご用意しています。 各製品の料金と機能の全リストは <{% data variables.product.pricing_url %}> に掲載されています。 {% data reusables.products.product-roadmap %}
 
 ### ユーザアカウント用の{% data variables.product.prodname_free_user %}
@@ -99,14 +101,3 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる
 {% data variables.product.prodname_ghe_cloud %} を評価するためのトライアルを設定できます。 詳しい情報については、「<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} のトライアルを設定する</a>」を参照してください。
 
 [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com)の独自インスタンスのホストに関する詳しい情報については、{% data variables.contact.contact_enterprise_sales %}に連絡してください。 {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-{% data variables.product.prodname_ghe_one %} には [{% data variables.product.prodname_enterprise %}](#github-enterprise) と、以下が含まれます。
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。{% endif %}
-- [Organization の {% data variables.product.prodname_learning %}](https://lab.github.com/organizations)
-
-{% data variables.product.prodname_ghe_one %} へのサインアップの詳細については、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。
diff --git a/translations/ja-JP/content/github/getting-started-with-github/index.md b/translations/ja-JP/content/github/getting-started-with-github/index.md
index 8f54aa88a6..0f6d895a5f 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/index.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md
index d5da0e589f..1b911faecb 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/keyboard-shortcuts.md
@@ -36,12 +36,16 @@ versions:
 | <kbd>g</kbd> <kbd>p</kbd> | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/articles/about-pull-requests)」を参照してください。"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | <kbd>g</kbd> <kbd>a</kbd> | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %}
 | <kbd>g</kbd> <kbd>b</kbd> | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。                                                                                                               |
-| <kbd>g</kbd> <kbd>w</kbd> | [**Wiki**] タブに移動します。 詳細は「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」を参照してください。                                                                                           |
+| <kbd>g</kbd> <kbd>w</kbd> | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ### ソースコード編集
 
 | キーボードショートカット                                                     | 説明                                                  |
 | ---------------------------------------------------------------- | --------------------------------------------------- |
+| <kbd>control b</kbd> または <kbd>command b</kbd>                    | 太字テキストの Markdown 書式を挿入します                           |
+| <kbd>control i</kbd> または <kbd>command i</kbd>                    | イタリック体のテキストの Markdown 書式を挿入します                      |
+| <kbd>control k</kbd> または <kbd>command k</kbd>                    | リンクを作成するための Markdown 書式を挿入します                       |
 | <kbd>e</kbd>                                                     | [**Edit file**] タブでソースコードファイルを開きます                  |
 | <kbd>control f</kbd> または <kbd>command f</kbd>                    | ファイルエディタで検索を開始します                                   |
 | <kbd>control g</kbd> または <kbd>command g</kbd>                    | 次を検索します                                             |
diff --git a/translations/ja-JP/content/github/getting-started-with-github/learning-about-github.md b/translations/ja-JP/content/github/getting-started-with-github/learning-about-github.md
index 08f8dbb60c..fcb8e3a2b7 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub について学ぶ
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/ja-JP/content/github/getting-started-with-github/managing-remote-repositories.md b/translations/ja-JP/content/github/getting-started-with-github/managing-remote-repositories.md
index 14d86e3b11..852ab7e019 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/managing-remote-repositories.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/managing-remote-repositories.md
@@ -107,7 +107,7 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
 
 You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and personal access token every time it talks to GitHub.
 
-#### Switching remote URLs from HTTPS to SSH
+#### リモート URL の HTTPS から SSH への切り替え
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. ワーキングディレクトリをローカルプロジェクトに変更します。
diff --git a/translations/ja-JP/content/github/getting-started-with-github/pushing-commits-to-a-remote-repository.md b/translations/ja-JP/content/github/getting-started-with-github/pushing-commits-to-a-remote-repository.md
index b0e63b10c1..1b61220063 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/pushing-commits-to-a-remote-repository.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/pushing-commits-to-a-remote-repository.md
@@ -99,4 +99,4 @@ git fetch upstream
 - [`git remote` の man ページ](https://git-scm.com/docs/git-remote.html)
 - [Git チートシート](/articles/git-cheatsheet)
 - [Git のワークフロー](/github/getting-started-with-github/git-workflows)
-- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"
+- 「[Git ハンドブック](https://guides.github.com/introduction/git-handbook/)」
diff --git a/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md b/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md
index 8b939193ef..ce1e4e1c29 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md
@@ -22,6 +22,8 @@ topics:
   - Accounts
 ---
 
+### Git を使用する
+
 コマンドラインで Git を使うには、あなたのコンピュータに Git をダウンロードし、インストールし、設定する必要があります。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} コマンドラインから {% data variables.product.prodname_cli %} をインストールして {% data variables.product.product_name %} を使用することもできます。 {% data variables.product.prodname_cli %} の詳細については、[{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) ドキュメントを参照してください。{% endif %}
 
 ローカルで Git を動かしたいけれどもコマンドラインを使いたくない場合、代わりに [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) クライアントをダウンロードしインストールしてください。  詳しい情報については、「[{% data variables.product.prodname_desktop %} のインストールと設定](/desktop/installing-and-configuring-github-desktop/)」を参照してください。
diff --git a/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 8eac4c10e4..c8084d752f 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ topics:
 
 Organization の {% data variables.product.prodname_free_team %} にダウングレードすると、トライアル期間中に設定した SAML 設定も無効になります。 {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入すると、Organization 内のユーザーが認証できるように SAML 設定が再度有効になります。
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. [{% data variables.product.prodname_ghe_cloud %} Free Trial] の下で、[**Buy Enterprise**] または [**Downgrade to Team**] をクリックします。 ![[Buy Enterprise and Downgrade to Team] ボタン](/assets/images/help/organizations/finish-trial-buttons.png)
 6. プロンプトに従ってお支払い方法を入力し、[**Submit**] をクリックします。
 
diff --git a/translations/ja-JP/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md b/translations/ja-JP/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md
index 5431950a54..4fed46abf3 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md
@@ -38,7 +38,7 @@ versions:
     - `BRANCH-NAME`: `master` や `gh-pages` などの、現在のプロジェクトのデフォルトブランチです。
     ```shell
     $ git filter-branch --prune-empty --subdirectory-filter <em>FOLDER-NAME BRANCH-NAME</em>
-    # Filter the specified branch in your directory and remove empty commits
+    # ディレクトリ内の指定されたブランチをフィルタし、空のコミットを削除する
     > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
     > Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
     ```
diff --git a/translations/ja-JP/content/github/getting-started-with-github/updating-credentials-from-the-macos-keychain.md b/translations/ja-JP/content/github/getting-started-with-github/updating-credentials-from-the-macos-keychain.md
index 560098094a..67ded09004 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/updating-credentials-from-the-macos-keychain.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/updating-credentials-from-the-macos-keychain.md
@@ -1,6 +1,6 @@
 ---
-title: Updating credentials from the macOS Keychain
-intro: 'You''ll need to update your saved credentials in the `git-credential-osxkeychain` helper if you change your{% if currentVersion != "github-ae@latest" %} username, password, or{% endif %} personal access token on {% data variables.product.product_name %}.'
+title: macOS キーチェーンからの認証情報を更新する
+intro: '{% data variables.product.product_name %} で{% if currentVersion != "github-ae@latest" %}ユーザ名、パスワード、{% endif %}または個人アクセストークンを変更する場合は、 `git-credential-osxkeychain` ヘルパーに保存されている認証情報を更新する必要があります。'
 redirect_from:
   - /articles/updating-credentials-from-the-osx-keychain
   - /github/using-git/updating-credentials-from-the-osx-keychain
@@ -15,14 +15,14 @@ versions:
 
 ### キーチェーンアクセスを介して認証情報を更新する
 
-1. Click on the Spotlight icon (magnifying glass) on the right side of the menu bar. Type `Keychain access` then press the Enter key to launch the app. ![スポットライト検索バー](/assets/images/help/setup/keychain-access.png)
+1. メニューバーの右側にある Spotlight アイコン (虫眼鏡) をクリックします。 `Keychain access` と入力し、Enter キーを押してアプリを起動します。 ![スポットライト検索バー](/assets/images/help/setup/keychain-access.png)
 2. キーチェーン Access で、**{% data variables.command_line.backticks %}** を探してください。
 3. `{% data variables.command_line.backticks %}` の「internet password」エントリを見つけてください。
 4. 適宜、エントリを編集または削除します。
 
 ### コマンドラインで認証情報を削除する
 
-Through the command line, you can use the credential helper directly to erase the keychain entry.
+コマンドラインから、認証情報ヘルパーを直接使用して、キーチェーンエントリを消去できます。
 
 ```shell
 $ git credential-osxkeychain erase
@@ -31,7 +31,7 @@ protocol=https
 > <em>[Press Return]</em>
 ```
 
-成功した場合、何もプリントアウトされません。 To test that it works, try and clone a private repository from {% data variables.product.product_location %}. If you are prompted for a password, the keychain entry was deleted.
+成功した場合、何もプリントアウトされません。 それが機能するかどうかをテストするには、{% data variables.product.product_location %} からプライベートリポジトリのクローンを作成します。 パスワードの入力を求められた場合は、キーチェーンエントリが削除されています。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/ja-JP/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index 9811691352..d025c403ee 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 この例では、`exec` を除く、利用可能なすべての ` git rebase ` コマンドについて説明します。
 
 端末で `git rebase --interactive HEAD~7` と入力して、リベースを開始します。 お気に入りのテキストエディタに以下の行が表示されます:
@@ -125,10 +127,10 @@ i cant' typ goods
 Git の履歴を変更したので、通常の `git push origin` **は動作しません**。 最新の変更を「強制プッシュ」して、コマンドを変更する必要があります:
 
 ```shell
-# Don't override changes
+# 変更をオーバーライドしない
 $ git push origin main --force-with-lease
 
-# Override changes
+# 変更をオーバーライドする
 $ git push origin main --force
 ```
 
diff --git a/translations/ja-JP/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md b/translations/ja-JP/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md
index 0db6cee980..f60b21a3a1 100644
--- a/translations/ja-JP/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md
+++ b/translations/ja-JP/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md
@@ -10,11 +10,11 @@ versions:
   github-ae: '*'
 ---
 
-HTTPS リモート URL を使用すると、 SSH を使用するときと比べていくつかの利点があります。 SSH よりも、設定が簡単です。 通常は厳密なファイアウォールやプロキシを介して動作します。 However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository.
+HTTPS リモート URL を使用すると、 SSH を使用するときと比べていくつかの利点があります。 SSH よりも、設定が簡単です。 通常は厳密なファイアウォールやプロキシを介して動作します。 ただし、リポジトリをプルまたはプッシュするたびに、{% data variables.product.product_name %} の認証情報を入力するように求められます。
 
 {% data reusables.user_settings.password-authentication-deprecation %}
 
-[認証情報をキャッシュする](/github/getting-started-with-github/caching-your-github-credentials-in-git)よう Git を設定すれば、パスワードの入力を求められなくなります。 Once you've configured credential caching, Git automatically uses your cached personal access token when you pull or push a repository using HTTPS.
+[認証情報をキャッシュする](/github/getting-started-with-github/caching-your-github-credentials-in-git)よう Git を設定すれば、パスワードの入力を求められなくなります。 認証情報のキャッシュを設定すると、HTTPS を使用してリポジトリをプルまたはプッシュするときに、Git はキャッシュされた個人アクセストークンを自動的に使用します。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/ja-JP/content/github/importing-your-projects-to-github/about-github-importer.md
index 07c68ba496..c94655aaaf 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Importerについて
-intro: ソースコードがSubversion、Mercurial、Team Foundation Server、あるいは他のGitリポジトリにあるなら、GitHub Importerを使ってそれをGitHubに移せます。
+intro: 'If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer.'
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ GitHub Importerは、コミットやリビジョン履歴を含めてソース
 
 インポートの間、インポート元のバージョン管理システムによって、リモートリポジトリでの認証、コミット作者の属性の更新、大きなファイルを持つリポジトリのインポート（あるいはGit Large File Storageを使いたくない場合は大きなファイルの削除）が行えます。
 
-| インポートのアクション                                                                       | Subversion | Mercurial | Team Foundation Server |  Git  |
-|:--------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:|
-| リモートリポジトリでの認証                                                                     |   **X**    |   **X**   |         **X**          | **X** |
-| [コミット作者の属性の更新](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   |         **X**          |       |
-| 大きなファイルの[Git Large File Storage](/articles/about-git-large-file-storage)への移動      |   **X**    |   **X**   |         **X**          |       |
-| リポジトリからの大きなファイルの削除                                                                |   **X**    |   **X**   |         **X**          |       |
+| インポートのアクション                                                                       | Subversion | Mercurial | TFVC  |  Git  |
+|:--------------------------------------------------------------------------------- |:----------:|:---------:|:-----:|:-----:|
+| リモートリポジトリでの認証                                                                     |   **X**    |   **X**   | **X** | **X** |
+| [コミット作者の属性の更新](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   | **X** |       |
+| 大きなファイルの[Git Large File Storage](/articles/about-git-large-file-storage)への移動      |   **X**    |   **X**   | **X** |       |
+| リポジトリからの大きなファイルの削除                                                                |   **X**    |   **X**   | **X** |       |
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/ja-JP/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index ae78911eca..08858c3c2d 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-Subversion、Mercurial、Team Foundation Server や他の Git リポジトリからプロジェクトをインポートするために、[GitHub Importer](/articles/about-github-importer) を使うことをおすすめします。 これらの外部ツールを使って、プロジェクトを Git に変換することもできます。
+We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. これらの外部ツールを使って、プロジェクトを Git に変換することもできます。
 
 {% endif %}
 
@@ -32,12 +32,9 @@ Subversion リポジトリを Git にコンバートするには、これらの
 
 Mercurial リポジトリを Git にコンバートするには、 [hg-fast-export](https://github.com/frej/fast-export) をおすすめします。
 
-### Team Foundation Server からインポートする
+### Importing from TFVC
 
-Team Foundation Server と Git の間で変更を反映するには、これらのツールをおすすめします。
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
 
 {% tip %}
 
diff --git a/translations/ja-JP/content/github/index.md b/translations/ja-JP/content/github/index.md
index 2c9c20951b..42a44ec754 100644
--- a/translations/ja-JP/content/github/index.md
+++ b/translations/ja-JP/content/github/index.md
@@ -36,7 +36,6 @@ versions:
 {% link_in_list /collaborating-with-issues-and-pull-requests %}
 
 {% link_in_list /managing-your-work-on-github %}
-{% link_in_list /developing-online-with-codespaces %}
 
 {% link_in_list /searching-for-information-on-github %}
 
@@ -57,7 +56,6 @@ versions:
 
 {% link_in_list /extending-github %}
 
-{% link_in_list /supporting-the-open-source-community-with-github-sponsors %}
 {% link_in_list /finding-talent-with-github-jobs %}
 {% link_in_list /working-with-github-support %}
 {% link_in_list /understanding-how-github-uses-and-protects-your-data %}
diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index 0ed40d4178..63a8ec5d19 100644
--- a/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/ja-JP/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### {% data variables.product.prodname_dotcom %} のナビゲーションコードについて
 
 コードナビゲーションでは、オープンソースライブラリの [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) を使用します。 以下の言語がサポートされています:
diff --git a/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index c6c5b9f8da..c624b3748d 100644
--- a/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -38,7 +38,7 @@ versions:
 
 {% data variables.large_files.product_name_short %} からファイルを削除した後でも、{% data variables.large_files.product_name_short %} オブジェクトはそのままリモートストレージに存在し{% if currentVersion == "free-pro-team@latest" %}、{% data variables.large_files.product_name_short %} のストレージ容量に対するカウントも継続します{% endif %}。
 
-リポジトリから {% data variables.large_files.product_name_short %} オブジェクトを削除するには、{% if currentVersion == "free-pro-team@latest" %}リポジトリを削除して再作成します。 リポジトリを削除すると、関連する Issue、Star、フォークもすべて削除されます。 詳しい情報については、「[リポジトリを削除する](/github/administering-a-repository/deleting-a-repository)」を参照するか、{% else %}{% data variables.product.prodname_enterprise %} 管理者に連絡してオブジェクトをアーカイブします。 アーカイブ化されたオブジェクトは、3 か月後にパージされます。{% endif %}
+リポジトリから {% data variables.large_files.product_name_short %} オブジェクトを削除するには、{% if currentVersion == "free-pro-team@latest" %}リポジトリを削除して再作成します。 リポジトリを削除すると、関連する Issue、Star、フォークもすべて削除されます。 For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. アーカイブ化されたオブジェクトは、3 か月後にパージされます。{% endif %}
 
 {% note %}
 
diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index f1b1808dd1..18dc0c0c02 100644
--- a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,91 +1,72 @@
 ---
-title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
-redirect_from:
-  - /articles/about-security-alerts-for-vulnerable-dependencies
-  - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
+title: 脆弱性のある依存関係に関するアラートについて
+intro: '{% data variables.product.product_name %} は、リポジトリに影響を与える脆弱性を検出すると、{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を送信します。'
 versions:
   enterprise-server: <=2.22
 topics:
   - Security
 ---
- 
-### About vulnerable dependencies
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
+### 脆弱性のある依存関係について
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it.
+セキュリティ上の脆弱性があるパッケージにコードが依存している場合、この脆弱性のある依存関係により、プロジェクトまたはそれを使用するユーザにさまざまな問題が発生する可能性があります。
 
-### Detection of vulnerable dependencies
+### 脆弱性のある依存関係の検出
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} は脆弱性のある依存関係を検出し、{% data variables.product.prodname_dependabot_alerts %}を送信します{% else %}{% data variables.product.product_name %} は脆弱性のある依存関係を検出し、次の場合にセキュリティアラート{% endif %}を送信します。
 
-{% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."
-- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- 新しいアドバイザリデータが {% data variables.product.prodname_dotcom_the_website %} から 1 時間ごとに {% data variables.product.prodname_ghe_server %} に同期されたとき。 {% data reusables.security-advisory.link-browsing-advisory-db %}
+- リポジトリの依存関係グラフが変更されたとき。 たとえば、コントリビューターがコミットをプッシュして、依存するパッケージまたはバージョンを変更するとき。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
 
 {% data reusables.repositories.dependency-review %}
 
-For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+{% data variables.product.product_name %} が脆弱性と依存関係を検出できるエコシステムのリストについては、「[サポートされているパッケージエコシステム](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)」を参照してください。
 
 {% note %}
 
-**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use.
+**注釈:** マニフェストとロックファイルを最新の状態に保つことが重要です。 依存関係グラフが現在の依存関係とバージョンを正確に反映していない場合、使用する脆弱性のある依存関係のアラートを見逃す可能性があります。 また、使用しなくなった依存関係のアラートを受け取る場合もあります。
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
-### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
+### 脆弱性のある依存関係の {% data variables.product.prodname_dependabot %} アラート
 {% else %}
-### Security alerts for vulnerable dependencies
+### 脆弱性のある依存対象に関するセキュリティアラート
 {% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% 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.
-
-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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
-
-{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+ー
+{% data variables.product.product_name %} が脆弱性のある依存関係を特定すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 アラートには、プロジェクト内で影響を受けるファイルへのリンクと、修正バージョンに関する情報が含まれています。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。 詳しい情報については、「[脆弱性のある依存関係に対する通知を設定する](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)」を参照してください。
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. 
+ー
+{% data variables.product.product_name %} が脆弱性のある依存関係を特定すると、影響を受けるリポジトリのメンテナに、脆弱性の詳細、プロジェクト内の影響を受けるファイルへのリンク、および修正バージョンに関する情報を含むセキュリティアラートを送信します。
 {% endif %}
 
 {% warning %}
 
-**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.
+**注釈**: {% data variables.product.product_name %} のセキュリティの機能は、すべての脆弱性を捕捉するものではありません。 当社は常に脆弱性データベースを更新し、最新の情報でアラートを生成するよう努力していますが、一定の期間内にすべてをの問題を把握したり、既知の脆弱性について通知したりすることはできません。 これらの機能は、それぞれの依存関係の潜在的な脆弱性やその他の問題に関する人によるレビューを置き換えるものではなく、必要な場合にはセキュリティサービスによるコンサルティングや、総合的な脆弱性レビューを行うことをおすすめします。
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}セキュリティ{% endif %}アラートへのアクセス
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+特定のプロジェクトに影響を与えるすべてのアラートは、リポジトリの依存関係グラフで確認できます。
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+デフォルト設定では、影響を受けるリポジトリの管理者権限を持つユーザに
+{% data variables.product.prodname_dependabot_alerts %} について通知します。{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
+デフォルトでは、影響を受けるリポジトリで管理者権限を持つ人々にセキュリティアラートが送られます。
+{% data variables.product.product_name %} は、特定のリポジトリに対して特定された脆弱性を公表することはありません。
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Further reading
-
-- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %}詳細については、「[通知の配信方法を選択する](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)」を参照してください。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %}詳細については、「[脆弱性のある依存関係に対する通知を設定する](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)」を参照してください。{% endif %}
diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index 2768009d90..46e81ed652 100644
--- a/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,20 +1,18 @@
 ---
 title: 脆弱性のある依存関係の通知を設定する
 shortTitle: 通知を設定する
-intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} セキュリティ{% endif %}アラートに関する通知の受信方法を最適化します。'
+intro: '{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} セキュリティ{% endif %}アラートに関する通知の受信方法を最適化します。'
 versions:
   enterprise-server: '>=2.21 <=2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies for the current version of this article -->
+
 ### 脆弱性のある依存関係の通知について
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} がリポジトリ内にある脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。{% else %}{% data variables.product.product_name %} がリポジトリ内の脆弱性のある依存関係を検出すると、セキュリティアラートを送信します。{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} は、すべてのパブリックリポジトリでデフォルト設定で有効になっています。 {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} がリポジトリ内にある脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。{% else %}{% data variables.product.product_name %} がリポジトリ内の脆弱性のある依存関係を検出すると、セキュリティアラートを送信します。{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
 この機能を使用する前に、サイト管理者は
@@ -28,14 +26,14 @@ topics:
 
 {% if currentVersion ver_lt "enterprise-server@2.22" %}サイト管理者は、通知なしでセキュリティアラートを有効にすることもできます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %}の脆弱性のある依存関係に関するセキュリティアラートの有効化](/enterprise/{{ currentVersion }}/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。 {% endif %}
 
-### {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %} セキュリティアラートの通知を設定する{% endif %}
+### {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %} セキュリティアラートの通知を設定する{% endif %}
 
 各ページの上部に表示される [Manage notifications] ドロップダウン {% octicon "bell" aria-label="The notifications bell" %} から、自分または Organization の通知設定を構成できます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)」を参照してください。
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} オプション](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 {% else %}
   ![セキュリティアラートオプション](/assets/images/help/notifications-v2/security-alerts-options.png)
@@ -47,11 +45,11 @@ topics:
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「通知を[設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}」を参照してください。{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」を参照してください。
 
 ### 脆弱性のある依存関係の通知を減らす方法
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}の通知が多すぎる場合は、毎週のメールダイジェストを選択するか、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を有効にしたまま通知をオフにすることをお勧めします。 その場合でも、リポジトリの [Security] タブで{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を表示できます。{% if currentVersion == "free-pro-team@latest" %}詳細については、「[リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}の通知が多すぎる場合は、毎週のメールダイジェストを選択するか、{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を有効にしたまま通知をオフにすることをお勧めします。 その場合でも、リポジトリの [Security] タブで{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を確認することはできます。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md
index 60658a2c52..f4200e0c5d 100644
--- a/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### 目次
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index cf7a8dafdb..1e9881c654 100644
--- a/translations/ja-JP/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index 6d581bef2d..04afb3b82a 100644
--- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -26,13 +26,9 @@ topics:
 サブスクライブできる通知は次のとおりです。
 - 特定の Issue、プルリクエスト、または Gist の会話。
 - リポジトリまたは Team ディスカッション内のすべてのアクティビティ。
-- {% data variables.product.prodname_actions %} で設定されたリポジトリ内のワークフローのステータスなどの CI アクティビティ。
-{% if currentVersion == "free-pro-team@latest" %}
-- リポジトリ内の Issue、プルリクエスト、リリース、ディスカッション (有効な場合)。
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- リポジトリ内のリリース。
-{% endif %}
+- {% data variables.product.prodname_actions %} で設定されたリポジトリ内のワークフローのステータスなどの CI アクティビティ。 {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 フォークを除き、あなたがプッシュアクセスを持つすべてのリポジトリを自動的にWatchすることもできます。 [**Watch**] をクリックすると、手動でアクセスできる他のリポジトリを Watch できます。
 
diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index 39dcb8d346..9378b62d29 100644
--- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -57,13 +57,13 @@ topics:
 {% data reusables.notifications.access_notifications %}
 1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Watch しているリポジトリのページで、Watchしているリポジトリを評価した後、次のいずれかを選択します。
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
     - リポジトリの Watch 解除
-    - リポジトリのリリースのみを Watch
-    - リポジトリのすべての通知を無視
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
     - リポジトリの Watch 解除
-    - リポジトリのすべての通知を無視
-    - 通知を受け取るイベントの種類をカスタマイズ (Issue、プルリクエスト、リリース、ディスカッションが有効の場合)
-{% endif %}
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index 44033a0e05..d5aa736905 100644
--- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your subscriptions
-intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
+title: サブスクリプションを表示する
+intro: 通知の送信元と通知のボリュームを把握するため、定期的にサブスクリプションを確認し、リポジトリを Watch することをお勧めします。
 redirect_from:
   - /articles/subscribing-to-conversations/
   - /articles/unsubscribing-from-conversations/
@@ -22,84 +22,61 @@ topics:
   - Notifications
 ---
 
-You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
+{% data variables.product.product_name %} で進行中のアクティビティのサブスクリプションの通知を受け取ります。 会話をサブスクライブする理由はたくさんあります。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)」を参照してください。
 
-We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+健全な通知ワークフローの一環として、サブスクリプションの監査とサブスクライブ解除をお勧めします。 サブスクライブ解除に関する詳しい情報については、「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。
 
-### Diagnosing why you receive too many notifications
+### 通知過多の理由を診断する
 
-When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
+インボックスの通知が多すぎて管理できない場合は、サブスクリプションが多すぎないか確認したり、通知設定を変更して、サブスクリプションと受信する通知の種類を減らしたりすることを検討してください。 たとえば、設定を無効にして、チームまたはリポジトリに参加するたびにすべてのリポジトリとすべての Team ディスカッションを自動的に監視することを検討できます。
 
-![Automatic watching](/assets/images/help/notifications-v2/automatic-watching-example.png)
+![自動 Watch](/assets/images/help/notifications-v2/automatic-watching-example.png)
 
-For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
+詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)」を参照してください。
 
-To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." 
-{% if currentVersion == "free-pro-team@latest" %}
+リポジトリのサブスクリプションの概要を確認するには、「[Watch しているリポジトリを確認する](#reviewing-repositories-that-youre-watching)」を参照してください。
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
+**参考:** [Watch ページ](https://github.com/watching)または {% data variables.product.product_name %} の任意のリポジトリページにある [**Watch/Unwatch**] ドロップダウンリストの [**Custom**] オプションを使用して、通知するイベントの種類を選択できます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。
 
 {% endtip %}
 {% endif %}
 
-Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+過去に Watch することを選択したリポジトリが忘れらていることが多くあります。 「Watched repositories」ページから、リポジトリから素早く Watch 解除することができます。 サブスクライブ解除する方法について詳しくは、{% data variables.product.prodname_blog %} の「[Watch 解除の推奨](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)」および「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。 トリアージワークフローを作成して、受信する通知を支援することもできます。 トリアージワークフローのガイダンスについては、「[通知をトリアージするためのにワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。
 
-### Reviewing all of your subscriptions
+### サブスクリプションのリストを確認する
 
 {% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
-  ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
+1. 左側のサイドバーの、通知元のリポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[**Subscriptions**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
 
-2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
+2. フィルタとソートを使用して、サブスクリプションのリストを絞り込み、通知の受信を希望しない会話のサブスクリプションを解除します。
 
-  ![Subscriptions page](/assets/images/help/notifications-v2/all-subscriptions.png)
+  ![サブスクリプションページ](/assets/images/help/notifications-v2/all-subscriptions.png)
 
 {% tip %}
 
-**Tips:**
-- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
+**参考:**
+- 忘れている可能性のあるサブスクリプションを確認するには、[least recently subscribed] でソートします。
 
-- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
+- 引き続き通知が受信可能なリポジトリのリストを確認するには、[filter by repository] ドロップダウンメニューのリポジトリリストを参照します。
 
 {% endtip %}
 
-### Reviewing repositories that you're watching
+### Watch しているリポジトリを確認する
 
-1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
-  ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
-2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
+1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンメニューを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
+2. Watch しているリポジトリを評価し、それらの更新がまだ関連していて有用であるかどうかを判断します。 リポジトリを Watch すると、そのリポジトリのすべての会話が通知されます。
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
+  ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications.png)
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+  ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" %}when there are updates to issues, pull requests, releases or discussions (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
-  
-  When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
+
+  リポジトリを Watch 解除しても、@メンションされたときやスレッドに参加しているときには通知を受信することができます。 特定のイベントタイプの通知を受信するように設定すると、リポジトリにこれらのイベントタイプが更新された場合、スレッドに参加している場合、または参加している自分または Team が @メンションされた場合にのみ通知されます。
 
   {% endtip %}
-
-### Configuring your watch settings for an individual repository
-
-You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
-
-{% data reusables.repositories.navigate-to-repo %}
-2. In the upper-right corner, click the "Watch" drop-down menu to select a watch option.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-  ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-   ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
-{% data reusables.notifications-v2.custom-notifications-beta %}
-The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
-
-   ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2.png)
-
-If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
-
-{% endif %}
diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/ja-JP/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index aeabb23a66..60d8228b5e 100644
--- a/translations/ja-JP/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/ja-JP/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ topics:
 
 クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 たとえばクエリパラメータの`labels`を使うには、Issueにラベルを追加する権限を持っていなければなりません。
 
-クエリパラメータを使うのに不正なURLを作成したり、適切な権限を持っていなかったりした場合には、そのURLに対して404エラーページが返されます。
+If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page.
 
 ### サポートされているクエリパラメータ
 
diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/ja-JP/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index 739d191d6f..7f39d2aa19 100644
--- a/translations/ja-JP/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. 以下のオプションから 1 つ選択します:
     - 新しいマイルストーンを作成するには、[**New Milestone**] をクリックします。 ![[New milestone] ボタン](/assets/images/help/repository/new-milestone.png)
     - マイルストーンを編集するには、編集対象のマイルストーンの隣にある [**Edit**] をクリックします。 ![マイルストーンの編集](/assets/images/help/repository/edit-milestone.png)
-5. マイルストーンのタイトル、説明、その他の変更を入力し、[**Create milestone**] または [**Save changes**] をクリックします。
+5. マイルストーンのタイトル、説明、その他の変更を入力し、[**Create milestone**] または [**Save changes**] をクリックします。 Milestones will render Markdown syntax. For more information about Markdown syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
 
 ### マイルストーンの削除
 
diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/ja-JP/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index cc3eadb7d5..2bbe79f55c 100644
--- a/translations/ja-JP/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/ja-JP/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ Organization 内にあるリポジトリのプロジェクトボードを無効
 
 プロジェクトボードを無効化すると、タイムラインや[監査ログ](/articles/reviewing-the-audit-log-for-your-organization/)でプロジェクトボード情報を見ることができなくなります。
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Organization 全体のプロジェクトボードを無効化するのか、Organization 内にあるリポジトリのプロジェクトボードを無効化するのか、その両方なのかを判断します。 次に [Projects] の下で:
     - Organization 全体のプロジェクトボードを無効化するには、[**Enable projects for the organization**] の選択を解除します。
     - Organization 内にあるリポジトリのプロジェクトボードを無効化するには、[**Enable projects for all repositories**] の選択を解除します。 ![Organization や Organization の全リポジトリのプロジェクトを無効にするチェックボックス](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/ja-JP/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index 038f7e7229..58ebc0b7af 100644
--- a/translations/ja-JP/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: Issue およびプルリクエストのファイル添付
-intro: Issue を開いたりプルリクエストを更新したりする際に、Issue の添付を使用して機能の提案やバグのスクリーンショットの画像をアップロードできます。
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -14,7 +14,7 @@ topics:
 
 {% warning %}
 
-**警告:**Pull Request や Issue へのコメントに画像添付を追加した場合、その Pull Request がプライベートリポジトリのものである場合、{% if enterpriseServerVersions contains currentVersion %}またはプライベートモードが有効化されている場合も、{% endif %}匿名化した画像 URL は認証なしに誰もが見ることができます。 機密の画像をプライベートにしておきたい場合は、それらを認証が必要なプライベートなネットワークあるいはサーバーから提供するようにしてください。 {% if currentVersion == "free-pro-team@latest" %}匿名化した URL の詳細については、「[匿名化された画像 URL について](/articles/about-anonymized-image-urls)」を参照してください。{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ Issue やプルリクエストの会話にファイルを添付するには、
 
 {% endtip %}
 
-ファイルの最大サイズは 25MB で、画像の最大サイズは 10MB です。
-{% if currentVersion == "free-pro-team@latest" %}
-有料の GitHub プランのユーザまたは Organization が所有しているリポジトリでは、ビデオのサイズが最大 100MB になる可能性があります。
-
-{% note %}
-
-**注釈:** ビデオ添付ファイルのサポートは現在ベータであり、変更される可能性があります。
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 以下のファイルがサポートされています:
 
@@ -49,7 +43,7 @@ Issue やプルリクエストの会話にファイルを添付するには、
 * Microsoft Word (*.docx*)、Powerpoint (*.pptx*)、および Excel (*.xlsx*) 文書
 * テキストファイル (*.txt*)
 * PDF (*.pdf*)
-* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" %}
+* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * ビデオ(*.mp4*, *.mov*){% endif %}
 
 ![添付アニメーション GIF](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md b/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md
index 70a684cb18..7c833980cd 100644
--- a/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md
+++ b/translations/ja-JP/content/github/managing-your-work-on-github/managing-labels.md
@@ -49,6 +49,8 @@ topics:
 
 リポジトリの作成時に、すべての新しいリポジトリにデフォルトのラベルが含められますが、後でそのラベルを編集または削除できます。
 
+Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 Organization のオーナーは、Organization 内のリポジトリのためのデフォルトラベルをカスタマイズできます。 詳しい情報については、「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/ja-JP/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index 9b482ec02e..024f4d001d 100644
--- a/translations/ja-JP/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ topics:
 * 最もコメントされていない Issue およびプルリクエスト
 * 一番新しく更新された Issue またはプルリクエスト
 * 一番古くに更新された Issue またはプルリクエスト
-* Issue またはプルリクエストに対して最も加えられた[リアクション](/articles/about-conversations-on-github#reacting-to-ideas-in-comments)
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. 右上にあるソートドロップダウンメニューをクリックします。 ![ソートドロップダウンタブを使用する](/assets/images/help/issues/issues_sort_dropdown.png)
+1. 右上にあるソートドロップダウンメニューをクリックします。 ![ソートドロップダウンタブを使用する](/assets/images/help/issues/issues_sort_dropdown.png)
 
 ソートの選択を解除するには、[**Sort**] > [**Newest**] をクリックします。
 
diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-code.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-code.md
index ca482eacde..6b26cbdfa7 100644
--- a/translations/ja-JP/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ topics:
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) は、<em>app/public</em> ディレクトリやそのサブディレクトリ (たとえば<em>app/public/js/form-validators</em> に属すものも) にあって「console」という単語がある JavaScript のファイルにマッチします。 |
 
 ### 言語で検索
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-コードが書かれた言語で検索することができます。
+コードが書かれた言語で検索することができます。 The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | 修飾子                        | サンプル                                                                                                                                                                         |
 | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 9eff6666c9..d92bd3c0f1 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} 詳しい情報については、「[利用上限について](#about-spending-limits)」を参照してください。
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. 詳しい情報については、「[{% data variables.product.prodname_registry %} の紹介](/packages/learn-github-packages/introduction-to-github-packages)」を参照してください。
+
+{% endnote %}
 
 Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_registry %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index 5899498c17..0a853902e3 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### 参考リンク
 
-- [{% data variables.product.prodname_sponsors %} について](/articles/about-github-sponsors)
-- [オープンソースコントリビューターをスポンサーする](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)
+- [{% data variables.product.prodname_sponsors %} について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index 86540a4445..d01fab287d 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,26 +16,11 @@ Enterprise アカウントの {% data variables.product.prodname_GH_advanced_sec
 
 ### {% data variables.product.prodname_GH_advanced_security %} のコミッター番号について
 
-{% data variables.product.prodname_dotcom_the_website %} の {% data variables.product.prodname_GH_advanced_security %} の 2 つのコミッター数を記録して表示します。
-
-- **コミッター**は、Organization 内の少なくとも 1 つのプライベートリポジトリにコントリビュートし、ライセンスのシートを使用するコミッターの数です。 つまり、Organization のメンバー、外部のコラボレータでもあるか、Enterprise 内の Organization に参加するための保留中の招待状を持っています。
-- **このリポジトリ/Organization に固有**は、このリポジトリまたはこの Organization のリポジトリにのみコントリビュートしたコミッターの数です。 この数値は、そのリポジトリまたは Organization の {% data variables.product.prodname_GH_advanced_security %} を無効にすることで解放できるライセンスシートの数を示しています。
-
-一意のコミッターがない場合、これは、すべてのアクティブなコミッターが {% data variables.product.prodname_GH_advanced_security %} を使用する他のリポジトリまたは Organization にもコントリビュートしていることを意味します。 そのリポジトリまたは Organization の機能を無効にしても、ライセンスのシートは解放されません。
-
-{% note %}
-
-**注釈:** ライセンスで使用されるシートの総数は、各リポジトリまたは Organization のコミッターまたは一意のコミッターの合計ではありません。 これは、複数のリポジトリや Organization にコントリビュートしている人がいるためです。 使用されたシートの数は、Enterprise アカウント全体で測定され、コントリビュートしているリポジトリや Organization の数に関係なく、各人が 1 回だけカウントされるようにします。
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### {% data variables.product.prodname_GH_advanced_security %} のライセンス利用を管理する
 
-単一のリポジトリまたは Organization 内のすべてのリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にすると、{% data variables.product.company_short %} は、使用する追加のシートの数を示し、確認を求めるプロンプトを表示します。 {% data variables.product.prodname_GH_advanced_security %} へのアクセスを無効にすると、「一意」のコミッターが使用するシートが解放されます。 これによって、ライセンスの使用に関する変更のインパクトを簡単に理解できます。
-
-ライセンス制限を超えている場合、{% data variables.product.prodname_GH_advanced_security %} はすでに有効になっているすべてのリポジトリで引き続き動作します。 ただし、{% data variables.product.prodname_GH_advanced_security %} が新しいリポジトリに対して有効になっている Organization では、リポジトは機能が無効の状態で作成されます。 さらに、既存のリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にするオプションは使用できなくなります。 パブリックリポジトリの可視性をプライベートに変更すると、そのリポジトリの {% data variables.product.prodname_GH_advanced_security %} は無効になります。
-
-一部のリポジトリで {% data variables.product.prodname_GH_advanced_security %} を無効にするか、ライセンスサイズを増やすと、一部のシートを解放した直後に {% data variables.product.prodname_GH_advanced_security %} を有効にするオプションが通常どおり動作します。
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
 Enterprise アカウントが所有する Organization による {% data variables.product.prodname_advanced_security %} の使用を許可または禁止するポリシーを適用できます。 詳しい情報については、「[Enterprise アカウントに {% data variables.product.prodname_advanced_security %} のポリシーを適用する](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)」を参照してください。
 
@@ -43,9 +28,4 @@ Enterprise アカウントが所有する Organization による {% data variabl
 
 ### {% data variables.product.prodname_GH_advanced_security %} ライセンスを最大限に活用する
 
-{% data variables.product.prodname_GH_advanced_security %} の優先順位を付けるリポジトリと Organization を決定するときは、それらを確認して次のことを特定する必要があります。
-
-- 会社の成功にとって最も重要なコードベース。 これらは、脆弱なコード、ハードコードされたシークレット、または脆弱な依存関係の導入が会社に最大の影響を与えるプロジェクトです。
-- コミット頻度が最も高いコードベース。 これらは最も積極的に開発されたプロジェクトであるため、セキュリティの問題が発生するリスクが高くなります。
-
-これらの Organization またはリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にした場合、一意のコミッターを追加したり、ライセンスのシートを使い切ったりせずに、追加できる他のコードベースを評価する必要があります。 この後、次に重要でビジーなコードベースを確認します。 ライセンスのシート数を増やす場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index d1402352cb..db77d32b08 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ topics:
 ### 個人アカウントの領収書への情報の追加
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### Organization の領収書への情報の追加
@@ -40,9 +40,9 @@ topics:
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index 2f6ebeb357..e301929243 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ topics:
 ### 個人アカウントの支払い方法を更新する
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### Organization の支払い方法を更新する
@@ -38,9 +39,10 @@ topics:
 
 Organization がアメリカ外にあるか、{% data variables.product.product_name %} への支払いに会社の当座預金口座を使っているなら、支払い方法として PayPal が役立つかもしれません
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index f1c56609b7..bf95db0581 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ topics:
 ### 個人アカウントのアプリケーションをキャンセルする
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### 個人アカウントのアプリケーション無料トライアルをキャンセルする
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index 0a8474c3ec..4fab8f0a94 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ topics:
 ### 個人アカウントの支払いサイクル期間の変更
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ topics:
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ topics:
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. [Billing overview] で、[**Change plan**] をクリックします。 ![[Billing overview] の [Change plan] ボタン](/assets/images/help/billing/billing_overview_change_plan.png)
 5. ページの右上で [**Switch to monthly billing**] または [**Switch to yearly billing**] をクリックします。 ![支払い情報セクション](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index 82bf13b892..c3e9114a92 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ topics:
 
 ### ステップ 3: Organization を年次支払いプランへ アップグレードする
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (次のステップで、Organizationにシートを追加できます。)
 6. Organization の支払いを年次で行うには、[Upgrade summary] の下で [**Pay yearly**] を選択します。 ![年次の支払いのラジオボタン](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. [Pay with] の下に、クレジットカード情報を入力します。 ![クレジットカード情報入力用フォーム](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. [**Update credit card**] をクリックします。
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### ステップ 4: Organization の有料シート数をアップグレードする
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index cd691bff06..96e16c99af 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -16,8 +16,7 @@ topics:
 ### 個人アカウントのストレージと帯域幅をダウングレード
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
@@ -25,10 +24,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 0361af9dc4..22fe9cb709 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ topics:
 ### 個人アカウントのアプリケーションをダウングレードする
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index 3324a3be9c..0e5a350197 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ topics:
 ユーザアカウントを{% data variables.product.prodname_pro %}から{% data variables.product.prodname_free_user %}にダウングレードした場合、プライベートリポジトリでの高度なコードレビューツールにはアクセスできなくなります。 {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. ** Edit（編集）**ドロップダウンを使い、**Downgrade to Free{Freeへのダウングレード）**をクリックしてください。 ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
 5. 次回の請求日にユーザアカウントがアクセスできなくなる機能に関する情報を読み、[**I understand. Continue with downgrade**] をクリックします。 ![[Continue with downgrade] ボタン](/assets/images/help/billing/continue-with-downgrade.png)
 
 プライベートリポジトリに {% data variables.product.prodname_pages %} サイトを公開し、カスタムドメインを追加した場合、ドメイン乗っ取りのリスクを回避するため、{% data variables.product.prodname_pro %} から {% data variables.product.prodname_free_user %} にダウングレードする前に DNS レコードを削除または更新します。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。
@@ -45,12 +44,10 @@ Organizationを{% data variables.product.prodname_team %}から{% data variables
 
 Organizationを{% data variables.product.prodname_ghe_cloud %}から{% data variables.product.prodname_team %}または{% data variables.product.prodname_free_team %}にダウングレードした場合、そのアカウントは高度なセキュリティ、コンプライアンス、およびデプロイメントコントロールにアクセスできなくなります。 {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. [**Edit**] ドロップダウンで、必要なダウングレード オプションをクリックします。 ![[Downgrade] ボタン](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![[Downgrade] ボタン](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### 従来のリポジトリ単位の支払いを使用しているOrganizationのプランをダウングレードする
@@ -59,10 +56,9 @@ Organizationを{% data variables.product.prodname_ghe_cloud %}から{% data vari
 
 {% data reusables.dotcom_billing.switch-legacy-billing %}詳しい情報については、「[Organization をリポジトリごとからユーザごとに切り替える](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. [Subscriptions] の下にある [Edit] ドロップダウンメニューから [**Edit plan**] をクリックします。 ![[Edit Plan] ドロップダウン](/assets/images/help/billing/edit-plan-dropdown.png)
 1. [Billing/Plans] で、変更する必要があるプランの横にある [**Downgrade**] をクリックします。 ![[Downgrade] ボタン](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. アカウントをダウングレードする理由を入力し、[**Downgrade plan**] をクリックします。 ![ダウングレードの理由を入力するテキストボックスと [Downgrade] ボタン](/assets/images/help/billing/downgrade-plan-button.png)
@@ -74,12 +70,10 @@ Organization が使用する有料シート数を減らすには、Organization
 - [Organizatin のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator)
 - [Organizationのリポジトリへの個人のアクセスの管理](/articles/managing-an-individual-s-access-to-an-organization-repository)
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. ** Edit（編集）**ドロップダウンを使い、**Remove seats（シートの削除）**をクリックしてください。 ![[Remove Seats] ドロップダウン](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![[Remove Seats] ドロップダウン](/assets/images/help/billing/remove-seats-dropdown.png)
 1. [Remove seats] の下でダウングレードするシート数を選択します。 ![[Remove Seats] オプション](/assets/images/help/billing/remove-seats-amount.png)
 1. 次回請求日の新しい支払いに関する情報を確認し、[**Remove seats**] をクリックします。 ![[Remove Seats] ボタン](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index 36981b38f0..bc9cc3b78d 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ $0 以外の利用上限を設定すると、直ちに現在の支払い期間
 自身のユーザアカウントに対する {% data variables.product.prodname_actions %} の利用上限は、誰でも管理できます。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ $0 以外の利用上限を設定すると、直ちに現在の支払い期間
 
 Organization の {% data variables.product.prodname_actions %} については、Organizationのオーナーと支払いマネージャーが利用上限を管理できます。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise アカウントの {% data variables.product.prodname_actions %} の
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. [
-[{% data variables.product.prodname_actions %} and Packages monthly usage] で、[**Cost management**] をクリックします。
-  ![コスト管理タブ](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index fe96e8d828..742b5d4408 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ $0 以外の利用上限を設定すると、直ちに現在の支払い期間
 自身のユーザアカウントに対する {% data variables.product.prodname_registry %} の利用上限は、誰でも管理できます。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ $0 以外の利用上限を設定すると、直ちに現在の支払い期間
 
 Organization の {% data variables.product.prodname_registry %} については、Organizationのオーナーと支払いマネージャーが利用上限を管理できます。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise アカウントの {% data variables.product.prodname_registry %} に
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. [
-[{% data variables.product.prodname_actions %} and Packages monthly usage] で、[**Cost management**] をクリックします。
-  ![コスト管理タブ](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index efb266f472..6e1b743f6c 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ topics:
 ### 個人アカウントの支払い方法を削除する
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index 0447643db0..ed7a8b27e5 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### Organization のクレジットカードを更新する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. セキュアなフォームで新しいクレジットカード情報を入力します。 ![クレジットカード情報フォーム](/assets/images/help/settings/creditcard-billing-form.png)
-1. [**Update credit card**] または [**Save credit card**] をクリックします。
+1. Under "Payment method", click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index 21396ce15f..9756e15ee3 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. [**Billing email**] (支払い請求先メールアドレス) の下に、有効なメールアドレスを入力します。 このメールアドレスは、Organization アカウント専用である必要はありません。 ![支払い請求先メールアドレステキストボックス](/assets/images/help/settings/org-billing-email.png)
 5. 変更を確定するには [**Update profile**] をクリックします。 ![[Update profile] ボタン](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ topics:
 #### 支払い通知の受信者を追加する
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. [Billing management] で、[Email recipients] の右の [**Add**] をクリックします。 ![受信者を追加](/assets/images/help/billing/billing-add-email-recipient.png)
 1. 受信者のメールアドレスを入力し、[**Add**] をクリックします。 ![受信者追加のモーダル](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ topics:
 第1受信者として必ずアドレスを 1 つは指定する必要があります。 第 1 受信者に指定したアドレスは、別の第 1 受信者を選定するまで、削除できません。
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. [Billing management] で、第 1 受信者に設定したいメールアドレスを探します。
 1. 見つかったメールアドレスの右にある [Edit] ドロップダウンメニューで、[**Mark as primary**] をクリックします。 ![第 1 受信者としてマーク](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### 支払い通知の受信者を削除する
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. [Email recipients] で、削除したいメールアドレスを探します。
 1. そのユーザのエントリで [**Edit**] をクリックします。 ![受信者を編集する](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. そのメールアドレスの右にある [Edit] ドロップダウンメニューで、[Remove] をクリックします。 ![受信者を削除する](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![受信者を削除する](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. 確認ダイアログを確かめてから、[**Remove**] をクリックします。
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index 215ecedb6a..26827882b0 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### 個人アカウント用に追加のストレージと帯域幅を購入する
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index 65617ef10a..5d03674a25 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,11 +22,9 @@ topics:
 
 ### Organization の有料シート数をアップグレードする
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -35,10 +33,8 @@ topics:
 
 ### Organization の有料シート数を無料にダウングレードする
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index c5ce6fcdde..8c5d64965b 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ topics:
 ### 個人アカウントのアプリケーションをアップグレードする
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index 22519c6d0e..cd3f446853 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 個人アカウントを {% data variables.product.prodname_free_user %} から {% data variables.product.prodname_pro %} にアップグレードして、プライベートリポジトリの高度なコードレビューツールを手に入れることができます。 {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. [
-{% data variables.product.prodname_free_user %}] の隣で、[**Upgrade**] をクリックします。
-  ![アップグレードボタン](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![アップグレードボタン](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ Organization を {% data variables.product.prodname_free_team %} から {% data
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ Organization を {% data variables.product.prodname_ghe_cloud %} にアップグ
 
 {% data variables.product.prodname_team %} Organization のプライベートリポジトリにアクセスできるユーザを追加したい場合、いつでもシートを買い足すことができます。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ Organization を {% data variables.product.prodname_ghe_cloud %} にアップグ
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. プラン名の右にある [**Edit**] ドロップダウンメニューで、[**Edit plan**] を選択します。 ![[Edit] ドロップダウンメニュー](/assets/images/help/billing/per-user-upgrade-button.png)
 6. [Advanced tools for teams] の右にある [**Upgrade now**] をクリックします。 ![[Upgrade now] ボタン](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index 14b62a9fad..1299961dd0 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ topics:
 ### 個人アカウントのプランに対する保留中の変更の表示と管理
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### Organization のプランに対する保留中の変更の表示と管理
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index 9c08c202d0..d75f60b20d 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### 個人アカウントのストレージと帯域幅の使用状況を表示する
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Organization のストレージと帯域幅の使用状況を表示する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### 参考リンク
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index 7f28b9f217..adbf181843 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ topics:
 自身のユーザアカウントの {% data variables.product.prodname_actions %} の使用状況は、誰でも表示できます。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ topics:
 
 Organization については、Organization のオーナーと支払いマネージャーが {% data variables.product.prodname_actions %} の使用状況を管理できます。 Enterprise アカウントで管理されている Organization の場合、Organization の支払いページで {% data variables.product.prodname_actions %} の使用状況を確認できるのは Organization のオーナーだけです。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index af0561fe47..5c56cf5be8 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,7 +1,7 @@
 ---
 title: Viewing your GitHub Advanced Security usage
 intro: 'You can view and manage usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
-permissions: 'Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index ddf3f364d1..c52c86c28a 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 自身のユーザアカウントの {% data variables.product.prodname_registry %} の使用状況は、誰でも表示できます。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ topics:
 
 Organization については、Organization のオーナーと支払いマネージャーが {% data variables.product.prodname_registry %} の使用状況を管理できます。 Enterprise アカウントで管理されている Organization の場合、Organization の支払いページで {% data variables.product.prodname_registry %} の使用状況を確認できるのは Organization のオーナーだけです。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index 94ca886af0..5218ab53a3 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### 個人アカウントの領収書を表示する
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index 0bd9ed3f8c..e54d6630dc 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### 個人アカウントの次の請求日を確認する
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Organization の次の請求日を確認する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### 参考リンク
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md
index 535263cbcd..137858a5cc 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts.md
@@ -18,15 +18,15 @@ topics:
 Enterprise アカウントでは、複数の {% data variables.product.prodname_dotcom %} Organization と {% data variables.product.prodname_ghe_server %} インスタンスを管理できます。 Enterprise アカウントは、{% data variables.product.prodname_dotcom %} 上の Organization や個人アカウントのようにハンドルを持たなければなりません。 Enterprise 管理者は、以下のような設定やプリファレンスを管理できます:
 
 - メンバーのアクセスと管理 (Organization のメンバー、外部コラボレーター)
-- Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs{% if currentVersion == "free-pro-team@latest" or ver_gt "enterprise-server@3.0" %}, {% data variables.product.prodname_GH_advanced_security %} usage{% endif %})
+- 支払いと使用状況（{% data variables.product.prodname_ghe_server %} インスタンス、ユーザライセンス、{% data variables.large_files.product_name_short %} パック{% if currentVersion == "free-pro-team@latest" or ver_gt "enterprise-server@3.0" %}、{% data variables.product.prodname_GH_advanced_security %} の使用状況{% endif %}）
 - セキュリティ (シングルサインオン、2 要素認証)
 - {% data variables.contact.enterprise_support %} とのリクエストおよび Support Bundle の共有
 
-{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." For more information about managing your {% data variables.product.prodname_ghe_server %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+{% data reusables.enterprise-accounts.enterprise-accounts-billing %}{% data variables.product.prodname_ghe_cloud %} サブスクリプションの管理に関する詳しい情報については、「[Enterprise アカウントのサブスクリプションと利用状況の表示](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)」を参照してください。 {% data variables.product.prodname_ghe_server %} の支払い設定の管理に関する詳しい情報については、「[Enterprise の支払いの管理](/admin/overview/managing-billing-for-your-enterprise)」を参照してください。
 
 {% data variables.product.prodname_ghe_cloud %} と {% data variables.product.prodname_ghe_server %} の違いについては、「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」を参照してください。 {% data variables.product.prodname_enterprise %} にアップグレードする、または Enterprise アカウントを使い始める場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。
 
-For more information about member access and management, see "{% if currentVersion == "free-pro-team@latest" %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}."
+メンバーのアクセスと管理の詳細については、「{% if currentVersion == "free-pro-team@latest" %}[Enterprise 内のユーザを管理する](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif currentVersion == "enterprise-ae@latest" or enterpriseServerVersions contains currentVersion %}[ユーザ、Organization、リポジトリを管理する](/admin/user-management)」を参照してください{% endif %}。
 
 GraphQL APIを利用したEnterpriseアカウントの管理に関する詳しい情報については、「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md
index 1ccf9bebfc..9fe0b8c335 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
-title: About identity and access management for your enterprise account
-intro: 'You can centrally manage access to your enterprise''s resources, organization membership, and team membership using your identity provider (IdP).'
+title: Enterprise アカウントのアイデンティおよびアクセス管理について
+intro: アイデンティティプロバイダ (IdP) を使用して、Enterprise のリソース、Organization のメンバーシップ、および Team のメンバーシップへのアクセスを一元管理できます。
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   free-pro-team: '*'
@@ -8,26 +8,26 @@ topics:
   - Enterprise
 ---
 
-### About identity and access management for your enterprise account
+### Enterprise アカウントのアイデンティおよびアクセス管理について
 
-{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)."
+{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} 詳しい情報については、「[Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)」を参照してください。
 
-After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features.
+SAML SSO を有効にした後、使用する IdP によっては、追加のアイデンティおよびアクセス管理機能を有効にできる場合があります。
 
-{% data reusables.saml.about-user-provisioning-enterprise-account %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)."
+{% data reusables.saml.about-user-provisioning-enterprise-account %} 詳しい情報については、「[Enterprise アカウント内の Organization のユーザプロビジョニングについて](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)」を参照してください。
 
-If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)."
+IdP として Azure AD を使用している場合は、Team 同期を使用して、各 Organization 内の Team メンバーシップを管理できます。 {% data reusables.identity-and-permissions.about-team-sync %} 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)」を参照してください。
 
-### Supported IdPs
+### サポートされている IdP
 
-We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. 詳しい情報については、OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) を参照してください。
+以下の IdP はテスト済みで公式にサポートされています。 SAML SSO の場合、SAML 2.0 標準を実装するすべてのアイデンティティプロバイダに対して限定的なサポートが提供されています。 詳しい情報については、OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) を参照してください。
 
-| IdP                                   |                              SAML                              |                                                                                           User provisioning                                                                                            |                           Team の同期                            |
-| ------------------------------------- |:--------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:|
-| Active Directory フェデレーションサービス (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" %} [<sup>Beta</sup>](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) |                                                               |
-| 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" %}  |                                                                                                                                                                                                        |                                                               |
+| IdP                                   |                              SAML                              |                                                                                              ユーザプロビジョニング                                                                                              |                           Team の同期                            |
+| ------------------------------------- |:--------------------------------------------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:|
+| Active Directory フェデレーションサービス (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" %} [<sup>ベータ</sup>](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account) |                                                               |
+| 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/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md
index 4a2d86e265..f2342d2484 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
-title: About user provisioning for organizations in your enterprise account
-intro: You can manage organization membership in an enterprise account directly from an identity provider (IdP).
+title: Enterprise アカウント内の Organization のユーザプロビジョニングについて
+intro: Enterprise アカウントの Organization のメンバーシップを直接アイデンティティプロバイダ (IdP) から管理できます。
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   free-pro-team: '*'
@@ -14,7 +14,7 @@ topics:
 
 {% data reusables.scim.enterprise-account-scim %} オプションで、SAML プロビジョニングを有効にして、別々にデプロビジョニングすることもできます。
 
-If you configure SCIM for the {% data variables.product.product_name %} application in your IdP, each time you make changes to group membership in your IdP, your IdP will make a SCIM call to {% data variables.product.prodname_dotcom %} to update the corresponding organization's membership. SAML プロビジョニングを有効にすると、Enterprise アカウントの SAML 設定で保護されているリソースに Enterprise のメンバーがアクセスするたびに、その SAML アサーションによってプロビジョニングがトリガーされすま。
+IdP で {% data variables.product.product_name %} アプリケーションの SCIM を設定すると、IdP でグループのメンバーシップに変更を加えるたびに IdP が {% data variables.product.prodname_dotcom %} に SCIM 呼び出しを行い、対応する Organization のメンバーシップを更新します。 SAML プロビジョニングを有効にすると、Enterprise アカウントの SAML 設定で保護されているリソースに Enterprise のメンバーがアクセスするたびに、その SAML アサーションによってプロビジョニングがトリガーされすま。
 
 SCIM 呼び出しまたは SAML アサーションのたびに、{% data variables.product.product_name %} はユーザが所属する IdP グループをチェックし、以下の操作を実行します。
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md
index ef12a5af16..1fa3e75c67 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md
@@ -13,7 +13,7 @@ topics:
 
 Enterprise のオーナーは、Enterprise アカウント内に新しい Organization を作成できます。
 
-Organization を Enterprise アカウントに追加するには、 Enterprise アカウント設定から Organization を作成する必要があります。 If you want to transfer an existing organization to your enterprise account, contact your {% data variables.product.prodname_dotcom %} sales account representative.
+Organization を Enterprise アカウントに追加するには、 Enterprise アカウント設定から Organization を作成する必要があります。 既存の Organization を Enterprise アカウントに移行する場合は、{% data variables.product.prodname_dotcom %} セールス顧客担当にお問い合わせください。
 
 ### Enterprise アカウント内で Organization を作成する
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md
index 39b05ff309..99f17221b3 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring identity and access management for your enterprise account
-intro: 'You can manage SAML single sign-on, user provisioning, and team synchronization for your enterprise.'
+title: Enterprise アカウントのアイデンティおよびアクセス管理を設定する
+intro: Enterprise の SAML シングルサインオン、ユーザプロビジョニング、Team 同期を管理できます。
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 mapTopic: true
 versions:
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index ea9b3d4b19..a2df9e2fc2 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting an Azure subscription to your enterprise
-intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.'
+title: Azure サブスクリプションを Enterprise に接続する
+intro: 'Microsoft Enterprise Agreement を使用して、Enterprise に含まれている金額を超える {% data variables.product.prodname_actions %} および {% data variables.product.prodname_registry %} の使用を有効化して支払うことができます。'
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
@@ -8,33 +8,33 @@ versions:
   free-pro-team: '*'
 ---
 
-### About Azure subscriptions and {% data variables.product.product_name %}
+### Azure サブスクリプションと {% data variables.product.product_name %}
 
-{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 詳しい情報については、「[{% data variables.product.prodname_actions %} の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)」および「[{% data variables.product.prodname_registry %} の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)」を参照してください。
 
-After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)."
+Azure サブスクリプションに接続した後、利用上限を管理することもできます。 アカウントの利用上限の管理と変更については、「[{% data variables.product.prodname_registry %} の利用上限の管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)」および「[{% data variables.product.prodname_actions %} の利用上限の管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)」を参照してください。
 
-### Connecting your Azure subscription to your enterprise account
+### Azure サブスクリプションを Enterprise アカウントに接続する
 
-To connect your Azure subscription, you must have owner permissions to the subscription.
+Azure サブスクリプションに接続するには、サブスクリプションに対するオーナーのアクセス許可が必要です。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Under "Payment Information", click **Add Azure Subscription**.
-1. To sign in to your Microsoft account, follow the prompts.
-1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**.
-1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise.
-1. Click **Connect**.
+1. [Payment Information] で、[**Add Azure Subscription**] をクリックします。
+1. 画面の指示に従って Microsoft アカウントにサインインします。
+1. [Permissions requested] という画面表示を確認します。 規約に同意する場合は、[**Accept**] をクリックします。
+1. [Select a subscription] で、Enterprise に接続する Azure サブスクリプション ID を選択します。
+1. [**Connect**] をクリックします。
 
-### Disconnecting your Azure subscription from your enterprise account
+### Enterprise アカウントから Azure サブスクリプションを切断する
 
-After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan.
+Azure サブスクリプションを Enterprise アカウントから切断すると、プランに含まれている金額以上の使用量を利用できなくなります。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
-1. Review the prompt, then click **Remove**.
+1. [Azure subscription] の下で、切断するサブスクリプション ID の右側にある [**{% octicon "trash" aria-label="The trash icon" %}**] をクリックします。
+1. 画面表示を確かめてから、[**Remove**] をクリックします。
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md
index 06c97a3578..b68f113d27 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
 title: Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする
-intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enabling SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.'
+intro: Enterprise アカウントが所有するすべての Organization で SAML シングルサインオン (SSO) と IdP を介した集中認証を有効にすることで、リポジトリ、Issue、プルリクエストなどのリソースへのアクセスを制御および保護できます。
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can enable SAML single sign-on for organizations in an enterprise account.
 versions:
@@ -9,7 +9,7 @@ topics:
   - Enterprise
 ---
 
-### About SAML single sign-on for enterprise accounts
+### Enterprise アカウントの SAML シングルサインオンについて
 
 {% data reusables.saml.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。
 
@@ -19,9 +19,9 @@ topics:
 
 {% data reusables.saml.saml-supported-idps %}
 
-{% data reusables.scim.enterprise-account-scim %} プライベートベータに参加していない場合、Enterprise アカウント に対して SCIM はサポートされません。 For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)."
+{% data reusables.scim.enterprise-account-scim %} プライベートベータに参加していない場合、Enterprise アカウント に対して SCIM はサポートされません。 詳しい情報については、「[Enterprise アカウント内の Organization のユーザプロビジョニングについて](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)」を参照してください。
 
-### Enabling SAML single-sign on for organizations in your enterprise account
+### Enterprise アカウントで Organization の SAML シングルサインオンを有効にする
 
 {% note %}
 
@@ -29,7 +29,7 @@ topics:
 
 {% endnote %}
 
-For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)."
+Okta を使用して SAML を有効にする方法については、「[Okta を使用して Enterprise アカウントの SAML シングルサインオンおよび SCIM を設定する](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -37,8 +37,8 @@ For more detailed information about how to enable SAML using Okta, see "[Configu
 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 5. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択します。 ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
 6. **Sign on URL**フィールドに、使用する IdP のシングルサインオンのリクエストのための HTTPS エンドポイントを入力してください。 この値は Idp の設定で使用できます。 ![メンバーがサインインする際にリダイレクトされる URL のフィールド](/assets/images/help/saml/saml_sign_on_url_business.png)
-7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. ![SAMl 発行者の名前のフィールド](/assets/images/help/saml/saml_issuer.png)
+7. 必要に応じて、[**Issuer**] フィールドに SAML 発行者の URL を入力して、送信されたメッセージの信頼性を確認します。 ![SAMl 発行者の名前のフィールド](/assets/images/help/saml/saml_issuer.png)
 8. [**Public Certificate**] で、証明書を貼り付けて SAML の応答を認証します。 ![アイデンティティプロバイダからの公開の証明書のフィールド](/assets/images/help/saml/saml_public_certificate.png)
-9. SAML 発行者からのリクエストの完全性を確認するには、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。 Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png)
+9. SAML 発行者からのリクエストの完全性を確認するには、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。 次に、[Signature Method] および [Digest Method] ドロップダウンで、SAML 発行者が使用するハッシュアルゴリズムを選択します。 ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png)
 10. Enterprise で SAML SSO を有効化する前に、[**Test SAML configuration**] をクリックして、入力した情報が正しいか確認します。 ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_test.png)
 11. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index cede751462..c1029b657f 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -29,14 +29,14 @@ Enterprise のワークフローをすべて無効にすることも、Organizat
 {% data reusables.actions.enterprise-actions-permissions %}
 1. [**Save**] をクリックします。
 
-### Allowing specific actions to run
+### 特定のアクションの実行を許可する
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
-1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
+1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![許可リストにアクションを追加する](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
 
 ### プライベートリポジトリのフォークのワークフローを有効にする
 
@@ -48,3 +48,19 @@ Enterprise のワークフローをすべて無効にすることも、Organizat
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### Setting the permissions of the `GITHUB_TOKEN` for your enterprise
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. **Save（保存）**をクリックして、設定を適用してください。
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md
index 898fb114bb..858f0429ed 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing policies for Advanced Security in your enterprise account
-intro: 'Enterprise owners can enforce policies to manage {% data variables.product.prodname_GH_advanced_security %} features for organizations owned by an enterprise account.'
+title: Enterprise アカウントでの Advanced Security のポリシーを適用する
+intro: 'Enterprise のオーナーは、Enterprise アカウントが所有する Organization の {% data variables.product.prodname_GH_advanced_security %} 機能を管理するためのポリシーを適用できます。'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
   free-pro-team: '*'
@@ -10,7 +10,7 @@ versions:
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
-### Enforcing a policy for {% data variables.product.prodname_advanced_security %} features
+### {% data variables.product.prodname_advanced_security %} 機能のポリシーを施行する
 
 {% data reusables.advanced-security.about-ghas-organization-policy %}
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md
index 4265331cb5..62a3aeb0cc 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account.md
@@ -51,7 +51,7 @@ topics:
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 3. [**Repository policies**] タブの [Repository invitations] で、設定変更についての情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository invitations", use the drop-down menu and choose a policy. ![外部コラボレーター招待ポリシーオプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
+4. [Repository invitations] で、ドロップダウンメニューを使用してポリシーを選択します。 ![外部コラボレーター招待ポリシーオプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
 
 ### リポジトリの表示の変更に関するポリシーを施行する
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md
index d4480bfac7..78ae0f8c7f 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account.md
@@ -117,4 +117,4 @@ CAを削除すると、元に戻すことはできません。 同じCAを使用
 
 ### 参考リンク
 
-- "[Configuring identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)"
+- 「[Enterprise アカウントのアイデンティおよびアクセス管理を設定する](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account)」
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md
index ad64e15f70..aec1ed04fe 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up and managing your enterprise
-shortTitle: Your enterprise
+title: Enterprise の設定と管理
+shortTitle: お使いの Enterprise
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md
index d041a0eed4..60fcf7233d 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Inviting people to manage your enterprise
+title: Enterprise を管理するようユーザを招待する
 intro: Enterprise アカウントで Enterprise オーナーまたは支払いマネージャーになるように人を招待することができます。 Enterprise アカウントにアクセスする必要がなくなった Enterprise オーナーまたは支払いマネージャーを削除することもできます。
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
@@ -15,7 +15,7 @@ topics:
 
 ### Enterprise アカウントを管理するようユーザを招待することについて
 
-{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise).
+{% data reusables.enterprise-accounts.enterprise-administrators %}詳しい情報については、「[Enterprise のロール](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)」を参照してください。
 
 {% tip %}
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md
index aad1b20450..369c0f9450 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise.md
@@ -17,9 +17,9 @@ topics:
 
 {% data variables.product.prodname_vss_ghe %} は、サブスクライバーが {% data variables.product.prodname_enterprise %} と {% data variables.product.prodname_vs %} の両方を使用できるように組み合わせて販売されている Microsoft の製品です。 {% data variables.product.prodname_vss_ghe %} は、Microsoft Enterprise Agreement の条件に基づいて Microsoft から入手できます。 詳しい情報については、「{% data variables.product.prodname_vs %} Web サイトの [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/)」を参照してください。
 
-After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise account with a user account on {% data variables.product.prodname_dotcom_the_website %}. If the email address for the user account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}.
+{% data variables.product.prodname_vss_ghe %} のライセンスをサブスクライバーに割り当てた後、サブスクライバーは、Enterprise アカウントの Organization に {% data variables.product.prodname_dotcom_the_website %} のユーザアカウントを使用して参加することにより、ライセンスの {% data variables.product.prodname_enterprise %} 部分を使用します。 {% data variables.product.prodname_dotcom_the_website %} の Enterprise メンバーのユーザアカウントのメールアドレスが {% data variables.product.prodname_vs %} アカウントのサブスクライバーのユーザプライマリ名 (UPN) と一致する場合、{% data variables.product.prodname_vs %} サブスクライバーは自動的に {% data variables.product.prodname_vss_ghe %} のライセンスを 1 つ消費します。
 
-The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the user account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the user account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber.
+{% data variables.product.prodname_dotcom %} での Enterprise のライセンスの合計数は、標準の {% data variables.product.prodname_enterprise %} ライセンスと {% data variables.product.prodname_dotcom %} へのアクセスを含む {% data variables.product.prodname_vs %} サブスクリプションライセンス数の合計です。 Enterprise メンバーのユーザーアカウントが {% data variables.product.prodname_vs %} サブスクライバーのメールアドレスと一致しない場合、ユーザアカウントが消費するライセンスは {% data variables.product.prodname_vs %} サブスクライバーには使用できません。
 
 {% data variables.product.prodname_enterprise %} の詳細は、「[{% data variables.product.company_short %} の製品](/github/getting-started-with-github/githubs-products#github-enterprise)」を参照してください。 {% data variables.product.prodname_dotcom_the_website %} のアカウントの詳細については、「[{% data variables.product.prodname_dotcom %} アカウントのタイプ](/github/getting-started-with-github/types-of-github-accounts)」を参照してください。
 
@@ -33,19 +33,19 @@ The total quantity of your licenses for your enterprise on {% data variables.pro
 
 ### サブスクライバーを招待して {% data variables.product.prodname_enterprise %} を使用する
 
-To use the {% data variables.product.prodname_enterprise %} portion of the license, the subscriber's user account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}.
+ライセンスの {% data variables.product.prodname_enterprise %} 部分を使用するには、{% data variables.product.prodname_dotcom_the_website %} のサブスクライバーのユーザアカウントが、{% data variables.product.prodname_dotcom_the_website %} の Enterprise が所有する Organization のメンバーであるかメンバーになる必要があります。
 
-Organization owners can invite new members to an organization by email address. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account.
+Organization のオーナーは、メールアドレスで新しいメンバーを Organization に招待できます。 サブスクライバーは、{% data variables.product.prodname_dotcom_the_website %} の既存のユーザ アカウントで招待を受け入れるか、新しいアカウントを作成できます。
 
-While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license.
+必須ではありませんが、Organization のオーナーは、{% data variables.product.prodname_vs %} サブスクライバーのユーザプライマリ名 (UPN) に使用されているのと同じメールアドレスに招待状を送信することをお勧めします。 {% data variables.product.product_name %} のメールアドレスがサブスクライバーの UPN と一致する場合、Organization の別のメンバーがサブスクライバーのライセンスをリクエストしないようにすることができます。
 
-For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)," "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)," and "[Managing email preferences](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)."
+詳しい情報については、「[Organization にユーザーを招待する](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)」、「[{% data variables.product.prodname_dotcom %} へのサインアップ](/github/getting-started-with-github/signing-up-for-github)」および「[メール プリファレンスの管理](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)」を参照してください。
 
 ### {% data variables.product.prodname_enterprise %} ライセンスを表示する
 
 {% data variables.product.prodname_vss_admin_portal_with_url %} で {% data variables.product.prodname_vss_ghe %} のライセンスを割り当てた後、Enterprise アカウントで使用可能な {% data variables.product.prodname_enterprise %} ライセンスの数を表示できます。 詳細は「[Enterprise アカウントのプランおよび利用状況を見る示](/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account)」を参照してください。
 
-{% data variables.product.prodname_vss_admin_portal_with_url %} のサブスクライバーへの保留中の {% data variables.product.prodname_enterprise %} 招待を確認することもできます。 保留中の招待リストには、Enterprise アカウントの少なくとも 1 つの Organization のメンバーではないサブスクライバーが含まれます。 For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)."
+{% data variables.product.prodname_vss_admin_portal_with_url %} のサブスクライバーへの保留中の {% data variables.product.prodname_enterprise %} 招待を確認することもできます。 保留中の招待リストには、Enterprise アカウントの少なくとも 1 つの Organization のメンバーではないサブスクライバーが含まれます。 詳しい情報については、「[Enterprise の人を表示する](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)」を参照してください。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md
index 040e48d28a..ad3c58fb81 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
 title: Enterprise アカウントで Organization の Team 同期を管理する
-intro: 'You can enable team synchronization between an identity provider (IdP) and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.'
+intro: 'アイデンティティプロバイダ (IdP) と {% data variables.product.product_name %} の間のチーム同期を有効にして、Enterprise アカウントが所有する Organization が IdP グループを介してチームメンバーシップを管理できるようにすることができます。'
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage team synchronization for an enterprise account.
 versions:
@@ -9,9 +9,9 @@ topics:
   - Enterprise
 ---
 
-### About team synchronization for enterprise accounts
+### Enterprise アカウントのチーム同期について
 
-If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups.
+Azure AD を IdP として使用する場合は、Enterprise アカウントのチーム同期を有効にして、Organization のオーナーとチームメンテナが、Enterprise アカウントが所有する Organization のチームを IdP グループと同期できるようにすることができます。
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
@@ -39,5 +39,5 @@ SAML SSO とサポートされる IdP を使用して Enterprise アカウント
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
 {% data reusables.identity-and-permissions.team-sync-confirm %}
-7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**. ![特定の IdP テナントに対して、Team の同期を有効化するペンディングリクエストと、リクエストを承認またはキャンセルするオプション](/assets/images/help/teams/approve-team-synchronization.png)
+7. Enterprise アカウントに接続する IdP のテナント詳細を確認してから、[**Approve**] をクリックします。 ![特定の IdP テナントに対して、Team の同期を有効化するペンディングリクエストと、リクエストを承認またはキャンセルするオプション](/assets/images/help/teams/approve-team-synchronization.png)
 8. Team 同期を無効にするには、 [**Disable team synchronization**] をクリックします。 ![Team の同期を無効化する](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md
index 38ec42dfe0..b6263a418b 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account.md
@@ -11,7 +11,7 @@ topics:
   - Enterprise
 ---
 
-ユーザのデプロビジョニングを有効にして Enterprise アカウントの Organization メンバーシップを管理していると、Organization のオーナーがいなくなることもあります。 For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)."
+ユーザのデプロビジョニングを有効にして Enterprise アカウントの Organization メンバーシップを管理していると、Organization のオーナーがいなくなることもあります。 詳しい情報については、「[Enterprise アカウント内の Organization のユーザプロビジョニングについて](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 2. 検索フィールドの右側で、[**X unowned**] をクリックします。 ![オーナーのいない Organization を表示するボタン](/assets/images/help/business-accounts/unowned-organizations-button.png)
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..20c711dcb8
--- /dev/null
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: Enterprise アカウントのメール通知を制限する
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### Enterprise アカウントのメール制限について
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Enterprise アカウントのメール通知を制限する
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md
index 3677c26ba2..1604b63484 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Roles in an enterprise
-intro: 'Everyone in an enterprise is a member of the enterprise. To control access to your enterprise''s settings and data, you can assign different roles to members of your enterprise.'
+title: Enterprise におけるロール
+intro: Enterprise 内の全員が Enterprise のメンバーです。 Enterprise の設定とデータへのアクセスを制御するために、Enterprise のメンバーにさまざまなロールを割り当てることができます。
 product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
@@ -14,47 +14,47 @@ topics:
   - Enterprise
 ---
 
-### About roles in an enterprise
+### Enterprise のロールについて
 
-Everyone in an enterprise is a member of the enterprise. You can also assign administrative roles to members of your enterprise. Each administrator role maps to business functions and provides permissions to do specific tasks within the enterprise.
+Enterprise 内の全員が Enterprise のメンバーです。 Enterprise のメンバーに管理者のロールを割り当てることもできます。 各管理者ロールはビジネス機能にマップされ、Enterprise 内の特定のタスクを行う権限を与えます。
 
 {% data reusables.enterprise-accounts.enterprise-administrators %}
 
-For more information about adding people to your enterprise, see "{% if currentVersion == "free-pro-team@latest" %}[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Authentication](/admin/authentication){% endif %}".
+Enterprise にユーザを追加する方法について詳しくは、「{% if currentVersion == "free-pro-team@latest" %}[Enterprise を管理するために人を招待する](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[認証](/admin/authentication){% endif %}」を参照してください。
 
 ### Enterprise オーナー
 
-Enterprise owners have complete control over the enterprise and can take every action, including:
+Enterprise オーナーは、Enterprise の完全な管理権限を持ち、以下を含むすべての操作を行うことができます。
 - 管理者を管理する
-- {% if currentVersion == "free-pro-team@latest" %}Adding and removing {% elsif currentVersion == "github-ae@latest" %}Managing{% endif %} organizations {% if currentVersion == "free-pro-team@latest" %}to and from {% elsif currentVersion == "github-ae@latest" %} in{% endif %} the enterprise
+- {% if currentVersion == "free-pro-team@latest" %}追加と削除 {% elsif currentVersion == "github-ae@latest" %} Enterprise {% endif %}{% if currentVersion == "free-pro-team@latest" %}内および {% elsif currentVersion == "github-ae@latest" %}Enterprise{% endif %} 内から Organization を管理する
 - Enterprise 設定を管理する
 - Organization にポリシーを強制する
-{% if currentVersion == "free-pro-team@latest" %}- Managing billing settings{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}- 支払い設定を管理する{% endif %}
 
-Enterprise オーナーは、Organization のオーナーになるか、Organization が所有するリポジトリに直接アクセスする権限を与えられない限り、Organization の設定またはコンテンツにはアクセスできません。 Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
+Enterprise オーナーは、Organization のオーナーになるか、Organization が所有するリポジトリに直接アクセスする権限を与えられない限り、Organization の設定またはコンテンツにはアクセスできません。 同様に、Enterprise の Organization のオーナーは、Enterprise のオーナーにならない限り、Enterprise にはアクセスできません。
 
-An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business.
+Enterprise のオーナーは、Enterprise 内の少なくとも 1 つの Organization のオーナーまたはメンバーである場合にのみ、ライセンスを消費できます。 {% if currentVersion == "free-pro-team@latest" %}Enterprise のオーナーは {% data variables.product.prodname_dotcom %} に個人アカウントを持っている必要があります。{% endif %} ベストプラクティスとして、ビジネスへのリスクを軽減するために、Enterprise のオーナーを数人にすることをお勧めします。
 
 ### Enterprise メンバー
 
-Members of organizations owned by your enterprise are also automatically members of the enterprise. Members can collaborate in organizations and may be organization owners, but members cannot access or configure enterprise settings{% if currentVersion == "free-pro-team@latest" %}, including billing settings{% endif %}.
+Enterprise が所有する Organization のメンバーも、自動的に Enterprise のメンバーになります。 メンバーは Organization 内でコラボレートできます。Organization のオーナーになることも可能です。メンバーは支払い設定を含む Enterprise 設定{% if currentVersion == "free-pro-team@latest" %}にアクセスまたは設定することはできません。{% endif %}
 
-People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. 各個人がアクセスできるリソースを確認することができます。 For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)."
+Enterprise 内のユーザは、Enterprise が所有するさまざまな Organization およびそれらの Organization 内のリポジトリへのあらゆるレベルのアクセス権を持つことができます。 各個人がアクセスできるリソースを確認することができます。 詳しい情報については、「[Enterprise の人を表示する](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)」を参照してください。
 
 Organization レベルの権限に関する詳しい情報については「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。
 
-People with outside collaborator access to repositories owned by your organization are also listed in your enterprise's People tab, but are not enterprise members and do not have any access to the enterprise. 外部コラボレーターに関する詳しい情報については「[Organization の権限レベル](/articles/permission-levels-for-an-organization#outside-collaborators)」を参照してください。
+Organization が所有するリポジトリへの外部のコラボレータアクセス権を持つユーザも、Enterprise の [People] タブに一覧表示されますが、Enterprise メンバーではなく、Enterprise へのアクセス権はありません。 外部コラボレーターに関する詳しい情報については「[Organization の権限レベル](/articles/permission-levels-for-an-organization#outside-collaborators)」を参照してください。
 
 {% if currentVersion == "free-pro-team@latest" %}
 
 ### 支払いマネージャー
 
-Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can:
+支払いマネージャーは、Enterprise の支払い設定にのみアクセスできます。 Enterprise の支払いマネージャーは次の操作ができます。
 - ユーザライセンス、{% data variables.large_files.product_name_short %} パック、およびその他の支払い設定の閲覧および管理
 - 支払いマネージャーのリストを閲覧
 - 他の支払いマネージャーの追加または削除
 
-Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. 支払いマネージャーは、{% data variables.product.prodname_dotcom %} 上に個人アカウントを持っていなければなりません。
+支払いマネージャーは、Enterprise 内の少なくとも 1 つの Organization のオーナーまたはメンバーである場合にのみ、ライセンスを消費できます。 支払いマネージャーは、Enterprise の Organization またはリポジトリにアクセスすることはできません。また、Enterprise のオーナーを追加または削除することもできません。 支払いマネージャーは、{% data variables.product.prodname_dotcom %} 上に個人アカウントを持っていなければなりません。
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..752e0a95e8
--- /dev/null
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### ドメイン検証について
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index 106b969856..a9c7c3bc19 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Viewing and managing a user's SAML access to your enterprise
+title: Enterprise へのユーザの SAML アクセスの表示および管理
 intro: Enterprise メンバーのリンクされたアイデンティティ、アクティブなセッション、認可されたクレデンシャルの表示と取り消しが可能です。
 permissions: Enterprise owners can view and manage a member's SAML access to an organization.
 product: '{% data reusables.gated-features.enterprise-accounts %}'
@@ -20,6 +20,15 @@ Enterprise アカウントに対する SAML シングルサインオンを有効
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index ef1534ea90..8461174d86 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -15,11 +15,11 @@ topics:
 
 ### Enterprise アカウントの支払いについて
 
-現時点では、Enterprise アカウントは請求書で支払いを行っている {% data variables.product.prodname_enterprise %} のお客様が利用できます。 Billing for all of the organizations and {% data variables.product.prodname_ghe_server %} instances connected to your enterprise account are aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services (including paid licenses in organizations, {% data variables.large_files.product_name_long %} data packs,{% if currentVersion == "free-pro-team@latest" or ver_gt "enterprise-server@3.0" %} {% data variables.product.prodname_GH_advanced_security %} usage,{% endif %} and subscriptions for {% data variables.product.prodname_marketplace %} apps).
+現時点では、Enterprise アカウントは請求書で支払いを行っている {% data variables.product.prodname_enterprise %} のお客様が利用できます。 Enterprise アカウントに接続されているすべての Organization と {% data variables.product.prodname_ghe_server %} インスタンスの支払いは、すべての有料 {% data variables.product.prodname_dotcom_the_website %} サービス（Organization の有料ライセンス、{% data variables.large_files.product_name_long %} データパック、{% if currentVersion == "free-pro-team@latest" or ver_gt "enterprise-server@3.0" %} {% data variables.product.prodname_GH_advanced_security %} の利用状況、{% endif %}{% data variables.product.prodname_marketplace %} アプリケーションのサブスクリプションを含む）の単一の支払いに集約されます。
 
-{% if currentVersion == "free-pro-team@latest" %}{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。{% endif %}
 
-For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)."
+支払いマネージャーの管理に関する詳細は、「[Enterprise の管理をするよう招待する](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)」を参照してください。
 
 ### Enterprise アカウントのプランおよび利用状況を表示する
 
@@ -30,16 +30,16 @@ For more information about managing billing managers, see "[Inviting people to m
 {% if currentVersion == "free-pro-team@latest" %}ライセンス{% else %}ライセンス{% endif %}で、ライセンスの合計数、消費ライセンス数、およびサブスクリプションの有効期限を表示します。
   {% if currentVersion == "free-pro-team@latest" %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %}
   ![Enterprise 支払い設定のライセンスおよびプラン情報](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %}
-1. Optionally, to view details for license usage or download a
-{% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} file with license details{% if currentVersion == "free-pro-team@latest" %}, to the right of "User Licenses"{% endif %}, click **View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}** or {% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**{% endif %}.{% if currentVersion == "free-pro-team@latest" %}
-  !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}
+1. 必要に応じて、ライセンス使用状況の詳細を表示するか、
+ライセンスの詳細を含む {% if currentVersion == "free-pro-team@latest" %}CSV{% elsif enterpriseServerVersions contains currentVersion %}JSON{% endif %} ファイルをダウンロードするには{% if currentVersion == "free-pro-team@latest" %}、[User Licenses]{% endif %} の右側にある [**View {% if currentVersion == "free-pro-team@latest" %}details{% elsif enterpriseServerVersions contains currentVersion %}users{% endif %}**] または [{% if currentVersion == "free-pro-team@latest" %}{% octicon "download" aria-label="The download icon" %}{% elsif enterpriseServerVersions contains currentVersion %}**Export license usage**] をクリックします{% endif %}。{% if currentVersion == "free-pro-team@latest" %}
+  ![[View details] ボタンと [User Licenses] の右にあるダウンロードアイコン付きボタン](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}
 {% if currentVersion == "free-pro-team@latest" or ver_gt "enterprise-server@3.0" %}
-1. Optionally, to view usage details for other features, in the left sidebar, click **Billing**. ![Enterpriseアカウント設定のサイドバーの支払いタブ](/assets/images/help/business-accounts/settings-billing-tab.png)
+1. 必要に応じて、他の機能の使用状況の詳細を表示するには、左サイドバーで [**Billing**] をクリックします。 ![Enterpriseアカウント設定のサイドバーの支払いタブ](/assets/images/help/business-accounts/settings-billing-tab.png)
 
 ### 参考リンク
 
-- "[About billing for GitHub Actions](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions#about-billing-for-github-actions)"
-- "[About billing for Git Large File Storage](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage)"
-- "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)"
+- 「[GitHub Actions の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions#about-billing-for-github-actions)」
+- 「[Git Large File Storage の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage)」
+- 「[{% data variables.product.prodname_GH_advanced_security %} のライセンスについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)」
 
 {% endif %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index 932cd659dd..dea42fe585 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 Organization の説明、場所、Web サイト、メールアドレスをオプションで追加することや、重要なリポジトリをページの上部にピン止めすることもできます。
 
-{% if currentVersion == "free-pro-team@latest" %}Organization の ID を確認し、Organization のプロファイルページに「Verified」のバッジを表示するには、{% data variables.product.product_name %} を使用して Organization のドメインを検証する必要があります。 詳しい情報については [Organization のドメインの検証](/organizations/managing-organization-settings/verifying-your-organizations-domain)を参照してください。
+{% if currentVersion == "free-pro-team@latest" %}Organization の ID を確認し、Organization のプロファイルページに「Verified」のバッジを表示するには、{% data variables.product.product_name %} を使用して Organization のドメインを検証する必要があります。 For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![検証済み Organization プロフィールページのサンプル](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index 4af3816e79..3d48f43bb9 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ topics:
 
 特定のプログラムに参加すると、{% data variables.product.prodname_dotcom %} でプロフィールに自動的にバッジが表示されます。
 
-| バッジ                                                             | プログラム                                                                | 説明                                                                                                                                                                                                                                                               |
-| --------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} Contributor** | 2020 Arctic Vault プログラムでアーカイブされたリポジトリのデフォルトブランチでコミットを作成すると、プロフィールで {% data variables.product.prodname_arctic_vault %} コントリビューターバッジを取得できます。 詳しい情報については、[{% data variables.product.prodname_archive %}](https://archiveprogram.github.com) を参照してください。            |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **開発者プログラムメンバー**                                                     | GitHub 開発者プログラムの登録メンバーの場合は、GitHub API でアプリを開発すると、プロフィールで開発者プログラムメンバーのバッジを取得します。 GitHub 開発者の詳しい情報については、「[GitHub 開発者](/program/)」を参照してください。                                                                                                                        |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **GitHub スポンサー**                                                     | {% data variables.product.prodname_sponsors %} を通じてオープンソースコントリビューターをスポンサーした場合、プロフィールで GitHub スポンサーのバッジを取得します。 詳細は、「[オープンソースコントリビューターに対するスポンサー](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)」を参照してください。 |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                              | {% data variables.product.prodname_pro %} を使用すると、プロフィールで PRO バッジを取得します。 {% data variables.product.prodname_pro %} の詳細は、「[{% data variables.product.prodname_dotcom %} の製品](/github/getting-started-with-github/githubs-products#github-pro)」を参照してください。         |
+| バッジ                                                                                                                      | プログラム                                                                | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter Contributor badge icon](/assets/images/help/profile/badge-mars-2020-small.png)                    | **Mars 2020 Helicopter Contributor**                                 | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
+| ![Arctic Code Vault Contributor badge icon](/assets/images/help/profile/badge-arctic-code-vault-small.png)               | **{% data variables.product.prodname_arctic_vault %} Contributor** | 2020 Arctic Vault プログラムでアーカイブされたリポジトリのデフォルトブランチでコミットを作成すると、プロフィールで {% data variables.product.prodname_arctic_vault %} コントリビューターバッジを取得できます。 Hovering over the badge shows you several of the repositories you contributed to that were part of the program. 詳しい情報については、[{% data variables.product.prodname_archive %}](https://archiveprogram.github.com) を参照してください。                                                                                                                                                                                                                                                                                           |
+| ![{% data variables.product.prodname_dotcom %} Sponsor badge icon](/assets/images/help/profile/badge-sponsors-small.png) | **{% data variables.product.prodname_dotcom %} Sponsor**             | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. 詳細は、「[オープンソースコントリビューターに対するスポンサー](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)」を参照してください。                                                                                                                                                                                                                                        |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                              | **開発者プログラムメンバー**                                                     | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% data variables.product.prodname_dotcom %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/).                                                                                                                                                                                                                                                                                   |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                                     | **Pro**                                                              | {% data variables.product.prodname_pro %} を使用すると、プロフィールで PRO バッジを取得します。 {% data variables.product.prodname_pro %} の詳細は、「[{% data variables.product.prodname_dotcom %} の製品](/github/getting-started-with-github/githubs-products#github-pro)」を参照してください。                                                                                                                                                                                                                                                                                                                                                                                                        |
 
 ### プロフィールでバッジを無効にする
 
-PRO および {% data variables.product.prodname_arctic_vault %} のバッジなど、参加している {% data variables.product.prodname_dotcom %} プログラムの一部のバッジを無効にできます。
+You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
 
 {% data reusables.user_settings.access_settings %}
-2. [Profile settings] で、無効にするバッジの選択を解除します。 ![プロフィールでバッジを非表示にするチェックボックス](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. [Profile settings] で、無効にするバッジの選択を解除します。 ![プロフィールでバッジを非表示にするチェックボックス](/assets/images/help/profile/profile-badge-settings.png)
 3. [**Update preferences**] をクリックします。
 
 {% endif %}
 
+### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
+
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+
+| {% data variables.product.prodname_dotcom %} Repository                       | バージョン     | Tag                                                                                                        |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.2       | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### 参考リンク
 
 - [プロフィールについて](/articles/about-your-profile)
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index eeca1bc3b6..f595d24dff 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. プライマリメールアドレスとして新しいメールアドレスを追加したい場合、[Add email address] の下で新しいメールアドレスを入力し、[**Add**] をクリックします。 ![別のメールアドレスを追加するボタン](/assets/images/help/settings/add_another_email_address.png)
 4. [Primary email address] で、ドロップダウンメニューからプライマリメールアドレスとして使いたいメールアドレスをクリックし、[**Save**] をクリックします。 ![プライマリに設定するボタン](/assets/images/help/settings/set_as_primary_email.png)
 5. アカウントから古いメールアドレスを削除するには、古いメールの横にある {% octicon "trashcan" aria-label="The trashcan symbol" %} をクリックします。
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}をクリックしてください。
 {% if currentVersion == "free-pro-team@latest" %}
 6. 新しいプライマリメールアドレスを検証してください。 認証済みメールアドレスがないと、
 {% data variables.product.product_name %} のすべての機能を使用できません。 詳細は「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index 7c3434d813..6f99b3fa5a 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -1,23 +1,20 @@
 ---
 title: テーマ設定を管理する
-intro: 'システム設定に従うか、ライトモードまたはダークモードを常に使用するようテーマ設定を行うことで、{% data variables.product.product_name %} の外観を管理できます。'
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
 versions:
   free-pro-team: '*'
 topics:
   - Accounts
 ---
 
-{% note %}
-
-**注釈:** テーマ設定は現在ベータで、変更されることがあります。
-
-{% endnote %}
-
-{% data variables.product.product_name %} を使用時期と使用方法を選択して柔軟性を高めるために、テーマ設定をして {% data variables.product.product_name %} の外観を変更できます。 ライトとダークの 2 つのテーマから選択するか、システム設定に従うかを {% data variables.product.product_name %} で設定できます。 一部の開発者は、個人の好みや、特定のデバイスの消費電力を削減するため、または暗い場所での目の疲れを軽減するためにダークテーマを使用しています。
+{% data variables.product.product_name %} を使用時期と使用方法を選択して柔軟性を高めるために、テーマ設定をして {% data variables.product.product_name %} の外観を変更できます。 You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
 
 {% data reusables.user_settings.access_settings %}
 1. [User settings] サイドバーで、[**Appearance**] をクリックします。 ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png)
-1. [Theme] で、テーマ設定を選択します。 ![テーマ設定用のラジオボタン](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. Under "Theme mode", select the drop-down menu, then click a theme preference. ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. 使いたいテーマをクリックしてください。
+    - If you chose a single theme, click a theme. ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - If you chose to follow your system settings, click a day theme and a night theme. ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### 参考リンク
 
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
index 27fa819d2b..79eb89b5c7 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
@@ -32,7 +32,7 @@ topics:
 | {% if currentVersion == "free-pro-team@latest" %}コラボレータを招待{% else %}コラボレータを追加{% endif %}                                                                                                                  |                                                                                                                                                                                                                                                                                                   |
 | [個人リポジトリへのコラボレータの招待](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)                                                                            |                                                                                                                                                                                                                                                                                                   |
 | リポジトリの表示変更                                                                                                                                                                                                | 「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」 |{% if currentVersion == "free-pro-team@latest" %}
-| リポジトリとのインタラクションの制限                                                                                                                                                                                        | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| リポジトリとのインタラクションの制限                                                                                                                                                                                        | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | デフォルトブランチを含むブランチ名の変更                                                                                                                                                                                      | 「[ブランチ名を変更する](/github/administering-a-repository/renaming-a-branch)」 
 {% endif %}
 | 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする                                                                                                                                                                      | [保護されたブランチについて](/github/administering-a-repository/about-protected-branches)                                                                                                                                                                                                                      |
@@ -70,7 +70,7 @@ topics:
 
 | アクション                                       | 詳細情報                                                                                                                                                                                                                                                                          |
 |:------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| リポジトリのフォーク                                  | 「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| リポジトリのフォーク                                  | 「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | デフォルトブランチ以外のブランチ名の変更                        | 「[ブランチ名を変更する](/github/administering-a-repository/renaming-a-branch)」 
 {% endif %}
 | リポジトリ内のコミット、プルリクエスト、Issue に関するコメントの作成、編集、削除 | <ul><li>「[About issues](/github/managing-your-work-on-github/about-issues)」</li><li>「[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)」</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                                     |
diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index ece5b15ff0..5098c828e8 100644
--- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ topics:
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. 削除するコラボレータの右側にある次をクリックします。
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}をクリックしてください。
   ![コラボレーターを削除するボタン](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. 左のサイドバーで、[**Collaborators & teams**] をクリックします。 ![[Collaborators] タブ](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md
index c306bb24f4..593d8bc84d 100644
--- a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md
+++ b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md
@@ -14,9 +14,9 @@ topics:
 
 GitHub.com、GitHub Enterprise Server、およびあなたがいずれかの製品にアップロードする情報は、米輸出管理規則（EAR）を含む貿易管理規制の対象となる場合があります。
 
-GitHub のビジョンは、開発者たちがどこからでもコラボレーションに参加できるグローバルなプラットフォームを築くことです。 当社は、政府の命令を精査し、ユーザーおよびお客様が法律で要求される範囲を超えた影響を受けることがないようにする責任を真摯に受け止めています。 こうした取り組みには、オープンソースプロジェクトを含むパブリックリポジトリサービスを利用可能かつアクセス可能に保つことで、制裁対象地域の開発者が参加する個人的なコミュニケーションをサポートすることも含まれます。 This also means GitHub will advocate for developers in sanctioned regions to enjoy greater access to the platform and full access to the global open source community.
+GitHub のビジョンは、開発者たちがどこからでもコラボレーションに参加できるグローバルなプラットフォームを築くことです。 当社は、政府の命令を精査し、ユーザーおよびお客様が法律で要求される範囲を超えた影響を受けることがないようにする責任を真摯に受け止めています。 こうした取り組みには、オープンソースプロジェクトを含むパブリックリポジトリサービスを利用可能かつアクセス可能に保つことで、制裁対象地域の開発者が参加する個人的なコミュニケーションをサポートすることも含まれます。 これは、 制裁対象地域にいる開発者がプラットフォームへのアクセスをより享受できること、そしてグローバルなオープンソースコミュニティに完全に参加できることをGitHubが提唱していることをも意味します。
 
-As a result of our advocacy and hard work with U.S. regulators, GitHub has secured a license from the U.S. Treasury Department’s Office of Foreign Assets Control (OFAC) to restore our cloud services to developers in Iran. And we will continue to work with U.S. regulators to secure similar licenses to offer collaboration services to developers in Syria and Crimea. We are committed to advocating for the broadest possible developer access, as we believe offering code collaboration services for developers in sanctioned regions makes the global developer community stronger, advances human progress, and supports the enduring U.S. foreign policy of promoting free speech and the free flow of information. For information about the license we secured for developers in Iran, read [the blog post](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran).
+当社の運動と米 規制当局による尽力のおかげで、GitHubは、米 財務省の外国資産管理局 (OFAC) から、イランの開発者のためにクラウドサービスを復活させるための認可を獲得しました。 当社は シリアおよびクリミアの開発者にもコラボレーションサービスを提供するため、同様の認可を獲得できるよう引き続き米規制当局に働きかけていきます。 当社は、開発者が可能な限り幅広くアクセスできるよう訴えることに取り組んでいます。なぜなら、制裁対象地域の開発者にコラボレーションサービスを提供することがグローバルな開発者コミュニティを強化し、人類の進歩を推し進め、そして言論の自由と情報の自由な流通を推進するという米国の 長期的な外交政策を支援するものであると信じているからです。 当社がイランの開発者のために獲得した認可に関する情報については、[こちらのブログ記事](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran)をお読みください。
 
 なお、以下の情報は便宜上提供されるものであり、GitHub の製品およびサービスをご利用になる際は、ご自身の責任のもと米 輸出管理法を含む適用されるすべての法律および規制を遵守してください。
 
@@ -24,15 +24,15 @@ As a result of our advocacy and hard work with U.S. regulators, GitHub has secur
 
 #### GitHub.com
 
-[利用規約](/articles/github-terms-of-service)に基づき、ユーザは米輸出管理法および制裁法を含む適用法を遵守した場合に限って、GitHub.com にアクセスし、これを使用できます。 export control and sanctions laws.
+[利用規約](/articles/github-terms-of-service)に基づき、ユーザは米輸出管理法および制裁法を含む適用法を遵守した場合に限って、GitHub.com にアクセスし、これを使用できます。
 
-ユーザには、GitHub.com で開発および共有するコンテンツが、EAR や米国際武器取引規制（ITAR）などの米輸出管理法を遵守していることを確認する責任があります。 export control laws, including the EAR and the U.S. International Traffic in Arms Regulations (ITAR). [GitHub.com](https://github.com) で利用可能なクラウドホスト型サービスは、ITAR に基づいてデータをホストするように設計されておらず、現在、国ごとにリポジトリアクセスを制限する機能を提供していません。 ITAR などの輸出管理対象データを扱うコラボレーションを検討している場合は、GitHub のオンプレミス製品である [GitHub Enterprise Server](https://enterprise.github.com) を検討することをお勧めします。
+ユーザには、GitHub.com で開発および共有するコンテンツが、EAR や米国際武器取引規制（ITAR）などの米輸出管理法を遵守していることを確認する責任があります。      [GitHub.com](https://github.com) で利用可能なクラウドホスト型サービスは、ITAR に基づいてデータをホストするように設計されておらず、現在、国ごとにリポジトリアクセスを制限する機能を提供していません。 ITAR などの輸出管理対象データを扱うコラボレーションを検討している場合は、GitHub のオンプレミス製品である [GitHub Enterprise Server](https://enterprise.github.com) を検討することをお勧めします。
 
-GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in Iran. This includes all public and private services for individuals and organizations, both free and paid.
+現在GitHubは、イランに居住する、またはその他何らかの意味でイランの住民である開発者に対し、クラウドサービスを提供する認可をOAFCから取得しています。 この認可には、個人および組織に対するあらゆる公開および非公開サービス (有料、無料の両方) が含まれています。
 
-GitHub cloud services, both free and paid, are also generally available to developers located in Cuba.
+GitHubのクラウドサービス (有料、無料の両方) は、キューバにいる開発者でもほとんど利用できます。
 
-Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials, may be restricted from accessing or using GitHub.com. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. さらに、[17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) に記載されている禁止対象の最終用途を含む、適用される輸出管理法の下で禁止されている目的に GitHub.com を使用することはできません。
+特別指定国民 (SDN) および米国およびその他の適用法の下で拒否または遮断されたその他の関係者、 および特定の政府関係者は、GitHub.comへのアクセスまたは利用が制限される場合があります。 また、ユーザは、制裁対象国の政府を含む上記の当事者のために、またはその代理としてGitHub.comを利用することはできません。 さらに、[17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) に記載されている禁止対象の最終用途を含む、適用される輸出管理法の下で禁止されている目的に GitHub.com を使用することはできません。
 
 #### GitHub Enterprise Server
 
@@ -44,31 +44,31 @@ GitHub Enterprise Server は商用の大衆市場製品であり、`5D992.c` の
 
 ### よくある質問
 
-#### On which countries and territories are U.S. government sanctions applied?
+#### 米政府の制裁はどの国や地域 に適用されますか？
 
-クリミア、キューバ、イラン、北朝鮮、シリアです。 With respect to Iran, however, GitHub now has a license from the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) to provide cloud services to developers located or otherwise resident in that country. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba.
+クリミア、キューバ、イラン、北朝鮮、シリアです。 ただしイランに関しては現在、 GitHubはイランに居住する、またはその他何らかの意味でイランの住民である開発者にための認可を財務省の外国資産管理局 (OFAC) から取得しています。 GitHubのクラウドサービス (有料、無料の両方) は、キューバにいる開発者でもほとんど利用できます。
 
 #### 制裁対象国/地域に住んでいない人や、制裁対象国/地域と職業的なつながりを持たない人がアクセスしたり異議を申し立てたりすることができるよう、GitHub は何か対策をしていますか？
 
 アカウントが意図せずまたは誤って影響を受けることはまれですが、そのような事態に対処するための異議申し立てプロセスはあります。
 
-個人ユーザまたは Organization 管理者に対する決定が誤りであると考えられる場合、そのユーザは GitHub に検証情報を提供することで決定に異議を申し立てることができます。 If GitHub receives sufficient information to verify that the user or organization is not affiliated with a U.S.-sanctioned jurisdiction for which we do not have a license or otherwise restricted by U.S. economic sanctions, then the flag will be removed. [個人アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrGBcceazKIoz6pY)と [Organization アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrB2je5RBkqLEt5D)をご覧ください。
+個人ユーザまたは Organization 管理者に対する決定が誤りであると考えられる場合、そのユーザは GitHub に検証情報を提供することで決定に異議を申し立てることができます。 ユーザまたは組織が米国の制裁対象区域と関連していないなど、米国の経済制裁によって制限されていないことを確認するのに十分な情報を GitHub が受け取った場合、 決定は取り消されます。 [個人アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrGBcceazKIoz6pY)と [Organization アカウントの異議申し立てリクエストフォーム](https://airtable.com/shrB2je5RBkqLEt5D)をご覧ください。
 
 #### 対象地域を旅行することによる影響はありますか？
 
-Travel in these regions may impact your account status, but availability may be reinstated once you are outside of the sanctioned region and upon submitting a successful [individual account appeals request](https://airtable.com/shrGBcceazKIoz6pY) or an [organizational account appeals request](https://airtable.com/shrB2je5RBkqLEt5D).
+対象地域内に旅行をすることがアカウントのステータスに影響する可能性はありますが、制裁対象国/地域外に出た後に[個人アカウントの異議申し立てリクエスト](https://airtable.com/shrGBcceazKIoz6pY)または[Organizationアカウントの異議申し立てリクエスト](https://airtable.com/shrB2je5RBkqLEt5D)を送信すると、再び利用可能になる場合があります。
 
 #### 何が利用できて何が利用できないのですか？
 
-GitHub now has a license from OFAC to provide cloud services to developers located or otherwise resident in the U.S.-sanctioned country of Iran. The license includes all public and private services for individuals and organizations, both free and paid. GitHub cloud services, both free and paid, are also generally available to developers located in Cuba.
+現在GitHubは、米国の制裁対象国であるイランに居住する、またはその他何らかの意味でイランの住民である開発者に対し、クラウドサービスを提供する認可をOAFCから取得しています。 この認可には、個人および組織に対するあらゆる公開および非公開サービス (有料、無料の両方) が含まれています。 GitHubのクラウドサービス (有料、無料の両方) は、キューバにいる開発者でもほとんど利用できます。
 
 GitHub is committed to continuing to offer free public repository services to developers with individual and organizational accounts in Syria and Crimea. This includes limited access to free services, such as public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes, for personal communications only, and not for commercial purposes.
 
-For paid organizational accounts in these sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes.
+制裁対象地域における有料の Organization アカウントの場合、ユーザはパブリックリポジトリへのアクセスが制限される場合があります。具体的には、アーカイブ済みの読み取り専用リポジトリになります。 For free organizational accounts in these sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes.
 
-GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. foreign policy of promoting free speech and the free flow of information.
+GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。   We believe that offering those services advances human progress, international communication, and the enduring U.S. 長期的な外交政策を支援するものであると信じているからです。
 
-Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries.
+特別指定国民 (SDN) および米国およびその他の適用法の下で拒否または遮断されたその他の関係者、 and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries.
 
 GitHub services are not available to developers located or otherwise resident in North Korea.
 
@@ -88,7 +88,7 @@ The restriction suspends access to private repository services and paid services
 
 #### 貿易制限のあるユーザは、プライベートリポジトリデータにアクセスできますか（リポジトリデータのダウンロードや削除など）？
 
-残念ながら、当社による法律の解釈では、米国政府の許可がない限り、プライベートリポジトリのコンテンツのダウンロードまたは削除を許可することはできません。 GitHub Enterprise Server is a self-hosted virtual appliance that can be run within Customer’s own datacenter or virtual private cloud. We will strongly advocate, with U.S. 私たちは、貿易制限のあるユーザがプライベートリポジトリのコンテンツを確保する権利を、米国の規制当局に強く主張する予定です。 また、制裁対象市場の開発者が GitHub サービスをもっと利用できるようになるよう求め、開発者のグローバルな個人通信をサポートすることで実現するコードコラボレーションの重要性をさらに強調するつもりです。
+残念ながら、当社による法律の解釈では、米国政府の許可がない限り、プライベートリポジトリのコンテンツのダウンロードまたは削除を許可することはできません。 GitHub Enterprise Server is a self-hosted virtual appliance that can be run within Customer’s own datacenter or virtual private cloud.   私たちは、貿易制限のあるユーザがプライベートリポジトリのコンテンツを確保する権利を、米国の規制当局に強く主張する予定です。 また、制裁対象市場の開発者が GitHub サービスをもっと利用できるようになるよう求め、開発者のグローバルな個人通信をサポートすることで実現するコードコラボレーションの重要性をさらに強調するつもりです。
 
 #### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran?
 
@@ -96,9 +96,9 @@ The license we have secured includes all public and private services, for indivi
 
 For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students.
 
-Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub.
+特別指定国民 (SDN) および米国およびその他の適用法の下で拒否または遮断されたその他の関係者、 and other applicable law, and certain government officials may be restricted from accessing or using GitHub.
 
-If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. economic sanctions, then the flag will be removed.
+If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. 決定は取り消されます。
 
 #### Will Iranian GitHub users be able to use paid services under the license?
 
@@ -107,4 +107,4 @@ Pursuant to the license we have received from OFAC, we are restoring all cloud s
 #### Can you clarify availability of GitHub to Cuban developers?
 
 GitHub cloud services, both free and paid, are generally available to developers located in Cuba.  
-Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Additionally, users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries.
+Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. また、ユーザは、制裁対象国の政府を含む上記の当事者のために、またはその代理としてGitHub.comを利用することはできません。
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 e790b96c35..32ce1c7cd4 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
@@ -52,13 +52,13 @@ Of course, you can always contact us to {% data variables.contact.report_abuse %
 
 - #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. 言葉を発する場合や画像を投稿する場合はもちろん、ソフトウェアを作成する場合でさえも、それが他人からどのように解釈される可能性があるかを慎重に考えてください。 あなたが冗談のつもりでも、そのように受け取られないかもしれません。 自分が投稿したコンテンツが脅しである、または暴力やテロを助長していると他の誰かが解釈する*かもしれない*と思われる場合は、 それをGitHubに投稿するのを止めましょう。 場合によっては、当社が身体的危害のリスクや公共の安全に対する脅威だと判断し、暴力の脅威として法執行機関に報告する場合があります。
 
-- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. 攻撃的または侮辱的なアプローチでこうしたデリケートなトピックを扱った場合、他の人を不快に感じさせたり、場合によっては危険にさえ感じさせたりすることがあることを認識してください。 誤解が生まれる可能性を完全に排除することはできませんが、デリケートなトピックを議論するときは、常に敬意を払い、礼儀正しく振る舞うことがコミュニティメンバーに期待されます。
+- #### 差別的発言と差別 年齢、体の大きさ、障害、民族性、性自認、性表現、経験の度合い、国籍、容姿、人種、宗教、性同一性、性的指向などのトピックを持ち出すこと自体は禁止されていませんが、相手が何者かであるかを根拠にして個人またはグループを攻撃する発言を当社は許容しません。 攻撃的または侮辱的なアプローチでこうしたデリケートなトピックを扱った場合、他の人を不快に感じさせたり、場合によっては危険にさえ感じさせたりすることがあることを認識してください。 誤解が生まれる可能性を完全に排除することはできませんが、デリケートなトピックを議論するときは、常に敬意を払い、礼儀正しく振る舞うことがコミュニティメンバーに期待されます。
 
-- #### Bullying and harassment We do not tolerate bullying or harassment. これは、特定の個人またはグループを標的とする常習的な煽りや脅迫のことです。 一般的に、迷惑な行動を続けた場合、いじめや嫌がらせになる恐れが高くなります。
+- #### いじめと嫌がらせ 私たちは、いじめや嫌がらせを容認しません。 これは、特定の個人またはグループを標的とする常習的な煽りや脅迫のことです。 一般的に、迷惑な行動を続けた場合、いじめや嫌がらせになる恐れが高くなります。
 
 - #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors.
 
-- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. なりすましは嫌がらせの一つです。
+- #### なりすまし 他人のアバターをコピーしたり、他人のメールアドレスを使ってコンテンツを投稿したり、類似するユーザ名を使用したりするなど、他人になりすまして自分の身元を誤解させようとしてはいけません。 なりすましは嫌がらせの一つです。
 
 - #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. 脅迫や嫌がらせに該当するなど状況次第では、当社は対象の同意なしに撮影または配信された写真やビデオなどの他の情報をプライバシーの侵害とみなす場合があります。その情報が対象の安全リスクになる場合は特にです。
 
diff --git a/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md
index af0ca43b78..2f43b015da 100644
--- a/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,10 +9,12 @@ topics:
   - Legal
 ---
 
+_These terms apply to 1) GitHub.com (non-Enterprise) customers who have accepted the Corporate Terms of Service, and 2) Enterprise customers who licensed the Service prior to January 4, 2021. Enterprise customers who purchase Products or Services after that date are directed to https://github.com/enterprise-legal for current terms._
+
 貴社のビジネスにおけるニーズを満たすために GitHub をお選びいただき、ありがとうございます。 本契約を注意深くお読みください。GitHub がお客様と書面による合意を別途行わない限り、本製品 (以下に定義) の利用に対しては、この契約が適用されます。 「同意する」またはそれに類似するボタンをクリックするか、本製品を利用することにより、お客様は本契約の規約および条件の全てに同意することになります。 お客様が、企業またはその他の法人を代表して契約を締結しようとする場合、お客様は、本契約を締結するためにその企業またはその他の法人に義務を負担させる法的権限を持つことを表明するものとします。
 
 ### GitHub企業向け利用規約
-Version Effective Date: November 16, 2020
+このバージョンの発効日: 2020 年 11 月 16 日
 
 本契約は、以下に詳述する GitHub の提供品 (併せて「**製品**」) に対して適用されます。
 - 「サービス」、
@@ -24,7 +26,7 @@ Version Effective Date: November 16, 2020
 
 「**関係会社**」とは、直接的または間接的に支配している、支配されている、あるいは当事者と共通の支配下にある、あらゆる法人を意味します。本定義において「支配」とは、所有権のうち 50% 超を持つか、当該法人の経営管理を指揮する権限を有することを意味します。
 
-「**契約**」とは、集合的に、本書に含まれるか、または本書で参照されるすべての規約、条件、通知、並びに、当社が適宜「サービス」に掲載する場合があるその他すべての操作規則、ポリシーおよび手順を指します。 GitHub のサイトポリシーは、[https://docs.github.com/categories/site-policy](/categories/site-policy) でご確認いただけます。
+「**契約**」とは、集合的に、本書に含まれるか、または本書で参照されるすべての規約、条件、通知、並びに、当社が適宜「サービス」に掲載する場合があるその他すべての操作規則、ポリシーおよび手順を指します。 GitHub's site policies are available at [https://docs.github.com/categories/site-policy](/categories/site-policy).
 
 「**全ユーザ**」とは、「サービス」を利用する、「お客様」の「ユーザ」および「外部ユーザ」を総称的に意味します。
 
@@ -281,7 +283,7 @@ GitHub は、独自の裁量により、いつでも本契約を修正する権
 GitHub は、「アップデート」および新機能の追加により、サービスを変更します。 上記にかかわらず、GitHubは通知の有無にかかわらず、「サービス」(またはその一部) をいつでも変更する、あるいは一時的または恒久的に停止する権利を留保するものとします。
 
 ### S. サポート
-GitHub は、週末および米国の休日を除き、1 日 24時間、週 5 日の標準的な技術「サポート」を、「サービス」に対して無料で提供するものとします。 （アメリカの祝日は除く） 「Standard Support」は、「GitHub Support」を通じたウェブベースのチケット発行によってのみ提供され、「サポート」の要請は、GitHub の「サポート」チームがやり取りできる「ユーザ」から行う必要があります。 GitHub may provide premium Support (subject to the [GitHub Premium Support for Enterprise Cloud](/articles/about-github-premium-support) terms) or dedicated technical Support for the Service at the Support level, Fees, and Subscription Term specified in an Order Form or SOW.
+GitHub は、週末および米国の休日を除き、1 日 24時間、週 5 日の標準的な技術「サポート」を、「サービス」に対して無料で提供するものとします。 （アメリカの祝日は除く） 「Standard Support」は、「GitHub Support」を通じたウェブベースのチケット発行によってのみ提供され、「サポート」の要請は、GitHub の「サポート」チームがやり取りできる「ユーザ」から行う必要があります。 GitHub は、「注文書」または「SOW」に記載されている「サポート」レベル、「料金」、および「プラン契約期間」で、「サービス」に対してプレミアム「サポート」 (「[GitHub Enterprise Cloud の GitHub Premium Support](/articles/about-github-premium-support)」の規定に従う) または専用技術「サポート」を提供することができます。
 
 ### T. 雑則
 
diff --git a/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
index 44d402517a..4b1a0cc010 100644
--- a/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
+++ b/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Data Protection Agreement (Non-Enterprise Customers)
+title: GitHubデータ保護契約 (Enterprise以外のお客様)
 redirect_from:
   - /github/site-policy/github-data-protection-addendum
   - /github/site-policy-deprecated/github-data-protection-addendum
@@ -7,7 +7,7 @@ versions:
   free-pro-team: '*'
 ---
 
-_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._
+_この規約は、Enterprise以外のお客様に適用されます。 また、2021年1月4日より前にGitHub製品のライセンスを取得したEnterpriseのお客様にも適用されます。 Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._
 
 ## はじめに
 
@@ -179,170 +179,170 @@ c.  gitHubがセクション7.7の義務に従っているという合理的な
 
 本標準契約条項の使用に規制当局の承認が必要な国においては、お客様が規制当局から必要な証人を得ていない限り、欧州委員会2010/87/EU (2010年2月) に基づき、当該国からのデータ輸出を合法とするにあたり、本標準契約条項に依拠することはできません。
 
-適切な水準のデータ保護を保証しない第三国に拠点を置く処理者に個人データを移転することについて定めた一般データ保護規則 (EU 2016/679) 第46条第2項において、お客様 (データ移転元) と、GitHub (データ移転先、本書下部に署名) との各「当事者」、総称して「両当事者」は、添付1に定めるデータ移転元からデータ移転先への個人データの移転のため、個人のプライバシー、基本的権利、および自由の保護に関する適切な保護措置に関する引証として、以下の契約条項 (「条項」または「標準契約条項」) に合意したものとします。
+適切な水準のデータ保護を保証しない第三国に拠点を置く処理者に個人データを移転することについて定めた一般データ保護規則 (EU 2016/679) 第46条第2項において、お客様 (データ輸出者) と、GitHub (データ輸入者、本書下部に署名) との各「当事者」、総称して「両当事者」は、添付文書1に定めるデータ輸出者からデータ輸入者への個人データの移転のため、個人のプライバシー、基本的権利、および自由の保護に関する適切な保護措置に関する引証として、以下の契約条項 (「条項」または「標準契約条項」) に合意したものとします。
 
 #### 第1条: 定義
-(a) 「個人データ」、「データの特別カテゴリ」、「処理」、「管理者」、「処理者」、「データ主体」、および「監督当局」という用語は、個人データの処理に関する保護およびかかるデータの自由な移動に関する一般データ保護規則 (EU 2016/679) と同じ意味を持つものとします。
+(a) 「個人データ」、「特別なカテゴリのデータ」、「処理」、「管理者」、「処理者」、「データ主体」、および「監督当局」という用語は、個人データの処理に関する保護およびかかるデータの自由な移動に関する一般データ保護規則 (EU 2016/679) と同じ意味を持つものとします。
 
-(b) 「データ移転元」とは、個人情報を移転する管理者を意味します。
+(b) 「データ輸出者」とは、個人情報を移転する管理者を意味します。
 
-(c) 「データ移転先」とは、移転後に、データ移転元の指示および本条項の規定に従って処理するためにデータ移転元から個人データを受信することに合意し、かつ一般データ保護規則 (EU 2016/679) 第45条第2項の意味する範囲において適切な保護を保証しない第三国の機構の支配下にない処理者のことを意味します。
+(c) 「データ輸入者」とは、移転後に、データ輸出者の指示および本条項の規定に従って処理するためにデータ輸出者から個人データを受信することに合意し、かつ一般データ保護規則 (EU 2016/679) 第45条第2項の意味する範囲において適切な保護を保証しない第三国の機構の支配下にない処理者のことを意味します。
 
-(d) 「サブプロセッサー」とは、データ移転元の指示、本条項の規定、および書面による請負契約の規定に従い、移転後にデータ移転元の代理として処理活動を実施することのみを目的として、データ移転先から、または データ移転先の別のサブプロセッサーから個人データを受信することに合意している、データ移転先またはデータ移転先の別のサブプロセッサーから業務を請け負う任意の処理者のことを意味します。
+(d) 「サブプロセッサー」とは、データ輸出者の指示、本条項の規定、および書面による請負契約の規定に従い、移転後にデータ輸出者の代理として処理活動を実施することのみを目的として、データ輸入者から、または データ輸入者の別のサブプロセッサーから個人データを受信することに合意している、データ輸入者またはデータ輸入者の別のサブプロセッサーから業務を請け負う任意の処理者のことを意味します。
 
-(e)「適用されるデータ保護法」とは、個人の基本的人権と自由、特に、データ移転元が存在する加盟国内におけるデータコントローラーに適用される、個人情報処理に関するプライバシーの権利を保護する法律のことを意味します。
+(e)「適用されるデータ保護法」とは、個人の基本的人権と自由、特に、データ輸出者が存在する加盟国内におけるデータコントローラーに適用される、個人情報処理に関するプライバシーの権利を保護する法律のことを意味します。
 
-(f) 特に処理がネットワークを介したデータの送信を伴う偶発的または違法な破壊、偶発的な紛失、改変、不正な開示またはアクセス、およびその他あらゆる違法な処理の形態に対して個人データを保護する対策のことを意味します。
+(f) 「技術的および組織的セキュリティ対策」とは、特に処理がネットワークを介したデータの送信を伴う偶発的または違法な破壊、偶発的な紛失、改変、不正な開示またはアクセス、およびその他あらゆる違法な処理の形態に対して個人データを保護する対策のことを意味します。
 
-#### Clause 2: Details of the transfer
-The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses.
+#### 第2条: 転送の詳細
+転送の詳細、特に適用される特別なカテゴリの個人データについては、本条項と不可分である、下記の添付文書1に明記されています。
 
-#### Clause 3: Third-party beneficiary clause
-1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary.
+#### 第3条: 第三者受益者条項
+1. データ主体は、データ輸出者に対して、本条項、第4条4 (b) から (i)、第5条 (a) から (e) および (g) から (j)、第6条 (1) および (2)、第7条、第8条 (2)、ならびに第9条から第12条を、第三者受益者として執行することができます。
 
-2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity.
+2. データ主体は、データ輸出者が事実上存在しなくなった場合、または法律上存在しなくなった場合、 データ輸入者に対して本条項、第5条 (a) から (e) および (g)、第6条、第7条、第条8 (2)、ならびに第9条から第12条を執行することができます。ただし、後継法人が契約または法律の定めによりデータ輸出者の法的義務をすべて引き受けた場合を除きます。この場合、後継法人がデータ輸出者の権利および義務を引き受けることとなり、データ主体はかかる法人に対して上記条項を執行できます。
 
-3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
+3. データ主体は、サブプロセッサーとデータ輸入者の双方が事実上存在しなくなった場合、法律上存在しなくなった場合、または、債務超過に陥った場合、サブプロセッサーに対して本条項、第5条 (a) から (e) および (g)、第6条、第7条、第条8 (2)、ならびに第9条から第12条を執行することができます。ただし、後継法人が契約または法律の定めによりデータ輸出者の法的義務をすべて引き受けた場合を除きます。この場合、後継法人がデータ輸出者の権利および義務を引き受けることとなり、データ主体はかかる法人に対して上記条項を執行できます。 サブプロセッサーの第三者に対するかかる責任は、かかる条項に基づく自らの処理操作に限定されるものとします。
 
-4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law.
+4. 両当事者は、データ主体が特に希望しており、かつ国家の法令により許可されている場合、組合またははその他組織体がデータ主体を代表することに反対しないものとします。
 
-#### Clause 4: Obligations of the data exporter
-The data exporter agrees and warrants:
+#### 第4条: データ輸出者の義務
+データ輸出者は、以下のことに同意し、保証します。
 
-(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
+(a) 個人データの処理 (その転送を含む) は、これまでも今後も引き続き、適用されるデータ保護法の関連条項に従って実行され、(および該当する該当する場合は、データ輸出者が登記された加盟国の関連当局に通知を行っており)、当該国の関連条項に違反していないこと。
 
-(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
+(b) データ輸入者に対し、移転された個人データの処理を、適用データ保護 法令および本契約条項に従い、当該データ輸出者のためにのみ行うよう指 示していること、また、個人データ処理サービスの継続期間を通じて、 かかる指示を行うこと。
 
-(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
+(c) データ輸入者が、下記の添付文書2に明記された技術的および組織的セキュリティ対策に関して十分な保証を提供すること。
 
-(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
+(d) 適用されるデータ保護法令要件の評価に従い、セキュリティ対策が、特にネットワークを通じた送信による処理が行われる場合の偶発的または違法な破壊、偶発的な喪失、変更、不正開示またアクセス、およびその他のあらゆる違法な処理形態から個人データを保護するのに適切なものであり、また、これらの対策が、最新の技術と対策実施費用を考慮した上で、処理およびデータの性質により生じるリスクを回避できるよう適切なレベルのセキュリティを確保するものであること。
 
-(e) that it will ensure compliance with the security measures;
+(e) セキュリティ対策を遵守するよう万全を期すこと。
 
-(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of the General Data Protection Regulation (EU 2016/679);
+(f) かかる移転に特別カテゴリのデータが含まれる場合、データ主体に対しかかるデータ主体のデータが一般データ保護規則 (EU 2016/679) の意図する範囲で十分な保護が提供されていない第三国に移転される可能性がある旨を通知済みであること、もしくは事前に通知すること、または事後的に可能な限りすみやかに通知すること。
 
-(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
+(g) データ輸出者が、移転の継続または移転の一時停止を解除する旨を決定した場合、第5条 (b) および第8条 (3) に基づきデータ輸入者またはサブプロセッサーから受領した通知を、データ保護監督当局に転送すること。
 
-(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
+h) 要請に応じて、データ主体に対し、添付文書2を除く本契約条項のコピー1 部およびセキュリティ対策の概要、ならびに副処理サービスに関する契約書 (この契約は、本契約条項に従い作成されなければならない) のコピー1 部を提供すること。ただし、本契約条項または副処理サービス契約に商業上の情報が含まれる場合、データ輸出者は、かかる商業上の情報を除外することができる。
 
-(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
+(i) 副処理が行われる場合、当該処理業務が、データ主体の個人データおよび権利に対し、少なくとも本契約条項におけるデータ輸入者と同水準の保護を提供する副処理者により、第11条に従って実施されること。
 
-(j) that it will ensure compliance with Clause 4(a) to (i).
+(j) 第4条 (a) から (i) を遵守するよう万全を期すこと。
 
-#### Clause 5: Obligations of the data importer
-The data importer agrees and warrants:
+#### 第5条: データ輸入者の義務
+データ輸入者は、以下のことに同意し、保証します。
 
-(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
+(a) 個人データの処理を、データ輸出者のためにのみ、データ輸出者の指示 および本契約条項に従って行うこと。何らかの理由により上記を遵守することができない場合、データ輸入者は、すみやかにデータ輸出者に通知することに同意する。この場合、データ輸出者は、データ移転を一時停止する権利および本契約を解除する権利を有する。
 
-(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
+(b) データ輸入者に適用される法令により、データ輸出者からの指示の遂行および本契約に基づく自身の義務の履行が妨げられると信じる理由は存在しないこと。また、本契約条項に規定された保証および義務に実質的に悪影響を及ぼすおそれのある上記法令への変更が行われた場合、データ輸入者は、当該変更を認識した後すみやかに、データ輸出者に対して当該変更を通知すること。この場合、当該データ輸出者は、データ移転を一時停止する権利および本契約を解除する権利を有する。
 
-(c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
+(c) 移転された個人データの処理を行う前に、添付文書2に明記された技術的および組織的セキュリティ対策を講じていること。
 
-(d) that it will promptly notify the data exporter about:
+(d) 以下について、データ輸出者にすみやかに通知すること。
 
-(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
+(i) 法執行機関から、個人データの法的拘束力を有する開示要請を受けた場合。ただし、通知を行うことが禁止されている場合 (例えば、刑法に基づく法執行機関の捜査の秘密性を維持するための禁止) を除く。
 
-(ii) any accidental or unauthorised access, and
+(ii) 偶発的または不正アクセス。
 
-(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
+(iii) データ主体から直接受けた要請。要請を受ける前には対応を行わない。ただし、対応することが認められている場合を除く。
 
-(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred;
+(e) 移転の対象である個人データの処理に関して、データ輸出者からの全ての問い合わせに対して迅速かつ適切に対応するすること。また、移転されたデータの処理に関する監督当局からの助言に従うこと。
 
-(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority;
+(f) データ輸出者の要請に応じて、本契約条項の対象となる処理活動のためのデータ処理施設について監査を受けること。この監査はデータ輸出者、またはデータ輸出者が選定し、該当する場合は監督当局の合意を得た、独立したメンバーにより構成される、必要な専門的資格を有し機密保護義務を課された検査機関により実施されるものとする。
 
-(g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
+(g) 要請に応じ、データ主体に対し、本契約条項またはデータの副処理に関する既存の契約書のコピー1 部を提供すること (ただし、本契約条項または上記副処理契約に商業上の情報が含まれる場合は、当該商業上の情報を除外することができる)。ただし、添付文書2については、データ主体がそのコピーをデータ輸出者から入手できない場合、セキュリティ対策の概要で代替するものとする。
 
-(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
+(h) データの副処理が行われる場合、事前にデータ輸出者に通知し、事前の書面による同意を取得していること。
 
-(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
+(i) 副処理者による処理サービスが、本契約条項の第11条に従い実施されること。
 
-(j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
+(j) 本契約条項に基づき締結されたデータの副処理契約書のコピー1部を、すみやかにデータ輸出者に送付すること。
 
-#### Clause 6: Liability
-1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.
+#### 第6条: 責任
+1. 両当事者は、当事者のいずれかまたは副処理者が本契約条項の第3条または第11条に違反したことにより損害を被ったデータ主体が、当該損害について、データ輸出者から賠償を受ける権利を有することに同意します。
 
-2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
+2. データ輸出者が事実上消滅し、もしくは法律上存在しなくなったこと、または支払不能に陥ったことにより、データ主体が、データ輸入者または副処理者が第3条または第11条に基づく義務に違反したことによる、第1項に基づく賠償請求をデータ輸出者に対して行うことができない場合、データ輸入者は、データ主体が、あたかもデータ輸入者がデータ輸出者であるかのように、データ輸入者に対して請求を行うことができることに同意します。ただし、データ輸出者の承継人が、契約または法律により、データ輸出者の法的義務を全て引き受けた場合を除きます。この場合、当該データ主体は、当該承継人に対して権利を行使することができます。 データ輸入者は、副処理者により違反が行われたという事実に依拠して自身の法的責任を回避することはできなません。
 
-3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses.
+3. データ輸出者およびデータ輸入者の双方が事実上消滅し、もしくは法律上存在しなくなった場合、またはこれらの双方が支払不能に陥ったために、データ主体が、副処理者が第3条または第11条に規定された義務に違反したことによるする請求について、第1項および第2項に規定されたデータ輸出者またはデータ輸入者に対する請求を行うことができない場合、副処理者は、データ主体が、本契約条項に基づく副処理者の副処理に関して、あたかも副処理者がデータ輸出者またはデータ輸入者であるかのように、副処理者に対して請求を行うことができることに同意します。ただし、データ輸出者またはデータ輸入者の承継人が、契約または法律により、データ輸出者またはデータ輸入者の法的義務を全て引き受けた場合を除きます。この場合、データ主体は、当該承継人に対して自身の権利を行使することができます。 副処理者の法的責任は、本契約条項に基づく自身の処理業務に限定されるものとします。
 
-#### Clause 7: Mediation and jurisdiction
-1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject:
+#### 第7条: 調停と管轄
+1. データ輸入者は、データ主体が本契約条項に基づきデータ輸入者に対して第三受益者としての権利を行使し、または損害賠償請求を行った場合、データ主体による以下の決定に従うことに同意します。
 
-(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority;
+(a) 当該紛争を、独立した第三者、また監督当局 (該当する場合) による調停に付託すること。
 
-(b) to refer the dispute to the courts in the Member State in which the data exporter is established.
+(b) 当該紛争を、データ輸出者が設立されている加盟国の裁判所に付託すること。
 
-2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law.
+2. 両当事者は、データ主体が上記選択を行っても、データ主体が国内法または国際法の他の条項に従い救済を求める実体的権利または手続的権利に影響を与えないことに同意します。
 
-#### Clause 8: Cooperation with supervisory authorities
-1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law.
+#### 第8条: 監督当局との協力
+1. データ輸出者は、監督当局が要請した場合、または適用されるデータ保護法令に基づき必要とされる場合、本契約書のコピーを監督当局に預けることに同意します。
 
-2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law.
+2. 両当事者は、監督当局がデータ輸入者および副処理者の監査を行う権利を有することに同意します。この監査の範囲は、適用されるデータ保護法令に基づくデータ輸出者に対する監査と同じものであり、また同じ条件が適用されます。
 
-3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5(b).
+3. データ輸入者は、第2項に基づくデータ輸入者または副処理者の監査の実施を妨げる、データ輸入者または副処理者に適用される法律が存在する場合、データ輸出者にすみやかに通知するものとします。 このような場合、データ輸出者は、第5条 (b) に記載された措置をとる権利を有するものとします。
 
-#### 第9条: 準拠法。
-The Clauses shall be governed by the law of the Member State in which the data exporter is established.
+#### 第9条: 準拠法
+本契約条項は、データ輸出者が設立されている加盟国の法律に準拠するものとします。
 
-#### Clause 10: Variation of the contract
-The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause.
+#### 第10条: 契約の変更
+両当事者は、本契約の変更または修正を行わないことを約束します。 これは、両当事者が、本契約と矛盾しない限度で、必要に応じて商取引上の条項を追加することを妨げるものではありません。
 
-#### Clause 11: Subprocessing
-1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.
+#### 第11条: 副処理
+1. データ輸入者は、データ輸出者の書面による事前の同意なしに、データ輸出者に代わって実施するいかなる処理操作も再委託してはなりません。 データ輸入者が、データ輸出者の同意を得て本契約条項に基づく自身の義務を委託する場合、データ輸入者は、本契約に基づきデータ輸入者に課されるものと同一の義務を副処理者に課す契約を書面で締結することによってのみ、かかる副処理の委託を行うものとします。 副処理者が、かかる書面による契約に基づくデータ保護義務の履行を怠った場合、データ輸入者は、当該契約に基づく副処理者の義務の履行について、データ輸出者に対し完全に責任を負うものとします。
 
-2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
+2. データ輸出者またはデータ輸入者が事実上消滅し、もしくは法律上存在しなくなった場合、またはこれらの双方が支払不能に陥った場合で、かつ契約または法律によりデータ輸出者またはデータ輸入者の法的義務を全て引き受ける承継人が存在しないため、データ主体が第6条1項に規定された損害賠償の請求をデータ輸出者またはデータ輸入者に対して行うことができない場合に備え、データ輸入者と副処理者との間の事前の書面による契約には、第3条に定められている第三者受益者条項を規定するものとします。 サブプロセッサーの第三者に対するかかる責任は、かかる条項に基づく自らの処理操作に限定されるものとします。
 
-3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established.
+3. 第1項で言及されている、契約に基づく副処理におけるデータ保護の観点に関する規定は、データ輸出者が設立された加盟国の法律に準拠するものとします。
 
-4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority.
+4. データ輸出者は、本契約に基づき締結され、第5条 (j) に基づきデータ輸入者から通知された副処理契約のリストを保管し、このリストを少なくとも1年に1回更新するものとします。 このリストは、データ輸出者のデータ保護監督当局も入手できるものとします。
 
-#### Clause 12: Obligation after the termination of personal data processing services
-1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.
+#### 第12条: 個人データ処理サービス終了後の義務
+1. 両当事者は、データ処理サービスの提供が終了した際、データ輸入者および副処理者が、データ輸出者の選択に従い、移転された全ての個人データおよびそのコピーをデータ輸出者に返却するか、または全ての個人データを破棄し、データ輸出者に対して破棄を行った旨を証明することに同意します。ただし、データ輸入者に適用される法律により、データ輸入者が移転されたデータの全部または一部を返還または破棄することが禁じられている場合を除きます。 この場合、データ輸入者は、移転された当該個人データの秘密を保証することおよび当該個人データの処理を積極的に行わないことを保証します。
 
-2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.
+2. データ輸入者および副処理者は、データ輸出者または監督当局の要請に応じ、第1項に規定された措置の監査のため、データ処理設備を提供することに同意します。
 
-### Appendix 1 to the Standard Contractual Clauses
-Data exporter: Customer is the data exporter.
+### 標準契約条項添付文書1
+データ輸出者: お客様はデータ輸出者です。
 
-**Data importer:** The data importer is GitHub, Inc., a global producer of software and services.
+**データ輸入者:** データ輸入者は、ソフトウェアとサービスの世界的なプロデューサーであるGitHub, Inc.です。
 
-**Data subjects:** Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal information to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data:
+**データ主体:** データ主体には、データ輸出者の営業代理人およびエンドユーザ (従業員、請負業者、コラボレーター、およびデータ輸出者のお客様を含む) が含まれます。 また、データ主体には、データ輸入者が提供するサービスのユーザに個人情報を伝達または転送しようと試みる個人も含まれる場合があります。 GitHub は、お客様によるサービスの利用方法に応じて、お客様の個人データに、以下の中から任意のタイプのデータ主体を個人データとして含めることができることを認識しています。
 
--   Employees, contractors and temporary workers (current, former, prospective) of data exporter;
--   Dependents of the above;
--   Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former);
--   Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of data exporter's services;
--   Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter;
--   Stakeholders or individuals who passively interact with data exporter (e.g., because they are the subject of an investigation, research or mentioned in documents or correspondence from or to the data exporter); or
--   Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers, etc.).
+-   データ輸出者の従業員、請負業者、派遣労働者 (現在、過去、見込みを含む)。
+-   上記の被扶養者。
+-   データ輸出者のコラボレータ/担当者 (自然人) または従業員、請負業者または法人コラボレータ/担当者の派遣労働者 (現在、見込み、過去を含む)。
+-   ユーザ (顧客、クライアント、患者、訪問者など) およびデータ輸出者によるサービスのユーザであるその他のデータ主体。
+-   データ輸出者の従業員と積極的に協力、連絡、その他のやり取りを行う、またはデータ輸出者が提供するアプリケーションやウェブサイトなどのコミュニケーションツールを使用するパートナー、利害関係者または個人。
+-   (調査、研究の対象、または文書もしくはデータ輸出者との通信で言及されているという理由などで) データ輸出者と受動的にやり取りを行う利害関係者または個人。
+-   職業的特権を持つ専門家 (医師、弁護士、公証人、宗教活動家など)
 
-**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Service.  GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data:
--   Authentication data (for example, username, email, password);
--   Contact information (for example, email);
--   Unique identification numbers and signatures (IP addresses, unique identifier in tracking cookies or similar technology).
--   Other unique identifying information. Data subjects may include more data such as real names, avatar images, and other personal information;
+**データのカテゴリ:** 電子メール、文書、および本サービスの文脈における電子的形式のその他データに含まれる、転送される個人データ。  GitHub は、お客様によるサービスの利用方法に応じて、お客様の個人データに、以下の中から任意のカテゴリを個人データとして含めることができることを認識しています。
+-   認証データ (ユーザ名、電子メール、パスワードなど)。
+-   連絡先情報 (電子メールなど)。
+-   一意の識別番号および署名 (IPアドレス、トラッキングクッキーまたは類似の技術における一意の識別子)。
+-   その他一意の識別情報。 データ主体には、実名、アバター画像、その他個人情報などが含まれる場合があります。
 
-**Special categories of data (if appropriate):** The data importer does not intentionally collect or process any special categories of data in carrying out its services to the data exporter.
+**特別カテゴリのデータ (該当する場合):** データ輸入者は、データ輸出者に対してサービスを提供するにあたり、いかなる特別カテゴリのデータも意図的に収集または処理しません。
 
-However, because the data importer provides storage services and does not control the categories of data it stores, the data exporter may choose to transfer special categories of data. Consequently, the data exporter is solely responsible for ensuring that it complies with all obligations imposed by applicable laws and regulations relating to the collection and processing of any special categories of data, including obtaining the explicit consent of the data subject prior to processing sensitive personal data.
+しかしながら、データ輸入者はストレージサービスを提供し、そこに保存するデータのカテゴリを管理していないため、データ輸出者は特別カテゴリのデータを転送することも選択できます。 したがってデータ輸出者は、センシティブな個人を処理する前にデータ主体の明示的同意を得ることを含め、特別カテゴリのデータの収集および処理に関して適用される法令により課されるあらゆる義務に確実に従う義務を単独で負います。
 
-**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain Customer Personal Data only to deliver the services the data importer has retained them to provide, and they are prohibited from using Customer Personal Data for any other purpose.
+**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. 下請け業者: DPAに従い、データ輸入者は顧客サポートの提供などの限定的なサービスをデータ輸入者に代わって提供するため、他の企業に業務を委託することができます。 かかる下請け業者は、データ輸入者が下請け業者に要請したサービスを提供する目的においてのみ、お客様の個人データを取得することができ、その他の目的でお客様の個人データを利用することはできないものとします。
 
-### Appendix 2 to the Standard Contractual Clauses
-Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c):
+### 標準契約条項添付文書2
+第4条 (d) および第5条 (c) に従ってデータ輸入者が実施する、技術的および組織的セキュリティ対策を以下に説明します。
 
-**1. Personnel.** Data importer’s personnel will not process Customer Personal Data without authorization. Personnel are obligated to maintain the confidentiality of any Customer Personal Data and this obligation continues even after their engagement ends.
+**1. スタッフ。**データ輸入者のスタッフは、お客様の個人データを承認なしに処理いたしません。 スタッフはあらゆるお客様の個人データについて機密を保持する義務を負い、この義務は雇用期間の終了後も継続します。
 
-**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA
+**2. データプライバシーに関する連絡先。**データ輸入者のデータプライバシー担当者の連絡先住所は次の通りです。 GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA
 
-**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction.
+**3. 技術的および組織的対策。**データ輸入者は、お客様の個人データを保護することを目的として、偶発的喪失、破壊、改変、および不正な開示やアクセス、および以下の違法な破壊に対して適切な技術的および組織的対策、内部統制、情報セキュリティに関する手順を実施してきており、またこれを維持し続けます。
 
-Signature of GitHub, Inc. appears below.
+GitHub, Inc.の署名は以下にあります。
 
-Signing the Standard Contractual Clauses, Appendix 1 and Appendix 2 on behalf of the data importer
+データ輸入者を代表し、標準契約条項、添付文書1、および添付文書2に署名する
 
 ![2020年7月20日、午後2:20:29のスクリーンショット](/assets/images/help/site-policy/docusign-signature.png)
 
-Lynn Hashimoto, Head of Product & Regulatory Legal
+製品および法規制部長　リン・ハシモト
 
 GitHub, Inc.
diff --git a/translations/ja-JP/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/ja-JP/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
index 3bd56057b1..05ef9ba54b 100644
--- a/translations/ja-JP/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
+++ b/translations/ja-JP/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insights and data protection for your organization
 intro: '{% data variables.product.prodname_insights %} analyzes your {% data variables.product.prodname_ghe_server %} data. This data could include personal data of individuals in your organization who may have the right to understand how such personal data is being used.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
   - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
@@ -14,8 +13,6 @@ topics:
   - Legal
 ---
 
-For more information about the terms that govern {% data variables.product.prodname_insights %}, see your {% data variables.product.prodname_ghe_one %} subscription agreement.
-
 For the avoidance of doubt, none of the foregoing information should be considered legal advice provided by {% data variables.product.prodname_dotcom %}. You are responsible for securing your own legal analysis of the information provided herein and for your compliance with privacy and data protection laws. It is up to you whether to use {% data variables.product.prodname_insights %} to process your employees’ and users’ data, and if you do so, you are solely responsible for conducting such processing in compliance with applicable law.
 
 ### The organization’s roles and responsibilities
diff --git a/translations/ja-JP/content/github/site-policy/github-pre-release-program.md b/translations/ja-JP/content/github/site-policy/github-pre-release-program.md
index c1f5aeb3d9..827072f529 100644
--- a/translations/ja-JP/content/github/site-policy/github-pre-release-program.md
+++ b/translations/ja-JP/content/github/site-policy/github-pre-release-program.md
@@ -51,7 +51,7 @@ GitHub Pre-release Program への参加にご登録いただきありがとう
 
 ### 7. 輸出規制
 
-  米国の法律または「機密情報」を取得した地域に適用される法律によって認められる場合を除き、お客様は当社のいかなる「機密情報」も輸出および再輸出することはできません。 In particular, you aren’t allowed to export or re-export our Confidential Information into any U.S. embargoed countries, to anyone on the U.S. Treasury Department's list of Specially Designated Nationals, or to anyone on the U.S. Department of Commerce Denied Person's List or Entity List. 「Pre-release Program」に参加するか、当社の「機密情報」を受け取るかのいずれかにより、お客様はかかる国に在住しておらず、またかかるリストに掲載されていることを表明し、保証するものとします。
+  米国の法律または「機密情報」を取得した地域に適用される法律によって認められる場合を除き、お客様は当社のいかなる「機密情報」も輸出および再輸出することはできません。 特に、 米国の禁輸対象国、米国 商務省の否認命令リストに掲載されている者、または米国 財務省の特定国籍業者リストに掲載されている者に対して、当社の「機密情報」を輸出および再輸出することは認められません。 「Pre-release Program」に参加するか、当社の「機密情報」を受け取るかのいずれかにより、お客様はかかる国に在住しておらず、またかかるリストに掲載されていることを表明し、保証するものとします。
 
 ### 8. 所有権
 
@@ -59,7 +59,7 @@ GitHub Pre-release Program への参加にご登録いただきありがとう
 
 ### 9. ユーザとしての政府機関
 
-  お客様が政府機関である場合、本セクションが適用されます。  Certain of our Confidential Information may be considered “Commercial Items”, as that term is defined at 48 C.F.R. §227.7202における用語による、「商用コンピュータソフトウェア」および「商用コンピュータソフトウェアドキュメンテーション」から構成される、48 C.F.R. §12.212または 48 C.F.R. §227.7202, as applicable. 48 C.F.R. §12.212または 48 C.F.R. §227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.  GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107。
+  お客様が政府機関である場合、本セクションが適用されます。  当社の「機密情報」の中には、48 C.F.R.  §227.7202における用語による、「商用コンピュータソフトウェア」および「商用コンピュータソフトウェアドキュメンテーション」から構成される、48 C.F.R. §12.212または 48 C.F.R. §2.101において定義される「商用品目」と見なされるものがある可能性があります。 48 C.F.R. §12.212または 48 C.F.R. §227.7202-1から227.7202-4のうち該当する法律に従い、「商用コンピュータソフトウェア」および「商用コンピュータソフトウェアドキュメンテーション」は、 （a）「商用品目」としてのみ、（b）本「契約」の規約および条件に従って、その他全てのエンドユーザに付与される権利のみ米国政府のエンドユーザにライセンス付与されるものとします。  GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107。
 
 ### 10. 独自の開発
 
diff --git a/translations/ja-JP/content/github/site-policy/github-privacy-statement.md b/translations/ja-JP/content/github/site-policy/github-privacy-statement.md
index b76caba3ae..4484eef794 100644
--- a/translations/ja-JP/content/github/site-policy/github-privacy-statement.md
+++ b/translations/ja-JP/content/github/site-policy/github-privacy-statement.md
@@ -42,7 +42,7 @@ Githubではお客様の個人情報をプライバシーステートメント
 | [お客様情報についての当社の保護方法](#how-github-secures-your-information)                                  | 当社では、GitHub上のお客様の個人情報の秘密性、統合性及び可用性を保護するために合理的なすべての必要な措置を講ずるとともに、サーバーのレジリエンスを保護します。                                                                                                                                                                |
 | [GitHubのグローバルプライバシープラクティス](#githubs-global-privacy-practices)                              | We provide the same high standard of privacy protection to all our users around the world.                                                                                                                                                        |
 | [当社とお客様との連絡方法](#how-we-communicate-with-you)                                               | 当社は、お客様にemailでご連絡します。 アカウント設定または当社にご連絡いただければ、当社からお客様への方法を管理できます。                                                                                                                                                                                  |
-| [苦情の解決](#resolving-complaints)                                                             | In the unlikely event that we are unable to resolve a privacy concern quickly and thoroughly, we provide a path of dispute resolution.                                                                                                            |
+| [苦情の解決](#resolving-complaints)                                                             | 万が一、当社がプライバシーに関する懸念を迅速かつ十分に解決できない場合、当社は紛争解決の方法を提案します。                                                                                                                                                                                             |
 | [プライバシーステートメントの変更](#changes-to-our-privacy-statement)                                      | 当社は、本プライバシーステートメントの重大な変更について当該変更が有効となる30日前に、お客様に通知します。 お客様は、変更を当社のサイトポリシーリポジトリにおいて確認することもできます。                                                                                                                                                    |
 | [ライセンス](#license)                                                                          | 本プライバシーステートメントは、[Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/)の元でライセンス付与されています。                                                                                                                              |
 | [GitHubへの連絡](#contacting-github)                                                           | 当社のプライバシーステートメントに関するご質問がある場合はお気軽にお問い合わせください。                                                                                                                                                                                                      |
@@ -64,7 +64,7 @@ Githubではお客様の個人情報をプライバシーステートメント
 ##### Payment information
 有料でのアカウントにサインオンする場合や、GitHub Sponsors Programを通じて送金する場合、GitHub Marketplaceでアプリケーションを購入する場合、当社は、お客様のフルネーム、住所およびクレジットカード情報またはPayPal情報を収集します。 GitHubは、お客様のクレジットカード情報またはPaypal情報を処理または保管しませんが、第三者の支払処理者はこれを行うことにご留意ください。
 
-If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
+If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
 
 ##### Profile information
 お客様は、フルネーム、写真を含むアバター、経歴、位置情報、会社、第三者のウェブサイトへのURLなどのお客様のアカウントプロフィールの追加情報を当社に提供するかどうかを選択できます。 この情報には、ユーザの個人情報が含まれる可能性があります。 プロフィール情報は、当社のサービスを使用する他のユーザからも閲覧ができますのでご注意ください。
diff --git a/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md b/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md
index 5304057101..37aece789b 100644
--- a/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md
+++ b/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md
@@ -59,7 +59,7 @@ GitHubは、多くの開発者に当社のプラットフォームをご愛用
 
 7. **支払いと料金**
 
-  本「プログラム」への参加に関して、料金が発生する場合があります。 当社が随時更新する「プログラム利用規約」において、この料金について説明します（「プログラム料金」）。 お客様が当社に支払い情報を提供したことがある場合、本契約の一環として、提供したものと同一のクレジットカードまたはPayPalアカウントに当社が課金できることに同意するものとします。 それ以外の場合は、有効な支払いアカウント、およびその他の補足情報を提供する必要があります。 セクション8において明示的に記載している場合を除き、本「プログラム」についての支払いは返金不可です。 セクション8に従って本「契約」をお客様が解約しない限り、お客様は当社に対して、最初の支払い日と同じ日に、次の年までの「プログラム料金」を、お客様の支払いアカウントに自動的に課金する許可を与えるものとします。 すべての料金はアメリカ合衆国ドルで支払うものとし、税務当局によって課されるすべての税金、課徴金、関税はこれに含まれません（すなわち、これらすべてをお客様が負担します。 Dollars, and are exclusive of all taxes, levies, or duties imposed by taxing authorities (you’re responsible for all of those, except for taxes based on our income).
+  本「プログラム」への参加に関して、料金が発生する場合があります。 当社が随時更新する「プログラム利用規約」において、この料金について説明します（「プログラム料金」）。 お客様が当社に支払い情報を提供したことがある場合、本契約の一環として、提供したものと同一のクレジットカードまたはPayPalアカウントに当社が課金できることに同意するものとします。 それ以外の場合は、有効な支払いアカウント、およびその他の補足情報を提供する必要があります。 セクション8において明示的に記載している場合を除き、本「プログラム」についての支払いは返金不可です。 セクション8に従って本「契約」をお客様が解約しない限り、お客様は当社に対して、最初の支払い日と同じ日に、次の年までの「プログラム料金」を、お客様の支払いアカウントに自動的に課金する許可を与えるものとします。 すべての料金はアメリカ合衆国ドルで支払うものとし、税務当局によって課されるすべての税金、課徴金、関税はこれに含まれません（すなわち、これらすべてをお客様が負担します。
 
 8. **契約期間および解約**
 
@@ -85,15 +85,15 @@ GitHubは、多くの開発者に当社のプラットフォームをご愛用
 
 12. **輸出規制**
 
-  米国の法律または「機密情報」を取得した地域に適用される法律によって認められる場合を除き、お客様は当社のいかなる「機密情報」も輸出および再輸出することはできません。 In particular, you aren’t allowed to export or re-export our Confidential Information into any U.S. embargoed countries, to anyone on the U.S. Treasury Department's list of Specially Designated Nationals, or to anyone on the U.S. Department of Commerce Denied Person's List or Entity List. 本「プログラム」に参加するか、当社の「機密情報」を受け取ることにより、お客様はかかる国に在住しておらず、またかかるリストに掲載されていることを表明し、保証するものとします。
+  米国の法律または「機密情報」を取得した地域に適用される法律によって認められる場合を除き、お客様は当社のいかなる「機密情報」も輸出および再輸出することはできません。 特に、 米国の禁輸対象国、米国 商務省の否認命令リストに掲載されている者、または米国 財務省の特定国籍業者リストに掲載されている者に対して、当社の「機密情報」を輸出および再輸出することは認められません。 本「プログラム」に参加するか、当社の「機密情報」を受け取ることにより、お客様はかかる国に在住しておらず、またかかるリストに掲載されていることを表明し、保証するものとします。
 
 13. **所有権**
 
-  お客様は、GitHubとそのライセンサーが、API、「プレリリース資料」、その他すべてのGitHubの製品とサービス、それらの構成と組み合わせに関連するすべての情報とデータ、およびそれらの変更と派生物のすべての権利、権原、および利益を所有していることに同意するものとします。 You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services.
+  お客様は、GitHubとそのライセンサーが、API、「プレリリース資料」、その他すべてのGitHubの製品とサービス、それらの構成と組み合わせに関連するすべての情報とデータ、およびそれらの変更と派生物のすべての権利、権原、および利益を所有していることに同意するものとします。 お客様は、当社がAPI、「プレリリース資料」やその他GitHub製品やサービスに掲載したり、埋め込んだりした著作権その他の所有権の表示を削除、変更、隠蔽、難読化しないことに同意するものとします。
 
 14. **ユーザとしての政府機関**
 
-  お客様が政府機関である場合、本セクションが適用されます。  Certain of our Confidential Information may be considered “Commercial Items”, as that term is defined at 48 C.F.R. §227.7202における用語による、「商用コンピュータソフトウェア」および「商用コンピュータソフトウェアドキュメンテーション」から構成される、48 C.F.R. §12.212または 48 C.F.R. §227.7202, as applicable. 48 C.F.R. §12.212または 48 C.F.R. §227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.  GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107。
+  お客様が政府機関である場合、本セクションが適用されます。  当社の「機密情報」の中には、48 C.F.R.  §227.7202における用語による、「商用コンピュータソフトウェア」および「商用コンピュータソフトウェアドキュメンテーション」から構成される、48 C.F.R. §12.212または 48 C.F.R. §2.101において定義される「商用品目」と見なされるものがある可能性があります。 48 C.F.R. §12.212または 48 C.F.R. §227.7202-1から227.7202-4のうち該当する法律に従い、「商用コンピュータソフトウェア」および「商用コンピュータソフトウェアドキュメンテーション」は、 （a）「商用品目」としてのみ、（b）本「契約」の規約および条件に従って、その他全てのエンドユーザに付与される権利のみ米国政府のエンドユーザにライセンス付与されるものとします。  GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107。
 
 15. **独自の開発**
 
diff --git a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
index 94201f266a..91fdfc2f53 100644
--- a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### プライベートリポジトリ用のデータ利用について
 
-When you enable data use for your private repository, you'll be able to access the dependency graph, where you can track your repository's dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)」を参照してください。
+プライベートリポジトリのデータ利用を設定すると、依存グラフにアクセスできます。依存グラフでは、リポジトリの依存関係を追跡し、{% data variables.product.product_name %} が脆弱性のある依存関係を検出したときに {% data variables.product.prodname_dependabot_alerts %} を受け取ることができます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)」を参照してください。
 
 ### データ利用機能の有効化と無効化
 
@@ -28,4 +28,4 @@ When you enable data use for your private repository, you'll be able to access t
 
 - [{% data variables.product.prodname_dotcom %} によるユーザのデータの利用について](/articles/about-github-s-use-of-your-data)
 - [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)
-- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
+- 「[リポジトリのセキュリティおよび分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md
index 90c86b1a4e..0b10f914df 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-repository-graphs.md
@@ -12,7 +12,7 @@ topics:
   - Repositories
 ---
 
-A repository's graphs give you information on {% if currentVersion == "free-pro-team@latest" %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. 自分が管理しているリポジトリがある場合、このデータを使用すれば、リポジトリを誰が使っているのか、なぜ使っているのかをよりよく知ることができます。
+リポジトリグラフは、{% if currentVersion == "free-pro-team@latest" %}トラフィック、リポジトリに依存するプロジェクト、{% endif %}リポジトリのコントリビューターとコミット、そしてリポジトリのフォークやネットワークに関する情報を提供します。 自分が管理しているリポジトリがある場合、このデータを使用すれば、リポジトリを誰が使っているのか、なぜ使っているのかをよりよく知ることができます。
 
 {% if currentVersion == "free-pro-team@latest" %}
 
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index 1a66878f1a..455f4898a8 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -1,89 +1,76 @@
 ---
-title: About the dependency graph
-intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.'
+title: 依存関係グラフについて
+intro: 依存関係グラフ、それがサポートするエコシステム、およびリポジトリが依存するパッケージの決定方法についての詳細。
 versions:
-  free-pro-team: '*'
-  enterprise-server: '*'
+  enterprise-server: <=2.22
+topics:
+  - Repositories
 ---
 
-### Dependency graph availability
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+### 依存関係グラフの利用
+
+依存関係グラフは、サポートされているファイル形式を使用して、サポートされているパッケージエコシステムの依存関係を定義するすべてのリポジトリで利用できます。
 
 {% data reusables.repositories.enable-security-alerts %}
 
-### About the dependency graph
+### 依存関係グラフについて
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+依存関係グラフは、リポジトリに保存されているマニフェストファイルおよびロックファイルのサマリーです。 リポジトリごとに、依存関係、つまり、それが依存しているエコシステムとパッケージが表示されます。 {% data variables.product.prodname_ghe_server %} は、リポジトリに依存している依存関係、リポジトリ、およびパッケージに関する情報を計算しません。
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+サポートされているマニフェストまたはロックファイルを変更する、またはデフォルトブランチに追加するコミットを {% data variables.product.product_name %} にプッシュすると、依存関係グラフが自動的に更新されます。 サポートされているエコシステムとマニフェストファイルについては、「[サポートされているパッケージエコシステム](#supported-package-ecosystems)」を参照してください。
 
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+### 含まれる依存関係
 
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+依存関係グラフには、サポートされているエコシステムについてマニフェストおよびロックファイル、または同等のもので詳細に定義されているリポジトリの依存関係がすべて含まれています。 これは以下のものが含まれます。
 
-### Dependencies included
+- マニフェストまたはロックファイルで明示的に定義されている、直接依存関係
+- 直接依存関係の間接依存関係。推移的な依存関係、または下位の依存関係とも言う。
 
-The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
+依存関係グラフは、間接的な依存関係を識別します。
 
-- Direct dependencies, that are explicitly defined in a manifest or lock file
-- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+### 依存関係グラフの使用
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+依存関係グラフを使用する目的は、次のとおりです。
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
+- コードが依存しているリポジトリを調べます。 詳しい情報については、「[リポジトリの依存関係を調べる](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)」を参照してください。
+- リポジトリの脆弱な依存関係を表示・更新すること。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
 
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
-
-### Using the dependency graph
-
-You can use the dependency graph to:
-
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
-
-### Enabling the dependency graph
-
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
+### 依存関係グラフの有効化
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} システムで依存関係グラフを使用できない場合は、サイト管理者が依存関係グラフとセキュリティアラートを有効にできます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %}の脆弱性のある依存関係に関するセキュリティアラートの有効化](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+依存関係グラフを初めて有効化すると、サポートされているエコシステムのマニフェストおよびロックファイルがすぐに解析されます。 グラフは通常数分以内に入力されますが、多くの依存関係を持つリポジトリの場合は時間がかかる場合があります。 有効にすると、リポジトリにプッシュするたびにグラフが自動的に更新されます。
 
-### Supported package ecosystems
+### サポートされているパッケージエコシステム
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+推奨されるフォーマットでは、直接および間接の依存関係すべてに使用されるバージョンを明示的に定義しています。 これらのフォーマットを使用したほうが、依存関係グラフは正確になります。 現在のビルドのセットアップも反映され、直接と間接のどちらの依存関係でも依存関係グラフで脆弱性をレポートできます。
 
-| Package manager | Languages | Recommended formats | All supported formats |
-| --- | --- | --- | ---|
-| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| 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.lock`, `setup.py`* |
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+以下にリストされているエコシステムは、依存関係グラフと{% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}でサポートされています。
+
+| パッケージマネージャー  | 言語                     | 推奨されるフォーマット                                        | サポートされているすべてのフォーマット                                                  |
+| ------------ | ---------------------- | -------------------------------------------------- | -------------------------------------------------------------------- |
+| Composer     | PHP                    | `composer.lock`                                    | `composer.json`、`composer.lock`                                      |
+| `dotnet` CLI | .NET 言語 (C#、C++、F#、VB) | `.csproj`、`.vbproj`、`.nuspec`、`.vcxproj`、`.fsproj` | `.csproj`、`.vbproj`、`.nuspec`、`.vcxproj`、`.fsproj`、`packages.config` |
+| 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`*           |
+| RubyGems     | Ruby                   | `Gemfile.lock`                                     | `Gemfile.lock`、`Gemfile`、`*.gemspec`                                 |
+| Yarn         | JavaScript             | `yarn.lock`                                        | `package.json`、`yarn.lock`                                           |
 
 {% note %}
 
-**Note:** 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.
+**メモ:** `setup.py` ファイルで Python の依存関係をリストする場合、プロジェクトの依存関係すべてを解析してリストすることはできない場合があります。
 
 {% endnote %}
 
-### Further reading
+### 参考リンク
 
-- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- Wikipedia の「[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)」
+- [リポジトリの依存関係を見る](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
index 6714b4ca41..1095f31197 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
@@ -1,6 +1,6 @@
 ---
 title: 基本的なリポジトリデータへのアクセス
-intro: 'You can view basic information about a repository, such as the repository''s activity{% if currentVersion == "free-pro-team@latest" %}, traffic,{% endif %} and contribution activity.'
+intro: 'リポジトリのアクティビティ{% if currentVersion == "free-pro-team@latest" %}、トラフィック{% endif %}、コントリビューションのアクティビティなど、リポジトリについての基本情報を見ることができます。'
 mapTopic: true
 redirect_from:
   - /articles/accessing-basic-repository-data
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index 20ae2cf4c4..e258c503cd 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -1,37 +1,28 @@
 ---
-title: Exploring the dependencies of a repository
-intro: 'Using the dependency graph, you can see the packages your project depends on{% if currentVersion == "free-pro-team@latest" %} and the repositories that depend on it{% endif %}. また、その依存関係で脆弱性が検出されると、それも表示されます。'
+title: リポジトリの依存関係を調べる
+intro: '依存関係グラフを使用すると、プロジェクトが依存しているパッケージ{% if currentVersion == "free-pro-team@latest" %}とそれに依存しているリポジトリを確認できます{% endif %}。 また、その依存関係で脆弱性が検出されると、それも表示されます。'
 versions:
   enterprise-server: <=2.22
 topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### 依存関係グラフの表示
 
 {% data reusables.repositories.enable-security-alerts %}
 
-The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+依存関係グラフには、リポジトリの依存関係が表示されます。 依存関係の検出とサポートされているエコシステムについては、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. オプションとして、[Dependency graph] で [**Dependents**] をクリックします。 ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### 依存関係ビュー
 
-{% if currentVersion == "free-pro-team@latest" %}
-依存関係はエコシステム別にグループ化されます。 依存関係を拡張すると、その依存関係を表示できます。 For dependencies on public repositories hosted on
-{% data variables.product.product_name %}, you can also click a dependency to view the repository. Dependencies on private repositories, private packages, or unrecognized files are shown in plain text.
-
-If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}.
-
-![依存関係グラフ](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
-Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to
+Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. リポジトリで脆弱性が検出された場合、次にアクセスできるユーザのビューの上部に脆弱性が表示されます
 {% data variables.product.prodname_dependabot_alerts %}について受ける方法は、カスタマイズできます。
 
 ![依存関係グラフ](/assets/images/help/graphs/dependencies_graph_server.png)
@@ -45,7 +36,7 @@ Any direct and indirect dependencies that are specified in the repository's mani
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
+Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. リポジトリで脆弱性が検出された場合、セキュリティアラートにアクセスできるユーザのビューの上部に脆弱性が表示されます。
 
 ![依存関係グラフ](/assets/images/help/graphs/dependencies_graph_server.png)
 
@@ -57,59 +48,8 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### 依存ビュー
-
-パブリックリポジトリの場合、他のリポジトリによってどう使用されているかが、依存ビューに表示されます。 パッケージマネージャーにライブラリを含むリポジトリのみを表示するには、依存リポジトリのリストのすぐ上にある「**NUMBER Packages**」をクリックします。 依存の数は概数であり、リストされている依存と一致しないことがあります。
-
-![依存グラフ](/assets/images/help/graphs/dependents_graph.png)
-
-### プライベートリポジトリの依存関係グラフを有効化および無効化する
-
-リポジトリ管理者は、プライベートリポジトリに対して依存関係グラフを有効または無効にすることができます。
-
-You can also enable or disable the dependency graph for all repositories owned by your user account or organization. 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)」または「[Organization のセキュリティおよび分析設定を管理する](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)」を参照してください。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. リポジトリ データへの読み取りアクセスを {% data variables.product.product_name %} に許可して依存関係グラフを有効にすることに関するメッセージを読んだうえで、[Dependency Graph] の隣にある [**Enable**] をクリックします。 ![依存関係グラフの [Enable] ボタン](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-[Security & analysis] タブで [Dependency Graph] の隣にある [**Disable**] をクリックすれば、依存関係グラフはいつでも無効にできます。
-
-### Changing the "Used by" package
-
-If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
-
-The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
-
-!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png)
-
-Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
-
-The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### 依存関係グラフのトラブルシューティング
 
 依存関係グラフが空の場合は、依存関係を含むファイルに問題があるかもしれません。 ファイルがファイルタイプに合わせて適切にフォーマットされているかをチェックしてください。
 
-{% if currentVersion == "free-pro-team@latest" %}
-ファイルのフォーマットが正しい場合は、大きさをチェックします。 The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a
-{% data variables.product.prodname_enterprise %} user. デフォルトでは、最大 20 個のマニフェストまたはロックファイルが処理されるので、リポジトリのサブディレクトリで依存関係を小さいファイルに分割することができます。{% endif %}
-
 マニフェストまたはロックファイルが処理されない場合、その依存関係は依存関係グラフから省略され、脆弱な依存関係はチェックされなくなります。
-
-### 参考リンク
-
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- [Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)
-- [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)
-- [{% data variables.product.product_name %} によるデータの利用方法と保護方法を理解する](/github/understanding-how-github-uses-and-protects-your-data)
-{% endif %}
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
index d1bb2b005e..6d8f24e557 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
@@ -1,6 +1,6 @@
 ---
 title: リポジトリ間の接続を理解する
-intro: 'You can better understand the connections that exist between repositories by viewing a repository''s network{% if currentVersion == "free-pro-team@latest" %}, projects that depend on the repository,{% endif %} and its forks.'
+intro: 'リポジトリのネットワーク{% if currentVersion == "free-pro-team@latest" %}、リポジトリに依存するプロジェクト{% endif %}やそのフォークを確認することで、リポジトリ間のつながりをより深く理解できます。'
 mapTopic: true
 redirect_from:
   - /articles/understanding-connections-between-repositories
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
index 5c156eb7df..087c116d48 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
@@ -1,6 +1,6 @@
 ---
 title: プロジェクトのコントリビューターを表示する
-intro: 'You can see who contributed commits to a repository{% if currentVersion == "free-pro-team@latest" %} and its dependencies{% endif %}.'
+intro: 'リポジトリへのコミットにコントリビュートした人{% if currentVersion == "free-pro-team@latest" %}とその依存関係{% endif %}を表示できます。'
 redirect_from:
   - /articles/i-don-t-see-myself-in-the-contributions-graph/
   - /articles/viewing-contribution-activity-in-a-repository/
@@ -16,10 +16,10 @@ topics:
 
 ### コントリビューターについて
 
-You can view the top 100 contributors to a repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, including commit co-authors,{% endif %} in the contributors graph. マージコミットと空のコミットは、このグラフでコントリビューションとして数えられません。
+コントリビューターグラフで{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}、コミットの共作者を含めて{% endif %}、リポジトリに貢献した上位 100 人のコントリビューターを表示できます。 マージコミットと空のコミットは、このグラフでコントリビューションとして数えられません。
 
 {% if currentVersion == "free-pro-team@latest" %}
-You can also see a list of people who have contributed to the project's Python dependencies. この、コミュニティコントリビューターのリストを表示するには、`https://github.com/REPO-OWNER/REPO-NAME/community_contributors` にアクセスしてください。
+プロジェクトの Python 依存関係に貢献した人のリストも表示されます。 この、コミュニティコントリビューターのリストを表示するには、`https://github.com/REPO-OWNER/REPO-NAME/community_contributors` にアクセスしてください。
 {% endif %}
 
 ### コントリビューターグラフにアクセスする
@@ -34,7 +34,7 @@ You can also see a list of people who have contributed to the project's Python d
 リポジトリのコントリビュータグラフにあなたが表示されない場合、以下の理由が考えられます:
 - 上位 100 人に入っていない。
 - コミットがデフォルトブランチにマージされていない。
-- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}.
+- コミットの作成に使用したメールアドレスが、{% data variables.product.product_name %} のアカウントに接続されていない。
 
 {% tip %}
 
@@ -44,4 +44,4 @@ You can also see a list of people who have contributed to the project's Python d
 
 リポジトリ内のあなたのコミットがすべてデフォルト以外のブランチにある場合、コントリビュータグラフには表示されません。 たとえば、`gh-pages`ブランチに対して行われたコミットは、`gh-pages`がリポジトリのデフォルトのブランチでない限り、グラフに含まれません。 コミットをデフォルトブランチにマージするため、プルリクエストを作成できます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests)を参照してください。
 
-If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}" and "[Adding an email address to your {% data variables.product.product_name %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}."
+コミットの作成に使用したメールアドレスが {% data variables.product.product_name %} のアカウントに接続されていない場合、コミットはアカウントにリンクされず、コントリビュータグラフに表示されません。 詳しい情報については、「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}」および「[{% data variables.product.product_name %} アカウントにメールアドレスを追加する](/articles/adding-an-email-address-to-your-github-account){% endif %}」を参照してください。
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-the-dependencies-of-a-repository.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-the-dependencies-of-a-repository.md
index 087cfb8870..7ca5195bc4 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-the-dependencies-of-a-repository.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-the-dependencies-of-a-repository.md
@@ -1,13 +1,13 @@
 ---
-title: Viewing the dependencies of a repository
-intro: You can use the dependency graph to explore the code your repository depends on.
+title: リポジトリの依存関係を表示する
+intro: 依存関係グラフを使用して、リポジトリが依存するコードを調べることができます。
 versions:
   free-pro-team: '*'
   enterprise-server: '>=3.0'
 ---
 
-Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
+ほとんどすべてのソフトウェアは、他の開発者 (サプライチェーンとして知られる) によって開発および保守されているコードに依存しています。 たとえば、ユーティリティ、ライブラリ、フレームワークなどです。 これらの依存関係はコードの不可欠な部分であり、それらのバグや脆弱性がコードに影響を与える可能性があります。 これらの依存関係をレビューして維持することが重要です。
 
-The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)."
+依存関係グラフは、リポジトリの依存関係を視覚化して調査するために最適な方法を提供しています。 詳しい情報については、「[依存関係グラフについて](/code-security/supply-chain-security/about-the-dependency-graph)」および「[リポジトリの依存関係を調べる](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) 」を参照してください。
 
-You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
+依存関係の 1 つにセキュリティの脆弱性が見つかった場合は、{% data variables.product.company_short %} が自動的に警告するようにリポジトリを設定することもできます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md
index 204dba9aeb..f0ceb0794b 100644
--- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md
+++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md
@@ -1,7 +1,7 @@
 ---
 title: リポジトリへのトラフィックを表示する
 intro: フルクローン (フェッチではない)、過去 14 日間の訪問者、参照サイト、トラフィックグラフの人気コンテンツなど、リポジトリへのプッシュアクセスを持つユーザは誰でもそのトラフィックを表示できます。
-product: 'This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{% data variables.product.prodname_dotcom %}''s products](/articles/github-s-products)."{% endif %}'
+product: 'このリポジトリインサイトグラフは、Organization の場合 {% data variables.product.prodname_free_user %} と {% data variables.product.prodname_free_team %} のパブリックリポジトリで、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} のパブリックリポジトリとプライベートリポジトリで利用できます。{% if currentVersion == "free-pro-team@latest" %}詳しい情報については、「[リポジトリグラフについて](/articles/about-repository-graphs)」および「{% data variables.product.prodname_dotcom %} の製品](/articles/github-s-products)」を参照してください。{% endif %}'
 redirect_from:
   - /articles/viewing-traffic-to-a-repository
 versions:
diff --git a/translations/ja-JP/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/ja-JP/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index 653fda64f7..e73801759e 100644
--- a/translations/ja-JP/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Enterprise Cloud の GitHub Premium Support について
-intro: '{% data variables.contact.premium_support %} は、{% data variables.product.prodname_ghe_cloud %} および {% data variables.product.prodname_ghe_one %} のお客様のための有料の補足的なサポートです。'
+intro: '{% data variables.contact.premium_support %} は、{% data variables.product.prodname_ghe_cloud %} のお客様のための有料の補足的なサポートです。'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
@@ -56,7 +56,7 @@ topics:
 
 ### サポートチケットの解決とクローズ
 
-{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, or workaround instructions,
+{% data variables.contact.premium_support %} は、説明、推奨対応、使用方法、または回避策を提供した後、解決済みのチケットを検討する場合があります。
 
 カスタムあるいはサポートされていないプラグイン、モジュール、カスタムコードを使っている場合、{% data variables.contact.premium_support %} は問題の解決を試みるに当たってサポートされていないプラグイン、モジュール、コードの削除をお願いすることがあります。 サポートされていないプラグイン、モジュール、カスタムコードが削除されたことで問題が修正された場合、{% data variables.contact.premium_support %}はチケットが解決されたと見なすことがあります。
 
diff --git a/translations/ja-JP/content/github/working-with-github-support/about-github-support.md b/translations/ja-JP/content/github/working-with-github-support/about-github-support.md
index 4bf6999689..88fa7c0af2 100644
--- a/translations/ja-JP/content/github/working-with-github-support/about-github-support.md
+++ b/translations/ja-JP/content/github/working-with-github-support/about-github-support.md
@@ -25,9 +25,9 @@ topics:
 
 ### {% data variables.contact.github_support %}への連絡
 
-You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}.
+{% data variables.contact.community_support_forum %} を使用して、トピックの閲覧、質問、ソリューションの共有、{% data variables.contact.community_support %} との直接やり取りができます。
 
-To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}.
+アカウント、セキュリティ、不正使用の問題の報告、または有料アカウントのサポートを受けるには、{% data variables.contact.contact_support_portal %}にアクセスしてください。 {% data variables.product.prodname_dotcom_the_website %} にユーザアカウントを持たない {% data variables.product.prodname_ghe_server %} の管理者の場合は、{% data variables.contact.contact_enterprise_portal %} にアクセスしてください。
 
 ### プライベートリポジトリへの{% data variables.contact.github_support %}の一時的なアクセスの許可
 
diff --git a/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md b/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md
index 1c271b57e3..fa3b3b2520 100644
--- a/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md
+++ b/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md
@@ -11,7 +11,7 @@ topics:
 
 自分のアカウントで有料の {% data variables.product.prodname_dotcom %} 製品を使用している場合は、{% data variables.contact.github_support %} に直接問い合わせることができます。 ユーザアカウントまたは Organization の {% data variables.product.prodname_free_user %} を使用している場合は、{% data variables.contact.contact_support %} に連絡してアカウント、セキュリティ、悪用の問題を報告できます。 詳しい情報については、「[GitHub Supportについて](/github/working-with-github-support/about-github-support)」を参照してください。
 
-If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)."
+Enterprise アカウントをお持ちでない場合は、{% data variables.contact.enterprise_portal %} を使用してチケットを送信してください。 Enterprise アカウントの詳細については、「[Enterprise アカウントについて](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)」を参照してください。
 
 ### {% data variables.contact.support_portal %} を使ってチケットをサブミットする
 
diff --git a/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md
index d51d7aee91..d7b5596b6a 100644
--- a/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/ja-JP/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ versions:
 
 ### Issue およびプルリクエスト
 
-{% data variables.product.product_name %} 上の会話の中では、Issue やプルリクエストへの参照は自動的に短縮リンクに変換されます。 詳細は「[{% data variables.product.prodname_dotcom %} 上の会話について](/articles/about-conversations-on-github)」を参照してください。
+{% data variables.product.product_name %} 上の会話の中では、Issue やプルリクエストへの参照は自動的に短縮リンクに変換されます。
 
 {% note %}
 
diff --git a/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index 64a8f8a43b..b57e4d9878 100644
--- a/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/ja-JP/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -23,7 +23,7 @@ versions:
 
 ### スタイル付きテキスト
 
-太字、斜体、取り消し線で強調を示すことができます。
+コメントフィールドと `.md` ファイルでは、太字、斜体、または取り消し線のテキストで強調を示すことができます。
 
 | スタイル          | 構文                 | キーボードショートカット        | サンプル                      | 出力                      |
 | ------------- | ------------------ | ------------------- | ------------------------- | ----------------------- |
@@ -171,7 +171,7 @@ git commit
 
 ### 人や Team のメンション
 
-{% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、`@` に加えてユーザ名もしくは Team 名を入力することでメンションできます。 This will trigger a notification and bring their attention to the conversation. コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 For more information about notifications, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
+{% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、`@` に加えてユーザ名もしくは Team 名を入力することでメンションできます。 これにより通知がトリガーされ、会話に注意が向けられます。 コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 通知の詳細は、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。
 
 `@github/support これらのアップデートについてどう思いますか？`
 
@@ -199,12 +199,16 @@ git commit
 
 ![コンテンツの添付](/assets/images/github-apps/content_reference_attachment.png)
 
-To see content attachments, you must have a {% data variables.product.prodname_github_app %} that uses the Content Attachments API installed on the repository.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Installing an app in your personal account](/articles/installing-an-app-in-your-personal-account)" and "[Installing an app in your organization](/articles/installing-an-app-in-your-organization)."{% endif %}
+コンテンツの添付を見るには、リポジトリにインストールされた Content Attachments API を使う {% data variables.product.prodname_github_app %} が必要です。{% if currentVersion == "free-pro-team@latest" %} 詳しい情報については、「[個人アカウントでアプリケーションをインストールする](/articles/installing-an-app-in-your-personal-account)」および「[Organization でアプリケーションをインストールする](/articles/installing-an-app-in-your-organization)」を参照してください。{% endif %}
 
 コンテンツの添付は、Markdown のリンクの一部になっている URL には表示されません。
 
 コンテンツの添付を利用する {% data variables.product.prodname_github_app %} の構築に関する詳しい情報については、「[コンテンツの添付を使用する](/apps/using-content-attachments)」を参照してください。
 
+### アセットをアップロードする
+
+ドラッグアンドドロップ、ファイルブラウザから選択、または貼り付けることにより、画像などのアセットをアップロードできます。 アセットをリポジトリ内の Issue、プルリクエスト、コメント、および `.md` ファイルにアップロードできます。
+
 ### 絵文字の利用
 
 `:EMOJICODE:` を入力して、書き込みに絵文字を追加できます。
@@ -215,7 +219,7 @@ To see content attachments, you must have a {% data variables.product.prodname_g
 
 `:` を入力すると、絵文字のサジェストリストが表示されます。 このリストは、入力を進めるにつれて絞り込まれていくので、探している絵文字が見つかったら、**Tab** または **Enter** を押すと、ハイライトされているものが入力されます。
 
-For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md).
+利用可能な絵文字とコードの完全なリストについては、[絵文字チートシート](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md)を参照してください。
 
 ### パラグラフ
 
diff --git a/translations/ja-JP/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/ja-JP/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index 41b5602756..d41e2c7f66 100644
--- a/translations/ja-JP/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/ja-JP/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### 構文の強調表示
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 言語識別子を追加して、コードブロックの構文を強調表示することができます。
 
diff --git a/translations/ja-JP/content/github/writing-on-github/creating-gists.md b/translations/ja-JP/content/github/writing-on-github/creating-gists.md
index 3a82f63fba..9dee74c3d5 100644
--- a/translations/ja-JP/content/github/writing-on-github/creating-gists.md
+++ b/translations/ja-JP/content/github/writing-on-github/creating-gists.md
@@ -1,6 +1,6 @@
 ---
 title: Gist の作成
-intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.'
+intro: '{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %}とシークレットの 2 種類の Gist を作成できます。 アイデアを {% if currentVersion == "github-ae@latest" %}Enterprise のメンバー{% else %}世界{% endif %}と共有する準備ができている場合は、{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %}の Gist を作成します。そうでない場合は、シークレットの Gist を作成します。'
 redirect_from:
   - /articles/about-gists/
   - /articles/cannot-delete-an-anonymous-gist/
@@ -14,11 +14,11 @@ versions:
 
 ### Gistについて
 
-すべての Gist は Git のリポジトリであり、フォークしたりクローンしたりできます。 {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}.
+すべての Gist は Git のリポジトリであり、フォークしたりクローンしたりできます。 {% if currentVersion != "github-ae@latest" %} Gist を作成する際 {% else %}{% endif %}{% data variables.product.product_name %} にサインインしている場合、その Gist は自分のアカウントに関連付けられ、{% data variables.gists.gist_homepage %} に移動すると自分の Gist リストに表示されます。
 
-Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. それらのGistは検索もできるので、他の人々に自分の作業を探して見てもらうために使うこともできます。
+Gist は、{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %}またはシークレットにすることができます。 {% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %} の Gist が {% data variables.gists.discover_url %} に表示され、{% if currentVersion == "github-ae@latest" %}Enterprise メンバー{% else %}ユーザ{% endif %} は作成された新しい Gist を参照できます。 それらのGistは検索もできるので、他の人々に自分の作業を探して見てもらうために使うこともできます。
 
-Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. 好奇心の強い眼から自分のコードを守っておきたいなら、[プライベートリポジトリを作成](/articles/creating-a-new-repository)するとよいでしょう。
+シークレット Gist は {% data variables.gists.discover_url %} に表示されず、検索できません。 シークレット Gist はプライベートではありません。 シークレット Gist の URL を{% if currentVersion == "github-ae@latest" %}別の Enterprise メンバー{% else %}友人{% endif %}に送信すると、メンバーはそれを確認することができます。 ただし、{% if currentVersion == "github-ae@latest" %}他の Enterprise メンバー{% else %}知らない人{% endif %}が URL を発見した場合、そのメンバーもあなたの Gist を確認できます。 好奇心の強い眼から自分のコードを守っておきたいなら、[プライベートリポジトリを作成](/articles/creating-a-new-repository)するとよいでしょう。
 
 {% data reusables.gist.cannot-convert-public-gists-to-secret %}
 
@@ -33,15 +33,15 @@ Secret gists don't show up in {% data variables.gists.discover_url %} and are no
 通知は以下の場合に送られます:
 - あなたが Gist の作者である場合。
 - 誰かがあなたを Gist 中でメンションした場合。
-- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
+- いずれかの Gist の上部で [** Subscribe**] をクリックして、Gist をサブスクライブした場合。
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-You can pin gists to your profile so other people can see them easily. 詳しい情報については、「[プロフィールにアイテムをピン止めする](/articles/pinning-items-to-your-profile)」を参照してください。
+Gist をプロフィールにピン止めして、他のユーザが簡単に見ることができるようにすることができます。 詳しい情報については、「[プロフィールにアイテムをピン止めする](/articles/pinning-items-to-your-profile)」を参照してください。
 
 {% endif %}
 
-You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. こうすると、すべての Gist が作成時刻または更新時刻でソートされて表示されるページに行きます。 また、Gist は {% data variables.gists.gist_search_url %} で言語ごとに検索できます。 Gist 検索は[コード検索](/articles/searching-code)と同じ検索構文を使います。
+{% data variables.gists.gist_homepage %} に移動し、[**All Gists**] をクリックすると、他の人が作成した{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %} Gist を見つけることができます。 こうすると、すべての Gist が作成時刻または更新時刻でソートされて表示されるページに行きます。 また、Gist は {% data variables.gists.gist_search_url %} で言語ごとに検索できます。 Gist 検索は[コード検索](/articles/searching-code)と同じ検索構文を使います。
 
 Gist は Git リポジトリであるため、完全なコミット履歴を diff とともに表示させることができます。 Gist はフォークしたりクローンしたりすることもできます。 詳細は「[Gist のフォークおよびクローン](/articles/forking-and-cloning-gists)」を参照してください。
 
@@ -55,14 +55,14 @@ Gist は GeoJSON ファイルのマッピングをサポートしています。
 
 ### Gist の作成
 
-Follow the steps below to create a gist.
+以下のステップに従って、Gist を作成します。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 {% note %}
 
-You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation.
+{% data variables.product.prodname_cli %} を使用して Gist を作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh gist create`](https://cli.github.com/manual/gh_gist_create)」を参照してください。
 
-Alternatively, you can drag and drop a text file from your desktop directly into the editor.
+または、デスクトップからエディタにテキストファイルを直接ドラッグアンドドロップすることもできます。
 
 {% endnote %}
 {% endif %}
@@ -71,8 +71,8 @@ Alternatively, you can drag and drop a text file from your desktop directly into
 2. {% data variables.gists.gist_homepage %}に移動します。
 3. Gist の名前と説明 (任意) を入力します。 ![Gist の名前と説明](/assets/images/help/gist/gist_name_description.png)
 
-4. Type the text of your gist into the gist text box. ![Gist テキストボックス](/assets/images/help/gist/gist_text_box.png)
+4. Gist のテキストを Gist テキストボックスに入力します。 ![Gist テキストボックス](/assets/images/help/gist/gist_text_box.png)
 
-5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
+5. 必要に応じて、{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %} Gist を作成するには、{% octicon "triangle-down" aria-label="The downwards triangle icon" %} をクリックしてから、[**Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**] をクリックします。 ![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
 
-6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png)
+6. [**Create secret Gist**] または [**Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**] をクリックします。 ![新しい Gist を作成するボタン](/assets/images/help/gist/create-secret-gist-button.png)
diff --git a/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md b/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md
index c396d28129..93ab04465b 100644
--- a/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md
+++ b/translations/ja-JP/content/github/writing-on-github/forking-and-cloning-gists.md
@@ -11,7 +11,7 @@ versions:
 
 ### Gist をフォークする
 
-Each gist indicates which forks have activity, making it easy to find interesting changes from others.
+各 Gist はどのフォークにアクティビティがあるのかを示すため、他のユーザによる興味深い変更を簡単に確認できます。
 
 ![Gist フォーク](/assets/images/help/gist/gist_forks.png)
 
diff --git a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
index e8961b6277..8330c985ff 100644
--- a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ Return type fields:
 
 ## 検索
 
-Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see ["Queries](/graphql/reference/queries#searchresultitemconnection)."
+Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/ja-JP/content/graphql/overview/breaking-changes.md b/translations/ja-JP/content/graphql/overview/breaking-changes.md
index ad5c3aded3..a7115aa75a 100644
--- a/translations/ja-JP/content/graphql/overview/breaking-changes.md
+++ b/translations/ja-JP/content/graphql/overview/breaking-changes.md
@@ -27,7 +27,7 @@ topics:
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}破壊的{% else %}危険{% endif %}</span>変更が<code>{{ change.location }}</code>に対して行われます。
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}破壊的{% else %}危険{% endif %}</span>変更が<code>{{ change.location }}</code>に対して行われます。
 
 <p><b>説明：</b>{{ change.description }}</p>
 
diff --git a/translations/ja-JP/content/graphql/overview/explorer.md b/translations/ja-JP/content/graphql/overview/explorer.md
index b4d07c0939..1d2d21729a 100644
--- a/translations/ja-JP/content/graphql/overview/explorer.md
+++ b/translations/ja-JP/content/graphql/overview/explorer.md
@@ -9,6 +9,6 @@ versions:
   github-ae: '*'
 layout: graphql-explorer
 topics:
-  - api
+  - API
 ---
 
diff --git a/translations/ja-JP/content/graphql/reference/input-objects.md b/translations/ja-JP/content/graphql/reference/input-objects.md
index 14a741904f..747371e5d2 100644
--- a/translations/ja-JP/content/graphql/reference/input-objects.md
+++ b/translations/ja-JP/content/graphql/reference/input-objects.md
@@ -19,6 +19,5 @@ topics:
 
 詳しい情報については「[ミューテーションについて](/graphql/guides/forming-calls-with-graphql#about-mutations)」を参照してください。
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index 0aa827fbb7..4bb49c421d 100644
--- a/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: GitHub Insightsで利用できるメトリクス
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %}には、チームのソフトウェアデリバリのプロセスを可視化してくれる様々なメトリクスが含まれています。'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index 260f72b858..25392876c7 100644
--- a/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub EnterpriseとGitHub Insights間のアクセス
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 807805a99b..9d47067f3f 100644
--- a/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/ja-JP/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: 主要なメトリクスとレポートの表示
 intro: データを通じてソフトウェアのデリバリのプロセスを理解し、改善できるよう、主要なメトリクスとレポートの表示とフィルタリングができます。
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index 0dddb1dd57..b41b425532 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insightsのデータについて
 intro: '{% data variables.product.prodname_insights %}のメトリクスに含まれるデータは、高度にカスタマイズできます。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index 1209fddf33..18d90cb3cf 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insightsについて
 intro: '{% data variables.product.prodname_insights %}は、エンジニアリングチームがソフトウェアデリバリのプロセスを理解し、改善することを支援するメトリクスと分析レポートを提供します。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index 68084a3968..71f2f27ab6 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub InsightsとGitHub Enterprise間のリンクの有効化
 intro: 'ユーザが{% data variables.product.prodname_ghe_server %}から{% data variables.product.prodname_insights %}へアクセスできるようにするリンクを有効化できます。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index d58fc508ba..b59015481e 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insightsのインストール
 intro: '{% data variables.product.prodname_insights %}をインストールし、そのスタンドアローンアプリケーションを{% data variables.product.prodname_ghe_server %}に接続できます。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
@@ -16,7 +15,7 @@ versions:
 - アプリケーションサーバーに依存関係をインストールしなければなりません。
   - [Docker](https://docs.docker.com/install/) 1.13.0+
   - [Docker Compose](https://docs.docker.com/compose/install/) v1.17.0+
-  - [netcat](http://netcat.sourceforge.net/), available via apt for [Debian](https://packages.debian.org/search?keywords=netcat) and [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names)
+  - [netcat](http://netcat.sourceforge.net/)、[Debian](https://packages.debian.org/search?keywords=netcat) および [Ubuntu](https://packages.ubuntu.com/search?keywords=netcat&searchon=names) 用の apt 経由で入手可能
 
   {% note %}
 
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-goals.md
index 8130654777..42325ed0d4 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: 目標の管理
 intro: 目標を使って、主要なメトリクスについてターゲットを設定し、それらのターゲットに到達する成功を計測できます。
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index dd022dbffb..9c6e4936ca 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insightsの権限管理
 intro: '{% data variables.product.prodname_insights %}のユーザ権限を更新できます。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index 8f25ddeeea..308ee7faaa 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insightsのシステム概要
 intro: '{% data variables.product.prodname_insights %}は、{% data variables.product.prodname_enterprise %}とインターフェースするスタンドアローンアプリケーションです。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index 6b4494a4d9..ed10b78947 100644
--- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insightsのアップデート
 intro: '{% data variables.product.prodname_insights %}を最新バージョンにアップデートし、改善やバグフィックスの恩恵を受けることができます。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index ac8c481ae8..6c696dd84f 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md
index b036faee4a..d6b6d76d91 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
 {% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index 353719964c..ea7a1525bc 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -26,9 +26,8 @@ Enterprise アカウントで Organization に対して許可される IP アド
 
 ### 許可 IP アドレスを追加する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ Enterprise アカウントで Organization に対して許可される IP アド
 
 ### 許可 IP アドレスを有効化する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. [IP allow list] で、「**Enable IP allow list**」を選択します。 ![IP アドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. [**Save**] をクリックします。
 
 ### 許可 IP アドレスを編集する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ Enterprise アカウントで Organization に対して許可される IP アド
 
 ### 許可 IP アドレスを削除する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index f47ce1f8e1..deba14979e 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### セキュリティと分析の設定を表示する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 表示されるページでは、Organization 内のリポジトリのすべてのセキュリティおよび分析機能を有効化または無効化にできます。
@@ -50,33 +49,38 @@ topics:
 
 1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
 2. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_GH_advanced_security %} のライセンスにシートがない場合、「{% data variables.product.prodname_GH_advanced_security %}」の制御は無効になります。{% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![新規のリポジトリの [Enable by default] オプション](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![機能 を無効または有効にするボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Organization 内の適格なすべてのリポジトリの機能を有効化するボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![Organization 内の適格なすべてのリポジトリの機能を有効化するボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -85,11 +89,14 @@ topics:
 
 1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
 2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -122,7 +129,7 @@ topics:
 [Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能へのアクセスを管理できます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 ただし、Organization の [Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にすることもできます。
 
 1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
-1. {% data variables.product.prodname_GH_advanced_security %} が有効になっている Organization 内のすべてのリポジトリのリストを表示するには、「{% data variables.product.prodname_GH_advanced_security %} リポジトリ」セクションまでスクロールします。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) この表は、各リポジトリの一意のコミッターの数を示しています。 これは、{% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除することによりライセンスで解放できるシートの数です。 ライセンスのサイズは、Organization レベルのライセンスに対して表示されます。 詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}のライセンスについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)」を参照してください。
+1. {% data variables.product.prodname_GH_advanced_security %} が有効になっている Organization 内のすべてのリポジトリのリストを表示するには、「{% data variables.product.prodname_GH_advanced_security %} リポジトリ」セクションまでスクロールします。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) この表は、各リポジトリの一意のコミッターの数を示しています。 これは、{% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除することによりライセンスで解放できるシートの数です。 {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. リポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除し、リポジトリ固有のコミッターが使用するシートを解放するには、隣接する {% octicon "x" aria-label="X symbol" %} をクリックします。
 1. 確認ダイアログで、[**Remove repository**] をクリックして、{% data variables.product.prodname_GH_advanced_security %} の機能へのアクセスを削除します。
 
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index 4168bde26f..4f4998d6cf 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ Enterprise で Organization の 2 要素認証を必須にすることもでき
 
 ### Organization で 2 要素認証を要求する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..3ee627cd4d
--- /dev/null
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### メールの制限について
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. 外部コラボレーターに関する詳しい情報については「[Organization の権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)」を参照してください。
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index 43790c769c..4efeb54377 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 Audit log には、過去 90 日以内に Organization に影響を与えたアクティビティによってトリガーされたイベントが一覧表示されます。 Organization の Audit log にアクセスできるのはオーナーのみです。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
 
 ### Audit log を検索する
@@ -36,6 +35,7 @@ Audit log には、過去 90 日以内に Organization に影響を与えたア
 | [`アカウント`](#account-category-actions)                                                                                                                                                                                                                                                                                                                       | Organization アカウントに関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                                                                 |
 | [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                                                                                                                                                     | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリのコントリビューターのクレジットに関連するすべてのアクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。                                                                        |
 | [`支払い`](#billing-category-actions)                                                                                                                                                                                                                                                                                                                         | Organization の支払いに関連するすべてのアクティビティが対象です。                                                                                                                                                                                                                                                                                                                  |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                                                                                               | Contains all activities related to your organization's codespaces.                                                                                                                                                                                                                                                                                       |
 | [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                                                                                                 | 既存のリポジトリ内の {% data variables.product.prodname_dependabot %} アラートの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。                                                                                                                   |
 | [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                                                                                                                                             | Organization 内に作成された新しいリポジトリ内の {% data variables.product.prodname_dependabot %} アラートの Organization レベルの設定アクティビティが対象です。                                                                                                                                                                                                                                   |
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                                                                                             | 既存のリポジトリ内の {% data variables.product.prodname_dependabot_security_updates %} の Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。                                                  |
@@ -191,6 +191,20 @@ Audit log にイベントとして記録される最も一般的なアクショ
 | `change_billing_type` | Organization が[{% data variables.product.prodname_dotcom %} の支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 |
 | `change_email`        | Organization の[支払い請求先メール アドレス](/articles/setting-your-billing-email)が変わるときにトリガーされます。                                               |
 
+#### `codespaces` カテゴリアクション
+
+| アクション                        | 説明                                                                                                                                                                                                                                             |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                     | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                   |
+| `resume`                     | Triggered when a user resumes a suspended codespace.                                                                                                                                                                                           |
+| `delete`                     | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                   |
+| `create_an_org_secret`       | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)  |
+| `update_an_org_secret`       | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `remove_an_org_secret`       | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+
+
+
 #### `dependabot_alerts` カテゴリアクション
 
 | アクション     | 説明                                                                                                                                                                                                                                                                                                                                                  |
@@ -343,64 +357,64 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 #### `org` カテゴリアクション
 
-| アクション                                                                                                                                    | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+| アクション                                                                                                                                    | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 | `advanced_security_policy_selected_member_disabled`                                                                                      | Enterprise のオーナーが、Organization が所有するリポジトリで {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できないようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}
 | `advanced_security_policy_selected_member_enabled`                                                                                       | Enterprise のオーナーが、Organization が所有するリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できるようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %}
-| `audit_log_export`                                                                                                                       | Organization の管理者が [Organization の Audit log のエクスポートを作成する](#exporting-the-audit-log)ときにトリガーされます。 エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。                                                                                                                                                                                                                                                                                                                      |
-| `block_user`                                                                                                                             | Organization のオーナーが[Organization のリポジトリにユーザーがアクセスするのをブロックする](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                              |
-| `cancel_invitation`                                                                                                                      | Organization の招待が取り消されている場合にトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                                                                        |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `create_actions_secret`                                                                                                                  | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。{% endif %}                                                                                                                                                                                                                                            |{% if currentVersion == "free-pro-team@latest"%}
-| `disable_oauth_app_restrictions`                                                                                                         | オーナーが Organization に対して[{% data variables.product.prodname_oauth_app %} のアクセス制限を無効にする](/articles/disabling-oauth-app-access-restrictions-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                |
+| `audit_log_export`                                                                                                                       | Organization の管理者が [Organization の Audit log のエクスポートを作成する](#exporting-the-audit-log)ときにトリガーされます。 エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。                                                                                                                                                                                                                                                              |
+| `block_user`                                                                                                                             | Organization のオーナーが[Organization のリポジトリにユーザーがアクセスするのをブロックする](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                                      |
+| `cancel_invitation`                                                                                                                      | Organization の招待が取り消されている場合にトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `create_actions_secret`                                                                                                                  | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。{% endif %}                                                                                                                                                                                    |{% if currentVersion == "free-pro-team@latest"%}
+| `disable_oauth_app_restrictions`                                                                                                         | オーナーが Organization に対して[{% data variables.product.prodname_oauth_app %} のアクセス制限を無効にする](/articles/disabling-oauth-app-access-restrictions-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                        |
 | `disable_saml`                                                                                                                           | Organization の管理者が Organization に対して SML シングルサインオンを無効にするときにトリガーされます。{% endif %}
 | `disable_member_team_creation_permission`                                                                                                | Organization のオーナーがオーナーに Team 作成を制限するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 |{% if currentVersion != "github-ae@latest" %}
 | `disable_two_factor_requirement`                                                                                                         | Organization のすべてのメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー、{% endif %}および外部のコラボレータに対してオーナーが 2 要素認証を無効化するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" %}
-| `enable_oauth_app_restrictions`                                                                                                          | オーナーが Organization に対して[{% data variables.product.prodname_oauth_app %} のアクセス制限を有効にする](/articles/enabling-oauth-app-access-restrictions-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                 |
+| `enable_oauth_app_restrictions`                                                                                                          | オーナーが Organization に対して[{% data variables.product.prodname_oauth_app %} のアクセス制限を有効にする](/articles/enabling-oauth-app-access-restrictions-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                         |
 | `enable_saml`                                                                                                                            | Organization の管理者が Organization に対して [SAML シングルサインオン を有効にする](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)ときにトリガーされます。{% endif %}
 | `enable_member_team_creation_permission`                                                                                                 | メンバーが Team を作成するのを Organizationのオーナーが許可するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 |{% if currentVersion != "github-ae@latest" %}
 | `enable_two_factor_requirement`                                                                                                          | Organization のすべてのメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー、{% endif %}および外部のコラボレータに対してオーナーが 2 要素認証を有効化するときにトリガーされます。{% endif %}
 | `invite_member`                                                                                                                          | [新しいユーザーがOrganization に参加するよう招待](/articles/adding-organization-members-to-a-team)されたにトリガーされます。{% if currentVersion == "free-pro-team@latest" %}
-| `oauth_app_access_approved`                                                                                                              | オーナーが [{% data variables.product.prodname_oauth_app %} へのアクセスを許可する](/articles/approving-oauth-apps-for-your-organization/)ときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                     |
-| `oauth_app_access_denied`                                                                                                                | オーナーが Organization への[以前に承認した {% data variables.product.prodname_oauth_app %} のアクセス権を無効にする](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                                                                                 |
+| `oauth_app_access_approved`                                                                                                              | オーナーが [{% data variables.product.prodname_oauth_app %} へのアクセスを許可する](/articles/approving-oauth-apps-for-your-organization/)ときにトリガーされます。                                                                                                                                                                                                                                                                                             |
+| `oauth_app_access_denied`                                                                                                                | オーナーが Organization への[以前に承認した {% data variables.product.prodname_oauth_app %} のアクセス権を無効にする](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)ときにトリガーされます。                                                                                                                                                                                                                                         |
 | `oauth_app_access_requested`                                                                                                             | オーナーが Organization への {% data variables.product.prodname_oauth_app %} アクセスを許可することを Organization のメンバーが要求するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `register_self_hosted_runner`                                                                                                            | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。                                                                                                                                                                                                                                                                                           |
-| `remove_actions_secret`                                                                                                                  | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}{% if currentVersion == "free-pro-team@latest"%}
+| `register_self_hosted_runner`                                                                                                            | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。                                                                                                                                                                                                                                   |
+| `remove_actions_secret`                                                                                                                  | {% data variables.product.prodname_actions %} シークレットが削除されるとトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest"%}
 | `remove_billing_manager`                                                                                                                 | [オーナーが Organization から支払いマネージャーを削除する](/articles/removing-a-billing-manager-from-your-organization/)とき、または [Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、支払いマネージャーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます。 
 {% endif %}
-| `remove_member`                                                                                                                          | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Organization から [Organization のメンバーが自身を削除](/articles/removing-yourself-from-an-organization/)するときにもトリガーされます。 |
-| `remove_outside_collaborator`                                                                                                            | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `remove_self_hosted_runner`                                                                                                              | セルフホストランナーが削除されたときにトリガーされます。 For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)."                                                                                                                                                                                                                                                                                    |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
-| `revoke_external_identity`                                                                                                               | Organization のオーナーがメンバーのリンクされたアイデンティティを取り消すときにトリガーされます。 詳細は、「[組織へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。                                                                                                                                                                                                     |
-| `revoke_sso_session`                                                                                                                     | Organization のオーナーがメンバーの SAML セッションを取り消すときにトリガーされます。 詳細は、「[組織へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。                                                                                                                                                                                                        |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `runner_group_created`                                                                                                                   | セルフホストランナーグループが作成されたときにトリガーされます。 For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."                                                                                                                                                                                                                       |
-| `runner_group_created`                                                                                                                   | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。                                                                                                                                                                                                                                                                                        |
-| `runner_group_updated`                                                                                                                   | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。                                                                                                                                                                                                                                                       |
-| `runner_group_runners_added`                                                                                                             | セルフホストランナーがグループに追加されたときにトリガーされます。 For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).                                                                                                                                                                                                                                                          |
-| `runner_group_runner_removed`                                                                                                            | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."                                                                                                                                                                                                                                                           |
-| `runner_group_runners_updated`                                                                                                           | ランナーグループのメンバーリストが更新されたときにトリガーされます。 For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `self_hosted_runner_updated`                                                                                                             | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}
+| `remove_member`                                                                                                                          | [オーナーが Organization からメンバーを削除する](/articles/removing-a-member-from-your-organization/)とき、または {% if currentVersion != "github-ae@latest" %}[Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、Organization のメンバーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます{% endif %}。 Organization から [Organization のメンバーが自身を削除](/articles/removing-yourself-from-an-organization/)するときにもトリガーされます。 |
+| `remove_outside_collaborator`                                                                                                            | オーナーが Organization から外部のコラボレータを削除するとき、{% if currentVersion != "github-ae@latest" %}または[Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、外部のコラボレータが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます{% endif %}。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `remove_self_hosted_runner`                                                                                                              | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。                                                                                                                                                                                                                                                |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| `revoke_external_identity`                                                                                                               | Organization のオーナーがメンバーのリンクされたアイデンティティを取り消すときにトリガーされます。 For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."                                                                                         |
+| `revoke_sso_session`                                                                                                                     | Organization のオーナーがメンバーの SAML セッションを取り消すときにトリガーされます。 For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."                                                                                            |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `runner_group_created`                                                                                                                   | セルフホストランナーグループが作成されたときにトリガーされます。 詳しい情報については、「[Organization のセルフホストランナーグループを作成する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)」を参照してください。                                                                                                                                                                                           |
+| `runner_group_created`                                                                                                                   | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。                                                                                                                                                                                                                                |
+| `runner_group_updated`                                                                                                                   | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。                                                                                                                                                                                               |
+| `runner_group_runners_added`                                                                                                             | セルフホストランナーがグループに追加されたときにトリガーされます。 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。                                                                                                                                                                                                                        |
+| `runner_group_runner_removed`                                                                                                            | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."                                                                                                                                                                                                   |
+| `runner_group_runners_updated`                                                                                                           | ランナーグループのメンバーリストが更新されたときにトリガーされます。 詳しい情報については、「[Organization のグループにセルフホストランナーを設定する](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `self_hosted_runner_updated`                                                                                                             | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。{% endif %}
 | `unblock_user`                                                                                                                           | Organizationのオーナーが[ Organization からユーザりブロックを解除](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `update_actions_secret`                                                                                                                  | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| `update_new_repository_default_branch_setting`                                                                                           | オーナーが Organization の新しいリポジトリのデフォルトブランチの名前を変更するときにトリガーされます。 詳しい情報については、「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照してください。{% endif %}
-| `update_default_repository_permission`                                                                                                   | オーナーが Organization のメンバーのデフォルトリポジトリの権限レベルを変更するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `update_member`                                                                                                                          | オーナーがユーザーのロールをオーナーからメンバーに、またはメンバーからオーナーに変更するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `update_actions_secret`                                                                                                                  | {% data variables.product.prodname_actions %} シークレットが更新されるとトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| `update_new_repository_default_branch_setting`                                                                                           | オーナーが Organization の新しいリポジトリのデフォルトブランチの名前を変更するときにトリガーされます。 For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."{% endif %}
+| `update_default_repository_permission`                                                                                                   | オーナーが Organization のメンバーのデフォルトリポジトリの権限レベルを変更するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                           |
+| `update_member`                                                                                                                          | オーナーがユーザーのロールをオーナーからメンバーに、またはメンバーからオーナーに変更するときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                             |
 | `update_member_repository_creation_permission`                                                                                           | オーナーが Organization のメンバーのリポジトリ作成権限を変更するときにトリガーされます。{% if currentVersion == "free-pro-team@latest" %}
-| `update_saml_provider_settings`                                                                                                          | Organization の SAML プロバイダ設定が更新されるときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `update_saml_provider_settings`                                                                                                          | Organization の SAML プロバイダ設定が更新されるときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                        |
 | `update_terms_of_service`                                                                                                                | Organization が標準利用規約と企業向け利用規約を切り替えるときにトリガーされます。 詳細は「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-#### `org_credential_authorization` category actions
+#### `org_credential_authorization` カテゴリアクション
 
-| アクション          | 説明                                                                                                                                                                                 |
-| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `grant`        | [SAML シングルサインオンに使用するクレデンシャルをメンバーが認可する](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。                                                       |
-| `deauthorized` | [SAML シングルサインオンに使用するクレデンシャルの認可をメンバーが取り消す](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。                                                    |
-| `revoke`       | オーナーが[認可されたクレデンシャルを取り消す](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)ときにトリガーされます。 |
+| アクション          | 説明                                                                                                                                                                                                      |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grant`        | [SAML シングルサインオンに使用するクレデンシャルをメンバーが認可する](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。                                                                            |
+| `deauthorized` | [SAML シングルサインオンに使用するクレデンシャルの認可をメンバーが取り消す](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。                                                                         |
+| `revoke`       | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). |
 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
-#### `organization_label` category actions
+#### `organization_label` カテゴリアクション
 
 | アクション     | 説明                         |
 | --------- | -------------------------- |
@@ -410,7 +424,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 {% endif %}
 
-#### `oauth_application` category actions
+#### `oauth_application` カテゴリアクション
 
 | アクション           | 説明                                                                                         |
 | --------------- | ------------------------------------------------------------------------------------------ |
@@ -421,15 +435,15 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `移譲`            | 既存の {% data variables.product.prodname_oauth_app %} が新しい Organization に移譲されるときにトリガーされます。 |
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-#### `packages` category actions
+#### `packages` カテゴリアクション
 
-| アクション                       | 説明                                                                                                                                                                                      |
-| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `package_version_published` | Triggered when a package version is published.                                                                                                                                          |
-| `package_version_deleted`   | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." |
-| `package_deleted`           | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."          |
-| `package_version_restored`  | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." |
-| `package_restored`          | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."         |
+| アクション                       | 説明                                                                                                                                      |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `package_version_published` | パッケージのバージョンが公開されるとトリガーされます。                                                                                                             |
+| `package_version_deleted`   | 特定のパッケージのバージョンが削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 |
+| `package_deleted`           | パッケージ全体が削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。        |
+| `package_version_restored`  | 特定のパッケージのバージョンが削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 |
+| `package_restored`          | パッケージ全体がリストアされるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。      |
 
 {% endif %}
 
@@ -464,74 +478,106 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_team_permission` | Team のプロジェクト ボードの権限レベルが変更されるとき、または Team がプロジェクト ボードに追加または削除されるときにトリガーされます。             |
 | `update_user_permission` | Organization のメンバーまたは外部コラボレーターがプロジェクト ボードに追加または削除されるとき、または彼らの権限レベルが変更されている場合にトリガーされます。 |
 
-#### `protected_branch` category actions
+#### `protected_branch` カテゴリアクション
 
-| アクション                                                 | 説明                                                                                                                                                                                                                                     |
-| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `create`                                              | ブランチでブランチの保護が有効になるときにトリガーされます。                                                                                                                                                                                                         |
-| `destroy`                                             | ブランチでブランチの保護が無効になるときにトリガーされます。                                                                                                                                                                                                         |
-| `update_admin_enforced`                               | リポジトリの管理者に対してブランチの保護が実施されるときにトリガーされます。                                                                                                                                                                                                 |
-| `update_require_code_owner_review`                    | 必須コードオーナーレビューの実施がブランチで更新されるときにトリガーされます。                                                                                                                                                                                                |
-| `dismiss_stale_reviews`                               | 古い Pull Request の却下の実施がブランチで更新されるときにトリガーされます。                                                                                                                                                                                          |
-| `update_signature_requirement_enforcement_level`      | 必須コミット署名の実施がブランチで更新されるときにトリガーされます。                                                                                                                                                                                                     |
-| `update_pull_request_reviews_enforcement_level`       | 必須 Pull Request レビューの実施がブランチで更新されるときにトリガーされます。                                                                                                                                                                                         |
-| `update_required_status_checks_enforcement_level`     | 必須ステータスチェックの実施がブランチで更新されるときにトリガーされます。                                                                                                                                                                                                  |
-| `update_strict_required_status_checks_policy`         | マージする前に最新にする必要があるブランチの要件が変更されるときにトリガーされます。                                                                                                                                                                                             |
-| `rejected_ref_update`                                 | ブランチ更新の試行が拒否されるときにトリガーされます。                                                                                                                                                                                                            |
-| `policy_override`                                     | Triggered when a branch protection requirement is overridden by a repository administrator.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
-| `update_allow_force_pushes_enforcement_level`         | 保護されたブランチについて、フォースプッシュが有効化または無効化されるときにトリガーされます。                                                                                                                                                                                        |
-| `update_allow_deletions_enforcement_level`            | 保護されたブランチについて、ブランチ削除が有効化または無効化されるときにトリガーされます。                                                                                                                                                                                          |
-| `update_linear_history_requirement_enforcement_level` | 保護されたブランチについて、必須の直線状のコミット履歴が有効化または無効化されるときにトリガーされます。                                                                                                                                                                                   |
+| アクション                                                 | 説明                                                                                                                                                                                      |
+| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                                              | ブランチでブランチの保護が有効になるときにトリガーされます。                                                                                                                                                          |
+| `destroy`                                             | ブランチでブランチの保護が無効になるときにトリガーされます。                                                                                                                                                          |
+| `update_admin_enforced`                               | リポジトリの管理者に対してブランチの保護が実施されるときにトリガーされます。                                                                                                                                                  |
+| `update_require_code_owner_review`                    | 必須コードオーナーレビューの実施がブランチで更新されるときにトリガーされます。                                                                                                                                                 |
+| `dismiss_stale_reviews`                               | 古い Pull Request の却下の実施がブランチで更新されるときにトリガーされます。                                                                                                                                           |
+| `update_signature_requirement_enforcement_level`      | 必須コミット署名の実施がブランチで更新されるときにトリガーされます。                                                                                                                                                      |
+| `update_pull_request_reviews_enforcement_level`       | 必須 Pull Request レビューの実施がブランチで更新されるときにトリガーされます。                                                                                                                                          |
+| `update_required_status_checks_enforcement_level`     | 必須ステータスチェックの実施がブランチで更新されるときにトリガーされます。                                                                                                                                                   |
+| `update_strict_required_status_checks_policy`         | マージする前に最新にする必要があるブランチの要件が変更されるときにトリガーされます。                                                                                                                                              |
+| `rejected_ref_update`                                 | ブランチ更新の試行が拒否されるときにトリガーされます。                                                                                                                                                             |
+| `policy_override`                                     | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされるときにトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
+| `update_allow_force_pushes_enforcement_level`         | 保護されたブランチについて、フォースプッシュが有効化または無効化されるときにトリガーされます。                                                                                                                                         |
+| `update_allow_deletions_enforcement_level`            | 保護されたブランチについて、ブランチ削除が有効化または無効化されるときにトリガーされます。                                                                                                                                           |
+| `update_linear_history_requirement_enforcement_level` | 保護されたブランチについて、必須の直線状のコミット履歴が有効化または無効化されるときにトリガーされます。                                                                                                                                    |
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### `pull_request` category actions
+
+| アクション                   | 説明                                                                                                         |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `create`                | Triggered when a pull request is created.                                                                  |
+| `close`                 | Triggered when a pull request is closed without being merged.                                              |
+| `reopen`                | Triggered when a pull request is reopened after previously being closed.                                   |
+| `マージ`                   | Triggered when a pull request is merged.                                                                   |
+| `indirect_merge`        | Triggered when a pull request is considered merged because its commits were merged into the target branch. |
+| `ready_for_review`      | Triggered when a pull request is marked as ready for review.                                               |
+| `converted_to_draft`    | Triggered when a pull request is converted to a draft.                                                     |
+| `create_review_request` | Triggered when a review is requested.                                                                      |
+| `remove_review_request` | Triggered when a review request is removed.                                                                |
+
+#### `pull_request_review` category actions
+
+| アクション    | 説明                                    |
+| -------- | ------------------------------------- |
+| `サブミット`  | Triggered when a review is submitted. |
+| `却下`     | Triggered when a review is dismissed. |
+| `delete` | Triggered when a review is deleted.   |
+
+#### `pull_request_review_comment` category actions
+
+| アクション    | 説明                                          |
+| -------- | ------------------------------------------- |
+| `create` | Triggered when a review comment is added.   |
+| `update` | Triggered when a review comment is changed. |
+| `delete` | Triggered when a review comment is deleted. |
 {% endif %}
 
 #### `repo` カテゴリアクション
 
-| アクション                                 | 説明                                                                                                                                                                                                                                                                                                                                                 |
-| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `access`                              | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization.                                                                                                                                                                                              |
-| `actions_enabled`                     | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)."                                                                          |
-| `add_member`                          | ユーザーが[リポジトリへのコラボレーションアクセスへの招待](/articles/inviting-collaborators-to-a-personal-repository)を受諾するときにトリガーされます。                                                                                                                                                                                                                                         |
-| `add_topic`                           | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
-| `advanced_security_disabled`          | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。                                                        |
-| `advanced_security_enabled`           | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".{% endif %}
+| アクション                                 | 説明                                                                                                                                                                                                                                                         |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                              | ユーザが Organization 内のリポジトリの[可視性を変更](/github/administering-a-repository/setting-repository-visibility)するとトリガーされます。                                                                                                                                           |
+| `actions_enabled`                     | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. REST API を使用して Audit log にアクセスする場合、このイベントは対象外です。 For more information, see "[Using the REST API](#using-the-rest-api)."              |
+| `add_member`                          | ユーザーが[リポジトリへのコラボレーションアクセスへの招待](/articles/inviting-collaborators-to-a-personal-repository)を受諾するときにトリガーされます。                                                                                                                                                 |
+| `add_topic`                           | リポジトリ管理者がリポジトリに[トピックを追加](/articles/classifying-your-repository-with-topics)するとトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+| `advanced_security_disabled`          | リポジトリ管理者がリポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にするとトリガーされます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。             |
+| `advanced_security_enabled`           | リポジトリ管理者がリポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を有効にするとトリガーされます。 詳しい情報については、「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %}
 | `archived`                            | リポジトリの管理者が[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% if enterpriseServerVersions contains currentVersion %}
-| `config.disable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。                                                                                                                                                                                                   |
-| `config.enable_anonymous_git_access`  | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。                                                                                                                                                                                                   |
-| `config.lock_anonymous_git_access`    | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。                                                                                                                                                                              |
+| `config.disable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。                                                                                                           |
+| `config.enable_anonymous_git_access`  | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。                                                                                                           |
+| `config.lock_anonymous_git_access`    | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。                                                                                      |
 | `config.unlock_anonymous_git_access`  | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。{% endif %}
-| `create`                              | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `create_actions_secret`               | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %}
+| `create`                              | [新しいリポジトリが作成された](/articles/creating-a-new-repository)ときにトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `create_actions_secret`               | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[リポジトリの暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。{% endif %}
 | `destroy`                             | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% if currentVersion == "free-pro-team@latest" %}
 | `disable`                             | リポジトリが無効になるときにトリガーされます ([残高不足](/articles/unlocking-a-locked-account)などの場合)。{% endif %}
-| `enable`                              | Triggered when a repository is reenabled.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `remove_actions_secret`               | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}
-| `remove_member`                       | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `register_self_hosted_runner`         | 新しいセルフホストランナーが登録されたときにトリガーされます。 For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."                                                                                                                               |
-| `remove_self_hosted_runner`           | セルフホストランナーが削除されたときにトリガーされます。 For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."                                                                                                                                                |{% endif %}
-| `remove_topic`                        | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。                                                                                                                                                                                                                                                                                                             |
-| `rename`                              | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `self_hosted_runner_updated`          | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}
-| `移譲`                                  | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。                                                                                                                                                                                                                                                                                  |
-| `transfer_start`                      | リポジトリの移譲が行われようとしているときにトリガーされます。                                                                                                                                                                                                                                                                                                                    |
-| `unarchived`                          | Triggered when a repository admin unarchives a repository.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-| `update_actions_secret`               | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %}
+| `enable`                              | リポジトリが有効化されたときにトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `remove_actions_secret`               | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。{% endif %}
+| `remove_member`                       | [ユーザがコラボレータとしてリポジトリから削除](/articles/removing-a-collaborator-from-a-personal-repository)されたときにトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `register_self_hosted_runner`         | 新しいセルフホストランナーが登録されたときにトリガーされます。 For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."                                       |
+| `remove_self_hosted_runner`           | セルフホストランナーが削除されたときにトリガーされます。 For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."                                                        |{% endif %}
+| `remove_topic`                        | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。                                                                                                                                                                                                                     |
+| `rename`                              | [リポジトリの名前が変更された](/articles/renaming-a-repository)ときにトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `self_hosted_runner_updated`          | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。{% endif %}
+| `移譲`                                  | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。                                                                                                                                                                                          |
+| `transfer_start`                      | リポジトリの移譲が行われようとしているときにトリガーされます。                                                                                                                                                                                                                            |
+| `unarchived`                          | リポジトリ管理者がリポジトリをアーカイブ解除するとトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| `update_actions_secret`               | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-#### `repository_advisory` category actions
+#### `repository_advisory` カテゴリアクション
 
-| アクション              | 説明                                                                                                                                                                                                                     |
-| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `close`            | Triggered when someone closes a security advisory. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 |
-| `cve_request`      | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory.                                                   |
-| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}.                                                         |
-| `github_withdraw`  | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error.                                                                                                 |
-| `オープン`             | Triggered when someone opens a draft security advisory.                                                                                                                                                                |
-| `publish`          | Triggered when someone publishes a security advisory.                                                                                                                                                                  |
-| `さいお`              | Triggered when someone reopens as draft security advisory.                                                                                                                                                             |
-| `update`           | Triggered when someone edits a draft or published security advisory.                                                                                                                                                   |
+| アクション              | 説明                                                                                                                                                                                                    |
+| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `close`            | ユーザがセキュリティアドバイザリをクローズするとトリガーされます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 |
+| `cve_request`      | ユーザがセキュリティアドバイザリのドラフトのために {% data variables.product.prodname_dotcom %} に CVE (Common Vulnerabilities and Exposures) 番号をリクエストするとトリガーされます。                                                              |
+| `github_broadcast` | {% data variables.product.prodname_dotcom %} が {% data variables.product.prodname_advisory_database %} でセキュリティアドバイザリを公開するとトリガーされます。                                                                 |
+| `github_withdraw`  | {% data variables.product.prodname_dotcom %} が誤って公開されたセキュリティアドバイザリを撤回するとトリガーされます。                                                                                                                     |
+| `オープン`             | ユーザがドラフトのセキュリティアドバイザリをオープンするとトリガーされます。                                                                                                                                                                |
+| `publish`          | ユーザがセキュリティアドバイザリを公開するとトリガーされます。                                                                                                                                                                       |
+| `reopen`           | ユーザがドラフトのセキュリティアドバイザリとして再オープンするとトリガーされます。                                                                                                                                                             |
+| `update`           | ユーザがドラフトまたは公開済みのセキュリティアドバイザリを編集するとトリガーされます。                                                                                                                                                           |
 
-#### `repository_content_analysis` category actions
+#### `repository_content_analysis`カテゴリアクション
 
 | アクション     | 説明                                                                                                                                                                                                          |
 | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -540,91 +586,93 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 {% endif %}{% if currentVersion != "github-ae@latest" %}
 
-#### `repository_dependency_graph` category actions
+#### `repository_dependency_graph` カテゴリアクション
 
-| アクション     | 説明                                                                                                                                                                                                                                                                                                                   |
-| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 |
-| `enable`  | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository.                                                                                                                   |
+| アクション     | 説明                                                                                                                                                                                                                                                 |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリの依存関係グラフを無効にするとトリガーされます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 |
+| `enable`  | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリの依存関係グラフを有効にするとトリガーされます。                                                                                                                  |
 
 {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-#### `repository_secret_scanning` category actions
+#### `repository_secret_scanning` カテゴリアクション
 
-| アクション     | 説明                                                                                                                                                                                                                                                                                                 |
-| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
-| `enable`  | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository.                                                                                                      |
+| アクション     | 説明                                                                                                                                                                                                                                       |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリのシークレットスキャンを無効にするとトリガーされます。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
+| `enable`  | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリのシークレットスキャンを有効にするとトリガーされます。                                                                                                     |
 
 {% endif %}{% if currentVersion != "github-ae@latest" %}
-#### `repository_vulnerability_alert` category actions
+#### `repository_vulnerability_alert` カテゴリアクション
 
-| アクション    | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 |
-| `却下`     | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency.                                                                                                                              |
-| `解決`     | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency.                                                                                                                                                                                                                                                                                                              |
+| アクション    | 説明                                                                                                                                                                                                                                                                                                                                                                                                      |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | {% data variables.product.product_name %} が脆弱性のある依存関係を使用するリポジトリの{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}セキュリティ{% endif %}アラートを作成するとトリガーされます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 |
+| `却下`     | Organization のオーナーまたはリポジトリへの管理者アクセスを持つユーザが、脆弱性のある依存関係に関する{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}セキュリティ{% endif %}アラートを却下したときにトリガーされます。                                                                                                                                          |
+| `解決`     | リポジトリへの書き込みアクセスを持つユーザが変更をプッシュして、プロジェクトの依存関係の脆弱性を更新および解決するとトリガーされます。                                                                                                                                                                                                                                                                                                                                     |
 
 {% endif %}{% if currentVersion == "free-pro-team@latest" %}
-#### `repository_vulnerability_alerts` category actions
+#### `repository_vulnerability_alerts` カテゴリアクション
 
-| アクション                    | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 |
-| `disable`                | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}.                                                                                                                                                                                                                                                                                            |
-| `enable`                 | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}.                                                                                                                                                                                                                                                                                             |
+| アクション                    | 説明                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `authorized_users_teams` | Organization のオーナーまたはリポジトリへの管理者権限を持つユーザが、リポジトリ内の脆弱性のある依存関係の {% data variables.product.prodname_dependabot_alerts %} を受け取ることを許可されたユーザまたは Team のリストを更新するとトリガーされます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 |
+| `disable`                | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが {% data variables.product.prodname_dependabot_alerts %} を無効にするとトリガーされます。                                                                                                                                                                                                                                        |
+| `enable`                 | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが {% data variables.product.prodname_dependabot_alerts %} を有効にするとトリガーされます。                                                                                                                                                                                                                                        |
 
 {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-#### `secret_scanning` category actions
+#### `secret_scanning` カテゴリアクション
 
-| アクション     | 説明                                                                                                                                                                                                                                                                    |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
-| `enable`  | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories.                                                                                                      |
+| アクション     | 説明                                                                                                                                                                                                                               |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが既存のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリのシークレットスキャンを無効にするとトリガーされます。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
+| `enable`  | Organization のオーナーが既存のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリのシークレットスキャンを有効にするとトリガーされます。                                                                                                     |
 
-#### `secret_scanning_new_repos` category actions
+#### `secret_scanning_new_repos` カテゴリアクション
 
-| アクション     | 説明                                                                                                                                                                                                                                                              |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `disable` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
-| `enable`  | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories.                                                                                                      |
+| アクション     | 説明                                                                                                                                                                                                                               |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `disable` | Organization のオーナーが新規のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリのシークレットスキャンを無効にするとトリガーされます。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
+| `enable`  | Organization のオーナーが新規のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリのシークレットスキャンを有効にするとトリガーされます。                                                                                                     |
 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` カテゴリアクション
 
-| アクション                                          | 説明                                                                                                                                                                                                                                                                                                                       |
-| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`              | リポジトリでスポンサーボタンの表示を有効化または無効化したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                                                                          |
-| `repo_funding_links_file_action`               | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                                                                               |
-| `sponsor_sponsorship_cancel`                   | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                                                                                                             |
-| `sponsor_sponsorship_create`                   | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)」を参照)                                                                                                                                                       |
-| `sponsor_sponsorship_preference_change`        | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/articles/managing-your-sponsorship)")                                                                                                                                                            |
-| `sponsor_sponsorship_tier_change`              | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                                     |
-| `sponsored_developer_approve`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
-| `sponsored_developer_create`                   | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
-| `sponsored_developer_profile_update`           | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
-| `sponsored_developer_request_approval`         | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
-| `sponsored_developer_tier_description_update`  | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
-| sponsored_developer_update_newsletter_send | スポンサーにメールで最新情報を送信したときにトリガーされます (「[スポンサーに連絡する](/articles/contacting-your-sponsors)」を参照)                                                                                                                                                                                                                                   |
-| `waitlist_invite_sponsored_developer`          | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
-| `waitlist_join`                                | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
+| アクション                                         | 説明                                                                                                                                                                                                                                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | カスタム金額を有効または無効にするとき、または提案されたカスタム金額を変更するときにトリガーされます (「[スポンサーシップ層を管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)」を参照)。                                                                                                                                  |
+| `repo_funding_links_file_action`              | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                                                                      |
+| `sponsor_sponsorship_cancel`                  | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                                                                                                    |
+| `sponsor_sponsorship_create`                  | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照)                                                                                                                                                                  |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                               |
+| `sponsor_sponsorship_tier_change`             | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照)                                                                                                                                            |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
+| `sponsored_developer_disable`                 | {% data variables.product.prodname_sponsors %} アカウントが無効になるとトリガーされます                                                                                                                                                                                                                                             |
+| `sponsored_developer_redraft`                 | {% data variables.product.prodname_sponsors %} アカウントが承認済みの状態からドラフト状態に戻るとトリガーされます                                                                                                                                                                                                                                |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
+| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を管理する](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)」を参照)                                                                                                                                                                  |
+| `sponsored_developer_update_newsletter_send`  | スポンサーにメールで最新情報を送信するとトリガーされます (「[スポンサーに連絡する](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)」を参照)                                                                                                                                                                             |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
 {% endif %}
 
 #### `team` カテゴリアクション
 
-| アクション                | 説明                                                                                                                                                                               |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `add_member`         | Organization のメンバーが[Team に追加される](/articles/adding-organization-members-to-a-team)ときにトリガーされます。                                                                                    |
-| `add_repository`     | リポジトリの管理が Team に任せられるときにトリガーされます。                                                                                                                                                |
-| `change_parent_team` | 子チームが作成されるとき、または[子チームの親が変更される](/articles/moving-a-team-in-your-organization-s-hierarchy)ときにトリガーされます。                                                                             |
-| `change_privacy`     | Team のプライバシー レベルが変更されるときにトリガーされます。                                                                                                                                               |
-| `create`             | Triggered when a new team is created.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| アクション                | 説明                                                                                                                                                                   |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member`         | Organization のメンバーが[Team に追加される](/articles/adding-organization-members-to-a-team)ときにトリガーされます。                                                                        |
+| `add_repository`     | リポジトリの管理が Team に任せられるときにトリガーされます。                                                                                                                                    |
+| `change_parent_team` | 子チームが作成されるとき、または[子チームの親が変更される](/articles/moving-a-team-in-your-organization-s-hierarchy)ときにトリガーされます。                                                                 |
+| `change_privacy`     | Team のプライバシー レベルが変更されるときにトリガーされます。                                                                                                                                   |
+| `create`             | 新しい Team が更新されるとトリガーされます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 
-`demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | Triggered when a repository is no longer under a team's control.
+`demote_maintainer` | ユーザがチームメンテナから Team メンバーに降格されるとトリガーされます。 For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `destroy` | Triggered when a team is deleted from the organization.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)."{% endif %} | `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). | `remove_repository` | リポジトリが Team の管理下でなくなるとトリガーされます。
 
-#### `team_discussions` category actions
+#### `team_discussions` カテゴリアクション
 
 | アクション     | 説明                                                                                                                                                                                     |
 | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -632,7 +680,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `enable`  | Organization のオーナーが Organization の Team ディスカッションを有効にするときにトリガーされます。                                                                                                                     |
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%}
-#### `workflows` category actions
+#### `workflows` カテゴリアクション
 
 {% data reusables.actions.actions-audit-events-workflow %}
 
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index 4f717991c9..77d90925a0 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -14,9 +14,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 左サイドバーで [**Installed {% data variables.product.prodname_github_app %}s**] をクリックします。 ![Organization の Settings サイドバーでの [Installed {% data variables.product.prodname_github_app %}s] タブ](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. レビューする {% data variables.product.prodname_github_app %}の横にある [**Configure**] をクリックします。 ![[Configure] ボタン](/assets/images/help/organizations/configure-installed-integration-button.png)
 6. {% data variables.product.prodname_github_app %} の権限とリポジトリのアクセス権をレビューします。 ![{% data variables.product.prodname_github_app %} にすべてのリポジトリまたは特定のリポジトリへのアクセス権を付与するためのオプション](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index 1f22cb2c93..8e732c4b0c 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ topics:
 
 ### Organization が所有するすべての {% data variables.product.prodname_github_app %} の管理権限を与える
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. [Management] の下で、Organization の {% data variables.product.prodname_github_app %} マネージャーに指名したい人物のユーザ名を入力し、[**Grant**] をクリックします。 ![{% data variables.product.prodname_github_app %} マネージャーを追加](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### 個々の {% data variables.product.prodname_github_app %} の管理権限を誰かに与える
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. [{% data variables.product.prodname_github_app %}s] の下で、{% data variables.product.prodname_github_app %} マネージャーを追加したいアプリケーションのアバターをクリックします。 ![{% data variables.product.prodname_github_app %} を選択](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index ff06968887..f8caaff209 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ topics:
 
 ### Organization 全体で {% data variables.product.prodname_github_app %} マネージャーの権限を削除する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. [Management] の下で、{% data variables.product.prodname_github_app %}マネージャー権限を削除する個人のユーザ名を探し、 [**Revoke**] をクリックします。 ![{% data variables.product.prodname_github_app %} マネージャー権限の削除](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### 個別の {% data variables.product.prodname_github_app %} で {% data variables.product.prodname_github_app %} マネージャーの権限を削除する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. [{% data variables.product.prodname_github_app %}] の下で、{% data variables.product.prodname_github_app %} マネージャーを削除するアプリケーションのアバターをクリックします。 ![{% data variables.product.prodname_github_app %} を選択](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 31b14ebdb5..f0bfe4012f 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -49,4 +49,4 @@ topics:
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. チームの会話の上にある {% octicon "project" aria-label="The Projects icon" %}[**Projects**] をクリックします。 ![チームの [Repositories] タブ](/assets/images/help/organizations/team-project-board-button.png)
-5. 権限レベルを変更するには、更新するプロジェクトボードの右にあるドロップダウンを使用します。 プロジェクトボードを削除するには、[**{% octicon "trashcan" aria-label="The trashcan icon" %}**] をクリックします。 ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png)
+5. 権限レベルを変更するには、更新するプロジェクトボードの右にあるドロップダウンを使用します。 プロジェクトボードを削除するには、[**{% octicon "trash" aria-label="The trash icon" %}**] をクリックします。 ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index d7a53194ae..f1547b01cf 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ Organization レベルの設定を管理することに加え、Organization の
 | リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照)                                                                                                                                                                                                                                                                                 |       |        |       |          |                                                                       **X**                                                                       |
 | リポジトリ設定の変更                                                                                                                                                                                                                                                                                                                                                        |       |        |       |          |                                                                       **X**                                                                       |
 | Team およびコラボレータのリポジトリへのアクセス管理                                                                                                                                                                                                                                                                                                                                      |       |        |       |          |                                                                       **X**                                                                       |
-| リポジトリのデフォルトブランチ編集                                                                                                                                                                                                                                                                                                                                                 |       |        |       |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| リポジトリのデフォルトブランチ編集                                                                                                                                                                                                                                                                                                                                                 |       |        |       |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照）                                                                                                                                                                                                                                                                |       |        |       |          |                                                                       **X**                                                                       |
 | リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照）                                                                                                                                                                                                                                                                   |       |        | **X** |  **X**   |                                                                **X** 
 {% endif %}
@@ -142,7 +142,8 @@ Organization レベルの設定を管理することに加え、Organization の
 | [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                 |       | **X**  | **X** |  **X**   |                                                                       **X**                                                                       |
 | [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                            |       | **X**  | **X** |  **X**   |                                                                       **X**                                                                       |
 | [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                              | **X** | **X**  | **X** |  **X**   |                                                                       **X**                                                                       |
-| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                 |       |        |       |  **X**   |                                                                **X** 
+| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                 |       |        |       |  **X**   |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                 |       |        | **X** |  **X**   |                                                                **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ Organization レベルの設定を管理することに加え、Organization の
 
 | リポジトリアクション                                                                                                                                                                                                                                                                    | Read  | Triage |        Write        |      Maintain       |                                                                             Admin                                                                             |
 |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                                                                             |       |        |                     |                     |                                                                                                                                                               |
-| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を受信                                                                                                       |       |        |                     |                     |                                                                             **X**                                                                             |
-| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                   |       |        |                     |                     |                                                                             **X**                                                                             |
-| 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)                                               |       |        |                     |                     |                                                                             **X**                                                                             |
-| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成                                                                                                                                                                                 |       |        |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |        |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                                                                           |       |        |                     |                     |                                                                                                                                                               |
+| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信                                                                                                            |       |        |                     |                     |                                                                             **X**                                                                             |
+| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                        |       |        |                     |                     |                                                                             **X**                                                                             |
+| 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)                                               |       |        |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成                                                                                                                                                                                        |       |        |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |        |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)                                                                                                                                                                    |       |        |                     |                     |                                                                             **X**                                                                             |
 | [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                                | **X** | **X**  |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                                                                                   | **X** | **X**  |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index ad7d472cb9..734450dbad 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ Organization のリポジトリに対する管理者権限があるユーザが
 
 ### 基本レベルの権限の設定
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Base permissions] で、ドロップダウンを使用して新しい基本レベルの権限を選択します。 ![[base permissions] ドロップダウンから新しい権限レベルを選択する](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. 変更を確認します。 確定するために、[**Change default permission to PERMISSION**] をクリックします。 ![基本レベルの権限の変更を確認して確定する](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index ca5872b597..fc1c8a46eb 100644
--- a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -22,17 +22,15 @@ SSH CAをOrganizationに追加すると、メンバーはあなたが提供し
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### SSH認証局を削除する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index ef873a5583..9c62c70507 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 有効化されると、Organization のオーナー、そして Organization が所有するリポジトリに管理権限を持つ人は、Issue を削除できるようになります。 リポジトリの管理権限を持つ人には、管理権限を持つ Organization メンバーや外部コラボレーターが含まれます。 詳細は「[Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization/)」および「[Issue を削除する](/articles/deleting-an-issue)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Issue deletion] の下で、[**Allow members to delete issues for this organization**] (この Organization の Issue の削除をメンバーに許可する) を選択します。 ![Issue の削除を許可するチェックボックス](/assets/images/help/settings/issue-deletion.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index 700cf94e95..b70d4012f4 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,9 +16,8 @@ Organization のオーナーは、organization dependency insights の表示制
 
 Enterprise のオーナーは、Enterprise アカウントにあるすべての Organization dependency insights について、表示制限を設定できます。 詳しい情報については、「[Enterprise アカウントに dependency insights に関するポリシーを施行する](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)」参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Member organization permissions] で、[**Allow members to view dependency insights**] を選択または選択解除します。 ![insights の表示をメンバーに許可するチェックボックス](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 819e3b99a6..74179e4921 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -28,7 +28,6 @@ Organization を削除すると、GitHub では**コンテンツを復元でき
 
 ### 2. Organization の削除
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Organization の設定ページの下の方にある [**Delete this Organization**] をクリックします。 ![[Delete this organization] ボタン](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index d1b5fe7d6f..bc9b0fe32b 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -27,9 +27,8 @@ Organization のすべてのリポジトリについて {% data variables.produc
 
 ### Organization の {% data variables.product.prodname_actions %} 権限の管理
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. [**Local and third-party Actions**] で、オプションを選択します。 ![この Organization でアクションを有効化、無効化、制限](/assets/images/help/repository/enable-org-actions.png)
 1. [**Save**] をクリックします。
@@ -50,22 +49,20 @@ Organization のワークフローをすべて無効にすることも、Organiz
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
-1. [**Policies**] でオプションを選択します。 ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png)
+1. [**Policies**] でオプションを選択します。 ![この Organization に対するアクションポリシーを設定する](/assets/images/help/organizations/actions-policy.png)
 1. [**Save**] をクリックします。
 
-### Allowing specific actions to run
+### 特定のアクションの実行を許可する
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
-1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
+1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![許可リストにアクションを追加する](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. [**Save**] をクリックします。
 
 {% endif %}
@@ -77,9 +74,27 @@ Organization のワークフローをすべて無効にすることも、Organiz
 
 #### Organization のプライベートフォークポリシーを設定する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your organization
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you choose the restricted option as the default in your organization settings, the same option is auto-selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and the more restricted default has been selected in the enterprise settings, you won't be able to choose the more permissive default in your organization settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. **Save（保存）**をクリックして、設定を適用してください。
+{% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/index.md b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
index 18fecfdb02..36ccde855b 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/index.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
@@ -13,7 +13,7 @@ topics:
   - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index 349aa028f4..7d2dbc9500 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ Organizationのオーナーは、Organization のリポジトリのデフォル
 
 ### デフォルトラベルの作成
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ Organizationのオーナーは、Organization のリポジトリのデフォル
 
 ### デフォルトラベルの編集
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ Organizationのオーナーは、Organization のリポジトリのデフォル
 
 ### デフォルトラベルの削除
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 0917c99ae7..92ffe65c6c 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,14 +17,13 @@ topics:
 
 デフォルト設定では、リポジトリ管理者または Organization のオーナーが Organization が所有するリポジトリのディスカッションを有効にすると、読み取りアクセス権を持つ Organization のメンバーがディスカッションを作成できます。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Repository discussions] で、[**Allow users with read access to create discussions**] を選択または選択解除します。 ![読み取りアクセス権を持つユーザがディスカッションを作成できるようにするチェックボックス](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. [**Save**] をクリックします。 ![ディスカッション設定の [Save] ボタン](/assets/images/help/discussions/click-save.png)
 
 ### 参考リンク
 
-- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
-- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)"
+- 「[Discussions について](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」
+- 「[コミュニティの Discussions を管理する](/discussions/managing-discussions-for-your-community)」
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index e56d5ac613..ae22ef7ac0 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ Organization のオーナーは、Team がレビューをリクエストされ
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### Organization のスケジュールされたリマインダーを作成する
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ Organization のオーナーは、Team がレビューをリクエストされ
 {% data reusables.reminders.create-reminder %}
 
 ### Organization のスケジュールされたリマインダーを管理する
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ Organization のオーナーは、Team がレビューをリクエストされ
 {% data reusables.reminders.update-buttons %}
 
 ### Organization のスケジュールされたリマインダーを削除する
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index deb5358813..6d0789f34d 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ Enterprise のオーナーが Enterprise のデフォルトブランチ名にポ
 
 ### デフォルトブランチ 名を設定する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. [Repository default branch] で、[**Change default branch name now**] をクリックします。 ![[Override] ボタン](/assets/images/help/organizations/repo-default-name-button.png)
 4. 新しいブランチに使用したいデフォルト名を入力します。 ![デフォルト名を入力するテキストフィールド](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 994821e12a..23c31a495c 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -20,9 +20,8 @@ Organization のオーナーは、Organization 内のメンバー名表示を管
 
 Organization の各メンバーは、自分のプロフィール名を設定で選択します。 詳細は「[プロフィールをパーソナライズする](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Admin repository permissions] の下で、[**Allow members to see comment author's profile name in private repositories**] を選択または選択解除します。 ![プライベートリポジトリ内で、コメント作者のフルネームを表示することをメンバーに許可するためのチェックボックス](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 811e0767c8..320e337a82 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ Organization レベルでプライベート{% if currentVersion == "free-pro-tea
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Repository forking] で、[**Allow forking of private repositories**] または [**Allow forking of private and internal repositories**] を選択します。 ![Organization でフォークを許可または禁止するチェックボックス](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
index 99e86578e0..2fb5d1ed6f 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -21,9 +21,8 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
 
 {% data variables.product.prodname_pages %} サイトの公開を許可しない場合、すでに公開されているサイトはすべて公開されたままになります。 そのサイトは手動で取り下げることができます。 詳細は「[{% data variables.product.prodname_pages %}サイトの取り下げ](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
 1. [Pages creation] で、許可する可視性を選択し、禁止する可視性を選択解除します。 ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
 1. [Pages creation] で、[**Allow members to publish sites**] を選択または選択解除します。 ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index 1f208d8622..8c2e0edcb8 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 Organization がスポンサーする開発者や Organization は、作業に関する最新情報を送信できます。 これらの更新を受信するメールアドレスを管理できます。
 
-Organization のスポンサーアカウントからの更新を無効化することもできます。 詳細は「[スポンサーシップを管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)」を参照してください。
+Organization のスポンサーアカウントからの更新を無効化することもできます。 詳細は「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. [Sponsors update email (Private)] の下に、Organization のスポンサーアカウントから更新を受信するメールアドレスを入力します。 ![スポンサーアカウントから更新を受信するためのメールアドレスを入力するためのテキストボックス](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. [**Update profile**] をクリックします。 ![[Update profile] ボタン](/assets/images/help/organizations/update-profile-button.png)
 
 ### 参考リンク
 
-- 「[{% data variables.product.prodname_sponsors %} でオープンソースコミュニティをサポートする](/github/supporting-the-open-source-community-with-github-sponsors)」
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md
index df2a567e9f..dca2ae833f 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -40,9 +40,8 @@ Organization の名前を変更したら、次のようになります:
 
 ### Organization の名前を変更する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 設定ページの末尾近くにある [Rename organization] の下の [**Rename Organization**] をクリックします。 ![[Rename organization] ボタン](/assets/images/help/settings/settings-rename-organization.png)
 
 ### 参考リンク
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index b94ee4d602..474bd597b0 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -27,9 +27,8 @@ Organization のオーナーは、いつでもどんなタイプの Team でも
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Repository creation] で、1 つ以上のオプションを選択します。 ![リポジトリ作成のオプション](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index d6cd08ba45..a378663fdf 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ topics:
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Repository visibility change] の下で、[**Allow members to change repository visibilities for this organization**] の選択を解除します。 ![リポジトリ可視性変更をメンバーに許可するチェックボックス](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index 7c2ef12887..162c27713f 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -19,9 +19,8 @@ topics:
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Repository invitations] で、[**Allow members to invite outside collaborators to repositories for this organization**] を選択します。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 3b97714883..1d2c778782 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -16,9 +16,8 @@ topics:
 
 コードオーナーは、Organization 内のリポジトリについて、削除や移譲の権限を設定できます。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Repository deletion and transfer] の下で、[**Allow members to delete or transfer repositories for this organization**] を選択または選択解除します。 ![リポジトリの削除をメンバーに許可するためのチェックボックス](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index b16e2ebc3e..ae9e3e5f79 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -17,9 +17,8 @@ Organization のオーナーは Team の作成権限を設定できます。
 
 Team の作成権限を設定しなかった場合、デフォルトでは、すべての Organization メンバーが Team を作成できるようになります。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. [Team creation rules] で、[**Allow members to create teams**] を選択または選択解除します。 ![Team の作成をメンバーに許可するためのチェックボックス](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..c629b11663
--- /dev/null
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### ドメイン検証について
+
+Organization のドメインの所有権を検証したあと、「検証済み」バッジが Organization のプロフィールに表示されます。 Organization が {% data variables.product.prodname_ghe_cloud %} 上にあり、企業向け利用規約に同意した場合、Organization のオーナーは、検証済みドメインにある各メンバーのメールアドレスを見て、Organization メンバーの身元を検証できるようになります。 詳細は「[Organization のプロフィールページについて](/articles/about-your-organization-s-profile/)」および「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。
+
+Enterprise アカウントがオーナーの Organization の場合、Organization による検証済みのドメインに加えて、Enterprise アカウントで検証されたドメインの「検証済み」バッジが Organization のプロフィールに表示されます。 Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+{% data variables.product.prodname_ghe_cloud %} では、Organization のドメインの所有権を検証したあと、その Organization へのメール通知を制限することができます。 For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. DNS 設定が変更されるまで待ちます。これには、最大 72 時間かかる場合があります。 コマンドラインで `dig` コマンドを実行し、`ORGANIZATION` を Organization の名前に、`example.com` を検証するドメインに置き換えることで、DNS 設定が変更されたことを確認できます。 新しい TXT レコードがコマンド出力に表示されているはずです。
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. 必要に応じて、Organization のプロフィールページに「検証済み」バッジが表示されたら、ドメインホスティングサービスの DNS レコードから TXT エントリを削除できます。 ![検証済みバッジ](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index 1b01ef3961..89ce9d1cee 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ Organization のオーナーの Team のメンバーは、人に*支払いマネ
 
 招待された人は、Organization の支払いマネージャーになることを依頼する招待メールを受信します。 招待された人が招待メール中の受諾のリンクをクリックすると、その人は自動的に支払いマネージャーとして Organization に追加されます。 その人がまだ GitHub のアカウントを持っていない場合は、アカウント作成のためのサインアップにリダイレクトされ、アカウント作成後に自動的に支払いマネージャーとして Organization に追加されます。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Billing managers（支払いマネージャー）の隣にある [**Add a billing manager**] をクリックします。 ![支払いマネージャーの招待](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![支払いマネージャーの招待](/assets/images/help/billing/settings_billing_managers_list.png)
 6. 追加したい人のユーザ名あるいはメールアドレスを入力し、[**Send Invitation**] をクリックします。 ![支払いマネージャーの招待ページ](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index 31b8a96c70..bac942d131 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -23,6 +23,12 @@ topics:
 
 Organizationのオーナーには、Organization に対する管理アクセス権限があります。 {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**Note**: As an organization owner, you can change the role of other organization members and owners. You can't change your own role.
+
+{% endnote %}
+
 ### Organizationのオーナーの指名
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index c7cf1379e1..821c2d8dca 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ Organization のメンバーは、*owner (オーナー)*{% if currentVersion ==
 | Organization 参加ログにアクセスする                                                                                                                                                                                                                                                               | **X** |       |           |
 | Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照)                                                                                                                                                                         | **X** |       |           |
 | Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照)                                                                                                                                                                            | **X** |       |           |
-| メール通知を検証済みドメインに制限する（詳細は、「[メール通知を承認済みドメインに制限する](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)」を参照してください）                                                                                                                       | **X** |       |           |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)                                        | **X** |       |           |
 | **すべての Team** を削除する                                                                                                                                                                                                                                                                    | **X** |       |           |
 | すべてのリポジトリを含めて Organization のアカウントを削除する                                                                                                                                                                                                                                                 | **X** |       |           |
 | Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照)                                                                                                                                                                    | **X** | **X** |           |
@@ -60,9 +60,9 @@ Organization のメンバーは、*owner (オーナー)*{% if currentVersion ==
 | Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照)                                                                                                                                          | **X** |       |           |
 | Organization dependency insights の可視性を管理する (詳細は「[Organization dependency insights の可視性を変更する](/articles/changing-the-visibility-of-your-organizations-dependency-insights)」を参照)                                                                                                         | **X** |       |           |
 | **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照)                                                                                                                                                                      | **X** |       |           |
-| アカウントをスポンサーし、Organization のスポンサーシップを管理する（詳細は、「[オープンソースコントリビューターをスポンサーする](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)」を参照）                                                                                                   | **X** | **X** |           |
+| アカウントをスポンサーし、Organization のスポンサーシップを管理する（詳細は、「[オープンソースコントリビューターをスポンサーする](/sponsors/sponsoring-open-source-contributors)」を参照）                                                                                                                                                           | **X** | **X** |           |
 | スポンサーアカウントからのメール更新の管理（詳細は、「[Organization のスポンサーアカウントからの更新を管理する](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)」を参照）                                                                                                          | **X** |       |           |
-| スポンサーシップを別の Organization に関連付ける（詳細は、「[Organization へのスポンサーシップの関連付け](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)」を参照してください）。                                                                                       | **X** |       |           |
+| スポンサーシップを別の Organization に関連付ける（詳細は、「[Organization へのスポンサーシップの関連付け](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)」を参照してください）。                                                                                                           | **X** |       |           |
 | Organization 内のリポジトリからの {% data variables.product.prodname_pages %} サイトの公開を管理する（詳細は、「[Organization の {% data variables.product.prodname_pages %} サイトの公開を管理する](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照） | **X** |       |           |
 | Organization のセキュリティおよび分析設定を管理する (詳細は「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照)                                                                                           | **X** |       |           |
 | [SAML シングルサインオン](/articles/about-identity-and-access-management-with-saml-single-sign-on)を有効にして強制する                                                                                                                                                                                    | **X** |       |           |
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index 7a04191f5e..065b156258 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. [支払いマネージャー] リストで、削除する個人の名前の横にある {% octicon "x" aria-label="X symbol" %} をクリックします。 ![支払いマネージャーの削除](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![支払いマネージャーの削除](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index d21148c708..1999733c83 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 リカバリコードは共有や配布しないでください。 [LastPass](https://lastpass.com/)、[1Password](https://1password.com/)、[Keeper](https://keepersecurity.com/) などのパスワードマネージャで保存することをおすすめします。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. [SAML single sign-on] の下にあるリカバリコードに関する注意書きの [**Save your recovery codes**] をクリックします。 ![リカバリコードを表示し保存するリンク](/assets/images/help/saml/saml_recovery_codes.png)
 6. [**Download**]、[**Print**]、または [**Copy**] をクリックしてリカバリコードを保存します。 ![リカバリコードをダウンロード、印刷、コピーするボタン](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index bd2687a017..86d18d1c84 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ SAML SSO を有効化しても強制はしない場合、SAML SSO を使用し
 
 Organization で SAML SSO を強制する前に、アイデンティティプロバイダ (IdP) を設定しておいてください。 詳細は「[Organization での SAML シングルサインオンの施行を準備する](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択します。 ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index eb27515290..2aa8443cb0 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ SAML SSO とサポートされる IdP を使用してOrganization に認証さ
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ SAML SSO とサポートされる IdP を使用してOrganization に認証さ
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ SAML SSO とサポートされる IdP を使用してOrganization に認証さ
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. [Team synchronization] の下にある [**Disable team synchronization**] をクリックします。 ![Team の同期を無効化する](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index 20937a33ca..48c32b25c6 100644
--- a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -29,9 +29,8 @@ topics:
 
 ### Organization のレガシーの管理者 Team をすべて移行する
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Organization のレガシーの管理者 Team をレビューし、[**Migrate all teams**] をクリックします。 ![[Migrate all teams] ボタン](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. 移行するチームのメンバーについて起きうる変化についての情報を読んだら、[**Migrate all teams**] をクリックします。 ![移行を確定するボタン](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index 531fb74095..4eaa7dea3d 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -15,9 +15,8 @@ topics:
 
 {% data reusables.organizations.team-discussions-default %}Team ディスカッションに関する詳しい情報については「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照してください。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. [Team discussions] の下で、[**Enable team discussions for this organization**] の選択を解除します。 ![Organization の Team ディスカッションを有効化または無効化するチェックボックス](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index 72a3123263..c37b7722bc 100644
--- a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 {% data variables.product.prodname_oauth_app %}のアクセス制限が有効化されている場合、Organization のメンバーは Organization のリソースへのアクセスを持つ {% data variables.product.prodname_oauth_app %}を承認する前に、Organization のオーナーからの[承認をリクエスト](/articles/requesting-organization-approval-for-oauth-apps)しなければなりません。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. 承認したいアプリケーションの隣で [**Review**] をクリックします。 ![レビューのリクエストリンク](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. リクエストされたアプリケーションに関する情報をレビューしたら、[**Grant access**] をクリックします。 ![アクセスの許可ボタン](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index 920e6cb0a1..8b451c9cd4 100644
--- a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -12,9 +12,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. 無効化したいアプリケーションの隣にある {% octicon "pencil" aria-label="The edit icon" %} をクリックします。 ![編集アイコン](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. [**Deny access**] をクリックします。 ![拒否の確定ボタン](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index 7d81caf9c2..aa1b2b3985 100644
--- a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. [**Remove restrictions**] をクリックします。 ![[Remove restrictions] ボタン](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. サードパーティアプリケーション制限の無効化に関する情報を確認したら、[**Yes, remove application restrictions**] (はい、アプリケーション制限を削除します) をクリックします。 ![[Remove confirmation] ボタン](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index b70bcae417..ff97f999ec 100644
--- a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. [Third-party application access policy] の下で [**Setup application access restrictions**] をクリックします。 ![制限の設定ボタン](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. サードパーティのアクセス制限に関する情報を確認したら、[**Restrict third-party application access**] をクリックします。 ![制限の確認ボタン](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md
index 864fc39f92..1a35b75392 100644
--- a/translations/ja-JP/content/packages/index.md
+++ b/translations/ja-JP/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..19d5f2c220
--- /dev/null
+++ b/translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,83 @@
+---
+title: About permissions for GitHub Packages
+intro: 'Learn about how to manage permissions for your packages.'
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### About scopes and permissions for package registries
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+For example:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted.{% elsif currentVersion == "github-ae@latest" %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+
+| Scope | Description | Required permission |
+| --- | --- | --- |
+|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read |
+|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write |
+| `delete:packages` | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Delete packages from {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin |
+| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin |
+
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens  
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..19ce960f11
--- /dev/null
+++ b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: パッケージのアクセス制御と可視性の設定
+intro: 'コンテナイメージに読み取り、書き込み、管理アクセス権限があるユーザと、{% data variables.product.prodname_dotcom %} 上のコンテナイメージの可視性を選択します。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。
+
+現在のところ、{% data variables.product.prodname_container_registry %}だけがコンテナイメージパッケージに関する詳細な権限を提供しています。
+
+リポジトリをスコープとするパッケージの権限や、PATに関するパッケージ関連のスコープ、Actionsのワークフローの権限の管理についての詳しい情報は、「[GitHub Packagesの権限について](/packages/learn-github-packages/about-permissions-for-github-packages)」を参照してください。
+
+### コンテナイメージの可視性とアクセス権限
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### 個人アカウントにコンテナイメージへのアクセス権限を設定する
+
+ユーザアカウントが所有するコンテナイメージに対する管理者権限がある場合には、他のユーザに読み取り、書き込み、管理者ロールを割り当てることができます。 これらの権限ロールに関する詳しい情報については、[コンテナイメージの可視性とアクセス権限](#visibility-and-access-permissions-for-container-images)」を参照してください。
+
+パッケージがプライベートもしくはインターナルで、Organizationによって所有されているなら、あなたにできることは他のOrganizationメンバーやTeamにアクセス権を与えることだけです。
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 Team には、ユーザアカウントが所持するコンテナイメージのアクセス権限を与えることができません。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png)
+1. ユーザ名または Team 名の隣にある [Role] のドロップダウンメニューで、付与する権限レベルを選択します。 ![コンテナアクセス権のオプション](/assets/images/help/package-registry/container-access-control-options.png)
+
+選択したユーザには自動的にアクセス権限が与えられ、招待を承諾する必要はありません。
+
+### Organization にコンテナイメージへのアクセス権限を設定する
+
+Organization が所有するコンテナイメージに対する管理者権限がある場合には、他のユーザや Team に読み取り、書き込み、管理者ロールを割り当てることができます。 これらの権限ロールに関する詳しい情報については、[コンテナイメージの可視性とアクセス権限](#visibility-and-access-permissions-for-container-images)」を参照してください。
+
+パッケージがプライベートもしくはインターナルで、Organizationによって所有されているなら、あなたにできることは他のOrganizationメンバーやTeamにアクセス権を与えることだけです。
+
+Organization イメージコンテナに対しては、Organization の管理者がパッケージを有効にしないと、可視性をパブリックに設定できません。 詳しい情報については「[コンテナレジストリでの改善されたコンテナサポートの有効化](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)」を参照してください。
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 また、Organization から Team 名を入力して、全 Team メンバーにアクセスを付与することもできます。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png)
+1. ユーザ名または Team 名の隣にある [Role] のドロップダウンメニューで、付与する権限レベルを選択します。 ![コンテナアクセス権のオプション](/assets/images/help/package-registry/container-access-control-options.png)
+
+選択したユーザや Team には自動的にアクセス権限が与えられ、招待を承諾する必要はありません。
+
+### リポジトリからコンテナイメージへのアクセスの継承
+
+{% data variables.product.prodname_actions %}ワークフローを通じたパッケージ管理を単純化するには、デフォルトでリポジトリのアクセス権をコンテナイメージが継承できるようにすることができます。
+
+パッケージのワークフローが保存されているリポジトリのアクセス権限を継承する場合、リポジトリの権限を通じてパッケージへのアクセスを調整できます。
+
+リポジトリが同期されると、パッケージの詳細なアクセス設定にはアクセスできなくなります。 詳細なパッケージのアクセス設定を通じてパッケージの権限をカスタマイズするには、まず同期されたリポジトリを取り除かなければなりません。
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. "Repository source（リポジトリソース）"の下で、**Inherit access from repository (recommended)（アクセスをリポジトリから継承（推奨））**を選択してください。 ![リポジトリアクセスの継承チェックボックス](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### パッケージへのワークフローのアクセスの確保
+
+{% data variables.product.prodname_actions %}ワークフローがパッケージに確実にアクセスできるようにするためには、ワークフローが保存されているリポジトリに対する明示的なアクセスを与えなければなりません。
+
+指定するリポジトリは、パッケージのソースコードが保存されているリポジトリである必要はありません。 パッケージに対して複数のリポジトリワークフローにアクセスを与えることができます。
+
+{% note %}
+
+**ノート:** **Actionsのアクセス**メニューオプションを通じてコンテナイメージをリポジトリと同期することは、コンテナをリポジトリに接続することとは異なります。 リポジトリのコンテナへのリンクに関する詳しい情報については、「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。
+
+{% endnote %}
+
+#### ユーザアカウントが所有するコンテナイメージへの{% data variables.product.prodname_actions %}のアクセス
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. ひだりのサイドバーで**Actions access（Actionsのアクセス）**をクリックしてください。 ![左メニューの"Actionsアクセス"オプション](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. ワークフローがコンテナパッケージに確実にアクセスできるようにするには、ワークフローが保存されるリポジトリを追加しなければなりません。 **Add repository（リポジトリの追加）**をクリックし、追加したいリポジトリを検索してください。 !["リポジトリの追加"ボタン](/assets/images/help/package-registry/add-repository-button.png)
+3. "role（ロール）"ドロップダウンメニューを使い、コンテナイメージに対してリポジトリに持たせたいデフォルトのアクセスレベルを選択してください。 ![リポジトリに付与する権限アクセスレベル](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+コンテナイメージへのアクセスをさらにカスタマイズするには、「[個人アカウントのためのコンテナイメージへのアクセスの設定](#configuring-access-to-container-images-for-your-personal-account)」を参照してください。
+
+#### Organizationが所有するコンテナイメージへの{% data variables.product.prodname_actions %}のアクセス
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. ひだりのサイドバーで**Actions access（Actionsのアクセス）**をクリックしてください。 ![左メニューの"Actionsアクセス"オプション](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. **Add repository（リポジトリの追加）**をクリックし、追加したいリポジトリを検索してください。 !["リポジトリの追加"ボタン](/assets/images/help/package-registry/add-repository-button.png)
+3. "role（ロール）"ドロップダウンメニューを使い、リポジトリのメンバーからコンテナイメージに対して持たせたいデフォルトのアクセスレベルを選択してください。 外部のコラボレータは含まれません。 ![リポジトリに付与する権限アクセスレベル](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+コンテナイメージへのアクセスをさらにカスタマイズするには、「[Organizationのためのコンテナイメージへのアクセスの設定](#configuring-access-to-container-images-for-an-organization)」を参照してください。
+
+### 個人アカウントにコンテナイメージの可視性を設定する
+
+パッケージを最初に公開する際のデフォルトの可視性はプライベートで、パッケージを表示できるのは公開したユーザだけです。 アクセス設定を変更することで、プライベートやパブリックなコンテナイメージのアクセス権限を変更できます。
+
+パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. [Danger Zone] の下で、可視性の設定を選択します。
+    - あらゆる人がコンテナイメージを表示できるようにするには、[**Make public**] をクリックします。
+    {% warning %}
+
+    **警告:** いったんパッケージをパブリックにすると、プライベートに戻すことはできません。
+
+    {% endwarning %}
+    - 指定したユーザだけがコンテナイメージを表示できるようにするには、[**Make private**] をクリックします。 ![コンテナ可視性のオプション](/assets/images/help/package-registry/container-visibility-option.png)
+
+### Organizationメンバーのためのコンテナ作成の可視性
+
+デフォルトでは、Organizationのメンバーが公開できるコンテナの可視性を選択できます。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. 左側にある [**Packages**] をクリックします。
+6. "Container creation（コンテナ作成）"の下で、パブリック、プライベート、インターナルのコンテナイメージの作成を有効化するかを選択してください。
+    - Organization のメンバーがパブリックのコンテナイメージを作成できるようにするには、[**Public**] をクリックします。
+    - Organization のメンバーに、Organization のメンバーのみが表示できるプライベートコンテナイメージの作成ができるようにするには、[**Private**] をクリックします。 プライベートコンテナイメージの可視性については、さらに細かくカスタマイズできます。
+    - **{% data variables.product.prodname_ghe_cloud %}のみ:** Organizationのメンバーが他のOrganizationのメンバーにだけ見えるインターナルコンテナイメージを作成できるようにするには、**Internal（インターナル）**をクリックしてください。 ![Organizationのメンバーが公開するコンテナイメージの可視性オプション](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### Organization にコンテナイメージの可視性を設定する
+
+パッケージを最初に公開する際のデフォルトの可視性はプライベートで、パッケージを表示できるのは公開したユーザだけです。 アクセス設定を使用して、コンテナイメージに対するさまざまなアクセスロールをユーザや Team に付与できます。
+
+パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。
+
+Organization イメージコンテナに対しては、Organization の管理者がパブリックパッケージを有効にしないと、可視性をパブリックに設定できません。 詳しい情報については「[コンテナレジストリでの改善されたコンテナサポートの有効化](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)」を参照してください。
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. [Danger Zone] の下で、可視性の設定を選択します。
+    - あらゆる人がコンテナイメージを表示できるようにするには、[**Make public**] をクリックします。
+    {% warning %}
+
+    **警告:** いったんパッケージをパブリックにすると、プライベートに戻すことはできません。
+
+    {% endwarning %}
+    - 指定したユーザだけがコンテナイメージを表示できるようにするには、[**Make private**] をクリックします。 ![コンテナ可視性のオプション](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..c423ec7568
--- /dev/null
+++ b/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: リポジトリのパッケージへの接続
+intro: 'リポジトリを{% data variables.product.prodname_dotcom %}上のコンテナイメージに接続できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+リポジトリをパッケージに接続することによって、パッケージのランディングページには、READMEなどのリポジトリからの情報やリンクが表示されるようになります。
+
+### リポジトリを{% data variables.product.prodname_dotcom %}上のユーザが所有するパッケージに接続する
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### リポジトリを{% data variables.product.prodname_dotcom %}上のOrganizationが所有するパッケージに接続する
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### コマンドラインを使ってリポジトリをコンテナイメージに接続する
+
+1. Dockerfile に以下の行を追加します。`OWNER` と `REPO` は、あなたの情報に置き換えてください。
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ たとえば、あなたのユーザ名が `monalisa` で、`my-repo` を所有している場合は、以下の行を Dockerfile に追加します。
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ 詳しい情報については、公式の Docker ドキュメンテーションの「[LABEL](https://docs.docker.com/engine/reference/builder/#label)」、および `opencontainers/image-spec` リポジトリの「[事前定義されたアノテーションキー](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)」を参照してください。
+
+2. あなたのコンテナイメージを構築します。 この連では、カレントディレクトリ内の Dockerfile からイメージを構築し、イメージ名を `hello_docker` とします。
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. 必要に応じて、タグ付けする Docker イメージの情報を確認します。
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Docker イメージを任意のイメージ名とホスティング先でタグ付けします。
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  例:
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. まだ{% data variables.product.prodname_container_registry %}で認証を受けていなければ、受けてください。 詳しい情報については「[{% data variables.product.prodname_container_registry %}で認証を受ける](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)」を参照してください。
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. コンテナイメージを{% data variables.product.prodname_container_registry %}にプッシュしてください。
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  例:
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/ja-JP/content/packages/learn-github-packages/index.md b/translations/ja-JP/content/packages/learn-github-packages/index.md
index fa637c6b05..5a488f1fc4 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/index.md
+++ b/translations/ja-JP/content/packages/learn-github-packages/index.md
@@ -1,7 +1,7 @@
 ---
 title: GitHub Packages について学ぶ
 shortTitle: GitHub Packages について学ぶ
-intro: '{% data variables.product.prodname_registry %} への新しいパッケージの公開など、GitHub Packages について詳しい情報を掲載しています。'
+intro: '新しいパッケージの{% data variables.product.prodname_registry %}での公開、既存のパッケージの表示とインストール、特殊な環境での既存のパッケージの削除を含む、GitHubでのパッケージの使い方についてさらに知ることができます。'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
   - /github/managing-packages-with-github-packages/publishing-and-managing-packages
@@ -17,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..bc08b2aadb
--- /dev/null
+++ b/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: パッケージをインストールする
+intro: '{% data variables.product.prodname_registry %}からパッケージをインストールし、そのパッケージを自分のプロジェクトの依存関係として使うことができます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### パッケージのインストールについて
+
+{% data variables.product.product_name %}を検索して、自分のプロジェクトにインストールできるパッケージを{% data variables.product.prodname_registry %}で見つけることができます。 詳しい情報については「[パッケージを{% data variables.product.prodname_registry %}で検索する](/github/searching-for-information-on-github/searching-for-packages)」を参照してください。
+
+パッケージを見つけたなら、そのパッケージの説明と、パッケージのページにあるインストールと利用方法の指示を読むことができます。
+
+### パッケージをインストールする
+
+以下の同じ一般的なガイドラインに従って、{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}サポートされているいずれかのパッケージのクライアント{% else %}インスタンスで有効化しているパッケージのタイプ{% endif %}を使い、{% data variables.product.prodname_registry %} からパッケージをインストールできます。
+
+1. 使用するパッケージクライアントについての指示に従って、{% data variables.product.prodname_registry %}の認証をしてください。 詳しい情報については「[GitHub Packagesでの認証](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)」を参照してください。
+2. 使用するパッケージクライアントに関する指示に従って、パッケージをインストールしてください。
+
+使用するパッケージクライアントに特有の指示については、「[{% data variables.product.prodname_registry %}の利用](/packages/working-with-a-github-packages-registry)」を参照してください。
diff --git a/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..39097cefd1
--- /dev/null
+++ b/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,131 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately {% if currentVersion == "github-ae@latest" %} for specified users or internally for your enterprise{% else %}or publicly{% endif %} and use packages as dependencies in your projects.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% if currentVersion != "github-ae@latest" %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
+
+You can integrate {% data variables.product.prodname_registry %} with {% data variables.product.product_name %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)."
+
+#### Overview of package permissions and visibility
+
+|                    |        |
+|--------------------|--------------------|
+| Permissions        | {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |
+| Visibility         | {% data reusables.package_registry.public-or-private-packages %} |
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About billing for {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+{% endif %}
+
+### Supported clients and formats
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
+#### Support for package registries
+
+| Language | Description | Package format | Package client |
+| --- | --- | --- | --- |
+| JavaScript | Node package manager | `package.json`  | `npm` |
+| Ruby |  RubyGems package manager | `Gemfile` |  `gem` |
+| Java | Apache Maven project management and comprehension tool | `pom.xml` |  `mvn` |
+| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts`  | `gradle`  |
+| .NET | NuGet package management for .NET | `nupkg`  |  `dotnet` CLI |
+| N/A | Docker container management | `Dockerfile` | `Docker` |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**Note:** Docker is not supported when subdomain isolation is disabled.
+
+{% endnote %}
+
+For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)."
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Managing packages
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. Or for repo-scoped packages, you can delete a version of a private package using GraphQL.
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
+
+### Contacting support
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use the [feedback form for {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages).
+
+Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if:
+
+* You experience anything that contradicts the documentation
+* You encounter vague or unclear errors
+* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information
+
+{% else %}
+If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators.
+
+{% endif %}
diff --git a/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md b/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..585af6eb5c
--- /dev/null
+++ b/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: パッケージの表示
+intro: リポジトリに公開されたパッケージの詳細を表示し、Organization またはユーザごとに結果を絞り込むことができます。
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### リポジトリのパッケージを表示する
+
+パッケージを見ることができるかどうかは、いくつかの要素に依存します。 デフォルトでは、公開したパッケージはすべて見ることができます。
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### リポジトリのパッケージを表示する
+
+特定のリポジトリにあるパッケージを見つけて表示できます。
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Organization のパッケージを表示する
+
+自分が所属するOrganizationのリポジトリにあるパッケージを見つけて表示できます。
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. Organization 名の下で、 {% octicon "package" aria-label="The package icon" %} [**Packages**] をクリックします。
+{% data reusables.package_registry.navigate-to-packages %}
+
+### パッケージを表示する
+
+すべてのOrganization及びリポジトリで、自分が公開したパッケージを見つけて表示できます。
+
+{% data reusables.profile.access_profile %}
+2. プロフィールページの一番上のメインナビゲーションにある [**Packages（パッケージ）**] をクリックします。 ![プロジェクトタブ](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### 参考リンク
+
+- [パッケージの検索](/github/searching-for-information-on-github/searching-for-packages)
diff --git a/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..9a077e61c3
--- /dev/null
+++ b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: GitHub PackagesとGitHub Actionsについて
+intro: '{% data variables.product.prodname_actions %}ワークフローを通じてパッケージを管理する基礎を学んでください。'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..e02367f0ef
--- /dev/null
+++ b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: パッケージ公開のワークフローの例
+intro: カスタムワークフローを扱い始めるために、パッケージを公開するワークフローのいくつかの例を確認してください。
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+ワークフローの例が、「[{% data variables.product.prodname_actions %}でのパッケージの公開とインストール](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)」あるいは以下の{% data variables.product.prodname_actions %}ガイドのいずれかにあります。
+
+  - [Node.jsパッケージの公開](/actions/guides/publishing-nodejs-packages)
+  - [Dockerイメージの公開](/actions/guides/publishing-docker-images)
+  - [MavenでのJavaのパッケージの公開](/actions/guides/publishing-java-packages-with-maven)
+  - [GradleでのJavaパッケージの公開](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..cfbe4b8206
--- /dev/null
+++ b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: GitHub Actionsワークフローを利用したGitHub Packagesの管理
+shortTitle: ワークフローでのGitHub Packagesの管理
+intro: コードのビルド、テスト、デプロイを行えるカスタムのワークフローを構築することによって、安全にパッケージの公開と利用ができます。
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..a370519036
--- /dev/null
+++ b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,455 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)."
+
+{% endif %}
+
+#### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+### About permissions and package access for repository-owned packages
+
+{% note %}
+
+**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.
+
+{% endnote %}
+
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
+
+{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About permissions and package access for {% data variables.product.prodname_container_registry %}
+
+The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions.
+
+All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+### Default permissions and access settings for containers modified through workflows
+
+When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
+
+For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
+- The container inherits the visibility and permissions model of the repository where the workflow is run.
+- Repository admins where the workflow is run become the admins of the container once the container is created.
+
+These are more examples of how default permissions work for workflows that manage packages.
+
+| {% data variables.product.prodname_actions %} workflow task | Default permissions and access |
+|----|----|
+| Download an existing container | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br>
+| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.
+| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.
+
+You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publishing a package using an action
+
+You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}:
+
+- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  The relevant settings are explained in the following table:
+
+  <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configures the <code>Create and publish a package</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    This job installs NPM and uses it to build the app.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Creates a new step called <code>Build container image</code>. This step runs as part of the <code>build-and-push-image</code> job. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sends the required parameters to the <code>build-push-action</code> action. This are defined in the subsequent lines.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the password that is used to access {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace <code>YOUR-HOSTNAME</code> with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use <code>ghcr.io</code> as the hostname.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines which repository will host the resulting package, and sets the name of the published package. Replace <code>octo-image</code> with the name you want for your package.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the first seven characters of the commit's SHA. For example, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the git ref. This can be the name of the branch used to create the package.
+  </td>
+  </tr>
+  </table>
+
+- This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
+- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
+
+
+### Installing a package using an action
+
+You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Upgrading a workflow that accesses `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**.
+  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add.
+   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image.
+  ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md
index a678f0b053..02662fff4a 100644
--- a/translations/ja-JP/content/packages/quickstart.md
+++ b/translations/ja-JP/content/packages/quickstart.md
@@ -71,7 +71,10 @@ versions:
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -95,7 +98,7 @@ versions:
 
 ### 公開したパッケージを表示する
 
-パッケージはリポジトリレベルで公開されます。 リポジトリ内のすべてのパッケージを表示し、特定のパッケージを検索できます。
+公開したすべてのパッケージは、見ることができます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ versions:
 
 ### 公開したパッケージをインストールする
 
-これでパッケージを公開できたので、プロジェクト全体で依存関係として利用できます。 詳しい情報については、「[{% data variables.product.prodname_registry %} で利用するために npm を設定する](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)」を参照してください。
+これでパッケージを公開できたので、プロジェクト全体で依存関係として利用できます。 詳しい情報については「[npmレジストリの利用](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)」を参照してください。
 
 ### 次のステップ
 
-ここで追加した基本的なワークフローは、リポジトリ内に新しいリリースが作成されるたびに実行されます。 ただし、これは {% data variables.product.prodname_registry %} でできることの一部にすぎません。 単一のワークフローで複数のレジストリにパッケージを公開する、ワークフローをトリガーしてマージされたプルリクエストなどさまざまなイベントで実行する、コンテナを管理するなど、いろいろなことができます。
+ここで追加した基本的なワークフローは、リポジトリ内に新しいリリースが作成されるたびに実行されます。 ただしこれは、{% data variables.product.prodname_registry %}でできることの手始めにすぎません。 単一のワークフローで複数のレジストリにパッケージを公開する、ワークフローをトリガーしてマージされたプルリクエストなどさまざまなイベントで実行する、コンテナを管理するなど、いろいろなことができます。
 
 {% data variables.product.prodname_registry %}と{% data variables.product.prodname_actions %}を組み合わせることで、プリケーション開発プロセスのほぼすべての要素を自動化するために役立ちます。 始める準備はできましたか？ 以下は、{% data variables.product.prodname_registry %}および{% data variables.product.prodname_actions %}で次のステップへ進むために役立つリソースです。
 
 - GitHub Packagesについての詳細なチュートリアル、「[{% data variables.product.prodname_registry %}を学ぶ](/packages/learn-github-packages)」
 - GitHub Actionsの詳細なチュートリアル、「[{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions)」
-- 特定の使用例とサンプルについては、「[ガイド](/packages/guides)」
+- 特定のユースケースと例のための「[{% data variables.product.prodname_registry %}レジストリの利用](/packages/working-with-a-github-packages-registry)」
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..7a772ac543
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: コンテナレジストリでの改善されたコンテナサポートの有効化
+intro: '{% data variables.product.prodname_container_registry %}を使うには、ユーザもしくはOrganizationアカウントで有効化しなければなりません。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**注釈:** {% data variables.product.prodname_container_registry %} は現在パブリックベータであり、変更されることがあります。 ベータ期間中は、ストレージおよび帯域幅の制限はありません。 詳しい情報については、「[{% data variables.product.prodname_registry %} の紹介](/packages/learn-github-packages/introduction-to-github-packages)」を参照してください。
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### 個人アカウントでの{% data variables.product.prodname_container_registry %}の有効化
+
+個人ユーザアカウントで{% data variables.product.prodname_container_registry %}を有効化すると、自分のユーザアカウントが所有する{% data variables.product.prodname_container_registry %}にコンテナを公開できます。
+
+Organization内で{% data variables.product.prodname_container_registry %}を使うには、Organizationのオーナーがこの機能をOrganizationのメンバーに対して有効化しなければなりません。
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. 左側にある [Improved container support] を選択し、[**Enable**] をクリックします。 ![改善されたコンテナサポート](/assets/images/help/settings/improved-container-support.png)
+
+### Organizationアカウントでの{% data variables.product.prodname_container_registry %}の有効化
+
+Organizationのオーナーもしくはメンバーがコンテナイメージを{% data variables.product.prodname_container_registry %}に公開できるようにするには、Organizationのオーナーがこの機能のプレビューをOrganizationに対して有効化しなければなりません。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. 左側にある [**Packages**] をクリックします。
+5. [Improved container support] の下で、[Enable improved container support] を選択し、[**Save**] をクリックします。 ![[Enable container registry support option] と [Save] ボタン](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. "Container creation（コンテナ作成）"の下で、パブリック、プライベート、インターナルのコンテナイメージの作成を有効化するかを選択してください。
+    - Organizationのメンバーがパブリックなコンテナイメージを作成できるようにするには、**Public（パブリック）**を選択してください。
+    - Organizationのメンバーが、他のOrganizationのメンバーにだけ見えるプライベートのコンテナイメージを作成できるようにするには、**Private（プライベート）**を選択してください。 プライベートコンテナイメージの可視性については、さらに細かくカスタマイズできます。 詳しい情報については「[パッケージのアクセス制御と可視性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。
+    - **{% data variables.product.prodname_ghe_cloud %}のみ:** Organizationメンバーが、他のOrganizationのメンバーにだけ見えるインターナルコンテナイメージを作成できるようにするには、**Internal（インターナル）**を選択してください。 ![Organizationのメンバーが公開するコンテナイメージの可視性オプション](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/index.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..78c774b610
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: GitHub Packagesレジストリの利用
+shortTitle: GitHub Packagesレジストリの利用
+intro: 'サポートされている{% data variables.product.prodname_registry %}レジストリの利用方法を学んでください。'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Docker、コンテナレジストリ、RubyGems、npm、Apache Maven、NuGet、Gradle のパッケージサポートを示す図](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Docker、RubyGems、npm、Apache Maven、Gradle、Nugetに対するパッケージサポートを示す図](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### 目次
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..1364893e45
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,126 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- Store container images within your organization and user account, rather than a repository.
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- Access public container images anonymously.
+
+|                   | Docker registry| {% data variables.product.prodname_container_registry %} |
+|-------------------|--------------------|----|
+| Hosting locations | You can host multiple Docker images in one repository. | You can host multiple container images in one organization or user account. |
+| Permissions       | Each image inherits the permissions of the repository where the image is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions.
+Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. |
+Anonymous access    | N/A | You can access public container images anonymously.
+Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### Billing changes
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. For more information, see "[About  billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+### Domain changes
+
+The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`.
+
+| Registry  | Example URL |
+|-----------------|-------------|
+| {% data variables.product.prodname_registry %} Docker registry |  `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME`
+| {% data variables.product.prodname_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME`
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}.
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Migrating a Docker image using the Docker CLI
+
+To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine.
+
+1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward.
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization.
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name.
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. Sign in to the new {% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### Updating your {% data variables.product.prodname_actions %} workflow
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers.
+
+1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)."
+
+2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`.
+
+3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+
+4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}.
+
+#### Example of updated workflow
+
+If part of your workflow accessed a Docker image hosted by the Docker registry like this:
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this:  
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..c0efd9f17d
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Apache Mavenレジストリの利用
+intro: '{% data variables.product.prodname_registry %} にパッケージを公開するよう Apache Mavenを設定し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係としてJavaプロジェクトで利用できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+### {% data variables.product.prodname_registry %} への認証を行う
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 個人アクセストークンでの認証
+
+{% data reusables.package_registry.required-scopes %}
+
+*~/.m2/settings.xml*ファイルを編集して個人アクセストークンを含めることで、Apache Mavenで{% data variables.product.prodname_registry %}の認証を受けられます。 *~/.m2/settings.xml*ファイルがないなら新しく作成してください。
+
+`servers`タグの中に、子として`server`タグを`id`付きで追加し、*USERNAME*を{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*を個人アクセストークンで置き換えてください。
+
+`repositories`の中で、リポジトリの`id`をクレデンシャルを含む`server`タグに追加した`id`にマッピングして、リポジトリを設定してください。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* を {% data variables.product.product_location %} のホスト名に、{% endif %}*OWNER* をリポジトリを所有するユーザもしくはOrganizationの名前に置き換えます。 大文字はサポートされていないため、仮に{% data variables.product.prodname_dotcom %}のユーザあるいはOrganization名が大文字を含んでいても、リポジトリオーナーには小文字を使わなければなりません。
+
+複数のリポジトリとやりとりをしたい場合には、それぞれのリポジトリを`repositories`タグの子の個別の`repository`に追加し、それぞれの`id`を`servers` タグのクレデンシャルにマッピングできます。
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### パッケージを公開する
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+同じリポジトリに複数のパッケージを公開したい場合には、そのリポジトリのURLを*pom.xml*ファイルの`<distributionManagement>`要素に含めてください。 {% data variables.product.prodname_dotcom %} は、このこのフィールドを元にしてリポジトリを照合します。 リポジトリ名も`distributionManagement`要素の一部なので、複数のパッケージを同じリポジトリに公開するための追加手順はありません。
+
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+
+1. パッケージディレクトリにある*pom.xml*ファイルの`distributionManagement`要素を編集し、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME*を{% data variables.product.product_location %}のホスト名で、{% endif %}`OWNER`をリポジトリを所有するユーザもしくはOrganizationアカウント名で、`REPOSITORY`をプロジェクトを含むリポジトリ名で置き換えてください。{% if enterpriseServerVersions contains currentVersion %}
+
+  もしもインスタンスでSubdomain Isolationが有効化されているなら:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. パッケージを公開します。
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### パッケージをインストールする
+
+{% data variables.product.prodname_registry %}からApache Mavenパッケージをインストールするには、*pom.xml*ファイルを編集してパッケージを依存関係として含めてください。 複数のリポジトリからパッケージをインストールしたい場合は、それぞれについて`repository`タグを追加してください。 プロジェクト内での*pom.xml*ファイルの利用に関する詳しい情報については、Apache Mavenドキュメンテーション中の「[ Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)」を参照してください。
+
+{% data reusables.package_registry.authenticate-step %}
+2. パッケージの依存関係をプロジェクトの*pom.xml*ファルの`dependencies`要素に追加し、`com.example:test`をパッケージで置き換えてください。
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. パッケージをインストールします。
+
+  ```shell
+  $ mvn install
+  ```
+
+### 参考リンク
+
+- 「[Gradleレジストリの利用](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)」
+- 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..17833a8a32
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: コンテナレジストリの利用
+intro: 'Docker及びOCIイメージを、パッケージの名前空間`https://ghcr.io`を使用する{% data variables.product.prodname_container_registry %}に保存して管理できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### {% data variables.product.prodname_container_registry %}サポートについて
+
+コンテナイメージをプッシュ及びプルするためには、Organizationの管理者もしくは個人アカウントのオーナーは、{% data variables.product.prodname_container_registry %}を有効化しなければなりません。 詳しい情報については「[{% data variables.product.prodname_container_registry %}での改善されたコンテナサポートの有効化](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)」を参照してください。
+
+Dockerイメージをインストールあるいは公開する際に、コンテナレジストリはWindowsイメージのような外部レイヤーをサポートします。
+
+現在のところ、{% data variables.product.prodname_container_registry %} では以下のコンテナフォーマットをサポートしています。
+
+* [DDocker イメージマニフェスト V2、スキーマ 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) 仕様](https://github.com/opencontainers/image-spec)
+
+### {% data variables.product.prodname_container_registry %}での認証
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### コンテナイメージをプッシュする
+
+以下の例では、`IMAGE-NAME` の最新バージョンをプッシュします。
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+以下の例では、イメージのバージョン `2.5` をプッシュします。
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+パッケージを最初に公開する際のデフォルトの可視性はプライベートです。 可視性を変更したりアクセス権限を設定するには、「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。
+
+### コンテナイメージをプルする
+
+#### ダイジェストによるプル
+
+常に同一のイメージを使用するため、`digest` SHA 値でプルするコンテナイメージのバージョンを指定できます。
+
+1. `docker inspect` または `docker pull` を使用してダイジェスト SHA 値を調べ、その SHA 値を `Digest:` の後にコピーします。
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. 必要に応じてローカルでイメージを削除します。
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+3. イメージ名の後に `@YOUR_SHA_VALUE` を付けてコンテナイメージをプルします。
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### 名前によるプル
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### 名前とバージョンによるプル
+
+名前と `1.14.1` バージョンタグにより Docker CLI でイメージをプルする例を以下に示します。
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### 名前と最新バージョンによるプル
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### コンテナイメージを構築する
+
+以下の例では `hello_docker` イメージを構築します。
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### コンテナイメージにタグ付けする
+
+1. タグ付けする Docker イメージの ID を調べます。
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. イメージ ID を使用して、Docker イメージを任意のイメージ名とホスティング先でタグ付けします。
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..c7ffb879f2
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,272 @@
+---
+title: Dockerレジストリの利用
+intro: 'パッケージの名前空間として`https://docker.pkg.github.com`を使う{% data variables.product.prodname_registry %} Dockerレジストリを利用して、Dockerイメージをプッシュ及びプルできます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Dockerサポートについて
+
+Dockerイメージをインストールあるいは公開する際に、Dockerレジストリは現在Windowsイメージのような外部レイヤーをサポートしません。
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+Docker レジストリを {% data variables.product.prodname_registry %} で使用する前に、{% data variables.product.product_location %} のサイト管理者がインスタンスに対し Docker のサポートとand Subdomain Isolation を有効化する必要があります。 詳しい情報については、「[Enterprise 向けの GitHub Packages を管理する](/enterprise/admin/packages)」を参照してください。
+
+{% endif %}
+
+### {% data variables.product.prodname_registry %} への認証を行う
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 個人アクセストークンでの認証
+
+{% data reusables.package_registry.required-scopes %}
+
+`docker` loginコマンドを使い、Dockerで{% data variables.product.prodname_registry %}の認証を受けることができます。
+
+クレデンシャルをセキュアに保つ貯めに、個人アクセストークンは自分のコンピュータのローカルファイルに保存し、ローカルファイルからトークンを読み取るDockerの`--password-stdin`フラグを使うことをおすすめします。
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+{% endif %}
+{% raw %}
+ ```shell
+ $ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# <em>OWNER/REPO/IMAGE_NAME</em>でイメージにタグ付けする
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# {{ site.data.variables.product.prodname_registry }}にイメージをプッシュ
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+この例の login コマンドを使うには、`USERNAME` を {% data variables.product.product_name %} ユーザ名に、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},`HOSTNAME` を {% data variables.product.product_location %} の URL に、{% endif %}`~/TOKEN.txt` {% data variables.product.product_name %} の個人アクセストークンへのファイルパスに置き換えてください。
+
+詳しい情報については「[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)」を参照してください。
+
+### イメージを公開する
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**注釈:** イメージ名には小文字のみを使用する必要があります。
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} は、リポジトリごとに複数の最上位 Docker イメージをサポートしています。 リポジトリは任意の数のイメージタグを持つことができます。 10GB以上のDockerイメージの公開やインストールの際には、サービスのパフォーマンスが低下するかもしれず、各レイヤーは5GBが上限です。 詳しい情報については、Dockerのドキュメンテーションの「[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)」を参照してください。
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. `docker images`を使って、Dockerイメージのイメージ名とIDを確認してください。
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. DockerイメージIDを使い、Dockerイメージにタグ付けしてください。*OWNER*をリポジトリを所有するユーザもしくはOrganizationアカウントの名前で、*REPOSITORY*をプロジェクトを含むリポジトリの名前で、*IMAGE_NAME*をパッケージもしくはイメージの名前で、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME*を{% data variables.product.product_location %}のホスト名で、{% endif %}*VERSION*をビルドの時点のパッケージバージョンで置き換えてください。
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+  {% endif %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. まだパッケージのDockerイメージをビルドしていないならビルドしてください。*OWNER*をリポジトリを所有するユーザもしくはOrganizationアカウントの名前で、*REPOSITORY*をプロジェクトを含むリポジトリの名前で、*IMAGE_NAME*をパッケージもしくはイメージの名前で、*VERSION*をビルド時点のパッケージバージョンで、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME*を{% data variables.product.product_location %}のホスト名で、{% endif %}もしもイメージが現在の作業ディレクトリ中になければ*PATH*をイメージへのパスで置き換えてください。
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. {% data variables.product.prodname_registry %}にイメージを公開してください。
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **ノート:** イメージのプッシュは`IMAGE_NAME:SHA`を使うのではなく、`IMAGE_NAME:VERSION`を使って行ってください。
+
+  {% endnote %}
+
+#### Dockerイメージのプッシュの例
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+この例では、インスタンスの Subdomain Isolation が有効化されていると仮定します。
+{% endif %}
+
+`monalisa`イメージのバージョン1.0を、イメージIDを使って`octocat/octo-app`に公開できます。
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# <em>OWNER/REPO/IMAGE_NAME</em>でイメージにタグ付けする
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# {% data variables.product.prodname_registry %}にイメージをプッシュ
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+新しいDockerイメージを初めて公開し、`monalisa`という名前にできます。
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> でイメージを構築
+# Dockerfileはカレントワーキングディレクトリ (.)にあるものとする
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### イメージをダウンロードする
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+`docker pull`コマンドを使って、Dockerイメージを{% data variables.product.prodname_registry %}からインストールできます。*OWNER*をリポジトリを所有しているユーザあるいはOrganizationのアカウント名で、*REPOSITORY*をプロジェクトを含むリポジトリ名で、*IMAGE_NAME*をパッケージもしくはイメージの名前で、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME*を{% data variables.product.product_location %}のホスト名で、{% endif %}*TAG_NAME*をインストールするイメージのタグで置き換えます。
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**ノート:** イメージのプルは`IMAGE_NAME:SHA`を使うのではなく、`IMAGE_NAME:VERSION`を使って行ってください。
+
+{% endnote %}
+
+### 参考リンク
+
+- 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..7b928620fd
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Gradleレジストリの利用
+intro: 'パッケージを{% data variables.product.prodname_registry %} Gradleレジストリに公開し、{% data variables.product.prodname_registry %}に保存されているパッケージをJavaプロジェクト中で依存関係として使うようにGradleを設定できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+### {% data variables.product.prodname_registry %} への認証を行う
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### 個人アクセストークンでの認証
+
+{% data reusables.package_registry.required-scopes %}
+
+Gradle GroovyもしくはKotlin DSLを使って、Gradleで{% data variables.product.prodname_registry %}に認証を受けることができます。それには、*build.gradle*ファイル（Gradle Groovy）もしくは*build.gradle.kts*ファイル（Kotlin DSL）ファイルを編集して、個人アクセストークンを含めます。 リポジトリ中の単一のパッケージもしくは複数パッケージを認識するようにGradle Groovy及びKotlin DSLを設定することもできます。
+
+{% if enterpriseServerVersions contains currentVersion %}
+*REGISTRY-URL* をインスタンスの Maven レジストリの URL に置き換えます。 インスタンスで Subdomain Isolation が有効になっている場合は、`maven.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/maven` を使用します。 In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+*REGISTRY-URL* を企業の Maven レジストリである `maven.HOSTNAME` の URL に置き換えます。 *HOSTNAME*を{% data variables.product.product_location %}のホスト名で置き換えてください。
+{% endif %}
+
+*USERNAME*を{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*を個人アクセストークンで、*REPOSITORY*を公開したいパッケージを含むリポジトリの名前で、*OWNER*をリポジトリを所有する{% data variables.product.prodname_dotcom %}のユーザもしくはOrganizationアカウント名で置き換えてください。 大文字はサポートされていないため、仮に{% data variables.product.prodname_dotcom %}のユーザあるいはOrganization名が大文字を含んでいても、リポジトリオーナーには小文字を使わなければなりません。
+
+{% note %}
+
+**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} 例として「[{% data variables.product.prodname_registry %}で使用するためのApache Mavenの設定](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)」を参照してください。
+
+{% endnote %}
+
+##### リポジトリ中の単一のパッケージのためにGradle Groovyを使う例
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### 同じリポジトリ中の複数のパッケージのためにGradle Groovyを使う例
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### 同じリポジトリ中の単一パッケージのためにKotlin DSLを使う例
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### 同じリポジトリ中の複数パッケージのためにKotlin DSLを使う例
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            register<MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+### パッケージを公開する
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test` {% data variables.product.prodname_registry %}リポジトリ内の`com.example.test`という名前のパッケージを公開します。
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. パッケージを作成した後、そのパッケージを公開できます。
+
+  ```shell
+   $ gradle publish
+  ```
+
+### パッケージをインストールする
+
+プロジェクトの依存関係としてパッケージを追加することで、パッケージをインストールできます。 詳しい情報については、Gradleのドキュメンテーションの 「[ Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)」を参照してください。
+
+{% data reusables.package_registry.authenticate-step %}
+2. *build.gradle*ファイル（Gradle Groovy）もしくは*build.gradle.kts*ファイル（Kotlin DSL）にパッケージの依存関係を追加してください。
+
+  Gradle Groovyの例：
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  Kotlin DSLの例：
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. *build.gradle*ファイル（Gradle Groovy）もしくは*build.gradle.kts*ファイル（Kotlin DSL）にmavenプラグインを追加してください。
+
+  Gradle Groovyの例：
+  ```shell
+  plugins {
+      id 'maven'
+  }
+  ```
+  Kotlin DSLの例：
+  ```shell
+  plugins {
+      `maven`
+  }
+  ```
+
+  3. パッケージをインストールします。
+
+  ```shell
+  $ gradle install
+  ```
+
+### 参考リンク
+
+- 「[ Apache Mavenレジストリの利用](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)」
+- 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..479bbf385f
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,218 @@
+---
+title: npmレジストリの利用
+intro: '{% data variables.product.prodname_registry %} にパッケージを公開するよう npm を設定し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係として npm プロジェクトで利用できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### 公開したnpmバージョンに対する制限
+
+{% data variables.product.prodname_registry %}に公開したnpmパッケージのバージョンが1000を超える場合、使用中にパフォーマンスの問題やタイムアウトが発生することがあります。
+
+サービスのパフォーマンスを向上させるため、将来的には1,000を超えるパッケージのバージョンを{% data variables.product.prodname_dotcom %}に公開できなくなります。 この制限に達しないバージョンであれば、今後も読み取り可能です。
+
+この制限に達した場合は、パッケージのバージョンを削除するよう検討するか、サポートにお問い合わせください。 この制限が施行されるようになると、ドキュメントが更新され、この制限を回避する方法が記載されることになります。 詳しい情報については、 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」または「[サポートへの連絡](/packages/learn-github-packages/about-github-packages#contacting-support)」を参照してください。
+
+{% endif %}
+
+### {% data variables.product.prodname_registry %} への認証を行う
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 個人アクセストークンでの認証
+
+{% data reusables.package_registry.required-scopes %}
+
+ユーザごとの*~/.npmrc*ファイルを編集して個人アクセストークンを含めるか、コマンドラインからユーザ名と個人アクセストークンを使ってnpmにログインすることによって、npmで{% data variables.product.prodname_registry %}の認証を受けられます。
+
+*~/.npmrc*ファイルに個人アクセストークンを追加して認証を受けるには、プロジェクトの*~/.npmrc*ファイルを編集して、以下の行を含めてください。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* は {% data variables.product.product_location %}のホスト名で、{% endif %}*TOKEN*は個人アクセストークンで置き換えてください。 *~/.npmrc*ファイルが存在しない場合は、新しく作成してください。
+
+{% if enterpriseServerVersions contains currentVersion %}
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+```shell
+$ npm login --registry=https://npm.pkg.github.com
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+npmにログインすることで認証を受けるには、`npm login`コマンドを使ってください。*USERNAME*は{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*は個人アクセストークンで、*PUBLIC-EMAIL-ADDRESS*はメールアドレスで置き換えてください。
+
+{% data variables.product.prodname_registry %}がnpmを使用するデフォルトのパッケージレジストリではなく、`npm audit` コマンドを使用する場合、{% data variables.product.prodname_registry %}への認証時には、パッケージの所有者権限と共に`--scope`フラグを使用することをおすすめします。
+
+{% if enterpriseServerVersions contains currentVersion %}
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### パッケージを公開する
+
+{% note %}
+
+**注釈:** パッケージ名およびスコープには小文字のみを使用する必要があります。
+
+{% endnote %}
+
+デフォルトでは、{% data variables.product.prodname_registry %}は*package.json*ファイルのnameフィールドで指定された{% data variables.product.prodname_dotcom %}のリポジトリにパッケージを公開します。 たとえば`@my-org/test`という名前のパッケージを{% data variables.product.prodname_dotcom %}リポジトリの`my-org/test`に公開します。 パッケージディレクトリに*README.md*ファイルを置くことで、パッケージリスティングページのためのまとめを追加できます。 詳しい情報については、npmのドキュメンテーション中の「[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)」及び「[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)」を参照してください。
+
+`URL`フィールドを*package.json*ファイルに含めることで、同じ{% data variables.product.prodname_dotcom %}のリポジトリに複数のパッケージを公開できます。 詳しい情報については「[同じリポジトリへの複数パッケージの公開](#publishing-multiple-packages-to-the-same-repository)」を参照してください。
+
+プロジェクト内にあるローカルの *.npmrc* ファイルか、*package.json* の `publishConfig` オプションを使って、スコープのマッピングを設定できます。 {% data variables.product.prodname_registry %}はスコープ付きのnpmパッケージのみをサポートしています。 スコープ付きパッケージには、`@owner/name` というフォーマットの名前が付いています。 スコープ付きパッケージの先頭には常に `@` 記号が付いています。 スコープ付きの名前を使うには、*package.json* の名前を更新する必要がある場合があります。 たとえば、`"name": "@codertocat/hello-world-npm"` のようになります。
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### ローカルの*.npmrc*ファイルを使ったパッケージの公開
+
+*.npmrc*ファイルを使って、プロジェクトのスコープのマッピングを設定できます。 *.npmrc*ファイル中で{% data variables.product.prodname_registry %} URLとアカウントオーナーを使い、{% data variables.product.prodname_registry %}がどこへパッケージリクエストをまわせばいいか把握できるようにしてください。 *.npmrc*を使う事で、他の開発者が{% data variables.product.prodname_registry %}の代わりにうっかりパッケージをnpmjs.orgに公開してしまうのを避けることができます。
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. プロジェクトの*package.json*中のパッケージ名を確認してください。 `name`フィールドは、スコープとパッケージの名前を含まなければなりません。 たとえば、パッケージの名前が "test" で、"My-org" {% data variables.product.prodname_dotcom %} Organizationに公開する場合、*package.json*の`name`フィールドは `@my-org/test`とする必要があります。
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### *package.json*ファイル中の`publishConfig`を利用したパッケージの公開
+
+*package.json*ファイル中の`publishConfig`要素を使い、パッケージを公開したいレジストリを指定できます。 詳しい情報についてはnpmドキュメンテーションの「[Configの公開](https://docs.npmjs.com/files/package.json#publishconfig)」を参照してください。
+
+1. パッケージの*package.json*ファイルを編集して、`publishConfig`エントリを含めてください。
+  {% if enterpriseServerVersions contains currentVersion %}
+  パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### 同じリポジトリへの複数パッケージの公開
+
+複数のパッケージを同じリポジトリに公開するには、{% data variables.product.prodname_dotcom %}リポジトリのURLを各パッケージの*package.json*ファイル中の`repository`フィールドに含めることができます。
+
+リポジトリのURLが正しいことを確認するには、REPOSITORYを公開したいパッケージを含むリポジトリ名で、OWNERをリポジトリを所有している{% data variables.product.prodname_dotcom %}のユーザもしくはOrganizationアカウント名で置き換えてください。
+
+{% data variables.product.prodname_registry %} は、パッケージ名の代わりに、このURLを元にしてリポジトリを照合します。
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### パッケージをインストールする
+
+プロジェクトの*package.json*ファイルに依存関係としてパッケージを追加することで、{% data variables.product.prodname_registry %}からパッケージをインストールできます。 プロジェクトにおける *package.json* の利用に関する詳しい情報については、npm ドキュメンテーションの「[package.json を使って作業する](https://docs.npmjs.com/getting-started/using-a-package.json)」を参照してください。
+
+デフォルトでは、パッケージは1つのOrganizationから追加できます。 詳しい情報については「[他のOrganizationからのパッケージのインストール](#installing-packages-from-other-organizations)」を参照してください。
+
+また、*.npmrc*ファイルをプロジェクトに追加して、パッケージのインストールのすべてのリクエストが{% data variables.product.prodname_registry %}を経由するようにしなければなりません。 すべてのパッケージリクエストを{% data variables.product.prodname_registry %}を経由させると、*npmjs.com*からスコープ付き及びスコープ付きではないパッケージの両方を利用できます。 詳しい情報については npm ドキュメンテーションの「[npm-scope](https://docs.npmjs.com/misc/scope)」を参照してください。
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. インストールしているパッケージを使うには、プロジェクトの*package.json*を設定してください。 {% data variables.product.prodname_registry %}のためにパッケージの依存関係を*package.json*ファイルに追加するには、`@my-org/server`というように完全なスコープ付きのパッケージ名を指定してください。 *npmjs.com*からのパッケージについては、`@babel/core`あるいは`@lodash`というような完全な名前を指定してください。 たとえば、以下の*package.json*は`@octo-org/octo-app`パッケージを依存関係として使っています。
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. パッケージをインストールします。
+
+  ```shell
+  $ npm install
+  ```
+
+#### 他のOrganizationからのパッケージのインストール
+
+デフォルトでは、1つのOrganizationからのみ{% data variables.product.prodname_registry %}パッケージを利用できます。 パッケージリクエストを複数のOrganizationおよびユーザにルーティングしたい場合、*.npmrc*ファイルに行を追加できます。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME*を、{% data variables.product.product_location %}のホスト名で、{% endif %}*OWNER*を、プロジェクトを含むリポジトリを所有しているユーザもしくはOrganizationアカウント名で置き換えてください。
+
+{% if enterpriseServerVersions contains currentVersion %}
+パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### 公式NPMレジストリを使用する
+
+{% data variables.product.prodname_registry %}では、{% data variables.product.prodname_ghe_server %}管理者がこの機能を有効化している場合、`registry.npmjs.com`の公式NPMにアクセスできます。 詳しい情報については、[公式NPMレジストリに接続する](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry)」を参照してください。
+{% endif %}
+
+### 参考リンク
+
+- 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..af29e3abb5
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,238 @@
+---
+title: NuGetレジストリの利用
+intro: '{% data variables.product.prodname_registry %} にNuGetパッケージを公開し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係として .Net プロジェクトで利用するよう`dotnet`コマンドラインインターフェース（CLI）を設定できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+### {% data variables.product.prodname_registry %} への認証を行う
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 個人アクセストークンでの認証
+
+{% data reusables.package_registry.required-scopes %}
+
+`dotnet`コマンドラインインターフェース（CLI）で{% data variables.product.prodname_registry %}に認証を受けるには、プロジェクトディレクトリに*nuget.config*ファイルを作成し、{% data variables.product.prodname_registry %}をソースとして`dotnet` CLIクライアントの`packageSources`の下に指定してください。
+
+以下のように置き換えてください。
+- `USERNAME`を{% data variables.product.prodname_dotcom %}上のユーザアカウント名で。
+- `TOKEN`を個人アクセストークンで。
+- `OWNER` を、プロジェクトを含むリポジトリを所有しているユーザまたはOrganizationアカウント名で。{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- `HOSTNAME` を、{% data variables.product.product_location %}インスタンスのホスト名で。{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %} インスタンスで Subdomain Isolation を有効化している場合:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+```xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://github.com/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+{% endif %}
+
+### パッケージを公開する
+
+*nuget.config*ファイルにより認証する{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%か、{% data variables.product.prodname_dotcom %}個人アクセストークン (PAT) で`--api-key`コマンドラインオプションを使用する
+{% endif %}ことにより、パッケージを{% data variables.product.prodname_registry %}に公開できます。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### GitHub PATをAPIキーとして使用してパッケージを公開する
+
+{% data variables.product.prodname_dotcom %}アカウントで使用するPATをまだ持っていない場合は、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
+
+1. 新しいプロジェクトを作成してください。
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. プロジェクトをパッケージ化してください。
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. PATをAPIキーとして使用して、パッケージを公開します。
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### *nuget.config*ファイルを使用してパッケージを公開する
+
+公開の際には、*nuget.config*認証ファイルで使用する*csproj*ファイル中で、`OWNER`に同じ値を使わなければなりません。 *.csproj*ファイル中でバージョン番号を指定もしくはインクリメントし、`dotnet pack`コマンドを使ってそのバージョンのための*.nuspec*ファイルを作成してください。 パッケージの作成に関する詳しい情報については、Microsoftのドキュメンテーション中の「[クイック スタート: パッケージの作成と公開 (dotnet CLI)](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)」を参照してください。
+
+{% data reusables.package_registry.authenticate-step %}
+2. 新しいプロジェクトを作成してください。
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. プロジェクト固有の情報をプロジェクトファイルに追加してください。プロジェクトファイルは*.csproj*で終わります。  以下のように置き換えてください。
+    - `OWNER`を、プロジェクトを含むリポジトリを所有しているユーザもしくはOrganizationアカウント名で。
+    - `REPOSITORY`を、公開したいパッケージを含むリポジトリの名前で。
+    - `1.0.0`を、パッケージのバージョン番号で。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - `HOSTNAME` を、{% data variables.product.product_location %}インスタンスのホスト名で。{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. プロジェクトをパッケージ化してください。
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. *nuget.config*ファイル中で指定した`key`を使ってパッケージを公開してください。
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### 同じリポジトリへの複数パッケージの公開
+
+複数のパッケージを同じリポジトリに公開するには、同じ{% data variables.product.prodname_dotcom %}リポジトリURLをすべての*.csproj*プロジェクトファイル中の`RepositoryURL`フィールドに含めることができます。 {% data variables.product.prodname_dotcom %}は、そのフィールドに基づいてリポジトリをマッチします。
+
+たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### パッケージをインストールする
+
+プロジェクトで{% data variables.product.prodname_dotcom %}からパッケージを利用するのは、*nuget.org*からパッケージを使用するのに似ています。 パッケージの依存関係を*.csproj*ファイルに追加し、パッケージ名とバージョンを指定してください。 プロジェクトでの*.csproj*ファイルの利用に関する詳しい情報については、Microsoftのドキュメンテーションの「[パッケージ利用のワークフロー](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)」を参照してください。
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. パッケージを利用するには、*.csproj*プロジェクトファイルに`ItemGroup`を追加し、`PackageReference`フィールドを設定してください。`OctokittenApp`パッケージをパッケージの依存関係で、`1.0.0`を使いたいバージョンで置き換えてください。
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. `restore`コマンドでパッケージをインストールしてください。
+  ```shell
+  dotnet restore
+  ```
+
+### トラブルシューティング
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### 参考リンク
+
+- 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..3be98d1d64
--- /dev/null
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,151 @@
+---
+title: RubyGemsレジストリの利用
+intro: '{% data variables.product.prodname_registry %} にパッケージを公開し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係としてBundlerを使うRubyのプロジェクトで利用するよう、RubyGemsを設定できます。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。
+
+### 必要な環境
+
+- rubygems 2.4.1 以上. rubygemsのバージョンは以下のようにすればわかります。
+
+  ```shell
+  $ gem --version
+  ```
+
+  - Bundler 1.6.4 以上. Bundlerのバージョンは以下のようにすれば分かります。
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - 複数の認証情報を扱うには、keycutter をインストールしてください. keycutterは以下のようにすればインストールできます。
+  ```shell
+  $ gem install keycutter
+  ```
+
+### {% data variables.product.prodname_registry %} への認証を行う
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 個人アクセストークンでの認証
+
+{% data reusables.package_registry.required-scopes %}
+
+gemの公開なら*~/.gem/credentials*ファイルを編集することで、単一のgemのインストールなら*~/.gemrc*ファイルを編集することで、Bundlerを使って1つ以上のgemを追跡してインストールするなら*~/.gemrc*ファイルを編集することで、RubyGemsで{% data variables.product.prodname_registry %}に認証を受けることができます。
+
+新しいgemsを公開するには、*~/.gem/credentials*ファイルを編集して個人アクセストークンを含めることによって、RubyGemsで{% data variables.product.prodname_registry %}に認証を受けなければなりません。  *~/.gem/credentials*ファイルが存在しない場合、新しく作成してください。
+
+たとえば、*~/.gem/credentials*を作成もしくは編集して、以下を含めてください。*TOKEN*は個人アクセストークンで置き換えてください。
+
+```shell
+gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" }
+```
+
+gemをインストールするには、プロジェクトの*~/.gemrc*ファイルを編集し、`https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`を含めることによって{% data variables.product.prodname_registry %}の認証を受けなければなりません。 以下のように置き換えてください。
+  - `USERNAME`を{% data variables.product.prodname_dotcom %}のユーザ名で。
+  - `TOKEN`を個人アクセストークンで。
+  - `OWNER` を、プロジェクトを含むリポジトリを所有しているユーザまたはOrganizationアカウント名で。{% if enterpriseServerVersions contains currentVersion %}
+  - `REGISTRY-URL` をインスタンスの Rubygems レジストリの URL で。 インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` をインスタンスの Rubygems レジストリである `rubygems.HOSTNAME` のURL で。 *HOSTNAME* を {% data variables.product.product_location %} のホスト名で。
+{% endif %}
+
+*~/.gemrc*ファイルがないなら、以下の例を使って新しい*~/.gemrc*ファイルを作成してください。
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+Bundlerで認証を受けるには、個人アクセストークンを使うようにBundlerを設定してください。 *USERNAME*を{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*を個人アクセストークンで、*OWNER*をプロジェクトを含むリポジトリを所有しているユーザもしくはOrganizationアカウント名で置き換えます。{% if enterpriseServerVersions contains currentVersion %}}`REGISTRY-URL` をインスタンスのRubygemsレジストリのURLで置き換えてください。 インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% elsif currentVersion == "github-ae@latest" %}`REGISTRY-URL` を、インスタンスの Rubygems レジストリの URL である `rubygems.HOSTNAME` に置き換えてください。 *HOSTNAME* を、{% data variables.product.product_location %} のホスト名に置き換えてください。{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### パッケージを公開する
+
+{% data reusables.package_registry.default-name %} たとえば、`octo-gem`を`octo-org`というOrganizationに公開するなら、{% data variables.product.prodname_registry %}はそのgemを`octo-org/octo-gem`リポジトリに公開します。 gem の作成に関する詳しい情報については、RubyGems ドキュメンテーションの「[gem の作成](http://guides.rubygems.org/make-your-own-gem/)」を参照してください。
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. *gemspec*からパッケージをビルドして、*.gem*パッケージを作成してください。
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. {% data variables.product.prodname_registry %}にパッケージを公開してください。 `OWNER`をプロジェクトを含むリポジトリを所有しているユーザもしくはOrganizationアカウント名で、`OCTO-GEM`をgemパッケージ名で置き換えます。{% if enterpriseServerVersions contains currentVersion %}`REGISTRY-URL` をインスタンスのRubygemsレジストリのURLで置き換えてください。 インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、*HOSTNAME* を{% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% elsif currentVersion == "github-ae@latest" %}`REGISTRY-URL` を、インスタンスの Rubygems レジストリの URL である `rubygems.HOSTNAME` に置き換えてください。 *HOSTNAME* を、{% data variables.product.product_location %} のホスト名に置き換えてください。{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### 同じリポジトリへの複数パッケージの公開
+
+複数のgemを同じリポジトリに公開したい場合は、{% data variables.product.prodname_dotcom %}リポジトリの`gem.metadata`にある`github_repo`フィールドに、URL を記述できます。 このフィールドを含めた場合、{% data variables.product.prodname_dotcom %} は、gem 名の代わりに、この値を元にしてリポジトリを照合します。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME*を、{% data variables.product.product_location %} のホスト名に置き換えます。{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### パッケージをインストールする
+
+{% data variables.product.prodname_registry %}からのgemsは、*rubygems.org*からのgemsを使うのと同じように利用できます。 {% data variables.product.prodname_dotcom %}ユーザあるいはOrganizationを*~/.gemrc*ファイルにソースとして追加するか、Bundlerを使って*Gemfile*を編集することによって、{% data variables.product.prodname_registry %}に認証を受けなければなりません。
+
+{% data reusables.package_registry.authenticate-step %}
+1. Bundlerについては、{% data variables.product.prodname_dotcom %}ユーザもしくはOrganizationをソースとして*Gemfile*に追加して、この新しいソースからgemsをフェッチするようにしてください。 たとえば、指定したパッケージに対してのみ{% data variables.product.prodname_registry %}を使用する*Gemfile*に新しい`source`ブロックを追加できます。*GEM NAME*を {% data variables.product.prodname_registry %}からインストールするパッケージで、*OWNER*をインストールしたいgemを含むリポジトリを所有するユーザまたはOrganizationで置き換えてください。{% if enterpriseServerVersions contains currentVersion %}`REGISTRY-URL`をインスタンスのRubygemsレジストリのURLで置き換えてください。 インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、*HOSTNAME* を{% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% elsif currentVersion == "github-ae@latest" %}`REGISTRY-URL` を、インスタンスの Rubygems レジストリの URL である `rubygems.HOSTNAME` に置き換えてください。 *HOSTNAME* を、{% data variables.product.product_location %} のホスト名に置き換えてください。{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. 1.7.0以前のバージョンのBundlerの場合、新しいグローバルな`source`を追加する必要があります。 Bundlerの利用に関する詳しい情報については[bundler.ioのドキュメンテーション](http://bundler.io/v1.5/gemfile.html)を参照してください。
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. パッケージをインストールしてください。
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### 参考リンク
+
+- 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」
diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
index f98d1793d6..db117c34e9 100644
--- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
+++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
@@ -52,7 +52,7 @@ Apex ドメインは、`example.com` といったようにサブドメインを
 
 Apex ドメインは、DNS プロバイダを通じて、`A`、`ALIAS`、`ANAME` レコードで設定されます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)」を参照してください。
 
-{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)."
+{% data reusables.pages.www-and-apex-domain-recommendation %} 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)」を参照してください。
 
 ### {% data variables.product.prodname_pages %} サイトが無効化された際にカスタムドメインを更新する
 
diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index aaf775b7a4..011d20f463 100644
--- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -38,15 +38,15 @@ DNS レコードの設定が正しいかどうかを検証するために利用
 
 ### サブドメインを設定する
 
-To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider.
+`www` または `www.example.com` や `blog.example.com` などのカスタムサブドメインを設定するには、リポジトリ設定にドメインを追加する必要があります。これにより、サイトのリポジトリに CNAME ファイルが作成されます。 その後、DNS プロバイダで CNAME レコードを設定します。
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
 4. "Custom domain（カスタムドメイン）" の下で、カスタムドメインを入力して**Save（保存）**をクリックします。 これで_CNAME_ファイルを公開ソースのルートに追加するコミットが作成されます。 ![カスタムドメインの保存ボタン](/assets/images/help/pages/save-custom-subdomain.png)
-5. お使いの DNS プロバイダにアクセスし、サブドメインがサイトのデフォルトドメインを指す `CNAME` レコードを作成します。 たとえば、サイトで `www.example.com` というサブドメインを使いたい場合、`www.example.com` が `<user>.github.io` を指す`CNAME` レコードを作成します。 If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
+5. お使いの DNS プロバイダにアクセスし、サブドメインがサイトのデフォルトドメインを指す `CNAME` レコードを作成します。 たとえば、サイトで `www.example.com` というサブドメインを使いたい場合、`www.example.com` が `<user>.github.io` を指す`CNAME` レコードを作成します。 Organization サイトで `www.anotherexample.com` というサブドメインを使用する場合、`www.anotherexample.com` が `<organization>.github.io` を指す`CNAME` レコードを作成します。 `CNAME` レコードは、リポジトリ名を除いて、常に`<user>.github.io` または `<organization>.github.io` を指している必要があります。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. DNS レコードが正しくセットアップされたことを確認するには、 `dig` コマンドを使います。_WWW.EXAMPLE.COM_ は、お使いのサブドメインに置き換えてください。
 ```shell
@@ -61,9 +61,9 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 
 ### Apexドメインを設定する
 
-To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file  in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
+`example.com` などの Apex ドメインを設定するには、{% data variables.product.prodname_pages %} リポジトリに _CNAME_ ファイルを設定し、DNS プロバイダで少なくとも 1 つの `ALIAS`、`ANAME`、または `A` レコードを設定する必要があります。
 
-{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
+{% data reusables.pages.www-and-apex-domain-recommendation %} 詳しい情報については、「[サブドメインを設定する](#configuring-a-subdomain)」を参照してください。
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -71,7 +71,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 4. "Custom domain（カスタムドメイン）" の下で、カスタムドメインを入力して**Save（保存）**をクリックします。 これで_CNAME_ファイルを公開ソースのルートに追加するコミットが作成されます。 ![カスタムドメインの保存ボタン](/assets/images/help/pages/save-custom-apex-domain.png)
 5. DNS プロバイダに移動し、`ALIAS`、`ANAME`、または `A` レコードを作成します。 {% data reusables.pages.contact-dns-provider %}
     - `ALIAS`または`ANAME`レコードを作成するには、Apexドメインをサイトのデフォルトドメインにポイントします。 {% data reusables.pages.default-domain-information %}
-    - To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+    - `A` レコードを作成するには、Apex ドメインが {% data variables.product.prodname_pages %} の IP アドレスを指すようにします。
       ```shell
       185.199.108.153
       185.199.109.153
@@ -79,7 +79,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. DNS レコードが正しく設定されたことを確認するには、 `dig` コマンドを使います。_EXAMPLE.COM_ は、お使いの Apex ドメインに置き換えてください。 結果が、上記の {% data variables.product.prodname_pages %} の IP アドレスに一致することを確認します。
   ```shell
diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
index fceaac2736..dcf0557f50 100644
--- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
+++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -24,8 +24,8 @@ topics:
 
 - _CNAME_ ファイル名は、すべて大文字である必要があります。
 - _CNAME_ ファイルにはドメインを 1 つだけ含めることができます。 複数のドメインをサイトにポイントするには、DNSプロバイダ経由のリダイレクトを設定する必要があります。
-- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
-- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. たとえば、別のリポジトリの _CNAME_ ファイルに `example.com` が含まれている場合、自分のリポジトリの _CNAME_ ファイルに `example.com` を使用することはできません。
+- _CNAME_ ファイルにはドメイン名のみが含まれている必要があります。 たとえば、`www.example.com`、`blog.example.com`、`example.com` などです。
+- ドメイン名は、すべての {% data variables.product.prodname_pages %} サイトで一意である必要があります。 たとえば、別のリポジトリの _CNAME_ ファイルに `example.com` が含まれている場合、自分のリポジトリの _CNAME_ ファイルに `example.com` を使用することはできません。
 
 ### DNS の設定ミス
 
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md
index b630dc6dca..2b92ff45a8 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -41,19 +41,19 @@ Organization owners can disable the publication of {% data variables.product.pro
 
 {% data variables.product.prodname_pages %} サイトには、3 つの種類があります。プロジェクト、ユーザ、そして Organization です。 プロジェクトサイトは、JavaScript ライブラリやレシピ集など、{% data variables.product.product_name %} の特定のプロジェクトに関するものです。 ユーザおよび Organization サイトは、特定の {% data variables.product.product_name %} に関するものです。
 
-To publish a user site, you must create a repository owned by your user account that's named {% if currentVersion == "free-pro-team@latest" %}`<username>.github.io`{% else %}`<username>.<hostname>`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% if currentVersion == "free-pro-team@latest" %}`<organization>.github.io`{% else %}`<organization>.<hostname>`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, user and organization sites are available at `http(s)://<username>.github.io` or `http(s)://<organization>.github.io`.{% elsif currentVersion == "github-ae@latest" %}User and organization sites are available at `http(s)://pages.<hostname>/<username>` or `http(s)://pages.<hostname>/<organization>`.{% endif %}
+ユーザサイトを公開するには、{% if currentVersion == "free-pro-team@latest" %}`<username>.github.io`{% else %}`<username>.<hostname>`{% endif %} という名前のユーザアカウントが所有するリポジトリを作成する必要があります。 Organization サイトを公開するには、 {% if currentVersion == "free-pro-team@latest" %}`<organization>.github.io`{% else %}`<organization>.<hostname>`{% endif %} という名前の Organization が所有するリポジトリを作成する必要があります。 {% if currentVersion == "free-pro-team@latest" %}カスタムドメインを使用している場合を除き、ユーザサイトと Organization サイトは `http(s)://<username>.github.io` または `http(s)://<organization>.github.io` で利用できます。{% elsif currentVersion == "github-ae@latest" %}ユーザサイトと Organization サイトは `http(s)://pages.<hostname>/<username>` または `http(s)://pages.<hostname>/<organization>` で利用できます。{% endif %}
 
-プロジェクトサイトのソースファイルは、プロジェクトと同じリポジトリに保存されます。 {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://<username>.github.io/<repository>` or `http(s)://<organization>.github.io/<repository>`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.<hostname>/<username>/<repository>/` or `http(s)://pages.<hostname>/<organization>/<repository>/`.{% endif %}
+プロジェクトサイトのソースファイルは、プロジェクトと同じリポジトリに保存されます。 {% if currentVersion == "free-pro-team@latest" %}カスタムドメインを使用している場合を除き、プロジェクトサイトは `http(s)://<username>.github.io/<repository>` または `http(s)://<organization>.github.io/<repository>` で利用できます。{% elsif currentVersion == "github-ae@latest" %}プロジェクトサイトは `http(s)://pages.<hostname>/<username>/<repository>/` または `http(s)://pages.<hostname>/<organization>/<repository>/` で利用できます。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
+サイトを非公開で公開する場合、サイトの URL が異なります。 For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 カスタムドメインがサイトの URL に与える影響に関する詳しい情報については、「[カスタムドメインと {% data variables.product.prodname_pages %} について](/articles/about-custom-domains-and-github-pages)」を参照してください。
 {% endif %}
 
-You can only create one user or organization site for each account on {% data variables.product.product_name %}. プロジェクトサイトの数については、Organization アカウントでもユーザアカウントでも、無制限です。
+{% data variables.product.product_name %} のアカウントごとに作成できるユーザまたは Organization サイトは 1 つだけです。 プロジェクトサイトの数については、Organization アカウントでもユーザアカウントでも、無制限です。
 
 {% if enterpriseServerVersions contains currentVersion %}
 サイトが利用できる URL については、{% data variables.product.product_location %} で Subdomain Isolation を有効にしているかどうかで異なります。
@@ -61,34 +61,26 @@ You can only create one user or organization site for each account on {% data va
 | サイトの種類 | Subdomain Isolation が有効 | Subdomain isolation が無効 |
 | ------ | ----------------------- | ----------------------- |
 |        |                         |                         |
- User | 
+ ユーザ | 
 
-`http(s)://pages.<hostname>/<username>` | `http(s)://<hostname>/pages/<username>` | Organization | `http(s)://pages.<hostname>/<organization>` | `http(s)://<hostname>/pages/<organization>` | Project site owned by user account | `http(s)://pages.<hostname>/<username>/<repository>/` | `http(s)://<hostname>/pages/<username>/<repository>/` Project site owned by organization account | `http(s)://pages.<hostname>/<orgname>/<repository>/` | `http(s)://<hostname>/pages/<orgname>/<repository>/`
+`http(s)://pages.<hostname>/<username>` | `http(s)://<hostname>/pages/<username>` | Organization | `http(s)://pages.<hostname>/<organization>` | `http(s)://<hostname>/pages/<organization>` | ユーザアカウントが所有するプロジェクトサイト | `http(s)://pages.<hostname>/<username>/<repository>/` | `http(s)://<hostname>/pages/<username>/<repository>/` Organization アカウントが所有するプロジェクトサイト | `http(s)://pages.<hostname>/<orgname>/<repository>/` | `http(s)://<hostname>/pages/<orgname>/<repository>/`
 
-For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator.
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Repositories using the legacy `<username>.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://<username>.github.com` to `http(s)://<username>.github.io`. If both a `<username>.github.com` and `<username>.github.io` repository exist, only the `<username>.github.io` repository will be published.
-
-{% endnote %}
+詳しい情報については、 「[Subdomain Isolation を有効化する](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)」を参照するか、サイト管理者にお問い合わせください。
 {% endif %}
 
 ### {% data variables.product.prodname_pages %} サイトの公開元
 
-The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored.
+{% data variables.product.prodname_pages %} サイトの公開元は、サイトのソースファイルが保存されているブランチまたはフォルダです。
 
 {% data reusables.pages.private_pages_are_public_warning %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
-If the default publishing source exists in your repository, {% data variables.product.prodname_pages %} will automatically publish a site from that source. The default publishing source for user and organization sites is the root of the default branch for the repository. The default publishing source for project sites is the root of the `gh-pages` branch.
+デフォルトの公開元がリポジトリに存在する場合、{% data variables.product.prodname_pages %} はそこから自動的にサイトを公開します。 ユーザサイトと Organization サイトのデフォルトの公開元は、リポジトリのデフォルトブランチのルートです。 プロジェクトサイトのデフォルトの公開元は、`gh-pages` ブランチのルートです。
 
-If you want to keep the source files for your site in a different location, you can change the publishing source for your site. You can publish your site from any branch in the repository, either from the root of the repository on that branch, `/`, or from the `/docs` folder on that branch. 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)」を参照してください。
+サイトのソースファイルを別の場所に保持する場合は、サイトの公開元を変更できます。 リポジトリ内の任意のブランチから、そのブランチのリポジトリのルート、`/`、またはそのブランチの `/docs` フォルダからサイトを公開できます。 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)」を参照してください。
 
-If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. _CNAME_ ファイルに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %}
+公開元としていずれかのブランチの `/docs` フォルダを選択した場合{% if currentVersion == "free-pro-team@latest" %}、{% data variables.product.prodname_pages %} は`/docs` フォルダから _CNAME_ ファイル{% endif %}を含むサイトを公開するためのすべてを読み取ります。{% if currentVersion == "free-pro-team@latest" %}たとえば、{% data variables.product.prodname_pages %} 設定を使用してカスタムドメインを編集すると、カスタムドメインは `/docs/CNAME` に書き込みます。 _CNAME_ ファイルに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %}
 
 {% else %}
 
@@ -98,7 +90,7 @@ If you choose the `/docs` folder of any branch as your publishing source, {% dat
 
 プロジェクトサイトは、`master` ブランチまたは `master` ブランチ場の `/docs` フォルダから公開することもできます。 これらの公開元からサイトを公開するには、別の公開元を設定する必要があります。 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)」を参照してください。
 
-If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. _CNAME_ ファイルに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %}
+公開元として`master` ブランチの `/docs` フォルダを選択した場合{% if currentVersion == "free-pro-team@latest" %}、{% data variables.product.prodname_pages %} は`/docs` フォルダから _CNAME_ ファイル{% endif %}を含むサイトを公開するためのすべてを読み取ります。{% if currentVersion == "free-pro-team@latest" %}たとえば、{% data variables.product.prodname_pages %} 設定を使用してカスタムドメインを編集すると、カスタムドメインは `/docs/CNAME` に書き込みます。 _CNAME_ ファイルに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %}
 
 デフォルトブランチが`master`または`gh-pages`ではない場合でも、他のブランチからはプロジェクトサイトを公開することはできません。
 
@@ -123,7 +115,7 @@ If you choose the `/docs` folder of the `master` branch as your publishing sourc
 {% endif %}
 {% data variables.product.prodname_pages %} サイトには、次の使用制限があります:
 
-  - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %}
+  - {% data variables.product.prodname_pages %} ソースリポジトリには、1GB の推奨上限があります。{% if currentVersion == "free-pro-team@latest" %}詳しい情報については、「[私のディスク容量はいくつですか？](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)」を参照してください。{% endif %}
   - 公開された{% data variables.product.prodname_pages %}のサイトは1GB以上であってはなりません。
 {% if currentVersion == "free-pro-team@latest" %}
   - {% data variables.product.prodname_pages %} サイトには、月当たり 100GB の*ソフトな*帯域幅制限があります。
@@ -135,7 +127,7 @@ If you choose the `/docs` folder of the `master` branch as your publishing sourc
 
 {% data variables.product.prodname_pages %} は、オンラインビジネス、eコマースサイト、主に商取引の円滑化またはサービスとしての商用ソフトウェアの提供 (SaaS) のどちらかを目的とする、その他のウェブサイトを運営するための無料のウェブホスティングサービスとしての使用を意図したものではなく、またそのような使用を許可するものでもありません。
 
-In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. For a list of prohibited uses, see "[{% data variables.product.prodname_dotcom %}'s Additional Product Terms for {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)."
+In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. 禁止されている用途のリストについては、「[{% data variables.product.prodname_dotcom %} の {% data variables.product.prodname_pages %} に関する追加製品の利用規約](/github/site-policy/github-additional-product-terms#4-pages)」を参照してください。
 {% endif %}
 
 ### {% data variables.product.prodname_pages %} での MIME タイプ
@@ -147,4 +139,4 @@ MIME タイプとは、ブラウザがリクエストするファイルの性質
 ### 参考リンク
 
 - {% data variables.product.prodname_learning %} の [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages)
-- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)"
+- 「[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)」
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
index bf4eb92e24..1b776c3b85 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
@@ -21,7 +21,7 @@ topics:
 
 テーマ選択画面の動作は、リポジトリがパブリックかプライベートかにより異なります。
   - {% data variables.product.prodname_pages %} がリポジトリに対して既に有効である場合、テーマ選択画面は、現在の公開元にテーマを追加します。
-  - If your repository is public and {% data variables.product.prodname_pages %} is disabled for your repository, using the theme chooser will enable {% data variables.product.prodname_pages %} and configure the default branch as your publishing source.
+  - リポジトリがパブリックで、{% data variables.product.prodname_pages %} がリポジトリに対して無効である場合、テーマ選択画面を使用することで {% data variables.product.prodname_pages %} が有効となり、デフォルトブランチを公開元として設定します。
   - リポジトリがプライベートで、{% data variables.product.prodname_pages %}がリポジトリに対して無効である場合、テーマ選択画面を使用する前に、公開元を設定して {% data variables.product.prodname_pages %} を有効にする必要があります。
 
 公開元に関する詳しい情報については、「[{% data variables.product.prodname_pages %} について](/articles/about-github-pages#publishing-sources-for-github-pages-sites)」を参照してください。
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index f57f4d3134..3c3895fc08 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Changing the visibility of your GitHub Pages site
-intro: You can manage access control for your project site by publishing the site publicly or privately.
+title: GitHub Pages サイトの可視性を変更する
+intro: プロジェクトサイトをパブリックまたはプライベートで公開することにより、プロジェクトサイトのアクセス制御を管理できます。
 product: '{% data reusables.gated-features.private-pages %}'
 versions:
   free-pro-team: '*'
@@ -9,26 +9,26 @@ redirect_from:
   - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site
 ---
 
-### About access control for {% data variables.product.prodname_pages %} sites
+### {% data variables.product.prodname_pages %} サイトのアクセス制御について
 
-If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+プロジェクトサイトが {% data variables.product.prodname_ghe_cloud %} を使用する Organization が所有するプライベートもしくは内部リポジトリから公開される場合、そのサイトのアクセス制御を管理できます。 アクセス制御を使用すると、インターネット上のすべての人にサイトを公開する（パブリック）か、リポジトリへの読み取りアクセス権を持つ人限定で公開する（プライベート）かを選択できます。 プライベートで公開されたサイトでは、社内のドキュメントやナレッジベースを Enterprise のメンバーと共有できます。 Organization サイトのアクセス制御を管理することはできません。 For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
 
-Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published:
+プライベートのサイトは、パブリックのサイトとは異なるサブドメインで利用できます。 これにより、{% data variables.product.prodname_pages %} サイトが公開された瞬間から安全になります。
 
-- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
-- We use a unique subdomain for the private page to ensure that other repositories in your organization cannot publish content on the same origin as the private page. This protects your private page from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain.
+- `*.pages.github.io` のすべてのサブドメインを TLS 証明書で自動的に保護し、HSTS を適用して、ブラウザーが常に HTTPS 経由でページを提供するようにします。
+- プライベートページには一意のサブドメインを使用して、Organization 内の他のリポジトリがプライベートページと同じオリジンでコンテンツを公開できないようにします。 これにより、プライベートページが「[Cookie のトス](https://github.blog/2013-04-09-yummy-cookies-across-domains/)」から保護されます。 これが、`github.com` ドメインで {% data variables.product.prodname_pages %} サイトをホストしない理由でもあります。
 
-You can see your site's unique subdomain in the pages tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator.
+リポジトリ設定のページタブで、サイトの一意のサブドメインを確認できます。 リポジトリ名をパスとしてサイトをビルドするように設定された静的サイトジェネレータを使用している場合、サイトをプライベートに変更するときに静的サイトジェネレータの設定を更新する必要がある場合があります。 For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator.
 
-To use a shorter and more memorable domain for your private {% data variables.product.prodname_pages %} site, you can configure a custom domain. 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインの設定](/pages/configuring-a-custom-domain-for-your-github-pages-site)」を参照してください。
+カスタムドメインを設定して、プライベートの {% data variables.product.prodname_pages %} サイトに短くて記憶に残るドメインを使用できます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインの設定](/pages/configuring-a-custom-domain-for-your-github-pages-site)」を参照してください。
 
-### Changing the visibility of your {% data variables.product.prodname_pages %} site
+### {% data variables.product.prodname_pages %} サイトの可視性を変更する
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png)
-4. 公開されたサイトを見るには、"{% data variables.product.prodname_pages %}"の下で、サイトのURLをクリックしてください。 ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png)
+3. [{% data variables.product.prodname_pages %}] の下で、[**{% data variables.product.prodname_pages %} visibility**] ドロップダウンメニューを選択してから、可視性をクリックします。 ![サイトの可視性を選択するドロップダウンメニュー](/assets/images/help/pages/public-or-private-visibility.png)
+4. 公開されたサイトを見るには、"{% data variables.product.prodname_pages %}"の下で、サイトのURLをクリックしてください。 ![プライベートで公開されたサイトの URL](/assets/images/help/pages/click-private-pages-url-to-preview.png)
 
   {% note %}
 
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
index d7efef481b..42cd311b61 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -25,8 +25,8 @@ Before you configure a publishing source, make sure the branch{% if currentVersi
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
-4. Optionally, use the drop-down menu to select a folder for your publishing source. ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png)
+3. [{% data variables.product.prodname_pages %}] で、[**None**] または [**Branch**] ドロップダウンメニューから公開元を選択します。 ![公開元を選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-drop-down.png)
+4. 必要に応じて、ドロップダウンメニューで発行元のフォルダを選択します。 ![公開元のフォルダを選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-folder-drop-down.png)
 5. [**Save**] をクリックします。 ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %}
 3. [{% data variables.product.prodname_pages %}] で、[**Source**] ドロップダウンメニューから公開元を選択します。 ![公開元を選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-drop-down.png)
 {% endif %}
@@ -35,4 +35,4 @@ Before you configure a publishing source, make sure the branch{% if currentVersi
 
 {% data reusables.pages.admin-must-push %}
 
-If you choose the `docs` folder on {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}any{% else %}the `master`{% endif %} branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. 詳細については、「[{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)」を参照してください。
+公開元として{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}いずれかの{% else %}`master`{% endif %} ブランチの `docs` フォルダを選択した場合、その後リポジトリ内のそのブランチから `/docs` フォルダを削除すると、サイトがビルドされず、`/docs` フォルダが見つからない場合にページのビルドエラーメッセージが表示されます。 詳細については、「[{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)」を参照してください。
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
index ab79c557a0..53535cef28 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -50,9 +50,9 @@ topics:
 
 ### 次のステップ
 
-新しいファイルを追加で作成することにより、ページを追加できます。 各ファイルは、公開元と同じディレクトリ構造で、サイト上に表示されます。 For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% if currentVersion == "free-pro-team@latest" %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html` で表示されます。
+新しいファイルを追加で作成することにより、ページを追加できます。 各ファイルは、公開元と同じディレクトリ構造で、サイト上に表示されます。 たとえば、プロジェクトサイトの公開元が `gh-pages` ブランチで、新しいファイル `/about/contact-us.md` を `gh-pages` ブランチに作成した場合、ファイルは {% if currentVersion == "free-pro-team@latest" %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html` で表示されます。
 
-また、サイトの見た目をカスタマイズするため、テーマを追加できます。 For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}."
+また、サイトの見た目をカスタマイズするため、テーマを追加できます。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" %}「[テーマ選択画面で {% data variables.product.prodname_pages %} サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}「[Jekyll テーマ選択画面で {% data variables.product.prodname_pages %} サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}」を参照してください。
 
 サイトを更にカスタマイズするには、Jekyll を使用できます。Jekyll は、{% data variables.product.prodname_pages %} に組み込まれている静的サイトジェネレータです。 詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll)」を参照してください。
 
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index 13c6cb6801..d2ca1e5636 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Pages サイトを取り下げる
-intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
+intro: '{% data variables.product.prodname_pages %} サイトを取り下げて、サイトを利用不可にすることができます。'
 redirect_from:
   - /articles/how-do-i-unpublish-a-project-page/
   - /articles/unpublishing-a-project-page/
@@ -31,5 +31,5 @@ topics:
 ### ユーザまたは Organization サイトを取り下げる
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Delete the branch that you're using as a publishing source, or delete the entire repository. 詳細は「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」および「[リポジトリを削除する](/articles/deleting-a-repository)」を参照してください。
+2. 公開元として使用しているブランチを削除するか、リポジトリ全体を削除します。 詳細は「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」および「[リポジトリを削除する](/articles/deleting-a-repository)」を参照してください。
 {% data reusables.pages.update_your_dns_settings %}
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
index dc53cc004b..e7e4dd1c9d 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -31,7 +31,7 @@ topics:
 
 Jekyllは、{% data variables.product.prodname_pages %}に組み込まれている静的サイトジェネレータで、ビルドプロセスを容易化できます。 JekyllはMarkdownおよびHTMLファイルを取り込み、選択したレイアウトに基づいて、完成された静的ウェブサイトを作成します。 Jekyllは、Markdownと、サイトに動的コンテンツを読み込むテンプレート言語のLiquidをサポートします。 詳しい情報については、[Jekyll](https://jekyllrb.com/)を参照してください。
 
-Windows は、Jekyll を公式にはサポートしていません。 For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation.
+Windows は、Jekyll を公式にはサポートしていません。 詳しい情報については、Jekyll のドキュメントの「[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)」を参照してください。
 
 {% data variables.product.prodname_pages %} ではJekyllを使用することをおすすめします。 お好みに応じて、別の静的サイトジェネレータを使用することも、ローカルまたは別のサーバーにおけるビルドプロセスをカスタマイズすることもできます。 詳しい情報については「[{% data variables.product.prodname_pages %}について](/articles/about-github-pages#static-site-generators)」を参照してください。
 
@@ -75,7 +75,7 @@ kramdown:
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.prodname_dotcom %} のサイトに、サポートされているテーマを追加できます。 詳しい情報については、{% data variables.product.prodname_pages %} サイトの「[サポートされているテーマ](https://pages.github.com/themes/)」および「[テーマ選択画面を使用して{% data variables.product.prodname_pages %}サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)」を参照してください。
 
-To use any other open source Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, you can add the theme manually.{% else %} You can add a theme to your site manually.{% endif %} For more information, see{% if currentVersion == "free-pro-team@latest" %} [themes hosted on {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) and{% else %} "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and{% endif %} "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+{% data variables.product.prodname_dotcom %} にホストされている他のオープンソース Jekyll テーマを使用する場合は、テーマを手動で追加できます。{% else %}テーマを手動でサイトに追加できます。{% endif %}詳しい情報については、{% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %} にホストされているテーマ](https://github.com/topics/jekyll-theme)と、{% else %}{% data variables.product.prodname_pages %}サイトの「[サポートされているテーマ](https://pages.github.com/themes/)」、および{% endif %}「[Jekyllを使用して{% data variables.product.prodname_pages %}サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)」を参照してください。
 
 テーマのファイルを編集することで、テーマのデフォルトを上書きできます。 詳しい情報については、テーマのドキュメンテーションおよびJekyllドキュメンテーションの「[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)」を参照してください。
 
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
index cb29a7ca46..d89367ee72 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
@@ -17,10 +17,10 @@ topics:
 
 ### Jekyllのビルドエラーについて
 
-Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %}
+サイトの公開元に変更をプッシュした後、{% data variables.product.prodname_pages %} がサイトのビルドを試行しない場合があります。{% if currentVersion == "free-pro-team@latest" %}
 - 変更をプッシュしたユーザーがメールアドレスを検証していない。 詳しい情報については、「[メールアドレスの検証](/articles/verifying-your-email-address)」を参照してください。{% endif %}
 - デプロイキーでプッシュしている。 サイトのリポジトリへのプッシュを自動化する場合は、かわりにマシンユーザーを設定できます。 詳しい情報については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys#machine-users)」を参照してください。
-- 公開元をビルドするようにCIサービスを設定していない。 For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. 詳細は、Travis CIまたはCIサービスのドキュメンテーションで、「[ビルドのカスタマイズ](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)」を参照してください。
+- 公開元をビルドするようにCIサービスを設定していない。 たとえば、Travis CI は `gh-pages` ブランチを、セーフリストに追加しない限りビルドしません。 詳細は、Travis CIまたはCIサービスのドキュメンテーションで、「[ビルドのカスタマイズ](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)」を参照してください。
 
 {% note %}
 
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
index 468432c892..d764facc2b 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
@@ -26,8 +26,8 @@ topics:
 2. *_config.yml* に移動します。
 {% data reusables.repositories.edit-file %}
 4. テーマ名のために、ファイルに新しい行を追加します。
-   - To use a supported theme, type `theme: THEME-NAME`, replacing _THEME-NAME_ with the name of the theme as shown in the README of the theme's repository. サポートされているテーマのリストについては、{% data variables.product.prodname_pages %} サイトで「[サポートされているテーマ](https://pages.github.com/themes/)」を参照してください。 ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png)
-   - {% data variables.product.prodname_dotcom %} にホストされているその他の任意の Jekyll テーマを使うには、`remote_theme: THEME-NAME` と入力します。THEME-NAME の部分は、テーマのリポジトリの README に表示されている名前に置き換えます。 ![Unsupported theme in config file](/assets/images/help/pages/add-remote-theme-to-config-file.png)
+   - サポートされているテーマを使用するには、`theme: THEME-NAME` と入力し、テーマのリポジトリの README に表示されているテーマの名前に _THEME-NAME_ を置き換えます。 サポートされているテーマのリストについては、{% data variables.product.prodname_pages %} サイトで「[サポートされているテーマ](https://pages.github.com/themes/)」を参照してください。 ![設定ファイルでサポートされているテーマ](/assets/images/help/pages/add-theme-to-config-file.png)
+   - {% data variables.product.prodname_dotcom %} にホストされているその他の任意の Jekyll テーマを使うには、`remote_theme: THEME-NAME` と入力します。THEME-NAME の部分は、テーマのリポジトリの README に表示されている名前に置き換えます。 ![設定ファイルでサポートされていないテーマ](/assets/images/help/pages/add-remote-theme-to-config-file.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
index 3ae4813d29..c811bae207 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
@@ -65,7 +65,7 @@ Jekyll サイトのコンテンツとして 2 つの主なタイプは、ペー
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
 
-Your post should now be up on your site! If the base URL of your site is `https://octocat.github.io`, then your new post will be located at `https://octocat.github.io/YYYY/MM/DD/TITLE.html`.
+あなたの投稿がサイトにアップされているはずです。 サイトのベース URL が `https://octocat.github.io` の場合、新しい投稿は `https://octocat.github.io/YYYY/MM/DD/TITLE.html` にあります。
 
 ### 次のステップ
 
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index 2275d30496..fb750f4d21 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -57,7 +57,7 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを
   ```
 {% data reusables.pages.decide-publishing-source %}
 {% data reusables.pages.navigate-publishing-source %}
-  For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder.
+  たとえば、デフォルトブランチの `docs` フォルダからサイトを公開することを選択した場合は、ディレクトリを作成して `docs ` フォルダに変更します。
  ```shell
  $ mkdir docs
  # Creates a new folder called docs
@@ -68,26 +68,31 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを
  $ git checkout --orphan gh-pages
  # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch
  ```
-7. To create a new Jekyll site, use the `jekyll new` command:
+7. 新しい Jekyll サイトを作成するには、`jekyll new` コマンドを使用します。
    ```shell
    $ jekyll new .
    # Creates a Jekyll site in the current directory
    ```
-8. Open the Gemfile that Jekyll created.
-1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line.
-1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to:
+8. Jekyll が作成した Gemfile を開きます。
+1. `gem "jekyll"` で始まる行の先頭に「#」を追加して行をコメントアウトします。
+1. `# gem "github-pages"` で始まる行を編集して `github-pages` を追加します。 行を次のように変更します。
 
    ```shell
    gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins
    ```
 
-   Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)."
+   _GITHUB-PAGES-VERSION_ をサポートされている最新バージョンの `github-pages` gem に置き換えます。 このバージョンについては、「[依存関係バージョン](https://pages.github.com/versions/)」を参照してください。
 
-   The correct version Jekyll will be installed as a dependency of the `github-pages` gem.
+   正しいバージョンの Jekyll は、`github-pages` gem の依存関係としてインストールされます。
 10. Gemfile を保存して閉じます。
-11. From the command line, run `bundle update`.
+11. コマンドラインで `bundle update` を実行します。
 11. 必要に応じて、サイトをローカルでテストします。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトをローカルでテストする](/articles/testing-your-github-pages-site-locally-with-jekyll)」を参照してください。
-12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. {% data variables.product.product_name %} リポジトリをリモートとして追加します。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ は Enterprise のホスト名に、{% endif %}_USER_ はリポジトリ所有者のアカウントに{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}、{% endif %}そして _REPOSITORY_ はリポジトリの名前に置き換えてください。
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
index badae7caab..8849629253 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
@@ -17,7 +17,7 @@ topics:
 
 リポジトリへの書き込み権限があるユーザは、{% data variables.product.prodname_pages %} サイトに対して Markdown プロセッサを設定できます。
 
-{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own extended [CommonMark](https://commonmark.org/) processor, which is used to render {% data variables.product.prodname_dotcom %} Flavored Markdown throughout {% data variables.product.product_name %}. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github)」を参照してください。
+{% data variables.product.prodname_pages %} は 2 つの Markdown プロセッサをサポートしています。[kramdown](http://kramdown.gettalong.org/) と {% data variables.product.prodname_dotcom %} 独自の拡張 [CommonMark](https://commonmark.org/) プロセッサで、後者は {% data variables.product.product_name %} を通じ {% data variables.product.prodname_dotcom %} Flavored Markdown をレンダリングする際に使用されます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github)」を参照してください。
 
 {% data variables.product.prodname_dotcom %} フレーバーの Markdown はどちらのプロセッサでも使用できますが、{% data variables.product.product_name %} に表示される結果と一致するのは常に CommonMark プロセッサのみです。
 
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
index 225a64bbd3..a0dc8af21f 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
@@ -31,7 +31,7 @@ Jekyll を使用してサイトをテストする前に、以下の操作が必
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.pages.navigate-publishing-source %}
-3. Run `bundle install`.
+3. `bundle install` を実行します。
 3. ローカルで Jekyll サイトを実行します.
   ```shell
   $ bundle exec jekyll serve
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
index db5c6baa0f..b4b26808b8 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
@@ -39,7 +39,7 @@ topics:
 {% data variables.product.prodname_pages %} サイトをローカルで、または {% data variables.product.product_name %} 上でビルドしているときに Jekyll でエラーが発生した場合、そのエラーメッセージをトラブルシューティングに利用できます。 エラーメッセージとその見方に関する詳しい情報は、「[{% data variables.product.prodname_pages %} サイトのJekyllビルドエラーについて](/articles/about-jekyll-build-errors-for-github-pages-sites)」を参照してください。
 
 一般的なエラーメッセージが表示された場合は、よくある問題をチェックします。
-- サポートされていないプラグインを使用している。 For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% if currentVersion == "free-pro-team@latest" %}
+- サポートされていないプラグインを使用している。 詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll について](/articles/about-github-pages-and-jekyll#plugins)」を参照してください。{% if currentVersion == "free-pro-team@latest" %}
 - リポジトリがリポジトリサイズの制限を超えている。 詳しい情報については「[私のディスク容量はいくつですか？](/articles/what-is-my-disk-quota)」を参照してください。{% endif %}
 - *_config.yml* ファイルで `source` の設定を変更した。 ビルドプロセス中に、この設定は {% data variables.product.prodname_pages %} によってオーバーライドされます。
 - 公開ソースにあるファイル名にコロン (`:`) が含まれている。コロンは使用できません。
@@ -135,11 +135,11 @@ Jekyll データファイルの詳細は、Jekyll のドキュメンテーショ
 
 ### Missing docs folder
 
-This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch.
+このエラーは、公開元としてブランチの `docs` フォルダを選択したが、そのブランチのリポジトリのルートに `docs` フォルダがないことを意味します。
 
-To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. `docs` フォルダを誤って削除した場合は、次のいずれかの方法が可能です。
+トラブルシューティングをするには、`docs` フォルダが誤って移動された場合は、公開元向けに選択したブランチのリポジトリのルートに `docs` フォルダを戻してみます。 `docs` フォルダを誤って削除した場合は、次のいずれかの方法が可能です。
 - Git を使用して削除を revert する、つまり取り消す。 詳細は、Git のドキュメンテーションで「[git-revert](https://git-scm.com/docs/git-revert.html)」を参照してください。
-- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. 詳細は「[新しいファイルを作成する](/articles/creating-new-files)」を参照してください。
+- 公開元向けに選択したブランチのリポジトリのルートに新しい `docs` フォルダを作成し、サイトのソースファイルをフォルダに追加します。 詳細は「[新しいファイルを作成する](/articles/creating-new-files)」を参照してください。
 - 公開ソースを変更する。 詳細は「[{% data variables.product.prodname_pages %} の公開ソースを設定する](/articles/configuring-a-publishing-source-for-github-pages)」を参照してください。
 
 ### Missing submodule
@@ -162,7 +162,7 @@ To troubleshoot, if your `docs` folder was accidentally moved, try moving the `d
 
 このエラーは、サイトの公開ソースに存在しないシンボリックリンク (symlink) がサイトに含まれていることを意味します。 シンボリックリンクの詳細は、Wikipedia で「[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)」を参照してください。
 
-トラブルシューティングするには、エラーメッセージで示されているファイルがサイトのビルドに使われているかどうかを確認します。 使われていない場合、またはファイルをシンボリックリンクにしたくない場合は、ファイルを削除します。 サイトのビルドにシンボリックファイルが必要な場合は、そのシンボリックリンクで参照されているファイルまたはディレクトリが、サイトの公開ソースにあることを確認してください。 To include external assets, consider using {% if currentVersion == "free-pro-team@latest" %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %}
+トラブルシューティングするには、エラーメッセージで示されているファイルがサイトのビルドに使われているかどうかを確認します。 使われていない場合、またはファイルをシンボリックリンクにしたくない場合は、ファイルを削除します。 サイトのビルドにシンボリックファイルが必要な場合は、そのシンボリックリンクで参照されているファイルまたはディレクトリが、サイトの公開ソースにあることを確認してください。 外部アセットを除外するには、{% if currentVersion == "free-pro-team@latest" %}`git submodule` または{% endif %}サードパーティのパッケージマネージャー、たとえば [Bower](https://bower.io/) などの使用を検討します。{% if currentVersion == "free-pro-team@latest" %}詳しい情報については、「[{% data variables.product.prodname_pages %} でサブモジュールを使う ](/articles/using-submodules-with-github-pages)」を参照してください。{% endif %}
 
 ### Syntax error in 'for' loop
 
@@ -186,6 +186,6 @@ To troubleshoot, if your `docs` folder was accidentally moved, try moving the `d
 
 このエラーは、コードに認識されない Liquid タグが含まれていることを意味します。
 
-トラブルシューティングするには、エラーメッセージで示されているファイルの Liquid タグがすべて Jekyll のデフォルトの変数に一致し、タグ名に誤入力がないことを確認します。 For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation.
+トラブルシューティングするには、エラーメッセージで示されているファイルの Liquid タグがすべて Jekyll のデフォルトの変数に一致し、タグ名に誤入力がないことを確認します。 デフォルトの変数のリストは、Jekyll のドキュメントで「[変数](https://jekyllrb.com/docs/variables/)」を参照してください。
 
 認識されないタグの主な原因は、サポート対象外のプラグインです。 サイトをローカルで生成し、静的なファイルを {% data variables.product.product_name %} にプッシュすることで、サポート対象外のプラグインを使用している場合は、そのプラグインで Jekyll のデフォルトの変数と異なるタグが使われていないかどうか確認してください。 サポート対象のプラグインについては、「[{% data variables.product.prodname_pages %} と Jekyll について](/articles/about-github-pages-and-jekyll#plugins)」を参照してください。
diff --git a/translations/ja-JP/content/rest/guides/basics-of-authentication.md b/translations/ja-JP/content/rest/guides/basics-of-authentication.md
index 0b0ed2a753..1854f08a1b 100644
--- a/translations/ja-JP/content/rest/guides/basics-of-authentication.md
+++ b/translations/ja-JP/content/rest/guides/basics-of-authentication.md
@@ -132,7 +132,7 @@ end
 
 リクエストを行う前にのみスコープを確認するだけでは不十分です。確認時と実際のリクエスト時の間に、ユーザがスコープを変更する可能性があります。 このような場合には、成功すると思っていたAPIの呼び出しが`404`または`401`ステータスになって失敗したり、情報の別のサブセットを返したりします。
 
-この状況にうまく対応できるように、有効なトークンによるリクエストに対するすべてのAPIレスポンスには、[`X-OAuth-Scopes`ヘッダ][oauth scopes]も含まれています。 このヘッダには、リクエストを行うために使用されたトークンのスコープのリストが含まれています。 In addition to that, the OAuth Applications API provides an endpoint to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} [check a token for validity](/rest/reference/apps#check-a-token){% else %}[check a token for validity](/rest/reference/apps#check-an-authorization){% endif %}. この情報を使用してトークンのスコープにおける変更を検出し、利用可能なアプリケーション機能の変更をユーザに通知します。
+この状況にうまく対応できるように、有効なトークンによるリクエストに対するすべてのAPIレスポンスには、[`X-OAuth-Scopes`ヘッダ][oauth scopes]も含まれています。 このヘッダには、リクエストを行うために使用されたトークンのスコープのリストが含まれています。 それに加えて、OAuthアプリケーションAPIは、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}[トークンの有効性のチェック](/rest/reference/apps#check-a-token){% else %}[トークンの有効性のチェック](/rest/reference/apps#check-an-authorization){% endif %}のためのエンドポイントを提供します。 この情報を使用してトークンのスコープにおける変更を検出し、利用可能なアプリケーション機能の変更をユーザに通知します。
 
 #### 認証リクエストの実施
 
diff --git a/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md b/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md
index aaa39afc95..13e6854e28 100644
--- a/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md
+++ b/translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md
@@ -24,7 +24,7 @@ topics:
 
 ### アプリケーションでアクセス可能なユーザのリポジトリを調べる
 
-ユーザは、個人でリポジトリを所有する他に、別のユーザやOrganizationが所有するリポジトリのコラボレータであることもあります。 Collectively, these are the repositories where the user has privileged access: either it's a private repository where the user has read or write access, or it's a {% if currentVersion != "github-ae@latest" %}public{% else %}internal{% endif %} repository where the user has write access.
+ユーザは、個人でリポジトリを所有する他に、別のユーザやOrganizationが所有するリポジトリのコラボレータであることもあります。 まとめると、ユーザが権限を持ってアクセスできるリポジトリがあります。それはユーザが読み取りあるいは書き込みアクセスを持つプライベートリポジトリであったり、ユーザが書き込み権限を持つ{% if currentVersion != "github-ae@latest" %}パブリック{% else %}インターナル{% endif %}リポジトリであったりします。
 
 アプリがユーザのどのリポジトリにアクセスできるかを決めるのは、[OAuthスコープ][scopes]および[Organizationのアプリケーションポリシー][oap]です。 以下のワークフローを使用して、これらのリポジトリを調べます。
 
@@ -89,11 +89,11 @@ client.organizations.each do |organization|
 end
 ```
 
-#### Return all of the user's organization memberships
+#### ユーザのすべてのOrganizationメンバーシップを返す
 
 このドキュメントを端から端まで読んだ方は、[ユーザのパブリックなOrganizationに属するメンバーを取得するAPIメソッド][list-public-orgs]に気付いたかもしれません。 ほとんどのアプリケーションでは、このAPIメソッドを避けるべきです。 このメソッドは、ユーザのパブリックなOrganizationに属するメンバーだけを返し、プライベートなOrganizationに属するメンバーは返しません。
 
-As an application, you typically want all of the user's organizations that your app is authorized to access. 上記のワークフローでは、まさにこれを実行しています。
+アプリケーションでは通常、アクセスを認可されたすべてのユーザのOrganizationが求められます。 上記のワークフローでは、まさにこれを実行しています。
 
 [basics-of-authentication]: /rest/guides/basics-of-authentication
 [list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user
diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md
index e0ac3ae715..5b6a926e80 100644
--- a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ $ curl https://api.github.com/users/defunkt
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -139,7 +139,7 @@ $ curl -i -u <em>your_username</em>:<em>your_token</em> {% data variables.produc
 > }
 ```
 
-This time, in addition to the same set of public information we retrieved for [@defunkt][defunkt github] earlier, you should also see the non-public information for your user profile. For example, you'll see a `plan` object in the response which gives details about the {% data variables.product.product_name %} plan for the account.
+今回は、以前に[@defunkt][defunkt github]について取得した公開情報の同じセットに加えて、あなたのユーザプロフィールのパブリックではない情報もあるはずです。 たとえば、アカウントの{% data variables.product.product_name %}プランに関する詳細を持つ`plan`オブジェクトがレスポンス中にあります。
 
 #### OAuthトークンのアプリケーションへの使用
 
@@ -188,10 +188,10 @@ $ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos
 これらの呼び出しから返される情報は、認証時にトークンが持っているスコープにより異なります。
 
 {% if currentVersion != "github-ae@latest" %}
-* A token with `public_repo` [scope][scopes] returns a response that includes all public repositories we have access to see on github.com.{% endif %}
-* A token with `repo` [scope][scopes] returns a response that includes all {% if currentVersion != "github-ae@latest" %}public{% else %}internal{% endif %} and private repositories we have access to see on {% data variables.product.product_location %}.
+* `public_repo` [スコープ][scopes]を持つトークンは、GitHub.com上で見るためのアクセス権を私たちが持つすべてのパブリックリポジトリを含むレスポンスを返します。{% endif %}
+* `repo` [スコープ][scopes]を持つトークンは、{% data variables.product.product_location %}上で私たちが見るためのアクセスを持つすねての{% if currentVersion != "github-ae@latest" %}パブリック{% else %}インターナル{% endif %}及びプライベートリポジトリを含むレスポンスを返します。
 
-As the [docs][repos-api] indicate, these methods take a `type` parameter that can filter the repositories returned based on what type of access the user has for the repository. こうすることで、直接所有するリポジトリ、Organizationのリポジトリ、またはチームによりユーザがコラボレーションするリポジトリに限定してフェッチすることができます。
+[Docs][repos-api]に記載されている通り、これらのメソッドは`type`パラメータを取り、これによって、ユーザがリポジトリに対して持つアクセス権に基づき、返されるリポジトリをフィルタリングできます。 こうすることで、直接所有するリポジトリ、Organizationのリポジトリ、またはチームによりユーザがコラボレーションするリポジトリに限定してフェッチすることができます。
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner"
@@ -216,7 +216,7 @@ $ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest
     {% data variables.product.api_url_pre %}/user/repos
 ```
 
-In this minimal example, we create a new private repository for our blog (to be served on [GitHub Pages][pages], perhaps). Though the blog {% if currentVersion != "github-ae@latest" %}will be public{% else %}is accessible to all enterprise members{% endif %}, we've made the repository private. In this single step, we'll also initialize it with a README and a [nanoc][nanoc]-flavored [.gitignore template][gitignore templates].
+この最小限の例では、ブログ用の新しいプライベートリポジトリを作成しています ([GitHub Pages][pages]で提供されるかもしれません)。 このブログは{% if currentVersion != "github-ae@latest" %}パブリックになり{% else %}すべてのEnterpriseメンバーからアクセスできるようになり{% endif %}ますが、このリポジトリはプライベートにしました。 このステップでは、READMEと[nanoc][nanoc]フレーバーの[.gitignore テンプレート][gitignore templates]によるリポジトリの初期化も行います。
 
 生成されたリポジトリは、`https://github.com/<your_username>/blog`にあります。 オーナーであるOrganization以下にリポジトリを作成するには、APIメソッドを `/user/repos`から`/orgs/<org_name>/repos`に変更するだけです。
 
@@ -225,7 +225,7 @@ In this minimal example, we create a new private repository for our blog (to be
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ Railsのような規模のプロジェクトになれば、万単位のIssueが
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ JSONの本文に加え、HTTPステータスコード `200`と`ETag`ヘッダに
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 `304`ステータスは、直近のリクエストからリソースが変更されておらず、レスポンスには本文が含まれないことを示しています。 特典として、`304`レスポンスは[レート制限][rate-limiting]にカウントされません。
diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md
index a3b91e7aad..6d335188f7 100644
--- a/translations/ja-JP/content/rest/overview/libraries.md
+++ b/translations/ja-JP/content/rest/overview/libraries.md
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
@@ -59,7 +59,7 @@ topics:
 
 ### Julia
 
-Library name | Repository | |---|---| **GitHub.jl**|[JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl)
+ライブラリ名 | リポジトリ | |---|---| **GitHub.jl**|[JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl)
 
 ### OCaml
 
@@ -67,7 +67,7 @@ Library name | Repository | |---|---| **GitHub.jl**|[JuliaWeb/GitHub.jl](https:/
 
 ### Perl
 
-Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub)
+ライブラリ名 | リポジトリ | ライブラリのmetacpan Webサイト |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub)
 
 ### PHP
 
@@ -75,11 +75,11 @@ Library name | Repository | metacpan Website for the Library |---|---|---| **Pit
 
 ### PowerShell
 
-Library name | Repository |---|---| **PowerShellForGitHub**|[microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub)
+ライブラリ名 | リポジトリ |---|---| **PowerShellForGitHub**|[microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub)
 
 ### Python
 
-Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)
+ライブラリ名 | リポジトリ |---|---| **gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (公式Webサイト)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)
 
 ### Ruby
 
@@ -87,7 +87,7 @@ Library name | Repository |---|---| **gidgethub**|[brettcannon/gidgethub](https:
 
 ### Rust
 
-Library name | Repository |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)
+ライブラリ名 | リポジトリ |---|---| **Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)
 
 ### Scala
 
diff --git a/translations/ja-JP/content/rest/overview/media-types.md b/translations/ja-JP/content/rest/overview/media-types.md
index 0e6dbd182d..e992993177 100644
--- a/translations/ja-JP/content/rest/overview/media-types.md
+++ b/translations/ja-JP/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ API がサポートする最も基本的なメディアタイプは次のとお
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/ja-JP/content/rest/overview/other-authentication-methods.md b/translations/ja-JP/content/rest/overview/other-authentication-methods.md
index 384952170f..f347a38253 100644
--- a/translations/ja-JP/content/rest/overview/other-authentication-methods.md
+++ b/translations/ja-JP/content/rest/overview/other-authentication-methods.md
@@ -45,7 +45,7 @@ $ curl -u <em>username</em>:<em>token</em> {% data variables.product.api_url_pre
 
 {% note %}
 
-**注釈:** {% data variables.product.prodname_dotcom %} は、すべての {% data variables.product.prodname_dotcom_the_website %} アカウントについて、API に対するパスポート認証を 2020 年 11 月 13 日で終了しました。{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、または {% data variables.product.prodname_ghe_cloud %} プランのアカウントもこれに該当します。 今後、{% data variables.product.prodname_dotcom %} API への認証には API トークンを使用してください。アクセストークンの扱い方に応じて、OAuth アクセストークン、 GitHub App インストールアクセストークン、個人アクセストークンなどを使用できます。 詳しい情報については、「[トラブルシューティング](/rest/overview/troubleshooting#basic-authentication-errors)」を参照してください。
+**注釈:** {% data variables.product.prodname_dotcom %} は、すべての {% data variables.product.prodname_dotcom_the_website %} アカウントについて、API に対するパスワード認証を 2020 年 11 月 13 日で終了しました。{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、または {% data variables.product.prodname_ghe_cloud %} プランのアカウントもこれに該当します。 今後、{% data variables.product.prodname_dotcom %} API への認証には API トークンを使用してください。アクセストークンの扱い方に応じて、OAuth アクセストークン、 GitHub App インストールアクセストークン、個人アクセストークンなどを使用できます。 詳しい情報については、「[トラブルシューティング](/rest/overview/troubleshooting#basic-authentication-errors)」を参照してください。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
index c5a87202e5..611d11a3d9 100644
--- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
@@ -34,7 +34,7 @@ JSON として送受信されます。
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: nginx
 > Date: Fri, 12 Oct 2012 23:33:14 GMT
 > Content-Type: application/json; charset=utf-8
@@ -126,7 +126,7 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
-> HTTP/1.1 401 Unauthorized
+> HTTP/2 401
 
 > {
 >   "message": "Bad credentials",
@@ -139,7 +139,7 @@ API は、無効な認証情報を含むリクエストを短期間に複数回
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 -u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > {
 >   "message": "Maximum number of login attempts exceeded. Please try again later.",
 >   "documentation_url": "{% data variables.product.doc_url_pre %}"
@@ -181,21 +181,21 @@ REST API を介して `node_id` を検索し、それらを GraphQL 操作で使
 
 1. 無効なJSONを送信すると、`400 Bad Request` レスポンスが返されます。
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 35
        
         {"message":"Problems parsing JSON"}
 
 2. 間違ったタイプの JSON 値を送信すると、`400 Bad Request` レスポンスが返されます。
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 40
        
         {"message":"Body should be a JSON object"}
 
 3. 無効なフィールドを送信すると、`422 Unprocessable Entity` レスポンスが返されます。
    
-        HTTP/1.1 422 Unprocessable Entity
+        HTTP/2 422
         Content-Length: 149
        
         {
@@ -211,13 +211,13 @@ REST API を介して `node_id` を検索し、それらを GraphQL 操作で使
 
 すべてのエラーオブジェクトにはリソースとフィールドのプロパティがあるため、クライアントは問題の内容を認識することができます。  また、フィールドの問題点を知らせるエラーコードもあります。  発生する可能性のある検証エラーコードは次のとおりです。
 
-| エラーコード名          | 説明                                                                          |
-| ---------------- | --------------------------------------------------------------------------- |
-| `missing`        | リソースが存在しません。                                                                |
-| `missing_field`  | リソースの必須フィールドが設定されていません。                                                     |
-| `invalid`        | フィールドのフォーマットが無効です。  Review the documentation for more specific information. |
-| `already_exists` | 別のリソースに、このフィールドと同じ値があります。  これは、一意のキー（ラベル名など）が必要なリソースで発生する可能性があります。          |
-| `unprocessable`  | 入力が無効です。                                                                    |
+| エラーコード名          | 説明                                                                 |
+| ---------------- | ------------------------------------------------------------------ |
+| `missing`        | リソースが存在しません。                                                       |
+| `missing_field`  | リソースの必須フィールドが設定されていません。                                            |
+| `invalid`        | フィールドのフォーマットが無効です。  詳細については、ドキュメントを参照してください。                       |
+| `already_exists` | 別のリソースに、このフィールドと同じ値があります。  これは、一意のキー（ラベル名など）が必要なリソースで発生する可能性があります。 |
+| `unprocessable`  | 入力が無効です。                                                           |
 
 リソースはカスタム検証エラー（`code` が `custom`）を送信する場合もあります。 カスタムエラーには常にエラーを説明する `message` フィールドがあり、ほとんどのエラーには、エラーの解決に役立つ可能性があるコンテンツを指す `documentation_url` フィールドも含まれます。
 
@@ -236,14 +236,14 @@ API v3 は、必要に応じて HTTP リダイレクトを使用します。 ク
 
 API v3 は、可能な限り各アクションに適切な HTTPメソッドを使用しようとします。
 
-| メソッド     | 説明                                                                                                                                                               |
-| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `HEAD`   | HTTP ヘッダ情報のみを取得するために、任意のリソースに対して発行できます。                                                                                                                          |
-| `GET`    | リソースを取得するために使用します。                                                                                                                                               |
-| `POST`   | リソースを作成するために使用します。                                                                                                                                               |
-| `PATCH`  | 部分的な JSON データでリソースを更新するために使用します。 たとえば、Issue リソースには `title` と `body` の属性があります。 A `PATCH` request may accept one or more of the attributes to update the resource. |
-| `PUT`    | リソースまたはコレクションを置き換えるために使用します。 `body` 属性のない `PUT` リクエストでは、必ず `Content-Length` ヘッダをゼロに設定してください。                                                                     |
-| `DELETE` | リソースを削除するために使用します。                                                                                                                                               |
+| メソッド     | 説明                                                                                                                            |
+| -------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `HEAD`   | HTTP ヘッダ情報のみを取得するために、任意のリソースに対して発行できます。                                                                                       |
+| `GET`    | リソースを取得するために使用します。                                                                                                            |
+| `POST`   | リソースを作成するために使用します。                                                                                                            |
+| `PATCH`  | 部分的な JSON データでリソースを更新するために使用します。 たとえば、Issue リソースには `title` と `body` の属性があります。 `PATCH`リクエストは、リソースを更新するための1つ以上の属性を受け付けることがあります。 |
+| `PUT`    | リソースまたはコレクションを置き換えるために使用します。 `body` 属性のない `PUT` リクエストでは、必ず `Content-Length` ヘッダをゼロに設定してください。                                  |
+| `DELETE` | リソースを削除するために使用します。                                                                                                            |
 
 ### ハイパーメディア
 
@@ -315,7 +315,7 @@ Basic 認証または OAuth を使用する API リクエストの場合、1 時
 
 {% endif %}
 
-When using the built-in `GITHUB_TOKEN` in GitHub Actions, the rate limit is 1,000 requests per hour per repository. For organizations that belong to a GitHub Enterprise Cloud account, this limit is 15,000 requests per hour per repository.
+ビルトインの`GITHUB_TOKEN`をGitHub Actionsで使う場合、レート制限はリポジトリごとに1時間あたり1,000リクエストです。 GitHub Enterprise Cloudアカウントに属するOrganizationでは、この制限はリポジトリごとに1時間あたり15,000リクエストです。
 
 認証されていないリクエストでは、レート制限により 1 時間あたり最大 60 リクエストまで可能です。 認証されていないリクエストは、リクエストを行っているユーザではなく、発信元の IP アドレスに関連付けられます。
 
@@ -327,7 +327,7 @@ API リクエストの返された HTTP ヘッダは、現在のレート制限
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 56
@@ -350,7 +350,7 @@ new Date(1372700873 * 1000)
 レート制限を超えると、次のようなエラーレスポンスが返されます。
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 0
@@ -370,7 +370,7 @@ OAuth アプリケーションが認証されていない呼び出しをより
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 5000
 > X-RateLimit-Remaining: 4966
@@ -396,7 +396,7 @@ Basic 認証または OAuth を使用してレート制限を超えた場合、A
 アプリケーションがこのレート制限をトリガーすると、次のような有益なレスポンスを受け取ります。
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Content-Type: application/json; charset=utf-8
 > Connection: close
 
@@ -449,7 +449,7 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/user
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -459,7 +459,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -469,7 +469,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
@@ -486,7 +486,7 @@ API は、任意のオリジンからの AJAX リクエストに対して、オ
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
-HTTP/1.1 302 Found
+HTTP/2 302
 Access-Control-Allow-Origin: *
 Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
@@ -495,7 +495,7 @@ CORS プリフライトリクエストは次のようになります。
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
-HTTP/1.1 204 No Content
+HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
diff --git a/translations/ja-JP/content/rest/reference/activity.md b/translations/ja-JP/content/rest/reference/activity.md
index d7c900f194..0c873eb1b3 100644
--- a/translations/ja-JP/content/rest/reference/activity.md
+++ b/translations/ja-JP/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ topics:
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
-# ETag 値を囲む引用符は重要
+# The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ Atom 形式のフィードを取得するには、`Accept` ヘッダで `applica
 #### レスポンス
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ HTTP/1.1 200 OK
 ``` shell
 # リクエストに認証を追加
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
-# Last-Modified ヘッダを正確に渡す
+# Last-Modifiedヘッダを正確に渡す
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/ja-JP/content/rest/reference/code-scanning.md b/translations/ja-JP/content/rest/reference/code-scanning.md
index 51a02be2df..a8777888e4 100644
--- a/translations/ja-JP/content/rest/reference/code-scanning.md
+++ b/translations/ja-JP/content/rest/reference/code-scanning.md
@@ -13,20 +13,20 @@ topics:
 
 {% data reusables.code-scanning.beta %}
 
-The {% data variables.product.prodname_code_scanning %} API lets you retrieve and update {% data variables.product.prodname_code_scanning %} alerts from a repository. You can use the endpoints to create automated reports for the {% data variables.product.prodname_code_scanning %} alerts in an organization or upload analysis results generated using offline {% data variables.product.prodname_code_scanning %} tools. 詳しい情報については、「[コード内のセキュリティの脆弱性とエラーを検出する](/github/finding-security-vulnerabilities-and-errors-in-your-code)」を参照してください。
+{% data variables.product.prodname_code_scanning %} APIを使うと、リオジトリから{% data variables.product.prodname_code_scanning %}アラートを取得して更新できます。 このエンドポイントを使って、Organization内で{% data variables.product.prodname_code_scanning %}アラートの自動化されたレポートを作成したり、オフラインの{% data variables.product.prodname_code_scanning %}ツールを使って生成された分析結果をアップロードしたりできます。 詳しい情報については、「[コード内のセキュリティの脆弱性とエラーを検出する](/github/finding-security-vulnerabilities-and-errors-in-your-code)」を参照してください。
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-### Custom media type for {% data variables.product.prodname_code_scanning %}
+### {% data variables.product.prodname_code_scanning %}のためのカスタムメディアタイプ
 
-There is one supported custom media type for the {% data variables.product.prodname_code_scanning %} REST API. You can use this with `GET` requests sent to the `/analyses/{analysis_id}` endpoint. When you use this media type with this operation, the response includes a subset of the actual data that was uploaded for the specified analysis, rather than details about the analysis, which is returned when you use the default media type. The response also includes additional data such as the `github/alertNumber` and `github/alertUrl` properties. The data is formatted as [SARIF version 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html).
+{% data variables.product.prodname_code_scanning %} REST API用にサポートされているカスタムメディアタイプが1つあります。 これは`/analyses/{analysis_id}`エンドポイントに送信される`GET`リクエストで利用できます。 この操作でこのメディアタイプを使う場合、レスポンスには指定された分析に関する詳細ではなく、その分析のためにアップロードされた実際のデータのサブセットが含まれます。分析の詳細は、デフォルトのメディアタイプを使った場合に返されます。 このレスポンスには、`github/alertNumber`や`github/alertUrl`プロパティなどの追加データも含まれます。 このデータは、[SARIF version 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html)でフォーマットされます。
 
     application/sarif+json
 
 詳しい情報については、「[メディアタイプ](/rest/overview/media-types)」を参照してください。
 
-#### Response using the custom media type
+#### カスタムメディアタイプを使用したレスポンス
 
-This example response is from a `GET` request to the `/analyses/{analysis_id}` endpoint, using `application/sarif+json` as the `Accept` header value. The example has had indendation and line breaks added for readability. For more information about this endpoint, see "[Get a {% data variables.product.prodname_code_scanning %} analysis for a repository](#get-a-code-scanning-analysis-for-a-repository)."
+このレスポンスの例は、`application/sarif+json`を`Accept`ヘッダの値として使用した`/analyses/{analysis_id}`への`GET`リクエストからのものです。 この例には、読みやすくなるようにインデントと改行が追加されています。 このエンドポイントに関する詳しい情報については「[リポジトリの{% data variables.product.prodname_code_scanning %}分析の取得](#get-a-code-scanning-analysis-for-a-repository)」を参照してください。
 
 ```
 {
diff --git a/translations/ja-JP/content/rest/reference/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md
index 0908c0868b..11953b5e15 100644
--- a/translations/ja-JP/content/rest/reference/enterprise-admin.md
+++ b/translations/ja-JP/content/rest/reference/enterprise-admin.md
@@ -18,7 +18,7 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints
 
 {% note %}
 
-**注釈:** この記事は {% data variables.product.prodname_ghe_cloud %} に適用されます。 To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu.
+**注釈:** この記事は {% data variables.product.prodname_ghe_cloud %} に適用されます。 {% data variables.product.prodname_ghe_managed %}あるいは{% data variables.product.prodname_ghe_server %}のバージョンを見るには、**{% data ui.pages.article_version %}**ドロップダウンメニューを使ってください。
 
 {% endnote %}
 
@@ -151,19 +151,6 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 {% endfor %}
 
 {% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
-
-## 保管時の暗号化
-
-保管時の暗号化の API を使用すると、{% data variables.product.product_name %} でデータを暗号化するキーを管理できます。 詳しい情報については、「[Enterprise 向けのデータ暗号化を設定する](/admin/configuration/configuring-data-encryption-for-your-enterprise)」を参照してください。
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## 管理統計
 
@@ -205,9 +192,9 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 
 ## LDAP
 
-You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.
+LDAP API を使用して、{% data variables.product.product_name %} ユーザまたは Team とそのリンクされた LDAP エントリ間のアカウント関係を更新するか、新しい同期をキューに入れることができます。
 
-LDAP マッピングエンドポイントを使用すると、ユーザまたは Team がマッピングする識別名（DN）を更新できます。 Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). [ユーザの LDAP マッピングの更新](#update-ldap-mapping-for-a-user)エンドポイントは、LDAP 同期が無効になっている場合でも、LDAP が有効になっていれば使用できます。
+LDAP マッピングエンドポイントを使用すると、ユーザまたは Team がマッピングする識別名（DN）を更新できます。 LDAP エンドポイントは通常、{% data variables.product.product_name %} アプライアンスで [LDAP 同期が有効](/enterprise/admin/authentication/using-ldap)になっている場合にのみ有効です。 [ユーザの LDAP マッピングの更新](#update-ldap-mapping-for-a-user)エンドポイントは、LDAP 同期が無効になっている場合でも、LDAP が有効になっていれば使用できます。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %}
@@ -231,7 +218,7 @@ LDAP マッピングエンドポイントを使用すると、ユーザまたは
 
 ## Management Console
 
-The Management Console API helps you manage your {% data variables.product.product_name %} installation.
+管理コンソール API は、{% data variables.product.product_name %} インストールの管理に役立ちます。
 
 {% tip %}
 
@@ -239,7 +226,7 @@ Management Console への API 呼び出しを行うときは、ポート番号
 
 ポート番号を提供しない場合は、自動的にリダイレクトに従うようにツールを設定する必要があります。
 
-You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/).
+{% data variables.product.product_name %} は、[独自の TLS 証明書](/enterprise/admin/guides/installation/configuring-tls/)を追加する前に自己署名証明書を使用するため、`cURL` を使用するときに [`-k` フラグ](http://curl.haxx.se/docs/manpage.html#-k)を追加する必要がある場合もあります。
 
 {% endtip %}
 
@@ -327,7 +314,7 @@ pre-receive 環境 API を使用すると、pre-receive フックの環境を作
 | `downloaded_at` | `string` | 最新のダウンロードの開始時刻。       |
 | `message`       | `string` | 失敗時に、エラーメッセージが生成されます。 |
 
-`state`が取り得る値は、`not_started`、`in_progress`、`success`、`failed`です。
+`state` の設定可能な値は、`not_started`、`in_progress`、`success`、`failed` です。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %}
diff --git a/translations/ja-JP/content/rest/reference/git.md b/translations/ja-JP/content/rest/reference/git.md
index abfda63f02..547657097d 100644
--- a/translations/ja-JP/content/rest/reference/git.md
+++ b/translations/ja-JP/content/rest/reference/git.md
@@ -19,7 +19,7 @@ Git Database APIでは、{% data variables.product.product_name %}上のGitデ
 
 ## Blob
 
-Git blob (バイナリラージオブジェクト) は、各ファイルのコンテンツをリポジトリに保存する際に使用されるオブジェクトタイプです。 ファイルの SHA-1 ハッシュが計算され、blob オブジェクトに保存されます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [blob オブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)の読み書きができます。 blob は[これらのカスタムメディアタイプ](#custom-media-types)を利用します。 API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
+Git blob (バイナリラージオブジェクト) は、各ファイルのコンテンツをリポジトリに保存する際に使用されるオブジェクトタイプです。 ファイルの SHA-1 ハッシュが計算され、blob オブジェクトに保存されます。 これらのエンドポイントを使用すると、{% data variables.product.product_name %} 上の Git データベースに対して [blob オブジェクト](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)の読み書きができます。 blob は[これらのカスタムメディアタイプ](#custom-media-types-for-blobs)を利用します。 API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
 
 ### Blob のカスタムメディアタイプ
 
diff --git a/translations/ja-JP/content/rest/reference/markdown.md b/translations/ja-JP/content/rest/reference/markdown.md
index e978876791..1d5c33f371 100644
--- a/translations/ja-JP/content/rest/reference/markdown.md
+++ b/translations/ja-JP/content/rest/reference/markdown.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ja-JP/content/rest/reference/migrations.md b/translations/ja-JP/content/rest/reference/migrations.md
index 5556469ede..a9e3f9610f 100644
--- a/translations/ja-JP/content/rest/reference/migrations.md
+++ b/translations/ja-JP/content/rest/reference/migrations.md
@@ -16,7 +16,7 @@ topics:
 
 ## Organization
 
-移行 API を使用できるのは、認証済みの Organization オーナーのみです。 For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)."
+移行 API を使用できるのは、認証済みの Organization オーナーのみです。 詳細については、「[Organization の権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)」と「[その他の認証方式](/rest/overview/other-authentication-methods)」を参照してください。
 
 {% data variables.migrations.organization_migrations_intro %}
 
diff --git a/translations/ja-JP/content/rest/reference/packages.md b/translations/ja-JP/content/rest/reference/packages.md
index 3a455e238f..9d63d9f5c2 100644
--- a/translations/ja-JP/content/rest/reference/packages.md
+++ b/translations/ja-JP/content/rest/reference/packages.md
@@ -1,5 +1,5 @@
 ---
-title: Packages
+title: パッケージ
 product: '{% data reusables.gated-features.packages %}'
 versions:
   free-pro-team: '*'
@@ -7,22 +7,22 @@ topics:
   - API
 ---
 
-The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+{% data variables.product.prodname_registry %} APIでは、REST APIを使ってパッケージを管理できます。 パッケージのリストアや削除についてさらに学ぶには、「[パッケージのリストアと削除](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。
 
-To use this API, you must authenticate using a personal access token.
-  - To access package metadata, your token must include the `read:packages` scope.
-  - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes.
-  - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes.
+このAPIを使うには、個人アクセストークンを使って認証を受けなければなりません。
+  - パッケージメタデータにアクセスするには、トークンに`read:packages`スコープが含まれていなければなりません。
+  - パッケージやパッケージのバージョンを削除するには、トークンに`read:packages`及び`delete:packages`スコープが含まれていなければなりません。
+  - パッケージやパッケージのバージョンをリストアするには、トークンに`read:packages`及び`write:packages`スコープが含まれていなければなりません。
 
-If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository.  For more information about scopes, see "[About scopes and permissions](/packages/learn-github-packages/about-github-packages#about-scopes-and-permissions-for-package-registries)" or "[Using the {% data variables.product.prodname_registry %} API with Docker](#using-the-github-packages-api-with-docker)."
+`package_type`が`npm`、`maven`、`rubygems`、`nuget`のいずれかなら、パッケージは{% data variables.product.prodname_dotcom %}リポジトリからの権限を継承するので、トークンには`repo`スコープも含まれていなければなりません。  スコープに関する詳しい情報については「[スコープと権限について](/packages/learn-github-packages/about-github-packages#about-scopes-and-permissions-for-package-registries)あるいは「[Dockerでの{% data variables.product.prodname_registry %} APIの利用](#using-the-github-packages-api-with-docker)」を参照してください。
 
-If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your personal access token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."
+SSOが有効化されたOrganization内のリソースにアクセスするために{% data variables.product.prodname_registry %} APIを使いたい場合は、個人アクセストークンにSSOを有効化しなければなりません。 詳しい情報については「[SAMLシングルサインオンと使う個人アクセストークンの認可](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。
 
-#### Using the {% data variables.product.prodname_registry %} API with Docker
+#### Dockerでの{% data variables.product.prodname_registry %} APIの利用
 
-If your package is a Docker image using the package namespace `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`, then your `package_type` is `docker` and your token must include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository.
+パッケージが`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`というパッケージの名前空間を使うDockerイメージなら、`package_type`は`docker`であり、パッケージが権限を{% data variables.product.prodname_dotcom %}リポジトリから継承するので、トークンには`repo`スコープが含まれていなければなりません。
 
-If your package is a Docker image using the package namespace `ghcr.io/OWNER/IMAGE-NAME`, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository.
+パッケージが`ghcr.io/OWNER/IMAGE-NAME`というパッケージの名前空間を使うDockerイメージなら、`package_type`は`container`であり、この`package_type`のアクセスあるいは管理のためにトークンに`repo`スコープが含まれている必要はありません。 `container`パッケージは、リポジトリは別に詳細な権限を提供します。
 
 
 {% for operation in currentRestOperations %}
diff --git a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
index 1f06c4c7af..2f911f8477 100644
--- a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md
@@ -32,7 +32,7 @@ GitHub Appは、デフォルトで`Read-only`メタデータ権限を持ちま
 - [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
 - [`GET /meta`](/rest/reference/meta#meta)
 - [`GET /organizations`](/rest/reference/orgs#list-organizations)
-- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization)
+- [`GET /orgs/:org`](/rest/reference/orgs#list-organizations)
 - [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects)
 - [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories)
 - [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
@@ -120,6 +120,9 @@ _検索_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _検索_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -678,6 +684,9 @@ _Team_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### "pull requests"に対する権限
 
@@ -767,6 +776,10 @@ _レビュー_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### "profile"に対する権限
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### "repository hooks"に対する権限
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md
index a1de896035..6f16ac9470 100644
--- a/translations/ja-JP/content/rest/reference/repos.md
+++ b/translations/ja-JP/content/rest/reference/repos.md
@@ -139,12 +139,12 @@ GitHub は、新しいデプロイメント、デプロイメントのステー
 
 GitHub は、あなたのサーバーに実際にアクセスすることはないということは覚えておきましょう。 デプロイメントイベントとやり取りするかどうかは、サードパーティインテグレーション次第です。 複数のシステムがデプロイメントイベントをリッスンできます。コードをサーバーにプッシュする、ネイティブコードを構築するなどを行うかどうかは、それぞれのシステムが決めることができます。
 
-Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% if currentVersion != "github-ae@latest" %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
+{% if currentVersion != "github-ae@latest" %}`public_repo` スコープおよび{% endif %}`repo` スコープはコードにもアクセス権を付与するのに対し、</code>repo_deployment</0> [OAuth scope](/developers/apps/scopes-for-oauth-apps) は、リポジトリのコードにアクセス権を付与**せず**、デプロイメントおよびデプロイメントステータスに絞ってアクセス権を付与することに注意してください。
 
 
 ### 非アクティブのデプロイメント
 
-When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。
+デプロイメントのステータスを `success` に設定すると、同じ環境に対する同じリポジトリ内の一時的でない、非本番環境のデプロイメントはすべて `inactive` になります。 これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。
 
 `state` を `inactive` に設定することで、一時的な環境が存在しなくなったことを伝えることができます。  `state` を `inactive` に設定すると、{% data variables.product.prodname_dotcom %} でデプロイメントが `destroyed` と表示され、アクセス権が削除されます。
 
@@ -155,7 +155,8 @@ When you set the state of a deployment to `success`, then all prior non-transien
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 ## 環境
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)."
+Environments APIを使うと、環境を作成、設定、削除できます。 環境に関する詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 環境のシークレットの管理については「[シークレット](/rest/reference/actions#secrets)」を参照してください。
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
@@ -193,7 +194,7 @@ Repo Merging API は、リポジトリ内にあるブランチのマージをサ
 
 ## ページ
 
-{% data variables.product.prodname_pages %} API は、{% data variables.product.prodname_pages %} の設定や、ビルドのステータスについての情報を取得します。 Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。
+{% data variables.product.prodname_pages %} API は、{% data variables.product.prodname_pages %} の設定や、ビルドのステータスについての情報を取得します。 サイトとビルドに関する情報は、{% if currentVersion != "github-ae@latest" %}Webサイトがパブリックの場合であっても{% endif %}認証を受けたユーザだけがアクセスできます。 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。
 
 レスポンスに `status` キーを持つ {% data variables.product.prodname_pages %} API エンドポイントにおいては、値は以下のいずれかになります。
 * `null`: サイトはまだビルドされていません。
diff --git a/translations/ja-JP/content/rest/reference/teams.md b/translations/ja-JP/content/rest/reference/teams.md
index a6e7ae278d..fac2d46537 100644
--- a/translations/ja-JP/content/rest/reference/teams.md
+++ b/translations/ja-JP/content/rest/reference/teams.md
@@ -18,7 +18,7 @@ topics:
 
 ## ディスカッション
 
-Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." ディスカッションの投稿に対するコメントの詳細については、「[Team ディスカッションのコメント API](/rest/reference/teams#discussion-comments)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
+Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 詳細については「[Teamディスカッションについて](//organizations/collaborating-with-your-team/about-team-discussions/)」を参照してください。 ディスカッションの投稿に対するコメントの詳細については、「[Team ディスカッションのコメント API](/rest/reference/teams#discussion-comments)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
@@ -26,7 +26,7 @@ Team ディスカッション API を使用すると、Team のページに投
 
 ## ディスカッションコメント
 
-Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." この API は、Team の Organization の、認証済みメンバーのみが利用できます。
+Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 詳細については「[Teamディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions/)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
diff --git a/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..8fde061cf8
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: GitHub スポンサーについて
+intro: '{% data variables.product.prodname_sponsors %} により、開発者コミュニティが依存しているオープンソースプロジェクトの設計、構築、維持に携わる人々や Organization を、{% data variables.product.product_name %} で直接、経済的に支援できます。'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### {% data variables.product.prodname_sponsors %} について
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %}詳細は「[{% data variables.product.prodname_sponsors %} の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+スポンサード開発者またはスポンサード Organization になると、{% data variables.product.prodname_sponsors %}に対する追加条項が適用されます。 詳細は、「[GitHub Sponsors に関する追加条項](/github/site-policy/github-sponsors-additional-terms)」を参照してください。
+
+### {% data variables.product.prodname_matching_fund %} について
+
+{% note %}
+
+**ノート:** {% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+{% data variables.product.prodname_matching_fund %} は、{% data variables.product.prodname_dotcom %} コミュニティのメンバーが[{% data variables.product.prodname_dotcom %} コミュニティガイドライン](/github/site-policy/github-community-guidelines)を推進するオープンソースソフトウェアを開発するのを支援することを目的としています。 スポンサード Organization に対する支払いと Organization からの支払は {% data variables.product.prodname_matching_fund %} を利用できません。
+
+{% data variables.product.prodname_matching_fund %} の資格を得るには、長期にわたって支えてくれるコミュニティを引き付けるようなプロフィールを作成する必要があります。 For more information about creating a strong profile, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."
+
+Donations between sponsored developers will not be matched.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### {% data variables.product.prodname_sponsors %} についてのフィードバックを共有する
+
+{% data reusables.sponsors.feedback %}
+
+### 参考リンク
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
+- {% data variables.product.prodname_blog %} の「[{% data variables.product.prodname_sponsors %} Team に関するよくある質問](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)」
diff --git a/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..6329dd90e9
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: Getting started with GitHub Sponsors
+intro: '{% data variables.product.prodname_sponsors %}と、スポンサーまたはオープンソースコントリビューターとしての参加のしかたについて学びます。'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..10d849147f
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: Quickstart for finding contributors to sponsor
+intro: Learn some best practices for finding open source contributors to sponsor.
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### Explore projects you depend on
+
+As you consider where to find open source contributors to sponsor, consider starting at https://github.com/sponsors/community.
+
+If you're logged in, the sponsors results will start with public dependencies that your repositories depend on.
+
+![The Babel open source project with highlighted text that says "4 of your repositories depend on this"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+You can also toggle which of your accounts to view results for and further filter or search.
+
+![Search options on sponsors community search page](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### Explore whom others sponsor
+
+You can see whom a user or organization sponsors on their {% data variables.product.prodname_dotcom %} profile page.
+
+### Consider how you benefit from different contributions
+
+Consider whether you benefit from the work of open source contributions, such as:
+ - ドキュメント
+ - Design
+ - Translation
+ - Newsletters
+ - Code reviews
+ - チュートリアル
+ - Mentoring
+ - Triaging issues and helping with project management
+ - Answering questions
+ - Event planning
+
+For more information on different types of open source contributions, see the [Open source guide](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+You can check if contributors you've benefited from have {% data variables.product.prodname_sponsors %} profiles by using search at https://github.com/sponsors/community.
+
+### Search for a specific project or contributor
+
+At https://github.com/sponsors/community, you can search by ecosystem, most used, recently updated, and more. You can filter search results for your personal user account or for organizations that you're a member of.
+
+### 次のステップ
+
+For more information on starting your sponsorship, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
diff --git a/translations/ja-JP/content/sponsors/guides.md b/translations/ja-JP/content/sponsors/guides.md
new file mode 100644
index 0000000000..565d547c2f
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Sponsors guides
+shortTitle: ガイド
+intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/ja-JP/content/sponsors/index.md b/translations/ja-JP/content/sponsors/index.md
new file mode 100644
index 0000000000..efd1738d8a
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Sponsors Documentation
+shortTitle: GitHub Sponsors
+intro: 'Invest in the open source projects you depend on, support digital infrastructure, and make open source careers possible by sponsoring open source contributors and their projects. Build a {% data variables.product.prodname_sponsors %} profile and receive compensation for your open source work.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: 'sponsors'
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..a0d32671bb
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: スポンサードアカウントでイベントに webhook を設定する
+intro: 新しいスポンサーシップを受領したとき、または既存のスポンサーシップに変更があったときにアラートがあるように webhook を設定することができます。
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### スポンサードアカウントでのイベントの webhook について
+
+支払い期間の終了に伴うキャンセルなど、スポンサーシップに対する変更を監視するために、スポンサードユーザまたはスポンサード Organization のアカウントに webhook を作成できます。 スポンサードアカウントに webhook を設定すると、スポンサーシップが作成、編集、削除されたときにアップデートを受け取れます。 詳細は、[`スポンサーシップ`webhook イベント](/webhooks/event-payloads/#sponsorship)を参照してください。
+
+### スポンサードアカウントでイベントの webhook を管理する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..ba4390fb79
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Getting started with the Sponsors GraphQL API
+intro: 'Using the GraphQL API, you can build custom integrations to manage or review your sponsorships.'
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+To get started with the GraphQL API, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+You can find the details about the Sponsors GraphQL API in the reference docs. For more information, see "[GraphQL reference](/graphql/reference)." We recommend using the GraphQL explorer to build your GraphQL calls. 詳しい情報については「[Explorerの利用](/graphql/guides/using-the-explorer)」を参照してください。
diff --git a/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/index.md b/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..37e7055360
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: Integrating with GitHub Sponsors
+intro: 'As an open source contributor, you can build custom tools to manage your GitHub sponsorships.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..6fdaa18539
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: オープンソースコントリビューターに対する GitHub スポンサーについて
+intro: オープンソースプロジェクトに貢献すれば、スポンサードコントリビューターとなって、作業に対する報酬を得られます。
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### {% data variables.product.prodname_sponsors %} に参加する
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %}詳細は「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照してください。
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data variables.product.prodname_sponsors %} に参加すると、あなたの {% data variables.product.prodname_sponsors %} プロフィールやその他の資金獲得プラットフォームの認知度を高めるため、コントリビュートしているオープンソースリポジトリにスポンサーボタンを追加できます。 詳しい情報については「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照してください。
+
+スポンサーシップの目標を設定できます。 詳細は「[スポンサーシップ目標を管理する](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal)」を参照してください。
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### スポンサーシップ層
+
+{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+
+あなたの作業を誰でも簡単にサポートできるように、月次および 1 回の層を含む、さまざまなスポンサーシップオプションを設定することをお勧めします。 特に、1 回の支払いにより、ユーザは定期的な支払いスケジュールが経済的に問題ないかどうかを心配することなく、あなたの努力に報いることができます。
+
+### スポンサーシップの支払い
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)."
+
+### {% data variables.product.prodname_sponsors %} についてのフィードバックを共有する
+
+{% data reusables.sponsors.feedback %}
+
+### 参考リンク
+- {% data variables.product.prodname_blog %} の「[{% data variables.product.prodname_sponsors %} Team に関するよくある質問](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)」
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..0b015608a8
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: スポンサーに連絡する
+intro: あなたの作業についての最新情報を受け取るようオプトインしたスポンサーに、メールを送信できます。
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### スポンサーシップのアップデートについて
+
+スポンサーは、メールで作業についての最新情報を受信するかどうかを選べます。 詳細は「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)」を参照してください。
+
+スポンサード開発者アカウントの場合、アップデートはユーザーアカウントのプライマリメールアドレスから送信されます。 ユーザアカウントでメールアドレスのプライバシーを有効化している場合は、`noreply@github.com` から送信されます。 スポンサードOrganizationの場合、アップデートはOrganizationの`noreply@github.com` メールアドレスから送信されます。 詳細は「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。
+
+### スポンサーに連絡する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..36e30acc58
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: GitHub スポンサーのプロフィール詳細を編集する
+intro: スポンサーとなる可能性がある人が、あなたの作業に関する情報を見ることができるように情報を更新できます。
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### スポンサープロフィールについて
+
+{% data variables.product.prodname_sponsors %} プロフィールは、スポンサーとなる可能性がある人に、サポートが必要な理由を伝えます。 スポンサーとなる人は、あなたのプロフィールの [**Sponsor**] ボタンをクリックして、あなたのスポンサープロフィールを見ることができます。 次の情報を設定しておくことをお勧めします。
+
+- あなたが貢献しているオープンソースの作業
+- オープンソース開発に携わっている理由
+
+### プロフィールの詳細を編集する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..e909c155de
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: GitHub スポンサーを通じてスポンサーシップを獲得する
+shortTitle: スポンサーシップを獲得する
+intro: 個人または Organization がスポンサードオープンソースコントリビューターになり、作業に対して支払いを受け取る、スポンサーシップの内容を更新する、およびスポンサーを表示して連絡することができます。
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..935e3aa58d
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: GitHub スポンサーからの支払いを管理する
+intro: '{% data variables.product.prodname_sponsors %} からの過去および将来の支払いに関する情報を確認し、銀行情報を編集することができます。'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### {% data variables.product.prodname_sponsors %} からの支払いについて
+
+{% data variables.product.prodname_sponsors %} からの支払いを管理できるのは、Stripe Connect を通じて支払っている場合だけです。 スポンサードユーザアカウントに対して、ACH 送金や電信を通じて支払われている場合は、スポンサードオープンソースのコントリビューターダッシュボードで [**Payouts**] タブが表示されません。 スポンサード Organization は、支払いに Stripe Connect しか使用できません。 詳細は、「[オープンソースコントリビューターに対する {% data variables.product.prodname_sponsors %} について](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)」を参照してください。
+
+{% data reusables.sponsors.payout-info %}
+
+### 支払い情報の表示と編集
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..0ddcf03073
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: スポンサーシップ目標を管理する
+intro: コミュニティがあなたをスポンサーすることによる影響を把握できるように、スポンサード開発者またはスポンサード Organization アカウントに対して目標を設定することができます。
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### スポンサーシップ目標について
+
+スポンサードアカウントの資金獲得目標を設定し、その目標をコミュニティと共有することができます。 目標を設定すると、オープンソースコミュニティにおける自分の影響を把握し、{% data variables.product.prodname_sponsors %} プログラムで影響力を持てるようになります。
+
+目標には、確保したいスポンサーの数、または毎月集めたい金額を設定できます。 一度に設定できる目標は 1 つだけです。 目標に達したら、次の目標を設定できます。
+
+### 目標の設定
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### 目標の編集
+
+目標を編集するとき、すでに達成した目標を選択することはできません。 たとえば、5 スポンサーをすでに達成している場合、目標を設定して 4 スポンサーにすることはできません。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### 目標の破棄
+
+いったん破棄した目標を、再度アクティブ化することはできません。 かわりに、新しい目標を設定してください。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..4524950a2f
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: スポンサーシップ層を管理する
+intro: 新しいスポンサーシップ層の追加や、既存スポンサーシップ層の編集、破棄が可能です。
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### スポンサーシップ層について
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### スポンサーシップ層を追加する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### スポンサーシップを編集または破棄する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### カスタム金額の層を有効化する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### カスタム金額の層を無効化する
+
+[**Sponsor tiers**] タブの [**Enable custom amounts**] オプションの選択を解除することで、カスタム金額の層を無効化できます。 カスタム金額を無効化すると、すべてのカスタム層が廃止されます。
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..78abdfa728
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: Organization の GitHub スポンサーシップを設定する
+intro: 'Organizationが{% data variables.product.prodname_sponsors %}に参加すると、作業に対する報酬を得られます。'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### {% data variables.product.prodname_sponsors %} に参加する
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Organizationとして{% data variables.product.prodname_sponsors %} 参加する招待を受け取ったら、以下のステップを実行すればスポンサードOrganizationになることができます。
+
+Organization 外の個人コントリビューターとして {% data variables.product.prodname_sponsors %} に参加するには、「[ユーザーアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照してください。
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. Organization の右にある [**Join the waitlist**] をクリックします。
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### スポンサードOrganizationプロフィールを記入する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### スポンサーシップ層を作成する
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### 銀行口座情報をサブミットする
+
+スポンサードOrganizationは、組織の専用銀行口座への支払いを、サポートされている地域で受け取る必要があります。 業務用の銀行口座は、[Open Collective](https://opencollective.com/)や[Stripe Atlas](https://stripe.com/atlas)といったサービスで設置できます。 Organization が法的に運営されている地域と、銀行口座の地域は一致している必要があります。 Organization のために {% data variables.product.prodname_sponsors %} を設定するユーザーも、サポートされている同じ地域に住んでいる必要があります。 {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+Open Collective を使用して Stripe Connect を設定する方法については、Open Collective のドキュメンテーションで「[{% data variables.product.prodname_sponsors %} の設定](https://docs.opencollective.com/help/collectives/github-sponsors)」を参照してください。
+
+### 納税情報をサブミットする
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### {% data variables.product.prodname_dotcom %} アカウントで 2 要素認証 (2FA) を有効にする
+
+Organization がスポンサード Organization になるには、{% data variables.product.product_name %} アカウントで 2FA を有効化する必要があります。 詳しい情報については「[2 要素認証の設定](/articles/configuring-two-factor-authentication)」を参照してください。
+
+### {% data variables.product.prodname_dotcom %} に申請をサブミットして承認を求める
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### 参考リンク
+- [{% data variables.product.prodname_sponsors %} について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..cfe2c15290
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: ユーザアカウントに GitHub スポンサーを設定する
+intro: 'スポンサード開発者になるには、{% data variables.product.prodname_sponsors %} に参加し、スポンサード開発者プロフィールに必要事項をすべて記入し、スポンサーシップ層を作成し、銀行口座情報と納税フォームをサブミットし、{% data variables.product.prodname_dotcom %} アカウントで 2 要素認証を有効にします。'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### {% data variables.product.prodname_sponsors %} に参加する
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Organization として {% data variables.product.prodname_sponsors %} に参加するには「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照してください。
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. Organization のオーナーの場合は、適格なアカウントが複数あります。 [**View your eligible accounts**] をクリックして、アカウントのリストからユーザ アカウントを見つけます。
+3. [**Join the waitlist**] をクリックします。
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+サポートされている地域で銀行口座をお持ちであれば、{% data variables.product.prodname_dotcom %} は 2 週間以内に申請をレビューします。
+
+### スポンサード開発者プロフィールを記入する
+
+{% data variables.product.prodname_dotcom %} で申請がレビューされたら、ユーザがあなたのスポンサーになれるようにスポンサード開発者プロフィールを設定できます。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### スポンサーシップ層を作成する
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### 銀行口座情報をサブミットする
+
+サポートされている地域にお住まいの場合は、次の手順に従って Stripe Connect アカウントを作成し、銀行口座情報をサブミットできます。 在住している地位と、銀行口座の地域は一致している必要があります。 {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### 納税情報をサブミットする
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### {% data variables.product.prodname_dotcom %} アカウントで 2 要素認証 (2FA) を有効にする
+
+スポンサード開発者になるには、{% data variables.product.product_name %} アカウントで 2FA を有効にする必要があります。 詳しい情報については「[2 要素認証の設定](/articles/configuring-two-factor-authentication)」を参照してください。
+
+### {% data variables.product.prodname_dotcom %} に申請をサブミットして承認を求める
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. [**Request approval**] をクリックします。 ![[Request approval] ボタン](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..c7fd60a977
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: GitHub スポンサーの納税情報
+intro: 'スポンサード開発者および Organization は、{% data variables.product.prodname_dotcom %} に納税フォームをサブミットする必要があり、自分の税金を算出して支払う責任を負います。'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+米国内の納税者は、支払いを受け取る前に W-9 をサブミットする必要があります。 米国外の納税者は、支払いを受け取る前に W-8BEN をサブミットする必要があります。 詳細は、「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)」と「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)」を参照してください。 {% data variables.product.prodname_dotcom %} から適切なフォームが送信されて期限が通知され、フォームに記入して送信する十分な時間が与えられます。
+
+If you are a taxpayer in the United States and earn more than $600 USD in a tax year, {% data variables.product.prodname_dotcom %} will send you a 1099 before January 31 of the next calendar year. 米国外の納税者に対しては、納税フォームを提供しません。
+
+{% data variables.product.prodname_dotcom %} は、{% data variables.product.prodname_sponsors %} の支払いについて源泉徴収しません。 スポンサード開発者は、自らの税金を算出して支払う責任を負います。
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### 参考リンク
+
+- [スポンサーとスポンサーシップを表示する](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..9877256c44
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: スポンサーとスポンサーシップを表示する
+intro: スポンサーとスポンサーシップについて、詳細情報と分析を表示し、エクスポートすることができます。
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### スポンサーとスポンサーシップについて
+
+現在と過去のスポンサーシップについての分析、スポンサーから受領した支払い、キャンセルなどのイベント、スポンサーシップのスポンサー層の変更を表示できます。 新しいスポンサーシップ、スポンサーシップの変更、スポンサーシップのキャンセルといったアクティビティも確認できます。 アクティビティのリストは、日付でフィルタリングできます。 表示しているアカウントのスポンサーシップデータを CSV または JSON 形式でエクスポートすることもできます。
+
+### スポンサーとスポンサーシップを表示する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. あるいは、スポンサーを層によってフィルタリングするには、**Filter（フィルター）**ドロップダウンメニューで、**Active tiers（アクティブな層）**または**Retired tiers（リタイアした層）**をクリックしてから、層を選択します。 ![層によってフィルタリングするドロップダウンメニュー](/assets/images/help/sponsors/filter-drop-down.png)
+
+### 最近のスポンサーシップアクティビティを表示する
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### スポンサーシップデータをエクスポートする
+
+スポンサーシップのトランザクションは 月単位でエクスポートできます。 {% data variables.product.company_short %} で、選択した月のスポンサーすべてのトランザクションデータがメールでエクスポートされます。 エクスポートが完了したら、別の月のデータをエクスポートできます。 スポンサードアカウントごとに、1 時間に 10 セットまでのデータをエクスポートできます。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. {% octicon "download" aria-label="The download icon" %}[**Export**] をクリックします。 ![エクスポートボタン](/assets/images/help/sponsors/export-all.png)
+1. エクスポートしたいデータの時間枠と形式を選択し、[**Start export**] をクリックします。 ![データエクスポートのオプション](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..05abc8ba23
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: Organizationへのスポンサーシップの関連付け
+intro: いずれかのOrganizationか支払っているスポンサーシップを、他のOrganizationに関連付けることができます。
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. 他のOrganizationにスポンサーシップを関連付けたい Organizationに移動します。
+2. Organization名の下で、{% octicon "heart" aria-label="The heart icon" %}[**Sponsoring**] をクリックします。 ![[Sponsoring] タブ](/assets/images/help/sponsors/sponsoring-tab.png)
+1. 右上隅で、{% octicon "gear" aria-label="The gear icon" %} [**Settings**] をクリックします。 ![[Settings] ボタン](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. [Link sponsorships to another account] のドロップダウンメニューで、こOrganizationのスポンサーシップを関連付けたいOrganizatioをクリックします。 ![アカウント選択のドロップダウンメニュー](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. [**Link account**] をクリックします。 ![[Link account] ボタン](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..8c98324044
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: オープンソースコントリビューターをスポンサーする
+intro: '{% data variables.product.product_name %} を通じて、コントリビューターのスポンサー、スポンサーしている開発者および Organization からの最新情報の受信、およびスポンサーバッジの表示ができます。'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..f49fc6612e
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: スポンサーシップを管理する
+intro: あなたのスポンサーシップを表示できる人や、スポンサードアカウントからメールで最新情報を受け取るかどうかを管理できます。
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### スポンサーシップのプライバシー設定を管理する
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### スポンサーシップのメールアップデートを管理する
+
+スポンサーしているアカウントがその作業に関するメールアップデートを送信できるかどうかを選択できます。 スポンサードアカウントは、あなたのメールアドレスにアクセスできません。
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### 参考リンク
+
+- [スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)
+- [スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)
diff --git a/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..f4b35c5974
--- /dev/null
+++ b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: オープンソースコントリビューターに対するスポンサー
+intro: あなたが頼りにしているオープンソースプロジェクトを設計、作成、維持する開発者または Organization に対して、毎月定期的に支払いをすることができます。
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### スポンサーシップについて
+
+{% data reusables.sponsors.sponsorship-details %}
+
+ユーザーアカウントの代わりにアカウントをスポンサーし、個人的に利益を得るプロジェクトに投資することができます。 Organization に代わってアカウントをスポンサーできますが、それには多くの理由があります。
+- Organization の作業が依存する特定のライブラリを維持する
+- Organization として依存しているエコシステム (たとえばブロックチェーン) に投資する
+- オープンソースを大切にする Organization としてブランド認知度を確立する
+- Organization が提供する製品を補完するライブラリを構築しているオープンソース開発者に感謝する
+
+{% data variables.product.product_name %} でアカウントをスポンサーするときは、クレジットカードを使用できます。 Organization が請求書で支払いしたい場合は、[お問い合わせ](https://support.github.com/contact/org-sponsors-waitlist)ください。
+
+{% data reusables.sponsors.no-fees %}詳細は「[{% data variables.product.prodname_sponsors %} の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。
+
+クレジットカードを使用してアカウントをスポンサーすると、その変更は直ちに有効になります。 {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+スポンサードアカウントがあなたのスポンサー層を廃止した場合、あなたが別の層を選択するか、プランをキャンセルするまで、あなたはその層にそのままとどまります。 詳細は「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照してください。
+
+スポンサーしたいアカウントが {% data variables.product.prodname_sponsors %} にプロフィールを持っていない場合は、アカウント参加を推奨できます。 詳細については、「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」と「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照してください。
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**注釈:** {% data variables.product.prodname_dotcom %} は、開発者の発言について責任を負いません。また、{% data variables.product.prodname_dotcom %} はスポンサードオープンソースプロジェクトについて何の保証もしません。 請求の責任は、資金を受ける開発者のみにあります。 スポンサーシップを提供する前に、信頼できる人かどうか確認してください。 詳細は、「[{% data variables.product.prodname_sponsors %} に関する追加条項](/github/site-policy/github-sponsors-additional-terms)」を参照してください。
+
+{% endnote %}
+
+### アカウントをスポンサーする
+
+アカウントをスポンサーするには、認証済みメールアドレスが必要です。 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。
+
+1. {% data variables.product.product_name %} で、スポンサーするユーザーまたは Organization のプロフィールに移動します。
+1. アカウントのスポンサーシップダッシュボードに移動します。
+   - 開発者をスポンサーする場合は、開発者の名前の下で [**Sponsor**] をクリックします。 ![[Sponsor] ボタン](/assets/images/help/profile/sponsor-button.png)
+   - Organization をスポンサーする場合は、開発者の名前の下で [**Sponsor**] をクリックします。 ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-org-button.png)
+1. オプションとして、ページの右側で、Organization に代わってアカウントをスポンサーする場合は、[**Sponsor as**] ドロップダウンメニューを使用して Organization をクリックします。 ![スポンサーとしてのアカウントを選択するドロップダウンメニュー](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![[Edit payment] ボタン](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![あなたのスポンサーシップを見ることができる人を選択するラジオボタン](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml
index 4cda566c83..d4dea5661b 100644
--- a/translations/ja-JP/data/glossaries/external.yml
+++ b/translations/ja-JP/data/glossaries/external.yml
@@ -88,7 +88,7 @@
 - 
   term: チェリーピック（する）
   description: >-
-    To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation.
+    変更のサブセットを一連の変更（通常はコミット）から選択して、新しい一連の変更を別の codebase 上に記録すること。Git では、これは「git cherry-pick」コマンドで実行するもので、別のブランチ上に存在するコミットによって引き起された変更を抽出し、現在のブランチの先端に基づき新規コミットとして記録します。詳しい情報については、Gitのドキュメンテーションの[git-cherry-pick](https://git-scm.com/docs/git-cherry-pick)を参照してください。
 - 
   term: 子チーム
   description: >-
@@ -181,7 +181,7 @@
 - 
   term: デフォルトブランチ
   description: >-
-    リポジトリ内の新しいPull Requestやコードのコミットのためのベースブランチ。それぞれのリポジトリは少なくとも1つのブランチを持ち、これはリポジトリを初期化したときにGitが作成します。最初のブランチは通常`main`と呼ばれ、多くの場合デフォルトブランチです。
+    リポジトリ内の新しいPull Requestやコードのコミットのためのベースブランチ。それぞれのリポジトリは少なくとも1つのブランチを持ち、これはリポジトリを初期化したときにGitが作成します。最初のブランチは通常{% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}と呼ばれ、多くの場合デフォルトブランチです。
 - 
   term: 依存グラフ
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    デフォルトの開発ブランチ。Git リポジトリを作成するたびに、「main」という名前のブランチが作成され、アクティブブランチとなります。ほとんどの場合、これにはローカル開発が含まれますが、単に慣習によるものであり、必須ではありません。
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}デフォルトの開発ブランチ。Gitリポジトリを作成すると、`main`という名前のブランチが作成され、アクティブなブランチになります。ほとんどの場合、これにはローカルの開発が含まれますが、これは純粋に慣例によるものであり、必須ではありません。{% else %}リポジトリのデフォルトブランチに対して、`master`の代わりとしてしばしば選択される名前。{% endif %}
 - 
   term: master
   description: >-
-    多くのGitリポジトリのデフォルトブランチ。デフォルトでは、新しいGitリポジトリをコマンドライン上で作成すると、`master`というブランチが作成されます。現在では、多くのツールがデフォルトブランチに代わりの名前を使うようになりました。たとえばGitHub上で新しいリポジトリを作成すると、デフォルトブランチは`main`になります。
+    多くのGitリポジトリのデフォルトブランチ。デフォルトでは、新しいGitリポジトリをコマンドライン上で作成すると、`master`というブランチが作成されます。現在では、多くのツールがデフォルトブランチに代わりの名前を使うようになりました。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}たとえばGitHub上で新しいリポジトリを作成すると、デフォルトブランチは`main`になります。{% endif %}
 - 
   term: メンバーグラフ
   description: リポジトリのすべてのフォークを表示するリポジトリグラフ。
diff --git a/translations/ja-JP/data/glossaries/internal.yml b/translations/ja-JP/data/glossaries/internal.yml
index a412efcce4..f3d1b6cc70 100644
--- a/translations/ja-JP/data/glossaries/internal.yml
+++ b/translations/ja-JP/data/glossaries/internal.yml
@@ -60,6 +60,10 @@
 - 
   term: Azure
   description: Microsoft のクラウドコンピューティングプラットフォーム。
+- 
+  term: Azure DevOps
+  description: >-
+    ソースコードのホスティング、Issue、CI/CDパイプライン、その他の開発者サービスを提供するMicrosoft製品。オンプレミスバージョンは、以前Team Foundation Serverとして知られていました。クラウドでホストされているバージョンは、Visual Studio Team Servicesとして知られていました。
 - 
   term: ベアリポジトリ
   description: >-
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    ソースコード管理などの Team サービスを提供する Microsoft 製品。
+    ソースコード管理及びその他のチームサービスを提供したMicrosoft製品の以前の名称。現在はAzure DevOps Serverとして知られています。
 - 
   term: Textile
   description: >-
diff --git a/translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..ec70522e48
--- /dev/null
+++ b/translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: パッケージのバージョン削除へのアクセス
+  description: >-
+    このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: デプロイメント
+  description: >-
+    このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - プルリクエストのマージ状態に関する詳細な情報。
+  description: >-
+    このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。
+  description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: プロジェクトイベントの詳細
+  description: >-
+    このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: コンテンツ添付ファイルの作成
+  description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: ラベルのプレビュー
+  description: >-
+    このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: プロジェクトのインポート
+  description: このプレビューは、プロジェクトのインポートのサポートを追加します。
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Teamレビューの割り当てプレビュー
+  description: >-
+    このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/ja-JP/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..c699bc4d84
--- /dev/null
+++ b/translations/ja-JP/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。'
+    reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。'
+    reason: アサインされた人を、マネキンにできるようになりました。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。'
+    reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。'
+    reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。'
+    reason: アサインされた人を、マネキンにできるようになりました。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: '`maintainer`は削除されます。代わりに`Sponsorship.sponsorable`を使ってください。'
+    reason: '`Sponsorship.maintainer`は削除されます。'
+    date: '2020-04-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: '`isUnlicensed`は削除されます。'
+    reason: 保留中の全メンバーはライセンスを消費します
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: '`pendingCollaborators`は削除されます。代わりに`pendingCollaboratorInvitations`フィールドを使用してください。'
+    reason: リポジトリの招待は、招待者だけではなくメールにも関連づけられるようになりました。
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。'
+    reason: '`timeline`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。'
+    reason: '`timeline`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: '`INVITEE_LOGIN`は削除されます。'
+    reason: '`INVITEE_LOGIN` は有効なフィールド値ではなくなりました。リポジトリの招待は、招待者だけではなく、メールにも関連付けられるようになりました。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: '`sponsor`は削除されます。代わりに`Sponsorship.sponsorEntity`を使ってください。'
+    reason: '`Sponsorship.sponsor`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: '`isUnlicensed`は削除されます。'
+    reason: すべてのメンバーはライセンスを消費します
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed`は削除されます。'
+    reason: すべての外部コラボレータはライセンスを消費します
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed`は削除されます。'
+    reason: すべての保留中のコラボレータはライセンスを消費します
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT`は削除されます。代わりにPullRequest.isDraftを使ってください。'
+    reason: DRAFTの状態はこのenumから削除されるので、代わりに`isDraft`を使わなければなりません。
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: nplasterer
diff --git a/translations/ja-JP/data/learning-tracks/README.md b/translations/ja-JP/data/learning-tracks/README.md
index a35c24e983..ce9934f997 100644
--- a/translations/ja-JP/data/learning-tracks/README.md
+++ b/translations/ja-JP/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # 学習トラック (別名 学習パス)
 
-学習トラックは、特定のテーマをマスターするのに役立つ記事の集まりです。 学習トラックは製品ごとに定義されています。
\ No newline at end of file
+学習トラックは、特定のテーマをマスターするのに役立つ記事の集まりです。 学習トラックは製品ごとに定義されています。 例としてhttps://docs.github.com/ja/actions/guidesを参照してください。
+
+製品の学習トラックのデータは2カ所で定義されています:
+
+1. 学習トラック名のシンプルな配列は、製品のサブランディングの索引ページの前付けで定義されています。
+
+    たとえば`content/actions/guides/index.md`では以下のようになっています:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. 各トラックの追加データは、`data`ディレクトリ中の**product**の名前のYAMLファイルで定義されています。
+
+    たとえば`data/learning-tracks/actions.yml`では、コンテンツファイルの`learningTracks`配列の各アイテムは、`title`や`description`、`guides`リンクの配列といった追加データとともに表現されています。
+
+    **バージョンごとに**このYAML中の1つの学習トラックを、`featured_track: true`を通じて「注目の」学習トラックとして指定する必要があります。これは、製品のサブランディングページの上部に表示されるように設定されます。 このプロパティがないと、テストは失敗します。
+
+    `featured_track`プロパティは、シンプルな論理値（すなわち`featured_track: true`）もしくは、バージョン付けの宣言を含む文字列（ たとえば`featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`）とすることができます。 バージョン付けを使用するなら、YMLファイルごとに複数の`featured_track`を持つことになりますが、必ず現在サポートされている各バージョンごとに1つだけがレンダリングされるようにしてください。 各バージョンに対して注目のリンクが1つより多くても少なくてもテストは失敗します。
+
+学習トラックのバージョン付けは、ページのレンダリングの時点で処理されます。 コードは[`lib/learning-tracks.js`](lib/learning-tracks.js)にあり、これは`page.render()`によって呼ばれます。 そして処理された学習トラックは、`layouts/product-sublanding.html`によってレンダリングされます。
+
+学習トラックのYAMLを検証するためのスキーマは[`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js)にあり、[`tests/content/lint-files.js`](tests/content/lint-files.js)によって実行されます。
diff --git a/translations/ja-JP/data/learning-tracks/actions.yml b/translations/ja-JP/data/learning-tracks/actions.yml
index cc6c9111d9..6ae1ae022a 100644
--- a/translations/ja-JP/data/learning-tracks/actions.yml
+++ b/translations/ja-JP/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: 'コードのビルドとテスト'
   description: 'まさにリポジトリ内に、カスタムの継続的インテグレーション（CI）を作成できます。'
diff --git a/translations/ja-JP/data/learning-tracks/admin.yml b/translations/ja-JP/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..824255c942
--- /dev/null
+++ b/translations/ja-JP/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: '{% data variables.product.prodname_ghe_managed %}を使ってみる'
+  description: '{% data variables.product.prodname_ghe_managed %}について学び、新しいEnterpriseの初期設定を完了してください。'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'インスタンスのデプロイ'
+  description: '選択したプラットフォームに{% data variables.product.prodname_ghe_server %}をインストールし、SAML認証を設定してください。'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'インスタンスのアップデート'
+  description: 'ステージングでアップグレードをテストし、ユーザにメンテナンスを通知し、最新機能とセキュリティアップデートのためにインスタンスをアップグレードしてください。'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'インスタンスの耐障害性を高めてください'
+  description: "開発者のコードをバックアップ、High Availability（HA）を設定して環境内の{% data variables.product.prodname_ghe_server %}の信頼性を保証してください。"
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'インスタンスのセキュリティを向上させてください'
+  description: "ネットワーク設定とセキュリティの機能をレビューし、Enterpriseのデータを保護するために{% data variables.product.prodname_ghe_server %}を実行するインスタンスを保護してください。"
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: '{% data variables.product.prodname_actions %}の設定'
+  description: '開発者が{% data variables.product.prodname_actions %}と合わせた{% data variables.product.product_location %}の強力なソフトウェア開発ワークフローの開発、自動化、カスタマイズ、実行をできるようにしてください。'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: '{% data variables.product.prodname_GH_advanced_security %}の設定'
+  description: "{% data variables.product.prodname_GH_advanced_security %}で開発者のコードの品質とセキュリティを改善してください。"
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/ja-JP/data/release-notes/2-21/19.yml b/translations/ja-JP/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..af052ec8f7
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/2-21/19.yml
@@ -0,0 +1,18 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - 'レプリカの昇格中に`jq: error (at <stdin>:0): Cannot index number with string "settings"`という警告メッセージが生じることがあります。'
+    - '`/settings/emails` ページにアクセスすると、ログアウトしてログインしなおしたときに不適切なリダイレクトの原因となりうる状態が保存されます。'
+    - '`vulnerable_version_ranges`内に大文字のパッケージ名を持つアドバイザリを持つ一部のコンポーネントで、依存関係グラフのアラートが表示されませんでした。'
+    - LDAP認証を設定されたインスタンス上でGitの操作を実行したユーザに500エラーが返されました。
+    - ghe-migratorでインポートエラーが生じた際に、プロセス全体が中断され、ログに十分なコンテキストが含まれないことがあります。
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - リポジトリへのプッシュをコマンドラインで行うと、セキュリティアラートが報告されません。
diff --git a/translations/ja-JP/data/release-notes/2-21/20.yml b/translations/ja-JP/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..a65e3ddd45
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/2-21/20.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - MySQLのレプリケーションで実行されるセットアップスクリプトは、データベースのフェイルオーバーの際に不要なデータベースの再シードを引き起こすことがありました。
+    - '`config-apply`は、不要な`rake db:migrate`の呼び出しのために必要以上に時間がかかることがありました。'
+    - オーケストレーターは、プライマリに接続できない場合のシーディングフェーズ中に、プライマリからレプリケーションをしていないMySQLレプリカにフェイルオーバーしてしまうことがありました。
+    - エラーのあるOrganizationもしくはプロジェクトが移行をブロックし、除外できませんでした。
+  changes:
+    - プリフライトチェックでは、デフォルトですべてのAWSのインスタンスタイプが許可されていました。
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - リポジトリへのプッシュをコマンドラインで行うと、セキュリティアラートが報告されません。
diff --git a/translations/ja-JP/data/release-notes/2-21/21.yml b/translations/ja-JP/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..735885b321
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/2-21/21.yml
@@ -0,0 +1,15 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - リポジトリへのプッシュをコマンドラインで行うと、セキュリティアラートが報告されません。
diff --git a/translations/ja-JP/data/release-notes/2-22/11.yml b/translations/ja-JP/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..9198ae2d07
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/2-22/11.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - 'レプリカの昇格中に`jq: error (at <stdin>:0): Cannot index number with string "settings"`という警告メッセージが生じることがあります。'
+    - MySQLのレプリカがプライマリへの接続に失敗することによって、継続的なバックアップのクラスタへのリストアが失敗することがありました。
+    - Treelightsコンテナのメモリ不足によって、構文強調が失敗することがありました。
+    - '`/settings/emails` ページにアクセスすると、ログアウトしてログインしなおしたときに不適切なリダイレクトの原因となりうる状態が保存されます。'
+    - '`vulnerable_version_ranges`内に大文字のパッケージ名を持つアドバイザリを持つ一部のコンポーネントで、依存関係グラフのアラートが表示されませんでした。'
+    - GitHubインテグレーションアプリケーションは、Issueコメント内のat-メンションで直接メンションされたときにTeamに通知できませんでした。
+    - ghe-migratorでインポートエラーが生じた際に、プロセス全体が中断され、ログに十分なコンテキストが含まれないことがあります。
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
diff --git a/translations/ja-JP/data/release-notes/2-22/12.yml b/translations/ja-JP/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..313febba38
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/2-22/12.yml
@@ -0,0 +1,22 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - アップグレード中に、`cleanup nomad job`の後プロセスが無期限に一時停止されます。
+    - '`ghe-cluster-failover`が`Trilogy::Error: trilogy_connect`というエラーメッセージで失敗します。'
+    - '`ghe-cluster-status-mysql`がフェイルオーバーに関する警告をエラーとして表示します。'
+    - MySQLのレプリケーションで実行されるセットアップスクリプトは、データベースのフェイルオーバーの際に不要なデータベースの再シードを引き起こすことがありました。
+    - '`config-apply`は、不要な`rake db:migrate`の呼び出しのために必要以上に時間がかかることがありました。'
+    - オーケストレーターは、プライマリに接続できない場合のシーディングフェーズ中に、プライマリからレプリケーションをしていないMySQLレプリカにフェイルオーバーしてしまうことがありました。
+    - エラーのあるOrganizationもしくはプロジェクトが移行をブロックし、除外できませんでした。
+    - 3つ以上のストレージホストを持つお客様が、空のノードではなく最も使われているディスクが選択されるために、ディザスタリカバリクラスタへリストアできませんでした。
+  changes:
+    - プリフライトチェックでは、デフォルトですべてのAWSのインスタンスタイプが許可されていました。
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
diff --git a/translations/ja-JP/data/release-notes/2-22/13.yml b/translations/ja-JP/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..5d1dc53e3b
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/2-22/13.yml
@@ -0,0 +1,20 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
diff --git a/translations/ja-JP/data/release-notes/3-0/0.yml b/translations/ja-JP/data/release-notes/3-0/0.yml
index a8f4b694cc..75cc565dde 100644
--- a/translations/ja-JP/data/release-notes/3-0/0.yml
+++ b/translations/ja-JP/data/release-notes/3-0/0.yml
@@ -134,6 +134,7 @@ sections:
     - レース条件によって依存関係グラフデータベースの移行が失敗したように見えることがあります。
     - 以前のGitHub Enterprise Serverのリリースからアップグレードされた、カスタムのタイムゾーンを持つインスタンスは、Web UIに不正確なタイムスタンプがあることがあります。
     - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。
+    - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。
   deprecations:
     - 
       heading: GitHub Enterprise Server 2.19の非推奨化
diff --git a/translations/ja-JP/data/release-notes/3-0/1.yml b/translations/ja-JP/data/release-notes/3-0/1.yml
index c665554e37..20aca59d40 100644
--- a/translations/ja-JP/data/release-notes/3-0/1.yml
+++ b/translations/ja-JP/data/release-notes/3-0/1.yml
@@ -45,6 +45,7 @@ sections:
     - '依存関係グラフがJavaScriptの`yarn.lock`マニフェストファイルのパースに失敗し、ログにHTTP 500エラーが残ります。'
     - '以前のGitHub Enterprise Serverのリリースからアップグレードされた、カスタムのタイムゾーンを持つインスタンスは、Web UIに不正確なタイムスタンプがあることがあります。'
     - 'Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。'
+    - 'Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。'
     - |
       ユーザは、アバターのようなアセットがロードされないことや、コードのプッシュ/プルの失敗を体験するかもしれません。これは、`haproxy-cluster-proxy`サービス内のPIDミスマッチによって生じることがあります。影響されたインスタンスがあるかは、以下のようにして判断します。
 
diff --git a/translations/ja-JP/data/release-notes/3-0/2.yml b/translations/ja-JP/data/release-notes/3-0/2.yml
index e72af6e790..58ef0586c7 100644
--- a/translations/ja-JP/data/release-notes/3-0/2.yml
+++ b/translations/ja-JP/data/release-notes/3-0/2.yml
@@ -31,6 +31,7 @@ sections:
     - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。
     - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。
     - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。
+    - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。
     - |
       ユーザは、アバターのようなアセットがロードされないことや、コードのプッシュ/プルの失敗を体験するかもしれません。これは、`haproxy-cluster-proxy`サービス内のPIDミスマッチによって生じることがあります。影響されたインスタンスがあるかは、以下のようにして判断します。
 
diff --git a/translations/ja-JP/data/release-notes/3-0/3.yml b/translations/ja-JP/data/release-notes/3-0/3.yml
index 6668da7e69..6f644e00a5 100644
--- a/translations/ja-JP/data/release-notes/3-0/3.yml
+++ b/translations/ja-JP/data/release-notes/3-0/3.yml
@@ -30,6 +30,7 @@ sections:
     - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。
     - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。
     - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。
+    - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。
     - |
       ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。
       この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)あるいは[GitHub Premium Support](https://premium.githubsupport.com/)に連絡して支援を求めてください。
diff --git a/translations/ja-JP/data/release-notes/3-0/4.yml b/translations/ja-JP/data/release-notes/3-0/4.yml
index da9f9f66b4..016b80f8ec 100644
--- a/translations/ja-JP/data/release-notes/3-0/4.yml
+++ b/translations/ja-JP/data/release-notes/3-0/4.yml
@@ -23,3 +23,4 @@ sections:
     - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
     - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。
     - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。
+    - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。
diff --git a/translations/ja-JP/data/release-notes/3-0/5.yml b/translations/ja-JP/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..0d2b8efb00
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/3-0/5.yml
@@ -0,0 +1,27 @@
+---
+date: '2021-04-14'
+intro: '{% data variables.product.prodname_ghe_server %} 3.0以降では最小のインフラストラクチャの要件が増加されました。詳しい情報については「[GitHub Enterprise Server 3.0以降に対する最小要件について](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)」を参照してください。'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - ログ転送設定に一部のログが含まれていませんでした。
+    - 'レプリカの昇格中に`jq: error (at <stdin>:0): Cannot index number with string "settings"`という警告メッセージが生じることがあります。'
+    - MySQLのレプリカがプライマリへの接続に失敗することによって、継続的なバックアップのクラスタへのリストアが失敗することがありました。
+    - カスタムのCA証明書を使用している場合、Pagesが公開されませんでした。
+    - Subdomain Isolationの"Test domain settings"プロンプトに、サブドメインに関連するパッケージが表示されませんでした。
+    - webhookと共に送信された`X-GitHub-Enterprise-Host`ヘッダに、そのHTTP POSTのペイロードを送信したGitHub Enterprise Serverインスタンスのホスト名ではなく、ランダムな文字列が含まれていました。
+    - GitHub Actionsが以前に有効化され、アップグレードの前に無効化されていると、2.22.xから3.0.xへのアップグレードが失敗しました。
+    - '`/settings/emails` ページにアクセスすると、ログアウトしてログインしなおしたときに不適切なリダイレクトの原因となりうる状態が保存されます。'
+    - GitHubインテグレーションアプリケーションは、Issueコメント内のat-メンションで直接メンションされたときにTeamに通知できませんでした。
+    - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されます。
+    - 依存関係グラフが完全に有効になっていない場合に、Secret Scanningのアラートのメール通知が認可されたユーザに送信されませんでした。
+    - ghe-migratorでインポートエラーが生じた際に、プロセス全体が中断され、ログに十分なコンテキストが含まれないことがあります。
+    - 非ASCII文字を含むJupyter notebookのレンダリングに失敗することがありました。
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。
diff --git a/translations/ja-JP/data/release-notes/3-0/6.yml b/translations/ja-JP/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..163e933839
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/3-0/6.yml
@@ -0,0 +1,30 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - アップグレード中に、`cleanup nomad job`の後プロセスが無期限に一時停止されます。
+    - '`ghe-cluster-failover`が`Trilogy::Error: trilogy_connect`というエラーメッセージで失敗します。'
+    - '`ghe-cluster-status-mysql`がフェイルオーバーに関する警告をエラーとして表示します。'
+    - MySQLのレプリケーションで実行されるセットアップスクリプトは、データベースのフェイルオーバーの際に不要なデータベースの再シードを引き起こすことがありました。
+    - アップグレードに、適切にインストールされた最新バージョンのActionsのランナーが含まれません。
+    - '`github-env`の設定でゾンビプロセスが残ることがあります。'
+    - '`config-apply`は、不要な`rake db:migrate`の呼び出しのために必要以上に時間がかかることがありました。'
+    - オーケストレーターは、プライマリに接続できない場合のシーディングフェーズ中に、プライマリからレプリケーションをしていないMySQLレプリカにフェイルオーバーしてしまうことがありました。
+    - エラーのあるOrganizationもしくはプロジェクトが移行をブロックし、除外できませんでした。
+    - 50以上のOrganizationに属しているユーザで、リポジトリの作成ボタンが無効になっていました。
+    - ブランチを削除すると、削除が成功した場合に何か問題が生じたことを示すエラーメッセージが一時的に表示されます。
+    - '`rms-packages`インデックスがサイト管理者のダッシュボードに表示されました。'
+    - Organizationのオーナーは、フォームで可視性の選択肢が正しく表示されないため、インターナルリポジトリを作成できませんでした。
+    - アクションのスターターワークフローの設定に問題がある場合に、リポジトリのアクションタブが500で表示されました。
+    - 3つ以上のストレージホストを持つお客様が、空のノードではなく最も使われているディスクが選択されるために、ディザスタリカバリクラスタへリストアできませんでした。
+    - Code Scanningのバックエンドサービスが、ホットパッチの適用後に確実には起動しませんでした。
+  changes:
+    - プリフライトチェックでは、デフォルトですべてのAWSのインスタンスタイプが許可されていました。
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
diff --git a/translations/ja-JP/data/release-notes/3-0/7.yml b/translations/ja-JP/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..83a77fcbc7
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/3-0/7.yml
@@ -0,0 +1,23 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
diff --git a/translations/ja-JP/data/release-notes/3-1/0-rc1.yml b/translations/ja-JP/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..cc710fa7a6
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: '{% data variables.product.product_location %}がリリース候補ビルドを実行しているなら、ホットパッチでアップグレードはできません。リリース候補を動作させるのは、テスト環境のみにすることをおすすめします。'
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security Secret Scanning
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security)は、{% data variables.product.prodname_ghe_server %} 3.1+で一般的に利用可能になりました。コミットされた認証情報をパブリック及びプライベートリポジトリでスキャンし、シークレットを見つけ、それらがリポジトリにコミットされた時点でシークレットのプロバイダもしくは管理者に通知します。
+
+          このリリースには、{% data variables.product.prodname_ghe_server %}上のSecret Scanningのベータからのいくつかの改善が含まれています。
+
+          - [パターンのカバレッジ](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories)を24パターンから37へ拡大
+          - [API](/rest/reference/secret-scanning)と[webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)の追加
+          - シークレットをコミットした際の[コミット作者への通知](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/)の追加
+          - 大量のシークレットのトリアージを容易にするインデックスビューの更新
+          - 多くのパターンでの偽陽性率の低下
+
+          {% data variables.product.prodname_GH_advanced_security %}を使用する管理者は、{% data variables.product.prodname_GH_advanced_security %}のSecret Scanningを[有効化して設定](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance)できます。{% data variables.product.prodname_GH_advanced_security %}のSecret Scanningを有効化する前に、[更新されたプラットフォームの最小要件](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューできます。
+    - 
+      heading: GitHub Advanced Securityの支払いの改善
+      notes:
+        - |
+          このリリースには、{% data variables.product.prodname_ghe_server %}に置ける{% data variables.product.prodname_GH_advanced_security %}の支払いに対するいくつかの改善が含まれています:
+
+          - {% data variables.product.prodname_GH_advanced_security %}のお客様は、OrganizationもしくはEnterpriseアカウントの支払いページでアクティブなコミッター数や未使用のコミッターシートの残数を見ることができるようになりました。EnterpriseでAdvanced Securityが購入されていると、管理者はEnterprise内で他のOrganizationによって使われているアクティブなコミッターシートを見ることもできます。詳しい情報については「[GitHub Acvenced Securityのライセンスについて](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)」及び「[GitHub Advanced Securityの利用状況の表示](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)」を参照してください。
+          - GitHub Advanced Securityのお客様は、OrganizationもしくはEnterpriseアカウントの支払いページでAdvanced Securityが有効化されている任意のリポジトリのアクティブなコミッター数を見ることができるようになりました。これらの変更は、支払いの管理者による購入したコミッターライセンス数の使用状況の対性を支援します。詳しい情報については「[Organizationのセキュリティ及び分析設定の管理](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。
+    - 
+      heading: Dependabotの改善
+      notes:
+        - |
+          このリリースには、{% data variables.product.prodname_ghe_server %}のDependabotアラートに対する改善が含まれています。
+
+          - Dependabotアラートを有効にしたユーザは、[GitHub Advisory Database](https://github.com/advisories)中のエントリにアクセスして、自分のリポジトリの中でどれが指定された脆弱性に影響を受けるかを見ることができます。この機能はパブリックベータとして利用できます。詳しい情報については「[リポジトリ中の脆弱な依存関係の表示と更新](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。
+          - 脆弱性がGitHub Advisory Databaseに追加されると、重要度が低もしくは中の脆弱性に対するDependabotアラートの[メール及びWeb通知](https://github.com/notifications)を受け取ることはなくなります。これらのアラートは、引き続きリポジトリのセキュリティタブからアクセスできます。詳しい情報については[リポジトリ中の脆弱な依存関係の表示と更新](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)を参照してください。
+          - リポジトリの`root`あるいは`docs`、`.github`フォルダーに`SECURITY.md`を追加することによって、プロジェクトのセキュリティ脆弱性を責任持って報告する方法を人々に指示できるようになりました。誰かがあなたのリポジトリでIssueを作成すると、その人にはプロジェクトのセキュリティポリシーへのリンクが示されます。詳しい情報については「[リポジトリへのセキュリティ歩シリーの追加](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)」を参照してください。
+    - 
+      heading: GitHub Actions Workflow Visualizationベータ
+      notes:
+        - |
+
+          GitHub Actionsは、実行ごとにワークフローの視覚的なグラフを生成するようになりました。ワークフローの可視化によって、以下ができるようになります。
+          - 複雑なワークフローの表示と理解
+          - リアルタイムでのワークフローの進捗の追跡
+          - ログとジョブのメタデータに容易にアクセスすることによって、素早く実行のトラブルシューティングを行う
+          - デプロイメントジョブの進捗のモニタと、デプロイメントのターゲットへの容易なアクセス
+
+          詳しい情報については「[可視化グラフの利用](/actions/managing-workflow-runs/using-the-visualization-graph)」」を参照してください。
+    - 
+      heading: OAuth 2.0デバイス認証の付与
+      notes:
+        - |
+          [OAuth 2.0 デバイス認証の付与](https://github.com/login/device)によって、任意のCLIクライアントもしくは開発者ツールが、ブラウザで二次的なシステムを使って認証を受けることができます。
+
+          [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)及び[GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow)を使う管理者は、既存のWebアプリケーションフローに加えてOAuth 2.0デバイス認証フローを[有効化して設定](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance)できます。OAuth 2.0デバイス認証フローを有効化する前に、[更新されたプラットフォームの最小要件](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューできます。
+    - 
+      heading: Pull request auto-merge
+      notes:
+        - |
+          自動マージでは、すべてのマージ要件が満たされたらPull Requestが自動的にマージされるように設定できます。こうすることで、ユーザはマージするためだけにPull Requestの状態を常にチェックする必要がなくなります。自動マージは、マージする権限を持つユーザによって、マージ要件を満たしていないPull Requestで有効化できます。詳しい情報については「[Pull Requestを自動的にマージ](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)」を参照してください。
+    - 
+      heading: カスタム通知
+      notes:
+        - |
+          個々のリポジトリから受信したい通知の種類をカスタマイズできます。詳しい情報については「[通知の設定](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。
+  changes:
+    - 
+      heading: 管理に関する変更
+      notes:
+        - チェックサムを事前に計算しておくことによって、リポジトリがロックされている時間が大幅に短くなり、より多くの書き込み操作が即座に成功し、単一リポジトリのパフォーマンスが改善されました。
+        - CodeQL CLIの最新リリースは、分析結果のGitHubへのアップロードをサポートします。これによって、GitHub Actions以外のCI/CDシステムを使いたいお客様がコード分析を実行しやすくなります。以前は、そういったユーザは別個のCodeQL Runnerを使わなければなりませんでした。CodeQL Runnerは引き続き利用できます。詳しい情報については「[CIシステムでのCode QL Code Scanningについて](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)」を参照してください。
+        - GitHub Actionsは、コミットメッセージ中の一般的なキーワードを探すことによる`push`及び`pull_request`ワークフローのスキップをサポートするようになりました。
+        - 4ヶ月以上経過したチェックアノテーションはアーカイブされます。
+    - 
+      heading: セキュリティの変更
+      notes:
+        - 'Pull RequestのIDをサブミットすることなくPull Request上にCode Scanningの結果を表示することは、サポートされなくなりました。詳しい情報については「[Code Scanningの設定](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)」及び「[CIシステムでのCode QL Code Scanningの設定] (/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests)」を参照してください。'
+        - SARIFアップロードのサポートは、アップロードごとに最大5000件の結果に増加しました。
+    - 
+      heading: 開発者の変更
+      notes:
+        - GitHub Appを設定する際には、複数のコールバックURLを指定できます。これは、複数のドメインもしくはサブドメインを持つサービスで利用できます。GitHubは、リクエストからのコールバックURLが認可コールバックURLリスト中にない場合には、常に認可を拒否します。
+        - GitHub Appのファイル権限は、アプリケーションがアクセスをリクエストできる最大で10のファイルに読み取りのみもしくは読み書きのアクセスをアプリケーション開発者が指定できるよう、更新されました。
+        - CodeQLは、様々な言語([C++](https://github.com/github/codeql/tree/main/cpp)、[JavaScript](https://github.com/github/codeql/tree/main/javascript)、[Python](https://github.com/github/codeql/tree/main/python)、[Java](https://github.com/github/codeql/tree/main/java)、[Go](https://github.com/github/codeql-go/tree/main))の[ライブラリやフレームワーク](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)をサポートするようになりました。CodeQLエンジンは、信頼できないユーザデータの多くのソースを検出できるようになり、それによってCode Scanningアラートの質と深さが改善されました。詳しい情報については「[CodeQLについて](https://codeql.github.com/docs/codeql-overview/about-codeql/)」を参照してください。
+        - GitHub Appを設定する際、認可コールバックURLは必須のフィールドです。開発者は、複数のコールバックURLを指定できるようになりました。これは、複数のドメインもしくはサブドメインを持つサービスで利用できます。GitHubは、リクエストからのコールバックURLが認可コールバックURLリスト中にない場合には、常に認可を拒否します。
+        - 'Webブラウザから、サブディレクトリを含むファイルのディレクトリ全体を削除します。詳しい情報については「[ファイルもしくはディレクトリの削除](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)」を参照してください。'
+        - 'Issue、ディスカッション、Pull Requestコメントで`#`の後に複数の語を含めて、検索をさらに絞り込めるようにしてください。'
+        - 'Issue、Pull Request、ディスカッションコメントを書いているときに、箇条書き、番号、タスクのためのリスト構文は、`return`あるいは`enter`を押した後に自動補完を行います。'
+    - 
+      heading: API の変更
+      notes:
+        - Code Scanning APIを利用すると、ユーザは静的分析のセキュリティテストの結果に関するデータをアップロードしたり、アラートに関するデータをエクスポートしたりできます。詳しい情報については[Code Scanning APIリファレンス](https://docs.github.com/ja/rest/reference/code-scanning)を参照してください。
+        - インストールを管理するための[GitHub Apps API](https://docs.github.com/rest/reference/apps)はAPIプレビューを卒業し、一般に利用可能なAPIになりました。これらのエンドポイントにアクセスするのに、[プレビューヘッダ](https://docs.github.com/rest/overview/api-previews)は不要になりました。
+  known_issues:
+    - GitHub Packagesのnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなり明日。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。
+    - '非常に大きな`check_annotations`テーブルを持つインスタンスで、スケジュールされたクリーンアップジョブがパフォーマンス低下を引き起こすことがあります。'
+    - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。
+    - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+  deprecations:
+    - 
+      heading: GitHub Enterprise Server 2.20の非推奨化
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20は、2021 年3月2日に廃止となりました**。これは、この日以降は重大なセキュリティの問題に対してであってもパッチリリースが行われなくなるということです。より優れたパフォーマンス、改善されたセキュリティ、新しい機能のために、[{% data variables.product.prodname_ghe_server %}の最新バージョンへのアップグレード](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server)をできるだけ早く行ってください。'
+    - 
+      heading: GitHub Enterprise Server 2.21の非推奨化
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21は、2021 年6月9日に廃止となりました**。これは、この日以降は重大なセキュリティの問題に対してであってもパッチリリースが行われなくなるということです。より優れたパフォーマンス、改善されたセキュリティ、新しい機能のために、[{% data variables.product.prodname_ghe_server %}の最新バージョンへのアップグレード](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server)をできるだけ早く行ってください。'
+    - 
+      heading: 旧来のGitHub App webhookイベントの非推奨化
+      notes:
+        - '{% data variables.product.prodname_ghe_server %} 2.21.0から、2つの旧来のGitHub Appsに関連するwebhookイベントが非推奨となり、{% data variables.product.prodname_ghe_server %} 3.2.0で削除されます。非推奨となったイベントの`integration_installation`と`integration_installation_repositories`には、サポートされることになる同等のイベントがあります。詳細な情報は[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/)にあります。'
+    - 
+      heading: 旧来のGitHub Appsのエンドポイントの非推奨化
+      notes:
+        - '{% data variables.product.prodname_ghe_server %} 2.21.0から、インストールアクセストークンを作成するための旧来のGitHub Appsのエンドポイントが非推奨となり、{% data variables.product.prodname_ghe_server %} 3.2.0で削除されます。詳細な情報は[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/)にあります。'
+    - 
+      heading: OAuth Application APIの非推奨化
+      notes:
+        - 'GitHubは、パスパラメータとして`access_token`を含むOAuthのアプリケーションエンドポイントをサポートしなくなりました。`access_token`をリクエストのボディに移すことにより、OAuth Appsのためのトークンをセキュアに管理できるようにする、新しいエンドポイントが導入されます。非推奨にはなりましたが、これらのエンドポイントはこのバージョンではまだ利用可能です。これらのエンドポイントは、{% data variables.product.prodname_ghe_server %} 3.4で削除しようとしています。詳細については[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/)を参照してください。'
+    - 
+      heading: GitHub Actionsの短いSHAサポートの非推奨化
+      notes:
+        - 'GitHub Actionsは、短縮バージョンのgitコミットSHAを使ったアクションの参照サポートを削除します。これによって、リポジトリ内のワークフローで動作しなくなるものがあるかもしれません。それらのワークフローを修正するには、アクションの参照を完全なコミットSHAを使うように更新しなければなりません。詳しい情報については「[GitHub Actionsのセキュリティ強化](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)」を参照してください。'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1は、[バックアップとディザスタリカバリ](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance)のために、最低でも[GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils)を必要とします。'
diff --git a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md
index 106536697d..66bb418987 100644
--- a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md
+++ b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md
@@ -4,7 +4,7 @@
 | `completed_workflow_run` | ワークフローのステータスが`completed`に変更されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。         |
 | `created_workflow_run`   | ワークフローの実行が作成されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[サンプルワークフローの作成](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。 |
 | `delete_workflow_run`    | ワークフローの実行が削除されたときにトリガーされます。 詳しい情報については「[ワークフローの実行の削除](/actions/managing-workflow-runs/deleting-a-workflow-run)」を参照してください。                                                                                         |
-| `disable_workflow`       | Triggered when a workflow is disabled.                                                                                                                                                                            |
-| `enable_workflow`        | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.                                                                                                                      |
+| `disable_workflow`       | ワークフローが無効化されたときにトリガーされます。                                                                                                                                                                                         |
+| `enable_workflow`        | 以前に`disable_workflow`によって無効化されたワークフローが有効化されたときにトリガーされます。                                                                                                                                                          |
 | `delete_workflow_run`    | ワークフローの実行が再実行されたときにトリガーされます。 詳しい情報については「[ワークフローの再実行](/actions/managing-workflow-runs/re-running-a-workflow)」を参照してください。                                                                                            |
 | `prepared_workflow_job`  | ワークフロージョブが開始されたときにトリガーされます。 ジョブに渡されたシークレットのリストを含みます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。          |
diff --git a/translations/ja-JP/data/reusables/actions/actions-cli.md b/translations/ja-JP/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..40a3fb58ca
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %}のセットアップに関する情報については「[GitHub CLIでのGitHub Actionsの管理](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md b/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..1a1617ed43
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+並列ジョブもしくはワークフローがキューに入っている場合、リポジトリ内の同じ並行グループを使う他のジョブもしくはワークフローが進行中だと、キューイングされたジョブもしくはワークフローは`保留中`になります。 この並行グループ内の以前の保留中のジョブもしくはワークフローは、キャンセルされます。 同じ並行グループ内にある実行中のジョブもしくはワークフローもキャンセルするには、`cancel-in-progress: true`を指定してください。
+
+##### 並行及びデフォルトの動作を使う例
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### 並行性を使って進行中のジョブもしくは実行をキャンセルする例
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/ja-JP/data/reusables/actions/concurrency-beta.md b/translations/ja-JP/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..16bb313244
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**ノート:** 並行処理は現在ベータであり、変更されることがあります。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/actions/enterprise-github-connect-warning.md b/translations/ja-JP/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..7d1b929fbe
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**ノート:** {% data variables.product.prodname_github_connect %}が有効化されていると、{% data variables.product.prodname_actions %}はまず{% data variables.product.prodname_ghe_server %}インスタンス上でリポジトリを見つけようとして、それから{% data variables.product.prodname_dotcom %}にフォールバックします。 ユーザが、{% data variables.product.prodname_dotcom %}上のOrganization及びリポジトリの名前に一致するOrganizationとリポジトリをEnterprise上に作成すると、{% data variables.product.prodname_dotcom %}リポジトリのところではEnterprise上のリポジトリが使用されます。 悪意あるユーザは、ワークフローの一部としてコードを実行するのに、この動作を利用できるかもしれません。
+
+{% endnote %}
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/enterprise-no-internet-actions.md b/translations/ja-JP/data/reusables/actions/enterprise-no-internet-actions.md
index d1c7ce7de6..e49299d8a9 100644
--- a/translations/ja-JP/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/ja-JP/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-{% data variables.product.prodname_ghe_server %}上の{% data variables.product.prodname_actions %}は、インターネットアクセスのない環境で動作するように設計されています。 デフォルトでは、ワークフローは{% data variables.product.prodname_dotcom_the_website %}及び[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)からのアクションを使うことができません。
+{% data variables.product.product_name %}上の{% data variables.product.prodname_actions %}は、完全なインターネットアクセスのない環境で動作するように設計されています。 デフォルトでは、ワークフローは{% data variables.product.prodname_dotcom_the_website %}及び[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)からのアクションを使うことができません。
diff --git a/translations/ja-JP/data/reusables/actions/forked-secrets.md b/translations/ja-JP/data/reusables/actions/forked-secrets.md
index c51a35d2d3..7bed9eb658 100644
--- a/translations/ja-JP/data/reusables/actions/forked-secrets.md
+++ b/translations/ja-JP/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-`GITHUB_TOKEN`を除き、フォークしたリポジトリからワークフローがトリガーされた場合、シークレットはランナーに渡されません。
+`GITHUB_TOKEN`を除き、フォークしたリポジトリからワークフローがトリガーされた場合、シークレットはランナーに渡されません。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..4ff0da79cb
--- /dev/null
+++ b/translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+{% data variables.product.product_location %} の {% data variables.product.prodname_GH_advanced_security %} の 2 つのコミッター数を記録して表示します。
+
+- **コミッター**は、Organization 内の少なくとも 1 つの{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリに貢献し、Enterprise ライセンスのシートを使用するコミッターの数です。 つまり、Organization のメンバー、外部のコラボレータでもあるか、Enterprise 内の Organization に参加するための保留中の招待状を持っています。
+- **このリポジトリ/Organization に固有**は、このリポジトリまたはこの Organization のリポジトリにのみコントリビュートしたコミッターの数です。 この数値は、そのリポジトリまたは Organization の {% data variables.product.prodname_GH_advanced_security %} を無効にすることで解放できるライセンスシートの数を示しています。
+
+一意のコミッターがない場合、これは、すべてのアクティブなコミッターが {% data variables.product.prodname_GH_advanced_security %} を使用する他のリポジトリまたは Organization にもコントリビュートしているということです。 そのリポジトリまたは Organization の機能を無効にしても、ライセンスのシートは解放されません。
+
+ユーザをEnterpriseアカウントから削除すると、そのユーザのライセンスは24時間以内に解放されます。
+
+{% note %}
+
+**ノート:** ユーザは複数のリポジトリもしくはOrganizationに貢献できます。 使用状況はEnterpriseアカウント全体にわたって計測され、各ユーザがいくつのリポジトリあるいはOrganizationに貢献していても、1つのシートしか使わないことを保証します。
+
+{% endnote %}
diff --git a/translations/ja-JP/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/ja-JP/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..ed15d25dfd
--- /dev/null
+++ b/translations/ja-JP/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_GH_advanced_security %}の各ライセンスは、それらの機能を使用できるアカウントもしくはシートの最大数を指定します。 定期的に、使用がライセンス容量の容量内であることを確認する必要があります。
diff --git a/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md
index 8d489c69d2..5b38a824ce 100644
--- a/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %}は{% data variables.product.prodname_advanced_security %}に対してコミッター単位で課金します。 {% if currentVersion == "free-pro-team@latest" %}詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}のライセンスの管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)」を参照してください。{% endif %}
+{% data variables.product.company_short %}は{% data variables.product.prodname_advanced_security %}に対してコミッター単位で課金します。 {% if currentVersion == "free-pro-team@latest" %}詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}のライセンスの管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)」を参照してください。{% elsif currentVersion ver_gt "enterprise-server@3.0" %}詳しい情報については「[Enterpriseの{% data variables.product.prodname_GH_advanced_security %}の管理](/admin/advanced-security)」を参照してください。{% endif %}
 
 リポジトリ管理者がOrganizationのリポジトリで{% data variables.product.prodname_advanced_security %}の機能を有効化できるようにするかをコントロールするポリシーを適用できます。 Enterpriseアカウントが所有するすべてのOrganizationに対して、あるいは選択した個々のOrganizationに対してポリシーを設定できます。
 
diff --git a/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..28f412cd02
--- /dev/null
+++ b/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+{% data variables.product.prodname_GH_advanced_security %} の優先順位を付けるリポジトリと Organization を決定するときは、それらを確認して次のことを特定する必要があります。
+
+- 会社の成功にとって最も重要なコードベース。 これらは、脆弱なコード、ハードコードされたシークレット、または脆弱な依存関係の導入が会社に最大の影響を与えるプロジェクトです。
+- コミット頻度が最も高いコードベース。 これらは最も積極的に開発されたプロジェクトであるため、セキュリティの問題が発生するリスクが高くなります。
+
+これらの Organization またはリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にした場合、一意のコミッターを追加したり、ライセンスのシートを使い切ったりせずに、追加できる他のコードベースを評価する必要があります。 この後、次に重要でビジーなコードベースを確認します。 ライセンスのシート数を増やす場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。
diff --git a/translations/ja-JP/data/reusables/advanced-security/ghas-helps-developers.md b/translations/ja-JP/data/reusables/advanced-security/ghas-helps-developers.md
index 849d427c93..9f999d583c 100644
--- a/translations/ja-JP/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/ja-JP/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-{% data variables.product.prodname_GH_advanced_security %}は、開発者がコードのセキュリティ及び品質を改善し、維持するための役に立ちます。 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください。
+{% data variables.product.prodname_GH_advanced_security %}は、開発者がコードのセキュリティと品質を改善し、維持するための役に立ちます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください。
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/ja-JP/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..22f04ef93d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+リポジトリで{% data variables.product.prodname_advanced_security %}を有効化あるいは無効化すると、{% data variables.product.prodname_dotcom %}はライセンスの利用に関する変更の概要を表示します。 {% data variables.product.prodname_GH_advanced_security %} へのアクセスを無効にすると、「一意」のコミッターが使用するシートが解放されます。
+
+ライセンス制限を超えている場合、{% data variables.product.prodname_GH_advanced_security %} はすでに有効になっているすべてのリポジトリで引き続き動作します。 ただし、{% data variables.product.prodname_GH_advanced_security %} が新しいリポジトリに対して有効になっている Organization では、リポジトは機能が無効の状態で作成されます。 加えて、既存のリポジトリに対する{% data variables.product.prodname_GH_advanced_security %}の有効化のオプションは利用できなくなります。{% if currentVersion == "free-pro-team@latest" %}パブリックリポジトリの可視性をプライベートに変更すると、そのリポジトリでは{% data variables.product.prodname_GH_advanced_security %}は無効化されます。{% endif %}
+
+一部のリポジトリで {% data variables.product.prodname_GH_advanced_security %} を無効にするか、ライセンスサイズを増やすと、一部のシートを解放した直後に {% data variables.product.prodname_GH_advanced_security %} を有効にするオプションが通常どおり動作します。
diff --git a/translations/ja-JP/data/reusables/branches/set-default-branch.md b/translations/ja-JP/data/reusables/branches/set-default-branch.md
index 225b533a0a..fff5e73db9 100644
--- a/translations/ja-JP/data/reusables/branches/set-default-branch.md
+++ b/translations/ja-JP/data/reusables/branches/set-default-branch.md
@@ -1 +1 @@
-新しいリポジトリのためのデフォルトブランチの名前を設定できます。 For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)," "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)," and {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)."{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)."{% endif %}
+新しいリポジトリのためのデフォルトブランチの名前を設定できます。 詳しい情報については、「[リポジトリのデフォルトブランチの管理](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)」、「[Organization内のリポジトリのデフォルトブランチ名の管理](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」、{% if currentVersion == "free-pro-team@latest" %}「[Enterpriseアカウントでのリポジトリ管理ポリシーの強制](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)」{% else %}「[Enterpriseでのリポジトリ管理ポリシーの強制](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)」{% endif %}を参照してください。
diff --git a/translations/ja-JP/data/reusables/cli/actions-cli-version.md b/translations/ja-JP/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..20935b5858
--- /dev/null
+++ b/translations/ja-JP/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %}関連のすべてのコマンドを利用するには、バージョン1.9.0以降を使わなければなりません。
diff --git a/translations/ja-JP/data/reusables/cli/cli-auth.md b/translations/ja-JP/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..7a7bd0ceaf
--- /dev/null
+++ b/translations/ja-JP/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %}は、{% data variables.product.prodname_dotcom %}アカウントを使って認証できます。 {% data variables.product.prodname_cli %}コマンドを実行する前に、`gh auth login`を実行して認証を受けなければなりません。 コマンドライン認証に関する詳しい情報については「[`gh auth login`](https://cli.github.com/manual/gh_auth_login)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/cli/cli-manual.md b/translations/ja-JP/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..86f69d5cfa
--- /dev/null
+++ b/translations/ja-JP/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %}に関する詳しい情報については、[{% data variables.product.prodname_cli %}マニュアル](https://cli.github.com/manual/)を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/cli/cli-repo.md b/translations/ja-JP/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..d6a46fb91c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %}のコマンドは、操作したいリポジトリ内で実行しなければならないので、まずリポジトリのローカルコピーがあるディレクトリに移動しなければなりません。 あるいは、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY`もしくは`--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY`もしくは`--repo OWNER/REPOSITORY`{% endif %}を渡してリポジトリを指定することもできます。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`HOSTNAME`は、{% data variables.product.product_location %}の名前で置き換えてください。 {% endif %}`OWNER`は、リポジトリのオーナーで置き換えてください。 `REPOSITORY` は、リポジトリ名に置き換えてください.
diff --git a/translations/ja-JP/data/reusables/cli/download-update-cli.md b/translations/ja-JP/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..c6c33c9fc3
--- /dev/null
+++ b/translations/ja-JP/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %}をダウンロードもしくはアップグレードするには、[{% data variables.product.prodname_cli %} README](https://github.com/cli/cli#installation)中の指示に従ってください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..9ad533ca1d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`、`csharp`、`go`、`java`、`javascript`、`python`
diff --git a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
index a6a427fdf8..eec8caa569 100644
--- a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
+++ b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      {% data variables.product.prodname_actions %}の利用（「<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">アクションを使う{% data variables.product.prodname_code_scanning %}のセットアップ</a>」参照）あるいはサードパーティの継続的インテグレーション（CI）システム中での{% data variables.product.prodname_codeql_runner %}の利用（「<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">CIシステム中での{% data variables.product.prodname_codeql %}コードスキャンの実行</a>」参照）。
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      サードパーティ
-    </td>
-    
-    <td>
-      {% data variables.product.prodname_actions %}の利用（「<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">アクションを使う{% data variables.product.prodname_code_scanning %}のセットアップ</a>」）あるいは外部で生成して{% data variables.product.product_name %}へアップロード（「<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">{% data variables.product.prodname_dotcom %}へのSARIFファイルのアップロード</a>」）。
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | {% data variables.product.prodname_actions %}の利用（「[Actionsを使う{% data variables.product.prodname_code_scanning %}のセットアップ](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)」）もしくはサードパーティの継続的インテグレーション（CI）システムでの{% data variables.product.prodname_codeql %}分析の実行（「[CIシステムでの{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}）](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)」）。
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | {% data variables.product.prodname_actions %}の利用（「[アクションを使う{% data variables.product.prodname_code_scanning %}のセットアップ](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)」参照）あるいはサードパーティの継続的インテグレーション（CI）システム中での{% data variables.product.prodname_codeql_runner %}の利用（「[CIシステム中での{% data variables.product.prodname_codeql %}コードスキャンの実行](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)」参照）。
+{%- endif %}
+| サードパーティ |
+{% data variables.product.prodname_actions %}の利用（「[アクションを使う{% data variables.product.prodname_code_scanning %}のセットアップ](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)」）あるいは外部で生成して{% data variables.product.product_name %}へアップロード（「[{% data variables.product.prodname_dotcom %}へのSARIFファイルのアップロード](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)」）。
diff --git a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
index c77c79cd4e..0591fe4b5c 100644
--- a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**ノート:** SARIFアップロードは、アップロードごとに1000件の結果をサポートしています。 この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。
+**ノート:** SARIFのアップロードは、アップロードごとに最大で{% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %}件の結果をサポートしています。 この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..4ac3525e0f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**ノート:** {% data variables.product.product_name %}で{% data variables.product.prodname_code_scanning %}の結果として表示するためにSARIFデータをアップロードすることは、{% data variables.product.prodname_GH_advanced_security %}が有効化されたOrganizationが所有するリポジトリ{% if currentVersion == "free-pro-team@latest" %}と{% data variables.product.prodname_dotcom_the_website %}上のパブリックリポジトリ{% endif %}でサポートされています。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..8bc758679d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+{% data variables.product.prodname_codeql_cli %}は、コードの分析に利用できるスタンドアローンの製品です。 その主な目的は、コードベースのデータベース表現である{% data variables.product.prodname_codeql %}データベースを生成することです。 データベースの準備ができれば、それに対してインタラクティブにクエリを実行したり、SARIFフォーマットで結果セットを生成するためのクエリのスイートを実行して、結果を{% data variables.product.product_location %}にアップロードしたりできます。
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/codespaces/about-personalization.md b/translations/ja-JP/data/reusables/codespaces/about-personalization.md
index 87cfca3c55..bfa56b8edc 100644
--- a/translations/ja-JP/data/reusables/codespaces/about-personalization.md
+++ b/translations/ja-JP/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-自分のアカウントで作成したcodespaceについて、codespace環境の様々な側面をパーソナライズすることもできます。 パーソナライズには、シェルの環境設定や追加のツールが含まれます。
+[dotfiles](https://dotfiles.github.io/tutorials/)リポジトリと[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)を使用して、作成した任意のcodespace環境の様々な面をパーソナライズすることもできます。 パーソナライズには、シェルの環境設定や追加のツールが含まれます。
diff --git a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..81e2b5041c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+アプリケーションのテストとデバッグのために、codespace中のポートをフォワードできます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..325636d0f9
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+リポジトリのための{% data variables.product.prodname_codespaces %}の設定が変更された後、codespaceのコンテナをリビルドしてその変更を既存のcodespaceに適用できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index af85b53287..4400acc1c9 100644
--- a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. {% data variables.product.prodname_vscode %}の左サイドバーで、 Remote Explorerのアイコンをクリックしてください。 ![{% data variables.product.prodname_vscode %}のRemote Explorerアイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. {% data variables.product.prodname_vscode %}の左サイドバーで、 Remote Explorerのアイコンをクリックしてください。 ![{% data variables.product.prodname_vscode %}のRemote Explorerアイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..cd09a0cb7c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+codespaceは、Basic、Standard、Premiumの3種類のリモートマシンから選択して実行できます。 これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**注釈:** {% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+マシンタイプを切り替えることで、作業に最も適したリソースを柔軟に選択できます。 特待のタスクでは、様々なマシンタイプが必要になることがあります。
+
+* ファイルの更新とPull Requestの作成に対しては**Basic**
+* Webサイトの編集に対しては**Standard**
+* データ分析のような高負荷のコンピューティングタスクに対しては**Premium**
diff --git a/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..737d91787e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+新しいコードであれ、設定の変更であれ、codespaceに変更を加えたら、その変更をコミットしたくなるでしょう。 リポジトリに変更をコミットすれば、このリポジトリからcodespaceを作成する他の人が、同じ設定になることを保証できます。 これはまた、{% data variables.product.prodname_vscode %}機能拡張の追加など、あなたが行うすべてのカスタマイズが、すべてのユーザに対して現れるようになるということでもあります。
+
+詳しい情報については「[codespaceでのソースコントロールの利用](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..f4722c8f52
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. codespaceで、テキストエディタの下で"Ports（ポート）"をクリックしてください。 ![ポートタブ](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..0c6f3d536b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+コマンドパレットにアクセス（`shift command P` / `shift control P`）し、続いて"Codespaces: Rebuild Container"と入力していってください。 **Codespaces: Rebuild Container**をクリックしてください。 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..c3e876cf70
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+codespaceの設定の変更でコンテナエラーが生じた場合、codespaceはリカバリモードで動作し、エラーメッセージが表示されます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/release-stage.md b/translations/ja-JP/data/reusables/codespaces/release-stage.md
index e190ef47ab..304cbc403c 100644
--- a/translations/ja-JP/data/reusables/codespaces/release-stage.md
+++ b/translations/ja-JP/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**注釈:** {% data variables.product.prodname_codespaces %} は現在限定パブリックベータであり、変更されることがあります。 ベータ期間中、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_codespaces %}の可用性について保証しません。 ベータへの参加に関する詳しい情報については「[{% data variables.product.prodname_codespaces %}について](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)」を参照してください。
+**注釈:** {% data variables.product.prodname_codespaces %} は現在限定パブリックベータであり、変更されることがあります。 ベータへの参加に関する詳しい情報については「[{% data variables.product.prodname_codespaces %}について](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)」を参照してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..7494d533a1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+複数のレベルで同じ名前のシークレットが存在する場合、低いレベルのシークレットが優先されます。 たとえば、Organization レベルのシークレット名がリポジトリレベルのシークレット名と同じ場合、リポジトリレベルのシークレット名が優先されます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/secrets-naming.md b/translations/ja-JP/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..7edc62b31f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+シークレットの名前には次のルールが適用されます。
+
+* シークレット名には、英数字（`[a-z]`、`[A-Z]`、`[0-9]`）または下線（`_`）のみを含めることができます。 スペースは使用できません。
+* シークレット名の最初を `GITHUB_` プレフィックスにすることはできません。
+* シークレット名の最初を数字にすることはできません。
+* シークレット名は大文字と小文字を区別しません。
+* シークレット名は、作成されたレベルで一意である必要があります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/secrets-on-start.md b/translations/ja-JP/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..6c20d574b1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+シークレットを作成すると、新しいcodespaceを作成したり、codespaceを再起動したりすれば、利用できるようになります。 現在のcodespaeで作成したばかりのシークレットを使うには、codespeceをサスペンドして再開する必要があります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md b/translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..2a62311454
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. Activityバーで、**Source Control（ソースコントロール）**ビューをクリックしてください。 ![ソースコントロールビュー](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/source-control-display.md b/translations/ja-JP/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..537d6acc2e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. Activityバーで、**Source Control（ソースコントロール）**ビューをクリックしてください。
+
+  ![ソースコントロールビュー](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/type-port-label.md b/translations/ja-JP/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..99b9f6faa7
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. ポートのラベルを入力し、Enterを押してください。 ![ポートのラベルを入力するためのテキストボックス](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index cfb19b8731..4d6c6dd0bd 100644
--- a/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-[github.com/codespaces](https://github.com/codespaces)で、自分のユーザアカウントが所有しているすべてのcodespaceを見ることができます。
+作成した利用可能なすべてのcodespaceは[github.com/codespaces](https://github.com/codespaces)で見ることができます。
diff --git a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..c2b4268878
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. {% data variables.product.product_name %}の右上で、自分のプロフィール写真をクリックし、続いて**Your codespaces（自分のcode spaces）**をクリックしてください。
+
+  !['自分のcodespaces'メニューオプション](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md
index bb2555adea..83f6535adf 100644
--- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@
 | Composer       | `composer`       | v1, v2                     |    **✓**    |    **✓**    |       |
 | Docker         | `docker`         | v1                         |    **✓**    |    **✓**    |       |
 | Hex            | `mix`            | v1                         |             |    **✓**    |       |
-| elm-package    | `elm`            | v0.18, v0.19               |    **✓**    |    **✓**    |       |
+| elm-package    | `elm`            | v0.19                      |    **✓**    |    **✓**    |       |
 | Gitサブモジュール     | `gitsubmodule`   | N/A (バージョンなし)              |    **✓**    |    **✓**    |       |
 | GitHub Actions | `github-actions` | N/A (バージョンなし)              |    **✓**    |    **✓**    |       |
 | Goモジュール        | `gomod`          | v1                         |    **✓**    |    **✓**    | **✓** |
diff --git a/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md
index 21e42799b8..2a787a99bf 100644
--- a/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@
 
 デフォルトでは、フォークされたリポジトリではワークフローは実行されません。 フォークされたリポジトリの** Actions**タブでGitHub Actionsを有効化しなければなりません。
 
+{% if currentVersion == "free-pro-team@latest"%}
+初めてのコントリビューターがパブリックリポジトリにPull Requestをサブミットした場合、書き込み権限を持つメンテナがそのPull Requestに対するワークフローの実行を承認しなければなりません。 詳しい情報については「[パブリックなフォークからのワークフローの実行の承認](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)」を参照してください。
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} フォークされたリポジトリ内の`GITHUB_TOKEN`の権限は読み取りのみです。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
 
 {% note %}
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-report-download.md
index 53d2dbae87..0ce314198e 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. あるいは、 **Get usage report（利用レポートの取得）**をクリックして、{% data variables.product.prodname_actions %}と{% data variables.product.prodname_registry %}のストレージ利用状況のCSVレポートを、アカウントのプライマリメールアドレスにメールすることもできます。 ![CSVレポートのダウンロード](/assets/images/help/billing/actions-packages-report-download.png)
+1. あるいは、 "Usage this month（今月の利用状況）"の隣の**Get usage report（利用レポートの取得）**をクリックして、{% data variables.product.prodname_actions %}と{% data variables.product.prodname_registry %}のストレージ利用状況のCSVレポートを、アカウントのプライマリメールアドレスにメールすることもできます。 ![CSVレポートのダウンロード](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/change_plan_duration.md b/translations/ja-JP/data/reusables/dotcom_billing/change_plan_duration.md
index d00a600699..b89ed0e567 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. "Billing overview（支払いの概要）"の下で、**Change to yearly billing（年間の支払いの変更）**もしくは**Change to monthly billing（月間の支払いの変更）**をクリックしてください。 ![[Billing overview] の [Change plan] ボタン](/assets/images/help/billing/change-plan-duration-link.png)
+1. "Current monthly bill（現在の月間支払額）"あるいは"Current yearly bill（現在の年間支払額）"の下で、**Switch to yearly billing（年間の支払いへの変更）**もしくは**Switch to monthly billing（月間の支払いへの変更）**をクリックしてください。 ![[Billing overview] の [Change plan] ボタン](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/choose_org_plan.md b/translations/ja-JP/data/reusables/dotcom_billing/choose_org_plan.md
index f75bf13377..afadbab07a 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. {% data variables.product.prodname_free_team %}からアップグレードをしているなら、"Upgrading to（アップグレード先）"の下から製品を選択してください。 ![アップグレードボタン](/assets/images/help/billing/upgrade-to-product.png)
+1. "Compare plans（プランの比較）"の下で、各プランの機能を比較できます。 現在のプランと選択したプランに応じて、**Upgrade to Team（Teamへのアップグレード）**あるいは**Upgrade to Enterprise（Enterpriseへのアップグレード）**をクリックしてください。 ![プランの比較とアップグレード](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/enter-payment-info.md b/translations/ja-JP/data/reusables/dotcom_billing/enter-payment-info.md
index 129fb6d599..7c37568c6e 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. "Billing information（支払い情報）"の下で、クレジットカードもしくはPayPalでの支払いを選択してください。 ![支払い方法の切り替え](/assets/images/help/billing/billing_switch_payments.png)
+1. "Payment method（支払い方法）"の下で、クレジットカード支払いかPayPalでの支払いかを選択してください。 ![支払い方法の切り替え](/assets/images/help/billing/billing_switch_payments.png)
 1. 支払い情報のフォームに入力し、**Submit（サブミット）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/lfs-add-data.md b/translations/ja-JP/data/reusables/dotcom_billing/lfs-add-data.md
index f1e1607399..e63e97d428 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. "{% data variables.large_files.product_name_short %} Data（{% data variables.large_files.product_name_short %}のデータ）"の隣の**Add more data（さらにデータを追加）**をクリックするか、Edit（編集）ドロップダウンを使って**Add more data packs（さらにデータパックを追加**をクリックしてください。 ![さらにデータを追加ボタン](/assets/images/help/billing/data-pack-purchase-more.png)
+1. "{% data variables.large_files.product_name_short %} Data"の隣で、**Add more data（データを追加）**をクリックするか、**Edit（編集）**ドロップダウンを使って**Add more data packs（データパックを追加）**をクリックしてください。 ![さらにデータを追加ボタン](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/ja-JP/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..ff78bb00d1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. ページの上部の"Payment information（支払い情報）"の下で、**Manage spending limit（使用限度の管理）**をクリックしてください。 ![使用限度の管理のリンク](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/next_billing_date.md b/translations/ja-JP/data/reusables/dotcom_billing/next_billing_date.md
index 1eaddc9e0b..9450a676a8 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. "Billing overview（支払いの概要）"の下で、次の支払いの期日をレビューしてください。 ![次の支払日](/assets/images/help/billing/settings_billing_next_payment.png)
+1. ページの上部の"Next payment due（次の支払期限）"の下で、次回の支払期限を確認してください。 ![次の支払日](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/review-pending-changes.md b/translations/ja-JP/data/reusables/dotcom_billing/review-pending-changes.md
index b397e60c43..a1d6c28643 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. "Subscriptions（プラン）"の下で、ペンディングになっている変更をレビューしてください。 ![ペンディングされているプランの変更のリストがある支払い設定のプランセクション](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. "Current plan（現在のプラン）"の下で、保留中の変更をレビューしてください。 ![ペンディングされているプランの変更のリストがある支払い設定のプランセクション](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/update_payment_method.md b/translations/ja-JP/data/reusables/dotcom_billing/update_payment_method.md
index e693c5b4bd..ab805e3043 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. "Billing overview（支払いの概要）"の下で、**Update payment method（支払い方法の更新）**をクリックしてください。 ![支払い方法の更新ボタン](/assets/images/help/billing/update_payment_method.png)
+1. ページの上部の"Payment information（支払い情報）"の下で、**Update payment method（支払い方法の更新）**をクリックしてください。 ![支払い方法の更新ボタン](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/upgrade_org.md b/translations/ja-JP/data/reusables/dotcom_billing/upgrade_org.md
index 3e9df5d2e2..d381271c21 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. {% data variables.product.prodname_free_team %}からアップグレードしているなら、**Upgrade options（アップグレードオプション）**をクリックしてください。 {% data variables.product.prodname_team %}からアップグレードしているなら、**Edit（編集）**ドロップダウンを使い、**Upgrade（アップグレード）**をクリックしてください。 ![アップグレードオプションボタン](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. "Current plan（現在のプラン）"の隣の**Upgrade（アップグレード）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/view-payment-history.md b/translations/ja-JP/data/reusables/dotcom_billing/view-payment-history.md
index 879e7c88fb..5b3fb124e5 100644
--- a/translations/ja-JP/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/ja-JP/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. "Billing overview（支払いの概要）"の下で、** View payment method（支払い方法の表示）**をクリックしてください。 ![支払い履歴の表示リンク](/assets/images/help/billing/view-payment-history-link.png)
+1. ページの上部の"Next payment due（次回の支払期限）"の下で、**View payment history（支払い履歴の表示）**をクリックしてください。 ![支払い履歴の表示リンク](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/add-a-domain.md b/translations/ja-JP/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..120a6bfaeb
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. [**Add a domain**] をクリックします。 ![[Add a domain] ボタン](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/ja-JP/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..f83c6f7d7d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/ja-JP/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..7730810353
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+ドメインを検証することで、Enterprise アカウントが所有する Organization のプロファイルにリストされている Web サイトとメールアドレスが Enterprise によって管理されていることを確認できます。 Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+Enterprise アカウントのドメインの所有権を検証すると、プロファイルにドメインがリストされている各 Organization のプロファイルに「検証済み」のバッジが表示されます。 {% data reusables.organizations.verified-domains-details %}
+
+Organization のオーナーは、検証済みのドメインにある各メンバーのメールアドレスを表示して Organization のメンバーのアイデンティティを確認できます。
+
+Enterprise アカウントのドメインを検証した後、Enterprise アカウントが所有するすべての Organization の検証済みドメインにメール通知を制限できます。 For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/domains-approving.md b/translations/ja-JP/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/domains-removing.md b/translations/ja-JP/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/domains-verifying.md b/translations/ja-JP/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..cffbb65dbd
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+Enterprise アカウントのドメイン検証するには、ドメインホスティングサービスでドメインレコードを変更するためのアクセス権が必要です。
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. DNS 設定が変更されるまで待ちます。これには、最大 72 時間かかる場合があります。 コマンドラインで `dig` コマンドを実行し、`ENTERPRISE-ACCOUNT` を Enterprise アカウントの名前に置き換え、`example.com` を検証するドメインに置き換えると、DNS 設定が変更されたことを確認できます。 新しい TXT レコードがコマンド出力に表示されているはずです。
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. 必要に応じて、Organization のプロフィールに「検証済み」バッジが表示されたら、ドメインホスティングサービスの DNS レコードから TXT エントリを削除します。 ![検証済みバッジ](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..df78c501f7
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+ドメインは、Enterprise アカウントから継承することも、特定の Organization 用に設定することもできます。 For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Enterprise アカウントでメール制限が有効になっている場合、Organization のオーナーは、Enterprise アカウントが所有する Organization のメール制限を無効にすることはできません。 If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..311ff4c22f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. [**Save**] をクリックします。
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/verified-domains-tab.md
index 7e88c5cdb4..85644af45c 100644
--- a/translations/ja-JP/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. "Settings（設定）"の下で、**Verified domains（検証済みドメイン）**をクリックしてください。 !["検証済みドメイン"タブ](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/ja-JP/data/reusables/enterprise_deprecation/deprecation_details.md
index 3efe855fc1..2edf4f0bb2 100644
--- a/translations/ja-JP/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/ja-JP/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1 +1 @@
-重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、<a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">最新バージョンのGitHub Enterpriseにアップグレード</a>してください。 アップグレードに関する支援については、<a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">GitHub Enterprise supportに連絡</a>してください。
+重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、<a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">最新バージョンのGitHub Enterpriseにアップグレード</a>してください。 アップグレードに関する支援については、<a href="https://enterprise.github.com/support">GitHub Enterprise supportに連絡</a>してください。
diff --git a/translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..39d10f08e5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### {% data variables.product.prodname_ghe_server %} 3.0 以降の最小要件について
+
+{% data variables.product.prodname_ghe_server %} 3.0 以降にアップグレードする前に、インスタンスにプロビジョニングしたハードウェアリソースを確認してください。 {% data variables.product.prodname_ghe_server %} 3.0 は、{% data variables.product.prodname_actions %} や {% data variables.product.prodname_registry %} などの新機能を導入しているため、バージョン 2.22 以前よりも多くのリソースが必要となります。 詳しい情報については、[{% data variables.product.prodname_ghe_server %} 3.0 のリリースノート](/enterprise-server@3.0/admin/release-notes)を参照してください。
+
+次の表では、{% data variables.product.prodname_ghe_server %} 3.0 以降の要件の増加を**太字**で示しています。
+
+| ユーザライセンス               |                        vCPUs |                                  メモリ |                         アタッチされたストレージ | ルートストレージ |
+|:---------------------- | ----------------------------:| ------------------------------------:| ------------------------------------:| --------:|
+| トライアル、デモ、あるいは10人の軽量ユーザ |   **4**<br/>_2 から増加_ |   **32 GB**<br/>_16 GB から増加_ | **150 GB**<br/>_100 GB から増加_ |   200 GB |
+| 10-3000                |   **8**<br/>_4 から増加_ |   **48 GB**<br/>_32 GB から増加_ | **300 GB**<br/>_250 GB から増加_ |   200 GB |
+| 3000-5000              |  **12**<br/>_8 から増加_ |                                64 GB |                               500 GB |   200 GB |
+| 5000-8000              | **16**<br/>_12 から増加_ |                                96 GB |                               750 GB |   200 GB |
+| 8000-10000+            | **20**<br/>_16 から増加_ | **160 GB**<br/>_128 GB から増加_ |                              1000 GB |   200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+{% data variables.product.prodname_actions %}のハードウェアの要件に関する詳しい情報については「[{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}を利用しはじめる](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)」を参照してください。
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md
index 07edc3765d..8d3ef52f09 100644
--- a/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/ja-JP/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**警告**: この設定を変更すると、{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}が再起動します。 この変更は、ダウンタイムを最小化するために慎重に時間を調整しなければなりません。
+**警告**: この設定を変更すると、{% data variables.product.prodname_ghe_server %}のユーザが利用するサービスが再起動されます。 ユーザにとってのダウンタイムを最小化するために、この変更の時間は慎重に調整しなければなりません。
 
 {% endwarning %}
diff --git a/translations/ja-JP/data/reusables/gated-features/actions-shared.md b/translations/ja-JP/data/reusables/gated-features/actions-shared.md
index 268c3cab2d..b06d5fdace 100644
--- a/translations/ja-JP/data/reusables/gated-features/actions-shared.md
+++ b/translations/ja-JP/data/reusables/gated-features/actions-shared.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %}は{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_free_team %}のOrganization、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %}、{% data variables.product.prodname_ghe_one %}、{% data variables.product.prodname_ghe_managed %}で利用できます。 {% data variables.product.prodname_actions %}は、レガシーのリポジトリごとのプランを使っているアカウントが所有しているプライベートリポジトリでは利用できません。 
+{% data variables.product.prodname_actions %}は{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_free_team %}のOrganization、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_managed %}で利用できます。 {% data variables.product.prodname_actions %}は、レガシーのリポジトリごとのプランを使っているアカウントが所有しているプライベートリポジトリでは利用できません。 
diff --git a/translations/ja-JP/data/reusables/gated-features/ghas.md b/translations/ja-JP/data/reusables/gated-features/ghas.md
index 88331fd6c7..35e4fe361f 100644
--- a/translations/ja-JP/data/reusables/gated-features/ghas.md
+++ b/translations/ja-JP/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %}ライセンスは{% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}{% endif %}、{% data variables.product.prodname_ghe_server %}上のEnterpriseアカウントで利用できます。 {% data variables.product.prodname_GH_advanced_security %}は、{% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %}及び{% data variables.product.prodname_dotcom_the_website %}上のすべてのパブリックリポジトリ{% endif %}にも含まれています。 詳しい情報については「[GitHubの製品について](/github/getting-started-with-github/githubs-products)」を参照してください。
\ No newline at end of file
+{% data variables.product.prodname_GH_advanced_security %}ライセンスは、{% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}{% endif %}、{% data variables.product.prodname_ghe_server %}上のEnterpriseアカウントで利用できます。{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_GH_advanced_security %}は、{% data variables.product.prodname_dotcom_the_website %}上のすべてのパブリックリポジトリにも含まれます。{% endif %}詳しい情報については「[GitHubの製品について](/github/getting-started-with-github/githubs-products)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/gated-features/github-insights.md b/translations/ja-JP/data/reusables/gated-features/github-insights.md
index 637d0cf102..fb2e2826fb 100644
--- a/translations/ja-JP/data/reusables/gated-features/github-insights.md
+++ b/translations/ja-JP/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %}は{% data variables.product.prodname_ghe_one %}で利用できます。 詳細は「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」を参照してください。
+{% data variables.product.prodname_insights %}は{% data variables.product.prodname_ghe_one %}で利用できます。 詳細は「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/gated-features/packages.md b/translations/ja-JP/data/reusables/gated-features/packages.md
index 6357c38e4a..aac5e16af7 100644
--- a/translations/ja-JP/data/reusables/gated-features/packages.md
+++ b/translations/ja-JP/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_registry %}は{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_free_team %}のOrganization、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %} 2.22、{% data variables.product.prodname_ghe_one %}、{% data variables.product.prodname_ghe_managed %}で利用できます。
+{% data variables.product.prodname_registry %}は{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_free_team %}のOrganization、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %}、{% data variables.product.prodname_ghe_managed %}で利用できます。
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-{% data variables.product.prodname_registry %}は、レガシーのリポジトリごとのプランを使っているアカウントが所有しているプライベートリポジトリでは利用できません。 {% data variables.product.prodname_registry %}は{% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_free_team %}のOrganization、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_one %}で利用できます。 {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_registry %}は、レガシーのリポジトリごとのプランを使っているアカウントが所有しているプライベートリポジトリでは利用できません。 また、レガシーのリポジトリごとのプランを使っているアカウントは、リポジトリごとに課金されるため、{% data variables.product.prodname_container_registry %}にはアクセスできません。 {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/gated-features/secret-scanning.md b/translations/ja-JP/data/reusables/gated-features/secret-scanning.md
index 34915a6f87..b9bf84bf14 100644
--- a/translations/ja-JP/data/reusables/gated-features/secret-scanning.md
+++ b/translations/ja-JP/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %}は{% if currentVersion == "free-pro-team@latest" %}パブリックリポジトリ及び{% data variables.product.prodname_advanced_security %}ライセンスを持つOrganizationが所有するプライベートリポジトリで{% else %}{% data variables.product.prodname_advanced_security %}ライセンスを持っていれば{% endif %}利用できます。 {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %}は、すべてのパブリック及びOrganizationが所有する{% data variables.product.prodname_GH_advanced_security %}が有効化されたプライベートリポジトリで利用できます。
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %}は、Organizationが所有するリポジトリで{% data variables.product.prodname_GH_advanced_security %}が有効化されていれば利用できます。
+{%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_secret_scanning_caps %}は、ベータリリースの間は無料である{% data variables.product.prodname_GH_advanced_security %}の一部として利用できます。
-{% endif %}
\ No newline at end of file
+{%- else %}
+{% data variables.product.prodname_secret_scanning_caps %}は、{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているなら利用できます。{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/forked-write-permission.md b/translations/ja-JP/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..918a2a1d4a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+`permissions`キーを使って、フォークされたリポジトリの読み取り権限の付与や削除ができますが、通常は書き込みアクセス権を付与することはできません。 この動作の例外としては、管理ユーザが{% data variables.product.prodname_actions %}の設定で**Send write tokens to workflows from pull requests（Pull Requestからワークフローに書き込みトークンを送る）**を選択している場合があります。 詳しい情報については「[リポジトリで{% data variables.product.prodname_actions %}を無効化あるいは制限する](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)」を参照してください。
\ No newline at end of file
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
new file mode 100644
index 0000000000..3f1b4fbfed
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+利用できるスコープとアクセスの値は以下のとおりです。
+
+```yaml
+権限:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+これらのスコープのいずれかに対してアクセスを指定した場合、指定されなかったスコープは`none`に設定されます。
+
+利用可能なすべてのスコープに対する読み取りあるいは書き込みアクセス権を定義するためには、以下の構文が使えます。
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/github-token-permissions.md b/translations/ja-JP/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..0f118a3edf
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+ワークフロー内のジョブが開始されるたびに、`GITHUB_TOKEN`はそのリポジトリのアクセストークンに設定されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}`contents`スコープに対する読み取りアクセス権と、`packages`スコープに対する書き込み権を付与するために、ワークフローファイル中でこのアクセストークンに権限を設定しなければなりません。 {% else %}これは、ワークフローが実行されるリポジトリ内でパッケージに対する読み取り及び書き込み権限を持っています。 {% endif %}詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 4a83160cc0..014c74286e 100644
--- a/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-{% data variables.product.prodname_registry %}に公開するために`mvn --batch-mode deploy`コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。
+{% data variables.product.prodname_registry %}に公開するために`mvn --batch-mode deploy`コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}`permissions`キーは、`GITHUB_TOKEN`に付与されたアクセス権を指定します。{% endif %}
diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index 1657606280..34033a5146 100644
--- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **Warning**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
diff --git a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md b/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
index 1e750713b8..b717e55615 100644
--- a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**警告**: Ubuntu 16.04は非推奨です。 いずれかのワークフローがUbuntu 16.04を使っているなら、Ubuntu 20.04もしくは18.04に移行してください。 詳しい情報については[ブログポスト](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021)を参照してください。
+
+{% endwarning %}
+
 | 仮想環境                 | YAMLのワークフローラベル                     |
 | -------------------- | ---------------------------------- |
 | Windows Server 2019  | `windows-latest`もしくは`windows-2019` |
+| Windows Server 2016  | `windows-2016`                     |
 | Ubuntu 20.04         | `ubuntu-latest`または`ubuntu-20.04`   |
 | Ubuntu 18.04         | `ubuntu-18.04`                     |
-| Ubuntu 16.04         | `ubuntu-16.04`                     |
 | macOS Big Sur 11.0   | `macos-11.0`                       |
 | macOS Catalina 10.15 | `macos-latest`もしくは`macos-10.15`    |
diff --git a/translations/ja-JP/data/reusables/github-actions/workflow-permissions-intro.md b/translations/ja-JP/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..4e3d423448
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+`GITHUB_TOKEN`に付与されるデフォルトの権限を設定できます。 `GITHUB_TOKEN`に関する詳しい情報については「[ワークフロー中の認証](/actions/reference/authentication-in-a-workflow)」を参照してください。 デフォルトとして制限された権限セットか、より幅広く許可をする設定を選択できます。 
diff --git a/translations/ja-JP/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/ja-JP/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..4b357b1f48
--- /dev/null
+++ b/translations/ja-JP/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+リポジトリに対して書き込みアクセス権を持つ人は、ワークフローファイル中の`permissions`キーを編集することによって、`GITHUB_TOKEN`に付与される権限を変更したり、必要に応じてアクセス権を追加したり削除したりできます。 詳しい情報については[`権限`](/actions/reference/workflow-syntax-for-github-actions#permissions)を参照してください。 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/verification-status-check.md b/translations/ja-JP/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..75b50fe080
--- /dev/null
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+{% data variables.product.product_name %}上の署名されたコミットあるいはタグの検証ステータスをチェックして、コミットの署名が検証されない理由を見ることができます。 詳細は「[コミットおよびタグの署名の検証のステータスをチェックする](/articles/checking-your-commit-and-tag-signature-verification-status)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..ace99e2a30
--- /dev/null
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**ノート:** Vigilantモードは現在ベータであり、変更されることがあります。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..1ab04ed556
--- /dev/null
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| ステータス                       | 説明                                                                                                                                               |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Verified**                | コミットは署名され、署名の検証も成功しており、コミッターは警戒モードを有効化した唯一の作者。                                                                                                   |
+| **Partially&nbsp;verified** | コミットは署名され、署名の検証も成功しているが、コミットには a) コミッターではなく b) 警戒モードを有効化した 作者がいる。 この場合、コミットの署名は作者の合意を保証しないので、コミットは部分的にのみ検証されています。                                |
+| **Unverified**              | 以下のいずれかが真: <br>- コミットは署名されているが、署名を検証できなかった。<br>- コミットが署名されておらず、コミッターは警戒モードを有効化した。<br>- コミットは署名されておらず、作者が警戒モードを有効化した。<br> |
diff --git a/translations/ja-JP/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/ja-JP/data/reusables/marketplace/cancel-app-billing-settings.md
index 5f32f73039..fa71a0b363 100644
--- a/translations/ja-JP/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/ja-JP/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. ** Edit（編集）**ドロップダウンを使い、**Cancel plan（プランのキャンセル）**をクリックしてください。 ![個人アカウントの支払い設定中のマーケットプレイスの購入セクションのキャンセルリンク](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. キャンセルしたいアプリケーションの隣の** Edit（編集）**ドロップダウンを使い、**Cancel plan（プランのキャンセル）**をクリックしてください。 ![個人アカウントの支払い設定中のマーケットプレイスの購入セクションのキャンセルリンク](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ja-JP/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/ja-JP/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index 7756f1945d..c753a75e1a 100644
--- a/translations/ja-JP/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/ja-JP/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. "Subscriptions（プラン）"の下で、キャンセルしたい無料トライアルの隣のEdit（編集）ドロップダウンを使って**Cancel plan（プランのキャンセル**をクリックしてください。
+1. キャンセルしたい無料トライアルの隣の** Edit（編集）**ドロップダウンを使い、**Cancel plan（プランのキャンセル）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/ja-JP/data/reusables/marketplace/downgrade-app-billing-settings.md
index c5804c1470..4086f0e1f2 100644
--- a/translations/ja-JP/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/ja-JP/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. "Your subscriptions（あなたのプラン）"の下で、ダウングレードしたいアプリケーションの隣でEditドロップダウンメニューを使い、**Change plan（プランの変更）**もしくは**Cancel plan（プランのキャンセル）**をクリックしてください。 ![個人アカウントの支払い設置中のMarketplaceの購入セクション内にあるEditリンク](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. ダウングレードしたいアプリケーションの隣の**Edit（編集）**ドロップダウンを使い、**Change plan（プランを変更）**もしくは**Cancel plan（プランをキャンセル）**をクリックしてください。 ![個人アカウントの支払い設置中のMarketplaceの購入セクション内にあるEditリンク](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ja-JP/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/ja-JP/data/reusables/marketplace/upgrade-app-billing-settings.md
index c74dd4415c..c5f7886ef3 100644
--- a/translations/ja-JP/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/ja-JP/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. ** Edit（編集）**ドロップダウンを使い、**Change plan（プランの変更）**をクリックしてください。 ![個人アカウントの支払い設定中のマーケットプレイスの購入セクションの編集ドロップダウンメニュー](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. アップグレードしたいアプリケーションの隣の** Edit（編集）**ドロップダウンを使い、**Change plan（プランの変更）**をクリックしてください。 ![個人アカウントの支払い設定中のマーケットプレイスの購入セクションの編集ドロップダウンメニュー](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..79275db7e2
--- /dev/null
+++ b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}Issue、Pull Request、リリース、セキュリティアラート、ディスカッション{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}Issue、Pull Request、リリース、ディスカッション{% endif %}
diff --git a/translations/ja-JP/data/reusables/notifications/email-restrictions-verification.md b/translations/ja-JP/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..6092517b67
--- /dev/null
+++ b/translations/ja-JP/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index 4d466593c6..0110f910c6 100644
--- a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-Watchしているリポジトリ上の{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}に関する通知の配信方法と、通知が送信される頻度を選択できます。
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+Watchしているか、セキュリティアラートをサブスクライブしているリポジトリ上で
+{% data variables.product.prodname_dependabot_alerts %}に関する通知の配信方法と頻度を選択できます。
+{% else %}
+Watchしているリポジトリ上の
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}に関する通知の配信方法を、通知が送信される頻度と共に選択できます。
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/add-a-domain.md b/translations/ja-JP/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..6de91e1a56
--- /dev/null
+++ b/translations/ja-JP/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. [**Add a domain**] をクリックします。 ![[Add a domain] ボタン](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/ja-JP/data/reusables/organizations/billing_plans.md b/translations/ja-JP/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..04a951b633
--- /dev/null
+++ b/translations/ja-JP/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. OrganizationのSettings（設定）サイドバーで、**Billing & plans（支払いとプラン）**をクリックしてください。 ![支払い設定](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/ja-JP/data/reusables/organizations/continue-verifying-domain.md b/translations/ja-JP/data/reusables/organizations/continue-verifying-domain.md
index 85456870d7..b096d47381 100644
--- a/translations/ja-JP/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/ja-JP/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. 検証待ちのドメインの右にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、[**Continue verifying（検証を続ける）**] をクリックします。 ![ドメインの検証を続行するボタン](/assets/images/help/organizations/continue-verifying-domain.png)
-10. [**Verify domain（ドメインの検証）**] をクリックします。 ![ドメイン検証ボタン](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. [**Verify**] をクリックします。 ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/organizations/domains-approve-domain.md b/translations/ja-JP/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/ja-JP/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/ja-JP/data/reusables/organizations/domains-approve-it-instead.md b/translations/ja-JP/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/ja-JP/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/ja-JP/data/reusables/organizations/verified-domains.md b/translations/ja-JP/data/reusables/organizations/verified-domains.md
index 630084acfe..9714304429 100644
--- a/translations/ja-JP/data/reusables/organizations/verified-domains.md
+++ b/translations/ja-JP/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. 左のサイドバーで、**Verified domains（検証済みドメイン）**をクリックしてください。 ![検証済みドメインボタン](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/ja-JP/data/reusables/package_registry/about-packaging-and-actions.md b/translations/ja-JP/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..5e76372ab6
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,30 @@
+### 継続的インテグレーションワークフロー内でのパッケージング
+
+パッケージングのステップは、継続的インテグレーションあるいは継続的デリバリのワークフローの一般的な部分です。 継続的インテグレーションワークフローの終わりにパッケージを作成すれば、Pull Requestに対するコードレビューの間に役立つことがあります。
+
+コードをビルドしてテストした後、パッケージングのステップで実行可能な、あるいはデプロイ可能な成果物を生成できます。 ビルドしているアプリケーションの種類によって、このパッケージは手動でのテストのためにローカルにダウンロードしたり、ユーザーがダウンロードできるようにしたり、ステージングあるいはプロダクションの環境にデプロイしたりできます。
+
+たとえば、Javaのプロジェクトのための継続的インテグレーションのワークフローは、`mvn package`を実行してJARファイルを生成するかもしれません。 あるいは、Node.jsアプリケーションのためのCIワークフローは、Dockerコンテナを作成するかもしれません。
+
+そうすれば、Pull Requestをレビューする際には、ワークフローの実行を見て生成された成果物をダウンロードできるでしょう。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+こうすれば、Pull Request中のコードを自分のマシン上で実行できるので、Pull Requestのデバッグやテストに役立ちます。
+
+### パッケージを公開するためのワークフロー
+
+継続的インテグレーションのワークフロー中で、テストのためにパッケージ化された成果物をアップロードすることに加えて、プロジェクトをビルドして、パッケージをパッケージレジストリに公開するワークフローを作成できます。
+
+* **{% data variables.product.prodname_registry %} へのパッケージの公開**
+  {% data variables.product.prodname_registry %} は、多くの種類のパッケージのパッケージホスティングサービスとして機能します。 パッケージを{% data variables.product.prodname_dotcom %}のすべてと共有することも、パッケージをプライベートにしてコラボレータやOrganizationと共有することもできます。 詳しい情報については「[GitHub Packagesの紹介](/packages/learn-github-packages/introduction-to-github-packages)」を参照してください。
+
+  デフォルトブランチへのプッシュごとに、パッケージを {% data variables.product.prodname_registry %} に公開することをお勧めします。 そうすれば、プロジェクトの開発者は常にデフォルトのブランチからの最新のビルドを{% data variables.product.prodname_registry %}からインストールして実行及びテストできるようになります。
+
+* **パッケージレジストリへのパッケージの公開** 多くのプロジェクトで、新しいバージョンのプロジェクトがリリースされたときにパッケージレジストリへの公開が行われます。 たとえば、JARファイルを生成するプロジェクトは、新しいリリースをMaven Centralリポジトリにアップロードするかもしれません。 あるいは、.NETのプロジェクトはnugetのパッケージを生成し、NuGet Galleryへアップロードするかもしれません。
+
+  これは、リリースが作成される度にパッケージをパッケージレジストリに公開するワークフローを作成すれば、自動化できます。 詳しい情報については「[リリースの作成](/github/administering-a-repository/creating-releases)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/ja-JP/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..7579483b50
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %}ワークフローで使われる`GITHUB_TOKEN`に関する詳しい情報については「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md b/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md
index e704b5f3f9..a3cfe368bc 100644
--- a/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md
+++ b/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md
@@ -1,14 +1,7 @@
-{{ site.data.variables.product.prodname_registry }}でパッケージを公開、インストール、削除するにはアクセストークンが必要です。 {% data variables.product.prodname_registry %}に直接、あるいは{% data variables.product.prodname_dotcom %} APIでユーザ名で認証を受けるのに、個人のアクセストークンが利用できます。 個人トークンを作成する際には、必要に応じて様々なスコープをトークンに割り当てできます。
+{% data variables.product.prodname_registry %}でパッケージを公開、インストール、削除するにはアクセストークンが必要です。
 
-{% if currentVersion == "free-pro-team@latest" %}
-認証を
-{% data variables.product.prodname_actions %}のワークフローで行うには:
-- パッケージレジストリの場合(`PACKAGE-REGISTRY.pkg.github.com`)は、`GITHUB_TOKEN`を利用できます。
-- コンテナレジストリ（`ghcr.io/OWNER/IMAGE-NAME`）の場合は、`GITHUB_TOKEN`もしくは個人アクセストークンを利用できます。 `GITHUB_TOKEN`を利用し、リポジトリに不要なアクセスをしないようにすることを強くおすすめします。
+{% data variables.product.prodname_registry %}、あるいは{% data variables.product.prodname_dotcom %} APIで認証を受けるのに、個人のアクセストークン（PAT）が利用できます。 個人トークンを作成する際には、必要に応じて様々なスコープをトークンに割り当てできます。 PATに関するパッケージ関連のスコープについての詳しい情報は、「[GitHub Packagesの権限について](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)」を参照してください。
 
-{% data variables.product.prodname_actions %}ワークフローで使われる`GITHUB_TOKEN`に関する情報については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」及び「[ワークフロー内での認証](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
-
-{% else %}
-認証を
-{% data variables.product.prodname_actions %}ワークフローを使って{% data variables.product.prodname_registry %}に対して行うには、`GITHUB_TOKEN`を使わなければなりません。
-{% endif %}
+{% data variables.product.prodname_actions %}ワークフロー内で{% data variables.product.prodname_registry %}レジストリに認証を受けるには、以下の方法が使えます。
+- `GITHUB_TOKEN`を使って、ワークフローリポジトリに関連づけられたパッケージを公開。
+- PATで他のプライベートリポジトリ（これには`GITHUB_TOKEN`がアクセスできない）に関連づけられたパッケージをインストール。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index d05ee36620..7981f11f4a 100644
--- a/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. コンテナタイプにあったCLIを利用して、
-`ghcr.io`にある{% data variables.product.prodname_github_container_registry %}サービスにサインインしてください。
+`ghcr.io`にある{% data variables.product.prodname_container_registry %}サービスにサインインしてください。
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index 991f1d2931..ca3dc3f646 100644
--- a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -2,9 +2,9 @@
 
 PATはアカウントに対する広汎なアクセスを許可できます。 {% data variables.product.prodname_container_registry %}での認証のためのPATを作成する際には、必要な`read:packages`、`write:packages`、`delete:packages`スコープだけを選択すべきです。
 
-{% data variables.product.prodname_actions %}ワークフロー内で{% data variables.product.prodname_github_container_registry %}の認証を受けるには、最善のセキュリティと体験のために`GITHUB_TOKEN`を使ってください。
+{% data variables.product.prodname_actions %}ワークフロー内で{% data variables.product.prodname_container_registry %}の認証を受けるには、最善のセキュリティと体験のために`GITHUB_TOKEN`を使ってください。
 
-個人アクセストークンで`ghcr.io`の認証を受けるワークフローの更新に関するガイダンスとしては、「[`ghcr.io`にアクセスするワークフローのアップグレード](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)」を参照してください。
+個人アクセストークンで`ghcr.io`の認証を受けるワークフローの更新に関するガイダンスとしては、「[`ghcr.io`にアクセスするワークフローのアップグレード](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)」を参照してください。
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md b/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md
index a4ea07d788..9119bd1ba7 100644
--- a/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 ベータ期間中は、ストレージおよび帯域幅の制限はありません。 {% data variables.product.prodname_github_container_registry %}を使用するには、機能プレビューを有効化しなければなりません。 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/guides/about-github-container-registry)」及び「[改善されたコンテナサポートの有効化](/packages/guides/enabling-improved-container-support)」を参照してください。
+**注釈:** {% data variables.product.prodname_container_registry %} は現在パブリックベータであり、変更されることがあります。 ベータ期間中は、ストレージおよび帯域幅の制限はありません。 {% data variables.product.prodname_container_registry %}を使用するには、機能プレビューを有効化しなければなりません。 詳しい情報については「[{% data variables.product.prodname_registry %}について](/packages/learn-github-packages/introduction-to-github-packages)」及び「[{% data variables.product.prodname_container_registry %}での改善されたコンテナサポートの有効化](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)」を参照してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/package_registry/docker-vs-container-registry.md b/translations/ja-JP/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..e01b1c4b2d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**Dockerレジストリと{% data variables.product.prodname_container_registry %}との比較:**
+- {% data variables.product.prodname_container_registry %}(`https://ghcr.io`)は、コンテナに対して改善されたパフォーマンスを提供し、将来的にはDockerレジストリを置き換えます。
+- Dockerイメージとワークフローは、Dockerレジストリ(`docker.pkg.github.com`)から{% data variables.product.prodname_container_registry %}(`https://ghcr.io`)へ、詳細な権限、コンテナストレージの最適化などのために移行できます。 詳しい情報については「[Dockerレジストリから{% data variables.product.prodname_container_registry %}への移行](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)」を参照してください。
+
+{% endnote %}
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md
index a1238dcc90..2eca205c0c 100644
--- a/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**ノート:**{% data variables.product.prodname_registry %} Dockerレジストリは、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}将来の{% data variables.product.product_name %}リリースで改善されたコンテナサポートを提供します。{% elsif currentVersion == "free-pro-team@latest" %}改善されたコンテナサポートを提供しています。 詳しい情報については「[GitHub Container Registryについて](/packages/guides/about-github-container-registry)」を参照してください。 既存のDockerイメージと、それらを使うワークフローの移行方法を学ぶには、「[Dockerイメージのための{% data variables.product.prodname_github_container_registry %}への移行](/packages/guides/migrating-to-github-container-registry-for-docker-images)」及び「[{% data variables.product.prodname_registry %}のためのコンテナガイド](/packages/guides/container-guides-for-github-packages)」を参照してください。{% endif %}
+**ノート:** {% data variables.product.prodname_registry %} Dockerレジストリは{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}将来の{% data variables.product.product_name %}リリースで{% data variables.product.prodname_container_registry %}とともに置き換えられます。これは改善されたコンテナサポートを提供します。{% elsif currentVersion == "free-pro-team@latest" %}、改善されたコンテナサポートを提供する{% data variables.product.prodname_container_registry %}によって置き換えられます。 {% endif %}{% if currentVersion == "free-pro-team@latest" %}既存のDockerイメージと、それらを使うワークフローの移行方法を学ぶには、「[Dockerレジストリから{% data variables.product.prodname_container_registry %}への移行](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)」を参照してください。 {% endif %}
 
 {% endwarning %}
diff --git a/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md
index 536ae7705c..fc2cf9195a 100644
--- a/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**ノート:** {% data variables.product.prodname_github_container_registry %}を使う前に、アカウントでこの機能を有効化しなければなりません。 詳しい情報については、「[改善されたコンテナサポートを有効化する](/packages/guides/enabling-improved-container-support)」を参照してください。
+**ノート:** {% data variables.product.prodname_container_registry %}を使う前に、アカウントでこの機能を有効化しなければなりません。 詳しい情報については「[{% data variables.product.prodname_container_registry %}での改善されたコンテナサポートの有効化](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)」を参照してください。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ja-JP/data/reusables/package_registry/github-token-security-over-pat.md b/translations/ja-JP/data/reusables/package_registry/github-token-security-over-pat.md
index 06fe65eb68..24e95ccecd 100644
--- a/translations/ja-JP/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/ja-JP/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_github_container_registry %}は、ワークフロー内での容易でセキュアな認証のために`GITHUB_TOKEN`をサポートするようになりました。 ワークフローが`ghcr.io`での認証のために個人アクセストークン（PAT）を使っているなら、`GITHUB_TOKEN`を使うようにワークフローを更新することを強くおすすめします。
+{% data variables.product.prodname_container_registry %}は、ワークフロー内での容易でセキュアな認証のために`GITHUB_TOKEN`をサポートするようになりました。 ワークフローが`ghcr.io`での認証のために個人アクセストークン（PAT）を使っているなら、`GITHUB_TOKEN`を使うようにワークフローを更新することを強くおすすめします。
 
-`GITHUB_TOKEN`に関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」及び「[ワークフロー内での認証](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
\ No newline at end of file
+`GITHUB_TOKEN`に関する詳しい情報については「[ワークフロー中の認証](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/ja-JP/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..e8bdd44a29
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+リポジトリをスコープとするパッケージは、そのパッケージを所有するリポジトリから権限と可視性を継承します。 以下のレジストリは、この種の権限を使用します。
+- Dockerレジストリ(`docker.pkg.github.com`)
+- npmレジストリ
+- RubyGemsレジストリ
+- Apache Mavenレジストリ
+- NuGetレジストリ
+
+{% if currentVersion == "free-pro-team@latest" %}
+Containerレジストリ(`ghcr.io`)は、個人ユーザもしくはOrganizationアカウントが所有する各パッケージごとにカスタマイズできる、詳細な権限及び可視性の設定を提供します。
+{% endif %}
+
+詳しい情報については「[GitHub Packagesの権限について](/packages/learn-github-packages/about-permissions-for-github-packages)」{% if currentVersion == "free-pro-team@latest" %}あるいは「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」{% endif %}を参照してください。
diff --git a/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..f46046b396
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+コンテナイメージへの管理権限を持っているなら、そのコンテナイメージへのアクセス権限をプライベートもしくはパブリックに設定できます。 パブリックイメージは匿名でアクセスでき、認証や CLI 経由でサインインすることなくプルできます。
+
+あなたが管理者であれば、Organization レベルおよびリポジトリレベルに設定した権限とは別に、コンテナイメージに対してアクセス権限を付与することもできます。
+
+ユーザアカウントが所有し公開しているコンテナイメージには、任意のユーザにアクセスロールを付与できます。 Organization が所有し公開しているコンテナイメージには、Organization 内の任意の Team にアクセスロールを付与できます。
+
+| 権限   | アクセス権の内容                                                                                             |
+| ---- | ---------------------------------------------------------------------------------------------------- |
+| 読み取り | パッケージをダウンロードできます。 <br>メタデータの読み取りができます。                                                         |
+| 書き込み | このパッケージをアップロードおよびダウンロードできます。 <br>パッケージのメタデータの読み取りおよび書き込みができます。                                 |
+| 管理   | このパッケージのアップロード、ダウンロード、削除、管理ができます。 <br>パッケージのメタデータの読み取りおよび書き込みができます。 <br>パッケージに権限を付与できます。 |
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/pages/sidebar-pages.md b/translations/ja-JP/data/reusables/pages/sidebar-pages.md
index 71a074df8c..b8fcd5da70 100644
--- a/translations/ja-JP/data/reusables/pages/sidebar-pages.md
+++ b/translations/ja-JP/data/reusables/pages/sidebar-pages.md
@@ -1,3 +1,3 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
-1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png)
+1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![左のサイドバーのPageタブ](/assets/images/help/pages/pages-tab.png)
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/profile/access_org.md b/translations/ja-JP/data/reusables/profile/access_org.md
index 5c9442e335..c84a156224 100644
--- a/translations/ja-JP/data/reusables/profile/access_org.md
+++ b/translations/ja-JP/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. プロフィールページの左側で、"Organizations"の下であなたのOrganizationのアイコンをクリックしてください。 ![organizationのアイコン](/assets/images/help/profile/profile_orgs_box.png)
+1. {% data variables.product.prodname_dotcom %}の右上で、プロフィール写真をクリックし、続いて**Your organizations（あなたのOrganization）**をクリックしてください。 ![プロフィールメニューのあなたのOrganization](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/profile/org_settings.md b/translations/ja-JP/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..26fb28ee5c
--- /dev/null
+++ b/translations/ja-JP/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. Organizationの隣の**Settings（設定）**をクリックしてください。 ![設定ボタン](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md b/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md
index c5830b3d11..4a4d516b2d 100644
--- a/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. 左のサイドバーのユーザのプロフィール写真の下にある [{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}] をクリックしてから、[**Block or report user（ユーザをブロックもしくは報告）**] をクリックします。 ![ユーザのブロックもしくはレポートのリンク](/assets/images/help/profile/profile-block-or-report-button.png)
+1. 左サイドバーで、ユーザプロフィール画像の下にある**Block or report（ブロックもしくはレポート）**をクリックします。 ![ブロックもしくはレポートのリンク](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md
index 0abccd4a1f..60a351db59 100644
--- a/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -5,7 +5,7 @@
 ```yaml
 on:
   schedule:
-    # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    # *はYAMLにおける特殊文字なので、この文字列はクオートしなければならない
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
index 95c29899e8..99f7aa9548 100644
--- a/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
+++ b/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
@@ -6,6 +6,6 @@
 - [LDAP Syncが有効化されている](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync)場合、リポジトリから個人を削除すると、その人はアクセス権を失いますが、その人のフォークは削除されません。 元々のOrganizationのリポジトリへのアクセスできるように3ヶ月以内にその人がTeamに追加されたなら、次回の同期の際にフォークへのアクセスは自動的に回復されます。{% endif %}
 - リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。
 
-- プライベート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}もしくはインターナル{% endif %}リポジトリに対する管理権限を持っている人は、そのリポジトリのフォークを禁止でき、OrganizationのオーナーはOrganization内の任意のプライベート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}もしくはインターナル{% endif %}リポジトリのフォークを禁止できます。 For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+- プライベート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}もしくはインターナル{% endif %}リポジトリに対する管理権限を持っている人は、そのリポジトリのフォークを禁止でき、OrganizationのオーナーはOrganization内の任意のプライベート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}もしくはインターナル{% endif %}リポジトリのフォークを禁止できます。 詳しい情報については「[Organizationのためのフォークのポリシーの管理](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」及び「[リポジトリのフォークのポリシーの管理](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)」を参照してください。
 
 {% endwarning %}
diff --git a/translations/ja-JP/data/reusables/repositories/request-changes-tips.md b/translations/ja-JP/data/reusables/repositories/request-changes-tips.md
index 377bbc0b0d..c4b7820140 100644
--- a/translations/ja-JP/data/reusables/repositories/request-changes-tips.md
+++ b/translations/ja-JP/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - リポジトリのオーナーと管理者は、プルリクエストが承認レビューを受けていなかったり、あるいは変更をリクエストしたレビュー担当者がOrganizationを離れていたりアクセスできなくなっている場合でも、プルリクエストをマージできます。
 - 必須レビューと古いレビューの棄却がどちらも有効化されており、承認済みのプルリクエストのブランチにコードを変更するコミットがプッシュされた場合、その承認は却下されます。 そのプルリクエストは、再度レビューされ承認されるまではマージできません。
 - 同じコミットを指す複数のオープンされたプルリクエストがあり、それぞれがheadブランチを持つ場合、いずれかがペンディングあるいは拒否されたレビューを持っているなら、それらはマージできません。
+- Pull Requestの作者は、自分自身のPull Requestを承認することはできません。
 
 {% endtip %}
diff --git a/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md
index 6197583150..ab50bd8bfa 100644
--- a/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md
+++ b/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md
@@ -1,5 +1,5 @@
-まだプロジェクト中のセキュリティ脆弱性に対するCVE識別番号を持っていない場合は、{% data variables.product.prodname_dotcom %}にCVE識別番号をリクエストできます。 {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE,  {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you publish the security advisory.
+まだプロジェクト中のセキュリティ脆弱性に対するCVE識別番号を持っていない場合は、{% data variables.product.prodname_dotcom %}にCVE識別番号をリクエストできます。 {% data variables.product.prodname_dotcom %}は通常、リクエストを72時間以内にレビューします。 CVE識別番号をリクエストしても、セキュリティアドバイザリはパブリックにはなりません。 セキュリティアドバイザリがCVEの対象となるなら、{% data variables.product.prodname_dotcom %}はそのアドバイザリのためにCVE識別番号を予約します。 そして、あなたがセキュリティアドバイザリを公開した後に、CVEの詳細を私たちがCVEの詳細を公開します。
 
-If you already have a CVE you want to use, for example, if you use a CNA other than {% data variables.product.prodname_dotcom %}, add it to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time.
+使いたいCVEをすでに持っている場合、たとえば{% data variables.product.prodname_dotcom %}ではなくCNAを使う場合には、それをセキュリティアドバイザリのフォームに入力してください。 これはたとえば、公開時に送信することを計画している他の通信先と、アドバイザリが一貫しているようにしたい場合に生じるかもしれません。
 
-If an advisory form doesn't have a CVE, we will request a CVE for you when you publish the advisory.
\ No newline at end of file
+アドバイザリのフォームにCVEがない場合は、アドバイザリをあなたが公開する際に私たちがあなたに代わってCVEをリクエストします。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md b/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md
index 372512e850..6de4b625bb 100644
--- a/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md
+++ b/translations/ja-JP/data/reusables/repositories/return-to-source-diff.md
@@ -1,5 +1,5 @@
-1. You may also want to review the source diff, because there could be changes to the manifest or lock file that don't change dependencies, or there could be dependencies that {% data variables.product.prodname_dotcom %} can't parse and which, as a result, don't appear in the dependency review.
+1. 依存関係を変化させないような変更がマニフェストあるいはロックファイルに行われているかもしれず、あるいは{% data variables.product.prodname_dotcom %}がパースできず、その結果として依存関係レビューに現れてこない依存関係があるかもしれないので、ソースdiffをレビューしたいこともあるでしょう。
 
-   To return to the source diff view, click the **{% octicon "code" aria-label="The source diff icon" %}** button.
+   ソースdiffのビューに戻るには、**{% octicon "code" aria-label="The source diff icon" %}**ボタンをクリックしてください。
 
    ![ソース diff ボタン](/assets/images/help/pull_requests/dependency-review-source-diff.png)
diff --git a/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md
index cfe413d8a0..1978118ae3 100644
--- a/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md
+++ b/translations/ja-JP/data/reusables/repositories/review-policy-overlapping-commits.md
@@ -1 +1 @@
-Even after all required reviewers have approved a pull request, collaborators cannot merge the pull request if there are other open pull requests that have a head branch pointing to the same commit with pending or rejected reviews. Someone with write permissions must approve or dismiss the blocking review on the other pull requests first.
+すべての必須のレビュー担当者がPull Requestを承認した後でも、同じコミットを指すヘッドブランチを持つ、保留中もしくは拒否されたレビューを持つオープンなPull Requestが他にある場合、コラボレータはそのPull Requestをマージできません。 まず、他のPull Request上のブロックしているレビューを、書き込み権限を持つ誰かが承認もしくは却下しなければなりません。
diff --git a/translations/ja-JP/data/reusables/repositories/security-advisory-edit-cwe-cve.md b/translations/ja-JP/data/reusables/repositories/security-advisory-edit-cwe-cve.md
index 813ebb08ee..8a1361dffb 100644
--- a/translations/ja-JP/data/reusables/repositories/security-advisory-edit-cwe-cve.md
+++ b/translations/ja-JP/data/reusables/repositories/security-advisory-edit-cwe-cve.md
@@ -1,2 +1,2 @@
-1. Add common weakness enumerators (CWEs) for the kinds of security weaknesses that this security advisory addresses. For a full list of CWEs, see the "[Common Weakness Enumeration](https://cwe.mitre.org/index.html)" from MITRE.
-1. If you have an existing CVE identifier, select "I have an existing CVE identifier" and type the CVE identifier in the text box. Otherwise, you can request a CVE from {% data variables.product.prodname_dotcom %} later. 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)」を参照してください。
+1. このセキュリティアドバイザリが指摘しているセキュリティ脆弱性の種類に対する共通脆弱性タイプ一覧（CWEs）を追加してください。 CWEの完全なリストについては、MITREの「[共通脆弱性タイプ一覧](https://cwe.mitre.org/index.html)」を参照してください。
+1. 既存のCVE識別子を持っているなら、"I have an existing CVE identifier（既存のCVE識別子を持っています） "を選択し、テキストボックスにCVE識別子を入力してください。 そうでない場合は、後で{% data variables.product.prodname_dotcom %}からCVEをリクエストできます。 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/repositories/security-advisory-edit-details.md b/translations/ja-JP/data/reusables/repositories/security-advisory-edit-details.md
index bcb329bed7..941b5bc2d0 100644
--- a/translations/ja-JP/data/reusables/repositories/security-advisory-edit-details.md
+++ b/translations/ja-JP/data/reusables/repositories/security-advisory-edit-details.md
@@ -1 +1 @@
-1. Edit the product and versions affected by the security vulnerability that this security advisory addresses. ![セキュリティアドバイザリのメタデータ](/assets/images/help/security/security-advisory-affected-product.png)
+1. このセキュリティアドバイザリが対応するセキュリティ脆弱性に影響される製品とバージョンを編集してください。 ![セキュリティアドバイザリのメタデータ](/assets/images/help/security/security-advisory-affected-product.png)
diff --git a/translations/ja-JP/data/reusables/repositories/security-advisory-edit-severity.md b/translations/ja-JP/data/reusables/repositories/security-advisory-edit-severity.md
index 0b9f45958e..73bb73ad2f 100644
--- a/translations/ja-JP/data/reusables/repositories/security-advisory-edit-severity.md
+++ b/translations/ja-JP/data/reusables/repositories/security-advisory-edit-severity.md
@@ -1 +1 @@
-1. Select the severity of the security vulnerability. To assign a CVSS score, select "Assess severity using CVSS" and click the appropriate values in the calculator. {% data variables.product.product_name %} calculates the score according to the "[Common Vulnerability Scoring System Calculator](https://www.first.org/cvss/calculator)." ![Drop-down menu to select the severity](/assets/images/help/security/security-advisory-severity.png)
+1. セキュリティ脆弱性の重要度を選択してください。 CVSSスコアを割り当てるには、"Assess severity using CVSS（CVSSを使って重要度を評価）"を選択し、適切な値を計算機でクリックしてください。 {% data variables.product.product_name %}は "[共通脆弱性スコアリングシステム計算機](https://www.first.org/cvss/calculator)"に従ってスコアを計算します。 ![重要度を選択するためのドロップダウンメニュー](/assets/images/help/security/security-advisory-severity.png)
diff --git a/translations/ja-JP/data/reusables/repositories/security-alert-delivery-options.md b/translations/ja-JP/data/reusables/repositories/security-alert-delivery-options.md
index dc371f34d4..862f70aca9 100644
--- a/translations/ja-JP/data/reusables/repositories/security-alert-delivery-options.md
+++ b/translations/ja-JP/data/reusables/repositories/security-alert-delivery-options.md
@@ -1,4 +1,4 @@
 {% if currentVersion != "github-ae@latest" %}
-If your repository has a supported dependency manifest
-{% if currentVersion == "free-pro-team@latest" %} (and if you've set up the dependency graph if it's a private repository){% endif %}, whenever {% data variables.product.product_name %} detects a vulnerable dependency in your repository, you will receive a weekly digest email. セキュリティアラートは、Web通知、個別のメール通知、日次のメールダイジェスト、{% data variables.product.product_name %}インターフェース上のアラートとして設定することもできます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
+リポジトリにサポートされている依存関係マニフェストがあり
+{% if currentVersion == "free-pro-team@latest" %}（そしてプライベートリポジトリの場合に依存関係グラフをセットアップしているなら）{% endif %}、リポジトリ内に脆弱な依存関係を{% data variables.product.product_name %}が検出すると、週次のダイジェストメールを受け取ることになります。 セキュリティアラートは、Web通知、個別のメール通知、日次のメールダイジェスト、{% data variables.product.product_name %}インターフェース上のアラートとして設定することもできます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
 {% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/repositories/security-alerts-x-github-severity.md b/translations/ja-JP/data/reusables/repositories/security-alerts-x-github-severity.md
index 7230ee9994..67a366bc7f 100644
--- a/translations/ja-JP/data/reusables/repositories/security-alerts-x-github-severity.md
+++ b/translations/ja-JP/data/reusables/repositories/security-alerts-x-github-severity.md
@@ -1 +1 @@
-Email notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} that affect one or more repositories include the `X-GitHub-Severity`  header field. You can use the value of the `X-GitHub-Severity` header field to filter email notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
+`X-GitHub-Severity`ヘッダフィールドを含む、1つ以上のリポジトリに影響する{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}に対するメール通知。 `X-GitHub-Severity`ヘッダフィールドは、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}に対するメール通知のフィルタリングに利用できます。
diff --git a/translations/ja-JP/data/reusables/repositories/security-guidelines.md b/translations/ja-JP/data/reusables/repositories/security-guidelines.md
index d3780d4aac..31d1a1a3f7 100644
--- a/translations/ja-JP/data/reusables/repositories/security-guidelines.md
+++ b/translations/ja-JP/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-セキュリティポリシーを作成して、プロジェクト中のセキュリティ脆弱性を責任を持って報告するための指示を出すことができます。 詳しい情報については「[リポジトリへのセキュリティポリシーの追加](/articles/adding-a-security-policy-to-your-repository)」を参照してください。
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+セキュリティポリシーを作成して、プロジェクト中のセキュリティ脆弱性を報告するための指示を出すことができます。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/code-security/getting-started/adding-a-security-policy-to-your-repository)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/select-marketplace-apps.md b/translations/ja-JP/data/reusables/repositories/select-marketplace-apps.md
index 2a403e814c..64bae969d0 100644
--- a/translations/ja-JP/data/reusables/repositories/select-marketplace-apps.md
+++ b/translations/ja-JP/data/reusables/repositories/select-marketplace-apps.md
@@ -1,5 +1,5 @@
 {% if currentVersion == "free-pro-team@latest" %}
-1. Optionally, if the personal account or organization in which you're creating uses any
-{% data variables.product.prodname_github_app %}s from {% data variables.product.prodname_marketplace %}, select any apps you'd like to use in the repository.
+1. あるいは、作成している個人アカウントあるいはOrganizationが
+{% data variables.product.prodname_marketplace %}からの{% data variables.product.prodname_github_app %}を使用しているなら、リポジトリで使用したいアプリケーションを選択してください。
   ![{% data variables.product.prodname_marketplace %} から取得したアカウントの {% data variables.product.prodname_github_app %} のリストと、アクセスを許可するオプション](/assets/images/help/repository/create-repository-choose-marketplace-apps.png)
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/ja-JP/data/reusables/repositories/sidebar-dependabot-alerts.md
index 7fe612c019..5192d1a657 100644
--- a/translations/ja-JP/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/ja-JP/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**. ![{% data variables.product.prodname_dependabot_alerts %}タブ](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. セキュリティサイドバーで、**{% data variables.product.prodname_dependabot_alerts %}**をクリックしてください。{% if currentVersion == "free-pro-team@latest" %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md
index ba73880189..89aa538ae2 100644
--- a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md
+++ b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md
@@ -1 +1 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}直線状のコミット履歴を必要とする保護されたブランチのルールがリポジトリ中にあるなら、squashマージ、リベースマージ、あるいはその両方を許可しなければなりません。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)」を参照してください。{% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/start-line-comment.md b/translations/ja-JP/data/reusables/repositories/start-line-comment.md
index 18ee4b237e..eb249854f2 100644
--- a/translations/ja-JP/data/reusables/repositories/start-line-comment.md
+++ b/translations/ja-JP/data/reusables/repositories/start-line-comment.md
@@ -1 +1 @@
-1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon.{% endif %} ![青いコメントアイコン](/assets/images/help/commits/hover-comment-icon.gif)
+1. コメントを追加したいコードの行の上にカーソルを移動し、青いコメントアイコンをクリックしてください。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}複数行にコメントを追加するには、クリックしてからドラッグで行の範囲を選択し、続いて青いコメントアイコンをクリックしてください。{% endif %} ![青いコメントアイコン](/assets/images/help/commits/hover-comment-icon.gif)
diff --git a/translations/ja-JP/data/reusables/repositories/suggest-changes.md b/translations/ja-JP/data/reusables/repositories/suggest-changes.md
index ac14832bc2..71d73982fc 100644
--- a/translations/ja-JP/data/reusables/repositories/suggest-changes.md
+++ b/translations/ja-JP/data/reusables/repositories/suggest-changes.md
@@ -1 +1 @@
-1. Optionally, to suggest a specific change to the line{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} or lines{% endif %}, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![サジェッションブロック](/assets/images/help/pull_requests/suggestion-block.png)
+1. あるいは、特定の変更を行{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}あるいは複数行{% endif %}に対して示唆するには、{% octicon "diff" aria-label="The diff symbol" %}をクリックし、示唆するブロック内のテキストを編集してください。 ![サジェッションブロック](/assets/images/help/pull_requests/suggestion-block.png)
diff --git a/translations/ja-JP/data/reusables/repositories/tracks-vulnerabilities.md b/translations/ja-JP/data/reusables/repositories/tracks-vulnerabilities.md
index 7b131594a3..74fe9cc690 100644
--- a/translations/ja-JP/data/reusables/repositories/tracks-vulnerabilities.md
+++ b/translations/ja-JP/data/reusables/repositories/tracks-vulnerabilities.md
@@ -1,5 +1,5 @@
-We add vulnerabilities to the {% data variables.product.prodname_advisory_database %} from the following sources:
+脆弱性は、以下のソースから{% data variables.product.prodname_advisory_database %}に追加されます。
 - [National Vulnerability Database](https://nvd.nist.gov/)
 - {% data variables.product.prodname_dotcom %}上のパブリックなコミット内の脆弱性の検出に、機械学習と人間によるレビューの組み合わせ
-- Security advisories reported on {% data variables.product.prodname_dotcom %}
-- The [npm Security advisories](https://www.npmjs.com/advisories) database
+- {% data variables.product.prodname_dotcom %}で報告されたセキュリティアドバイザリ
+- [npm Security advisories](https://www.npmjs.com/advisories)データベース
diff --git a/translations/ja-JP/data/reusables/repositories/transfer-repository-steps.md b/translations/ja-JP/data/reusables/repositories/transfer-repository-steps.md
index ba96c652f4..c3241f0a47 100644
--- a/translations/ja-JP/data/reusables/repositories/transfer-repository-steps.md
+++ b/translations/ja-JP/data/reusables/repositories/transfer-repository-steps.md
@@ -4,7 +4,7 @@
 1. 新しいオーナーのプランによって生じうる機能の損失についての警告を読んでください。 ![無料製品を使っている人物へのリポジトリの移譲に関する警告](/assets/images/help/repository/repo-transfer-free-plan-warnings.png)
 1. 移譲したいリポジトリの名前を入力し、**I understand, transfer this repository（理解しました。このリポジトリを移譲してください）**をクリックしてください。 ![移譲ボタン](/assets/images/help/repository/repo-transfer-complete.png)
 {% else %}
-1. Click **Transfer**. ![移譲ボタン](/assets/images/help/repository/repo-transfer.png)
+1. **Transfer（移譲）**をクリックしてください。 ![移譲ボタン](/assets/images/help/repository/repo-transfer.png)
 1. 警告を読み、リポジトリ名を入力して行ったことを確認してください。
 1. 新しいオーナーの名前を入力し、**I understand, transfer this repo（理解しました。このリポジトリを移譲してください）**をクリックしてください。 ![移譲ボタン](/assets/images/help/repository/repo-transfer-complete.png)
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md
index 1a25944892..444d28f60d 100644
--- a/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md
+++ b/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md
@@ -1 +1 @@
-For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`.
+たとえば、以下のURLは短縮された7文字のSHAコードを使って`c3a414e`と`faf7c6f`のコミットを比較しています。 `https://github.com/github/linguist/compare/c3a414e..faf7c6f.`.
diff --git a/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md
index 39cc5396f0..8e405a1614 100644
--- a/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md
+++ b/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md
@@ -1,9 +1,9 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-1. Any failed steps are automatically expanded to display the results.
+1. 失敗したステップは自動的に展開され、結果が表示されます。
    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %}
+   ![Super linterワークフローの結果](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %}
 ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png)
 {% endif %}
 {% else %}
-1. Expand the **Run Super-Linter** step to view the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results.png)
+1. **Run Super-Linter**ステップを展開して、結果を表示してください。 ![Super linterワークフローの結果](/assets/images/help/repository/super-linter-workflow-results.png)
 {% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/repositories/view-run-superlinter.md b/translations/ja-JP/data/reusables/repositories/view-run-superlinter.md
index 8725b33e6c..12ba4e5ac1 100644
--- a/translations/ja-JP/data/reusables/repositories/view-run-superlinter.md
+++ b/translations/ja-JP/data/reusables/repositories/view-run-superlinter.md
@@ -1 +1 @@
-1. From the list of workflow runs, click the name of the run you want to see. ![ワークフローの実行の名前](/assets/images/help/repository/superlinter-run-name.png)
\ No newline at end of file
+1. ワークフローの実行リストから、表示させたい実行の名前をクリックしてください。 ![ワークフローの実行の名前](/assets/images/help/repository/superlinter-run-name.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/repositories/view-run.md b/translations/ja-JP/data/reusables/repositories/view-run.md
index a508293d61..fb43be0f7a 100644
--- a/translations/ja-JP/data/reusables/repositories/view-run.md
+++ b/translations/ja-JP/data/reusables/repositories/view-run.md
@@ -1 +1 @@
-1. From the list of workflow runs, click the name of the run you want to see. ![ワークフローの実行の名前](/assets/images/help/repository/run-name.png)
+1. ワークフローの実行リストから、表示させたい実行の名前をクリックしてください。 ![ワークフローの実行の名前](/assets/images/help/repository/run-name.png)
diff --git a/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md b/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md
index 51721e7a7e..6a9cb56c23 100644
--- a/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md
+++ b/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md
@@ -1,10 +1,10 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 You can then copy the link from the address bar of your web browser.
+1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 このリンクは、Webブラウザのアドレスバーからコピーできます。
   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
   ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button-updated-2.png)
   {% else %}
   ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button-updated.png)
   {% endif %}
 {% else %}
-1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 You can then copy the link from the address bar of your web browser. ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button.png)
+1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 このリンクは、Webブラウザのアドレスバーからコピーできます。 ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button.png)
 {% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/repositories/workflow-notifications.md b/translations/ja-JP/data/reusables/repositories/workflow-notifications.md
index 106d0e87ba..119c631a29 100644
--- a/translations/ja-JP/data/reusables/repositories/workflow-notifications.md
+++ b/translations/ja-JP/data/reusables/repositories/workflow-notifications.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_actions %}に対するメールあるいはWeb通知を有効化すると、あなたが起動したワークフローランが完了すると通知されます。 この通知には、ワークフローランのステータス（成功、失敗、ニュートラル、キャンセルされたランが含まれます）が含まれます。 ワークフローランが失敗したときにだけ通知を受けるようにすることもできます。
+{% data variables.product.prodname_actions %}に対するメールあるいはWeb通知を有効化すると、あなたが起動したワークフローの実行が完了すると通知されます。 この通知には、ワークフローの実行のステータス（成功、失敗、ニュートラル、キャンセルされた実行が含まれます）が含まれます。 ワークフローの実行が失敗したときにだけ通知を受けるようにすることもできます。
 
-Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %}
+スケジュールされたワークフローに関する通知は、最初にワークフローを作成したユーザに送信されます。 ワークフローファイルのcron構文を他のユーザが更新した場合、それ以降の通知はそのユーザに送られるようになります。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}スケジュールされたワークフローが無効化され、その後に有効化されると、通知は最後にcron構文を変更したユーザではなく、ワークフローを再有効化したユーザに送られるようになります。{% endif %}
 
-リポジトリのActionsタブでワークフローランのステータスを見ることもできます。 詳細については、「[ワークフロー実行の管理](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)」を参照してください。
+リポジトリのActionsタブでワークフローの実行のステータスを見ることもできます。 詳細については、「[ワークフロー実行の管理](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/repositories/you-can-fork.md b/translations/ja-JP/data/reusables/repositories/you-can-fork.md
index 691c670483..4b06d149ef 100644
--- a/translations/ja-JP/data/reusables/repositories/you-can-fork.md
+++ b/translations/ja-JP/data/reusables/repositories/you-can-fork.md
@@ -1,7 +1,7 @@
-{% if currentVersion == "github-ae@latest" %}If the policies for your enterprise permit forking internal and private repositories, you{% else %}You{% endif %} can fork a repository to your user account or any organization where you have repository creation permissions. 詳細は「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。
+{% if currentVersion == "github-ae@latest" %}Enterpriseのポリシーでインターナル及びプライベートのリポジトリのフォークが許されているなら、{% endif %}ユーザアカウントあるいはリポジトリの作成権限を持つOrganizationにリポジトリをフォークできます。 詳細は「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-If you have access to a private repository and the owner permits forking, you can fork the repository to your user account or any organization on {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} where you have repository creation permissions. {% if currentVersion == "free-pro-team@latest" %}You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}. For more information, see "[GitHub's products](/articles/githubs-products)."{% endif %}
+プライベートリポジトリにアクセスでき、オーナーがフォークを許可しているなら、そのリポジトリを自分のアカウントあるいはリポジトリの作成権限を持っている{% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %}上のOrganizationにフォークできます。 {% if currentVersion == "free-pro-team@latest" %}ぷらいべーとリポジトリは、{% data variables.product.prodname_free_team %}を使っているOrganizationにはフォークできません。 詳しい情報については「[GitHubの製品](/articles/githubs-products)」を参照してください。{% endif %}
 
 {% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md
index c83e052fa8..3ccc409bd8 100644
--- a/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md
+++ b/translations/ja-JP/data/reusables/saml/about-user-provisioning-enterprise-account.md
@@ -1 +1 @@
-If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP.
+OktaをIdPとして使っており、Enterpriseアカウントのためのプライベートベータに参加しているなら、EnterpriseアカウントOrganizationのメンバーシップをSCIMで管理できます。 SCIMは、IdP上でそれぞれのOrganizationに対応するグループのメンバーかどうかに基づいて、人を自動的にEnterpriseのOrganizationに招待したり削除したりします。
diff --git a/translations/ja-JP/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md b/translations/ja-JP/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md
index e60bce6013..0adb2680fb 100644
--- a/translations/ja-JP/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md
+++ b/translations/ja-JP/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md
@@ -1 +1 @@
-You'll configure identity and access management for {% data variables.product.product_name %} by entering the details for your SAML IdP during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)."
+初期化の間にSAML IdPの詳細を入力することによって、{% data variables.product.product_name %}のアイデンティティとアクセスの管理を設定することになります。 詳しい情報については「[{% data variables.product.prodname_ghe_managed %}の初期化](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md b/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md
index 08c138d1ba..8154c49b11 100644
--- a/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md
+++ b/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md
@@ -1 +1 @@
-{% data variables.product.product_name %} uses SAML SSO for user authentication. You can centrally manage access to {% data variables.product.prodname_ghe_managed %} from an IdP that supports the SAML 2.0 standard.
+{% data variables.product.product_name %}は、ユーザ認証にSAML SSOを使用します。 {% data variables.product.prodname_ghe_managed %}へのアクセスは、SAML 2.0標準をサポートするIdPから集中管理できます。
diff --git a/translations/ja-JP/data/reusables/saml/assert-the-administrator-attribute.md b/translations/ja-JP/data/reusables/saml/assert-the-administrator-attribute.md
index ff9e3bc75d..9814264a4b 100644
--- a/translations/ja-JP/data/reusables/saml/assert-the-administrator-attribute.md
+++ b/translations/ja-JP/data/reusables/saml/assert-the-administrator-attribute.md
@@ -1 +1 @@
-To make a person an enterprise owner, you must delegate ownership permission in your IdP. Include the `administrator` attribute in the SAML assertion for the user account on the IdP, with the value of `true`. For more information about enterprise owners, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)."
+人をEnterpriseのオーナーにするには、所有権をIdPで委任しなければなりません。 IdP上のユーザアカウントに対して、SAMLアサーションの`administrator`属性を、値を`true`にして含めてください。 Enterpriseのオーナーに関する詳しい情報については「[Enterprise内のロール](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/saml/assign-yourself-to-okta.md b/translations/ja-JP/data/reusables/saml/assign-yourself-to-okta.md
index 42cb7d475a..ca407cd5d4 100644
--- a/translations/ja-JP/data/reusables/saml/assign-yourself-to-okta.md
+++ b/translations/ja-JP/data/reusables/saml/assign-yourself-to-okta.md
@@ -1 +1 @@
-1. Assign the application to your user in Okta. For more information, see [Assign applications to users](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm) in the Okta documentation.
+1. Oktaでユーザにアプリケーションを割り当ててください。 詳しい情報については、Oktaのドキュメンテーションの[Assign applications to users](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm)を参照してください。
diff --git a/translations/ja-JP/data/reusables/saml/click-enterprise-account-application.md b/translations/ja-JP/data/reusables/saml/click-enterprise-account-application.md
index 3f8b0dcf57..abdbe19cbe 100644
--- a/translations/ja-JP/data/reusables/saml/click-enterprise-account-application.md
+++ b/translations/ja-JP/data/reusables/saml/click-enterprise-account-application.md
@@ -1 +1 @@
-1. Click the label for the application you created for your enterprise account.
+1. Enterpriseアカウント用に作成したアプリケーションのラベルをクリックしてください。
diff --git a/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md
index 231a386883..ca65df233c 100644
--- a/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md
+++ b/translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md
@@ -1 +1 @@
-If you can't sign into your enterprise because {% data variables.product.product_name %} can't communicate with your SAML IdP, you can contact {% data variables.contact.github_support %}, who can help you access {% data variables.product.product_name %} to update the SAML SSO configuration. 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。
+{% data variables.product.product_name %}がSAML IdPと通信できないためにEnterpriseにサインインできない場合は、SAML SSOの設定を更新するための{% data variables.product.product_name %}へのアクセスを支援してくれる{% data variables.contact.github_support %}に連絡してください。 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/saml/create-a-machine-user.md b/translations/ja-JP/data/reusables/saml/create-a-machine-user.md
index 0f0bdbf11d..01b9fe0f9e 100644
--- a/translations/ja-JP/data/reusables/saml/create-a-machine-user.md
+++ b/translations/ja-JP/data/reusables/saml/create-a-machine-user.md
@@ -1 +1 @@
-Create and use a dedicated machine user account on your IdP to associate with the first enterprise owner account on {% data variables.product.product_name %}. Store the credentials for the user account securely in a password manager.
+{% data variables.product.product_name %}上の最初のEnterpriseオーナーアカウントと関連づけるための、専用のマシンユーザアカウントをIdPで作成して使用してください。 このユーザアカウントの認証情報は、パスワードマネージャに安全に保存してください。
diff --git a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md
index be784eeb4f..3908d8a61b 100644
--- a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md
+++ b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md
@@ -1 +1 @@
-SAML single sign-on (SSO) gives organization owners and enterprise owners on {% data variables.product.prodname_dotcom %} a way to control and secure access to organization resources like repositories, issues, and pull requests.
+SAMLシングルサインオン（SSO）は、{% data variables.product.prodname_dotcom %}上のOrganizationのオーナー及びEnterpriseのオーナーに対し、リポジトリ、Issue、Pull RequestのようなOrganizationのリソースに対するアクセスをコントロールし、セキュアに保つ方法を提供します。
diff --git a/translations/ja-JP/data/reusables/saml/okta-admin-button.md b/translations/ja-JP/data/reusables/saml/okta-admin-button.md
index ffc7938d2d..49f980b96d 100644
--- a/translations/ja-JP/data/reusables/saml/okta-admin-button.md
+++ b/translations/ja-JP/data/reusables/saml/okta-admin-button.md
@@ -1 +1 @@
-1. In Okta, in the upper-right corner, click **Admin**. ![Admin button in Okta](/assets/images/help/saml/okta-admin-button.png)
+1. Oktaで、右上の**Admin**をクリックしてください。 ![OktaのAdminボタン](/assets/images/help/saml/okta-admin-button.png)
diff --git a/translations/ja-JP/data/reusables/saml/okta-provisioning-tab.md b/translations/ja-JP/data/reusables/saml/okta-provisioning-tab.md
index 3b44550fd4..7088b8618a 100644
--- a/translations/ja-JP/data/reusables/saml/okta-provisioning-tab.md
+++ b/translations/ja-JP/data/reusables/saml/okta-provisioning-tab.md
@@ -1 +1 @@
-1. Under the name of the application, click **Provisioning**. ![Okta アプリケーションの [Provisioning] タブ](/assets/images/help/saml/okta-provisioning-tab.png)
+1. アプリケーション名の下で、**Provisioning（プロビジョニング）**をクリックしてください。 ![Okta アプリケーションの [Provisioning] タブ](/assets/images/help/saml/okta-provisioning-tab.png)
diff --git a/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md b/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md
index 535bceec2f..ed96c2ae94 100644
--- a/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md
+++ b/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md
@@ -1 +1 @@
-1. Under the name of the application, click **Sign on**. ![Okta アプリケーションの [Sign on] タブ](/assets/images/help/saml/okta-sign-on-tab.png)
+1. アプリケーション名の下で、**Sign on（サインオン）**をクリックしてください。 ![Okta アプリケーションの [Sign on] タブ](/assets/images/help/saml/okta-sign-on-tab.png)
diff --git a/translations/ja-JP/data/reusables/saml/use-classic-ui.md b/translations/ja-JP/data/reusables/saml/use-classic-ui.md
index f424386af0..e707b49b75 100644
--- a/translations/ja-JP/data/reusables/saml/use-classic-ui.md
+++ b/translations/ja-JP/data/reusables/saml/use-classic-ui.md
@@ -1,3 +1,3 @@
-You must use the "Classic UI" in Okta. 詳しい情報については、Okta のブログで「[Organized Navigation](https://developer.okta.com/blog/2017/09/25/all-new-developer-console#new-look--feel)」を参照してください。
+Oktaでは"Classic UI"を使わなければなりません。 詳しい情報については、Okta のブログで「[Organized Navigation](https://developer.okta.com/blog/2017/09/25/all-new-developer-console#new-look--feel)」を参照してください。
 
 ![ダッシュボードの上にある Okta の UI 選択機能で [Classic UI] を選択](/assets/images/help/saml/okta-classic-ui.png)
diff --git a/translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md b/translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md
index f5965053ba..96ff9dd99b 100644
--- a/translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md
+++ b/translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md
@@ -1 +1 @@
-You must periodically authenticate with your SAML IdP to authenticate and gain access to {% if currentVersion == "free-pro-team@latest" %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}. このログイン間隔は利用しているアイデンティティプロバイダ (IdP) によって指定されますが、一般的には 24 時間です。 このように定期的にログインしなければならないことから、アクセスの長さには制限があり、アクセスを続行するには再認証が必要になります。 {% if currentVersion == "free-pro-team@latest" %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %}
+認証を受けて、{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}上のOrganizationのリソース{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}にアクセスできるようにするには、定期的にSAML IdPで認証を受けなければなりません。 このログイン間隔は利用しているアイデンティティプロバイダ (IdP) によって指定されますが、一般的には 24 時間です。 このように定期的にログインしなければならないことから、アクセスの長さには制限があり、アクセスを続行するには再認証が必要になります。 {% if currentVersion == "free-pro-team@latest" %}アクティブなSAMLセッションは、セキュリティ設定で表示及び管理できます。 詳しい情報については「[アクティブなSAMLセッションの表示と管理](/articles/viewing-and-managing-your-active-saml-sessions)」を参照してください。{% endif %}
diff --git a/translations/ja-JP/data/reusables/scim/after-you-configure-saml.md b/translations/ja-JP/data/reusables/scim/after-you-configure-saml.md
index 85246f3cf0..e6267936b4 100644
--- a/translations/ja-JP/data/reusables/scim/after-you-configure-saml.md
+++ b/translations/ja-JP/data/reusables/scim/after-you-configure-saml.md
@@ -1 +1 @@
-By default, your IdP does not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application. {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" %}provisions access to your resources on {% else %}creates a user account {% endif %}using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% if currentVersion == "free-pro-team@latest" %}your resources on {% endif %} {% data variables.product.product_name %} and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to {% data variables.product.product_name %}, and you must manually {% if currentVersion == "free-pro-team@latest" %}deprovision access {% else %}deactivate the user account on {% endif %}{% data variables.product.product_name %} during offboarding. You can use SCIM to provision and deprovision {% if currentVersion == "free-pro-team@latest" %}access to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %} {% else %}user accounts and access for {% data variables.product.product_name %} {% endif %}automatically when you assign or unassign the application on your IdP.
\ No newline at end of file
+デフォルトでは、アプリケーションを割り当てあるいは割り当て解除したときに、IdPは{% data variables.product.product_name %}と自動的に通信はしません。 {% data variables.product.product_name %}は、誰かが初めてIdPを通じて認証を受けて{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}上のリソース{% endif %}にアクセスし、サインインした時に、SAML Just-in-Time (JIT)プロビジョニングを使用して {% if currentVersion == "free-pro-team@latest" %}リソースへのアクセスをプロビジョニング{% else %}ユーザアカウントを作成{% endif %}します。 {% data variables.product.product_name %}へのアクセスを許可した際には、ユーザに手動で通知する必要があるかもしれません。そしてオフボーディングの間には、手動で{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}へのアクセスのプロビジョニングを解除{% else %}上のユーザアカウントの無効化{% endif %}をしなければなりません。 IdP上でアプリケーションを割り当てもしくは割り当て解除する際には、SCIMを使って自動的に{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}上のEnterpriseが所有しているOrganizationへのアクセスを{% else %}{% data variables.product.product_name %}のユーザアカウントとアクセスを{% endif %}プロビジョニング及びプロビジョニング解除できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/scim/enterprise-account-scim.md b/translations/ja-JP/data/reusables/scim/enterprise-account-scim.md
index 1797863354..a919fc54c5 100644
--- a/translations/ja-JP/data/reusables/scim/enterprise-account-scim.md
+++ b/translations/ja-JP/data/reusables/scim/enterprise-account-scim.md
@@ -1 +1 @@
-If you're participating in the private beta for user provisioning for enterprise accounts, when you enable SAML for your enterprise account, SCIM provisioning and deprovisioning is enabled by default in {% data variables.product.product_name %}. You can use provisioning to manage organization membership by configuring SCIM in your IdP.
+Enterpriseアカウントのためのユーザプロビジョニングのプライベートベータに参加しているなら、EnterpriseアカウントでSAMLを有効化すると、{% data variables.product.product_name %}ではデフォルトでSCIMのプロビジョニング及びプロビジョニング解除が有効になります。 IdPでSCIMを設定することによって、プロビジョニングでOrganizationのメンバーシップを管理できます。
diff --git a/translations/ja-JP/data/reusables/scim/supported-idps.md b/translations/ja-JP/data/reusables/scim/supported-idps.md
index 84aea5e724..df090da0ed 100644
--- a/translations/ja-JP/data/reusables/scim/supported-idps.md
+++ b/translations/ja-JP/data/reusables/scim/supported-idps.md
@@ -1,4 +1,4 @@
-The following IdPs can provision or deprovision user accounts on {% data variables.product.product_location %} using SCIM.
+以下のIdPは、SCIMを使って{% data variables.product.product_location %}上のユーザアカウントのプロビジョニングあるいはプロビジョニング解除ができます。
 
 {% if currentVersion == "github-ae@latest" %}
 - Azure AD
diff --git a/translations/ja-JP/data/reusables/search/date_gt_lt.md b/translations/ja-JP/data/reusables/search/date_gt_lt.md
index 213cd754e1..0a975f4d9a 100644
--- a/translations/ja-JP/data/reusables/search/date_gt_lt.md
+++ b/translations/ja-JP/data/reusables/search/date_gt_lt.md
@@ -1 +1 @@
-When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
+日付に対して検索を行う場合、結果をさらにフィルタリングするためにより大きい、より小さい、範囲の修飾子を利用できます。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/search/required_login.md b/translations/ja-JP/data/reusables/search/required_login.md
index 6d8598a94a..352eb454dd 100644
--- a/translations/ja-JP/data/reusables/search/required_login.md
+++ b/translations/ja-JP/data/reusables/search/required_login.md
@@ -1 +1 @@
-You must be signed into a user account on {% data variables.product.product_name %} to search for code across all public repositories.
+すべてのパブリックリポジトリに渡ってコードを検索するには、{% data variables.product.product_name %}上のユーザアカウントにサインインしなければなりません。
diff --git a/translations/ja-JP/data/reusables/search/syntax_tips.md b/translations/ja-JP/data/reusables/search/syntax_tips.md
index 35686bbc54..92a1293a09 100644
--- a/translations/ja-JP/data/reusables/search/syntax_tips.md
+++ b/translations/ja-JP/data/reusables/search/syntax_tips.md
@@ -1,7 +1,7 @@
 {% tip %}
 
 **参考:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
-  - This article contains links to example searches on the {% data variables.product.prodname_dotcom_the_website %} website, but you can use the same search filters with {% data variables.product.product_name %}. In the linked example searches, replace `github.com` with the hostname for {% data variables.product.product_location %}.{% endif %}
+  - この記事には、{% data variables.product.prodname_dotcom_the_website %} のウェブサイトでの検索例へのリンクが含まれていますが、同じ検索フィルターは {% data variables.product.product_name %} でも使えます。 リンクされている検索例で、`github.com`を{% data variables.product.product_location %}のホスト名で置き換えてください。{% endif %}
   - 検索結果を改良する検索修飾子を追加できる検索構文のリストについては、「[検索構文を理解する](/articles/understanding-the-search-syntax)」を参照してください。
   - 複数単語の検索用語は引用符で囲みます。 たとえば "In progress" というラベルを持つ Issue を検索したい場合は、`label:"in progress"` とします。 検索では、大文字と小文字は区別されません。
 
diff --git a/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md b/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md
index 51b8c7a7d1..e498d85c79 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/about-secret-scanning.md
@@ -1 +1 @@
-If someone checks a secret from a {% data variables.product.company_short %} partner into a {% if currentVersion == "free-pro-team@latest" %}public or private{% endif %} repository on {% data variables.product.product_name %}, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository.
+誰かが{% data variables.product.company_short %}パートナーからシークレットを{% data variables.product.product_name %}上の{% if currentVersion == "free-pro-team@latest" %}パブリックもしくはプライベートの{% endif %}リポジトリにチェックインすると、{% data variables.product.prodname_secret_scanning %}はそのシークレットがチェックインされたときに捕捉し、漏洩のインパクトの緩和を支援します。 リポジトリ管理者は、シークレットを含むコミットについて通知され、リポジトリのセキュリティタブですべての検出されたシークレットを素早く見ることができます。
diff --git a/translations/ja-JP/data/reusables/secret-scanning/api-beta.md b/translations/ja-JP/data/reusables/secret-scanning/api-beta.md
index 22975c18ff..538577e7d9 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/api-beta.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/api-beta.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change.
+**ノート:** {% data variables.product.prodname_secret_scanning %} APIは現在ベータで、変更されることがあります。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/secret-scanning/beta.md b/translations/ja-JP/data/reusables/secret-scanning/beta.md
index b7bbe9befc..cce665e1e0 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/beta.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/beta.md
@@ -1,7 +1,7 @@
 {% if  currentVersion == "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned repositories is currently in beta and subject to change.
+**ノート:** Organizationが所有するリポジトリのための{% data variables.product.prodname_secret_scanning_caps %}は現在ベータで、変更されることがあります。
 
 {% endnote %}
 
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**ノート:** {% data variables.product.prodname_secret_scanning_caps %}は{% data variables.product.prodname_ghe_server %} 3.0ではベータです。 For the generally available release of secret scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
+**ノート:** {% data variables.product.prodname_secret_scanning_caps %}は{% data variables.product.prodname_ghe_server %} 3.0ではベータでした。 {% data variables.product.prodname_secret_scanning %}の一般に利用なリリースについては、{% data variables.product.prodname_ghe_server %}の最新リリースにアップグレードしてください。
 
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md
index eb0329e7fe..448a350a5a 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)."
+**ノート:** この機能を使う前には、サイト管理者が{% data variables.product.product_location %}の{% data variables.product.prodname_secret_scanning %}を有効化していなければなりません。 詳しい情報については「[アプライアンスのための{% data variables.product.prodname_secret_scanning %}の設定](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)」を参照してください。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index e75538fe3d..e45beb53f4 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| Partner                   | Supported secret                       | API slug                                 |
-| ------------------------- | -------------------------------------- | ---------------------------------------- |
-| n/a                       | JSON Web Token                         | json_web_token                         |
-| n/a                       | OAuth Client Credential                | api_credential_assignment              |
-| Adafruit IO               | Adafruit IO Key                        | adafruit_io_key                        |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID            | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Alibaba Cloud Access Key Secret        | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID               | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Amazon AWS Secret Access Key           | aws_secret_access_key                  |
-| Asana                     | Asana Personal Access Token            | asana_personal_access_token            |
-| Atlassian                 | Atlassian API Token                    | atlassian_api_token                    |
-| Atlassian                 | Atlassian JSON Web Token               | atlassian_jwt                            |
-| Azure                     | Azure DevOps Personal Access Token     | azure_devops_personal_access_token   |
-| Azure                     | Azure SAS Token                        | azure_sas_token                        |
-| Azure                     | Azure Service Management Certificate   | azure_management_certificate           |
-| Azure                     | Azure SQL Connection String            | azure_sql_connection_string            |
-| Azure                     | Azure Storage Account Key              | azure_storage_account_key              |
-| Clojars                   | Clojars Deploy Token                   | clojars_deploy_token                   |
-| CloudBees CodeShip        | CloudBees CodeShip Credential          | codeship_credential                      |
-| Databricks                | Databricks Access Token                | databricks_access_token                |
-| Discord                   | Discord Bot Token                      | discord_bot_token                      |
-| Doppler                   | Doppler Personal Token                 | doppler_personal_token                 |
-| Doppler                   | Doppler Service Token                  | doppler_service_token                  |
-| Doppler                   | Doppler CLI Token                      | doppler_cli_token                      |
-| Doppler                   | Doppler SCIM Token                     | doppler_scim_token                     |
-| Dropbox                   | Dropbox Access Token                   | dropbox_access_token                   |
-| Dropbox                   | Dropbox Short Lived Access Token       | dropbox_short_lived_access_token     |
-| Dynatrace                 | Dynatrace Access Token                 | dynatrace_access_token                 |
-| Dynatrace                 | Dynatrace Internal Token               | dynatrace_internal_token               |
-| Facebook                  | Facebook Access Token                  | facebook_access_token                  |
-| Finicity                  | Finicity App Key                       | finicity_app_key                       |
-| Frame.io                  | Frame.io JSON Web Token                | frameio_jwt                              |
-| Frame.io                  | Frame.io Developer Token               | frameio_developer_token                |
-| GitHub                    | GitHub SSH Private Key                 | github_ssh_private_key                 |
-| GitHub                    | GitHub Personal Access Token           | github_personal_access_token           |
-| GitHub                    | GitHub App Installation Access Token   | github_app_installation_access_token |
-| GoCardless                | GoCardless Live Access Token           | gocardless_live_access_token           |
-| GoCardless                | GoCardless Sandbox Access Token        | gocardless_sandbox_access_token        |
-| Google Cloud              | Google API Key                         | google_api_key                         |
-| Google Cloud              | Google Cloud Private Key ID            | google_cloud_private_key_id          |
-| Grafana                   | Grafana API Key                        | grafana_api_key                        |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token | terraform_api_token                    |
-| Hubspot                   | Hubspot API Key                        | hubspot_api_key                        |
-| Intercom                  | Intercom Access Token                  | intercom_access_token                  |
-| Lob                       | Lob Live API Key                       | lob_live_api_key                       |
-| Lob                       | Lob Test API Key                       | lob_test_api_key                       |
-| Mailchimp                 | Mailchimp API Key                      | mailchimp_api_key                      |
-| Mailgun                   | Mailgun API Key                        | mailgun_api_key                        |
-| npm                       | npm Access Token                       | npm_access_token                       |
-| NuGet                     | NuGet API Key                          | nuget_api_key                          |
-| Palantir                  | Palantir JSON Web Token                | palantir_jwt                             |
-| Postman                   | Postman API Key                        | postman_api_key                        |
-| Proctorio                 | Proctorio Consumer Key                 | proctorio_consumer_key                 |
-| Proctorio                 | Proctorio Linkage Key                  | proctorio_linkage_key                  |
-| Proctorio                 | Proctorio Registration Key             | proctorio_registration_key             |
-| Proctorio                 | Proctorio Secret Key                   | proctorio_secret_key                   |
-| Pulumi                    | Pulumi Access Token                    | pulumi_access_token                    |
-| PyPI                      | PyPI API Token                         | pypi_api_token                         |
-| RubyGems                  | RubyGems API Key                       | rubygems_api_key                       |
-| Samsara                   | Samsara API Token                      | samsara_api_token                      |
-| Samsara                   | Samsara OAuth Access Token             | samsara_oauth_access_token             |
-| SendGrid                  | SendGrid API Key                       | sendgrid_api_key                       |
-| Shopify                   | Shopify App Shared Secret              | shopify_app_shared_secret              |
-| Shopify                   | Shopify Access Token                   | shopify_access_token                   |
-| Shopify                   | Shopify Custom App Access Token        | shopify_custom_app_access_token      |
-| Shopify                   | Shopify Private App Password           | shopify_private_app_password           |
-| Slack                     | Slack API Token                        | slack_api_token                        |
-| Slack                     | Slack Incoming Webhook URL             | slack_incoming_webhook_url             |
-| Slack                     | Slack Workflow Webhook URL             | slack_workflow_webhook_url             |
-| SSLMate                   | SSLMate API Key                        | sslmate_api_key                        |
-| SSLMate                   | SSLMate Cluster Secret                 | sslmate_cluster_secret                 |
-| Stripe                    | Stripe API Key                         | stripe_api_key                         |
-| Stripe                    | Stripe Live API Secret Key             | stripe_live_secret_key                 |
-| Stripe                    | Stripe Test API Secret Key             | stripe_test_secret_key                 |
-| Stripe                    | Stripe Live API Restricted Key         | stripe_live_restricted_key             |
-| Stripe                    | Stripe Test API Restricted Key         | stripe_test_restricted_key             |
-| Tencent Cloud             | Tencent Cloud Secret ID                | tencent_cloud_secret_id                |
-| Twilio                    | Twilio Account String Identifier       | twilio_account_sid                     |
-| Twilio                    | Twilio API Key                         | twilio_api_key                         |
+| パートナー | サポートされているシークレット | APIスラッグ |
+| ----- | --------------- | ------- |
+|       |                 |         |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub個人アクセストークン | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuthアクセストークン | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHubリフレッシュトークン | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Appインストールアクセストークン | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH秘密鍵 | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index ebc268a20d..6365911578 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| Partner                   | Supported secret                                                            |
-| ------------------------- | --------------------------------------------------------------------------- |
-| Adafruit IO               | Adafruit IO Key                                                             |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair                      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair                         |
-| Atlassian                 | Atlassian API Token                                                         |
-| Atlassian                 | Atlassian JSON Web Token                                                    |
-| Azure                     | Azure DevOps Personal Access Token | azure_devops_personal_access_token |
-| Azure                     | Azure SAS Token | azure_sas_token                                         |
-| Azure                     | Azure Service Management Certificate | azure_management_certificate       |
-| Azure                     | Azure SQL Connection String | azure_sql_connection_string                 |
-| Azure                     | Azure Storage Account Key | azure_storage_account_key                     |
-| Clojars                   | Clojars Deploy Token                                                        |
-| CloudBees CodeShip        | CloudBees CodeShip Credential                                               |
-| Databricks                | Databricks Access Token                                                     |
-| Datadog                   | Datadog API Key                                                             |
-| Discord                   | Discord Bot Token                                                           |
-| Doppler                   | Doppler Personal Token                                                      |
-| Doppler                   | Doppler Service Token                                                       |
-| Doppler                   | Doppler CLI Token                                                           |
-| Doppler                   | Doppler SCIM Token                                                          |
-| Dropbox                   | Dropbox Access Token                                                        |
-| Dropbox                   | Dropbox Short Lived Access Token                                            |
-| Dynatrace                 | Dynatrace Access Token                                                      |
-| Dynatrace                 | Dynatrace Internal Token                                                    |
-| Finicity                  | Finicity App Key                                                            |
-| Frame.io                  | Frame.io JSON Web Token                                                     |
-| Frame.io                  | Frame.io Developer Token                                                    |
-| GitHub                    | GitHub SSH Private Key                                                      |
-| GitHub                    | GitHub Personal Access Token                                                |
-| GitHub                    | GitHub App Installation Access Token                                        |
-| GoCardless                | GoCardless Live Access Token                                                |
-| GoCardless                | GoCardless Sandbox Access Token                                             |
-| Google Cloud              | Google API Key                                                              |
-| Google Cloud              | Google Cloud Private Key ID                                                 |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                                      |
-| Hubspot                   | Hubspot API Key                                                             |
-| Mailchimp                 | Mailchimp API Key                                                           |
-| Mailchimp                 | Mandrill API Key                                                            |
-| Mailgun                   | Mailgun API Key                                                             |
-| MessageBird               | MessageBird API Key                                                         |
-| npm                       | npm Access Token                                                            |
-| NuGet                     | NuGet API Key                                                               |
-| Palantir                  | Palantir JSON Web Token                                                     |
-| Plivo                     | Plivo Auth Token                                                            |
-| Postman                   | Postman API Key                                                             |
-| Proctorio                 | Proctorio Consumer Key                                                      |
-| Proctorio                 | Proctorio Linkage Key                                                       |
-| Proctorio                 | Proctorio Registration Key                                                  |
-| Proctorio                 | Proctorio Secret Key                                                        |
-| Pulumi                    | Pulumi Access Token                                                         |
-| PyPI                      | PyPI API Token                                                              |
-| RubyGems                  | RubyGems API Key                                                            |
-| Samsara                   | Samsara API Token                                                           |
-| Samsara                   | Samsara OAuth Access Token                                                  |
-| Shopify                   | Shopify App Shared Secret                                                   |
-| Shopify                   | Shopify Access Token                                                        |
-| Shopify                   | Shopify Custom App Access Token                                             |
-| Shopify                   | Shopify Private App Password                                                |
-| Slack                     | Slack API Token                                                             |
-| Slack                     | Slack Incoming Webhook URL                                                  |
-| Slack                     | Slack Workflow Webhook URL                                                  |
-| SSLMate                   | SSLMate API Key                                                             |
-| SSLMate                   | SSLMate Cluster Secret                                                      |
-| Stripe                    | Stripe Live API Secret Key                                                  |
-| Stripe                    | Stripe Test API Secret Key                                                  |
-| Stripe                    | Stripe Live API Restricted Key                                              |
-| Stripe                    | Stripe Test API Restricted Key                                              |
-| Tencent Cloud             | Tencent Cloud Secret ID                                                     |
-| Twilio                    | Twilio Account String Identifier                                            |
-| Twilio                    | Twilio API Key                                                              |
+| パートナー                     | サポートされているシークレット                                     |
+| ------------------------- | --------------------------------------------------- |
+| Adafruit IO               | Adafruit IO Key                                     |
+| Adobe                     | Adobe Device Token                                  |
+| Adobe                     | Adobe Service Token                                 |
+| Adobe                     | Adobe Short-Lived Access Token                      |
+| Adobe                     | Adobe JSON Web Token                                |
+| Alibaba Cloud             | Alibaba Cloud Access Key ID及びAccess Key Secret pair |
+| Amazon Web Services (AWS) | Amazon AWS Access Key ID及びSecret Access Key pair    |
+| Atlassian                 | Atlassian API Token                                 |
+| Atlassian                 | Atlassian JSON Web Token                            |
+| Azure                     | Azure DevOps Personal Access Token                  |
+| Azure                     | Azure SAS Token                                     |
+| Azure                     | Azure Service Management Certificate                |
+| Azure                     | Azure SQL Connection String                         |
+| Azure                     | Azure Storage Account Key                           |
+| Clojars                   | Clojars Deploy Token                                |
+| CloudBees CodeShip        | CloudBees CodeShip Credential                       |
+| Databricks                | Databricks Access Token                             |
+| Datadog                   | Datadog API Key                                     |
+| Discord                   | Discord Bot Token                                   |
+| Doppler                   | Doppler Personal Token                              |
+| Doppler                   | Doppler Service Token                               |
+| Doppler                   | Doppler CLI Token                                   |
+| Doppler                   | Doppler SCIM Token                                  |
+| Dropbox                   | Dropbox Access Token                                |
+| Dropbox                   | Dropbox Short Lived Access Token                    |
+| Dynatrace                 | Dynatrace Access Token                              |
+| Dynatrace                 | Dynatrace Internal Token                            |
+| Finicity                  | Finicity App Key                                    |
+| Frame.io                  | Frame.io JSON Web Token                             |
+| Frame.io                  | Frame.io Developer Token                            |
+| GitHub                    | GitHub個人アクセストークン                                    |
+| GitHub                    | GitHub OAuthアクセストークン                                |
+| GitHub                    | GitHub Refreshトークン                                  |
+| GitHub                    | GitHubアプリケーションインストールアクセストークン                        |
+| GitHub                    | GitHub SSH秘密鍵                                       |
+| GoCardless                | GoCardless Live Access Token                        |
+| GoCardless                | GoCardless Sandbox Access Token                     |
+| Google Cloud              | Google API Key                                      |
+| Google Cloud              | Google Cloud Private Key ID                         |
+| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token              |
+| Hubspot                   | Hubspot API Key                                     |
+| Mailchimp                 | Mailchimp API Key                                   |
+| Mailchimp                 | Mandrill API Key                                    |
+| Mailgun                   | Mailgun API Key                                     |
+| MessageBird               | MessageBird API Key                                 |
+| npm                       | npm Access Token                                    |
+| NuGet                     | NuGet API Key                                       |
+| OpenAI                    | OpenAI API Key                                      |
+| Palantir                  | Palantir JSON Web Token                             |
+| Plivo                     | Plivo Auth Token                                    |
+| Postman                   | Postman API Key                                     |
+| Proctorio                 | Proctorio Consumer Key                              |
+| Proctorio                 | Proctorio Linkage Key                               |
+| Proctorio                 | Proctorio Registration Key                          |
+| Proctorio                 | Proctorio Secret Key                                |
+| Pulumi                    | Pulumi Access Token                                 |
+| PyPI                      | PyPI API Token                                      |
+| RubyGems                  | RubyGems API Key                                    |
+| Samsara                   | Samsara API Token                                   |
+| Samsara                   | Samsara OAuth Access Token                          |
+| SendGrid                  | SendGrid API Key                                    |
+| Shopify                   | Shopify App Shared Secret                           |
+| Shopify                   | Shopify Access Token                                |
+| Shopify                   | Shopify Custom App Access Token                     |
+| Shopify                   | Shopify Private App Password                        |
+| Slack                     | Slack API Token                                     |
+| Slack                     | Slack Incoming Webhook URL                          |
+| Slack                     | Slack Workflow Webhook URL                          |
+| SSLMate                   | SSLMate API Key                                     |
+| SSLMate                   | SSLMate Cluster Secret                              |
+| Stripe                    | Stripe Live API Secret Key                          |
+| Stripe                    | Stripe Test API Secret Key                          |
+| Stripe                    | Stripe Live API Restricted Key                      |
+| Stripe                    | Stripe Test API Restricted Key                      |
+| Tencent Cloud             | Tencent Cloud Secret ID                             |
+| Twilio                    | Twilio Account String Identifier                    |
+| Twilio                    | Twilio API Key                                      |
diff --git a/translations/ja-JP/data/reusables/security-advisory/disclosing-vulnerabilities.md b/translations/ja-JP/data/reusables/security-advisory/disclosing-vulnerabilities.md
index 27c28d714c..301f71caf9 100644
--- a/translations/ja-JP/data/reusables/security-advisory/disclosing-vulnerabilities.md
+++ b/translations/ja-JP/data/reusables/security-advisory/disclosing-vulnerabilities.md
@@ -1 +1 @@
-Vulnerability disclosure is an area where collaboration between vulnerability reporters, such as security researchers, and project maintainers is very important. Both parties need to work together from the moment a potentially harmful security vulnerability is found, right until a vulnerability is disclosed to the world, ideally with a patch available. Typically, when someone lets a maintainer know privately about a security vulnerability, the maintainer develops a fix, validates it, and notifies the users of the project or package.
+脆弱性の開示は、セキュリティの研究者などの脆弱性の報告者とプロジェクトのメンテナとの間の協力が非常に重要な分野です。 潜在的に有害なセキュリティの脆弱性が見つかったときから、脆弱性が世界に向けて公開され、理想的にはパッチが利用可能になるまで、どちらも協力しあって作業しなければなりません。 通常は、誰かがメンテナに対してセキュリティの脆弱性について個人的に知らせると、メンテナはパッチを開発し、検証し、プロジェクトあるいはパッケージのユーザに通知します。
diff --git a/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..a2073d68d4
--- /dev/null
+++ b/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" %}詳しい情報については「[{% data variables.product.prodname_advisory_database %}でのセキュリティ脆弱性を参照する](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)」及び「[{% data variables.product.prodname_security_advisories %}について](/code-security/security-advisories/about-github-security-advisories)」を参照してください。
+{% else %}アドバイザリデータに関する詳しい情報については、「<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する</a>」を参照してください。
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md b/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md
index a2dc799e0b..fbcbec7ea1 100644
--- a/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md
+++ b/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md
@@ -1 +1 @@
-{% data variables.product.prodname_security_advisories %} allow repository maintainers to privately discuss and fix a security vulnerability in a project. リポジトリメンテナは、修正に協力した後、セキュリティアドバイザリを公開して、プロジェクトのコミュニティにセキュリティの脆弱性を公開します。 リポジトリメンテナは、セキュリティアドバイザリを公開することで、コミュニティがパッケージの依存関係を更新し、セキュリティの脆弱性の影響を調査しやすくなります。
\ No newline at end of file
+{% data variables.product.prodname_security_advisories %} を使用すると、リポジトリメンテナがプロジェクトのセキュリティの脆弱性について非公開で議論し、修正できます。 リポジトリメンテナは、修正に協力した後、セキュリティアドバイザリを公開して、プロジェクトのコミュニティにセキュリティの脆弱性を公開します。 リポジトリメンテナは、セキュリティアドバイザリを公開することで、コミュニティがパッケージの依存関係を更新し、セキュリティの脆弱性の影響を調査しやすくなります。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md b/translations/ja-JP/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md
index cb1b6b59bf..2b7287534a 100644
--- a/translations/ja-JP/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md
+++ b/translations/ja-JP/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** If you are a security researcher, you should directly contact maintainers to ask them to create security advisories or issue CVEs on your behalf in repositories that you don't administer.
+**ノート:** セキュリティの研究者は、管理していないリポジトリでは自分の代わりにセキュリティアドバイザリあるいはIssueを作成してもらうよう、メンテナに直接連絡すべきです。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/security-center/beta.md b/translations/ja-JP/data/reusables/security-center/beta.md
index e0074292ba..11d6285ac1 100644
--- a/translations/ja-JP/data/reusables/security-center/beta.md
+++ b/translations/ja-JP/data/reusables/security-center/beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** The security overview is currently in beta and subject to change.
+**ノート：** セキュリティの概要は現在ベータで、変更されることがあります。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/security/displayed-information.md b/translations/ja-JP/data/reusables/security/displayed-information.md
index 02f38c36db..73e96ab1d9 100644
--- a/translations/ja-JP/data/reusables/security/displayed-information.md
+++ b/translations/ja-JP/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
-When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
+既存のリポジトリで1つ以上のセキュリティ及び分析機能を有効化すると、数分のうちに{% data variables.product.prodname_dotcom %}上に結果が表示されます。
 
-- All the existing repositories will have the selected configuration.
-- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- We use the permissions to scan for manifest files to apply the relevant services.
-- You'll see information on your dependency graph.
-- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} and raise pull requests{% endif %}. 
+- 既存のすべてのリポジトリは、選択された設定を持ちます。
+- 新しいリポジトリは、新しいリポジトリのチェックボックスを有効にしていれば、選択された設定に従います。{% if currentVersion == "free-pro-team@latest" %}
+- 関連するサービスに適用するマニフェストファイルをスキャンするために権限を使用します。
+- 依存関係グラフ上に情報が表示されます。
+- {% data variables.product.prodname_dotcom %}は、{% data variables.product.prodname_dependabot_alerts %}を生成します。 そして、Pull Requestを作成します。{% endif %} 
diff --git a/translations/ja-JP/data/reusables/security/security-and-analysis-features-enable-read-only.md b/translations/ja-JP/data/reusables/security/security-and-analysis-features-enable-read-only.md
index ff3b3d7360..8caed947ab 100644
--- a/translations/ja-JP/data/reusables/security/security-and-analysis-features-enable-read-only.md
+++ b/translations/ja-JP/data/reusables/security/security-and-analysis-features-enable-read-only.md
@@ -1,4 +1,4 @@
 {% if currentVersion == "free-pro-team@latest" %}
-If you enable security and analysis features,
-{% data variables.product.company_short %} performs read-only analysis on your repository. 詳しい情報については、「[{% data variables.product.company_short %} によるデータ使用について](/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data)」を参照してください。
+セキュリティと分析の機能を有効化すると、
+{% data variables.product.company_short %}はリポジトリ上で読み取りのみの分析を行います。 詳しい情報については、「[{% data variables.product.company_short %} によるデータ使用について](/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/shortdesc/authenticating_github_app.md b/translations/ja-JP/data/reusables/shortdesc/authenticating_github_app.md
index 2bd7cd6418..057af1adf5 100644
--- a/translations/ja-JP/data/reusables/shortdesc/authenticating_github_app.md
+++ b/translations/ja-JP/data/reusables/shortdesc/authenticating_github_app.md
@@ -1 +1 @@
-For information on how to authenticate as a GitHub App, see "[Authentication Options for GitHub Apps](/apps/building-github-apps/authentication-options-for-github-apps#authenticating-as-a-github-app)."
+GitHub Appとして認証を受ける方法については「[GitHub Appのための認証オプション](/apps/building-github-apps/authentication-options-for-github-apps#authenticating-as-a-github-app)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/shortdesc/authenticating_with_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/authenticating_with_github_apps.md
index 8e70dfde22..9e42fbf116 100644
--- a/translations/ja-JP/data/reusables/shortdesc/authenticating_with_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/authenticating_with_github_apps.md
@@ -1 +1 @@
-You can authenticate as a {% data variables.product.prodname_github_app %} or as an installation.
+{% data variables.product.prodname_github_app %}として、あるいはインストールとして認証を受けることができます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/authorizing_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/authorizing_oauth_apps.md
index 09e76d7eae..3e5ef60580 100644
--- a/translations/ja-JP/data/reusables/shortdesc/authorizing_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/authorizing_oauth_apps.md
@@ -1 +1 @@
-You can enable other users to authorize your OAuth App.
+他のユーザがOAuthアプリケーションを認可できるようにすることができます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_github_apps.md
index b988f3ab5c..93d9876bb1 100644
--- a/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_github_apps.md
@@ -1 +1 @@
-You can replace the default badge on your GitHub App by uploading your own logo image and customizing the background.
+独自のロゴ画像をアップロードし、背景をカスタマイズすることによって、GitHub Appのデフォルトのバッジを置き換えられます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md
index f2c602b885..7d05966d19 100644
--- a/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md
@@ -1 +1 @@
-You can replace the default badge on your OAuth App by uploading your own logo image and customizing the background.
+独自のロゴ画像をアップロードし、背景をカスタマイズすることによって、OAuth Appのデフォルトのバッジを置き換えられます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/creating_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/creating_github_apps.md
index a9b51d1a03..77c9447840 100644
--- a/translations/ja-JP/data/reusables/shortdesc/creating_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/creating_github_apps.md
@@ -1 +1 @@
-You can create and register a GitHub App under your personal account or under any organization you have administrative access to.
+個人アカウントの下で、あるいは管理アクセス権を持っているOrganizationの下で、GitHub Appを作成し、登録できます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/creating_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/creating_oauth_apps.md
index 16fc041009..22573044e5 100644
--- a/translations/ja-JP/data/reusables/shortdesc/creating_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/creating_oauth_apps.md
@@ -1 +1 @@
-You can create and register an OAuth App under your personal account or under any organization you have administrative access to. While creating your OAuth app, remember to protect your privacy by only using information you consider public.
+個人アカウントの下で、あるいは管理アクセス権を持っているOrganizationの下で、OAuth Appを作成し、登録できます。 OAuth Appを作成する際には、公開してもよいと考える情報だけを使うことで、プライバシーを保護することを忘れないようにしてください。
diff --git a/translations/ja-JP/data/reusables/shortdesc/deleting_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/deleting_github_apps.md
index fcc568a45b..cf99110763 100644
--- a/translations/ja-JP/data/reusables/shortdesc/deleting_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/deleting_github_apps.md
@@ -1 +1 @@
-You can delete GitHub Apps when you no longer use them.
+もう使わなくなったGitHub Appは削除できます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/deleting_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/deleting_oauth_apps.md
index 61efb0b055..b2de067159 100644
--- a/translations/ja-JP/data/reusables/shortdesc/deleting_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/deleting_oauth_apps.md
@@ -1 +1 @@
-You can delete OAuth Apps when you no longer use them.
+もう使わなくなったOAuth Appは削除できます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/editing_permissions_for_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/editing_permissions_for_github_apps.md
index e8c900f1e4..f048ecf84c 100644
--- a/translations/ja-JP/data/reusables/shortdesc/editing_permissions_for_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/editing_permissions_for_github_apps.md
@@ -1 +1 @@
-After registering a GitHub App, you can modify your app's permissions.
+GitHub Appを登録した後に、アプリケーションの権限を変更できます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md
index 8753f972a4..b0dd78757d 100644
--- a/translations/ja-JP/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md
@@ -1 +1 @@
-Your GitHub App can perform actions on behalf of a user, like creating an issue, creating a deployment, and using other supported endpoints.
+GitHub Appは、Issueの作成、デプロイメントの作成、サポートされている他のエンドポイントの利用など、アクションをユーザの代わりに行うことができます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/making-a-github-app-public-or-private.md b/translations/ja-JP/data/reusables/shortdesc/making-a-github-app-public-or-private.md
index b715bb3db7..1d7d04d11b 100644
--- a/translations/ja-JP/data/reusables/shortdesc/making-a-github-app-public-or-private.md
+++ b/translations/ja-JP/data/reusables/shortdesc/making-a-github-app-public-or-private.md
@@ -1 +1 @@
-When setting up a GitHub App, you can make its installation public so any GitHub user or organization can install the app, or private so you can only install it on the account that created it.
+GitHub Appをセットアップする際に、そのインストールをパブリックにして、任意のGitHubユーザあるいはOrganizationがそのアプリケーションをインストールできるようにすることもできます。あるいはプライベートにして、アプリケーションを作成したアカウントにだけインストールできるようにすることもできます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/modifying_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/modifying_github_apps.md
index 9986f7af61..8c38a01ce7 100644
--- a/translations/ja-JP/data/reusables/shortdesc/modifying_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/modifying_github_apps.md
@@ -1 +1 @@
-After creating a GitHub App, you can make changes to it.
+GitHub Appを作成した後に、変更を加えることができます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/modifying_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/modifying_oauth_apps.md
index 85907ba04e..6353f8d120 100644
--- a/translations/ja-JP/data/reusables/shortdesc/modifying_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/modifying_oauth_apps.md
@@ -1 +1 @@
-After creating and registering an OAuth App, you can make changes to it.
+OAuth Appを作成して登録した後に、変更を加えることができます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/permissions_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/permissions_github_apps.md
index fe03198b1a..b12bd562f6 100644
--- a/translations/ja-JP/data/reusables/shortdesc/permissions_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/permissions_github_apps.md
@@ -1 +1 @@
-When you create a GitHub App, you set the permissions that define the resources the app can access via the REST API.
+GitHub Appを作成する際に、REST APIを通じてそのアプリケーションがアクセスできるリソースを決定する権限を設定します。
diff --git a/translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md
index bcba4f706a..c67f169b80 100644
--- a/translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md
@@ -1 +1 @@
-Rate limits for GitHub Apps help control the rate of traffic.
+GitHub Appのレート制限は、トラフィックのレートを制御するための役に立ちます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/suspending_a_github_app.md b/translations/ja-JP/data/reusables/shortdesc/suspending_a_github_app.md
index 4f8e977217..13eed9406e 100644
--- a/translations/ja-JP/data/reusables/shortdesc/suspending_a_github_app.md
+++ b/translations/ja-JP/data/reusables/shortdesc/suspending_a_github_app.md
@@ -1 +1 @@
-You can temporarily block a {% data variables.product.prodname_github_app %}'s access to your account's resources by suspending the app.
+アプリケーションをサスペンドすることによって、{% data variables.product.prodname_github_app %}からのあなたのアカウントのリソースへのアクセスを一時的にブロックできます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_github_apps.md b/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_github_apps.md
index b8693c9278..1b22ba6008 100644
--- a/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_github_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_github_apps.md
@@ -1 +1 @@
-You can transfer ownership of a GitHub App to another user or organization.
+GitHub Appの所有権は、他のユーザもしくはOrganizationに移譲できます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md
index 4648045047..68e94e4143 100644
--- a/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md
@@ -1 +1 @@
-You can transfer ownership of an OAuth App to another user or organization.
+OAuth Appの所有権は、他のユーザもしくはOrganizationに移譲できます。
diff --git a/translations/ja-JP/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md
index ab1aaac67e..65fa644b37 100644
--- a/translations/ja-JP/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md
@@ -1 +1 @@
-When exchanging a code for an access token, there are an additional set of errors that can occur. The format of these responses is determined by the accept header you pass.
+アクセストークンのコードを交換する場合、発生しうるエラーが増えます。 これらのレスポンスのフォーマットは、渡したacceptヘッダによって決まります。
diff --git a/translations/ja-JP/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md
index fb7ef66aad..8731a797fa 100644
--- a/translations/ja-JP/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md
@@ -1 +1 @@
-When obtaining an OAuth token for a user, some errors may occur during the initial authorization request phase.
+ユーザのOAuthトークンを取得する場合、初期の認可リクエストのフェーズでエラーが生じることがあります。
diff --git a/translations/ja-JP/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md b/translations/ja-JP/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md
index 477fc8cb9e..e14914a6b9 100644
--- a/translations/ja-JP/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md
+++ b/translations/ja-JP/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md
@@ -1 +1 @@
-Scopes let you specify exactly what type of access you need. Scopes _limit_ access for OAuth tokens. They do not grant any additional permission beyond that which the user already has.
+スコープによって、必要なアクセスの種類を正確に指定できます。 スコープは、OAuthトークンのアクセスを_制限_します。 ユーザがすでに持っている範囲を超えた権限を許可することはありません。
diff --git a/translations/ja-JP/data/reusables/sponsors/billing-switcher.md b/translations/ja-JP/data/reusables/sponsors/billing-switcher.md
index 4831c34a3b..71f51b20ee 100644
--- a/translations/ja-JP/data/reusables/sponsors/billing-switcher.md
+++ b/translations/ja-JP/data/reusables/sponsors/billing-switcher.md
@@ -1 +1 @@
-1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png)
+1. あるいは、Organizationの代わりにスポンサーシップを管理するために、左上の**Personal settings（個人設定）**ドロップダウンメニューを使い、Organizationをクリックしてください。 ![設定のアカウントを切り替えるためのドロップダウンメニュー](/assets/images/help/sponsors/billing-account-switcher.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/change-tier.md b/translations/ja-JP/data/reusables/sponsors/change-tier.md
index 07f7c9cafa..c889d8a142 100644
--- a/translations/ja-JP/data/reusables/sponsors/change-tier.md
+++ b/translations/ja-JP/data/reusables/sponsors/change-tier.md
@@ -1 +1 @@
-1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![層の変更ボタン](/assets/images/help/billing/edit-sponsor-billing.png)
+1. "{% data variables.product.prodname_sponsors %}"の下で、スポンサードアカウントの右のあなたの層の額の隣にある{% octicon "triangle-down" aria-label="The down triangle octicon" %}をクリックし、**Change tier（層の変更）**をクリックしてください。 ![層の変更ボタン](/assets/images/help/billing/edit-sponsor-billing.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/choose-updates.md b/translations/ja-JP/data/reusables/sponsors/choose-updates.md
index 93f8807013..5521a0626c 100644
--- a/translations/ja-JP/data/reusables/sponsors/choose-updates.md
+++ b/translations/ja-JP/data/reusables/sponsors/choose-updates.md
@@ -1 +1 @@
-4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png)
+4. スポンサードアカウントからのメールによる更新を受信するかを決定し、"Receive email updates from _ACCOUNT_（アカウントからのメール更新を受信する）"を選択もしくは選択解除してください。 ![スポンサードアカウントからの更新を受け取るためのチェックボックス](/assets/images/help/sponsors/updates-checkbox-manage.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/click-add-tier.md b/translations/ja-JP/data/reusables/sponsors/click-add-tier.md
index 8ee0602d01..9eddd044c3 100644
--- a/translations/ja-JP/data/reusables/sponsors/click-add-tier.md
+++ b/translations/ja-JP/data/reusables/sponsors/click-add-tier.md
@@ -1 +1 @@
-1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![層の追加ボタン](/assets/images/help/sponsors/add-a-tier-button.png)
+1. 月次の層を作成するには、ページの右側の**Add a monthly tier（月次の層の追加）**をクリックしてください。 あるいは、一回払いの層を作成するには、**One-time tiers（一回の層）**をクリックし、続いて**Add a one-time tier（一回の層の追加）**をクリックしてください。 ![層の追加ボタン](/assets/images/help/sponsors/add-a-tier-button.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md b/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md
index 1889367cb9..6ec452a525 100644
--- a/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md
+++ b/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md
@@ -1,2 +1,2 @@
-1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png)
-1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png)
+1. 少なくとも1つの層を持っているなら、カスタムの金額を有効化するオプションが月額及び1回の層の上に表示されます。 スポンサーが支払い額を設定できるようにしたいなら、**Enable custom amounts（カスタムの額を有効化）**を選択してください。 ![カスタムの額の有効化](/assets/images/help/sponsors/enable-custom-amounts.png)
+1. あるいは、カスタムの額を有効化した場合、カスタムの層に対して表示されるデフォルトの金額を設定できます。 ドルの全体の金額を指定し、**Set default amount（デフォルトの金額を設定）**をクリックしてください。 ![デフォルトの金額を設定](/assets/images/help/sponsors/set-default-amount.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/feedback.md b/translations/ja-JP/data/reusables/sponsors/feedback.md
index b358580842..8a580050a8 100644
--- a/translations/ja-JP/data/reusables/sponsors/feedback.md
+++ b/translations/ja-JP/data/reusables/sponsors/feedback.md
@@ -1 +1 @@
-{% data variables.product.prodname_sponsors %} に関するフィードバックを {% data variables.product.company_short %} と共有できます。 To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)."
+{% data variables.product.prodname_sponsors %} に関するフィードバックを {% data variables.product.company_short %} と共有できます。 会話に参加するには、「[スポンサーのフィードバック](https://github.com/github/feedback/discussions/categories/sponsors-feedback)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md b/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md
index 125d4020ad..f32e5a1eab 100644
--- a/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md
+++ b/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md
@@ -1 +1 @@
-1. To the right of your current tier, click **Manage**. ![スポンサーシップの管理ボタン](/assets/images/help/sponsors/manage-your-sponsorship-button.png)
\ No newline at end of file
+1. 現在の層の右で**Manage（管理）**をクリックしてください。 ![スポンサーシップの管理ボタン](/assets/images/help/sponsors/manage-your-sponsorship-button.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md
index b47ac0599d..4b4a422e7f 100644
--- a/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md
+++ b/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md
@@ -1 +1 @@
-You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)."
+Organizationがスポンサーするアカウントからの更新を受信するメールアドレスを指定できます。 詳しい情報については「[Organizationがスポンサーするアカウントからの更新の管理](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/sponsors/matching-fund-eligible.md b/translations/ja-JP/data/reusables/sponsors/matching-fund-eligible.md
index 0f4d492bcf..65ee219ea5 100644
--- a/translations/ja-JP/data/reusables/sponsors/matching-fund-eligible.md
+++ b/translations/ja-JP/data/reusables/sponsors/matching-fund-eligible.md
@@ -1 +1 @@
-Eligibility for the {% data variables.product.prodname_matching_fund %} has passed. Applications received after the January 1, 2020 deadline are not eligible for {% data variables.product.prodname_matching_fund %}.
+{% data variables.product.prodname_matching_fund %}の適格性にパスしました。 2020年1月1日の締め切り以降に受付された申請は、{% data variables.product.prodname_matching_fund %}の対象外になります。
diff --git a/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md
index def70f43f1..df7c206281 100644
--- a/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md
+++ b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md
@@ -1 +1 @@
-1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile.
+1. {% data variables.product.product_name %}で、スポンサードアカウントのプロフィールにアクセスしてください。
diff --git a/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
index 7a4eaac3c6..9ebe4d6211 100644
--- a/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
+++ b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
@@ -1,2 +1,2 @@
 1. 任意のページの右上隅で、プロフィール画像をクリックし、続いて [**{% data variables.product.prodname_sponsors %}**] をクリックします。 ![{% data variables.product.prodname_sponsors %}ボタン](/assets/images/help/sponsors/access-github-sponsors-dashboard.png)
-2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![開発者スポンサーダッシュボードボタン](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png)
+2. スポンサー付きの適格なアカウントのリストが表示されているなら、管理したいアカウントの右で**Dashboard（ダッシュボード）**をクリックしてください。 ![開発者スポンサーダッシュボードボタン](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/no-fees.md b/translations/ja-JP/data/reusables/sponsors/no-fees.md
index ea983ae36d..11f2ade316 100644
--- a/translations/ja-JP/data/reusables/sponsors/no-fees.md
+++ b/translations/ja-JP/data/reusables/sponsors/no-fees.md
@@ -1 +1 @@
-{% data variables.product.prodname_sponsors %}はユーザアカウントからスポンサーシップの費用を請求しないので、これらのスポンサーシップの100%がスポンサー付きの開発者あるいはOrganizationに渡ります。 The 10% fee for sponsorships from organizations is waived during the beta.
+{% data variables.product.prodname_sponsors %}はユーザアカウントからスポンサーシップの費用を請求しないので、これらのスポンサーシップの100%がスポンサー付きの開発者あるいはOrganizationに渡ります。 ベータの期間中、このOrganizationからのスポンサーシップの10%は免除されます。
diff --git a/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md
index 75983073a4..e92efe5538 100644
--- a/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md
+++ b/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change.
+**ノート:** Organizationに代わってのスポンサーは現在ベータで、変更されることがあります。
 
 {% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md b/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md
index 32f6b098f7..0ea95f890a 100644
--- a/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md
+++ b/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md
@@ -1 +1 @@
-1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png)
\ No newline at end of file
+1. あるいは、Organizationとしてスポンサーをしている場合、完全な月額の支払いを行う代わりに日割りの額を支払うには、"Total due now（すぐに全額）"の下で、**Pay prorated $X.XX instead（代わりに日割りの$X.XXを支払う）**をクリックしてください。 ![日割りの額を支払うためのリンク](/assets/images/help/sponsors/pay-prorated-amount-link.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md b/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md
index 9e560bf708..bef4f6a4ca 100644
--- a/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md
+++ b/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md
@@ -1 +1 @@
-If you're starting a monthly sponsorship on behalf of your user account, you'll immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment.
+自分のユーザアカウントに代わって月額のスポンサーシップを開始すると、次回の通常の支払日までの日割りの額がすぐに請求されます。 Organizationに代わってスポンサーを行っている場合、日割りの額を支払うか、月額全体を支払うかを選択できます。
diff --git a/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md b/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md
index a84fd2930a..78786933ec 100644
--- a/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md
+++ b/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md
@@ -1 +1 @@
-1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png)
+1. 層の確認をしてから、**Publish _TYPE_ tier（種類層の公開）**をクリックしてください。 ![月額層の公開ボタン](/assets/images/help/sponsors/publish-tier-button.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md b/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md
index 523a2c0a96..bb6a2fcde9 100644
--- a/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md
+++ b/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md
@@ -1 +1 @@
-1. ページの右側で、"Select a tire（層の選択）"の下で利用可能なスポンサーシップ層をレビューしてください。 If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png)
+1. ページの右側で、"Select a tire（層の選択）"の下で利用可能なスポンサーシップ層をレビューしてください。 複数の種類の層が利用可能で"Monthly（月額）"層が表示されているなら、**One-time（1回）**をクリックして、1回払いの層を表示させてください。 !["1回"の層を表示](/assets/images/help/sponsors/show-one-time-tiers.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/select-a-tier.md b/translations/ja-JP/data/reusables/sponsors/select-a-tier.md
index 1da5bab143..aa3ee14da4 100644
--- a/translations/ja-JP/data/reusables/sponsors/select-a-tier.md
+++ b/translations/ja-JP/data/reusables/sponsors/select-a-tier.md
@@ -1 +1 @@
-1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![層の選択ボックス](/assets/images/help/sponsors/select-a-tier-box.png)
+1. 選択したい層の右で**Select（選択）**をクリックしてください。 カスタムの額を選択したい場合には、"Select（選択）"をクリックする前に、スポンサーシップの金額を入力してください。 ![層の選択ボックス](/assets/images/help/sponsors/select-a-tier-box.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/sponsor-account.md b/translations/ja-JP/data/reusables/sponsors/sponsor-account.md
index 28ea6f4fa5..0457b8e5a2 100644
--- a/translations/ja-JP/data/reusables/sponsors/sponsor-account.md
+++ b/translations/ja-JP/data/reusables/sponsors/sponsor-account.md
@@ -1 +1 @@
-1. Click **Sponsor _ACCOUNT_**. ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-developer-button.png)
\ No newline at end of file
+1. **Sponsor _ACCOUNT_（スポンサーアカウント）**をクリックしてください。 ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-developer-button.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md b/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md
index 15390e887d..cf6216249d 100644
--- a/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md
+++ b/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md
@@ -1,4 +1,4 @@
 1. アカウントのスポンサーシップダッシュボードに移動します。
-   - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![スポンサーをするボタン](/assets/images/help/profile/sponsoring-button.png)
-   -  If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![スポンサーをするボタン](/assets/images/help/sponsors/org-sponsoring-button.png)
-1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png)
+   - ユーザアカウントをスポンサーする場合は、ユーザ名の下で**Sponsorring（スポンサー）**をクリックしてください。 ![スポンサーをするボタン](/assets/images/help/profile/sponsoring-button.png)
+   -  Organizationをスポンサーする場合には、Organization名の右で**Sponsoring（スポンサー）**をクリックしてください。 ![スポンサーをするボタン](/assets/images/help/sponsors/org-sponsoring-button.png)
+1. あるいは、Organizationの代わりにスポンサーシップを管理するには、ページの右側で**Sponsoring as（スポンサーを行う）**ドロップダウンメニューを使い、そのOrganizationをクリックしてください。 ![スポンサーとしてのアカウントを選択するドロップダウンメニュー](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png)
diff --git a/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md b/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md
index 1b1f4699d5..3242f34d1e 100644
--- a/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md
+++ b/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md
@@ -1 +1 @@
-You can sponsor anyone with a sponsored developer profile or sponsored organization profile on behalf of your user account or an organization. You can choose from multiple sponsorship tiers, with one-time or monthly payment amounts and benefits that are set by the sponsored account. スポンサーシップは、既存の支払日、支払い方法、領収書を共有します。
+スポンサード開発者プロフィールもしくはスポンサードOrganizationプロフィールがある対象者は、自分のユーザアカウントもしくはOrganizationに代わってスポンサーできます。 スポンサードアカウントが設定した1回あるいは月次の支払い額やメリットを持つ複数のスポンサーシップ層から選択することができます。 スポンサーシップは、既存の支払日、支払い方法、領収書を共有します。
diff --git a/translations/ja-JP/data/reusables/sponsors/tier-details.md b/translations/ja-JP/data/reusables/sponsors/tier-details.md
index 48ce54ab0e..666a918589 100644
--- a/translations/ja-JP/data/reusables/sponsors/tier-details.md
+++ b/translations/ja-JP/data/reusables/sponsors/tier-details.md
@@ -1,3 +1,3 @@
-スポンサーが選択できる層として、最大で10個のスポンサーシップ層を作成できます。 Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time).
+スポンサーが選択できる層として、最大で10個のスポンサーシップ層を作成できます。 各層にはそれぞれの米ドルでの月額もしくは1回の額と、新バージョンへの早期アクセスやプロジェクトのREADMEで取り上げられたりするといったメリットがあります。 加えて、カスタムの額（月額及び1回）の層の有効化を選択することもできます。
 
-Once you have published a tier, you can't edit the price of that tier. その代わりに、その層を止めて新しい層を作成できます。 Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires.
+層を公開すると、その層の金額は編集できなくなります。 その代わりに、その層を止めて新しい層を作成できます。 終了した層の既存のスポンサーは、スポンサーシップの層を変更するか、スポンサーシップをキャンセルするか、1回のスポンサーシップの期間が終了するまで、そのまま残ります。
diff --git a/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-developer.md b/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-developer.md
index 1503c52567..22d9db64f5 100644
--- a/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-developer.md
+++ b/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-developer.md
@@ -1 +1 @@
-Anyone who contributes to an open source project and lives in a supported region is eligible to become a sponsored developer. コントリビューションにはバグレポート、Issueのトリアージ、コード、ドキュメンテーション、リーダーシップ、ビジネス開発、プロジェクト管理、メンターシップ、設計などがありますが、これだけに限定されません。 {% data variables.product.prodname_sponsors %}にまだサポートされていない地域に住んでいる場合、{% data variables.product.prodname_sponsors %}のベータへの参加の待ちリストにサインアップできます。
+オープンソースプロジェクトにコントリビュートし、サポートされている地域に居住している人は、スポンサード開発者になることができます。 コントリビューションにはバグレポート、Issueのトリアージ、コード、ドキュメンテーション、リーダーシップ、ビジネス開発、プロジェクト管理、メンターシップ、設計などがありますが、これだけに限定されません。 {% data variables.product.prodname_sponsors %}にまだサポートされていない地域に住んでいる場合、{% data variables.product.prodname_sponsors %}のベータへの参加の待ちリストにサインアップできます。
diff --git a/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-organization.md b/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-organization.md
index 8b1a3ed050..2ddac9b940 100644
--- a/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-organization.md
+++ b/translations/ja-JP/data/reusables/sponsors/you-can-be-a-sponsored-organization.md
@@ -1 +1 @@
-Any organization that contributes to an open source project and legally operates in a supported region is eligible to become a sponsored organization. If your organization operates in a region that isn't already supported by {% data variables.product.prodname_sponsors %}, join the waitlist at [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors).
+オープンソースプロジェクトにコントリビュートし、サポートされている地域で法的に活動しているOrganizationは、スポンサードOrganizationになることができます。 Organizationが{% data variables.product.prodname_sponsors %}にまだサポートされていない地域で活動している場合は、[{% data variables.product.prodname_sponsors %}](https://github.com/sponsors)の待ちリストに加わってください。
diff --git a/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md
index fb1ca5ec34..6c0a9c55cb 100644
--- a/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md
+++ b/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md
@@ -1 +1 @@
-If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_ed25519* in the command with the name of your private key file.
+キーを別の名前で作成したか、別の名前を持つ既存のキーを追加しようとしている場合は、コマンド内の*id_ed25519*を秘密鍵ファイルの名前で置き換えてください。
diff --git a/translations/ja-JP/data/reusables/ssh/dsa-support.md b/translations/ja-JP/data/reusables/ssh/dsa-support.md
index e75e3cecd2..3b87851c21 100644
--- a/translations/ja-JP/data/reusables/ssh/dsa-support.md
+++ b/translations/ja-JP/data/reusables/ssh/dsa-support.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** DSA keys (SSH-DSS) are no longer supported. 既存のキーは引き続き動作しますが、{% data variables.product.product_name %}アカウントに新しいDSAキーを追加することはできません。
+**ノート:** DSAキー（SSH-DSS）はサポートされなくなりました。 既存のキーは引き続き動作しますが、{% data variables.product.product_name %}アカウントに新しいDSAキーを追加することはできません。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/ja-JP/data/reusables/support/enterprise-resolving-and-closing-tickets.md
index fd4d59fc03..c6316cf195 100644
--- a/translations/ja-JP/data/reusables/support/enterprise-resolving-and-closing-tickets.md
+++ b/translations/ja-JP/data/reusables/support/enterprise-resolving-and-closing-tickets.md
@@ -1,5 +1,5 @@
-{% data variables.contact.enterprise_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, {% if currentVersion == "github-ae@latest" %}or {% endif %} workaround instructions{% if enterpriseServerVersions contains currentVersion %}, or by advising you of an available release that addresses the issue{% endif %}.
+{% data variables.contact.enterprise_support %}は、説明、推薦事項、利用方法の指示、{% if currentVersion == "github-ae@latest" %}あるいは{% endif %}回避策の指示{% if enterpriseServerVersions contains currentVersion %}あるいはその問題に対処している利用可能なリリースのアドバイス{% endif %}の提供を持って、チケットが解決したものと見なすことがあります。
 
 カスタムあるいはサポートされていないプラグイン、モジュール、カスタムコードを使っている場合、{% data variables.contact.enterprise_support %} は問題の解決を試みるに当たってサポートされていないプラグイン、モジュール、コードの削除をお願いすることがあります。 サポートされていないプラグイン、モジュール、カスタムコードが削除されたことで問題が修正された場合、{% data variables.contact.enterprise_support %}はチケットが解決されたと見なすことがあります。
 
-{% data variables.contact.enterprise_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. 反応がなかったことによって{% data variables.contact.enterprise_support %}がチケットをクローズした場合、{% data variables.contact.enterprise_support %}にチケットをサイドオープンするようリクエストできます。
+{% data variables.contact.enterprise_support %}は、チケットがサポートの範囲外の場合、あるいは複数回の連絡に対して返答がいただけなかった場合、チケットをクローズすることがあります。 反応がなかったことによって{% data variables.contact.enterprise_support %}がチケットをクローズした場合、{% data variables.contact.enterprise_support %}にチケットをサイドオープンするようリクエストできます。
diff --git a/translations/ja-JP/data/reusables/support/ghae-priorities.md b/translations/ja-JP/data/reusables/support/ghae-priorities.md
index 6c472bc308..6d323afd84 100644
--- a/translations/ja-JP/data/reusables/support/ghae-priorities.md
+++ b/translations/ja-JP/data/reusables/support/ghae-priorities.md
@@ -1,6 +1,6 @@
-|                                  優先度                                  | 説明                                                                                                                                                                                                                                                                            | サンプル                                                                                                                          |
-|:---------------------------------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %} is inaccessible or failing entirely, and the failure directly impacts the operation of your business.<br/><br/>_After you file a support ticket, reach out to {% data variables.contact.github_support %} via phone._ | <ul><li>すべてのユーザーについて、中核的なGitあるいはWebアプリケーションの機能に影響するエラーもしくは中断</li><li>Severe network or performance degradation for majority of users</li><li>ストレージがフル、もしくは急速に埋まりつつある</li><li>Known security incidents or a breach of access</li></ul>                                                                                                     |
-|  {% data variables.product.support_ticket_priority_high %} - Sev B  | {% data variables.product.product_name %} is failing in a production environment, with limited impact to your business processes, or only affecting certain customers.                                                                                                        | <ul><li>多くのユーザの生産性を引き下げるパフォーマンスの低下</li><li>Reduced redundancy concerns from failures or service degradation</li><li>Production-impacting bugs or errors</li><li>{% data variables.product.product_name %} configuration security concerns</li></ul>                                                                                                     |
-| {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %} is experiencing limited or moderate issues and errors with {% data variables.product.product_name %}, or you have general concerns or questions about the operation of {% data variables.product.product_name %}.                 | <ul><li>Advice on using {% data variables.product.prodname_dotcom %} APIs and features, or questions about integrating business workflows</li><li>Issues with user tools and data collection methods</li><li>アップグレード</li><li>Bug reports, general security questions, or other feature related questions</li> |
-|  {% data variables.product.support_ticket_priority_low %} - Sev D   | {% data variables.product.product_name %} is functioning as expected, however, you have a question or suggestion about {% data variables.product.product_name %} that is not time-sensitive, or does not otherwise block the productivity of your team.                     | <ul><li>Feature requests and product feedback</li><li>General questions on overall configuration or use of {% data variables.product.product_name %}</li><li>Notifying {% data variables.contact.github_support %} of any planned changes</li></ul>                                                                                                     |
+|                                  優先度                                  | 説明                                                                                                                                                                                          | サンプル                                                                                                                          |
+|:---------------------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| {% data variables.product.support_ticket_priority_urgent %} - Sev A | {% data variables.product.product_name %}はアクセスできない、もしくは完全に障害で停止しており、この障害がビジネスの運営に直接影響している。<br/><br/>_サポートチケットを作成した後、電話で{% data variables.contact.github_support %}に連絡してください。_ | <ul><li>すべてのユーザーについて、中核的なGitあるいはWebアプリケーションの機能に影響するエラーもしくは中断</li><li>ユーザーの大多数についての重大なネットワークもしくはパフォーマンスの低下</li><li>ストレージがフル、もしくは急速に埋まりつつある</li><li>既知のセキュリティインシデントもしくはアクセス侵害</li></ul>                                                                                                     |
+|  {% data variables.product.support_ticket_priority_high %} - Sev B  | {% data variables.product.product_name %}がプロダクション環境で障害を起こしており、ビジネスプロセスに限定的な影響があるか、特定の顧客にのみ影響している。                                                                                           | <ul><li>多くのユーザの生産性を引き下げるパフォーマンスの低下</li><li>障害あるいはサービスの劣化による冗長性の減少の懸念</li><li>実働環境に影響するバグもしくはエラー</li><li>{% data variables.product.product_name %}の設定のセキュリティに関する懸念</li></ul>                                                                                                     |
+| {% data variables.product.support_ticket_priority_normal %} - Sev C | {% data variables.product.product_name %}で限定的あるいは中程度の問題や{% data variables.product.product_name %}でエラーが生じている。あるいは、{% data variables.product.product_name %}の運用に関する一般的な懸念や疑問がある。            | <ul><li>{% data variables.product.prodname_dotcom %}のAPI及び機能の利用方法についてのアドバイス、あるいはビジネスワークフローのインテグレーションに関する疑問</li><li>ユーザツールやデータ収集方法に関する問題</li><li>アップグレード</li><li>バグレポート、一般的なセキュリティの疑問、あるいは他の機能に関連する疑問</li> |
+|  {% data variables.product.support_ticket_priority_low %} - Sev D   | {% data variables.product.product_name %}は期待どおりに機能しているが、期限が重要ではない、あるいはチームの生産性を妨げたりはしない{% data variables.product.product_name %}に関する疑問あるいは示唆がある。                                           | <ul><li>機能リクエストと製品のフィードバック</li><li>全体的な設定あるいは{% data variables.product.product_name %}の利用に関する一般的な質問</li><li>計画された変更の{% data variables.contact.github_support %}への通知</li></ul>                                                                                                     |
diff --git a/translations/ja-JP/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/ja-JP/data/reusables/support/premium-resolving-and-closing-tickets.md
index 902603dde4..61ce36d24c 100644
--- a/translations/ja-JP/data/reusables/support/premium-resolving-and-closing-tickets.md
+++ b/translations/ja-JP/data/reusables/support/premium-resolving-and-closing-tickets.md
@@ -2,4 +2,4 @@
 
 カスタムあるいはサポートされていないプラグイン、モジュール、カスタムコードを使っている場合、{% data variables.contact.premium_support %} は問題の解決を試みるに当たってサポートされていないプラグイン、モジュール、コードの削除をお願いすることがあります。 サポートされていないプラグイン、モジュール、カスタムコードが削除されたことで問題が修正された場合、{% data variables.contact.premium_support %}はチケットが解決されたと見なすことがあります。
 
-{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. 反応がなかったことによって{% data variables.contact.premium_support %}がチケットをクローズした場合、{% data variables.contact.premium_support %}にチケットをサイドオープンするようリクエストできます。
+{% data variables.contact.premium_support %}は、チケットがサポートのスコープ外の場合、あるいは複数回の連絡に対して回答がなかった場合、チケットをクローズすることがあります。 反応がなかったことによって{% data variables.contact.premium_support %}がチケットをクローズした場合、{% data variables.contact.premium_support %}にチケットをサイドオープンするようリクエストできます。
diff --git a/translations/ja-JP/data/reusables/support/receiving-credits.md b/translations/ja-JP/data/reusables/support/receiving-credits.md
index 87d94e3db9..7d5a6603fd 100644
--- a/translations/ja-JP/data/reusables/support/receiving-credits.md
+++ b/translations/ja-JP/data/reusables/support/receiving-credits.md
@@ -14,6 +14,6 @@
 - **日付** （日付は、遅延が生じた{% data variables.product.company_short %}の会計年度の四半期から30日以内でなければなりません[1月31日、4月30日、7月31日、10月31日]）
 - **顧客の連絡先** （名前とメールアドレスをどちらも指定しなければなりません）
 - **顧客の住所**
-- **Qualifying credits** (You must provide the date of each qualifying credit and the associated ticket number.){% if currentVersion == "free-pro-team@latest" %}
+- **有効なクレジット** （それぞれの有効なクレジットの日付と関連するチケット番号が必要です）{% if currentVersion == "free-pro-team@latest" %}
 - **{% data variables.product.prodname_ghe_cloud %}のOrganization名**{% endif %}
 - **チケット番号**
diff --git a/translations/ja-JP/data/reusables/support/scope-of-support.md b/translations/ja-JP/data/reusables/support/scope-of-support.md
index 375a6444b9..9905c269ae 100644
--- a/translations/ja-JP/data/reusables/support/scope-of-support.md
+++ b/translations/ja-JP/data/reusables/support/scope-of-support.md
@@ -1,7 +1,7 @@
 
 ### サポートのスコープ
 
-サポートリクエストが弊社のチームが支援できるスコープ外だった場合、{% data variables.contact.github_support %}外で問題を解決するための次のステップをおすすめすることがあります。 Your support request is possibly out of {% data variables.contact.github_support %}'s scope if the request is primarily about:
+サポートリクエストが弊社のチームが支援できるスコープ外だった場合、{% data variables.contact.github_support %}外で問題を解決するための次のステップをおすすめすることがあります。 サポートリクエストが主に以下の内容に関するものであれば、おそらく{% data variables.contact.github_support %}のスコープ外になります。
 - サードパーティとのインテグレーション
 - ハードウェアのセットアップ
 - JenkinsのようなCI/CD
diff --git a/translations/ja-JP/data/reusables/supported-languages/C.md b/translations/ja-JP/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/Cpp.md b/translations/ja-JP/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/Cs.md b/translations/ja-JP/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/go.md b/translations/ja-JP/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..40bd61946e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/java.md b/translations/ja-JP/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/javascript.md b/translations/ja-JP/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/php.md b/translations/ja-JP/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/products-table-header.md b/translations/ja-JP/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..105117ec83
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [コードナビゲーション](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依存関係グラフ, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依存関係グラフ, {% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/python.md b/translations/ja-JP/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/ruby.md b/translations/ja-JP/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/scala.md b/translations/ja-JP/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/supported-languages/typescript.md b/translations/ja-JP/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/ja-JP/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/two_fa/about-2fa.md b/translations/ja-JP/data/reusables/two_fa/about-2fa.md
index 704cb699cc..33bf1e7c05 100644
--- a/translations/ja-JP/data/reusables/two_fa/about-2fa.md
+++ b/translations/ja-JP/data/reusables/two_fa/about-2fa.md
@@ -1 +1 @@
-Two-factor authentication (2FA) is an extra layer of security used when logging into websites or apps.
+2 要素認証（2FA） は、Web サイトあるいはアプリケーションにログインする際に使われる追加のセキュリティレイヤーです。
diff --git a/translations/ja-JP/data/reusables/two_fa/after-2fa-add-security-key.md b/translations/ja-JP/data/reusables/two_fa/after-2fa-add-security-key.md
index 46decf91ec..cce86e5653 100644
--- a/translations/ja-JP/data/reusables/two_fa/after-2fa-add-security-key.md
+++ b/translations/ja-JP/data/reusables/two_fa/after-2fa-add-security-key.md
@@ -1 +1 @@
-After you configure 2FA using a mobile app{% if currentVersion == "free-pro-team@latest" %} or via text message{% endif %}, you can add a security key, like a fingerprint reader or Windows Hello. The technology that enables authentication with a security key is called WebAuthn. WebAuthnはU2Fの後継であり、現代的なすべてのブラウザーで動作します。 For more information, see "[WebAuthn](https://webauthn.guide/)" and "[Can I Use](https://caniuse.com/#search=webauthn)."
+モバイルアプリケーションを使い{% if currentVersion == "free-pro-team@latest" %}、あるいはテキストメッセージを通じて{% endif %}2FAを設定した後、指紋リーダーやWindows Helloのようなセキュリティキーを追加できます。 セキュリティキーを使用した認証を可能にする技術は、WebAuthnと呼ばれます。 WebAuthnはU2Fの後継であり、現代的なすべてのブラウザーで動作します。 詳しい情報については「[WebAuthn](https://webauthn.guide/)」及び「[使えますか](https://caniuse.com/#search=webauthn)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md b/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md
index 306c505acf..32d1a7bb26 100644
--- a/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md
+++ b/translations/ja-JP/data/reusables/user-settings/edit_marketplace_listing.md
@@ -1 +1 @@
-5. On the app settings landing page, scroll down to the Marketplace section and click **List in Marketplace**. If you already have a Marketplace draft listing, click **Edit Marketplace listing**. The Marketplace section is only visible if you allowed your app to be installed by any user or organization when registering the app.  For more information, see the list of [Marketplace requirements](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![link to edit your GitHub Marketplace listing](/assets/images/marketplace/marketplace_edit_listing_text.png)
+5. アプリケーション設定のランディングページで、Marketplaceセクションまでスクロールし、**List in Marketplace（Marketplaceでリスト）**をクリックしてください。 すでにMarketplaceのドラフトのリストを持っているなら、**Edit Marketplace listing（Marketplaceのリストの編集）**をクリックしてください。 Marketplaceセクションは、アプリケーションの登録時に任意のユーザあるいはOrganizationによるインストールを許可している場合にのみ表示されます。  詳しい情報については[Marketplaceの要件](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/)のリストを参照してください。 ![GitHub Marketplaceリストの編集リンク](/assets/images/marketplace/marketplace_edit_listing_text.png)
diff --git a/translations/ja-JP/data/reusables/user-settings/github_apps.md b/translations/ja-JP/data/reusables/user-settings/github_apps.md
index 907112a5ec..8bb21973a9 100644
--- a/translations/ja-JP/data/reusables/user-settings/github_apps.md
+++ b/translations/ja-JP/data/reusables/user-settings/github_apps.md
@@ -1 +1 @@
-1. In the left sidebar, click **GitHub Apps**. ![GitHub Apps セクション](/assets/images/settings/github_apps.png)
+1. 左のサイドバーで**GitHub Apps**をクリックしてください。 ![GitHub Apps セクション](/assets/images/settings/github_apps.png)
diff --git a/translations/ja-JP/data/reusables/user-settings/github_apps_advanced.md b/translations/ja-JP/data/reusables/user-settings/github_apps_advanced.md
index 5378aa17dc..ceb0000808 100644
--- a/translations/ja-JP/data/reusables/user-settings/github_apps_advanced.md
+++ b/translations/ja-JP/data/reusables/user-settings/github_apps_advanced.md
@@ -1 +1 @@
-1. In the left sidebar, click **Advanced**. ![Advanced tab](/assets/images/github-apps/github_apps_advanced.png)
+1. 左のサイドバーで** Advanced（高度）**をクリックしてください。 ![高度のタブ](/assets/images/github-apps/github_apps_advanced.png)
diff --git a/translations/ja-JP/data/reusables/user-settings/marketplace_apps.md b/translations/ja-JP/data/reusables/user-settings/marketplace_apps.md
index 11ffb16b03..c1045e08fd 100644
--- a/translations/ja-JP/data/reusables/user-settings/marketplace_apps.md
+++ b/translations/ja-JP/data/reusables/user-settings/marketplace_apps.md
@@ -1,4 +1,4 @@
 {% if currentVersion == "free-pro-team@latest" %}
-1. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the {% data variables.product.prodname_marketplace %} listing you'd like to manage. **Note:** You can also manage your listing by navigating to https://github.com/marketplace/manage. ![アプリケーションの種類の選択](/assets/images/settings/apps_choose_app.png)
+1. 左のサイドバーで、管理したい{% data variables.product.prodname_marketplace %}のリストに応じて**OAuth Apps**もしくは**GitHub Apps**をクリックしてください。 **ノート:** https://github.com/marketplace/manageにアクセスしてもリストを管理できます。 ![アプリケーションの種類の選択](/assets/images/settings/apps_choose_app.png)
 
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/user-settings/modify_github_app.md b/translations/ja-JP/data/reusables/user-settings/modify_github_app.md
index b92bf8f05f..b2d4771c57 100644
--- a/translations/ja-JP/data/reusables/user-settings/modify_github_app.md
+++ b/translations/ja-JP/data/reusables/user-settings/modify_github_app.md
@@ -1 +1 @@
-1. Select the GitHub App you want to modify. ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
+1. 変更したいGitHub Appを選択してください。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
diff --git a/translations/ja-JP/data/reusables/user-settings/oauth_apps.md b/translations/ja-JP/data/reusables/user-settings/oauth_apps.md
index 7bf00c16f7..5fcccdf79b 100644
--- a/translations/ja-JP/data/reusables/user-settings/oauth_apps.md
+++ b/translations/ja-JP/data/reusables/user-settings/oauth_apps.md
@@ -1 +1 @@
-1. In the left sidebar, click **OAuth Apps**. ![OAuth Apps section](/assets/images/help/settings/developer-settings-oauth-apps.png)
+1. ひだりのサイドバーで**OAuth Apps**をクリックしてください。 ![OAuth Appsセクション](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/translations/ja-JP/data/reusables/user-settings/update_oauth_app.md b/translations/ja-JP/data/reusables/user-settings/update_oauth_app.md
index 5d0f1ffa7f..e7c260eb8e 100644
--- a/translations/ja-JP/data/reusables/user-settings/update_oauth_app.md
+++ b/translations/ja-JP/data/reusables/user-settings/update_oauth_app.md
@@ -1 +1 @@
-1. Click **Update application**. ![Button to update the application](/assets/images/oauth-apps/oauth_apps_update_application.png)
+1. **Update application（アプリケーションの更新）**をクリックしてください。 ![アプリケーションを更新するボタン](/assets/images/oauth-apps/oauth_apps_update_application.png)
diff --git a/translations/ja-JP/data/reusables/user_settings/about-commit-email-addresses.md b/translations/ja-JP/data/reusables/user_settings/about-commit-email-addresses.md
index c1d07e7683..25b4ec2cb9 100644
--- a/translations/ja-JP/data/reusables/user_settings/about-commit-email-addresses.md
+++ b/translations/ja-JP/data/reusables/user_settings/about-commit-email-addresses.md
@@ -1 +1 @@
-For more information on commit email addresses,{% if currentVersion == "free-pro-team@latest" %} including your {% data variables.product.product_name %}-provided `noreply` email address,{% endif %} see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} が提供する`noreply`メールアドレスを含む{% endif %}コミットメールアドレスに関する詳しい情報については「[コミットメールアドレスの設定](/articles/setting-your-commit-email-address)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/user_settings/billing_plans.md b/translations/ja-JP/data/reusables/user_settings/billing_plans.md
index 8d26ab1479..e0308860fb 100644
--- a/translations/ja-JP/data/reusables/user_settings/billing_plans.md
+++ b/translations/ja-JP/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. ユーザ設定サイドバーで**Billing & plans（支払いプラン）**をクリックしてください。 ![支払いプランの設定](/assets/images/help/settings/settings-sidebar-billing-plans.png)
diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md
index ae43f35c1f..5fbef30671 100644
--- a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md
+++ b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md
@@ -1 +1 @@
-1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png)
\ No newline at end of file
+1. "Repository access（リポジトリアクセス）"ドロップダウンメニューを選択し、続いてシークレットへアクセスしたいリポジトリをクリックしてください。 シークレットにアクセスしたいすべてのリポジトリに対して繰り返してください。 !["リポジトリアクセス"ドロップダウンメニュー](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md
index 82cb0fbffe..adb80f1285 100644
--- a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md
+++ b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md
@@ -1 +1 @@
-1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png)
\ No newline at end of file
+1. "Value（値）"の下で、シークレットの値を入力してください。 !["値"テキストボックス](/assets/images/help/settings/codespaces-secret-value-field.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md
index e4908fcf75..1c2363d30c 100644
--- a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md
+++ b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md
@@ -1 +1 @@
-1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png)
\ No newline at end of file
+1. 左のサイドバーで**Codespaces**をクリックしてください。 ![ユーザ設定サイドバーのCodespacesタブ](/assets/images/help/settings/codespaces-tab.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/user_settings/export-data.md b/translations/ja-JP/data/reusables/user_settings/export-data.md
index 857cba63b9..f2deb48c45 100644
--- a/translations/ja-JP/data/reusables/user_settings/export-data.md
+++ b/translations/ja-JP/data/reusables/user_settings/export-data.md
@@ -1,4 +1,4 @@
 {% if currentVersion == "free-pro-team@latest" %}
-You can export and review the metadata that
-{% data variables.product.product_name %} stores about your personal account.
+個人アカウントに関する
+{% data variables.product.product_name %}が保存するメタデータを、エクスポートしてレビューできます。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/ja-JP/data/reusables/user_settings/keeping_your_email_address_private.md
index 3a0551f6f3..10c3d48ce3 100644
--- a/translations/ja-JP/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/ja-JP/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. WebベースのGit操作をする際にメールアドレスをプライベートに保つには、**Keep my email address private（メールアドレスをプライベートに保つ）**をクリックしてください。 ![メールアドレスをプライベートに保つチェックボックスの画像](/assets/images/help/settings/email_privacy.png)
+5. WebベースのGit操作をする際にメールアドレスをプライベートに保つには、**Keep my email addresses private（メールアドレスをプライベートに保つ）**をクリックしてください。 ![メールアドレスをプライベートに保つチェックボックスの画像](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/ja-JP/data/reusables/user_settings/link_email_with_your_account.md b/translations/ja-JP/data/reusables/user_settings/link_email_with_your_account.md
index a1fa5e4664..67b9f238f1 100644
--- a/translations/ja-JP/data/reusables/user_settings/link_email_with_your_account.md
+++ b/translations/ja-JP/data/reusables/user_settings/link_email_with_your_account.md
@@ -1,4 +1,4 @@
 {% if currentVersion != "github-ae@latest" %}
-Add the email address to your account on
-{% data variables.product.product_name %}, so that your commits are attributed to you and appear in your contributions graph. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."
+メールアドレスを
+{% data variables.product.product_name %}上のアカウントに追加して、自分のコミットが自分に帰属し、コントリビューショングラフに表示されるようにしてください。 詳しい情報については「[{% data variables.product.prodname_dotcom %}アカウントへのメールアドレスの追加](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)」を参照してください。
 {% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation-desktop.md b/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation-desktop.md
index cb23969e5b..13534916dc 100644
--- a/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation-desktop.md
+++ b/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation-desktop.md
@@ -1,5 +1,5 @@
   {% warning %}
 
-  **Warning**: Authenticating to {% data variables.product.prodname_dotcom %} using your username and password is deprecated. We recommend authenticating using the browser instead.
+  **警告**: ユーザ名とパスワードで{% data variables.product.prodname_dotcom %}の認証を受けることは、非推奨です。 代わりにブラウザで認証を受けることをおすすめします。
 
   {% endwarning %}
diff --git a/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation.md b/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation.md
index bd247793ce..d4cbf3206b 100644
--- a/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation.md
+++ b/translations/ja-JP/data/reusables/user_settings/password-authentication-deprecation.md
@@ -1 +1 @@
-When Git prompts you for your password, enter your personal access token (PAT) instead.{% if currentVersion != "github-ae@latest" %} Password-based authentication for Git is deprecated, and using a PAT is more secure.{% endif %} For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Gitがパスワードを求めてきたときは、代わりに個人アクセストークン（PAT）を入力してください。{% if currentVersion != "github-ae@latest" %}パスワードベースのGitの認証は非推奨であり、PATを利用する方がセキュアです。{% endif %}詳しい情報については「[個人アクセストークンの作成](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/user_settings/payment-info-link.md b/translations/ja-JP/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..0cefab4c9a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. ページの上部で**Payment information（支払い情報）**をクリックしてください。 ![支払い情報のリンク](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/ja-JP/data/reusables/user_settings/personal_dashboard.md b/translations/ja-JP/data/reusables/user_settings/personal_dashboard.md
index 07083b821d..5b52cf377c 100644
--- a/translations/ja-JP/data/reusables/user_settings/personal_dashboard.md
+++ b/translations/ja-JP/data/reusables/user_settings/personal_dashboard.md
@@ -1 +1 @@
-{% if currentVersion == "free-pro-team@latest" %}[personal dashboard](https://github.com/dashboard){% else %}personal dashboard (`https://[hostname]/dashboard`){% endif %}
+{% if currentVersion == "free-pro-team@latest" %}[personal dashboard（個人ダッシュボード）](https://github.com/dashboard){% else %}personal dashboard （個人ダッシュボード）(`https://[hostname]/dashboard`){% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/review_oauth_tokens_tip.md b/translations/ja-JP/data/reusables/user_settings/review_oauth_tokens_tip.md
index 7cd5caddf1..33d7d1a2a8 100644
--- a/translations/ja-JP/data/reusables/user_settings/review_oauth_tokens_tip.md
+++ b/translations/ja-JP/data/reusables/user_settings/review_oauth_tokens_tip.md
@@ -1 +1 @@
-We recommend that you regularly review your authorized integrations. しばらくの間使われていないアプリケーションやトークンは削除してください。 詳しい情報については「[認可されたインテグレーションのレビュー](/articles/reviewing-your-authorized-integrations)」を参照してください。
+認可されたインテグレーションを定期的にレビューすることをおすすめします。 しばらくの間使われていないアプリケーションやトークンは削除してください。 詳しい情報については「[認可されたインテグレーションのレビュー](/articles/reviewing-your-authorized-integrations)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/user_settings/security-analysis.md b/translations/ja-JP/data/reusables/user_settings/security-analysis.md
index d602fb3a9d..dbf88ee9b5 100644
--- a/translations/ja-JP/data/reusables/user_settings/security-analysis.md
+++ b/translations/ja-JP/data/reusables/user_settings/security-analysis.md
@@ -1 +1 @@
-1. 左のサイドバーで、**Security & analysis（セキュリティと分析）**をクリックしてください。 ![Security and analysis settings](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+1. 左のサイドバーで、**Security & analysis（セキュリティと分析）**をクリックしてください。 ![セキュリティと分析の設定](/assets/images/help/settings/settings-sidebar-security-analysis.png)
diff --git a/translations/ja-JP/data/reusables/user_settings/security.md b/translations/ja-JP/data/reusables/user_settings/security.md
index 5487060910..244f3c73a8 100644
--- a/translations/ja-JP/data/reusables/user_settings/security.md
+++ b/translations/ja-JP/data/reusables/user_settings/security.md
@@ -1,4 +1,4 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}1. In the left sidebar, click **Account security**.
-![User account security settings](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}1. 左のサイドバーで**Account security（アカウントのセキュリティ）**をクリックしてください。
+![ユーザアカウントのセキュリティ設定](/assets/images/help/settings/settings-sidebar-account-security.png)
 {% else %}1. 左のサイドバーで**Security（セキュリティ）**をクリックしてください。
-![User account security settings](/assets/images/help/settings/settings-sidebar-security.png){% endif %}
+![ユーザアカウントのセキュリティ設定](/assets/images/help/settings/settings-sidebar-security.png){% endif %}
diff --git a/translations/ja-JP/data/reusables/user_settings/set_your_email_address_in_git.md b/translations/ja-JP/data/reusables/user_settings/set_your_email_address_in_git.md
index 5a5e1701cf..4da93da584 100644
--- a/translations/ja-JP/data/reusables/user_settings/set_your_email_address_in_git.md
+++ b/translations/ja-JP/data/reusables/user_settings/set_your_email_address_in_git.md
@@ -1 +1 @@
-Gitでメールアドレスを設定してください。 You can use {% if currentVersion == "free-pro-team@latest"%}your [{% data variables.product.product_name %}-provided `no-reply` email address](/articles/setting-your-commit-email-address) or {% endif %}any email address.
+Gitでメールアドレスを設定してください。 {% if currentVersion == "free-pro-team@latest"%}[{% data variables.product.product_name %}が提供する`no-reply`メールアドレス](/articles/setting-your-commit-email-address)もしくは{% endif %}任意のメールアドレスが利用できます。
diff --git a/translations/ja-JP/data/reusables/webhooks/action_type_desc.md b/translations/ja-JP/data/reusables/webhooks/action_type_desc.md
index 43e5cb80e4..67d972758f 100644
--- a/translations/ja-JP/data/reusables/webhooks/action_type_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/action_type_desc.md
@@ -1 +1 @@
-The type of activity is specified in the `action` property of the payload object.
+アクティビティのタイプは、ペイロードオブジェクトの`action`プロパティで指定されます。
diff --git a/translations/ja-JP/data/reusables/webhooks/app_always_desc.md b/translations/ja-JP/data/reusables/webhooks/app_always_desc.md
index d52aaebe58..a3e68cebb0 100644
--- a/translations/ja-JP/data/reusables/webhooks/app_always_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/app_always_desc.md
@@ -1 +1 @@
-`installation` | `object` | The {% data variables.product.prodname_github_app %} installation.
+`installation` | `object` | {% data variables.product.prodname_github_app %}のインストール。
diff --git a/translations/ja-JP/data/reusables/webhooks/app_desc.md b/translations/ja-JP/data/reusables/webhooks/app_desc.md
index e81bab2cf4..6f44ce4a36 100644
--- a/translations/ja-JP/data/reusables/webhooks/app_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/app_desc.md
@@ -1 +1 @@
-`installation` | `object` | The {% data variables.product.prodname_github_app %} installation. Webhook payloads contain the `installation` property when the event is configured for and sent to a {% data variables.product.prodname_github_app %}.
+`installation` | `object` | {% data variables.product.prodname_github_app %}のインストール。 イベントが{% data variables.product.prodname_github_app %}用に設定され、送信される場合、webhookのペイロードには`installation`プロパティが含まれます。
diff --git a/translations/ja-JP/data/reusables/webhooks/authorization_event.md b/translations/ja-JP/data/reusables/webhooks/authorization_event.md
index 4afc18c3f4..a5d5254ee0 100644
--- a/translations/ja-JP/data/reusables/webhooks/authorization_event.md
+++ b/translations/ja-JP/data/reusables/webhooks/authorization_event.md
@@ -1 +1 @@
-Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error.
+誰でも、自分の[GitHubアカウント設定ページ](https://github.com/settings/apps/authorizations)からGitHub Appの認可を取り消すことができます。 GitHub Appの認可を取り消しても、そのGitHub Appはアンインストールされません。 GitHub Appは、このwebhookを受信したら、トークンを取り返した人の代わりにAPIを呼ぶことを止めるようにプログラムしなければなりません。 取り消されたアクセストークンを使い続けると、GitHub Appは`401 Bad Credentials`エラーを受け取ることになります。
diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md
index e20f49811f..d9e78b3a6c 100644
--- a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md
@@ -1,12 +1,12 @@
-| キー                                      | 種類        | 説明                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| --------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`                                | `string`  | 実行されたアクション。 次のいずれかになります。 <ul><li> `created` - A new check run was created.</li><li> `completed` - The `status` of the check run is `completed`.</li><li> `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.</li><li> `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."</li></ul>                                                                                                                                                                                                                                                                                                                                                                       |
-| `check_run`                             | `オブジェクト`  | The [check_run](/rest/reference/checks#get-a-check-run).                                                                                                                                                                                                                                                                                                                                                                |
-| `check_run[status]`                     | `string`  | The current status of the check run. Can be `queued`, `in_progress`, or `completed`.                                                                                                                                                                                                                                                                                                                                    |
-| `check_run[conclusion]`                 | `string`  | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`,  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`.                       |
-| `check_run[name]`                       | `string`  | The name of the check run.                                                                                                                                                                                                                                                                                                                                                                                              |
-| `check_run[check_suite][id]`            | `integer` | The id of the check suite that this check run is part of.                                                                                                                                                                                                                                                                                                                                                               |
-| `check_run[check_suite][pull_requests]` | `array`   | An array of pull requests that match this check suite. A pull request matches a check suite if they have the same `head_sha` and `head_branch`. When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-| `check_run[check_suite][deployment]`    | `オブジェクト`  | A deployment to a repository environment. This will only be populated if the check run was created by a {% data variables.product.prodname_actions %} workflow job that references an environment.{% endif %}
-| `requested_action`                      | `オブジェクト`  | The action requested by the user.                                                                                                                                                                                                                                                                                                                                                                                       |
-| `requested_action[identifier]`          | `string`  | The integrator reference of the action requested by the user.                                                                                                                                                                                                                                                                                                                                                           |
+| キー                                      | 種類        | 説明                                                                                                                                                                                                                                                                                                                           |
+| --------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`                                | `string`  | 実行されたアクション。 次のいずれかになります。 <ul><li> `created` - 新しいチェックランが作成されました。</li><li> `completed` - チェックランの`status`は`completed`です。</li><li> `rerequested` - 誰かがPull RequestのUIからチェックランの再実行をリクエストしています。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。 `rerequested`アクションを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 誰かがチェックの再実行をリクエストした{% data variables.product.prodname_github_app %}だけが`rerequested`ペイロードを受け取ります。</li><li> `requested_action` - 誰かが、アプリケーションが提供するアクションの実行をリクエストしました。 誰かがアクションの実行をリクエストした{% data variables.product.prodname_github_app %}だけが`requested_action`ペイロードを受け取ります。 チェックランとリクエストされたアクションについて学ぶには、「[チェックランとリクエストされたアクション](/rest/reference/checks#check-runs-and-requested-actions)」を参照してください。</li></ul>                                                                                                                                                                                                                                                                            |
+| `check_run`                             | `オブジェクト`  | [check_run](/rest/reference/checks#get-a-check-run)。                                                                                                                                                                                                                                                                         |
+| `check_run[status]`                     | `string`  | チェックランの現在のステータス。 `queued`、`in_progress`、`completed`のいずれか。                                                                                                                                                                                                                                                                    |
+| `check_run[conclusion]`                 | `string`  | 完了したチェックランの結果。 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required`、`stale`{% else %}`action_required`{% endif %}のいずれか。 チェックランが`completed`になるまで、この値は`null`になる。 |
+| `check_run[name]`                       | `string`  | チェックランの名前。                                                                                                                                                                                                                                                                                                                   |
+| `check_run[check_suite][id]`            | `integer` | このチェックランが一部になっているチェックスイートのid。                                                                                                                                                                                                                                                                                                |
+| `check_run[check_suite][pull_requests]` | `array`   | このチェックスイートにマッチするPull Requestの配列。 同じ`head_sha`と`head_branch`を持っている場合に、Pull Requestはチェックスイートにマッチする。 チェックスイートの`head_branch`がフォークされたリポジトリにあるなら、それは`null`になり、 `pull_requests`配列は空になる。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+| `check_run[check_suite][deployment]`    | `オブジェクト`  | リポジトリ環境へのデプロイメント。 これは、チェックランが環境を参照する{% data variables.product.prodname_actions %}ワークフロージョブによって作成された場合にのみ展開される。{% endif %}
+| `requested_action`                      | `オブジェクト`  | ユーザによってリクエストされたアクション。                                                                                                                                                                                                                                                                                                        |
+| `requested_action[identifier]`          | `string`  | ユーザによってリクエストされたアクションのインテグレーター参照。                                                                                                                                                                                                                                                                                             |
diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md b/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md
index 15cbbb7936..43aa11f5db 100644
--- a/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/check_run_short_desc.md
@@ -1 +1 @@
-Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check runs](/rest/reference/checks#runs)" REST API.
+チェックランのアクティビティが発生しました。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[check runs](/rest/reference/checks#runs)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md
index abc6ecc54d..a4ee48dbf5 100644
--- a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md
@@ -1,10 +1,10 @@
-| キー                           | 種類       | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`                     | `string` | 実行されたアクション。 Can be:<ul><li>`completed` - All check runs in a check suite have completed.</li><li>`requested` - Occurs when new code is pushed to the app's repository. When you receive the `requested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run).</li><li>`rerequested` - Occurs when someone requests to re-run the entire check suite from the pull request UI. When you receive the `rerequested` action events, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                           |
-| `check_suite`                | `オブジェクト` | The [check_suite](/rest/reference/checks#suites).                                                                                                                                                                                                                                                                                                                                                                                      |
-| `check_suite[head_branch]`   | `string` | The head branch name the changes are on.                                                                                                                                                                                                                                                                                                                                                                                               |
-| `check_suite[head_sha]`      | `string` | The SHA of the most recent commit for this check suite.                                                                                                                                                                                                                                                                                                                                                                                |
-| `check_suite[status]`        | `string` | The summary status for all check runs that are part of the check suite. Can be `requested`, `in_progress`, or `completed`.                                                                                                                                                                                                                                                                                                             |
-| `check_suite[conclusion]`    | `string` | The summary conclusion for all check runs that are part of the check suite. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`,  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. |
-| `check_suite[url]`           | `string` | URL that points to the check suite API resource.                                                                                                                                                                                                                                                                                                                                                                                       |
-| `check_suite[pull_requests]` | `array`  | An array of pull requests that match this check suite. A pull request matches a check suite if they have the same `head_sha` and `head_branch`. When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.                                                                                                                                                          |
+| キー                           | 種類       | 説明                                                                                                                                                                                                                                                                                                                                             |
+| ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`                     | `string` | 実行されたアクション。 以下のいずれかになる。<ul><li>`completed` - チェックスイート内のすべてのチェックランが完了しました。</li><li>`requested` - アプリケーションのリポジトリに新しいコードがプッシュされたときに発生します。 `requested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。</li><li>`rerequested` - 誰かがチェックスイート全体の再実行をPull Request UIからリクエストしたときに発生します。 `rerequested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。</li></ul>                                                                                                                                                                                                                                                                                               |
+| `check_suite`                | `オブジェクト` | [check_suite](/rest/reference/checks#suites)。                                                                                                                                                                                                                                                                                                  |
+| `check_suite[head_branch]`   | `string` | 変更があるヘッドブランチ名。                                                                                                                                                                                                                                                                                                                                 |
+| `check_suite[head_sha]`      | `string` | このチェックスイートに対する最新のコミットのSHA。                                                                                                                                                                                                                                                                                                                     |
+| `check_suite[status]`        | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 `requested`、`in_progress`、`completed`のいずれか。                                                                                                                                                                                                                                                                 |
+| `check_suite[conclusion]`    | `string` | チェックスイートの一部であるすべてのチェックランのサマリの結論。 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required`、`stale`{% else %}`action_required`{% endif %}のいずれか。 チェックランが`completed`になるまで、この値は`null`になる。 |
+| `check_suite[url]`           | `string` | チェックスイートAPIのリソースを指すURL。                                                                                                                                                                                                                                                                                                                        |
+| `check_suite[pull_requests]` | `array`  | このチェックスイートにマッチするPull Requestの配列。 同じ`head_sha`と`head_branch`を持っている場合に、Pull Requestはチェックスイートにマッチする。 チェックスイートの`head_branch`がフォークされたリポジトリ内の場合、それは`null`になり、`pull_requests`配列は空になります。                                                                                                                                                               |
diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md b/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md
index 94ed6dc937..94e939791d 100644
--- a/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/check_suite_short_desc.md
@@ -1 +1 @@
-Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[check suites](/rest/reference/checks#suites)" REST API.
+チェックスイートのアクティビティが発生しました。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[check suites](/rest/reference/checks#suites)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_properties.md
index f831a12370..13cf6a010a 100644
--- a/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,6 +1,6 @@
-| キー           | 種類       | 説明                                                                                                                                                                              |
-| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`     | `string` | 実行されたアクション. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                                                   |
-| `アラート`       | `オブジェクト` | The code scanning alert involved in the event.                                                                                                                                  |
-| `ref`        | `string` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty. |
-| `commit_oid` | `string` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty.    |
+| キー           | 種類       | 説明                                                                                                                 |
+| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------ |
+| `action`     | `string` | 実行されたアクション. `created`、`reopened_by_user`、`closed_by_user`、`fixed`、`appeared_in_branch`、`reopened`のいずれか。            |
+| `alert`      | `オブジェクト` | このイベントに関わるCode Scanningのアラート。                                                                                      |
+| `ref`        | `string` | Code ScanningアラートのGit参照。 アクションが`reopened_by_user`もしくは`closed_by_user`であれば、イベントは`sender`によってトリガーされており、この値は空になります。   |
+| `commit_oid` | `string` | Code ScanningアラートのコミットSHA。 アクションが`reopened_by_user`もしくは`closed_by_user`であれば、イベントは`sender`によってトリガーされており、この値は空になります。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_short_desc.md b/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_short_desc.md
index e5163ce2d0..c65519d7c7 100644
--- a/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/code_scanning_alert_event_short_desc.md
@@ -1 +1 @@
-Activity related to code scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning).”
+リポジトリのCode Scanningアラートに関連するアクティビティ。 アクティビティのタイプは、ペイロードオブジェクトのactionプロパティで指定されます。 詳しい情報については「[Code Scanningについて](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md
index 7329b1ed61..920bd49015 100644
--- a/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/commit_comment_short_desc.md
@@ -1 +1 @@
-A commit comment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[commit comment](/rest/reference/repos#comments)" REST API.
+コミットコメントが作成されました。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[コミットコメント](/rest/reference/repos#comments)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/content_reference_short_desc.md b/translations/ja-JP/data/reusables/webhooks/content_reference_short_desc.md
index 5187dbb40b..686f989c63 100644
--- a/translations/ja-JP/data/reusables/webhooks/content_reference_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/content_reference_short_desc.md
@@ -1 +1 @@
-A new content reference is `created`. A new content reference is created when the body or comment of an issue or pull request includes a URL that matches a configured content reference domain. For more information, see "[Using content attachments](/apps/using-content-attachments/)" to learn more about content references and attachments.
+新しいコンテンツ参照が`作成されました`。 新しいコンテンツ参照は、IssueもしくはPull Requestのボディあるいはコメントが、設定されたコンテンツ参照ドメインにマッチする場合に作成されます。 詳しい情報については「[コンテンツの添付ファイルの使用](/apps/using-content-attachments/)」を参照して、コンテンツ参照と添付ファイルについて学んでください。
diff --git a/translations/ja-JP/data/reusables/webhooks/create_properties.md b/translations/ja-JP/data/reusables/webhooks/create_properties.md
index 435e23091b..1911b261ad 100644
--- a/translations/ja-JP/data/reusables/webhooks/create_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| キー              | 種類       | 説明                                                                                                                                                                                                                                    |
-| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                        |
-| `ref_type`      | `string` | リポジトリで作成されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。                                                                                                                                                                                    |
-| `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
-| `説明`            | `string` | リポジトリの現在の説明。                                                                                                                                                                                                                          |
+| キー              | 種類       | 説明                                                                                                                                                                                                    |
+| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ref`           | `string` | [`git ref`](/rest/reference/git#get-a-reference)リソース。                                                                                                                                                 |
+| `ref_type`      | `string` | リポジトリで作成されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。                                                                                                                                                    |
+| `master_branch` | `string` | リポジトリのデフォルトブランチの名前（通常は{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}）。 |
+| `description`   | `string` | リポジトリの現在の説明。                                                                                                                                                                                          |
diff --git a/translations/ja-JP/data/reusables/webhooks/create_short_desc.md b/translations/ja-JP/data/reusables/webhooks/create_short_desc.md
index 5cf906a338..9c466b6cb2 100644
--- a/translations/ja-JP/data/reusables/webhooks/create_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/create_short_desc.md
@@ -1 +1 @@
-A Git branch or tag is created. For more information, see the "[Git data](/rest/reference/git)" REST API.
+Gitブランチもしくはタグが作成されました。 詳しい情報については「[Gitデータ](/rest/reference/git)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/delete_properties.md b/translations/ja-JP/data/reusables/webhooks/delete_properties.md
index 16e33e07f5..80f9fe79b5 100644
--- a/translations/ja-JP/data/reusables/webhooks/delete_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/delete_properties.md
@@ -1,4 +1,4 @@
-| キー         | 種類       | 説明                                                             |
-| ---------- | -------- | -------------------------------------------------------------- |
-| `ref`      | `string` | The [`git ref`](/rest/reference/git#get-a-reference) resource. |
-| `ref_type` | `string` | リポジトリで削除されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。             |
+| キー         | 種類       | 説明                                                    |
+| ---------- | -------- | ----------------------------------------------------- |
+| `ref`      | `string` | [`git ref`](/rest/reference/git#get-a-reference)リソース。 |
+| `ref_type` | `string` | リポジトリで削除されたGit refオブジェクトの種類。 `branch`もしくは`tag`になる。    |
diff --git a/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md b/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md
index 726e68df82..2b4bea3283 100644
--- a/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/delete_short_desc.md
@@ -1 +1 @@
-A Git branch or tag is deleted. For more information, see the "[Git data](/rest/reference/git)" REST API.
+Gitブランチまたはタグが削除されました。 詳しい情報については「[Gitデータ](/rest/reference/git)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md b/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md
index b51766f731..98b272ae1e 100644
--- a/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/deploy_key_properties.md
@@ -1,4 +1,4 @@
-| キー       | 種類       | 説明                                                                   |
-| -------- | -------- | -------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション。 Can be either `created` or `deleted`.                    |
-| `キー`     | `オブジェクト` | The [`deploy key`](/rest/reference/repos#get-a-deploy-key) resource. |
+| キー       | 種類       | 説明                                                          |
+| -------- | -------- | ----------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション。 `created`もしくは`deleted`のいずれか。                    |
+| `key`    | `オブジェクト` | [`deploy key`](/rest/reference/repos#get-a-deploy-key)リソース。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md b/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md
index 1d4565e788..f3f9dde52d 100644
--- a/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/deploy_key_short_desc.md
@@ -1 +1 @@
-A deploy key is added or removed from a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[Deploy keys](/rest/reference/repos#keys)" REST API.
+デプロイキーが、リポジトリに追加もしくはリポジトリから削除される。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[デプロイキー](/rest/reference/repos#keys)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/deployment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/deployment_short_desc.md
index 249535a29d..63422d2b4f 100644
--- a/translations/ja-JP/data/reusables/webhooks/deployment_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/deployment_short_desc.md
@@ -1 +1 @@
-A deployment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[deployment](/rest/reference/repos#list-deployments)" REST API.
+デプロイメントが作成されました。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[デプロイメント](/rest/reference/repos#list-deployments)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/deployment_status_short_desc.md b/translations/ja-JP/data/reusables/webhooks/deployment_status_short_desc.md
index d58bd3e0ef..d852ba202e 100644
--- a/translations/ja-JP/data/reusables/webhooks/deployment_status_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/deployment_status_short_desc.md
@@ -1 +1 @@
-A deployment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[deployment statuses](/rest/reference/repos#list-deployment-statuses)" REST API.
+デプロイメントが作成されました。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[デプロイメントステータス](/rest/reference/repos#list-deployment-statuses)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/discussion_desc.md b/translations/ja-JP/data/reusables/webhooks/discussion_desc.md
index 1b221660e0..532eb76894 100644
--- a/translations/ja-JP/data/reusables/webhooks/discussion_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/discussion_desc.md
@@ -1 +1 @@
-`discussion` | `object` | The [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion) resource.
\ No newline at end of file
+`discussion` | `object` | [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion)リソース。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/webhooks/discussions-webhooks-beta.md b/translations/ja-JP/data/reusables/webhooks/discussions-webhooks-beta.md
index 2033ca20ea..3bbf2d224f 100644
--- a/translations/ja-JP/data/reusables/webhooks/discussions-webhooks-beta.md
+++ b/translations/ja-JP/data/reusables/webhooks/discussions-webhooks-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Webhook events for {% data variables.product.prodname_discussions %} are currently in beta and subject to change.
+**ノート:** {% data variables.product.prodname_discussions %}のwebhookイベントは現在ベータであり、変更されることがあります。
 
 {% endnote %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/webhooks/enterprise_short_desc.md b/translations/ja-JP/data/reusables/webhooks/enterprise_short_desc.md
index 07659be69c..b015f3de8b 100644
--- a/translations/ja-JP/data/reusables/webhooks/enterprise_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/enterprise_short_desc.md
@@ -1 +1 @@
-A site or repository administrator enables or disables anonymous Git read access. See "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)" for more details. This event is not available in the Events API.
+サイトもしくはリポジトリ管理者が、匿名Git読み取りアクセスを有効化あるいは無効化します。 詳細については「[パブリックリポジトリへの匿名Git読み取りアクセスの有効化を管理者に許可する](/enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)」を参照してください。 このイベントはEvents APIでは利用できません。
diff --git a/translations/ja-JP/data/reusables/webhooks/events_api_payload.md b/translations/ja-JP/data/reusables/webhooks/events_api_payload.md
index d63dfb496e..345e42bd27 100644
--- a/translations/ja-JP/data/reusables/webhooks/events_api_payload.md
+++ b/translations/ja-JP/data/reusables/webhooks/events_api_payload.md
@@ -1 +1 @@
-The [event object](#event-object-common-properties) includes properties that are common for all events. Each event object includes a `payload` property and the value is unique to each event type. The `payload` object for this event is described below.
+[イベントオブジェクト](#event-object-common-properties)には、すべてのイベントに共通のプロパティが含まれます。 それぞれのイベントオブジェクトには`payload`プロパティが含まれ、その値はそれぞれのイベントタイプに固有です。 このイベントの`payload`は以下に示します。
diff --git a/translations/ja-JP/data/reusables/webhooks/fork_properties.md b/translations/ja-JP/data/reusables/webhooks/fork_properties.md
index a7c6752e06..06dad4efeb 100644
--- a/translations/ja-JP/data/reusables/webhooks/fork_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/fork_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                           |
-| -------- | -------- | ---------------------------------------------------------------------------- |
-| `forkee` | `オブジェクト` | The created [`repository`](/rest/reference/repos#get-a-repository) resource. |
+| キー       | 種類       | 説明                                                               |
+| -------- | -------- | ---------------------------------------------------------------- |
+| `forkee` | `オブジェクト` | 作成された[`repository`](/rest/reference/repos#get-a-repository)リソース。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md b/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md
index 23b9eff136..d502a36cb5 100644
--- a/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/fork_short_desc.md
@@ -1 +1 @@
-A user forks a repository. For more information, see the "[forks](/rest/reference/repos#forks)" REST API.
+ユーザがリポジトリをフォークします。 詳しい情報については「[forks](/rest/reference/repos#forks)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/gollum_properties.md b/translations/ja-JP/data/reusables/webhooks/gollum_properties.md
index d42a7df972..a8bf013083 100644
--- a/translations/ja-JP/data/reusables/webhooks/gollum_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/gollum_properties.md
@@ -1,8 +1,8 @@
-| キー                   | 種類       | 説明                                                                       |
-| -------------------- | -------- | ------------------------------------------------------------------------ |
-| `pages`              | `array`  | The pages that were updated.                                             |
-| `pages[][page_name]` | `string` | The name of the page.                                                    |
-| `pages[][title]`     | `string` | The current page title.                                                  |
-| `pages[][action]`    | `string` | The action that was performed on the page. Can be `created` or `edited`. |
-| `pages[][sha]`       | `string` | The latest commit SHA of the page.                                       |
-| `pages[][html_url]`  | `string` | Points to the HTML wiki page.                                            |
+| キー                   | 種類       | 説明                                          |
+| -------------------- | -------- | ------------------------------------------- |
+| `pages`              | `array`  | 更新されたページ。                                   |
+| `pages[][page_name]` | `string` | ページの名前。                                     |
+| `pages[][title]`     | `string` | 現在のページのタイトル。                                |
+| `pages[][action]`    | `string` | ページ上で行われたアクション。 `created`もしくは`edited`のいずれか。 |
+| `pages[][sha]`       | `string` | ページの最新のコミットSHA。                             |
+| `pages[][html_url]`  | `string` | HTMLのwikiページを指す。                            |
diff --git a/translations/ja-JP/data/reusables/webhooks/gollum_short_desc.md b/translations/ja-JP/data/reusables/webhooks/gollum_short_desc.md
index 3049191763..d2fbf3fa1b 100644
--- a/translations/ja-JP/data/reusables/webhooks/gollum_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/gollum_short_desc.md
@@ -1 +1 @@
-A wiki page is created or updated. For more information, see the "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)".
+wikiページが作成もしくは更新されました。 詳しい情報については「[wikiについて](/communities/documenting-your-project-with-wikis/about-wikis)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/installation_properties.md b/translations/ja-JP/data/reusables/webhooks/installation_properties.md
index b8d658fcfc..850e73339e 100644
--- a/translations/ja-JP/data/reusables/webhooks/installation_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/installation_properties.md
@@ -1,4 +1,4 @@
-| キー             | 種類       | 説明                                                               |
-| -------------- | -------- | ---------------------------------------------------------------- |
-| `action`       | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`created` - Someone installs a {% data variables.product.prodname_github_app %}.</li><li>`deleted` - Someone uninstalls a {% data variables.product.prodname_github_app %}</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}<li>`suspend` - Someone suspends a {% data variables.product.prodname_github_app %} installation.</li><li>`unsuspend` - Someone unsuspends a {% data variables.product.prodname_github_app %} installation.</li>{% endif %}<li>`new_permissions_accepted` - Someone accepts new permissions for a {% data variables.product.prodname_github_app %} installation. When a {% data variables.product.prodname_github_app %} owner requests new permissions, the person who installed the {% data variables.product.prodname_github_app %} must accept the new permissions request. </li></ul>                |
-| `repositories` | `array`  | An array of repository objects that the installation can access. |
+| キー             | 種類       | 説明                                                |
+| -------------- | -------- | ------------------------------------------------- |
+| `action`       | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`created` - 誰かが{% data variables.product.prodname_github_app %}をインストールする。</li><li>`deleted` - だれかが{% data variables.product.prodname_github_app %}をアンインストールする。</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}<li>`suspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンドする。</li><li>`unsuspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンド解除する。</li>{% endif %}<li>`new_permissions_accepted` - 誰かが{% data variables.product.prodname_github_app %}インストールに対する新しい権限を受け入れる。 {% data variables.product.prodname_github_app %}のオーナーが新しい権限をリクエストすると、{% data variables.product.prodname_github_app %}をインストールした人は新しい権限リクエストを受け入れなければならない。 </li></ul> |
+| `repositories` | `array`  | インストールがアクセスできるリポジトリオブジェクトの配列。                     |
diff --git a/translations/ja-JP/data/reusables/webhooks/installation_repositories_properties.md b/translations/ja-JP/data/reusables/webhooks/installation_repositories_properties.md
index e0ab22a847..2658ee5dd6 100644
--- a/translations/ja-JP/data/reusables/webhooks/installation_repositories_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/installation_repositories_properties.md
@@ -1,6 +1,6 @@
-| キー                     | 種類       | 説明                                                                                    |
-| ---------------------- | -------- | ------------------------------------------------------------------------------------- |
-| `action`               | `string` | 実行されたアクション. Can be either `added` or `removed`.                                       |
-| `repository_selection` | `string` | The choice of repositories the installation is on. Can be either `selected` or `all`. |
-| `repositories_added`   | `array`  | An array of repository objects, which were added to the installation.                 |
-| `repositories_removed` | `array`  | An array of repository objects, which were removed from the installation.             |
+| キー                     | 種類       | 説明                                           |
+| ---------------------- | -------- | -------------------------------------------- |
+| `action`               | `string` | 実行されたアクション. `added`あるいは`removed`のいずれか。       |
+| `repository_selection` | `string` | インストールがあるリポジトリの選択。 `selected`あるいは`all`のいずれか。 |
+| `repositories_added`   | `array`  | インストールに追加されたリポジトリオブジェクトの配列。                  |
+| `repositories_removed` | `array`  | インストールから削除されたリポジトリオブジェクトの配列。                 |
diff --git a/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md
index f1debb10f2..4403ff84f5 100644
--- a/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/installation_repositories_short_desc.md
@@ -1 +1 @@
-Activity related to repositories being added to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API.
+GitHub Appのインストールに追加されたリポジトリに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[GitHub Appインストール](/rest/reference/apps)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md b/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md
index 21cffb5f50..3007d96855 100644
--- a/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/installation_short_desc.md
@@ -1 +1 @@
-Activity related to a GitHub App installation. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub App installation](/rest/reference/apps)" REST API.
+GitHub Appインストールに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[GitHub Appインストール](/rest/reference/apps)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md
index 159facecf3..58a8acde06 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_comment_properties.md
@@ -1 +1 @@
-`changes`|`object` | The changes to the comment if the action was `edited`. `changes[body][from]` |`string` | アクションが`edited`だった場合の、以前のバージョンのbody。 `issue`|`object` | The [issue](/rest/reference/issues) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/issues#comments) itself.
+`changes`|`object` | アクションが`edited`だった場合のコメントへの変更。 `changes[body][from]` |`string` | アクションが`edited`だった場合の、以前のバージョンのbody。 `issue`|`object` | コメントが属する[Issue](/rest/reference/issues)。 `comment`|`object` | [コメント](/rest/reference/issues#comments)自体。
diff --git a/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md
index dd67c3de2d..b3e7864a79 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_comment_short_desc.md
@@ -1 +1 @@
-Activity related to an issue comment. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issue comments](/rest/reference/issues#comments)" REST API.
+Issueコメントに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Issueコメント](/rest/reference/issues#comments)" REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/issue_comment_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_comment_webhook_properties.md
index 58ed157537..15ebe2a70a 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_comment_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_comment_webhook_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                             |
-| -------- | -------- | ---------------------------------------------------------------------------------------------- |
-| `action` | `string` | The action that was performed on the comment. Can be one of `created`, `edited`, or `deleted`. |
+| キー       | 種類       | 説明                                                   |
+| -------- | -------- | ---------------------------------------------------- |
+| `action` | `string` | コメント上で実行されたアクション。 `created`、`edited`、`deleted`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md
index 7388a84009..5c4bc227b2 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                                             |
-| -------- | -------- | -------------------------------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. Can be one of `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, or `unlabeled`. |
+| キー       | 種類       | 説明                                                                                           |
+| -------- | -------- | -------------------------------------------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. `opened`、`closed`、`reopened`、`assigned`、`unassigned`、`labeled`、`unlabeled`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/issue_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_properties.md
index bff204fc72..f9c6627137 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_properties.md
@@ -1 +1 @@
-`issue`|`object` | The [issue](/rest/reference/issues) itself. `changes`|`object`| The changes to the issue if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `assignee`|`object` | The optional user who was assigned or unassigned from the issue. `label`|`object` | The optional label that was added or removed from the issue.
+`issue`|`object` | [Issue](/rest/reference/issues)自体。 `changes`|`object`| アクションが`edited`の場合、Issueへの変更。 `changes[title][from]`|`string` | アクションが`edited`の場合、以前のバージョンのタイトル。 `changes[body][from]`|`string` | アクションが`edited`の場合、以前のバージョンのボディ。 `assignee`|`object` | Issueに割り当てられた、あるいは割り当てを解除されたオプションのユーザ。 `label`|`object` | Issueに追加された、あるいはIssueから削除されたオプションのラベル。
diff --git a/translations/ja-JP/data/reusables/webhooks/issue_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_webhook_properties.md
index 010aef01e3..aa5cfbe116 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_webhook_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                                                                                                                                                            |
-| -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `deleted`, `pinned`, `unpinned`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, `unlabeled`, `locked`, `unlocked`,  `transferred`, `milestoned`, or `demilestoned`. |
+| キー       | 種類       | 説明                                                                                                                                                                                                |
+| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. `opened`、`edited`、`deleted`、`pinned`、`unpinned`、`closed`、`reopened`、`assigned`、`unassigned`、`labeled`、`unlabeled`、`locked`、`unlocked`、`transferred`、`milestoned`、`demilestoned`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md b/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md
index 3edc02859f..1c73e53103 100644
--- a/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/issues_short_desc.md
@@ -1 +1 @@
-Activity related to an issue. {% data reusables.webhooks.action_type_desc %} For more information, see the "[issues](/rest/reference/issues#comments)" REST API.
+Issueに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Issue](/rest/reference/issues#comments)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/label_short_desc.md b/translations/ja-JP/data/reusables/webhooks/label_short_desc.md
index 0f4041c4bb..766b4cf55d 100644
--- a/translations/ja-JP/data/reusables/webhooks/label_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/label_short_desc.md
@@ -1 +1 @@
-Activity related to a label. {% data reusables.webhooks.action_type_desc %} For more information, see the "[labels](/rest/reference/issues#labels)" REST API.
+ラベルに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[ラベル](/rest/reference/issues#labels)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/member_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/member_event_api_properties.md
index 0cb5875d9d..16c8a570a1 100644
--- a/translations/ja-JP/data/reusables/webhooks/member_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/member_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                    |
-| -------- | -------- | ------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. Can be `added` to indicate a user accepted an invitation to a repository. |
+| キー       | 種類       | 説明                                                |
+| -------- | -------- | ------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. `added`になり、ユーザがリポジトリへの招待を承認したことを示します。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/member_properties.md b/translations/ja-JP/data/reusables/webhooks/member_properties.md
index add035dc19..a4f9b641e9 100644
--- a/translations/ja-JP/data/reusables/webhooks/member_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/member_properties.md
@@ -1 +1 @@
-`member`|`object` | The [user](/rest/reference/users) that was added. `changes`|`object`| The changes to the collaborator permissions if the action was `edited`. `changes[old_permission][from]`|`string` | The previous permissions of the collaborator if the action was `edited`.
+`member`|`object` | 追加された[ユーザ](/rest/reference/users)。 `changes`|`object`| アクションが`edited`の場合、コラボレータの権限の変更。 `changes[old_permission][from]`|`string` | アクションが`edited`の場合、コラボレータの以前の権限。
diff --git a/translations/ja-JP/data/reusables/webhooks/member_short_desc.md b/translations/ja-JP/data/reusables/webhooks/member_short_desc.md
index b664392fdf..3b5f4e586f 100644
--- a/translations/ja-JP/data/reusables/webhooks/member_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/member_short_desc.md
@@ -1 +1 @@
-Activity related to repository collaborators. {% data reusables.webhooks.action_type_desc %} For more information, see the "[collaborators](/rest/reference/repos#collaborators)" REST API.
+リポジトリのコラボレータに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[コラボレータ](/rest/reference/repos#collaborators)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md
index 1f8317a1c0..572cbac683 100644
--- a/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md
@@ -1,3 +1,3 @@
 | キー       | 種類       | 説明                                                |
 | -------- | -------- | ------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. 次のいずれかになります。<ul><li> `added` - A user accepts an invitation to a repository.</li><li>`removed` - A user is removed as a collaborator in a repository.</li><li>`edited` - A user's collaborator permissions have changed. </li></ul> |
+| `action` | `string` | 実行されたアクション. 次のいずれかになります。<ul><li> `added` - ユーザがリポジトリへの招待を受け入れた。</li><li>`removed` - ユーザがリポジトリのコラボレータとして削除された。</li><li>`edited` - ユーザのコラボレータ権限が変更された。 </li></ul> |
diff --git a/translations/ja-JP/data/reusables/webhooks/membership_properties.md b/translations/ja-JP/data/reusables/webhooks/membership_properties.md
index 28a16d9b2a..5aaed01da6 100644
--- a/translations/ja-JP/data/reusables/webhooks/membership_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/membership_properties.md
@@ -1,6 +1,6 @@
-| キー       | 種類       | 説明                                                           |
-| -------- | -------- | ------------------------------------------------------------ |
-| `action` | `string` | 実行されたアクション. Can be `added` or `removed`.                     |
-| `スコープ`   | `string` | The scope of the membership. Currently, can only be `team`.  |
-| `member` | `オブジェクト` | The [user](/rest/reference/users) that was added or removed. |
-| `Team`   | `オブジェクト` | The [team](/rest/reference/teams) for the membership.        |
+| キー       | 種類       | 説明                                       |
+| -------- | -------- | ---------------------------------------- |
+| `action` | `string` | 実行されたアクション. `added`もしくは`removed`。        |
+| `scope`  | `string` | メンバーシップのスコープ。 現在は`team`にのみなりうる。          |
+| `member` | `オブジェクト` | 追加もしくは削除された[ユーザ](/rest/reference/users)。 |
+| `Team`   | `オブジェクト` | メンバーシップの[Team](/rest/reference/teams)。   |
diff --git a/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md b/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md
index f7867d25a9..3fc6840a12 100644
--- a/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/membership_short_desc.md
@@ -1 +1 @@
-Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[team members](/rest/reference/teams#members)" REST API.
+Teamのメンバーシップに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Teamメンバー](/rest/reference/teams#members)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/milestone_properties.md b/translations/ja-JP/data/reusables/webhooks/milestone_properties.md
index 7bfcb86615..208d0b91ba 100644
--- a/translations/ja-JP/data/reusables/webhooks/milestone_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/milestone_properties.md
@@ -1,8 +1,8 @@
-| キー                           | 種類       | 説明                                                                               |
-| ---------------------------- | -------- | -------------------------------------------------------------------------------- |
-| `action`                     | `string` | 実行されたアクション. Can be one of `created`, `closed`, `opened`, `edited`, or `deleted`. |
-| `マイルストーン`                    | `オブジェクト` | The milestone itself.                                                            |
-| `変更`                         | `オブジェクト` | The changes to the milestone if the action was `edited`.                         |
-| `changes[description][from]` | `string` | The previous version of the description if the action was `edited`.              |
-| `changes[due_on][from]`      | `string` | The previous version of the due date if the action was `edited`.                 |
-| `changes[title][from]`       | `string` | The previous version of the title if the action was `edited`.                    |
+| キー                           | 種類       | 説明                                                               |
+| ---------------------------- | -------- | ---------------------------------------------------------------- |
+| `action`                     | `string` | 実行されたアクション. `created`、`closed`、`opened`、`edited`、`deleted`のいずれか。 |
+| `milestone`                  | `オブジェクト` | マイルストーン自体。                                                       |
+| `changes`                    | `オブジェクト` | アクションが`edited`の場合、マイルストーンへの変更。                                   |
+| `changes[description][from]` | `string` | アクションが `edited` の場合、以前のバージョンの説明。                                 |
+| `changes[due_on][from]`      | `string` | アクションが`edited`だった場合の、以前のバージョンの期限。                                |
+| `changes[title][from]`       | `string` | アクションが`edited`だった場合の、以前のバージョンのタイトル。                              |
diff --git a/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md b/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md
index c9edf73236..5ec8c8de0b 100644
--- a/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/milestone_short_desc.md
@@ -1 +1 @@
-Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[milestones](/rest/reference/issues#milestones)" REST API.
+マイルストーンに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[マイルストーン](/rest/reference/issues#milestones)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md b/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md
index ec89e9f647..61868ad9bd 100644
--- a/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md
@@ -1 +1 @@
-Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} 詳しい情報については、「[Organization ユーザをブロックする](/rest/reference/orgs#blocking)」REST API を参照してください。
+Organizationでブロックされている人に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については、「[Organization ユーザをブロックする](/rest/reference/orgs#blocking)」REST API を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/org_desc.md b/translations/ja-JP/data/reusables/webhooks/org_desc.md
index 90d218b876..3e0e9cb3c8 100644
--- a/translations/ja-JP/data/reusables/webhooks/org_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/org_desc.md
@@ -1 +1 @@
-`organization` | `object` | Webhook payloads contain the [`organization`](/rest/reference/orgs#get-an-organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization.
+`organization` | `object` | webhookがOrganizationに対して設定されている場合、あるいはOrganizationが所有するリポジトリ内のアクティビティからイベントが発生した場合の、[`organization`](/rest/reference/orgs#get-an-organization)オブジェクトを含むwebhookペイロード。
diff --git a/translations/ja-JP/data/reusables/webhooks/org_desc_graphql.md b/translations/ja-JP/data/reusables/webhooks/org_desc_graphql.md
index 4bd5d803b1..04ba776b1c 100644
--- a/translations/ja-JP/data/reusables/webhooks/org_desc_graphql.md
+++ b/translations/ja-JP/data/reusables/webhooks/org_desc_graphql.md
@@ -1 +1 @@
-`organization` | `object` | Webhook payloads contain the [`organization`](/graphql/reference/objects#organization) object when the webhook is configured for an organization or the event occurs from activity in a repository owned by an organization.
+`organization` | `object` | webhookがOrganizationに対して設定されている場合、あるいはOrganizationが所有するリポジトリ内のアクティビティからイベントが発生した場合の、[`organization`](/graphql/reference/objects#organization)オブジェクトを含むwebhookペイロード。
diff --git a/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md b/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md
index 0b539ee364..60a8a44ef9 100644
--- a/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/organization_short_desc.md
@@ -1 +1 @@
-Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[organizations](/rest/reference/orgs)" REST API.
+Organization及びそのメンバーと関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Organization](/rest/reference/orgs)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/package_properties.md b/translations/ja-JP/data/reusables/webhooks/package_properties.md
index 231b9e34ae..8f13be672b 100644
--- a/translations/ja-JP/data/reusables/webhooks/package_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/package_properties.md
@@ -1,4 +1,4 @@
-| キー        | 種類       | 説明                                           |
-| --------- | -------- | -------------------------------------------- |
-| `action`  | `string` | 実行されたアクション. Can be `published` or `updated`. |
-| `package` | `オブジェクト` | Information about the package.               |
+| キー        | 種類       | 説明                                         |
+| --------- | -------- | ------------------------------------------ |
+| `action`  | `string` | 実行されたアクション. `published`あるいは`updated`のいずれか。 |
+| `package` | `オブジェクト` | パッケージに関する情報。                               |
diff --git a/translations/ja-JP/data/reusables/webhooks/page_build_short_desc.md b/translations/ja-JP/data/reusables/webhooks/page_build_short_desc.md
index dda5755d88..83adb12112 100644
--- a/translations/ja-JP/data/reusables/webhooks/page_build_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/page_build_short_desc.md
@@ -1 +1 @@
-Represents an attempted build of a {% data variables.product.prodname_pages %} site, whether successful or not. A push to a {% data variables.product.prodname_pages %} enabled branch (`gh-pages` for project pages, the default branch for user and organization pages) triggers this event.
+成功か否かにかかわらず、{% data variables.product.prodname_pages %}サイトの試行されたビルドを表します。 {% data variables.product.prodname_pages %}が有効化されたブランチ（プロジェクトのPagesなら`gh-pages`、ユーザ及びOrganizationのPagesならデフォルトブランチ）へのプッシュがこのイベントをトリガーします。
diff --git a/translations/ja-JP/data/reusables/webhooks/payload_url.md b/translations/ja-JP/data/reusables/webhooks/payload_url.md
index f48cdfee0e..5ef942f616 100644
--- a/translations/ja-JP/data/reusables/webhooks/payload_url.md
+++ b/translations/ja-JP/data/reusables/webhooks/payload_url.md
@@ -1 +1 @@
-The payload URL is the URL of the server that will receive the webhook `POST` requests.
+ペイロードURLは、webhookの`POST`リクエストを受信するサーバーのURLです。
diff --git a/translations/ja-JP/data/reusables/webhooks/ping_short_desc.md b/translations/ja-JP/data/reusables/webhooks/ping_short_desc.md
index 32c9de4bdd..5eb451555c 100644
--- a/translations/ja-JP/data/reusables/webhooks/ping_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/ping_short_desc.md
@@ -1 +1 @@
-新しいwebhookが作成されると、シンプルな`ping`イベントが送信され、webhookが正しくセットアップされたことを知らせます。 This event isn't stored so it isn't retrievable via the [Events API](/rest/reference/activity#ping-a-repository-webhook) endpoint.
+新しいwebhookが作成されると、シンプルな`ping`イベントが送信され、webhookが正しくセットアップされたことを知らせます。 このイベントは保存されないので、[Events API](/rest/reference/activity#ping-a-repository-webhook)エンドポイントを通じて取り出すことはできません。
diff --git a/translations/ja-JP/data/reusables/webhooks/project_card_properties.md b/translations/ja-JP/data/reusables/webhooks/project_card_properties.md
index 0e2304eb52..414d9a7b8f 100644
--- a/translations/ja-JP/data/reusables/webhooks/project_card_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/project_card_properties.md
@@ -1,7 +1,7 @@
-| キー                    | 種類        | 説明                                                                                                                           |
-| --------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `action`              | `string`  | The action performed on the project card. Can be `created`, `edited`, `moved`, `converted`, or `deleted`.                    |
-| `変更`                  | `オブジェクト`  | The changes to the project card if the action was `edited` or `converted`.                                                   |
-| `changes[note][from]` | `string`  | The previous version of the note if the action was `edited` or `converted`.                                                  |
-| `after_id`            | `integer` | The id of the card that this card now follows if the action was "moved". Will be `null` if it is the first card in a column. |
-| `project_card`        | `オブジェクト`  | The [project card](/rest/reference/projects#cards) itself.                                                                   |
+| キー                    | 種類        | 説明                                                                          |
+| --------------------- | --------- | --------------------------------------------------------------------------- |
+| `action`              | `string`  | プロジェクトカードで行われたアクション。 `created`、`edited`、`moved`、`converted`、`deleted`のいずれか。 |
+| `changes`             | `オブジェクト`  | アクションが`edited`もしくは`converted`だった場合、プロジェクトカードへの変更。                           |
+| `changes[note][from]` | `string`  | アクションが`edited`もしくは`converted`だった場合、以前のバージョンのノート。                            |
+| `after_id`            | `integer` | アクションが"moved"だった場合、このカードがフォローするようになったカードのid。 これが列内の最初のカードの場合は`null`になる。     |
+| `project_card`        | `オブジェクト`  | [プロジェクトカード](/rest/reference/projects#cards)自体。                              |
diff --git a/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md b/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md
index 6fe2904d9e..f8e13d9f17 100644
--- a/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/project_card_short_desc.md
@@ -1 +1 @@
-Activity related to project cards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project cards](/rest/reference/projects#cards)" REST API.
+プロジェクトカードに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[プロジェクトカード](/rest/reference/projects#cards)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/project_column_properties.md b/translations/ja-JP/data/reusables/webhooks/project_column_properties.md
index fc42b2e783..d9a27eb628 100644
--- a/translations/ja-JP/data/reusables/webhooks/project_column_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/project_column_properties.md
@@ -1,7 +1,7 @@
-| キー                    | 種類        | 説明                                                                                                                                  |
-| --------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| `action`              | `string`  | The action that was performed on the project column. Can be one of `created`, `edited`, `moved` or `deleted`.                       |
-| `変更`                  | `オブジェクト`  | The changes to the project column if the action was `edited`.                                                                       |
-| `changes[name][from]` | `string`  | The previous version of the name if the action was `edited`.                                                                        |
-| `after_id`            | `integer` | The id of the column that this column now follows if the action was "moved". Will be `null` if it is the first column in a project. |
-| `project_column`      | `オブジェクト`  | The [project column](/rest/reference/projects#columns) itself.                                                                      |
+| キー                    | 種類        | 説明                                                                       |
+| --------------------- | --------- | ------------------------------------------------------------------------ |
+| `action`              | `string`  | プロジェクト列で実行されたアクション。 `created`、`edited`、`moved`、`deleted`のいずれか。           |
+| `changes`             | `オブジェクト`  | アクションが`edited`だった場合、プロジェクト列に対する変更。                                       |
+| `changes[name][from]` | `string`  | アクションが`edited`だった場合、以前のバージョンの名前。                                         |
+| `after_id`            | `integer` | アクションが"moved"だった場合、この列がフォローするようになった列のid。 これがプロジェクト内の最初の列だった場合は`null`になる。 |
+| `project_column`      | `オブジェクト`  | [プロジェクトの列](/rest/reference/projects#columns)自体。                          |
diff --git a/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md b/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md
index 35d38e4101..429ed5821c 100644
--- a/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/project_column_short_desc.md
@@ -1 +1 @@
-Activity related to columns in a project board. {% data reusables.webhooks.action_type_desc %} For more information, see the "[project columns](/rest/reference/projects#columns)" REST API.
+プロジェクトボード内の列に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[プロジェクトの列](/rest/reference/projects#columns)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/project_properties.md b/translations/ja-JP/data/reusables/webhooks/project_properties.md
index af4aabb07b..ba7245d4fc 100644
--- a/translations/ja-JP/data/reusables/webhooks/project_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/project_properties.md
@@ -1,7 +1,7 @@
-| キー                    | 種類       | 説明                                                                                                                   |
-| --------------------- | -------- | -------------------------------------------------------------------------------------------------------------------- |
-| `action`              | `string` | The action that was performed on the project. Can be one of `created`, `edited`, `closed`, `reopened`, or `deleted`. |
-| `変更`                  | `オブジェクト` | The changes to the project if the action was `edited`.                                                               |
-| `changes[name][from]` | `string` | The previous version of the name if the action was `edited`.                                                         |
-| `changes[body][from]` | `string` | The previous version of the body if the action was `edited`.                                                         |
-| `project`             | `オブジェクト` | The [project](/rest/reference/projects) itself.                                                                      |
+| キー                    | 種類       | 説明                                                                        |
+| --------------------- | -------- | ------------------------------------------------------------------------- |
+| `action`              | `string` | プロジェクトで実行されたアクション。 `created`、`edited`、`closed`、`reopened`、`deleted`のいずれか。 |
+| `changes`             | `オブジェクト` | アクションが`edited`の場合、プロジェクトへの変更。                                             |
+| `changes[name][from]` | `string` | アクションが`edited`だった場合、以前のバージョンの名前。                                          |
+| `changes[body][from]` | `string` | アクションが`edited`だった場合の、以前のバージョンのボディ。                                        |
+| `project`             | `オブジェクト` | [プロジェクト](/rest/reference/projects)自体。                                     |
diff --git a/translations/ja-JP/data/reusables/webhooks/project_short_desc.md b/translations/ja-JP/data/reusables/webhooks/project_short_desc.md
index 2ae5d8be21..f3461a7c3f 100644
--- a/translations/ja-JP/data/reusables/webhooks/project_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/project_short_desc.md
@@ -1 +1 @@
-Activity related to project boards. {% data reusables.webhooks.action_type_desc %} For more information, see the "[projects](/rest/reference/projects)" REST API.
+プロジェクトボードに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[プロジェクト](/rest/reference/projects)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/public_short_desc.md b/translations/ja-JP/data/reusables/webhooks/public_short_desc.md
index 9333dc3841..fbb7eef3b7 100644
--- a/translations/ja-JP/data/reusables/webhooks/public_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/public_short_desc.md
@@ -1 +1 @@
-When a private repository is made public.  Without a doubt: the best {% data variables.product.product_name %} event. 
+プライベートリポジトリがパブリックにされたとき。  間違いなく: 最高の{% data variables.product.product_name %}イベント。 
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md
index 8f68bd4681..4c5f0d3e08 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                                                                                                           |
-| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. Can be one of `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, and `synchronize`. |
+| キー       | 種類       | 説明                                                                                                                                                     |
+| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `action` | `string` | 実行されたアクション. `opened`、`closed`、`reopened`、`assigned`、`unassigned`、`review_requested`、`review_request_removed`、`labeled`、`unlabeled`、`synchronize`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md
index 948f78e0b0..2354c7f903 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_properties.md
@@ -1 +1 @@
-`number`|`integer` | The pull request number. `changes`|`object`| The changes to the comment if the action was `edited`. `changes[title][from]`|`string` | The previous version of the title if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) itself.
+`number`|`integer` | Pull Requestの番号。 `changes`|`object`| アクションが`edited`の場合、コメントへの変更。 `changes[title][from]`|`string` | アクションが`edited`の場合、以前のバージョンのタイトル。 `changes[body][from]`|`string` | アクションが`edited`の場合、以前のバージョンのボディ。 `pull_request`|`object` | [Pull Request](/rest/reference/pulls)自体。
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
index e606eabb55..02ce5ac01b 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                             |
-| -------- | -------- | -------------------------------------------------------------- |
-| `action` | `string` | The action that was performed on the comment. `created `になりうる。 |
+| キー       | 種類       | 説明                                 |
+| -------- | -------- | ---------------------------------- |
+| `action` | `string` | コメント上で実行されたアクション。 `created `になりうる。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md
index 1b854809c7..30f26c6c22 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_properties.md
@@ -1 +1 @@
-`changes`|`object`| The changes to the comment if the action was `edited`. `changes[body][from]`|`string` | The previous version of the body if the action was `edited`. `pull_request`|`object` | The [pull request](/rest/reference/pulls) the comment belongs to. `comment`|`object` | The [comment](/rest/reference/pulls#comments) itself.
+`changes`|`object`| アクションが`edited`の場合、コメントへの変更。 `changes[body][from]`|`string` | アクションが`edited`の場合、以前のバージョンのボディ。 `pull_request`|`object` | コメントが属する[Pull Request](/rest/reference/pulls)。 `comment`|`object` | [コメント](/rest/reference/pulls#comments)自体。
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md
index e002a3be49..9894cbd7ce 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_short_desc.md
@@ -1 +1 @@
-Activity related to pull request review comments in the pull request's unified diff. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request review comments](/rest/reference/pulls#comments)" REST API.
+Pull Requestの統合diff中のPull Requestレビューコメントに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Pull Requestのレビューコメント](/rest/reference/pulls#comments)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
index 58ed157537..15ebe2a70a 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                             |
-| -------- | -------- | ---------------------------------------------------------------------------------------------- |
-| `action` | `string` | The action that was performed on the comment. Can be one of `created`, `edited`, or `deleted`. |
+| キー       | 種類       | 説明                                                   |
+| -------- | -------- | ---------------------------------------------------- |
+| `action` | `string` | コメント上で実行されたアクション。 `created`、`edited`、`deleted`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md
index cb0f3b9e46..4dbe5efb0f 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md
@@ -1,6 +1,6 @@
-| キー                    | 種類       | 説明                                                                |
-| --------------------- | -------- | ----------------------------------------------------------------- |
-| `action`              | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`submitted` - A pull request review is submitted into a non-pending state.</li><li>`edited` - The body of a review has been edited.</li><li>`dismissed` - A review has been dismissed.</li></ul>                 |
-| `pull_request`        | `オブジェクト` | The [pull request](/rest/reference/pulls) the review pertains to. |
-| `レビュー`                | `オブジェクト` | The review that was affected.                                     |
-| `changes[body][from]` | `string` | The previous version of the body if the action was `edited`.      |
+| キー                    | 種類       | 説明                                                |
+| --------------------- | -------- | ------------------------------------------------- |
+| `action`              | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`submitted` - Pull Requestレビューが非保留状態にサブミットされた。</li><li>`edited` - レビューのボディが編集された。</li><li>`dismissed` - レビューが却下された。</li></ul> |
+| `pull_request`        | `オブジェクト` | レビューが関連する[Pull Request](/rest/reference/pulls)。   |
+| `review`              | `オブジェクト` | 影響されるレビュー。                                        |
+| `changes[body][from]` | `string` | アクションが`edited`だった場合の、以前のバージョンのボディ。                |
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md
index 3329d4b62e..6dee6e4958 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_short_desc.md
@@ -1 +1 @@
-Activity related to pull request reviews. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull request reviews](/rest/reference/pulls#reviews)" REST API.
+Pull Requestレビューに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Pull Requestレビュー](/rest/reference/pulls#reviews)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md b/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md
index 45bc1b5789..7bbb6c4ae6 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_short_desc.md
@@ -1 +1 @@
-Activity related to pull requests. {% data reusables.webhooks.action_type_desc %} For more information, see the "[pull requests](/rest/reference/pulls)" REST API.
+Pull Requestに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Pull Request](/rest/reference/pulls)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md
index 18b8b78c01..20e9b9ec77 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. |
+| キー       | 種類       | 説明                                                |
+| -------- | -------- | ------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`: アクションが`closed`で`merged`キーが`false`なら、Pull Requestはマージされていないコミットともにクローズされています。 アクションが`closed`で`merged`キーが`true`であれば、Pull Requestはマージされています。</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Pull Requestが追跡しているブランチがPull Requestのソースブランチと同期されたときにトリガーされます。これは、ソースブランチが更新されたときに生じます。</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/ja-JP/data/reusables/webhooks/push_short_desc.md b/translations/ja-JP/data/reusables/webhooks/push_short_desc.md
index 9d434a42fb..d370bc4f94 100644
--- a/translations/ja-JP/data/reusables/webhooks/push_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/push_short_desc.md
@@ -1 +1 @@
-One or more commits are pushed to a repository branch or tag.
+リポジトリのブランチもしくはタグに、1つ以上のコミットがプッシュされました。
diff --git a/translations/ja-JP/data/reusables/webhooks/pusher_type_desc.md b/translations/ja-JP/data/reusables/webhooks/pusher_type_desc.md
index 867fad6a56..511c68a0d2 100644
--- a/translations/ja-JP/data/reusables/webhooks/pusher_type_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/pusher_type_desc.md
@@ -1 +1 @@
-`pusher_type`|`string`| The pusher type for the event. Can be either `user` or a deploy key.
\ No newline at end of file
+`pusher_type`|`string`| イベントのプッシュ者の種類。 `user`もしくはデプロイキー。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/webhooks/release_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/release_event_api_properties.md
index a699d7c2e6..94296a1ee2 100644
--- a/translations/ja-JP/data/reusables/webhooks/release_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/release_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                              |
-| -------- | -------- | ------------------------------- |
-| `action` | `string` | 実行されたアクション. Can be `published`. |
+| キー       | 種類       | 説明                            |
+| -------- | -------- | ----------------------------- |
+| `action` | `string` | 実行されたアクション. `published`になりうる。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/release_short_desc.md b/translations/ja-JP/data/reusables/webhooks/release_short_desc.md
index a8d506f409..29cd01afca 100644
--- a/translations/ja-JP/data/reusables/webhooks/release_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/release_short_desc.md
@@ -1 +1 @@
-Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/rest/reference/repos#releases)" REST API.
+リリースに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[リリース](/rest/reference/repos#releases)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md
index 45743ee342..c4f213b6ec 100644
--- a/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md
@@ -1,3 +1,3 @@
 | キー       | 種類       | 説明                                                                                                                                                                                                                               |
 | -------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`published`: a release, pre-release, or draft of a release is published</li><li>`unpublished`: a release or pre-release is deleted</li><li>`created`: a draft is saved, or a release or pre-release is published without previously being saved as a draft</li><li>`edited`: a release, pre-release, or draft release is edited</li><li>`deleted`: a release, pre-release, or draft release is deleted</li><li>`prereleased`: a pre-release is created</li><li>`released`: a release or draft of a release is published, or a pre-release is changed to a release</li> |
+| `action` | `string` | 実行されたアクション. 次のいずれかになります。<ul><li>`published`: リリース、プレリリース、あるいはリリースのドラフトが公開された</li><li>`unpublished`: リリースもしくはプレリリースが削除された</li><li>`created`: ドラフトが保存された、あるいは以前にドラフトとして保存されることなくリリースもしくはプレリリースが公開された</li><li>`edited`: リリース、プレリリース、あるいはドラフトのリリースが編集された</li><li>`deleted`: リリース、プレリリース、あるいはドラフトリリースが削除された</li><li>`prereleased`: プレリリースが作成された</li><li>`released`: リリースもしくはリリースのドラフトが公開されたか、プレリリースがリリースに変更された</li> |
diff --git a/translations/ja-JP/data/reusables/webhooks/repo_desc.md b/translations/ja-JP/data/reusables/webhooks/repo_desc.md
index e0eca4218d..b7bbbd0317 100644
--- a/translations/ja-JP/data/reusables/webhooks/repo_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/repo_desc.md
@@ -1 +1 @@
-`repository` | `object` | The [`repository`](/rest/reference/repos#get-a-repository) where the event occurred.
+`repository` | `object` | イベントが発生した[`リポジトリ`](/rest/reference/repos#get-a-repository)。
diff --git a/translations/ja-JP/data/reusables/webhooks/repo_desc_graphql.md b/translations/ja-JP/data/reusables/webhooks/repo_desc_graphql.md
index 7cfc041ade..2757c8f7e5 100644
--- a/translations/ja-JP/data/reusables/webhooks/repo_desc_graphql.md
+++ b/translations/ja-JP/data/reusables/webhooks/repo_desc_graphql.md
@@ -1 +1 @@
-`repository` | `object` | The [`repository`](/graphql/reference/objects#repository) where the event occurred.
\ No newline at end of file
+`repository` | `object` | イベントが発生した[`リポジトリ`](/graphql/reference/objects#repository)。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/webhooks/repository_import_properties.md b/translations/ja-JP/data/reusables/webhooks/repository_import_properties.md
index dd659fb1c0..3f2461030f 100644
--- a/translations/ja-JP/data/reusables/webhooks/repository_import_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/repository_import_properties.md
@@ -1,3 +1,3 @@
-| キー      | 種類       | 説明                                                                                      |
-| ------- | -------- | --------------------------------------------------------------------------------------- |
-| `ステータス` | `string` | The final state of the import. This can be one of `success`, `cancelled`, or `failure`. |
+| キー       | 種類       | 説明                                                 |
+| -------- | -------- | -------------------------------------------------- |
+| `status` | `string` | インポートの最終の状態。 `success`、`cancelled`、`failure`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md b/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md
index d4b6cf9aa0..0e19521c41 100644
--- a/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/repository_import_short_desc.md
@@ -1 +1 @@
-Activity related to a repository being imported to GitHub. {% data reusables.webhooks.action_type_desc %} For more information, see the "[source imports](/rest/reference/migrations#source-imports)" REST API.
+GitHubにインポートされるリポジトリに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[ソースのインポート](/rest/reference/migrations#source-imports)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md b/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md
index b3e90e8d64..5a590e6e66 100644
--- a/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/repository_short_desc.md
@@ -1 +1 @@
-Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[repositories](/rest/reference/repos)" REST API.
+リポジトリに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[リポジトリ](/rest/reference/repos)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_properties.md b/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_properties.md
index a79b91787c..6ccc8f9423 100644
--- a/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_properties.md
@@ -1,4 +1,4 @@
-| キー       | 種類       | 説明                                                                |
-| -------- | -------- | ----------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. This can be one of `create`, `dismiss`, or `resolve`. |
-| `アラート`   | `オブジェクト` | The security alert of the vulnerable dependency.                  |
+| キー       | 種類       | 説明                                             |
+| -------- | -------- | ---------------------------------------------- |
+| `action` | `string` | 実行されたアクション. `create`、`dismiss`、`resolve`のいずれか。 |
+| `alert`  | `オブジェクト` | 脆弱性のある依存関係のセキュリティアラート。                         |
diff --git a/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md b/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md
index 6275d07399..4aea385281 100644
--- a/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md
@@ -1 +1 @@
-リポジトリ内のセキュリティ脆弱性アラートに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} For more information, see the "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)".
+リポジトリ内のセキュリティ脆弱性アラートに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/secret.md b/translations/ja-JP/data/reusables/webhooks/secret.md
index 95f3a341ca..9ed57a38dc 100644
--- a/translations/ja-JP/data/reusables/webhooks/secret.md
+++ b/translations/ja-JP/data/reusables/webhooks/secret.md
@@ -1 +1 @@
-Setting a webhook secret allows you to ensure that `POST` requests sent to the payload URL are from {% data variables.product.product_name %}. When you set a secret, you'll receive the {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature` and `X-Hub-Signature-256` headers{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` header{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256` header{% endif %} in the webhook `POST` request. For more information on how to use a secret with a signature header to secure your webhook payloads, see "[Securing your webhooks](/webhooks/securing/)."
+webhookのシークレットを設定することで、ペイロードのURLに送信される`POST`リクエストが、{% data variables.product.product_name %}からのものであることが保証できます。 シークレットを設定すると、webhookの`POST`リクエスト中の{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature`及び`X-Hub-Signature-256`ヘッダ{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`ヘッダ{% elsif currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`ヘッダ{% endif %}を受信することになります。 署名ヘッダでシークレットを使用してwebhookのペイロードをセキュアに保つ方法に関する詳細については、「[webhookをセキュアに保つ](/webhooks/securing/)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md
index 4afbdd9682..c06dd8baec 100644
--- a/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md
@@ -1,4 +1,4 @@
-| キー       | 種類       | 説明                                                                   |
-| -------- | -------- | -------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. This can be either `created`, `resolved`, or `reopened`. |
-| `アラート`   | `オブジェクト` | The secret scanning alert involved in the event.                     |
+| キー       | 種類       | 説明                                                |
+| -------- | -------- | ------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. `created`、`resolved`、`reopened`のいずれか。 |
+| `alert`  | `オブジェクト` | このイベントに関わるSecret Scanningアラート。                    |
diff --git a/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
index 5da7e75271..6e39c71e24 100644
--- a/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
@@ -1 +1 @@
-Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).”
+リポジトリ中のSecret Scanningアラートに関連するアクティビティ。 アクティビティのタイプは、ペイロードオブジェクトのactionプロパティで指定されます。 詳しい情報については「[Secret Scanningについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/sender_desc.md b/translations/ja-JP/data/reusables/webhooks/sender_desc.md
index 218063f9e0..c7a74ac1d0 100644
--- a/translations/ja-JP/data/reusables/webhooks/sender_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/sender_desc.md
@@ -1 +1 @@
-`sender` | `object` | The user that triggered the event.
+`sender` | `object` | このイベントをトリガーしたユーザ。
diff --git a/translations/ja-JP/data/reusables/webhooks/sponsorship_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/sponsorship_event_api_properties.md
index f0abfe5272..09e310e0ce 100644
--- a/translations/ja-JP/data/reusables/webhooks/sponsorship_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/sponsorship_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                 |
-| -------- | -------- | ---------------------------------- |
-| `action` | `string` | 実行されたアクション. This can be `created`. |
+| キー       | 種類       | 説明                          |
+| -------- | -------- | --------------------------- |
+| `action` | `string` | 実行されたアクション. `created`になりうる。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/sponsorship_properties.md b/translations/ja-JP/data/reusables/webhooks/sponsorship_properties.md
index 939d7fd0ea..eb090a923a 100644
--- a/translations/ja-JP/data/reusables/webhooks/sponsorship_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/sponsorship_properties.md
@@ -1 +1 @@
-`effective_date` | `string` | The `pending_cancellation` and `pending_tier_change` event types will include the date the cancellation or tier change will take effect. `changes[tier][from]` | `object` | The `tier_changed` and `pending_tier_change` will include the original tier before the change or pending change. For more information, see the [pending tier change payload](/webhooks/event-payloads#webhook-payload-example-when-someone-downgrades-a-sponsorship). `changes[privacy_level][from]` | `string` | The `edited` event types include the details about the change when someone edits a sponsorship to change the privacy.
+`effective_date` | `string` | `pending_cancellation`及び`pending_tier_change`のイベントタイプには、キャンセルあるいは層の変更が有効になる期日が含まれます。 `changes[tier][from]` | `object` | `tier_changed`及び`pending_tier_change`には、変更あるいは保留されている変更の元の層が含まれます。 詳しい情報については[保留されている層の変更のペイロード](/webhooks/event-payloads#webhook-payload-example-when-someone-downgrades-a-sponsorship)を参照してください。 `changes[privacy_level][from]` | `string` | `edited`のイベントタイプには、誰かがプライバシーを変更するためにスポンサーシップを編集したときの変更に関する詳細が含まれます。
diff --git a/translations/ja-JP/data/reusables/webhooks/sponsorship_short_desc.md b/translations/ja-JP/data/reusables/webhooks/sponsorship_short_desc.md
index 2f62ffe8d8..af876c1f4f 100644
--- a/translations/ja-JP/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)".
+スポンサーシップのリストに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[GitHub Sponsorsについて](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/sponsorship_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/sponsorship_webhook_properties.md
index 04b95206bd..c5a0eaa385 100644
--- a/translations/ja-JP/data/reusables/webhooks/sponsorship_webhook_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/sponsorship_webhook_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                                                                 |
-| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. This can be one of `created`, `cancelled`, `edited`, `tier_changed`, `pending_cancellation`, or `pending_tier_change`. |
+| キー       | 種類       | 説明                                                                                                           |
+| -------- | -------- | ------------------------------------------------------------------------------------------------------------ |
+| `action` | `string` | 実行されたアクション. `created`、`cancelled`、`edited`、`tier_changed`、`pending_cancellation`、`pending_tier_change`のいずれか。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/star_properties.md b/translations/ja-JP/data/reusables/webhooks/star_properties.md
index 52e0bc54a0..005562a457 100644
--- a/translations/ja-JP/data/reusables/webhooks/star_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/star_properties.md
@@ -1,4 +1,4 @@
-| キー           | 種類       | 説明                                                                                                              |
-| ------------ | -------- | --------------------------------------------------------------------------------------------------------------- |
-| `action`     | `string` | 実行されたアクション。 Can be `created` or `deleted`.                                                                      |
-| `starred_at` | `string` | The time the star was created. {% data reusables.shortdesc.iso_8601 %} Will be `null` for the `deleted` action. |
+| キー           | 種類       | 説明                                                                                   |
+| ------------ | -------- | ------------------------------------------------------------------------------------ |
+| `action`     | `string` | 実行されたアクション。 `created`もしくは`deleted`のいずれか。                                             |
+| `starred_at` | `string` | Starが作成された時刻。 `deleted`アクションに対しては、{% data reusables.shortdesc.iso_8601 %}は`null`になる。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/star_short_desc.md b/translations/ja-JP/data/reusables/webhooks/star_short_desc.md
index 9569c6958e..53cfb3586d 100644
--- a/translations/ja-JP/data/reusables/webhooks/star_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/star_short_desc.md
@@ -1 +1 @@
-Activity related to a repository being starred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API.
+Starされるリポジトリに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Star付け](/rest/reference/activity#starring)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/status_short_desc.md b/translations/ja-JP/data/reusables/webhooks/status_short_desc.md
index 6d835788c9..3df6b19c8e 100644
--- a/translations/ja-JP/data/reusables/webhooks/status_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/status_short_desc.md
@@ -1 +1 @@
-When the status of a Git commit changes. {% data reusables.webhooks.action_type_desc %} For more information, see the "[statuses](/rest/reference/repos#statuses)" REST API.
+Gitコミットのステータスが変化したとき。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[ステータス](/rest/reference/repos#statuses)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/team_short_desc.md b/translations/ja-JP/data/reusables/webhooks/team_short_desc.md
index ff27913e21..9ac940ee25 100644
--- a/translations/ja-JP/data/reusables/webhooks/team_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/team_short_desc.md
@@ -1 +1 @@
-Activity related to an organization's team. {% data reusables.webhooks.action_type_desc %} For more information, see the "[teams](/rest/reference/teams)" REST API.
+OrganizationのTeamに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Team](/rest/reference/teams)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/watch_properties.md b/translations/ja-JP/data/reusables/webhooks/watch_properties.md
index e23ed0fd7c..033edede92 100644
--- a/translations/ja-JP/data/reusables/webhooks/watch_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/watch_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                            |
-| -------- | -------- | --------------------------------------------- |
-| `action` | `string` | 実行されたアクション. Currently, can only be `started`. |
+| キー       | 種類       | 説明                               |
+| -------- | -------- | -------------------------------- |
+| `action` | `string` | 実行されたアクション. 現在は`started`にのみなりうる。 |
diff --git a/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md b/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md
index 1b250fb019..4ff33d2c60 100644
--- a/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/watch_short_desc.md
@@ -1 +1 @@
-When someone stars a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[starring](/rest/reference/activity#starring)" REST API.
+誰かがリポジトリにStarを付けたとき。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[Star付け](/rest/reference/activity#starring)」 REST APIを参照してください。
diff --git a/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md
index 1dd3383c2f..4c7740d5fe 100644
--- a/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,4 +1,4 @@
-You can use the repository, organization, and app webhook REST APIs to create, update, delete, and ping webhooks. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}You can also use the REST API to change the configuration of the webhook. For example, you can modify the payload URL, content type, SSL verification, and secret. {% endif %}For more information, see:
-- [Repository Webhooks REST API](/rest/reference/repos#webhooks)
-- [Organization Webhooks REST API](/rest/reference/orgs#webhooks){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-- [GitHub App Webhooks REST API](/rest/reference/apps#webhooks){% endif %}
+webhookの作成、更新、削除、pingには、リポジトリ、Organization、アプリケーションのwebhook REST APIが使用できます。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}webhookの設定の変更にもREST APIが使用できます。 たとえば、ペイロードURL、コンテントタイプ、SSLの検証、シークレットを変更できます。 {% endif %}詳しい情報については以下を参照してください。
+- [リポジトリwebhook REST API](/rest/reference/repos#webhooks)
+- [Organization web hook REST API](/rest/reference/orgs#webhooks){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- [GitHub App webhook REST API](/rest/reference/apps#webhooks){% endif %}
diff --git a/translations/ja-JP/data/reusables/webhooks/webhooks_intro.md b/translations/ja-JP/data/reusables/webhooks/webhooks_intro.md
index eb7b435376..abd24889a6 100644
--- a/translations/ja-JP/data/reusables/webhooks/webhooks_intro.md
+++ b/translations/ja-JP/data/reusables/webhooks/webhooks_intro.md
@@ -1 +1 @@
-When configuring a webhook, you can use the UI or API to choose which events will send you payloads. Only subscribing to the specific events you plan on handling limits the number of HTTP requests to your server. You can also subscribe to all current and future events. By default, webhooks are only subscribed to the push event. You can change the list of subscribed events anytime.
+webhookを設定する際には、ペイロードを送信するイベントを選択するためにUIもしくはAPIが使用できます。 処理する計画の特定のイベントだけをサブスクライブすることによってのみ、サーバーへのHTTPリクエスト数を制限できます。 現在、そして未来のすべてのイベントをサブスクライブすることもできます。 デフォルトでは、webhookはプッシュイベントだけをサブスクライブします。 サブスクライブするイベントのリストは、いつでも変更できます。
diff --git a/translations/ja-JP/data/reusables/webhooks/webhooks_ssl.md b/translations/ja-JP/data/reusables/webhooks/webhooks_ssl.md
index c0d40e6392..66aff77cf1 100644
--- a/translations/ja-JP/data/reusables/webhooks/webhooks_ssl.md
+++ b/translations/ja-JP/data/reusables/webhooks/webhooks_ssl.md
@@ -1 +1 @@
-If your "Payload URL" is a secure site (HTTPS), you will have the option to configure the SSL verification settings. If your "Payload URL" is not secure (HTTP), GitHub will not display this option. By default, GitHub verifies the SSL certificate of your website when delivering webhook payloads. SSL verification helps ensure that hook payloads are delivered to your URL endpoint securely. You have the option to disable SSL, but we recommend keeping **Enable SSL verification** selected.
+「ペイロードURL」がセキュアなサイト（HTTPS）の場合、SSL検証の設定をするオプションがあります。 「ペイロードURL」がセキュアでない（HTTP）場合、GitHubはこのオプションを表示しません。 デフォルトでは、webhookのペイロードを配信する際に、GitHubはWebサイトのSSL証明書を検証します。 SSL検証は、フックのペイロードがURLのエンドポイントにセキュアに配信されることを保証するための役に立ちます。 SSLを無効化するオプションもありますが、**Enable SSL verification（SSLの検証の有効化）**を選択しておくことをおすすめします。
diff --git a/translations/ja-JP/data/reusables/webhooks/workflow_desc.md b/translations/ja-JP/data/reusables/webhooks/workflow_desc.md
index 6f716dbe56..1c828f759b 100644
--- a/translations/ja-JP/data/reusables/webhooks/workflow_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/workflow_desc.md
@@ -1 +1 @@
-`workflow` | `object` | The workflow that generated the workflow run.
+`workflow` | `object` | ワークフローの実行を生成したワークフロー。
diff --git a/translations/ja-JP/data/reusables/webhooks/workflow_run_desc.md b/translations/ja-JP/data/reusables/webhooks/workflow_run_desc.md
index 486a20dcd1..6777e15832 100644
--- a/translations/ja-JP/data/reusables/webhooks/workflow_run_desc.md
+++ b/translations/ja-JP/data/reusables/webhooks/workflow_run_desc.md
@@ -1,5 +1,5 @@
-This event occurs when a workflow run is requested or completed, and allows you to execute a workflow based on the finished result of another workflow. A workflow run is triggered regardless of the result of the previous workflow.
+このイベントは、ワークフローの実行がリクエストされたか完了した場合に生じ、他のワークフローの終了した結果に基づいてワークフローを実行できるようにしてくれます。 ワークフローの実行は、以前のワークフローの結果にかかわらずトリガーされます。
 
-For example, if your `pull_request` workflow generates build artifacts, you can create a new workflow that uses `workflow_run` to analyze the results and add a comment to the original pull request.
+たとえば、`pull_request`ワークフローがビルドの成果物を生成するなら、`workflow_run`を使って結果を分析し、オリジナルのPull Requestにコメントする新しいワークフローを作成できます。
 
-The workflow started by the `workflow_run` event is able to access secrets and write tokens, even if the previous workflow was not. This is useful in cases where the previous workflow is intentionally not privileged, but you need to take a privileged action in a later workflow.
+`workflow_run`イベントによってStarされたワークフローは、以前のワークフローができなくても、シークレットや書き込みトークンにアクセスできます。 これは、以前のワークフローが意図的に権限を与えられていない場合に役立ちますが、権限を与えられたアクションは後のワークフローで行わなければなりません。
diff --git a/translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md b/translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md
index 55e9281d3e..68bafd1b5c 100644
--- a/translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md
@@ -1,4 +1,4 @@
-| キー             | 種類       | 説明                                                                                                                                                                    |
-| -------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`       | `string` | 実行されたアクション. Can be one of `requested` or `completed`.                                                                                                                 |
-| `workflow_run` | `オブジェクト` | The workflow run. Many `workflow_run` keys, such as `head_branch`, `conclusion`, and `pull_requests` are the same as those in a [`check_suite`](#check_suite) object. |
+| キー             | 種類       | 説明                                                                                                                          |
+| -------------- | -------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `action`       | `string` | 実行されたアクション. `requested`あるいは`completed`のいずれか。                                                                                |
+| `workflow_run` | `オブジェクト` | ワークフローの実行。 `head_branch`、`conclusion`、`pull_requests`といった多くの`workflow_run`のキーは、[`check_suite`](#check_suite)オブジェクト内のそれらと同じ。 |
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 6d783b4ad0..853e44e6f9 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -3,15 +3,15 @@ header:
   github_docs: GitHub Docs
   contact: お問い合わせ
   notices:
-    ghae_silent_launch: GitHub AE is currently under limited release. Please <a href="https://enterprise.github.com/contact">contact our Sales Team</a> to find out more.
-    release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently available as a release candidate. For more information, see "<a href="/admin/overview/about-upgrades-to-new-releases">About upgrades to new releases</a>."'''
+    ghae_silent_launch: GitHub AEは、現在限定リリース中です。詳細については<a href="https://enterprise.github.com/contact">営業チームにお問い合わせ</a>ください。
+    release_candidate: '# バージョン名はincludes/header-notification.htmlを通じて下のテキストの前に表示されます。これは現在リリース候補として利用できます。詳しい情報については「<a href="/admin/overview/about-upgrades-to-new-releases">新しいリリースへのアップグレードについて</a>」を参照してください。'
     localization_complete: ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、<a id="to-english-doc" href="/en">英語のドキュメンテーション</a>をご参照ください。本ページの翻訳に問題がある場合は<a href="https://github.com/contact?form[subject]=translation%20issue%20on%20docs.github.com&form[comments]=">こちらまで</a>ご連絡ください。
     localization_in_progress: こんにちは！このページは開発中か、まだ翻訳中です。最新の正しい情報を得るには、<a id="to-english-doc" href="/en">英語のドキュメンテーション</a>にアクセスしてください。
-    early_access: '📣 Please <b>do not share</b> this URL publicly. This page contains content about an early access feature.'
-    ghes_release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes.
-    ghes_release_notes_upgrade_patch_only: '📣 This is not the <a href="#{{ latestPatch }}">latest patch release</a> of Enterprise Server. {% data ui.header.notices.ghes_release_notes_use_latest %}'
-    ghes_release_notes_upgrade_release_only: '📣 This is not the <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">latest release</a> of Enterprise Server. {% data ui.header.notices.ghes_release_notes_use_latest %}'
-    ghes_release_notes_upgrade_patch_and_release: '📣 This is not the <a href="#{{ latestPatch }}">latest patch release</a> of this release series, and this is not the <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">latest release</a> of Enterprise Server. {% data ui.header.notices.ghes_release_notes_use_latest %}'
+    early_access: '📣 このURLは公に<b>共有しないで</b>ください。このページには、早期アクセスの機能に関する内容が含まれています。'
+    ghes_release_notes_use_latest: 最新のセキュリティ、パフォーマンス、バグフィックスのために、最新のリリースをお使いください。
+    ghes_release_notes_upgrade_patch_only: '📣 これはEnterprise Serverの<a href="#{{ latestPatch }}">最新パッチリリース</a>ではありません。{% data ui.header.notices.ghes_release_notes_use_latest %}'
+    ghes_release_notes_upgrade_release_only: '📣 これはEnterprise Sererの<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新リリース</a>ではありません。{% data ui.header.notices.ghes_release_notes_use_latest %}'
+    ghes_release_notes_upgrade_patch_and_release: '📣 これは、このリリースシリーズの<a href="#{{ latestPatch }}">最新のパッチリリース</a>ではなく、Enterprise Serverの<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新リリース</a>でもありません。{% data ui.header.notices.ghes_release_notes_use_latest %}'
 search:
   need_help: お困りですか？
   placeholder: トピックや製品などの検索
@@ -20,7 +20,7 @@ homepage:
   version_picker: バージョン
 toc:
   getting_started: はじめましょう
-  popular_articles: 人気
+  popular: 人気
   guides: ガイド
   whats_new: 更新情報
 pages:
@@ -32,36 +32,28 @@ errors:
   we_track_errors: 弊社はこれらのエラーを自動的に追跡しますが、問題が生じ続けるなら弊社に連絡をしてください。
   page_doesnt_exist: 指定されたページは存在しません。
 support:
-  still_need_help: Still need help?
+  still_need_help: 問題がまだ解決していませんか？
   contact_support: サポートへの連絡
-  ask_community: Ask the GitHub community
+  ask_community: GitHubコミュニティで質問する
 helpfulness:
-  able_to_find: Did this doc help you?
+  able_to_find: このドキュメントは役立ちましたか？
   yes: true
   no: false
-  yes_feedback: Want to learn about new docs features and updates? Sign up for updates!
+  yes_feedback: 新しいドキュメントの機能とアップデートについて学びたいですか？アップデートのためにサインアップを！
   email_placeholder: email@example.com
-  no_feedback: We're continually improving our docs. We'd love to hear how we can do better.
-  comment_label: Let us know what we can do better
+  no_feedback: 私たちはドキュメントを継続的に改善しています。改善の方法をお聞かせください。
+  comment_label: 改善の方法をお知らせください。
   optional: 任意
   required: 必須
-  email_label: Can we contact you if we have more questions?
+  email_label: さらに質問がある場合、ご連絡差し上げてもよいでしょうか？
   send: 送信
   feedback: ありがとうございます。フィードバックが送信されました。
 contribution_cta:
-  title: Help us make these docs great!
-  body: All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.
-  button: Make a contribution
+  title: これらのドキュメントを素晴らしいものにするのを手伝ってください！
+  body: GitHubのすべてのドキュメントはオープンソースです。間違っていたり、はっきりしないところがありましたか？Pull Requestをお送りください。
+  button: コントリビューションを行う
   or: OR,
-  to_guidelines: learn how to contribute.
-enterprise_releases_list:
-  title: Enterprise Server Releases
-  currently_supported: Currently supported
-  currently_supported_message: See <a href="https://github.com/enterprise">GitHub Enterprise</a> for information about the latest release.
-  deprecated: Deprecated
-  deprecated_message: 'These docs remain available but are no longer maintained:'
-  deprecated_developer: Deprecated on developer.github.com
-  deprecated_developer_message: 'These docs remain available on the legacy <a href="https://developer.github.com">developer site</a> but are no longer maintained:'
+  to_guidelines: コントリビューションの方法を学んでください。
 products:
   graphql:
     reference:
@@ -127,30 +119,54 @@ footer:
       press: プレス
       shop: ショップ
 product_landing:
-  quick_start: クイックスタート
-  reference_guides: Reference guides
+  quickstart: クイックスタート
+  reference: リファレンス
   overview: 概要
+  guides: ガイド
+  code_examples: コード例
+  search_code_examples: 検索コードの例
+  show_more: 詳細を表示
+  explore_people_and_projects: 人やプロジェクトを調べる
+  sorry: 検索結果はありません
+  no_example: 指定されたフィルタにあった例がないようです。
+  try_another: 他のフィルタを試すか、あなたのコードサンプルを追加してください。
+  no_result: 申し訳ありませんが、指定されたフィルタにマッチするガイドはありません。
+  learn: コードサンプルの追加方法を学ぶ
+  communities_using_discussions: ディスカッションを使用しているコミュニティ
+  add_your_community: コミュニティを追加する
+  sponsor_community: GitHub Sponsorsコミュニティ
+  supported_releases: サポートされているリリース
+  release_notes_for: リリースノート
+  upgrade_from: アップグレード元
+  browse_all_docs: すべてのドキュメントの参照
+  explore_release_notes: リリースノートを調べる
 product_sublanding:
-  start: Start
-  start_path: Start path
-  learning_paths: '{{ allProducts[currentProduct].name }} learning paths'
-  learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject.
-  guides: '{{ allProducts[currentProduct].name }} guides'
+  start: 開始
+  start_path: 開始パス
+  learning_paths: '{{ productMap[currentProduct].name }}の学習パス'
+  learning_paths_desc: 学習パスは、特定の課題をマスターするのに役立つガイド集です。
+  guides: '{{ productMap[currentProduct].name }}のガイド'
   more_guides: その他のガイド
-  load_more: Load more guides
-  all_guides: 'All {{ allProducts[currentProduct].name }} guides'
-  no_result: Sorry, there is no guide that match your filter.
+  load_more: さらにガイドをロード
+  all_guides: 'すべての{{ productMap[currentProduct].name }}のガイド'
   filters:
     type: 種類
-    topic: Topic
+    topic: トピック
     all: すべて
   guide_types:
     overview: 概要
     quick_start: クイックスタート
     tutorial: チュートリアル
-    how_to: How-to guide
+    how_to: ハウツーガイド
     reference: リファレンス
 learning_track_nav:
-  prevGuide: Previous guide
-  nextGuide: Next guide
-contributor_callout: This article is contributed and maintained by
+  prevGuide: 前のガイド
+  nextGuide: 次のガイド
+contributor_callout: この記事は、次の人によってコントリビュートされ、管理されています。
+toggle_images:
+  off: 画像はオフです。クリックして表示
+  on: 画像はオンです。クリックして隠す
+  hide_single: 画像を隠す
+  show_single: 画像を表示
+scroll_button:
+  scroll_to_top: 最上部へスクロール
diff --git a/translations/ja-JP/data/variables/actions.yml b/translations/ja-JP/data/variables/actions.yml
index 29499fda82..df17edeb55 100644
--- a/translations/ja-JP/data/variables/actions.yml
+++ b/translations/ja-JP/data/variables/actions.yml
@@ -1,2 +1,2 @@
 ---
-hosted_runner: 'AE hosted runner'
+hosted_runner: 'AEホストランナー'
diff --git a/translations/ja-JP/data/variables/actions_code_examples.yml b/translations/ja-JP/data/variables/actions_code_examples.yml
index b648ccc73e..71bcc4f5fe 100644
--- a/translations/ja-JP/data/variables/actions_code_examples.yml
+++ b/translations/ja-JP/data/variables/actions_code_examples.yml
@@ -1,72 +1,72 @@
 ---
 - 
-  title: Example services
-  description: Example workflows using service containers
+  title: サービスの例
+  description: サービスコンテナを使うワークフローの例
   languages: JavaScript
   href: actions/example-services
   tags:
-    - service containers
+    - サービスコンテナ
 - 
-  title: Declaratively setup GitHub Labels
-  description: GitHub Action to declaratively setup labels across repos
+  title: GitHubラベルを宣言的にセットアップ
+  description: リポジトリ間にわたってラベルを宣言的にセットアップするGitHub Actions
   languages: JavaScript
   href: lannonbr/issue-label-manager-action
   tags:
     - issues
     - labels
 - 
-  title: Declaratively sync GitHub labels
-  description: GitHub Action to sync GitHub labels in the declarative way
+  title: 宣言的にGitHubラベルを同期
+  description: 宣言的な方法でGitHubラベルを同期するGitHub Action
   languages: 'Go, Dockerfile'
   href: micnncim/action-label-syncer
   tags:
     - issues
     - labels
 - 
-  title: Add releases to GitHub
-  description: Publish GitHub releases in an action
+  title: GitHubへのリリースの追加
+  description: アクションでGitHubリリースを公開
   languages: 'Dockerfile, Shell'
   href: elgohr/Github-Release-Action
   tags:
     - releases
-    - publishing
+    - 公開
 - 
-  title: Publish a docker image to Dockerhub
-  description: A GitHub Action used to build and publish Docker images
+  title: Dockerhubにdockerイメージを公開
+  description: Dockerイメージのビルドと公開に使われるGitHub Action
   languages: 'Dockerfile, Shell'
   href: elgohr/Publish-Docker-Github-Action
   tags:
     - docker
-    - publishing
+    - 公開
     - ビルド
 - 
-  title: Create an issue using content from a file
-  description: A GitHub action to create an issue using content from a file
+  title: ファイルからの内容を使ってIssueを作成
+  description: ファイルからの内容を利用してIssueを作成するGitHub Action
   languages: 'JavaScript, Python'
   href: peter-evans/create-issue-from-file
   tags:
     - issues
 - 
-  title: Publish GitHub Releases with Assets
-  description: GitHub Action for creating GitHub Releases
+  title: アセット付きでGitHubリリースを公開
+  description: GitHubリリースを作成するGitHub Action
   languages: 'TypeScript, Shell, JavaScript'
   href: softprops/action-gh-release
   tags:
     - releases
-    - publishing
+    - 公開
 - 
-  title: GitHub Project Automation+
-  description: Automate GitHub Project cards with any webhook event
+  title: GitHubプロジェクトオートメーション+
+  description: 任意のwebhookイベントでGitHubプロジェクトカードを自動化
   languages: JavaScript
   href: alex-page/github-project-automation-plus
   tags:
     - projects
-    - automation
+    - 自動化
     - issues
     - pull requests
 - 
-  title: Run GitHub Actions Locally with a web interface
-  description: Runs GitHub Actions workflows locally (local)
+  title: WebインターフェースでGitHub Actionsをローカル実行
+  description: GitHub Actionsワークフローをローカルで実行（local）
   languages: 'JavaScript, HTML, Dockerfile, CSS'
   href: phishy/wflow
   tags:
@@ -74,8 +74,8 @@
     - devops
     - docker
 - 
-  title: Run your GitHub Actions locally
-  description: Run GitHub Actions Locally in Terminal
+  title: GitHub Actionsをローカルで実行
+  description: ターミナル内でGitHub Actionsをローカルで実行
   languages: 'Go, Shell'
   href: nektos/act
   tags:
@@ -83,47 +83,47 @@
     - devops
     - docker
 - 
-  title: Build and Publish Android debug APK
-  description: Build and release debug APK from your Android project
+  title: AndroidのデバッグAPKをビルド及び公開
+  description: デバッグAPKをAndroidプロジェクトからビルド及びリリース
   languages: 'Shell, Dockerfile'
   href: ShaunLWM/action-release-debugapk
   tags:
     - android
     - ビルド
 - 
-  title: Generate sequential build numbers for GitHub Actions
-  description: GitHub action for generating sequential build numbers.
+  title: GitHub Actions用の連続したビルド番号の生成
+  description: 連続したビルド番号を生成するためのGitHub Action
   languages: JavaScript
   href: einaregilsson/build-number
   tags:
     - ビルド
-    - automation
+    - 自動化
 - 
-  title: GitHub actions to push back to repository
-  description: Push Git changes to GitHub repository without authentication difficulties
+  title: リポジトリにプッシュバックするGitHub Action
+  description: 認証の問題なくGitHubリポジトリにGitの変更をプッシュ
   languages: 'JavaScript, Shell'
   href: ad-m/github-push-action
   tags:
-    - publishing
+    - 公開
 - 
-  title: Generate release notes based on your events
-  description: Action to auto generate a release note based on your events
+  title: イベントに基づいてリリースノートを生成
+  description: イベントに基づいてリリースノートを自動生成するアクション
   languages: 'Shell, Dockerfile'
   href: Decathlon/release-notes-generator-action
   tags:
     - releases
-    - publishing
+    - 公開
 - 
-  title: Create a GitHub wiki page based on the provided markdown file
-  description: Create a GitHub wiki page based on the provided markdown file
+  title: 提供されたMarkdownファイルに基づいてGitHub wikiページを生成
+  description: 提供されたMarkdownファイルに基づいてGitHub wikiページを生成
   languages: 'Shell, Dockerfile'
   href: Decathlon/wiki-page-creator-action
   tags:
     - wiki
-    - publishing
+    - 公開
 - 
-  title: Label your Pull Requests auto-magically (using committed files)
-  description: GitHub action to label your pull requests auto-magically (using committed files)
+  title: Pull Requestを自動的に魔法のようにラベル付け（コミットされたファイルを使用）
+  description: Pull Requestを自動的に魔法のようにラベル付けするGitHub Action（コミットされたファイルを使用）
   languages: 'TypeScript, Dockerfile, JavaScript'
   href: Decathlon/pull-request-labeler-action
   tags:
@@ -131,32 +131,32 @@
     - issues
     - labels
 - 
-  title: Add Label to your Pull Requests based on the author team name
-  description: GitHub action to label your pull requests based on the author name
+  title: 作者のTeam名に基づいてPull Requestにラベルを追加
+  description: 作者名に基づいてPull Requestをラベル付けするGitHub Action
   languages: 'TypeScript, JavaScript'
   href: JulienKode/team-labeler-action
   tags:
     - プルリクエスト
     - labels
 - 
-  title: Get a list of file changes with a PR/Push
-  description: This action gives you will get outputs of the files that have changed in your repository
+  title: PR/プッシュによるファイル変更のリスト取得
+  description: このアクションで、リポジトリ中で変更されたファイルの出力が得られます。
   languages: 'TypeScript, Shell, JavaScript'
   href: trilom/file-changes-action
   tags:
     - ワークフロー
     - リポジトリ
 - 
-  title: Private actions in any workflow
-  description: Allows private GitHub Actions to be easily reused
+  title: 任意のワークフロー中のプライベートアクション
+  description: プライベートのGitHub Actionsを容易に再利用できるようにします
   languages: 'TypeScript, JavaScript, Shell'
   href: InVisionApp/private-action-loader
   tags:
     - ワークフロー
     - tools
 - 
-  title: Label your issues using the issue's contents
-  description: A GitHub Action to automatically tag issues with labels and assignees
+  title: Issueの内容を使ってIssueにラベル付けします
+  description: ラベルとアサインされた人で自動的にIssueにタグ付けするGitHub Action
   languages: 'JavaScript, TypeScript'
   href: damccorm/tag-ur-it
   tags:
@@ -165,16 +165,16 @@
     - labels
     - issues
 - 
-  title: Rollback a GitHub Release
-  description: A GitHub Action to rollback or delete a release
+  title: GitHubリリースのロールバック
+  description: リリースをロールバックあるいは削除するGitHub Action
   languages: 'JavaScript'
   href: author/action-rollback
   tags:
     - ワークフロー
     - releases
 - 
-  title: Lock closed issues and Pull Requests
-  description: GitHub Action that locks closed issues and pull requests after a period of inactivity
+  title: クローズされたIssue及びPull Requestのロック
+  description: 一定期間アクティビティのなかったあとにクローズされたIssueやPull RequestをロックするGitHub Action
   languages: 'JavaScript'
   href: dessant/lock-threads
   tags:
@@ -182,8 +182,8 @@
     - pull requests
     - ワークフロー
 - 
-  title: Get Commit Difference Count Between Two Branches
-  description: This GitHub Action compares two branches and gives you the commit count between them
+  title: 2つのブランチ間のコミットの差異数の取得
+  description: このGitHub Actionは2つのブランチを比較し、それらの間のコミットカウントを返します。
   languages: 'JavaScript, Shell'
   href: jessicalostinspace/commit-difference-action
   tags:
@@ -191,8 +191,8 @@
     - diff
     - ワークフロー
 - 
-  title: Generate Release Notes Based on Git References
-  description: GitHub Action to generate changelogs, and release notes
+  title: Git参照に基づくリリースノートを生成
+  description: changelogとリリースノートを生成するGitHub Action
   languages: 'JavaScript, Shell'
   href: metcalfc/changelog-generator
   tags:
@@ -201,8 +201,8 @@
     - ワークフロー
     - 変更履歴
 - 
-  title: Enforce Policies on GitHub Repositories and Commits
-  description: Policy enforcement for your pipelines
+  title: GitHubリポジトリとコミットにポリシーを適用する
+  description: パイプラインに対するポリシーの適用
   languages: 'Go, Makefile, Dockerfile, Shell'
   href: talos-systems/conform
   tags:
@@ -210,17 +210,17 @@
     - build-automation
     - ワークフロー
 - 
-  title: Auto Label Issue Based
-  description: Automatically label an issue based on the issue description
+  title: Issueに基づく自動ラベル
+  description: Issueの説明に基づいてIssueに自動的にラベル付け
   languages: 'TypeScript, JavaScript, Dockerfile'
   href: Renato66/auto-label
   tags:
     - labels
     - ワークフロー
-    - automation
+    - 自動化
 - 
-  title: Update Configured GitHub Actions to the Latest Versions
-  description: CLI tool to check whehter all your actions are up-to-date or not
+  title: 設定されたGitHub Actionsを最新バージョンにアップデート
+  description: すべてのアクションが最新かどうかをチェックするCLIツール
   languages: 'C#, Inno Setup, PowerSHell, Shell'
   href: fabasoad/ghacu
   tags:
@@ -228,8 +228,8 @@
     - cli
     - ワークフロー
 - 
-  title: Create Issue Branch
-  description: GitHub Action that automates the creation of issue branches
+  title: Issueブランチの作成
+  description: Issueブランチの作成を自動化するGitHub Action
   languages: 'JavaScript, Shell'
   href: robvanderleek/create-issue-branch
   tags:
@@ -237,25 +237,25 @@
     - issues
     - labels
 - 
-  title: Remove old artifacts
-  description: Customize artifact cleanup
+  title: 古い成果物を削除
+  description: 成果物のクリーンアップをカスタマイズ
   languages: 'JavaScript, Shell'
   href: c-hive/gha-remove-artifacts
   tags:
     - 成果物
     - ワークフロー
 - 
-  title: Sync Defined Files/Binaries to Wiki or External Repositories
-  description: GitHub Action to automatically sync changes to external repositories, like the wiki, for example
+  title: 定義されたファイル/バイナリをWikiあるいは外部リポジトリと同期
+  description: 変更を、たとえばwikiのような外部リポジトリに自動的に同期するGitHub Action
   languages: 'Shell, Dockerfile'
   href: kai-tub/external-repo-sync-action
   tags:
     - wiki
-    - sync
+    - 同期
     - ワークフロー
 - 
-  title: Create/Update/Delete a GitHub Wiki page based on any file
-  description: Updates your GitHub wiki by using rsync, allowing for exclusion of files and directories and actual deletion of files
+  title: 任意のファイルに基づいてGitHub Wikiページを作成/更新/削除
+  description: ファイルとディレクトリの除外、そして実際のファイルの削除をできるようにしながら、rsyncを使ってGitHub wikiを更新
   languages: 'Shell, Dockerfile'
   href: Andrew-Chen-Wang/github-wiki-action
   tags:
@@ -264,7 +264,7 @@
     - ワークフロー
 - 
   title: Prow GitHub Actions
-  description: Automation of policy enforcement, chat-ops, and automatic PR merging
+  description: ポリシー適用の自動化、chat-ops、自動PRマージ
   languages: 'TypeScript, JavaScript'
   href: jpmcb/prow-github-actions
   tags:
@@ -272,8 +272,8 @@
     - prow
     - ワークフロー
 - 
-  title: Check GitHub Status in your Workflow
-  description: Check GitHub Status in your workflow
+  title: ワークフロー中でのGitHubステータスのチェック
+  description: ワークフロー中でのGitHubステータスのチェック
   languages: 'TypeScript, JavaScript'
   href: crazy-max/ghaction-github-status
   tags:
@@ -281,26 +281,26 @@
     - モニタリング
     - ワークフロー
 - 
-  title: Manage labels on GitHub as code
-  description: GitHub Action to manage labels (create/rename/update/delete)
+  title: GitHub上でラベルをコードとして管理
+  description: ラベルを管理（作成/名前の変更/更新/削除）をするGitHub Action
   languages: 'TypeScript, JavaScript'
   href: crazy-max/ghaction-github-labeler
   tags:
     - labels
     - ワークフロー
-    - automation
+    - 自動化
 - 
-  title: Distribute funding in free and open source projects
-  description: Continuous Distribution of funding to project contributors and dependencies
+  title: フリーでオープンソースのプロジェクトに資金を分配
+  description: プロジェクトのコントリビューター及び依存関係への資金の継続的配分
   languages: 'Python, Dockerfile, Shell, Ruby'
   href: protontypes/libreselery
   tags:
     - sponsors
-    - funding
+    - 資金
     - payment
 - 
-  title: Herald rules for GitHub
-  description: Add reviewers, subscribers, labels and assignees to your PR
+  title: GitHubの先駆者ルール
+  description: PRへのレビュー担当者、サブスクライバー、ラベル、アサインされた人の追加
   languages: 'TypeScript, JavaScript'
   href: gagoar/use-herald-action
   tags:
@@ -309,27 +309,27 @@
     - assignees
     - プルリクエスト
 - 
-  title: Codeowner validator
-  description: Ensures the correctness of your GitHub CODEOWNERS file, supports public and private GitHub repositories and also GitHub Enterprise installations
+  title: コードオーナーバリデータ
+  description: パブリック及びプライベートのGitHubリポジトリと、GitHub Enterpriseの環境もサポートする、GitHub CODEOWNERSファイルの正確性の保証
   languages: 'Go, Shell, Makefile, Dockerfile'
   href: mszostok/codeowners-validator
   tags:
-    - codeowners
-    - validate
+    - コードオーナー
+    - 検証
     - ワークフロー
 - 
   title: Copybara Action
-  description: Move and transform code between repositories (ideal to maintain several repos from one monorepo)
+  description: リポジトリ間でコードを移動して変換（1つの単一リポジトリから複数のリポジトリを管理するのに理想的）
   languages: 'TypeScript, JavaScript, Shell'
   href: olivr/copybara-action
   tags:
-    - monorepo
+    - 単一リポジトリ
     - copybara
     - ワークフロー
 - 
-  title: Deploy static files to GitHub Pages
-  description: GitHub Action to publish website to GitHub Pages automatically
+  title: 静的ファイルをGitHub Pagesにデプロイ
+  description: WebサイトをGitHub Pagesに自動的に公開するGitHub Action
   languages: 'TypeScript, JavaScript'
   href: peaceiris/actions-gh-pages
   tags:
-    - publishing
+    - 公開
diff --git a/translations/ja-JP/data/variables/codespaces_code_examples.yml b/translations/ja-JP/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..ae9bc6b022
--- /dev/null
+++ b/translations/ja-JP/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.jsサンプルプロジェクト
+  description: カスタムdevコンテナとあわせてNode.jsプロジェクトを試してください
+  languages: JavaScript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - 開発コンテナ
+- 
+  title: Pythonサンプルプロジェクト
+  description: カスタムdevコンテナとあわせてPythonプロジェクトを試してください
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - 開発コンテナ
+- 
+  title: Javaサンプルプロジェクト
+  description: カスタムdevコンテナとあわせてJavaプロジェクトを試してください
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - 開発コンテナ
+- 
+  title: Goサンプルプロジェクト
+  description: カスタムdevコンテナとあわせてGoプロジェクトを試してください
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - 開発コンテナ
+- 
+  title: Rustサンプルプロジェクト
+  description: カスタムdevコンテナとあわせてRustプロジェクトを試してください
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - 開発コンテナ
+- 
+  title: PHPサンプルプロジェクト
+  description: カスタムdevコンテナとあわせてPHPプロジェクトを試してください
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - 開発コンテナ
diff --git a/translations/ja-JP/data/variables/contact.yml b/translations/ja-JP/data/variables/contact.yml
index 6f788ad1e7..5eab58c51d 100644
--- a/translations/ja-JP/data/variables/contact.yml
+++ b/translations/ja-JP/data/variables/contact.yml
@@ -1,15 +1,15 @@
 ---
 contact_ent_support: '[GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) または [GitHub Premium Support](https://premium.githubsupport.com)'
 contact_support: >-
-  {% if currentVersion == "free-pro-team@latest" %}[GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://premium.githubsupport.com){% else %}your site administrator{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[GitHub Support](https://support.github.com/contact)あるいは [GitHub Premium Support](https://premium.githubsupport.com){% else %}サイト管理者{% endif %}
 report_abuse: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Report abuse](https://github.com/contact/report-abuse){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[不正利用の報告](https://github.com/contact/report-abuse){% endif %}
 report_content: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Report content](https://github.com/contact/report-content){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[コンテンツを報告](https://github.com/contact/report-content){% endif %}
 contact_dmca: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[著作権侵害の申し立て](https://github.com/contact/dmca){% endif %}
 contact_privacy: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[プライバシーに関する連絡フォーム](https://github.com/contact/privacy){% endif %}
 contact_enterprise_sales: "[GitHubの営業チーム](https://enterprise.github.com/contact)"
 contact_feedback_actions: '[GitHub Actionsのフィードバックフォーム](https://support.github.com/contact/feedback?contact[category]=actions)'
 #The team that provides Standard Support
@@ -22,8 +22,8 @@ premium_support: 'GitHub Premium Support'
 enterprise_portal: 'GitHub Enterprise Supportポータル'
 contact_enterprise_portal: '[GitHub Enterprise Supportポータル](https://enterprise.githubsupport.com/hc/en-us)'
 #Azure support (GitHub AE) portal
-ae_azure_portal: 'Azure Support portal'
-contact_ae_portal: '[Azure Support portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)'
+ae_azure_portal: 'Azureサポートポータル'
+contact_ae_portal: '[Azureサポートポータル](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)'
 #GitHub Support portal (for dotcom - this sends users to a contact form)
 support_portal: 'GitHub Support ページ'
 contact_support_portal: '[GitHub Support ページ](https://support.github.com/contact)'
diff --git a/translations/ja-JP/data/variables/desktop.yml b/translations/ja-JP/data/variables/desktop.yml
index 913f51d4c3..24df2baea9 100644
--- a/translations/ja-JP/data/variables/desktop.yml
+++ b/translations/ja-JP/data/variables/desktop.yml
@@ -1,4 +1,4 @@
 ---
 #Supported platforms
 mac-osx-versions: macOS 10.10以降
-windows-versions: Windows 7 64-bit or later
+windows-versions: Windows 7 64-bit以降
diff --git a/translations/ja-JP/data/variables/discussions_community_examples.yml b/translations/ja-JP/data/variables/discussions_community_examples.yml
index 8b3594f2ec..8308f5751b 100644
--- a/translations/ja-JP/data/variables/discussions_community_examples.yml
+++ b/translations/ja-JP/data/variables/discussions_community_examples.yml
@@ -2,37 +2,37 @@
 - 
   #Images and descriptions are pulled directly from the repo
   repo: vercel/next.js
-  description: The React Framework
+  description: Reactフレームワーク
 - 
   repo: gatsbyjs/gatsby
-  description: Build blazing fast, modern apps and websites with React
+  description: モダンなアプリケーションやWebサイトをReactで高速に構築
 - 
   repo: nodejs/node
-  description: Node.js JavaScript runtime ✨🐢🚀✨
+  description: Node.js JavaScriptランタイム ✨🐢🚀✨
 - 
   repo: tailwindlabs/tailwindcss
-  description: A utility-first CSS framework for rapid UI development.
+  description: 高速なUI開発のためのユーティリティファーストなCSSフレームワーク
 - 
   repo: laravel/framework
-  description: Laravel is a web application framework with expressive, elegant syntax.
+  description: Laravelは、表現力のあるエレガントな構文を持つWebアプリケーションフレームワークです。
 - 
   repo: prisma/prisma
-  description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite
+  description: Node.js & TypeScriptのためのモダンなデータベースアクセス（ORMの代替） | PostgreSQL, MySQL, MariaDB & SQLite
 - 
   repo: dotnet/csharplang
-  description: 'The official repo for the design of the C# programming language'
+  description: 'C#プログラミング言語の設計のための公式リポジトリ'
 - 
   repo: home-assistant/frontend
-  description: '🍭 Frontend for Home Assistant'
+  description: '🍭 ホームアシスタントのためのフロントエンド'
 - 
   repo: jspsych/jsPsych
-  description: A JavaScript library for creating and running behavioral experiments in a web browser
+  description: Webブラウザ内で動作実験を作成して実行するためのJaavScriptライブラリ
 - 
   repo: adonisjs/core
-  description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence'
+  description: '🚀 The Node.jsフレームワークは、開発者の人間工学、安定性、信頼性に強く焦点を置いています'
 - 
   repo: ImageMagick/ImageMagick
   description: '🧙‍♂️ ImageMagick 7'
 - 
   repo: react-hook-form/react-hook-form
-  description: '📋 React Hooks for forms validation (Web + React Native)'
+  description: '📋 フォーム検証のためのReactフック(Web + React Native)'
diff --git a/translations/ja-JP/data/variables/explore.yml b/translations/ja-JP/data/variables/explore.yml
index e9d43c4230..954e67c9f7 100644
--- a/translations/ja-JP/data/variables/explore.yml
+++ b/translations/ja-JP/data/variables/explore.yml
@@ -1,7 +1,7 @@
 ---
 explore_github: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Explore GitHub](https://github.com/explore){% else %}Explore GitHub (`https://[hostname]/explore`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[GitHub 探訪](https://github.com/explore){% else %}GitHub 探訪 (`https://[hostname]/explore`){% endif %}
 your_stars_page: >-
-  {% if currentVersion == "free-pro-team@latest" %}[stars page](https://github.com/stars){% else %}stars page (`https://[hostname]/stars`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Star ページ](https://github.com/stars){% else %}Star ページ(`https://[hostname]/stars`){% endif %}
 trending_page: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Trending page](https://github.com/trending){% else %}Trending page (`https://[hostname]/trending`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[トレンドページ](https://github.com/trending){% else %}トレンドページ (`https://[hostname]/trending`){% endif %}
diff --git a/translations/ja-JP/data/variables/gists.yml b/translations/ja-JP/data/variables/gists.yml
index 12c745fd3c..629b6e217d 100644
--- a/translations/ja-JP/data/variables/gists.yml
+++ b/translations/ja-JP/data/variables/gists.yml
@@ -1,7 +1,7 @@
 ---
 gist_homepage: >-
-  {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[gistホームページ](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gistホームページ, `http(s)://gist.[hostname)`,{% else %}gistホームページ, `http(s)://[hostname]/gist`もしくはサブドメインが有効化されている場合は`http(s)://gist.[hostname]` {% endif %}
 gist_search_url: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Gist検索](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist検索, `http(s)://gist.[hostname]/search`,{% else %}Gist検索, `http(s)://[hostname]/gist/search`もしくはサブドメインが有効化されている場合は`http(s)://gist.[hostname]/search`{% endif %}
 discover_url: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover`もしくはサブドメインが有効化されている場合は`http(s)://gist.[hostname]/discover`{% endif %}
diff --git a/translations/ja-JP/data/variables/migrations.yml b/translations/ja-JP/data/variables/migrations.yml
index 15201e4a03..5b9da83fb6 100644
--- a/translations/ja-JP/data/variables/migrations.yml
+++ b/translations/ja-JP/data/variables/migrations.yml
@@ -1,7 +1,7 @@
 ---
 user_migrations_intro: >-
-  You can use this API to review, backup, or migrate your user data stored on {% data variables.product.product_name %}.com.
+  このAPIを使って{% data variables.product.product_name %}.comに保存されているユーザデータのレビュー、バックアップ、移行を行えます。
 organization_migrations_intro: >-
-  The organization migrations API lets you move a repository from GitHub to {% data variables.product.prodname_ghe_server %}.
+  Organization移行APIを使うと、リポジトリをGitHubから{% data variables.product.prodname_ghe_server %}に移動できます。
 source_imports_intro: >-
-  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Server source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
+  ソースインポートAPIを使用すると、Git、Subversion、Mercurial、Team Foundation Version Controlソースリポジトリからインポートを開始できます。これは{% data variables.product.prodname_dotcom %} Importerと同じ機能です。詳しい情報については「[{% data variables.product.prodname_dotcom %} Importerでのリポジトリのインポート](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)」を参照してください。
diff --git a/translations/ja-JP/data/variables/notifications.yml b/translations/ja-JP/data/variables/notifications.yml
index 441bdba328..d26937b55e 100644
--- a/translations/ja-JP/data/variables/notifications.yml
+++ b/translations/ja-JP/data/variables/notifications.yml
@@ -1,5 +1,5 @@
 ---
 no_reply_address: >-
-  {% if currentVersion == "free-pro-team@latest" %}`noreply@github.com`{% else %}the no-reply email address configured by your site administrator{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}`noreply@github.com`{% else %}サイト管理者が設定したno-replyメールアドレス{% endif %}
 cc_address: >-
-  {% if currentVersion == "free-pro-team@latest" %}`@noreply.github.com`{% else %}based on the no-reply email address configured by your site administrator{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}`@noreply.github.com`{% else %}サイト管理者が設定した no-reply メールアドレスに基づく{% endif %}
diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml
index 3919b1bafd..8d7c14f086 100644
--- a/translations/ja-JP/data/variables/product.yml
+++ b/translations/ja-JP/data/variables/product.yml
@@ -20,7 +20,7 @@ prodname_ghe_managed: 'GitHub AE'
 prodname_ghe_one: 'GitHub One'
 ## Use these variables when referring specifically to a location within a product
 product_location: >-
-  {% if enterpriseServerVersions contains currentVersion %}your GitHub Enterprise Server instance{% elsif currentVersion == "github-ae@latest" %}your enterprise{% else %}GitHub{% endif %}
+  {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Serverのインスタンス{% elsif currentVersion == "github-ae@latest" %}Enterprise{% else %}GitHub{% endif %}
 #Used ONLY when you need to refer to a GHES instance in an article that is versioned for non-GHES versions.
 #Do not use in other situations!
 product_location_enterprise: 'GitHub Enterprise Server インスタンス'
@@ -37,7 +37,7 @@ prodname_unified_search: 'Unified Search'
 #GitHub Education
 prodname_education: 'GitHub Education'
 prodname_education_community: 'Education Community'
-prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)'
+prodname_education_community_with_url: '[GitHub Education Community](https://education.github.community)'
 prodname_classroom: 'GitHub Classroom'
 prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)'
 prodname_campus_program: 'GitHub Campus Program'
@@ -56,6 +56,7 @@ prodname_pages: 'GitHub Pages'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'GitHub App'
@@ -63,11 +64,11 @@ prodname_github_apps: 'GitHub Apps'
 prodname_oauth_app: 'OAuth App'
 prodname_oauth_apps: 'OAuth App'
 #API and developer docs
-prodname_enterprise_api: 'the {% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} APIs'
+prodname_enterprise_api: '{% if enterpriseServerVersions contains currentVersion %}GitHub Enterprise Server{% elsif currentVersion == "github-ae@latest" %}GitHub AE{% endif %} API'
 prodname_support_forum_with_url: '[GitHub API Development and Support Forum](https://github.community/c/github-api-development-and-support/37)'
 prodname_unfurls: 'Content Attachments'
 #Azure AD
-ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterpriseserver)'
+ae_azure_ad_app_link: '[GitHub AEアプリケーション](https://azuremarketplace.microsoft.com/ja-jp/marketplace/apps/aad.githubenterpriseserver)'
 #GitHub Actions
 ## Use this variable only when referring to GitHub Actions the product. When referring to the thing that someone creates using the product, call it an action (small a). See the terminology page of the Brand Guide for more.
 prodname_actions: 'GitHub Actions'
@@ -77,8 +78,7 @@ prodname_debug: 'GitHub デバッグ'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
-prodname_github_container_registry: 'GitHub Container Registry'
-prodname_container_registry: 'container registry'
+prodname_container_registry: 'コンテナレジストリ'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -88,10 +88,9 @@ prodname_matching_fund: 'GitHub Sponsors Matching Fund'
 prodname_GH_advanced_security: 'GitHub Advanced Security'
 prodname_advanced_security: 'Advanced Security'
 #Security Center
-prodname_security_center: 'Security Center'
+prodname_security_center: 'セキュリティセンター'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Visual Studio Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'GitHub Community Support'
@@ -99,7 +98,7 @@ prodname_blog: 'GitHub ブログ'
 prodname_jobs: 'GitHub Jobs'
 prodname_learning: 'GitHub Learning Lab'
 prodname_learning_link: 'https://lab.github.com/'
-prodname_roadmap: 'GitHub public roadmap'
+prodname_roadmap: 'GitHubパブリックロードマップ'
 prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap'
 #GitHub support
 premium_support_plan: 'Premium プラン'
@@ -118,19 +117,19 @@ prodname_secret_scanning: 'secret scanning'
 prodname_secret_scanning_caps: 'Secret scanning'
 prodname_code_scanning: 'code scanning'
 prodname_code_scanning_capc: 'Code scanning'
-prodname_codeql_runner: 'CodeQL runner'
+prodname_codeql_runner: 'CodeQLランナー'
 prodname_advisory_database: 'GitHub Advisory Database'
-prodname_codeql_workflow: 'CodeQL analysis workflow'
+prodname_codeql_workflow: 'CodeQL分析ワークフロー'
 #Visual Studio
 prodname_vs: 'Visual Studio'
 prodname_vscode: 'Visual Studio Code'
 prodname_vss_ghe: 'Visual Studio subscription with GitHub Enterprise'
-prodname_vss_admin_portal_with_url: 'the [administrator portal for Visual Studio subscriptions](https://visualstudio.microsoft.com/subscriptions-administration/)'
+prodname_vss_admin_portal_with_url: '[Visual Studio subscriptions管理ポータル](https://visualstudio.microsoft.com/subscriptions-administration/)'
 #GitHub Dependabot
 prodname_dependabot: 'Dependabot'
-prodname_dependabot_alerts: 'Dependabot alerts'
-prodname_dependabot_security_updates: 'Dependabot security updates'
-prodname_dependabot_version_updates: 'Dependabot version updates'
+prodname_dependabot_alerts: 'Dependabotアラート'
+prodname_dependabot_security_updates: 'Dependabotセキュリティアップデート'
+prodname_dependabot_version_updates: 'Dependabotバージョンアップデート'
 #GitHub Archive Program
 prodname_archive: 'GitHub Archive Program'
 prodname_arctic_vault: 'Arctic Code Vault'
@@ -139,9 +138,9 @@ product_url: >-
   {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %}
 pricing_url: 'https://github.com/pricing'
 signin_link: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Sign in](https://github.com/login){% else %}Sign in (`https://[hostname]/login`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[サインイン](https://github.com/login){% else %}サインイン (`https://[hostname]/login`){% endif %}
 signout_link: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Sign out](https://github.com/logout){% else %}Sign out (`https://[hostname]/logout`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[サインアウト](https://github.com/logout){% else %}サインアウト (`https://[hostname]/logout`){% endif %}
 raw_github_com: >-
   {% if currentVersion == "free-pro-team@latest" %}raw.githubusercontent.com{% else %}[hostname]/user/repo/raw{% endif %}
 #GitHub Enterprise Server past versions
diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/ja-JP/data/variables/release_candidate.yml
+++ b/translations/ja-JP/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/ja-JP/data/variables/search.yml b/translations/ja-JP/data/variables/search.yml
index f22c85c916..bcc19612c3 100644
--- a/translations/ja-JP/data/variables/search.yml
+++ b/translations/ja-JP/data/variables/search.yml
@@ -1,5 +1,5 @@
 ---
 advanced_url: >-
-  {% if currentVersion == "free-pro-team@latest" %}[advanced search](https://github.com/search/advanced) page{% else %}advanced search page (`https://[hostname]/search/advanced`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[高度な検索(https://github.com/search/advanced)ページ{% else %}高度な件レ区ページ(`https://[hostname]/search/advanced`){% endif %}
 search_page_url: >-
-  {% if currentVersion == "free-pro-team@latest" %}[search](https://github.com/search) page{% else %}search page (`https://[hostname]/search`){% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[search](https://github.com/search)ページ{% else %}検索ページ(`https://[hostname]/search`){% endif %}
diff --git a/translations/ja-JP/data/variables/sponsors_user_examples.yml b/translations/ja-JP/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..043e00aa0d
--- /dev/null
+++ b/translations/ja-JP/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chaynは、虐待を経験している女性が正しい情報を見つけることを支援し、自分たちの人生をコントロールできるようにするためのサポートをします。
+- 
+  user: foosel
+  description: '👋私はGinaです。OctoPrintのクリエイター、そして主要な開発者として主に知られています 🐙.'
+- 
+  user: dayhaysoos
+  description: 最近どうですか？私はNickです。私はeコマース開発者の体験から不和を取り除くということに、新たに情熱を見つけました。
+- 
+  user: yyx990803
+  description: 私はWebアプリケーションを構築するためのフロントエンドJavaScriptフレームワークであるVue.js、そしてモダンなWebビルとツールのViteにフルタイムで取り組んでいます。
+- 
+  user: calebporzio
+  description: '🚶‍♂️私は2019年1月にオープンソースを追求するために日中の仕事を辞めました。それ以来、私はLaravel Livewire、AlpineJS、その他多くのものを構築しています。'
+- 
+  user: kjaymiller
+  description: 皆さんこんにちは、私はJayです! 👋私は開発者になった海兵隊退役軍人で、2014年から活発にコーディングをしています。私はまた、好みのアプリケーションやツールのために自動化をしている人々を支援する生産性の分野にも関わっています。
diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index 0caa471152..e24f970c94 100644
--- a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md
index 9a2b277f05..da879bd5b1 100644
--- a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md
index d2a0315692..25dd263783 100644
--- a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md
@@ -222,14 +222,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-javascript-action@v1.1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index def2b6d8a2..fe1f3007e0 100644
--- a/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -171,7 +171,7 @@ In this example, `cleanup.js` only runs on Linux-based runners:
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 #### `게시`
@@ -197,7 +197,7 @@ For example, this `cleanup.js` will only run on Linux-based runners:
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 ### `runs` for composite run steps actions
@@ -295,7 +295,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
@@ -323,7 +323,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/ko-KR/content/actions/guides/about-continuous-integration.md b/translations/ko-KR/content/actions/guides/about-continuous-integration.md
index 3d3706d537..4cb220560b 100644
--- a/translations/ko-KR/content/actions/guides/about-continuous-integration.md
+++ b/translations/ko-KR/content/actions/guides/about-continuous-integration.md
@@ -48,11 +48,13 @@ In addition to helping you set up CI workflows for your project, you can use {%
 For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)."
 
 ### Supported languages
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} offers CI workflow templates for a variety of languages and frameworks.
 
 Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### Skipping workflow runs
 
 If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any any of the following strings to the commit message in a push, or the HEAD commit of a pull request:
@@ -72,6 +74,7 @@ You won't be able to merge the pull request if your repository is configured to
 **Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running.
 
 {% endnote %}
+{% endif %}
 
 ### Notifications for workflow runs
 
diff --git a/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md b/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md
index e2669d284c..0ae7c96b6d 100644
--- a/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/ko-KR/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,39 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### About packaging steps
-
-A packaging step is a common part of a continuous integration or continuous delivery workflow. After building and testing your application, a runnable or deployable artifact is produced in the form of a package. For example, a continuous integration workflow for a Java project may run `mvn package` to produce a JAR file. Or, a CI workflow for a Node.js application may create a Docker container.
-
-Depending on the kind of application you're building, this package can be downloaded locally for manual testing, made available for users to download, or deployed to a staging or production environment.
-
-### Packaging in continuous integration workflows
-
-Creating a package at the end of a continuous integration workflow can help during code reviews on a pull request. After building and testing your code, a packaging step can produce a runnable or deployable artifact. Your workflow can then take that artifact and upload it as part of the workflow.
-
-Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced.
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request.
-
-### Workflows for publishing packages
-
-In addition to uploading packaging artifacts for testing in a continuous integration workflow, you can create workflows that build your project and publish packages to a package registry.
-
-* **Publish packages to {% data variables.product.prodname_registry %}**
-  {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. You can choose to share your packages with all of {% data variables.product.prodname_dotcom %}, or private packages to share with collaborators or an organization. For more information, see "[About {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)."
-
-  You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build out of master easily, by installing it from {% data variables.product.prodname_registry %}.
-
-* **Publish packages to a package registry**  
-  For many projects, publishing to a package registry is performed whenever a new version of a project is released. For example, a project that produces a JAR file may upload new releases to the Maven Central repository. Or, a .NET project may produce a nuget package and upload it to the NuGet Gallery.
-
-  You can automate this by creating a workflow that publishes packages to a package registry on every release creation. For more information, see "[Creating releases](/github/administering-a-repository/creating-releases)."
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md b/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md
index 33711a86bb..6c47069235 100644
--- a/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,14 +38,17 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `add-labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
 5. {% data reusables.actions.commit-workflow %}
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-net.md b/translations/ko-KR/content/actions/guides/building-and-testing-net.md
index 8b182bd3ba..3ebf76e22d 100644
--- a/translations/ko-KR/content/actions/guides/building-and-testing-net.md
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-net.md
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,7 +139,7 @@ For more information, see "[Caching dependencies to speed up workflows](/actions
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
@@ -171,7 +171,7 @@ You can use the same commands that you use locally to build and test your code.
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`.
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md
index 0365d27281..d70ed237cb 100644
--- a/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ We recommend that you have a basic understanding of Node.js, YAML, workflow conf
 
 {% data variables.product.prodname_dotcom %} provides a Node.js workflow template that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the template. For more information, see the [Node.js workflow template](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the template to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,14 +119,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 If you don't specify a Node.js version,
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md b/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md
index f4c75808a4..d5003ff12e 100644
--- a/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-powershell.md
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1`
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-python.md b/translations/ko-KR/content/actions/guides/building-and-testing-python.md
index 66a850fb9f..8daa72360b 100644
--- a/translations/ko-KR/content/actions/guides/building-and-testing-python.md
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-python.md
@@ -58,25 +58,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Lint with flake8
-      run: |
-        # stop the build if there are Python syntax errors or undefined names
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - name: Test with pytest
-      run: |
-        pytest
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -117,14 +117,14 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -144,17 +144,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # Semantic version range syntax or exact version of a Python version
-        python-version: '3.x'
-        # Optional - x64 or x86 architecture, defaults to x64
-        architecture: 'x64'
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -373,25 +373,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Install pip and pytest
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # Use always() to always run this step to publish test results when there are test failures
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -413,22 +413,22 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 {% endraw %}
 
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md
index 66ee7b2eee..56e0097fb6 100644
--- a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ We recommend that you have a basic understanding of Ruby, YAML, workflow configu
 
 {% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the template to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,7 +264,6 @@ You can configure your workflow to publish your Ruby package to any package regi
 
 You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`.
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
@@ -272,46 +271,48 @@ name: Ruby Gem
 on:
   # Manually publish
   workflow_dispatch:
-  # Alternatively, publish whenever changes are merged to the default branch.
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-swift.md b/translations/ko-KR/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..71d5456b9e
--- /dev/null
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Building and testing Swift
+intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introduction
+
+This guide shows you how to build and test a Swift package.
+
+{% if currentVersion == "github-ae@latest" %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
+{% else %}{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swift packages. For a full list of up-to-date software and the preinstalled versions of Swift and Xcode, see "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### 빌드전 요구 사양
+
+You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+
+We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
+
+### Starting with the Swift workflow template
+
+{% data variables.product.prodname_dotcom %} provides a Swift workflow template that should work for most Swift projects, and this guide includes examples that show you how to customize this template. For more information, see the [Swift workflow template](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+To get started quickly, add the template to the `.github/workflows` directory of your repository.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Specifying a Swift version
+
+To use a specific preinstalled version of Swift on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `fwal/setup-swift` action. This action finds a specific version of Swift from the tools cache on the runner and adds the necessary binaries to `PATH`. These changes will persist for the remainder of a job. For more information, see the [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) action.
+
+If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+
+The examples below demonstrate using the `fwal/setup-swift` action.
+
+#### Using multiple Swift versions
+
+You can configure your job to use a multiple versions of Swift in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Using a single specific Swift version
+
+You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### Building and testing your code
+
+You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/ko-KR/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..69002915b8
--- /dev/null
+++ b/translations/ko-KR/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Building and testing Xamarin applications
+intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Xamarin application.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introduction
+
+This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. The workflow you create will allow you to see when commits to a pull request cause build or test failures against your default branch; this approach can help ensure that your code is always healthy.
+
+{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### 빌드전 요구 사양
+
+We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+
+- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
+- "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Bulding Xamarin.iOS apps
+
+The example below demonstrates how to change the default Xamarin bundle and build  a Xamarin.iOS application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Bulding Xamarin.Android apps
+
+The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### Specifying a .NET version
+
+To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job.
+
+The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action.
diff --git a/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index a16b3c3fdf..59bb76edbd 100644
--- a/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/ko-KR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
 
 - `key`: **Required** The key created when saving a cache and the key used to search for a cache. Can be any combination of variables, context values, static strings, and functions. Keys have a maximum length of 512 characters, and keys longer than the maximum length will cause the action to fail.
 - `path`: **Required** The file path on the runner to cache or restore. The path can be an absolute path or relative to the working directory.
-  - With `v2` of the `cache` action, you can specify a single path, or multiple paths as a list. Paths can be either directories or single files, and glob patterns are supported.
+  - Paths can be either directories or single files, and glob patterns are supported.
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. 예시:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - With `v1` of the `cache` action, only a single path is supported and it must be a directory. You cannot cache a single file.
 - `restore-keys`: **Optional** An ordered list of alternative keys to use for finding the cache if no cache hit occurred for `key`.
 
@@ -82,30 +91,29 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-    - name: Cache node modules
-      uses: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm` on Linux/macOS
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - name: Install Dependencies
-      run: npm install
+      - name: Install Dependencies
+        run: npm install
 
-    - name: Build
-      run: npm build
-
-    - name: Test
-      run: npm test
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/ko-KR/content/actions/guides/closing-inactive-issues.md b/translations/ko-KR/content/actions/guides/closing-inactive-issues.md
index 6cd1cb2179..806ebe7112 100644
--- a/translations/ko-KR/content/actions/guides/closing-inactive-issues.md
+++ b/translations/ko-KR/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,9 +51,9 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every day at 1:30 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `days-before-issue-stale` to the number of days without activity before the `actions/stale` action labels an issue. If you never want this action to label issues, set this value to `-1`.
diff --git a/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index c1120b2731..b02b7b5137 100644
--- a/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **Make sure to reference this issue in your pull request.** :sparkles: Thank you for your contribution! :sparkles:
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Replace `help-wanted` in `if: github.event.label.name == 'help-wanted'` with the label that you want to act on. If you want to act on more than one label, separate the conditions with `||`. For example, `if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` will comment whenever the `bug` or `fix me` labels are added to an issue.
    - Change the value for `body` to the comment that you want to add. GitHub flavored markdown is supported. For more information about markdown, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
diff --git a/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md b/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md
index ef6e505a25..43c47879b0 100644
--- a/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/ko-KR/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### Introduction
 
-This guide shows you workflow examples that configure a service container using the Docker Hub `postgres` image. The workflow runs a script to create a PostgreSQL client and populate the client with data. To test that the workflow creates and populates the PostgreSQL client, the script prints the client's data to the console.
+This guide shows you workflow examples that configure a service container using the Docker Hub `postgres` image. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -81,10 +81,10 @@ jobs:
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client, populates
-        # the client with data, and retrieves data
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
         run: node client.js
-        # Environment variable used by the `client.js` script to create a new PostgreSQL client.
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # The hostname used to communicate with the PostgreSQL service container
           POSTGRES_HOST: postgres
@@ -141,8 +141,8 @@ steps:
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL client, populates
-    # the client with data, and retrieves data
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
     run: node client.js
     # Environment variable used by the `client.js` script to create
     # a new PostgreSQL client.
@@ -204,11 +204,11 @@ jobs:
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client, populates
-        # the client with data, and retrieves data
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
         run: node client.js
-        # Environment variable used by the `client.js` script to create
-        # a new PostgreSQL client.
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # The hostname used to communicate with the PostgreSQL service container
           POSTGRES_HOST: localhost
@@ -268,11 +268,11 @@ steps:
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL client, populates
-    # the client with data, and retrieves data
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new PostgreSQL client.
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # The hostname used to communicate with the PostgreSQL service container
       POSTGRES_HOST: localhost
@@ -286,9 +286,9 @@ steps:
 
 ### Testing the PostgreSQL service container
 
-You can test your workflow using the following script, which creates a PostgreSQL client and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `pg` npm module. For more information, see the [npm pg module](https://www.npmjs.com/package/pg).
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `pg` npm module. For more information, see the [npm pg module](https://www.npmjs.com/package/pg).
 
-You can modify *client.js* to include any PostgreSQL operations needed by your workflow. In this example, the script creates the PostgreSQL client instance, creates a table, adds placeholder data, then retrieves the data.
+You can modify *client.js* to include any PostgreSQL operations needed by your workflow. In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-The script creates a new PostgreSQL `Client`, which accepts a `host` and `port` parameter. The script uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to set the client's IP address and port. If `host` and `port` are not defined, the default host is `localhost` and the default port is 5432.
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. If `host` and `port` are not defined, the default host is `localhost` and the default port is 5432.
 
-The script creates a table and populates it with placeholder data. To test that the PostgreSQL database contains the data, the script prints the contents of the table to the console log.
+The script creates a table and populates it with placeholder data. To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step confirming you created the PostgreSQL client and added data:
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index afcce12612..7608bafbba 100644
--- a/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ The following example workflow demonstrates how to build a container image and p
 
 Ensure that you provide your own values for all the variables in the `env` key of the workflow.
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### Additional resources
 
diff --git a/translations/ko-KR/content/actions/guides/index.md b/translations/ko-KR/content/actions/guides/index.md
index ce126dbc93..0f0ae3b526 100644
--- a/translations/ko-KR/content/actions/guides/index.md
+++ b/translations/ko-KR/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/ko-KR/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/ko-KR/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..a117c95c40
--- /dev/null
+++ b/translations/ko-KR/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Managing GitHub Actions with GitHub CLI
+intro: 'You can use {% data variables.product.prodname_cli %} to interact with {% data variables.product.prodname_actions %}.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Setting up {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### Managing {% data variables.product.prodname_actions %} with {% data variables.product.prodname_cli %}
+
+To view all available commands related to {% data variables.product.prodname_actions %}, run `gh actions`.
+
+For more information on using commands in specific scenarios, see the following procedures:
+
+- "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)"
+- "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/ko-KR/content/actions/guides/publishing-docker-images.md b/translations/ko-KR/content/actions/guides/publishing-docker-images.md
index 3e3a5570d4..f0b038c38f 100644
--- a/translations/ko-KR/content/actions/guides/publishing-docker-images.md
+++ b/translations/ko-KR/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ You might also find it helpful to have a basic understanding of the following:
 
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
-- "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)"
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### About image configuration
 
@@ -98,7 +98,6 @@ The `build-push-action` options required for {% data variables.product.prodname_
 * `registry`: Must be set to `docker.pkg.github.com`.
 * `repository`: Must be set in the format `OWNER/REPOSITORY/IMAGE_NAME`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `repository` option should be set to `octo-org/octo-repo/octo-image`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -107,21 +106,23 @@ on:
 jobs:
   push_to_registry:
     name: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,7 +132,6 @@ In a single workflow, you can publish your Docker image to multiple registries b
 
 The following example workflow uses the `build-push-action` steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -140,26 +140,28 @@ on:
 jobs:
   push_to_registries:
     name: Push Docker image to multiple registries
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to Docker Hub
         uses: docker/build-push-action@v1
         with:
-          username: ${{ secrets.DOCKER_USERNAME }}
-          password: ${{ secrets.DOCKER_PASSWORD }}
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
           repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, and uses the `build-push-action` action twice to build and push the Docker image to Docker Hub and {% data variables.product.prodname_registry %}. For both steps, it sets the `build-push-action` option [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) to automatically tag the built Docker image with the Git reference of the workflow event. This workflow is triggered on publishing a {% data variables.product.prodname_dotcom %} release, so the reference for both registries will be the Git tag for the release.
diff --git a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md
index 4d982ef7ac..28effba768 100644
--- a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ For more information about creating a CI workflow for your Java project with Gra
 
 You may also find it helpful to have a basic understanding of the following:
 
-- "[Configuring npm for use with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -108,7 +108,7 @@ Each time you create a new release, you can trigger a workflow to publish your p
 
 You can define a new Maven repository in the publishing block of your _build.gradle_ that points to {% data variables.product.prodname_registry %}.  In that repository configuration, you can also take advantage of environment variables set in your CI workflow run.  You can use the `GITHUB_ACTOR` environment variable as a username, and you can set the `GITHUB_TOKEN` environment variable with your `GITHUB_TOKEN` secret.
 
-The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.github-token-permissions %}
 
 For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example.
 
@@ -133,7 +133,6 @@ publishing {
 
 With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret.
+1. Runs the `gradle publish` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
@@ -199,7 +200,6 @@ publishing {
 
 With this configuration, you can create a workflow that publishes your package to both the Maven Central Repository and {% data variables.product.prodname_registry %} by running the `gradle publish` command.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret.
+1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
diff --git a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md
index dfe73a0c71..100d734261 100644
--- a/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/ko-KR/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ For more information about creating a CI workflow for your Java project with Mav
 
 You may also find it helpful to have a basic understanding of the following:
 
-- "[Configuring npm for use with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -112,9 +112,9 @@ This workflow performs the following steps:
 
 Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs when the `release` event triggers with type `created`. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
 
-In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, and also sets up a Maven _settings.xml_ for publishing the package to {% data variables.product.prodname_registry %}. The generated _settings.xml_ defines authentication for a server with an `id` of `github`, using the `GITHUB_ACTOR` environment variable as the username and the `GITHUB_TOKEN` environment variable as the password.
+In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, and also sets up a Maven _settings.xml_ for publishing the package to {% data variables.product.prodname_registry %}. The generated _settings.xml_ defines authentication for a server with an `id` of `github`, using the `GITHUB_ACTOR` environment variable as the username and the `GITHUB_TOKEN` environment variable as the password. The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
 
-The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.github-token-permissions %}
 
 For a Maven-based project, you can make use of these settings by creating a distribution repository in your _pom.xml_ file with an `id` of `github` that points to your {% data variables.product.prodname_registry %} endpoint.
 
@@ -137,7 +137,6 @@ For example, if your organization is named "octocat" and your repository is name
 
 With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by making use of the automatically generated _settings.xml_.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 This workflow performs the following steps:
 
@@ -173,7 +174,6 @@ You can publish your packages to both the Maven Central Repository and {% data v
 
 Ensure your _pom.xml_ file includes a distribution management repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider. For example, if you deploy to the Central Repository through the OSSRH hosting project, you might want to specify it in a distribution management repository with the `id` set to `ossrh`, and you might want to specify {% data variables.product.prodname_registry %} in a distribution management repository with the `id` set to `github`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 This workflow calls the `setup-java` action twice.  Each time the `setup-java` action runs, it overwrites the Maven _settings.xml_ file for publishing packages.  For authentication to the repository, the _settings.xml_ file references the distribution management repository `id`, and the username and password.
 
diff --git a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md
index 2d50143279..bcf197df7a 100644
--- a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ For more information about creating a CI workflow for your Node.js project, see
 
 You may also find it helpful to have a basic understanding of the following:
 
-- "[Configuring npm for use with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ However, if you do provide the `repository` key, then the repository in that key
 
 #### Authenticating to the destination repository
 
-To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)."
+To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 
@@ -120,7 +120,6 @@ If you want to publish your package to a different repository, you must use a pe
 
 This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file.
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,13 +197,13 @@ If you publish a package to both registries, you'll need to ensure that your sco
 
 Ensure your *package.json* file includes the scope of your {% data variables.product.prodname_dotcom %} repository and npm registry. For example, if you plan to publish a package in the `octocat/npm-hello-world-test` repository to {% data variables.product.prodname_dotcom %} and https://www.npmjs.com/package/@octocat/npm-hello-world-test, the name in your *package.json* file would be `"name": "@octocat/npm-hello-world-test"`.
 
-To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 When you use the `scope` input to the `setup-node` action, the action creates an *.npmrc* file that includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the user or organization that owns the workflow file.
 
 This workflow calls the `setup-node` action two times. Each time the `setup-node` action runs, it overwrites the *.npmrc* file. The *.npmrc* file references the token that allows you to perform authenticated operations against the package registry from the `NODE_AUTH_TOKEN` environment variable. The workflow sets the `NODE_AUTH_TOKEN` environment variable each time the `npm publish` command is run, first with a token to publish to npm (`NPM_TOKEN`) and then with a token to publish to {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
 
-{% raw %}
+
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -210,28 +211,30 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v1
-      with:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    # Publish to npm
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v1
-      with:
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    # Publish to GitHub Packages
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index fbdec485ed..8d54cceca4 100644
--- a/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 3. {% data reusables.actions.make-workflow-file %}
 4. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. Customize the parameters in your workflow file:
    - In `github.event.project_card.column_id == '12345678'`, replace `12345678` with the ID of the column where you want to un-label issues and pull requests that are moved there.
 
diff --git a/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md b/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md
index 583eea26e7..690c506902 100644
--- a/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:20 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `assignees` to the list of {% data variables.product.prodname_dotcom %} usernames that you want to assign to the issue.
diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 41e25d5c29..b031c804b2 100644
--- a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -53,7 +53,7 @@ When creating a group, you must choose a policy that defines which repositories
 
    **경고**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
@@ -85,7 +85,7 @@ When creating a group, you must choose a policy that defines which organizations
 
    **경고**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index d56c4d03b4..af1547b132 100644
--- a/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -66,7 +66,7 @@ To remove a self-hosted runner from an organization, you must be an organization
 
 {% if currentVersion == "free-pro-team@latest" %}
 To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 To remove a self-hosted runner at the enterprise level of
 {% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine.
 {% endif %}
diff --git a/translations/ko-KR/content/actions/index.md b/translations/ko-KR/content/actions/index.md
index 7160434e13..bd0c0559a3 100644
--- a/translations/ko-KR/content/actions/index.md
+++ b/translations/ko-KR/content/actions/index.md
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Code examples</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Search code examples" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Show more {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Sorry, there is no result for <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Learn how to add a code example {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index 7c87a322a0..6461c05082 100644
--- a/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/ko-KR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md
index dcd1e62000..2fa9c6e87d 100644
--- a/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md
+++ b/translations/ko-KR/content/actions/learn-github-actions/security-hardening-for-github-actions.md
@@ -16,6 +16,7 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### 개요
 
@@ -23,9 +24,9 @@ This guide explains how to configure security hardening for certain {% data vari
 
 ### Using secrets
 
-Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
 
-Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps the minimize risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime.
+Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime.
 
 To help prevent accidental disclosure, {% data variables.product.product_name %} uses a mechanism that attempts to redact any secrets that appear in run logs. This redaction looks for exact matches of any configured secrets, as well as common encodings of the values, such as Base64. However, because there are multiple ways a secret value can be transformed, this redaction is not guaranteed. As a result, there are certain proactive steps and good practices you should follow to help ensure secrets are redacted, and to limit other risks associated with secrets:
 
@@ -38,11 +39,12 @@ To help prevent accidental disclosure, {% data variables.product.product_name %}
     - Audit how secrets are used, to help ensure they’re being handled as expected. You can do this by reviewing the source code of the repository executing the workflow, and checking any actions used in the workflow. For example, check that they’re not sent to unintended hosts, or explicitly being printed to log output.
     - View the run logs for your workflow after testing valid/invalid inputs, and check that secrets are properly redacted, or not shown. It's not always obvious how a command or tool you’re invoking will send errors to `STDOUT` and `STDERR`, and secrets might subsequently end up in error logs. As a result, it is good practice to manually review the workflow logs after testing valid and invalid inputs.
 - **Use credentials that are minimally scoped**
-    - Make sure the credentials being used within workflows have the least privileges required, and be mindful that any user with write access to your repository has read access to all secrets configured in your repository.
+    - Make sure the credentials being used within workflows have the least privileges required, and be mindful that any user with write access to your repository has read access to all secrets configured in your repository. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." You should therefore make sure that the `GITHUB_TOKEN` is granted the minimum required permissions. It's good security practice to set the default permission for the `GITHUB_TOKEN` to read access only for repository contents. The permissions can then be increased, as required, for individual jobs within the workflow file. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." {% endif %}
 - **Audit and rotate registered secrets**
     - Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed.
     - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid.
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 - **Consider requiring review for access to secrets**
     - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)."
 {% endif %}
@@ -51,7 +53,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %}
 
 The individual jobs in a workflow can interact with (and compromise) other jobs. For example, a job querying the environment variables used by a later job, writing files to a shared directory that a later job processes, or even more directly by interacting with the Docker socket and inspecting other running containers and executing commands in them.
 
-This means that a compromise of a single action within a workflow can be very significant, as that compromised action would have access to all secrets configured on your repository, and can use the `GITHUB_TOKEN` to write to the repository. Consequently, there is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. You can help mitigate this risk by following these good practices:
+This means that a compromise of a single action within a workflow can be very significant, as that compromised action would have access to all secrets configured on your repository, and may be able to use the `GITHUB_TOKEN` to write to the repository. Consequently, there is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. You can help mitigate this risk by following these good practices:
 
 * **Pin actions to a full length commit SHA**
 
@@ -76,14 +78,14 @@ This means that a compromise of a single action within a workflow can be very si
 
 ### Considering cross-repository access
 
-{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
+{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying a workflow file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}, elevating the permissions of the `GITHUB_TOKEN` if necessary{% endif %}. Users have specific permissions for each repository, so allowing the `GITHUB_TOKEN` for one repository to grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
 
 We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended.
 
 This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference:
 
 1. **The `GITHUB_TOKEN`**
-    -  This token is intentionally scoped to the single repository that invoked the workflow, and has the same level of access as a write-access user on the repository. The token is created before each job begins and expires when the job is finished. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}can have {% else %}has {% endif %}the same level of access as a write-access user on the repository. The token is created before each job begins and expires when the job is finished. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
     - The `GITHUB_TOKEN` should be used whenever possible.
 2. **Repository deploy key**
     - Deploy keys are one of the only credential types that grant read or write access to a single repository, and can be used to interact with another repository within a workflow. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)."
@@ -102,7 +104,7 @@ This list describes the recommended approaches for accessing repository data wit
 
 **Self-hosted** runners on {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
 
-As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a PR (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the more privileged `GITHUB_TOKEN` which grants write-access permissions on the repository.
+As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a pull request (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}, depending on its settings, can grant {% else %} grants {% endif %}write-access permissions on the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner.
 
 When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
 
@@ -116,33 +118,68 @@ Some customers might attempt to partially mitigate these risks by implementing s
 
 You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which user account performed the action.
 
-For example, you can use the audit log to track the `action:org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+For example, you can use the audit log to track the `org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
 
-The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Events for environments
+
+| 동작                                  | 설명                                                                                                                                                              |
+| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."   |
+| `environment.delete`                | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)."       |
+| `environment.remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." |
+| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."   |
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+#### Events for configuration changes
+| 동작                     | 설명                                                                                                                                                                                                                                                                       |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." |
+{% endif %}
 
 #### Events for secret management
-| 동작                                  | 설명                                                                                                                                                                                         |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action:org.create_actions_secret`  | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization). |
-| `action:org.remove_actions_secret`  | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret.                                                                                        |
-| `action:org.update_actions_secret`  | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret.                                                                                        |
-| `action:repo.create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).      |
-| `action:repo.remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret.                                                                                          |
-| `action:repo.update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret.                                                                                          |
+| 동작                           | 설명                                                                                                                                                                                                                                                                       |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `org.create_actions_secret`  | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)." |
+| `org.remove_actions_secret`  | Triggered when a {% data variables.product.prodname_actions %} secret is removed.                                                                                                                                                                                        |
+| `org.update_actions_secret`  | Triggered when a {% data variables.product.prodname_actions %} secret is updated.                                                                                                                                                                                        |
+| `repo.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."          |
+| `repo.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.                                                                                                                                                                                        |
+| `repo.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.                                                                                                                                                                                        |
 
 #### Events for self-hosted runners
-| 동작                                        | 설명                                                                                                                                                                                      |
-| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action:org.register_self_hosted_runner`  | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). |
-| `action:org.remove_self_hosted_runner`    | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).             |
-| `action:repo.register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository).       |
-| `action:repo.remove_self_hosted_runner`   | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository).                   |
+| 동작                                        | 설명                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% else %}                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `enterprise.register_self_hosted_runner`  | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an enterprise](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)."                                                                                                                                                                                                                                                                               |
+| `enterprise.remove_self_hosted_runner`    | Triggered when a self-hosted runner is removed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `enterprise.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."                                                                                                                                                                                                                                                                                           |
+| `enterprise.self_hosted_runner_updated`   | Triggered when the runner application is updated. Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."{% endif %}
+| `org.register_self_hosted_runner`         | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)."                                                                                                                                                                                                                                                                           |
+| `org.remove_self_hosted_runner`           | Triggered when a self-hosted runner is removed. For more information, see [Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).                                                                                                                                                                                                                                                                                                  |
+| `org.runner_group_runners_updated`        | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."                                                                                                                                                                                                                                                                                           |
+| `org.runner_group_updated`                | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."                                                                                                                                                                                                          |
+| `org.self_hosted_runner_updated`          | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                          |
+| `repo.register_self_hosted_runner`        | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."                                                                                                                                                                                                                                                                                 |
+| `repo.remove_self_hosted_runner`          | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."                                                                                                                                                                                                                                                                                                      |
+| `repo.self_hosted_runner_updated`         | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                          |
 
 #### Events for self-hosted runner groups
-| 동작                                        | 설명                                                                                                                                                                                                                        |
-| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action:org.runner_group_created`         | Triggered when an organization admin [creates a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization). |
-| `action:org.runner_group_removed`         | Triggered when an organization admin removes a self-hosted runner group.                                                                                                                                                  |
-| `action:org.runner_group_renamed`         | Triggered when an organization admin renames a self-hosted runner group.                                                                                                                                                  |
-| `action:org.runner_group_runners_added`   | Triggered when an organization admin [adds a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).                |
-| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group.                                                                                                                                           |
+| 동작                                       | 설명                                                                                                                                                                                                                                                                                                                 |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `enterprise.runner_group_created`        | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an enterprise](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)."                            |
+| `enterprise.runner_group_removed`        | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."                                                                |
+| `enterprise.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group.                                                                                                                                                                                                                                   |
+| `enterprise.runner_group_runners_added`  | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."                                                       |
+| `enterprise.runner_group_updated`        | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." |
+| `org.runner_group_created`               | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."                        |
+| `org.runner_group_removed`               | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."                                                                |
+| `org.runner_group_runners_added`         | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."                                                       |
+| `org.runner_group_runner_removed`        | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."                                                 |
+
+#### Events for workflow activities
+
+{% data reusables.actions.actions-audit-events-workflow %}
diff --git a/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index d18b11a58c..cd7a7836d6 100644
--- a/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ If you need to share workflows and other {% data variables.product.prodname_acti
 
 ### Creating a workflow template
 
-Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise or GitHub One plan.
+Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise plan.
 
 This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow.
 
 1. If it doesn't already exist, create a new public repository named `.github` in your organization.
-1. Create a directory named `workflow-templates`.
-1. Create your new workflow file inside the `workflow-templates` directory.
+2. Create a directory named `workflow-templates`.
+3. Create your new workflow file inside the `workflow-templates` directory.
 
    If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch.
 
@@ -52,7 +52,7 @@ This procedure demonstrates how to create a workflow template and metadata file.
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
+4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
    ```yaml
    {
        "name": "Octo Organization Workflow",
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..a41d459b53
--- /dev/null
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: Approving workflow runs from public forks
+intro: 'When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve any workflow runs.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+Forks of public repositories can submit pull requests that propose changes to a repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests are not run automatically if they are received from first-time contributors, and must be approved first.
+
+Maintainers with write access to the repository can use the following procedure to review and run workflows on pull requests from first-time contributors. After a contributor has at least one pull request merged into a project's repository, any future pull requests from that contributor's fork will automatically run workflows.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
+1. If you are comfortable with running workflows on the pull request branch, return to the {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
+
+   ![Approve and run workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index 5c3b16248a..9507a100cf 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Disabling and enabling a workflow
-intro: 'You can disable and re-enable a workflow using {% data variables.product.prodname_dotcom %} or the REST API.'
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}. You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
 
 Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
 
@@ -27,7 +27,9 @@ Temporarily disabling a workflow can be useful in many scenarios. These are a fe
 
 {% endwarning %}
 
-### Disabling a workflow
+### Disabling and enabling workflows with the {% data variables.product.prodname_dotcom %} UI
+
+#### Disabling a workflow
 
 You can manually disable a workflow so that it won't execute any workflow runs. A disabled workflow is not deleted, and can be re-enabled.
 
@@ -37,7 +39,7 @@ You can manually disable a workflow so that it won't execute any workflow runs.
 1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. Click **Disable workflow**. ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png) The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status. ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### Enabling a workflow
+#### Enabling a workflow
 
 You can re-enable a workflow that was previously disabled.
 
@@ -45,3 +47,23 @@ You can re-enable a workflow that was previously disabled.
 {% data reusables.repositories.actions-tab %}
 1. In the left sidebar, click the workflow you want to enable. ![actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. Click **Enable workflow**. ![actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+
+### Disabling and enabling workflows with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### Disabling and enabling workflows through the REST API
+
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 4f6f73cfca..c37ad5434f 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Configuring the retention period for GitHub Actions artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %}
 
+### Download artifacts with the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### Download artifacts with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+{% data variables.product.prodname_cli %} will download each artifact into separate directories based on the artifact name. If only a single artifact is specified, it will be extracted into the current directory.
+
+To download all artifacts generated by a workflow run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run download <em>run-id</em>
+```
+
+To download a specific artifact from a run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. Replace `artifact-name` with the name of the artifact that you want to download.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+You can specify more than one artifact.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+To download specific artifacts across all runs in a repository, use the `run download` subcommand.
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/index.md b/translations/ko-KR/content/actions/managing-workflow-runs/index.md
index 2606df2f97..2e9d581196 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/index.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index 9ac6d7f072..7388e7af69 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Manually running a workflow
-intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the REST API or from the Actions tab on {% data variables.product.prodname_dotcom %}.'
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -28,6 +28,40 @@ To trigger the `workflow_dispatch` event on {% data variables.product.prodname_d
 1. Above the list of workflow runs, select **Run workflow**. ![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
 1. Select the branch where the workflow will run and type the input parameters used by the workflow. Click **Run workflow**. ![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
 
+### Running a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+You can also pass inputs as JSON by using standard input.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
+
 ### Running a workflow using the REST API
 
 When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md
index f72ee39863..171c1397f3 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Re-run a workflow using the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### Re-run a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run.  If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 51b0352ed6..9f5b117a0e 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. Under **Artifacts**, click
-{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove.
+{% octicon "trash" aria-label="The trash icon" %} next to the artifact you want to remove.
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index db404eeba7..55b1e2f6b3 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ After deleting logs, the **Delete all logs** button is removed to indicate that
 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) After the logs have been deleted, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
 {% endif %}
+
+### Viewing logs with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To view the log for a specific job, use the `run view` subcommand. Replace `run-id` with the ID of run that you want to view logs for. {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a job from the run. If you don't specify `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run, and then returns another interactive menu for you to choose a job from the run.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+You can also use the `--job` flag to specify a job ID. Replace `job-id` with the ID of the job that you want to view logs for.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+You can use `grep` to search the log. For example, this command will return all log entries that contain the word `error`.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+To filter the logs for any failed steps, use `--log-failed` instead of `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/ko-KR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index 284bd3fcd9..e5370f30fa 100644
--- a/translations/ko-KR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/ko-KR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Viewing workflow run history on {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### Viewing workflow run history with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+#### Viewing recent workflow runs
+
+To list the recent workflow runs, use the `run list` subcommand.
+
+```shell
+gh run list
+```
+
+To specify the maximum number of runs to return, you can use the `-L` or `--limit` flag . The default is `10`.
+
+```shell
+gh run list --limit 5
+```
+
+To only return runs for the specified workflow, you can use the `-w` or `--workflow` flag.  Replace `workflow` with either the workflow name, workflow ID, or workflow file name. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### Viewing details for a specific workflow run
+
+To display details for a specific workflow run, use the `run view` subcommand. Replace `run-id` with the ID of the run that you want to view. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+To include job steps in the output, use the `-v` or `--verbose` flag.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+To view details for a specific job in the run, use the `-j` or `--job` flag.  Replace `job-id` with the ID of the job that you want to view.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+To view the full log for a job, use the `--log` flag.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Use the `--exit-status` flag to exit with a non-zero status if the run failed. 예시:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md b/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md
index 0a98243ac7..03dc9ee036 100644
--- a/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/ko-KR/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ The token is also available in the `github.token` context. For more information,
 
 ### Using the `GITHUB_TOKEN` in a workflow
 
-To use the `GITHUB_TOKEN` secret, you must reference it in your workflow file. Using a token might include passing the token as an input to an action that requires it, or making authenticated {% data variables.product.prodname_dotcom %} API calls.
+You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% data variables.product.prodname_dotcom %} API request.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### Example passing `GITHUB_TOKEN` as an input
+#### Example 1: passing the `GITHUB_TOKEN` as an input
 
 This example workflow uses the [labeler action](https://github.com/actions/labeler), which requires the `GITHUB_TOKEN` as the value for the `repo-token` input parameter:
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### Example calling the REST API
+#### Example 2: calling the REST API
 
 You can use the `GITHUB_TOKEN` to make authenticated API calls. This example workflow creates an issue using the {% data variables.product.prodname_dotcom %} REST API:
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,15 +88,31 @@ You can use the `GITHUB_TOKEN` to make authenticated API calls. This example wor
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_."
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### Permissions for the `GITHUB_TOKEN`
 
 For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)."
 
-| Permission          | Access type | Access by forked repos |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an enterprise, organization, or repository 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 {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-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 "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
+
+| 범위                  | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
+| ------------------- | ------------------------------------ | ------------------------------------ | --------------------------------------- |
+| actions             | read/write                           | none                                 | read                                    |
+| checks              | read/write                           | none                                 | read                                    |
+| contents            | read/write                           | read                                 | read                                    |
+| deployments         | read/write                           | none                                 | read                                    |
+| issues              | read/write                           | none                                 | read                                    |
+| 메타데이터               | read                                 | read                                 | read                                    |
+| 패키지                 | read/write                           | none                                 | read                                    |
+| pull requests       | read/write                           | none                                 | read                                    |
+| repository projects | read/write                           | none                                 | read                                    |
+| security events     | read/write                           | none                                 | read                                    |
+| statuses            | read/write                           | none                                 | read                                    |
+{% else %}
+| 범위                  | Access type | Access by forked repos |
 | ------------------- | ----------- | ---------------------- |
 | actions             | read/write  | read                   |
 | checks              | read/write  | read                   |
@@ -94,9 +124,32 @@ For information about the API endpoints {% data variables.product.prodname_githu
 | pull requests       | read/write  | read                   |
 | repository projects | read/write  | read                   |
 | statuses            | read/write  | read                   |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### Modifying the permissions for the `GITHUB_TOKEN`
+
+You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access.
+
+You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "Set up job" section of the workflow run log. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+
+You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
+
+{% data reusables.github-actions.forked-write-permission %}
+
+The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
+
+For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+
+##### How the permissions are calculated for a workflow job
+
+The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
+
+#### Granting additional permissions
+{% endif %}
+
 If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a personal access token and set it as a secret in your repository:
 
 1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
diff --git a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index cfa9092a61..ec762f4a5c 100644
--- a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ Contexts are a way to access information about workflow runs, runner environment
 | Context name | 유형   | 설명                                                                                                                                                                                                                                                |
 | ------------ | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `github`     | `개체` | Information about the workflow run. For more information, see [`github` context](#github-context).                                                                                                                                                |
-| `env`        | `개체` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context) .                                                                                                                         |
+| `env`        | `개체` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context).                                                                                                                          |
 | `작업`         | `개체` | Information about the currently executing job. For more information, see [`job` context](#job-context).                                                                                                                                           |
 | `steps`      | `개체` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context).                                                                                                                          |
 | `runner`     | `개체` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context).                                                                                                                      |
@@ -93,11 +93,11 @@ The `github` context contains information about the workflow run and the event t
 | `github.action`           | `문자열` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `run` when the current step runs a script.  If you use the same action more than once in the same job, the name will include a suffix with the sequence number.  For example, the first script you run will have the name `run1`, and the second script will be named `run2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
 | `github.action_path`      | `문자열` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite run steps actions.                                                                                                                                                                                                                                                                                                 |
 | `github.actor`            | `문자열` | The login of the user that initiated the workflow run.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `github.base_ref`         | `문자열` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`.                                                                                                                                                                                                                                                                                                                             |
+| `github.base_ref`         | `문자열` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                                                                                                                                                                                                               |
 | `github.event`            | `개체`  | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context.                                                                                                                                                                                                                                                                                        |
 | `github.event_name`       | `문자열` | The name of the event that triggered the workflow run.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | `github.event_path`       | `문자열` | The path to the full event webhook payload on the runner.                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `github.head_ref`         | `문자열` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`.                                                                                                                                                                                                                                                                                                                             |
+| `github.head_ref`         | `문자열` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                                                                                                                                                                                                               |
 | `github.job`              | `문자열` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                                                                                                                                                                                                                                                |
 | `github.ref`              | `문자열` | The branch or tag ref that triggered the workflow run. For branches this in the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                          |
 | `github.repository`       | `문자열` | The owner and repository name. For example, `Codertocat/Hello-World`.                                                                                                                                                                                                                                                                                                                                                                                                                               |
@@ -323,7 +323,7 @@ Returns `true` if `searchString` ends with `searchValue`. This function is not c
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-Replaces values in the `string`, with the variable `replaceValueN`. Variables in the `string` are specified using the `{N}` syntax, where `N` is an integer. You must specify at least one `replaceValue` and `string`. There is no maximum for the number of variables (`replaceValueN`) you can use. Escape curly braces useing double braces.
+Replaces values in the `string`, with the variable `replaceValueN`. Variables in the `string` are specified using the `{N}` syntax, where `N` is an integer. You must specify at least one `replaceValue` and `string`. There is no maximum for the number of variables (`replaceValueN`) you can use. Escape curly braces using double braces.
 
 ##### 예시
 
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
diff --git a/translations/ko-KR/content/actions/reference/encrypted-secrets.md b/translations/ko-KR/content/actions/reference/encrypted-secrets.md
index 6420f45af1..32884126ce 100644
--- a/translations/ko-KR/content/actions/reference/encrypted-secrets.md
+++ b/translations/ko-KR/content/actions/reference/encrypted-secrets.md
@@ -29,15 +29,9 @@ For secrets stored at the environment level, you can enable required reviewers t
 
 #### Naming your secrets
 
-The following rules apply to secret names:
+{% data reusables.codespaces.secrets-naming %}. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
 
-* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
-* Secret names must not start with the `GITHUB_` prefix.
-* Secret names must not start with a number.
-* Secret names are not case-sensitive.
-* Secret names must be unique at the level they are created at. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
-
-  If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
+  {% data reusables.codespaces.secret-precedence %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
 
 To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs.
 
@@ -83,7 +77,8 @@ If your repository {% if currentVersion == "free-pro-team@latest" or currentVers
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" }
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+
 ### Creating encrypted secrets for an environment
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
@@ -125,7 +120,11 @@ You can check which access policies are being applied to a secret in your organi
 
 ### Using encrypted secrets in a workflow
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
+
+**Note:** {% data reusables.actions.forked-secrets %}
+
+{% endnote %}
 
 To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 
diff --git a/translations/ko-KR/content/actions/reference/environment-variables.md b/translations/ko-KR/content/actions/reference/environment-variables.md
index 9044dde564..9d1a7a7d72 100644
--- a/translations/ko-KR/content/actions/reference/environment-variables.md
+++ b/translations/ko-KR/content/actions/reference/environment-variables.md
@@ -58,6 +58,7 @@ We strongly recommend that actions use environment variables to access the files
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
 | `GITHUB_JOB`         | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                                                                                                                 |
 | `GITHUB_ACTION`      | The unique identifier (`id`) of the action.                                                                                                                                                                                                                                                                                                                        |
+| `GITHUB_ACTION_PATH` | The path where your action is located. You can use this path to access files located in the same repository as your action. This variable is only supported in composite run steps actions.                                                                                                                                                                        |
 | `GITHUB_ACTIONS`     | Always set to `true` when {% data variables.product.prodname_actions %} is running the workflow. You can use this variable to differentiate when tests are being run locally or by {% data variables.product.prodname_actions %}.                                                                                                                                |
 | `GITHUB_ACTOR`       | The name of the person or app that initiated the workflow. For example, `octocat`.                                                                                                                                                                                                                                                                                 |
 | `GITHUB_REPOSITORY`  | The owner and repository name. For example, `octocat/Hello-World`.                                                                                                                                                                                                                                                                                                 |
@@ -84,10 +85,6 @@ We strongly recommend that actions use environment variables to access the files
 
 ### Naming conventions for environment variables
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dotcom %} reserves the `GITHUB_` environment variable prefix for internal use by {% data variables.product.prodname_dotcom %}. Setting an environment variable or secret with the `GITHUB_` prefix will result in an error.
-
-{% endnote %}
+When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
 
 Any new environment variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `HOME` and `GITHUB_WORKSPACE` default variables are exceptions to this convention because the words "home" and "workspace" already imply a location.
diff --git a/translations/ko-KR/content/actions/reference/environments.md b/translations/ko-KR/content/actions/reference/environments.md
index d0e0ca0360..176d45cb8d 100644
--- a/translations/ko-KR/content/actions/reference/environments.md
+++ b/translations/ko-KR/content/actions/reference/environments.md
@@ -48,6 +48,12 @@ Use deployment branches to restrict which branches can deploy to the environment
 
 Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 
+{% note %}
+
+**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level as security as repository and organization secrets. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+{% endnote %}
+
 ### Creating an environment
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -71,6 +77,9 @@ For more information on syntax to reference environments in workflows, see "[Wor
 
 When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
+### Using concurrency to serialize deployments in an environment
+You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#concurrency)."
+
 ### Deleting an environment
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -80,7 +89,7 @@ Deleting an environment will delete all secrets and protection rules associated
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
+1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
 2. Click **I understand, delete this environment**.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
diff --git a/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md b/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md
index b673d32d88..4e54d668f5 100644
--- a/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        echo "- in ${{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          echo "- in ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ Runs your workflow anytime the `check_run` event occurs. {% data reusables.devel
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload                              | Activity types                                                                               | `GITHUB_SHA`                  | `GITHUB_REF`   |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ----------------------------- | -------------- |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | Last commit on default branch | Default branch |
+| Webhook event payload                              | Activity types                                                | `GITHUB_SHA`                  | `GITHUB_REF`   |
+| -------------------------------------------------- | ------------------------------------------------------------- | ----------------------------- | -------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | Last commit on default branch | Default branch |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a check run has been `rerequested` or `requested_action`.
+For example, you can run a workflow when a check run has been `rerequested` or `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ For example, you can run a workflow when a project card has been `opened` or `de
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**Note:** The `prereleased` type will not trigger for pre-releases published from draft releases, but the `published` type will trigger. If you want a workflow to run when stable *and* pre-releases publish, subscribe to `published` instead of `released` and `prereleased`.
+
+{% endnote %}
+
 #### `상태`
 
 Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/rest/reference/repos#statuses).
diff --git a/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md
index 2f2c23e5db..3a622d80e4 100644
--- a/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/ko-KR/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### Adding a system path
diff --git a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md
index 14455bdc84..e9961fed58 100644
--- a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -110,8 +110,8 @@ The following workflow will run on pushes to `releases/10` or `releases/beta/mon
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
@@ -128,7 +128,7 @@ When all the path names match patterns in `paths-ignore`, the workflow will not
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
 #### Example including paths
@@ -139,7 +139,7 @@ If at least one path matches a pattern in the `paths` filter, the workflow runs.
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
 #### Excluding paths
@@ -160,8 +160,8 @@ This example runs anytime the `push` event includes a file in the `sub-project`
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
 #### Git diff comparisons
@@ -187,6 +187,32 @@ For more information, see "[About comparing branches in pull requests](/articles
 
 For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)."
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify.  For more information, see [`jobs.<job_id>.permissions`](#jobsjob_idpermissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### 예시
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will apply to all jobs in the workflow. All permissions are granted read access.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
+
 ### `env`
 
 A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
@@ -221,6 +247,18 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the `github` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+You can also specify `concurrency` at the job level. For more information, see [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs`
 
 A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs.<job_id>.needs` keyword.
@@ -339,6 +377,34 @@ runs-on: [self-hosted, linux]
 
 For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](#permissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### 예시
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access.
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 ### `jobs.<job_id>.environment`
 
@@ -347,10 +413,11 @@ The environment that the job references. All environment protection rules must p
 You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
 
 ##### Example using a single environment name
-
+{% raw %}
 ```yaml
 environment: staging_environment
 ```
+{% endraw %}
 
 ##### Example using environment name and URL
 
@@ -372,6 +439,25 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other.
+
+{% endnote %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
 A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs.<job_id>.needs`](#jobsjob_idneeds).
@@ -392,15 +478,15 @@ jobs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
@@ -470,14 +556,14 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
@@ -609,11 +695,11 @@ jobs:
 ```
 
 {% if currentVersion == "free-pro-team@latest" %}
-##### Example using the {% data variables.product.prodname_github_container_registry %}
+##### Example using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in the {% data variables.product.prodname_github_container_registry %}.
+A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
 
 ```yaml
 jobs:
@@ -639,7 +725,9 @@ jobs:
 
 #### Example using action inside a different private repository than the workflow
 
-Your workflow must checkout the private repository and reference the action locally.
+Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
 
 {% raw %}
 ```yaml
@@ -651,7 +739,7 @@ jobs:
         with:
           repository: octocat/my-private-repo
           ref: v1.0
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
           path: ./.github/actions/my-private-repo
       - name: Run my action
         uses: ./.github/actions/my-private-repo/my-action
@@ -899,7 +987,7 @@ The order that you define a `matrix` matters. The first option you define will b
 
 #### Example running with more than one version of Node.js
 
-You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 6, 8, and 10, you could specify an array of those versions in the `matrix`.
+You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 10, 12, and 14, you could specify an array of those versions in the `matrix`.
 
 This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version.
 
@@ -907,10 +995,10 @@ This example creates a matrix of three jobs by setting the `node` key to an arra
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
   # Configures the node version used on GitHub-hosted runners
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       # The Node.js version to configure
       node-version: ${{ matrix.node }}
@@ -933,10 +1021,10 @@ You can create a matrix to run workflows on more than one runner operating syste
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
@@ -948,7 +1036,7 @@ steps:
 
 #### Example including additional values into combinations
 
-You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 4 of `node` runs, you can use `include` to specify that additional option.
+You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 8 of `node` runs, you can use `include` to specify that additional option.
 
 {% raw %}
 ```yaml
@@ -956,29 +1044,29 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 2
+      # includes a new variable of npm with a value of 6
       # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
 #### Example including new combinations
 
-You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 12 to build on multiple operating systems, but wanted one extra experimental job using node version 13 on Ubuntu, you can use `include` to specify that additional job.
+You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 14 to build on multiple operating systems, but wanted one extra experimental job using node version 15 on Ubuntu, you can use `include` to specify that additional job.
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -994,11 +1082,11 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # excludes node 4 on macOS
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
@@ -1033,7 +1121,7 @@ Prevents a workflow run from failing when a job fails. Set to `true` to allow a
 
 #### Example preventing a specific failing matrix job from failing a workflow run
 
-You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `13` to fail without failing the workflow run.
+You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
 
 {% raw %}
 ```yaml
@@ -1042,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -1064,7 +1152,7 @@ If you do not set a `container`, all steps will run directly on the host specifi
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -1079,7 +1167,7 @@ When you only specify a container image, you can omit the `image` keyword.
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
@@ -1181,7 +1269,7 @@ The Docker image to use as the service container to run the action. The value ca
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 29eab55bcd..7b98bceae2 100644
--- a/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ For the overall list of included tools for each runner operating system, see the
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ We recommend using actions to interact with the software installed on runners. T
 
 If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners.
 
+#### Installing additional software
+
+You can install additional software on {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Customizing GitHub-hosted runners](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
 ### IP addresses
 
 {% note %}
diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..fa8b92c9d6
--- /dev/null
+++ b/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Customizing GitHub-hosted runners
+intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow.
+
+To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+
+This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner.
+
+### Installing software on Ubuntu runners
+
+The following example demonstrates how to install an `apt` package as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**Note:** Always run `sudo apt-get update` before installing a package. In case the `apt` index is stale, this command fetches and re-indexes any available packages, which helps prevent package installation failures.
+
+{% endnote %}
+
+### Installing software on macOS runners
+
+The following example demonstrates how to install Brew packages and casks as part of a job.
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### Installing software on Windows runners
+
+The following example demonstrates how to use [Chocolatey](https://community.chocolatey.org/packages) to install the {% data variables.product.prodname_dotcom %} CLI as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/index.md b/translations/ko-KR/content/actions/using-github-hosted-runners/index.md
index 681269a253..fb91ee9e64 100644
--- a/translations/ko-KR/content/actions/using-github-hosted-runners/index.md
+++ b/translations/ko-KR/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% link_in_list /about-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/ko-KR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/ko-KR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..9793d2f7e2
--- /dev/null
+++ b/translations/ko-KR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: About licensing for GitHub Advanced Security
+intro: 'You need a license to use {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### About licensing for {% data variables.product.prodname_GH_advanced_security %}
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% data reusables.advanced-security.license-overview %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for {% data variables.product.product_name %}, contact {% data variables.contact.contact_enterprise_sales %}. To enable {% data variables.product.prodname_GH_advanced_security %}, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your appliance](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### Managing your license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+
+For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+
+### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..e380519195
--- /dev/null
+++ b/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: Configuring code scanning for your appliance
+shortTitle: Configuring code scanning
+intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### About {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+### Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
+
+#### Setting up a self-hosted runner
+
+{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions.
+
+#### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+
+You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
+
+#### Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access
+If the server on which you are running {% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} action sync tool to copy the {% data variables.product.prodname_codeql %} analysis bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/).
+
+If you set up the {% data variables.product.prodname_codeql %} action sync tool, you can use it to sync the latest releases of the {% data variables.product.prodname_codeql %} action and associated {% data variables.product.prodname_codeql %} analysis bundle. These are compatible with {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways.
+
+- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)."
+- If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer.
+- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases.
+{% endif %}
+
+#### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}
+1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)."
+2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
+3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
+4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}
+If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}.
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
diff --git a/translations/ko-KR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/ko-KR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..235ca27807
--- /dev/null
+++ b/translations/ko-KR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: Configuring secret scanning for your appliance
+shortTitle: Configuring secret scanning
+intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### About {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+
+### Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+
+- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}.
+
+- A license for {% data variables.product.prodname_GH_advanced_security %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### Checking support for the SSSE3 flag on your vCPUs
+
+The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance.
+
+1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+2. Enter the following command:
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs.
+
+#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### Enabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. ![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### Disabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_secret_scanning_caps %}**. ![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..0c598b26ed
--- /dev/null
+++ b/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% if currentVersion == "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+{% endif %}
+
+### Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} For information about licensing, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
+2. Upload the new license to {% data variables.product.product_location %}. For more information, see "[Managing your GitHub Enterprise license](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Under "{% data variables.product.prodname_advanced_security %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+
+### Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} via the administrative shell (SSH)
+
+You can enable or disable features programmatically on {% data variables.product.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)."
+
+For example, you can enable {% data variables.product.prodname_code_scanning %} with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
+
+1. SSH into {% data variables.product.product_location %}.
+1. Enable {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. Optionally, disable {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. Apply the configuration.
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}To enable and disable {% data variables.product.prodname_secret_scanning %} in the same way, set: `ghe-config app.secret-scanning.enabled` true or false and apply the configuration.{% endif %}
diff --git a/translations/ko-KR/content/admin/advanced-security/index.md b/translations/ko-KR/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..7761e2edff
--- /dev/null
+++ b/translations/ko-KR/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing GitHub Advanced Security for your enterprise
+shortTitle: Managing GitHub Advanced Security
+intro: You can configure {% data variables.product.prodname_advanced_security %} and manage use by your enterprise to suit your organization's needs.
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### Table of Contents
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/ko-KR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/ko-KR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..670d420947
--- /dev/null
+++ b/translations/ko-KR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,23 @@
+---
+title: Viewing your GitHub Advanced Security usage
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."
+
+### Viewing license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+You can check how many seats your license includes and how many seats are currently in use.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[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/ko-KR/content/admin/all-releases.md b/translations/ko-KR/content/admin/all-releases.md
new file mode 100644
index 0000000000..4205448568
--- /dev/null
+++ b/translations/ko-KR/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Enterprise Server releases
+intro: 'Documentation for the currently supported and previously deprecated versions of {{ site.data.variables.product.prodname_ghe_server }}.'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## Currently supported
+
+See [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) for information about the latest release.
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## Deprecated
+
+Documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## Deprecated developer documentation
+
+Developer documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/ko-KR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/ko-KR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index 6aedb8478b..b9c2875ad5 100644
--- a/translations/ko-KR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: 'You can use {% if enterpriseServerVersions contains currentVersion %}{%
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### About identity and access management for your enterprise
diff --git a/translations/ko-KR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/ko-KR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index ebc9232047..183900bc53 100644
--- a/translations/ko-KR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/ko-KR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### About built-in authentication for users outside your identity provider
diff --git a/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md b/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md
index 5f2d5efa5b..81dd010f34 100644
--- a/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/ko-KR/content/admin/authentication/changing-authentication-methods.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 User accounts on {% data variables.product.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change.
diff --git a/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index a0a17983e8..94b419600a 100644
--- a/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About authentication and user provisioning with Azure AD
diff --git a/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index fe58ac3be4..383778fb9f 100644
--- a/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About SAML SSO
diff --git a/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index ffd93d0a25..ccda9e7aa4 100644
--- a/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About user provisioning for your enterprise
diff --git a/translations/ko-KR/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/ko-KR/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index 5b05b167d2..c420e4f682 100644
--- a/translations/ko-KR/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/ko-KR/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: 'If you''re using built-in authentication, you can block unauthenticated people from being able to create an account.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/authentication/using-built-in-authentication.md b/translations/ko-KR/content/admin/authentication/using-built-in-authentication.md
index 2a1d42b98e..31e6d36e57 100644
--- a/translations/ko-KR/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/ko-KR/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 You can create custom messages that users will see on the sign in and sign out pages. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)."
diff --git a/translations/ko-KR/content/admin/authentication/using-cas.md b/translations/ko-KR/content/admin/authentication/using-cas.md
index a5d404b627..7af06596a6 100644
--- a/translations/ko-KR/content/admin/authentication/using-cas.md
+++ b/translations/ko-KR/content/admin/authentication/using-cas.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% if currentVersion ver_gt "enterprise-server@2.16" %}user license{% else %}seat{% endif %} until the user signs in.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ko-KR/content/admin/authentication/using-ldap.md b/translations/ko-KR/content/admin/authentication/using-ldap.md
index 87467b29ad..23c1f9ab3e 100644
--- a/translations/ko-KR/content/admin/authentication/using-ldap.md
+++ b/translations/ko-KR/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: 'LDAP lets you authenticate {% data variables.product.prodname_ghe_server %} against your existing accounts and centrally manage repository access. LDAP is a popular application protocol for accessing and maintaining directory information services, and is one of the most common protocols used to integrate third-party software with large company user directories.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ko-KR/content/admin/authentication/using-saml.md b/translations/ko-KR/content/admin/authentication/using-saml.md
index ec34df8dfb..e1bc9837bf 100644
--- a/translations/ko-KR/content/admin/authentication/using-saml.md
+++ b/translations/ko-KR/content/admin/authentication/using-saml.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'SAML is an XML-based standard for authentication and authorization. {% data variables.product.prodname_ghe_server %} can act as a service provider (SP) with your internal SAML identity provider (IdP).'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ko-KR/content/admin/configuration/about-enterprise-configuration.md b/translations/ko-KR/content/admin/configuration/about-enterprise-configuration.md
index aea778d725..600c3450f1 100644
--- a/translations/ko-KR/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/ko-KR/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: 'You can use the site admin dashboard{% if enterpriseServerVersions conta
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 The first time you access your enterprise, you will complete an initial configuration to get
-{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an idP, authenticating with SAML SSO, and configuring policies for repositories and organizations in your enterprise. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-
-For users to receive any emails from {% data variables.product.product_name %} after the initial configuration, you must ask {% data variables.contact.github_support %} to configure outbound email support with your SMTP server. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)."
+{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an identity provider (IdP), authenticating with SAML SSO, configuring policies for repositories and organizations in your enterprise, and configuring SMTP for outbound email. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
 
 Later, you can use the site admin dashboard and enterprise settings to further configure your enterprise, manage users, organizations and repositories, and set policies that reduce risk and increase quality.
 
diff --git a/translations/ko-KR/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/ko-KR/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index 6fd326734b..a7f7caae00 100644
--- a/translations/ko-KR/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/ko-KR/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### About administrative shell access
diff --git a/translations/ko-KR/content/admin/configuration/accessing-the-management-console.md b/translations/ko-KR/content/admin/configuration/accessing-the-management-console.md
index f0adf005d9..5b2b4d0ca8 100644
--- a/translations/ko-KR/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/ko-KR/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### About the {% data variables.enterprise.management_console %}
diff --git a/translations/ko-KR/content/admin/configuration/command-line-utilities.md b/translations/ko-KR/content/admin/configuration/command-line-utilities.md
index 5ddd2a1109..2d55a4fca0 100644
--- a/translations/ko-KR/content/admin/configuration/command-line-utilities.md
+++ b/translations/ko-KR/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
@@ -483,9 +485,15 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 To show the full hook payload, result, and any exceptions for the delivery:
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### Clustering
 
@@ -644,14 +652,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-This utility imports from Team Foundation Version Control. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+This utility imports from Team Foundation Version Control (TFVC). For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFS, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-rewrite
 ```
diff --git a/translations/ko-KR/content/admin/configuration/configuring-a-hostname.md b/translations/ko-KR/content/admin/configuration/configuring-a-hostname.md
index 54160261c6..969ed98d2c 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that {% data variables.product.product_location %} runs on without affecting users or client software.
diff --git a/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 5f5c4ffbf2..af7829ccc9 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 When a proxy server is enabled for {% data variables.product.product_location %}, outbound messages sent by {% data variables.product.prodname_ghe_server %} are first sent through the proxy server, unless the destination host is added as an HTTP proxy exclusion. Types of outbound messages include outgoing webhooks, uploading bundles, and fetching legacy avatars. The proxy server's URL is the protocol, domain or IP address, plus the port number, for example `http://127.0.0.1:8123`.
diff --git a/translations/ko-KR/content/admin/configuration/configuring-applications.md b/translations/ko-KR/content/admin/configuration/configuring-applications.md
index c537b568d9..7840ded67f 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-applications.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Adjusting image caching
diff --git a/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md
index f922095344..6f2579c2b0 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: Configuring backups on your appliance
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### About {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/ko-KR/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/ko-KR/content/admin/configuration/configuring-built-in-firewall-rules.md
index 098709faab..bdb64f0a92 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### About {% data variables.product.product_location %}'s firewall
diff --git a/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index c242fd9bb0..19c11b2328 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: Configuring data encryption
 intro: 'For encryption at rest, you can provide your own encryption key to encrypt your data under your encryption policies.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 To provide a high level of security, {% data variables.product.product_name %} encrypts your data while at rest in the data centers and while your data is in transit between users' machines and the data centers.
 
-For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. After you've initialized your enterprise, you can choose to provide your own key instead. Your key should be a 2048 bit RSA private key in PEM format.
-
-The key that you provide is stored in a FIPS 140-2 compliant hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages.
-
-To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
-
-### Adding or updating an encryption key
-
-You can add a new encryption key as often as you need. When you add a new key, the old key is discarded. Your enterprise won't experience downtime when you update the key.
-
-Your 2048 bit RSA private key should be in PEM format, for example in a file called _private-key.pem_.
-
-   ```
-   -----BEGIN RSA PRIVATE KEY-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----END RSA PRIVATE KEY-----
-   ```
-
-1. To add your key, use the `PATCH /enterprise/encryption` endpoint, replacing *~/private-key.pem* with the path to your private key.
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. Optionally, check the status of the update operation.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### Disabling your encryption key
-
-To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
-
-1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
-
-### 더 읽을거리
-
-- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation 
+For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. 
diff --git a/translations/ko-KR/content/admin/configuration/configuring-dns-nameservers.md b/translations/ko-KR/content/admin/configuration/configuring-dns-nameservers.md
index b4179fd598..96a0e4954f 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 The nameservers you specify must resolve {% data variables.product.product_location %}'s hostname.
diff --git a/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md b/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md
index ee2ff7cadc..356537a452 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/ko-KR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/ko-KR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index 609857dc18..c36c074446 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### Enabling public sites for {% data variables.product.prodname_pages %}
diff --git a/translations/ko-KR/content/admin/configuration/configuring-rate-limits.md b/translations/ko-KR/content/admin/configuration/configuring-rate-limits.md
index 2ee7b09ef2..b4f780f806 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### Enabling rate limits for {% data variables.product.prodname_enterprise_api %}
diff --git a/translations/ko-KR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/ko-KR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index bad85c20c7..9a8fa10e3f 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/ko-KR/content/admin/configuration/configuring-time-synchronization.md b/translations/ko-KR/content/admin/configuration/configuring-time-synchronization.md
index 4ca5725025..8043b2ff42 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Changing the default NTP servers
diff --git a/translations/ko-KR/content/admin/configuration/configuring-tls.md b/translations/ko-KR/content/admin/configuration/configuring-tls.md
index 47a99208dc..92d114bcf6 100644
--- a/translations/ko-KR/content/admin/configuration/configuring-tls.md
+++ b/translations/ko-KR/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### About Transport Layer Security
diff --git a/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 8e50c323ba..ce2f883761 100644
--- a/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/ko-KR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### About {% data variables.product.prodname_github_connect %}
diff --git a/translations/ko-KR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/ko-KR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index ae9cdeaf7c..7a097e1ba5 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}
diff --git a/translations/ko-KR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/ko-KR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index 4bc825c5a0..a9d163635d 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### About maintenance mode
diff --git a/translations/ko-KR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ko-KR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 57fdd9606f..ba37060cfd 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### About license synchronization
diff --git a/translations/ko-KR/content/admin/configuration/enabling-private-mode.md b/translations/ko-KR/content/admin/configuration/enabling-private-mode.md
index 02ee4c2b05..41af99eb4a 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-private-mode.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 You must enable private mode if {% data variables.product.product_location %} is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over `git://`. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "[Using built-in authentication](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)."
diff --git a/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md b/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md
index 3fe191f6a4..b1ac8a51c9 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### About subdomain isolation
@@ -19,7 +24,7 @@ When subdomain isolation is enabled, {% data variables.product.prodname_ghe_serv
 
 {% if currentVersion == "enterprise-server@2.22" %}
 To use Docker with
-{% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)."
+{% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/ko-KR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/ko-KR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index c638609ec9..92e0978d90 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 As a site administrator, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.prodname_ghe_server %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph.
diff --git a/translations/ko-KR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/ko-KR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index b14a57aeab..5801dda7ea 100644
--- a/translations/ko-KR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/ko-KR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location_enterprise %}.
diff --git a/translations/ko-KR/content/admin/configuration/index.md b/translations/ko-KR/content/admin/configuration/index.md
index 52861ec7d8..1be14baeb9 100644
--- a/translations/ko-KR/content/admin/configuration/index.md
+++ b/translations/ko-KR/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/ko-KR/content/admin/configuration/initializing-github-ae.md b/translations/ko-KR/content/admin/configuration/initializing-github-ae.md
index ddd46d99d1..0a2e7054bd 100644
--- a/translations/ko-KR/content/admin/configuration/initializing-github-ae.md
+++ b/translations/ko-KR/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: Initializing GitHub AE
 intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### About initialization
@@ -79,11 +82,11 @@ Once this is initialized, you can reconfigure any settings after the initializat
 1. To the right of "Configure email settings", click **Configure**. !["Configure" button for email settings configuration](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Complete your email server settings:
-  - In the **Server address** field, type the address of your SMTP server.
-  - In the **Port** field, type the port that your SMTP server uses to send email.
-  - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
-  - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
-  - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
+    - In the **Server address** field, type the address of your SMTP server.
+    - In the **Port** field, type the port that your SMTP server uses to send email.
+    - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+    - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
+    - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
 
 4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. Click **Test email settings**. !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 2358f1b0ab..2b7850d503 100644
--- a/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: 'You can decide whether authenticated users can connect to {% data variab
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ko-KR/content/admin/configuration/network-ports.md b/translations/ko-KR/content/admin/configuration/network-ports.md
index d548eaeb8e..b596b592ce 100644
--- a/translations/ko-KR/content/admin/configuration/network-ports.md
+++ b/translations/ko-KR/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Administrative ports
diff --git a/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index c87d759095..bdf3f30676 100644
--- a/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -4,6 +4,13 @@ shortTitle: Restricting network traffic
 intro: You can use an IP allow list to restrict access to your enterprise to connections from specified IP addresses.
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### About IP allow lists
diff --git a/translations/ko-KR/content/admin/configuration/site-admin-dashboard.md b/translations/ko-KR/content/admin/configuration/site-admin-dashboard.md
index 9149ba89ce..9245f6bfc3 100644
--- a/translations/ko-KR/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/ko-KR/content/admin/configuration/site-admin-dashboard.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 To access the dashboard, in the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}. ![Rocket ship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/ko-KR/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/ko-KR/content/admin/configuration/troubleshooting-ssl-errors.md
index f84c128894..dfb33ad5d2 100644
--- a/translations/ko-KR/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/ko-KR/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### Removing the passphrase from your key file
diff --git a/translations/ko-KR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/ko-KR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index 34c481736d..51a81c3e7f 100644
--- a/translations/ko-KR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/ko-KR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/ko-KR/content/admin/configuration/validating-your-domain-settings.md b/translations/ko-KR/content/admin/configuration/validating-your-domain-settings.md
index aef34f5c0b..25a765f31e 100644
--- a/translations/ko-KR/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/ko-KR/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/ko-KR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/ko-KR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/ko-KR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/ko-KR/content/admin/enterprise-management/about-cluster-nodes.md b/translations/ko-KR/content/admin/enterprise-management/about-cluster-nodes.md
index e4377f1f12..11f5886486 100644
--- a/translations/ko-KR/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/ko-KR/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/enterprise-management/about-clustering.md b/translations/ko-KR/content/admin/enterprise-management/about-clustering.md
index 6e92726533..b586ce8fb6 100644
--- a/translations/ko-KR/content/admin/enterprise-management/about-clustering.md
+++ b/translations/ko-KR/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/enterprise-management/about-geo-replication.md b/translations/ko-KR/content/admin/enterprise-management/about-geo-replication.md
index ccf7778d30..9eb440acdd 100644
--- a/translations/ko-KR/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/ko-KR/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London.
diff --git a/translations/ko-KR/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/ko-KR/content/admin/enterprise-management/about-high-availability-configuration.md
index 2c244cdeda..9f3bfce2db 100644
--- a/translations/ko-KR/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/ko-KR/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 When you configure high availability, there is an automated setup of one-way, asynchronous replication of all datastores (Git repositories, MySQL, Redis, and Elasticsearch) from the primary to the replica appliance.
diff --git a/translations/ko-KR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/ko-KR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 59af4f4dab..aa002a29e2 100644
--- a/translations/ko-KR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/ko-KR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Accessing the monitor dashboard
diff --git a/translations/ko-KR/content/admin/enterprise-management/cluster-network-configuration.md b/translations/ko-KR/content/admin/enterprise-management/cluster-network-configuration.md
index 7ad08c1329..9e2183eb83 100644
--- a/translations/ko-KR/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/ko-KR/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### Network considerations
diff --git a/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md b/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md
index a698a5e92a..33260f463c 100644
--- a/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/ko-KR/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Set up an external `collectd` server
diff --git a/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index 6d39c3cfca..1aa1d2ddcc 100644
--- a/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/ko-KR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About high availability replication for clusters
@@ -22,7 +26,7 @@ We recommend configuring high availability as a part of a comprehensive disaster
 
 #### Hardware and software
 
-For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 64 GB of RAM, and 750 GB of attached storage.
+For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage.
 
 On each new virtual machine, install the same version of {% data variables.product.prodname_ghe_server %} that runs on the nodes in your active cluster. You don't need to upload a license or perform any additional configuration. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)."
 
diff --git a/translations/ko-KR/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/ko-KR/content/admin/enterprise-management/creating-a-high-availability-replica.md
index adc5cb4919..9a73e69421 100644
--- a/translations/ko-KR/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/ko-KR/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/ko-KR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/ko-KR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index 62e395e8a2..16aaec34d4 100644
--- a/translations/ko-KR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/ko-KR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Failure scenarios
diff --git a/translations/ko-KR/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/ko-KR/content/admin/enterprise-management/enabling-automatic-update-checks.md
index 3e6a0cd329..14c7501dda 100644
--- a/translations/ko-KR/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/ko-KR/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 When an upgrade package is automatically downloaded for {% data variables.product.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.product.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)."
diff --git a/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md
index b740c95ae4..81f8691a6c 100644
--- a/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/ko-KR/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/ko-KR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index 03746bec39..a6fc068013 100644
--- a/translations/ko-KR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/ko-KR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/ko-KR/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/ko-KR/content/admin/enterprise-management/increasing-storage-capacity.md
index 928fc04b9f..c5b3f1b139 100644
--- a/translations/ko-KR/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/ko-KR/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -31,7 +35,10 @@ As more users join {% data variables.product.product_location %}, you may need t
 1. Resize the existing user volume disk using your virtualization platform's tools.
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
-4. Reboot the appliance to detect the new storage allocation.
+4. Reboot the appliance to detect the new storage allocation:
+  ```shell
+  $ sudo reboot
+  ```
 5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ As more users join {% data variables.product.product_location %}, you may need t
 ### Increasing the root partition size using a new appliance
 
 1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
-2. Shut down the current appliance.
+2. Shut down the current appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 3. Detach the data disk from the current appliance using your virtualization platform's tools.
 4. Attach the data disk to the new appliance with the larger root disk.
 
@@ -57,6 +67,9 @@ As more users join {% data variables.product.product_location %}, you may need t
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. Shut down the appliance.
+4. Shut down the appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 5. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
 6. Start the appliance.
diff --git a/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md b/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md
index bd7db2d848..d26a1e9c72 100644
--- a/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/ko-KR/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 5edd1e08ed..773707f899 100644
--- a/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 The time required to failover depends on how long it takes to manually promote the replica and redirect traffic. The average time ranges between 2-10 minutes.
diff --git a/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index 26617e9c22..08da66c750 100644
--- a/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About failover to your replica cluster
diff --git a/translations/ko-KR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/ko-KR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index 194e1c4f37..f0597246e3 100644
--- a/translations/ko-KR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/ko-KR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -12,8 +12,11 @@ redirect_from:
 intro: 'To migrate from {% data variables.product.prodname_enterprise %} 11.10.x to 2.1.23, you''ll need to set up a new appliance instance and migrate data from the previous instance.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 Migrations from {% data variables.product.prodname_enterprise %} 11.10.348 and later are supported. Migrating from {% data variables.product.prodname_enterprise %} 11.10.348 and earlier is not supported. You must first upgrade to 11.10.348 in several upgrades. For more information, see the 11.10.348 upgrading procedure, "[Upgrading to the latest release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)."
diff --git a/translations/ko-KR/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/ko-KR/content/admin/enterprise-management/monitoring-cluster-nodes.md
index 63ec7bdb83..81c4b41204 100644
--- a/translations/ko-KR/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/ko-KR/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -6,8 +6,14 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Manually checking cluster status
diff --git a/translations/ko-KR/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/ko-KR/content/admin/enterprise-management/monitoring-using-snmp.md
index 57f13d6bff..88c606587b 100644
--- a/translations/ko-KR/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/ko-KR/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP is a common standard for monitoring devices over a network. We strongly recommend enabling SNMP so you can monitor the health of {% data variables.product.product_location %} and know when to add more memory, storage, or processor power to the host machine.
diff --git a/translations/ko-KR/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/ko-KR/content/admin/enterprise-management/recommended-alert-thresholds.md
index 535133a84c..2483a58d6d 100644
--- a/translations/ko-KR/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/ko-KR/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### Monitoring storage
diff --git a/translations/ko-KR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/ko-KR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index 7424886651..fa0fef37f5 100644
--- a/translations/ko-KR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/ko-KR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 You can use the former primary appliance as the new replica appliance if the failover was planned or was not related to the health of the appliance. If the failover was related to an issue with the primary appliance, you may prefer to create a new replica appliance. For more information, see "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)."
diff --git a/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md
index 6bd2642b8d..f41c196815 100644
--- a/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/ko-KR/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### Stopping replication temporarily
diff --git a/translations/ko-KR/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/ko-KR/content/admin/enterprise-management/replacing-a-cluster-node.md
index d543180faf..749940e87b 100644
--- a/translations/ko-KR/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/ko-KR/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/ko-KR/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/ko-KR/content/admin/enterprise-management/setting-up-external-monitoring.md
index 7862e96eb2..b7d128e601 100644
--- a/translations/ko-KR/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/ko-KR/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### About SNMP
diff --git a/translations/ko-KR/content/admin/enterprise-management/upgrade-requirements.md b/translations/ko-KR/content/admin/enterprise-management/upgrade-requirements.md
index 28c62408a1..a52a18afac 100644
--- a/translations/ko-KR/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/ko-KR/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration.
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### 다음 단계
+
 After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)."
diff --git a/translations/ko-KR/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/ko-KR/content/admin/enterprise-management/upgrading-a-cluster.md
index 31b92b012f..28275b87ac 100644
--- a/translations/ko-KR/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/ko-KR/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### Upgrading with a hotpatch
diff --git a/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index e217297405..e353d32ff5 100644
--- a/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### Preparing to upgrade
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
-
-Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
-
-Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
-
-| User licenses                  |                           vCPUs |                                  Memory |                        Attached storage | Root storage |
-|:------------------------------ | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
-| Trial, demo, or 10 light users |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
-| 10 to 3,000                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
-| 3,000 to 5000                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
-| 5,000 to 8000                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
-| 8,000 to 10,000+               | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### Taking a snapshot
 
@@ -81,7 +59,7 @@ There are two types of snapshots:
 | Hyper-V               | VM              | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | Disk            | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM              | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM              | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM              | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### Upgrading with a hotpatch
 
@@ -89,7 +67,12 @@ There are two types of snapshots:
 
 {% note %}
 
-**Note**: Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}Notes{% else %}Note{% endif %}**:
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+
+- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
 
 {% endnote %}
 
diff --git a/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md
index a38b1a0c2a..6776459ac4 100644
--- a/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/ko-KR/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index aa64bd3467..cead90d713 100644
--- a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index e8fda7b5d8..5b7a55d2f0 100644
--- a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ko-KR/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/ko-KR/content/admin/enterprise-support/about-support-for-advanced-security.md
index f30620078d..00a0c87435 100644
--- a/translations/ko-KR/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/ko-KR/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ko-KR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/ko-KR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index 9e623b4ae3..93f1ba297d 100644
--- a/translations/ko-KR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/ko-KR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 Before submitting a ticket, you should:
diff --git a/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md
index b0c448d904..d2ab876687 100644
--- a/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/ko-KR/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Creating and sharing diagnostic files
diff --git a/translations/ko-KR/content/admin/enterprise-support/reaching-github-support.md b/translations/ko-KR/content/admin/enterprise-support/reaching-github-support.md
index 7c212c89fc..5b2ba398bd 100644
--- a/translations/ko-KR/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/ko-KR/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Using automated ticketing systems
diff --git a/translations/ko-KR/content/admin/enterprise-support/submitting-a-ticket.md b/translations/ko-KR/content/admin/enterprise-support/submitting-a-ticket.md
index bcec8abff2..cdb02e3c22 100644
--- a/translations/ko-KR/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/ko-KR/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### About submitting a ticket
diff --git a/translations/ko-KR/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/ko-KR/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..341f73ba73
--- /dev/null
+++ b/translations/ko-KR/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: About using actions in your enterprise
+intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community.
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### Official actions bundled with your enterprise instance
+
+Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}.
+
+The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: <code>https://<em>HOSTNAME</em>/actions</code>.
+
+Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)."
+
+{% note %}
+
+**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)."
+
+{% endnote %}
+
+### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
+
+If users in your enterprise need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options.
+
+The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %}
+
+Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)."
diff --git a/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 782191e0e5..9afbe3c827 100644
--- a/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/ko-KR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: Backing up and restoring
 intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index dfa03f3d04..a0856b2242 100644
--- a/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/ko-KR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: Enabling automatic access to GitHub.com actions using GitHub Connect
-intro: 'To allow {% data variables.product.prodname_actions %} on your enterprise instance to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %}.'
+intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)."
+To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
 
-Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location_enterprise %}, you must connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index 8df79cb8b8..4613c86538 100644
--- a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 
-* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index f40b380820..63e755acbd 100644
--- a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 
 * To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}.
-* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 9a35874248..48959da8e5 100644
--- a/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index ef72ddb56e..6a5f4f4296 100644
--- a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: Getting started with GitHub Actions for GitHub AE
+shortTitle: Getting started with GitHub Actions
 intro: 'Learn configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index 63e7d1bdfd..409d925417 100644
--- a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,5 +1,6 @@
 ---
 title: Getting started with GitHub Actions for GitHub Enterprise Server
+shortTitle: Getting started with GitHub Actions
 intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
@@ -7,7 +8,9 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
+  - Actions
   - Enterprise
 ---
 
@@ -116,7 +119,7 @@ To run {% data variables.product.prodname_actions %} workflows, you need to add
 
 You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}.
 
-For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)."
+For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### General security hardening for {% data variables.product.prodname_actions %}
 
diff --git a/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md
index a1c649316c..1634f9088d 100644
--- a/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/ko-KR/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: High availability for GitHub Actions
 intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### Replication or redundancy of your {% data variables.product.prodname_actions %} data
diff --git a/translations/ko-KR/content/admin/github-actions/index.md b/translations/ko-KR/content/admin/github-actions/index.md
index 3e40fcb92e..e0ef0b3895 100644
--- a/translations/ko-KR/content/admin/github-actions/index.md
+++ b/translations/ko-KR/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index 70e234e0f3..7c6e7f4433 100644
--- a/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/ko-KR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: Manually syncing actions from GitHub.com
-intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your {% data variables.product.prodname_ghe_server %} instance.'
+intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance.
+However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise.
 
 ### About the `actions-sync` tool
 
-The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API. The machine doesn't need to be connected to both at the same time.
+The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time.
 
 If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands.
 
@@ -29,8 +30,8 @@ The `actions-sync` tool can only download actions from {% data variables.product
 
 ### 빌드전 요구 사양
 
-* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
-* You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
 * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
 
   {% note %}
@@ -51,7 +52,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
 
 {% note %}
 
-**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
+**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
    * `--destination-url`: The URL of the destination enterprise instance.
    * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`.
 
-     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination {% data variables.product.prodname_ghe_server %} instance. You must create the organization named `synced-actions` on your enterprise instance before running the above command.
-     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise instance. Before running the command, you must create a new organization on your instance that matches the owner name of the action. Consider using a central organization to store the synced actions on your instance, as this means you will not need to  create multiple new organizations if you sync actions from different owners.
+     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command.
+     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners.
      * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync).
-1. After the action repository is created on your enterprise instance, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
+1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 32d86f27fc..fdf8a69bd1 100644
--- a/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### About the included setup actions and the runner tool cache
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}. However, self-hosted runners without internet access  will require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
+Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}. However, self-hosted runners without internet access require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
 
 The `actions/setup-LANGUAGE` actions normally need internet access to download the required environment binaries into the runner's tool cache. Self-hosted runners without internet access can't download the binaries, so you must manually populate the tool cache on the runner.
 
diff --git a/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md b/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md
index 084447c299..31be310990 100644
--- a/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/ko-KR/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: Using a staging environment
 intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment.
diff --git a/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 3e0191625c..a0949360df 100644
--- a/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
 title: Using the latest version of the official bundled actions
-intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)."
 
-These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
+These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.
 
-Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
+### Using `actions-sync` to update the bundled actions
 
-- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
-- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
+To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
 
-These options are described in more detail in the following sections.
+### Using {% data variables.product.prodname_github_connect %} to access the latest actions
 
-### Using actions-sync to update a bundled action
+You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
 
-To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
+Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}:
 
-### Using actions from {% data variables.product.prodname_dotcom_the_website %}
+1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." 예시:
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
-
-### Using the latest version by removing the specific action's tag
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
-
-For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
-
-1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
-1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
-
-When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)."
+1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)."
+1. Configure your workflow's YAML to use `actions/checkout@v2`.
+1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/ko-KR/content/admin/guides.md b/translations/ko-KR/content/admin/guides.md
new file mode 100644
index 0000000000..8156c32da7
--- /dev/null
+++ b/translations/ko-KR/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: GitHub Enterprise guides
+shortTitle: 안내서
+intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/ko-KR/content/admin/index.md b/translations/ko-KR/content/admin/index.md
index 543eca374d..2c141854a9 100644
--- a/translations/ko-KR/content/admin/index.md
+++ b/translations/ko-KR/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: Enterprise Administrators
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
+title: GitHub Enterprise Documentation
+shortTitle: GitHub Enterprise
 intro: 'Documentation and guides for enterprise administrators, system administrators, and security specialists who {% if enterpriseServerVersions contains currentVersion %}deploy, {% endif %}configure{% if enterpriseServerVersions contains currentVersion %},{% endif %} and manage {% data variables.product.product_name %}.'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/ko-KR/content/admin/installation/index.md b/translations/ko-KR/content/admin/installation/index.md
index 514ae4464e..74e8ed3453 100644
--- a/translations/ko-KR/content/admin/installation/index.md
+++ b/translations/ko-KR/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md b/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md
index cf833f09ef..4ac39e1725 100644
--- a/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/ko-KR/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/ko-KR/content/admin/overview/about-data-residency.md b/translations/ko-KR/content/admin/overview/about-data-residency.md
index a83066177e..08df5703dc 100644
--- a/translations/ko-KR/content/admin/overview/about-data-residency.md
+++ b/translations/ko-KR/content/admin/overview/about-data-residency.md
@@ -1,8 +1,12 @@
 ---
 title: About data residency
-intro: You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.
+intro: 'You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %} You can choose the geography where you store all the customer data for {% data variables.product.product_location %}, and members of your enterprise can access {% data variables.product.product_name %} from anywhere in the world.
diff --git a/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md b/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md
index fdaf0e4c8b..68a101ab35 100644
--- a/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md
@@ -7,8 +7,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
+type: overview
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### About enterprise accounts on {% data variables.product.product_name %}
diff --git a/translations/ko-KR/content/admin/overview/about-github-ae.md b/translations/ko-KR/content/admin/overview/about-github-ae.md
index 6803cd9110..bd6e01d112 100644
--- a/translations/ko-KR/content/admin/overview/about-github-ae.md
+++ b/translations/ko-KR/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: About GitHub AE
 intro: '{% data variables.product.prodname_ghe_managed %} is a security-enhanced and compliant way to use {% data variables.product.prodname_dotcom %} in the cloud.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### About {% data variables.product.prodname_ghe_managed %}
@@ -21,7 +25,7 @@ All of your data is stored within the geographic region of your choosing. You ca
 
 ### Encryption on your terms
 
-All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
+All customer data is encrypted at rest. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
 
 ### Isolated accounts
 
diff --git a/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md
index 2290c1a532..24062f0e7c 100644
--- a/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,8 +5,10 @@ intro: '{% if currentVersion == "github-ae@latest" %}Your {% data variables.prod
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
diff --git a/translations/ko-KR/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/ko-KR/content/admin/overview/managing-billing-for-your-enterprise.md
index 98ff0564b7..4961229504 100644
--- a/translations/ko-KR/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ For example, here are the costs for users with licenses on different dates.
 | User      | License dates                                           | Counted days | Cost   |
 | --------- | ------------------------------------------------------- | ------------ | ------ |
 | @octocat  | January 1 - January 31                                  | 31           | $39    |
-| @robocat  | February 1 - February 28                                | 29           | $35.23 |
+| @robocat  | February 1 - February 28                                | 28           | $35.23 |
 | @devtocat | January 15 - January 31                                 | 17           | $21.39 |
 | @doctocat | January 1 - January 15                                  | 31           | $39    |
 | @prodocat | January 7 - January 15                                  | 25           | $31.45 |
 | @monalisa | January 1 - January 7,<br>January 15 - January 31 | 31           | $39    |
 
-Your enterprise can include one or more instances. {% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
+{% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
 
 You can see your current usage in your [Azure account portal](https://portal.azure.com).
 
diff --git a/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md b/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md
index b38d293466..41e841547b 100644
--- a/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/ko-KR/content/admin/overview/managing-your-github-enterprise-license.md
@@ -56,7 +56,7 @@ If you'd like to renew or add user licenses to {% data variables.product.prodnam
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
 3. In the left sidebar, click **Enterprise licensing**. !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-4. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.
+4. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses. {% if currentVersion ver_gt "enterprise-server@3.0" %}If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
 
 ### Automatically syncing user license usage with {% data variables.product.prodname_ghe_cloud %}
 
diff --git a/translations/ko-KR/content/admin/overview/system-overview.md b/translations/ko-KR/content/admin/overview/system-overview.md
index f80334e0f2..2a6344681a 100644
--- a/translations/ko-KR/content/admin/overview/system-overview.md
+++ b/translations/ko-KR/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### Storage architecture
diff --git a/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index cce7316823..51c82f8525 100644
--- a/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 398ccc528c..ca1bd427f3 100644
--- a/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: Getting started with GitHub Packages for your enterprise
+shortTitle: Getting started with GitHub Packages
 intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index ea9e3f5384..1e1cf5d3e5 100644
--- a/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/ko-KR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: Quickstart for configuring your MinIO storage bucket for GitHub Packages
 intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/ko-KR/content/admin/policies/about-pre-receive-hooks.md b/translations/ko-KR/content/admin/policies/about-pre-receive-hooks.md
index 11fda56c85..73ed0a1805 100644
--- a/translations/ko-KR/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/ko-KR/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 When a push occurs, each script runs in an isolated environment and can perform checks on the content of the push. The scripts will cause the push to be accepted if the exit status is 0, or rejected if the exit status is non-zero.
diff --git a/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-environment.md
index 2e641c92f7..1bd126152e 100644
--- a/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 A pre-receive environment for {% data variables.product.prodname_ghe_server %} is a Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot) environment. Because pre-receive hooks execute on every push event, they should be fast and lightweight. The environment needed for such checks will typically be minimal.
diff --git a/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md
index 63a007f21b..b0e79ddd71 100644
--- a/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/ko-KR/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 You can see examples of pre-receive hooks for {% data variables.product.prodname_ghe_server %} in the [`github/platform-samples` repository](https://github.com/github/platform-samples/tree/master/pre-receive-hooks).
diff --git a/translations/ko-KR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/ko-KR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index 381b03d1bd..afd8481d88 100644
--- a/translations/ko-KR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/ko-KR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,6 +5,13 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### About {% data variables.product.prodname_GH_advanced_security %}
diff --git a/translations/ko-KR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ko-KR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 15f6a28ef4..3a996c08b5 100644
--- a/translations/ko-KR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ko-KR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Configuring the default visibility of new repositories in your enterprise
diff --git a/translations/ko-KR/content/admin/policies/index.md b/translations/ko-KR/content/admin/policies/index.md
index cdc0668700..d5d9bedc36 100644
--- a/translations/ko-KR/content/admin/policies/index.md
+++ b/translations/ko-KR/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/ko-KR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/ko-KR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 4f55f53348..340f5a015d 100644
--- a/translations/ko-KR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/ko-KR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### Creating pre-receive hooks
diff --git a/translations/ko-KR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/ko-KR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..03b083ea40
--- /dev/null
+++ b/translations/ko-KR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About email restrictions for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restricting email notifications for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/ko-KR/content/admin/release-notes.md b/translations/ko-KR/content/admin/release-notes.md
index 1af66701b5..7dfc63a71c 100644
--- a/translations/ko-KR/content/admin/release-notes.md
+++ b/translations/ko-KR/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/ko-KR/content/admin/user-management/about-migrations.md b/translations/ko-KR/content/admin/user-management/about-migrations.md
index 0ca940949b..67f510520c 100644
--- a/translations/ko-KR/content/admin/user-management/about-migrations.md
+++ b/translations/ko-KR/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Types of migrations
diff --git a/translations/ko-KR/content/admin/user-management/adding-people-to-teams.md b/translations/ko-KR/content/admin/user-management/adding-people-to-teams.md
index 6ddc24d377..522d39f391 100644
--- a/translations/ko-KR/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/ko-KR/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: 'Once a team has been created, organization admins can add users from {% data variables.product.product_location %} to the team and determine which repositories they have access to.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization).
diff --git a/translations/ko-KR/content/admin/user-management/audit-logging.md b/translations/ko-KR/content/admin/user-management/audit-logging.md
index cb3fa1d9f8..b54a5b15c2 100644
--- a/translations/ko-KR/content/admin/user-management/audit-logging.md
+++ b/translations/ko-KR/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 For a full list, see "[Audited actions](/admin/user-management/audited-actions)." For more information on finding a particular action, see "[Searching the audit log](/admin/user-management/searching-the-audit-log)."
diff --git a/translations/ko-KR/content/admin/user-management/audited-actions.md b/translations/ko-KR/content/admin/user-management/audited-actions.md
index 8dc67643c5..67e2234fed 100644
--- a/translations/ko-KR/content/admin/user-management/audited-actions.md
+++ b/translations/ko-KR/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### Authentication
diff --git a/translations/ko-KR/content/admin/user-management/auditing-ssh-keys.md b/translations/ko-KR/content/admin/user-management/auditing-ssh-keys.md
index b53e4577ea..f3156f9022 100644
--- a/translations/ko-KR/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/ko-KR/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 Once initiated, the audit disables all existing SSH keys and forces users to approve or reject them before they're able to clone, pull, or push to any repositories. An audit is useful in situations where an employee or contractor leaves the company and you need to ensure that all keys are verified.
diff --git a/translations/ko-KR/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/ko-KR/content/admin/user-management/auditing-users-across-your-enterprise.md
index 25f46b42d4..cd1d32ef50 100644
--- a/translations/ko-KR/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### Accessing the audit log
diff --git a/translations/ko-KR/content/admin/user-management/best-practices-for-user-security.md b/translations/ko-KR/content/admin/user-management/best-practices-for-user-security.md
index 85382758ff..e814bc4358 100644
--- a/translations/ko-KR/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/ko-KR/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ko-KR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/ko-KR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index f2b7bd328d..8e1e6eb406 100644
--- a/translations/ko-KR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### About {% data variables.large_files.product_name_long %}
diff --git a/translations/ko-KR/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/ko-KR/content/admin/user-management/configuring-visibility-for-organization-membership.md
index 99f5fde542..c12145465b 100644
--- a/translations/ko-KR/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/ko-KR/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ko-KR/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/ko-KR/content/admin/user-management/continuous-integration-using-jenkins.md
index 2e526bd5e7..f8ce65b131 100644
--- a/translations/ko-KR/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/ko-KR/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/user-management/creating-teams.md b/translations/ko-KR/content/admin/user-management/creating-teams.md
index 74f76723fa..e2f5af45f7 100644
--- a/translations/ko-KR/content/admin/user-management/creating-teams.md
+++ b/translations/ko-KR/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Teams are central to many of {% data variables.product.prodname_dotcom %}'s collaborative features, such as team @mentions to notify appropriate parties that you'd like to request their input or attention. For more information, see "[Permission levels for an organization repository](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)".
diff --git a/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index b81f86865b..582fed951f 100644
--- a/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: Customizing user messages for your enterprise
+shortTitle: Customizing user messages
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: 'You can create custom messages that users will see on {% data variables.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### About user messages
diff --git a/translations/ko-KR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/ko-KR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index 4562fc05e9..8e54fbd585 100644
--- a/translations/ko-KR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: You can prevent people from using Git over SSH for certain or all reposit
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### Disabling Git SSH access to a specific repository
diff --git a/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md
index b1463aa91b..b3c850efce 100644
--- a/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the source organization on {% data variables.product.prodname_dotcom %}
diff --git a/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index aef125ce7d..f0b975c6e6 100644
--- a/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the {% data variables.product.prodname_ghe_server %} source instance
diff --git a/translations/ko-KR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/ko-KR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 7394f22dba..2da648f012 100644
--- a/translations/ko-KR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/ko-KR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Importing projects from Mercurial
diff --git a/translations/ko-KR/content/admin/user-management/log-forwarding.md b/translations/ko-KR/content/admin/user-management/log-forwarding.md
index f07d53847f..d508a91b35 100644
--- a/translations/ko-KR/content/admin/user-management/log-forwarding.md
+++ b/translations/ko-KR/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Any log collection system that supports syslog-style log streams is supported (e.g., [Logstash](http://logstash.net/) and [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
diff --git a/translations/ko-KR/content/admin/user-management/managing-dormant-users.md b/translations/ko-KR/content/admin/user-management/managing-dormant-users.md
index 03e776d889..ac9bc21f66 100644
--- a/translations/ko-KR/content/admin/user-management/managing-dormant-users.md
+++ b/translations/ko-KR/content/admin/user-management/managing-dormant-users.md
@@ -9,8 +9,11 @@ intro: 'A user account is considered to be dormant if it has not been active for
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 "Activity" includes, but is not limited to:
diff --git a/translations/ko-KR/content/admin/user-management/managing-global-webhooks.md b/translations/ko-KR/content/admin/user-management/managing-global-webhooks.md
index 64ee497612..7f6e78cb30 100644
--- a/translations/ko-KR/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/ko-KR/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### About global webhooks
diff --git a/translations/ko-KR/content/admin/user-management/managing-projects-using-jira.md b/translations/ko-KR/content/admin/user-management/managing-projects-using-jira.md
index e953a14d21..c992dfa998 100644
--- a/translations/ko-KR/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/ko-KR/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: Managing projects using JIRA
-intro: 'You can integrate JIRA with {% data variables.product.prodname_enterprise %} for project management.'
+title: Managing projects using Jira
+intro: 'You can integrate Jira with {% data variables.product.prodname_enterprise %} for project management.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### Connecting JIRA to a {% data variables.product.prodname_enterprise %} organization
+### Connecting Jira to a {% data variables.product.prodname_enterprise %} organization
 
-1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login.
-1. In the upper right corner of any page, click the account settings (gear) icon.
-1. In the left sidebar, click the name of your organization.
-1. In the left sidebar, click **Applications**.
-1. In the upper right corner of the **Organization applications** box, click **Register new application**.
-1. Fill in the application settings:
-    - In the **Application name** field, type "JIRA".
-    - In the **Homepage URL** field, type the full URL of your JIRA instance.
-    - In the **Authorization callback URL** field, type the full URL of your JIRA instance.
-1. Click **Register application**.
-1. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your JIRA instance.
+1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
+2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira.
 
-### JIRA instance configuration
+  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. On your JIRA instance, log into an account with administrative access.
-1. At the top of the page, click the settings (gear) icon.
-1. In the settings dropdown, choose **Add-ons**.
-1. In the left sidebar, under **Source control**, click **DVCS accounts**.
-1. Click **Link Bitbucket or GitHub account**.
-1. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings:
-    - From the **Host** dropdown menu, choose **GitHub Enterprise**.
+3. Click on the **Edit _organization name_ settings** link.
+
+  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
+
+  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Click on the **Register new application** button.
+
+  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. Fill in the application settings:
+    - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance.
+    - In the **Homepage URL** field, type the full URL of your Jira instance.
+    - In the **Authorization callback URL** field, type the full URL of your Jira instance.
+7. Click **Register application**.
+8. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your Jira instance.
+
+### Jira instance configuration
+
+1. On your Jira instance, log into an account with administrative access.
+2. At the top of the page, click the settings (gear) icon and choose **Applications**.
+
+  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
+
+  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
+
+  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings:
+    - From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**.
     - In the **Team or User Account** field, type the name of your {% data variables.product.prodname_enterprise %} organization or personal account.
     - In the **OAuth Key** field, type the Client ID of your {% data variables.product.prodname_enterprise %} developer application.
     - In the **OAuth Secret** field, type the Client Secret for your {% data variables.product.prodname_enterprise %} developer application.
-    - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, unselect **Auto Link New Repositories**.
-    - If you don't want to enable smart commits, unselect **Enable Smart Commits**.
+    - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, deselect **Auto Link New Repositories**.
+    - If you don't want to enable smart commits, deselect **Enable Smart Commits**.
     - Click **Add**.
-1. Review the permissions you are granting to your {% data variables.product.prodname_enterprise %} account and click **Authorize application**.
-1. If necessary, type your password to continue.
+6. Review the permissions you are granting to your {% data variables.product.prodname_enterprise %} account and click **Authorize application**.
+7. If necessary, type your password to continue.
diff --git a/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md
index c7c1a2ca62..847918219b 100644
--- a/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Applying the imported data on {% data variables.product.prodname_ghe_server %}
diff --git a/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md
index de51d14b7a..4ba612d682 100644
--- a/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/ko-KR/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### About internal repositories
@@ -34,6 +38,12 @@ If you don't have private mode enabled, the migration script will have no effect
 ### Running the migration
 
 1. Connect to the administrative shell. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)."
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. Run the migration command.
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. Navigate to the `/data/github/current` directory.
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ If you don't have private mode enabled, the migration script will have no effect
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 Log output will appear in the terminal and `/tmp/convert_public_ghes_repos_to_internal.log`.
 
diff --git a/translations/ko-KR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/ko-KR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index 875847ad67..d4a65aa90b 100644
--- a/translations/ko-KR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/ko-KR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 Usually, if someone deletes a repository, it will be available on disk for 90 days and can be restored via the site admin dashboard. After 90 days the repository is purged and deleted forever. If you place a legal hold on a user or organization, repositories they own are available for restore indefinitely.
diff --git a/translations/ko-KR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/ko-KR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index df07f7fb6b..09c90cd84b 100644
--- a/translations/ko-KR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/ko-KR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
diff --git a/translations/ko-KR/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/ko-KR/content/admin/user-management/preventing-users-from-creating-organizations.md
index ac2412dffc..733793d89b 100644
--- a/translations/ko-KR/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/ko-KR/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: You can prevent users from creating organizations in your enterprise.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/ko-KR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/ko-KR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index a1dd6ec636..c6ffc7095c 100644
--- a/translations/ko-KR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/ko-KR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: 'Site administrators can promote any normal user account to a site administrator, as well as demote other site administrators to regular users.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/ko-KR/content/admin/user-management/rebuilding-contributions-data.md b/translations/ko-KR/content/admin/user-management/rebuilding-contributions-data.md
index 5fb410c7c0..9728193fdc 100644
--- a/translations/ko-KR/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/ko-KR/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 Whenever a commit is pushed to {% data variables.product.prodname_enterprise %}, it is linked to a user account if they are both associated with the same email address. However, existing commits are *not* retroactively linked when a user registers a new email address or creates a new account.
diff --git a/translations/ko-KR/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/ko-KR/content/admin/user-management/removing-users-from-teams-and-organizations.md
index 43dc19d077..06605e9e8d 100644
--- a/translations/ko-KR/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/ko-KR/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Only owners or team admins can remove organization members. When a user is removed from a team or organization, their issues, pull requests, and comments in the organization's repositories remain intact and are still attributed to the user.
diff --git a/translations/ko-KR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/ko-KR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index 5da4357a63..ba6c3e94a7 100644
--- a/translations/ko-KR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/ko-KR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.product.product_location %}. Organization administrators can require members to have two-factor authentication enabled.
diff --git a/translations/ko-KR/content/admin/user-management/searching-the-audit-log.md b/translations/ko-KR/content/admin/user-management/searching-the-audit-log.md
index 7b60f45788..1905d8b78d 100644
--- a/translations/ko-KR/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/ko-KR/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### Search query syntax
diff --git a/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md
index 88932cb85a..85a3836c7a 100644
--- a/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/ko-KR/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'If a user leaves or moves to a different part of the company, you should remove or modify their ability to access {% data variables.product.product_location %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 If employees leave the company, you can suspend their {% data variables.product.prodname_ghe_server %} accounts to open up user licenses in your {% data variables.product.prodname_enterprise %} license while preserving the issues, comments, repositories, gists, and other data they created. Suspended users cannot sign into your instance, nor can they push or pull code.
diff --git a/translations/ko-KR/content/admin/user-management/viewing-push-logs.md b/translations/ko-KR/content/admin/user-management/viewing-push-logs.md
index b766ad3b56..43bfa6e547 100644
--- a/translations/ko-KR/content/admin/user-management/viewing-push-logs.md
+++ b/translations/ko-KR/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 Push log entries show:
diff --git a/translations/ko-KR/content/code-security/getting-started/about-securing-your-repository.md b/translations/ko-KR/content/code-security/getting-started/about-securing-your-repository.md
index 18ab31fdb0..545aaf972a 100644
--- a/translations/ko-KR/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/ko-KR/content/code-security/getting-started/about-securing-your-repository.md
@@ -22,11 +22,13 @@ The first step to securing a repository is to set up who can see and modify your
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 #### Available for all repositories
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **Security policy**
 
-  Make it easy for people to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)."
+  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 %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **Security advisories**
 
   Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage them to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
diff --git a/translations/ko-KR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/ko-KR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..9cd3ac3f7e
--- /dev/null
+++ b/translations/ko-KR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+You can create a default security policy for your organization or user account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+{% endif %}
+
+{% tip %}
+
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about {% data variables.product.prodname_security_advisories %}, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+### Adding a security policy to your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**. ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**. ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### 더 읽을거리
+
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/ko-KR/content/code-security/getting-started/index.md b/translations/ko-KR/content/code-security/getting-started/index.md
index 78a1a2ed78..df45c60bb4 100644
--- a/translations/ko-KR/content/code-security/getting-started/index.md
+++ b/translations/ko-KR/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### Table of Contents
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index c89e4c2f39..d188ca9461 100644
--- a/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -27,13 +27,19 @@ topics:
 
 ### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories
 
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization.
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. You may need to enable {% data variables.product.prodname_GH_advanced_security %} to activate the button for "{% data variables.product.prodname_secret_scanning_caps %}". To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% if currentVersion == "free-pro-team@latest" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
 7. To the right of "{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
@@ -66,7 +72,7 @@ You can use a *secret_scanning.yml* file to exclude directories from {% data var
 
     {% endnote %}
 
-You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)."
+You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)."
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/ko-KR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index c60b3e7cfb..b8dfbbf39e 100644
--- a/translations/ko-KR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/ko-KR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -14,7 +14,7 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-### Managing alerts
+### Managing {% data variables.product.prodname_secret_scanning %} alerts
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
@@ -49,3 +49,11 @@ Once a secret has been committed to a repository, you should consider the secret
 
 - For a compromised {% data variables.product.prodname_dotcom %} personal access token, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)."
 - For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.prodname_dotcom %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
diff --git a/translations/ko-KR/content/code-security/secure-coding/about-code-scanning.md b/translations/ko-KR/content/code-security/secure-coding/about-code-scanning.md
index 0f2096b08c..2b2f926c33 100644
--- a/translations/ko-KR/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/ko-KR/content/code-security/secure-coding/about-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -36,7 +38,7 @@ You can use {% data variables.product.prodname_code_scanning %} with {% data var
 
 {% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
 
@@ -48,17 +50,14 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 {% endif %}
 
-### About third-party code scanning tools
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### About third-party {% data variables.product.prodname_code_scanning %} tools
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+You can run third-party analysis tools within {% data variables.product.product_name %} using actions or within an external CI system. For more information, see "[Setting up code scanning for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
 
 ### 더 읽을거리
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/translations/ko-KR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..3a04b180a9
--- /dev/null
+++ b/translations/ko-KR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using actions. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case.
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Codebases with a compiled language that can be built with a single command or by running a single script.
+
+For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to:
+- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis.
+- Analyze more than one language in a repository.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
diff --git a/translations/ko-KR/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/ko-KR/content/code-security/secure-coding/about-integration-with-code-scanning.md
index 7cc6fd8b54..f3ce9567ef 100644
--- a/translations/ko-KR/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/ko-KR/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/ko-KR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/ko-KR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index f059efe9c0..5d12ce283b 100644
--- a/translations/ko-KR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/ko-KR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ko-KR/content/code-security/secure-coding/configuring-code-scanning.md b/translations/ko-KR/content/code-security/secure-coding/configuring-code-scanning.md
index b123758a6e..85b4c939f1 100644
--- a/translations/ko-KR/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/ko-KR/content/code-security/secure-coding/configuring-code-scanning.md
@@ -14,14 +14,21 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
 ### About {% data variables.product.prodname_code_scanning %} configuration
 
-You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+{%- else %}
+"[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}.
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
 
 Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
 
@@ -143,7 +150,7 @@ jobs:
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
@@ -184,34 +191,66 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. 예시:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)."
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
 ### Running additional queries
 
 {% data reusables.code-scanning.run-additional-queries %}
@@ -308,6 +347,7 @@ paths-ignore:
 **Note**:
 
 * The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
 * `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
diff --git a/translations/ko-KR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/ko-KR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..8a21dcc0a0
--- /dev/null
+++ b/translations/ko-KR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,203 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configuring CodeQL runner
+intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows.
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively.
+
+To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
+
+### Scanning pull requests
+
+Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code.
+
+To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch.
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`.
+
+{% endnote %}
+
+### Overriding automatic language detection
+
+The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### Running additional queries
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
+
+If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file. If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to <nobr>`--queries`</nobr> with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+
+In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### Using a custom configuration file
+
+Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file.
+
+The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
+
+Use the `--config-file` flag of the `init` command to specify the configuration file. The value of <nobr>`--config-file`</nobr> is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### Example configuration files
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+
+For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+
+For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first.
+
+The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command.
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)."
+
+### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+
+By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
+
+Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository.
+- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+### {% data variables.product.prodname_codeql_runner %} command reference
+
+The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags.
+
+#### `init`
+
+Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
+
+| Flag                             | 필수 사항 | Input value                                                                                                                                                                         |
+| -------------------------------- |:-----:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                   |   ✓   | Name of the repository to initialize.                                                                                                                                               |
+| `--github-url`                   |   ✓   | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                   |
+| `--github-auth`                  |   ✓   | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                               |
+| `--languages`                    |       | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. |
+| `--queries`                      |       | Comma-separated list of additional queries to run, in addition to the default suite of security queries.                                                                            |
+| `--config-file`                  |       | Path to custom configuration file.                                                                                                                                                  |
+| `--codeql-path`                  |       | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy.   |
+| `--temp-dir`                     |       | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                       |
+| `--tools-dir`                    |       | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory.                    |
+| <nobr>`--checkout-path`</nobr> |       | The path to the checkout of your repository. The default is the current working directory.                                                                                          |
+| `--debug`                        |       | None. Prints more verbose output.                                                                                                                                                   |
+| `-h`, `--help`                   |       | None. Displays help for the command.                                                                                                                                                |
+
+#### `autobuild`
+
+Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps.
+
+| Flag                        | 필수 사항 | Input value                                                                                                                                    |
+| --------------------------- |:-----:| ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--language`                |       | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. |
+| <nobr>`--temp-dir`</nobr> |       | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                  |
+| `--debug`                   |       | None. Prints more verbose output.                                                                                                              |
+| `-h`, `--help`              |       | None. Displays help for the command.                                                                                                           |
+
+#### `analyze`
+
+Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}.
+
+| Flag                               | 필수 사항 | Input value                                                                                                                                                                                                                                                                                                                         |
+| ---------------------------------- |:-----:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     |   ✓   | Name of the repository to analyze.                                                                                                                                                                                                                                                                                                  |
+| `--commit`                         |   ✓   | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                                                                                                                     |
+| `--ref`                            |   ✓   | Name of the reference to analyze, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`.                                                                                              |
+| `--github-url`                     |   ✓   | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                                                                                                                   |
+| `--github-auth`                    |   ✓   | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                                                                                                               |
+| <nobr>`--checkout-path`</nobr>   |       | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                                                                                                          |
+| `--no-upload`                      |       | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}.                                                                                                                                                                                      |
+| `--output-dir`                     |       | Directory where the output SARIF files are stored. The default is in the directory of temporary files.                                                                                                                                                                                                                              |
+| `--ram`                            |       | Amount of memory to use when running queries. The default is to use all available memory.                                                                                                                                                                                                                                           |
+| <nobr>`--no-add-snippets`</nobr> |       | None. Excludes code snippets from the SARIF output. |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |       | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |       | Number of threads to use when running queries. The default is to use all available cores.                                                                                                                                                                                                                                           |
+| `--temp-dir`                       |       | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                                                                                                                                                                       |
+| `--debug`                          |       | None. Prints more verbose output.                                                                                                                                                                                                                                                                                                   |
+| `-h`, `--help`                     |       | None. Displays help for the command.                                                                                                                                                                                                                                                                                                |
+
+#### `업로드`
+
+Uploads SARIF files to {% data variables.product.product_name %}.
+
+{% note %}
+
+**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools.
+
+{% endnote %}
+
+| Flag                             | 필수 사항 | Input value                                                                                                                                                                                                                                   |
+| -------------------------------- |:-----:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   |   ✓   | SARIF file to upload, or a directory containing multiple SARIF files.                                                                                                                                                                         |
+| `--repository`                   |   ✓   | Name of the repository that was analyzed.                                                                                                                                                                                                     |
+| `--commit`                       |   ✓   | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                        |
+| `--ref`                          |   ✓   | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
+| `--github-url`                   |   ✓   | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                             |
+| `--github-auth`                  |   ✓   | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                         |
+| <nobr>`--checkout-path`</nobr> |       | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                    |
+| `--debug`                        |       | None. Prints more verbose output.                                                                                                                                                                                                             |
+| `-h`, `--help`                   |       | None. Displays help for the command.                                                                                                                                                                                                          |
diff --git a/translations/ko-KR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ko-KR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index d3a292b276..d1ebef944b 100644
--- a/translations/ko-KR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ko-KR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/ko-KR/content/code-security/secure-coding/index.md b/translations/ko-KR/content/code-security/secure-coding/index.md
index 9a4f7ebd77..4d14b380ca 100644
--- a/translations/ko-KR/content/code-security/secure-coding/index.md
+++ b/translations/ko-KR/content/code-security/secure-coding/index.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### Table of Contents
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% link_in_list /running-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-the-codeql-action-for-compiled-languages %}
-    {% link_in_list /managing-alerts-from-code-scanning %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/ko-KR/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/ko-KR/content/code-security/secure-coding/integrating-with-code-scanning.md
index 88ab7921b4..cde681b9f8 100644
--- a/translations/ko-KR/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/ko-KR/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index 0c7a58146b..0aba071686 100644
--- a/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
 title: Managing code scanning alerts for your repository
 shortTitle: Managing alerts
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About alerts from {% data variables.product.prodname_code_scanning %}
@@ -60,7 +62,7 @@ You need write permission to view a summary of all the alerts for a repository o
 
 Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
 
 Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
 
@@ -70,14 +72,6 @@ Alerts may be fixed in one branch but not in another. You can use the "Branch" d
 ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### Closing an alert
-
-Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### Dismissing or deleting alerts
 
 There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
@@ -101,20 +95,9 @@ When you delete an alert:
 
 To dismiss or delete alerts:
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. Select the **Close** drop-down menu and click a reason for closing the alert.    
-   ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
 
    ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,8 +128,6 @@ To dismiss or delete alerts:
 
 If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
 
-{% endif %}
-
 ### 더 읽을거리
 
 - "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/ko-KR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/ko-KR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..dfc229b2af
--- /dev/null
+++ b/translations/ko-KR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Running CodeQL CLI in your CI system
+shortTitle: Running CodeQL CLI
+intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About the {% data variables.product.prodname_codeql_cli %}
+
+You can use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_codeql_runner %} in your CI system, or {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% note %}
+
+**Note:** {% if currentVersion == "free-pro-team@latest" %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% endnote %}
+
+### Downloading the {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. 예시:
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      필수 사항
+    </th>
+    
+    <th>
+      사용법
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      선택 사항. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      필수 사항
+    </th>
+    
+    <th>
+      사용법
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. For more information, see "<a href="/code-security/secure-coding/sarif-support-for-code-scanning">SARIF support for {% data variables.product.prodname_code_scanning %}</a>."
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      선택 사항. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      선택 사항. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      필수 사항
+    </th>
+    
+    <th>
+      사용법
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. For more information, see "<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">Managing security and analysis settings for your repository</a>."
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      선택 사항. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### 더 읽을거리
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/ko-KR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/ko-KR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index 9238263909..8b8de1d3d3 100644
--- a/translations/ko-KR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ko-KR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -13,13 +13,19 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} with a containerized build
 
 If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.
 
-You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% else %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% endif %}
 
 ### Dependencies
 
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/ko-KR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/ko-KR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..495d68c51c
--- /dev/null
+++ b/translations/ko-KR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Running CodeQL runner in your CI system
+shortTitle: Running CodeQL runner
+intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About the {% data variables.product.prodname_codeql_runner %}
+
+The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. The runner is more complex and less forgiving to set up than the CLI, and is recommended only if you need its capability to analyze multiple compiled languages with a single build, or to integrate with complex build processes. For more information, see "[About CodeQL code scanning in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
+
+{% note %}
+
+**참고:**
+{% if currentVersion == "free-pro-team@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{% else %}
+* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
+{% endif %}
+{% endnote %}
+
+### Downloading the {% data variables.product.prodname_codeql_runner %}
+
+You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+
+On Linux:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+macOS 의 경우 :
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
+
+### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system
+
+Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+In addition to this, each CI server also needs:
+
+- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+
+The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+
+1. Allow the CI servers access to https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
+
+### Calling the {% data variables.product.prodname_codeql_runner %}
+
+You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+
+1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
+1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
+
+For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
+
+You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
+
+To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### Basic example
+
+This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
+
+In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
+
+1. Check out the repository to analyze.
+1. Move into the directory where the repository is checked out.
+1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### Compiled language example
+
+This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
+
+1. Check out the repository to analyze.
+1. Move into the directory where the repository is checked out.
+1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place.
+
+{% endnote %}
+
+### 더 읽을거리
+
+- "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
diff --git a/translations/ko-KR/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/ko-KR/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index e85214d015..7542f2449a 100644
--- a/translations/ko-KR/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/ko-KR/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: SARIF support for code scanning
 shortTitle: SARIF support
 intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for {% data variables.product.prodname_code_scanning %}. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About SARIF support
@@ -22,7 +25,15 @@ SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https:
 
 To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
 
 {% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
@@ -122,6 +133,45 @@ A location within a programming artifact, such as a file in the repository or a
 | `region.endLine`       | **Required.** The line number of the last character in the region.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | `region.endColumn`     | **Required.** The column number of the character following the end of the region.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| 이름   | 설명                                                                                                                                                                                                                                    |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id` | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | 카테고리              | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
+
 ### SARIF output file examples
 
 These example SARIF output files show supported properties and example values.
@@ -130,7 +180,6 @@ These example SARIF output files show supported properties and example values.
 
 This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties or don't include values, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}.
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ This SARIF output file has example values to show the minimum required propertie
 
 This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}.
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ This SARIF output file has example values to show all supported SARIF properties
   ]
 }
 ```
+{% endif %}
diff --git a/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
index 05674e8f2b..fda66f6f32 100644
--- a/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
@@ -17,6 +17,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/ko-KR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ko-KR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index ef961fb031..a6749cecda 100644
--- a/translations/ko-KR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ko-KR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -14,13 +14,15 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} results on pull requests
 
 In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or dismiss all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
 
 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -44,18 +46,10 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
 
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Fixing an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 ### Dismissing an alert on your pull request
 
 An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
@@ -67,5 +61,3 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/ko-KR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/ko-KR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..0cdbfc9d1d
--- /dev/null
+++ b/translations/ko-KR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshooting CodeQL runner
+intro: 'If you''re having problems with the {% data variables.product.prodname_codeql_runner %}, you can troubleshoot by using these tips.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### The `init` command takes too long
+
+Before the {% data variables.product.prodname_codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries.
+
+When you use the {% data variables.product.prodname_codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes. The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.product.prodname_codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again.
+
+To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command.
+
+### No code found during the build
+
+If the `analyze` command for the {% data variables.product.prodname_codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure.
+
+1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)."
+
+1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the build process. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command.
+   - On macOS and Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - On Windows, using the Command shell (`cmd`) or a batch file (`.bat`):
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - On Windows, using PowerShell:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead.
+
+   {% note %}
+
+   **Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different.
+
+   {% endnote %}
+
+1. You're analyzing a compiled language on macOS without using the `autobuild` command and you run the build steps yourself after the `init` step. If SIP (System Integrity Protection) is enabled, which is the default on recent versions of OSX, analysis might fail. To fix this, prefix the build command with the `$CODEQL_RUNNER` environment variable. For example, if your build command is `cmd arg1 arg2`, you should run `$CODEQL_RUNNER cmd arg1 arg2`.
+
+1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.product.prodname_codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
diff --git a/translations/ko-KR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/ko-KR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
index 9b6fe97058..ceebbed87e 100644
--- a/translations/ko-KR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
+++ b/translations/ko-KR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -33,19 +35,22 @@ If an automatic build of code for a compiled language within your project fails,
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
         matrix:
           language: ['csharp', 'cpp', 'javascript']
 
+      steps:
       ...
-
-      - name: Initialize {% data variables.product.prodname_codeql %}
-        uses: github/codeql-action/init@v1
-        with:
-          languages: {% raw %}${{ matrix.language }}{% endraw %}
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: github/codeql-action/init@v1
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
   For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
@@ -150,29 +155,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/ko-KR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/ko-KR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index 08feb90947..14dbbb302f 100644
--- a/translations/ko-KR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/ko-KR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -24,18 +26,19 @@ topics:
 
 You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
 
 - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
-- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
-- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)").
+- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").
 - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
 
 ### Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
 
-To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a  workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a  workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
 Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameter you'll use is `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository. For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/HEAD/upload-sarif).
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Example workflow that runs the ESLint analysis tool
@@ -87,7 +92,7 @@ This example workflow runs anytime commits are pushed to the repository. The act
 
 The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### 더 읽을거리
 
 - "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
+- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
 - "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
diff --git a/translations/ko-KR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/ko-KR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index 1610e347ef..1f2e2e0164 100644
--- a/translations/ko-KR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/ko-KR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/ko-KR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/ko-KR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 613e9f91ce..7483e0d587 100644
--- a/translations/ko-KR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/ko-KR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -43,7 +43,7 @@ Publishing the details of a security vulnerability doesn't make maintainers look
 
 The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
 
- If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
+ If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
 
  If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
 
@@ -55,7 +55,7 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
 
- If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
+ If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
 
  As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
diff --git a/translations/ko-KR/content/code-security/security-advisories/index.md b/translations/ko-KR/content/code-security/security-advisories/index.md
index 0b43542ea5..f303ea9b4e 100644
--- a/translations/ko-KR/content/code-security/security-advisories/index.md
+++ b/translations/ko-KR/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### Table of Contents
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
index a98a7225e1..fab6c1d905 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
 title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
+intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository.'
 redirect_from:
   - /articles/about-security-alerts-for-vulnerable-dependencies
   - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
@@ -12,6 +12,7 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
 
 ### About vulnerable dependencies
@@ -22,12 +23,12 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 ### Detection of vulnerable dependencies
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %}
+- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)."
 
 {% data reusables.repositories.dependency-review %}
 
@@ -39,11 +40,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
 ### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
-{% else %}
-### Security alerts for vulnerable dependencies
-{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
@@ -56,41 +53,28 @@ For information about permission requirements for actions related to {% data var
 {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
-{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
-{% endif %}
-
 {% warning %}
 
 **Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Access to {% data variables.product.prodname_dependabot %} alerts
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
-{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
-{% endif %}
+You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### 더 읽을거리
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index 0b93fd7956..7b8fa4e1a3 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -35,6 +35,7 @@ You specify how often to check each ecosystem for new versions in the configurat
 If you've enabled security updates, you'll sometimes see extra pull requests for security updates. These are triggered by a {% data variables.product.prodname_dependabot %} alert for a dependency on your default branch. {% data variables.product.prodname_dependabot %} automatically raises a pull request to update the vulnerable dependency.
 
 ### Supported repositories and ecosystems
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)."
 
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md
index 97dec37d5f..5bb742ab0c 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md
@@ -10,6 +10,7 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
 <!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
 
 ### Dependency graph availability
@@ -60,10 +61,6 @@ You can use the dependency graph to:
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
-
-{% endif %}
-
 When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
 
 ### Supported package ecosystems
@@ -90,6 +87,6 @@ The recommended formats explicitly define which versions are used for all direct
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
 - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
+- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}
 - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index f686bd730e..6ab483b260 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -164,7 +164,7 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Use the `allow` option to customize which dependencies are updated. This has no impact on security updates for vulnerable dependencies. You can use the following options:
+Use the `allow` option to customize which dependencies are updated. This applies to both version and security updates. You can use the following options:
 
 - `dependency-name`—use to allow updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId`, for example: `org.kohsuke:github-api`.
 - `dependency-type`—use to allow updates for dependencies of specific types.
@@ -445,12 +445,12 @@ updates:
 
 #### `rebase-strategy`
 
-By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects conflicts. Use `rebase-strategy` to disable this behavior.
+By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. Use `rebase-strategy` to disable this behavior.
 
 Available rebase strategies
 
 - `disabled` to disable automatic rebasing.
-- `auto` to use the default behavior and rebase open pull requests when conflicts are detected.
+- `auto` to use the default behavior and rebase open pull requests when changes are detected.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -473,11 +473,11 @@ To allow {% data variables.product.prodname_dependabot %} to access a private pa
 
 To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution).
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -493,11 +493,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -716,7 +716,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
@@ -730,6 +730,7 @@ You use the following options to specify access settings. Registry settings must
 | `url`                                                                                                  | The URL to use to access the dependencies in this registry. The protocol is optional. If not specified, `https://` is assumed. {% data variables.product.prodname_dependabot %} adds or ignores trailing slashes as required.                                                   |
 | `사용자 이름`                                                                                               | The username that {% data variables.product.prodname_dependabot %} uses to access the registry.                                                                                                                                                                                 |
 | `암호`                                                                                                   | A reference to a {% data variables.product.prodname_dependabot %} secret containing the password for the specified user. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)." |
+| `키`                                                                                                    | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access key for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."     |
 | `토큰`                                                                                                   | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access token for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."   |
 | `replaces-base`                                                                                        | For registries with `type: python-index`, if the boolean value is `true`, pip resolves dependencies by using the specified URL rather than the base URL of the Python Package Index (by default `https://pypi.org/simple`).                                                     |
 
@@ -766,6 +767,19 @@ registries:
 ```
 {% endraw %}
 
+The `docker-registry` type can also be used to pull from Amazon ECR using static AWS credentials.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 The `git` type supports username and password.
@@ -781,6 +795,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+The `hex-organization` type supports organization and key.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 The `maven-repository` type supports username and password, or token.
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index f958fa0829..ded3fc5ba6 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
 title: Configuring notifications for vulnerable dependencies
 shortTitle: Configuring notifications
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+intro: 'Optimize how you receive notifications about {% data variables.product.prodname_dependabot %} alerts.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
@@ -11,48 +11,41 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
+
 ### About notifications for vulnerable dependencies
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
+When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %}
+By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.{% endif %}
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
 
 You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
-{% else %}
-  ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png)
-{% endif %}
 
 {% note %}
 
-**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
 
 ### How to reduce the noise from notifications for vulnerable dependencies
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index 02fd2a67b0..8e26f2f55a 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -18,7 +18,7 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c
 
 {% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)."
 
-{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
+{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
 
 ### Enabling {% data variables.product.prodname_dependabot_version_updates %}
 
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index fd707e9495..beb4efb700 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -15,6 +15,8 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
@@ -50,19 +52,6 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
-
-![의존성 그래프](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view.
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### Dependents view
 
@@ -113,8 +102,8 @@ If a manifest or lock file is not processed, its dependencies are omitted from t
 
 ### 더 읽을거리
 
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
 - "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
 - "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)"
 {% endif %}
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/index.md b/translations/ko-KR/content/code-security/supply-chain-security/index.md
index a0a051b654..4c9c860ff6 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/index.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index bd5d9c8950..d072c556a6 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -17,18 +17,18 @@ The results of dependency detection reported by {% data variables.product.produc
 
 {% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following:
 
-*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 *   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-*   {% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
 
-    {% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is discovered and added to the advisory database.
+    {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% if currentVersion ver_gt "enterprise-server@2.22" %} and synchronized to {% data variables.product.prodname_ghe_server %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
 
 ### Why don't I get vulnerability alerts for some ecosystems?
 
-{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot %} security updates are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot %} alerts are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
 
-It's worth noting that [{% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems.
+It's worth noting that {% data variables.product.prodname_dotcom %} Security Advisories may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}
 
 **Check**: Does the uncaught vulnerability apply to an unsupported ecosystem?
 
@@ -36,9 +36,9 @@ It's worth noting that [{% data variables.product.prodname_dotcom %} Security Ad
 
 The dependency graph includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
 
-{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% data variables.product.prodname_dependabot %} security updates only suggests a change where it can directly "fix" the dependency, that is, when these are:
+{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
 * Direct dependencies explicitly declared in a manifest or lockfile
-* Transitive dependencies declared in a lockfile
+* Transitive dependencies declared in a lockfile{% endif %}
 
 The dependency graph doesn't include “loose” dependencies. “Loose” dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile.
 
@@ -84,6 +84,7 @@ Some third-party tools use uncurated CVE data that isn't checked or filtered by
 
 Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant.
 
+{% if currentVersion == "free-pro-team@latest" %}
 ### 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.
@@ -97,10 +98,11 @@ When you click to display the alert details, you can see how many vulnerabilitie
 ![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
 **Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers.
+{% endif %}
 
 ### 더 읽을거리
 
 - "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/ko-KR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..7c186aac17
--- /dev/null
+++ b/translations/ko-KR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Upgrading from Dependabot.com to GitHub-native Dependabot
+intro: You can upgrade to GitHub-native Dependabot by merging a pull request that will allow your dependencies to continue being updated.
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot before then.
+
+After that date, any open pull requests from Dependabot Preview will remain open, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations.
+
+{% endwarning %}
+
+### About upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Dependabot Preview has been built directly into {% data variables.product.prodname_dotcom %}, so you can use {% data variables.product.prodname_dependabot %} alongside all the other functionality in {% data variables.product.prodname_dotcom %} without having to install and use a separate application. By migrating to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, we can also focus on bringing lots of exciting new features to {% data variables.product.prodname_dependabot %}, including more [ecosystem updates](https://github.com/github/roadmap/issues/150), [improved notifications](https://github.com/github/roadmap/issues/133), and {% data variables.product.prodname_dependabot %} support for [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) and [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Differences between Dependabot Preview and {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+While most of the Dependabot Preview features exist in {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, a few remain unavailable:
+- **Live updates:** We hope to bring these back in the future. For now, you can run {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} daily to catch new packages within one day of release.
+- **PHP environment variable registries:** For now, you can use {% data variables.product.prodname_actions %} to fetch dependencies from these registries.
+- **Auto-merge:** We always recommend verifying your dependencies before merging them; therefore, auto-merge will not be supported for the foreseeable future. For those of you who have vetted your dependencies, or are only using internal dependencies, we recommend adding third-party auto-merge apps, or setting up GitHub Actions to merge.
+
+In {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, you can configure all version updates using the configuration file. This file is similar to the Dependabot Preview configuration file with a few changes and improvements that will be automatically included in your upgrade pull request. For more information about the upgrade pull request, see "[Upgrading to GitHub-native Dependabot](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+To see update logs for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} that were previously on the Dependabot.com dashboard:
+
+  1. Navigate to your repository’s **Insights** page.
+  2. Click **Dependency graph** to the left.
+  3. Click **{% data variables.product.prodname_dependabot %}**.
+
+For more information about version updates with {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, see "[About Dependabot version updates](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+### Upgrading to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} requires you to merge the *Upgrade to GitHub-native Dependabot* pull request in your repository. This pull request includes the updated configuration file needed for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}.
+
+If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
+
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
+
+If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/ko-KR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ko-KR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index f44d3c3fa9..00b3248bac 100644
--- a/translations/ko-KR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/ko-KR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}. You can sort the list of alerts using 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 %}{% if currentVersion == "free-pro-team@latest" %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts using 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)."
 
+{% if currentVersion == "free-pro-team@latest" %}
 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 %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ 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.
+{% endif %}
 
 ### Viewing and updating vulnerable dependencies
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ You can enable automatic security updates for any repository that uses {% data v
 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](/github/administering-a-repository/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, use 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 currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Click the alert you'd like to view. ![Alert selected in list of alerts](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency.
+1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, click the **Dismiss** drop-down, and select a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. Click the version number of the vulnerable dependency to display detailed information. ![Detailed information on the vulnerable dependency](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert.
+1. The banner at the top of the **Dependencies** tab is displayed until all the vulnerable dependencies are resolved or you dismiss it. Click **Dismiss** in the top right corner of the banner and select a reason for dismissing the alert. ![Dismiss security banner](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### 더 읽을거리
 
-- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"
+- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
 - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ko-KR/content/codespaces/about-codespaces.md b/translations/ko-KR/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..e0792098d3
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: About Codespaces
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![An open codespace](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Developers can contribute from anywhere, on any machine, including tablets or Chromebooks, and there is no need to maintain local copies of intellectual property. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### About billing for {% data variables.product.prodname_codespaces %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %} For more information, see "[About billing for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)."
+
+### Joining the beta
+
+A limited number of people will be invited to join the beta. To join the waitlist, see [Sign up for Codespaces beta](https://github.com/features/codespaces/signup).
+
+### Contacting us about {% data variables.product.prodname_codespaces %}
+
+If you encounter problems using {% data variables.product.prodname_codespaces %}, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
+
+If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the [Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) discussion.
diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..f621a80494
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: About billing for Codespaces
+intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..75be9e6f73
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Allowing your codespace to access a private image registry
+intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry.
+
+When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)."
+
+For example, if you had a private image registry in Azure, you could create the following secrets:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/index.md b/translations/ko-KR/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..21334e4bb5
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: Reference
+intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..2e91229596
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: Troubleshooting your codespace
+intro: Use this guide to help you troubleshoot common issues with your codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Known Limitations
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### {% data variables.product.prodname_vscode %} troubleshooting
+
+Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.
+
+
+### Configuration troubleshooting
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+This codespace is currently running in recovery mode due to a container error.
+```
+
+Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
+
+### dotfiles troubleshooting
+
+- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles.
+- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned.
+  - If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
+  - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
+- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**.
+
+
+### Browser troubleshooting
+
+If you encounter issues while using a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as[`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari).
+
+If you encounter issues while using a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository.
+
+### Container storage troubleshooting
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.
+
+- Remove packages that are no longer by using `sudo apt autoremove`
+- Clean the apt cache by using `sudo apt clean`
+- Delete unneeded files like build artifacts and logs (these are very project-dependent)
+- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10`
+
+More destructive options:
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes)
+- Remove untracked files from working tree: `git clean -i`
+
+### 문의처
+
+If you still need help, you can contact us. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)."
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..19fc36dfc5
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Creating a codespace
+intro: You can create a codespace for a branch in a repository to develop online.
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About codespace creation
+
+You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)."
+
+
+When you create a codespace, a number of steps happen to enable full access to your development environment.
+
+- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
+- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
+- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+- Your Docker container, `docker-compose`, or other initialization is run.
+- At this point, the codespace is marked as available and you can connect.
+- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up.
+  - The codespace shares ports added in the `devcontainer.json` file.
+  - The codespace runs anything specified in `postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Finally, the codespace does a full clone of the repo so you have full access to it.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### Creating a codespace
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Under the repository name, use the "Branch" drop-down menu, and select the branch you want to create a codespace for.
+
+  ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..e6784b3775
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: Deleting a codespace
+intro: You can delete a codespace you no longer need.
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+
+2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
+
+### Deleting a codespace in {% data variables.product.prodname_vscode %}
+
+For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)."
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..a3ae678e34
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: Developing in a codespace
+intro: 'You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}''s features.'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About development with {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Side Bar - By default, this area shows your project files in the Explorer.
+2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
+3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
+4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
+5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
+
+For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
+
+#### Personalizing your codespace
+
+{% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)."
+
+{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
+
+#### Running your app from a codespace
+{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)."
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Navigating to an existing codespace
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. Click the name of the codespace you want to develop in. ![Name of codespace](/assets/images/help/codespaces/click-name-codespace.png)
+
+Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..7965bfc793
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Forwarding ports in your codespace
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About forwarded ports
+
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application.
+
+When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. For example, if an application outputs `http://127.0.0.1:4000` or `http://localhost:4000` to the console, the log would automatically convert the output to a clickable URL for port 4000.
+
+![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration.
+
+### Forwarding a port
+
+You can manually forward a port that wasn't forwarded automatically.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png)
+1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
+
+### Labeling a port
+
+You can label a port to make the port more easily identifiable in a list.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### Sharing a port
+
+If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png)
+1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Send the copied URL to the person you want to share the port with.
+
+### Adding a port to the codespace configuration
+
+You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..e436eb79e8
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: Developing in a codespace
+intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..f9d0fa00c3
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: Using Codespaces in Visual Studio Code
+intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 빌드전 요구 사양
+
+To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later.
+
+Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation.
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+4. Sign in to {% data variables.product.product_name %} to approve the extension.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+5. Sign in to {% data variables.product.product_name %} to approve the extension.
+
+{% endwindows %}
+
+### Creating a codespace in {% data variables.product.prodname_vscode %}
+
+After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_github_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Click the machine type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png)
+### Opening a codespace in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Under "Codespaces", click the codespace you want to develop in.
+3. Click the Connect to Codespace icon. ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### Changing the machine type in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+You can change the machine type of your codespace at any time.
+
+1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`).
+2. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. Click the codespace that you want to change. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. Choose the machine type you want to use. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts.
+
+### Deleting a codespace in {% data variables.product.prodname_vscode %}
+
+1. Under "Codespaces", right-click the codespace you want to delete.
+2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..1ef48ef4f9
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About source control in {% data variables.product.prodname_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+### Creating or switching branches
+
+1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**.
+1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace.
+
+{% endtip %}
+
+### Pulling changes from the remote repository
+
+You can pull changes from the remote repository into your codespace at any time.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. In the drop-down menu, click **Pull**.
+
+If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+### Setting your codespace to automatically fetch new changes
+
+You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
+
+If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
+
+1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Click **Create**.
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..762b944b79
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Getting started with your C# (.NET) project in Codespaces
+shortTitle: Getting started with your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 빌드전 요구 사양
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 다음 단계
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..2416d6abaa
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Getting started with your Java project in Codespaces
+shortTitle: Getting started with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 빌드전 요구 사양
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 다음 단계
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..8843fe5e05
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Getting started with your Node.js project in Codespaces
+shortTitle: Getting started with your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 빌드전 요구 사양
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 다음 단계
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..7af44493d7
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Getting started with your Python project in Codespaces
+shortTitle: Getting started with your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 빌드전 요구 사양
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 다음 단계
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..013f96d508
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: Getting Started with {% data variables.product.prodname_codespaces %}
+intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/ko-KR/content/codespaces/guides.md b/translations/ko-KR/content/codespaces/guides.md
new file mode 100644
index 0000000000..9a56c01990
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: 안내서
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/ko-KR/content/codespaces/index.md b/translations/ko-KR/content/codespaces/index.md
new file mode 100644
index 0000000000..428d92acb6
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc'
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..1034377b45
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing Codespaces for your organization
+intro: 'You can manange and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..f3d0f9eb29
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Managing access and security for your organization's codespaces
+shortTitle: Managing access and security for your organization
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Organization owners can manage which repositories a codespace can access.
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.
+
+To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
new file mode 100644
index 0000000000..7f5cb98c71
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Managing encrypted secrets for your repository and organization for Codespaces
+shortTitle: Managing secrets for your repository and organization
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Limits for secrets
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+Secrets are limited to 64 KB in size.
+
+### Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. At the top of the page, click **New repository secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the value for your secret.
+1. Click **Add secret**.
+
+### Adding secrets for an organization
+
+When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. At the top of the page, click **New organization secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the **Value** for your secret.
+1. From the **Repository access** dropdown list, choose an access policy. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+1. Click **Add secret**.
+
+### Reviewing access to organization-level secrets
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. The list of secrets includes any configured permissions and policies. 예시: ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
+1. For more details on the configured permissions for each secret, click **Update**.
diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..f8c2c9ac71
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.
+permissions: To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..c438a70311
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing your organization's audit logs for Codespaces
+shortTitle: Reviewing your organization's audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)."
diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/index.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..2241dd5ecf
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..6ad3cdee4a
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### About encrypted secrets for {% data variables.product.prodname_codespaces %}
+
+You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets.
+
+- Personal access tokens to cloud services
+- Service principals
+- Subscription identifiers
+- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Limits for secrets
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+Secrets are limited to 64 KB in size.
+
+### Adding a secret
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. Under "Name", type a name for your secret. !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Click **Add secret**.
+
+### Editing a secret
+
+You can update the value of an existing secret, and you can change which repositories can access a secret.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. Click **Save changes**.
+
+### Deleting a secret
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..c9492f1760
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: Managing GPG verification for Codespaces
+intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)."
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..f7e213e258
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)."
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
diff --git a/translations/ko-KR/content/codespaces/quickstart.md b/translations/ko-KR/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..aa93c46407
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..37ebec2c4c
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,142 @@
+---
+title: Configuring Codespaces for your project
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### Dockerfile
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Follow the prompts to customize your definition.
+1. Click **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### Creating a custom codespace configuration
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+You can define default editor settings for {% data variables.product.prodname_vscode %} in two places.
+
+* Editor settings defined in `.vscode/settings.json` are applied as _Workspace_-scoped settings in the codespace.
+* Editor settings defined in the `settings` key in `devcontainer.json` are applied as _Remote [Codespaces]_-scoped settings in the codespace.
+
+After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)."
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### Applying changes to your configuration
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}
+!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - To diagnose the error by reviewing the creation logs, click **View creation log**.
+   - To fix the errors identified in the logs, update your `devcontainer.json` file.
+   - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md b/translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..c98262fe43
--- /dev/null
+++ b/translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: Personalizing Codespaces for your account
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your `dotfiles` repository, see [GitHub does dotfiles](https://dotfiles.github.io/).
+
+If your user account on {% data variables.product.prodname_dotcom %} owns a public repository named `dotfiles`, {% data variables.product.prodname_dotcom %} automatically uses this repository to personalize your codespace environment. Private `dotfiles` repositories are not currently supported.
+
+Your `dotfiles` repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make.
+
+When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your `dotfiles` repository to the codespace environment, and looks for one of the following files to set up the environment.
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
+
+Any changes to your `dotfiles` repository will apply only to each new codespace, and do not affect any existing codespace.
+
+{% note %}
+
+**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the _User_ settings for the {% data variables.product.prodname_vscode %} editor with your `dotfiles` repository. You can set default _Workspace_ and _Remote [Codespaces]_ settings for a specific project in the project's repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)."
+
+{% endnote %}
+
+You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)."
+
+### 더 읽을거리
+
+* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
diff --git a/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md
index 49434a71bb..8f7175f7d5 100644
--- a/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ With wikis, you can write content just like everywhere else on {% data variables
 
 You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository. For more information, see "[Changing access permissions for wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)".
 
+{% note %}
+
+**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository.
+
+{% endnote %}
+
 ### 더 읽을거리
 
 - "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
diff --git a/translations/ko-KR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/ko-KR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index 3211bde2a1..1721d9b3fa 100644
--- a/translations/ko-KR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/ko-KR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ In your organization's repositories, blocked users also cannot:
 ### Blocking a user in the organization settings
 
 1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. Under "Block a user", type the username of the user you'd like to block. ![Username field](/assets/images/help/organizations/org-block-username-field.png)
 7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user. ![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/ko-KR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/ko-KR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index d902d4f02b..78cc30755a 100644
--- a/translations/ko-KR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/ko-KR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,9 +28,9 @@ If you selected a specific amount of time to block the user, they will be automa
 
 ### Unblocking a user in the organization settings
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**. ![Unblock user button](/assets/images/help/organizations/org-unblock-user-button.png)
 
diff --git a/translations/ko-KR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/ko-KR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index 4c964a5b04..25b505cc31 100644
--- a/translations/ko-KR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/ko-KR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,9 +10,9 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Under "Blocked users", review the list of users who are blocked from your organization. ![List of blocked users](/assets/images/help/settings/list-of-blocked-users-for-org.png)
 
diff --git a/translations/ko-KR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/ko-KR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index 7c81047466..855167b88a 100644
--- a/translations/ko-KR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/ko-KR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -28,9 +28,9 @@ Organization owners can also block users for a specific amount of time. After th
 
 ### Limiting interactions in your organization
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the organization settings sidebar, click **Moderation settings**. !["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. Under "Moderation settings", click **Interaction limits**. !["Interaction limits" in the organization settings sidebar](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index f158f1949b..84231640da 100644
--- a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -29,14 +29,14 @@ Default files are not included in clones, packages, or downloads of individual r
 
 You can create defaults in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} for the following community health files:
 
-| Community health file                                                                                                                                                                                   | 설명                                                                                                                                                                                                                                                                                                                                                  |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| Community health file                                                                                                                                                                                   | 설명                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
 | *CODE_OF_CONDUCT.md*                                                                                                                                                                                  | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
 | *CONTRIBUTING.md*                                                                                                                                                                                       | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% if currentVersion == "free-pro-team@latest" %}
 | *FUNDING.yml*                                                                                                                                                                                           | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
-| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" %}
-| *SECURITY.md*                                                                                                                                                                                           | A SECURITY file gives instructions for how to responsibly report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/articles/adding-a-security-policy-to-your-repository)."{% endif %}
-| *SUPPORT.md*                                                                                                                                                                                            | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."                                                                                                                                              |
+| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| *SECURITY.md*                                                                                                                                                                                           | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+| *SUPPORT.md*                                                                                                                                                                                            | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."                                                                                                                                                                                               |
 
 You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
 
diff --git a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index e0aa4c72c8..7fd4abbed9 100644
--- a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file.
+### About contributing guidelines
+To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ You can create default contribution guidelines for your organization{% if curren
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive, and can have an extension such as *.md* or *.txt*. ![New file name](/assets/images/help/repository/new-file-name.png)
+3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![New file name](/assets/images/help/repository/new-file-name.png)
     - To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
     - To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. In the new file, add contribution guidelines. These could include:
     - Steps for creating good issues or pull requests.
     - Links to external documentation, mailing lists, or a code of conduct.
diff --git a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md
index 799c6a0689..5959585913 100644
--- a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -179,7 +179,7 @@ You must complete this step of the GitHub App Manifest flow within one hour.
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest).
 
diff --git a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index 1e4013ae47..491c3abb8f 100644
--- a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method.
+This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
 
 To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run.
 
@@ -240,31 +235,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -276,40 +262,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created.
+The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created.
 
-Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
+Here's what this code is doing. First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
 
 You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`.
 
@@ -613,29 +589,23 @@ Now you've got all the information you need to update your check run. In the [fi
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -645,51 +615,45 @@ You'll need to update that code to use the `conclusion` variable you set based o
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/ko-KR/content/developers/apps/making-a-github-app-public-or-private.md b/translations/ko-KR/content/developers/apps/making-a-github-app-public-or-private.md
index a3938ed702..86e6d04355 100644
--- a/translations/ko-KR/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/ko-KR/content/developers/apps/making-a-github-app-public-or-private.md
@@ -23,7 +23,7 @@ Public installation flows have a landing page to enable other people besides the
 
 ### Private installation flow
 
-Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private, or internal, GitHub Apps can only be installed on the user or organization account of the owner.
+Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### Changing who can install your GitHub App
 
@@ -34,5 +34,5 @@ To change who can install the GitHub App:
 {% data reusables.user-settings.github_apps %}
 3. Select the GitHub App whose installation option you want to change. ![App selection](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. Depending on the installation option of your GitHub App, click either **Make public** or **Make internal**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
-6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App internal**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md
index 008af19028..8eddbd9a8d 100644
--- a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md
+++ b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md
@@ -30,7 +30,7 @@ Check headers to see what OAuth scopes you have, and what the API action accepts
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
-HTTP/1.1 200 OK
+HTTP/2 200
 X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
diff --git a/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 86a4e7d7b8..eed9079e16 100644
--- a/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -370,10 +370,10 @@ After you click **Install**, look at the output in your Terminal. You should see
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 This is good news! It means your app received a notification that it was installed on your GitHub account. If you see something like this, your app is running on the server as expected. 🙌
diff --git a/translations/ko-KR/content/developers/apps/using-content-attachments.md b/translations/ko-KR/content/developers/apps/using-content-attachments.md
index 708a0e1f46..18fcfa1b29 100644
--- a/translations/ko-KR/content/developers/apps/using-content-attachments.md
+++ b/translations/ko-KR/content/developers/apps/using-content-attachments.md
@@ -130,9 +130,8 @@ To create a Probot App, follow these steps:
 2. Open the project you created, and customize the settings in the `app.yml` file. Subscribe to the `content_reference` event and enable `content_references` write permissions:
 
    ``` yml
-
     default_events:
-    - content_reference
+      - content_reference
     # The set of permissions needed by the GitHub App. The format of the object uses
     # the permission name for the key (for example, issues) and the access type for
     # the value (for example, write).
@@ -141,10 +140,10 @@ To create a Probot App, follow these steps:
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
diff --git a/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index a8f63bf4a5..3d5f8d6c53 100644
--- a/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ To offer paid plans for your app, the app must be owned by an organization and y
 
 ### Requesting publisher verification
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the left sidebar, click **Developer settings**. ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. Under "Publisher Verification", complete the information in the checklist:
    - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
    - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."
-   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/ko-KR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/ko-KR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index 647380828e..6410831f4d 100644
--- a/translations/ko-KR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/ko-KR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ Here are guidelines about the fields you'll need to fill out in the **Listing de
 
 #### Listing name
 
-Your app's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters.
+Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing {% data variables.product.product_name %} user, unless the name is your own user or organization name.
 
 #### Very short description
 
diff --git a/translations/ko-KR/content/developers/overview/secret-scanning.md b/translations/ko-KR/content/developers/overview/secret-scanning.md
index 7a055b18d2..a8672ddbe9 100644
--- a/translations/ko-KR/content/developers/overview/secret-scanning.md
+++ b/translations/ko-KR/content/developers/overview/secret-scanning.md
@@ -15,9 +15,9 @@ topics:
 
 When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice.
 
-When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
+When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
 
-This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program.
+This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program.
 
 ### The {% data variables.product.prodname_secret_scanning %} process
 
@@ -54,26 +54,20 @@ Send this information to <a href="mailto:secret-scanning@github.com">secret-scan
 
 #### Create a secret alert service
 
-Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send a HTTP `POST` message to your endpoint.
+Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint.
 
 ##### Example POST sent to your endpoint
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %}  may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out.
@@ -88,19 +82,31 @@ We strongly recommend you implement signature validation in your secret alert se
 
 You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm.
 
-Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set.
+{% note %}
+
+**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
+
+{% endnote %}
+
+Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code snippets assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens) to avoid hitting rate limits. The PAT does not need any scopes/permissions.
+
+{% note %}
+
+**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
+
+{% endnote %}
 
 **Sample message sent to verify endpoint**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Validation sample in Go**
@@ -123,14 +129,14 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
   // Fetch the list of GitHub Public Keys
-  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
     fmt.Printf("Error preparing request: %s\n", err)
     os.Exit(1)
@@ -242,16 +248,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -357,4 +363,3 @@ A few important points:
 **Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
 {% endnote %}
-
diff --git a/translations/ko-KR/content/developers/overview/using-ssh-agent-forwarding.md b/translations/ko-KR/content/developers/overview/using-ssh-agent-forwarding.md
index c6d14bbea8..8ca4a4bc20 100644
--- a/translations/ko-KR/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/ko-KR/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-On Mac OS X, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
+On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md b/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md
index a9078885ea..96b15d4fcc 100644
--- a/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ The event objects returned from the Events API endpoints have the same structure
 This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events).
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
diff --git a/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index 047202952d..0065927c9a 100644
--- a/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -61,7 +61,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 #### Example delivery
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -200,7 +200,9 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment.
 
-Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event.
+#### Availability
+
+- {% data variables.product.prodname_github_app %}s with the `content_references:write` permission
 
 #### Webhook payload example
 
@@ -1010,12 +1012,6 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% endnote %}
 
-{% tip %}
-
-**Note**: The webhook payload example following the table differs significantly from the Events API payload described in the table. Among other differences, the webhook payload includes both `sender` and `pusher` objects. Sender and pusher are the same user who initiated the `push` event, but the `sender` object contains more detail.
-
-{% endtip %}
-
 #### Availability
 
 - Repository webhooks
@@ -1206,7 +1202,7 @@ Activity related to a security advisory. A security advisory provides informatio
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
+You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
 
 #### Availability
 
diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 58d0b5fbac..9c203e3365 100644
--- a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
 
-In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)."
+In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji.
 
 You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."
 
diff --git a/translations/ko-KR/content/discussions/index.md b/translations/ko-KR/content/discussions/index.md
index 9974eb20a2..3c52fee2cf 100644
--- a/translations/ko-KR/content/discussions/index.md
+++ b/translations/ko-KR/content/discussions/index.md
@@ -34,24 +34,3 @@ versions:
 <!-- {% link_with_intro /discussions-guides %} -->
 <!-- {% link_with_intro /collaborating-with-your-community-using-discussions %} -->
 <!-- {% link_with_intro /managing-discussions-for-your-community %} -->
-
-<!-- Community examples -->
-{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %}
-{% if discussionsCommunityExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Communities using discussions</h2>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render discussions-community-card for discussionsCommunityExamples as example %}
-  </div>
-  {% if discussionsCommunityExamples.length > 6 %}
-    <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Show more {% octicon "arrow-right" %}</button>
-  {% endif %}
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Sorry, there is no result for <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/discussions_community_examples.yml">Add your community {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md b/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md
index 1ebace0509..47fefa334e 100644
--- a/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md
@@ -47,6 +47,8 @@ For each branch protection rule, you can choose to enable or disable the followi
 - [Allow force pushes](#allow-force-pushes)
 - [Allow deletions](#allow-deletions)
 
+For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+
 #### Require pull request reviews before merging
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
@@ -100,7 +102,15 @@ When you enable required commit signing on a branch, contributors {% if currentV
 
 {% note %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+**참고:**
+
+* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+
+{% else %}
 **Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+{% endif %}
 
 {% endnote %}
 
diff --git a/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md
index 8e5e0bc38c..f3071030df 100644
--- a/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/ko-KR/content/github/administering-a-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ You can choose the default branch for a repository. The default branch is the ba
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
 You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
 
diff --git a/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index 83b7e0b95b..1f9fff8095 100644
--- a/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -82,3 +82,21 @@ You can disable all workflows for a repository or set a policy that configures w
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your repository
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. Click **Save** to apply the settings.
+{% endif %}
diff --git a/translations/ko-KR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index 4206ed02d1..0a368869a7 100644
--- a/translations/ko-KR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/ko-KR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### About FUNDING files
 
-You can configure your sponsor button by editing a _FUNDING.yml_ file in your repository's `.github` folder, on the default branch. You can configure the button to include sponsored developers in {% data variables.product.prodname_sponsors %}, external funding platforms, or a custom funding URL. For more information about {% data variables.product.prodname_sponsors %}, see "[About GitHub Sponsors](/articles/about-github-sponsors)."
+You can configure your sponsor button by editing a _FUNDING.yml_ file in your repository's `.github` folder, on the default branch. You can configure the button to include sponsored developers in {% data variables.product.prodname_sponsors %}, external funding platforms, or a custom funding URL. For more information about {% data variables.product.prodname_sponsors %}, see "[About GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
 
 You can add one username, package name, or project name per external funding platform and up to four custom URLs. You can add up to four sponsored developers or organizations in {% data variables.product.prodname_sponsors %}. Add each platform on a new line, using the following syntax:
 
@@ -76,5 +76,5 @@ Anyone with admin permissions can enable a sponsor button in a repository.
 {% data reusables.files.propose_new_file %}
 
 ### 더 읽을거리
-- "[About {% data variables.product.prodname_sponsors %} for open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
 - "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index e71f3a4f06..32ce0feb2d 100644
--- a/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -35,10 +35,11 @@ You can manage the security and analysis features for your {% if currentVersion
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. The control for "
+{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% if currentVersion == "free-pro-team@latest" %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
 **Note:** If you disable
 
@@ -46,11 +47,11 @@ You can manage the security and analysis features for your {% if currentVersion
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
 4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. Before you can enable "
-{% data variables.product.prodname_secret_scanning %}" for your repository, you need to enable {% data variables.product.prodname_GH_advanced_security %}.
+{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.
    ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index 3368c6d013..2043b151eb 100644
--- a/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ For more information about repository permission levels, see "[Permission levels
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Trashcan icon for removing access](/assets/images/help/repository/manage-access-remove.png)
+4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trash" aria-label="The trash icon" %}. ![trash icon for removing access](/assets/images/help/repository/manage-access-remove.png)
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md b/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md
index 190210ca02..9f56a37283 100644
--- a/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/ko-KR/content/github/administering-a-repository/renaming-a-branch.md
@@ -6,7 +6,7 @@ versions:
   free-pro-team: '*'
   enterprise-server: '>=3.2'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About renaming branches
@@ -17,6 +17,8 @@ When you rename a branch on {% data variables.product.product_location %}, any U
 
 Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
 
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+
 ### Renaming a branch
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -35,4 +37,10 @@ From the local clone of the repository on a computer, run the following commands
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+Optionally, run the following command to remove tracking references to the old branch name.
+```
+$ git remote prune origin
 ```
diff --git a/translations/ko-KR/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/ko-KR/content/github/administering-a-repository/restoring-a-deleted-repository.md
index 2fda93f2f3..39efaee3f2 100644
--- a/translations/ko-KR/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/ko-KR/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -31,9 +31,9 @@ Restoring a repository will not restore release attachments or team permissions.
 
 ### Restoring a deleted repository that was owned by an organization
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/ko-KR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index e7bdafed55..8f6ef6295b 100644
--- a/translations/ko-KR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/ko-KR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ You can also see deployment information on the "Conversation" tab of a pull requ
 ### Viewing the deployments dashboard
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### 더 읽을거리
  - "[About pull requests](/articles/about-pull-requests)"
diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/ko-KR/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..3960dbd54e
--- /dev/null
+++ b/translations/ko-KR/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Troubleshooting issues with Camo
+
+In rare circumstances, images that are processed through Camo might not appear on {% data variables.product.prodname_dotcom %}. Here are some steps you can take to determine where the problem lies.
+
+{% windows %}
+
+{% tip %}
+
+Windows users will either need to use the Git Powershell (which is installed alongside [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) or download [curl for Windows](http://curl.haxx.se/download.html).
+
+{% endtip %}
+
+{% endwindows %}
+
+#### An image is not showing up
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Request the image headers using `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. Check the value of `Content-Type`. In this case, it's `image/x-png`.
+4. Check that content type against [the list of types supported by Camo](https://github.com/atmos/camo/blob/master/mime-types.json).
+
+If your content type is not supported by Camo, you can try several actions:
+  * If you own the server that's hosting the image, modify it so that it returns a correct content type for images.
+  * If you're using an external service for hosting images, contact support for that service.
+  * Make a pull request to Camo to add your content type to the list.
+
+#### An image that changed recently is not updating
+
+If you changed an image recently and it's showing up in your browser but not {% data variables.product.prodname_dotcom %}, you can try resetting the cache of the image.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Request the image headers using `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+Check the value of `Cache-Control`. In this example, there's no `Cache-Control`. In that case:
+  * If you own the server that's hosting the image, modify it so that it returns a `Cache-Control` of `no-cache` for images.
+  * If you're using an external service for hosting images, contact support for that service.
+
+ If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
+
+#### Removing an image from Camo's cache
+
+Purging the cache forces every {% data variables.product.prodname_dotcom %} user to re-request the image, so you should use it very sparingly and only in the event that the above steps did not work.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Purge the image using `curl -X PURGE` on the Camo URL.
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### Viewing images on private networks
+
+If an image is being served from a private network or from a server that requires authentication, it can't be viewed by {% data variables.product.prodname_dotcom %}. In fact, it can't be viewed by any user without asking them to log into the server.
+
+To fix this, please move the image to a service that is publicly available.
+
+### 더 읽을거리
+
+- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md
index cea6440806..9eeabd1213 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: About commit signature verification
-intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can trust that the changes come from a trusted source.'
+intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures/
   - /articles/about-gpg/
@@ -16,15 +16,35 @@ topics:
 
 ### About commit signature verification
 
-You can sign commits and tags locally, so other people can verify that your work comes from a trusted source. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag as verified.
+You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% if currentVersion == "free-pro-team@latest" %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
 
 ![Verified commit](/assets/images/help/commits/verified-commit.png)
 
-If a commit or tag has a signature that cannot be verified, {% data variables.product.product_name %} marks the commit or tag as unverified.
+{% if currentVersion == "free-pro-team@latest" %}
+Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+#### Default statuses
+
+| 상태                     | 설명                                                                |
+| ---------------------- | ----------------------------------------------------------------- |
+| **Verified**           | The commit is signed and the signature was successfully verified. |
+| **Unverified**         | The commit is signed but the signature could not be verified.     |
+| No verification status | The commit is not signed.                                         |
+
+#### Statuses with vigilant mode enabled
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+If a commit or tag has a signature that can't be verified,
+{% data variables.product.product_name %} marks the commit or tag "Unverified."
+{% endif %}
 
 Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."
 
-You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see "[Checking your commit and tag signature verification status](/articles/checking-your-commit-and-tag-signature-verification-status)."
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."
diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-ssh.md b/translations/ko-KR/content/github/authenticating-to-github/about-ssh.md
index 49b0d0b135..c410cbbe34 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-When you set up SSH, you'll [generate an SSH key and add it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and then [add the key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). Adding the SSH key to the ssh-agent ensures that your SSH key has an extra layer of security through the use of a passphrase. For more information, see "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
+When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
-{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you'll need to authorize it first. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %}
+You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
 
-We recommend that you regularly [review your SSH keys list](/articles/reviewing-your-ssh-keys) and revoke any that are invalid or have been compromised.
+{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %}
+
+To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. For more information, see "[Reviewing your SSH keys](/github/authenticating-to-github/reviewing-your-ssh-keys)."
 
 {% if currentVersion == "free-pro-team@latest" %}
 If you haven't used your SSH key for a year, then
@@ -28,8 +30,4 @@ If you're a member of an organization that provides SSH certificates, you can us
 
 - "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
 - "[Testing your SSH connection](/articles/testing-your-ssh-connection)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
 - "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
-{%- if currentVersion == "free-pro-team@latest" %}
-- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"
-{%- endif %}
diff --git a/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index 8b9e94a0e8..26b77759f2 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also add an SSH key using the {% data variables.product.prodname_cli %}. For more information, see "[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. Copy the SSH public key to your clipboard.
@@ -80,6 +88,7 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc
   If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace.
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
   # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
 
diff --git a/translations/ko-KR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/ko-KR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index 05e38479a3..84aed25766 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**Note:** GPG does not come installed by default on OS X or Windows. To install GPG command line tools, see [GnuPG's Download page](https://www.gnupg.org/download/).
+**Note:** GPG does not come installed by default on macOS or Windows. To install GPG command line tools, see [GnuPG's Download page](https://www.gnupg.org/download/).
 
 {% endnote %}
 
diff --git a/translations/ko-KR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/ko-KR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index 24bde26f18..e85865d63f 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %}, navigate to your pull request.
 {% data reusables.repositories.review-pr-commits %}
-3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified or unverified. ![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. To view more detailed information about the commit signature, click **Verified** or **Unverified**. ![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-If your commit signature is unverified, you can learn more about why by clicking the **Unverified** box. ![Unverified signed commit](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. To view more detailed information about the commit signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### Checking your tag signature verification status
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. At the top of the Releases page, click **Tags**. ![Tags page](/assets/images/help/releases/tags-list.png)
-3. Next to your tag description, there is a box that shows whether your tag signature is verified or unverified. ![verified tag signature](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. To view more detailed information about the tag signature, click **Verified** or **Unverified**. If your tag signature is unverified, you can learn more about why by clicking the **Unverified** box. ![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. Next to your tag description, there is a box that shows whether your tag signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![verified tag signature](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. To view more detailed information about the tag signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md
index 72e0a67b4d..1899d40dd3 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
 
-{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### Creating a token
 
-{% if currentVersion == "free-pro-team@latest" %}1. [Verify your email address](/articles/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -45,13 +45,13 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
    {% else %}
    ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **Warning:** Treat your tokens like passwords and keep them secret. When working with the API, use tokens as environment variables instead of hardcoding them into your programs.
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
 
 ### Using a token on the command line
 
@@ -59,7 +59,7 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
 
 Personal access tokens can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
 
-If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/articles/updating-credentials-from-the-osx-keychain) to replace your old password with the token.
+If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/ko-KR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..47895a80cd
--- /dev/null
+++ b/translations/ko-KR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
+
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### Enabling vigilant mode
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/ko-KR/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/ko-KR/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..507c21cb45
--- /dev/null
+++ b/translations/ko-KR/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### 빌드전 요구 사양
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### Solving the issue
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. Open Terminal.
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/ko-KR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ko-KR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index e6c44c2a0d..a9bd621dbf 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-If you don't already have an SSH key, you must [generate a new SSH key](#generating-a-new-ssh-key). If you're unsure whether you already have an SSH key, check for [existing keys](/articles/checking-for-existing-ssh-keys).
+### About SSH key generation
 
-If you don't want to reenter your passphrase every time you use your SSH key, you can [add your key to the SSH agent](#adding-your-ssh-key-to-the-ssh-agent), which manages your SSH keys and remembers your passphrase.
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
 
 ### Generating a new SSH key
 
@@ -62,7 +69,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
 
   {% endlinux %}
 
-4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases).
+4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
 
 ### Adding your SSH key to the ssh-agent
 
-Before adding a new SSH key to the ssh-agent to manage your keys, you should have [checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) and [generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). <span class="platform-mac">When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source.</span>
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source.</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
       $ touch ~/.ssh/config
       ```
 
-    * Open your `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` if you are not using the default location and name for your `id_ed25519` key.
+    * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
 
       ```
       Host *
@@ -106,6 +113,25 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **Note:** If you see an error like this
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      add an additional config line to your `Host *` section:
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
   {% endnote %}
 
-4. [Add the SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Add the SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  In some Linux environments, you need root access to run the command:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Add the SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endif %}
+
 ### 더 읽을거리
 
 - "[About SSH](/articles/about-ssh)"
diff --git a/translations/ko-KR/content/github/authenticating-to-github/index.md b/translations/ko-KR/content/github/authenticating-to-github/index.md
index 6d04aeac57..c29fb47c03 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/index.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/index.md
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/ko-KR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ko-KR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index e517adc621..047bbadc4b 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ You can use your two-factor authentication credentials or two-factor authenticat
 5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent. ![One-time password field](/assets/images/help/2fa/one-time-password-field.png)
 6. Click **Verify email address**.
 7. Choose an alternative verification factor.
-    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify this device**.
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
     - 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**. ![Alternative verification buttons](/assets/images/help/2fa/alt-verifications.png)
 8. A member of {% data variables.contact.github_support %} will review your request and email you within 3-5 business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
diff --git a/translations/ko-KR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/ko-KR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index b3553f6b84..6338e180d8 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -15,7 +15,7 @@ topics:
 
 {% mac %}
 
-If you [configured your SSH passphrase with the OS X Keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
 
 1. In Finder, search for the **Keychain Access** app. ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
 2. In Keychain Access, search for **SSH**.
diff --git a/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md
index 1804326600..37221334d4 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-security-log.md
@@ -38,23 +38,23 @@ The security log lists all actions performed within the last 90 days{% if curren
 
 The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
 
-| Category name                                                                          | 설명                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %}
-| [`account_recovery_token`](#account_recovery_token-category-actions)                   | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                |
-| [`결제`](#billing-category-actions)                                                      | Contains all activities related to your billing information.                                                                                                                                                                                                                                                                                                                                                                   |
-| [`codespaces`](#codespaces-category-actions)                                           | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."                                                                                                                                                                                         |
-| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.                                                                                                                                                                                                                                                                                                          |
+| Category name                                                                          | 설명                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| [`account_recovery_token`](#account_recovery_token-category-actions)                   | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                                                     |
+| [`결제`](#billing-category-actions)                                                      | Contains all activities related to your billing information.                                                                                                                                                                                                                                                                                                                                                                                                        |
+| [`codespaces`](#codespaces-category-actions)                                           | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."                                                                                                                                                                                                                              |
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.                                                                                                                                                                                                                                                                                                                                               |
 | [`marketplace_listing`](#marketplace_listing-category-actions)                         | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
 | [`oauth_access`](#oauth_access-category-actions)                                       | Contains all activities related to [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) you've connected with.{% if currentVersion == "free-pro-team@latest" %}
 | [`payment_method`](#payment_method-category-actions)                                   | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %}
-| [`profile_picture`](#profile_picture-category-actions)                                 | Contains all activities related to your profile picture.                                                                                                                                                                                                                                                                                                                                                                       |
-| [`프로젝트`](#project-category-actions)                                                    | Contains all activities related to project boards.                                                                                                                                                                                                                                                                                                                                                                             |
-| [`public_key`](#public_key-category-actions)                                           | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                              |
+| [`profile_picture`](#profile_picture-category-actions)                                 | Contains all activities related to your profile picture.                                                                                                                                                                                                                                                                                                                                                                                                            |
+| [`프로젝트`](#project-category-actions)                                                    | Contains all activities related to project boards.                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| [`public_key`](#public_key-category-actions)                                           | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                                                                   |
 | [`repo`](#repo-category-actions)                                                       | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %}
-| [`sponsors`](#sponsors-category-actions)                                               | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+| [`sponsors`](#sponsors-category-actions)                                               | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 | [`팀`](#team-category-actions)                                                          | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %}
 | [`two_factor_authentication`](#two_factor_authentication-category-actions)             | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
-| [`사용자`](#user-category-actions)                                                        | Contains all activities related to your account.                                                                                                                                                                                                                                                                                                                                                                               |
+| [`사용자`](#user-category-actions)                                                        | Contains all activities related to your account.                                                                                                                                                                                                                                                                                                                                                                                                                    |
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -90,6 +90,10 @@ An overview of some of the most common actions that are recorded as events in th
 
 | 동작                                   | 설명                                                                                                                                                                                                                       |
 | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create`                             | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                 |
+| `resume`                             | Triggered when you resume a suspended codespace.                                                                                                                                                                         |
+| `delete`                             | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                 |
+| `manage_access_and_security`         | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                           |
 | `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). |
 
 #### `marketplace_agreement_signature` category actions
@@ -181,22 +185,24 @@ An overview of some of the most common actions that are recorded as events in th
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` category actions
 
-| 동작                                            | 설명                                                                                                                                                                                                                                                                                                                       |
-| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`             | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                              |
-| `repo_funding_links_file_action`              | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                         |
-| `sponsor_sponsorship_cancel`                  | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                         |
-| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                           |
-| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/articles/managing-your-sponsorship)")                                                                                                                                                          |
-| `sponsor_sponsorship_tier_change`             | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                     |
-| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                     |
-| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                      |
-| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                   |
-| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
-| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
-| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)")                                                                                                                                                                                          |
-| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")    |
-| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                       |
+| 동작                                            | 설명                                                                                                                                                                                                                                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                |
+| `repo_funding_links_file_action`              | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                |
+| `sponsor_sponsorship_cancel`                  | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                |
+| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                             |
+| `sponsor_sponsorship_tier_change`             | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                            |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                      |
+| `sponsored_developer_disable`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled                                                                                                                                                                                                                          |
+| `sponsored_developer_redraft`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                   |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
+| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                                  |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                       |
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -258,4 +264,3 @@ An overview of some of the most common actions that are recorded as events in th
 | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `업데이트`    | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." |
 | `destroy` | Triggered when you clear the status on your profile.                                                                                                                 |
-
diff --git a/translations/ko-KR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/ko-KR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index a9248fc25a..197845d34c 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -11,7 +11,7 @@ topics:
 
 {% tip %}
 
-**GitHub Enterprise users**: Accessing GitHub Enterprise via SSH over the HTTPS port is currently not supported.
+**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
 
 {% endtip %}
 
diff --git a/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index 8293e7f31d..a99b0d5a18 100644
--- a/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/ko-KR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -89,7 +89,7 @@ The `ssh-agent` process will continue to run until you log out, shut down your c
 
 ### Saving your passphrase in the keychain
 
-On OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
+On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index 85dee1f9cc..f2b4f19782 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: About collaborative development models
-intro: The way you use pull requests depends on the type of development model you use in your project.
+intro: The way you use pull requests depends on the type of development model you use in your project. You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-There are two main types of development models with which you'd use pull requests. In the *fork and pull model*, anyone can fork an existing repository and push changes to their personal fork. You do not need permission to the source repository to push to a user-owned fork. The changes can be pulled into the source repository by the project maintainer. When you open a pull request proposing changes from your user-owned fork to a branch in the source (upstream) repository, you can allow anyone with push access to the upstream repository to make changes to your pull request.  This model is popular with open source projects as it reduces the amount of friction for new contributors and allows people to work independently without upfront coordination.
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. You do not need permission to the source repository to push to a user-owned fork. The changes can be pulled into the source repository by the project maintainer. When you open a pull request proposing changes from your user-owned fork to a branch in the source (upstream) repository, you can allow anyone with push access to the upstream repository to make changes to your pull request.  This model is popular with open source projects as it reduces the amount of friction for new contributors and allows people to work independently without upfront coordination.
 
 {% tip %}
 
@@ -20,7 +22,9 @@ There are two main types of development models with which you'd use pull request
 
 {% endtip %}
 
-In the *shared repository model*, collaborators are granted push access to a single shared repository and topic branches are created when changes need to be made. Pull requests are useful in this model as they initiate code review and general discussion about a set of changes before the changes are merged into the main development branch. This model is more prevalent with small teams and organizations collaborating on private projects.
+### Shared repository model
+
+In the shared repository model, collaborators are granted push access to a single shared repository and topic branches are created when changes need to be made. Pull requests are useful in this model as they initiate code review and general discussion about a set of changes before the changes are merged into the main development branch. This model is more prevalent with small teams and organizations collaborating on private projects.
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index 4948fdd1d9..0e5d20d58e 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -53,18 +53,18 @@ When a repository is set to automatically request checks for pushes, you can cho
 
 To skip or request checks for your commit, add one of the following trailer lines to the end of your commit message:
 
-- To _skip checks_ for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines followed by `skip-checks: true`:
+- To _skip checks_ for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - To _request_ checks for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines followed by `request-checks: true`:
+- To _request_ checks for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 6b96780b0a..ce6c7e0295 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. In the "Pull requests" list, click the pull request you'd like to mark as ready for review.
 3. In the merge box, click **Ready for review**. ![Ready for review button](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index 07febc66b0..39f341c177 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Modifying an active pull request locally
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index 7d880aebc2..596853b175 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ To reply to an existing line comment, you'll need to navigate to the comment on
 
 **팁:**
 - Pull request comments support the same [formatting](/categories/writing-on-github) as regular comments on {% data variables.product.product_name %}, such as @mentions, emoji, and references.
-- You can [add reactions](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) to comments in pull requests in the **Files changed** tab.
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index a51975c7e9..56e0dd1004 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -19,6 +19,14 @@ You can specify which branch you'd like to merge your changes into when you crea
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Changing the branch range and destination repository
 
 By default, pull requests are based on the parent repository's default branch. For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index 7ad0528134..8146b695c8 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ If the branch you want to delete is associated with an open pull request, you mu
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. Scroll to the branch that you want to delete, then click {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![delete the branch](/assets/images/help/branches/branches-delete.png)
+1. Scroll to the branch that you want to delete, then click {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![delete the branch](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..6b1de76aa9
--- /dev/null
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: 시작하기
+shortTitle: 시작하기
+intro: 'Learn about the {% data variables.product.prodname_dotcom %} flow and different ways to collaborate on and discuss your projects.'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md
index b822cfb422..1289052f0f 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Collaborating with issues and pull requests
-intro: 'Use the {% data variables.product.prodname_dotcom %} flow to track and discuss changes in issues, then propose and review changes in pull requests.'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -18,10 +18,9 @@ topics:
 
 ### Table of Contents
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index b5fc9f91f6..89adb6197a 100644
--- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ You can't merge a draft pull request. For more information about draft pull requ
 
 If you decide you don't want the changes in a topic branch to be merged to the upstream branch, you can [close the pull request](/articles/closing-a-pull-request) without merging.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Merging a pull request on {% data variables.product.prodname_dotcom %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..497f96cd9a
--- /dev/null
+++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### Introduction
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### 문제
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### Pull requests
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### Team discussions
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion.
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### 다음 단계
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index 52b31ee5d7..551e0bb040 100644
--- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
 
 {% endif %}
 
+### Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+The auto-generated table of contents is enabled by default for all Markdown files in a repository, but you can disable this feature for your repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under "Features", deselect **Table of contents**. ![Automatic TOC setting for repositories](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### Section links in README files and blob pages
 
-Many projects use a table of contents at the start of a README to direct users to different sections of the file. {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### Relative links and image paths in README files
 
diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index 3ff4803cf5..2e48725b34 100644
--- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -24,7 +24,7 @@ Anyone with read permissions to a template repository can create a repository fr
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches.
+You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 Creating a repository from a template is similar to forking a repository, but there are important differences:
diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index 39c4e310fa..47a0f23a2d 100644
--- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -20,7 +20,7 @@ topics:
 
 To create a template repository, you must create a repository, then make the repository a template. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)."
 
-After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
index 1653e79465..2bf5b8b24c 100644
--- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
+++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### Choosing the right license
 
-We created [choosealicense.com](http://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision.
+We created [choosealicense.com](https://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision.
 
 You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project.
 
@@ -76,7 +76,7 @@ When you search by a family license, your results will include all licenses in t
 
 ### Detecting a license
 
-[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
 
 If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file.
 
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
index 1a391907f9..2ad2b93a7e 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -31,18 +33,10 @@ You can use {% data variables.product.prodname_code_scanning %} with {% data var
 
 {% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
 
-{% if currentVersion == "free-pro-team@latest" %}
-
-### About billing for {% data variables.product.prodname_code_scanning %}
-
-{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
-
-{% endif %}
-
 ### About third-party code scanning tools
 
 {% data reusables.code-scanning.you-can-upload-third-party-analysis %}
@@ -53,7 +47,5 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 ### 더 읽을거리
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index 06cbc047d8..2c82c8ab9f 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 7aed7106e6..f358f5f7cf 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
index e5f964d564..c47cd6c407 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -23,7 +25,7 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %} on {% data variables.product.prodname_dotcom_the_website %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
 
 ### Editing a {% data variables.product.prodname_code_scanning %} workflow
 
@@ -47,7 +49,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the `
 
 #### Scanning pull requests
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. The `pull_request` event is not triggered if the pull request was opened from a private fork.
 
 For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
 
@@ -108,9 +110,7 @@ This workflow scans:
 
 ### Specifying an operating system
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
-
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.
 
 ``` yaml
 jobs:
@@ -119,17 +119,15 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
+You must ensure that Git is in the PATH variable on your self-hosted runners.
 
 ### Changing the languages that are analyzed
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
@@ -170,31 +168,34 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
@@ -294,6 +295,7 @@ paths-ignore:
 **Note**:
 
 * The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
 * `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index 863e2d4cbe..3edf6f1499 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -48,11 +50,11 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are `cpp`, `csharp`, `go`, `java`, `javascript`, and `python`.
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index db698238a7..3f7c8ed959 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -31,11 +33,7 @@ If your workflow uses a `language` matrix, `autobuild` attempts to build each of
 
 {% note %}
 
-{% if currentVersion == "github-ae@latest" %}**Note**: For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
-{% else %}
-**Note**: If you use self-hosted runners for
-{% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
-{% endif %}
+**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 
 {% endnote %}
 
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index 61ad2aa872..6f9db3849c 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### Table of Contents
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 25fb7e862d..7ffac959cb 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index da6a2dbb13..a22e9e9cd1 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,13 +1,15 @@
 ---
 title: Managing code scanning alerts for your repository
 shortTitle: Managing alerts
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, or close alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About alerts from {% data variables.product.prodname_code_scanning %}
@@ -45,81 +47,25 @@ You need write permission to view a summary of all the alerts for a repository o
 
 Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have closed.
 
 Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
 
 ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 ### Closing an alert
 
 Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
 
-{% else %}
-
-### Dismissing or deleting alerts
-
-There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
-
-Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
-
-When you dismiss an alert:
-
-- It's dismissed in all branches.
-- The alert is removed from the number of current alerts for your project.
-- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required.
-- The reason why you closed the alert is recorded.
-- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert.
-
-When you delete an alert:
-
-- It's deleted in all branches.
-- The alert is removed from the number of current alerts for your project.
-- It is _not_ added to the "Closed" list in the summary of alerts.
-- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.
-
-To dismiss or delete alerts:
-
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
 1. Select the **Close** drop-down menu and click a reason for closing the alert.    
    ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
-
-   ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   Optionally, you can use the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
-
-  ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
-
-  ![Open an alert from the summary list](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### Dismissing multiple alerts at once
-
-If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
-
-{% endif %}
-
 ### 더 읽을거리
 
 - "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index 7a20d4fd24..45d86bb47f 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} with a containerized build
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index 1fbde6c118..13c78e931c 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
@@ -30,17 +31,13 @@ The {% data variables.product.prodname_codeql_runner %} is a command-line tool t
 {% note %}
 
 **참고:**
-{% if currentVersion == "free-pro-team@latest" %}
-* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
-{% else %}
 * The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
-{% endif %}
 * The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
 {% endnote %}
 
 ### Downloading the {% data variables.product.prodname_codeql_runner %}
 
-You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+You can download the {% data variables.product.prodname_codeql_runner %} from https://github.com/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
 
 On Linux:
 
@@ -62,7 +59,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi
 Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
@@ -73,9 +70,8 @@ In addition to this, each CI server also needs:
 
 The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
 
-1. Allow the CI servers access to https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
-{% if currentVersion == "enterprise-server@2.22" %}
-1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
+1. Allow the CI servers access to https://github.com/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.
 1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
 
 ### Calling the {% data variables.product.prodname_codeql_runner %}
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index 8495bd7275..b7dbd10b8a 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About SARIF support
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
index 4d9a716b44..68c42221b1 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -21,12 +23,10 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a
 
 ### Setting up {% data variables.product.prodname_code_scanning %} using actions
 
-{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
+3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
 
    Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index d8f3762383..45396bd1a6 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -10,13 +10,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} results on pull requests
 
 In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or close all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
 
 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -40,28 +42,10 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
 
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Resolving an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### Dismissing an alert on your pull request
-
-An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
-
-![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index 33145fa730..e0eb0f2d3b 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index 55e26da56a..a60bf1c77c 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -28,7 +30,10 @@ If an automatic build of code for a compiled language within your project fails,
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -113,25 +118,13 @@ If you split your analysis into multiple workflows as described above, we still
 
 If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Results differ between analysis platforms
-
-If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
-
-On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)."
-
-{% endif %}
-
 ### Error: "Server error"
 
 If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
 
 ### Error: "Out of disk" or "Out of memory"
-On very large projects,
 
-{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. If you encounter this issue, try increasing the memory on the runner.
 
 ### Warning: "git checkout HEAD^2 is no longer necessary"
 
@@ -146,29 +139,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index 014f175502..9b7795584d 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -19,7 +21,7 @@ topics:
 
 You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)."
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %} (available if your organization is taking part in the beta program), the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
 
 - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
 - {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
@@ -58,20 +60,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Example workflow that runs the ESLint analysis tool
@@ -82,7 +86,7 @@ This example workflow runs anytime commits are pushed to the repository. The act
 
 The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -90,23 +94,26 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### 더 읽을거리
diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index 8ae5b92b6c..4b6edc962b 100644
--- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ko-KR/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/ko-KR/content/github/getting-started-with-github/about-git-subtree-merges.md
index 15a0f8b3ea..1f3f320321 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 Typically, a subtree merge is used to contain a repository within a repository. The "subrepository" is stored in a folder of the main repository.
 
 The best way to explain subtree merges is to show by example. We will:
diff --git a/translations/ko-KR/content/github/getting-started-with-github/be-social.md b/translations/ko-KR/content/github/getting-started-with-github/be-social.md
index 628fec58f6..177b5cbbb5 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/be-social.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/be-social.md
@@ -38,6 +38,10 @@ Click **Watch** at the top of a repository to watch it.
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### Doing even more
 
 #### Creating pull requests
@@ -68,8 +72,8 @@ You're now connected to the {% data variables.product.product_name %} community.
 
 ![Star a project](/assets/images/help/stars/star-a-project.png)
 
-- [Set up Git](/articles/set-up-git)
-- [Create a repository](/articles/create-a-repo)
-- [Fork a repository](/articles/fork-a-repo)
+- "[Set up Git](/articles/set-up-git)"
+- "[Create a repository](/articles/create-a-repo)"
+- "[Fork a repository](/articles/fork-a-repo)"
 - **Be social**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/ko-KR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/ko-KR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index 14594fe791..b58adc4820 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 Every time you press <kbd>return</kbd> on your keyboard you insert an invisible character called a line ending. Different operating systems handle line endings differently.
 
-When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in OS X.
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
 
@@ -25,11 +25,11 @@ The `git config core.autocrlf` command is used to change how Git handles line en
 
 {% mac %}
 
-On OS X, you simply pass `input` to the configuration. 예시:
+On macOS, you simply pass `input` to the configuration. 예시:
 
 ```shell
 $ git config --global core.autocrlf input
-# Configure Git to ensure line endings in files you checkout are correct for OS X
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/ko-KR/content/github/getting-started-with-github/create-a-repo.md b/translations/ko-KR/content/github/getting-started-with-github/create-a-repo.md
index e1dcb37788..9ea2734452 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/create-a-repo.md
@@ -15,6 +15,8 @@ topics:
   - Accounts
 ---
 
+### Create a repository
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 You can store a variety of projects in {% data variables.product.product_name %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software.
@@ -29,7 +31,7 @@ You can store a variety of projects in {% data variables.product.product_name %}
 
 {% note %}
 
-**Note:** You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](http://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
+**Note:** You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/ko-KR/content/github/getting-started-with-github/fork-a-repo.md b/translations/ko-KR/content/github/getting-started-with-github/fork-a-repo.md
index 4da0fc56da..df51afff4b 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### About forks
+
 Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.
 
 #### Propose changes to someone else's project
@@ -34,7 +36,7 @@ For more information about applying open source principles to your organization'
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](http://choosealicense.com/)" at choosealicense.com.
+When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com.
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
@@ -154,5 +156,6 @@ You have now forked a repository, practiced cloning your fork, and configured an
 
 - "[Set up Git](/articles/set-up-git)"
 - "[Create a repository](/articles/create-a-repo)"
+- **Fork a repository**
 - "[Be social](/articles/be-social)"
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/ko-KR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/ko-KR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index 0341e58d6c..6d314e6118 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 These commands are very useful when interacting with [a remote repository](/github/getting-started-with-github/about-remote-repositories). `clone` and `fetch` download remote code from a repository's remote URL to your local computer, `merge` is used to merge different people's work together with yours, and `pull` is a combination of `fetch` and `merge`.
 
 ### Cloning a repository
diff --git a/translations/ko-KR/content/github/getting-started-with-github/git-workflows.md b/translations/ko-KR/content/github/getting-started-with-github/git-workflows.md
index f32df477d2..cbb4e138f6 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[GitHub flow](/github/collaborating-with-issues-and-pull-requests/github-flow)" and "[Understanding the GitHub flow](http://guides.github.com/overviews/flow/)" in the {% data variables.product.prodname_dotcom %} Guides.
+You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/ko-KR/content/github/getting-started-with-github/github-flow.md b/translations/ko-KR/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..0e6d473486
--- /dev/null
+++ b/translations/ko-KR/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: GitHub flow
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### Introduction
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### 빌드전 요구 사양
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### Create a pull request
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. Your pull request will update automatically.
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)."
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. For more information, see "[Addressing merge conflicts](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)."
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md b/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md
index 5c6f3197a9..84fed24cac 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ You can be simultaneously signed into mobile with one user account on {% data va
 
 You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}.
 
-To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
+To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}.
 
diff --git a/translations/ko-KR/content/github/getting-started-with-github/github-language-support.md b/translations/ko-KR/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/ko-KR/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md b/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md
index 1d68f78f32..5542290725 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 {% data variables.product.prodname_dotcom %} offers free and paid products. You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %}
 
 ### {% data variables.product.prodname_free_user %} for user accounts
@@ -99,14 +101,3 @@ In addition to the features available with {% data variables.product.prodname_te
 You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">Setting up a trial of {% data variables.product.prodname_ghe_cloud %}</a>."
 
 For more information about hosting your own instance of [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contact {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-{% data variables.product.prodname_ghe_one %} includes [{% data variables.product.prodname_enterprise %}](#github-enterprise), plus:
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %}
-- [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations)
-
-For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/ko-KR/content/github/getting-started-with-github/index.md b/translations/ko-KR/content/github/getting-started-with-github/index.md
index 4be4ef0d11..c85000a1e2 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/index.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md
index d8086b7096..d8a93d8f07 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/keyboard-shortcuts.md
@@ -36,12 +36,16 @@ Below is a list of some of the available keyboard shortcuts.
 | <kbd>g</kbd> <kbd>p</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | <kbd>g</kbd> <kbd>a</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
 | <kbd>g</kbd> <kbd>b</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."                                                                                                       |
-| <kbd>g</kbd> <kbd>w</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."                                                                                      |
+| <kbd>g</kbd> <kbd>w</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ### Source code editing
 
 | Keyboard shortcut                                               | 설명                                                             |
 | --------------------------------------------------------------- | -------------------------------------------------------------- |
+| <kbd>control b</kbd> or <kbd>command b</kbd>                    | Inserts Markdown formatting for bolding text                   |
+| <kbd>control i</kbd> or <kbd>command i</kbd>                    | Inserts Markdown formatting for italicizing text               |
+| <kbd>control k</kbd> or <kbd>command k</kbd>                    | Inserts Markdown formatting for creating a link                |
 | <kbd>e</kbd>                                                    | Open source code file in the **Edit file** tab                 |
 | <kbd>control f</kbd> or <kbd>command f</kbd>                    | Start searching in file editor                                 |
 | <kbd>control g</kbd> or <kbd>command g</kbd>                    | Find next                                                      |
diff --git a/translations/ko-KR/content/github/getting-started-with-github/learning-about-github.md b/translations/ko-KR/content/github/getting-started-with-github/learning-about-github.md
index 935030de96..2cfefb4683 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: Learning about GitHub
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/ko-KR/content/github/getting-started-with-github/set-up-git.md b/translations/ko-KR/content/github/getting-started-with-github/set-up-git.md
index 0f8e5599e0..11bb04203e 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/set-up-git.md
@@ -22,6 +22,8 @@ topics:
   - Accounts
 ---
 
+### Using Git
+
 To use Git on the command line, you'll need to download, install, and configure Git on your computer. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. For more information on {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation.{% endif %}
 
 If you want to work with Git locally, but don't want to use the command line, you can instead download and install the [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) client.  For more information, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)."
diff --git a/translations/ko-KR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/ko-KR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 9f04a9bb49..9c32bcc442 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ If you don't purchase {% data variables.product.prodname_enterprise %} or {% dat
 
 Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**. ![Buy Enterprise and Downgrade to Team buttons](/assets/images/help/organizations/finish-trial-buttons.png)
 6. Follow the prompts to enter your payment method, then click **Submit**.
 
diff --git a/translations/ko-KR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/ko-KR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index 057ee99fa2..9403ddc58b 100644
--- a/translations/ko-KR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/ko-KR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 In this example, we will cover all of the `git rebase` commands available, except for `exec`.
 
 We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
diff --git a/translations/ko-KR/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/ko-KR/content/github/importing-your-projects-to-github/about-github-importer.md
index 7422986d9e..b6514fd057 100644
--- a/translations/ko-KR/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/ko-KR/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: About GitHub Importer
-intro: 'If you have source code in Subversion, Mercurial, Team Foundation Server, or another Git repository, you can move it to GitHub using GitHub Importer.'
+intro: 'If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer.'
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ GitHub Importer is a tool that quickly imports source code repositories, includi
 
 During an import, depending on the version control system you're importing from, you can authenticate with your remote repository, update commit author attribution, and import repositories with large files (or remove large files if you don't want to use Git Large File Storage).
 
-| Import action                                                                                         | Subversion | Mercurial | Team Foundation Server |  Git  |
-|:----------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:|
-| Authenticate with remote repository                                                                   |   **X**    |   **X**   |         **X**          | **X** |
-| [Update commit author attribution](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   |         **X**          |       |
-| Move large files to [Git Large File Storage](/articles/about-git-large-file-storage)                  |   **X**    |   **X**   |         **X**          |       |
-| Remove large files from your repository                                                               |   **X**    |   **X**   |         **X**          |       |
+| Import action                                                                                         | Subversion | Mercurial | TFVC  |  Git  |
+|:----------------------------------------------------------------------------------------------------- |:----------:|:---------:|:-----:|:-----:|
+| Authenticate with remote repository                                                                   |   **X**    |   **X**   | **X** | **X** |
+| [Update commit author attribution](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   | **X** |       |
+| Move large files to [Git Large File Storage](/articles/about-git-large-file-storage)                  |   **X**    |   **X**   | **X** |       |
+| Remove large files from your repository                                                               |   **X**    |   **X**   | **X** |       |
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/ko-KR/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index 85b79b09f8..ede0c4aa4d 100644
--- a/translations/ko-KR/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/ko-KR/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Server, or another Git repository. You can also use these external tools to convert your project to Git.
+We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. You can also use these external tools to convert your project to Git.
 
 {% endif %}
 
@@ -32,12 +32,9 @@ We recommend these tools for converting Subversion repositories to Git:
 
 We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
 
-### Importing from Team Foundation Server
+### Importing from TFVC
 
-We recommend these tools for moving changes between Team Foundation Server and Git:
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
 
 {% tip %}
 
diff --git a/translations/ko-KR/content/github/index.md b/translations/ko-KR/content/github/index.md
index d97b60cc5d..cc43338794 100644
--- a/translations/ko-KR/content/github/index.md
+++ b/translations/ko-KR/content/github/index.md
@@ -36,7 +36,6 @@ versions:
 {% link_in_list /collaborating-with-issues-and-pull-requests %}
 
 {% link_in_list /managing-your-work-on-github %}
-{% link_in_list /developing-online-with-codespaces %}
 
 {% link_in_list /searching-for-information-on-github %}
 
@@ -57,7 +56,6 @@ versions:
 
 {% link_in_list /extending-github %}
 
-{% link_in_list /supporting-the-open-source-community-with-github-sponsors %}
 {% link_in_list /finding-talent-with-github-jobs %}
 {% link_in_list /working-with-github-support %}
 {% link_in_list /understanding-how-github-uses-and-protects-your-data %}
diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
index d0fcba272c..a02c9d2fdf 100644
--- a/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
+++ b/translations/ko-KR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
@@ -26,7 +26,7 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_
 
 1. Browse to the file in your repository that you want to delete.
 2. At the top of the file, click
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index a9f3b4855b..3b84578a37 100644
--- a/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/ko-KR/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### About navigating code on {% data variables.product.prodname_dotcom %}
 
 Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). The following languages are supported:
diff --git a/translations/ko-KR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/ko-KR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index 32b79170eb..4400a25fd6 100644
--- a/translations/ko-KR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/ko-KR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -38,7 +38,7 @@ versions:
 
 After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}.
 
-To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)."{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archived objects are purged after three months.{% endif %}
+To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archived objects are purged after three months.{% endif %}
 
 {% note %}
 
diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index 095b13a1cd..ffee9964f5 100644
--- a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,12 +1,14 @@
 ---
 title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
+intro: '{% data variables.product.product_name %} sends {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
 versions:
   enterprise-server: <=2.22
 topics:
   - Security
 ---
- 
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
 ### About vulnerable dependencies
 
 {% data reusables.repositories.a-vulnerability-is %}
@@ -15,12 +17,10 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 ### Detection of vulnerable dependencies
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
 
-{% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
+- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
 {% data reusables.repositories.dependency-review %}
 
@@ -32,7 +32,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
 ### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
 {% else %}
 ### Security alerts for vulnerable dependencies
@@ -40,25 +40,11 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% 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.
-
-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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
-
-{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 When
 {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-For repositories where
-{% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 When
 {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
@@ -70,30 +56,17 @@ When
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Access to {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+You can see all of the alerts that affect a particular project in the repository's dependency graph.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 By default, we notify people with admin permissions in the affected repositories about new
-{% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
-{% endif %}
+{% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 We send security alerts to people with admin permissions in the affected repositories by default.
 {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-You can also see all the
-{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### 더 읽을거리
-
-- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index aa43b807f6..9cdfdb4cf8 100644
--- a/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,20 +1,18 @@
 ---
 title: Configuring notifications for vulnerable dependencies
 shortTitle: Configuring notifications
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+intro: 'Optimize how you receive notifications about  {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
 versions:
   enterprise-server: '>=2.21 <=2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies for the current version of this article -->
+
 ### About notifications for vulnerable dependencies
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
 Your site administrator needs to enable security alerts for vulnerable dependencies for
@@ -28,14 +26,14 @@ By default, if your site administrator has configured email for notifications on
 
 {% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configuring notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
 
 You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 {% else %}
   ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png)
@@ -47,11 +45,11 @@ You can configure notification settings for yourself or your organization from t
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
 
 ### How to reduce the noise from notifications for vulnerable dependencies
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+If you are concerned about receiving too many notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md
index cea165b9ad..b6e7b7ecfe 100644
--- a/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### Table of Contents
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index 8f5f7ecb65..d6cd9d9227 100644
--- a/translations/ko-KR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index 3f293a4301..d8c0e532cf 100644
--- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -26,13 +26,9 @@ You can choose to receive ongoing updates about specific activity on {% data var
 You can choose to subscribe to notifications for:
 - A conversation in a specific issue, pull request, or gist.
 - All activity in a repository or team discussion.
-- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}.
-{% if currentVersion == "free-pro-team@latest" %}
-- Issues, pulls requests, releases and discussions (if enabled) in a repository.
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- Releases in a repository.
-{% endif %}
+- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**.
 
diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
index c6dd0e7b32..780e0f22ec 100644
--- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
+++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
@@ -58,7 +58,7 @@ In addition, you can receive and triage notifications on your mobile device with
 
 #### Benefits of using an email client for notifications
 
-One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
+One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
 
 Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.
 
@@ -69,15 +69,16 @@ Email notifications also allow flexibility with the types of notifications you r
 When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
 
 To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
 #### Configuring notifications
 {% endif %}
 You can configure notifications for a repository on the repository page, or on your watching page.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 #### About custom notifications
-{% data reusables.notifications-v2.custom-notifications-beta %}
-You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository.
+You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events (
+{% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository.
 {% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
 
 #### Participating in conversations
@@ -159,19 +160,22 @@ If "Automatically watch repositories" is disabled, then you will not automatical
 
 ### Configuring your watch settings for an individual repository
 
-You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
+You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 2. In the upper-right corner, click the "Watch" drop-down menu to select a watch option.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
    ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
-{% data reusables.notifications-v2.custom-notifications-beta %}
+
 The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
 
+{% if currentVersion == "free-pro-team@latest" %}
+   ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png)
+{% else %}
    ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2.png)
+{% endif %}
 
 If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
 
diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index a5ea3dd86a..820719b15f 100644
--- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -57,13 +57,13 @@ When you unwatch a repository, you unsubscribe from future updates from that rep
 {% data reusables.notifications.access_notifications %}
 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-    - unwatch a repository
-    - only watch releases for a repository
-    - ignore all notifications for a repository
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-    - unwatch a repository
-    - ignore all notifications for a repository
-    - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled)
-{% endif %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
+    - Unwatch a repository
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    - Unwatch a repository
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index 6c850a2ea1..58625da17d 100644
--- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -35,10 +35,10 @@ When your inbox has too many notifications to manage, consider whether you have
 For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
 
 To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
 
 {% endtip %}
 {% endif %}
@@ -67,16 +67,15 @@ Many people forget about repositories that they've chosen to watch in the past.
 
 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
   ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" %}when there are updates to issues, pull requests, releases or discussions (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
 
   When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
 
diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/ko-KR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index 070d3289f6..3d8c876f22 100644
--- a/translations/ko-KR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/ko-KR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ Query parameters are optional parts of a URL you can customize to share a specif
 
 You must have the proper permissions for any action to use the equivalent query parameter. For example, you must have permission to add a label to an issue to use the `labels` query parameter.
 
-If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a 404 error page.
+If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page.
 
 ### Supported query parameters
 
diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/ko-KR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index dc34134e43..591d00a2aa 100644
--- a/translations/ko-KR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/ko-KR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. Choose one of these options:
     - To create a new milestone, click **New Milestone**. ![New milestone button](/assets/images/help/repository/new-milestone.png)
     - To edit a milestone, next to the milestone you want to edit, click **Edit**. ![Edit milestone option](/assets/images/help/repository/edit-milestone.png)
-5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**.
+5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
 
 ### Deleting milestones
 
diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/ko-KR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index 79f4128a26..717f19d4ae 100644
--- a/translations/ko-KR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/ko-KR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ After you disable repository project boards in an organization, it won't be poss
 
 When you disable project boards, you will no longer see project board information in timelines or [audit logs](/articles/reviewing-the-audit-log-for-your-organization/).
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects":
     - To disable organization-wide project boards, unselect **Enable projects for the organization**.
     - To disable repository project boards in the organization, unselect **Enable projects for all repositories**. ![Checkboxes to disable projects for an organization or for all of an organization's repositories](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/ko-KR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index aedfd88d1e..11605dd076 100644
--- a/translations/ko-KR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/ko-KR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: File attachments on issues and pull requests
-intro: 'When you open issue or update a pull request, you can use issue attachments to upload images of proposed features or screenshots of bugs.'
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -14,7 +14,7 @@ topics:
 
 {% warning %}
 
-**Warning:** If you add an image to a pull request or issue comment, anyone can view the anonymized image URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive images private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized image URLs](/articles/about-anonymized-image-urls)".{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ To attach a file to an issue or pull request conversation, drag and drop it into
 
 {% endtip %}
 
-The maximum size for files is 25MB and the maximum size for images is 10MB.
-{% if currentVersion == "free-pro-team@latest" %}
-Videos can be up to 100 MB in size if the repository is owned by a user or organization on a paid GitHub plan.
-
-{% note %}
-
-**Note:** Support for video attachments is currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 We support these files:
 
@@ -49,7 +43,7 @@ We support these files:
 * Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
 * Text files (*.txt*)
 * PDFs (*.pdf*)
-* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" %}
+* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * Video (*.mp4*, *.mov*){% endif %}
 
 ![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md b/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md
index 5dde002615..fc24fc2454 100644
--- a/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md
+++ b/translations/ko-KR/content/github/managing-your-work-on-github/managing-labels.md
@@ -49,6 +49,8 @@ Anyone with read access to a repository can view and search the repository’s l
 
 Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later.
 
+Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)."
 {% endif %}
diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/ko-KR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index d30e40396b..cb2b927ba0 100644
--- a/translations/ko-KR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/ko-KR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ You can sort any filtered view by:
 * The least commented issues or pull requests
 * The newest updated issues or pull requests
 * The oldest updated issues or pull requests
-* The most added [reaction](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) on issues or pull requests
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. In the upper-right corner, select the Sort drop-down menu. ![Using the Sort drop-down tab](/assets/images/help/issues/issues_sort_dropdown.png)
+1. In the upper-right corner, select the Sort drop-down menu. ![Using the Sort drop-down tab](/assets/images/help/issues/issues_sort_dropdown.png)
 
 To clear your sort selection, click **Sort** > **Newest**.
 
diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-code.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-code.md
index b6442ea271..606603edc0 100644
--- a/translations/ko-KR/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ You can use the `path` qualifier to search for source code that appears at a spe
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in an <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>). |
 
 ### Search by language
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-You can search for code based on what language it's written in.
+You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | Qualifier                  | 예시                                                                                                                                                                                                      |
 | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 7993f58f1b..bebd87b077 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)."
+
+{% endnote %}
 
 If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
 
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index ba9ae3ca3a..0d424e4a4d 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### 더 읽을거리
 
-- "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)"
-- "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)"
+- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index 86893eac64..f7fc24aa7a 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,26 +16,11 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %}
 
 ### About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
 
-We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_dotcom_the_website %}:
-
-- **Committers** is the number of committers who contributed to at least one private repository in an organization and who use a seat in your license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
-- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
-
-If there are no unique committers, this means that all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
-
-{% note %}
-
-**Note:** The total number of seats used in your license is not the sum of either the committers or the unique committers to each repository or organization. This is because there are people who contribute to multiple repositories or organizations. The number of seats used is measured across the whole enterprise account to ensure that each person is counted only once regardless of how many repositories or organizations they contribute to.
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### Managing your license usage for {% data variables.product.prodname_GH_advanced_security %}
 
-When you enable {% data variables.product.prodname_GH_advanced_security %} for a single repository, or for all repositories in an organization, {% data variables.product.company_short %} shows how many extra seats this will use and prompts you for confirmation. If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up. This makes it easy to understand the impact of your changes on the use of your license.
-
-If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available. If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.
-
-As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal.
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
 You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)."
 
@@ -43,9 +28,4 @@ For more information on viewing license usage, see "[Viewing your {% data variab
 
 ### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license
 
-When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify:
-
-- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company.
-- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced.
-
-When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index 3e5505adad..192efaf986 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
 ### Adding information to your personal account's receipts
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### Adding information to your organization's receipts
@@ -40,9 +40,9 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index ddc31481f1..a6c67402b4 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ We don't provide invoicing or support purchase orders for personal accounts. We
 ### Updating your personal account's payment method
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### Updating your organization's payment method
@@ -38,9 +39,10 @@ We don't provide invoicing or support purchase orders for personal accounts. We
 
 If your organization is outside of the US or if you're using a corporate checking account to pay for {% data variables.product.product_name %}, PayPal could be a helpful method of payment.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index 075e3502f4..983c92cae7 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 ### Canceling an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### Canceling a free trial for an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index d276d19b9c..878bc94a1e 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 ### Changing the duration of your personal account's billing cycle
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. Under "Billing overview", click **Change plan**. ![Billing overview change plan button](/assets/images/help/billing/billing_overview_change_plan.png)
 5. At the top right corner, click **Switch to monthly billing** or **Switch to yearly billing**. ![Billing information section](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index 433a85414a..f343f6d145 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ If you already have a personal {% data variables.product.prodname_dotcom %} user
 
 ### Step 3: Upgrade the organization to a yearly paid subscription
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (You can add more seats to the organization in the next step.)
 6. Under "Upgrade summary", select **Pay yearly** to pay for the organization yearly. ![Radio button for yearly billing](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. Under "Pay with", type your credit card information. ![Form for entering credit card information](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. Click **Update credit card**.
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### Step 4: Upgrade the number of paid seats in the organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index 4f47eaeb91..b0dad06edb 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -16,8 +16,7 @@ When you downgrade your number of data packs, your change takes effect on your n
 ### Downgrading storage and bandwidth for a personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
@@ -25,10 +24,8 @@ When you downgrade your number of data packs, your change takes effect on your n
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 75da2d942f..214cc3b68c 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ When you downgrade an app, your subscription remains active until the end of you
 ### Downgrading an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ When you downgrade an app, your subscription remains active until the end of you
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index d536bb1abc..6714a54f7f 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ When you downgrade your user account or organization's subscription, pricing and
 If you downgrade your user account from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, the account will lose access to advanced code review tools on private repositories. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Use the **Edit** drop-down and click **Downgrade to Free**. ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
 5. Read the information about the features your user account will no longer have access to on your next billing date, then click **I understand. Continue with downgrade**. ![Continue with downgrade button](/assets/images/help/billing/continue-with-downgrade.png)
 
 If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, remove or update your DNS records before downgrading from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
@@ -45,12 +44,10 @@ If you downgrade your organization from {% data variables.product.prodname_team
 
 If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Use the **Edit** drop-down and click the downgrade option you want. ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### Downgrading an organization's subscription with legacy per-repository pricing
@@ -59,10 +56,9 @@ If you downgrade your organization from {% data variables.product.prodname_ghe_c
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**. ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png)
 1. Under "Billing/Plans",  next to the plan you want to change, click **Downgrade**. ![Downgrade button](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. Enter the reason you're downgrading your account, then click **Downgrade plan**. ![Text box for downgrade reason and downgrade button](/assets/images/help/billing/downgrade-plan-button.png)
@@ -74,12 +70,10 @@ To reduce the number of paid seats your organization uses, you can remove member
 - "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
 - "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Use the **Edit** drop-down and click **Remove seats**. ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
 1. Under "Remove seats", select the number of seats you'd like to downgrade to. ![remove seats option](/assets/images/help/billing/remove-seats-amount.png)
 1. Review the information about your new payment on your next billing date, then click **Remove seats**. ![remove seats button](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index c0c11e3fc0..be35125eab 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ Because you have not enabled overages, your next attempt to create a workflow ar
 Anyone can manage the spending limit for {% data variables.product.prodname_actions %} for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Anyone can manage the spending limit for {% data variables.product.prodname_acti
 
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise owners and billing managers can manage the spending limit for {% data
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "
-{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**.
-  ![Cost management tab](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index 2944ea140f..8b6ed40fe3 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ Because you have not enabled overages, your next attempt to publish a version of
 Anyone can manage the spending limit for {% data variables.product.prodname_registry %} for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Anyone can manage the spending limit for {% data variables.product.prodname_regi
 
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise owners and billing managers can manage the spending limit for {% data
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "
-{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**.
-  ![Cost management tab](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index 2a311494f0..3a223dc1ec 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ If you're paying for your {% data variables.product.product_name %} subscription
 ### Removing your personal account's payment method
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ If you're paying for your {% data variables.product.product_name %} subscription
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index 17e8c5b6e8..7b7b694bc2 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### Updating your organization's credit card
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. Type your new credit card information in the secure form. ![Credit card information form](/assets/images/help/settings/creditcard-billing-form.png)
-1. Click **Update credit card** or **Save credit card**.
+1. Under "Payment method", click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index 61cf642bc6..94456eca76 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ Your organization's billing email is where {% data variables.product.product_nam
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Under **Billing email**, type a valid email address. The email does not need to be unique to the organization account. ![Billing email textbox](/assets/images/help/settings/org-billing-email.png)
 5. To confirm your changes, click **Update profile**. ![Update profile button](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ If you have users that want to receive billing reports, you can add their email
 #### Adding a recipient for billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Billing management", to the right of "Email recipients", click **Add**. ![Add recipient](/assets/images/help/billing/billing-add-email-recipient.png)
 1. Type the email address of the recipient, then click **Add**. ![Add recipient modal](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ If you have users that want to receive billing reports, you can add their email
 One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected.
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Billing management", find the email address you want to set as the primary recipient.
 1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**. ![Mark primary recipient](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### Removing a recipient from billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Email recipients", find the email address you want to remove.
 1. For the user's entry in the list, click **Edit**. ![Edit recipient](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. To the right of the email address, use the "Edit" drop-down menu, and click *Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. Review the confirmation prompt, then click **Remove**.
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index a162509608..189ffd9073 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### Purchasing additional storage and bandwidth for a personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index ce93275910..6fdffd5f75 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,11 +22,9 @@ topics:
 
 ### Upgrading an organization's number of paid seats
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -35,10 +33,8 @@ After you add seats, the payment method on file for the organization will be cha
 
 ### Downgrading an organization's number of paid seats to free
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 6bd3483a28..7eca07d340 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
 ### Upgrading an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ When you upgrade an app, your payment method is charged a prorated amount based
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index 6260f208ff..fd1a0f6a4c 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Next to "
-{% data variables.product.prodname_free_user %}", click **Upgrade**.
-  ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ If you'd like to use an enterprise account with {% data variables.product.prodna
 
 If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ If you'd like additional users to have access to your {% data variables.product.
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**. ![Edit drop-down menu](/assets/images/help/billing/per-user-upgrade-button.png)
 6. To the right of "Advanced tools for teams", click **Upgrade now**. ![Upgrade now button](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index ecd19216bf..4445281d8e 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ When you cancel a pending change, your subscription will not change on your next
 ### Viewing and managing pending changes to your personal account's subscription
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### Viewing and managing pending changes to your organization's subscription
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index a81b7c56f5..33f9f51414 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### Viewing storage and bandwidth usage for a personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Viewing storage and bandwidth usage for an organization
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### 더 읽을거리
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index a12363a682..6bff6d36f6 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ You can also view the billable job execution minutes for an individual workflow
 Anyone can view {% data variables.product.prodname_actions %} usage for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ Anyone can view {% data variables.product.prodname_actions %} usage for their ow
 
 Organization owners and billing managers can view {% data variables.product.prodname_actions %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_actions %} usage in the organization billing page.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index 151c1b0164..27b5e7d242 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,24 +1,24 @@
 ---
 title: Viewing your GitHub Advanced Security usage
-intro: 'You can view and manage usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
-permissions: 'Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
   free-pro-team: '*'
 ---
 
-Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Periodically you should check that your use is within your license capacity. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
 
-### Viewing and managing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
+### Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
 
-You can check how many seats your license includes and how many of them are currently used on the "Enterprise licensing" page.
+You can check how many seats your license includes and how many of them are currently used.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
-4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png)
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
 5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
 6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[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/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index 739d4f10da..dc11426e97 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 Anyone can view {% data variables.product.prodname_registry %} usage for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ Anyone can view {% data variables.product.prodname_registry %} usage for their o
 
 Organization owners and billing managers can view {% data variables.product.prodname_registry %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_registry %} usage in the organization billing page.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index 7cf7a65ce0..d1880d2822 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### Viewing receipts for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index 241b2c8038..adf50b3f06 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### Finding your personal account's next billing date
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Finding your organization's next billing date
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### 더 읽을거리
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index ea9b3d4b19..791e958b09 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -36,5 +36,5 @@ After you disconnect your Azure subscription from your enterprise account, your
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
+1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**.
 1. Review the prompt, then click **Remove**.
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index 024664c550..f070ac7de3 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -48,3 +48,19 @@ You can disable all workflows for an enterprise or set a policy that configures
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### Setting the permissions of the `GITHUB_TOKEN` for your enterprise
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. Click **Save** to apply the settings.
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md
index a60b8b14a8..fe74fb917f 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..39850b1dd2
--- /dev/null
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: Restricting email notifications for your enterprise account
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### About email restrictions for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restricting email notifications for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..fa4be47e6b
--- /dev/null
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About domain verification
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index 1c14fb7f70..7234f3f52d 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -20,6 +20,15 @@ When you enable SAML single sign-on for your enterprise account, each enterprise
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index 85d71fa6a2..43593e3638 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories to the top of the page.
 
-{% if currentVersion == "free-pro-team@latest" %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+{% if currentVersion == "free-pro-team@latest" %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![Sample verified organization profile page](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index ced5bebd13..c70afef51c 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ If you select the "Busy" option, when people @mention your username, assign you
 
 When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
 
-| Badge                                                           | Program                                                              | 설명                                                                                                                                                                                                                                                                                                                                                         |
-| --------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **Developer Program Member**                                         | If you're a registered member of the GitHub Developer Program, building an app with the GitHub API, you'll get a Developer Program Member badge on your profile. For more information on the GitHub Developer Program, see [GitHub Developer](/program/).                                                                                                  |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **GitHub Sponsor**                                                   | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a GitHub Sponsor badge on your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)."                            |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                              | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)."                                                     |
+| Badge                                                                                                                    | Program                                                              | 설명                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter Contributor badge icon](/assets/images/help/profile/badge-mars-2020-small.png)                    | **Mars 2020 Helicopter Contributor**                                 | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
+| ![Arctic Code Vault Contributor badge icon](/assets/images/help/profile/badge-arctic-code-vault-small.png)               | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were part of the program. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com).                                                                                                                                                                                      |
+| ![{% data variables.product.prodname_dotcom %} Sponsor badge icon](/assets/images/help/profile/badge-sponsors-small.png) | **{% data variables.product.prodname_dotcom %} Sponsor**             | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)."                                                                                                                                                                                                                 |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                              | **Developer Program Member**                                         | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% data variables.product.prodname_dotcom %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/).                                                                                                                                                                                                                                                                                   |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                                     | **Pro**                                                              | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)."                                                                                                                                                                                                                                                                                                                                                          |
 
 ### Disabling badges on your profile
 
-You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO and {% data variables.product.prodname_arctic_vault %} badges.
+You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
 
 {% data reusables.user_settings.access_settings %}
-2. Under "Profile settings", deselect the badge you want you disable. ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. Under "Profile settings", deselect the badge you want you disable. ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/profile-badge-settings.png)
 3. Click **Update preferences**.
 
 {% endif %}
 
+### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
+
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+
+| {% data variables.product.prodname_dotcom %} Repository                       | 버전        | Tag                                                                                                        |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.2       | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### 더 읽을거리
 
 - "[About your profile](/articles/about-your-profile)"
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index 984e3d8dcd..6ca1acce7c 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. If you'd like to add a new email address to set as your primary email address, under "Add email address", type a new email address and click **Add**. ![Add another email address button](/assets/images/help/settings/add_another_email_address.png)
 4. Under "Primary email address", use the drop-down menu to click the email address you'd like to set as your primary email address, and click **Save**. ![Set as primary button](/assets/images/help/settings/set_as_primary_email.png)
 5. To remove the old email address from your account, next to the old email, click
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}.
 {% if currentVersion == "free-pro-team@latest" %}
 6. Verify your new primary email address. Without a verified email address, you won't be able to use all of
 {% data variables.product.product_name %}'s features. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index 544c8f70ce..c5ee3d510d 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -1,23 +1,20 @@
 ---
 title: Managing your theme settings
-intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode.'
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
 versions:
   free-pro-team: '*'
 topics:
   - Accounts
 ---
 
-{% note %}
-
-**Note:** Theme settings is currently in beta and subject to change.
-
-{% endnote %}
-
-For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions.
+For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
 
 {% data reusables.user_settings.access_settings %}
 1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
-1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. Under "Theme mode", select the drop-down menu, then click a theme preference. ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Click the theme you'd like to use.
+    - If you chose a single theme, click a theme. ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - If you chose to follow your system settings, click a day theme and a night theme. ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### 더 읽을거리
 
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
index 5eec8af1a9..6bed6e9ce8 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
@@ -32,7 +32,7 @@ The repository owner has full control of the repository. In addition to the acti
 | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %}                                                                                                                  |                                                                                                                                                                                                                                                                                                                                |
 | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)"                                                                |                                                                                                                                                                                                                                                                                                                                |
 | Change the visibility of the repository                                                                                                                                                                                      | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %}
-| Limit interactions with the repository                                                                                                                                                                                       | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Limit interactions with the repository                                                                                                                                                                                       | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename a branch, including the default branch                                                                                                                                                                                | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Merge a pull request on a protected branch, even if there are no approving reviews                                                                                                                                           | "[About protected branches](/github/administering-a-repository/about-protected-branches)"                                                                                                                                                                                                                                      |
@@ -70,7 +70,7 @@ Collaborators can also perform the following actions.
 
 | 동작                                                                                        | More information                                                                                                                                                                                                                                                                                         |
 |:----------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Fork the repository                                                                       | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Fork the repository                                                                       | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename a branch other than the default branch                                             | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                                                                |
diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index 40843ec701..c662e93605 100644
--- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ While forks of private repositories are deleted when a collaborator is removed,
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. To the right of the collaborator you want to remove, click
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
   ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. In the left sidebar, click **Collaborators & teams**. ![Collaborators tab](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/ko-KR/content/github/site-policy/github-candidate-privacy-policy.md b/translations/ko-KR/content/github/site-policy/github-candidate-privacy-policy.md
index fe8605d913..f1e55a6457 100644
--- a/translations/ko-KR/content/github/site-policy/github-candidate-privacy-policy.md
+++ b/translations/ko-KR/content/github/site-policy/github-candidate-privacy-policy.md
@@ -3,8 +3,8 @@ title: GitHub Candidate Privacy Policy
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Effective Date: March 8, 2021
diff --git a/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md
index 8ab1fde8fc..9ad4639a51 100644
--- a/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,6 +9,8 @@ topics:
   - Legal
 ---
 
+_These terms apply to 1) GitHub.com (non-Enterprise) customers who have accepted the Corporate Terms of Service, and 2) Enterprise customers who licensed the Service prior to January 4, 2021. Enterprise customers who purchase Products or Services after that date are directed to https://github.com/enterprise-legal for current terms._
+
 THANK YOU FOR CHOOSING GITHUB FOR YOUR COMPANY’S BUSINESS NEEDS. PLEASE READ THIS AGREEMENT CAREFULLY AS IT GOVERNS USE OF THE PRODUCTS (AS DEFINED BELOW), UNLESS GITHUB HAS EXECUTED A SEPARATE WRITTEN AGREEMENT WITH CUSTOMER FOR THAT PURPOSE. BY CLICKING ON THE "I AGREE" OR SIMILAR BUTTON OR BY ACCESSING THE PRODUCTS, CUSTOMER ACCEPTS ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF CUSTOMER IS ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, CUSTOMER REPRESENTS THAT IT HAS THE LEGAL AUTHORITY TO BIND THE COMPANY OR OTHER LEGAL ENTITY TO THIS AGREEMENT.
 
 ### GitHub Corporate Terms of Service
diff --git a/translations/ko-KR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/ko-KR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
index fd9c1568fb..18a2ec5da2 100644
--- a/translations/ko-KR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
+++ b/translations/ko-KR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insights and data protection for your organization
 intro: '{% data variables.product.prodname_insights %} analyzes your {% data variables.product.prodname_ghe_server %} data. This data could include personal data of individuals in your organization who may have the right to understand how such personal data is being used.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
   - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
@@ -14,8 +13,6 @@ topics:
   - Legal
 ---
 
-For more information about the terms that govern {% data variables.product.prodname_insights %}, see your {% data variables.product.prodname_ghe_one %} subscription agreement.
-
 For the avoidance of doubt, none of the foregoing information should be considered legal advice provided by {% data variables.product.prodname_dotcom %}. You are responsible for securing your own legal analysis of the information provided herein and for your compliance with privacy and data protection laws. It is up to you whether to use {% data variables.product.prodname_insights %} to process your employees’ and users’ data, and if you do so, you are solely responsible for conducting such processing in compliance with applicable law.
 
 ### The organization’s roles and responsibilities
diff --git a/translations/ko-KR/content/github/site-policy/github-privacy-statement.md b/translations/ko-KR/content/github/site-policy/github-privacy-statement.md
index 2a1f528005..0d4ec87736 100644
--- a/translations/ko-KR/content/github/site-policy/github-privacy-statement.md
+++ b/translations/ko-KR/content/github/site-policy/github-privacy-statement.md
@@ -64,7 +64,7 @@ We require some basic information at the time of account creation. When you crea
 ##### Payment information
 If you sign on to a paid Account with us, send funds through the GitHub Sponsors Program, or buy an application on GitHub Marketplace, we collect your full name, address, and credit card information or PayPal information. Please note, GitHub does not process or store your credit card information or PayPal information, but our third-party payment processor does.
 
-If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
+If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
 
 ##### Profile information
 You may choose to give us more information for your Account profile, such as your full name, an avatar which may include a photograph, your biography, your location, your company, and a URL to a third-party website. This information may include User Personal Information. Please note that your profile information may be visible to other Users of our Service.
diff --git a/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md
index ca969b288e..73fe607515 100644
--- a/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md
+++ b/translations/ko-KR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md
@@ -3,8 +3,8 @@ title: GitHub's Notice about the California Consumer Privacy Act
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Effective January 1, 2020
diff --git a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index 6941e8dcfc..a04ea64d75 100644
--- a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -7,25 +7,19 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
+
 ### Dependency graph availability
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+The dependency graph is available for every repository that defines dependencies in a supported package ecosystem using a supported file format.
 
 {% data reusables.repositories.enable-security-alerts %}
 
 ### About the dependency graph
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
-
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
-
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch,
-{% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated. For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
 
 ### Dependencies included
 
@@ -34,41 +28,32 @@ The dependency graph includes all the dependencies of a repository that are deta
 - Direct dependencies, that are explicitly defined in a manifest or lock file
 - Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
-
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+The dependency graph identifies indirect dependencies.
 
 ### Using the dependency graph
 
 You can use the dependency graph to:
 
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
+- Explore the repositories your code depends on. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."
+- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
 
 ### Enabling the dependency graph
 
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository.
 
 ### Supported package ecosystems
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.
+
+The ecosystems listed below are supported for the dependency graph and {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
 
-{% if currentVersion == "free-pro-team@latest" %}The ecosystems listed below are supported for the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot_security_updates %}.{% endif %}
-|
-{% if currentVersion ver_gt "enterprise-server@2.21" %}The ecosystems listed below are supported for the dependency graph and {% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 | Package manager | 다국어 지원                           | Recommended formats                                    | All supported formats                                                     |
 | --------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
 | Composer        | PHP                              | `composer.lock`                                        | `composer.json`, `composer.lock`                                          |
@@ -88,7 +73,4 @@ The recommended formats explicitly define which versions are used for all direct
 ### 더 읽을거리
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
diff --git a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index a1a89c5622..700f1c7a6d 100644
--- a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -7,29 +7,20 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
 
-The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+The dependency graph shows the dependencies of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. Optionally, under "Dependency graph", click **Dependents**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### Dependencies view
 
-{% if currentVersion == "free-pro-team@latest" %}
-Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies on public repositories hosted on
-{% data variables.product.product_name %}, you can also click a dependency to view the repository. Dependencies on private repositories, private packages, or unrecognized files are shown in plain text.
-
-If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}.
-
-![의존성 그래프](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
 Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to
 {% data variables.product.prodname_dependabot_alerts %}.
@@ -57,59 +48,8 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### Dependents view
-
-For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
-
-![의존도 그래프](/assets/images/help/graphs/dependents_graph.png)
-
-### Enabling and disabling the dependency graph for a private repository
-
-Repository administrators can enable or disable the dependency graph for private repositories.
-
-You can also enable or disable the dependency graph 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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
-
-### Changing the "Used by" package
-
-If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
-
-The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
-
-!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png)
-
-Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
-
-The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### Troubleshooting the dependency graph
 
 If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.
 
-{% if currentVersion == "free-pro-team@latest" %}
-If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a
-{% data variables.product.prodname_enterprise %} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %}
-
 If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.
-
-### 더 읽을거리
-
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)"
-{% endif %}
diff --git a/translations/ko-KR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/ko-KR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index 5e6495b846..c0e774954d 100644
--- a/translations/ko-KR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/ko-KR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: About GitHub Premium Support for GitHub Enterprise Cloud
-intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_one %} customers.'
+intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_ghe_cloud %} customers.'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
diff --git a/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md
index 819ac47d2f..0f3e6b98fe 100644
--- a/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/ko-KR/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ For more information on creating links, see "[Basic writing and formatting synta
 
 ### Issues and pull requests
 
-Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links. For more information, see "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)."
+Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links.
 
 {% note %}
 
diff --git a/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index a280bf093c..ae46cbdc22 100644
--- a/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/ko-KR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -23,7 +23,7 @@ To create a heading, add one to six `#` symbols before your heading text. The nu
 
 ### Styling text
 
-You can indicate emphasis with bold, italic, or strikethrough text.
+You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files.
 
 | Style                  | Syntax             | Keyboard shortcut   | 예시                                       | Output                                 |
 | ---------------------- | ------------------ | ------------------- | ---------------------------------------- | -------------------------------------- |
@@ -205,6 +205,10 @@ Content attachments will not be displayed for URLs that are part of a markdown l
 
 For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."
 
+### Uploading assets
+
+You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and `.md` files in your repository.
+
 ### Using emoji
 
 You can add emoji to your writing by typing `:EMOJICODE:`.
diff --git a/translations/ko-KR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/ko-KR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index 48b3e74e7c..bb60ed01d3 100644
--- a/translations/ko-KR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/ko-KR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### Syntax highlighting
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 You can add an optional language identifier to enable syntax highlighting in your fenced code block.
 
diff --git a/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 690cce63b0..9b8851f802 100644
--- a/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ Return type fields:
 
 ## 검색
 
-Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see ["Queries](/graphql/reference/queries#searchresultitemconnection)."
+Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/ko-KR/content/graphql/overview/breaking-changes.md b/translations/ko-KR/content/graphql/overview/breaking-changes.md
index 60e198a093..30ae5ee702 100644
--- a/translations/ko-KR/content/graphql/overview/breaking-changes.md
+++ b/translations/ko-KR/content/graphql/overview/breaking-changes.md
@@ -27,7 +27,7 @@ We'll announce upcoming breaking changes at least three months before making cha
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> A change will be made to <code>{{ change.location }}</code>.
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> A change will be made to <code>{{ change.location }}</code>.
 
 <p><b>Description:</b> {{ change.description }}</p>
 
diff --git a/translations/ko-KR/content/graphql/overview/explorer.md b/translations/ko-KR/content/graphql/overview/explorer.md
index b4d07c0939..1d2d21729a 100644
--- a/translations/ko-KR/content/graphql/overview/explorer.md
+++ b/translations/ko-KR/content/graphql/overview/explorer.md
@@ -9,6 +9,6 @@ versions:
   github-ae: '*'
 layout: graphql-explorer
 topics:
-  - api
+  - API
 ---
 
diff --git a/translations/ko-KR/content/graphql/reference/input-objects.md b/translations/ko-KR/content/graphql/reference/input-objects.md
index 944e9c0f8b..72fe36ae79 100644
--- a/translations/ko-KR/content/graphql/reference/input-objects.md
+++ b/translations/ko-KR/content/graphql/reference/input-objects.md
@@ -19,6 +19,5 @@ For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) tak
 
 For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index 1686366af2..2ccf7e0b2a 100644
--- a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: Metrics available with GitHub Insights
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %} includes a variety of metrics to give you visibility into your team''s software delivery process.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index 1d4e6eb413..aee7193685 100644
--- a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Navigating between GitHub Enterprise and GitHub Insights
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index b8f8cfd53d..7c5c5ea881 100644
--- a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Setting your timezone for GitHub Insights
 intro: 'You can set the timezone for metrics you view in {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 65f7322257..9829c35a69 100644
--- a/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/ko-KR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing key metrics and reports
 intro: You can view and filter key metrics and reports to help you understand and improve your software delivery process through data.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index 4539d67e19..c45d03609c 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: About data in GitHub Insights
 intro: 'The data included in {% data variables.product.prodname_insights %} metrics is highly customizable.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index 8583463457..942e137fc1 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: About GitHub Insights
 intro: '{% data variables.product.prodname_insights %} provides metrics and analytical reports to help engineering teams understand and improve their software delivery process.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
index d383b614f3..6aac89c215 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring the connection between GitHub Insights and GitHub Enterprise
 intro: 'You can manage how {% data variables.product.prodname_insights %} connects to {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can configure the connection to {% data variables.product.prodname_enterprise %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index e3d8eea29a..11ee06287c 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Enabling a link between GitHub Insights and GitHub Enterprise
 intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index c9f586770d..085e610f5e 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Installing GitHub Insights
 intro: 'You can install {% data variables.product.prodname_insights %} and connect the standalone application to {% data variables.product.prodname_ghe_server %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index f6344ccd82..b2deeb9d34 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Managing available metrics and reports
 intro: 'You can enable and disable specific metrics across {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
index 12be82871c..6d5ea396b7 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
@@ -1,7 +1,6 @@
 ---
 title: Managing contributors and teams
 intro: You can manage the people and teams included in metrics and reports.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage contributors and teams.'
@@ -98,7 +97,7 @@ You can create and manage custom teams in {% data variables.product.prodname_ins
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.teams-tab %}
 {% data reusables.github-insights.edit-team %}
-3. To the right of the contributor you'd like to remove, click {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Trashcan button](/assets/images/help/insights/contributor-trashcan.png)
+3. To the right of the contributor you'd like to remove, click {% octicon "trash" aria-label="The trash icon" %}. ![trash button](/assets/images/help/insights/contributor-trashcan.png)
 
 #### Renaming a custom team
 
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-events.md
index d64fb180f8..a70c80de3a 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-events.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-events.md
@@ -1,7 +1,6 @@
 ---
 title: Managing events
 intro: '{% data reusables.github-insights.events %}'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-events
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage events.'
@@ -29,5 +28,5 @@ After you create an event in {% data variables.product.prodname_insights %}, any
 
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.events-tab %}
-3. To the right of the event you want to delete, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Trash can button](/assets/images/help/insights/trashcan-button.png)
+3. To the right of the event you want to delete, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Trash can button](/assets/images/help/insights/trashcan-button.png)
 4. Click **Confirm**.
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-goals.md
index 5f779abc01..c7364eded7 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: Managing goals
 intro: You can use goals to set targets for key metrics and measure success reaching those targets.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 08f932de21..cdcf82b9e3 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -1,7 +1,6 @@
 ---
 title: Managing organizations
 intro: 'You can manage the {% data variables.product.prodname_enterprise %} organizations that are included in metrics.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index f747452514..8bf8c4d001 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Managing permissions in GitHub Insights
 intro: 'You can update a user''s permissions in {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-repositories.md
index c1a2b21ac4..920cf3d94b 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-repositories.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/managing-repositories.md
@@ -1,7 +1,6 @@
 ---
 title: Managing repositories
 intro: 'You can manage the repositories connected to {% data variables.product.prodname_insights %} and the data included in metrics for each repository.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-repositories
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories. '
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index 587e055bb9..dd7ddd3633 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: System overview for GitHub Insights
 intro: '{% data variables.product.prodname_insights %} is a standalone application which interfaces with {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index e17b23f341..20cca11a52 100644
--- a/translations/ko-KR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/ko-KR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Updating GitHub Insights
 intro: 'You can update to the latest version of {% data variables.product.prodname_insights %} to benefit from improvements and bug fixes.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index d11b7362a1..05690aca24 100644
--- a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md
index c2594b20a9..dce004ec4e 100644
--- a/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -43,7 +43,7 @@ For more information, see {% if currentVersion == "free-pro-team@latest" or curr
 
 ### 더 읽을거리
 
-- "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)"
+- "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
 - "[About teams](/articles/about-teams)"
 - "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)"
 - "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)"
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md
index 26004b73d3..0e6fcbceb7 100644
--- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
 {% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index 0da102c303..f6edcdcffd 100644
--- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -26,9 +26,8 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 
 ### Adding an allowed IP address
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 
 ### Enabling allowed IP addresses
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. Under "IP allow list", select **Enable IP allow list**. ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. Click **Save**.
 
 ### Editing an allowed IP address
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 
 ### Deleting an allowed IP address
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index 67e90991d3..43fa025d37 100644
--- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### Displaying the security and analysis settings
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
@@ -50,33 +49,38 @@ You can enable or disable features for all repositories. {% if currentVersion ==
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
 2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. Optionally, enable the feature by default for new repositories in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Enable by default" option for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -85,11 +89,14 @@ You can enable or disable features for all repositories. {% if currentVersion ==
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
 2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -122,7 +129,7 @@ To allow {% data variables.product.prodname_dependabot %} to access a private {%
 You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
-1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. The size of your license is shown for organization-level licenses. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
+1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}.
 1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}.
 
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index 826daccdb4..ccde3cc027 100644
--- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ Before you require use of two-factor authentication, we recommend notifying {% i
 
 ### Requiring two-factor authentication in your organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..97c7a9133a
--- /dev/null
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About email restrictions
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. For more information about outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)."
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index 271c3f01a2..8c139fa7de 100644
--- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
 
 ### Searching the audit log
@@ -36,6 +35,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`계정`](#account-category-actions)                                                                                                                                                                                                                                                                                                                                           | Contains all activities related to your organization account.                                                                                                                                                                                                                                                                                                                                                 |
 | [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                                                                                                                                                                      | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."                                                                        |
 | [`결제`](#billing-category-actions)                                                                                                                                                                                                                                                                                                                                           | Contains all activities related to your organization's billing.                                                                                                                                                                                                                                                                                                                                               |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                                                                                                                | Contains all activities related to your organization's codespaces.                                                                                                                                                                                                                                                                                                                                            |
 | [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                                                                                                                  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."                                                                                                        |
 | [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                                                                                                                                                              | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization.                                                                                                                                                                                                                                             |
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                                                                                                              | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."                                                      |
@@ -191,6 +191,20 @@ An overview of some of the most common actions that are recorded as events in th
 | `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). |
 | `change_email`        | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes.                                              |
 
+#### `codespaces` category actions
+
+| 동작                           | 설명                                                                                                                                                                                                                                             |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                     | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                   |
+| `resume`                     | Triggered when a user resumes a suspended codespace.                                                                                                                                                                                           |
+| `delete`                     | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                   |
+| `create_an_org_secret`       | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)  |
+| `update_an_org_secret`       | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `remove_an_org_secret`       | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+
+
+
 #### `dependabot_alerts` category actions
 
 | 동작     | 설명                                                                                                                                                                                                                                                                                                                                                                                                                     |
@@ -484,6 +498,38 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_linear_history_requirement_enforcement_level` | Triggered when required linear commit history is enabled or disabled for a protected branch.                                                                                                                                           |
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `pull_request` category actions
+
+| 동작                      | 설명                                                                                                         |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `create`                | Triggered when a pull request is created.                                                                  |
+| `close`                 | Triggered when a pull request is closed without being merged.                                              |
+| `reopen`                | Triggered when a pull request is reopened after previously being closed.                                   |
+| `병합`                    | Triggered when a pull request is merged.                                                                   |
+| `indirect_merge`        | Triggered when a pull request is considered merged because its commits were merged into the target branch. |
+| `ready_for_review`      | Triggered when a pull request is marked as ready for review.                                               |
+| `converted_to_draft`    | Triggered when a pull request is converted to a draft.                                                     |
+| `create_review_request` | Triggered when a review is requested.                                                                      |
+| `remove_review_request` | Triggered when a review request is removed.                                                                |
+
+#### `pull_request_review` category actions
+
+| 동작       | 설명                                    |
+| -------- | ------------------------------------- |
+| `제출`     | Triggered when a review is submitted. |
+| `해제`     | Triggered when a review is dismissed. |
+| `delete` | Triggered when a review is deleted.   |
+
+#### `pull_request_review_comment` category actions
+
+| 동작       | 설명                                          |
+| -------- | ------------------------------------------- |
+| `create` | Triggered when a review comment is added.   |
+| `업데이트`   | Triggered when a review comment is changed. |
+| `delete` | Triggered when a review comment is deleted. |
+{% endif %}
+
 #### `repo` category actions
 
 | 동작                                    | 설명                                                                                                                                                                                                                                                                                                                                                 |
@@ -593,22 +639,24 @@ For more information, see "[Managing the publication of {% data variables.produc
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` category actions
 
-| 동작                                             | 설명                                                                                                                                                                                                                                                                                                                       |
-| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`              | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                              |
-| `repo_funding_links_file_action`               | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                         |
-| `sponsor_sponsorship_cancel`                   | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                         |
-| `sponsor_sponsorship_create`                   | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                           |
-| `sponsor_sponsorship_preference_change`        | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/articles/managing-your-sponsorship)")                                                                                                                                                            |
-| `sponsor_sponsorship_tier_change`              | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                     |
-| `sponsored_developer_approve`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
-| `sponsored_developer_create`                   | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
-| `sponsored_developer_profile_update`           | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
-| `sponsored_developer_request_approval`         | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
-| `sponsored_developer_tier_description_update`  | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
-| sponsored_developer_update_newsletter_send | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)")                                                                                                                                                                                          |
-| `waitlist_invite_sponsored_developer`          | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
-| `waitlist_join`                                | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
+| 동작                                            | 설명                                                                                                                                                                                                                                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                |
+| `repo_funding_links_file_action`              | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                |
+| `sponsor_sponsorship_cancel`                  | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                |
+| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                               |
+| `sponsor_sponsorship_tier_change`             | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                            |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
+| `sponsored_developer_disable`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled                                                                                                                                                                                                                          |
+| `sponsored_developer_redraft`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
+| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                                  |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
 {% endif %}
 
 #### `team` category actions
diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index e34e94897a..6db88dddd8 100644
--- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -14,9 +14,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**. ![Installed {% data variables.product.prodname_github_app %}s tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png)
 6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index a1cfcce236..92bb476d86 100644
--- a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ For more information about {% data variables.product.prodname_github_app %} mana
 
 ### Giving someone the ability to manage all {% data variables.product.prodname_github_app %}s owned by the organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "Management", type the username of the person you want to designate as a {% data variables.product.prodname_github_app %} manager in the organization, and click **Grant**. ![Add a {% data variables.product.prodname_github_app %} manager](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### Giving someone the ability to manage an individual {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to add a {% data variables.product.prodname_github_app %} manager for. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index c91680f3e5..105d2a3167 100644
--- a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ For more information about {% data variables.product.prodname_github_app %} mana
 
 ### Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "Management", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**. ![Revoke {% data variables.product.prodname_github_app %} manager permissions](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to remove a {% data variables.product.prodname_github_app %} manager from. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 226974d8c2..d811edf2ce 100644
--- a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -49,4 +49,4 @@ If a team's access to a project board is inherited from a parent team, you must
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png)
-5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png)
+5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index ebe9d75fd2..531bc5468d 100644
--- a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ In addition to managing organization-level settings, organization owners have ad
 | Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)")                                                                                                                                                                                                                                                                    |       |       |       |          |                                                                       **X**                                                                        |
 | Change a repository's settings                                                                                                                                                                                                                                                                                                                                                     |       |       |       |          |                                                                       **X**                                                                        |
 | Manage team and collaborator access to the repository                                                                                                                                                                                                                                                                                                                              |       |       |       |          |                                                                       **X**                                                                        |
-| Edit the repository's default branch                                                                                                                                                                                                                                                                                                                                               |       |       |       |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Edit the repository's default branch                                                                                                                                                                                                                                                                                                                                               |       |       |       |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                                           |       |       |       |          |                                                                       **X**                                                                        |
 | Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                       |       |       | **X** |  **X**   |                                                                 **X** 
 {% endif %}
@@ -142,7 +142,8 @@ In addition to managing organization-level settings, organization owners have ad
 | [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                         |       | **X** | **X** |  **X**   |                                                                       **X**                                                                        |
 | [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                          |       | **X** | **X** |  **X**   |                                                                       **X**                                                                        |
 | [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                       | **X** | **X** | **X** |  **X**   |                                                                       **X**                                                                        |
-| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                          |       |       |       |  **X**   |                                                                 **X** 
+| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                          |       |       |       |  **X**   |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                  |       |       | **X** |  **X**   |                                                                 **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ In this section, you can find the repository permission levels required for secu
 
 | Repository action                                                                                                                                                                                                                                                             | Read  |  심사   |        Write        |      Maintain       |                                                                             Admin                                                                             |
 |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                                                                             |       |       |                     |                     |                                                                                                                                                               |
-| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository                                                                           |       |       |                     |                     |                                                                             **X**                                                                             |
-| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                |       |       |                     |                     |                                                                             **X**                                                                             |
-| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies    |       |       |                     |                     |                                                                             **X**                                                                             |
-| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)                                                                                                                                                                      |       |       |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |       |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                                                                           |       |       |                     |                     |                                                                                                                                                               |
+| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository                                                                                |       |       |                     |                     |                                                                             **X**                                                                             |
+| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                     |       |       |                     |                     |                                                                             **X**                                                                             |
+| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies    |       |       |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [security advisories](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                                                             |       |       |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |       |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository                                                                                                                                       |       |       |                     |                     |                                                                             **X**                                                                             |
 | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                       | **X** | **X** |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                                                                         | **X** | **X** |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index 3e0aecf9bf..0ca973c38f 100644
--- a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ If someone with admin permissions to an organization's repository grants a membe
 
 ### Setting base permissions
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Base permissions", use the drop-down to select new base permissions. ![Selecting new permission level from base permissions drop-down](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. Review the changes. To confirm, click **Change default permission to PERMISSION**. ![Reviewing and confirming change of base permissions](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index 579f0d1be2..60426bc12d 100644
--- a/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -22,17 +22,15 @@ You can allow members to access your organization's repositories using SSH certi
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### Deleting an SSH certificate authority
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index 2e93ff6e28..90801f8d04 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -17,9 +17,8 @@ By default, issues cannot be deleted in an organization's repositories. An organ
 
 Once enabled, organization owners and people with admin permissions in an organization-owned repository can delete issues. People with admin permissions in a repository include organization members and outside collaborators with admin privileges. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)" and "[Deleting an issue](/articles/deleting-an-issue)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Issue deletion", select **Allow members to delete issues for this organization**. ![Checkbox to allow people to delete issues](/assets/images/help/settings/issue-deletion.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index 6eddab65c9..5c75ddf307 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,9 +16,8 @@ Organization owners can set limitations for viewing organization dependency insi
 
 Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing a policy on dependency insights in your enterprise account](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**. ![Checkbox to allow members to view insights](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 133f52739a..a55928f3ee 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -28,7 +28,6 @@ Once you delete an organization, GitHub **cannot restore your content**. Therefo
 
 ### 2. Delete the organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Near the bottom of the organization's settings page, click **Delete this Organization**. ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index baf40e2ac8..84f63f9764 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -27,9 +27,8 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for
 
 ### Managing {% data variables.product.prodname_actions %} permissions for your organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Local and third-party Actions**, select an option. ![Enable, disable, or limit actions for this organization](/assets/images/help/repository/enable-org-actions.png)
 1. Click **Save**.
@@ -50,9 +49,8 @@ You can disable all workflows for an organization or set a policy that configure
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Policies**, select an option. ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png)
 1. Click **Save**.
@@ -61,9 +59,8 @@ You can disable all workflows for an organization or set a policy that configure
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. Click **Save**.
@@ -77,9 +74,27 @@ You can disable all workflows for an organization or set a policy that configure
 
 #### Configuring the private fork policy for an organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your organization
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you choose the restricted option as the default in your organization settings, the same option is auto-selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and the more restricted default has been selected in the enterprise settings, you won't be able to choose the more permissive default in your organization settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. Click **Save** to apply the settings.
+{% endif %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/index.md b/translations/ko-KR/content/organizations/managing-organization-settings/index.md
index e44eea4306..44acf14e45 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/index.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/index.md
@@ -13,7 +13,7 @@ topics:
   - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index a9307d5b72..cb98ea549e 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ Default labels are included in every new repository in your organization, but an
 
 ### Creating a default label
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ Default labels are included in every new repository in your organization, but an
 
 ### Editing a default label
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ Default labels are included in every new repository in your organization, but an
 
 ### Deleting a default label
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 324675daeb..748db9fa9e 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. Click **Save**. !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png)
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index 8cd727cfef..1684ad779f 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ Organization owners can schedule a reminder for one or more teams in their organ
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### Creating a scheduled reminder for an organization
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ Organization owners can schedule a reminder for one or more teams in their organ
 {% data reusables.reminders.create-reminder %}
 
 ### Managing a scheduled reminder for an organization
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ Organization owners can schedule a reminder for one or more teams in their organ
 {% data reusables.reminders.update-buttons %}
 
 ### Deleting a scheduled reminder for an organization
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index fbde6acd22..8215475852 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ If an enterprise owner has enforced a policy for the default branch name for you
 
 ### Setting the default branch name
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. Under "Repository default branch", click **Change default branch name now**. ![Override button](/assets/images/help/organizations/repo-default-name-button.png)
 4. Type the default name that you would like to use for new branches. ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 44f16b2b27..25cf4001fd 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -20,9 +20,8 @@ Organization owners can manage the display of member names in an organization.
 
 Each organization member chooses their own profile name in their settings. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Admin repository permissions", select or unselect **Allow members to see comment author's profile name in private repositories**. ![Checkbox to allow members to see comment author's full name in private repositories](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index ed5d05bf7f..660593d99b 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ If you allow forking of private{% if currentVersion == "free-pro-team@latest" or
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**. ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
index a86a70c96d..f2cb44ed3f 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -21,9 +21,8 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
 
 If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
 1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
 1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index 4bb4538471..e132e6a321 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates.
 
-You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)."
+You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. Click **Update profile**. ![Update profile button](/assets/images/help/organizations/update-profile-button.png)
 
 ### 더 읽을거리
 
-- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)"
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md
index c93dc46942..9ddfce5c6e 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -40,9 +40,8 @@ After changing your organization's name:
 
 ### Changing your organization's name
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**. ![Rename organization button](/assets/images/help/settings/settings-rename-organization.png)
 
 ### 더 읽을거리
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index 288e2e4d23..e8246f8ca4 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -27,9 +27,8 @@ Organization owners can always create any type of repository.
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository creation", select one or more options. ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index 5b2cf4ca77..7a292f4137 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ You can restrict the ability to change repository visibility to organization own
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository visibility change", deselect **Allow members to change repository visibilities for this organization**. ![Checkbox to allow members to change repository visibility](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index 32b3683f40..cb887e6729 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -19,9 +19,8 @@ Organization owners, and members with admin privileges for a repository, can inv
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 7cd517d82f..ca79374550 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -16,9 +16,8 @@ topics:
 
 Owners can set permissions for deleting or transferring repositories in an organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository deletion and transfer", select or deselect **Allow members to delete or transfer repositories for this organization**. ![Checkbox to allow members to delete repositories](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index 47df668469..3ceab7932a 100644
--- a/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -17,9 +17,8 @@ Organization owners can set team creation permissions.
 
 If you do not set team creation permissions, all organization members will be able to create teams by default.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Team creation rules", select or deselect **Allow members to create teams**. ![Checkbox to allow members to create teams](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..528c73b1bc
--- /dev/null
+++ b/translations/ko-KR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About domain verification
+
+After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
+
+If your organization is owned by an enterprise account, a "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output.
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service. ![Verified badge](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index d28295df68..510a304726 100644
--- a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ Billing managers **are not** able to:
 
 The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Next to Billing managers, click **Add a billing manager**. ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png)
 6. Type the username or email address of the person you want to add and click **Send invitation**. ![Invite billing manager page](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index 480c1e0669..5beb9f2dd5 100644
--- a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -23,6 +23,12 @@ topics:
 
 Organization owners have full administrative access to the organization. {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**Note**: As an organization owner, you can change the role of other organization members and owners. You can't change your own role.
+
+{% endnote %}
+
 ### Appointing an organization owner
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index 657c20f64f..c405041eb4 100644
--- a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
 | Access the organization audit log                                                                                                                                                                                                                                                                                                                               | **X**  |         |                  |
 | Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" for details)                                                                                                                                                                                                                       | **X**  |         |                  |
 | Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details)                                                                                                                                                                                                                    | **X**  |         |                  |
-| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" for details)                                                                                                                             | **X**  |         |                  |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)                                                                                                                 | **X**  |         |                  |
 | Delete **all teams**                                                                                                                                                                                                                                                                                                                                            | **X**  |         |                  |
 | Delete the organization account, including all repositories                                                                                                                                                                                                                                                                                                     | **X**  |         |                  |
 | Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details)                                                                                                                                                                                                     | **X**  |  **X**  |                  |
@@ -60,9 +60,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
 | Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details)                                                                                                                                                                                 | **X**  |         |                  |
 | Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details)                                                                                                                                        | **X**  |         |                  |
 | Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details)                                                                                                                                                                                                            | **X**  |         |                  |
-| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details)                                                                                                                                    | **X**  |  **X**  |                  |
+| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)" for details)                                                                                                                                                                                            | **X**  |  **X**  |                  |
 | Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" for details)                                                                                                                         | **X**  |         |                  |
-| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details )                                                                                                                       | **X**  |         |                  |
+| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details )                                                                                                                                           | **X**  |         |                  |
 | Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X**  |         |                  |
 | Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details)                                                                                                                        | **X**  |         |                  |
 | Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                                                                                                               | **X**  |         |                  |
diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index 1187e89f46..d75ba364cc 100644
--- a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. In the Billing managers list, next to the name of the person you want to remove, click {% octicon "x" aria-label="X symbol" %}. ![Remove billing manager](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![Remove billing manager](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index f73bcd3aab..8336a15180 100644
--- a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/).
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**. ![Link to view and save your recovery codes](/assets/images/help/saml/saml_recovery_codes.png)
 6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**. ![Buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index fa147ba020..4e9dec58ac 100644
--- a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
 
 Prior to enforcing SAML SSO in your organization, ensure that you've set up your identity provider (IdP). For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index f3f3edad9f..deebdcdacf 100644
--- a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "Team synchronization", click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index 09a5a86cab..ca61f74cd4 100644
--- a/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -29,9 +29,8 @@ For more information, see "[Repository permission levels for an organization](/a
 
 ### Migrating all of your organization's legacy admin teams
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Review your organization's legacy admin teams, then click **Migrate all teams**. ![Migrate all teams button](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. Read the information about possible permissions changes for members of these teams, then click **Migrate all teams.** ![Confirm migration button](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index 55e50ac0fe..7a04bb8111 100644
--- a/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -15,9 +15,8 @@ topics:
 
 {% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. Under "Team discussions", unselect **Enable team discussions for this organization**. ![Checkbox to enable or disable team discussions for an organization](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. Click **Save**.
diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index 206fbca184..46a1e3d63e 100644
--- a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Next to the application you'd like to approve, click **Review**. ![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. After you review the information about the requested application, click **Grant access**. ![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index caac5719c4..803cb0bb14 100644
--- a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -12,9 +12,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="The edit icon" %}. ![Edit icon](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. Click **Deny access**. ![Deny confirmation button](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index 02d80ff0a7..5ed8a69ef3 100644
--- a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Click **Remove restrictions**. ![Remove restrictions button](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**. ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index 071d77982f..5415a22717 100644
--- a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Under "Third-party application access policy," click **Setup application access restrictions**. ![Set up restrictions button](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. After you review the information about third-party access restrictions, click **Restrict third-party application access**. ![Restriction confirmation button](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/ko-KR/content/packages/index.md b/translations/ko-KR/content/packages/index.md
index 0d7b1e5e13..5f693358ee 100644
--- a/translations/ko-KR/content/packages/index.md
+++ b/translations/ko-KR/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/ko-KR/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/ko-KR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..94ba1a685d
--- /dev/null
+++ b/translations/ko-KR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,85 @@
+---
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### About scopes and permissions for package registries
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+예시:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted.{% elsif currentVersion == "github-ae@latest" %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+
+| 범위                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 설명                                                                                | Required permission |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------- |
+| `read:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Download and install packages from {% data variables.product.prodname_registry %} | read                |
+| `write:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Upload and publish packages to {% data variables.product.prodname_registry %}     | write               |
+| `delete:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                                   |                     |
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Delete packages from {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} |                                                                                   |                     |
+| admin                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                   |                     |
+| `repo`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Upload and delete packages (along with `write:packages`, or `delete:packages`)    | write or admin      |
+
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/ko-KR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/ko-KR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..26b5e55a8a
--- /dev/null
+++ b/translations/ko-KR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: Configuring a package's access control and visibility
+intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### Configuring access to container images for your personal account
+
+If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users will automatically be given access and don't need to accept an invitation first.
+
+### Configuring access to container images for an organization
+
+If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users or teams will automatically be given access and don't need to accept an invitation first.
+
+### Inheriting access for a container image from a repository
+
+To simplify package management through {% data variables.product.prodname_actions %} workflows, you can enable a container image to inherit the access permissions of a repository by default.
+
+If you inherit the access permissions of the repository where your package's workflows are stored, then you can adjust access to your package through the repository's permissions.
+
+Once a repository is synced, you can't access the package's granular access settings. To customize the package's permissions through the granular package access settings, you must remove the synced repository first.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. Under "Repository source", select **Inherit access from repository (recommended)**. ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### Ensuring workflow access to your package
+
+To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored.
+
+The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package.
+
+{% note %}
+
+**Note:** Syncing your container image with a repository through the **Actions access** menu option is different than connecting your container to a repository. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+#### {% data variables.product.prodname_actions %} access for user-account-owned container images
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+#### {% data variables.product.prodname_actions %} access for organization-owned container images
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like repository members to have to your container image. Outside collaborators will not be included. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for an organization](#configuring-access-to-container-images-for-an-organization)."
+
+### Configuring visibility of container images for your personal account
+
+When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
+
+### Container creation visibility for organization members
+
+You can choose the visibility of containers that organization members can publish by default.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, click **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images.
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, click **Internal**. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### Configuring visibility of container images for an organization
+
+When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/ko-KR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/ko-KR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..0cb35ed674
--- /dev/null
+++ b/translations/ko-KR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+### Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to a container image using the command line
+
+1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details:
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile:
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository.
+
+2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`.
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. Optionally, review details for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Tag your Docker image with your desired image name and hosting destination.
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  예시:
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  예시:
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/ko-KR/content/packages/learn-github-packages/index.md b/translations/ko-KR/content/packages/learn-github-packages/index.md
index c30d5e485e..01dcc26748 100644
--- a/translations/ko-KR/content/packages/learn-github-packages/index.md
+++ b/translations/ko-KR/content/packages/learn-github-packages/index.md
@@ -1,7 +1,7 @@
 ---
 title: Learn GitHub Packages
 shortTitle: Learn GitHub Packages
-intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.'
+intro: 'You can find out more about using packages in GitHub, including publishing new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
   - /github/managing-packages-with-github-packages/publishing-and-managing-packages
@@ -17,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md b/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..342d24ea7d
--- /dev/null
+++ b/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: Installing a package
+intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About package installation
+
+You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)."
+
+After you find a package, you can read the package's description and installation and usage instructions on the package page.
+
+### Installing a package
+
+You can install a package from {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+
+1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. Install the package using the instructions for your package client.
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/ko-KR/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/ko-KR/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..6c77cdb0e0
--- /dev/null
+++ b/translations/ko-KR/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,133 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately {% if currentVersion == "github-ae@latest" %} for specified users or internally for your enterprise{% else %}or publicly{% endif %} and use packages as dependencies in your projects.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% if currentVersion != "github-ae@latest" %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
+
+You can integrate {% data variables.product.prodname_registry %} with {% data variables.product.product_name %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)."
+
+#### Overview of package permissions and visibility
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| Permissions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                  |
+| {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |                                                                  |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| Visibility                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | {% data reusables.package_registry.public-or-private-packages %}
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About billing for {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+{% endif %}
+
+### Supported clients and formats
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
+#### Support for package registries
+
+| Language   | 설명                                                     | Package format                       | Package client |
+| ---------- | ------------------------------------------------------ | ------------------------------------ | -------------- |
+| JavaScript | Node package manager                                   | `package.json`                       | `npm`          |
+| Ruby       | RubyGems package manager                               | `Gemfile`                            | `gem`          |
+| Java       | Apache Maven project management and comprehension tool | `pom.xml`                            | `mvn`          |
+| Java       | Gradle build automation tool for Java                  | `build.gradle` or `build.gradle.kts` | `gradle`       |
+| .NET       | NuGet package management for .NET                      | `nupkg`                              | `dotnet` CLI   |
+| N/A        | Docker container management                            | `Dockerfile`                         | `Docker`       |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**Note:** Docker is not supported when subdomain isolation is disabled.
+
+{% endnote %}
+
+For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)."
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Managing packages
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. Or for repo-scoped packages, you can delete a version of a private package using GraphQL.
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
+
+### Contacting support
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use the [feedback form for {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages).
+
+Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if:
+
+* You experience anything that contradicts the documentation
+* You encounter vague or unclear errors
+* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information
+
+{% else %}
+If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators.
+
+{% endif %}
diff --git a/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md b/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md
index 2cb9438ee4..bd3c14e366 100644
--- a/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md
+++ b/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md
@@ -19,7 +19,7 @@ versions:
 
 You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
 
-{% data reusables.package_registry.public-or-private-packages %} A repository can contain more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
 
 {% if currentVersion == "free-pro-team@latest" %}
 If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository.
@@ -30,10 +30,10 @@ If a new version of a package fixes a security vulnerability, you should publish
 
 You can publish a package to {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
 
-1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 2. Authenticate to {% data variables.product.prodname_registry %} using your access token and the instructions for your package client.
 3. Publish the package using the instructions for your package client.
 
-For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)."
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
 
-After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see “[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages).”
+After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/learn-github-packages/viewing-packages)."
diff --git a/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md b/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..53342f7975
--- /dev/null
+++ b/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: Viewing packages
+intro: 'You can see details about packages published to a repository, and narrow results by organization or user.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About package views
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### Viewing a repository's packages
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Viewing an organization's packages
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**.
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Viewing your packages
+
+You can find and view any package you've published across all organizations and repositories.
+
+{% data reusables.profile.access_profile %}
+2. On the top of the profile page, in the main navigation, click **Packages**. ![Project tab](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### 더 읽을거리
+
+- "[Searching for packages](/github/searching-for-information-on-github/searching-for-packages)"
diff --git a/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..db022b22ec
--- /dev/null
+++ b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: About GitHub Packages and GitHub Actions
+intro: Learn the fundamentals of managing packages through your {% data variables.product.prodname_actions %} workflows.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..5c6b375de3
--- /dev/null
+++ b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: Example workflows for publishing a package
+intro: To help you get started with your own custom workflows, review some example workflows for publishing packages.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+You can find example workflows in "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
+
+  - [Publishing Node.js packages](/actions/guides/publishing-nodejs-packages)
+  - [Publishing Docker images](/actions/guides/publishing-docker-images)
+  - [Publishing Java packages with Maven](/actions/guides/publishing-java-packages-with-maven)
+  - [Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..790a661916
--- /dev/null
+++ b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: Managing GitHub packages using GitHub Actions workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'You can safely publish and consume packages by building custom workflows that can also build, test, and deploy your code.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..3c9eaa040e
--- /dev/null
+++ b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,450 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)."
+
+{% endif %}
+
+#### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+### About permissions and package access for repository-owned packages
+
+{% note %}
+
+**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.
+
+{% endnote %}
+
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
+
+{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About permissions and package access for {% data variables.product.prodname_container_registry %}
+
+The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions.
+
+All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+### Default permissions and access settings for containers modified through workflows
+
+When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
+
+For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
+- The container inherits the visibility and permissions model of the repository where the workflow is run.
+- Repository admins where the workflow is run become the admins of the container once the container is created.
+
+These are more examples of how default permissions work for workflows that manage packages.
+
+| {% data variables.product.prodname_actions %} workflow task | Default permissions and access                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Download an existing container                              | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br> |
+| Upload a new version to an existing container               | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.                                                                                                                                                                                                                                                                                                                          |
+| Delete a container or versions of a container               | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.                                                                                                                                                                                                                                                                                                                                      |
+
+You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publishing a package using an action
+
+You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}:
+
+- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  The relevant settings are explained in the following table: <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configures the <code>Create and publish a package</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    This job installs NPM and uses it to build the app.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Creates a new step called <code>Build container image</code>. This step runs as part of the <code>build-and-push-image</code> job. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sends the required parameters to the <code>build-push-action</code> action. This are defined in the subsequent lines.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the password that is used to access {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace <code>YOUR-HOSTNAME</code> with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use <code>ghcr.io</code> as the hostname.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines which repository will host the resulting package, and sets the name of the published package. Replace <code>octo-image</code> with the name you want for your package.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the first seven characters of the commit's SHA. For example, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the git ref. This can be the name of the branch used to create the package.
+  </td>
+  </tr>
+  </table>
+
+- This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
+- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
+
+
+### Installing a package using an action
+
+You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Upgrading a workflow that accesses `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
diff --git a/translations/ko-KR/content/packages/quickstart.md b/translations/ko-KR/content/packages/quickstart.md
index a4b845a88f..2f9dbc07b9 100644
--- a/translations/ko-KR/content/packages/quickstart.md
+++ b/translations/ko-KR/content/packages/quickstart.md
@@ -71,7 +71,10 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -95,7 +98,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
 
 ### Viewing your published package
 
-Packages are published at the repository level. You can see all the packages in a repository and search for a specific package.
+You can view all of the packages you have published.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ Packages are published at the repository level. You can see all the packages in
 
 ### Installing a published package
 
-Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)."
+Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
 
 ### 다음 단계
 
-The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
+The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
 
 Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
 
 - "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages
 - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions
-- "[Guides](/packages/guides)" for specific uses cases and examples
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..3397c52972
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: Enabling improved container support with the Container registry
+intro: 'To use the {% data variables.product.prodname_container_registry %}, you must enable it for your user or organization account.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)."
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your personal account
+
+Once the {% data variables.product.prodname_container_registry %} is enabled for your personal user account, you can publish containers to the {% data variables.product.prodname_container_registry %} owned by your user account.
+
+To use the {% data variables.product.prodname_container_registry %} within an organization, the organization owner must enable the feature for organization members.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png)
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your organization account
+
+Before organization owners or members can publish container images to the {% data variables.product.prodname_container_registry %}, an organization owner must enable the feature preview for the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, select **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, select **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, select **Internal**. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/index.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..c0017ab0a4
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with a GitHub Packages registry
+shortTitle: Working with a GitHub Packages registry
+intro: 'Learn how to use a supported {% data variables.product.prodname_registry %} registry.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### Table of Contents
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..e5e3d10430
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,124 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- Store container images within your organization and user account, rather than a repository.
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- Access public container images anonymously.
+
+|                   | Docker registry                                                                                                                                                                                                                                                                            | {% data variables.product.prodname_container_registry %}
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Hosting locations | You can host multiple Docker images in one repository.                                                                                                                                                                                                                                     | You can host multiple container images in one organization or user account.                                                                                                            |
+| Permissions       | Each image inherits the permissions of the repository where the image is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. |
+ Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access    | N/A | You can access public container images anonymously. Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### Billing changes
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. For more information, see "[About  billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+### Domain changes
+
+The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`.
+
+| Registry                                                       | Example URL                                         |
+| -------------------------------------------------------------- | --------------------------------------------------- |
+| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` |
+| {% data variables.product.prodname_container_registry %}     | `ghcr.io/OWNER/IMAGE_NAME`                          |
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}.
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Migrating a Docker image using the Docker CLI
+
+To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine.
+
+1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward.
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization.
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name.
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. Sign in to the new {% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### Updating your {% data variables.product.prodname_actions %} workflow
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers.
+
+1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)."
+
+2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`.
+
+3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+
+4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}.
+
+#### Example of updated workflow
+
+If part of your workflow accessed a Docker image hosted by the Docker registry like this:
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this:
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..6e4e51805b
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Working with the Apache Maven registry
+intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist.
+
+In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token.
+
+In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag.
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`.
+
+If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `<distributionManagement>` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository.
+
+For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+
+1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+
+  If your instance has subdomain isolation enabled:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. Publish the package.
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Installing a package
+
+To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package.
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. Install the package.
+
+  ```shell
+  $ mvn install
+  ```
+
+### 더 읽을거리
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..0137b96e7a
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://ghcr.io`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About {% data variables.product.prodname_container_registry %} support
+
+To push and pull container images, an organization admin or the owner of a personal account must enable the {% data variables.product.prodname_container_registry %}. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+When installing or publishing a Docker image, the Container registry supports foreign layers, such as Windows images.
+
+The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
+
+* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Pushing container images
+
+This example pushes the latest version of `IMAGE-NAME`.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+This example pushes the `2.5` version of the image.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+### Pulling container images
+
+#### Pull by digest
+
+To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
+
+1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. Remove image locally as needed.
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### Pull by name
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### Pull by name and version
+
+Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### Pull by name and latest version
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### Building container images
+
+This example builds the `hello_docker` image:
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### Tagging container images
+
+1. Find the ID for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. Tag your Docker image using the image ID and your desired image name and hosting destination.
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..a5dce745d7
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,262 @@
+---
+title: Working with the Docker registry
+intro: 'You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)."
+
+{% endif %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command.
+
+To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file.
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login docker.HOSTNAME -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation disabled:
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}.
+
+For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)."
+
+### Publishing an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**Note:** Image names must only use lowercase letters.
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. Determine the image name and ID for your docker image using `docker images`.
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. Publish the image to {% data variables.product.prodname_registry %}.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+  {% endnote %}
+
+#### Example publishing a Docker image
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+These examples assume your instance has subdomain isolation enabled.
+{% endif %}
+
+You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+You can publish a new Docker image for the first time and name it `monalisa`.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### Downloading an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %} and *TAG_NAME* with tag for the image you want to install.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation disabled:
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+{% endnote %}
+
+### 더 읽을거리
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..c878fe2bdc
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your personal access token. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+Replace *REGISTRY-URL* with the URL for your enterprise's Maven registry, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.
+{% endif %}
+
+Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+{% note %}
+
+**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)."
+
+{% endnote %}
+
+##### Example using Gradle Groovy for a single package in a repository
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### Example using Gradle Groovy for multiple packages in the same repository
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### Example using Kotlin DSL for a single package in the same repository
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### Example using Kotlin DSL for multiple packages in the same repository
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            register<MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+### Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. After creating your package, you can publish the package.
+
+  ```shell
+   $ gradle publish
+  ```
+
+### Installing a package
+
+You can install a package by adding the package as a dependency to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Gradle Groovy:
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. Add the maven plugin to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Gradle Groovy:
+  ```shell
+  plugins {
+      id 'maven'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  plugins {
+      `maven`
+  }
+  ```
+
+  3. Install the package.
+
+  ```shell
+  $ gradle install
+  ```
+
+### 더 읽을거리
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..ec4dc104c9
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,215 @@
+---
+title: Working with the npm registry
+intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Limits for published npm versions
+
+If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage.
+
+In the future, to improve performance of the service, you won't be able to publish more than 1,000 versions of a package on {% data variables.product.prodname_dotcom %}. Any versions published before hitting this limit will still be readable.
+
+If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
+
+{% endif %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token.
+
+To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+//<em>HOSTNAME</em>/_registry/npm/:_authToken=<em>TOKEN</em>
+```
+{% endif %}
+
+To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address.
+
+If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### Publishing a package
+
+{% note %}
+
+**Note:** Package names and scopes must only use lowercase letters.
+
+{% endnote %}
+
+By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation.
+
+You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)."
+
+You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`.
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### Publishing a package using a local *.npmrc* file
+
+You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" {% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`.
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### Publishing a package using `publishConfig` in the *package.json* file
+
+You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+
+1. Edit the *package.json* file for your package and include a `publishConfig` entry.
+  {% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package.
+
+To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository.
+
+{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name.
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### Installing a package
+
+You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation.
+
+By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)."
+
+You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency.
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. Install the package.
+
+  ```shell
+  $ npm install
+  ```
+
+#### Installing packages from other organizations
+
+By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### Using the official NPM registry
+
+{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
+{% endif %}
+
+### 더 읽을거리
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..704e2fec78
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,236 @@
+---
+title: Working with the NuGet registry
+intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client.
+
+You must replace:
+- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}.
+- `TOKEN` with your personal access token.
+- `OWNER` with the name of the user or organization account that owns the repository containing your project.{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %}If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://HOSTNAME/_registry/nuget/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+{% endif %}
+
+### Publishing a package
+
+You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### Publishing a package using a GitHub PAT as your API key
+
+If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+1. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. Publish the package using your PAT as the API key.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### Publishing a package using a *nuget.config* file
+
+When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. Add your project's specific information to your project's file, which ends in *.csproj*.  You must replace:
+    - `OWNER` with the name of the user or organization account that owns the repository containing your project.
+    - `REPOSITORY` with the name of the repository containing the package you want to publish.
+    - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. Publish the package using the `key` you specified in the *nuget.config* file.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field.
+
+For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository:
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### Installing a package
+
+Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use:
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. Install the packages with the `restore` command.
+  ```shell
+  dotnet restore
+  ```
+
+### 문제 해결
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### 더 읽을거리
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..262dad2367
--- /dev/null
+++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,152 @@
+---
+title: Working with the RubyGems registry
+intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### 빌드전 요구 사양
+
+- You must have rubygems 2.4.1 or higher. To find your rubygems version:
+
+  ```shell
+  $ gem --version
+  ```
+
+  - You must have bundler 1.6.4 or higher. To find your Bundler version:
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - Install keycutter to manage multiple credentials. To install keycutter:
+  ```shell
+  $ gem install keycutter
+  ```
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the  *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems.
+
+To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your personal access token.  Create a new *~/.gem/credentials* file if this file doesn't exist.
+
+For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your personal access token.
+
+```shell
+---
+:github: Bearer <em>TOKEN</em>
+```
+
+To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace:
+  - `USERNAME` with your {% data variables.product.prodname_dotcom %} username.
+  - `TOKEN` with your personal access token.
+  - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.
+{% endif %}
+
+If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example.
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Build the package from the *gemspec* to create the *.gem* package.
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### Publishing multiple packages to the same repository
+
+To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### Installing a package
+
+You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html).
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. Install the package:
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### 더 읽을거리
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index a9a8946ef1..83bd268c9a 100644
--- a/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -46,7 +46,7 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png)
 5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
 ```shell
@@ -79,7 +79,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
   ```shell
diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md
index 8a1f526a27..2f0a59c610 100644
--- a/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -68,14 +68,6 @@ The URL where your site is available depends on whether subdomain isolation is e
 For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator.
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Repositories using the legacy `<username>.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://<username>.github.com` to `http(s)://<username>.github.io`. If both a `<username>.github.com` and `<username>.github.io` repository exist, only the `<username>.github.io` repository will be published.
-
-{% endnote %}
-{% endif %}
-
 ### Publishing sources for {% data variables.product.prodname_pages %} sites
 
 The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored.
diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index a710e4ddc2..319e8cfdd2 100644
--- a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -87,7 +87,12 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 10. Save and close the Gemfile.
 11. From the command line, run `bundle update`.
 11. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
-12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md
index ea11beb711..7645217ecf 100644
--- a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -225,7 +225,7 @@ Next, let's fetch our newly created repository:
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ A project the size of Rails has thousands of issues. We'll need to [paginate][pa
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ A big part of being a good API citizen is respecting rate limits by caching info
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ In addition to the JSON body, take note of the HTTP status code of `200` and the
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 The `304` status indicates that the resource hasn't changed since the last time we asked for it and the response will contain no body. As a bonus, `304` responses don't count against your [rate limit][rate-limiting].
diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md
index 8315a053f7..a87e65016c 100644
--- a/translations/ko-KR/content/rest/overview/libraries.md
+++ b/translations/ko-KR/content/rest/overview/libraries.md
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
diff --git a/translations/ko-KR/content/rest/overview/media-types.md b/translations/ko-KR/content/rest/overview/media-types.md
index b0c7b0c817..1e6cb85efa 100644
--- a/translations/ko-KR/content/rest/overview/media-types.md
+++ b/translations/ko-KR/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ You can check the current version through every response's headers.  Look for th
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md
index 9da9d4845e..612781e7d0 100644
--- a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md
@@ -34,7 +34,7 @@ sent and received as JSON.
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: nginx
 > Date: Fri, 12 Oct 2012 23:33:14 GMT
 > Content-Type: application/json; charset=utf-8
@@ -126,7 +126,7 @@ Authenticating with invalid credentials will return `401 Unauthorized`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
-> HTTP/1.1 401 Unauthorized
+> HTTP/2 401
 
 > {
 >   "message": "Bad credentials",
@@ -139,7 +139,7 @@ After detecting several requests with invalid credentials within a short period,
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 -u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > {
 >   "message": "Maximum number of login attempts exceeded. Please try again later.",
 >   "documentation_url": "{% data variables.product.doc_url_pre %}"
@@ -181,7 +181,7 @@ There are three possible types of client errors on API calls that receive reques
 
 1. Sending invalid JSON will result in a `400 Bad Request` response.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 35
        
         {"message":"Problems parsing JSON"}
@@ -189,14 +189,14 @@ There are three possible types of client errors on API calls that receive reques
 2. Sending the wrong type of JSON values will result in a `400 Bad
 Request` response.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 40
        
         {"message":"Body should be a JSON object"}
 
 3. Sending invalid fields will result in a `422 Unprocessable Entity` response.
    
-        HTTP/1.1 422 Unprocessable Entity
+        HTTP/2 422
         Content-Length: 149
        
         {
@@ -328,7 +328,7 @@ The returned HTTP headers of any API request show your current rate limit status
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 56
@@ -351,7 +351,7 @@ new Date(1372700873 * 1000)
 If you exceed the rate limit, an error response returns:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 0
@@ -371,7 +371,7 @@ If your OAuth application needs to make unauthenticated calls with a higher rate
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 5000
 > X-RateLimit-Remaining: 4966
@@ -397,7 +397,7 @@ Abuse rate limits are not intended to interfere with legitimate use of the API.
 If your application triggers this rate limit, you'll receive an informative response:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Content-Type: application/json; charset=utf-8
 > Connection: close
 
@@ -450,7 +450,7 @@ Most responses return an `ETag` header. Many responses also return a `Last-Modif
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/user
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -460,7 +460,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -470,7 +470,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
@@ -487,7 +487,7 @@ Here's a sample request sent from a browser hitting `http://example.com`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
-HTTP/1.1 302 Found
+HTTP/2 302
 Access-Control-Allow-Origin: *
 Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
@@ -496,7 +496,7 @@ This is what the CORS preflight request looks like:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
-HTTP/1.1 204 No Content
+HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
diff --git a/translations/ko-KR/content/rest/reference/activity.md b/translations/ko-KR/content/rest/reference/activity.md
index 447883944f..7e7b089684 100644
--- a/translations/ko-KR/content/rest/reference/activity.md
+++ b/translations/ko-KR/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ Events are optimized for polling with the "ETag" header. If no new events have b
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
 # The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ To get a feed in Atom format, you must specify the `application/atom+xml` type i
 #### 응답
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ Notifications are optimized for polling with the `Last-Modified` header.  If the
 ``` shell
 # Add authentication to your requests
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
 # Pass the Last-Modified header exactly
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/ko-KR/content/rest/reference/emojis.md b/translations/ko-KR/content/rest/reference/emojis.md
index ec918c60c2..4f4dac4de9 100644
--- a/translations/ko-KR/content/rest/reference/emojis.md
+++ b/translations/ko-KR/content/rest/reference/emojis.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ko-KR/content/rest/reference/enterprise-admin.md b/translations/ko-KR/content/rest/reference/enterprise-admin.md
index a95395a085..53b66b3ec5 100644
--- a/translations/ko-KR/content/rest/reference/enterprise-admin.md
+++ b/translations/ko-KR/content/rest/reference/enterprise-admin.md
@@ -151,19 +151,6 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 {% endfor %}
 
 {% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
-
-## Encryption at rest
-
-You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## Admin stats
 
diff --git a/translations/ko-KR/content/rest/reference/git.md b/translations/ko-KR/content/rest/reference/git.md
index 722105c236..052bf87e08 100644
--- a/translations/ko-KR/content/rest/reference/git.md
+++ b/translations/ko-KR/content/rest/reference/git.md
@@ -19,7 +19,7 @@ The Git Database API gives you access to read and write raw Git objects to your
 
 ## Blobs
 
-A Git blob (binary large object) is the object type used to store the contents of each file in a repository. The file's SHA-1 hash is computed and stored in the blob object. These endpoints allow you to read and write [blob objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) to your Git database on {% data variables.product.product_name %}. Blobs leverage [these custom media types](#custom-media-types). You can read more about the use of media types in the API [here](/rest/overview/media-types).
+A Git blob (binary large object) is the object type used to store the contents of each file in a repository. The file's SHA-1 hash is computed and stored in the blob object. These endpoints allow you to read and write [blob objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) to your Git database on {% data variables.product.product_name %}. Blobs leverage [these custom media types](#custom-media-types-for-blobs). You can read more about the use of media types in the API [here](/rest/overview/media-types).
 
 ### Custom media types for blobs
 
diff --git a/translations/ko-KR/content/rest/reference/markdown.md b/translations/ko-KR/content/rest/reference/markdown.md
index e978876791..1d5c33f371 100644
--- a/translations/ko-KR/content/rest/reference/markdown.md
+++ b/translations/ko-KR/content/rest/reference/markdown.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ko-KR/content/rest/reference/meta.md b/translations/ko-KR/content/rest/reference/meta.md
index 6cd6fa2083..7d6ba6201c 100644
--- a/translations/ko-KR/content/rest/reference/meta.md
+++ b/translations/ko-KR/content/rest/reference/meta.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ko-KR/content/rest/reference/packages.md b/translations/ko-KR/content/rest/reference/packages.md
index 74f8d40c22..3a455e238f 100644
--- a/translations/ko-KR/content/rest/reference/packages.md
+++ b/translations/ko-KR/content/rest/reference/packages.md
@@ -4,7 +4,7 @@ product: '{% data reusables.gated-features.packages %}'
 versions:
   free-pro-team: '*'
 topics:
-  - api
+  - API
 ---
 
 The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
diff --git a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md
index 0dc7074456..873cd34565 100644
--- a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md
@@ -120,6 +120,9 @@ _검색_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _검색_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -678,6 +684,9 @@ _Teams_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### Permission on "pull requests"
 
@@ -767,6 +776,10 @@ _Reviews_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### Permission on "profile"
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### Permission on "repository hooks"
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
diff --git a/translations/ko-KR/content/rest/reference/repos.md b/translations/ko-KR/content/rest/reference/repos.md
index b93390a651..d823e51b7b 100644
--- a/translations/ko-KR/content/rest/reference/repos.md
+++ b/translations/ko-KR/content/rest/reference/repos.md
@@ -155,7 +155,8 @@ You can communicate that a transient environment no longer exists by setting its
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 ## Environments
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)."
+The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
diff --git a/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..6d88b32e86
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: About GitHub Sponsors
+intro: '{% data variables.product.prodname_sponsors %} allows the developer community to financially support the people and organizations who design, build, and maintain the open source projects they depend on, directly on {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### About {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+When you become a sponsored developer or sponsored organization, additional terms for {% data variables.product.prodname_sponsors %} apply. For more information, see "[GitHub Sponsors Additional Terms](/github/site-policy/github-sponsors-additional-terms)."
+
+### About the {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**Note:** {% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/github/site-policy/github-community-guidelines). Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}.
+
+To be eligible for the {% data variables.product.prodname_matching_fund %}, you must create a profile that will attract a community that will sustain you for the long term. For more information about creating a strong profile, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."
+
+Donations between sponsored developers will not be matched.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### Sharing feedback about {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### 더 읽을거리
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
+- "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..4c473a5869
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: Getting started with GitHub Sponsors
+intro: 'Learn about {% data variables.product.prodname_sponsors %} and how you can get involved as a sponsor or open source contributor.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..5899009f30
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: Quickstart for finding contributors to sponsor
+intro: Learn some best practices for finding open source contributors to sponsor.
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### Explore projects you depend on
+
+As you consider where to find open source contributors to sponsor, consider starting at https://github.com/sponsors/community.
+
+If you're logged in, the sponsors results will start with public dependencies that your repositories depend on.
+
+![The Babel open source project with highlighted text that says "4 of your repositories depend on this"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+You can also toggle which of your accounts to view results for and further filter or search.
+
+![Search options on sponsors community search page](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### Explore whom others sponsor
+
+You can see whom a user or organization sponsors on their {% data variables.product.prodname_dotcom %} profile page.
+
+### Consider how you benefit from different contributions
+
+Consider whether you benefit from the work of open source contributions, such as:
+ - 문서
+ - Design
+ - Translation
+ - Newsletters
+ - Code reviews
+ - 따라하기
+ - Mentoring
+ - Triaging issues and helping with project management
+ - Answering questions
+ - Event planning
+
+For more information on different types of open source contributions, see the [Open source guide](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+You can check if contributors you've benefited from have {% data variables.product.prodname_sponsors %} profiles by using search at https://github.com/sponsors/community.
+
+### Search for a specific project or contributor
+
+At https://github.com/sponsors/community, you can search by ecosystem, most used, recently updated, and more. You can filter search results for your personal user account or for organizations that you're a member of.
+
+### 다음 단계
+
+For more information on starting your sponsorship, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
diff --git a/translations/ko-KR/content/sponsors/guides.md b/translations/ko-KR/content/sponsors/guides.md
new file mode 100644
index 0000000000..2fc26a9cdc
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Sponsors guides
+shortTitle: 안내서
+intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/ko-KR/content/sponsors/index.md b/translations/ko-KR/content/sponsors/index.md
new file mode 100644
index 0000000000..efd1738d8a
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Sponsors Documentation
+shortTitle: GitHub Sponsors
+intro: 'Invest in the open source projects you depend on, support digital infrastructure, and make open source careers possible by sponsoring open source contributors and their projects. Build a {% data variables.product.prodname_sponsors %} profile and receive compensation for your open source work.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: 'sponsors'
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..676c329400
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: Configuring webhooks for events in your sponsored account
+intro: You can configure webhooks to alert you when you receive new sponsorships or existing sponsors make changes to their sponsorships.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### About webhooks for events in your sponsored account
+
+To monitor changes to your sponsorships, such as cancellations at the end of a pay period, you can create webhooks for your sponsored user or organization account. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship).
+
+### Managing webhooks for events in your sponsored account
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..8d05fd7671
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Getting started with the Sponsors GraphQL API
+intro: 'Using the GraphQL API, you can build custom integrations to manage or review your sponsorships.'
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+To get started with the GraphQL API, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+You can find the details about the Sponsors GraphQL API in the reference docs. For more information, see "[GraphQL reference](/graphql/reference)." We recommend using the GraphQL explorer to build your GraphQL calls. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer)."
diff --git a/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/index.md b/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..37e7055360
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: Integrating with GitHub Sponsors
+intro: 'As an open source contributor, you can build custom tools to manage your GitHub sponsorships.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..288ccf1de1
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: About GitHub Sponsors for open source contributors
+intro: 'If you provide value to an open source project, you can become a sponsored contributor to receive payments for your work.'
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+After you join {% data variables.product.prodname_sponsors %}, you can add a sponsor button to the open source repository you contribute to, to increase the visibility of your {% data variables.product.prodname_sponsors %} profile and other funding platforms. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."
+
+You can set a goal for your sponsorships. For more information, see "[Managing your sponsorship goal](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal)."
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### Sponsorship tiers
+
+{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+
+It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule.
+
+### Sponsorship payouts
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)."
+
+### Sharing feedback about {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### 더 읽을거리
+- "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..d67d4e0ae8
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: Contacting your sponsors
+intro: You can send an email to your sponsors who have opted in to receive updates about your work.
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### About sponsorship updates
+
+Your sponsors can choose whether they receive email updates about your work. For more information, see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)."
+
+For sponsored developer accounts, the update will come from your user account's primary email address. If you've enabled email address privacy on your user account, the update will come from `noreply@github.com` instead. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+
+### Contacting your sponsors
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..5fd8daa518
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: Editing your profile details for GitHub Sponsors
+intro: You can update the information that potential sponsors see about your work.
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### About sponsor profiles
+
+Your {% data variables.product.prodname_sponsors %} profile tells potential sponsors why they should support you. People see your sponsor profile when they click the **Sponsor** button on your profile. We recommend including the following information.
+
+- Open source work that you contribute to
+- Why you are committed to open source development
+
+### Editing your profile details
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..7e3d0358ca
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: Receiving sponsorships through GitHub Sponsors
+shortTitle: Receiving sponsorships
+intro: 'You or your organization can become a sponsored open source contributor to receive payments for your work, update your sponsorship details, and view and contact your sponsors.'
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..ad80a4facd
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Managing your payouts from GitHub Sponsors
+intro: 'You can view information about past and future payouts from {% data variables.product.prodname_sponsors %} and edit your bank information.'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### About payouts from {% data variables.product.prodname_sponsors %}
+
+You can only manage your payouts from {% data variables.product.prodname_sponsors %} if you are paid through Stripe Connect. If you are paid through ACH transfer or wire transfer for your sponsored user account, you will not see the **Payouts** tab on your sponsored open source contributor dashboard. Sponsored organizations can only use Stripe Connect for payouts. For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)."
+
+{% data reusables.sponsors.payout-info %}
+
+### Viewing and editing payout information
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..d0d1f06197
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: Managing your sponsorship goal
+intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### About sponsorship goals
+
+You can set a funding goal for your sponsored account and share the goal with your community. Goals help you understand the impact you have in the open source community and build up your presence in the {% data variables.product.prodname_sponsors %} program.
+
+Your goal can set a target for the number of sponsors you want to have or the amount of money you want to earn each month. You can only set one goal up at a time. After you reach a goal, you can set another goal.
+
+### Setting a goal
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Editing a goal
+
+When you edit a goal, you can't choose a goal you've already achieved. For example, if you already have 5 sponsors, you can't edit your goal so that you're aiming for 4 sponsors.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Retiring a goal
+
+After you retire a goal, you won't be able to reactivate the goal. You must create a new goal instead.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..7f5f951ecd
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: Managing your sponsorship tiers
+intro: 'You can add a new sponsorship tier, or edit or retire an existing tier.'
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### About sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### Adding a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### Editing or retiring a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### Enabling tiers with custom amounts
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### Disabling tiers with custom amounts
+
+You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired.
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..07a45c27b1
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: Setting up GitHub Sponsors for your organization
+intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization.
+
+To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. To the right of your organization, click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### Completing your sponsored organization profile
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Creating sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Submitting your bank information
+
+As a sponsored organization, you must receive payouts to a dedicated bank account for your organization in a supported region. You can get a business bank account through services like [Open Collective](https://opencollective.com/) and [Stripe Atlas](https://stripe.com/atlas). The region your organization legally operates in and the region of your bank account must match. The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+For more information about setting up Stripe Connect using Open Collective, see [Setting up {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) in the Open Collective Docs.
+
+### Submitting your tax information
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+
+Before your organization can become a sponsored organization, you must enable 2FA on your {% data variables.product.product_name %} account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+### Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### 더 읽을거리
+- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..1e28d8e153
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: Setting up GitHub Sponsors for your user account
+intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication on your {% data variables.product.prodname_dotcom %} account.'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+To join {% data variables.product.prodname_sponsors %} as an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. If you are an organization owner, you have more than one eligible account. Click **View your eligible accounts**, then in the list of accounts, find your user account.
+3. Click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
+
+### Completing your sponsored developer profile
+
+After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Creating sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Submitting your bank information
+
+If you live in a supported region, you can follow these instructions to submit your bank information by creating a Stripe Connect account. Your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### Submitting your tax information
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+
+Before you can become a sponsored developer, you must enable 2FA on your {% data variables.product.product_name %} account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+### Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. Click **Request approval**. ![Request approval button](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..538778e424
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Tax information for GitHub Sponsors
+intro: 'Sponsored developers and organizations must submit tax information to {% data variables.product.prodname_dotcom %} and are responsible for evaluating and paying their own taxes.'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are a taxpayer in the United States, you must submit a W-9 before you can receive payments. If you are a taxpayer in any other region besides the United States, you must submit a W-8BEN before you can receive payments. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms.
+
+If you are a taxpayer in the United States and earn more than $600 USD in a tax year, {% data variables.product.prodname_dotcom %} will send you a 1099 before January 31 of the next calendar year. We do not provide tax forms for international taxpayers.
+
+{% data variables.product.prodname_dotcom %} does not withhold tax from {% data variables.product.prodname_sponsors %} payments. Sponsored developers are responsible for evaluating and paying their own taxes.
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### 더 읽을거리
+
+- [Viewing your sponsors and sponsorships](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..ca39d19435
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: Viewing your sponsors and sponsorships
+intro: You can view and export detailed information and analytics about your sponsors and sponsorships.
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### About sponsors and sponsorships
+
+You can view analytics on your current and past sponsorships, the payments you've received from sponsors, and events, such as cancellations and sponsor tier changes for your sponsorships. You can also view activity such as new sponsorships, changes to sponsorships, and canceled sponsorships. You can filter the list of activities by date. You can also export sponsorship data for the account you're viewing in CSV or JSON format.
+
+### Viewing your sponsors and sponsorships
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. Optionally, to filter your sponsors by tier, use the **Filter** drop-down menu, click **Active tiers** or **Retired tiers**, and select a tier. ![Drop-down menu to filter by tier](/assets/images/help/sponsors/filter-drop-down.png)
+
+### Viewing recent sponsorship activity
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### Exporting your sponsorship data
+
+You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Export button](/assets/images/help/sponsors/export-all.png)
+1. Choose a time frame and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..1126a8c136
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: Attributing sponsorships to your organization
+intro: You can attribute the sponsorships paid by one of your organizations to another organization.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. Navigate to the organization whose sponsorships you want to attribute to another organization.
+2. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png)
+1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..5bfcaebe24
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: Sponsoring open source contributors
+intro: 'You can sponsor contributors, receive updates on developers and organizations you sponsor, and display a sponsor badge throughout {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..be89037d9a
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: Managing your sponsorship
+intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account.
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Managing the privacy setting for your sponsorship
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Managing email updates for your sponsorship
+
+You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address.
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### 더 읽을거리
+
+- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)"
+- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)"
diff --git a/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..611f1aa2c1
--- /dev/null
+++ b/translations/ko-KR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: Sponsoring an open source contributor
+intro: 'You can make a monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.'
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### About sponsorships
+
+{% data reusables.sponsors.sponsorship-details %}
+
+You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons.
+- Sustaining specific libraries that your organization's work depends on
+- Investing in the ecosystem you rely on as a organization (such as blockchain)
+- Developing brand awareness as an organization that values open source
+- Thanking open source developers for building libraries that complement the product your organization offers
+
+You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist).
+
+{% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)."
+
+When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)."
+
+If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_dotcom %} is not responsible for how developers represent themselves nor does {% data variables.product.prodname_dotcom %} endorse any sponsored open source projects. The claims are solely the responsibility of the developer receiving the funds. Make sure you trust a person before offering a sponsorship. For more information, see the [{% data variables.product.prodname_sponsors %} Additional Terms](/github/site-policy/github-sponsors-additional-terms).
+
+{% endnote %}
+
+### Sponsoring an account
+
+Before you can sponsor an account, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
+
+1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor.
+1. Navigate to your sponsorship dashboard for the account.
+   - To sponsor a developer, under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png)
+   - To sponsor an organization, to the right of the organization's name, click **Sponsor**. ![Sponsor button](/assets/images/help/sponsors/sponsor-org-button.png)
+1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![Edit payment button](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![Radio buttons to choose who can see your sponsorship](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/ko-KR/data/glossaries/external.yml b/translations/ko-KR/data/glossaries/external.yml
index d681f6b5fc..ee10588886 100644
--- a/translations/ko-KR/data/glossaries/external.yml
+++ b/translations/ko-KR/data/glossaries/external.yml
@@ -181,7 +181,7 @@
 - 
   term: 기본 분기
   description: >-
-    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called `main`, and is often the default branch.
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}, and is often the default branch.
 - 
   term: 의존도 그래프
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.{% else %}Name often chosen as an alternative to `master` for the default branch of a repository.{% endif %}
 - 
   term: master
   description: >-
-    The default branch in many Git repositories. By default, when you create a new Git repository on the command line a branch called `master` is created. Many tools now use an alternative name for the default branch. For example, when you create a new repository on GitHub the default branch is called `main`.
+    The default branch in many Git repositories. By default, when you create a new Git repository on the command line, a branch called `master` is created. Many tools now use an alternative name for the default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} For example, when you create a new repository on GitHub, the default branch is called `main`.{% endif %}
 - 
   term: 구성원 그래프
   description: 리포지토리의 모든 포크를 표시하는 리포지토리 그래프입니다.
diff --git a/translations/ko-KR/data/glossaries/internal.yml b/translations/ko-KR/data/glossaries/internal.yml
index 5044398dc7..e8524a489f 100644
--- a/translations/ko-KR/data/glossaries/internal.yml
+++ b/translations/ko-KR/data/glossaries/internal.yml
@@ -60,6 +60,10 @@
 - 
   term: Azure
   description: Microsoft 클라우드 컴퓨팅 플랫폼입니다.
+- 
+  term: Azure DevOps
+  description: >-
+    A Microsoft product offering source code hosting, issues, CI/CD pipelines, and other developer services. The on-premises version was formerly known as Team Foundation Server. The cloud-hosted version was formerly known as Visual Studio Team Services.
 - 
   term: 베어 리포지토리
   description: >-
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    소스 코드 관리 및 기타 팀 서비스를 제공하는 Microsoft 제품입니다.
+    The former name of a Microsoft product that provides source code management and other team services. Now known as Azure DevOps Server.
 - 
   term: Textile
   description: >-
diff --git a/translations/ko-KR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/ko-KR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..f3f59a1364
--- /dev/null
+++ b/translations/ko-KR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: Access to package version deletion
+  description: >-
+    This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: Deployments
+  description: >-
+    This preview adds support for deployments mutations and new deployments features.
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - More detailed information about a pull request's merge state.
+  description: >-
+    This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - Update multiple refs in a single operation.
+  description: This preview adds support for updating multiple refs in a single operation.
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: Project Event Details
+  description: >-
+    This preview adds project, project card, and project column details to project-related issue events.
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: Create content attachments
+  description: This preview adds support for creating content attachments.
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: Labels Preview
+  description: >-
+    This preview adds support for adding, updating, creating and deleting labels.
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: Import Project
+  description: This preview adds support for importing projects.
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Team Review Assignments Preview
+  description: >-
+    This preview adds support for updating the settings for team review assignment.
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/ko-KR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/ko-KR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..3d4deaabeb
--- /dev/null
+++ b/translations/ko-KR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
+    reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user` will be removed. Use the `assignee` field instead.'
+    reason: Assignees can now be mannequins.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
+    reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
+    reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: '`user` will be removed. Use the `assignee` field instead.'
+    reason: Assignees can now be mannequins.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
+    reason: '`Sponsorship.maintainer` will be removed.'
+    date: '2020-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All pending members consume a license
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.'
+    reason: Repository invitations can now be associated with an email, not only an invitee.
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: '`timeline` will be removed. Use Issue.timelineItems instead.'
+    reason: '`timeline` will be removed'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
+    reason: '`timeline` will be removed'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: '`INVITEE_LOGIN` will be removed.'
+    reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.'
+    reason: '`Sponsorship.sponsor` will be removed.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All members consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All outside collaborators consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All pending collaborators consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.'
+    reason: DRAFT state will be removed from this enum and `isDraft` should be used instead
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nplasterer
diff --git a/translations/ko-KR/data/learning-tracks/README.md b/translations/ko-KR/data/learning-tracks/README.md
index ec0f70309e..d8bd99c5fe 100644
--- a/translations/ko-KR/data/learning-tracks/README.md
+++ b/translations/ko-KR/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # Learning Tracks (aka Learning Paths)
 
-Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis.
\ No newline at end of file
+Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. For example, see https://docs.github.com/en/actions/guides.
+
+Learning track data for a product is defined in two places:
+
+1. A simple array of learning track names is defined in the product sublanding index page frontmatter.
+
+    For example, in `content/actions/guides/index.md`:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. Additional data for each track is defined in a YAML file named for the **product** in the `data` directory.
+
+    For example, in `data/learning-tracks/actions.yml`, each of the items from the content file's `learningTracks` array is represented with additional data such as `title`, `description`, and an array of `guides` links.
+
+    One learning track in this YAML **per version** must be designated as a "featured" learning track via `featured_track: true`, which will set it to appear at the top of the product sublanding page. A test will fail if this property is missing.
+
+    The `featured_track` property can be a simple boolean (i.e., `featured_track: true`) or it can be a string that includes versioning statements (e.g., `featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`). If you use versioning, you'll have multiple `featured_track`s per YML file, but make sure that only one will render in each currently supported version. A test will fail if there are more or less than one featured link for each version.
+
+Versioning for learning tracks is processed at page render time. The code lives in [`lib/learning-tracks.js`](lib/learning-tracks.js), which is called by `page.render()`. The processed learning tracks are then rendered by `layouts/product-sublanding.html`.
+
+The schema for validating the learning track YAML lives in [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) and is exercised by [`tests/content/lint-files.js`](tests/content/lint-files.js).
diff --git a/translations/ko-KR/data/learning-tracks/actions.yml b/translations/ko-KR/data/learning-tracks/actions.yml
index c825769cc8..d532f1a2e7 100644
--- a/translations/ko-KR/data/learning-tracks/actions.yml
+++ b/translations/ko-KR/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: 'Build and test code'
   description: 'You can create custom continuous integration (CI) workflows right in your repository.'
diff --git a/translations/ko-KR/data/learning-tracks/admin.yml b/translations/ko-KR/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..5e06a59c40
--- /dev/null
+++ b/translations/ko-KR/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: 'Get started with {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/ko-KR/data/release-notes/2-21/19.yml b/translations/ko-KR/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..5726fd8bda
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/2-21/19.yml
@@ -0,0 +1,18 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - User saw 500 error when executing git operations on an instance configured with LDAP authentication.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/ko-KR/data/release-notes/2-21/20.yml b/translations/ko-KR/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..4a3d11dfb6
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/2-21/20.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/ko-KR/data/release-notes/2-21/21.yml b/translations/ko-KR/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..2a76183f01
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/2-21/21.yml
@@ -0,0 +1,15 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/ko-KR/data/release-notes/2-21/6.yml b/translations/ko-KR/data/release-notes/2-21/6.yml
index d85f716f13e9ef45f34e1e88173b5394e06ac9ad..24127f581cae28c719bbc25d3035bb75529ebf5b 100644
GIT binary patch
delta 109
zcmWNHu?@mN5Cn5Fcd)XNh)fg2WEAihoZl<qJL~QdqAO~k5BI{4G||j4{m$QGP;_RD
zH@AiL6|@RL=<dnp@wp^+jg6UfLvxfzP^uPqpxlMlx&@2ynRv6U5Q9eaylG}%ujA<t
DjTI+M

delta 7
OcmX@4a#wl7T|od2<pYHP

diff --git a/translations/ko-KR/data/release-notes/2-22/11.yml b/translations/ko-KR/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..909f09ff83
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/2-22/11.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Syntax highlighting could fail due to the Treelights container running out of memory.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ko-KR/data/release-notes/2-22/12.yml b/translations/ko-KR/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..bb7d46505d
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/2-22/12.yml
@@ -0,0 +1,22 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ko-KR/data/release-notes/2-22/13.yml b/translations/ko-KR/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..ef4bbc46f3
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/2-22/13.yml
@@ -0,0 +1,20 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ko-KR/data/release-notes/3-0/0.yml b/translations/ko-KR/data/release-notes/3-0/0.yml
index 0eca470194..c9d3801bce 100644
--- a/translations/ko-KR/data/release-notes/3-0/0.yml
+++ b/translations/ko-KR/data/release-notes/3-0/0.yml
@@ -134,6 +134,7 @@ sections:
     - A race condition can cause dependency graph database migrations to appear to fail.
     - Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
   deprecations:
     - 
       heading: Deprecation of GitHub Enterprise Server 2.19
diff --git a/translations/ko-KR/data/release-notes/3-0/1.yml b/translations/ko-KR/data/release-notes/3-0/1.yml
index 3e7296628a..9df6976efc 100644
--- a/translations/ko-KR/data/release-notes/3-0/1.yml
+++ b/translations/ko-KR/data/release-notes/3-0/1.yml
@@ -45,6 +45,7 @@ sections:
     - 'Dependency graph fails to parse `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.'
     - 'Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.'
     - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.'
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/ko-KR/data/release-notes/3-0/2.yml b/translations/ko-KR/data/release-notes/3-0/2.yml
index e38aa78664..52e610b757 100644
--- a/translations/ko-KR/data/release-notes/3-0/2.yml
+++ b/translations/ko-KR/data/release-notes/3-0/2.yml
@@ -31,6 +31,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/ko-KR/data/release-notes/3-0/3.yml b/translations/ko-KR/data/release-notes/3-0/3.yml
index 4255a873dc..355b774734 100644
--- a/translations/ko-KR/data/release-notes/3-0/3.yml
+++ b/translations/ko-KR/data/release-notes/3-0/3.yml
@@ -30,6 +30,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
       To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
diff --git a/translations/ko-KR/data/release-notes/3-0/4.yml b/translations/ko-KR/data/release-notes/3-0/4.yml
index b3a39c1743..4b70a13ae5 100644
--- a/translations/ko-KR/data/release-notes/3-0/4.yml
+++ b/translations/ko-KR/data/release-notes/3-0/4.yml
@@ -23,3 +23,4 @@ sections:
     - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/ko-KR/data/release-notes/3-0/5.yml b/translations/ko-KR/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..1bcc84c956
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/3-0/5.yml
@@ -0,0 +1,27 @@
+---
+date: '2021-04-14'
+intro: 'The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Some logs were not included in the log forwarding configuration.
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Pages were not getting published when using custom CA certificate.
+    - Packages related subdomains were not showing up in the "Test domain settings" prompt for subdomain isolation.
+    - The `X-GitHub-Enterprise-Host` header sent with webhooks included a random string, rather than the hostname of the GitHub Enterprise Server instance that sent the HTTP POST payload.
+    - Upgrading from 2.22.x to 3.0.x would fail if GitHub Actions had previously been enabled, but disabled before the upgrade.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - reStructuredText (RST) rendering in the web UI would fail and instead displayed raw RST markup text.
+    - Email notifications for Secret Scanning alerts were not sent to authorized users when the Dependency Graph was not fully enabled.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+    - Jupyter notebooks with non-ASCII characters could fail to render.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/ko-KR/data/release-notes/3-0/6.yml b/translations/ko-KR/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..83604b5f77
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/3-0/6.yml
@@ -0,0 +1,30 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - Upgrades did not include the latest version of Actions runner properly installed.
+    - '`github-env` configuration could result in zombie processes.'
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - The Create Repository button was disabled for users who belonged to more than 50 organizations.
+    - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful.
+    - The `rms-packages` index was shown in the site admin dashboard.
+    - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form.
+    - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+    - Code Scanning backend services did not start up reliably after applying hotpatches.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ko-KR/data/release-notes/3-0/7.yml b/translations/ko-KR/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..4c176c0b41
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/3-0/7.yml
@@ -0,0 +1,23 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ko-KR/data/release-notes/3-1/0-rc1.yml b/translations/ko-KR/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..0682b06933
--- /dev/null
+++ b/translations/ko-KR/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security Secret Scanning
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository.
+
+          This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}:
+
+          - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37
+          - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)
+          - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets
+          - Updated the index view to made it easy to triage secrets in bulk
+          - Reduced the false positive rate on many patterns
+
+          Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+    - 
+      heading: GitHub Advanced Security billing improvements
+      notes:
+        - |
+          This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}:
+
+          - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+          - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+    - 
+      heading: Dependabot improvements
+      notes:
+        - |
+          This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}:
+
+          - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
+          - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository).
+          - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."'
+    - 
+      heading: GitHub Actions Workflow Visualization beta
+      notes:
+        - |
+
+          GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can:
+          - View and understand complex workflows
+          - Track progress of workflows in real-time
+          - Troubleshoot runs quickly by easily accessing logs and jobs metadata
+          - Monitor progress of deployment jobs and easily access deployment targets
+
+          For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+    - 
+      heading: OAuth 2.0 Device Authorization Grant
+      notes:
+        - |
+          [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser.
+
+          Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow.
+    - 
+      heading: Pull request auto-merge
+      notes:
+        - |
+          With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+    - 
+      heading: Custom notifications
+      notes:
+        - |
+          You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+  changes:
+    - 
+      heading: Administration Changes
+      notes:
+        - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+        - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+        - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+        - Check annotations older than four months will be archived.
+    - 
+      heading: Security Changes
+      notes:
+        - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).'
+        - SARIF upload support increased to a maximum of 5000 results per upload.
+    - 
+      heading: Developer Changes
+      notes:
+        - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to.
+        - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)."
+        - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."'
+        - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.'
+        - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.'
+    - 
+      heading: API Changes
+      notes:
+        - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning).
+        - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints.
+  known_issues:
+    - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.20
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.21
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of Legacy GitHub App Webhook Events
+      notes:
+        - 'Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).'
+    - 
+      heading: Deprecation of Legacy GitHub Apps Endpoint
+      notes:
+        - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0.  More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).
+    - 
+      heading: Deprecation of OAuth Application API
+      notes:
+        - 'GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).'
+    - 
+      heading: Deprecation of GitHub Actions short SHA support
+      notes:
+        - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/ko-KR/data/reusables/actions/actions-cli.md b/translations/ko-KR/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..9de328800e
--- /dev/null
+++ b/translations/ko-KR/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+For information on setting up {% data variables.product.prodname_cli %}, see "[Managing GitHub Actions with GitHub CLI](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)."
diff --git a/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md b/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..493e81cb45
--- /dev/null
+++ b/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.
+
+##### Examples using concurrency and the default behavior
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### Example using concurrency to cancel any in-progress job or run
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/ko-KR/data/reusables/actions/concurrency-beta.md b/translations/ko-KR/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..c3f2c9a831
--- /dev/null
+++ b/translations/ko-KR/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Concurrency is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/actions/enterprise-github-connect-warning.md b/translations/ko-KR/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..ce755253ef
--- /dev/null
+++ b/translations/ko-KR/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom %}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/actions/enterprise-no-internet-actions.md b/translations/ko-KR/data/reusables/actions/enterprise-no-internet-actions.md
index 9f2287cfee..e568edbd05 100644
--- a/translations/ko-KR/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/ko-KR/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} is designed to work in environments without internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+{% data variables.product.prodname_actions %} on {% data variables.product.product_name %} is designed to work in environments without full internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
diff --git a/translations/ko-KR/data/reusables/actions/forked-secrets.md b/translations/ko-KR/data/reusables/actions/forked-secrets.md
index 600bc85a95..3c6011328b 100644
--- a/translations/ko-KR/data/reusables/actions/forked-secrets.md
+++ b/translations/ko-KR/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.
+With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/ko-KR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..43937ba24a
--- /dev/null
+++ b/translations/ko-KR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.product_location %}:
+
+- **Committers** is the number of committers who contributed to at least one {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
+- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
+
+If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
+
+When you remove a user from your enterprise account, the user's license is freed within 24 hours.
+
+{% note %}
+
+**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
+
+{% endnote %}
diff --git a/translations/ko-KR/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/ko-KR/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..d0ea836b42
--- /dev/null
+++ b/translations/ko-KR/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Periodically you should check that your use is within your license capacity.
diff --git a/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md
index b6abfe68c7..1b77a9051e 100644
--- a/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% endif %}
+{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% elsif currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your Enterprise](/admin/advanced-security)."{% endif %}
 
 You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose.
 
diff --git a/translations/ko-KR/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/ko-KR/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..ff7d774004
--- /dev/null
+++ b/translations/ko-KR/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify:
+
+- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company.
+- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced.
+
+When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/ko-KR/data/reusables/advanced-security/ghas-helps-developers.md b/translations/ko-KR/data/reusables/advanced-security/ghas-helps-developers.md
index fcd5fb9586..e1b69b9a6e 100644
--- a/translations/ko-KR/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/ko-KR/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/ko-KR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..d447e24e28
--- /dev/null
+++ b/translations/ko-KR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+When you enable or disable {% data variables.product.prodname_advanced_security %} for repositories, {% data variables.product.prodname_dotcom %} displays an overview of changes to the use of your license. If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up.
+
+If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available.{% if currentVersion == "free-pro-team@latest" %} If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.{% endif %}
+
+As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal.
diff --git a/translations/ko-KR/data/reusables/cli/actions-cli-version.md b/translations/ko-KR/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..83cd5971dd
--- /dev/null
+++ b/translations/ko-KR/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+To access all of the {% data variables.product.prodname_actions %}-related commands, you must use version 1.9.0 or greater.
diff --git a/translations/ko-KR/data/reusables/cli/cli-auth.md b/translations/ko-KR/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..be9a823c3c
--- /dev/null
+++ b/translations/ko-KR/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} can authenticate using your {% data variables.product.prodname_dotcom %} account. Before running {% data variables.product.prodname_cli %} commands, you will need to authenticate by running `gh auth login`. For more information on command line authentication, see "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)."
diff --git a/translations/ko-KR/data/reusables/cli/cli-manual.md b/translations/ko-KR/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..dd2012d873
--- /dev/null
+++ b/translations/ko-KR/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+For more information about {% data variables.product.prodname_cli %}, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/).
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/cli/cli-repo.md b/translations/ko-KR/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..535b1d8e8c
--- /dev/null
+++ b/translations/ko-KR/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} commands must be run within the repository that you want to interact with, so you must first navigate to the directory containing the local copy of your repository. Alternatively, you can specify a repository by passing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY` or `--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY` or `--repo OWNER/REPOSITORY`{% endif %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Replace `HOSTNAME` with the name of {% data variables.product.product_location %}. {% endif %}Replace `OWNER` with owner of the repository. Replace `REPOSITORY` with the name of the repository.
diff --git a/translations/ko-KR/data/reusables/cli/download-update-cli.md b/translations/ko-KR/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..b26363cf45
--- /dev/null
+++ b/translations/ko-KR/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+To download or upgrade {% data variables.product.prodname_cli %}, follow the instructions in the [{% data variables.product.prodname_cli %} README](https://github.com/cli/cli#installation).
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/ko-KR/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/ko-KR/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/ko-KR/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/ko-KR/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..a101d1809f
--- /dev/null
+++ b/translations/ko-KR/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`, `csharp`, `go`, `java`, `javascript`, and `python`
diff --git a/translations/ko-KR/data/reusables/code-scanning/enabling-options.md b/translations/ko-KR/data/reusables/code-scanning/enabling-options.md
index 3e78b63452..137dd09d78 100644
--- a/translations/ko-KR/data/reusables/code-scanning/enabling-options.md
+++ b/translations/ko-KR/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">Running {% data variables.product.prodname_codeql %} code scanning in your CI system</a>").
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      Third&#8209;party
-    </td>
-    
-    <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or generated externally and uploaded to {% data variables.product.product_name %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Uploading a SARIF file to {% data variables.product.prodname_dotcom %}</a>").
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)").
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql %} code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
+{%- endif %}
+| Third&#8209;party | Using
+{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)").|
diff --git a/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md
index c5142332f6..6881be29fa 100644
--- a/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries.
+**Note:** SARIF upload supports a maximum of {% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries.
 
 {% endnote %}
diff --git a/translations/ko-KR/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..52dda51137
--- /dev/null
+++ b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**Note:** Uploading SARIF data to display as {% data variables.product.prodname_code_scanning %} results in {% data variables.product.product_name %} is supported for organization-owned repositories with {% data variables.product.prodname_GH_advanced_security %} enabled{% if currentVersion == "free-pro-team@latest" %}, and public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/ko-KR/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..5c772293bc
--- /dev/null
+++ b/translations/ko-KR/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.product.product_location %}.
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/codespaces/about-personalization.md b/translations/ko-KR/data/reusables/codespaces/about-personalization.md
index 8f5ccbdb99..958370ebd8 100644
--- a/translations/ko-KR/data/reusables/codespaces/about-personalization.md
+++ b/translations/ko-KR/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-You can also personalize aspects of the codespace environment for any codespace that your account creates. Personalization can include shell preferences and additional tools.
+You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. Personalization can include shell preferences and additional tools.
diff --git a/translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md b/translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..39b29dc4a0
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+You can forward ports in your codespace to test and debug your application.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..8031bfb4af
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index c49f29679d..5e0618af02 100644
--- a/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md b/translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..475114c1c5
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Each of these has a different level of resources and a different billing tier.<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**Note:** {% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types:
+
+* **Basic** for updating a file and raising a pull request
+* **Standard** for editing a website
+* **Premium** for high compute tasks such as data analysis
diff --git a/translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..87bfa539ff
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users.
+
+For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..fed860897b
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/ko-KR/data/reusables/codespaces/rebuild-command.md b/translations/ko-KR/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..ea9e45b032
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/recovery-mode.md b/translations/ko-KR/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..fa4e73d013
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/release-stage.md b/translations/ko-KR/data/reusables/codespaces/release-stage.md
index 2fd3475ccd..57e551dd72 100644
--- a/translations/ko-KR/data/reusables/codespaces/release-stage.md
+++ b/translations/ko-KR/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. During the beta period, {% data variables.product.prodname_dotcom %} does not make any guarantees about the availability of {% data variables.product.prodname_codespaces %}. For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
+**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
 
 {% endnote %}
diff --git a/translations/ko-KR/data/reusables/codespaces/secret-precedence.md b/translations/ko-KR/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..582b91c1aa
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/secrets-naming.md b/translations/ko-KR/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..eddb8aa7f5
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+The following rules apply to secret names:
+
+* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
+* Secret names must not start with the `GITHUB_` prefix.
+* Secret names must not start with a number.
+* Secret names are not case-sensitive.
+* Secret names must be unique at the level they are created at.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/secrets-on-start.md b/translations/ko-KR/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..c4a5bf3b41
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it.
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md b/translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..90b3503dcd
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/source-control-display.md b/translations/ko-KR/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..09917cd3c8
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. In the Activity Bar, click the **Source Control** view.
+
+  ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/type-port-label.md b/translations/ko-KR/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..498c9eb752
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index 59c85e47d7..afb626e71c 100644
--- a/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-You can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..a5e98437c0
--- /dev/null
+++ b/translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**.
+
+  !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md
index d405e1471a..d3a12e3d59 100644
--- a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@ The following table shows, for each package manager:
 | Composer        | `composer`       | v1, v2                         |        **✓**         |       **✓**        |           |
 | Docker          | `docker`         | v1                             |        **✓**         |       **✓**        |           |
 | Hex             | `mix`            | v1                             |                      |       **✓**        |           |
-| elm-package     | `elm`            | v0.18, v0.19                   |        **✓**         |       **✓**        |           |
+| elm-package     | `elm`            | v0.19                          |        **✓**         |       **✓**        |           |
 | git submodule   | `gitsubmodule`   | N/A (no version)               |        **✓**         |       **✓**        |           |
 | GitHub Actions  | `github-actions` | N/A (no version)               |        **✓**         |       **✓**        |           |
 | Go modules      | `gomod`          | v1                             |        **✓**         |       **✓**        |   **✓**   |
diff --git a/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md
index 54d745b497..3d29c028b4 100644
--- a/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@ When you create a pull request from a forked repository to the base repository,
 
 Workflows don't run on forked repositories by default. You must enable GitHub Actions in the **Actions** tab of the forked repository.
 
+{% if currentVersion == "free-pro-team@latest"%}
+When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve running workflows on the pull request. For more information, see "[Approving workflow runs from public forks](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)."
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} The permissions for the `GITHUB_TOKEN` in forked repositories is read-only. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
 
 {% note %}
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-report-download.md
index 34834c681c..5ac6ab4bb1 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. Optionally, click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![Download CSV report](/assets/images/help/billing/actions-packages-report-download.png)
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![Download CSV report](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/change_plan_duration.md b/translations/ko-KR/data/reusables/dotcom_billing/change_plan_duration.md
index a43cb113de..31f59222d7 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. Under "Billing overview", click **Change to yearly billing** or **Change to monthly billing**. ![Billing overview change plan button](/assets/images/help/billing/change-plan-duration-link.png)
+1. Under "Current monthly bill" or "Current yearly bill", click **Switch to yearly billing** or **Switch to monthly billing**. ![Billing overview change plan button](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/choose_org_plan.md b/translations/ko-KR/data/reusables/dotcom_billing/choose_org_plan.md
index 80d23b08e6..2121e37d1c 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. If you're upgrading from {% data variables.product.prodname_free_team %}, under "Upgrading to", select a product. ![Upgrade button](/assets/images/help/billing/upgrade-to-product.png)
+1. Under "Compare plans", you can compare the features of each plan. Depending on your current plan and what plan you have chosen, click either **Upgrade to Team** or **Upgrade to Enterprise**. ![Compare plans and upgrade](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/enter-payment-info.md b/translations/ko-KR/data/reusables/dotcom_billing/enter-payment-info.md
index 461de210a0..436d92d9df 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. Under "Billing information", choose to pay with a credit card or PayPal. ![Switch Billing payment methods](/assets/images/help/billing/billing_switch_payments.png)
+1. Under "Payment method", choose to pay with a credit card or PayPal. ![Switch Billing payment methods](/assets/images/help/billing/billing_switch_payments.png)
 1. Complete the payment information form, then click **Submit**.
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/lfs-add-data.md b/translations/ko-KR/data/reusables/dotcom_billing/lfs-add-data.md
index 5769f06c4a..8f4a7c8ca7 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the Edit drop-down and click **Add more data packs**. ![Add more data button](/assets/images/help/billing/data-pack-purchase-more.png)
+1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**. ![Add more data button](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/ko-KR/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..4f2bd7bf2d
--- /dev/null
+++ b/translations/ko-KR/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. At the top of the page, under "Payment information", click **Manage spending limit**. ![Manage spending limit link](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/next_billing_date.md b/translations/ko-KR/data/reusables/dotcom_billing/next_billing_date.md
index c415f04fea..4b342eafae 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. Under "Billing overview", review when your next payment is due. ![Next billing date](/assets/images/help/billing/settings_billing_next_payment.png)
+1. At the top of the page, under "Next payment due", review when your next payment is due. ![Next billing date](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/review-pending-changes.md b/translations/ko-KR/data/reusables/dotcom_billing/review-pending-changes.md
index 49820941df..bd29edbd23 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. Under "Subscriptions," review your pending changes. ![Subscriptions section of billing settings listing any pending subscription changes](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. Under "Current plan", review your pending changes. ![Subscriptions section of billing settings listing any pending subscription changes](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/update_payment_method.md b/translations/ko-KR/data/reusables/dotcom_billing/update_payment_method.md
index 4f735635cd..0aa1c98a2f 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. Under "Billing overview", click **Update payment method**. ![Update payment method button](/assets/images/help/billing/update_payment_method.png)
+1. At the top of the page, under "Payment information", click **Update payment method**. ![Update payment method button](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/upgrade_org.md b/translations/ko-KR/data/reusables/dotcom_billing/upgrade_org.md
index 60ea8fef5c..aba4840ee5 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. If you're upgrading from {% data variables.product.prodname_free_team %}, click **Upgrade options**. If you're upgrading from {% data variables.product.prodname_team %}, use the **Edit** drop-down and click **Upgrade**. ![Upgrade options button](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. Click **Upgrade** next to "Current plan".
diff --git a/translations/ko-KR/data/reusables/dotcom_billing/view-payment-history.md b/translations/ko-KR/data/reusables/dotcom_billing/view-payment-history.md
index 3bc9031627..9bec769655 100644
--- a/translations/ko-KR/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/ko-KR/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. Under "Billing overview", click **View payment history**. ![View payment history link](/assets/images/help/billing/view-payment-history-link.png)
+1. At the top of the page, under "Next payment due", click **View payment history**. ![View payment history link](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/add-a-domain.md b/translations/ko-KR/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..f6a4648a23
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. Click **Add a domain**. ![Add a domain button](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/ko-KR/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..e30ede90e5
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/ko-KR/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..0783f95521
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+You can confirm that the websites and email addresses listed on the profiles of any organization owned by your enterprise account are controlled by your enterprise by verifying the domains. Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %}
+
+Organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain.
+
+After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/domains-approving.md b/translations/ko-KR/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/domains-removing.md b/translations/ko-KR/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/domains-verifying.md b/translations/ko-KR/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..49018320b4
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output.
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. Optionally, after the "Verified" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service. ![Verified badge](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..4087e5cdd0
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+The domains can be inherited from the enterprise account or configured for the specific organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..eb771a1f37
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. Click **Save**.
diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/ko-KR/data/reusables/enterprise-accounts/verified-domains-tab.md
index 35420a6888..85644af45c 100644
--- a/translations/ko-KR/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/ko-KR/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. Under "Settings", click **Verified domains**. !["Verified domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/ko-KR/data/reusables/enterprise_deprecation/deprecation_details.md
index a6ccee5e90..2d220a0ba0 100644
--- a/translations/ko-KR/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/ko-KR/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1 +1 @@
-No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">upgrade to the latest version of GitHub Enterprise</a>. For help with the upgrade, <a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">contact GitHub Enterprise support</a>.
+No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">upgrade to the latest version of GitHub Enterprise</a>. For help with the upgrade, <a href="https://enterprise.github.com/support">contact GitHub Enterprise support</a>.
diff --git a/translations/ko-KR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/ko-KR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..728c8da3a1
--- /dev/null
+++ b/translations/ko-KR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
+
+Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
+
+Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
+
+| User licenses                  |                           vCPUs |                                  Memory |                        Attached storage | Root storage |
+|:------------------------------ | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
+| Trial, demo, or 10 light users |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
+| 10 to 3,000                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
+| 3,000 to 5000                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
+| 5,000 to 8000                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
+| 8,000 to 10,000+               | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md
index 4b1379243e..e7d45c6fb3 100644
--- a/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/ko-KR/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Warning**: Changing this setting will cause {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} to restart. You should time this change carefully, to minimize downtime.
+**Warning**: Changing this setting will cause user-facing services on {% data variables.product.prodname_ghe_server %} to restart. You should time this change carefully, to minimize downtime for users.
 
 {% endwarning %}
diff --git a/translations/ko-KR/data/reusables/gated-features/actions-shared.md b/translations/ko-KR/data/reusables/gated-features/actions-shared.md
index d5bceb9ab1..1b9eb6926d 100644
--- a/translations/ko-KR/data/reusables/gated-features/actions-shared.md
+++ b/translations/ko-KR/data/reusables/gated-features/actions-shared.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. 
+{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. 
diff --git a/translations/ko-KR/data/reusables/gated-features/code-scanning.md b/translations/ko-KR/data/reusables/gated-features/code-scanning.md
index 775fa28256..3786dad893 100644
--- a/translations/ko-KR/data/reusables/gated-features/code-scanning.md
+++ b/translations/ko-KR/data/reusables/gated-features/code-scanning.md
@@ -1,5 +1,5 @@
-{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
-{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository.
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
 {%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_code_scanning_capc %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
 {%- else %}
diff --git a/translations/ko-KR/data/reusables/gated-features/ghas.md b/translations/ko-KR/data/reusables/gated-features/ghas.md
index fcf1b455c7..166bbffcbe 100644
--- a/translations/ko-KR/data/reusables/gated-features/ghas.md
+++ b/translations/ko-KR/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_GH_advanced_security %} is also included in {% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %} and in all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
+{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/gated-features/github-insights.md b/translations/ko-KR/data/reusables/gated-features/github-insights.md
index f99859ae15..fb6b9703b2 100644
--- a/translations/ko-KR/data/reusables/gated-features/github-insights.md
+++ b/translations/ko-KR/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %} is available with {% data variables.product.prodname_ghe_one %}. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."
+{% data variables.product.prodname_insights %} is available with {% data variables.product.prodname_ghe_one %}. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/gated-features/packages.md b/translations/ko-KR/data/reusables/gated-features/packages.md
index 46b66987c9..3222088079 100644
--- a/translations/ko-KR/data/reusables/gated-features/packages.md
+++ b/translations/ko-KR/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}.
+{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}.
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access {% data variables.product.prodname_github_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/ko-KR/data/reusables/gated-features/secret-scanning.md b/translations/ko-KR/data/reusables/gated-features/secret-scanning.md
index f67bcdf4e4..8ae85ccf2f 100644
--- a/translations/ko-KR/data/reusables/gated-features/secret-scanning.md
+++ b/translations/ko-KR/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_secret_scanning_caps %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
-{% endif %}
\ No newline at end of file
+{%- else %}
+{% data variables.product.prodname_secret_scanning_caps %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/github-actions/forked-write-permission.md b/translations/ko-KR/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..3fe9804246
--- /dev/null
+++ b/translations/ko-KR/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+You can use the `permissions` key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the **Send write tokens to workflows from pull requests** option in the {% data variables.product.prodname_actions %} settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/github-actions/github-token-available-permissions.md b/translations/ko-KR/data/reusables/github-actions/github-token-available-permissions.md
new file mode 100644
index 0000000000..4e5ca65fe7
--- /dev/null
+++ b/translations/ko-KR/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+Available scopes and access values:
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
+
+You can use the following syntax to define read or write access for all of the available scopes:
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/github-actions/github-token-permissions.md b/translations/ko-KR/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..88604df1dc
--- /dev/null
+++ b/translations/ko-KR/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+The `GITHUB_TOKEN` secret is set to an access token for the repository each time a job in a workflow begins. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 743020588d..c5a1bf2f45 100644
--- a/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret.
+Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access granted to the `GITHUB_TOKEN`.{% endif %}
diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index 0cb603cd97..0508627063 100644
--- a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **경고**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
diff --git a/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md b/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md
index e14f648811..d3443cc757 100644
--- a/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**Warning**: Ubuntu 16.04 is being deprecated. If any of your workflows use Ubuntu 16.04, migrate to Ubuntu 20.04 or 18.04. For more information, see [the blog post](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021).
+
+{% endwarning %}
+
 | Virtual environment  | YAML workflow label                |
 | -------------------- | ---------------------------------- |
 | Windows Server 2019  | `windows-latest` or `windows-2019` |
+| Windows Server 2016  | `windows-2016`                     |
 | Ubuntu 20.04         | `ubuntu-latest` or `ubuntu-20.04`  |
 | Ubuntu 18.04         | `ubuntu-18.04`                     |
-| Ubuntu 16.04         | `ubuntu-16.04`                     |
 | macOS Big Sur 11.0   | `macos-11.0`                       |
 | macOS Catalina 10.15 | `macos-latest` or `macos-10.15`    |
diff --git a/translations/ko-KR/data/reusables/github-actions/workflow-permissions-intro.md b/translations/ko-KR/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..88382e0d54
--- /dev/null
+++ b/translations/ko-KR/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." You can choose between a restricted set of permissions as the default or a permissive setting. 
diff --git a/translations/ko-KR/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/ko-KR/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..14ee1f9279
--- /dev/null
+++ b/translations/ko-KR/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/reference/workflow-syntax-for-github-actions#permissions). 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/gpg/x-509-key.md b/translations/ko-KR/data/reusables/gpg/x-509-key.md
index 00a5c1c896..7bb93711ea 100644
--- a/translations/ko-KR/data/reusables/gpg/x-509-key.md
+++ b/translations/ko-KR/data/reusables/gpg/x-509-key.md
@@ -30,7 +30,7 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
   $ git config --local gpg.program smimesign
   ```
   If you're using an X.509 key that matches your committer identity, you can begin signing commits and tags.
-4. If you're not using an X.509 key that matches your commiter identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
+4. If you're not using an X.509 key that matches your committer identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
   ```shell
   $ smimesign --list-keys
   ```
diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/verification-status-check.md b/translations/ko-KR/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..85b8a05d3c
--- /dev/null
+++ b/translations/ko-KR/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see "[Checking your commit and tag signature verification status](/articles/checking-your-commit-and-tag-signature-verification-status)."
diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..bb9ea14675
--- /dev/null
+++ b/translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Vigilant mode is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..3e6f0179b2
--- /dev/null
+++ b/translations/ko-KR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| 상태                          | 설명                                                                                                                                                                                                                                                                                       |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Verified**                | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.                                                                                                                                                       |
+| **Partially&nbsp;verified** | The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified. |
+| **Unverified**              | Any of the following is true:<br>- The commit is signed but the signature could not be verified.<br>- The commit is not signed and the committer has enabled vigilant mode.<br>- The commit is not signed and an author has enabled vigilant mode.<br>           |
diff --git a/translations/ko-KR/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/ko-KR/data/reusables/marketplace/cancel-app-billing-settings.md
index ff68cb20f8..335490b598 100644
--- a/translations/ko-KR/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/ko-KR/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. Use the **Edit** drop-down and click **Cancel plan**. ![Cancel link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to cancel, use the **Edit** drop-down and click **Cancel plan**. ![Cancel link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ko-KR/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/ko-KR/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index 7008b67f98..b9901ac4a8 100644
--- a/translations/ko-KR/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/ko-KR/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. Under "Subscriptions", next to the free trial you'd like to cancel, use the Edit drop-down and click **Cancel plan**.
+1. Next to the free trial you'd like to cancel, use the **Edit** drop-down and click **Cancel plan**.
diff --git a/translations/ko-KR/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/ko-KR/data/reusables/marketplace/downgrade-app-billing-settings.md
index 249f85d344..10370e87c2 100644
--- a/translations/ko-KR/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/ko-KR/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Under "Your subscriptions", next to the app you'd like to downgrade, use the Edit drop-down and click **Change plan** or **Cancel plan**. ![Edit link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you'd like to downgrade, use the **Edit** drop-down and click **Change plan** or **Cancel plan**. ![Edit link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ko-KR/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/ko-KR/data/reusables/marketplace/upgrade-app-billing-settings.md
index 630c6656ae..89945a1cf1 100644
--- a/translations/ko-KR/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/ko-KR/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Use the **Edit** drop-down and click **Change plan**. ![Edit drop-down in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to upgrade, use the **Edit** drop-down and click **Change plan**. ![Edit drop-down in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md b/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..e5d59aceea
--- /dev/null
+++ b/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}issues, pulls requests, releases, security alerts, or discussions{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}issues, pull requests, releases, or discussions{% endif %}
diff --git a/translations/ko-KR/data/reusables/notifications/email-restrictions-verification.md b/translations/ko-KR/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..c30f3f4092
--- /dev/null
+++ b/translations/ko-KR/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
diff --git a/translations/ko-KR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/ko-KR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index 6b3de47d4c..dc6894c3f7 100644
--- a/translations/ko-KR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/ko-KR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-You can choose the delivery method for notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+You can choose the delivery method and frequency of notifications about
+{% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts.
+{% else %}
+You can choose the delivery method for notifications about
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/organizations/add-a-domain.md b/translations/ko-KR/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..a775029654
--- /dev/null
+++ b/translations/ko-KR/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. Click **Add a domain**. ![Add a domain button](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/ko-KR/data/reusables/organizations/billing_plans.md b/translations/ko-KR/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..6fc2306e57
--- /dev/null
+++ b/translations/ko-KR/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. In your organization's Settings sidebar, click **Billing & plans**. ![Billing settings](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/ko-KR/data/reusables/organizations/continue-verifying-domain.md b/translations/ko-KR/data/reusables/organizations/continue-verifying-domain.md
index 0f99787752..f5169707f9 100644
--- a/translations/ko-KR/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/ko-KR/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. To the right of the domain that's pending verification, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Continue verifying**. ![Continue verifying domain button](/assets/images/help/organizations/continue-verifying-domain.png)
-10. Click **Verify domain**. ![Verify domain button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. Click **Verify**. ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/organizations/domains-approve-domain.md b/translations/ko-KR/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/ko-KR/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/ko-KR/data/reusables/organizations/domains-approve-it-instead.md b/translations/ko-KR/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/ko-KR/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/ko-KR/data/reusables/organizations/verified-domains.md b/translations/ko-KR/data/reusables/organizations/verified-domains.md
index 534d60d588..9714304429 100644
--- a/translations/ko-KR/data/reusables/organizations/verified-domains.md
+++ b/translations/ko-KR/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. In the left sidebar, click **Verified domains**. ![Verified domains button](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/ko-KR/data/reusables/package_registry/about-packaging-and-actions.md b/translations/ko-KR/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..15bfa7d693
--- /dev/null
+++ b/translations/ko-KR/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,31 @@
+### Packaging in continuous integration workflows
+
+A packaging step is a common part of a continuous integration or continuous delivery workflow. Creating a package at the end of a continuous integration workflow can help during code reviews on a pull request.
+
+After building and testing your code, a packaging step can produce a runnable or deployable artifact. Depending on the kind of application you're building, this package can be downloaded locally for manual testing, made available for users to download, or deployed to a staging or production environment.
+
+For example, a continuous integration workflow for a Java project may run `mvn package` to produce a JAR file. Or, a CI workflow for a Node.js application may create a Docker container.
+
+Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request.
+
+### Workflows for publishing packages
+
+In addition to uploading packaging artifacts for testing in a continuous integration workflow, you can create workflows that build your project and publish packages to a package registry.
+
+* **Publish packages to {% data variables.product.prodname_registry %}**
+  {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. You can choose to share your packages with all of {% data variables.product.prodname_dotcom %}, or private packages to share with collaborators or an organization. For more information, see "[Introduction to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages)."
+
+  You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.
+
+* **Publish packages to a package registry**  
+  For many projects, publishing to a package registry is performed whenever a new version of a project is released. For example, a project that produces a JAR file may upload new releases to the Maven Central repository. Or, a .NET project may produce a nuget package and upload it to the NuGet Gallery.
+
+  You can automate this by creating a workflow that publishes packages to a package registry on every release creation. For more information, see "[Creating releases](/github/administering-a-repository/creating-releases)."
diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/ko-KR/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..a02c0f89d8
--- /dev/null
+++ b/translations/ko-KR/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md b/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md
index 3bb18dfd14..5abadfbc3d 100644
--- a/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md
+++ b/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md
@@ -1,14 +1,7 @@
-You need an access token to publish, install, and delete packages. You can use a personal access token to authenticate with your username directly to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs.
+You need an access token to publish, install, and delete packages.
 
-{% if currentVersion == "free-pro-team@latest" %}
-To authenticate using a
-{% data variables.product.prodname_actions %} workflow:
-- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`.
-- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you can use a `GITHUB_TOKEN` or a personal access token. We strongly recommend you use a `GITHUB_TOKEN` to avoid unncessary access to your repositories.
+You can use a personal access token (PAT) to authenticate to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a PAT, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
 
-For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
-
-{% else %}
-To authenticate to
-{% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`.
-{% endif %}
+To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
+- `GITHUB_TOKEN` to publish packages associated with the workflow repository.
+- a PAT to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index 1581f1cf5e..46aad43e24 100644
--- a/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. Using the CLI for your container type, sign in to the
-{% data variables.product.prodname_github_container_registry %} service at `ghcr.io`.
+{% data variables.product.prodname_container_registry %} service at `ghcr.io`.
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index 666a293400..38994e051e 100644
--- a/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -2,9 +2,9 @@
 
 PATs can grant broad access to your account. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}.
 
-To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
+To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
 
-For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
+For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md b/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md
index 6bd738198e..2b790bdbb1 100644
--- a/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)."
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use the {% data variables.product.prodname_container_registry %}, you must enable the feature preview. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" and "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
 {% endnote %}
diff --git a/translations/ko-KR/data/reusables/package_registry/docker-vs-container-registry.md b/translations/ko-KR/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..60ba872bf2
--- /dev/null
+++ b/translations/ko-KR/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**Comparing the Docker registry and the {% data variables.product.prodname_container_registry %}:**
+- The {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) offers improved performance for containers and will supercede the Docker registry in the future.
+- You can migrate your Docker images and workflows from the Docker registry  (`docker.pkg.github.com`)  to the {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) for granular permissions, container storage optimization, and more. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."
+
+{% endnote %}
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md
index 73a07a040b..67608dc1e2 100644
--- a/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will offer improved container support in a future {% data variables.product.product_name %} release.{% elsif currentVersion == "free-pro-team@latest" %} now offers improved container support. For more information, see "[About GitHub Container Registry](/packages/guides/about-github-container-registry)." To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/guides/migrating-to-github-container-registry-for-docker-images)" and "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)."{% endif %}
+**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will be superseded in a future {% data variables.product.product_name %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif currentVersion == "free-pro-team@latest" %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)." {% endif %}
 
 {% endwarning %}
diff --git a/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md
index 3b74dd6c78..3b8032849e 100644
--- a/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)."
+**Note:** Before you can use the {% data variables.product.prodname_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ko-KR/data/reusables/package_registry/github-token-security-over-pat.md b/translations/ko-KR/data/reusables/package_registry/github-token-security-over-pat.md
index bee4d1039b..ca6ffe0360 100644
--- a/translations/ko-KR/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/ko-KR/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_github_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
+The {% data variables.product.prodname_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
 
-For more information about `GITHUB_TOKEN`, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
+For more information about `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
diff --git a/translations/ko-KR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/ko-KR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..9bc7ee0d6e
--- /dev/null
+++ b/translations/ko-KR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below use this type of permissions:
+- Docker registry (`docker.pkg.github.com`)
+- npm registry
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+The Container registry (`ghcr.io`) offers granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account.
+{% endif %}
+
+For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)"{% if currentVersion == "free-pro-team@latest" %} or "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."{% endif %}.
diff --git a/translations/ko-KR/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/ko-KR/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..773bfbfb5e
--- /dev/null
+++ b/translations/ko-KR/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+If you have admin permissions to a container image, you can set the access permissions for the container image to private or public. Public images allow anonymous access and can be pulled without authentication or signing in via the CLI.
+
+As an admin, you can also grant access permissions for a container image that are separate from the permissions you've set at the organization and repository levels.
+
+For container images published and owned by a user account, you can give any person an access role. For container images published and owned by an organization, you can give any person or team in the organization an access role.
+
+| Permission | Access description                                                                                                                               |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| read       | Can download package. <br> Can read package metadata.                                                                                      |
+| write      | Can upload and download this package. <br> Can read and write package metadata.                                                            |
+| admin      | Can upload, download, delete, and manage this package. <br> Can read and write package metadata. <br> Can grant package permissions. |
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/profile/access_org.md b/translations/ko-KR/data/reusables/profile/access_org.md
index 908518fb60..9356bd4ee8 100644
--- a/translations/ko-KR/data/reusables/profile/access_org.md
+++ b/translations/ko-KR/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. On the left side of your profile page, under "Organizations", click the icon for your organization. ![organization icons](/assets/images/help/profile/profile_orgs_box.png)
+1. In the top right corner of {% data variables.product.prodname_dotcom %}, click your profile photo, then click **Your organizations**. ![Your organizations in the profile menu](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/profile/org_settings.md b/translations/ko-KR/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..4c7f5b7078
--- /dev/null
+++ b/translations/ko-KR/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. Click **Settings** next to the organization. ![The settings button](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/profile/user_profile_page_block_or_report.md b/translations/ko-KR/data/reusables/profile/user_profile_page_block_or_report.md
index 65e0ff56f1..32f5c49ac1 100644
--- a/translations/ko-KR/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/ko-KR/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. In the left sidebar, under the user's profile picture, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block or report user**. ![Block or report user link](/assets/images/help/profile/profile-block-or-report-button.png)
+1. In the left sidebar, below the user's profile information, click **Block or Report**. ![Block or report link](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/ko-KR/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/ko-KR/data/reusables/repositories/actions-scheduled-workflow-example.md
index 40d253284b..3dae8f356e 100644
--- a/translations/ko-KR/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/ko-KR/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -6,6 +6,6 @@ This example triggers the workflow every day at 5:30 and 17:30 UTC:
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/ko-KR/data/reusables/repositories/request-changes-tips.md b/translations/ko-KR/data/reusables/repositories/request-changes-tips.md
index 3012e9f3c7..2a2b27a916 100644
--- a/translations/ko-KR/data/reusables/repositories/request-changes-tips.md
+++ b/translations/ko-KR/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - Repository owners and administrators can merge a pull request even if it hasn't received an approving review, or if a reviewer who requested changes has left the organization or is unavailable.
 - If both required reviews and stale review dismissal are enabled and a code-modifying commit is pushed to the branch of an approved pull request, the approval is dismissed. The pull request must be reviewed and approved again before it can be merged.
 - When several open pull requests each have a head branch pointing to the same commit, you won’t be able to merge them if one or both have a pending or rejected review.
+- Pull request authors cannot approve their own pull requests.
 
 {% endtip %}
diff --git a/translations/ko-KR/data/reusables/repositories/security-guidelines.md b/translations/ko-KR/data/reusables/repositories/security-guidelines.md
index 739a556bb3..a6cd502721 100644
--- a/translations/ko-KR/data/reusables/repositories/security-guidelines.md
+++ b/translations/ko-KR/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-You can create a security policy to give people instructions for responsibly reporting security vulnerabilities in your project. For more information, see "[Adding a security policy to your repository](/articles/adding-a-security-policy-to-your-repository)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+You can create a security policy to give people instructions for reporting security vulnerabilities in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
 {% endif %}
diff --git a/translations/ko-KR/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/ko-KR/data/reusables/repositories/sidebar-dependabot-alerts.md
index 58d37a45ad..2b642f5ebf 100644
--- a/translations/ko-KR/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/ko-KR/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**. ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**.{% if currentVersion == "free-pro-team@latest" %} ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/ko-KR/data/reusables/secret-scanning/beta.md b/translations/ko-KR/data/reusables/secret-scanning/beta.md
index 714002d52b..6adcb7d57e 100644
--- a/translations/ko-KR/data/reusables/secret-scanning/beta.md
+++ b/translations/ko-KR/data/reusables/secret-scanning/beta.md
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} is in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of secret scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} was in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of {% data variables.product.prodname_secret_scanning %}, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
 
 
 {% endnote %}
diff --git a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index e75538fe3d..3e52aeadb6 100644
--- a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| Partner                   | Supported secret                       | API slug                                 |
-| ------------------------- | -------------------------------------- | ---------------------------------------- |
-| n/a                       | JSON Web Token                         | json_web_token                         |
-| n/a                       | OAuth Client Credential                | api_credential_assignment              |
-| Adafruit IO               | Adafruit IO Key                        | adafruit_io_key                        |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID            | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Alibaba Cloud Access Key Secret        | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID               | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Amazon AWS Secret Access Key           | aws_secret_access_key                  |
-| Asana                     | Asana Personal Access Token            | asana_personal_access_token            |
-| Atlassian                 | Atlassian API Token                    | atlassian_api_token                    |
-| Atlassian                 | Atlassian JSON Web Token               | atlassian_jwt                            |
-| Azure                     | Azure DevOps Personal Access Token     | azure_devops_personal_access_token   |
-| Azure                     | Azure SAS Token                        | azure_sas_token                        |
-| Azure                     | Azure Service Management Certificate   | azure_management_certificate           |
-| Azure                     | Azure SQL Connection String            | azure_sql_connection_string            |
-| Azure                     | Azure Storage Account Key              | azure_storage_account_key              |
-| Clojars                   | Clojars Deploy Token                   | clojars_deploy_token                   |
-| CloudBees CodeShip        | CloudBees CodeShip Credential          | codeship_credential                      |
-| Databricks                | Databricks Access Token                | databricks_access_token                |
-| Discord                   | Discord Bot Token                      | discord_bot_token                      |
-| Doppler                   | Doppler Personal Token                 | doppler_personal_token                 |
-| Doppler                   | Doppler Service Token                  | doppler_service_token                  |
-| Doppler                   | Doppler CLI Token                      | doppler_cli_token                      |
-| Doppler                   | Doppler SCIM Token                     | doppler_scim_token                     |
-| Dropbox                   | Dropbox Access Token                   | dropbox_access_token                   |
-| Dropbox                   | Dropbox Short Lived Access Token       | dropbox_short_lived_access_token     |
-| Dynatrace                 | Dynatrace Access Token                 | dynatrace_access_token                 |
-| Dynatrace                 | Dynatrace Internal Token               | dynatrace_internal_token               |
-| Facebook                  | Facebook Access Token                  | facebook_access_token                  |
-| Finicity                  | Finicity App Key                       | finicity_app_key                       |
-| Frame.io                  | Frame.io JSON Web Token                | frameio_jwt                              |
-| Frame.io                  | Frame.io Developer Token               | frameio_developer_token                |
-| GitHub                    | GitHub SSH Private Key                 | github_ssh_private_key                 |
-| GitHub                    | GitHub Personal Access Token           | github_personal_access_token           |
-| GitHub                    | GitHub App Installation Access Token   | github_app_installation_access_token |
-| GoCardless                | GoCardless Live Access Token           | gocardless_live_access_token           |
-| GoCardless                | GoCardless Sandbox Access Token        | gocardless_sandbox_access_token        |
-| Google Cloud              | Google API Key                         | google_api_key                         |
-| Google Cloud              | Google Cloud Private Key ID            | google_cloud_private_key_id          |
-| Grafana                   | Grafana API Key                        | grafana_api_key                        |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token | terraform_api_token                    |
-| Hubspot                   | Hubspot API Key                        | hubspot_api_key                        |
-| Intercom                  | Intercom Access Token                  | intercom_access_token                  |
-| Lob                       | Lob Live API Key                       | lob_live_api_key                       |
-| Lob                       | Lob Test API Key                       | lob_test_api_key                       |
-| Mailchimp                 | Mailchimp API Key                      | mailchimp_api_key                      |
-| Mailgun                   | Mailgun API Key                        | mailgun_api_key                        |
-| npm                       | npm Access Token                       | npm_access_token                       |
-| NuGet                     | NuGet API Key                          | nuget_api_key                          |
-| Palantir                  | Palantir JSON Web Token                | palantir_jwt                             |
-| Postman                   | Postman API Key                        | postman_api_key                        |
-| Proctorio                 | Proctorio Consumer Key                 | proctorio_consumer_key                 |
-| Proctorio                 | Proctorio Linkage Key                  | proctorio_linkage_key                  |
-| Proctorio                 | Proctorio Registration Key             | proctorio_registration_key             |
-| Proctorio                 | Proctorio Secret Key                   | proctorio_secret_key                   |
-| Pulumi                    | Pulumi Access Token                    | pulumi_access_token                    |
-| PyPI                      | PyPI API Token                         | pypi_api_token                         |
-| RubyGems                  | RubyGems API Key                       | rubygems_api_key                       |
-| Samsara                   | Samsara API Token                      | samsara_api_token                      |
-| Samsara                   | Samsara OAuth Access Token             | samsara_oauth_access_token             |
-| SendGrid                  | SendGrid API Key                       | sendgrid_api_key                       |
-| Shopify                   | Shopify App Shared Secret              | shopify_app_shared_secret              |
-| Shopify                   | Shopify Access Token                   | shopify_access_token                   |
-| Shopify                   | Shopify Custom App Access Token        | shopify_custom_app_access_token      |
-| Shopify                   | Shopify Private App Password           | shopify_private_app_password           |
-| Slack                     | Slack API Token                        | slack_api_token                        |
-| Slack                     | Slack Incoming Webhook URL             | slack_incoming_webhook_url             |
-| Slack                     | Slack Workflow Webhook URL             | slack_workflow_webhook_url             |
-| SSLMate                   | SSLMate API Key                        | sslmate_api_key                        |
-| SSLMate                   | SSLMate Cluster Secret                 | sslmate_cluster_secret                 |
-| Stripe                    | Stripe API Key                         | stripe_api_key                         |
-| Stripe                    | Stripe Live API Secret Key             | stripe_live_secret_key                 |
-| Stripe                    | Stripe Test API Secret Key             | stripe_test_secret_key                 |
-| Stripe                    | Stripe Live API Restricted Key         | stripe_live_restricted_key             |
-| Stripe                    | Stripe Test API Restricted Key         | stripe_test_restricted_key             |
-| Tencent Cloud             | Tencent Cloud Secret ID                | tencent_cloud_secret_id                |
-| Twilio                    | Twilio Account String Identifier       | twilio_account_sid                     |
-| Twilio                    | Twilio API Key                         | twilio_api_key                         |
+| Partner | Supported secret | API slug |
+| ------- | ---------------- | -------- |
+|         |                  |          |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index ebc268a20d..701b6505b7 100644
--- a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| Partner                   | Supported secret                                                            |
-| ------------------------- | --------------------------------------------------------------------------- |
-| Adafruit IO               | Adafruit IO Key                                                             |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair                      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair                         |
-| Atlassian                 | Atlassian API Token                                                         |
-| Atlassian                 | Atlassian JSON Web Token                                                    |
-| Azure                     | Azure DevOps Personal Access Token | azure_devops_personal_access_token |
-| Azure                     | Azure SAS Token | azure_sas_token                                         |
-| Azure                     | Azure Service Management Certificate | azure_management_certificate       |
-| Azure                     | Azure SQL Connection String | azure_sql_connection_string                 |
-| Azure                     | Azure Storage Account Key | azure_storage_account_key                     |
-| Clojars                   | Clojars Deploy Token                                                        |
-| CloudBees CodeShip        | CloudBees CodeShip Credential                                               |
-| Databricks                | Databricks Access Token                                                     |
-| Datadog                   | Datadog API Key                                                             |
-| Discord                   | Discord Bot Token                                                           |
-| Doppler                   | Doppler Personal Token                                                      |
-| Doppler                   | Doppler Service Token                                                       |
-| Doppler                   | Doppler CLI Token                                                           |
-| Doppler                   | Doppler SCIM Token                                                          |
-| Dropbox                   | Dropbox Access Token                                                        |
-| Dropbox                   | Dropbox Short Lived Access Token                                            |
-| Dynatrace                 | Dynatrace Access Token                                                      |
-| Dynatrace                 | Dynatrace Internal Token                                                    |
-| Finicity                  | Finicity App Key                                                            |
-| Frame.io                  | Frame.io JSON Web Token                                                     |
-| Frame.io                  | Frame.io Developer Token                                                    |
-| GitHub                    | GitHub SSH Private Key                                                      |
-| GitHub                    | GitHub Personal Access Token                                                |
-| GitHub                    | GitHub App Installation Access Token                                        |
-| GoCardless                | GoCardless Live Access Token                                                |
-| GoCardless                | GoCardless Sandbox Access Token                                             |
-| Google Cloud              | Google API Key                                                              |
-| Google Cloud              | Google Cloud Private Key ID                                                 |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                                      |
-| Hubspot                   | Hubspot API Key                                                             |
-| Mailchimp                 | Mailchimp API Key                                                           |
-| Mailchimp                 | Mandrill API Key                                                            |
-| Mailgun                   | Mailgun API Key                                                             |
-| MessageBird               | MessageBird API Key                                                         |
-| npm                       | npm Access Token                                                            |
-| NuGet                     | NuGet API Key                                                               |
-| Palantir                  | Palantir JSON Web Token                                                     |
-| Plivo                     | Plivo Auth Token                                                            |
-| Postman                   | Postman API Key                                                             |
-| Proctorio                 | Proctorio Consumer Key                                                      |
-| Proctorio                 | Proctorio Linkage Key                                                       |
-| Proctorio                 | Proctorio Registration Key                                                  |
-| Proctorio                 | Proctorio Secret Key                                                        |
-| Pulumi                    | Pulumi Access Token                                                         |
-| PyPI                      | PyPI API Token                                                              |
-| RubyGems                  | RubyGems API Key                                                            |
-| Samsara                   | Samsara API Token                                                           |
-| Samsara                   | Samsara OAuth Access Token                                                  |
-| Shopify                   | Shopify App Shared Secret                                                   |
-| Shopify                   | Shopify Access Token                                                        |
-| Shopify                   | Shopify Custom App Access Token                                             |
-| Shopify                   | Shopify Private App Password                                                |
-| Slack                     | Slack API Token                                                             |
-| Slack                     | Slack Incoming Webhook URL                                                  |
-| Slack                     | Slack Workflow Webhook URL                                                  |
-| SSLMate                   | SSLMate API Key                                                             |
-| SSLMate                   | SSLMate Cluster Secret                                                      |
-| Stripe                    | Stripe Live API Secret Key                                                  |
-| Stripe                    | Stripe Test API Secret Key                                                  |
-| Stripe                    | Stripe Live API Restricted Key                                              |
-| Stripe                    | Stripe Test API Restricted Key                                              |
-| Tencent Cloud             | Tencent Cloud Secret ID                                                     |
-| Twilio                    | Twilio Account String Identifier                                            |
-| Twilio                    | Twilio API Key                                                              |
+| Partner                   | Supported secret                                       |
+| ------------------------- | ------------------------------------------------------ |
+| Adafruit IO               | Adafruit IO Key                                        |
+| Adobe                     | Adobe Device Token                                     |
+| Adobe                     | Adobe Service Token                                    |
+| Adobe                     | Adobe Short-Lived Access Token                         |
+| Adobe                     | Adobe JSON Web Token                                   |
+| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair |
+| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair    |
+| Atlassian                 | Atlassian API Token                                    |
+| Atlassian                 | Atlassian JSON Web Token                               |
+| Azure                     | Azure DevOps Personal Access Token                     |
+| Azure                     | Azure SAS Token                                        |
+| Azure                     | Azure Service Management Certificate                   |
+| Azure                     | Azure SQL Connection String                            |
+| Azure                     | Azure Storage Account Key                              |
+| Clojars                   | Clojars Deploy Token                                   |
+| CloudBees CodeShip        | CloudBees CodeShip Credential                          |
+| Databricks                | Databricks Access Token                                |
+| Datadog                   | Datadog API Key                                        |
+| Discord                   | Discord Bot Token                                      |
+| Doppler                   | Doppler Personal Token                                 |
+| Doppler                   | Doppler Service Token                                  |
+| Doppler                   | Doppler CLI Token                                      |
+| Doppler                   | Doppler SCIM Token                                     |
+| Dropbox                   | Dropbox Access Token                                   |
+| Dropbox                   | Dropbox Short Lived Access Token                       |
+| Dynatrace                 | Dynatrace Access Token                                 |
+| Dynatrace                 | Dynatrace Internal Token                               |
+| Finicity                  | Finicity App Key                                       |
+| Frame.io                  | Frame.io JSON Web Token                                |
+| Frame.io                  | Frame.io Developer Token                               |
+| GitHub                    | GitHub Personal Access Token                           |
+| GitHub                    | GitHub OAuth Access Token                              |
+| GitHub                    | GitHub Refresh Token                                   |
+| GitHub                    | GitHub App Installation Access Token                   |
+| GitHub                    | GitHub SSH Private Key                                 |
+| GoCardless                | GoCardless Live Access Token                           |
+| GoCardless                | GoCardless Sandbox Access Token                        |
+| Google Cloud              | Google API Key                                         |
+| Google Cloud              | Google Cloud Private Key ID                            |
+| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                 |
+| Hubspot                   | Hubspot API Key                                        |
+| Mailchimp                 | Mailchimp API Key                                      |
+| Mailchimp                 | Mandrill API Key                                       |
+| Mailgun                   | Mailgun API Key                                        |
+| MessageBird               | MessageBird API Key                                    |
+| npm                       | npm Access Token                                       |
+| NuGet                     | NuGet API Key                                          |
+| OpenAI                    | OpenAI API Key                                         |
+| Palantir                  | Palantir JSON Web Token                                |
+| Plivo                     | Plivo Auth Token                                       |
+| Postman                   | Postman API Key                                        |
+| Proctorio                 | Proctorio Consumer Key                                 |
+| Proctorio                 | Proctorio Linkage Key                                  |
+| Proctorio                 | Proctorio Registration Key                             |
+| Proctorio                 | Proctorio Secret Key                                   |
+| Pulumi                    | Pulumi Access Token                                    |
+| PyPI                      | PyPI API Token                                         |
+| RubyGems                  | RubyGems API Key                                       |
+| Samsara                   | Samsara API Token                                      |
+| Samsara                   | Samsara OAuth Access Token                             |
+| SendGrid                  | SendGrid API Key                                       |
+| Shopify                   | Shopify App Shared Secret                              |
+| Shopify                   | Shopify Access Token                                   |
+| Shopify                   | Shopify Custom App Access Token                        |
+| Shopify                   | Shopify Private App Password                           |
+| Slack                     | Slack API Token                                        |
+| Slack                     | Slack Incoming Webhook URL                             |
+| Slack                     | Slack Workflow Webhook URL                             |
+| SSLMate                   | SSLMate API Key                                        |
+| SSLMate                   | SSLMate Cluster Secret                                 |
+| Stripe                    | Stripe Live API Secret Key                             |
+| Stripe                    | Stripe Test API Secret Key                             |
+| Stripe                    | Stripe Live API Restricted Key                         |
+| Stripe                    | Stripe Test API Restricted Key                         |
+| Tencent Cloud             | Tencent Cloud Secret ID                                |
+| Twilio                    | Twilio Account String Identifier                       |
+| Twilio                    | Twilio API Key                                         |
diff --git a/translations/ko-KR/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/ko-KR/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..ecb8f968d6
--- /dev/null
+++ b/translations/ko-KR/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,5 @@
+{% if currentVersion == "free-pro-team@latest" %}
+For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."
+{% else %}
+For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."
+{% endif %}
diff --git a/translations/ko-KR/data/reusables/security/displayed-information.md b/translations/ko-KR/data/reusables/security/displayed-information.md
index 02f38c36db..744735db2d 100644
--- a/translations/ko-KR/data/reusables/security/displayed-information.md
+++ b/translations/ko-KR/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
 When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
 
 - All the existing repositories will have the selected configuration.
-- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" %}
 - We use the permissions to scan for manifest files to apply the relevant services.
 - You'll see information on your dependency graph.
-- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} and raise pull requests{% endif %}. 
+- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} and create pull requests{% endif %}. 
diff --git a/translations/ko-KR/data/reusables/supported-languages/C.md b/translations/ko-KR/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/Cpp.md b/translations/ko-KR/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/Cs.md b/translations/ko-KR/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/go.md b/translations/ko-KR/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..40bd61946e
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/java.md b/translations/ko-KR/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/javascript.md b/translations/ko-KR/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/php.md b/translations/ko-KR/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/products-table-header.md b/translations/ko-KR/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..743339ee69
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/python.md b/translations/ko-KR/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/ruby.md b/translations/ko-KR/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/scala.md b/translations/ko-KR/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/supported-languages/typescript.md b/translations/ko-KR/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/ko-KR/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/ko-KR/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/ko-KR/data/reusables/user_settings/keeping_your_email_address_private.md
index cabc7cc611..1359461643 100644
--- a/translations/ko-KR/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/ko-KR/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. To keep your email address private when performing web-based Git operations, click **Keep my email address private**. ![Image of checkbox to keep your email address private](/assets/images/help/settings/email_privacy.png)
+5. To keep your email address private when performing web-based Git operations, click **Keep my email addresses private**. ![Image of checkbox to keep your email address private](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/ko-KR/data/reusables/user_settings/payment-info-link.md b/translations/ko-KR/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..8d441f3be4
--- /dev/null
+++ b/translations/ko-KR/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. At the top of the page, click **Payment information**. ![Payment information link](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/ko-KR/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/ko-KR/data/reusables/webhooks/code_scanning_alert_event_properties.md
index 3a584bebff..f0dc1af18f 100644
--- a/translations/ko-KR/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/ko-KR/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,6 +1,6 @@
-| 키            | 유형    | 설명                                                                                                                                                                              |
-| ------------ | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `동작`         | `문자열` | The action that was performed. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                                |
-| `경고`         | `개체`  | The code scanning alert involved in the event.                                                                                                                                  |
-| `ref`        | `문자열` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty. |
-| `commit_oid` | `문자열` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty.    |
+| 키            | 유형    | 설명                                                                                                                                                                             |
+| ------------ | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `동작`         | `문자열` | The action that was performed. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                               |
+| `경고`         | `개체`  | The code scanning alert involved in the event.                                                                                                                                 |
+| `ref`        | `문자열` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty. |
+| `commit_oid` | `문자열` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty.    |
diff --git a/translations/ko-KR/data/reusables/webhooks/create_properties.md b/translations/ko-KR/data/reusables/webhooks/create_properties.md
index fbfd2d8019..1d71338fad 100644
--- a/translations/ko-KR/data/reusables/webhooks/create_properties.md
+++ b/translations/ko-KR/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| 키               | 유형    | 설명                                                                                                                                                                                                                                    |
-| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `문자열` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                        |
-| `ref_type`      | `문자열` | The type of Git ref object created in the repository. Can be either `branch` or `tag`.                                                                                                                                                |
-| `master_branch` | `문자열` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
-| `설명`            | `문자열` | The repository's current description.                                                                                                                                                                                                 |
+| 키               | 유형    | 설명                                                                                                                                                                                                                                   |
+| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ref`           | `문자열` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                       |
+| `ref_type`      | `문자열` | The type of Git ref object created in the repository. Can be either `branch` or `tag`.                                                                                                                                               |
+| `master_branch` | `문자열` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
+| `설명`            | `문자열` | The repository's current description.                                                                                                                                                                                                |
diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md
index ea7542abb1..02d9836e9c 100644
--- a/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| 키    | 유형    | 설명                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ---- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `동작` | `문자열` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. |
+| 키    | 유형    | 설명                                                                     |
+| ---- | ----- | ---------------------------------------------------------------------- |
+| `동작` | `문자열` | The action that was performed. Can be one of:<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's tracking branch is synchronized with the source branch for the pull request, which happens when the source branch is updated.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/ko-KR/data/reusables/webhooks/sponsorship_short_desc.md b/translations/ko-KR/data/reusables/webhooks/sponsorship_short_desc.md
index 2f62ffe8d8..bf99f9f71a 100644
--- a/translations/ko-KR/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/ko-KR/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)".
+Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml
index d953af3c0d..8e20246f81 100644
--- a/translations/ko-KR/data/ui.yml
+++ b/translations/ko-KR/data/ui.yml
@@ -20,7 +20,7 @@ homepage:
   version_picker: 버전
 toc:
   getting_started: 시작하기
-  popular_articles: Popular
+  popular: Popular
   guides: 안내서
   whats_new: What's new
 pages:
@@ -54,14 +54,6 @@ contribution_cta:
   button: Make a contribution
   or: Or,
   to_guidelines: learn how to contribute.
-enterprise_releases_list:
-  title: Enterprise Server Releases
-  currently_supported: Currently supported
-  currently_supported_message: See <a href="https://github.com/enterprise">GitHub Enterprise</a> for information about the latest release.
-  deprecated: Deprecated
-  deprecated_message: 'These docs remain available but are no longer maintained:'
-  deprecated_developer: Deprecated on developer.github.com
-  deprecated_developer_message: 'These docs remain available on the legacy <a href="https://developer.github.com">developer site</a> but are no longer maintained:'
 products:
   graphql:
     reference:
@@ -127,19 +119,36 @@ footer:
       press: 보도 자료
       shop: 쇼핑
 product_landing:
-  quick_start: Quickstart
-  reference_guides: Reference guides
+  quickstart: Quickstart
+  reference: Reference
   overview: 개요
+  guides: 안내서
+  code_examples: Code examples
+  search_code_examples: Search code examples
+  show_more: Show more
+  explore_people_and_projects: Explore people and projects
+  sorry: Sorry, there is no result for
+  no_example: It looks like we don't have an example that fits your filter.
+  try_another: Try another filter or add your code example.
+  no_result: Sorry, there is no guide that match your filter.
+  learn: Learn how to add a code example
+  communities_using_discussions: Communities using discussions
+  add_your_community: Add your community
+  sponsor_community: GitHub Sponsors community
+  supported_releases: Supported releases
+  release_notes_for: Release notes for
+  upgrade_from: Upgrade from
+  browse_all_docs: Browse all docs
+  explore_release_notes: Explore release notes
 product_sublanding:
   start: Start
   start_path: Start path
-  learning_paths: '{{ allProducts[currentProduct].name }} learning paths'
+  learning_paths: '{{ productMap[currentProduct].name }} learning paths'
   learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject.
-  guides: '{{ allProducts[currentProduct].name }} guides'
+  guides: '{{ productMap[currentProduct].name }} guides'
   more_guides: more guides
   load_more: Load more guides
-  all_guides: 'All {{ allProducts[currentProduct].name }} guides'
-  no_result: Sorry, there is no guide that match your filter.
+  all_guides: 'All {{ productMap[currentProduct].name }} guides'
   filters:
     type: 유형
     topic: Topic
@@ -154,3 +163,10 @@ learning_track_nav:
   prevGuide: Previous guide
   nextGuide: Next guide
 contributor_callout: This article is contributed and maintained by
+toggle_images:
+  off: Images are off, click to show
+  on: Images are on, click to hide
+  hide_single: Hide image
+  show_single: Show image
+scroll_button:
+  scroll_to_top: Scroll to top
diff --git a/translations/ko-KR/data/variables/codespaces_code_examples.yml b/translations/ko-KR/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..00958245ab
--- /dev/null
+++ b/translations/ko-KR/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.js sample project
+  description: Try a Node.js project with a custom dev container
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - development containers
+- 
+  title: Python sample project
+  description: Try a Python project with a custom dev container
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - development containers
+- 
+  title: Java sample project
+  description: Try a Java project with a custom dev container
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - development containers
+- 
+  title: Go sample project
+  description: Try a Go project with a custom dev container
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - development containers
+- 
+  title: Rust sample project
+  description: Try a Rust project with a custom dev container
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - development containers
+- 
+  title: PHP sample project
+  description: Try a PHP project with a custom dev container
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - development containers
diff --git a/translations/ko-KR/data/variables/migrations.yml b/translations/ko-KR/data/variables/migrations.yml
index 15201e4a03..61cd8c80be 100644
--- a/translations/ko-KR/data/variables/migrations.yml
+++ b/translations/ko-KR/data/variables/migrations.yml
@@ -4,4 +4,4 @@ user_migrations_intro: >-
 organization_migrations_intro: >-
   The organization migrations API lets you move a repository from GitHub to {% data variables.product.prodname_ghe_server %}.
 source_imports_intro: >-
-  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Server source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
+  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Version Control source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
diff --git a/translations/ko-KR/data/variables/product.yml b/translations/ko-KR/data/variables/product.yml
index 53af633f87..6fe5cc433d 100644
--- a/translations/ko-KR/data/variables/product.yml
+++ b/translations/ko-KR/data/variables/product.yml
@@ -56,6 +56,7 @@ prodname_pages: 'GitHub 페이지'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub 마켓플레이스'
 prodname_github_app: 'GitHub 앱'
@@ -77,8 +78,7 @@ prodname_debug: 'GitHub Debug'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
-prodname_github_container_registry: 'GitHub Container Registry'
-prodname_container_registry: 'container registry'
+prodname_container_registry: 'Container registry'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -91,7 +91,6 @@ prodname_advanced_security: 'Advanced Security'
 prodname_security_center: 'Security Center'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Visual Studio Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'GitHub Community Support'
diff --git a/translations/ko-KR/data/variables/release_candidate.yml b/translations/ko-KR/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/ko-KR/data/variables/release_candidate.yml
+++ b/translations/ko-KR/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/ko-KR/data/variables/sponsors_user_examples.yml b/translations/ko-KR/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..92800edaf3
--- /dev/null
+++ b/translations/ko-KR/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chayn helps women experiencing abuse find the right information and support they need to take control of their lives.
+- 
+  user: foosel
+  description: '👋 I''m Gina, and I''m mostly known for being the creator and main developer of OctoPrint 🐙.'
+- 
+  user: dayhaysoos
+  description: What's up? I'm Nick. I'm an engineer who has a new-found passion for removing friction from the e-commerce developer experience.
+- 
+  user: yyx990803
+  description: I'm working fulltime on Vue.js, a frontend JavaScript framework for building web applications, and Vite, a modern web build tool.
+- 
+  user: calebporzio
+  description: '🚶‍♂️I left my day job in Jan 2019 to pursue open-source. Since then, I''ve built Laravel Livewire, AlpineJS, and a bunch of other stuff.'
+- 
+  user: kjaymiller
+  description: Hi Y'all I'm Jay! 👋 I'm a Marine Corps Veteran turned developer that's been actively coding since 2014. I'm also involved in the productivity space where I can be found helping people with automations for some of their favorite apps and tools.
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index 3020f0c473..fa3014c365 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md
index e2cb88949c..4507bfa8d9 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md
index 2a190963e4..a70222adf5 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md
@@ -215,21 +215,21 @@ O fluxo de trabalho a seguir usa a ação completa "hello world" no repositório
 {% raw %}
 **.github/workflows/main.yml**
 ```yaml
-em: [push]
+on: [push]
 
-empregos:
+jobs:
   hello_world_job:
-    runs-on: ubuntu-mais recente
-    nome: Um trabalho para dizer olá
-    passos:
-    - nome: Olá passo de ação mundial
-      id: Olá
-      usa: ações/hello-world-javascript-action@v1.1
-      com:
-        quem cumprimentar: 'Mona, o Octocat'
-    # Use a saída do passo 'olá'
-    - nome: Obtenha o tempo de saída
-      executado: echo "O tempo era ${{ steps.hello.outputs.time }}"
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
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 3ace31d26a..a5ed645b3a 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
@@ -171,7 +171,7 @@ Neste exemplo, o `cleanup.js` é executado apenas nos executores baseados no Lin
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 #### `post`
@@ -197,7 +197,7 @@ Por exemplo, este `cleanup.js` só será executado em executores baseados no Lin
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 ### `runs` para ações em etapas de execução compostas
@@ -291,11 +291,11 @@ O aplicativo especificado com a sintaxe [`using`](#runsusing) executará esse ar
 Neste exemplo, a ação `pre-entrypoint:` executa um script denominado `setup.sh`:
 
 ```yaml
-executa:
+runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
@@ -319,11 +319,11 @@ Para obter mais informações sobre como o `entrypoint` é executado, consulte "
 **Opcional**Permite que você execute um script de cleanup, uma vez finalizada a ação`runs.entrypoint`. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação. Porque {% data variables.product.prodname_actions %} executa o script dentro de um novo contêiner usando a mesma imagem-base, o estado do momento da execução é diferente do contêiner principal do `entrypoint`. Você pode acessar qualquer estado que precisar na área de trabalho, em `HOME` ou como variável `STATE_`. A ação `post-entrypoint:` é sempre executada por padrão, mas você pode substituí-la usando [`post-if`](#post-if).
 
 ```yaml
-executa:
+runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/pt-BR/content/actions/guides/about-continuous-integration.md b/translations/pt-BR/content/actions/guides/about-continuous-integration.md
index e11baa847e..bc09ef60d4 100644
--- a/translations/pt-BR/content/actions/guides/about-continuous-integration.md
+++ b/translations/pt-BR/content/actions/guides/about-continuous-integration.md
@@ -48,11 +48,13 @@ Além de ajudá-lo a configurar fluxos de trabalho de CI para seu projeto, você
 Para obter uma definição de termos comuns, consulte "[Conceitos básicos de {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)".
 
 ### Linguagens compatíveis
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} oferece modelos de fluxo de trabalho de CI para uma variedade de linguagens e estruturas.
 
 Pesquise a lista completa dos modelos de fluxo de trabalho de CI oferecidos por {% data variables.product.product_name %} no repositório {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) {% else %} e no repositório `actions/starter-workflows` em {% data variables.product.product_location %}{% endif %}.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### Ignorar execuções de fluxo de trabalho
 
 Se você deseja impedir temporariamente que um fluxo de trabalho seja acionado, pode adicionar uma instrução para ignorar a mensagem de commit. Os fluxos de trabalho que seriam acionados `on: push` ou `on: pull_request` não serão acionado se você adicionar qualquer uma das strings a seguir para a mensagem de commit em um push, ou o commit HEAD de um pull request:
@@ -72,6 +74,7 @@ Você não conseguirá fazer o merge do pull request se o repositório estiver c
 **Observação:** Ignorar instruções só se aplica aos eventos `push` e `pull_request`. Por exemplo, adicionar `[skip ci]` a uma mensagem de commit não impedirá que um fluxo de trabalho que acionou `on : pull_request_target` seja executado.
 
 {% endnote %}
+{% endif %}
 
 ### Notificações para execução de fluxo de trabalho
 
diff --git a/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md b/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md
index de3fefe069..39f233088e 100644
--- a/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/pt-BR/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,38 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### Sobre as etapas do empacotamento
-
-Uma etapa de empacotamento é uma parte comum de um fluxo de trabalho de integração contínua ou de continuous delivery. Após criar e testar o seu aplicativo, será produzido um artefato executável ou aplicável produzido na forma de um pacote. Por exemplo, um fluxo de trabalho de integração contínua para um projeto Java pode executar o `pacote mvn` para produzir um arquivo JAR. Ou um fluxo de trabalho CI para um aplicativo Node.js pode criar um contêiner Docker.
-
-Dependendo do tipo de aplicativo que você estiver criando, este pacote pode ser baixado localmente para teste manual, disponibilizado para download dos usuários ou implementado em um ambiente de teste ou produção.
-
-### Empacotamento em fluxos de trabalho de integração contínua
-
-Criar um pacote ao fim de um fluxo de trabalho de integração contínua pode ajudar durante as análises de código ou durante o pull request. Após criar e testar o seu código, uma etapa de empacotamento pode produzir um artefato executável ou aplicável. Em seguida, o seu fluxo de trabalho pode pegar esse artefato e fazer o upload como parte do fluxo de trabalho.
-
-Agora, ao revisar um pull request, você poderá ver a execução do fluxo de trabalho e fazer o download do artefato produzido.
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-Isso permitirá que você execute o código no pull request em sua máquina, o que pode ajudar a depurar ou testar o pull request.
-
-### Fluxos de trabalho para publicação de pacotes
-
-Além de fazer o upload dos artefatos de empacotamento para teste em um fluxo de trabalho de integração contínua, você poderá criar fluxos de trabalho que criam o seu projeto e publicam pacotes no pacote de registro.
-
-* **Publicar pacotes para {% data variables.product.prodname_registry %}**
-  {% data variables.product.prodname_registry %} pode atuar como um serviço de hospedagem de pacotes para vários tipos de pacotes. Você pode escolher compartilhar os seus pacotes com todos {% data variables.product.prodname_dotcom %} ou compartilhar pacotes privados com colaboradores ou uma organização. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)."
-
-  Você pode querer publicar pacotes em {% data variables.product.prodname_registry %} em cada push no branch padrão. Isso fará com que os desenvolvedores no seu projeto sempre consigam executar e testar facilmente a última criação feita a partir do mestre, instalando-a a partir de {% data variables.product.prodname_registry %}.
-
-* **Publicar pacotes em um registro de pacote** Para muitos projetos, a publicação de um registro de pacote é realizada sempre que uma versão nova de um projeto é lançada. Por exemplo, um projeto que produz um arquivo JAR pode fazer o upload de novas versões no repositório central do Maven. Ou um projeto .NET pode produzir um pacote nuget e fazer o upload na Galeria NuGet.
-
-  Você pode automatizar isso criando um fluxo de trabalho que publica pacotes em um registro de pacote em cada versão. Para obter mais informações, consulte "[Criando versões](/github/administering-a-repository/creating-releases)."
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/actions/guides/adding-labels-to-issues.md b/translations/pt-BR/content/actions/guides/adding-labels-to-issues.md
index 8fdaee2185..6688002a8a 100644
--- a/translations/pt-BR/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/pt-BR/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a a
 2. {% data reusables.actions.make-workflow-file %}
 3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,14 +38,17 @@ No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a a
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Personalize os parâmetros no seu arquivo do fluxo de trabalho:
    - Altere o valor de `add-labels` para a lista de etiquetas que você deseja adicionar ao problema. Separe etiquetas múltiplas com vírgulas. Por exemplo, `"help wanted, good first issue"`. Para obter mais informações sobre etiquetas, consulte "[Gerenciar etiquetas](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)".
 5. {% data reusables.actions.commit-workflow %}
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-net.md b/translations/pt-BR/content/actions/guides/building-and-testing-net.md
index 893608336b..5cdc06fec1 100644
--- a/translations/pt-BR/content/actions/guides/building-and-testing-net.md
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-net.md
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ Você pode configurar o seu trabalho para usar uma versão específica do .NET,
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ Os executores hospedados em {% data variables.product.prodname_dotcom %} têm o
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,7 +139,7 @@ Para obter mais informações, consulte "[Memorizar dependências para acelerar
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
@@ -171,7 +171,7 @@ Você pode usar os mesmos comandos usados localmente para criar e testar seu có
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 É possível configurar o seu fluxo de trabalho para publicar o pacote Dotnet em um pacote de registro quando o CI teste passa. Você pode usar segredos do repositório para armazenar quaisquer tokens ou credenciais necessárias para publicar seu binário. O exemplo a seguir cria e publica um pacote em {% data variables.product.prodname_registry %} usando `dotnet core cli`.
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md
index 850e9a93fe..789ac20013 100644
--- a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ Recomendamos que você tenha um entendimento básico do Node.js, YAML, das opç
 
 O {% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do Node.js que funcionará para a maioria dos projetos Node.js. Esse guia inclui exemplos de npm e Yarn que você pode usar para personalizar o modelo. Para obter mais informações, consulte o [modelo do fluxo de trabalho do Node.js](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório.
+Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. O fluxo de trabalho mostrado abaixo pressupõe que o branch padrão para o seu repositório é `principal`.
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,14 +119,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 Se você não especificar uma versão do Node.js,
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md
index 451719de91..5afeb8be03 100644
--- a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ O exemplo a seguir instala `PSScriptAnalyzer` e o usa para limpar todos os arqui
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-python.md b/translations/pt-BR/content/actions/guides/building-and-testing-python.md
index 2594800980..e8ac2f57a4 100644
--- a/translations/pt-BR/content/actions/guides/building-and-testing-python.md
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-python.md
@@ -45,38 +45,38 @@ Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do
 
 {% raw %}
 ```yaml{:copy}
-nome: Pacote do Python
+name: Python package
 
-em: [push]
+on: [push]
 
-trabalhos:
-  criar:
+jobs:
+  build:
 
     runs-on: ubuntu-latest
-    estratégia:
-      matriz:
+    strategy:
+      matrix:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
-    etapas:
-    - usa: actions/checkout@v2
-    - nome: Configura o Python ${{ matrix.python-version }}
-      usa: actions/setup-python@v2
-      com:
-        python-version: ${{ matrix.python-version }}
-    - nome: Instalar dependências
-      executar: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - nome : Lint with flake8
-      executar: |
-        # interrompe a criação em caso de erros de sintaxe do Python ou de nomes indefinidos
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zero trata todos os errors como avisos. O editor do GitHub tem 127 caracteres
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - nome: Testar com pytest
-      executar: |
-        pytest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -112,19 +112,19 @@ trabalhos:
     runs-on: ubuntu-latest
     estratégia:
       # Você pode usar as versões do PyPy em python-version.
-      # Por exemplo, pypy2 and pypy3
-      matriz:
+      # For example, pypy2 and pypy3
+      matrix:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
-    etapas:
-    - usa: actions/checkout@v2
-    - nome: Configura o Python ${{ matrix.python-version }}
-      usa: actions/setup-python@v2
-      com:
-        python-version: ${{ matrix.python-version }}
-    # Você pode testar a sua matriz imprimindo a versão atual do Python
-    - nome: Exibe a versão do Python
-      executar: python -c "import sys; print(sys.version)"
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -144,17 +144,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # Semantic version range syntax or exact version of a Python version
-        python-version: '3.x'
-        # Optional - x64 or x86 architecture, defaults to x64
-        architecture: 'x64'
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -373,25 +373,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Install pip and pytest
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # Use always() to always run this step to publish test results when there are test failures
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -403,32 +403,32 @@ Você pode armazenar qualquer token de acesso ou credenciais necessárias para p
 
 {% raw %}
 ```yaml{:copy}
-Nome: Fazer o upload no pacote Python
+name: Upload Python Package
 
-em:
-  versão:
-    tipos: [created]
+on:
+  release:
+    types: [created]
 
-trabalhos:
-  implementar:
+jobs:
+  deploy:
     runs-on: ubuntu-latest
-    etapas:
-    - usa: actions/checkout@v2
-    - nome: Configurar Python
-      usa: actions/setup-python@v2
-      com:
-        python-version: '3.x'
-    - nome: Instalar dependências
-      executar: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - nome: Criar e publicar
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      executar: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 {% endraw %}
 
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md
index 6934e98984..239bdd9843 100644
--- a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ Recomendamos que você tenha um entendimento básico do Ruby, YAML, das opções
 
 {% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do Ruby que funcionará para a maioria dos projetos do Ruby. Para obter mais informações, consulte o [modelo do workflow do Ruby](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório.
+Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório. O fluxo de trabalho mostrado abaixo pressupõe que o branch padrão para o seu repositório é `principal`.
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,7 +264,6 @@ Você pode configurar o seu fluxo de trabalho para publicar o seu pacote do Ruby
 
 Você pode armazenar qualquer token de acesso ou credenciais necessárias para publicar seu pacote usando segredos do repositório. O exemplo a seguir cria e publica um pacote no `Registro de Pacote do GitHub` e `RubyGems`.
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
@@ -272,46 +271,48 @@ name: Ruby Gem
 on:
   # Manually publish
   workflow_dispatch:
-  # Alternatively, publish whenever changes are merged to the default branch.
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-swift.md b/translations/pt-BR/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..a0aacd10a1
--- /dev/null
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Construção e teste Swift
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto no Swift.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introdução
+
+Este guia mostra como criar e testar um pacote do Swift.
+
+{% if currentVersion == "github-ae@latest" %} Para criar e testar seu projeto Swift em {% data variables.product.prodname_ghe_managed %}, você deverá criar uma imagem personalizada do sistema operacional que inclua as dependências necessárias do Swift. Para obter instruções sobre como garantir que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)".
+Executores hospedados em {% else %}{% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado e os executores Ubuntu e macOS incluem as dependências para construir pacotes Swift. Para obter uma lista completa do software atualizado e das versões pré-instaladas do Swift e do Xcode, consulte "[Sobre executores hospedados pelo GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### Pré-requisitos
+
+Você já deve estar familiarizado com a sintaxe YAML e como é usado com {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+
+Recomendamos que você tenha uma compreensão básica dos pacotes Swift. Para obter mais informações, consulte "[Pacotes Swift](https://developer.apple.com/documentation/swift_packages)" na documentação de desenvolvedor da Apple.
+
+### Começando com o modelo de fluxo de trabalho do Swift
+
+{% data variables.product.prodname_dotcom %} fornece um modelo de fluxo de trabalho do Swift que deve funcionar na maioria dos projetos do Swift, e este guia inclui exemplos que mostram como personalizar este modelo. Para obter mais informações, consulte o [Modelo do fluxo de trabalho do Swift](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+Para iniciar rapidamente, adicione o modelo ao diretório `.github/workflows` do repositório.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Especificando uma versão do Swift
+
+Para usar uma versão específica do Swift em um executor hospedado em {% data variables.product.prodname_dotcom %}, use a ação `fwal/setup-fast`. Esta ação encontra uma versão específica do Swift do cache de ferramentas no executor e adiciona os binários necessários a `PATH`. Estas alterações persistirão para o restante de um trabalho. Para obter mais informações, consulte a ação [`fwal/setup-speed`](https://github.com/marketplace/actions/setup-swift).
+
+Se você estiver usando um executor auto-hospedado, você deverá instalar as versões do Swift desejadas e adicioná-las a `PATH`.
+
+Os exemplos abaixo demonstram o uso da ação `fwal/setup-fast`.
+
+#### Usando várias versões do Swift
+
+Você pode configurar seu trabalho para usar várias versões do Swift em uma matriz de criação.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Usando uma única versão específica do Swift
+
+Você pode configurar sua tarefa para usar uma única versão específica do Swift como, por exemplo, `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### Criar e testar seu código
+
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código usando o Swift. Este exemplo demonstra como usar `swift build` e `swift test` em um trabalho:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/pt-BR/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..dd3ccd48b4
--- /dev/null
+++ b/translations/pt-BR/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Criando e testando aplicativos Xamarin
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para construir e testar o seu aplicativo Xamarin.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introdução
+
+Este guia mostra como criar um fluxo de trabalho que executa a integração contínua (CI) para o seu projeto Xamarin. O fluxo de trabalho que você criar permitirá que você veja quando commits em um pull request gerarão falhas de criação ou de teste em comparação com o seu branch-padrão. Essa abordagem pode ajudar a garantir que seu código seja sempre saudável.
+
+O executor do macOS hospedado em {% data variables.product.prodname_actions %} armazena versões do Xamarin SDK e versões Mono associadas como links simbólicos para as localidades o Xamarin SDK que estão disponíveis por um link simbólico único do pacote. Para obter uma lista completa das versões do Xamarin SDK e seus pacotes correspondentes, consulte a documentação dos executores:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### Pré-requisitos
+
+Recomendamos que você tenha um entendimento básico do Xamarin, .NET Core SDK, YAML, opções de configuração do fluxo de trabalho e como criar um arquivo de fluxo de trabalho. Para obter mais informações, consulte:
+
+- "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Começando com o .NET](https://dotnet.microsoft.com/learn)"
+- "[Conheça o Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Criando aplicativos Xamarin.iOS
+
+O exemplo abaixo demonstra como alterar o pacote padrão do Xamarin e criar um aplicativo Xamarin.iOS.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Criando aplicativos Xamarin.Android
+
+O exemplo abaixo demonstra como alterar o padrão do pacote Xamarin e construir um aplicativo Xamarin.Android.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### Especificando uma versão do .NET
+
+Para usar uma versão pré-instalada do .NET Core SDK em um executor hospedado em {% data variables.product.prodname_dotcom %}, use a ação `setup-dotnet`. Esta ação encontra uma versão específica do .NET do cache de ferramentas em cada executor e adiciona os binários necessários para `PATH`. Estas alterações persistirão para o resto do trabalho.
+
+A ação `setup-dotnet` é a forma recomendada de usar .NET com {% data variables.product.prodname_actions %}, porque garante um comportamento consistente em executores diferentes e versões diferentes do .NET. Se você estiver usando um executor auto-hospedado, você deverá instalar o .NET e adicioná-lo ao `PATH`. Para obter mais informações, consulte a ação [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk).
diff --git a/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index 5c35197289..ed4c9cc58b 100644
--- a/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/pt-BR/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ Para obter mais informações, consulte [`ações/cache`](https://github.com/act
 
 - `key`: **Obrigatório** A chave criada ao salvar uma cache e a chave usada para pesquisar uma cache. Pode ser qualquer combinação de variáveis, valores de contexto, strings estáticas e funções. As chaves têm um tamanho máximo de 512 caracteres e as chaves maiores que o tamanho máximo gerarão uma falha na ação.
 - ``de caminho : **Required** O caminho do arquivo no corredor para cache ou restauração. O caminho pode ser absoluto ou relativo com relação ao diretório de trabalho.
-  - Com `v2` da ação da `cache`, você pode especificar um caminho único ou caminhos múltiplos como uma lista. Os caminhos podem ser diretórios ou arquivos únicos. Os padrões de glob são compatíveis.
+  - Os caminhos podem ser diretórios ou arquivos únicos. Os padrões de glob são compatíveis.
+  - Com o `v2` da ação `cache`, é possível especificar um único caminho ou é possível adicionar vários caminhos em linhas separadas. Por exemplo:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - Com `v1` da ação da `cache`, somente um caminho único é compatível e deve ser um diretório. Você não pode armazenar um único arquivo.
 - `chaves de restauração`: **Opcional** Uma lista ordenada de chaves alternativas a serem usadas para encontrar a cache se não ocorrer correspondência para a `chave`.
 
@@ -73,39 +82,38 @@ Este exemplo cria uma nova cache quando são alterados os pacotes no arquivo `pa
 
 {% raw %}
 ```yaml{:copy}
-nome : Memorização com npm
+name: Caching with npm
 
-em: push
+on: push
 
-trabalho:
-  criar:
+jobs:
+  build:
     runs-on: ubuntu-latest
 
-    etapas:
-    - usa: ações/checkout@v2
+    steps:
+      - uses: actions/checkout@v2
 
-    - nome: Módulos do nó da cache
-      usa: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        # arquivos de cache npm são armazenados em `~/.npm` on Linux/macOS
-        caminho: ~/.npm
-        chave: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - nome: Instalar dependências
-      executar: instalação de npm
+      - name: Install Dependencies
+        run: npm install
 
-    - nome: Build
-      executar: npm build
-
-    - nome: Teste
-      executar: teste de npm
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/pt-BR/content/actions/guides/closing-inactive-issues.md b/translations/pt-BR/content/actions/guides/closing-inactive-issues.md
index a4190d4b85..6a8c280afd 100644
--- a/translations/pt-BR/content/actions/guides/closing-inactive-issues.md
+++ b/translations/pt-BR/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ No tutorial, primeiro você vai fazer um arquivo de fluxo de trabalho que usa a
 2. {% data reusables.actions.make-workflow-file %}
 3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ No tutorial, primeiro você vai fazer um arquivo de fluxo de trabalho que usa a
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,9 +51,9 @@ No tutorial, primeiro você vai fazer um arquivo de fluxo de trabalho que usa a
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Personalize os parâmetros no seu arquivo do fluxo de trabalho:
    - Altere o valor de `on.schagen` para ditar quando você deseja que este fluxo de trabalho seja executado. No exemplo acima, o fluxo de trabalho será executado todos os dias à 1:30 UTC. Para obter mais informações sobre fluxos de trabalho agendados, consulte "[Eventos agendados](/actions/reference/events-that-trigger-workflows#scheduled-events)".
    - Altere o valor de `days-before-issue-stale` para o número de dias sem atividade antes da ação `actions/stale` etiquetar um problema. Se você nunca quiser que esta ação etiquete problemas, defina esse valor como `-1`.
diff --git a/translations/pt-BR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/pt-BR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index 6beea6d1d4..56ae74c5c5 100644
--- a/translations/pt-BR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/pt-BR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
 2. {% data reusables.actions.make-workflow-file %}
 3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **Certifique-se de fazer referência a esse problema no seu pull request.** :sparkles: Obrigado pela sua contribuição! :sparkles:
     ```
-    {% endraw %}
+
 4. Personalize os parâmetros no seu arquivo do fluxo de trabalho:
    - Substitua `help-wanted` em `if: github.event.label.name == 'help-wanted'` pela etiqueta na qual você deseja agir. Se você desejar atuar em mais de uma etiqueta, separe as condições com `||`. Por exemplo, `if: github.event.label.name == 'bug' ➜ github.event.label. ame == 'corrija-me'` irá comentar sempre que as etiquetas `bug` ou `fix me` forem adicionadas a um problema.
    - Altere o valor de `texto` para o comentário que você deseja adicionar. Markdown em estilo GitHub é compatível. Para obter mais informações sobre markdown, consulte "[Sintaxe básica de escrita e formatação](/github/writing-on-github/basic-writing-and-formatting-syntax)".
diff --git a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md
index 9908b3af8e..a79698f27b 100644
--- a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### Introdução
 
-Este guia mostra exemplos de fluxo de trabalho que configuram um contêiner de serviço usando a imagem `postgres` do Docker Hub. O fluxo de trabalho executa um script para criar um cliente PostgreSQL e preencher os dados do cliente. Para testar se o fluxo de trabalho cria e preenche o cliente PostgreSQL, o script imprime os dados do cliente no console.
+Este guia mostra exemplos de fluxo de trabalho que configuram um contêiner de serviço usando a imagem `postgres` do Docker Hub. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -43,48 +43,48 @@ Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% da
 
 {% raw %}
 ```yaml{:copy}
-nome: exemplo de serviço PostgreSQL
-em: push
+name: PostgreSQL service example
+on: push
 
-trabalhos:
-  # Etiqueta do trabalho do contêiner
+jobs:
+  # Label of the container job
   container-job:
-    # Os contêineres devem ser executados em sistemas operacionais baseados no Linux
+    # Containers must run in Linux based operating systems
     runs-on: ubuntu-latest
-    # Imagem do Docker Hub em que o `container-job` é executado
-    contêiner: node:10.18-jessie
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
 
-    # Contêineres de serviço a serem executados com `container-job`
-    serviços:
-      # Etiqueta usada para acessar o contêiner de serviço
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
       postgres:
-        # Imagem do Docker Hub
-        imagem: postgres
-        # Fornece a senha para postgres
+        # Docker Hub image
+        image: postgres
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # Define verificações gerais até a inicialização do postgres
+        # Set health checks to wait until postgres has started
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
 
-    etapas:
-      # Faz o download de uma cópia do código no seu repositório antes de executar testes de CI
-      - nome: Verifica o código do repositório
-        usa: actions/checkout@v2
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
+      - name: Check out repository code
+        uses: actions/checkout@v2
 
-      # Realiza uma instalação limpa de todas as dependências no arquivo `package.json`
-      # Para obter mais informações, consulte https://docs.npmjs.com/cli/ci.html
-      - nome: Instalar dependências
-        executar: npm ci
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
+      - name: Install dependencies
+        run: npm ci
 
-      - nome: Conectar-se ao PostgreSQL
-        # Executa um script que cria um cliente PostgreSQL client, preenche
-        # os dados do cliente e recupera dados
-        executar: node client.js
-        # Variável de ambiente usada pelo script `client.js` para criar um novo PostgreSQL client.
+      - name: Connect to PostgreSQL
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
+        run: node client.js
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # O nome do host usado para comunicar-se com o contêiner de serviço do PostgreSQL
           POSTGRES_HOST: postgres
@@ -130,22 +130,22 @@ trabalhos:
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
-etapas:
-  # Faz o download de uma cópia do código no seu repositório antes de executar testes de CI
-  - nome: Verifica o código do repositório
-    usa: actions/checkout@v2
+steps:
+  # Downloads a copy of the code in your repository before running CI tests
+  - name: Check out repository code
+    uses: actions/checkout@v2
 
-  # Executa uma instalação limpa de todas as dependências no arquivo `package.json`
-  # Para obter mais informações, consulte https://docs.npmjs.com/cli/ci.html
-  - Nome: Instalar dependências
-    executar: npm ci
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
+  - name: Install dependencies
+    run: npm ci
 
-  - nome: Conectar-se ao PostgreSQL
-    # Executa um script que cria um cliente PostgreSQL client, preenche
-    # os dados do cliente e recupera dados
-    executar: node client.js
-    # Variável do ambiente usada pelo script `client.js` script para criar
-    # um novo cliente PostgreSQL.
+  - name: Connect to PostgreSQL
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
+    run: node client.js
+    # Environment variable used by the `client.js` script to create
+    # a new PostgreSQL client.
     env:
       # O nome do host usado para comunicar-se com o contêiner de serviço do PostgreSQL
       POSTGRES_HOST: postgres
@@ -165,50 +165,50 @@ Ao executar um trabalho diretamente na máquina executora, você deverá mapear
 
 {% raw %}
 ```yaml{:copy}
-nome: Exemplo de serviço do PostgreSQL
-em: push
+name: PostgreSQL Service Example
+on: push
 
-trabalhos:
-  # Etiqueta do trabalho executor
+jobs:
+  # Label of the runner job
   runner-job:
-    # Você deve usar um ambiente do Linux ao usar os contêineres de serviço ou os trabalhos do contêiner
+    # You must use a Linux environment when using service containers or container jobs
     runs-on: ubuntu-latest
 
-    # Os serviços dos contêineres a serem executados com `runner-job`
-    serviços:
-      # Etiqueta usada para acessar o contêiner de serviço
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
       postgres:
-        # Imagem do Docker Hub
-        imagem: postgres
-        # Fornece a senha para postgres
+        # Docker Hub image
+        image: postgres
+        # Provide the password for postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # Define verificações gerais até a inicialização do postgres
-        opções: >-
+        # Set health checks to wait until postgres has started
+        options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
-        portas:
-          # Mapeia a porta port 5432 tcp no contêiner de serviço com o host
+        ports:
+          # Maps tcp port 5432 on service container to the host
           - 5432:5432
 
-    etapas:
-      # Faz o download de uma cópia do código no seu repositório antes de executar um teste de CI
-      - nome: Verifica o código do repositório
-        usa: actions/checkout@v2
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
+      - name: Check out repository code
+        uses: actions/checkout@v2
 
-      # Realiza uma instalação limpa de todas as dependências no arquivo `package.json`
-      # Para obter mais informações, consulte https://docs.npmjs.com/cli/ci.html
-      - nome: Instalar dependências
-        executar: npm ci
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
+      - name: Install dependencies
+        run: npm ci
 
-      - nome: Conectar-se ao PostgreSQL
-        # Executa um script que cria um cliente PostgreSQL, preenche
-        # os dados do cliente e recupera dados
-        executar: node client.js
-        # Variável de ambiente usada pelo script `client.js` para criar
-        # um novo cliente PostgreSQL.
+      - name: Connect to PostgreSQL
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
+        run: node client.js
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # O nome do host usado para comunicar-se com o contêiner de serviço PostgreSQL
           POSTGRES_HOST: localhost
@@ -257,22 +257,22 @@ trabalhos:
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
-etapas:
-  # Faz o download de uma cópia do código no seu repositório antes de executar testes de CI
-  - nome: Verifica o código do repositório
-    usa: actions/checkout@v2
+steps:
+  # Downloads a copy of the code in your repository before running CI tests
+  - name: Check out repository code
+    uses: actions/checkout@v2
 
-  # Executa uma instalação limpa de todas as dependências no arquivo `package.json`
-  # Para obter mais informações, consulte https://docs.npmjs.com/cli/ci.html
-  - Nome: Instalar dependências
-    executar: npm ci
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
+  - name: Install dependencies
+    run: npm ci
 
-  - nome: Conectar-se ao PostgreSQL
-    # Executa um script que cria um cliente PostgreSQL client, preenche
-    # os dados do cliente e recupera dados
-    executar: node client.js
-    # Variável do ambiente usada pelo script `client.js` script para criar
-    # um novo cliente PostgreSQL.
+  - name: Connect to PostgreSQL
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
+    run: node client.js
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # O nome do host usado para comunicar-se com o contêiner de serviço do PostgreSQL
       POSTGRES_HOST: localhost
@@ -286,9 +286,9 @@ etapas:
 
 ### Testar o contêiner de serviço do PostgreSQL
 
-Você pode testar o seu fluxo de trabalho usando o script a seguir, que cria um cliente PostgreSQL e adiciona uma tabela com alguns dados com espaços reservados. Em seguida, o script imprime no terminal os valores armazenados no cliente PostgreSQL. O seu script pode usar qualquer linguagem que você desejar, mas este exemplo usa Node.js e o módulo npm `pg`. Para obter mais informações, consulte [módulo npm pg](https://www.npmjs.com/package/pg).
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. O seu script pode usar qualquer linguagem que você desejar, mas este exemplo usa Node.js e o módulo npm `pg`. Para obter mais informações, consulte [módulo npm pg](https://www.npmjs.com/package/pg).
 
-Você pode modificar o *client.js* para incluir qualquer operação do PostgreSQL exigida pelo seu fluxo de trabalho. Neste exemplo, o script cria a instância do cliente PostgreSQL, cria uma tabela, adiciona dados de espaços reservados e, em seguida, recupera os dados.
+Você pode modificar o *client.js* para incluir qualquer operação do PostgreSQL exigida pelo seu fluxo de trabalho. In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-O script cria um novo `Client` PostgreSQL, que aceita um `host` e o parâmetro da `porta`. O script usa as variáveis de ambiente `POSTGRES_HOST` e `POSTGRES_PORT` para definir o endereço IP e a porta do cliente. Se o `host` e a `porta` não forem definidos, o host-padrão será `localhost` e a porta-padrão será 5432.
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. Se o `host` e a `porta` não forem definidos, o host-padrão será `localhost` e a porta-padrão será 5432.
 
-O script cria uma tabela e preenche com dados de espaço reservado. Para testar se o banco de dados do PostgreSQL contém os dados, o script imprime o conteúdo da tabela no registro do console.
+O script cria uma tabela e preenche com dados de espaço reservado. To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-Ao executar este fluxo de trabalho, você deve ver a saída a seguir na etapa "Conectar-se ao PostgreSQL", que confirma que você criou o cliente PostgreSQL e adicionou dados:
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index 2a9932d9ef..0f24734d00 100644
--- a/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ O fluxo de trabalho a seguir demonstra como construir uma imagem de contêiner e
 
 Certifique-se de fornecer seus próprios valores para todas as variáveis na chave `env` do fluxo de trabalho.
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### Recursos adicionais
 
diff --git a/translations/pt-BR/content/actions/guides/index.md b/translations/pt-BR/content/actions/guides/index.md
index 0b7f2aa900..a5df988703 100644
--- a/translations/pt-BR/content/actions/guides/index.md
+++ b/translations/pt-BR/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/pt-BR/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/pt-BR/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..0b448db3ad
--- /dev/null
+++ b/translations/pt-BR/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Gerenciar o GitHub Actions com o GitHub CLI
+intro: 'Você pode usar {% data variables.product.prodname_cli %} para interagir com {% data variables.product.prodname_actions %}.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Configurar o {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### Gerenciar {% data variables.product.prodname_actions %} com {% data variables.product.prodname_cli %}
+
+Para visualizar todos os comandos disponíveis relacionados a {% data variables.product.prodname_actions %}, execute `gh actions`.
+
+Para obter mais informações sobre o uso de comandos em cenários específicos, consulte os procedimentos a seguir:
+
+- "[Reexecutar um fluxo de trabalho](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[Executar um fluxo de trabalho manualmente](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)
+- "[Fazer o download dos artefatos do fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[Usar registros de execução de fluxo de trabalho](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[Desabilitar e habilitar um fluxo de trabalho](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/pt-BR/content/actions/guides/publishing-docker-images.md b/translations/pt-BR/content/actions/guides/publishing-docker-images.md
index 765dae6971..84dbece96f 100644
--- a/translations/pt-BR/content/actions/guides/publishing-docker-images.md
+++ b/translations/pt-BR/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ Você também pode achar útil ter um entendimento básico do seguinte:
 
 - "[Segredos criptografados](/actions/reference/encrypted-secrets)"
 - "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)"
-- "[Configurar o Docker para uso com o {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)"
+- "[Trabalhando com o registro Docker](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### Sobre a configuração da imagem
 
@@ -98,30 +98,31 @@ As opções de `build-push-action` necessárias para {% data variables.product.p
 * `registro`: Deve ser definido como `docker.pkg.github.com`.
 * `repositório`: Deve ser definido no formato `OWNER/REPOSITORY/IMAGE_NAME`. Por exemplo, para uma imagem denominada `octo-image` armazenada no {% data variables.product.prodname_dotcom %} em `http://github. Um/octo-org/octo-repo`, a opção `repositório` deve ser definida como `octo-org/octo-repo/octo-image`.
 
-{% raw %}
 ```yaml{:copy}
-nome: Publish Docker image
-em:
-  versão:
-    tipos: [published]
-trabalhos:
+name: Publish Docker image
+on:
+  release:
+    types: [published]
+jobs:
   push_to_registry:
-    nome: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
-    etapas:
-      - nome: Check out the repo
-        usa: actions/checkout@v2
-      - nome: Push to GitHub Packages
-        usa: docker/build-push-action@v1
-        com:
-          nome de usuário: ${{ github.actor }}
-          senha: ${{ secrets.GITHUB_TOKEN }}
-          registro: docker.pkg.github.com
-          repositório: my-org/my-repo/my-image
+    name: Push Docker image to GitHub Packages
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+    steps:
+      - name: Check out the repo
+        uses: actions/checkout@v2
+      - name: Push to GitHub Packages
+        uses: docker/build-push-action@v1
+        with:
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          registry: docker.pkg.github.com
+          repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,35 +132,36 @@ Em um único fluxo de trabalho, você pode publicar sua imagem do Docker em vár
 
 O exemplo do fluxo de trabalho a seguir usa as etapas `build-push-action` das seções anteriores ("[Publicar imagens para o Docker Hub](#publishing-images-to-docker-hub)" e "[Publicar imagens em {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para criar um único fluxo de trabalho que faça push em ambos os registros.
 
-{% raw %}
 ```yaml{:copy}
-nome: Publicar imagem do Docker
-em:
-  versão:
-    tipos: [published]
-trabalhos:
+name: Publish Docker image
+on:
+  release:
+    types: [published]
+jobs:
   push_to_registries:
-    nome: Fazer push da imagem do Docker em múltiplos registros
-    runs-on: ubuntu-latest
-    etapas:
-      - nome: Verificar o repo
-        usa: actions/checkout@v2
-      - nome: Push to Docker Hub
-        usa: docker/build-push-action@v1
+    name: Push Docker image to multiple registries
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+    steps:
+      - name: Check out the repo
+        uses: actions/checkout@v2
+      - name: Push to Docker Hub
+        uses: docker/build-push-action@v1
         with:
-          nome de usuário: ${{ secrets.DOCKER_USERNAME }}
-          senha: ${{ secrets.DOCKER_PASSWORD }}
-          repositório: my-docker-hub-namespace/my-docker-hub-repository
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
+          repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
-      - nome: Push to GitHub Packages
-        usa: docker/build-push-action@v1
-        com:
-          nome de usuário: ${{ github.actor }}
-          senha: ${{ secrets.GITHUB_TOKEN }}
-          registro: docker.pkg.github.com
-          repositório: my-org/my-repo/my-image
+      - name: Push to GitHub Packages
+        uses: docker/build-push-action@v1
+        with:
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          registry: docker.pkg.github.com
+          repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 O fluxo de trabalho acima verifica o repositório {% data variables.product.prodname_dotcom %} e usa a ação `construção-push-action` duas vezes para criar e fazer push da imagem do Docker Hub e {% data variables.product.prodname_registry %}. Para ambas as etapas, ele define a opção `construção-push-action` [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) para marcar automaticamente a imagem do Docker criada com a referêcia do Git do evento do fluxo de trabalho. Este fluxo de trabalho é acionado na publicação de uma versão do {% data variables.product.prodname_dotcom %}. Portanto, a referência para ambos os registros será a tag do Git para a versão.
diff --git a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md
index 190ee75db0..f009888fdf 100644
--- a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ Para obter mais informações sobre a criação de um fluxo de trabalho de CI pa
 
 Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[Configurar o npm para uso com o {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Trabalhando com o registro npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Variáveis de ambiente](/actions/reference/environment-variables)"
 - "[Segredos criptografados](/actions/reference/encrypted-secrets)"
 - "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)"
@@ -108,7 +108,7 @@ Cada vez que você criar uma nova versão, você poderá acionar um fluxo de tra
 
 Você pode definir um novo repositório do Maven no bloco de publicação do _build.gradle_ que aponta para {% data variables.product.prodname_registry %}.  Nessa configuração do repositório, também é possível aproveitar as variáveis de ambiente definidas na execução do fluxo de trabalho de CI.  Você pode usar a variável de ambiente `GITHUB_ACTOR` como um nome de usuário e você pode definir a variável de ambiente `GITHUB_TOKEN` com seu segredo `GITHUB_TOKEN`.
 
-O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+{% data reusables.github-actions.github-token-permissions %}
 
 Por exemplo, se sua organização é denominado "octocat" e seu repositório é denominado de "hello-world", a configuração do {% data variables.product.prodname_registry %} no _build.gradle_ será parecida ao exemplo abaixo.
 
@@ -133,7 +133,6 @@ publicando {
 
 Com essa configuração, é possível criar um fluxo de trabalho que publica seu pacote no Repositório Central do Maven ao executar o comando `publicação do gradle`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Executa o comando `publicação do gradle` para publicar no {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`.
+1. Executa o comando `publicação do gradle` para publicar no {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}A chave de `permissões` especifica o acesso que o segredo `GITHUB_TOKEN` permitirá.{% endif %}
 
    Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
@@ -199,7 +200,6 @@ publicando {
 
 Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote no Repositório Central do Maven e em {% data variables.product.prodname_registry %}, executando o comando `publicação do gradle`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Executa o comando `publicação do gradle` para publicar no repositório do Maven `OSSRH` e em {% data variables.product.prodname_registry %}. A variável de ambiente `MAVEN_USERNAME` será definida com o conteúdo do seu segredo `OSSRH_USERNAME`, e a variável de ambiente `MAVEN_PASSWORD` será definida com o conteúdo do seu segredo `OSSRH_TOKEN`. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`.
+1. Executa o comando `publicação do gradle` para publicar no repositório do Maven `OSSRH` e em {% data variables.product.prodname_registry %}. A variável de ambiente `MAVEN_USERNAME` será definida com o conteúdo do seu segredo `OSSRH_USERNAME`, e a variável de ambiente `MAVEN_PASSWORD` será definida com o conteúdo do seu segredo `OSSRH_TOKEN`. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}A chave de `permissões` especifica o acesso que o segredo `GITHUB_TOKEN` permitirá.{% endif %}
 
    Para obter mais informações sobre o uso de segredos no seu fluxo de trabalho, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md
index 5388e6aca9..421441f247 100644
--- a/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/pt-BR/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ Para obter mais informações sobre a criação de um fluxo de trabalho de CI pa
 
 Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[Configurar o npm para uso com o {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Trabalhando com o registro npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Variáveis de ambiente](/actions/reference/environment-variables)"
 - "[Segredos criptografados](/actions/reference/encrypted-secrets)"
 - "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)"
@@ -112,9 +112,9 @@ Este fluxo de trabalho executa os seguintes passos:
 
 Cada vez que você criar uma nova versão, você poderá acionar um fluxo de trabalho para publicar o seu pacote. O fluxo de trabalho no exemplo abaixo é executado quando o evento `versão` é acionado com o tipo `criado`. O fluxo de trabalho publica o pacote em {% data variables.product.prodname_registry %} se o teste de CI for aprovado. Para obter mais informações sobre o evento da `versão`, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#release)".
 
-Neste fluxo de trabalho, você pode usar a ação `setup-java`. Esta ação instala a versão determinada do JDK no `PATH`, e também configura _settings.xml_ do Maven para a publicação {% data variables.product.prodname_registry %}. O _settings.xml_ gerado define a autenticação para um servidor com um `id` do `github`, usando a variável de ambiente `GITHUB_ACTOR` como o nome de usuário e a variável de ambiente `GITHUB_TOKEN` como a senha.
+Neste fluxo de trabalho, você pode usar a ação `setup-java`. Esta ação instala a versão determinada do JDK no `PATH`, e também configura _settings.xml_ do Maven para a publicação {% data variables.product.prodname_registry %}. O _settings.xml_ gerado define a autenticação para um servidor com um `id` do `github`, usando a variável de ambiente `GITHUB_ACTOR` como o nome de usuário e a variável de ambiente `GITHUB_TOKEN` como a senha. A variável de ambiente `GITHUB_TOKEN` foi atribuída ao valor do segredo especial `GITHUB_TOKEN`.
 
-O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+{% data reusables.github-actions.github-token-permissions %}
 
 Para um projeto baseado no Maven, você pode usar essas configurações ao criar um repositório de distribuição no seu arquivo _pom.xml_ com um `id` do `github` que aponta para seu ponto final {% data variables.product.prodname_registry %}.
 
@@ -137,7 +137,6 @@ Por exemplo, se sua organização é denominada "octocat" e seu repositório é
 
 Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote em {% data variables.product.prodname_registry %}, fazendo uso do _settings.xml_ gerado automaticamente.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Este fluxo de trabalho executa os seguintes passos:
 
@@ -173,7 +174,6 @@ Você pode publicar seus pacotes no Repositório Central Maven e em {% data vari
 
 Certifique-se de que seu arquivo _pom.xml_ inclui um repositório de gerenciamento de distribuição tanto para seu repositório {% data variables.product.prodname_dotcom %} como para o seu provedor de Repositório Central do Maven. Por exemplo, se você fizer a implementação em um Repositório Central por meio do projeto de hospedagem OSSRH, é possível que você deseje especificá-la em um repositório de gerenciamento de distribuição com o `id` definido como `ossrh`. Além disso, você pode desejar especificar {% data variables.product.prodname_registry %} em um repositório de gerenciamento de distribuição com o `id` definido como `github`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 Este fluxo de trabalho chama a ação `setup-java` duas vezes.  Cada vez que a ação `setup-java` é executada, ela sobrescreve o arquivo _settings.xml_ do Maven para a publicação de pacotes.  Para autenticação no repositório, o arquivo _settings.xml_ faz referência ao `ID`do repositório de gerenciamento de distribuição e ao nome de usuário e senha.
 
diff --git a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md
index b216efad5b..0dfd5b17d4 100644
--- a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ Para obter mais informações sobre a criação de um fluxo de trabalho de CI pa
 
 Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[Configurar o npm para uso com o {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Trabalhando com o registro npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Variáveis de ambiente](/actions/reference/environment-variables)"
 - "[Segredos criptografados](/actions/reference/encrypted-secrets)"
 - "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)"
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ No entanto, se você fornecer a chave `repositório`, o repositório nessa chave
 
 #### Efetuar a autenticação no repositório de destino
 
-Para efetuar a autenticação no registro de {% data variables.product.prodname_registry %} no seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN` do seu repositório. Ele é criado automaticamente e tem permissão de _leitura_ e _gravação_ para pacotes no repositório, em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)".
+Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 Se você quiser publicar seu pacote em um repositório diferente, você deverá usar um token de acesso pessoal (PAT) que tenha permissão para escrever pacotes no repositório de destino. Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)".
 
@@ -120,7 +120,6 @@ Se você quiser publicar seu pacote em um repositório diferente, você deverá
 
 Este exemplo armazena o segredo `GITHUB_TOKEN` na variável de ambiente `NODE_AUTH_TOKEN`. Quando a ação `setup-node` cria um arquivo *.npmrc*, ela faz referência ao token da variável de ambiente `NODE_AUTH_TOKEN`.
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 A ação `setup-node` cria um arquivo *.npmrc* no executor. Ao usar a entrada do `escopo` para a ação `setup-node`, o arquivo *.npmrc* incluirá o prefixo do escopo. Por padrão, a ação `setup-node` define o escopo no arquivo *.npmrc* na conta que contém esse arquivo do fluxo de trabalho.
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,42 +197,44 @@ Se você publicar um pacote em ambos os registros, você deverá garantir que se
 
 Certifique-se de que seu arquivo *package.json* inclua o escopo do seu repositório {% data variables.product.prodname_dotcom %} e o registro npm. Por exemplo, se você planeja publicar um pacote no repositório `octocat/npm-hello-world-test` em {% data variables.product.prodname_dotcom %} e em https://www.npmjs. om/package/@octocat/npm-hello-world-test, o nome no arquivo do seu *package.json* seria `"name": "@octocat/npm-hello-world-test"`.
 
-Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. O `GITHUB_TOKEN` existe no repositório por padrão e tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
+Para realizar operações autenticadas no registro do {% data variables.product.prodname_registry %} em seu fluxo de trabalho, você pode usar o `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 Ao usar a entrada do `escopo` para a ação `setup-node`, esta cria um arquivo *.npmrc* que inclui o prefixo do escopo. Por padrão, a ação `setup-node` define o escopo no arquivo *.npmrc* para o usuário ou organização proprietário do arquivo do fluxo de trabalho.
 
 Este fluxo de trabalho chama a ação `setup-node` duas vezes. Cada vez que a ação `setup-node` é executada, ela substitui o arquivo *.npmrc*. O arquivo *.npmrc* faz referência ao token que permite que você execute operações autenticadas com o registro do pacote a partir da variável de ambiente `NODE_AUTH_TOKEN`. O fluxo de trabalho define a variável de ambiente `NODE_AUTH_TOKEN` toda vez que o comando `publicação do npm` é executado. Primeiro com um token para publicar no npm (`NPM_TOKEN`) e, em seguida, com um token para publicar em {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
 
-{% raw %}
+
 ```yaml{:copy}
-nome: Pacote Node.js
-em:
-  versão:
-    tipos: [created]
-trabalhos:
-  criar:
-    runs-on: ubuntu-latest
-    etapas:
-    - usa: actions/checkout@v2
-    # Configura o arquivo .npmrc a ser publicado no npm
-    - usa: actions/setup-node@v1
-      com:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - executa: npm install
-    # Publica no npm
-    - executa: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # Configura o arquivo .npmrc a ser publicado nos pacotes do GitHub
-    - usa: actions/setup-node@v1
-      com:
-        registry-url: 'https://npm.pkg.github.com'
-        # Tem como padrão o usuário ou a organização proprietário do arquivo do fluxo de trabalho
-        escopo: '@octocat'
-    # Publicar nos pacotes do GitHub
-    - executar: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+name: Node.js Package
+on:
+  release:
+    types: [created]
+jobs:
+  build:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
+    steps:
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/pt-BR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/pt-BR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index 73c19f9d30..50d15222d8 100644
--- a/translations/pt-BR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/pt-BR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a a
 3. {% data reusables.actions.make-workflow-file %}
 4. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a a
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. Personalize os parâmetros no seu arquivo do fluxo de trabalho:
    - Em `github.event.project_card. olumn_id == '12345678'`, substitua `12345678` pelo ID da coluna em que você deseja desetiquetar os problemas e os pull requests que são transferidos para lá.
 
diff --git a/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md b/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md
index f41ae82830..fee54ccc82 100644
--- a/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
 2. {% data reusables.actions.make-workflow-file %}
 3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Personalize os parâmetros no seu arquivo do fluxo de trabalho:
    - Altere o valor de `on.schagen` para ditar quando você deseja que este fluxo de trabalho seja executado. No exemplo acima, o fluxo de trabalho será executado todas as segundas às 7h20 UTC. Para obter mais informações sobre fluxos de trabalho agendados, consulte "[Eventos agendados](/actions/reference/events-that-trigger-workflows#scheduled-events)".
    - Altere o valor de `responsáveis` para a lista de nomes de usuário de {% data variables.product.prodname_dotcom %} que você deseja atribuir ao problema.
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 0b58ec715d..155d2c7b89 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
@@ -11,8 +11,14 @@ versions:
 type: tutorial
 ---
 
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+Você pode adicionar um executor auto-hospedado a {{ site.data.variables.product.prodname_actions }}.
+
+Se você é um administrador de empresa ou organização, talvez você queira adicionar seus executores auto-hospedados a nível da organização ou empresa. Esta abordagem torna o executor disponível para vários repositórios na sua organização ou empresa, e também permite gerenciar seus executores em um só lugar.
 
 Para obter informações sobre sistemas operacionais compatíveis com executores auto-hospedados ou sobre como usar executores auto-hospedados com um servidor proxy, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
 
@@ -46,13 +52,15 @@ Você pode adicionar executores auto-hospedados no nível da organização, onde
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
 
+{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+
 ### Adicionar um executor auto-hospedado a uma empresa
 
 Você pode adicionar executores auto-hospedados a uma empresa, onde podem ser atribuídos a várias organizações. Os administradores da organização poderão então controlar quais repositórios podem usá-los.
 
 {% if currentVersion == "free-pro-team@latest" %}
 Para adicionar um executor auto-hospedado a uma conta corporativa, você deve ser proprietário da organização.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%}
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 Para adicionar um executor auto-hospedado no nível de empresa de
 {% data variables.product.product_location %}, você deve ser um administrador do site.
 {% endif %}
@@ -64,3 +72,13 @@ Para adicionar um executor auto-hospedado no nível de empresa de
 1. Clique em **Adicionar novo** e depois clique em **Novo executor**. Novos runners são atribuídos ao grupo padrão. Você pode modificar o grupo do executor depois de registrar o runner (executor). Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)".
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+
+{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+
+#### Disponibilizar executores corporativos para repositórios
+
+Por padrão, os executores do grupo de executores "Padrão" de uma empresa estão disponíveis para todas as organizações da empresa, mas não estão disponíveis para todos os repositórios em cada organização.
+
+Para tornar um grupo de executores auto-hospedado de nível empresarial disponível para um repositório da organização, você pode precisar alterar as configurações herdadas da organização para o grupo de executores a fim de tornar o executor disponível para repositórios na organização.
+
+Para mais informações sobre como alterar as configurações de acesso de grupo de executor, consulte "[Gerenciar acesso a executores auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
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 ae3a434be4..6853b7e5da 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
@@ -54,7 +54,7 @@ Insira um nome para o seu grupo de executor e atribua uma política para acesso
 
    **Aviso**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    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)."
 
@@ -87,7 +87,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç
 
    **Aviso**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    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)."
 
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 c8583d0852..10490d6f8a 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
@@ -66,7 +66,7 @@ Para remover um executor auto-hospedado de uma organização, você deve ser um
 
 {% if currentVersion == "free-pro-team@latest" %}
 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.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 Para remover um executor auto-hospedado no nível da empresa de
 {% data variables.product.product_location %}, você deve ser um administrador do site. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado.
 {% endif %}
diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md
index b7b973dc19..1c9ff59992 100644
--- a/translations/pt-BR/content/actions/index.md
+++ b/translations/pt-BR/content/actions/index.md
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Exemplos de códigos</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Exemplos de código de pesquisa" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Mostrar mais {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Desculpe, não há resultados para <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">Parece que não temos um exemplo que se encaixa no seu filtro.<br>Tente outro filtro ou adicione seu exemplo de código</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Saiba como adicionar um exemplo de código {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md
index ab15273a51..5e00c825fa 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Managing complex workflows
-shortTitle: Managing complex workflows
-intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} environments,{% endif %} and labels.'
+title: Gerenciar fluxos de trabalhos complexos
+shortTitle: Gerenciar fluxos de trabalhos complexos
+intro: 'Este guia mostra como usar os recursos avançados de {% data variables.product.prodname_actions %}, com gestão de segredos, trabalhos dependentes, cache, matrizes de criação{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} ambientes,{% endif %} e etiquetas.'
 versions:
   free-pro-team: '*'
   enterprise-server: '>=2.22'
@@ -13,16 +13,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### Overview
+### Visão Geral
 
-This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you work create more complex workflows.
+Este artigo descreve alguns dos recursos avançados de {% data variables.product.prodname_actions %} que ajudam você a trabalhar criar fluxos de trabalho mais complexos.
 
-### Storing secrets
+### Armazenar segredos
 
-If your workflows use sensitive data, such as passwords or certificates, you can save these in {% data variables.product.prodname_dotcom %} as _secrets_ and then use them in your workflows as environment variables. This means that you will be able to create and share workflows without having to embed sensitive values directly in the YAML workflow.
+Se os seus fluxos de trabalho usarem dados confidenciais, como senhas ou certificados, você pode salvá-los em {% data variables.product.prodname_dotcom %} como _segredos_ e usá-los nos seus fluxos de trabalho como variáveis de ambiente. Isto significa que você poderá criar e compartilhar fluxos de trabalho sem ter de incorporar valores sensíveis diretamente no fluxo de trabalho de YAML.
 
-This example action demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command.
+Esta ação de exemplo demonstra como fazer referência a um segredo existente como uma variável de ambiente e enviá-lo como um parâmetro para um comando de exemplo.
 
 {% raw %}
 ```yaml
@@ -38,13 +39,13 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
 
-### Creating dependent jobs
+### Criar trabalhos dependentes
 
-By default, the jobs in your workflow all run in parallel at the same time. So if you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the [`if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) conditional statement.
+Por padrão, os trabalhos do seu fluxo de trabalho são executadas em paralelo e ao mesmo tempo. Portanto, se você tem um trabalho que só deve ser executado após a conclusão de outro trabalho, você pode usar a palavra-chave `needs` para criar esta dependência. Se um dos trabalhos falhar, todos os trabalhos dependentes serão suprimidos. No entanto, se você precisa que os trabalhos continuem, você pode definir isso usando a declaração condicional [`se`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif).
 
-In this example, the `setup`, `build`, and `test` jobs run in series, with `build` and `test` being dependent on the successful completion of the job that precedes them:
+Neste exemplo, os trabalhos de `configuração`, `criação` e `teste` executados em série, com `criação` e `teste` sendo dependentes da conclusão bem-sucedida do trabalho que os precede:
 
 ```yaml
 jobs:
@@ -64,11 +65,11 @@ jobs:
       - run: ./test_server.sh
 ```
 
-For more information, see [`jobs.<job_id>.needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds).
+Para obter mais informações, consulte [`jobs.<job_id>.needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds).
 
-### Using a build matrix
+### Usar uma matriz de criação
 
-You can use a build matrix if you want your workflow to run tests across multiple combinations of operating systems, platforms, and languages. The build matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this build matrix will run the job multiple times, using different versions of Node.js:
+Você pode usar uma matriz de criação se quiser que seu fluxo de trabalho execute testes em várias combinações de sistemas operacionais, plataformas e linguagens. A matriz de criação é criada usando a palavra-chave `estratégia`, que recebe as opções de compilação como um array. Por exemplo, essa matriz de criação irá executar o trabalho várias vezes, usando diferentes versões do Node.js:
 
 {% raw %}
 ```yaml
@@ -85,13 +86,14 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see [`jobs.<job_id>.strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
+Para obter mais informações, consulte [`>jobs.<job_id>.strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
 
-### Caching dependencies
+{% if currentVersion == "free-pro-team@latest" %}
+### Memorizar dependências
 
-{% data variables.product.prodname_dotcom %}-hosted runners are started as fresh environments for each job, so if your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. Once the cache is created, it is available to all workflows in the same repository.
+Executores hospedados em {% data variables.product.prodname_dotcom %} são iniciados como ambientes novos para cada trabalho. Portanto, se os seus trabalhos reutilizam dependências regularmente, você pode considerar fazer armazenamento em cache desses arquivos para ajudar a melhorar o desempenho. Após a criação do armazenamento em cache, ele fica disponível para todos os fluxos de trabalho no mesmo repositório.
 
-This example demonstrates how to cache the ` ~/.npm` directory:
+Este exemplo demonstra como armazenar em cache o diretório `~/.npm`:
 
 {% raw %}
 ```yaml
@@ -110,11 +112,12 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+Para obter mais informações, consulte "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Memorizar dependências para acelerar fluxos de trabalho</a>".
+{% endif %}
 
-### Using databases and service containers
+### Usar bancos de dados e contêineres de serviço
 
-If your job requires a database or cache service, you can use the [`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) keyword to create an ephemeral container to host the service; the resulting container is then available to all steps in that job and is removed when the job has completed. This example demonstrates how a job can use `services` to create a `postgres` container, and then use `node` to connect to the service.
+Se sua tarefa exigir um banco de dados ou serviço de cache, você poderá usar a palavra-chave [`serviços`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) para criar um contêiner efêmero para hospedar o serviço; o contêiner resultante ficará disponível em todas as etapas do trabalho e será removido quando o trabalho for concluído. Este exemplo demonstra como um trabalho pode usar `serviços` para criar um contêiner `postgres` e, em seguida, usar o `nó` para conectar-se ao serviço.
 
 ```yaml
 jobs:
@@ -136,39 +139,47 @@ jobs:
           POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using databases and service containers](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)."
+Para obter mais informações, consulte "[Usar bancos de dados e contêineres de serviço](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)".
 
-### Using labels to route workflows
+### Usar etiquetas para encaminhar fluxos de trabalho
 
-This feature helps you assign jobs to a specific self-hosted runner. If you want to be sure that a particular type of runner will process your job, you can use labels to control where jobs are executed. You can assign labels to a self-hosted runner, and then refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.
+Esse recurso ajuda você a atribuir tarefas a um executor hospedado específico. Se você quiser ter certeza de que um determinado tipo de executor irá processar seu trabalho, você pode usar etiquetas para controlar os locais onde os trabalhos são executados. Você pode atribuir etiquetas a um corredor hospedado e, em seguida, consultá-las no fluxo de trabalho de YAML, garantindo que o trabalho seja encaminhado de uma forma previsível.
 
-This example shows how a workflow can use labels to specify the required runner:
+{% if currentVersion == "github-ae@latest" %}
+Este exemplo mostra como um fluxo de trabalho pode usar etiquetas para especificar o executor obrigatório:
 
+```yaml
+jobs:
+  example-job:
+    runs-on: [AE-runner-for-CI]
+```
+
+Para obter mais informações, consulte ["Usar etiquetas com {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners)".
+{% else %}
 ```yaml
 jobs:
   example-job:
     runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-For more information, see  ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-### Using environments
-
-You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)."
+Para obter mais informações, consulte ["Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)".
 {% endif %}
 
-### Using a workflow template
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+### Usar ambientes
+
+Você pode configurar ambientes com regras de proteção e segredos. Cada trabalho em um fluxo de trabalho pode fazer referência a um único ambiente. Todas as regras de proteção configuradas para o ambiente têm de ser aprovadas antes que um trabalho de referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)".
+{% endif %}
+
+### Usar um modelo do fluxo de trabalho
 
 {% data reusables.actions.workflow-template-overview %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. If your repository already has existing workflows: In the upper-left corner, click **New workflow**.
-  ![Create a new workflow](/assets/images/help/repository/actions-new-workflow.png)
-1. Under the name of the template you'd like to use, click **Set up this workflow**.
-  ![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png)
+1. Caso o seu repositório tenha fluxos de trabalho existentes: No canto superior esquerdo, clique em **Novo fluxo de trabalho**. ![Criar um novo fluxo de trabalho](/assets/images/help/repository/actions-new-workflow.png)
+1. Sob, nome do template que você gostaria de usar, clique em **Configurar este fluxo de trabalho**. ![Configurar este fluxo de trabalho](/assets/images/help/settings/actions-create-starter-workflow.png)
 
-### Next steps
+### Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)."
+Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Compartilhar fluxos de trabalho com a sua organização](/actions/learn-github-actions/sharing-workflows-with-your-organization)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index 869279f339..63f42130d4 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index 58603366da..7ad53224e7 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ Se você precisar compartilhar fluxos de trabalho e outros recursos de {% data v
 
 ### Criar um modelo do fluxo de trabalho
 
-Os modelos do fluxo de trabalh podem ser criados por usuários com acesso de gravação ao repositório `.github` da organização. Em seguida, os modelos podem ser usados por integrantes da organização com permissão para criar fluxos de trabalho. Os modelos do fluxo de trabalho podem ser usados para criar novos fluxos de trabalho nos repositórios públicos de uma organização; para usar modelos para criar fluxos de trabalho em repositórios privados, a organização deve fazer parte de um plano corporativo ou do GitHub One.
+Os modelos do fluxo de trabalh podem ser criados por usuários com acesso de gravação ao repositório `.github` da organização. Em seguida, os modelos podem ser usados por integrantes da organização com permissão para criar fluxos de trabalho. Os modelos do fluxo de trabalho podem ser usados para criar novos fluxos de trabalho nos repositórios públicos de uma organização; para usar modelos para criar fluxos de trabalho em repositórios privados, a organização deve fazer parte de um plano corporativo.
 
 Este procedimento demonstra como criar um modelo de fluxo de trabalho e um arquivo de metadados. O arquivo de metadados descreve como o modelo é apresentado aos usuários quando estão criando um novo fluxo de trabalho.
 
 1. Se já não existir, crie um novo repositório público denominado `.github` na sua organização.
-1. Crie um diretório denominado `workflow-templates`.
-1. Crie seu novo arquivo de fluxo de trabalho dentro do diretório `workflow-templates`.
+2. Crie um diretório denominado `workflow-templates`.
+3. Crie seu novo arquivo de fluxo de trabalho dentro do diretório `workflow-templates`.
 
    Se você precisar referir-se ao branch-padrão de um repositório, você poderá usar o espaço reservado `branch$default`. Quando um fluxo de trabalho é criado usando seu modelo, o espaço reservado será automaticamente substituído pelo nome do branch-padrão do repositório.
 
@@ -52,7 +52,7 @@ Este procedimento demonstra como criar um modelo de fluxo de trabalho e um arqui
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. Crie um arquivo de metadados dentro do diretório `workflow-templates`. O arquivo de metadados deve ter o mesmo nome do arquivo de fluxo de trabalho, mas em vez da extensão `.yml`, deve-se adicionar `.properties.json`. Por exemplo, este arquivo denominado `octo-organization-ci.properties.json` contém os metadados para um arquivo de fluxo de trabalho denominado `octo-organization-ci.yml`:
+4. Crie um arquivo de metadados dentro do diretório `workflow-templates`. O arquivo de metadados deve ter o mesmo nome do arquivo de fluxo de trabalho, mas em vez da extensão `.yml`, deve-se adicionar `.properties.json`. Por exemplo, este arquivo denominado `octo-organization-ci.properties.json` contém os metadados para um arquivo de fluxo de trabalho denominado `octo-organization-ci.yml`:
    ```yaml
    {
        "name": "Octo Organization Workflow",
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..db9631ba24
--- /dev/null
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: Aprovando execuções de fluxo de trabalho das bifurcações públicas
+intro: 'Quando um primeiro contribuidor envia um pull request para um repositório público, um mantenedor com acesso de gravação deverá aprovar qualquer execução de fluxo de trabalho.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+As bifurcações de repositórios públicos podem enviar pull requests que proponham alterações nos fluxos de trabalho de {% data variables.product.prodname_actions %} de um repositório. Embora os fluxos de trabalho das bifurcações não tenham acesso a dados confidenciais como segredos, podem ser uma dor de cabeça para os mantenedores se forem modificados para fins abusivos. Para ajudar a evitar isso, os fluxos de trabalho em pull requests não são executados automaticamente se forem recebidos de contribuidores pela primeira vez e devem ser aprovados primeiro.
+
+Os mantenedores com acesso de gravação ao repositório podem usar o procedimento a seguir para revisar e executar fluxos de trabalho em pull requests dos primeiros colaboradores. Após um contribuidor ter pelo menos um pull request mesclado no repositório de um projeto, todos os pull requests futuros da bifurcação daquele contribuidor executarão automaticamente os fluxos de trabalho.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspecione as alterações propostas no pull request e certifique-se de que você esteja confortável em executar seus fluxos de trabalho no branch do pull request. Você deve estar especialmente alerta para qualquer mudança proposta no diretório `.github/workflows/` que afete os arquivos do fluxo de trabalho.
+1. Se você estiver confortável em executar fluxos de trabalho no branch do pull request, retorne para a aba {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversation** e, em "Fluxo de trabalho(s) aguardando aprovação", clique em **Aprovar e executar**.
+
+   ![Aprovar e executar fluxos de trabalho](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index dc02608144..4f6215fa0f 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Desabilitar e habilitar um fluxo de trabalho
-intro: 'Você pode desabilitar e reabilitar um fluxo de trabalho usando {% data variables.product.prodname_dotcom %} ou a API REST.'
+intro: 'Você pode desabilitar e habilitar novamente um fluxo de trabalho usando a interface do usuário de {% data variables.product.prodname_dotcom %}, a API REST, ou {% data variables.product.prodname_cli %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-Desabilitar um fluxo de trabalho permite que você impeça que um fluxo de trabalho seja acionado sem ter de excluir o arquivo do repositório. Você pode facilmente reabilitar o fluxo de trabalho novamente em {% data variables.product.prodname_dotcom %}. Também é possível desabilitar e habilitar um fluxo de trabalho usando a API REST. Para obter mais informações, consulte a "[Ações da REST API](/rest/reference/actions#workflows)".
+Desabilitar um fluxo de trabalho permite que você impeça que um fluxo de trabalho seja acionado sem ter de excluir o arquivo do repositório. Você pode facilmente reabilitar o fluxo de trabalho novamente em {% data variables.product.prodname_dotcom %}.
 
 Desabilitar temporariamente um fluxo de trabalho pode ser útil em vários cenários. Estes são alguns exemplos em que desabilitar um fluxo de trabalho pode ser útil:
 
@@ -27,7 +27,9 @@ Desabilitar temporariamente um fluxo de trabalho pode ser útil em vários cená
 
 {% endwarning %}
 
-### Desabilitar um fluxo de trabalho
+### Desabilitar e habilitar fluxos de trabalho com a interface de {% data variables.product.prodname_dotcom %}
+
+#### Desabilitar um fluxo de trabalho
 
 Você pode desabilitar manualmente um fluxo de trabalho para que não realize qualquer execução de fluxo de trabalho. Um fluxo de trabalho desabilitado não é excluído e pode ser reabilitado.
 
@@ -37,7 +39,7 @@ Você pode desabilitar manualmente um fluxo de trabalho para que não realize qu
 1. Clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![menu de ações kebab](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. Clique **Desabilitar fluxo de trabalho**. ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png) O fluxo de trabalho desabilitado está marcado {% octicon "stop" aria-label="The stop icon" %} para indicar seu status. ![lista de ações desabilitada no fluxo de trabalho](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### Habilitar um fluxo de trabalho
+#### Habilitar um fluxo de trabalho
 
 Você pode habilitar novamente um fluxo de trabalho que foi desabilitado anteriormente.
 
@@ -45,3 +47,23 @@ Você pode habilitar novamente um fluxo de trabalho que foi desabilitado anterio
 {% data reusables.repositories.actions-tab %}
 1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja habilitar. ![ações selecionam um fluxo de trabalho desativado](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. Clique em **Habilitar o fluxo de trabalho**. ![ações habilitam fluxo de trabalho](/assets/images/help/repository/actions-enable-workflow.png)
+
+### Desabilitar e habilitar fluxos de trabalho com {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para desabilitar um fluxo de trabalho, use o subcomando `desabilitar fluxo de trabalho`. Substitua `fluxo de trabalho` pelo nome, ID ou arquivo do fluxo de trabalho que você deseja desabilitar. Por exemplo, `"Verificador de Link"`, `1234567`, ou `"link-check-test.yml"`. Se você não especificar um fluxo de trabalho, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher um fluxo de trabalho.
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+Para habilitar um fluxo de trabalho, use o subcomando `habilitar fluxo de trabalho`. Substitua `fluxo de trabalho` pelo nome, ID ou arquivo do fluxo de trabalho que você deseja habilitar. Por exemplo, `"Verificador de Link"`, `1234567`, ou `"link-check-test.yml"`. Se você não especificar um fluxo de trabalho, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher um fluxo de trabalho.
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### Desabilitar e habilitar fluxos de trabalho por meio da API REST
+
+Também é possível desabilitar e habilitar um fluxo de trabalho usando a API REST. Para obter mais informações, consulte a "[Ações da REST API](/rest/reference/actions#workflows)".
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index be7a86f423..b52d30af09 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} Por padrão, {% data variables.product.product_name %} armazena registros de criação por 90 dias e você pode personalizar este período de retenção, dependendo do tipo de repositório. Para obter mais informações, consulte "[Configurar o período de retenção para artefatos e registros do GitHub Actions no seu repositório](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} armazena registros de criação completos e artefatos por 90 dias.{% endif %}
 
+### Faça o download dos artefatos com a interface do usuário de {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### Faça o download dos artefatos com {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+{% data variables.product.prodname_cli %} irá fazer o download de cada artefato em diretórios separados baseados no nome do artefato. Se apenas um único artefato for especificado, ele será extraído para o diretório atual.
+
+Para fazer o download de todos os artefatos gerados pela execução de um fluxo de trabalho, use o subcomando `fazer download`. Substitua `run-id` pelo ID da execução do qual você deseja fazer o download dos artefatos. Se você não especificar um `run-id`, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher uma execução recente.
+
+```shell
+gh run download <em>run-id</em>
+```
+
+Para fazer o download de um artefato específico de uma execução, use o subcomando `fazer download`. Substitua `run-id` pelo ID da execução do qual você deseja fazer o download dos artefatos. Substitua `artifact-name` pelo nome do artefato que você deseja baixar.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+Você pode especificar mais de um artefato.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+Para fazer o download de artefatos específicos em todas as execuções em um repositório, use o subcomando `fazer download`.
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/index.md b/translations/pt-BR/content/actions/managing-workflow-runs/index.md
index 8304d5aff7..c5f976ce39 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/index.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index ce9f30443a..c3125875ec 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Executando manualmente um fluxo de trabalho
-intro: 'Quando um fluxo de trabalho é configurado para ser executado no evento `workflow_dispatch`, você pode executar o fluxo de trabalho usando a API REST ou na aba Ações em {% data variables.product.prodname_dotcom %}.'
+intro: 'Quando um fluxo de trabalho é configurado para ser executado no evento `workflow_dispatch`, você pode executar o fluxo de trabalho usando a aba de Ações em {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %} ou a API REST.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -28,6 +28,40 @@ Para acionar o evento `workflow_dispatch` em {% data variables.product.prodname_
 1. Acima da lista de execuções de fluxo de trabalho, selecione **Executar**de fluxo de trabalho . ![expedição de fluxo de trabalho ações](/assets/images/actions-workflow-dispatch.png)
 1. Selecione o ramo onde o fluxo de trabalho será executado e digite os parâmetros de entrada usados pelo fluxo de trabalho. Clique em **Executar**de fluxo de trabalho . ![ações executar manualmente fluxo de trabalho](/assets/images/actions-manually-run-workflow.png)
 
+### Executar um fluxo de trabalho usando {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para executar um fluxo de trabalho, use o subcomando `execução do fluxo de trabalho`. Substitua o parâmetro `fluxo de trabalho` Pelo nome, ID ou nome do arquivo do fluxo de trabalho que você deseja executar. Por exemplo, `"Verificador de Link"`, `1234567`, ou `"link-check-test.yml"`. Se você não especificar um fluxo de trabalho, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher um fluxo de trabalho.
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+Se o fluxo de trabalho aceitar entradas, {% data variables.product.prodname_cli %} solicitará que você os insira. Como alternativa, você pode usar `-f` ou `-F` para adicionar uma entrada no formato `key=value`. Use `-F` para ler de um arquivo.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+Você também pode passar as entradas como JSON usando a entrada padrão.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+Para executar um fluxo de trabalho em um branch que não seja o branch padrão do repositório, use o sinalizador`--ref`.
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+Para visualizar o progresso da execução do fluxo de trabalho, use o subcomando `executar inspeção` e selecione a execução na lista interativa.
+
+```shell
+gh run watch
+```
+
 ### Executar um fluxo de trabalho usando a API REST
 
 Ao usar a API REST, você configura as entradas de `` e `ref` como parâmetros do corpo de solicitação. Se as entradas forem omitidas, os valores padrão definidos no arquivo de fluxo de trabalho ão usados.
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md
index 5c4f12994b..8243863d89 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Execute novamente um fluxo de trabalho usando a interface do usuário de {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. No canto superior direito do fluxo de trabalho, use o menu suspenso **Reexecutar trabalhos** e selecione **Reexecutar todos os trabalhos**{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### Execute novamente um fluxo de trabalho usando {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para executar novamente um fluxo de trabalho com falha, use o subcomando `executar novamente`. Substitua `run-id` pelo ID da execução com falha que você deseja executar novamente.  Se você não especificar um `run-id`, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher uma execução com falha recente.
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+Para visualizar o progresso da execução do fluxo de trabalho, use o subcomando `executar inspeção` e selecione a execução na lista interativa.
+
+```shell
+gh run watch
+```
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 225ee08dd5..5e56649428 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. Em **Artefatos**, clique em
-{% octicon "trashcan" aria-label="The trashcan icon" %} ao lado do artefato que você deseja remover.
+{% octicon "trash" aria-label="The trash icon" %} ao lado do artefato que você deseja remover.
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![Menu suspenso para excluir o artefato](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index e0fba36ecb..2529ec4c2f 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ Após excluir os registros, o botão **Excluir todos os registros** será removi
 1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. Para excluir os arquivos de registro, clique no botão **Excluir todos os registros** e revise a instrução de confirmação. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) Depois que os registros forem excluídos, o botão **Excluir todos os registros** é removido para indicar que nenhum arquivo de registro permanece na execução do fluxo de trabalho.
 {% endif %}
+
+### Visualizar registros com {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+Para visualizar o registro para uma tarefa específica, use o subcomando `executar a vista`. Substitua `run-id` pelo ID da execução que você deseja visualizar os registros. {% data variables.product.prodname_cli %} retorna um menu interativo para você escolher um trabalho a partir da execução. Se você não especificar `run-id`, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher uma execução recente e, em seguida, irá retornar outro menu interativo para você escolher um trabalho da execução.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+Você também pode usar o sinalizador `--job` para especificar um ID de trabalho. Substitua `job-id` pelo ID do trabalho para o qual você deseja exibir os registros.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Você pode usar `grep` para pesquisar o registro. Por exemplo, este comando retornará todas as entradas do registro que contêm a palavra `erro`.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+Para filtrar os registros para quaisquer etapas que falharam, use `--log-failed` em vez de `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/pt-BR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index e547ffd296..bc3d546f0f 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Visualizar histórico de execução do fluxo de trabalho em {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### Visualizar histórico de execução do fluxo de trabalho com {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+#### Visualizando execuções de fluxo de trabalho recentes
+
+Para listar as execuções recentes do fluxo de trabalho, use o subcomando `executar lista`.
+
+```shell
+gh run list
+```
+
+Para especificar o número máximo de execuções a retornar, você pode usar o sinalizador `-L` ou `--limit`. O padrão é `10`.
+
+```shell
+gh run list --limit 5
+```
+
+Para somente retornar execuções para o fluxo de trabalho especificado, você pode usar o sinalizador `-w` ou `--workflow`.  Substitua `fluxo de trabalho` por um nome de fluxo de trabalho, ID do fluxo de trabalho ou nome de arquivo do fluxo de trabalho. Por exemplo, `"Verificador de Link"`, `1234567`, ou `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### Visualizar detalhes para uma execução específica do fluxo de trabalho
+
+Para exibir detalhes para uma execução específica do fluxo de trabalho, use o subcomando `executar visualização`. Substitua `run-id` pelo ID da execução que você deseja visualizar. Se você não especificar um `run-id`, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher uma execução recente.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+Para incluir etapas de trabalho na saída, use o sinalizador `-v` ou `--verbose`.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+Para visualizar detalhes de um trabalho específico na execução, use o sinalizador `-j` ou `--job`.  Substitua `job-id` pelo ID do trabalho que você deseja visualizar.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+Para ver o registro completo para um trabalho, use o sinalizador `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Use o sinalizador `--exit-status` para sair com um status diferente de zero se a execução falhar. Por exemplo:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md
index 34e16d7917..18cd29a134 100644
--- a/translations/pt-BR/content/actions/quickstart.md
+++ b/translations/pt-BR/content/actions/quickstart.md
@@ -1,6 +1,6 @@
 ---
 title: Início rápido para GitHub Actions
-intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
+intro: 'Experimente as funcionalidades de {% data variables.product.prodname_actions %} em 5 minutos ou menos.'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates
@@ -19,9 +19,9 @@ topics:
 
 ### Introdução
 
-You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}.
+Você precisa apenas de um repositório de {% data variables.product.prodname_dotcom %} para criar e executar um fluxo de trabalho de {% data variables.product.prodname_actions %}. Neste guia, você adicionará um fluxo de trabalho que demonstra algumas das funcionalidades essenciais de {% data variables.product.prodname_actions %}.
 
-The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository.
+O exemplo a seguir mostra como os trabalhos de {% data variables.product.prodname_actions %} podem ser acionados automaticamente, onde são executados e como podem interagir com o código no seu repositório.
 
 ### Criar o seu primeiro fluxo de trabalho
 
@@ -51,7 +51,7 @@ The following example shows you how {% data variables.product.prodname_actions %
     {% endraw %}
 3. Vá até o final da página e selecione **Criar um novo branch para este commit e iniciar um pull request**. Em seguida, para criar um pull request, clique em **Propor novo arquivo**. ![Arquivo do fluxo de trabalho do commit](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
 
-Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
+Fazer commit do arquivo de fluxo de trabalho para um branch em seu repositório aciona o evento `push` e executa seu fluxo de trabalho.
 
 ### Visualizar seus resultados do fluxo de trabalho
 
@@ -63,14 +63,14 @@ Committing the workflow file to a branch in your repository triggers the `push`
 1. Na lista de execuções do fluxo de trabalho, clique no nome da execução que você deseja visualizar.
 
    ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/actions-quickstart-run-name.png)
-1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
+1. Em **Trabalhos**, clique no trabalho **Explore-GitHub-Actions**.
 
-   ![Locate job](/assets/images/help/repository/actions-quickstart-job.png)
-1. The log shows you how each of the steps was processed. Expand any of the steps to view its details.
+   ![Localizar trabalho](/assets/images/help/repository/actions-quickstart-job.png)
+1. O registro mostra como cada uma das etapas foi processada. Expanda qualquer um dos passos para ver seus detalhes.
 
-   ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png)
+   ![Exemplos de resultados do fluxo de trabalho](/assets/images/help/repository/actions-quickstart-logs.png)
 
-   For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png)
+   Por exemplo, você pode ver a lista de arquivos no seu repositório: ![Exemplo do detalhe da ação](/assets/images/help/repository/actions-quickstart-log-detail.png)
 
 ### Mais modelos de fluxo de trabalho
 
@@ -78,10 +78,10 @@ Committing the workflow file to a branch in your repository triggers the `push`
 
 ### Próximas etapas
 
-The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. Mas este é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}:
+O exemplo do fluxo de trabalho que você acabou de adicionar é executado cada vez que o código for enviado para o branch e mostra como {% data variables.product.prodname_actions %} pode funcionar com o conteúdo do seu repositório. Mas este é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}:
 
 - O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos.
-- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
+- Você pode usar um fluxo de trabalho para instalar aplicativos de teste de software e fazer com que testem automaticamente seu código nos executores de {% data variables.product.prodname_dotcom %}.
 
 O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}:
 
diff --git a/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md b/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md
index 7c31727fcc..6f473530af 100644
--- a/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/pt-BR/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ O token também está disponível no contexto `github.token`. Para obter mais in
 
 ### Usar o `GITHUB_TOKEN` em um fluxo de trabalho
 
-Para usar o segredo `GITHUB_TOKEN`, você deve referenciá-lo no arquivo do fluxo de trabalho. Usar um token pode compreender disponibilizar o token como uma entrada para uma ação que o exige ou fazer solicitações de API {% data variables.product.prodname_dotcom %} autenticadas.
+Você pode usar o `GITHUB_TOKEN` ao usar a sintaxe padrão para fazer referência a segredos: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Exemplos de uso do `GITHUB_TOKEN` incluem passar o token como uma entrada para uma ação ou usá-lo para fazer uma solicitação da API de {% data variables.product.prodname_dotcom %} autenticada.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**Importante:** Uma ação pode acessar o `GITHUB_TOKEN` por meio do contexto `github.token`, mesmo que o fluxo de trabalho não passe explicitamente o `GITHUB_TOKEN` para a ação. Como uma boa prática de segurança, você deve sempre certificar-se de que as ações só têm o acesso mínimo necessário limitando as permissões concedidas ao `GITHUB_TOKEN`. Para obter mais informações, consulte "[Permissões para o `GITHUB_TOKEN`](#permissions-for-the-github_token)".
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### Exemplo de passar um `GITHUB_TOKEN` como uma entrada
+#### Exemplo 1: Passar o `GITHUB_TOKEN` como uma entrada
 
 Este exemplo de fluxo de trabalho usa a [ação etiquetadora](https://github.com/actions/labeler), que exige o `GITHUB_TOKEN` como o valor para o parâmetro de entrada do `token`:
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### Exemplo de acessar o API REST
+#### Exemplo 2: chamando a API REST
 
 Você pode usar o `GITHUB_TOKEN` para fazer chamadas de API autenticada. Este exemplo de fluxo de trabalho cria um problema usando a API REST de {% data variables.product.prodname_dotcom %}:
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,15 +88,31 @@ Você pode usar o `GITHUB_TOKEN` para fazer chamadas de API autenticada. Este ex
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n O hash do commit foi: _${{ github.sha }}_."
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### Permissões para o `GITHUB_TOKEN`
 
-Para obter informações sobre os pontos de extremidade da API que {% data variables.product.prodname_github_apps %} pode acessar com cada permissão, consulte "[Permissões de {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps). "
+Para obter informações sobre quais os pontos de extremidade da API de {% data variables.product.prodname_github_apps %} podem acessar com cada permissão, consulte "[Permissões de {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)."
 
-| Permissão               | Tipo de acesso   | Acesso pelos repositórios bifurcados |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão. As pessoas com permissões de administrador para uma empresa, organização ou repositório podem definir as permissões padrão como permissivas ou restritas. Para obter mais informações sobre como definir as permissões padrão para `GITHUB_TOKEN` para a sua empresa, organização ou repositório, consulte "[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)," "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organizaçãon](/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)," ou "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para um repositório](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
+
+| Escopo                  | Acesso padrão<br>(permissivo) | Acesso padrão<br>(restrito) | Acesso máximo<br>por repositórios bifurcados |
+| ----------------------- | ----------------------------------- | --------------------------------- | -------------------------------------------------- |
+| 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                                            |
+| Problemas               | leitura/gravação                    | nenhum                            | leitura                                            |
+| metadados               | leitura                             | leitura                           | leitura                                            |
+| pacotes                 | leitura/gravação                    | nenhum                            | leitura                                            |
+| Pull requests           | leitura/gravação                    | nenhum                            | leitura                                            |
+| Projetos de repositório | leitura/gravação                    | nenhum                            | leitura                                            |
+| eventos de segurança    | leitura/gravação                    | nenhum                            | leitura                                            |
+| Status                  | leitura/gravação                    | nenhum                            | leitura                                            |
+{% else %}
+| Escopo                  | Tipo de acesso   | Acesso pelos repositórios bifurcados |
 | ----------------------- | ---------------- | ------------------------------------ |
 | ações                   | leitura/gravação | leitura                              |
 | Verificações            | leitura/gravação | leitura                              |
@@ -94,9 +124,32 @@ Para obter informações sobre os pontos de extremidade da API que {% data varia
 | Pull requests           | leitura/gravação | leitura                              |
 | Projetos de repositório | leitura/gravação | leitura                              |
 | Status                  | leitura/gravação | leitura                              |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### Modificar as permissões para o `GITHUB_TOKEN`
+
+Você pode modificar as permissões para o `GITHUB_TOKEN` nos arquivos de fluxo de trabalho individuais. Se as permissões padrão para o `GITHUB_TOKEN` forem restritivas, você poderá ter que elevar as permissões para permitir que algumas ações e comandos sejam executados com sucesso. Se as permissões padrão forem permissivas, você poderá editar o arquivo do fluxo de trabalho para remover algumas permissões do `GITHUB_TOKEN`. Como uma boa prática de segurança, você deve conceder ao `GITHUB_TOKEN` o acesso menos necessário.
+
+Você pode ver as permissões que o `GITHUB_TOKEN` tem para uma tarefa específica na seção "Configurar trabalho" no registro de execução do fluxo de trabalho. Para obter mais informações, consulte "[Usar registros de execução do fluxo de trabalho](/actions/managing-workflow-runs/using-workflow-run-logs)".
+
+Você pode usar a chave de `permissões` no seu arquivo de fluxo de trabalho para modificar as permissões para o `GITHUB_TOKEN` para um fluxo de trabalho inteiro ou para trabalhos individuais. Isso permite que você configure as permissões mínimas necessárias para um fluxo de trabalho ou trabalho. Quando a chave `permissions` for usada, todas as permissões não especificadas são configuradas como sem acesso, com exceção do escopo de `metadados`, que sempre recebe acesso de leitura.
+
+{% data reusables.github-actions.forked-write-permission %}
+
+Os dois exemplos de fluxo de trabalho anteriores neste artigo mostram a chave de `permissões` usada no nível de fluxo de trabalho e no nível de trabalho. Em [Exemplo 1](#example-1-passing-the-github_token-as-an-input) as duas permissões são especificadas para todo o fluxo de trabalho. No [Exemplo 2](#example-2-calling-the-rest-api) de acesso de gravação é concedido para um único escopo para um único trabalho.
+
+Para obter detalhes completos sobre a chave de `permissões`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions).
+
+##### Como as permissões são calculadas para um trabalho de fluxo de trabalho
+
+As permissões para o `GITHUB_TOKEN` são inicialmente definidas como a configuração padrão para a empresa, organização ou repositório. Se o padrão for definido como permissões restritas em qualquer um desses níveis, isso irá aplicar-se aos repositórios relevantes. Por exemplo, Se você escolher o padrão restrito no nível da organização, todos os repositórios nessa organização usarão as permissões restritas como padrão. As permissões serão, então, ajustadas com base em qualquer configuração dentro do arquivo de fluxo de trabalho, primeiro no nível de fluxo de trabalho e, em seguida, no nível de trabalho. Por fim, se o fluxo de trabalho foi acionado por um pull request de um repositório bifurcado, e a configuração **Enviar tokens de gravação para fluxos de trabalho de pull requests** não estiver selecionada, as permissões serão ajustadas para alterar qualquer permissão de gravação para somente leitura.
+
+#### Conceder permissões adicionais
+{% endif %}
+
 Se você precisa de um token que exige premissões que não estão disponíveis no `GITHUB_TOKEN`, é possível criar um token de acesso pessoal e configurá-lo como um segredo no repositório:
 
 1. Use ou crie um token com as permissões adequadas para o repositório. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
diff --git a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index 3536ad8563..43d6ad6023 100644
--- a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ Os contextos são uma forma de acessar informações sobre execuções de fluxo
 | Nome do contexto | Tipo     | Descrição                                                                                                                                                                                                                                         |
 | ---------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `github`         | `objeto` | Informações sobre a execução do fluxo de trabalho. Para obter mais informações, consulte [contexto `github`](#github-context).                                                                                                                    |
-| `env`            | `objeto` | Contém variáveis de ambiente definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações, consulte o contexto contexto [`env`](#env-context).                                                                               |
+| `env`            | `objeto` | Contém variáveis de ambiente definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações, consulte o contexto [`env`](#env-context).                                                                                        |
 | `job`            | `objeto` | Tem informações sobre o trabalho em execução no momento. Para obter mais informações, consulte [contexto `trabalho`](#job-context).                                                                                                               |
 | `steps`          | `objeto` | Informações sobre as etapas que foram executadas neste trabalho. Para obter mais informações, consulte [contexto `etapas`](#steps-context).                                                                                                       |
 | `runner`         | `objeto` | Informações sobre o executor do trabalho atual. Para obter mais informações, consulte [`runner` context](#runner-context).                                                                                                                        |
@@ -93,11 +93,11 @@ O contexto `github` context contém informações sobre a execução do fluxo de
 | `github.action`           | `string` | O nome da ação atualmente em execução. O {% data variables.product.prodname_dotcom %} remove os caracteres especiais ou usa o nome `executar` quando a etapa atual executa um script.  Se você usar a mesma ação mais de uma vez no mesmo trabalho, o nome incluirá um sufixo com o número de sequência.  Por exemplo, o primeiro script que você executa será denominado `run1`, e o segundo script será denominado `run2`. Da mesma forma, a segunda invocação de `actions/checkout` será `actionscheckout2`. |
 | `github.action_path`      | `string` | O caminho onde está localizada a sua ação. Você pode usar esse caminho para acessar facilmente os arquivos localizados no mesmo repositório que sua ação. Este atributo só é suportado em ações de etapas de execução compostas.                                                                                                                                                                                                                                                                                |
 | `github.actor`            | `string` | Login do usuário que iniciou a execução do fluxo de trabalho.                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `github.base_ref`         | `string` | `base_ref` ou branch alvo da pull request em uma execução de fluxo de trabalho. Essa propriedade só está disponível quando o evento que aciona a execução do fluxo de trabalho é uma `pull_request`.                                                                                                                                                                                                                                                                                                            |
+| `github.base_ref`         | `string` | `base_ref` ou branch alvo da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`.                                                                                                                                                                                                                                                                                  |
 | `github.event`            | `objeto` | Carga de evento de webhook completa. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows/)". Você pode acessar as propriedades individuais do evento usando este contexto.                                                                                                                                                                                                                                                                  |
 | `github.event_name`       | `string` | Nome do evento que acionou a execução do fluxo de trabalho.                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | `github.event_path`       | `string` | O caminho para a carga completa do evento do webhook no executor.                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `github.head_ref`         | `string` | `head_ref` ou branch de origem da pull request em uma execução de fluxo de trabalho. Essa propriedade só está disponível quando o evento que aciona a execução do fluxo de trabalho é uma `pull_request`.                                                                                                                                                                                                                                                                                                       |
+| `github.head_ref`         | `string` | `head_ref` ou branch de origem da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`.                                                                                                                                                                                                                                                                             |
 | `github.job`              | `string` | O [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual.                                                                                                                                                                                                                                                                                                                                                                                                               |
 | `github.ref`              | `string` | Branch ou ref tag que acionou a execução do fluxo de trabalho. Para branches, está no formato  `refs/heads/<branch_name>`, e, para tags, está em `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                            |
 | `github.repository`       | `string` | Nome do repositório e o proprietário. Por exemplo, `Codertocat/Hello-World`.                                                                                                                                                                                                                                                                                                                                                                                                                                    |
@@ -323,7 +323,7 @@ Retorna `true` se `searchString` terminar com `searchValue`. Essa função não
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-Substitui valores na `string` pela variável `replaceValueN`. As variáveis na `string` são especificadas usando a sintaxe `{N}`, onde `N` é um inteiro. Você deve especificar pelo menos um `replaceValue` e `string`. Não há máximo para o número de variáveis (`replaceValueN`) que você pode usar. Use chaves duplas como escape das chaves.
+Substitui valores na `string` pela variável `replaceValueN`. As variáveis na `string` são especificadas usando a sintaxe `{N}`, onde `N` é um inteiro. Você deve especificar pelo menos um `replaceValue` e `string`. Não há máximo para o número de variáveis (`replaceValueN`) que você pode usar. Escape de chaves usando chaves duplas.
 
 ##### Exemplo
 
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
diff --git a/translations/pt-BR/content/actions/reference/encrypted-secrets.md b/translations/pt-BR/content/actions/reference/encrypted-secrets.md
index 824afa8688..6d743d1abd 100644
--- a/translations/pt-BR/content/actions/reference/encrypted-secrets.md
+++ b/translations/pt-BR/content/actions/reference/encrypted-secrets.md
@@ -29,15 +29,9 @@ Para segredos armazenados no nível do ambiente, você pode habilitar os revisor
 
 #### Nomear os seus segredos
 
-As regras a seguir aplicam-se aos nomes dos segredos:
+{% data reusables.codespaces.secrets-naming %}. Por exemplo, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}um segredo criado a nível de ambiente deve ter um nome exclusivo nesse ambiente, {% endif %}um segredo criado no nível do repositório deve ter um nome exclusivo nesse repositório, e um segredo criado no nível da organização deve ter um nome exclusivo nesse nível.
 
-* Os nomes dos segredos podem conter apenas caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) or sublinhado (`_`). Não são permitidos espaços.
-* Os nomes dos segredos não devem começar com o prefixo `GITHUB_`.
-* Os nomes dos segredos não devem começar com um número.
-* Nomes dos segredos não diferenciam maiúsculas de minúsculas.
-* Os nomes dos segredos devem ser únicos no nível em que são criados. Por exemplo, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}um segredo criado a nível de ambiente deve ter um nome exclusivo nesse ambiente, {% endif %}um segredo criado no nível do repositório deve ter um nome exclusivo nesse repositório, e um segredo criado no nível da organização deve ter um nome exclusivo nesse nível.
-
-  Se existir um segredo com o mesmo nome em vários níveis, o segredo no nível inferior tem prioridade. Por exemplo, se um segredo no nível de organização tiver o mesmo nome que um segredo no nível de repositório, o segredo no nível de repositório terá prioridade.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Da mesma forma, se uma organização, repositório, e ambiente tiverem um segredo com o mesmo nome, o segredo do ambiente terá prioridade.{% endif %}
+  {% data reusables.codespaces.secret-precedence %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Da mesma forma, se uma organização, repositório e o ambiente tiverem um segredo com o mesmo nome, o segredo ambiental terá prioridade.{% endif %}
 
 Para ajudar a garantir que {% data variables.product.prodname_dotcom %} remova o seu segredo dos registros, evite usar dados estruturados como valores dos segredos. Por exemplo, evite criar segredos que contêm JSON ou Git blobs.
 
@@ -83,7 +77,8 @@ Se o seu repositório {% if currentVersion == "free-pro-team@latest" or currentV
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" }
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+
 ### Criar segredos criptografados para um ambiente
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
@@ -125,7 +120,11 @@ Você pode verificar quais políticas de acesso são aplicadas a um segredo na s
 
 ### Usando segredos encriptados em um fluxo de trabalho
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
+
+**Observação:** {% data reusables.actions.forked-secrets %}
+
+{% endnote %}
 
 Para fornecer uma ação com um segredo como uma entrada ou variável de ambiente, você pode usar o contexto de `segredos` para acessar os segredos que você criou no seu repositório. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" e "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 
diff --git a/translations/pt-BR/content/actions/reference/environment-variables.md b/translations/pt-BR/content/actions/reference/environment-variables.md
index 71d49a99d5..b391ab0658 100644
--- a/translations/pt-BR/content/actions/reference/environment-variables.md
+++ b/translations/pt-BR/content/actions/reference/environment-variables.md
@@ -58,6 +58,7 @@ Você também pode usar o {% if currentVersion == "free-pro-team@latest" or curr
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
 | `GITHUB_JOB`         | O [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual.                                                                                                                                                                                                                                                                                      |
 | `GITHUB_ACTION`      | Identificador único (`id`) da ação.                                                                                                                                                                                                                                                                                                                                                  |
+| `GITHUB_ACTION_PATH` | O caminho onde está localizada a sua ação. Você pode usar esse caminho para acessar os arquivos localizados no mesmo repositório que sua ação. Esta variável só é compatível com ações de etapas de execução compostas.                                                                                                                                                              |
 | `GITHUB_ACTIONS`     | Definido sempre como `verdadeiro` quando {% data variables.product.prodname_actions %} estiver executando o fluxo de trabalho. Você pode usar esta variável para diferenciar quando os testes estão sendo executados localmente ou por {% data variables.product.prodname_actions %}.                                                                                              |
 | `GITHUB_ACTOR`       | Nome da pessoa ou aplicativo que iniciou o fluxo de trabalho. Por exemplo, `octocat`.                                                                                                                                                                                                                                                                                                |
 | `GITHUB_REPOSITORY`  | Nome do repositório e o proprietário. Por exemplo, `octocat/Hello-World`.                                                                                                                                                                                                                                                                                                            |
@@ -68,9 +69,9 @@ Você também pode usar o {% if currentVersion == "free-pro-team@latest" or curr
 | `GITHUB_REF`         | Branch ou ref tag que acionou o fluxo de trabalho. Por exemplo, `refs/heads/feature-branch-1`. Se não houver branch ou tag disponível para o tipo de evento, a variável não existirá.                                                                                                                                                                                                |
 | `GITHUB_HEAD_REF`    | Definir somente para eventos de pull request. O nome do branch principal.                                                                                                                                                                                                                                                                                                            |
 | `GITHUB_BASE_REF`    | Definir somente para eventos de pull request. O nome do branch de base.                                                                                                                                                                                                                                                                                                              |
-| `GITHUB_SERVER_URL`  | Retorna a URL do servidor {% data variables.product.product_name %}. Por exemplo: `https://github.com`.                                                                                                                                                                                                                                                                              |
-| `GITHUB_API_URL`     | Retorna a URL da API. Por exemplo: `https://api.github.com`.                                                                                                                                                                                                                                                                                                                         |
-| `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo: `https://api.github.com/graphql`.                                                                                                                                                                                                                                                                                                         |
+| `GITHUB_SERVER_URL`  | Retorna a URL do servidor {% data variables.product.product_name %}. Por exemplo: `https://{% data variables.product.product_url %}`.                                                                                                                                                                                                                                                |
+| `GITHUB_API_URL`     | Retorna a URL da API. Por exemplo: `{% data variables.product.api_url_code %}`.                                                                                                                                                                                                                                                                                                      |
+| `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo: `{% data variables.product.graphql_url_code %}`.                                                                                                                                                                                                                                                                                          |
 
 {% tip %}
 
@@ -84,10 +85,6 @@ Você também pode usar o {% if currentVersion == "free-pro-team@latest" or curr
 
 ### Convenções de nomenclatura para variáveis de ambiente
 
-{% note %}
-
-**Observação**{% data variables.product.prodname_dotcom %} reserva o prefixo da variável de ambiente `GITHUB_` para uso interno por {% data variables.product.prodname_dotcom %}. Definir uma variável de ambiente ou segredo com o prefixo `GITHUB_` resultará em erro.
-
-{% endnote %}
+Ao definir uma variável de ambiente personalizada, você não poderá usar qualquer um dos nomes de variáveis de ambiente padrão listados acima com o prefixo `GITHUB_`. Se você tentar substituir o valor de uma dessas variáveis de ambiente padrão, a atribuição será ignorada.
 
 Qualquer variável de ambiente nova que você definir e apontar para um local no sistema de arquivos deve ter um sufixo `_PATH`. As variáveis padrão `HOME` e `GITHUB_WORKSPACE` são exceções a essa convenção porque as palavras "inicial" e "espaço de trabalho" já indicam o local.
diff --git a/translations/pt-BR/content/actions/reference/environments.md b/translations/pt-BR/content/actions/reference/environments.md
index c5ffbabc03..2e312a5e80 100644
--- a/translations/pt-BR/content/actions/reference/environments.md
+++ b/translations/pt-BR/content/actions/reference/environments.md
@@ -48,6 +48,12 @@ Use os branches de implantação para restringir quais branches podem ser implem
 
 Os segredos armazenados em um ambiente só estão disponíveis para trabalhos de fluxo de trabalho que fazem referência ao ambiente. Se o ambiente exigir aprovação, um trabalho não poderá acessar segredos de ambiente até que um dos revisores necessários o aprove. Para obter mais informações sobre segredos, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)".
 
+{% note %}
+
+**Observação:** Os fluxos de trabalho executados em executores auto-hospedados não são executados em um contêiner isolado, mesmo que usem ambientes. Os segredos de ambiente devem ser tratados com o mesmo nível de segurança que os segredos do repositório e da organização. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)".
+
+{% endnote %}
+
 ### Criar um ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -71,6 +77,9 @@ Para obter mais informações sobre sintaxe para ambientes de referência em flu
 
 Quando um fluxo de trabalho faz referência a um ambiente, o ambiente aparecerá nas implantações do repositório. Para obter mais informações sobre a visualização de implementações atuais e anteriores, consulte "[Visualizar histórico de implantação](/developers/overview/viewing-deployment-history)".
 
+### Usar a concorrência para serializar implantações em um ambiente
+Você pode usar a concorrência para que um ambiente tenha, no máximo, uma implantação em andamento e uma implantação pendente por vez. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#concurrency)".
+
 ### Excluir um ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -80,7 +89,7 @@ A exclusão de um ambiente apagará todos os segredos e regras de proteção ass
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. Próximo o ambiente que você deseja excluir, clique em {% octicon "trashcan" aria-label="The trashcan icon" %}.
+1. Ao lado do ambiente que você deseja excluir, clique em {% octicon "trash" aria-label="The trash icon" %}.
 2. Clique em **Eu entendi, exclua este ambiente**.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}Você também pode excluir ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)."{% endif %}
diff --git a/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md
index 2e1ce3d93e..420789df79 100644
--- a/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/pt-BR/content/actions/reference/events-that-trigger-workflows.md
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        eco "- em ${{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          eco "- em ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ Executa o fluxo de trabalho sempre que o evento `check_run` ocorre. {% data reus
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Carga de evento webhook                            | Tipos de atividade                                                                           | `GITHUB_SHA`                   | `GITHUB_REF`  |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | Último commit no branch padrão | Branch padrão |
+| Carga de evento webhook                            | Tipos de atividade                                            | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------------- | ------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-Por exemplo, você pode executar um fluxo de trabalho quando uma execução de verificação tiver sido `rerequested` ou `requested_action`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma execução de verificação tiver sido `rerequested` ou `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ Por exemplo, você pode executar um fluxo de trabalho quando um cartão de proje
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**Observação:** O tipo</code>prereleased`não será acionado para pré-versões publicadas a partir de versões de rascunho, mas o tipo <code>published` será acionado. Se você quiser que um fluxo de trabalho seja executado quando *e* forem publicadas pré-versões, assine `published` em vez de `released` e `prereleased`.
+
+{% endnote %}
+
 #### `status`
 
 Executa o fluxo de trabalho sempre que o status de um commit do Git muda, o que aciona o evento `status`. Para obter informações sobre a API REST, consulte [Status](/rest/reference/repos#statuses).
diff --git a/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md
index fc2b2eba46..12c2c0826b 100644
--- a/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/pt-BR/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### Adicionar um caminho do sistema
diff --git a/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md
index 6a1a9b03c8..4920b29122 100644
--- a/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Workflow syntax for GitHub Actions
-shortTitle: Workflow syntax
-intro: A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration.
+title: Sintaxe de fluxo de trabalho para o GitHub Actions
+shortTitle: Sintaxe de fluxo de trabalho
+intro: Um fluxo de trabalho é um processo automatizado configurável constituído de um ou mais trabalhos. Você deve criar um arquivo YAML para definir a configuração do seu fluxo de trabalho.
 product: '{% data reusables.gated-features.actions %}'
 redirect_from:
   - /articles/workflow-syntax-for-github-actions
@@ -15,46 +15,47 @@ versions:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### About YAML syntax for workflows
+### Sobre sintaxe YAML para fluxos de trabalho
 
-Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+Arquivos de fluxo de trabalho usam sintaxe YAML e devem ter uma extensão de arquivo `.yml` ou `.yaml`. {% data reusables.actions.learn-more-about-yaml %}
 
-You must store workflow files in the `.github/workflows` directory of your repository.
+Você deve armazenar os arquivos de fluxo de trabalho no diretório `.github/workflows` do seu repositório.
 
 ### `name`
 
-The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
+Nome do fluxo de trabalho. O {% data variables.product.prodname_dotcom %} exibe os nomes dos fluxos de trabalho na página de ações do repositório. Se você omitir o `nome`, o {% data variables.product.prodname_dotcom %} irá defini-lo como o caminho do arquivo do fluxo de trabalho relativo à raiz do repositório.
 
 ### `on`
 
-**Required** The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. You can provide a single event `string`, `array` of events, `array` of event `types`, or an event configuration `map` that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see "[Events that trigger workflows](/articles/events-that-trigger-workflows)."
+**Obrigatório**. O nome do evento de {% data variables.product.prodname_dotcom %} que aciona o fluxo de trabalho. Você pode fornecer uma única `string` de evento, um `array` de eventos, um `array` de `types` (tipos) de eventos ou um `map` (mapa) de configuração de eventos que programe um fluxo de trabalho ou restrinja a execução do fluxo de trabalho a alterações em determinados arquivos, tags ou branches. Para obter uma lista de eventos disponíveis, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows)".
 
 {% data reusables.github-actions.actions-on-examples %}
 
 ### `on.<event_name>.types`
 
-Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity.  For example, the event for the release resource is triggered when a release is `published`, `unpublished`, `created`, `edited`, `deleted`, or `prereleased`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary.
+Seleciona os tipos de atividades que acionarão a execução de um fluxo de trabalho. A maioria dos eventos GitHub são acionados por mais de um tipo de atividade.  Por exemplo, o evento para o recurso release (versão) é acionado quando uma versão é `published` (publicada), `unpublished` (a publicação é cancelada), `created` (criada), `edited` (editada), `deleted` (excluída) ou `prereleased` (versão prévia). A palavra-chave `types` (tipos) permite que você limite a atividade que faz com que o fluxo de trabalho seja executado. Quando somente um tipo de atividade aciona um evento de webhook, a palavra-chave `types` (tipos) é desnecessária.
 
-You can use an array of event `types`. For more information about each event and their activity types, see "[Events that trigger workflows](/articles/events-that-trigger-workflows#webhook-events)."
+É possível usar um array de `types` (tipos) de evento. Para obter mais informações sobre cada evento e seus tipos de atividades, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows#webhook-events)".
 
 ```yaml
-# Trigger the workflow on pull request activity
+# Aciona o fluxo de trabalho na atividade de pull request
 on:
   release:
-    # Only use the types keyword to narrow down the activity types that will trigger your workflow.
+    # Usa apenas a palavra-chave types (tipos) para limitar os tipos de atividades que acionam o fluxo de trabalho.
     types: [published, created, edited]
 ```
 
 ### `on.<push|pull_request>.<branches|tags>`
 
-When using the `push` and `pull_request` events, you can configure a workflow to run on specific branches or tags. For a `pull_request` event, only branches and tags on the base are evaluated. If you define only `tags` or only `branches`, the workflow won't run for events affecting the undefined Git ref.
+Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado em branches ou tags específicos. Para um evento de `pull_request`, são avaliados apenas os branches e tags na base. Se você definir apenas `tags` ou `branches`, o fluxo de trabalho não será executado para eventos que afetam o Git ref indefinido.
 
-The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one branch or tag name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+As palavras-chave `branches`, `branches-ignore`, `tags` e `tags-ignore` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de branch ou tag. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)".
 
-#### Example including branches and tags
+#### Exemplo com branches e tags
 
-The patterns defined in `branches` and `tags` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**` will match the `refs/heads/releases/10` Git ref.
+Os padrões definidos nos `branches` e `tags` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**` corresponderá ao Git ref `refs/heads/releases/10`.
 
 ```yaml
 on:
@@ -73,145 +74,171 @@ on:
       - v1.*           # Push events to v1.0, v1.1, and v1.9 tags
 ```
 
-#### Example ignoring branches and tags
+#### Exemplo desconsiderando branches e tags
 
-Anytime a pattern matches the `branches-ignore` or `tags-ignore` pattern, the workflow will not run. The patterns defined in `branches-ignore` and `tags-ignore` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**-alpha` in `branches` will match the `refs/releases/beta/3-alpha` Git ref.
+Sempre que um padrão corresponde ao padrão `branches-ignore` ou `tags-ignore`, o fluxo de trabalho não será executado. Os padrões definidos em `branches-ignore` e `tags-ignore` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**-alpha` em `branches` corresponderá ao Git ref `refs/releases/beta/3-alpha`.
 
 ```yaml
-on:
+em:
   push:
-    # Sequence of patterns matched against refs/heads
+    # Sequência de padrões que correspondem a refs/heads
     branches-ignore:
-      # Push events to branches matching refs/heads/mona/octocat
+      # Push de eventos para branches que correspondem a refs/heads/mona/octocat
       - 'mona/octocat'
-      # Push events to branches matching refs/heads/releases/beta/3-alpha
+      # Push de eventos para branches que correspondem a refs/heads/releases/beta/3-alpha
       - 'releases/**-alpha'
-    # Sequence of patterns matched against refs/tags
+    # Sequência de padrões que correspondem a refs/tags
     tags-ignore:
       - v1.*           # Push events to tags v1.0, v1.1, and v1.9
 ```
 
-#### Excluding branches and tags
+#### Excluir branches e tags
 
-You can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches.
-- `branches` or `branches-ignore` - You cannot use both the `branches` and `branches-ignore` filters for the same event in a workflow. Use the `branches` filter when you need to filter branches for positive matches and exclude branches. Use the `branches-ignore` filter when you only need to exclude branch names.
-- `tags` or `tags-ignore` - You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow. Use the `tags` filter when you need to filter tags for positive matches and exclude tags. Use the `tags-ignore` filter when you only need to exclude tag names.
+Você pode usar dois tipos de filtros para impedir a execução de um fluxo de trabalho em pushes e pull requests para tags e branches.
+- `branches` ou `branches-ignore` - não é possível usar os dois filtros `branches` e `branches-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `branches` quando você precisa filtrar branches para correspondências positivas e excluir branches. Use o filtro `branches-ignore` quando você só precisa excluir nomes de branches.
+- `tags` ou `tags-ignore` - não é possível usar os dois filtros `tags` e `tags-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `tags` quando você precisa filtrar tags para correspondências positivas e excluir tags. Use o filtro `tags-ignore` quando você só precisa excluir nomes de tags.
 
-#### Example using positive and negative patterns
+#### Exemplo com padrões positivos e negativos
 
-You can exclude `tags` and `branches` using the `!` character. The order that you define patterns matters.
-  - A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref.
-  - A matching positive pattern after a negative match will include the Git ref again.
+Você pode excluir `tags` e `branches` usando o caractere `!`. A ordem de definição dos padrões é importante.
+  - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o Git ref.
+  - Um padrão positivo correspondente após uma correspondência negativa incluirá a Git ref novamente.
 
-The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern.
+O fluxo de trabalho a seguir será executado em pushes para `releases/10` ou `releases/beta/mona`, mas não em `releases/10-alpha` ou `releases/beta/3-alpha`, pois o padrão negativo `!releases/**-alpha` está na sequência do padrão positivo.
 
 ```yaml
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
 
-When using the `push` and `pull_request` events, you can configure a workflow to run when at least one file does not match `paths-ignore` or at least one modified file matches the configured `paths`. Path filters are not evaluated for pushes to tags.
+Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado quando pelo menos um arquivo não corresponde a `paths-ignore` ou pelo menos um arquivo modificado corresponde ao `paths` configurado. Flitros de caminho não são avaliados em pushes para tags.
 
-The `paths-ignore` and `paths` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+As palavras-chave `paths-ignore` e `paths` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de caminho. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)".
 
-#### Example ignoring paths
+#### Exemplo desconsiderando caminhos
 
-Anytime a path name matches a pattern in `paths-ignore`, the workflow will not run. {% data variables.product.prodname_dotcom %} evaluates patterns defined in `paths-ignore` against the path name. A workflow with the following path filter will only run on `push` events that include at least one file outside the `docs` directory at the root of the repository.
+Quando todos os caminhos de nome correspondem a padrões em `paths-ignore`, o fluxo de trabalho não será executado. O {% data variables.product.prodname_dotcom %} avalia os padrões definidos em `paths-ignore` com relação ao nome do caminho. Um fluxo de trabalho com o seguinte filtro de caminho só será executado em eventos `push` que tiverem pelo menos um arquivo fora do diretório `docs` na raiz do repositório.
 
 ```yaml
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
-#### Example including paths
+#### Exemplo incluindo caminhos
 
-If at least one path matches a pattern in the `paths` filter, the workflow runs. To trigger a build anytime you push a JavaScript file, you can use a wildcard pattern.
+Se pelo menos um caminho corresponder a um padrão no filtro `paths`, o fluxo de trabalho será executado. Para acionar uma compilação sempre que você fizer push de um arquivo JavaScript, você pode usar um padrão curinga.
 
 ```yaml
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
-#### Excluding paths
+#### Excluir caminhos
 
-You can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow.
-- `paths-ignore` - Use the `paths-ignore` filter when you only need to exclude path names.
-- `paths` - Use the `paths` filter when you need to filter paths for positive matches and exclude paths.
+Você pode excluir caminhos com dois tipos de filtros. Não é possível usar ambos os filtros para o mesmo evento em um fluxo de trabalho.
+- `paths-ignore` - use o filtro `paths-ignore` quando você precisa somente excluir nomes de caminhos.
+- `paths` - use o filtro `paths` quando você precisa filtrar caminhos para correspondências positivas e excluir caminhos.
 
-#### Example using positive and negative patterns
+#### Exemplo com padrões positivos e negativos
 
-You can exclude `paths` using the `!` character. The order that you define patterns matters:
-  - A matching negative pattern (prefixed with `!`) after a positive match will exclude the path.
-  - A matching positive pattern after a negative match will include the path again.
+Você pode excluir `paths` usando o caractere `!`. A ordem de definição dos padrões é importante:
+  - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o caminho.
+  - Um padrão positivo correspondente após uma correspondência negativa incluirá o caminho novamente.
 
-This example runs anytime the `push` event includes a file in the `sub-project` directory or its subdirectories, unless the file is in the `sub-project/docs` directory. For example, a push that changed `sub-project/index.js` or `sub-project/src/index.js` will trigger a workflow run, but a push changing only `sub-project/docs/readme.md` will not.
+Este exemplo é executado sempre que o evento `push` inclui um arquivo no diretório `sub-project` ou seus subdiretórios, a menos que o arquivo esteja no diretório `sub-project/docs`. Por exemplo, um push que alterou `sub-project/index.js` ou `sub-project/src/index.js` acionará uma execução de fluxo de trabalho, mas um push que altere somente`sub-project/docs/readme.md` não acionará.
 
 ```yaml
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
-#### Git diff comparisons
+#### Comparações Git diff
 
 {% note %}
 
-**Note:** If you push more than 1,000 commits, or if {% data variables.product.prodname_dotcom %} does not generate the diff due to a timeout (diffs that are too large diffs), the workflow will always run.
+**Observação:** se você fizer push de mais de 1.000 commits ou se o {% data variables.product.prodname_dotcom %} não gera o diff devido a um tempo limite esgotado (diffs muito grandes), o fluxo de trabalho sempre será executado.
 
 {% endnote %}
 
-The filter determines if a workflow should run by evaluating the changed files and running them against the `paths-ignore` or `paths` list. If there are no files changed, the workflow will not run.
+O filtro determina se um fluxo de trabalho deve ser executado avaliando os arquivos alterados e comparando-os à lista de `paths-ignore` ou `paths`. Se não houver arquivos alterados, o fluxo de trabalho não será executado.
 
-{% data variables.product.prodname_dotcom %} generates the list of changed files using two-dot diffs for pushes and three-dot diffs for pull requests:
-- **Pull requests:** Three-dot diffs are a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch.
-- **Pushes to existing branches:** A two-dot diff compares the head and base SHAs directly with each other.
-- **Pushes to new branches:** A two-dot diff against the parent of the ancestor of the deepest commit pushed.
+O {% data variables.product.prodname_dotcom %} gera a lista de arquivos alterados usando diffs de dois pontos para pushes e diffs de três pontos para pull requests:
+- **Pull requests:** diffs de três pontos são uma comparação entre a versão mais recente do branch de tópico e o commit onde o branch de tópico foi sincronizado pela última vez com o branch de base.
+- **Pushes para branches existentes:** um diff de dois pontos compara os SHAs head e base, um com o outro.
+- **Pushes para novos branches:** um diff de dois pontos compara o principal do ancestral do commit mais extenso que foi feito push.
 
-For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)."
+Para obter mais informações, consulte "[Sobre comparação de branches em pull requests](/articles/about-comparing-branches-in-pull-requests)".
 
 ### `on.schedule`
 
 {% data reusables.repositories.actions-scheduled-workflow-example %}
 
-For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)."
+Para obter mais informações sobre a sintaxe cron, consulte "[Eventos que acionam fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)".
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `permissões`
+
+Você pode modificar as permissões padrão concedidas ao `GITHUB_TOKEN`, adicionando ou removendo o acesso conforme necessário, para que você permita apenas o acesso mínimo necessário. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
+
+Você pode usar as permissões de `` como uma chave de nível superior, para aplicar a todos os trabalhos do fluxo de trabalho ou em trabalhos específicos. Ao adicionar a chave das `permissões` em um trabalho específico, todas as ações e comandos de execução dentro desse trabalho que usam o `GITHUB_TOKEN` ganham os direitos de acesso que você especificar.  Para obter mais informações, consulte [`jobs.<job_id>.permissions`](#jobsjob_idpermissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Exemplo
+
+Este exemplo mostra as permissões que estão sendo definidas para o `GITHUB_TOKEN` que será aplicado a todos os trabalhos do fluxo de trabalho. É concedido acesso de leitura a todas as permissões.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
 
 ### `env`
 
-A `map` of environment variables that are available to all jobs and steps in the workflow. You can also set environment variables that are only available to a job or step. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
+Um `mapa` das variáveis de ambiente que estão disponíveis para as etapas de todos os trabalhos do fluxo de trabalho. Também é possível definir variáveis de ambiente que estão disponíveis apenas para as etapas de um único trabalho ou para uma única etapa. Para obter mais informações, consulte [`jobs.<job_id>.env`](#jobsjob_idenv) e [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
 
 {% data reusables.repositories.actions-env-var-note %}
 
-#### Example
+#### Exemplo
 
 ```yaml
 env:
   SERVER: production
 ```
 
-### `defaults`
+### `padrões`
 
-A `map` of default settings that will apply to all jobs in the workflow. You can also set default settings that are only available to a job. For more information, see [`jobs.<job_id>.defaults`](#jobsjob_iddefaults).
+Um `mapa` das configurações-padrão que serão aplicadas a todos os trabalhos do fluxo de trabalho. Você também pode definir as configurações-padrão disponíveis para um trabalho. Para obter mais informações, consulte [`jobs.<job_id>.defaults`](#jobsjob_iddefaults).
 
 {% data reusables.github-actions.defaults-override %}
 
 ### `defaults.run`
 
-You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a workflow. You can also set default settings for `run` that are only available to a job. For more information, see [`jobs.<job_id>.defaults.run`](#jobsjob_iddefaultsrun). You cannot use contexts or expressions in this keyword.
+Você pode fornecer opções-padrão de `shell` e `working-directory` para todas as etapas de [`executar`](#jobsjob_idstepsrun) em um fluxo de trabalho. Você também pode definir as configurações-padrão para `execução` apenas disponíveis para um trabalho. Para obter mais informações, consulte [`jobs.<job_id>.defaults.run`](#jobsjob_iddefaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave.
 
 {% data reusables.github-actions.defaults-override %}
 
-#### Example
+#### Exemplo
 
 ```yaml
 defaults:
@@ -220,39 +247,51 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concorrência`
+
+{% data reusables.actions.concurrency-beta %}
+
+A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão só pode usar o contexto `github`. Para obter mais informações sobre expressões, consulte "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
+
+Você também pode especificar `concorrência` no nível do trabalho. Para obter mais informações, consulte [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs`
 
-A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs.<job_id>.needs` keyword.
+A execução de um fluxo de trabalho consiste em um ou mais trabalhos. Por padrão, os trabalhos são executados paralelamente. Para executar trabalhos sequencialmente, você pode definir dependências em outros trabalhos usando a palavra-chave `jobs.<job_id>.needs`.
 
-Each job runs in a runner environment specified by `runs-on`.
+Cada trabalho é executado em um ambiente de executor especificado por `runs-on`.
 
-You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
+Você pode executar quantos trabalhos desejar, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados.
 
-If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)."
+Se você precisar encontrar o identificador exclusivo de um trabalho e execução em um fluxo de trabalho, você poderá usar a API {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Trabalhos do fluxo de trabalho](/rest/reference/actions#workflow-jobs)".
 
 ### `jobs.<job_id>`
 
-Each job must have an id to associate with the job. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `<job_id>` with a string that is unique to the `jobs` object. The `<job_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+Cada trabalho deve ter um id associado. A chave `job_id` é uma string, e seu valor é um mapa dos dados de configuração do trabalho. Você deve substituir `<job_id>` por uma string exclusiva para o objeto `jobs`. `<job_id>` deve começar por uma letra ou `_`, além de conter somente caracteres alfanuméricos, `-` ou `_`.
 
-#### Example
+#### Exemplo
 
 ```yaml
 jobs:
-  my_first_job:
-    name: My first job
-  my_second_job:
-    name: My second job
+  meu_primeiro_trabalho:
+    name: meu primeiro trabalho
+  meu_segundo_trabalho:
+    name: meu segundo trabalho
 ```
 
 ### `jobs.<job_id>.name`
 
-The name of the job displayed on {% data variables.product.prodname_dotcom %}.
+Nome do trabalho no {% data variables.product.prodname_dotcom %}.
 
 ### `jobs.<job_id>.needs`
 
-Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue.
+Identifica todos os trabalhos a serem concluídos com êxito antes da execução deste trabalho. Esse código pode ser uma string ou array de strings. Se houver falha em um trabalho, todos os trabalhos que dependem dele serão ignorados, a menos que os trabalhos usem uma expressão condicional que faça o trabalho continuar.
 
-#### Example requiring dependent jobs to be successful
+#### Exemplo que exige que trabalhos dependentes sejam bem sucedidos
 
 ```yaml
 jobs:
@@ -263,15 +302,15 @@ jobs:
     needs: [job1, job2]
 ```
 
-In this example, `job1` must complete successfully before `job2` begins, and `job3` waits for both `job1` and `job2` to complete.
+Neste exemplo, `job1` deve ser concluído com êxito antes do início de `job2`, e `job3` aguarda a conclusão de `job1` e `job2`.
 
-The jobs in this example run sequentially:
+Os trabalhos neste exemplo são executados sequencialmente:
 
 1. `job1`
 2. `job2`
 3. `job3`
 
-#### Example not requiring dependent jobs to be successful
+#### Exemplo que não exige que trabalhos dependentes sejam bem sucedidos
 
 ```yaml
 jobs:
@@ -283,58 +322,104 @@ jobs:
     needs: [job1, job2]
 ```
 
-In this example, `job3` uses the `always()` conditional expression so that it always runs after `job1` and `job2` have completed, regardless of whether they were successful. For more information, see "[Context and expression syntax](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)."
+Neste exemplo, `job3` usa a expressão condicional `always()` para que ela sempre seja executada depois de `job1` e `job2` terem sido concluídos, independentemente de terem sido bem sucedidos. Para obter mais informações, consulte "[sintaxe de contexto e expressão](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)".
 
 ### `jobs.<job_id>.runs-on`
 
-**Required** The type of machine to run the job on. The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.
+**Obrigatório**. O tipo de máquina na qual se executa o trabalho. A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado.
 
+{% if currentVersion == "github-ae@latest" %}
+#### {% data variables.actions.hosted_runner %}s
+
+Se você usar um {% data variables.actions.hosted_runner %}, cada trabalho será executado em uma instância atualizada de um ambiente virtual especificado por `runs-on`.
+
+##### Exemplo
+
+```yaml
+runs-on: [AE-runner-for-CI]
+```
+
+Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)".
+
+{% else %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-#### {% data variables.product.prodname_dotcom %}-hosted runners
+#### Runners hospedados no {% data variables.product.prodname_dotcom %}
 
-If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a virtual environment specified by `runs-on`.
+Se você usar um executor hospedado no {% data variables.product.prodname_dotcom %}, cada trabalho será executado em uma nova instância de um ambiente virtual especificado por `runs-on`.
 
-Available {% data variables.product.prodname_dotcom %}-hosted runner types are:
+Os tipos de executor disponíveis para {% data variables.product.prodname_dotcom %} são:
 
 {% data reusables.github-actions.supported-github-runners %}
 
-{% data reusables.github-actions.ubuntu-runner-preview %}
+{% data reusables.github-actions.macos-runner-preview %}
 
-##### Example
+##### Exemplo
 
 ```yaml
 runs-on: ubuntu-latest
 ```
 
-For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)."
+Para obter mais informações, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)".
+{% endif %}
 
-#### Self-hosted runners
+#### Executores auto-hospedados
+
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 
 {% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
 
-##### Example
+##### Exemplo
 
 ```yaml
 runs-on: [self-hosted, linux]
 ```
 
-For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
+Para obter mais informações, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" e "[Usar executores auto-hospedados em um fluxo de trabalho](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-### `jobs.<job_id>.environment`
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
 
-The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)."
+Você pode modificar as permissões padrão concedidas ao `GITHUB_TOKEN`, adicionando ou removendo o acesso conforme necessário, para que você permita apenas o acesso mínimo necessário. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
 
-You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
+Ao especificar a permissão de uma definição de trabalho, você pode configurar um conjunto diferente de permissões para o `GITHUB_TOKEN` para cada trabalho, se necessário. Como alternativa, você pode especificar as permissões para todas as tarefas do fluxo de trabalho. Para informações sobre como definir permissões no nível do fluxo de trabalho, consulte [`permissões`](#permissions).
 
-##### Example using a single environment name
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Exemplo
+
+Este exemplo mostra as permissões que estão sendo definidas para o `GITHUB_TOKEN` que só se aplicará ao trabalho denominado `stale`. O acesso de gravação é concedido para os escopos dos `problemas` e `pull-requests`. Todos os outros escopos não terão acesso.
 
 ```yaml
-environment: staging_environment
-```
+jobs:
+  stale:
+    runs-on: ubuntu-latest
 
-##### Example using environment name and URL
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+### `jobs.<job_id>.environment`
+
+O ambiente ao qual o trabalho faz referência. Todas as regras de proteção do ambiente têm de ser aprovadas para que um trabalho que faça referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)".
+
+Você pode fornecer o ambiente apenas como o `nome` do ambiente, ou como um objeto de ambiente com o `nome` e `url`. A URL é mapeada com `environment_url` na API de implantações. Para obter mais informações sobre a API de implantações, consulte "[Implantações](/rest/reference/repos#deployments)".
+
+##### Exemplo de uso de um único nome de ambiente
+{% raw %}
+```yaml
+ambiente: staging_environment
+```
+{% endraw %}
+
+##### Exemplo de uso de nome de ambiente e URL
 
 ```yaml
 environment:
@@ -342,9 +427,9 @@ environment:
   url: https://github.com
 ```
 
-The URL can be an expression and can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+A URL pode ser uma expressão e pode usar qualquer contexto, exceto o contexto de `segredos`. Para obter mais informações sobre expressões, consulte "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
-#### Example
+#### Exemplo
 {% raw %}
 ```yaml
 environment:
@@ -354,15 +439,34 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**Observação:** Quando a concorrência é especificada no nível do trabalho, não se garante a ordem para trabalhos ou execuções que são enfileiradas em 5 minutos uma da outra.
+
+{% endnote %}
+
+A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão pode usar qualquer contexto, exceto para o contexto de `segredos`. Para obter mais informações sobre expressões, consulte "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
+
+Você também pode especificar `concorrência` no nível do fluxo de trabalho. Para obter mais informações, consulte [`concorrência`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
-A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs.<job_id>.needs`](#jobsjob_idneeds).
+Um `mapa` de saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs.<job_id>.needs`](#jobsjob_idneeds).
 
-Job outputs are strings, and job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}.
+As saídas de trabalho são strings e saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}.
 
-To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)."
+Para usar as saídas de trabalho em um trabalho dependente, você poderá usar o contexto `needs`. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)".
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
@@ -374,25 +478,25 @@ jobs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
 ### `jobs.<job_id>.env`
 
-A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
+Um `map` (mapa) das variáveis de ambiente que estão disponíveis para todos as etapas do trabalho. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou uma etapa individual. Para obter mais informações, consulte [`env`](#env) e [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
 
 {% data reusables.repositories.actions-env-var-note %}
 
-#### Example
+#### Exemplo
 
 ```yaml
 jobs:
@@ -403,19 +507,19 @@ jobs:
 
 ### `jobs.<job_id>.defaults`
 
-A `map` of default settings that will apply to all steps in the job. You can also set default settings for the entire workflow. For more information, see [`defaults`](#defaults).
+Um `mapa` com as configurações- padrão que serão aplicadas a todas as etapas do trabalho. Você também pode definir as configurações-padrão para todo o fluxo de trabalho. Para obter mais informações, consulte [`padrão`](#defaults).
 
 {% data reusables.github-actions.defaults-override %}
 
 ### `jobs.<job_id>.defaults.run`
 
-Provide default `shell` and `working-directory` to all `run` steps in the job. Context and expression are not allowed in this section.
+Forneça o `shell` e `working-directory` para todas as etapas do trabalho `executar`. Não são permitidos contexto e expressão nesta seção.
 
-You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`jobs.defaults.run`](#defaultsrun). You cannot use contexts or expressions in this keyword.
+Você pode fornecer as opções-padrão de `shell` e `working-directory` para todas as etapas de [`execução`](#jobsjob_idstepsrun) de um trabalho. Você também pode definir as configurações-padrão para `execução` para todo o fluxo de trabalho. Para obter mais informações, consulte [`jobs.defaults.run`](#defaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave.
 
 {% data reusables.github-actions.defaults-override %}
 
-#### Example
+#### Exemplo
 
 ```yaml
 jobs:
@@ -429,17 +533,17 @@ jobs:
 
 ### `jobs.<job_id>.if`
 
-You can use the `if` conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional.
+Você pode usar a condicional `if` (se) para evitar que um trabalho seja executado a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional.
 
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
 ### `jobs.<job_id>.steps`
 
-A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job.
+Trabalhos contêm sequências de tarefas chamadas `steps`. As etapas podem executar comandos, executar trabalhos de configuração ou executar ações no seu repositório, em repositórios públicos, ou ações publicadas em registros do Docker. Nem todas as etapas executam ações, mas todas as ações são executadas como etapas. Cada etapa é executada em seu próprio processo no ambiente do executor, tendo acesso ao espaço de trabalho e ao sistema de arquivos. Como as etapas são executadas em seus próprios processos, as alterações nas variáveis de ambiente não são preservadas entre as etapas. O {% data variables.product.prodname_dotcom %} fornece etapas integradas para configurar e concluir trabalhos.
 
-You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
+Você pode executar quantas etapas quiser, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados.
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
@@ -452,30 +556,30 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
 ### `jobs.<job_id>.steps[*].id`
 
-A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à etapa em contextos. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
 ### `jobs.<job_id>.steps[*].if`
 
-You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+Você pode usar a condicional `if` (se) para evitar que uma etapa trabalho seja executada a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional.
 
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
-#### Example using contexts
+#### Exemplo usando contextos
 
- This step only runs when the event type is a `pull_request` and the event action is `unassigned`.
+ Essa etapa somente é executada quando o tipo de evento é uma `pull_request` e a ação do evento é `unassigned` (não atribuída).
 
  ```yaml
 steps:
@@ -484,9 +588,9 @@ steps:
     run: echo This event is a pull request that had an assignee removed.
 ```
 
-#### Example using status check functions
+#### Exemplo usando funções de verificação de status
 
-The `my backup step` only runs when the previous step of a job fails. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)."
+A função `my backup step` (minha etapa de backup) somente é executada quando houver falha em uma etapa anterior do trabalho. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)".
 
 ```yaml
 steps:
@@ -499,27 +603,27 @@ steps:
 
 ### `jobs.<job_id>.steps[*].name`
 
-A name for your step to display on {% data variables.product.prodname_dotcom %}.
+Nome da etapa no {% data variables.product.prodname_dotcom %}.
 
 ### `jobs.<job_id>.steps[*].uses`
 
-Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/).
+Seleciona uma ação para executar como parte de uma etapa no trabalho. A ação é uma unidade reutilizável de código. Você pode usar uma ação definida no mesmo repositório que o fluxo de trabalho, um repositório público ou em uma [imagem publicada de contêiner Docker](https://hub.docker.com/).
 
-We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.
-- Using the commit SHA of a released action version is the safest for stability and security.
-- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.
-- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.
+É altamente recomendável incluir a versão da ação que você está usando ao especificar um número de tag Docker, SHA ou ref do Git. Se você não especificar uma versão, ela poderá interromper seus fluxos de trabalho ou causar um comportamento inesperado quando o proprietário da ação publicar uma atualização.
+- Usar o commit SHA de uma versão de ação lançada é a maneira mais garantida de obter estabilidade e segurança.
+- Usar a versão principal da ação permite receber correções importantes e patches de segurança sem perder a compatibilidade. Fazer isso também garante o funcionamento contínuo do fluxo de trabalho.
+- Usar o branch-padrão de uma ação pode ser conveniente, mas se alguém lançar uma nova versão principal com uma mudança significativa, seu fluxo de trabalho poderá ter problemas.
 
-Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required.
+Algumas ações requerem entradas que devem ser definidas com a palavra-chave [`with`](#jobsjob_idstepswith) (com). Revise o arquivo README da ação para determinar as entradas obrigatórias.
 
-Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on).
+Ações são arquivos JavaScript ou contêineres Docker. Se a ação em uso for um contêiner do Docker, você deverá executar o trabalho em um ambiente do Linux. Para obter mais detalhes, consulte [`runs-on`](#jobsjob_idruns-on).
 
-#### Example using versioned actions
+#### Exemplo usando ações com versão
 
 ```yaml
 steps:    
   # Reference a specific commit
-  - uses: actions/setup-node@74bc508
+  - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e
   # Reference the major version of a release
   - uses: actions/setup-node@v1
   # Reference a minor version of a release
@@ -528,11 +632,11 @@ steps:
   - uses: actions/setup-node@main
 ```
 
-#### Example using a public action
+#### Exemplo usando uma ação pública
 
 `{owner}/{repo}@{ref}`
 
-You can specific branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository.
+Você pode especificar um branch, ref ou SHA em um repositório público {% data variables.product.prodname_dotcom %}.
 
 ```yaml
 jobs:
@@ -546,11 +650,11 @@ jobs:
         uses: actions/aws@v2.0.1
 ```
 
-#### Example using a public action in a subdirectory
+#### Exemplo usando uma ação pública em um subdiretório
 
 `{owner}/{repo}/{path}@{ref}`
 
-A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA.
+Subdiretório em um repositório público do {% data variables.product.prodname_dotcom %} em um branch, ref ou SHA específico.
 
 ```yaml
 jobs:
@@ -560,11 +664,11 @@ jobs:
         uses: actions/aws/ec2@main
 ```
 
-#### Example using action in the same repository as the workflow
+#### Exemplo usando a ação no mesmo repositório que o fluxo de trabalho
 
 `./path/to/dir`
 
-The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action.
+Caminho para o diretório que contém a ação no repositório do seu fluxo de trabalho. Você deve reservar seu repositório antes de usar a ação.
 
 ```yaml
 jobs:
@@ -576,50 +680,88 @@ jobs:
         uses: ./.github/actions/my-action
 ```
 
-#### Example using a Docker Hub action
+#### Exemplo usando uma ação do Docker Hub
 
 `docker://{image}:{tag}`
 
-A Docker image published on [Docker Hub](https://hub.docker.com/).
+Imagem Docker publicada no [Docker Hub](https://hub.docker.com/).
 
 ```yaml
-jobs:
+empregos:
   my_first_job:
-    steps:
-      - name: My first step
-        uses: docker://alpine:3.8
+    passos:
+      - nome: Meu primeiro passo
+        usa: docker://alpine:3.8
 ```
 
-#### Example using a Docker public registry action
+{% if currentVersion == "free-pro-team@latest" %}
+##### Exemplo que utiliza {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in a public registry.
+Uma imagem Docker em {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
 
+```yaml
+jobs:
+  meu_primeiro_trabalho:
+    steps:
+      - name: minha primeira etapa
+        uses: docker://ghcr.io/OWNER/IMAGE_NAME
+```
+{% endif %}
+##### Exemplo usando uma ação do registro público do Docker Hub
+
+`docker://{host}/{image}:{tag}`
+
+Imagem Docker em um registro público. Este exemplo usa o Registro de Contêiner do Google em `gcr.io`.
+
+```yaml
+jobs:
+  meu_primeiro_trabalho:
+    steps:
+      - name: minha primeira etapa
+        uses: docker://gcr.io/cloud-builders/gradle
+```
+
+#### Exemplo de uso de ação dentro de um repositório privado diferente do fluxo de trabalho
+
+Seu fluxo de trabalho deve fazer checkout no repositório privado e referenciar a ação localmente. Generate a personal access token and add the token as an encrypted secret. Para obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)".
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
+
+{% raw %}
 ```yaml
 jobs:
   my_first_job:
     steps:
-      - name: My first step
-        uses: docker://gcr.io/cloud-builders/gradle
+      - name: Check out repository
+        uses: actions/checkout@v2
+        with:
+          repository: octocat/my-private-repo
+          ref: v1.0
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
+          path: ./.github/actions/my-private-repo
+      - name: Run my action
+        uses: ./.github/actions/my-private-repo/my-action
 ```
+{% endraw %}
 
 ### `jobs.<job_id>.steps[*].run`
 
-Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command.
+Executa programas de linha de comando usando o shell do sistema operacional. Se você não informar um `name`, o nome da etapa será configurado por padrão como o texto indicado no comando `run`.
 
-Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see "[Using a specific shell](#using-a-specific-shell)."
+Por padrão, os comandos run usam shells de não login. Você pode escolher um shell diferente e personalizar o shell usado para executar comandos. Para obter mais informações, consulte "[Usar um shell específico](#using-a-specific-shell)".
 
-Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example:
+Cada palavra-chave `run` representa um novo processo e shell no ambiente do executor. Quando você fornece comandos de várias linhas, cada linha será executada no mesmo shell. Por exemplo:
 
-* A single-line command:
+* Um comando de linha única:
 
   ```yaml
   - name: Install Dependencies
     run: npm install
   ```
 
-* A multi-line command:
+* Um comando de várias linhas:
 
   ```yaml
   - name: Clean install dependencies and build
@@ -628,7 +770,7 @@ Each `run` keyword represents a new process and shell in the runner environment.
       npm run build
   ```
 
-Using the `working-directory` keyword, you can specify the working directory of where to run the command.
+Com a palavra-chave `working-directory` (diretório de trabalho), é possível especificar o diretório de trabalho de onde o comando será executado.
 
 ```yaml
 - name: Clean temp directory
@@ -636,20 +778,21 @@ Using the `working-directory` keyword, you can specify the working directory of
   working-directory: ./temp
 ```
 
-#### Using a specific shell
+#### Usar um shell específico
 
-You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options.
+Você pode anular as configurações padrão de shell no sistema operacional do executor usando a palavra-chave `shell`. É possível usar palavras-chave integradas a `shell` ou definir um conjunto personalizado de opções de shell.
 
-| Supported platform | `shell` parameter | Description | Command run internally |
-|--------------------|-------------------|-------------|------------------------|
-| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` |
-| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` |
-| All | `python` | Executes the python command. | `python {0}` |
-| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` |
-| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. |
-| Windows | `powershell` | This is the default shell used on Windows. The Desktop PowerShell. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. |
+| Plataforma compatível | Parâmetro `shell` | Descrição                                                                                                                                                                                                                                                                  | Comando executado internamente                  |
+| --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
+| Todas                 | `bash`            | O shell padrão em plataformas que não sejam Windows como uma alternativa para `sh`. Ao especificar um shell bash no Windows, é utilizado o shell bash incluído no Git para Windows.                                                                                        | `bash --noprofile --norc -eo pipefail {0}`      |
+| Todas                 | `pwsh`            | Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script.                                                                                                                                                                 | `pwsh -command ". '{0}'"`                       |
+| Todas                 | `python`          | Executa o comando python.                                                                                                                                                                                                                                                  | `python {0}`                                    |
+| Linux / macOS         | `sh`              | Comportamento alternativo para plataformas que não sejam Windows se nenhum shell for fornecido e o `bash` não for encontrado no caminho.                                                                                                                                   | `sh -e {0}`                                     |
+| Windows               | `cmd`             | O {% data variables.product.prodname_dotcom %} anexa a extensão `.cmd` ao nome do script e a substitui por `{0}`.                                                                                                                                                          | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. |
+| Windows               | `pwsh`            | Essa é a shell padrão usada no Windows. Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. Se o seu executor do Windows auto-hospedado não tiver o _PowerShell Core_ instalado, será usado o _PowerShell Desktop_. | `pwsh -command ". '{0}'"`.                      |
+| Windows               | `powershell`      | O PowerShell Desktop. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script.                                                                                                                                                            | `powershell -command ". '{0}'"`.                |
 
-#### Example running a script using bash
+#### Exemplo de execução de um script usando bash:
 
 ```yaml
 steps:
@@ -658,7 +801,7 @@ steps:
     shell: bash
 ```
 
-#### Example running a script using Windows `cmd`
+#### Exemplo de execução de um script usando Windows `cmd`
 
 ```yaml
 steps:
@@ -667,7 +810,7 @@ steps:
     shell: cmd
 ```
 
-#### Example running a script using PowerShell Core
+#### Exemplo de execução de um script usando PowerShell Core
 
 ```yaml
 steps:
@@ -676,7 +819,16 @@ steps:
     shell: pwsh
 ```
 
-#### Example running a python script
+#### Exemplo: Usar o PowerShell Desktop para executar um script
+
+```yaml
+steps:
+  - name: Display the path
+    run: echo ${env:PATH}
+    shell: powershell
+```
+
+#### Exemplo de execução de um script python
 
 ```yaml
 steps:
@@ -687,35 +839,53 @@ steps:
     shell: python
 ```
 
-#### Custom shell
+#### Shell personalizado
 
-You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`.
+Você pode usar o valor `shell` em um string modelo usando `command […options] {0} [..more_options]`. O {% data variables.product.prodname_dotcom %} interpreta a primeira palavra da string delimitada por um espaço em branco como o comando e insere o nome do arquivo para o script temporário em `{0}`.
 
-#### Exit codes and error action preference
+Por exemplo:
 
-For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
+```yaml
+steps:
+  - name: Display the environment variables and their values
+    run: |
+      print %ENV
+    shell: perl {0}
+```
+
+O comando usado, `perl` neste exemplo, deve ser instalado no executor.
+
+
+{% if currentVersion == "github-ae@latest" %}Para instruções instruções sobre como ter certeza de que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)".
+{% else %}
+Para informações sobre o software incluído nos executores hospedados no GitHub, consulte "[Especificações para os executores hospedados no GitHub](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+{% endif %}
+
+#### Preferências de ação de erro e códigos de saída
+
+Para palavras-chave de shell integradas, fornecemos os seguintes padrões usados por executores hospedados no {% data variables.product.prodname_dotcom %}. Você deve seguir estas diretrizes quando executar scripts shell.
 
 - `bash`/`sh`:
-  - Fail-fast behavior using `set -e o pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms.
-  - You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`.
-  - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code.
+  - Comportamento de falha rápido que usa `set -eo pipefail`: Padrão para `bash` e `shell` embutido. Também é o padrão quando você não der opção em plataformas que não sejam Windows.
+  - Você pode cancelar o fail-fast e assumir o controle fornecendo uma string de modelo para as opções do shell. Por exemplo, `bash {0}`.
+  - Shells do tipo sh saem com o código de saída do último comando executado em um script, que também é o comportamento padrão das ações. O executor relatará o status da etapa como falha/êxito com base nesse código de saída.
 
 - `powershell`/`pwsh`
-  - Fail-fast behavior when possible. For `pwsh` and `powershell` built-in shell, we will prepend `$ErrorActionPreference = 'stop'` to script contents.
-  - We append `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` to powershell scripts so action statuses reflect the script's last exit code.
-  - Users can always opt out by not using the built-in shell, and providing a custom shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need.
+  - Comportamento fail-fast quando possível. Para shell integrado `pwsh` e `powershell`, precederemos `$ErrorActionPreference = 'stop'` para conteúdos de script.
+  - Vincularemos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a scripts powershell para que os status da ação reflitam o código de saída mais recente do script.
+  - Os usuários podem sempre optar por não usar o shell integrado e fornecer uma opção personalizada, como: `pwsh -File {0}` ou `powershell -Command "& '{0}'"`, dependendo da situação.
 
 - `cmd`
-  - There doesn't seem to be a way to fully opt into fail-fast behavior other than writing your script to check each error code and respond accordingly. Because we can't actually provide that behavior by default, you need to write this behavior into your script.
-  - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. This behavior is internally consistent with the previous `sh` and `pwsh` default behavior and is the `cmd.exe` default, so this behavior remains intact.
+  - Parece não haver uma forma de optar totalmente por um comportamento fail-fast que não seja gravar seu script para verificar cada código de erro e reagir de acordo. Como não podemos fornecer esse comportamento por padrão, você precisa gravá-lo em seu script.
+  - `cmd.exe` sairá com o nível de erro do último programa que executou e retornará o código de erro para o executor. Este comportamento é internamente consistente o padrão de comportamento anterior `sh` e `pwsh`, e é o padrão `cmd.exe`; portanto, ele fica intacto.
 
 ### `jobs.<job_id>.steps[*].with`
 
-A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case.
+Um `map` (mapa) dos parâmetros de entrada definidos pela ação. Cada parâmetro de entrada é um par chave/valor. Parâmetros de entrada são definidos como variáveis de ambiente. A variável é precedida por `INPUT_` e convertida em letras maiúsculas.
 
-#### Example
+#### Exemplo
 
-Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables.
+Define os três parâmetros de entrada (`first_name`, `middle_name` e `last_name`) definidos pela ação `hello_world`. Essas variáveis de entrada estarão acessíveis para a ação `hello-world` como variáveis de ambiente `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` e `INPUT_LAST_NAME`.
 
 ```yaml
 jobs:
@@ -731,9 +901,9 @@ jobs:
 
 ### `jobs.<job_id>.steps[*].with.args`
 
-A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter.
+Uma `string` que define as entradas para um contêiner Docker. O {% data variables.product.prodname_dotcom %} entrega os `args` ao `ENTRYPOINT` do contêiner quando o contêiner inicia. Um `array de strings` não é compatível com esse parâmetro.
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
@@ -746,17 +916,17 @@ steps:
 ```
 {% endraw %}
 
-The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference:
+`args` são usados em substituição à instrução `CMD` em um `Dockerfile`. Se você usar `CMD` no `Dockerfile`, use as diretrizes ordenadas por preferência:
 
-1. Document required arguments in the action's README and omit them from the `CMD` instruction.
-1. Use defaults that allow using the action without specifying any `args`.
-1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting.
+1. Documente os argumentos necessários no README das ações e omita-os da instrução `CMD`.
+1. Use padrões que permitam o uso da ação sem especificação de `args`.
+1. Se a ação expõe um sinalizador `--help` ou similar, use isso como padrão para que a ação se documente automaticamente.
 
 ### `jobs.<job_id>.steps[*].with.entrypoint`
 
-Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run.
+Anula o `ENTRYPOINT` Docker no `Dockerfile` ou define-o caso ainda não tenha sido especificado. Diferentemente da instrução Docker `ENTRYPOINT` que tem um formulário shell e exec, a palavra-chave `entrypoint` aceita apena uma única string que define o executável.
 
-#### Example
+#### Exemplo
 
 ```yaml
 steps:
@@ -766,83 +936,83 @@ steps:
       entrypoint: /a/different/executable
 ```
 
-The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs.
+A palavra-chave `entrypoint` é para ser usada com ações de contêiner Docker, mas você também pode usá-la com ações JavaScript que não definem nenhuma entrada.
 
 ### `jobs.<job_id>.steps[*].env`
 
-Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs.<job_id>.env`](#jobsjob_idenv).
+Define variáveis de ambiente para etapas a serem usadas no ambiente do executor. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou para um trabalho. Para obter mais informações, consulte [`env`](#env) e [`jobs.<job_id>.env`](#jobsjob_idenv).
 
 {% data reusables.repositories.actions-env-var-note %}
 
-Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+Ações públicas podem especificar variáveis de ambiente esperadas no arquivo LEIAME. Se você está configurando um segredo em uma variável de ambiente, use o contexto `secrets`. Para obter mais informações, consulte "[Usar variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)e "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
 steps:
-  - name: My first action
-    env:
-      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      FIRST_NAME: Mona
-      LAST_NAME: Octocat
+ - name: minha primeira ação
+  env:
+    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    FIRST_NAME: Mona
+    LAST_NAME: Octocat
 ```
 {% endraw %}
 
 ### `jobs.<job_id>.steps[*].continue-on-error`
 
-Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails.
+Impede a falha de um trabalho se uma etapa não funcionar. Defina `true` (verdadeiro) para permitir que um trabalho aconteça quando essa etapa falhar.
 
 ### `jobs.<job_id>.steps[*].timeout-minutes`
 
-The maximum number of minutes to run the step before killing the process.
+Número máximo de minutos para executar a etapa antes de interromper o processo.
 
 ### `jobs.<job_id>.timeout-minutes`
 
-The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360
+Número máximo de minutos para permitir a execução de um trabalho o antes que o {% data variables.product.prodname_dotcom %} o cancele automaticamente. Padrão: 360
 
 ### `jobs.<job_id>.strategy`
 
-A strategy creates a build matrix for your jobs. You can define different variations to run each job in.
+Estratégias criam matrizes de compilação para os trabalhos. Você pode definir variações diferentes variações nas quais executar os trabalhos.
 
 ### `jobs.<job_id>.strategy.matrix`
 
-You can define a matrix of different job configurations. A matrix allows you to create multiple jobs by performing variable substitution in a single job definition. For example, you can use a matrix to create jobs for more than one supported version of a programming language, operating system, or tool. A matrix reuses the job's configuration and creates a job for each matrix you configure.
+Você pode definir uma matriz de diferentes configurações de trabalho. Uma matriz permite que você crie vários trabalhos que realizam a substituição de variável em uma definição de trabalho único. Por exemplo, você pode usar uma matriz para criar trabalhos para mais de uma versão compatível de uma linguagem de programação, sistema operacional ou ferramenta. Uma matriz reutiliza a configuração do trabalho e cria trabalho para cada matriz que você configurar.
 
 {% data reusables.github-actions.usage-matrix-limits %}
 
-Each option you define in the `matrix` has a key and value. The keys you define become properties in the `matrix` context and you can reference the property in other areas of your workflow file. For example, if you define the key `os` that contains an array of operating systems, you can use the `matrix.os` property as the value of the `runs-on` keyword to create a job for each operating system. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+Cada opção que você define na `matriz` tem uma chave e um valor. As chaves que você define tornam-se propriedades no contexto da `matriz` e você pode fazer referência à propriedade em outras áreas do seu arquivo de fluxo de trabalho. Por exemplo, se você definir a chave `os` que contém um array de sistemas operacionais, você poderá usar a propriedade `matrix.os` como o valor da palavra-chave `runs-on` para criar um trabalho para cada sistema operacional. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
-The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow.
+A ordem que você define uma `matriz` importa. A primeira opção que você definir será a primeira que será executada no seu fluxo de trabalho.
 
-#### Example running with more than one version of Node.js
+#### Exemplo de execução com mais de uma versão do Node.js
 
-You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 6, 8, and 10, you could specify an array of those versions in the `matrix`.
+Você pode especificar uma matriz ao fornecer um array para as opções de configuração. Por exemplo, se o executor for compatível com as versões 10, 12 e 14 do Node.js versões, você poderá especificar um array dessas versões na `matriz`.
 
-This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version.
+Este exemplo cria uma matriz de três trabalhos, definindo a chave `nó` para um array de três versões do Node.js. Para usar a matriz, o exemplo define a propriedade do contexto `matrix.node` como o valor do parâmetro `setup-node` de entrada da ação `node-version`. Como resultado, três trabalhos serão executados, cada uma usando uma versão diferente do Node.js.
 
 {% raw %}
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
   # Configures the node version used on GitHub-hosted runners
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       # The Node.js version to configure
       node-version: ${{ matrix.node }}
 ```
 {% endraw %}
 
-The `setup-node` action is the recommended way to configure a Node.js version when using {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see the [`setup-node`](https://github.com/actions/setup-node) action.
+A ação setup-node `` é a forma recomendada de configurar uma versão do Node.js ao usar executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a ação [`setup-node`](https://github.com/actions/setup-node).
 
-#### Example running with more than one operating system
+#### Exemplo de execução com mais de um sistema operacional
 
-You can create a matrix to run workflows on more than one runner operating system. You can also specify more than one matrix configuration. This example creates a matrix of 6 jobs:
+Você pode criar uma matriz para executar fluxos de trabalho em mais de um sistema operacional do executor. Você também pode especificar mais de uma configuração da matriz. Este exemplo cria uma matriz de 6 trabalhos:
 
-- 2 operating systems specified in the `os` array
-- 3 Node.js versions specified in the `node` array
+- 2 sistemas operacionais especificados na array `os`
+- 3 versões do Node.js especificadas na array do `nó`
 
 {% data reusables.repositories.actions-matrix-builds-os %}
 
@@ -851,20 +1021,22 @@ You can create a matrix to run workflows on more than one runner operating syste
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
 {% endraw %}
 
-To find supported configuration options for {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)."
+{% if currentVersion == "github-ae@latest" %}Para encontrar opções de configuração suportadas para {% data variables.actions.hosted_runner %}s, consulte "[Especificações de software](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)".
+{% else %}Para encontrar opções de configuração compatíveis com executores hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)."
+{% endif %}
 
-#### Example including additional values into combinations
+#### Exemplo de inclusão valores adicionais em combinações
 
-You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 4 of `node` runs, you can use `include` to specify that additional option.
+Você pode adicionar opções de configurações para um trabalho de matriz de compilação existente. Por exemplo, se você quer usar uma versão específica do `npm` quando o trabalho que usa o `windows-latest` e a versão 8 do `nó` é executado, você pode usar `incluir` para especificar a opção adicional.
 
 {% raw %}
 ```yaml
@@ -872,37 +1044,37 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 2
+      # includes a new variable of npm with a value of 6
       # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
-#### Example including new combinations
+#### Exemplo de inclusão novas combinações
 
-You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 12 to build on multiple operating systems, but wanted one extra experimental job using node version 13 on Ubuntu, you can use `include` to specify that additional job.
+Você pode usar `incluir` para adicionar novos trabalhos a uma matriz de criação. Qualquer configuração sem correspondência de incluir será adicionadas à matriz. Por exemplo, se você quiser usar a versão 14 do `nó` para compilar em vários sistemas operacionais, mas quiser uma tarefa experimental extra usando o node 15 no Ubuntu, você poderá usar `incluir` para especificar essa tarefa adicional.
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
 {% endraw %}
 
-#### Example excluding configurations from a matrix
+#### Exemplo excluindo configurações de uma matriz
 
-You can remove a specific configurations defined in the build matrix using the `exclude` option. Using `exclude` removes a job defined by the build matrix. The number of jobs is the cross product of the number of operating systems (`os`) included in the arrays you provide, minus any subtractions (`exclude`).
+Você pode remover uma configuração específica definida na matriz de compilação usando a opção `exclude` (excluir). `exclude` remove um trabalho definido pela matriz de compilação. O número de trabalhos é o produto cruzado do número de sistemas operacionais (`os`) incluídos nos arrays fornecidos por você, menos quaisquer subtrações (`exclude`).
 
 {% raw %}
 ```yaml
@@ -910,33 +1082,33 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # excludes node 4 on macOS
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
 {% note %}
 
-**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded.
+**Observação:** Todas as combinações de `incluir` são processadas depois de `excluir`. Isso permite que você use `incluir` para voltar a adicionar combinações que foram excluídas anteriormente.
 
 {% endnote %}
 
-##### Using environment variables in a matrix
+##### Usando variáveis de ambiente em uma matriz
 
-You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step.
+Você pode adicionar variáveis de ambiente personalizadas para cada combinação de testes usando a chave `include`. Em seguida, você pode se referir às variáveis de ambiente personalizadas em um passo posterior.
 
 {% data reusables.github-actions.matrix-variable-example %}
 
 ### `jobs.<job_id>.strategy.fail-fast`
 
-When set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs if any `matrix` job fails. Default: `true`
+Quando definido como `true`, o {% data variables.product.prodname_dotcom %} cancela todos os trabalhos em andamento em caso de falha de algum trabalho de  `matrix`. Padrão: `true`
 
 ### `jobs.<job_id>.strategy.max-parallel`
 
-The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. By default, {% data variables.product.prodname_dotcom %} will maximize the number of jobs run in parallel depending on the available runners on {% data variables.product.prodname_dotcom %}-hosted virtual machines.
+Número máximo de trabalhos que podem ser executados simultaneamente ao usar uma estratégia de trabalho de `matrix`. Por padrão, o {% data variables.product.prodname_dotcom %} maximizará o número de trabalhos executados em paralelo dependendo dos executores disponíveis nas máquinas virtuais hospedadas no {% data variables.product.prodname_dotcom %}.
 
 ```yaml
 strategy:
@@ -945,11 +1117,11 @@ strategy:
 
 ### `jobs.<job_id>.continue-on-error`
 
-Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails.
+Impede que ocorra falha na execução de um fluxo de trabalho quando ocorrer uma falha em um trabalho. Defina como `verdadeiro` para permitir que uma execução de um fluxo de trabalho passe quando este trabalho falhar.
 
-#### Example preventing a specific failing matrix job from failing a workflow run
+#### Exemplo do impedimento de uma matriz falha específica de gerar uma falha na execução do fluxo de trabalho
 
-You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `13` to fail without failing the workflow run.
+Você pode permitir que as tarefas específicas em uma matriz de tarefas falhem sem que ocorra falha na execução do fluxo de trabalho. Por exemplo, se você deseja permitir apenas um trabalho experimental com o `nó` definido como `15` sem falhar a execução do fluxo de trabalho.
 
 {% raw %}
 ```yaml
@@ -958,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -970,17 +1142,17 @@ strategy:
 
 ### `jobs.<job_id>.container`
 
-A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts.
+Contêiner para executar qualquer etapa em um trabalho que ainda não tenha especificado um contêiner. Se você tiver etapas que usam ações de script e de contêiner, as ações de contêiner serão executadas como contêineres irmãos na mesma rede e com as mesmas montagens de volume.
 
-If you do not set a `container`, all steps will run directly on the host specified by `runs-on` unless a step refers to an action configured to run in a container.
+Se você não definir um `container`, todas as etapas serão executadas diretamente no host especificado por `runs-on`, a menos que uma etapa se refira a uma ação configurada para execução em um contêiner.
 
-#### Example
+#### Exemplo
 
 ```yaml
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -990,25 +1162,25 @@ jobs:
       options: --cpus 1
 ```
 
-When you only specify a container image, you can omit the `image` keyword.
+Ao especificar somente uma imagem de contêiner, você pode omitir a palavra-chave `image`.
 
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
 
-The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name.
+Imagem Docker a ser usada como contêiner para executar a ação. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 ### `jobs.<job_id>.container.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
@@ -1023,23 +1195,23 @@ container:
 
 ### `jobs.<job_id>.container.env`
 
-Sets a `map` of environment variables in the container.
+Define um `mapa` das variáveis de ambiente no contêiner.
 
 ### `jobs.<job_id>.container.ports`
 
-Sets an `array` of ports to expose on the container.
+Define um `array` de portas para expor no contêiner.
 
 ### `jobs.<job_id>.container.volumes`
 
-Sets an `array` of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.
+Define um `array` de volumes para uso do contêiner. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host.
 
-To specify a volume, you specify the source and destination path:
+Para especificar um volume, especifique o caminho de origem e destino:
 
 `<source>:<destinationPath>`.
 
-The `<source>` is a volume name or an absolute path on the host machine, and `<destinationPath>` is an absolute path in the container.
+`<source>` é um nome de volume ou caminho absoluto na máquina host, e `<destinationPath>` é um caminho absoluto no contêiner.
 
-#### Example
+#### Exemplo
 
 ```yaml
 volumes:
@@ -1050,54 +1222,54 @@ volumes:
 
 ### `jobs.<job_id>.container.options`
 
-Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)."
+Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)".
 
 ### `jobs.<job_id>.services`
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner  automatically creates a Docker network and manages the life cycle of the service containers.
+Usado para hospedar contêineres de serviço para um trabalho em um fluxo de trabalho. Contêineres de serviço são úteis para a criação de bancos de dados ou serviços armazenamento em cache como o Redis. O executor cria automaticamente uma rede do Docker e gerencia o ciclo de vida dos contêineres do serviço.
 
-If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow.
+Se você configurar seu trabalho para ser executado em um contêiner, ou a sua etapa usar ações ao contêiner, você não precisará mapear as portas para acessar o serviço ou a ação. O Docker expõe automaticamente todas as portas entre os contêineres da mesma rede de ponte definida pelo usuário. Você pode fazer referência ao contêiner de serviço diretamente pelo seu nome de host. O nome do host é mapeado automaticamente com o nome da etiqueta que você configurar para o serviço no fluxo de trabalho.
 
-If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port.
+Se você configurar a tarefa para executar diretamente na máquina do executor e sua etapa não usar uma ação de contêiner, você deverá mapear todas as portas de contêiner de serviço do Docker necessárias para o host do Docker (a máquina do executor). Você pode acessar o contêiner de serviço usando host local e a porta mapeada.
 
-For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+Para obter mais informações sobre as diferenças entre os contêineres de serviço de rede, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers)".
 
-#### Example using localhost
+#### Exemplo de uso de host local
 
-This example creates two services: nginx and redis. When you specify the Docker host port but not the container port, the container port is randomly assigned to a free port. {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services.<service_name>.ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts.
+Este exemplo cria dois serviços: nginx e redis. Ao especificar a porta do host do Docker mas não a porta do contêiner, a porta do contêiner será atribuída aleatoriamente a uma porta livre. O {% data variables.product.prodname_dotcom %} define a porta de contêiner atribuída no contexto {% raw %}`${{job.services.<service_name>.ports}}`{% endraw %}. Neste exemplo, você pode acessar as portas do contêiner de serviço usando os contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} e {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}.
 
 ```yaml
-services:
+serviços:
   nginx:
-    image: nginx
-    # Map port 8080 on the Docker host to port 80 on the nginx container
-    ports:
+    imagem: nginx
+    # Mapeia a porta 8080 no host do Docker com a porta 80 no contêiner nginx
+    portas:
       - 8080:80
   redis:
-    image: redis
-    # Map TCP port 6379 on Docker host to a random free port on the Redis container
-    ports:
+    imagem: redis
+    # Mapeia a porta  port 6379 TCP no host do Docker com uma porta livre aleatória no contêiner Redis
+    portas:
       - 6379/tcp
 ```
 
 ### `jobs.<job_id>.services.<service_id>.image`
 
-The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name.
+Imagem Docker a ser usada como contêiner de serviço para executar a ação. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 ### `jobs.<job_id>.services.<service_id>.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
@@ -1113,23 +1285,23 @@ services:
 
 ### `jobs.<job_id>.services.<service_id>.env`
 
-Sets a `map` of environment variables in the service container.
+Define um `maá` das variáveis de ambiente no contêiner do serviço.
 
 ### `jobs.<job_id>.services.<service_id>.ports`
 
-Sets an `array` of ports to expose on the service container.
+Define um `array` de portas para expor no contêiner de serviço.
 
 ### `jobs.<job_id>.services.<service_id>.volumes`
 
-Sets an `array` of volumes for the service container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.
+Define um `array` de volumes para uso do contêiner de serviço. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host.
 
-To specify a volume, you specify the source and destination path:
+Para especificar um volume, especifique o caminho de origem e destino:
 
 `<source>:<destinationPath>`.
 
-The `<source>` is a volume name or an absolute path on the host machine, and `<destinationPath>` is an absolute path in the container.
+`<source>` é um nome de volume ou caminho absoluto na máquina host, e `<destinationPath>` é um caminho absoluto no contêiner.
 
-#### Example
+#### Exemplo
 
 ```yaml
 volumes:
@@ -1140,63 +1312,63 @@ volumes:
 
 ### `jobs.<job_id>.services.<service_id>.options`
 
-Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)."
+Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)".
 
-### Filter pattern cheat sheet
+### Folha de consulta de filtro padrão
 
-You can use special characters in path, branch, and tag filters.
+Você pode usar caracteres especiais nos filtros de caminhos, branches e tags.
 
-- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`.
-- `**`: Matches zero or more of any character.
-- `?`: Matches zero or one single character. For example, `Octoc?t` matches `Octocat`.
-- `+`: Matches one or more of the preceding character.
-- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-f]` matches any digits or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`.
-- `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character.
+- `*`: Corresponde a zero ou mais caracteres, mas não Corresponde ao caractere `/`. Por exemplo, `Octo*` corresponde a `Octocat`.
+- `**`: Corresponde a zero ou mais de qualquer caractere.
+- `?`: Corresponde a zero ou a um único caractere. Por exemplo, `Octoc?t` corresponde a `Octocat`.
+- `+`: Corresponde a um ou mais dos caracteres anteriores.
+- `[]` Corresponde a um caractere listado entre colchetes ou incluído nos intervalos. Os intervalos só podem incluir valores de `a-z`, `A-Z`, e `0-9`. Por exemplo, o intervalo`[0-9a-z]` corresponde a qualquer letra maiúscula ou minúscula. Por exemplo, `[CB]at` corresponde a `Cat` ou `Bat` e `[1-2]00` corresponde a `100` e `200`.
+- `!` No início de um padrão faz com que ele anule padrões positivos anteriores. Não tem nenhum significado especial caso não seja o primeiro caractere.
 
-The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes.
+Os caracteres `*`, `[` e `!` são caracteres especiais em YAML. Se você iniciar um padrão com `*`, `[` ou `!`, você deverá colocá-lo entre aspas.
 
 ```yaml
-# Valid
+# Válido
 - '**/README.md'
 
-# Invalid - creates a parse error that
-# prevents your workflow from running.
+# Inválido - Cria um erro de análise que
+# impede que o seu fluxo de trabalho seja executado.
 - **/README.md
 ```
 
-For more information about branch, tag, and path filter syntax, see "[`on.<push|pull_request>.<branches|tags>`](#onpushpull_requestbranchestags)" and "[`on.<push|pull_request>.paths`](#onpushpull_requestpaths)."
+Para obter mais informações sobre a sintaxe de filtros de branches, tags e caminhos, consulte "[`on.<push|pull_request>.<branches|tags>`](#onpushpull_requestbranchestags)" e "[`on.<push|pull_request>.paths`](#onpushpull_requestpaths)".
 
-#### Patterns to match branches and tags
+#### Padrões para corresponder branches e tags
 
-| Pattern | Description | Example matches |
-|---------|------------------------|---------|
-| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). |  -`feature/my-branch`<br/>-`feature/your-branch` |
-| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | -`feature/beta-a/my-branch`<br/>-`feature/your-branch`<br/>-`feature/mona/the/octocat` |
-| -`main`<br/>-`releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | -`main`<br/>-`releases/mona-the-octocat` |
-| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`main`<br/>-`releases` |
-| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | -`all/the/branches`<br/>-`every/tag` |
-| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`mona-feature`<br/>-`feature`<br/>-`ver-10-feature` |
-| `v2*` | Matches branch and tag names that start with `v2`. | -`v2`<br/>-`v2.0`<br/>-`v2.9` |
-| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | -`v1.10.1`<br/>-`v2.0.0` |
+| Padrão                                                 | Descrição                                                                                                                                                                           | Exemplos de correspondências                                                                                          |
+| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `feature/*`                                            | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`).                                                                                                    | `feature/my-branch`<br/><br/>`feature/your-branch`                                                        |
+| `feature/**`                                           | `**` correspondem a qualquer caractere, incluindo a barra (`/`) em nomes de branches e tags.                                                                                        | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
+| `main`<br/><br/>`releases/mona-the-octcat` | Corresponde ao nome exato de um branch ou tag.                                                                                                                                      | `main`<br/><br/>`releases/mona-the-octocat`                                                               |
+| `'*'`                                                  | Corresponde a todos os nomes de branches e tags que não contêm uma barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `main`<br/><br/>`releases`                                                                                |
+| `'**'`                                                 | Corresponde a todos os nomes de branches e tags. Esse é o comportamento padrão quando você não usa um filtro de `branches` ou `tags`.                                               | `all/the/branches`<br/><br/>`every/tag`                                                                   |
+| `'*feature'`                                           | O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas.                                                                                 | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature`                                   |
+| `v2*`                                                  | Corresponde aos nomes de branches e tags que iniciam com `v2`.                                                                                                                      | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9`                                                          |
+| `v[12].[0-9]+.[0-9]+`                                  | Corresponde a todas as tags de versão de branch semântica com a versão principal 1 ou 2                                                                                             | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
 
-#### Patterns to match file paths
+#### Padrões para corresponder a caminhos de arquivos
 
-Path patterns must match the whole path, and start from the repository's root.
+Padrões de caminhos devem corresponder ao caminho completo e iniciar a partir da raiz do repositório.
 
-| Pattern | Description of matches | Example matches |
-|---------|------------------------|-----------------|
-| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`README.md`<br/>-`server.rb` |
-| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | -`page.js`<br/>-`page.jsx` |
-| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | -`all/the/files.md` |
-| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | -`app.js`<br/>-`index.js`
-| `'**.js'` | Matches all `.js` files in the repository. | -`index.js`<br/>-`js/index.js`<br/>-`src/js/app.js` |
-| `docs/*`  | All files within the root of the `docs` directory, at the root of the repository. | -`docs/README.md`<br/>-`docs/file.txt` |
-| `docs/**` | Any files in the `/docs` directory at the root of the repository. | -`docs/README.md`<br/>-`docs/mona/octocat.txt` |
-| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | -`docs/README.md`<br/>-`docs/mona/hello-world.md`<br/>-`docs/a/markdown/file.md`
-| `'**/docs/**'`   | Any files in a `docs` directory anywhere in the repository. | -`/docs/hello.md`<br/>-`dir/docs/my-file.txt`<br/>-`space/docs/plan/space.doc`
-| `'**/README.md'` | A README.md file anywhere in the repository. | -`README.md`<br/>-`js/README.md`
-| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | -`a/src/app.js`<br/>-`my-src/code/js/app.js`
-| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | -`my-post.md`<br/>-`path/their-post.md` |
-| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | -`migrate-10909.sql`<br/>-`db/migrate-v1.0.sql`<br/>-`db/sept/migrate-v1.sql` |
-| -`*.md`<br/>-`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | -`hello.md`<br/>_Does not match_<br/>-`README.md`<br/>-`docs/hello.md` |
-| -`*.md`<br/>-`!README.md`<br/>-`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | -`hello.md`<br/>-`README.md`<br/>-`README.doc`|
+| Padrão                                                                  | Descrição das correspondências                                                                                                                                                                                         | Exemplos de correspondências                                                                                             |
+| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `'*'`                                                                   | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas.                                   | `README.md`<br/><br/>`server.rb`                                                                             |
+| `'*.jsx?'`                                                              | O caractere `?` corresponde a zero ou a um dos caracteres anteriores.                                                                                                                                                  | `page.js`<br/><br/>`page.jsx`                                                                                |
+| `'**'`                                                                  | `**` corresponde a qualquer caractere incluindo a barra (`/`). Esse é o comportamento padrão quando você não usa um filtro de `path`.                                                                                  | `all/the/files.md`                                                                                                       |
+| `'*.js'`                                                                | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). Corresponde a todos os arquivos `.js` na raiz do repositório.                                                                         | `app.js`<br/><br/>`index.js`                                                                                 |
+| `'**.js'`                                                               | Corresponde a todos os arquivos `.js` no repositório.                                                                                                                                                                  | `index.js`<br/><br/>`js/index.js`<br/><br/>`src/js/app.js`                                       |
+| `docs/*`                                                                | Todos os arquivos dentro da raiz do diretório `docs`, na raiz do repositório.                                                                                                                                          | `docs/README.md`<br/><br/>`docs/file.txt`                                                                    |
+| `docs/**`                                                               | Qualquer arquivo no diretório `docs`, na raiz do repositório.                                                                                                                                                          | `docs/README.md`<br/><br/>`docs/mona/octocat.txt`                                                            |
+| `docs/**/*.md`                                                          | Um arquivo com um sufixo `.md` em qualquer local do diretório `docs`.                                                                                                                                                  | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`          |
+| `'**/docs/**'`                                                          | Qualquer arquivo no diretório `docs`, em qualquer local do repositório.                                                                                                                                                | `/docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`            |
+| `'**/README.md'`                                                        | Um arquivo README.md em qualquer local do repositório.                                                                                                                                                                 | `README.md`<br/><br/>`js/README.md`                                                                          |
+| `'**/*src/**'`                                                          | Qualquer arquivo em uma pasta com o sufixo `src` em qualquer local do repositório.                                                                                                                                     | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`                                                              |
+| `'**/*-post.md'`                                                        | Um arquivo com o sufixo `-post.md` em qualquer local do repositório.                                                                                                                                                   | `my-post.md`<br/><br/>`path/their-post.md`                                                                   |
+| `'**/migrate-*.sql'`                                                    | Um arquivo com o prefixo `migrate-` e sufixo `.sql` em qualquer local do repositório.                                                                                                                                  | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql`             |
+| `*.md`<br/><br/>`!README.md`                                | Usar um sinal de exclamação (`!`) na frente de um padrão o anula. Quando um arquivo corresponde a um padrão e também corresponde a um padrão negativo definido posteriormente no arquivo, o arquivo não será incluído. | `hello.md`<br/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
+| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | Os padrões são verificados sequencialmente. Um padrão que anula um padrão anterior irá incluir caminhos de arquivos novamente.                                                                                         | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`                                            |
diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 59233eab00..d7e6f0eb32 100644
--- a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ Para a lista geral das ferramentas incluídas para cada sistema operacional do e
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ Recomendamos usar ações para interagir com o software instalado nos executores
 
 Se houver uma ferramenta que você queira solicitar, abra um problema em [actions/virtual-environments](https://github.com/actions/virtual-environments). Este repositório também contém anúncios sobre todas as principais atualizações de software nos executores.
 
+#### Instalando software adicional
+
+Você pode instalar um software adicional em executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Personalizar executores hospedados no GitHub](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
 ### Endereços IP
 
 {% note %}
diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..3a78c8e776
--- /dev/null
+++ b/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Personalizando executores hospedados no GitHub
+intro: Você pode instalar software adicional em executores hospedados no GitHub como parte do seu fluxo de trabalho.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+Se você precisar de pacotes de software adicionais em executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá criar um trabalho que instale os pacotes como parte de seu fluxo de trabalho.
+
+Para ver quais pacotes já estão instalados por padrão, consulte "[Software pré-instalado](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)".
+
+Este guia demonstra como criar um trabalho que instale software adicional em um executor hospedado em {% data variables.product.prodname_dotcom %}.
+
+### Instalando software nos executores do Ubuntu
+
+O exemplo a seguir demonstra como instalar um pacote `apt` como parte de um trabalho.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**Observação:** Sempre execute `sudo apt-get update` antes de instalar um pacote. Caso o índice `apt` seja obsoleto, este comando busca e indexa novamente quaisquer pacotes disponíveis, o que ajuda a prevenir falhas na instalação do pacote.
+
+{% endnote %}
+
+### Instalando o software nos executores do macOS
+
+O exemplo a seguir demonstra como instalar pacotes de Brew e cascas como parte de um trabalho.
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### Instalando software em executores do Windows
+
+O exemplo a seguir demonstra como usar o [Chocolatey](https://community.chocolatey.org/packages) para instalar a CLI de {% data variables.product.prodname_dotcom %} como parte de um trabalho.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/index.md b/translations/pt-BR/content/actions/using-github-hosted-runners/index.md
index d21bb651ab..b96fba75f1 100644
--- a/translations/pt-BR/content/actions/using-github-hosted-runners/index.md
+++ b/translations/pt-BR/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% link_in_list /about-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/pt-BR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/pt-BR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..f2994094be
--- /dev/null
+++ b/translations/pt-BR/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: Sobre o licenciamento para o GitHub Advanced Security
+intro: 'Você precisa de uma licença para usar funcionalidades de {% data variables.product.prodname_GH_advanced_security %}, como {% data variables.product.prodname_code_scanning %} e {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### Sobre o licenciamento para {% data variables.product.prodname_GH_advanced_security %}
+
+Você pode disponibilizar funcionalidades adicionais para segurança de código, comprando e fazendo o upload de uma licença para {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações sobre {% data variables.product.prodname_GH_advanced_security %}, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% data reusables.advanced-security.license-overview %}
+
+Para discutir licenciamento {% data variables.product.prodname_GH_advanced_security %} para {% data variables.product.product_name %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para habilitar {% data variables.product.prodname_GH_advanced_security %}, consulte "[Habilitar {% data variables.product.prodname_GH_advanced_security %} para seu dispositivo](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### Sobre os números do committer para {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### Gerenciar o uso de sua licença para {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+É possível aplicar políticas que permitam ou não o uso de {% data variables.product.prodname_advanced_security %} por parte de organizações pertencentes à conta corporativa. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
+
+Para obter mais informações sobre a visualização do uso da licença, consulte "[Visualizar o seu uso de {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/viewing-your-github-advanced-security-usage)".
+
+### Obtenha o máximo da sua licença de {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..3feb27c435
--- /dev/null
+++ b/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: Configurar a varredura de código para o seu aparelho
+shortTitle: Configurar a varredura do código
+intro: 'Você pode habilitar, configurar e desativar {% data variables.product.prodname_code_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} permite aos usuários varrer códigos com relação a erros e vulnerabilidades.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### Sobre o {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+Você pode configurar {% data variables.product.prodname_code_scanning %} para executar análise de {% data variables.product.prodname_codeql %} e análise de terceiros. {% data variables.product.prodname_code_scanning_capc %} também é compatível com a análise de execução nativa que utiliza {% data variables.product.prodname_actions %} ou externamente que utiliza a infraestrutura de CI/CD existente. A tabela abaixo resume todas as opções disponíveis para os usuários quando você configurar {% data variables.product.product_location %} para permitir que {% data variables.product.prodname_code_scanning %} use ações.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Pré-requisitos para {% data variables.product.prodname_code_scanning %}
+
+- Uma licença para {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (consulte "[Sobre licenciamento para {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} habilitado no console de gerenciamento (consulte "[Habilitando {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- Uma VM ou contêiner para que a análise de {% data variables.product.prodname_code_scanning %} seja executada.
+
+### Executar {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_actions %}
+
+#### Configurar um executor auto-hospedado
+
+{% data variables.product.prodname_ghe_server %} pode executar {% data variables.product.prodname_code_scanning %} usando um fluxo de trabalho de {% data variables.product.prodname_actions %}. Primeiro, você precisa fornecer um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} em seu ambiente. É possível fornecer executores auto-hospedados no nível da conta do repositório, organização ou empresa. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
+
+Você deve garantir que o Git esteja na variável do PATH em qualquer executor auto-hospedados que você usar para executar ações de {% data variables.product.prodname_codeql %}.
+
+#### Provisionando ações para {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Se você deseja usar ações para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %}, as ações deverão estar disponíveis no seu dispositivo.
+
+A ação {% data variables.product.prodname_codeql %} está incluída na sua instalação de {% data variables.product.prodname_ghe_server %}. Se {% data variables.product.prodname_ghe_server %} tiver acesso à internet, a ação fará automaticamente o download do pacote de {% data variables.product.prodname_codeql %} necessário para realizar a análise. Como alternativa, você pode usar uma ferramenta de sincronização para tornar o pacote de análise de {% data variables.product.prodname_codeql %} disponível localmente. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_codeql %} análise em um servidor sem acesso à internet](#configuring-codeql-analysis-on-a-server-without-internet-access)" abaixo.
+
+Você também pode disponibilizar ações de terceiros para os usuários de {% data variables.product.prodname_code_scanning %}, configurando {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_github_connect %} para sincronizar {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" abaixo.
+
+#### Configurar a análise de {% data variables.product.prodname_codeql %} em um servidor sem acesso à internet
+Se o servidor em que você está executando {% data variables.product.prodname_ghe_server %} não estiver conectado à internet e você deseja permitir que os usuários habilitem {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para seus repositórios, você deverá usar a ferramenta de sincronização de ação {% data variables.product.prodname_codeql %} para copiar o pacote de análises {% data variables.product.prodname_codeql %} de {% data variables.product.prodname_dotcom_the_website %} para seu servidor. A ferramenta e os detalhes de como usá-la estão disponíveis em [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/).
+
+Se você configurar a ferramenta de sincronização de ação de {% data variables.product.prodname_codeql %}, você poderá usá-la para sincronizar as últimas versões da ação de {% data variables.product.prodname_codeql %} e pacote de análise associado a {% data variables.product.prodname_codeql %}. Estes são compatíveis com {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+Para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %}, as ações apropriadas devem estar disponíveis localmente. Você pode disponibilizar as ações de três maneiras.
+
+- **Recomendado**: Você pode usar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)".
+- Se você desejar usar o {% data variables.product.prodname_codeql_workflow %}, você pode sincronizar o repositório do {% data variables.product.prodname_dotcom_the_website %} ao {% data variables.product.prodname_ghe_server %}, usando a ferramenta de sincronização de Ação do {% data variables.product.prodname_codeql %} disponível em [https://github. om/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Você pode usar essa ferramenta independentemente se {% data variables.product.product_location %} ou seus executores de {% data variables.product.prodname_actions %} terem acesso à internet, contanto que você possa acessar {% data variables.product.product_location %} e {% data variables.product.prodname_dotcom_the_website %} simultaneamente no seu computador.
+- É possível criar uma cópia local do repositório de uma ação no servidor, clonando o repositório de {% data variables.product.prodname_dotcom_the_website %} que contém a ação. Por exemplo, se você quiser usar as ações para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você poderá criar um repositório na sua instância denominado `github/codeql-action`. Em seguida, clone o [repositório](https://github.com/github/codeql-action) de {% data variables.product.prodname_dotcom_the_website %} depois faça push desse repositório no repositório `github/codeql-action` da instância. Você também deverá fazer o download de qualquer uma das versões do repositório no {% data variables.product.prodname_dotcom_the_website %} e fazer o upload no repositório `github/codeql-action` de sua instância como versões.
+{% endif %}
+
+#### Configurar {% data variables.product.prodname_github_connect %} para sincronizar {% data variables.product.prodname_actions %}
+1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)".
+2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)".
+3. A próxima etapa é configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+4. Adicione um executor auto-hospedado ao seu repositório, organização ou conta corporativa. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
+
+### Executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}
+Se você não quiser usar {% data variables.product.prodname_actions %}, você poderá executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}.
+
+O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que você pode adicionar ao seu sistema CI/CD de terceiros. A ferramenta executa a análise do {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
diff --git a/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..c0a28cf0df
--- /dev/null
+++ b/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: Configurar a varredura de segredo para o seu dispositivo
+shortTitle: Configurar a varredura de segredo
+intro: 'Você pode habilitar, configurar e desabilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} permite aos usuários fazer a varredura de códigos para os segredos que se confirmaram acidentalmente.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### Sobre o {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.secret-scanning.about-secret-scanning %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning).
+
+### Pré-requisitos para {% data variables.product.prodname_secret_scanning %}
+
+
+- É necessário habilitar o sinalizador de CPU das [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extensões SIMD de Streaming Suplementar 3) no VM/KVM que executa {% data variables.product.product_location %}.
+
+- Uma licença para {% data variables.product.prodname_GH_advanced_security %} (consulte "[Sobre a licença para {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} habilitado no console de gerenciamento (consulte "[Habilitando {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### Verificar suporte para o sinalizador SSSE3 nos seus vCPUs
+
+O conjunto de instruções das SSSE3 é necessário porque o {% data variables.product.prodname_secret_scanning %} alavanca o padrão acelerado de hardware que corresponde para encontrar possíveis credenciais confirmadas com os seus repositórios de {% data variables.product.prodname_dotcom %}. SSSE3 está habilitado para a maioria das CPUs modernas. Você pode verificar se o SSSE3 está habilitado para oa vCPUs disponíveis para sua instância de {% data variables.product.prodname_ghe_server %}.
+
+1. Conecte ao shell administrativo para sua instância de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)".
+2. Insira o seguinte comando:
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+Se ele retornar o valor `0`, significa que o sinalizador SSSE3 está disponível e habilitado. Agora você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" abaixo.
+
+Se isso não retornar `0`, SSSE3 não está habilitado no seu VM/KVM. Você precisa consultar a documentação do hardware/hipervisor sobre como habilitar o sinalizador ou disponibilizá-lo para VMs convidados.
+
+#### Verificar se você tem uma licença de {% data variables.product.prodname_advanced_security %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Verificar se há uma **{% data variables.product.prodname_advanced_security %}** entrada na barra lateral esquerda. ![Barra lateral de segurança avançada](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### Habilitar {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Em "{% data variables.product.prodname_advanced_security %}," clique em **{% data variables.product.prodname_secret_scanning_caps %}**. ![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### Desabilitar {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Em "{% data variables.product.prodname_advanced_security %}", desmarque **{% data variables.product.prodname_secret_scanning_caps %}**. ![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..a9ca009a71
--- /dev/null
+++ b/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Habilitar o GitHub Advanced Security para a sua empresa
+shortTitle: Habilitar o GitHub Advanced Security
+intro: 'Você pode configurar {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}. Isso fornece funcionalidades extras que ajudam os usuários a encontrar e corrigir problemas de segurança no seu código.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### Sobre habilitar {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, os administradores de repositórios em todas as organizações poderão habilitar as funcionalidades, a menos que você configure uma política para restringir o acesso. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".
+{% else %}
+Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, os administradores de repositórios em todas as organizações podem habilitar as funcionalidades. {% if currentVersion == "enterprise-server@3.0" %}Para obter mais informações, consulte "[Gerenciar as configurações de segurança e análise de sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %}
+{% endif %}
+
+### Pré-requisitos para habilitar {% data variables.product.prodname_GH_advanced_security %}
+
+1. Atualize sua licença para {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} Para obter informações sobre licenças, consulte "[Sobre licenciamento para {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)".{% endif %}
+2. Faça o upload da nova licença para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Gerenciar a sua licença do GitHub Enterprise](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Revise os pré-requisitos para as funcionalidades que você pretende habilitar.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, consulte "[Configurando {% data variables.product.prodname_code_scanning %} para seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, consulte "[Configurando {% data variables.product.prodname_secret_scanning %} para seu dispositivo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. Se sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, a página de licença incluirá uma seção que mostra os detalhes do uso atual. ![Seção de {% data variables.product.prodname_GH_advanced_security %} de licença empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Se a sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, haverá uma entrada de **{% data variables.product.prodname_advanced_security %}** na barra lateral esquerda. ![Barra lateral de segurança avançada](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Habilitar e desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Em "{% data variables.product.prodname_advanced_security %}", selecione as funcionalidades que você deseja habilitar e desmarque quaisquer funcionalidades que deseja desabilitar. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %}
+1. Em "{% data variables.product.prodname_advanced_security %}," clique em **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+Quando {% data variables.product.product_name %} terminar de reiniciar, você estará pronto para definir todas as funcionalidades adicionais necessárias para recursos recém-habilitados. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_code_scanning %} para seu aplicativo ](/admin/advanced-security/configuring-code-scanning-for-your-appliance)".
+
+### Habilitar ou desabilitar {% data variables.product.prodname_GH_advanced_security %} através do shell administrativo (SSH)
+
+Você pode habilitar ou desabilitar as funcionalidades programaticamente em {% data variables.product.product_location %}. Para mais informações sobre o shell administrativo e os utilitários da linha de comando para {% data variables.product.prodname_ghe_server %}, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[Utilitários de linha de comando](/admin/configuration/command-line-utilities#ghe-config)".
+
+Por exemplo, você pode habilitar {% data variables.product.prodname_code_scanning %} com suas ferramentas de código de infraestrutura quando e quando você implantar uma instância para preparação ou recuperação de desastres.
+
+1. SSH em {% data variables.product.product_location %}.
+1. Habilite {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. Opcionalmente, desabilite {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. Aplique a configuração.
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}Para habilitar e desabilitar {% data variables.product.prodname_secret_scanning %} da mesma forma, defina: `app ghe-config. ecret-scanning.enabled` como verdadeiro ou falso e aplique a configuração.{% endif %}
diff --git a/translations/pt-BR/content/admin/advanced-security/index.md b/translations/pt-BR/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..f8eb1644b3
--- /dev/null
+++ b/translations/pt-BR/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Gerenciando o GitHub Advanced Security para a sua empresa
+shortTitle: Gerenciar o GitHub Advanced Security
+intro: 'Você pode configurar {% data variables.product.prodname_advanced_security %} e gerenciar o uso pela sua empresa para atender às necessidades da sua organização.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### Índice
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..d89c564561
--- /dev/null
+++ b/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,23 @@
+---
+title: Visualizar o seu uso do GitHub Advanced Security
+intro: 'Você pode visualizar o uso de sua licença do {% data variables.product.prodname_GH_advanced_security %}.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} Para obter mais informações, consulte "[Sobre licenciamento para {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security).
+
+### Visualizar o uso de licença para {% data variables.product.prodname_GH_advanced_security %}
+
+Você pode verificar quantas estações a sua licença inclui e quantas estações estão atualmente em uso.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   A seção "{% data variables.product.prodname_GH_advanced_security %}" mostra os detalhes do uso atual. Você pode ver o número total de estações usadas, bem como uma tabela com o número de committers e committers únicos para cada organização. ![Seção de {% data variables.product.prodname_GH_advanced_security %} de licença empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Opcionalmente, clique no nome de uma organização em que você é um proprietário para exibir as configurações de segurança e análise para a organização. ![Organização proprietária na seção de {% data variables.product.prodname_GH_advanced_security %} das configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. Na página de configurações "Análise de & segurança" desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}" para ver uma descrição detalhada do uso por repositório para esta organização. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
diff --git a/translations/pt-BR/content/admin/all-releases.md b/translations/pt-BR/content/admin/all-releases.md
new file mode 100644
index 0000000000..5397c7fb3e
--- /dev/null
+++ b/translations/pt-BR/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: Versões do GitHub Enterprise Server
+intro: 'Documentação para as versões atualmente compatíveis e obsoletas do {{ site.data.variables.product.prodname_ghe_server }}.'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## Atualmente compatível
+
+Consulte [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) para obter informações sobre a versão mais recente.
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## Obsoleto
+
+A documentação para versões obsoletas permanece disponível, mas não é mais mantida.
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## Documentação de desenvolvedor descontinuada
+
+A documentação do desenvolvedor para versões obsoletas permanece disponível, mas não é mais mantida.
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index 9cab5f9699..f0dd010b21 100644
--- a/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: 'Você pode usar a autenticação incluída em {% if enterpriseServerVers
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### Sobre a identidade e gestão de acesso para a sua empresa
diff --git a/translations/pt-BR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/pt-BR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index fbe97fce55..cd55cc9aed 100644
--- a/translations/pt-BR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/pt-BR/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### Sobre a autenticação integrada para usuários de fora do provedor de identidade
diff --git a/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md b/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md
index 4d09210fb9..d068b60073 100644
--- a/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 As contas de usuário no {% data variables.product.product_location %} são preservadas quando você altera o método de autenticação, e os usuários continuarão fazendo login na mesma conta (desde que não haja alteração nos nomes de usuário).
diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index f1299a3b89..31dfcf706f 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Sobre autenticação e provisionamento de usuário com Azure AD
diff --git a/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index 069b81865c..3d14ffd356 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Sobre o SAML SSO
diff --git a/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index 17ab5e80ec..05fbee838f 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### Sobre provisionamento de usuários para sua empresa
diff --git a/translations/pt-BR/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/pt-BR/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index 7c899695af..c184167cda 100644
--- a/translations/pt-BR/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/pt-BR/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: 'Se você estiver usando a autenticação integrada, será possível impedir que pessoas não autenticadas criem uma conta.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/authentication/using-built-in-authentication.md b/translations/pt-BR/content/admin/authentication/using-built-in-authentication.md
index 86ac5f7084..12a1e03762 100644
--- a/translations/pt-BR/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/pt-BR/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 Você pode criar mensagens personalizadas que os usuários verão nas páginas de login e logout. Para obter mais informações, consulte "[Personalizar mensagens de usuário na instância](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)".
diff --git a/translations/pt-BR/content/admin/authentication/using-cas.md b/translations/pt-BR/content/admin/authentication/using-cas.md
index 269ca9a18b..0f9a6f3843 100644
--- a/translations/pt-BR/content/admin/authentication/using-cas.md
+++ b/translations/pt-BR/content/admin/authentication/using-cas.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'O CAS é um protocolo de logon único (SSO) para vários aplicativos da web. Uma conta de usuário CAS não ocupa uma {% if currentVersion ver_gt "enterprise-server@2.16" %}licença de usuário{% else %}estação{% endif %} até que o usuário se conecte.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/pt-BR/content/admin/authentication/using-ldap.md b/translations/pt-BR/content/admin/authentication/using-ldap.md
index 75b650752f..a110944131 100644
--- a/translations/pt-BR/content/admin/authentication/using-ldap.md
+++ b/translations/pt-BR/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: 'O LDAP permite autenticar o {% data variables.product.prodname_ghe_server %} em suas contas existentes e gerenciar centralmente o acesso ao repositório. O LDAP é um protocolo de aplicativo popular de acesso e manutenção dos serviços de informações de diretório, além de ser um dos protocolos mais comuns para integrar software de terceiros a diretórios de usuários em grandes empresas.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/pt-BR/content/admin/authentication/using-saml.md b/translations/pt-BR/content/admin/authentication/using-saml.md
index 15c65a3c9f..11eea5330e 100644
--- a/translations/pt-BR/content/admin/authentication/using-saml.md
+++ b/translations/pt-BR/content/admin/authentication/using-saml.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'O SAML é um padrão de autenticação e autorização baseado em XML. O {% data variables.product.prodname_ghe_server %} pode agir como provedor de serviços (SP, Service Provider) com seu provedor de identidade (IdP, Identity Provider) SAML interno.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
@@ -48,7 +53,7 @@ O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam prese
 
 ### Metadados SAML
 
-Os metadados do provedor de serviços da sua instância do {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`.
+Os metadados do seu provedor de serviço da instância de {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`.
 
 Para configurar seu provedor de identidade manualmente, a URL do serviço de consumidor de declaração (ACS, Assertion Consumer Service) é `http(s)://[hostname]/saml/consume` e usa a associação `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`.
 
@@ -81,7 +86,7 @@ Os atributos a seguir estão disponíveis. Você pode alterar seus nomes no [con
 
   {% endtip %}
 
-5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. ![Configuração desativar administrador SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png)
+5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. ![Configuração de desabilitar administrador de SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png)
 6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTP ou HTTPS do seu IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o nome do host só estiver disponível na rede interna, talvez seja necessário [configurar a {% data variables.product.product_location %} para usar servidores de nomes internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticação SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png)
 7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Fazer isso verifica a autenticidade das mensagens enviadas para a {% data variables.product.product_location %}. ![Emissor SAML](/assets/images/enterprise/management-console/saml-issuer.png)
 8. Nos menus suspensos **Signature Method** (Método de assinatura) e **Digest Method** (Método de compilação), escolha o algoritmo de hash usado pelo emissor SAML para verificar a integridade das solicitações do {% data variables.product.product_location %}. Especifique o formato no menu suspenso **Name Identifier Format** (Formato de identificador de nome). ![Método SAML ](/assets/images/enterprise/management-console/saml-method.png)
diff --git a/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md b/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md
index 782a03c7fa..2c79f14dfe 100644
--- a/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/pt-BR/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: 'Você pode usar o painel de administração do site{% if enterpriseServe
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 A primeira vez que você acessar sua empresa, você irá definir uma configuração inicial para fazer com que
-{% data variables.product.product_name %} esteja pronto para usar. A configuração inicial inclui conectar a sua empresa a um idP, efetuar a autenticação com o SSO SAML e configurar políticas para repositórios e organizações da sua empresa. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
-
-Para os usuários receberem qualquer e-mail de {% data variables.product.product_name %} após a configuração inicial, você precisa pedir que {% data variables.contact.github_support %} configure o suporte a email de saída com o seu servidor SMTP. Para obter mais informações, consulte "[Configurar e-mail para notificações](/admin/configuration/configuring-email-for-notifications).
+{% data variables.product.product_name %} esteja pronto para usar. A configuração inicial inclui conectar a sua empresa a um provedor de identidade (IdP), efetuando a autenticação com SAML SSO, configurando políticas para repositórios e organizações na sua empresa e configurando SMTP para e-mails de saída. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
 
 Posteriormente, você poderá usar o painel de administração do site e as configurações corporativas para configurar ainda mais sua empresa, gerenciar usuários, organizações e repositórios e definir políticas que reduzem o risco e aumentam a qualidade.
 
diff --git a/translations/pt-BR/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/pt-BR/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index 8e01cf5c11..01ce530ad4 100644
--- a/translations/pt-BR/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/pt-BR/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### Sobre o acesso ao shell administrativo
diff --git a/translations/pt-BR/content/admin/configuration/accessing-the-management-console.md b/translations/pt-BR/content/admin/configuration/accessing-the-management-console.md
index 6185fc4953..cbb23d4591 100644
--- a/translations/pt-BR/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/pt-BR/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Sobre o {% data variables.enterprise.management_console %}
diff --git a/translations/pt-BR/content/admin/configuration/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/command-line-utilities.md
index 727399d01a..46c2fad2a0 100644
--- a/translations/pt-BR/content/admin/configuration/command-line-utilities.md
+++ b/translations/pt-BR/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 Depois de entrar como usuário administrador com SSH, você pode executar esses comandos de qualquer lugar na VM. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)".
@@ -483,15 +485,21 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 Para exibir a carga útil total do hook, o resultado e quaisquer exceções para a entrega:
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### Clustering
 
 #### ghe-cluster-status
 
-Este utilitário permite que você gerencie o servidor distribuído {% data variables.product.prodname_pages %}.
+Verifique a saúde dos seus nós e serviços em uma implantação de clustering de {% data variables.product.prodname_ghe_server %}.
 
 ```shell
 $ ghe-cluster-status
@@ -644,14 +652,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-Este utilitário importa de Controle de versões do Team Foundation. Para obter mais informações, consulte [Importar dados de sistemas de controle de versões de terceiros](/enterprise/{}/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+Este utilitário faz a importação a partir do Controle de Versão da Fundação da Equipe (TFVC). Para obter mais informações, consulte [Importar dados de sistemas de controle de versões de terceiros](/enterprise/{}/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-Este utilitário reescreve o repositório importado. Isso lhe dá a chance de renomear os autores e, para Subversion e TFS, produz branches Git baseados em pastas. Para obter mais informações, consulte [Importar dados de sistemas de controle de versões de terceiros](/enterprise/{}/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+Este utilitário reescreve o repositório importado. Isso dá a você a oportunidade de renomear autores e, para o Subversion e TFVC, produz branches Git baseados em pastas. Para obter mais informações, consulte [Importar dados de sistemas de controle de versões de terceiros](/enterprise/{}/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-rewrite
 ```
diff --git a/translations/pt-BR/content/admin/configuration/configuring-a-hostname.md b/translations/pt-BR/content/admin/configuration/configuring-a-hostname.md
index c1d710ba58..b9964f0155 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 Se configurar um nome de host em vez de um endereço IP codificado, você poderá alterar o hardware físico em que a {% data variables.product.product_location %} é executada sem afetar os usuários ou o software cliente.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 16110b1196..95cfafa0fe 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Quando houver um servidor proxy habilitado para a {% data variables.product.product_location %}, as mensagens de saída enviadas para o {% data variables.product.prodname_ghe_server %} sairão primeiramente pelo servidor proxy, a menos que o host de destino seja adicionado como exclusão de proxy HTTP. Os tipos de mensagens de saída incluem webhooks de saída, pacotes para upload e fetch de avatares herdados. A URL do servidor proxy é o protocolo, domínio ou endereço IP e o número da porta, por exemplo: `http://127.0.0.1:8123`.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-applications.md b/translations/pt-BR/content/admin/configuration/configuring-applications.md
index a3d0ae5ed8..0b3fcd1ae9 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-applications.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Ajustar cache de imagem
diff --git a/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md
index 7f86d0c5f8..cdf9d39de1 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: Configurar backups no appliance
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: 'Como parte de um plano de recuperação de desastre, é possível proteger os dados de produção na {% data variables.product.product_location %} configurando backups automatizados.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### Sobre o {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/pt-BR/content/admin/configuration/configuring-built-in-firewall-rules.md
index 1d19b12a15..41258a7123 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Sobre o firewall da {% data variables.product.product_location %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index a309ac328b..c1134a593a 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: Configurar criptografia de dados
 intro: 'Para criptografia estática, você pode fornecer sua própria chave de criptografia para criptografar seus dados conforme as suas políticas de criptografia.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 Proporcionar um alto nível de segurança {% data variables.product.product_name %} criptografa seus dados em modo estático nos centros de dados e enquanto seus dados estão em trânsito entre as máquinas dos usuários e os centros de dados.
 
-Para criptografia em trânsito, {% data variables.product.product_name %} usa o Transport Layer Security (TLS). Para criptografia em modo estático, {% data variables.product.product_name %} fornece uma chave RSA padrão. Depois de ter inicializado a sua empresa, você pode escolher fornecer a sua própria chave. A sua chave deve ser uma chave RSA privada de 2048 bits no formato PEM.
-
-A chave que você fornecer é armazenada em um módulo de segurança de hardware compatível com o FIPS 140-2 (HSM) em um cofre de chave que {% data variables.product.company_short %} gerencia.
-
-Para configurar sua chave de criptografia, use a API REST. Existem vários pontos de extremidade da API, por exemplo, para verificar o status da criptografia, atualizar sua chave de criptografia e desabilitar sua chave de criptografia. Observe que que desabilitar a sua chave irá congelar a sua empresa. Para obter mais informações sobre os pontos de extremidade da API, consulte "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST.
-
-### Adicionar ou atualizar uma chave de criptografia
-
-Você pode adicionar uma nova chave de criptografia sempre que precisar. Ao adicionar uma chave nova, a chave antiga é descartada. A sua empresa não vai ter inatividade quando você atualizar a chave.
-
-Sua chave privada RSA de 2048 bits deve estar no formato PEM como, por exemplo, em um arquivo denominado _private-key.pem_.
-
-   ```
-   -----BEGIN RSA PRIVATE KEY-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----END RSA PRIVATE KEY-----
-   ```
-
-1. Para adicionar a sua chave, use o ponto de extremidade `PATCH /enterprise/encryption`, substituindo *~/private-key.pem* pelo caminho para sua chave privada.
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. Opcionalmente, verifique o status da operação de atualização.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### Desabilitar a sua chave de criptografia
-
-Para congelar a sua empresa, por exemplo, no caso de uma violação, você pode desabilitar a criptografia, marcando a sua chave de criptografia como desabilitada.
-
-1. Para desabilitar a sua chave e a criptografia estática, use o ponto de extremidade `DELETE /enterprise/encryption`. Esta operação não exclui a chave permanentemente.
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. Opcionalmente, verifique o status da operação de exclusão. Demora aproximadamente dez minutos para desabilitar a criptografia em repouso.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-Para descongelar a sua empresa depois de ter desabilitado a sua chave de criptografia, entre em contato com o suporte. Para obter mais informações, consulte "[Sobre o {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)".
-
-### Leia mais
-
-- "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST 
+Para criptografia em trânsito, {% data variables.product.product_name %} usa o Transport Layer Security (TLS). Para criptografia em modo estático, {% data variables.product.product_name %} fornece uma chave RSA padrão. 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-dns-nameservers.md b/translations/pt-BR/content/admin/configuration/configuring-dns-nameservers.md
index d3be2566fd..7cedc33237 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 Os servidores de nomes que você especificar devem resolver o nome de host da {% data variables.product.product_location %}.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md
index da09bf189c..96a63d0b7c 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index 331004a2fd..58c5ead513 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### Habilitar sites públicos para {% data variables.product.prodname_pages %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-rate-limits.md b/translations/pt-BR/content/admin/configuration/configuring-rate-limits.md
index 782b1fdf8f..b30c5f2bcd 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### Habilitar limites de taxa para a {% data variables.product.prodname_enterprise_api %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/pt-BR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index 9b55a2ede7..18c1fd8692 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-time-synchronization.md b/translations/pt-BR/content/admin/configuration/configuring-time-synchronization.md
index 3265bc85a2..6cfde2eb7e 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Alterar os servidores NTP padrão
diff --git a/translations/pt-BR/content/admin/configuration/configuring-tls.md b/translations/pt-BR/content/admin/configuration/configuring-tls.md
index c2b5c331db..388d886872 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-tls.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Sobre o protocolo Transport Layer Security
diff --git a/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 52f1dabc09..ee343505c0 100644
--- a/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### Sobre o {% data variables.product.prodname_github_connect %}
diff --git a/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index 65b09ef617..552454f7ba 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### Sobre alertas para dependências vulneráveis no {% data variables.product.prodname_ghe_server %}
diff --git a/translations/pt-BR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/pt-BR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index 09f63e29ca..007d212e52 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### Sobre o modo de manutenção
diff --git a/translations/pt-BR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 5e83f5dd47..1951870262 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### Sobre a sincronização de licenças
diff --git a/translations/pt-BR/content/admin/configuration/enabling-private-mode.md b/translations/pt-BR/content/admin/configuration/enabling-private-mode.md
index 55f8c07348..b29317e58d 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-private-mode.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 Você deve habilitar o modo privado se a {% data variables.product.product_location %} estiver acessível publicamente pela Internet. No modo privado, os usuários não podem clonar anonimamente repositórios em `git://`. Se a autenticação integrada também estiver habilitada, o administrador deverá convidar novos usuários para criar uma conta na instância. Para obter mais informações, consulte "[Usar autenticação integrada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)".
diff --git a/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md b/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md
index 9763e4af1e..a021074a5e 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Sobre isolamento de subdomínio
@@ -19,7 +24,7 @@ Quando o isolamento do subdomínio está ativado, o {% data variables.product.pr
 
 {% if currentVersion == "enterprise-server@2.22" %}
 Para usar o Docker com
-{% data variables.product.prodname_registry %}, você também deve habilitar o isolamento de subdomínio. Para obter mais informações, consulte "[Configurar Docker para uso com o {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)".
+{% data variables.product.prodname_registry %}, você também deve habilitar o isolamento de subdomínio. Para obter mais informações, consulte "[Trabalhando com o registro Docker](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)".
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/pt-BR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/pt-BR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index 8adf1afe65..95b1da3b18 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 Como administrador do site, você pode permitir que os usuários finais enviem as contagens de contribuição anônimas do trabalho deles no {% data variables.product.prodname_ghe_server %} pelos respectivos gráficos de contribuição no {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/pt-BR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/pt-BR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 5f06237a09..bfe9225173 100644
--- a/translations/pt-BR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/pt-BR/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 Quando você habilita a pesquisa unificada, os usuários podem ver resultados em conteúdos públicos e privados no {% data variables.product.prodname_dotcom_the_website %} quando pesquisam pela {% data variables.product.product_location_enterprise %}.
diff --git a/translations/pt-BR/content/admin/configuration/index.md b/translations/pt-BR/content/admin/configuration/index.md
index 22bcb628a6..c16318b9db 100644
--- a/translations/pt-BR/content/admin/configuration/index.md
+++ b/translations/pt-BR/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/pt-BR/content/admin/configuration/initializing-github-ae.md b/translations/pt-BR/content/admin/configuration/initializing-github-ae.md
index 4b4ee63f0a..fec9e0341a 100644
--- a/translations/pt-BR/content/admin/configuration/initializing-github-ae.md
+++ b/translations/pt-BR/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: Inicializar o GitHub AE
 intro: 'Para deixar a sua empresa pronta para uso, você pode definir a configuração inicial de {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### Sobre a inicialização
@@ -79,11 +82,11 @@ Uma vez inicializado, você poderá reconfigurar qualquer configuração após o
 1. À direita de "Definir as configurações de e-mail", clique em **Configurar**. ![Botão "Configurar" para configurações de e-mail](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. Selecione **Enable email** (Habilitar e-mail). Isto habilitará e-mails de saída e de entrada. No entanto, para que o e-mail de entrada funcione, você também deverá definir as suas configurações de DNS. Para obter mais informações, consulte "[Definir configurações de DNS e firewall para permitir e-mails recebidos](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". ![Caixa de seleção "Habilitar" para configurações de e-mail](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Defina as suas configurações de servidor de e-mail:
-  - No campo **Server address** (Endereço do servidor), digite o endereço do seu servidor SMTP.
-  - No campo **Port** (Porta), digite a porta que o servidor SMTP usa para enviar e-mails.
-  - No campo **Domain** (Domínio), digite o nome do domínio que o servidor SMTP enviará com resposta HELO, se houver.
-  - No menu suspenso **Authentication** (Autenticação), escolha o tipo de criptografia usado pelo servidor SMTP.
-  - No campo **No-reply email address** (Endereço de e-mail no-reply), digite o endereço de e-mail para usar nos campos De e Para em todos os e-mails de notificação.
+    - No campo **Server address** (Endereço do servidor), digite o endereço do seu servidor SMTP.
+    - No campo **Port** (Porta), digite a porta que o servidor SMTP usa para enviar e-mails.
+    - No campo **Domain** (Domínio), digite o nome do domínio que o servidor SMTP enviará com resposta HELO, se houver.
+    - No menu suspenso **Authentication** (Autenticação), escolha o tipo de criptografia usado pelo servidor SMTP.
+    - No campo **No-reply email address** (Endereço de e-mail no-reply), digite o endereço de e-mail para usar nos campos De e Para em todos os e-mails de notificação.
 
 4. Se você quiser descartar todos os e-mails recebidos destinados ao endereço no-reply, selecione **Discard email addressed to the no-reply email address** (Descartar e-mails recebidos no endereço no-reply). ![Caixa de seleção "Descartar" para configurações de e-mail](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. Clique em **Configurações de e-mail de teste**. ![Botão "Configurações de e-mail de teste" para configurações de e-mail](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 029c53412b..5c86508ef4 100644
--- a/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: 'Você pode decidir se usuários autenticados podem se conectar-se a {% d
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/pt-BR/content/admin/configuration/network-ports.md b/translations/pt-BR/content/admin/configuration/network-ports.md
index 8e7baac07c..4b09400b1e 100644
--- a/translations/pt-BR/content/admin/configuration/network-ports.md
+++ b/translations/pt-BR/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Abra as portas de rede seletivamente com base nos serviços que você precisa expor para administradores, usuários finais e suporte por e-mail.'
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Portas administrativas
diff --git a/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index 5bd9026b91..0ef3928f59 100644
--- a/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -4,6 +4,13 @@ shortTitle: Restringir tráfego de rede
 intro: Você pode usar um IP permitir que a lista restrinja o acesso ao seu negócio a conexões a partir de endereços IP especificados.
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### Sobre listas de permissões de IP
diff --git a/translations/pt-BR/content/admin/configuration/site-admin-dashboard.md b/translations/pt-BR/content/admin/configuration/site-admin-dashboard.md
index 797d941cb1..24ad96c75c 100644
--- a/translations/pt-BR/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/pt-BR/content/admin/configuration/site-admin-dashboard.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 Para acessar o painel, clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/pt-BR/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/pt-BR/content/admin/configuration/troubleshooting-ssl-errors.md
index ce0cf2a096..71a57f11bf 100644
--- a/translations/pt-BR/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/pt-BR/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### Remover a frase secreta do arquivo de chave
diff --git a/translations/pt-BR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/pt-BR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index 5605c6bdd4..91a0daeec4 100644
--- a/translations/pt-BR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/pt-BR/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/pt-BR/content/admin/configuration/validating-your-domain-settings.md b/translations/pt-BR/content/admin/configuration/validating-your-domain-settings.md
index cda71c286f..fb14e9210f 100644
--- a/translations/pt-BR/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/pt-BR/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/pt-BR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/pt-BR/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/pt-BR/content/admin/enterprise-management/about-cluster-nodes.md b/translations/pt-BR/content/admin/enterprise-management/about-cluster-nodes.md
index b5cc1bec5c..79a238e19c 100644
--- a/translations/pt-BR/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/pt-BR/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/about-clustering.md b/translations/pt-BR/content/admin/enterprise-management/about-clustering.md
index 977cdb1640..0671257ed5 100644
--- a/translations/pt-BR/content/admin/enterprise-management/about-clustering.md
+++ b/translations/pt-BR/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/about-geo-replication.md b/translations/pt-BR/content/admin/enterprise-management/about-geo-replication.md
index 182835b4d8..d22e313011 100644
--- a/translations/pt-BR/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/pt-BR/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 Usar várias réplicas ativas diminui a distância até a réplica mais próxima. Por exemplo, uma organização com escritórios em San Francisco, Nova York e Londres pode executar o appliance primário em um datacenter próximo a Nova York e duas réplicas em datacenters próximos a San Francisco e Londres. Ao usar um DNS compatível com localização geográfica, os usuários podem ser direcionados para o servidor mais próximo disponível e acessar os dados do repositório em menos tempo. Definir o appliance próximo a Nova York como o primário ajuda a reduzir a latência entre os hosts, em comparação a definir o appliance próximo a San Francisco como o principal, que tem maior latência para Londres.
diff --git a/translations/pt-BR/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/pt-BR/content/admin/enterprise-management/about-high-availability-configuration.md
index 1d07488bc9..fe70c7658f 100644
--- a/translations/pt-BR/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/pt-BR/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Quando você configura alta disponibilidade, há uma configuração automatizada de replicação assíncrona e unidirecional de todos os armazenamentos de dados (repositórios do Git, MySQL, Redis e Elasticsearch) do appliance primário para o appliance réplica.
diff --git a/translations/pt-BR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/pt-BR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 2556d7d063..dc9b42b9bd 100644
--- a/translations/pt-BR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/pt-BR/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Acessar o painel de monitoramento
diff --git a/translations/pt-BR/content/admin/enterprise-management/cluster-network-configuration.md b/translations/pt-BR/content/admin/enterprise-management/cluster-network-configuration.md
index 4e68c6b579..d62b3cbeb1 100644
--- a/translations/pt-BR/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/pt-BR/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### Considerações de rede
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md b/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md
index 2163128362..2e428bcd49 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Configurar um servidor externo `collectd`
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index 9915efb7a1..b88ba5b1a2 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Sobre a alta disponibilidade de replicação de clusters
@@ -22,7 +26,7 @@ Recomendamos configurar uma alta disponibilidade como parte de um plano de recup
 
 #### Hardware e software
 
-Para cada nó existente no seu cluster ativo, você precisará fornecer uma segunda máquina virtual com recursos de hardware idênticos. Por exemplo, se seu cluster tiver 11 nós e cada nó tem 12 vCPUs, 96 GB de RAM e 750 GB de armazenamento anexado, você deverá fornecer 11 novas máquinas virtuais, tendo cada uma 12 vCPUs, 64 GB de RAM e 750 GB de armazenamento anexado.
+Para cada nó existente no seu cluster ativo, você precisará fornecer uma segunda máquina virtual com recursos de hardware idênticos. Por exemplo, se seu cluster tiver 11 nós e cada nó tem 12 vCPUs, 96 GB de RAM e 750 GB de armazenamento anexado, você deverá fornecer 11 novas máquinas virtuais, tendo cada uma 12 vCPUs, 96 GB de RAM e 750 GB de armazenamento anexado.
 
 Em cada nova máquina virtual, instale a mesma versão do {% data variables.product.prodname_ghe_server %} que é executada nos nós do seu cluster ativo. Você não precisa fazer o upload de uma licença ou executar qualquer configuração adicional. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)".
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/pt-BR/content/admin/enterprise-management/creating-a-high-availability-replica.md
index e537364393..2f7a2fb92a 100644
--- a/translations/pt-BR/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/pt-BR/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/pt-BR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/pt-BR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index 5084b12429..75f935e240 100644
--- a/translations/pt-BR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/pt-BR/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Cenários de falha
diff --git a/translations/pt-BR/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/pt-BR/content/admin/enterprise-management/enabling-automatic-update-checks.md
index 38b08858a1..d277fd527e 100644
--- a/translations/pt-BR/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/pt-BR/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 Quando um pacote de atualização for baixado automaticamente para a {% data variables.product.product_location %}, você receberá uma mensagem informando que pode atualizar o {% data variables.product.prodname_ghe_server %}. Os pacotes baixados ficam no diretório `/var/lib/ghe-updates` na {% data variables.product.product_location %}. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)".
diff --git a/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md
index 80f1a6dd07..30344617a3 100644
--- a/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/pt-BR/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/pt-BR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index 298d81fd4e..634664116f 100644
--- a/translations/pt-BR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/pt-BR/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md
index e1dd543945..d0c19843f0 100644
--- a/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/pt-BR/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -31,7 +35,10 @@ topics:
 1. Redimensione o disco de volume de usuário existente usando as ferramentas da plataforma de virtualização.
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. Deixe o appliance em modo de manutenção. Para obter mais informações, consulte "[Habilitar e programar o modo de manutenção](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)".
-4. Reinicie o appliance para detectar a alocação do novo armazenamento.
+4. Reinicie o appliance para detectar a alocação do novo armazenamento:
+  ```shell
+  $ sudo reboot
+  ```
 5. Execute o comando `ghe-storage-extend` para expandir o sistema de arquivos `/data/user`:
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ topics:
 ### Aumentar o tamanho da partição de dados raiz usando um novo appliance
 
 1. Configure uma nova instância do {% data variables.product.prodname_ghe_server %} com um disco raiz maior usando a mesma versão do appliance atual. Para obter mais informações, consulte "[Configurar uma instância do {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)".
-2. Desligue o appliance atual.
+2. Desligue o appliance atual:
+  ```shell
+  $ sudo poweroff
+  ```
 3. Desvincule o disco de dados do appliance atual usando as ferramentas da plataforma de virtualização.
 4. Vincule o disco de dados ao novo appliance com o disco raiz maior.
 
@@ -57,6 +67,9 @@ topics:
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. Desligue o appliance.
+4. Desligue o appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 5. No hipervisor, remova o disco raiz antigo e vincule o novo disco raiz no mesmo local do antigo.
 6. Inicie o appliance.
diff --git a/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md b/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md
index f06fb3a2c4..b370669580 100644
--- a/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/pt-BR/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 299a267d22..df06cdbf77 100644
--- a/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 O tempo do failover dependerá do tempo necessário para promover manualmente a réplica e redirecionar o tráfego. Em média, o procedimento leva de dois a dez minutos.
diff --git a/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index 09b428dd88..56e98e47ab 100644
--- a/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Sobre failover para seu cluster de réplicas
diff --git a/translations/pt-BR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/pt-BR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index bc324c5f00..f0d0ac6723 100644
--- a/translations/pt-BR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/pt-BR/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -12,8 +12,11 @@ redirect_from:
 intro: 'Para migrar do {% data variables.product.prodname_enterprise %} 11.10.x para o 2.1.23, você precisará configurar uma nova instância do appliance e migrar os dados da instância anterior.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 Há suporte para migrações do {% data variables.product.prodname_enterprise %} 11.10.348 e mais recentes. Não há suporte para migrações do {% data variables.product.prodname_enterprise %} 11.10.348 e versões anteriores. Você deve atualizar o 11.10.348 em várias etapas de atualização. Para obter mais informações, consulte o procedimento de atualização do 11.10.348, "[Atualizar para a versão mais recente](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)".
diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md
index 698551d87f..c535109254 100644
--- a/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -6,8 +6,14 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Verificar o status do cluster manualmente
diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-using-snmp.md
index 9505ee5b48..3f38559e53 100644
--- a/translations/pt-BR/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 O SNMP é um padrão comum para monitorar dispositivos em uma rede. É altamente recomendável ativar o SNMP para monitorar a integridade da {% data variables.product.product_location %} e saber quando adicionar mais memória, armazenamento ou potência do processador à máquina host.
diff --git a/translations/pt-BR/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/pt-BR/content/admin/enterprise-management/recommended-alert-thresholds.md
index 3ac5f7eb7e..f138d51a53 100644
--- a/translations/pt-BR/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/pt-BR/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### Monitorar o armazenamento
diff --git a/translations/pt-BR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/pt-BR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index 99c2da012d..fe015de77a 100644
--- a/translations/pt-BR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/pt-BR/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 Você pode usar o appliance primário anterior como novo appliance de réplica em caso de failover planejado ou não relacionado à integridade do appliance. Se o failover estiver relacionado a um problema no appliance primário, talvez você prefira criar outro appliance de réplica. Para obter mais informações, consulte "[Criar réplica de alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)".
diff --git a/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md
index 99e08c0fa9..a300195e76 100644
--- a/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/pt-BR/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### Parar a replicação temporariamente
diff --git a/translations/pt-BR/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/pt-BR/content/admin/enterprise-management/replacing-a-cluster-node.md
index 230871cdbb..3daaceebb3 100644
--- a/translations/pt-BR/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/pt-BR/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/pt-BR/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/pt-BR/content/admin/enterprise-management/setting-up-external-monitoring.md
index 31938fcbdf..41021a6773 100644
--- a/translations/pt-BR/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/pt-BR/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Sobre o SNMP
diff --git a/translations/pt-BR/content/admin/enterprise-management/upgrade-requirements.md b/translations/pt-BR/content/admin/enterprise-management/upgrade-requirements.md
index 1c9bc07a25..261f1bbb08 100644
--- a/translations/pt-BR/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/pt-BR/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 Use o número para estimar o espaço em disco necessário para os logs de auditoria do MySQL. O script também monitora seu espaço livre em disco durante o andamento da importação. Monitorar esse número é útil principalmente se o espaço livre em disco estiver próximo da quantidade de espaço em disco necessária para a migração.
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### Próximas etapas
+
 Após ler essas recomendações e requisitos, você poderá atualizar para o {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)".
diff --git a/translations/pt-BR/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/pt-BR/content/admin/enterprise-management/upgrading-a-cluster.md
index 4be6c05c45..4640e536ee 100644
--- a/translations/pt-BR/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/pt-BR/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### Atualizar com hotpatch
diff --git a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index f6ece7cf43..2e57ee0485 100644
--- a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### Preparar para a atualização
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### Sobre os requisitos mínimos para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior
-
-Antes de atualizar para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior, revise os recursos de hardware que você forneceu para sua instância. {% data variables.product.prodname_ghe_server %} 3.0 introduz novas funcionalidades, como {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %}, e exige mais recursos do que as versões 2.22 e anteriores. Para obter mais informações, consulte as observações sobre a versão [{% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes).
-
-Os requisitos aumentados para {% data variables.product.prodname_ghe_server %} 3.0 e posterior estão em **negrito** na tabela a seguir.
-
-| Licenças de usuário                      |                         vCPUs |                               Memória |                 Armazenamento anexado | Armazenamento raiz |
-|:---------------------------------------- | -----------------------------:| -------------------------------------:| -------------------------------------:| ------------------:|
-| Teste, demonstração ou 10 usuários leves | **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up de 16 GB_ | **150 GB**<br/>_Up de 100 GB_ |             200 GB |
-| 10-3000                                  |   **8**<br/>_Up de 4_ |   **48 GB**<br/>_Up de 32 GB_ | **300 GB**<br/>_Up de 250 GB_ |             200 GB |
-| 3000-5000                                |  **12**<br/>_Up de 8_ |                                 64 GB |                                500 GB |             200 GB |
-| 5000-8000                                | **16**<br/>_Up de 12_ |                                 96 GB |                                750 GB |             200 GB |
-| 8000-10000+                              | **20**<br/>_Up de 16_ | **160 GB**<br/>_Up de 128 GB_ |                               1000 GB |             200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-Para obter mais informações sobre requisitos de hardware para {% data variables.product.prodname_actions %}, consulte "[Introdução a {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### Obter um instantâneo
 
@@ -81,7 +59,7 @@ Há dois tipos de instantâneo:
 | Hyper-V               | VM                    | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | Disco                 | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM                    | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM                    | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM                    | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### Atualizar com hotpatch
 
@@ -89,7 +67,12 @@ Há dois tipos de instantâneo:
 
 {% note %}
 
-**Observação**: A instalação de hotpatch com o {% data variables.enterprise.management_console %} não está disponível para ambientes em cluster. Para instalar um hotpatch em um ambiente em cluster, consulte "[Atualizar um cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)".
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}Observações{% else %}Note{% endif %}**:
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- Se {% data variables.product.product_location %} estiver executando a compilação de um candidato à versão, você não poderá atualizar com um hotpatch.
+
+- {% endif %}Instalando um hotpatch usando o {% data variables.enterprise.management_console %} não está disponível em ambientes com cluster. Para instalar um hotpatch em um ambiente em cluster, consulte "[Atualizar um cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)".
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md
index 3aaf6c48fa..5859e4b2c9 100644
--- a/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/pt-BR/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index f559004acb..0bf6f8edcd 100644
--- a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index caabbf8ef1..80df382495 100644
--- a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/pt-BR/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/pt-BR/content/admin/enterprise-support/about-support-for-advanced-security.md
index 5657afd42e..5886d83e73 100644
--- a/translations/pt-BR/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/pt-BR/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index 39e28ecf29..5b7bad77b0 100644
--- a/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/pt-BR/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 Antes de enviar um tíquete, você deve:
diff --git a/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md
index 40bdf756bd..d8220e65b3 100644
--- a/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/pt-BR/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Criar e compartilhar arquivos de diagnóstico
diff --git a/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md b/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md
index e0a7926aa7..8414e3264c 100644
--- a/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/pt-BR/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Usar sistemas automatizados de geração de tíquetes
diff --git a/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md b/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md
index 7285790c4c..a291c66884 100644
--- a/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/pt-BR/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Como enviar um tíquete
diff --git a/translations/pt-BR/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..8e52a360ac
--- /dev/null
+++ b/translations/pt-BR/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: Sobre como usar ações na sua empresa
+intro: '{% data variables.product.product_name %} inclui a maioria das ações de autoria de {% data variables.product.prodname_dotcom %} e tem opções para permitir o acesso a outras ações de {% data variables.product.prodname_dotcom_the_website %} e {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+Os fluxos de trabalho de {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que você pode combinar para criar tarefas e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}.
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### Ações oficiais agrupadas com a sua instância corporativa
+
+A maioria das ações oficiais de autoria de {% data variables.product.prodname_dotcom %} são automaticamente agrupadas com {% data variables.product.product_name %} e são capturadas em um momento a partir do {% data variables.product.prodname_marketplace %}.
+
+As ações oficiais empacotadas incluem `ações/checkout`, `actions/upload-artefact`, `actions/download-artefact`, `actions/labeler`, e várias ações de `actions/setup-`, entre outras. Para ver todas as ações oficiais incluídas na instância da sua empresa, acesse a organização das `ações` na sua instância: <code>https://<em>HOSTNAME</em>/actions</code>.
+
+Cada ação é um repositório na organização de `ações`, e cada repositório de ação inclui as tags necessárias, branches e commit de SHAs que seus fluxos de trabalho podem usar para fazer referência à ação. Para obter informações sobre como atualizar as ações oficiais empacotadas, consulte "[Usar a versão mais recente das ações oficiais empacotadas](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)".
+
+{% note %}
+
+**Observação:** Ao usar ações de configuração (como `actions/setup-LANGUAGE`) em {% data variables.product.product_name %} com executores auto-hospedados, você pode precisar configurar o cache de ferramentas em executores que não possuem acesso à Internet. Para obter mais informações, consulte "[Configurar o cache da ferramenta em executores auto-hospedados sem acesso à internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)".
+
+{% endnote %}
+
+### Configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %}
+
+Se os usuários da sua empresa precisam de acesso a outras ações a partir de {% data variables.product.prodname_dotcom_the_website %} ou {% data variables.product.prodname_marketplace %}, há algumas opções de configuração.
+
+A abordagem recomendada é habilitar o acesso automático para todas as ações a partir de {% data variables.product.prodname_dotcom_the_website %}. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} com {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %}
+
+Como alternativa, se você quiser ter um controle mais rigoroso sobre quais as ações que são permitidas na sua empresa, você pode fazer o download e sincronizar manualmente as ações na instância da sua empresa usando a ferramenta de `actions-sync`. Para obter mais informações, consulte "[Sincronizando ações manualmente com o {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)".
diff --git a/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index ebf9268fd7..020f1cf29d 100644
--- a/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/pt-BR/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: Backup e restauração
 intro: 'Os dados de {% data variables.product.prodname_actions %} no seu provedor de armazenamento externo não estão incluídos em backups regulares de {% data variables.product.prodname_ghe_server %} e precisam ser salvos separadamente.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index 3dd3b3488a..93480da475 100644
--- a/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/pt-BR/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: Habilitar o acesso automático às ações do GitHub.com usando o GitHub Connect
-intro: 'Para permitir que o {% data variables.product.prodname_actions %} na instância corporativa use ações do {% data variables.product.prodname_dotcom_the_website %}, você pode conectar o {% data variables.product.product_location_enterprise %} ao {% data variables.product.prodname_ghe_cloud %}.'
+intro: 'Para permitir que {% data variables.product.prodname_actions %} na sua empresa use ações a partir de {% data variables.product.prodname_dotcom_the_website %}, você pode conectar a sua instância corporativa a {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} não podem usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %} ou [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} em {% data variables.product.product_name %} não podem usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %} ou [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-Para tornar todas as ações de {% data variables.product.prodname_dotcom_the_website %} disponíveis na sua instância corporativa, você pode usar {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}. Para conhecer outras formas de acessar ações a partir de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre ações em {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server).
+Para tornar todas as ações de {% data variables.product.prodname_dotcom_the_website %} disponíveis na sua instância corporativa, você pode usar {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} a {% data variables.product.prodname_ghe_cloud %}. Para saber outras formas de acessar ações a partir da {% data variables.product.prodname_dotcom_the_website %}, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
 
 ### Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %}
 
-Antes de permitir o acesso a todas as ações de {% data variables.product.prodname_dotcom_the_website %} em {% data variables.product.product_location_enterprise %}, você deve conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)".
+Antes de habilitar o acesso a todas as ações de {% data variables.product.prodname_dotcom_the_website %} na sua instância corporativa, você deve conectar sua empresa a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index 4e3e7e633c..15c6fa6e0d 100644
--- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos:
 
-* Crie seu bucket do Amazon S3 para armazenar artefatos gerados pelas execuções do fluxo de trabalho. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Crie seu bucket do Amazon S3 para armazenar artefatos gerados pelas execuções do fluxo de trabalho. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index 9eabff8d0b..629b1d99b9 100644
--- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos:
 
 * Para evitar contenção de recursos no dispositivo, recomendamos que o MinIO seja hospedado separadamente de {% data variables.product.product_location %}.
-* Crie seu bucket para armazenar artefatos de fluxo de trabalho. Para configurar seu bucket e chave de acesso, consulte a [Documentação do MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Crie seu bucket para armazenar artefatos de fluxo de trabalho. Para configurar seu bucket e chave de acesso, consulte a [Documentação do MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 83eefd7e02..fed6881d68 100644
--- a/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index f9fc2a824d..45af450418 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: Introdução ao GitHub Actions para GitHub AE
+shortTitle: Indrodução ao GitHub Actions
 intro: 'Aprenda a configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index c3233c9d60..e99f3d91a7 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,5 +1,6 @@
 ---
 title: Primeiros passos com o GitHub Actions para o GitHub Enterprise Server
+shortTitle: Indrodução ao GitHub Actions
 intro: 'Saiba mais sobre como habilitar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} pela primeira vez.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
@@ -7,7 +8,9 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
+  - Actions
   - Enterprise
 ---
 
@@ -116,7 +119,7 @@ Para executar fluxos de trabalho de {% data variables.product.prodname_actions %
 
 Você pode controlar quais ações os usuários têm permissão para usar na sua empresa. Isso inclui a configuração de {% data variables.product.prodname_github_connect %} para acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %}, ou a sincronização manual das ações de {% data variables.product.prodname_dotcom_the_website %}.
 
-Para obter mais informações, consulte "[Sobre o uso de ações em {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)".
+Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
 
 ### Fortalecimento geral de segurança para {% data variables.product.prodname_actions %}
 
diff --git a/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md b/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md
index 04d8aa2be7..d6658b989e 100644
--- a/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/pt-BR/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: Alta disponibilidade para o GitHub Actions
 intro: 'Há algumas considerações especiais para administrar {% data variables.product.prodname_actions %} em uma configuração de alta disponibilidade.'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### Replicação ou redundância dos seus dados de {% data variables.product.prodname_actions %}
diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md
index f5c2b82dba..0ef2e17e89 100644
--- a/translations/pt-BR/content/admin/github-actions/index.md
+++ b/translations/pt-BR/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index abcb371faa..89ed5f8754 100644
--- a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: Sincronização manual de ações do GitHub.com
-intro: 'Para usuários que precisam acessar ações a partir de {% data variables.product.prodname_dotcom_the_website %}, você pode sincronizar ações específicas para sua instância do {% data variables.product.prodname_ghe_server %}.'
+intro: 'Para usuários que precisam acessar as ações a partir de {% data variables.product.prodname_dotcom_the_website %}, você pode sincronizar ações específicas para sua empresa.'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} com {% data variables.product.prodname_ghe_cloud %} . Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-No entanto, se você quer ter um controle mais rigoroso sobre quais as ações permitidas na sua empresa, você pode seguir esse guia para usar a ferramenta de código aberto de {% data variables.product.company_short %}de [`actions-sync`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} com sua instância corporativa.
+No entanto, se você quer ter um controle mais rigoroso sobre quais as ações permitidas na sua empresa, você pode seguir esse guia para usar a ferramenta de código aberto de {% data variables.product.company_short %}de [`actions-sync`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} da sua empresa.
 
 ### Sobre a ferramenta `actions-sync`
 
-A ferramenta `actions-sync` deve ser executada em uma máquina que pode acessar a API de {% data variables.product.prodname_dotcom_the_website %} e sua API da instância do {% data variables.product.prodname_ghe_server %}. A máquina não precisa estar conectada a ambos ao mesmo tempo.
+A ferramenta `actions-sync` deve ser executada em uma máquina que pode acessar a API de {% data variables.product.prodname_dotcom_the_website %} e sua API da instância do {% data variables.product.product_name %}. A máquina não precisa estar conectada a ambos ao mesmo tempo.
 
 Se sua máquina tiver acesso aos dois sistemas ao mesmo tempo, você poderá fazer a sincronização com um único comando de `actions-sync`. Se você só puder acessar um sistema de cada vez, pode usar os comandos `actions-sync pull` e `push`.
 
@@ -29,17 +30,17 @@ A ferramenta `actions-sync` só pode fazer download de ações de {% data variab
 
 ### Pré-requisitos
 
-* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino já existam na instância corporativa. O exemplo a seguir demonstra como sincronizar ações com uma organização denominada `synced-actions` em uma instância corporativa. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
-* Você deve criar um token de acesso pessoal (PAT) na instância corporativa que pode criar e gravar em repositórios nas organizações de destino. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
-* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
+* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino existem na sua empresa. O exemplo a seguir demonstra como sincronizar ações com uma organização com o nome de `synced-actions`. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
+* Você deve criar um token de acesso pessoal (PAT) na sua empresa que pode criar e gravar em repositórios nas organizações de destino. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
+* Se você deseja sincronizar as ações empacotadas na organização das `ações` em {% data variables.product.product_location %}, você deverá ser proprietário da organização das `ações`.
 
   {% note %}
 
-  **Note:** By default, even site administrators are not owners of the bundled `actions` organization.
+  **Observação:** Por padrão, até os administradores do site não são proprietários das ações agrupadas ``.
 
   {% endnote %}
 
-  Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)."
+  Os administradores dos sites podem usar o comando `ghe-org-admin-promote` no shell administrativo para promover um usuário para ser proprietários da organização das `ações` empacotadas. Para obter mais informações, consulte "[Acessar o shell administrativa (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)".
 
   ```shell
   ghe-org-admin-promote -u <em>USERNAME</em> -o actions
@@ -51,7 +52,7 @@ Este exemplo demonstra o uso da ferramenta de `actions-sync` para sincronizar um
 
 {% note %}
 
-**Observação:** Este exemplo usa o comando `actions-sync`, que exige acesso simultâneo à API do {% data variables.product.prodname_dotcom_the_website %} e à API da instância do {% data variables.product.prodname_ghe_server %} a partir da sua máquina. Se você só puder acessar um sistema de cada vez, pode usar os comandos `actions-sync pull` e `push`. Para obter mais informações, consulte o README de [`actions-sync`](https://github.com/actions/actions-sync#not-connected-instances).
+**Observação:** Este exemplo usa o comando `actions-sync`, que requer acesso simultâneo à API de {% data variables.product.prodname_dotcom_the_website %} e à API da instância empresarial a partir da sua máquina. Se você só puder acessar um sistema de cada vez, pode usar os comandos `actions-sync pull` e `push`. Para obter mais informações, consulte o README de [`actions-sync`](https://github.com/actions/actions-sync#not-connected-instances).
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ Este exemplo demonstra o uso da ferramenta de `actions-sync` para sincronizar um
    * `--destination-url`: A URL da instância empresarial de destino.
    * `--repo-name`: O repositório da ação a ser sincronizado. Ele aceita o formato de `owner/repository:destination_owner/destination_repository`.
 
-     * O exemplo acima sincroniza o repositório [`docker/build-push-action`](https://github.com/docker/build-push-action) com o repositório `synced-actions/docker-build-push-action` na instância de destino de {% data variables.product.prodname_ghe_server %}. Você deve criar a organização denominada `synced-actions` na instância da empresa antes de executar o comando acima.
-     * Se você omitir `:destination_owner/destination_repository`, a ferramenta usará o proprietário original e o nome do repositório para a instância corporativa. Antes de executar o comando, você deve criar uma nova organização na sua instância que corresponde ao nome do proprietário da ação. Considere usar uma organização central para armazenar as ações sincronizadas na sua instância, já que isso significa que você não precisará criar várias novas organizações se sincronizar ações de diferentes proprietários.
+     * O exemplo acima sincroniza o repositório [`docker/build-push-action`](https://github.com/docker/build-push-action) com o repositório `sincronizado-actions/docker-build-push-action` na instância corporativa de destino. Você deve criar a organização denominada `synced-actions` na sua empresa antes de executar o comando acima.
+     * Se você omitir `:destination_owner/destination_repository`, a ferramenta usará o proprietário original e o nome do repositório para a sua empresa. Antes de executar o comando, você deve criar uma nova organização em sua empresa que corresponda ao nome da ação do proprietário. Considere usar uma organização central para armazenar as ações sincronizadas na sua empresa, uma vez que isso significa que você não precisará criar várias novas organizações se sincronizar ações de diferentes proprietários.
      * Você pode sincronizar várias ações substituindo o parâmetro `--repo-name` por `--repo-name-list` ou `--repo-name-list-file`. Para obter mais informações, consulte o README de [`actions-sync`](https://github.com/actions/actions-sync#actions-sync).
-1. Depois que o repositório de ação é criada na instância corporativa, as pessoas da sua empresa podem usar o repositório de destino para fazer referência à ação nos fluxos de trabalho. Para o exemplo da ação mostrado acima:
+1. Depois que o repositório de ação for criado na sua empresa, as pessoas da sua empresa poderão usar o repositório de destino para fazer referência à ação nos fluxos de trabalho. Para o exemplo da ação mostrado acima:
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/pt-BR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/pt-BR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index ffd10c8a48..01d2f11565 100644
--- a/translations/pt-BR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/pt-BR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### Sobre as ações de configuração incluídas e o cache da ferramenta do executor
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-As maioria das oficiais de autoria de {% data variables.product.prodname_dotcom %}mais são automaticamente agrupadas com {% data variables.product.prodname_ghe_server %}. No entanto, os executores auto-hospedados sem acesso à internet precisarão de alguma configuração antes de poderem usar as ações `actions/setup-LANGUAGE` inclusas como, por exemplo, `setup-node`.
+As maioria das oficiais de autoria de {% data variables.product.prodname_dotcom %}mais são automaticamente agrupadas com {% data variables.product.product_name %}. No entanto, os executores auto-hospedados sem acesso à internet precisarão de alguma configuração antes de poder usar as ações `actions/setup-LANGUAGE` inclusas como, por exemplo, `setup-node`.
 
 As ações `actions/setup-LANGUAGE` normalmente precisam de acesso à internet para fazer o download os binários do ambiente necessário para o cache de ferramentas do executor. Os executores auto-hospedados sem acesso à internet não podem fazer o download dos binários. Portanto, você deve preencher manualmente o cache de ferramentas no executor.
 
diff --git a/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md b/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md
index d9d3c4fe8d..4a7af798ab 100644
--- a/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/pt-BR/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: Usar um ambiente de preparo
 intro: 'Aprenda a usar {% data variables.product.prodname_actions %} com ambientes de preparo de {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 Pode ser útil ter um ambiente de preparo ou de teste para {% data variables.product.product_location %} para que você possa testar atualizações ou novas funcionalidades antes de implementá-las no seu ambiente de produção.
diff --git a/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 232e3c0a12..a387719dc1 100644
--- a/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
 title: Usar a versão mais recente das ações agrupadas oficialmente
-intro: 'Você pode atualizar as ações que estão empacotadas com sua instância de {% data variables.product.prodname_ghe_server %} ou usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %}.'
+intro: 'Você pode atualizar as ações que estão empacotadas com a sua empresa ou usar ações diretamente a partir de {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-A sua instância de {% data variables.product.prodname_ghe_server %} inclui uma série de ações integradas que você pode usar nos seus fluxos de trabalho. Para obter mais informações sobre as ações agrupadas, consulte ["Ações oficiais agrupadas com {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+A instância da sua empresa inclui uma série de ações integradas que podem ser usadas nos seus fluxos de trabalho. Para obter mais informações sobre as ações agrupadas, consulte "[Ações oficiais agrupadas com a sua instância corporativa](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)".
 
-Essas ações agrupadas são um instantâneo no momento das ações oficiais encontradas em https://github.com/actions; como resultado, essas ações podem ser versões anteriores que podem ser atualizadas. Para atualizar estas ações, você pode usar `actions-sync` para recuperar versões atualizadas de {% data variables.product.prodname_dotcom_the_website %}.
+Essas ações empacotadas são um instantâneo no momento das ações oficiais encontradas em https://github.com/actions. Portanto, pode haver versões mais recentes dessas ações disponíveis. Você pode usar a ferramenta de `actions-sync` para atualizar essas ações ou você pode configurar {% data variables.product.prodname_github_connect %} para permitir o acesso às últimas ações em {% data variables.product.prodname_dotcom_the_website %}. Estas opções são descritas nas seguintes seções.
 
-Como alternativa, se sua instância do {% data variables.product.prodname_ghe_server %} tiver {% data variables.product.prodname_github_connect %} habilitado, você terá opções adicionais para usar as últimas ações de {% data variables.product.prodname_dotcom_the_website %}:
+### Usar `actions-sync` para atualizar as ações empacotadas
 
-- O seu arquivo de fluxo de trabalho pode referir-se diretamente a uma tag específica que só existe em {% data variables.product.prodname_dotcom_the_website %}.
-- Para forçar o arquivo do fluxo de trabalho a usar as ações em {% data variables.product.prodname_dotcom_the_website %}, você poderá editar a tag atribuída às ações agrupadas.
+Para atualizar as ações agrupadas, você pode usar a ferramenta `actions-sync` para atualizar o instantâneo. Para obter mais informações sobre como usar `actions-sync`, consulte "[Sincronizar as ações manualmente de {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)".
 
-Estas opções são descritas com mais detalhes nas seções a seguir.
+### Usar {% data variables.product.prodname_github_connect %} para acessar as últimas ações
 
-### Usar sincronismo de ações para atualizar uma ação empacotada
+Você pode usar {% data variables.product.prodname_github_connect %} para permitir que {% data variables.product.product_name %} use ações a partir do {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-Para atualizar as ações agrupadas, você poderá usar a ferramenta de `actions-sync` para sincronizar as ações com {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre como usar `actions-sync`, consulte "[Sincronizar as ações manualmente de {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)".
+Uma vez configurado {% data variables.product.prodname_github_connect %}, você poderá usar a última versão de uma ação, excluindo seu repositório local nas `ações` da organização na sua instância. Por exemplo, se a instância corporativa estiver usando a ação `actions/checkout@v1`, e você precisar usar `actions/checkout@v2` que não estão disponíveis na sua instância corporativa, por exemplo, siga as etapas a seguir para poder usar a última ação de `checkout` de {% data variables.product.prodname_dotcom_the_website %}:
 
-### Usar as ações de {% data variables.product.prodname_dotcom_the_website %}
+1. Por padrão, os administradores do site não são proprietários da organização de ações agrupadas. Para obter o acesso necessário para excluir o repositório </code>checkout`, use o comando<code>ghe-org-admin-promote` para promover um usuário a proprietário da organização das `ações` empacotadas. Para obter mais informações, consulte "[Acessar o shell administrativa (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)". Por exemplo:
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Uma vez configurado, você poderá usar uma nova versão de uma ação a partir de {% data variables.product.prodname_dotcom_the_website %}, especificando, manualmente, a versão necessária no arquivo de fluxo de trabalho. Por exemplo, para usar a versão `v2.2.` de `actions/setup-python` de {% data variables.product.prodname_dotcom_the_website %}, você pode especificar a tag `actions/setup-python@v2.2.1` no seu arquivo de fluxo de trabalho.
-
-### Usar a versão mais recente removendo a tag da ação específica
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Se você remover a tag de versão que foi atribuída anteriormente a uma ação, {% data variables.product.prodname_ghe_server %} verificará {% data variables.product.prodname_dotcom_the_website %} com relação à tag necessária. Para obter mais informações sobre como trabalhar com tags, consulte "[Visualizar tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)".
-
-Por exemplo, para usar a versão `v2.2.1` de `actions/setup-python` de {% data variables.product.prodname_dotcom_the_website %}:
-
-1. Em {% data variables.product.prodname_ghe_server %}, exclua a tag `v2` do repositório `actions/setup-python`.
-1. Crie um fluxo de trabalho que usa `actions/setup-python` com a tag `v2`.
-
-Quando o fluxo de trabalho não consegue encontrar a tag `v2` especificada no {% data variables.product.prodname_ghe_server %}, ele irá verificar a tag necessária de {% data variables.product.prodname_dotcom_the_website %} Se encontrar uma versão com tag dessa ação, {% data variables.product.prodname_ghe_server %} usará a versão de {% data variables.product.prodname_dotcom_the_website %}.
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. Na sua instância {% data variables.product.product_name %}, exclua o repositório `checkout` dentro da organização de `ações`. Para obter informações sobre como excluir um repositório, consulte "[Excluir um repositório ](/github/administering-a-repository/deleting-a-repository)".
+1. É recomendável que você deixe as `ações` da organização uma vez que não necessite mais de acesso administrativo. Para obter mais informações, consulte "[Remover-se de uma organização ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)".
+1. Configure o YAML do seu fluxo de trabalho para usar `ações/checkout@v2`.
+1. Cada vez que o seu fluxo de trabalho é executado, o executor usará a versão `v2` de `actions/checkout` de {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/pt-BR/content/admin/guides.md b/translations/pt-BR/content/admin/guides.md
new file mode 100644
index 0000000000..30e321c222
--- /dev/null
+++ b/translations/pt-BR/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: Guias do GitHub Enterprise
+shortTitle: Guias
+intro: 'Aprenda a aumentar a produtividade do desenvolvedor e a qualidade do código com {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md
index 79ad7e1837..1a5dc6c922 100644
--- a/translations/pt-BR/content/admin/index.md
+++ b/translations/pt-BR/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: Administradores da Empresa
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
+title: Documentação do GitHub Enterprise
+shortTitle: GitHub Enterprise
 intro: 'Documentação e guias para administradores da empresa, administradores de sistema e especialistas em segurança que {% if enterpriseServerVersions contains currentVersion %}implementam, {% endif %}configuram{% if enterpriseServerVersions contains currentVersion %},{% endif %} e gerenciam {% data variables.product.product_name %}.'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/pt-BR/content/admin/installation/index.md b/translations/pt-BR/content/admin/installation/index.md
index d68683162d..9726d20a01 100644
--- a/translations/pt-BR/content/admin/installation/index.md
+++ b/translations/pt-BR/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 Para obter mais informações ou comprar o {% data variables.product.prodname_enterprise %}, consulte [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md b/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md
index b3266ef889..621d85ebef 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/pt-BR/content/admin/overview/about-data-residency.md b/translations/pt-BR/content/admin/overview/about-data-residency.md
index ba853922eb..7a3e01734e 100644
--- a/translations/pt-BR/content/admin/overview/about-data-residency.md
+++ b/translations/pt-BR/content/admin/overview/about-data-residency.md
@@ -3,6 +3,10 @@ title: Sobre a residência de dados
 intro: 'Você pode escolher a localidade onde {% data variables.product.product_name %} armazena todos os dados de clientes da sua empresa.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %} Você pode escolher a localidade onde você armazena todos os dados do cliente para {% data variables.product.product_location %}, e os integrantes da sua empresa poderão acessar {% data variables.product.product_name %} de qualquer lugar do mundo.
diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
index 4b5b3b8320..d4ed69ff45 100644
--- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
@@ -7,8 +7,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
+type: overview
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### Sobre as contas corporativas do {% data variables.product.product_name %}
diff --git a/translations/pt-BR/content/admin/overview/about-github-ae.md b/translations/pt-BR/content/admin/overview/about-github-ae.md
index 96b8e1f155..ccc0a26470 100644
--- a/translations/pt-BR/content/admin/overview/about-github-ae.md
+++ b/translations/pt-BR/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: Sobre o GitHub AE
 intro: '{% data variables.product.prodname_ghe_managed %} é uma forma de segurança aprimorada e compatível de usar {% data variables.product.prodname_dotcom %} na nuvem.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### Sobre o {% data variables.product.prodname_ghe_managed %}
@@ -21,7 +25,7 @@ Todos os seus dados são armazenados na região geográfica da sua escolha. Voc
 
 ### Criptografia conforme as suas condições
 
-Todos os dados do cliente serão criptografados de forma estática e você pode fornecer a sua própria chave de criptografia para criptografar seus dados com base nos termos das suas políticas de criptografia. Você controla sua chave e o acesso a todos os seus dados. Para obter mais informações, consulte "[Configurar a criptografia de dados para sua empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)".
+Todos os dados do cliente são criptografados em repouso. Para obter mais informações, consulte "[Configurar a criptografia de dados para sua empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)".
 
 ### Contas isoladas
 
diff --git a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md
index b009d0d905..61d7669262 100644
--- a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,8 +5,10 @@ intro: '{% if currentVersion == "github-ae@latest" %}A sua empresa de {% data va
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_name %} está constantemente melhorando, com novas funcionalidades e correções de erros introduzidas por meio de versões maiores e menores. {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} é um serviço totalmente gerenciado. Portanto, {% data variables.product.company_short %} conclui o processo de atualização da sua empresa.{% endif %}
diff --git a/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md
index 300d8b8bf7..605e85386d 100644
--- a/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ Por exemplo, aqui estão os custos para os usuários com licenças em datas dife
 | Usuário   | Datas de licença                                                   | Dias contados | Custo   |
 | --------- | ------------------------------------------------------------------ | ------------- | ------- |
 | @octocat  | 1 de Janeiro - 31 de Janeiro                                       | 31            | $ 39    |
-| @robocat  | 1 de fevereiro - 28 de fevereiro                                   | 29            | $ 35,23 |
+| @robocat  | 1 de fevereiro - 28 de fevereiro                                   | 28            | $ 35,23 |
 | @devtocat | 15 de Janeiro - 31 de Janeiro                                      | 17            | $ 21,39 |
 | @doctocat | 1 de Janeiro - 15 de Janeiro                                       | 31            | $ 39    |
 | @prodocat | 7 de Janeiro - 15 de Janeiro                                       | 25            | $ 31,45 |
 | @monalisa | 1 de janeiro - 7 de janeiro<br>15 de janeiro - 31 de janeiro | 31            | $ 39    |
 
-A sua empresa pode incluir uma ou mais instâncias. {% data variables.product.prodname_ghe_managed %} tem uma instância mínima de 500 usuários. {% data variables.product.company_short %} cobra de você um mínimo de 500 usuários por instância, mesmo que haja menos de 500 usuários com uma licença nesse dia.
+{% data variables.product.prodname_ghe_managed %} tem uma instância mínima de 500 usuários. {% data variables.product.company_short %} cobra de você um mínimo de 500 usuários por instância, mesmo que haja menos de 500 usuários com uma licença nesse dia.
 
 Você pode ver seu uso atual no seu [Portal da conta do Azure](https://portal.azure.com).
 
diff --git a/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md b/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md
index 2345851fe4..b5424f1a23 100644
--- a/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/pt-BR/content/admin/overview/managing-your-github-enterprise-license.md
@@ -82,7 +82,7 @@ Caso queira renovar ou adicionar licenças de usuário com o {% data variables.p
 
 3. Na barra lateral esquerda, clique em **Enterprise licensing** (Licenciamento Empresarial). ![Aba "Licenciamento empresarial" na barra lateral de configurações da conta corporativa](/assets/images/help/enterprises/enterprise-licensing-tab.png)
 
-4. Revise sua licença atual de {% data variables.product.prodname_enterprise %}, bem como licenças de usuário consumidas e disponíveis.
+4. Revise sua licença atual de {% data variables.product.prodname_enterprise %}, bem como licenças de usuário consumidas e disponíveis. {% if currentVersion ver_gt "enterprise-server@3.0" %}Se sua licença inclui {% data variables.product.prodname_GH_advanced_security %}, você pode rever o uso total das suas estações e uma discriminação por organização de commiters. Para obter mais informações, consulte "[Gerenciar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security)".{% endif %}
 
 
 
diff --git a/translations/pt-BR/content/admin/overview/system-overview.md b/translations/pt-BR/content/admin/overview/system-overview.md
index fc38db0b15..c6afb1406c 100644
--- a/translations/pt-BR/content/admin/overview/system-overview.md
+++ b/translations/pt-BR/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### Arquitetura de armazenamento
diff --git a/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index fd56b022e9..ca1c0729f8 100644
--- a/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 80160e9ca0..6d13c36b03 100644
--- a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: Primeiros passos com o GitHub Packages para a sua empresa
+shortTitle: Getting started with GitHub Packages
 intro: 'Você pode começar a usar {% data variables.product.prodname_registry %} em {% data variables.product.product_location %} habilitando o recurso, configurando armazenamento de terceiros, configurando os ecossistemas que você deseja que sejam compatíveis e atualizando seu certificado TLS.'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index 4aca895af8..024a1fea8b 100644
--- a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: Guia de início rápido para configurar o seu bucket de armazenamento de
 intro: 'Configure seu bucket de armazenamento do MinIO personalizado para uso com {% data variables.product.prodname_registry %}.'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/pt-BR/content/admin/policies/about-pre-receive-hooks.md b/translations/pt-BR/content/admin/policies/about-pre-receive-hooks.md
index 445c831329..397b012445 100644
--- a/translations/pt-BR/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/pt-BR/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Quando ocorre um push, cada script é executado em um ambiente isolado e pode executar verificações no conteúdo do push. Os scripts farão o push ser aceito se o status de saída for 0, ou farão o push ser rejeitado se o status de saída for diferente de zero.
diff --git a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md
index b0e30262fb..f81f6755f7 100644
--- a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Um ambiente pre-receive para o {% data variables.product.prodname_ghe_server %} é um ambiente Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot). Como são executados em todos os eventos de push, os hooks pre-receive devem ser rápidos e leves. Em geral, o ambiente necessário para tais verificações é mínimo.
diff --git a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md
index a3722cc7b9..b17e0b1134 100644
--- a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 Veja exemplos de hooks pre-receive para o {% data variables.product.prodname_ghe_server %} no repositório  [`github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks).
@@ -91,32 +94,32 @@ A variável `$GITHUB_VIA` está disponível no ambiente de pre-receive quando a
 | <pre>pull request branch undo button</pre> | Restauração de um branch de tópico de um pull request na interface web                                                                                                    | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)"                |
 | <pre>pull request merge api</pre> | Merge de um pull request através da API                                                                                                                                   | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" na documentação da API REST                                                                                                        |
 | <pre>pull request merge button</pre> | Merge de um pull request na interface web                                                                                                                                 | "[Fazer merge de uma pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)"                                         |
-| <pre>pull request revert button</pre> | Revert of a pull request                                                                                                                                                  | "[Reverter uma pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)"                                                                              |
-| <pre>releases delete button</pre> | Deletion of a release                                                                                                                                                     | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)"                                                         |
-| <pre>stafftools branch restore</pre> | Restoration of a branch from the site admin dashboard                                                                                                                     | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)"                                                                                                         |
-| <pre>tag create api</pre> | Creation of a tag via the API                                                                                                                                             | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation                                                                                                  |
-| <pre>slumlord (#<em>SHA</em>)</pre> | Commit via Subversion                                                                                                                                                     | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)"                                                |
-| <pre>web branch create</pre> | Creation of a branch via the web interface                                                                                                                                | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)"      |
+| <pre>pull request revert button</pre> | Reverter um pull request                                                                                                                                                  | "[Reverter uma pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)"                                                                              |
+| <pre>releases delete button</pre> | Exclusão de uma versão                                                                                                                                                    | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)"                                                         |
+| <pre>stafftools branch restore</pre> | Restauração de um branch do painel de administração do site                                                                                                               | "[Painel de administração do site](/admin/configuration/site-admin-dashboard#repositories)"                                                                                              |
+| <pre>tag create api</pre> | Criação de uma tag através da API                                                                                                                                         | "[Banco de dados Git](/rest/reference/git#create-a-tag-object)" na documentação da API REST                                                                                              |
+| <pre>slumlord (#<em>SHA</em>)</pre> | Commit por meio do Subversion                                                                                                                                             | "[Compatibilidade para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)"                                   |
+| <pre>web branch create</pre> | Criação de um branch através da interface web                                                                                                                             | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)"      |
 
 ##### Disponível para merge de pull request
 
-The following variables are available in the pre-receive hook environment when the push that triggers the hook is a push due to the merge of a pull request.
+As variáveis a seguir estão disponíveis no ambiente de hook pre-receive quando o push que aciona o hook é um push devido ao merge de um pull request.
 
-| Variável                   | Descrição                                                                    | Valor de exemplo             |
-|:-------------------------- |:---------------------------------------------------------------------------- |:---------------------------- |
-| <pre>$GITHUB_PULL_REQUEST_AUTHOR_LOGIN</pre> | Username of account that authored the pull request                           | octocat                      |
-| <pre>$GITHUB_PULL_REQUEST_HEAD</pre> | The name of the pull request's topic branch, in the format `USERNAME:BRANCH` | <nobr>octocat:fix-bug</nobr> |
-| <pre>$GITHUB_PULL_REQUEST_BASE</pre> | The name of the pull request's base branch, in the format `USERNAME:BRANCH`  | octocat:main                 |
+| Variável                   | Descrição                                                                | Valor de exemplo             |
+|:-------------------------- |:------------------------------------------------------------------------ |:---------------------------- |
+| <pre>$GITHUB_PULL_REQUEST_AUTHOR_LOGIN</pre> | Nome de usuário da conta que criou o pull request                        | octocat                      |
+| <pre>$GITHUB_PULL_REQUEST_HEAD</pre> | O nome do branch de tópico do pull request, no formato `USERNAME:BRANCH` | <nobr>octocat:fix-bug</nobr> |
+| <pre>$GITHUB_PULL_REQUEST_BASE</pre> | O nome do branch de base do pull request no formato `USERNAME:BRANCH`    | octocat:main                 |
 
 ##### Disponível para pushes que usam autenticação SSH
 
-| Variável                   | Descrição                                                      | Valor de exemplo                                |
-|:-------------------------- |:-------------------------------------------------------------- |:----------------------------------------------- |
-| <pre>$GITHUB_PUBLIC_KEY_FINGERPRINT</pre> | The public key fingerprint for the user who pushed the changes | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 |
+| Variável                   | Descrição                                                                       | Valor de exemplo                                |
+|:-------------------------- |:------------------------------------------------------------------------------- |:----------------------------------------------- |
+| <pre>$GITHUB_PUBLIC_KEY_FINGERPRINT</pre> | A impressão digital da chave pública para o usuário que fez push das alterações | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 |
 
 ### Configurar permissões e fazer push de um hook pre-receive para o {% data variables.product.prodname_ghe_server %}
 
-A pre-receive hook script is contained in a repository on {% data variables.product.product_location %}. O administrador do site deve considerar as permissões do repositório e garantir que somente os usuários adequados tenham acesso.
+Um script de hook pre-receive está contido em um repositório em {% data variables.product.product_location %}. O administrador do site deve considerar as permissões do repositório e garantir que somente os usuários adequados tenham acesso.
 
 Recomendamos consolidar os hooks em um único repositório. Se o repositório consolidado do hook for público, será possível usar `README.md` para explicar a execução das políticas. Além disso, é possível aceitar contribuições via pull request. No entanto, os hooks pre-receive só podem ser adicionados pelo branch padrão. Em fluxos de trabalho de teste, devem ser usados forks do repositório com a devida configuração.
 
@@ -131,7 +134,7 @@ Recomendamos consolidar os hooks em um único repositório. Se o repositório co
    git update-index --chmod=+x <em>SCRIPT_FILE.sh</em>
    ```
 
-2. Commit and push to the designated repository for pre-receive hooks on {% data variables.product.product_location %}.
+2. Faça o commit e push para o repositório designado para os hooks pre-receive em {% data variables.product.product_location %}.
 
    ```shell
    $ git commit -m "<em>YOUR COMMIT MESSAGE</em>"
@@ -141,7 +144,7 @@ Recomendamos consolidar os hooks em um único repositório. Se o repositório co
 3. [Crie o hook pre-receive](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) na instância do {% data variables.product.prodname_ghe_server %}.
 
 ### Testar scripts pre-receive no local
-You can test a pre-receive hook script locally before you create or update it on {% data variables.product.product_location %}. Uma forma de fazer isso é criar um ambiente Docker local para funcionar como repositório remoto que pode executar o hook pre-receive.
+Você pode testar um script do hook pre-receive localmente antes de criá-lo ou atualizá-lo em {% data variables.product.product_location %}. Uma forma de fazer isso é criar um ambiente Docker local para funcionar como repositório remoto que pode executar o hook pre-receive.
 
 {% data reusables.linux.ensure-docker %}
 
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index 3c243debcc..0805f2a156 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,13 +5,20 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### Sobre o {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
-### Enforcing a policy for {% data variables.product.prodname_advanced_security %} features
+### Aplicar uma política para funcionalidades de {% data variables.product.prodname_advanced_security %}
 
 {% data reusables.advanced-security.about-ghas-organization-policy %}
 
diff --git a/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index ba80b0791f..d7a8b27a90 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Configurar a visibilidade padrão de novos repositórios na sua empresa
diff --git a/translations/pt-BR/content/admin/policies/index.md b/translations/pt-BR/content/admin/policies/index.md
index d350e06ca1..129ca0fc75 100644
--- a/translations/pt-BR/content/admin/policies/index.md
+++ b/translations/pt-BR/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/pt-BR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/pt-BR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 06600f7ba7..df643b3c4e 100644
--- a/translations/pt-BR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/pt-BR/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### Criar hooks pre-receive
diff --git a/translations/pt-BR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/pt-BR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..1348cc49a6
--- /dev/null
+++ b/translations/pt-BR/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Sobre restrições de e-mail para a sua conta corporativa
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restringir notificações de e-mail para a conta corporativa
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/pt-BR/content/admin/release-notes.md b/translations/pt-BR/content/admin/release-notes.md
index 75a6e125cf..a919e5dc33 100644
--- a/translations/pt-BR/content/admin/release-notes.md
+++ b/translations/pt-BR/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/pt-BR/content/admin/user-management/about-migrations.md b/translations/pt-BR/content/admin/user-management/about-migrations.md
index acc2155ee4..0122e1650d 100644
--- a/translations/pt-BR/content/admin/user-management/about-migrations.md
+++ b/translations/pt-BR/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Tipos de migração
diff --git a/translations/pt-BR/content/admin/user-management/adding-people-to-teams.md b/translations/pt-BR/content/admin/user-management/adding-people-to-teams.md
index 86a01ad863..5dc2a78b61 100644
--- a/translations/pt-BR/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/pt-BR/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: 'Após a criação de uma equipe, os administradores da organização podem adicionar usuários da {% data variables.product.product_location %} e determinar quais repositórios eles poderão acessar.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Cada equipe tem suas próprias [ permissões de acesso definidas individualmente para os repositórios pertencentes à organização](/articles/permission-levels-for-an-organization).
diff --git a/translations/pt-BR/content/admin/user-management/audit-logging.md b/translations/pt-BR/content/admin/user-management/audit-logging.md
index d6dff53d36..6792f4cd48 100644
--- a/translations/pt-BR/content/admin/user-management/audit-logging.md
+++ b/translations/pt-BR/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Para obter uma lista completa, consulte "[Ações auditadas](/admin/user-management/audited-actions)". Para obter mais informações sobre como encontrar uma ação em particular, consulte "[Pesquisar no log de auditoria](/admin/user-management/searching-the-audit-log)".
diff --git a/translations/pt-BR/content/admin/user-management/audited-actions.md b/translations/pt-BR/content/admin/user-management/audited-actions.md
index ea7348eefb..c8dc3ae9d0 100644
--- a/translations/pt-BR/content/admin/user-management/audited-actions.md
+++ b/translations/pt-BR/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### Autenticação
diff --git a/translations/pt-BR/content/admin/user-management/auditing-ssh-keys.md b/translations/pt-BR/content/admin/user-management/auditing-ssh-keys.md
index 9407951213..a142f0130d 100644
--- a/translations/pt-BR/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/pt-BR/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 Depois de iniciada, a auditoria desabilita todas as chaves SSH e força os usuários a aprová-las ou rejeitá-las antes que eles possam clonar, fazer pull ou fazer push para qualquer repositório. Auditorias são úteis nos casos em que um funcionário ou contratado sai da empresa e você deve garantir a verificação de todas as chaves.
diff --git a/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md
index 90320047fe..1a4d9b2b00 100644
--- a/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### Acessar o log de auditoria
diff --git a/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md b/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md
index be5ec7f678..9fafce255f 100644
--- a/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/pt-BR/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index cd295df1e4..d3dd26235c 100644
--- a/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### Sobre o {% data variables.large_files.product_name_long %}
diff --git a/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md
index 6ac32e56f3..a111b45733 100644
--- a/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/pt-BR/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/pt-BR/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/pt-BR/content/admin/user-management/continuous-integration-using-jenkins.md
index de5d713485..70a415d5d0 100644
--- a/translations/pt-BR/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/pt-BR/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/user-management/creating-teams.md b/translations/pt-BR/content/admin/user-management/creating-teams.md
index dfcc430395..0c8cda672c 100644
--- a/translations/pt-BR/content/admin/user-management/creating-teams.md
+++ b/translations/pt-BR/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 As equipes são essenciais para vários recursos de colaboração do {% data variables.product.prodname_dotcom %}, como as @menções, que chamam a atenção dos integrantes envolvidos em alguma questão específica. Para obter mais informações sobre como configurar equipes e permissões de equipe, consulte "[Níveis de permissão nos repositórios da organização](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)".
diff --git a/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index adcc719ae4..bdb5204b86 100644
--- a/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: Personalizar mensagens de usuário para sua empresa
+shortTitle: Personalizar mensagens de usuário
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: 'Você pode criar mensagens personalizadas que os usuários verão em {%
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### Sobre mensagens de usuário
diff --git a/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index a727654897..222d69289c 100644
--- a/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: Você pode impedir que as pessoas usem o Git através do SSH para certos
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### Desabilitar o acesso por SSH do Git a repositórios específicos
diff --git a/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md
index 30f4249112..775820d89c 100644
--- a/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparar a organização de origem em {% data variables.product.prodname_dotcom %}
diff --git a/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index cb5ef53c4b..c18b1c20c1 100644
--- a/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparar a instância de origem de {% data variables.product.prodname_ghe_server %}
diff --git a/translations/pt-BR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/pt-BR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 62b77a16c4..2b64f888b4 100644
--- a/translations/pt-BR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/pt-BR/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Importar projetos do Mercurial
diff --git a/translations/pt-BR/content/admin/user-management/log-forwarding.md b/translations/pt-BR/content/admin/user-management/log-forwarding.md
index 2e57acc814..ff7446b929 100644
--- a/translations/pt-BR/content/admin/user-management/log-forwarding.md
+++ b/translations/pt-BR/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Qualquer sistema de coleta de logs com suporte a fluxos de logs do estilo syslog é compatível (por exemplo, [Logstash](http://logstash.net/) e [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
diff --git a/translations/pt-BR/content/admin/user-management/managing-dormant-users.md b/translations/pt-BR/content/admin/user-management/managing-dormant-users.md
index 92503b3c9a..54d2c66160 100644
--- a/translations/pt-BR/content/admin/user-management/managing-dormant-users.md
+++ b/translations/pt-BR/content/admin/user-management/managing-dormant-users.md
@@ -9,8 +9,11 @@ intro: 'Uma conta de usuário é considerada inativa se não estiver ativa por p
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 O termo "atividade" inclui, entre outros:
diff --git a/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md b/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md
index 0f9b96f7d4..6cf60bfa58 100644
--- a/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/pt-BR/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### Sobre webhooks globais
diff --git a/translations/pt-BR/content/admin/user-management/managing-projects-using-jira.md b/translations/pt-BR/content/admin/user-management/managing-projects-using-jira.md
index af540d2c95..9fec9dfa7c 100644
--- a/translations/pt-BR/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/pt-BR/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: Gerenciar projetos usando JIRA
-intro: 'Você pode integrar o JIRA ao {% data variables.product.prodname_enterprise %} para gerenciar projetos.'
+title: Gerenciar projetos usando o Jira
+intro: 'Você pode integrar o Jira com {% data variables.product.prodname_enterprise %} para o gerenciamento de projeto.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### Conectar o JIRA a uma organização do {% data variables.product.prodname_enterprise %}
+### Conectar o Jira a uma organização de {% data variables.product.prodname_enterprise %}
 
-1. Entre na sua conta do {% data variables.product.prodname_enterprise %} em http[s]://[hostname]/login.
-1. No canto superior direito de qualquer página, clique no ícone de configuração da conta (engrenagem).
-1. Na barra lateral esquerda, clique no nome da organização.
-1. Na barra lateral esquerda, clique em **Applications** (Aplicativos).
-1. No canto superior direito da caixa **Organization applications** (Aplicativos da organização), clique em **Register new application** (Registrar novo aplicativo).
-1. Defina as configurações do aplicativo:
-    - No campo **Application name** (Nome do aplicativo), digite "JIRA".
-    - No campo **Homepage URL** (URL da página inicial), digite a URL completa da sua instância do JIRA.
-    - No campo **URL de callback de autorização**, digite a URL completa da sua instância do JIRA.
-1. Clique em **Register application** (Registrar aplicativo).
-1. Na parte superior da página, anote os dados dos campos **Client ID** (ID do cliente) e **Client Secret** (Segredo do cliente). Você precisará dessas informações para configurar sua instância do JIRA.
+1. Entre na sua conta do {% data variables.product.prodname_enterprise %} em http[s]://[hostname]/login. Se já conectado, clique no logotipo de {% data variables.product.prodname_dotcom %} no canto superior esquerdo.
+2. Clique no seu ícone de perfil abaixo do logotipo de {% data variables.product.prodname_dotcom %} e selecione a organização que você deseja que se conecte com o Jira.
 
-### Configurar a instância do JIRA
+  ![Selecione uma organização](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. Na instância do JIRA, entre em uma conta com acesso administrativo.
-1. Na parte superior da página, clique no ícone de configuração (engrenagem).
-1. No menu suspenso de configuração, clique em **Add-ons** (Complementos).
-1. Na barra lateral esquerda, em **Source control** (Controle de fontes), clique em **DVCS accounts** (Contas DVCS).
-1. Clique em **Link Bitbucket or GitHub account** (Vincular conta do Bitbucket ou GitHub).
-1. No modal **Add New Account** (Adicionar nova conta), defina as configurações do {% data variables.product.prodname_enterprise %}:
-    - No menu suspenso **Host**, clique em **GitHub Enterprise**.
+3. Clique no link de configuração **Editar _nome da organização_ **.
+
+  ![Editar configurações da organização](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. Na barra lateral esquerda, em **Configurações do desenvolvedor**, clique em **Aplicativos OAuth**.
+
+  ![Selecionar aplicativos OAuth](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Clique no botão **Registrar novo aplicativo**.
+
+  ![Botão para cadastrar novo aplicativo](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. Defina as configurações do aplicativo:
+    - No campo **do nome do aplicativo**, digite "Jira" ou qualquer nome que você gostaria de usar para identificar a instância do Jira.
+    - No campo **Homepage URL**, digite a URL completa da sua instância do Jira.
+    - No campo **URL de retorno de chamada de autorização**, digite a URL completa de sua instância do Jira.
+7. Clique em **Register application** (Registrar aplicativo).
+8. Na parte superior da página, anote os dados dos campos **Client ID** (ID do cliente) e **Client Secret** (Segredo do cliente). Você precisará dessas informações para configurar sua instância do Jira.
+
+### Configuração da instância do Jira
+
+1. Na instância do Jira, faça login em uma conta com acesso administrativo.
+2. Na parte superior da página, clique no ícone de configurações (engrenagem) e selecione **Aplicativos**.
+
+  ![Selecionar aplicativos nas configurações do Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. Na barra lateral esquerda, em **Integrações**, clique em **contas DVCS**.
+
+  ![Menu de Integrações do Jira - Contas DVCS](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Clique **Link Bitbucket Cloud ou conta de {% data variables.product.prodname_dotcom %}**.
+
+  ![Vincular conta do GitHub ao Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. No modal **Add New Account** (Adicionar nova conta), defina as configurações do {% data variables.product.prodname_enterprise %}:
+    - No menu suspenso **Host**, selecione **{% data variables.product.prodname_enterprise %}**.
     - No campo **Team or User Account** (Conta de equipe ou usuário), digite o nome da sua organização ou conta pessoal do {% data variables.product.prodname_enterprise %}.
     - No campo **OAuth Key** (Chave OAuth), informe o Client ID (ID do cliente) do seu aplicativo de desenvolvedor do {% data variables.product.prodname_enterprise %}.
     - No campo **OAuth Secret** (Segredo OAuth), informe o Client Secret (Segredo do cliente) do seu aplicativo de desenvolvedor do {% data variables.product.prodname_enterprise %}.
-    - Se você não quiser vincular novos repositórios pertencentes à sua organização ou conta pessoal do {% data variables.product.prodname_enterprise %}, desmarque a opção **Auto Link New Repositories** (Vincular automaticamente novos repositórios).
-    - Se você não quiser habilitar os commits inteligentes, desmarque a opção  **Habilitar commits inteligentes**.
+    - Se você não desejar vincular novos repositórios que pertencem à sua organização de {% data variables.product.prodname_enterprise %} ou conta pessoal, desmarque a opção **Vincular novos repositórios automaticamente**.
+    - Se você não quiser ativar commits inteligentes, desmarque **Habilitar commits inteligentes**.
     - Clique em **Salvar**.
-1. Revise as permissões que você vai conceder à sua conta do {% data variables.product.prodname_enterprise %} e clique em **Authorize application** (Autorizar aplicativo).
-1. Se necessário, digite a senha para continuar.
+6. Revise as permissões que você vai conceder à sua conta do {% data variables.product.prodname_enterprise %} e clique em **Authorize application** (Autorizar aplicativo).
+7. Se necessário, digite a senha para continuar.
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md
index 299f4a8910..8c6e12e223 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Aplicar os dados importados em {% data variables.product.prodname_ghe_server %}
diff --git a/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md b/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md
index 010a4fa020..7c79bc4615 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### Sobre repositórios internos
@@ -34,6 +38,12 @@ Se você não tiver o modo privado ativado, o script de migração não terá ef
 ### Executando a migração
 
 1. Conecte-se ao shell administrativo. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/enterprise/{}/admin/installation/accessing-the-administrative-shell-ssh)".
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. Execute o comando de migração.
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. Navegue no diretório `/data/github/current`.
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ Se você não tiver o modo privado ativado, o script de migração não terá ef
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 O output do log aparecerá no terminal e no `/tmp/convert_public_ghes_repos_to_internal.log`.
 
diff --git a/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index 6177db066c..9bdf07cabe 100644
--- a/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/pt-BR/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 Geralmente, quando alguém exclui um repositório, ele continua disponível em disco por 90 dias e pode ser restaurado pelo painel de administração do site. Após esse período, o repositório é removido e excluído permanentemente. Ao impor uma retenção legal a um usuário ou organização, os repositórios desse usuário ou organização ficarão disponíveis para restauração por tempo indefinido.
diff --git a/translations/pt-BR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index c1bc65e95a..da462196b6 100644
--- a/translations/pt-BR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Preparar os dados migrados para importação para {% data variables.product.prodname_ghe_server %}
diff --git a/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md
index 9cdae8d77b..7c97be6ed3 100644
--- a/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/pt-BR/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: Você pode impedir que usuários criem organizações na sua empresa.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/pt-BR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/pt-BR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index 25e9479469..86ffc6a3b0 100644
--- a/translations/pt-BR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/pt-BR/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: Os administradores do site podem promover qualquer conta de usuário como administrador do site e rebaixar administradores do site para usuários regulares.
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/pt-BR/content/admin/user-management/rebuilding-contributions-data.md b/translations/pt-BR/content/admin/user-management/rebuilding-contributions-data.md
index 46ba8d14c3..833c4a3f08 100644
--- a/translations/pt-BR/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/pt-BR/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 Sempre que é enviado para o {% data variables.product.prodname_enterprise %}, o commit é vinculado a uma conta de usuário caso ambos estejam associados ao mesmo endereço de e-mail. No entanto, os commits *não* são vinculados retroativamente quando um usuário registra um endereço de e-mail ou cria uma conta.
diff --git a/translations/pt-BR/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/pt-BR/content/admin/user-management/removing-users-from-teams-and-organizations.md
index e342bfbc94..64b96a33e2 100644
--- a/translations/pt-BR/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/pt-BR/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Somente proprietários ou administradores de equipe podem remover integrantes da organização. Quando um usuário é removido de uma equipe ou organização, seus problemas, pull requests e comentários nos repositórios da organização continuam intactos e atribuídos a ele.
diff --git a/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index 3a5c4b127d..11ecd6b9f3 100644
--- a/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/pt-BR/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 Ao usar o LDAP ou autenticação integrada, a autenticação de dois fatores será compatível em {% data variables.product.product_location %}. Os administradores da organização podem exigir que os integrantes habilitem a autenticação de dois fatores.
diff --git a/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md b/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md
index f28dd783f1..229a78d081 100644
--- a/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/pt-BR/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### Sintaxe de consulta de pesquisa
diff --git a/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md
index 70262de204..e92465b448 100644
--- a/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Se um usuário sair da empresa ou mudar para outro departamento, você deve remover ou modificar a forma como ele acessa a {% data variables.product.product_location %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 Se funcionários saírem da empresa, você poderá suspender suas contas do {% data variables.product.prodname_ghe_server %} para disponibilizar licenças de usuário em sua licença {% data variables.product.prodname_enterprise %}, embora os problemas, comentários, repositórios, gists e outros dados que eles criaram continuem existindo. Usuários suspensos não podem entrar na sua instância nem fazer push ou pull de códigos.
diff --git a/translations/pt-BR/content/admin/user-management/viewing-push-logs.md b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md
index 6599691c6a..2edb47b54d 100644
--- a/translations/pt-BR/content/admin/user-management/viewing-push-logs.md
+++ b/translations/pt-BR/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 As entradas de log de push mostram o seguinte:
diff --git a/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md
index 3ca1948796..f4889ebcd9 100644
--- a/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md
@@ -22,11 +22,13 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 #### Disponível para todos os repositórios
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **Política de segurança**
 
-  Facilita para as pessoas relatar, de modo confidencial, vulnerabilidades de segurança que encontram no seu repositório. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)".
+  Facilite o acesso dos seus usuários para relatar confidencialmente vulnerabilidades de segurança que encontraram no seu repositório. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/code-security/getting-started/adding-a-security-policy-to-your-repository)".
+{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **Consultorias de segurança**
 
   Discute em particular e corrige vulnerabilidades de segurança no código do seu repositório. Em seguida, você pode publicar uma consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade e incentivá-los a fazer a atualização. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
diff --git a/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..bafa536077
--- /dev/null
+++ b/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: Adicionar uma política de segurança ao repositório
+intro: 'Você pode dar instruções sobre como relatar uma vulnerabilidade de segurança no seu projeto, adicionando uma política de segurança ao seu repositório.'
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### Sobre políticas de segurança
+
+Para dar às pessoas instruções para relatar vulnerabilidades de segurança no seu projeto{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} você pode adicionar um arquivo _SECURITY.md_ à raiz do seu repositório, `docs` ou à pasta `.github`.{% else %} você pode adicionar um arquivo _SECURITY.md_ à raiz do seu repositório ou à pasta `docs`.{% endif %} Quando alguém criar um problema no seu repositório, a pessoa verá um link para a política de segurança do seu projeto.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+Você pode criar uma política de segurança padrão para sua organização ou conta de usuário. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+{% endif %}
+
+{% tip %}
+
+**Dica:** para ajudar as pessoas a encontrar a política de segurança, você poderá vincular seu arquivo _SECURITY.md_ a outros locais em seu repositório, como o arquivo README. Para obter mais informações, consulte "[Sobre README](/articles/about-readmes)".
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+Depois que alguém informar uma vulnerabilidade de segurança no seu projeto, você pode usar o {% data variables.product.prodname_security_advisories %} para divulgar, corrigir e publicar informações sobre a vulnerabilidade. Para obter mais informações sobre o processo de relatórios e divulgação de vulnerabilidades em {% data variables.product.prodname_dotcom %}, consulte "[Sobre divulgação coordenada das vulnerabilidades de segurança](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para obter mais informações sobre {% data variables.product.prodname_security_advisories %}, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+Ao disponibilizar claramente instruções de relatório de segurança, você torna mais fácil para os usuários relatar quaisquer vulnerabilidades de segurança que encontrem no repositório usando seu canal de comunicação preferido.
+{% endif %}
+
+### Adicionar uma política de segurança ao repositório
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. Na barra lateral esquerda, clique em **Política de segurança**. ![Aba de política de segurança](/assets/images/help/security/security-policy-tab.png)
+4. Clique em **Start setup** (Iniciar configuração). ![Botão Start setup (Iniciar configuração)](/assets/images/help/security/start-setup-security-policy-button.png)
+5. No novo arquivo _SECURITY.md_, adicione informações sobre versões compatíveis do seu projeto e como relatar uma vulnerabilidade.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### Leia mais
+
+- "[Sobre como proteger o repositório](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Configurar o projeto para contribuições saudáveis](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/pt-BR/content/code-security/getting-started/index.md b/translations/pt-BR/content/code-security/getting-started/index.md
index 9a34c65ce1..f0f979e672 100644
--- a/translations/pt-BR/content/code-security/getting-started/index.md
+++ b/translations/pt-BR/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### Índice
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md b/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md
index 771f7aea7d..69fa2c2888 100644
--- a/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md
@@ -45,7 +45,7 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p
 {% data variables.product.prodname_secret_scanning_caps %} está disponível em todos os repositórios de propriedade da organização como parte de {% data variables.product.prodname_GH_advanced_security %}. Não está disponível em repositórios pertencentes a usuários.
 {% endif %}
 
-Se você é um administrador de repositório ou um proprietário de uma organização, você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% if currentVersion == "free-pro-team@latest" %} repositórios privados{% endif %} pertencentes a organizações. You can enable  {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+Se você é um administrador de repositório ou um proprietário de uma organização, você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% if currentVersion == "free-pro-team@latest" %} repositórios privados{% endif %} pertencentes a organizações. Você pode habilitar  {% data variables.product.prodname_secret_scanning %} para todos os seus repositórios ou para todos os novos repositórios da organização.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados pertencentes a usuários.{% endif %} Para mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" e "[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)".
 
 Quando você faz push dos commits para um repositório{% if currentVersion == "free-pro-team@latest" %} privado{% endif %} com {% data variables.product.prodname_secret_scanning %} habilitado, {% data variables.product.prodname_dotcom %} verifica o conteúdo dos segredos dos commits.
 
diff --git a/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index 8763d258a3..27f3abdd5f 100644
--- a/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -27,13 +27,19 @@ topics:
 
 ### Habilitar {% data variables.product.prodname_secret_scanning %} para repositórios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}
 
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Você pode habilitar {% data variables.product.prodname_secret_scanning %} para qualquer repositório que pertença a uma organização.
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. Talvez seja necessário habilitar {% data variables.product.prodname_GH_advanced_security %} para ativar o botão para "{% data variables.product.prodname_secret_scanning_caps %}". À direita de "{% data variables.product.prodname_GH_advanced_security %}", clique em **Habilitar**. ![Habilitar {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. Clique **Habilitar {% data variables.product.prodname_GH_advanced_security %} para este repositório** para confirmar a ação. ![Confirme a habilitação de {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. Ao habilitar {% data variables.product.prodname_GH_advanced_security %}, isso poderá automaticamente habilitar {% data variables.product.prodname_secret_scanning %} para o repositório (isso é controlado pela configuração da organização). Se "{% data variables.product.prodname_secret_scanning_caps %}" é exibido com um botão **habilitar**. Você ainda precisa habilitar {% data variables.product.prodname_secret_scanning %} clicando em **Habilitar**. Se você vir um botão **Desabilitar**, significa que {% data variables.product.prodname_secret_scanning %} já está habilitado. ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. Se {% data variables.product.prodname_advanced_security %} ainda não estiver habilitado para o repositório, à direita de "{% data variables.product.prodname_GH_advanced_security %}", clique em **Habilitar**.
+   {% if currentVersion == "free-pro-team@latest" %}![Habilitar {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Revise o impacto de habilitar {% data variables.product.prodname_advanced_security %}, e clique em **Permitir {% data variables.product.prodname_GH_advanced_security %} para este repositório**.
+6. Quando você habilitar {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} pode ser habilitado automaticamente para o repositório, devido às configurações da organização. Se "{% data variables.product.prodname_secret_scanning_caps %}" é exibido com um botão **habilitar**. Você ainda precisa habilitar {% data variables.product.prodname_secret_scanning %} clicando em **Habilitar**. Se você vir um botão **Desabilitar**, significa que {% data variables.product.prodname_secret_scanning %} já está habilitado. ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
 7. À direita de "{% data variables.product.prodname_secret_scanning_caps %}", clique em **Habilitar**. ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
@@ -66,7 +72,7 @@ Você pode usar um arquivo *secret_scanning.yml* para excluir diretórios do {%
 
     {% endnote %}
 
-Você também pode ignorar alertas individuais de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)."
+Você também pode ignorar alertas individuais de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)."
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/pt-BR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index 61555ca125..4608a3e111 100644
--- a/translations/pt-BR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -14,7 +14,7 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-### Gerenciando alertas
+### Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
@@ -49,3 +49,11 @@ Uma vez que um segredo tenha sido committed a um repositório, você deve consid
 
 - Para um token de acesso pessoal do {% data variables.product.prodname_dotcom %}, exclua o token comprometido, crie outro token e atualize os serviços que usam o token antigo. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)".
 - Para todos os outros segredos, primeiro, verifique se o segredo commited para {% data variables.product.product_name %} é válido. Se sim, crie um novo segredo, atualize quaisquer serviços que utilizam o segredo antigo, e depois exclua o segredo antigo.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configurando notificações para alertas de {% data variables.product.prodname_secret_scanning %}
+
+Quando um novo segredo é detectado, {% data variables.product.prodname_dotcom %} notifica todos os usuários com acesso a alertas de segurança para o repositório, de acordo com suas preferências de notificação. Você receberá alertas se estiver acompanhando o repositório, tiver ativado notificações para alertas de segurança, ou o autor do commit que contém o segredo e não estiver ignorando o repositório.
+
+Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" e "[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
+{% endif %}
diff --git a/translations/pt-BR/content/code-security/secure-coding/about-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/about-code-scanning.md
index a32b2393d9..9339b72357 100644
--- a/translations/pt-BR/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/pt-BR/content/code-security/secure-coding/about-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -36,7 +38,7 @@ Você pode visualizar e contribuir para as consultas do {% data variables.produc
 
 Para obter mais informações sobre os pontos de extremidade da API para {% data variables.product.prodname_code_scanning %}, consulte "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)".
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 Você pode visualizar e contribuir para as consultas do {% data variables.product.prodname_code_scanning %} no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %} consultas](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) na documentação do {% data variables.product.prodname_codeql %}.
 
@@ -48,17 +50,14 @@ Você pode visualizar e contribuir para as consultas do {% data variables.produc
 
 {% endif %}
 
-### Ferramentas de varredura de código de terceiros
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### Sobre ferramentas de {% data variables.product.prodname_code_scanning %} de terceiros
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+Você pode executar ferramentas de análise de terceiros em {% data variables.product.product_name %} usando ações ou em um sistema CI externo. Para mais informações consulte "[Configurar a verificação de código para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" ou "[Enviar um arquivo SARIF para o GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)".
 
 ### Leia mais
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- "[Sobre proteger seu repositório](/github/administering-a-repository/about-securing-your-repository)"
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [Formato de Intercâmbio de Resultados de Análise Estática OASIS (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) no site do Comitê OASIS
diff --git a/translations/pt-BR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..df8f91cefa
--- /dev/null
+++ b/translations/pt-BR/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: Sobre a varredura de código de CodeQL no seu sistema de CI
+shortTitle: Varredura de código na sua CI
+intro: 'Você pode analisar o seu código com {% data variables.product.prodname_codeql %} em um sistema de integração contínua de terceiros e fazer o upload dos resultados para {% data variables.product.product_location %}. Os alertas de {% data variables.product.prodname_code_scanning %} resultantes são exibidos junto com todos os alertas gerados dentro de {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Sobre {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI
+
+{% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning).
+
+Você pode executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} dentro de {% data variables.product.product_name %} usando ações. Como alternativa, se você usar um sistema de integração contínua ou um sistema de entrega/Continuous Delivery (CI/CD) de terceiros você poderá executar a análise {% data variables.product.prodname_codeql %} no seu sistema existente e enviar os resultados para {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Se você adicionar {% data variables.product.prodname_codeql_cli %} ou {% data variables.product.prodname_codeql_runner %} ao seu sistema de terceiros, chame a ferramenta para analisar o código e fazer o upload dos resultados SARIF para {% data variables.product.product_name %}. Os alertas de {% data variables.product.prodname_code_scanning %} resultantes são exibidos junto com todos os alertas gerados dentro de {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparar {% data variables.product.prodname_codeql_cli %} e {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+A {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que utiliza o {% data variables.product.prodname_codeql_cli %} para analisar o código e fazer o upload dos resultados para {% data variables.product.product_name %}. A ferramenta imita a análise executada nativamente dentro de {% data variables.product.product_name %} usando ações. O executor é capaz de integrar-se a ambientes de compilação mais complexos do que o CLI, mas esta capacidade torna mais difícil e suscetível de erros de configuração. É também mais difícil depurar quaisquer problemas. De modo geral, é melhor usar {% data variables.product.prodname_codeql_cli %} diretamente a menos que não seja compatível com o seu caso de uso.
+
+Use {% data variables.product.prodname_codeql_cli %} para analisar:
+
+- Linguagens dinâmicas, por exemplo, JavaScript e Python.
+- Bases de código com uma linguagem compilada que pode ser construída com um único comando ou executando um único script.
+
+Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)".
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+Você precisará usar {% data variables.product.prodname_codeql_runner %} se precisar:
+- Configurar o sistema de CI para orquestrar as invocações do compilador, bem como executar a análise de {% data variables.product.prodname_codeql %}.
+- Analisar mais de uma linguagem em um repositório.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)".
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+Se você adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de terceiros, chame a ferramenta para analisar o código e fazer o upload dos resultados do SARIF para {% data variables.product.product_name %}. Os alertas de {% data variables.product.prodname_code_scanning %} resultantes são exibidos junto com todos os alertas gerados dentro de {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+Para configurar a verificação de código no seu sistema de CI, consulte "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)".
+{% endif %}
diff --git a/translations/pt-BR/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/about-integration-with-code-scanning.md
index b72e4c72c5..014ba9b66d 100644
--- a/translations/pt-BR/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/pt-BR/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/pt-BR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/pt-BR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 71e283624a..365d59f2ab 100644
--- a/translations/pt-BR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/pt-BR/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md
index f6c50f54a0..2d3cd5b0f4 100644
--- a/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md
@@ -14,14 +14,21 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
 ### Sobre a configuração do {% data variables.product.prodname_code_scanning %}
 
-Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}, usando {% data variables.product.prodname_actions %}, ou a partir do seu sistema de integração contínua (CI), ao usar {% data variables.product.prodname_codeql_runner %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." Para obter mais informações sobre o {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)".
+Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}, usando {% data variables.product.prodname_actions %} ou a partir do seu sistema de integração contínua (CI). Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" ou
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[Sobre {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{%- else %}
+"[Executar {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-Este artigo é sobre a execução de {% data variables.product.prodname_code_scanning %} no {% data variables.product.product_name %}.
+Este artigo é sobre a execução de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} usando ações.
 
 Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve configurar {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
 
@@ -59,7 +66,7 @@ Se você fizer uma varredura no push, os resultados aparecerão na aba **Seguran
 
 #### Fazer a varredura de pull requests
 
-O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% if currentVersion ver_gt "enterprise-server@2.21" %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."{% endif %}
+O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% if currentVersion ver_gt "enterprise-server@2.21" %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. Para obter mais informações, consulte "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para um repositório](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %}
 
 Para obter mais informações sobre o evento `pull_request` , consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)".
 
@@ -122,7 +129,7 @@ Este fluxo de trabalho faz a varredura:
 
 ### Especificar um sistema operacional
 
-Se seu código exigir um sistema operacional específico para compilar, você poderá configurar o sistema operacional em seu {% data variables.product.prodname_codeql_workflow %}. Edite o valor de `jobs.analyze.runs-on` para especificar o sistema operacional para a máquina que executa suas ações de {% data variables.product.prodname_code_scanning %}. {% if currentVersion ver_gt "enterprise-server@2. 1" %}Você especifica o sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos após `auto-hospedado`.{% else %}
+Se seu código exigir um sistema operacional específico para compilar, você poderá configurar o sistema operacional em seu {% data variables.product.prodname_codeql_workflow %}. Edite o valor de `jobs.analyze.runs-on` para especificar o sistema operacional para a máquina que executa suas ações de {% data variables.product.prodname_code_scanning %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}Você especifica o sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos, após `auto-hospedado`.{% else %}
 
 Se você optar por usar um executor auto-hospedado para varredura de código, você pode especificar um sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos, após `auto-hospedado`.{% endif %}
 
@@ -135,7 +142,7 @@ jobs:
 
 {% if currentVersion == "free-pro-team@latest" %}Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
 
-O {% data variables.product.prodname_code_scanning_capc %} é compatível com as versões mais recentes do macOS, Ubuntu, e Windows. Portanto, os valores típicos para essa configuração são `ubuntu-latest`, `windows-latest` e `macos-latest`. Para obter mais informações, consulte {% if currentVersion ver_gt "enterprise-server@2. 1" %}"[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" e "[Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+O {% data variables.product.prodname_code_scanning_capc %} é compatível com as versões mais recentes do macOS, Ubuntu, e Windows. Portanto, os valores típicos para essa configuração são `ubuntu-latest`, `windows-latest` e `macos-latest`. Para obter mais informações, consulte {% if currentVersion ver_gt "enterprise-server@2.21" %}" %}"[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" e "[Usando rótulos com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}Você deve garantir que o Git esteja na variável do PATH em seus executores auto-hospedados.{% else %}Se você usa um executor auto-hospedado, você deve garantir que o Git esteja na variável de PATH.{% endif %}
 
@@ -143,7 +150,7 @@ O {% data variables.product.prodname_code_scanning_capc %} é compatível com as
 
 O {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} detecta automaticamente código escrito nas linguagens compatíveis.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 O arquivo padrão do {% data variables.product.prodname_codeql_workflow %} contém uma matriz de criação denominada `linguagem` que lista as linguagens no seu repositório que são analisadas. O {% data variables.product.prodname_codeql %} preenche automaticamente esta matriz quando você adiciona o {% data variables.product.prodname_code_scanning %} a um repositório. Usar a matriz de `linguagem` otimiza {% data variables.product.prodname_codeql %} para executar cada análise em paralelo. Recomendamos que todos os fluxos de trabalho adotem esta configuração devido aos benefícios de desempenho de criações paralelas. Para obter mais informações sobre matrizes de criação, consulte "[Gerenciar fluxos de trabalho complexos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
 
@@ -184,34 +191,66 @@ Alternativamente, você pode instalar as dependências do Python manualmente em
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. Por exemplo:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. Para obter mais informações, consulte "[Suporte SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)".
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
 ### Executar consultas adicionais
 
 {% data reusables.code-scanning.run-additional-queries %}
@@ -308,6 +347,7 @@ paths-ignore:
 **Observação**:
 
 * As palavras-chave `caminhos` e `paths-ignore`, usados no contexto do arquivo de configuração do {% data variables.product.prodname_code_scanning %}, não deve ser confundido com as mesmas palavras-chave usadas para `on.<push|pull_request>.paths` em um fluxo de trabalho. Quando estão acostumados a modificar `on.<push|pull_request>` em um fluxo de trabalho, eles determinam se as ações serão executadas quando alguém modifica o código nos diretórios especificados. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)".
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
 * `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por exemplo, `foo/**`, `**/foo` e `foo/**/bar` são todos de sintaxe permitida, mas `**foo` não é. No entanto, você pode usar estrelas únicas junto com outros caracteres, conforme mostrado no exemplo. Você precisará colocar entre aspas qualquer coisa que contenha um caractere `*`.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..f20965db96
--- /dev/null
+++ b/translations/pt-BR/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,203 @@
+---
+title: Configurar o executor do CodeQL no seu sistema de CI
+shortTitle: Configurar o executor do CodeQL
+intro: 'Você pode configurar como o {% data variables.product.prodname_codeql_runner %} faz a varredura do código no seu projeto e faz o upload dos resultados para o {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Sobre a configuração de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI
+
+Para integrar {% data variables.product.prodname_code_scanning %} ao seu sistema de CI, você pode usar o {% data variables.product.prodname_codeql_runner %}. Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)".
+
+De modo geral, você invoca o {% data variables.product.prodname_codeql_runner %} da seguinte forma.
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` depende do local onde você fez o download do {% data variables.product.prodname_codeql_runner %} no seu sistema de CI. `codeql-runner-OS` depende do sistema operacional que você usa. Existem três versões do {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos` e `codeql-runner-win`, para os sistemas Linux, macOS e Windows, respectivamente.
+
+Para personalizar a maneira como o {% data variables.product.prodname_codeql_runner %} faz a varredura do seu código, você pode usar sinalizadores, como `--languages` e `--queries`, ou você pode especificar configurações personalizadas em um arquivo de configuração separado.
+
+### Fazer a varredura de pull requests
+
+A varredura de código sempre que uma pull request é criada impede que os desenvolvedores introduzam novas vulnerabilidades e erros no código.
+
+Para fazer a varredura de um pull request, execute o comando `analyze` e use o sinalizador `--ref` para especificar o pull request. A referência é `refs/pull/<PR-number>/head` ou `refs/pull/<PR-number>/merge`, dependendo se você verificou o commit HEAD do branch do pull request ou um commit de merge com o branch de base.
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**Observação**: Se você analisar o código com uma ferramenta de terceiros e desejar que os resultados apareçam como verificações de pull request, você deverá executar o comando `upload` e usar o sinalizador `--ref` para especificar o pull request em vez do branch. A referência é `refs/pull/<PR-number>/head` ou `refs/pull/<PR-number>/merge`.
+
+{% endnote %}
+
+### Sobrescrever a detecção automática de linguagem
+
+O {% data variables.product.prodname_codeql_runner %} detecta e faz a varredura automática do código escrito nas linguagens compatíveis.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+Para substituir a detecção automática de idioma, execute o comando `init` com o sinalizador `--languages`, seguido de uma lista de palavras-chave de linguagem separada por vírgulas. As palavras-chave para os idiomas compatíveis são {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### Executar consultas adicionais
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+Para adicionar uma ou mais consultas, passe uma lista de caminhos separados por vírgulas para o sinalizador `--queries` do comando `init`. Você também pode especificar consultas adicionais em um arquivo de configuração.
+
+Se você também estiver usando um arquivo de configuração para configurações personalizadas, e você também estiver especificando consultas adicionais com o sinalizador `--queries`, o {% data variables.product.prodname_codeql_runner %} usará as consultas adicionais especificadas com o sinalizador <nobr>`--queries`</nobr> em vez de qualquer um no arquivo de configuração. Se você desejar executar o conjunto combinado de consultas adicionais especificadas com o sinalizador e no arquivo de configuração, determine previamente o valor passado para <nobr>`--queries`</nobr> com o símbolo `+`. Para obter exemplos de arquivos de configuração, consulte "[Exemplo de arquivos de configuração](#example-configuration-files)".
+
+No exemplo a seguir,. o símbolo `+` garante que o {% data variables.product.prodname_codeql_runner %} usará as consultas adicionais junto com quaisquer consultas especificadas no arquivo de configuração referenciado.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### Usar uma ferramenta de varredura de código de terceiros
+
+Em vez de passar informações adicionais para os comandos de {% data variables.product.prodname_codeql_runner %}, você pode especificar configurações personalizadas em um arquivo de configuração separado.
+
+O arquivo de configuração é um arquivo YAML. Ele usa uma sintaxe semelhante à sintaxe do fluxo de trabalho do {% data variables.product.prodname_actions %}, conforme ilustrado nos exemplos abaixo. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
+
+Use o sinalizador `--config-file` do comando `init` para especificar o arquivo de configuração. O valor de <nobr>`--config-file`</nobr> é o caminho para o arquivo de configuração que você deseja usar. Este exemplo carrega o arquivo de configuração _.github/codeql/codeql-config.yml_.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### Exemplo de arquivo de configuração
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### Configurar o {% data variables.product.prodname_code_scanning %} para linguagens compiladas
+
+Para as linguagens compiladas C/C++, C#, e Java, o {% data variables.product.prodname_codeql %} constrói o código antes de analisá-lo. {% data reusables.code-scanning.analyze-go %}
+
+Para muitos sistemas de criação comuns, o {% data variables.product.prodname_codeql_runner %} pode construir o código automaticamente. Para tentar construir o código automaticamente, execute `autobuild` entre `init` e `analise` as etapas. Observe que, se seu repositório precisar de uma versão específica de uma ferramenta de criação, primeiro você precisará instalar a ferramenta de criação manualmente.
+
+O processo `autobuild` sempre tenta criar _uma_ linguagem compilada para um repositório. A linguagem selecionada automaticamente para análise é a linguagem com mais arquivos. Se você quiser escolher um idioma explicitamente, use o sinalizador `--language` do comando `autobuild`.
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+Se o comando `autobuild` não puder criar o seu código, você poderá executar as etapas de compilação, entre as etapas de `init` e de `análise`. Para obter mais informações, consulte "[Executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)".
+
+### {% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}.
+
+Por padrão, o {% data variables.product.prodname_codeql_runner %} faz o upload dos resultados a partir de {% data variables.product.prodname_code_scanning %} quando você executa o comando de `análise`. Você também pode carregar arquivos do SARIF separadamente, usando o comando `upload`.
+
+Depois de enviar os dados, o {% data variables.product.prodname_dotcom %} exibirá os alertas no seu repositório.
+- Se você fez o upload de um pull request como, por exemplo, `--ref refs/pull/42/merge` ou `--ref refs/pull/42/head`, os resultados aparecerão como alertas em uma verificação de pull request. Para obter mais informações, consulte "[Alertas de varredura de código de triagem em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
+- Se você fez upload de um branch como, por exemplo `--ref refs/heads/my-branch`, os resultados aparecerão na aba **Segurança** do seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). "
+
+### Comando de referência de {% data variables.product.prodname_codeql_runner %}
+
+O {% data variables.product.prodname_codeql_runner %} é compatível os seguintes comandos e sinalizadores.
+
+#### `init`
+
+Inicializa o {% data variables.product.prodname_codeql_runner %} e cria um banco de dados de {% data variables.product.prodname_codeql %} para cada linguagem a ser analisada.
+
+| Sinalizador                      | Obrigatório | Valor de entrada                                                                                                                                                                                       |
+| -------------------------------- |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `--repository`                   |      ✓      | Nome do repositório a ser inicializado.                                                                                                                                                                |
+| `--github-url`                   |      ✓      | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado.                                                                                                  |
+| `--github-auth`                  |      ✓      | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal.                                                                                                            |
+| `--languages`                    |             | Lista de linguagens para análise separada por vírgulas. Por padrão, o {% data variables.product.prodname_codeql_runner %} detecta e analisa todas as linguagens compatíveis no repositório.          |
+| `--queries`                      |             | Lista separada por vírgulas de consultas adicionais a serem executadas, além do conjunto-padrão de consultas de segurança.                                                                             |
+| `--config-file`                  |             | Caminho para o arquivo de configuração personalizado.                                                                                                                                                  |
+| `--codeql-path`                  |             | Caminho para uma cópia do CLI de {% data variables.product.prodname_codeql %} executável a ser usado. Por padrão, o {% data variables.product.prodname_codeql_runner %} faz o download de uma cópia. |
+| `--temp-dir`                     |             | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`.                                                                                                                  |
+| `--tools-dir`                    |             | Diretório onde as ferramentas de {% data variables.product.prodname_codeql %} e outros arquivos são armazenados entre as execuções. O padrão é um subdiretório do diretório home.                      |
+| <nobr>`--checkout-path`</nobr> |             | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual.                                                                                                                |
+| `--debug`                        |             | Nenhum. Imprime mais resultados verbose.                                                                                                                                                               |
+| `-h`, `--help`                   |             | Nenhum. Exibe ajuda para o comando.                                                                                                                                                                    |
+
+#### `autobuild`
+
+Tenta construir o código para as linguagens compiladas C/C++, C# e Java. Para essas linguagens, {% data variables.product.prodname_codeql %} cria o código antes de analisá-lo. Executar `autobuild` entre as etapas de `init` e `analise`.
+
+| Sinalizador                 | Obrigatório | Valor de entrada                                                                                                                            |
+| --------------------------- |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--language`                |             | A linguagem a ser criada. Por padrão, o {% data variables.product.prodname_codeql_runner %} cria a linguagem compilada com mais arquivos. |
+| <nobr>`--temp-dir`</nobr> |             | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`.                                                       |
+| `--debug`                   |             | Nenhum. Imprime mais resultados verbose.                                                                                                    |
+| `-h`, `--help`              |             | Nenhum. Exibe ajuda para o comando.                                                                                                         |
+
+#### `analyze`
+
+Analisa o código nos bancos de dados do {% data variables.product.prodname_codeql %} e faz o upload dos resultados para o {% data variables.product.product_name %}.
+
+| Sinalizador                        | Obrigatório | Valor de entrada                                                                                                                                                                                                                                                                                                                    |
+| ---------------------------------- |:-----------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     |      ✓      | Nome do repositório a ser analisado.                                                                                                                                                                                                                                                                                                |
+| `--commit`                         |      ✓      | SHA do commit a ser analisado. No Git e no Azure DevOps, isso corresponde ao valor de `git rev-parse HEAD`. No Jenkins, isso corresponde a `$GIT_COMMIT`.                                                                                                                                                                           |
+| `--ref`                            |      ✓      | Nome da referência para análise, por exemplo `refs/heads/main` ou `refs/pull/42/merge`. No Git ou no Jenkins, isso corresponde ao valor de `git simbolic-ref HEAD`. No Azure DevOps, isso corresponde a `$(Build.SourceBranch)`.                                                                                                    |
+| `--github-url`                     |      ✓      | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado.                                                                                                                                                                                                                               |
+| `--github-auth`                    |      ✓      | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal.                                                                                                                                                                                                                                         |
+| <nobr>`--checkout-path`</nobr>   |             | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual.                                                                                                                                                                                                                                             |
+| `--no-upload`                      |             | Nenhum. Impede que o {% data variables.product.prodname_codeql_runner %} faça o upload dos resultados para {% data variables.product.product_name %}.                                                                                                                                                                             |
+| `--output-dir`                     |             | Diretório onde os arquivos SARIF de saída são armazenados. O padrão está no diretório de arquivos temporários.                                                                                                                                                                                                                      |
+| `--ram`                            |             | A quantidade de memória a ser usada ao executar consultas. O padrão é usar toda a memória disponível.                                                                                                                                                                                                                               |
+| <nobr>`--no-add-snippets`</nobr> |             | Nenhum. Exclui snippets de código da saída de SARIF. |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |             | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |             | Número de threads a serem usados ao executar consultas. O padrão é usar todos os núcleos disponíveis.                                                                                                                                                                                                                               |
+| `--temp-dir`                       |             | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`.                                                                                                                                                                                                                                               |
+| `--debug`                          |             | Nenhum. Imprime mais resultados verbose.                                                                                                                                                                                                                                                                                            |
+| `-h`, `--help`                     |             | Nenhum. Exibe ajuda para o comando.                                                                                                                                                                                                                                                                                                 |
+
+#### `fazer upload`
+
+Faz o upload dos arquivos SARIF para {% data variables.product.product_name %}.
+
+{% note %}
+
+**Observação**: Se você analisar o código com o executor do CodeQL, o comando `analyze` irá carregar os resultados SARIF, por padrão. Você pode usar o comando `upload` para carregar os resultados SARIF que foram gerados por outras ferramentas.
+
+{% endnote %}
+
+| Sinalizador                      | Obrigatório | Valor de entrada                                                                                                                                                                                                                      |
+| -------------------------------- |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   |      ✓      | O arquivo SARIF a ser subido ou um diretório que contém vários arquivos SARIF.                                                                                                                                                        |
+| `--repository`                   |      ✓      | Nome do repositório que foi analisado.                                                                                                                                                                                                |
+| `--commit`                       |      ✓      | SHA do commit que foi analisado. No Git e no Azure DevOps, isso corresponde ao valor de `git rev-parse HEAD`. No Jenkins, isso corresponde a `$GIT_COMMIT`.                                                                           |
+| `--ref`                          |      ✓      | Nome da referência que foi analisada, por exemplo `refs/heads/main` ou `refs/pull/42/merge`. No Git ou no Jenkins, isso corresponde ao valor de `git simbolic-ref HEAD`. No Azure DevOps, isso corresponde a `$(Build.SourceBranch)`. |
+| `--github-url`                   |      ✓      | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado.                                                                                                                                 |
+| `--github-auth`                  |      ✓      | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal.                                                                                                                                           |
+| <nobr>`--checkout-path`</nobr> |             | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual.                                                                                                                                               |
+| `--debug`                        |             | Nenhum. Imprime mais resultados verbose.                                                                                                                                                                                              |
+| `-h`, `--help`                   |             | Nenhum. Exibe ajuda para o comando.                                                                                                                                                                                                   |
diff --git a/translations/pt-BR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index 0aaf0b46e1..4168de481b 100644
--- a/translations/pt-BR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/pt-BR/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/pt-BR/content/code-security/secure-coding/index.md b/translations/pt-BR/content/code-security/secure-coding/index.md
index 4d12da4189..e00f749e7c 100644
--- a/translations/pt-BR/content/code-security/secure-coding/index.md
+++ b/translations/pt-BR/content/code-security/secure-coding/index.md
@@ -1,7 +1,7 @@
 ---
 title: Encontrar vulnerabilidades e erros de segurança no seu código
 shortTitle: Codificação segura
-intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.'
+intro: 'Mantenha seu código seguro usando {% data variables.product.prodname_code_scanning %} para identificar e corrigir potenciais vulnerabilidades de segurança e outros erros no seu código.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### Índice
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% topic_link_in_list /using-codeql-code-scanning-with-your-existing-ci-system %}
-    {% link_in_list /running-codeql-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-codeql-code-scanning-in-your-ci-system %}
-    {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/pt-BR/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/integrating-with-code-scanning.md
index 35c6720dbe..a9fc4fb628 100644
--- a/translations/pt-BR/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/pt-BR/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index 867736cccc..c2af63b673 100644
--- a/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
 title: Gerenciar alertas de verificação de código para o seu repositório
 shortTitle: Gerenciando alertas
-intro: 'Da vista da segurança, você pode visualizar, corrigir, {% if currentVersion == "enterprise-server@2. 2" %}ou fechar{% else %}ignorar ou excluir{% endif %} alertas de potenciais vulnerabilidades ou erros no código do seu projeto.'
+intro: 'Da visão de segurança, você pode visualizar, corrigir, ignorar ou excluir alertas de potenciais vulnerabilidades ou erros no código do seu projeto.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre os alertas de {% data variables.product.prodname_code_scanning %}
@@ -60,7 +62,7 @@ Você precisa de permissão de gravação para visualizar um resumo de todos os
 
 Qualquer pessoa com permissão de gravação para um repositório pode corrigir um alerta, fazendo o commit de uma correção do código. Se o repositório tiver {% data variables.product.prodname_code_scanning %} agendado para ser executado em pull requests, recomenda-se registrar um pull request com sua correção. Isso ativará a análise de {% data variables.product.prodname_code_scanning %} referente às alterações e irá testar se sua correção não apresenta nenhum problema novo. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" e " "[Testar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
 
-Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra os alertas corrigidos e aqueles que os usuários têm {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra alertas e alertas corrigidos que os usuários ignoraram.
 
 Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico.
 
@@ -70,14 +72,6 @@ Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o
 ![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### Fechar um alerta
-
-Fechar um alerta é uma maneira de resolver um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### Ignorar ou excluir alertas
 
 Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você configurou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você configurou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**.
@@ -101,20 +95,9 @@ Ao excluir um alerta:
 
 Para ignorar ou excluir alertas:
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. Selecione o menu suspenso **Fechar** e clique em um motivo para fechar o alerta.    
-   ![Escolher o motivo para fechar o alerta no menu suspenso Fechar](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. Se você tem permissões de administrador para o repositório e deseja excluir alertas para esta ferramenta de {% data variables.product.prodname_code_scanning %}, selecione algumas ou todas as caixas de seleção e clique em **Excluir**.
 
    ![Excluir alertas](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,8 +128,6 @@ Para ignorar ou excluir alertas:
 
 Se um projeto tem vários alertas que você deseja ignorar pelo mesmo motivo, você pode ignorá-los em massa do resumo de alertas. Normalmente, você pode querer filtrar a lista e, em seguida, ignorar todos os alertas correspondentes. Por exemplo, você pode querer ignorar todos os alertas atuais no projeto que foram marcados para uma vulnerabilidade específica de Enumeração de Fraqueza Comum (CWE).
 
-{% endif %}
-
 ### Leia mais
 
 - "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/pt-BR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..6fec19123e
--- /dev/null
+++ b/translations/pt-BR/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Executando o CodeQL CLI no seu sistema de CI
+shortTitle: Executando o CodeQL de CLI
+intro: 'Você pode usar {% data variables.product.prodname_codeql_cli %} para executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em um sistema de integração contínua de terceiros.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Sobre o {% data variables.product.prodname_codeql_cli %}
+
+Você pode usar {% data variables.product.prodname_codeql_cli %} para executar o {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua (CI) de terceiros. {% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning).
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Como alternativa, você pode usar {% data variables.product.prodname_codeql_runner %} no seu sistema de CI, ou {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} dentro de {% data variables.product.product_name %}. Para obter uma visão geral das opções para os sistemas de CI, consulte "[Sobre o CodeQL {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". Para obter informações sobre {% data variables.product.prodname_code_scanning %} usando ações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
+
+{% note %}
+
+**Observação:** {% if currentVersion == "free-pro-team@latest" %}
+O {% data variables.product.prodname_codeql_cli %} é grátis para usar em repositórios públicos mantidos em {% data variables.product.prodname_dotcom_the_website %}, e disponível para uso em repositórios privados que são propriedade de clientes com uma licença de {% data variables.product.prodname_advanced_security %}. Para obter informações, consulte "[{% data variables.product.product_name %} Termos e Condições](https://securitylab.github.com/tools/codeql/license) de do CLI de {% data variables.product.prodname_codeql %} " e "[{% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
+{%- else %}O {% data variables.product.prodname_codeql_cli %} está disponível para clientes com uma licença de {% data variables.product.prodname_advanced_security %}.
+{% endif %}
+{% endnote %}
+
+### Fazer o download do {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. Por exemplo:
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)".
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> opção.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opção
+    </th>
+    
+    <th align="center">
+      Obrigatório
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Exemplo básico
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opção
+    </th>
+    
+    <th align="center">
+      Obrigatório
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. Para obter mais informações, consulte "<a href="/code-security/secure-coding/sarif-support-for-code-scanning">Suporte SARIF para {% data variables.product.prodname_code_scanning %}</a>".
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Exemplo básico
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opção
+    </th>
+    
+    <th align="center">
+      Obrigatório
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. Para obter mais informações, consulte "<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">Gerenciar configurações de segurança e análise do seu repositório</a>".
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Exemplo básico
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### Leia mais
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index edc91170e0..19786b2e08 100644
--- a/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -13,13 +13,19 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre {% data variables.product.prodname_code_scanning %} com uma compilação de contêiner
 
 Se você estiver configurando {% data variables.product.prodname_code_scanning %} para um idioma compilado e estiver criando o código em um ambiente de contêiner, a análise pode falhar com a mensagem de erro "Nenhum código fonte foi visto durante a compilação." Isso indica que {% data variables.product.prodname_codeql %} não conseguiu monitorar seu código da forma como foi compilado.
 
-Você precisa executar {% data variables.product.prodname_codeql %} no mesmo contêiner em que você cria o seu código. Isto se aplica independentemente de você usar {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Se você estiver usando {% data variables.product.prodname_codeql_runner %}, execute-o no contêiner onde seu código é criado. Para obter mais informações sobre {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)". Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)".
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Você deve executar {% data variables.product.prodname_codeql %} dentro do contêiner no qual você constrói seu código. Isso se aplica se você estiver usando o {% data variables.product.prodname_codeql_cli %}, o {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Para {% data variables.product.prodname_codeql_cli %} ou {% data variables.product.prodname_codeql_runner %}, consulte "[Executando {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)ou "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" para obter mais informações. Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)".
+{% else %}
+Você deve executar {% data variables.product.prodname_codeql %} dentro do contêiner no qual você constrói seu código. Isso se aplica se você estiver usando {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Para {% data variables.product.prodname_codeql_runner %}, consulte "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" para obter mais informações. Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)".
+{% endif %}
 
 ### Dependências
 
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/pt-BR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..ccb58b2177
--- /dev/null
+++ b/translations/pt-BR/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Executando um executor de CodeQL no seu sistema de CI
+shortTitle: Executando um executor de CodeQL
+intro: 'Você pode usar {% data variables.product.prodname_codeql_runner %} para executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em um sistema de integração contínua de terceiros.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Sobre o {% data variables.product.prodname_codeql_runner %}
+
+O {% data variables.product.prodname_codeql_runner %} é uma ferramenta que você pode usar para executar {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua de terceiros (CI). {% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning).
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Em muitos casos, é mais fácil configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql_cli %} diretamente no seu sistema de CI. O executor é mais complexo e menos clemente para ser configurado do que o CLI, e é recomendado apenas se você precisar da sua capacidade de analisar várias linguagens compiladas com uma única compilação, ou para integrar-se a processos de compilação complexos. Para obter mais informações, consulte "[Sobre a verificação de código CodeQL no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Como alternativa, você pode usar {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}. Para obter informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)".
+
+O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que executa a análise de {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Você adiciona o executor ao seu sistema de terceiros e, em seguida, chama o executor para analisar o código e fazer o upload dos resultados para o {% data variables.product.product_name %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório.
+
+{% note %}
+
+**Observação:**
+{% if currentVersion == "free-pro-team@latest" %}
+* O {% data variables.product.prodname_codeql_runner %} usa o CLI de {% data variables.product.prodname_codeql %} para analisar o código e, portanto, tem as mesmas condições da licença. É grátis usar em repositórios públicos que são mantidos no {% data variables.product.prodname_dotcom_the_website %}, e disponíveis para uso em repositórios privados que são propriedade de clientes com uma licença do {% data variables.product.prodname_advanced_security %}. Para obter informações, consulte "[{% data variables.product.product_name %} Termos e Condições](https://securitylab.github.com/tools/codeql/license) de do CLI de {% data variables.product.prodname_codeql %} " e "[{% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
+{% else %}
+* O {% data variables.product.prodname_codeql_runner %} está disponível para os clientes com uma licença de {% data variables.product.prodname_advanced_security %}.
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* O {% data variables.product.prodname_codeql_runner %} não deve ser confundido com o CLI de {% data variables.product.prodname_codeql %}. A CLI de {% data variables.product.prodname_codeql %} é uma interface de linha de comando que permite que você crie bancos de dados de {% data variables.product.prodname_codeql %} para pesquisa de segurança e executar consultas de {% data variables.product.prodname_codeql %}. Para obter mais informações, consulte "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)".
+{% endif %}
+{% endnote %}
+
+### Fazer o download do {% data variables.product.prodname_codeql_runner %}
+
+Você pode fazer o download de {% data variables.product.prodname_codeql_runner %} de https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. Em alguns sistemas operacionais, talvez você precise alterar as permissões para o arquivo baixado antes de executá-lo.
+
+No Linux:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+No macOS:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+No Windows, o arquivo `codeql-runner-win.exe` normalmente não exige alteração de permissões.
+
+### Adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de CI
+
+Após fazer o download de {% data variables.product.prodname_codeql_runner %} e verificar se pode ser executado, você deverá disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. Por exemplo, você pode configurar cada servidor para que copie o executor de um local central interno. Como alternativa, você poderia usar a API REST para obter o executor diretamente do {% data variables.product.prodname_dotcom %}, por exemplo:
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+Além disso, cada servidor de CI também precisa:
+
+- Um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para {% data variables.product.prodname_codeql_runner %} usar. Você deve usar um token de acesso com o escopo do `repositório`, ou um {% data variables.product.prodname_github_app %} com a permissão de gravação de `security_events` e `metadados` e permissões de leitura de `conteúdo`. Para obter informações, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)".
+- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. Este pacote contém consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %} mais o CLI de {% data variables.product.prodname_codeql %}, que é usado internamente pelo executor. Para obter informações, consulte "[CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
+
+As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são:
+
+1. Permita o acesso dos servidores de CI a https://{% if currentVersion == "free-pro-team@latest" %}github. om{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action para que {% data variables.product.prodname_codeql_runner %} possa fazer o download do pacote automaticamente.
+1. Faça o download/extraia o pacote manualmente, armazene-o com outros recursos centrais e use <nobr>`--codeql-path`</nobr> o sinalizador para especificar o local do pacote nas chamadas para inicializar o {% data variables.product.prodname_codeql_runner %}.
+
+### Chamar {% data variables.product.prodname_codeql_runner %}
+
+Você deve chamar {% data variables.product.prodname_codeql_runner %} no local de checkout do repositório que deseja analisar. Os dois comandos principais são:
+
+1. `init` necessário para inicializar o executor e criar um banco de dados de {% data variables.product.prodname_codeql %} para que cada linguagem seja analisada. Estas bases de dados são preenchidas e analisadas por comandos subsequentes.
+1. `análise` necessário para preencher os bancos de dados {% data variables.product.prodname_codeql %}, analisá-los e fazer o upload dos resultados para {% data variables.product.product_name %}.
+
+Para ambos os comandos, você deve especificar a URL de {% data variables.product.product_name %}, o repositório **OWNER/NAME e o {% data variables.product.prodname_github_apps %} ou token de acesso pessoal para usar para autenticação. Você também precisa especificar a localização do pacote CodeQL, a menos que o servidor CI tenha acesso para fazer o download diretamente do repositório `github/codeql-action`.
+
+Você pode configurar o local onde o {% data variables.product.prodname_codeql_runner %} armazena o pacote do CodeQL para futuras análises em um servidor usando o sinalizador <nobr>`--tools-dir`</nobr> e onde armazena arquivos temporários durante a análise usando <nobr>`--temp-dir`</nobr>.
+
+Para visualizar a referência de linha de comando para o executor, use o sinalizador `-h`. Por exemplo, para listar todos os comandos executados: `codeql-runner-OS -h` ou para listar todos os sinalizadores disponíveis para o comando `init` executado: `codeql-runner-OS init -h` (em que `OS` varia de acordo com o executável que você está usando). Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)".
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### Exemplo básico
+
+Este exemplo executa a análise do {% data variables.product.prodname_codeql %} em um servidor de Linux CI para o repositório `octo-org/example-repo` hospedado em `{% data variables.command_line.git_url_example %}`. O processo é muito simples porque o repositório contém apenas linguagens que podem ser analisadas diretamente pelo {% data variables.product.prodname_codeql %}, sem ser criado (ou seja, Go, JavaScript, Python e TypeScript).
+
+Neste exemplo, o servidor tem acesso para fazer o download do pacote {% data variables.product.prodname_codeql %} diretamente do repositório `github/codeql-action`. Portanto, não há necessidade de usar o sinalizador `--codeql-path`.
+
+1. Confira o repositório a ser analisado.
+1. Mova para o diretório para o local onde o repositório está reservado.
+1. Inicialize {% data variables.product.prodname_codeql_runner %} e crie banco de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Banco de dados do CodeQL criado em /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### Exemplo de linguagem compilada
+
+Este exemplo é semelhante ao exemplo anterior. No entanto, desta vez, o repositório tem o código em C/C++, C# ou Java. Para criar um banco de dados de {% data variables.product.prodname_codeql %} para essas linguagens, o CLI precisa monitorar a criação. No final do processo de inicialização, o executor informa o comando que você precisa configurar o ambiente antes de criar o código. Você precisa executar esse comando antes de chamar o processo de criação normal da CI e, em seguida, executar o comando `analisar`.
+
+1. Confira o repositório a ser analisado.
+1. Mova para o diretório para o local onde o repositório está reservado.
+1. Inicialize {% data variables.product.prodname_codeql_runner %} e crie banco de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Exporte essas variáveis para processos futuros para que o CodeQL possa monitorar a criação, por exemplo, executando 
+". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. Extraia o script gerado pela ação `iniciar` para configurar o ambiente a fim de monitorar a criação. Observe o ponto e espaço principal no seguinte trecho do código.
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. Crie o código. No macOS, você precisa prefixar o comando de criação com a variável de ambiente `$CODEQL_RUNNER`. Para obter mais informações, consulte "[Solução de problemas {% data variables.product.prodname_codeql_runner %} no seu sistema CI](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**Observação:** Se você usar uma criação conteinerizada, você deverá executar o {% data variables.product.prodname_codeql_runner %} no contêiner em que ocorre a tarefa de criação.
+
+{% endnote %}
+
+### Leia mais
+
+- "[Configurar {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[Solução de problemas de {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
diff --git a/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index d23c28b54a..ede0d8df7a 100644
--- a/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: Suporte SARIF para a varredura de código
 shortTitle: Suporte SARIF
 intro: 'Para exibir os resultados de uma ferramenta de análise estática de terceiros no seu repositório no {% data variables.product.prodname_dotcom %}, você precisará dos resultados armazenados em um arquivo SARIF que seja compatível com um subconjunto específico do esquema SARIF 2.1.0 JSON para varredura de código. Se você usar o mecanismo de análise estática padrão do {% data variables.product.prodname_codeql %}, os resultados aparecerão automaticamente no seu repositório no {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre o suporte SARIF
@@ -22,7 +25,15 @@ SARIF (Formato de Intercâmbio de Resultados de Análise Estática) é um [OASIS
 
 Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)". Para obter mais informações sobre o esquema SARIF 2.1.0 JSON, consulte [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. Para mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" ou "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)".
+Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" ou "[Executar {% data variables.product.prodname_codeql_runner %} no seu sistema CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)".
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Se você estiver usando o {% data variables.product.prodname_codeql_cli %}, especifique a versão do SARIF a ser usada. Para obter mais informações, consulte "[Executar {% data variables.product.prodname_codeql_cli %} no seu sistema CI](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)".{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
 
 {% data variables.product.prodname_dotcom %} usa propriedades no arquivo SARIF para exibir alertas. Por exemplo, `shortDescription` e `fullDescription` aparecem na parte superior de um alerta de {% data variables.product.prodname_code_scanning %}. O `local` permite que {% data variables.product.prodname_dotcom %} mostre anotações no seu arquivo de código. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
 
@@ -122,6 +133,45 @@ Um local dentro de um artefato de programação, como, por exemplo, um arquivo n
 | `region.endLine`       | **Requerido.** O número da linha do último caractere na região.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | `region.endColumn`     | **Obrigatório.** O número da coluna do caractere após o final da região.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| Nome | Descrição                                                                                                                                                                                                                             |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id` | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | categoria         | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
+
 ### Exemplos de arquivos de saída SARIF
 
 Estes exemplos de arquivos de saída SARIF mostram as propriedades compatíveis e os valores de exemplo.
@@ -130,7 +180,6 @@ Estes exemplos de arquivos de saída SARIF mostram as propriedades compatíveis
 
 Este arquivo de saída SARIF tem exemplo de valores para mostrar as propriedades mínimas necessárias para que os resultados de {% data variables.product.prodname_code_scanning %} funcionem conforme esperado. Se você remover qualquer propriedade ou não incluir valores, esses dados não serão exibidos corretamente e não serão sincronizados em {% data variables.product.prodname_dotcom %}.
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ Este arquivo de saída SARIF tem exemplo de valores para mostrar as propriedades
 
 Este arquivo de saída SARIF tem valores de exemplo para mostrar todas as propriedades do SARIF compatíveis com {% data variables.product.prodname_code_scanning %}.
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ Este arquivo de saída SARIF tem valores de exemplo para mostrar todas as propri
   ]
 }
 ```
+{% endif %}
diff --git a/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
index 0dc85b3520..cf0a3359e8 100644
--- a/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
+++ b/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
@@ -17,6 +17,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index 24ce40f6f2..4c42c7f891 100644
--- a/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -14,13 +14,15 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre os resultados de {% data variables.product.prodname_code_scanning %} em pull requests
 
 Em repositórios onde {% data variables.product.prodname_code_scanning %} está configurado como uma verificação de pull request, {% data variables.product.prodname_code_scanning %} verifica o código no pull request. Por padrão, isso é limitado a pull requests que visam o branch-padrão ou branches protegidos, mas você pode alterar esta configuração em {% data variables.product.prodname_actions %} ou em um sistema de CI/CD de terceiros. Se o merge das alterações introduziria novos alertas de {% data variables.product.prodname_code_scanning %} no branch de destino, estes serão relatados como resultados de verificação no pull request. Os alertas também são exibidos como anotações na aba **Arquivos alterados** do pull request. Se você tiver permissão de gravação no repositório, você poderá ver qualquer alerta de {% data variables.product.prodname_code_scanning %} existente na aba **Segurança**. Para obter informações sobre os alertas do repositório, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} do repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)".
 
-Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido usar {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou {% if currentVersion == "enterprise-server@2.22" %}fechar{% else %}ignorar{% endif %} todos os erros alertas antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
+Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request for direcionado a um branch protegido que usa {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório tiver configurado as verificações de status obrigatórias, você deverá corrigir ou ignorar todos os alertas de erro antes que o pull request poder fazer o merge do pull request. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
 
 ![Ocorreu uma falha na verificação de {% data variables.product.prodname_code_scanning %} em um pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -44,18 +46,10 @@ Na visualização detalhada de um alerta, algumas ferramentas de {% data variabl
 
 ![Descrição do alerta e link para mostrar mais informações](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolvendo{% else %}Corrigindo{% endif %} um alerta no seu pull request
+### Corrigir de um alerta no seu pull request
 
 Qualquer pessoa com acesso push a um pull request pode corrigir um alerta de {% data variables.product.prodname_code_scanning %} que seja identificado nesse pull request. Se você fizer commit de alterações na solicitação do pull request, isto acionará uma nova execução das verificações do pull request. Se suas alterações corrigirem o problema, o alerta será fechado e a anotação removida.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-Se você não considera que um alerta deve ser corrigido, os usuários com permissão de gravação podem fechar o alerta manualmente. {% data reusables.code-scanning.close-alert-examples %} O botão **Fechar** está disponível nas anotações e no modo de exibição de alertas se você tiver permissão de gravação no repositório.
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 ### Ignorar um alerta no seu pull request
 
 Uma forma alternativa de fechar um alerta é ignorá-lo. Você pode descartar um alerta se não acha que ele precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Se você tem permissão de gravação no repositório, o botão **Ignorar** estará disponível nas anotações de código e no resumo de alertas. Ao clicar em **Ignorar** será solicitado que você escolha um motivo para fechar o alerta.
@@ -67,5 +61,3 @@ Uma forma alternativa de fechar um alerta é ignorá-lo. Você pode descartar um
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 Para obter mais informações sobre alertas ignorados, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)".
-
-{% endif %}
diff --git a/translations/pt-BR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..eed3c00518
--- /dev/null
+++ b/translations/pt-BR/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: Solução de problemas do executor do CodeQL no seu sistema de CI
+shortTitle: Solução de problemas do executor do CodeQL
+intro: 'Se você tiver problemas com {% data variables.product.prodname_codeql_runner %}, você poderá solucionar esses problemas usando essas dicas.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### O comando `init` leva muito tempo
+
+Antes de o {% data variables.product.prodname_codeql_runner %} poder criar e analisar o código, ele precisa acessar o pacote de {% data variables.product.prodname_codeql %} que contém a CLI de {% data variables.product.prodname_codeql %} e as bibliotecas de {% data variables.product.prodname_codeql %}.
+
+Ao usar o {% data variables.product.prodname_codeql_runner %} pela primeira vez na sua máquina, o comando `init` faz o download do pacote de {% data variables.product.prodname_codeql %} para a sua máquina. Este download pode levar alguns minutos. O pacote de {% data variables.product.prodname_codeql %} fica armazenado em cache entre as execuções. Portanto, se você usar o {% data variables.product.prodname_codeql_runner %} novamente na mesma máquina, ele não fará o download do pacote de {% data variables.product.prodname_codeql %} novamente.
+
+Para evitar este download automático, você pode fazer o download manualmente do pacote de {% data variables.product.prodname_codeql %} para a sua máquina e especificar o caminho usando o parâmetro `--codeql-path` do comando `init`.
+
+### Nenhum código encontrado durante a criação
+
+Se o comando `analisar` para o {% data variables.product.prodname_codeql_runner %} falhar com um erro `Nenhum código fonte foi visto durante a criação`, isto indica que {% data variables.product.prodname_codeql %} não conseguiu monitorar o seu código. Há várias explicações para essa falha.
+
+1. A detecção automática da linguagem identificou uma linguagem compatível, mas não há código analisável dessa linguagem no repositório. Um exemplo típico é quando nosso serviço de detecção de linguagem encontra um arquivo associado a uma determinada linguagem de programação, como um arquivo `.h`, or `.gyp`, mas nenhum código executável correspondente está presente no repositório. Para resolver o problema, você pode definir manualmente as linguagens que você deseja analisar usando o sinalizador `--languages` do comando `init`. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)".
+
+1. Você está analisando uma linguagem compilada sem usar o comando `autobuild` e você mesmo executa os passos de criação após a etapa `init`. Para que a construção funcione, você deverá configurar o ambiente de modo que o {% data variables.product.prodname_codeql_runner %} possa monitorar o processo de construção. O comando `init` gera instruções sobre como exportar as variáveis de ambiente necessárias. Portanto, você pode copiar e executar o script depois de executar o comando `init`.
+   - No macOS e no Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - No Windows, usando o shell de comando (`cmd`) ou um arquivo de lote (`.bat`):
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - No Windows, usando o PowerShell:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   As variáveis de ambiente também são armazenadas no arquivo `codeql-runner/codeql-env.json`. Este arquivo contém um único objeto JSON que mapeia chaves de variável de ambiente com valores. Se você não conseguir executar o script gerado pelo comando `init`, você poderá usar os dados no formato JSON.
+
+   {% note %}
+
+   **Observação:**Se você usou o sinalizador `--temp-dir` do comando `init` para especificar um diretório personalizado para arquivos temporários, o caminho para os arquivos `codeql-env` podem ser diferentes.
+
+   {% endnote %}
+
+1. Você está analisando uma linguagem compilada no macOS sem usar o comando `autobuild` e você mesmo executa os passos de compilação após a etapa `init`. Se a opção SIP (Proteção da Integridade do Sistema) estiver habilitada, que é o padrão nas versões recentes do OSX, poderá ocorrer uma falha na análise. Para corrigir isso, prefixe o comando de compilação com a variável de ambiente `$CODEQL_RUNNER`. Por exemplo, se seu comando de criação for `cmd arg1 arg2`, você deverá executar `$CODEQL_RUNNER cmd arg1 arg2`.
+
+1. O código é criado em um contêiner ou em uma máquina separada. Se você usar uma criação em contêiner ou se você externalizar a criação para outra máquina, certifique-se de executar {% data variables.product.prodname_codeql_runner %} no contêiner ou na máquina onde a tarefa de criação ocorrer. Para obter mais informações, consulte "[Executar a varredura de código do CodeQL em um contêiner](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)".
diff --git a/translations/pt-BR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
index 2d879ca48d..9e8dc35fbc 100644
--- a/translations/pt-BR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
+++ b/translations/pt-BR/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -33,19 +35,22 @@ Se ocorrer uma falha na uma criação automática de código para uma linguagem
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
         matrix:
           language: ['csharp', 'cpp', 'javascript']
 
+      steps:
       ...
-
-      - name: Initialize {% data variables.product.prodname_codeql %}
-        uses: github/codeql-action/init@v1
-        with:
-          languages: {% raw %}${{ matrix.language }}{% endraw %}
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: github/codeql-action/init@v1
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
   Para obter mais informações sobre a edição do fluxo de trabalho, consulte "[Configurar a varredura de código](/code-security/secure-coding/configuring-code-scanning)".
@@ -148,29 +153,29 @@ commit for best results.
 Corrija isto removendo as seguintes linhas do fluxo de trabalho {% data variables.product.prodname_codeql %}. Essas linhas foram incluídas na seção `etapas` do trabalho `Analyze` nas versões iniciais do fluxo de trabalho de {% data variables.product.prodname_codeql %}.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 A seção revisada de `etapas` do fluxo de trabalho será parecida com esta:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 Para obter mais informações sobre a edição do arquivo de fluxo de trabalho {% data variables.product.prodname_codeql %}, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)".
diff --git a/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index 6a68127aa3..f74d922149 100644
--- a/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -24,18 +26,19 @@ O {% data variables.product.prodname_dotcom %} cria alertas de {% data variables
 
 Você pode gerar arquivos SARIF usando muitas ferramentas de teste de segurança de análise estática, incluindo {% data variables.product.prodname_codeql %}. Para fazer o upload dos resultados das ferramentas de terceiros, você deve usar o formato Intercâmbio de Resultados de Análise Estática (SARIF) 2.1.0. Para obter mais informações, consulte "[Suporte SARIF para {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)".
 
-Você pode fazer o upload dos resultados usando {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2. 2" %} (disponível se sua organização participa do programa beta){% endif %}, a API de {% data variables.product.prodname_code_scanning %} ou {% data variables.product.prodname_codeql_runner %}. O melhor método de upload dependerá de como você gera o arquivo SARIF. Por exemplo, se você usar:
+Você pode enviar os resultados usando {% data variables.product.prodname_actions %}, a API de {% data variables.product.prodname_code_scanning %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}ou {% data variables.product.prodname_codeql_runner %}. O melhor método de upload dependerá de como você gera o arquivo SARIF. Por exemplo, se você usar:
 
 - {% data variables.product.prodname_actions %} para executar a ação {% data variables.product.prodname_codeql %}, não haverá nenhuma ação adicional necessária. A ação {% data variables.product.prodname_codeql %} faz o upload do arquivo SARIF automaticamente quando ele conclui a análise.
-- O arquivo SARIF pode ser gerado a partir de uma ferramenta de análise compatível com o SARIF, que você executa no mesmo fluxo de trabalho de {% data variables.product.prodname_actions %} usado para fazer o upload do arquivo.
-- {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. Se você bloquear o envio automático, quando você estiver pronto para enviar resultados, você poderá usar o comando `upload` (para mais informações, consulte "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)").
+- O arquivo SARIF pode ser gerado a partir de uma ferramenta de análise compatível com o SARIF, que você executa no mesmo fluxo de trabalho de {% data variables.product.prodname_actions %} usado para fazer o upload do arquivo. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - O {% data variables.product.prodname_codeql_cli %} para executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI, você pode usar a CLI para fazer o upload de resultados para {% data variables.product.prodname_dotcom %} (para mais informações, consulte "[Executando {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. Se você bloquear o upload automático, quando você estiver pronto para fazer o upload dos resultados, você poderá usar o comando `enviar` (para mais informações, ver "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").
 - Uma ferramenta que gera resultados como um artefato fora do seu repositório, você pode usar a API de {% data variables.product.prodname_code_scanning %} para fazer o upload do arquivo (para mais informações, consulte "[Enviar uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
 
 ### Fazer o upload uma análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_actions %}
 
-Para fazer o upload de um arquivo SARIF de terceiros para {% data variables.product.prodname_dotcom %}, você precisará de um fluxo de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprender {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" e "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
+Para fazer o upload de um arquivo SARIF de terceiros para {% data variables.product.prodname_dotcom %}, você precisará de um fluxo de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
 O seu fluxo de trabalho precisará usar a ação `upload-sarif`, que tem parâmetros de entrada que você pode usar para configurar o upload. Ele tem parâmetros de entrada que você pode usar para configurar o upload. O parâmetro de entrada principal que você usará é `sarif-file`, que configura o arquivo ou diretório dos arquivos SARIF a serem carregados. O diretório ou caminho do arquivo é relativo à raiz do repositório. Para mais informações, consulte a ação [`upload-sarif`](https://github.com/github/codeql-action/tree/HEAD/upload-sarif).
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Exemplo de fluxo de trabalho que executa a ferramenta de análise ESLint
@@ -87,7 +92,7 @@ Este exemplo de fluxo de trabalho é executado sempre que os commits são carreg
 
 O fluxo de trabalho mostra um exemplo de execução da ferramenta de análise estática ESLint como uma etapa de um fluxo de trabalho. A etapa `Executar ESLint` executa a ferramenta ESLint e produz o arquivo `results.sarif`. Em seguida, o fluxo de trabalho faz o upload do arquivo `results.sarif` para {% data variables.product.prodname_dotcom %} usando a ação `upload-sarif`. Para obter mais informações sobre a criação de um arquivo de fluxo de trabalho, consulte "[Introdução ao GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Leia mais
 
 - "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
-- "[Visualizar o seu histórico de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
+- "[Visualizando o seu histórico de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[Cerca de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Executando {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
 - "[Fazer o upload de uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
diff --git a/translations/pt-BR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/pt-BR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index 1951bb5383..d5e951eba5 100644
--- a/translations/pt-BR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/pt-BR/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index b802a1c358..1909c04538 100644
--- a/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -43,7 +43,7 @@ Publicar os detalhes de uma vulnerabilidade de segurança não faz com que os ma
 
 O processo de relatório e divulgação de vulnerabilidades para projetos em {% data variables.product.prodname_dotcom_the_website %} é o seguinte:
 
- Se você é um relator de vulnerabilidades (por exemplo, um pesquisador de segurança) que gostaria de relatar uma vulnerabilidade, primeiro verifique se existe uma política de segurança para o repositório relacionado. Para obter mais informações, consulte "[Sobre políticas de segurança](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)". Se houver uma, siga-a para entender o processo antes de entrar em contato com a equipe de segurança do repositório.
+ Se você é um relator de vulnerabilidades (por exemplo, um pesquisador de segurança) que gostaria de relatar uma vulnerabilidade, primeiro verifique se existe uma política de segurança para o repositório relacionado. Para obter mais informações, consulte "[Sobre políticas de segurança](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)". Se houver uma, siga-a para entender o processo antes de entrar em contato com a equipe de segurança do repositório.
 
  Se não houver uma política de segurança, a forma mais eficiente de estabelecer um meio privado de comunicação com os mantenedores é criar uma problema, solicitando um contato de segurança preferido. Vale a pena notar que o problema será imediatamente visível ao público. Portanto, não deve incluir nenhuma informação sobre o erro. Quando a comunicação for estabelecida, você poderá sugerir que os mantenedores definam uma política de segurança para uso futuro.
 
@@ -55,7 +55,7 @@ O processo de relatório e divulgação de vulnerabilidades para projetos em {%
 
  Se você encontrou uma vulnerabilidade de segurança em {% data variables.product.prodname_dotcom_the_website %}, informe a vulnerabilidade por meio de nosso processo de divulgação coordenada. Para obter mais informações, consulte o site [{% data variables.product.prodname_dotcom %} Recompensa por Erros de Segurança](https://bounty.github.com/).
 
- Se for mantenedor, você poderá assumir a propriedade do processo no início do pipeline, configurando uma política de segurança para o seu repositório, ou disponibilizando as instruções de relatórios de segurança de forma clara, por exemplo, no arquivo LEIAME do seu projeto. Para obter informações sobre como adicionar uma política de segurança, consulte "[Sobre políticas de segurança](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)". Se não houver política de segurança, é provável que um relator de vulnerabilidade tente enviar um e-mail para você ou entrar em contato com você de forma privada. Como alternativa, alguém pode abrir um problema (público) com detalhes de um problema de segurança.
+ Se for mantenedor, você poderá assumir a propriedade do processo no início do pipeline, configurando uma política de segurança para o seu repositório, ou disponibilizando as instruções de relatórios de segurança de forma clara, por exemplo, no arquivo LEIAME do seu projeto. Para obter informações sobre como adicionar uma política de segurança, consulte "[Sobre políticas de segurança](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)". Se não houver política de segurança, é provável que um relator de vulnerabilidade tente enviar um e-mail para você ou entrar em contato com você de forma privada. Como alternativa, alguém pode abrir um problema (público) com detalhes de um problema de segurança.
 
  Como mantenedor, para divulgar uma vulnerabilidade no seu código, você primeiro cria um rascunho de uma consultoria de segurança no repositório do pacote em {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories).
 
diff --git a/translations/pt-BR/content/code-security/security-advisories/index.md b/translations/pt-BR/content/code-security/security-advisories/index.md
index d6222f2058..f17352813c 100644
--- a/translations/pt-BR/content/code-security/security-advisories/index.md
+++ b/translations/pt-BR/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### Índice
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md b/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md
index a35975ecb1..a923940809 100644
--- a/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md
+++ b/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md
@@ -13,7 +13,7 @@ versions:
 
 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. 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 "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 
-The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. Para obter mais informações, consulte "[Sobre proteger seu repositório](/code-security/getting-started/about-securing-your-repository).
+A visão geral de segurança indica se as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão habilitadas para repositórios pertencentes à sua organização e consolida alertas das funcionalidades de {% data variables.product.prodname_advanced_security %}, incluindo alertas de {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot_alerts %} e alertas de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações, consulte "[Sobre proteger seu repositório](/code-security/getting-started/about-securing-your-repository).
 
 No resumo da segurança, é possível visualizar, ordenar e filtrar alertas para entender os riscos de segurança na sua organização e nos repositórios específicos. Você pode aplicar vários filtros para concentrar-se em áreas de interesse. Por exemplo, você pode identificar repositórios privados que têm um número elevado de {% data variables.product.prodname_dependabot_alerts %} ou repositórios que não têm alertas {% data variables.product.prodname_code_scanning %}.
 
@@ -87,33 +87,33 @@ O nível de risco para um repositório é determinado pelo número e gravidade d
 | `enabled:dependabot-alerts`     | Exibe repositórios com {% data variables.product.prodname_dependabot_alerts %} habilitado.         |
 | `not-enabled:dependabot-alerts` | Exibe repositórios que não têm {% data variables.product.prodname_dependabot_alerts %} habilitado. |
 
-#### Filter by repository type
+#### Filtrar por tipo de repositório
 
-| Qualifier       | Descrição                      |
-| --------------- | ------------------------------ |
-| `is:public`     | Display public repositories.   |
-| `is:internal`   | Display internal repositories. |
-| `is:private`    | Display private repositories.  |
-| `archived:true` | Display archived repositories. |
+| Qualifier       | Descrição                       |
+| --------------- | ------------------------------- |
+| `is:public`     | Exibir repositórios públicos.   |
+| `is:internal`   | Exibir repositórios internos.   |
+| `is:private`    | Exibir repositórios privados.   |
+| `archived:true` | Exibir repositórios arquivados. |
 
-#### Filter by team
+#### Filtrar por equipe
 
-| Qualifier                 | Descrição                                                        |
-| ------------------------- | ---------------------------------------------------------------- |
-| <code>team:<em>TEAM-NAME</em></code> | Displays repositories that *TEAM-NAME* has admin privileges for. |
+| Qualifier                 | Descrição                                                                         |
+| ------------------------- | --------------------------------------------------------------------------------- |
+| <code>team:<em>TEAM-NAME</em></code> | Exibe os repositórios para os quais *TEAM-NAME* tem privilégios de administrador. |
 
-#### Filter by topic
+#### Filtrar por tópico
 
 | Qualifier                 | Descrição                                                    |
 | ------------------------- | ------------------------------------------------------------ |
-| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+| <code>topic:<em>TOPIC-NAME</em></code> | Exibe repositórios que são classificados com o *TOPIC-NAME*. |
 
-#### Sort the list of alerts
+#### Classificar a lista de alertas
 
-| Qualifier                     | Descrição                                                                                                                     |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `sort:risk`                   | Sorts the repositories in your security overview by risk.                                                                     |
-| `sort:repos`                  | Sorts the repositories in your security overview alphabetically by name.                                                      |
-| `sort:code-scanning-alerts`   | Sorts the repositories in your security overview by number of {% data variables.product.prodname_code_scanning %} alerts.   |
-| `sort:secret-scanning-alerts` | Sorts the repositories in your security overview by number of {% data variables.product.prodname_secret_scanning %} alerts. |
-| `sort:dependabot-alerts`      | Sorts the repositories in your security overview by number of {% data variables.product.prodname_dependabot_alerts %}.      |
+| Qualifier                     | Descrição                                                                                                                                |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| `sort:risk`                   | Classifica os repositórios na visão geral de segurança por risco.                                                                        |
+| `sort:repos`                  | Classifica alfabeticamente pelo nome os repositórios na sua visão geral de segurança.                                                    |
+| `sort:code-scanning-alerts`   | Classifica os repositórios na visão geral de segurança por número de alertas de {% data variables.product.prodname_code_scanning %}.   |
+| `sort:secret-scanning-alerts` | Classifica os repositórios na visão geral de segurança por número de alertas de {% data variables.product.prodname_secret_scanning %}. |
+| `sort:dependabot-alerts`      | Classifica os repositórios na sua visão geral de segurança por número de {% data variables.product.prodname_dependabot_alerts %}.      |
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
index 07c09090ba..c9d72aa443 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre alertas para dependências vulneráveis
-intro: '{% data variables.product.product_name %} envia {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} quando detectarmos vulnerabilidades que afetam o repositório.'
+intro: 'O {% data variables.product.product_name %} envia {% data variables.product.prodname_dependabot_alerts %} quando detectamos vulnerabilidades que afetam o seu repositório.'
 redirect_from:
   - /articles/about-security-alerts-for-vulnerable-dependencies
   - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
@@ -12,6 +12,7 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
 
 ### Sobre as dependências vulneráveis
@@ -22,12 +23,12 @@ Quando o seu código depende de um pacote que tenha uma vulnerabilidade de segur
 
 ### Detecção de dependências vulneráveis
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %} detecta dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %} alertas{% else %}{% data variables.product.product_name %} detecta dependências vulneráveis e envia alertas de segurança{% endif %} quando:
+{% data variables.product.prodname_dependabot %} detecta dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %} quando:
 
 {% if currentVersion == "free-pro-team@latest" %}
-- Uma nova vulnerabilidade foi adicionada ao {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança em {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)".{% else %}
-- São sincronizados novos dados de consultoria com {% data variables.product.prodname_ghe_server %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre dados de consultoria, consulte "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Procurar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}</a>{% endif %}
-- O gráfico de dependências para alterações de repositório. Por exemplo, quando um colaborador faz push de um commit para alterar os pacotes ou versões de que depende{% if currentVersion == "free-pro-team@latest" %} ou quando o código de uma das dependências muda{% endif %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
+- Uma nova vulnerabilidade foi adicionada ao {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança em {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" e "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %}
+- São sincronizados novos dados de consultoria com {% data variables.product.prodname_ghe_server %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+- O gráfico de dependências para alterações de repositório. Por exemplo, quando um colaborador faz push de um commit para alterar os pacotes ou versões de que depende{% if currentVersion == "free-pro-team@latest" %} ou quando o código de uma das dependências muda{% endif %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/code-security/supply-chain-security/about-the-dependency-graph)".
 
 {% data reusables.repositories.dependency-review %}
 
@@ -39,58 +40,41 @@ Para obter uma lista dos ecossistemas para os quais o {% data variables.product.
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
 ### Alertas do {% data variables.product.prodname_dependabot %} para dependências vulneráveis
-{% else %}
-### Alertas de segurança para dependências vulneráveis
-{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% 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.
 
-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. 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)."
+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)".
 
-For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
+Para informações sobre os requisitos de permissão para ações relacionadas a {% data variables.product.prodname_dependabot_alerts %}, consulte "[Níveis de permissão do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)".
 
 {% data variables.product.product_name %} começa a gerar o gráfico de dependências imediatamente e gera alertas para quaisquer dependências vulneráveis assim que forem identificadas. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Para obter mais informações, consulte "[Gerenciando configurações do uso de dados de seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)".
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 Quando {% data variables.product.product_name %} identifica uma dependência vulnerável, geramos um alerta de {% data variables.product.prodname_dependabot %} e o exibimos na aba Segurança do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.product_name %} também notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)".
-{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 Para repositórios em que {% data variables.product.prodname_dependabot_security_updates %} estão habilitados, o alerta também pode conter um link para um pull request para atualizar o manifesto ou arquivo de bloqueio para a versão mínima que resolve a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Quando {% data variables.product.product_name %} identifica uma dependência vulnerável, enviamos um alerta de segurança de para os mantenedores dos repositórios afetados, com informações sobre a vulnerabilidade, um link para o arquivo afetado no projeto, bem como informações sobre uma versão corrigida.
-{% endif %}
-
 {% warning %}
 
 **Observação**: Os recursos de segurança de {% data variables.product.product_name %} não reivindicam garantem que todas as vulnerabilidades sejam detectadas. Embora estejamos sempre tentando atualizar nosso banco de dados de vulnerabilidades e gerar alertas com nossas informações mais atualizadas. não seremos capazes de pegar tudo ou falar sobre vulnerabilidades conhecidas dentro de um período de tempo garantido. Esses recursos não substituem a revisão humana de cada dependência em busca de possíveis vulnerabilidades ou algum outro problema, e nossa sugestão é consultar um serviço de segurança ou realizar uma revisão completa de vulnerabilidade quando necessário.
 
 {% endwarning %}
 
-### Acesso a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %}
+### Acesso a alertas de {% data variables.product.prodname_dependabot %}
 
-É possível ver todos os alertas que afetam um determinado projeto{% if currentVersion == "free-pro-team@latest" %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository){% endif %}
+É possível ver todos os alertas que afetam um determinado projeto{% if currentVersion == "free-pro-team@latest" %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository). "
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
+Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)".
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Enviamos alertas de segurança para as pessoas com permissões de administrador nos repositórios afetados por padrão. O {% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório.
-{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)".
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para mais informações, consulte "[Escolher o método de entrega para as suas notificações](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-Você também pode ver todos os {% data variables.product.prodname_dependabot_alerts %} que correspondem a uma vulnerabilidade particular em {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)".
-{% endif %}
+Você também pode ver todos os {% data variables.product.prodname_dependabot_alerts %} que correspondem a uma vulnerabilidade particular em {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Leia mais
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index 66948ffa41..8107c4f0af 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -35,6 +35,7 @@ Você especifica com que frequência verifica cada ecossistema para novas versõ
 Se tiver habilitado atualizações de segurança, às vezes você verá atualizações de segurança extras de pull requests. Elas são acionadas por um alerta de {% data variables.product.prodname_dependabot %} para uma dependência de seu branch padrão. {% data variables.product.prodname_dependabot %} gera automaticamente um pull request para atualizar a dependência vulnerável.
 
 ### Repositórios e ecossistemas suportados
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 É possível configurar atualizações de versão para repositórios que contenham um manifesto de dependência ou arquivo de bloqueio para um dos gerentes de pacotes suportados. Para alguns gerenciadores de pacotes, você também pode configurar o armazenamento para dependências. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)".
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md
index abbe6c6912..a1e07700d0 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md
@@ -10,6 +10,7 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
 <!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
 
 ### Disponibilidade do gráfico de dependências
@@ -60,10 +61,6 @@ Você pode usar o gráfico de dependências para:
 
 {% if enterpriseServerVersions contém currentVersion and currentVersion ver_gt "enterprise-server@2. 1" %}Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e os alertas de segurança. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".
-
-{% endif %}
-
 Quando o gráfico de dependências é ativado pela primeira vez, todos manifesto e arquivos de bloqueio para ecossistemas suportados são analisados imediatamente. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Uma vez habilitado, o gráfico é atualizado automaticamente a cada push para o repositório{% if currentVersion == "free-pro-team@latest" %} e cada push para outros repositórios no gráfico{% endif %}.
 
 ### Ecossistemas de pacote compatíveis
@@ -90,6 +87,6 @@ Os formatos recomendados definem explicitamente quais versões são usadas para
 
 - "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia
 - "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
+- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}
 - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index cf83b013d6..739f48ff8d 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -164,7 +164,7 @@ atualizações:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Use a opção `allow` para personalizar quais dependências são atualizadas. Isso não tem impacto nas atualizações de segurança para dependências vulneráveis. Você pode usar o seguinte opções:
+Use a opção `allow` para personalizar quais dependências são atualizadas. Isso se aplica tanto às atualizações de versão quanto de segurança. Você pode usar o seguinte opções:
 
 - `dependency-name`—use para permitir atualizações para dependências com nomes correspondentes, opcionalmente usando `*` para corresponder a zero ou mais caracteres. Para dependências Java, o formato do atributo `dependency-name` é: `groupId:artifactId`, por exemplo: `org.kohsuke:github-api`.
 - `dependency-type`—use para permitir atualizações para dependências de tipos específicos.
@@ -445,12 +445,12 @@ updates:
 
 #### `rebase-strategy`
 
-Por padrão, o {% data variables.product.prodname_dependabot %} faz o rebasamento automaticamente das pull requests abertas quando detectar conflitos. Use `rebase-strategy` para desativar este comportamento.
+Por padrão, {% data variables.product.prodname_dependabot %} faz os rebases dos pull requests abertos automaticamente quando detecta qualquer alteração no pull request. Use `rebase-strategy` para desativar este comportamento.
 
 Estratégias de rebase disponíveis
 
 - `disabled` para desabilitar rebasing automático.
-- `auto` para usar o comportamento padrão e rebase das pull request abertas quando conflitos forem detectados.
+- `auto` para usar o comportamento padrão e fazer rebase dos pull requests abertos quando forem detectadas alterações.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -473,11 +473,11 @@ Para permitir que {% data variables.product.prodname_dependabot %} acesse um reg
 
 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).
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -493,11 +493,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -716,7 +716,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
@@ -724,14 +724,15 @@ updates:
 
 Você utiliza as seguintes opções para especificar as configurações de acesso. As configurações de registro devem conter um `tipo` e uma `url`, e, de modo geral, uma combinação de `nome de usuário` e `senha` ou `token`.
 
-| Option&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Descrição                                                                                                                                                                                                                                                                                                      |
-|:------------------------------------------------------------------------------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `tipo`                                                                                                 | Identifica o tipo de registro. Veja a lista completa de tipos abaixo.                                                                                                                                                                                                                                          |
-| `url`                                                                                                  | A URL a ser usada para acessar as dependências deste registro. O protocolo é opcional. Se não for especificado, presume-se `https://`. {% data variables.product.prodname_dependabot %} adiciona ou ignora barras à direita, conforme necessário.                                                              |
-| `nome de usuário`                                                                                      | O nome de usuário que {% data variables.product.prodname_dependabot %} usa para acessar o registro.                                                                                                                                                                                                            |
-| `senha`                                                                                                | Uma referência a um segredo de {% data variables.product.prodname_dependabot %} que contém a senha para o usuário especificado. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)".   |
-| `token`                                                                                                | Uma referência a um segredo de {% data variables.product.prodname_dependabot %} que contém um token de acesso para este registro. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". |
-| `replaces-base`                                                                                        | Para registros com `type: python-index`, se o valor booleano for `true`, o pip resolverá as dependências usando a URL especificada, em vez da URL base do Índice de Pacotes Python (por padrão `https://pypi.org/simple`).                                                                                     |
+| Option&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Descrição                                                                                                                                                                                                                                                                                                       |
+|:------------------------------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `tipo`                                                                                                 | Identifica o tipo de registro. Veja a lista completa de tipos abaixo.                                                                                                                                                                                                                                           |
+| `url`                                                                                                  | A URL a ser usada para acessar as dependências deste registro. O protocolo é opcional. Se não for especificado, presume-se `https://`. {% data variables.product.prodname_dependabot %} adiciona ou ignora barras à direita, conforme necessário.                                                               |
+| `nome de usuário`                                                                                      | O nome de usuário que {% data variables.product.prodname_dependabot %} usa para acessar o registro.                                                                                                                                                                                                             |
+| `senha`                                                                                                | Uma referência a um segredo de {% data variables.product.prodname_dependabot %} que contém a senha para o usuário especificado. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)".    |
+| `Chave`                                                                                                | Uma referência a um segredo de {% data variables.product.prodname_dependabot %} que contém uma chave de acesso para este registro. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)". |
+| `token`                                                                                                | Uma referência a um segredo de {% data variables.product.prodname_dependabot %} que contém um token de acesso para este registro. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)".  |
+| `replaces-base`                                                                                        | Para registros com `type: python-index`, se o valor booleano for `true`, o pip resolverá as dependências usando a URL especificada, em vez da URL base do Índice de Pacotes Python (por padrão `https://pypi.org/simple`).                                                                                      |
 
 
 Cada `tipo` de configuração exige que você forneça configurações específicas. Alguns tipos permitem mais de uma maneira de conectar-se. As seções a seguir fornecem detalhes das configurações que você deve usar para cada `tipo`.
@@ -766,6 +767,19 @@ registries:
 ```
 {% endraw %}
 
+O tipo `docker-registry` também pode ser usado para extrair do Amazon ECR usando credenciais estáticas do AWS.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 O tipo `git` é compatível com o nome de usuário e senha.
@@ -781,6 +795,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+O tipo `hex-organization` é compatível com organização e com a chave.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 O tipo `maven-repository` é compatível com o nome de usuário e senha ou token.
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
index dd6148f279..4bb829c40d 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
@@ -49,7 +49,7 @@ Se as atualizações de segurança não estiverem habilitadas para o seu reposit
 
 Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para um repositório individual (veja abaixo).
 
-Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios pertencentes à sua conta de usuário ou organização. 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)."
+Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} 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)".
 
 O {% data variables.product.prodname_dependabot_security_updates %} exige configurações específicas do repositório. Para obter mais informações, consulte "[Repositórios compatíveis](#supported-repositories)".
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index c82dcb534c..b29f2cf967 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
 title: Configurar notificações para dependências vulneráveis
 shortTitle: Configurar notificações
-intro: 'Otimiza como você recebe notificações sobre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %}.'
+intro: 'Otimize como você recebe notificações sobre alertas de {% data variables.product.prodname_dependabot %}.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
@@ -11,48 +11,41 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
+
 ### Sobre notificações para dependências vulneráveis
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}Quando {% data variables.product.prodname_dependabot %} detecta dependências vulneráveis nos seus repositórios, geramos um alerta {% data variables.product.prodname_dependabot %} e exibimo-lo na aba Segurança do repositório. {% data variables.product.product_name %} notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação.{% else %}Quando {% data variables.product.product_name %} detecta dependências vulneráveis no seu repositório, ele envia alertas de segurança.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} está habilitado por padrão em todos os repositórios públicos. Para {% data variables.product.prodname_dependabot_alerts %}, por padrão, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail, agrupado pela vulnerabilidade específica.
+Quando {% data variables.product.prodname_dependabot %} detecta dependências vulneráveis nos seus repositórios, geramos um alerta de {% data variables.product.prodname_dependabot %} e o exibimos na aba Segurança do repositório. {% data variables.product.product_name %} notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com as suas preferências de notificação.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} está habilitado por padrão em todos os repositórios públicos. Para {% data variables.product.prodname_dependabot_alerts %}, por padrão, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail, agrupado pela vulnerabilidade específica.
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)".
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-O administrador do seu site precisa habilitar alertas de segurança para dependências vulneráveis para {% data variables.product.product_location %} antes de poder usar o recurso. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-Por padrão, se o administrador do site tiver configurado o e-mail para notificações na sua empresa, você receberá {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} por e-mail.{% endif %}
+Por padrão, se o administrador do site tiver configurado o e-mail para notificações na sua empresa, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail.{% endif %}
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}Os administradores do site também podem habilitar {% data variables.product.prodname_dependabot_alerts %} sem notificações. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. Para obter mais informações, consulte "[Habilitar alertas de segurança para dependências vulneráveis no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
-
-### Configurar notificações para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}
+### Configurar notificações para {% data variables.product.prodname_dependabot_alerts %}
 
 Você pode definir as configurações de notificação para si mesmo ou para sua organização no menu suspenso Gerenciar notificações {% octicon "bell" aria-label="The notifications bell" %} exibido na parte superior de cada página. Para obter mais informações, consulte “[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)".
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
   ![Opções {% data variables.product.prodname_dependabot_alerts %} ](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
-{% else %}
-  ![Opções de alerta de segurança](/assets/images/help/notifications-v2/security-alerts-options.png)
-{% endif %}
 
 {% note %}
 
-**Observação:** Você filtrar as notificações de {% data variables.product.company_short %} para mostrar os alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}segurança {% endif %} do {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)".
+**Observação:** Você pode filtrar as suas notificações sobre {% data variables.product.company_short %} para mostrar alertas de {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciando notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)".
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" % %}{% data reusables.repositories.security-alerts-x-github-severity %} Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} Para obter mais informações, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
 
 ### Como reduzir o ruído das notificações para dependências vulneráveis
 
-Se você estiver preocupado em receber muitas notificações para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, recomendamos que você opte pelo resumo semanal por e-mail ou desative as notificações ao mesmo tempo que mantém os {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} habilitados. Você ainda pode navegar para ver os seus {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} na aba de Segurança do seu repositório. {% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %}
+Se você estiver preocupado em receber muitas notificações para {% data variables.product.prodname_dependabot_alerts %}, recomendamos que você opte pelo resumo semanal de e-mail ou desabilite as notificações enquanto mantém {% data variables.product.prodname_dependabot_alerts %} habilitado. Você ainda pode navegar para ver seu {% data variables.product.prodname_dependabot_alerts %} na aba Segurança do seu repositório. Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository). "
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index 51f0d7fcdc..c1b7fc7695 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -18,7 +18,7 @@ Você habilita {% data variables.product.prodname_dependabot_version_updates %},
 
 {% data reusables.dependabot.initial-updates %} Para obter mais informações, consulte "[Personalizar atualizações de dependência](/github/administering-a-repository/customizing-dependency-updates)".
 
-{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, {% data variables.product.prodname_dependabot %} não é compatível com dependências privadas {% data variables.product.prodname_dotcom %} para todos os gerenciadores de pacote. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)".
+{% data reusables.dependabot.private-dependencies-note %} Adicionalmente, {% data variables.product.prodname_dependabot %} não é compatível com dependências privadas {% data variables.product.prodname_dotcom %} para todos os gerenciadores de pacote. Para obter mais informações, consulte "[Sobre atualizações de versão do Dependabot](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" e "[{% data variables.product.prodname_dotcom %} suporte a idiomas](/github/getting-started-with-github/github-language-support)".
 
 ### Habilitar {% data variables.product.prodname_dependabot_version_updates %}
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index e0bdcfb276..4c0a53f087 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -15,6 +15,8 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
@@ -50,19 +52,6 @@ Todas as dependências diretas e indiretas especificadas no manifesto do reposit
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Todas as dependências diretas e indiretas especificadas no manifesto do repositório ou arquivos de bloqueio são listadas e agrupadas pelo ecossistema. Se foram detectadas vulnerabilidades no repositório, estas são exibidas na parte superior da visualização para usuários com acesso a alertas de segurança.
-
-![Gráfico de dependências](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**Observação:** {% data variables.product.prodname_ghe_server %} não preenche a vista de **Dependentes**.
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### Vista de dependentes
 
@@ -74,7 +63,7 @@ Para repositórios públicos, a vista de dependentes mostra como o repositório
 
 Os administradores de repositórios podem habilitar ou desabilitar o gráfico de dependências em repositórios privados.
 
-Você também pode habilitar ou desabilitar o gráfico de dependências para todos os repositórios pertencentes à sua conta de usuário ou organização. 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)."
+Você também pode habilitar ou desabilitar o gráfico de dependências 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)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -113,8 +102,8 @@ Se um arquivo de manifesto ou de bloqueio não for processado, suas dependência
 
 ### Leia mais
 
-- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
 - "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
 - "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/github/understanding-how-github-uses-and-protects-your-data)"
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/index.md b/translations/pt-BR/content/code-security/supply-chain-security/index.md
index 8989fbd7fb..875bd1c336 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/index.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 1a8d613946..da4f4dda3d 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -17,18 +17,18 @@ Os resultados da detecção de dependências relatados pelo {% data variables.pr
 
 O {% data variables.product.prodname_dotcom %} gera e exibe dados de dependência de maneira diferente de outras ferramentas. Consequentemente, se você usou outra ferramenta para identificar dependências, quase certamente verá resultados diferentes. Considere o seguinte:
 
-*   {% data variables.product.prodname_advisory_database %} é uma das fontes de dados que {% data variables.product.prodname_dotcom %} usa para identificar dependências vulneráveis. É um banco de dados gratuito e curado com informações sobre vulnerabilidade para ecossistemas de pacote comum em {% data variables.product.prodname_dotcom %}. Inclui tanto dados relatados diretamente para {% data variables.product.prodname_dotcom %} de {% data variables.product.prodname_security_advisories %} quanto os feeds oficiais e as fontes comunitárias. Estes dados são revisados e curados por {% data variables.product.prodname_dotcom %} para garantir que informações falsas ou não acionáveis não sejam compartilhadas com a comunidade de desenvolvimento. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" e "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
+*   {% data variables.product.prodname_advisory_database %} é uma das fontes de dados que {% data variables.product.prodname_dotcom %} usa para identificar dependências vulneráveis. É um banco de dados gratuito e curado com informações sobre vulnerabilidade para ecossistemas de pacote comum em {% data variables.product.prodname_dotcom %}. Inclui tanto dados relatados diretamente para {% data variables.product.prodname_dotcom %} de {% data variables.product.prodname_security_advisories %} quanto os feeds oficiais e as fontes comunitárias. Estes dados são revisados e curados por {% data variables.product.prodname_dotcom %} para garantir que informações falsas ou não acionáveis não sejam compartilhadas com a comunidade de desenvolvimento. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   O gráfico de dependências analisa todos os arquivos conhecidos de manifesto de pacote no repositório de um usuário. Por exemplo, para o npm, ele irá analisar o arquivo _package-lock.json_. Ele constrói um gráfico de todas as dependências do repositório e dependências públicas. Isso acontece quando você habilita o gráfico de dependências e quando alguém faz push para o branch-padrão, e inclui commits que fazem alterações em um formato de manifesto compatível. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 *   {% data variables.product.prodname_dependabot %} verifica qualquer push, para o branch-padrão, que contém um arquivo de manifesto. Quando um novo registro de vulnerabilidade é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório vulnerável. {% data variables.product.prodname_dependabot_alerts %} são agregados ao nível do repositório, em vez de criar um alerta por vulnerabilidade. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-*   {% data variables.product.prodname_dependabot_security_updates %} são acionados quando você recebe um alerta sobre uma dependência vulnerável em seu repositório. Sempre que possível, {% data variables.product.prodname_dependabot %} cria um pull request no repositório para atualizar a dependência vulnerável à versão mínima segura necessária para evitar a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" e "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)".
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} são acionados quando você recebe um alerta sobre uma dependência vulnerável no repositório. Sempre que possível, {% data variables.product.prodname_dependabot %} cria um pull request no repositório para atualizar a dependência vulnerável à versão mínima segura necessária para evitar a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" e "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)".
 
-    {% data variables.product.prodname_dependabot %} não faz a varredura de repositórios de dependências vulneráveis em uma programação, mas o faz quando algo muda. Por exemplo, uma varredura é acionada quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é descoberta e adicionada ao banco de dados consultivo.
+    {% endif %}{% data variables.product.prodname_dependabot %} não pesquisa repositórios com relação a dependências vulneráveis de uma programação, mas o faz quando algo muda. Por exemplo, aciona-se uma varredura quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é adicionada ao banco de dados da consultoria{% if currentVersion ver_gt "enterprise-server@2.22" %} e sincronizado com {% data variables.product.prodname_ghe_server %}{% endif %}. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)"
 
 ### Por que não recebo alertas de vulnerabilidade em alguns ecossistemas?
 
-O {% data variables.product.prodname_dotcom %} limita seu suporte a alertas de vulnerabilidade a um conjunto de ecossistemas onde podemos fornecer dados de alta qualidade e relevantes. Vulnerabilidades organizadas em {% data variables.product.prodname_advisory_database %}, o gráfico de dependências, {% data variables.product.prodname_dependabot_alerts %} e as atualizações de segurança de {% data variables.product.prodname_dependabot %} são fornecidas para vários ecossistemas, incluindo o Maven do Java, npm e Yarn do JavaScript, ,NET's NuGet, Pip Python, RubyGems e Compositor do PHP. Nós continuaremos a adicionar suporte para mais ecossistemas ao longo do tempo. Para uma visão geral dos ecossistemas de pacotes suportados por nós, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
+O {% data variables.product.prodname_dotcom %} limita seu suporte a alertas de vulnerabilidade a um conjunto de ecossistemas onde podemos fornecer dados de alta qualidade e relevantes. Vulnerabilidades curadas no {% data variables.product.prodname_advisory_database %}, o gráfico de dependências, {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot %} atualizações de segurança {% endif %}e alertas de {% data variables.product.prodname_dependabot %} são fornecidos para vários ecossistemas, incluindo o Java Maven, o npm de JavaScript e o Yarn, .NET's NuGet, Pip Python, RubyGems e Compositor do PHP. Nós continuaremos a adicionar suporte para mais ecossistemas ao longo do tempo. Para uma visão geral dos ecossistemas de pacotes suportados por nós, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
 
-Vale a pena notar que a [{% data variables.product.prodname_dotcom %} Consultoria de Segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) pode existir para outros ecossistemas. As informações em uma consultoria de segurança são fornecidas pelos mantenedores de um determinado repositório. Estes dados não são curados da mesma forma que as informações relativas aos ecossistemas suportados.
+Vale a pena observar que as consultorias de segurança de {% data variables.product.prodname_dotcom %} podem existir para outros ecossistemas. As informações em uma consultoria de segurança são fornecidas pelos mantenedores de um determinado repositório. Estes dados não são curados da mesma forma que as informações relativas aos ecossistemas suportados. {% if currentVersion == "free-pro-team@latest" %}Para obter mais informações, consulte "[Sobre consultorias de segurança de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories){% endif %}
 
 **Verificar**: A vulnerabilidade não capturada se aplica a um ecossistema não suportado?
 
@@ -36,9 +36,9 @@ Vale a pena notar que a [{% data variables.product.prodname_dotcom %} Consultori
 
 O gráfico de dependências inclui informações sobre dependências explicitamente declaradas em seu ambiente. Ou seja, dependências que são especificadas em um manifesto ou um arquivo de bloqueio. O gráfico de dependências, geralmente, também inclui dependências transitivas, mesmo quando não são especificadas em um arquivo de travamento analisando as dependências das dependências em um arquivo de manifesto.
 
-Os {% data variables.product.prodname_dependabot_alerts %} aconselham você com relação a dependências que você deve atualizar, incluindo dependências transitivas, em que a versão pode ser determinada a partir de um manifesto ou de um arquivo de bloqueio. As  atualizações de segurança {% data variables.product.prodname_dependabot %} apenas sugerem uma mudança onde ela pode "corrigir" diretamente a dependência, ou seja, quando estas são:
+Os {% data variables.product.prodname_dependabot_alerts %} aconselham você com relação a dependências que você deve atualizar, incluindo dependências transitivas, em que a versão pode ser determinada a partir de um manifesto ou de um arquivo de bloqueio. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} sugere apenas uma mudança em que {% data variables.product.prodname_dependabot %} pode "corrigir" diretamente a dependência, ou seja, quando são:
 * Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio
-* Dependências transitórias declaradas em um arquivo de bloqueio
+* Dependências transitórias declaradas em um arquivo de bloqueio{% endif %}
 
 O gráfico de dependências não inclui dependências de "soltas". As dependências "soltas" são arquivos individuais copiados de outra fonte e verificados no repositório diretamente ou dentro de um arquivo (como um arquivo ZIP ou JAR), em vez de ser referenciadas pelo manifesto ou arquivo de bloqueio do gerenciador de pacotes.
 
@@ -84,6 +84,7 @@ Algumas ferramentas de terceiros usam dados de CVE não descurados que não são
 
 Uma vez que {% data variables.product.prodname_dependabot %} usa dados curados em {% data variables.product.prodname_advisory_database %}, o volume de alertas pode ser menor, mas os alertas que você recebe serão precisos e relevantes.
 
+{% if currentVersion == "free-pro-team@latest" %}
 ### 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.
@@ -97,10 +98,11 @@ Ao clicar para exibir os detalhes de alerta, você pode ver quantas vulnerabilid
 ![Múltiplas vulnerabilidades para um alerta de {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
 **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.
+{% endif %}
 
 ### Leia mais
 
 - "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Gerenciar as configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Solucionar problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/pt-BR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..02f9742808
--- /dev/null
+++ b/translations/pt-BR/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Atualizando de Dependabot.com para Dependabot nativo do GitHub
+intro: 'Você pode atualizar para o Dependabt nativo do GitHub, fazendo um merge de um pull request que permitirá que as suas dependências continuem sendo atualizadas.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+A visualização do Dependabot será descontinuada em 3 de agosto de 2021. Para continuar recebendo atualizações do Dependabot, faça a migração para o Dependabot GitHub nativo antes dessa data.
+
+Após essa data, todos os pull requests abertos do Dependabot Preview permanecerão abertos, mas o próprio bot não funcionará mais nas suas contas e organizações do {% data variables.product.prodname_dotcom %}.
+
+{% endwarning %}
+
+### Sobre a atualização de Dependabot Preview para um nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}
+
+A visualização do Dependabot foi construída diretamente em {% data variables.product.prodname_dotcom %}. Portanto, você poderá usar {% data variables.product.prodname_dependabot %} junto com todas as outras funcionalidades em {% data variables.product.prodname_dotcom %} sem ter que instalar e usar um aplicativo separado. Ao fazer a migração para um nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}, também podemos focar em trazer muitas novas funcionalidades empolgantes para {% data variables.product.prodname_dependabot %}, incluindo mais [atualizações do ecossistema](https://github.com/github/roadmap/issues/150), [notificações melhoradas](https://github.com/github/roadmap/issues/133) e suporte {% data variables.product.prodname_dependabot %} para [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) e [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Diferenças entre o Dependabot Preview e nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}
+
+Embora a maior parte das funcionalidades do Dependabot Preview existam no nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}, algumas permanecem indisponíveis:
+- **Atualizações ao vivo:** Esperamos trazê-las de volta no futuro. Por enquanto, você pode executar {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} diariamente para pegar novos pacotes dentro de um dia de versão.
+- **Registros variáveis de ambiente PHP:** Por enquanto, você pode usar {% data variables.product.prodname_actions %} para buscar dependências destes registros.
+- **Auto-merge:** Sempre recomendamos verificar suas dependências antes de mesclá-las. Portanto, a fusão automática não será compatível em um futuro próximo. Para aqueles de vocês que avaliaram as suas dependências ou estiverem usando apenas dependências internas, recomendamos adicionar aplicativos de auto-merge de terceiros ou configurar o GitHub Actions para fazer o merge.
+
+Em nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}, você pode configurar todas as atualizações da versão usando o arquivo de configuração. Este arquivo é semelhante ao arquivo de configuração do Dependabot Preview com algumas alterações e melhorias que serão incluídas automaticamente no seu pull request de atualização. Para obter mais informações sobre o pull request de atualização, consulte "[Atualizando ppara o Dependabot nativo do GitHub](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+Para visualizar os registros de atualização para nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} que estavam anteriormente no painel do Dependabot.com:
+
+  1. Acesse a página **Insights** do seu repositório.
+  2. Clique em **Gráfico de dependência** à esquerda.
+  3. Clique em **{% data variables.product.prodname_dependabot %}**.
+
+Para obter mais informações sobre as atualizações de versão com nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}, consulte "[Sobre atualizações da versão do Dependabot](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+### Atualizando para nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}
+
+A atualização de Dependabot Preview para {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} exige a fusão do *Atualize para um Dependabot nativo do GitHub* no seu repositório. Este pull request inclui o arquivo de configuração atualizado necessário para nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}.
+
+Se você estiver usando repositórios privados, você terá que conceder acesso a Dependabot a esses repositórios nas configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[permitir que o Dependabot acesse dependências privadas](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Anteriormente, o Dependabot tinha acesso a todos os repositórios de uma organização, mas implementamos esta alteração, porque é muito mais seguro utilizar o princípio do menor privilégio de Dependabot.
+
+Se você estiver usando registros privados, será necessário adicionar seus segredos de Dependabot Preview aos "Segredos de Dependabot" do seu repositório ou da organização. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot). ".
+
+Se você tiver alguma dúvidas ou precisar de ajuda para migrar, você poderá visualizar ou abrir problemas no repositório [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=).
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index a00c1f297a..6c1c825342 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-A aba de alertas do {% data variables.product.prodname_dependabot %} do seu repositório lista todos {% data variables.product.prodname_dependabot_alerts %} e as {% data variables.product.prodname_dependabot_security_updates %} correspondente. Você pode classificar a lista de alertas usando o menu suspenso e clicar em determinados alertas para ver 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)"
+A aba de alertas de {% data variables.product.prodname_dependabot %} do repositório lista as todos os {% data variables.product.prodname_dependabot_alerts %} abertos e fechados {% if currentVersion == "free-pro-team@latest" %} e {% data variables.product.prodname_dependabot_security_updates %} correspondentes {% endif %}. Você pode classificar a lista de alertas usando o menu suspenso e clicar em determinados alertas para ver 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)"
 
+{% if currentVersion == "free-pro-team@latest" %}
 É 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 %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ A aba de alertas do {% data variables.product.prodname_dependabot %} do seu repo
 ### 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.
+{% endif %}
 
 ### Visualizar e atualizar dependências vulneráveis
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ A aba de alertas do {% data variables.product.prodname_dependabot %} do seu repo
 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](/github/administering-a-repository/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, use 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 currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Clique no alerta que deseja exibir. ![Alerta selecionado na lista de alertas](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. Revise os detalhes da vulnerabilidade e determine se você precisa atualizar a dependência.
+1. Ao fazer merge de um pull request que atualiza o manifesto ou arquivo de bloqueio para uma versão segura da dependência, isso resolverá o alerta. Como alternativa, se você decidir não atualizar a dependência, clique no menu suspenso **Ignorar** e selecione um motivo para ignorar o alerta. ![Escolher o motivo para ignorar o alerta a partir do menu suspenso "Ignorar"down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. Clique no número da versão da dependência vulnerável para exibir informações detalhadas. ![Informações detalhadas sobre a dependência vulnerável](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. Revise os detalhes da vulnerabilidade e determine se você precisa atualizar a dependência. Ao fazer merge de um pull request que atualiza o manifesto ou arquivo de bloqueio para uma versão segura da dependência, isso resolverá o alerta.
+1. O banner na parte superior da aba **Dependências** é exibido até que todas as dependências vulneráveis sejam resolvidas ou até que você o ignore. Clique em **Ignorar** no canto superior direito do banner e selecione uma razão para ignorar o alerta. ![Ignorar banner de segurança](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### Leia mais
 
-- "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-- "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"
+- "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
 - "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
-- "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Solucionar a detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Solucionar problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/pt-BR/content/codespaces/about-codespaces.md b/translations/pt-BR/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..d36ae87c95
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: Sobre os Codespaces
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Sobre o {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![Um codespace aberto](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)".
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Os desenvolvedores podem contribuir de qualquer lugar, em qualquer máquina, incluindo tablets ou Chromebooks, e não há necessidade de manter cópias locais da propriedade intelectual. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### Sobre a cobrança do {% data variables.product.prodname_codespaces %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)".
+
+### Juntar-se ao beta
+
+Um número limitado de pessoas será convidado a participar do beta. Para participar da lista de espera, consulte [Registrar-se no beta de codespaces](https://github.com/features/codespaces/signup).
+
+### Entre em contato conosco com relação a {% data variables.product.prodname_codespaces %}
+
+Se você tiver algum problema ao usar {% data variables.product.prodname_codespaces %}, consulte "[Solucionar problemas do seu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)".
+
+Se você ainda precisa de ajuda ou tem feedback sobre {% data variables.product.prodname_codespaces %}, use a discussão de [Feedback para codespaces](https://github.com/github/feedback/discussions/categories/codespaces-feedback).
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..05178d0387
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: Sobre a cobrança para codespaces
+intro: 'Quando {% data variables.product.prodname_codespaces %} se torna geralmente disponível, você será cobrado para armazenamento e uso de computação.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
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
new file mode 100644
index 0000000000..2946135002
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Permitir que seu codespace acesse um registro de imagens privadas
+intro: 'Você pode usar segredos para permitir que {% data variables.product.prodname_codespaces %} acesse um registro de imagens privada'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Um registro é um espaço seguro para armazenar e gerenciar imagens de contêineres privadas, como Azure Container Registry ou DockerHub. Você pode criar segredos no GitHub para armazenar os detalhes de acesso de um registro privado e usá-los para dar ao seu código acesso as imagens armazenadas no registro.
+
+Ao iniciar iniciar um código, {% data variables.product.prodname_codespaces %} verifica três segredos, que definem o nome do servidor, o nome de usuário e o token de acesso pessoal (PAT) para um registro do contêiner. Se estes segredos forem encontrados, {% data variables.product.prodname_codespaces %} disponibilizará o registro dentro do seu codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+É possível armazenar segredos a nível do usuário, repositório ou organização, permitindo que você os compartilhe de forma segura entre diferentes codespaces. Ao criar um conjunto de segredos para um registro de imagem privado, você precisa substituir o "<*>" no nome por um identificador consistente. Para mais informações, consulte "[Gerenciar segredos criptografados para seus códigos](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" e "[Gerenciar segredos criptografados para seu repositório e organização para os codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)".
+
+Por exemplo, se você tiver um registro de imagens privadas no Azure, você poderá criar os seguintes segredos:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![Exemplo de segredo do registro de imagem](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/index.md b/translations/pt-BR/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..897af060ac
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: Referência
+intro: 'Esta seção contém referências que permitirão seu sucesso com {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..3ca3eecf87
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: Solucionar problemas do seu codespace
+intro: Use este guia para ajudá-lo a resolver problemas comuns com seu codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Limitações conhecidas
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### Solução de problemas de {% data variables.product.prodname_vscode %}
+
+Use **Problemas** no [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) para verificar problemas conhecidos ou registrar problemas sobre a experiência de {% data variables.product.prodname_vscode %}.
+
+
+### Solução de problemas de configuração
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+Este codespace está em execução em modo de recuperação devido a um erro no contêiner.
+```
+
+Revise os registros de criação, atualize a configuração conforme necessário e execute **Codespaces: Rebuild Container** na paleta de comandos para tentar novamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)".
+
+### solução de problemas dotfiles
+
+- Certifique-se de que seu repositório dotfiles seja público. Se você tem segredos ou dados confidenciais que você deseja usar em seu código, use [segredos de codespaces ](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) em vez dos dotfiles privados.
+- Verifique `/workspaces/.codespaces/.persistedshare/dotfiles` para ver se seus dotfiles foram clonados.
+  - Se seus dotfiles foram clonados, tente reexecutar manualmente seu script de instalação para verificar se ele é executável.
+  - Se seus dotfiles não foram clonados, verifique `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` para ver se havia um problema com a clonagem.
+- Verifique `/workspaces/.codespaces/.persistedshare/creation.log` com relação a possíveis problemas. Como alternativa, você pode ver o `creation.log` acessando a paleta de comandos e inserindo os **Codespaces: View Creation Log**.
+
+
+### Solução de problemas do navegador
+
+Se você encontrar problemas ao usar um navegador que não se baseie no Chromium, tente alternar para um navegador baseado no Chromium ou verifique se há problemas conhecidos com seu navegador no repositório `microsoft/vscode` procurando por problemas etiquetados com o nome do seu navegador, como, por exemplo, [`fogo-fogo`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) ou [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari).
+
+Se você encontrar problemas ao usar um navegador baseado em Chromium, você poderá verificar se você está tendo outro problema conhecido com {% data variables.product.prodname_vscode %} no repositório [`microsoft/vscode`](https://github.com/microsoft/vscode/issues).
+
+### Solução de problemas de armazenamento do contêiner
+
+Ao criar um codespace, ele terá uma quantidade limitada de armazenamento e, após um tempo, poderá ser necessário que você libere espaço. Experimente qualquer um dos seguintes itens para liberar espaço de armazenamento.
+
+- Remova pacotes que não são mais usando `sudo apt autoremove`
+- Limpe o cache apt usando `sudo apt clean`
+- Exclua arquivos desnecessários, como artefatos de compilação e registros (estes são muito dependentes do projeto)
+- Veja os 10 principais arquivos no codespace: `sudo find / -printf '%s %p\n'├sort -nr ├head -10`
+
+Mais opções para exclusão:
+- Remova imagens não utilizadas do Docker, redes, e contêineres utilizando o `docker system prune` (insira `-a` se desejar remover todas as imagens, e `--volumes` se desejar remover todos os volumes)
+- Remova os arquivos não rastreados da árvore de trabalho: `git clean -i`
+
+### Entrar em contato
+
+Se precisar de ajuda, você poderá entrar em contato conosco. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)."
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..0cddc6d9f8
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Criar um codespace
+intro: Você pode criar um codespace para uma branch em um repositório para fazer o desenvolvimento on-line.
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Sobre a criação do codespace
+
+Você pode criar um codespace em {% data variables.product.prodname_dotcom_the_website %} ou em {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Os codespaces são associados a um branch específico de um repositório e o repositório não pode estar vazio. {% data reusables.codespaces.concurrent-codespace-limit %} Para obter mais informações, consulte "[Excluir um codespace](/github/developing-online-with-codespaces/deleting-a-codespace)".
+
+
+Ao criar um codespace, várias etapas acontecem para permitir o acesso total ao seu ambiente de desenvolvimento.
+
+- Recursos como uma VM e armazenamento para seu contêiner foram atribuídos. Uma nova VM é criada toda vez que você criar ou iniciar um codespace para garantir que você sempre tenha as versões mais recentes e patch de segurança.
+- {% data variables.product.prodname_codespaces %} recebe informações sobre o seu repositório, branch, commits, seu repositório dotfiles público e quaisquer segredos que você tenha criado.
+- {% data variables.product.prodname_codespaces %} executa um clone raso do repositório.
+- Se você tiver um no seu repositório, {% data variables.product.prodname_codespaces %} irá executar o arquivo `devcontainer.json`. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)".
+- Seu contêiner Docker, `docker-compose`, ou outra inicialização é executada.
+- Neste ponto, o codespace está marcado como disponível e você pode conectar-se.
+- Assim que o codespace for disponibilizado, dependendo dos comandos no devcontainer, o codespace continuará com algumas configurações.
+  - O codespace compartilha as portas adicionadas no arquivo</code>devcontainer.json.`.</li>
+<li>O codespace executa qualquer coisa especificada em <code>postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clona o repositório do dotfiles no ambiente de código e procura um arquivo de instalação. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Por fim, o código do repositório faz um clone completo para que você tenha acesso total ao mesmo.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### Criar um codespace
+
+{% data reusables.repositories.navigate-to-repo %}
+2. No nome do repositório, use o menu suspenso "Branch", e selecione o branch para o qual você deseja criar um codespace.
+
+  ![Menu suspenso do branch](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. No nome do repositório, use o menu suspenso do {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com os espaços de código**.
+
+  ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. Para criar um codespace usando um tipo de máquina padrão, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**.
+
+  ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..b994587165
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: Excluir um codespace
+intro: Você pode excluir um codespace de que você não precisa mais.
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Acesse o repositório onde você criou o codespace. Selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** e, em seguida, clique em {% octicon "gear" aria-label="The Settings gear" %}. Isto irá exibir todo o {% data variables.product.prodname_codespaces %} que você criou no repositório. ![Aba Codespaces](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Como alternativa, você pode ver todos os códigos existentes na sua conta de usuário em [github.com/codespaces](https://github.com/codespaces).
+
+2. À direita do código que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, depois em **{% octicon "trash" aria-label="The trash icon" %} Apagar** ![Botão excluir](/assets/images/help/codespaces/delete-codespace.png)
+
+### Excluir um codespace em {% data variables.product.prodname_vscode %}
+
+Para obter informações sobre como excluir um codespace em {% data variables.product.prodname_vscode %}, consulte "[Usando codespaces no Visual Studio](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)".
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..a8eeba2482
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: Desenvolver em um codespace
+intro: 'Você pode abrir um codespace em {% data variables.product.product_name %} e, em seguida, desenvolver usando os recursos do {% data variables.product.prodname_vscode %}.'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Sobre o desenvolvimento com {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} fornece a você a experiência completa de desenvolvimento de {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Visão geral do codespace com anotações](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Barra lateral - Por padrão, esta área mostra os arquivos do seu projeto no Explorador.
+2. Barra de Atividades - Exibe a visualização e fornece uma maneira de alternar entre elas. Você pode reordenar as Visualizações arrastando e soltando-as.
+3. Editor - É aqui que você edita seus arquivos. Você pode usar a aba para cada editor para posicioná-lo exatamente onde você precisa.
+4. Painéis - É aqui que você pode visualizar as informações de saída e depuração, bem como o local padrão para o Terminal integrado.
+5. Barra de Status - Esta área fornece informações úteis sobre seu codespace e projeto. Por exemplo, o nome da agência, portas configuradas e muito mais.
+
+Para obter mais informações sobre como usar {% data variables.product.prodname_vscode %}, consulte o [Guia da Interface do Usuário](https://code.visualstudio.com/docs/getstarted/userinterface) na documentação de {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} Para obter mais informações, consulte "[Solucionar problemas do seu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)".
+
+#### Personalizando seu codespace
+
+{% data reusables.codespaces.about-personalization %} Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)".
+
+{% data reusables.codespaces.apply-devcontainer-changes %} Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para o seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)".
+
+#### Executando seu aplicativo a partir de um codespace
+{% data reusables.codespaces.about-port-forwarding %} Para obter mais informações, consulte "[Encaminhar portas no seu codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)".
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Acessar um codespace existente
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. Clique no nome do codespace em que você deseja desenvolver. ![Nome do codespace](/assets/images/help/codespaces/click-name-codespace.png)
+
+Como alternativa, você pode ver quaisquer codespaces ativos para um repositório, acessando o repositório no qual ele foi criado e selecionando **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..1641292a54
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Encaminhar portas no seu código
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Sobre as portas encaminhadas
+
+O redirecionamento de porta dá acesso a portas TCP que estão em execução no seu codespace. Por exemplo, se você estiver executando um aplicativo web na porta 4000, você poderá acessá-lo a partir do seu navegador para testar e depurar o aplicativo.
+
+Quando um aplicativo que se executa dentro de um codespace tem uma saída na porta para o console, o {% data variables.product.prodname_codespaces %} detecta o padrão do URL do host local e encaminha a porta automaticamente. Você pode clicar na URL no terminal para abrir a porta em um navegador. Por exemplo, se um aplicativo gerar `http://127.0.0.:4000` ou `http://localhost:4000` para o console, o registro irá converter automaticamente a saída em uma URL para a porta 4000 em que se pode clicar.
+
+![Encaminhamento de porta automático](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+Você também pode encaminhar uma porta manualmente, etiquetar portas encaminhadas, compartilhar portas anunciadas publicamente e adicionar portas encaminhadas para a configuração do código.
+
+### Encaminhar uma porta
+
+Você pode encaminhar manualmente uma porta que não foi encaminhada automaticamente.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Na lista de portas, clique em **Adicionar porta**. ![Botão adicionar porta](/assets/images/help/codespaces/add-port-button.png)
+1. Digite o número da porta ou endereço e, em seguida, pressione enter. ![Caixa de texto para o botão digitar porta](/assets/images/help/codespaces/port-number-text-box.png)
+
+### Etiquetar uma porta
+
+Você pode etiquetar uma porta para tornar a porta mais facilmente identificável em uma lista.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Passe o mouse sobre a porta que você deseja etiquetar, em seguida, clique no ícone da etiqueta. ![Ícone da etiqueta para a porta](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### Compartilhar uma porta
+
+Se você quiser compartilhar uma porta encaminhada com outras pessoas, você poderá tornar a porta pública. Após tornar uma porta pública, qualquer pessoa com a URL da porta poderá ver o aplicativo em execução sem precisar efetuar a autenticação.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Clique com o botão direito na porta que você deseja compartilhar e clique em **Tornar pública**. ![Opção para tornar a porta pública no menu com o clique com o botão direito](/assets/images/help/codespaces/make-public-option.png)
+1. À direita do endereço local para a porta, clique no ícone copiar. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Envie a URL copiada para a pessoa com quem você deseja compartilhar a porta.
+
+### Adicionar uma porta à configuração do código
+
+É possível adicionar uma porta encaminhada para a configuração {% data variables.product.prodname_codespaces %} do repositório para que a porta seja automaticamente encaminhada para todos os códigos criados a partir do repositório. Depois de atualizar a configuração, todos os codespaces criados anteriormente deverão ser reconstruídos para que a alteração seja aplicada. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)".
+
+Você pode configurar manualmente as portas predefinidas em um arquivo `.devcontainer.json` usando a propriedade `forwardPorts`, ou você pode usar o painel "Portas" no seu codespace.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Clique com o botão direito na porta que você deseja adicionar à configuração do codespace e, em seguida, clique em **Definir etiqueta e atualizar devcontainer.json**. ![Opção para definir a etiqueta e adicionar a porta ao devcontainer.json no menu com o clique no botão direito](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..3031defd0d
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: Desenvolver em um codespace
+intro: 'Crie um codespace para começar a desenvolver seu projeto dentro de um ambiente de nuvem dedicado. Você pode usar portas encaminhadas para executar o seu aplicativo e até mesmo usar codespaces dentro de {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..39324761fc
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: Usar espaços de código no Visual Studio Code
+intro: 'Você pode desenvolver seu codespace diretamente em {% data variables.product.prodname_vscode %}, conectando a extensão de {% data variables.product.prodname_github_codespaces %} à sua conta no {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Pré-requisitos
+
+Para desenvolver em um código diretamente em {% data variables.product.prodname_vscode %}, você deve inscrever-se na extensão de {% data variables.product.prodname_github_codespaces %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode %}.
+
+Use o {% data variables.product.prodname_vs %} Marketplace para instalar a extensão [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}.
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_dotcom %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**.
+4. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Utilize o menu suspenso "EXPLORADOR REMOTO" e clique em **{% data variables.product.prodname_github_codespaces %}**. ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_codespaces %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**.
+5. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão.
+
+{% endwindows %}
+
+### Criar um codespace em {% data variables.product.prodname_vscode %}
+
+Depois de conectar sua conta de {% data variables.product.product_name %} à extensão de {% data variables.product.prodname_github_codespaces %}, você pode desenvolver em um codespace que você criou no {% data variables.product.product_name %} ou em {% data variables.product.prodname_vscode %}.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Clique no ícone Adicionar e, em seguida, clique em **Criar novo codespace**. ![A opção "Criar novo codespace" em {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. Digite e, em seguida, clique no nome do repositório no qual você deseja desenvolver. ![Pesquisar um repositório para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. Clique no branch que você deseja desenvolver. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Clique no tipo de máquina na qual você deseja desenvolver. ![Tipos de instância para um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png)
+### Abrir um codespace em {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Em "Codedespaces", clique no código que você deseja desenvolver.
+3. Clique no ícone Conectar-se ao Codespace. ![Ícone de conectar-se a um Codespace em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### Alterar o tipo da máquina em {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+Você pode alterar o tipo de máquina do seu codespace a qualquer momento.
+
+1. Em {% data variables.product.prodname_vscode %}, abra a Paleta de Comando (`shift comando P` / `shift control P`).
+2. Pesquise e selecione "Codespaces: Alterar tipo de máquina." ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. Clique no codespace que você deseja alterar. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. Escolha o tipo de máquina que você quer usar. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+Se o codespace estiver sendo executado, será exibida uma mensagem perguntando se você deseja reiniciar e reconectar-se ao seu codespace agora. Clique em **Sim** se desejar mudar o tipo de máquina utilizado para este codespace imediatamente. Se você clicar em **Não**, ou se o código não estiver em execução, a alteração entrará em vigor na próxima vez que o codespace for reiniciado.
+
+### Excluir um codespace em {% data variables.product.prodname_vscode %}
+
+1. Em "Codedespaces", clique com o botão direito no código que você deseja excluir.
+2. No menu suspenso, clique em **Excluir o codespace**. ![Excluir um codespace em {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..369b04e544
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Usando controle de origem no seu codespace
+intro: 'Depois de fazer alterações em um arquivo no seu código, você pode fazer um commit rápido das alterações e fazer push da sua atualização para o repositório remoto.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Sobre o controle de origem em {% data variables.product.prodname_codespaces %}
+
+Você pode executar todas as ações do Git necessárias diretamente no seu codespace. Por exemplo, é possível obter alterações do repositório remoto, alternar os branches, criar um novo branch, fazer commit, fazer push e criar um pull request. Você pode usar o terminal integrado dentro do seu codespace para inserir nos comandos do Git, ou você pode clicar em ícones e opções de menu para realizar todas as tarefas mais comuns do Git. Este guia explica como usar a interface gráfica de usuário para controle de origem.
+
+O controle de origem em {% data variables.product.prodname_github_codespaces %} usa o mesmo fluxo de trabalho que {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte a documentação {% data variables.product.prodname_vscode %}"[Usando Controle de Versão no Código VS](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)".
+
+Um fluxo de trabalho típico para atualizar um arquivo que usa {% data variables.product.prodname_github_codespaces %} seria:
+
+* A partir do branch padrão do seu repositório em {% data variables.product.prodname_dotcom %}, crie um codespace. Consulte "[Criando um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".
+* No seu código, crie uma nova agência para trabalhar.
+* Faça suas alterações e salve-as.
+* Faça commit da alteração.
+* Abra um pull request.
+
+### Criar ou trocar de branches
+
+1. Se o branch atual não for mostrado na barra de status, na parte inferior do seu codespace, clique com o botão direito na barra de status e selecione **Controle de origem**.
+1. Clique no nome do branch na barra de status. ![O branch na barra de status](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. No menu suspenso, clique no branch para o qual você deseja alternar ou digite o nome de um novo branch e clique em **Criar novo branch**. ![Escolha no menu do branch](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Dica**: Se alguém alterou um arquivo no repositório remoto, no branch para o qual você mudou, você não verá essas alterações até você fazer pull das alterações no seu codespace.
+
+{% endtip %}
+
+### Fazer pull das alterações do repositório remoto
+
+Você pode fazer pull das alterações do repositório remoto para seu codespace a qualquer momento.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. Na parte superior da barra lateral, clique na elipse (**...**). ![Botão Elipsis para visualizar e mais ações](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. No menu suspenso, clique em **Pull**.
+
+Se um contêiner de desenvolvimento foi alterado desde que você criou o codespace, você poderá aplicar as alterações reconstruindo o contêiner para o codespace. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)".
+
+### Configurar o seu codespace para buscar novas alterações automaticamente
+
+É possível definir seu codespace para obter automaticamente os detalhes de quaisquer novos commits que tenham sido criados no repositório remoto. Isso permite que você veja se sua cópia local do repositório está desatualizada. Nesse caso, você pode optar por fazer pull das novas alterações.
+
+Se a operação de busca detectarem novas alterações no repositório remoto, você verá o número de novos commits na barra de status. Você pode fazer pull das alterações para a sua cópia local.
+
+1. Clique no botão **Gerenciar** na parte inferior da barra de atividades. ![Botão Gerenciar](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Clique em **Criar**.
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. Na parte superior da barra lateral, clique na elipse (**...**). ![Botão Elipsis para visualizar e mais ações](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..7f1c9e8c04
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Primeiros passos com o seu projeto C# (.NET) em codespaces
+shortTitle: Primeiros passos com o seu projeto C# (.NET)
+allowTitleToDifferFromFilename: true
+intro: 'Primeiros passos com o seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introdução
+
+Este guia mostra como configurar seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo.
+
+#### Pré-requisitos
+
+- Você deve ter um projeto C# (.NET) existente em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
+
+Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu codespace têm várias linguagens e tempos de execução, incluindo .NET. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano.
+
+Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados.
+
+{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+O contêiner de codespaces padrão vem com a versão mais recente do .NET e as ferramentas mais comuns pré-instaladas. No entanto, recomendamos que você configure um contêiner personalizado para que possa personalizar as ferramentas e scripts que são executados como parte da criação do codespace para as necessidades do seu projeto e garantir um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} no seu repositório.
+
+Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar codespaces para o seu projeto ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. Para este exemplo, clique em **C# (.NET)**. Se você precisar de funcionalidades adicionais, você poderá selecionar qualquer contêiner específico para o C# (.NET) ou uma combinação de ferramentas como C# (.NET) e MS SQL. ![Selecione a opção C# (.NET) na lista](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Clique na versão recomendada do .NET. ![Seleção da versão .NET](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Aceite a opção padrão para adicionar Node.js à sua personalização. ![Adicionar seleção de Node.js](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+A adição do modelo de contêiner de C# (.NET) adiciona uma pasta de contêiner de desenvolvimento `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos:
+
+- `devcontainer.json`
+- arquivo Docker
+
+O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. Mais informações: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Nome** - Você pode dar qualquer nome ao nosso contêiner de desenvolvimento. Este é apenas o padrão.
+- **Build** - As propriedades de compilação.
+  - **Arquivo Docker** - No objeto de compilação, `arquivo Docker` é uma referência ao arquivo arquivo Docker que também foi adicionado a partir do template.
+  - **Args**
+    - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a versão do .NET Core que queremos usar.
+- **Configurações** - Estas são as configurações de {% data variables.product.prodname_vscode %}.
+  - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - A extensão Microsoft C# fornece amplo suporte para o desenvolvimento em C#, incluindo funcionalidades como IntelliSense, links, depuração, navegação de código, formatação de código, refatoração, explorador de variáveis, explorador de testes e muito mais.
+- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente.
+- **postCreateCommand** - Se você quiser executar qualquer coisa depois de parar no seu codespace, isso não estará definido no arquivo Docker como a `Dotnet restore`. Você pode fazer isso aqui.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### arquivo Docker
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+Você pode usar o arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do OS, versões de nó ou pacotes globais que queremos que sejam incluídos no nosso contêiner.
+
+### Etapa 3: Modifique seu arquivo devcontainer.json
+
+Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar extensões e restaurar as dependências do seu projeto quando o seu codespace for iniciado.
+
+1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Atualize a sua lista de `extensões` no seu arquivo `devcontainer.json` para adicionar algumas extensões úteis ao trabalhar com o seu projeto.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Remova o comentário o `postCreateCommand` para restaurar as dependências como parte do processo de configuração do codespace.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' para executar os comandos após a criação do contêiner.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. Para reconstruir seu contêiner e aplicar as alterações do devcontainer.json, acesse a paleta de comandos (`shift comando P` / `shift control P`). Em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Verifique se suas alterações foram aplicadas com sucesso verificando se a extensão "Code Spell Checker" foi instalada.
+
+    ![Lista de extensões](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via pip3. Com nossas dependências agora instaladas, podemos executar nosso aplicativo.
+
+1. Execute seu aplicativo pressionando `F5` ou inserindo `dotnet watch run` no seu terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Próximas etapas
+
+Agora você deve estar pronto para começar a desenvolver seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados.
+
+- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..ac843ec632
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Primeiros passos com o seu projeto Java no Codespaces
+shortTitle: Primeiros passos para seu projeto Java
+intro: 'Dê os primeiros passos com o seu projeto Java em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introdução
+
+Este guia mostra como configurar seu projeto Java em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo.
+
+#### Pré-requisitos
+
+- Você deve ter um projeto Java existente em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
+
+Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner do seu código possui muitas linguagens e tempos de execução, incluindo Java, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano.
+
+Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados.
+
+{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+O contêiner de codespaces padrão vem com a versão mais recente do Java, gerenciadores de pacotes (Maven, Gradle) e outras ferramentas comuns pré-instaladas. No entanto, recomendamos que você configure um contêiner personalizado para definir as ferramentas e scripts de que seu projeto precisa. Isso garantirá um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} do seu repositório.
+
+Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar espaços de códigos para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. Para este exemplo, clique em **Java**. Na prática, você pode selecionar qualquer contêiner específico para Java ou uma combinação de ferramentas como Java e Azure Functions. ![Selecione a opção Java na lista](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Clique na versão recomendada do Java. ![Seleção da versão Java](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+A adição do modelo de contêiner de desenvolvimento Java adiciona uma pasta `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos:
+
+- `devcontainer.json`
+- arquivo Docker
+
+O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. Consulte https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - As propriedades de compilação.
+  - **Arquivo Docker** - No objeto de compilação, o arquivo Docker é uma referência ao arquivo Docker que também foi adicionado a partir do template.
+  - **Args**
+    - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a versão de Java que é passada para o arquivo Docker.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - O pacote de extensão Java fornece extensões populares para o desenvolvimento do Java para você começar.
+- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - Por padrão, você está executando como usuário do `vscode`, mas, opcionalmente, você pode definir isso como `root`.
+
+##### arquivo Docker
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+Você pode usar o arquivo arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do sistema operacional, versões do Java ou pacotes globais que queremos que sejam incluídos no nosso arquivo Docker.
+
+### Etapa 3: Modifique seu arquivo devcontainer.json
+
+Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar extensões e dependências do seu projeto quando seu codespace for iniciado.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  Para obter mais informações sobre as propriedades `devcontainer.json`, consulte a [referência devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) na documentação do Visual Studio Code.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via npm. Agora você pode usar isso para executar nosso aplicativo com npm.
+
+1. Execute o seu aplicativo pressionando `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Próximas etapas
+
+Agora você deve estar pronto para começar a desenvolver seu projeto Java em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados.
+
+- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..61a5ebf262
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Primeiros passos com o seu projeto Node.js em Codedespaces
+shortTitle: Primeiros passos para o seu projeto Node.js
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introdução
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo.
+
+#### Pré-requisitos
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
+
+Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu código possui muitas linguagens e tempos de execução, incluindo Node.js, JavaScript, Typescript, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano.
+
+Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados.
+
+{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- arquivo Docker
+
+O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. Mais informações: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - As propriedades de compilação.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a variante de nó que queremos usar e que é passada para o arquivo Docker.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### arquivo Docker
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+Você pode usar o arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do sistema operacional, versões de nó ou pacotes globais que queremos que sejam incluídos no nosso arquivo Docker.
+
+### Etapa 3: Modifique seu arquivo devcontainer.json
+
+Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar o npm quando seu codespace for lançado e para fazer uma lista de portas dentro do contêiner disponível localmente.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. Agora você pode usar isso para executar nosso aplicativo com npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Próximas etapas
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..4b4ec1094b
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Primeiros passos para seu projeto Python no Codedespaces
+shortTitle: Primeiros passos para seu projeto Python
+intro: 'Dê os primeiros passos com seu projeto Python em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introdução
+
+Este guia mostra como configurar seu projeto Python em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo.
+
+#### Pré-requisitos
+
+- Você deve ter um projeto Python existente em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
+
+Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu código possui muitas linguagens e tempos de execução, incluindo Node.js, JavaScript, Typescript, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano.
+
+Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados.
+
+{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+O contêiner de códigos padrão vem com a versão mais recente do Python, gerenciadores de pacotes (pip, Miniconda) e outras ferramentas comuns pré-instaladas. No entanto, recomendamos que você configure um contêiner personalizado para definir as ferramentas e scripts de que seu projeto precisa. Isso garantirá um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} do seu repositório.
+
+Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar espaços de códigos para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. Para este exemplo, clique em **Python 3**. Se precisar de funcionalidades adicionais, você poderá selecionar qualquer contêiner específico para Python ou uma combinação de ferramentas como Python 3 e PostgresSQL. ![Selecione a opção Python na lista](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Clique na versão recomendada do Python. ![Seleção de versão Python](/assets/images/help/codespaces/add-python-version.png)
+4. Aceite a opção padrão para adicionar Node.js à sua personalização. ![Adicionar seleção de Node.js](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+A adição do modelo de contêiner de desenvolvimento do Python adiciona uma pasta `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos:
+
+- `devcontainer.json`
+- arquivo Docker
+
+O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. Mais informações: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Nome** - Você pode dar qualquer nome ao nosso contêiner de desenvolvimento. Este é apenas o padrão.
+- **Build** - As propriedades de compilação.
+  - **Arquivo Docker** - No objeto de compilação, `arquivo Docker` é uma referência ao arquivo arquivo Docker que também foi adicionado a partir do template.
+  - **Args**
+    - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a variante de nó que queremos usar e que é passada para o arquivo Docker.
+- **Configurações** - Estas são as configurações de {% data variables.product.prodname_vscode %}.
+  - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação.
+- **Extensions** - These are extensions included by default.
+  - **ms-python. ython** - A extensão Microsoft Python fornece um amplo suporte para a linguagem do Python (para todas as versões ativamente compatíveis da linguagem: >=3.), incluindo recursos como IntelliSense, linting, depuração, navegação de código, formatação de código, refatoração, explorador de variáveis, explorador de teste e muito mais.
+- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente.
+- **postCreateCommand** - Se você quiser executar qualquer coisa depois de pousar no seu codespace, isso não está definido no arquivo Docker como `pip3 install -r requirements`. Você pode fazer isso aqui.
+- **remoteUser** - Por padrão, você está executando como usuário do `vscode`, mas, opcionalmente, você pode definir isso como `root`.
+
+##### arquivo Docker
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+Você pode usar o arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do OS, versões de nó ou pacotes globais que queremos que sejam incluídos no nosso contêiner.
+
+### Etapa 3: Modifique seu arquivo devcontainer.json
+
+Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar extensões e dependências do seu projeto quando o seu codespace for iniciado.
+
+1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Atualize a lista de extensões `` no seu arquivo `devcontainer.json` para adicionar algumas extensões que são úteis ao trabalhar com seu projeto.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Remova o comentário o `postCreateCommand` para instalar automaticamente os requisitos como parte do processo de configuração dos codespaces.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' para executar os comandos após a criação do contêiner.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. Para reconstruir seu contêiner e aplicar as alterações do devcontainer.json, acesse a paleta de comandos (`shift comando P` / `shift control P`). Em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Verifique se suas alterações foram aplicadas com sucesso verificando se as extensões Code Spell Checker e Flask Snippet foram instaladas.
+
+    ![Lista de extensões](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via pip3. Com suas dependências agora instaladas, você pode executar seu aplicativo.
+
+1. Execute seu aplicativo pressionando `F5` ou digitando `python -m Flask run` no terminal do codespace.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Próximas etapas
+
+Agora você deve estar pronto para começar a desenvolver seu projeto Python em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados.
+
+- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..f5e823be65
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: 'Primeiros passos com {% data variables.product.prodname_codespaces %}'
+intro: 'Aprenda como dar os primeiros passos com {% data variables.product.prodname_codespaces %}, incluindo a configuração para linguagens específicas.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/pt-BR/content/codespaces/guides.md b/translations/pt-BR/content/codespaces/guides.md
new file mode 100644
index 0000000000..fb19b16082
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: Guias
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/pt-BR/content/codespaces/index.md b/translations/pt-BR/content/codespaces/index.md
new file mode 100644
index 0000000000..df9aee66d9
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: https://www.youtube-nocookie.com/embed/_W9B7qc9lVc
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
\ No newline at end of file
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..73e043f884
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Gerenciando codespaces para a sua organização
+intro: 'Você pode gerenciar e revisar como os usuários da sua organização podem usar  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..851c2ca722
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Gerenciar os codespaces de acesso e segurança da sua organização
+shortTitle: Gerenciar o acesso e a segurança da sua organização
+intro: 'Você pode gerenciar os repositórios na sua organização que {% data variables.product.prodname_codespaces %} pode acessar.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Os proprietários da organização podem gerenciar quais repositórios um codespace pode acessar.
+
+By default, a codespace can only access the repository where it was created. Ao habilitar o acesso e a segurança de um repositório pertencente à sua organização, todos os codespaces que forem criados para esse repositório também terão permissões de leitura e gravação para todos os outros repositórios que a organização possui e o criador de codespace terá permissões para acessar. Se você deseja restringir os repositórios que um codespace pode acessar, você pode limitá-lo ao repositório em que o codespace foi criado ou a repositórios específicos. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia.
+
+Para gerenciar quais usuários na sua organização podem usar {% data variables.product.prodname_codespaces %}, consulte "[Gerenciar permissões de usuário para a sua organização](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)".
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Em "Acesso e segurança", selecione a configuração que você deseja para a sua organização. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para permitir que os codespaces do repositório acessem outros repositórios pertencentes à sua organização. Repita isso para todos os repositórios cujos códigos você deseja que acessem outros repositórios. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
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
new file mode 100644
index 0000000000..92260550e5
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Gerenciar segredos criptografados para o seu repositório e organização para codespaces
+shortTitle: Gerenciar segredos para o seu repositório e organização
+intro: 'Os segredos criptografados permitem que você armazene informações confidenciais na sua organização, repositório ou {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Sobre segredos
+
+Segredos são variáveis de ambiente criptografadas que você cria em uma organização ou repositório. Os segredos que você criou estão disponíveis para uso em {% data variables.product.prodname_codespaces %}. O GitHub usa uma [caixa protegida pela libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para criptografar segredos antes que eles cheguem ao GitHub e só descriptografa quando você os usa em um codespace.
+
+Os segredos no nível da organização permitem que você compartilhe segredos entre vários repositórios, o que reduz a necessidade de criar segredos duplicados. Você pode usar políticas de acesso para controlar quais repositórios podem usar segredos da organização.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Nomeando segredos
+
+{% data reusables.codespaces.secrets-naming %} Por exemplo, um segredo criado no nível do repositório deve ter um nome exclusivo nesse repositório, e um segredo criado no nível da organização deve ter um nome exclusivo nesse nível.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Limites para segredos
+
+Você pode armazenar até 100 segredos por organização e 100 segredos por repositório.
+
+Os segredos são limitados a 64 kB.
+
+### Adicionar segredos para um repositório
+
+Para criar segredos para um repositório da organização, você deve ter acesso de administrador.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Desça a barra de rolagem e, em **Segredos**, selecione **Codespaces**. ![Opção de codespace na barra lateral](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. Na parte superior da página, clique em **Novo segredo de repositório**.
+1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
+1. Insira o valor para o seu segredo.
+1. Clique em **Add secret** (Adicionar segredo).
+
+### Adicionar segredos para uma organização
+
+Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios.
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Desça a barra de rolagem e, em **Segredos**, selecione **Codespaces**. ![Opção de codespace na barra lateral](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. Na parte superior da página, clique em **Novo segredo de organização**.
+1. Digite um nome para o seu segredo na caixa de entrada **Nome**.
+1. Insira o **Valor** para o seu segredo.
+1. Na lista suspensa **Acesso do repositório**, escolha uma política de acesso. ![Lista de Acesso ao Repositório com repositórios privados selecionados](/assets/images/help/codespaces/secret-repository-access.png)
+1. Clique em **Add secret** (Adicionar segredo).
+
+### Rever o acesso para os segredos do nível da organização
+
+Você pode verificar quais políticas de acesso são aplicadas a um segredo na sua organização.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. A lista de segredos inclui quaisquer permissões e políticas configuradas. Por exemplo: ![Lista de segredos](/assets/images/help/settings/actions-org-secrets-list.png)
+1. Para obter mais detalhes sobre as permissões configuradas para cada segredo, clique em **Atualizar**.
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..fee663a78c
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..f6de804a4a
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Revisando os logs de auditoria da sua organização para os codespaces
+shortTitle: Revisando os logs de auditoria da sua organização
+intro: 'Você pode usar o log de auditoria para revisar todas as ações relacionadas a {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Quando qualquer integrante da sua organização executa uma ação relacionada a {% data variables.product.prodname_codespaces %}, você poderá revisar as ações no log de auditoria. Para obter informações sobre acesso ao registro, consulte "[Revisar seu log de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)".
+
+![Log de auditoria com informações sobre codespaces](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+O log de auditoria inclui detalhes como quem realizou a ação, qual foi a ação e quando a ação foi realizada. Para obter informações sobre ações de {% data variables.product.prodname_codespaces %}, consulte "[ações de categoria de {% data variables.product.prodname_codespaces %}](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)."
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..43e257c4d4
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Em "Acesso e segurança", selecione a configuração que deseja para sua conta de usuário. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. Se você escolher "repositórios selecionados", selecione o menu suspenso e clique em um repositório para permitir que os codespaces do repositório tenham acesso a outros repositórios dos quais você é proprietário. Repita para todos os repositórios cujos codespaces você deseja que acessem outros repositórios dos quais você é proprietário. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..5ef6048c37
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 'Você pode armazenar informações confidenciais, como tokens, que você deseja acessar nos seus codespaces por meio de variáveis de ambiente.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### Sobre os segredos criptografados para {% data variables.product.prodname_codespaces %}
+
+Você pode adicionar segredos criptografados à sua conta de usuário que deseja usar nos seus codespaces. Por exemplo, você pode querer armazenar e acessar as seguintes informações confidenciais como segredos criptografados.
+
+- Tokens de acesso pessoal para os serviços da nuvem
+- Entidades de serviço
+- Identificadores da assinatura
+- [Credenciais para um registro de imagens privado](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+Você pode escolher quais repositórios devem ter acesso a cada segredo. Em seguida, você pode usar o segredo em qualquer código que criar para um repositório que tiver acesso ao segredo.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Nomeando segredos
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Limites para segredos
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+Os segredos são limitados a 64 kB.
+
+### Adicionar um segredo
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. À direita dos "Segredos dos codespaces", clique em **Novo segredo**. ![Botão "Novo segredo"](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. Em "Nome", digite um nome para seu segredo. ![Caixa de texto "Nome"](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Clique em **Add secret** (Adicionar segredo).
+
+### Editar um segredo
+
+Você pode atualizar o valor de um segredo existente, bem como alterar quais repositórios podem acessar um segredo.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Em "Segredos do codespace", à direita do segredo que você deseja editar, clique em **Atualizar**. ![Botão "Atualizar"](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. Em "Valor", clique em **Inserir um novo valor**. ![Link "Inserir um novo valor"](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Opcionalmente, para remover o acesso do segredo a um repositório, desmarque o repositório. ![Caixas de seleção para remover acesso aos repositórios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. Clique em **Save changes** (Salvar alterações).
+
+### Excluir um segredo
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Em "Segredos dos codespaces", à direita do segredo que você deseja excluir, clique em **Excluir**. ![Botão "Excluir"](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. Leia o alerta e clique em **OK**. ![Confirmação para excluir um segredo](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..5a604802b7
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: Gerenciar a verificação de GPG de codespaces
+intro: 'Você pode permitir que {% data variables.product.company_short %} use o GPG automaticamente para assinar os commits que você faz nos seus codespaces para que outras pessoas possam confiar que as alterações vêm de uma fonte de confiança.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Depois que você habilitar a verificação do GPG, {% data variables.product.company_short %} assinará automaticamente os commits que você fizer em {% data variables.product.prodname_codespaces %}, e os commits terão um status de verificado em {% data variables.product.product_name %}. Por padrão, a verificação do GPG está desabilitada para os codespaces que você criar. Você pode optar por permitir a verificação do GPG para todos os repositórios ou repositórios específicos. Habilite apenas a verificação do GPG para repositórios nos quais você confia. Para obter mais informações sobre commits assinado por {% data variables.product.product_name %}, consulte "[Sobre a verificação de assinatura do commit](/github/authenticating-to-github/about-commit-signature-verification)".
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Em "Verificação do GPG, selecione a configuração que deseja para verificação do GPG. ![Botões de opção para gerenciar a verificação do GPG](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para o qual deseja habilitar a verificação do GPG. Repita esse procedimento para todos os repositórios para os quais você deseja habilitar a verificação do GPG. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..b69fdd3417
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. Para obter informações sobre acesso ao registro, consulte "[Revisar seu log de segurança](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)".
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+O log de segurança inclui detalhes sobre qual ação ocorreu e quando você a executou. Para obter informações sobre ações de {% data variables.product.prodname_codespaces %}, consulte "[ações de categoria de {% data variables.product.prodname_codespaces %}](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
diff --git a/translations/pt-BR/content/codespaces/quickstart.md b/translations/pt-BR/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..76f935605d
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introdução
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. No nome do repositório, use o menu suspenso do {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com os espaços de código**.
+
+  ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..04d0b08ba6
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,142 @@
+---
+title: Configurar codespaces para seu projeto
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### arquivo Docker
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um código com uma imagem-base do Linux. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Follow the prompts to customize your definition.
+1. Clique em **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### Criar uma configuração personalizada de codespace
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+Você pode definir as configurações de editor-padrão para {% data variables.product.prodname_vscode %} em dois lugares.
+
+* As configurações do editor definidas em `.vscode/settings.json` são aplicadas como configurações do escopo do _espaço de trabalho_ no codespace.
+* Configurações do editor definidas na chave `Configurações` no `devcontainer.json` são aplicadas como configuração de escopo _Remote [Codespaces]_ nesse codespace.
+
+After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)."
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### Applying changes to your configuration
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}
+!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - To diagnose the error by reviewing the creation logs, click **View creation log**.
+   - To fix the errors identified in the logs, update your `devcontainer.json` file.
+   - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md b/translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..0bda3efd2f
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: Personalizar os codespaces para a sua conta
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+Os mantenedores do projeto também podem definir uma configuração-padrão que se aplica a todos os codespaces de um repositório, criados por qualquer pessoa. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)".
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+Os Dotfiles são arquivos e pastas de sistemas de tipo Unix, que começam com `.` e controlam a configuração de aplicativos e shells no seu sistema. Você pode armazenar e gerenciar seus dotfiles em um repositório no {% data variables.product.prodname_dotcom %}. Para obter aconselhamento e tutoriais sobre o que incluir no repositório `dotfiles`, consulte [GitHub gerencia dotfiles](https://dotfiles.github.io/).
+
+Se sua conta de usuário no {% data variables.product.prodname_dotcom %} possui um repositório público denominado `dotfiles`, o {% data variables.product.prodname_dotcom %} usa este repositório automaticamente para personalizar seu ambiente de codespace. Atualmente, não são compatíveis os repositórios privados `dotfiles`.
+
+O seu repositório `dotfiles` pode incluir os alias e preferências do seu shell, quaisquer ferramentas que você deseja instalar ou qualquer outra personalização de codespace que desejar fazer.
+
+Ao criar um novo codespace, o {% data variables.product.prodname_dotcom %} clona seus repositórios de `dotfiles` para o ambiente do codespace e procura por um dos seguintes arquivos para configurar o ambiente.
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+Se nenhum desses arquivos for encontrado, quaisquer arquivos ou pastas nos `dotfiles` que comecem com `.` será vinculado simbolicamente ao diretório `~` ou `$HOME` do codespace.
+
+Quaisquer alterações no repositório de `dotfiles` serão aplicadas apenas a cada novo codespace e não afetarão nenhum codespace existente.
+
+{% note %}
+
+**Observação:** Atualmente, o {% data variables.product.prodname_codespaces %} não é compatível com a personalização das configurações do _Usuário_ para o editor de {% data variables.product.prodname_vscode %} com o repositório `dotfiles`. É possível definir as configurações-padrão do _espaço de trabalho_ e _Remote [Codespaces]_ para um projeto específico no repositório do projeto. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)".
+
+{% endnote %}
+
+Você também pode definir as configurações para que a sua conta de usuário adicione segredos criptografados, habilitar a verificação de GPG e permitir que os seus codespaces acessem outros repositórios. Para obter mais informações, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Gerenciar verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)" e "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)".
+
+### Leia mais
+
+* "[Criar um repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md
index c2e6c61de5..11480386df 100644
--- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ Com wikis, é possível gravar conteúdo assim como em qualquer outro lugar no {
 
 Você pode editar wikis diretamente no {% data variables.product.product_name %} ou editar arquivos wiki localmente. Por padrão, somente as pessoas com acesso de gravação ao repositório podem fazer alterações no wikis, embora você possa permitir que todos em {% data variables.product.product_location %} contribuam para um wiki em {% if currentVersion == "github-ae@latest" %}um repositório interno{% else %}público{% endif %}. Para obter mais informações, consulte "[Alterar permissões de acesso para wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)".
 
+{% note %}
+
+**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository.
+
+{% endnote %}
+
 ### Leia mais
 
 - "[Adicionar ou editar páginas wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
diff --git a/translations/pt-BR/content/communities/index.md b/translations/pt-BR/content/communities/index.md
index 2f4b4df409..6bb90e22e0 100644
--- a/translations/pt-BR/content/communities/index.md
+++ b/translations/pt-BR/content/communities/index.md
@@ -1,5 +1,5 @@
 ---
-title: Building communities
+title: Criar comunidades
 intro: 'Quer seu projeto seja de código aberto ou privado, você pode criar um ambiente saudável e eficaz para a colaboração.'
 redirect_from:
   - /categories/building-a-strong-community
diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index e831ca46a9..b85f8c024b 100644
--- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ Nos repositórios da sua organização, os usuários bloqueados também não pod
 ### Bloquear um usuário nas configurações da organização
 
 1. Para bloquear um integrante da organização, primeiramente, [ remova o usuário](/articles/removing-a-member-from-your-organization) da organização.
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. Em "Block a user" (Bloquear um usuário), digite o nome de usuário que deseja bloquear. ![Campo Username (Nome de usuário)](/assets/images/help/organizations/org-block-username-field.png)
 7. Se quiser configurar um limite de tempo para o bloqueio, use o menu suspenso Block options (Opções de bloqueio) e selecione o período pelo qual deseja bloquear o usuário. ![Menu suspenso Block options (Opções de bloqueio)](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index 882b853a94..01d83b57cd 100644
--- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,9 +28,9 @@ Se você tiver selecionado uma duração para o bloqueio do usuário, ele será
 
 ### Desbloquear usuários nas configurações da organização
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Em "Blocked users" (Usuários bloqueados), clique em **Unblock** (Desbloquear) próximo ao usuário que deseja desbloquear. ![Botão Unblock user (Desbloquear usuário)](/assets/images/help/organizations/org-unblock-user-button.png)
 
diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index 79c48a08df..e9a9595aca 100644
--- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,9 +10,9 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Em "Blocked users" (Usuários bloqueados), revise a lista de usuários que estão bloqueados da organização. ![Lista de usuários bloqueados](/assets/images/help/settings/list-of-blocked-users-for-org.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 d8083c3b07..fe79519e02 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
@@ -28,9 +28,9 @@ Os proprietários da organização também podem bloquear os usuários por um de
 
 ### Restringir interações na organização
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Na barra lateral de configurações da organização, clique em **Configurações de moderação**. !["Configurações de moderação" na barra lateral das configurações da organização](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. Em "Configurações de moderação", clique em **Limites de interação**. !["Limites de interação" na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 5a4daae8ae..abd9e51b83 100644
--- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -21,7 +21,7 @@ Você pode adicionar arquivos padrão de saúde da comunidade à raiz de um repo
 - a pasta `.github`
 - a pasta `docs`
 
-Por exemplo, qualquer pessoa que cria um problema ou uma pull request em um repositório público que não tem o próprio arquivo CONTRIBUTING verá um link para o arquivo CONTRIBUTING padrão. Se um repositório tiver arquivos na usa própria pasta `.github/ISSUE_TEMPLATE`{% if currentVersion == "free-pro-team@latest" or currentversion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}, incluindo modelos de problema ou um arquivo *config.yml*,{% endif %} nenhum conteúdo da pasta padrão `.github/ISSUE_TEMPLATE` será usado.
+Por exemplo, qualquer pessoa que cria um problema ou uma pull request em um repositório público que não tem o próprio arquivo CONTRIBUTING verá um link para o arquivo CONTRIBUTING padrão. Se um repositório tiver arquivos na usa própria pasta `.github/ISSUE_TEMPLATE`{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}, incluindo modelos de problema ou um arquivo *config.yml*,{% endif %} nenhum conteúdo da pasta padrão `.github/ISSUE_TEMPLATE` será usado.
 
 Os arquivos padrão não são incluídos em clones, pacotes ou downloads de repositórios individuais, pois eles são armazenados somente no repositório `.github`.
 
@@ -29,14 +29,14 @@ Os arquivos padrão não são incluídos em clones, pacotes ou downloads de repo
 
 Você pode criar padrões na sua organização{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou conta de usuário{% endif %} para os seguintes arquivos de saúde da comunidade:
 
-| Arquivo de integridade da comunidade                                                                                                                                                                     | Descrição                                                                                                                                                                                                                                                                                                                                                                         |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| Arquivo de integridade da comunidade                                                                                                                                                                     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
 | *CODE_OF_CONDUCT.md*                                                                                                                                                                                   | Um arquivo CODE_OF_CONDUCT define os padrões de como ingressar em uma comunidade. Para obter mais informações, consulte "[Adicionar um código de conduta ao projeto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %}
 | *CONTRIBUTING.md*                                                                                                                                                                                        | Um arquivo CONTRIBUTING comunica como as pessoas devem contribuir com o seu projeto. Para obter mais informações, consulte "[Definir diretrizes para contribuidores de repositórios](/articles/setting-guidelines-for-repository-contributors/)".{% if currentVersion == "free-pro-team@latest" %}
 | *FUNDING.yml*                                                                                                                                                                                            | Um arquivo FUNDING exibe um botão de patrocinador no repositório para aumentar a visibilidade das opções de financiamento para seu projeto de código aberto. Para obter mais informações, consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %}
-| Modelos de problemas e pull request{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e *config.yml*{% endif %} | Os modelos de problema e pull request personalizam e padronizam as informações que você deseja que contribuidores incluam quando eles abrem problemas e pull requests no seu repositório. Para obter mais informações, consulte "[Sobre problemas e modelos de pull request](/articles/about-issue-and-pull-request-templates/).{% if currentVersion == "free-pro-team@latest" %}
-| *SECURITY.md*                                                                                                                                                                                            | Um arquivo SECURITY fornece instruções sobre como relatar com responsabilidade uma vulnerabilidade de segurança em seu projeto. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/articles/adding-a-security-policy-to-your-repository)".{% endif %}
-| *SUPPORT.md*                                                                                                                                                                                             | Um arquivo SUPPORT permite que as pessoas conheçam maneiras de obter ajudar com seu projeto. Para obter mais informações, consulte "[Adicionar recursos de suporte ao projeto](/articles/adding-support-resources-to-your-project/)".                                                                                                                                             |
+| Modelos de problemas e pull request{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e *config.yml*{% endif %} | Os modelos de problema e pull request personalizam e padronizam as informações que você deseja que contribuidores incluam quando eles abrem problemas e pull requests no seu repositório. Para obter mais informações, consulte "[Sobre problemas e modelos de pull request](/articles/about-issue-and-pull-request-templates/).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| *SECURITY.md*                                                                                                                                                                                            | A SECURITY file gives instructions for how to report a security vulnerability in your project. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/code-security/getting-started/adding-a-security-policy-to-your-repository)".{% endif %}
+| *SUPPORT.md*                                                                                                                                                                                             | Um arquivo SUPPORT permite que as pessoas conheçam maneiras de obter ajudar com seu projeto. Para obter mais informações, consulte "[Adicionar recursos de suporte ao projeto](/articles/adding-support-resources-to-your-project/)".                                                                                                                                                                                              |
 
 Você não pode criar um arquivo de licença padrão. Os arquivos de licença devem ser adicionados a repositórios individuais para que o arquivo seja incluído quando um projeto for clonado, empacotado ou baixado.
 
diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md
index fd059c9a9e..73bc7c35a2 100644
--- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md
+++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md
@@ -1,6 +1,6 @@
 ---
 title: Configurar projeto para contribuições úteis
-shortTitle: Healthy contributions
+shortTitle: Contribuições saudáveis
 intro: Os mantenedores de repositório podem definir diretrizes de contribuição para ajudar os colaboradores a fazer contribuições relevantes e úteis a um projeto.
 redirect_from:
   - /articles/helping-people-contribute-to-your-project/
diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index 1b5dba10b3..100b64ec48 100644
--- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-Para ajudar os contribuidores do projeto a fazer um bom trabalho, você pode adicionar um arquivo com diretrizes de contribuição às pastas raiz, `docs` ou `.github` do repositório do projeto. Quando alguém abrir uma pull request ou criar um problema, verá um link para esse arquivo.
+### About contributing guidelines
+Para ajudar os contribuidores do projeto a fazer um bom trabalho, você pode adicionar um arquivo com diretrizes de contribuição às pastas raiz, `docs` ou `.github` do repositório do projeto. Quando alguém abrir uma pull request ou criar um problema, verá um link para esse arquivo. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![diretrizes de contribuição](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ Você pode criar diretrizes de contribuição padrão para a organização{% if
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. Decida se deseja armazenar as diretrizes de contribuição no diretório root, `docs` ou `.github` do repositório. Em seguida, no campo de nome do arquivo, digite o nome e a extensão do arquivo. Os nomes de arquivo das diretrizes de contribuição não diferenciam maiúsculas de minúsculas e podem ter uma extensão *.md* ou *.txt*. ![Nome do novo arquivo](/assets/images/help/repository/new-file-name.png)
+3. Decida se deseja armazenar as diretrizes de contribuição no diretório root, `docs` ou `.github` do repositório. Em seguida, no campo de nome do arquivo, digite o nome e a extensão do arquivo. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![Nome do novo arquivo](/assets/images/help/repository/new-file-name.png)
     - Para tornar as diretrizes de contribuição visíveis no diretório raiz do repositório, digite *CONTRIBUTING*.
     - Para tornar as diretrizes de contribuição visíveis no diretório `docs` do repositório, digite *docs/* para criar o diretório e, em seguida, digite *CONTRIBUTING*.
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. Adicione as diretrizes de contribuição ao novo arquivo. Elas podem conter:
     - Etapas para criar bons problemas ou pull requests.
     - Links para documentações externas, listas de distribuição ou um código de conduta.
diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
index 6b9683294b..981ca3fbff 100644
--- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
+++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Usando modelos para incentivar problemas úteis e receber pull request
-shortTitle: Issue & PR templates
+shortTitle: Problema & Modelos PR
 intro: Os mantenedores de repositório podem adicionar modelos a um repositório para ajudar os contribuidores a criar problemas e pull requests de alta qualidade.
 redirect_from:
   - /github/building-a-strong-community/using-issue-and-pull-request-templates
diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md
index ef096cc901..dea74b27c8 100644
--- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md
+++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md
@@ -1,6 +1,6 @@
 ---
 title: Cherry-picking a commit
-intro: You can pick a specific commit on one branch and copy the commit to another branch.
+intro: Você pode escolher um commit específico em um branch e copiar o commit para outro branch.
 versions:
   free-pro-team: '*'
 ---
diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md
index 308d780849..6bf7e6a840 100644
--- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md
+++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md
@@ -12,7 +12,7 @@ Autenticar-se no {% data variables.product.prodname_dotcom %}."</p>
 
 Depois de se autenticar no {% data variables.product.prodname_dotcom %}, você poderá se conectar a repositórios remotos com o {% data variables.product.prodname_desktop %}. O {% data variables.product.prodname_desktop %} armazena suas credenciais (nome de usuário e senha ou token de acesso pessoal) e usa as credenciais para autenticar cada conexão ao repositório remoto.
 
-{% data variables.product.prodname_desktop %} se conecta ao {% data variables.product.prodname_dotcom %} usando HTTPS. Se você usar o {% data variables.product.prodname_desktop %} para acessar repositórios que foram clonados usando SSH, você poderá encontrar erros. Para se conectar a um repositório que foi clonado usando SSH, altere as URLs do remote. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+{% data variables.product.prodname_desktop %} se conecta ao {% data variables.product.prodname_dotcom %} usando HTTPS. Se você usar o {% data variables.product.prodname_desktop %} para acessar repositórios que foram clonados usando SSH, você poderá encontrar erros. Para se conectar a um repositório que foi clonado usando SSH, altere as URLs do remote. Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 
 
diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md
index d8052bbf04..1c63caa081 100644
--- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md
+++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md
@@ -92,6 +92,6 @@ Agora que você criou e publicou seu repositório, você está pronto para fazer
 Agora você criou um repositório, publicou o repositório no {% data variables.product.product_name %}, fez um commit e fez push das suas alterações no {% data variables.product.product_name %}. Você pode seguir esse mesmo fluxo de trabalho ao contribuir para outros projetos os quais você cria ou nos quais você colabora.
 
 ### Leia mais
-- "[Getting started with Git](/github/getting-started-with-github/getting-started-with-git)"
+- "[Primeiros passos com o Git](/github/getting-started-with-github/getting-started-with-git)"
 - "[Aprender sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)"
 - "[Começar com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)"
diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md
index 11dde1158e..80d15eb4ec 100644
--- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md
+++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md
@@ -13,7 +13,7 @@ Este guia ajudará você a dar os primeiros passos com {% data variables.product
 
 Você pode achar útil ter um entendimento básico do Git e do {% data variables.product.prodname_dotcom %} antes de começar a usar o {% data variables.product.prodname_desktop %}. Para obter mais informações, consulte os seguintes artigos.
 
-- "[Using Git](/github/getting-started-with-github/using-git)"
+- "[Usar o Git](/github/getting-started-with-github/using-git)"
 - "[Aprender sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)"
 - "[Começar com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)"
 
diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md
index 7e51c449e9..912ca5bab3 100644
--- a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -54,18 +54,18 @@ A pessoa que está criando o aplicativo será redirecionada para uma página do
 
 ##### Parâmetros do manifesto do aplicativo GitHub
 
- | Nome                  | Tipo               | Descrição                                                                                                                                                                                                                                                     |
- | --------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
- | `name`                | `string`           | O nome do aplicativo GitHub.                                                                                                                                                                                                                                  |
- | `url`                 | `string`           | **Obrigatório.** A página inicial do seu aplicativo GitHub.                                                                                                                                                                                                   |
- | `hook_attributes`     | `objeto`           | A configuração do webhook do aplicativo GitHub.                                                                                                                                                                                                               |
- | `redirect_url`        | `string`           | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
- | `callback_urls`       | `array de strigns` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %}
- | `callback_url`        | `string`           | A full URL to redirect to after someone authorizes an installation.{% endif %}
- | `descrição`           | `string`           | Uma descrição do aplicativo GitHub.                                                                                                                                                                                                                           |
- | `público`             | `boolean`          | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo.                                                                                            |
- | `default_events`      | `array`            | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub.                                                                                                                                                                                 |
- | `default_permissions` | `objeto`           | O conjunto de [permissões](/rest/reference/permissions-required-for-github-apps) exigido pelo aplicativo GitHub. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`). |
+ | Nome                  | Tipo               | Descrição                                                                                                                                                                                                                                                           |
+ | --------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | `name`                | `string`           | O nome do aplicativo GitHub.                                                                                                                                                                                                                                        |
+ | `url`                 | `string`           | **Obrigatório.** A página inicial do seu aplicativo GitHub.                                                                                                                                                                                                         |
+ | `hook_attributes`     | `objeto`           | A configuração do webhook do aplicativo GitHub.                                                                                                                                                                                                                     |
+ | `redirect_url`        | `string`           | A URL completa para a qual redirecionar após um usuário iniciar a criação de um aplicativo GitHub a partir de um manifesto.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
+ | `callback_urls`       | `array de strigns` | Uma URL completa para a qual redirecionar após alguém autorizar uma instalação. Você pode fornecer até 10 URLs de chamada de retorno.{% else %}
+ | `callback_url`        | `string`           | Uma URL completa para a qual redirecionar após alguém autorizar uma instalação.{% endif %}
+ | `descrição`           | `string`           | Uma descrição do aplicativo GitHub.                                                                                                                                                                                                                                 |
+ | `público`             | `boolean`          | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo.                                                                                                  |
+ | `default_events`      | `array`            | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub.                                                                                                                                                                                       |
+ | `default_permissions` | `objeto`           | O conjunto de [permissões](/rest/reference/permissions-required-for-github-apps) exigido pelo aplicativo GitHub. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`).       |
 
 O objeto `hook_attributes` tem a chave a seguir:
 
@@ -179,7 +179,7 @@ Você deve concluir esta etapa do fluxo do manifesto do aplicativo GitHub em uma
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 Para obter mais informações sobre a resposta do ponto de extremidade, consulte [Criar um aplicativo GitHub a partir de um manifesto](/rest/reference/apps#create-a-github-app-from-a-manifest).
 
diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md
index 2b29322b11..8d4daf33e8 100644
--- a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md
@@ -16,7 +16,7 @@ topics:
 
 Você pode adicionar parâmetros de consulta a essas URLs para pré-selecionar a configuração de um {% data variables.product.prodname_github_app %} em uma conta pessoal ou de organização:
 * **Conta de usuário:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
-* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+* **Conta da organização:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
 
 A pessoa que está criando o aplicativo pode editar os valores pré-selecionados a partir da página de registro do {% data variables.product.prodname_github_app %}, antes de enviar o aplicativo. Se você não incluir os parâmetros necessários na string de consulta da URL, como, por exemplo, o `nome`, a pessoa que criar o aplicativo deverá inserir um valor antes de enviar o aplicativo.
 
@@ -40,9 +40,9 @@ Lista completa de parâmetros de consulta, permissões e eventos disponíveis en
  | -------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | `name`                     | `string`           | O nome do {% data variables.product.prodname_github_app %}. Dê um nome claro e sucinto ao seu aplicativo. Seu aplicativo não pode ter o mesmo nome de um usuário existente no GitHub, a menos que seja o seu próprio nome de usuário ou da sua organização. Uma versão movida do nome do seu aplicativo será exibida na interface do usuário quando sua integração realizar uma ação.                                                                                                                                                                                                                           |
  | `descrição`                | `string`           | Uma descrição do {% data variables.product.prodname_github_app %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
- | `url`                      | `string`           | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
- | `callback_urls`            | `array de strigns` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %}
- | `callback_url`             | `string`           | A URL completa para onde redirecionar após alguém autorizar uma instalação. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %}
+ | `url`                      | `string`           | A URL completa da página inicial do site do {% data variables.product.prodname_github_app %}. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}
+ | `callback_urls`            | `array de strigns` | Uma URL completa para a qual redirecionar após alguém autorizar uma instalação. Você pode fornecer até 10 URLs de retorno de chamada. Essas URLs são usadas se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. Por exemplo, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %}
+ | `callback_url`             | `string`           | A URL completa para onde redirecionar após alguém autorizar uma instalação. Este URL é usada se o seu aplicativo precisar identificar e autorizar solicitações de usuário para servidor.{% endif %}
  | `request_oauth_on_install` | `boolean`          | Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você poderá definir essa opção como `verdadeiro` para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando um passo. Se você selecionar esta opção, `setup_url` irá tornar-se indisponível e os usuários serão redirecionados para sua `callback_url` após instalar o aplicativo.                                                                                                                                                                                                                                                    |
  | `setup_url`                | `string`           | A URL completa para redirecionamento após alguém instalar o {% data variables.product.prodname_github_app %}, se o aplicativo precisar de configuração adicional após a instalação.                                                                                                                                                                                                                                                                                                                                                                                                                             |
  | `setup_on_update`          | `boolean`          | Defina como `verdadeiro` para redirecionar as pessoas para a URL de configuração quando as instalações forem atualizadas, por exemplo, após os repositórios serem adicionados ou removidos.                                                                                                                                                                                                                                                                                                                                                                                                                       |
@@ -89,7 +89,7 @@ Você pode selecionar permissões em uma string de consultas usando o nome da pe
 | [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring)                                        | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                                     |
 | [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                         | Concede acesso à [API de status](/rest/reference/repos#statuses). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                                        |
 | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions)                       | Concede acesso à [API de discussões de equipe](/rest/reference/teams#discussions) e à [API de comentários de discussão de equipe](/rest/reference/teams#discussion-comments). Pode ser: `none`, `read` ou `write`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %}
-| `vulnerability_alerts`                                                                                                           | Concede acesso a alertas de segurança para dependências vulneráveis em um repositório. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Pode ser: `none` ou `read`.{% endif %}
+| `vulnerability_alerts`                                                                                                           | Concede acesso a alertas de segurança para dependências vulneráveis em um repositório. Consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" para saber mais. Pode ser: `none` ou `read`.{% endif %}
 | `inspecionando`                                                                                                                  | Concede acesso à lista e alterações de repositórios que um usuário assinou. Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                              |
 
 ### Eventos webhook do {% data variables.product.prodname_github_app %}
diff --git a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index 8ad0b030f7..6b2627e61a 100644
--- a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ Você irá adicionar este novo método como um [Auxiliar do Sinatra](https://git
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      nome: 'Octo RuboCop',
-      # A estrutura da carga difere dependendo da ocorrência de um evento de execução de verificação ou de conjunto de verificações.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      nome: 'Octo RuboCop',
-      # A estrutura da carga difere dependendo da ocorrência de um evento de execução de verificação ou de conjunto de verificações.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-Este código chama o ponto de extremidade "[Criar uma execução de verificação](/rest/reference/checks#create-a-check-run)" que usa o método genérico [HTTP `POST`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). Este método tem dois parâmetros: a URL do ponto final e os parâmetros de entrada do método.
+This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
 
 Para criar uma execução de verificação, são necessários apenas dois parâmetros de entrada: `nome` e `head_sha`. Vamos usar o [Rubocop](https://rubocop.readthedocs.io/en/latest/) para implementar o teste CI mais adiante início rápido. Por esse motivo, o nome "Octo Rubocop" é usado aqui, mas você pode escolher qualquer nome que desejar para a execução da verificação.
 
@@ -240,31 +235,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -276,40 +262,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-O código acima chama o ponto de extremidade da API "[Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run)" usando o método genérico [`patch` HTTP](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) para atualizar a execução da verificação que você já criou.
+The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created.
 
-Veja o que este código está fazendo. Primeiro, ele atualiza o status de verificação de execução para `in_progress` e define o tempo do `started_at` para o tempo atual. Na [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) deste início rápido, você irá adicionar um código que inicia um teste de CI real em `***** EXECUTAR UM TEST DE CI *****`. Por enquanto, você sairá da seção como um espaço reservado, para que o código que o segue apenas simule que o processo de CI seja bem-sucedido e todos os testes sejam aprovados. Finalmente, o código atualiza o status da execução de verificação novamente para `concluído`.
+Veja o que este código está fazendo. First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. Na [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) deste início rápido, você irá adicionar um código que inicia um teste de CI real em `***** EXECUTAR UM TEST DE CI *****`. Por enquanto, você sairá da seção como um espaço reservado, para que o código que o segue apenas simule que o processo de CI seja bem-sucedido e todos os testes sejam aprovados. Finalmente, o código atualiza o status da execução de verificação novamente para `concluído`.
 
 Na documentação "[Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run)", você observará que, ao fornecer um status de `concluído`, são necessários os parâmetros `conclusão` e `completed_at`. A conclusão `` resume o resultado de uma verificação de resultado e pode ser `sucesso`, `falha`, `neutro`, `cancelado`, `timed_out` ou `action_required`. Você irá definir a conclusão como `sucesso`, o tempo `completed_at` como a hora atual e o status como `concluído`.
 
@@ -613,29 +589,23 @@ Agora você tem todas as informações de que precisa para atualizar sua execuç
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -645,51 +615,45 @@ Você deverá atualizar esse código para usar a variável de `conclusão` defin
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! E, se houver avisos, compartilhe-os.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! E, se houver avisos, compartilhe-os.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md
index cfa0ccc755..26a9be7aae 100644
--- a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md
@@ -52,7 +52,7 @@ Quando seu aplicativo GitHub especifica um parâmetro do `login`, ele solicita a
 | `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Este deve ser um match exato para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} um dos URLs fornecidos como uma **URL de Callback**{% else %} a URL fornecida no campo de **URL de callback de autorização do usuário**{% endif %} ao configurar o aplicativo GitHub e não pode conter nenhum parâmetro adicional. |
 | `estado`       | `string` | Isso deve conter uma string aleatória para proteger contra ataques falsificados e pode conter quaisquer outros dados arbitrários.                                                                                                                                                                                                                                                                                                                          |
 | `login`        | `string` | Sugere uma conta específica para iniciar a sessão e autorizar o aplicativo.                                                                                                                                                                                                                                                                                                                                                                                |
-| `allow_signup` | `string` | Whether or not unauthenticated users will be offered an option to sign up for {% data variables.product.prodname_dotcom %} during the OAuth flow. O padrão é `verdadeiro`. Use `falso` quando uma política proibir inscrições.                                                                                                                                                                                                                             |
+| `allow_signup` | `string` | Independentemente de os usuários autenticados ou não atenticados terem a opção de iscrever-se em {% data variables.product.prodname_dotcom %} durante o fluxo do OAuth. O padrão é `verdadeiro`. Use `falso` quando uma política proibir inscrições.                                                                                                                                                                                                       |
 
 {% note %}
 
diff --git a/translations/pt-BR/content/developers/apps/making-a-github-app-public-or-private.md b/translations/pt-BR/content/developers/apps/making-a-github-app-public-or-private.md
index ae27f07257..fb08471306 100644
--- a/translations/pt-BR/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/pt-BR/content/developers/apps/making-a-github-app-public-or-private.md
@@ -23,7 +23,7 @@ Os fluxos de instalação pública têm uma página inicial para permitir que ou
 
 ### Fluxo privado de instalação
 
-Os fluxos privados de instalação permitem que somente o proprietário de um aplicativo GitHub a instale. Informações limitadas sobre o GitHub App continuarão a existir em uma página pública, mas o botão **Instalar** só estará disponível para administradores da organização ou para a conta de usuário se o aplicativo GitHub for propriedade de uma conta individual. Privados ou internos, os aplicativos GitHub só podem ser instalados na conta do usuário ou da organização do proprietário.
+Os fluxos privados de instalação permitem que somente o proprietário de um aplicativo GitHub a instale. Informações limitadas sobre o GitHub App continuarão a existir em uma página pública, mas o botão **Instalar** só estará disponível para administradores da organização ou para a conta de usuário se o aplicativo GitHub for propriedade de uma conta individual. Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### Alterar quem pode instalar seu aplicativo GitHub
 
@@ -34,5 +34,5 @@ Para alterar quem pode instalar o aplicativo GitHub:
 {% data reusables.user-settings.github_apps %}
 3. Selecione o aplicativo GitHub cuja opção de instalação você deseja alterar. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. Dependendo da opção de instalação do seu aplicativo GitHub, clique em **Tornar público** ou **Tornar interno**. ![Botão para alterar a opção de instalação do seu aplicativo GitHub](/assets/images/github-apps/github_apps_make_public.png)
-6. Dependendo da opção de instalação do seu aplicativo GitHub, clique em **Sim, tornar este aplicativo GitHub público** ou **Sim, tornar este aplicativo GitHub interno**. ![Botão para confirmar a mudança de sua opção de instalação](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Botão para alterar a opção de instalação do seu aplicativo GitHub](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Botão para confirmar a mudança de sua opção de instalação](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 233266d1dd..e9b580c419 100644
--- a/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -139,7 +139,7 @@ Após criar seu aplicativo, você será levado de volta para a [página de confi
 
 ### Etapa 4. Prepare o ambiente do tempo de execução
 
-Para manter suas informações seguras, recomendamos colocar todos os segredos referentes ao aplicativo na memória do computador onde seu aplicativo poderá encontrá-los, em vez de colocá-los diretamente no seu código. Uma ferramenta útil de desenvolvimento denominada [dotenv](https://github.com/bkeepers/dotenv) carrega variáveis de ambiente específicas do projeto a partir de um arquivo `.env` para `ENV`. Nunca verifique o seu arquivo `.env` no GitHub. Este é um arquivo local que armazena informações confidenciais que você não deseja que estejam na internet pública. The `.env` file is already included in the repository's [`.gitignore`](/github/getting-started-with-github/ignoring-files/) file to prevent that.
+Para manter suas informações seguras, recomendamos colocar todos os segredos referentes ao aplicativo na memória do computador onde seu aplicativo poderá encontrá-los, em vez de colocá-los diretamente no seu código. Uma ferramenta útil de desenvolvimento denominada [dotenv](https://github.com/bkeepers/dotenv) carrega variáveis de ambiente específicas do projeto a partir de um arquivo `.env` para `ENV`. Nunca verifique o seu arquivo `.env` no GitHub. Este é um arquivo local que armazena informações confidenciais que você não deseja que estejam na internet pública. O arquivo `.env` já está incluído no arquivo do repositório [`.gitignore`](/github/getting-started-with-github/ignoring-files/) para evitar isso.
 
 O código do modelo que você baixou na seção [Pré-requisitos](#prerequisites) já tem um exemplo de arquivo denominado `.env-example`. Renomeie o arquivo de exemplo de `.env-example` para `.env` ou crie uma cópia do arquivo `.env-example` denominada `.env`. Você ainda não instalou a dotenv, mas você irá instalá-la mais adiante neste início rápido ao executar o `pacote de instalação`. **Observação:** Os inícios rápidos que fazem referência às etapas neste guia pode incluir variáveis de ambiente adicionais no arquivo `.env-example`. Faça referência ao guia de início rápido para o projeto que você clonou no GitHub para orientação que define essas variáveis de ambiente adicionais.
 
@@ -370,10 +370,10 @@ Após clicar em **Instalar**, veja a saída no seu Terminal. Você deverá ver a
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 Isto é bom! Isso significa que seu aplicativo recebeu uma notificação de que foi instalado na sua conta do GitHub. Se você vir algo assim, seu aplicativo estará em execução no servidor, conforme esperado. 🙌
diff --git a/translations/pt-BR/content/developers/apps/using-content-attachments.md b/translations/pt-BR/content/developers/apps/using-content-attachments.md
index d2dad09b5b..97f86fd3e7 100644
--- a/translations/pt-BR/content/developers/apps/using-content-attachments.md
+++ b/translations/pt-BR/content/developers/apps/using-content-attachments.md
@@ -130,10 +130,9 @@ Para criar um aplicativo Probot, siga as etapas a seguir:
 2. Abra o projeto que você criou e personalize as configurações no arquivo `app.yml`. Assine o evento `content_reference` e habilite as permissões de gravação `content_reference`:
 
    ``` yml
-
     default_events:
-    - content_reference
-    # O conjunto de permissões necessárias para o aplicativo GitHub. O formato do objeto usa
+      - content_reference
+    # The set of permissions needed by the GitHub App. O formato do objeto usa
     # o nome da permissão para a chave (por exemplo, problemas) e o tipo de acesso para
     # o valor (por exemplo, gravação)
     # Valid values are `read`, `write`, and `none`
@@ -141,10 +140,10 @@ Para criar um aplicativo Probot, siga as etapas a seguir:
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. Adicione este código ao arquivo `index.js` para lidar com eventos `content_reference` e chamar a API REST:
diff --git a/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md b/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md
index 2676928128..55e20c7c51 100644
--- a/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md
+++ b/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md
@@ -9,21 +9,21 @@ versions:
 
 ### Para aplicativos GitHub
 
-Certain apps on the {% data variables.product.prodname_marketplace %} have the {% octicon "verified" aria-label="The verified badge" %} badge and a tooltip that says "Publisher domain and email verified". This means that the app is owned by an organization that has:
+Alguns aplicativos em {% data variables.product.prodname_marketplace %} têm o selo {% octicon "verified" aria-label="The verified badge" %} e uma dica que diz "domínio de editor e e-mail verificados". Isso significa que o aplicativo é propriedade de uma organização que tem:
 
-- Verified ownership of their domain and has a verified badge on their profile
+- Propriedade verificada do seu domínio e tem um selo verificado no seu perfil
 - Confirmou o endereço de e-mail da empresa, para que o suporte de {% data variables.product.prodname_dotcom %} possa entrar em contato com a empresa
 - Exigiu a autenticação de dois fatores para sua organização. Para obter mais informações, consulte "[Exigir autenticação de dois fatores em sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)".
 
 ![Selo do Marketplace para Aplicativos GitHub](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png)
 
 {% note %}
-{% data variables.product.prodname_dotcom %} does not analyze the app. The marketplace badge {% octicon "verified" aria-label="The verified badge" %} only confirms that the publisher meets the requirements listed above.
+{% data variables.product.prodname_dotcom %} não analisa o aplicativo. O selo do marketplace {% octicon "verified" aria-label="The verified badge" %} somente confirma que o editor atende aos requisitos listados acima.
 {% endnote %}
 
 Para saber como adicionar esse selo ao seu aplicativo, consulte "[Candidatar-se para a verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
 
-Some apps on the {% data variables.product.prodname_marketplace %} have the {% octicon "verified" aria-label="The verified badge" %} badge and a tooltip that says "App meets the requirements for listing" instead of, "Publisher domain and email verified." This means that the app meets the listing requirements described in "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)," but the publisher has not been verified, as described in "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". Apps with this badge cannot change their pricing plan until the publisher successfully applies for verification.
+Alguns aplicativos em {% data variables.product.prodname_marketplace %} têm o selo {% octicon "verified" aria-label="The verified badge" %} e uma dica que diz "O aplicativo atende aos requisitos para o anúncio" em vez de "Domínio e e-mail de editor verificados". Isso significa que o aplicativo atende aos requisitos de anúncio descritos em "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app), mas o editor não foi verificado, conforme descrito em "[Aplicar a verificação de editor para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". Os aplicativos com este selo não podem alterar seu plano de preços até que o editor solicite a verificação de forma bem-sucedida.
 
 ![Selo do Marketplace para Aplicativos GitHub](/assets/images/marketplace/apps-with-unverified-publisher-badge-tooltip.png)
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index 399df9a68e..611bd0d52d 100644
--- a/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ Para oferecer planos pagos para o seu aplicativo, este deverá pertencer a uma o
 
 ### Solicitar verificação de publicador
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Na barra lateral esquerda, clique em **Developer settings** (Configurações do desenvolvedor). ![Opção de configurações do desenvolvedor na barra lateral de configurações da organização](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Em "Configurações de desenvolvedor", clique em **Verificação do publicador**. ![Opção de verificação do editor na barra lateral de configurações da organização](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. Em "Verificação do Publicador, preencha as informações na lista de verificação:
    - Certifique-se de que as suas informações básicas do perfil estejam presentes e precisas. Além disso, certifique-se de incluir o melhor endereço de e-mail para suporte e atualizações de {% data variables.product.company_short %}.
    - Certifique-se de que a autenticação de dois fatores esteja habilitada para a sua organização. Para obter mais informações, consulte "[Exigir autenticação de dois fatores em sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)".
-   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. Para obter informações relacionadas, consulte "[Verificar o domínio da sua organização](/organizations/managing-organization-settings/verifying-your-organizations-domain)".
+   - Envie um domínio verificado e certifique-se de que um selo "Verificado" seja exibido na página de perfil da sua organização. For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![Lista de verificação do publicador](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md
index ef065fa79c..e99e17d448 100644
--- a/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md
+++ b/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md
@@ -12,7 +12,7 @@ topics:
 
 
 
-Os planos de preços de {% data variables.product.prodname_marketplace %} podem ser grátis, fixos ou por unidade. Os preços são definidos, exibidos e processados em dólares. Paid plans are restricted to apps published by verified publishers. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)."
+Os planos de preços de {% data variables.product.prodname_marketplace %} podem ser grátis, fixos ou por unidade. Os preços são definidos, exibidos e processados em dólares. Os planos pagos são restritos a aplicativos publicados por editores verificados. Para obter mais informações sobre como se tornar um editor verificado, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
 
 Os clientes compram seu aplicativo usando um método de pagamento anexado à sua conta de {% data variables.product.product_name %} sem precisar sair de {% data variables.product.prodname_dotcom_the_website %}. Você não precisa escrever um código para realizar transações de cobrança, mas deverá gerenciar eventos da API de {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md
index a88aff30ca..5756a108ca 100644
--- a/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md
+++ b/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md
@@ -50,7 +50,7 @@ Para proteger seus clientes, recomendamos que siga as práticas recomendadas em
 
 ### Requisitos para aplicativos pagos
 
-Para publicar um plano pago para o seu aplicativo em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá pertencer a uma organização que seja um publicador verificado. For more information about the verification process or transferring ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)."
+Para publicar um plano pago para o seu aplicativo em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá pertencer a uma organização que seja um publicador verificado. Para obter mais informações sobre o processo de verificação ou transferir a propriedade do seu aplicativo, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
 
 Se seu aplicativo já está publicado e você é um editor verificado, você poderá publicar um novo plano pago no editor do plano de preços. Para obter mais informações, consulte "[Configurar planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)".
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md
index 367a048c37..c2077422cf 100644
--- a/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md
+++ b/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md
@@ -29,7 +29,7 @@ Se seu aplicativo já foi publicado com um plano pago e você é um editor verif
 
 ![Botão Publicar este plano](/assets/images/marketplace/publish-this-plan-button.png)
 
-If your app is already published with a paid plan and but you are not a verified publisher, then you can cannot publish a new paid plan until you are a verified publisher. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)."
+Se seu aplicativo já foi publicado com um plano pago, mas você não é um editor verificado, você não poderá publicar um novo plano pago até que um editor seja verificado. Para obter mais informações sobre como se tornar um editor verificado, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
 
 ### Sobre como salvar planos de preços
 
@@ -82,4 +82,4 @@ Você pode desativar os testes grátis do GitHub Marketplace sem remover o plano
 
 Depois de remover um plano de preços, você poderá criar um novo plano com o mesmo nome do plano de preços removido. Por exemplo, se você tem um plano de preços "Pro", mas precisa alterar o preço fixo, você poderá remover o plano de preços "Pro" e criar um novo plano de preços "Pro" com um preço atualizado. Os usuários poderão comprar o novo plano de preços imediatamente.
 
-If you are not a verified publisher, then you cannot change a pricing plan for your app. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)."
+Se você não for um editor verificado, você não poderá alterar um plano de preços para o seu aplicativo. Para obter mais informações sobre como se tornar um editor verificado, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
diff --git a/translations/pt-BR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index cf1deaab7f..b4df4ba2a4 100644
--- a/translations/pt-BR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/pt-BR/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ Aqui estão as diretrizes sobre os campos que você precisará preencher na seç
 
 #### Nome da listagem
 
-O nome de seu aplicativo aparecerá [na página inicial do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). O nome tem o limite de 255 caracteres.
+O nome do seu anúncio irá aparecer na [página inicial de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). O nome é limitado a 255 caracteres e pode ser diferente do nome do seu aplicativo. O seu anúncio não pode ter o mesmo nome de um usuário existente de {% data variables.product.product_name %}, a menos que o nome seja seu próprio nome de usuário ou organização.
 
 #### Descrição muito curta
 
diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
index 998db7c767..1ee9b98140 100644
--- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
+++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
@@ -124,41 +124,41 @@ $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% el
 
 
 
-### Server-to-server tokens
+### Tokens do servidor para servidor
 
-If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. 
+Se seu servidor precisar acessar repositórios em uma ou mais organizações, você poderá usar um aplicativo GitHub para definir o acesso que você precisa e, em seguida, gerar tokens de _escopo limitado_, _servidor para servidor_ a partir daquele aplicativo GitHub. Os tokens do servidor para servidor podem ter escopo de repositório único ou múltiplo e podem ter permissões refinadas. Por exemplo, você pode gerar um token com acesso somente leitura para o conteúdo de um repositório. 
 
-Since GitHub Apps are a first class actor on  {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps).
+Uma vez que os aplicativos GitHub são um ator de primeira classe em  {% data variables.product.product_name %}, os tokens do servidor para servidor são dissociados de qualquer usuário do GitHub, o que os torna comparáveis aos "tokens de serviço". Além disso, tokens de servidor para servidor têm limites de taxa dedicados que escalam com o tamanho das organizações sobre as quais eles atuam. Para obter mais informações, consulte [Limites de taxa para os aplicativos Github](/developers/apps/rate-limits-for-github-apps).
 
 
 
 ##### Prós
 
-- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API).
-- Dedicated rate limits that grow with your organization.
-- Decoupled from GitHub user identities, so they do not consume any licensed seats.
-- Never granted a password, so cannot be directly signed in to.
+- Tokens com escopo limitado com conjuntos de permissões bem definidos e tempos de expiração (1 hora, ou menos se for revogado manualmente usando a API).
+- Limites de taxa dedicados que crescem com a sua organização.
+- Separados das identidades de usuários do GitHub para que não consumam nenhuma estação licenciada.
+- Nunca concedeu uma senha. Portanto, não pode efetuar o login diretamente.
 
 
 
 ##### Contras
 
-- Additional setup is needed to create the GitHub App.
-- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code.
+- É necessária uma configuração adicional para criar o aplicativo GitHub.
+- Os tokens de servidor para servidor expiram após 1 hora. Portanto, precisam ser gerados novamente, geralmente sob demanda e usando código.
 
 
 
 ##### Configuração
 
-1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private.
-1. Determine the permissions your GitHub App requires, such as read-only access to repository contents.
-1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app).
-1. Note your GitHub App `id`.
-1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
-1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization.
-1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access.  Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
-1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
-1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client.
+1. Determine se seu aplicativo GitHub deve ser público ou privado. Se o seu aplicativo GitHub agir apenas nos repositórios da organização, é provável que você queira que ele seja privado.
+1. Determine as permissões que o aplicativo GitHub exige, como acesso somente leitura ao conteúdo do repositório.
+1. Crie seu aplicativo GitHub por meio da página de configurações da sua organização. Para obter mais informações, consulte [Criar um aplicativo GitHub](/developers/apps/creating-a-github-app).
+1. Observe seu id `id` do aplicativo GitHub.
+1. Gere e faça o download da chave privada do seu aplicativo GitHub e armazene-a com segurança. Para obter mais informações, consulte [Gerar uma chave privada](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
+1. Instale o aplicativo GitHub nos repositórios nos quais ele precisa agir. Opcionalmente você poderá instalar o aplicativo GitHub em todos os repositórios da sua organização.
+1. Identifique o `installation_id` que representa a conexão entre o aplicativo GitHub e os repositórios da organização à qual ele pode acessar.  Cada aplicativo GitHub e par de organização tem, no máximo, um `installation_id` único. Você pode identificar este `installation_id` por meio de [Obter uma instalação da organização para o aplicativo autenticado](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). Isto exige autenticação como um aplicativo GitHub usando um JWT. Para obter mais informações, consulte [Efetuar a autenticação como um aplicativo GitHub](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
+1. Gere um token de servidor para servidor usando o ponto de extremidade correspondente da API REST, [Crie um token de acesso de instalação para um aplicativo](/rest/reference/apps#create-an-installation-access-token-for-an-app). Isto exige autenticação como um aplicativo GitHub usando um JWT. Para obter mais informações, consulte [Efetuar a autenticação como um aplicativo GitHub](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app) e [Efetuar a autenticação como uma instalação](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
+1. Use este token de servidor para servidor para interagir com seus repositórios, seja por meio das APIs REST ou GraphQL, ou por meio de um cliente Git.
 
 
 
diff --git a/translations/pt-BR/content/developers/overview/secret-scanning.md b/translations/pt-BR/content/developers/overview/secret-scanning.md
index 3735187f9e..945f672b98 100644
--- a/translations/pt-BR/content/developers/overview/secret-scanning.md
+++ b/translations/pt-BR/content/developers/overview/secret-scanning.md
@@ -15,9 +15,9 @@ O {% data variables.product.prodname_dotcom %} faz a varredura de repositórios
 
 Quando uma correspondência do seu formato secreto é encontrada em um repositório público, uma carga é enviada para um ponto de extremidade HTTP de sua escolha.
 
-Quando uma correspondência do formato do segredo é encontrada em um repositório privado configurado para {% data variables.product.prodname_secret_scanning %}, os administradores do repositório são alertados e podem visualizar e gerenciar os resultados {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
+When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
 
-Este artigo descreve como fazer parceria com {% data variables.product.prodname_dotcom %} como um provedor de serviço e participa do programa de {% data variables.product.prodname_secret_scanning %}.
+This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program.
 
 ### O processo de {% data variables.product.prodname_secret_scanning %}
 
@@ -54,26 +54,20 @@ Envie esta informação para <a href="mailto:secret-scanning@github.com">secret-
 
 #### Crie um serviço de alerta secreto
 
-Crie um ponto de extremidade HTTP público e acessível à internet na URL que você nos forneceu. Quando uma correspondência de sua expressão regular é encontrada em um repositório público, o {% data variables.product.prodname_dotcom %} enviará uma mensagem HTTP de `POST` para o seu ponto de extremidade.
+Crie um ponto de extremidade HTTP público e acessível à internet na URL que você nos forneceu. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint.
 
 ##### Exemplo de POST enviado para seu ponto de extremidade
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 O corpo da mensagem é um array do JSON que contém um ou mais objetos com o seguinte conteúdo. Quando várias correspondências forem encontradas, o {% data variables.product.prodname_dotcom %} pode enviar uma única mensagem com mais de uma correspondência secreta. Seu ponto de extremidade deve ser capaz de lidar com solicitações com um grande número de correspondências sem exceder o tempo.
@@ -88,19 +82,31 @@ O corpo da mensagem é um array do JSON que contém um ou mais objetos com o seg
 
 Você pode recuperar a chave pública de da varredura secreta do segredo do {% data variables.product.prodname_dotcom %} em https://api.github.com/meta/public_keys/secret_scanning e validar a mensagem usando o algoritmo `ECDSA-NIST-P256V1-SHA256`.
 
-Supondo que você receba a mensagem a seguir, os trechos de código abaixo demonstram como você poderia efetuar a validação da assinatura. O código também assume que você definiu uma variável de ambiente denominada `GITHUB_PRODUCTION_TOKEN` com um PAT gerado (https://github.com/settings/tokens). O token não precisa de nenhuma permissão definida.
+{% note %}
+
+**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
+
+{% endnote %}
+
+Supondo que você receba a mensagem a seguir, os trechos de código abaixo demonstram como você poderia efetuar a validação da assinatura. The code snippets assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens) to avoid hitting rate limits. The PAT does not need any scopes/permissions.
+
+{% note %}
+
+**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
+
+{% endnote %}
 
 **Mensagem de exemplo enviada para verificar o ponto de extremidade**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Exemplo de validação em Go**
@@ -123,73 +129,73 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
   // Fetch the list of GitHub Public Keys
-  req, err := http. NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
-    fmt. Printf("Error preparing request: %s\n", err)
-    os. Exit(1)
+    fmt.Printf("Error preparing request: %s\n", err)
+    os.Exit(1)
   }
 
-  if len(os. Getenv("GITHUB_PRODUCTION_TOKEN")) == 0 {
-    fmt. Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN")
-    os. Exit(1)
+  if len(os.Getenv("GITHUB_PRODUCTION_TOKEN")) == 0 {
+    fmt.Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN")
+    os.Exit(1)
   }
 
-  req. Header. Add("Authorization", "Bearer "+os. Getenv("GITHUB_PRODUCTION_TOKEN"))
+  req.Header.Add("Authorization", "Bearer "+os.Getenv("GITHUB_PRODUCTION_TOKEN"))
 
-  resp, err := http. DefaultClient. Do(req)
+  resp, err := http.DefaultClient.Do(req)
   if err != nil {
-    fmt. Printf("Error requesting GitHub signing keys: %s\n", err)
-    os. Exit(2)
+    fmt.Printf("Error requesting GitHub signing keys: %s\n", err)
+    os.Exit(2)
   }
 
-  decoder := json. NewDecoder(resp. Body)
+  decoder := json.NewDecoder(resp.Body)
   var keys GitHubSigningKeys
-  if err := decoder. Decode(&keys); err != nil {
-    fmt. Printf("Error decoding GitHub signing key request: %s\n", err)
-    os. Exit(3)
+  if err := decoder.Decode(&keys); err != nil {
+    fmt.Printf("Error decoding GitHub signing key request: %s\n", err)
+    os.Exit(3)
   }
 
   // Find the Key used to sign our webhook
   pubKey, err := func() (string, error) {
-    for _, v := range keys. PublicKeys {
+    for _, v := range keys.PublicKeys {
       if v.KeyIdentifier == kID {
         return v.Key, nil
 
       }
     }
-    return "", errors. New("specified key was not found in GitHub key list")
+    return "", errors.New("specified key was not found in GitHub key list")
   }()
 
   if err != nil {
-    fmt. Printf("Error finding GitHub signing key: %s\n", err)
-    os. Exit(4)
+    fmt.Printf("Error finding GitHub signing key: %s\n", err)
+    os.Exit(4)
   }
 
   // Decode the Public Key
   block, _ := pem.Decode([]byte(pubKey))
   if block == nil {
-    fmt. Println("Error parsing PEM block with GitHub public key")
-    os. Exit(5)
+    fmt.Println("Error parsing PEM block with GitHub public key")
+    os.Exit(5)
   }
 
   // Create our ECDSA Public Key
-  key, err := x509. ParsePKIXPublicKey(block. Bytes)
+  key, err := x509.ParsePKIXPublicKey(block.Bytes)
   if err != nil {
-    fmt. Printf("Error parsing DER encoded public key: %s\n", err)
-    os. Exit(6)
+    fmt.Printf("Error parsing DER encoded public key: %s\n", err)
+    os.Exit(6)
   }
 
-  // Because of documentation, we know it's a *ecdsa. PublicKey
-  ecdsaKey, ok := key.(*ecdsa. PublicKey)
+  // Because of documentation, we know it's a *ecdsa.PublicKey
+  ecdsaKey, ok := key.(*ecdsa.PublicKey)
   if !ok {
-    fmt.
+    fmt.Println("GitHub key was not ECDSA, what are they doing?!")
     Exit(7)
   }
 
@@ -241,16 +247,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -356,4 +362,3 @@ Alguns pontos importantes:
 **Nota:** Nosso tempo limite de solicitação está definido para ser maior (isto é, 30 segundos) para parceiros que fornecem dados sobre falsos positivos. Se você precisar de um tempo limite superior a 30 segundos, envie um e-mail para <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
 {% endnote %}
-
diff --git a/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md b/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md
index 29e814041f..a7c23d6ceb 100644
--- a/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-No Mac OS X `ssh-agent` irá "esquecer" essa chave, assim que for reiniciado. No entanto, você poderá importar suas chaves SSH para o Keychain usando este comando:
+On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. No entanto, você poderá importar suas chaves SSH para o Keychain usando este comando:
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md
index 3ae5749d56..a9d05a5d7b 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md
@@ -1,6 +1,6 @@
 ---
-title: About webhooks
-intro: Learn the basics of how webhooks work to help you build and set up integrations.
+title: Sobre webhooks
+intro: Aprenda os princípios básicos de como os webhooks funcionam para ajudá-lo a criar e configurar integrações.
 redirect_from:
   - /webhooks
 versions:
@@ -12,25 +12,25 @@ topics:
 ---
 
 
-Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination.
+Os webhooks permitem que você crie ou configure integrações, como [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) ou [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), que assinam determinados eventos no GitHub.com. Quando um desses eventos é acionado, enviaremos uma carga de POST por HTTP POST para a URL de configuração do webhook. Os webhooks podem ser usados para atualizar um rastreador de problemas externo, acionar criações de CI, atualizar um espelho de backup, ou até mesmo fazer uma implantação no seu servidor de produção. A sua imaginação é o único limite.
 
-Webhooks can be installed on{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} an [organization][org-hooks], a specific [repository][repo-hooks], or a {% data variables.product.prodname_github_app %}. Once installed, the webhook will be sent each time one or more subscribed events occurs.
+Os webhooks podem ser instalados em{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} uma [organização][org-hooks], em um repositório[específico][repo-hooks] ou em {% data variables.product.prodname_github_app %}. Uma vez instalado, o webhook será enviado cada vez que ocorrer um ou mais eventos assinados.
 
-You can create up to {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} webhooks for each event on each installation target {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}({% data variables.product.prodname_ghe_server %} instance, specific organization, or specific repository).{% else %}(specific organization or specific repository).{% endif %}
+Você pode criar até {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} webhooks para cada evento em cada destino de instalação {% if enterpriseServerVersions contains currentVersion or currentVersion or currentVersion == "github-ae@latest" %}(instância de {% data variables.product.prodname_ghe_server %}, organização específica ou repositório específico).{% else %}(organização específica ou repositório específico).{% endif %}
 
-### Events
+### Eventos
 
 {% data reusables.webhooks.webhooks_intro %}
 
-Each event corresponds to a certain set of actions that can happen to your organization and/or repository. For example, if you subscribe to the `issues` event you'll receive detailed payloads every time an issue is opened, closed, labeled, etc.
+Cada evento corresponde a um certo conjunto de ações que podem ocorrer na sua organização e/ou repositório. Por exemplo, se você assinar o evento `problemas`, você receberá cargas detalhadas toda vez que uma tarefa for aberta, fechada, etiquetada, etc.
 
-See "[Webhook event payloads](/webhooks/event-payloads)" for the list of available webhook events and their payloads.
+Para obter uma lista completa de eventos de webhook disponíveis e suas cargas, consulte "[Eventos e cargas de webhook](/developers/webhooks-and-events/webhook-events-and-payloads)".
 
-### Ping event
+### Evento de ping
 
 {% data reusables.webhooks.ping_short_desc %}
 
-For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event.
+Para obter mais informações sobre a carga do webhook do evento de `ping`, consulte o evento [`ping`](/webhooks/event-payloads/#ping).
 
 [org-hooks]: /rest/reference/orgs#webhooks/
 [repo-hooks]: /rest/reference/repos#hooks
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md
index a355a0ae1b..59baf02f6a 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md
@@ -17,13 +17,13 @@ Agora que nosso webhook está pronto para enviar mensagens, vamos configurar um
 
 {% note %}
 
-**Note:** You can download the complete source code for this project [from the platform-samples repo][platform samples].
+**Observação:** Você pode fazer o download do código-fonte completo para este projeto [no repositório de amostras de plataforma][platform samples].
 
 {% endnote %}
 
 ### Escrevendo o servidor
 
-Queremos que nosso servidor escute as solicitações de `POST`, em `/payload`, porque foi onde informamos ao GitHub que era a nossa URL. Because we're using ngrok to expose our local environment, we don't need to set up a real server somewhere online, and can happily test out our code locally.
+Queremos que nosso servidor escute as solicitações de `POST`, em `/payload`, porque foi onde informamos ao GitHub que era a nossa URL. Uma vez que estamos usando ngrok para expor o nosso ambiente local, não precisamos configurar um servidor real on-line, e é possível testar tranquilamente o nosso código localmente.
 
 Vamos configurar um pouco o aplicativo Sinatra para fazer algo com as informações. Nossa configuração inicial do a configuração pode parecer como isso:
 
@@ -41,7 +41,7 @@ end
 
 Inicie este servidor.
 
-Since we set up our webhook to listen to events dealing with `Issues`, go ahead and create a new issue on the repository you're testing with. Depois de criar, volte para o terminal. Você deve ver algo assim em sua saída:
+Desde que configuramos nosso webhook para ouvir eventos que gerenciam `Problemas`, siga em frente e crie uma novo problema no repositório que você está testando. Depois de criar, volte para o terminal. Você deve ver algo assim em sua saída:
 
 ```shell
 $ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server.rb
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md
index e3db174ea1..b59dec7277 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/creating-webhooks.md
@@ -13,26 +13,26 @@ topics:
 
 
 
-Now that we understand [the basics of webhooks][webhooks-overview], let's go through the process of building out our own webhook-powered integration. In this tutorial, we'll create a repository webhook that will be responsible for listing out how popular our repository is, based on the number of issues it receives per day.
+Agora que entendemos [os conceitos básicos de webhooks][webhooks-overview], vamos analisar o processo de criação da nossa própria integração com o webhook. Neste tutorial, vamos criar um webhook de repositório que será responsável por listar quão popular é o nosso repositório, com base no número de problemas que recebe por dia.
 
-Criar um webhook é um processo de duas etapas. You'll first need to set up how you want your webhook to behave through {% data variables.product.product_name %}: what events should it listen to. Em seguida, você irá configurar seu servidor para receber e gerenciar a carga.
+Criar um webhook é um processo de duas etapas. Primeiro, você deverá configurar como deseja que seu webhook se comporte através do {% data variables.product.product_name %}: quais eventos devem ser ouvidos. Em seguida, você irá configurar seu servidor para receber e gerenciar a carga.
 
 
 {% data reusables.webhooks.webhooks-rest-api-links %}
 
-### Exposing localhost to the internet
+### Expor o host local na internet
 
-For the purposes of this tutorial, we're going to use a local server to receive messages from {% data variables.product.prodname_dotcom %}. So, first of all, we need to expose our local development environment to the internet. We'll use ngrok to do this. ngrok is available, free of charge, for all major operating systems. For more information, see [the ngrok download page](https://ngrok.com/download).
+Para fins deste tutorial, vamos usar um servidor local para receber mensagens de {% data variables.product.prodname_dotcom %}. Portanto, em primeiro lugar, temos de expor o nosso ambiente de desenvolvimento local à internet. Nós usaremos ngrok para fazer isso. Ngrok está disponível, gratuitamente, para todos os principais sistemas operacionais. Para obter mais informações, consulte [a página de download do ngrok](https://ngrok.com/download).
 
-After installing ngrok, you can expose your localhost by running `./ngrok http 4567` on the command line. 4567 is the port number on which our server will listen for messages. Você deve ver uma linha parecida mais ou menos com isso:
+Depois de instalar o ngrok, você poderá expor seu host local executando `./ngrok http 4567` na linha de comando. 4567 é o número da porta em que o nosso servidor ouvirá mensagens. Você deve ver uma linha parecida mais ou menos com isso:
 
 ```shell
 $ Forwarding    http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
 ```
 
-Make a note of the `*.ngrok.io` URL. We'll use it to set up our webhook.
+Faça uma anotação da URL `*.ngrok.io.`. Vamos usá-lo para configurar nosso webhook.
 
-### Setting up a webhook
+### Configurar um webhook
 
 É possível instalar webhooks em uma organização ou em um repositório específico.
 
@@ -46,7 +46,7 @@ Os webhooks exigem algumas opções de configuração antes de você poder usá-
 
 {% data reusables.webhooks.payload_url %}
 
-Since we're developing locally for our tutorial, we'll set it to the `*.ngrok.io` URL, followed by `/payload`. For example, `http://7e9ea9dc.ngrok.io/payload`.
+Já que estamos estamos fazendo um desenvolvimento local para o nosso tutorial, vamos configurá-lo para a URL `*.ngrok.io`, seguida de `/payload`. Por exemplo, `http://7e9ea9dc.ngrok.io/payload`.
 
 ### Tipo de conteúdo
 
@@ -56,7 +56,7 @@ Since we're developing locally for our tutorial, we'll set it to the `*.ngrok.io
 
 {% data reusables.webhooks.secret %}
 
-### SSL verification
+### Verificação SSL
 
 {% data reusables.webhooks.webhooks_ssl %}
 
@@ -70,13 +70,13 @@ Os eventos encontram-se no núcleo dos webhooks. Esses webhooks são acionados s
 
 Uma lista completa de eventos de webhook e quando são executados pode ser encontrada na referência [da API de webhooks][hooks-api].
 
-Since our webhook is dealing with issues in a repository, we'll click **Let me select individual events** and then **Issues**. Certifique-se de selecionar **Ativo** para receber eventos de problemas para webhooks acionados. Você também pode selecionar todos os eventos usando a opção-padrão.
+Como nosso webhook está lidando com problemas em um repositório, clicaremos em **Deixe-me selecionar eventos individuais** e, em seguida, **problemas**. Certifique-se de selecionar **Ativo** para receber eventos de problemas para webhooks acionados. Você também pode selecionar todos os eventos usando a opção-padrão.
 
 Ao terminar, clique em **Adicionar webhook**.
 
-Now that you've created the webhook, it's time to set up our local server to test the webhook. Vá até [Configurar seu servidor](/webhooks/configuring/) para aprender como fazê-lo.
+Agora que você criou o webhook, é hora de configurar nosso servidor local para testar o webhook. Vá até [Configurar seu servidor](/webhooks/configuring/) para aprender como fazê-lo.
 
-#### Wildcard event
+#### Evento curinga
 
 Para configurar um webhook para todos os eventos, use o caractere curinga (`*`) para especificar os eventos de webhook. Ao adicionar o evento curinga, substituiremos todos os eventos existentes que você tenha configurado pelo evento curinga e enviaremos todas as cargas para os eventos compatíveis. Você também obterá automaticamente todos os novos eventos que possamos adicionar no futuro.
 
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md
index fb4cb975d4..46be029fbc 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ Os objetos de evento retornados dos pontos de extremidade da API de eventos têm
 Este exemplo mostra o formato da resposta do [WatchEvent](#watchevent) ao usar a [API de eventos](/rest/reference/activity#events).
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
@@ -194,7 +194,7 @@ Este evento retorna um objeto de `carga` vazio.
 | Tecla          | Tipo     | Descrição                                    |
 | -------------- | -------- | -------------------------------------------- |
 | `Ação`         | `string` | A ação que foi executada. Pode ser `criado`. |
-| `pull_request` | `objeto` | The pull request the review pertains to.     |
+| `pull_request` | `objeto` | O pull request ao qual a revisão pertence.   |
 | `revisar`      | `objeto` | A revisão que foi afetada.                   |
 
 ### PullRequestReviewCommentEvent
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md
index c1f7d1a693..9b63becc46 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your webhooks
-intro: 'Ensure your server is only receiving the expected {% data variables.product.prodname_dotcom %} requests for security reasons.'
+title: Protegendo seus webhooks
+intro: 'Certifique-se de que seu servidor só esteja recebendo as solicitações esperadas do {% data variables.product.prodname_dotcom %} por motivos de segurança.'
 redirect_from:
   - /webhooks/securing
 versions:
@@ -13,42 +13,41 @@ topics:
 
 
 
-Once your server is configured to receive payloads, it'll listen for any payload sent to the endpoint you configured. For security reasons, you probably want to limit requests to those coming from GitHub. There are a few ways to go about this--for example, you could opt to allow requests from GitHub's IP address--but a far easier method is to set up a secret token and validate the information.
+Assim que seu servidor estiver configurado para receber cargas, ele ouvirá qualquer carga enviada para o ponto de extremidade que você configurou. Por motivos de segurança, você provavelmente vai querer limitar os pedidos para aqueles provenientes do GitHub. Existem algumas maneiras de fazer isso. Você poderia, por exemplo, optar por permitir solicitações do endereço IP do GitHub. No entanto, um método muito mais fácil é configurar um token secreto e validar a informação.
 
 {% data reusables.webhooks.webhooks-rest-api-links %}
 
-### Setting your secret token
+### Definir seu token secreto
 
-You'll need to set up your secret token in two places: GitHub and your server.
+Você precisará configurar seu token secreto em dois lugares: no GitHub e no seu servidor.
 
-To set your token on GitHub:
+Para definir seu token no GitHub:
 
-1. Navigate to the repository where you're setting up your webhook.
-2. Fill out the Secret textbox. Use a random string with high entropy (e.g., by taking the output of `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` at the terminal).
-![Webhook secret token field](/assets/images/webhook_secret_token.png)
-3. Click **Update Webhook**.
+1. Navegue até o repositório onde você está configurando seu webhook.
+2. Preencha a caixa de texto do segredo. Use uma string aleatória com alta entropia (por exemplo, pegando a saída de `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` no terminal). ![Campo de webhook e token secreto](/assets/images/webhook_secret_token.png)
+3. Clique em **Atualizar o webhook**.
 
-Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running:
+Em seguida, configure uma variável de ambiente em seu servidor que armazene este token. Normalmente, isso é tão simples quanto executar:
 
 ```shell
 $ export SECRET_TOKEN=<em>your_token</em>
 ```
 
-**Never** hardcode the token into your app!
+**Nunca** pré-programe o token no seu aplicativo!
 
-### Validating payloads from GitHub
+### Validar cargas do GitHub
 
-When your secret token is set, {% data variables.product.product_name %} uses it to create a hash signature with each payload. This hash signature is included with the headers of each request as {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`{% endif %}.
+Quando seu token secreto está definido, {% data variables.product.product_name %} o utiliza para criar uma assinatura de hash com cada carga. Esta assinatura hash está incluída com os cabeçalhos de cada solicitação como {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" ou currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`{% endif %}.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 {% note %}
 
-**Note:** For backward-compatibility, we also include the `X-Hub-Signature` header that is generated using the SHA-1 hash function. If possible, we recommend that you use the `X-Hub-Signature-256` header for improved security. The example below demonstrate using the `X-Hub-Signature-256` header.
+**Observação:** Para compatibilidade com versões anteriores, também incluímos o cabeçalho `X-Hub-Signature` gerado usando a função de hash SHA-1. Se possível, recomendamos que você use o cabeçalho `X-Hub-Signature-256` para melhorar a segurança. O exemplo abaixo demonstra o uso do cabeçalho `X-Hub-Signature-256`.
 
 {% endnote %}
 {% endif %}
 
-For example, if you have a basic server that listens for webhooks, it might be configured similar to this:
+Por exemplo, se você tem um servidor básico que ouve webhooks, ele poderá ser configurado de forma semelhante a isso:
 
 ``` ruby
 require 'sinatra'
@@ -60,7 +59,7 @@ post '/payload' do
 end
 ```
 
-The intention is to calculate a hash using your `SECRET_TOKEN`, and ensure that the result matches the hash from {% data variables.product.product_name %}. {% data variables.product.product_name %} uses an HMAC hex digest to compute the hash, so you could reconfigure your server to look a little like this:
+O objetivo é calcular um hash usando seu `SECRET_TOKEN` e garantir que o resultado corresponda ao hash de {% data variables.product.product_name %}. {% data variables.product.product_name %} usa um resumo hexadecimal HMAC para calcular o hash. Portanto, você pode reconfigurar o seu servidor para que se pareça mais ou menos assim:
 
 ``` ruby
 post '/payload' do
@@ -82,10 +81,16 @@ def verify_signature(payload_body)
 end{% endif %}
 ```
 
-Your language and server implementations may differ from this example code. However, there are a number of very important things to point out:
+{% note %}
 
-* No matter which implementation you use, the hash signature starts with {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`sha1=`{% endif %}, using the key of your secret token and your payload body.
+**Observação:** As cargas de webhook podem conter caracteres de unicode. Se o seu idioma e a implementação de servidor especificarem uma codificação de caracteres, certifique-se de que você manipula a carga como UTF-8.
 
-* Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators.
+{% endnote %}
 
-[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare
+A sua linguagem e implementações do servidor podem ser diferentes deste código de exemplo. No entanto, há uma série de aspectos muito importantes a destacar:
+
+* Não importa qual implementação você usar, a assinatura hash começa com {% if currentVersion == "free-pro-team@latest" ou currentVersion ver_gt "enterprise-server@2. 2" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2. 3" %}`sha1=`{% endif %}, usando a chave do seu token secreto e o seu texto de carga.
+
+* Não **se recomenda** usar um operador simples de`==`. Um método como [`secure_compare`][secure_compare] executa uma comparação de strings "tempo constante", o que ajuda a mitigar certos ataques de tempo contra operadores de igualdade regular.
+
+[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index b055ba6345..9a7f277d8b 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -1,6 +1,6 @@
 ---
-title: Webhook events and payloads
-intro: 'For each webhook event, you can review when the event occurs, an example payload, and descriptions about the payload object parameters.'
+title: Eventos de webhook e cargas
+intro: 'Para cada evento de webhook, você pode revisar quando o evento ocorrer, uma carga de exemplo, bem como as descrições sobre os parâmetros do objeto da carga.'
 product: '{% data reusables.gated-features.enterprise_account_webhooks %}'
 redirect_from:
   - /early-access/integrations/webhooks/
@@ -21,47 +21,47 @@ topics:
 
 {% data reusables.webhooks.webhooks_intro %}
 
-You can create webhooks that subscribe to the events listed on this page. Each webhook event includes a description of the webhook properties and an example payload. For more information, see "[Creating webhooks](/webhooks/creating/)."
+Você pode criar webhooks que assinam os eventos listados nesta página. Cada evento de webhook inclui uma descrição das propriedades do webhook e uma carga de exemplo. Para obter mais informações, consulte "[Criar webhooks](/webhooks/creating/)."
 
-### Webhook payload object common properties
+### Propriedades comuns do objeto da carga do webhook
 
-Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections.
+Cada carga do evento do webhook também contém propriedades únicas para o evento. Você pode encontrar as propriedades únicas nas seções individuais de tipos de evento.
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event.
-{% data reusables.webhooks.sender_desc %} This property is included in every webhook payload.
-{% data reusables.webhooks.repo_desc %} Webhook payloads contain the `repository` property when the event occurs from activity in a repository.
+| Tecla  | Tipo     | Descrição                                                                                                              |
+| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- |
+| `Ação` | `string` | A maioria das cargas de webhook contém uma ação `` propriedade que contém a atividade específica que acionou o evento. |
+{% data reusables.webhooks.sender_desc %} Esta propriedade está incluída em todas as cargas do webhook.
+{% data reusables.webhooks.repo_desc %} As cargas do webhook contêm a propriedade `repository` quando ocorre o evento a partir da atividade em um repositório.
 {% data reusables.webhooks.org_desc %}
-{% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)."
+{% data reusables.webhooks.app_desc %} Para obter mais informações, consulte "[Criar um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/).
 
-The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information.
+As propriedades únicas para um evento de webhook são as mesmas propriedades que você encontrará na propriedade `payload` ao usar a [Eventos API](/rest/reference/activity#events). Uma exceção é o evento de [`push`](#push). As propriedades únicas da carga do webhook do evento `push` e a propriedade `carga` na API de eventos são diferentes. A carga do webhook contém informações mais detalhadas.
 
 {% tip %}
 
-**Note:** Payloads are capped at 25 MB. If your event generates a larger payload, a webhook will not be fired. This may happen, for example, on a `create` event if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery.
+**Observação:** As cargas são limitados a 25 MB. Se o seu evento gerar uma carga maior, um webhook não será disparado. Isso pode acontecer, por exemplo, em um evento `criar`, caso muitos branches ou tags sejam carregados de uma só vez. Sugerimos monitorar o tamanho da sua carga para garantir a entrega.
 
 {% endtip %}
 
-#### Delivery headers
+#### Cabeçalhos de entrega
 
-HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers:
+As cargas de HTTP POST que são entregues no ponto de extremidade da URL configurado do seu webhook conterão vários cabeçalhos especiais:
 
-Header | Description
--------|-------------|
-`X-GitHub-Event`| Name of the event that triggered the delivery.
-`X-GitHub-Delivery`| A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
-`X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.
-`X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %}
-`X-Hub-Signature`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-`X-Hub-Signature-256`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %}
+| Header                        | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `X-GitHub-Event`              | Nome do evento que ativou a entrega.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `X-GitHub-Delivery`           | Um [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) para identificar a entrega.{% if enterpriseServerVersions contém currentVersion or currentVersion == "github-ae@latest" %}
+| `X-GitHub-Enterprise-Version` | A versão da instância do {% data variables.product.prodname_ghe_server %} que enviou a carga do HTTP POST.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `X-GitHub-Enterprise-Host`    | O nome do host da instância de {% data variables.product.prodname_ghe_server %} que enviou a carga HTTP POST.{% endif %}{% if currentVersion != "github-ae@latest" %}
+| `X-Hub-Signature`             | Este cabeçalho é enviado se o webhook for configurado com um [`secret`](/rest/reference/repos#create-hook-config-params). Este é o resumo hexadecimal de HMAC do texto da solicitação e é gerado usando a função hash SHA-1 e `segredo` como a `chave` de HMAC.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` é fornecido para compatibilidade com integrações existentes, e recomendamos que você use um `X-Hub-Signature-256` mais seguro.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| `X-Hub-Signature-256`         | Este cabeçalho é enviado se o webhook for configurado com um [`secret`](/rest/reference/repos#create-hook-config-params). Este é o resumo hexadecimal HMAC do texto da solicitação e é gerado usando a função hash SHA-256 e a `segredo` como a `chave` HMAC.{% endif %}
 
-Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
+Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hookshot/`.
 
-#### Example delivery
+#### Exemplo de entrega
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -105,13 +105,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks only receive payloads for the `created` and `completed` event types in a repository
-- Organization webhooks only receive payloads for the `created` and `completed` event types in repositories
-- {% data variables.product.prodname_github_app %}s with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_app %}s with the `checks:write` are automatically subscribed to this webhook event.
+- Os webhooks de repositório só recebem cargas para os tipos de evento `criados` e `concluídos` em um repositório
+- Os webhooks da organização só recebem cargas para os tipos de eventos `criados` e `concluídos` nos repositórios
+- Os {% data variables.product.prodname_github_app %}s com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `requested_action`. As cargas do tipo de evento `solicitadas` e `requested_action` são enviadas apenas para o {% data variables.product.prodname_github_app %} que está sendo solicitado. Os {% data variables.product.prodname_github_app %}s com `checks:write` são automaticamente inscritos neste evento webhook.
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.check_run_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -119,7 +119,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.check_run.created }}
 
@@ -129,13 +129,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks only receive payloads for the `completed` event types in a repository
-- Organization webhooks only receive payloads for the `completed` event types in repositories
-- {% data variables.product.prodname_github_app %}s with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_app %}s with the `checks:write` are automatically subscribed to this webhook event.
+- Os webhooks de repositório só recebem cargas para os tipos de evento `concluídos` em um repositório
+- Os webhooks da organização só recebem cargas para os tipos de eventos `concluídos` nos repositórios
+- Os {% data variables.product.prodname_github_app %}s com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `ressolicitados.`. As cargas de evento `solicitadas` e `ressolicitadas` são enviadas apenas para {% data variables.product.prodname_github_app %} que está sendo solicitado. Os {% data variables.product.prodname_github_app %}s com `checks:write` são automaticamente inscritos neste evento webhook.
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.check_suite_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -143,30 +143,31 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.check_suite.completed }}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 ### code_scanning_alert
 
-{% data reusables.webhooks.code_scanning_alert_event_short_desc %}
+Os {% data variables.product.prodname_github_app %}s com a permissão `security_events`
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `security_events :read` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de `conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.code_scanning_alert_event_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
-`sender` | `object` | If the `action` is `reopened_by_user` or `closed_by_user`, the `sender` object will be the user that triggered the event. The `sender` object is empty for all other actions.
+</code>remetente`| <code>objeto` | Se a </code> de ação ` for <code>reopened_by_user` ou `closed_by_user`, o objeto `remetente` será o usuário que ativou o evento. O objeto `remetente` é
+{% if currentVersion == "free-pro-team@latest" %}`github` {% elsif currentVersion ver_gt "enterprise-server@3.0" %}`github-enterprise` {% else %}empty {% endif %}para todas as outras ações.
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }}
 
@@ -174,13 +175,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 {% data reusables.webhooks.commit_comment_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.commit_comment_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -188,7 +189,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.commit_comment.created }}
 {% endif %}
@@ -197,11 +198,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 {% data reusables.webhooks.content_reference_short_desc %}
 
-Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment.
+Os eventos de webhook são acionados com base na especificidade do domínio que você registra. Por exemplo, se você registrar um subdomínio (`https://subdomain.example.com`), apenas as URLs para o subdomínio irão ativar este evento. Se você registrar um domínio (`https://example.com`), as URLs para domínio e todos os subdomínios irão ativar este evento. Consulte "[Crie um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment)" para criar um novo anexo de conteúdo.
 
-Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event.
+#### Disponibilidade
 
-#### Webhook payload example
+- {% data variables.product.prodname_github_app %}s com a permissão `content_references:write`
+
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.content_reference.created }}
 
@@ -211,25 +214,26 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. {
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez.
 
 {% endnote %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.create_properties %}
+{% data reusables.webhooks.pusher_type_desc %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.create }}
 
@@ -239,25 +243,26 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. {
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you delete more than three tags at once.
+**Observação:** Você não receberá um webhook para este evento ao excluir mais de três tags de uma só vez.
 
 {% endnote %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.delete_properties %}
+{% data reusables.webhooks.pusher_type_desc %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.delete }}
 
@@ -265,109 +270,163 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. {
 
 {% data reusables.webhooks.deploy_key_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks do repositório
+- Webhooks da organização
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.deploy_key_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.deploy_key.created }}
 
-### deployment
+### implantação
 
 {% data reusables.webhooks.deployment_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `deployments` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de `implantação`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments).
+| Tecla         | Tipo                                                                                                                                        | Descrição                                                  |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+| `Ação`        | `string`                                                                                                                                    | A ação realizada. Pode ser `criado`.{% endif %}
+| `implantação` | `objeto`                                                                                                                                    | The [implantação](/rest/reference/repos#list-deployments). |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.deployment }}
 
-### deployment_status
+### implantação_status
 
 {% data reusables.webhooks.deployment_status_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `deployments` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de `implantação`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment_status` |`object` | The [deployment status](/rest/reference/repos#list-deployment-statuses).
-`deployment_status["state"]` |`string` | The new state. Can be `pending`, `success`, `failure`, or `error`.
-`deployment_status["target_url"]` |`string` | The optional link added to the status.
-`deployment_status["description"]`|`string` | The optional human-readable description added to the status.
-`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments) that this status is associated with.
+| Tecla                              | Tipo                                                                                                                                        | Descrição                                                                                  |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+| `Ação`                             | `string`                                                                                                                                    | A ação realizada. Pode ser `criado`.{% endif %}
+| `implantação_status`               | `objeto`                                                                                                                                    | O [estado de implantação](/rest/reference/repos#list-deployment-statuses).                 |
+| `deployment_status["state"]`       | `string`                                                                                                                                    | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`.                          |
+| `deployment_status["target_url"]`  | `string`                                                                                                                                    | O link opcional adicionado ao status.                                                      |
+| `deployment_status["description"]` | `string`                                                                                                                                    | A descrição opcional legível para pessoas adicionada ao status.                            |
+| `implantação`                      | `objeto`                                                                                                                                    | A [implantação](/rest/reference/repos#list-deployments) à qual este status está associado. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.deployment_status }}
 
+{% if currentVersion == "free-pro-team@latest" %}
+### discussão
+
+{% data reusables.webhooks.discussions-webhooks-beta %}
+
+Atividade relacionada a uma discussão. Para obter mais informações, consulte "[Usar a API do GraphQL para discussões](/graphql/guides/using-the-graphql-api-for-discussions)".
+#### Disponibilidade
+
+- Webhooks do repositório
+- Webhooks da organização
+- {% data variables.product.prodname_github_app %}s com a permissão de `discussões`
+
+#### Objeto da carga do webhook
+
+| Tecla  | Tipo     | Descrição                                                                                                                                                             |
+| ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação realizada. Pode ser `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered` ou `unanswered`. |
+{% data reusables.webhooks.discussion_desc %}
+{% data reusables.webhooks.repo_desc_graphql %}
+{% data reusables.webhooks.org_desc_graphql %}
+{% data reusables.webhooks.sender_desc %}
+
+#### Exemplo de carga de webhook
+
+{{ webhookPayloadsForCurrentVersion.discussion.created }}
+
+### discussion_comment
+
+{% data reusables.webhooks.discussions-webhooks-beta %}
+
+Atividade relacionada a um comentário em uma discussão. Para obter mais informações, consulte "[Usar a API do GraphQL para discussões](/graphql/guides/using-the-graphql-api-for-discussions)".
+
+#### Disponibilidade
+
+- Webhooks do repositório
+- Webhooks da organização
+- {% data variables.product.prodname_github_app %}s com a permissão de `discussões`
+
+#### Objeto da carga do webhook
+
+| Tecla        | Tipo     | Descrição                                                                                                       |
+| ------------ | -------- | --------------------------------------------------------------------------------------------------------------- |
+| `Ação`       | `string` | A ação realizada. Pode ser `criado`, `editado` ou `excluído`.                                                   |
+| `comentário` | `objeto` | O recurso [`comentário de discussão`](/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment). |
+{% data reusables.webhooks.discussion_desc %}
+{% data reusables.webhooks.repo_desc_graphql %}
+{% data reusables.webhooks.org_desc_graphql %}
+{% data reusables.webhooks.sender_desc %}
+
+#### Exemplo de carga de webhook
+
+{{ webhookPayloadsForCurrentVersion.discussion_comment.created }}
+{% endif %}
+
 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 
 ### enterprise
 
 {% data reusables.webhooks.enterprise_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)."
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`.
+| Tecla  | Tipo     | Descrição                                                                             |
+| ------ | -------- | ------------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação realizada. Pode ser `anonymous_access_enabled` ou `anonymous_access_disabled`. |
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }}
 
 {% endif %}
 
-### fork
+### bifurcação
 
 {% data reusables.webhooks.fork_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.fork_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -375,28 +434,28 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.fork }}
 
 ### github_app_authorization
 
-When someone revokes their authorization of a {% data variables.product.prodname_github_app %}, this event occurs. A {% data variables.product.prodname_github_app %} receives this webhook by default and cannot unsubscribe from this event.
+Este evento ocorre quando alguém revoga a autorização de um {% data variables.product.prodname_github_app %}. Um {% data variables.product.prodname_github_app %} recebe este webhook por padrão e não pode cancelar a assinatura deste evento.
 
-{% data reusables.webhooks.authorization_event %} For details about user-to-server requests, which require {% data variables.product.prodname_github_app %} authorization, see "[Identifying and authorizing users for {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+{% data reusables.webhooks.authorization_event %} Para obter informações sobre solicitações de usuário para servidor, que exigem autorização do {% data variables.product.prodname_github_app %}, consulte "[Identificando e autorizando usuários para os {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
-#### Availability
+#### Disponibilidade
 
 - {% data variables.product.prodname_github_app %}s
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `revoked`.
+| Tecla  | Tipo     | Descrição                              |
+| ------ | -------- | -------------------------------------- |
+| `Ação` | `string` | A ação realizada. Pode ser `revogada`. |
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }}
 
@@ -404,13 +463,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.gollum_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.gollum_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -418,39 +477,31 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.gollum }}
 
-### installation
+### instalação
 
 {% data reusables.webhooks.installation_short_desc %}
 
 {% note %}
 
-**Note:** This event replaces the deprecated `integration_installation` event.  
+**Observação:** Este evento substitui o evento `integration_installation` obsoleto.
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** {% data reusables.pre-release-program.suspend-installation-beta %} For more information, see "[Suspending a {% data variables.product.prodname_github_app %} installation](/apps/managing-github-apps/suspending-a-github-app-installation/)."
-
-{% endnote %}
-{% endif %}
-
-#### Availability
+#### Disponibilidade
 
 - {% data variables.product.prodname_github_app %}s
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.installation_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.installation.deleted }}
 
@@ -460,21 +511,21 @@ Key | Type | Description
 
 {% note %}
 
-**Note:** This event replaces the deprecated `integration_installation_repositories` event.
+**Observação:** Este evento substitui o evento obsoleto `integration_installation_repositories`.
 
 {% endnote %}
 
-#### Availability
+#### Disponibilidade
 
 - {% data variables.product.prodname_github_app %}s
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.installation_repositories_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.installation_repositories.added }}
 
@@ -482,177 +533,266 @@ Key | Type | Description
 
 {% data reusables.webhooks.issue_comment_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `issues` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão </code>problemas`</li>
+</ul>
 
-#### Webhook payload object
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
 
-{% data reusables.webhooks.issue_comment_webhook_properties %}
-{% data reusables.webhooks.issue_comment_properties %}
+<p spaces-before="0">{% data reusables.webhooks.issue_comment_webhook_properties %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.issue_comment_properties %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.repo_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.org_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.app_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.sender_desc %}</p>
+
+<h4 spaces-before="0">Exemplo de carga de webhook</h4>
+
+<p spaces-before="0">{{ webhookPayloadsForCurrentVersion.issue_comment.created }}</p>
+
+<h3 spaces-before="0">Problemas</h3>
+
+<p spaces-before="0">{% data reusables.webhooks.issues_short_desc %}</p>
+
+<h4 spaces-before="0">Disponibilidade</h4>
+
+<ul>
+<li>Webhooks do repositório</li>
+<li>Webhooks da organização</li>
+<li>Os {% data variables.product.prodname_github_app %}s com a permissão `problemas`</li>
+</ul>
+
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
+
+<p spaces-before="0">{% data reusables.webhooks.issue_webhook_properties %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.issue_properties %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.repo_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.org_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.app_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.sender_desc %}</p>
+
+<h4 spaces-before="0">Exemplo de carga de webhook quando alguém editar um problema</h4>
+
+<p spaces-before="0">{{ webhookPayloadsForCurrentVersion.issues.edited }}</p>
+
+<h3 spaces-before="0">etiqueta</h3>
+
+<p spaces-before="0">{% data reusables.webhooks.label_short_desc %}</p>
+
+<h4 spaces-before="0">Disponibilidade</h4>
+
+<ul>
+<li>Webhooks do repositório</li>
+<li>Webhooks da organização</li>
+<li>Os {% data variables.product.prodname_github_app %}s com a permissão <code>metadados`
+
+#### Objeto da carga do webhook
+
+| Tecla                  | Tipo     | Descrição                                                             |
+| ---------------------- | -------- | --------------------------------------------------------------------- |
+| `Ação`                 | `string` | A ação que foi executada. Pode ser `criado`, `editado` ou `excluído`. |
+| `etiqueta`             | `objeto` | A etiqueta que foi adicionada.                                        |
+| `alterações`           | `objeto` | As alterações na etiqueta se a ação foi `editada`.                    |
+| `changes[name][from]`  | `string` | A versão anterior do nome se a ação foi `editada`.                    |
+| `changes[color][from]` | `string` | A versão anterior da cor se a ação foi `editada`.                     |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
-
-{{ webhookPayloadsForCurrentVersion.issue_comment.created }}
-
-### issues
-
-{% data reusables.webhooks.issues_short_desc %}
-
-#### Availability
-
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `issues` permission
-
-#### Webhook payload object
-
-{% data reusables.webhooks.issue_webhook_properties %}
-{% data reusables.webhooks.issue_properties %}
-{% data reusables.webhooks.repo_desc %}
-{% data reusables.webhooks.org_desc %}
-{% data reusables.webhooks.app_desc %}
-{% data reusables.webhooks.sender_desc %}
-
-#### Webhook payload example when someone edits an issue
-
-{{ webhookPayloadsForCurrentVersion.issues.edited }}
-
-### label
-
-{% data reusables.webhooks.label_short_desc %}
-
-#### Availability
-
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `metadata` permission
-
-#### Webhook payload object
-
-Key | Type | Description
-----|------|-------------
-`action`|`string` | The action that was performed. Can be `created`, `edited`, or `deleted`.
-`label`|`object` | The label that was added.
-`changes`|`object`| The changes to the label if the action was `edited`.
-`changes[name][from]`|`string` | The previous version of the name if the action was `edited`.
-`changes[color][from]`|`string` | The previous version of the color if the action was `edited`.
-{% data reusables.webhooks.repo_desc %}
-{% data reusables.webhooks.org_desc %}
-{% data reusables.webhooks.app_desc %}
-{% data reusables.webhooks.sender_desc %}
-
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.label.deleted }}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### marketplace_purchase
 
-Activity related to a GitHub Marketplace purchase. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub Marketplace](/marketplace/)."
+Atividade relacionada a uma compra do GitHub Marketplace. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte o "[GitHub Marketplace](/marketplace/)".
 
-#### Availability
+#### Disponibilidade
 
 - {% data variables.product.prodname_github_app %}s
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | The action performed for a [GitHub Marketplace](https://github.com/marketplace) plan. Can be one of:<ul><li>`purchased` - Someone purchased a GitHub Marketplace plan. The change should take effect on the account immediately.</li><li>`pending_change` - You will receive the `pending_change` event when someone has downgraded or cancelled a GitHub Marketplace plan to indicate a change will occur on the account. The new plan or cancellation takes effect at the end of the billing cycle.  The `cancelled` or `changed` event type will be sent when the billing cycle has ended and the cancellation or new plan should take effect.</li><li>`pending_change_cancelled` - Someone has cancelled a pending change. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle. </li><li>`changed` - Someone has upgraded or downgraded a GitHub Marketplace plan and the change should take effect on the account immediately.</li><li>`cancelled` - Someone cancelled a GitHub Marketplace plan and the last billing cycle has ended. The change should take effect on the account immediately.</li></ul>
+| Tecla  | Tipo     | Descrição                                                                                                                                         |
+| ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação realizada para um plano do [GitHub Marketplace](https://github.com/marketplace). Pode ser uma das ações a seguir:<ul><li>`comprado` - Alguém comprou um plano do GitHub Marketplace. A mudança deve entrar em vigor na conta imediatamente.</li><li>`pending_change` - Você receberá o evento `pending_change` quando alguém tiver feito o downgrade ou cancelado um plano do GitHub Marketplace para indicar que uma alteração ocorrerá na conta. O novo plano ou cancelamento entra em vigor no final do ciclo de cobrança.  O tipo de evento `cancelado` ou `alterado` será enviado quando o ciclo de cobrança terminar e o cancelamento ou o novo plano entrarem em vigor.</li><li>`pending_change_cancelled` - Alguém cancelou uma alteração pendente. Alterações pendentes incluem planos de cancelamento e downgrades que entrarão em vigor ao fim de um ciclo de cobrança. </li><li>`alterado` - Alguém fez o upgrade ou downgrade de um plano do GitHub Marketplace e a alteração entrará em vigor na conta imediatamente.</li><li>`cancelado` - Alguém cancelou um plano do GitHub Marketplace e o último ciclo de cobrança foi finalizado. A mudança deve entrar em vigor na conta imediatamente.</li></ul> |
 
-For a detailed description of this payload and the payload for each type of `action`, see [{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/).
+Para obter uma descrição detalhada desta carga e da carga para cada tipo de `ação`, consulte [eventos do webhook de {% data variables.product.prodname_marketplace %} ](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/).
 
-#### Webhook payload example when someone purchases the plan
+#### Exemplo de carga de webhook quando alguém compra o plano
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
 {% endif %}
 
-### member
+### integrante
 
 {% data reusables.webhooks.member_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `members` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão </code>membros`</li>
+</ul>
 
-#### Webhook payload object
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
 
-{% data reusables.webhooks.member_webhook_properties %}
-{% data reusables.webhooks.member_properties %}
-{% data reusables.webhooks.repo_desc %}
-{% data reusables.webhooks.org_desc %}
-{% data reusables.webhooks.app_desc %}
-{% data reusables.webhooks.sender_desc %}
+<p spaces-before="0">{% data reusables.webhooks.member_webhook_properties %}</p>
 
-#### Webhook payload example
+<p spaces-before="0">
+</p>
 
-{{ webhookPayloadsForCurrentVersion.member.added }}
+<p spaces-before="0">{% data reusables.webhooks.member_properties %}</p>
 
-### membership
+<p spaces-before="0">
+</p>
 
-{% data reusables.webhooks.membership_short_desc %}
+<p spaces-before="0">{% data reusables.webhooks.repo_desc %}</p>
 
-#### Availability
+<p spaces-before="0">
+</p>
 
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `members` permission
+<p spaces-before="0">{% data reusables.webhooks.org_desc %}</p>
 
-#### Webhook payload object
+<p spaces-before="0">
+</p>
 
-{% data reusables.webhooks.membership_properties %}
-{% data reusables.webhooks.org_desc %}
-{% data reusables.webhooks.app_desc %}
-{% data reusables.webhooks.sender_desc %}
+<p spaces-before="0">{% data reusables.webhooks.app_desc %}</p>
 
-#### Webhook payload example
+<p spaces-before="0">
+</p>
 
-{{ webhookPayloadsForCurrentVersion.membership.removed }}
+<p spaces-before="0">{% data reusables.webhooks.sender_desc %}</p>
 
-### meta
+<h4 spaces-before="0">Exemplo de carga de webhook</h4>
 
-The webhook this event is configured on was deleted. This event will only listen for changes to the particular hook the event is installed on. Therefore, it must be selected for each hook that you'd like to receive meta events for.
+<p spaces-before="0">{{ webhookPayloadsForCurrentVersion.member.added }}</p>
 
-#### Availability
+<h3 spaces-before="0">filiação</h3>
 
-- Repository webhooks
-- Organization webhooks
+<p spaces-before="0">{% data reusables.webhooks.membership_short_desc %}</p>
 
-#### Webhook payload object
+<h4 spaces-before="0">Disponibilidade</h4>
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `deleted`.
-`hook_id`  |`integer` | The id of the modified webhook.
-`hook` |`object` | The modified webhook. This will contain different keys based on the type of webhook it is: repository, organization, business, app, or GitHub Marketplace.
+<ul>
+<li>Webhooks da organização</li>
+<li>Os {% data variables.product.prodname_github_app %}s com a permissão `membros`</li>
+</ul>
+
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
+
+<p spaces-before="0">{% data reusables.webhooks.membership_properties %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.org_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.app_desc %}</p>
+
+<p spaces-before="0">
+</p>
+
+<p spaces-before="0">{% data reusables.webhooks.sender_desc %}</p>
+
+<h4 spaces-before="0">Exemplo de carga de webhook</h4>
+
+<p spaces-before="0">{{ webhookPayloadsForCurrentVersion.membership.removed }}</p>
+
+<h3 spaces-before="0">meta</h3>
+
+<p spaces-before="0">O webhook em que este evento está configurado em foi excluído. Este evento só ouvirá alterações no hook em que o evento está instalado. Portanto, deve ser selecionado para cada hook para o qual você gostaria de receber metaeventos.</p>
+
+<h4 spaces-before="0">Disponibilidade</h4>
+
+<ul>
+<li>Webhooks do repositório</li>
+<li>Webhooks da organização</li>
+</ul>
+
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
+
+<p spaces-before="0"><table spaces-before="0">
+<thead>
+<tr>
+  <th>Tecla</th>
+  <th>Tipo</th>
+  <th>Descrição</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>Ação`</td> 
+  </tr> 
+  </tbody> </table> </p>
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.meta.deleted }}
 
-### milestone
+### marco
 
 {% data reusables.webhooks.milestone_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.milestone_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -660,33 +800,42 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.milestone.created }}
 
-### organization
+### organização
 
 {% data reusables.webhooks.organization_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
-- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %}
-- Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events
-- {% data variables.product.prodname_github_app %}s with the `members` permission
+- Os webhooks do GitHub Enterprise recebem apenas eventos `criados` e `excluídos`. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/).{% endif %}
+- Os webhooks da organização recebem apenas os eventos `excluídos`, `adicionados`, `removidos`, `renomeado` e `convidados`
+- Os {% data variables.product.prodname_github_app %}s com a permissão </code>membros`</li>
+</ul>
 
-#### Webhook payload object
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. Can be one of:{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, or `member_invited`.
-`invitation` |`object` | The invitation for the user or email if the action is `member_invited`.
-`membership`  |`object` | The membership between the user and the organization.  Not present when the action is `member_invited`.
+<p spaces-before="0"><table spaces-before="0">
+<thead>
+<tr>
+  <th>Tecla</th>
+  <th>Tipo</th>
+  <th>Descrição</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>Ação`</td> 
+  </tr> 
+  </tbody> </table> </p>
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.organization.member_added }}
 
@@ -696,42 +845,46 @@ Key | Type | Description
 
 {% data reusables.webhooks.org_block_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `organization_administration` permission
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `organization_administration`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|------------
-`action` | `string` | The action performed. Can be `blocked` or `unblocked`.
-`blocked_user` | `object` | Information about the user that was blocked or unblocked.
+| Tecla          | Tipo     | Descrição                                                 |
+| -------------- | -------- | --------------------------------------------------------- |
+| `Ação`         | `string` | A ação realizada. Pode ser `bloqueado` ou `desbloqueado`. |
+| `blocked_user` | `objeto` | Informações sobre o usuário bloqueado ou desbloqueado.    |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.org_block.blocked }}
 
-### package
+{% endif %}
 
-Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}.
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 
-#### Availability
+### pacote
 
-- Repository webhooks
-- Organization webhooks
+Atividade relacionada a {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Gerenciar pacotes com {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para saber mais sobre {% data variables.product.prodname_registry %}.
 
-#### Webhook payload object
+#### Disponibilidade
+
+- Webhooks do repositório
+- Webhooks da organização
+
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.package_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.package.published }}
 {% endif %}
@@ -740,24 +893,24 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
 
 {% data reusables.webhooks.page_build_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `pages` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `páginas`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|------------
-`id` | `integer` | The unique identifier of the page build.
-`build` | `object` | The [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) itself.
+| Tecla   | Tipo      | Descrição                                                                               |
+| ------- | --------- | --------------------------------------------------------------------------------------- |
+| `id`    | `inteiro` | O identificador exclusivo da criação de páginas.                                        |
+| `build` | `objeto`  | A [Listar as criações do GitHub Pages](/rest/reference/repos#list-github-pages-builds). |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.page_build }}
 
@@ -765,25 +918,25 @@ Key | Type | Description
 
 {% data reusables.webhooks.ping_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s receive a ping event with an `app_id` used to register the app
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s recebem um evento de ping com um `app_id` usado para registrar o aplicativo
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|------------
-`zen` | `string` | Random string of GitHub zen.
-`hook_id` | `integer` | The ID of the webhook that triggered the ping.
-`hook` | `object` | The [webhook configuration](/rest/reference/repos#get-a-repository-webhook).
-`hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app.
+| Tecla          | Tipo      | Descrição                                                                                                                                                                                                                                                                                                                                                                                                               |
+| -------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `zen`          | `string`  | String aleatória do Github zen.                                                                                                                                                                                                                                                                                                                                                                                         |
+| `hook_id`      | `inteiro` | O ID do webhook que acionou o ping.                                                                                                                                                                                                                                                                                                                                                                                     |
+| `hook`         | `objeto`  | A [configuração do webhook](/rest/reference/repos#get-a-repository-webhook).                                                                                                                                                                                                                                                                                                                                            |
+| `hook[app_id]` | `inteiro` | Ao registrar um novo {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} envia um evento de ping para a **URL do webhook** que você especificou no registro. O evento contém o `app_id`, que é necessário para a [efetuar a autenticação](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) em um aplicativo. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.ping }}
 
@@ -791,13 +944,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_card_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `repository_projects` ou `organization_projects`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.project_card_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -805,7 +958,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.project_card.created }}
 
@@ -813,13 +966,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_column_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `repository_projects` ou `organization_projects`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.project_column_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -827,7 +980,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.project_column.created }}
 
@@ -835,13 +988,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `repository_projects` ou `organization_projects`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.project_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -849,44 +1002,45 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.project.created }}
 
-### public
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+### público
 
 {% data reusables.webhooks.public_short_desc %}
+#### Disponibilidade
 
-#### Availability
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `metadados`
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `metadata` permission
+#### Objeto da carga do webhook
 
-#### Webhook payload object
-
-Key | Type | Description
-----|------|-------------
+| Tecla | Tipo | Descrição |
+| ----- | ---- | --------- |
+|       |      |           |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.public }}
-
+{% endif %}
 ### pull_request
 
 {% data reusables.webhooks.pull_request_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.pull_request_webhook_properties %}
 {% data reusables.webhooks.pull_request_properties %}
@@ -895,9 +1049,9 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
-Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`.
+As entregas para eventos `review_requested` e `review_request_removed` terão um campo adicional denominado `requested_reviewer`.
 
 {{ webhookPayloadsForCurrentVersion.pull_request.opened }}
 
@@ -905,13 +1059,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% data reusables.webhooks.pull_request_review_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.pull_request_review_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -919,7 +1073,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }}
 
@@ -927,13 +1081,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% data reusables.webhooks.pull_request_review_comment_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.pull_request_review_comment_webhook_properties %}
 {% data reusables.webhooks.pull_request_review_comment_properties %}
@@ -942,7 +1096,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }}
 
@@ -952,62 +1106,56 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez.
 
 {% endnote %}
 
-{% tip %}
+#### Disponibilidade
 
-**Note**: The webhook payload example following the table differs significantly from the Events API payload described in the table. Among other differences, the webhook payload includes both `sender` and `pusher` objects. Sender and pusher are the same user who initiated the `push` event, but the `sender` object contains more detail.
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-{% endtip %}
+#### Objeto da carga do webhook
 
-#### Availability
-
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
-
-#### Webhook payload object
-
-Key | Type | Description
-----|------|-------------
-`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`.
-`before`|`string` | The SHA of the most recent commit on `ref` before the push.
-`after`|`string` | The SHA of the most recent commit on `ref` after the push.
-`commits`|`array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.)
-`commits[][id]`|`string` | The SHA of the commit.
-`commits[][timestamp]`|`string` | The ISO 8601 timestamp of the commit.
-`commits[][message]`|`string` | The commit message.
-`commits[][author]`|`object` | The git author of the commit.
-`commits[][author][name]`|`string` | The git author's name.
-`commits[][author][email]`|`string` | The git author's email address.
-`commits[][url]`|`url` | URL that points to the commit API resource.
-`commits[][distinct]`|`boolean` | Whether this commit is distinct from any that have been pushed before.
-`commits[][added]`|`array` | An array of files added in the commit.
-`commits[][modified]`|`array` | An array of files modified by the commit.
-`commits[][removed]`|`array` | An array of files removed in the commit.
-`pusher` | `object` | The user who pushed the commits.
+| Tecla                      | Tipo      | Descrição                                                                                                                                                                                                                                                                                                                        |
+| -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ref`                      | `string`  | O [`git ref completo`](/rest/reference/git#refs) que foi empurrado. Exemplo: `refs/heads/master`.                                                                                                                                                                                                                                |
+| `antes`                    | `string`  | O SHA do último commit em `ref` antes do push.                                                                                                                                                                                                                                                                                   |
+| `depois`                   | `string`  | O SHA do último commit no `ref` após o push.                                                                                                                                                                                                                                                                                     |
+| `commits`                  | `array`   | Um array de objetos de commit, que descreve os commits carregados. (O array inclui um máximo de 20 commits. Se necessário, você pode usar a [API de Commits](/rest/reference/repos#commits) para obter commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook.) |
+| `commits[][id]`            | `string`  | O SHA do commit.                                                                                                                                                                                                                                                                                                                 |
+| `commits[][timestamp]`     | `string`  | O carimbo de tempo ISO 8601 do commit.                                                                                                                                                                                                                                                                                           |
+| `commits[][message]`       | `string`  | A mensagem do commit.                                                                                                                                                                                                                                                                                                            |
+| `commits[][author]`        | `objeto`  | O autor do git do commit.                                                                                                                                                                                                                                                                                                        |
+| `commits[][author][name]`  | `string`  | O nome do autor do git.                                                                                                                                                                                                                                                                                                          |
+| `commits[][author][email]` | `string`  | O endereço de e-mail do autor do git.                                                                                                                                                                                                                                                                                            |
+| `commits[][url]`           | `url`     | URL que aponta para o recurso de commit de API.                                                                                                                                                                                                                                                                                  |
+| `commits[][distinct]`      | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente.                                                                                                                                                                                                                                        |
+| `commits[][added]`         | `array`   | Um array de arquivos adicionados no commit.                                                                                                                                                                                                                                                                                      |
+| `commits[][modified]`      | `array`   | Um array de arquivos modificados pelo commit.                                                                                                                                                                                                                                                                                    |
+| `commits[][removed]`       | `array`   | Um array de arquivos removidos no commit.                                                                                                                                                                                                                                                                                        |
+| `pusher`                   | `objeto`  | O usuário que fez o push dos commits.                                                                                                                                                                                                                                                                                            |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.push }}
 
-### release
+### versão
 
 {% data reusables.webhooks.release_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `contents` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.release_webhook_properties %}
 {% data reusables.webhooks.release_properties %}
@@ -1016,66 +1164,66 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.release.published }}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
 ### repository_dispatch
 
-This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint.
+Este evento ocorre quando um {% data variables.product.prodname_github_app %} envia uma solicitação de `POST` para o "[Crie um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint.
 
-#### Availability
+#### Disponibilidade
 
-- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook.
+- Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `conteúdo` para receber este webhook.
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.repository_dispatch }}
 {% endif %}
 
-### repository
+### repositório
 
 {% data reusables.webhooks.repository_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks receive all event types except `deleted`
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `metadata` permission receive all event types except `deleted`
+- Os webhooks do repositório recebem todos os tipos de eventos, exceto `excluído`
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão de `metadados` recebem todos os tipos de eventos, exceto `excluídos`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. This can be one of:<ul><li>`created` - A repository is created.</li><li>`deleted` - A repository is deleted.</li><li>`archived` - A repository is archived.</li><li>`unarchived` - A repository is unarchived.</li>{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}<li>`anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)</li>{% endif %}<li>`edited` - A repository's information is edited.</li><li>`renamed` - A repository is renamed.</li><li>`transferred` - A repository is transferred.</li><li>`publicized` - A repository is made public.</li><li> `privatized` - A repository is made private.</li></ul>
+| Tecla  | Tipo     | Descrição                                                                          |
+| ------ | -------- | ---------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação que foi executada. Este pode ser um dos seguintes:<ul><li>`created` - Um repositório foi criado.</li><li>`deleted` - Um repositório foi excluído.</li><li>`archived` - Um repositório está arquivado.</li><li>`unarchived` - Um repositório não está arquivado.</li>{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}<li>`anonymous_access_enabled` - Um repositório está [habilitado para acesso anônimo ao Git](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - Um repositório está [desativado para acesso anônimo ao Git](/rest/overview/api-previews#anonymous-git-access-to-repositories)</li>{% endif %}<li>`edited` - As informações de um repositório são editadas.</li><li>`renamed` - Um repositório é renomeado.</li><li>`transferred` - Um repositório é transferido.</li><li>`publicized` - Um repositório é publicado.</li><li> `privatizado` - Um repositório é privatizado.</li></ul> |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.repository.publicized }}
 
 {% if currentVersion == "free-pro-team@latest"%}
 ### repository_import
 
-{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports).
+{% data reusables.webhooks.repository_import_short_desc %} Para receber este evento para um repositório pessoal, você deve criar um repositório vazio antes da importação. Este evento pode ser acionado usando o [Importador do GitHub](/articles/importing-a-repository-with-github-importer/) ou a API [Api de Importação de Fonte](/rest/reference/migrations#source-imports).
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks do repositório
+- Webhooks da organização
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.repository_import_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.repository_import }}
 
@@ -1083,19 +1231,19 @@ Key | Type | Description
 
 {% data reusables.webhooks.repository_vulnerability_alert_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks do repositório
+- Webhooks da organização
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.repository_vulnerability_alert_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }}
 
@@ -1107,21 +1255,21 @@ Key | Type | Description
 
 {% data reusables.webhooks.secret_scanning_alert_event_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `secret_scanning_alerts:read` permission
+- Webhooks do repositório
+- Webhooks da organização
+- {% data variables.product.prodname_github_app %}s com a permissão `secret_scanning_alerts:read`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.secret_scanning_alert_event_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
-`sender` | `object` | If the `action` is `resolved` or `reopened`, the `sender` object will be the user that triggered the event. The `sender` object is empty for all other actions.
+`sender` | `object` | Se a `action` is `resolved` ou `reopened`, o objeto de `sender` será o usuário que acionou o evento. O objeto `remetente` está vazio para todas as outras ações.
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }}
 {% endif %}
@@ -1129,68 +1277,68 @@ Key | Type | Description
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %}
 ### security_advisory
 
-Activity related to a security advisory. A security advisory provides information about security-related vulnerabilities in software on GitHub. The security advisory dataset also powers the GitHub security alerts, see "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies/)."
+Atividade relacionada a uma consultora de segurança. Uma consultoria de segurança fornece informações sobre vulnerabilidades relacionadas à segurança em softwares no GitHub. O conjunto de dados da consultoria de segurança também promove os alertas de segurança do GitHub, consulte "[Sobre os alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)."
 {% endif %}
 
-#### Availability
+#### Disponibilidade
 
-- {% data variables.product.prodname_github_app %}s with the `security_events` permission
+- Os {% data variables.product.prodname_github_app %}s com a permissão `security_events`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. The action can be one of `published`, `updated`, or `performed` for all new events.
-`security_advisory` |`object` | The details of the security advisory, including summary, description, and severity.
+| Tecla               | Tipo     | Descrição                                                                                                           |
+| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
+| `Ação`              | `string` | A ação que foi executada. A ação pode ser `publicadas`, `atualizadas`, ou `executadas` para todos os novos eventos. |
+| `security_advisory` | `objeto` | As informações da consultoria de segurança, incluindo resumo, descrição e gravidade.                                |
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.security_advisory.published }}
 
 {% if currentVersion == "free-pro-team@latest" %}
-### sponsorship
+### patrocínio
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
+Você só pode criar um webhook de patrocínio em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Configurar webhooks para eventos na sua conta patrocinada](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
 
-#### Availability
+#### Disponibilidade
 
-- Sponsored accounts
+- Contas patrocinadas
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.sponsorship_webhook_properties %}
 {% data reusables.webhooks.sponsorship_properties %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example when someone creates a sponsorship
+#### Exemplo de carga de webhook quando alguém cria um patrocínio
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.created }}
 
-#### Webhook payload example when someone downgrades a sponsorship
+#### Exemplo de carga de webhook quando alguém faz o downgrade de um patrocínio
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }}
 
 {% endif %}
 
-### star
+### estrela
 
 {% data reusables.webhooks.star_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks do repositório
+- Webhooks da organização
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.star_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.star.created }}
 
@@ -1198,58 +1346,60 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_
 
 {% data reusables.webhooks.status_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `statuses` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `status`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`id` | `integer` | The unique identifier of the status.
-`sha`|`string` | The Commit SHA.
-`state`|`string` | The new state. Can be `pending`, `success`, `failure`, or `error`.
-`description`|`string` | The optional human-readable description added to the status.
-`target_url`|`string` | The optional link added to the status.
-`branches`|`array` | An array of branch objects containing the status' SHA. Each branch contains the given SHA, but the SHA may or may not be the head of the branch. The array includes a maximum of 10 branches.
+| Tecla         | Tipo      | Descrição                                                                                                                                                                              |
+| ------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`          | `inteiro` | O identificador exclusivo do status.                                                                                                                                                   |
+| `sha`         | `string`  | O SHA do commit.                                                                                                                                                                       |
+| `estado`      | `string`  | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`.                                                                                                                      |
+| `descrição`   | `string`  | A descrição opcional legível para pessoas adicionada ao status.                                                                                                                        |
+| `url_destino` | `string`  | O link opcional adicionado ao status.                                                                                                                                                  |
+| `branches`    | `array`   | Um array de objetos de branch que contém o SHA do status. Cada branch contém o SHA fornecido, mas o SHA pode ou não ser o cabeçalho do branch. O array inclui, no máximo, 10 branches. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.status }}
 
-### team
+### equipe
 
 {% data reusables.webhooks.team_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `members` permission
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão </code>membros`</li>
+</ul>
 
-#### Webhook payload object
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. Can be one of `created`, `deleted`, `edited`, `added_to_repository`, or `removed_from_repository`.
-`team`  |`object` | The team itself.
-`changes`|`object` | The changes to the team if the action was `edited`.
-`changes[description][from]` |`string` | The previous version of the description if the action was `edited`.
-`changes[name][from]` |`string` | The previous version of the name if the action was `edited`.
-`changes[privacy][from]` |`string` | The previous version of the team's privacy if the action was `edited`.
-`changes[repository][permissions][from][admin]` | `boolean` | The previous version of the team member's `admin` permission on a repository, if the action was `edited`.
-`changes[repository][permissions][from][pull]` | `boolean` | The previous version of the team member's `pull` permission on a repository, if the action was `edited`.
-`changes[repository][permissions][from][push]` | `boolean` | The previous version of the team member's `push` permission on a repository, if the action was `edited`.
-`repository`|`object` | The repository that was added or removed from to the team's purview if the action was `added_to_repository`, `removed_from_repository`, or `edited`. For `edited` actions, `repository` also contains the team's new permission levels for the repository.
+<p spaces-before="0"><table spaces-before="0">
+<thead>
+<tr>
+  <th>Tecla</th>
+  <th>Tipo</th>
+  <th>Descrição</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>Ação`</td> 
+  </tr> 
+  </tbody> </table> </p>
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.team.added_to_repository }}
 
@@ -1257,54 +1407,64 @@ Key | Type | Description
 
 {% data reusables.webhooks.team_add_short_desc %}
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `members` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão </code>membros`</li>
+</ul>
 
-#### Webhook payload object
+<h4 spaces-before="0">Objeto da carga do webhook</h4>
 
-Key | Type | Description
-----|------|-------------
-`team`|`object` | The [team](/rest/reference/teams) that was modified.  **Note:** Older events may not include this in the payload.
+<p spaces-before="0"><table spaces-before="0">
+<thead>
+<tr>
+  <th>Tecla</th>
+  <th>Tipo</th>
+  <th>Descrição</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>equipe`</td> 
+  </tr> </tbody> </table> </p>
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.team_add }}
 
 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 
-### user
+### usuário
 
-When a user is `created` or `deleted`.
+Quando um usuário é `criado` ou `excluído`.
 
-#### Availability
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+#### Disponibilidade
+- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)."
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.user.created }}
 
 {% endif %}
 
-### watch
+### inspecionar
 
 {% data reusables.webhooks.watch_short_desc %}
 
-The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred.
+O ator do evento é o [usuário](/rest/reference/users) que favoritou um repositório, e o repositório do evento é [repositório](/rest/reference/repos) que foi marcado com estrela.
 
-#### Availability
+#### Disponibilidade
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_app %}s with the `metadata` permission
+- Webhooks do repositório
+- Webhooks da organização
+- Os {% data variables.product.prodname_github_app %}s com a permissão `metadados`
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
 {% data reusables.webhooks.watch_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -1312,20 +1472,20 @@ The event’s actor is the [user](/rest/reference/users) who starred a repositor
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.watch.started }}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 ### workflow_dispatch
 
-This event occurs when someone triggers a workflow run on GitHub or sends a `POST` request to the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" endpoint. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)."
+Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no GitHub ou envia uma solicitação de `POST` para o ponto de extremidade "[Criar um evento de envio de fluxo de trabalho](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
-#### Availability
+#### Disponibilidade
 
-- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook.
+- Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `conteúdo` para receber este webhook.
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
 {% endif %}
@@ -1333,22 +1493,21 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 ### workflow_run
 
-When a {% data variables.product.prodname_actions %} workflow run is requested or completed. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_run)."
+Quando uma execução do fluxo de trabalho de {% data variables.product.prodname_actions %} for solicitada ou concluída. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_run)".
 
-#### Availability
+#### Disponibilidade
 
-- {% data variables.product.prodname_github_app %}s with the `actions` or `contents` permissions.
+- {% data variables.product.prodname_github_app %} com as `ações` ou permissões de `conteúdo`.
 
-#### Webhook payload object
+#### Objeto da carga do webhook
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event.
+{% data reusables.webhooks.workflow_run_properties %}
+{% data reusables.webhooks.workflow_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-#### Webhook payload example
+#### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_run }}
 {% endif %}
diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index f2f4a2ab9c..4d4770f840 100644
--- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %} Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 
-Além de começar ou visualizar uma discussão, você pode comentar em resposta ao comentário original do autor da discussão. Você também pode criar um tópico de comentário respondendo a um comentário individual feito por outro integrante da comunidade dentro da discussão e reagir aos comentários com emoji. Para obter mais informações sobre reações, consulte "[Sobre conversas em {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)".
+Além de começar ou visualizar uma discussão, você pode comentar em resposta ao comentário original do autor da discussão. Você também pode criar um tópico de comentário respondendo a um comentário individual feito por outro integrante da comunidade dentro da discussão e reagir aos comentários com emoji.
 
 Você pode bloquear usuários e reportar conteúdo disruptivo para manter um ambiente seguro e agradável para você mesmo em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Manter sua segurança em {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)".
 
diff --git a/translations/pt-BR/content/discussions/index.md b/translations/pt-BR/content/discussions/index.md
index 73c1ec0fd8..d11db4bb05 100644
--- a/translations/pt-BR/content/discussions/index.md
+++ b/translations/pt-BR/content/discussions/index.md
@@ -34,24 +34,3 @@ versions:
 <!-- {% link_with_intro /discussions-guides %} -->
 <!-- {% link_with_intro /collaborating-with-your-community-using-discussions %} -->
 <!-- {% link_with_intro /managing-discussions-for-your-community %} -->
-
-<!-- Community examples -->
-{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %}
-{% if discussionsCommunityExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Comunidades que usam discussões</h2>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render discussions-community-card for discussionsCommunityExamples as example %}
-  </div>
-  {% if discussionsCommunityExamples.length > 6 %}
-    <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Mostrar mais {% octicon "arrow-right" %}</button>
-  {% endif %}
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Desculpe, não há resultados para <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">Parece que não temos um exemplo que se encaixa no seu filtro.<br>Tente outro filtro ou adicione seu exemplo de código</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/discussions_community_examples.yml">Adicione sua comunidade {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md
index 9e2b30c187..bc8b2833ad 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Campus Program
-intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.'
+title: Sobre o Programa do GitHub Campus
+intro: '{% data variables.product.prodname_campus_program %} oferece {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} gratuitamente para as escolas que querem tirar o máximo proveito de {% data variables.product.prodname_dotcom %} para a sua comunidade.'
 redirect_from:
   - /education/teach-and-learn-with-github-education/about-github-education
   - /github/teaching-and-learning-with-github-education/about-github-education
@@ -10,14 +10,14 @@ versions:
   free-pro-team: '*'
 ---
 
-{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes:
+{% data variables.product.prodname_campus_program %} é um pacote de acesso premium de {% data variables.product.prodname_dotcom %} para instituições orientadas para o ensino que concedem graus, diplomas ou certificados. {% data variables.product.prodname_campus_program %} inclui:
 
-- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments
+- Acesso sem custo a {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} para todos os seus departamentos técnicos e acadêmicos
 - Treinamento do professor para domínio do Git e do {% data variables.product.prodname_dotcom %} com nosso programa de consultores de campus
-- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners
+- Acesso exclusivo a novas funcionalidades, swage específico do GitHub Education e ferramentas grátis de desenvolvedor dos parceiros de {% data variables.product.prodname_dotcom %}
 - Acesso automatizado a recursos premium do {% data variables.product.prodname_education %}, como o {% data variables.product.prodname_student_pack %}
 
-Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join.
+Qualquer escola que concorde com os [termos do programa](https://education.github.com/schools/terms) é bem-vinda.
 
 Para obter mais informações, consulte a página [oficial do {% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
 
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md
index eb74647023..e4c7502f41 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md
@@ -59,11 +59,11 @@ Para obter mais informações, consulte:
 ### Status de aluno não qualificado
 
 Você não estará qualificado para um {% data variables.product.prodname_student_pack %} se:
-- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study.
-- You're pursuing a degree which will be terminated in the current academic session.
+- Você está inscrito em um programa de aprendizagem informal que não faz parte de [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) e não está inscrito em curso que irá conceder uma título ou diploma.
+- Você irá obter um título que não estará mais disponível na sessão acadêmica atual.
 - Tiver menos de 13 anos.
 
-Seu instrutor ainda poderá se candidatar a um desconto {% data variables.product.prodname_education %} para uso em sala de aula. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
+Seu instrutor ainda poderá se candidatar a um desconto {% data variables.product.prodname_education %} para uso em sala de aula. Se você é um estudante em uma escola de programação ou bootcamp, você irá tornar-se elegível a {% data variables.product.prodname_student_pack %}, caso sua escola ingresse em [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
index 492b4bd0b5..77e3094770 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
@@ -17,7 +17,7 @@ Quando um aluno aceita uma atividade em grupo, o aluno poderá criar uma nova eq
 
 {% data reusables.classroom.about-assignments %}
 
-Você pode decidir quantas equipes uma atividade pode ter e quantos integrantes cada equipe pode ter. Cada equipe que um estudante cria para uma atividade é uma equipe dentro da sua organização em {% data variables.product.product_name %}. A visibilidade da equipe é secreta. Equipes criadas em {% data variables.product.product_name %} não aparecerão em {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Você pode decidir quantas equipes uma atividade pode ter e quantos integrantes cada equipe pode ter. Cada equipe que um estudante cria para uma atividade é uma equipe dentro da sua organização em {% data variables.product.product_name %}. A visibilidade da equipe é secreta. Equipes criadas em {% data variables.product.product_name %} não aparecerão em {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Sobre equipes](/organizations/organizing-members-into-teams/about-teams)".
 
 Para uma demonstração de vídeo da criação de uma atividade de grupo, consulte "[Fundamentos de configuração de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)".
 
@@ -132,7 +132,7 @@ Você pode ver as equipes que estão trabalhando ou que enviaram uma atividade n
 
 ### Próximas etapas
 
-- Após criar a atividade e seus alunos formarem equipes, os integrantes da equipe poderão começar a trabalhar nas atividades usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Tanto você como a equipe podem revisar o histórico de commit do repositório. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}.
+- Após criar a atividade e seus alunos formarem equipes, os integrantes da equipe poderão começar a trabalhar nas atividades usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Tanto você como a equipe podem revisar o histórico de commit do repositório. Para obter mais informações, consulte "[Começando com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github), "[Criar, clonar e arquivar repositórios](/github/creating-cloning-and-archiving-repositories)," "[Usar Git](/github/getting-started-with-github/using-git), e "[Colaborar com problemas e pull requests](/github/collaborating-with-issues-and-pull-requests) e o curso grátis em [gerenciar conflitos de merge](https://lab.github.com/githubtraining/managing-merge-conflicts) de {% data variables.product.prodname_learning %}.
 
 - Quando uma equipe termina uma atividade, você poderá revisar os arquivos no repositório, ou você poderá revisar o histórico e as visualizações do repositório para entender melhor como a equipe colaborou. Para obter mais informações, consulte "[Visualizar dados do repositório com gráficos](/github/visualizing-repository-data-with-graphs)".
 
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md
index 9d612ad3f1..3e52063329 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md
@@ -112,7 +112,7 @@ Você pode ver se um aluno juntou-se à sala de aula e aceitou ou enviou uma ati
 
 ### Próximas etapas
 
-- Depois de criar a atividade, os alunos poderão começar a trabalhar na atividade usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Você e o aluno podem revisar o histórico do commit do repositório. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- Depois de criar a atividade, os alunos poderão começar a trabalhar na atividade usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Você e o aluno podem revisar o histórico do commit do repositório. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Criar, clonar e arquivar repositórios](/github/creating-cloning-and-archiving-repositories)", "[Usar o Git](/github/getting-started-with-github/using-git)" e "[Colaborar com problemas e pull requests](/github/collaborating-with-issues-and-pull-requests)".
 
 - Quando um aluno concluir uma atividade, você poderá revisar os arquivos no repositório ou você poderá revisar o histórico e as visualizações do repositório para entender melhor o trabalho do aluno. Para obter mais informações, consulte "[Visualizar dados do repositório com gráficos](/github/visualizing-repository-data-with-graphs)".
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md b/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md
index 08f1d2a3f4..ded97e356e 100644
--- a/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/pt-BR/content/github/administering-a-repository/about-protected-branches.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre branches protegidos
-intro: 'Os branches protegidos garantem que colaboradores no seu repositório não possam fazer alterações irreversíveis nos branches. Habilitar branches protegidos também permite habilitar outros requisitos e verificações opcionais, como verificação de status obrigatória e revisões obrigatórias.'
+intro: 'Você pode proteger branches importantes definindo regras de proteção de branch, que definem se os colaboradores podem excluir ou forçar push para o branch e definem os requisitos para todos os pushes para o branch, tais como verificações de status de passagem ou um histórico linear de commits.'
 product: '{% data reusables.gated-features.protected-branches %}'
 redirect_from:
   - /articles/about-protected-branches
@@ -23,28 +23,132 @@ topics:
   - Repositories
 ---
 
-### Sobre branches protegidos
+### Sobre as regras de proteção do branch
 
-{% data reusables.pull_requests.about-protected-branches %} Você pode optar por aplicar restrições sobre como um pull request é mesclado no seu repositório.
+É possível aplicar certos fluxos de trabalho ou requisitos antes que um colaborador possa fazer push de alterações em um branch no repositório, incluindo o merge de um pull request no branch, criando uma regra de proteção de branch.
 
-Os proprietários de repositório e as pessoas com permissões de administrador para um repositório podem impor determinados fluxos de trabalho ou requisitos, antes que um colaborador possa fazer merge em seu repositório criando regras de branch protegido.
+Por padrão, cada regra de proteção de branch desabilita push forçado para os branches correspondentes e impede que os branches correspondentes sejam excluídos. Você pode, opcionalmente, desabilitar essas restrições e habilitar configurações adicionais de proteção de branches.
 
-{% data reusables.repositories.branch-rules-example %} Para obter mais informações, consulte "[Configurar branches protegidos](/articles/configuring-protected-branches/)."
+Por padrão, as restrições de uma regra de proteção de branch não se aplicam a pessoas com permissões de administrador para o repositório. Opcionalmente, você também pode escolher incluir administradores.
+
+{% data reusables.repositories.branch-rules-example %} Para obter mais informações sobre os padrões de nomes do branch, consulte "[Gerenciar uma regra de proteção de branch](/github/administering-a-repository/managing-a-branch-protection-rule)".
 
 {% data reusables.pull_requests.you-can-auto-merge %}
 
-### Priorização de regras de branches protegidos
+### Sobre as configurações de proteção do branch
 
-Se um repositório tiver várias regras de branch protegido que afetem os mesmos branches, as regras que incluírem um nome de branch específico terão a prioridade mais alta. Se houver mais de uma regra de branch protegido que faça referência ao mesmo nome de branch específico, a regra de branch criada primeiro terá a prioridade mais alta.
+Para cada regra de proteção do branch, você pode escolher habilitar ou desabilitar as seguintes configurações.
+- [Exigir revisões de pull request antes do merge](#require-pull-request-reviews-before-merging)
+- [Exigir verificações de status antes do merge](#require-status-checks-before-merging)
+- [Exigir commits assinados](#require-signed-commits)
+- [Exigir histórico linear](#require-linear-history)
+- [Incluir administradores](#include-administrators)
+- [Restringir quem pode fazer push para branches correspondentes](#restrict-who-can-push-to-matching-branches)
+- [Permitir push forçado](#allow-force-pushes)
+- [Permitir exclusões](#allow-deletions)
 
-As regras de branch protegido que mencionam um caractere especial, como `*`, `?` ou `]`, são aplicadas na ordem em que foram criadas, de modo que as regras mais antigas com esses caracteres têm uma prioridade mais alta.
+For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
 
-### Configurações de proteção de branch
+#### Exigir revisões de pull request antes do merge
 
-Ao criar uma regra de proteção de branch em um repositório, os colaboradores não podem fazer push forçado no branch protegido ou excluir o branch{% if currentVersion == "free-pro-team@latest" %} por padrão{% endif %}. Você pode habilitar outras configurações de proteção de branch. Para obter informações, consulte "[Definir a possibilidade de mesclagem de pull requests](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)".
+{% data reusables.pull_requests.required-reviews-for-prs-summary %}
 
-### Leia mais
+Se você habilitar as revisões necessárias, os colaboradores só podem fazer push das alterações em um branch protegido por meio de um pull request aprovado pelo número necessário de revisores com permissões de gravação.
 
-- "[Sobre verificações de status obrigatórias](/articles/about-required-status-checks)"
-- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)"
-- "[Sobre a assinatura de commit obriagória](/articles/about-required-commit-signing)"
+Se uma pessoa com permissões de administrador escolher a opção **Solicitar alterações** em uma revisão, essa pessoa deverá aprovar o pull request antes que o merge possa ser efetuado. Se um revisor que solicita alterações em um pull request não estiver disponível, qualquer pessoa com permissões de gravação no repositório poderá ignorar a revisão de bloqueio.
+
+{% data reusables.repositories.review-policy-overlapping-commits %}
+
+Se um colaborador tentar fazer merge de um pull request com revisões pendentes ou rejeitadas no branch protegido, o colaborador receberá uma mensagem de erro.
+
+```shell
+remote: error: GH006: Protected branch update failed for refs/heads/main.
+remote: error: Changes have been requested.
+```
+
+Opcionalmente, você pode escolher ignorar as aprovações de pull request obsoletas quando commits são enviados por push. Se alguém fizer push de um commit que modifica código para um pull request aprovado, a aprovação será ignorada e o pull request não poderá ser mesclado. Isso não se aplica se o colaborador fizer push de commits que não modificam código, como mesclar o branch de base no branch do pull request. Para obter mais informações sobre branch base, consulte "[Sobre pull requests](/articles/about-pull-requests)".
+
+Opcionalmente, você pode restringir a capacidade de ignorar comentários de pull request para pessoas ou equipes específicas. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/articles/dismissing-a-pull-request-review)".
+
+Opcionalmente, você pode optar por exigir análises dos proprietários do código. Se você o fizer, qualquer pull request que afeta código com o proprietário do código deverá ser aprovado pelo proprietário desse código antes que o pull request possa ser mesclada no branch protegido.
+
+#### Exigir verificações de status antes do merge
+
+As verificações de status obrigatórias garantem que todos os testes de CI sejam aprovados antes que os colaboradores possam fazer alterações em um branch protegido. Para obter mais informações, consulte "[Configurar branches protegidos](/articles/configuring-protected-branches/)" e "[Habilitar verificações de status obrigatórias](/articles/enabling-required-status-checks)". Para obter mais informações, consulte "[Sobre verificações de status](/github/collaborating-with-issues-and-pull-requests/about-status-checks)".
+
+Antes de habilitar as verificações de status necessárias, é necessário configurar o repositório para usar a API de status. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#statuses)" na documentação do REST.
+
+Depois de habilitar a verificação de status obrigatória, todas as verificações de status necessárias deverão passar para que os colaboradores possam fazer merge das alterações no branch protegido. Depois que todas as verificações de status necessárias passarem, quaisquer commits devem ser enviados por push para outro branch e, em seguida, mesclados ou enviados por push diretamente para o branch protegido.
+
+{% note %}
+
+**Observação:** Qualquer pessoa ou integração com permissões de gravação em um repositório pode configurar o estado de qualquer verificação de status no repositório. O {% data variables.product.company_short %} não analisa se o autor de uma verificação está autorizado a criar uma verificação com um determinado nome ou modificar um status existente. Antes de realizar o merge de uma pull request, você deve verificar se o autor de cada status, listado na caixa de merge, é esperado.
+
+{% endnote %}
+
+Você pode configurar as verificações de status obrigatórias como "flexível" ou "rígida". O tipo de verificação de status obrigatória que você escolher determinará se o branch precisará ser atualizado com o branch base antes do merge.
+
+| Tipo de verificação de status obrigatória | Configuração                                                                                                                                                  | Requisitos de merge                                                    | Considerações                                                                                                                                                                                                                                                                                |
+| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Rígida**                                | A caixa de seleção **Exigir a atualização dos branches antes de fazer merge** fica marcada.                                                                   | O branch **precisa** ser atualizado no branch base antes do merge.     | Este é o comportamento padrão para verificações de status obrigatórias. Podem ser necessárias mais compilações, já que você precisará atualizar o branch head depois que outros colaboradores fizerem merge de pull requests no branch base protegido.                                       |
+| **Flexível**                              | A caixa de seleção **Exigir a atualização dos branches antes de fazer merge** **não** fica marcada.                                                           | O branch **não precisa** ser atualizado no branch base antes do merge. | Serão necessárias menos compilações, já que você não precisará atualizar o branch head depois que outros colaboradores fizerem merge de pull requests. As verificações de status poderão falhar depois que você fizer merge do branch, caso haja alterações incompatíveis com o branch base. |
+| **Desabilitada**                          | A caixa de seleção **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge) **não** fica marcada. | O branch não tem restrições de merge.                                  | Se as verificações de status obrigatórias não estiverem habilitadas, os colaboradores poderão fazer merge do branch a qualquer momento, estando ou não atualizados com o branch base. Isso aumenta a possibilidade de alterações incompatíveis.                                              |
+
+Para obter informações sobre a solução de problemas, consulte "[Solucionar problemas para as verificações de status obrigatórias](/github/administering-a-repository/troubleshooting-required-status-checks)".
+
+#### Exigir commits assinados
+
+Ao habilitar a assinatura de commit obrigatória em um branch, os contribuidores {% if currentVersion == "free-pro-team@latest" %}e bots{% endif %} só podem fazer push de commits que foram assinados e verificados no branch. Para obter mais informações, consulte "[Sobre verificação de assinatura commit](/articles/about-commit-signature-verification)".
+
+{% note %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Notas:**
+
+* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+
+{% else %}
+**Observação:** Se um colaborador fizer push de um commit não assinado para um branch que exige assinaturas de commit, o colaborador deverá fazer rebase do commit para incluir uma assinatura verificada e, em seguida, fazer push forçado no commit reescrito para o branch.
+{% endif %}
+
+{% endnote %}
+
+Você sempre pode fazer push de commits locais para o branch se os commits forem assinados e verificados. {% if currentVersion == "free-pro-team@latest" %}Você também pode fazer merge de commits assinados e verificados no branch usando um pull request em {% data variables.product.product_name %}. No entanto, você não pode realizar a combinação por squash e fazer o merge de um pull request no branch em {% data variables.product.product_name %} a menos que você seja o autor do pull request.{% else %}No entanto, você não pode fazer merge de pull requests no branch em {% data variables.product.product_name %}.{% endif %} Você pode {% if currentVersion == "free-pro-team@latest" %}fazer combinação por squash e {% endif %} fazer merge de pull requests localmente. Para obter mais informações, consulte "[Fazer checkout de pull requests localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)".
+
+{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações sobre métodos de merge, consulte "[Sobre métodos de merge em {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github){% endif %}
+
+#### Exigir histórico linear
+
+Aplicar o histórico linear de commit impede que os colaboradores façam push de commits de merge no branch. Isto significa que quaisquer pull requests mesclada no branch protegido devem usar um merge squash ou um merge rebase. Um histórico de commit estritamente linear pode ajudar as equipes a reverter alterações mais facilmente. Para obter mais informações sobre métodos de merge, consulte "[Sobre merges de pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)".
+
+Antes de exigir um histórico de commit linear, seu repositório deve permitir merge squash ou merge rebase. Para obter mais informações, consulte "[Configurando merges da pull request](/github/administering-a-repository/configuring-pull-request-merges)".
+
+#### Incluir administradores
+
+Por padrão, as regras de branch protegidos não se aplicam a pessoas com permissões de administrador em um repositório. Você pode habilitar essa configuração para incluir administradores em suas regras de branch protegido.
+
+#### Restringir quem pode fazer push para branches correspondentes
+
+{% if currentVersion == "free-pro-team@latest" %}
+Você pode habilitar restrições de branch se o seu repositório pertencer a uma organização que usa
+{% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}.
+{% endif %}
+
+Ao habilitar as restrições de branches, apenas usuários, equipes ou aplicativos com permissão podem fazer push para o branch protegido. Você pode visualizar e editar usuários, equipes ou aplicativos com acesso de push a um branch protegido nas configurações do branch protegido.
+
+Você só pode dar acesso de push a um branch protegido a usuários, equipes ou {% data variables.product.prodname_github_apps %} instalados com acesso de gravação a um repositório. As pessoas e os aplicativos com permissões de administrador em um repositório sempre conseguem fazer push em um branch protegido.
+
+#### Permitir push forçado
+
+Por padrão, os blocks do {% data variables.product.product_name %} fazem push forçado em todos os branches protegidos. Quando você habilitar push forçado em um branch protegido, qualquer pessoa com, pelo menos, permissões de gravação no repositório pode forçar o push ao branch, incluindo aqueles com permissões de administrador.
+
+Habilitar push forçado não irá substituir quaisquer outras regras de proteção de branch. Por exemplo, se um branch exigir um histórico de commit linear, você não poderá forçar commits a mesclar commits para esse branch.
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Você não pode habilitar push forçados para um branch protegido se um administrador do site bloqueou o push forçado para todos os branches no seu repositório. Para obter mais informações, consulte "[Bloqueando push forçado para repositórios de propriedade de uma conta de usuário ou organização](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)."
+
+Se um administrador do site bloquear pushes forçados apenas para o branch padrão, você ainda pode habilitar pushes forçados para qualquer outro branch protegido.{% endif %}
+
+#### Permitir exclusões
+
+Por padrão, você não pode excluir um branch protegido. Ao habilitar a exclusão de um branch protegido, qualquer pessoa com permissão de gravação no repositório pode excluir o branch.
diff --git a/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md b/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md
index c8a1327b49..4c678eaa6a 100644
--- a/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/pt-BR/content/github/administering-a-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ Você pode escolher o branch-padrão para um repositório. O branch-padrão é o
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
 Você também pode renomear o branch padrão. Para obter mais informações, consulte "[Renomear um branch](/github/administering-a-repository/renaming-a-branch).
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index e42e96d394..ab3d5d1b20 100644
--- a/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -26,7 +26,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti
 
 {% note %}
 
-**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
+**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. Para obter mais informações, consulte "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" ou {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
 
 {% endnote %}
 
@@ -47,7 +47,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti
 
 {% note %}
 
-**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. Para obter mais informações, consulte "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" ou {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
 
 {% endif %}
 
@@ -82,3 +82,25 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Definir as permissões do `GITHUB_TOKEN` para o seu repositório
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+As permissões padrão também podem ser configuradas nas configurações da organização. Se o padrão mais restrito foi selecionado nas configurações da organização, a mesma opção será selecionada automaticamente nas configurações do repositório e a opção permissiva estará desabilitada.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configurar as permissões padrão do `GITHUB_TOKEN`
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. Em **permissões do fluxo de trabalho**, escolha se você quer que o `GITHUB_TOKEN` tenha acesso de leitura e gravação para todos os escopos, ou apenas acesso de leitura para o escopo do </code>conteúdo.
+<img src="/assets/images/help/settings/actions-workflow-permissions-repository.png" alt="Definir permissões do GITHUB_TOKEN para este repositório" /></p></li>
+<li><p spaces-before="0">Clique em <strong x-id="1">Salvar</strong> para aplicar as configurações.
+</p>
+
+<p spaces-before="0">{% endif %}</p></li>
+</ol>
diff --git a/translations/pt-BR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index 07f6768efe..c977a31812 100644
--- a/translations/pt-BR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### Sobre arquivos FUNDING
 
-Para configurar o botão de patrocinador, edite um arquivo _FUNDING.yml_ na pasta `.github` do repositório, no branch padrão. É possível configurar o botão para incluir desenvolvedores patrocinados no {% data variables.product.prodname_sponsors %}, em plataformas de financiamento externas ou em uma URL de financiamento personalizado. Para obter mais informações a respeito do {% data variables.product.prodname_sponsors %}, consulte "[Sobre o GitHub Sponsors](/articles/about-github-sponsors)".
+Para configurar o botão de patrocinador, edite um arquivo _FUNDING.yml_ na pasta `.github` do repositório, no branch padrão. É possível configurar o botão para incluir desenvolvedores patrocinados no {% data variables.product.prodname_sponsors %}, em plataformas de financiamento externas ou em uma URL de financiamento personalizado. Para obter mais informações a respeito do {% data variables.product.prodname_sponsors %}, consulte "[Sobre o GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
 
 Você pode adicionar um nome de usuário, de pacote ou de projeto por plataforma de financiamento externa e até quatro URLs personalizadas. Você pode adicionar até quatro organizações ou desenvolvedores patrocinados no {% data variables.product.prodname_sponsors %}. Adicione cada plataforma em uma nova linha, usando a seguinte sintaxe:
 
@@ -76,5 +76,5 @@ Qualquer pessoa com permissões de administrador pode habilitar um botão de pat
 {% data reusables.files.propose_new_file %}
 
 ### Leia mais
-- "[Sobre {% data variables.product.prodname_sponsors %} para colaboradores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- "[Sobre {% data variables.product.prodname_sponsors %} para colaboradores de código aberto](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
 - "[Perguntas frequentes com a equipe do {% data variables.product.prodname_sponsors %}](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" no {% data variables.product.prodname_blog %}
diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
index b6be783cb7..5b5a5fa49c 100644
--- a/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -13,9 +13,9 @@ topics:
 
 ### Sobre o merge automático
 
-If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+Se você permitir uma merge automático para pull requests no seu repositório, as pessoas com permissões de gravação poderão configurar pull requests individuais no repositório para fazer merge automaticamente quando todos os requisitos de merge forem atendidos. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}Se alguém que não tiver permissão de gravação fizer push de um pull request que tenha merge automático habilitado, o merge automático será desabilitado para esse pull request. {% endif %}Para obter mais informações, consulte "[Fazer merge automático de um pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)".
 
-### Managing auto-merge
+### Gerenciar merge automático
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md
index 502a4d58e9..f421723ceb 100644
--- a/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/managing-releases-in-a-repository.md
@@ -69,7 +69,7 @@ Você pode escolher se
    
    {%- if currentVersion == "free-pro-team@latest" %}
 
-1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) 
+1. Opcionalmente, selecione **Criar uma discussão para esta versão** e, em seguida, selecione a **Categoria** no menu suspenso e clique em uma categoria para a discussão da versão. ![Caixa de seleção para criar uma discussão de versão e menu suspenso para escolher uma categoria](/assets/images/help/releases/create-release-discussion.png) 
    
    {%- endif %}
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index dca2509d5c..7b2969f37b 100644
--- a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -35,10 +35,11 @@ topics:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**.
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}O controle para "{% data variables.product.prodname_GH_advanced_security %}" fica desabilitado se você não tiver estações disponíveis na sua licença de {% data variables.product.prodname_GH_advanced_security %}.
-  ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. The control for "
+{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% if currentVersion == "free-pro-team@latest" %}
+  ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
 **Observação:** Se você desabilitar
 
@@ -46,11 +47,11 @@ topics:
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
 4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. Antes de poder habilitar"
-{% data variables.product.prodname_secret_scanning %}" para o seu repositório, você precisa habilitar {% data variables.product.prodname_GH_advanced_security %}.
+{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.
    ![Habilite ou desabilite {% data variables.product.prodname_GH_advanced_security %} ou {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index 98b505ae81..1025d62446 100644
--- a/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ Para obter mais informações, consulte "[Níveis de permissão para um reposit
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. Em "Gerenciar acesso", localize a equipe ou pessoa cujo acesso você deseja remover e clique em {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Ícone da lixeira para remover acesso](/assets/images/help/repository/manage-access-remove.png)
+4. Em "Gerenciar acesso", localize a equipe ou pessoa cujo acesso você deseja remover e clique em {% octicon "trash" aria-label="The trash icon" %}. ![ícone da lixeira para remover acesso](/assets/images/help/repository/manage-access-remove.png)
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
index 14149e9710..ba9059b2ec 100644
--- a/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Gerenciando a política de bifurcação para seu repositório
-intro: 'Você pode permitir ou impedir a bifurcação de um repositórios privado específico{% if currentVersion == "free-pro-team@latest" or currentversion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou interno{% endif %} pertencente a uma organização.'
+intro: 'Você pode permitir ou impedir a bifurcação de um repositórios privado específico{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} ou interno{% endif %} pertencente a uma organização.'
 redirect_from:
   - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization
   - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization
diff --git a/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md b/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md
index 36040d543e..74d3542fcb 100644
--- a/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/pt-BR/content/github/administering-a-repository/renaming-a-branch.md
@@ -13,9 +13,11 @@ topics:
 
 Você pode renomear um branch em um repositório em {% data variables.product.product_location %}. Para obter mais informações sobre os branches, consulte "[Sobre os branches](/github/collaborating-with-issues-and-pull-requests/about-branches)".
 
-When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments.
+Ao renomear um branch em {% data variables.product.product_location %}, todas as URLs que contiverem o nome do branch antigo serão automaticamente redirecionadas para a URL equivalente para o branch renomeado. Atualizam-se também as políticas de proteção de branch também, bem como o branch base para pull requests abertos (incluindo aqueles para bifurcações) e rascunhos de versões. Depois que a renomeação for concluída, {% data variables.product.prodname_dotcom %} fornecerá instruções na página inicial do repositório direcionando os colaboradores para atualizar seus ambientes do Git locais.
 
-Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
+Embora as URLs do arquivo sejam automaticamente redirecionadas, as URLs do arquivo não processado não são redirecionadas. Além disso, {% data variables.product.prodname_dotcom %} não realiza nenhum redirecionamento se os usuários executarem um `git pull` para o nome do branch anterior.
+
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
 
 ### Renomear um branch
 
@@ -35,4 +37,10 @@ A partir do clone local do repositório em um computador, execute os seguintes c
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+Opcionalmente, execute o comando a seguir para remover as referências de rastreamento para o nome do branch antigo.
+```
+$ git remote prune origin
 ```
diff --git a/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md
index da13475962..ffbe780b86 100644
--- a/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md
@@ -18,7 +18,7 @@ Quando você renomear um repositório, todas as informações existentes, com ex
 * Estrelas
 * Seguidores
 
-For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Para obter mais informações sobre sites de projeto, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Além do redirecionamento do tráfego da web, todas as operações `git clone`, `git fetch` ou `git push` direcionadas ao local antigo continuarão a funcionar como se tivessem sido criadas no novo local. No entanto, para reduzir a confusão, recomendamos que a atualização de quaisquer clones locais existentes apontem para a nova URL do repositório. Você pode fazer isso usando o `git remote` na linha de comando:
 
@@ -26,7 +26,7 @@ Além do redirecionamento do tráfego da web, todas as operações `git clone`,
 $ git remote set-url origin <em>new_url</em>
 ```
 
-For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 {% if currentVersion == "free-pro-team@latest" %}
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/pt-BR/content/github/administering-a-repository/restoring-a-deleted-repository.md
index b1e126979d..c8425db51a 100644
--- a/translations/pt-BR/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -31,9 +31,9 @@ Restaurar um repositório não vai restaurar anexos de versão nem permissões d
 
 ### Restaurar um repositório excluído que pertencia a uma organização
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/pt-BR/content/github/administering-a-repository/transferring-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/transferring-a-repository.md
index 54c700092a..5a956fdff1 100644
--- a/translations/pt-BR/content/github/administering-a-repository/transferring-a-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/transferring-a-repository.md
@@ -48,7 +48,7 @@ Quando você transfere um repositório, também são transferidos problemas, pul
   $ git remote set-url origin <em>new_url</em>
   ```
 
-For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 #### Transferências de repositório e organizações
 
diff --git a/translations/pt-BR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index 1e25039eda..995e7d0ec5 100644
--- a/translations/pt-BR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/pt-BR/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ Também é possível ver informações de implantação na guia "Conversation" (
 ### Exibir o painel de implantações
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Acima da lista de arquivos, clique em **Environments** (Ambientes). ![Ambientes na parte superior da página do repositório](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### Leia mais
  - "[Sobre pull requests](/articles/about-pull-requests)"
diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..a0c9a411b9
--- /dev/null
+++ b/translations/pt-BR/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+Para hospedar imagens, o {% data variables.product.product_name %} usa o [Camo do projeto de código aberto](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. A URL começa `https://<subdomain>.githubusercontent.com/`, com subdomínios diferentes dependendo de como você fez o upload da imagem.
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Solucionar problemas com o Camo
+
+As imagens que são processadas por meio do Camo raramente não aparecem no {% data variables.product.prodname_dotcom %}. Veja a seguir algumas etapas que podem ser seguidas para determinar onde está o problema.
+
+{% windows %}
+
+{% tip %}
+
+Os usuários do Windows precisam usar o Git Powershell (que é instalado com o [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) ou baixar um [curl para Windows](http://curl.haxx.se/download.html).
+
+{% endtip %}
+
+{% endwindows %}
+
+#### Uma imagem não está sendo exibida
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Solicite os headers da imagem usando `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. Verifique o valor de `Content-Type`. Nesse caso, é `image/x-png`.
+4. Verifique o tipo de conteúdo em relação [à lista de tipos compatíveis com o Camo](https://github.com/atmos/camo/blob/master/mime-types.json).
+
+Se o tipo de conteúdo não for compatível com o Camo, você poderá tentar várias ações:
+  * Se tiver posse do servidor que está hospedando a imagem, modifique-o para que ele retorne um tipo de conteúdo correto para imagens.
+  * Se estiver usando um serviço externo para hospedar imagens, entre em contato com o suporte do serviço em questão.
+  * Faça uma pull request ao Camo a fim de adicionar seu tipo de conteúdo à lista.
+
+#### Uma imagem que foi alterada recentemente não está atualizando
+
+Se você alterou uma imagem recentemente e ela está sendo exibida no navegador, mas não no {% data variables.product.prodname_dotcom %}, tente redefinir o cache da imagem.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Solicite os headers da imagem usando `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+Verifique o valor de `Cache-Control`. Neste exemplo, não há `Cache-Contro`. Nesse caso:
+  * Se tiver posse do servidor que está hospedando a imagem, modifique-o para que ele retorne um `Cache-Control` de `no-cache` para imagens.
+  * Se estiver usando um serviço externo para hospedar imagens, entre em contato com o suporte do serviço em questão.
+
+ Se `Cache-Control` *estiver * definido como `no-cache`, entre em contato com {% data variables.contact.contact_support %} ou pesquise no {% data variables.contact.community_support_forum %}.
+
+#### Remover uma imagem do cache do Camo
+
+A limpeza do cache força os usuários do {% data variables.product.prodname_dotcom %} a solicitar novamente a imagem. Portanto, você deve usá-la bem moderadamente e somente no caso em que as etapas acima não funcionarem.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Limpe a imagem usando `curl-X PURGE` na URL do Camo.
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### Exibir imagens em redes privadas
+
+Se uma imagem estiver sendo fornecida por uma rede privada ou um servidor que exige autenticação, ela não poderá ser exibida pelo {% data variables.product.prodname_dotcom %}. Na verdade, a imagem não pode ser exibida pelos usuários sem que eles façam login no servidor.
+
+Para corrigir isso, mova a imagem para um serviço que esteja disponível publicamente.
+
+### Leia mais
+
+- "[Retransmitir imagens do usuário](https://github.com/blog/1766-proxying-user-images)" em {% data variables.product.prodname_blog %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md
index 8a3f1c55e2..88f688f354 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md
@@ -54,7 +54,7 @@ Você pode efetuar a autenticação com a API de diferentes formas.
 
 ### Efetuando a autenticação com a linha de comando
 
-Você pode acessar repositórios no {% data variables.product.product_name %} pela linha de comando de duas maneiras, HTTPS e SSH. Ambos têm uma maneira diferente de efetuar a autenticação. O método de autenticação é determinado com base na escolha de uma URL remota de HTTPS ou SSH quando você clonar o repositório. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+Você pode acessar repositórios no {% data variables.product.product_name %} pela linha de comando de duas maneiras, HTTPS e SSH. Ambos têm uma maneira diferente de efetuar a autenticação. O método de autenticação é determinado com base na escolha de uma URL remota de HTTPS ou SSH quando você clonar o repositório. Para obter mais informações sobre qual maneira acessar, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
 * Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de HTTPS, mesmo que você esteja atrás de um firewall ou proxy. Sempre que você usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você insira suas credenciais para efetuar a autenticação com {% data variables.product.product_name %}, a não ser que você os armazene com um [auxiliar de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git). {% data reusables.user_settings.password-authentication-deprecation %}
 
@@ -66,17 +66,17 @@ Você pode acessar repositórios no {% data variables.product.product_name %} pe
 
 
 
-### {% data variables.product.company_short %}'s token formats
+### Formatos de token de {% data variables.product.company_short %}
 
-{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type.
+{% data variables.product.company_short %} emite tokens que começam com um prefixo para indicar o tipo do token.
 
-| Token type                                                                      | Prefix | Mais informações                                                                                                                                                  |
-|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Token de acesso de pessoal                                                      | `ghp_` | "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)"                                                         |
-| OAuth access token                                                              | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)"                                                       |
-| User-to-server token for a {% data variables.product.prodname_github_app %}   | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
-| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)"   |
-| Refresh token for a {% data variables.product.prodname_github_app %}          | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)"                                                             |
+| Tipo de token                                                                             | Prefixo | Mais informações                                                                                                                                                |
+|:----------------------------------------------------------------------------------------- |:------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Token de acesso de pessoal                                                                | `ghp_`  | "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)"                                                       |
+| Token de acesso do OAuth                                                                  | `gho_`  | "[Autorizar {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)"                                                       |
+| Token de usuário para servidor para um {% data variables.product.prodname_github_app %} | `ghu_`  | "[Identificar e autorizar usuários em {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
+| Token de servidor para usuário para {% data variables.product.prodname_github_app %}    | `ghs_`  | "[Autenticar com {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)"      |
+| Atualizar token para um {% data variables.product.prodname_github_app %}                | `ghr_`  | "[Atualizar tokens de acesso do usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)"                                               |
 
 
 {% endif %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
index 2df103f8d2..8b942c74b8 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
@@ -51,5 +51,5 @@ Após o proprietário de uma empresa ou organização habilitar ou aplicar o SSO
 
 ### Leia mais
 
-{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}- "[Sobre identidade e gerenciamento de acesso com logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
 {% if currentVersion == "github-ae@latest" %}- "[Sobre identidade e gerenciamento de acesso para a sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md
index 11b729bde8..951d616526 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre a verificação de assinatura de commit
-intro: 'Ao usar GPG ou S/MIME, você pode assinar tags e commits localmente. Esses commits ou tags são marcados como verificados no {% data variables.product.product_name %} para que outras pessoas tenham a segurança de que as alterações vêm de uma fonte confiável.'
+intro: 'Ao usar GPG ou S/MIME, você pode assinar tags e commits localmente. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures/
   - /articles/about-gpg/
@@ -16,15 +16,35 @@ topics:
 
 ### Sobre a verificação de assinatura de commit
 
-Você pode assinar commits e tags localmente para que outras pessoas possam verificar se seu trabalho tem origem em uma fonte confiável. Se um commit ou uma tag tiver uma assinatura GPG ou S/MIME que possa ser verificada de maneira criptográfica, o {% data variables.product.product_name %} marcará o commit ou tag como verificado.
+You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% if currentVersion == "free-pro-team@latest" %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
 
 ![Commit verificado](/assets/images/help/commits/verified-commit.png)
 
-Se um commit ou uma tag tiver uma assinatura que não possa ser verificada, o {% data variables.product.product_name %} marcará o commit ou a tag como não verificado(a).
+{% if currentVersion == "free-pro-team@latest" %}
+Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
 
-Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits)".
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
 
-Você pode conferir o status de verificação de seus commits ou tags assinados no {% data variables.product.product_name %} e ver por que as assinaturas de commit podem não ter sido verificadas. Para obter mais informações, consulte "[Conferir o status de verificação da assinatura de commit ou tag](/articles/checking-your-commit-and-tag-signature-verification-status)".
+#### Default statuses
+
+| Status                 | Descrição                                                         |
+| ---------------------- | ----------------------------------------------------------------- |
+| **Verificado**         | The commit is signed and the signature was successfully verified. |
+| **Unverified**         | The commit is signed but the signature could not be verified.     |
+| No verification status | The commit is not signed.                                         |
+
+#### Statuses with vigilant mode enabled
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+If a commit or tag has a signature that can't be verified,
+{% data variables.product.product_name %} marks the commit or tag "Unverified."
+{% endif %}
+
+Os administradores do repositório podem impor a assinatura de commit obrigatória em um branch para bloquear todos os commits que não estejam assinados e verificados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits)."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} usará automaticamente o GPG para assinar os commits que você fizer usando a interface web do {% data variables.product.product_name %} exceto quando você faz combinação por squash e mescla um pull request do qual você não é o autor. Opcionalmente, você pode escolher que {% data variables.product.product_name %} assine os commits que você fizer em {% data variables.product.prodname_codespaces %}. Commits assinados por {% data variables.product.product_name %} terão um status de verificado em {% data variables.product.product_name %}. É possível verificar a assinatura localmente usando a chave pública disponível em https://github.com/web-flow.gpg. Para obter mais informações sobre como habilitar a verificação de GPG para os seus códigos, consulte "[Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md b/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md
index 7bbdad428a..06a0adeb88 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-Ao configurar o SSH, você vai [gerar uma chave SSH e adicioná-la ao ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) e, em seguida, [adicionar a chave à sua conta do {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account). Adicionar a chave SSH ao ssh-agent garante que sua chave SSH tenha uma camada extra de segurança por meio do uso de uma frase secreta. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/articles/working-with-ssh-key-passphrases)".
+When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
-{% if currentVersion == "free-pro-team@latest" %}Para usar a sua chave SSH com um repositório pertencente a uma organização que usa o login único SAML, primeiro você precisará autorizá-lo. Para obter mais informações, consulte "[Autorizar uma chave SSH para uso com logon único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %}
+You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)".
 
-É recomendável [revisar regularmente sua lista de chaves SSH](/articles/reviewing-your-ssh-keys) e revogar qualquer uma que esteja inválida ou tenha sido comprometida.
+{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. Para obter mais informações, consulte "[Autorizar uma chave SSH para uso com logon único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %}
+
+To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. Para obter mais informações, consulte "[Revisar as chaves SSH](/github/authenticating-to-github/reviewing-your-ssh-keys)".
 
 {% if currentVersion == "free-pro-team@latest" %}
 Se você não usou a sua chave SSH por um ano,
@@ -28,8 +30,4 @@ Se for integrante de uma organização que fornece certificados SSH, você poder
 
 - "[Verificar se há chaves SSH existentes](/articles/checking-for-existing-ssh-keys)"
 - "[Testar a conexão SSH](/articles/testing-your-ssh-connection)"
-- "[Trabalhar com frases secretas da chave SSH](/articles/working-with-ssh-key-passphrases)"
 - "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)"
-{%- if currentVersion == "free-pro-team@latest" %}
-- "[Autorizar uma chave SSH para uso com logon único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"
-{%- endif %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index 94d17980e9..dcb2815ccb 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also add an SSH key using the {% data variables.product.prodname_cli %}. For more information, see "[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. Copie a chave pública SSH para a sua área de transferência.
@@ -80,8 +88,9 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product
   Se o seu arquivo de chave pública SSH tiver um nome diferente do código de exemplo, modifique o nome do arquivo para corresponder à sua configuração atual. Ao copiar sua chave, não adicione novas linhas nem espaços em branco.
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
-  # Baixa e instala xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
+  # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
 
   $ xclip -selection clipboard &lt; ~/.ssh/id_ed25519.pub
   # Copies the contents of the id_ed25519.pub file to your clipboard
diff --git a/translations/pt-BR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/pt-BR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index 32c09bbee5..12b2aa5d67 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**Observação:** a GPG não vem instalada por padrão no OS X nem no Windows. Para instalar ferramentas de linha de comando GPG, consulte a [página de download da GnuPG](https://www.gnupg.org/download/).
+**Note:** GPG does not come installed by default on macOS or Windows. Para instalar ferramentas de linha de comando GPG, consulte a [página de download da GnuPG](https://www.gnupg.org/download/).
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/pt-BR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index b21404834b..9e293eda97 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %}, navegue até o seu pull request.
 {% data reusables.repositories.review-pr-commits %}
-3. Ao lado do hash de commit abreviado do seu commit, há uma caixa que mostra se a assinatura do commit foi verificada ou não. ![Commit assinado](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. Para exibir informações mais detalhadas sobre a assinatura do commit, clique em **Verified** (Verificada) ou **Unverified** (Não verificada). ![Commit assinado verificado](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-Se a assinatura do commit não estiver verificada, você poderá saber mais sobre o por quê clicando na caixa **Unverified** (Não verificada). ![Commit assinado não verificado](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![Commit assinado](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. To view more detailed information about the commit signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Commit assinado verificado](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### Confirmar o status de verificação da assinatura da tag
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. Na parte superior da página Versões, clique em **Tags**. ![Página de tags](/assets/images/help/releases/tags-list.png)
-3. Ao lado da descrição da tag, há uma caixa que mostra se a assinatura da tag está verificada ou não verificada. ![assinatura de tag verificada](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. Para exibir informações mais detalhadas sobre a assinatura da tag, clique em **Verified** (Verificada) ou **Unverified** (Não verificada). Se a assinatura da tag não estiver verificada, você poderá saber mais sobre o por quê clicando na caixa **Unverified** (Não verificada). ![Tag assinada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. Next to your tag description, there is a box that shows whether your tag signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![assinatura de tag verificada](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. To view more detailed information about the tag signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Tag assinada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md
index d50bad65f3..b20f6399d6 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas para autenticação no {% data variables.product.product_name %} ao usar a [API do GitHub](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) ou a [linha de comando](#using-a-token-on-the-command-line).
 
-{% if currentVersion == "free-pro-team@latest" %}Se você deseja usar um PAT para acessar recursos pertencentes a uma organização que usa SAML SSO, você deve autorizar o PAT. Para mais informações consulte "[Sobre autenticação com logon único SAML](/articles/about-authentication-with-saml-single-sign-on)" e "[Autorizando um token de acesso pessoal para uso com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}Se você deseja usar um PAT para acessar recursos pertencentes a uma organização que usa SAML SSO, você deve autorizar o PAT. Para mais informações consulte "[Sobre autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" e "[Autorizando um token de acesso pessoal para uso com logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### Criar um token
 
-{% if currentVersion == "free-pro-team@latest" %}1. [Verifique seu endereço de e-mail](/articles/verifying-your-email-address), caso ainda não o tenha verificado.{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. [Verifique seu endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address), caso ainda não o tenha verificado.{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -37,21 +37,21 @@ Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas par
    {% endif %}
 7. Clique em **Generate token** (Gerar token). ![Botão Generate token (Gerar token)](/assets/images/help/settings/generate_token.png)
 8. Clique em
-{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again.
+{% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar o token para sua área de transferência. Por motivos de segurança, ao sair da página, você não poderá ver o token novamente.
    {% if currentVersion == "free-pro-team@latest" %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![Token recém-criado](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png)
+   ![Token recém-criado](/assets/images/help/settings/personal_access_tokens_ghe.png)
    {% else %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
+   ![Token recém-criado](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **Aviso:** trate seus tokens como senhas e mantenha-os em segredo. Ao trabalhar com a API, use tokens como variáveis de ambiente em vez de embuti-los em código nos seus programas.
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. Para usar seu token a fim de se autenticar em uma organização que usa SAML SSO, [autorize o token para uso com uma organização de logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. Para usar seu token a fim de se autenticar em uma organização que usa SAML SSO, [autorize o token para uso com uma organização de logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
 
 ### Usar um token na linha de comando
 
@@ -59,7 +59,7 @@ Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas par
 
 Os tokens de acesso pessoais podem ser usados apenas para operações Git HTTPS. Se seu repositório usar uma URL remote SSH, você precisará [alternar o remote de SSH para HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
 
-Se não for solicitado a informar seu nome de usuário e a senha, suas credenciais poderão ser armazenadas em cache no seu computador. Você pode [atualizar suas credenciais no keychain](/articles/updating-credentials-from-the-osx-keychain) para substituir a senha antiga pelo token.
+Se não for solicitado a informar seu nome de usuário e a senha, suas credenciais poderão ser armazenadas em cache no seu computador. Você pode [atualizar suas credenciais no keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) para substituir a senha antiga pelo token.
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/pt-BR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..47895a80cd
--- /dev/null
+++ b/translations/pt-BR/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
+
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### Enabling vigilant mode
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/pt-BR/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/pt-BR/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..aa501185bb
--- /dev/null
+++ b/translations/pt-BR/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### Pré-requisitos
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### Resolver o problema
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. Abra o terminal.
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)".
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index bec8d0f8ba..dc7a8a32e4 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-Se você ainda não tem uma chave SSH, você deve [gerar uma nova chave SSH](#generating-a-new-ssh-key). Caso não tenha certeza de que já tem uma chave SSH, procure por [chaves existentes](/articles/checking-for-existing-ssh-keys).
+### About SSH key generation
 
-Caso não queira reinserir sua frase secreta cada vez que usa a chave SSH, é possível [adicionar sua chave ao SSH agent](#adding-your-ssh-key-to-the-ssh-agent), que poderá gerenciar suas chaves SSH e lembrar sua frase secreta.
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
 
 ### Gerar uma nova chave SSH
 
@@ -62,7 +69,7 @@ Caso não queira reinserir sua frase secreta cada vez que usa a chave SSH, é po
 
   {% endlinux %}
 
-4. Digite uma frase secreta segura no prompt. Para obter mais informações, consulte ["Trabalhar com frases secretas da chave SSH"](/articles/working-with-ssh-key-passphrases).
+4. Digite uma frase secreta segura no prompt. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ Caso não queira reinserir sua frase secreta cada vez que usa a chave SSH, é po
 
 ### Adicionar sua chave SSH ao ssh-agent
 
-Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, você deve ter [verificado a existência de chaves SSH](/articles/checking-for-existing-ssh-keys) e [gerado uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). <span class="platform-mac">Ao adicionar sua chave SSH ao agent, use o comando padrão "ssh-add" do macOS, e não um aplicativo instalado por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) ou qualquer outra fonte externa.</span>
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">Ao adicionar sua chave SSH ao agent, use o comando padrão "ssh-add" do macOS, e não um aplicativo instalado por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) ou qualquer outra fonte externa.</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v
       $ touch ~/.ssh/config
       ```
 
-    * Abre o seu arquivo `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` se você não estiver usando o local e nome padrão para a sua chave `id_ed25519`.
+    * Abra seu arquivo `~/.ssh/config` e modifique o arquivo para que contenha as seguintes linhas. Se o seu arquivo de chave SSH tiver um nome ou caminho diferente do exemplo de código, modifique o nome ou o caminho para corresponder à sua configuração atual.
 
       ```
       Host *
@@ -106,6 +113,25 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **Note:** If you see an error like this
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      add an additional config line to your `Host *` section:
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. Adicione sua chave SSH privada ao ssh-agent e armazene sua frase secreta no keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v
 
   {% endnote %}
 
-4. [Adicione a chave SSH à sua conta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account).
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v
 2. Adicione sua chave SSH privada ao ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Adicione a chave SSH à sua conta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ Antes de adicionar uma nova chave SSH ao ssh-agent para gerenciar suas chaves, v
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  In some Linux environments, you need root access to run the command:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. Adicione sua chave SSH privada ao ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Adicione a chave SSH à sua conta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endif %}
+
 ### Leia mais
 
 - "[Sobre SSH](/articles/about-ssh)"
diff --git a/translations/pt-BR/content/github/authenticating-to-github/index.md b/translations/pt-BR/content/github/authenticating-to-github/index.md
index 6d04aeac57..59715c5a62 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/index.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/index.md
@@ -1,7 +1,7 @@
 ---
-title: Authenticating to GitHub
-shortTitle: Authentication
-intro: 'Keep your account and data secure with features like {% if currentVersion != "github-ae@latest" %}two-factor authentication, {% endif %}SSH{% if currentVersion != "github-ae@latest" %},{% endif %} and commit signature verification.'
+title: Autenticar com o GitHub
+shortTitle: Autenticação
+intro: 'Mantenha sua conta e dados protegidos com recursos como {% if currentVersion != "github-ae@latest" %}autenticação de dois fatores, {% endif %}SSH{% if currentVersion ! "github-ae@latest" %},{% endif %} e verificação de assinatura do commit.'
 redirect_from:
   - /categories/56/articles/
   - /categories/ssh/
@@ -26,7 +26,7 @@ topics:
 ---
 
 
-### Table of Contents
+### Índice
 
 {% topic_link_in_list /keeping-your-account-and-data-secure %}
     {% link_in_list /about-authentication-to-github %}
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/pt-BR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 774359d92a..ce6a9bc5f6 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ Você pode usar as suas credenciais de autenticação de dois fatores ou os cód
 5. Em "Única senha", digite a senha temporária do endereço e-mail de recuperação {% data variables.product.prodname_dotcom %} enviada. ![Campo para a senha de uso único](/assets/images/help/2fa/one-time-password-field.png)
 6. Clique **Verificar endereço de e-mail**.
 7. Escolha um fator de verificação alternativo.
-    - Se você usou seu dispositivo atual para acessar essa conta anteriormente e gostaria de usar o dispositivo para verificação, clique em **Verificar este dispositivo**.
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - 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**. ![Botões de verificação alternativa](/assets/images/help/2fa/alt-verifications.png)
 8. Um integrante do {% data variables.contact.github_support %} irá rever a sua solicitação e o seu endereço de e-mail de 3 a 5 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.
diff --git a/translations/pt-BR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/pt-BR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index 4aab438ab7..a292a6b62b 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -15,7 +15,7 @@ topics:
 
 {% mac %}
 
-Se a [ frase secreta da SSH tiver sido configurada com o app Keychain (Chaves) do OS X](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), talvez você consiga recuperá-la.
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
 
 1. Procure o app **Keychain Access** (Acesso a keychain) no Finder (Localizador). ![Barra de pesquisa do Spotlight](/assets/images/help/setup/keychain-access.png)
 2. No Acesso às Chaves, pesquise **SSH**.
diff --git a/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md
index 78bfaff509..5cf6fd1463 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/reviewing-your-security-log.md
@@ -38,23 +38,23 @@ O log de segurança lista todas as ações realizadas nos últimos 90 dias{% if
 
 Os eventos listados no seu registro de segurança são acionados por suas ações. As ações são agrupadas nas seguintes categorias:
 
-| Categoria                                                                              | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
-| [`account_recovery_token`](#account_recovery_token-category-actions)                   | Contém todas as atividade relacionadas a [adicionar um token de recuperação](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                 |
-| [`cobrança`](#billing-category-actions)                                                | Contém todas as atividades relacionadas às suas informações de cobrança.                                                                                                                                                                                                                                                                                                                                                                        |
-| [`espaços de código`](#codespaces-category-actions)                                    | Contém todas as atividades relacionadas a {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)".                                                                                                                                                                                     |
-| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contém todas as atividades relacionadas à assinatura do Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                         |
+| Categoria                                                                              | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| [`account_recovery_token`](#account_recovery_token-category-actions)                   | Contém todas as atividade relacionadas a [adicionar um token de recuperação](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                                                          |
+| [`cobrança`](#billing-category-actions)                                                | Contém todas as atividades relacionadas às suas informações de cobrança.                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| [`espaços de código`](#codespaces-category-actions)                                    | Contém todas as atividades relacionadas a {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)".                                                                                                                                                                                                                              |
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contém todas as atividades relacionadas à assinatura do Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                                                                  |
 | [`marketplace_listing`](#marketplace_listing-category-actions)                         | Contém todas as atividades relacionadas aos aplicativos listados no {% data variables.product.prodname_marketplace %}.{% endif %}
 | [`oauth_access`](#oauth_access-category-actions)                                       | Contém todas as atividades relacionadas a [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) com as quais você se conectou.{% if currentVersion == "free-pro-team@latest" %}
 | [`payment_method`](#payment_method-category-actions)                                   | Contém todas as atividades relacionadas ao pagamento da sua assinatura do {% data variables.product.prodname_dotcom %}.{% endif %}
-| [`profile_picture`](#profile_picture-category-actions)                                 | Contém todas as atividades relacionadas à imagem do seu perfil.                                                                                                                                                                                                                                                                                                                                                                                 |
-| [`project`](#project-category-actions)                                                 | Contém todas as atividades relacionadas aos quadros de projeto.                                                                                                                                                                                                                                                                                                                                                                                 |
-| [`public_key`](#public_key-category-actions)                                           | Contém todas as atividades relacionadas às [chaves SSH públicas](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                                        |
+| [`profile_picture`](#profile_picture-category-actions)                                 | Contém todas as atividades relacionadas à imagem do seu perfil.                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| [`project`](#project-category-actions)                                                 | Contém todas as atividades relacionadas aos quadros de projeto.                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| [`public_key`](#public_key-category-actions)                                           | Contém todas as atividades relacionadas às [chaves SSH públicas](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                                                                                 |
 | [`repo`](#repo-category-actions)                                                       | Contém todas as atividades relacionadas aos repositórios que você possui.{% if currentVersion == "free-pro-team@latest" %}
-| [`sponsors`](#sponsors-category-actions)                                               | Contém todos os eventos relacionados a {% data variables.product.prodname_sponsors %} e botões de patrocinador (veja "[Sobre {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" e "[ Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+| [`sponsors`](#sponsors-category-actions)                                               | Contém todos os eventos relacionados a {% data variables.product.prodname_sponsors %} e botões de patrocinador (consulte "[Sobre {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" e "[ Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 | [`equipe`](#team-category-actions)                                                     | Contém todas as atividades relacionadas a equipes das quais você faz parte.{% endif %}{% if currentVersion != "github-ae@latest" %}
 | [`two_factor_authentication`](#two_factor_authentication-category-actions)             | Contem todas as atividades relacionadas a [autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
-| [`usuário`](#user-category-actions)                                                    | Contém todas as atividades relacionadas à sua conta.                                                                                                                                                                                                                                                                                                                                                                                            |
+| [`usuário`](#user-category-actions)                                                    | Contém todas as atividades relacionadas à sua conta.                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -90,6 +90,10 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev
 
 | Ação                                 | Descrição                                                                                                                                                                                                                                    |
 | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                             | Acionada ao [criar codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                               |
+| `resume`                             | Acionada ao retomar um codespace suspenso.                                                                                                                                                                                                   |
+| `delete`                             | Acionada quando você [exclui um codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                  |
+| `manage_access_and_security`         | Acionada quando você atualiza [os repositórios aos quais um codespace tem acesso](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                    |
 | `trusted_repositories_access_update` | Acionada quando você altera o [acesso e as configurações de segurança da sua conta de usuário para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). |
 
 #### ações de categoria de `marketplace_agreement_signature`
@@ -181,22 +185,24 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev
 {% if currentVersion == "free-pro-team@latest" %}
 #### ações de categoria de `patrocinadores`
 
-| Ação                                          | Descrição                                                                                                                                                                                                                                                                                                                                        |
-| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`             | Acionada quando você habilita ou desabilita um botão de patrocinador no repositório (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                  |
-| `repo_funding_links_file_action`              | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                                                |
-| `sponsor_sponsorship_cancel`                  | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                                  |
-| `sponsor_sponsorship_create`                  | Acionada quando você patrocina uma conta (veja "[Patrocinar um contribuidor de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                                         |
-| `sponsor_sponsorship_preference_change`       | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/articles/managing-your-sponsorship)")                                                                                                                                                                   |
-| `sponsor_sponsorship_tier_change`             | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)")                                                                                                                                |
-| `sponsored_developer_approve`                 | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (ver "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                    |
-| `sponsored_developer_create`                  | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                      |
-| `sponsored_developer_profile_update`          | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                           |
-| `sponsored_developer_request_approval`        | Acionada quando você enviar seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")             |
-| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                                                    |
-| `sponsored_developer_update_newsletter_send`  | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/articles/contacting-your-sponsors)")                                                                                                                                                                              |
-| `waitlist_invite_sponsored_developer`         | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} a partir da lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
-| `waitlist_join`                               | Acionada quando você se junta à lista de espera para tornar-se um desenvolvedor patrocinado (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                               |
+| Ação                                          | Descrição                                                                                                                                                                                                                                                                                                                               |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Acionada quando você habilita ou desabilita os valores personalizados ou quando altera os valores sugeridos (consulte "[Gerenciar as suas camadas de patrocínio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                   |
+| `repo_funding_links_file_action`              | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                                       |
+| `sponsor_sponsorship_cancel`                  | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                         |
+| `sponsor_sponsorship_create`                  | Acionada quando você patrocina uma conta (consulte "[Patrocinar um contribuidor de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                                |
+| `sponsor_sponsorship_preference_change`       | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                                      |
+| `sponsor_sponsorship_tier_change`             | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)")                                                                                                                       |
+| `sponsored_developer_approve`                 | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (consulte "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                               |
+| `sponsored_developer_create`                  | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                      |
+| `sponsored_developer_disable`                 | Acionada quando sua conta {% data variables.product.prodname_sponsors %} está desabilitado                                                                                                                                                                                                                                              |
+| `sponsored_developer_redraft`                 | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é retornada ao estado de rascunho a partir do estado aprovado                                                                                                                                                                                               |
+| `sponsored_developer_profile_update`          | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                           |
+| `sponsored_developer_request_approval`        | Acionada quando você enviar seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")             |
+| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de uma camada de patrocínio (consulte "[Gerenciar suas camadas de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                                       |
+| `sponsored_developer_update_newsletter_send`  | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                      |
+| `waitlist_invite_sponsored_developer`         | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} a partir da lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
+| `waitlist_join`                               | Acionada quando você se junta à lista de espera para tornar-se um desenvolvedor patrocinado (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                               |
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -250,7 +256,7 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev
 | `login`                                                                                                                                                                                                                                     | Acionada quando você efetua o login em {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 
 
-`mandatory_message_viewed`  | Acionada quando você visualiza uma mensagem obrigatória (consulte "[Personalizar mensagens de usuário](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obter detalhes) e ├{% endif %}➲ ├ `falhou_login` | Acionada quando você não efetuou o login com sucesso. | `remove_email` | Acionado quando você remove um endereço de e-mail. | `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} | `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
+`mandatory_message_viewed`  | Acionada quando você visualiza uma mensagem obrigatória (consulte "[Personalizar mensagens de usuário](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obter detalhes) e ├{% endif %}➲ ├ `falhou_login` | Acionada quando você não efetuou o login com sucesso. | `remove_email` | Acionado quando você remove um endereço de e-mail. | `rename` | Acionado quando você renomeia a sua conta.{% if currentVersion == "free-pro-team@latest" %} | `report_content` | Acionado quando você [relata um problema ou um pull request ou um comentário em um problema, pull request ou commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Acionado quando você [divulga contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | Acionado quando {% data variables.product.product_name %} solicita [o seu código de autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication).{% endif %}
 
 #### ações de categoria `user_status`
 
@@ -258,4 +264,3 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev
 | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `update`  | Acionada quando você configura ou altera o status no perfil. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)". |
 | `destroy` | Acionada quando você remove o status no perfil.                                                                                                                                      |
-
diff --git a/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
index 4cf1587e84..ab139f1854 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/telling-git-about-your-signing-key.md
@@ -31,12 +31,12 @@ Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usad
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file:
+1. Se você não estiver usando o pacote GPG, execute o comando a seguir no shell do `zsh` para adicionar a chave GPG ao seu arquivo `.zshrc`, se ele existir, ou seu arquivo `.zprofile`:
   ```shell
   $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi
   ```
-  Alternatively, if you use the `bash` shell, run this command:
+  Como alternativa, se você usar o shall de `bash`, execute este comando:
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
@@ -93,7 +93,7 @@ Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usad
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. To add your GPG key to your bash profile, run the following command:
+1. Para adicionar a sua chave GPG ao seu perfil bash, execute o seguinte comando:
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
diff --git a/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md
index ceaf019750..1d8be72cca 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Updating your GitHub access credentials
-intro: '{% data variables.product.product_name %} credentials include{% if currentVersion != "github-ae@latest" %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.'
+title: Atualizar credenciais de acesso do GitHub
+intro: 'As credenciais de {% data variables.product.product_name %} incluem{% if currentVersion != "github-ae@latest" %} não apenas sua senha, mas também{% endif %} os tokens de acesso, Chaves SSH e tokens do aplicativo da API que você usa para se comunicar com {% data variables.product.product_name %}. Se houver necessidade, você mesmo pode redefinir todas essas credenciais de acesso.'
 redirect_from:
   - /articles/rolling-your-credentials/
   - /articles/how-can-i-reset-my-password/
@@ -15,51 +15,49 @@ topics:
 ---
 
 {% if currentVersion != "github-ae@latest" %}
-### Requesting a new password
+### Solicitar uma nova senha
 
-1. To request a new password, visit {% if currentVersion == "free-pro-team@latest" %}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 personal {% data variables.product.product_name %} account, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.
-  ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png)
-3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder.
-4. After clicking on the link in your email, you'll be asked to enter a new password.
-  ![Password recovery box](/assets/images/help/settings/password_recovery_page.png)
+1. Para solicitar uma nova senha, acesse {% if currentVersion == "free-pro-team@latest" %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
+2. Digite o endereço de e-mail associado à sua conta pessoal do {% data variables.product.product_name %} e clique em **Send password reset email** (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. Depois de clicar no link contido no e-mail, você precisará digitar uma nova senha.![Caixa para recuperar senha](/assets/images/help/settings/password_recovery_page.png)
 
 {% tip %}
 
-To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/).
+Para evitar que você perca a senha, sugerimos que você use um gerenciador de senhas seguras, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), ou [Keeper](https://keepersecurity.com/).
 
 {% endtip %}
 
-### Changing an existing password
+### Alterar uma senha existente
 
 {% data reusables.repositories.blocked-passwords %}
 
-1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}.
+1. {% data variables.product.signin_link %} para o {% data variables.product.product_name %}.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)"
-5. Click **Update password**.
+4. Em "Change password" (Alterar senha), insira a senha antiga, digite uma nova senha forte e confirme a nova senha. Consulte "[Criar uma senha forte](/articles/creating-a-strong-password)" para obter ajuda sobre esse assunto.
+5. Clique em **Update password** (Atualizar senha).
 
 {% tip %}
 
-For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details.
+Para maior segurança, além de alterar a senha, habilite também a autenticação de dois fatores. Consulte [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication) para ver mais detalhes.
 
 {% endtip %}
 {% endif %}
-### Updating your access tokens
+### Atualizar tokens de acesso
 
-See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Consulte "[Revisar integrações autorizadas](/articles/reviewing-your-authorized-integrations)" para ver instruções sobre como revisar e excluir tokens de acesso. Para gerar novos tokens de acesso, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
 
-### Updating your SSH keys
+### Atualizar chaves SSH
 
-See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)."
+Consulte "[Revisar as chaves SSH](/articles/reviewing-your-ssh-keys)" para ver instruções sobre como revisar e excluir chaves SSH. Para gerar e adicionar novas chaves SSH, consulte "[Gerar uma chave SSH](/articles/generating-an-ssh-key)".
 
-### Resetting API tokens
+### Redefinir tokens da API
 
-If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint.
+Se você tiver algum aplicativo registrado no {% data variables.product.product_name %}, talvez precise redefinir os tokens OAuth dele. Para obter mais informações, consulte o ponto de extremidade "[Redefinir uma autorização](/rest/reference/apps#reset-an-authorization)".
 
 {% if currentVersion != "github-ae@latest" %}
-### Preventing unauthorized access
+### Impedir acesso não autorizado
 
-For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)."
+Consulte "[Impedir acesso não autorizado](/articles/preventing-unauthorized-access)" para obter mais dicas sobre como proteger a conta e impedir acesso não autorizado.
 {% endif %}
diff --git a/translations/pt-BR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/pt-BR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index a6457fdbb4..64ef295b6c 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -1,6 +1,6 @@
 ---
 title: Usar SSH na porta HTTPS
-intro: 'Às vezes, os firewalls se recusam a permitir conexões SSH completamente.  If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port.  A maioria das regras de firewall deve permitir isso, mas o servidores proxy podem interferir.'
+intro: 'Às vezes, os firewalls se recusam a permitir conexões SSH completamente.  Se a usar [a clonagem de HTTPS com caching de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git) não for uma opção, você poderá tentar clonar usando uma conexão SSH feita por meio da porta HTTPS.  A maioria das regras de firewall deve permitir isso, mas o servidores proxy podem interferir.'
 redirect_from:
   - /articles/using-ssh-over-the-https-port
 versions:
@@ -11,7 +11,7 @@ topics:
 
 {% tip %}
 
-**Usuários do GitHub Enterprise**: não há suporte atualmente ao GitHub Enterprise via SSH na porta HTTPS.
+**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
 
 {% endtip %}
 
diff --git a/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index 522cb6d324..3c692ea578 100644
--- a/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/pt-BR/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -91,7 +91,7 @@ O processo do `ssh-agent` continuará sendo executado até você fazer logoff, d
 
 ### Salvar a frase secreta na keychain
 
-No OS X Leopard até o OS X El Capitan, estes arquivos padrão de chave privada são processados de forma automática:
+On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md b/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md
index 69f5f02501..392b66da6f 100644
--- a/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md
+++ b/translations/pt-BR/content/github/building-a-strong-community/creating-a-default-community-health-file.md
@@ -20,7 +20,7 @@ Você pode adicionar arquivos padrão de saúde da comunidade à raiz de um repo
 - a pasta `.github`
 - a pasta `docs`
 
-Por exemplo, qualquer pessoa que cria um problema ou uma pull request em um repositório público que não tem o próprio arquivo CONTRIBUTING verá um link para o arquivo CONTRIBUTING padrão. Se um repositório tiver arquivos na usa própria pasta `.github/ISSUE_TEMPLATE`{% if currentVersion == "free-pro-team@latest" or currentversion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}, incluindo modelos de problema ou um arquivo *config.yml*,{% endif %} nenhum conteúdo da pasta padrão `.github/ISSUE_TEMPLATE` será usado.
+Por exemplo, qualquer pessoa que cria um problema ou uma pull request em um repositório público que não tem o próprio arquivo CONTRIBUTING verá um link para o arquivo CONTRIBUTING padrão. Se um repositório tiver arquivos na usa própria pasta `.github/ISSUE_TEMPLATE`{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}, incluindo modelos de problema ou um arquivo *config.yml*,{% endif %} nenhum conteúdo da pasta padrão `.github/ISSUE_TEMPLATE` será usado.
 
 Os arquivos padrão não são incluídos em clones, pacotes ou downloads de repositórios individuais, pois eles são armazenados somente no repositório `.github`.
 
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index 322fa16b64..b28d4e4609 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre modelos de desenvolvimento colaborativo
-intro: O modo como você usa pull requests depende do tipo de modelo de desenvolvimento usado no projeto.
+intro: O modo como você usa pull requests depende do tipo de modelo de desenvolvimento usado no projeto. You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-Há dois tipos principais de modelo de desenvolvimento com os quais é possível usar pull requests. No *fork e pull model*, qualquer um pode bifurcar um repositório existente e fazer push das alterações em sua bifurcação pessoal. Você não precisa de permissão ao repositório de origem para fazer push em uma bifurcação de propriedade do usuário. As alterações podem ser enviadas por pull no repositório de origem pelo mantenedor do projeto. Ao abrir uma pull request propondo alterações a partir de sua bifurcação de propriedade de usuário para um branch no repositório de origem (upstream), você poderá permitir que qualquer pessoa com acesso push ao repositório upstream faça alterações na sua pull request.  Esse modelo é popular entre projetos de código aberto, pois ele reduz a resistência de novos contribuidores, além de permitir que as pessoas trabalhem de modo independente sem coordenação inicial.
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. Você não precisa de permissão ao repositório de origem para fazer push em uma bifurcação de propriedade do usuário. As alterações podem ser enviadas por pull no repositório de origem pelo mantenedor do projeto. Ao abrir uma pull request propondo alterações a partir de sua bifurcação de propriedade de usuário para um branch no repositório de origem (upstream), você poderá permitir que qualquer pessoa com acesso push ao repositório upstream faça alterações na sua pull request.  Esse modelo é popular entre projetos de código aberto, pois ele reduz a resistência de novos contribuidores, além de permitir que as pessoas trabalhem de modo independente sem coordenação inicial.
 
 {% tip %}
 
@@ -20,7 +22,9 @@ Há dois tipos principais de modelo de desenvolvimento com os quais é possível
 
 {% endtip %}
 
-No *modelo de repositório compartilhado*, os colaboradores recebem acesso push a um único repositório compartilhado e branches de tópico são criados quando alterações precisam ser feitas. As pull requests são úteis nesse modelo, uma vez que iniciam a revisão de código e a discussão geral sobre um conjunto de alterações antes que elas sofram merge no branch de desenvolvimento principal. Esse modelo é mais predominante em equipes e organizações pequenas que colaboram em projetos privados.
+### Shared repository model
+
+No modelo de repositório compartilhado, os colaboradores recebem acesso push a um único repositório compartilhado e branches de tópico são criados quando alterações precisam ser feitas. As pull requests são úteis nesse modelo, uma vez que iniciam a revisão de código e a discussão geral sobre um conjunto de alterações antes que elas sofram merge no branch de desenvolvimento principal. Esse modelo é mais predominante em equipes e organizações pequenas que colaboram em projetos privados.
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index 4f2ed93800..b80be006be 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -53,18 +53,18 @@ Quando um repositório é definido para solicitar verificações por pushes auto
 
 Para ignorar ou solicitar verificações para seu commit, adicione uma das seguintes linhas de trailer ao fim da mensagem do commit:
 
-- Para _ignorar verificações_ para um commit, digite a mensagem do commit e uma descrição breve e significativa das alterações. Após a descrição do commit, em vez de aspas de fechamento, adicione duas linhas vazias seguidas por `skip-checks: true`:
+- Para _ignorar verificações_ para um commit, digite a mensagem do commit e uma descrição breve e significativa das alterações. After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - Para _solicitar_ verificações para um commit, digite a mensagem do commit e uma descrição breve e significativa das alterações. Após a descrição do commit, em vez de aspas de fechamento, adicione duas linhas vazias seguidas por `request-checks: true`:
+- Para _solicitar_ verificações para um commit, digite a mensagem do commit e uma descrição breve e significativa das alterações. After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
index ab791c77d0..3a233c10ef 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
@@ -14,9 +14,9 @@ topics:
 
 Se você habilitar o merge automático para um pull request, este será mesclado automaticamente quando todas as revisões necessárias forem atendidas e as verificações de status forem aprovadas. O merge automático impede que você espere que os sejam atendidos para que você possa passar para outras tarefas.
 
-Antes de usar o merge automático com um pull request, o merge automático deve ser habilitado para o repositório. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
+Antes de usar o merge automático com um pull request, o merge automático deve ser habilitado para o repositório. Para obter mais informações, consulte "[Gerenciar merge automático para pull requests no seu repositório](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
 
-After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %}
+Depois que você ativar o merge automático para uma pull request, se alguém que não tiver permissões de gravação no repositório fizer push de novas alterações no branch principal ou alterar o branch de base do pull request, o merge automático será desabilitado. Por exemplo, se um mantenedor permitir o merge automático para um pull request a partir de uma bifurcação, o merge automático será desabilitado depois que um colaborador fizer push de novas alterações no pull request.{% endif %}
 
 Você pode fornecer feedback sobre o merge automático [entrando em contato conosco](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
 
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 946d110dbb..1ea56a5b86 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. Na lista "Pull requests", clique na pull request que deseja marcar como pronta para revisão.
 3. Na caixa de merge, clique em **Pronto para revisar**. ![Botão Ready for review (Pronta para revisão)](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index 73d0c2d497..2e1293f1f9 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Modificar uma pull request ativa no local
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index 524346ff97..7c6c1df74e 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ Para responder a um comentário em linha existente, é preciso navegar até o co
 
 **Dicas:**
 - Os comentários da pull request aceitam a mesma [formatação](/categories/writing-on-github) como comentários regulares no {% data variables.product.product_name %}, como @menções, emoji e referências.
-- Você pode [adicionar reações](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) a comentários em pull requests na guia **Files changed** (Arquivos alterados).
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index ab32c6f689..2469c7e0bf 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -19,6 +19,14 @@ Qualquer pessoa com permissões de leitura em um repositório pode criar um pull
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Alterar o intervalo de branches e o repositório de destino
 
 Por padrão, as pull requests são baseadas no [branch padrão](/articles/setting-the-default-branch) do repositório principal. Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)".
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index 1d43e3a1cc..ebc1e17c09 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ Se o branch que você deseja excluir estiver associado a um pull request aberto,
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. Role até o branch que deseja excluir e clique em {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![excluir o branch](/assets/images/help/branches/branches-delete.png)
+1. Role até o branch que deseja excluir e clique em {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![excluir o branch](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..5e94c14cd2
--- /dev/null
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: Introdução
+shortTitle: Introdução
+intro: 'Saiba mais sobre o fluxo do {% data variables.product.prodname_dotcom %} e diferentes maneiras de colaborar e discutir seus projetos.'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md
index 143ad29eb5..3003b98235 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Colaborar com problemas e pull requests
-intro: 'Use o fluxo do {% data variables.product.prodname_dotcom %} para rastrear e discutir alterações em problemas e também para propor e revisar alterações em pull requests.'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -18,10 +18,9 @@ topics:
 
 ### Índice
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index 40401ebfa2..cb208ae293 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ Você não pode realizar o merge de um rascunho de um pull request. Para obter m
 
 Se decidir que não quer que as alterações em um branch de tópico sofram merge no branch upstream, é possível [fechar a pull request](/articles/closing-a-pull-request) sem fazer merge.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Fazer merge de uma pull request no {% data variables.product.prodname_dotcom %}
 
 {% data reusables.repositories.sidebar-pr %}
@@ -65,13 +73,10 @@ O repositório pode ser configurado para que o branch principal de um pull reque
    {% endnote %}
    {% endif %}
 
-As pull requests sofrem merge com [a opção`--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge), exceto pelas
-pull requests com commits com combinação por squash ou com rebase/<2>, que passam por merge com a opção fast-forward.</p> 
+Pull requests are merged using [the `--no-ff` option](https://git-scm.com/docs/git-merge#_fast_forward_merge), except for [pull requests with squashed or rebased commits](/articles/about-pull-request-merges), which are merged using the fast-forward option.
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
-
-
 ### Leia mais
 
 - "[Reverter uma pull request](/articles/reverting-a-pull-request)"
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..2f2c91a21a
--- /dev/null
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### Introdução
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### Problemas
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### Pull requests
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### Discussões de equipe
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Em vez de abrir uma issue em um repositório para discutir uma ideia, você pode incluir toda a equipe tendo uma conversa em uma discussão de equipe.
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### Próximas etapas
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)".
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)".
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index ef0e259703..c1c1997417 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -19,7 +19,7 @@ topics:
 
 {% data reusables.dependency-review.feature-overview %}
 
-Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)".
+Revisão de dependência permite a você "desloque para a esquerda". Você pode usar as informações preditivas fornecidas para capturar dependências vulneráveis antes que elas cheguem à produção. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)".
 
 ### Revisar as dependências em um pull request
 
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
index b2fb10aa11..6e41e427ea 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
@@ -51,6 +51,6 @@ Para poder sincronizar a bifurcação com o repositório upstream, você deve [c
 
 {% tip %}
 
-**Dica**: a sincronização da bifurcação só atualiza a cópia local do repositório. To update your fork on {% data variables.product.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+**Dica**: a sincronização da bifurcação só atualiza a cópia local do repositório. Para atualizar a bifurcação no {% data variables.product.product_location %}, você precisa [fazer push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
 
 {% endtip %}
diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 975ed6f918..875e62c582 100644
--- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -79,5 +79,5 @@ Se você alterar a visibilidade de um repositório interno e, em seguida, exclui
 - "[Definir a visibilidade de um repositório](/articles/setting-repository-visibility)"
 - "[Sobre bifurcações](/articles/about-forks)"
 - "[Gerenciando a política de bifurcação de seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)"
-- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
+- "[Gerenciar a política de bifurcação para sua organização](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
 - "{% if currentVersion == "free-pro-team@latest" %}[Aplicar políticas de gerenciamento do repositório na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}"
diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md
index ed96783b90..8a187dd3f6 100644
--- a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md
+++ b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md
@@ -1,9 +1,9 @@
 ---
-title: Why are my commits linked to the wrong user?
+title: Por que meus commits estão vinculados ao usuário errado?
 redirect_from:
   - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/
   - /articles/why-are-my-commits-linked-to-the-wrong-user
-intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% if currentVersion != "github-ae@latest" %}, add an email address to your account email settings, or do both{% endif %}.'
+intro: 'O {% data variables.product.product_name %} usa o endereço de e-mail no header do commit para vincular o commit a um usuário do GitHub. Se seus commits estão sendo vinculados a outro usuário, ou não vinculados a um usuário, você pode precisar alterar suas configurações locais de configuração do Git, {% if currentVersion != "github-ae@latest" %}, adicionar um endereço de e-mail nas configurações de e-mail da sua conta ou fazer ambas as coisas{% endif %}.'
 versions:
   free-pro-team: '*'
   enterprise-server: '*'
@@ -13,44 +13,42 @@ versions:
 
 {% tip %}
 
-**Note**: If your commits are linked to another user, that does not mean the user can access your repository. A user can only access a repository you own if you add them as a collaborator or add them to a team that has access to the repository.
+**Observação**: se os commits estiverem vinculados a outro usuário, não significa que o usuário possa acessar o repositório pertencente a você. Um usuário só poderá acessar um repositório seu se você adicioná-lo como colaborador ou incluí-lo em uma equipe que tenha acesso ao repositório.
 
 {% endtip %}
 
-### Commits are linked to another user
+### Commits vinculados a outro usuário
 
-If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% if currentVersion == "github-ae@latest" %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your {% data variables.product.product_name %} account to link future commits to your account.
+Se seus commits estiverem vinculados a outro usuário, isso significa que o endereço de e-mail nas configurações locais do Git está conectado à conta desse usuário em {% data variables.product.product_name %}. Neste caso, você pode alterar o e-mail nas configurações locais do Git, {% if currentVersion == "github-ae@latest" %} ao endereço associado à sua conta em {% data variables.product.product_name %} para vincular seus commits futuros. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Definir o seu endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git).{% else %} E adicione o novo endereço de e-mail à sua conta de {% data variables.product.product_name %} para vincular futuros commits à sua conta.
 
-1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one.
-2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %}
+1. Para alterar o endereço de e-mail na sua configuração Git local, siga os passos em "[Definir o seu endereço de e-mail de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Se você trabalha em várias máquinas, precisa alterar essa configuração em cada uma deles.
+2. Adicione o endereço de e-mail da etapa 2 às configurações da sua conta seguindo os passos em "[Adicionar um endereço de e-mail à sua conta GitHub](/articles/adding-an-email-address-to-your-github-account)".{% endif %}
 
-Commits you make from this point forward will be linked to your account.
+Os commits criados a partir daí serão vinculados à sua conta.
 
-### Commits are not linked to any user
+### Commits não vinculados a nenhum usuário
 
-If your commits are not linked to any user, the commit author's name will not be rendered as a link to a user profile.
+Se seus commits não estiverem vinculados a nenhum usuário, o nome do autor do commit não será exibido como um link para o perfil de um usuário.
 
-To check the email address used for those commits and connect commits to your account, take the following steps:
+Para verificar o endereço de e-mail usado para esses commits e conectar commits à sua conta, siga estas etapas:
 
-1. Navigate to the commit by clicking the commit message link.
-![Commit message link](/assets/images/help/commits/commit-msg-link.png)
-2. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username.
-![Commit hover message](/assets/images/help/commits/commit-hover-msg.png)
+1. Navegue até o commit clicando no link da mensagem do commit. ![Link da mensagem do commit](/assets/images/help/commits/commit-msg-link.png)
+2. Para ler uma mensagem sobre o motivo do commit não estar vinculado, passe o mouse sobre o {% octicon "question" aria-label="Question mark" %} azul à direita do nome de usuário. ![Mensagem do commit exibida ao passar o mouse](/assets/images/help/commits/commit-hover-msg.png)
 
-  - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat.
-  - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %}
-  - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %}
+  - **Autor não reconhecido (com endereço de e-mail)** Se você vir esta mensagem com um endereço de e-mail, o endereço que você usou para criar o commit não estará conectado à sua conta em {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}Para vincular seus commits, [adicione o endereço de e-mail às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account).{% endif %} Se o endereço de e-mail tiver um Gravatar associado, o Gravatar será exibido ao lado do commit, em vez do Octoact cinza padrão.
+  - **Autor não reconhecido (sem endereço de e-mail)** Se você vir esta mensagem sem um endereço de e-mail, significa que você usou um endereço de e-mail genérico que não pode ser conectado à sua conta em {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} Você precisará [definir seu endereço de e-mail do commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %}
+  - **E-mail inválido** O endereço de e-mail nas configurações locais do Git está em branco ou não está formatado como um endereço de e-mail.{% if currentVersion != "github-ae@latest" %} Você precisará [definir seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de email do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %}
 
 {% if currentVersion == "github-ae@latest" %}
-You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."
+Você pode alterar o e-mail nas configurações locais do Git para o endereço associado à sua conta para vincular seus futuros commits. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Configurar o endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".
 {% endif %}
 
 {% warning %}
 
-If your local Git configuration contained a generic email address, or an email address that was already attached to another user's account, then your previous commits will not be linked to your account. While Git does allow you to change the email address used for previous commits, we strongly discourage this, especially in a shared repository.
+Caso a configuração local do Git contenha um endereço de e-mail genérico ou um endereço de e-mail já anexado à conta de outro usuário, os commits anteriores não serão vinculados à sua conta. Embora o Git permita que você altere o endereço de e-mail usado para commits anteriores, é recomendável evitar isso, principalmente em um repositório compartilhado.
 
 {% endwarning %}
 
-### Further reading
+### Leia mais
 
-* "[Searching commits](/articles/searching-commits)"
+* "[Pesquisar commits](/articles/searching-commits)"
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index 7de593f8dd..e3b291d203 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ Se você colocar o arquivo README na raiz do repositório, `docs`, ou no diretó
 
 {% endif %}
 
+### Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+The auto-generated table of contents is enabled by default for all Markdown files in a repository, but you can disable this feature for your repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under "Features", deselect **Table of contents**. ![Automatic TOC setting for repositories](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### Links de seção nos arquivos README e páginas blob
 
-Muitos projetos usam uma tabela de conteúdo no início de um README para direcionar usuários para diferentes seções do arquivo. {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### Links relativos e caminhos de imagem em arquivos README
 
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md
index f9fc43c46d..d7bf0adc2a 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md
@@ -15,7 +15,7 @@ topics:
 
 Você pode clonar um repositório do {% data variables.product.product_location %} para o seu computador local para facilitar a correção de conflitos de merge, adicionar ou remover arquivos e fazer push de commits maiores. Ao clonar um repositório, você copia o repositório do {% data variables.product.product_location %} para a sua máquina local.
 
-Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.product_location %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Você pode fazer push das alterações no repositório remoto no {% data variables.product.product_location %} ou extrair as alterações de outras pessoas no {% data variables.product.product_location %}. For more information, see "[Using Git](/github/getting-started-with-github/using-git)".
+Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.product_location %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Você pode fazer push das alterações no repositório remoto no {% data variables.product.product_location %} ou extrair as alterações de outras pessoas no {% data variables.product.product_location %}. Para obter mais informações, consulte "[Usar o Git](/github/getting-started-with-github/using-git).
 
 É possível clonar o repositório existente ou clonar o repositório existente de outra pessoa para contribuir para um projeto.
 
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index 16d4e9cea5..c1c341c0f3 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -24,7 +24,7 @@ Qualquer pessoa com permissões de leitura em um repositório de modelos pode cr
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-Você pode optar por incluir a estrutura do diretório e os arquivos apenas a partir do branch-padrão do repositório de modelos ou incluir todos os branches.
+Você pode optar por incluir a estrutura do diretório e os arquivos apenas a partir do branch-padrão do repositório de modelos ou incluir todos os branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 Criar um repositório a partir de um modelo é semelhante a bifurcar um repositório, mas há diferenças importantes:
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index a35cd26386..eb5cb185cc 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -20,7 +20,7 @@ topics:
 
 Para criar um repositório de modelos, é preciso criar um repositório e, em seguida, torná-lo um modelo. Para obter mais informações sobre como criar um repositório, consulte "[Criar um repositório](/articles/creating-a-new-repository)".
 
-Depois de fazer o seu repositório um modelo, qualquer pessoa com acesso ao repositório pode gerar um novo repositório com a mesma estrutura de diretório e arquivos, assim como o branch padrão. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Eles também podem optar por incluir todos os outros branches no seu repositório.{% endif %} Para obter mais informações, consulte "[Criar um repositório de um modelo](/articles/creating-a-repository-from-a-template)."
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
index ce6f8d9d71..5822f938b4 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
@@ -17,7 +17,7 @@ Erros de digitação acontecem e os nomes dos repositórios diferenciam maiúscu
 
 Para evitar o erro ao clonar, sempre copie e cole a URL clone da página do repositório. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 
-To update the remote on an existing repository, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)".
+Para atualizar o repositório remoto em um repositório existente, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 ### Verifique as permissões
 
@@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > fornece acesso shell.
 ```
 
-Se o repositório pertencer a uma organização e você estiver usando uma chave SSH gerada por um aplicativo OAuth, o acesso ao aplicativo OAuth poderá ser restringido pelo proprietário da organização. For more information, see "<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">About OAuth App access restrictions</a>."
+Se o repositório pertencer a uma organização e você estiver usando uma chave SSH gerada por um aplicativo OAuth, o acesso ao aplicativo OAuth poderá ser restringido pelo proprietário da organização. Para obter mais informações, consulte "<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">Sobre as restrições de acesso ao aplicativo OAuth</a>".
 
 Para obter mais informações, consulte [Adicionar uma nova chave SSH à sua conta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account).
 
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
index cb856a10b3..e533766110 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
@@ -79,4 +79,4 @@ Quando for solicitado um nome e senha, certifique-se de usar uma conta que tenha
 
 ### Substitua por SSH
 
-Se você configurou as chaves SSH previamente, é possível usar a URL clone SSH em vez de HTTPS.  For more information, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+Se você configurou as chaves SSH previamente, é possível usar a URL clone SSH em vez de HTTPS.  Para obter mais informações, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)."
diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
index a8e61bf48c..282b43e046 100644
--- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
+++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### Escolher a licença ideal
 
-Nós criamos o [choosealicense.com](http://choosealicense.com), para ajudá-lo a compreender como licenciar seu código. Uma licença de software descreve o que pode e não pode ser feito com seu código-fonte, assim é importante tomar uma decisão fundamentada.
+Nós criamos o [choosealicense.com](https://choosealicense.com), para ajudá-lo a compreender como licenciar seu código. Uma licença de software descreve o que pode e não pode ser feito com seu código-fonte, assim é importante tomar uma decisão fundamentada.
 
 Você não tem qualquer obrigação de escolher uma licença. Entretanto, sem uma licença, são aplicadas as leis padrão de copyright, o que significa que você detém todos os direitos de seu código-fonte e ninguém poderá reproduzir, distribuir ou criar derivativos de seu trabalho. Se você está criando um projeto de código aberto, incentivamos fortemente que você contemple uma licença de código aberto. O [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) (Guia de código aberto) apresenta orientações adicionais para a escolha da licença correta para seu projeto.
 
@@ -76,7 +76,7 @@ Quando você pesquisar uma família de licenças, os resultados incluirão todas
 
 ### Identificar uma licença
 
-[A licenciada de código aberto Ruby gem ](https://github.com/licensee/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](http://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+[A licenciada de código aberto Ruby gem ](https://github.com/licensee/licensee) compara o arquivo *LICENSE* do repositório com uma lista curta de licenças conhecidas. A licenciada também fornece as [APIs de licenças](/rest/reference/licenses) e [dá informações sobre como os repositórios no {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o seu repositório usa uma licença que não está listada no [site Choose a License](https://choosealicense.com/appendix/), você pode [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
 
 Caso o seu repositório use uma licença listada no site Choose a License que não aparece na parte superior da página do repositório, ele pode conter licenças múltiplas ou outras complexidades. Para que sua licença seja detectada, simplifique o arquivo *LICENSE* e anote a complexidade em algum outro local, como no arquivo *README* do repositório.
 
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index 88b3451249..cbbddbcef2 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index e14b66d6f8..44ac010fc4 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
index 75b3525738..ed88b0c65e 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
@@ -10,24 +10,26 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
 ### Sobre a configuração do {% data variables.product.prodname_code_scanning %}
 
-Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}, usando {% data variables.product.prodname_actions %} ou a partir do seu sistema de integração contínua (CI), usando o {% data variables.product.prodname_codeql_runner %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." Para obter mais informações sobre o {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
+Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}, usando {% data variables.product.prodname_actions %}, ou a partir do seu sistema de integração contínua (CI), ao usar {% data variables.product.prodname_codeql_runner %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." Para obter mais informações sobre o {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
 
-Este artigo é sobre executar {% data variables.product.prodname_code_scanning %} dentro de {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}.
+Este artigo é sobre a execução de {% data variables.product.prodname_code_scanning %} no {% data variables.product.product_name %}.
 
-Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve habilitar o {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning).
+Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve configurar {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)".
 
 {% data reusables.code-scanning.edit-workflow %}
 
-A análise de {% data variables.product.prodname_codeql %} é apenas um tipo de {% data variables.product.prodname_code_scanning %} que você pode fazer em {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} em  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contém outros fluxos de trabalho de {% data variables.product.prodname_code_scanning %}  que você pode usar. {% if currentVersion == "free-pro-team@latest" %}Você pode encontrar uma seleção destes na página "Começar com {% data variables.product.prodname_code_scanning %}" que você pode acessar na aba **{% octicon "shield" aria-label="The shield symbol" %} Segurança** .{% endif %} Os exemplos específicos apresentados neste artigo estão relacionados ao arquivo de {% data variables.product.prodname_codeql_workflow %}.
+A análise de {% data variables.product.prodname_codeql %} é apenas um tipo de {% data variables.product.prodname_code_scanning %} que você pode fazer em {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %} em {% data variables.product.prodname_dotcom_the_website %} contém outros fluxos de trabalho de {% data variables.product.prodname_code_scanning %} que você pode usar. Os exemplos específicos indicados neste artigo relacionam-se com o arquivo de {% data variables.product.prodname_codeql_workflow %}.
 
 ### Editing a code scanning workflow
 
-O {% data variables.product.prodname_dotcom %} salva arquivos de fluxo de trabalho no diretório _.github/workflows_ do seu repositório. You can find the workflow by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
+O {% data variables.product.prodname_dotcom %} salva arquivos de fluxo de trabalho no diretório _.github/workflows_ do seu repositório. Você pode encontrar um fluxo de trabalho que você adicionou procurando o nome do seu arquivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
 1. No seu repositório, pesquise o arquivo do fluxo de trabalho que você deseja editar.
 1. No canto superior direito da vista do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %} para abrir o editor do fluxo de trabalho. ![Edite o botão do arquivo do fluxo de trabalho](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
@@ -47,7 +49,7 @@ Se você usar o fluxo de trabalho padrão, o {% data variables.product.prodname_
 
 #### Fazer a varredura de pull requests
 
-O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% if currentVersion ver_gt "enterprise-server@2.21" %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."{% endif %}
+O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. O evento `pull_request` não será acionado se o pull request tiver sido aberto a partir de uma bifurcação privada.
 
 Para obter mais informações sobre o evento `pull_request` , consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)".
 
@@ -71,7 +73,7 @@ on:
 **Observações**
 
 * `on:pull_request:paths-ignore` e `on:pull_request:paths` definem condições que determinam se as ações no fluxo de trabalho serão executadas em um pull request. Eles não determinam quais arquivos serão analisados quando as ações _são_ executadas. Quando uma pull request contém quaisquer arquivos não correspondidos por `on:pull_request:paths-ignore` ou `on:pull_request:paths`, o fluxo de trabalho executa as ações e faz a varredura de todos os arquivos alterados no pull request, incluindo aqueles que correspondidos por `on:pull_request:paths-ignore` ou `on:pull_request:paths`, a menos que os arquivos tenham sido excluídos. Para obter informações sobre como excluir arquivos da análise, consulte "[Especificar diretórios a serem varridos](#specifying-directories-to-scan)".
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. Para resultados precisos, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} precisam conseguir comparar novas alterações com a análise do commit anterior.
+* Para arquivos do fluxo de trabalho de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, não use as palavras-chave `paths-ignore` ou `paths` com o evento `on:push`, pois é provável que isso gere análises ausentes. Para resultados precisos, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} precisam conseguir comparar novas alterações com a análise do commit anterior.
 
 {% endnote %}
 
@@ -94,21 +96,21 @@ O exemplo a seguir mostra um {% data variables.product.prodname_codeql_workflow
 ``` yaml
 on:
   push:
+    branches: [main, protected]
   pull_request:
+    branches: [main]
   schedule:
-    - cron: '0 15 * * 0'
+    - cron: '40 7 * * 2'
 ```
 
 Este fluxo de trabalho faz a varredura:
 * Cada push para o branch-padrão e o branch protegido
 * Cada pull request para o branch-padrão
-* O branch-padrão às 15h. todo domingo
+* O branch padrão toda terça-feira às 7h40 UTC
 
 ### Especificar um sistema operacional
 
-Se seu código exigir um sistema operacional específico para compilar, você poderá configurar o sistema operacional em seu {% data variables.product.prodname_codeql_workflow %}. Edite o valor de `jobs.analyze.runs-on` para especificar o sistema operacional para a máquina que executa suas ações de {% data variables.product.prodname_code_scanning %}. {% if currentVersion ver_gt "enterprise-server@2. 1" %}Você especifica o sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos após `auto-hospedado`.{% else %}
-
-Se você optar por usar um executor auto-hospedado para varredura de código, você pode especificar um sistema operacional usando uma etiqueta apropriada como segundo elemento em um array de dois elementos, após `auto-hospedado`.{% endif %}
+Se seu código exigir um sistema operacional específico para compilar, você poderá configurar o sistema operacional em seu {% data variables.product.prodname_codeql_workflow %}. Edite o valor de `jobs.analyze.runs-on` para especificar o sistema operacional para a máquina que executa suas ações de {% data variables.product.prodname_code_scanning %}. Você especifica o sistema operacional usando uma etiqueta apropriada como segundo elemento em uma matriz de dois elementos, depois de `auto-hospedado`.
 
 ``` yaml
 jobs:
@@ -117,23 +119,21 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+O {% data variables.product.prodname_code_scanning_capc %} é compatível com as versões mais recentes do macOS, Ubuntu, e Windows. Portanto, os valores típicos para essa configuração são `ubuntu-latest`, `windows-latest` e `macos-latest`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" e "[Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)".
 
-O {% data variables.product.prodname_code_scanning_capc %} é compatível com as versões mais recentes do macOS, Ubuntu, e Windows. Portanto, os valores típicos para essa configuração são `ubuntu-latest`, `windows-latest` e `macos-latest`. Para obter mais informações, consulte {% if currentVersion ver_gt "enterprise-server@2. 1" %}"[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" e "[Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}Você deve garantir que o Git esteja na variável do PATH em seus executores auto-hospedados.{% else %}Se você usa um executor auto-hospedado, você deve garantir que o Git esteja na variável de PATH.{% endif %}
+Você deve garantir que o Git esteja na variável PATH nos seus executores auto-hospedados.
 
 ### Alterar as linguagens que são analisadas
 
 O {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} detecta automaticamente código escrito nas linguagens compatíveis.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 O arquivo padrão do {% data variables.product.prodname_codeql_workflow %} contém uma matriz de criação denominada `linguagem` que lista as linguagens no seu repositório que são analisadas. O {% data variables.product.prodname_codeql %} preenche automaticamente esta matriz quando você adiciona o {% data variables.product.prodname_code_scanning %} a um repositório. Usar a matriz de `linguagem` otimiza {% data variables.product.prodname_codeql %} para executar cada análise em paralelo. Recomendamos que todos os fluxos de trabalho adotem esta configuração devido aos benefícios de desempenho de criações paralelas. Para obter mais informações sobre matrizes de criação, consulte "[Gerenciar fluxos de trabalho complexos](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-Se o seu fluxo de trabalho usar a matriz de </code>linguagem `, o {% data variables.product.prodname_codeql %} será codificado para analisar apenas as linguagens da matriz. Para alterar as linguagens que você deseja analisar, edite o valor da variável da matriz. Você pode remover uma linguagem para evitar que ele seja analisado ou adicionar uma linguagem que não estava presente no repositório quando o {% data variables.product.prodname_code_scanning %} estava habilitado. Por exemplo, se o repositório inicialmente continha apenas JavaScript quando {% data variables.product.prodname_code_scanning %} foi habilitado e, posteriormente, você adicionou o código Python, você precisará adicionar o <code>python` à matriz.
+Se o seu fluxo de trabalho usar a matriz de </code>linguagem `, o {% data variables.product.prodname_codeql %} será codificado para analisar apenas as linguagens da matriz. Para alterar as linguagens que você deseja analisar, edite o valor da variável da matriz. Você pode remover uma linguagem para evitar que ele seja analisado ou adicionar uma linguagem que não estava presente no repositório quando o {% data variables.product.prodname_code_scanning %} estava configurado. Por exemplo, se o repositório inicialmente continha apenas JavaScript quando {% data variables.product.prodname_code_scanning %} foi configurado e, posteriormente, você adicionou o código Python, você precisará adicionar o <code>python` à matriz.
 
 ```yaml
 jobs:
@@ -168,31 +168,34 @@ Alternativamente, você pode instalar as dependências do Python manualmente em
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
@@ -200,13 +203,17 @@ jobs:
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho.
+Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. Se as consultas estiverem em um repositório privado, use o parâmetro `external-repository-token` para especificar um token que tenha acesso ao repositório privado.
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     queries: COMMA-SEPARATED LIST OF PATHS
+    # Optional. Forneça uma token para acessar repositórios privados.
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
 Você também pode executar suítes de consultas adicionais especificando-os em um arquivo de configuração. Os suítes de consulta são coleções de consultas, geralmente agrupados por finalidade ou linguagem.
 
@@ -216,12 +223,15 @@ Você pode executar consultas adicionais especificando-as em um arquivo de confi
 
 Para incluir um ou mais suites de consulta, adicione uma seção `consultas` ao seu arquivo de configuração.
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     config-file: ./.github/codeql/codeql-config.yml
     queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
 ### Usar uma ferramenta de varredura de código de terceiros
 
@@ -235,7 +245,19 @@ No arquivo de workflow use o parâmetro `config-file` da ação `init` para espe
     config-file: ./.github/codeql/codeql-config.yml
 ```
 
-O arquivo de configuração pode ser localizado no repositório local ou em um repositório remoto público. Para repositórios remotos, você pode usar a sintaxe _owner/repository/file.yml@branch_. As configurações no arquivo são escritas no formato YAML.
+{% data reusables.code-scanning.custom-configuration-file %}
+
+Se o arquivo de configuração estiver localizado em um repositório privado externo, use o parâmetro `external-repository-token` da ação `init` para especificar um token que tenha acesso ao repositório privado.
+
+{% raw %}
+```yaml
+uses: github/codeql-action/init@v1
+with:
+  external-repository-token: ${{ secrets.ACCESS_TOKEN }}
+```
+{% endraw %}
+
+As configurações no arquivo de configuração estão escritas no formato YAML.
 
 #### Especificar consultas adicionais
 
@@ -273,13 +295,14 @@ paths-ignore:
 **Observação**:
 
 * As palavras-chave `caminhos` e `paths-ignore`, usados no contexto do arquivo de configuração do {% data variables.product.prodname_code_scanning %}, não deve ser confundido com as mesmas palavras-chave usadas para `on.<push|pull_request>.paths` em um fluxo de trabalho. Quando estão acostumados a modificar `on.<push|pull_request>` em um fluxo de trabalho, eles determinam se as ações serão executadas quando alguém modifica o código nos diretórios especificados. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)".
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
 * `**` **Note**: `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. Por exemplo, `foo/**`, `**/foo` e `foo/**/bar` são todos de sintaxe permitida, mas `**foo` não é. No entanto, você pode usar estrelas únicas junto com outros caracteres, conforme mostrado no exemplo. Você precisará colocar entre aspas qualquer coisa que contenha um caractere `*`.
 
 {% endnote %}
 
 Para linguagens compiladas, se você deseja limitar {% data variables.product.prodname_code_scanning %} a diretórios específicos no seu projeto, você deverá especificar os passos de compilação adequados no fluxo de trabalho. Os comandos que você precisa usar para excluir um diretório da criação dependerão do seu sistema de criação. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 
-Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o código em diretórios específicos. Você deverá excluir diretórios nas suas etapas de criação e usar as palavras-chave `paths-ignore` e `caminhos` para [`on.<push|pull_request>`](https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) no seu arquivo de fluxo de trabalho.
+Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o código em diretórios específicos. Você deverá excluir diretórios nas suas etapas de criação e usar as palavras-chave `paths-ignore` e `caminhos` para [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) no seu arquivo de fluxo de trabalho.
 
 #### Exemplo de arquivo de configuração
 
@@ -291,25 +314,6 @@ Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o c
 
 {% data reusables.code-scanning.autobuild-add-build-steps %} Para obter mais informações sobre como configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para linguagens compiladas, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)".
 
-### Acessar repositórios privados
-
-Se o seu fluxo de trabalho para {% data variables.product.prodname_code_scanning %} acessar repositórios privados no {% data variables.product.prodname_dotcom %}, você deverá configurar o Git para efetuar a autenticação com um token de acesso pessoal. Defina o segredo no ambiente do executor usando `jobs.<job_id>.steps[*].env` no seu fluxo de trabalho antes de qualquer ação do {% data variables.product.prodname_codeql %}. Para mais informações consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" e "[Criar e armazenar segredos criptografados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
-
-Por exemplo, a configuração a seguir faz com que o Git substitua todas as URLs para os repositórios de `ghost/foo`, `ghost/bar` e `ghost/baz` em {% data variables.product.prodname_dotcom_the_website %} pelas URLs que incluem o token de acesso pessoal que você armazena na variável de ambiente de `ACCESS_TOKEN`.
-
-{% raw %}
-```yaml
-steps:
-- name: Configure access to private repositories
-  env:
-    TOKEN: ${{ secrets.ACCESS_TOKEN }}
-  run: |
-    git config --global url."https://${TOKEN}@github.com/ghost/foo".insteadOf "https://github.com/ghost/foo"
-    git config --global url."https://${TOKEN}@github.com/ghost/bar".insteadOf "https://github.com/ghost/bar"
-    git config --global url."https://${TOKEN}@github.com/ghost/baz".insteadOf "https://github.com/ghost/baz"
-```
-{% endraw %}
-
 ### {% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}.
 
 Você pode exibir análise de código de uma ferramenta de terceiros em {% data variables.product.prodname_dotcom %}, adicionando a ação de `upload-sarif` ao seu fluxo de trabalho. Você pode fazer o upload de dados de análise de código com a ação `upload-sarif`. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)".
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index 6b040910a0..3aa32b0a23 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -48,11 +50,11 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 O {% data variables.product.prodname_codeql_runner %} detecta e faz a varredura automática do código escrito nas linguagens compatíveis.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-Para substituir a detecção automática de idioma, execute o comando `init` com o sinalizador `--languages`, seguido de uma lista de palavras-chave de linguagem separada por vírgulas. As palavras-chave para as linguagens compatíveis são `cpp`, `csharp`, `go`, `java`, `javascript` e `python`.
+Para substituir a detecção automática de idioma, execute o comando `init` com o sinalizador `--languages`, seguido de uma lista de palavras-chave de linguagem separada por vírgulas. As palavras-chave para os idiomas compatíveis são {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index 8de99768c7..d2d2b5ecf5 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -31,11 +33,7 @@ Se o fluxo de trabalho usar uma matriz de `linguagem`, `autobuild` tentará cria
 
 {% note %}
 
-{% if currentVersion == "github-ae@latest" %}**Observação**: Para instruções sobre como certificar-se de que o {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)".
-{% else %}
-**Observação**: Se você usa executores auto-hospedados para
-{% data variables.product.prodname_actions %}, talvez você precise instalar um software adicional para usar o processo de `criação automática`. Além disso, se seu repositório precisar de uma versão específica de uma ferramenta de criação, talvez seja necessário instalá-lo manualmente. Para obter mais informações, consulte "[Especificações para executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
-{% endif %}
+**Observação**: Se você usa executores auto-hospedados para {% data variables.product.prodname_actions %}, talvez seja necessário instalar um software adicional para usar o processo de `autobuild`. Além disso, se seu repositório precisar de uma versão específica de uma ferramenta de criação, talvez seja necessário instalá-lo manualmente. Para obter mais informações, consulte "[Especificações para executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index 0f00bb4b66..a53b293a84 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### Índice
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 16f5aee9ac..b950a974a2 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index f2fdab785c..15c4385640 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,13 +1,15 @@
 ---
 title: Gerenciar alertas de verificação de código para o seu repositório
 shortTitle: Gerenciando alertas
-intro: 'Da vista da segurança, você pode visualizar, corrigir, {% if currentVersion == "enterprise-server@2. 2" %}ou fechar{% else %}ignorar ou excluir{% endif %} alertas de potenciais vulnerabilidades ou erros no código do seu projeto.'
+intro: 'Na visão de segurança, você pode visualizar, corrigir ou fechar alertas de possíveis vulnerabilidades ou erros no código do seu projeto.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre os alertas de {% data variables.product.prodname_code_scanning %}
@@ -45,81 +47,25 @@ Você precisa de permissão de gravação para visualizar um resumo de todos os
 
 Qualquer pessoa com permissão de gravação para um repositório pode corrigir um alerta, fazendo o commit de uma correção do código. Se o repositório tiver {% data variables.product.prodname_code_scanning %} agendado para ser executado em pull requests, recomenda-se registrar um pull request com sua correção. Isso ativará a análise de {% data variables.product.prodname_code_scanning %} referente às alterações e irá testar se sua correção não apresenta nenhum problema novo. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" e " "[Testar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)".
 
-Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra os alertas corrigidos e aqueles que os usuários têm {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra alertas e alertas corrigidos que os usuários fecharam.
 
 Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico.
 
 ![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 ### Fechar um alerta
 
 Fechar um alerta é uma maneira de resolver um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %}
 
-{% else %}
-
-### Ignorar ou excluir alertas
-
-Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você configurou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você configurou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**.
-
-Ignorar um alerta é uma maneira de fechar um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Você pode ignorar alertas de anotações de {% data variables.product.prodname_code_scanning %} no código ou da lista de resumo dentro na aba **Segurança**.
-
-Ao descartar um alerta:
-
-- Ele é ignorado em todos os branches.
-- O alerta é removido do número de alertas atuais para o seu projeto.
-- O alerta é movido para a lista "Fechado" no resumo dos alertas, onde você pode reabri-lo, se necessário.
-- O motivo pelo qual você fechou o alerta foi gravado.
-- Da próxima vez que {% data variables.product.prodname_code_scanning %} for executado, o mesmo código não gerará um alerta.
-
-Ao excluir um alerta:
-
-- Ele é excluído em todos os branches.
-- O alerta é removido do número de alertas atuais para o seu projeto.
-- Ele _não é_ adicionado à lista "Fechado" no resumo dos alertas.
-- Se o código que gerou o alerta permanecer o mesmo, e a mesma ferramenta {% data variables.product.prodname_code_scanning %} for executada novamente sem qualquer alteração de configuração, o alerta será exibido novamente nos resultados das análises.
-
-Para ignorar ou excluir alertas:
-
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
 1. Selecione o menu suspenso **Fechar** e clique em um motivo para fechar o alerta.    
    ![Escolher o motivo para fechar o alerta no menu suspenso Fechar](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. Se você tem permissões de administrador para o repositório e deseja excluir alertas para esta ferramenta de {% data variables.product.prodname_code_scanning %}, selecione algumas ou todas as caixas de seleção e clique em **Excluir**.
-
-   ![Excluir alertas](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   Opcionalmente, você pode usar os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas de correspondência de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas.
-
-  ![Filtrar alertas por regra](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. Se você deseja ignorar um alerta, é importante explorar primeiro o alerta para que você possa escolher o motivo correto para ignorá-lo. Clique no alerta que você deseja explorar.
-
-  ![Abrir um alerta da lista de resumo](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. Revise o alerta e clique em **Ignorar** e escolha um motivo para fechar o alerta. ![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### Ignorar múltiplos alertas de uma vez
-
-Se um projeto tem vários alertas que você deseja ignorar pelo mesmo motivo, você pode ignorá-los em massa do resumo de alertas. Normalmente, você pode querer filtrar a lista e, em seguida, ignorar todos os alertas correspondentes. Por exemplo, você pode querer ignorar todos os alertas atuais no projeto que foram marcados para uma vulnerabilidade específica de Enumeração de Fraqueza Comum (CWE).
-
-{% endif %}
-
 ### Leia mais
 
 - "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index 0da1f1b35e..34e85b04b8 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -9,13 +9,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre {% data variables.product.prodname_code_scanning %} com uma compilação de contêiner
 
 Se você estiver configurando {% data variables.product.prodname_code_scanning %} para um idioma compilado e estiver criando o código em um ambiente de contêiner, a análise pode falhar com a mensagem de erro "Nenhum código fonte foi visto durante a compilação." Isso indica que {% data variables.product.prodname_codeql %} não conseguiu monitorar seu código da forma como foi compilado.
 
-Você precisa executar {% data variables.product.prodname_codeql %} no mesmo contêiner em que você cria o seu código. Isto se aplica independentemente de você usar {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Se você estiver usando {% data variables.product.prodname_codeql_runner %}, execute-o no contêiner onde seu código é criado. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)".
+Você precisa executar {% data variables.product.prodname_codeql %} no mesmo contêiner em que você cria o seu código. Isto se aplica independentemente de você usar {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Se você estiver usando {% data variables.product.prodname_codeql_runner %}, execute-o no contêiner onde seu código é criado. Para obter mais informações sobre {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)".
 
 ### Dependências
 
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index 4a38426396..e64b81223c 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
@@ -30,17 +31,13 @@ O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha
 {% note %}
 
 **Notas:**
-{% if currentVersion == "free-pro-team@latest" %}
-* O {% data variables.product.prodname_codeql_runner %} usa o CLI de {% data variables.product.prodname_codeql %} para analisar o código e, portanto, tem as mesmas condições da licença. É grátis usar em repositórios públicos que são mantidos no {% data variables.product.prodname_dotcom_the_website %}, e disponíveis para uso em repositórios privados que são propriedade de clientes com uma licença do {% data variables.product.prodname_advanced_security %}. Para obter informações, consulte "[{% data variables.product.product_name %} Termos e Condições](https://securitylab.github.com/tools/codeql/license) de do CLI de {% data variables.product.prodname_codeql %} " e "[{% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
-{% else %}
 * O {% data variables.product.prodname_codeql_runner %} está disponível para os clientes com uma licença de {% data variables.product.prodname_advanced_security %}.
-{% endif %}
 * O {% data variables.product.prodname_codeql_runner %} não deve ser confundido com o CLI de {% data variables.product.prodname_codeql %}. O CLI de {% data variables.product.prodname_codeql %} é uma interface de linha de comando interativa que permite que você crie bancos de dados de {% data variables.product.prodname_codeql %} para pesquisa de segurança e realize consultas de {% data variables.product.prodname_codeql %}. Para obter mais informações, consulte "[ CLI de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)".
 {% endnote %}
 
 ### Fazer o download do {% data variables.product.prodname_codeql_runner %}
 
-Você pode fazer o download de {% data variables.product.prodname_codeql_runner %} de https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. Em alguns sistemas operacionais, talvez você precise alterar as permissões para o arquivo baixado antes de executá-lo.
+Você pode fazer o download do {% data variables.product.prodname_codeql_runner %} em https://github.com/github/codeql-action/releases. Em alguns sistemas operacionais, talvez você precise alterar as permissões para o arquivo baixado antes de executá-lo.
 
 No Linux:
 
@@ -62,7 +59,7 @@ No Windows, o arquivo `codeql-runner-win.exe` normalmente não exige alteração
 Após fazer o download de {% data variables.product.prodname_codeql_runner %} e verificar se pode ser executado, você deverá disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. Por exemplo, você pode configurar cada servidor para que copie o executor de um local central interno. Como alternativa, você poderia usar a API REST para obter o executor diretamente do {% data variables.product.prodname_dotcom %}, por exemplo:
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
@@ -73,9 +70,8 @@ Além disso, cada servidor de CI também precisa:
 
 As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são:
 
-1. Permita o acesso dos servidores de CI a https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github. om{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action para que {% data variables.product.prodname_codeql_runner %} possa fazer o download do pacote automaticamente.
-{% if currentVersion == "enterprise-server@2.22" %}
-1. Espelhe o repositório `github/codeql-action` em {% data variables.product.product_name %}. A menos que você especifique o sinalizador <nobr>`--codeql-path`</nobr> , o executor verifica automaticamente o pacote neste local e no {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
+1. Permite que os servidores de CI acessem https://github.com/github/codeql-action para que {% data variables.product.prodname_codeql_runner %} possa fazer o download do pacote automaticamente.
+1. Espelhe o repositório `github/codeql-action` em {% data variables.product.product_name %}. A menos que você especifique o sinalizador <nobr>`--codeql-path`</nobr> , o executor verifica automaticamente o pacote neste local e no {% data variables.product.prodname_dotcom_the_website %}.
 1. Faça o download/extraia o pacote manualmente, armazene-o com outros recursos centrais e use <nobr>`--codeql-path`</nobr> o sinalizador para especificar o local do pacote nas chamadas para inicializar o {% data variables.product.prodname_codeql_runner %}.
 
 ### Chamar {% data variables.product.prodname_codeql_runner %}
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index 97fa61126f..a07046bbf4 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre o suporte SARIF
@@ -17,7 +19,7 @@ SARIF (Formato de Intercâmbio de Resultados de Análise Estática) é um [OASIS
 
 Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para obter mais informações, consulte "[Enviar um arquivo SARIF para o {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". Para obter mais informações sobre o esquema SARIF 2.1.0 JSON, consulte [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. Para mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" ou "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)".
 
 {% data variables.product.prodname_dotcom %} usa propriedades no arquivo SARIF para exibir alertas. Por exemplo, `shortDescription` e `fullDescription` aparecem na parte superior de um alerta de {% data variables.product.prodname_code_scanning %}. O `local` permite que {% data variables.product.prodname_dotcom %} mostre anotações no seu arquivo de código. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)".
 
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
index 55666f80f0..d6310956fc 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -21,12 +23,10 @@ Você decide como gerar alertas de {% data variables.product.prodname_code_scann
 
 ### Configurar {% data variables.product.prodname_code_scanning %} usando ações
 
-{% if currentVersion == "free-pro-team@latest" %}Usar ações para executar {% data variables.product.prodname_code_scanning %} levará minutos. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3. " %}Se {% data variables.product.prodname_code_scanning %} estiver faltando, peça para um proprietário da organização ou administrador de repositório habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Os fluxos de trabalho são exibidos apenas se forem relevantes para as linguagens de programação detectadas no repositório. O {% data variables.product.prodname_codeql_workflow %} é sempre exibido, mas o botão "Configurar este fluxo de trabalho" só é habilitado se a análise de {% data variables.product.prodname_codeql %} for compatível com as linguagens presentes no repositório.{% endif %}
+3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. ![Botão "Configurar este fluxo de trabalho" em "Começar com cabeçalho de {% data variables.product.prodname_code_scanning %}"](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
 5. Para personalizar como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho.
 
    Geralmente, você pode fazer commit do {% data variables.product.prodname_codeql_workflow %} sem fazer nenhuma alteração nele. No entanto, muitos dos fluxos de trabalho de terceiros exigem uma configuração adicional. Portanto, leia os comentários no fluxo de trabalho antes de fazer o commit.
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index 7089c64944..0c0d0b4ed9 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -10,13 +10,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### Sobre os resultados de {% data variables.product.prodname_code_scanning %} em pull requests
 
 Em repositórios onde {% data variables.product.prodname_code_scanning %} está configurado como uma verificação de pull request, {% data variables.product.prodname_code_scanning %} verifica o código no pull request. Por padrão, isso é limitado a pull requests que visam o branch-padrão ou branches protegidos, mas você pode alterar esta configuração em {% data variables.product.prodname_actions %} ou em um sistema de CI/CD de terceiros. Se o merge das alterações introduziria novos alertas de {% data variables.product.prodname_code_scanning %} no branch de destino, estes serão relatados como resultados de verificação no pull request. Os alertas também são exibidos como anotações na aba **Arquivos alterados** do pull request. Se você tiver permissão de gravação no repositório, você poderá ver qualquer alerta de {% data variables.product.prodname_code_scanning %} existente na aba **Segurança**. Para obter informações sobre os alertas do repositório, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} do repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)".
 
-Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido usar {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou {% if currentVersion == "enterprise-server@2.22" %}fechar{% else %}ignorar{% endif %} todos os erros alertas antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
+Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido usar {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou fechar todos os alertas de erro antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
 
 ![Ocorreu uma falha na verificação de {% data variables.product.prodname_code_scanning %} em um pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -24,7 +26,7 @@ Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com
 
 Há muitas opções para configurar {% data variables.product.prodname_code_scanning %} como uma verificação de pull request. Portanto, a configuração exata de cada repositório irá variar e alguns terão mais de uma verificação. A verificação que contém os resultados de {% data variables.product.prodname_code_scanning %} é: **Resultados da varredura de código**.
 
-Se o repositório usar a {% data variables.product.prodname_codeql_workflow %} uma **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)**, executa-se a verificação para cada linguagem antes que a verificação de resultados seja executada. A verificação de análise pode falhar se houver problemas de configuração ou se o pull request altera a criação para uma linguagem que a análise precisa para compilar (por exemplo, C/C++, C#, ou Java). Assim como com outras verificações de pull request, você poderá ver informações completas da falha de verificação na aba de **Verificações**. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)."
+Se o repositório usar a {% data variables.product.prodname_codeql_workflow %} uma **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)**, executa-se a verificação para cada linguagem antes que a verificação de resultados seja executada. A verificação de análise pode falhar se houver problemas de configuração ou se o pull request altera a criação para uma linguagem que a análise precisa para compilar (por exemplo, C/C++, C#, ou Java). Assim como com outras verificações de pull request, você poderá ver informações completas da falha de verificação na aba de **Verificações**. Para obter mais informações sobre configuração e solução de problemas, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" ou "[Solução de problemas do fluxo de trabalho de {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)".
 
 ### Triar de um alerta no seu pull request
 
@@ -40,28 +42,10 @@ Na visualização detalhada de um alerta, algumas ferramentas de {% data variabl
 
 ![Descrição do alerta e link para mostrar mais informações](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolvendo{% else %}Corrigindo{% endif %} um alerta no seu pull request
+### Resolver um alerta no seu pull request
 
 Qualquer pessoa com acesso push a um pull request pode corrigir um alerta de {% data variables.product.prodname_code_scanning %} que seja identificado nesse pull request. Se você fizer commit de alterações na solicitação do pull request, isto acionará uma nova execução das verificações do pull request. Se suas alterações corrigirem o problema, o alerta será fechado e a anotação removida.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 Se você não considera que um alerta deve ser corrigido, os usuários com permissão de gravação podem fechar o alerta manualmente. {% data reusables.code-scanning.close-alert-examples %} O botão **Fechar** está disponível nas anotações e no modo de exibição de alertas se você tiver permissão de gravação no repositório.
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### Ignorar um alerta no seu pull request
-
-Uma forma alternativa de fechar um alerta é ignorá-lo. Você pode descartar um alerta se não acha que ele precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Se você tem permissão de gravação no repositório, o botão **Ignorar** estará disponível nas anotações de código e no resumo de alertas. Ao clicar em **Ignorar** será solicitado que você escolha um motivo para fechar o alerta.
-
-![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-Para obter mais informações sobre alertas ignorados, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)".
-
-{% endif %}
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index f64fccbab2..563fc30360 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index e528e4fe5a..e8d893b2d0 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -28,7 +30,10 @@ Se ocorrer uma falha na uma criação automática de código para uma linguagem
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -111,25 +116,13 @@ 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>
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Os resultados diferem entre as plataformas de análise
-
-Se você estiver analisando o código escrito no Python, você poderá ver resultados diferentes dependendo se você executa o {% data variables.product.prodname_codeql_workflow %} no Linux, macOS ou Windows.
-
-Nos executores hospedados no GitHub que usam o Linux, o {% data variables.product.prodname_codeql_workflow %} tenta instalar e analisar as dependências do Python, o que pode gerar mais resultados. Para desabilitar a instalação automática, adicione `setup-python-dependencies: false` à etapa "Inicializar CodeQL" do fluxo de trabalho. Para obter mais informações sobre a configuração da análise de dependências do Python, consulte "[Analisar as dependências do Python](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)".
-
-{% endif %}
-
 ### Error: "Erro do servidor"
 
 Se a execução de um fluxo de trabalho para {% data variables.product.prodname_code_scanning %} falhar devido a um erro no servidor, tente executar o fluxo de trabalho novamente. Se o problema persistir, entre em contato com {% data variables.contact.contact_support %}.
 
 ### Erro: "Fora do disco" ou "Sem memória"
-Em projetos muito grandes,
 
-{% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor.
-{% if currentVersion == "free-pro-team@latest" %}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 %}
+Em projetos muito grandes, {% data variables.product.prodname_codeql %} pode ficar ficar sem disco ou sem memória no executor do {% data variables.product.prodname_actions %} hospedado. Se você encontrar esse problema, tente aumentar a memória no executor.
 
 ### Aviso: "git checkout HEAD^2 is no longer necessary"
 
@@ -144,29 +137,29 @@ commit for best results.
 Corrija isto removendo as seguintes linhas do fluxo de trabalho {% data variables.product.prodname_codeql %}. Essas linhas foram incluídas na seção `etapas` do trabalho `Analyze` nas versões iniciais do fluxo de trabalho de {% data variables.product.prodname_codeql %}.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 A seção revisada de `etapas` do fluxo de trabalho será parecida com esta:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 Para obter mais informações sobre a edição do arquivo de fluxo de trabalho {% data variables.product.prodname_codeql %}, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)".
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index b1efa03fe9..737d592743 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -19,11 +21,11 @@ O {% data variables.product.prodname_dotcom %} cria alertas de {% data variables
 
 Você pode gerar arquivos SARIF usando muitas ferramentas de teste de segurança de análise estática, incluindo {% data variables.product.prodname_codeql %}. Para fazer o upload dos resultados das ferramentas de terceiros, você deve usar o formato Intercâmbio de Resultados de Análise Estática (SARIF) 2.1.0. Para obter mais informações, consulte "[Suporte SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)".
 
-Você pode fazer o upload dos resultados usando {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2. 2" %} (disponível se sua organização participa do programa beta){% endif %}, a API de {% data variables.product.prodname_code_scanning %} ou {% data variables.product.prodname_codeql_runner %}. O melhor método de upload dependerá de como você gera o arquivo SARIF. Por exemplo, se você usar:
+Você pode fazer o upload dos resultados usando {% data variables.product.prodname_actions %} (disponível se a sua organização estiver participando do programa beta), a API de {% data variables.product.prodname_code_scanning %} ou {% data variables.product.prodname_codeql_runner %}. O melhor método de upload dependerá de como você gera o arquivo SARIF. Por exemplo, se você usar:
 
 - {% data variables.product.prodname_actions %} para executar a ação {% data variables.product.prodname_codeql %}, não haverá nenhuma ação adicional necessária. A ação {% data variables.product.prodname_codeql %} faz o upload do arquivo SARIF automaticamente quando ele conclui a análise.
 - O arquivo SARIF pode ser gerado a partir de uma ferramenta de análise compatível com o SARIF, que você executa no mesmo fluxo de trabalho de {% data variables.product.prodname_actions %} usado para fazer o upload do arquivo.
-- {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
+- {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. Se você bloquear o envio automático, quando você estiver pronto para enviar resultados, você poderá usar o comando `upload` (para mais informações, consulte "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
 - Uma ferramenta que gera resultados como um artefato fora do seu repositório, você pode usar a API de {% data variables.product.prodname_code_scanning %} para fazer o upload do arquivo (para mais informações, consulte "[Enviar uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
@@ -36,7 +38,7 @@ O seu fluxo de trabalho precisará usar a ação `upload-sarif`, que tem parâme
 
 A ação `upload-sarif` pode ser configurada para ser executada quando ocorrem o evento `push` e `agendado`. Para obter mais informações sobre eventos do {% data variables.product.prodname_actions %}, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-Se o seu arquivo SARIF não incluir `partialFingerprints`, a ação `upload-sarif` calculará o campo `parcialFingerprints` para você e tentará evitar alertas duplicados. O {% data variables.product.prodname_dotcom %} só pode criar `partialFingerprints` quando o repositório contiver o arquivo SARIF e o código-fonte usado na análise estática. For more information about preventing duplicate alerts, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)."
+Se o seu arquivo SARIF não incluir `partialFingerprints`, a ação `upload-sarif` calculará o campo `parcialFingerprints` para você e tentará evitar alertas duplicados. O {% data variables.product.prodname_dotcom %} só pode criar `partialFingerprints` quando o repositório contiver o arquivo SARIF e o código-fonte usado na análise estática. Para obter mais informações sobre a prevenção de alertas duplicados, consulte "[suporte SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)".
 
 {% data reusables.code-scanning.upload-sarif-alert-limit %}
 
@@ -58,20 +60,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Exemplo de fluxo de trabalho que executa a ferramenta de análise ESLint
@@ -82,7 +86,7 @@ Este exemplo de fluxo de trabalho é executado sempre que os commits são carreg
 
 O fluxo de trabalho mostra um exemplo de execução da ferramenta de análise estática ESLint como uma etapa de um fluxo de trabalho. A etapa `Executar ESLint` executa a ferramenta ESLint e produz o arquivo `results.sarif`. Em seguida, o fluxo de trabalho faz o upload do arquivo `results.sarif` para {% data variables.product.prodname_dotcom %} usando a ação `upload-sarif`. Para obter mais informações sobre a criação de um arquivo de fluxo de trabalho, consulte "[Introdução ao GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -90,28 +94,31 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Leia mais
 
 - "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
 - "[Visualizar o seu histórico de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)"
+- "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)"
 - "[Fazer o upload de uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index d59047cd52..40b4a2cd1f 100644
--- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/pt-BR/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/pt-BR/content/github/getting-started-with-github/about-git-subtree-merges.md
index b5a4ababab..7dc1f2dea6 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 Normalmente, um merge de subárvore é usado para conter um repositório dentro de outro repositório. O "sub-repositório" é armazenado em uma pasta do repositório principal.
 
 A melhor maneira de explicar merges de subárvore é mostrar com exemplo. O que faremos:
diff --git a/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md
index d531dd9d64..249b74577d 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/about-github-advanced-security.md
@@ -38,7 +38,7 @@ O administrador do site deve habilitar
 {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de poder utilizar estas funcionalidades. Para obter mais informações, consulte "[Configurar funcionalidades avançadas de segurança](/admin/configuration/configuring-advanced-security-features)".
 {% endif %}
 
-Após configurar o sistema, você poderá habilitar e desabilitar esses recursos no nível da organização ou repositório. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+Após configurar o sistema, você poderá habilitar e desabilitar esses recursos no nível da organização ou repositório. Para mais informações, consulte "[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)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".
 
 {% endif %}
 
@@ -47,7 +47,7 @@ Após configurar o sistema, você poderá habilitar e desabilitar esses recursos
 
 Para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}, Essas funcionalidades estão permanentemente habilitadas e só podem ser desabilitadas se você alterar a visibilidade do projeto para que o código não seja mais público.
 
-Para outros repositórios, uma vez que você tenha uma licença da conta corporativa, é possível habilitar e desabilitar essas funcionalidades no nível da organização ou repositório. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+Para outros repositórios, uma vez que você tenha uma licença da conta corporativa, é possível habilitar e desabilitar essas funcionalidades no nível da organização ou repositório. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para obter mais informações, consulte "[Gerenciar as configurações de segurança e análise de sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %}
 
 {% endif %}
 
@@ -60,12 +60,12 @@ Se você tem uma conta corporativa, a utilização da licença para toda a empre
 
 ### Leia mais
 
-- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)"
+- "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)"
 
 {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 
 ### Leia mais
 
-- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
+- "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/github/getting-started-with-github/about-remote-repositories.md b/translations/pt-BR/content/github/getting-started-with-github/about-remote-repositories.md
index b6cbdf5675..4efe59a62f 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/about-remote-repositories.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/about-remote-repositories.md
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/which-remote-url-should-i-use
   - /github/using-git/which-remote-url-should-i-use
   - /github/using-git/about-remote-repositories
-intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.'
+intro: 'A abordagem colaborativa do GitHub para o desenvolvimento depende da publicação de commits do seu repositório local para {% data variables.product.product_name %} para que outras pessoas visualizem, façam buscas e atualizações.'
 versions:
   free-pro-team: '*'
   enterprise-server: '*'
@@ -17,7 +17,7 @@ versions:
 
 ### Sobre repositórios remotos
 
-Uma URL remota é outra forma de o Git dizer "o lugar onde seu código é armazenado". That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
+Uma URL remota é outra forma de o Git dizer "o lugar onde seu código é armazenado". A URL poderia ser seu repositório no GitHub, ou a bifurcação de outro usuário, ou até mesmo em um servidor totalmente diferente.
 
 Você pode fazer push apenas de dois tipos de endereço URL:
 
@@ -26,7 +26,7 @@ Você pode fazer push apenas de dois tipos de endereço URL:
 
 O Git associa uma URL remota a um nome, e seu remote padrão geralmente é chamado de `origin`.
 
-### Creating remote repositories
+### Criar repositórios remotos
 
 Você pode usar o comando `git remote add` para corresponder uma URL remota a um nome. Por exemplo, você digitaria o seguinte na linha de comando:
 
@@ -38,13 +38,13 @@ Isso associa o nome `origin` ao `URL_REMOTO`.
 
 É possível usar o comando `git remote set-url` para [alterar uma URL de remote](/github/getting-started-with-github/managing-remote-repositories).
 
-### Choosing a URL for your remote repository
+### Escolher uma URL para o seu repositório remoto
 
 Existem várias maneiras de clonar repositórios disponíveis no {% data variables.product.product_location %}.
 
 Quando você visualiza um repositório conectado à sua conta, as URLs que podem ser usadas para clonar o projeto no computador ficam disponíveis abaixo dos detalhes do repositório.
 
-For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Para obter informações sobre a configuração ou alteração da URL remota, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 ### Clonando com as URLs de HTTPS
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/be-social.md b/translations/pt-BR/content/github/getting-started-with-github/be-social.md
index 57ef5b1c3b..15a531bc30 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/be-social.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/be-social.md
@@ -38,6 +38,10 @@ Clique em **Watch** (Inspecionar) no topo de um repositório para inspecioná-lo
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### Mais ação
 
 #### Criar pull requests
@@ -68,8 +72,8 @@ Agora você está conectado à comunidade do {% data variables.product.product_n
 
 ![Marcar um projeto com estrela](/assets/images/help/stars/star-a-project.png)
 
-- [Configurar o Git](/articles/set-up-git)
-- [Criar um repositório](/articles/create-a-repo)
-- [Bifurcar um repositório](/articles/fork-a-repo)
+- "[Configurar o Git](/articles/set-up-git)"
+- "[Criar um repositório](/articles/creating-a-new-repository)"
+- "[Bifurcar um repositório](/articles/fork-a-repo)"
 - **Interações sociais**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/pt-BR/content/github/getting-started-with-github/caching-your-github-credentials-in-git.md b/translations/pt-BR/content/github/getting-started-with-github/caching-your-github-credentials-in-git.md
index 2fc2d5139c..107d7ca5c1 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/caching-your-github-credentials-in-git.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/caching-your-github-credentials-in-git.md
@@ -5,7 +5,7 @@ redirect_from:
   - /articles/caching-your-github-password-in-git
   - /github/using-git/caching-your-github-password-in-git
   - /github/using-git/caching-your-github-credentials-in-git
-intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), you can use a credential helper to tell Git to remember your credentials.'
+intro: 'Se você estiver [clonando repositórios de {% data variables.product.product_name %} usando HTTPS](/github/getting-started-with-github/about-remote-repositories), você poderá usar um auxiliar de credenciais para dizer ao Git para lembrar suas credenciais.'
 versions:
   free-pro-team: '*'
   enterprise-server: '*'
diff --git a/translations/pt-BR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/pt-BR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index 53708bf5df..9df96381ec 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 Toda vez que você pressionar <kbd>retornar</kbd> no seu teclado, você insere um caractere invisível denominado delimitador. Os diferentes sistemas operacionais gerenciam os delimitadores de formas diferentes.
 
-Ao colaborar em projetos com Git e {% data variables.product.product_name %}, o Git pode produzir resultados inesperados se, por exemplo, você estiver trabalhando em uma máquina que use o Windows e o seu colaborador dizer uma mudança no OS X.
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 Você pode configurar o Git para gerenciar os delimitadores automaticamente para que você possa colaborar efetivamente com pessoas que usam diferentes sistemas operacionais.
 
@@ -25,11 +25,11 @@ O comando `git config core.autocrlf` é utilizado para alterar a forma como o Gi
 
 {% mac %}
 
-No OS X, você simplesmente introduz `input` (entrada) na configuração. Por exemplo:
+On macOS, you simply pass `input` to the configuration. Por exemplo:
 
 ```shell
 $ git config --global core.autocrlf input
-# Configure Git to ensure line endings in files you checkout are correct for OS X
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md b/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md
index 4610f5d1c3..8a0ef213fc 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/create-a-repo.md
@@ -15,6 +15,8 @@ topics:
   - Accounts
 ---
 
+### Criar um repositório
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 Você pode armazenar vários projetos nos repositórios do {% data variables.product.product_name %}, incluindo projetos de código aberto. Com os [projetos de código aberto](http://opensource.org/about), é possível compartilhar código para criar softwares melhores e mais confiáveis.
@@ -29,7 +31,7 @@ Você pode armazenar uma série de projetos em repositórios de {% data variable
 
 {% note %}
 
-**Observação:** você pode criar repositórios públicos para um projeto de código aberto. Ao criar um repositório público, certifique-se de incluir um [arquivo de licença](http://choosealicense.com/) que determina como deseja que seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
+**Observação:** você pode criar repositórios públicos para um projeto de código aberto. Ao criar um repositório público, certifique-se de incluir um [arquivo de licença](https://choosealicense.com/) que determina como deseja que seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md b/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md
index 9a91fcaa08..0a23fafa86 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### Sobre bifurcações
+
 O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia.
 
 #### Proponha mudanças no projeto de outra pessoa
@@ -34,7 +36,7 @@ Para obter mais informações sobre a aplicação dos princípios de código abe
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-Ao criar um repositório público a partir de uma bifurcação do projeto de outra pessoa, confirme que incluiu um arquivo de licença que estabelece como você quer que seu projeto seja compartilhado com outros. Para obter mais informações, consulte [Escolha uma licença de código aberto](http://choosealicense.com/)" em choosealicense.com.
+Ao criar um repositório público a partir de uma bifurcação do projeto de outra pessoa, confirme que incluiu um arquivo de licença que estabelece como você quer que seu projeto seja compartilhado com outros. Para obter mais informações, consulte [Escolha uma licença de código aberto](https://choosealicense.com/)" em choosealicense.com.
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
@@ -154,5 +156,6 @@ Você já bifurcou um repositório, treinou clonar sua bifurcação e configurou
 
 - "[Configurar o Git](/articles/set-up-git)"
 - "[Criar um repositório](/articles/creating-a-new-repository)"
+- **Bifurcar um repositório**
 - "[Socializar](/articles/be-social)"
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/pt-BR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/pt-BR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index cc94e84b8e..a27c5f8790 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 Esses comandos são muito úteis ao interagir com [um repositório remote](/github/getting-started-with-github/about-remote-repositories). `clone` e `fetch` baixam códigos remote de uma URL remota do repositório para seu computador, `merge` é usado para mesclar o trabalho de diferentes pessoas com o seu e `pull` é uma combinação de `fetch` e `merge`.
 
 ### Clonar um repositório
@@ -39,14 +41,14 @@ Para cada branch `foo` no repositório remote, um branch de acompanhamento remot
 
 Use `git fetch` para recuperar trabalhos novos feitos por outra pessoas. Fazer fetch de um repositório captura todos os branches de acompanhamento remoto e tags novos *sem* fazer merge dessas alterações em seus próprios branches.
 
-If you already have a local repository with a remote URL set up for the desired project, you can grab all the new information by using `git fetch *remotename*` in the terminal:
+Se você já tem um repositório local com uma URL remota configurada para o projeto desejado, você pode pegar todas as novas informações usando `git buscar *remotename*` no terminal:
 
 ```shell
 $ git fetch <em>remotename</em>
 # Faz fetch de atualizações feitas em um repositório remote
 ```
 
-Otherwise, you can always add a new remote and then fetch. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Caso contrário, você sempre pode adicionar um novo remoto e, em seguida, procurar. Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 ### Fazer merge de alterações em seu branch local
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/getting-started-with-git.md b/translations/pt-BR/content/github/getting-started-with-github/getting-started-with-git.md
index 621b181b4c..6447d2d66d 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/getting-started-with-git.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/getting-started-with-git.md
@@ -1,5 +1,5 @@
 ---
-title: Getting started with Git
+title: Primeiros passos com o Git
 intro: ''
 mapTopic: true
 redirect_from:
diff --git a/translations/pt-BR/content/github/getting-started-with-github/git-workflows.md b/translations/pt-BR/content/github/getting-started-with-github/git-workflows.md
index d5669046ba..f8329d41ba 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-Você pode adotar o método de fluxo {% data variables.product.prodname_dotcom %} para padronizar o funcionamento e a colaboração da sua equipe no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Fluxo do GitHub](/github/collaborating-with-issues-and-pull-requests/github-flow)" e "[Entender o fluxo de GitHub](http://guides.github.com/overviews/flow/)" nos guias do {% data variables.product.prodname_dotcom %}.
+Você pode adotar o método de fluxo {% data variables.product.prodname_dotcom %} para padronizar o funcionamento e a colaboração da sua equipe no {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/pt-BR/content/github/getting-started-with-github/github-flow.md b/translations/pt-BR/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..92d06d5f5d
--- /dev/null
+++ b/translations/pt-BR/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: Fluxo do GitHub
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### Introdução
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### Pré-requisitos
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)".
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### Criar um pull request
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. Para obter mais informações, consulte "[Criar uma pull request](/articles/creating-a-pull-request)".
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. Para obter mais informações, consulte "[Sobre verificações de status](/github/collaborating-with-issues-and-pull-requests/about-status-checks)".
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. Sua pull request atualizará automaticamente.
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. Para obter mais informações, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request)".
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. Para obter mais informações, consulte "[Solucionar conflitos de merge](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)."
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md
index 3e8fc9ac0a..1b1acd659a 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ Você pode estar conectado simultaneamente em um celular com uma conta de usuár
 
 Você precisa instalar {% data variables.product.prodname_mobile %} 1.4 ou superior no seu dispositivo para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}.
 
-Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. Para obter mais informações, consulte "[Notas de versão](/enterprise-server/admin/release-notes)" e "[Gerenciar {% data variables.product.prodname_mobile %} para a sua empresa](/admin/configuration/managing-github-for-mobile-for-your-enterprise)".
+Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 Durante o beta para {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, você deve estar conectado com uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}.
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/github-language-support.md b/translations/pt-BR/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/pt-BR/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md b/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md
index f315be6320..4f50d98d89 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 O {% data variables.product.prodname_dotcom %} oferece produtos grátis e pagos. Você pode ver o preço e uma lista completa dos recursos de cada produto em <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %}
 
 ### {% data variables.product.prodname_free_user %} para contas de usuário
@@ -99,14 +101,3 @@ O {% data variables.product.prodname_ghe_cloud %} também inclui:
 Você pode configurar uma versão para avaliar o {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}</a>".
 
 Para obter mais informações sobre hospedar sua própria instância do [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), entre em contato com {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-O {% data variables.product.prodname_ghe_one %} inclui [{% data variables.product.prodname_enterprise %}](#github-enterprise), mais:
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning){% endif %}
-- [{% data variables.product.prodname_learning %} para organizações](https://lab.github.com/organizations)
-
-Para obter mais informações sobre a inscrição para {% data variables.product.prodname_ghe_one %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/pt-BR/content/github/getting-started-with-github/index.md b/translations/pt-BR/content/github/getting-started-with-github/index.md
index 5cf8a0b0d8..30b3996d04 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/index.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md
index 2983f732dc..64f7e2158b 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'Nearly every page on {% data variables.product.product_name %} has a keyboard shortcut to perform actions faster.'
+title: Atalhos de teclado
+intro: 'Quase todas as páginas no {% data variables.product.product_name %} tem um atalho de teclado que executa as ações mais rapidamente.'
 redirect_from:
   - /articles/using-keyboard-shortcuts/
   - /categories/75/articles/
@@ -13,186 +13,193 @@ versions:
 ---
 
 
-### About keyboard shortcuts
+### Sobre atalhos do teclado
 
-Typing <kbd>?</kbd> in {% data variables.product.product_name %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate.
+Digitar <kbd>?</kbd> no {% data variables.product.product_name %} exibe uma caixa de diálogo que lista os atalhos de teclado disponíveis para aquela página. Você pode usar esses atalhos de teclado para executar ações no site sem precisar usar o mouse para navegar.
 
-Below is a list of some of the available keyboard shortcuts.
+Veja abaixo uma lista dos atalhos de teclado disponíveis.
 
-### Site wide shortcuts
+### Atalhos para o site
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>s</kbd> or <kbd>/</kbd> | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/articles/about-searching-on-github)."
-|<kbd>g</kbd> <kbd>n</kbd> | Go to your notifications. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
-|<kbd>esc</kbd> | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in
+| Atalho                       | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>s</kbd> or <kbd>/</kbd> | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/articles/about-searching-on-github)".                                                                                                                                                                                                                                                                |
+| <kbd>g</kbd> <kbd>n</kbd>    | Vai para suas notificações. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." |
+| <kbd>esc</kbd>               | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está                                                                                                                                                                                                                                                                                            |
 
-### Repositories
+### Repositórios
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>g</kbd> <kbd>c</kbd> | Go to the **Code** tab
-|<kbd>g</kbd> <kbd>i</kbd> | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)."
-|<kbd>g</kbd> <kbd>p</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-|<kbd>g</kbd> <kbd>a</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
-|<kbd>g</kbd> <kbd>b</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."
-|<kbd>g</kbd> <kbd>w</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/articles/about-wikis)."
+| Atalho                    | Descrição                                                                                                                                                                                                                          |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>g</kbd> <kbd>c</kbd> | Vai para a aba **Code** (Código)                                                                                                                                                                                                   |
+| <kbd>g</kbd> <kbd>i</kbd> | Vai para a aba **Issues** (Problemas). Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)".                                                                                                          |
+| <kbd>g</kbd> <kbd>p</kbd> | Vai para a aba **Pull requests**. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+| <kbd>g</kbd> <kbd>a</kbd> | Acesse a aba de **Ações**. Para obter mais informações, consulte "[Sobre ações](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %}
+| <kbd>g</kbd> <kbd>b</kbd> | Vai para a aba **Projects** (Projetos). Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)".                                                                                        |
+| <kbd>g</kbd> <kbd>w</kbd> | Vai para a aba **Wiki**. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
-### Source code editing
+### Edição de código-fonte
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>e</kbd> | Open source code file in the **Edit file** tab
-|<kbd>control f</kbd> or <kbd>command f</kbd> | Start searching in file editor
-|<kbd>control g</kbd> or <kbd>command g</kbd> | Find next
-|<kbd>shift control g</kbd> or <kbd>shift command g</kbd> | Find previous
-|<kbd>shift control f</kbd> or <kbd>command option f</kbd> | Replace
-|<kbd>shift control r</kbd> or <kbd>shift command option f</kbd> | Replace all
-|<kbd>alt g</kbd> | Jump to line
-|<kbd>control z</kbd> or <kbd>command z</kbd> | Undo
-|<kbd>control y</kbd> or <kbd>command y</kbd> | Redo
-|<kbd>cmd + shift + p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
+| Atalho                                                          | Descrição                                                                                         |
+| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| <kbd>control b</kbd> ou <kbd>command b</kbd>                    | Insere formatação Markdown para texto em negrito                                                  |
+| <kbd>control i</kbd> ou <kbd>command i</kbd>                    | Insere formatação Markdown para texto em itálico                                                  |
+| <kbd>control k</kbd> ou <kbd>command k</kbd>                    | Insere formatação Markdown para criar um link                                                     |
+| <kbd>e</kbd>                                                    | Abra o arquivo de código-fonte na aba **Editar arquivo**                                          |
+| <kbd>control f</kbd> ou <kbd>command f</kbd>                    | Começa a pesquisar no editor de arquivo                                                           |
+| <kbd>control g</kbd> ou <kbd>command g</kbd>                    | Localiza o próximo                                                                                |
+| <kbd>shift control g</kbd> ou <kbd>shift command g</kbd>        | Localiza o anterior                                                                               |
+| <kbd>shift control f</kbd> ou <kbd>command option f</kbd>       | Substitui                                                                                         |
+| <kbd>shift control r</kbd> ou <kbd>shift command option f</kbd> | Substitui todos                                                                                   |
+| <kbd>alt g</kbd>                                                | Pula para linha                                                                                   |
+| <kbd>control z</kbd> ou <kbd>command z</kbd>                    | Desfaz                                                                                            |
+| <kbd>control y</kbd> ou <kbd>command y</kbd>                    | Refaz                                                                                             |
+| <kbd>cmd + shift + p</kbd>                                      | Alterna entre as abas **Edit file** (Editar aquivo) e **Preview changes** (Visualizar alterações) |
+| <kbd>control s</kbd> ou <kbd>comando s</kbd>                    | Escrever uma mensagem de commit                                                                   |
 
-For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
+Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://codemirror.net/doc/manual.html#commands).
 
-### Source code browsing
+### Navegação de código-fonte
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>t</kbd> | Activates the file finder
-|<kbd>l</kbd> | Jump to a line in your code
-|<kbd>w</kbd> | Switch to a new branch or tag
-|<kbd>y</kbd> | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)."
-|<kbd>i</kbd> | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)."
-|<kbd>b</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
+| Atalho       | Descrição                                                                                                                                                                  |
+| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>t</kbd> | Ativa o localizador de arquivos                                                                                                                                            |
+| <kbd>l</kbd> | Pula para uma linha no código                                                                                                                                              |
+| <kbd>w</kbd> | Muda para um novo branch ou tag                                                                                                                                            |
+| <kbd>y</kbd> | Expande a URL para sua forma canônica. Para obter mais informações, consulte "[Obter links permanentes em arquivos](/articles/getting-permanent-links-to-files)".          |
+| <kbd>i</kbd> | Mostra ou oculta comentários em diffs. Para obter mais informações, consulte "[Comentar no diff de uma pull request](/articles/commenting-on-the-diff-of-a-pull-request)". |
+| <kbd>a</kbd> | Exibir ou ocultar anotações em diffs                                                                                                                                       |
+| <kbd>b</kbd> | Abre a vsualização de blame. Para obter mais informações, consulte "[Rastrear alterações em um arquivo](/articles/tracing-changes-in-a-file)".                             |
 
-### Comments
+### Comentários
 
-| Keyboard shortcut | Description
-|-----------|------------
-| <kbd>control b</kbd> or <kbd>command b</kbd> | Inserts Markdown formatting for bolding text
-| <kbd>control i</kbd> or <kbd>command i</kbd> | Inserts Markdown formatting for italicizing text
-| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link
-| <kbd>control shift p</kbd> or <kbd>command shift p</kbd>| Toggles between the **Write** and **Preview** comment tabs
-| <kbd>control enter</kbd> | Submits a comment
-| <kbd>control .</kbd> and then <kbd>control [saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %}
-|<kbd>control g</kbd> or <kbd>command g</kbd> | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
-| <kbd>r</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
+| Atalho                                                               | Descrição                                                                                                                                                                                                                                      |
+| -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>control b</kbd> ou <kbd>command b</kbd>                         | Insere formatação Markdown para texto em negrito                                                                                                                                                                                               |
+| <kbd>control i</kbd> ou <kbd>command i</kbd>                         | Insere formatação Markdown para texto em itálico                                                                                                                                                                                               |
+| <kbd>control k</kbd> ou <kbd>command k</kbd>                         | Insere formatação Markdown para criar um link                                                                                                                                                                                                  |
+| <kbd>control shift p</kbd> ou <kbd>command shift p</kbd>             | Alterna entre as abas de comentários **Write** (Escrever) e **Preview** (Visualizar)                                                                                                                                                           |
+| <kbd>control enter</kbd>                                             | Envia um comentário                                                                                                                                                                                                                            |
+| <kbd>control .</kbd> e <kbd>control [número de resposta salvo]</kbd> | Abre o menu de respostas salvas e autocompleta o campo de comentário com uma resposta salva. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>control g</kbd> ou <kbd>command g</kbd>                         | Insere uma sugestão. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". 
+{% endif %}
+| <kbd>r</kbd>                                                         | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)".                                                       |
 
-### Issue and pull request lists
+### Listas de problemas e pull requests
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>c</kbd> | Create an issue
-| <kbd>control /</kbd> or <kbd>command /</kbd> | Focus your cursor on the issues or pull requests search bar. For more information, see "[Using search to filter issues and pull requests](/articles/using-search-to-filter-issues-and-pull-requests)."||
-|<kbd>u</kbd> | Filter by author
-|<kbd>l</kbd> | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
-| <kbd>alt</kbd> and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
-|<kbd>m</kbd> | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)."
-|<kbd>a</kbd> | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)."
-|<kbd>o</kbd> or <kbd>enter</kbd> | Open issue
+| Atalho                                       | Descrição                                                                                                                                                                                                                             |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>c</kbd>                                 | Cria um problema                                                                                                                                                                                                                      |
+| <kbd>control /</kbd> ou <kbd>command /</kbd> | Evidencia seu cursor na barra de pesquisa de problemas e pull requests. Para obter mais informações, consulte "[Usar a pesquisa para filtrar problemas e pull requests](/articles/using-search-to-filter-issues-and-pull-requests)".| |
+| <kbd>u</kbd>                                 | Filtra por autor                                                                                                                                                                                                                      |
+| <kbd>l</kbd>                                 | Filtra por ou edita etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)".                                                     |
+| <kbd>alt</kbd> e clique                      | Ao filtrar por etiquetas, exclui etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)".                                        |
+| <kbd>m</kbd>                                 | Filtra por ou edita marcos. Para obter mais informações, consulte "[Filtrar problemas e pull requests por marcos](/articles/filtering-issues-and-pull-requests-by-milestone)".                                                        |
+| <kbd>a</kbd>                                 | Filtra por ou edita um responsável. Para obter mais informações, consulte "[Filtrar problemas e pull requests por responsáveis](/articles/filtering-issues-and-pull-requests-by-assignees)".                                          |
+| <kbd>o</kbd> ou <kbd>enter</kbd>             | Abre um problema                                                                                                                                                                                                                      |
 
-### Issues and pull requests
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>q</kbd> | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)."
-|<kbd>m</kbd> | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)."
-|<kbd>l</kbd> | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)."
-|<kbd>a</kbd> | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)."
-|<kbd>cmd + shift + p</kbd> or <kbd>control + shift + p</kbd> | Toggles between the **Write** and **Preview** tabs
+### Problemas e pull requests
+| Atalho                                                       | Descrição                                                                                                                                                                                                                              |
+| ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>q</kbd>                                                 | Solicita um revisor. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review/)".                                                                                     |
+| <kbd>m</kbd>                                                 | Define um marco. Para obter mais informações, consulte "[Associar marcos a problemas e pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)".                                                               |
+| <kbd>l</kbd>                                                 | Aplica uma etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests/)".                                                                  |
+| <kbd>a</kbd>                                                 | Define um responsável. Para obter mais informações, consulte "[Atribuir problemas e pull requests a outros usuários {% data variables.product.company_short %}](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". |
+| <kbd>cmd + shift + p</kbd> ou <kbd>control + shift + p</kbd> | Alterna entre as abas **Write** (Escrever) e **Preview** (Visualizar)                                                                                                                                                                  |
 
-### Changes in pull requests
+### Alterações em pull requests
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>c</kbd> | Open the list of commits in the pull request
-|<kbd>t</kbd> | Open the list of changed files in the pull request
-|<kbd>j</kbd> | Move selection down in the list
-|<kbd>k</kbd> | Move selection up in the list
-| <kbd>cmd + shift + enter </kbd> | Add a single comment on a pull request diff |
-| <kbd>alt</kbd> and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
-| Click, then <kbd>shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %}
+| Atalho                                       | Descrição                                                                                                                                                                                                                                                                                                                                                                  |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>c</kbd>                                 | Abre a lista de commits na pull request                                                                                                                                                                                                                                                                                                                                    |
+| <kbd>t</kbd>                                 | Abre a lista de arquivos alterados na pull request                                                                                                                                                                                                                                                                                                                         |
+| <kbd>j</kbd>                                 | Move a seleção para baixo na lista                                                                                                                                                                                                                                                                                                                                         |
+| <kbd>k</kbd>                                 | Move a seleção para cima na lista                                                                                                                                                                                                                                                                                                                                          |
+| <kbd>cmd + shift + enter </kbd>              | Adiciona um comentário único no diff da pull request                                                                                                                                                                                                                                                                                                                       |
+| <kbd>alt</kbd> e clique                      | Alterna entre recolhimento e expansão de todos os comentários de revisão desatualizados em um pull request, mantendo pressionada a tecla `alt` e clicando em **Mostrar desatualizados** ou **Ocultar desatualizados**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+| Clique, em seguida <kbd>shift</kbd> e clique | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado <kbd>shift</kbd>, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."
+{% endif %}
 
-### Project boards
+### Quadros de projeto
 
-#### Moving a column
+#### Mover uma coluna
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>enter</kbd> or <kbd>space</kbd> | Start moving the focused column
-|<kbd>escape</kbd> | Cancel the move in progress
-|<kbd>enter</kbd> | Complete the move in progress
-|<kbd>←</kbd> or <kbd>h</kbd> | Move column to the left
-|<kbd>command + ←</kbd> or <kbd>command + h</kbd> or <kbd>control + ←</kbd> or <kbd>control + h</kbd> | Move column to the leftmost position
-|<kbd>→</kbd> or <kbd>l</kbd> | Move column to the right
-|<kbd>command + →</kbd> or <kbd>command + l</kbd> or <kbd>control + →</kbd> or <kbd>control + l</kbd> | Move column to the rightmost position
+| Atalho                                                                                               | Descrição                                    |
+| ---------------------------------------------------------------------------------------------------- | -------------------------------------------- |
+| <kbd>enter</kbd> ou <kbd>space</kbd>                                                                 | Começa a mover a coluna em evidência         |
+| <kbd>escape</kbd>                                                                                    | Cancela o movimento em curso                 |
+| <kbd>enter</kbd>                                                                                     | Completa o movimento em curso                |
+| <kbd>←</kbd> ou <kbd>h</kbd>                                                                         | Move a coluna para a esquerda                |
+| <kbd>command + ←</kbd> ou <kbd>command + h</kbd> ou <kbd>control + ←</kbd> ou <kbd>control + h</kbd> | Move a coluna para a posição mais à esquerda |
+| <kbd>→</kbd> ou <kbd>l</kbd>                                                                         | Move a coluna para a direita                 |
+| <kbd>command + →</kbd> ou <kbd>command + l</kbd> ou <kbd>control + →</kbd> ou <kbd>control + l</kbd> | Move a coluna para a posição mais à direita  |
 
-#### Moving a card
+#### Mover um cartão
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>enter</kbd> or <kbd>space</kbd> | Start moving the focused card
-|<kbd>escape</kbd> | Cancel the move in progress
-|<kbd>enter</kbd> | Complete the move in progress
-|<kbd>↓</kbd> or <kbd>j</kbd> | Move card down
-|<kbd>command + ↓</kbd> or <kbd>command + j</kbd> or <kbd>control + ↓</kbd> or <kbd>control + j</kbd> | Move card to the bottom of the column
-|<kbd>↑</kbd> or <kbd>k</kbd> | Move card up
-|<kbd>command + ↑</kbd> or <kbd>command + k</kbd> or <kbd>control + ↑</kbd> or <kbd>control + k</kbd> | Move card to the top of the column
-|<kbd>←</kbd> or <kbd>h</kbd> | Move card to the bottom of the column on the left
-|<kbd>shift + ←</kbd> or <kbd>shift + h</kbd> | Move card to the top of the column on the left
-|<kbd>command + ←</kbd> or <kbd>command + h</kbd> or <kbd>control + ←</kbd> or <kbd>control + h</kbd> | Move card to the bottom of the leftmost column
-|<kbd>command + shift + ←</kbd> or <kbd>command + shift + h</kbd> or <kbd>control + shift + ←</kbd> or <kbd>control + shift + h</kbd> | Move card to the top of the leftmost column
-|<kbd>→</kbd> | Move card to the bottom of the column on the right
-|<kbd>shift + →</kbd> or <kbd>shift + l</kbd> | Move card to the top of the column on the right
-|<kbd>command + →</kbd> or <kbd>command + l</kbd> or <kbd>control + →</kbd> or <kbd>control + l</kbd> | Move card to the bottom of the rightmost column
-|<kbd>command + shift + →</kbd> or <kbd>command + shift + l</kbd> or <kbd>control + shift + →</kbd> or <kbd>control + shift + l</kbd> | Move card to the bottom of the rightmost column
+| Atalho                                                                                                                               | Descrição                                                     |
+| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- |
+| <kbd>enter</kbd> ou <kbd>space</kbd>                                                                                                 | Começa a mover o cartão em evidência                          |
+| <kbd>escape</kbd>                                                                                                                    | Cancela o movimento em curso                                  |
+| <kbd>enter</kbd>                                                                                                                     | Completa o movimento em curso                                 |
+| <kbd>↓</kbd> ou <kbd>j</kbd>                                                                                                         | Move o cartão para baixo                                      |
+| <kbd>command + ↓</kbd> ou <kbd>command + j</kbd> ou <kbd>control + ↓</kbd> ou <kbd>control + j</kbd>                                 | Move o cartão para a parte inferior da coluna                 |
+| <kbd>↑</kbd> ou <kbd>k</kbd>                                                                                                         | Move o cartão para cima                                       |
+| <kbd>command + ↑</kbd> ou <kbd>command + k</kbd> ou <kbd>control + ↑</kbd> ou <kbd>control + k</kbd>                                 | Move o cartão para a parte superior da coluna                 |
+| <kbd>←</kbd> ou <kbd>h</kbd>                                                                                                         | Move o cartão para a parte inferior da coluna à esquerda      |
+| <kbd>shift + ←</kbd> ou <kbd>shift + h</kbd>                                                                                         | Move o cartão para a parte superior da coluna à esquerda      |
+| <kbd>command + ←</kbd> ou <kbd>command + h</kbd> ou <kbd>control + ←</kbd> ou <kbd>control + h</kbd>                                 | Move o cartão para a parte inferior da coluna mais à esquerda |
+| <kbd>command + shift + ←</kbd> ou <kbd>command + shift + h</kbd> ou <kbd>control + shift + ←</kbd> ou <kbd>control + shift + h</kbd> | Move o cartão para a parte superior da coluna mais à esquerda |
+| <kbd>→</kbd>                                                                                                                         | Move o cartão para a parte inferior da coluna à direita       |
+| <kbd>shift + →</kbd> ou <kbd>shift + l</kbd>                                                                                         | Move o cartão para a parte superior da coluna à direita       |
+| <kbd>command + →</kbd> ou <kbd>command + l</kbd> ou <kbd>control + →</kbd> ou <kbd>control + l</kbd>                                 | Move o cartão para a parte inferior da coluna mais à direita  |
+| <kbd>command + shift + →</kbd> ou <kbd>command + shift + l</kbd> ou <kbd>control + shift + →</kbd> ou <kbd>control + shift + l</kbd> | Move o cartão para a parte inferior da coluna mais à direita  |
 
-#### Previewing a card
+#### Pré-visualizar um cartão
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>esc</kbd> | Close the card preview pane
+| Atalho         | Descrição                                |
+| -------------- | ---------------------------------------- |
+| <kbd>esc</kbd> | Fecha o painel de visualização do cartão |
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### {% data variables.product.prodname_actions %}
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>command + space </kbd> or <kbd>control + space</kbd> | In the workflow editor, get suggestions for your workflow file.
-|<kbd>g</kbd> <kbd>f</kbd> | Go to the workflow file
-|<kbd>shift + t</kbd> or <kbd>T</kbd> | Toggle timestamps in logs
-|<kbd>shift + f</kbd> or <kbd>F</kbd> | Toggle fullscreen logs
-|<kbd>esc</kbd> | Exit fullscreen logs
+| Atalho                                                    | Descrição                                                                            |
+| --------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| <kbd>command + space </kbd> ou <kbd>control + space</kbd> | No editor de fluxo de trabalho, obtém sugestões para o arquivo de fluxo de trabalho. |
+| <kbd>g</kbd> <kbd>f</kbd>                                 | Acesse o arquivo do fluxo de trabalho                                                |
+| <kbd>shift + t</kbd> or <kbd>T</kbd>                      | Alternar as marcas de tempo nos registros                                            |
+| <kbd>shift + f</kbd> ou <kbd>F</kbd>                      | Alternar os registros em tela cheia                                                  |
+| <kbd>esc</kbd>                                            | Sair dos registros em tela cheia                                                     |
 
 {% endif %}
 
-### Notifications
-
+### Notificações
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>e</kbd> | Mark as done
-| <kbd>shift + u</kbd>| Mark as unread
-| <kbd>shift + i</kbd>| Mark as read
-| <kbd>shift + m</kbd> | Unsubscribe
+| Atalho               | Descrição            |
+| -------------------- | -------------------- |
+| <kbd>e</kbd>         | Marcar como pronto   |
+| <kbd>shift + u</kbd> | Marcar como não lido |
+| <kbd>shift + i</kbd> | Marca como lido      |
+| <kbd>shift + m</kbd> | Cancelar assinatura  |
 
 {% else %}
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>e</kbd> or <kbd>I</kbd> or <kbd>y</kbd> | Mark as read
-|<kbd>shift + m</kbd> | Mute thread
+| Atalho                                       | Descrição       |
+| -------------------------------------------- | --------------- |
+| <kbd>e</kbd> ou <kbd>I</kbd> ou <kbd>y</kbd> | Marca como lido |
+| <kbd>shift + m</kbd>                         | Desativa o som  |
 {% endif %}
 
-### Network graph
+### gráfico de rede
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>←</kbd> or <kbd>h</kbd> | Scroll left
-|<kbd>→</kbd> or <kbd>l</kbd> | Scroll right
-|<kbd>↑</kbd> or <kbd>k</kbd> | Scroll up
-|<kbd>↓</kbd> or <kbd>j</kbd> | Scroll down
-|<kbd>shift + ←</kbd> or <kbd>shift + h</kbd> | Scroll all the way left
-|<kbd>shift + →</kbd> or <kbd>shift + l</kbd> | Scroll all the way right
-|<kbd>shift + ↑</kbd> or <kbd>shift + k</kbd> | Scroll all the way up
-|<kbd>shift + ↓</kbd> or <kbd>shift + j</kbd> | Scroll all the way down
+| Atalho                                       | Descrição                        |
+| -------------------------------------------- | -------------------------------- |
+| <kbd>←</kbd> ou <kbd>h</kbd>                 | Rola para a esquerda             |
+| <kbd>→</kbd> ou <kbd>l</kbd>                 | Rola para a direita              |
+| <kbd>↑</kbd> ou <kbd>k</kbd>                 | Rola para cima                   |
+| <kbd>↓</kbd> ou <kbd>j</kbd>                 | Rola para baixo                  |
+| <kbd>shift + ←</kbd> ou <kbd>shift + h</kbd> | Rola até o final para a esquerda |
+| <kbd>shift + →</kbd> ou <kbd>shift + l</kbd> | Rola até o final para a direita  |
+| <kbd>shift + ↑</kbd> ou <kbd>shift + k</kbd> | Rola até o final para cima       |
+| <kbd>shift + ↓</kbd> ou <kbd>shift + j</kbd> | Rola até o final para baixo      |
diff --git a/translations/pt-BR/content/github/getting-started-with-github/learning-about-github.md b/translations/pt-BR/content/github/getting-started-with-github/learning-about-github.md
index 456d22eceb..8600a3cc06 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre o GitHub
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/pt-BR/content/github/getting-started-with-github/managing-remote-repositories.md b/translations/pt-BR/content/github/getting-started-with-github/managing-remote-repositories.md
index 4814789d5f..de74ca3ff8 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/managing-remote-repositories.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/managing-remote-repositories.md
@@ -22,9 +22,9 @@ versions:
   github-ae: '*'
 ---
 
-### Adding a remote repository
+### Adicionar um repositório remoto
 
-To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
+Para adicionar um novo remoto, use o comando `adicionar remoto do git` no terminal do diretório no qual seu repositório está armazenado.
 
 O comando `git remote add` usa dois argumentos:
 * Um nome de remote, por exemplo, `origin`
@@ -42,9 +42,9 @@ $ git remote -v
 > origin  https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (push)
 ```
 
-For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+Para obter mais informações sobre qual URL usar, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
-#### Troubleshooting: Remote origin already exists
+#### Solução de problemas: A origem remota já existe
 
 Esse erro significa que você tentou adicionar um remote com um nome que já existe no repositório local.
 
@@ -55,16 +55,16 @@ $ git remote add origin https://{% data variables.command_line.codeblock %}/octo
 
 Para corrigir isso, é possível:
 * Usar um nome diferente para o novo remote
-* Rename the existing remote repository
-* Delete the existing remote repository
+* Renomeie o repositório remoto existente
+* Exclua o repositório remoto existente
 
-### Changing a remote repository's URL
+### Alterar a URL de um repositório remoto
 
-The `git remote set-url` command changes an existing remote repository URL.
+O comando `git remote set-url` altera a URL de um repositório remoto existente.
 
 {% tip %}
 
-**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+**Dica:** Para obter informações sobre a diferença entre as URLs de HTTPS e SSH, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
 {% endtip %}
 
@@ -129,7 +129,7 @@ Você pode [usar um auxiliar de credenciais](/github/getting-started-with-github
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-#### Troubleshooting: No such remote '[name]'
+#### Solução de problemas: Não há tal '[name]' remoto '
 
 Este erro informa que o remote que você tentou alterar não existe:
 
@@ -140,9 +140,9 @@ $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/
 
 Verifique se você inseriu corretamente o nome do remote.
 
-### Renaming a remote repository
+### Renomear um repositório remoto
 
-Use the `git remote rename` command to rename an existing remote.
+Use o comando `renomear o remoto do git` para renomear um remoto existente.
 
 O comando `git remote rename` tem dois argumentos:
 * O nome de um remote existente, como `origin`
@@ -167,7 +167,7 @@ $ git remote -v
 > destination  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 ```
 
-#### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]'
+#### Solução de problemas: Não foi possível renomear a seção de configuração 'remote.[old name]' para 'remote.[new name]'
 
 Esse erro informa que o nome do remote antigo que você inseriu não existe.
 
@@ -180,13 +180,13 @@ $ git remote -v
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 ```
 
-#### Troubleshooting: Remote [new name] already exists
+#### Solução de problemas: Já existe um [new name] remoto
 
-Esse erro informa que o nome de remote que você deseja usar já existe. To solve this, either use a different remote name, or rename the original remote.
+Esse erro informa que o nome de remote que você deseja usar já existe. Para resolver isso, use um nome remoto diferente ou renomeie o remoto original.
 
-### Removing a remote repository
+### Remover um repositório remoto
 
-Use the `git remote rm` command to remove a remote URL from your repository.
+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`
@@ -217,7 +217,7 @@ $ git remote -v
 
 {% endwarning %}
 
-#### Troubleshooting: Could not remove config section 'remote.[name]'
+#### Solução de problemas: Não foi possível remover a seção 'remote.[name]'
 
 Esse erro informa que o remote que você tentou excluir não existe:
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md b/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md
index a0930f493b..d090dd1e3f 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/set-up-git.md
@@ -22,6 +22,8 @@ topics:
   - Accounts
 ---
 
+### Usar o Git
+
 Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.product_name %} na linha de comando. Para obter mais informações sobre {% data variables.product.prodname_cli %}, consulte a documentação de [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) .{% endif %}
 
 Se quiser trabalhar com o Git, mas não quiser usar a linha de comando, você poderá baixar e instalar o cliente do [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}).  Para obter mais informações, consulte "[Instalar e configurar o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)".
diff --git a/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index 4588032549..5cc7bbac39 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ Se você não comprar o {% data variables.product.prodname_enterprise %} ou o {%
 
 Fazer downgrade para o {% data variables.product.prodname_free_team %} para organizações também desabilita quaisquer configurações SAML feitas durante o período de avaliação. Ao adquirir o {% data variables.product.prodname_enterprise %} ou o {% data variables.product.prodname_team %}, suas configurações SAML serão habilitadas novamente para os usuários da organização se autenticarem.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Em "{% data variables.product.prodname_ghe_cloud %} Free Trial" (Versão de avaliação grátis do {% data variables.product.prodname_ghe_cloud %}) clique em **Buy Enterprise** (Comprar versão Enterprise) ou **Downgrade to Team** (Fazer downgrade para versão Team). ![Botões comprar versão Enterprise e fazer downgrade para versão Team](/assets/images/help/organizations/finish-trial-buttons.png)
 6. Siga as instruções para inserir seu método de pagamento e clique em **Submit** (Enviar).
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md
index 04633846f3..cadae1eed3 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository.md
@@ -49,7 +49,7 @@ Se você criar um clone do repositório, não perderá nenhuma alteração ou hi
 
   {% tip %}
 
-  **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+  **Dica:** Para obter informações sobre a diferença entre as URLs de HTTPS e SSH, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
   {% endtip %}
 
diff --git a/translations/pt-BR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/pt-BR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index c76ee9b010..708ac7469e 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 Neste exemplo, abordaremos todos os comandos `git rebase` disponíveis, exceto `exec`.
 
 Vamos começar digitando `git rebase --interactive HEAD~7` no terminal. O editor de texto exibirá as seguintes linhas:
diff --git a/translations/pt-BR/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md b/translations/pt-BR/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md
index f53eb0fc2b..6d999af64a 100644
--- a/translations/pt-BR/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md
+++ b/translations/pt-BR/content/github/getting-started-with-github/why-is-git-always-asking-for-my-password.md
@@ -18,6 +18,6 @@ Você pode evitar que seja solicitada a sua senha ao configurar o Git para [arma
 
 ### Leia mais
 
-- "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+- "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)."
 - "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
 - "[Adicionar a sua chave SSH ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)"
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/pt-BR/content/github/importing-your-projects-to-github/about-github-importer.md
index 4fea97601e..efd00b2446 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre o Importador do GitHub
-intro: 'Se você tiver código-fonte em Subversion, Mercurial, Team Foundation Server ou outro repositório Git, será possível movê-lo para o GitHub usando o Importador do GitHub.'
+intro: 'If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer.'
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ O Importador do GitHub é uma ferramenta que importa rapidamente repositórios d
 
 Durante uma importação, dependendo do sistema de controle de versão do qual você está fazendo a importação, é possível autenticar com seu repositório remoto, atualizar a atribuição do autor do commit e importar repositórios com arquivos grandes (ou remover arquivos grandes se não desejar usar o Armazenamento de arquivos grandes do Git).
 
-| Ação de importação                                                                                               | Subversion | Mercurial | Team Foundation Server |  Git  |
-|:---------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:|
-| Autenticar com repositório remoto                                                                                |   **X**    |   **X**   |         **X**          | **X** |
-| [Atualizar atribuição do autor do commit](/articles/updating-commit-author-attribution-with-github-importer)     |   **X**    |   **X**   |         **X**          |       |
-| Mover arquivos grandes para o [Armazenamento de arquivos grandes do Git](/articles/about-git-large-file-storage) |   **X**    |   **X**   |         **X**          |       |
-| Remover arquivos grandes do repositório                                                                          |   **X**    |   **X**   |         **X**          |       |
+| Ação de importação                                                                                               | Subversion | Mercurial | TFVC  |  Git  |
+|:---------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:-----:|:-----:|
+| Autenticar com repositório remoto                                                                                |   **X**    |   **X**   | **X** | **X** |
+| [Atualizar atribuição do autor do commit](/articles/updating-commit-author-attribution-with-github-importer)     |   **X**    |   **X**   | **X** |       |
+| Mover arquivos grandes para o [Armazenamento de arquivos grandes do Git](/articles/about-git-large-file-storage) |   **X**    |   **X**   | **X** |       |
+| Remover arquivos grandes do repositório                                                                          |   **X**    |   **X**   | **X** |       |
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/pt-BR/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index 26496717e4..036956a674 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-Recomendamos o uso do [Importador do GitHub](/articles/about-github-importer) para importar projetos do Subversion, Mercurial, Team Foundation Server ou outro repositório do Git. Você também pode usar essas ferramentas externas para converter o projeto em Git.
+We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. Você também pode usar essas ferramentas externas para converter o projeto em Git.
 
 {% endif %}
 
@@ -32,12 +32,9 @@ Recomendamos estas ferramentas para converter repositórios do Subversion em Git
 
 Recomendamos o [hg-fast-export](https://github.com/frej/fast-export) para converter repositórios do Mercurial em Git.
 
-### Importar do Team Foundation Server
+### Importing from TFVC
 
-Recomendamos estas ferramentas para mover alterações entre oTeam Foundation Server e o Git:
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
 
 {% tip %}
 
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md b/translations/pt-BR/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md
index 5d090bd321..29604f3678 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md
@@ -51,7 +51,7 @@ Para obter mais informações, consulte “[Submódulos de ferramentas Git](http
 
 ### Preservar o histórico
 
-O SVN está configurado para pressupor que o histórico de um projeto nunca é alterado. Git allows you to modify previous commits and changes using tools like [`git rebase`](/github/getting-started-with-github/about-git-rebase).
+O SVN está configurado para pressupor que o histórico de um projeto nunca é alterado. O Git permite modificar alterações e commits anteriores usando ferramentas como [`git rebase`](/github/getting-started-with-github/about-git-rebase).
 
 {% tip %}
 
diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
index 34fa519b8e..d3e058e05e 100644
--- a/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
+++ b/translations/pt-BR/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
@@ -26,7 +26,7 @@ Se o arquivo{% if currentVersion == "free-pro-team@latest" or currentVersion ver
 
 1. Navegue até o arquivo no repositório que deseja excluir.
 2. Na parte superior do arquivo, clique
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index 4eb134d9da..9628303380 100644
--- a/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/pt-BR/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### Sobre a navegação do código no {% data variables.product.prodname_dotcom %}
 
 A navegação por código usa a biblioteca de código aberto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). As linguagens a seguir são compatíveis:
diff --git a/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md
index b04c985005..d0e00cc297 100644
--- a/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md
+++ b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md
@@ -1,6 +1,6 @@
 ---
-title: Conditions for large files
-intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories, and will block a push to a repository if the files are larger than the maximum file limit.'
+title: Condições para arquivos grandes
+intro: 'O {% data variables.product.product_name %} limita o tamanho dos arquivos permitidos nos repositórios e irá bloquear um push para um repositório se os arquivos forem maiores que o limite máximo de arquivos.'
 redirect_from:
   - /articles/conditions-for-large-files
 versions:
@@ -11,10 +11,10 @@ versions:
 
 {% data reusables.large_files.use_lfs_tip %}
 
-### Warning for files larger than {% data variables.large_files.warning_size %}
+### Aviso para arquivos maiores que {% data variables.large_files.warning_size %}
 
-If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](/github/managing-large-files/removing-files-from-a-repositorys-history)."
+Se você tentar adicionar ou atualizar um arquivo maior do que {% data variables.large_files.warning_size %}, você receberá um aviso do Git. As alterações ainda serão carregadas no seu repositório com sucesso, mas você pode considerar remover o commit para minimizar o impacto no desempenho. Para obter mais informações, consulte "[Remover arquivos do histórico de um repositório](/github/managing-large-files/removing-files-from-a-repositorys-history)".
 
-### Blocked pushes for large files
+### Pushes bloqueados para arquivos grandes
 
-{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %}
+{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}Por padrão, {% endif %}{% data variables.product.product_name %} bloqueia pushes que excedem {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}No entanto, um administrador do site pode configurar um limite diferente para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Definir limites de push do Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %}
diff --git a/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index 6c6aacf77b..89cc4dcb50 100644
--- a/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/pt-BR/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -38,7 +38,7 @@ versions:
 
 Depois de remover arquivos de {% data variables.large_files.product_name_short %}, os objetos de {% data variables.large_files.product_name_short %} ainda existem no armazenamento remoto {% if currentVersion == "free-pro-team@latest" %} e continuarão a contar para a sua cota de armazenamento de {% data variables.large_files.product_name_short %}{% endif %}.
 
-Para remover objetos de {% data variables.large_files.product_name_short %} de um repositório, {% if currentVersion == "free-pro-team@latest" %}, apague e recrie o repositório. Ao excluir um repositório, todos os problemas associados, estrelas e bifurcações também serão excluídos. Para obter mais informações, consulte "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)".{% else %}entre em contato com o administrador do {% data variables.product.prodname_enterprise %} para arquivar os objetos. Os objetos arquivados são excluídos após três meses.{% endif %}
+Para remover objetos de {% data variables.large_files.product_name_short %} de um repositório, {% if currentVersion == "free-pro-team@latest" %}, apague e recrie o repositório. Ao excluir um repositório, todos os problemas associados, estrelas e bifurcações também serão excluídos. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Os objetos arquivados são excluídos após três meses.{% endif %}
 
 {% note %}
 
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index 67f9613edb..15ec439078 100644
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,90 +1,72 @@
 ---
-title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
-redirect_from:
-  - /articles/about-security-alerts-for-vulnerable-dependencies
-  - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
+title: Sobre alertas para dependências vulneráveis
+intro: '{% data variables.product.product_name %} envia {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} quando detectarmos vulnerabilidades que afetam o repositório.'
 versions:
-  free-pro-team: '*'
-  enterprise-server: '*'
+  enterprise-server: <=2.22
+topics:
+  - Security
 ---
- 
-### About vulnerable dependencies
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
+### Sobre as dependências vulneráveis
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it.
+Quando o seu código depende de um pacote que tenha uma vulnerabilidade de segurança, essa dependência vulnerável pode causar uma série de problemas para o seu projeto ou para as pessoas que o usam.
 
-### Detection of vulnerable dependencies
+### Detecção de dependências vulneráveis
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detecta dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detecta dependências vulneráveis e envia alertas de segurança{% endif %} quando:
 
-{% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."
-- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- São sincronizados novos dados de consultoria com {% data variables.product.prodname_ghe_server %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
+- O gráfico de dependências para alterações de repositório. Por exemplo, quando um contribuidor faz push de um commit para alterar os pacotes ou versões de que ele depende. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 
 {% data reusables.repositories.dependency-review %}
 
-For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+Para obter uma lista dos ecossistemas para os quais o {% data variables.product.product_name %} pode detectar vulnerabilidades e dependências, consulte "[Ecossistemas de pacotes compatíveis](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
 
 {% note %}
 
-**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use.
+**Observação:** É importante manter seus manifestos atualizados e seu arquivos bloqueados. Se o gráfico de dependências não refletir corretamente suas dependências e versões atuais, você poderá perder alertas para dependências vulneráveis que você usar. Você também pode receber alertas de dependências que você já não usa.
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
-### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
+### Alertas do {% data variables.product.prodname_dependabot %} para dependências vulneráveis
 {% else %}
-### Security alerts for vulnerable dependencies
+### Alertas de segurança para dependências vulneráveis
 {% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% 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.
-
-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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
-
-{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+Quando
+{% data variables.product.product_name %} identifica uma dependência vulnerável, geramos um alerta {% data variables.product.prodname_dependabot %} e o exibimos na aba Segurança do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.product_name %} também notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. 
+Quando
+{% data variables.product.product_name %} identifica uma dependência vulnerável, enviamos um alerta de segurança aos mantenedores dos repositórios afetados, com informações sobre a vulnerabilidade, um link para o arquivo afetado no projeto e informações sobre uma versão corrigida.
 {% endif %}
 
 {% warning %}
 
-**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.
+**Observação**: Os recursos de segurança de {% data variables.product.product_name %} não reivindicam garantem que todas as vulnerabilidades sejam detectadas. Embora estejamos sempre tentando atualizar nosso banco de dados de vulnerabilidades e gerar alertas com nossas informações mais atualizadas. não seremos capazes de pegar tudo ou falar sobre vulnerabilidades conhecidas dentro de um período de tempo garantido. Esses recursos não substituem a revisão humana de cada dependência em busca de possíveis vulnerabilidades ou algum outro problema, e nossa sugestão é consultar um serviço de segurança ou realizar uma revisão completa de vulnerabilidade quando necessário.
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Acesso a {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %}
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+É possível ver todos os alertas que afetam um determinado projeto no gráfico de dependências do repositório.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre novos
+{% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
+Enviamos alertas de segurança para as pessoas com permissões de administrador nos repositórios afetados por padrão.
+O {% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório.
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Further reading
-
-- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obter mais informações, consulte "[Escolher o método de entrega para as suas notificações](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %} Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index 846ce41b5a..9d9bfd3f64 100644
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,20 +1,18 @@
 ---
 title: Configurar notificações para dependências vulneráveis
 shortTitle: Configurar notificações
-intro: 'Otimiza como você recebe notificações sobre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %}.'
+intro: 'Otimiza como você recebe notificações sobre {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %}.'
 versions:
   enterprise-server: '>=2.21 <=2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies for the current version of this article -->
+
 ### Sobre notificações para dependências vulneráveis
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}Quando {% data variables.product.prodname_dependabot %} detecta dependências vulneráveis nos seus repositórios, geramos um alerta {% data variables.product.prodname_dependabot %} e exibimo-lo na aba Segurança do repositório. {% data variables.product.product_name %} notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação.{% else %}Quando {% data variables.product.product_name %} detecta dependências vulneráveis no seu repositório, ele envia alertas de segurança.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} está habilitado por padrão em todos os repositórios públicos. Para {% data variables.product.prodname_dependabot_alerts %}, por padrão, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail, agrupado pela vulnerabilidade específica.
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
 O administrador do seu site precisa habilitar alertas de segurança para dependências vulneráveis para
@@ -28,14 +26,14 @@ Por padrão, se o administrador do site tiver configurado e-mail para notificaç
 
 {% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. Para obter mais informações, consulte "[Habilitar alertas de segurança para dependências vulneráveis no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %}
 
-### Configurar notificações para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}
+### Configurar notificações para {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}
 
 Você pode definir as configurações de notificação para si mesmo ou para sua organização no menu suspenso Gerenciar notificações {% octicon "bell" aria-label="The notifications bell" %} exibido na parte superior de cada página. Para obter mais informações, consulte “[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)".
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
   ![Opções {% data variables.product.prodname_dependabot_alerts %} ](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 {% else %}
   ![Opções de alerta de segurança](/assets/images/help/notifications-v2/security-alerts-options.png)
@@ -47,11 +45,11 @@ Você pode definir as configurações de notificação para si mesmo ou para sua
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" % %}{% data reusables.repositories.security-alerts-x-github-severity %} Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} Para obter mais informações, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
 
 ### Como reduzir o ruído das notificações para dependências vulneráveis
 
-Se você estiver preocupado em receber muitas notificações para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, recomendamos que você opte pelo resumo semanal por e-mail ou desative as notificações ao mesmo tempo que mantém os {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} habilitados. Você ainda pode navegar para ver os seus {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} na aba de Segurança do seu repositório. {% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %}
+If you are concerned about receiving too many notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md
index 4cc88a83e8..507cfcf172 100644
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### Índice
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index 9d76159b96..0e320becdc 100644
--- a/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index 8caa6935ae..4b3a10f1f6 100644
--- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -26,13 +26,9 @@ Você pode optar por receber atualizações em curso sobre a atividade específi
 Você pode optar por assinar notificações para:
 - Uma conversa em um problema específico, pull request ou gist.
 - Todas as atividades em um repositório ou em uma discussão em equipe.
-- Atividade CI, como o status de fluxos de trabalho nos repositórios configurados com {% data variables.product.prodname_actions %}.
-{% if currentVersion == "free-pro-team@latest" %}
-- Problemas, pull requests, versões e discussões (se habilitado) em um repositório.
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- Lançamentos em um repositório.
-{% endif %}
+- Atividade CI, como o status de fluxos de trabalho nos repositórios configurados com {% data variables.product.prodname_actions %}. {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 Você também pode optar por assistir automaticamente todos os repositórios aos quais você tem acesso de push, exceto as bifurcações. É possível assistir qualquer outro repositório ao qual você tenha acesso manualmente clicando em **Watch** (Assistir).
 
diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
index 3e10e43823..407a3bc077 100644
--- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
+++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
@@ -58,7 +58,7 @@ Além disso, você pode receber e acessar as notificações no seu dispositivo m
 
 #### Benefícios da utilização de um cliente de e-mail para notificações
 
-Um benefício de usar um cliente de e-mail é que todas as suas notificações podem ser mantidas indefinidamente, dependendo da capacidade de armazenamento do seu cliente de e-mail. Suas notificações na caixa de entrada só serão mantidas por 5 meses, a menos que você as tenha marcado como **Salvas**. As notificações **Saved** (Salvas) são mantidas indefinidamente. Para obter mais informações sobre a política de retenção da sua caixa de entrada, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)".
+Um benefício de usar um cliente de e-mail é que todas as suas notificações podem ser mantidas indefinidamente, dependendo da capacidade de armazenamento do seu cliente de e-mail. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. As notificações **Saved** (Salvas) são mantidas indefinidamente. Para obter mais informações sobre a política de retenção da sua caixa de entrada, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)".
 
 O envio de notificações para o cliente de e-mail também permite que você personalize sua caixa de entrada de acordo com as configurações do cliente de e-mail que pode incluir etiquetas personalizadas ou codificadas por cores.
 
@@ -69,16 +69,17 @@ As notificações de e-mail também permitem flexibilidade com os tipos de notif
 Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)".
 
 Para ver repositórios que você está inspecionando, acesse a sua [página de inspeção](https://github.com/watching). Para obter mais informações, consulte "[Gerenciando assinaturas e notificações do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)".
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
 #### Configurar notificações
 {% endif %}
 Você pode configurar as notificações para um repositório na página do repositório ou na página de visitas.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} Você pode optar por receber apenas notificações de versões em um repositório ou ignorar todas as notificações de um repositório.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 #### Sobre as notificações personalizadas
-{% data reusables.notifications-v2.custom-notifications-beta %}
-É possível personalizar notificações para um repositório. Você pode optar, por exemplo, por receber notificações somente quando atualizações para um ou mais tipos de eventos (problemas, pull request, versões, discussões) ocorrerem dentro de um repositório ou ignorar todas as notificações de um repositório.
-{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
+You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events (
+{% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository.
+{% endif %} Para obter mais informações, consulte "[Definir as suas configurações de inspeção para um repositório individual](#configuring-your-watch-settings-for-an-individual-repository)" abaixo.
 
 #### Participar de conversas
 A qualquer momento que você comentar em uma conversa ou quando alguém @mencionar seu nome de usuário, você estará _participando_ de uma conversa. Por padrão, você é inscrito automaticamente em uma conversa ao participar dela. Você pode cancelar manualmente a inscrição de uma conversa que você participou, clicando em **Cancelar inscrição** no problema ou na pull request ou através da opção **Cancelar inscrição** na caixa de entrada de notificações.
@@ -133,7 +134,7 @@ As notificações de e-mail do {% data variables.product.product_name %} contêm
 | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Endereço do `remetente`   | Este endereço será sempre {% if currentVersion == "free-pro-team@latest" %}'`notifications@github. om`'{% else %}'endereço de e-mail de não responda configurado pelo administrador do site'{% endif %}.                                                                                                                                                       |
 | Campo `To`                | Este campo conecta-se diretamente à corrente.{% if currentVersion != "github-ae@latest" %} Se você responder ao e-mail, você adicionará um novo comentário na conversa.{% endif %}
-| Endereço de `Cc`          | O {% data variables.product.product_name %} colocará você em cópia (`Cc`) se você estiver inscrito para uma conversa. O segundo endereço de e-mail de `Cc` corresponde ao motivo da notificação. O sufixo para esses motivos de notificação é {% data variables.notifications.cc_address %}. Os possíveis motivos de notificação são: <ul><li>'assign': você foi atribuído a um problema ou uma pull request.</li><li>'author': você criou um problema ou uma pull request.</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}<li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li>{% endif %}<li>'comment': você comentou um problema ou uma pull request.</li><li>'manual': houve uma atualização em um problema ou uma pull request para o(a) qual você assinou manualmente.</li><li>'mention': você foi mencionado em um problema ou uma pull request.</li><li>'push': alguém fez commit em uma pull request que você assinou.</li><li>'review_requested': você ou uma equipe da qual faz você faz parte foi solicitado para revisar uma pull request.</li>{% if currentVersion != "github-ae@latest" %}<li>'security_alert': o {% data variables.product.prodname_dotcom %} detectou uma vulnerabilidade em um repositório para o qual você recebe alertas de segurança.</li>{% endif %}<li>'state_change': um problema ou uma pull request que você assinou foi fechado(a) ou aberto(a).</li><li>'subscribed': houve uma atualização em um repositório que você está inspecionando.</li><li>'team_mention': uma equipe a qual você pertence foi mencionada em um problema ou uma pull request.</li><li>'your_activity': você abriu, comentou ou fechou um problema ou uma pull request.</li></ul> |
+| Endereço de `Cc`          | O {% data variables.product.product_name %} colocará você em cópia (`Cc`) se você estiver inscrito para uma conversa. O segundo endereço de e-mail de `Cc` corresponde ao motivo da notificação. O sufixo para esses motivos de notificação é {% data variables.notifications.cc_address %}. Os possíveis motivos de notificação são: <ul><li>'assign': você foi atribuído a um problema ou uma pull request.</li><li>'author': você criou um problema ou uma pull request.</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}<li>`ci_activity`: Uma execução de fluxo de trabalho de {% data variables.product.prodname_actions %} que você acionou foi concluída.</li>{% endif %}<li>'comment': você comentou um problema ou uma pull request.</li><li>'manual': houve uma atualização em um problema ou uma pull request para o(a) qual você assinou manualmente.</li><li>'mention': você foi mencionado em um problema ou uma pull request.</li><li>'push': alguém fez commit em uma pull request que você assinou.</li><li>'review_requested': você ou uma equipe da qual faz você faz parte foi solicitado para revisar uma pull request.</li>{% if currentVersion != "github-ae@latest" %}<li>'security_alert': o {% data variables.product.prodname_dotcom %} detectou uma vulnerabilidade em um repositório para o qual você recebe alertas de segurança.</li>{% endif %}<li>'state_change': um problema ou uma pull request que você assinou foi fechado(a) ou aberto(a).</li><li>'subscribed': houve uma atualização em um repositório que você está inspecionando.</li><li>'team_mention': uma equipe a qual você pertence foi mencionada em um problema ou uma pull request.</li><li>'your_activity': você abriu, comentou ou fechou um problema ou uma pull request.</li></ul> |
 | campo `mailing list`      | Esse campo identifica o nome do repositório e seu proprietário. O formato desse endereço é sempre `<nome do repositório>.<proprietário do repositório>.{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 | campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Os níveis possíveis de gravidade são:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" 
 {% endif %}
@@ -159,19 +160,22 @@ Se "Inspecionar repositórios automaticamente" estiver desativado, então você
 
 ### Configurando as configurações de inspeção para um repositório individual
 
-É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. Você também pode optar por receber notificações apenas sobre {% if currentVersion == "free-pro-team@latest" %}certos tipos de eventos como problemas, pull requests, discussões (se habilitado para o repositório) e {% endif %}novas versões, ou ignorar completamente um repositório individual.
+É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 2. No canto superior direito, clique no menu suspenso "Inspecionar" para selecionar uma opção de inspeção.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
    ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
-{% data reusables.notifications-v2.custom-notifications-beta %}
+
 A opção **Personalizar** permite que você personalize ainda mais as notificações para que você seja notificado apenas quando eventos específicos ocorrerem no repositório, além de participar e @mentions.
 
+{% if currentVersion == "free-pro-team@latest" %}
+   ![Opções de inspeção personalizadas em um menu suspenso para um repositório](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png)
+{% else %}
    ![Opções de inspeção personalizadas em um menu suspenso para um repositório](/assets/images/help/notifications-v2/watch-repository-options-custom2.png)
+{% endif %}
 
 Se você selecionar "Problemas", você será notificado e irá inscrever-se para receber atualizações sobre cada problema (incluindo aqueles que existiam antes de você selecionar esta opção) no repositório. Se você for @mentioned em um pull request neste repositório, você receberá notificações sobre isso também e será inscrito em atualizações desse pull request específico, além de ser notificado sobre problemas.
 
@@ -220,7 +224,7 @@ Para obter mais informações sobre os métodos de entrega de notificações dis
 
 Escolha como você deseja receber atualizações de execução de fluxo de trabalho para repositórios que você está inspecionando que estão configurados com o {% data variables.product.prodname_actions %}. Você também pode optar por receber apenas notificações de execução de fluxo de trabalho falha.
 
-  ![Opções de alertas {% data variables.product.prodname_dependabot_short %}](/assets/images/help/notifications-v2/github-actions-notification-options.png)
+  ![Notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png)
 
 {% endif %}
 
@@ -248,7 +252,7 @@ Você também pode agendar quando {% data variables.product.prodname_mobile %} e
 
 1. No menu inferior, toque em **Perfil**.
 2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}.
-3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
+3. Para atualizar suas configurações de notificação, toque em **Configurar notificações** e, em seguida, use os atalhos para habilitar ou desabilitar seus tipos preferidos de notificações push.
 4. Opcionalmente, para agendar quando {% data variables.product.prodname_mobile %} enviará notificações de push para seu dispositivo móvel, toque em **Horas de Trabalho**, use o **horário de trabalho personalizado** e, em seguida, escolha quando você gostaria de receber notificações de push.
 
 ### Configurar as configurações de inspeção para um repositório individual com {% data variables.product.prodname_mobile %}
diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md
index d7441869f5..86e6ea1055 100644
--- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md
+++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md
@@ -1,6 +1,6 @@
 ---
-title: Managing notifications from your inbox
-intro: 'Use your inbox to quickly triage and sync your notifications across email{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.'
+title: Gerenciamento de notificações da sua caixa de entrada
+intro: 'Use sua caixa de entrada para rastrear e sincronizar rapidamente as notificações nos e-mails{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} e dispositivos móveis{% endif %}.'
 redirect_from:
   - /articles/marking-notifications-as-read
   - /articles/saving-notifications-for-later
@@ -16,96 +16,96 @@ topics:
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-### About your inbox
+### Sobre sua caixa de entrada
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %}
-{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
+{% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obter mais informações, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)".
 {% endif %}
 
-To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}.
+Para acessar sua caixa de entrada de notificações, no canto superior direito de qualquer página, clique em {% octicon "bell" aria-label="The notifications bell" %}.
 
-  ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png)
+  ![Notificação indicando qualquer mensagem não lida](/assets/images/help/notifications/notifications_general_existence_indicator.png)
 
-Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview.
+Sua caixa de entrada mostra todas as notificações que você não cancelou sua inscrição ou marcou como **Concluído.** Você pode personalizar sua caixa de entrada para melhor se adequar ao seu fluxo de trabalho usando filtros, visualizando todas ou apenas notificações não lidas e agrupando suas notificações para obter uma visão geral.
 
-  ![inbox view](/assets/images/help/notifications-v2/inbox-view.png)
+  ![visualização da caixa de entrada](/assets/images/help/notifications-v2/inbox-view.png)
 
-By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query.
+Por padrão, sua caixa de entrada mostrará notificações lidas e não lidas. Para ver apenas notificações não lidas, clique em **Não lidas** ou use a consulta `is:unread`.
 
-  ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png)
+  ![visualização da caixa de entrada não lida](/assets/images/help/notifications-v2/unread-inbox-view.png)
 
-### Triaging options
+### Opções de triagem
 
-You have several options for triaging notifications from your inbox.
+Você tem várias opções para fazer triagem de notificações a partir de sua caixa de entrada.
 
-| Triaging option | Description |
-|-----------------|-------------|
-| Save            | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}. <br> <br> Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. |
-| Done            | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months.
-| Unsubscribe     | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review.
-| Read            | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**.
-| Unread          | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. |
+| Opções de triagem   | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Salvar              | Salva a sua notificação para revisão posterior. Para salvar uma notificação, à direita da notificação, clique em {% octicon "bookmark" aria-label="The bookmark icon" %}. <br> <br> As notificações salvas são mantidas indefinidamente e podem ser vistas clicando em **Salvo** na barra lateral ou com a consulta `is:saved`. Se sua notificação salva tiver mais de 5 meses e tornar-se não salva, a notificação desaparecerá da sua caixa de entrada em um dia. |
+| Concluído           | Marca uma notificação como concluída e remove a notificação da sua caixa de entrada. Você pode ver todas as notificações concluídas clicando em **Concluido** na barra lateral ou com a consulta `is:done`. Notificações marcadas como **Concluídas** são salvas por 5 meses.                                                                                                                                                                                                   |
+| Cancelar assinatura | Remove automaticamente a notificação de sua caixa de entrada e cancela sua assinatura da conversa até que você seja @mencionado, uma equipe na qual você esteja seja @mencionada, ou você seja solicitado para revisão.                                                                                                                                                                                                                                                         |
+| Leitura             | Marca uma notificação como lida. Para ver apenas as notificações lidas na sua caixa de entrada, use a consulta `is:read`. Esta consulta não inclui notificações marcadas como **Concluído**.                                                                                                                                                                                                                                                                                    |
+| Não lido            | Marca uma notificação como não lida. Para ver apenas as notificações não lidas na sua caixa de entrada, use a consulta `is:read`.                                                                                                                                                                                                                                                                                                                                               |
 
-To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)."
+Para ver os atalhos de teclado disponíveis, consulte "[Atalhos de teclado](/github/getting-started-with-github/keyboard-shortcuts#notifications)".
 
-Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)."
+Antes de escolher uma opção de triagem, primeiro você pode pré-visualizar os detalhes da sua notificação e investigar. Para obter mais informações, consulte “[Fazendo triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)".
 
-### Triaging multiple notifications at the same time
+### Fazer triagem de várias notificações ao mesmo tempo
 
-To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option.
+Para fazer triagem de várias notificações de uma só vez, selecione as notificações relevantes e use o menu suspenso {% octicon "kebab-horizontal" aria-label="The edit icon" %} para escolher uma opção de triagem.
 
-![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
+![Menu suspenso com opções de triagem e notificações selecionadas](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
 
-### Default notification filters
+### Filtros de notificação padrão
 
-By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned.
+Por padrão, sua caixa de entrada tem filtros para quando você é responsável, participa de um thread, é solicitado a rever uma pull request ou quando seu nome de usuário for @mencionado diretamente ou quando uma equipe da qual você é integrante é @mencionada.
 
-  ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png)
+  ![Filtros personalizados padrão](/assets/images/help/notifications-v2/default-filters.png)
 
-### Customizing your inbox with custom filters
+### Personalizando sua caixa de entrada com filtros personalizados
 
-You can add up to 15 of your own custom filters.
+Você pode adicionar até 15 dos seus próprios filtros personalizados.
 
 {% data reusables.notifications.access_notifications %}
-2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}.
+2. Para abrir as configurações de filtro, na barra lateral esquerda, próximo de "Filtros", clique em {% octicon "gear" aria-label="The Gear icon" %}.
 
   {% tip %}
 
-  **Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings.
+  **Dica:** Você pode visualizar rapidamente os resultados da caixa de entrada de um filtro, criando uma consulta na sua caixa de entrada e clicando em **Salvar**, que abre as configurações de filtro personalizado.
 
   {% endtip %}
 
-3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)."
+3. Adicione um nome para seu filtro e uma consulta de filtro. Por exemplo, para ver apenas notificações para um repositório específico, é possível criar um filtro usando a consulta `repo:octocat/open-source-project-name reason:participating`. Você também pode adicionar emojis com um teclado de emojis nativo. Para obter uma lista de consultas de pesquisa compatíveis, consulte "[Consultas suportadas para filtros personalizados](#supported-queries-for-custom-filters)".
 
-  ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png)
+  ![Exemplo de filtro personalizado](/assets/images/help/notifications-v2/custom-filter-example.png)
 
-4. Click **Create**.
+4. Clique em **Criar**.
 
-### Custom filter limitations
+### Limitações de filtro personalizadas
 
-Custom filters do not currently support:
-  - Full text search in your inbox, including searching for pull request or issue titles.
-  - Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests.
-  - Creating more than 15 custom filters.
-  - Changing the default filters or their order.
-  - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`.
+Filtros personalizados atualmente não suportam:
+  - Pesquisa de texto completo em sua caixa de entrada, incluindo busca de pull request ou títulos de problema.
+  - Distinguindo entre filtros de consulta `is:issue`, `is:pr` e `is:pull-request`. Essas consultas retornarão problemas e pull requests.
+  - Criando mais de 15 filtros personalizados.
+  - Alterando os filtros padrão ou sua ordenação.
+  - Pesquise a [exclusão](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) usando `NÃO` ou `-QUALIFICADOR`.
 
-### Supported queries for custom filters
+### Consultas suportadas para filtros personalizados
 
-These are the types of filters that you can use:
-  - Filter by repository with `repo:`
-  - Filter by discussion type with `is:`
-  - Filter by notification reason with `reason:`{% if currentVersion == "free-pro-team@latest" %}
-  - Filter by notification author with `author:`
-  - Filter by organization with `org:`{% endif %}
+Estes são os tipos de filtros que você pode usar:
+  - Filtrar por repositório com `repo:`
+  - Filtrar por tipo de discussão com `is:`
+  - Filtrar por motivo de notificação com `reason:`{% if currentVersion == "free-pro-team@latest" %}
+  - Filtrar por autor de notificação com `author:`
+  - Filtrar por organização com `org:`{% endif %}
 
-#### Supported `repo:` queries
+#### Consultas de `repo:` compatíveis
 
-To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization.
+Para adicionar um filtro de `repo:`, você deve incluir o proprietário do repositório na consulta: `repo:owner/repository`. Um proprietário é a organização ou o usuário que possui o ativo de {% data variables.product.prodname_dotcom %} que aciona a notificação. Por exemplo, `repo:octo-org/octo-repo` irá mostrar notificações acionadas no repositório octo-repo dentro da organização octo-org.
 
-#### Supported `is:` queries
+#### Consultas suportadas `is:`
 
-To filter notifications for specific activity on {% data variables.product.product_name %}, you can use the  `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% if currentVersion != "github-ae@latest" %}, and to only see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts, use `is:repository-vulnerability-alert`.{% endif %}
+Para filtrar notificações para uma atividade específica no {% data variables.product.product_name %}, você pode usar a  consulta `is`. Por exemplo, para ver apenas atualizações de convite do repositório, use `is:repository-invitation`{% if currentVersion != "github-ae@latest" %}, e para ver somente {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %}{% else %} alertas de {% endif %} segurança, use `is:repository-vulnerability-alert`.{% endif %}
 
 - `is:check-suite`
 - `is:commit`
@@ -119,64 +119,69 @@ To filter notifications for specific activity on {% data variables.product.produ
 - `is:discussions`{% endif %}
 
 {% if currentVersion != "github-ae@latest" %}
-For information about reducing noise from notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
+Para informações sobre a redução de ruído de notificações para
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".
 {% endif %}
 
-You can also use the `is:` query to describe how the notification was triaged.
+Você também pode usar a consulta `is:` para descrever como a notificação passou pela triagem.
 
 - `is:saved`
 - `is:done`
 - `is:unread`
 - `is:read`
 
-#### Supported `reason:` queries
+#### Consultas suportadas `reason:`
 
-To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)."
+Para filtrar notificações por motivos pelos quais recebeu uma atualização, você pode usar a consulta `reason:`. Por exemplo, para ver notificações quando você (ou uma equipe da qual você participa) é solicitado a rever uma pull request, use `reason:review-requested`. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)".
 
-| Query | Description |
-|-----------------|-------------|
-| `reason:assign` | When there's an update on an issue or pull request you've been assigned to.
-| `reason:author` | When you opened a pull request or issue and there has been an update or new comment.
-| `reason:comment`| When you commented on an issue, pull request, or team discussion.
-| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned.
-| `reason:invitation` | When you're invited to a team, organization, or repository.
-| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to.
-| `reason:mention` | You were directly @mentioned.
-| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% if currentVersion != "github-ae@latest" %}
-| `reason:security-alert` | When a security alert is issued for a repository.{% endif %}
-| `reason:state-change`  | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged.
-| `reason:team-mention` | When a team you're a member of is @mentioned.
-| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status.
+| Consulta                  | Descrição                                                                                                                         |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `reason:assign`           | Quando houver uma atualização em um problema ou numa pull request que você tenha sido designado responsável.                      |
+| `reason:author`           | Quando você abriu uma pull request ou um problema e houve uma atualização ou novo comentário.                                     |
+| `reason:comment`          | Quando você comentou em um problema, numa pull request ou numa discussão em equipe.                                               |
+| `reason:participating`    | Quando você tiver comentado um problema, uma pull request ou numa discussão de equipe ou tiver sido @mencionado.                  |
+| `reason:invitation`       | Quando você for convidado para uma equipe, organização ou repositório.                                                            |
+| `reason:manual`           | Quando você clicar em **Assinar** em um problema ou uma pull request que você ainda não estava inscrito.                          |
+| `reason:mention`          | Você foi @mencionado diretamente.                                                                                                 |
+| `reason:review-requested` | Foi solicitado que você ou uma equipe revise um um pull request.{% if currentVersion != "github-ae@latest" %}
+| `reason:security-alert`   | Quando um alerta de segurança é emitido para um repositório.{% endif %}
+| `reason:state-change`     | Quando o estado de uma pull request ou um problema é alterado. Por exemplo, um problema é fechado ou uma pull request é mesclada. |
+| `reason:team-mention`     | Quando uma equipe da qual você é integrante é @mencionada.                                                                        |
+| `reason:ci-activity`      | Quando um repositório tem uma atualização de CI, como um novo status de execução de fluxo de trabalho.                            |
 
 {% if currentVersion == "free-pro-team@latest" %}
-#### Supported `author:` queries
+#### Consultas de `author:` compatíveis
 
-To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`.
+Para filtrar as notificações por usuário, você pode usar a consulta de `author:`. Um autor é o autor original da corrente (problema, pull request, discussões gist, e assim por diante) referente ao qual você está sendo notificado. Por exemplo, para visualizar notificações referentes a tópicos criados pelo usuário do Octocat use `author:octocat`.
 
-#### Supported `org:` queries
+#### Consultas `org:` compatíveis
 
-To filter notifications by organization, you can use the  `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization.
+Para filtrar notificações por organização, você pode usar a consulta `org`. A organização que você precisa especificar na consulta é a organização do repositório, para a qual você está sendo notificado em {% data variables.product.prodname_dotcom %}. Esta consulta é útil se você pertencer a várias organizações e desejar ver as notificações para uma organização específica.
 
-For example, to see notifications from the octo-org organization, use `org:octo-org`. 
+Por exemplo, para ver notificações da organização octo-org, use `org:octo-org`.
 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-### {% data variables.product.prodname_dependabot %} custom filters
+### Filtros personalizados de {% data variables.product.prodname_dependabot %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters:
-- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
-- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests.
-- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests.
+Se você usar
+{% data variables.product.prodname_dependabot %} para manter suas dependências atualizadas, você poderá usar e salvar estes filtros personalizados:
+- `is:repository_vulnerability_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}.
+- `reason:security_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %} e pull requests das atualizações de segurança.
+- `author:app/dependabot` para mostrar as notificações geradas por {% data variables.product.prodname_dependabot %}. Isto inclui {% data variables.product.prodname_dependabot_alerts %}, pull requests para atualizações de segurança e pull requests para atualizações de versão.
+Para mais informações sobre
 
-For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)."
+{% data variables.product.prodname_dependabot %}, consulte "[Sobre o gerenciamento de dependências vulneráveis](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)".
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
-If you use {% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
+Se você usar
+{% data variables.product.prodname_dependabot %} para manter suas dependências atualizadas, você pode usar e salvar o filtro personalizado `é:repository_vulnerability_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}.
+Para mais informações sobre
 
-For more information about {% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+{% data variables.product.prodname_dependabot %}, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".
 {% endif %}
 
 {% endif %}
diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index ad2841ffd9..58a5769fb9 100644
--- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -57,13 +57,13 @@ Quando você deixa de inspecionar um repositório, você cancela sua assinatura
 {% data reusables.notifications.access_notifications %}
 1. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" para clicar em **Inspecionar repositórios**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Na página de repositórios inspecionados, depois de ter avaliado os repositórios que você está inspecionando, escolha se deseja:
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-    - deixar de inspecionar um repositório
-    - inspecionar somente versões em um repositório
-    - ignorar todas as notificações de um repositório
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-    - deixar de inspecionar um repositório
-    - ignorar todas as notificações de um repositório
-    - personalizar os tipos de eventos para os quais você recebe notificações (problemas, pull requests, versões ou discussões, se habilitado)
-{% endif %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
+    - Deixar de inspecionar um repositório
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    - Deixar de inspecionar um repositório
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index 1d0e731dd8..6f11a6113d 100644
--- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -35,10 +35,10 @@ Quando sua caixa de entrada tiver muitas notificações para gerenciar, consider
 Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)".
 
 Para ter uma visão geral das assinaturas de seu repositório, consulte "[Revisando repositórios que você está inspecionando](#reviewing-repositories-that-youre-watching).
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**Dica:** Você pode selecionar os tipos de evento a serem notificados utilizando a opção **Personalizar** na lista suspensa **Inspecionar/Cancelar inspeção** na sua [página](https://github.com/watching) ou em qualquer página de repositório em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
+**Dica:** Você pode selecionar os tipos de evento a serem notificados utilizando a opção **Personalizar** na lista suspensa **Inspecionar/Cancelar inspeção** na sua [página](https://github.com/watching) ou em qualquer página de repositório em {% data variables.product.product_name %}. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)".
 
 {% endtip %}
 {% endif %}
@@ -67,16 +67,15 @@ Muitas pessoas esquecem os repositórios que eles escolheram inspecionar no pass
 
 1. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" e clique em **Repositórios inspecionados**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Avalie os repositórios que você está inspecionando e decida se suas atualizações ainda são relevantes e úteis. Quando você inspeciona um repositório, você será notificado de todas as conversas desse repositório.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
   ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **Dica:** Em vez de inspecionar um repositório, considere receber apenas notificações {% if currentVersion == "free-pro-team@latest" %}quando houver atualizações sobre problemas, pull requests, versões ou discussões (se habilitado para o repositório), ou qualquer combinação destas opções,{% else %}para versões em um repositório,{% endif %} ou para cancelar a inspeção por completo de um repositório.
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
 
   Quando você deixa de inspecionar um repositório, você ainda pode ser notificado quando for @mencionado ou estiver participando de um thread. Ao definir a configuração para receber notificações de certos tipos de evento, você só será notificado quando houver atualizações desses tipos de eventos no repositório, quando você estiver participando de um tópico ou quando você ou a sua equipe for @mentioned.
 
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/pt-BR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index 6e4452b7b2..60d3f14db6 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ Os parâmetros de consulta são partes opcionais de uma URL que podem ser person
 
 Você deve ter as permissões adequadas para qualquer ação para usar o parâmetro de consulta equivalente. Por exemplo, é preciso ter permissão para adicionar uma etiqueta a um problema para usar o parâmetro de consulta `label`.
 
-Se você criar um URL inválido usando parâmetros de consulta, ou se não tiver as permissões adequadas, o URL retornará uma página de erro 404.
+If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page.
 
 ### Parâmetros de consulta compatíveis
 
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md b/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md
index 527e8ec133..11cb49b260 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/about-issues.md
@@ -1,6 +1,6 @@
 ---
-title: About issues
-intro: 'Use issues to track ideas, enhancements, tasks, or bugs for work on {% data variables.product.product_name %}.'
+title: Sobre problemas
+intro: 'Use problemas para rastrear ideias, aprimoramentos, tarefas ou erros para trabalhar no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/creating-issues/
   - /articles/about-issues/
@@ -12,29 +12,31 @@ topics:
   - Pull requests
 ---
 
-### About issues
+### Sobre problemas
 
-You can collect user feedback, report software bugs, and organize tasks you'd like to accomplish with issues in a repository. Issues can act as more than just a place to report software bugs.
+Você pode coletar feedback, reportar erros de software e organizar tarefas que deseja realizar com problemas em um repositório. Os problemas podem ser mais do que um lugar para relatar erros de relatório.
 
-Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %}
+{% if currentVersion == "free-pro-team@latest" %}
+Outras conversas são mais adequadas para discussões. {% data reusables.discussions.you-can-use-discussions %}
 
 {% data reusables.discussions.you-cannot-convert-a-discussion %}
+{% endif %}
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
-To stay updated on the most recent comments in an issue, you can watch an issue to receive notifications about the latest comments. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." 
+Para se manter atualizado sobre os comentários mais recentes em um problema, você pode inspecionar um problema a fim de recebe notificações sobre os últimos comentários. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
 
-To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)".
 
-### Working with issues
+### Trabalhar com problemas
 
-With issues, you can:
-- Track and prioritize your work using project boards. For more information, see "[Using project boards](/articles/about-project-boards)."
-- Create new issues to track out-of-scope feedback from a comment in an issue or a pull request review. For more information, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)."
-- Create issue templates to help contributors open meaningful issues. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
-- Transfer open issues to other repositories. For more information, see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)."
-- Pin important issues to make them easier to find, preventing duplicate issues and reducing noise. For more information, see "[Pinning an issue to your repository](/articles/pinning-an-issue-to-your-repository)."
-- Track duplicate issues using saved replies. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %}
-- Report comments that violate {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/articles/github-community-guidelines). For more information, see "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)."{% endif %}
+Com problemas, você pode:
+- Acompanhar e priorizar seu trabalho usando quadros de projeto. Para obter mais informações, consulte "[Usar quadros de projeto](/articles/about-project-boards)".
+- Criar novos problemas para rastrear feedbacks fora do escopo a partir de um comentário em um problema ou de uma revisão de pull request. Para obter mais informações, consulte "[Abrir um problema a partir de um comentário](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)".
+- Criar modelos de problema para ajudar os contribuidores a abrir problemas significativos. Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)".
+- Transferir problemas abertos para outros repositórios. Para obter mais informações, consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)".
+- Fixar problemas importantes para que seja mais fácil encontrá-los, evitando a duplicação de problemas e reduzindo ruídos. Para obter mais informações, consulte "[Fixar um problema no seu repositório](/articles/pinning-an-issue-to-your-repository)".
+- Acompanhar problemas duplicados usando respostas salvas. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %}
+- Relatar comentários que violam as [Diretrizes da comunidade](/articles/github-community-guidelines) do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Relatar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)".{% endif %}
 
-Issues can also be [assigned to other users](/articles/assigning-issues-and-pull-requests-to-other-github-users), [tagged with labels](/articles/applying-labels-to-issues-and-pull-requests) for quicker searching, and [grouped together with milestones](/articles/creating-and-editing-milestones-for-issues-and-pull-requests).
+Os problemas também podem ser [atribuídos a outros usuários](/articles/assigning-issues-and-pull-requests-to-other-github-users), [marcados com etiquetas](/articles/applying-labels-to-issues-and-pull-requests) para pesquisa mais rápida e [agrupados com marcos](/articles/creating-and-editing-milestones-for-issues-and-pull-requests).
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index db637c3404..4215e467de 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. Escolha uma destas opções:
     - Para criar um marco, clique em **New Milestone** (Novo marco). ![Botão New milestone (Novo marco)](/assets/images/help/repository/new-milestone.png)
     - Para editar um marco, ao lado do marco que deseja editar, clique em **Edit** (Editar). ![Opção para editar marco](/assets/images/help/repository/edit-milestone.png)
-5. Digite o título, a descrição ou outras alterações do marco e clique em **Create milestone** (Criar marco) ou **Save changes** (Salvar alterações).
+5. Digite o título, a descrição ou outras alterações do marco e clique em **Create milestone** (Criar marco) ou **Save changes** (Salvar alterações). Os marcos irão renderizar a sintaxe do Markdown. Para obter mais informações sobre como criar links, consulte "[Sintaxe básica de gravação e formatação](/github/writing-on-github/basic-writing-and-formatting-syntax)".
 
 ### Excluir marcos
 
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/pt-BR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index 33fba0c11c..3b37fb60ae 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ Após a desabilitação dos quadros de projeto de repositório em uma organizaç
 
 Quando você desabilita quadros de projeto, deixa de ver informações relacionadas a eles em linhas do tempo ou [logs de auditoria](/articles/reviewing-the-audit-log-for-your-organization/).
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 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):
     - Para desabilitar quadros de projeto em toda a organização, desmarque **Enable projects for the organization** (Habilitar projetos da organização).
     - Para desabilitar quadros de projeto de repositório na organização, desmarque **Enable projects for all repositories** (Habilitar projetos de todos os repositórios). ![Caixas de seleção para desabilitar projetos de uma organização ou de todos os repositórios de uma organização](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index 44511158e0..c091d1f45b 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: Anexar arquivos em problemas e pull requests
-intro: 'Ao abrir um problema ou atualizar uma pull request, é possível usar a publicação de anexos para fazer upload de imagens de recursos propostos ou capturas de tela de erros.'
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -14,7 +14,7 @@ topics:
 
 {% warning %}
 
-**Aviso:** caso você inclua uma imagem para uma pull request ou comentário de problemas, qualquer pessoa poderá ver a URL anônima de imagem sem autenticação, mesmo se a pull request estiver em um repositório privado{% if enterpriseServerVersions contains currentVersion %} ou se o modo privado estiver habilitado{% endif %}. Para manter imagens confidenciais privadas, use uma rede privada ou um servidor que requer autenticação. {% if currentVersion == "free-pro-team@latest" %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs de imagem anônima](/articles/about-anonymized-image-urls)".{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ Para anexar um arquivo a uma conversa sobre um problema ou pull request, arraste
 
 {% endtip %}
 
-O tamanho máximo é de 25MB para arquivos e 10MB para imagens.
-{% if currentVersion == "free-pro-team@latest" %}
-Os vídeos podem ter até 100 MB de tamanho se o repositório pertencer a um usuário ou organização em um plano pago do GitHub.
-
-{% note %}
-
-**Observação:** O suporte a anexos de vídeo está atualmente em fase beta e está sujeito a alterações.
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 Arquivos compatíveis:
 
@@ -49,7 +43,7 @@ Arquivos compatíveis:
 * Documentos do Microsoft Word (*.docx*), Powerpoint (*.pptx*), e Excel (*.xlsx*)
 * Arquivos de texto (*.txt*)
 * PDFs (*.pdf*)
-* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" %}
+* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * Vídeo (*.mp4*, *.mov*){% endif %}
 
 ![Anexos GIF animados](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md
index 566006b588..3995259615 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md
@@ -1,6 +1,6 @@
 ---
-title: Linking a pull request to an issue
-intro: You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when the pull request is merged.
+title: Vinculando uma pull request a um problema
+intro: Você pode vincular um pull request a um problema para mostrar que uma correção está em andamento e para fechar automaticamente o problema quando o pull request for mesclado.
 redirect_from:
   - /articles/closing-issues-via-commit-message/
   - /articles/closing-issues-via-commit-messages/
@@ -16,37 +16,35 @@ topics:
 
 {% note %}
 
-**Note:** The special keywords in a pull request description are interpreted when the pull request targets the repository's *default* branch. However, if the PR's base is *any other branch*, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. **If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.**
+**Observação:** As palavras-chave especiais na descrição de um pull request são interpretadas quando o pull request aponta para o branch-padrão do *repositório*. No entanto, se a base do PR's for *qualquer outro branch*, essas palavras-chave serão ignoradas, nenhum link será criado e o merge do PR não terá efeito sobre os problemas. **Se você deseja vincular um pull request a um problema usando uma palavra-chave, o PR deverá estar no branch-padrão.**
 
 {% endnote %}
 
-### About linked issues and pull requests
+### Sobre problemas e pull requests vinculados
 
-You can link an issue to a pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}manually or {% endif %}using a supported keyword in the pull request description. 
+Você pode vincular um problema a um pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}manualmente ou {% endif %}usando uma palavra-chave compatível na descrição do pull request.
 
-When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue. {% if currentVersion ver_lt "enterprise-server@2.21" %}If the pull request and the issue are in different repositories, {% data variables.product.product_name %} will display the link after the pull request is merged, if the person who merges the pull request also has permission to close the issue.{% endif %}
+Quando você vincula uma pull request ao problema que a pull request tem de lidar, os colaboradores poderão ver que alguém está trabalhando no problema. {% if currentVersion ver_lt "enterprise-server@2. 1" %}Se o pull request e o problema estiverem em repositórios diferentes, {% data variables.product.product_name %} mostrará o link após o merge do pull request, se a pessoa que mescla o pull request também tiver permissão para fechar o problema.{% endif %}
 
-When you merge a linked pull request into the default branch of a repository, its linked issue is automatically closed. For more information about the default branch, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+Quando você mescla uma pull request vinculada no branch padrão de um repositório, o problema vinculado será fechado automaticamente. Para obter mais informações sobre o branch padrão, consulte "[Configurado o branch padrão](/github/administering-a-repository/setting-the-default-branch). "
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
-### Manually linking a pull request to an issue
+### Vinculando manualmente uma pull request a um problema
 
-Anyone with write permissions to a repository can manually link a pull request to an issue.
+Qualquer pessoa com permissões de gravação em um repositório pode vincular manualmente uma pull request a um problema.
 
-You can manually link up to ten issues to each pull request. The issue and pull request must be in the same repository.
+Você pode vincular manualmente até dez problemas para cada pull request. O problema e a pull request devem estar no mesmo repositório.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-3. In the list of pull requests, click the pull request that you'd like to link to an issue.
-4. In the right sidebar, click **Linked issues**.
-  ![Linked issues in the right sidebar](/assets/images/help/pull_requests/linked-issues.png)
-5. Click the issue you want to link to the pull request.
-  ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png)
+3. Na lista de pull requests, clique na pull request que você gostaria de vincular a um problema.
+4. Na barra lateral direita, clique em **Linked issues** (Problemas vinculados) ![Problemas vinculados na barra lateral direita](/assets/images/help/pull_requests/linked-issues.png)
+5. Clique no problema que você deseja associar à pull request. ![Menu suspenso para problemas vinculados](/assets/images/help/pull_requests/link-issue-drop-down.png)
 {% endif %}
 
-### Linking a pull request to an issue using a keyword
+### Vinculando uma pull request a um problema usando uma palavra-chave
 
-You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message (please note that the pull request must be on the default branch). 
+Você pode vincular uma solicitação de pull a um problema usando uma palavra-chave compatível na descrição do pull request ou em uma mensagem de commit (observe que a solicitação do pull deve estar no branch-padrão).
 
 * close
 * closes
@@ -55,21 +53,21 @@ You can link a pull request to an issue by using a supported keyword in the pull
 * fixes
 * fixed
 * resolve
-* resolves
+* resolve
 * resolved
 
-The syntax for closing keywords depends on whether the issue is in the same repository as the pull request.
+A sintaxe para fechar palavras-chave depende se o problema está no mesmo repositório que a pull request.
 
-Linked issue | Syntax | Example
---------------- | ------ | ------
-Issue in the same repository | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10`
-Issue in a different repository | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100`
-Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100`
+| Problemas vinculado                  | Sintaxe                                       | Exemplo                                                        |
+| ------------------------------------ | --------------------------------------------- | -------------------------------------------------------------- |
+| Problema no mesmo repositório        | *KEYWORD* #*ISSUE-NUMBER*                     | `Closes #10`                                                   |
+| Problema em um repositório diferente | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100`                                 |
+| Múltiplos problemas                  | Usar sintaxe completa para cada problema      | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` |
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}Apenas pull requests vinculados manualmente podem ser desvinculados. Para desvincular um problema que você vinculou usando uma palavra-chave, você deve editar a descrição da pull request para remover a palavra-chave.{% endif %}
 
-You can also use closing keywords in a commit message. The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request.
+Você também pode usar palavras-chave de fechamento em uma mensagem de commit. O problema será encerrado quando você mesclar o commit no branch padrão, mas o pull request que contém o commit não será listado como um pull request vinculado.
 
-### Further reading
+### Leia mais
 
-- "[Autolinked references and URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)"
+- "[Referências autovinculadas e URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)"
diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index 302f13be08..ddab866566 100644
--- a/translations/pt-BR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ Você pode ordenar qualquer exibição filtrada por:
 * Problemas ou pull requests com menos comentários
 * Prolemas ou pull requests com data de atualização mais recente
 * Prolemas ou pull requests com data de atualização mais antiga
-* Problemas ou pull requests com mais [reações](/articles/about-conversations-on-github#reacting-to-ideas-in-comments)
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. No canto superior direito, selecione o menu suspenso Sort (Ordenar). ![Usar a aba suspensa Sort (Ordenar)](/assets/images/help/issues/issues_sort_dropdown.png)
+1. No canto superior direito, selecione o menu suspenso Sort (Ordenar). ![Usar a aba suspensa Sort (Ordenar)](/assets/images/help/issues/issues_sort_dropdown.png)
 
 Para limpar a seleção da ordenação, clique em **Sort** (Ordenar) > **Newest** (Mais recente).
 
diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md
index 67f1997fe0..5aa2ad410d 100644
--- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ Você pode usar o qualificador `path` para pesquisar o código-fonte que aparece
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) identifica os arquivos JavaScript com a palavra "console" em um diretório <em>app/public</em> ou em seus subdiretórios (mesmo que eles residam em <em>app/public/js/form-validators</em>). |
 
 ### Pesquisar por linguagem
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-Você pode pesquisar código com base na linguagem na qual ele foi escrito.
+Você pode pesquisar código com base na linguagem na qual ele foi escrito. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | Qualifier                  | Exemplo                                                                                                                                                                                                     |
 | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 7afafa367e..213a6eb3da 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} Para obter mais informações, consulte "[Sobre limites de gastos](#about-spending-limits)".
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. Para obter mais informações, consulte "[Introdução a {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)".
+
+{% endnote %}
 
 Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar o seu ID de assinatura do Azure à sua conta corporativa para habilitar e pagar o uso de {% data variables.product.prodname_registry %}, além dos valores incluindo na sua conta. Para obter mais informações, consulte "[Conectar uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)".
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index d0a92e8d32..c6d07a1041 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### Leia mais
 
-- [Sobre o {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)"
-- "[Patrocinando contribuidores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)"
+- [Sobre o {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index d8b35024df..5b765e5414 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,36 +16,16 @@ Para discutir o licenciamento de {% data variables.product.prodname_GH_advanced_
 
 ### Sobre os números do committer para {% data variables.product.prodname_GH_advanced_security %}
 
-Registramos e exibimos dois números de committers para {% data variables.product.prodname_GH_advanced_security %} em {% data variables.product.prodname_dotcom_the_website %}:
-
-- **Committers** é o número de committers que contribuíram para pelo menos um repositório privado em uma organização e que usam uma estação na sua licença. Ou seja, eles também são integrantes da organização, um colaborador externo ou têm um convite pendente para ingressar em uma organização na sua empresa.
-- **Único para este repositório/organização** é o número de committers que contribuíram apenas para este repositório ou para repositórios nesta organização. Este número mostra a quantidade de estações de licença que você pode liberar, desabilitando {% data variables.product.prodname_GH_advanced_security %} para esse repositório ou organização.
-
-Se não houver committers exclusivos, isso significa que todos os committers ativos também contribuem para outros repositórios ou organizações que usam {% data variables.product.prodname_GH_advanced_security %}. Desabilitar o recurso para esse repositório ou organização não liberaria nenhuma estação na sua licença.
-
-{% note %}
-
-**Observação:** O número total de estações utilizadas na sua licença não é a soma dos committers ou dos committers únicos de cada repositório ou organização. Isso ocorre porque existem pessoas que contribuem para vários repositórios ou organizações. O número de estações utilizadas é medido em toda a conta da empresa para garantir que cada pessoa é contabilizada apenas uma vez, independentemente de quantos repositórios ou organizações contribuem.
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### Gerenciar o uso de sua licença para {% data variables.product.prodname_GH_advanced_security %}
 
-Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para um único repositório ou para todos os repositórios de uma organização, {% data variables.product.company_short %} irá mostrar quantos assentos adicionais ele usará e irá solicitar a confirmação. Se você desabilitar o acesso a {% data variables.product.prodname_GH_advanced_security %}, todas as estações usadas por committers "únicos" serão liberadas. Isso faz com que seja fácil entender o impacto das suas alterações no uso da sua licença.
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
-Se você exceder limite de licença, {% data variables.product.prodname_GH_advanced_security %} irá continuar a funcionar em todos os repositórios onde já está habilitado. No entanto, em organizações onde {% data variables.product.prodname_GH_advanced_security %} está habilitado para novos repositórios, os repositórios serão criados com o recurso desabilitado. Além disso, a opção de habilitar {% data variables.product.prodname_GH_advanced_security %} para repositórios existentes não estará disponível. Se você alterar a visibilidade de um repositório público para privado, {% data variables.product.prodname_GH_advanced_security %} será desabilitado para esse repositório.
+É possível aplicar políticas que permitam ou não o uso de {% data variables.product.prodname_advanced_security %} por parte de organizações pertencentes à conta corporativa. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)".
 
-Assim que você liberar algumas estações, desabilitando {% data variables.product.prodname_GH_advanced_security %} para alguns repositórios ou aumentando o tamanho da sua licença, as opções para habilitar {% data variables.product.prodname_GH_advanced_security %} funcionarão de novo normalmente.
-
-You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)."
-
-For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage)."
+Para obter mais informações sobre a visualização do uso da licença, consulte "[Visualizar o seu uso de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage)".
 
 ### Obtenha o máximo da sua licença de {% data variables.product.prodname_GH_advanced_security %}
 
-Ao decidir quais repositórios e organizações priorizar para {% data variables.product.prodname_GH_advanced_security %}, você deverá revisá-los e identificá-los:
-
-- As bases de código que são as mais críticas para o sucesso da sua empresa. Esses são os projetos em que a introdução de códigos vulneráveis, segredos codificados ou dependências vulneráveis teriam o maior impacto na sua empresa.
-- Bases de código com a maior frequência de commit. Estes são os projetos mais ativamente desenvolvidos e, consequentemente, há um risco maior de poder introduzir problemas de segurança.
-
-Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para essas organizações ou repositórios, você deverá avaliar quais outras bases de código você poderia adicionar sem adicionar quaisquer committers adicionais exclusivos e utilizando mais estações na sua licença. Depois disso, reveja as próximas bases de código mais importantes e ocupadas. Se você deseja aumentar o número de estações na sua licença, entre em contato com {% data variables.contact.contact_enterprise_sales %}.
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index a18f238eb7..c356d78572 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ Seus recibos incluem sua assinatura do {% data variables.product.prodname_dotcom
 ### Adicionar informações aos recibos da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### Adicionar informações ao recibos da sua organização
@@ -40,9 +40,9 @@ Seus recibos incluem sua assinatura do {% data variables.product.prodname_dotcom
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index c13d669b94..bf553ba517 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ Não fornecemos fatura nem damos suporte a ordens de compra para contas pessoais
 ### Atualizar a forma de pagamento da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### Atualizar a forma de pagamento da sua organização
@@ -38,9 +39,10 @@ Não fornecemos fatura nem damos suporte a ordens de compra para contas pessoais
 
 Se sua organização estiver fora dos EUA ou se você estiver usando uma conta de verificação corporativa para pagar pelo {% data variables.product.product_name %}, o PayPal pode ser uma forma prática de pagamento.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index 55f8ce73a3..04b1373c69 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ Quando você cancela uma versão de avaliação gratuita em um plano pago, a ass
 ### Cancelar um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### Cancelar a versão de avaliação gratuita de um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ Quando você cancela uma versão de avaliação gratuita em um plano pago, a ass
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ Quando você cancela uma versão de avaliação gratuita em um plano pago, a ass
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index 707f6bed9b..9146cb3d7f 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ Quando você altera a duração do ciclo de cobrança, sua assinatura do {% data
 ### Alterar a duração do ciclo de cobrança da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ Quando você altera a duração do ciclo de cobrança, sua assinatura do {% data
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ Quando você altera a duração do ciclo de cobrança, sua assinatura do {% data
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. Em "Billing overview" (Visão geral de cobrança), clique em **Change plan** (Alterar plano). ![Botão de alteração de plano na visão geral de cobrança](/assets/images/help/billing/billing_overview_change_plan.png)
 5. No canto superior direito, clique em **Switch to monthly billing** (Alternar para cobrança mensal) ou **Switch to yearly billing** (Alternar para cobrança anual). ![Seção de informações de cobrança](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index ac6087ec9a..9724bb145b 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ Se você já tem uma conta de usuário pessoal no {% data variables.product.prod
 
 ### Etapa 3: Atualizar a organização para uma assinatura paga anual
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (Você pode adicionar mais estações na organização na próxima etapa.)
 6. Em "Upgrade summary" (Atualizar resumo), selecione **Pay yearly** (Pagar anualmente) para pagar pela organização anualmente. ![Botão de rádio para cobrança anual](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. Em "Pay with" (Pagar com), digite as informações do seu cartão de crédito. ![Formulário para inserir informações do cartã de crédito](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. Clique em **Update credit card** (Atualizar cartão de crédito).
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### Etapa 4: Atualizar o número de estações pagas na organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index 91004c34d2..51d197477f 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -16,8 +16,7 @@ Quando você faz downgrade do número de pacotes de dados, as alterações entra
 ### Fazer downgrade de armazenamento e largura de banda de uma conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
@@ -25,10 +24,8 @@ Quando você faz downgrade do número de pacotes de dados, as alterações entra
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 3befe37688..e54ab39f4a 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ Quando você faz downgrade de um app, sua assinatura permanece ativa até o fina
 ### Fazer downgrade de um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ Quando você faz downgrade de um app, sua assinatura permanece ativa até o fina
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index 919a553059..a24b7ddce8 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ Quando você faz o downgrade (rebaixa) a assinatura da sua conta de usuário ou
 Se você fizer o downgrade da sua conta de usuário de {% data variables.product.prodname_pro %} para {% data variables.product.prodname_free_user %}, a conta perderá o acesso a ferramentas avançadas de revisão de código em repositórios privados. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Use o menu suspenso **Edit** (Editar) e clique em **Downgrade to Free** (Fazer downgrade para o Free). ![Botão Downgrade to free (Fazer downgrade para o Free)](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![Botão Downgrade to free (Fazer downgrade para o Free)](/assets/images/help/billing/downgrade-to-free.png)
 5. Leia as informações sobre os recursos aos quais sua organização deixará de ter acesso na próxima data de sua cobrança e clique em **Eu compreendi. Continue com o downgrade**. ![Continuar com o botão de downgrade](/assets/images/help/billing/continue-with-downgrade.png)
 
 Se você tiver publicado um site do {% data variables.product.prodname_pages %} em um repositório privado e adicionado um domínio personalizado, remova ou atualize seus registros DNS antes de fazer downgrade do {% data variables.product.prodname_pro %} para {% data variables.product.prodname_free_user %}, a fim de evitar o risco de uma aquisição de domínio. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
@@ -45,12 +44,10 @@ Se você fizer o downgrade da sua organização de {% data variables.product.pro
 
 Se você fizer o downgrade da sua organização de {% data variables.product.prodname_ghe_cloud %} para {% data variables.product.prodname_team %} ou {% data variables.product.prodname_free_team %}, a conta perderá o acesso a controles avançados de segurança, conformidade e implantação. {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Use o menu suspenso **Edit** (Editar) e clique na opção de downgrade que você deseja. ![Botão Downgrade (Fazer downgrade)](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![Botão Downgrade (Fazer downgrade)](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### Fazer downgrade da assinatura de uma organização com o preço antigo por repositório
@@ -59,10 +56,9 @@ Se você fizer o downgrade da sua organização de {% data variables.product.pro
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} Para obter mais informações, consulte "[Mudar sua organização de um preço por repositório para um preço por usuário](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Em "Assinaturas", selecione o menu suspenso "Editar" e clique em **Editar plano**. ![Menu suspenso Editar plano](/assets/images/help/billing/edit-plan-dropdown.png)
 1. Em "Billing/Plans" (Cobrança/Planos), ao lado do plano que deseja alterar, clique em **Downgrade**. ![Botão Downgrade (Fazer downgrade)](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. Insira o motivo pelo qual você está fazendo o downgrade da sua conta e clique em **Fazer downgrade do plano**. ![Caixa de texto para motivo de downgrade e botão de downgrade](/assets/images/help/billing/downgrade-plan-button.png)
@@ -74,12 +70,10 @@ Para reduzir o número de estações pagas usadas pela sua organização, remova
 - "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)"
 - "[Gerenciar o acesso de um indivíduo a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Use o menu suspenso **Edit** (Editar) e clique em **Remove seats** (Remover estações). ![menu suspenso para remover estações](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![menu suspenso para remover estações](/assets/images/help/billing/remove-seats-dropdown.png)
 1. Em "Remove seats" (Remover estações), selecione o número de estações em que você deseja fazer downgrade. ![opção de remover estações](/assets/images/help/billing/remove-seats-amount.png)
 1. Revise as informações sobre seu novo pagamento na sua próxima data de cobrança e clique em **Remove seats** (Remover estações). ![botão de remover estações](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index b1085c8764..7361d56c16 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ Como você não habilitou os excedentes, a sua próxima tentativa de criar um ar
 Qualquer pessoa pode gerenciar o limite de gastos do {% data variables.product.prodname_actions %} para sua própria conta de usuário.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Qualquer pessoa pode gerenciar o limite de gastos do {% data variables.product.p
 
 Proprietários de organizações e gestores de faturamento podem gerenciar o limite de gastos de {% data variables.product.prodname_actions %} para uma organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Em "
-{% data variables.product.prodname_actions %} e pacotes de uso mensal", clique em **Gestão de custo**.
-  ![Aba de gestão de custos](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index 03532b9719..256549d7a5 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ Como você não ativou os excessos, sua próxima tentativa de publicar uma vers
 Qualquer pessoa pode gerenciar o limite de gastos do {% data variables.product.prodname_registry %} para sua própria conta de usuário.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Qualquer pessoa pode gerenciar o limite de gastos do {% data variables.product.p
 
 Proprietários de organizações e gestores de faturamento podem gerenciar o limite de gastos de {% data variables.product.prodname_registry %} para uma organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Em "
-{% data variables.product.prodname_actions %} e pacotes de uso mensal", clique em **Gestão de custo**.
-  ![Aba de gestão de custos](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index 634779b11b..99297fae28 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ Se estiver pagando a assinatura do {% data variables.product.product_name %} com
 ### Remover a forma de pagamento da conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ Se estiver pagando a assinatura do {% data variables.product.product_name %} com
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index 587c747281..0369f1c46e 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### Atualizar as informações de cartão de crédito da organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. Insira as informações do novo cartão de crédito no formulário seguro. ![Formulário de informações do cartão de crédito](/assets/images/help/settings/creditcard-billing-form.png)
-1. Clique em **Update credit card** (Atualizar cartão de crédito) ou em **Save credit card** (Salvar cartão de crédito).
+1. Under "Payment method", click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index 19d7643f51..0b209527dd 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ O e-mail de cobrança da organização é o endereço para o qual o {% data vari
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Em **Billing email** (E-mail de cobrança), insira um endereço de e-mail válido. O e-mail não precisa ser exclusivo na conta da organização. ![Caixa de texto Billing email (E-mail de cobrança)](/assets/images/help/settings/org-billing-email.png)
 5. Para confirmar as alterações, clique em **Update profile** (Atualizar perfil). ![Botão Update profile (Atualizar perfil)](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ Se você tiver usuários que desejem receber relatórios de cobrança, você pod
 #### Adicionar um destinatário para notificações de cobrança
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Em gerenciamento de cobrança, à direita "destinatários de e-mail", clique em **Adicionar**. ![Adicionar destinatário](/assets/images/help/billing/billing-add-email-recipient.png)
 1. Digite o endereço de e-mail do destinatário e, em seguida, clique em **Adicionar**. ![Adicionar modal de destinatário](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ Se você tiver usuários que desejem receber relatórios de cobrança, você pod
 Deve-se sempre designar um endereço como o destinatário principal. O endereço com esta designação não pode ser removido até que um novo destinatário principal seja selecionado.
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Em "Gestão de cobrança", encontre o endereço de e-mail que deseja definir como principal destinatário.
 1. À direita do endereço de e-mail, use o menu suspenso "Editar" e, em seguida, clique em **Marcar como primário**. ![Marque o destinatário primário](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### Remover um destinatário das notificações de cobrança
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Em "Destinatários de e-mail", encontre o endereço de e-mail que deseja remover.
 1. Para inserir o usuário na lista, clique em **Editar**. ![Editar destinatário](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. À direita do endereço de e-mail, use o menu suspenso "Editar" e clique em *Remover**. ![Remover destinatário](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![Remover destinatário](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. Revise a instrução de confirmação e clique em **Remover**.
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index b4ade08a25..ed70ba5cec 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### Comprar mais armazenamento e largura de banda para uma conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index 31216ebdb7..ce5fe68666 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,11 +22,9 @@ topics:
 
 ### Atualizar o número de estações pagas de uma organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -35,10 +33,8 @@ Depois que você adicionar as estações, será cobrado na forma de pagamento re
 
 ### Fazer downdgrade do número de estações pagas de uma organização para gratuitas
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 7311fb085a..f76bd643d1 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ Quando você atualiza um app, é cobrado na forma de pagamento um valor proporci
 ### Atualizar um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ Quando você atualiza um app, é cobrado na forma de pagamento um valor proporci
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index 2154e9d363..163f6c86c5 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 Você pode atualizar sua conta pessoal do {% data variables.product.prodname_free_user %} para o {% data variables.product.prodname_pro %} para obter ferramentas de revisão de código avançadas em repositórios privados. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Ao lado de "
-{% data variables.product.prodname_free_user %}", clique em **Atualizar**.
-  ![Botão Upgrade (Atualizar)](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![Botão Upgrade (Atualizar)](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ Você pode atualizar sua organização de {% data variables.product.prodname_fre
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ Caso queira usar uma conta corporativa com o {% data variables.product.prodname_
 
 Se você quiser que outros usuários tenham acesso aos repositórios privados da organização {% data variables.product.prodname_team %}, você poderá comprar mais estações a qualquer momento.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ Se você quiser que outros usuários tenham acesso aos repositórios privados da
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. À direita do nome do seu plano, use o menu suspenso **Editar** e selecione **Editar plano**. ![Menu suspenso de editar](/assets/images/help/billing/per-user-upgrade-button.png)
 6. À direita das "Ferramentas avançadas para equipes", clique em **Atualizar agora**. ![Botão Atualizar agora](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index e6212a72a1..f0d839d857 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ Quando você cancela uma alteração pendente, sua assinatura não é alterada n
 ### Exibir e gerenciar alterações pendentes na assinatura da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### Exibir e gerenciar alterações pendentes na assinatura da sua organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index 3d0281a14f..094535f682 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### Exibir o uso de armazenamento e largura de banda de uma conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Exibir o uso de armazenamento e largura de banda de uma organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Leia mais
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index e96b512458..931a0ca692 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ Você também pode visualizar os minutos de execução do trabalho faturáveis p
 Qualquer pessoa pode visualizar o uso de {% data variables.product.prodname_actions %} para sua própria conta de usuário.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ Qualquer pessoa pode visualizar o uso de {% data variables.product.prodname_acti
 
 Os proprietários da organização e gerentes de faturamento podem ver o uso do {% data variables.product.prodname_actions %} para uma organização. Para organizações gerenciadas por uma conta corporativa, somente os proprietários da organização podem visualizar o uso do {% data variables.product.prodname_actions %} na página de cobrança da organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -38,7 +37,7 @@ Proprietários de organizações e gestores de faturamento podem visualizar o us
 
 {% note %}
 
-**Observação:** As informações de cobrança para contas corporativas não resumem os minutos de uso para cada sistema operacional. {% data reusables.github-actions.enterprise-billing-details %}
+**Nota:** Os detalhes de faturamento para contas corporativas não resumem os minutos de uso para cada sistema operacional. {% data reusables.github-actions.enterprise-billing-details %}
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index a430ac4c47..b7a9c9a5d0 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,24 +1,24 @@
 ---
 title: Visualizar o seu uso do GitHub Advanced Security
-intro: 'Você pode visualizar e gerenciar o uso de sua licença do {% data variables.product.prodname_GH_advanced_security %}.'
-permissions: 'Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
+intro: 'Você pode visualizar o uso de sua licença do {% data variables.product.prodname_GH_advanced_security %}.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
   free-pro-team: '*'
 ---
 
-Cada licença de {% data variables.product.prodname_GH_advanced_security %} especifica um número máximo de contas, ou estações, que podem usar essas funcionalidades. Periodicamente você deve verificar que sua utilização está dentro da sua capacidade de licença. Para obter mais informações, consulte "[Sobre licenciamento para licença corporativa de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)".
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
 
-### Visualizar e gerenciar o uso da licença de {% data variables.product.prodname_GH_advanced_security %} para a sua conta corporativa
+### Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
 
-Você pode verificar quantas estações a sua licença inclui e quantas delas são usadas atualmente na página de "Licenciamento corporativo".
+You can check how many seats your license includes and how many of them are currently used.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-   A seção "{% data variables.product.prodname_GH_advanced_security %}" mostra os detalhes do uso atual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Se você ficar sem estações, a seção ficará vermelha. Você deve quer reduzir o seu uso de {% data variables.product.prodname_GH_advanced_security %} ou comprar mais estações. Para obter mais informações, consulte "[Sobre licenciamento para licença corporativa de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)". ![{% data variables.product.prodname_GH_advanced_security %} em configurações de licenciamento corporativo](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
-4. Opcionalmente, para ver uma análise detalhada do uso por organização, clique em **Cobrança**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) Na seção "{% data variables.product.prodname_GH_advanced_security %}", você pode ver o número de committers e committers únicos para cada organização. ![{% data variables.product.prodname_GH_advanced_security %} em configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise.png)
+   A seção "{% data variables.product.prodname_GH_advanced_security %}" mostra os detalhes do uso atual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Se você ficar sem estações, a seção ficará vermelha. Você deve quer reduzir o seu uso de {% data variables.product.prodname_GH_advanced_security %} ou comprar mais estações. Para obter mais informações, consulte "[Sobre licenciamento para {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)". ![{% data variables.product.prodname_GH_advanced_security %} em configurações de licenciamento corporativo](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. Opcionalmente, para ver uma análise detalhada do uso por organização, clique em **Cobrança**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) Na seção "{% data variables.product.prodname_GH_advanced_security %}", você pode ver o número de committers e committers únicos para cada organização. ![{% data variables.product.prodname_GH_advanced_security %} em configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
 5. Opcionalmente, clique no nome de uma organização em que você é um proprietário para exibir as configurações de segurança e análise para a organização. ![Organização proprietária na seção de {% data variables.product.prodname_GH_advanced_security %} das configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
 6. Na página de configurações "Análise de & segurança" desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}" para ver uma descrição detalhada do uso por repositório para esta organização. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)".
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index ae95a62662..a2ca8dd5e2 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 Qualquer pessoa pode visualizar o uso de {% data variables.product.prodname_registry %} para sua própria conta de usuário.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ Qualquer pessoa pode visualizar o uso de {% data variables.product.prodname_regi
 
 Os proprietários da organização e gerentes de cobrança podem ver o uso do {% data variables.product.prodname_registry %} para uma organização. Para organizações gerenciadas por uma conta corporativa, somente os proprietários da organização podem visualizar o uso do {% data variables.product.prodname_registry %} na página de cobrança da organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index 083789c584..dfb72bf296 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### Exibir recibos da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index 39d2716f55..4a4d43ceff 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### Localizar a próxima data de cobrança da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Localizar a próxima data de cobrança da sua organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Leia mais
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md
index a0f9e74965..9e850f3ec4 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account.md
@@ -13,7 +13,7 @@ topics:
 
 Proprietários corporativos podem criar novas organizações nas configurações da conta corporativa.
 
-Para adicionar uma organização à sua conta corporativa, você deve criar a organização dentro das configurações de conta corporativa. If you want to transfer an existing organization to your enterprise account, contact your {% data variables.product.prodname_dotcom %} sales account representative.
+Para adicionar uma organização à sua conta corporativa, você deve criar a organização dentro das configurações de conta corporativa. Se você deseja transferir uma organização existente para a conta corporativa, entre em contato com a representante de vendas da sua conta de {% data variables.product.prodname_dotcom %}.
 
 ### Criar uma organização em sua conta corporativa
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index 0f1c18bea5..0b6980738b 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -36,5 +36,5 @@ Após desconectar a sua assinatura Azure da conta corporativa, seu uso não pode
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Em "Assinatura do Azure", à direita do ID de assinatura que você deseja desconectar, clique em **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
+1. Em "Assinatura do Azure", à direita do ID de assinatura que você deseja desconectar, clique em **{% octicon "trash" aria-label="The trash icon" %}**.
 1. Revise a instrução e clique em **Remover**.
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index 85e4723bf5..523eb427d3 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -48,3 +48,21 @@ Você pode desabilitar todos os fluxos de trabalho para uma empresa ou definir u
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### Definir as permissões do `GITHUB_TOKEN` para a sua empresa
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para sua empresa, organizações ou repositórios. Se você escolher a opção restrita como padrão nas configurações da empresa, isto impedirá que a configuração mais permissiva seja escolhida nas configurações da organização ou repositório.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configurar as permissões padrão do `GITHUB_TOKEN`
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Em **permissões do fluxo de trabalho**, escolha se você quer que o `GITHUB_TOKEN` tenha acesso de leitura e gravação para todos os escopos, ou apenas acesso de leitura para o escopo do </code>conteúdo.
+<img src="/assets/images/help/settings/actions-workflow-permissions-enterprise.png" alt="Definir permissões do GITHUB_TOKEN para esta empresa" /></p></li>
+<li><p spaces-before="0">Clique em <strong x-id="1">Salvar</strong> para aplicar as configurações.</p></li>
+</ol>
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md
index 023e257e77..36301e35e5 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing policies for Advanced Security in your enterprise account
-intro: 'Enterprise owners can enforce policies to manage {% data variables.product.prodname_GH_advanced_security %} features for organizations owned by an enterprise account.'
+title: Aplicar políticas de Segurança Avançada na sua conta corporativa
+intro: 'Os proprietários da empresa podem impor políticas para gerenciar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para organizações que pertencem a uma conta corporativa.'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
   free-pro-team: '*'
@@ -10,7 +10,7 @@ versions:
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
-### Enforcing a policy for {% data variables.product.prodname_advanced_security %} features
+### Aplicar uma política para funcionalidades de {% data variables.product.prodname_advanced_security %}
 
 {% data reusables.advanced-security.about-ghas-organization-policy %}
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md
index c37a622cfc..69f6c5cfed 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..e3b6964421
--- /dev/null
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: Restringir notificações de e-mail para a conta corporativa
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### Sobre restrições de e-mail para a sua conta corporativa
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restringir notificações de e-mail para a conta corporativa
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..df1529b329
--- /dev/null
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Sobre a verificação do domínio
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index 138495dd33..0068de3040 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -20,6 +20,15 @@ Ao ativar o logon único do SAML para a sua conta corporativa, cada integrante d
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index b88250d292..929eecc6c7 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 Se desejar, você pode optar por adicionar uma descrição, um local, um site e um endereço de e-mail para sua organização, além de fixar repositórios importantes no topo da página.
 
-{% if currentVersion == "free-pro-team@latest" %}Para confirmar a identidade da sua organização e exibir um selo "Verificado" na página de perfil da sua organização, você deve verificar os domínios da sua organização com {% data variables.product.product_name %}. Par obter mais informações, consulte "[Verificar o domínio da sua organização](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+{% if currentVersion == "free-pro-team@latest" %}Para confirmar a identidade da sua organização e exibir um selo "Verificado" na página de perfil da sua organização, você deve verificar os domínios da sua organização com {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![Exemplo de página de perfil verificada da organização](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md
index 1ab3ea7492..670ae67e93 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: About your profile
-intro: 'Your profile page tells people the story of your work through the repositories you''re interested in, the contributions you''ve made, and the conversations you''ve had.'
+title: Sobre seu perfil
+intro: 'Sua página de perfil conta a história do seu trabalho por meio de repositórios nos quais você está interessado, das contribuições que fez e das conversas que teve.'
 redirect_from:
   - /articles/viewing-your-feeds/
   - /articles/profile-pages/
@@ -13,29 +13,29 @@ topics:
   - Profiles
 ---
 
-You can add personal information about yourself in your bio, like previous places you've worked, projects you've contributed to, or interests you have that other people may like to know about. For more information, see "[Adding a bio to your profile](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)."
+Você pode adicionar informações pessoais sobre si mesmo na bio, como locais em que trabalhou anteriormente, os projetos com os quais contribuiu ou interesses que você tem que outras pessoas talvez gostem de saber. Para obter mais informações, consulte "[Adicionar uma bio ao seu perfil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)".
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 
 {% data reusables.profile.profile-readme %}
 
-![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png)
+![Arquivo README do perfil exibido no perfil](/assets/images/help/repository/profile-with-readme.png)
 
 {% endif %}
 
-People who visit your profile see a timeline of your contribution activity, like issues and pull requests you've opened, commits you've made, and pull requests you've reviewed. You can choose to display only public contributions or to also include private, anonymized contributions. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" or "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+As pessoas que visitam seu perfil veem uma linha do tempo da sua atividade de contribuição, como problemas e pull requests que abriu, commits que fez e pull requests que revisou. Você pode optar por exibir apenas contribuições públicas ou também incluir contribuições privadas e anônimas. Para obter mais informações, consulte "[Exibir contribuições na sua página de perfil](/articles/viewing-contributions-on-your-profile-page)" ou "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)".
 
-People who visit your profile can also see the following information.
+As pessoas que visitam seu perfil também podem ver as informações a seguir.
 
-- Repositories and gists you own or contribute to. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can showcase your best work by pinning repositories and gists to your profile. For more information, see "[Pinning items to your profile](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)."{% endif %}
-- Repositories you've starred. For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)."
-- An overview of your activity in organizations, repositories, and teams you're most active in. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% if currentVersion == "free-pro-team@latest" %}
-- Badges that show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)."{% endif %}
+- Repositórios e gists que você possui ou com os quais contribui. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contém currentVersion %}Você pode exibir o melhor trabalho fixando repositórios e gists no seu perfil. Para obter mais informações, consulte "[Fixar itens no seu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)".{% endif %}
+- Repositórios que você salvou com estrela. Para obter mais informações, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)."
+- Uma visão geral da sua atividade em organizações, repositórios e equipes nos quais você está mais ativo. Para obter mais informações, consulte "[Exibir uma visão geral da sua atividade no seu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% if currentVersion == "free-pro-team@latest" %}
+- Selos que serão exibidos se você usar {% data variables.product.prodname_pro %} ou participar de programas como {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %} ou do programa de desenvolvedor de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Personalizar seu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)".{% endif %}
 
-You can also set a status on your profile to provide information about your availability. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)."
+Você também pode definir um status no seu perfil para fornecer informações sobre a sua disponibilidade. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)".
 
-### Further reading
+### Leia mais
 
-- "[How do I set up my profile picture?](/articles/how-do-i-set-up-my-profile-picture)"
-- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
-- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
+- "[Como configurar minha foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)"
+- "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
+- "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)"
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index 41ede48013..d46084ec18 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ Se você selecionar a opção "Busy" (Ocupado), quando as pessoas fizerem @menç
 
 Ao participar de determinados programas, {% data variables.product.prodname_dotcom %} exibe automaticamente um selo no seu perfil.
 
-| Selo                                                            | Programa                                                             | Descrição                                                                                                                                                                                                                                                                                                                                                                |
-| --------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Se você criou algum(ns) commit(s) no branch-padrão de um repositório arquivado no programa Cofre do Ártico 2020, você receberá um selo de contribuidor de {% data variables.product.prodname_arctic_vault %} no seu perfil. Para obter mais informações sobre o programa, consulte [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **Integrante do programa de desenvolvedores**                        | Se você for um integrante registrado do Programa de Desenvolvedor do GitHub, ao criar um aplicativo com a API do GitHub, você receberá um selo de integrante do programa de desenvolvedor no seu perfil. Para obter mais informações sobre o Programa de Desenvolvedor do GitHub, consulte o [Desenvolvedor do GitHub](/program/).                                       |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **Patrocinador do GitHub**                                           | Se você patrocinou um contribuidor de código aberto por meio de {% data variables.product.prodname_sponsors %}, você receberá um selo de patrocinador no seu perfil. Para obter mais informações, consulte "[Patrocinar contribuidores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)".        |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                              | Se você usar {% data variables.product.prodname_pro %}, você receberá um selo PRO no seu perfil. Para obter mais informações sobre o {% data variables.product.prodname_pro %}, consulte "[Produtos do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)".                                                |
+| Selo                                                                                                                                   | Programa                                                             | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter Contributor badge icon](/assets/images/help/profile/badge-mars-2020-small.png)                                  | **Mars 2020 Helicopter Contributor**                                 | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Passar o mouse sobre o selo mostra vários dos repositórios para os quais você contribuiu na missão. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
+| ![Arctic Code Vault Contributor badge icon](/assets/images/help/profile/badge-arctic-code-vault-small.png)                             | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Se você criou algum(ns) commit(s) no branch-padrão de um repositório arquivado no programa Cofre do Ártico 2020, você receberá um selo de contribuidor de {% data variables.product.prodname_arctic_vault %} no seu perfil. Passar o mouse sobre o selo mostra vários dos repositórios para os quais você contribuiu que faziam parte do programa. Para obter mais informações sobre o programa, consulte [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com).                                                                                                                                                     |
+| ![Ícone do selo de patrocinador de {% data variables.product.prodname_dotcom %}](/assets/images/help/profile/badge-sponsors-small.png) | **Patrocinador de {% data variables.product.prodname_dotcom %}**     | Se você patrocinou um contribuidor de código aberto por meio de {% data variables.product.prodname_sponsors %} você receberá um selo do Sponsor de {% data variables.product.prodname_dotcom %} no seu perfil. Clicar no selo direcionará você para a aba **Patrocínio** do seu perfil. Para obter mais informações, consulte "[Patrocinar contribuidores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)".                                                                                                                                                              |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                                            | **Integrante do programa de desenvolvedores**                        | Se você é um integrante registrado do Programa de Desenvolvedores de {% data variables.product.prodname_dotcom %} que está criando um aplicativo com a API de {% data variables.product.prodname_dotcom %} você receberá um selo de integrante do Programa de Desenvolvimento no seu perfil. Para obter mais informações sobre o Programa de Desenvolvedores de {% data variables.product.prodname_dotcom %}, consulte o [Desenvolvedor do GitHub](/program/).                                                                                                                                                                                    |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                                                   | **Pro**                                                              | Se você usar {% data variables.product.prodname_pro %}, você receberá um selo PRO no seu perfil. Para obter mais informações sobre o {% data variables.product.prodname_pro %}, consulte "[Produtos do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)".                                                                                                                                                                                                                                                                                                                           |
 
 ### Desabilitar selos no seu perfil
 
-Você pode desabilitar alguns dos selos dos programas de {% data variables.product.prodname_dotcom %} dos quais você está participando, incluindo os selos PRO e {% data variables.product.prodname_arctic_vault %}.
+You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
 
 {% data reusables.user_settings.access_settings %}
-2. Em "Configurações de perfil", desmarque o selo que você deseja desabilitar. ![Caixa de seleção para deixar de exibir um selo no seu perfil](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. Em "Configurações de perfil", desmarque o selo que você deseja desabilitar. ![Caixa de seleção para deixar de exibir um selo no seu perfil](/assets/images/help/profile/profile-badge-settings.png)
 3. Clique em **Update preferences** (Atualizar preferências).
 
 {% endif %}
 
+### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
+
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+
+| {% data variables.product.prodname_dotcom %} Repository                       | Versão    | Tag                                                                                                        |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.2       | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### Leia mais
 
 - "[Sobre seu perfil](/articles/about-your-profile)"
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md
index b67b17f237..f6e66bfa8a 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing contributions on your profile
-intro: 'Your {% data variables.product.product_name %} profile shows off {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.'
+title: Exibir contribuições no perfil
+intro: 'Seu perfil de {% data variables.product.product_name %} exibe {% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %}os seus repositórios fixados, bem como{% endif %} um gráfico de contribuições de repositório ao longo do último ano.'
 redirect_from:
   - /articles/viewing-contributions/
   - /articles/viewing-contributions-on-your-profile-page/
@@ -13,88 +13,91 @@ topics:
   - Profiles
 ---
 
-{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Seu gráfico de contribuição mostra a atividade dos repositórios públicos. {% endif %}Você pode escolher mostrar a atividade dos {% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %}repositórios públicos e {% endif %}privados, com informações específicos da atividade em repositórios privados anonimizados. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)".
 
 {% note %}
 
-**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
+**Observação:** Os commits só aparecerão no seu gráfico de contribuições se o endereço de e-mail que você usou para criar das submissões estiver conectado à sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
 
 {% endnote %}
 
-### What counts as a contribution
+### O que conta como contribuição
 
-On your profile page, certain actions count as contributions:
+Na sua página de perfil, determinadas ações contam como contribuições:
 
-- Committing to a repository's default branch or `gh-pages` branch
-- Opening an issue
-- Proposing a pull request
-- Submitting a pull request review{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
-- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %}
+- Fazer commit no branch `gh-pages` ou no branch padrão de um repositório
+- Abrir um problema
+- Abrir uma discussão
+- Responder a uma discussão
+- Propor uma pull request
+- Enviar uma revisão de pull request{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- Fazer coautoria de commits no branch `gh-pages` ou no branch padrão do repositório{% endif %}
 
 {% data reusables.pull_requests.pull_request_merges_and_contributions %}
 
-### Popular repositories
+### Repositórios populares
 
-This section displays your repositories with the most watchers. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %}
+Esta seção exibe os repositórios com a maioria dos inspetores. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contém currentVersion %}Após [fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile), esta seção irá mudar para "Repositórios fixos".{% endif %}
 
-![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png)
+![Repositórios populares](/assets/images/help/profile/profile_popular_repositories.png)
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-### Pinned repositories
+### Repositórios fixos
 
-This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)."
+Esta seção exibe até seis repositórios públicos e pode incluir tanto repositórios pertencentes a você como aqueles com os quais você contribuiu. Para ver detalhes importantes sobre os repositórios que você escolheu retratar, cada repositório nesta seção inclui um resumo do trabalho que está sendo feito, o número de [estrelas](/articles/saving-repositories-with-stars/) que ele recebeu e a principal linguagem de programação usada nele. Para obter mais informações, consulte "[Fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile)".
 
-![Pinned repositories](/assets/images/help/profile/profile_pinned_repositories.png)
+![Repositórios fixos](/assets/images/help/profile/profile_pinned_repositories.png)
 
 {% endif %}
 
-### Contributions calendar
+### Calendário de contribuições
 
-Your contributions calendar shows your contribution activity.
+O calendário de contribuições mostra sua atividade de contribuição.
 
-#### Viewing contributions from specific times
+#### Exibir contribuições de horários específicos
 
-- Click on a day's square to show the contributions made during that 24-hour period.
-- Press *Shift* and click on another day's square to show contributions made during that timespan.
+- Clique no quadrado de um dia para mostrar as contribuições feitas durante esse período de 24 horas.
+- Pressione *Shift* e clique no quadrado de outro data para mostrar as contribuições feitas durante esse período.
 
 {% note %}
 
-**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger timespan, we will only display one month of contributions.
+**Observação:** só é possível selecionar um intervalo de até um mês no calendário de contribuições. Se você selecionar um período maior, será exibido apenas um mês de contribuições.
 
 {% endnote %}
 
-![Your contributions graph](/assets/images/help/profile/contributions_graph.png)
+![Gráfico de contribuição](/assets/images/help/profile/contributions_graph.png)
 
-#### How contribution event times are calculated
+#### Como são calculados os horários de evento de contribuição
 
-Timestamps are calculated differently for commits and pull requests:
-- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)."
-- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes).
+Os registros de data e hora são calculados de forma diferente para commits e pull requests:
+- Os **commits** usam as informações de fuso horário no registro de data e hora do commit. Para obter mais informações, consulte "[Solucionar problemas de commits na linha do tempo](/articles/troubleshooting-commits-on-your-timeline)".
+- As **pull requests** e os **problemas** abertos no {% data variables.product.product_name %} usam o fuso horário do navegador. Os abertos pela API usam o registro de data e hora ou o fuso horário [especificado na chamada de API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes).
 
-### Activity overview
+### Visão geral de atividade
 
-{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+{% data reusables.profile.activity-overview-summary %} Para obter mais informações, consulte "[Exibir a visão geral das atividades no perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)".
 
-![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png)
+![Seção Visão geral de atividade no perfil](/assets/images/help/profile/activity-overview-section.png)
 
-The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see “[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)."
+As organizações retratadas na visão geral da atividade são priorizadas de acordo com a forma como você está ativo na organização. Se você for integrante de uma organização e @mencioná-la na bio do perfil, essa organização será priorizada na visão geral da atividade. Para obter mais informações, consulte “[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” ou "[Adicionar uma bio ao seu perfil](/articles/adding-a-bio-to-your-profile/)".
 
-### Contribution activity
+### Atividade de contribuição
 
-The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened.
+A seção de atividade de contribuição contém uma linha do tempo detalhada do seu trabalho, incluindo commits feitos exclusivamente por você ou em coautoria, solicitações de pull que você propôs e problemas que você abriu. Para ver suas contribuições ao longo do tempo, clique em **Mostrar mais atividade** na parte inferior da atividade de contribuição ou clique no ano em que você está interessado em visualizar, no lado direito da página. Momentos importantes, como a data em que você ingressou na organização, propôs sua primeira pull request ou abriu um problema relevante, são realçados na atividade de contribuição. Se você não conseguir ver determinados eventos na sua linha do tempo, verifique se ainda tem acesso à organização ou ao repositório em que o evento aconteceu
 
-![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png)
+![Filtro de hora de atividade de contribuição](/assets/images/help/profile/contributions_activity_time_filter.png)
 
 {% if currentVersion != "github-ae@latest" %}
-### Viewing contributions from {% data variables.product.product_location_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
+### Exibir contribuições da {% data variables.product.product_location_enterprise %} no {% data variables.product.prodname_dotcom_the_website %}
+Se o administrador do site habilitou
 
-If your site administrator has enabled {% data variables.product.prodname_unified_contributions %}, you can send {% data variables.product.prodname_enterprise %} contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending your {% data variables.product.prodname_ghe_server %} contributions to your {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)."
+{% data variables.product.prodname_unified_contributions %}, você pode enviar contagens de contribuição de {% data variables.product.prodname_enterprise %} para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Enviar suas contribuições do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)".
 {% endif %}
 
-### Further reading
+### Leia mais
 
-- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
-- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
-- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
-- "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)"
+- "[Visualizar contribuições na página de perfil](/articles/viewing-contributions-on-your-profile-page)"
+- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
+- "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
+- "[Exibir a visão geral das atividades no perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)"
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
index 14f5ae117a..7f4c8bf60b 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -25,7 +25,7 @@ Os commits aparecerão no gráfico de contribuições se atenderem a **todas** e
   - No branch-padrão do repositório
   - No branch `gh-pages` (para repositórios com sites de projetos)
 
-For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Para obter mais informações sobre sites de projeto, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Além disso, **pelo menos uma** das seguintes afirmativas devem ser verdadeiras:
 - Você é um colaborador no repositório ou um integrante da organização que possui o repositório.
@@ -66,7 +66,7 @@ Não é possível adicionar endereços de e-mail genéricos, como `jane@computer
 
 #### O commit não foi criado no branch `gh-pages` ou padrão
 
-Os commits só são contados se forem feitos no branch-padrão ou no branch `gh-pages` (para repositórios com sites de projeto). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Os commits só são contados se forem feitos no branch-padrão ou no branch `gh-pages` (para repositórios com sites de projeto). Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Se os commits estiverem em um branch que não seja `gh-pages` ou o padrão e você quiser que eles sejam contabilizados para suas contribuições, precisará seguir um destes procedimentos:
 - [Abrir uma pull request](/articles/creating-a-pull-request) para que ocorra o merge das alterações no branch `gh-pages` ou padrão.
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md
index 2e9edad892..9a90934e37 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md
@@ -1,10 +1,10 @@
 ---
-title: About your personal dashboard
+title: Sobre seu painel pessoal
 redirect_from:
   - /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github/
   - /articles/opting-into-the-public-beta-for-a-new-dashboard/
   - /articles/about-your-personal-dashboard
-intro: 'You can visit your personal dashboard to keep track of issues and pull requests you''re working on or following, navigate to your top repositories and team pages, stay updated on recent activities in organizations and repositories you''re subscribed to, and explore recommended repositories.'
+intro: 'Você pode visitar seu painel pessoal para acompanhar problemas e pull requests nos quais está trabalhando ou seguindo, navegar para os repositórios principais e páginas de equipe, manter-se atualizado sobre atividades recentes nas organizações e nos repositórios em que está inscrito e explorar repositórios recomendados.'
 versions:
   free-pro-team: '*'
   enterprise-server: '*'
@@ -13,46 +13,46 @@ topics:
   - Accounts
 ---
 
-### Accessing your personal dashboard
+### Acessar seu painel pessoal
 
-Your personal dashboard is the first page you'll see when you sign in on {% data variables.product.product_name %}.
+Seu quadro pessoal é a primeira página que você verá quando entrar no {% data variables.product.product_name %}.
 
-To access your personal dashboard once you're signed in, click the {% octicon "mark-github" aria-label="The github octocat logo" %} in the upper-left corner of any page on {% data variables.product.product_name %}.
+Para acessar seu quadro pessoal assim que se conectar, clique no {% octicon "mark-github" aria-label="The github octocat logo" %} no canto superior esquerdo de qualquer página em {% data variables.product.product_name %}.
 
-### Finding your recent activity
+### Encontrar sua atividade recente
 
-In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests you're working on. Under "Recent activity", you can preview up to 12 recent updates made in the last two weeks.
+Na seção "Recent activity" (Atividade recente) do feed de notícias, você pode encontrar e acompanhar problemas e pull requests recém-atualizados nos quais você está trabalhando, além de visualizar até 12 atualizações recentes feitas nas últimas duas semanas.
 
 {% data reusables.dashboard.recent-activity-qualifying-events %}
 
-### Finding your top repositories and teams
+### Encontrar equipes e repositórios principais
 
-In the left sidebar of your dashboard, you can access the top repositories and teams you use.
+Na barra lateral esquerda do painel, é possível acessar os repositórios e equipes principais que usa.
 
-![list of repositories and teams from different organizations](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png)
+![lista de repositórios e equipes de diferentes organizações](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png)
 
-The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list 4 months after you last interacted with them.
+A lista dos principais repositórios é gerada automaticamente e pode incluir qualquer repositório com o qual você interagiu, independentemente de pertencer diretamente à sua conta. As interações incluem criação commits, abrir ou comentar em problemas e pull requests. A lista dos principais repositórios não pode ser editada, mas os repositórios serão excluídos da lista 4 meses após a última vez que você interagir com eles.
 
-You can also find a list of your recently visited repositories, teams, and project boards when you click into the search bar at the top of any page on {% data variables.product.product_name %}.
+Também é possível encontrar uma lista de seus repositórios, equipes e quadros de projeto recentemente visitados quando você clica na barra de pesquisa no topo de qualquer página do {% data variables.product.product_name %}.
 
-### Staying updated with activity from the community
+### Permanecer atualizado com as atividades da comunidade
 
-In the "All activity" section of your news feed, you can view updates from repositories you're subscribed to and people you follow. The "All activity" section shows updates from repositories you watch or have starred, and from users you follow.
+Na seção "All activity" (Todas as atividades) do feed de notícias, você pode exibir atualizações de repositórios em que está inscrito e de pessoas que você segue. Essa seção mostra atualizações dos repositórios que você inspeciona ou marca com estrela e dos usuários que você segue.
 
-You'll see updates in your news feed when a user you follow:
-- Stars a repository.
+Atualizações serão exibidas no feed de notícias quando um usuário que você segue:
+- Marcar um repositório com estrelas.
 - Follows another user.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
-- Creates a public repository.{% endif %}
-- Opens an issue or pull request with "help wanted" or "good first issue" label on a repository you're watching.
-- Pushes commits to a repository you watch.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
-- Forks a public repository.{% endif %}
+- Cria um repositório público.{% endif %}
+- Abrir um problema ou uma pull request com a etiqueta "help wanted" ou "good first issue" em um repositório que você está inspecionando.
+- Faz push de commits para um repositório que você inspeciona.{% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %}
+- Bifurca um repositório público.{% endif %}
 
-For more information about starring repositories and following people, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)" and "[Following people](/articles/following-people)."
+Para obter mais informações sobre como atribuir estrelas a repositórios e seguir pessoas, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)" e "[Seguir pessoas](/articles/following-people)".
 
-### Exploring recommended repositories
+### Explorar repositórios recomendados
 
-In the "Explore repositories" section on the right side of your dashboard, you can explore recommended repositories in your communities. Recommendations are based on repositories you've starred or visited, the people you follow, and activity within repositories that you have access to.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+Na seção "Explorar repositórios" no lado direito do painel, é possível explorar repositórios recomendados nas suas comunidades. As recomendações têm por base repositórios que você marcou com uma estrela ou visitou, as pessoas que você segue e a atividade nos repositórios aos quais você tem acesso.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Encontrar maneiras de contribuir com código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %}
 
-### Further reading
+### Leia mais
 
-- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
+- "[Sobre o painel da sua organização](/articles/about-your-organization-dashboard)"
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md
index 561759cd6c..d06a57ffad 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md
@@ -32,7 +32,7 @@ Após alteração do nome de usuário, o {% data variables.product.product_name
 - Os links da web para repositórios existentes continuarão funcionando. Esse processo pode demorar alguns minutos para ser concluído após a alteração.
 - A linha de comando que faz push dos clones do repositório local para as URLs de controle do remote continuarão funcionando.
 
-Se o novo proprietário do seu antigo nome de usuário criar um repositório com o mesmo nome do seu repositório, isso substituirá a entrada de redirecionamento e o seu redirecionamento para de funcionar. Por conta dessa possibilidade, é recomendável atualizar todas as URLs existentes do repositório remote após alteração do seu nome de usuário. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Se o novo proprietário do seu antigo nome de usuário criar um repositório com o mesmo nome do seu repositório, isso substituirá a entrada de redirecionamento e o seu redirecionamento para de funcionar. Por conta dessa possibilidade, é recomendável atualizar todas as URLs existentes do repositório remote após alteração do seu nome de usuário. Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
 ### Links para a página de perfil anterior
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index 1943015e1a..aa29ee8a2d 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. Se desejar adicionar um novo endereço de e-mail para definir como endereço de e-mail principal, em "Add email address" (Adicionar endereço de e-mail), digite um novo endereço de e-mail e clique em **Add** (Adicionar). ![Botão para adicionar outro endereço de e-mail](/assets/images/help/settings/add_another_email_address.png)
 4. Em "Primary email address" (Endereço de e-mail principal), use o menu suspenso para clicar no endereço de e-mail que deseja definir como endereço de e-mail principal e clique em **Save** (Salvar). ![Botão para definir como principal](/assets/images/help/settings/set_as_primary_email.png)
 5. Para remover o endereço de e-mail antigo da sua conta, ao lado do e-mail antigo, clique em
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}.
 {% if currentVersion == "free-pro-team@latest" %}
 6. Verifique o novo endereço de e-mail principal. Sem um endereço de e-mail verificado, você não será conseguirá usar todos os
 recursos de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)".
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md
index 0918bd2b6b..ca5e578562 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up and managing your GitHub user account
-shortTitle: User accounts
+title: Configurar e gerenciar sua conta de usuário do GitHub
+shortTitle: Contas de usuário
 redirect_from:
   - /categories/setting-up-and-managing-your-github-user-account
 versions:
@@ -12,7 +12,7 @@ topics:
 ---
 
 
-### Table of Contents
+### Índice
 
 {% topic_link_in_list /managing-user-account-settings %}
     {% link_in_list /about-your-personal-dashboard %}
@@ -25,7 +25,7 @@ topics:
     {% link_in_list /permission-levels-for-user-owned-project-boards %}
     {% link_in_list /managing-the-default-branch-name-for-your-repositories %}
     {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %}
-    {% link_in_list /managing-access-to-your-user-accounts-project-boards %}    
+    {% link_in_list /managing-access-to-your-user-accounts-project-boards %}
     {% link_in_list /integrating-jira-with-your-personal-projects %}
     {% link_in_list /best-practices-for-leaving-your-company %}
     {% link_in_list /what-does-the-available-for-hire-checkbox-do %}
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index 2216f3de2a..dad54731ce 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -1,23 +1,20 @@
 ---
 title: Gerenciar as configurações de temas
-intro: 'Você pode gerenciar como {% data variables.product.product_name %} se parece com você definindo uma preferência de um tema que segue as configurações do sistema ou sempre usa o modo claro ou escuro.'
+intro: 'Você pode gerenciar como {% data variables.product.product_name %} se parece com você definindo uma preferência de tema que segue as configurações do seu sistema ou sempre usa um modo claro ou escuro.'
 versions:
   free-pro-team: '*'
 topics:
   - Accounts
 ---
 
-{% note %}
-
-**Observação:** As configurações do tema estão atualmente em fase beta e sujeitas a alterações.
-
-{% endnote %}
-
-Por escolha e flexibilidade sobre como e quando você usa {% data variables.product.product_name %}, você pode configurar configurações de tema para mudar como {% data variables.product.product_name %} fica para você. Você pode escolher dois temas, claro e escuro, ou você pode configurar {% data variables.product.product_name %} para seguir as configurações do seu sistema. Alguns desenvolvedores usam tema escuro para preferências pessoais, para reduzir o consumo de energia em certos dispositivos ou para reduzir o cansaço da vista em condições de pouco brilho.
+Por escolha e flexibilidade sobre como e quando você usa {% data variables.product.product_name %}, você pode configurar configurações de tema para mudar como {% data variables.product.product_name %} fica para você. Você pode escolher entre temas claros e escuros ou você pode configurar {% data variables.product.product_name %} para seguir as configurações do seu sistema. Você pode querer usar um tema escuro para reduzir o consumo de energia em certos dispositivos, reduzir o cansaço da vista em condições com pouca luz, ou porque você prefere o tema.
 
 {% data reusables.user_settings.access_settings %}
 1. Na barra lateral de configurações do usuário, clique em **Aparência**. ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png)
-1. Em "Tema", selecione uma preferência de tema. ![Botões de opção para configurações de tema](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. Em "Modo do tema", selecione o menu suspenso e clique em uma preferência de tema. ![Menu suspenso em "Modo tema" para seleção de preferência de tema](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Clique no tema que deseja usar.
+    - Se você escolheu um único tema, clique em um tema. ![Botões de opção para escolher um único tema](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - Se você escolheu seguir as configurações do sistema, clique em um tema diurno e um tema noturno. ![Botões para a escolha de um tema para sincronizar com a configuração do sistema](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index 6548584b87..6ffd249bf3 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ Apesar de as bifurcações de repositórios privados serem excluídas quando um
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. À direita do colaborador que deseja remover, clique em
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
   ![Botão para remover o colaborador](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. Na barra lateral esquerda, clique em **Collaborators & teams** (Colaboradores e equipes). ![Guia Collaborators (Colaboradores)](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md
index fbec96a5ca..49e8f9cc2e 100644
--- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md
+++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Setting a backup email address
-intro: 'Use a backup email address as an additional destination for security-relevant account notifications{% if currentVersion != "github-ae@latest" %} and to securely reset your password if you can no longer access your primary email address{% endif %}.'
+title: Configurar endereço de e-mail de backup
+intro: 'Use um endereço de e-mail de backup como um destino adicional para notificações de conta relevantes para segurança{% if currentVersion != "github-ae@latest" %} e para redefinir sua senha de forma segura, se não puder mais acessar seu endereço de e-mail principal{% endif %}.'
 redirect_from:
   - /articles/setting-a-backup-email-address
 versions:
@@ -14,11 +14,10 @@ topics:
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.emails %}
-3. Under "Backup email address," select the address you want to set as your backup email address using the drop-down menu.
-![Backup email address](/assets/images/help/settings/backup-email-address.png)
-4. Click **Save**.
+3. Em "Backup email address" (Endereço de e-mail de backup), selecione o endereço que deseja configurar como endereço de e-mail de backup usando o menu suspenso. ![Endereço de e-mail de backup](/assets/images/help/settings/backup-email-address.png)
+4. Clique em **Salvar**.
 
-### Further reading
+### Leia mais
 
-- "[Managing email preferences](/articles/managing-email-preferences/)"
-- "[Updating your GitHub access credentials](/articles/updating-your-github-access-credentials/)"
+- "[Gerenciar preferências de e-mail](/articles/managing-email-preferences/)"
+- "[Atualizar credenciais de acesso do GitHub](/articles/updating-your-github-access-credentials/)"
diff --git a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md
index f1a5112c7b..c4e043985f 100644
--- a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md
+++ b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md
@@ -7,7 +7,7 @@ topics:
   - Legal
 ---
 
-Version Effective Date: February 22, 2021
+Entrada em vigor desta versão: 22 de fevereiro de 2021
 
 Quando você cria uma Conta, tem acesso a vários recursos e produtos diferentes que fazem parte do Serviço. Como muitos desses recursos e produtos oferecem diferentes funcionalidades, eles podem exigir termos e condições adicionais específicos para esse recurso ou produto. Abaixo, listamos esses recursos e produtos, juntamente com os termos adicionais correspondentes que se aplicam ao uso deles.
 
@@ -44,14 +44,14 @@ Se você ativar o Git Large File Storage ("Git LFS") em sua Conta, poderá busca
 
 Cada Conta vem com acesso a [serviços de hospedagem estática do GitHub Pages](/github/working-with-github-pages/about-github-pages). Este serviço de hospedagem destina-se a hospedar páginas da web estáticas para todos os Usuários, mas principalmente, como uma vitrine para projetos pessoais e organizacionais.
 
-GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Alguns esforços de monetização são permitidos no Pages, como botões de doação e links para crowdfunding.
+O GitHub Pages não foi projetado e nem tem permissão para ser usado como um serviço de hospedagem gratuita na web, capaz de administrar sua empresa online, seu site de comércio eletrônico ou qualquer outro site desenvolvido principalmente para facilitar transações comerciais ou fornecer software comercial como um serviço (SaaS). Alguns esforços de monetização são permitidos no Pages, como botões de doação e links para crowdfunding.
 
-#### a. Bandwidth and Usage Limits
-GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Consulte nossas [diretrizes do GitHub Pages](/github/working-with-github-pages/about-github-pages) para obter mais informações.
+#### a. Banda larga e limites de uso
+O GitHub Pages está sujeito a limites específicos de uso e largura de banda e pode não ser apropriado para alguns usos elevados de banda larga. Consulte nossas [diretrizes do GitHub Pages](/github/working-with-github-pages/about-github-pages) para obter mais informações.
 
-#### b. Prohibited Uses
-Prohibited uses of GitHub Pages include
-- Content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service), [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies) or [Community Guidelines](/github/site-policy/github-community-guidelines)
+#### b. Uso proibido
+O uso proibido do GitHub Pages inclui
+- Conteúdo ou atividade ilegal ou proibido pelos nossos [Termos de Serviço](/github/site-policy/github-terms-of-service), [Políticas de uso aceitáveis](/github/site-policy/github-acceptable-use-policies) ou [Diretrizes da comunidade](/github/site-policy/github-community-guidelines)
 - Atividade ou conteúdo violento ou ameaçador
 - Excesso de atividade automatizada em massa (spam, por exemplo)
 - Atividade que comprometa serviços ou usuários do GitHub
@@ -59,7 +59,7 @@ Prohibited uses of GitHub Pages include
 - Conteúdo sexual obsceno
 - Conteúdo que deturpe sua identidade ou a finalidade do site
 
-If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://premium.githubsupport.com/). O GitHub se reserva o direito de recuperar qualquer subdomínio GitHub sem responsabilidade.
+Em caso de dúvidas sobre se o seu uso ou a intenção se enquadra nestas categorias, entre em contato com o [Suporte do GitHub](https://support.github.com/contact) ou com o [Suporte Premium do GitHub](https://premium.githubsupport.com/). O GitHub se reserva o direito de recuperar qualquer subdomínio GitHub sem responsabilidade.
 
 ### 5. Ações e Pacotes
 
diff --git a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md
index f8532ec779..029b872cd4 100644
--- a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md
+++ b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md
@@ -78,7 +78,7 @@ Se o GitHub determinar que um usuário ou cliente está localizado em uma regiã
 
 #### Como as contas da organização são impactadas?
 
-If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. government, or if the organization otherwise appears to be subject to U.S. sanções econômicas e, posteriormente, a conta de organização e a conta de proprietário afiliado serão restritas.
+If an organization is based out of, or the key individuals or membership of an organization shows sufficient ties to, a sanctioned territory or country for which GitHub does not yet have a license from the U.S. governo, ou se a organização, de outra forma, parece estar sujeita aos EUA. sanções econômicas e, posteriormente, a conta de organização e a conta de proprietário afiliado serão restritas.
 
 A restrição suspende o acesso a serviços de repositório privados e serviços pagos, como disponibilidade de repositórios privados gratuitos ou pagos, gists secretas, minutos de Ação pagos, Sponsors (patrocinadores) e serviços do GitHub Marketplace. Para contas organizacionais pagas associadas a regiões sancionadas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas em tais regiões sancionadas, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados gratuitos.
 
@@ -90,19 +90,19 @@ Os usuários de contas individuais gratuitas podem tornar repositórios privados
 
 Infelizmente, a nossa interpretação da lei não nos dá a opção de permitir downloads ou exclusão de conteúdo de repositórios privados até que seja autorizado de outra forma pelo governo dos EUA. governo. Defenderemos energicamente com os EUA. Defenderemos, fortemente, junto dos órgãos reguladores dos EUA, o direito de usuários restritos à negociação protegerem o conteúdo de seus repositórios privados. Também defenderemos uma maior disponibilidade de serviços do GitHub para desenvolvedores em mercados sancionados, e reforçaremos ainda mais a importância da colaboração de códigos no apoio a comunicações pessoais para desenvolvedores em todo o mundo.
 
-#### Under the license GitHub has received from OFAC, which types of accounts will be available in Iran?
+#### Sob a licença que o GitHub recebeu do OFAC, que tipos de contas estarão disponíveis no Irã?
 
-The license we have secured includes all public and private services, for individuals and organizations, both free and paid.
+A licença que garantimos inclui todos os serviços públicos e privados, indivíduos e organizações, tanto grátis como pagos.
 
-For example, a developer in Iran may sign up for a Free or Pro plan for their individual use, and an Iranian university may set up an organization account to collaborate with students.
+Por exemplo, um desenvolvedor no Irã pode inscrever-se em um plano grátis ou Pro para seu uso individual, e uma universidade iraniana pode criar uma conta de organização para colaborar com os estudantes.
 
-Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA and other applicable law, and certain government officials may be restricted from accessing or using GitHub.
+Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA e outras leis aplicáveis, e certos funcionários do governo, podem ter restrições para acessar ou usar o GitHub.
 
-If GitHub determines that an individual or organization falls into a restricted category (SDNs, other blocked parties, or certain government officials), their account will be flagged and they will not be able to use any GitHub features. If they believe that they have been flagged in error, then they have the opportunity to appeal the flag by providing verification information to GitHub using our [individual account appeals request form or organization account appeals request form](https://airtable.com/shrGBcceazKIoz6pY). If GitHub receives sufficient information to verify that the individual is not in a category restricted by U.S. sanções econômicas. Portanto, o sinalizador será removido.
+Se o GitHub determinar que um indivíduo ou organização pertence a uma categoria restrita (SDNs, outros grupos bloqueados. ou certos funcionários do governo), a conta deles será sinalizada e eles não poderão usar nenhuma funcionalidade do GitHub. Se acharem que foram marcados por engano, eles terão a oportunidade de recorrer, fornecendo informações de verificação ao GitHub usando o nosso[formulário de solicitação de reivindicação de conta individual ou formulário de solicitação de reivindicação de conta de organização](https://airtable.com/shrGBcceazKIoz6pY). Se o GitHub recebe informações suficientes para verificar se o indivíduo não está em categoria restrita pelos EUA. sanções econômicas. Portanto, o sinalizador será removido.
 
-#### Will Iranian GitHub users be able to use paid services under the license?
+#### Os usuários iranianos do GitHub poderão utilizar os serviços pagos sob a licença?
 
-Pursuant to the license we have received from OFAC, we are restoring all cloud services to Iranian users, including paid services. Aceitamos todos os principais cartões de crédito, mas terceiros processam pagamentos para nós. Portanto, os pagamentos estão sujeitos aos termos e condições de nossos processadores de pagamento. Those third parties may include restrictions that block payments from Iran.
+Em conformidade com a licença que recebemos do OFAC, estamos restaurando todos os serviços em nuvem para usuários iranianos, incluindo serviços pagos. Aceitamos todos os principais cartões de crédito, mas terceiros processam pagamentos para nós. Portanto, os pagamentos estão sujeitos aos termos e condições de nossos processadores de pagamento. Those third parties may include restrictions that block payments from Iran.
 
 #### Can you clarify availability of GitHub to Cuban developers?
 
diff --git a/translations/pt-BR/content/github/site-policy/github-candidate-privacy-policy.md b/translations/pt-BR/content/github/site-policy/github-candidate-privacy-policy.md
index 5a3e3389a1..bd03c7de56 100644
--- a/translations/pt-BR/content/github/site-policy/github-candidate-privacy-policy.md
+++ b/translations/pt-BR/content/github/site-policy/github-candidate-privacy-policy.md
@@ -27,7 +27,7 @@ As informações pessoais do candidato que coletamos, usamos e mantemos (ou "pro
 
 **Identificadores nacionais**, como o status da sua cidadania, residência e status de permissão de trabalho.
 
-**Employment and education history**, such as your resume or CV, cover letter, details of how you heard about the position you are applying for, information about any previous employment at GitHub or affiliates of GitHub, or other information you provide to us in support of an application and/or the application and recruitment process.
+**Histórico de trabalho e escolar**, como seu currículo ou CV, carta de apresentação, informações sobre como você ouviu sobre a vaga à qual você está se candidatando, informações sobre qualquer trabalho anterior no GitHub ou afiliados do GitHub, ou outras informações que nos fornecem como suporte a uma candidatura e/ou processo de recrutamento.
 
 **Professional or employment information**, including your desired salary or terms related to benefits, willingness to relocate, other job preferences, interview details, reference information and/or information received from background checks (where applicable), and information from publicly available resources (such as your LinkedIn profile or website).
 
diff --git a/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md
index 7beb16cd19..7acfbc2ec4 100644
--- a/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,6 +9,8 @@ topics:
   - Legal
 ---
 
+_These terms apply to 1) GitHub.com (non-Enterprise) customers who have accepted the Corporate Terms of Service, and 2) Enterprise customers who licensed the Service prior to January 4, 2021. Enterprise customers who purchase Products or Services after that date are directed to https://github.com/enterprise-legal for current terms._
+
 OBRIGADO POR ESCOLHER O GITHUB PARA AS NECESSIDADES COMERCIAIS DE SUA EMPRESA. LEIA ESTES TERMOS ATENTAMENTE, POIS ELES REGEM O USO DOS PRODUTOS (CONFORME DEFINIDO ABAIXO), A MENOS QUE O GITHUB TENHA FIRMADO COM VOCÊ UM CONTRATO A PARTE, POR ESCRITO, COM ESSE OBJETIVO. AO CLICAR NO BOTÃO "CONCORDO" OU SEMELHANTE OU ACESSAR OS PRODUTOS, O CLIENTE ACEITA TODOS OS TERMOS E CONDIÇÕES DESTE CONTRATO. SE VOCÊ ESTIVER CELEBRANDO ESTE CONTRATO EM NOME DE UMA EMPRESA OU OUTRA ENTIDADE JURÍDICA, O CLIENTE DECLARA QUE TEM OS PODERES LEGAIS DE VINCULAR A EMPRESA OU OUTRA ENTIDADE JURÍDICA A ESTE CONTRATO.
 
 ### Termos de Serviço Corporativos do GitHub
@@ -24,7 +26,7 @@ Este Contrato aplica-se às seguintes ofertas do GitHub, conforme definido a seg
 
 **"Afiliada"** significa qualquer entidade que controle direta ou indiretamente, ou que seja controlada por ou que esteja sob controle comum de uma parte, no qual "controle" signifique possuir mais de cinquenta por cento (50%) da propriedade ou o direito de conduzir a administração da entidade.
 
-**"Contrato"** significa, coletivamente, todos os termos, condições, avisos contidos ou referenciados neste documento e todas as outras regras de funcionamento, políticas e procedimentos que o GitHub possa publicar em algum momento no Serviço. As políticas de site do GitHub estão disponíveis em [https://docs.github.com/categories/site-policy](/categories/site-policy).
+**"Contrato"** significa, coletivamente, todos os termos, condições, avisos contidos ou referenciados neste documento e todas as outras regras de funcionamento, políticas e procedimentos que o GitHub possa publicar em algum momento no Serviço. GitHub's site policies are available at [https://docs.github.com/categories/site-policy](/categories/site-policy).
 
 **"Todos os usuários"** significa, coletivamente, Usuários e Usuários externos do Cliente que utilizam o Serviço.
 
@@ -111,7 +113,7 @@ O Cliente é responsável por: (i) todo o Conteúdo publicado e a atividade que
 Em algumas situações, os termos de terceiros podem ser aplicados ao uso do GitHub pelo Cliente.  Por exemplo, o Cliente pode ser integrante de uma Organização com seus próprios termos ou contratos de licença. O cliente poderá baixar um aplicativo que se integra ao Serviço ou utilizar o Serviço para autenticar em outro serviço. Embora este Contrato seja o acordo completo do GitHub com o Cliente, os termos de outras partes regem as relações delas com o Cliente.
 
 #### 5. EUA Termos do Governo Federal
-Se o cliente é dos EUA. Se o Cliente for uma entidade do governo dos EUA ou que acessa ou usa o Serviço em instalações governamentais, a [Emenda do Governo Federal dos EUA](https://help.github.com/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) se aplicará e o Cliente concorda com as disposições dela. Aplica-se a alteração do Governo Federal</a> e o Cliente concorda com suas disposições.
+Se o cliente é dos EUA. government entity or otherwise accessing or using the Service in a government capacity, the [U.S. Aplica-se a alteração do Governo Federal](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) e o Cliente concorda com suas disposições.
 
 #### 6. Acordo de Nível de Serviço de Nuvem Empresarial
 O compromisso trimestral de tempo de atividade do GitHub para o GitHub Enterprise Cloud é fornecido no [Contrato de Nível de Serviço Empresarial](/github/site-policy/github-enterprise-service-level-agreement). Se o cliente inscreveu-se no GitHub Enterprise Cloud, ele terá direito a um crédito de serviço se o GitHub não atender ao seu nível de serviço.
diff --git a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
index 8c94bfb559..f40e49caf6 100644
--- a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
+++ b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Data Protection Agreement (Non-Enterprise Customers)
+title: Contrato de Proteção de Dados do GitHub (Clientes não corporativos)
 redirect_from:
   - /github/site-policy/github-data-protection-addendum
   - /github/site-policy-deprecated/github-data-protection-addendum
@@ -7,11 +7,11 @@ versions:
   free-pro-team: '*'
 ---
 
-_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._
+_Esses termos aplicam-se a clientes não corporativos. Elas também se aplicam aos clientes corporativos que licenciaram as ofertas do GitHub antes de 4 de janeiro de 2021. Os clientes corporativos que compraram as ofertas do GitHub após essa data serão direcionados para https://www.github.com/enterprise-legal para os termos atuais._
 
 ## INTRODUÇÃO
 
-The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products.
+As partes concordam que o Contrato de Proteção de Dados do GitHub (clientes não corporativos) (**“DPA”**) define suas obrigações no que diz respeito ao processamento dos Dados Pessoais do Cliente em relação ao serviço hospedado pelo GitHub Enterprise Cloud (o **“Serviço”**). O GitHub assume compromissos neste DPA perante todos os clientes não corporativos que usam o Serviço. Termos separados, incluindo diferentes termos de privacidade, regem o uso do cliente de produtos que não são do GitHub.
 
 Na hipótese de qualquer conflito ou inconsistência entre o DPA e quaisquer outros termos nos acordos do Cliente com o GitHub, prevalecerá o DPA. As provisões do DPA substituem quaisquer disposições conflitantes da Declaração de Privacidade do GitHub que, de outra forma, possam aplicar-se ao processamento de Dados Pessoais do Cliente definidos no presente documento. Para clareza, consistente com a Cláusula 10 das Cláusulas Contratuais Padrão no Anexo 1, as Cláusulas Contratuais Padrão prevalecem sobre quaisquer outros termos no DPA.
 
@@ -90,7 +90,7 @@ e.  *As obrigações e os direitos do Cliente* estão previstos no Contrato e ne
 Levando em consideração o que há de mais moderno, os custos de implementação e a natureza, o escopo, o contexto e as finalidades do processamento, bem como o risco de probabilidade e gravidade variadas para direitos e liberdades fundamentais das pessoas físicas, o GitHub implementará medidas técnicas e organizacionais para garantir um nível de segurança adequado contra os riscos (como destruição acidental ou ilegal, perda, alteração, divulgação ou acesso não autorizado) que se apresentam ao processar Dados Protegidos. O GitHub monitorará regularmente o cumprimento dessas medidas e continuará a tomar as providências apropriadas ao longo da vigência do Contrato.
 
 #### 4.2 - Resposta de incidente e notificação de violação.
-GitHub will comply with Applicable Data Protection Laws.
+O GitHub cumprirá as leis de proteção de dados aplicáveis.
 
 #### 4.3 Equipe do GitHub.
 O GitHub declara e garante que tomará medidas razoáveis para assegurar que todos os funcionários do GitHub que processam Dados protegidos tenham concordado em manter a confidencialidade dos Dados Protegidos e recebido treinamento adequado sobre o cumprimento deste Adendo e das Leis de Proteção de Dados aplicáveis.
@@ -326,7 +326,7 @@ Exportador de dados: Cliente é o exportador de dados.
 
 No entanto, uma vez que o importador de dados fornece serviços de armazenamento e não controla as categorias de dados que armazena, o exportador de dados pode optar por transferir as categorias especiais de dados. Consequentemente, o exportador de dados é o único responsável por assegurar que cumpre todas as obrigações impostas por leis e regulamentos aplicáveis relativos à coleta e processamento de quaisquer categorias especiais de dados, incluindo a obtenção do consentimento explícito dos dados sujeitos antes de processar dados pessoais confidenciais.
 
-**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontratados: de acordo com o DPA, o importador de dados pode contratar outras empresas para prestar serviços limitados em nome do importador de dados, tais como fornecer suporte ao cliente. Esses subcontratantes terão a permissão de obter Dados Pessoais do Cliente apenas para fornecer os serviços que o importador de dados os manteve para fornecer, e são proibidos de usar os Dados Pessoais do Cliente para qualquer outra finalidade.
+**Processamento de operações:** Os dados pessoais transferidos estarão sujeitos às seguintes atividades básicas de processamento: O GitHub usa dados pessoais para fins limitados definidos na Declaração de Privacidade do GitHub, disponível em [https://docs. ithub.com/articles/github-privacy-statement](/articles/github-privacy-statement), e a seção "Processamento de Dados" da DPA. Subcontratados: de acordo com o DPA, o importador de dados pode contratar outras empresas para prestar serviços limitados em nome do importador de dados, tais como fornecer suporte ao cliente. Esses subcontratantes terão a permissão de obter Dados Pessoais do Cliente apenas para fornecer os serviços que o importador de dados os manteve para fornecer, e são proibidos de usar os Dados Pessoais do Cliente para qualquer outra finalidade.
 
 ### Apêndice 2 das Cláusulas Contratuais Padrão
 Descrição das medidas de segurança técnicas e organizacionais implementadas pelo importador de dados, de acordo com as Cláusulas 4(d) e 5(c):
diff --git a/translations/pt-BR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/pt-BR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
index 77bd5e1d8a..ee796249e0 100644
--- a/translations/pt-BR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
+++ b/translations/pt-BR/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
@@ -1,7 +1,6 @@
 ---
 title: O GitHub Insights e a proteção de dados para sua organização
 intro: '{% data variables.product.prodname_insights %} analisa seus dados {% data variables.product.prodname_ghe_server %}. Esses dados podem incluir dados pessoais de indivíduos em sua organização que podem ter o direito de entender como esses dados pessoais estão sendo usados.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
   - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
@@ -14,8 +13,6 @@ topics:
   - Legal
 ---
 
-Para obter mais informações sobre os termos que regem {% data variables.product.prodname_insights %}, consulte o seu contrato de assinatura do {% data variables.product.prodname_ghe_one %}.
-
 Para evitar dúvidas, nenhuma das informações acima devem ser consideradas aconselhamento legal fornecido por {% data variables.product.prodname_dotcom %}. Você é responsável por proteger sua própria análise legal das informações fornecidas neste documento e pelo seu cumprimento das leis de privacidade e proteção de dados. Fica a seu critério exclusivo usar {% data variables.product.prodname_insights %} para processar os dados dos seus funcionários e usuários e, se você fizer isso, você é o único responsável por realizar esse processamento em conformidade com a lei aplicável.
 
 ### Funções e responsabilidades da organização
diff --git a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md
index 07b6af8cc2..bb594dc456 100644
--- a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md
+++ b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md
@@ -64,7 +64,7 @@ Solicitaremos algumas informações básicas no momento de criação da conta. Q
 ##### Informações de pagamento
 Se você fizer um registro de Conta paga conosco, enviar fundos pelo Programa de Patrocinadores do GitHub ou comprar um aplicativo no GitHub Marketplace, coletaremos seu nome completo, endereço e informações do PayPal ou do cartão de crédito. Observe que o GitHub não processa ou armazena suas informações de cartão de crédito ou do PayPal, mas nosso processador de pagamento de terceiros o fará.
 
-Se você listar e vender um aplicativo no [GitHub Marketplace](https://github.com/marketplace), precisaremos das suas informações bancárias. Se você angariar fundos pelo [Programa de Patrocinadores do GitHub](https://github.com/sponsors), solicitaremos algumas [informações adicionais](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) no processo de registro para você participar e receber fundos através desses serviços e para fins de compliance.
+Se você listar e vender um aplicativo no [GitHub Marketplace](https://github.com/marketplace), precisaremos das suas informações bancárias. Se você angariar fundos pelo [Programa de Patrocinadores do GitHub](https://github.com/sponsors), solicitaremos algumas [informações adicionais](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) no processo de registro para você participar e receber fundos por esses serviços e para fins de conformidade.
 
 ##### Informações do perfil
 Você pode optar por nos enviar mais informações para o perfil da sua Conta, como nome completo, avatar com foto, biografia, localidade, empresa e URL para um site de terceiros. Essas informações podem incluir Informações Pessoais de Usuário. Observe que as suas informações de perfil podem ficar visíveis para outros Usuários do nosso Serviço.
diff --git a/translations/pt-BR/content/github/site-policy/github-private-information-removal-policy.md b/translations/pt-BR/content/github/site-policy/github-private-information-removal-policy.md
index 7cf19af66d..3d6bc7ebce 100644
--- a/translations/pt-BR/content/github/site-policy/github-private-information-removal-policy.md
+++ b/translations/pt-BR/content/github/site-policy/github-private-information-removal-policy.md
@@ -28,9 +28,9 @@ Para os fins deste documento, “informações privadas” refere-se ao conteúd
 - Nomes internos do servidor, endereços IP e URLs, por conta própria. Você deve ser capaz de mostrar que o seu uso em um determinado arquivo ou código representa uma ameaça de segurança.
 - Menções simples à identidade da sua empresa, nome, marca, nome de domínio ou outras referências à sua empresa em arquivos no GitHub. Você deve ser ser capaz de explicar a razão pela qual o uso da identidade da empresa é uma ameaça à posição de segurança da empresa.
 - Arquivos ou repositórios inteiros que não representam um risco específico de segurança, mas você acredita que, de qualquer forma, são censuráveis.
-- Solicitações para remover conteúdo que possa infringir seus direitos autorais ou os de sua organização. Se você tiver dúvidas sobre como o GitHub lida com questões relacionadas aos direitos autorais ou gostaria de relatar conteúdos potencialmente infratores, por favor, reveja nossa [Política de Retirada](/articles/dmca-takedown-policy/) DMCA. The private information removal process is generally not intended for the removal of full files or repositories — only for the specific pieces of private information in those files. While there may be cases where files are filled entirely with private information, you must justify the security risk for the removal of such files, and this may increase the time required to process your request.
+- Solicitações para remover conteúdo que possa infringir seus direitos autorais ou os de sua organização. Se você tiver dúvidas sobre como o GitHub lida com questões relacionadas aos direitos autorais ou gostaria de relatar conteúdos potencialmente infratores, por favor, reveja nossa [Política de Retirada](/articles/dmca-takedown-policy/) DMCA. O processo de remoção de informações privadas geralmente não é destinado à remoção de arquivos completos ou repositórios — apenas para as partes específicas de informações privadas nesses arquivos. Embora possa haver casos em que os arquivos são preenchidos inteiramente com informações privadas, você deverá justificar o risco de segurança referente à remoção desses arquivos, e isso poderá aumentar o tempo necessário para processar a sua solicitação.
 - Disputas de marcas registradas. Se você tiver dúvidas sobre como o GitHub lida com as questões relacionadas às marcas registradas ou gostaria de denunciar conteúdo que contenha sua marca comercial ou seus serviços, por favor, revise nossa [Política de Marca Registrada](/articles/github-trademark-policy/).
-- Queixas de privacidade. If you wish to access, transfer, change, or delete your personal information on GitHub, please contact us via [our Privacy contact form](https://github.com/contact/privacy).
+- Queixas de privacidade. Se você deseja acessar, transferir, alterar ou excluir suas informações pessoais no GitHub, entre em contato conosco por meio do [nosso formulário de contato de privacidade](https://github.com/contact/privacy).
 - Conteúdo regido pelas nossas [Diretrizes da Comunidade](/articles/github-community-guidelines/), como malware ou ferramentas de propósito geral. Se você tiver dúvidas sobre nossas Diretrizes da Comunidade ou acredita que o conteúdo no GitHub pode violar nossas diretrizes, você pode usar {% data variables.contact.report_content %} para entrar em contato conosco.
 
 ### Informações que você precisa saber
@@ -39,13 +39,13 @@ Para os fins deste documento, “informações privadas” refere-se ao conteúd
 
 **Sem bots.** Você precisa contar com a avaliação de um profissional treinado a respeito dos fatos de cada solicitação que você envia. Se você estiver terceirizando seus esforços, certifique-se de saber como eles operam, e certifique-se de que eles não estão usando bots automatizados para enviar reclamações em massa. Essas queixas, muitas vezes, incluem dados que não representam quaisquer ameaças à segurança e não incluem explicações suficientes, exigindo idas e vindas de documentos e resultando em atrasos, mesmo quando a reclamação é válida.
 
-**Send In The Correct Request.** As noted above, we offer this private information removal process as an exceptional service only for high-risk content. We are not able to use this process to remove other kinds of content, such as potentially infringing content, and we are not able to process any other kinds of removal requests simultaneously while processing private information removal requests. We will be able to help you more quickly if you send in your private information removal requests separately from any requests to remove potentially infringing content. If you are unsure whether your request involves only private information or also involves other legal matters, please consult legal counsel.
+**Envie a solicitação correta.** Conforme mencionado acima, oferecemos este processo de remoção de informações privadas como um serviço excepcional somente para conteúdo de alto risco. Não podemos usar este processo para remover outros tipos de conteúdo, como conteúdo potencialmente infrator e não conseguimos processar qualquer outro tipo de solicitação de remoção simultaneamente ao pedido de remoção das informações privadas. Nós poderemos ajudar você mais rapidamente se você enviar, nas suas solicitações de remoção de informações privadas separadamente de qualquer solicitação, para remover conteúdo potencialmente infrator. Se você não tem certeza se a sua solicitação envolve apenas informações privadas ou também envolve outras questões jurídicas, solicite aconselhamento jurídico.
 
-**Processing Time.** While we do process private information removal requests as quickly as possible, due to the volume of requests we process, it may take some time for your request to be reviewed. Solicitações adicionais ou vários pedidos de pontos de contatos diferentes podem resultar em atrasos.
+**Tempo de Processamento.** Embora processemos as solicitações de remoção de informações privadas o mais rápido possível, devido ao volume de solicitações que processamos, pode levar algum tempo para que seu pedido seja revisado. Solicitações adicionais ou vários pedidos de pontos de contatos diferentes podem resultar em atrasos.
 
 ### Como realmente funciona?
 
-1. **O requerente deve investigar.** Cabe à parte requerente realizar sua própria investigação e nos fornecer os [detalhes necessários](#your-request-must-include) — e o mais importante: uma explicação de como os dados representam um risco à segurança. GitHub is not in a position to search for or make initial determinations about private information on any individual's or organization's behalf.
+1. **O requerente deve investigar.** Cabe à parte requerente realizar sua própria investigação e nos fornecer os [detalhes necessários](#your-request-must-include) — e o mais importante: uma explicação de como os dados representam um risco à segurança. O GitHub não está em posição de procurar ou fazer determinações iniciais sobre informações privadas em nome de qualquer indivíduo ou organização.
 
 2. **Complainant Sends a Private Information Removal Request.** After conducting an investigation, the complainant prepares and [sends a private information removal request](#sending-a-private-information-removal-request) to GitHub. Se o pedido não for suficientemente detalhado para demonstrar o risco de segurança, e para que o GitHub localize os dados, responderemos e pediremos mais informações.
 
@@ -64,28 +64,28 @@ Para os fins deste documento, “informações privadas” refere-se ao conteúd
 #### O que significa Bifurcação? (ou O que é uma Bifurcação?)
 Um dos melhores recursos do GitHub é a possibilidade de os usuários "bifurcarem" repositórios uns dos outros. O que isso significa? Basicamente, isso significa que os usuários podem fazer uma cópia de um projeto no GitHub em seus próprios repositórios. Conforme a licença ou a lei permitirem, os usuários podem fazer alterações nessa bifurcação para ou fazer push de volta para o projeto principal ou simplesmente manter como sua própria variação de um projeto. Cada uma dessas cópias é uma "[bifurcação](/articles/github-glossary/#fork)" do repositório original que, por sua vez, também pode ser chamado de "principal" da bifurcação.
 
-O GitHub não irá desabilitar bifurcações automaticamente quando desabilitar um repositório principal. Isso porque as bifurcações pertencem a usuários diferentes e podem ter sido alteradas de maneiras significativas. O GitHub não realiza nenhuma investigação independente sobre as bifurcações. We expect those sending private information removal requests to conduct that investigation and, if they believe that the forks also contain private information, expressly include forks in their request.
+O GitHub não irá desabilitar bifurcações automaticamente quando desabilitar um repositório principal. Isso porque as bifurcações pertencem a usuários diferentes e podem ter sido alteradas de maneiras significativas. O GitHub não realiza nenhuma investigação independente sobre as bifurcações. Esperamos que aqueles que enviam solicitações de remoção de informações privadas realizem essa investigação e, se entenderem que as bifurcações também contêm informações privadas, incluam expressamente as bifurcações na sua solicitação.
 
-If at the time that you submitted your notice, you identified all existing forks of that repository, we would process a valid claim against all forks in that network at the time we process the notice. Nós faríamos isso tendo em conta a probabilidade de todas as novas bifurcações criadas conterem o mesmo conteúdo. In addition, if the reported network that contains the reported content is larger than one hundred (100) repositories and thus would be difficult to review in its entirety, we may consider disabling the entire network if you state in your notice that, based on the representative number of forks you have reviewed, you believe that all or most of the forks contain the content reported in the parent repository.
+Se, no momento que você enviou o aviso, você identificou todas as bifurcações existentes desse repositório, nós processaríamos uma reivindicação válida para todas as bifurcações dessa rede no momento em que processamos a notificação. Nós faríamos isso tendo em conta a probabilidade de todas as novas bifurcações criadas conterem o mesmo conteúdo. Além disso, se a rede informada que contém o conteúdo relatado for superior a cem (100) repositórios, o que dificulta revisá-la na sua totalidade, podemos considerar a desabilitação de toda a rede se você declarar na sua notificação que, com base no número representativo de bifurcações revisados, você acredita que todas ou a maioria das bifurcações contêm o conteúdo informado no repositório principal.
 
-### Sending A Private Information Removal Request
+### Enviar uma solicitação de remoção de informações privadas
 
-Devido ao tipo de conteúdo que o GitHub hospeda (principalmente código de software) e a forma como o conteúdo é gerenciado (com o Git), precisamos que as queixas sejam as mais específicas possíveis. In order for us to verify that a user has removed reported private information completely, we need to know exactly where to look.
+Devido ao tipo de conteúdo que o GitHub hospeda (principalmente código de software) e a forma como o conteúdo é gerenciado (com o Git), precisamos que as queixas sejam as mais específicas possíveis. Para que possamos verificar se um usuário removeu informações privadas relatadas completamente, precisamos saber exatamente onde procurar.
 
-These guidelines are designed to make the processing of requests to remove private information as straightforward as possible.
+Estas diretrizes tem o objetivo de simplificar, o máximo possível, o tratamento dos pedidos de remoção das informações privadas.
 
 #### Seu pedido deve incluir:
 
-1. A working, clickable link to each file containing private information. (Note que não podemos trabalhar a partir de resultados de pesquisa, exemplos ou capturas de tela.)
-2. Specific line numbers within each file containing the private information.
+1. Um link funcional e clicável para cada arquivo que contém informações privadas. (Note que não podemos trabalhar a partir de resultados de pesquisa, exemplos ou capturas de tela.)
+2. As linhas específicas dentro de cada arquivo que contém as informações privadas.
 3. Uma breve descrição de como cada item que você identificou representa um risco de segurança para você ou sua organização. ***É importante que você forneça uma explicação de como os dados representam um risco de segurança além de simplesmente afirmar isso.***
 4. Se você é um terceiro atuando como representante de uma organização que enfrenta um risco de segurança, inclua uma declaração de que tem o direito legal de agir em nome dessa organização.
-5. OPCIONAL: informe-nos se o seu pedido é particularmente urgente, e por quê. We respond to all private information removal requests as quickly as possible. No entanto, se esse pedido for especialmente sensível ao tempo, como uma exposição de credenciais muito recente, por favor, explique o porquê.
+5. OPCIONAL: informe-nos se o seu pedido é particularmente urgente, e por quê. Respondemos a todas as solicitações de remoção de informações privadas o mais rápido possível. No entanto, se esse pedido for especialmente sensível ao tempo, como uma exposição de credenciais muito recente, por favor, explique o porquê.
 
 ### Como enviar sua solicitação
 
-You can submit your request to remove private information via our [contact form](https://support.github.com/contact?tags=docs-private-information). Por favor, inclua uma versão simples de texto da sua solicitação no corpo da mensagem. Enviar sua solicitação em um anexo pode resultar em atrasos.
+Você pode enviar a sua solicitação para remover informações privadas por meio do nosso [formulário de contato](https://support.github.com/contact?tags=docs-private-information). Por favor, inclua uma versão simples de texto da sua solicitação no corpo da mensagem. Enviar sua solicitação em um anexo pode resultar em atrasos.
 
 ### Disputas
 
-If you received a private information removal request from us, you can dispute it by replying to our email and letting us know — in as much detail as possible — why you think the content in question is not private information subject to this Policy.
+Se você recebeu a nossa solicitação de remoção de informações privada, você pode contestar respondendo ao nosso e-mail e nos informando — da forma mais detalhada possível —  por que você acha que o conteúdo em questão não é uma informação privada sujeita a esta Política.
diff --git a/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md b/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md
index 3c03388ed1..e47825c005 100644
--- a/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md
+++ b/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md
@@ -121,7 +121,7 @@ Durante a vigência, o GitHub enviará a você todos os Pagamentos para Desenvol
 
 - Para Contas de Desenvolvedor Patrocinado recém-criadas, o GitHub remeterá a você todos os Pagamentos de Desenvolvedor Patrocinado recebidos em um determinado mês dentro de 90 dias após a criação de sua Conta de Desenvolvedor Patrocinado, sujeito às variáveis abaixo. Os pagamentos subsequentes serão novamente enviados no prazo de 30 dias após o encerramento desse mês, de acordo com esta seção.
 
-- If you are paid through Stripe Connect, you will receive payouts on the 22nd of the month for the balance accrued since the last payout, regardless of the amount of the balance. Payout initiation dates vary by country, and can change from month to month due to public holidays, weekends, and other factors.
+- Se você for pago pelo Stripe Connect, você receberá pagamentos no dia 22 de cada mês pelo saldo acumulado desde o último pagamento, independentemente do montante do saldo. As datas de início dos pagamentos variam de país para país e podem mudar de mês para mês, em razão de feriados, fins de semana e outros fatores.
 
 - Se você for receber por meio de transferência ACH ou transferência eletrônica, você receberá pagamentos na terceira quinta-feira do mês. O GitHub emitirá um pagamento para você em qualquer mês que seu saldo atingir US$ 100. Contribuições do Fundo Correspondentes para Patrocinadores do GitHub não contam para esse limite. Se o seu saldo ficar abaixo de US$ 100 no fim do mês, ele será acumulado até que ultrapasse o limite no fim do mês. Se você deixar o GitHub Sponsors, o GitHub emitirá um pagamento a partir do seu saldo restante, mesmo que o saldo esteja abaixo de US$ 100.
 
@@ -141,9 +141,9 @@ Para ser pago, você deverá fornecer as informações financeiras, tributárias
 
 #### 4.8. Stripe Connect
 
-If you are paid through Stripe Connect, the following additional terms apply to your usage of GitHub Sponsors:
+Se você é pago pelo do Stripe Connect, aplicam-se os seguintes termos adicionais ao seu uso do GitHub Sponsors:
 
-**Full service agreement**
+**Contrato de Serviço Completo**
 
 _Applies to Sponsored Developer Accounts registered in Australia, Austria, Belgium, Canada, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Netherlands, New Zealand, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland, United Kingdom, United States._
 
diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index 1a66878f1a..d92b58e261 100644
--- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -1,89 +1,76 @@
 ---
-title: About the dependency graph
-intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.'
+title: Sobre o gráfico de dependências
+intro: 'Informações detalhadas sobre o gráfico de dependência, os ecossistemas que apoia e como determina quais pacotes um repositório depende.'
 versions:
-  free-pro-team: '*'
-  enterprise-server: '*'
+  enterprise-server: <=2.22
+topics:
+  - Repositories
 ---
 
-### Dependency graph availability
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+### Disponibilidade do gráfico de dependências
+
+O gráfico de dependências está disponível para cada repositório que define as dependências em um ecossistema de pacote compatível usando um formato de arquivo compatível.
 
 {% data reusables.repositories.enable-security-alerts %}
 
-### About the dependency graph
+### Sobre o gráfico de dependências
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, ele mostra dependências, ou seja, os ecossistemas e os pacotes do qual depende. O {% data variables.product.prodname_ghe_server %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+Ao fazer push de um commit para {% data variables.product.product_name %} que muda ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch padrão, o gráfico de dependências será atualizado automaticamente. Para obter informações sobre ecossistemas compatíveis e arquivos de manifesto, consulte "[Ecossistemas de pacotes compatíveis](#supported-package-ecosystems)" abaixo.
 
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+### Dependências incluídas
 
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+O gráfico de dependências inclui todas as dependências de um repositório detalhadas nos arquivos de manifesto e de bloqueio ou seu equivalente para ecossistemas compatíveis. Isto inclui:
 
-### Dependencies included
+- Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio
+- Dependências indiretas dessas dependências diretas, também conhecidas como dependências transitórias ou subdependências
 
-The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
+O gráfico de dependências identifica dependências indiretas.
 
-- Direct dependencies, that are explicitly defined in a manifest or lock file
-- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+### Usar o gráfico de dependências
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+Você pode usar o gráfico de dependências para:
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
+- Explore os repositórios dos quais o código depende. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)".
+- Ver e atualizar dependências vulneráveis no seu repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)"
 
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+### Habilitar o gráfico de dependências
 
-### Using the dependency graph
+{% if enterpriseServerVersions contém currentVersion and currentVersion ver_gt "enterprise-server@2. 1" %}Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %}
 
-You can use the dependency graph to:
-
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
-
-### Enabling the dependency graph
-
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
-
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e os alertas de segurança. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+Quando o gráfico de dependências é ativado pela primeira vez, todos manifesto e arquivos de bloqueio para ecossistemas suportados são analisados imediatamente. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Uma vez habilitado, o gráfico é automaticamente atualizado a cada push no repositório.
 
-### Supported package ecosystems
+### Ecossistemas de pacote compatíveis
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+Os formatos recomendados definem explicitamente quais versões são usadas para todas as dependências diretas e indiretas. Se você usar esses formatos, seu gráfico de dependências será mais preciso. Além disso, ele reflete a configuração da compilação atual e permite que o gráfico de dependências relate vulnerabilidades em dependências diretas e indiretas.
 
-| Package manager | Languages | Recommended formats | All supported formats |
-| --- | --- | --- | ---|
-| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| 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.lock`, `setup.py`* |
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+Os ecossistemas listados abaixo são compatíveis com o gráfico de dependências e com {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}os alertas de segurança{% endif %}.
+
+| Gerenciador de pacotes | Idiomas                          | Formatos recomendados                                  | Todos os formatos compatíveis                                             |
+| ---------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
+| Composer               | PHP                              | `composer.lock`                                        | `composer.json`, `composer.lock`                                          |
+| `dotnet` CLI           | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+| 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`*                |
+| RubyGems               | Ruby                             | `Gemfile.lock`                                         | `Gemfile.lock`, `Gemfile`, `*.gemspec`                                    |
+| Yarn                   | JavaScript                       | `yarn.lock`                                            | `package.json`, `yarn.lock`                                               |
 
 {% note %}
 
-**Note:** 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.
+**Observação:** se você listar suas dependências de Python em um arquivo `setup.py`, será provável que não possamos analisar e listar cada dependência no seu projeto.
 
 {% endnote %}
 
-### Further reading
+### Leia mais
 
-- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia
+- "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index a51f8d1afc..070a78060b 100644
--- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -7,29 +7,20 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
 
-O gráfico de dependências mostra as dependências{% if currentVersion == "free-pro-team@latest" %} e dependentes{% endif %} do seu repositório. Para obter informações sobre a detecção de dependências e quais ecossistemas são compatíveis, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
+O gráfico de dependências mostra as dependências do seu repositório. Para obter informações sobre a detecção de dependências e quais ecossistemas são compatíveis, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. Opcionalmente, em "Gráfico de dependência", clique em **Dependentes**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### Vista de dependências
 
-{% if currentVersion == "free-pro-team@latest" %}
-As dependências são agrupadas por ecossistema. Você pode expandir sua dependência para visualizar suas dependências. Para dependências de repositórios públicos hospedados em
-{% data variables.product.product_name %}, você também pode clicar em uma dependência para visualizar o repositório. Dependências de repositórios privados, pacotes privados ou arquivos não reconhecidos são exibidos em texto sem formatação.
-
-Se foram detectadas vulnerabilidades no repositório, estas são exibidas na parte superior da visualização para usuários com acesso ao {% data variables.product.prodname_dependabot_alerts %}.
-
-![Gráfico de dependências](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
 Todas as dependências diretas e indiretas especificadas no manifesto do repositório ou arquivos de bloqueio são listadas e agrupadas pelo ecossistema. Se foram detectadas vulnerabilidades no repositório, estas serão exibidas na parte superior da visualização para usuários com acesso ao
 {% data variables.product.prodname_dependabot_alerts %}.
@@ -57,59 +48,8 @@ Todas as dependências diretas e indiretas especificadas no manifesto do reposit
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### Vista de dependentes
-
-Para repositórios públicos, a vista de dependentes mostra como o repositório é usado por outros repositórios. Para exibir apenas os repositórios que contêm uma biblioteca em um gerente de pacotes, clique em **QUANTIDADE de pacotes** imediatamente acima da lista de repositórios dependentes. A quantidade de dependentes é aproximada e pode nem sempre corresponder aos dependentes listados.
-
-![gráfico de dependentes](/assets/images/help/graphs/dependents_graph.png)
-
-### Habilitar e desabilitar o gráfico de dependências para um repositório privado
-
-Os administradores de repositórios podem habilitar ou desabilitar o gráfico de dependências em repositórios privados.
-
-Você também pode habilitar ou desabilitar o gráfico de dependências 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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)".
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Leia a mensagem sobre a concessão de acesso somente leitura pelo {% data variables.product.product_name %} aos dados do repositório para habilitar o gráfico de dependências e, em seguida, ao lado de "Gráfico de Dependência", clique em **Habilitar**. ![Botão "Habilitar" para o gráfico de dependência](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-Você pode desabilitar o gráfico de dependências a qualquer momento clicando em **Desabilitar** ao lado de "Gráfico de dependência" na aba de análise & de Segurança &.
-
-### Alterar o pacote "Usado por"
-
-Se o gráfico de dependências estiver habilitado e o seu repositório contiver um pacote publicado em um ecossistema de pacote compatível, {% data variables.product.prodname_dotcom %} exibirá uma seção "Usado por" na barra lateral da aba do **Código** do seu repositório. Para obter mais informações sobre os ecossistemas de pacotes compatíveis, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)".
-
-A seção "Usado por" mostra o número de referências públicas ao pacote que foi encontrado, e exibe os avatares de alguns dos proprietários dos projetos dependentes.
-
-![Seção da barra lateral "Usado por"](/assets/images/help/repository/used-by-section.png)
-
-Clicar em qualquer item desta seção irá levar você para a aba **Dependentes** do gráfico de dependências.
-
-A seção "Usado por" representa um único pacote do repositório. Se você tiver permissões de administrador em um repositório que contém vários pacotes, você poderá escolher qual pacote a seção "Usado por" representa.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Em "Configure as funcionalidades de segurança e análise", clique no menu suspenso na seção "Usados pelo contador" e escolha um pacote. ![Escolha um pacote "Usado por"](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### Solução de problemas para o gráfico de dependências
 
 Se seu gráfico de dependências estiver vazio, poderá haver um problema com o arquivo que contém suas dependências. Selecione o arquivo para garantir que ele esteja corretamente formatado para o tipo de arquivo.
 
-{% if currentVersion == "free-pro-team@latest" %}
-Se o arquivo estiver formatado corretamente, verifique o seu tamanho. O gráfico de dependências ignora manifesto individual e arquivos de bloqueio com tamanho superior a 0,5 Mb, a menos que você seja um
-usuário de {% data variables.product.prodname_enterprise %}. Ele processa até 20 arquivos de manifesto ou de bloqueio por repositório por padrão; logo você pode dividir dependências em arquivos menores em subdiretórios do repositório.{% endif %}
-
 Se um arquivo de manifesto ou de bloqueio não for processado, suas dependências serão omitidas no gráfico de dependências e não será possível verificar se há dependências.
-
-### Leia mais
-
-- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/github/understanding-how-github-uses-and-protects-your-data)"
-{% endif %}
diff --git a/translations/pt-BR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/pt-BR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index d2cf6de648..62e067a42c 100644
--- a/translations/pt-BR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: Sobre o suporte Premium do GitHub para o GitHub Enterprise Cloud
-intro: 'O {% data variables.contact.premium_support %} é uma oferta de suporte complementar paga para clientes do {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_one %}.'
+intro: 'O {% data variables.contact.premium_support %} é uma oferta de suporte complementar paga para clientes do {% data variables.product.prodname_ghe_cloud %}.'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
diff --git a/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md b/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md
index 18771bc336..1ce9842364 100644
--- a/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md
+++ b/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md
@@ -11,7 +11,7 @@ topics:
 
 Se a sua conta usa um produto {% data variables.product.prodname_dotcom %} pago, você pode entrar em contato diretamente com {% data variables.contact.github_support %}. Se a sua conta usa {% data variables.product.prodname_free_user %} para contas de usuários e organizações, você pode entrar em contato com {% data variables.contact.contact_support %} para relatar problemas com a conta, de segurança e abusos. Para obter mais informações, consulte "[Sobre GitHub Support](/github/working-with-github-support/about-github-support)".
 
-If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)."
+Se você não tem uma conta corporativa, use {% data variables.contact.enterprise_portal %} para enviar tíquetes. Para obter mais informações sobre contas corporativas, consulte "[Sobre contas corporativas](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)".
 
 ### Enviando um tíquete usando o {% data variables.contact.support_portal %}
 
diff --git a/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md
index e7cab073db..6bd8dc7fa5 100644
--- a/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/pt-BR/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ Para obter mais informações sobre como criar links, consulte "[Sintaxe básica
 
 ### Problemas e pull requests
 
-Nas conversas do {% data variables.product.product_name %}, as referências a problemas e pull request são convertidas automaticamente em links curtos. Para obter mais informações, consulte "[Sobre conversas no {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)".
+Nas conversas do {% data variables.product.product_name %}, as referências a problemas e pull request são convertidas automaticamente em links curtos.
 
 {% note %}
 
diff --git a/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index 4c0e060889..412c0bbb2a 100644
--- a/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/pt-BR/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -1,6 +1,6 @@
 ---
-title: Basic writing and formatting syntax
-intro: Create sophisticated formatting for your prose and code on GitHub with simple syntax.
+title: Sintaxe básica de escrita e formatação no GitHub
+intro: Crie formatação sofisticada para narração e código no GitHub com sintaxe simples.
 redirect_from:
   - /articles/basic-writing-and-formatting-syntax
 versions:
@@ -9,62 +9,62 @@ versions:
   github-ae: '*'
 ---
 
-### Headings
+### Títulos
 
-To create a heading, add one to six `#` symbols before your heading text. The number of `#` you use will determine the size of the heading.
+Para criar um título, adicione de um a seis símbolos `#` antes do texto do título. O número de `#` que você usa determinará o tamanho do título.
 
-```
-# The largest heading
-## The second largest heading
-###### The smallest heading
+```markdown
+# O título maior
+## O segundo maior título
+###### O título menor
 ```
 
-![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png)
+![Títulos H1, H2 e H6 renderizados](/assets/images/help/writing/headings-rendered.png)
 
-### Styling text
+### Estilizar texto
 
-You can indicate emphasis with bold, italic, or strikethrough text.
+Você pode indicar ênfase com texto em negrito, itálico ou riscado em campos de comentários e arquivos de `.md`.
 
-| Style | Syntax | Keyboard shortcut | Example | Output |
-| --- | --- | --- | --- | --- |
-| Bold | `** **` or `__ __` | command/control + b | `**This is bold text**` | **This is bold text** |
-| Italic | `* *` or `_ _` | command/control + i | `*This text is italicized*` | *This text is italicized* |
-| Strikethrough | `~~ ~~` | | `~~This was mistaken text~~` | ~~This was mistaken text~~ |
-| Bold and nested italic | `** **` and `_ _` | | `**This text is _extremely_ important**` | **This text is _extremely_ important** |
-| All bold and italic | `*** ***` | | `***All this text is important***` | ***All this text is important*** |
+| Estilo                     | Sintaxe            | Atalho              | Exemplo                                      | Resultado                                  |
+| -------------------------- | ------------------ | ------------------- | -------------------------------------------- | ------------------------------------------ |
+| Negrito                    | `** **` ou `__ __` | command/control + b | `**Esse texto está em negrito**`             | **Esse texto está em negrito**             |
+| Itálico                    | `* *` ou `_ _`     | command/control + i | `*Esse texto está em itálico*`               | *Esse texto está em itálico*               |
+| Tachado                    | `~~ ~~`            |                     | `~~Esse texto estava errado~~`               | ~~Esse texto estava errado~~               |
+| Negrito e itálico aninhado | `** **` e `_ _`    |                     | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** |
+| Todo em negrito e itálico  | `*** ***`          |                     | `***Todo esse texto é importante***`         | ***Todo esse texto é importante***         |
 
-### Quoting text
+### Citar texto
 
-You can quote text with a `>`.
+Você pode citar texto com um `>`.
 
-```
-In the words of Abraham Lincoln:
+```markdown
+Nas palavras de Abraham Lincoln:
 
 > Pardon my French
 ```
 
-![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png)
+![Texto citado renderizado](/assets/images/help/writing/quoted-text-rendered.png)
 
 {% tip %}
 
-**Tip:** When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing `r`. You can quote an entire comment by clicking {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Quote reply**. For more information about keyboard shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts/)."
+**Dica:** ao exibir uma conversa, você pode citar textos automaticamente em um comentário destacando o texto e digitando `r`. É possível citar um comentário inteiro clicando em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Quote reply** (Resposta à citação). Para obter mais informações sobre atalhos de teclado, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts/)".
 
 {% endtip %}
 
-### Quoting code
+### Citar código
 
-You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.
+Você pode chamar código ou um comando em uma frase com aspas simples. O texto entre as aspas não será formatado.
 
-```
-Use `git status` to list all new or modified files that haven't yet been committed.
+```markdown
+Use 'git status' para listar todos os arquivos novos ou modificados que ainda não receberam commit.
 ```
 
-![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png)
+![Bloco de código inline renderizado](/assets/images/help/writing/inline-code-rendered.png)
 
-To format code or text into its own distinct block, use triple backticks.
+Para formatar código ou texto no próprio bloco distinto, use aspas triplas.
 
 <pre>
-Some basic Git commands are:
+Alguns comandos Git básicos são:
 ```
 git status
 git add
@@ -72,168 +72,172 @@ git commit
 ```
 </pre>
 
-![Rendered code block](/assets/images/help/writing/code-block-rendered.png)
+![Bloco de código renderizado](/assets/images/help/writing/code-block-rendered.png)
 
-For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+Para obter mais informações, consulte "[Criar e destacar blocos de código](/articles/creating-and-highlighting-code-blocks)".
 
 ### Links
 
-You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut `command + k` to create a link.
+Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` e, em seguida, o URL entre parênteses `( )`. Também é possível usar o atalho de teclado `command + k` para criar um link.
 
-`This site was built using [GitHub Pages](https://pages.github.com/).`
+`Este site foi construído usando [GitHub Pages](https://pages.github.com/).`
 
-![Rendered link](/assets/images/help/writing/link-rendered.png)
+![Link renderizado](/assets/images/help/writing/link-rendered.png)
 
 {% tip %}
 
-**Tip:** {% data variables.product.product_name %} automatically creates links when valid URLs are written in a comment. For more information, see "[Autolinked references and URLS](/articles/autolinked-references-and-urls)."
+**Dica:** o {% data variables.product.product_name %} cria links automaticamente quando URLs válidos são escritos em um comentário. Para obter mais informações, consulte "[Referências e URLs vinculados automaticamente](/articles/autolinked-references-and-urls)".
 
 {% endtip %}
 
-### Section links
+### Links de seção
 
 {% data reusables.repositories.section-links %}
 
-### Relative links
+### Links relativos
 
 {% data reusables.repositories.relative-links %}
 
-### Lists
+### Listas
 
-You can make an unordered list by preceding one or more lines of text with `-` or `*`.
+Você pode criar uma lista não ordenada precedendo uma ou mais linhas de texto com `-` ou `*`.
 
-```
+```markdown
 - George Washington
 - John Adams
 - Thomas Jefferson
 ```
 
-![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png)
+![Lista não ordenada renderizada](/assets/images/help/writing/unordered-list-rendered.png)
 
-To order your list, precede each line with a number.
+Para ordenar a lista, coloque um número na frente de cada linha.
 
-```
+```markdown
 1. James Madison
 2. James Monroe
 3. John Quincy Adams
 ```
 
-![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png)
+![Lista ordenada renderizada](/assets/images/help/writing/ordered-list-rendered.png)
 
-#### Nested Lists
+#### Listas aninhadas
 
-You can create a nested list by indenting one or more list items below another item.
+Você pode criar uma lista aninhada recuando um ou mais itens da lista abaixo de outro item.
 
-To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [Atom](https://atom.io/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (`-` or `*`) lies directly below the first character of the text in the item above it.
+Para criar uma lista aninhada usando o editor web do {% data variables.product.product_name %} ou um editor de texto que usa uma fonte monoespaçada, como o [Atom](https://atom.io/), você pode alinhar sua lista visualmente. Digite caracteres de espaço na fonte do item da lista aninhada, até que o caractere de marcador da lista (`-` ou `*`) fique diretamente abaixo do primeiro caractere do texto no item acima dele.
 
-```
-1. First list item
-   - First nested list item
-     - Second nested list item
+```markdown
+1. Primeiro item da lista
+   - Primeiro item de lista aninhado
+     - Segundo item de lista aninhada
 ```
 
-![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png)
+![Lista aninhada com alinhamento destacado](/assets/images/help/writing/nested-list-alignment.png)
 
-![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png)
+![Lista com dois níveis de itens aninhados](/assets/images/help/writing/nested-list-example-1.png)
 
-To create a nested list in the comment editor on {% data variables.product.product_name %}, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item.
+Para criar uma lista aninhada no editor de comentários do {% data variables.product.product_name %}, que não usa uma fonte monoespaçada, você pode observar o item da lista logo acima da lista aninhada e contar o número de caracteres que aparecem antes do conteúdo do item. Em seguida, digite esse número de caracteres de espaço na fonte do item da linha aninhada.
 
-In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100. `) before `First list item`.
+Neste exemplo, você pode adicionar um item de lista aninhada abaixo do item de lista `100. Primeiro item da lista` recuando o item da lista aninhada com no mínimo cinco espaços, uma vez que há cinco caracteres (`100.`) antes de `Primeiro item da lista`.
 
-```
-100. First list item
-     - First nested list item
+```markdown
+100. Primeiro item da lista
+     - Primeiro item da lista aninhada
 ```
 
-![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png)   
+![Lista com um item de lista aninhada](/assets/images/help/writing/nested-list-example-3.png)
 
-You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven spaces (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces.
+Você pode criar vários níveis de listas aninhadas usando o mesmo método. Por exemplo, como o primeiro item da lista aninhada tem sete espaços (`␣␣␣␣␣-␣`) antes do conteúdo da lista aninhada `Primeiro item da lista aninhada`, você precisaria recuar o segundo item da lista aninhada com sete espaços.
 
-```
-100. First list item
-     - First nested list item
-       - Second nested list item
+```markdown
+100. Primeiro item da lista
+     - Primeiro item da lista aninhada
+       - Segundo item da lista aninhada
 ```
 
-![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png)    
+![Lista com dois níveis de itens aninhados](/assets/images/help/writing/nested-list-example-2.png)
 
-For more examples, see the [GitHub Flavored Markdown Spec](https://github.github.com/gfm/#example-265).
+Para obter mais exemplos, consulte a [Especificação de markdown em estilo GitHub](https://github.github.com/gfm/#example-265).
 
-### Task lists
+### Listas de tarefas
 
 {% data reusables.repositories.task-list-markdown %}
 
-If a task list item description begins with a parenthesis, you'll need to escape it with `\`:
+Se a descrição de um item da lista de tarefas começar com parênteses, você precisará usar `\` para escape:
 
-`- [ ] \(Optional) Open a followup issue`
+`- [ ] \(Optional) Abrir um problema de acompanhamento`
 
-For more information, see "[About task lists](/articles/about-task-lists)."
+Para obter mais informações, consulte "[Sobre listas de tarefas](/articles/about-task-lists)".
 
-### Mentioning people and teams
+### Mencionar pessoas e equipes
 
-You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing `@` plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
+Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando `@` mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. Para obter mais informações sobre notificações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}."
 
-`@github/support What do you think about these updates?`
+`@github/suporte O que você acha dessas atualizações?`
 
-![Rendered @mention](/assets/images/help/writing/mention-rendered.png)
+![@menção renderizada](/assets/images/help/writing/mention-rendered.png)
 
-When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "[About teams](/articles/about-teams)."
+Quando você menciona uma equipe principal, os integrantes de suas equipes secundárias também recebem notificações, simplificando a comunicação com vários grupos de pessoas. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)".
 
-Typing an `@` symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation.
+Digitar um símbolo `@` chamará uma lista de pessoas ou equipes em um projeto. A lista é filtrada à medida que você digita. Portanto, assim que você achar o nome da pessoa ou da equipe que está procurando, use as teclas de seta para selecioná-lo e pressione tab ou enter para completar o nome. Para equipes, digite nome da @organização/equipe e todos os integrantes dessa equipe serão inscritos na conversa.
 
-The autocomplete results are restricted to repository collaborators and any other participants on the thread.
+Os resultados do preenchimento automático são restritos aos colaboradores do repositório e qualquer outro participante no thread.
 
-### Referencing issues and pull requests
+### Fazer referências a problemas e pull requests
 
-You can bring up a list of suggested issues and pull requests within the repository by typing `#`. Type the issue or pull request number or title to filter the list, and then press either tab or enter to complete the highlighted result.
+Você pode trazer à tona uma lista de problemas e pull requests sugeridos no repositório digitando `#`. Digite o número ou o título do problema ou da pull request para filtrar a lista e, em seguida, pressione tab ou enter para completar o resultado destacado.
 
-For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)."
+Para obter mais informações, consulte "[Referências e URLs vinculados automaticamente](/articles/autolinked-references-and-urls)".
 
-### Referencing external resources
+### Fazer referência a recursos externos
 
 {% data reusables.repositories.autolink-references %}
 
-### Content attachments
+### Anexos de conteúdo
 
-Some {% data variables.product.prodname_github_app %}s provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} renders the information provided by the app under the URL in the body or comment of an issue or pull request.
+Alguns {% data variables.product.prodname_github_app %}s fornecem informações no {% data variables.product.product_name %} para URLs que são vinculados aos respectivos domínios registrados. O {% data variables.product.product_name %} renderiza as informações fornecidas pelo app sob o URL no texto ou comentário de um problema ou uma pull request.
 
-![Content attachment](/assets/images/help/writing/content-attachment.png)
+![Anexo de conteúdo](/assets/images/github-apps/content_reference_attachment.png)
 
-To see content attachments, you must have a {% data variables.product.prodname_github_app %} that uses the Content Attachments API installed on the repository.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Installing an app in your personal account](/articles/installing-an-app-in-your-personal-account)" and "[Installing an app in your organization](/articles/installing-an-app-in-your-organization)."{% endif %}
+Para ver os anexos de conteúdo, é necessário ter um {% data variables.product.prodname_github_app %} que use a API de anexos de conteúdo instalada no repositório.{% if currentVersion == "free-pro-team@latest" %} Para mais informações, consulte "[Instalar um aplicativo na sua conta pessoal](/articles/installing-an-app-in-your-personal-account)" e "[Instalar um aplicativo na sua organização](/articles/installing-an-app-in-your-organization).{% endif %}
 
-Content attachments will not be displayed for URLs that are part of a markdown link.
+Os anexos de conteúdo não serão exibidos para URLs que fazem parte de um link markdown.
 
-For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."
+Para obter mais informações sobre como compilar um {% data variables.product.prodname_github_app %} que use anexos de conteúdo, consulte "[Usar anexos de conteúdo](/apps/using-content-attachments)".
 
-### Using emoji
+### Fazer upload de ativos
 
-You can add emoji to your writing by typing `:EMOJICODE:`.
+Você pode fazer upload de ativos como imagens, arrastando e soltando, fazendo a seleção a partir de um navegador de arquivos ou colando. É possível fazer o upload de recursos para problemas, pull requests, comentários e arquivos `.md` no seu repositório.
 
-`@octocat :+1: This PR looks great - it's ready to merge! :shipit:`
+### Usar emoji
 
-![Rendered emoji](/assets/images/help/writing/emoji-rendered.png)
+Você pode adicionar emoji à sua escrita digitando `:EMOJICODE:`.
 
-Typing `:` will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result.
+`@octocat :+1: Este PR parece ótimo - está pronto para o merge! :shipit:`
 
-For a full list of available emoji and codes, check out [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com).
+![Emoji renderizado](/assets/images/help/writing/emoji-rendered.png)
 
-### Paragraphs
+Digitar `:` trará à tona uma lista de emojis sugeridos. A lista será filtrada à medida que você digita. Portanto, assim que encontrar o emoji que estava procurando, pressione **Tab** ou **Enter** para completar o resultado destacado.
 
-You can create a new paragraph by leaving a blank line between lines of text.
+Para obter uma lista completa dos emojis e códigos disponíveis, confira [a lista de emojis](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md).
 
-### Ignoring Markdown formatting
+### Parágrafos
 
-You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character.
+Você pode criar um parágrafo deixando uma linha em branco entre as linhas de texto.
 
-`Let's rename \*our-new-project\* to \*our-old-project\*.`
+### Ignorar formatação markdown
 
-![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png)
+Para informar ao {% data variables.product.product_name %} que deve ignorar a formatação markdown (ou usar escape nela), anteceda o caractere markdown com `\`.
 
-For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
+`Vamos renomear \*our-new-project\* para \*our-old-project\*.`
 
-### Further reading
+![Caractere com escape renderizado](/assets/images/help/writing/escaped-character-rendered.png)
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)"
-- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
-- "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/)"
+Para obter mais informações, consulte "[Sintaxe markdown](https://daringfireball.net/projects/markdown/syntax#backslash)" de Daring Fireball.
+
+### Leia mais
+
+- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/)
+- "[Sobre escrita e formatação no GitHub](/articles/about-writing-and-formatting-on-github)"
+- "[Trabalhar com formatação avançada](/articles/working-with-advanced-formatting)"
+- "[Dominar o markdown](https://guides.github.com/features/mastering-markdown/)"
diff --git a/translations/pt-BR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/pt-BR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index 7e4c0359c5..ab69786ce5 100644
--- a/translations/pt-BR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/pt-BR/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### Realce de sintaxe
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 Você pode adicionar um identificador de linguagem opcional para habilitar o realce de sintaxe no bloco de código isolado.
 
diff --git a/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 0cc6d841f1..4e05092f16 100644
--- a/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ Campos de tipo de retorno:
 
 ## Pesquisar
 
-A discussão pode ser retornada do campo de `pesquisa` de alto nível. Para pesquisar uma discussão, especifique o `tipo` como `DSCUSSÃO`. O tipo `SearchResultItemConnection` tem um campo `discussionCount` para relatar o número de discussões retornadas, e o tipo `Discussão` é adicionado à união DE `SearchResultItem`. Para obter mais informações, consulte ["Consultas](/graphql/reference/queries#searchresultitemconnection)".
+A discussão pode ser retornada do campo de `pesquisa` de alto nível. Para pesquisar uma discussão, especifique o `tipo` como `DSCUSSÃO`. O tipo `SearchResultItemConnection` tem um campo `discussionCount` para relatar o número de discussões retornadas, e o tipo `Discussão` é adicionado à união DE `SearchResultItem`. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/pt-BR/content/graphql/overview/breaking-changes.md b/translations/pt-BR/content/graphql/overview/breaking-changes.md
index b380d7cb4d..2eee501f13 100644
--- a/translations/pt-BR/content/graphql/overview/breaking-changes.md
+++ b/translations/pt-BR/content/graphql/overview/breaking-changes.md
@@ -27,7 +27,7 @@ Vamos anunciar as próximas mudanças significativas em andamento pelo menos tr
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}Substancial{% else %}Perigoso{% endif %}</span>Será feita uma mudança em <code>{{ change.location }}</code>.
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}Substancial{% else %}Perigoso{% endif %}</span>Será feita uma mudança em <code>{{ change.location }}</code>.
 
 <p><b>Descrição:</b> {{ change.description }}</p>
 
diff --git a/translations/pt-BR/content/graphql/reference/input-objects.md b/translations/pt-BR/content/graphql/reference/input-objects.md
index 99b4b44cde..4df65a8561 100644
--- a/translations/pt-BR/content/graphql/reference/input-objects.md
+++ b/translations/pt-BR/content/graphql/reference/input-objects.md
@@ -19,6 +19,5 @@ Por exemplo, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) tom
 
 Para obter mais informações, consulte "[Sobre mutações](/graphql/guides/forming-calls-with-graphql#about-mutations)".
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index 5b7c40438d..337d2a4505 100644
--- a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: Métricas disponíveis com o GitHub Insights
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %} inclui uma variedade de métricas para dar visibilidade no processo de entrega de software da sua equipe.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index eb6a5dad87..eab74a2b7d 100644
--- a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Navegar entre o GitHub Enterprise e o GitHub Insights
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index d3993901be..39e90c49da 100644
--- a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Definindo o seu fuso horário para o GitHub Insights
 intro: 'Você pode definir o fuso horário para as métricas que você visualizar em {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
diff --git a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index f7bd336f66..949b52f447 100644
--- a/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/pt-BR/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Visualizar métricas e relatórios principais
 intro: Você pode visualizar e filtrar métricas e relatórios principais para ajudá-lo a entender e melhorar o processo de entrega de software através dos dados.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index d32a935faf..83b3f1a57a 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Sobre dados no GitHub Insights
 intro: 'Os dados incluídos nas métricas do {% data variables.product.prodname_insights %} são altamente personalizáveis.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index 0deea7498b..43a9152143 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Sobre o GitHub Insights
 intro: 'O {% data variables.product.prodname_insights %} fornece métricas e relatórios analíticos para ajudar as equipes de engenharia a entender e melhorar seu processo de entrega de software.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
index dc6cb2f9c7..65d56af637 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Configurar a conexão entre o GitHub Insights e o GitHub Enterprise
 intro: 'Você pode gerenciar como o {% data variables.product.prodname_insights %} conecta-se com {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can configure the connection to {% data variables.product.prodname_enterprise %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index 7da0e3193d..c040a97efd 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Habilitar um link entre o GitHub Insights e o GitHub Enterprise
 intro: 'Você pode habilitar um link que permitirá que os usuários naveguem de {% data variables.product.prodname_ghe_server %} para {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index d0bfd2e2a3..61d1b135ec 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Instalar o GitHub Insights
 intro: 'Você pode instalar o {% data variables.product.prodname_insights %} e conectar o aplicativo autônomo ao {% data variables.product.prodname_ghe_server %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index 88eb1fe09c..63661a8303 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar métricas e relatórios disponíveis
 intro: 'Você pode habilitar e desabilitar as métricas específicas em {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
index 5d127d8c9a..3e53edcb8b 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar contribuidores e equipes
 intro: É possível gerenciar as pessoas e equipes incluídas em métricas e relatórios.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage contributors and teams.'
@@ -98,7 +97,7 @@ Você pode criar e gerenciar equipes personalizadas no {% data variables.product
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.teams-tab %}
 {% data reusables.github-insights.edit-team %}
-3. À direita do contribuidor que você deseja remover, clique em {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Botão de Lixeira](/assets/images/help/insights/contributor-trashcan.png)
+3. À direita do contribuidor que você deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}. ![botão da lixeira](/assets/images/help/insights/contributor-trashcan.png)
 
 #### Renomear uma equipe personalizada
 
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-events.md
index 6072f3bc47..b296181e71 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-events.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-events.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar eventos
 intro: '{% data reusables.github-insights.events %}'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-events
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage events.'
@@ -29,5 +28,5 @@ Após criar um evento em {% data variables.product.prodname_insights %}, qualque
 
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.events-tab %}
-3. À direita do evento que você deseja excluir, clique em **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botão de Lixeira](/assets/images/help/insights/trashcan-button.png)
+3. À direita do evento que você deseja excluir, clique em **{% octicon "trash" aria-label="The trash icon" %}**. ![Botão de Lixeira](/assets/images/help/insights/trashcan-button.png)
 4. Clique em **Confirmar**.
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-goals.md
index 99b0edba00..749eb1b11c 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar metas
 intro: Você pode usar objetivos para definir metas para métricas principais e medir o sucesso ao alcançar essas metas.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 81c9f6f9b4..b96c4823b6 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar organizações
 intro: 'Você pode gerenciar as organizações de {% data variables.product.prodname_enterprise %} que estão incluídas nas métricas.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index c11b7a2901..378904bfb6 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar as permissões no GitHub Insights
 intro: 'Você pode atualizar as permissões de um usuário no {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-repositories.md
index 29adef74fa..47ede86331 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-repositories.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/managing-repositories.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciar repositórios
 intro: 'É possível gerenciar os repositórios conectados ao {% data variables.product.prodname_insights %} e os dados incluídos nas métricas de cada repositório.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-repositories
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories. '
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index d3bd1d745e..fda4e4c5d0 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Visão geral do sistema para o GitHub Insights
 intro: '{% data variables.product.prodname_insights %} é um aplicativo autônomo que faz interface com o {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index 9ae39e75ae..39d6087c21 100644
--- a/translations/pt-BR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/pt-BR/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Atualizar o GitHub Insights
 intro: 'Você pode fazer a atualização para a última versão do {% data variables.product.prodname_insights %} para se beneficiar de melhorias e correções de erros.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index bcbb10824f..8a8536d735 100644
--- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md
index 488ee936d0..492c962fe3 100644
--- a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -43,7 +43,7 @@ Para obter mais informações, consulte {% if currentVersion == "free-pro-team@l
 
 ### Leia mais
 
-- "[Sobre conversas no {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)"
+- "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
 - "[Sobre equipes](/articles/about-teams)"
 - "[Criar uma discussão de equipe](/organizations/collaborating-with-your-team/creating-a-team-discussion)"
 - "[Editar ou excluir uma discussão de equipe](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)"
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md
index 3ccff22fe7..635835ce21 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
 {% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index dfb464bee7..560b897e36 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -26,9 +26,8 @@ Você também pode configurar endereços IP permitidos para as organizações em
 
 ### Adicionar endereços IP permitidos
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ Você também pode configurar endereços IP permitidos para as organizações em
 
 ### Habilitar endereços IP permitidos
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. Em "IP allow list" (Lista de permissões IP), selecione **Enable IP allow list** (Habilitar lista de permissões IP). ![Caixa de seleção para permitir endereços IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. Clique em **Salvar**.
 
 ### Editar endereços IP permitidos
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ Você também pode configurar endereços IP permitidos para as organizações em
 
 ### Excluir endereços IP permitidos
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index 4cbbb87f3d..f1688ab204 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os reposit
 
 ### Exibir as configurações de segurança e análise
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização.
@@ -50,33 +49,38 @@ Você pode habilitar ou desabilitar funcionalidades para todos os repositórios.
 
 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
 2. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3. " %}O controle para "{% data variables.product.prodname_GH_advanced_security %}" fica desabilitado se você não tiver estações disponíveis na sua licença de {% data variables.product.prodname_GH_advanced_security %}{% endif %}.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Botão para desabilitar ou habilitar recurso](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Botão para habilitar o recurso para todos os repositórios elegíveis na organização](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![Botão para habilitar o recurso para todos os repositórios elegíveis na organização](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -84,12 +88,15 @@ Você pode habilitar ou desabilitar funcionalidades para todos os repositórios.
 ### Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados
 
 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
-2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+2. Em "Configurar funcionalidades de segurança e análise", à direita da funcionalidade, habilite ou desabilite o recurso por padrão para novos repositórios{% if currentVersion == "free-pro-team@latest" %}, ou todos os novos repositórios privados,{% endif %} na sua organização.
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -112,7 +119,7 @@ Para permitir que {% data variables.product.prodname_dependabot %} acesse um rep
 1. Comece a digitar o nome do repositório que você deseja permitir. ![Botão para adicionar repositórios](/assets/images/help/organizations/dependabot-private-repo-choose.png)
 1. Clique no repositório que você deseja permitir.
 
-1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. ![Botão "X" para remover um repositório](/assets/images/help/organizations/dependabot-private-repository-list.png)
+1. Opcionalmente, para remover um repositório da lista, à direita do repositório, clique em {% octicon "x" aria-label="The X icon" %}. ![Botão "X" para remover um repositório](/assets/images/help/organizations/dependabot-private-repository-list.png)
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
@@ -122,7 +129,7 @@ Para permitir que {% data variables.product.prodname_dependabot %} acesse um rep
 Você pode gerenciar o acesso a funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações". Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". No entanto, você também pode desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações" da organização.
 
 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)".
-1. Para ver uma lista de todos os repositórios na sua organização com {% data variables.product.prodname_GH_advanced_security %} habilitados, desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) A tabela lista o número de committers únicos para cada repositório. Este é o número de estações que você poderia liberar em sua licença, removendo acesso a {% data variables.product.prodname_GH_advanced_security %}. O tamanho da sua licença é mostrado para licenças no nível da organização. Para obter mais informações, consulte "[Sobre licenciamento para {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)".
+1. Para ver uma lista de todos os repositórios na sua organização com {% data variables.product.prodname_GH_advanced_security %} habilitados, desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) A tabela lista o número de committers únicos para cada repositório. Este é o número de estações que você poderia liberar em sua licença, removendo acesso a {% data variables.product.prodname_GH_advanced_security %}. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. Para remover acesso ao {% data variables.product.prodname_GH_advanced_security %} de um repositório e liberar estações usadas por todos os committers que são exclusivos do repositório, clique no {% octicon "x" aria-label="X symbol" %} adjacente.
 1. Na caixa de diálogo de confirmação, clique em **Remover repositório** para remover acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %}.
 
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index 8e005bf0df..1159f4993b 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ Antes de exigir o uso da autenticação de dois fatores, recomendamos notificar
 
 ### Exigir autenticação de dois fatores em sua organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..130d0da68d
--- /dev/null
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Sobre restrições de e-mail
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. Para obter mais informações sobre colaboradores externos, consulte "[Níveis de permissão da organização](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)".
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index 9f80146cd7..f0e4c25618 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -14,9 +14,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Na barra lateral esquerda, clique em **Installed {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s instalados). ![Guia Installed {% data variables.product.prodname_github_app %}s ({% data variables.product.prodname_github_app %}s instalados) na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. 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)
 6. Revise o acesso ao repositório e as permissões de {% data variables.product.prodname_github_app %}. ![Opção para fornecer ao {% data variables.product.prodname_github_app %} acesso a todos os repositórios ou a repositórios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index 467d92f7d9..faa78f17b8 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ Para obter mais informações sobre as permissões de gerente do {% data variabl
 
 ### Dar a um indivíduo a capacidade de gerenciar todos os {% data variables.product.prodname_github_app %}s possuídos pela organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Em "Management" (Gerenciamento), digite o nome de usuário da pessoa que deseja designar como um gerente do {% data variables.product.prodname_github_app %} na organização e clique em **Grant** (Conceder). ![Adicionar um gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### Dar a um indivíduo a capacidade de gerenciar um {% data variables.product.prodname_github_app %} individual
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Em "{% data variables.product.prodname_github_app %}s", clique no avatar do app ao qual deseja adicionar um gerente do {% data variables.product.prodname_github_app %}. ![Selecione {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index cab2db10f0..d173001f48 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ Para obter mais informações sobre as permissões de gerente do {% data variabl
 
 ### Remover as permissões de gerente do {% data variables.product.prodname_github_app %} em toda a organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Em "Management" (Gerenciamento), encontre o nome de usuário da pessoa da qual deseja remover as permissões de gerente do {% data variables.product.prodname_github_app %} e clique em **Revoke** (Revogar). ![Revogue as permissões de gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### Remover as permissões de gerente do {% data variables.product.prodname_github_app %} de um {% data variables.product.prodname_github_app %} individual
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Em "{% data variables.product.prodname_github_app %}s", clique no avatar do app no qual deseja remover um gerente do {% data variables.product.prodname_github_app %}. ![Selecione {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 81bfd73ae3..fa5720f9d3 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -49,4 +49,4 @@ Se o acesso de uma equipe a um quadro de projeto for herdado de uma equipe princ
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Acima das conversas da equipe, clique em {% octicon "project" aria-label="The Projects icon" %} **Projects** (Projetos). ![Aba repositórios da equipe](/assets/images/help/organizations/team-project-board-button.png)
-5. Para alterar os níveis de permissão, à direita do quadro de projetos que deseja atualizar, use o menu suspenso. Para remover um quadro de projeto, clique em **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botão Trash (Lixeira) Remove a project board from your team (Remover um quadro de projeto de sua equipe)](/assets/images/help/organizations/trash-button.png)
+5. Para alterar os níveis de permissão, à direita do quadro de projetos que deseja atualizar, use o menu suspenso. Para remover um quadro de projeto, clique em **{% octicon "trash" aria-label="The trash icon" %}**. ![Botão Trash (Lixeira) Remove a project board from your team (Remover um quadro de projeto de sua equipe)](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
index b65338590c..7277b41e0f 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
@@ -26,7 +26,7 @@ Se a sua organização [exigir que os integrantes usem a autenticação de dois
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
 {% if currentVersion == "free-pro-team@latest" %}
-5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![Convidar colaboradores externos para a organização](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
+5. À direita do nome do colaborador externo que você deseja que se torne integrante, use o menu suspenso {% octicon "gear" aria-label="The gear icon" %} e clique em **Convidar para a organização**.![Convidar colaboradores externos para a organização](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
 {% else %}
 5. À direita do nome do colaborador externo que você deseja que se torne integrante, clique em **Invite to organization** (Convidar para a organização).![Convidar colaboradores externos para a organização](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
 {% endif %}
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index dc746bfa5b..de37ac72cb 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ Além de gerenciar as configurações da organização, os proprietários da org
 | Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)")                                                                                                                                                                                                                                                            |         |         |          |            |                                                                       **X**                                                                        |
 | Alterar as configurações do repositório                                                                                                                                                                                                                                                                                                                                           |         |         |          |            |                                                                       **X**                                                                        |
 | Gerenciar o acesso de equipe e de colaborador ao repositório                                                                                                                                                                                                                                                                                                                      |         |         |          |            |                                                                       **X**                                                                        |
-| Editar o branch padrão do repositório                                                                                                                                                                                                                                                                                                                                             |         |         |          |            |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Editar o branch padrão do repositório                                                                                                                                                                                                                                                                                                                                             |         |         |          |            |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                                       |         |         |          |            |                                                                       **X**                                                                        |
 | Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                  |         |         |  **X**   |   **X**    |                                                                 **X** 
 {% endif %}
@@ -142,7 +142,8 @@ Além de gerenciar as configurações da organização, os proprietários da org
 | [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                  |         |  **X**  |  **X**   |   **X**    |                                                                       **X**                                                                        |
 | [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                  |         |  **X**  |  **X**   |   **X**    |                                                                       **X**                                                                        |
 | [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                      |  **X**  |  **X**  |  **X**   |   **X**    |                                                                       **X**                                                                        |
-| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                       |         |         |          |   **X**    |                                                                 **X** 
+| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                       |         |         |          |   **X**    |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                 |         |         |  **X**   |   **X**    |                                                                 **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ Nesta seção, você pode encontrar os níveis de permissão de repositório nec
 
 | Ação no repositório                                                                                                                                                                                                                                                                            | Leitura | Triagem |      Gravação       |     Manutenção      |                                                                         Administrador                                                                         |
 |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                                                                                              |         |         |                     |                     |                                                                                                                                                               |
-| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório                                                                                        |         |         |                     |                     |                                                                             **X**                                                                             |
-| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                                 |         |         |                     |                     |                                                                             **X**                                                                             |
-| [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para as dependências vulneráveis                |         |         |                     |                     |                                                                             **X**                                                                             |
-| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories)                                                                                                                                                                                  |         |         |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar 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)") |         |         |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                                                                                            |         |         |                     |                     |                                                                                                                                                               |
+| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) em um repositório                                                                                             |         |         |                     |                     |                                                                             **X**                                                                             |
+| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                                      |         |         |                     |                     |                                                                             **X**                                                                             |
+| [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para as dependências vulneráveis                |         |         |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Criar [consultorias de segurança](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                                                                         |         |         |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar 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)") |         |         |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado                                                                                                                                               |         |         |                     |                     |                                                                             **X**                                                                             |
 | [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                         |  **X**  |  **X**  |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                                                                                |  **X**  |  **X**  |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index 322bebdad6..03702b7650 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ Se alguém com permissão de administrador no repositório de uma organização
 
 ### Definir permissões básicas
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Permissões básicas", use o menu suspenso para selecionar novas permissões básicas. ![Selecionar novo nível de permissão a partir do menu suspenso de permissões básicas](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. Revise as alterações. Para confirmar, clique em **Alterar permissão-padrão para PERMISSÃO**. ![Revisar e confirmar a alteração das permissões básicas](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index ee9cb84eef..17eef7bc46 100644
--- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -22,17 +22,15 @@ Você pode permitir que os integrantes acessem os repositórios da organização
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### Excluir uma autoridade certificada de SSH
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index a77f69082a..ea36391206 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -17,9 +17,8 @@ Por padrão, os problemas não podem ser excluídos dos repositórios de uma org
 
 Uma vez habilitado, os proprietários da organização e as pessoas com permissões de administrador em um repositório pertencente à organização podem excluir os problemas. As pessoas com permissões de administrador em um repositório incluem integrantes da organização e colaboradores externos com privilégios administrativos. Para obter mais informações, consulte "[ Níveis de permissão do repositório da organização](/articles/repository-permission-levels-for-an-organization/)" e "[Excluir um problema](/articles/deleting-an-issue)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Issue deletion" (Exclusão do problema), selecione **Allow members to delete issues for this organization** (Permitir que integrantes excluam problemas dessa organização). ![Caixa de seleção para permitir que as pessoas excluam problemas](/assets/images/help/settings/issue-deletion.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index 0822d4e59c..7c41bd678e 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,9 +16,8 @@ Os proprietários da organização podem definir limitações para exibir inform
 
 Os proprietários corporativos podem definir limitações para exibir informações de dependência da organização em todas as organizações da sua conta corporativa. Para obter mais informações, consulte "[Aplicar uma política nas informações de dependência de sua conta corporativa](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Member organization permissions" (Permissões da organização do integrante), marque ou desmarque **Allow members to view dependency insights** (Permitir que integrantes exibam informações de dependência). ![Caixa de seleção para permitir que integrantes exibam informações](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 49018f903f..69d6b7bd88 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -28,7 +28,6 @@ Depois que você exclui uma organização, o GitHub **não pode restaurar o cont
 
 ### 2. Excluir a organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Próximo à parte inferior da página de configurações da organização, clique em **Delete this Organization** (Excluir esta organização). ![Botão Delete this organization (Excluir esta organização)](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 8633147cf5..84c0faa1ec 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -27,9 +27,8 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti
 
 ### Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Em **Ações locais e de terceiros**, selecione uma opção. ![Habilitar, desabilitar ou limitar ações para esta organização](/assets/images/help/repository/enable-org-actions.png)
 1. Clique em **Salvar**.
@@ -50,9 +49,8 @@ Você pode desabilitar todos os fluxos de trabalho para uma organização ou def
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Em **Políticas**, selecione uma opção. ![Definir política de ações para esta organização](/assets/images/help/organizations/actions-policy.png)
 1. Clique em **Salvar**.
@@ -61,9 +59,8 @@ Você pode desabilitar todos os fluxos de trabalho para uma organização ou def
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. Clique em **Salvar**.
@@ -77,9 +74,31 @@ Você pode desabilitar todos os fluxos de trabalho para uma organização ou def
 
 #### Configurar a política de bifurcação privada para uma organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Definindo as permissões do `GITHUB_TOKEN` para a sua organização
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para a sua organização ou repositórios. Se você escolher a opção restrita como padrão nas configurações da sua organização, a mesma opção será selecionada automaticamente nas configurações dos repositórios na organização, e a opção permissiva ficará desabilitada. Se sua organização pertence a uma conta {% data variables.product.prodname_enterprise %} e o padrão mais restrito foi selecionado nas configurações corporativas, você não poderá de escolher o padrão mais permissivo nas configurações da organização.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configurar as permissões padrão do `GITHUB_TOKEN`
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. Em **permissões do fluxo de trabalho**, escolha se você quer que o `GITHUB_TOKEN` tenha acesso de leitura e gravação para todos os escopos, ou apenas acesso de leitura para o escopo do </code>conteúdo.
+<img src="/assets/images/help/settings/actions-workflow-permissions-organization.png" alt="Definir permissões do GITHUB_TOKEN para esta organização" /></p></li>
+<li><p spaces-before="0">Clique em <strong x-id="1">Salvar</strong> para aplicar as configurações.
+</p>
+
+<p spaces-before="0">{% endif %}</p></li>
+</ol>
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/index.md b/translations/pt-BR/content/organizations/managing-organization-settings/index.md
index 9ea745b340..7589f8cb2b 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/index.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/index.md
@@ -13,7 +13,7 @@ topics:
   - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index ab739daacc..be22796119 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ As etiquetas padrão são incluídas em cada repositório novo na organização,
 
 ### Criar etiquetas padrão
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ As etiquetas padrão são incluídas em cada repositório novo na organização,
 
 ### Editar etiquetas padrão
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ As etiquetas padrão são incluídas em cada repositório novo na organização,
 
 ### Excluir etiquetas padrão
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 0443acd12e..a0bbb7dded 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 Por padrão, integrantes da organização com acesso de leitura podem criar discussões se um administrador ou proprietário da organização habilitar discussões para um repositório pertencente à organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Discussões do repositório, selecione ou desmarque **Permitir que os usuários com acesso de leitura criem discussões**. ![Caixa de seleção para permitir que pessoas com acesso de leitura criem discussões](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. Clique em **Salvar**. ![Botão "Salvar" para configurações de discussões](/assets/images/help/discussions/click-save.png)
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index 756e6b1c3c..d477c993c3 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ Os proprietários da organização podem agendar um lembrete para uma ou mais eq
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### Criar um lembrete agendado para uma organização
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Botão de lembretes agendados](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ Os proprietários da organização podem agendar um lembrete para uma ou mais eq
 {% data reusables.reminders.create-reminder %}
 
 ### Gerenciar um lembrete agendado para uma organização
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Botão de lembretes agendados](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ Os proprietários da organização podem agendar um lembrete para uma ou mais eq
 {% data reusables.reminders.update-buttons %}
 
 ### Excluir um lembrete agendado para uma organização
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Botão de lembretes agendados](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index 7652a46712..cb9bcfdf80 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ Se um proprietário da empresa tiver aplicado uma política para o nome do branc
 
 ### Definir o nome do branch-padrão
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. Em "Branch padrão do repositório", clique em **Alterar o nome do branch-padrão agora**. ![Botão de sobrescrever](/assets/images/help/organizations/repo-default-name-button.png)
 4. Digite o nome-padrão que você gostaria de usar para novos branches. ![Caixa de texto para digitar o nome-padrão](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index ceac24a103..c836c8053f 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -20,9 +20,8 @@ Proprietários de organização podem gerenciar a exibição do nome de integran
 
 Cada integrante da organização escolhe o próprio nome de perfil nas configurações. Para obter mais informações, consulte "[Personalizar seu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Admin repository permissions" (Permissões do administrador do repositório), marque ou desmarque **Allow members to see comment author's profile name in private repositories** (Permitir que integrantes vejam nome de perfil do autor nos repositórios privados). ![Caixa de seleção para permitir que integrantes vejam o nome completo do autor do comentário nos repositórios privados](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 16b6d9210b..dba010f35d 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ Se você permite a bifurcação do repositório privado{% if currentVersion == "
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Bifurcação do repositório", selecione **Permitir bifurcação de repositórios privados** ou **Permitir bifurcação de repositórios internos e privados**. ![Caixa de seleção para permitir ou proibir a bifurcação na organização](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
index ab466ddbe1..5a75872703 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -16,14 +16,13 @@ topics:
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
-If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Caso contrário, você pode optar por permitir ou negar a publicação pública. Para obter mais informações sobre controle de acesso para sites de {% data variables.product.prodname_pages %}, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)".
+Se sua organização usar {% data variables.product.prodname_ghe_cloud %}, você poderá optar por permitir que os integrantes da organização criem sites públicos ou privados, ambos ou nenhum. Caso contrário, você pode optar por permitir ou negar a publicação pública. Para obter mais informações sobre controle de acesso para sites de {% data variables.product.prodname_pages %}, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)".
 {% endif %}
 
 Se você não permitir a publicação de sites de {% data variables.product.prodname_pages %}, todos os sites publicados permanecerão publicados. Você pode remover manualmente a publicação do site. Para obter mais informações, consulte "[Cancelar a publicação de um site do {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
 1. Em "Criação de páginas", selecione as visibilidades que você deseja permitir e desmarque as visibilidades que você não deseja permitir. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
 1. Em "Criação de páginas", marque ou desmarque **Permitir que os integrantes publiquem sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}
@@ -31,4 +30,4 @@ Se você não permitir a publicação de sites de {% data variables.product.prod
 
 ### Leia mais
 
-- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)"
+- "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)"
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index bd3a3912eb..79b86050f0 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 Os desenvolvedores e as organizações que sua organização patrocina podem enviar atualizações sobre o seu trabalho para você. Você pode gerenciar o endereço de e-mail que recebe essas atualizações.
 
-Você também pode desabilitar atualizações de contas que a sua organização patrocina. Para obter mais informações, consulte "[Gerenciar o patrocínio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)".
+Você também pode desabilitar atualizações de contas que a sua organização patrocina. Para obter mais informações, consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Em "E-mail de atualização de patrocínios (Privado)", digite o endereço de e-mail em que deseja receber atualizações de contas patrocinadas pela sua organização. ![Caixa de texto para inserir o endereço de email para receber atualizações de contas patrocinadas](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. Clique em **Update profile** (Atualizar perfil). ![Botão Update profile (Atualizar perfil)](/assets/images/help/organizations/update-profile-button.png)
 
 ### Leia mais
 
-- "[Apoiar a comunidade de código aberto com {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)"
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md
index c75d40b41a..542a628a6a 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -27,7 +27,7 @@ Depois que você altera o nome da organização, o nome antigo da organização
 #### Alterações que ocorrem automaticamente
 
 - O {% data variables.product.prodname_dotcom %} redireciona automaticamente as referências aos seus repositórios.  Os links da web para os **repositórios** da organização continuarão a funcionar. Esse processo pode demorar alguns minutos após a alteração.
-- Você pode continuar a fazer push dos repositórios locais para a URL de controle do remote antigo sem atualizá-lo. No entanto, recomendamos que você atualize todas as URLs do repositório remoto depois de alterar o nome da organização. Como o nome antigo da organização ficou disponível para uso por qualquer pessoa após a alteração, o proprietário da nova organização pode criar repositórios que sobrescrevem as entradas de redirecionamento para o seu repositório. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+- Você pode continuar a fazer push dos repositórios locais para a URL de controle do remote antigo sem atualizá-lo. No entanto, recomendamos que você atualize todas as URLs do repositório remoto depois de alterar o nome da organização. Como o nome antigo da organização ficou disponível para uso por qualquer pessoa após a alteração, o proprietário da nova organização pode criar repositórios que sobrescrevem as entradas de redirecionamento para o seu repositório. Para obter mais informações, consulte "[Gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 - Os Git commits anteriores também serão atribuídos corretamente ao usuários na sua organização.
 
 #### Alterações que não são automáticas
@@ -35,14 +35,13 @@ Depois que você altera o nome da organização, o nome antigo da organização
 Depois de alterar o nome da organização:
 - Os links para a página de perfil da organização anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, retornarão um erro 404. Recomendamos que você atualize os links para a sua organização a partir de outros sites{% if currentVersion == "free-pro-team@latest" %}, como, por exemplo, os seus perfis do LinkedIn ou do Twitter{% endif %}.
 - As solicitações de API que usam o nome antigo da organização retornarão um erro 404. Recomendamos que você atualize o nome da organização nas solicitações de API.
-- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %}
-- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %}
+- Não há redirecionamentos de [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) automática para equipes que usam o nome da organização antiga.{% if currentVersion == "free-pro-team@latest" %}
+- Se o SAML logon único (SSO) estiver habilitado para a organização, você deverá atualizar o nome da organização no aplicativo para {% data variables.product.prodname_ghe_cloud %} no seu provedor de identidade (IdP). Se você não atualizar o nome da organização no seu IdP, os integrantes da organização não poderão mais efetuar a autenticação com seu IdP para acessar os recursos da organização. Para obter mais informações, consulte "[Conectando o seu provedor de identidade à sua organização](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %}
 
 ### Alterar o nome da organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Perto da parte inferior da página de configuração, em "Rename organization" (Renomear organização), clique em **Rename Organization** (Renomear organização). ![Botão Rename organization (Renomear organização)](/assets/images/help/settings/settings-rename-organization.png)
 
 ### Leia mais
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 96379dace1..4ea1ce266a 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
@@ -27,9 +27,8 @@ Os proprietários da organização sempre podem criar qualquer tipo de repositó
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Criação do repositório", selecione uma ou mais opções. ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index 04f210ee5e..255caac16d 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ Você pode restringir a capacidade de alterar a visibilidade do repositório ape
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Repository visibility change" (Alteração da visibilidade do repositório), desmarque a opção **Allow members to change repository visibilities for this organization** (Permitir que os integrantes alterem a visibilidade dos repositórios nesta organização). ![Caixa de seleção para permitir que os integrantes alterem a visibilidade dos repositórios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index b836d6b273..d29936cb4d 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -19,9 +19,8 @@ Os proprietários da organização e integrantes com privilégios de administrad
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Convites para o repositório", selecione **Permitir que os integrantes convidem colaboradores externos para repositórios desta organização**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 165b76766f..3e50f28994 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -16,9 +16,8 @@ topics:
 
 Proprietários podem definir permissões para excluir ou transferir repositórios na organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Repository deletion and transfer" (Exclusão e transferência de repositório), marque ou desmarque a opção **Allow members to delete or transfer repositories for this organization** (Permitir que os integrantes excluam ou transfiram repositórios na organização). ![Caixa de seleção para permitir que os integrantes excluam repositórios](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index 817dd46208..833807f5df 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -17,9 +17,8 @@ Os proprietários da organização podem configurar permissões de criação de
 
 Se você não configurar as permissões de criação de equipes, todos os integrantes da organização poderão criar equipes por padrão.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Em "Team creation rules" (Regras de criação de equipes), marque ou desmarque a opção **Allow members to create teams** (Permitir que integrantes criem equipes). ![Caixa de seleção para permitir que integrantes criem equipes](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..c8a2b9aca2
--- /dev/null
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### Sobre a verificação do domínio
+
+Após a verificação da propriedade dos domínios da sua organização, é exibido um selo "Verified" (Verificado) no perfil da organização. Se ela estiver no {% data variables.product.prodname_ghe_cloud %} e tiver concordado com os Termos de serviço corporativos, os proprietários da organização poderão verificar a identidade dos integrantes dela exibindo o endereço de e-mail de cada um deles no domínio verificado. Para obter mais informações, consulte "[Sobre a página de perfil da sua organização](/articles/about-your-organization-s-profile/)" e "[Atualizar para os Termos de serviço corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".
+
+Se sua organização pertence a uma conta corporativa, será exibido um selo "Verificado" no perfil da sua organização para quaisquer domínios verificados para a conta corporativa, além de quaisquer domínios verificados para a organização. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+No {% data variables.product.prodname_ghe_cloud %}, após a verificação da propriedade do domínio da sua organização, você pode restringir as notificações de email para a organização a esse domínio. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Aguarde a alteração da configuração de DNS, que pode demorar até 72 horas. Você pode confirmar que a configuração do DNS foi alterada executando o comando `dig` na linha de comando, substituindo `ORGANIZATION` pelo nome da sua organização e `example.com` pelo o domínio que você gostaria de verificar. Você deverá ver o novo registro TXT listado na saída do comando.
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. Depois que o selo "Verified" (Verificado) estiver visível na página de perfil da sua organização, a entrada TXT poderá ser excluída do registro DNS no serviço de hospedagem de domínio. ![Selo Verified (Verificado)](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index e8cd6e745a..4cf54fa8db 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ Os gerentes de cobrança **não** podem:
 
 A pessoa convidada receberá um e-mail de convite solicitando que ela se torne um gerente de cobrança da sua organização. Assim que a pessoa convidada clicar no link de aceitação no e-mail de convite, ela será adicionada automaticamente à organização como um gerente de cobrança. Se ela ainda não tiver uma conta do GitHub, ela será direcionada para se inscrever em uma, e será adicionada automaticamente à organização como um gerente de cobrança depois que ela criar uma conta.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Ao lado de Billing managers (Gerentes de cobrança), clique em **Add a billing manager** (Adicionar um gerente de cobrança). ![Convidar gerente de cobrança](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![Convidar gerente de cobrança](/assets/images/help/billing/settings_billing_managers_list.png)
 6. Digite o nome de usuário ou endereço de e-mail da pessoa que deseja adicionar e clique em **Send invitation** (Enviar convite). ![Página para convidar gerente de cobrança](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index 30f6a2292e..af09de7841 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -23,6 +23,12 @@ topics:
 
 Os proprietários da organização têm pleno acesso administrativo à organização. {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**Observação**: Como proprietário de uma organização, você pode alterar a função dos outros integrantes e proprietários da organização. Você não pode mudar a sua própria função.
+
+{% endnote %}
+
 ### Designar um proprietário da organização
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index 249e1d97df..66d06add70 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ Os integrantes da organização podem ter funções de *proprietário*{% if curr
 | Acessar o log de auditoria da organização                                                                                                                                                                                                                                                                                                                                                  |     **X**     |             |                      |
 | Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes)                                                                                                                                                                                                                                       |     **X**     |             |                      |
 | Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes)                                                                                                                                                                                                                                   |     **X**     |             |                      |
-| Restringir notificações de e-mail a domínios verificados (consulte "[Restringir notificações de e-mail para um domínio aprovado](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" para obter informações)                                                                                                                           |     **X**     |             |                      |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)                                                                                                                                            |     **X**     |             |                      |
 | Excluir **todas as equipes**                                                                                                                                                                                                                                                                                                                                                               |     **X**     |             |                      |
 | Excluir a conta da organização, inclusive todos os repositórios                                                                                                                                                                                                                                                                                                                            |     **X**     |             |                      |
 | Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes)                                                                                                                                                                                                                    |     **X**     |    **X**    |                      |
@@ -60,9 +60,9 @@ Os integrantes da organização podem ter funções de *proprietário*{% if curr
 | Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes)                                                                                                                                                                                               |     **X**     |             |                      |
 | Gerenciar a visualização de informações de dependência da organização (consulte "[Alterar a visibilidade das informações de dependência da organização](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para detalhes)                                                                                                                                       |     **X**     |             |                      |
 | Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes)                                                                                                                                                                                                        |     **X**     |             |                      |
-| Patrocinar contas e gerenciar os patrocínios da organização (Consulte "[Patrocinar contribuidoresde código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para mais detalhes)                                                                                                                                             |     **X**     |    **X**    |                      |
+| Patrocinar contas e gerenciar os patrocínios da organização (Consulte "[Patrocinar contribuidoresde código aberto](/sponsors/sponsoring-open-source-contributors)" para mais detalhes)                                                                                                                                                                                                     |     **X**     |    **X**    |                      |
 | Gerenciar atualizações de e-mail de contas patrocinadas (consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" para obter detalhes)                                                                                                                       |     **X**     |             |                      |
-| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obter mais detalhes)                                                                                                                                           |     **X**     |             |                      |
+| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" para obter mais detalhes)                                                                                                                                                               |     **X**     |             |                      |
 | Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) |     **X**     |             |                      |
 | Gerenciar as configurações de segurança e análise (consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para obter mais informações)                                                                                                       |     **X**     |             |                      |
 | Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                                                                                                                                           |     **X**     |             |                      |
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index a8176574b8..72a8d4e278 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Na lista Billing managers (Gerentes de cobrança), clique em {% octicon "x" aria-label="X symbol" %} ao lado do nome do usuário que deseja remover. ![Remover gerente de cobrança](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![Remover gerente de cobrança](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index eb73c2ecee..ea21aeb98c 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 Os códigos de recuperação não devem ser compartilhados ou distribuídos. É recomendável salvá-los com um gerenciador de senha como [LastPass](https://lastpass.com/), [1Password](https://1password.com/) ou [Keeper](https://keepersecurity.com/).
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Em "SAML single sign-on" (Logon único de SAML), na observação sobre código de recuperação, clique em **Save your recovery codes** (Salvar os códigos de recuperação). ![Link para exibir e salvar os códigos de recuperação](/assets/images/help/saml/saml_recovery_codes.png)
 6. Salve seus códigos de recuperação clicando em **Download** (Baixar), **Print** (Imprimir) ou **Copy** (Copiar). ![Botões para baixar, imprimir ou copiar os códigos de recuperação](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index 327aa9f6aa..416b3160c4 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ Se você habilitar em vez de aplicar o SAML SSO, os integrantes da organização
 
 Antes de aplicar o SAML SSO à sua organização, verifique se você configurou o provedor de identidade (IdP, Identity Provider). Para obter mais informações, consulte "[Preparar para aplicar logon único de SAML na organização](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)".
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Em "SAML single sign-on" (Logon único de SAML), selecione **Enable SAML authentication** (Habilitar autenticação SAML). ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index 3894743ff5..36dc34ba6f 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ Você deve efetuar a autenticação para a sua organização usando SAML SSO e o
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ Você deve efetuar a autenticação para a sua organização usando SAML SSO e o
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ Você deve efetuar a autenticação para a sua organização usando SAML SSO e o
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Em "Team synchronization" (Sincronização de equipes), clique em **Disable team synchronization** (Desabilitar sincronização de equipes). ![Desabilitar a sincronização de equipes](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index da399932a0..a51e6df2a3 100644
--- a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -29,9 +29,8 @@ Para obter mais informações, consulte "[Níveis de permissão do repositório
 
 ### Migrar todas as equipes de administradores legadas da organização
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Revise as equipes de administradores legadas da organização e clique em **Migrate all teams** (Migrar todas as equipes). ![Botão Migrate all teams (Migrar todas as equipes)](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. Leia as informações sobre possíveis alterações de permissões para integrantes dessas equipes e clique em **Migrate all teams** (Migrar todas as equipes). ![Botão Confirm migration (Confirmar migração)](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index df80b065f2..e301435cc0 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -15,9 +15,8 @@ topics:
 
 {% data reusables.organizations.team-discussions-default %} Consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para obter mais informações sobre esse assunto.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. Em "Team discussions" (Discussões de equipe), desmarque **Enable team discussions for this organization** (Habilitar discussões de equipe desta organização). ![Caixa de seleção para habilitar ou desabilitar discussões de equipe de uma organização](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
index d909224449..da37727a44 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
@@ -30,7 +30,7 @@ Todas as alterações de membros da equipe feitas através do seu IdP aparecerã
 {% endif %}
 
 {% if currentVersion == "github-ae@latest" %}
-When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Qualquer solicitação que altere a equipe de {% data variables.product.prodname_dotcom %} equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário. Para obter mais informações sobre essa conta, consulte "[Configurar o provisionamento de usuários para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obter mais informações sobre o agendamento de pedidos do SCIM, consulte "[Verificar o status do provisionamento do usuário](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" na documentação da Microsoft.
+Quando o membro do grupo for alterado no seu IdP, este enviará uma solicitação SCIM com as alterações para {% data variables.product.product_name %} de acordo com o agendamento determinado pelo seu IdP. Qualquer solicitação que altere a equipe de {% data variables.product.prodname_dotcom %} equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário. Para obter mais informações sobre essa conta, consulte "[Configurar o provisionamento de usuários para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obter mais informações sobre o agendamento de pedidos do SCIM, consulte "[Verificar o status do provisionamento do usuário](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" na documentação da Microsoft.
 {% endif %}
 
 As equipes principais não podem sincronizar com grupos de IdP. Se a equipe que você deseja conectar a um grupo IdP for uma equipe principal, recomendamos criar uma equipe nova ou remover as relações aninhadas que fazem da sua equipe uma equipe principal. Para obter mais informações, consulte "[Sobre as equipes](/articles/about-teams#nested-teams)"[Criar uma equipe](/organizations/organizing-members-into-teams/creating-a-team), e "[Mover uma equipe para a hierarquia da sua organização](/articles/moving-a-team-in-your-organizations-hierarchy)
@@ -47,7 +47,7 @@ Após conectar uma equipe a um grupo de IdP, a sincronização da equipe adicion
 - A pessoa já efetuou o login com sua conta de usuário em {% data variables.product.product_name %} e efetuou a autenticação na conta corporativa ou corporativa via logon único SAML pelo menos uma vez.
 - A identidade SSO da pessoa é um integrante do grupo IdP.
 
-As equipes ou integrantes de grupo que não atenderem a esses critérios serão automaticamente removidos da equipe em {% data variables.product.product_name %} e perderão o acesso aos repositórios. Revogar a identidade vinculada a um usuário também removerá o usuário de quaisquer equipes mapeadas com os grupos de IdP. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."
+As equipes ou integrantes de grupo que não atenderem a esses critérios serão automaticamente removidos da equipe em {% data variables.product.product_name %} e perderão o acesso aos repositórios. Revogar a identidade vinculada a um usuário também removerá o usuário de quaisquer equipes mapeadas com os grupos de IdP. Para mais informações consulte "[Visualizar e gerenciar o acesso SAML de um membro à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" e "[Visualizar e gerenciar o acesso SAML de um usuário à sua empresa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)".
 
 Um integrante removido da equipe pode ser adicionado de volta a uma equipe automaticamente após efetuar a autenticação na conta da organização ou na conta corporativa usando SSO e será movidos para o grupo de IdP conectado.
 
@@ -60,16 +60,16 @@ Se sua organização pertencer a uma conta corporativa, habilitar a sincronizaç
 ### Pré-requisitos
 
 {% if currentVersion == "free-pro-team@latest" %}
-Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)."
+Antes de você poder conectar uma equipe de {% data variables.product.product_name %} a um grupo de provedores de identidade, uma organização ou proprietário da empresa deverá habilitar a sincronização de equipes para a sua organização ou conta corporativa. Para mais informações, consulte "[Gerenciar a sincronização de equipes para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" e "[Gerenciando a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)".
 
 Para evitar a remoção involuntária dos integrantes da equipe, visite o portal administrativo do seu IdP e confirme se cada integrante atual da equipe está também nos grupos de IdP aos quais você deseja conectar a esta equipe. Se você não tiver acesso ao provedor de identidade, entre em contato com o administrador do IdP.
 
 Você deve efetuar a autenticação usando SAML SSO. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)".
 
 {% elsif currentVersion == "github-ae@latest" %}
-Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
+Antes de conectar uma equipe de {% data variables.product.product_name %} a um grupo de IdP, primeiro você deve configurar o provisionamento de usuários para {% data variables.product.product_location %} usando um Sistema suportado para Gerenciamento de Identidade entre Domínios (SCIM). Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
 
-Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. Para obter mais informações, consulte [Configurar o provisionamento automático do usuário no GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) na documentação da Microsoft.
+Quando o provisionamento de {% data variables.product.product_name %} for configurado usando o SCIM, você poderá atribuir o aplicativo de {% data variables.product.product_name %} a cada grupo de IdP que você deseja usar em {% data variables.product.product_name %}. Para obter mais informações, consulte [Configurar o provisionamento automático do usuário no GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) na documentação da Microsoft.
 {% endif %}
 
 ### Conectar um grupo de IdP a uma equipe
diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index d8580a2964..5b71287e87 100644
--- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} são habilitadas, os integrantes da organização devem [solicitar aprovação](/articles/requesting-organization-approval-for-oauth-apps) de um proprietário da organização para que eles possam autorizar um {% data variables.product.prodname_oauth_app %} que tenha acesso aos recursos da organização.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Ao lado do aplicativo que deseja aprovar, clique em **Review** (Revisar). ![Link de solicitação de revisão](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. Depois que revisar as informações sobre o aplicativo solicitado, clique em **Grant access** (Conceder acesso). ![Botão Grant access (Conceder acesso)](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index 76dadbc8f2..e2bedeb663 100644
--- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -12,9 +12,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Ao lado do aplicativo que deseja desabilitar, clique em {% octicon "pencil" aria-label="The edit icon" %}. ![Ícone Edit (Editar)](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. Clique em **Deny access** (Negar). ![Botão Deny confirmation (Negar confirmação)](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index cf8496d6cc..9b82f23a3b 100644
--- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Clique em **Remove restrictions** (Remover restrições). ![Botão Remove restrictions (Remover restrições)](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. Depois de revisar as informações sobre desabilitação de restrições de aplicativos de terceiros, clique em **Yes, remove application restrictions** (Sim, remover restrições de aplicativos). ![Botão de remover confirmação](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index 1f8090202a..81fc873745 100644
--- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Em "Third-party application access policy" (Política de acesso a aplicativos de terceiros), clique em **Setup application access restrictions** (Configurar restrições de acesso a aplicativos). ![Botão Set up restrictions (Configurar restrições)](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. Depois de revisar as informações sobre restrições de acesso a terceiros, clique em **Restrict third-party application access** (Restringir acesso a aplicativos de terceiros). ![Botão Restriction confirmation (Confirmação de restrição)](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/pt-BR/content/packages/index.md b/translations/pt-BR/content/packages/index.md
index 16909bad44..56da6e12a3 100644
--- a/translations/pt-BR/content/packages/index.md
+++ b/translations/pt-BR/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..cad5b82ad0
--- /dev/null
+++ b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,85 @@
+---
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Visibilidade e permissões de acesso para imagens de contêiner
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Sobre escopos e permissões para registros de pacotes
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+Por exemplo:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}Para excluir um pacote em {% data variables.product.product_name %}, o seu token deve ter pelo menos o escopo `delete:packages` e `read:packages`. O escopo de `repo` também é necessário para pacotes com escopo de repositórios.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}Para excluir uma versão especificada de um pacote privado em {% data variables.product.product_name %}, o seu token deve ter o escopo `delete:packages` e `repo`. Public packages cannot be deleted.{% elsif currentVersion == "github-ae@latest" %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+
+| Escopo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Descrição                                                                             | Permissão necessária |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------- |
+| `read:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Faça o download e instale pacotes do {% data variables.product.prodname_registry %}   | leitura              |
+| `write:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Faça o upload e publique os pacotes em {% data variables.product.prodname_registry %} | gravação             |
+| `delete:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                                       |                      |
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Delete packages from {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} |                                                                                       |                      |
+| administrador                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                                                                                       |                      |
+| `repo`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Faça o upload e exclua os pacotes (junto com `write:packages` ou `delete:packages`)   | write or admin       |
+
+Ao criar um fluxo de trabalho de {% data variables.product.prodname_actions %}, você pode usar o `GITHUB_TOKEN` para publicar e instalar pacotes no {% data variables.product.prodname_registry %} sem precisar armazenar e gerenciar um token de acesso pessoal.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Escopos disponíveis](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..bb976760a4
--- /dev/null
+++ b/translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: Configuring a package's access control and visibility
+intro: 'Escolha quem tem acesso de leitura, gravação ou administrador à sua imagem de contêiner e a visibilidade das suas imagens de contêiner em {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+### Visibilidade e permissões de acesso para imagens de contêiner
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### Configurar acesso a imagens de contêiner para sua conta pessoal
+
+If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](#visibility-and-access-permissions-for-container-images)".
+
+Se o seu pacote for privado ou interno e pertencer a uma organização, você somente poderá dar acesso a outros integrantes ou equipes da organização.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. As equipes não podem ter acesso a uma imagem de contêiner de uma conta de usuário. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png)
+1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png)
+
+Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro.
+
+### Configurar o acesso a imagens de contêiner para uma organização
+
+Se você tiver permissões de administrador para uma imagem de contêiner pertencente à organização, pode atribuir funções de leitura, gravação ou administrador para outros usuários e equipes. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](#visibility-and-access-permissions-for-container-images)".
+
+Se o seu pacote for privado ou interno e pertencer a uma organização, você somente poderá dar acesso a outros integrantes ou equipes da organização.
+
+Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes antes que você possa definir a visibilidade como pública. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. Você também pode inserir um nome de equipe da organização para dar acesso a todos os integrantes da equipe. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png)
+1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png)
+
+Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro.
+
+### Herdar acesso a uma imagem de contêiner de um repositório
+
+Para simplificar o gerenciamento de pacotes por meio dos fluxos de trabalho de {% data variables.product.prodname_actions %}, você pode habilitar uma imagem contêiner para herdar as permissões de acesso de um repositório por padrão.
+
+Se você herdar as permissões de acesso do repositório onde os fluxos de trabalho do seu pacote são armazenados, posteriormente, você poderá ajustar o acesso ao seu pacote pelas permissões do repositório.
+
+Uma vez que um repositório é sincronizado, você não poderá acessar as configurações de acesso granular do pacote. Para personalizar as permissões do pacote através das configurações de acesso ao pacote granular, você deverá remover a sincronização do repositório primeiro.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. Em "Fonte do repositório", selecione **Herdar acesso do repositório (recomendado)**. ![Caixa de seleção herdar acesso do repositório](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### Garantir o acesso ao fluxo de trabalho para o seu pacote
+
+Para garantir que um fluxo de trabalho do {% data variables.product.prodname_actions %} tenha acesso ao seu pacote, você deverá conceder acesso explícito ao repositório onde o fluxo de trabalho é armazenado.
+
+O repositório especificado não precisa ser o repositório onde o código-fonte do pacote é mantido. Você pode conceder acesso ao fluxo de trabalho de vários repositórios para um pacote.
+
+{% note %}
+
+**Observação:** Sincronizar sua imagem de contêiner com um repositório por meio da opção de menu **Acesso de ações** é diferente de conectar seu contêiner a um repositório. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+#### {% data variables.product.prodname_actions %} access for user-account-owned container images
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+#### {% data variables.product.prodname_actions %} access for organization-owned container images
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Usando o menu suspenso "função", selecione o nível de acesso padrão que você gostaria que os integrantes do repositório tivessem na sua imagem contêiner. Os colaboradores externos não serão incluídos. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+Para personalizar ainda mais o acesso à sua imagem de contêiner, consulte "[Configurar acesso a imagens de contêiner para uma organização](#configuring-access-to-container-images-for-an-organization)".
+
+### Configurar a visibilidade de imagens de contêiner para sua conta pessoal
+
+Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver o pacote. Você pode modificar o acesso de uma imagem do contêiner privada ou pública, alterando as configurações de acesso.
+
+Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. Em "Zona de Perigo", escolha uma configuração de visibilidade:
+    - Para tornar a imagem do contêiner visível para qualquer pessoa, clique em **Tornar pública**.
+    {% warning %}
+
+    **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente.
+
+    {% endwarning %}
+    - Para tornar a imagem do contêiner visível para uma seleção personalizada de pessoas, clique em **Tornar privada**. ![Opções de visibilidade do contêiner](/assets/images/help/package-registry/container-visibility-option.png)
+
+### Visibilidade da criação de contêiner para os integrantes da organização
+
+Você pode escolher a visibilidade de contêineres que os integrantes da organização podem publicar por padrão.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. À esquerda, clique em **Pacotes**.
+6. Em "Criação de contêiner", escolha se deseja permitir a criação de imagens públicas, privadas ou internas de contêineres.
+    - Para permitir que os integrantes da organização criem imagens de contêiner público, clique em **Público**.
+    - Para permitir que os integrantes da organização criem imagens privadas de contêiner visíveis apenas para outros integrantes da organização, clique em **Privado**. Você pode personalizar ainda mais a visibilidade de imagens de contêiner privado.
+    - **Para {% data variables.product.prodname_ghe_cloud %} apenas:** Para permitir que os integrantes da organização criem imagens internas de contêiner visíveis apenas para outros integrantes da organização, clique em **Interno**. ![Opções de visibilidade para imagens de contêiner publicadas por integrantes da organização](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### Configurar a visibilidade de imagens de contêiner para uma organização
+
+Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver o pacote. Você pode conceder a usuários ou equipes diferentes funções de acesso para sua imagem de contêiner por meio das configurações de acesso.
+
+Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente.
+
+Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes públicos antes que você possa definir a visibilidade como pública. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. Em "Zona de Perigo", escolha uma configuração de visibilidade:
+    - Para tornar a imagem do contêiner visível para qualquer pessoa, clique em **Tornar pública**.
+    {% warning %}
+
+    **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente.
+
+    {% endwarning %}
+    - Para tornar a imagem do contêiner visível para uma seleção personalizada de pessoas, clique em **Tornar privada**. ![Opções de visibilidade do contêiner](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..b354fc5f48
--- /dev/null
+++ b/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+### Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to a container image using the command line
+
+1. No seu arquivo Docker, adicione esta linha, substituindo `PROPRIETÁRIO` e `REPO` pelas suas informações:
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ Por exemplo, se você é o usuário de `monalisa` e proprietário de `my-repo`, você adicionaria essa linha ao seu arquivo Docker:
+ ```shell
+ ETIQUETA org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ Para obter mais informações, consulte "[ETIQUETA](https://docs.docker.com/engine/reference/builder/#label)" na documentação oficial do Docker e "[Chaves de anotação pré-definidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" no repositório `opencontainers/image-spec`.
+
+2. Construa a sua imagem do contêiner. Este exemplo cria uma imagem do arquivo Docker no diretório atual e atribui o nome da imagem `hello_docker`.
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. Opcionalmente, revise os detalhes para a imagem do Docker que você deseja marcar.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Marque sua imagem Docker com o nome de imagem desejado e hospedagem de destino.
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  Por exemplo:
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  Por exemplo:
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
index e0ce4676ac..6db56f6522 100644
--- a/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
+++ b/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -112,9 +112,9 @@ Para obter mais informações sobre a mutação `deletePackageVersion`, consulte
 Você não pode excluir diretamente um pacote inteiro usando o GraphQL, mas se você excluir todas as versões de um pacote, o pacote não será mostrado em {% data variables.product.product_name %}.
 
 {% if currentVersion == "free-pro-team@latest" %}
-### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
+### Excluindo uma versão de pacote com escopo do usuário em {% data variables.product.prodname_dotcom %}
 
-To delete a specific version of a user-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps. To delete an entire package, see "[Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)."
+Para excluir uma versão específica de um pacote com escopo de usuário em {% data variables.product.prodname_dotcom %}, como para uma imagem Docker em `ghcr. o`, siga estas etapas. Para excluir um pacote inteiro, consulte "[Excluir todo um pacote com escopo do usuário em {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)".
 
 {% data reusables.package_registry.container-registry-beta %}
 
diff --git a/translations/pt-BR/content/packages/learn-github-packages/index.md b/translations/pt-BR/content/packages/learn-github-packages/index.md
index f4f5915104..61c91b058f 100644
--- a/translations/pt-BR/content/packages/learn-github-packages/index.md
+++ b/translations/pt-BR/content/packages/learn-github-packages/index.md
@@ -1,7 +1,7 @@
 ---
 title: Aprenda sobre o GitHub Pckages
 shortTitle: Aprenda sobre o GitHub Pckages
-intro: 'Você pode saber mais sobre o GitHub Packages, incluindo a publicação de novos pacotes em {% data variables.product.prodname_registry %}.'
+intro: 'You can find out more about using packages in GitHub, including publishing new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
   - /github/managing-packages-with-github-packages/publishing-and-managing-packages
@@ -17,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..ad2448b0f4
--- /dev/null
+++ b/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: Instalar um pacote
+intro: 'Você pode instalar um pacote do {% data variables.product.prodname_registry %} e usá-lo como uma dependência no seu próprio projeto.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Sobre a instalação do pacote
+
+Você pode pesquisar {% data variables.product.product_name %} para encontrar pacotes no {% data variables.product.prodname_registry %} que você pode instalar no seu próprio projeto. Para obter mais informações, consulte "[Pesquisar pacotes no {% data variables.product.prodname_registry %}](/github/searching-for-information-on-github/searching-for-packages)".
+
+Depois de encontrar um pacote, você pode ler a descrição e as instruções de instalação e utilização na página de pacotes.
+
+### Instalar um pacote
+
+Você pode instalar um pacote de {% data variables.product.prodname_registry %} usando qualquer {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}cliente de pacote compatível{% else %}tipo de pacote habilitado para a sua instância{% endif %}, seguindo as mesmas diretrizes gerais.
+
+1. Efetue a autenticação com {% data variables.product.prodname_registry %} usando as instruções para seu cliente de pacote. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. Instale o pacote usando as instruções para seu cliente de pacote.
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..de082602e2
--- /dev/null
+++ b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,133 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} é um serviço de hospedagem de pacotes de software que permite que você hospede seus pacotes de software de forma privada{% if currentVersion == "github-ae@latest" %} para usuários especificados ou internamente para a empresa{% else %}ou publicamente{% endif %} e use pacotes como dependências dos seus projetos.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Sobre o {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} is a package hosting service, fully integrated with {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combina seu código-fonte e pacotes em um só lugar para fornecer o gerenciamento integrado de permissões{% if currentVersion ! "github-ae@latest" %} e cobrança{% endif %}, para centralizar o desenvolvimento do software em {% data variables.product.product_name %}.
+
+Você pode integrar {% data variables.product.prodname_registry %} com as APIs de {% data variables.product.product_name %}, {% data variables.product.prodname_actions %} e webhooks para criar um fluxo de trabalho de ponta a ponta que inclui as suas soluções de código, CI e implantação.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. Para obter mais informações, consulte "[Visualizar pacotes](/packages/manage-packages/viewing-packages)".
+
+#### Overview of package permissions and visibility
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| Permissões                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |                                                                  |
+| {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |                                                                  |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| Visibilidade                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | {% data reusables.package_registry.public-or-private-packages %}
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Sobre a cobrança do {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".
+
+{% endif %}
+
+### Clientes e formatos compatíveis
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+O {% data variables.product.prodname_registry %} usa os comandos nativos de ferramentas de pacotes com os quais você já está familiarizado para publicar e instalar versões de pacote.
+#### Suporte para registros de pacotes
+
+| Linguagem  | Descrição                                                             | Formato do pacote                    | Cliente do pacote |
+| ---------- | --------------------------------------------------------------------- | ------------------------------------ | ----------------- |
+| JavaScript | Gerenciador de pacotes de nó                                          | `package.json`                       | `npm`             |
+| Ruby       | Gerenciador de pacotes de RubyGems                                    | `Gemfile`                            | `gem`             |
+| Java       | Ferramenta de gerenciamento de projetos e compreensão do Apache Maven | `pom.xml`                            | `mvn`             |
+| Java       | Ferramenta de automação do build Gradle para Java                     | `build.gradle` ou `build.gradle.kts` | `gradle`          |
+| .NET       | Gerenciamento de pacotes NuGet para .NET                              | `nupkg`                              | `dotnet` CLI      |
+| N/A        | Gerenciamento do contêiner do Docker                                  | `arquivo Docker`                     | `Docker`          |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**Observação:** O Docker não é compatível quando o isolamento de subdomínio está desativado.
+
+{% endnote %}
+
+Para obter mais informações sobre o isolamento de subdomínio, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)".
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### Autenticar-se no {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Gerenciar pacotes
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. Para obter mais informações, consulte o "[API de {% data variables.product.prodname_registry %}](/rest/reference/packages)".
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. Ou para pacotes com escopo de repositório, você pode excluir uma versão de um pacote privado usando o GraphQL.
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+Você pode excluir uma versão de um pacote privado na interface de usuário de {% data variables.product.product_name %} ou usando a API do GraphQL.
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+Você pode configurar webhooks para assinar eventos relacionados aos pacotes, como quando um pacote é publicado ou atualizado. Para obter mais informações, consulte o evento de webhook de "[`pacote`](/webhooks/event-payloads/#package)".
+
+### Entrar em contato com o suporte
+
+{% if currentVersion == "free-pro-team@latest" %}
+Se você tiver comentários ou solicitações de recursos para {% data variables.product.prodname_registry %}, use o [formulário de feedback para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages).
+
+Entre em contato com {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando o [nosso formulário de contato](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) se:
+
+* Você encontrar qualquer coisa que contradiga a documentação
+* Você encontra erros vagos ou pouco claros
+* Seu pacote publicado contém dados confidenciais, como violações do RGPD, chaves API ou informações de identificação pessoal
+
+{% else %}
+Se você precisar de suporte para {% data variables.product.prodname_registry %}, entre em contato com os administradores do seu site.
+
+{% endif %}
diff --git a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md
index cbeca9c876..06d54b0cb4 100644
--- a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md
+++ b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md
@@ -19,7 +19,7 @@ versions:
 
 Você pode ajudar as pessoas a entender e usar seu pacote fornecendo uma descrição e outros detalhes como, por exemplo, a instalação e instruções de uso na página do pacote. GitHub provides metadata for each version, such as the publication date, download activity, and recent versions. Para uma página de pacote de exemplo, veja [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
 
-{% data reusables.package_registry.public-or-private-packages %} Um repositório pode conter mais de um pacote. Para evitar confusão, certifique-se de que o README e a descrição fornecem informações claras sobre cada pacote.
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. Para evitar confusão, certifique-se de que o README e a descrição fornecem informações claras sobre cada pacote.
 
 {% if currentVersion == "free-pro-team@latest" %}
 Se uma nova versão de um pacote corrigir uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório.
@@ -30,10 +30,10 @@ Se uma nova versão de um pacote corrigir uma vulnerabilidade de segurança, voc
 
 Você pode publicar um pacote em {% data variables.product.prodname_registry %} usando qualquer tipo de {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}cliente de pacote compatível{% else %}tipo de pacote habilitado para a sua instância{% endif %}, seguindo as mesmas diretrizes gerais.
 
-1. Crie ou use um token de acesso existente com os escopos apropriados para a tarefa que você deseja realizar. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+1. Crie ou use um token de acesso existente com os escopos apropriados para a tarefa que você deseja realizar. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 2. Efetue a autenticação em {% data variables.product.prodname_registry %} usando seu token de acesso e as instruções para seu cliente do pacote.
 3. Publique o pacote usando as instruções do seu cliente de pacote.
 
-Para obter instruções específicas para o seu cliente de pacotes, consulte "[Usar o {% data variables.product.prodname_registry %} com o ecossistema do seu projeto](/packages/using-github-packages-with-your-projects-ecosystem)".
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
 
-Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte “[Visualizar pacotes](/packages/publishing-and-managing-packages/viewing-packages).”
+Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Visualizar pacotes](/packages/learn-github-packages/viewing-packages)".
diff --git a/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md b/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..632184d64a
--- /dev/null
+++ b/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: Visualizar pacotes
+intro: É possível ver informações sobre pacotes publicados em um repositório e limitar os resultados por organização ou usuário.
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### Sobre a visualização de pacotes
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### Visualizar pacotes de um repositório
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Visualizar pacotes de uma organização
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. No nome da sua organização, clique em {% octicon "package" aria-label="The package icon" %} **Pacotes**.
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Visualizar seus pacotes
+
+You can find and view any package you've published across all organizations and repositories.
+
+{% data reusables.profile.access_profile %}
+2. No topo da página de perfil, na navegação principal, clique em **Pacotes**. ![Aba Project (Projeto)](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Leia mais
+
+- "[Procurar pacotes](/github/searching-for-information-on-github/searching-for-packages)"
diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..db022b22ec
--- /dev/null
+++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: About GitHub Packages and GitHub Actions
+intro: Learn the fundamentals of managing packages through your {% data variables.product.prodname_actions %} workflows.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..1d243733c6
--- /dev/null
+++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: Example workflows for publishing a package
+intro: 'To help you get started with your own custom workflows, review some example workflows for publishing packages.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+You can find example workflows in "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
+
+  - [Publicar pacotes do Node.js](/actions/guides/publishing-nodejs-packages)
+  - [Publicar imagens do Docker](/actions/guides/publishing-docker-images)
+  - [Publicar pacotes Java com Maven](/actions/guides/publishing-java-packages-with-maven)
+  - [Publicar pacotes Java com Gradle](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..790a661916
--- /dev/null
+++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: Managing GitHub packages using GitHub Actions workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'You can safely publish and consume packages by building custom workflows that can also build, test, and deploy your code.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..22870a8384
--- /dev/null
+++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,450 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'É possível configurar um fluxo de trabalho no {% data variables.product.prodname_actions %} para publicar ou instalar automaticamente um pacote do {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### Sobre {% data variables.product.prodname_registry %} com {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)".
+
+Você pode estender os recursos de CI e CD do seu repositório publicando ou instalando pacotes como parte do seu fluxo de trabalho.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+Para um exemplo de autenticação, consulte "[Efetuar a autenticação com o {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)".
+
+{% endif %}
+
+#### Efetuar a autenticação nos registros do pacote em {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}Se você deseja que o fluxo de trabalho efetue a autenticação em {% data variables.product.prodname_registry %} para acessar um registro de pacotes diferentes do {% data variables.product.prodname_container_registry %} em {% data variables.product.product_name %}, {% else %}Para efetuar a autenticação nos registros de pacotes no {% data variables.product.product_name %},{% endif %} recomendamos usar o `GITHUB_TOKEN` que {% data variables.product.product_name %} cria automaticamente para o seu repositório quando você habilita {% data variables.product.prodname_actions %} em vez de um token de acesso pessoal para autenticação. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+
+Você pode fazer referência ao `GITHUB_TOKEN` no seu arquivo de fluxo de trabalho usando o contexto {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)".
+
+### Sobre permissões e acesso de pacote para pacotes pertencentes ao repositório
+
+{% note %}
+
+**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.
+
+{% endnote %}
+
+Quando você habilita o GitHub Actions, o GitHub instala um aplicativo GitHub no repositório. O segredo `GITHUB_TOKEN` é um token de acesso de instalação do aplicativo GitHub. Você pode usar o token de acesso de instalação para efetuar a autenticação em nome do aplicativo GitHub instalado no seu repositório. As permissões do token são restritas ao repositório do fluxo de trabalho. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)".
+
+{% data variables.product.prodname_registry %} permite que você faça push e pull de pacotes por meio do `GITHUB_TOKEN` disponível para um fluxo de trabalho de {% data variables.product.prodname_actions %}.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Sobre permissões e acesso de pacote para {% data variables.product.prodname_container_registry %}
+
+O {% data variables.product.prodname_container_registry %} (`ghcr.io`) permite aos usuários criar e administrar contêineres como recursos independentes no nível da organização. Os contêineres podem pertencer a uma conta de usuário ou organização e você pode personalizar o acesso a cada um dos seus contêineres separadamente das permissões de repositório.
+
+Todos os workflows que acessam o {% data variables.product.prodname_container_registry %} devem usar o `GITHUB_TOKEN` em vez de um token de acesso pessoal. Para obter mais informações sobre as melhores práticas de segurança, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)".
+
+### Configurações padrão de permissões e acesso para contêineres modificados por meio de fluxos de trabalho
+
+Ao criar, instalar, modificar ou excluir um contêiner por meio de um fluxo de trabalho, existem algumas configurações padrão de permissão e acesso para garantir que os administradores tenham acesso ao fluxo de trabalho. Você também pode ajustar estas configurações de acesso.
+
+Por exemplo, por padrão, se um fluxo de trabalho cria um contêiner usando o `GITHUB_TOKEN`:
+- O contêiner herdará o modelo de visibilidade e permissões do repositório onde o fluxo de trabalho é executado.
+- Os administradores do repositório onde o fluxo de trabalho é executado tornam-se os administradores do contêiner depois que o contêiner é criado.
+
+Estes são outros exemplos de como as permissões padrão funcionam para fluxos de trabalho que gerenciam pacotes.
+
+| Tarefa de fluxo de trabalho de {% data variables.product.prodname_actions %} | Acesso e permissões padrão                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Faça o download de um contêiner existente                                    | - Se o contêiner for público, qualquer fluxo de trabalho em execução em qualquer repositório poderá fazer o download do container. <br> - Se o contêiner for interno, todos os fluxos de trabalho em execução em qualquer repositório pertencente à conta corporativa poderão fazer o download do contêiner. Para organizações pertencentes a empresas, você poderá ler qualquer repositório na empresa <br> - Se o contêiner for privado, somente fluxos de trabalho executados em repositórios que recebem permissões de leitura nesse contêiner podem fazer o download do container. <br> |
+| Faça o upload de uma nova versão para um contêiner existente                 | - Se o contêiner for privado, interno ou público, somente fluxos de trabalho executados em repositórios que recebem permissões de gravação nesse contêiner podem fazer o upload de novas versões para o container.                                                                                                                                                                                                                                                                                                                                                                                             |
+| Excluir um contêiner ou versões de um contêiner                              | - Se o recipiente for privado, interno ou público, somente fluxos de trabalho executados em repositórios que recebem permissão de exclusão pode excluir versões existentes do container.                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+Você também pode ajustar o acesso a contêineres de uma forma mais granular ou ajustar alguns dos comportamentos padrão de permissões. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publicar um pacote usando uma ação
+
+Você pode usar {% data variables.product.prodname_actions %} para publicar automaticamente pacotes como parte do fluxo de integração contínua (CI). Esta abordagem da implantação contínua (CD) permite que você automatize a criação de novas versões do pacote, se o código atender aos seus padrões de qualidade. Por exemplo, você pode criar um fluxo de trabalho que executa testes CI toda vez que um desenvolvedor faz push do código para um branch específico. Se os testes passarem, o fluxo de trabalho poderá publicar uma nova versão do pacote em {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+O exemplo a seguir demonstra como você pode usar {% data variables.product.prodname_actions %} para criar e testar seu aplicativo e, em seguida, criar automaticamente uma imagem do Docker e publicá-la em {% data variables.product.prodname_registry %}:
+
+- Crie um novo arquivo de fluxo de trabalho no repositório (como `.github/workflows/deploy-image.yml`) e adicione o YAML a seguir:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  As configurações relevantes são explicadas na seguinte tabela: <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configura o fluxo de trabalho <code>Criar e publicar um pacote</code> para ser executado toda vez que uma alteração é enviada para o branch denominado <code>versão</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    Este trabalho instala o NPM e o usa para criar o aplicativo.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Este trabalho usa <code>teste do npm</code> para testar o código. O comando <code>needs: run-npm-build</code> torna esse trabalho dependente do trabalho <code>run-npm-build</code>.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Cria uma nova etapa denominada <code>Build container image</code>. Esta etapa é executada como parte do trabalho <code>build-and-push-image</code>. O comando <code>needs: run-npm-test</code> torna essa tarefa dependente do trabalho <code>run-npm-test</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Usa a ação <code>build-push-action</code> do Docker para criar a imagem com base no <code>arquivo Docker</code> do seu repositório. Se a criação for bem-sucedida, ela faz p push da imagem para {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Envia os parâmetros necessários para a ação </code>build-push-action<code>. Isto é definido nas linhas subsequentes.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Define a conta de usuário que publicará os pacotes. Uma vez publicados, os pacotes pertencem à conta definida aqui.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Define a senha usada para acessar {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Define o registro que hospedará os pacotes resultantes. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace <code>YOUR-HOSTNAME</code> with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use <code>ghcr.io</code> as the hostname.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Define qual repositório hospedará o pacote resultante e define o nome do pacote publicado. Substitui <code>octo-image</code> pelo nome que você deseja para o seu pacote.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Marca o pacote publicado com os primeiros sete caracteres do SHA do commit. Por exemplo, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags o pacote publicado com a referência do Git. Este pode ser o nome do branch usado para criar o pacote.
+  </td>
+  </tr>
+  </table>
+
+- Este novo fluxo de trabalho será executado automaticamente toda vez que você fizer uma alteração em uma `versão` nomeada do branch no repositório. Você pode visualizar o progresso na aba **Ações**.
+- Alguns minutos após a conclusão do fluxo de trabalho, o novo pacote ficará visível no seu repositório. Para encontrar seus pacotes disponíveis, consulte "[Visualizar os pacotes de um repositório](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)".
+
+
+### Instalar um pacote usando uma ação
+
+Você pode instalar pacotes como parte de seu fluxo de CI usando o {% data variables.product.prodname_actions %}. Por exemplo, você poderia configurar um fluxo de trabalho para que sempre que um desenvolvedor fizesse push do código para um pull request, o fluxo de trabalho resolveria as dependências, fazendo o download e instalando pacotes hospedados pelo {% data variables.product.prodname_registry %}. Em seguida, o fluxo de trabalho pode executar testes de CI que exigem as dependências.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Upgrading a workflow that accesses `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. Para obter mais informações sobre as melhores práticas de segurança, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)".
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Abra o arquivo do seu fluxo de trabalho. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
diff --git a/translations/pt-BR/content/packages/quickstart.md b/translations/pt-BR/content/packages/quickstart.md
index 732eef43e2..45e6266a4f 100644
--- a/translations/pt-BR/content/packages/quickstart.md
+++ b/translations/pt-BR/content/packages/quickstart.md
@@ -71,7 +71,10 @@ Neste guia, você criará um fluxo de trabalho de {% data variables.product.prod
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -95,7 +98,7 @@ Neste guia, você criará um fluxo de trabalho de {% data variables.product.prod
 
 ### Visualizar o seu pacote publicado
 
-Os pacotes são publicados no nível de repositório. Você pode visualizar todos os pacotes em um repositório e procurar um pacote específico.
+You can view all of the packages you have published.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ Os pacotes são publicados no nível de repositório. Você pode visualizar todo
 
 ### Instalar um pacote publicado
 
-Agora que você publicou o pacote, você vai querer usá-lo como uma dependência nos seus projetos. Para obter mais informações, consulte "[Configurar npm para uso com o {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)".
+Agora que você publicou o pacote, você vai querer usá-lo como uma dependência nos seus projetos. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
 
 ### Próximas etapas
 
-O fluxo de trabalho básico que você acabou de adicionar é executado sempre que uma nova versão for criada no seu repositório. Mas este é apenas o início do que você pode fazer com {% data variables.product.prodname_registry %}. Pode publicar o seu pacote em vários registros com um único fluxo de trabalho, acionar o fluxo de trabalho para ser executado em eventos diferentes, como um pull request mesclado, gerenciar contêineres, entre outros.
+O fluxo de trabalho básico que você acabou de adicionar é executado sempre que uma nova versão for criada no seu repositório. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. Pode publicar o seu pacote em vários registros com um único fluxo de trabalho, acionar o fluxo de trabalho para ser executado em eventos diferentes, como um pull request mesclado, gerenciar contêineres, entre outros.
 
 Combinar {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seguir as próximas etapas com {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}:
 
 - "[Aprenda sobre {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" para obter um tutorial aprofundado no GitHub Packages
 - "[Aprenda sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obter um tutorial aprofundado no GitHub Actions
-- "[Guias](/packages/guides)" para casos e exemplos específicos de uso
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..1e2c459463
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: Enabling improved container support with the Container registry
+intro: 'To use the {% data variables.product.prodname_container_registry %}, you must enable it for your user or organization account.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. Durante o beta, o armazenamento e a banda larga são grátis. Para obter mais informações, consulte "[Introdução a {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)".
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your personal account
+
+Once the {% data variables.product.prodname_container_registry %} is enabled for your personal user account, you can publish containers to the {% data variables.product.prodname_container_registry %} owned by your user account.
+
+To use the {% data variables.product.prodname_container_registry %} within an organization, the organization owner must enable the feature for organization members.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. À esquerda, selecione "Suporte ao contêiner aprimorado" e, em seguida, clique em **Habilitar**. ![Suporte ao contêiner aprimorado](/assets/images/help/settings/improved-container-support.png)
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your organization account
+
+Before organization owners or members can publish container images to the {% data variables.product.prodname_container_registry %}, an organization owner must enable the feature preview for the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. À esquerda, clique em **Pacotes**.
+5. Em "Melhorar suporte ao container", selecione "Suporte ao contêiner aprimorado" e clique em **Salvar**. ![Opção de habilitar suporte de registro do contêiner e botão de salvar](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. Em "Criação de contêiner", escolha se deseja permitir a criação de imagens públicas, privadas ou internas de contêineres.
+    - To enable organization members to create public container images, select **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, select **Private**. Você pode personalizar ainda mais a visibilidade de imagens de contêiner privado. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, select **Internal**. ![Opções de visibilidade para imagens de contêiner publicadas por integrantes da organização](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/index.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..2d63b2b150
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with a GitHub Packages registry
+shortTitle: Working with a GitHub Packages registry
+intro: 'Learn how to use a supported {% data variables.product.prodname_registry %} registry.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### Índice
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..c676e39eae
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,124 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- Armazenar imagens de contêiner na sua conta de organização e usuário, em vez de um repositório.
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- Acessar imagens de contêineres públicos anonimamente.
+
+|                      | Docker registry                                                                                                                                                                                                                                         | {% data variables.product.prodname_container_registry %}
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Locais de hospedagem | You can host multiple Docker images in one repository.                                                                                                                                                                                                  | Você pode hospedar várias imagens de contêiner em uma organização ou conta de usuário.                                                                                                                    |
+| Permissões           | Each image inherits the permissions of the repository where the image is hosted. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | Para cada imagem de container, você pode escolher o nível de acesso que os outros têm. As permissões para acesso a imagens do contêiner são separadas da sua organização e das permissões do repositório. |
+ Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. Uma imagem privada de contêiner só é visível para pessoas e equipes às quais é fornecido acesso na sua organização. Qualquer pessoa pode ver uma imagem pública de contêiner. | Anonymous access    | N/A | You can access public container images anonymously. Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### Alterações de cobrança
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. Para obter mais informações, consulte "[Sobre a cobrança para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".
+
+### Alterações de domínio
+
+O domínio para o {% data variables.product.prodname_container_registry %} é `ghcr.io`.
+
+| Registro                                                          | Exemplo de URL                                      |
+| ----------------------------------------------------------------- | --------------------------------------------------- |
+| Registro Docker de {% data variables.product.prodname_registry %} | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` |
+| {% data variables.product.prodname_container_registry %}        | `ghcr.io/OWNER/IMAGE_NAME`                          |
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+Você deverá efetuar a autenticação no {% data variables.product.prodname_container_registry %} com a URL de base `ghcr.io`. Recomendamos criar um novo token de acesso para usar o {% data variables.product.prodname_container_registry %}.
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Fazer a migração de uma imagem do Docker usando a CLI do Docker
+
+Para mover imagens do Docker que você hospeda no registro do Docker do {% data variables.product.prodname_registry %}, você deve republicar as imagens para {% data variables.product.prodname_container_registry %}. Recomendamos republicar as imagens do Docker existentes usando a linha de comando na sua máquina local.
+
+1. Faça o login no registro do Docker usando um PAT temporário com pelo menos o escopo de `read:packages`. Este PAT só será usado para fazer o login no registro do Docker para puxar imagens e poderá ser excluído posteriormente.
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. Puxe para baixo a imagem que você gostaria de migrar, substituindo o PROPRIETÁRIO pelo nome do usuário ou conta de organização proprietária do repositório, REPOSITÓRIO pelo nome do repositório que contém seu projeto, IMAGE_NAME pelo o nome do pacote ou imagem, VERSÃO pela tag para a imagem que você deseja instalar. Por exemplo, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` move a tag mais recente da imagem `octoshift/octoshift` na organização octo-org.
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. Remarque a imagem com o novo domínio e um novo nome de imagem. Para obter mais informações, consulte "[Tag do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação Docker. Use a mesma URL que você usou na etapa anterior para a URL FONTE. Substitua TARGET_OWNER pelo usuário ou organização para o qual você está migrando a imagem do contêiner e substitua TARGET_IMAGE_NAME pelo novo nome de imagem de {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. Faça login no novo {% data variables.product.prodname_container_registry %}. Recomendamos criar um novo PAT limitado aos escopos `read:packages` e `write: packages` já que você não precisa mais do escopo `repositório` e seu PAT anterior pode não ter o escopo `write:packages`.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. Faça push da sua imagem re-etiquetada para o {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+Se tiver um fluxo de trabalho de {% data variables.product.prodname_actions %} que usa uma imagem do Docker do registro Docker do {% data variables.product.prodname_registry %}, você deverá atualizar seu fluxo de trabalho para {% data variables.product.prodname_container_registry %} para permitir acesso anônimo para imagens públicas de contêiner, permissões de acesso refinado e melhor compatibilidade de armazenamento e largura de banda para contêineres.
+
+1. Migre as suas imagens do Docker para o novo {% data variables.product.prodname_container_registry %} em `ghcr.io`. Por exemplo, consulte "[Migrar uma imagem do Docker usando a CLI do Docker](#migrating-a-docker-image-using-the-docker-cli)".
+
+2. No seu arquivo de fluxo de trabalho do {% data variables.product.prodname_actions %}, atualize a URL do pacote de `https://docker.pkg.github.com` para `ghcr.io`.
+
+3. Adicione seu novo token de acesso de autenticação pessoal (PAT) de {% data variables.product.prodname_container_registry %} como um segredo do GitHub Action. The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
+
+4. No seu arquivo de fluxo de trabalho de {% data variables.product.prodname_actions %} atualize a autenticação do PAT substituindo o seu PAT do registro do Docker ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) por uma nova variável para o seu PAT de {% data variables.product.prodname_container_registry %}, como, por exemplo, {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}.
+
+#### Exemplo de fluxo de trabalho atualizado
+
+Se parte de seu fluxo de trabalho acessou uma imagem do Docker hospedada pelo registro Docker dessa forma:
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+Você deverá atualizar o seu fluxo de trabalho com a nova URL de {% data variables.product.prodname_container_registry %} e PAT dessa forma:
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..90181978d9
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Working with the Apache Maven registry
+intro: 'Você pode configurar o Apache Maven para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto Java.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Autenticar-se no {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Efetuando a autenticação com um token de acesso pessoal
+
+{% data reusables.package_registry.required-scopes %}
+
+Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o Apache Maven editando seu arquivo *~/.m2/settings.xml* para incluir seu token de acesso pessoal. Criar um novo arquivo *~/.m2/settings.xml*, caso não exista um.
+
+Na etiqueta `servidores`, adicione uma etiqueta `servidor` secundário com um `Id`, substituindo *USERNAME* pelo o seu nome de usuário {% data variables.product.prodname_dotcom %} e *Token* pelo seu token de acesso pessoal.
+
+Na etiqueta `repositórios`, configure um repositório mapeando o `id` do repositório com o `id` que você adicionou na etiqueta `servidor` que contém as suas credenciais. Replace {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas.
+
+Se desejar interagir com vários repositórios, você poderá adicionar cada repositório para separar os `repositório` secundários na etiqueta `repositórios`, mapeando o `ID` de cada um com as credenciais na etiqueta `servidores`.
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio habilitado:
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio desabilitado:
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### Publicar um pacote
+
+O {% data reusables.package_registry.default-name %} por exemplo, o {% data variables.product.prodname_dotcom %} publicará um pacote denominado `com.example:test` em um repositório denominado`OWNER/test`.
+
+Caso queira publicar vários pacotes no mesmo repositório, você poderá incluir a URL do repositório no `<distributionManagement>` elemento do arquivo *pom.xml*. O {% data variables.product.prodname_dotcom %} fará a correspondência do repositório com base nesse campo. Como o nome do repositório também faz parte do elemento `distributionManagement`, não há etapas adicionais para publicar vários pacotes no mesmo repositório.
+
+Para obter mais informações sobre como criar um pacote, consulte a [documentação maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+
+1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+
+  Se sua instância tiver o isolamento de subdomínio habilitado:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. Publique o pacote.
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Instalar um pacote
+
+Para instalar um pacote de Apache Maven a partir do {% data variables.product.prodname_registry %}, edite o arquivo *pom.xml* para incluir o pacote como uma dependência. Se você desejar instalar pacotes de mais de um repositório, adicione uma etiqueta de `repositório` para cada um. Para obter mais informações sobre como usar o arquivo *pom.xml* no seu projeto, consulte "[Introdução a POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" na documentação do Apache Maven.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Adicione as dependências do pacote ao elemento `dependências` do arquivo *pom.xml* do seu projeto, substituindo `com.exemplo:test` pelo seu pacote.
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. Instale o pacote.
+
+  ```shell
+  $ mvn install
+  ```
+
+### Leia mais
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..85adf2c92f
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://ghcr.io`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About {% data variables.product.prodname_container_registry %} support
+
+To push and pull container images, an organization admin or the owner of a personal account must enable the {% data variables.product.prodname_container_registry %}. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+When installing or publishing a Docker image, the Container registry supports foreign layers, such as Windows images.
+
+O {% data variables.product.prodname_container_registry %} é atualmente compatível com os seguintes formatos de imagem do contêiner:
+
+* [Docker Image Manifest V2, Modelo 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Especificações de Open Container Initiative (OCI)](https://github.com/opencontainers/image-spec)
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Fazer push das imagens do contêiner
+
+Este exemplo faz push da versão mais recente de `IMAGE-NAME`.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+Este exemplo faz push da versão `2.5` da imagem.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+Ao publicar um pacote pela primeira vez a visibilidade-padrão será privada. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+### Fazer pull das imagens de contêiner
+
+#### Pull por resumo
+
+Para garantir que você esteja sempre usando a mesma imagem, você pode especificar a versão exata da imagem de contêiner que você deseja fazer pull pelo valor do SHA do `resumo`.
+
+1. Para encontrar o valor do SHA do resumo, use `docker inspect` or `docker pull` e copie o valor de SHA após `Digest:`
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. Remova a imagem localmente, conforme necessário.
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+3. Faça pull da imagem do contêiner com `@YOUR_SHA_VALUE` após o nome da imagem.
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### Pull por nome
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### Pull por nome e versão
+
+Exemplo de CLI do Docker mostrando uma imagem extraída pelo seu nome e a tag de versão `1.14.1`:
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### Pull por nome e última versão
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### Criar imagens de contêiner
+
+Este exemplo cria a imagem `hello_docker`:
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### Marcar imagens de contêiner
+
+1. Encontre o ID da imagem do Docker que você deseja marcar.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. Marque a sua imagem do Docker usando o ID da imagem, o nome da imagem desejada e a hospedagem de destino.
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..789c0f234a
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,263 @@
+---
+title: Working with the Docker registry
+intro: 'You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+Antes de poder usar o registro do Docker no {% data variables.product.prodname_registry %}, o administrador do site para {% data variables.product.product_location %} deve habilitar o suporte do Docker e o isolamento do subdomínio para a sua instância. Para obter mais informações, consulte "[Gerenciar pacotes do GitHub para a sua empresa](/enterprise/admin/packages)".
+
+{% endif %}
+
+### Autenticar-se no {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Efetuando a autenticação com um token de acesso pessoal
+
+{% data reusables.package_registry.required-scopes %}
+
+Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} usando o comando de login do `docker`.
+
+Para manter suas credenciais seguras, recomendamos que você salve seu token de acesso pessoal em um arquivo local no seu computador e use o sinalizador `--password-stdin` do Docker que lê o seu token a partir de um arquivo local.
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Se sua instância tem o isolamento de subdomínio habilitado:
+{% endif %}
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login docker.HOSTNAME -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Se sua instância tem o isolamento de subdomínio desabilitado:
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+Par usar este exemplo de comando de login, substitua `USERNAME` pelo seu nome de usuário de {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, `HOSTNAME` pela URL para {% data variables.product.product_location %},{% endif %} e `~/TOKEN.txt` pelo caminho do arquivo para oseu token de acesso pessoal para {% data variables.product.product_name %}.
+
+Para obter mais informações, consulte "[Login do Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)".
+
+### Publicar uma imagem
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**Observação:** Os nomes de imagem devem usar apenas letras minúsculas.
+
+{% endnote %}
+
+O {% data variables.product.prodname_registry %} aceita várias imagens do Docker de nível superior por repositório. Um repositório pode ter qualquer número de tags de imagem. Você poderá conhecer uma publicação de serviço degradada ou instalar imagens do Docker com tamanho superior a 10 GB. As camadas são limitadas em 5 GB cada. Para obter mais informações, consulte "[Tag do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação Docker.
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. Determine o nome da imagem e o ID da sua imagem do docker usando `imagens do docker`.
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Se sua instância tem o isolamento de subdomínio habilitado:
+  {% endif %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Se sua instância tem o isolamento de subdomínio desabilitado:
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Se sua instância tem o isolamento de subdomínio habilitado:
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Se sua instância tem o isolamento de subdomínio desabilitado:
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. Publicar a imagem no {% data variables.product.prodname_registry %}.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Se sua instância tem o isolamento de subdomínio habilitado:
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  Se sua instância tem o isolamento de subdomínio desabilitado:
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **Observação:** Você deve enviar sua imagem usando `IMAGE_NAME:VERSION` e não `IMAGE_NAME:SHA`.
+
+  {% endnote %}
+
+#### Exemplo de publicação de uma imagem do Docker
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Esses exemplos assumem que sua instância tem o isolamento de subdomínio habilitado.
+{% endif %}
+
+Você pode publicar a versão 1.0 da imagem de `monalisa` para o repositório `octocat/octo-app` usando um ID de imagem.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+Você pode publicar uma nova imagem do Docker pela primeira vez e nomeá-la como `monalisa`.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Faça push da imagem no {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### Fazer o download de uma imagem
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+Você pode usar o comando `docker pull` para instalar uma imagem do docker a partir de {% data variables.product.prodname_registry %}, substituindo *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* pelo nome do repositório que contém seu projeto, *IMAGE_NAME* pelo nome do pacote ou da imagem,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* com o nome de host de {% data variables.product.product_location %}, {% endif %} e *TAG_NAME* pela tag para a imagem que você deseja instalar.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Se sua instância tem o isolamento de subdomínio habilitado:
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+Se sua instância tem o isolamento de subdomínio desabilitado:
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**Nota:** Você deve fazer pull da imagem usando `IMAGE_NAME:VERSION` e não usar `IMAGE_NAME:SHA`.
+
+{% endnote %}
+
+### Leia mais
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..cec519498e
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Autenticar-se no {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### Efetuando a autenticação com um token de acesso pessoal
+
+{% data reusables.package_registry.required-scopes %}
+
+Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com Gradle usando Gradle Groovy ou Kotlin DSL e editando o seu arquivo *build.gradle* (Gradle Groovy) ou o arquivo *build.gradle.kts* (Kotlin DSL) para incluir seu token de acesso pessoal. Também é possível configurar o Gradle Groovy e o Kotlin DSL para reconhecer um único pacote ou vários pacotes em um repositório.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Substitua *REGISTRY-URL* pela URL do registro do Maven para a sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `maven.HOSTNAME`. Se sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/maven`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %}.
+{% elsif currentVersion == "github-ae@latest" %}
+Substitua *URL REGISTRA-* pela URL para o registro Maven da sua empresa, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.
+{% endif %}
+
+Substitua *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %} *TOKEN* pelo seu token de acesso pessoal, *REPOSITÓRIO* pelo nome do repositório que contém o pacote que você deseja publicar, e *PROPRIETÁRIO* pelo nome do usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas.
+
+{% note %}
+
+**Observação:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Por exemplo, consulte "[Configuraro Apache Maven para uso com {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)".
+
+{% endnote %}
+
+##### Exemplo de uso do Gradle Groovy para um único pacote em um repositório
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### Exemplo de uso do Gradle Groovy para vários pacotes no mesmo repositório
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### Exemplo de uso do Kotlin DSL para um único pacote no mesmo repositório
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### Exemplo de uso do Kotlin DSL para vários pacotes no mesmo repositório
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            register<MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+### Publicar um pacote
+
+{% data reusables.package_registry.default-name %} Por exemplo, {% data variables.product.prodname_dotcom %} publicará um pacote denominado `com.example.test` no repositório `OWNER/test` {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Depois de criar seu pacote, você poderá publicá-lo.
+
+  ```shell
+   $ gradle publish
+  ```
+
+### Instalar um pacote
+
+Você pode instalar um pacote adicionando-o como uma dependência ao seu projeto. Para obter mais informações, consulte "[Declarar dependências](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" na documentação do Gradle.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Adicione as dependências do pacote ao seu arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (arquivo de Kotlin DSL).
+
+  Exemplo do uso do Gradle Groovy:
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  Exemplo de uso do Kotlin DSL:
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. Adicione o plugin do maven ao seu arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (arquivo Kotlin DSL).
+
+  Exemplo do uso do Gradle Groovy:
+  ```shell
+  plugins {
+      id 'maven'
+  }
+  ```
+  Exemplo de uso do Kotlin DSL:
+  ```shell
+  plugins {
+      `maven`
+  }
+  ```
+
+  3. Instale o pacote.
+
+  ```shell
+  $ gradle install
+  ```
+
+### Leia mais
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..dbee971196
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,218 @@
+---
+title: Working with the npm registry
+intro: 'Você pode configurar o npm para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto npm.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Limites para versões publicadas do npm
+
+Se você publicar mais de 1.000 versões de pacote de npm até {% data variables.product.prodname_registry %}, você poderá ver problemas de performance e tempo-limite que ocorrem durante o uso.
+
+No futuro, para melhorar o desempenho do serviço, você não será capaz de publicar mais de 1.000 versões de um pacote em {% data variables.product.prodname_dotcom %}. Todas as versões publicadas antes de atingir esse limite serão legíveis.
+
+Se você atingir este limite, considere excluir versões de pacote ou entre em contato com o suporte para obter ajuda. Quando este limite for aplicado, a nossa documentação será atualizada com uma forma de contornar este limite. Para obter mais informações, consulte "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}" ou "[Entrar em contato com o suporte](/packages/learn-github-packages/about-github-packages#contacting-support)."
+
+{% endif %}
+
+### Autenticar-se no {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Efetuando a autenticação com um token de acesso pessoal
+
+{% data reusables.package_registry.required-scopes %}
+
+Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o npm editando seu arquivo *~/.npmrc* por usuário para incluir o seu token de acesso pessoal ou fazer o login no npm na linha de comando usando seu nome de usuário e token de acesso pessoal.
+
+Para efetuar a autenticação adicionando seu token de acesso pessoal ao seu arquivo *~/.npmrc*, edite o arquivo *~/.npmrc* para o seu projeto incluir a seguinte linha, substituindo {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}*HOSTNAME* pelo nome de host de {% data variables.product.product_location %} e {% endif %}*TOKEN* pelo seu token de acesso pessoal. Crie um novo arquivo *~/.npmrc* se um não existir.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio habilitado:
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio desabilitado:
+
+```shell
+$ npm login --registry=https://npm.pkg.github.com
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+Para efetuar a autenticação conectado no npm, use o comando `npm login` , substituindo o *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, o *TOKEN* pelo seu token de acesso pessoal e *PUBLIC-EMAIL-ADDRESS* pelo seu endereço de e-mail.
+
+Se {% data variables.product.prodname_registry %} não é seu registro de pacote padrão para usar npm e você deseja usar o comando `npm audit` , recomendamos que você use o sinalizador `--scope` com o proprietário do pacote quando você efetuar a autenticação no {% data variables.product.prodname_registry %}.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio habilitado:
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio desabilitado:
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### Publicar um pacote
+
+{% note %}
+
+**Nota:** Os nomes dos pacotes e escopos só devem usar letras minúsculas.
+
+{% endnote %}
+
+Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório {% data variables.product.prodname_dotcom %} que você especificar no campo nome do arquivo *package.json*. Por exemplo, você publicaria um pacote denominado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Você pode adicionar um resumo da página de listagem do pacote incluindo um arquivo *README.md* no diretório do seu pacote. Para obter mais informações, consulte "[Trabalhando com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" e "[Como criar Módulos de Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" na documentação do npm.
+
+Você pode publicar vários pacotes no mesmo repositório do {% data variables.product.prodname_dotcom %} incluindo um campo de `URL` no arquivo *package.json*. Para obter mais informações, consulte "[Publicar vários pacotes no mesmo repositório](#publishing-multiple-packages-to-the-same-repository)".
+
+É possível definir o mapeamento do escopo para o seu projeto usando um arquivo local *.npmrc* no projeto ou usando a opção `publishConfig` em *package.json*. {% data variables.product.prodname_registry %} só é compatível com pacotes npm com escopo definido. Pacotes com escopo têm nomes no formato `@owner/name`. Os pacotes com escopo sempre começam pelo símbolo `@`. Talvez seja necessário atualizar o nome no *package.json* para usar o nome com escopo. Por exemplo, `"name": "@codertocat/hello-world-npm"`.
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### Publicar um pacote usando o arquivo *.npmrc* local
+
+Você pode usar um arquivo *.npmrc* para configurar o mapeamento do escopo para o seu projeto. No arquivo *.npmrc*, use a URL e o proprietário da conta de {% data variables.product.prodname_registry %} para que {% data variables.product.prodname_registry %} saiba onde rotear as solicitações de pacotes. O uso de um arquivo *.npmrc* impede que outros desenvolvedores publiquem acidentalmente o pacote no npmjs.org em vez de {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Verifique o nome do pacote no *package.json* do seu projeto. O campo `name` (nome) deve conter o escopo e o nome do pacote. Por exemplo, se o pacote for chamado de "test" e você estiver publicando na organização "My-org" do {% data variables.product.prodname_dotcom %}, o campo `name` (nome) do seu *package.json* deverá ser `@my-org/test`.
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### Publicar um pacote usando o `publishConfig` no arquivo *package.json*
+
+Você pode usar o elemento `publishConfig` no arquivo *package.json* para especificar o registro onde você quer o pacote publicado. Para obter mais informações, consulte "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação npm.
+
+1. Edite o arquivo *package.json* do seu pacote e inclua uma entrada `publishConfig`.
+  {% if enterpriseServerVersions contains currentVersion %}
+  Se sua instância tem o isolamento de subdomínio habilitado:
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  Se sua instância tem o isolamento de subdomínio desabilitado:
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### Publicar vários pacotes no mesmo repositório
+
+Para publicar vários pacotes no mesmo repositório, você pode incluir a URL do repositório do {% data variables.product.prodname_dotcom %} no campo `repositório` do arquivo *package.json* para cada pacote.
+
+Para garantir que a URL do repositório esteja correta, substitua REPOSITÓRIO pelo nome do repositório que contém o pacote que você deseja publicar, e o PROPRIETÁRIO pelo nome de usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório.
+
+O {% data variables.product.prodname_registry %} corresponderá ao repositório baseado na URL, em vez de ser baseado no nome do pacote.
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### Instalar um pacote
+
+Você pode instalar pacotes do {% data variables.product.prodname_registry %} adicionando os pacotes como dependências no arquivo *package.json* para o seu projeto. Para obter mais informações sobre como usar um pacote *package.json* no projeto, consulte "[Trabalhar com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" na documentação npm.
+
+Por padrão, você pode adicionar pacotes a partir de uma organização. Para obter mais informações, consulte [Instalar pacotes de outras organizações](#installing-packages-from-other-organizations)."
+
+Você também precisa adicionar o arquivo *.npmrc* ao seu projeto para que todas as solicitações de instalação passem pelo {% data variables.product.prodname_registry %}. Ao encaminhar todas as solicitações através de {% data variables.product.prodname_registry %}, você pode usar pacotes com escopo e sem escopo de *npmjs.com*. Para obter mais informações, consulte "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação npm.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. Configure *package.json* no seu projeto para usar o pacote que você está instalando. Para adicionar as suas dependências de pacote ao arquivo *package.json* para {% data variables.product.prodname_registry %}, especifique o nome do pacote com escopo completo, como, por exemplo, `@my-org/server`. Para pacotes do *npmjs.com*, especifique o nome completo, como `@babel/core` ou `@lodash`. Por exemplo, o arquivo *package.json* a seguir usa o pacote `@octo-org/octo-app` como uma dependência.
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. Instale o pacote.
+
+  ```shell
+  $ npm install
+  ```
+
+#### Instalar pacotes de outras organizações
+
+Por padrão, você só pode usar pacotes do {% data variables.product.prodname_registry %} de uma organização. Se você deseja encaminhar solicitações de pacotes para várias organizações e usuários, você pode adicionar linhas adicionais ao seu arquivo *.npmrc* substituindo {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}*HOSTNAME* pelo nome de host de {% data variables.product.product_location %} e {% endif %}*OWNER* pelo nome do usuário ou da organização que é dono do repositório que contém o seu projeto.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio habilitado:
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+Se sua instância tem o isolamento de subdomínio desabilitado:
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### Usando o registro oficial do NPM
+
+{% data variables.product.prodname_registry %} permite que você acesse o registro oficial do NPM no `registry.npmjs.com`, caso seu administrador de {% data variables.product.prodname_ghe_server %} tenha habilitado esta funcionalidade. Para obter mais informações, consulte [Conectar ao registro oficial do NPM](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
+{% endif %}
+
+### Leia mais
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..9e87089f62
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,236 @@
+---
+title: Working with the NuGet registry
+intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client.
+
+You must replace:
+- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}.
+- `TOKEN` with your personal access token.
+- `OWNER` with the name of the user or organization account that owns the repository containing your project.{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %}If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://HOSTNAME/_registry/nuget/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+{% endif %}
+
+### Publishing a package
+
+You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### Publishing a package using a GitHub PAT as your API key
+
+If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+1. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. Publish the package using your PAT as the API key.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### Publishing a package using a *nuget.config* file
+
+When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. Add your project's specific information to your project's file, which ends in *.csproj*.  You must replace:
+    - `OWNER` with the name of the user or organization account that owns the repository containing your project.
+    - `REPOSITORY` with the name of the repository containing the package you want to publish.                      
+    - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. Publish the package using the `key` you specified in the *nuget.config* file.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field.
+
+For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository:
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### Installing a package
+
+Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use:
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. Install the packages with the `restore` command.
+  ```shell
+  dotnet restore
+  ```
+
+### Troubleshooting
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### Further reading
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..5de7f930a7
--- /dev/null
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,151 @@
+---
+title: Working with the RubyGems registry
+intro: 'Você pode configurar RubyGems para publicar um pacote em {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências em um projeto Ruby com o Bundler.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
+
+### Pré-requisitos
+
+- Você deve ter o rubygems 2.4.1 ou superior. Para encontrar sua versão do rubygems:
+
+  ```shell
+  $ gem --version
+  ```
+
+  - Você deve ter o bundler 1.6.4 ou superior. Para encontrar sua versão do Bundler:
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - Instale o keycutter para gerenciar várias credenciais. Para instalar o keycutter:
+  ```shell
+  $ gem install keycutter
+  ```
+
+### Autenticar-se no {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Efetuando a autenticação com um token de acesso pessoal
+
+{% data reusables.package_registry.required-scopes %}
+
+Você pode efetuar a autenticação em {% data variables.product.prodname_registry %} com o RubyGems editando o arquivo *~/.gem/credentials* para publicação de gems, editando o arquivo *~/.gemrc* para instalar um único gem, ou usando o Bundler para rastrear e instalar um ou mais gems.
+
+Para publicar novos gems, você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} com RubyGems, editando seu arquivo *~/.gem/credentials* para incluir seu token de acesso pessoal.  Crie um novo arquivo *~/.gem/credentials* se este arquivo não existir.
+
+Por exemplo, você criaria ou editaria um arquivo *~/.gem/credentials* para incluir o indicado a seguir, substituindo *TOKEN* pelo seu token de acesso pessoal.
+
+```shell
+gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" }
+```
+
+Para instalar gems, você deve efetuar a autenticação no {% data variables.product.prodname_registry %}, editando o arquivo *~/.gemrc* para o seu projeto incluir `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Você deve substituir:
+  - `NOME DE USUÁRIO` pelo seu nome de usuário no {% data variables.product.prodname_dotcom %}.
+  - `TOKEN` pelo seu token de acesso pessoal.
+  - `PROPRIETÁRIO` com o nome da conta do usuário ou da organização que é proprietário do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %}
+  - `URL` com a URL para o registro do Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %}.
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` com a URL para o registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.
+{% endif %}
+
+Se você não tiver um arquivo *~/.gemrc*, crie um arquivo *~/.gemrc* usando este exemplo.
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+Para autenticar com o bundler, configure o Bundler para usar o seu token de acesso pessoal, substituindo *USERNAME* com seu {% data variables.product.prodname_dotcom %} nome de usuário, *TOKEN* com seu token de acesso pessoal, e *OWNER* com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} Substitua `URL REGISTRO` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Substitua `REGISTRY-URL` pela URL do registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### Publicar um pacote
+
+{% data reusables.package_registry.default-name %} Por exemplo, ao publicar `octo-gem` na organização `octo-org` , {% data variables.product.prodname_registry %} publicará o gem no repositório `octo-org/octo-gem`. Para obter mais informações sobre como criar seu gem, consulte "[Criar seu próprio gem](http://guides.rubygems.org/make-your-own-gem/)" na documentação do RubyGems.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Crie o pacote da *gemspec* para criar o pacote *.gem*.
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. Publicar um pacote em {% data variables.product.prodname_registry %}, substituindo o `OWNER` pelo nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto e `OCTO-GEM` pelo nome do seu pacote de gemas.{% if enterpriseServerVersions contains currentVersion %} substitui `REGISTRY-URL` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %} Substitua `REGISTRY-URL` pela URL do registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### Publicar vários pacotes no mesmo repositório
+
+Para publicar vários gems no mesmo repositório, você pode incluir a URL no repositório de {% data variables.product.prodname_dotcom %} no campo `github_repo` em `gem.metadata`. Se você incluir este campo, {% data variables.product.prodname_dotcom %} corresponderá ao repositório baseado neste valor, ao invés de usar o nome do gem.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### Instalar um pacote
+
+É possível usar gems do {% data variables.product.prodname_registry %} assim como você usa gems de *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. Para o Bundler, adicione seu usuário ou organização {% data variables.product.prodname_dotcom %} como uma fonte no seu *Gemfile* para buscar gems a partir desta nova fonte. Por exemplo, você pode adicionar um novo bloco`de fonte`ao seu *Gemfile* que usa {% data variables.product.prodname_registry %} apenas para os pacotes que você especificar, substituindo *GEM NOME* pelo pacote que deseja instalar de {% data variables.product.prodname_registry %} e *OWNER* pelo usuário ou organização que possui o repositório que contém a gema que deseja instalar.{% if enterpriseServerVersions contains currentVersion %} substitua `URL REGISTRY` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %} Substitua `REGISTRY-URL` pela URL do registro do Rubygems da sua instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome de host de {% data variables.product.product_location %}.{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. Para versões do Bundler anteriores à 1.7.0, você deve adicionar uma nova `fonte` global. Para obter mais informações sobre como usar o Bundler, consulte a [documentação bundler.io](http://bundler.io/v1.5/gemfile.html).
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. Instale o pacote:
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### Leia mais
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
index 2b8affe154..e5400ec4a8 100644
--- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
+++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
@@ -24,9 +24,9 @@ O {% data variables.product.prodname_pages %} trabalha com dois tipos de domíni
 | Subdomínio personalizado                 | `blog.example.com` |
 | Domínio apex                             | `example.com`      |
 
-You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)."
+Você pode definir as duas configurações apex e subdomínio de `www` para o seu site. Para obter mais informações sobre domínios apex, consulte "[Usar um domínio apex para o seu site {% data variables.product.prodname_pages %}](#using-an-apex-domain-for-your-github-pages-site)".
 
-É recomendável sempre usar um subdomínio `www`, mesmo se você também usar um domínio apex. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
+É recomendável sempre usar um subdomínio `www`, mesmo se você também usar um domínio apex. Ao criar um novo site com um domínio apex, tentamos proteger automaticamente o subdomínio `www` para uso ao servir o conteúdo do seu site. Se você configurar um subdomínio `www`, nós tentaremos proteger automaticamente o domínio apex associado. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
 
 Depois que você configurar um domínio personalizado para um site de usuário ou organização, o domínio personalizado substituirá a parte `<user>.github.io` ou `<organization>.github.io` da URL para qualquer site de projeto de propriedade da conta que não tenha um domínio personalizado configurado. Por exemplo, se o domínio personalizado para o site de usuário for `www.octocat.com` e você tiver um site de projeto sem domínio personalizado configurado que seja publicado de um repositório chamado `octo-project`, o site do {% data variables.product.prodname_pages %} para esse repositório estará disponível em `www.octocat.com/octo-project`.
 
@@ -44,7 +44,7 @@ Os subdomínios `www` são o tipo mais estável de domínio personalizado, pois
 
 #### Subdomínios personalizados
 
-A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Os subdomínios personalizados são usados mais frequentemente quando você deseja duas seções distintas do site. Por exemplo, você pode criar um site chamado `blog.example.com.` e personalizar essa seção independentemente de `www.example.com`.
+Um subdomínio personalizado é um tipo de subdomínio que não usa a variante padrão `www`. Os subdomínios personalizados são usados mais frequentemente quando você deseja duas seções distintas do site. Por exemplo, você pode criar um site chamado `blog.example.com.` e personalizar essa seção independentemente de `www.example.com`.
 
 ### Usar um domínio apex para seu site do {% data variables.product.prodname_pages %}
 
@@ -52,7 +52,7 @@ Um domínio apex é um domínio personalizado que não contém um subdomínio, c
 
 Um domínio apex é configurado com um registro `A`, `ALIAS` ou `ANAME` por meio do provedor DNS. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)".
 
-{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)."
+{% data reusables.pages.www-and-apex-domain-recommendation %} Para obter mais informações, consulte "[Gerenciar um domínio personalizado para o seu site de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)".
 
 ### Atualizar domínios personalizados quando seu site do {% data variables.product.prodname_pages %} é desabilitado
 
diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index 21a1124462..04d44e1697 100644
--- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -46,7 +46,7 @@ Para configurar um `www` ou um subdomínio personalizado como, por exemplo, `www
 4. Em "Domínio personalizado,", digite o seu domínio personalizado e clique em **Salvar**. Isso criará um commit que adiciona um arquivo _CNAME_ à raiz da sua fonte de publicação. ![Botão Salvar domínio personalizado](/assets/images/help/pages/save-custom-subdomain.png)
 5. Navegue até o provedor DNS e crie um registro `CNAME` que aponte seu subdomínio para o domínio padrão do seu site. Por exemplo, se você quiser usar o subdomínio `www.example.com` para seu site de usuário, crie um registro `CNAME` que aponte `www.example.com` para `<user>.github.io`. Se você desejar usar o subdomínio `www.anotherexample.com` no seu site da organização, crie um registro `CNAME` que aponte `www. notherexample.com` para `<organization>.github.io`. O registro `CNAME` sempre deve apontar para `<user>.github.io` ou `<organization>.github.io`, excluindo o nome do repositório. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. Para confirmar que o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WW.EXAMPLE.COM_ pelo seu subdomínio.
 ```shell
@@ -61,9 +61,9 @@ Para configurar um `www` ou um subdomínio personalizado como, por exemplo, `www
 
 ### Configurando um domínio apex
 
-To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file  in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
+Para configurar um domínio apex, como `example.com`, você deve configurar um arquivo</em> CNAME_ no seu repositório de {% data variables.product.prodname_pages %} e pelo menos um `ALIAS`, `ANAME` ou um registro `A` com seu provedor DNS.</p>
 
-{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
+{% data reusables.pages.www-and-apex-domain-recommendation %} Para obter mais informações, consulte "[Configurar um subdomínio](#configuring-a-subdomain)".
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -71,7 +71,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 4. Em "Domínio personalizado,", digite o seu domínio personalizado e clique em **Salvar**. Isso criará um commit que adiciona um arquivo _CNAME_ à raiz da sua fonte de publicação. ![Botão Salvar domínio personalizado](/assets/images/help/pages/save-custom-apex-domain.png)
 5. Navegue até o provedor DNS e crie um registro `ALIAS`, `ANAME` ou `A`. {% data reusables.pages.contact-dns-provider %}
     - Para criar um registro `ALIAS` ou `ANAME`, aponte o domínio apex para o domínio padrão do seu site. {% data reusables.pages.default-domain-information %}
-    - To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+    - Para criar registros `A`, aponte seu domínio apex para os endereços IP para {% data variables.product.prodname_pages %}.
       ```shell
       185.199.108.153
       185.199.109.153
@@ -79,7 +79,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. Para confirmar que o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WW.EXAMPLE.COM_ pelo domínio apex. Confirme que os resultados correspondem aos endereços IP do {% data variables.product.prodname_pages %} acima.
   ```shell
@@ -92,16 +92,16 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
 
-### Configuring an apex domain and the `www` subdomain variant
+### Configurar um domínio apex e a variante de subdomínio `www`
 
-When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant.
+Ao usar um domínio apex, recomendamos que você configure o seu site de {% data variables.product.prodname_pages %} para hospedar o conteúdo tanto no domínio apex quanto na variante de subdomínio `www`.
 
-To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
+Para configurar um subdomínio de `www` junto com o domínio apex, você deve primeiro configurar um domínio apex, que irá criar um `ALIAS`, `ANAME` ou registro `A` junto ao seu provedor DNS. Para obter mais informações, consulte "[Configurar um domínio apex](#configuring-an-apex-domain)".
 
-After you configure the apex domain, you must to configure a CNAME record with your DNS provider.
+Depois de configurar o domínio apex, você deverá configurar um registro CNAME com seu provedor DNS.
 
-1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
-2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
+1. Acesse o provedor DNS e crie um registro `CNAME` que aponte `www.example.com` para o domínio padrão do seu site: `<user>.github.io` ou `<organization>.github.io`. Não inclua o nome do repositório. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
+2. Para confirmar que o registro DNS foi configurado corretamente, use o comando `dig` substituindo _WWW.EXAMPLE.COM_ pela sua variante de subdomínio `www`.
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -109,12 +109,12 @@ After you configure the apex domain, you must to configure a CNAME record with y
     > <em>YOUR-USERNAME</em>.github.io.      43192   IN      CNAME   <em> GITHUB-PAGES-SERVER </em>.
     > <em> GITHUB-PAGES-SERVER </em>.         22      IN      A       192.0.2.1
 ```
-### Removing a custom domain
+### Remover um domínio personalizado
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-4. Under "Custom domain," click **Remove**. ![Botão Salvar domínio personalizado](/assets/images/help/pages/remove-custom-domain.png)
+4. Em "Domínio personalizado, clique em **Remover**. ![Botão Salvar domínio personalizado](/assets/images/help/pages/remove-custom-domain.png)
 
 ### Leia mais
 
diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
index bae45c0e5b..f56e78a3fa 100644
--- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
+++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -24,8 +24,8 @@ Em seguida, verifique se o arquivo _CNAME_ está formatado corretamente.
 
 - O nome de arquivo _CNAME_ deve estar todo em letras maiúsculas.
 - O arquivo _CNAME_ só pode conter um domínio. Para apontar vários domínios para o site, é preciso configurar um redirecionamento por meio do provedor DNS.
-- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
-- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. Por exemplo, se o arquivo _CNAME_ de outro repositório contiver `example.com`, você não poderá usar `example.com` no arquivo _CNAME_ para o repositório.
+- O arquivo _CNAME_ deve conter apenas o nome do domínio. Por exemplo, `www.example.com`, `blog.example.com` ou `example.com`.
+- O nome de domínio precisa ser único em todos os sites de {% data variables.product.prodname_pages %}. Por exemplo, se o arquivo _CNAME_ de outro repositório contiver `example.com`, você não poderá usar `example.com` no arquivo _CNAME_ para o repositório.
 
 ### Configuração incorreta do DNS
 
@@ -42,7 +42,7 @@ Verifique se o seu site não:
 - Usa mais de um subdomínio `www`. Por exemplo, `www.example.com` e `www.anotherexample.com`.
 - Usa um domínio apex e um subdomínio personalizado. Por exemplo, `example.com` e `docs.example.com`.
 
-  The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)".
+  A única exceção é o subdomínio `www`. Se configurado corretamente, o subdomínio `www` é automaticamente redirecionado para o domínio apex. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)".
 
 {% data reusables.pages.wildcard-dns-warning %}
 
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md
index ca2158faed..7a0ef86f2a 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -68,14 +68,6 @@ O URL onde o site estará disponível depende da habilitação do isolamento do
 Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" ou entre em contato com o administrador do site.
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Observação:** os repositórios que usam o esquema de nomenclatura `<username>.github.com` herdado ainda são publicados, mas os visitantes serão redirecionados de `http(s)://<username>.github.com` para `http(s)://<username>.github.io`. Se ambos os repositórios, `<username>.github.com` e `<username>.github.io` existirem, somente o repositório `<username>.github.io` será publicado.
-
-{% endnote %}
-{% endif %}
-
 ### Publicar fontes para sites do {% data variables.product.prodname_pages %}
 
 A fonte de publicação do seu site de {% data variables.product.prodname_pages %} é o branch e a pasta onde os arquivos de origem do seu site são armazenados.
@@ -135,7 +127,7 @@ Se o seu site exceder essas cotas de uso, talvez não possamos atender a ele ou
 
 O {% data variables.product.prodname_pages %} não foi projetado e nem tem permissão para ser usado como um serviço de hospedagem gratuita na web, capaz de administrar sua empresa online, seu site de comércio eletrônico ou qualquer outro site desenvolvido principalmente para facilitar transações comerciais ou fornecer software comercial como um serviço (SaaS).
 
-In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. Para uma lista de usos proibidos, consulte "[Termos Adicionais do Produto de {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)".
+Além disso, {% data variables.product.prodname_dotcom %} não permite que {% data variables.product.prodname_pages %} seja usado para certos propósitos ou atividades. Para uma lista de usos proibidos, consulte "[Termos Adicionais do Produto de {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)".
 {% endif %}
 
 ### Tipos de MIME no {% data variables.product.prodname_pages %}
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index f715178415..144905b6fc 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -11,7 +11,7 @@ redirect_from:
 
 ### Sobre controle de acesso para sites de {% data variables.product.prodname_pages %}
 
-Se o seu site de projeto for publicado de um repositório privado ou interno, pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. Com controle de acesso, você pode optar por publicar o site publicamente para qualquer pessoa na internet ou em particular para pessoas com acesso de leitura ao seu repositório. Um site publicado de forma privada pode ser usado para compartilhar sua documentação interna ou base de conhecimento com integrantes da sua empresa. Você não pode gerenciar o controle de acesso para um site da organização. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+Se o seu site de projeto for publicado de um repositório privado ou interno, pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. Com controle de acesso, você pode optar por publicar o site publicamente para qualquer pessoa na internet ou em particular para pessoas com acesso de leitura ao seu repositório. Um site publicado de forma privada pode ser usado para compartilhar sua documentação interna ou base de conhecimento com integrantes da sua empresa. Você não pode gerenciar o controle de acesso para um site da organização. Para obter mais informações sobre os tipos de sites do {% data variables.product.prodname_pages %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)".
 
 Os sites publicados em particular estão disponíveis em um subdomínio diferente dos sites publicados em modo público. Isso garante que seu site do {% data variables.product.prodname_pages %} esteja seguro a partir do momento em que for publicado:
 
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index 09e311c329..866748aac5 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -22,7 +22,7 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 2. Se existir um branch `gh-pages` no repositório, exclua o branch `gh-pages`. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)".
-3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+3. Se o branch `gh-pages` fosse a sua fonte de publicação, {% if currentVersion == "free-pro-team@latest" %}pule para a etapa 6{% else %}agora o seu site não está publicado e você pode pular as etapas restantes{% endif %}.
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
 5. No "{% data variables.product.prodname_pages %}", use o menu suspenso **Source** (Fonte) e selecione **None** (Nenhuma). ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png)
diff --git a/translations/pt-BR/content/pages/index.md b/translations/pt-BR/content/pages/index.md
index e1ca6b6d6f..fe62223953 100644
--- a/translations/pt-BR/content/pages/index.md
+++ b/translations/pt-BR/content/pages/index.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Pages Documentation
+title: Documentação do GitHub Pages
 shortTitle: GitHub Pages
 intro: 'Você pode criar um site diretamente de um repositório do {% data variables.product.product_name %}.'
 redirect_from:
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
index ebb0c93f39..d0d5ce0e9d 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -56,7 +56,7 @@ kramdown:
 
 Por padrão, o Jekyll não cria arquivos nem pastas que:
 - estão localizadas em uma pasta chamada `/node_modules` ou `/vendor`
-- start with `_`, `.`, or `#`
+- comece com `_`, `.` ou `#`
 - terminam com `~`
 - são excluídos pela configuração `exclude` em seu arquivo de configuração
 
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index c2ee49d48e..1f4841abfe 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -87,7 +87,12 @@ Antes de poder usar o Jekyll para criar um site do {% data variables.product.pro
 10. Salve e feche o Gemfile.
 11. Na linha de comando, execute `atualização do pacote`.
 11. Como alternativa, teste seu site localmente. Para obter mais informações, consulte "[Testar seu site do {% data variables.product.prodname_pages %} localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)".
-12. Adicione seu repositório {% data variables.product.product_name %} como um remoto, substituindo {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ pelo nome de host da sua empresa,{% endif %} _USUÁRIO_ pela conta proprietária do repositório{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} e _REPOSITÓRIO_ pelo nome do repositório.
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. Adicione seu repositório {% data variables.product.product_name %} como um remoto, substituindo {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ pelo nome de host da sua empresa,{% endif %} _USUÁRIO_ pela conta proprietária do repositório{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} e _REPOSITÓRIO_ pelo nome do repositório.
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
index 30bfef42c1..29031a9ee4 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
@@ -31,7 +31,7 @@ Antes de usar o Jekyll para testar um site, você deve:
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.pages.navigate-publishing-source %}
-3. Run `bundle install`.
+3. Execute a `instalação do bundle`.
 3. Execute o site do Jekyll localmente.
   ```shell
   $ bundle exec jekyll serve
diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md
index cd88e97fcf..cdad9ef041 100644
--- a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ Mmmmm, tem sabor de [JSON][json]. Vamos adicionar o sinalizador `-i` para inclui
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -225,7 +225,7 @@ Em seguida, vamos buscar nosso repositório recém-criado:
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ Um projeto do tamanho de Rails tem milhares de problemas. Vamos precisar [pagina
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ Uma grande parte de ser um bom cidadão da API é respeitar os limites de taxa p
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ Além do texto do JSON, anote o código de status de HTTP de `200` e o cabeçalh
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 O status `304` indica que o recurso não mudou desde a última vez que pedimos e a resposta não conterá texto. Como um bônus, as respostas de `304` não contam contra o seu [limite de taxa][rate-limiting].
diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md
index 70fdcf85f7..80e7c43748 100644
--- a/translations/pt-BR/content/rest/overview/libraries.md
+++ b/translations/pt-BR/content/rest/overview/libraries.md
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
diff --git a/translations/pt-BR/content/rest/overview/media-types.md b/translations/pt-BR/content/rest/overview/media-types.md
index 67a87197fa..739d3823bd 100644
--- a/translations/pt-BR/content/rest/overview/media-types.md
+++ b/translations/pt-BR/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ Você pode verificar a versão atual por meio de cada cabeçalho de resposta.  P
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
index 7fff78381f..49ac2eed23 100644
--- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md
@@ -34,7 +34,7 @@ enviados e recebidos como JSON.
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: nginx
 > Date: Fri, 12 Oct 2012 23:33:14 GMT
 > Content-Type: application/json; charset=utf-8
@@ -126,7 +126,7 @@ A autenticação com credenciais inválidas retornará `401 Unauthorized`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
-> HTTP/1.1 401 Unauthorized
+> HTTP/2 401
 
 > {
 >   "message": "Bad credentials",
@@ -139,7 +139,7 @@ Após detectar várias solicitações com credenciais inválidas em um curto per
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 -u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > {
 >   "message": "Maximum number of login attempts exceeded. Please try again later.",
 >   "documentation_url": "{% data variables.product.doc_url_pre %}"
@@ -181,7 +181,7 @@ Há três tipos possíveis de erros de cliente na chamadas da API que recebem te
 
 1. O envio de um JSON inválido resultará em uma resposta </code>400 Bad Request`.</p>
 
-<pre><code> HTTP/1.1 400 Bad Request
+<pre><code> HTTP/2 400
  Content-Length: 35
 
  {"message":"Problems parsing JSON"}
@@ -192,7 +192,7 @@ Há três tipos possíveis de erros de cliente na chamadas da API que recebem te
 Enviar o tipo incorreto de valores do JSON resultará em uma resposta `400 Bad
 Request`.
   
-       HTTP/1.1 400 Bad Request
+       HTTP/2 400
        Content-Length: 40
       
        {"message":"Body should be a JSON object"}
@@ -201,7 +201,7 @@ Request`.
 
 O envio de campos inválidos resultará em uma resposta `422 Unprocessable Entity`.
   
-       HTTP/1.1 422 Unprocessable Entity
+       HTTP/2 422
        Content-Length: 149
       
        {
@@ -334,7 +334,7 @@ Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu st
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 56
@@ -357,7 +357,7 @@ new Date(1372700873 * 1000)
 Se você exceder o limite de taxa, uma resposta do erro retorna:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 0
@@ -377,7 +377,7 @@ Se o seu aplicativo OAuth precisar fazer chamadas não autenticadas com um limit
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 5000
 > X-RateLimit-Remaining: 4966
@@ -403,7 +403,7 @@ O abuso dos limites de taxa não são destinados a interferir no uso legítimo d
 Se seu aplicativo acionar este limite de taxa, você receberá uma resposta informativa:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Content-Type: application/json; charset=utf-8
 > Connection: close
 
@@ -456,7 +456,7 @@ A maioria das respostas retorna um cabeçalho de </code>Etag`. Muitas respostas
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/user
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -466,7 +466,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -476,7 +476,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
@@ -493,7 +493,7 @@ Aqui está uma solicitação de exemplo enviada a partir de uma consulta em `htt
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
-HTTP/1.1 302 Found
+HTTP/2 302
 Access-Control-Allow-Origin: *
 Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
@@ -502,7 +502,7 @@ A solicitação pré-voo de CORS se parece com isso:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
-HTTP/1.1 204 No Content
+HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
diff --git a/translations/pt-BR/content/rest/reference/activity.md b/translations/pt-BR/content/rest/reference/activity.md
index d5b2ee7d3b..2f1b139fc7 100644
--- a/translations/pt-BR/content/rest/reference/activity.md
+++ b/translations/pt-BR/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ Os eventos são otimizados para sondagem a com o cabeçalho "ETag". Se nenhum no
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
 # The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ Para obter um feed no formato Atom você deve especificar o tipo `application/at
 #### Resposta
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ As notificações são otimizadas para sondagem com o cabeçalho `Last-Modified`
 ``` shell
 # Add authentication to your requests
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
 # Pass the Last-Modified header exactly
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/pt-BR/content/rest/reference/emojis.md b/translations/pt-BR/content/rest/reference/emojis.md
index ec918c60c2..4f4dac4de9 100644
--- a/translations/pt-BR/content/rest/reference/emojis.md
+++ b/translations/pt-BR/content/rest/reference/emojis.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md
index 886b24b303..1fef69a1c5 100644
--- a/translations/pt-BR/content/rest/reference/enterprise-admin.md
+++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md
@@ -18,7 +18,7 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints
 
 {% note %}
 
-**Observação:** Este artigo aplica-se a {% data variables.product.prodname_ghe_cloud %}. Para ver a versão do {% data variables.product.prodname_ghe_server %}, use o menu suspenso **{% data ui.pages.article_version %}**.
+**Observação:** Este artigo aplica-se a {% data variables.product.prodname_ghe_cloud %}. Para visualizar a versão de {% data variables.product.prodname_ghe_managed %} ou de {% data variables.product.prodname_ghe_server %}, use o menu suspenso **{% data ui.pages.article_version %}**.
 
 {% endnote %}
 
@@ -26,10 +26,10 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints
 
 ### URLs do ponto de extremidade
 
-REST API endpoints{% if enterpriseServerVersions contains currentVersion %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL:
+Pontos de extremidade da API REST{% if enterpriseServerVersions contains currentVersion %}—exceto os pontos de extremidades da API REST do [Console de gerenciamento](#management-console) -{% endif %} são prefixados com a seguinte URL:
 
 ```shell
-http(s)://<em>hostname</em>/api/v3/
+{% data variables.product.api_url_pre %}
 ```
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -42,16 +42,16 @@ http(s)://<em>hostname</em>/
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ### Autenticação
 
-Os endpoints de API da sua instalação do {% data variables.product.product_name %} aceitam [os mesmos métodos de autenticação](/rest/overview/resources-in-the-rest-api#authentication) da API do GitHub.com. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} Os tokens OAuth devem ter o `site_admin` [escopo OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) quando usados com endpoints específicos da Enterprise.{% endif %}
+Os endpoints de API da sua instalação do {% data variables.product.product_name %} aceitam [os mesmos métodos de autenticação](/rest/overview/resources-in-the-rest-api#authentication) da API do GitHub.com. Você pode efetuar a autenticação com **[tokens do OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(que podem ser criado usando a [API de Autorizações](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}ou **[autenticação básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} Os tokens OAuth devem ter o `site_admin` [escopo OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) quando usados com endpoints específicos da Enterprise.{% endif %}
 
-Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% if enterpriseServerVersions contains currentVersion %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
+Os pontos de extremidade da API da administração da empresa podem ser acessados por administradores do site de {% data variables.product.product_name %}autenticados{% if enterpriseServerVersions contains currentVersion %}, exceto a API do [Console de Gerenciamento](#management-console), que exige a [senha do console de gerenciamento](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
 
 {% endif %}
 
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ### Informações da versão
 
-The current version of your enterprise is returned in the response header of every API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` You can also read the current version by calling the [meta endpoint](/rest/reference/meta/).
+A versão atual da sua empresa é retornada no cabeçalho de resposta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` Você também pode ler a versão atual chamando o [ponto de extremidade de meta](/rest/reference/meta/).
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
@@ -78,9 +78,11 @@ The current version of your enterprise is returned in the response header of eve
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 ## GitHub Actions
 
+{% data reusables.actions.ae-beta %}
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
@@ -98,7 +100,7 @@ O IdP deve usar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{
 
 {% note %}
 
-**Nota:** A API corporativa SCIM está disponível apenas para empresas em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)."
+**Nota:** A API corporativa SCIM está disponível apenas para empresas em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
 
 {% endnote %}
 
@@ -149,19 +151,6 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 {% endfor %}
 
 {% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
-
-## Encryption at rest
-
-You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## Estatísticas de admin
 
@@ -175,9 +164,9 @@ A API de Estatísticas Administrativas fornece uma variedade de métricas sobre
 
 {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 
-## Announcements
+## Anúncios
 
-The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+A API de anúncios permite que você gerencie o banner de anúncio global na sua empresa. Para obter mais informações, consulte "[Personalizar mensagens de usuários para a sua empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)".
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %}
@@ -189,7 +178,7 @@ The Announcements API allows you to manage the global announcement banner in you
 
 ## Webhooks globais
 
-Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Webhooks globais podem se inscrever para os tipos de eventos  [organização](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuário](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositório](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipe](/developers/webhooks-and-events/webhook-events-and-payloads#team), [integrante](/developers/webhooks-and-events/webhook-events-and-payloads#member), [filiação](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifurcação](/developers/webhooks-and-events/webhook-events-and-payloads#fork)e [ping](/developers/webhooks-and-events/about-webhooks#ping-event).
+Webhooks globais são instalados na sua empresa. Você pode usar webhooks globais para monitorar, responder ou aplicar regras automaticamente para usuários, organizações, equipes e repositórios na sua empresa. Webhooks globais podem se inscrever para os tipos de eventos  [organização](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuário](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositório](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipe](/developers/webhooks-and-events/webhook-events-and-payloads#team), [integrante](/developers/webhooks-and-events/webhook-events-and-payloads#member), [filiação](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifurcação](/developers/webhooks-and-events/webhook-events-and-payloads#fork)e [ping](/developers/webhooks-and-events/about-webhooks#ping-event).
 
 *Esta API está disponível somente para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la. Para aprender como configurar webhooks globais, consulte [Sobre webhooks globais](/enterprise/admin/user-management/about-global-webhooks).
 
@@ -205,7 +194,7 @@ Global webhooks are installed on your enterprise. You can use global webhooks to
 
 Você pode usar a API LDAP para atualizar as relações de conta entre um usuário ou equipe {% data variables.product.product_name %} e sua entrada LDAP vinculada ou enfileirar uma nova sincronização.
 
-Com os endpoints de mapeamento LDAP, você é capaz de atualizar o Nome Distinto (DN) para o qual um usuário ou uma equipe mapeia. Note que os endpoints LDAP são geralmente eficazes apenas se o seu appliance {% data variables.product.product_name %} tiver [Sincronização LDAP habilitada](/enterprise/admin/authentication/using-ldap). O endpoint [mapeamento LDAP de atualização para um usuário](#update-ldap-mapping-for-a-user) pode ser usado quando o LDAP é habilitado, mesmo que a sincronização LDAP esteja desativada.
+Com os endpoints de mapeamento LDAP, você é capaz de atualizar o Nome Distinto (DN) para o qual um usuário ou uma equipe mapeia. Note que os endpoints LDAP são geralmente eficazes apenas se o seu aplicativo de {% data variables.product.product_name %} tiver [Sincronização LDAP habilitada](/enterprise/admin/authentication/using-ldap). O endpoint [mapeamento LDAP de atualização para um usuário](#update-ldap-mapping-for-a-user) pode ser usado quando o LDAP é habilitado, mesmo que a sincronização LDAP esteja desativada.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %}
@@ -233,7 +222,7 @@ A API do Console de Gerenciamento ajuda você a gerenciar sua instalação do {%
 
 {% tip %}
 
-Você deve definir explicitamente o número da porta ao fazer chamadas de API para o Console de Gerenciamento. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`.
+Você deve definir explicitamente o número da porta ao fazer chamadas de API para o Console de Gerenciamento. Se o TLS estiver habilitado na sua empresa, o número da porta será `8443`; caso contrário, o número da porta será `8080`.
 
 Se não quiser fornecer um número da porta, você precisará configurar sua ferramenta para seguir os redirecionamentos automaticamente.
 
@@ -266,7 +255,7 @@ $ curl -L 'https://api_key:<em>your-amazing-password</em>@<em>hostname</em>:<em>
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## Organizações
 
-The Organization Administration API allows you to create organizations on your enterprise. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
+A API de administração da organização permite a criação de organizações na sua empresa. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
@@ -386,7 +375,7 @@ Os valores possíveis para *aplicação* são `habilitado`, `desabilitado` e`tes
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## Usuários
 
-The User Administration API allows you to suspend{% if enterpriseServerVersions contains currentVersion %}, unsuspend, promote, and demote{% endif %}{% if currentVersion == "github-ae@latest" %} and unsuspend{% endif %} users on your enterprise. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `403` se tentarem acessá-la.
+A API de Administração do Usuário permite que você suspenda{% if enterpriseServerVersions contains currentVersion %}, cancele a suspensão, promova e rebaixe{% endif %}{% if currentVersion == "github-ae@latest" %} e cancele o suspensão{% endif %} dos usuários da sua empresa. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `403` se tentarem acessá-la.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/gists.md b/translations/pt-BR/content/rest/reference/gists.md
index d9a1836585..7fcfee8e74 100644
--- a/translations/pt-BR/content/rest/reference/gists.md
+++ b/translations/pt-BR/content/rest/reference/gists.md
@@ -10,43 +10,43 @@ topics:
   - API
 ---
 
-### Authentication
+### Autenticação
 
-You can read public gists {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}and create them for anonymous users without a token.{% else %} anonymously, but you must be signed into GitHub to create gists.{% endif %} To read or write gists on a user's behalf, you need the gist OAuth scope and a token. For more information, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps)."
+Você pode ler gists públicos {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contém currentVersion %}e criá-los para usuários anônimos sem um token{% else %} de forma anônima, mas você precisa entrar no GitHub para criar gists.{% endif %} Para ler ou escrever gists em nome do usuário, você precisa do escopo OAuth para gists e um token. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)."
 
 <!-- When an OAuth client does not have the gists scope, the API will return a 404 "Not Found" response regardless of the validity of the credentials. The API will return a 401 "Bad credentials" response if the gists scope was given to the application but the credentials are invalid. -->
 
-### Truncation
+### Truncamento
 
-The Gist API provides up to one megabyte of content for each file in the gist. Each file returned for a gist through the API has a key called `truncated`. If `truncated` is `true`, the file is too large and only a portion of the contents were returned in `content`.
+A API de Gist fornece até um megabyte de conteúdo para cada arquivo no gist. Cada arquivo retornado por um gist através da API tem uma chave denominada `truncada`. Se `truncado` for `verdadeiro`, significa que arquivo é muito grande e apenas uma parte do conteúdo foi retornado em `conteúdo`.
 
-If you need the full contents of the file, you can make a `GET` request to the URL specified by `raw_url`. Be aware that for files larger than ten megabytes, you'll need to clone the gist via the URL provided by `git_pull_url`.
+Se você precisar do conteúdo completo do arquivo, você pode fazer uma solicitação `GET` para a URL especificada por `raw_url`. Tenha em mente que, para arquivos maiores que dez megabytes, você deverá clonar o gist através da URL fornecida por `git_pull_url`.
 
-In addition to a specific file's contents being truncated, the entire files list may be truncated if the total number exceeds 300 files. If the top level `truncated` key is `true`, only the first 300 files have been returned in the files list. If you need to fetch all of the gist's files, you'll need to clone the gist via the URL provided by `git_pull_url`.
+Além do conteúdo de um arquivo específico ser truncado, toda a lista de arquivos pode ser truncada se o número total exceder 300 arquivos. Se a chave de nível superior `truncado` é `verdadeira`, apenas os primeiros 300 arquivos foram retornados na lista de arquivos. Se você precisar buscar todos os arquivos do gist, você deverá clonar o gist através da URL fornecida por `git_pull_url`.
 
-### Custom media types for gists
+### Tipos de mídia personalizados para gists
 
-These are the supported media types for fetching gist contents.
+Estes são os tipos de mídia compatíveis para buscar conteúdo geral.
 
     application/vnd.github.VERSION.raw
     application/vnd.github.VERSION.base64
 
-For more information, see "[Media types](/rest/overview/media-types)."
+Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)".
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Comments
+## Comentários
 
-### Custom media types for Gist comments
+### Tipos de mídia personalizados para comentários do Gist
 
-These are the supported media types for gist comments.
+Estes são os tipos de mídia compatíveis para comentários de gist.
 
     application/vnd.github.VERSION.raw
     application/vnd.github.VERSION.base64
 
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
+Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)".
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/git.md b/translations/pt-BR/content/rest/reference/git.md
index 170e82ead9..83d419ca86 100644
--- a/translations/pt-BR/content/rest/reference/git.md
+++ b/translations/pt-BR/content/rest/reference/git.md
@@ -19,7 +19,7 @@ A API do banco de dados do Git dá acesso para ler e gravar objetos do Git sem p
 
 ## Blobs
 
-Um blob (objeto binário grande) do Git é o tipo de objeto usado para armazenar o conteúdo de cada arquivo em um repositório. O hash SHA-1 do arquivo é calculado e armazenado no objeto do blob. Estes pontos de extremidade permitem ler e escrever [objetos do blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) em seu banco de dados d Git em {% data variables.product.product_name %}. Os blobs aproveitam [esses tipos de mídia personalizados](#custom-media-types). Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
+Um blob (objeto binário grande) do Git é o tipo de objeto usado para armazenar o conteúdo de cada arquivo em um repositório. O hash SHA-1 do arquivo é calculado e armazenado no objeto do blob. Estes pontos de extremidade permitem ler e escrever [objetos do blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) em seu banco de dados d Git em {% data variables.product.product_name %}. Os blobs aproveitam [esses tipos de mídia personalizados](#custom-media-types-for-blobs). Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
 
 ### Tipos de mídia personalizados para os blobs
 
diff --git a/translations/pt-BR/content/rest/reference/meta.md b/translations/pt-BR/content/rest/reference/meta.md
index 6cd6fa2083..7d6ba6201c 100644
--- a/translations/pt-BR/content/rest/reference/meta.md
+++ b/translations/pt-BR/content/rest/reference/meta.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md
index 3e39167eee..ecacf29d55 100644
--- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md
@@ -120,6 +120,9 @@ _Pesquisar_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _Pesquisar_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -678,6 +684,9 @@ _Equipes_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### Permissão em "pull requests"
 
@@ -767,6 +776,10 @@ _Revisões_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### Permission on "profile"
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### Permissão em "hooks de repositório"
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
@@ -780,10 +793,10 @@ _Revisões_
 {% if enterpriseServerVersions contains currentVersion %}
 ### Permission on "repository pre receive hooks"
 
-- [`GET /repos/:owner/:repo/pre-receive-hooks`](/v3/enterprise-admin/repo_pre_receive_hooks/#list-pre-receive-hooks-for-a-repository) (:read)
-- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/v3/enterprise-admin/repo_pre_receive_hooks/#get-a-pre-receive-hook-for-a-repository) (:read)
-- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/v3/enterprise-admin/repo_pre_receive_hooks/#update-pre-receive-hook-enforcement-for-a-repository) (:write)
-- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/v3/enterprise-admin/repo_pre_receive_hooks/#remove-pre-receive-hook-enforcement-for-a-repository) (:write)
+- [`GET /repos/:owner/:repo/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) (:read)
+- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) (:read)
+- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) (:write)
+- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) (:write)
 {% endif %}
 
 ### Permissão em "projetos de repositório"
diff --git a/translations/pt-BR/content/rest/reference/repos.md b/translations/pt-BR/content/rest/reference/repos.md
index afc16b7911..205213ecb0 100644
--- a/translations/pt-BR/content/rest/reference/repos.md
+++ b/translations/pt-BR/content/rest/reference/repos.md
@@ -1,5 +1,5 @@
 ---
-title: Repositories
+title: Repositórios
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /v3/repos
@@ -21,25 +21,24 @@ topics:
   {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Collaborators
+## Colaboradores
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Comments
+## Comentários
 
-### Custom media types for commit comments
+### Tipos de mídia personalizados para comentários de commit
 
-These are the supported media types for commit comments. You can read more
-about the use of media types in the API [here](/rest/overview/media-types).
+Estes são os tipos de mídia compatíveis com os comentários do commit. Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
 
     application/vnd.github-commitcomment.raw+json
     application/vnd.github-commitcomment.text+json
     application/vnd.github-commitcomment.html+json
     application/vnd.github-commitcomment.full+json
 
-For more information, see "[Custom media types](/rest/overview/media-types)."
+Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)".
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
@@ -47,14 +46,14 @@ For more information, see "[Custom media types](/rest/overview/media-types)."
 
 ## Commits
 
-The Repo Commits API supports listing, viewing, and comparing commits in a repository.
+A API de Commits do repositório é compatível com a listagem, visualização e comparação de commits em um repositório.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-## Community
+## Comunidade
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
@@ -62,56 +61,54 @@ The Repo Commits API supports listing, viewing, and comparing commits in a repos
 
 {% endif %}
 
-## Contents
+## Conteúdo
 
-These API endpoints let you create, modify, and delete Base64 encoded content in a repository. To request the raw format or rendered HTML (when supported), use custom media types for repository contents.
+Estes pontos de extremidade da API permitem criar, modificar e excluir conteúdo codificado em Base64 em um repositório. Para solicitar o formato sem processar ou HTML interpretado (quando compatível), use os tipos de mídia personalizados para o conteúdo do repositório.
 
-### Custom media types for repository contents
+### Tipos de mídia personalizados para conteúdo do repositório
 
-[READMEs](/rest/reference/repos#get-a-repository-readme), [files](/rest/reference/repos#get-repository-content), and [symlinks](/rest/reference/repos#get-repository-content) support the following custom media types:
+Os [READMEs](/rest/reference/repos#get-a-repository-readme), [arquivos](/rest/reference/repos#get-repository-content) e [links simbólicos](/rest/reference/repos#get-repository-content) são compatíveis com os seguintes tipos de mídia personalizados:
 
     application/vnd.github.VERSION.raw
     application/vnd.github.VERSION.html
 
-Use the `.raw` media type to retrieve the contents of the file.
+Use o tipo de mídia `.raw` para recuperar o conteúdo do arquivo.
 
-For markup files such as Markdown or AsciiDoc, you can retrieve the rendered HTML using the `.html` media type. Markup languages are rendered to HTML using our open-source [Markup library](https://github.com/github/markup).
+Para arquivos de markup, como Markdown ou AsciiDoc, você pode recuperar o HTML interpretado usando o tipo de mídia `.html`. As linguagens de markup são processadas em HTML usando nossa [biblioteca de markup](https://github.com/github/markup) de código aberto.
 
-[All objects](/rest/reference/repos#get-repository-content) support the following custom media type:
+[Todos os objetos](/rest/reference/repos#get-repository-content) são compatíveis com o seguinte tipo de mídia personalizado:
 
     application/vnd.github.VERSION.object
 
-Use the `object` media type parameter to retrieve the contents in a consistent object format regardless of the content type. For example, instead of an array of objects
-for a directory, the response will be an object with an `entries` attribute containing the array of objects.
+Use o parâmetro do tipo de mídia do `objeto` para recuperar o conteúdo em um formato de objeto consistente independentemente do tipo de conteúdo. Por exemplo, em vez de um array de objetos para um diretório, a resposta será um objeto com um atributo de `entrada` contendo o array de objetos.
 
-You can read more about the use of media types in the API [here](/rest/overview/media-types).
+Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types).
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Deploy keys
+## Chaves de implantação
 
 {% data reusables.repositories.deploy-keys %}
 
-Deploy keys can either be setup using the following API endpoints, or by using GitHub. To learn how to set deploy keys up in GitHub, see "[Managing deploy keys](/developers/overview/managing-deploy-keys)."
+Chaves de implantação podem ser configuradas usando os seguintes pontos de extremidades da API ou usando o GitHub. Para saber como configurar as chaves de implantação no GitHub, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys)".
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Deployments
+## Implantações
 
-Deployments are requests to deploy a specific ref (branch, SHA, tag). GitHub dispatches a [`deployment` event](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) that external services can listen for and act on when new deployments are created. Deployments enable developers and organizations to build loosely coupled tooling around deployments, without having to worry about the implementation details of delivering different types of applications (e.g., web, native).
+As implantações são solicitações para implantar um ref específico (branch, SHA, tag). O GitHub envia um [ evento de `implantação`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) pelo qual os serviços externos podem ouvir e atuar quando novas implantações são criadas. As implantações permitem que os desenvolvedores e as organizações construam ferramentas associadas em torno de implantações sem ter que se preocupar com os detalhes de implementação da entrega de diferentes tipos de aplicativos (p. ex., web, nativo).
 
-Deployment statuses allow external services to mark deployments with an `error`, `failure`, `pending`, `in_progress`, `queued`, or `success` state that systems listening to [`deployment_status` events](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) can consume.
+Os status de implantação externos permitem marcar implantações com `error`, `failure`, `pending`, `in_progress`, `queued` ou `success` afirmar que os sistemas que estão escutando os eventos [`deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) podem consumir.
 
-Deployment statuses can also include an optional `description` and `log_url`, which are highly recommended because they make deployment statuses more useful. The `log_url` is the full URL to the deployment output, and
-the `description` is a high-level summary of what happened with the deployment.
+Os status de implantação também podem incluir uma `descrição` opcional e `log_url`, que são altamente recomendados porque tornam o status de implantação mais útil. O `log_url` é a URL completa para a saída de implantação e a `descrição` é um resumo de alto nível do que aconteceu com a implantação.
 
-GitHub dispatches `deployment` and `deployment_status` events when new deployments and deployment statuses are created. These events allows third-party integrations to receive respond to deployment requests and update the status of a deployment as progress is made.
+O GitHub envia os eventos de `implantação` e `deployment_status` quando novas implantações de status de implantação são criadas. Esses eventos permitem que as integrações de terceiros recebam resposta para solicitações de implantação e atualizem o status de implantação conforme o progresso é feito.
 
-Below is a simple sequence diagram for how these interactions would work.
+Abaixo está um diagrama de sequência sobre para como essas interações funcionariam.
 
 ```
 +---------+             +--------+            +-----------+        +-------------+
@@ -140,49 +137,56 @@ Below is a simple sequence diagram for how these interactions would work.
      |                      |                       |                     |
 ```
 
-Keep in mind that GitHub is never actually accessing your servers. It's up to your third-party integration to interact with deployment events. Multiple systems can listen for deployment events, and it's up to each of those systems to decide whether they're responsible for pushing the code out to your servers, building native code, etc.
+Tenha em mente que o GitHub nunca terá acesso aos seus servidores. Cabe à sua integração de terceiros interagir com os eventos de implantação. Vários sistemas podem ouvir eventos de implantação, e cabe a cada um desses sistemas decidir se serão responsáveis por retirar o código dos seus servidores, criar código nativo, etc.
 
-Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the `public_repo` and `repo` scopes grant permission to code as well.
+Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% if currentVersion != "github-ae@latest" %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
 
-### Inactive deployments
 
-When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
+### Implantações inativas
 
-You can communicate that a transient environment no longer exists by setting its `state` to `inactive`.  Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it.
+Ao definir o estado de uma implantação como `sucesso`, todas as implantações de ambiente de não produção e não transitórios anteriores no mesmo nome do ambiente irão tornar-se `inativas`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação.
+
+Você pode informar que um ambiente transitório não existe mais definindo seu `estado` como `inativo`.  Definir o `estado` como `inativo` mostra a implantação como `destruída` em {% data variables.product.prodname_dotcom %} e remove o acesso a ela.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Forks
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+## Ambientes
+
+The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+{% endif %}
+
+## Bifurcações
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Invitations
+## Convites
 
-The Repository Invitations API allows users or external services to invite other users to collaborate on a repo. The invited users (or external services on behalf of invited users) can choose to accept or decline the invitations.
+A API de Convites do Repositório permite que usuários ou serviços externos convidem outros usuários para colaborar em um repositório. Os usuários convidados (ou serviços externos em nome dos usuários convidados) podem optar por aceitar ou recusar os convites.
 
-Note that the `repo:invite` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted
-access to invitations **without** also granting access to repository code, while the
-`repo` scope grants permission to code as well as invitations.
+Observe que o [Escopo OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` concede acesso direcionado aos convites **sem** conceder também acesso ao código do repositório. enquanto o escopo `repo` concede permissão ao código e aos convites convites.
 
-### Invite a user to a repository		
+### Convidar um usuário para um repositório
 
-Use the API endpoint for adding a collaborator. For more information, see "[Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator)."
+Use o ponto de extremidade da API para adicionar um colaborador. Para obter mais informações, consulte "[Adicionar um colaborador de repositório](/rest/reference/repos#add-a-repository-collaborator)".
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Merging
+## Mesclar
 
-The Repo Merging API supports merging branches in a repository. This accomplishes
-essentially the same thing as merging one branch into another in a local repository
-and then pushing to {% data variables.product.product_name %}. The benefit is that the merge is done on the server side and a local repository is not needed. This makes it more appropriate for automation and other tools where maintaining local repositories would be cumbersome and inefficient.
+A API de merge do repositório é compatível com o merge de branches em um repositório. Isso realiza, essencialmente, a mesma coisa que mesclar um branch em outro em um repositório local e, em seguida, fazer push para {% data variables.product.product_name %}. O benefício é que o merge é realizado no lado do servidor e não é necessário um repositório local. Isso o torna mais apropriado para automação e outras ferramentas em que a manutenção de repositórios locais seria pesada e ineficiente.
 
-The authenticated user will be the author of any merges done through this endpoint.
+O usuário autenticado será o autor de qualquer merge feito por meio deste ponto de extremidade.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %}
@@ -190,30 +194,30 @@ The authenticated user will be the author of any merges done through this endpoi
 
 ## Pages
 
-The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners, even though the websites are public. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)."
+A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
 
-In {% data variables.product.prodname_pages %} API endpoints with a `status` key in their response, the value can be one of:
-* `null`: The site has yet to be built.
-* `queued`: The build has been requested but not yet begun.
-* `building`:The build is in progress.
-* `built`: The site has been built.
-* `errored`: Indicates an error occurred during the build.
+Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} com uma chave de `status` na sua resposta, o valor pode ser:
+* `null`: O site ainda não foi criado.
+* `queued`: A criação foi solicitada, mas ainda não começou.
+* `building`:A criaçãoestá em andamento.
+* `built`: O site foi criado.
+* `errored`: Indica que ocorreu um erro durante a criação.
 
-In {% data variables.product.prodname_pages %} API endpoints that  return GitHub Pages site information, the JSON responses include these fields:
-* `html_url`: The absolute URL (including scheme) of the rendered Pages site. For example, `https://username.github.io`.
-* `source`: An object that contains the source branch and directory for the rendered Pages site. This includes:
-   - `branch`: The repository branch used to publish your [site's source files](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_.
-   - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`.
+Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} que devolvem as informações do site do GitHub Pages, as respostas do JSON incluem esses campos:
+* `html_url`: A URL absoluta (incluindo o esquema) do site de páginas interpretadas. Por exemplo, `https://username.github.io`.
+* `source`: Um objeto que contém o branch de origem e o diretório do site de páginas interpretadas. Isto inclui:
+   - `branch`: O branch do repositório utilizado para publicar os [arquivos de origem do site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por exemplo, _principal_ ou _gh-pages_.
+   - `path`: O diretório do repositório a partir do qual o site é publicado. Será `/` ou `/docs`.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Releases
+## Versões
 
 {% note %}
 
-**Note:** The Releases API replaces the Downloads API. You can retrieve the download count and browser download URL from the endpoints in this API that return releases and release assets.
+**Observação:** A API de versões substitui a API de Downloads. Você pode recuperar a contagem de download e a URL de download do navegador a partir dos pontos de extremidades nesta API que retornam versões e liberam ativos.
 
 {% endnote %}
 
@@ -221,68 +225,50 @@ In {% data variables.product.prodname_pages %} API endpoints that  return GitHub
   {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Statistics
+## Estatísticas
 
-The Repository Statistics API allows you to fetch the data that {% data variables.product.product_name %} uses for visualizing different
-types of repository activity.
+A API de Estatísticas do Repositório permite que você recupere os dados que o {% data variables.product.product_name %} usa para visualizar diferentes tipos de atividade do repositório.
 
-### A word about caching
+### Umas palavras sobre o armazenamento em cache
 
-Computing repository statistics is an expensive operation, so we try to return cached
-data whenever possible.  If the data hasn't been cached when you query a repository's
-statistics, you'll receive a `202` response; a background job is also fired to
-start compiling these statistics. Give the job a few moments to complete, and
-then submit the request again. If the job has completed, that request will receive a
-`200` response with the statistics in the response body.
+Computar as estatísticas do repositório é uma operação cara. Por esse motivo, tentamos retornar dados armazenados em cache sempre que possível.  Se os dados não forem armazenados em cache nas estatísticas de um repositório, você receberá uma resposta de `202`; um trabalho em segundo plano também é acionado para começar a compilar estas estatísticas. Dê ao trabalho alguns instantes para que seja concluído e, em seguida, envie a solicitação novamente. Se o trabalho foi concluído, essa solicitação receberá uma resposta de `200` com as estatísticas no texto da resposta.
 
-Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache.
+As estatísticas do repositório são armazenadas em cache pelo SHA do branch-padrão do repositório; fazer push para o branch-padrão redefine o armazenamento em cache de estatísticas.
 
-### Statistics exclude some types of commits
+### As estatísticas excluem alguns tipos de commits
 
-The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
+As estatísticas expostas pela API correspondem às estatísticas mostradas pelos [diferentes gráficos de repositórios](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
 
-To summarize:
-- All statistics exclude merge commits.
-- Contributor statistics also exclude empty commits.
+Resumo:
+- Todas as estatísticas excluem commits de merge.
+- As estatísticas do contribuidor também excluem commits vazios.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Statuses
+## Status
 
-The status API allows external services to mark commits with an `error`,
-`failure`, `pending`, or `success` state, which is then reflected in pull requests
-involving those commits.
+A API de status permite que serviços externos marquem commits com status de `erro`, `falha`, `pendente` ou `sucesso`, o que é refletido em pull requests que envolvem esses commits.
 
-Statuses can also include an optional `description` and `target_url`, and
-we highly recommend providing them as they make statuses much more
-useful in the GitHub UI.
+Os status também podem incluir uma `descrição` opcional e `target_url`, e é altamente recomendável fornecê-los, pois tornam o status muito mais útil na interface de usuário do GitHub.
 
-As an example, one common use is for continuous integration
-services to mark commits as passing or failing builds using status.  The
-`target_url` would be the full URL to the build output, and the
-`description` would be the high level summary of what happened with the
-build.
+Como exemplo, um uso comum é para serviços de integração contínua para marcar commits como criações que passam ou que falham usando o status.  O `target_url` seria a URL completa para a saída da criação, e a `descrição` seria o resumo de alto nível do que aconteceu com a criação.
 
-Statuses can include a `context` to indicate what service is providing that status.
-For example, you may have your continuous integration service push statuses with a context of `ci`, and a security audit tool push statuses with a context of `security`.  You can
-then use the [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) to retrieve the whole status for a commit.
+Os status podem incluir um `contexto` para indicar qual serviço está fornecendo esse status. Por exemplo, você pode fazer com que o seu serviço de integração contínua faça push status com um contexto de `ci`, e uma ferramenta de auditoria de segurança faça push dos status com um contexto de `segurança`.  Você pode usar [Obter o status combinado para uma referência específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) para recuperar todo o status de um commit.
 
-Note that the `repo:status` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to statuses **without** also granting access to repository code, while the
-`repo` scope grants permission to code as well as statuses.
+Observe que o `escopo do OAuth` [repo:status](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a status **sem** conceder acesso ao código do repositório, enquanto o escopo `repo` concede permissão para o código e para status.
 
-If you are developing a GitHub App and want to provide more detailed information about an external service, you may want to use the [Checks API](/rest/reference/checks).
+Se você está desenvolvendo um aplicativo GitHub e deseja fornecer informações mais detalhadas sobre um serviço externo, você deverá usar a [API de verificação](/rest/reference/checks).
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-## Traffic
+## Tráfego
 
-For repositories that you have push access to, the traffic API provides access
-to the information provided in your repository graph. For more information, see "<a href="/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository" class="dotcom-only">Viewing traffic to a repository</a>."
+Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. Para obter mais informações, consulte "<a href="/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository" class="dotcom-only">Visualizar tráfego para um repositório</a>. "
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
@@ -291,41 +277,41 @@ to the information provided in your repository graph. For more information, see
 
 ## Webhooks
 
-The Repository Webhooks API allows repository admins to manage the post-receive hooks for a repository. Webhooks can be managed using the JSON HTTP API, or the [PubSubHubbub](#PubSubHubbub) API.
+A API de Webhooks do Repositório permite que os administradores do repositório gerenciem os hooks post-receive de um repositório. Os webhooks podem ser gerenciados usando a API de HTTP do JSON ou a API de [SubHubbub](#PubSubHubbub).
 
-If you would like to set up a single webhook to receive events from all of your organization's repositories, see our API documentation for [Organization Webhooks](/rest/reference/orgs#webhooks).
+Se você deseja configurar um único webhook para receber eventos de todos os repositórios da organização, consulte nossa documentação de API para [Webhooks de organização](/rest/reference/orgs#webhooks).
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-### Receiving Webhooks
+### Receber Webhooks
 
-In order for {% data variables.product.product_name %} to send webhook payloads, your server needs to be accessible from the Internet. We also highly suggest using SSL so that we can send encrypted payloads over HTTPS.
+Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS.
 
-#### Webhook headers
+#### Cabeçalhos de webhook
 
-{% data variables.product.product_name %} will send along several HTTP headers to differentiate between event types and payload identifiers. See [webhook headers](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) for details.
+{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para obter informações.
 
 ### PubSubHubbub
 
-GitHub can also serve as a [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) hub for all repositories. PSHB is a simple publish/subscribe protocol that lets servers register to receive updates when a topic is updated. The updates are sent with an HTTP POST request to a callback URL.
-Topic URLs for a GitHub repository's pushes are in this format:
+O GitHub também pode servir como um centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos os repositórios. O PSHB é um simples protocolo de publicação/assinatura que permite o registro de servidores para receber atualizações quando um tópico é atualizado. As atualizações são enviadas com uma solicitação HTTP do tipo POST para uma URL de chamada de retorno. As URLs dos tópicos dos pushes de um repositório do GitHub estão neste formato:
 
 `https://github.com/{owner}/{repo}/events/{event}`
 
-The event can be any available webhook event. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)."
+O evento pode ser qualquer evento de webhook disponível. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/developers/webhooks-and-events/webhook-events-and-payloads)".
 
-#### Response format
+#### Formato de resposta
 
-The default format is what [existing post-receive hooks should expect](/post-receive-hooks/): A JSON body sent as the `payload` parameter in a POST.  You can also specify to receive the raw JSON body with either an `Accept` header, or a `.json` extension.
+O formato padrão é o que [os hooks post-receive existentes devem esperar](/post-receive-hooks/): Um texto JSON enviado como parâmetro `payload` em um POST.  Você também pode especificar para receber o texto do JSON sem processar com um cabeçalho `Aceitar` ou uma extensão `.json`.
 
     Accept: application/json
     https://github.com/{owner}/{repo}/events/push.json
 
-#### Callback URLs
+#### URLs de chamada de retorno
+As URLs de chamada de retorno podem usar o protocolo `http://`.
 
-Callback URLs can use the `http://` protocol. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %}You can also `github://` callbacks to specify a GitHub service.
+{% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.20" %}Você também pode fazer chamada de retorno `github://` para especificar um serviço do GitHub.
 {% data reusables.apps.deprecating_github_services_ghe %}
 {% endif %}
 
@@ -333,13 +319,12 @@ Callback URLs can use the `http://` protocol. {% if enterpriseServerVersions con
     http://postbin.org/123
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %}
-    # Send updates to Campfire
-    github://campfire?subdomain=github&room=Commits&token=abc123
+    # Send updates to Campfire github://campfire?subdomain=github&room=Commits&token=abc123
 {% endif %}
 
-#### Subscribing
+#### Assinar
 
-The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like:
+O ponto de extremidade do GitHub PubSubHubbub é: `{% data variables.product.api_url_code %}/hub`. Uma solicitação bem-sucedida com o curl parece como:
 
 ``` shell
 curl -u "user" -i \
@@ -349,13 +334,13 @@ curl -u "user" -i \
   -F "hub.callback=http://postbin.org/123"
 ```
 
-PubSubHubbub requests can be sent multiple times. If the hook already exists, it will be modified according to the request.
+Solicitações do PubSubHubbub podem ser enviadas várias vezes. Se o hook já existe, ele será modificado de acordo com a solicitação.
 
-##### Parameters
+##### Parâmetros
 
-Name | Type | Description
------|------|--------------
-``hub.mode``|`string` | **Required**. Either `subscribe` or `unsubscribe`.
-``hub.topic``|`string` |**Required**.  The URI of the GitHub repository to subscribe to.  The path must be in the format of `/{owner}/{repo}/events/{event}`.
-``hub.callback``|`string` | The URI to receive the updates to the topic.
-``hub.secret``|`string` | A shared secret key that generates a SHA1 HMAC of the outgoing body content.  You can verify a push came from GitHub by comparing the raw request body with the contents of the `X-Hub-Signature` header. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details.
+| Nome           | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                   |
+| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hub.mode`     | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`.                                                                                                                                                                                                                                                                                                                                                        |
+| `hub.topic`    | `string` | **Obrigatório**.  A URI do repositório do GitHub a ser assinada.  O caminho deve estar no formato `/{owner}/{repo}/events/{event}`.                                                                                                                                                                                                                                                                         |
+| `hub.callback` | `string` | A URI para receber as atualizações do tópico.                                                                                                                                                                                                                                                                                                                                                               |
+| `hub.secret`   | `string` | Uma chave secreta compartilhada que gera um HMAC de SHA1 do conteúdo do texto de saída.  Você pode verificar se um push veio do GitHub, comparando o texto da solicitação sem processamento com o conteúdo do cabeçalho `X-Hub-Signature`. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. |
diff --git a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..da26f8e248
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: Sobre o GitHub Sponsors
+intro: 'O {% data variables.product.prodname_sponsors %} permite à comunidade de desenvolvedores apoiar financeiramente as pessoas e organizações que projetam, criam e mantêm projetos de código aberto do qual dependem, diretamente no {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Sobre o {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)".
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+Quando você se tornar um desenvolvedor patrocinado ou uma organização patrocinada, termos adicionais para o {% data variables.product.prodname_sponsors %} se aplicam. Para obter mais informações, consulte "[Termos Adicionais do GitHub Sponsors [Patrocinadores do GitHub]](/github/site-policy/github-sponsors-additional-terms)."
+
+### Sobre o {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**Observação:** {% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+O {% data variables.product.prodname_matching_fund %} visa beneficiar os membros da comunidade {% data variables.product.prodname_dotcom %} que desenvolvem softwares de código aberto que promovem as [{% data variables.product.prodname_dotcom %}Diretrizes da Comunidade](/github/site-policy/github-community-guidelines). Pagamentos a organizações patrocinadas e pagamentos de organizações não são elegíveis para {% data variables.product.prodname_matching_fund %}.
+
+Para ser elegível para o {% data variables.product.prodname_matching_fund %}, você deve criar um perfil que atrairá uma comunidade que irá sustentar você a longo prazo. For more information about creating a strong profile, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."
+
+Donations between sponsored developers will not be matched.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### Compartilhando feedback sobre o {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### Leia mais
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
+- "[Perguntas frequentes com a equipe do {% data variables.product.prodname_sponsors %}](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" no {% data variables.product.prodname_blog %}
diff --git a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..aa4af740b4
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: Getting started with GitHub Sponsors
+intro: 'Saiba mais sobre {% data variables.product.prodname_sponsors %} e como você pode se envolver como patrocinador ou contribuidor de código aberto.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..a892d78ff1
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: Quickstart for finding contributors to sponsor
+intro: Learn some best practices for finding open source contributors to sponsor.
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### Explore projects you depend on
+
+As you consider where to find open source contributors to sponsor, consider starting at https://github.com/sponsors/community.
+
+If you're logged in, the sponsors results will start with public dependencies that your repositories depend on.
+
+![The Babel open source project with highlighted text that says "4 of your repositories depend on this"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+You can also toggle which of your accounts to view results for and further filter or search.
+
+![Search options on sponsors community search page](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### Explore whom others sponsor
+
+You can see whom a user or organization sponsors on their {% data variables.product.prodname_dotcom %} profile page.
+
+### Consider how you benefit from different contributions
+
+Consider whether you benefit from the work of open source contributions, such as:
+ - Documentação
+ - Design
+ - Translation
+ - Newsletters
+ - Code reviews
+ - Tutoriais
+ - Mentoring
+ - Triaging issues and helping with project management
+ - Answering questions
+ - Event planning
+
+For more information on different types of open source contributions, see the [Open source guide](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+You can check if contributors you've benefited from have {% data variables.product.prodname_sponsors %} profiles by using search at https://github.com/sponsors/community.
+
+### Search for a specific project or contributor
+
+At https://github.com/sponsors/community, you can search by ecosystem, most used, recently updated, and more. You can filter search results for your personal user account or for organizations that you're a member of.
+
+### Próximas etapas
+
+For more information on starting your sponsorship, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
diff --git a/translations/pt-BR/content/sponsors/guides.md b/translations/pt-BR/content/sponsors/guides.md
new file mode 100644
index 0000000000..560137d106
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Sponsors guides
+shortTitle: Guias
+intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/pt-BR/content/sponsors/index.md b/translations/pt-BR/content/sponsors/index.md
new file mode 100644
index 0000000000..efd1738d8a
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Sponsors Documentation
+shortTitle: GitHub Sponsors
+intro: 'Invest in the open source projects you depend on, support digital infrastructure, and make open source careers possible by sponsoring open source contributors and their projects. Build a {% data variables.product.prodname_sponsors %} profile and receive compensation for your open source work.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: 'sponsors'
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..6d9541856a
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: Configurando webhooks para eventos em sua conta patrocinada
+intro: Você pode configurar webhooks para alertá-lo quando receber novos patrocínios ou patrocinadores existentes fizerem alterações em seus patrocínios.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### Sobre webhooks para eventos da sua conta patrocinada
+
+Para monitorar as alterações de seus patrocínios, como os cancelamentos no final de um período de pagamento, você pode criar webhooks para sua conta de usuário ou organização patrocinada. Ao configurar um webhook para sua conta patrocinada, você receberá atualizações quando patrocinadores forem criados, editados ou excluídos. Para obter mais informações, consulte o [`evento de patrocínio` de webhook](/webhooks/event-payloads/#sponsorship).
+
+### Gerenciando webhooks para eventos na sua conta patrocinada
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..f7c71667da
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Getting started with the Sponsors GraphQL API
+intro: 'Using the GraphQL API, you can build custom integrations to manage or review your sponsorships.'
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+To get started with the GraphQL API, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+You can find the details about the Sponsors GraphQL API in the reference docs. For more information, see "[GraphQL reference](/graphql/reference)." We recommend using the GraphQL explorer to build your GraphQL calls. Para obter mais informações, consulte "[Usando o explorador](/graphql/guides/using-the-explorer).
diff --git a/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/index.md b/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..37e7055360
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: Integrating with GitHub Sponsors
+intro: 'As an open source contributor, you can build custom tools to manage your GitHub sponsorships.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..09e49a58a1
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: 'Sobre o GitHub Sponsors [Patrocinadores do GitHub] para contribuidores de código aberto'
+intro: 'Ao fornecer valor a um projeto de código aberto, você pode se tornar um contribuidor patrocinado para receber pagamentos pelo seu trabalho.'
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Ingressar no {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para obter mais informações, consulte "[Configurando o {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+Depois de se juntar ao {% data variables.product.prodname_sponsors %}, você poderá adicionar um botão de patrocinador ao repositório de código aberto com o qual você contribui, de modo a aumentar a visibilidade do perfil do seu {% data variables.product.prodname_sponsors %} e outras plataformas de financiamento. Para obter mais informações, consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)".
+
+Você pode definir uma meta para seus patrocínios. Para obter mais informações, consulte "[Gerenciar sua meta de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal)".
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### Níveis de patrocínio
+
+{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+
+É melhor criar uma série de diferentes opções de patrocínio, incluindo camadas mensais e únicas, para facilitar o apoio de qualquer pessoa ao seu trabalho. Em particular, os pagamentos únicos permitem que as pessoas recompensem os seus esforços sem se preocuparem se as suas finanças irão acomodar um calendário de pagamentos regular.
+
+### Pagamentos de patrocínios
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)."
+
+### Compartilhando feedback sobre o {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### Leia mais
+- "[Perguntas frequentes com a equipe do {% data variables.product.prodname_sponsors %}](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" no {% data variables.product.prodname_blog %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..c4ee2708b3
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: Entrar em contato com os patrocinadores
+intro: Você pode enviar um e-mail aos patrocinadores que aceitaram receber atualizações sobre seu trabalho.
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### Sobre atualizações de patrocínio
+
+Seus patrocinadores podem escolher se querem receber atualizações sobre seu trabalho por e-mail. Para obter mais informações, consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)".
+
+Para contas de desenvolvedor patrocinado, a atualização virá do endereço de e-mail principal da sua conta de usuário. Se você habilitou a privacidade do endereço de e-mail, em sua conta de usuário, a atualização virá de `noreply@github.com`. Para organizações patrocinadas, a atualização virá do endereço de e-mail `noreply@github.com` da organização. Para obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+
+### Entrar em contato com os patrocinadores
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..cb798a1452
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: 'Editando os detalhes do seu perfil para o GitHub Sponsors [Patrocinadores do GitHub]'
+intro: Você pode atualizar as informações que são visualizadas pelos possíveis patrocinadores sobre o seu trabalho.
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### Sobre os perfis dos patrocinadores
+
+Seu perfil do {% data variables.product.prodname_sponsors %} diz aos patrocinadores potenciais por que eles devem apoiá-lo. As pessoas veem seu perfil de patrocinador quando clicam no botão **Patrocinador** no seu perfil. Recomendamos incluir as seguintes informações.
+
+- Trabalho de código aberto para o qual você contribui
+- Por que você está comprometido com o desenvolvimento de código aberto
+
+### Editar as informações do seu perfil
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..0aba617ba4
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: Recebimento de patrocínios através do GitHub Sponsors (Patrocinadores do GitHub)
+shortTitle: Recebendo patrocínios
+intro: 'Você ou sua organização podem se tornar um colaborador de código aberto patrocinado para receber pagamentos pelo seu trabalho, atualize os detalhes de patrocínio, veja e entre em contato com seus patrocinadores.'
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..683dcb9a7d
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Gerenciar pagamentos do GitHub Sponsors
+intro: 'Você pode visualizar informações sobre pagamentos anteriores e futuros do {% data variables.product.prodname_sponsors %} e editar suas informações bancárias.'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### Sobre pagamentos do {% data variables.product.prodname_sponsors %}
+
+Só é possível gerenciar seus pagamentos {% data variables.product.prodname_sponsors %} se você for pago por meio do Stripe Connect. Se receber seus pagamentos na conta de usuário patrocinado por meio de transferência ACH ou eletrônica, você não verá a aba **Payouts** (Pagamentos) no painel de contribuidor de  código aberto. Organizações patrocinadas só podem usar o Stripe Connect para pagamentos. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_sponsors %} para contribuidores do código aberto](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)".
+
+{% data reusables.sponsors.payout-info %}
+
+### Visualizar e editar informações de pagamento
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..b3cb597c26
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: Gerenciando sua meta de patrocínio
+intro: Você pode definir uma meta para o seu desenvolvedor patrocinado ou conta da organização patrocinada para ajudar a comunidade a entender o impacto de patrocinar você.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### Sobre metas de patrocínio
+
+Você pode definir uma meta de financiamento para a sua conta patrocinada e compartilhar o objetivo com sua comunidade. Metas ajudam você a entender o impacto que você tem na comunidade de código aberto e construir sua presença no programa {% data variables.product.prodname_sponsors %}.
+
+Sua meta pode definir um objetivo para o número de patrocinadores que você deseja ter ou a quantidade de dinheiro que você quer ganhar a cada mês. Você só pode definir em uma meta de cada vez. Depois de atingir uma meta, você pode definir outra meta.
+
+### Definir uma meta
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Editando uma meta
+
+Ao editar uma meta, você não pode escolher uma meta que já atingiu. Por exemplo, se você já tem 5 patrocinadores, você não pode editar sua meta buscando 4 patrocinadores.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Removendo uma meta
+
+Depois de retirar uma meta, você não poderá reativá-la. Você deve criar uma nova meta em vez disso.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..e58c3248d8
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: Gerenciar as suas camadas de patrocínio
+intro: 'Você pode adicionar uma nova camada de patrocínio, ou editar ou retirar uma camada existente.'
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### Sobre as camadas de patrocínio
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### Adicionar uma camada
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### Editando ou retirar uma camada
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### Habilitar camadas com quantidades personalizadas
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### Desabilitar camadas com quantidades personalizadas
+
+Você pode desabilitar camadas com valores personalizados desmarcando a opção **Habilitar valores** personalizados na aba **Camadas de Sponsors**. Se você desabilitar quantidades personalizadas, todas as camadas personalizadas irão se tornar obsoletas..
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..6a1efbe3f2
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: Configurando o GitHub Sponsors (Patrocinadores do GitHub) para sua organização
+intro: 'Sua organização pode ingressar no {% data variables.product.prodname_sponsors %} para receber pagamentos pelo seu trabalho.'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### Ingressar no {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Depois de receber um convite para sua organização ingressar no {% data variables.product.prodname_sponsors %}, você poderá concluir as etapas abaixo para se tornar uma organização patrocinada.
+
+Para se juntar ao {% data variables.product.prodname_sponsors %} como colaborador individual fora de uma organização, consulte "[Configurando o {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. À direita da sua organização, clique em **Juntar-se à lista de espera**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### Preencher seu perfil de organização patrocinada
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Criar camadas de patrocínio
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Enviando informações bancárias
+
+Como organização patrocinada, você deve receber pagamentos em uma conta bancária exclusiva para sua organização em uma região apoiada. Você pode ter uma conta bancária jurídica por meio de serviços como [Open Collective](https://opencollective.com/) e [Stripe Atlas](https://stripe.com/atlas). A região em que sua organização opera legalmente e a região da sua conta bancária devem corresponder. A pessoa que criou o {% data variables.product.prodname_sponsors %} para a organização também deve morar na mesma região suportada. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+Para obter mais informações sobre como configurar o Stripe Connect usando o Open Collective, consulte [Configurando {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) no Open Collective Docs.
+
+### Enviando suas informações fiscais
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Habilitar a autenticação de dois fatores (2FA, two-factor authentication) na sua conta do {% data variables.product.prodname_dotcom %}
+
+Antes da sua organização se tornar uma organização patrocinada, você deve habilitar a 2FA na sua conta do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)".
+
+### Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### Leia mais
+- [Sobre o {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..32a2281317
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: Configurando o GitHub Sponsors (Patrocinadores do GitHub) para sua conta de usuário
+intro: 'Você pode se tornar um desenvolvedor patrocinado ingressando no {% data variables.product.prodname_sponsors %}, preenchendo seu perfil de desenvolvedor patrocinado, criando camadas de patrocínio, enviando informações bancárias e fiscais, bem como habilitando a autenticação de dois fatores na sua conta do {% data variables.product.prodname_dotcom %}.'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### Ingressar no {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+Para aderir ao {% data variables.product.prodname_sponsors %} como organização, consulte "[Configurando o {% data variables.product.prodname_sponsors %} para sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. Se você é o proprietário de uma organização, você tem mais de uma conta elegível. Clique em **Ver suas contas elegíveis**, depois na lista de contas, encontrar sua conta de usuário.
+3. Clique em **Join the waitlist ** (Entrar para a lista de espera).
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+Se você tiver uma conta bancária em uma região aceita, o {% data variables.product.prodname_dotcom %} irá rever sua solicitação dentro de duas semanas.
+
+### Preencher seu perfil de desenvolvedor patrocinado
+
+Depois de {% data variables.product.prodname_dotcom %} avaliar sua solicitação, você pode configurar o seu perfil de desenvolvedor patrocinado para que as pessoas possam começar a patrocinar você.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Criar camadas de patrocínio
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Enviando informações bancárias
+
+Se você vive em uma região aceita, você pode seguir essas instruções para enviar informações bancárias criando uma conta do Stripe Connect. A sua região de residência e a região da sua conta bancária devem corresponder. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### Enviando suas informações fiscais
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Habilitar a autenticação de dois fatores (2FA, two-factor authentication) na sua conta do {% data variables.product.prodname_dotcom %}
+
+Antes de se tornar um desenvolvedor patrocinado, você deve habilitar a 2FA em sua conta do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)".
+
+### Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. Clique em **Request approval** (Solicitar aprovação). ![Botão Request approval (Solicitar aprovação)](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..a8f251746c
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Informações fiscais para os Patrocinadores do GitHub
+intro: 'Os desenvolvedores patrocinados e as organizações devem enviar informações fiscais para {% data variables.product.prodname_dotcom %} e são responsáveis por avaliar e pagar seus próprios impostos.'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+Se você é contribuinte nos Estados Unidos, deve enviar um formulário W-9 antes de poder receber pagamentos. Se você é contribuinte em qualquer outro país, deve enviar um formulário W-8BEN antes de poder receber pagamentos. Para mais informações, consulte "[Configurando {% data variables.product.prodname_sponsors %} para sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" e "[Configurando {% data variables.product.prodname_sponsors %} para sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} lhe enviará os formulários apropriados, avisando quando estiverem vencidos, e lhe dará um tempo razoável para completar e enviar os formulários.
+
+If you are a taxpayer in the United States and earn more than $600 USD in a tax year, {% data variables.product.prodname_dotcom %} will send you a 1099 before January 31 of the next calendar year. Não fornecemos formulários de impostos para contribuintes internacionais.
+
+O {% data variables.product.prodname_dotcom %} não retém impostos de pagamentos de {% data variables.product.prodname_sponsors %}. Os desenvolvedores patrocinados são responsáveis por avaliar e pagar seus próprios impostos.
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### Leia mais
+
+- [Exibir patrocinadores e patrocínios](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..3211a88736
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: Exibir patrocinadores e patrocínios
+intro: Você pode ver e exportar informações detalhadas e análises sobre seus patrocinadores e patrocínios.
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### Sobre patrocinadores e patrocínios
+
+Você pode ver a análise sobre seus patrocínios atuais e anteriores, os pagamentos que recebeu de patrocinadores e eventos, como cancelamentos e mudanças na camada dos patrocinadores para seus patrocínios. Você também pode visualizar as atividades, tais como novos patrocinadores, alterações e cancelamentos nos patrocínios. Você pode filtrar a lista de atividades por data. Você também pode exportar dados de patrocínio para a conta que você está visualizando em formato CSV ou JSON.
+
+### Exibir patrocinadores e patrocínios
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. Como alternativa, para filtrar os patrocinadores por nível, use o menu suspenso **Filter** (Filtro), clique em **Active tiers** (Níveis ativos) ou **Retired tiers** (Níveis removidos) e selecione um nível. ![Menu suspenso para filtrar por nível](/assets/images/help/sponsors/filter-drop-down.png)
+
+### Visualizando atividade de patrocínio recente
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### Exportando seus dados de patrocínio
+
+Você pode exportar suas transações de patrocínio por mês. {% data variables.product.company_short %} enviará um e-mail com dados de transação para todos os seus patrocinadores do mês que você selecionar. Depois que a exportação estiver concluída, você poderá exportar mais um mês de dados. Você pode exportar até 10 conjuntos de dados por hora para qualquer uma das suas contas patrocinadas.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. Clique em {% octicon "download" aria-label="The download icon" %} **Exportar**. ![Botão de exportação](/assets/images/help/sponsors/export-all.png)
+1. Escolha um período de tempo e um formato para os dados que você gostaria de exportar e, em seguida, clique em **Iniciar a exportação**. ![Opções de Exportar dados](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..8f4ca9614d
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: Atribuir patrocínios à sua organização
+intro: Você pode atribuir os patrocínios pagos por uma das suas organizações a outra organização.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. Acesse a organização cujos patrocínios você deseja atribuir a outra organização.
+2. No nome da sua organização, clique em {% octicon "heart" aria-label="The heart icon" %} **Patrocínio**. ![Aba "Patrocínio"](/assets/images/help/sponsors/sponsoring-tab.png)
+1. No canto superior direito, clique em {% octicon "gear" aria-label="The gear icon" %} **Configurações**. ![Botão "Configurações"](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. Em "Vincular patrocínios a outra conta", use o menu suspenso e, em seguida, clique na organização à qual você deseja que os patrocínios desta organização sejam atribuídos. ![Menu suspenso para selecionar conta](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. Clique em **Vincular conta**. ![Botão "Vincular conta"](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..8d2ec53f55
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: Patrocinando um colaborador de código aberto
+intro: 'Você pode patrocinar colaboradores, receber atualizações sobre os desenvolvedores e organizações que você patrocina e exibir um selo de patrocinador através do {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..679b5fa884
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: Gerenciar o patrocínio
+intro: Você pode gerenciar quem pode ver seu patrocínio e se você recebe atualizações de e-mail de uma conta patrocinada.
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Gerenciar as configurações de privacidade para seu patrocínio
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Gerenciar atualizações de e-mail para seu patrocínio
+
+Você pode escolher se uma conta que você patrocina pode enviar para você atualizações de e-mail sobre o trabalho deles. A conta patrocinada não terá acesso ao seu endereço de e-mail.
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Leia mais
+
+- "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)"
+- "[Fazer o downgrade de um patrocínio](/articles/downgrading-a-sponsorship)"
diff --git a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..899cb6e624
--- /dev/null
+++ b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: Patrocinando um colaborador de código aberto
+intro: 'Você pode fazer um pagamento recorrente mensal a um desenvolvedor ou uma organização que projeta, cria ou mantém projetos de código aberto dos quais você depende.'
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Sobre patrocínios
+
+{% data reusables.sponsors.sponsorship-details %}
+
+Você pode patrocinar uma conta em nome de sua conta de usuário para investir em projetos dos quais você se beneficia pessoalmente. Você pode patrocinar uma conta em nome de sua organização por muitas razões.
+- Sustentar bibliotecas específicas das quais o trabalho da sua organização depende
+- Investir no ecossistema com o qual você conta como uma organização (como a blockchain)
+- Desenvolver a conscientização da marca como uma organização que valoriza o código aberto
+- Agradecer aos desenvolvedores de código aberto para a criação de bibliotecas que complementam os produtos que a sua organização oferece
+
+Você pode usar um cartão de crédito para patrocinar uma conta em {% data variables.product.product_name %}. Se sua organização desejar pagar por fatura, [entre em contato conosco](https://support.github.com/contact/org-sponsors-waitlist).
+
+{% data reusables.sponsors.no-fees %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)".
+
+Ao patrocinar uma conta usando um cartão de crédito, a alteração entrará em vigor imediatamente. {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+Se a conta patrocinada for retirada, a sua camada permanecerá em vigor para você até que você escolha uma camada diferente ou cancele a sua assinatura. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)".
+
+Se a conta que você deseja patrocinar não tiver um perfil em {% data variables.product.prodname_sponsors %}, você pode incentivar que participe. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_sponsors %} para a sua conta de usuário](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" e "[Configurando {% data variables.product.prodname_sponsors %} para sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**Nota:** O {% data variables.product.prodname_dotcom %} não é responsável por como os desenvolvedores representam a si mesmos nem {% data variables.product.prodname_dotcom %} endossa quaisquer projetos de código aberto patrocinados. As reivindicações são de responsabilidade exclusiva do desenvolvedor que recebe os fundos. Certifique-se de confiar em uma pessoa antes de oferecer um patrocínio. Para obter mais informações, consulte "[{% data variables.product.prodname_sponsors %} Termos Adicionais ](/github/site-policy/github-sponsors-additional-terms).
+
+{% endnote %}
+
+### Patrocinar uma conta
+
+Antes de poder patrocinar uma conta, você deve ter um endereço de e-mail verificado. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)".
+
+1. Em {% data variables.product.product_name %}, acesse o perfil do usuário ou organização que deseja patrocinar.
+1. Acesse o painel de patrocínio para a conta.
+   - Para patrocinar um desenvolvedor, sob o nome do desenvolvedor, clique em **Patrocinador**. ![Botão Sponsor (Patrocinar)](/assets/images/help/profile/sponsor-button.png)
+   - Para patrocinar uma organização clique em **Patrocinador** à direita do nome da organização. ![Botão Sponsor (Patrocinar)](/assets/images/help/sponsors/sponsor-org-button.png)
+1. Opcionalmente, no lado direito da página, para patrocinar a conta em nome da sua organização, use o menu suspenso **Patrocinar como** e clique na organização. ![Menu suspenso para escolher a conta que você irá patrocinar como](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![Botão para editar pagamento](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![Botões de opção para escolher quem pode ver seu patrocínio](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml
index 1f4536ced6..bea4ea19ab 100644
--- a/translations/pt-BR/data/glossaries/external.yml
+++ b/translations/pt-BR/data/glossaries/external.yml
@@ -1,7 +1,7 @@
 ---
 - 
   term: '@menção'
-  description: notificar uma pessoa no GitHub adicionando `@` antes do nome de usuário. Os usuários de uma organização no GitHub também podem integrar uma equipe que pode ser mencionada.
+  description: Notificar uma pessoa no GitHub adicionando `@` antes do nome de usuário. Os usuários de uma organização no GitHub também podem integrar uma equipe que pode ser mencionada.
 - 
   term: token de acesso
   description: >-
@@ -181,7 +181,7 @@
 - 
   term: branch padrão
   description: >-
-    O branch de base para novos pull requests e commits de código em um repositório. Cada repositório tem pelo menos um branch, que o Git cria quando você inicializa o repositório. O primeiro branch é geralmente denominado `main`, e é, muitas vezes, o branch-padrão.
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}, and is often the default branch.
 - 
   term: gráfico de dependentes
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    Branch de desenvolvimento padrão. Sempre que um repositório do Git é criado, um branch "principal" também é criado e passa a ser o branch ativo. Contém o desenvolvimento local na maioria dos casos, embora isso ocorra meramente por convenção e não seja obrigatório.
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.{% else %}Name often chosen as an alternative to `master` for the default branch of a repository.{% endif %}
 - 
   term: mestre
   description: >-
-    O branch padrão em muitos repositórios do Git. Por padrão, ao criar um novo repositório do Git na linha de comando um branch denominado "mestre" é criado. Muitas ferramentas agora usam um nome alternativo para o branch padrão. Por exemplo, quando você cria um novo repositório no GitHub, a branch padrão é chamada de "principal".
+    The default branch in many Git repositories. By default, when you create a new Git repository on the command line, a branch called `master` is created. Many tools now use an alternative name for the default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} For example, when you create a new repository on GitHub, the default branch is called `main`.{% endif %}
 - 
   term: gráfico de integrantes
   description: Gráfico que exibe todas as bifurcações de um repositório.
diff --git a/translations/pt-BR/data/glossaries/internal.yml b/translations/pt-BR/data/glossaries/internal.yml
index 5980c780f9..2cdcb9dc1d 100644
--- a/translations/pt-BR/data/glossaries/internal.yml
+++ b/translations/pt-BR/data/glossaries/internal.yml
@@ -60,6 +60,10 @@
 - 
   term: Azure
   description: Plataforma de computação em nuvem da Microsoft.
+- 
+  term: Azure DevOps
+  description: >-
+    A Microsoft product offering source code hosting, issues, CI/CD pipelines, and other developer services. The on-premises version was formerly known as Team Foundation Server. The cloud-hosted version was formerly known as Visual Studio Team Services.
 - 
   term: repositório bare
   description: >-
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    Produto da Microsoft que oferece gerenciamento de código-fonte e outros serviços de equipe.
+    The former name of a Microsoft product that provides source code management and other team services. Now known as Azure DevOps Server.
 - 
   term: Textile
   description: >-
diff --git a/translations/pt-BR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/pt-BR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..5627a1d7db
--- /dev/null
+++ b/translations/pt-BR/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: Acesso à exclusão de versão pacote
+  description: >-
+    Esta pré-visualização adiciona suporte para a mudança do DeletePackageVersion que permite a exclusão de versões privadas de pacotes.
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: Implantações
+  description: >-
+    Esta visualização adiciona suporte para mudanças e novos recursos nos deployments.
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - Mais informações detalhadas sobre o estado de merge de uma pull request.
+  description: >-
+    Esta visualização adiciona suporte para acessar campos que fornecem informações mais detalhadas sobre o estado de merge de uma pull request.
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - Atualiza vários refs em uma única operação.
+  description: Essa pré-visualização adiciona suporte para atualizar múltiplas refs em uma única operação.
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: Detalhes Tarefa Projeto
+  description: >-
+    Esta visualização adiciona detalhes de projeto, cartão de projeto e coluna de projetos para eventos de questões relacionadas ao projeto.
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: Criar anexos de conteúdo
+  description: Esta visualização adiciona suporte para a criação de anexos de conteúdo.
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: Visualização de Etiquetas
+  description: >-
+    Esta visualização adiciona suporte para adicionar, atualizar, criar e excluir etiquetas.
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: Importar Projeto
+  description: Esta visualização adiciona suporte para a importação de projetos.
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Pré-visualização da Revisão da Equipe
+  description: >-
+    Esta pré-visualização adiciona suporte para atualizar as configurações da atribuição de revisão de equipe.
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/pt-BR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..65bf5b1ce0
--- /dev/null
+++ b/translations/pt-BR/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate` será removido. Use `uploadUrl` em vez disso.'
+    reason: '''uploadUrlTemplate'' está sendo removido porque não é uma URL padrão e adiciona um passo extra do usuário.'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user` será removido. Use o campo `assignee`.'
+    reason: Os responsáveis podem agora ser mannequines.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.'
+    reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.'
+    reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: '`user` será removido. Use o campo `assignee`.'
+    reason: Os responsáveis podem agora ser mannequines.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: '`maintainer` será removido. Use `Sponsorship.sponsorable` em vez disso.'
+    reason: '`Sponsorship.maintainer` será removido.'
+    date: 'RegistryPackageDependency.dependencyType'
+    criticality: breaking
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: '`isUnlicensed` será removido.'
+    reason: Todos os integrantes pendentes consomem uma licença
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.'
+    reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado.
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: '`timeline` será removido. Use Issue.timelineItems em vez disso.'
+    reason: '`timeline` será removido'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.'
+    reason: '`timeline` será removido'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: '`INVITEE_LOGIN` será removido.'
+    reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: '`sponsor` será removido. Use `Sponsorship.sponsorEntity` em vez disso.'
+    reason: '`Sponsorship.sponsor` será removido.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: '`isUnlicensed` será removido.'
+    reason: Todos os integrantes consomem uma licença
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` será removido.'
+    reason: Todos os colaboradores externos consomem uma licença
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` será removido.'
+    reason: Todos os colaboradores pendentes consomem uma licença
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: 'O `DRAFT` será removido. Use PullRequest.isDraft.'
+    reason: O status DRAFT será removido deste enum e o `isDraft` deverá ser usado
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nplasterer
diff --git a/translations/pt-BR/data/learning-tracks/README.md b/translations/pt-BR/data/learning-tracks/README.md
index 598fdfa116..7611f2d506 100644
--- a/translations/pt-BR/data/learning-tracks/README.md
+++ b/translations/pt-BR/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # Trilhos de aprendizado (também conhecido como caminhos de aprendizado)
 
-Os trilhos de aprendizado são uma coleção de artigos que ajudam você a dominar um assunto específico. Os caminhos de aprendizado são definidos por produto.
\ No newline at end of file
+Os trilhos de aprendizado são uma coleção de artigos que ajudam você a dominar um assunto específico. Os caminhos de aprendizado são definidos por produto. For example, see https://docs.github.com/en/actions/guides.
+
+Learning track data for a product is defined in two places:
+
+1. A simple array of learning track names is defined in the product sublanding index page frontmatter.
+
+    For example, in `content/actions/guides/index.md`:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. Additional data for each track is defined in a YAML file named for the **product** in the `data` directory.
+
+    For example, in `data/learning-tracks/actions.yml`, each of the items from the content file's `learningTracks` array is represented with additional data such as `title`, `description`, and an array of `guides` links.
+
+    One learning track in this YAML **per version** must be designated as a "featured" learning track via `featured_track: true`, which will set it to appear at the top of the product sublanding page. A test will fail if this property is missing.
+
+    The `featured_track` property can be a simple boolean (i.e., `featured_track: true`) or it can be a string that includes versioning statements (e.g., `featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`). If you use versioning, you'll have multiple `featured_track`s per YML file, but make sure that only one will render in each currently supported version. A test will fail if there are more or less than one featured link for each version.
+
+Versioning for learning tracks is processed at page render time. The code lives in [`lib/learning-tracks.js`](lib/learning-tracks.js), which is called by `page.render()`. The processed learning tracks are then rendered by `layouts/product-sublanding.html`.
+
+The schema for validating the learning track YAML lives in [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) and is exercised by [`tests/content/lint-files.js`](tests/content/lint-files.js).
diff --git a/translations/pt-BR/data/learning-tracks/actions.yml b/translations/pt-BR/data/learning-tracks/actions.yml
index 832b11e287..d46cc8501d 100644
--- a/translations/pt-BR/data/learning-tracks/actions.yml
+++ b/translations/pt-BR/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: 'Criar e testar código'
   description: 'É possível criar fluxos de trabalho personalizados de integração contínua (CI) diretamente no seu repositório.'
diff --git a/translations/pt-BR/data/learning-tracks/admin.yml b/translations/pt-BR/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..a757d9cb4b
--- /dev/null
+++ b/translations/pt-BR/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: 'Primeiros passos com {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/pt-BR/data/release-notes/2-21/19.yml b/translations/pt-BR/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..66280dc78c
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/2-21/19.yml
@@ -0,0 +1,18 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - O usuário visualizou a mensagem 500 error ao executar operações no git em uma instância configurada com autenticação do LDAP.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando.
diff --git a/translations/pt-BR/data/release-notes/2-21/20.yml b/translations/pt-BR/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..b541c5d2e4
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/2-21/20.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando.
diff --git a/translations/pt-BR/data/release-notes/2-21/21.yml b/translations/pt-BR/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..50268eff2d
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/2-21/21.yml
@@ -0,0 +1,15 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando.
diff --git a/translations/pt-BR/data/release-notes/2-22/11.yml b/translations/pt-BR/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..6efb54ebcd
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/2-22/11.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Syntax highlighting could fail due to the Treelights container running out of memory.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
diff --git a/translations/pt-BR/data/release-notes/2-22/12.yml b/translations/pt-BR/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..f7492d7e23
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/2-22/12.yml
@@ -0,0 +1,22 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
diff --git a/translations/pt-BR/data/release-notes/2-22/13.yml b/translations/pt-BR/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..dc01586703
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/2-22/13.yml
@@ -0,0 +1,20 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
diff --git a/translations/pt-BR/data/release-notes/3-0/0.yml b/translations/pt-BR/data/release-notes/3-0/0.yml
index 93c736f550..3a10ac7665 100644
--- a/translations/pt-BR/data/release-notes/3-0/0.yml
+++ b/translations/pt-BR/data/release-notes/3-0/0.yml
@@ -121,6 +121,7 @@ sections:
     - A race condition can cause dependency graph database migrations to appear to fail.
     - Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.
     - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.'
   deprecations:
     - heading: Depreciação do GitHub Enterprise Server 2.19
       notes:
diff --git a/translations/pt-BR/data/release-notes/3-0/1.yml b/translations/pt-BR/data/release-notes/3-0/1.yml
index 400c502c14..2c4b45b9fd 100644
--- a/translations/pt-BR/data/release-notes/3-0/1.yml
+++ b/translations/pt-BR/data/release-notes/3-0/1.yml
@@ -45,6 +45,7 @@ sections:
     - 'Dependency graph fails to parse `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.'
     - 'Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.'
     - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.'
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/pt-BR/data/release-notes/3-0/2.yml b/translations/pt-BR/data/release-notes/3-0/2.yml
index 98c723e739..04ff5febd9 100644
--- a/translations/pt-BR/data/release-notes/3-0/2.yml
+++ b/translations/pt-BR/data/release-notes/3-0/2.yml
@@ -30,6 +30,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.'
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/pt-BR/data/release-notes/3-0/3.yml b/translations/pt-BR/data/release-notes/3-0/3.yml
index 05e75349d6..41e6ae75ec 100644
--- a/translations/pt-BR/data/release-notes/3-0/3.yml
+++ b/translations/pt-BR/data/release-notes/3-0/3.yml
@@ -30,6 +30,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
       To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
diff --git a/translations/pt-BR/data/release-notes/3-0/4.yml b/translations/pt-BR/data/release-notes/3-0/4.yml
index 577ca023dc..eee917ab2d 100644
--- a/translations/pt-BR/data/release-notes/3-0/4.yml
+++ b/translations/pt-BR/data/release-notes/3-0/4.yml
@@ -23,3 +23,4 @@ sections:
     - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/pt-BR/data/release-notes/3-0/5.yml b/translations/pt-BR/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..233cb643b2
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/3-0/5.yml
@@ -0,0 +1,27 @@
+---
+date: '2021-04-14'
+intro: 'Os requisitos mínimos de infraestrutura aumentaram para {% data variables.product.prodname_ghe_server %} 3.0+. Para obter mais informações, consulte "[Sobre requisitos mínimos para o GitHub Enterprise Server 3.0 e posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Some logs were not included in the log forwarding configuration.
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Pages were not getting published when using custom CA certificate.
+    - Packages related subdomains were not showing up in the "Test domain settings" prompt for subdomain isolation.
+    - The `X-GitHub-Enterprise-Host` header sent with webhooks included a random string, rather than the hostname of the GitHub Enterprise Server instance that sent the HTTP POST payload.
+    - Upgrading from 2.22.x to 3.0.x would fail if GitHub Actions had previously been enabled, but disabled before the upgrade.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - reStructuredText (RST) rendering in the web UI would fail and instead displayed raw RST markup text.
+    - Email notifications for Secret Scanning alerts were not sent to authorized users when the Dependency Graph was not fully enabled.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+    - Jupyter notebooks with non-ASCII characters could fail to render.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/pt-BR/data/release-notes/3-0/6.yml b/translations/pt-BR/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..bc39c6a2c6
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/3-0/6.yml
@@ -0,0 +1,30 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - Upgrades did not include the latest version of Actions runner properly installed.
+    - '`github-env` configuration could result in zombie processes.'
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - The Create Repository button was disabled for users who belonged to more than 50 organizations.
+    - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful.
+    - The `rms-packages` index was shown in the site admin dashboard.
+    - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form.
+    - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+    - Code Scanning backend services did not start up reliably after applying hotpatches.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
diff --git a/translations/pt-BR/data/release-notes/3-0/7.yml b/translations/pt-BR/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..f5cbc61dcf
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/3-0/7.yml
@@ -0,0 +1,23 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Os pacotes foram atualizados para as últimas versões de segurança.
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
diff --git a/translations/pt-BR/data/release-notes/3-1/0-rc1.yml b/translations/pt-BR/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..41ef77e7df
--- /dev/null
+++ b/translations/pt-BR/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security Secret Scanning
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository.
+
+          This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}:
+
+          - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37
+          - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)
+          - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets
+          - Updated the index view to made it easy to triage secrets in bulk
+          - Reduced the false positive rate on many patterns
+
+          Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+    - 
+      heading: GitHub Advanced Security billing improvements
+      notes:
+        - |
+          This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}:
+
+          - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+          - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+    - 
+      heading: Dependabot improvements
+      notes:
+        - |
+          This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}:
+
+          - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
+          - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository).
+          - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."'
+    - 
+      heading: GitHub Actions Workflow Visualization beta
+      notes:
+        - |
+
+          GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can:
+          - View and understand complex workflows
+          - Track progress of workflows in real-time
+          - Troubleshoot runs quickly by easily accessing logs and jobs metadata
+          - Monitor progress of deployment jobs and easily access deployment targets
+
+          For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+    - 
+      heading: OAuth 2.0 Device Authorization Grant
+      notes:
+        - |
+          [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser.
+
+          Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow.
+    - 
+      heading: Merge automático de pull request
+      notes:
+        - |
+          With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+    - 
+      heading: Custom notifications
+      notes:
+        - |
+          You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+  changes:
+    - 
+      heading: Alterações na administração
+      notes:
+        - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+        - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+        - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+        - Check annotations older than four months will be archived.
+    - 
+      heading: Alterações de segurança
+      notes:
+        - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).'
+        - SARIF upload support increased to a maximum of 5000 results per upload.
+    - 
+      heading: Alterações de desenvolvedor
+      notes:
+        - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to.
+        - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)."
+        - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."'
+        - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.'
+        - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.'
+    - 
+      heading: Alterações de API
+      notes:
+        - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning).
+        - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints.
+  known_issues:
+    - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - As regras personalizadas de firewall não são mantidas durante uma atualização.
+    - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.20
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.21
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Obsolescência de Eventos de Webhook de legado do aplicativo GitHub
+      notes:
+        - 'Começando com {% data variables.product.prodname_ghe_server %} 2.21.0, dois eventos legados de webhook relacionados a aplicativos GitHub foram descontinuados e serão removidos em {% data variables.product.prodname_ghe_server %} 3.2.0. Os eventos obsoletos `integration_installation` e `integration_installation_repositories` têm eventos equivalentes que serão compatíveis. Mais informações estão disponíveis no [post do blogue de anúncio de obsolescência](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).'
+    - 
+      heading: Obsolescência do ponto de extremidade de legado dos aplicativos GitHub
+      notes:
+        - Começando com {% data variables.product.prodname_ghe_server %} 2.21, o ponto de extremidade do legado dos aplicativos GitHub para a criação de tokens de acesso de instalação foi suspenso e será removido em {% data variables.product.prodname_ghe_server %} 3.2.0. Mais informações estão disponíveis no [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).
+    - 
+      heading: Obsolescência da API do aplicativo OAuth
+      notes:
+        - 'O GitHub não é compatível mais com os pontos de extremidade do aplicativo OAuth que contêm `access_token` como um parâmetro de caminho. Nós introduzimos novos pontos de extremidade que permitem que você gerencie, com segurança, tokens para aplicativos OAuth movendo `access_token` para o texto da solicitação. Embora obsoleto, os pontos de extremidade ainda podem ser acessados nesta versão. Queremos remover esses pontos de extremidade em {% data variables.product.prodname_ghe_server %} 3.4. Para obter mais informações, consulte [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).'
+    - 
+      heading: Deprecation of GitHub Actions short SHA support
+      notes:
+        - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/pt-BR/data/reusables/actions/actions-cli.md b/translations/pt-BR/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..9de328800e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+For information on setting up {% data variables.product.prodname_cli %}, see "[Managing GitHub Actions with GitHub CLI](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)."
diff --git a/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md b/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..493e81cb45
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.
+
+##### Examples using concurrency and the default behavior
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### Example using concurrency to cancel any in-progress job or run
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/pt-BR/data/reusables/actions/concurrency-beta.md b/translations/pt-BR/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..c3f2c9a831
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Concurrency is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/actions/enterprise-github-connect-warning.md b/translations/pt-BR/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..ce755253ef
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom %}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/actions/enterprise-no-internet-actions.md b/translations/pt-BR/data/reusables/actions/enterprise-no-internet-actions.md
index 4fa97816b0..9c46405edd 100644
--- a/translations/pt-BR/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/pt-BR/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-O {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} é projetado para funcionar em ambientes sem acesso à Internet. Por padrão, os fluxos de trabalho não podem usar ações de {% data variables.product.prodname_dotcom_the_website %} e [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+{% data variables.product.prodname_actions %} on {% data variables.product.product_name %} is designed to work in environments without full internet access. Por padrão, os fluxos de trabalho não podem usar ações de {% data variables.product.prodname_dotcom_the_website %} e [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
diff --git a/translations/pt-BR/data/reusables/actions/forked-secrets.md b/translations/pt-BR/data/reusables/actions/forked-secrets.md
index 0132f98a4a..d191dda549 100644
--- a/translations/pt-BR/data/reusables/actions/forked-secrets.md
+++ b/translations/pt-BR/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-Com exceção do `GITHUB_TOKEN`, os segredos não são disponibilizados para o executor quando um fluxo de trabalho é acionado a partir de um repositório bifurcado.
+Com exceção do `GITHUB_TOKEN`, os segredos não são disponibilizados para o executor quando um fluxo de trabalho é acionado a partir de um repositório bifurcado.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..5339a97951
--- /dev/null
+++ b/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+Registramos e exibimos dois números de committers para {% data variables.product.prodname_GH_advanced_security %} em {% data variables.product.product_location %}:
+
+- **Committers** is the number of committers who contributed to at least one {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository in an organization and who use a seat in your enterprise license. Ou seja, eles também são integrantes da organização, um colaborador externo ou têm um convite pendente para ingressar em uma organização na sua empresa.
+- **Único para este repositório/organização** é o número de committers que contribuíram apenas para este repositório ou para repositórios nesta organização. Este número mostra a quantidade de estações de licença que você pode liberar, desabilitando {% data variables.product.prodname_GH_advanced_security %} para esse repositório ou organização.
+
+If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Desabilitar o recurso para esse repositório ou organização não liberaria nenhuma estação na sua licença.
+
+When you remove a user from your enterprise account, the user's license is freed within 24 hours.
+
+{% note %}
+
+**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
+
+{% endnote %}
diff --git a/translations/pt-BR/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/pt-BR/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..ec4d94b8a4
--- /dev/null
+++ b/translations/pt-BR/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+Cada licença de {% data variables.product.prodname_GH_advanced_security %} especifica um número máximo de contas, ou estações, que podem usar essas funcionalidades. Periodicamente você deve verificar que sua utilização está dentro da sua capacidade de licença.
diff --git a/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md
index b6abfe68c7..1b77a9051e 100644
--- a/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% endif %}
+{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% elsif currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your Enterprise](/admin/advanced-security)."{% endif %}
 
 You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose.
 
diff --git a/translations/pt-BR/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/pt-BR/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..bf5e38e0ae
--- /dev/null
+++ b/translations/pt-BR/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+Ao decidir quais repositórios e organizações priorizar para {% data variables.product.prodname_GH_advanced_security %}, você deverá revisá-los e identificá-los:
+
+- As bases de código que são as mais críticas para o sucesso da sua empresa. Esses são os projetos em que a introdução de códigos vulneráveis, segredos codificados ou dependências vulneráveis teriam o maior impacto na sua empresa.
+- Bases de código com a maior frequência de commit. Estes são os projetos mais ativamente desenvolvidos e, consequentemente, há um risco maior de poder introduzir problemas de segurança.
+
+Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para essas organizações ou repositórios, você deverá avaliar quais outras bases de código você poderia adicionar sem adicionar quaisquer committers adicionais exclusivos e utilizando mais estações na sua licença. Depois disso, reveja as próximas bases de código mais importantes e ocupadas. Se você deseja aumentar o número de estações na sua licença, entre em contato com {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/pt-BR/data/reusables/advanced-security/ghas-helps-developers.md b/translations/pt-BR/data/reusables/advanced-security/ghas-helps-developers.md
index 32514f5c7a..e1b69b9a6e 100644
--- a/translations/pt-BR/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/pt-BR/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)".
+{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/pt-BR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..1a65031cec
--- /dev/null
+++ b/translations/pt-BR/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+When you enable or disable {% data variables.product.prodname_advanced_security %} for repositories, {% data variables.product.prodname_dotcom %} displays an overview of changes to the use of your license. Se você desabilitar o acesso a {% data variables.product.prodname_GH_advanced_security %}, todas as estações usadas por committers "únicos" serão liberadas.
+
+Se você exceder limite de licença, {% data variables.product.prodname_GH_advanced_security %} irá continuar a funcionar em todos os repositórios onde já está habilitado. No entanto, em organizações onde {% data variables.product.prodname_GH_advanced_security %} está habilitado para novos repositórios, os repositórios serão criados com o recurso desabilitado. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available.{% if currentVersion == "free-pro-team@latest" %} If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.{% endif %}
+
+Assim que você liberar algumas estações, desabilitando {% data variables.product.prodname_GH_advanced_security %} para alguns repositórios ou aumentando o tamanho da sua licença, as opções para habilitar {% data variables.product.prodname_GH_advanced_security %} funcionarão de novo normalmente.
diff --git a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md
index 26ea19355f..437c1acc2f 100644
--- a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md
+++ b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md
@@ -1,9 +1,9 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 {% warning %}
 
-**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %}  For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/).
+**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá descontinuar a autenticação para a API usando parâmetros de consulta. A autenticação para a API deve ser feita com a [autenticação básica HTTP](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Usar parâmetros de consulta para efetuar a autenticação na API não funcionará mais a partir de 5 de maio de 2021. {% endif %}  Para mais informações, incluindo brownouts agendadas, veja [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/).
 
-{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %}
+{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %} Autenticação na API usando parâmetros de consulta enquanto disponível não é mais compatível devido a questões de segurança. Em vez disso, recomendamos que integradores movam seu token de acesso, `client_id`, or `client_secret` no cabeçalho. {% data variables.product.prodname_dotcom %} anunciará a remoção da autenticação por parâmetros de consulta com aviso prévio. {% endif %}
 
 {% endwarning %}
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/cli/actions-cli-version.md b/translations/pt-BR/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..83cd5971dd
--- /dev/null
+++ b/translations/pt-BR/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+To access all of the {% data variables.product.prodname_actions %}-related commands, you must use version 1.9.0 or greater.
diff --git a/translations/pt-BR/data/reusables/cli/cli-auth.md b/translations/pt-BR/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..be9a823c3c
--- /dev/null
+++ b/translations/pt-BR/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} can authenticate using your {% data variables.product.prodname_dotcom %} account. Before running {% data variables.product.prodname_cli %} commands, you will need to authenticate by running `gh auth login`. For more information on command line authentication, see "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)."
diff --git a/translations/pt-BR/data/reusables/cli/cli-manual.md b/translations/pt-BR/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..dd2012d873
--- /dev/null
+++ b/translations/pt-BR/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+For more information about {% data variables.product.prodname_cli %}, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/cli/cli-repo.md b/translations/pt-BR/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..7914da4358
--- /dev/null
+++ b/translations/pt-BR/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} commands must be run within the repository that you want to interact with, so you must first navigate to the directory containing the local copy of your repository. Alternatively, you can specify a repository by passing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY` or `--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY` or `--repo OWNER/REPOSITORY`{% endif %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Replace `HOSTNAME` with the name of {% data variables.product.product_location %}. {% endif %}Replace `OWNER` with owner of the repository. Substitua `REPOSITORY` pelo nome do repositório.
diff --git a/translations/pt-BR/data/reusables/cli/download-update-cli.md b/translations/pt-BR/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..b26363cf45
--- /dev/null
+++ b/translations/pt-BR/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+To download or upgrade {% data variables.product.prodname_cli %}, follow the instructions in the [{% data variables.product.prodname_cli %} README](https://github.com/cli/cli#installation).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/pt-BR/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/pt-BR/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/pt-BR/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/pt-BR/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..a101d1809f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`, `csharp`, `go`, `java`, `javascript`, and `python`
diff --git a/translations/pt-BR/data/reusables/code-scanning/enabling-options.md b/translations/pt-BR/data/reusables/code-scanning/enabling-options.md
index 0bdd9e70cc..1573dc19bc 100644
--- a/translations/pt-BR/data/reusables/code-scanning/enabling-options.md
+++ b/translations/pt-BR/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">Running {% data variables.product.prodname_codeql %} code scanning in your CI system</a>").
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      Third&#8209;party
-    </td>
-    
-    <td>
-      Usar {% data variables.product.prodname_actions %} (ver "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Configurar {% data variables.product.prodname_code_scanning %} usando ações</a>") ou gerado externamente e enviado para {% data variables.product.product_name %} (ver "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Fazer o upload de um arquivo SARIF para {% data variables.product.prodname_dotcom %}</a>").
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)").
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql %} code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
+{%- endif %}
+| Third&#8209;party | Using
+{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)").|
diff --git a/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md
index ac81f29880..ada3a687bb 100644
--- a/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Observação:** O upload do SARIF é compatível com um máximo de 1000 resultados por upload. Todos os resultados acima deste limite são ignorados. Se uma ferramenta gerar muitos resultados, você deverá atualizar a configuração para focar nos resultados para as regras ou consultas mais importantes.
+**Note:** SARIF upload supports a maximum of {% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %} results per upload. Todos os resultados acima deste limite são ignorados. Se uma ferramenta gerar muitos resultados, você deverá atualizar a configuração para focar nos resultados para as regras ou consultas mais importantes.
 
 {% endnote %}
diff --git a/translations/pt-BR/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..66bcb1b40c
--- /dev/null
+++ b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**Note:** Uploading SARIF data to display as {% data variables.product.prodname_code_scanning %} results in {% data variables.product.product_name %} is supported for organization-owned repositories with {% data variables.product.prodname_GH_advanced_security %} enabled{% if currentVersion == "free-pro-team@latest" %}, and public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..5c772293bc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.product.product_location %}.
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/codespaces/about-personalization.md b/translations/pt-BR/data/reusables/codespaces/about-personalization.md
index a737ba1aff..067c6e3fee 100644
--- a/translations/pt-BR/data/reusables/codespaces/about-personalization.md
+++ b/translations/pt-BR/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-Você também pode personalizar aspectos do ambiente dos espaços de códigos para qualquer espaço de código que sua conta criar. A personalização pode incluir preferências de shell e ferramentas adicionais.
+You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. A personalização pode incluir preferências de shell e ferramentas adicionais.
diff --git a/translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md b/translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..39b29dc4a0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+You can forward ports in your codespace to test and debug your application.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..8031bfb4af
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index 44f5e4ef6f..c45d078f12 100644
--- a/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. Em {% data variables.product.prodname_vscode %}, na barra lateral esquerda, clique no ícone Remote Explorer. ![O ícone do Remote Explorer em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. Em {% data variables.product.prodname_vscode %}, na barra lateral esquerda, clique no ícone Remote Explorer. ![O ícone do Remote Explorer em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md b/translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..b66b4193f5
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Cada uma delas tem um nível diferente de recursos e uma camada diferente de cobrança.<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**Observação:** {% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types:
+
+* **Basic** for updating a file and raising a pull request
+* **Standard** for editing a website
+* **Premium** for high compute tasks such as data analysis
diff --git a/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md b/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..87bfa539ff
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users.
+
+For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..fed860897b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/pt-BR/data/reusables/codespaces/rebuild-command.md b/translations/pt-BR/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..ea9e45b032
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/recovery-mode.md b/translations/pt-BR/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..fa4e73d013
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/release-stage.md b/translations/pt-BR/data/reusables/codespaces/release-stage.md
index 600f7802d1..50df2085af 100644
--- a/translations/pt-BR/data/reusables/codespaces/release-stage.md
+++ b/translations/pt-BR/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Observação:** {% data variables.product.prodname_codespaces %} está atualmente em versão beta pública limitada e sujeito a alterações. Durante o período beta, {% data variables.product.prodname_dotcom %} não faz nenhuma garantia sobre a disponibilidade de {% data variables.product.prodname_codespaces %}. Para obter mais informações sobre fontes de publicação, consulte "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
+**Observação:** {% data variables.product.prodname_codespaces %} está atualmente em versão beta pública limitada e sujeito a alterações. Para obter mais informações sobre fontes de publicação, consulte "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
 
 {% endnote %}
diff --git a/translations/pt-BR/data/reusables/codespaces/secret-precedence.md b/translations/pt-BR/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..d5102fd3fa
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+Se existir um segredo com o mesmo nome em vários níveis, o segredo no nível inferior tem prioridade. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/secrets-naming.md b/translations/pt-BR/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..0b93679cdf
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+As regras a seguir aplicam-se aos nomes dos segredos:
+
+* Os nomes dos segredos podem conter apenas caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) or sublinhado (`_`). Não são permitidos espaços.
+* Os nomes dos segredos não devem começar com o prefixo `GITHUB_`.
+* Os nomes dos segredos não devem começar com um número.
+* Nomes dos segredos não diferenciam maiúsculas de minúsculas.
+* Os nomes dos segredos devem ser únicos no nível em que são criados.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/secrets-on-start.md b/translations/pt-BR/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..c4a5bf3b41
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md b/translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..90b3503dcd
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/source-control-display.md b/translations/pt-BR/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..09917cd3c8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. In the Activity Bar, click the **Source Control** view.
+
+  ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/type-port-label.md b/translations/pt-BR/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..498c9eb752
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index e973538df0..afb626e71c 100644
--- a/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-Você pode ver todos os códigos pertencentes a sua conta de usuário em [github.com/codespaces](https://github.com/codespaces).
+You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..a5e98437c0
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**.
+
+  !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md
index 485b246864..082018b197 100644
--- a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@ A tabela a seguir mostra, para cada gerenciador de pacotes:
 | Composer               | `composer`       | v1, v2                         |         **✓**         |       **✓**        |           |
 | Docker                 | `docker`         | v1                             |         **✓**         |       **✓**        |           |
 | Hex                    | `mix`            | v1                             |                       |       **✓**        |           |
-| elm-package            | `elm`            | v0.18, v0.19                   |         **✓**         |       **✓**        |           |
+| elm-package            | `elm`            | v0.19                          |         **✓**         |       **✓**        |           |
 | git submodule          | `gitsubmodule`   | N/A (sem versão)               |         **✓**         |       **✓**        |           |
 | GitHub Actions         | `github-actions` | N/A (sem versão)               |         **✓**         |       **✓**        |           |
 | Módulos Go             | `gomod`          | v1                             |         **✓**         |       **✓**        |   **✓**   |
diff --git a/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md
index ce8a04b485..b65bb03683 100644
--- a/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@ Quando você cria uma pull request a partir de um repositório bifurcado para o
 
 Fluxos de trabalho não são executados em repositórios bifurcados por padrão. Você deve habilitar o GitHub Actions na aba **Actions** (Ações) do repositório bifurcado.
 
+{% if currentVersion == "free-pro-team@latest"%}
+When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve running workflows on the pull request. For more information, see "[Approving workflow runs from public forks](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)."
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} As permissões para o `GITHUB_TOKEN` em repositórios bifurcados são somente leitura. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
 
 {% note %}
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-report-download.md
index 41295f491c..244a3d8475 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. Opcionalmente, clique em **Get usage report** (Obter relatório de uso) para enviar um relatório CSV de armazenamento para {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %} para o endereço de e-mail principal da conta. ![Baixar relatório em CSV](/assets/images/help/billing/actions-packages-report-download.png)
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![Baixar relatório em CSV](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/change_plan_duration.md b/translations/pt-BR/data/reusables/dotcom_billing/change_plan_duration.md
index 9d5625189a..5867d5e1a8 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. Em "Billing overview" (Visão geral de cobrança), clique em **Change to yearly billing** (Alterar para cobrança anual) ou **Change to monthly billing** (Alterar para cobrança mensal). ![Botão de alteração de plano na visão geral de cobrança](/assets/images/help/billing/change-plan-duration-link.png)
+1. Under "Current monthly bill" or "Current yearly bill", click **Switch to yearly billing** or **Switch to monthly billing**. ![Botão de alteração de plano na visão geral de cobrança](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/choose_org_plan.md b/translations/pt-BR/data/reusables/dotcom_billing/choose_org_plan.md
index f7f398d689..2121e37d1c 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. Se você está atualizando o {% data variables.product.prodname_free_team %}, selecione um produto em "Upgrading to" (Atualizar para). ![Botão Upgrade (Atualizar)](/assets/images/help/billing/upgrade-to-product.png)
+1. Under "Compare plans", you can compare the features of each plan. Depending on your current plan and what plan you have chosen, click either **Upgrade to Team** or **Upgrade to Enterprise**. ![Compare plans and upgrade](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/enter-payment-info.md b/translations/pt-BR/data/reusables/dotcom_billing/enter-payment-info.md
index 9a3dcee8a6..3254f59285 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. Em "Billing information" (Informações de cobrança), escolha para pagar com cartão de crédito ou PayPal. ![Mudar forma de pagamento de cobrança](/assets/images/help/billing/billing_switch_payments.png)
+1. Under "Payment method", choose to pay with a credit card or PayPal. ![Mudar forma de pagamento de cobrança](/assets/images/help/billing/billing_switch_payments.png)
 1. Preencha o formulário de informações de pagamento e clique em **Submit** (Enviar).
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/lfs-add-data.md b/translations/pt-BR/data/reusables/dotcom_billing/lfs-add-data.md
index 369bd169a1..45312d6879 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. Ao lado de "{% data variables.large_files.product_name_short %} Data" (Dados do {% data variables.large_files.product_name_short %})", clique em **Add more data** (Adicionar mais dados) ou use o menu suspenso Edit (Editar) e clique em **Add more data packs** (Adicionar mais pacotes de dados). ![Botão Add more data (Adicionar mais dados)](/assets/images/help/billing/data-pack-purchase-more.png)
+1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**. ![Botão Add more data (Adicionar mais dados)](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/pt-BR/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..4f2bd7bf2d
--- /dev/null
+++ b/translations/pt-BR/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. At the top of the page, under "Payment information", click **Manage spending limit**. ![Manage spending limit link](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/next_billing_date.md b/translations/pt-BR/data/reusables/dotcom_billing/next_billing_date.md
index 1942ee82bd..f1fc38fa69 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. Em "Billing overview" (Visão geral da cobrança), revise a data do seu próximo pagamento. ![Data da próxima cobrança](/assets/images/help/billing/settings_billing_next_payment.png)
+1. At the top of the page, under "Next payment due", review when your next payment is due. ![Data da próxima cobrança](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/review-pending-changes.md b/translations/pt-BR/data/reusables/dotcom_billing/review-pending-changes.md
index 59b9e0023d..18b63aace3 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. Em "Subscriptions" (Assinaturas), revise suas alterações pendentes. ![Seção Subscriptions (Assinaturas) de Billing settings (configurações de cobrança) listando quaisquer alterações de assinatura pendentes](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. Under "Current plan", review your pending changes. ![Seção Subscriptions (Assinaturas) de Billing settings (configurações de cobrança) listando quaisquer alterações de assinatura pendentes](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/update_payment_method.md b/translations/pt-BR/data/reusables/dotcom_billing/update_payment_method.md
index f3c05888df..8ef39f6b23 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. Em "Billing overview" (Visão geral de cobrança), clique em **Update payment method** (Atualizar forma de pagamento). ![Botão Update payment method (Atualizar forma de pagamento)](/assets/images/help/billing/update_payment_method.png)
+1. At the top of the page, under "Payment information", click **Update payment method**. ![Botão Update payment method (Atualizar forma de pagamento)](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/upgrade_org.md b/translations/pt-BR/data/reusables/dotcom_billing/upgrade_org.md
index 361fd13fc0..aba4840ee5 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. Se você está atualizando a partir de {% data variables.product.prodname_free_team %}, clique em **Upgrade options** (Opções de atualização). Se você está atualizando a partir de {% data variables.product.prodname_team %}, use o menu suspenso **Edit** e clique em **Upgrade**. ![Botão de opções de atualização](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. Click **Upgrade** next to "Current plan".
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/view-payment-history.md b/translations/pt-BR/data/reusables/dotcom_billing/view-payment-history.md
index d3a09aee83..b654152e91 100644
--- a/translations/pt-BR/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/pt-BR/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. Em "Billing overview" (Visão geral de cobrança), clique em **View payment history** (Exibir histórico de pagamentos). ![Link View payment history (Exibir histórico de pagamentos)](/assets/images/help/billing/view-payment-history-link.png)
+1. At the top of the page, under "Next payment due", click **View payment history**. ![Link View payment history (Exibir histórico de pagamentos)](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/add-a-domain.md b/translations/pt-BR/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..fa373d9440
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. Clique em **Add a domain** (Adicionar um domínio). ![Botão Add a domain (Adicionar um domínio)](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/pt-BR/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..deac57a6fe
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)".
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/pt-BR/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..9c698cef0b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+Você pode confirmar que os sites e endereços de e-mail listados nos perfis de qualquer organização pertencente à sua conta corporativa são controlados pela sua empresa verificando os domínios. Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+Depois de verificar a propriedade dos domínios da sua conta, será exibido um selo "Verificado" no perfil de cada organização com o domínio listado no seu perfil. {% data reusables.organizations.verified-domains-details %}
+
+Os proprietários da organização conseguirão de verificar a identidade dos integrantes da organização, visualizando o endereço de e-mail de cada integrante dentro do domínio verificado.
+
+Após verificar domínios para a sua conta corporativa, você poderá restringir notificações de e-mail para domínios verificados para todas as organizações pertencentes à sua conta corporativa. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/domains-approving.md b/translations/pt-BR/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/domains-removing.md b/translations/pt-BR/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/domains-verifying.md b/translations/pt-BR/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..c9b861e66c
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+Para verificar o domínio da sua conta corporativa, você deve ter acesso para modificar registros de domínio com o seu serviço de hospedagem de domínio.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Aguarde a alteração da configuração de DNS, que pode demorar até 72 horas. Você pode confirmar que a configuração do DNS foi alterada executando o comando `dig` na linha de comando, substituindo `ENTERPRISE-CONTA` pelo nome da conta corporativa e `example.com` pelo o domínio que você gostaria de verificar. Você deverá ver o novo registro TXT listado na saída do comando.
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. Opcionalmente, depois que o selo "Verificado" estiver visível nos perfis da sua organização, exclua a entrada TXT do registro do DNS no seu serviço de hospedagem de domínio. ![Selo Verified (Verificado)](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..529897cc5e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+Os domínios podem ser herdados da conta corporativa ou configurados para a organização específica. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Se restrições de e-mail estiverem habilitadas para uma conta corporativa, os proprietários da organização não poderão desabilitar restrições de e-mail para qualquer organização que pertence à conta corporativa. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..ec2ab36992
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. Clique em **Salvar**.
diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md
index 9613a09be2..85644af45c 100644
--- a/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. Em "Configurações", clique em **Domínios verificados**. ![Aba "Domínios verificados"](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/pt-BR/data/reusables/enterprise_deprecation/deprecation_details.md
index b49c24d9e8..0f523bd335 100644
--- a/translations/pt-BR/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/pt-BR/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1 +1 @@
-Nenhum lançamento de patch será feito, mesmo para questões críticas de segurança. Para obter melhor desempenho, melhorar a segurança e novos recursos, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">upgrade to the latest version of GitHub Enterprise</a>. Para ajuda com a atualização, <a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">contact GitHub Enterprise support</a>.
+Nenhum lançamento de patch será feito, mesmo para questões críticas de segurança. Para obter melhor desempenho, melhorar a segurança e novos recursos, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">upgrade to the latest version of GitHub Enterprise</a>. Para ajuda com a atualização, <a href="https://enterprise.github.com/support">contact GitHub Enterprise support</a>.
diff --git a/translations/pt-BR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/pt-BR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..399fd5b32b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### Sobre os requisitos mínimos para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior
+
+Antes de atualizar para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior, revise os recursos de hardware que você forneceu para sua instância. {% data variables.product.prodname_ghe_server %} 3.0 introduz novas funcionalidades, como {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %}, e exige mais recursos do que as versões 2.22 e anteriores. Para obter mais informações, consulte as observações sobre a versão [{% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes).
+
+Os requisitos aumentados para {% data variables.product.prodname_ghe_server %} 3.0 e posterior estão em **negrito** na tabela a seguir.
+
+| Licenças de usuário                      |                         vCPUs |                               Memória |                 Armazenamento anexado | Armazenamento raiz |
+|:---------------------------------------- | -----------------------------:| -------------------------------------:| -------------------------------------:| ------------------:|
+| Teste, demonstração ou 10 usuários leves | **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up de 16 GB_ | **150 GB**<br/>_Up de 100 GB_ |             200 GB |
+| 10-3000                                  |   **8**<br/>_Up de 4_ |   **48 GB**<br/>_Up de 32 GB_ | **300 GB**<br/>_Up de 250 GB_ |             200 GB |
+| 3000-5000                                |  **12**<br/>_Up de 8_ |                                 64 GB |                                500 GB |             200 GB |
+| 5000-8000                                | **16**<br/>_Up de 12_ |                                 96 GB |                                750 GB |             200 GB |
+| 8000-10000+                              | **20**<br/>_Up de 16_ | **160 GB**<br/>_Up de 128 GB_ |                               1000 GB |             200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+Para obter mais informações sobre requisitos de hardware para {% data variables.product.prodname_actions %}, consulte "[Introdução a {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md
index 1e053507af..e7d45c6fb3 100644
--- a/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/pt-BR/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Aviso**: Alterar essa configuração fará com que {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} seja reiniciado. Você deve programar essa mudança com cuidado para minimizar o tempo de inatividade.
+**Warning**: Changing this setting will cause user-facing services on {% data variables.product.prodname_ghe_server %} to restart. You should time this change carefully, to minimize downtime for users.
 
 {% endwarning %}
diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md
index 83944acdce..727552ef5d 100644
--- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md
+++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md
@@ -1,2 +1 @@
-1. In the left sidebar, click **Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %}**.
-  ![Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %} tab in the Site admin settings](/assets/images/enterprise/site-admin-settings/enterprise-tab.png)
+1. Na barra lateral esquerda, clique em **Empresa{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} visão geral{% endif %}**. ![Aba de {% if currentVersion ver_gt "enterprise-server@2.21" ou currentVersion == "github-ae@latest" %} visão geral da empresa{% endif %} nas configurações de administrador do site.](/assets/images/enterprise/site-admin-settings/enterprise-tab.png)
diff --git a/translations/pt-BR/data/reusables/gated-features/actions-shared.md b/translations/pt-BR/data/reusables/gated-features/actions-shared.md
index 2c839c82d0..03d4a1cf5d 100644
--- a/translations/pt-BR/data/reusables/gated-features/actions-shared.md
+++ b/translations/pt-BR/data/reusables/gated-features/actions-shared.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} não está disponível para repositórios privados pertencentes a contas usando os planos de legado por repositório. 
+{% data variables.product.prodname_actions %} está disponível com {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizações, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} não está disponível para repositórios privados pertencentes a contas usando os planos de legado por repositório. 
diff --git a/translations/pt-BR/data/reusables/gated-features/code-scanning.md b/translations/pt-BR/data/reusables/gated-features/code-scanning.md
index ed24735838..8b848819a3 100644
--- a/translations/pt-BR/data/reusables/gated-features/code-scanning.md
+++ b/translations/pt-BR/data/reusables/gated-features/code-scanning.md
@@ -1,5 +1,5 @@
-{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} está disponível para todos os repositórios públicos e para repositórios privados pertencentes a organizações em que {% data variables.product.prodname_GH_advanced_security %} está habilitado.
-{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} está disponível se {% data variables.product.prodname_GH_advanced_security %} estiver habilitado para o repositório.
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
 {%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_code_scanning_capc %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
 {%- else %}
diff --git a/translations/pt-BR/data/reusables/gated-features/ghas.md b/translations/pt-BR/data/reusables/gated-features/ghas.md
index fcf1b455c7..166bbffcbe 100644
--- a/translations/pt-BR/data/reusables/gated-features/ghas.md
+++ b/translations/pt-BR/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_GH_advanced_security %} is also included in {% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %} and in all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
+{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/gated-features/github-insights.md b/translations/pt-BR/data/reusables/gated-features/github-insights.md
index fdd0fd1c09..e7750957d6 100644
--- a/translations/pt-BR/data/reusables/gated-features/github-insights.md
+++ b/translations/pt-BR/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %} está disponível com {% data variables.product.prodname_ghe_one %}. Para obter mais informações, consulte os "[Produtos da {% data variables.product.prodname_dotcom %}](/articles/githubs-products)".
+{% data variables.product.prodname_insights %} está disponível com {% data variables.product.prodname_ghe_one %}. Para obter mais informações, consulte os "[Produtos da {% data variables.product.prodname_dotcom %}](/articles/githubs-products)".
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/gated-features/packages.md b/translations/pt-BR/data/reusables/gated-features/packages.md
index 80542e19aa..898b2c12b9 100644
--- a/translations/pt-BR/data/reusables/gated-features/packages.md
+++ b/translations/pt-BR/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}.
+{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}.
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-O {% data variables.product.prodname_registry %} não está disponível para repositórios privados de contas que utilizam planos antigos por-repositório. {% data variables.product.prodname_registry %} está disponível com {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizações, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_one %}. {% data reusables.gated-features.more-info %}
+O {% data variables.product.prodname_registry %} não está disponível para repositórios privados de contas que utilizam planos antigos por-repositório. Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md
index f5ee4e99c8..c5e460da82 100644
--- a/translations/pt-BR/data/reusables/gated-features/secret-scanning.md
+++ b/translations/pt-BR/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %} está disponível {% if currentVersion == "free-pro-team@latest" %}em repositórios públicos, e em repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_secret_scanning_caps %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
-{% endif %}
\ No newline at end of file
+{%- else %}
+{% data variables.product.prodname_secret_scanning_caps %} está disponível se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/forked-write-permission.md b/translations/pt-BR/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..3fe9804246
--- /dev/null
+++ b/translations/pt-BR/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+You can use the `permissions` key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the **Send write tokens to workflows from pull requests** option in the {% data variables.product.prodname_actions %} settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."
\ No newline at end of file
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
new file mode 100644
index 0000000000..4e5ca65fe7
--- /dev/null
+++ b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+Available scopes and access values:
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
+
+You can use the following syntax to define read or write access for all of the available scopes:
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/github-token-permissions.md b/translations/pt-BR/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..88604df1dc
--- /dev/null
+++ b/translations/pt-BR/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+The `GITHUB_TOKEN` secret is set to an access token for the repository each time a job in a workflow begins. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 1b1e0448e8..8356a3a2af 100644
--- a/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Executa o comando `mvn --batch-mode` para publicar em {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`.
+Executa o comando `mvn --batch-mode` para publicar em {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access granted to the `GITHUB_TOKEN`.{% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index 2bdd5dc0a4..2344590f24 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **Aviso**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    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)."
 
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
index 9ddc7c7b5c..6b88ca8b5b 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
+++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md
@@ -1,9 +1,9 @@
-A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added:
-- **User repository**: You must be the repository owner.
-- **Organization**: You must be an organization owner. 
-- **Organization repository**: You must be an organization owner, or have admin access to the repository.
+A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. Para gerenciar um executor auto-hospedado, você deve ter as seguintes permissões, dependendo de onde o executor auto-hospedado foi adicionado:
+- **Repositório de Usuário**: Você deve ser o proprietário do repositório.
+- **Organização**: Você deve ser um proprietário da organização.
+- **Repositório da organização**: Você deve ser o proprietário da organização ou ter acesso de administrador ao repositório.
 {% if currentVersion == "free-pro-team@latest" %}
-- **Enterprise account**: You must be an enterprise owner.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
-- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator.
+- **Conta corporativa**: Você deve ser proprietário de uma empresa.
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
+- **Empresa**: Você deve ser um administrador do site de {% data variables.product.prodname_enterprise %}
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
index 12756c93a0..d6fcc551bf 100644
--- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
+++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
@@ -1,12 +1,12 @@
-1. Navigate to where your self-hosted runner is registered:
-   * **In an organization or repository**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
-   * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**:
-   
-     1. In the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}.
-     1. In the left sidebar, click **Enterprise overview**. 
-     1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**.
-1. Navigate to the {% data variables.product.prodname_actions %} settings:
-   * **In an organization or repository**: click **Actions** in the left sidebar.
-     
-     ![Actions setting](/assets/images/help/settings/settings-sidebar-actions.png)
-   * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies".
+1. Navegue por onde seu runner auto-hospedado está registrado:
+   * **Em uma organização ou repositório**: navegue até a página principal e clique em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**.
+   * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}**If using an enterprise-level runner**:
+
+     1. No canto superior direito de qualquer página, clique em {% octicon "rocket" aria-label="The rocket ship" %}.
+     1. Na barra lateral esquerda, clique em **Visão geral da empresa**.
+     1. {% endif %} Na barra lateral da empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**.
+1. Navegue até as configurações {% data variables.product.prodname_actions %}:
+   * **Em uma organização ou um repositório**: clique em **Ações** na barra lateral esquerda.
+
+     ![Configuração de ações](/assets/images/help/settings/settings-sidebar-actions.png)
+   * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies".
diff --git a/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md b/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md
index 19c1303115..7be5a2099d 100644
--- a/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**Warning**: Ubuntu 16.04 is being deprecated. If any of your workflows use Ubuntu 16.04, migrate to Ubuntu 20.04 or 18.04. For more information, see [the blog post](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021).
+
+{% endwarning %}
+
 | Ambiente virtual     | Etiqueta de fluxo de trabalho YAML |
 | -------------------- | ---------------------------------- |
 | Windows Server 2019  | `windows-latest` ou `windows-2019` |
+| Windows Server 2016  | `windows-2016`                     |
 | Ubuntu 20.04         | `ubuntu-latest` ou `ubuntu-20.04`  |
 | Ubuntu 18.04         | `ubuntu-18.04`                     |
-| Ubuntu 16.04         | `ubuntu-16.04`                     |
 | macOS Big Sur 11.0   | `macos-11.0`                       |
 | macOS Catalina 10.15 | `macos-latest` or `macos-10.15`    |
diff --git a/translations/pt-BR/data/reusables/github-actions/workflow-permissions-intro.md b/translations/pt-BR/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..88382e0d54
--- /dev/null
+++ b/translations/pt-BR/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." You can choose between a restricted set of permissions as the default or a permissive setting. 
diff --git a/translations/pt-BR/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/pt-BR/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..14ee1f9279
--- /dev/null
+++ b/translations/pt-BR/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/reference/workflow-syntax-for-github-actions#permissions). 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/gpg/x-509-key.md b/translations/pt-BR/data/reusables/gpg/x-509-key.md
index 6570c46734..954c61e92f 100644
--- a/translations/pt-BR/data/reusables/gpg/x-509-key.md
+++ b/translations/pt-BR/data/reusables/gpg/x-509-key.md
@@ -30,7 +30,7 @@ Você pode usar [smimesign](https://github.com/github/smimesign) para assinar co
   $ git config --local gpg.program smimesign
   ```
   Se você estiver usando uma chave X.509 que corresponde à sua identidade do committer, poderá começar a assinar commits e tags.
-4. Se você não estiver usando uma chave X.509 que corresponde à sua identidade de commiter, liste X.509 chaves para as quais você tem um certificado e uma chave privada usando o comando `smimesign --list-keys`.
+4. If you're not using an X.509 key that matches your committer identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
   ```shell
   $ smimesign --list-keys
   ```
diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/verification-status-check.md b/translations/pt-BR/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..ef7a981baa
--- /dev/null
+++ b/translations/pt-BR/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+Você pode conferir o status de verificação de seus commits ou tags assinados no {% data variables.product.product_name %} e ver por que as assinaturas de commit podem não ter sido verificadas. Para obter mais informações, consulte "[Conferir o status de verificação da assinatura de commit ou tag](/articles/checking-your-commit-and-tag-signature-verification-status)".
diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..bb9ea14675
--- /dev/null
+++ b/translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Vigilant mode is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..311db86861
--- /dev/null
+++ b/translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| Status                      | Descrição                                                                                                                                                                                                                                                                                |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Verificado**              | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.                                                                                                                                                       |
+| **Partially&nbsp;verified** | The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified. |
+| **Unverified**              | Any of the following is true:<br>- The commit is signed but the signature could not be verified.<br>- The commit is not signed and the committer has enabled vigilant mode.<br>- The commit is not signed and an author has enabled vigilant mode.<br>           |
diff --git a/translations/pt-BR/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/pt-BR/data/reusables/marketplace/cancel-app-billing-settings.md
index 60bc7f2cc5..8b4b548302 100644
--- a/translations/pt-BR/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/pt-BR/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. Use o menu suspenso **Edit** e clique em **Cancel plan**. ![Cancelar o link na seção Compras no Marketplace das configurações de faturamento da sua conta pessoal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to cancel, use the **Edit** drop-down and click **Cancel plan**. ![Cancelar o link na seção Compras no Marketplace das configurações de faturamento da sua conta pessoal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/pt-BR/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/pt-BR/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index e5b58479b4..b9901ac4a8 100644
--- a/translations/pt-BR/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/pt-BR/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. Em "Subscriptions" (Assinaturas), ao lado do teste gratuito que deseja cancelar, use o menu Edit e clique em **Cancel plan**.
+1. Next to the free trial you'd like to cancel, use the **Edit** drop-down and click **Cancel plan**.
diff --git a/translations/pt-BR/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/pt-BR/data/reusables/marketplace/downgrade-app-billing-settings.md
index 5eb4bdb452..93860c92ad 100644
--- a/translations/pt-BR/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/pt-BR/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Em "Your subscriptions" (Suas assinaturas), ao lado do aplicativo que você gostaria de fazer o downgrade, use o menu Editar e clique em **Change plan** (Alterar plano) ou **Cancel plan** (Cancelar plano). ![Editar link na seção Compras no Marketplace das configurações de faturamento da sua conta pessoal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you'd like to downgrade, use the **Edit** drop-down and click **Change plan** or **Cancel plan**. ![Editar link na seção Compras no Marketplace das configurações de faturamento da sua conta pessoal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/pt-BR/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/pt-BR/data/reusables/marketplace/upgrade-app-billing-settings.md
index 1164b02bc4..48c9ff9813 100644
--- a/translations/pt-BR/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/pt-BR/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Use o menu suspenso **Edit** (Editar) e clique em **Change plan** (Alterar plano). ![Editar menu suspenso na seção de Compras no Mercado das configurações de faturamento da sua conta pessoal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to upgrade, use the **Edit** drop-down and click **Change plan**. ![Editar menu suspenso na seção de Compras no Mercado das configurações de faturamento da sua conta pessoal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md b/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..e5d59aceea
--- /dev/null
+++ b/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}issues, pulls requests, releases, security alerts, or discussions{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}issues, pull requests, releases, or discussions{% endif %}
diff --git a/translations/pt-BR/data/reusables/notifications/email-restrictions-verification.md b/translations/pt-BR/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..22f589e8a5
--- /dev/null
+++ b/translations/pt-BR/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)".
diff --git a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index ed551f5d2d..dc6894c3f7 100644
--- a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-Você pode escolher o método de entrega para notificações sobre {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} em repositórios que você está inspecionando, bem como a frequência na qual as notificações são enviadas para você.
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+You can choose the delivery method and frequency of notifications about
+{% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts.
+{% else %}
+You can choose the delivery method for notifications about
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/organizations/add-a-domain.md b/translations/pt-BR/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..af1a152576
--- /dev/null
+++ b/translations/pt-BR/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. Clique em **Add a domain** (Adicionar um domínio). ![Botão Add a domain (Adicionar um domínio)](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/pt-BR/data/reusables/organizations/billing_plans.md b/translations/pt-BR/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..8b003196da
--- /dev/null
+++ b/translations/pt-BR/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. In your organization's Settings sidebar, click **Billing & plans**. ![Configurações de faturamento](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/pt-BR/data/reusables/organizations/continue-verifying-domain.md b/translations/pt-BR/data/reusables/organizations/continue-verifying-domain.md
index 7baf532cce..aa857a998e 100644
--- a/translations/pt-BR/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/pt-BR/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. À direita do domínio que está pendente de verificação, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Continuar verificando**. ![Botão do domínio Continue verifying (Continuar a verificação)](/assets/images/help/organizations/continue-verifying-domain.png)
-10. Clique em **Verify domain** (Verificar domínio). ![Botão Verify domain (Verificar domínio)](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. Clique em **Verificar**. ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/organizations/domains-approve-domain.md b/translations/pt-BR/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/pt-BR/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/pt-BR/data/reusables/organizations/domains-approve-it-instead.md b/translations/pt-BR/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/pt-BR/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/pt-BR/data/reusables/organizations/verified-domains.md b/translations/pt-BR/data/reusables/organizations/verified-domains.md
index bae9f656fa..9714304429 100644
--- a/translations/pt-BR/data/reusables/organizations/verified-domains.md
+++ b/translations/pt-BR/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. Na barra lateral esquerda, clique em **Verified domains** (Domínios verificados). ![Botão de domínios verificados](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/pt-BR/data/reusables/package_registry/about-packaging-and-actions.md b/translations/pt-BR/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..22885e3ccd
--- /dev/null
+++ b/translations/pt-BR/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,30 @@
+### Empacotamento em fluxos de trabalho de integração contínua
+
+Uma etapa de empacotamento é uma parte comum de um fluxo de trabalho de integração contínua ou de continuous delivery. Criar um pacote ao fim de um fluxo de trabalho de integração contínua pode ajudar durante as análises de código ou durante o pull request.
+
+Após criar e testar o seu código, uma etapa de empacotamento pode produzir um artefato executável ou aplicável. Dependendo do tipo de aplicativo que você estiver criando, este pacote pode ser baixado localmente para teste manual, disponibilizado para download dos usuários ou implementado em um ambiente de teste ou produção.
+
+Por exemplo, um fluxo de trabalho de integração contínua para um projeto Java pode executar o `pacote mvn` para produzir um arquivo JAR. Ou um fluxo de trabalho CI para um aplicativo Node.js pode criar um contêiner Docker.
+
+Agora, ao revisar um pull request, você poderá ver a execução do fluxo de trabalho e fazer o download do artefato produzido.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+Isso permitirá que você execute o código no pull request em sua máquina, o que pode ajudar a depurar ou testar o pull request.
+
+### Fluxos de trabalho para publicação de pacotes
+
+Além de fazer o upload dos artefatos de empacotamento para teste em um fluxo de trabalho de integração contínua, você poderá criar fluxos de trabalho que criam o seu projeto e publicam pacotes no pacote de registro.
+
+* **Publicar pacotes para {% data variables.product.prodname_registry %}**
+  {% data variables.product.prodname_registry %} pode atuar como um serviço de hospedagem de pacotes para vários tipos de pacotes. Você pode escolher compartilhar os seus pacotes com todos {% data variables.product.prodname_dotcom %} ou compartilhar pacotes privados com colaboradores ou uma organização. For more information, see "[Introduction to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages)."
+
+  Você pode querer publicar pacotes em {% data variables.product.prodname_registry %} em cada push no branch padrão. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.
+
+* **Publicar pacotes em um registro de pacote** Para muitos projetos, a publicação de um registro de pacote é realizada sempre que uma versão nova de um projeto é lançada. Por exemplo, um projeto que produz um arquivo JAR pode fazer o upload de novas versões no repositório central do Maven. Ou um projeto .NET pode produzir um pacote nuget e fazer o upload na Galeria NuGet.
+
+  Você pode automatizar isso criando um fluxo de trabalho que publica pacotes em um registro de pacote em cada versão. Para obter mais informações, consulte "[Criando versões](/github/administering-a-repository/creating-releases)."
diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/pt-BR/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..a02c0f89d8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md b/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md
index 45e2d6778e..b560f6b77e 100644
--- a/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md
+++ b/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md
@@ -1,14 +1,7 @@
-Você precisa de um token de acesso para publicar, instalar e excluir pacotes no {{ site.data.variables.product.prodname_registry }}. Você pode usar um token de acesso pessoal para autenticar com seu nome de usuário diretamente no {% data variables.product.prodname_registry %} ou na API {% data variables.product.prodname_dotcom %}. Ao criar um token de acesso pessoal, você pode atribuir diferentes escopos de token, dependendo da sua necessidade.
+Você precisa de um token de acesso para publicar, instalar e excluir pacotes no {% data variables.product.prodname_registry %}.
 
-{% if currentVersion == "free-pro-team@latest" %}
-Para efetuar a autenticação usando um
-fluxo de trabalho do {% data variables.product.prodname_actions %}:
-- Para registros de pacotes (`PACKAGE-REGISTRY.pkg.github.com`), você pode usar um `GITHUB_TOKEN`.
-- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you can use a `GITHUB_TOKEN` or a personal access token. We strongly recommend you use a `GITHUB_TOKEN` to avoid unncessary access to your repositories.
+You can use a personal access token (PAT) to authenticate to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. Ao criar um token de acesso pessoal, você pode atribuir diferentes escopos de token, dependendo da sua necessidade. For more information about packages-related scopes for a PAT, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
 
-For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
-
-{% else %}
-Para efetuar a autenticação em
-{% data variables.product.prodname_registry %} usando um fluxo de trabalho de {% data variables.product.prodname_actions %}, você deve usar `GITHUB_TOKEN`.
-{% endif %}
+To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
+- `GITHUB_TOKEN` to publish packages associated with the workflow repository.
+- a PAT to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index 40d0c22824..d7b6268017 100644
--- a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. Ao usar a CLI para seu tipo de container, faça login em
-serviço de {% data variables.product.prodname_github_container_registry %} em `ghcr.io`.
+serviço de {% data variables.product.prodname_container_registry %} em `ghcr.io`.
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index b660b74b1a..dc3721257a 100644
--- a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -2,9 +2,9 @@
 
 Os PATs podem conceder amplo acesso à sua conta. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}.
 
-To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
+To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
 
-For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
+For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md b/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md
index 5e789b1e8f..b778c65e92 100644
--- a/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para usar {% data variables.product.prodname_github_container_registry %}, você precisa habilitar a pré-visualização de recursos. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" e "[Habilitar melhor suporte ao contêiner](/packages/guides/enabling-improved-container-support)".
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. Durante o beta, o armazenamento e a banda larga são grátis. To use the {% data variables.product.prodname_container_registry %}, you must enable the feature preview. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" and "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
 {% endnote %}
diff --git a/translations/pt-BR/data/reusables/package_registry/docker-vs-container-registry.md b/translations/pt-BR/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..60ba872bf2
--- /dev/null
+++ b/translations/pt-BR/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**Comparing the Docker registry and the {% data variables.product.prodname_container_registry %}:**
+- The {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) offers improved performance for containers and will supercede the Docker registry in the future.
+- You can migrate your Docker images and workflows from the Docker registry  (`docker.pkg.github.com`)  to the {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) for granular permissions, container storage optimization, and more. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."
+
+{% endnote %}
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md
index 73a07a040b..67608dc1e2 100644
--- a/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will offer improved container support in a future {% data variables.product.product_name %} release.{% elsif currentVersion == "free-pro-team@latest" %} now offers improved container support. For more information, see "[About GitHub Container Registry](/packages/guides/about-github-container-registry)." To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/guides/migrating-to-github-container-registry-for-docker-images)" and "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)."{% endif %}
+**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will be superseded in a future {% data variables.product.product_name %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif currentVersion == "free-pro-team@latest" %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)." {% endif %}
 
 {% endwarning %}
diff --git a/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md
index bed975aa5e..3b8032849e 100644
--- a/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Observação:** Antes de poder usar {% data variables.product.prodname_github_container_registry %}, você deve habilitar o recurso para sua conta. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/guides/enabling-improved-container-support)".
+**Note:** Before you can use the {% data variables.product.prodname_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/pt-BR/data/reusables/package_registry/github-token-security-over-pat.md b/translations/pt-BR/data/reusables/package_registry/github-token-security-over-pat.md
index bee4d1039b..ca6ffe0360 100644
--- a/translations/pt-BR/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/pt-BR/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_github_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
+The {% data variables.product.prodname_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
 
-For more information about `GITHUB_TOKEN`, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
+For more information about `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
diff --git a/translations/pt-BR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/pt-BR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..9bc7ee0d6e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below use this type of permissions:
+- Docker registry (`docker.pkg.github.com`)
+- npm registry
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+The Container registry (`ghcr.io`) offers granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account.
+{% endif %}
+
+For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)"{% if currentVersion == "free-pro-team@latest" %} or "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."{% endif %}.
diff --git a/translations/pt-BR/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/pt-BR/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..e79919f49a
--- /dev/null
+++ b/translations/pt-BR/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+If you have admin permissions to a container image, you can set the access permissions for the container image to private or public. As imagens públicas permitem acesso anônimo e podem ser carregadas sem autenticação ou login via CLI.
+
+Como administrador, você também pode conceder permissões de acesso para uma imagem contêiner separada das permissões que você configurou nos níveis da organização e repositório.
+
+Para imagens de contêiner publicadas e pertencentes a uma conta de usuário, você pode dar a qualquer pessoa uma função de acesso. Para imagens de contêineres publicadas e pertencentes a uma organização, você pode dar uma função de acesso a qualquer pessoa ou equipe na organização.
+
+| Permissão     | Descrição de acesso                                                                                                                                          |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| leitura       | Pode fazer o download do pacote. <br> Pode ler metadados do pacote.                                                                                    |
+| gravação      | Pode fazer upload e download deste pacote. <br> Pode ler gravar metadados do pacote.                                                                   |
+| administrador | Pode fazer upload, download, excluir e gerenciar este pacote. <br> Pode ler gravar metadados do pacote. <br> Pode conceder permissões de pacote. |
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/profile/access_org.md b/translations/pt-BR/data/reusables/profile/access_org.md
index 3874f1d1cb..9356bd4ee8 100644
--- a/translations/pt-BR/data/reusables/profile/access_org.md
+++ b/translations/pt-BR/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. No lado esquerdo da página do seu perfil, em "Organizações", clique no ícone da sua organização. ![ícones da organização](/assets/images/help/profile/profile_orgs_box.png)
+1. In the top right corner of {% data variables.product.prodname_dotcom %}, click your profile photo, then click **Your organizations**. ![Your organizations in the profile menu](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/profile/org_settings.md b/translations/pt-BR/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..4c7f5b7078
--- /dev/null
+++ b/translations/pt-BR/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. Click **Settings** next to the organization. ![The settings button](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md b/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md
index c5f8b4e116..32f5c49ac1 100644
--- a/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/pt-BR/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. Na barra lateral esquerda, abaixo da imagem de perfil do usuário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Bloquear ou relatar usuário**. ![Link para bloquear ou relatar usuário](/assets/images/help/profile/profile-block-or-report-button.png)
+1. In the left sidebar, below the user's profile information, click **Block or Report**. ![Block or report link](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md
index 3ab5a09d6e..b2df164fe6 100644
--- a/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/pt-BR/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -6,6 +6,6 @@ This example triggers the workflow every day at 5:30 and 17:30 UTC:
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/pt-BR/data/reusables/repositories/request-changes-tips.md b/translations/pt-BR/data/reusables/repositories/request-changes-tips.md
index 9f797a846c..28850dac69 100644
--- a/translations/pt-BR/data/reusables/repositories/request-changes-tips.md
+++ b/translations/pt-BR/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - Proprietários e administradores do repositório podem fazer merge de um pull request mesmo que não tenham recebido uma revisão de aprovação; ou se um revisor que solicitou alterações saiu da organização ou estiver indisponível.
 - Se as revisões necessárias e o descarte de uma revisão obsoleta estiverem habilitados e um commit de modificação de código for enviado para o branch de um pull request aprovado, a aprovação será ignorada. O pull request deve ser revisado e aprovado novamente antes de poder ser mesclado.
 - Quando vários pull requests abertos têm um branch principal que aponta para o mesmo commit, você não conseguirá mesclá-los se um ou ambos tiverem uma revisão pendente ou rejeitada.
+- Pull request authors cannot approve their own pull requests.
 
 {% endtip %}
diff --git a/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md b/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md
index 7230ee9994..4069452d97 100644
--- a/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md
+++ b/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md
@@ -1 +1 @@
-Email notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} that affect one or more repositories include the `X-GitHub-Severity`  header field. You can use the value of the `X-GitHub-Severity` header field to filter email notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
+Notificações de e-mail para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} que afetam um ou mais repositórios incluem o campo do cabeçalho `X-GitHub-Severity`. Você pode usar o valor do campo de cabeçalho `X-GitHub-Severity` para filtrar notificações de e-mail para {% if currentVersion == "free-pro-team@latest" ou currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}.
diff --git a/translations/pt-BR/data/reusables/repositories/security-guidelines.md b/translations/pt-BR/data/reusables/repositories/security-guidelines.md
index d25b9c7d39..e93ccdaf29 100644
--- a/translations/pt-BR/data/reusables/repositories/security-guidelines.md
+++ b/translations/pt-BR/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-Você pode criar uma política de segurança para dar às pessoas instruções para relatar vulnerabilidades de segurança de forma responsável em seu projeto. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/articles/adding-a-security-policy-to-your-repository)".
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+You can create a security policy to give people instructions for reporting security vulnerabilities in your project. Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/code-security/getting-started/adding-a-security-policy-to-your-repository)".
 {% endif %}
diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md
index 9d1cab75f6..2b642f5ebf 100644
--- a/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/pt-BR/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. Na barra lateral de segurança, clique em **{% data variables.product.prodname_dependabot_alerts %}**. ![Aaba {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**.{% if currentVersion == "free-pro-team@latest" %} ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md
index b74d5905b1..e46622acd1 100644
--- a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md
+++ b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md
@@ -1 +1 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[Requiring a linear commit history](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" ou currentVersion == "github-ae@latest" %}Se houver uma regra de branch protegido no repositório que exija um histórico de commit linear. você deve permitir merge de combinação por squash, merge de rebase ou ambos. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %}
diff --git a/translations/pt-BR/data/reusables/repositories/suggest-changes.md b/translations/pt-BR/data/reusables/repositories/suggest-changes.md
index 4e7a49c9ed..7405d386dd 100644
--- a/translations/pt-BR/data/reusables/repositories/suggest-changes.md
+++ b/translations/pt-BR/data/reusables/repositories/suggest-changes.md
@@ -1,2 +1 @@
-1. Optionally, to suggest a specific change to the line{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} or lines{% endif %}, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block.
-![Suggestion block](/assets/images/help/pull_requests/suggestion-block.png)
+1. Opcionalmente, para sugerir uma alteração específica à linha{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %} ou linhas{% endif %}, clique em {% octicon "diff" aria-label="The diff symbol" %} e, em seguida, edite o texto dentro do bloco de sugestão. ![Bloco de sugestão](/assets/images/help/pull_requests/suggestion-block.png)
diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta.md b/translations/pt-BR/data/reusables/secret-scanning/beta.md
index 5ec5159d3c..6adcb7d57e 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/beta.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/beta.md
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**Observação:** {% data variables.product.prodname_secret_scanning_caps %} está em beta em {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of secret scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} was in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of {% data variables.product.prodname_secret_scanning %}, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
 
 
 {% endnote %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index cfad6356b5..5f8a8fd23e 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| Parceiro                  | Segredo compatível                                  | Slug da API                              |
-| ------------------------- | --------------------------------------------------- | ---------------------------------------- |
-| n/a                       | Token web do JSON                                   | json_web_token                         |
-| n/a                       | Credencial do Cliente do OAuth                      | api_credential_assignment              |
-| Adafruit IO               | Chave de IO de Adafruit                             | adafruit_io_key                        |
-| Alibaba Cloud             | ID da chave de acesso da nuvem do Alibaba           | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Segredo da chave de acesso à nuvem do Alibaba       | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | ID da Chave de Acesso do AWS da Amazon              | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Chave de acesso secreta do AWS da Amazon            | aws_secret_access_key                  |
-| Asana                     | Asana Personal Access Token                         | asana_personal_access_token            |
-| Atlassian                 | Token da API de Atlassian                           | atlassian_api_token                    |
-| Atlassian                 | Token web de JSON de Atlassian                      | atlassian_jwt                            |
-| Azure                     | Token de acesso pessoal do Azure DevOps             | azure_devops_personal_access_token   |
-| Azure                     | Token do Azure SAS                                  | azure_sas_token                        |
-| Azure                     | Certificado de Gerenciamento de Serviços do Azure   | azure_management_certificate           |
-| Azure                     | String de conexão do Azure SQL                      | azure_sql_connection_string            |
-| Azure                     | Chave da conta de armazenamento do Azure            | azure_storage_account_key              |
-| Clojars                   | Token de implantação de Clojars                     | clojars_deploy_token                   |
-| CloudBees CodeShip        | Credencial de Coadship de CloudBees                 | codeship_credential                      |
-| Databricks                | Token de acesso de Databricks                       | databricks_access_token                |
-| Discord                   | Token de Bot de Discord                             | discord_bot_token                      |
-| Doppler                   | Token pessoal de Doppler                            | doppler_personal_token                 |
-| Doppler                   | Token de serviço de Doppler                         | doppler_service_token                  |
-| Doppler                   | Token de CLI de Doppler                             | doppler_cli_token                      |
-| Doppler                   | Token de SCIM de Doppler                            | doppler_scim_token                     |
-| Dropbox                   | Token de Acesso de Dropbox                          | dropbox_access_token                   |
-| Dropbox                   | Token de acesso à vida curta do Dropbox             | dropbox_short_lived_access_token     |
-| Dynatrace                 | Token de acesso de Dynatrace                        | dynatrace_access_token                 |
-| Dynatrace                 | Token interno de Dynatrace                          | dynatrace_internal_token               |
-| Facebook                  | Facebook Access Token                               | facebook_access_token                  |
-| Finicity                  | Chave do aplicativo de Finicity                     | finicity_app_key                       |
-| Frame.io                  | Token web do JSON de Frame.io                       | frameio_jwt                              |
-| Frame.io                  | Token do desenvolvedor de Frame.io                  | frameio_developer_token                |
-| GitHub                    | Chave privada de SSH do GitHub                      | github_ssh_private_key                 |
-| GitHub                    | Token de acesso pessoal do GitHub                   | github_personal_access_token           |
-| GitHub                    | Token de acesso à instalação do aplicativo GitHub   | github_app_installation_access_token |
-| GoCardless                | Token de acesso ao vivo ao GoCardless               | gocardless_live_access_token           |
-| GoCardless                | Token de acesso de GoCardless Sandbox               | gocardless_sandbox_access_token        |
-| Google Cloud              | Chave da API do GOogle                              | google_api_key                         |
-| Google Cloud              | ID da chave privada do Google Cloud                 | google_cloud_private_key_id          |
-| Grafana                   | Grafana API Key                                     | grafana_api_key                        |
-| Hashicorp Terraform       | Token da API de Terraform Cloud / Enterprise        | terraform_api_token                    |
-| Hubspot                   | Chave da API de Hubspot                             | hubspot_api_key                        |
-| Intercom                  | Intercom Access Token                               | intercom_access_token                  |
-| Lob                       | Lob Live API Key                                    | lob_live_api_key                       |
-| Lob                       | Lob Test API Key                                    | lob_test_api_key                       |
-| Mailchimp                 | Chave da API de Mailchimp                           | mailchimp_api_key                      |
-| Mailgun                   | Chave da API de Mailgun                             | mailgun_api_key                        |
-| npm                       | Token de acesso de npm                              | npm_access_token                       |
-| NuGet                     | Chave de API de NuGet                               | nuget_api_key                          |
-| Palantir                  | Token web de JSON de Palantir                       | palantir_jwt                             |
-| Postman                   | Chave da API de Postman                             | postman_api_key                        |
-| Proctorio                 | Chave de Consumidor de Proctorio                    | proctorio_consumer_key                 |
-| Proctorio                 | Chave de vínculo de Proctorio                       | proctorio_linkage_key                  |
-| Proctorio                 | Chave de registro de Proctorio                      | proctorio_registration_key             |
-| Proctorio                 | Chave de segredo de Proctorio                       | proctorio_secret_key                   |
-| Pulumi                    | Token de acesso de Pulumi                           | pulumi_access_token                    |
-| PyPI                      | PyPI API Token                                      | pypi_api_token                         |
-| RubyGems                  | RubyGems API Key                                    | rubygems_api_key                       |
-| Samsara                   | Token de API de Samsara                             | samsara_api_token                      |
-| Samsara                   | Token de acesso de OAuth de Samsara                 | samsara_oauth_access_token             |
-| SendGrid                  | SendGrid API Key                                    | sendgrid_api_key                       |
-| Shopify                   | Segredo compartilhado do aplicativo Shopify         | shopify_app_shared_secret              |
-| Shopify                   | Token de acesso de Shopify                          | shopify_access_token                   |
-| Shopify                   | Token de acesso do aplicativo personalizado Shopify | shopify_custom_app_access_token      |
-| Shopify                   | Senha do aplicativo privado Shopify                 | shopify_private_app_password           |
-| Slack                     | Token da API de Slack                               | slack_api_token                        |
-| Slack                     | URL de entrada do webhook de Slack                  | slack_incoming_webhook_url             |
-| Slack                     | URL do fluxo de trabalho do webhook de Slack        | slack_workflow_webhook_url             |
-| SSLMate                   | Chave da API de SSLMate                             | sslmate_api_key                        |
-| SSLMate                   | Segredo do cluster de SSLMate                       | sslmate_cluster_secret                 |
-| Stripe                    | Stripe API Key                                      | stripe_api_key                         |
-| Stripe                    | Chave de segredo Stripe Live                        | stripe_live_secret_key                 |
-| Stripe                    | Chave secreta da API de Teste de Stripe             | stripe_test_secret_key                 |
-| Stripe                    | Chave restrita da API de Stripe Live                | stripe_live_restricted_key             |
-| Stripe                    | Chave restrita da API de testes de Stripe           | stripe_test_restricted_key             |
-| Tencent Cloud             | ID de segredot de Tencent Cloud                     | tencent_cloud_secret_id                |
-| Twilio                    | Identificador de string de conta de Twilio          | twilio_account_sid                     |
-| Twilio                    | Chave da API de Twilio                              | twilio_api_key                         |
+| Parceiro | Segredo compatível | Slug da API |
+| -------- | ------------------ | ----------- |
+|          |                    |             |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index cae8ca1247..d339751964 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| Parceiro                  | Segredo compatível                                                                   |
-| ------------------------- | ------------------------------------------------------------------------------------ |
-| Adafruit IO               | Chave de IO de Adafruit                                                              |
-| Alibaba Cloud             | Par de ID e segredo da chave de acesso à nuvem do Alibaba                            |
-| Amazon Web Services (AWS) | Par do ID de segredo da chave de acesso ao AWS da Amazon                             |
-| Atlassian                 | Token da API de Atlassian                                                            |
-| Atlassian                 | Token web de JSON de Atlassian                                                       |
-| Azure                     | Token de acesso pessoal para o Azure DevOps | azure_devops_personal_access_token |
-| Azure                     | Token de Azure SAS | azure_sas_token                                               |
-| Azure                     | Certificado de Gerenciamento de Serviços do Azure | azure_management_certificate   |
-| Azure                     | String de conexão do SQL de Azure | azure_sql_connection_string                    |
-| Azure                     | Chave de conta de armazenamento do Azure | azure_storage_account_key               |
-| Clojars                   | Token de implantação de Clojars                                                      |
-| CloudBees CodeShip        | Credencial de Coadship de CloudBees                                                  |
-| Databricks                | Token de acesso de Databricks                                                        |
-| Datadog                   | Chave de API de Datadog                                                              |
-| Discord                   | Token de Bot de Discord                                                              |
-| Doppler                   | Token pessoal de Doppler                                                             |
-| Doppler                   | Token de serviço de Doppler                                                          |
-| Doppler                   | Token de CLI de Doppler                                                              |
-| Doppler                   | Token de SCIM de Doppler                                                             |
-| Dropbox                   | Token de Acesso de Dropbox                                                           |
-| Dropbox                   | Token de acesso à vida curta do Dropbox                                              |
-| Dynatrace                 | Token de acesso de Dynatrace                                                         |
-| Dynatrace                 | Token interno de Dynatrace                                                           |
-| Finicity                  | Chave do aplicativo de Finicity                                                      |
-| Frame.io                  | Token web do JSON de Frame.io                                                        |
-| Frame.io                  | Token do desenvolvedor de Frame.io                                                   |
-| GitHub                    | Chave privada de SSH do GitHub                                                       |
-| GitHub                    | Token de acesso pessoal do GitHub                                                    |
-| GitHub                    | Token de acesso à instalação do aplicativo GitHub                                    |
-| GoCardless                | Token de acesso ao vivo ao GoCardless                                                |
-| GoCardless                | Token de acesso de GoCardless Sandbox                                                |
-| Google Cloud              | Chave da API do GOogle                                                               |
-| Google Cloud              | ID da chave privada do Google Cloud                                                  |
-| Hashicorp Terraform       | Token da API de Terraform Cloud / Enterprise                                         |
-| Hubspot                   | Chave da API de Hubspot                                                              |
-| Mailchimp                 | Chave da API de Mailchimp                                                            |
-| Mailchimp                 | Chave da API de Mandrill                                                             |
-| Mailgun                   | Chave da API de Mailgun                                                              |
-| MessageBird               | Chave da API de MessageBird                                                          |
-| npm                       | Token de acesso de npm                                                               |
-| NuGet                     | Chave de API de NuGet                                                                |
-| Palantir                  | Token web de JSON de Palantir                                                        |
-| Plivo                     | Token de Plivo Auth                                                                  |
-| Postman                   | Chave da API de Postman                                                              |
-| Proctorio                 | Chave de Consumidor de Proctorio                                                     |
-| Proctorio                 | Chave de vínculo de Proctorio                                                        |
-| Proctorio                 | Chave de registro de Proctorio                                                       |
-| Proctorio                 | Chave de segredo de Proctorio                                                        |
-| Pulumi                    | Token de acesso de Pulumi                                                            |
-| PyPI                      | PyPI API Token                                                                       |
-| RubyGems                  | RubyGems API Key                                                                     |
-| Samsara                   | Token de API de Samsara                                                              |
-| Samsara                   | Token de acesso de OAuth de Samsara                                                  |
-| Shopify                   | Segredo compartilhado do aplicativo Shopify                                          |
-| Shopify                   | Token de acesso de Shopify                                                           |
-| Shopify                   | Token de acesso do aplicativo personalizado Shopify                                  |
-| Shopify                   | Senha do aplicativo privado Shopify                                                  |
-| Slack                     | Token da API de Slack                                                                |
-| Slack                     | URL de entrada do webhook de Slack                                                   |
-| Slack                     | URL do fluxo de trabalho do webhook de Slack                                         |
-| SSLMate                   | Chave da API de SSLMate                                                              |
-| SSLMate                   | Segredo do cluster de SSLMate                                                        |
-| Stripe                    | Chave de segredo Stripe Live                                                         |
-| Stripe                    | Chave secreta da API de Teste de Stripe                                              |
-| Stripe                    | Chave restrita da API de Stripe Live                                                 |
-| Stripe                    | Chave restrita da API de testes de Stripe                                            |
-| Tencent Cloud             | ID de segredot de Tencent Cloud                                                      |
-| Twilio                    | Identificador de string de conta de Twilio                                           |
-| Twilio                    | Chave da API de Twilio                                                               |
+| Parceiro                  | Segredo compatível                                        |
+| ------------------------- | --------------------------------------------------------- |
+| Adafruit IO               | Chave de IO de Adafruit                                   |
+| Adobe                     | Adobe Device Token                                        |
+| Adobe                     | Adobe Service Token                                       |
+| Adobe                     | Adobe Short-Lived Access Token                            |
+| Adobe                     | Adobe JSON Web Token                                      |
+| Alibaba Cloud             | Par de ID e segredo da chave de acesso à nuvem do Alibaba |
+| Amazon Web Services (AWS) | Par do ID de segredo da chave de acesso ao AWS da Amazon  |
+| Atlassian                 | Token da API de Atlassian                                 |
+| Atlassian                 | Token web de JSON de Atlassian                            |
+| Azure                     | Token de acesso pessoal do Azure DevOps                   |
+| Azure                     | Token do Azure SAS                                        |
+| Azure                     | Certificado de Gerenciamento de Serviços do Azure         |
+| Azure                     | String de conexão do Azure SQL                            |
+| Azure                     | Chave da conta de armazenamento do Azure                  |
+| Clojars                   | Token de implantação de Clojars                           |
+| CloudBees CodeShip        | Credencial de Coadship de CloudBees                       |
+| Databricks                | Token de acesso de Databricks                             |
+| Datadog                   | Chave de API de Datadog                                   |
+| Discord                   | Token de Bot de Discord                                   |
+| Doppler                   | Token pessoal de Doppler                                  |
+| Doppler                   | Token de serviço de Doppler                               |
+| Doppler                   | Token de CLI de Doppler                                   |
+| Doppler                   | Token de SCIM de Doppler                                  |
+| Dropbox                   | Token de Acesso de Dropbox                                |
+| Dropbox                   | Token de acesso à vida curta do Dropbox                   |
+| Dynatrace                 | Token de acesso de Dynatrace                              |
+| Dynatrace                 | Token interno de Dynatrace                                |
+| Finicity                  | Chave do aplicativo de Finicity                           |
+| Frame.io                  | Token web do JSON de Frame.io                             |
+| Frame.io                  | Token do desenvolvedor de Frame.io                        |
+| GitHub                    | Token de acesso pessoal do GitHub                         |
+| GitHub                    | GitHub OAuth Access Token                                 |
+| GitHub                    | GitHub Refresh Token                                      |
+| GitHub                    | Token de acesso à instalação do aplicativo GitHub         |
+| GitHub                    | Chave privada de SSH do GitHub                            |
+| GoCardless                | Token de acesso ao vivo ao GoCardless                     |
+| GoCardless                | Token de acesso de GoCardless Sandbox                     |
+| Google Cloud              | Chave da API do GOogle                                    |
+| Google Cloud              | ID da chave privada do Google Cloud                       |
+| Hashicorp Terraform       | Token da API de Terraform Cloud / Enterprise              |
+| Hubspot                   | Chave da API de Hubspot                                   |
+| Mailchimp                 | Chave da API de Mailchimp                                 |
+| Mailchimp                 | Chave da API de Mandrill                                  |
+| Mailgun                   | Chave da API de Mailgun                                   |
+| MessageBird               | Chave da API de MessageBird                               |
+| npm                       | Token de acesso de npm                                    |
+| NuGet                     | Chave de API de NuGet                                     |
+| OpenAI                    | OpenAI API Key                                            |
+| Palantir                  | Token web de JSON de Palantir                             |
+| Plivo                     | Token de Plivo Auth                                       |
+| Postman                   | Chave da API de Postman                                   |
+| Proctorio                 | Chave de Consumidor de Proctorio                          |
+| Proctorio                 | Chave de vínculo de Proctorio                             |
+| Proctorio                 | Chave de registro de Proctorio                            |
+| Proctorio                 | Chave de segredo de Proctorio                             |
+| Pulumi                    | Token de acesso de Pulumi                                 |
+| PyPI                      | PyPI API Token                                            |
+| RubyGems                  | RubyGems API Key                                          |
+| Samsara                   | Token de API de Samsara                                   |
+| Samsara                   | Token de acesso de OAuth de Samsara                       |
+| SendGrid                  | SendGrid API Key                                          |
+| Shopify                   | Segredo compartilhado do aplicativo Shopify               |
+| Shopify                   | Token de acesso de Shopify                                |
+| Shopify                   | Token de acesso do aplicativo personalizado Shopify       |
+| Shopify                   | Senha do aplicativo privado Shopify                       |
+| Slack                     | Token da API de Slack                                     |
+| Slack                     | URL de entrada do webhook de Slack                        |
+| Slack                     | URL do fluxo de trabalho do webhook de Slack              |
+| SSLMate                   | Chave da API de SSLMate                                   |
+| SSLMate                   | Segredo do cluster de SSLMate                             |
+| Stripe                    | Chave de segredo Stripe Live                              |
+| Stripe                    | Chave secreta da API de Teste de Stripe                   |
+| Stripe                    | Chave restrita da API de Stripe Live                      |
+| Stripe                    | Chave restrita da API de testes de Stripe                 |
+| Tencent Cloud             | ID de segredot de Tencent Cloud                           |
+| Twilio                    | Identificador de string de conta de Twilio                |
+| Twilio                    | Chave da API de Twilio                                    |
diff --git a/translations/pt-BR/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/pt-BR/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..ecb8f968d6
--- /dev/null
+++ b/translations/pt-BR/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,5 @@
+{% if currentVersion == "free-pro-team@latest" %}
+For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."
+{% else %}
+For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."
+{% endif %}
diff --git a/translations/pt-BR/data/reusables/security/displayed-information.md b/translations/pt-BR/data/reusables/security/displayed-information.md
index 02f38c36db..744735db2d 100644
--- a/translations/pt-BR/data/reusables/security/displayed-information.md
+++ b/translations/pt-BR/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
 When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
 
 - All the existing repositories will have the selected configuration.
-- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" %}
 - We use the permissions to scan for manifest files to apply the relevant services.
 - You'll see information on your dependency graph.
-- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} and raise pull requests{% endif %}. 
+- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} and create pull requests{% endif %}. 
diff --git a/translations/pt-BR/data/reusables/supported-languages/C.md b/translations/pt-BR/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/Cpp.md b/translations/pt-BR/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/Cs.md b/translations/pt-BR/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/go.md b/translations/pt-BR/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..40bd61946e
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/java.md b/translations/pt-BR/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/javascript.md b/translations/pt-BR/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/php.md b/translations/pt-BR/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/products-table-header.md b/translations/pt-BR/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..743339ee69
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/python.md b/translations/pt-BR/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/ruby.md b/translations/pt-BR/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/scala.md b/translations/pt-BR/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/supported-languages/typescript.md b/translations/pt-BR/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/pt-BR/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/pt-BR/data/reusables/user_settings/keeping_your_email_address_private.md
index 236230306e..25f9cc6052 100644
--- a/translations/pt-BR/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/pt-BR/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. Para manter seu endereço de e-mail privado ao realizar operações do Git baseadas na web, clique em **Manter meu endereço de e-mail privado**. ![Imagem da caixa de seleção para manter seu endereço de e-mail privado](/assets/images/help/settings/email_privacy.png)
+5. To keep your email address private when performing web-based Git operations, click **Keep my email addresses private**. ![Imagem da caixa de seleção para manter seu endereço de e-mail privado](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/pt-BR/data/reusables/user_settings/payment-info-link.md b/translations/pt-BR/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..8d441f3be4
--- /dev/null
+++ b/translations/pt-BR/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. At the top of the page, click **Payment information**. ![Payment information link](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/pt-BR/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/pt-BR/data/reusables/webhooks/code_scanning_alert_event_properties.md
index a8b62caff8..9dec7aa0af 100644
--- a/translations/pt-BR/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/pt-BR/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,6 +1,6 @@
-| Tecla        | Tipo     | Descrição                                                                                                                                                                  |
-| ------------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Ação`       | `string` | A ação que foi executada. Isto pode ser: `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch` ou `reopened`.                                     |
-| `alerta`     | `objeto` | O alerta de varredura de código envolvido no evento.                                                                                                                       |
-| `ref`        | `string` | A referência do Git do alerta de varredura de código. Quando a ação é `reopened_by_user` ou `closed_by_user`, o evento foi acionado pelo `sender` e este valor será vazio. |
-| `commit_oid` | `string` | O SHA de commit do alerta de varredura de código. Quando a ação é `reopened_by_user` ou `closed_by_user`, o evento foi acionado pelo `sender` e este valor será vazio.     |
+| Tecla        | Tipo     | Descrição                                                                                                                                                                              |
+| ------------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Ação`       | `string` | A ação que foi executada. Isto pode ser: `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch` ou `reopened`.                                                 |
+| `alerta`     | `objeto` | O alerta de varredura de código envolvido no evento.                                                                                                                                   |
+| `ref`        | `string` | A referência do Git do alerta de varredura de código. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty. |
+| `commit_oid` | `string` | O SHA de commit do alerta de varredura de código. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty.     |
diff --git a/translations/pt-BR/data/reusables/webhooks/create_properties.md b/translations/pt-BR/data/reusables/webhooks/create_properties.md
index 2b83b8bc83..022b698795 100644
--- a/translations/pt-BR/data/reusables/webhooks/create_properties.md
+++ b/translations/pt-BR/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| Tecla           | Tipo     | Descrição                                                                                                                                                                                                                             |
-| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `string` | O recurso [`ref do git`](/rest/reference/git#get-a-reference).                                                                                                                                                                        |
-| `ref_type`      | `string` | O tipo de objeto de ref do Git criado no repositório. Pode ser `branch` ou `tag`.                                                                                                                                                     |
-| `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
-| `descrição`     | `string` | Descrição atual do repositório.                                                                                                                                                                                                       |
+| Tecla           | Tipo     | Descrição                                                                                                                                                                                                                            |
+| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ref`           | `string` | O recurso [`ref do git`](/rest/reference/git#get-a-reference).                                                                                                                                                                       |
+| `ref_type`      | `string` | O tipo de objeto de ref do Git criado no repositório. Pode ser `branch` ou `tag`.                                                                                                                                                    |
+| `master_branch` | `string` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
+| `descrição`     | `string` | Descrição atual do repositório.                                                                                                                                                                                                      |
diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md
index 149cbcfe14..d5428051f1 100644
--- a/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| Tecla  | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ------ | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Ação` | `string` | A ação que foi executada. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. Se a ação é `closed` e a chave `merged` é `false`, o pull request foi fechado com commits não mesclados. Se a ação for `closed` e a chave `merged` for `verdadeira`, o pull request foi mesclado. |
+| Tecla  | Tipo     | Descrição                                                                           |
+| ------ | -------- | ----------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's tracking branch is synchronized with the source branch for the pull request, which happens when the source branch is updated.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/pt-BR/data/reusables/webhooks/sponsorship_short_desc.md b/translations/pt-BR/data/reusables/webhooks/sponsorship_short_desc.md
index 025ff2b4cd..b9c9f6da08 100644
--- a/translations/pt-BR/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/pt-BR/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-Atividade relacionada a uma listagem de patrocínios. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Sobre os Patrocinadores do GitHub](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)".
+Atividade relacionada a uma listagem de patrocínios. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte "[Sobre os Patrocinadores do GitHub](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml
index 0497e299f4..8a77452477 100644
--- a/translations/pt-BR/data/ui.yml
+++ b/translations/pt-BR/data/ui.yml
@@ -20,7 +20,7 @@ homepage:
   version_picker: Versão
 toc:
   getting_started: Introdução
-  popular_articles: Popular
+  popular: Popular
   guides: Guias
   whats_new: O que há de novo
 pages:
@@ -54,14 +54,6 @@ contribution_cta:
   button: Faça uma contribuição
   or: Ou,
   to_guidelines: aprenda como contribuir.
-enterprise_releases_list:
-  title: Versões de servidor corporativo
-  currently_supported: Atualmente compatível
-  currently_supported_message: Consulte <a href="https://github.com/enterprise">o GitHub Enterprise</a> para obter informações sobre a versão mais recente.
-  deprecated: Obsoleto
-  deprecated_message: 'Esses documentos permanecem disponíveis, mas não são mais mantidos:'
-  deprecated_developer: Obsoleto no developer.github.com
-  deprecated_developer_message: 'Estes documentos permanecem disponíveis no legado do <a href="https://developer.github.com">site de desenvolvimento</a> mas não são mais mantidos:'
 products:
   graphql:
     reference:
@@ -127,19 +119,36 @@ footer:
       press: Imprensa
       shop: Loja
 product_landing:
-  quick_start: QuickStart
-  reference_guides: Guias de referência
+  quickstart: QuickStart
+  reference: Referência
   overview: Visão Geral
+  guides: Guias
+  code_examples: Exemplos de códigos
+  search_code_examples: Exemplos de código de pesquisa
+  show_more: Show more
+  explore_people_and_projects: Explore people and projects
+  sorry: Desculpe, não há resultados para
+  no_example: It looks like we don't have an example that fits your filter.
+  try_another: Try another filter or add your code example.
+  no_result: Desculpe, não há nenhum guia que corresponda ao seu filtro.
+  learn: Learn how to add a code example
+  communities_using_discussions: Comunidades que usam discussões
+  add_your_community: Add your community
+  sponsor_community: GitHub Sponsors community
+  supported_releases: Supported releases
+  release_notes_for: Release notes for
+  upgrade_from: Upgrade from
+  browse_all_docs: Browse all docs
+  explore_release_notes: Explore release notes
 product_sublanding:
   start: Início
   start_path: Caminho de início
-  learning_paths: '{{ allProducts[currentProduct].name }} learning paths'
+  learning_paths: '{{ productMap[currentProduct].name }} learning paths'
   learning_paths_desc: Os caminhos de aprendizado são uma coleção de guias que ajudam você a dominar um assunto específico.
-  guides: '{{ allProducts[currentProduct].name }} guides'
+  guides: '{{ productMap[currentProduct].name }} guides'
   more_guides: mais guias
   load_more: Carregar mais guias
-  all_guides: 'All {{ allProducts[currentProduct].name }} guides'
-  no_result: Desculpe, não há nenhum guia que corresponda ao seu filtro.
+  all_guides: 'All {{ productMap[currentProduct].name }} guides'
   filters:
     type: Tipo
     topic: Tópico
@@ -154,3 +163,10 @@ learning_track_nav:
   prevGuide: Guia anterior
   nextGuide: Próximo guia
 contributor_callout: This article is contributed and maintained by
+toggle_images:
+  off: Images are off, click to show
+  on: Images are on, click to hide
+  hide_single: Hide image
+  show_single: Show image
+scroll_button:
+  scroll_to_top: Scroll to top
diff --git a/translations/pt-BR/data/variables/codespaces_code_examples.yml b/translations/pt-BR/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..00958245ab
--- /dev/null
+++ b/translations/pt-BR/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.js sample project
+  description: Try a Node.js project with a custom dev container
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - development containers
+- 
+  title: Python sample project
+  description: Try a Python project with a custom dev container
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - development containers
+- 
+  title: Java sample project
+  description: Try a Java project with a custom dev container
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - development containers
+- 
+  title: Go sample project
+  description: Try a Go project with a custom dev container
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - development containers
+- 
+  title: Rust sample project
+  description: Try a Rust project with a custom dev container
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - development containers
+- 
+  title: PHP sample project
+  description: Try a PHP project with a custom dev container
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - development containers
diff --git a/translations/pt-BR/data/variables/migrations.yml b/translations/pt-BR/data/variables/migrations.yml
index 13ee04f095..960b2c3476 100644
--- a/translations/pt-BR/data/variables/migrations.yml
+++ b/translations/pt-BR/data/variables/migrations.yml
@@ -4,4 +4,4 @@ user_migrations_intro: >-
 organization_migrations_intro: >-
   A API de migrações da organização permite que você transfira um repositório do GitHub para {% data variables.product.prodname_ghe_server %}.
 source_imports_intro: >-
-  A API de Importação de Código-Fonte permite que você inicie uma importação a partir de um repositório de origem no Git, Subversion, Mercurial ou Team Foundation Server. Esta é a mesma funcionalidade do Importador de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Importar um repositório com o importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
+  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Version Control source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml
index 2bf59de351..d574da2ba3 100644
--- a/translations/pt-BR/data/variables/product.yml
+++ b/translations/pt-BR/data/variables/product.yml
@@ -56,6 +56,7 @@ prodname_pages: 'GitHub Pages'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'aplicativo GitHub'
@@ -77,8 +78,7 @@ prodname_debug: 'GitHub Debug'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'GitHub Package Registry'
-prodname_github_container_registry: 'Registro de contêiner do GitHub'
-prodname_container_registry: 'registro de contêiner'
+prodname_container_registry: 'Container registry'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -91,7 +91,6 @@ prodname_advanced_security: 'Segurança Avançada'
 prodname_security_center: 'Security Center'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Espaços de códigos Visual Studio'
 prodname_github_codespaces: 'GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'Suporte à Comunidade GitHub'
diff --git a/translations/pt-BR/data/variables/release_candidate.yml b/translations/pt-BR/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/pt-BR/data/variables/release_candidate.yml
+++ b/translations/pt-BR/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/pt-BR/data/variables/sponsors_user_examples.yml b/translations/pt-BR/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..92800edaf3
--- /dev/null
+++ b/translations/pt-BR/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chayn helps women experiencing abuse find the right information and support they need to take control of their lives.
+- 
+  user: foosel
+  description: '👋 I''m Gina, and I''m mostly known for being the creator and main developer of OctoPrint 🐙.'
+- 
+  user: dayhaysoos
+  description: What's up? I'm Nick. I'm an engineer who has a new-found passion for removing friction from the e-commerce developer experience.
+- 
+  user: yyx990803
+  description: I'm working fulltime on Vue.js, a frontend JavaScript framework for building web applications, and Vite, a modern web build tool.
+- 
+  user: calebporzio
+  description: '🚶‍♂️I left my day job in Jan 2019 to pursue open-source. Since then, I''ve built Laravel Livewire, AlpineJS, and a bunch of other stuff.'
+- 
+  user: kjaymiller
+  description: Hi Y'all I'm Jay! 👋 I'm a Marine Corps Veteran turned developer that's been actively coding since 2014. I'm also involved in the productivity space where I can be found helping people with automations for some of their favorite apps and tools.
diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index 0b55e2a358..9aaf6b6ded 100644
--- a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md
index 61bf5626ce..1906d7ece3 100644
--- a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md
index 45ab3945f7..0605fd7492 100644
--- a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md
+++ b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md
@@ -222,14 +222,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-javascript-action@v1.1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
diff --git a/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 18d090f6b0..32cb81ec7e 100644
--- a/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -171,7 +171,7 @@ In this example, `cleanup.js` only runs on Linux-based runners:
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 #### `сообщение`
@@ -197,7 +197,7 @@ For example, this `cleanup.js` will only run on Linux-based runners:
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 ### `runs` for composite run steps actions
@@ -295,7 +295,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
@@ -323,7 +323,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/ru-RU/content/actions/guides/about-continuous-integration.md b/translations/ru-RU/content/actions/guides/about-continuous-integration.md
index cd2f166950..72726ab888 100644
--- a/translations/ru-RU/content/actions/guides/about-continuous-integration.md
+++ b/translations/ru-RU/content/actions/guides/about-continuous-integration.md
@@ -48,11 +48,13 @@ In addition to helping you set up CI workflows for your project, you can use {%
 For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)."
 
 ### Supported languages
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} offers CI workflow templates for a variety of languages and frameworks.
 
 Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### Skipping workflow runs
 
 If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any any of the following strings to the commit message in a push, or the HEAD commit of a pull request:
@@ -72,6 +74,7 @@ You won't be able to merge the pull request if your repository is configured to
 **Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running.
 
 {% endnote %}
+{% endif %}
 
 ### Notifications for workflow runs
 
diff --git a/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md b/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md
index 665bcacc4f..668d50fcd2 100644
--- a/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/ru-RU/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,39 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### About packaging steps
-
-A packaging step is a common part of a continuous integration or continuous delivery workflow. After building and testing your application, a runnable or deployable artifact is produced in the form of a package. For example, a continuous integration workflow for a Java project may run `mvn package` to produce a JAR file. Or, a CI workflow for a Node.js application may create a Docker container.
-
-Depending on the kind of application you're building, this package can be downloaded locally for manual testing, made available for users to download, or deployed to a staging or production environment.
-
-### Packaging in continuous integration workflows
-
-Creating a package at the end of a continuous integration workflow can help during code reviews on a pull request. After building and testing your code, a packaging step can produce a runnable or deployable artifact. Your workflow can then take that artifact and upload it as part of the workflow.
-
-Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced.
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request.
-
-### Workflows for publishing packages
-
-In addition to uploading packaging artifacts for testing in a continuous integration workflow, you can create workflows that build your project and publish packages to a package registry.
-
-* **Publish packages to {% data variables.product.prodname_registry %}**
-  {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. You can choose to share your packages with all of {% data variables.product.prodname_dotcom %}, or private packages to share with collaborators or an organization. For more information, see "[About {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)."
-
-  You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build out of master easily, by installing it from {% data variables.product.prodname_registry %}.
-
-* **Publish packages to a package registry**  
-  For many projects, publishing to a package registry is performed whenever a new version of a project is released. For example, a project that produces a JAR file may upload new releases to the Maven Central repository. Or, a .NET project may produce a nuget package and upload it to the NuGet Gallery.
-
-  You can automate this by creating a workflow that publishes packages to a package registry on every release creation. For more information, see "[Creating releases](/github/administering-a-repository/creating-releases)."
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md b/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md
index cf4673d1e3..ac6186e769 100644
--- a/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,14 +38,17 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `add-labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
 5. {% data reusables.actions.commit-workflow %}
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-net.md b/translations/ru-RU/content/actions/guides/building-and-testing-net.md
index 5cdbb65242..d0f15df5c7 100644
--- a/translations/ru-RU/content/actions/guides/building-and-testing-net.md
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-net.md
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,7 +139,7 @@ For more information, see "[Caching dependencies to speed up workflows](/actions
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
@@ -171,7 +171,7 @@ You can use the same commands that you use locally to build and test your code.
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 You can configure your workflow to publish your Dotnet package to a package registry when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your binary. The following example creates and publishes a package to {% data variables.product.prodname_registry %} using `dotnet core cli`.
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md
index a18f0da38d..46b85411ec 100644
--- a/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ We recommend that you have a basic understanding of Node.js, YAML, workflow conf
 
 {% data variables.product.prodname_dotcom %} provides a Node.js workflow template that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the template. For more information, see the [Node.js workflow template](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the template to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,14 +119,14 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 If you don't specify a Node.js version,
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md b/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md
index 2a5ee5e15d..ec2bede704 100644
--- a/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-powershell.md
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1`
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-python.md b/translations/ru-RU/content/actions/guides/building-and-testing-python.md
index 4fe13263b0..c5f71de130 100644
--- a/translations/ru-RU/content/actions/guides/building-and-testing-python.md
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-python.md
@@ -58,25 +58,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Lint with flake8
-      run: |
-        # stop the build if there are Python syntax errors or undefined names
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - name: Test with pytest
-      run: |
-        pytest
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -117,14 +117,14 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -144,17 +144,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # Semantic version range syntax or exact version of a Python version
-        python-version: '3.x'
-        # Optional - x64 or x86 architecture, defaults to x64
-        architecture: 'x64'
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
@@ -373,25 +373,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Install pip and pytest
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # Use always() to always run this step to publish test results when there are test failures
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -413,22 +413,22 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 {% endraw %}
 
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md
index 71ff62efbf..e58b1f463b 100644
--- a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ We recommend that you have a basic understanding of Ruby, YAML, workflow configu
 
 {% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the template to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,7 +264,6 @@ You can configure your workflow to publish your Ruby package to any package regi
 
 You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`.
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
@@ -272,46 +271,48 @@ name: Ruby Gem
 on:
   # Manually publish
   workflow_dispatch:
-  # Alternatively, publish whenever changes are merged to the default branch.
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-swift.md b/translations/ru-RU/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..688c7978d1
--- /dev/null
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Building and testing Swift
+intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introduction
+
+This guide shows you how to build and test a Swift package.
+
+{% if currentVersion == "github-ae@latest" %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
+{% else %}{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swift packages. For a full list of up-to-date software and the preinstalled versions of Swift and Xcode, see "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### Требования
+
+You should already be familiar with YAML syntax and how it's used with {% data variables.product.prodname_actions %}. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+
+We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
+
+### Starting with the Swift workflow template
+
+{% data variables.product.prodname_dotcom %} provides a Swift workflow template that should work for most Swift projects, and this guide includes examples that show you how to customize this template. For more information, see the [Swift workflow template](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+To get started quickly, add the template to the `.github/workflows` directory of your repository.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Specifying a Swift version
+
+To use a specific preinstalled version of Swift on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `fwal/setup-swift` action. This action finds a specific version of Swift from the tools cache on the runner and adds the necessary binaries to `PATH`. These changes will persist for the remainder of a job. For more information, see the [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) action.
+
+If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+
+The examples below demonstrate using the `fwal/setup-swift` action.
+
+#### Using multiple Swift versions
+
+You can configure your job to use a multiple versions of Swift in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Using a single specific Swift version
+
+You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### Building and testing your code
+
+You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/ru-RU/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..e5fa401d66
--- /dev/null
+++ b/translations/ru-RU/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Building and testing Xamarin applications
+intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Xamarin application.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Introduction
+
+This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. The workflow you create will allow you to see when commits to a pull request cause build or test failures against your default branch; this approach can help ensure that your code is always healthy.
+
+{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### Требования
+
+We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML, workflow configuration options, and how to create a workflow file. Дополнительные сведения см. в:
+
+- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
+- "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Bulding Xamarin.iOS apps
+
+The example below demonstrates how to change the default Xamarin bundle and build  a Xamarin.iOS application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Bulding Xamarin.Android apps
+
+The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### Specifying a .NET version
+
+To use a preinstalled version of the .NET Core SDK on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-dotnet` action. This action finds a specific version of .NET from the tools cache on each runner, and adds the necessary binaries to `PATH`. These changes will persist for the remainder of the job.
+
+The `setup-dotnet` action is the recommended way of using .NET with {% data variables.product.prodname_actions %}, because it ensures consistent behavior across different runners and different versions of .NET. If you are using a self-hosted runner, you must install .NET and add it to `PATH`. For more information, see the [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) action.
diff --git a/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index a16b3c3fdf..e7d768bf64 100644
--- a/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/ru-RU/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
 
 - `key`: **Required** The key created when saving a cache and the key used to search for a cache. Can be any combination of variables, context values, static strings, and functions. Keys have a maximum length of 512 characters, and keys longer than the maximum length will cause the action to fail.
 - `path`: **Required** The file path on the runner to cache or restore. The path can be an absolute path or relative to the working directory.
-  - With `v2` of the `cache` action, you can specify a single path, or multiple paths as a list. Paths can be either directories or single files, and glob patterns are supported.
+  - Paths can be either directories or single files, and glob patterns are supported.
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. Например:
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - With `v1` of the `cache` action, only a single path is supported and it must be a directory. You cannot cache a single file.
 - `restore-keys`: **Optional** An ordered list of alternative keys to use for finding the cache if no cache hit occurred for `key`.
 
@@ -82,30 +91,29 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-    - name: Cache node modules
-      uses: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm` on Linux/macOS
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - name: Install Dependencies
-      run: npm install
+      - name: Install Dependencies
+        run: npm install
 
-    - name: Build
-      run: npm build
-
-    - name: Test
-      run: npm test
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/ru-RU/content/actions/guides/closing-inactive-issues.md b/translations/ru-RU/content/actions/guides/closing-inactive-issues.md
index 3c90e164ff..a264104a1b 100644
--- a/translations/ru-RU/content/actions/guides/closing-inactive-issues.md
+++ b/translations/ru-RU/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,9 +51,9 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every day at 1:30 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `days-before-issue-stale` to the number of days without activity before the `actions/stale` action labels an issue. If you never want this action to label issues, set this value to `-1`.
diff --git a/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index 0b508458db..baab1d29b1 100644
--- a/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **Make sure to reference this issue in your pull request.** :sparkles: Thank you for your contribution! :sparkles:
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Replace `help-wanted` in `if: github.event.label.name == 'help-wanted'` with the label that you want to act on. If you want to act on more than one label, separate the conditions with `||`. For example, `if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` will comment whenever the `bug` or `fix me` labels are added to an issue.
    - Change the value for `body` to the comment that you want to add. GitHub flavored markdown is supported. For more information about markdown, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
diff --git a/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md b/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md
index 39e013193d..2b1a682a70 100644
--- a/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/ru-RU/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### Introduction
 
-This guide shows you workflow examples that configure a service container using the Docker Hub `postgres` image. The workflow runs a script to create a PostgreSQL client and populate the client with data. To test that the workflow creates and populates the PostgreSQL client, the script prints the client's data to the console.
+This guide shows you workflow examples that configure a service container using the Docker Hub `postgres` image. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -81,10 +81,10 @@ jobs:
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client, populates
-        # the client with data, and retrieves data
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
         run: node client.js
-        # Environment variable used by the `client.js` script to create a new PostgreSQL client.
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # The hostname used to communicate with the PostgreSQL service container
           POSTGRES_HOST: postgres
@@ -141,8 +141,8 @@ steps:
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL client, populates
-    # the client with data, and retrieves data
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
     run: node client.js
     # Environment variable used by the `client.js` script to create
     # a new PostgreSQL client.
@@ -204,11 +204,11 @@ jobs:
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client, populates
-        # the client with data, and retrieves data
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
         run: node client.js
-        # Environment variable used by the `client.js` script to create
-        # a new PostgreSQL client.
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # The hostname used to communicate with the PostgreSQL service container
           POSTGRES_HOST: localhost
@@ -268,11 +268,11 @@ steps:
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL client, populates
-    # the client with data, and retrieves data
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new PostgreSQL client.
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # The hostname used to communicate with the PostgreSQL service container
       POSTGRES_HOST: localhost
@@ -286,9 +286,9 @@ steps:
 
 ### Testing the PostgreSQL service container
 
-You can test your workflow using the following script, which creates a PostgreSQL client and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `pg` npm module. For more information, see the [npm pg module](https://www.npmjs.com/package/pg).
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `pg` npm module. For more information, see the [npm pg module](https://www.npmjs.com/package/pg).
 
-You can modify *client.js* to include any PostgreSQL operations needed by your workflow. In this example, the script creates the PostgreSQL client instance, creates a table, adds placeholder data, then retrieves the data.
+You can modify *client.js* to include any PostgreSQL operations needed by your workflow. In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-The script creates a new PostgreSQL `Client`, which accepts a `host` and `port` parameter. The script uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to set the client's IP address and port. If `host` and `port` are not defined, the default host is `localhost` and the default port is 5432.
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. If `host` and `port` are not defined, the default host is `localhost` and the default port is 5432.
 
-The script creates a table and populates it with placeholder data. To test that the PostgreSQL database contains the data, the script prints the contents of the table to the console log.
+The script creates a table and populates it with placeholder data. To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step confirming you created the PostgreSQL client and added data:
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index 5a2dd5ada0..6d7fb9f2c1 100644
--- a/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ The following example workflow demonstrates how to build a container image and p
 
 Ensure that you provide your own values for all the variables in the `env` key of the workflow.
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### Additional resources
 
diff --git a/translations/ru-RU/content/actions/guides/index.md b/translations/ru-RU/content/actions/guides/index.md
index ac729a23af..179b073117 100644
--- a/translations/ru-RU/content/actions/guides/index.md
+++ b/translations/ru-RU/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/ru-RU/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/ru-RU/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..a117c95c40
--- /dev/null
+++ b/translations/ru-RU/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Managing GitHub Actions with GitHub CLI
+intro: 'You can use {% data variables.product.prodname_cli %} to interact with {% data variables.product.prodname_actions %}.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### Setting up {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### Managing {% data variables.product.prodname_actions %} with {% data variables.product.prodname_cli %}
+
+To view all available commands related to {% data variables.product.prodname_actions %}, run `gh actions`.
+
+For more information on using commands in specific scenarios, see the following procedures:
+
+- "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)"
+- "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/ru-RU/content/actions/guides/publishing-docker-images.md b/translations/ru-RU/content/actions/guides/publishing-docker-images.md
index d425423f49..e19ae62f1f 100644
--- a/translations/ru-RU/content/actions/guides/publishing-docker-images.md
+++ b/translations/ru-RU/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ You might also find it helpful to have a basic understanding of the following:
 
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
-- "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)"
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### About image configuration
 
@@ -98,7 +98,6 @@ The `build-push-action` options required for {% data variables.product.prodname_
 * `registry`: Must be set to `docker.pkg.github.com`.
 * `repository`: Must be set in the format `OWNER/REPOSITORY/IMAGE_NAME`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `repository` option should be set to `octo-org/octo-repo/octo-image`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -107,21 +106,23 @@ on:
 jobs:
   push_to_registry:
     name: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,7 +132,6 @@ In a single workflow, you can publish your Docker image to multiple registries b
 
 The following example workflow uses the `build-push-action` steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -140,26 +140,28 @@ on:
 jobs:
   push_to_registries:
     name: Push Docker image to multiple registries
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to Docker Hub
         uses: docker/build-push-action@v1
         with:
-          username: ${{ secrets.DOCKER_USERNAME }}
-          password: ${{ secrets.DOCKER_PASSWORD }}
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
           repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, and uses the `build-push-action` action twice to build and push the Docker image to Docker Hub and {% data variables.product.prodname_registry %}. For both steps, it sets the `build-push-action` option [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) to automatically tag the built Docker image with the Git reference of the workflow event. This workflow is triggered on publishing a {% data variables.product.prodname_dotcom %} release, so the reference for both registries will be the Git tag for the release.
diff --git a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md
index 3ae75b08f5..c190c2535a 100644
--- a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ For more information about creating a CI workflow for your Java project with Gra
 
 You may also find it helpful to have a basic understanding of the following:
 
-- "[Configuring npm for use with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -108,7 +108,7 @@ Each time you create a new release, you can trigger a workflow to publish your p
 
 You can define a new Maven repository in the publishing block of your _build.gradle_ that points to {% data variables.product.prodname_registry %}.  In that repository configuration, you can also take advantage of environment variables set in your CI workflow run.  You can use the `GITHUB_ACTOR` environment variable as a username, and you can set the `GITHUB_TOKEN` environment variable with your `GITHUB_TOKEN` secret.
 
-The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.github-token-permissions %}
 
 For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example.
 
@@ -133,7 +133,6 @@ publishing {
 
 With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret.
+1. Runs the `gradle publish` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
@@ -199,7 +200,6 @@ publishing {
 
 With this configuration, you can create a workflow that publishes your package to both the Maven Central Repository and {% data variables.product.prodname_registry %} by running the `gradle publish` command.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret.
+1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
 
    For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
diff --git a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md
index c5e8b35fc1..d81367f358 100644
--- a/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/ru-RU/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ For more information about creating a CI workflow for your Java project with Mav
 
 You may also find it helpful to have a basic understanding of the following:
 
-- "[Configuring npm for use with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -112,9 +112,9 @@ This workflow performs the following steps:
 
 Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs when the `release` event triggers with type `created`. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
 
-In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, and also sets up a Maven _settings.xml_ for publishing the package to {% data variables.product.prodname_registry %}. The generated _settings.xml_ defines authentication for a server with an `id` of `github`, using the `GITHUB_ACTOR` environment variable as the username and the `GITHUB_TOKEN` environment variable as the password.
+In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, and also sets up a Maven _settings.xml_ for publishing the package to {% data variables.product.prodname_registry %}. The generated _settings.xml_ defines authentication for a server with an `id` of `github`, using the `GITHUB_ACTOR` environment variable as the username and the `GITHUB_TOKEN` environment variable as the password. The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
 
-The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.github-token-permissions %}
 
 For a Maven-based project, you can make use of these settings by creating a distribution repository in your _pom.xml_ file with an `id` of `github` that points to your {% data variables.product.prodname_registry %} endpoint.
 
@@ -137,7 +137,6 @@ For example, if your organization is named "octocat" and your repository is name
 
 With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by making use of the automatically generated _settings.xml_.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 This workflow performs the following steps:
 
@@ -173,7 +174,6 @@ You can publish your packages to both the Maven Central Repository and {% data v
 
 Ensure your _pom.xml_ file includes a distribution management repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider. For example, if you deploy to the Central Repository through the OSSRH hosting project, you might want to specify it in a distribution management repository with the `id` set to `ossrh`, and you might want to specify {% data variables.product.prodname_registry %} in a distribution management repository with the `id` set to `github`.
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 This workflow calls the `setup-java` action twice.  Each time the `setup-java` action runs, it overwrites the Maven _settings.xml_ file for publishing packages.  For authentication to the repository, the _settings.xml_ file references the distribution management repository `id`, and the username and password.
 
diff --git a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md
index 4cfdfcc3fa..6ae73f9fdb 100644
--- a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ For more information about creating a CI workflow for your Node.js project, see
 
 You may also find it helpful to have a basic understanding of the following:
 
-- "[Configuring npm for use with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[Environment variables](/actions/reference/environment-variables)"
 - "[Encrypted secrets](/actions/reference/encrypted-secrets)"
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ However, if you do provide the `repository` key, then the repository in that key
 
 #### Authenticating to the destination repository
 
-To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)."
+To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 
@@ -120,7 +120,6 @@ If you want to publish your package to a different repository, you must use a pe
 
 This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file.
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,13 +197,13 @@ If you publish a package to both registries, you'll need to ensure that your sco
 
 Ensure your *package.json* file includes the scope of your {% data variables.product.prodname_dotcom %} repository and npm registry. For example, if you plan to publish a package in the `octocat/npm-hello-world-test` repository to {% data variables.product.prodname_dotcom %} and https://www.npmjs.com/package/@octocat/npm-hello-world-test, the name in your *package.json* file would be `"name": "@octocat/npm-hello-world-test"`.
 
-To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. The `GITHUB_TOKEN` exists in your repository by default and has read and write permissions for packages in the repository where the workflow runs. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
 
 When you use the `scope` input to the `setup-node` action, the action creates an *.npmrc* file that includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the user or organization that owns the workflow file.
 
 This workflow calls the `setup-node` action two times. Each time the `setup-node` action runs, it overwrites the *.npmrc* file. The *.npmrc* file references the token that allows you to perform authenticated operations against the package registry from the `NODE_AUTH_TOKEN` environment variable. The workflow sets the `NODE_AUTH_TOKEN` environment variable each time the `npm publish` command is run, first with a token to publish to npm (`NPM_TOKEN`) and then with a token to publish to {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
 
-{% raw %}
+
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -210,28 +211,30 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v1
-      with:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    # Publish to npm
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v1
-      with:
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    # Publish to GitHub Packages
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index 07aea71cd8..96abfd942d 100644
--- a/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
 3. {% data reusables.actions.make-workflow-file %}
 4. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. Customize the parameters in your workflow file:
    - In `github.event.project_card.column_id == '12345678'`, replace `12345678` with the ID of the column where you want to un-label issues and pull requests that are moved there.
 
diff --git a/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md b/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md
index af72f9fd58..eb1dcaede4 100644
--- a/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
 2. {% data reusables.actions.make-workflow-file %}
 3. Copy the following YAML contents into your workflow file.
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. Customize the parameters in your workflow file:
    - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:20 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `assignees` to the list of {% data variables.product.prodname_dotcom %} usernames that you want to assign to the issue.
diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
index 2c09058474..2292946024 100644
--- a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -53,7 +53,7 @@ When creating a group, you must choose a policy that defines which repositories
 
    **Предупреждение**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
@@ -85,7 +85,7 @@ When creating a group, you must choose a policy that defines which organizations
 
    **Предупреждение**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
index d56c4d03b4..af1547b132 100644
--- a/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
+++ b/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -66,7 +66,7 @@ To remove a self-hosted runner from an organization, you must be an organization
 
 {% if currentVersion == "free-pro-team@latest" %}
 To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 To remove a self-hosted runner at the enterprise level of
 {% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine.
 {% endif %}
diff --git a/translations/ru-RU/content/actions/index.md b/translations/ru-RU/content/actions/index.md
index 0f1b4b9341..bd0c0559a3 100644
--- a/translations/ru-RU/content/actions/index.md
+++ b/translations/ru-RU/content/actions/index.md
@@ -22,9 +22,9 @@ featuredLinks:
     - /actions/reference/environment-variables
     - /actions/reference/encrypted-secrets
 changelog:
-  label: 'actions'
-  prefix: 'GitHub Actions:'
-product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU
+  label: actions
+  prefix: 'GitHub Actions: '
+product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
 redirect_from:
   - /articles/automating-your-workflow-with-github-actions/
   - /articles/customizing-your-project-with-github-actions/
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Code examples</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Search code examples" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Show more {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Sorry, there is no result for <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Learn how to add a code example {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index 7c87a322a0..6461c05082 100644
--- a/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/ru-RU/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md
index 447b04362d..6776d39f14 100644
--- a/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md
+++ b/translations/ru-RU/content/actions/learn-github-actions/security-hardening-for-github-actions.md
@@ -16,6 +16,7 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### Обзор
 
@@ -23,9 +24,9 @@ This guide explains how to configure security hardening for certain {% data vari
 
 ### Using secrets
 
-Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
 
-Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps the minimize risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime.
+Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime.
 
 To help prevent accidental disclosure, {% data variables.product.product_name %} uses a mechanism that attempts to redact any secrets that appear in run logs. This redaction looks for exact matches of any configured secrets, as well as common encodings of the values, such as Base64. However, because there are multiple ways a secret value can be transformed, this redaction is not guaranteed. As a result, there are certain proactive steps and good practices you should follow to help ensure secrets are redacted, and to limit other risks associated with secrets:
 
@@ -38,11 +39,12 @@ To help prevent accidental disclosure, {% data variables.product.product_name %}
     - Audit how secrets are used, to help ensure they’re being handled as expected. You can do this by reviewing the source code of the repository executing the workflow, and checking any actions used in the workflow. For example, check that they’re not sent to unintended hosts, or explicitly being printed to log output.
     - View the run logs for your workflow after testing valid/invalid inputs, and check that secrets are properly redacted, or not shown. It's not always obvious how a command or tool you’re invoking will send errors to `STDOUT` and `STDERR`, and secrets might subsequently end up in error logs. As a result, it is good practice to manually review the workflow logs after testing valid and invalid inputs.
 - **Use credentials that are minimally scoped**
-    - Make sure the credentials being used within workflows have the least privileges required, and be mindful that any user with write access to your repository has read access to all secrets configured in your repository.
+    - Make sure the credentials being used within workflows have the least privileges required, and be mindful that any user with write access to your repository has read access to all secrets configured in your repository. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." You should therefore make sure that the `GITHUB_TOKEN` is granted the minimum required permissions. It's good security practice to set the default permission for the `GITHUB_TOKEN` to read access only for repository contents. The permissions can then be increased, as required, for individual jobs within the workflow file. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." {% endif %}
 - **Audit and rotate registered secrets**
     - Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed.
     - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid.
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 - **Consider requiring review for access to secrets**
     - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)."
 {% endif %}
@@ -51,7 +53,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %}
 
 The individual jobs in a workflow can interact with (and compromise) other jobs. For example, a job querying the environment variables used by a later job, writing files to a shared directory that a later job processes, or even more directly by interacting with the Docker socket and inspecting other running containers and executing commands in them.
 
-This means that a compromise of a single action within a workflow can be very significant, as that compromised action would have access to all secrets configured on your repository, and can use the `GITHUB_TOKEN` to write to the repository. Consequently, there is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. You can help mitigate this risk by following these good practices:
+This means that a compromise of a single action within a workflow can be very significant, as that compromised action would have access to all secrets configured on your repository, and may be able to use the `GITHUB_TOKEN` to write to the repository. Consequently, there is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. You can help mitigate this risk by following these good practices:
 
 * **Pin actions to a full length commit SHA**
 
@@ -76,14 +78,14 @@ This means that a compromise of a single action within a workflow can be very si
 
 ### Considering cross-repository access
 
-{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
+{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying a workflow file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}, elevating the permissions of the `GITHUB_TOKEN` if necessary{% endif %}. Users have specific permissions for each repository, so allowing the `GITHUB_TOKEN` for one repository to grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
 
 We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended.
 
 This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference:
 
 1. **The `GITHUB_TOKEN`**
-    -  This token is intentionally scoped to the single repository that invoked the workflow, and has the same level of access as a write-access user on the repository. The token is created before each job begins and expires when the job is finished. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}can have {% else %}has {% endif %}the same level of access as a write-access user on the repository. The token is created before each job begins and expires when the job is finished. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
     - The `GITHUB_TOKEN` should be used whenever possible.
 2. **Repository deploy key**
     - Deploy keys are one of the only credential types that grant read or write access to a single repository, and can be used to interact with another repository within a workflow. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)."
@@ -102,7 +104,7 @@ This list describes the recommended approaches for accessing repository data wit
 
 **Self-hosted** runners on {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
 
-As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a PR (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the more privileged `GITHUB_TOKEN` which grants write-access permissions on the repository.
+As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a pull request (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}, depending on its settings, can grant {% else %} grants {% endif %}write-access permissions on the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner.
 
 When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
 
@@ -116,33 +118,68 @@ Some customers might attempt to partially mitigate these risks by implementing s
 
 You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which user account performed the action.
 
-For example, you can use the audit log to track the `action:org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+For example, you can use the audit log to track the `org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
 
-The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Events for environments
+
+| Действие                            | Description                                                                                                                                                     |
+| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."   |
+| `environment.delete`                | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)."       |
+| `environment.remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." |
+| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."   |
+{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+#### Events for configuration changes
+| Действие               | Description                                                                                                                                                                                                                                                              |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." |
+{% endif %}
 
 #### Events for secret management
-| Действие                            | Description                                                                                                                                                                                |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action:org.create_actions_secret`  | Triggered when a organization admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization). |
-| `action:org.remove_actions_secret`  | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret.                                                                                        |
-| `action:org.update_actions_secret`  | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret.                                                                                        |
-| `action:repo.create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).      |
-| `action:repo.remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret.                                                                                          |
-| `action:repo.update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret.                                                                                          |
+| Действие                     | Description                                                                                                                                                                                                                                                              |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `org.create_actions_secret`  | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)." |
+| `org.remove_actions_secret`  | Triggered when a {% data variables.product.prodname_actions %} secret is removed.                                                                                                                                                                                        |
+| `org.update_actions_secret`  | Triggered when a {% data variables.product.prodname_actions %} secret is updated.                                                                                                                                                                                        |
+| `repo.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."          |
+| `repo.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.                                                                                                                                                                                        |
+| `repo.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.                                                                                                                                                                                        |
 
 #### Events for self-hosted runners
-| Действие                                  | Description                                                                                                                                                                             |
-| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action:org.register_self_hosted_runner`  | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). |
-| `action:org.remove_self_hosted_runner`    | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).             |
-| `action:repo.register_self_hosted_runner` | Triggered when a repository admin [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository).       |
-| `action:repo.remove_self_hosted_runner`   | Triggered when a repository admin [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository).                   |
+| Действие                                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% else %}                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `enterprise.register_self_hosted_runner`  | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an enterprise](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)."                                                                                                                                                                                                                                                                               |
+| `enterprise.remove_self_hosted_runner`    | Triggered when a self-hosted runner is removed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `enterprise.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."                                                                                                                                                                                                                                                                                           |
+| `enterprise.self_hosted_runner_updated`   | Triggered when the runner application is updated. Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."{% endif %}
+| `org.register_self_hosted_runner`         | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)."                                                                                                                                                                                                                                                                           |
+| `org.remove_self_hosted_runner`           | Triggered when a self-hosted runner is removed. For more information, see [Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).                                                                                                                                                                                                                                                                                                  |
+| `org.runner_group_runners_updated`        | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."                                                                                                                                                                                                                                                                                           |
+| `org.runner_group_updated`                | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."                                                                                                                                                                                                          |
+| `org.self_hosted_runner_updated`          | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                          |
+| `repo.register_self_hosted_runner`        | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."                                                                                                                                                                                                                                                                                 |
+| `repo.remove_self_hosted_runner`          | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."                                                                                                                                                                                                                                                                                                      |
+| `repo.self_hosted_runner_updated`         | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                          |
 
 #### Events for self-hosted runner groups
-| Действие                                  | Description                                                                                                                                                                                                               |
-| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action:org.runner_group_created`         | Triggered when an organization admin [creates a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization). |
-| `action:org.runner_group_removed`         | Triggered when an organization admin removes a self-hosted runner group.                                                                                                                                                  |
-| `action:org.runner_group_renamed`         | Triggered when an organization admin renames a self-hosted runner group.                                                                                                                                                  |
-| `action:org.runner_group_runners_added`   | Triggered when an organization admin [adds a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).                |
-| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group.                                                                                                                                           |
+| Действие                                 | Description                                                                                                                                                                                                                                                                                                        |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `enterprise.runner_group_created`        | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an enterprise](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)."                            |
+| `enterprise.runner_group_removed`        | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."                                                                |
+| `enterprise.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group.                                                                                                                                                                                                                                   |
+| `enterprise.runner_group_runners_added`  | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."                                                       |
+| `enterprise.runner_group_updated`        | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." |
+| `org.runner_group_created`               | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."                        |
+| `org.runner_group_removed`               | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."                                                                |
+| `org.runner_group_runners_added`         | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."                                                       |
+| `org.runner_group_runner_removed`        | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."                                                 |
+
+#### Events for workflow activities
+
+{% data reusables.actions.actions-audit-events-workflow %}
diff --git a/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index 0b50e8cc2f..ad8ff1456d 100644
--- a/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ If you need to share workflows and other {% data variables.product.prodname_acti
 
 ### Creating a workflow template
 
-Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise or GitHub One plan.
+Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. Workflow templates can be used to create new workflows in an organizations' public repositories; to use templates to create workflows in private repositories, the organization must be part of an enterprise plan.
 
 This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow.
 
 1. If it doesn't already exist, create a new public repository named `.github` in your organization.
-1. Create a directory named `workflow-templates`.
-1. Create your new workflow file inside the `workflow-templates` directory.
+2. Create a directory named `workflow-templates`.
+3. Create your new workflow file inside the `workflow-templates` directory.
 
    If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch.
 
@@ -52,7 +52,7 @@ This procedure demonstrates how to create a workflow template and metadata file.
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
+4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
    ```yaml
    {
        "name": "Octo Organization Workflow",
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..a41d459b53
--- /dev/null
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: Approving workflow runs from public forks
+intro: 'When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve any workflow runs.'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+Forks of public repositories can submit pull requests that propose changes to a repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests are not run automatically if they are received from first-time contributors, and must be approved first.
+
+Maintainers with write access to the repository can use the following procedure to review and run workflows on pull requests from first-time contributors. After a contributor has at least one pull request merged into a project's repository, any future pull requests from that contributor's fork will automatically run workflows.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
+1. If you are comfortable with running workflows on the pull request branch, return to the {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
+
+   ![Approve and run workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index 5c3b16248a..9507a100cf 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Disabling and enabling a workflow
-intro: 'You can disable and re-enable a workflow using {% data variables.product.prodname_dotcom %} or the REST API.'
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}. You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
 
 Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
 
@@ -27,7 +27,9 @@ Temporarily disabling a workflow can be useful in many scenarios. These are a fe
 
 {% endwarning %}
 
-### Disabling a workflow
+### Disabling and enabling workflows with the {% data variables.product.prodname_dotcom %} UI
+
+#### Disabling a workflow
 
 You can manually disable a workflow so that it won't execute any workflow runs. A disabled workflow is not deleted, and can be re-enabled.
 
@@ -37,7 +39,7 @@ You can manually disable a workflow so that it won't execute any workflow runs.
 1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. Click **Disable workflow**. ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png) The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status. ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### Enabling a workflow
+#### Enabling a workflow
 
 You can re-enable a workflow that was previously disabled.
 
@@ -45,3 +47,23 @@ You can re-enable a workflow that was previously disabled.
 {% data reusables.repositories.actions-tab %}
 1. In the left sidebar, click the workflow you want to enable. ![actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. Click **Enable workflow**. ![actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+
+### Disabling and enabling workflows with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### Disabling and enabling workflows through the REST API
+
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 4f6f73cfca..c37ad5434f 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Configuring the retention period for GitHub Actions artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %}
 
+### Download artifacts with the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### Download artifacts with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+{% data variables.product.prodname_cli %} will download each artifact into separate directories based on the artifact name. If only a single artifact is specified, it will be extracted into the current directory.
+
+To download all artifacts generated by a workflow run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run download <em>run-id</em>
+```
+
+To download a specific artifact from a run, use the `run download` subcommand. Replace `run-id` with the ID of the run that you want to download artifacts from. Replace `artifact-name` with the name of the artifact that you want to download.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+You can specify more than one artifact.
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+To download specific artifacts across all runs in a repository, use the `run download` subcommand.
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/index.md b/translations/ru-RU/content/actions/managing-workflow-runs/index.md
index 2606df2f97..2e9d581196 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/index.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index 9ac6d7f072..7388e7af69 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: Manually running a workflow
-intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the REST API or from the Actions tab on {% data variables.product.prodname_dotcom %}.'
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -28,6 +28,40 @@ To trigger the `workflow_dispatch` event on {% data variables.product.prodname_d
 1. Above the list of workflow runs, select **Run workflow**. ![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
 1. Select the branch where the workflow will run and type the input parameters used by the workflow. Click **Run workflow**. ![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
 
+### Running a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+You can also pass inputs as JSON by using standard input.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
+
 ### Running a workflow using the REST API
 
 When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md
index f72ee39863..171c1397f3 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Re-run a workflow using the {% data variables.product.prodname_dotcom %} UI
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### Re-run a workflow using {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run.  If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 51b0352ed6..9f5b117a0e 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. Under **Artifacts**, click
-{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove.
+{% octicon "trash" aria-label="The trash icon" %} next to the artifact you want to remove.
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index db404eeba7..55b1e2f6b3 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ After deleting logs, the **Delete all logs** button is removed to indicate that
 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) After the logs have been deleted, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
 {% endif %}
+
+### Viewing logs with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+To view the log for a specific job, use the `run view` subcommand. Replace `run-id` with the ID of run that you want to view logs for. {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a job from the run. If you don't specify `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run, and then returns another interactive menu for you to choose a job from the run.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+You can also use the `--job` flag to specify a job ID. Replace `job-id` with the ID of the job that you want to view logs for.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+You can use `grep` to search the log. For example, this command will return all log entries that contain the word `error`.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+To filter the logs for any failed steps, use `--log-failed` instead of `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/ru-RU/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index 284bd3fcd9..9e507b8b21 100644
--- a/translations/ru-RU/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/ru-RU/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### Viewing workflow run history on {% data variables.product.prodname_dotcom %}
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### Viewing workflow run history with {% data variables.product.prodname_cli %}
+
+{% data reusables.actions.actions-cli %}
+
+#### Viewing recent workflow runs
+
+To list the recent workflow runs, use the `run list` subcommand.
+
+```shell
+gh run list
+```
+
+To specify the maximum number of runs to return, you can use the `-L` or `--limit` flag . По умолчанию - `10`.
+
+```shell
+gh run list --limit 5
+```
+
+To only return runs for the specified workflow, you can use the `-w` or `--workflow` flag.  Replace `workflow` with either the workflow name, workflow ID, or workflow file name. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### Viewing details for a specific workflow run
+
+To display details for a specific workflow run, use the `run view` subcommand. Replace `run-id` with the ID of the run that you want to view. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent run.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+To include job steps in the output, use the `-v` or `--verbose` flag.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+To view details for a specific job in the run, use the `-j` or `--job` flag.  Replace `job-id` with the ID of the job that you want to view.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+To view the full log for a job, use the `--log` flag.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Use the `--exit-status` flag to exit with a non-zero status if the run failed. Например:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md b/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md
index 40060919d9..f4c992a651 100644
--- a/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/ru-RU/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ The token is also available in the `github.token` context. For more information,
 
 ### Using the `GITHUB_TOKEN` in a workflow
 
-To use the `GITHUB_TOKEN` secret, you must reference it in your workflow file. Using a token might include passing the token as an input to an action that requires it, or making authenticated {% data variables.product.prodname_dotcom %} API calls.
+You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% data variables.product.prodname_dotcom %} API request.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### Example passing `GITHUB_TOKEN` as an input
+#### Example 1: passing the `GITHUB_TOKEN` as an input
 
 This example workflow uses the [labeler action](https://github.com/actions/labeler), which requires the `GITHUB_TOKEN` as the value for the `repo-token` input parameter:
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### Example calling the REST API
+#### Example 2: calling the REST API
 
 You can use the `GITHUB_TOKEN` to make authenticated API calls. This example workflow creates an issue using the {% data variables.product.prodname_dotcom %} REST API:
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,15 +88,31 @@ You can use the `GITHUB_TOKEN` to make authenticated API calls. This example wor
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n The commit hash was: _${{ github.sha }}_."
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### Permissions for the `GITHUB_TOKEN`
 
 For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)."
 
-| Permission          | Access type | Access by forked repos |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an enterprise, organization, or repository 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 {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-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 "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
+
+| Scope               | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
+| ------------------- | ------------------------------------ | ------------------------------------ | --------------------------------------- |
+| actions             | read/write                           | нет                                  | read                                    |
+| checks              | read/write                           | нет                                  | read                                    |
+| contents            | read/write                           | read                                 | read                                    |
+| deployments         | read/write                           | нет                                  | read                                    |
+| issues              | read/write                           | нет                                  | read                                    |
+| метаданные          | read                                 | read                                 | read                                    |
+| пакеты              | read/write                           | нет                                  | read                                    |
+| pull requests       | read/write                           | нет                                  | read                                    |
+| repository projects | read/write                           | нет                                  | read                                    |
+| security events     | read/write                           | нет                                  | read                                    |
+| statuses            | read/write                           | нет                                  | read                                    |
+{% else %}
+| Scope               | Access type | Access by forked repos |
 | ------------------- | ----------- | ---------------------- |
 | actions             | read/write  | read                   |
 | checks              | read/write  | read                   |
@@ -94,9 +124,32 @@ For information about the API endpoints {% data variables.product.prodname_githu
 | pull requests       | read/write  | read                   |
 | repository projects | read/write  | read                   |
 | statuses            | read/write  | read                   |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### Modifying the permissions for the `GITHUB_TOKEN`
+
+You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access.
+
+You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "Set up job" section of the workflow run log. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+
+You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
+
+{% data reusables.github-actions.forked-write-permission %}
+
+The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
+
+For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+
+##### How the permissions are calculated for a workflow job
+
+The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
+
+#### Granting additional permissions
+{% endif %}
+
 If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a personal access token and set it as a secret in your repository:
 
 1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
diff --git a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index fdfdca30f5..0d40d76e2b 100644
--- a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ Contexts are a way to access information about workflow runs, runner environment
 | Context name | Тип      | Description                                                                                                                                                                                                                                       |
 | ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `github`     | `объект` | Information about the workflow run. For more information, see [`github` context](#github-context).                                                                                                                                                |
-| `env`        | `объект` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context) .                                                                                                                         |
+| `env`        | `объект` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context).                                                                                                                          |
 | `задание`    | `объект` | Information about the currently executing job. For more information, see [`job` context](#job-context).                                                                                                                                           |
 | `steps`      | `объект` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context).                                                                                                                          |
 | `runner`     | `объект` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context).                                                                                                                      |
@@ -93,11 +93,11 @@ The `github` context contains information about the workflow run and the event t
 | `github.action`           | `строка` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `run` when the current step runs a script.  If you use the same action more than once in the same job, the name will include a suffix with the sequence number.  For example, the first script you run will have the name `run1`, and the second script will be named `run2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
 | `github.action_path`      | `строка` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite run steps actions.                                                                                                                                                                                                                                                                                                 |
 | `github.actor`            | `строка` | The login of the user that initiated the workflow run.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `github.base_ref`         | `строка` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`.                                                                                                                                                                                                                                                                                                                             |
+| `github.base_ref`         | `строка` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                                                                                                                                                                                                               |
 | `github.event`            | `объект` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context.                                                                                                                                                                                                                                                                                        |
 | `github.event_name`       | `строка` | The name of the event that triggered the workflow run.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | `github.event_path`       | `строка` | The path to the full event webhook payload on the runner.                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `github.head_ref`         | `строка` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`.                                                                                                                                                                                                                                                                                                                             |
+| `github.head_ref`         | `строка` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                                                                                                                                                                                                                                                               |
 | `github.job`              | `строка` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                                                                                                                                                                                                                                                |
 | `github.ref`              | `строка` | The branch or tag ref that triggered the workflow run. For branches this in the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                          |
 | `github.repository`       | `строка` | The owner and repository name. For example, `Codertocat/Hello-World`.                                                                                                                                                                                                                                                                                                                                                                                                                               |
@@ -323,7 +323,7 @@ Returns `true` if `searchString` ends with `searchValue`. This function is not c
 
 `format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
 
-Replaces values in the `string`, with the variable `replaceValueN`. Variables in the `string` are specified using the `{N}` syntax, where `N` is an integer. You must specify at least one `replaceValue` and `string`. There is no maximum for the number of variables (`replaceValueN`) you can use. Escape curly braces useing double braces.
+Replaces values in the `string`, with the variable `replaceValueN`. Variables in the `string` are specified using the `{N}` syntax, where `N` is an integer. You must specify at least one `replaceValue` and `string`. There is no maximum for the number of variables (`replaceValueN`) you can use. Escape curly braces using double braces.
 
 ##### Пример
 
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
diff --git a/translations/ru-RU/content/actions/reference/encrypted-secrets.md b/translations/ru-RU/content/actions/reference/encrypted-secrets.md
index 85b34888d9..c82835fae6 100644
--- a/translations/ru-RU/content/actions/reference/encrypted-secrets.md
+++ b/translations/ru-RU/content/actions/reference/encrypted-secrets.md
@@ -29,15 +29,9 @@ For secrets stored at the environment level, you can enable required reviewers t
 
 #### Naming your secrets
 
-The following rules apply to secret names:
+{% data reusables.codespaces.secrets-naming %}. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
 
-* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
-* Secret names must not start with the `GITHUB_` prefix.
-* Secret names must not start with a number.
-* Secret names are not case-sensitive.
-* Secret names must be unique at the level they are created at. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
-
-  If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
+  {% data reusables.codespaces.secret-precedence %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
 
 To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs.
 
@@ -83,7 +77,8 @@ If your repository {% if currentVersion == "free-pro-team@latest" or currentVers
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" }
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+
 ### Creating encrypted secrets for an environment
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
@@ -125,7 +120,11 @@ You can check which access policies are being applied to a secret in your organi
 
 ### Using encrypted secrets in a workflow
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
+
+**Note:** {% data reusables.actions.forked-secrets %}
+
+{% endnote %}
 
 To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 
diff --git a/translations/ru-RU/content/actions/reference/environment-variables.md b/translations/ru-RU/content/actions/reference/environment-variables.md
index 9248fb40e8..c50dbf6af6 100644
--- a/translations/ru-RU/content/actions/reference/environment-variables.md
+++ b/translations/ru-RU/content/actions/reference/environment-variables.md
@@ -58,6 +58,7 @@ We strongly recommend that actions use environment variables to access the files
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
 | `GITHUB_JOB`         | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job.                                                                                                                                                                                                                                                                 |
 | `GITHUB_ACTION`      | The unique identifier (`id`) of the action.                                                                                                                                                                                                                                                                                                                        |
+| `GITHUB_ACTION_PATH` | The path where your action is located. You can use this path to access files located in the same repository as your action. This variable is only supported in composite run steps actions.                                                                                                                                                                        |
 | `GITHUB_ACTIONS`     | Always set to `true` when {% data variables.product.prodname_actions %} is running the workflow. You can use this variable to differentiate when tests are being run locally or by {% data variables.product.prodname_actions %}.                                                                                                                                |
 | `GITHUB_ACTOR`       | The name of the person or app that initiated the workflow. For example, `octocat`.                                                                                                                                                                                                                                                                                 |
 | `GITHUB_REPOSITORY`  | The owner and repository name. For example, `octocat/Hello-World`.                                                                                                                                                                                                                                                                                                 |
@@ -84,10 +85,6 @@ We strongly recommend that actions use environment variables to access the files
 
 ### Naming conventions for environment variables
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_dotcom %} reserves the `GITHUB_` environment variable prefix for internal use by {% data variables.product.prodname_dotcom %}. Setting an environment variable or secret with the `GITHUB_` prefix will result in an error.
-
-{% endnote %}
+When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
 
 Any new environment variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `HOME` and `GITHUB_WORKSPACE` default variables are exceptions to this convention because the words "home" and "workspace" already imply a location.
diff --git a/translations/ru-RU/content/actions/reference/environments.md b/translations/ru-RU/content/actions/reference/environments.md
index d0e0ca0360..176d45cb8d 100644
--- a/translations/ru-RU/content/actions/reference/environments.md
+++ b/translations/ru-RU/content/actions/reference/environments.md
@@ -48,6 +48,12 @@ Use deployment branches to restrict which branches can deploy to the environment
 
 Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 
+{% note %}
+
+**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level as security as repository and organization secrets. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+{% endnote %}
+
 ### Creating an environment
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -71,6 +77,9 @@ For more information on syntax to reference environments in workflows, see "[Wor
 
 When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
+### Using concurrency to serialize deployments in an environment
+You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#concurrency)."
+
 ### Deleting an environment
 
 {% data reusables.github-actions.permissions-statement-environment %}
@@ -80,7 +89,7 @@ Deleting an environment will delete all secrets and protection rules associated
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
+1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
 2. Click **I understand, delete this environment**.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
diff --git a/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md b/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md
index 04e24a3131..8d258a8e2b 100644
--- a/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        echo "- in ${{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          echo "- in ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ Runs your workflow anytime the `check_run` event occurs. {% data reusables.devel
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload                              | Activity types                                                                               | `GITHUB_SHA`                  | `GITHUB_REF`   |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ----------------------------- | -------------- |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | Last commit on default branch | Default branch |
+| Webhook event payload                              | Activity types                                                | `GITHUB_SHA`                  | `GITHUB_REF`   |
+| -------------------------------------------------- | ------------------------------------------------------------- | ----------------------------- | -------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | Last commit on default branch | Default branch |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a check run has been `rerequested` or `requested_action`.
+For example, you can run a workflow when a check run has been `rerequested` or `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ For example, you can run a workflow when a project card has been `opened` or `de
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**Note:** The `prereleased` type will not trigger for pre-releases published from draft releases, but the `published` type will trigger. If you want a workflow to run when stable *and* pre-releases publish, subscribe to `published` instead of `released` and `prereleased`.
+
+{% endnote %}
+
 #### `состояние`
 
 Runs your workflow anytime the status of a Git commit changes, which triggers the `status` event. For information about the REST API, see [Statuses](/rest/reference/repos#statuses).
diff --git a/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md b/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md
index 6b0367608b..8c3c902bb0 100644
--- a/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/ru-RU/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### Adding a system path
diff --git a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md
index 17cca6c83b..5fdaef15ea 100644
--- a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -110,8 +110,8 @@ The following workflow will run on pushes to `releases/10` or `releases/beta/mon
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
@@ -128,7 +128,7 @@ When all the path names match patterns in `paths-ignore`, the workflow will not
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
 #### Example including paths
@@ -139,7 +139,7 @@ If at least one path matches a pattern in the `paths` filter, the workflow runs.
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
 #### Excluding paths
@@ -160,8 +160,8 @@ This example runs anytime the `push` event includes a file in the `sub-project`
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
 #### Git diff comparisons
@@ -187,6 +187,32 @@ For more information, see "[About comparing branches in pull requests](/articles
 
 For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)."
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+You can use `permissions` either as a top-level key, to apply to all jobs in the workflow, or within specific jobs. When you add the `permissions` key within a specific job, all actions and run commands within that job that use the `GITHUB_TOKEN` gain the access rights you specify.  For more information, see [`jobs.<job_id>.permissions`](#jobsjob_idpermissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Пример
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will apply to all jobs in the workflow. All permissions are granted read access.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
+
 ### `env`
 
 A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
@@ -221,6 +247,18 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the `github` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+You can also specify `concurrency` at the job level. For more information, see [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs`
 
 A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs.<job_id>.needs` keyword.
@@ -339,6 +377,34 @@ runs-on: [self-hosted, linux]
 
 For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
+
+You can modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](#permissions).
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### Пример
+
+This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access.
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 ### `jobs.<job_id>.environment`
 
@@ -347,10 +413,11 @@ The environment that the job references. All environment protection rules must p
 You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
 
 ##### Example using a single environment name
-
+{% raw %}
 ```yaml
 environment: staging_environment
 ```
+{% endraw %}
 
 ##### Example using environment name and URL
 
@@ -372,6 +439,25 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other.
+
+{% endnote %}
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+You can also specify `concurrency` at the workflow level. For more information, see [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
 A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs.<job_id>.needs`](#jobsjob_idneeds).
@@ -392,15 +478,15 @@ jobs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
@@ -470,14 +556,14 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
@@ -609,11 +695,11 @@ jobs:
 ```
 
 {% if currentVersion == "free-pro-team@latest" %}
-##### Example using the {% data variables.product.prodname_github_container_registry %}
+##### Example using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in the {% data variables.product.prodname_github_container_registry %}.
+A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
 
 ```yaml
 jobs:
@@ -639,7 +725,9 @@ jobs:
 
 #### Example using action inside a different private repository than the workflow
 
-Your workflow must checkout the private repository and reference the action locally.
+Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
 
 {% raw %}
 ```yaml
@@ -651,7 +739,7 @@ jobs:
         with:
           repository: octocat/my-private-repo
           ref: v1.0
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
           path: ./.github/actions/my-private-repo
       - name: Run my action
         uses: ./.github/actions/my-private-repo/my-action
@@ -899,7 +987,7 @@ The order that you define a `matrix` matters. The first option you define will b
 
 #### Example running with more than one version of Node.js
 
-You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 6, 8, and 10, you could specify an array of those versions in the `matrix`.
+You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 10, 12, and 14, you could specify an array of those versions in the `matrix`.
 
 This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version.
 
@@ -907,10 +995,10 @@ This example creates a matrix of three jobs by setting the `node` key to an arra
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
   # Configures the node version used on GitHub-hosted runners
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       # The Node.js version to configure
       node-version: ${{ matrix.node }}
@@ -933,10 +1021,10 @@ You can create a matrix to run workflows on more than one runner operating syste
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
@@ -948,7 +1036,7 @@ steps:
 
 #### Example including additional values into combinations
 
-You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 4 of `node` runs, you can use `include` to specify that additional option.
+You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 8 of `node` runs, you can use `include` to specify that additional option.
 
 {% raw %}
 ```yaml
@@ -956,29 +1044,29 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 2
+      # includes a new variable of npm with a value of 6
       # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
 #### Example including new combinations
 
-You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 12 to build on multiple operating systems, but wanted one extra experimental job using node version 13 on Ubuntu, you can use `include` to specify that additional job.
+You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 14 to build on multiple operating systems, but wanted one extra experimental job using node version 15 on Ubuntu, you can use `include` to specify that additional job.
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -994,11 +1082,11 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # excludes node 4 on macOS
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
@@ -1033,7 +1121,7 @@ Prevents a workflow run from failing when a job fails. Set to `true` to allow a
 
 #### Example preventing a specific failing matrix job from failing a workflow run
 
-You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `13` to fail without failing the workflow run.
+You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
 
 {% raw %}
 ```yaml
@@ -1042,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -1064,7 +1152,7 @@ If you do not set a `container`, all steps will run directly on the host specifi
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -1079,7 +1167,7 @@ When you only specify a container image, you can omit the `image` keyword.
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
@@ -1181,7 +1269,7 @@ The Docker image to use as the service container to run the action. The value ca
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 1889ddc093..d02975e6e1 100644
--- a/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ For the overall list of included tools for each runner operating system, see the
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ We recommend using actions to interact with the software installed on runners. T
 
 If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners.
 
+#### Installing additional software
+
+You can install additional software on {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Customizing GitHub-hosted runners](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
 ### IP addresses
 
 {% note %}
diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..fa8b92c9d6
--- /dev/null
+++ b/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Customizing GitHub-hosted runners
+intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow.
+
+To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+
+This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner.
+
+### Installing software on Ubuntu runners
+
+The following example demonstrates how to install an `apt` package as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**Note:** Always run `sudo apt-get update` before installing a package. In case the `apt` index is stale, this command fetches and re-indexes any available packages, which helps prevent package installation failures.
+
+{% endnote %}
+
+### Installing software on macOS runners
+
+The following example demonstrates how to install Brew packages and casks as part of a job.
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### Installing software on Windows runners
+
+The following example demonstrates how to use [Chocolatey](https://community.chocolatey.org/packages) to install the {% data variables.product.prodname_dotcom %} CLI as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/index.md b/translations/ru-RU/content/actions/using-github-hosted-runners/index.md
index 681269a253..fb91ee9e64 100644
--- a/translations/ru-RU/content/actions/using-github-hosted-runners/index.md
+++ b/translations/ru-RU/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% link_in_list /about-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md
index ae80f57784..4e24052a85 100644
--- a/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md
+++ b/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
 title: Using groups to manage access to AE hosted runners
-intro: You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.
+intro: 'You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.'
 versions:
   github-ae: '*'
 ---
diff --git a/translations/ru-RU/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/ru-RU/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..9793d2f7e2
--- /dev/null
+++ b/translations/ru-RU/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: About licensing for GitHub Advanced Security
+intro: 'You need a license to use {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### About licensing for {% data variables.product.prodname_GH_advanced_security %}
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% data reusables.advanced-security.license-overview %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for {% data variables.product.product_name %}, contact {% data variables.contact.contact_enterprise_sales %}. To enable {% data variables.product.prodname_GH_advanced_security %}, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your appliance](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### Managing your license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+
+For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+
+### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..e380519195
--- /dev/null
+++ b/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: Configuring code scanning for your appliance
+shortTitle: Configuring code scanning
+intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### About {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+### Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
+
+#### Setting up a self-hosted runner
+
+{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions.
+
+#### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+
+You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
+
+#### Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access
+If the server on which you are running {% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} action sync tool to copy the {% data variables.product.prodname_codeql %} analysis bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/).
+
+If you set up the {% data variables.product.prodname_codeql %} action sync tool, you can use it to sync the latest releases of the {% data variables.product.prodname_codeql %} action and associated {% data variables.product.prodname_codeql %} analysis bundle. These are compatible with {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways.
+
+- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)."
+- If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer.
+- You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases.
+{% endif %}
+
+#### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}
+1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)."
+2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
+3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
+4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}
+If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}.
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
diff --git a/translations/ru-RU/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/ru-RU/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..235ca27807
--- /dev/null
+++ b/translations/ru-RU/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: Configuring secret scanning for your appliance
+shortTitle: Configuring secret scanning
+intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### About {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+
+### Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+
+- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.product.product_location %}.
+
+- A license for {% data variables.product.prodname_GH_advanced_security %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### Checking support for the SSSE3 flag on your vCPUs
+
+The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance.
+
+1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+2. Enter the following command:
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs.
+
+#### Checking whether you have an {% data variables.product.prodname_advanced_security %} license
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### Enabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. ![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### Disabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_secret_scanning_caps %}**. ![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..0c598b26ed
--- /dev/null
+++ b/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% if currentVersion == "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+{% endif %}
+
+### Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} For information about licensing, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
+2. Upload the new license to {% data variables.product.product_location %}. For more information, see "[Managing your GitHub Enterprise license](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Under "{% data variables.product.prodname_advanced_security %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+
+### Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} via the administrative shell (SSH)
+
+You can enable or disable features programmatically on {% data variables.product.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)."
+
+For example, you can enable {% data variables.product.prodname_code_scanning %} with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
+
+1. SSH into {% data variables.product.product_location %}.
+1. Enable {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. Optionally, disable {% data variables.product.prodname_code_scanning %}.
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. Apply the configuration.
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}To enable and disable {% data variables.product.prodname_secret_scanning %} in the same way, set: `ghe-config app.secret-scanning.enabled` true or false and apply the configuration.{% endif %}
diff --git a/translations/ru-RU/content/admin/advanced-security/index.md b/translations/ru-RU/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..7761e2edff
--- /dev/null
+++ b/translations/ru-RU/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing GitHub Advanced Security for your enterprise
+shortTitle: Managing GitHub Advanced Security
+intro: You can configure {% data variables.product.prodname_advanced_security %} and manage use by your enterprise to suit your organization's needs.
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### Table of Contents
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/ru-RU/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/ru-RU/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..670d420947
--- /dev/null
+++ b/translations/ru-RU/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,23 @@
+---
+title: Viewing your GitHub Advanced Security usage
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."
+
+### Viewing license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+You can check how many seats your license includes and how many seats are currently in use.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[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/ru-RU/content/admin/all-releases.md b/translations/ru-RU/content/admin/all-releases.md
new file mode 100644
index 0000000000..4205448568
--- /dev/null
+++ b/translations/ru-RU/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Enterprise Server releases
+intro: 'Documentation for the currently supported and previously deprecated versions of {{ site.data.variables.product.prodname_ghe_server }}.'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## Currently supported
+
+See [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) for information about the latest release.
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## Deprecated
+
+Documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## Deprecated developer documentation
+
+Developer documentation for deprecated versions remains available but is no longer maintained.
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/ru-RU/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/ru-RU/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index 3e949e71aa..6bdfb2204d 100644
--- a/translations/ru-RU/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: 'You can use {% if enterpriseServerVersions contains currentVersion %}{%
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### About identity and access management for your enterprise
diff --git a/translations/ru-RU/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/ru-RU/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index 8636baf933..ecd0b681df 100644
--- a/translations/ru-RU/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/ru-RU/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### About built-in authentication for users outside your identity provider
diff --git a/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md b/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md
index 5f2d5efa5b..81dd010f34 100644
--- a/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/ru-RU/content/admin/authentication/changing-authentication-methods.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 User accounts on {% data variables.product.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change.
diff --git a/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 28ab7aa1f7..d90372f635 100644
--- a/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About authentication and user provisioning with Azure AD
diff --git a/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index 0c515ab69f..823be287c3 100644
--- a/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About SAML SSO
diff --git a/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index bf715fa725..924a51f302 100644
--- a/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### About user provisioning for your enterprise
diff --git a/translations/ru-RU/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/ru-RU/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index 5b05b167d2..c420e4f682 100644
--- a/translations/ru-RU/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/ru-RU/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: 'If you''re using built-in authentication, you can block unauthenticated people from being able to create an account.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/authentication/using-built-in-authentication.md b/translations/ru-RU/content/admin/authentication/using-built-in-authentication.md
index 2a1d42b98e..31e6d36e57 100644
--- a/translations/ru-RU/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/ru-RU/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 You can create custom messages that users will see on the sign in and sign out pages. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)."
diff --git a/translations/ru-RU/content/admin/authentication/using-cas.md b/translations/ru-RU/content/admin/authentication/using-cas.md
index 3338c2df2d..d818543de7 100644
--- a/translations/ru-RU/content/admin/authentication/using-cas.md
+++ b/translations/ru-RU/content/admin/authentication/using-cas.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% if currentVersion ver_gt "enterprise-server@2.16" %}user license{% else %}seat{% endif %} until the user signs in.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ru-RU/content/admin/authentication/using-ldap.md b/translations/ru-RU/content/admin/authentication/using-ldap.md
index 8a1c4ca5fc..2ebeba0f3a 100644
--- a/translations/ru-RU/content/admin/authentication/using-ldap.md
+++ b/translations/ru-RU/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: 'LDAP lets you authenticate {% data variables.product.prodname_ghe_server %} against your existing accounts and centrally manage repository access. LDAP is a popular application protocol for accessing and maintaining directory information services, and is one of the most common protocols used to integrate third-party software with large company user directories.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ru-RU/content/admin/authentication/using-saml.md b/translations/ru-RU/content/admin/authentication/using-saml.md
index 525b76736d..c1a1432e67 100644
--- a/translations/ru-RU/content/admin/authentication/using-saml.md
+++ b/translations/ru-RU/content/admin/authentication/using-saml.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'SAML is an XML-based standard for authentication and authorization. {% data variables.product.prodname_ghe_server %} can act as a service provider (SP) with your internal SAML identity provider (IdP).'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/ru-RU/content/admin/configuration/about-enterprise-configuration.md b/translations/ru-RU/content/admin/configuration/about-enterprise-configuration.md
index 6e67acb453..bb50e63161 100644
--- a/translations/ru-RU/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/ru-RU/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: 'You can use the site admin dashboard{% if enterpriseServerVersions conta
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 The first time you access your enterprise, you will complete an initial configuration to get
-{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an idP, authenticating with SAML SSO, and configuring policies for repositories and organizations in your enterprise. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-
-For users to receive any emails from {% data variables.product.product_name %} after the initial configuration, you must ask {% data variables.contact.github_support %} to configure outbound email support with your SMTP server. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)."
+{% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an identity provider (IdP), authenticating with SAML SSO, configuring policies for repositories and organizations in your enterprise, and configuring SMTP for outbound email. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
 
 Later, you can use the site admin dashboard and enterprise settings to further configure your enterprise, manage users, organizations and repositories, and set policies that reduce risk and increase quality.
 
diff --git a/translations/ru-RU/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/ru-RU/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index 6fd326734b..a7f7caae00 100644
--- a/translations/ru-RU/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/ru-RU/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### About administrative shell access
diff --git a/translations/ru-RU/content/admin/configuration/accessing-the-management-console.md b/translations/ru-RU/content/admin/configuration/accessing-the-management-console.md
index f0adf005d9..5b2b4d0ca8 100644
--- a/translations/ru-RU/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/ru-RU/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### About the {% data variables.enterprise.management_console %}
diff --git a/translations/ru-RU/content/admin/configuration/command-line-utilities.md b/translations/ru-RU/content/admin/configuration/command-line-utilities.md
index 3337dd9f8e..7392567981 100644
--- a/translations/ru-RU/content/admin/configuration/command-line-utilities.md
+++ b/translations/ru-RU/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
@@ -483,9 +485,15 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 To show the full hook payload, result, and any exceptions for the delivery:
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### Clustering
 
@@ -644,14 +652,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-This utility imports from Team Foundation Version Control. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+This utility imports from Team Foundation Version Control (TFVC). For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFS, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
 ```shell
 git-import-rewrite
 ```
diff --git a/translations/ru-RU/content/admin/configuration/configuring-a-hostname.md b/translations/ru-RU/content/admin/configuration/configuring-a-hostname.md
index 54160261c6..969ed98d2c 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that {% data variables.product.product_location %} runs on without affecting users or client software.
diff --git a/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 5f5c4ffbf2..af7829ccc9 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 When a proxy server is enabled for {% data variables.product.product_location %}, outbound messages sent by {% data variables.product.prodname_ghe_server %} are first sent through the proxy server, unless the destination host is added as an HTTP proxy exclusion. Types of outbound messages include outgoing webhooks, uploading bundles, and fetching legacy avatars. The proxy server's URL is the protocol, domain or IP address, plus the port number, for example `http://127.0.0.1:8123`.
diff --git a/translations/ru-RU/content/admin/configuration/configuring-applications.md b/translations/ru-RU/content/admin/configuration/configuring-applications.md
index c537b568d9..7840ded67f 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-applications.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### Adjusting image caching
diff --git a/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md
index fe628944c4..d38a6ab94b 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: Configuring backups on your appliance
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### About {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/ru-RU/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/ru-RU/content/admin/configuration/configuring-built-in-firewall-rules.md
index 098709faab..bdb64f0a92 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### About {% data variables.product.product_location %}'s firewall
diff --git a/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index a97591e39a..19c11b2328 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: Configuring data encryption
 intro: 'For encryption at rest, you can provide your own encryption key to encrypt your data under your encryption policies.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 To provide a high level of security, {% data variables.product.product_name %} encrypts your data while at rest in the data centers and while your data is in transit between users' machines and the data centers.
 
-For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. After you've initialized your enterprise, you can choose to provide your own key instead. Your key should be a 2048 bit RSA private key in PEM format.
-
-The key that you provide is stored in a FIPS 140-2 compliant hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages.
-
-To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
-
-### Adding or updating an encryption key
-
-You can add a new encryption key as often as you need. When you add a new key, the old key is discarded. Your enterprise won't experience downtime when you update the key.
-
-Your 2048 bit RSA private key should be in PEM format, for example in a file called _private-key.pem_.
-
-   ```
-   -----BEGIN RSA PRIVATE KEY-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----END RSA PRIVATE KEY-----
-   ```
-
-1. To add your key, use the `PATCH /enterprise/encryption` endpoint, replacing *~/private-key.pem* with the path to your private key.
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. Optionally, check the status of the update operation.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### Disabling your encryption key
-
-To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
-
-1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest.
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
-
-### Дополнительная литература
-
-- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation 
+For encryption in transit, {% data variables.product.product_name %} uses Transport Layer Security (TLS). For encryption at rest, {% data variables.product.product_name %} provides a default RSA key. 
diff --git a/translations/ru-RU/content/admin/configuration/configuring-dns-nameservers.md b/translations/ru-RU/content/admin/configuration/configuring-dns-nameservers.md
index b4179fd598..96a0e4954f 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 The nameservers you specify must resolve {% data variables.product.product_location %}'s hostname.
diff --git a/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md b/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md
index ee2ff7cadc..356537a452 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/ru-RU/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index b5bae497ec..4ca368d978 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### Enabling public sites for {% data variables.product.prodname_pages %}
diff --git a/translations/ru-RU/content/admin/configuration/configuring-rate-limits.md b/translations/ru-RU/content/admin/configuration/configuring-rate-limits.md
index 2ee7b09ef2..b4f780f806 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### Enabling rate limits for {% data variables.product.prodname_enterprise_api %}
diff --git a/translations/ru-RU/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/ru-RU/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index bad85c20c7..9a8fa10e3f 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/admin/configuration/configuring-time-synchronization.md b/translations/ru-RU/content/admin/configuration/configuring-time-synchronization.md
index 9e0a76a6df..b7eeb18700 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### Changing the default NTP servers
diff --git a/translations/ru-RU/content/admin/configuration/configuring-tls.md b/translations/ru-RU/content/admin/configuration/configuring-tls.md
index 3fef22f08e..9dabe29b8d 100644
--- a/translations/ru-RU/content/admin/configuration/configuring-tls.md
+++ b/translations/ru-RU/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### About Transport Layer Security
diff --git a/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 8e50c323ba..ce2f883761 100644
--- a/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/ru-RU/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### About {% data variables.product.prodname_github_connect %}
diff --git a/translations/ru-RU/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/ru-RU/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index ae9cdeaf7c..7a097e1ba5 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}
diff --git a/translations/ru-RU/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/ru-RU/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index 4bc825c5a0..a9d163635d 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### About maintenance mode
diff --git a/translations/ru-RU/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ru-RU/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 57fdd9606f..ba37060cfd 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### About license synchronization
diff --git a/translations/ru-RU/content/admin/configuration/enabling-private-mode.md b/translations/ru-RU/content/admin/configuration/enabling-private-mode.md
index 02ee4c2b05..41af99eb4a 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-private-mode.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 You must enable private mode if {% data variables.product.product_location %} is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over `git://`. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "[Using built-in authentication](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)."
diff --git a/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md b/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md
index c095cdc14f..d78c8a1d33 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### About subdomain isolation
@@ -19,7 +24,7 @@ When subdomain isolation is enabled, {% data variables.product.prodname_ghe_serv
 
 {% if currentVersion == "enterprise-server@2.22" %}
 To use Docker with
-{% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)."
+{% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/ru-RU/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/ru-RU/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index c638609ec9..92e0978d90 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 As a site administrator, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.prodname_ghe_server %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph.
diff --git a/translations/ru-RU/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/ru-RU/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 844e689a1e..3759f6efcc 100644
--- a/translations/ru-RU/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/ru-RU/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location_enterprise %}.
diff --git a/translations/ru-RU/content/admin/configuration/index.md b/translations/ru-RU/content/admin/configuration/index.md
index 52861ec7d8..1be14baeb9 100644
--- a/translations/ru-RU/content/admin/configuration/index.md
+++ b/translations/ru-RU/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/ru-RU/content/admin/configuration/initializing-github-ae.md b/translations/ru-RU/content/admin/configuration/initializing-github-ae.md
index 6a1cf39cea..fbf67d1d8d 100644
--- a/translations/ru-RU/content/admin/configuration/initializing-github-ae.md
+++ b/translations/ru-RU/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: Initializing GitHub AE
 intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### About initialization
@@ -79,11 +82,11 @@ Once this is initialized, you can reconfigure any settings after the initializat
 1. To the right of "Configure email settings", click **Configure**. !["Configure" button for email settings configuration](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Complete your email server settings:
-  - In the **Server address** field, type the address of your SMTP server.
-  - In the **Port** field, type the port that your SMTP server uses to send email.
-  - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
-  - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
-  - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
+    - In the **Server address** field, type the address of your SMTP server.
+    - In the **Port** field, type the port that your SMTP server uses to send email.
+    - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+    - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
+    - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
 
 4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. Click **Test email settings**. !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 2358f1b0ab..2b7850d503 100644
--- a/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: 'You can decide whether authenticated users can connect to {% data variab
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ru-RU/content/admin/configuration/network-ports.md b/translations/ru-RU/content/admin/configuration/network-ports.md
index 046ecb5f92..8091bc7b4d 100644
--- a/translations/ru-RU/content/admin/configuration/network-ports.md
+++ b/translations/ru-RU/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### Administrative ports
diff --git a/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index 98e7414d45..bdf3f30676 100644
--- a/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -1,9 +1,16 @@
 ---
 title: Restricting network traffic to your enterprise
 shortTitle: Restricting network traffic
-intro: 'You can use an IP allow list to restrict access to your enterprise to connections from specified IP addresses.'
+intro: You can use an IP allow list to restrict access to your enterprise to connections from specified IP addresses.
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### About IP allow lists
diff --git a/translations/ru-RU/content/admin/configuration/site-admin-dashboard.md b/translations/ru-RU/content/admin/configuration/site-admin-dashboard.md
index 18d3629d25..1c9d13c22f 100644
--- a/translations/ru-RU/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/ru-RU/content/admin/configuration/site-admin-dashboard.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 To access the dashboard, in the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}. ![Rocket ship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/ru-RU/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/ru-RU/content/admin/configuration/troubleshooting-ssl-errors.md
index f84c128894..dfb33ad5d2 100644
--- a/translations/ru-RU/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/ru-RU/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### Removing the passphrase from your key file
diff --git a/translations/ru-RU/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/ru-RU/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index 34c481736d..51a81c3e7f 100644
--- a/translations/ru-RU/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/ru-RU/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/ru-RU/content/admin/configuration/validating-your-domain-settings.md b/translations/ru-RU/content/admin/configuration/validating-your-domain-settings.md
index aef34f5c0b..25a765f31e 100644
--- a/translations/ru-RU/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/ru-RU/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/ru-RU/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/ru-RU/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/ru-RU/content/admin/enterprise-management/about-cluster-nodes.md b/translations/ru-RU/content/admin/enterprise-management/about-cluster-nodes.md
index e4377f1f12..11f5886486 100644
--- a/translations/ru-RU/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/ru-RU/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/enterprise-management/about-clustering.md b/translations/ru-RU/content/admin/enterprise-management/about-clustering.md
index 6e92726533..b586ce8fb6 100644
--- a/translations/ru-RU/content/admin/enterprise-management/about-clustering.md
+++ b/translations/ru-RU/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/enterprise-management/about-geo-replication.md b/translations/ru-RU/content/admin/enterprise-management/about-geo-replication.md
index 32c26179a1..bf0465660b 100644
--- a/translations/ru-RU/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/ru-RU/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London.
diff --git a/translations/ru-RU/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/ru-RU/content/admin/enterprise-management/about-high-availability-configuration.md
index 7697f958e5..7729065960 100644
--- a/translations/ru-RU/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/ru-RU/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 When you configure high availability, there is an automated setup of one-way, asynchronous replication of all datastores (Git repositories, MySQL, Redis, and Elasticsearch) from the primary to the replica appliance.
diff --git a/translations/ru-RU/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/ru-RU/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 59af4f4dab..aa002a29e2 100644
--- a/translations/ru-RU/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/ru-RU/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Accessing the monitor dashboard
diff --git a/translations/ru-RU/content/admin/enterprise-management/cluster-network-configuration.md b/translations/ru-RU/content/admin/enterprise-management/cluster-network-configuration.md
index ee5ee60921..750db85161 100644
--- a/translations/ru-RU/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/ru-RU/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### Network considerations
diff --git a/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md b/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md
index 0a03ff98f7..4bbaaa9793 100644
--- a/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/ru-RU/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Set up an external `collectd` server
diff --git a/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index e29b83cae9..93bd033761 100644
--- a/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/ru-RU/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About high availability replication for clusters
@@ -22,7 +26,7 @@ We recommend configuring high availability as a part of a comprehensive disaster
 
 #### Hardware and software
 
-For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 64 GB of RAM, and 750 GB of attached storage.
+For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage.
 
 On each new virtual machine, install the same version of {% data variables.product.prodname_ghe_server %} that runs on the nodes in your active cluster. You don't need to upload a license or perform any additional configuration. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)."
 
diff --git a/translations/ru-RU/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/ru-RU/content/admin/enterprise-management/creating-a-high-availability-replica.md
index 78b2d39667..35ebe120d9 100644
--- a/translations/ru-RU/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/ru-RU/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/ru-RU/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/ru-RU/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index c46ad6951e..856f83ac28 100644
--- a/translations/ru-RU/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/ru-RU/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### Failure scenarios
diff --git a/translations/ru-RU/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/ru-RU/content/admin/enterprise-management/enabling-automatic-update-checks.md
index 3e6a0cd329..14c7501dda 100644
--- a/translations/ru-RU/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/ru-RU/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 When an upgrade package is automatically downloaded for {% data variables.product.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.product.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)."
diff --git a/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md
index b740c95ae4..81f8691a6c 100644
--- a/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/ru-RU/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/ru-RU/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index 03746bec39..a6fc068013 100644
--- a/translations/ru-RU/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/ru-RU/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/ru-RU/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/ru-RU/content/admin/enterprise-management/increasing-storage-capacity.md
index 928fc04b9f..c5b3f1b139 100644
--- a/translations/ru-RU/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/ru-RU/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -31,7 +35,10 @@ As more users join {% data variables.product.product_location %}, you may need t
 1. Resize the existing user volume disk using your virtualization platform's tools.
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
-4. Reboot the appliance to detect the new storage allocation.
+4. Reboot the appliance to detect the new storage allocation:
+  ```shell
+  $ sudo reboot
+  ```
 5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ As more users join {% data variables.product.product_location %}, you may need t
 ### Increasing the root partition size using a new appliance
 
 1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
-2. Shut down the current appliance.
+2. Shut down the current appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 3. Detach the data disk from the current appliance using your virtualization platform's tools.
 4. Attach the data disk to the new appliance with the larger root disk.
 
@@ -57,6 +67,9 @@ As more users join {% data variables.product.product_location %}, you may need t
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. Shut down the appliance.
+4. Shut down the appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 5. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
 6. Start the appliance.
diff --git a/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md b/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md
index bd7db2d848..d26a1e9c72 100644
--- a/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/ru-RU/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index cf2c0ba576..a55b1beeca 100644
--- a/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 The time required to failover depends on how long it takes to manually promote the replica and redirect traffic. The average time ranges between 2-10 minutes.
diff --git a/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index 334ad1fc48..b0d1e87c36 100644
--- a/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### About failover to your replica cluster
diff --git a/translations/ru-RU/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/ru-RU/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index 194e1c4f37..f0597246e3 100644
--- a/translations/ru-RU/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/ru-RU/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -12,8 +12,11 @@ redirect_from:
 intro: 'To migrate from {% data variables.product.prodname_enterprise %} 11.10.x to 2.1.23, you''ll need to set up a new appliance instance and migrate data from the previous instance.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 Migrations from {% data variables.product.prodname_enterprise %} 11.10.348 and later are supported. Migrating from {% data variables.product.prodname_enterprise %} 11.10.348 and earlier is not supported. You must first upgrade to 11.10.348 in several upgrades. For more information, see the 11.10.348 upgrading procedure, "[Upgrading to the latest release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)."
diff --git a/translations/ru-RU/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/ru-RU/content/admin/enterprise-management/monitoring-cluster-nodes.md
index 25a24f54a9..f05354b4e3 100644
--- a/translations/ru-RU/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/ru-RU/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -6,8 +6,14 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### Manually checking cluster status
diff --git a/translations/ru-RU/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/ru-RU/content/admin/enterprise-management/monitoring-using-snmp.md
index c47fd6f241..7dc44b7249 100644
--- a/translations/ru-RU/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/ru-RU/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP is a common standard for monitoring devices over a network. We strongly recommend enabling SNMP so you can monitor the health of {% data variables.product.product_location %} and know when to add more memory, storage, or processor power to the host machine.
diff --git a/translations/ru-RU/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/ru-RU/content/admin/enterprise-management/recommended-alert-thresholds.md
index bf8d0bf97e..4d15a0d436 100644
--- a/translations/ru-RU/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/ru-RU/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### Monitoring storage
diff --git a/translations/ru-RU/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/ru-RU/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index 7424886651..fa0fef37f5 100644
--- a/translations/ru-RU/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/ru-RU/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 You can use the former primary appliance as the new replica appliance if the failover was planned or was not related to the health of the appliance. If the failover was related to an issue with the primary appliance, you may prefer to create a new replica appliance. For more information, see "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)."
diff --git a/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md
index 6bd2642b8d..f41c196815 100644
--- a/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/ru-RU/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### Stopping replication temporarily
diff --git a/translations/ru-RU/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/ru-RU/content/admin/enterprise-management/replacing-a-cluster-node.md
index d543180faf..749940e87b 100644
--- a/translations/ru-RU/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/ru-RU/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/ru-RU/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/ru-RU/content/admin/enterprise-management/setting-up-external-monitoring.md
index 7862e96eb2..b7d128e601 100644
--- a/translations/ru-RU/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/ru-RU/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### About SNMP
diff --git a/translations/ru-RU/content/admin/enterprise-management/upgrade-requirements.md b/translations/ru-RU/content/admin/enterprise-management/upgrade-requirements.md
index 3ae0cf4673..01e247a0cf 100644
--- a/translations/ru-RU/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/ru-RU/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration.
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### Дальнейшие шаги
+
 After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)."
diff --git a/translations/ru-RU/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/ru-RU/content/admin/enterprise-management/upgrading-a-cluster.md
index 31b92b012f..28275b87ac 100644
--- a/translations/ru-RU/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/ru-RU/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### Upgrading with a hotpatch
diff --git a/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index 54be56a96c..5c97a4adc6 100644
--- a/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### Preparing to upgrade
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
-
-Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
-
-Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
-
-| User licenses                  |                           vCPUs |                                  Memory |                        Attached storage | Root storage |
-|:------------------------------ | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
-| Trial, demo, or 10 light users |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
-| 10 to 3,000                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
-| 3,000 to 5000                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
-| 5,000 to 8000                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
-| 8,000 to 10,000+               | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### Taking a snapshot
 
@@ -81,7 +59,7 @@ There are two types of snapshots:
 | Hyper-V               | VM              | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | Disk            | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM              | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM              | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM              | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### Upgrading with a hotpatch
 
@@ -89,7 +67,12 @@ There are two types of snapshots:
 
 {% note %}
 
-**Note**: Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}Notes{% else %}Note{% endif %}**:
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+
+- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
 
 {% endnote %}
 
diff --git a/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md
index c1a0507898..b7b14520cf 100644
--- a/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/ru-RU/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index 81540a8ec3..998b85f087 100644
--- a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index 7006750314..dc252de3cc 100644
--- a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/ru-RU/content/admin/enterprise-support/about-support-for-advanced-security.md
index af3ce85362..581b99a1ac 100644
--- a/translations/ru-RU/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/ru-RU/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/ru-RU/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index 9e623b4ae3..93f1ba297d 100644
--- a/translations/ru-RU/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/ru-RU/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 Before submitting a ticket, you should:
diff --git a/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md
index b889f2f284..9a4445327f 100644
--- a/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/ru-RU/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Creating and sharing diagnostic files
diff --git a/translations/ru-RU/content/admin/enterprise-support/reaching-github-support.md b/translations/ru-RU/content/admin/enterprise-support/reaching-github-support.md
index d7db706199..56159b2a01 100644
--- a/translations/ru-RU/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/ru-RU/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### Using automated ticketing systems
diff --git a/translations/ru-RU/content/admin/enterprise-support/submitting-a-ticket.md b/translations/ru-RU/content/admin/enterprise-support/submitting-a-ticket.md
index 8b572395cc..345f6fdb4b 100644
--- a/translations/ru-RU/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/ru-RU/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### About submitting a ticket
diff --git a/translations/ru-RU/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/ru-RU/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..341f73ba73
--- /dev/null
+++ b/translations/ru-RU/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: About using actions in your enterprise
+intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community.
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### Official actions bundled with your enterprise instance
+
+Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}.
+
+The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: <code>https://<em>HOSTNAME</em>/actions</code>.
+
+Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)."
+
+{% note %}
+
+**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)."
+
+{% endnote %}
+
+### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
+
+If users in your enterprise need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options.
+
+The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% data reusables.actions.enterprise-limit-actions-use %}
+
+Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)."
diff --git a/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 782191e0e5..9afbe3c827 100644
--- a/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/ru-RU/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: Backing up and restoring
 intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index dfa03f3d04..a0856b2242 100644
--- a/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/ru-RU/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: Enabling automatic access to GitHub.com actions using GitHub Connect
-intro: 'To allow {% data variables.product.prodname_actions %} on your enterprise instance to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %}.'
+intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)."
+To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
 
-Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location_enterprise %}, you must connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index f9b19f11ea..25e57f96c5 100644
--- a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 
-* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index b4e55812cf..a516f50033 100644
--- a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
 
 * To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}.
-* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 9a35874248..48959da8e5 100644
--- a/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index ef72ddb56e..6a5f4f4296 100644
--- a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: Getting started with GitHub Actions for GitHub AE
+shortTitle: Getting started with GitHub Actions
 intro: 'Learn configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index 4adfc8b23a..73815d8bb8 100644
--- a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,5 +1,6 @@
 ---
 title: Getting started with GitHub Actions for GitHub Enterprise Server
+shortTitle: Getting started with GitHub Actions
 intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 redirect_from:
@@ -7,7 +8,9 @@ redirect_from:
   - /admin/github-actions/enabling-github-actions-and-configuring-storage
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
+  - Actions
   - Enterprise
 ---
 
@@ -116,7 +119,7 @@ To run {% data variables.product.prodname_actions %} workflows, you need to add
 
 You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}.
 
-For more information, see "[About using actions on {% data variables.product.prodname_ghe_server %}](/admin/github-actions/about-using-actions-on-github-enterprise-server)."
+For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
 
 ### General security hardening for {% data variables.product.prodname_actions %}
 
diff --git a/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md b/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md
index a1c649316c..1634f9088d 100644
--- a/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/ru-RU/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: High availability for GitHub Actions
 intro: 'There are some special considerations for administering {% data variables.product.prodname_actions %} in a high availability configuration.'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### Replication or redundancy of your {% data variables.product.prodname_actions %} data
diff --git a/translations/ru-RU/content/admin/github-actions/index.md b/translations/ru-RU/content/admin/github-actions/index.md
index 3e40fcb92e..e0ef0b3895 100644
--- a/translations/ru-RU/content/admin/github-actions/index.md
+++ b/translations/ru-RU/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index 36f128356c..d118cd96fd 100644
--- a/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/ru-RU/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: Manually syncing actions from GitHub.com
-intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your {% data variables.product.prodname_ghe_server %} instance.'
+intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
+The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)".
 
-However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance.
+However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise.
 
 ### About the `actions-sync` tool
 
-The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API. The machine doesn't need to be connected to both at the same time.
+The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time.
 
 If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands.
 
@@ -29,8 +30,8 @@ The `actions-sync` tool can only download actions from {% data variables.product
 
 ### Требования
 
-* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
-* You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
 * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
 
   {% note %}
@@ -51,7 +52,7 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
 
 {% note %}
 
-**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
+**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
    * `--destination-url`: The URL of the destination enterprise instance.
    * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`.
 
-     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination {% data variables.product.prodname_ghe_server %} instance. You must create the organization named `synced-actions` on your enterprise instance before running the above command.
-     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise instance. Before running the command, you must create a new organization on your instance that matches the owner name of the action. Consider using a central organization to store the synced actions on your instance, as this means you will not need to  create multiple new organizations if you sync actions from different owners.
+     * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command.
+     * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners.
      * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync).
-1. After the action repository is created on your enterprise instance, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
+1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above:
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 017c7ba607..01e6cc3ed3 100644
--- a/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### About the included setup actions and the runner tool cache
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}. However, self-hosted runners without internet access  will require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
+Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.product_name %}. However, self-hosted runners without internet access require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`.
 
 The `actions/setup-LANGUAGE` actions normally need internet access to download the required environment binaries into the runner's tool cache. Self-hosted runners without internet access can't download the binaries, so you must manually populate the tool cache on the runner.
 
diff --git a/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md b/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md
index b019a706df..d81c5148e0 100644
--- a/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/ru-RU/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: Using a staging environment
 intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging environments.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 It can be useful to have a staging or testing environment for {% data variables.product.product_location %}, so that you can test updates or new features before implementing them in your production environment.
diff --git a/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 3e0191625c..7b4ac5110c 100644
--- a/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
 title: Using the latest version of the official bundled actions
-intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)."
 
-These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
+These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections.
 
-Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
+### Using `actions-sync` to update the bundled actions
 
-- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
-- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
+To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
 
-These options are described in more detail in the following sections.
+### Using {% data variables.product.prodname_github_connect %} to access the latest actions
 
-### Using actions-sync to update a bundled action
+You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
 
-To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
+Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}:
 
-### Using actions from {% data variables.product.prodname_dotcom_the_website %}
+1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." Например:
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
-
-### Using the latest version by removing the specific action's tag
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
-
-For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
-
-1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
-1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
-
-When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)."
+1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)."
+1. Configure your workflow's YAML to use `actions/checkout@v2`.
+1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/ru-RU/content/admin/guides.md b/translations/ru-RU/content/admin/guides.md
new file mode 100644
index 0000000000..9fc42a4a26
--- /dev/null
+++ b/translations/ru-RU/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: GitHub Enterprise guides
+shortTitle: Руководства
+intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/ru-RU/content/admin/index.md b/translations/ru-RU/content/admin/index.md
index 6928e31fc4..2c141854a9 100644
--- a/translations/ru-RU/content/admin/index.md
+++ b/translations/ru-RU/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: Enterprise Administrators
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
-intro: Documentation and guides for enterprise administrators, system administrators, and security specialists who {% if enterpriseServerVersions contains currentVersion %}deploy, {% endif %}configure{% if enterpriseServerVersions contains currentVersion %},{% endif %} and manage {% data variables.product.product_name %}.
+title: GitHub Enterprise Documentation
+shortTitle: GitHub Enterprise
+intro: 'Documentation and guides for enterprise administrators, system administrators, and security specialists who {% if enterpriseServerVersions contains currentVersion %}deploy, {% endif %}configure{% if enterpriseServerVersions contains currentVersion %},{% endif %} and manage {% data variables.product.product_name %}.'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/ru-RU/content/admin/installation/index.md b/translations/ru-RU/content/admin/installation/index.md
index 514ae4464e..74e8ed3453 100644
--- a/translations/ru-RU/content/admin/installation/index.md
+++ b/translations/ru-RU/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md b/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md
index 326b73bf8b..9f8ad4d3b2 100644
--- a/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/ru-RU/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/ru-RU/content/admin/overview/about-data-residency.md b/translations/ru-RU/content/admin/overview/about-data-residency.md
index a83066177e..08df5703dc 100644
--- a/translations/ru-RU/content/admin/overview/about-data-residency.md
+++ b/translations/ru-RU/content/admin/overview/about-data-residency.md
@@ -1,8 +1,12 @@
 ---
 title: About data residency
-intro: You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.
+intro: 'You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %} You can choose the geography where you store all the customer data for {% data variables.product.product_location %}, and members of your enterprise can access {% data variables.product.product_name %} from anywhere in the world.
diff --git a/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md b/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md
index fdaf0e4c8b..68a101ab35 100644
--- a/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md
@@ -7,8 +7,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
+type: overview
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### About enterprise accounts on {% data variables.product.product_name %}
diff --git a/translations/ru-RU/content/admin/overview/about-github-ae.md b/translations/ru-RU/content/admin/overview/about-github-ae.md
index 6803cd9110..bd6e01d112 100644
--- a/translations/ru-RU/content/admin/overview/about-github-ae.md
+++ b/translations/ru-RU/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: About GitHub AE
 intro: '{% data variables.product.prodname_ghe_managed %} is a security-enhanced and compliant way to use {% data variables.product.prodname_dotcom %} in the cloud.'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### About {% data variables.product.prodname_ghe_managed %}
@@ -21,7 +25,7 @@ All of your data is stored within the geographic region of your choosing. You ca
 
 ### Encryption on your terms
 
-All customer data is encrypted at rest, and you can provide your own encryption key to encrypt your data under your encryption policies. You control your key and access to all of your data. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
+All customer data is encrypted at rest. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
 
 ### Isolated accounts
 
diff --git a/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md
index 5cfe7898e0..cd1e629cdb 100644
--- a/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,8 +5,10 @@ intro: '{% if currentVersion == "github-ae@latest" %}Your {% data variables.prod
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
diff --git a/translations/ru-RU/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/ru-RU/content/admin/overview/managing-billing-for-your-enterprise.md
index 98ff0564b7..4961229504 100644
--- a/translations/ru-RU/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ For example, here are the costs for users with licenses on different dates.
 | User      | License dates                                           | Counted days | Cost   |
 | --------- | ------------------------------------------------------- | ------------ | ------ |
 | @octocat  | January 1 - January 31                                  | 31           | $39    |
-| @robocat  | February 1 - February 28                                | 29           | $35.23 |
+| @robocat  | February 1 - February 28                                | 28           | $35.23 |
 | @devtocat | January 15 - January 31                                 | 17           | $21.39 |
 | @doctocat | January 1 - January 15                                  | 31           | $39    |
 | @prodocat | January 7 - January 15                                  | 25           | $31.45 |
 | @monalisa | January 1 - January 7,<br>January 15 - January 31 | 31           | $39    |
 
-Your enterprise can include one or more instances. {% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
+{% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
 
 You can see your current usage in your [Azure account portal](https://portal.azure.com).
 
diff --git a/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md b/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md
index 3624945526..acacb52654 100644
--- a/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/ru-RU/content/admin/overview/managing-your-github-enterprise-license.md
@@ -56,7 +56,7 @@ If you'd like to renew or add user licenses to {% data variables.product.prodnam
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
 3. In the left sidebar, click **Enterprise licensing**. !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-4. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.
+4. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses. {% if currentVersion ver_gt "enterprise-server@3.0" %}If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
 
 ### Automatically syncing user license usage with {% data variables.product.prodname_ghe_cloud %}
 
diff --git a/translations/ru-RU/content/admin/overview/system-overview.md b/translations/ru-RU/content/admin/overview/system-overview.md
index d7d9ba2f86..5820780a01 100644
--- a/translations/ru-RU/content/admin/overview/system-overview.md
+++ b/translations/ru-RU/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### Storage architecture
diff --git a/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index d4c9ab71e5..a18408b06f 100644
--- a/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 398ccc528c..ca1bd427f3 100644
--- a/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: Getting started with GitHub Packages for your enterprise
+shortTitle: Getting started with GitHub Packages
 intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index 043cd4a455..618762545f 100644
--- a/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/ru-RU/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: Quickstart for configuring your MinIO storage bucket for GitHub Packages
 intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/ru-RU/content/admin/policies/about-pre-receive-hooks.md b/translations/ru-RU/content/admin/policies/about-pre-receive-hooks.md
index 11fda56c85..73ed0a1805 100644
--- a/translations/ru-RU/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/ru-RU/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 When a push occurs, each script runs in an isolated environment and can perform checks on the content of the push. The scripts will cause the push to be accepted if the exit status is 0, or rejected if the exit status is non-zero.
diff --git a/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-environment.md
index 333e9518bd..e48153dcf2 100644
--- a/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 A pre-receive environment for {% data variables.product.prodname_ghe_server %} is a Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot) environment. Because pre-receive hooks execute on every push event, they should be fast and lightweight. The environment needed for such checks will typically be minimal.
diff --git a/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md
index 33c0065777..224372efb6 100644
--- a/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/ru-RU/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 You can see examples of pre-receive hooks for {% data variables.product.prodname_ghe_server %} in the [`github/platform-samples` repository](https://github.com/github/platform-samples/tree/master/pre-receive-hooks).
diff --git a/translations/ru-RU/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/ru-RU/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index 381b03d1bd..afd8481d88 100644
--- a/translations/ru-RU/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/ru-RU/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,6 +5,13 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### About {% data variables.product.prodname_GH_advanced_security %}
diff --git a/translations/ru-RU/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ru-RU/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 15f6a28ef4..3a996c08b5 100644
--- a/translations/ru-RU/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ru-RU/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### Configuring the default visibility of new repositories in your enterprise
diff --git a/translations/ru-RU/content/admin/policies/index.md b/translations/ru-RU/content/admin/policies/index.md
index cdc0668700..d5d9bedc36 100644
--- a/translations/ru-RU/content/admin/policies/index.md
+++ b/translations/ru-RU/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/ru-RU/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/ru-RU/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 4f55f53348..340f5a015d 100644
--- a/translations/ru-RU/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/ru-RU/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### Creating pre-receive hooks
diff --git a/translations/ru-RU/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/ru-RU/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..03b083ea40
--- /dev/null
+++ b/translations/ru-RU/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About email restrictions for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restricting email notifications for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/ru-RU/content/admin/release-notes.md b/translations/ru-RU/content/admin/release-notes.md
index 1af66701b5..7dfc63a71c 100644
--- a/translations/ru-RU/content/admin/release-notes.md
+++ b/translations/ru-RU/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/ru-RU/content/admin/user-management/about-migrations.md b/translations/ru-RU/content/admin/user-management/about-migrations.md
index a5692e645d..e885b6c140 100644
--- a/translations/ru-RU/content/admin/user-management/about-migrations.md
+++ b/translations/ru-RU/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Types of migrations
diff --git a/translations/ru-RU/content/admin/user-management/adding-people-to-teams.md b/translations/ru-RU/content/admin/user-management/adding-people-to-teams.md
index 6ddc24d377..522d39f391 100644
--- a/translations/ru-RU/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/ru-RU/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: 'Once a team has been created, organization admins can add users from {% data variables.product.product_location %} to the team and determine which repositories they have access to.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization).
diff --git a/translations/ru-RU/content/admin/user-management/audit-logging.md b/translations/ru-RU/content/admin/user-management/audit-logging.md
index c9d7347644..aaf7b47f33 100644
--- a/translations/ru-RU/content/admin/user-management/audit-logging.md
+++ b/translations/ru-RU/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 For a full list, see "[Audited actions](/admin/user-management/audited-actions)." For more information on finding a particular action, see "[Searching the audit log](/admin/user-management/searching-the-audit-log)."
diff --git a/translations/ru-RU/content/admin/user-management/audited-actions.md b/translations/ru-RU/content/admin/user-management/audited-actions.md
index 61e693d543..20b8803474 100644
--- a/translations/ru-RU/content/admin/user-management/audited-actions.md
+++ b/translations/ru-RU/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### Authentication
diff --git a/translations/ru-RU/content/admin/user-management/auditing-ssh-keys.md b/translations/ru-RU/content/admin/user-management/auditing-ssh-keys.md
index b53e4577ea..f3156f9022 100644
--- a/translations/ru-RU/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/ru-RU/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 Once initiated, the audit disables all existing SSH keys and forces users to approve or reject them before they're able to clone, pull, or push to any repositories. An audit is useful in situations where an employee or contractor leaves the company and you need to ensure that all keys are verified.
diff --git a/translations/ru-RU/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/ru-RU/content/admin/user-management/auditing-users-across-your-enterprise.md
index 08c06c3ad4..bfe8fe628a 100644
--- a/translations/ru-RU/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### Accessing the audit log
diff --git a/translations/ru-RU/content/admin/user-management/best-practices-for-user-security.md b/translations/ru-RU/content/admin/user-management/best-practices-for-user-security.md
index 85382758ff..e814bc4358 100644
--- a/translations/ru-RU/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/ru-RU/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ru-RU/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/ru-RU/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index b5e66ca265..ba073ccc59 100644
--- a/translations/ru-RU/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### About {% data variables.large_files.product_name_long %}
diff --git a/translations/ru-RU/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/ru-RU/content/admin/user-management/configuring-visibility-for-organization-membership.md
index 99f5fde542..c12145465b 100644
--- a/translations/ru-RU/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/ru-RU/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/ru-RU/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/ru-RU/content/admin/user-management/continuous-integration-using-jenkins.md
index 9d2dca9471..3f567ef617 100644
--- a/translations/ru-RU/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/ru-RU/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/user-management/creating-teams.md b/translations/ru-RU/content/admin/user-management/creating-teams.md
index 94b48684f0..6d469b1a5a 100644
--- a/translations/ru-RU/content/admin/user-management/creating-teams.md
+++ b/translations/ru-RU/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 Teams are central to many of {% data variables.product.prodname_dotcom %}'s collaborative features, such as team @mentions to notify appropriate parties that you'd like to request their input or attention. For more information, see "[Permission levels for an organization repository](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)".
diff --git a/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index b81f86865b..582fed951f 100644
--- a/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: Customizing user messages for your enterprise
+shortTitle: Customizing user messages
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: 'You can create custom messages that users will see on {% data variables.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### About user messages
diff --git a/translations/ru-RU/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/ru-RU/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index 4562fc05e9..8e54fbd585 100644
--- a/translations/ru-RU/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: You can prevent people from using Git over SSH for certain or all reposit
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### Disabling Git SSH access to a specific repository
diff --git a/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md
index b1463aa91b..b3c850efce 100644
--- a/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the source organization on {% data variables.product.prodname_dotcom %}
diff --git a/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index aef125ce7d..f0b975c6e6 100644
--- a/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the {% data variables.product.prodname_ghe_server %} source instance
diff --git a/translations/ru-RU/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/ru-RU/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index f1f43c4703..4f752b7057 100644
--- a/translations/ru-RU/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/ru-RU/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Importing projects from Mercurial
diff --git a/translations/ru-RU/content/admin/user-management/log-forwarding.md b/translations/ru-RU/content/admin/user-management/log-forwarding.md
index 96a7b3edd9..d4a15debdd 100644
--- a/translations/ru-RU/content/admin/user-management/log-forwarding.md
+++ b/translations/ru-RU/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 Any log collection system that supports syslog-style log streams is supported (e.g., [Logstash](http://logstash.net/) and [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
diff --git a/translations/ru-RU/content/admin/user-management/managing-dormant-users.md b/translations/ru-RU/content/admin/user-management/managing-dormant-users.md
index 03e776d889..ac9bc21f66 100644
--- a/translations/ru-RU/content/admin/user-management/managing-dormant-users.md
+++ b/translations/ru-RU/content/admin/user-management/managing-dormant-users.md
@@ -9,8 +9,11 @@ intro: 'A user account is considered to be dormant if it has not been active for
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 "Activity" includes, but is not limited to:
diff --git a/translations/ru-RU/content/admin/user-management/managing-global-webhooks.md b/translations/ru-RU/content/admin/user-management/managing-global-webhooks.md
index 64ee497612..7f6e78cb30 100644
--- a/translations/ru-RU/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/ru-RU/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### About global webhooks
diff --git a/translations/ru-RU/content/admin/user-management/managing-projects-using-jira.md b/translations/ru-RU/content/admin/user-management/managing-projects-using-jira.md
index e953a14d21..c992dfa998 100644
--- a/translations/ru-RU/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/ru-RU/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: Managing projects using JIRA
-intro: 'You can integrate JIRA with {% data variables.product.prodname_enterprise %} for project management.'
+title: Managing projects using Jira
+intro: 'You can integrate Jira with {% data variables.product.prodname_enterprise %} for project management.'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### Connecting JIRA to a {% data variables.product.prodname_enterprise %} organization
+### Connecting Jira to a {% data variables.product.prodname_enterprise %} organization
 
-1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login.
-1. In the upper right corner of any page, click the account settings (gear) icon.
-1. In the left sidebar, click the name of your organization.
-1. In the left sidebar, click **Applications**.
-1. In the upper right corner of the **Organization applications** box, click **Register new application**.
-1. Fill in the application settings:
-    - In the **Application name** field, type "JIRA".
-    - In the **Homepage URL** field, type the full URL of your JIRA instance.
-    - In the **Authorization callback URL** field, type the full URL of your JIRA instance.
-1. Click **Register application**.
-1. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your JIRA instance.
+1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
+2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira.
 
-### JIRA instance configuration
+  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. On your JIRA instance, log into an account with administrative access.
-1. At the top of the page, click the settings (gear) icon.
-1. In the settings dropdown, choose **Add-ons**.
-1. In the left sidebar, under **Source control**, click **DVCS accounts**.
-1. Click **Link Bitbucket or GitHub account**.
-1. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings:
-    - From the **Host** dropdown menu, choose **GitHub Enterprise**.
+3. Click on the **Edit _organization name_ settings** link.
+
+  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
+
+  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Click on the **Register new application** button.
+
+  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. Fill in the application settings:
+    - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance.
+    - In the **Homepage URL** field, type the full URL of your Jira instance.
+    - In the **Authorization callback URL** field, type the full URL of your Jira instance.
+7. Click **Register application**.
+8. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your Jira instance.
+
+### Jira instance configuration
+
+1. On your Jira instance, log into an account with administrative access.
+2. At the top of the page, click the settings (gear) icon and choose **Applications**.
+
+  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
+
+  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
+
+  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings:
+    - From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**.
     - In the **Team or User Account** field, type the name of your {% data variables.product.prodname_enterprise %} organization or personal account.
     - In the **OAuth Key** field, type the Client ID of your {% data variables.product.prodname_enterprise %} developer application.
     - In the **OAuth Secret** field, type the Client Secret for your {% data variables.product.prodname_enterprise %} developer application.
-    - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, unselect **Auto Link New Repositories**.
-    - If you don't want to enable smart commits, unselect **Enable Smart Commits**.
+    - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, deselect **Auto Link New Repositories**.
+    - If you don't want to enable smart commits, deselect **Enable Smart Commits**.
     - Click **Add**.
-1. Review the permissions you are granting to your {% data variables.product.prodname_enterprise %} account and click **Authorize application**.
-1. If necessary, type your password to continue.
+6. Review the permissions you are granting to your {% data variables.product.prodname_enterprise %} account and click **Authorize application**.
+7. If necessary, type your password to continue.
diff --git a/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md
index 11dd573630..7b45f8cd16 100644
--- a/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Applying the imported data on {% data variables.product.prodname_ghe_server %}
diff --git a/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md
index 6af4934433..3bb4621aec 100644
--- a/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/ru-RU/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### About internal repositories
@@ -34,6 +38,12 @@ If you don't have private mode enabled, the migration script will have no effect
 ### Running the migration
 
 1. Connect to the administrative shell. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)."
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. Run the migration command.
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. Navigate to the `/data/github/current` directory.
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ If you don't have private mode enabled, the migration script will have no effect
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 Log output will appear in the terminal and `/tmp/convert_public_ghes_repos_to_internal.log`.
 
diff --git a/translations/ru-RU/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/ru-RU/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index 875847ad67..d4a65aa90b 100644
--- a/translations/ru-RU/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/ru-RU/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 Usually, if someone deletes a repository, it will be available on disk for 90 days and can be restored via the site admin dashboard. After 90 days the repository is purged and deleted forever. If you place a legal hold on a user or organization, repositories they own are available for restore indefinitely.
diff --git a/translations/ru-RU/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/ru-RU/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index bca7ba5532..f5c436f5e4 100644
--- a/translations/ru-RU/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/ru-RU/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
diff --git a/translations/ru-RU/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/ru-RU/content/admin/user-management/preventing-users-from-creating-organizations.md
index ac2412dffc..733793d89b 100644
--- a/translations/ru-RU/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/ru-RU/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: You can prevent users from creating organizations in your enterprise.
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/ru-RU/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/ru-RU/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index a1dd6ec636..c6ffc7095c 100644
--- a/translations/ru-RU/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/ru-RU/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: 'Site administrators can promote any normal user account to a site administrator, as well as demote other site administrators to regular users.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/ru-RU/content/admin/user-management/rebuilding-contributions-data.md b/translations/ru-RU/content/admin/user-management/rebuilding-contributions-data.md
index 5fb410c7c0..9728193fdc 100644
--- a/translations/ru-RU/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/ru-RU/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 Whenever a commit is pushed to {% data variables.product.prodname_enterprise %}, it is linked to a user account if they are both associated with the same email address. However, existing commits are *not* retroactively linked when a user registers a new email address or creates a new account.
diff --git a/translations/ru-RU/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/ru-RU/content/admin/user-management/removing-users-from-teams-and-organizations.md
index 43dc19d077..06605e9e8d 100644
--- a/translations/ru-RU/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/ru-RU/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 Only owners or team admins can remove organization members. When a user is removed from a team or organization, their issues, pull requests, and comments in the organization's repositories remain intact and are still attributed to the user.
diff --git a/translations/ru-RU/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/ru-RU/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index 1f702fd7a3..ad1afe1fd1 100644
--- a/translations/ru-RU/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/ru-RU/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.product.product_location %}. Organization administrators can require members to have two-factor authentication enabled.
diff --git a/translations/ru-RU/content/admin/user-management/searching-the-audit-log.md b/translations/ru-RU/content/admin/user-management/searching-the-audit-log.md
index f88962f71b..94784178fe 100644
--- a/translations/ru-RU/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/ru-RU/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### Search query syntax
diff --git a/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md
index 90e6cfd913..8f998d08e2 100644
--- a/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/ru-RU/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 'If a user leaves or moves to a different part of the company, you should remove or modify their ability to access {% data variables.product.product_location %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 If employees leave the company, you can suspend their {% data variables.product.prodname_ghe_server %} accounts to open up user licenses in your {% data variables.product.prodname_enterprise %} license while preserving the issues, comments, repositories, gists, and other data they created. Suspended users cannot sign into your instance, nor can they push or pull code.
diff --git a/translations/ru-RU/content/admin/user-management/viewing-push-logs.md b/translations/ru-RU/content/admin/user-management/viewing-push-logs.md
index b766ad3b56..43bfa6e547 100644
--- a/translations/ru-RU/content/admin/user-management/viewing-push-logs.md
+++ b/translations/ru-RU/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 Push log entries show:
diff --git a/translations/ru-RU/content/code-security/getting-started/about-securing-your-repository.md b/translations/ru-RU/content/code-security/getting-started/about-securing-your-repository.md
index 0f22c87877..545aaf972a 100644
--- a/translations/ru-RU/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/ru-RU/content/code-security/getting-started/about-securing-your-repository.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### Setting up your repository securely
@@ -22,11 +22,13 @@ The first step to securing a repository is to set up who can see and modify your
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 #### Available for all repositories
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **Security policy**
 
-  Make it easy for people to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)."
+  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 %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **Security advisories**
 
   Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage them to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
diff --git a/translations/ru-RU/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/ru-RU/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..322dfc6c1b
--- /dev/null
+++ b/translations/ru-RU/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+You can create a default security policy for your organization or user account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+{% endif %}
+
+{% tip %}
+
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about {% data variables.product.prodname_security_advisories %}, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+### Adding a security policy to your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**. ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**. ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### Дополнительная литература
+
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/ru-RU/content/code-security/getting-started/index.md b/translations/ru-RU/content/code-security/getting-started/index.md
index 6a546c8391..f50d8252fc 100644
--- a/translations/ru-RU/content/code-security/getting-started/index.md
+++ b/translations/ru-RU/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### Table of Contents
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index 85fb015ac0..b854cc7591 100644
--- a/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -27,13 +27,19 @@ topics:
 
 ### Enabling {% data variables.product.prodname_secret_scanning %} for {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories
 
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization.
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. You may need to enable {% data variables.product.prodname_GH_advanced_security %} to activate the button for "{% data variables.product.prodname_secret_scanning_caps %}". To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% if currentVersion == "free-pro-team@latest" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
 7. To the right of "{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
@@ -66,7 +72,7 @@ You can use a *secret_scanning.yml* file to exclude directories from {% data var
 
     {% endnote %}
 
-You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)."
+You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)."
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/code-security/secret-security/index.md b/translations/ru-RU/content/code-security/secret-security/index.md
index bf316ab2da..af7b99583a 100644
--- a/translations/ru-RU/content/code-security/secret-security/index.md
+++ b/translations/ru-RU/content/code-security/secret-security/index.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### Table of Contents
diff --git a/translations/ru-RU/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/ru-RU/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index ec67221960..b8dfbbf39e 100644
--- a/translations/ru-RU/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/ru-RU/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -9,12 +9,12 @@ versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.secret-scanning.beta %}
 
-### Managing alerts
+### Managing {% data variables.product.prodname_secret_scanning %} alerts
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
@@ -49,3 +49,11 @@ Once a secret has been committed to a repository, you should consider the secret
 
 - For a compromised {% data variables.product.prodname_dotcom %} personal access token, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)."
 - For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.prodname_dotcom %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
diff --git a/translations/ru-RU/content/code-security/secure-coding/about-code-scanning.md b/translations/ru-RU/content/code-security/secure-coding/about-code-scanning.md
index bc0bfaccdd..bb05aaebb7 100644
--- a/translations/ru-RU/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/ru-RU/content/code-security/secure-coding/about-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -36,7 +38,7 @@ You can use {% data variables.product.prodname_code_scanning %} with {% data var
 
 {% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
 
@@ -48,17 +50,14 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 {% endif %}
 
-### About third-party code scanning tools
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### About third-party {% data variables.product.prodname_code_scanning %} tools
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+You can run third-party analysis tools within {% data variables.product.product_name %} using actions or within an external CI system. For more information, see "[Setting up code scanning for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
 
 ### Дополнительная литература
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/translations/ru-RU/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..3a04b180a9
--- /dev/null
+++ b/translations/ru-RU/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using actions. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case.
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Codebases with a compiled language that can be built with a single command or by running a single script.
+
+For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to:
+- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis.
+- Analyze more than one language in a repository.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
diff --git a/translations/ru-RU/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/ru-RU/content/code-security/secure-coding/about-integration-with-code-scanning.md
index 32dd603ca6..786befccd6 100644
--- a/translations/ru-RU/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/ru-RU/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/ru-RU/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/ru-RU/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index f059efe9c0..5d12ce283b 100644
--- a/translations/ru-RU/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/ru-RU/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ru-RU/content/code-security/secure-coding/configuring-code-scanning.md b/translations/ru-RU/content/code-security/secure-coding/configuring-code-scanning.md
index 15d999cb5b..c931b81c11 100644
--- a/translations/ru-RU/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/ru-RU/content/code-security/secure-coding/configuring-code-scanning.md
@@ -14,14 +14,21 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
 ### About {% data variables.product.prodname_code_scanning %} configuration
 
-You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+{%- else %}
+"[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}.
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
 
 Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
 
@@ -143,7 +150,7 @@ jobs:
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
@@ -184,34 +191,66 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. Например:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)."
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
 ### Running additional queries
 
 {% data reusables.code-scanning.run-additional-queries %}
@@ -308,6 +347,7 @@ paths-ignore:
 **Note**:
 
 * The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
 * `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
diff --git a/translations/ru-RU/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/ru-RU/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..4fa1d57d10
--- /dev/null
+++ b/translations/ru-RU/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,203 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configuring CodeQL runner
+intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows.
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively.
+
+To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
+
+### Scanning pull requests
+
+Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code.
+
+To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch.
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`.
+
+{% endnote %}
+
+### Overriding automatic language detection
+
+The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### Running additional queries
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
+
+If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file. If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to <nobr>`--queries`</nobr> with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+
+In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### Using a custom configuration file
+
+Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file.
+
+The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
+
+Use the `--config-file` flag of the `init` command to specify the configuration file. The value of <nobr>`--config-file`</nobr> is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### Example configuration files
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+
+For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+
+For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first.
+
+The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command.
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)."
+
+### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+
+By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
+
+Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository.
+- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+### {% data variables.product.prodname_codeql_runner %} command reference
+
+The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags.
+
+#### `init`
+
+Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
+
+| Flag                             | Required | Input value                                                                                                                                                                         |
+| -------------------------------- |:--------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                   |    ✓     | Name of the repository to initialize.                                                                                                                                               |
+| `--github-url`                   |    ✓     | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                   |
+| `--github-auth`                  |    ✓     | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                               |
+| `--languages`                    |          | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. |
+| `--queries`                      |          | Comma-separated list of additional queries to run, in addition to the default suite of security queries.                                                                            |
+| `--config-file`                  |          | Path to custom configuration file.                                                                                                                                                  |
+| `--codeql-path`                  |          | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy.   |
+| `--temp-dir`                     |          | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                       |
+| `--tools-dir`                    |          | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory.                    |
+| <nobr>`--checkout-path`</nobr> |          | The path to the checkout of your repository. The default is the current working directory.                                                                                          |
+| `--debug`                        |          | None. Prints more verbose output.                                                                                                                                                   |
+| `-h`, `--help`                   |          | None. Displays help for the command.                                                                                                                                                |
+
+#### `autobuild`
+
+Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps.
+
+| Flag                        | Required | Input value                                                                                                                                    |
+| --------------------------- |:--------:| ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--language`                |          | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. |
+| <nobr>`--temp-dir`</nobr> |          | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                  |
+| `--debug`                   |          | None. Prints more verbose output.                                                                                                              |
+| `-h`, `--help`              |          | None. Displays help for the command.                                                                                                           |
+
+#### `analyze`
+
+Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}.
+
+| Flag                               | Required | Input value                                                                                                                                                                                                                                                                                                                         |
+| ---------------------------------- |:--------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     |    ✓     | Name of the repository to analyze.                                                                                                                                                                                                                                                                                                  |
+| `--commit`                         |    ✓     | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                                                                                                                     |
+| `--ref`                            |    ✓     | Name of the reference to analyze, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`.                                                                                              |
+| `--github-url`                     |    ✓     | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                                                                                                                   |
+| `--github-auth`                    |    ✓     | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                                                                                                               |
+| <nobr>`--checkout-path`</nobr>   |          | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                                                                                                          |
+| `--no-upload`                      |          | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}.                                                                                                                                                                                      |
+| `--output-dir`                     |          | Directory where the output SARIF files are stored. The default is in the directory of temporary files.                                                                                                                                                                                                                              |
+| `--ram`                            |          | Amount of memory to use when running queries. The default is to use all available memory.                                                                                                                                                                                                                                           |
+| <nobr>`--no-add-snippets`</nobr> |          | None. Excludes code snippets from the SARIF output. |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |          | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |          | Number of threads to use when running queries. The default is to use all available cores.                                                                                                                                                                                                                                           |
+| `--temp-dir`                       |          | Directory where temporary files are stored. The default is `./codeql-runner`.                                                                                                                                                                                                                                                       |
+| `--debug`                          |          | None. Prints more verbose output.                                                                                                                                                                                                                                                                                                   |
+| `-h`, `--help`                     |          | None. Displays help for the command.                                                                                                                                                                                                                                                                                                |
+
+#### `загрузить`
+
+Uploads SARIF files to {% data variables.product.product_name %}.
+
+{% note %}
+
+**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools.
+
+{% endnote %}
+
+| Flag                             | Required | Input value                                                                                                                                                                                                                                   |
+| -------------------------------- |:--------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   |    ✓     | SARIF file to upload, or a directory containing multiple SARIF files.                                                                                                                                                                         |
+| `--repository`                   |    ✓     | Name of the repository that was analyzed.                                                                                                                                                                                                     |
+| `--commit`                       |    ✓     | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`.                                                                        |
+| `--ref`                          |    ✓     | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
+| `--github-url`                   |    ✓     | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted.                                                                                                                                             |
+| `--github-auth`                  |    ✓     | A {% data variables.product.prodname_github_apps %} token or personal access token.                                                                                                                                                         |
+| <nobr>`--checkout-path`</nobr> |          | The path to the checkout of your repository. The default is the current working directory.                                                                                                                                                    |
+| `--debug`                        |          | None. Prints more verbose output.                                                                                                                                                                                                             |
+| `-h`, `--help`                   |          | None. Displays help for the command.                                                                                                                                                                                                          |
diff --git a/translations/ru-RU/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ru-RU/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index d3a292b276..d1ebef944b 100644
--- a/translations/ru-RU/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ru-RU/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/ru-RU/content/code-security/secure-coding/index.md b/translations/ru-RU/content/code-security/secure-coding/index.md
index f2f148e538..eb40155468 100644
--- a/translations/ru-RU/content/code-security/secure-coding/index.md
+++ b/translations/ru-RU/content/code-security/secure-coding/index.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### Table of Contents
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% topic_link_in_list /using-codeql-code-scanning-with-your-existing-ci-system %}
-    {% link_in_list /running-codeql-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-codeql-code-scanning-in-your-ci-system %}
-    {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/ru-RU/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/ru-RU/content/code-security/secure-coding/integrating-with-code-scanning.md
index 88ab7921b4..cde681b9f8 100644
--- a/translations/ru-RU/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/ru-RU/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index bc07fc34c2..792dc56ce2 100644
--- a/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
 title: Managing code scanning alerts for your repository
 shortTitle: Managing alerts
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About alerts from {% data variables.product.prodname_code_scanning %}
@@ -60,7 +62,7 @@ You need write permission to view a summary of all the alerts for a repository o
 
 Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
 
 Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
 
@@ -70,14 +72,6 @@ Alerts may be fixed in one branch but not in another. You can use the "Branch" d
 ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### Closing an alert
-
-Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### Dismissing or deleting alerts
 
 There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
@@ -101,20 +95,9 @@ When you delete an alert:
 
 To dismiss or delete alerts:
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. Select the **Close** drop-down menu and click a reason for closing the alert.    
-   ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
 
    ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,8 +128,6 @@ To dismiss or delete alerts:
 
 If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
 
-{% endif %}
-
 ### Дополнительная литература
 
 - "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/ru-RU/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/ru-RU/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..e6dc2333a4
--- /dev/null
+++ b/translations/ru-RU/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Running CodeQL CLI in your CI system
+shortTitle: Running CodeQL CLI
+intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About the {% data variables.product.prodname_codeql_cli %}
+
+You can use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_codeql_runner %} in your CI system, or {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% note %}
+
+**Note:** {% if currentVersion == "free-pro-team@latest" %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% endnote %}
+
+### Downloading the {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. Например:
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      Required
+    </th>
+    
+    <th>
+      Использование
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      Required
+    </th>
+    
+    <th>
+      Использование
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. For more information, see "<a href="/code-security/secure-coding/sarif-support-for-code-scanning">SARIF support for {% data variables.product.prodname_code_scanning %}</a>."
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      Option
+    </th>
+    
+    <th align="center">
+      Required
+    </th>
+    
+    <th>
+      Использование
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. For more information, see "<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">Managing security and analysis settings for your repository</a>."
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### Basic example
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### Дополнительная литература
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/ru-RU/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/ru-RU/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index 9238263909..8b8de1d3d3 100644
--- a/translations/ru-RU/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ru-RU/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -13,13 +13,19 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} with a containerized build
 
 If you're setting up {% data variables.product.prodname_code_scanning %} for a compiled language, and you're building the code in a containerized environment, the analysis may fail with the error message "No source code was seen during the build." This indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code as it was compiled.
 
-You must run {% data variables.product.prodname_codeql %} in the same container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. If you're using the {% data variables.product.prodname_codeql_runner %}, run it in the container where your code builds. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% else %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. If you're using {% data variables.product.prodname_actions %}, configure your workflow to run all the actions in the same container. For more information, see "[Example workflow](#example-workflow)."
+{% endif %}
 
 ### Dependencies
 
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/ru-RU/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/ru-RU/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..ad7069e70c
--- /dev/null
+++ b/translations/ru-RU/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Running CodeQL runner in your CI system
+shortTitle: Running CodeQL runner
+intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About the {% data variables.product.prodname_codeql_runner %}
+
+The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. The runner is more complex and less forgiving to set up than the CLI, and is recommended only if you need its capability to analyze multiple compiled languages with a single build, or to integrate with complex build processes. For more information, see "[About CodeQL code scanning in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
+
+{% note %}
+
+**Примечание:**
+{% if currentVersion == "free-pro-team@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+{% else %}
+* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
+{% endif %}
+{% endnote %}
+
+### Downloading the {% data variables.product.prodname_codeql_runner %}
+
+You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+
+On Linux:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+На macOS:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
+
+### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system
+
+Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+In addition to this, each CI server also needs:
+
+- A {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
+
+The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+
+1. Allow the CI servers access to https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
+
+### Calling the {% data variables.product.prodname_codeql_runner %}
+
+You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+
+1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
+1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
+
+For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
+
+You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
+
+To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### Basic example
+
+This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
+
+In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
+
+1. Check out the repository to analyze.
+1. Move into the directory where the repository is checked out.
+1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### Compiled language example
+
+This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
+
+1. Check out the repository to analyze.
+1. Move into the directory where the repository is checked out.
+1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place.
+
+{% endnote %}
+
+### Дополнительная литература
+
+- "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
diff --git a/translations/ru-RU/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/ru-RU/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index cfe9d0050c..e12effe3fb 100644
--- a/translations/ru-RU/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/ru-RU/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: SARIF support for code scanning
 shortTitle: SARIF support
 intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for code scanning. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About SARIF support
@@ -22,7 +25,15 @@ SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https:
 
 To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json).
 
-If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
 
 {% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
@@ -122,6 +133,45 @@ A location within a programming artifact, such as a file in the repository or a
 | `region.endLine`       | **Required.** The line number of the last character in the region.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | `region.endColumn`     | **Required.** The column number of the character following the end of the region.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| Name | Description                                                                                                                                                                                                                           |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id` | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | категория         | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
+
 ### SARIF output file examples
 
 These example SARIF output files show supported properties and example values.
@@ -130,7 +180,6 @@ These example SARIF output files show supported properties and example values.
 
 This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties or don't include values, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}.
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ This SARIF output file has example values to show the minimum required propertie
 
 This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}.
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ This SARIF output file has example values to show all supported SARIF properties
   ]
 }
 ```
+{% endif %}
diff --git a/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
index fc53f8392a..6bef78fbe3 100644
--- a/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
@@ -17,6 +17,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
diff --git a/translations/ru-RU/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ru-RU/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index ef961fb031..a6749cecda 100644
--- a/translations/ru-RU/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ru-RU/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -14,13 +14,15 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} results on pull requests
 
 In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or dismiss all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
 
 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -44,18 +46,10 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
 
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Fixing an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 ### Dismissing an alert on your pull request
 
 An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
@@ -67,5 +61,3 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/ru-RU/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/ru-RU/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..0cdbfc9d1d
--- /dev/null
+++ b/translations/ru-RU/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshooting CodeQL runner
+intro: 'If you''re having problems with the {% data variables.product.prodname_codeql_runner %}, you can troubleshoot by using these tips.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### The `init` command takes too long
+
+Before the {% data variables.product.prodname_codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries.
+
+When you use the {% data variables.product.prodname_codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes. The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.product.prodname_codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again.
+
+To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command.
+
+### No code found during the build
+
+If the `analyze` command for the {% data variables.product.prodname_codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure.
+
+1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)."
+
+1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the build process. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command.
+   - On macOS and Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - On Windows, using the Command shell (`cmd`) or a batch file (`.bat`):
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - On Windows, using PowerShell:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead.
+
+   {% note %}
+
+   **Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different.
+
+   {% endnote %}
+
+1. You're analyzing a compiled language on macOS without using the `autobuild` command and you run the build steps yourself after the `init` step. If SIP (System Integrity Protection) is enabled, which is the default on recent versions of OSX, analysis might fail. To fix this, prefix the build command with the `$CODEQL_RUNNER` environment variable. For example, if your build command is `cmd arg1 arg2`, you should run `$CODEQL_RUNNER cmd arg1 arg2`.
+
+1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.product.prodname_codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
diff --git a/translations/ru-RU/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/ru-RU/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
index 9b6fe97058..ceebbed87e 100644
--- a/translations/ru-RU/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
+++ b/translations/ru-RU/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -33,19 +35,22 @@ If an automatic build of code for a compiled language within your project fails,
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
         matrix:
           language: ['csharp', 'cpp', 'javascript']
 
+      steps:
       ...
-
-      - name: Initialize {% data variables.product.prodname_codeql %}
-        uses: github/codeql-action/init@v1
-        with:
-          languages: {% raw %}${{ matrix.language }}{% endraw %}
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: github/codeql-action/init@v1
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
   For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
@@ -150,29 +155,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/ru-RU/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/ru-RU/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index ab7075184c..2e58dd665e 100644
--- a/translations/ru-RU/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/ru-RU/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -24,18 +26,19 @@ topics:
 
 You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
 
 - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
-- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
-- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)").
+- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- The {% data variables.product.prodname_codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").
 - A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)").
 
 {% data reusables.code-scanning.not-available %}
 
 ### Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}
 
-To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a  workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a  workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
 Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameter you'll use is `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository. For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/HEAD/upload-sarif).
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Example workflow that runs the ESLint analysis tool
@@ -87,7 +92,7 @@ This example workflow runs anytime commits are pushed to the repository. The act
 
 The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Дополнительная литература
 
 - "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)"
-- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
+- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
 - "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"
diff --git a/translations/ru-RU/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/ru-RU/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index 1610e347ef..1f2e2e0164 100644
--- a/translations/ru-RU/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/ru-RU/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/ru-RU/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/ru-RU/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 2bed45f931..7483e0d587 100644
--- a/translations/ru-RU/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/ru-RU/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -1,6 +1,6 @@
 ---
 title: About coordinated disclosure of security vulnerabilities
-intro: 'Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.'
+intro: Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.
 miniTocMaxHeadingLevel: 4
 versions:
   free-pro-team: '*'
@@ -43,7 +43,7 @@ Publishing the details of a security vulnerability doesn't make maintainers look
 
 The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
 
- If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
+ If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository.
 
  If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
 
@@ -55,7 +55,7 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
 
- If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
+ If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
 
  As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
diff --git a/translations/ru-RU/content/code-security/security-advisories/index.md b/translations/ru-RU/content/code-security/security-advisories/index.md
index 0b43542ea5..f303ea9b4e 100644
--- a/translations/ru-RU/content/code-security/security-advisories/index.md
+++ b/translations/ru-RU/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### Table of Contents
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
index 11e23bcd76..57aca8bd52 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
 title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
+intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository.'
 redirect_from:
   - /articles/about-security-alerts-for-vulnerable-dependencies
   - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
@@ -12,6 +12,7 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
 
 ### About vulnerable dependencies
@@ -22,12 +23,12 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 ### Detection of vulnerable dependencies
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %}
+- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)."
 
 {% data reusables.repositories.dependency-review %}
 
@@ -39,11 +40,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
 ### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
-{% else %}
-### Security alerts for vulnerable dependencies
-{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
@@ -56,41 +53,28 @@ For information about permission requirements for actions related to {% data var
 {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
-{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
-{% endif %}
-
 {% warning %}
 
 **Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Access to {% data variables.product.prodname_dependabot %} alerts
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
-{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
-{% endif %}
+You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### Дополнительная литература
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index d831bca031..7b8fa4e1a3 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About {% data variables.product.prodname_dependabot_version_updates %}
@@ -35,6 +35,7 @@ You specify how often to check each ecosystem for new versions in the configurat
 If you've enabled security updates, you'll sometimes see extra pull requests for security updates. These are triggered by a {% data variables.product.prodname_dependabot %} alert for a dependency on your default branch. {% data variables.product.prodname_dependabot %} automatically raises a pull request to update the vulnerable dependency.
 
 ### Supported repositories and ecosystems
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)."
 
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-dependency-review.md b/translations/ru-RU/content/code-security/supply-chain-security/about-dependency-review.md
index aef885dac5..941a5b2f95 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/about-dependency-review.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/about-dependency-review.md
@@ -4,7 +4,7 @@ intro: 'Dependency review lets you catch vulnerable dependencies before you intr
 versions:
   free-pro-team: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md
index 53e155d122..e80c1c970d 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md
@@ -10,6 +10,7 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
 <!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
 
 ### Dependency graph availability
@@ -60,10 +61,6 @@ You can use the dependency graph to:
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
-
-{% endif %}
-
 When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
 
 ### Supported package ecosystems
@@ -90,6 +87,6 @@ The recommended formats explicitly define which versions are used for all direct
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
 - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
+- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}
 - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index 28538a8164..5ca3b8688d 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -164,7 +164,7 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Use the `allow` option to customize which dependencies are updated. This has no impact on security updates for vulnerable dependencies. You can use the following options:
+Use the `allow` option to customize which dependencies are updated. This applies to both version and security updates. You can use the following options:
 
 - `dependency-name`—use to allow updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId`, for example: `org.kohsuke:github-api`.
 - `dependency-type`—use to allow updates for dependencies of specific types.
@@ -445,12 +445,12 @@ updates:
 
 #### `rebase-strategy`
 
-By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects conflicts. Use `rebase-strategy` to disable this behavior.
+By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. Use `rebase-strategy` to disable this behavior.
 
 Available rebase strategies
 
 - `disabled` to disable automatic rebasing.
-- `auto` to use the default behavior and rebase open pull requests when conflicts are detected.
+- `auto` to use the default behavior and rebase open pull requests when changes are detected.
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -473,11 +473,11 @@ To allow {% data variables.product.prodname_dependabot %} to access a private pa
 
 To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution).
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -493,11 +493,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -716,7 +716,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
@@ -730,6 +730,7 @@ You use the following options to specify access settings. Registry settings must
 | `url`                                                                                                  | The URL to use to access the dependencies in this registry. The protocol is optional. If not specified, `https://` is assumed. {% data variables.product.prodname_dependabot %} adds or ignores trailing slashes as required.                                                   |
 | `имя пользователя`                                                                                     | The username that {% data variables.product.prodname_dependabot %} uses to access the registry.                                                                                                                                                                                 |
 | `пароль`                                                                                               | A reference to a {% data variables.product.prodname_dependabot %} secret containing the password for the specified user. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)." |
+| `клавиша`                                                                                              | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access key for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."     |
 | `токен`                                                                                                | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access token for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)."   |
 | `replaces-base`                                                                                        | For registries with `type: python-index`, if the boolean value is `true`, pip resolves dependencies by using the specified URL rather than the base URL of the Python Package Index (by default `https://pypi.org/simple`).                                                     |
 
@@ -766,6 +767,19 @@ registries:
 ```
 {% endraw %}
 
+The `docker-registry` type can also be used to pull from Amazon ECR using static AWS credentials.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 The `git` type supports username and password.
@@ -781,6 +795,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+The `hex-organization` type supports organization and key.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 The `maven-repository` type supports username and password, or token.
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index 9f40d16d4c..f2b77b4852 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,7 +1,7 @@
 ---
 title: Configuring notifications for vulnerable dependencies
 shortTitle: Configuring notifications
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+intro: 'Optimize how you receive notifications about {% data variables.product.prodname_dependabot %} alerts.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
@@ -11,48 +11,41 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
+
 ### About notifications for vulnerable dependencies
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
+When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
-Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.20" %}
-By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %}
+By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.{% endif %}
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
 
 You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
-{% else %}
-  ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png)
-{% endif %}
 
 {% note %}
 
-**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} alerts. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
 
 ### How to reduce the noise from notifications for vulnerable dependencies
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md
index f058194f72..f121e18c39 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md
@@ -7,7 +7,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About customizing dependency updates
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index 784a8ccb2f..8e26f2f55a 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -7,7 +7,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About version updates for dependencies".-->
@@ -18,7 +18,7 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c
 
 {% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)."
 
-{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
+{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
 
 ### Enabling {% data variables.product.prodname_dependabot_version_updates %}
 
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index f84d07765f..159e0c8801 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -15,6 +15,8 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
@@ -50,19 +52,6 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
-
-![График зависимостей](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view.
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### Dependents view
 
@@ -113,8 +102,8 @@ If a manifest or lock file is not processed, its dependencies are omitted from t
 
 ### Дополнительная литература
 
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
 - "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
 - "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)"
 {% endif %}
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/index.md b/translations/ru-RU/content/code-security/supply-chain-security/index.md
index a0a051b654..4c9c860ff6 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/index.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md b/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md
index 10b7e9e41a..bcdffa6346 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md
@@ -7,6 +7,6 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md
index b58accff31..7acd9de5f8 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### Viewing dependencies monitored by {% data variables.product.prodname_dependabot %}
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md
index 53a261fe7d..7d23d29dbb 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About {% data variables.product.prodname_dependabot %} pull requests
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 5e61d008cb..a452958e07 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -17,18 +17,18 @@ The results of dependency detection reported by {% data variables.product.produc
 
 {% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following:
 
-*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies. It's a free, curated database of vulnerability information for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 *   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-*   {% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
 
-    {% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is discovered and added to the advisory database.
+    {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% if currentVersion ver_gt "enterprise-server@2.22" %} and synchronized to {% data variables.product.prodname_ghe_server %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
 
 ### Why don't I get vulnerability alerts for some ecosystems?
 
-{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot %} security updates are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+{% data variables.product.prodname_dotcom %} limits its support for vulnerability alerts to a set of ecosystems where we can provide high-quality, actionable data. Curated vulnerabilities in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot %} alerts are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
 
-It's worth noting that [{% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems.
+It's worth noting that {% data variables.product.prodname_dotcom %} Security Advisories may exist for other ecosystems. The information in a security advisory is provided by the maintainers of a particular repository. This data is not curated in the same way as information for the supported ecosystems. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}
 
 **Check**: Does the uncaught vulnerability apply to an unsupported ecosystem?
 
@@ -36,9 +36,9 @@ It's worth noting that [{% data variables.product.prodname_dotcom %} Security Ad
 
 The dependency graph includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
 
-{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% data variables.product.prodname_dependabot %} security updates only suggests a change where it can directly "fix" the dependency, that is, when these are:
+{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
 * Direct dependencies explicitly declared in a manifest or lockfile
-* Transitive dependencies declared in a lockfile
+* Transitive dependencies declared in a lockfile{% endif %}
 
 The dependency graph doesn't include “loose” dependencies. “Loose” dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile.
 
@@ -84,6 +84,7 @@ Some third-party tools use uncurated CVE data that isn't checked or filtered by
 
 Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant.
 
+{% if currentVersion == "free-pro-team@latest" %}
 ### 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.
@@ -97,10 +98,11 @@ When you click to display the alert details, you can see how many vulnerabilitie
 ![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
 **Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with vulnerability numbers.
+{% endif %}
 
 ### Дополнительная литература
 
 - "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/ru-RU/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..7c186aac17
--- /dev/null
+++ b/translations/ru-RU/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Upgrading from Dependabot.com to GitHub-native Dependabot
+intro: You can upgrade to GitHub-native Dependabot by merging a pull request that will allow your dependencies to continue being updated.
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot before then.
+
+After that date, any open pull requests from Dependabot Preview will remain open, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations.
+
+{% endwarning %}
+
+### About upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Dependabot Preview has been built directly into {% data variables.product.prodname_dotcom %}, so you can use {% data variables.product.prodname_dependabot %} alongside all the other functionality in {% data variables.product.prodname_dotcom %} without having to install and use a separate application. By migrating to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, we can also focus on bringing lots of exciting new features to {% data variables.product.prodname_dependabot %}, including more [ecosystem updates](https://github.com/github/roadmap/issues/150), [improved notifications](https://github.com/github/roadmap/issues/133), and {% data variables.product.prodname_dependabot %} support for [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) and [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Differences between Dependabot Preview and {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+While most of the Dependabot Preview features exist in {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, a few remain unavailable:
+- **Live updates:** We hope to bring these back in the future. For now, you can run {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} daily to catch new packages within one day of release.
+- **PHP environment variable registries:** For now, you can use {% data variables.product.prodname_actions %} to fetch dependencies from these registries.
+- **Auto-merge:** We always recommend verifying your dependencies before merging them; therefore, auto-merge will not be supported for the foreseeable future. For those of you who have vetted your dependencies, or are only using internal dependencies, we recommend adding third-party auto-merge apps, or setting up GitHub Actions to merge.
+
+In {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, you can configure all version updates using the configuration file. This file is similar to the Dependabot Preview configuration file with a few changes and improvements that will be automatically included in your upgrade pull request. For more information about the upgrade pull request, see "[Upgrading to GitHub-native Dependabot](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+To see update logs for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} that were previously on the Dependabot.com dashboard:
+
+  1. Navigate to your repository’s **Insights** page.
+  2. Click **Dependency graph** to the left.
+  3. Click **{% data variables.product.prodname_dependabot %}**.
+
+For more information about version updates with {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, see "[About Dependabot version updates](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+### Upgrading to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} requires you to merge the *Upgrade to GitHub-native Dependabot* pull request in your repository. This pull request includes the updated configuration file needed for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}.
+
+If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
+
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
+
+If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/ru-RU/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ru-RU/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index d45b4a9146..f2ebddc49e 100644
--- a/translations/ru-RU/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/ru-RU/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}. You can sort the list of alerts using 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 %}{% if currentVersion == "free-pro-team@latest" %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts using 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)."
 
+{% if currentVersion == "free-pro-team@latest" %}
 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 %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ 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.
+{% endif %}
 
 ### Viewing and updating vulnerable dependencies
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ You can enable automatic security updates for any repository that uses {% data v
 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](/github/administering-a-repository/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, use 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 currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Click the alert you'd like to view. ![Alert selected in list of alerts](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency.
+1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, click the **Dismiss** drop-down, and select a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. Click the version number of the vulnerable dependency to display detailed information. ![Detailed information on the vulnerable dependency](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. Review the details of the vulnerability and determine whether or not you need to update the dependency. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert.
+1. The banner at the top of the **Dependencies** tab is displayed until all the vulnerable dependencies are resolved or you dismiss it. Click **Dismiss** in the top right corner of the banner and select a reason for dismissing the alert. ![Dismiss security banner](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### Дополнительная литература
 
-- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"
+- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
 - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ru-RU/content/codespaces/about-codespaces.md b/translations/ru-RU/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..e0792098d3
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: About Codespaces
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![An open codespace](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Developers can contribute from anywhere, on any machine, including tablets or Chromebooks, and there is no need to maintain local copies of intellectual property. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### About billing for {% data variables.product.prodname_codespaces %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %} For more information, see "[About billing for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)."
+
+### Joining the beta
+
+A limited number of people will be invited to join the beta. To join the waitlist, see [Sign up for Codespaces beta](https://github.com/features/codespaces/signup).
+
+### Contacting us about {% data variables.product.prodname_codespaces %}
+
+If you encounter problems using {% data variables.product.prodname_codespaces %}, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
+
+If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the [Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) discussion.
diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..f621a80494
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: About billing for Codespaces
+intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..75be9e6f73
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Allowing your codespace to access a private image registry
+intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry.
+
+When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)."
+
+For example, if you had a private image registry in Azure, you could create the following secrets:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/index.md b/translations/ru-RU/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..21334e4bb5
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: Reference
+intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..6284b0674a
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: Troubleshooting your codespace
+intro: Use this guide to help you troubleshoot common issues with your codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Known Limitations
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### {% data variables.product.prodname_vscode %} troubleshooting
+
+Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.
+
+
+### Configuration troubleshooting
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+This codespace is currently running in recovery mode due to a container error.
+```
+
+Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
+
+### dotfiles troubleshooting
+
+- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles.
+- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned.
+  - If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
+  - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
+- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**.
+
+
+### Browser troubleshooting
+
+If you encounter issues while using a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as[`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari).
+
+If you encounter issues while using a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository.
+
+### Container storage troubleshooting
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.
+
+- Remove packages that are no longer by using `sudo apt autoremove`
+- Clean the apt cache by using `sudo apt clean`
+- Delete unneeded files like build artifacts and logs (these are very project-dependent)
+- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10`
+
+More destructive options:
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes)
+- Remove untracked files from working tree: `git clean -i`
+
+### Contact us
+
+If you still need help, you can contact us. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)."
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..19fc36dfc5
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Creating a codespace
+intro: You can create a codespace for a branch in a repository to develop online.
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About codespace creation
+
+You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)."
+
+
+When you create a codespace, a number of steps happen to enable full access to your development environment.
+
+- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
+- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
+- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+- Your Docker container, `docker-compose`, or other initialization is run.
+- At this point, the codespace is marked as available and you can connect.
+- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up.
+  - The codespace shares ports added in the `devcontainer.json` file.
+  - The codespace runs anything specified in `postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Finally, the codespace does a full clone of the repo so you have full access to it.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### Creating a codespace
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Under the repository name, use the "Branch" drop-down menu, and select the branch you want to create a codespace for.
+
+  ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..e6784b3775
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: Deleting a codespace
+intro: You can delete a codespace you no longer need.
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+
+2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
+
+### Deleting a codespace in {% data variables.product.prodname_vscode %}
+
+For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)."
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..a3ae678e34
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: Developing in a codespace
+intro: 'You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}''s features.'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About development with {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Side Bar - By default, this area shows your project files in the Explorer.
+2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
+3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
+4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
+5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
+
+For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)."
+
+#### Personalizing your codespace
+
+{% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)."
+
+{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)."
+
+#### Running your app from a codespace
+{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)."
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Navigating to an existing codespace
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. Click the name of the codespace you want to develop in. ![Name of codespace](/assets/images/help/codespaces/click-name-codespace.png)
+
+Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..7965bfc793
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: Forwarding ports in your codespace
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About forwarded ports
+
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application.
+
+When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. For example, if an application outputs `http://127.0.0.1:4000` or `http://localhost:4000` to the console, the log would automatically convert the output to a clickable URL for port 4000.
+
+![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration.
+
+### Forwarding a port
+
+You can manually forward a port that wasn't forwarded automatically.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png)
+1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
+
+### Labeling a port
+
+You can label a port to make the port more easily identifiable in a list.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### Sharing a port
+
+If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png)
+1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Send the copied URL to the person you want to share the port with.
+
+### Adding a port to the codespace configuration
+
+You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..e436eb79e8
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: Developing in a codespace
+intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..3cac79d040
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: Using Codespaces in Visual Studio Code
+intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Требования
+
+To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later.
+
+Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation.
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+4. Sign in to {% data variables.product.product_name %} to approve the extension.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+5. Sign in to {% data variables.product.product_name %} to approve the extension.
+
+{% endwindows %}
+
+### Creating a codespace in {% data variables.product.prodname_vscode %}
+
+After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_github_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Click the machine type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png)
+### Opening a codespace in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Under "Codespaces", click the codespace you want to develop in.
+3. Click the Connect to Codespace icon. ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### Changing the machine type in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+You can change the machine type of your codespace at any time.
+
+1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`).
+2. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. Click the codespace that you want to change. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. Choose the machine type you want to use. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts.
+
+### Deleting a codespace in {% data variables.product.prodname_vscode %}
+
+1. Under "Codespaces", right-click the codespace you want to delete.
+2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..1ef48ef4f9
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About source control in {% data variables.product.prodname_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+### Creating or switching branches
+
+1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**.
+1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace.
+
+{% endtip %}
+
+### Pulling changes from the remote repository
+
+You can pull changes from the remote repository into your codespace at any time.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. In the drop-down menu, click **Pull**.
+
+If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+### Setting your codespace to automatically fetch new changes
+
+You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
+
+If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
+
+1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Click **Create**.
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..4b7bfcf855
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Getting started with your C# (.NET) project in Codespaces
+shortTitle: Getting started with your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Требования
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Файл Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Файл Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Дальнейшие шаги
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..8169ac2a3e
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Getting started with your Java project in Codespaces
+shortTitle: Getting started with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Требования
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Файл Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Файл Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Дальнейшие шаги
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..fe41bc2570
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Getting started with your Node.js project in Codespaces
+shortTitle: Getting started with your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Требования
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Файл Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Файл Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Дальнейшие шаги
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..9df77249c6
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Getting started with your Python project in Codespaces
+shortTitle: Getting started with your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### Требования
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Файл Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Файл Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**.
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Дальнейшие шаги
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..013f96d508
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: Getting Started with {% data variables.product.prodname_codespaces %}
+intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/ru-RU/content/codespaces/guides.md b/translations/ru-RU/content/codespaces/guides.md
new file mode 100644
index 0000000000..8c3032ac5a
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: Руководства
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/ru-RU/content/codespaces/index.md b/translations/ru-RU/content/codespaces/index.md
new file mode 100644
index 0000000000..df9aee66d9
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: https://www.youtube-nocookie.com/embed/_W9B7qc9lVc
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
\ No newline at end of file
diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..1034377b45
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing Codespaces for your organization
+intro: 'You can manange and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..f3d0f9eb29
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Managing access and security for your organization's codespaces
+shortTitle: Managing access and security for your organization
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Organization owners can manage which repositories a codespace can access.
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.
+
+To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
new file mode 100644
index 0000000000..ac148f188a
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Managing encrypted secrets for your repository and organization for Codespaces
+shortTitle: Managing secrets for your repository and organization
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Limits for secrets
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+Secrets are limited to 64 KB in size.
+
+### Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. At the top of the page, click **New repository secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the value for your secret.
+1. Click **Add secret**.
+
+### Adding secrets for an organization
+
+When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. At the top of the page, click **New organization secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the **Value** for your secret.
+1. From the **Repository access** dropdown list, choose an access policy. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+1. Click **Add secret**.
+
+### Reviewing access to organization-level secrets
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. The list of secrets includes any configured permissions and policies. Например: ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
+1. For more details on the configured permissions for each secret, click **Update**.
diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..f8c2c9ac71
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.
+permissions: To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..c438a70311
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing your organization's audit logs for Codespaces
+shortTitle: Reviewing your organization's audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)."
diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/index.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..2241dd5ecf
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..6ad3cdee4a
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### About encrypted secrets for {% data variables.product.prodname_codespaces %}
+
+You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets.
+
+- Personal access tokens to cloud services
+- Service principals
+- Subscription identifiers
+- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### Limits for secrets
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+Secrets are limited to 64 KB in size.
+
+### Adding a secret
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. Under "Name", type a name for your secret. !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Click **Add secret**.
+
+### Editing a secret
+
+You can update the value of an existing secret, and you can change which repositories can access a secret.
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. Click **Save changes**.
+
+### Deleting a secret
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..c9492f1760
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: Managing GPG verification for Codespaces
+intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)."
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..f7e213e258
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)."
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
diff --git a/translations/ru-RU/content/codespaces/quickstart.md b/translations/ru-RU/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..aa93c46407
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Introduction
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**.
+
+  ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..9df28ebec6
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,142 @@
+---
+title: Configuring Codespaces for your project
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### Файл Dockerfile
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Follow the prompts to customize your definition.
+1. Click **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### Creating a custom codespace configuration
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+You can define default editor settings for {% data variables.product.prodname_vscode %} in two places.
+
+* Editor settings defined in `.vscode/settings.json` are applied as _Workspace_-scoped settings in the codespace.
+* Editor settings defined in the `settings` key in `devcontainer.json` are applied as _Remote [Codespaces]_-scoped settings in the codespace.
+
+After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)."
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### Applying changes to your configuration
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}
+!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - To diagnose the error by reviewing the creation logs, click **View creation log**.
+   - To fix the errors identified in the logs, update your `devcontainer.json` file.
+   - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md b/translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..7f70ac5943
--- /dev/null
+++ b/translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: Personalizing Codespaces for your account
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)."
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your `dotfiles` repository, see [GitHub does dotfiles](https://dotfiles.github.io/).
+
+If your user account on {% data variables.product.prodname_dotcom %} owns a public repository named `dotfiles`, {% data variables.product.prodname_dotcom %} automatically uses this repository to personalize your codespace environment. Private `dotfiles` repositories are not currently supported.
+
+Your `dotfiles` repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make.
+
+When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your `dotfiles` repository to the codespace environment, and looks for one of the following files to set up the environment.
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
+
+Any changes to your `dotfiles` repository will apply only to each new codespace, and do not affect any existing codespace.
+
+{% note %}
+
+**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the _User_ settings for the {% data variables.product.prodname_vscode %} editor with your `dotfiles` repository. You can set default _Workspace_ and _Remote [Codespaces]_ settings for a specific project in the project's repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)."
+
+{% endnote %}
+
+You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)."
+
+### Дополнительная литература
+
+* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
diff --git a/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md
index ab70b9d2dd..f03b737bd4 100644
--- a/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ With wikis, you can write content just like everywhere else on {% data variables
 
 You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository. For more information, see "[Changing access permissions for wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)".
 
+{% note %}
+
+**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository.
+
+{% endnote %}
+
 ### Дополнительная литература
 
 - "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
diff --git a/translations/ru-RU/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/ru-RU/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index a04d95fddd..01cc51a6b3 100644
--- a/translations/ru-RU/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/ru-RU/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ In your organization's repositories, blocked users also cannot:
 ### Blocking a user in the organization settings
 
 1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. Under "Block a user", type the username of the user you'd like to block. ![Username field](/assets/images/help/organizations/org-block-username-field.png)
 7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user. ![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/ru-RU/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/ru-RU/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index d799533db2..78bd366156 100644
--- a/translations/ru-RU/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/ru-RU/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,9 +28,9 @@ If you selected a specific amount of time to block the user, they will be automa
 
 ### Unblocking a user in the organization settings
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**. ![Unblock user button](/assets/images/help/organizations/org-unblock-user-button.png)
 
diff --git a/translations/ru-RU/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/ru-RU/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index ebeebfcd70..6232d7dc81 100644
--- a/translations/ru-RU/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/ru-RU/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,9 +10,9 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. Under "Blocked users", review the list of users who are blocked from your organization. ![List of blocked users](/assets/images/help/settings/list-of-blocked-users-for-org.png)
 
diff --git a/translations/ru-RU/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/ru-RU/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index 3171d42d23..3cbbfd02b6 100644
--- a/translations/ru-RU/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/ru-RU/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -28,9 +28,9 @@ Organization owners can also block users for a specific amount of time. After th
 
 ### Limiting interactions in your organization
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the organization settings sidebar, click **Moderation settings**. !["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. Under "Moderation settings", click **Interaction limits**. !["Interaction limits" in the organization settings sidebar](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 465c7b629b..8ec0e364cf 100644
--- a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -29,14 +29,14 @@ Default files are not included in clones, packages, or downloads of individual r
 
 You can create defaults in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} for the following community health files:
 
-| Community health file                                                                                                                                                                                   | Description                                                                                                                                                                                                                                                                                                                                         |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| Community health file                                                                                                                                                                                   | Description                                                                                                                                                                                                                                                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
 | *CODE_OF_CONDUCT.md*                                                                                                                                                                                  | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
 | *CONTRIBUTING.md*                                                                                                                                                                                       | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% if currentVersion == "free-pro-team@latest" %}
 | *FUNDING.yml*                                                                                                                                                                                           | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
-| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" %}
-| *SECURITY.md*                                                                                                                                                                                           | A SECURITY file gives instructions for how to responsibly report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/articles/adding-a-security-policy-to-your-repository)."{% endif %}
-| *SUPPORT.md*                                                                                                                                                                                            | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."                                                                                                                                              |
+| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| *SECURITY.md*                                                                                                                                                                                           | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
+| *SUPPORT.md*                                                                                                                                                                                            | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."                                                                                                                                                                                               |
 
 You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
 
diff --git a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index f6d4475c87..0c18a3e7cc 100644
--- a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file.
+### About contributing guidelines
+To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ You can create default contribution guidelines for your organization{% if curren
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive, and can have an extension such as *.md* or *.txt*. ![New file name](/assets/images/help/repository/new-file-name.png)
+3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![New file name](/assets/images/help/repository/new-file-name.png)
     - To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
     - To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. In the new file, add contribution guidelines. These could include:
     - Steps for creating good issues or pull requests.
     - Links to external documentation, mailing lists, or a code of conduct.
diff --git a/translations/ru-RU/content/developers/apps/about-apps.md b/translations/ru-RU/content/developers/apps/about-apps.md
index bf3f30d2eb..3eca7a0073 100644
--- a/translations/ru-RU/content/developers/apps/about-apps.md
+++ b/translations/ru-RU/content/developers/apps/about-apps.md
@@ -11,7 +11,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% if currentVersion == "free-pro-team@latest" %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %}
diff --git a/translations/ru-RU/content/developers/apps/activating-optional-features-for-apps.md b/translations/ru-RU/content/developers/apps/activating-optional-features-for-apps.md
index 59cf83a4b6..98119e34e3 100644
--- a/translations/ru-RU/content/developers/apps/activating-optional-features-for-apps.md
+++ b/translations/ru-RU/content/developers/apps/activating-optional-features-for-apps.md
@@ -8,7 +8,7 @@ versions:
   github-ae: '*'
   enterprise-server: '>=2.22'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% warning %}
diff --git a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md
index 9f392eccf3..b63e07c246 100644
--- a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md
+++ b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
diff --git a/translations/ru-RU/content/developers/apps/building-github-apps.md b/translations/ru-RU/content/developers/apps/building-github-apps.md
index 8c79f00995..9ab58bd3a9 100644
--- a/translations/ru-RU/content/developers/apps/building-github-apps.md
+++ b/translations/ru-RU/content/developers/apps/building-github-apps.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
diff --git a/translations/ru-RU/content/developers/apps/building-oauth-apps.md b/translations/ru-RU/content/developers/apps/building-oauth-apps.md
index ef1c5d8540..f2c27c7988 100644
--- a/translations/ru-RU/content/developers/apps/building-oauth-apps.md
+++ b/translations/ru-RU/content/developers/apps/building-oauth-apps.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md
index 8d056f62a1..4a7c2b971a 100644
--- a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -179,7 +179,7 @@ You must complete this step of the GitHub App Manifest flow within one hour.
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest).
 
diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app.md b/translations/ru-RU/content/developers/apps/creating-a-github-app.md
index 2f9823ffa8..88e9fb58d4 100644
--- a/translations/ru-RU/content/developers/apps/creating-a-github-app.md
+++ b/translations/ru-RU/content/developers/apps/creating-a-github-app.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}To learn how to use GitHub App Manifests, which allow people to create preconfigured GitHub Apps, see "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
diff --git a/translations/ru-RU/content/developers/apps/creating-an-oauth-app.md b/translations/ru-RU/content/developers/apps/creating-an-oauth-app.md
index 0676ef0eb8..592b33276c 100644
--- a/translations/ru-RU/content/developers/apps/creating-an-oauth-app.md
+++ b/translations/ru-RU/content/developers/apps/creating-an-oauth-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
diff --git a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index 1c96b2cd18..3ee37dfd63 100644
--- a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sina
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). This method takes two parameters: the URL of the endpoint and the input parameters to the method.
+This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
 
 To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [Rubocop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo Rubocop" is used here, but you can choose any name you'd like for the check run.
 
@@ -240,31 +235,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -276,40 +262,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created.
+The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created.
 
-Here's what this code is doing. First, it updates the check run's status to `in_progress` and sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
+Here's what this code is doing. First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
 
 You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`.
 
@@ -613,29 +589,23 @@ Now you've got all the information you need to update your check run. In the [fi
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -645,51 +615,45 @@ You'll need to update that code to use the `conclusion` variable you set based o
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/ru-RU/content/developers/apps/deleting-a-github-app.md b/translations/ru-RU/content/developers/apps/deleting-a-github-app.md
index 6853b6de79..98359bc0a1 100644
--- a/translations/ru-RU/content/developers/apps/deleting-a-github-app.md
+++ b/translations/ru-RU/content/developers/apps/deleting-a-github-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/ru-RU/content/developers/apps/deleting-an-oauth-app.md b/translations/ru-RU/content/developers/apps/deleting-an-oauth-app.md
index 81259c8f8f..2d2c6cc790 100644
--- a/translations/ru-RU/content/developers/apps/deleting-an-oauth-app.md
+++ b/translations/ru-RU/content/developers/apps/deleting-an-oauth-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/ru-RU/content/developers/apps/editing-a-github-apps-permissions.md b/translations/ru-RU/content/developers/apps/editing-a-github-apps-permissions.md
index e15d99d4ed..0cc2909909 100644
--- a/translations/ru-RU/content/developers/apps/editing-a-github-apps-permissions.md
+++ b/translations/ru-RU/content/developers/apps/editing-a-github-apps-permissions.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/developers/apps/getting-started-with-apps.md b/translations/ru-RU/content/developers/apps/getting-started-with-apps.md
index 46aa599b97..e6ce597b56 100644
--- a/translations/ru-RU/content/developers/apps/getting-started-with-apps.md
+++ b/translations/ru-RU/content/developers/apps/getting-started-with-apps.md
@@ -7,6 +7,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
diff --git a/translations/ru-RU/content/developers/apps/installing-github-apps.md b/translations/ru-RU/content/developers/apps/installing-github-apps.md
index c9a690a9bf..08e75e709a 100644
--- a/translations/ru-RU/content/developers/apps/installing-github-apps.md
+++ b/translations/ru-RU/content/developers/apps/installing-github-apps.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/developers/apps/making-a-github-app-public-or-private.md b/translations/ru-RU/content/developers/apps/making-a-github-app-public-or-private.md
index bb972114bb..86e6d04355 100644
--- a/translations/ru-RU/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/ru-RU/content/developers/apps/making-a-github-app-public-or-private.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
@@ -23,7 +23,7 @@ Public installation flows have a landing page to enable other people besides the
 
 ### Private installation flow
 
-Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private, or internal, GitHub Apps can only be installed on the user or organization account of the owner.
+Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### Changing who can install your GitHub App
 
@@ -34,5 +34,5 @@ To change who can install the GitHub App:
 {% data reusables.user-settings.github_apps %}
 3. Select the GitHub App whose installation option you want to change. ![App selection](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. Depending on the installation option of your GitHub App, click either **Make public** or **Make internal**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
-6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App internal**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/ru-RU/content/developers/apps/managing-github-apps.md b/translations/ru-RU/content/developers/apps/managing-github-apps.md
index 0bab3a14a5..4c37303a74 100644
--- a/translations/ru-RU/content/developers/apps/managing-github-apps.md
+++ b/translations/ru-RU/content/developers/apps/managing-github-apps.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
diff --git a/translations/ru-RU/content/developers/apps/managing-oauth-apps.md b/translations/ru-RU/content/developers/apps/managing-oauth-apps.md
index 296ec9d672..203151e7d2 100644
--- a/translations/ru-RU/content/developers/apps/managing-oauth-apps.md
+++ b/translations/ru-RU/content/developers/apps/managing-oauth-apps.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
diff --git a/translations/ru-RU/content/developers/apps/modifying-a-github-app.md b/translations/ru-RU/content/developers/apps/modifying-a-github-app.md
index 137734f529..0b2ef3bff9 100644
--- a/translations/ru-RU/content/developers/apps/modifying-a-github-app.md
+++ b/translations/ru-RU/content/developers/apps/modifying-a-github-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/ru-RU/content/developers/apps/modifying-an-oauth-app.md b/translations/ru-RU/content/developers/apps/modifying-an-oauth-app.md
index a20728b58f..ce9e9af067 100644
--- a/translations/ru-RU/content/developers/apps/modifying-an-oauth-app.md
+++ b/translations/ru-RU/content/developers/apps/modifying-an-oauth-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md b/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md
index 2451916675..af855b748b 100644
--- a/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md
+++ b/translations/ru-RU/content/developers/apps/rate-limits-for-github-apps.md
@@ -11,7 +11,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 ### Server-to-server requests
diff --git a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md
index ebd4e480fa..d91f7a7f90 100644
--- a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md
+++ b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md
@@ -30,7 +30,7 @@ Check headers to see what OAuth scopes you have, and what the API action accepts
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
-HTTP/1.1 200 OK
+HTTP/2 200
 X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
diff --git a/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md b/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md
index 4d9c1fb557..565070617d 100644
--- a/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md
+++ b/translations/ru-RU/content/developers/apps/setting-permissions-for-github-apps.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 GitHub Apps don't have any permissions by default. When you create a GitHub App, you can select the permissions it needs to access end user data. Permissions can also be added and removed. For more information, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)."
diff --git a/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 0aac1914cf..a7e3a69480 100644
--- a/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -370,10 +370,10 @@ After you click **Install**, look at the output in your Terminal. You should see
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 This is good news! It means your app received a notification that it was installed on your GitHub account. If you see something like this, your app is running on the server as expected. 🙌
diff --git a/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md b/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md
index 691e61e739..e42c1e20b5 100644
--- a/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md
+++ b/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 ### Suspending a GitHub App
diff --git a/translations/ru-RU/content/developers/apps/transferring-ownership-of-a-github-app.md b/translations/ru-RU/content/developers/apps/transferring-ownership-of-a-github-app.md
index 2ccce695dc..983813f6cb 100644
--- a/translations/ru-RU/content/developers/apps/transferring-ownership-of-a-github-app.md
+++ b/translations/ru-RU/content/developers/apps/transferring-ownership-of-a-github-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/ru-RU/content/developers/apps/transferring-ownership-of-an-oauth-app.md b/translations/ru-RU/content/developers/apps/transferring-ownership-of-an-oauth-app.md
index 8c9ca7df9e..4ffe69fc28 100644
--- a/translations/ru-RU/content/developers/apps/transferring-ownership-of-an-oauth-app.md
+++ b/translations/ru-RU/content/developers/apps/transferring-ownership-of-an-oauth-app.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/ru-RU/content/developers/apps/troubleshooting-authorization-request-errors.md b/translations/ru-RU/content/developers/apps/troubleshooting-authorization-request-errors.md
index 6a634e8ba0..c04a47d395 100644
--- a/translations/ru-RU/content/developers/apps/troubleshooting-authorization-request-errors.md
+++ b/translations/ru-RU/content/developers/apps/troubleshooting-authorization-request-errors.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github apps
+  - GitHub Apps
 ---
 
 ### Application suspended
diff --git a/translations/ru-RU/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/ru-RU/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md
index 94538d0b21..a2b6bdeba3 100644
--- a/translations/ru-RU/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md
+++ b/translations/ru-RU/content/developers/apps/troubleshooting-oauth-app-access-token-request-errors.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - oauth apps
+  - OAuth Apps
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/developers/apps/using-content-attachments.md b/translations/ru-RU/content/developers/apps/using-content-attachments.md
index 882ecb64d3..74b0632748 100644
--- a/translations/ru-RU/content/developers/apps/using-content-attachments.md
+++ b/translations/ru-RU/content/developers/apps/using-content-attachments.md
@@ -130,9 +130,8 @@ To create a Probot App, follow these steps:
 2. Open the project you created, and customize the settings in the `app.yml` file. Subscribe to the `content_reference` event and enable `content_references` write permissions:
 
    ``` yml
-
     default_events:
-    - content_reference
+      - content_reference
     # The set of permissions needed by the GitHub App. The format of the object uses
     # the permission name for the key (for example, issues) and the access type for
     # the value (for example, write).
@@ -141,10 +140,10 @@ To create a Probot App, follow these steps:
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
diff --git a/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index ce3bc647be..5f6c3d899f 100644
--- a/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ To offer paid plans for your app, the app must be owned by an organization and y
 
 ### Requesting publisher verification
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. In the left sidebar, click **Developer settings**. ![Developer settings option in the organization settings sidebar](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. Under "Publisher Verification", complete the information in the checklist:
    - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
    - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."
-   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+   - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/ru-RU/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/ru-RU/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index a1d737790c..ca0ac1ca59 100644
--- a/translations/ru-RU/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/ru-RU/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ Here are guidelines about the fields you'll need to fill out in the **Listing de
 
 #### Listing name
 
-Your app's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters.
+Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing {% data variables.product.product_name %} user, unless the name is your own user or organization name.
 
 #### Very short description
 
diff --git a/translations/ru-RU/content/developers/overview/about-githubs-apis.md b/translations/ru-RU/content/developers/overview/about-githubs-apis.md
index 7141a1ac74..591c29932f 100644
--- a/translations/ru-RU/content/developers/overview/about-githubs-apis.md
+++ b/translations/ru-RU/content/developers/overview/about-githubs-apis.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). For information on using the GraphQL API, see the [v4 docs](/graphql).
diff --git a/translations/ru-RU/content/developers/overview/github-developer-program.md b/translations/ru-RU/content/developers/overview/github-developer-program.md
index 947b290ce3..96a79602d0 100644
--- a/translations/ru-RU/content/developers/overview/github-developer-program.md
+++ b/translations/ru-RU/content/developers/overview/github-developer-program.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - api
+  - API
 ---
 
 Building an application that integrates with GitHub? Register for our Developer Program! The possibilities are endless, and you enjoy the kudos. [Register now](https://github.com/developer/register)
diff --git a/translations/ru-RU/content/developers/overview/replacing-github-services.md b/translations/ru-RU/content/developers/overview/replacing-github-services.md
index 05f75c5079..b5aefd1903 100644
--- a/translations/ru-RU/content/developers/overview/replacing-github-services.md
+++ b/translations/ru-RU/content/developers/overview/replacing-github-services.md
@@ -9,7 +9,7 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - api
+  - API
 ---
 
 
diff --git a/translations/ru-RU/content/developers/overview/secret-scanning.md b/translations/ru-RU/content/developers/overview/secret-scanning.md
index 6df6574480..a8672ddbe9 100644
--- a/translations/ru-RU/content/developers/overview/secret-scanning.md
+++ b/translations/ru-RU/content/developers/overview/secret-scanning.md
@@ -8,16 +8,16 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - api
+  - API
 ---
 
 {% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}.
 
 When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice.
 
-When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
+When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
 
-This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program.
+This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program.
 
 ### The {% data variables.product.prodname_secret_scanning %} process
 
@@ -54,26 +54,20 @@ Send this information to <a href="mailto:secret-scanning@github.com">secret-scan
 
 #### Create a secret alert service
 
-Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send a HTTP `POST` message to your endpoint.
+Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint.
 
 ##### Example POST sent to your endpoint
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %}  may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out.
@@ -88,19 +82,31 @@ We strongly recommend you implement signature validation in your secret alert se
 
 You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm.
 
-Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set.
+{% note %}
+
+**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
+
+{% endnote %}
+
+Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code snippets assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens) to avoid hitting rate limits. The PAT does not need any scopes/permissions.
+
+{% note %}
+
+**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
+
+{% endnote %}
 
 **Sample message sent to verify endpoint**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Validation sample in Go**
@@ -123,14 +129,14 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
   // Fetch the list of GitHub Public Keys
-  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
     fmt.Printf("Error preparing request: %s\n", err)
     os.Exit(1)
@@ -242,16 +248,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -357,4 +363,3 @@ A few important points:
 **Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
 {% endnote %}
-
diff --git a/translations/ru-RU/content/developers/overview/using-ssh-agent-forwarding.md b/translations/ru-RU/content/developers/overview/using-ssh-agent-forwarding.md
index 030b2a7855..45574b6bcc 100644
--- a/translations/ru-RU/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/ru-RU/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-On Mac OS X, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
+On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/ru-RU/content/developers/overview/viewing-deployment-history.md b/translations/ru-RU/content/developers/overview/viewing-deployment-history.md
index 5d9f721581..64085f3187 100644
--- a/translations/ru-RU/content/developers/overview/viewing-deployment-history.md
+++ b/translations/ru-RU/content/developers/overview/viewing-deployment-history.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% data reusables.actions.environments-beta %}
diff --git a/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md b/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md
index 4eea773712..fa7ca33119 100644
--- a/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ The event objects returned from the Events API endpoints have the same structure
 This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events).
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
diff --git a/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index 968121fdfe..1880038f1e 100644
--- a/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -61,7 +61,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 #### Example delivery
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -200,7 +200,9 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 
 Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment.
 
-Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event.
+#### Availability
+
+- {% data variables.product.prodname_github_app %}s with the `content_references:write` permission
 
 #### Webhook payload example
 
@@ -400,7 +402,7 @@ Activity related to a comment in a discussion. For more information, see "[Using
 
 #### Availability
 
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/v3/enterprise-admin/global_webhooks/)."
+- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
 
 #### Webhook payload object
 
@@ -720,7 +722,7 @@ The webhook this event is configured on was deleted. This event will only listen
 #### Availability
 
 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
-- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/v3/enterprise-admin/global_webhooks/).{% endif %}
+- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %}
 - Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events
 - {% data variables.product.prodname_github_app %}s with the `members` permission
 
@@ -801,10 +803,10 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
 
 #### Webhook payload object
 
-| Клавиша | Тип       | Description                                                                       |
-| ------- | --------- | --------------------------------------------------------------------------------- |
-| `id`    | `integer` | The unique identifier of the page build.                                          |
-| `build` | `объект`  | The [List GitHub Pages builds](/v3/repos/pages/#list-github-pages-builds) itself. |
+| Клавиша | Тип       | Description                                                                            |
+| ------- | --------- | -------------------------------------------------------------------------------------- |
+| `id`    | `integer` | The unique identifier of the page build.                                               |
+| `build` | `объект`  | The [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) itself. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
@@ -1010,12 +1012,6 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% endnote %}
 
-{% tip %}
-
-**Note**: The webhook payload example following the table differs significantly from the Events API payload described in the table. Among other differences, the webhook payload includes both `sender` and `pusher` objects. Sender and pusher are the same user who initiated the `push` event, but the `sender` object contains more detail.
-
-{% endtip %}
-
 #### Availability
 
 - Repository webhooks
@@ -1206,7 +1202,7 @@ Activity related to a security advisory. A security advisory provides informatio
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
+You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)".
 
 #### Availability
 
@@ -1338,7 +1334,7 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_
 When a user is `created` or `deleted`.
 
 #### Availability
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/v3/enterprise-admin/global_webhooks/)."
+- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
 
 #### Webhook payload example
 
diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 5f544bee18..55e913beee 100644
--- a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
 
-In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)."
+In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji.
 
 You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."
 
diff --git a/translations/ru-RU/content/discussions/index.md b/translations/ru-RU/content/discussions/index.md
index 9974eb20a2..3c52fee2cf 100644
--- a/translations/ru-RU/content/discussions/index.md
+++ b/translations/ru-RU/content/discussions/index.md
@@ -34,24 +34,3 @@ versions:
 <!-- {% link_with_intro /discussions-guides %} -->
 <!-- {% link_with_intro /collaborating-with-your-community-using-discussions %} -->
 <!-- {% link_with_intro /managing-discussions-for-your-community %} -->
-
-<!-- Community examples -->
-{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %}
-{% if discussionsCommunityExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">Communities using discussions</h2>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render discussions-community-card for discussionsCommunityExamples as example %}
-  </div>
-  {% if discussionsCommunityExamples.length > 6 %}
-    <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">Show more {% octicon "arrow-right" %}</button>
-  {% endif %}
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">Sorry, there is no result for <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/discussions_community_examples.yml">Add your community {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md
index f4245ea672..0afca8a7e5 100644
--- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md
+++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md
@@ -1,7 +1,7 @@
 ---
 title: Integrate GitHub Classroom with an IDE
 shortTitle: Integrate with an IDE
-intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}.
+intro: 'You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}.'
 mapTopic: true
 versions:
   free-pro-team: '*'
diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md
index bca1150346..cd2024f9f8 100644
--- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md
+++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md
@@ -1,6 +1,6 @@
 ---
 title: Learn with GitHub Classroom
-intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher.
+intro: 'You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher.'
 mapTopic: true
 versions:
   free-pro-team: '*'
diff --git a/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md b/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md
index 6533a3ec45..e0fef6467a 100644
--- a/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md
+++ b/translations/ru-RU/content/github/administering-a-repository/about-merge-methods-on-github.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.pull_requests.configure_pull_request_merges_intro %} You can enforce one type of merge method, such as commit squashing or rebasing, by only enabling the desired method for your repository.
diff --git a/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md b/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md
index a50cef4cda..0059a6cc9e 100644
--- a/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md
@@ -20,7 +20,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About branch protection rules
@@ -47,6 +47,8 @@ For each branch protection rule, you can choose to enable or disable the followi
 - [Allow force pushes](#allow-force-pushes)
 - [Allow deletions](#allow-deletions)
 
+For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+
 #### Require pull request reviews before merging
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
@@ -100,7 +102,15 @@ When you enable required commit signing on a branch, contributors {% if currentV
 
 {% note %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+**Замечания:**
+
+* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+
+{% else %}
 **Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+{% endif %}
 
 {% endnote %}
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/about-releases.md b/translations/ru-RU/content/github/administering-a-repository/about-releases.md
index a79cf91973..f5de482d4e 100644
--- a/translations/ru-RU/content/github/administering-a-repository/about-releases.md
+++ b/translations/ru-RU/content/github/administering-a-repository/about-releases.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About releases
diff --git a/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md b/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md
index ddd74ba113..b45b302e6e 100644
--- a/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/ru-RU/content/github/administering-a-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ You can choose the default branch for a repository. The default branch is the ba
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
 You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/classifying-your-repository-with-topics.md b/translations/ru-RU/content/github/administering-a-repository/classifying-your-repository-with-topics.md
index 3d211640c6..9a1cd65fa1 100644
--- a/translations/ru-RU/content/github/administering-a-repository/classifying-your-repository-with-topics.md
+++ b/translations/ru-RU/content/github/administering-a-repository/classifying-your-repository-with-topics.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About topics
diff --git a/translations/ru-RU/content/github/administering-a-repository/comparing-releases.md b/translations/ru-RU/content/github/administering-a-repository/comparing-releases.md
index 096c2f6092..28c3d93c99 100644
--- a/translations/ru-RU/content/github/administering-a-repository/comparing-releases.md
+++ b/translations/ru-RU/content/github/administering-a-repository/comparing-releases.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md b/translations/ru-RU/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md
index 7841e59b68..eb511e86c2 100644
--- a/translations/ru-RU/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md
+++ b/translations/ru-RU/content/github/administering-a-repository/configuring-autolinks-to-reference-external-resources.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests,{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} commit messages, and release descriptions{% else %} and commit messages{% endif %} to external third-party services.
diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md b/translations/ru-RU/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md
index 34fd8b7ae4..f46b683a3a 100644
--- a/translations/ru-RU/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md
+++ b/translations/ru-RU/content/github/administering-a-repository/configuring-commit-rebasing-for-pull-requests.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.pull_requests.configure_pull_request_merges_intro %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-pull-request-merges.md b/translations/ru-RU/content/github/administering-a-repository/configuring-pull-request-merges.md
index 4f05c5af5a..33ec61095b 100644
--- a/translations/ru-RU/content/github/administering-a-repository/configuring-pull-request-merges.md
+++ b/translations/ru-RU/content/github/administering-a-repository/configuring-pull-request-merges.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md
index 309dca088f..1cd2ba3993 100644
--- a/translations/ru-RU/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '>=2.23'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.actions.about-artifact-log-retention %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md b/translations/ru-RU/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md
index beb609f0db..e909840eca 100644
--- a/translations/ru-RU/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md
+++ b/translations/ru-RU/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Until you add an image, repository links expand to show basic information about the repository and the owner's avatar. Adding an image to your repository can help identify your project across various social platforms.
diff --git a/translations/ru-RU/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md b/translations/ru-RU/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md
index 584181f842..c99db74dee 100644
--- a/translations/ru-RU/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md
+++ b/translations/ru-RU/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests.md
@@ -12,6 +12,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/deleting-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/deleting-a-repository.md
index 2e417ee1f5..96f072c487 100644
--- a/translations/ru-RU/content/github/administering-a-repository/deleting-a-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/deleting-a-repository.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.organizations.owners-and-admins-can %} delete an organization repository. If **Allow members to delete or transfer repositories for this organization** has been disabled, only organization owners can delete organization repositories. {% data reusables.organizations.new-repo-permissions-more-info %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index 36eef2ec21..1f9fff8095 100644
--- a/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -82,3 +82,21 @@ You can disable all workflows for a repository or set a policy that configures w
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your repository
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. Click **Save** to apply the settings.
+{% endif %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index 4590ddb400..8a92008282 100644
--- a/translations/ru-RU/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### About FUNDING files
 
-You can configure your sponsor button by editing a _FUNDING.yml_ file in your repository's `.github` folder, on the default branch. You can configure the button to include sponsored developers in {% data variables.product.prodname_sponsors %}, external funding platforms, or a custom funding URL. For more information about {% data variables.product.prodname_sponsors %}, see "[About GitHub Sponsors](/articles/about-github-sponsors)."
+You can configure your sponsor button by editing a _FUNDING.yml_ file in your repository's `.github` folder, on the default branch. You can configure the button to include sponsored developers in {% data variables.product.prodname_sponsors %}, external funding platforms, or a custom funding URL. For more information about {% data variables.product.prodname_sponsors %}, see "[About GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
 
 You can add one username, package name, or project name per external funding platform and up to four custom URLs. You can add up to four sponsored developers or organizations in {% data variables.product.prodname_sponsors %}. Add each platform on a new line, using the following syntax:
 
@@ -76,5 +76,5 @@ Anyone with admin permissions can enable a sponsor button in a repository.
 {% data reusables.files.propose_new_file %}
 
 ### Дополнительная литература
-- "[About {% data variables.product.prodname_sponsors %} for open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
 - "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/linking-to-releases.md b/translations/ru-RU/content/github/administering-a-repository/linking-to-releases.md
index e4bd7f9a9b..962b1340f2 100644
--- a/translations/ru-RU/content/github/administering-a-repository/linking-to-releases.md
+++ b/translations/ru-RU/content/github/administering-a-repository/linking-to-releases.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md b/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md
index 6084347758..ab8a7fbf30 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-a-branch-protection-rule.md
@@ -22,7 +22,7 @@ versions:
   github-ae: '*'
 permissions: People with admin permissions to a repository can manage branch protection rules.
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About branch protection rules
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
index 708fb360ee..704587a28d 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -8,7 +8,7 @@ versions:
   github-ae: '*'
 permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository.
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About auto-merge
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-branches-in-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-branches-in-your-repository.md
index c59c70f2b2..6b61dddaa7 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-branches-in-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-branches-in-your-repository.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md
index 2e45a26eb9..1d6642a5fd 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '>3.0'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About {% data variables.large_files.product_name_short %} objects in archives
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-repository-settings.md b/translations/ru-RU/content/github/administering-a-repository/managing-repository-settings.md
index d62b9d82b2..df0cc523ea 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-repository-settings.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-repository-settings.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index 0a896acbd8..6576016169 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -35,10 +35,11 @@ You can manage the security and analysis features for your {% if currentVersion
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. The control for "
+{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% if currentVersion == "free-pro-team@latest" %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
 **Note:** If you disable
 
@@ -46,11 +47,11 @@ You can manage the security and analysis features for your {% if currentVersion
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
 4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. Before you can enable "
-{% data variables.product.prodname_secret_scanning %}" for your repository, you need to enable {% data variables.product.prodname_GH_advanced_security %}.
+{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.
    ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index b1f6fc6d3f..a905b8de3e 100644
--- a/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ For more information about repository permission levels, see "[Permission levels
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Trashcan icon for removing access](/assets/images/help/repository/manage-access-remove.png)
+4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trash" aria-label="The trash icon" %}. ![trash icon for removing access](/assets/images/help/repository/manage-access-remove.png)
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/releasing-projects-on-github.md b/translations/ru-RU/content/github/administering-a-repository/releasing-projects-on-github.md
index 0ee087417a..f131b29302 100644
--- a/translations/ru-RU/content/github/administering-a-repository/releasing-projects-on-github.md
+++ b/translations/ru-RU/content/github/administering-a-repository/releasing-projects-on-github.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md b/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md
index 190210ca02..9f56a37283 100644
--- a/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/ru-RU/content/github/administering-a-repository/renaming-a-branch.md
@@ -6,7 +6,7 @@ versions:
   free-pro-team: '*'
   enterprise-server: '>=3.2'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About renaming branches
@@ -17,6 +17,8 @@ When you rename a branch on {% data variables.product.product_location %}, any U
 
 Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
 
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+
 ### Renaming a branch
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -35,4 +37,10 @@ From the local clone of the repository on a computer, run the following commands
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+Optionally, run the following command to remove tracking references to the old branch name.
+```
+$ git remote prune origin
 ```
diff --git a/translations/ru-RU/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/ru-RU/content/github/administering-a-repository/restoring-a-deleted-repository.md
index 56b11eb70e..5ed98371be 100644
--- a/translations/ru-RU/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -31,9 +31,9 @@ Restoring a repository will not restore release attachments or team permissions.
 
 ### Restoring a deleted repository that was owned by an organization
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md
index 357d9148e6..f9b0e1946a 100644
--- a/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/administering-a-repository/transferring-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/transferring-a-repository.md
index 34d3eff514..47eada135d 100644
--- a/translations/ru-RU/content/github/administering-a-repository/transferring-a-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/transferring-a-repository.md
@@ -17,7 +17,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About repository transfers
diff --git a/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md b/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md
index 06da317419..39a89440a9 100644
--- a/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md
+++ b/translations/ru-RU/content/github/administering-a-repository/troubleshooting-required-status-checks.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)."
diff --git a/translations/ru-RU/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index 784b0396ae..78c6de87f2 100644
--- a/translations/ru-RU/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/ru-RU/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ You can also see deployment information on the "Conversation" tab of a pull requ
 ### Viewing the deployments dashboard
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### Дополнительная литература
  - "[About pull requests](/articles/about-pull-requests)"
diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/ru-RU/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..4fc52cf3c6
--- /dev/null
+++ b/translations/ru-RU/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Troubleshooting issues with Camo
+
+In rare circumstances, images that are processed through Camo might not appear on {% data variables.product.prodname_dotcom %}. Here are some steps you can take to determine where the problem lies.
+
+{% windows %}
+
+{% tip %}
+
+Windows users will either need to use the Git Powershell (which is installed alongside [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) or download [curl for Windows](http://curl.haxx.se/download.html).
+
+{% endtip %}
+
+{% endwindows %}
+
+#### An image is not showing up
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Request the image headers using `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. Check the value of `Content-Type`. In this case, it's `image/x-png`.
+4. Check that content type against [the list of types supported by Camo](https://github.com/atmos/camo/blob/master/mime-types.json).
+
+If your content type is not supported by Camo, you can try several actions:
+  * If you own the server that's hosting the image, modify it so that it returns a correct content type for images.
+  * If you're using an external service for hosting images, contact support for that service.
+  * Make a pull request to Camo to add your content type to the list.
+
+#### An image that changed recently is not updating
+
+If you changed an image recently and it's showing up in your browser but not {% data variables.product.prodname_dotcom %}, you can try resetting the cache of the image.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Request the image headers using `curl`.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+Check the value of `Cache-Control`. In this example, there's no `Cache-Control`. In that case:
+  * If you own the server that's hosting the image, modify it so that it returns a `Cache-Control` of `no-cache` for images.
+  * If you're using an external service for hosting images, contact support for that service.
+
+ If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
+
+#### Removing an image from Camo's cache
+
+Purging the cache forces every {% data variables.product.prodname_dotcom %} user to re-request the image, so you should use it very sparingly and only in the event that the above steps did not work.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Purge the image using `curl -X PURGE` on the Camo URL.
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### Viewing images on private networks
+
+If an image is being served from a private network or from a server that requires authentication, it can't be viewed by {% data variables.product.prodname_dotcom %}. In fact, it can't be viewed by any user without asking them to log into the server.
+
+To fix this, please move the image to a service that is publicly available.
+
+### Дополнительная литература
+
+- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md
index 635451a908..61ac0ec4eb 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -1,6 +1,6 @@
 ---
 title: About commit signature verification
-intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can trust that the changes come from a trusted source.'
+intro: 'Using GPG or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures/
   - /articles/about-gpg/
@@ -16,15 +16,35 @@ topics:
 
 ### About commit signature verification
 
-You can sign commits and tags locally, so other people can verify that your work comes from a trusted source. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag as verified.
+You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% if currentVersion == "free-pro-team@latest" %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
 
 ![Verified commit](/assets/images/help/commits/verified-commit.png)
 
-If a commit or tag has a signature that cannot be verified, {% data variables.product.product_name %} marks the commit or tag as unverified.
+{% if currentVersion == "free-pro-team@latest" %}
+Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+#### Default statuses
+
+| Состояние              | Description                                                       |
+| ---------------------- | ----------------------------------------------------------------- |
+| **Verified**           | The commit is signed and the signature was successfully verified. |
+| **Unverified**         | The commit is signed but the signature could not be verified.     |
+| No verification status | The commit is not signed.                                         |
+
+#### Statuses with vigilant mode enabled
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+If a commit or tag has a signature that can't be verified,
+{% data variables.product.product_name %} marks the commit or tag "Unverified."
+{% endif %}
 
 Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."
 
-You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see "[Checking your commit and tag signature verification status](/articles/checking-your-commit-and-tag-signature-verification-status)."
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."
diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-ssh.md b/translations/ru-RU/content/github/authenticating-to-github/about-ssh.md
index 0e5e6c3e1b..59e3e9f042 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-When you set up SSH, you'll [generate an SSH key and add it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and then [add the key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). Adding the SSH key to the ssh-agent ensures that your SSH key has an extra layer of security through the use of a passphrase. For more information, see "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
+When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
-{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you'll need to authorize it first. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %}
+You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
 
-We recommend that you regularly [review your SSH keys list](/articles/reviewing-your-ssh-keys) and revoke any that are invalid or have been compromised.
+{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %}
+
+To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. For more information, see "[Reviewing your SSH keys](/github/authenticating-to-github/reviewing-your-ssh-keys)."
 
 {% if currentVersion == "free-pro-team@latest" %}
 If you haven't used your SSH key for a year, then
@@ -28,8 +30,4 @@ If you're a member of an organization that provides SSH certificates, you can us
 
 - "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
 - "[Testing your SSH connection](/articles/testing-your-ssh-connection)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
 - "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
-{%- if currentVersion == "free-pro-team@latest" %}
-- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"
-{%- endif %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index ad4e139c2a..88ae40f6d3 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also add an SSH key using the {% data variables.product.prodname_cli %}. For more information, see "[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. Copy the SSH public key to your clipboard.
@@ -80,6 +88,7 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc
   If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace.
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
   # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md b/translations/ru-RU/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md
index bd089ba9e7..1a11bd78a4 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md
@@ -10,6 +10,6 @@ versions:
   free-pro-team: '*'
   github-ae: '*'
 topics:
-  - sso
+  - SSO
 ---
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index bf72a6c451..04676c38b6 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**Note:** GPG does not come installed by default on OS X or Windows. To install GPG command line tools, see [GnuPG's Download page](https://www.gnupg.org/download/).
+**Note:** GPG does not come installed by default on macOS or Windows. To install GPG command line tools, see [GnuPG's Download page](https://www.gnupg.org/download/).
 
 {% endnote %}
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md b/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md
index 1131f1f04e..6406f844c5 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/checking-for-existing-ssh-keys.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 {% data reusables.ssh.dsa-support %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/ru-RU/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index 5f594b2163..a991a1fc8e 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %}, navigate to your pull request.
 {% data reusables.repositories.review-pr-commits %}
-3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified or unverified. ![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. To view more detailed information about the commit signature, click **Verified** or **Unverified**. ![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-If your commit signature is unverified, you can learn more about why by clicking the **Unverified** box. ![Unverified signed commit](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. To view more detailed information about the commit signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### Checking your tag signature verification status
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. At the top of the Releases page, click **Tags**. ![Tags page](/assets/images/help/releases/tags-list.png)
-3. Next to your tag description, there is a box that shows whether your tag signature is verified or unverified. ![verified tag signature](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. To view more detailed information about the tag signature, click **Verified** or **Unverified**. If your tag signature is unverified, you can learn more about why by clicking the **Unverified** box. ![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. Next to your tag description, there is a box that shows whether your tag signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![verified tag signature](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. To view more detailed information about the tag signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/connecting-to-github-with-ssh.md b/translations/ru-RU/content/github/authenticating-to-github/connecting-to-github-with-ssh.md
index 09ce32816e..4a3ac9116d 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/connecting-to-github-with-ssh.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/connecting-to-github-with-ssh.md
@@ -16,6 +16,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md
index 243647ba3a..2e2f7903f3 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
 
-{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### Creating a token
 
-{% if currentVersion == "free-pro-team@latest" %}1. [Verify your email address](/articles/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -45,13 +45,13 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
    {% else %}
    ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **Warning:** Treat your tokens like passwords and keep them secret. When working with the API, use tokens as environment variables instead of hardcoding them into your programs.
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
 
 ### Using a token on the command line
 
@@ -59,7 +59,7 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
 
 Personal access tokens can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
 
-If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/articles/updating-credentials-from-the-osx-keychain) to replace your old password with the token.
+If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md b/translations/ru-RU/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md
index 2d62415729..2c8539a6ac 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/deleted-or-missing-ssh-keys.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 {% data variables.product.prodname_dotcom %} automatically deletes inactive SSH keys to help keep accounts safe, such as after someone leaves a job or loses a computer.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/ru-RU/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..47895a80cd
--- /dev/null
+++ b/translations/ru-RU/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
+
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### Enabling vigilant mode
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md b/translations/ru-RU/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md
index 0a0cf75aaf..fcc1145e8c 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-agent-admitted-failure-to-sign.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-key-already-in-use.md b/translations/ru-RU/content/github/authenticating-to-github/error-key-already-in-use.md
index 91003389a0..84627b43f9 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-key-already-in-use.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-key-already-in-use.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 ### Finding where the key has been used
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md b/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md
index 2a422a7406..d7cc357eba 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md
@@ -40,7 +40,7 @@ All connections, including those for remote URLs, must be made as the "git" user
 $ ssh -T <em>GITHUB-USERNAME</em>@{% data variables.command_line.codeblock %}
 > Permission denied (publickey).
 ```
-If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/articles/changing-a-remote-s-url/).
+If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/github/getting-started-with-github/managing-remote-repositories).
 
 You should verify your connection by typing:
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md b/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md
index 51660edaec..76e938d8c5 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 To fix this, the owner of the repository (`user`) needs to add your account (`other-user`) as a collaborator on the repository or to a team that has write access to the repository.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md b/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md
index 818e7dc717..c8fd97faac 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 To fix this, remove the deploy key from the repository, and [add the key to your user account](/articles/adding-a-new-ssh-key-to-your-github-account) instead.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md b/translations/ru-RU/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md
index 40152673d0..0e4528be3a 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 The error you receive may look like the following:
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/ru-RU/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..9062a049cd
--- /dev/null
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### Требования
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### Solving the issue
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. Open Terminal.
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md b/translations/ru-RU/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md
index fadb01e5fd..7165fac8a4 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/error-were-doing-an-ssh-key-audit.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 When using an unverified key to perform Git operations, you will be prompted to perform an audit of your SSH keys.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ru-RU/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index a52198b84a..a6af547b36 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-If you don't already have an SSH key, you must [generate a new SSH key](#generating-a-new-ssh-key). If you're unsure whether you already have an SSH key, check for [existing keys](/articles/checking-for-existing-ssh-keys).
+### About SSH key generation
 
-If you don't want to reenter your passphrase every time you use your SSH key, you can [add your key to the SSH agent](#adding-your-ssh-key-to-the-ssh-agent), which manages your SSH keys and remembers your passphrase.
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
 
 ### Generating a new SSH key
 
@@ -62,7 +69,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
 
   {% endlinux %}
 
-4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases).
+4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
 
 ### Adding your SSH key to the ssh-agent
 
-Before adding a new SSH key to the ssh-agent to manage your keys, you should have [checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) and [generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). <span class="platform-mac">When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source.</span>
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source.</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
       $ touch ~/.ssh/config
       ```
 
-    * Open your `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` if you are not using the default location and name for your `id_ed25519` key.
+    * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
 
       ```
       Host *
@@ -106,6 +113,25 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **Note:** If you see an error like this
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      add an additional config line to your `Host *` section:
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
   {% endnote %}
 
-4. [Add the SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Add the SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  In some Linux environments, you need root access to run the command:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [Add the SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endif %}
+
 ### Дополнительная литература
 
 - "[About SSH](/articles/about-ssh)"
diff --git a/translations/ru-RU/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md b/translations/ru-RU/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md
index 6b47b5874f..5dc5de38e7 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md
@@ -8,8 +8,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
 These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
diff --git a/translations/ru-RU/content/github/authenticating-to-github/index.md b/translations/ru-RU/content/github/authenticating-to-github/index.md
index d59e1b78c4..c29fb47c03 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/index.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/index.md
@@ -19,10 +19,10 @@ versions:
   github-ae: '*'
 topics:
   - 2fa
-  - identity
-  - access management
-  - usernames
-  - device verification
+  - Identity
+  - Access management
+  - Usernames
+  - Device verification
 ---
 
 
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md b/translations/ru-RU/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md
index f2cceaccef..f52428bb90 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/keeping-your-account-and-data-secure.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/ru-RU/content/github/authenticating-to-github/managing-commit-signature-verification.md
index 1402793ca0..1888924c82 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/managing-commit-signature-verification.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/managing-commit-signature-verification.md
@@ -11,7 +11,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/preventing-unauthorized-access.md b/translations/ru-RU/content/github/authenticating-to-github/preventing-unauthorized-access.md
index 80cf7fc056..15c3908111 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/preventing-unauthorized-access.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/preventing-unauthorized-access.md
@@ -7,8 +7,8 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
 {% data variables.product.product_name %} requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ru-RU/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index d973b5cf4d..1725331e55 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ You can use your two-factor authentication credentials or two-factor authenticat
 5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent. ![One-time password field](/assets/images/help/2fa/one-time-password-field.png)
 6. Click **Verify email address**.
 7. Choose an alternative verification factor.
-    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify this device**.
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
     - 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**. ![Alternative verification buttons](/assets/images/help/2fa/alt-verifications.png)
 8. A member of {% data variables.contact.github_support %} will review your request and email you within 3-5 business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/ru-RU/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index a64ceb78cd..6338e180d8 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -10,12 +10,12 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 {% mac %}
 
-If you [configured your SSH passphrase with the OS X Keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
 
 1. In Finder, search for the **Keychain Access** app. ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
 2. In Keychain Access, search for **SSH**.
diff --git a/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-deploy-keys.md b/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-deploy-keys.md
index f9df701974..56e9299933 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-deploy-keys.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-deploy-keys.md
@@ -8,8 +8,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md
index 5ace91d0b1..b2689d5fc5 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/reviewing-your-security-log.md
@@ -38,23 +38,23 @@ The security log lists all actions performed within the last 90 days{% if curren
 
 The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
 
-| Category name                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %}
-| [`account_recovery_token`](#account_recovery_token-category-actions)                   | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                |
-| [`выставление счетов`](#billing-category-actions)                                      | Contains all activities related to your billing information.                                                                                                                                                                                                                                                                                                                                                                   |
-| [`codespaces`](#codespaces-category-actions)                                           | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."                                                                                                                                                                                         |
-| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.                                                                                                                                                                                                                                                                                                          |
+| Category name                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| [`account_recovery_token`](#account_recovery_token-category-actions)                   | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods).                                                                                                                                                                                                                                                                                                                                     |
+| [`выставление счетов`](#billing-category-actions)                                      | Contains all activities related to your billing information.                                                                                                                                                                                                                                                                                                                                                                                                        |
+| [`codespaces`](#codespaces-category-actions)                                           | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."                                                                                                                                                                                                                              |
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.                                                                                                                                                                                                                                                                                                                                               |
 | [`marketplace_listing`](#marketplace_listing-category-actions)                         | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
 | [`oauth_access`](#oauth_access-category-actions)                                       | Contains all activities related to [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) you've connected with.{% if currentVersion == "free-pro-team@latest" %}
 | [`payment_method`](#payment_method-category-actions)                                   | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %}
-| [`profile_picture`](#profile_picture-category-actions)                                 | Contains all activities related to your profile picture.                                                                                                                                                                                                                                                                                                                                                                       |
-| [`проект`](#project-category-actions)                                                  | Contains all activities related to project boards.                                                                                                                                                                                                                                                                                                                                                                             |
-| [`public_key`](#public_key-category-actions)                                           | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                              |
+| [`profile_picture`](#profile_picture-category-actions)                                 | Contains all activities related to your profile picture.                                                                                                                                                                                                                                                                                                                                                                                                            |
+| [`проект`](#project-category-actions)                                                  | Contains all activities related to project boards.                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| [`public_key`](#public_key-category-actions)                                           | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                                                                   |
 | [`repo`](#repo-category-actions)                                                       | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %}
-| [`sponsors`](#sponsors-category-actions)                                               | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+| [`sponsors`](#sponsors-category-actions)                                               | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 | [`команда`](#team-category-actions)                                                    | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %}
 | [`two_factor_authentication`](#two_factor_authentication-category-actions)             | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
-| [`пользователь`](#user-category-actions)                                               | Contains all activities related to your account.                                                                                                                                                                                                                                                                                                                                                                               |
+| [`пользователь`](#user-category-actions)                                               | Contains all activities related to your account.                                                                                                                                                                                                                                                                                                                                                                                                                    |
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -90,6 +90,10 @@ An overview of some of the most common actions that are recorded as events in th
 
 | Действие                             | Description                                                                                                                                                                                                              |
 | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create`                             | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                 |
+| `resume`                             | Triggered when you resume a suspended codespace.                                                                                                                                                                         |
+| `delete - Удалить`                   | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                 |
+| `manage_access_and_security`         | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                           |
 | `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). |
 
 #### `marketplace_agreement_signature` category actions
@@ -181,22 +185,24 @@ An overview of some of the most common actions that are recorded as events in th
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` category actions
 
-| Действие                                      | Description                                                                                                                                                                                                                                                                                                              |
-| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`             | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                              |
-| `repo_funding_links_file_action`              | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                         |
-| `sponsor_sponsorship_cancel`                  | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                         |
-| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                           |
-| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/articles/managing-your-sponsorship)")                                                                                                                                                          |
-| `sponsor_sponsorship_tier_change`             | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                     |
-| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                     |
-| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                      |
-| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                   |
-| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
-| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
-| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)")                                                                                                                                                                                          |
-| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")    |
-| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                       |
+| Действие                                      | Description                                                                                                                                                                                                                                                                                                     |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                |
+| `repo_funding_links_file_action`              | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                |
+| `sponsor_sponsorship_cancel`                  | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                |
+| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                             |
+| `sponsor_sponsorship_tier_change`             | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                            |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                      |
+| `sponsored_developer_disable`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled                                                                                                                                                                                                                          |
+| `sponsored_developer_redraft`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                   |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
+| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                                  |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                                       |
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -258,4 +264,3 @@ An overview of some of the most common actions that are recorded as events in th
 | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `обновление` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." |
 | `destroy`    | Triggered when you clear the status on your profile.                                                                                                                 |
-
diff --git a/translations/ru-RU/content/github/authenticating-to-github/testing-your-ssh-connection.md b/translations/ru-RU/content/github/authenticating-to-github/testing-your-ssh-connection.md
index 167a477bb5..0b23421c06 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/testing-your-ssh-connection.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/testing-your-ssh-connection.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 Before testing your SSH connection, you should have:
diff --git a/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md b/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md
index ae4ef0099e..74febb6bab 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-commit-signature-verification.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-ssh.md b/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-ssh.md
index a7d35a006e..217db4af50 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-ssh.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/troubleshooting-ssh.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/ru-RU/content/github/authenticating-to-github/updating-your-github-access-credentials.md
index d0efb6c7f8..e10bc0219e 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/updating-your-github-access-credentials.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/updating-your-github-access-credentials.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - identity
-  - access management
+  - Identity
+  - Access management
 ---
 
 {% if currentVersion != "github-ae@latest" %}
diff --git a/translations/ru-RU/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/ru-RU/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index 3acbcec275..197845d34c 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -6,12 +6,12 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - ssh
+  - SSH
 ---
 
 {% tip %}
 
-**GitHub Enterprise users**: Accessing GitHub Enterprise via SSH over the HTTPS port is currently not supported.
+**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
 
 {% endtip %}
 
diff --git a/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index f7144c0dba..e1ccbf39a0 100644
--- a/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/ru-RU/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -89,7 +89,7 @@ The `ssh-agent` process will continue to run until you log out, shut down your c
 
 ### Saving your passphrase in the keychain
 
-On OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
+On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index b565aa18b4..2073de2dea 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: About collaborative development models
-intro: The way you use pull requests depends on the type of development model you use in your project.
+intro: The way you use pull requests depends on the type of development model you use in your project. You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-There are two main types of development models with which you'd use pull requests. In the *fork and pull model*, anyone can fork an existing repository and push changes to their personal fork. You do not need permission to the source repository to push to a user-owned fork. The changes can be pulled into the source repository by the project maintainer. When you open a pull request proposing changes from your user-owned fork to a branch in the source (upstream) repository, you can allow anyone with push access to the upstream repository to make changes to your pull request.  This model is popular with open source projects as it reduces the amount of friction for new contributors and allows people to work independently without upfront coordination.
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. You do not need permission to the source repository to push to a user-owned fork. The changes can be pulled into the source repository by the project maintainer. When you open a pull request proposing changes from your user-owned fork to a branch in the source (upstream) repository, you can allow anyone with push access to the upstream repository to make changes to your pull request.  This model is popular with open source projects as it reduces the amount of friction for new contributors and allows people to work independently without upfront coordination.
 
 {% tip %}
 
@@ -20,7 +22,9 @@ There are two main types of development models with which you'd use pull request
 
 {% endtip %}
 
-In the *shared repository model*, collaborators are granted push access to a single shared repository and topic branches are created when changes need to be made. Pull requests are useful in this model as they initiate code review and general discussion about a set of changes before the changes are merged into the main development branch. This model is more prevalent with small teams and organizations collaborating on private projects.
+### Shared repository model
+
+In the shared repository model, collaborators are granted push access to a single shared repository and topic branches are created when changes need to be made. Pull requests are useful in this model as they initiate code review and general discussion about a set of changes before the changes are merged into the main development branch. This model is more prevalent with small teams and organizations collaborating on private projects.
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index cf4fb304a9..0e5d20d58e 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 Status checks are based on external processes, such as continuous integration builds, which run for each push you make to a repository. You can see the *pending*, *passing*, or *failing* state of status checks next to individual commits in your pull request.
@@ -53,18 +53,18 @@ When a repository is set to automatically request checks for pushes, you can cho
 
 To skip or request checks for your commit, add one of the following trailer lines to the end of your commit message:
 
-- To _skip checks_ for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines followed by `skip-checks: true`:
+- To _skip checks_ for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - To _request_ checks for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines followed by `request-checks: true`:
+- To _request_ checks for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md
index bc9829b98f..64ecc3d0d4 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
index 063b7b8993..a363f9db48 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '>=3.1'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 ### About auto-merge
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 28f738d58f..c9984c8d90 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. In the "Pull requests" list, click the pull request you'd like to mark as ready for review.
 3. In the merge box, click **Ready for review**. ![Ready for review button](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index 28eba535f3..39f341c177 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
   {% note %}
@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Modifying an active pull request locally
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md
index 56936a04eb..d01784b019 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% tip %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md
index 1d4bdbd223..651ddfa20c 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index fe22396081..f3ebbf72f4 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ To reply to an existing line comment, you'll need to navigate to the comment on
 
 **Советы:**
 - Pull request comments support the same [formatting](/categories/writing-on-github) as regular comments on {% data variables.product.product_name %}, such as @mentions, emoji, and references.
-- You can [add reactions](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) to comments in pull requests in the **Files changed** tab.
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md
index ed2a4c2f42..bce7a45e72 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index aeeda09453..56157540da 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -19,6 +19,14 @@ You can specify which branch you'd like to merge your changes into when you crea
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Changing the branch range and destination repository
 
 By default, pull requests are based on the parent repository's [default branch](/articles/setting-the-default-branch). For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index 07f5b29ad1..f156988d2e 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ If the branch you want to delete is associated with an open pull request, you mu
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. Scroll to the branch that you want to delete, then click {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![delete the branch](/assets/images/help/branches/branches-delete.png)
+1. Scroll to the branch that you want to delete, then click {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![delete the branch](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..4db7e09bc4
--- /dev/null
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: Getting started
+shortTitle: Getting started
+intro: 'Learn about the {% data variables.product.prodname_dotcom %} flow and different ways to collaborate on and discuss your projects.'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md
index d6d564c409..b4ad8adda2 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md
index 51e6d15485..1289052f0f 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Collaborating with issues and pull requests
-intro: 'Use the {% data variables.product.prodname_dotcom %} flow to track and discuss changes in issues, then propose and review changes in pull requests.'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -12,16 +12,15 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 
 ### Table of Contents
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index 2102f95145..623f3bd82a 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ You can't merge a draft pull request. For more information about draft pull requ
 
 If you decide you don't want the changes in a topic branch to be merged to the upstream branch, you can [close the pull request](/articles/closing-a-pull-request) without merging.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### Merging a pull request on {% data variables.product.prodname_dotcom %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md
index ac36b0b4a7..697ebb4dda 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md
index efe90d1598..bcefb8b9f8 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..a1292048c3
--- /dev/null
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### Introduction
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### Вопросы
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### Pull requests
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### Team discussions
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion.
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### Дальнейшие шаги
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md
index 82c9fa85d6..d4ba747958 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 ### About reverting a pull request
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md
index f0b03a1aae..7829d761b1 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index a99cf4a417..af78b5f0a2 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -4,7 +4,7 @@ intro: 'If a pull request contains changes to dependencies, you can view a summa
 versions:
   free-pro-team: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Sign up for the dependency review beta" and "Reviewing dependency changes in a pull request".-->
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
index 939b9a7cb2..ae1cc2cbe3 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/articles/configuring-a-remote-for-a-fork) in Git.
diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md
index 0fca472b8f..5035195ad8 100644
--- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md
+++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/working-with-forks.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md
index 2df075cbef..0228316d83 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### Persistence of public repositories
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index 86409e9769..e7a0cbf114 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
 
 {% endif %}
 
+### Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+The auto-generated table of contents is enabled by default for all Markdown files in a repository, but you can disable this feature for your repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under "Features", deselect **Table of contents**. ![Automatic TOC setting for repositories](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### Section links in README files and blob pages
 
-Many projects use a table of contents at the start of a README to direct users to different sections of the file. {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### Relative links and image paths in README files
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md
index edc0500dfe..7b10bab44c 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md
@@ -13,7 +13,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md
index dabd0a63d6..930187de1f 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About repository visibility
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md
index 39ef8ed46e..f1d169d24c 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository.md
@@ -11,6 +11,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md
index e8b70b558f..43c0babe5e 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index 594e5645d6..2e48725b34 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About repository templates
@@ -24,7 +24,7 @@ Anyone with read permissions to a template repository can create a repository fr
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches.
+You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 Creating a repository from a template is similar to forking a repository, but there are important differences:
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md
index ab4eaeb9cd..0cf8296bed 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index 8f25268cc5..47a0f23a2d 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% note %}
@@ -20,7 +20,7 @@ topics:
 
 To create a template repository, you must create a repository, then make the repository a template. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)."
 
-After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md
index c02192cb38..8ae758fe6b 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 1. Create a **private** repository to host the source code from your project.
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md
index d0990e60e8..f2e1d8bcee 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Before you can duplicate a repository and push to your new copy, or _mirror_, of the repository, you must [create the new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. In these examples, `exampleuser/new-repository` or `exampleuser/mirrored` are the mirrors.
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md
index ccb72dd8cb..b1363cf9de 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Detecting this error is simple; Git will warn you when you try to clone the repository:
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
index c7a0d6029d..51cccc3a81 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### Check your spelling
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
index d3d8bd68d4..8297e04c6a 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Here's an example of an HTTPS error you might receive:
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md
index c5b3fb896f..e45d89e11b 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
index bf50983d63..be3635d65d 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### Choosing the right license
 
-We created [choosealicense.com](http://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision.
+We created [choosealicense.com](https://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision.
 
 You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project.
 
@@ -76,7 +76,7 @@ When you search by a family license, your results will include all licenses in t
 
 ### Detecting a license
 
-[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
 
 If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file.
 
diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md
index 1ebf7e51a8..229e0b7984 100644
--- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md
+++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Most of the limits below affect both {% data variables.product.product_name %} and the API.
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
index 6360ad7b4f..0f0f00c4c5 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -31,18 +33,10 @@ You can use {% data variables.product.prodname_code_scanning %} with {% data var
 
 {% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation.
 
-{% if currentVersion == "free-pro-team@latest" %}
-
-### About billing for {% data variables.product.prodname_code_scanning %}
-
-{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
-
-{% endif %}
-
 ### About third-party code scanning tools
 
 {% data reusables.code-scanning.you-can-upload-third-party-analysis %}
@@ -53,7 +47,5 @@ You can view and contribute to the queries for {% data variables.product.prodnam
 
 ### Дополнительная литература
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index 1cc921ca9b..572858a7f8 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 7aed7106e6..f358f5f7cf 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
index 8fdb7190fb..01183d9fe6 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -23,7 +25,7 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %} on {% data variables.product.prodname_dotcom_the_website %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
 
 ### Editing a {% data variables.product.prodname_code_scanning %} workflow
 
@@ -47,7 +49,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the `
 
 #### Scanning pull requests
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. The `pull_request` event is not triggered if the pull request was opened from a private fork.
 
 For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
 
@@ -108,9 +110,7 @@ This workflow scans:
 
 ### Specifying an operating system
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
-
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.
 
 ``` yaml
 jobs:
@@ -119,17 +119,15 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
+You must ensure that Git is in the PATH variable on your self-hosted runners.
 
 ### Changing the languages that are analyzed
 
 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
 
@@ -170,31 +168,34 @@ Alternatively, you can install Python dependencies manually on any operating sys
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
@@ -294,6 +295,7 @@ paths-ignore:
 **Note**:
 
 * The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
 * `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
 
 {% endnote %}
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index 3a07a2cc42..1d10719558 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -48,11 +50,11 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages.
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are `cpp`, `csharp`, `go`, `java`, `javascript`, and `python`.
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index db698238a7..3f7c8ed959 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -31,11 +33,7 @@ If your workflow uses a `language` matrix, `autobuild` attempts to build each of
 
 {% note %}
 
-{% if currentVersion == "github-ae@latest" %}**Note**: For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)."
-{% else %}
-**Note**: If you use self-hosted runners for
-{% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
-{% endif %}
+**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 
 {% endnote %}
 
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index daeec5d95a..b0957da47f 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### Table of Contents
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 25fb7e862d..7ffac959cb 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index 96167850d7..a0b40b74ed 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,13 +1,15 @@
 ---
 title: Managing code scanning alerts for your repository
 shortTitle: Managing alerts
-intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
+intro: 'From the security view, you can view, fix, or close alerts for potential vulnerabilities or errors in your project''s code.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About alerts from {% data variables.product.prodname_code_scanning %}
@@ -45,81 +47,25 @@ You need write permission to view a summary of all the alerts for a repository o
 
 Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have closed.
 
 Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
 
 ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 ### Closing an alert
 
 Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
 
-{% else %}
-
-### Dismissing or deleting alerts
-
-There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
-
-Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
-
-When you dismiss an alert:
-
-- It's dismissed in all branches.
-- The alert is removed from the number of current alerts for your project.
-- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required.
-- The reason why you closed the alert is recorded.
-- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert.
-
-When you delete an alert:
-
-- It's deleted in all branches.
-- The alert is removed from the number of current alerts for your project.
-- It is _not_ added to the "Closed" list in the summary of alerts.
-- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.
-
-To dismiss or delete alerts:
-
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
 1. Select the **Close** drop-down menu and click a reason for closing the alert.    
    ![Choosing reason for closing the alert via the Close drop-down](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
-
-   ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   Optionally, you can use the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
-
-  ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
-
-  ![Open an alert from the summary list](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### Dismissing multiple alerts at once
-
-If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
-
-{% endif %}
-
 ### Дополнительная литература
 
 - "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index 7a20d4fd24..45d86bb47f 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} with a containerized build
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index 37358a3663..9e1e1f669d 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
@@ -30,17 +31,13 @@ The {% data variables.product.prodname_codeql_runner %} is a command-line tool t
 {% note %}
 
 **Замечания:**
-{% if currentVersion == "free-pro-team@latest" %}
-* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
-{% else %}
 * The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
-{% endif %}
 * The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is an interactive command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. For more information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
 {% endnote %}
 
 ### Downloading the {% data variables.product.prodname_codeql_runner %}
 
-You can download the {% data variables.product.prodname_codeql_runner %} from https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
+You can download the {% data variables.product.prodname_codeql_runner %} from https://github.com/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
 
 On Linux:
 
@@ -62,7 +59,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi
 Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
@@ -73,9 +70,8 @@ In addition to this, each CI server also needs:
 
 The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
 
-1. Allow the CI servers access to https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
-{% if currentVersion == "enterprise-server@2.22" %}
-1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
+1. Allow the CI servers access to https://github.com/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically.
+1. Mirror the `github/codeql-action` repository on {% data variables.product.product_name %}. Unless you specify the <nobr>`--codeql-path`</nobr> flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.
 1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}.
 
 ### Calling the {% data variables.product.prodname_codeql_runner %}
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index b872e9131b..c4f5c68006 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About SARIF support
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
index 3fdbef956f..18558b7c2b 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -21,12 +23,10 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a
 
 ### Setting up {% data variables.product.prodname_code_scanning %} using actions
 
-{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
+3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with code scanning" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
 
    Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index d8f3762383..45396bd1a6 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -10,13 +10,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### About {% data variables.product.prodname_code_scanning %} results on pull requests
 
 In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
 
-If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or close all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
 
 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -40,28 +42,10 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
 
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
+### Resolving an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### Dismissing an alert on your pull request
-
-An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
-
-![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
-
-{% endif %}
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index 33145fa730..e0eb0f2d3b 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index 55e26da56a..a60bf1c77c 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
@@ -28,7 +30,10 @@ If an automatic build of code for a compiled language within your project fails,
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -113,25 +118,13 @@ If you split your analysis into multiple workflows as described above, we still
 
 If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Results differ between analysis platforms
-
-If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
-
-On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)."
-
-{% endif %}
-
 ### Error: "Server error"
 
 If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
 
 ### Error: "Out of disk" or "Out of memory"
-On very large projects,
 
-{% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. If you encounter this issue, try increasing the memory on the runner.
 
 ### Warning: "git checkout HEAD^2 is no longer necessary"
 
@@ -146,29 +139,29 @@ commit for best results.
 Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
 The revised `steps` section of the workflow will look like this:
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
 For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index 6511522e8c..330f44588f 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -19,7 +21,7 @@ topics:
 
 You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)."
 
-You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
+You can upload the results using {% data variables.product.prodname_actions %} (available if your organization is taking part in the beta program), the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use:
 
 - {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis.
 - {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below).
@@ -58,20 +60,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### Example workflow that runs the ESLint analysis tool
@@ -82,7 +86,7 @@ This example workflow runs anytime commits are pushed to the repository. The act
 
 The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -90,23 +94,26 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### Дополнительная литература
diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index 8ae5b92b6c..4b6edc962b 100644
--- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/ru-RU/content/github/finding-talent-with-github-jobs/index.md b/translations/ru-RU/content/github/finding-talent-with-github-jobs/index.md
index 16bb315d08..aeea22f640 100644
--- a/translations/ru-RU/content/github/finding-talent-with-github-jobs/index.md
+++ b/translations/ru-RU/content/github/finding-talent-with-github-jobs/index.md
@@ -7,7 +7,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - jobs
+  - Jobs
 ---
 
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/ru-RU/content/github/getting-started-with-github/about-git-subtree-merges.md
index 26a0158475..242da7c281 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 Typically, a subtree merge is used to contain a repository within a repository. The "subrepository" is stored in a folder of the main repository.
 
 The best way to explain subtree merges is to show by example. We will:
diff --git a/translations/ru-RU/content/github/getting-started-with-github/be-social.md b/translations/ru-RU/content/github/getting-started-with-github/be-social.md
index 628fec58f6..177b5cbbb5 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/be-social.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/be-social.md
@@ -38,6 +38,10 @@ Click **Watch** at the top of a repository to watch it.
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### Doing even more
 
 #### Creating pull requests
@@ -68,8 +72,8 @@ You're now connected to the {% data variables.product.product_name %} community.
 
 ![Star a project](/assets/images/help/stars/star-a-project.png)
 
-- [Set up Git](/articles/set-up-git)
-- [Create a repository](/articles/create-a-repo)
-- [Fork a repository](/articles/fork-a-repo)
+- "[Set up Git](/articles/set-up-git)"
+- "[Create a repository](/articles/create-a-repo)"
+- "[Fork a repository](/articles/fork-a-repo)"
 - **Be social**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/ru-RU/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/ru-RU/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index 8761058e20..476574527e 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 Every time you press <kbd>return</kbd> on your keyboard you insert an invisible character called a line ending. Different operating systems handle line endings differently.
 
-When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in OS X.
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
 
@@ -25,11 +25,11 @@ The `git config core.autocrlf` command is used to change how Git handles line en
 
 {% mac %}
 
-On OS X, you simply pass `input` to the configuration. Например:
+On macOS, you simply pass `input` to the configuration. Например:
 
 ```shell
 $ git config --global core.autocrlf input
-# Configure Git to ensure line endings in files you checkout are correct for OS X
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/ru-RU/content/github/getting-started-with-github/create-a-repo.md b/translations/ru-RU/content/github/getting-started-with-github/create-a-repo.md
index 3cf2717bff..9ea2734452 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/create-a-repo.md
@@ -9,12 +9,14 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
-  - issues
-  - notifications
-  - accounts
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
 ---
 
+### Create a repository
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 You can store a variety of projects in {% data variables.product.product_name %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software.
@@ -29,7 +31,7 @@ You can store a variety of projects in {% data variables.product.product_name %}
 
 {% note %}
 
-**Note:** You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](http://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
+**Note:** You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/exploring-projects-on-github.md b/translations/ru-RU/content/github/getting-started-with-github/exploring-projects-on-github.md
index 86b64226f4..f9e28c86b0 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/exploring-projects-on-github.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/exploring-projects-on-github.md
@@ -12,6 +12,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - projects
+  - Projects
 ---
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md b/translations/ru-RU/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md
index c9bba505fd..fda82e1144 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md
@@ -4,7 +4,7 @@ intro: 'As of April 14, 2020, GitHub announced that all of the core GitHub featu
 versions:
   free-pro-team: '*'
 topics:
-  - github
+  - GitHub
 ---
 
 ### What plans and pricing changes did GitHub announce on April 14?
diff --git a/translations/ru-RU/content/github/getting-started-with-github/fork-a-repo.md b/translations/ru-RU/content/github/getting-started-with-github/fork-a-repo.md
index 0adf9d15cd..6606775bc0 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### About forks
+
 Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.
 
 #### Propose changes to someone else's project
@@ -34,7 +36,7 @@ For more information about applying open source principles to your organization'
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](http://choosealicense.com/)" at choosealicense.com.
+When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com.
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
@@ -154,5 +156,6 @@ You have now forked a repository, practiced cloning your fork, and configured an
 
 - "[Set up Git](/articles/set-up-git)"
 - "[Create a repository](/articles/create-a-repo)"
+- **Fork a repository**
 - "[Be social](/articles/be-social)"
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/ru-RU/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/ru-RU/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index 9f729f1b57..d9de9e7eaf 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 These commands are very useful when interacting with [a remote repository](/github/getting-started-with-github/about-remote-repositories). `clone` and `fetch` download remote code from a repository's remote URL to your local computer, `merge` is used to merge different people's work together with yours, and `pull` is a combination of `fetch` and `merge`.
 
 ### Cloning a repository
diff --git a/translations/ru-RU/content/github/getting-started-with-github/git-workflows.md b/translations/ru-RU/content/github/getting-started-with-github/git-workflows.md
index f32df477d2..cbb4e138f6 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[GitHub flow](/github/collaborating-with-issues-and-pull-requests/github-flow)" and "[Understanding the GitHub flow](http://guides.github.com/overviews/flow/)" in the {% data variables.product.prodname_dotcom %} Guides.
+You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-cli.md b/translations/ru-RU/content/github/getting-started-with-github/github-cli.md
index ff68b7c922..c5fbe3ac6b 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/github-cli.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/github-cli.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '>2.19'
   github-ae: '*'
 topics:
-  - cli
+  - CLI
 ---
 
 ### About {% data variables.product.prodname_cli %}
diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-desktop.md b/translations/ru-RU/content/github/getting-started-with-github/github-desktop.md
index cfb8affbb7..64bc2beaf1 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/github-desktop.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/github-desktop.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - desktop
+  - Desktop
 ---
 
 ### About {% data variables.product.prodname_desktop %}
diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-flow.md b/translations/ru-RU/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..202c91657b
--- /dev/null
+++ b/translations/ru-RU/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: GitHub flow
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### Introduction
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### Требования
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### Create a pull request
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. Your pull request will update automatically.
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)."
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. For more information, see "[Addressing merge conflicts](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)."
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md b/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md
index 2e8789b4d4..15d6abefa4 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ You can be simultaneously signed into mobile with one user account on {% data va
 
 You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}.
 
-To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
+To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a user account on {% data variables.product.prodname_dotcom_the_website %}.
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-language-support.md b/translations/ru-RU/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/ru-RU/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md b/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md
index 1d68f78f32..5542290725 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 {% data variables.product.prodname_dotcom %} offers free and paid products. You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %}
 
 ### {% data variables.product.prodname_free_user %} for user accounts
@@ -99,14 +101,3 @@ In addition to the features available with {% data variables.product.prodname_te
 You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">Setting up a trial of {% data variables.product.prodname_ghe_cloud %}</a>."
 
 For more information about hosting your own instance of [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contact {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-{% data variables.product.prodname_ghe_one %} includes [{% data variables.product.prodname_enterprise %}](#github-enterprise), plus:
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %}
-- [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations)
-
-For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/ru-RU/content/github/getting-started-with-github/index.md b/translations/ru-RU/content/github/getting-started-with-github/index.md
index 36d79985d9..252056d516 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/index.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md
index 6d602192ba..f80e03dad8 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/keyboard-shortcuts.md
@@ -36,12 +36,16 @@ Below is a list of some of the available keyboard shortcuts.
 | <kbd>g</kbd> <kbd>p</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | <kbd>g</kbd> <kbd>a</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
 | <kbd>g</kbd> <kbd>b</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."                                                                                                       |
-| <kbd>g</kbd> <kbd>w</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."                                                                                      |
+| <kbd>g</kbd> <kbd>w</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ### Source code editing
 
 | Keyboard shortcut                                               | Description                                                    |
 | --------------------------------------------------------------- | -------------------------------------------------------------- |
+| <kbd>control b</kbd> or <kbd>command b</kbd>                    | Inserts Markdown formatting for bolding text                   |
+| <kbd>control i</kbd> or <kbd>command i</kbd>                    | Inserts Markdown formatting for italicizing text               |
+| <kbd>control k</kbd> or <kbd>command k</kbd>                    | Inserts Markdown formatting for creating a link                |
 | <kbd>e</kbd>                                                    | Open source code file in the **Edit file** tab                 |
 | <kbd>control f</kbd> or <kbd>command f</kbd>                    | Start searching in file editor                                 |
 | <kbd>control g</kbd> or <kbd>command g</kbd>                    | Find next                                                      |
diff --git a/translations/ru-RU/content/github/getting-started-with-github/learning-about-github.md b/translations/ru-RU/content/github/getting-started-with-github/learning-about-github.md
index 935030de96..2cfefb4683 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: Learning about GitHub
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/ru-RU/content/github/getting-started-with-github/quickstart.md b/translations/ru-RU/content/github/getting-started-with-github/quickstart.md
index d123093cb0..9af8f8cbc2 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/quickstart.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/quickstart.md
@@ -7,9 +7,9 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
-  - issues
-  - notifications
-  - accounts
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
 ---
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/set-up-git.md b/translations/ru-RU/content/github/getting-started-with-github/set-up-git.md
index d9061874ec..11bb04203e 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/set-up-git.md
@@ -16,12 +16,14 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
-  - issues
-  - notifications
-  - accounts
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
 ---
 
+### Using Git
+
 To use Git on the command line, you'll need to download, install, and configure Git on your computer. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. For more information on {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation.{% endif %}
 
 If you want to work with Git locally, but don't want to use the command line, you can instead download and install the [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) client.  For more information, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)."
diff --git a/translations/ru-RU/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/ru-RU/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index cd6ab77053..c27c344d0d 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ If you don't purchase {% data variables.product.prodname_enterprise %} or {% dat
 
 Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**. ![Buy Enterprise and Downgrade to Team buttons](/assets/images/help/organizations/finish-trial-buttons.png)
 6. Follow the prompts to enter your payment method, then click **Submit**.
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-github.md b/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-github.md
index b231d472ab..47012b1935 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-github.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-github.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
diff --git a/translations/ru-RU/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/ru-RU/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index 958f8b8442..27bcc03cbf 100644
--- a/translations/ru-RU/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/ru-RU/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 In this example, we will cover all of the `git rebase` commands available, except for `exec`.
 
 We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
diff --git a/translations/ru-RU/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/ru-RU/content/github/importing-your-projects-to-github/about-github-importer.md
index 4ef27c2707..4da7f17856 100644
--- a/translations/ru-RU/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/ru-RU/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: About GitHub Importer
-intro: 'If you have source code in Subversion, Mercurial, Team Foundation Server, or another Git repository, you can move it to GitHub using GitHub Importer.'
+intro: 'If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer.'
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ GitHub Importer is a tool that quickly imports source code repositories, includi
 
 During an import, depending on the version control system you're importing from, you can authenticate with your remote repository, update commit author attribution, and import repositories with large files (or remove large files if you don't want to use Git Large File Storage).
 
-| Import action                                                                                         | Subversion | Mercurial | Team Foundation Server |  Git  |
-|:----------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:|
-| Authenticate with remote repository                                                                   |   **X**    |   **X**   |         **X**          | **X** |
-| [Update commit author attribution](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   |         **X**          |       |
-| Move large files to [Git Large File Storage](/articles/about-git-large-file-storage)                  |   **X**    |   **X**   |         **X**          |       |
-| Remove large files from your repository                                                               |   **X**    |   **X**   |         **X**          |       |
+| Import action                                                                                         | Subversion | Mercurial | TFVC  |  Git  |
+|:----------------------------------------------------------------------------------------------------- |:----------:|:---------:|:-----:|:-----:|
+| Authenticate with remote repository                                                                   |   **X**    |   **X**   | **X** | **X** |
+| [Update commit author attribution](/articles/updating-commit-author-attribution-with-github-importer) |   **X**    |   **X**   | **X** |       |
+| Move large files to [Git Large File Storage](/articles/about-git-large-file-storage)                  |   **X**    |   **X**   | **X** |       |
+| Remove large files from your repository                                                               |   **X**    |   **X**   | **X** |       |
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/ru-RU/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index f5b101a3fd..de14fc7640 100644
--- a/translations/ru-RU/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/ru-RU/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Server, or another Git repository. You can also use these external tools to convert your project to Git.
+We recommend using [GitHub Importer](/articles/about-github-importer) to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. You can also use these external tools to convert your project to Git.
 
 {% endif %}
 
@@ -32,12 +32,9 @@ We recommend these tools for converting Subversion repositories to Git:
 
 We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
 
-### Importing from Team Foundation Server
+### Importing from TFVC
 
-We recommend these tools for moving changes between Team Foundation Server and Git:
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
 
 {% tip %}
 
diff --git a/translations/ru-RU/content/github/index.md b/translations/ru-RU/content/github/index.md
index d97b60cc5d..cc43338794 100644
--- a/translations/ru-RU/content/github/index.md
+++ b/translations/ru-RU/content/github/index.md
@@ -36,7 +36,6 @@ versions:
 {% link_in_list /collaborating-with-issues-and-pull-requests %}
 
 {% link_in_list /managing-your-work-on-github %}
-{% link_in_list /developing-online-with-codespaces %}
 
 {% link_in_list /searching-for-information-on-github %}
 
@@ -57,7 +56,6 @@ versions:
 
 {% link_in_list /extending-github %}
 
-{% link_in_list /supporting-the-open-source-community-with-github-sponsors %}
 {% link_in_list /finding-talent-with-github-jobs %}
 {% link_in_list /working-with-github-support %}
 {% link_in_list /understanding-how-github-uses-and-protects-your-data %}
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
index 262370f841..a02c9d2fdf 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
@@ -11,7 +11,7 @@ versions:
   github-ae: '*'
 permissions: 'People with write permissions can delete files{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} or directories{% endif %} in a repository.'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion
@@ -26,7 +26,7 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_
 
 1. Browse to the file in your repository that you want to delete.
 2. At the top of the file, click
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/index.md b/translations/ru-RU/content/github/managing-files-in-a-repository/index.md
index c17ebfd9e9..405efebf2e 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/index.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/index.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-on-github.md b/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-on-github.md
index 847cc2c4f7..699284a0a5 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-on-github.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-on-github.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md b/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md
index 4e9a2a76e5..f7ae5c17b6 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/managing-files-using-the-command-line.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md b/translations/ru-RU/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md
index ec6afeeac9..16ca90bf83 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 In addition to changing the file location, you can also [update the contents of your file](/articles/editing-files-in-your-repository), or [give it a new name](/articles/renaming-a-file) in the same commit.
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index 74c94d1aa3..e5d754932c 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### About navigating code on {% data variables.product.prodname_dotcom %}
 
 Code navigation uses the open source library [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). The following languages are supported:
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/renaming-a-file.md b/translations/ru-RU/content/github/managing-files-in-a-repository/renaming-a-file.md
index e645bb4a28..95ad4bbdff 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/renaming-a-file.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/renaming-a-file.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% tip %}
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md
index cbb171c5b3..4598764ee6 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-and-diffing-images.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md
index 8bc5d86520..5067779c89 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-csv-and-tsv-data.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 GitHub supports rendering tabular data in the form of *.csv* (comma-separated) and .*tsv* (tab-separated) files.
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md
index 82499927c8..da0b2cf000 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Commits and pull requests that include prose documents have the ability to represent those documents with *source* and *rendered* views.
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-pdf-documents.md b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-pdf-documents.md
index b5de8bd9b4..4319303a49 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-pdf-documents.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/rendering-pdf-documents.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 GitHub supports rendering of PDF documents.
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md b/translations/ru-RU/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md
index cd5d7cf839..da89d3d40b 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/tracking-changes-in-a-file.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/working-with-non-code-files.md b/translations/ru-RU/content/github/managing-files-in-a-repository/working-with-non-code-files.md
index 2632f39bf4..76c21bb2a5 100644
--- a/translations/ru-RU/content/github/managing-files-in-a-repository/working-with-non-code-files.md
+++ b/translations/ru-RU/content/github/managing-files-in-a-repository/working-with-non-code-files.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/ru-RU/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index 24ded122f4..8db6d0abea 100644
--- a/translations/ru-RU/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/ru-RU/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -38,7 +38,7 @@ versions:
 
 After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}.
 
-To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)."{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archived objects are purged after three months.{% endif %}
+To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archived objects are purged after three months.{% endif %}
 
 {% note %}
 
diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index f4a8266498..ffee9964f5 100644
--- a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,12 +1,14 @@
 ---
 title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
+intro: '{% data variables.product.product_name %} sends {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
 versions:
   enterprise-server: <=2.22
 topics:
   - Security
 ---
- 
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
 ### About vulnerable dependencies
 
 {% data reusables.repositories.a-vulnerability-is %}
@@ -15,12 +17,10 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 ### Detection of vulnerable dependencies
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
 
-{% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
+- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
 {% data reusables.repositories.dependency-review %}
 
@@ -32,7 +32,7 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
 ### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
 {% else %}
 ### Security alerts for vulnerable dependencies
@@ -40,25 +40,11 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% 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.
-
-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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
-
-{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 When
 {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-For repositories where
-{% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 When
 {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.
@@ -70,30 +56,17 @@ When
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### Access to {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+You can see all of the alerts that affect a particular project in the repository's dependency graph.
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
 By default, we notify people with admin permissions in the affected repositories about new
-{% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
-{% endif %}
+{% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 We send security alerts to people with admin permissions in the affected repositories by default.
 {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-You can also see all the
-{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Дополнительная литература
-
-- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index 9f0660db3c..1fd076e0ca 100644
--- a/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,20 +1,18 @@
 ---
 title: Configuring notifications for vulnerable dependencies
 shortTitle: Configuring notifications
-intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
+intro: 'Optimize how you receive notifications about  {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
 versions:
   enterprise-server: '>=2.21 <=2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies for the current version of this article -->
+
 ### About notifications for vulnerable dependencies
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
 Your site administrator needs to enable security alerts for vulnerable dependencies for
@@ -28,14 +26,14 @@ By default, if your site administrator has configured email for notifications on
 
 {% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
-### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
+### Configuring notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}
 
 You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
   ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
 {% else %}
   ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png)
@@ -47,11 +45,11 @@ You can configure notification settings for yourself or your organization from t
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %}
+{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
 
 ### How to reduce the noise from notifications for vulnerable dependencies
 
-If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+If you are concerned about receiving too many notifications for {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md
index cea165b9ad..b6e7b7ecfe 100644
--- a/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### Table of Contents
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index 8f5f7ecb65..d6cd9d9227 100644
--- a/translations/ru-RU/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index 980fbb0414..d8c0e532cf 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -26,13 +26,9 @@ You can choose to receive ongoing updates about specific activity on {% data var
 You can choose to subscribe to notifications for:
 - A conversation in a specific issue, pull request, or gist.
 - All activity in a repository or team discussion.
-- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}.
-{% if currentVersion == "free-pro-team@latest" %}
-- Issues, pulls requests, releases and discussions (if enabled) in a repository.
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- Releases in a repository.
-{% endif %}
+- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**.
 
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
index 7b821d4b6a..a42e6dcca5 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
@@ -58,7 +58,7 @@ In addition, you can receive and triage notifications on your mobile device with
 
 #### Benefits of using an email client for notifications
 
-One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
+One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
 
 Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.
 
@@ -69,15 +69,16 @@ Email notifications also allow flexibility with the types of notifications you r
 When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
 
 To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
 #### Configuring notifications
 {% endif %}
 You can configure notifications for a repository on the repository page, or on your watching page.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 #### About custom notifications
-{% data reusables.notifications-v2.custom-notifications-beta %}
-You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository.
+You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events (
+{% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository.
 {% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
 
 #### Participating in conversations
@@ -159,19 +160,22 @@ If "Automatically watch repositories" is disabled, then you will not automatical
 
 ### Configuring your watch settings for an individual repository
 
-You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
+You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 2. In the upper-right corner, click the "Watch" drop-down menu to select a watch option.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
    ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
-{% data reusables.notifications-v2.custom-notifications-beta %}
+
 The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
 
+{% if currentVersion == "free-pro-team@latest" %}
+   ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png)
+{% else %}
    ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2.png)
+{% endif %}
 
 If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
 
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md
index bfc6a6038a..eabcafdda7 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
 ### Starting your inbox triage
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/index.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/index.md
index 2ac3e96335..49ced1224d 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/index.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/index.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
 ### Table of Contents
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md
index 4783be44f1..5da3111869 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github.md
@@ -7,6 +7,6 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index c7bdb7a9bb..820719b15f 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
 To help you understand your subscriptions and decide whether to unsubscribe, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)."
@@ -57,13 +57,13 @@ When you unwatch a repository, you unsubscribe from future updates from that rep
 {% data reusables.notifications.access_notifications %}
 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-    - unwatch a repository
-    - only watch releases for a repository
-    - ignore all notifications for a repository
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
-    - unwatch a repository
-    - ignore all notifications for a repository
-    - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled)
-{% endif %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
+    - Unwatch a repository
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    - Unwatch a repository
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md
index 7995dcba50..a00ab3380e 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md
index 6214d8b1ea..80432701b7 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md
@@ -6,7 +6,7 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
 ### Saving a single notification
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md
index 1d23e517b8..3cd311b766 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '>=2.21'
   github-ae: '*'
 topics:
-  - notifications
+  - Notifications
 ---
 
diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index bfbd1d8140..a15f011611 100644
--- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -35,10 +35,10 @@ When your inbox has too many notifications to manage, consider whether you have
 For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
 
 To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
 
 {% endtip %}
 {% endif %}
@@ -67,16 +67,15 @@ Many people forget about repositories that they've chosen to watch in the past.
 
 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
   ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" %}when there are updates to issues, pull requests, releases or discussions (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
 
   When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/ru-RU/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index b06d666832..ec88277158 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ Query parameters are optional parts of a URL you can customize to share a specif
 
 You must have the proper permissions for any action to use the equivalent query parameter. For example, you must have permission to add a label to an issue to use the `labels` query parameter.
 
-If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a 404 error page.
+If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page.
 
 ### Supported query parameters
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md
index 9f7ec04b68..43da983837 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 For a "marked as duplicate" timeline event to appear, the user who creates the duplicate reference comment must have write access to the repository where they create the comment.
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md b/translations/ru-RU/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md
index b095a8b53f..650d156dc2 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/archiving-cards-on-a-project-board.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 Automation in your project board does not apply to archived project board cards. For example, if you close an issue in a project board's archive, the archived card does not automatically move to the "Done" column. When you restore a card from the project board archive, the card will return to the column where it was archived.
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md b/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md
index 01019a9aa5..f6194ffabb 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/changing-project-board-visibility.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% data reusables.project-management.project-board-visibility %}
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md b/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md
index c420517a54..f0c136cc3a 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/copying-a-project-board.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 Copying a project board allows you to reuse a project board's title, description, and automation configuration. You can copy project boards to eliminate the manual process of creating new project boards for similar workflows.
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index fe8a4e8ae5..c34b54928d 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. Choose one of these options:
     - To create a new milestone, click **New Milestone**. ![New milestone button](/assets/images/help/repository/new-milestone.png)
     - To edit a milestone, next to the milestone you want to edit, click **Edit**. ![Edit milestone option](/assets/images/help/repository/edit-milestone.png)
-5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**.
+5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
 
 ### Deleting milestones
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/disabling-issues.md b/translations/ru-RU/content/github/managing-your-work-on-github/disabling-issues.md
index 02e4406d35..d97a301151 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/disabling-issues.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/disabling-issues.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md b/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md
index 2e0fca26ba..78901dbe9d 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-a-repository.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 When you disable project boards, you will no longer see project board information in timelines or [audit logs](/articles/reviewing-your-security-log/).
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index 2af3620e91..8ff8624420 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ After you disable repository project boards in an organization, it won't be poss
 
 When you disable project boards, you will no longer see project board information in timelines or [audit logs](/articles/reviewing-the-audit-log-for-your-organization/).
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects":
     - To disable organization-wide project boards, unselect **Enable projects for the organization**.
     - To disable repository project boards in the organization, unselect **Enable projects for all repositories**. ![Checkboxes to disable projects for an organization or for all of an organization's repositories](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index 7005200547..11605dd076 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: File attachments on issues and pull requests
-intro: 'When you open issue or update a pull request, you can use issue attachments to upload images of proposed features or screenshots of bugs.'
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -9,12 +9,12 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% warning %}
 
-**Warning:** If you add an image to a pull request or issue comment, anyone can view the anonymized image URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive images private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized image URLs](/articles/about-anonymized-image-urls)".{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ To attach a file to an issue or pull request conversation, drag and drop it into
 
 {% endtip %}
 
-The maximum size for files is 25MB and the maximum size for images is 10MB.
-{% if currentVersion == "free-pro-team@latest" %}
-Videos can be up to 100 MB in size if the repository is owned by a user or organization on a paid GitHub plan.
-
-{% note %}
-
-**Note:** Support for video attachments is currently in beta and subject to change.
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 We support these files:
 
@@ -49,7 +43,7 @@ We support these files:
 * Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
 * Text files (*.txt*)
 * PDFs (*.pdf*)
-* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" %}
+* ZIP (*.zip*, *.gz*){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * Video (*.mp4*, *.mov*){% endif %}
 
 ![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/finding-information-in-a-repository.md b/translations/ru-RU/content/github/managing-your-work-on-github/finding-information-in-a-repository.md
index d90d3de261..0a73d1c3ed 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/finding-information-in-a-repository.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/finding-information-in-a-repository.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/index.md b/translations/ru-RU/content/github/managing-your-work-on-github/index.md
index a425a1a411..1333cf341f 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/index.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/index.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md b/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md
index dac21a4d1f..09c8d0dbbc 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/managing-labels.md
@@ -49,6 +49,8 @@ Anyone with read access to a repository can view and search the repository’s l
 
 Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later.
 
+Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)."
 {% endif %}
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/managing-project-boards.md b/translations/ru-RU/content/github/managing-your-work-on-github/managing-project-boards.md
index ccc1c55316..f18692d4d0 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/managing-project-boards.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/managing-project-boards.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md
index b8e7517513..5e48a4ef52 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md b/translations/ru-RU/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md
index 69ccb1dec0..9029f22b7e 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/pinning-an-issue-to-your-repository.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 ![Pinned issues](/assets/images/help/issues/pinned-issues.png)
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index bb01bd6db8..88cbef62f0 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ You can sort any filtered view by:
 * The least commented issues or pull requests
 * The newest updated issues or pull requests
 * The oldest updated issues or pull requests
-* The most added [reaction](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) on issues or pull requests
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. In the upper-right corner, select the Sort drop-down menu. ![Using the Sort drop-down tab](/assets/images/help/issues/issues_sort_dropdown.png)
+1. In the upper-right corner, select the Sort drop-down menu. ![Using the Sort drop-down tab](/assets/images/help/issues/issues_sort_dropdown.png)
 
 To clear your sort selection, click **Sort** > **Newest**.
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md b/translations/ru-RU/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md
index db90f8f6a3..3078734721 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/tracking-progress-on-your-project-board.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
 {% data reusables.project-management.project-progress-locations %}
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md b/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md
index 081bd66cfd..316482f324 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md b/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md
index 9ad7f25801..52acab2585 100644
--- a/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md
+++ b/translations/ru-RU/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards.md
@@ -10,6 +10,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pull requests
+  - Pull requests
 ---
 
diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md b/translations/ru-RU/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md
index df48291d6e..29ba7dc2a7 100644
--- a/translations/ru-RU/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md
+++ b/translations/ru-RU/content/github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md
@@ -10,7 +10,7 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - github search
+  - GitHub search
 ---
 
 If you use {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %} and your {% data variables.product.prodname_ghe_server %} site administrator has enabled {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories, then you can search for designated private repositories in the connected organization.
diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md b/translations/ru-RU/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md
index b29b41a6b2..1d8988a552 100644
--- a/translations/ru-RU/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md
+++ b/translations/ru-RU/content/github/searching-for-information-on-github/getting-started-with-searching-on-github.md
@@ -8,6 +8,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github search
+  - GitHub search
 ---
 
diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/index.md b/translations/ru-RU/content/github/searching-for-information-on-github/index.md
index d5c9601add..39993e2955 100644
--- a/translations/ru-RU/content/github/searching-for-information-on-github/index.md
+++ b/translations/ru-RU/content/github/searching-for-information-on-github/index.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github search
+  - GitHub search
 ---
 
 
diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-code.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-code.md
index 7caa37e703..23e85aef4e 100644
--- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ You can use the `path` qualifier to search for source code that appears at a spe
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in an <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>). |
 
 ### Search by language
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-You can search for code based on what language it's written in.
+You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | Qualifier                  | Пример                                                                                                                                                                                                  |
 | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-on-github.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-on-github.md
index add2f14613..c17c8aba57 100644
--- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-on-github.md
+++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-on-github.md
@@ -8,6 +8,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - github search
+  - GitHub search
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 32079f6cf3..3f91863595 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)."
+
+{% endnote %}
 
 If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index eee2a3e952..56641f6d06 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### Дополнительная литература
 
-- "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)"
-- "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)"
+- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index 86893eac64..f7fc24aa7a 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,26 +16,11 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %}
 
 ### About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
 
-We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_dotcom_the_website %}:
-
-- **Committers** is the number of committers who contributed to at least one private repository in an organization and who use a seat in your license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
-- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
-
-If there are no unique committers, this means that all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
-
-{% note %}
-
-**Note:** The total number of seats used in your license is not the sum of either the committers or the unique committers to each repository or organization. This is because there are people who contribute to multiple repositories or organizations. The number of seats used is measured across the whole enterprise account to ensure that each person is counted only once regardless of how many repositories or organizations they contribute to.
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### Managing your license usage for {% data variables.product.prodname_GH_advanced_security %}
 
-When you enable {% data variables.product.prodname_GH_advanced_security %} for a single repository, or for all repositories in an organization, {% data variables.product.company_short %} shows how many extra seats this will use and prompts you for confirmation. If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up. This makes it easy to understand the impact of your changes on the use of your license.
-
-If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available. If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.
-
-As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal.
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
 You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)."
 
@@ -43,9 +28,4 @@ For more information on viewing license usage, see "[Viewing your {% data variab
 
 ### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license
 
-When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify:
-
-- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company.
-- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced.
-
-When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index 3e5505adad..192efaf986 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
 ### Adding information to your personal account's receipts
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### Adding information to your organization's receipts
@@ -40,9 +40,9 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index ddc31481f1..a6c67402b4 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ We don't provide invoicing or support purchase orders for personal accounts. We
 ### Updating your personal account's payment method
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### Updating your organization's payment method
@@ -38,9 +39,10 @@ We don't provide invoicing or support purchase orders for personal accounts. We
 
 If your organization is outside of the US or if you're using a corporate checking account to pay for {% data variables.product.product_name %}, PayPal could be a helpful method of payment.
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index 075e3502f4..983c92cae7 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 ### Canceling an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### Canceling a free trial for an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index d276d19b9c..878bc94a1e 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 ### Changing the duration of your personal account's billing cycle
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ When you change your billing cycle's duration, your {% data variables.product.pr
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. Under "Billing overview", click **Change plan**. ![Billing overview change plan button](/assets/images/help/billing/billing_overview_change_plan.png)
 5. At the top right corner, click **Switch to monthly billing** or **Switch to yearly billing**. ![Billing information section](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index 722609c567..c041927148 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ If you already have a personal {% data variables.product.prodname_dotcom %} user
 
 ### Step 3: Upgrade the organization to a yearly paid subscription
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} (You can add more seats to the organization in the next step.)
 6. Under "Upgrade summary", select **Pay yearly** to pay for the organization yearly. ![Radio button for yearly billing](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. Under "Pay with", type your credit card information. ![Form for entering credit card information](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. Click **Update credit card**.
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### Step 4: Upgrade the number of paid seats in the organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index 4f47eaeb91..b0dad06edb 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -16,8 +16,7 @@ When you downgrade your number of data packs, your change takes effect on your n
 ### Downgrading storage and bandwidth for a personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
@@ -25,10 +24,8 @@ When you downgrade your number of data packs, your change takes effect on your n
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index a24a63d77e..7c1d0c6d67 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ When you downgrade an app, your subscription remains active until the end of you
 ### Downgrading an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ When you downgrade an app, your subscription remains active until the end of you
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index c3501da0c2..9f9be8377a 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ When you downgrade your user account or organization's subscription, pricing and
 If you downgrade your user account from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, the account will lose access to advanced code review tools on private repositories. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Use the **Edit** drop-down and click **Downgrade to Free**. ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
 5. Read the information about the features your user account will no longer have access to on your next billing date, then click **I understand. Continue with downgrade**. ![Continue with downgrade button](/assets/images/help/billing/continue-with-downgrade.png)
 
 If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, remove or update your DNS records before downgrading from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
@@ -45,12 +44,10 @@ If you downgrade your organization from {% data variables.product.prodname_team
 
 If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Use the **Edit** drop-down and click the downgrade option you want. ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### Downgrading an organization's subscription with legacy per-repository pricing
@@ -59,10 +56,9 @@ If you downgrade your organization from {% data variables.product.prodname_ghe_c
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**. ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png)
 1. Under "Billing/Plans",  next to the plan you want to change, click **Downgrade**. ![Downgrade button](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. Enter the reason you're downgrading your account, then click **Downgrade plan**. ![Text box for downgrade reason and downgrade button](/assets/images/help/billing/downgrade-plan-button.png)
@@ -74,12 +70,10 @@ To reduce the number of paid seats your organization uses, you can remove member
 - "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
 - "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. Use the **Edit** drop-down and click **Remove seats**. ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
 1. Under "Remove seats", select the number of seats you'd like to downgrade to. ![remove seats option](/assets/images/help/billing/remove-seats-amount.png)
 1. Review the information about your new payment on your next billing date, then click **Remove seats**. ![remove seats button](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index c0c11e3fc0..be35125eab 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ Because you have not enabled overages, your next attempt to create a workflow ar
 Anyone can manage the spending limit for {% data variables.product.prodname_actions %} for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Anyone can manage the spending limit for {% data variables.product.prodname_acti
 
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise owners and billing managers can manage the spending limit for {% data
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "
-{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**.
-  ![Cost management tab](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index 2944ea140f..8b6ed40fe3 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ Because you have not enabled overages, your next attempt to publish a version of
 Anyone can manage the spending limit for {% data variables.product.prodname_registry %} for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ Anyone can manage the spending limit for {% data variables.product.prodname_regi
 
 Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ Enterprise owners and billing managers can manage the spending limit for {% data
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "
-{% data variables.product.prodname_actions %} and Packages monthly usage", click **Cost management**.
-  ![Cost management tab](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index 2a311494f0..3a223dc1ec 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ If you're paying for your {% data variables.product.product_name %} subscription
 ### Removing your personal account's payment method
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ If you're paying for your {% data variables.product.product_name %} subscription
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index 17e8c5b6e8..7b7b694bc2 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### Updating your organization's credit card
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. Type your new credit card information in the secure form. ![Credit card information form](/assets/images/help/settings/creditcard-billing-form.png)
-1. Click **Update credit card** or **Save credit card**.
+1. Under "Payment method", click **New Card**. ![Billing New Card button](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index 61cf642bc6..94456eca76 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ Your organization's billing email is where {% data variables.product.product_nam
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Under **Billing email**, type a valid email address. The email does not need to be unique to the organization account. ![Billing email textbox](/assets/images/help/settings/org-billing-email.png)
 5. To confirm your changes, click **Update profile**. ![Update profile button](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ If you have users that want to receive billing reports, you can add their email
 #### Adding a recipient for billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Billing management", to the right of "Email recipients", click **Add**. ![Add recipient](/assets/images/help/billing/billing-add-email-recipient.png)
 1. Type the email address of the recipient, then click **Add**. ![Add recipient modal](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ If you have users that want to receive billing reports, you can add their email
 One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected.
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Billing management", find the email address you want to set as the primary recipient.
 1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**. ![Mark primary recipient](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### Removing a recipient from billing notifications
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. Under "Email recipients", find the email address you want to remove.
 1. For the user's entry in the list, click **Edit**. ![Edit recipient](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. To the right of the email address, use the "Edit" drop-down menu, and click *Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. Review the confirmation prompt, then click **Remove**.
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index d151a8ac4a..90d1277980 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### Purchasing additional storage and bandwidth for a personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index ce93275910..6fdffd5f75 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,11 +22,9 @@ topics:
 
 ### Upgrading an organization's number of paid seats
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -35,10 +33,8 @@ After you add seats, the payment method on file for the organization will be cha
 
 ### Downgrading an organization's number of paid seats to free
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 6bd3483a28..7eca07d340 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
 ### Upgrading an app for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ When you upgrade an app, your payment method is charged a prorated amount based
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index bcb1111fc6..254158c097 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. Next to "
-{% data variables.product.prodname_free_user %}", click **Upgrade**.
-  ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ If you'd like to use an enterprise account with {% data variables.product.prodna
 
 If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ If you'd like additional users to have access to your {% data variables.product.
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**. ![Edit drop-down menu](/assets/images/help/billing/per-user-upgrade-button.png)
 6. To the right of "Advanced tools for teams", click **Upgrade now**. ![Upgrade now button](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index 1986f1b569..47d397f3f0 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ When you cancel a pending change, your subscription will not change on your next
 ### Viewing and managing pending changes to your personal account's subscription
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### Viewing and managing pending changes to your organization's subscription
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index 9ae11e3122..60adbe7fa0 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### Viewing storage and bandwidth usage for a personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Viewing storage and bandwidth usage for an organization
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### Дополнительная литература
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index a12363a682..6bff6d36f6 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ You can also view the billable job execution minutes for an individual workflow
 Anyone can view {% data variables.product.prodname_actions %} usage for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ Anyone can view {% data variables.product.prodname_actions %} usage for their ow
 
 Organization owners and billing managers can view {% data variables.product.prodname_actions %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_actions %} usage in the organization billing page.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index 2a55ae7412..27b5e7d242 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,24 +1,24 @@
 ---
 title: Viewing your GitHub Advanced Security usage
-intro: 'You can view and manage usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
-permissions: Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
   free-pro-team: '*'
 ---
 
-Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Periodically you should check that your use is within your license capacity. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
 
-### Viewing and managing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
+### Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
 
-You can check how many seats your license includes and how many of them are currently used on the "Enterprise licensing" page.
+You can check how many seats your license includes and how many of them are currently used.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
-4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png)
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
 5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
 6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[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/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index 739d4f10da..dc11426e97 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 Anyone can view {% data variables.product.prodname_registry %} usage for their own user account.
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ Anyone can view {% data variables.product.prodname_registry %} usage for their o
 
 Organization owners and billing managers can view {% data variables.product.prodname_registry %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_registry %} usage in the organization billing page.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index 7cf7a65ce0..d1880d2822 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### Viewing receipts for your personal account
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index 33d5c644fc..8454d43a87 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### Finding your personal account's next billing date
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Finding your organization's next billing date
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### Дополнительная литература
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index ea9b3d4b19..791e958b09 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -36,5 +36,5 @@ After you disconnect your Azure subscription from your enterprise account, your
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
+1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**.
 1. Review the prompt, then click **Remove**.
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index 024664c550..f070ac7de3 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -48,3 +48,19 @@ You can disable all workflows for an enterprise or set a policy that configures
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### Setting the permissions of the `GITHUB_TOKEN` for your enterprise
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. Click **Save** to apply the settings.
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md
index a60b8b14a8..fe74fb917f 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..39850b1dd2
--- /dev/null
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: Restricting email notifications for your enterprise account
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### About email restrictions for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### Restricting email notifications for your enterprise account
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..fa4be47e6b
--- /dev/null
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About domain verification
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index e4ae690e71..8740387ece 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -20,6 +20,15 @@ When you enable SAML single sign-on for your enterprise account, each enterprise
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index de8869bcf0..d2de38d94c 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories to the top of the page.
 
-{% if currentVersion == "free-pro-team@latest" %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
+{% if currentVersion == "free-pro-team@latest" %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![Sample verified organization profile page](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md
index 529e65c64d..2e5c88861f 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - profiles
+  - Profiles
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/index.md
index 65df71a043..93bcfb96f1 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/index.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/index.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - profiles
+  - Profiles
 ---
 
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md
index 54d688fdac..4b1fb5337b 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - profiles
+  - Profiles
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index d8a85f2371..0a9ce4c849 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ If you select the "Busy" option, when people @mention your username, assign you
 
 When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
 
-| Badge                                                           | Program                                                              | Description                                                                                                                                                                                                                                                                                                                                                |
-| --------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **Developer Program Member**                                         | If you're a registered member of the GitHub Developer Program, building an app with the GitHub API, you'll get a Developer Program Member badge on your profile. For more information on the GitHub Developer Program, see [GitHub Developer](/program/).                                                                                                  |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **GitHub Sponsor**                                                   | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a GitHub Sponsor badge on your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)."                            |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                              | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)."                                                     |
+| Badge                                                                                                                    | Program                                                              | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter Contributor badge icon](/assets/images/help/profile/badge-mars-2020-small.png)                    | **Mars 2020 Helicopter Contributor**                                 | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
+| ![Arctic Code Vault Contributor badge icon](/assets/images/help/profile/badge-arctic-code-vault-small.png)               | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were part of the program. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com).                                                                                                                                                                                      |
+| ![{% data variables.product.prodname_dotcom %} Sponsor badge icon](/assets/images/help/profile/badge-sponsors-small.png) | **{% data variables.product.prodname_dotcom %} Sponsor**             | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)."                                                                                                                                                                                                                 |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                              | **Developer Program Member**                                         | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% data variables.product.prodname_dotcom %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/).                                                                                                                                                                                                                                                                                   |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                                     | **Pro**                                                              | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)."                                                                                                                                                                                                                                                                                                                                                          |
 
 ### Disabling badges on your profile
 
-You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO and {% data variables.product.prodname_arctic_vault %} badges.
+You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
 
 {% data reusables.user_settings.access_settings %}
-2. Under "Profile settings", deselect the badge you want you disable. ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. Under "Profile settings", deselect the badge you want you disable. ![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/profile-badge-settings.png)
 3. Click **Update preferences**.
 
 {% endif %}
 
+### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
+
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+
+| {% data variables.product.prodname_dotcom %} Repository                       | Версия    | Tag                                                                                                        |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.2       | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### Дополнительная литература
 
 - "[About your profile](/articles/about-your-profile)"
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md
index 63f03064e6..a55d21cac0 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - profiles
+  - Profiles
 ---
 
 {% data reusables.profile.activity-overview-summary %} For more information, see "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)."
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md
index 6042dc6f6b..908898155e 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/accessing-an-organization.md
@@ -11,7 +11,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 {% tip %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md
index 9bba3b05ed..06e6f5d224 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 Before you leave your company, make sure you update the following information in your user account:
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index 3196bb68bf..ff07e6ef7f 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. If you'd like to add a new email address to set as your primary email address, under "Add email address", type a new email address and click **Add**. ![Add another email address button](/assets/images/help/settings/add_another_email_address.png)
 4. Under "Primary email address", use the drop-down menu to click the email address you'd like to set as your primary email address, and click **Save**. ![Set as primary button](/assets/images/help/settings/set_as_primary_email.png)
 5. To remove the old email address from your account, next to the old email, click
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}.
 {% if currentVersion == "free-pro-team@latest" %}
 6. Verify your new primary email address. Without a verified email address, you won't be able to use all of
 {% data variables.product.product_name %}'s features. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md
index a45c90b984..b486a00679 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
index 0899fdf912..b61cfaab1a 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
@@ -4,8 +4,8 @@ intro: You can invite someone to manage your user owned repositories if you are
 versions:
   free-pro-team: '*'
 topics:
-  - accounts
-  - repositories
+  - Accounts
+  - Repositories
 ---
 
 ### About successors
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md
index eb7faf4527..499aac4ded 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
-  - repositories
+  - Accounts
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md
index 94340043a8..ad875570f2 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 A collaborator is a person who has permissions to a project board you own. A collaborator's permissions will default to read access. For more information, see "[Permission levels for user-owned project boards](/articles/permission-levels-for-user-owned-project-boards)."
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md
index 0b29ed6699..26f736ea02 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
-  - notifications
+  - Accounts
+  - Notifications
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md
index fcbe11a0a4..65050694bf 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings.md
@@ -11,6 +11,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md
index 37b22a88d8..3ebd000d9a 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index f815877060..026007c997 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -1,23 +1,20 @@
 ---
 title: Managing your theme settings
-intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode.'
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
 versions:
   free-pro-team: '*'
 topics:
   - Accounts
 ---
 
-{% note %}
-
-**Note:** Theme settings is currently in beta and subject to change.
-
-{% endnote %}
-
-For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions.
+For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
 
 {% data reusables.user_settings.access_settings %}
 1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
-1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. Under "Theme mode", select the drop-down menu, then click a theme preference. ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Click the theme you'd like to use.
+    - If you chose a single theme, click a theme. ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - If you chose to follow your system settings, click a day theme and a night theme. ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### Дополнительная литература
 
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
index 774403d22e..a923433735 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
@@ -32,7 +32,7 @@ The repository owner has full control of the repository. In addition to the acti
 | {% if currentVersion == "free-pro-team@latest" %}Invite collaborators{% else %}Add collaborators{% endif %}                                                                                                                  |                                                                                                                                                                                                                                                                                                                                |
 | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)"                                                                |                                                                                                                                                                                                                                                                                                                                |
 | Change the visibility of the repository                                                                                                                                                                                      | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% if currentVersion == "free-pro-team@latest" %}
-| Limit interactions with the repository                                                                                                                                                                                       | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Limit interactions with the repository                                                                                                                                                                                       | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename a branch, including the default branch                                                                                                                                                                                | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Merge a pull request on a protected branch, even if there are no approving reviews                                                                                                                                           | "[About protected branches](/github/administering-a-repository/about-protected-branches)"                                                                                                                                                                                                                                      |
@@ -70,7 +70,7 @@ Collaborators can also perform the following actions.
 
 | Действие                                                                                  | More information                                                                                                                                                                                                                                                                                         |
 |:----------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Fork the repository                                                                       | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Fork the repository                                                                       | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename a branch other than the default branch                                             | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                                                                |
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md
index 465eefca91..32801e8335 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 ![Profile organizations box](/assets/images/help/profile/profile_orgs_box.png)
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index 875c17f2f5..1c1d3453af 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ While forks of private repositories are deleted when a collaborator is removed,
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. To the right of the collaborator you want to remove, click
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
   ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. In the left sidebar, click **Collaborators & teams**. ![Collaborators tab](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md
index e1a28b8111..439665e43c 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository.md
@@ -13,8 +13,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
-  - repositories
+  - Accounts
+  - Repositories
 ---
 
 {% data reusables.user_settings.access_settings %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md
index 1ab856f028..61f373a6ab 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md
index c2ee6b124f..315196e84c 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address.md
@@ -15,8 +15,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
-  - notifications
+  - Accounts
+  - Notifications
 ---
 
 ### About commit email addresses
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md
index 6fcfee0db7..1787bb6bf5 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - accounts
-  - notifications
+  - Accounts
+  - Notifications
 ---
 
 ### Notification emails
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md
index 9e6d656e6f..411f7a2c65 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md
index f7b6ab46c5..82920cec9c 100644
--- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md
+++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - accounts
+  - Accounts
 ---
 
 The [GitHub Jobs](https://jobs.github.com/) board is a great way to find employment in tech. You can opt to see jobs posted there on your GitHub dashboard.
diff --git a/translations/ru-RU/content/github/site-policy/dmca-takedown-policy.md b/translations/ru-RU/content/github/site-policy/dmca-takedown-policy.md
index a2548534a3..7070c8eac7 100644
--- a/translations/ru-RU/content/github/site-policy/dmca-takedown-policy.md
+++ b/translations/ru-RU/content/github/site-policy/dmca-takedown-policy.md
@@ -9,8 +9,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Welcome to GitHub's Guide to the Digital Millennium Copyright Act, commonly known as the "DMCA." This page is not meant as a comprehensive primer to the statute. However, if you've received a DMCA takedown notice targeting content you've posted on GitHub or if you're a rights-holder looking to issue such a notice, this page will hopefully help to demystify the law a bit as well as our policies for complying with it.
diff --git a/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md
index 0a63b70043..a01d8ca567 100644
--- a/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md
+++ b/translations/ru-RU/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 ### Summary
diff --git a/translations/ru-RU/content/github/site-policy/github-candidate-privacy-policy.md b/translations/ru-RU/content/github/site-policy/github-candidate-privacy-policy.md
index fe8605d913..f1e55a6457 100644
--- a/translations/ru-RU/content/github/site-policy/github-candidate-privacy-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-candidate-privacy-policy.md
@@ -3,8 +3,8 @@ title: GitHub Candidate Privacy Policy
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Effective Date: March 8, 2021
diff --git a/translations/ru-RU/content/github/site-policy/github-community-forum-code-of-conduct.md b/translations/ru-RU/content/github/site-policy/github-community-forum-code-of-conduct.md
index aa9b32dd80..90fc83e338 100644
--- a/translations/ru-RU/content/github/site-policy/github-community-forum-code-of-conduct.md
+++ b/translations/ru-RU/content/github/site-policy/github-community-forum-code-of-conduct.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 ### Overview and Purpose
diff --git a/translations/ru-RU/content/github/site-policy/github-community-guidelines.md b/translations/ru-RU/content/github/site-policy/github-community-guidelines.md
index 05d0328b1a..acc9e7df63 100644
--- a/translations/ru-RU/content/github/site-policy/github-community-guidelines.md
+++ b/translations/ru-RU/content/github/site-policy/github-community-guidelines.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Millions of developers host millions of projects on GitHub — both open and closed source — and we're honored to play a part in enabling collaboration across the community every day. Together, we all have an exciting opportunity and responsibility to make this a community we can be proud of.
diff --git a/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md
index c598cc47e6..2bf113c6ee 100644
--- a/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,6 +9,8 @@ topics:
   - Legal
 ---
 
+_These terms apply to 1) GitHub.com (non-Enterprise) customers who have accepted the Corporate Terms of Service, and 2) Enterprise customers who licensed the Service prior to January 4, 2021. Enterprise customers who purchase Products or Services after that date are directed to https://github.com/enterprise-legal for current terms._
+
 THANK YOU FOR CHOOSING GITHUB FOR YOUR COMPANY’S BUSINESS NEEDS. PLEASE READ THIS AGREEMENT CAREFULLY AS IT GOVERNS USE OF THE PRODUCTS (AS DEFINED BELOW), UNLESS GITHUB HAS EXECUTED A SEPARATE WRITTEN AGREEMENT WITH CUSTOMER FOR THAT PURPOSE. BY CLICKING ON THE "I AGREE" OR SIMILAR BUTTON OR BY ACCESSING THE PRODUCTS, CUSTOMER ACCEPTS ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF CUSTOMER IS ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, CUSTOMER REPRESENTS THAT IT HAS THE LEGAL AUTHORITY TO BIND THE COMPANY OR OTHER LEGAL ENTITY TO THIS AGREEMENT.
 
 ### GitHub Corporate Terms of Service
diff --git a/translations/ru-RU/content/github/site-policy/github-event-terms.md b/translations/ru-RU/content/github/site-policy/github-event-terms.md
index 5145ee3b6c..dde3f1249d 100644
--- a/translations/ru-RU/content/github/site-policy/github-event-terms.md
+++ b/translations/ru-RU/content/github/site-policy/github-event-terms.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 By RSVP'ing to or attending a GitHub event, including any of the events or activities organized by GitHub in association with the GitHub event (collectively the "Event"), you signal that you have read, understand, and agree to the following Event Terms and Conditions.
diff --git a/translations/ru-RU/content/github/site-policy/github-gifts-and-entertainment-policy.md b/translations/ru-RU/content/github/site-policy/github-gifts-and-entertainment-policy.md
index 5fce72f4af..237f1ffb1a 100644
--- a/translations/ru-RU/content/github/site-policy/github-gifts-and-entertainment-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-gifts-and-entertainment-policy.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 GitHub recognizes that our business is built on positive and transparent relationships. While informal interactions and exchanges of gifts may be part of developing those relationships and may even be considered customary in some countries, we need to ensure that we’re following anti-bribery laws. We have a legal obligation to behave ethically, including by not using such interactions to create a special advantage or influence a deal.
diff --git a/translations/ru-RU/content/github/site-policy/github-government-takedown-policy.md b/translations/ru-RU/content/github/site-policy/github-government-takedown-policy.md
index 05611f38f0..1d1a0150eb 100644
--- a/translations/ru-RU/content/github/site-policy/github-government-takedown-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-government-takedown-policy.md
@@ -3,8 +3,8 @@ title: GitHub Government Takedown Policy
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 #### What is this?
diff --git a/translations/ru-RU/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/ru-RU/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
index a4b4d3fc5e..18a2ec5da2 100644
--- a/translations/ru-RU/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
+++ b/translations/ru-RU/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insights and data protection for your organization
 intro: '{% data variables.product.prodname_insights %} analyzes your {% data variables.product.prodname_ghe_server %} data. This data could include personal data of individuals in your organization who may have the right to understand how such personal data is being used.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
   - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
@@ -10,12 +9,10 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
-For more information about the terms that govern {% data variables.product.prodname_insights %}, see your {% data variables.product.prodname_ghe_one %} subscription agreement.
-
 For the avoidance of doubt, none of the foregoing information should be considered legal advice provided by {% data variables.product.prodname_dotcom %}. You are responsible for securing your own legal analysis of the information provided herein and for your compliance with privacy and data protection laws. It is up to you whether to use {% data variables.product.prodname_insights %} to process your employees’ and users’ data, and if you do so, you are solely responsible for conducting such processing in compliance with applicable law.
 
 ### The organization’s roles and responsibilities
diff --git a/translations/ru-RU/content/github/site-policy/github-logo-policy.md b/translations/ru-RU/content/github/site-policy/github-logo-policy.md
index ce0de00a56..a5df64214f 100644
--- a/translations/ru-RU/content/github/site-policy/github-logo-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-logo-policy.md
@@ -7,8 +7,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 You can add {% data variables.product.prodname_dotcom %} logos to your website or third-party application in some scenarios. For more information and specific guidelines on logo usage, see the [{% data variables.product.prodname_dotcom %} Logos and Usage page](https://github.com/logos).
diff --git a/translations/ru-RU/content/github/site-policy/github-marketplace-terms-of-service.md b/translations/ru-RU/content/github/site-policy/github-marketplace-terms-of-service.md
index 29c23bb282..2670f2c811 100644
--- a/translations/ru-RU/content/github/site-policy/github-marketplace-terms-of-service.md
+++ b/translations/ru-RU/content/github/site-policy/github-marketplace-terms-of-service.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Welcome to GitHub Marketplace ("Marketplace")! We're happy you're here. Please read these Terms of Service ("Marketplace Terms") carefully before accessing or using GitHub Marketplace. GitHub Marketplace is a platform that allows you to select developer apps or actions (for free or for a charge) that can be used with your GitHub.com account ("Developer Products"). Although offered by GitHub, Inc. ("GitHub", "we", "us"), Developer Products may be developed and maintained by either GitHub or by third-party software providers. Your selection or use of Developer Products is subject to these Marketplace Terms and any applicable fees, and may require you to agree to additional terms as provided by the third party licensor of that Developer Product (the "Product Provider").
diff --git a/translations/ru-RU/content/github/site-policy/github-privacy-statement.md b/translations/ru-RU/content/github/site-policy/github-privacy-statement.md
index 47988eff46..91f2358576 100644
--- a/translations/ru-RU/content/github/site-policy/github-privacy-statement.md
+++ b/translations/ru-RU/content/github/site-policy/github-privacy-statement.md
@@ -64,7 +64,7 @@ We require some basic information at the time of account creation. When you crea
 ##### Payment information
 If you sign on to a paid Account with us, send funds through the GitHub Sponsors Program, or buy an application on GitHub Marketplace, we collect your full name, address, and credit card information or PayPal information. Please note, GitHub does not process or store your credit card information or PayPal information, but our third-party payment processor does.
 
-If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
+If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
 
 ##### Profile information
 You may choose to give us more information for your Account profile, such as your full name, an avatar which may include a photograph, your biography, your location, your company, and a URL to a third-party website. This information may include User Personal Information. Please note that your profile information may be visible to other Users of our Service.
diff --git a/translations/ru-RU/content/github/site-policy/github-private-information-removal-policy.md b/translations/ru-RU/content/github/site-policy/github-private-information-removal-policy.md
index cdc973b36c..f0b38c51e9 100644
--- a/translations/ru-RU/content/github/site-policy/github-private-information-removal-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-private-information-removal-policy.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 We offer this private information removal process as an exceptional service only for high-risk content that violates [GitHub's Terms of Service](/github/site-policy/github-acceptable-use-policies#3-conduct-restrictions), such as when your security is at risk from exposed access credentials. This guide describes the information GitHub needs from you in order to process a request to remove private information from a repository.
diff --git a/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md b/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md
index c0eaa58df8..ab23d95761 100644
--- a/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md
+++ b/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 GitHub is fortunate to have many developers integrating with our platform. We think that’s awesome, and we want to make that experience even better.  GitHub’s Developer Program (the “Program”) helps us to connect with you, share information with you, and support your creative efforts better than ever before. The special relationship between GitHub and the developer community that the Program creates requires a special set of terms. Welcome to the Registered Developer Agreement (“Agreement”).
diff --git a/translations/ru-RU/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md b/translations/ru-RU/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md
index c9ef28d3f2..230fd2ec97 100644
--- a/translations/ru-RU/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md
+++ b/translations/ru-RU/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 *2018 statement*
diff --git a/translations/ru-RU/content/github/site-policy/github-trademark-policy.md b/translations/ru-RU/content/github/site-policy/github-trademark-policy.md
index 22fe58b146..4e7514ce44 100644
--- a/translations/ru-RU/content/github/site-policy/github-trademark-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-trademark-policy.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 ### What is a GitHub Trademark Policy Violation?
diff --git a/translations/ru-RU/content/github/site-policy/github-username-policy.md b/translations/ru-RU/content/github/site-policy/github-username-policy.md
index 89ef4713f9..5c7abd19a6 100644
--- a/translations/ru-RU/content/github/site-policy/github-username-policy.md
+++ b/translations/ru-RU/content/github/site-policy/github-username-policy.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
diff --git a/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md
index ca969b288e..73fe607515 100644
--- a/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md
+++ b/translations/ru-RU/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md
@@ -3,8 +3,8 @@ title: GitHub's Notice about the California Consumer Privacy Act
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Effective January 1, 2020
diff --git a/translations/ru-RU/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/ru-RU/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
index 25cd66fb34..9ae381250a 100644
--- a/translations/ru-RU/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
+++ b/translations/ru-RU/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
@@ -7,8 +7,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 This guide describes the information that GitHub needs in order to process a DMCA takedown request. If you have more general questions about what the DMCA is or how GitHub processes DMCA takedown requests, please review our [DMCA Takedown Policy](/articles/dmca-takedown-policy).
diff --git a/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
index 95bd441208..1858a54be5 100644
--- a/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
+++ b/translations/ru-RU/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 Are you a law enforcement officer conducting an investigation that may involve user content hosted on GitHub? Or maybe you're a privacy-conscious person who would like to know what information we share with law enforcement and under what circumstances. Either way, you're on the right page.
diff --git a/translations/ru-RU/content/github/site-policy/index.md b/translations/ru-RU/content/github/site-policy/index.md
index 72c9182c43..c147ccd2b3 100644
--- a/translations/ru-RU/content/github/site-policy/index.md
+++ b/translations/ru-RU/content/github/site-policy/index.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 
diff --git a/translations/ru-RU/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md b/translations/ru-RU/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md
index 465e91452a..63bda75c17 100644
--- a/translations/ru-RU/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md
+++ b/translations/ru-RU/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md
@@ -6,8 +6,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 We want to keep GitHub safe for everyone. If you've discovered a security vulnerability in GitHub, we appreciate your help in disclosing it to us in a responsible manner.
diff --git a/translations/ru-RU/content/github/site-policy/submitting-content-removal-requests.md b/translations/ru-RU/content/github/site-policy/submitting-content-removal-requests.md
index 88c636f344..28f2df4d2c 100644
--- a/translations/ru-RU/content/github/site-policy/submitting-content-removal-requests.md
+++ b/translations/ru-RU/content/github/site-policy/submitting-content-removal-requests.md
@@ -5,8 +5,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 We understand that copyrighted, trademarked, or private content may get published on GitHub – either accidentally or on purpose – sometimes in repositories that you do not own. Because the nature of this content varies, and because of different applicable laws, each category has its own, distinct reporting requirements outlined in our policies.
diff --git a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md
index d8c5ccd8f1..53fd800a7e 100644
--- a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md
+++ b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md
@@ -7,8 +7,8 @@ intro: '{% data variables.product.product_name %} uses your repository''s data t
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
  
 ### About {% data variables.product.product_name %}'s use of your data
diff --git a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md
index 4c3f84122a..ed0f336644 100644
--- a/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md
+++ b/translations/ru-RU/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md
@@ -7,8 +7,8 @@ intro: '{% data reusables.user_settings.export-data %}'
 versions:
   free-pro-team: '*'
 topics:
-  - policy
-  - legal
+  - Policy
+  - Legal
 ---
 
 {% data variables.product.product_name %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through settings on {% data variables.product.prodname_dotcom_the_website %} or with the User Migration API.
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index 196bcd6829..e65d927799 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -7,25 +7,19 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
+
 ### Dependency graph availability
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+The dependency graph is available for every repository that defines dependencies in a supported package ecosystem using a supported file format.
 
 {% data reusables.repositories.enable-security-alerts %}
 
 ### About the dependency graph
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
-
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
-
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch,
-{% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated. For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
 
 ### Dependencies included
 
@@ -34,41 +28,32 @@ The dependency graph includes all the dependencies of a repository that are deta
 - Direct dependencies, that are explicitly defined in a manifest or lock file
 - Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
-
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+The dependency graph identifies indirect dependencies.
 
 ### Using the dependency graph
 
 You can use the dependency graph to:
 
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
+- Explore the repositories your code depends on. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."
+- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
 
 ### Enabling the dependency graph
 
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository.
 
 ### Supported package ecosystems
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.
+
+The ecosystems listed below are supported for the dependency graph and {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}.
 
-{% if currentVersion == "free-pro-team@latest" %}The ecosystems listed below are supported for the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot_security_updates %}.{% endif %}
-|
-{% if currentVersion ver_gt "enterprise-server@2.21" %}The ecosystems listed below are supported for the dependency graph and {% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 | Package manager | Языки                            | Recommended formats                                    | All supported formats                                                     |
 | --------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- |
 | Composer        | PHP                              | `composer.lock`                                        | `composer.json`, `composer.lock`                                          |
@@ -88,7 +73,4 @@ The recommended formats explicitly define which versions are used for all direct
 ### Дополнительная литература
 
 - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
index b5f1e57168..0257555e9e 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md
index 46548cb73a..ae6697467a 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content.md
@@ -11,6 +11,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index a7083f548a..d0187f3a03 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -7,29 +7,20 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### Viewing the dependency graph
 
 {% data reusables.repositories.enable-security-alerts %}
 
-The dependency graph shows the dependencies{% if currentVersion == "free-pro-team@latest" %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+The dependency graph shows the dependencies of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. Optionally, under "Dependency graph", click **Dependents**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### Dependencies view
 
-{% if currentVersion == "free-pro-team@latest" %}
-Dependencies are grouped by ecosystem. You can expand a dependency to view its dependencies. For dependencies on public repositories hosted on
-{% data variables.product.product_name %}, you can also click a dependency to view the repository. Dependencies on private repositories, private packages, or unrecognized files are shown in plain text.
-
-If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}.
-
-![График зависимостей](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
 Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to
 {% data variables.product.prodname_dependabot_alerts %}.
@@ -57,59 +48,8 @@ Any direct and indirect dependencies that are specified in the repository's mani
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### Dependents view
-
-For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
-
-![Диаграмма зависимостей](/assets/images/help/graphs/dependents_graph.png)
-
-### Enabling and disabling the dependency graph for a private repository
-
-Repository administrators can enable or disable the dependency graph for private repositories.
-
-You can also enable or disable the dependency graph 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/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
-
-### Changing the "Used by" package
-
-If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
-
-The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
-
-!["Used by" sidebar section](/assets/images/help/repository/used-by-section.png)
-
-Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
-
-The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. ![Choose a "Used by" package](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### Troubleshooting the dependency graph
 
 If your dependency graph is empty, there may be a problem with the file containing your dependencies. Check the file to ensure that it's correctly formatted for the file type.
 
-{% if currentVersion == "free-pro-team@latest" %}
-If the file is correctly formatted, then check its size. The dependency graph ignores individual manifest and lock files that are over 0.5 Mb, unless you are a
-{% data variables.product.prodname_enterprise %} user. It processes up to 20 manifest or lock files per repository by default, so you can split dependencies into smaller files in subdirectories of the repository.{% endif %}
-
 If a manifest or lock file is not processed, its dependencies are omitted from the dependency graph and they can't be checked for vulnerable dependencies.
-
-### Дополнительная литература
-
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)"
-{% endif %}
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md
index f3c9243563..63cab4ba57 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md
index 3532b559f1..1fde203d51 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Forks are listed alphabetically by the username of the person who forked the repository. You can click on the username to be redirected to the user's {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
index 4ebccd26f2..be2da0bdec 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories.md
@@ -9,6 +9,6 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
index 8e0ba10525..4a9f157361 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md
@@ -11,7 +11,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ### About contributors
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md
index f1648929dc..8f73314241 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network.md
@@ -10,7 +10,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 ![Repository network graph](/assets/images/help/graphs/repo_network_graph.png)
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md
index a5e0b26677..0f21dad59d 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 Commit co-authors are included in the commit activity summary if their commits were merged into the repository's default branch and they're in the top 15 users who have contributed the most commits.
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md
index 4d27f9e82b..ccde39f294 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository.md
@@ -7,7 +7,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 You can navigate to referring sites, excluding search engines and {% data variables.product.product_name %} itself, from the links the specific paths were referred from. The popular content links to the specific content that generated traffic.
diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md
index 48dd24deb2..3997a66ce5 100644
--- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md
+++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - repositories
+  - Repositories
 ---
 
 The top graph shows commits for the entire year by week.
diff --git a/translations/ru-RU/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/ru-RU/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index 1c6d2dc982..548e36254c 100644
--- a/translations/ru-RU/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/ru-RU/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: About GitHub Premium Support for GitHub Enterprise Cloud
-intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_one %} customers.'
+intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_ghe_cloud %} customers.'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
diff --git a/translations/ru-RU/content/github/working-with-github-support/about-github-support.md b/translations/ru-RU/content/github/working-with-github-support/about-github-support.md
index 29888a41f9..0d30d628b5 100644
--- a/translations/ru-RU/content/github/working-with-github-support/about-github-support.md
+++ b/translations/ru-RU/content/github/working-with-github-support/about-github-support.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - jobs
+  - Jobs
 ---
 
 ### About {% data variables.contact.github_support %}
diff --git a/translations/ru-RU/content/github/working-with-github-support/github-enterprise-cloud-support.md b/translations/ru-RU/content/github/working-with-github-support/github-enterprise-cloud-support.md
index 412a41aeca..2fd3025988 100644
--- a/translations/ru-RU/content/github/working-with-github-support/github-enterprise-cloud-support.md
+++ b/translations/ru-RU/content/github/working-with-github-support/github-enterprise-cloud-support.md
@@ -8,7 +8,7 @@ intro: '{% data variables.product.prodname_ghe_cloud %} includes a target eight-
 versions:
   free-pro-team: '*'
 topics:
-  - jobs
+  - Jobs
 ---
 
 {% note %}
diff --git a/translations/ru-RU/content/github/working-with-github-support/index.md b/translations/ru-RU/content/github/working-with-github-support/index.md
index 5e266237af..dd626535ef 100644
--- a/translations/ru-RU/content/github/working-with-github-support/index.md
+++ b/translations/ru-RU/content/github/working-with-github-support/index.md
@@ -6,7 +6,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - jobs
+  - Jobs
 ---
 
 
diff --git a/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md
index b0679a98b8..6f025196f7 100644
--- a/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/ru-RU/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ For more information on creating links, see "[Basic writing and formatting synta
 
 ### Issues and pull requests
 
-Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links. For more information, see "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)."
+Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links.
 
 {% note %}
 
diff --git a/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index 821a3f56f6..a0f9e5c91f 100644
--- a/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/ru-RU/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -23,7 +23,7 @@ To create a heading, add one to six `#` symbols before your heading text. The nu
 
 ### Styling text
 
-You can indicate emphasis with bold, italic, or strikethrough text.
+You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files.
 
 | Style                  | Syntax             | Keyboard shortcut   | Пример                                   | Output                                 |
 | ---------------------- | ------------------ | ------------------- | ---------------------------------------- | -------------------------------------- |
@@ -205,6 +205,10 @@ Content attachments will not be displayed for URLs that are part of a markdown l
 
 For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."
 
+### Uploading assets
+
+You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and `.md` files in your repository.
+
 ### Using emoji
 
 You can add emoji to your writing by typing `:EMOJICODE:`.
diff --git a/translations/ru-RU/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/ru-RU/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index eefa9c953e..09c363a2b5 100644
--- a/translations/ru-RU/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/ru-RU/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### Syntax highlighting
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 You can add an optional language identifier to enable syntax highlighting in your fenced code block.
 
diff --git a/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md b/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md
index 8843f5d892..4f0f913f2e 100644
--- a/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md
+++ b/translations/ru-RU/content/graphql/guides/introduction-to-graphql.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### GraphQL terminology
diff --git a/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md
index f51a5ec5e3..482400fc20 100644
--- a/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md
+++ b/translations/ru-RU/content/graphql/guides/migrating-from-rest-to-graphql.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### Differences in API logic
diff --git a/translations/ru-RU/content/graphql/guides/using-global-node-ids.md b/translations/ru-RU/content/graphql/guides/using-global-node-ids.md
index 80ef4ebd38..8780071951 100644
--- a/translations/ru-RU/content/graphql/guides/using-global-node-ids.md
+++ b/translations/ru-RU/content/graphql/guides/using-global-node-ids.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 You can access most objects in GitHub (users, issues, pull requests, etc.) using either the REST API or the GraphQL API. With a [recent update](https://developer.github.com/changes/2017-12-19-graphql-node-id/), you can find the **global node ID** of many objects from within the REST API and use these IDs in your GraphQL operations.
diff --git a/translations/ru-RU/content/graphql/guides/using-the-explorer.md b/translations/ru-RU/content/graphql/guides/using-the-explorer.md
index 632c0b17fe..8a4f907cb8 100644
--- a/translations/ru-RU/content/graphql/guides/using-the-explorer.md
+++ b/translations/ru-RU/content/graphql/guides/using-the-explorer.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ## About the GraphQL Explorer
diff --git a/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md
index 4107b67e77..f3fb6e64a1 100644
--- a/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ Return type fields:
 
 ## Поиск
 
-Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see ["Queries](/graphql/reference/queries#searchresultitemconnection)."
+Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/ru-RU/content/graphql/overview/breaking-changes.md b/translations/ru-RU/content/graphql/overview/breaking-changes.md
index 6cdf450bef..30ae5ee702 100644
--- a/translations/ru-RU/content/graphql/overview/breaking-changes.md
+++ b/translations/ru-RU/content/graphql/overview/breaking-changes.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About breaking changes
@@ -27,7 +27,7 @@ We'll announce upcoming breaking changes at least three months before making cha
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> A change will be made to <code>{{ change.location }}</code>.
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> A change will be made to <code>{{ change.location }}</code>.
 
 <p><b>Description:</b> {{ change.description }}</p>
 
diff --git a/translations/ru-RU/content/graphql/overview/changelog.md b/translations/ru-RU/content/graphql/overview/changelog.md
index 3ecd22c955..b70a7fc628 100644
--- a/translations/ru-RU/content/graphql/overview/changelog.md
+++ b/translations/ru-RU/content/graphql/overview/changelog.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 Breaking changes include changes that will break existing queries or could affect the runtime behavior of clients. For a list of breaking changes and when they will occur, see our [breaking changes log](/graphql/overview/breaking-changes).
diff --git a/translations/ru-RU/content/graphql/overview/public-schema.md b/translations/ru-RU/content/graphql/overview/public-schema.md
index 81dceae4a8..9bf94828b0 100644
--- a/translations/ru-RU/content/graphql/overview/public-schema.md
+++ b/translations/ru-RU/content/graphql/overview/public-schema.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 You can [perform introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) against the GraphQL API directly.
diff --git a/translations/ru-RU/content/graphql/overview/resource-limitations.md b/translations/ru-RU/content/graphql/overview/resource-limitations.md
index 9056b21ed0..6d5e7a5c84 100644
--- a/translations/ru-RU/content/graphql/overview/resource-limitations.md
+++ b/translations/ru-RU/content/graphql/overview/resource-limitations.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ## Node limit
diff --git a/translations/ru-RU/content/graphql/overview/schema-previews.md b/translations/ru-RU/content/graphql/overview/schema-previews.md
index d653fad776..90c1d85a49 100644
--- a/translations/ru-RU/content/graphql/overview/schema-previews.md
+++ b/translations/ru-RU/content/graphql/overview/schema-previews.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About schema previews
diff --git a/translations/ru-RU/content/graphql/reference/enums.md b/translations/ru-RU/content/graphql/reference/enums.md
index 108b9b8be4..c1226715b1 100644
--- a/translations/ru-RU/content/graphql/reference/enums.md
+++ b/translations/ru-RU/content/graphql/reference/enums.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About enums
diff --git a/translations/ru-RU/content/graphql/reference/input-objects.md b/translations/ru-RU/content/graphql/reference/input-objects.md
index 35065838c7..72fe36ae79 100644
--- a/translations/ru-RU/content/graphql/reference/input-objects.md
+++ b/translations/ru-RU/content/graphql/reference/input-objects.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About input objects
@@ -19,6 +19,5 @@ For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) tak
 
 For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/ru-RU/content/graphql/reference/interfaces.md b/translations/ru-RU/content/graphql/reference/interfaces.md
index 175ff95b3d..2d6baa8031 100644
--- a/translations/ru-RU/content/graphql/reference/interfaces.md
+++ b/translations/ru-RU/content/graphql/reference/interfaces.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About interfaces
diff --git a/translations/ru-RU/content/graphql/reference/mutations.md b/translations/ru-RU/content/graphql/reference/mutations.md
index f523fd3168..d00268eb02 100644
--- a/translations/ru-RU/content/graphql/reference/mutations.md
+++ b/translations/ru-RU/content/graphql/reference/mutations.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About mutations
diff --git a/translations/ru-RU/content/graphql/reference/objects.md b/translations/ru-RU/content/graphql/reference/objects.md
index c99b46cca6..59402cc63b 100644
--- a/translations/ru-RU/content/graphql/reference/objects.md
+++ b/translations/ru-RU/content/graphql/reference/objects.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About objects
diff --git a/translations/ru-RU/content/graphql/reference/scalars.md b/translations/ru-RU/content/graphql/reference/scalars.md
index 8df4267a78..fb24332e20 100644
--- a/translations/ru-RU/content/graphql/reference/scalars.md
+++ b/translations/ru-RU/content/graphql/reference/scalars.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About scalars
diff --git a/translations/ru-RU/content/graphql/reference/unions.md b/translations/ru-RU/content/graphql/reference/unions.md
index 9b7381ec3f..e16eb60b28 100644
--- a/translations/ru-RU/content/graphql/reference/unions.md
+++ b/translations/ru-RU/content/graphql/reference/unions.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About unions
diff --git a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index 20259e722f..3438674ea4 100644
--- a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: Metrics available with GitHub Insights
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %} includes a variety of metrics to give you visibility into your team''s software delivery process.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index 1d4e6eb413..aee7193685 100644
--- a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Navigating between GitHub Enterprise and GitHub Insights
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index b8f8cfd53d..7c5c5ea881 100644
--- a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Setting your timezone for GitHub Insights
 intro: 'You can set the timezone for metrics you view in {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 833f2f5777..a8c4b1b728 100644
--- a/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/ru-RU/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing key metrics and reports
 intro: You can view and filter key metrics and reports to help you understand and improve your software delivery process through data.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index 298e41ff48..152a16edd3 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: About data in GitHub Insights
 intro: 'The data included in {% data variables.product.prodname_insights %} metrics is highly customizable.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index f84e621f8b..5931b15d06 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: About GitHub Insights
 intro: '{% data variables.product.prodname_insights %} provides metrics and analytical reports to help engineering teams understand and improve their software delivery process.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
index d383b614f3..6aac89c215 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring the connection between GitHub Insights and GitHub Enterprise
 intro: 'You can manage how {% data variables.product.prodname_insights %} connects to {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can configure the connection to {% data variables.product.prodname_enterprise %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index e3d8eea29a..11ee06287c 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Enabling a link between GitHub Insights and GitHub Enterprise
 intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index 7a6732b8f9..f554af41b8 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Installing GitHub Insights
 intro: 'You can install {% data variables.product.prodname_insights %} and connect the standalone application to {% data variables.product.prodname_ghe_server %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index f6344ccd82..b2deeb9d34 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: Managing available metrics and reports
 intro: 'You can enable and disable specific metrics across {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
index 12be82871c..6d5ea396b7 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
@@ -1,7 +1,6 @@
 ---
 title: Managing contributors and teams
 intro: You can manage the people and teams included in metrics and reports.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage contributors and teams.'
@@ -98,7 +97,7 @@ You can create and manage custom teams in {% data variables.product.prodname_ins
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.teams-tab %}
 {% data reusables.github-insights.edit-team %}
-3. To the right of the contributor you'd like to remove, click {% octicon "trashcan" aria-label="The trashcan icon" %}. ![Trashcan button](/assets/images/help/insights/contributor-trashcan.png)
+3. To the right of the contributor you'd like to remove, click {% octicon "trash" aria-label="The trash icon" %}. ![trash button](/assets/images/help/insights/contributor-trashcan.png)
 
 #### Renaming a custom team
 
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-events.md
index d64fb180f8..a70c80de3a 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-events.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-events.md
@@ -1,7 +1,6 @@
 ---
 title: Managing events
 intro: '{% data reusables.github-insights.events %}'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-events
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage events.'
@@ -29,5 +28,5 @@ After you create an event in {% data variables.product.prodname_insights %}, any
 
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.events-tab %}
-3. To the right of the event you want to delete, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Trash can button](/assets/images/help/insights/trashcan-button.png)
+3. To the right of the event you want to delete, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Trash can button](/assets/images/help/insights/trashcan-button.png)
 4. Click **Confirm**.
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-goals.md
index 5f779abc01..c7364eded7 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: Managing goals
 intro: You can use goals to set targets for key metrics and measure success reaching those targets.
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 08f932de21..cdcf82b9e3 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -1,7 +1,6 @@
 ---
 title: Managing organizations
 intro: 'You can manage the {% data variables.product.prodname_enterprise %} organizations that are included in metrics.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index f747452514..8bf8c4d001 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Managing permissions in GitHub Insights
 intro: 'You can update a user''s permissions in {% data variables.product.prodname_insights %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-repositories.md
index 1f443eca96..920cf3d94b 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-repositories.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/managing-repositories.md
@@ -1,10 +1,9 @@
 ---
 title: Managing repositories
 intro: 'You can manage the repositories connected to {% data variables.product.prodname_insights %} and the data included in metrics for each repository.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-repositories
-permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories.'
+permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories. '
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index 587e055bb9..dd7ddd3633 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: System overview for GitHub Insights
 intro: '{% data variables.product.prodname_insights %} is a standalone application which interfaces with {% data variables.product.prodname_enterprise %}.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index e17b23f341..20cca11a52 100644
--- a/translations/ru-RU/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/ru-RU/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: Updating GitHub Insights
 intro: 'You can update to the latest version of {% data variables.product.prodname_insights %} to benefit from improvements and bug fixes.'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index f2dda89e95..0b0df77983 100644
--- a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.organizations.organizations_include %}
diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
index 6b42ae2b62..60548ec9fd 100644
--- a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
+++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 ### Accessing your organization dashboard
diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
index 728b1ac690..cdc80b08e1 100644
--- a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
+++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
@@ -11,8 +11,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}.
diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index eab2e56131..05690aca24 100644
--- a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -15,8 +15,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md
index 1cff1af763..cb93764372 100644
--- a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md
+++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /about-organizations %}
@@ -19,4 +19,4 @@ topics:
 {% link_in_list /creating-a-new-organization-from-scratch %}
 {% link_in_list /accessing-your-organizations-settings %}
 {% link_in_list /about-your-organizations-news-feed %}
-{% link_in_list /viewing-insights-for-your-organization %}
\ No newline at end of file
+{% link_in_list /viewing-insights-for-your-organization %}
diff --git a/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md
index f344a8cfbd..6b125f6fd5 100644
--- a/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -43,7 +43,7 @@ For more information, see {% if currentVersion == "free-pro-team@latest" or curr
 
 ### Дополнительная литература
 
-- "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)"
+- "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
 - "[About teams](/articles/about-teams)"
 - "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)"
 - "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)"
diff --git a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
index 9406a2c559..16fea7cfa0 100644
--- a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
+++ b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
@@ -7,10 +7,10 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %}
 {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %}
-{% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %}
\ No newline at end of file
+{% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %}
diff --git a/translations/ru-RU/content/organizations/index.md b/translations/ru-RU/content/organizations/index.md
index 0cfd817912..fe1a54c544 100644
--- a/translations/ru-RU/content/organizations/index.md
+++ b/translations/ru-RU/content/organizations/index.md
@@ -11,8 +11,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_with_intro /collaborating-with-groups-in-organizations %}
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md
index f3cdc109bd..0e6fcbceb7 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %}
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
-{% link_in_list /reviewing-your-organizations-installed-integrations %}
\ No newline at end of file
+{% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index e89cbfb4a9..f6edcdcffd 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -8,8 +8,8 @@ versions:
   free-pro-team: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Organization owners can manage allowed IP addresses for an organization.
@@ -26,9 +26,8 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 
 ### Adding an allowed IP address
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 
 ### Enabling allowed IP addresses
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. Under "IP allow list", select **Enable IP allow list**. ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. Click **Save**.
 
 ### Editing an allowed IP address
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 
 ### Deleting an allowed IP address
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index e83422b657..bbe611c2c5 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### Displaying the security and analysis settings
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
@@ -50,33 +49,38 @@ You can enable or disable features for all repositories. {% if currentVersion ==
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
 2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. Optionally, enable the feature by default for new repositories in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Enable by default" option for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -85,11 +89,14 @@ You can enable or disable features for all repositories. {% if currentVersion ==
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
 2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -122,7 +129,7 @@ To allow {% data variables.product.prodname_dependabot %} to access a private {%
 You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
 
 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
-1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. The size of your license is shown for organization-level licenses. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
+1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}.
 1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}.
 
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md
index a23a4647fe..e3b416ee3e 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md
@@ -8,8 +8,8 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 We recommend that you notify {% if currentVersion == "free-pro-team@latest" %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} at least one week before you require 2FA in your organization.
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index bf91950f73..3455b4e51f 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ Before you require use of two-factor authentication, we recommend notifying {% i
 
 ### Requiring two-factor authentication in your organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..97c7a9133a
--- /dev/null
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About email restrictions
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. For more information about outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)."
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index 73e8b41318..ac16f11648 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
 
 ### Searching the audit log
@@ -36,6 +35,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`учетная запись`](#account-category-actions)                                                                                                                                                                                                                                                                                                                               | Contains all activities related to your organization account.                                                                                                                                                                                                                                                                                                                                                 |
 | [`advisory_credit`](#advisory_credit-category-actions)                                                                                                                                                                                                                                                                                                                      | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."                                                                        |
 | [`выставление счетов`](#billing-category-actions)                                                                                                                                                                                                                                                                                                                           | Contains all activities related to your organization's billing.                                                                                                                                                                                                                                                                                                                                               |
+| [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                                                                                                                | Contains all activities related to your organization's codespaces.                                                                                                                                                                                                                                                                                                                                            |
 | [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                                                                                                                  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."                                                                                                        |
 | [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions)                                                                                                                                                                                                                                                                                              | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization.                                                                                                                                                                                                                                             |
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                                                                                                              | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."                                                      |
@@ -191,6 +191,20 @@ An overview of some of the most common actions that are recorded as events in th
 | `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). |
 | `change_email`        | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes.                                              |
 
+#### `codespaces` category actions
+
+| Действие                     | Description                                                                                                                                                                                                                                    |
+| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                     | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                   |
+| `resume`                     | Triggered when a user resumes a suspended codespace.                                                                                                                                                                                           |
+| `delete - Удалить`           | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                   |
+| `create_an_org_secret`       | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)  |
+| `update_an_org_secret`       | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `remove_an_org_secret`       | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+
+
+
 #### `dependabot_alerts` category actions
 
 | Действие    | Description                                                                                                                                                                                                                                                                                                                                                                                                            |
@@ -484,6 +498,38 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_linear_history_requirement_enforcement_level` | Triggered when required linear commit history is enabled or disabled for a protected branch.                                                                                                                                           |
 {% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `pull_request` category actions
+
+| Действие                | Description                                                                                                |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `create`                | Triggered when a pull request is created.                                                                  |
+| `close`                 | Triggered when a pull request is closed without being merged.                                              |
+| `reopen`                | Triggered when a pull request is reopened after previously being closed.                                   |
+| `слияние`               | Triggered when a pull request is merged.                                                                   |
+| `indirect_merge`        | Triggered when a pull request is considered merged because its commits were merged into the target branch. |
+| `ready_for_review`      | Triggered when a pull request is marked as ready for review.                                               |
+| `converted_to_draft`    | Triggered when a pull request is converted to a draft.                                                     |
+| `create_review_request` | Triggered when a review is requested.                                                                      |
+| `remove_review_request` | Triggered when a review request is removed.                                                                |
+
+#### `pull_request_review` category actions
+
+| Действие           | Description                           |
+| ------------------ | ------------------------------------- |
+| `отправить`        | Triggered when a review is submitted. |
+| `отклонить`        | Triggered when a review is dismissed. |
+| `delete - Удалить` | Triggered when a review is deleted.   |
+
+#### `pull_request_review_comment` category actions
+
+| Действие           | Description                                 |
+| ------------------ | ------------------------------------------- |
+| `create`           | Triggered when a review comment is added.   |
+| `обновление`       | Triggered when a review comment is changed. |
+| `delete - Удалить` | Triggered when a review comment is deleted. |
+{% endif %}
+
 #### `repo` category actions
 
 | Действие                              | Description                                                                                                                                                                                                                                                                                                                                        |
@@ -593,22 +639,24 @@ For more information, see "[Managing the publication of {% data variables.produc
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` category actions
 
-| Действие                                       | Description                                                                                                                                                                                                                                                                                                              |
-| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `repo_funding_link_button_toggle`              | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                              |
-| `repo_funding_links_file_action`               | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                         |
-| `sponsor_sponsorship_cancel`                   | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                         |
-| `sponsor_sponsorship_create`                   | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")                                                                                                                           |
-| `sponsor_sponsorship_preference_change`        | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/articles/managing-your-sponsorship)")                                                                                                                                                            |
-| `sponsor_sponsorship_tier_change`              | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                     |
-| `sponsored_developer_approve`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
-| `sponsored_developer_create`                   | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
-| `sponsored_developer_profile_update`           | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
-| `sponsored_developer_request_approval`         | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
-| `sponsored_developer_tier_description_update`  | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
-| sponsored_developer_update_newsletter_send | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)")                                                                                                                                                                                          |
-| `waitlist_invite_sponsored_developer`          | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
-| `waitlist_join`                                | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
+| Действие                                      | Description                                                                                                                                                                                                                                                                                                     |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                                                |
+| `repo_funding_links_file_action`              | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                |
+| `sponsor_sponsorship_cancel`                  | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                |
+| `sponsor_sponsorship_create`                  | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                      |
+| `sponsor_sponsorship_preference_change`       | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                                               |
+| `sponsor_sponsorship_tier_change`             | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")                                                                                                            |
+| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                     |
+| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                      |
+| `sponsored_developer_disable`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled                                                                                                                                                                                                                          |
+| `sponsored_developer_redraft`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state                                                                                                                                                                                       |
+| `sponsored_developer_profile_update`          | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") |
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                            |
+| `sponsored_developer_update_newsletter_send`  | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                                                  |
+| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")    |
+| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")                                    |
 {% endif %}
 
 #### `team` category actions
diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index 4e7d59f603..6db88dddd8 100644
--- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -10,13 +10,12 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**. ![Installed {% data variables.product.prodname_github_app %}s tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png)
 6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index ca20fd0155..37fa299f8c 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ For more information about {% data variables.product.prodname_github_app %} mana
 
 ### Giving someone the ability to manage all {% data variables.product.prodname_github_app %}s owned by the organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "Management", type the username of the person you want to designate as a {% data variables.product.prodname_github_app %} manager in the organization, and click **Grant**. ![Add a {% data variables.product.prodname_github_app %} manager](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### Giving someone the ability to manage an individual {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to add a {% data variables.product.prodname_github_app %} manager for. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md
index 07610efc3f..fca2b094b0 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md
@@ -10,9 +10,9 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /adding-github-app-managers-in-your-organization %}
-{% link_in_list /removing-github-app-managers-from-your-organization %}
\ No newline at end of file
+{% link_in_list /removing-github-app-managers-from-your-organization %}
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index 3836f39704..5bcb8d14e9 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ For more information about {% data variables.product.prodname_github_app %} mana
 
 ### Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "Management", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**. ![Revoke {% data variables.product.prodname_github_app %} manager permissions](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. Under "{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to remove a {% data variables.product.prodname_github_app %} manager from. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
index 26843c4457..c70d55f0b6 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a project board in your organization.
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md
index 22f18b40c8..b6376df04a 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /project-board-permissions-for-an-organization %}
@@ -19,4 +19,4 @@ topics:
 {% link_in_list /managing-team-access-to-an-organization-project-board %}
 {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %}
 {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %}
-{% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %}
\ No newline at end of file
+{% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %}
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 14426751a6..d811edf2ce 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% warning %}
@@ -49,4 +49,4 @@ If a team's access to a project board is inherited from a parent team, you must
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png)
-5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png)
+5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trash" aria-label="The trash icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
index 4c2d3ff3cf..2fa71ab870 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md
index 3570e12c1d..e6821cbb38 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md
@@ -7,8 +7,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 You can view a list of all people with pending invitations to become an outside collaborator on any repository owned by your organization.
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md
index b8b30ba6d4..948806389c 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md
@@ -11,8 +11,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /repository-permission-levels-for-an-organization %}
@@ -25,4 +25,4 @@ topics:
 {% link_in_list /removing-an-outside-collaborator-from-an-organization-repository %}
 {% link_in_list /converting-an-organization-member-to-an-outside-collaborator %}
 {% link_in_list /converting-an-outside-collaborator-to-an-organization-member %}
-{% link_in_list /reinstating-a-former-outside-collaborators-access-to-your-organization %}
\ No newline at end of file
+{% link_in_list /reinstating-a-former-outside-collaborators-access-to-your-organization %}
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index eb2d8d0dc8..dd8e9b74e7 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ In addition to managing organization-level settings, organization owners have ad
 | Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)")                                                                                                                                                                                                                                                                    |       |               |       |          |                                                                       **X**                                                                        |
 | Change a repository's settings                                                                                                                                                                                                                                                                                                                                                     |       |               |       |          |                                                                       **X**                                                                        |
 | Manage team and collaborator access to the repository                                                                                                                                                                                                                                                                                                                              |       |               |       |          |                                                                       **X**                                                                        |
-| Edit the repository's default branch                                                                                                                                                                                                                                                                                                                                               |       |               |       |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| Edit the repository's default branch                                                                                                                                                                                                                                                                                                                                               |       |               |       |          |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                                           |       |               |       |          |                                                                       **X**                                                                        |
 | Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)")                                                                                                                                                                                                                                       |       |               | **X** |  **X**   |                                                                 **X** 
 {% endif %}
@@ -142,7 +142,8 @@ In addition to managing organization-level settings, organization owners have ad
 | [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                         |       |     **X**     | **X** |  **X**   |                                                                       **X**                                                                        |
 | [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                          |       |     **X**     | **X** |  **X**   |                                                                       **X**                                                                        |
 | [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                       | **X** |     **X**     | **X** |  **X**   |                                                                       **X**                                                                        |
-| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                          |       |               |       |  **X**   |                                                                 **X** 
+| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                          |       |               |       |  **X**   |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                  |       |               | **X** |  **X**   |                                                                 **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ In this section, you can find the repository permission levels required for secu
 
 | Repository action                                                                                                                                                                                                                                                             | Read  | Приоритизация |        Write        |      Maintain       |                                                                             Admin                                                                             |
 |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                                                                             |       |               |                     |                     |                                                                                                                                                               |
-| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository                                                                           |       |               |                     |                     |                                                                             **X**                                                                             |
-| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                |       |               |                     |                     |                                                                             **X**                                                                             |
-| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies    |       |               |                     |                     |                                                                             **X**                                                                             |
-| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)                                                                                                                                                                      |       |               |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |               |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                                                                           |       |               |                     |                     |                                                                                                                                                               |
+| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository                                                                                |       |               |                     |                     |                                                                             **X**                                                                             |
+| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                                                                                     |       |               |                     |                     |                                                                             **X**                                                                             |
+| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies    |       |               |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [security advisories](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                                                             |       |               |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") |       |               |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository                                                                                                                                       |       |               |                     |                     |                                                                             **X**                                                                             |
 | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                       | **X** |     **X**     |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                                                                         | **X** |     **X**     |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index 4bd43bb6f0..413bb61b87 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ If someone with admin permissions to an organization's repository grants a membe
 
 ### Setting base permissions
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Base permissions", use the drop-down to select new base permissions. ![Selecting new permission level from base permissions drop-down](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. Review the changes. To confirm, click **Change default permission to PERMISSION**. ![Reviewing and confirming change of base permissions](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
index 70fba13ca5..0ff5bd2bb3 100644
--- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
+++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Administrators can use this information to help off-board people, gather data for compliance, and other general security checkups.
diff --git a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index 7b371b9ae4..b807a722b7 100644
--- a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)."
diff --git a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
index 8bdd4f0224..f9c23de4e4 100644
--- a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
+++ b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -11,9 +11,9 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /about-ssh-certificate-authorities %}
-{% link_in_list /managing-your-organizations-ssh-certificate-authorities %}
\ No newline at end of file
+{% link_in_list /managing-your-organizations-ssh-certificate-authorities %}
diff --git a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index 775efdaa45..60426bc12d 100644
--- a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Organization owners can manage an organization's SSH certificate authorities (CA).
@@ -22,17 +22,15 @@ You can allow members to access your organization's repositories using SSH certi
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### Deleting an SSH certificate authority
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
index f13fa6a80f..420c5a2808 100644
--- a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
+++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
@@ -8,8 +8,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Because you access an organization by logging in to a personal account, each of your team members needs a personal account. Once you have user names for each person you'd like to add to your organization, you can add them to teams.
diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md
index f28c95e40d..89f6c7c91e 100644
--- a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md
+++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /inviting-users-to-join-your-organization %}
@@ -20,4 +20,4 @@ topics:
 {% link_in_list /adding-people-to-your-organization %}
 {% link_in_list /removing-a-member-from-your-organization %}
 {% link_in_list /reinstating-a-former-member-of-your-organization %}
-{% link_in_list /can-i-create-accounts-for-people-in-my-organization %}
\ No newline at end of file
+{% link_in_list /can-i-create-accounts-for-people-in-my-organization %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index 2b4f1b54a6..90801f8d04 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -9,17 +9,16 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 By default, issues cannot be deleted in an organization's repositories. An organization owner must enable this feature for all of the organization's repositories first.
 
 Once enabled, organization owners and people with admin permissions in an organization-owned repository can delete issues. People with admin permissions in a repository include organization members and outside collaborators with admin privileges. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)" and "[Deleting an issue](/articles/deleting-an-issue)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Issue deletion", select **Allow members to delete issues for this organization**. ![Checkbox to allow people to delete issues](/assets/images/help/settings/issue-deletion.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index c262ff9885..5c75ddf307 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -8,17 +8,16 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default.
 
 Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing a policy on dependency insights in your enterprise account](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**. ![Checkbox to allow members to view insights](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
index a10c0b1708..412aaa955b 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
@@ -8,8 +8,8 @@ versions:
   enterprise-server: '>=2.23'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.actions.about-artifact-log-retention %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
index 134897705c..91d41ce717 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
@@ -8,8 +8,8 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 9ab30b3656..a55928f3ee 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -28,7 +28,6 @@ Once you delete an organization, GitHub **cannot restore your content**. Therefo
 
 ### 2. Delete the organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Near the bottom of the organization's settings page, click **Delete this Organization**. ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index ba9aed9fc1..84f63f9764 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -8,8 +8,8 @@ versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -27,9 +27,8 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for
 
 ### Managing {% data variables.product.prodname_actions %} permissions for your organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Local and third-party Actions**, select an option. ![Enable, disable, or limit actions for this organization](/assets/images/help/repository/enable-org-actions.png)
 1. Click **Save**.
@@ -50,9 +49,8 @@ You can disable all workflows for an organization or set a policy that configure
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Policies**, select an option. ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png)
 1. Click **Save**.
@@ -61,9 +59,8 @@ You can disable all workflows for an organization or set a policy that configure
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. Click **Save**.
@@ -77,9 +74,27 @@ You can disable all workflows for an organization or set a policy that configure
 
 #### Configuring the private fork policy for an organization
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### Setting the permissions of the `GITHUB_TOKEN` for your organization
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you choose the restricted option as the default in your organization settings, the same option is auto-selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and the more restricted default has been selected in the enterprise settings, you won't be able to choose the more permissive default in your organization settings.
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### Configuring the default `GITHUB_TOKEN` permissions
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. Click **Save** to apply the settings.
+{% endif %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/index.md b/translations/ru-RU/content/organizations/managing-organization-settings/index.md
index 407237383f..44acf14e45 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/index.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/index.md
@@ -9,11 +9,11 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index 9b2ad46fc5..e0012b5bf5 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ Default labels are included in every new repository in your organization, but an
 
 ### Creating a default label
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ Default labels are included in every new repository in your organization, but an
 
 ### Editing a default label
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ Default labels are included in every new repository in your organization, but an
 
 ### Deleting a default label
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 2438a3aa07..fbb1f6481e 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. Click **Save**. !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png)
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index e5859e4feb..54dbd5e1e9 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ Organization owners can schedule a reminder for one or more teams in their organ
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### Creating a scheduled reminder for an organization
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ Organization owners can schedule a reminder for one or more teams in their organ
 {% data reusables.reminders.create-reminder %}
 
 ### Managing a scheduled reminder for an organization
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ Organization owners can schedule a reminder for one or more teams in their organ
 {% data reusables.reminders.update-buttons %}
 
 ### Deleting a scheduled reminder for an organization
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index d225742587..1b345f8e4b 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ If an enterprise owner has enforced a policy for the default branch name for you
 
 ### Setting the default branch name
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. Under "Repository default branch", click **Change default branch name now**. ![Override button](/assets/images/help/organizations/repo-default-name-button.png)
 4. Type the default name that you would like to use for new branches. ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 625d7c1471..25cf4001fd 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Organization owners can manage the display of member names in an organization.
@@ -20,9 +20,8 @@ Organization owners can manage the display of member names in an organization.
 
 Each organization member chooses their own profile name in their settings. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Admin repository permissions", select or unselect **Allow members to see comment author's profile name in private repositories**. ![Checkbox to allow members to see comment author's full name in private repositories](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index a5ab059c52..7cec2b94f2 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ If you allow forking of private{% if currentVersion == "free-pro-team@latest" or
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**. ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
index 1db6ef0c01..e58f0e0e5c 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -21,9 +21,8 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
 
 If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
 1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
 1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index 7bfa22cf18..af6eb9cdb5 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates.
 
-You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)."
+You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. Click **Update profile**. ![Update profile button](/assets/images/help/organizations/update-profile-button.png)
 
 ### Дополнительная литература
 
-- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)"
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md
index ab24e857f4..39469acbb2 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -40,9 +40,8 @@ After changing your organization's name:
 
 ### Changing your organization's name
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**. ![Rename organization button](/assets/images/help/settings/settings-rename-organization.png)
 
 ### Дополнительная литература
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index f004cf1151..e8246f8ca4 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 You can choose whether members can create repositories in your organization. If you allow members to create repositories, you can choose which types of repositories members can create.{% if currentVersion == "free-pro-team@latest" %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %} For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)."
@@ -27,9 +27,8 @@ Organization owners can always create any type of repository.
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository creation", select one or more options. ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index 2374bbf81e..ac1afd02de 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ You can restrict the ability to change repository visibility to organization own
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository visibility change", deselect **Allow members to change repository visibilities for this organization**. ![Checkbox to allow members to change repository visibility](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index acec392575..cb887e6729 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -11,17 +11,16 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Organization owners, and members with admin privileges for a repository, can invite outside collaborators to work on the repository. You can also restrict outside collaborator invite permissions to only organization owners.
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 9db1d155b8..ca79374550 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -10,15 +10,14 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Owners can set permissions for deleting or transferring repositories in an organization.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Repository deletion and transfer", select or deselect **Allow members to delete or transfer repositories for this organization**. ![Checkbox to allow members to delete repositories](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index c641903238..3ceab7932a 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -9,17 +9,16 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Organization owners can set team creation permissions.
 
 If you do not set team creation permissions, all organization members will be able to create teams by default.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. Under "Team creation rules", select or deselect **Allow members to create teams**. ![Checkbox to allow members to create teams](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md
index 36919bf9d1..99a930a85b 100644
--- a/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 1. If you're the only member with *owner* privileges, give another organization member the owner role. For more information, see "[Appointing an organization owner](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)."
diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..528c73b1bc
--- /dev/null
+++ b/translations/ru-RU/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About domain verification
+
+After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
+
+If your organization is owned by an enterprise account, a "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output.
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service. ![Verified badge](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index d28295df68..510a304726 100644
--- a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ Billing managers **are not** able to:
 
 The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. Next to Billing managers, click **Add a billing manager**. ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png)
 6. Type the username or email address of the person you want to add and click **Send invitation**. ![Invite billing manager page](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md
index 481560522e..82e900117e 100644
--- a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md
+++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.organizations.team_maintainers_can %}
diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
index a6fedeb7bc..3ec8de5c84 100644
--- a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
+++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
@@ -10,12 +10,12 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /permission-levels-for-an-organization %}
 {% link_in_list /maintaining-ownership-continuity-for-your-organization %}
 {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %}
 {% link_in_list /adding-a-billing-manager-to-your-organization %}
-{% link_in_list /removing-a-billing-manager-from-your-organization %}
\ No newline at end of file
+{% link_in_list /removing-a-billing-manager-from-your-organization %}
diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index 07a0373218..5beb9f2dd5 100644
--- a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -6,14 +6,15 @@ redirect_from:
   - /articles/changing-a-persons-role-to-owner
   - /github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner
   - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization
 permissions: Organization owners can promote any member of an organization to an organization owner.
 versions:
   free-pro-team: '*'
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 ### About maintaining ownership continuity for your organization
@@ -22,6 +23,12 @@ topics:
 
 Organization owners have full administrative access to the organization. {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**Note**: As an organization owner, you can change the role of other organization members and owners. You can't change your own role.
+
+{% endnote %}
+
 ### Appointing an organization owner
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index bb42bc33e1..dec9e4bc51 100644
--- a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
 | Access the organization audit log                                                                                                                                                                                                                                                                                                                               | **X**  |         |                  |
 | Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" for details)                                                                                                                                                                                                                       | **X**  |         |                  |
 | Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details)                                                                                                                                                                                                                    | **X**  |         |                  |
-| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" for details)                                                                                                                             | **X**  |         |                  |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)                                                                                                                 | **X**  |         |                  |
 | Delete **all teams**                                                                                                                                                                                                                                                                                                                                            | **X**  |         |                  |
 | Delete the organization account, including all repositories                                                                                                                                                                                                                                                                                                     | **X**  |         |                  |
 | Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details)                                                                                                                                                                                                     | **X**  |  **X**  |                  |
@@ -60,9 +60,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
 | Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details)                                                                                                                                                                                 | **X**  |         |                  |
 | Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details)                                                                                                                                        | **X**  |         |                  |
 | Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details)                                                                                                                                                                                                            | **X**  |         |                  |
-| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details)                                                                                                                                    | **X**  |  **X**  |                  |
+| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/sponsors/sponsoring-open-source-contributors)" for details)                                                                                                                                                                                            | **X**  |  **X**  |                  |
 | Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" for details)                                                                                                                         | **X**  |         |                  |
-| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details )                                                                                                                       | **X**  |         |                  |
+| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)" for details )                                                                                                                                           | **X**  |         |                  |
 | Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X**  |         |                  |
 | Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details)                                                                                                                        | **X**  |         |                  |
 | Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                                                                                                               | **X**  |         |                  |
diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index 1187e89f46..d75ba364cc 100644
--- a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. In the Billing managers list, next to the name of the person you want to remove, click {% octicon "x" aria-label="X symbol" %}. ![Remove billing manager](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![Remove billing manager](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index c72945f787..b76f06b38c 100644
--- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/).
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**. ![Link to view and save your recovery codes](/assets/images/help/saml/saml_recovery_codes.png)
 6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**. ![Buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index 3396c1b512..df2e1415ba 100644
--- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
 
 Prior to enforcing SAML SSO in your organization, ensure that you've set up your identity provider (IdP). For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
index 6dc52297a3..c22476428e 100644
--- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
+++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -8,8 +8,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %}
@@ -21,4 +21,4 @@ topics:
 {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %}
 {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %}
 {% link_in_list /managing-team-synchronization-for-your-organization %}
-{% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %}
\ No newline at end of file
+{% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %}
diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index d676444c67..80a6a2d4fd 100644
--- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. Under "Team synchronization", click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
index 30f8dcea86..b2a1b17596 100644
--- a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
+++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
@@ -9,8 +9,8 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 You can remove the ability for members of legacy admin teams to create repositories by creating a new team for these members, ensuring that the team has necessary access to the organization's repositories, then deleting the legacy admin team.
diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md
index 5a0539da2a..b160864b26 100644
--- a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md
+++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md
@@ -11,10 +11,10 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %}
 {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %}
-{% link_in_list /migrating-admin-teams-to-improved-organization-permissions %}
\ No newline at end of file
+{% link_in_list /migrating-admin-teams-to-improved-organization-permissions %}
diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index fd5c3fb2f1..ca61f74cd4 100644
--- a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -9,8 +9,8 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 By default, all organization members can create repositories. If you restrict [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) to organization owners, and your organization was created under the legacy organization permissions structure, members of legacy admin teams will still be able to create repositories.
@@ -29,9 +29,8 @@ For more information, see "[Repository permission levels for an organization](/a
 
 ### Migrating all of your organization's legacy admin teams
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. Review your organization's legacy admin teams, then click **Migrate all teams**. ![Migrate all teams button](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. Read the information about possible permissions changes for members of these teams, then click **Migrate all teams.** ![Confirm migration button](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md
index d8450c6b27..8d6a2fceeb 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.organizations.types-of-team-visibility %}
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md
index 8dcd1238cb..ed0d8796c2 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% tip %}
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index bef774e006..7a04bb8111 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -9,15 +9,14 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. Under "Team discussions", unselect **Enable team discussions for this organization**. ![Checkbox to enable or disable team discussions for an organization](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. Click **Save**.
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md
index 0efd481006..f9a7c2c99e 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md
@@ -17,8 +17,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /about-teams %}
@@ -35,4 +35,4 @@ topics:
 {% link_in_list /removing-organization-members-from-a-team %}
 {% link_in_list /disabling-team-discussions-for-your-organization %}
 {% link_in_list /managing-scheduled-reminders-for-your-team %}
-{% link_in_list /deleting-a-team %}
\ No newline at end of file
+{% link_in_list /deleting-a-team %}
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md
index 7bb33d871c..6b85ea4666 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Team maintainers and organization owners can configure code review assignments.
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
index 9af60f3276..dea5599e0b 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md
index b62593f46d..fdefbaad5c 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md
@@ -9,8 +9,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md
index 03cac455eb..2aa3cd1c58 100644
--- a/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md
+++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 Unless you set a profile picture for a team, the team profile picture will match the organization's profile picture.
diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index 391f39bad8..a6d2e84277 100644
--- a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources.
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Next to the application you'd like to approve, click **Review**. ![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. After you review the information about the requested application, click **Grant access**. ![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index c66ed142f3..803cb0bb14 100644
--- a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -8,13 +8,12 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="The edit icon" %}. ![Edit icon](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. Click **Deny access**. ![Deny confirmation button](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index 5e5847e2c7..5ed8a69ef3 100644
--- a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -8,8 +8,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% danger %}
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Click **Remove restrictions**. ![Remove restrictions button](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**. ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index 857938eae1..5415a22717 100644
--- a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -8,8 +8,8 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. Under "Third-party application access policy," click **Setup application access restrictions**. ![Set up restrictions button](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. After you review the information about third-party access restrictions, click **Restrict third-party application access**. ![Restriction confirmation button](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md
index 9cf976f93a..efc0ce43a9 100644
--- a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md
+++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md
@@ -8,12 +8,12 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 {% link_in_list /about-oauth-app-access-restrictions %}
 {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %}
 {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %}
 {% link_in_list /approving-oauth-apps-for-your-organization %}
-{% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %}
\ No newline at end of file
+{% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %}
diff --git a/translations/ru-RU/content/packages/index.md b/translations/ru-RU/content/packages/index.md
index 0d7b1e5e13..5f693358ee 100644
--- a/translations/ru-RU/content/packages/index.md
+++ b/translations/ru-RU/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/ru-RU/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/ru-RU/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..158a9b08d6
--- /dev/null
+++ b/translations/ru-RU/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,85 @@
+---
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### About scopes and permissions for package registries
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+Например:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted.{% elsif currentVersion == "github-ae@latest" %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+
+| Scope                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Description                                                                       | Required permission |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------- |
+| `read:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Download and install packages from {% data variables.product.prodname_registry %} | read                |
+| `write:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Upload and publish packages to {% data variables.product.prodname_registry %}     | write               |
+| `delete:packages`                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                                   |                     |
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Delete packages from {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} |                                                                                   |                     |
+| admin                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                                   |                     |
+| `repo`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Upload and delete packages (along with `write:packages`, or `delete:packages`)    | write or admin      |
+
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/ru-RU/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/ru-RU/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..26b5e55a8a
--- /dev/null
+++ b/translations/ru-RU/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: Configuring a package's access control and visibility
+intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### Configuring access to container images for your personal account
+
+If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users will automatically be given access and don't need to accept an invitation first.
+
+### Configuring access to container images for an organization
+
+If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users or teams will automatically be given access and don't need to accept an invitation first.
+
+### Inheriting access for a container image from a repository
+
+To simplify package management through {% data variables.product.prodname_actions %} workflows, you can enable a container image to inherit the access permissions of a repository by default.
+
+If you inherit the access permissions of the repository where your package's workflows are stored, then you can adjust access to your package through the repository's permissions.
+
+Once a repository is synced, you can't access the package's granular access settings. To customize the package's permissions through the granular package access settings, you must remove the synced repository first.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. Under "Repository source", select **Inherit access from repository (recommended)**. ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### Ensuring workflow access to your package
+
+To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored.
+
+The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package.
+
+{% note %}
+
+**Note:** Syncing your container image with a repository through the **Actions access** menu option is different than connecting your container to a repository. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+#### {% data variables.product.prodname_actions %} access for user-account-owned container images
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+#### {% data variables.product.prodname_actions %} access for organization-owned container images
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like repository members to have to your container image. Outside collaborators will not be included. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for an organization](#configuring-access-to-container-images-for-an-organization)."
+
+### Configuring visibility of container images for your personal account
+
+When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
+
+### Container creation visibility for organization members
+
+You can choose the visibility of containers that organization members can publish by default.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, click **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images.
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, click **Internal**. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### Configuring visibility of container images for an organization
+
+When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/ru-RU/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/ru-RU/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..657ca54e15
--- /dev/null
+++ b/translations/ru-RU/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+### Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to a container image using the command line
+
+1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details:
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile:
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository.
+
+2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`.
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. Optionally, review details for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Tag your Docker image with your desired image name and hosting destination.
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  Например:
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  Например:
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/ru-RU/content/packages/learn-github-packages/index.md b/translations/ru-RU/content/packages/learn-github-packages/index.md
index cd736ad2b3..01dcc26748 100644
--- a/translations/ru-RU/content/packages/learn-github-packages/index.md
+++ b/translations/ru-RU/content/packages/learn-github-packages/index.md
@@ -1,9 +1,13 @@
 ---
 title: Learn GitHub Packages
 shortTitle: Learn GitHub Packages
-intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.'
+intro: 'You can find out more about using packages in GitHub, including publishing new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages
+  - /github/packages/publishing-and-managing-packages
+  - /packages/publishing-and-managing-packages
+  - /packages/manage-packages
 versions:
   free-pro-team: '*'
   enterprise-server: '>=2.22'
@@ -13,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md b/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..342d24ea7d
--- /dev/null
+++ b/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: Installing a package
+intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About package installation
+
+You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)."
+
+After you find a package, you can read the package's description and installation and usage instructions on the package page.
+
+### Installing a package
+
+You can install a package from {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+
+1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. Install the package using the instructions for your package client.
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/ru-RU/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/ru-RU/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..0dbfb1b792
--- /dev/null
+++ b/translations/ru-RU/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,133 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately {% if currentVersion == "github-ae@latest" %} for specified users or internally for your enterprise{% else %}or publicly{% endif %} and use packages as dependencies in your projects.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% if currentVersion != "github-ae@latest" %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
+
+You can integrate {% data variables.product.prodname_registry %} with {% data variables.product.product_name %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)."
+
+#### Overview of package permissions and visibility
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| Permissions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |                                                                  |
+| {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |                                                                  |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| Visibility                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | {% data reusables.package_registry.public-or-private-packages %}
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About billing for {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+{% endif %}
+
+### Supported clients and formats
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
+#### Support for package registries
+
+| Language   | Description                                            | Package format                       | Package client |
+| ---------- | ------------------------------------------------------ | ------------------------------------ | -------------- |
+| JavaScript | Node package manager                                   | `package.json`                       | `npm`          |
+| Ruby       | RubyGems package manager                               | `Gemfile`                            | `gem`          |
+| Java       | Apache Maven project management and comprehension tool | `pom.xml`                            | `mvn`          |
+| Java       | Gradle build automation tool for Java                  | `build.gradle` or `build.gradle.kts` | `gradle`       |
+| .NET       | NuGet package management for .NET                      | `nupkg`                              | `dotnet` CLI   |
+| Нет        | Docker container management                            | `Файл Dockerfile`                    | `Докер`        |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**Note:** Docker is not supported when subdomain isolation is disabled.
+
+{% endnote %}
+
+For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)."
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Managing packages
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. Or for repo-scoped packages, you can delete a version of a private package using GraphQL.
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+You can delete a version of a private package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
+
+### Contacting support
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use the [feedback form for {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages).
+
+Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if:
+
+* You experience anything that contradicts the documentation
+* You encounter vague or unclear errors
+* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information
+
+{% else %}
+If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators.
+
+{% endif %}
diff --git a/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md b/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md
index 2cb9438ee4..bd3c14e366 100644
--- a/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md
+++ b/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md
@@ -19,7 +19,7 @@ versions:
 
 You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
 
-{% data reusables.package_registry.public-or-private-packages %} A repository can contain more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
 
 {% if currentVersion == "free-pro-team@latest" %}
 If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository.
@@ -30,10 +30,10 @@ If a new version of a package fixes a security vulnerability, you should publish
 
 You can publish a package to {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
 
-1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 2. Authenticate to {% data variables.product.prodname_registry %} using your access token and the instructions for your package client.
 3. Publish the package using the instructions for your package client.
 
-For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)."
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
 
-After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see “[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages).”
+After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/learn-github-packages/viewing-packages)."
diff --git a/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md b/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..d34df4ff71
--- /dev/null
+++ b/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: Viewing packages
+intro: 'You can see details about packages published to a repository, and narrow results by organization or user.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### About package views
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### Viewing a repository's packages
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Viewing an organization's packages
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**.
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Viewing your packages
+
+You can find and view any package you've published across all organizations and repositories.
+
+{% data reusables.profile.access_profile %}
+2. On the top of the profile page, in the main navigation, click **Packages**. ![Project tab](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### Дополнительная литература
+
+- "[Searching for packages](/github/searching-for-information-on-github/searching-for-packages)"
diff --git a/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..db022b22ec
--- /dev/null
+++ b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: About GitHub Packages and GitHub Actions
+intro: Learn the fundamentals of managing packages through your {% data variables.product.prodname_actions %} workflows.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..5c6b375de3
--- /dev/null
+++ b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: Example workflows for publishing a package
+intro: To help you get started with your own custom workflows, review some example workflows for publishing packages.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+You can find example workflows in "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
+
+  - [Publishing Node.js packages](/actions/guides/publishing-nodejs-packages)
+  - [Publishing Docker images](/actions/guides/publishing-docker-images)
+  - [Publishing Java packages with Maven](/actions/guides/publishing-java-packages-with-maven)
+  - [Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..790a661916
--- /dev/null
+++ b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: Managing GitHub packages using GitHub Actions workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'You can safely publish and consume packages by building custom workflows that can also build, test, and deploy your code.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..3c9eaa040e
--- /dev/null
+++ b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,450 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)."
+
+{% endif %}
+
+#### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+### About permissions and package access for repository-owned packages
+
+{% note %}
+
+**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.
+
+{% endnote %}
+
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
+
+{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About permissions and package access for {% data variables.product.prodname_container_registry %}
+
+The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions.
+
+All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+### Default permissions and access settings for containers modified through workflows
+
+When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
+
+For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
+- The container inherits the visibility and permissions model of the repository where the workflow is run.
+- Repository admins where the workflow is run become the admins of the container once the container is created.
+
+These are more examples of how default permissions work for workflows that manage packages.
+
+| {% data variables.product.prodname_actions %} workflow task | Default permissions and access                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Download an existing container                              | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br> |
+| Upload a new version to an existing container               | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.                                                                                                                                                                                                                                                                                                                          |
+| Delete a container or versions of a container               | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.                                                                                                                                                                                                                                                                                                                                      |
+
+You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publishing a package using an action
+
+You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}:
+
+- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  The relevant settings are explained in the following table: <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configures the <code>Create and publish a package</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    This job installs NPM and uses it to build the app.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Creates a new step called <code>Build container image</code>. This step runs as part of the <code>build-and-push-image</code> job. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sends the required parameters to the <code>build-push-action</code> action. This are defined in the subsequent lines.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the password that is used to access {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace <code>YOUR-HOSTNAME</code> with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use <code>ghcr.io</code> as the hostname.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines which repository will host the resulting package, and sets the name of the published package. Replace <code>octo-image</code> with the name you want for your package.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the first seven characters of the commit's SHA. For example, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the git ref. This can be the name of the branch used to create the package.
+  </td>
+  </tr>
+  </table>
+
+- This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
+- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
+
+
+### Installing a package using an action
+
+You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Upgrading a workflow that accesses `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
diff --git a/translations/ru-RU/content/packages/quickstart.md b/translations/ru-RU/content/packages/quickstart.md
index 2a09f8a084..21a7257d5d 100644
--- a/translations/ru-RU/content/packages/quickstart.md
+++ b/translations/ru-RU/content/packages/quickstart.md
@@ -71,7 +71,10 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -95,7 +98,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
 
 ### Viewing your published package
 
-Packages are published at the repository level. You can see all the packages in a repository and search for a specific package.
+You can view all of the packages you have published.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ Packages are published at the repository level. You can see all the packages in
 
 ### Installing a published package
 
-Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)."
+Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
 
 ### Дальнейшие шаги
 
-The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
+The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
 
 Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
 
 - "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages
 - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions
-- "[Guides](/packages/guides)" for specific uses cases and examples
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..3397c52972
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: Enabling improved container support with the Container registry
+intro: 'To use the {% data variables.product.prodname_container_registry %}, you must enable it for your user or organization account.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)."
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your personal account
+
+Once the {% data variables.product.prodname_container_registry %} is enabled for your personal user account, you can publish containers to the {% data variables.product.prodname_container_registry %} owned by your user account.
+
+To use the {% data variables.product.prodname_container_registry %} within an organization, the organization owner must enable the feature for organization members.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png)
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your organization account
+
+Before organization owners or members can publish container images to the {% data variables.product.prodname_container_registry %}, an organization owner must enable the feature preview for the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, select **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, select **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, select **Internal**. ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/index.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..c0017ab0a4
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with a GitHub Packages registry
+shortTitle: Working with a GitHub Packages registry
+intro: 'Learn how to use a supported {% data variables.product.prodname_registry %} registry.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### Table of Contents
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..e5e3d10430
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,124 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- Store container images within your organization and user account, rather than a repository.
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- Access public container images anonymously.
+
+|                   | Docker registry                                                                                                                                                                                                                                                                            | {% data variables.product.prodname_container_registry %}
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Hosting locations | You can host multiple Docker images in one repository.                                                                                                                                                                                                                                     | You can host multiple container images in one organization or user account.                                                                                                            |
+| Permissions       | Each image inherits the permissions of the repository where the image is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. |
+ Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access    | N/A | You can access public container images anonymously. Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### Billing changes
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. For more information, see "[About  billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
+
+### Domain changes
+
+The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`.
+
+| Registry                                                       | Example URL                                         |
+| -------------------------------------------------------------- | --------------------------------------------------- |
+| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` |
+| {% data variables.product.prodname_container_registry %}     | `ghcr.io/OWNER/IMAGE_NAME`                          |
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}.
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Migrating a Docker image using the Docker CLI
+
+To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine.
+
+1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward.
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization.
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name.
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. Sign in to the new {% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### Updating your {% data variables.product.prodname_actions %} workflow
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers.
+
+1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)."
+
+2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`.
+
+3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+
+4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}.
+
+#### Example of updated workflow
+
+If part of your workflow accessed a Docker image hosted by the Docker registry like this:
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this:
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..b1e7b4c803
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Working with the Apache Maven registry
+intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist.
+
+In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token.
+
+In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag.
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`.
+
+If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `<distributionManagement>` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository.
+
+For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+
+1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+
+  If your instance has subdomain isolation enabled:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. Publish the package.
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Installing a package
+
+To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package.
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. Install the package.
+
+  ```shell
+  $ mvn install
+  ```
+
+### Дополнительная литература
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..0137b96e7a
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://ghcr.io`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About {% data variables.product.prodname_container_registry %} support
+
+To push and pull container images, an organization admin or the owner of a personal account must enable the {% data variables.product.prodname_container_registry %}. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+When installing or publishing a Docker image, the Container registry supports foreign layers, such as Windows images.
+
+The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
+
+* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### Pushing container images
+
+This example pushes the latest version of `IMAGE-NAME`.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+This example pushes the `2.5` version of the image.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+### Pulling container images
+
+#### Pull by digest
+
+To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
+
+1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. Remove image locally as needed.
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### Pull by name
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### Pull by name and version
+
+Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### Pull by name and latest version
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### Building container images
+
+This example builds the `hello_docker` image:
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### Tagging container images
+
+1. Find the ID for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. Tag your Docker image using the image ID and your desired image name and hosting destination.
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..8eb1ac15bc
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,262 @@
+---
+title: Working with the Docker registry
+intro: 'You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)."
+
+{% endif %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command.
+
+To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file.
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login docker.HOSTNAME -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation disabled:
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}.
+
+For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)."
+
+### Publishing an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**Note:** Image names must only use lowercase letters.
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. Determine the image name and ID for your docker image using `docker images`.
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. Publish the image to {% data variables.product.prodname_registry %}.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+  {% endnote %}
+
+#### Example publishing a Docker image
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+These examples assume your instance has subdomain isolation enabled.
+{% endif %}
+
+You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+You can publish a new Docker image for the first time and name it `monalisa`.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### Downloading an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the host name of {% data variables.product.product_location %}, {% endif %} and *TAG_NAME* with tag for the image you want to install.
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If your instance has subdomain isolation disabled:
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+{% endnote %}
+
+### Дополнительная литература
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..5fd144c131
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your personal access token. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository.
+
+{% if enterpriseServerVersions contains currentVersion %}
+Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+Replace *REGISTRY-URL* with the URL for your enterprise's Maven registry, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.
+{% endif %}
+
+Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+{% note %}
+
+**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)."
+
+{% endnote %}
+
+##### Example using Gradle Groovy for a single package in a repository
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### Example using Gradle Groovy for multiple packages in the same repository
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### Example using Kotlin DSL for a single package in the same repository
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### Example using Kotlin DSL for multiple packages in the same repository
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            register<MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+### Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. After creating your package, you can publish the package.
+
+  ```shell
+   $ gradle publish
+  ```
+
+### Installing a package
+
+You can install a package by adding the package as a dependency to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Gradle Groovy:
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. Add the maven plugin to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Gradle Groovy:
+  ```shell
+  plugins {
+      id 'maven'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  plugins {
+      `maven`
+  }
+  ```
+
+  3. Install the package.
+
+  ```shell
+  $ gradle install
+  ```
+
+### Дополнительная литература
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..c782a86122
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,215 @@
+---
+title: Working with the npm registry
+intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### Limits for published npm versions
+
+If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage.
+
+In the future, to improve performance of the service, you won't be able to publish more than 1,000 versions of a package on {% data variables.product.prodname_dotcom %}. Any versions published before hitting this limit will still be readable.
+
+If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
+
+{% endif %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token.
+
+To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+//<em>HOSTNAME</em>/_registry/npm/:_authToken=<em>TOKEN</em>
+```
+{% endif %}
+
+To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address.
+
+If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### Publishing a package
+
+{% note %}
+
+**Note:** Package names and scopes must only use lowercase letters.
+
+{% endnote %}
+
+By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation.
+
+You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)."
+
+You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`.
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### Publishing a package using a local *.npmrc* file
+
+You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" {% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`.
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### Publishing a package using `publishConfig` in the *package.json* file
+
+You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+
+1. Edit the *package.json* file for your package and include a `publishConfig` entry.
+  {% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  If your instance has subdomain isolation disabled:
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package.
+
+To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository.
+
+{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name.
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### Installing a package
+
+You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation.
+
+By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)."
+
+You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency.
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. Install the package.
+
+  ```shell
+  $ npm install
+  ```
+
+#### Installing packages from other organizations
+
+By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project.
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### Using the official NPM registry
+
+{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
+{% endif %}
+
+### Дополнительная литература
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..3621cffd01
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,236 @@
+---
+title: Working with the NuGet registry
+intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client.
+
+You must replace:
+- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}.
+- `TOKEN` with your personal access token.
+- `OWNER` with the name of the user or organization account that owns the repository containing your project.{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %}If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://HOSTNAME/_registry/nuget/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+{% endif %}
+
+### Publishing a package
+
+You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%}, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} personal access token (PAT){% endif %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### Publishing a package using a GitHub PAT as your API key
+
+If you don't already have a PAT to use for your {% data variables.product.prodname_dotcom %} account, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+1. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. Publish the package using your PAT as the API key.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### Publishing a package using a *nuget.config* file
+
+When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. Add your project's specific information to your project's file, which ends in *.csproj*.  You must replace:
+    - `OWNER` with the name of the user or organization account that owns the repository containing your project.
+    - `REPOSITORY` with the name of the repository containing the package you want to publish.
+    - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - `HOSTNAME` with the host name for {% data variables.product.product_location %}.{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. Publish the package using the `key` you specified in the *nuget.config* file.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field.
+
+For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository:
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### Installing a package
+
+Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use:
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. Install the packages with the `restore` command.
+  ```shell
+  dotnet restore
+  ```
+
+### Устранение проблем
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### Дополнительная литература
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..2b40e1203e
--- /dev/null
+++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,152 @@
+---
+title: Working with the RubyGems registry
+intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+### Требования
+
+- You must have rubygems 2.4.1 or higher. To find your rubygems version:
+
+  ```shell
+  $ gem --version
+  ```
+
+  - You must have bundler 1.6.4 or higher. To find your Bundler version:
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - Install keycutter to manage multiple credentials. To install keycutter:
+  ```shell
+  $ gem install keycutter
+  ```
+
+### Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### Authenticating with a personal access token
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the  *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems.
+
+To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your personal access token.  Create a new *~/.gem/credentials* file if this file doesn't exist.
+
+For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your personal access token.
+
+```shell
+---
+:github: Bearer <em>TOKEN</em>
+```
+
+To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace:
+  - `USERNAME` with your {% data variables.product.prodname_dotcom %} username.
+  - `TOKEN` with your personal access token.
+  - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.
+{% endif %}
+
+If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example.
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Build the package from the *gemspec* to create the *.gem* package.
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### Publishing multiple packages to the same repository
+
+To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### Installing a package
+
+You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif currentVersion == "github-ae@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html).
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. Install the package:
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### Дополнительная литература
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
index 9e748a4882..686149e1e0 100644
--- a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
+++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
@@ -15,9 +15,9 @@ product: '{% data reusables.gated-features.pages %}'
 versions:
   free-pro-team: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 {% link_in_list /about-custom-domains-and-github-pages %}
 {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %}
-{% link_in_list /troubleshooting-custom-domains-and-github-pages %}
\ No newline at end of file
+{% link_in_list /troubleshooting-custom-domains-and-github-pages %}
diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index fc5aeb63a9..ab6e65ee63 100644
--- a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -46,7 +46,7 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png)
 5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
 ```shell
@@ -79,7 +79,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
   ```shell
diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
index 3b7ee96541..47646f0de3 100644
--- a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
+++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -11,7 +11,7 @@ product: '{% data reusables.gated-features.pages %}'
 versions:
   free-pro-team: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 ### _CNAME_ errors
diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md
index 83ae235456..88097ccec0 100644
--- a/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md
+++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -68,14 +68,6 @@ The URL where your site is available depends on whether subdomain isolation is e
 For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator.
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-{% note %}
-
-**Note:** Repositories using the legacy `<username>.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://<username>.github.com` to `http(s)://<username>.github.io`. If both a `<username>.github.com` and `<username>.github.io` repository exist, only the `<username>.github.io` repository will be published.
-
-{% endnote %}
-{% endif %}
-
 ### Publishing sources for {% data variables.product.prodname_pages %} sites
 
 The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored.
diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index d765eb4e9f..a58348592a 100644
--- a/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -1,10 +1,10 @@
 ---
 title: Changing the visibility of your GitHub Pages site
-intro: 'You can manage access control for your project site by publishing the site publicly or privately.'
+intro: You can manage access control for your project site by publishing the site publicly or privately.
 product: '{% data reusables.gated-features.private-pages %}'
 versions:
   free-pro-team: '*'
-permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site.
+permissions: 'People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site.'
 redirect_from:
   - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site
 ---
diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
index 8fc3589bbb..2578fc29ab 100644
--- a/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
+++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md
index 6dcbaf8ab7..42412ec2e0 100644
--- a/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 {% link_in_list /about-github-pages %}
@@ -23,4 +23,4 @@ topics:
 {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %}
 {% link_in_list /securing-your-github-pages-site-with-https %}
 {% link_in_list /using-submodules-with-github-pages %}
-{% link_in_list /unpublishing-a-github-pages-site %}
\ No newline at end of file
+{% link_in_list /unpublishing-a-github-pages-site %}
diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
index cb9bf8e593..057d7c2d32 100644
--- a/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
+++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   free-pro-team: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site.
diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index 26904123a8..3b780a75a1 100644
--- a/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -15,7 +15,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 ### Unpublishing a project site
diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
index e9ada225c6..9ba64cfbc0 100644
--- a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
+++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -24,7 +24,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 ### About Jekyll
diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
index 9b2ffcb839..f95aa1a35f 100644
--- a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 ### About Jekyll build errors
diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index a2c08509ee..3238044dbe 100644
--- a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -87,7 +87,12 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 10. Save and close the Gemfile.
 11. From the command line, run `bundle update`.
 11. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
-12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository.
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
index 90f13f8482..4f9519da40 100644
--- a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
+++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
@@ -12,7 +12,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 {% link_in_list /about-github-pages-and-jekyll %}
@@ -22,4 +22,4 @@ topics:
 {% link_in_list /setting-a-markdown-processor-for-your-github-pages-site-using-jekyll %}
 {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %}
 {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %}
-{% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %}
\ No newline at end of file
+{% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %}
diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
index 907cb3c671..bf5f6be020 100644
--- a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
@@ -31,7 +31,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - pages
+  - Pages
 ---
 
 ### Troubleshooting build errors
diff --git a/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md b/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md
index e5c2674648..6ab892e0d9 100644
--- a/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md
+++ b/translations/ru-RU/content/rest/guides/best-practices-for-integrators.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 
diff --git a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md
index 411d852838..f856ff8dc4 100644
--- a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -225,7 +225,7 @@ Next, let's fetch our newly created repository:
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ A project the size of Rails has thousands of issues. We'll need to [paginate][pa
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ A big part of being a good API citizen is respecting rate limits by caching info
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ In addition to the JSON body, take note of the HTTP status code of `200` and the
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 The `304` status indicates that the resource hasn't changed since the last time we asked for it and the response will contain no body. As a bonus, `304` responses don't count against your [rate limit][rate-limiting].
diff --git a/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md b/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md
index 4d2b803cf5..c1f141cd76 100644
--- a/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md
+++ b/translations/ru-RU/content/rest/guides/rendering-data-as-graphs.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
  
 
diff --git a/translations/ru-RU/content/rest/guides/traversing-with-pagination.md b/translations/ru-RU/content/rest/guides/traversing-with-pagination.md
index 71d98cd85c..7c88326244 100644
--- a/translations/ru-RU/content/rest/guides/traversing-with-pagination.md
+++ b/translations/ru-RU/content/rest/guides/traversing-with-pagination.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
  
diff --git a/translations/ru-RU/content/rest/guides/working-with-comments.md b/translations/ru-RU/content/rest/guides/working-with-comments.md
index afa2e9a873..b587840805 100644
--- a/translations/ru-RU/content/rest/guides/working-with-comments.md
+++ b/translations/ru-RU/content/rest/guides/working-with-comments.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 
diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md
index de78d29ca0..a87e65016c 100644
--- a/translations/ru-RU/content/rest/overview/libraries.md
+++ b/translations/ru-RU/content/rest/overview/libraries.md
@@ -9,7 +9,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 <div class="jumbotron libraries-jumbotron">
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
diff --git a/translations/ru-RU/content/rest/overview/media-types.md b/translations/ru-RU/content/rest/overview/media-types.md
index 8d38204c91..148ac7ae3b 100644
--- a/translations/ru-RU/content/rest/overview/media-types.md
+++ b/translations/ru-RU/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ You can check the current version through every response's headers.  Look for th
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/ru-RU/content/rest/overview/openapi-description.md b/translations/ru-RU/content/rest/overview/openapi-description.md
index 9b38ae760b..2215f7ddff 100644
--- a/translations/ru-RU/content/rest/overview/openapi-description.md
+++ b/translations/ru-RU/content/rest/overview/openapi-description.md
@@ -5,7 +5,7 @@ versions:
   free-pro-team: '*'
   enterprise-server: '*'
 topics:
-  - api
+  - API
 ---
 
 ### About OpenAPI descriptions
diff --git a/translations/ru-RU/content/rest/overview/other-authentication-methods.md b/translations/ru-RU/content/rest/overview/other-authentication-methods.md
index fcff0de19e..4466bd314b 100644
--- a/translations/ru-RU/content/rest/overview/other-authentication-methods.md
+++ b/translations/ru-RU/content/rest/overview/other-authentication-methods.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 
diff --git a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md
index a711952971..740aff4784 100644
--- a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md
@@ -34,7 +34,7 @@ sent and received as JSON.
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: nginx
 > Date: Fri, 12 Oct 2012 23:33:14 GMT
 > Content-Type: application/json; charset=utf-8
@@ -126,7 +126,7 @@ Authenticating with invalid credentials will return `401 Unauthorized`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
-> HTTP/1.1 401 Unauthorized
+> HTTP/2 401
 
 > {
 >   "message": "Bad credentials",
@@ -139,7 +139,7 @@ After detecting several requests with invalid credentials within a short period,
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
 -u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > {
 >   "message": "Maximum number of login attempts exceeded. Please try again later.",
 >   "documentation_url": "{% data variables.product.doc_url_pre %}"
@@ -181,7 +181,7 @@ There are three possible types of client errors on API calls that receive reques
 
 1. Sending invalid JSON will result in a `400 Bad Request` response.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 35
        
         {"message":"Problems parsing JSON"}
@@ -189,14 +189,14 @@ There are three possible types of client errors on API calls that receive reques
 2. Sending the wrong type of JSON values will result in a `400 Bad
 Request` response.
    
-        HTTP/1.1 400 Bad Request
+        HTTP/2 400
         Content-Length: 40
        
         {"message":"Body should be a JSON object"}
 
 3. Sending invalid fields will result in a `422 Unprocessable Entity` response.
    
-        HTTP/1.1 422 Unprocessable Entity
+        HTTP/2 422
         Content-Length: 149
        
         {
@@ -328,7 +328,7 @@ The returned HTTP headers of any API request show your current rate limit status
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 56
@@ -351,7 +351,7 @@ new Date(1372700873 * 1000)
 If you exceed the rate limit, an error response returns:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > X-RateLimit-Limit: 60
 > X-RateLimit-Remaining: 0
@@ -371,7 +371,7 @@ If your OAuth application needs to make unauthenticated calls with a higher rate
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > X-RateLimit-Limit: 5000
 > X-RateLimit-Remaining: 4966
@@ -397,7 +397,7 @@ Abuse rate limits are not intended to interfere with legitimate use of the API.
 If your application triggers this rate limit, you'll receive an informative response:
 
 ```shell
-> HTTP/1.1 403 Forbidden
+> HTTP/2 403
 > Content-Type: application/json; charset=utf-8
 > Connection: close
 
@@ -450,7 +450,7 @@ Most responses return an `ETag` header. Many responses also return a `Last-Modif
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/user
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -460,7 +460,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
@@ -470,7 +470,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b
 > X-RateLimit-Reset: 1372700873
 
 $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > Cache-Control: private, max-age=60
 > Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
 > Vary: Accept, Authorization, Cookie
@@ -487,7 +487,7 @@ Here's a sample request sent from a browser hitting `http://example.com`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
-HTTP/1.1 302 Found
+HTTP/2 302
 Access-Control-Allow-Origin: *
 Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
 ```
@@ -496,7 +496,7 @@ This is what the CORS preflight request looks like:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
-HTTP/1.1 204 No Content
+HTTP/2 204
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
 Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
diff --git a/translations/ru-RU/content/rest/reference/activity.md b/translations/ru-RU/content/rest/reference/activity.md
index d7f709376b..625372029d 100644
--- a/translations/ru-RU/content/rest/reference/activity.md
+++ b/translations/ru-RU/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ Events are optimized for polling with the "ETag" header. If no new events have b
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
 # The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ To get a feed in Atom format, you must specify the `application/atom+xml` type i
 #### Response
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ Notifications are optimized for polling with the `Last-Modified` header.  If the
 ``` shell
 # Add authentication to your requests
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
 # Pass the Last-Modified header exactly
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/ru-RU/content/rest/reference/billing.md b/translations/ru-RU/content/rest/reference/billing.md
index 0fab2af1cd..d7b1020447 100644
--- a/translations/ru-RU/content/rest/reference/billing.md
+++ b/translations/ru-RU/content/rest/reference/billing.md
@@ -3,7 +3,7 @@ title: Billing
 versions:
   free-pro-team: '*'
 topics:
-  - api
+  - API
 ---
 
 You can monitor your {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} charges and usage for a user and organization through the Billing API.
diff --git a/translations/ru-RU/content/rest/reference/code-scanning.md b/translations/ru-RU/content/rest/reference/code-scanning.md
index 6e605630bf..424801acda 100644
--- a/translations/ru-RU/content/rest/reference/code-scanning.md
+++ b/translations/ru-RU/content/rest/reference/code-scanning.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% data reusables.code-scanning.beta %}
diff --git a/translations/ru-RU/content/rest/reference/codes-of-conduct.md b/translations/ru-RU/content/rest/reference/codes-of-conduct.md
index 109bf9e922..5d9d11791a 100644
--- a/translations/ru-RU/content/rest/reference/codes-of-conduct.md
+++ b/translations/ru-RU/content/rest/reference/codes-of-conduct.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 You can use the Codes of Conduct API to retrieve information about a repository's code of conduct. To get a repository's code of conduct, use the "[Get a repository](/rest/reference/repos#get-a-repository)" endpoint.
diff --git a/translations/ru-RU/content/rest/reference/emojis.md b/translations/ru-RU/content/rest/reference/emojis.md
index ec918c60c2..4f4dac4de9 100644
--- a/translations/ru-RU/content/rest/reference/emojis.md
+++ b/translations/ru-RU/content/rest/reference/emojis.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ru-RU/content/rest/reference/enterprise-admin.md b/translations/ru-RU/content/rest/reference/enterprise-admin.md
index f71f2a1834..632834e808 100644
--- a/translations/ru-RU/content/rest/reference/enterprise-admin.md
+++ b/translations/ru-RU/content/rest/reference/enterprise-admin.md
@@ -151,19 +151,6 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 {% endfor %}
 
 {% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
-
-## Encryption at rest
-
-You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## Admin stats
 
diff --git a/translations/ru-RU/content/rest/reference/git.md b/translations/ru-RU/content/rest/reference/git.md
index 33ecf8c6c5..052bf87e08 100644
--- a/translations/ru-RU/content/rest/reference/git.md
+++ b/translations/ru-RU/content/rest/reference/git.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 The Git Database API gives you access to read and write raw Git objects to your Git database on {% data variables.product.product_name %} and to list and update your references (branch heads and tags). For more information about using the Git Database API, see "[Getting started with the Git data API](/rest/guides/getting-started-with-the-git-database-api)."
@@ -19,7 +19,7 @@ The Git Database API gives you access to read and write raw Git objects to your
 
 ## Blobs
 
-A Git blob (binary large object) is the object type used to store the contents of each file in a repository. The file's SHA-1 hash is computed and stored in the blob object. These endpoints allow you to read and write [blob objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) to your Git database on {% data variables.product.product_name %}. Blobs leverage [these custom media types](#custom-media-types). You can read more about the use of media types in the API [here](/rest/overview/media-types).
+A Git blob (binary large object) is the object type used to store the contents of each file in a repository. The file's SHA-1 hash is computed and stored in the blob object. These endpoints allow you to read and write [blob objects](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) to your Git database on {% data variables.product.product_name %}. Blobs leverage [these custom media types](#custom-media-types-for-blobs). You can read more about the use of media types in the API [here](/rest/overview/media-types).
 
 ### Custom media types for blobs
 
diff --git a/translations/ru-RU/content/rest/reference/gitignore.md b/translations/ru-RU/content/rest/reference/gitignore.md
index f1a193f354..f62e5e7f6e 100644
--- a/translations/ru-RU/content/rest/reference/gitignore.md
+++ b/translations/ru-RU/content/rest/reference/gitignore.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 When you create a new {% data variables.product.product_name %} repository via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. The .gitignore templates API lists and fetches templates from the {% data variables.product.product_name %} [.gitignore repository](https://github.com/github/gitignore).
diff --git a/translations/ru-RU/content/rest/reference/index.md b/translations/ru-RU/content/rest/reference/index.md
index 88efef37c8..98adb6d7d7 100644
--- a/translations/ru-RU/content/rest/reference/index.md
+++ b/translations/ru-RU/content/rest/reference/index.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### Table of Contents
diff --git a/translations/ru-RU/content/rest/reference/licenses.md b/translations/ru-RU/content/rest/reference/licenses.md
index 3a67c0b3c8..2e450a9067 100644
--- a/translations/ru-RU/content/rest/reference/licenses.md
+++ b/translations/ru-RU/content/rest/reference/licenses.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 The Licenses API returns metadata about popular open source licenses and information about a particular project's license file.
diff --git a/translations/ru-RU/content/rest/reference/markdown.md b/translations/ru-RU/content/rest/reference/markdown.md
index e978876791..1d5c33f371 100644
--- a/translations/ru-RU/content/rest/reference/markdown.md
+++ b/translations/ru-RU/content/rest/reference/markdown.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ru-RU/content/rest/reference/meta.md b/translations/ru-RU/content/rest/reference/meta.md
index 6cd6fa2083..7d6ba6201c 100644
--- a/translations/ru-RU/content/rest/reference/meta.md
+++ b/translations/ru-RU/content/rest/reference/meta.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ru-RU/content/rest/reference/orgs.md b/translations/ru-RU/content/rest/reference/orgs.md
index ba7a65b915..5bc88a7d60 100644
--- a/translations/ru-RU/content/rest/reference/orgs.md
+++ b/translations/ru-RU/content/rest/reference/orgs.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% for operation in currentRestOperations %}
diff --git a/translations/ru-RU/content/rest/reference/packages.md b/translations/ru-RU/content/rest/reference/packages.md
index 74f8d40c22..3a455e238f 100644
--- a/translations/ru-RU/content/rest/reference/packages.md
+++ b/translations/ru-RU/content/rest/reference/packages.md
@@ -4,7 +4,7 @@ product: '{% data reusables.gated-features.packages %}'
 versions:
   free-pro-team: '*'
 topics:
-  - api
+  - API
 ---
 
 The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
diff --git a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md
index dc8f94db6c..8b14f23852 100644
--- a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md
@@ -120,6 +120,9 @@ _Поиск_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _Поиск_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -678,6 +684,9 @@ _Teams_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### Permission on "pull requests"
 
@@ -767,6 +776,10 @@ _Reviews_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### Permission on "profile"
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### Permission on "repository hooks"
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
diff --git a/translations/ru-RU/content/rest/reference/projects.md b/translations/ru-RU/content/rest/reference/projects.md
index 30b524f6e5..a8612ade35 100644
--- a/translations/ru-RU/content/rest/reference/projects.md
+++ b/translations/ru-RU/content/rest/reference/projects.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% for operation in currentRestOperations %}
diff --git a/translations/ru-RU/content/rest/reference/rate-limit.md b/translations/ru-RU/content/rest/reference/rate-limit.md
index c5110c19eb..22309392db 100644
--- a/translations/ru-RU/content/rest/reference/rate-limit.md
+++ b/translations/ru-RU/content/rest/reference/rate-limit.md
@@ -8,7 +8,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 The REST API overview documentation describes the [rate limit rules](/rest/overview/resources-in-the-rest-api#rate-limiting). You can check your current rate limit status at any time using the Rate Limit API described below.
diff --git a/translations/ru-RU/content/rest/reference/reactions.md b/translations/ru-RU/content/rest/reference/reactions.md
index 7ddd930ec4..ebdc1066dc 100644
--- a/translations/ru-RU/content/rest/reference/reactions.md
+++ b/translations/ru-RU/content/rest/reference/reactions.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 ### Reaction types
diff --git a/translations/ru-RU/content/rest/reference/repos.md b/translations/ru-RU/content/rest/reference/repos.md
index d99270e899..67c54c0fc5 100644
--- a/translations/ru-RU/content/rest/reference/repos.md
+++ b/translations/ru-RU/content/rest/reference/repos.md
@@ -155,7 +155,8 @@ You can communicate that a transient environment no longer exists by setting its
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 ## Environments
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)."
+The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
diff --git a/translations/ru-RU/content/rest/reference/teams.md b/translations/ru-RU/content/rest/reference/teams.md
index d98f01e647..1924bdbc44 100644
--- a/translations/ru-RU/content/rest/reference/teams.md
+++ b/translations/ru-RU/content/rest/reference/teams.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 This API is only available to authenticated members of the team's [organization](/rest/reference/orgs). OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %}  generates the team's `slug` from the team `name`.
diff --git a/translations/ru-RU/content/rest/reference/users.md b/translations/ru-RU/content/rest/reference/users.md
index a8be9cb182..ed3d6d1f5f 100644
--- a/translations/ru-RU/content/rest/reference/users.md
+++ b/translations/ru-RU/content/rest/reference/users.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 Many of the resources on the users API provide a shortcut for getting information about the currently authenticated user. If a request URL does not include a `{username}` parameter then the response will be for the logged in user (and you must pass [authentication information](/rest/overview/resources-in-the-rest-api#authentication) with your request).{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} Additional private information, such as whether a user has two-factor authentication enabled, is included when authenticated through basic auth or OAuth with the `user` scope.{% endif %}
diff --git a/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..04cdd58987
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: About GitHub Sponsors
+intro: '{% data variables.product.prodname_sponsors %} allows the developer community to financially support the people and organizations who design, build, and maintain the open source projects they depend on, directly on {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### About {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+When you become a sponsored developer or sponsored organization, additional terms for {% data variables.product.prodname_sponsors %} apply. For more information, see "[GitHub Sponsors Additional Terms](/github/site-policy/github-sponsors-additional-terms)."
+
+### About the {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**Note:** {% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/github/site-policy/github-community-guidelines). Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}.
+
+To be eligible for the {% data variables.product.prodname_matching_fund %}, you must create a profile that will attract a community that will sustain you for the long term. For more information about creating a strong profile, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."
+
+Donations between sponsored developers will not be matched.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### Sharing feedback about {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### Дополнительная литература
+- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
+- "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..4c473a5869
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: Getting started with GitHub Sponsors
+intro: 'Learn about {% data variables.product.prodname_sponsors %} and how you can get involved as a sponsor or open source contributor.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..2da01792b9
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: Quickstart for finding contributors to sponsor
+intro: Learn some best practices for finding open source contributors to sponsor.
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### Explore projects you depend on
+
+As you consider where to find open source contributors to sponsor, consider starting at https://github.com/sponsors/community.
+
+If you're logged in, the sponsors results will start with public dependencies that your repositories depend on.
+
+![The Babel open source project with highlighted text that says "4 of your repositories depend on this"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+You can also toggle which of your accounts to view results for and further filter or search.
+
+![Search options on sponsors community search page](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### Explore whom others sponsor
+
+You can see whom a user or organization sponsors on their {% data variables.product.prodname_dotcom %} profile page.
+
+### Consider how you benefit from different contributions
+
+Consider whether you benefit from the work of open source contributions, such as:
+ - Документация
+ - Design
+ - Translation
+ - Newsletters
+ - Code reviews
+ - Инструкции
+ - Mentoring
+ - Triaging issues and helping with project management
+ - Answering questions
+ - Event planning
+
+For more information on different types of open source contributions, see the [Open source guide](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+You can check if contributors you've benefited from have {% data variables.product.prodname_sponsors %} profiles by using search at https://github.com/sponsors/community.
+
+### Search for a specific project or contributor
+
+At https://github.com/sponsors/community, you can search by ecosystem, most used, recently updated, and more. You can filter search results for your personal user account or for organizations that you're a member of.
+
+### Дальнейшие шаги
+
+For more information on starting your sponsorship, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
diff --git a/translations/ru-RU/content/sponsors/guides.md b/translations/ru-RU/content/sponsors/guides.md
new file mode 100644
index 0000000000..cacd9d3786
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Sponsors guides
+shortTitle: Руководства
+intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/ru-RU/content/sponsors/index.md b/translations/ru-RU/content/sponsors/index.md
new file mode 100644
index 0000000000..efd1738d8a
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Sponsors Documentation
+shortTitle: GitHub Sponsors
+intro: 'Invest in the open source projects you depend on, support digital infrastructure, and make open source careers possible by sponsoring open source contributors and their projects. Build a {% data variables.product.prodname_sponsors %} profile and receive compensation for your open source work.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: 'sponsors'
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..676c329400
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: Configuring webhooks for events in your sponsored account
+intro: You can configure webhooks to alert you when you receive new sponsorships or existing sponsors make changes to their sponsorships.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### About webhooks for events in your sponsored account
+
+To monitor changes to your sponsorships, such as cancellations at the end of a pay period, you can create webhooks for your sponsored user or organization account. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship).
+
+### Managing webhooks for events in your sponsored account
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..8d05fd7671
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Getting started with the Sponsors GraphQL API
+intro: 'Using the GraphQL API, you can build custom integrations to manage or review your sponsorships.'
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+To get started with the GraphQL API, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+You can find the details about the Sponsors GraphQL API in the reference docs. For more information, see "[GraphQL reference](/graphql/reference)." We recommend using the GraphQL explorer to build your GraphQL calls. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer)."
diff --git a/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/index.md b/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..37e7055360
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: Integrating with GitHub Sponsors
+intro: 'As an open source contributor, you can build custom tools to manage your GitHub sponsorships.'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..22b75eb406
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: About GitHub Sponsors for open source contributors
+intro: 'If you provide value to an open source project, you can become a sponsored contributor to receive payments for your work.'
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+After you join {% data variables.product.prodname_sponsors %}, you can add a sponsor button to the open source repository you contribute to, to increase the visibility of your {% data variables.product.prodname_sponsors %} profile and other funding platforms. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."
+
+You can set a goal for your sponsorships. For more information, see "[Managing your sponsorship goal](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal)."
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### Sponsorship tiers
+
+{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+
+It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule.
+
+### Sponsorship payouts
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)."
+
+### Sharing feedback about {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.feedback %}
+
+### Дополнительная литература
+- "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..d67d4e0ae8
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: Contacting your sponsors
+intro: You can send an email to your sponsors who have opted in to receive updates about your work.
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### About sponsorship updates
+
+Your sponsors can choose whether they receive email updates about your work. For more information, see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)."
+
+For sponsored developer accounts, the update will come from your user account's primary email address. If you've enabled email address privacy on your user account, the update will come from `noreply@github.com` instead. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+
+### Contacting your sponsors
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..5fd8daa518
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: Editing your profile details for GitHub Sponsors
+intro: You can update the information that potential sponsors see about your work.
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### About sponsor profiles
+
+Your {% data variables.product.prodname_sponsors %} profile tells potential sponsors why they should support you. People see your sponsor profile when they click the **Sponsor** button on your profile. We recommend including the following information.
+
+- Open source work that you contribute to
+- Why you are committed to open source development
+
+### Editing your profile details
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..7e3d0358ca
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: Receiving sponsorships through GitHub Sponsors
+shortTitle: Receiving sponsorships
+intro: 'You or your organization can become a sponsored open source contributor to receive payments for your work, update your sponsorship details, and view and contact your sponsors.'
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..ad80a4facd
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Managing your payouts from GitHub Sponsors
+intro: 'You can view information about past and future payouts from {% data variables.product.prodname_sponsors %} and edit your bank information.'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### About payouts from {% data variables.product.prodname_sponsors %}
+
+You can only manage your payouts from {% data variables.product.prodname_sponsors %} if you are paid through Stripe Connect. If you are paid through ACH transfer or wire transfer for your sponsored user account, you will not see the **Payouts** tab on your sponsored open source contributor dashboard. Sponsored organizations can only use Stripe Connect for payouts. For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)."
+
+{% data reusables.sponsors.payout-info %}
+
+### Viewing and editing payout information
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..d0d1f06197
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: Managing your sponsorship goal
+intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### About sponsorship goals
+
+You can set a funding goal for your sponsored account and share the goal with your community. Goals help you understand the impact you have in the open source community and build up your presence in the {% data variables.product.prodname_sponsors %} program.
+
+Your goal can set a target for the number of sponsors you want to have or the amount of money you want to earn each month. You can only set one goal up at a time. After you reach a goal, you can set another goal.
+
+### Setting a goal
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Editing a goal
+
+When you edit a goal, you can't choose a goal you've already achieved. For example, if you already have 5 sponsors, you can't edit your goal so that you're aiming for 4 sponsors.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### Retiring a goal
+
+After you retire a goal, you won't be able to reactivate the goal. You must create a new goal instead.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..7f5f951ecd
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: Managing your sponsorship tiers
+intro: 'You can add a new sponsorship tier, or edit or retire an existing tier.'
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### About sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### Adding a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### Editing or retiring a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### Enabling tiers with custom amounts
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### Disabling tiers with custom amounts
+
+You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired.
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..de7b16c649
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: Setting up GitHub Sponsors for your organization
+intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization.
+
+To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. To the right of your organization, click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### Completing your sponsored organization profile
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Creating sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Submitting your bank information
+
+As a sponsored organization, you must receive payouts to a dedicated bank account for your organization in a supported region. You can get a business bank account through services like [Open Collective](https://opencollective.com/) and [Stripe Atlas](https://stripe.com/atlas). The region your organization legally operates in and the region of your bank account must match. The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+For more information about setting up Stripe Connect using Open Collective, see [Setting up {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) in the Open Collective Docs.
+
+### Submitting your tax information
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+
+Before your organization can become a sponsored organization, you must enable 2FA on your {% data variables.product.product_name %} account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+### Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### Дополнительная литература
+- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..1e28d8e153
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: Setting up GitHub Sponsors for your user account
+intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication on your {% data variables.product.prodname_dotcom %} account.'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+To join {% data variables.product.prodname_sponsors %} as an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. If you are an organization owner, you have more than one eligible account. Click **View your eligible accounts**, then in the list of accounts, find your user account.
+3. Click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
+
+### Completing your sponsored developer profile
+
+After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### Creating sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### Submitting your bank information
+
+If you live in a supported region, you can follow these instructions to submit your bank information by creating a Stripe Connect account. Your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### Submitting your tax information
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+
+Before you can become a sponsored developer, you must enable 2FA on your {% data variables.product.product_name %} account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+### Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. Click **Request approval**. ![Request approval button](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..33b850604e
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: Tax information for GitHub Sponsors
+intro: 'Sponsored developers and organizations must submit tax information to {% data variables.product.prodname_dotcom %} and are responsible for evaluating and paying their own taxes.'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are a taxpayer in the United States, you must submit a W-9 before you can receive payments. If you are a taxpayer in any other region besides the United States, you must submit a W-8BEN before you can receive payments. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms.
+
+If you are a taxpayer in the United States and earn more than $600 USD in a tax year, {% data variables.product.prodname_dotcom %} will send you a 1099 before January 31 of the next calendar year. We do not provide tax forms for international taxpayers.
+
+{% data variables.product.prodname_dotcom %} does not withhold tax from {% data variables.product.prodname_sponsors %} payments. Sponsored developers are responsible for evaluating and paying their own taxes.
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### Дополнительная литература
+
+- [Viewing your sponsors and sponsorships](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..ca39d19435
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: Viewing your sponsors and sponsorships
+intro: You can view and export detailed information and analytics about your sponsors and sponsorships.
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### About sponsors and sponsorships
+
+You can view analytics on your current and past sponsorships, the payments you've received from sponsors, and events, such as cancellations and sponsor tier changes for your sponsorships. You can also view activity such as new sponsorships, changes to sponsorships, and canceled sponsorships. You can filter the list of activities by date. You can also export sponsorship data for the account you're viewing in CSV or JSON format.
+
+### Viewing your sponsors and sponsorships
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. Optionally, to filter your sponsors by tier, use the **Filter** drop-down menu, click **Active tiers** or **Retired tiers**, and select a tier. ![Drop-down menu to filter by tier](/assets/images/help/sponsors/filter-drop-down.png)
+
+### Viewing recent sponsorship activity
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### Exporting your sponsorship data
+
+You can export your sponsorship transactions by month. {% data variables.product.company_short %} will send you an email with transaction data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. Click {% octicon "download" aria-label="The download icon" %} **Export**. ![Export button](/assets/images/help/sponsors/export-all.png)
+1. Choose a time frame and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..1126a8c136
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: Attributing sponsorships to your organization
+intro: You can attribute the sponsorships paid by one of your organizations to another organization.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. Navigate to the organization whose sponsorships you want to attribute to another organization.
+2. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png)
+1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..5bfcaebe24
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: Sponsoring open source contributors
+intro: 'You can sponsor contributors, receive updates on developers and organizations you sponsor, and display a sponsor badge throughout {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..7f3e940ab5
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: Managing your sponsorship
+intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account.
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### Managing the privacy setting for your sponsorship
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Managing email updates for your sponsorship
+
+You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address.
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### Дополнительная литература
+
+- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)"
+- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)"
diff --git a/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..611f1aa2c1
--- /dev/null
+++ b/translations/ru-RU/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: Sponsoring an open source contributor
+intro: 'You can make a monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.'
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### About sponsorships
+
+{% data reusables.sponsors.sponsorship-details %}
+
+You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons.
+- Sustaining specific libraries that your organization's work depends on
+- Investing in the ecosystem you rely on as a organization (such as blockchain)
+- Developing brand awareness as an organization that values open source
+- Thanking open source developers for building libraries that complement the product your organization offers
+
+You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist).
+
+{% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)."
+
+When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)."
+
+If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_dotcom %} is not responsible for how developers represent themselves nor does {% data variables.product.prodname_dotcom %} endorse any sponsored open source projects. The claims are solely the responsibility of the developer receiving the funds. Make sure you trust a person before offering a sponsorship. For more information, see the [{% data variables.product.prodname_sponsors %} Additional Terms](/github/site-policy/github-sponsors-additional-terms).
+
+{% endnote %}
+
+### Sponsoring an account
+
+Before you can sponsor an account, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
+
+1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor.
+1. Navigate to your sponsorship dashboard for the account.
+   - To sponsor a developer, under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png)
+   - To sponsor an organization, to the right of the organization's name, click **Sponsor**. ![Sponsor button](/assets/images/help/sponsors/sponsor-org-button.png)
+1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![Edit payment button](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![Radio buttons to choose who can see your sponsorship](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/ru-RU/data/glossaries/external.yml b/translations/ru-RU/data/glossaries/external.yml
index 4b2ba682ee..6448228354 100644
--- a/translations/ru-RU/data/glossaries/external.yml
+++ b/translations/ru-RU/data/glossaries/external.yml
@@ -1,7 +1,7 @@
 ---
 - 
   term: '@упоминание'
-  description: уведомить человека на GitHub, используя `@` перед именем пользователя. Пользователи в организации на GitHub также могут быть частью команды, которую можно упомянуть.
+  description: Уведомить человека на GitHub, используя `@` перед именем пользователя. Пользователи в организации на GitHub также могут быть частью команды, которую можно упомянуть.
 - 
   term: токен доступа
   description: >-
@@ -181,7 +181,7 @@
 - 
   term: ветвь по умолчанию
   description: >-
-    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called `main`, and is often the default branch.
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}, and is often the default branch.
 - 
   term: Диаграмма зависимостей
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required.{% else %}Name often chosen as an alternative to `master` for the default branch of a repository.{% endif %}
 - 
   term: главная (ветвь)
   description: >-
-    The default branch in many Git repositories. By default, when you create a new Git repository on the command line a branch called `master` is created. Many tools now use an alternative name for the default branch. For example, when you create a new repository on GitHub the default branch is called `main`.
+    The default branch in many Git repositories. By default, when you create a new Git repository on the command line, a branch called `master` is created. Many tools now use an alternative name for the default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} For example, when you create a new repository on GitHub, the default branch is called `main`.{% endif %}
 - 
   term: Диаграмма участников
   description: График репозитория, на котором показаны все ответвления репозитория.
diff --git a/translations/ru-RU/data/glossaries/internal.yml b/translations/ru-RU/data/glossaries/internal.yml
index 71a3c8ee16..34ba2ff602 100644
--- a/translations/ru-RU/data/glossaries/internal.yml
+++ b/translations/ru-RU/data/glossaries/internal.yml
@@ -60,12 +60,16 @@
 - 
   term: Azure
   description: Платформа Microsoft облачных вычислений.
+- 
+  term: Azure DevOps
+  description: >-
+    A Microsoft product offering source code hosting, issues, CI/CD pipelines, and other developer services. The on-premises version was formerly known as Team Foundation Server. The cloud-hosted version was formerly known as Visual Studio Team Services.
 - 
   term: чистый репозиторий
   description: >-
     Чистый репозиторий обычно представляет собой каталог с соответствующим названием и с расширением .git, который не имеет локально выгруженных копий файлов, изменения которых контролируются. То есть все управляющие и контрольные файлы Git, которые обычно должны находиться в скрытом подкаталоге .git, вместо этого расположены в каталоге repository.git, а все остальные файлы отсутствуют и не выгружаются. Обычно издатели публичных репозиториев обеспечивают свободный доступ к чистым репозиториям.
 - 
-  term: Инструмент очистки репозитория BFG
+  term: Средство очистки репозитория BFG
   description: BFG. Инструмент стороннего разработчика, предназначенный для удаления данных из журнала репозитория Git.
 - 
   term: объект типа «большой двоичный объект»
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    Продукт Microsoft для управления исходным кодом и другими службами команды.
+    The former name of a Microsoft product that provides source code management and other team services. Now known as Azure DevOps Server.
 - 
   term: Textile
   description: >-
diff --git a/translations/ru-RU/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/ru-RU/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..f3f59a1364
--- /dev/null
+++ b/translations/ru-RU/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: Access to package version deletion
+  description: >-
+    This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: Deployments
+  description: >-
+    This preview adds support for deployments mutations and new deployments features.
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - More detailed information about a pull request's merge state.
+  description: >-
+    This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - Update multiple refs in a single operation.
+  description: This preview adds support for updating multiple refs in a single operation.
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: Project Event Details
+  description: >-
+    This preview adds project, project card, and project column details to project-related issue events.
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: Create content attachments
+  description: This preview adds support for creating content attachments.
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: Labels Preview
+  description: >-
+    This preview adds support for adding, updating, creating and deleting labels.
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: Import Project
+  description: This preview adds support for importing projects.
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Team Review Assignments Preview
+  description: >-
+    This preview adds support for updating the settings for team review assignment.
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/ru-RU/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/ru-RU/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..3d4deaabeb
--- /dev/null
+++ b/translations/ru-RU/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
+    reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user` will be removed. Use the `assignee` field instead.'
+    reason: Assignees can now be mannequins.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
+    reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
+    reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: '`user` will be removed. Use the `assignee` field instead.'
+    reason: Assignees can now be mannequins.
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
+    reason: '`Sponsorship.maintainer` will be removed.'
+    date: '2020-04-01T00:00:00+00:00'
+    criticality: breaking
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All pending members consume a license
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.'
+    reason: Repository invitations can now be associated with an email, not only an invitee.
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: '`timeline` will be removed. Use Issue.timelineItems instead.'
+    reason: '`timeline` will be removed'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
+    reason: '`timeline` will be removed'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: '`INVITEE_LOGIN` will be removed.'
+    reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.'
+    reason: '`Sponsorship.sponsor` will be removed.'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All members consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All outside collaborators consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` will be removed.'
+    reason: All pending collaborators consume a license
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.'
+    reason: DRAFT state will be removed from this enum and `isDraft` should be used instead
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: breaking
+    owner: nplasterer
diff --git a/translations/ru-RU/data/learning-tracks/README.md b/translations/ru-RU/data/learning-tracks/README.md
index ec0f70309e..d8bd99c5fe 100644
--- a/translations/ru-RU/data/learning-tracks/README.md
+++ b/translations/ru-RU/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # Learning Tracks (aka Learning Paths)
 
-Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis.
\ No newline at end of file
+Learning tracks are a collection of articles that help you master a particular subject. Learning tracks are defined on a per-product basis. For example, see https://docs.github.com/en/actions/guides.
+
+Learning track data for a product is defined in two places:
+
+1. A simple array of learning track names is defined in the product sublanding index page frontmatter.
+
+    For example, in `content/actions/guides/index.md`:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. Additional data for each track is defined in a YAML file named for the **product** in the `data` directory.
+
+    For example, in `data/learning-tracks/actions.yml`, each of the items from the content file's `learningTracks` array is represented with additional data such as `title`, `description`, and an array of `guides` links.
+
+    One learning track in this YAML **per version** must be designated as a "featured" learning track via `featured_track: true`, which will set it to appear at the top of the product sublanding page. A test will fail if this property is missing.
+
+    The `featured_track` property can be a simple boolean (i.e., `featured_track: true`) or it can be a string that includes versioning statements (e.g., `featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`). If you use versioning, you'll have multiple `featured_track`s per YML file, but make sure that only one will render in each currently supported version. A test will fail if there are more or less than one featured link for each version.
+
+Versioning for learning tracks is processed at page render time. The code lives in [`lib/learning-tracks.js`](lib/learning-tracks.js), which is called by `page.render()`. The processed learning tracks are then rendered by `layouts/product-sublanding.html`.
+
+The schema for validating the learning track YAML lives in [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) and is exercised by [`tests/content/lint-files.js`](tests/content/lint-files.js).
diff --git a/translations/ru-RU/data/learning-tracks/actions.yml b/translations/ru-RU/data/learning-tracks/actions.yml
index c825769cc8..d532f1a2e7 100644
--- a/translations/ru-RU/data/learning-tracks/actions.yml
+++ b/translations/ru-RU/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: 'Build and test code'
   description: 'You can create custom continuous integration (CI) workflows right in your repository.'
diff --git a/translations/ru-RU/data/learning-tracks/admin.yml b/translations/ru-RU/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..5e06a59c40
--- /dev/null
+++ b/translations/ru-RU/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: 'Get started with {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/ru-RU/data/release-notes/2-21/19.yml b/translations/ru-RU/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..5726fd8bda
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/2-21/19.yml
@@ -0,0 +1,18 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - User saw 500 error when executing git operations on an instance configured with LDAP authentication.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/ru-RU/data/release-notes/2-21/20.yml b/translations/ru-RU/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..4a3d11dfb6
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/2-21/20.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/ru-RU/data/release-notes/2-21/21.yml b/translations/ru-RU/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..2a76183f01
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/2-21/21.yml
@@ -0,0 +1,15 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - Security alerts are not reported when pushing to a repository on the command line.
diff --git a/translations/ru-RU/data/release-notes/2-22/11.yml b/translations/ru-RU/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..909f09ff83
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/2-22/11.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Syntax highlighting could fail due to the Treelights container running out of memory.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ru-RU/data/release-notes/2-22/12.yml b/translations/ru-RU/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..bb7d46505d
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/2-22/12.yml
@@ -0,0 +1,22 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ru-RU/data/release-notes/2-22/13.yml b/translations/ru-RU/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..ef4bbc46f3
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/2-22/13.yml
@@ -0,0 +1,20 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ru-RU/data/release-notes/3-0/0.yml b/translations/ru-RU/data/release-notes/3-0/0.yml
index f63b941d5a..c71602c75d 100644
--- a/translations/ru-RU/data/release-notes/3-0/0.yml
+++ b/translations/ru-RU/data/release-notes/3-0/0.yml
@@ -134,6 +134,7 @@ sections:
     - A race condition can cause dependency graph database migrations to appear to fail.
     - Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
   deprecations:
     - 
       heading: Deprecation of GitHub Enterprise Server 2.19
diff --git a/translations/ru-RU/data/release-notes/3-0/1.yml b/translations/ru-RU/data/release-notes/3-0/1.yml
index 3e7296628a..9df6976efc 100644
--- a/translations/ru-RU/data/release-notes/3-0/1.yml
+++ b/translations/ru-RU/data/release-notes/3-0/1.yml
@@ -45,6 +45,7 @@ sections:
     - 'Dependency graph fails to parse `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.'
     - 'Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI.'
     - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).'
+    - 'When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.'
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/ru-RU/data/release-notes/3-0/2.yml b/translations/ru-RU/data/release-notes/3-0/2.yml
index e38aa78664..52e610b757 100644
--- a/translations/ru-RU/data/release-notes/3-0/2.yml
+++ b/translations/ru-RU/data/release-notes/3-0/2.yml
@@ -31,6 +31,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance:
 
diff --git a/translations/ru-RU/data/release-notes/3-0/3.yml b/translations/ru-RU/data/release-notes/3-0/3.yml
index 4255a873dc..355b774734 100644
--- a/translations/ru-RU/data/release-notes/3-0/3.yml
+++ b/translations/ru-RU/data/release-notes/3-0/3.yml
@@ -30,6 +30,7 @@ sections:
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
     - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
     - |
       Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion.
       To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance:
diff --git a/translations/ru-RU/data/release-notes/3-0/4.yml b/translations/ru-RU/data/release-notes/3-0/4.yml
index b3a39c1743..4b70a13ae5 100644
--- a/translations/ru-RU/data/release-notes/3-0/4.yml
+++ b/translations/ru-RU/data/release-notes/3-0/4.yml
@@ -23,3 +23,4 @@ sections:
     - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
     - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters.
     - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/ru-RU/data/release-notes/3-0/5.yml b/translations/ru-RU/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..1bcc84c956
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/3-0/5.yml
@@ -0,0 +1,27 @@
+---
+date: '2021-04-14'
+intro: 'The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Some logs were not included in the log forwarding configuration.
+    - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
+    - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
+    - Pages were not getting published when using custom CA certificate.
+    - Packages related subdomains were not showing up in the "Test domain settings" prompt for subdomain isolation.
+    - The `X-GitHub-Enterprise-Host` header sent with webhooks included a random string, rather than the hostname of the GitHub Enterprise Server instance that sent the HTTP POST payload.
+    - Upgrading from 2.22.x to 3.0.x would fail if GitHub Actions had previously been enabled, but disabled before the upgrade.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
+    - reStructuredText (RST) rendering in the web UI would fail and instead displayed raw RST markup text.
+    - Email notifications for Secret Scanning alerts were not sent to authorized users when the Dependency Graph was not fully enabled.
+    - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
+    - Jupyter notebooks with non-ASCII characters could fail to render.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds.
diff --git a/translations/ru-RU/data/release-notes/3-0/6.yml b/translations/ru-RU/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..83604b5f77
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/3-0/6.yml
@@ -0,0 +1,30 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - During upgrades, the process would pause indefinitely after `cleanup nomad job`.
+    - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
+    - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
+    - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
+    - Upgrades did not include the latest version of Actions runner properly installed.
+    - '`github-env` configuration could result in zombie processes.'
+    - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
+    - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
+    - Organizations or projects with errors blocked migration and could not be excluded.
+    - The Create Repository button was disabled for users who belonged to more than 50 organizations.
+    - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful.
+    - The `rms-packages` index was shown in the site admin dashboard.
+    - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form.
+    - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured.
+    - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
+    - Code Scanning backend services did not start up reliably after applying hotpatches.
+  changes:
+    - Preflight checks allow all AWS instance types by default.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ru-RU/data/release-notes/3-0/7.yml b/translations/ru-RU/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..4c176c0b41
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/3-0/7.yml
@@ -0,0 +1,23 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
diff --git a/translations/ru-RU/data/release-notes/3-1/0-rc1.yml b/translations/ru-RU/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..28f7719683
--- /dev/null
+++ b/translations/ru-RU/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security Secret Scanning
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository.
+
+          This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}:
+
+          - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37
+          - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)
+          - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets
+          - Updated the index view to made it easy to triage secrets in bulk
+          - Reduced the false positive rate on many patterns
+
+          Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+    - 
+      heading: GitHub Advanced Security billing improvements
+      notes:
+        - |
+          This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}:
+
+          - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+          - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+    - 
+      heading: Dependabot improvements
+      notes:
+        - |
+          This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}:
+
+          - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
+          - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository).
+          - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."'
+    - 
+      heading: GitHub Actions Workflow Visualization beta
+      notes:
+        - |
+
+          GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can:
+          - View and understand complex workflows
+          - Track progress of workflows in real-time
+          - Troubleshoot runs quickly by easily accessing logs and jobs metadata
+          - Monitor progress of deployment jobs and easily access deployment targets
+
+          For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+    - 
+      heading: OAuth 2.0 Device Authorization Grant
+      notes:
+        - |
+          [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser.
+
+          Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow.
+    - 
+      heading: Pull request auto-merge
+      notes:
+        - |
+          With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+    - 
+      heading: Custom notifications
+      notes:
+        - |
+          You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+  changes:
+    - 
+      heading: Administration Changes
+      notes:
+        - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+        - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+        - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+        - Check annotations older than four months will be archived.
+    - 
+      heading: Security Changes
+      notes:
+        - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).'
+        - SARIF upload support increased to a maximum of 5000 results per upload.
+    - 
+      heading: Developer Changes
+      notes:
+        - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to.
+        - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)."
+        - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."'
+        - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.'
+        - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.'
+    - 
+      heading: Изменения API
+      notes:
+        - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning).
+        - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints.
+  known_issues:
+    - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
+    - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
+    - Custom firewall rules are not maintained during an upgrade.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.20
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.21
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of Legacy GitHub App Webhook Events
+      notes:
+        - 'Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).'
+    - 
+      heading: Deprecation of Legacy GitHub Apps Endpoint
+      notes:
+        - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0.  More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).
+    - 
+      heading: Deprecation of OAuth Application API
+      notes:
+        - 'GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).'
+    - 
+      heading: Deprecation of GitHub Actions short SHA support
+      notes:
+        - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/ru-RU/data/reusables/actions/actions-cli.md b/translations/ru-RU/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..9de328800e
--- /dev/null
+++ b/translations/ru-RU/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+For information on setting up {% data variables.product.prodname_cli %}, see "[Managing GitHub Actions with GitHub CLI](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)."
diff --git a/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md b/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..493e81cb45
--- /dev/null
+++ b/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.
+
+##### Examples using concurrency and the default behavior
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### Example using concurrency to cancel any in-progress job or run
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/ru-RU/data/reusables/actions/concurrency-beta.md b/translations/ru-RU/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..c3f2c9a831
--- /dev/null
+++ b/translations/ru-RU/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Concurrency is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/actions/enterprise-github-connect-warning.md b/translations/ru-RU/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..ce755253ef
--- /dev/null
+++ b/translations/ru-RU/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom %}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/actions/enterprise-no-internet-actions.md b/translations/ru-RU/data/reusables/actions/enterprise-no-internet-actions.md
index 9f2287cfee..e568edbd05 100644
--- a/translations/ru-RU/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/ru-RU/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} is designed to work in environments without internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+{% data variables.product.prodname_actions %} on {% data variables.product.product_name %} is designed to work in environments without full internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
diff --git a/translations/ru-RU/data/reusables/actions/forked-secrets.md b/translations/ru-RU/data/reusables/actions/forked-secrets.md
index 600bc85a95..3c6011328b 100644
--- a/translations/ru-RU/data/reusables/actions/forked-secrets.md
+++ b/translations/ru-RU/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.
+With the exception of `GITHUB_TOKEN`, secrets are not passed to the runner when a workflow is triggered from a forked repository.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/ru-RU/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..43937ba24a
--- /dev/null
+++ b/translations/ru-RU/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.product_location %}:
+
+- **Committers** is the number of committers who contributed to at least one {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
+- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
+
+If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
+
+When you remove a user from your enterprise account, the user's license is freed within 24 hours.
+
+{% note %}
+
+**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
+
+{% endnote %}
diff --git a/translations/ru-RU/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/ru-RU/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..d0ea836b42
--- /dev/null
+++ b/translations/ru-RU/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Periodically you should check that your use is within your license capacity.
diff --git a/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md
index b6abfe68c7..1b77a9051e 100644
--- a/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% endif %}
+{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. {% if currentVersion == "free-pro-team@latest" %}For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)."{% elsif currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your Enterprise](/admin/advanced-security)."{% endif %}
 
 You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose.
 
diff --git a/translations/ru-RU/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/ru-RU/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..ff7d774004
--- /dev/null
+++ b/translations/ru-RU/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify:
+
+- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company.
+- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced.
+
+When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/ru-RU/data/reusables/advanced-security/ghas-helps-developers.md b/translations/ru-RU/data/reusables/advanced-security/ghas-helps-developers.md
index fcd5fb9586..e1b69b9a6e 100644
--- a/translations/ru-RU/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/ru-RU/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% data variables.product.prodname_GH_advanced_security %} helps developers improve and maintain the security and quality of code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/ru-RU/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..d447e24e28
--- /dev/null
+++ b/translations/ru-RU/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+When you enable or disable {% data variables.product.prodname_advanced_security %} for repositories, {% data variables.product.prodname_dotcom %} displays an overview of changes to the use of your license. If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up.
+
+If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available.{% if currentVersion == "free-pro-team@latest" %} If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository.{% endif %}
+
+As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal.
diff --git a/translations/ru-RU/data/reusables/cli/actions-cli-version.md b/translations/ru-RU/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..83cd5971dd
--- /dev/null
+++ b/translations/ru-RU/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+To access all of the {% data variables.product.prodname_actions %}-related commands, you must use version 1.9.0 or greater.
diff --git a/translations/ru-RU/data/reusables/cli/cli-auth.md b/translations/ru-RU/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..be9a823c3c
--- /dev/null
+++ b/translations/ru-RU/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} can authenticate using your {% data variables.product.prodname_dotcom %} account. Before running {% data variables.product.prodname_cli %} commands, you will need to authenticate by running `gh auth login`. For more information on command line authentication, see "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)."
diff --git a/translations/ru-RU/data/reusables/cli/cli-manual.md b/translations/ru-RU/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..dd2012d873
--- /dev/null
+++ b/translations/ru-RU/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+For more information about {% data variables.product.prodname_cli %}, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/).
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/cli/cli-repo.md b/translations/ru-RU/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..535b1d8e8c
--- /dev/null
+++ b/translations/ru-RU/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} commands must be run within the repository that you want to interact with, so you must first navigate to the directory containing the local copy of your repository. Alternatively, you can specify a repository by passing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY` or `--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY` or `--repo OWNER/REPOSITORY`{% endif %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Replace `HOSTNAME` with the name of {% data variables.product.product_location %}. {% endif %}Replace `OWNER` with owner of the repository. Replace `REPOSITORY` with the name of the repository.
diff --git a/translations/ru-RU/data/reusables/cli/download-update-cli.md b/translations/ru-RU/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..b26363cf45
--- /dev/null
+++ b/translations/ru-RU/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+To download or upgrade {% data variables.product.prodname_cli %}, follow the instructions in the [{% data variables.product.prodname_cli %} README](https://github.com/cli/cli#installation).
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/ru-RU/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/ru-RU/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/ru-RU/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/ru-RU/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..a101d1809f
--- /dev/null
+++ b/translations/ru-RU/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`, `csharp`, `go`, `java`, `javascript`, and `python`
diff --git a/translations/ru-RU/data/reusables/code-scanning/enabling-options.md b/translations/ru-RU/data/reusables/code-scanning/enabling-options.md
index 3e78b63452..137dd09d78 100644
--- a/translations/ru-RU/data/reusables/code-scanning/enabling-options.md
+++ b/translations/ru-RU/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">Running {% data variables.product.prodname_codeql %} code scanning in your CI system</a>").
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      Third&#8209;party
-    </td>
-    
-    <td>
-      Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or generated externally and uploaded to {% data variables.product.product_name %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Uploading a SARIF file to {% data variables.product.prodname_dotcom %}</a>").
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)").
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | Using {% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "[Running {% data variables.product.prodname_codeql %} code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)").
+{%- endif %}
+| Third&#8209;party | Using
+{% data variables.product.prodname_actions %} (see "[Setting up {% data variables.product.prodname_code_scanning %} using actions](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)") or generated externally and uploaded to {% data variables.product.product_name %} (see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)").|
diff --git a/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md
index c5142332f6..6881be29fa 100644
--- a/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** SARIF upload supports a maximum of 1000 results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries.
+**Note:** SARIF upload supports a maximum of {% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries.
 
 {% endnote %}
diff --git a/translations/ru-RU/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..52dda51137
--- /dev/null
+++ b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**Note:** Uploading SARIF data to display as {% data variables.product.prodname_code_scanning %} results in {% data variables.product.product_name %} is supported for organization-owned repositories with {% data variables.product.prodname_GH_advanced_security %} enabled{% if currentVersion == "free-pro-team@latest" %}, and public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/ru-RU/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..5c772293bc
--- /dev/null
+++ b/translations/ru-RU/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.product.product_location %}.
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/codespaces/about-personalization.md b/translations/ru-RU/data/reusables/codespaces/about-personalization.md
index 8f5ccbdb99..958370ebd8 100644
--- a/translations/ru-RU/data/reusables/codespaces/about-personalization.md
+++ b/translations/ru-RU/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-You can also personalize aspects of the codespace environment for any codespace that your account creates. Personalization can include shell preferences and additional tools.
+You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. Personalization can include shell preferences and additional tools.
diff --git a/translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md b/translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..39b29dc4a0
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+You can forward ports in your codespace to test and debug your application.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..8031bfb4af
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index c49f29679d..5e0618af02 100644
--- a/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md b/translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..475114c1c5
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Each of these has a different level of resources and a different billing tier.<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**Note:** {% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types:
+
+* **Basic** for updating a file and raising a pull request
+* **Standard** for editing a website
+* **Premium** for high compute tasks such as data analysis
diff --git a/translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..87bfa539ff
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users.
+
+For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..fed860897b
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/ru-RU/data/reusables/codespaces/rebuild-command.md b/translations/ru-RU/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..ea9e45b032
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/recovery-mode.md b/translations/ru-RU/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..fa4e73d013
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/release-stage.md b/translations/ru-RU/data/reusables/codespaces/release-stage.md
index 2fd3475ccd..57e551dd72 100644
--- a/translations/ru-RU/data/reusables/codespaces/release-stage.md
+++ b/translations/ru-RU/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. During the beta period, {% data variables.product.prodname_dotcom %} does not make any guarantees about the availability of {% data variables.product.prodname_codespaces %}. For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
+**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)."
 
 {% endnote %}
diff --git a/translations/ru-RU/data/reusables/codespaces/secret-precedence.md b/translations/ru-RU/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..582b91c1aa
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/secrets-naming.md b/translations/ru-RU/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..eddb8aa7f5
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+The following rules apply to secret names:
+
+* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
+* Secret names must not start with the `GITHUB_` prefix.
+* Secret names must not start with a number.
+* Secret names are not case-sensitive.
+* Secret names must be unique at the level they are created at.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/secrets-on-start.md b/translations/ru-RU/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..c4a5bf3b41
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it.
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md b/translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..90b3503dcd
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/source-control-display.md b/translations/ru-RU/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..09917cd3c8
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. In the Activity Bar, click the **Source Control** view.
+
+  ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/type-port-label.md b/translations/ru-RU/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..498c9eb752
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index 59c85e47d7..afb626e71c 100644
--- a/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-You can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..a5e98437c0
--- /dev/null
+++ b/translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**.
+
+  !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md
index deb30db8e8..9a706f0d08 100644
--- a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@ The following table shows, for each package manager:
 | Composer                          | `composer`       | v1, v2                         |        **✓**         |       **✓**        |           |
 | Докер                             | `докер`          | v1                             |        **✓**         |       **✓**        |           |
 | Hex                               | `mix`            | v1                             |                      |       **✓**        |           |
-| elm-package                       | `elm`            | v0.18, v0.19                   |        **✓**         |       **✓**        |           |
+| elm-package                       | `elm`            | v0.19                          |        **✓**         |       **✓**        |           |
 | git submodule                     | `gitsubmodule`   | N/A (no version)               |        **✓**         |       **✓**        |           |
 | GitHub Actions                    | `github-actions` | N/A (no version)               |        **✓**         |       **✓**        |           |
 | Go modules                        | `gomod`          | v1                             |        **✓**         |       **✓**        |   **✓**   |
diff --git a/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md
index 54d745b497..3d29c028b4 100644
--- a/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@ When you create a pull request from a forked repository to the base repository,
 
 Workflows don't run on forked repositories by default. You must enable GitHub Actions in the **Actions** tab of the forked repository.
 
+{% if currentVersion == "free-pro-team@latest"%}
+When a first-time contributor submits a pull request to a public repository, a maintainer with write access must approve running workflows on the pull request. For more information, see "[Approving workflow runs from public forks](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)."
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} The permissions for the `GITHUB_TOKEN` in forked repositories is read-only. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
 
 {% note %}
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-report-download.md
index 34834c681c..5ac6ab4bb1 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. Optionally, click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![Download CSV report](/assets/images/help/billing/actions-packages-report-download.png)
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} to the account's primary email address. ![Download CSV report](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/change_plan_duration.md b/translations/ru-RU/data/reusables/dotcom_billing/change_plan_duration.md
index a43cb113de..31f59222d7 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. Under "Billing overview", click **Change to yearly billing** or **Change to monthly billing**. ![Billing overview change plan button](/assets/images/help/billing/change-plan-duration-link.png)
+1. Under "Current monthly bill" or "Current yearly bill", click **Switch to yearly billing** or **Switch to monthly billing**. ![Billing overview change plan button](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/choose_org_plan.md b/translations/ru-RU/data/reusables/dotcom_billing/choose_org_plan.md
index 80d23b08e6..2121e37d1c 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. If you're upgrading from {% data variables.product.prodname_free_team %}, under "Upgrading to", select a product. ![Upgrade button](/assets/images/help/billing/upgrade-to-product.png)
+1. Under "Compare plans", you can compare the features of each plan. Depending on your current plan and what plan you have chosen, click either **Upgrade to Team** or **Upgrade to Enterprise**. ![Compare plans and upgrade](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/enter-payment-info.md b/translations/ru-RU/data/reusables/dotcom_billing/enter-payment-info.md
index 461de210a0..436d92d9df 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. Under "Billing information", choose to pay with a credit card or PayPal. ![Switch Billing payment methods](/assets/images/help/billing/billing_switch_payments.png)
+1. Under "Payment method", choose to pay with a credit card or PayPal. ![Switch Billing payment methods](/assets/images/help/billing/billing_switch_payments.png)
 1. Complete the payment information form, then click **Submit**.
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/lfs-add-data.md b/translations/ru-RU/data/reusables/dotcom_billing/lfs-add-data.md
index 5769f06c4a..8f4a7c8ca7 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the Edit drop-down and click **Add more data packs**. ![Add more data button](/assets/images/help/billing/data-pack-purchase-more.png)
+1. Next to "{% data variables.large_files.product_name_short %} Data", click **Add more data** or use the **Edit** drop-down and click **Add more data packs**. ![Add more data button](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/ru-RU/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..4f2bd7bf2d
--- /dev/null
+++ b/translations/ru-RU/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. At the top of the page, under "Payment information", click **Manage spending limit**. ![Manage spending limit link](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/next_billing_date.md b/translations/ru-RU/data/reusables/dotcom_billing/next_billing_date.md
index c415f04fea..4b342eafae 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. Under "Billing overview", review when your next payment is due. ![Next billing date](/assets/images/help/billing/settings_billing_next_payment.png)
+1. At the top of the page, under "Next payment due", review when your next payment is due. ![Next billing date](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/review-pending-changes.md b/translations/ru-RU/data/reusables/dotcom_billing/review-pending-changes.md
index 49820941df..bd29edbd23 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. Under "Subscriptions," review your pending changes. ![Subscriptions section of billing settings listing any pending subscription changes](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. Under "Current plan", review your pending changes. ![Subscriptions section of billing settings listing any pending subscription changes](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/update_payment_method.md b/translations/ru-RU/data/reusables/dotcom_billing/update_payment_method.md
index 4f735635cd..0aa1c98a2f 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. Under "Billing overview", click **Update payment method**. ![Update payment method button](/assets/images/help/billing/update_payment_method.png)
+1. At the top of the page, under "Payment information", click **Update payment method**. ![Update payment method button](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/upgrade_org.md b/translations/ru-RU/data/reusables/dotcom_billing/upgrade_org.md
index 60ea8fef5c..aba4840ee5 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. If you're upgrading from {% data variables.product.prodname_free_team %}, click **Upgrade options**. If you're upgrading from {% data variables.product.prodname_team %}, use the **Edit** drop-down and click **Upgrade**. ![Upgrade options button](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. Click **Upgrade** next to "Current plan".
diff --git a/translations/ru-RU/data/reusables/dotcom_billing/view-payment-history.md b/translations/ru-RU/data/reusables/dotcom_billing/view-payment-history.md
index 3bc9031627..9bec769655 100644
--- a/translations/ru-RU/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/ru-RU/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. Under "Billing overview", click **View payment history**. ![View payment history link](/assets/images/help/billing/view-payment-history-link.png)
+1. At the top of the page, under "Next payment due", click **View payment history**. ![View payment history link](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/add-a-domain.md b/translations/ru-RU/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..f6a4648a23
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. Click **Add a domain**. ![Add a domain button](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/ru-RU/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..e30ede90e5
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/ru-RU/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..0783f95521
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+You can confirm that the websites and email addresses listed on the profiles of any organization owned by your enterprise account are controlled by your enterprise by verifying the domains. Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %}
+
+Organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain.
+
+After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/domains-approving.md b/translations/ru-RU/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/domains-removing.md b/translations/ru-RU/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/domains-verifying.md b/translations/ru-RU/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..49018320b4
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output.
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. Optionally, after the "Verified" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service. ![Verified badge](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..4087e5cdd0
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+The domains can be inherited from the enterprise account or configured for the specific organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..eb771a1f37
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. Click **Save**.
diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/ru-RU/data/reusables/enterprise-accounts/verified-domains-tab.md
index 35420a6888..85644af45c 100644
--- a/translations/ru-RU/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/ru-RU/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. Under "Settings", click **Verified domains**. !["Verified domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/ru-RU/data/reusables/enterprise_deprecation/deprecation_details.md
index a6ccee5e90..2d220a0ba0 100644
--- a/translations/ru-RU/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/ru-RU/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1 +1 @@
-No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">upgrade to the latest version of GitHub Enterprise</a>. For help with the upgrade, <a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">contact GitHub Enterprise support</a>.
+No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">upgrade to the latest version of GitHub Enterprise</a>. For help with the upgrade, <a href="https://enterprise.github.com/support">contact GitHub Enterprise support</a>.
diff --git a/translations/ru-RU/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/ru-RU/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..728c8da3a1
--- /dev/null
+++ b/translations/ru-RU/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
+
+Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
+
+Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
+
+| User licenses                  |                           vCPUs |                                  Memory |                        Attached storage | Root storage |
+|:------------------------------ | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
+| Trial, demo, or 10 light users |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ |       200 GB |
+| 10 to 3,000                    |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ |       200 GB |
+| 3,000 to 5000                  |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB |       200 GB |
+| 5,000 to 8000                  | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB |       200 GB |
+| 8,000 to 10,000+               | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB |       200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+For more information about hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md
index 4b1379243e..e7d45c6fb3 100644
--- a/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/ru-RU/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Warning**: Changing this setting will cause {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} to restart. You should time this change carefully, to minimize downtime.
+**Warning**: Changing this setting will cause user-facing services on {% data variables.product.prodname_ghe_server %} to restart. You should time this change carefully, to minimize downtime for users.
 
 {% endwarning %}
diff --git a/translations/ru-RU/data/reusables/gated-features/actions-shared.md b/translations/ru-RU/data/reusables/gated-features/actions-shared.md
index d5bceb9ab1..1b9eb6926d 100644
--- a/translations/ru-RU/data/reusables/gated-features/actions-shared.md
+++ b/translations/ru-RU/data/reusables/gated-features/actions-shared.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. 
+{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}. {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. 
diff --git a/translations/ru-RU/data/reusables/gated-features/code-scanning.md b/translations/ru-RU/data/reusables/gated-features/code-scanning.md
index 775fa28256..3786dad893 100644
--- a/translations/ru-RU/data/reusables/gated-features/code-scanning.md
+++ b/translations/ru-RU/data/reusables/gated-features/code-scanning.md
@@ -1,5 +1,5 @@
-{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
-{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository.
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
 {%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_code_scanning_capc %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
 {%- else %}
diff --git a/translations/ru-RU/data/reusables/gated-features/ghas.md b/translations/ru-RU/data/reusables/gated-features/ghas.md
index fcf1b455c7..166bbffcbe 100644
--- a/translations/ru-RU/data/reusables/gated-features/ghas.md
+++ b/translations/ru-RU/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_GH_advanced_security %} is also included in {% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %} and in all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
+{% data variables.product.prodname_GH_advanced_security %} licenses are available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/gated-features/github-insights.md b/translations/ru-RU/data/reusables/gated-features/github-insights.md
index f99859ae15..fb6b9703b2 100644
--- a/translations/ru-RU/data/reusables/gated-features/github-insights.md
+++ b/translations/ru-RU/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %} is available with {% data variables.product.prodname_ghe_one %}. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."
+{% data variables.product.prodname_insights %} is available with {% data variables.product.prodname_ghe_one %}. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/gated-features/packages.md b/translations/ru-RU/data/reusables/gated-features/packages.md
index 46b66987c9..3222088079 100644
--- a/translations/ru-RU/data/reusables/gated-features/packages.md
+++ b/translations/ru-RU/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}.
+{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_managed %}.
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access {% data variables.product.prodname_github_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/ru-RU/data/reusables/gated-features/secret-scanning.md b/translations/ru-RU/data/reusables/gated-features/secret-scanning.md
index f67bcdf4e4..8ae85ccf2f 100644
--- a/translations/ru-RU/data/reusables/gated-features/secret-scanning.md
+++ b/translations/ru-RU/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% if currentVersion == "free-pro-team@latest" %}in public repositories, and in private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} is available for all public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled.
+{%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_secret_scanning_caps %} is available as part of {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release.
-{% endif %}
\ No newline at end of file
+{%- else %}
+{% data variables.product.prodname_secret_scanning_caps %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/github-actions/forked-write-permission.md b/translations/ru-RU/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..3fe9804246
--- /dev/null
+++ b/translations/ru-RU/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+You can use the `permissions` key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the **Send write tokens to workflows from pull requests** option in the {% data variables.product.prodname_actions %} settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/github-actions/github-token-available-permissions.md b/translations/ru-RU/data/reusables/github-actions/github-token-available-permissions.md
new file mode 100644
index 0000000000..4e5ca65fe7
--- /dev/null
+++ b/translations/ru-RU/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+Available scopes and access values:
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
+
+You can use the following syntax to define read or write access for all of the available scopes:
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/github-actions/github-token-permissions.md b/translations/ru-RU/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..88604df1dc
--- /dev/null
+++ b/translations/ru-RU/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+The `GITHUB_TOKEN` secret is set to an access token for the repository each time a job in a workflow begins. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 743020588d..c5a1bf2f45 100644
--- a/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret.
+Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}The `permissions` key specifies the access granted to the `GITHUB_TOKEN`.{% endif %}
diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index 0632ee2cdc..2a7fa3e50a 100644
--- a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **Предупреждение**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
diff --git a/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md b/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md
index e14f648811..d3443cc757 100644
--- a/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**Warning**: Ubuntu 16.04 is being deprecated. If any of your workflows use Ubuntu 16.04, migrate to Ubuntu 20.04 or 18.04. For more information, see [the blog post](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021).
+
+{% endwarning %}
+
 | Virtual environment  | YAML workflow label                |
 | -------------------- | ---------------------------------- |
 | Windows Server 2019  | `windows-latest` or `windows-2019` |
+| Windows Server 2016  | `windows-2016`                     |
 | Ubuntu 20.04         | `ubuntu-latest` or `ubuntu-20.04`  |
 | Ubuntu 18.04         | `ubuntu-18.04`                     |
-| Ubuntu 16.04         | `ubuntu-16.04`                     |
 | macOS Big Sur 11.0   | `macos-11.0`                       |
 | macOS Catalina 10.15 | `macos-latest` or `macos-10.15`    |
diff --git a/translations/ru-RU/data/reusables/github-actions/workflow-permissions-intro.md b/translations/ru-RU/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..88382e0d54
--- /dev/null
+++ b/translations/ru-RU/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." You can choose between a restricted set of permissions as the default or a permissive setting. 
diff --git a/translations/ru-RU/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/ru-RU/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..14ee1f9279
--- /dev/null
+++ b/translations/ru-RU/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/reference/workflow-syntax-for-github-actions#permissions). 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/gpg/x-509-key.md b/translations/ru-RU/data/reusables/gpg/x-509-key.md
index 00a5c1c896..7bb93711ea 100644
--- a/translations/ru-RU/data/reusables/gpg/x-509-key.md
+++ b/translations/ru-RU/data/reusables/gpg/x-509-key.md
@@ -30,7 +30,7 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
   $ git config --local gpg.program smimesign
   ```
   If you're using an X.509 key that matches your committer identity, you can begin signing commits and tags.
-4. If you're not using an X.509 key that matches your commiter identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
+4. If you're not using an X.509 key that matches your committer identity, list X.509 keys for which you have both a certificate and private key using the `smimesign --list-keys` command.
   ```shell
   $ smimesign --list-keys
   ```
diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/verification-status-check.md b/translations/ru-RU/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..85b8a05d3c
--- /dev/null
+++ b/translations/ru-RU/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+You can check the verification status of your signed commits or tags on {% data variables.product.product_name %} and view why your commit signatures might be unverified. For more information, see "[Checking your commit and tag signature verification status](/articles/checking-your-commit-and-tag-signature-verification-status)."
diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..bb9ea14675
--- /dev/null
+++ b/translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** Vigilant mode is currently in beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..47ba1b33a5
--- /dev/null
+++ b/translations/ru-RU/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| Состояние                   | Description                                                                                                                                                                                                                                                                              |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Verified**                | The commit is signed, the signature was successfully verified, and the committer is the only author who has enabled vigilant mode.                                                                                                                                                       |
+| **Partially&nbsp;verified** | The commit is signed, and the signature was successfully verified, but the commit has an author who: a) is not the committer and b) has enabled vigilant mode. In this case, the commit signature doesn't guarantee the consent of the author, so the commit is only partially verified. |
+| **Unverified**              | Any of the following is true:<br>- The commit is signed but the signature could not be verified.<br>- The commit is not signed and the committer has enabled vigilant mode.<br>- The commit is not signed and an author has enabled vigilant mode.<br>           |
diff --git a/translations/ru-RU/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/ru-RU/data/reusables/marketplace/cancel-app-billing-settings.md
index ff68cb20f8..335490b598 100644
--- a/translations/ru-RU/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/ru-RU/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. Use the **Edit** drop-down and click **Cancel plan**. ![Cancel link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to cancel, use the **Edit** drop-down and click **Cancel plan**. ![Cancel link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ru-RU/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/ru-RU/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index 7008b67f98..b9901ac4a8 100644
--- a/translations/ru-RU/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/ru-RU/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. Under "Subscriptions", next to the free trial you'd like to cancel, use the Edit drop-down and click **Cancel plan**.
+1. Next to the free trial you'd like to cancel, use the **Edit** drop-down and click **Cancel plan**.
diff --git a/translations/ru-RU/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/ru-RU/data/reusables/marketplace/downgrade-app-billing-settings.md
index 249f85d344..10370e87c2 100644
--- a/translations/ru-RU/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/ru-RU/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Under "Your subscriptions", next to the app you'd like to downgrade, use the Edit drop-down and click **Change plan** or **Cancel plan**. ![Edit link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you'd like to downgrade, use the **Edit** drop-down and click **Change plan** or **Cancel plan**. ![Edit link in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ru-RU/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/ru-RU/data/reusables/marketplace/upgrade-app-billing-settings.md
index 630c6656ae..89945a1cf1 100644
--- a/translations/ru-RU/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/ru-RU/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. Use the **Edit** drop-down and click **Change plan**. ![Edit drop-down in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. Next to the app you want to upgrade, use the **Edit** drop-down and click **Change plan**. ![Edit drop-down in the Marketplace Purchases section of your personal account's billing settings](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md b/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..e5d59aceea
--- /dev/null
+++ b/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}issues, pulls requests, releases, security alerts, or discussions{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}issues, pull requests, releases, or discussions{% endif %}
diff --git a/translations/ru-RU/data/reusables/notifications/email-restrictions-verification.md b/translations/ru-RU/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..c30f3f4092
--- /dev/null
+++ b/translations/ru-RU/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
diff --git a/translations/ru-RU/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/ru-RU/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index 6b3de47d4c..dc6894c3f7 100644
--- a/translations/ru-RU/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/ru-RU/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-You can choose the delivery method for notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+You can choose the delivery method and frequency of notifications about
+{% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts.
+{% else %}
+You can choose the delivery method for notifications about
+{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you.
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/organizations/add-a-domain.md b/translations/ru-RU/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..a775029654
--- /dev/null
+++ b/translations/ru-RU/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. Click **Add a domain**. ![Add a domain button](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/ru-RU/data/reusables/organizations/billing_plans.md b/translations/ru-RU/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..6fc2306e57
--- /dev/null
+++ b/translations/ru-RU/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. In your organization's Settings sidebar, click **Billing & plans**. ![Billing settings](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/ru-RU/data/reusables/organizations/continue-verifying-domain.md b/translations/ru-RU/data/reusables/organizations/continue-verifying-domain.md
index 0f99787752..f5169707f9 100644
--- a/translations/ru-RU/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/ru-RU/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. To the right of the domain that's pending verification, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Continue verifying**. ![Continue verifying domain button](/assets/images/help/organizations/continue-verifying-domain.png)
-10. Click **Verify domain**. ![Verify domain button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. Click **Verify**. ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/organizations/domains-approve-domain.md b/translations/ru-RU/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/ru-RU/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/ru-RU/data/reusables/organizations/domains-approve-it-instead.md b/translations/ru-RU/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/ru-RU/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/ru-RU/data/reusables/organizations/verified-domains.md b/translations/ru-RU/data/reusables/organizations/verified-domains.md
index 534d60d588..9714304429 100644
--- a/translations/ru-RU/data/reusables/organizations/verified-domains.md
+++ b/translations/ru-RU/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. In the left sidebar, click **Verified domains**. ![Verified domains button](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/ru-RU/data/reusables/package_registry/about-packaging-and-actions.md b/translations/ru-RU/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..15bfa7d693
--- /dev/null
+++ b/translations/ru-RU/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,31 @@
+### Packaging in continuous integration workflows
+
+A packaging step is a common part of a continuous integration or continuous delivery workflow. Creating a package at the end of a continuous integration workflow can help during code reviews on a pull request.
+
+After building and testing your code, a packaging step can produce a runnable or deployable artifact. Depending on the kind of application you're building, this package can be downloaded locally for manual testing, made available for users to download, or deployed to a staging or production environment.
+
+For example, a continuous integration workflow for a Java project may run `mvn package` to produce a JAR file. Or, a CI workflow for a Node.js application may create a Docker container.
+
+Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request.
+
+### Workflows for publishing packages
+
+In addition to uploading packaging artifacts for testing in a continuous integration workflow, you can create workflows that build your project and publish packages to a package registry.
+
+* **Publish packages to {% data variables.product.prodname_registry %}**
+  {% data variables.product.prodname_registry %} can act as a package hosting service for many types of packages. You can choose to share your packages with all of {% data variables.product.prodname_dotcom %}, or private packages to share with collaborators or an organization. For more information, see "[Introduction to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages)."
+
+  You may want to publish packages to {% data variables.product.prodname_registry %} on every push into the default branch. This will allow developers on your project to always be able to run and test the latest build from the default branch easily, by installing it from {% data variables.product.prodname_registry %}.
+
+* **Publish packages to a package registry**  
+  For many projects, publishing to a package registry is performed whenever a new version of a project is released. For example, a project that produces a JAR file may upload new releases to the Maven Central repository. Or, a .NET project may produce a nuget package and upload it to the NuGet Gallery.
+
+  You can automate this by creating a workflow that publishes packages to a package registry on every release creation. For more information, see "[Creating releases](/github/administering-a-repository/creating-releases)."
diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/ru-RU/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..a02c0f89d8
--- /dev/null
+++ b/translations/ru-RU/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md b/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md
index 3bb18dfd14..5abadfbc3d 100644
--- a/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md
+++ b/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md
@@ -1,14 +1,7 @@
-You need an access token to publish, install, and delete packages. You can use a personal access token to authenticate with your username directly to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs.
+You need an access token to publish, install, and delete packages.
 
-{% if currentVersion == "free-pro-team@latest" %}
-To authenticate using a
-{% data variables.product.prodname_actions %} workflow:
-- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`.
-- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you can use a `GITHUB_TOKEN` or a personal access token. We strongly recommend you use a `GITHUB_TOKEN` to avoid unncessary access to your repositories.
+You can use a personal access token (PAT) to authenticate to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a PAT, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
 
-For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
-
-{% else %}
-To authenticate to
-{% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`.
-{% endif %}
+To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
+- `GITHUB_TOKEN` to publish packages associated with the workflow repository.
+- a PAT to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index 1581f1cf5e..46aad43e24 100644
--- a/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. Using the CLI for your container type, sign in to the
-{% data variables.product.prodname_github_container_registry %} service at `ghcr.io`.
+{% data variables.product.prodname_container_registry %} service at `ghcr.io`.
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index 666a293400..38994e051e 100644
--- a/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -2,9 +2,9 @@
 
 PATs can grant broad access to your account. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}.
 
-To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
+To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience.
 
-For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
+For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md b/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md
index 6bd738198e..2b790bdbb1 100644
--- a/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)."
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use the {% data variables.product.prodname_container_registry %}, you must enable the feature preview. For more information, see "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" and "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
 {% endnote %}
diff --git a/translations/ru-RU/data/reusables/package_registry/docker-vs-container-registry.md b/translations/ru-RU/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..60ba872bf2
--- /dev/null
+++ b/translations/ru-RU/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**Comparing the Docker registry and the {% data variables.product.prodname_container_registry %}:**
+- The {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) offers improved performance for containers and will supercede the Docker registry in the future.
+- You can migrate your Docker images and workflows from the Docker registry  (`docker.pkg.github.com`)  to the {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) for granular permissions, container storage optimization, and more. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."
+
+{% endnote %}
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md
index 73a07a040b..67608dc1e2 100644
--- a/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will offer improved container support in a future {% data variables.product.product_name %} release.{% elsif currentVersion == "free-pro-team@latest" %} now offers improved container support. For more information, see "[About GitHub Container Registry](/packages/guides/about-github-container-registry)." To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/guides/migrating-to-github-container-registry-for-docker-images)" and "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)."{% endif %}
+**Note:** The {% data variables.product.prodname_registry %} Docker registry {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} will be superseded in a future {% data variables.product.product_name %} release with the {% data variables.product.prodname_container_registry %}, which offers improved container support.{% elsif currentVersion == "free-pro-team@latest" %} is superseded by the {% data variables.product.prodname_container_registry %}, which offers improved container support. {% endif %} {% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)." {% endif %}
 
 {% endwarning %}
diff --git a/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md
index 3b74dd6c78..3b8032849e 100644
--- a/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)."
+**Note:** Before you can use the {% data variables.product.prodname_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ru-RU/data/reusables/package_registry/github-token-security-over-pat.md b/translations/ru-RU/data/reusables/package_registry/github-token-security-over-pat.md
index bee4d1039b..ca6ffe0360 100644
--- a/translations/ru-RU/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/ru-RU/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_github_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
+The {% data variables.product.prodname_container_registry %} now supports `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use `GITHUB_TOKEN`.
 
-For more information about `GITHUB_TOKEN`, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
+For more information about `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
diff --git a/translations/ru-RU/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/ru-RU/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..9bc7ee0d6e
--- /dev/null
+++ b/translations/ru-RU/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below use this type of permissions:
+- Docker registry (`docker.pkg.github.com`)
+- npm registry
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+The Container registry (`ghcr.io`) offers granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account.
+{% endif %}
+
+For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)"{% if currentVersion == "free-pro-team@latest" %} or "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."{% endif %}.
diff --git a/translations/ru-RU/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/ru-RU/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..773bfbfb5e
--- /dev/null
+++ b/translations/ru-RU/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+If you have admin permissions to a container image, you can set the access permissions for the container image to private or public. Public images allow anonymous access and can be pulled without authentication or signing in via the CLI.
+
+As an admin, you can also grant access permissions for a container image that are separate from the permissions you've set at the organization and repository levels.
+
+For container images published and owned by a user account, you can give any person an access role. For container images published and owned by an organization, you can give any person or team in the organization an access role.
+
+| Permission | Access description                                                                                                                               |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| read       | Can download package. <br> Can read package metadata.                                                                                      |
+| write      | Can upload and download this package. <br> Can read and write package metadata.                                                            |
+| admin      | Can upload, download, delete, and manage this package. <br> Can read and write package metadata. <br> Can grant package permissions. |
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/profile/access_org.md b/translations/ru-RU/data/reusables/profile/access_org.md
index 908518fb60..9356bd4ee8 100644
--- a/translations/ru-RU/data/reusables/profile/access_org.md
+++ b/translations/ru-RU/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. On the left side of your profile page, under "Organizations", click the icon for your organization. ![organization icons](/assets/images/help/profile/profile_orgs_box.png)
+1. In the top right corner of {% data variables.product.prodname_dotcom %}, click your profile photo, then click **Your organizations**. ![Your organizations in the profile menu](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/profile/org_settings.md b/translations/ru-RU/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..4c7f5b7078
--- /dev/null
+++ b/translations/ru-RU/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. Click **Settings** next to the organization. ![The settings button](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/profile/user_profile_page_block_or_report.md b/translations/ru-RU/data/reusables/profile/user_profile_page_block_or_report.md
index 65e0ff56f1..32f5c49ac1 100644
--- a/translations/ru-RU/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/ru-RU/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. In the left sidebar, under the user's profile picture, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block or report user**. ![Block or report user link](/assets/images/help/profile/profile-block-or-report-button.png)
+1. In the left sidebar, below the user's profile information, click **Block or Report**. ![Block or report link](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/ru-RU/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/ru-RU/data/reusables/repositories/actions-scheduled-workflow-example.md
index 40d253284b..3dae8f356e 100644
--- a/translations/ru-RU/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/ru-RU/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -6,6 +6,6 @@ This example triggers the workflow every day at 5:30 and 17:30 UTC:
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/ru-RU/data/reusables/repositories/request-changes-tips.md b/translations/ru-RU/data/reusables/repositories/request-changes-tips.md
index 3012e9f3c7..2a2b27a916 100644
--- a/translations/ru-RU/data/reusables/repositories/request-changes-tips.md
+++ b/translations/ru-RU/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - Repository owners and administrators can merge a pull request even if it hasn't received an approving review, or if a reviewer who requested changes has left the organization or is unavailable.
 - If both required reviews and stale review dismissal are enabled and a code-modifying commit is pushed to the branch of an approved pull request, the approval is dismissed. The pull request must be reviewed and approved again before it can be merged.
 - When several open pull requests each have a head branch pointing to the same commit, you won’t be able to merge them if one or both have a pending or rejected review.
+- Pull request authors cannot approve their own pull requests.
 
 {% endtip %}
diff --git a/translations/ru-RU/data/reusables/repositories/security-guidelines.md b/translations/ru-RU/data/reusables/repositories/security-guidelines.md
index 739a556bb3..a6cd502721 100644
--- a/translations/ru-RU/data/reusables/repositories/security-guidelines.md
+++ b/translations/ru-RU/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-You can create a security policy to give people instructions for responsibly reporting security vulnerabilities in your project. For more information, see "[Adding a security policy to your repository](/articles/adding-a-security-policy-to-your-repository)."
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+You can create a security policy to give people instructions for reporting security vulnerabilities in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
 {% endif %}
diff --git a/translations/ru-RU/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/ru-RU/data/reusables/repositories/sidebar-dependabot-alerts.md
index 58d37a45ad..2b642f5ebf 100644
--- a/translations/ru-RU/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/ru-RU/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**. ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. In the security sidebar, click **{% data variables.product.prodname_dependabot_alerts %}**.{% if currentVersion == "free-pro-team@latest" %} ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/ru-RU/data/reusables/secret-scanning/beta.md b/translations/ru-RU/data/reusables/secret-scanning/beta.md
index 714002d52b..6adcb7d57e 100644
--- a/translations/ru-RU/data/reusables/secret-scanning/beta.md
+++ b/translations/ru-RU/data/reusables/secret-scanning/beta.md
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} is in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of secret scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} was in beta in {% data variables.product.prodname_ghe_server %} 3.0. For the generally available release of {% data variables.product.prodname_secret_scanning %}, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}.
 
 
 {% endnote %}
diff --git a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index e75538fe3d..3e52aeadb6 100644
--- a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| Partner                   | Supported secret                       | API slug                                 |
-| ------------------------- | -------------------------------------- | ---------------------------------------- |
-| n/a                       | JSON Web Token                         | json_web_token                         |
-| n/a                       | OAuth Client Credential                | api_credential_assignment              |
-| Adafruit IO               | Adafruit IO Key                        | adafruit_io_key                        |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID            | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Alibaba Cloud Access Key Secret        | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID               | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Amazon AWS Secret Access Key           | aws_secret_access_key                  |
-| Asana                     | Asana Personal Access Token            | asana_personal_access_token            |
-| Atlassian                 | Atlassian API Token                    | atlassian_api_token                    |
-| Atlassian                 | Atlassian JSON Web Token               | atlassian_jwt                            |
-| Azure                     | Azure DevOps Personal Access Token     | azure_devops_personal_access_token   |
-| Azure                     | Azure SAS Token                        | azure_sas_token                        |
-| Azure                     | Azure Service Management Certificate   | azure_management_certificate           |
-| Azure                     | Azure SQL Connection String            | azure_sql_connection_string            |
-| Azure                     | Azure Storage Account Key              | azure_storage_account_key              |
-| Clojars                   | Clojars Deploy Token                   | clojars_deploy_token                   |
-| CloudBees CodeShip        | CloudBees CodeShip Credential          | codeship_credential                      |
-| Databricks                | Databricks Access Token                | databricks_access_token                |
-| Discord                   | Discord Bot Token                      | discord_bot_token                      |
-| Doppler                   | Doppler Personal Token                 | doppler_personal_token                 |
-| Doppler                   | Doppler Service Token                  | doppler_service_token                  |
-| Doppler                   | Doppler CLI Token                      | doppler_cli_token                      |
-| Doppler                   | Doppler SCIM Token                     | doppler_scim_token                     |
-| Dropbox                   | Dropbox Access Token                   | dropbox_access_token                   |
-| Dropbox                   | Dropbox Short Lived Access Token       | dropbox_short_lived_access_token     |
-| Dynatrace                 | Dynatrace Access Token                 | dynatrace_access_token                 |
-| Dynatrace                 | Dynatrace Internal Token               | dynatrace_internal_token               |
-| Facebook                  | Facebook Access Token                  | facebook_access_token                  |
-| Finicity                  | Finicity App Key                       | finicity_app_key                       |
-| Frame.io                  | Frame.io JSON Web Token                | frameio_jwt                              |
-| Frame.io                  | Frame.io Developer Token               | frameio_developer_token                |
-| GitHub                    | GitHub SSH Private Key                 | github_ssh_private_key                 |
-| GitHub                    | GitHub Personal Access Token           | github_personal_access_token           |
-| GitHub                    | GitHub App Installation Access Token   | github_app_installation_access_token |
-| GoCardless                | GoCardless Live Access Token           | gocardless_live_access_token           |
-| GoCardless                | GoCardless Sandbox Access Token        | gocardless_sandbox_access_token        |
-| Google Cloud              | Google API Key                         | google_api_key                         |
-| Google Cloud              | Google Cloud Private Key ID            | google_cloud_private_key_id          |
-| Grafana                   | Grafana API Key                        | grafana_api_key                        |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token | terraform_api_token                    |
-| Hubspot                   | Hubspot API Key                        | hubspot_api_key                        |
-| Intercom                  | Intercom Access Token                  | intercom_access_token                  |
-| Lob                       | Lob Live API Key                       | lob_live_api_key                       |
-| Lob                       | Lob Test API Key                       | lob_test_api_key                       |
-| Mailchimp                 | Mailchimp API Key                      | mailchimp_api_key                      |
-| Mailgun                   | Mailgun API Key                        | mailgun_api_key                        |
-| npm                       | npm Access Token                       | npm_access_token                       |
-| NuGet                     | NuGet API Key                          | nuget_api_key                          |
-| Palantir                  | Palantir JSON Web Token                | palantir_jwt                             |
-| Postman                   | Postman API Key                        | postman_api_key                        |
-| Proctorio                 | Proctorio Consumer Key                 | proctorio_consumer_key                 |
-| Proctorio                 | Proctorio Linkage Key                  | proctorio_linkage_key                  |
-| Proctorio                 | Proctorio Registration Key             | proctorio_registration_key             |
-| Proctorio                 | Proctorio Secret Key                   | proctorio_secret_key                   |
-| Pulumi                    | Pulumi Access Token                    | pulumi_access_token                    |
-| PyPI                      | PyPI API Token                         | pypi_api_token                         |
-| RubyGems                  | RubyGems API Key                       | rubygems_api_key                       |
-| Samsara                   | Samsara API Token                      | samsara_api_token                      |
-| Samsara                   | Samsara OAuth Access Token             | samsara_oauth_access_token             |
-| SendGrid                  | SendGrid API Key                       | sendgrid_api_key                       |
-| Shopify                   | Shopify App Shared Secret              | shopify_app_shared_secret              |
-| Shopify                   | Shopify Access Token                   | shopify_access_token                   |
-| Shopify                   | Shopify Custom App Access Token        | shopify_custom_app_access_token      |
-| Shopify                   | Shopify Private App Password           | shopify_private_app_password           |
-| Slack                     | Slack API Token                        | slack_api_token                        |
-| Slack                     | Slack Incoming Webhook URL             | slack_incoming_webhook_url             |
-| Slack                     | Slack Workflow Webhook URL             | slack_workflow_webhook_url             |
-| SSLMate                   | SSLMate API Key                        | sslmate_api_key                        |
-| SSLMate                   | SSLMate Cluster Secret                 | sslmate_cluster_secret                 |
-| Stripe                    | Stripe API Key                         | stripe_api_key                         |
-| Stripe                    | Stripe Live API Secret Key             | stripe_live_secret_key                 |
-| Stripe                    | Stripe Test API Secret Key             | stripe_test_secret_key                 |
-| Stripe                    | Stripe Live API Restricted Key         | stripe_live_restricted_key             |
-| Stripe                    | Stripe Test API Restricted Key         | stripe_test_restricted_key             |
-| Tencent Cloud             | Tencent Cloud Secret ID                | tencent_cloud_secret_id                |
-| Twilio                    | Twilio Account String Identifier       | twilio_account_sid                     |
-| Twilio                    | Twilio API Key                         | twilio_api_key                         |
+| Partner | Supported secret | API slug |
+| ------- | ---------------- | -------- |
+|         |                  |          |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index ebc268a20d..701b6505b7 100644
--- a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| Partner                   | Supported secret                                                            |
-| ------------------------- | --------------------------------------------------------------------------- |
-| Adafruit IO               | Adafruit IO Key                                                             |
-| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair                      |
-| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair                         |
-| Atlassian                 | Atlassian API Token                                                         |
-| Atlassian                 | Atlassian JSON Web Token                                                    |
-| Azure                     | Azure DevOps Personal Access Token | azure_devops_personal_access_token |
-| Azure                     | Azure SAS Token | azure_sas_token                                         |
-| Azure                     | Azure Service Management Certificate | azure_management_certificate       |
-| Azure                     | Azure SQL Connection String | azure_sql_connection_string                 |
-| Azure                     | Azure Storage Account Key | azure_storage_account_key                     |
-| Clojars                   | Clojars Deploy Token                                                        |
-| CloudBees CodeShip        | CloudBees CodeShip Credential                                               |
-| Databricks                | Databricks Access Token                                                     |
-| Datadog                   | Datadog API Key                                                             |
-| Discord                   | Discord Bot Token                                                           |
-| Doppler                   | Doppler Personal Token                                                      |
-| Doppler                   | Doppler Service Token                                                       |
-| Doppler                   | Doppler CLI Token                                                           |
-| Doppler                   | Doppler SCIM Token                                                          |
-| Dropbox                   | Dropbox Access Token                                                        |
-| Dropbox                   | Dropbox Short Lived Access Token                                            |
-| Dynatrace                 | Dynatrace Access Token                                                      |
-| Dynatrace                 | Dynatrace Internal Token                                                    |
-| Finicity                  | Finicity App Key                                                            |
-| Frame.io                  | Frame.io JSON Web Token                                                     |
-| Frame.io                  | Frame.io Developer Token                                                    |
-| GitHub                    | GitHub SSH Private Key                                                      |
-| GitHub                    | GitHub Personal Access Token                                                |
-| GitHub                    | GitHub App Installation Access Token                                        |
-| GoCardless                | GoCardless Live Access Token                                                |
-| GoCardless                | GoCardless Sandbox Access Token                                             |
-| Google Cloud              | Google API Key                                                              |
-| Google Cloud              | Google Cloud Private Key ID                                                 |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                                      |
-| Hubspot                   | Hubspot API Key                                                             |
-| Mailchimp                 | Mailchimp API Key                                                           |
-| Mailchimp                 | Mandrill API Key                                                            |
-| Mailgun                   | Mailgun API Key                                                             |
-| MessageBird               | MessageBird API Key                                                         |
-| npm                       | npm Access Token                                                            |
-| NuGet                     | NuGet API Key                                                               |
-| Palantir                  | Palantir JSON Web Token                                                     |
-| Plivo                     | Plivo Auth Token                                                            |
-| Postman                   | Postman API Key                                                             |
-| Proctorio                 | Proctorio Consumer Key                                                      |
-| Proctorio                 | Proctorio Linkage Key                                                       |
-| Proctorio                 | Proctorio Registration Key                                                  |
-| Proctorio                 | Proctorio Secret Key                                                        |
-| Pulumi                    | Pulumi Access Token                                                         |
-| PyPI                      | PyPI API Token                                                              |
-| RubyGems                  | RubyGems API Key                                                            |
-| Samsara                   | Samsara API Token                                                           |
-| Samsara                   | Samsara OAuth Access Token                                                  |
-| Shopify                   | Shopify App Shared Secret                                                   |
-| Shopify                   | Shopify Access Token                                                        |
-| Shopify                   | Shopify Custom App Access Token                                             |
-| Shopify                   | Shopify Private App Password                                                |
-| Slack                     | Slack API Token                                                             |
-| Slack                     | Slack Incoming Webhook URL                                                  |
-| Slack                     | Slack Workflow Webhook URL                                                  |
-| SSLMate                   | SSLMate API Key                                                             |
-| SSLMate                   | SSLMate Cluster Secret                                                      |
-| Stripe                    | Stripe Live API Secret Key                                                  |
-| Stripe                    | Stripe Test API Secret Key                                                  |
-| Stripe                    | Stripe Live API Restricted Key                                              |
-| Stripe                    | Stripe Test API Restricted Key                                              |
-| Tencent Cloud             | Tencent Cloud Secret ID                                                     |
-| Twilio                    | Twilio Account String Identifier                                            |
-| Twilio                    | Twilio API Key                                                              |
+| Partner                   | Supported secret                                       |
+| ------------------------- | ------------------------------------------------------ |
+| Adafruit IO               | Adafruit IO Key                                        |
+| Adobe                     | Adobe Device Token                                     |
+| Adobe                     | Adobe Service Token                                    |
+| Adobe                     | Adobe Short-Lived Access Token                         |
+| Adobe                     | Adobe JSON Web Token                                   |
+| Alibaba Cloud             | Alibaba Cloud Access Key ID and Access Key Secret pair |
+| Amazon Web Services (AWS) | Amazon AWS Access Key ID and Secret Access Key pair    |
+| Atlassian                 | Atlassian API Token                                    |
+| Atlassian                 | Atlassian JSON Web Token                               |
+| Azure                     | Azure DevOps Personal Access Token                     |
+| Azure                     | Azure SAS Token                                        |
+| Azure                     | Azure Service Management Certificate                   |
+| Azure                     | Azure SQL Connection String                            |
+| Azure                     | Azure Storage Account Key                              |
+| Clojars                   | Clojars Deploy Token                                   |
+| CloudBees CodeShip        | CloudBees CodeShip Credential                          |
+| Databricks                | Databricks Access Token                                |
+| Datadog                   | Datadog API Key                                        |
+| Discord                   | Discord Bot Token                                      |
+| Doppler                   | Doppler Personal Token                                 |
+| Doppler                   | Doppler Service Token                                  |
+| Doppler                   | Doppler CLI Token                                      |
+| Doppler                   | Doppler SCIM Token                                     |
+| Dropbox                   | Dropbox Access Token                                   |
+| Dropbox                   | Dropbox Short Lived Access Token                       |
+| Dynatrace                 | Dynatrace Access Token                                 |
+| Dynatrace                 | Dynatrace Internal Token                               |
+| Finicity                  | Finicity App Key                                       |
+| Frame.io                  | Frame.io JSON Web Token                                |
+| Frame.io                  | Frame.io Developer Token                               |
+| GitHub                    | GitHub Personal Access Token                           |
+| GitHub                    | GitHub OAuth Access Token                              |
+| GitHub                    | GitHub Refresh Token                                   |
+| GitHub                    | GitHub App Installation Access Token                   |
+| GitHub                    | GitHub SSH Private Key                                 |
+| GoCardless                | GoCardless Live Access Token                           |
+| GoCardless                | GoCardless Sandbox Access Token                        |
+| Google Cloud              | Google API Key                                         |
+| Google Cloud              | Google Cloud Private Key ID                            |
+| Hashicorp Terraform       | Terraform Cloud / Enterprise API Token                 |
+| Hubspot                   | Hubspot API Key                                        |
+| Mailchimp                 | Mailchimp API Key                                      |
+| Mailchimp                 | Mandrill API Key                                       |
+| Mailgun                   | Mailgun API Key                                        |
+| MessageBird               | MessageBird API Key                                    |
+| npm                       | npm Access Token                                       |
+| NuGet                     | NuGet API Key                                          |
+| OpenAI                    | OpenAI API Key                                         |
+| Palantir                  | Palantir JSON Web Token                                |
+| Plivo                     | Plivo Auth Token                                       |
+| Postman                   | Postman API Key                                        |
+| Proctorio                 | Proctorio Consumer Key                                 |
+| Proctorio                 | Proctorio Linkage Key                                  |
+| Proctorio                 | Proctorio Registration Key                             |
+| Proctorio                 | Proctorio Secret Key                                   |
+| Pulumi                    | Pulumi Access Token                                    |
+| PyPI                      | PyPI API Token                                         |
+| RubyGems                  | RubyGems API Key                                       |
+| Samsara                   | Samsara API Token                                      |
+| Samsara                   | Samsara OAuth Access Token                             |
+| SendGrid                  | SendGrid API Key                                       |
+| Shopify                   | Shopify App Shared Secret                              |
+| Shopify                   | Shopify Access Token                                   |
+| Shopify                   | Shopify Custom App Access Token                        |
+| Shopify                   | Shopify Private App Password                           |
+| Slack                     | Slack API Token                                        |
+| Slack                     | Slack Incoming Webhook URL                             |
+| Slack                     | Slack Workflow Webhook URL                             |
+| SSLMate                   | SSLMate API Key                                        |
+| SSLMate                   | SSLMate Cluster Secret                                 |
+| Stripe                    | Stripe Live API Secret Key                             |
+| Stripe                    | Stripe Test API Secret Key                             |
+| Stripe                    | Stripe Live API Restricted Key                         |
+| Stripe                    | Stripe Test API Restricted Key                         |
+| Tencent Cloud             | Tencent Cloud Secret ID                                |
+| Twilio                    | Twilio Account String Identifier                       |
+| Twilio                    | Twilio API Key                                         |
diff --git a/translations/ru-RU/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/ru-RU/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..ecb8f968d6
--- /dev/null
+++ b/translations/ru-RU/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,5 @@
+{% if currentVersion == "free-pro-team@latest" %}
+For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."
+{% else %}
+For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."
+{% endif %}
diff --git a/translations/ru-RU/data/reusables/security/displayed-information.md b/translations/ru-RU/data/reusables/security/displayed-information.md
index 02f38c36db..744735db2d 100644
--- a/translations/ru-RU/data/reusables/security/displayed-information.md
+++ b/translations/ru-RU/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
 When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
 
 - All the existing repositories will have the selected configuration.
-- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% if currentVersion == "free-pro-team@latest" %}
 - We use the permissions to scan for manifest files to apply the relevant services.
 - You'll see information on your dependency graph.
-- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} and raise pull requests{% endif %}. 
+- {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} and create pull requests{% endif %}. 
diff --git a/translations/ru-RU/data/reusables/supported-languages/C.md b/translations/ru-RU/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/Cpp.md b/translations/ru-RU/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/Cs.md b/translations/ru-RU/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/go.md b/translations/ru-RU/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..40bd61946e
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/java.md b/translations/ru-RU/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/javascript.md b/translations/ru-RU/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/php.md b/translations/ru-RU/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/products-table-header.md b/translations/ru-RU/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..743339ee69
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/python.md b/translations/ru-RU/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/ruby.md b/translations/ru-RU/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/scala.md b/translations/ru-RU/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/supported-languages/typescript.md b/translations/ru-RU/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/ru-RU/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/ru-RU/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/ru-RU/data/reusables/user_settings/keeping_your_email_address_private.md
index cabc7cc611..1359461643 100644
--- a/translations/ru-RU/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/ru-RU/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. To keep your email address private when performing web-based Git operations, click **Keep my email address private**. ![Image of checkbox to keep your email address private](/assets/images/help/settings/email_privacy.png)
+5. To keep your email address private when performing web-based Git operations, click **Keep my email addresses private**. ![Image of checkbox to keep your email address private](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/ru-RU/data/reusables/user_settings/payment-info-link.md b/translations/ru-RU/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..8d441f3be4
--- /dev/null
+++ b/translations/ru-RU/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. At the top of the page, click **Payment information**. ![Payment information link](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/ru-RU/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/ru-RU/data/reusables/webhooks/code_scanning_alert_event_properties.md
index ecf20164ba..7646a0f473 100644
--- a/translations/ru-RU/data/reusables/webhooks/code_scanning_alert_event_properties.md
+++ b/translations/ru-RU/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -1,6 +1,6 @@
-| Клавиша      | Тип      | Description                                                                                                                                                                     |
-| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `действие`   | `строка` | The action that was performed. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                                |
-| `оповещение` | `объект` | The code scanning alert involved in the event.                                                                                                                                  |
-| `ref`        | `строка` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty. |
-| `commit_oid` | `строка` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`,  the event was triggered by the `sender` and this value will be empty.    |
+| Клавиша      | Тип      | Description                                                                                                                                                                    |
+| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `действие`   | `строка` | The action that was performed. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`.                               |
+| `оповещение` | `объект` | The code scanning alert involved in the event.                                                                                                                                 |
+| `ref`        | `строка` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty. |
+| `commit_oid` | `строка` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty.    |
diff --git a/translations/ru-RU/data/reusables/webhooks/create_properties.md b/translations/ru-RU/data/reusables/webhooks/create_properties.md
index f9a2ccdb87..d9e7d18c7e 100644
--- a/translations/ru-RU/data/reusables/webhooks/create_properties.md
+++ b/translations/ru-RU/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| Клавиша         | Тип      | Description                                                                                                                                                                                                                           |
-| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `строка` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                        |
-| `ref_type`      | `строка` | The type of Git ref object created in the repository. Can be either `branch` or `tag`.                                                                                                                                                |
-| `master_branch` | `строка` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
-| `описание`      | `строка` | The repository's current description.                                                                                                                                                                                                 |
+| Клавиша         | Тип      | Description                                                                                                                                                                                                                          |
+| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ref`           | `строка` | The [`git ref`](/rest/reference/git#get-a-reference) resource.                                                                                                                                                                       |
+| `ref_type`      | `строка` | The type of Git ref object created in the repository. Can be either `branch` or `tag`.                                                                                                                                               |
+| `master_branch` | `строка` | The name of the repository's default branch (usually {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}). |
+| `описание`      | `строка` | The repository's current description.                                                                                                                                                                                                |
diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md
index 0abc07b65e..4176e9b7c9 100644
--- a/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| Клавиша    | Тип      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `действие` | `строка` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. |
+| Клавиша    | Тип      | Description                                                            |
+| ---------- | -------- | ---------------------------------------------------------------------- |
+| `действие` | `строка` | The action that was performed. Can be one of:<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's tracking branch is synchronized with the source branch for the pull request, which happens when the source branch is updated.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/ru-RU/data/reusables/webhooks/sponsorship_short_desc.md b/translations/ru-RU/data/reusables/webhooks/sponsorship_short_desc.md
index 2f62ffe8d8..bf99f9f71a 100644
--- a/translations/ru-RU/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/ru-RU/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)".
+Activity related to a sponsorship listing. {% data reusables.webhooks.action_type_desc %} For more information, see "[About GitHub Sponsors](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml
index 26ebe77588..3f1caaa448 100644
--- a/translations/ru-RU/data/ui.yml
+++ b/translations/ru-RU/data/ui.yml
@@ -20,7 +20,7 @@ homepage:
   version_picker: Версия
 toc:
   getting_started: Getting started
-  popular_articles: Popular
+  popular: Popular
   guides: Руководства
   whats_new: What's new
 pages:
@@ -54,14 +54,6 @@ contribution_cta:
   button: Make a contribution
   or: Or,
   to_guidelines: learn how to contribute.
-enterprise_releases_list:
-  title: Enterprise Server Releases
-  currently_supported: Currently supported
-  currently_supported_message: See <a href="https://github.com/enterprise">GitHub Enterprise</a> for information about the latest release.
-  deprecated: Deprecated
-  deprecated_message: 'These docs remain available but are no longer maintained:'
-  deprecated_developer: Deprecated on developer.github.com
-  deprecated_developer_message: 'These docs remain available on the legacy <a href="https://developer.github.com">developer site</a> but are no longer maintained:'
 products:
   graphql:
     reference:
@@ -127,19 +119,36 @@ footer:
       press: Press
       shop: Shop
 product_landing:
-  quick_start: Quickstart
-  reference_guides: Reference guides
+  quickstart: Quickstart
+  reference: Reference
   overview: Обзор
+  guides: Руководства
+  code_examples: Code examples
+  search_code_examples: Search code examples
+  show_more: Show more
+  explore_people_and_projects: Explore people and projects
+  sorry: Sorry, there is no result for
+  no_example: It looks like we don't have an example that fits your filter.
+  try_another: Try another filter or add your code example.
+  no_result: Sorry, there is no guide that match your filter.
+  learn: Learn how to add a code example
+  communities_using_discussions: Communities using discussions
+  add_your_community: Add your community
+  sponsor_community: GitHub Sponsors community
+  supported_releases: Supported releases
+  release_notes_for: Release notes for
+  upgrade_from: Upgrade from
+  browse_all_docs: Browse all docs
+  explore_release_notes: Explore release notes
 product_sublanding:
   start: Start
   start_path: Start path
-  learning_paths: '{{ allProducts[currentProduct].name }} learning paths'
+  learning_paths: '{{ productMap[currentProduct].name }} learning paths'
   learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject.
-  guides: '{{ allProducts[currentProduct].name }} guides'
+  guides: '{{ productMap[currentProduct].name }} guides'
   more_guides: more guides
   load_more: Load more guides
-  all_guides: 'All {{ allProducts[currentProduct].name }} guides'
-  no_result: Sorry, there is no guide that match your filter.
+  all_guides: 'All {{ productMap[currentProduct].name }} guides'
   filters:
     type: Тип
     topic: Topic
@@ -154,3 +163,10 @@ learning_track_nav:
   prevGuide: Previous guide
   nextGuide: Next guide
 contributor_callout: This article is contributed and maintained by
+toggle_images:
+  off: Images are off, click to show
+  on: Images are on, click to hide
+  hide_single: Hide image
+  show_single: Show image
+scroll_button:
+  scroll_to_top: Scroll to top
diff --git a/translations/ru-RU/data/variables/codespaces_code_examples.yml b/translations/ru-RU/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..00958245ab
--- /dev/null
+++ b/translations/ru-RU/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.js sample project
+  description: Try a Node.js project with a custom dev container
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - development containers
+- 
+  title: Python sample project
+  description: Try a Python project with a custom dev container
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - development containers
+- 
+  title: Java sample project
+  description: Try a Java project with a custom dev container
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - development containers
+- 
+  title: Go sample project
+  description: Try a Go project with a custom dev container
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - development containers
+- 
+  title: Rust sample project
+  description: Try a Rust project with a custom dev container
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - development containers
+- 
+  title: PHP sample project
+  description: Try a PHP project with a custom dev container
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - development containers
diff --git a/translations/ru-RU/data/variables/migrations.yml b/translations/ru-RU/data/variables/migrations.yml
index 15201e4a03..61cd8c80be 100644
--- a/translations/ru-RU/data/variables/migrations.yml
+++ b/translations/ru-RU/data/variables/migrations.yml
@@ -4,4 +4,4 @@ user_migrations_intro: >-
 organization_migrations_intro: >-
   The organization migrations API lets you move a repository from GitHub to {% data variables.product.prodname_ghe_server %}.
 source_imports_intro: >-
-  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Server source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
+  The Source Import API lets you start an import from a Git, Subversion, Mercurial, or Team Foundation Version Control source repository. This is the same functionality as the {% data variables.product.prodname_dotcom %} Importer. For more information, see "[Importing a repository with {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)."
diff --git a/translations/ru-RU/data/variables/product.yml b/translations/ru-RU/data/variables/product.yml
index 181f1bc718..5c0bc3a4f0 100644
--- a/translations/ru-RU/data/variables/product.yml
+++ b/translations/ru-RU/data/variables/product.yml
@@ -56,6 +56,7 @@ prodname_pages: 'Страницы GitHub'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'Магазин GitHub'
 prodname_github_app: 'Приложение GitHub'
@@ -77,8 +78,7 @@ prodname_debug: 'GitHub Debug'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
-prodname_github_container_registry: 'GitHub Container Registry'
-prodname_container_registry: 'container registry'
+prodname_container_registry: 'Container registry'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -91,7 +91,6 @@ prodname_advanced_security: 'Advanced Security'
 prodname_security_center: 'Security Center'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Visual Studio Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'GitHub Community Support'
diff --git a/translations/ru-RU/data/variables/release_candidate.yml b/translations/ru-RU/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/ru-RU/data/variables/release_candidate.yml
+++ b/translations/ru-RU/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/ru-RU/data/variables/sponsors_user_examples.yml b/translations/ru-RU/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..92800edaf3
--- /dev/null
+++ b/translations/ru-RU/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chayn helps women experiencing abuse find the right information and support they need to take control of their lives.
+- 
+  user: foosel
+  description: '👋 I''m Gina, and I''m mostly known for being the creator and main developer of OctoPrint 🐙.'
+- 
+  user: dayhaysoos
+  description: What's up? I'm Nick. I'm an engineer who has a new-found passion for removing friction from the e-commerce developer experience.
+- 
+  user: yyx990803
+  description: I'm working fulltime on Vue.js, a frontend JavaScript framework for building web applications, and Vite, a modern web build tool.
+- 
+  user: calebporzio
+  description: '🚶‍♂️I left my day job in Jan 2019 to pursue open-source. Since then, I''ve built Laravel Livewire, AlpineJS, and a bunch of other stuff.'
+- 
+  user: kjaymiller
+  description: Hi Y'all I'm Jay! 👋 I'm a Marine Corps Veteran turned developer that's been actively coding since 2014. I'm also involved in the productivity space where I can be found helping people with automations for some of their favorite apps and tools.
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md
index fde4bd5b99..ef7fd0ef2b 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-run-steps-action.md
@@ -121,13 +121,13 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - uses: actions/checkout@v2
-    - id: foo
-      uses: actions/hello-world-composite-run-steps-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    - run: echo random-number ${{ steps.foo.outputs.random-number }}
-      shell: bash
+      - uses: actions/checkout@v2
+      - id: foo
+        uses: actions/hello-world-composite-run-steps-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number ${{ steps.foo.outputs.random-number }}
+        shell: bash
 ```
 {% endraw %}
 
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 eedaae7bbb..071f6c34ee 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
@@ -195,14 +195,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-docker-action@v1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
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 9f18df5eff..bfdc8261d6 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
@@ -222,14 +222,14 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-    - name: Hello world action step
-      id: hello
-      uses: actions/hello-world-javascript-action@v1.1
-      with:
-        who-to-greet: 'Mona the Octocat'
-    # Use the output from the `hello` step
-    - name: Get the output time
-      run: echo "The time was ${{ steps.hello.outputs.time }}"
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
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 dadb064a08..e945ffec53 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
@@ -201,7 +201,7 @@ runs:
 
 ```yaml
   pre: 'cleanup.js'
-  pre-if: 'runner.os == linux'
+  pre-if: runner.os == 'linux'
 ```
 
 
@@ -237,7 +237,7 @@ runs:
 
 ```yaml
   post: 'cleanup.js'
-  post-if: 'runner.os == linux'
+  post-if: runner.os == 'linux'
 ```
 
 
@@ -379,7 +379,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   pre-entrypoint: 'setup.sh'
   entrypoint: 'main.sh'
 ```
@@ -418,7 +418,7 @@ runs:
   using: 'docker'
   image: 'Dockerfile'
   args:
-  - 'bzz'
+    - 'bzz'
   entrypoint: 'main.sh'
   post-entrypoint: 'cleanup.sh'
 ```
diff --git a/translations/zh-CN/content/actions/guides/about-continuous-integration.md b/translations/zh-CN/content/actions/guides/about-continuous-integration.md
index b12314976a..19d1e84e17 100644
--- a/translations/zh-CN/content/actions/guides/about-continuous-integration.md
+++ b/translations/zh-CN/content/actions/guides/about-continuous-integration.md
@@ -48,11 +48,13 @@ topics:
 有关常用术语的定义，请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。
 
 ### 支持的语言
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 {% data variables.product.product_name %} 提供各种不同语言和框架的 CI 工作流程模板。
 
 在 {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) 仓库{% else %}{% data variables.product.product_location %} 上的 `actions/starter-workflows` 仓库{% endif %}中浏览 {% data variables.product.product_name %} 提供的 CI 工作流程模板的完整列表。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### 跳过工作流程运行
 
 如果您想暂时阻止触发工作流程，可以对提交消息添加跳过指令。 本来会触发 `on: push` 或 `on: pull_request` 的工作流程，如果您将以下任何字符串添加到推送中的提交消息或者拉取请求的 HEAD 提交，则不会触发：
@@ -72,6 +74,7 @@ topics:
 **注意：**跳过指令仅适用于 `push` 和 `pull_request` 事件。 例如，将 `[skip ci]` 添加到提交消息不会停止触发 `on: pull_request_target` 的工作流程运行。
 
 {% endnote %}
+{% endif %}
 
 ### 工作流程运行通知
 
diff --git a/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md b/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md
index e1f4b70431..9b6b8b3d55 100644
--- a/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md
+++ b/translations/zh-CN/content/actions/guides/about-packaging-with-github-actions.md
@@ -18,38 +18,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-### 关于打包步骤
-
-打包步骤是持续集成或持续交付工作流程的常见部分。 构建并测试应用程序后，将以包的形式生成可运行或可部署的构件。 例如，Java 项目的连续集成工作流程可能运行 `mvn package` 来生成 JAR 文件。 或者，Node.js 应用程序的 CI 工作流程可能会创建 Docker 容器。
-
-根据您构建的应用程序类型，此包可本地下载以进行手动测试、可供用户下载或部署到暂存或生产环境。
-
-### 持续集成工作流程中的打包
-
-在持续集成工作流程结束时创建包有助于拉取请求的代码审查。 构建并测试代码后，打包步骤可以生成可运行或可部署的构件。 然后，您的工作流程可提取该构件并将其上传为工作流程的一部分。
-
-现在，在审查拉取请求时，您将能够查看工作流程运行并下载生成的构件。
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
-![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down-updated.png)
-{% else %}
-![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png)
-{% endif %}
-
-这将允许您在计算机上运行拉取请求中的代码，有助于调试或测试拉取请求。
-
-### 发布包的工作流程
-
-除了上传打包构件以测试持续集成工作流程之外， 您还可以创建工作流程来构建项目并发布包到软件包注册表。
-
-* **发布软件包到 {% data variables.product.prodname_registry %}**
-  {% data variables.product.prodname_registry %} 可以作为多种类型包的包托管服务。 您可以选择与所有 {% data variables.product.prodname_dotcom %} 共享您的软件包，或者与合作者或组织共享私有软件包。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/about-github-packages)”。
-
-  每次推送到默认分支，您可能想将软件包发布到 {% data variables.product.prodname_registry %}。 这可让项目开发者始终能够通过从 {% data variables.product.prodname_registry %} 安装，很容易地运行和测试主版本中的最新构建版本。
-
-* **将软件包发布到软件包注册表** 对于许多项目，每当发布项目的新版本时，都会执行发布到软件包注册表。 例如，生成 JAR 文件的项目可能会将新版本上传到 Maven Central 仓库。 或者，.NET 项目可能会生成一个微件包并上传到 Nuget Gallery。
-
-  您可以创建一个工作流程来自动执行此操作，在每次创建版本时将软件包发布到软件包注册表。 更多信息请参阅“[创建发行版](/github/administering-a-repository/creating-releases)”。
+{% data reusables.package_registry.about-packaging-and-actions %}
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md b/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md
index 4e8cc84086..b9a2a14250 100644
--- a/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md
+++ b/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md
@@ -29,7 +29,6 @@ topics:
 2. {% data reusables.actions.make-workflow-file %}
 3. 将以下 YAML 内容复制到工作流程文件中。
 
-    {% raw %}
     ```yaml{:copy}
     name: Label issues
     on:
@@ -39,14 +38,17 @@ topics:
           - opened
     jobs:
       label_issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Label issues
             uses: andymckay/labeler@1.0.2
             with:
               add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. 自定义工工作流程文件中的参数：
    - 将 `add-labels` 的值更改为您想要添加到此议题的标签列表。 使用逗号分隔多个标签。 例如 `"help wanted, good first issue"`。 有关标签的更多信息，请参阅“[管理标签](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)”。
 5. {% data reusables.actions.commit-workflow %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md
index a58aee91aa..899df67e37 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-ant.md
@@ -23,7 +23,7 @@ topics:
 
 本指南介绍如何使用 Ant 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以从工作流程运行上传构件。
 
-{% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}
 {% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件，包括 Java Development Kits (JDKs) 和 Ant。 有关软件以及 JDK 和 Ant 预安装版本的列表，请参阅 [{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)。
 {% endif %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md
index f018dc6a00..fd242b176a 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md
@@ -23,7 +23,7 @@ topics:
 
 本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以缓存文件并且从工作流程运行上传构件。
 
-{% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}
 {% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件，包括 Java Development Kits (JDKs) 和 Gradle。 有关软件以及 JDK 和 Gradle 预安装版本的列表，请参阅 [{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)。
 {% endif %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md
index 32c91afd41..7e9c81b54f 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md
@@ -23,7 +23,7 @@ topics:
 
 本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以缓存文件并且从工作流程运行上传构件。
 
-{% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}
 {% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件，包括 Java Development Kits (JDKs) 和 Maven。 有关软件以及 JDK 和 Maven 预安装版本的列表，请参阅 [{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)。
 {% endif %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-net.md b/translations/zh-CN/content/actions/guides/building-and-testing-net.md
index 964e2201ed..84b1d61213 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-net.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-net.md
@@ -16,7 +16,7 @@ versions:
 
 本指南介绍如何构建、测试和发布 .NET 包。
 
-{% if currentversion == "github-ae@latest" %} 要构建和测试您在 {% data variables.product.prodname_ghe_managed %} 上的 .NET 项目，则需要创建包含 .NET Core SDK 的自定义操作系统映像。 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %} 要构建和测试您在 {% data variables.product.prodname_ghe_managed %} 上的 .NET 项目，则需要创建包含 .NET Core SDK 的自定义操作系统映像。 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %} {% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件，包括 .NET Core SDK。 有关最新版软件以及 .NET Core SDK 预安装版本的完整列表，请参阅 [{% data variables.product.prodname_dotcom %} 自托管运行器上安装的软件](/actions/reference/specifications-for-github-hosted-runners)。
 {% endif %}
 
@@ -47,17 +47,17 @@ jobs:
         dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    - name: Install dependencies
-      run: dotnet restore
-    - name: Build
-      run: dotnet build --configuration Release --no-restore
-    - name: Test
-      run: dotnet test --no-restore --verbosity normal
+      - uses: actions/checkout@v2
+      - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1.7.2
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
 ```
 {% endraw %}
 
@@ -84,14 +84,14 @@ jobs:
         dotnet: [ '3.0', '3.1.x', '5.0.x' ]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup dotnet ${{ matrix.dotnet-version }}
-      uses: actions/setup-dotnet@v1.7.2
-      with:
-        dotnet-version: ${{ matrix.dotnet-version }}
-    # You can test your matrix by printing the current dotnet version
-    - name: Display dotnet version
-      run: dotnet --version
+      - uses: actions/checkout@v2
+      - name: Setup dotnet ${{ matrix.dotnet-version }}
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: ${{ matrix.dotnet-version }}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
 ```
 {% endraw %}
 
@@ -102,7 +102,7 @@ jobs:
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
-      uses: actions/setup-dotnet@v2
+      uses: actions/setup-dotnet@v1
       with:
         # Semantic version range syntax or exact version of a dotnet version
         dotnet-version: '3.x' 
@@ -118,7 +118,7 @@ jobs:
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -139,7 +139,7 @@ steps:
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - uses: actions/cache@v2
@@ -171,7 +171,7 @@ steps:
 steps:
 - uses: actions/checkout@v2
 - name: Setup dotnet
-  uses: actions/setup-dotnet@v1.7.2
+  uses: actions/setup-dotnet@v1
   with:
     dotnet-version: '3.1.x'
 - name: Install dependencies
@@ -204,22 +204,22 @@ jobs:
         dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
 
       steps:
-      - uses: actions/checkout@v2
-      - name: Setup dotnet
-        uses: actions/setup-dotnet@v1.7.2
-        with:
-          dotnet-version: ${{ matrix.dotnet-version }}
-      - name: Install dependencies
-        run: dotnet restore
-      - name: Test with dotnet
-        run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
-      - name: Upload dotnet test results
-        uses: actions/upload-artifact@v2
-        with:
-          name: dotnet-results-${{ matrix.dotnet-version }}
-          path: TestResults-${{ matrix.dotnet-version }}
-        # Use always() to always run this step to publish test results when there are test failures
-        if: ${{ always() }}
+        - uses: actions/checkout@v2
+        - name: Setup dotnet
+          uses: actions/setup-dotnet@v1
+          with:
+            dotnet-version: ${{ matrix.dotnet-version }}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory "TestResults-${{ matrix.dotnet-version }}"
+        - name: Upload dotnet test results
+          uses: actions/upload-artifact@v2
+          with:
+            name: dotnet-results-${{ matrix.dotnet-version }}
+            path: TestResults-${{ matrix.dotnet-version }}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: ${{ always() }}
 ```
 {% endraw %}
 
@@ -227,7 +227,6 @@ jobs:
 
 您可以配置工作流程在 CI 测试通过后将 Dotnet 包发布到包注册表。 您可以使用仓库机密来存储发布二进制文件所需的任何令牌或凭据。 下面的示例使用 `dotnet core cli`创建并发布软件包到 {% data variables.product.prodname_registry %}。
 
-{% raw %}
 ```yaml
 name: Upload dotnet package
 
@@ -237,19 +236,21 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-dotnet@v1
-    with:
-        dotnet-version: '3.1.x' # SDK Version to use.
-        source-url: https://nuget.pkg.github.com/<owner>/index.json
-    env:
-        NUGET_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
-    - run: dotnet build --configuration Release <my project>
-    - name: Create the package
-    run: dotnet pack --configuration Release <my project>
-    - name: Publish the package to GPR
-    run: dotnet nuget push <my project>/bin/Release/*.nupkg
+      - uses: actions/checkout@v2
+      - uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
 ```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md
index 1aa2fb5168..c0bb4d1d07 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md
@@ -37,7 +37,7 @@ topics:
 
 {% data variables.product.prodname_dotcom %} 提供 Node.js 适用于大多数 Node.js 项目的工作流程模板。 本指南包含可用于自定义模板的 npm 和 Yarn 示例。 更多信息请参阅 [Node.js 工作流程模板](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml)。
 
-要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。
+要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。 下面显示的工作流假定仓库的默认分支是 `main`。
 
 {% raw %}
 ```yaml{:copy}
@@ -45,9 +45,9 @@ name: Node.js CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
@@ -59,14 +59,14 @@ jobs:
         node-version: [10.x, 12.x, 14.x, 15.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: ${{ matrix.node-version }}
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 
@@ -119,20 +119,20 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Use Node.js
-      uses: actions/setup-node@v1
-      with:
-        node-version: '12.x'
-    - run: npm ci
-    - run: npm run build --if-present
-    - run: npm test
+      - uses: actions/checkout@v2
+      - name: Use Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
 ```
 {% endraw %}
 如果您没有指定 Node.js 版本，
 
 {% data variables.product.prodname_dotcom %} 使用环境的默认 Node.js 版本。
-{% if currentversion == "github-ae@latest" %} 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %} 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
 {% endif %}
 
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md b/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md
index b5ed0d049a..836c1009b1 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-powershell.md
@@ -24,7 +24,7 @@ topics:
 
 {% data variables.product.prodname_dotcom %} 托管的运行器具有预安装了软件的工具缓存，包括 PowerShell 和 Pester。
 
-{% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}有关最新版软件以及 PowerShell 和 Pester 预安装版本的完整列表，请参阅 [{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)。
 {% endif %}
 
@@ -54,15 +54,15 @@ jobs:
     name: Pester test
     runs-on: ubuntu-latest
     steps:
-    - name: Check out repository code
-      uses: actions/checkout@v2
-    - name: Perform a Pester test from the command-line
-      shell: pwsh
-      run: Test-Path resultsfile.log | Should -Be $true
-    - name: Perform a Pester test from the Tests.ps1 file
-      shell: pwsh
-      run: |
-        Invoke-Pester Unit.Tests.ps1 -Passthru
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
 ```
 {% endraw %}
 
@@ -116,12 +116,12 @@ jobs:
     name: Install dependencies
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install from PSGallery
-      shell: pwsh
-      run: |
-        Set-PSRepository PSGallery -InstallationPolicy Trusted
-        Install-Module SqlServer, PSScriptAnalyzer
+      - uses: actions/checkout@v2
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
 ```
 {% endraw %}
 
@@ -170,23 +170,23 @@ steps:
     name: Install and run PSScriptAnalyzer
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Install PSScriptAnalyzer module
-      shell: pwsh
-      run: |
-            Set-PSRepository PSGallery -InstallationPolicy Trusted
-            Install-Module PSScriptAnalyzer -ErrorAction Stop
-    - name: Lint with PSScriptAnalyzer
-      shell: pwsh
-      run: |
-            Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
-            $errors   = $issues.Where({$_.Severity -eq 'Error'})
-            $warnings = $issues.Where({$_.Severity -eq 'Warning'})
-            if ($errors) {
-                Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
-            } else {
-                Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
-            }
+      - uses: actions/checkout@v2
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
 ```
 {% endraw %}
 
@@ -207,15 +207,15 @@ jobs:
     name: Run Pester and upload results
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Test with Pester
-      shell: pwsh
-      run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
-    - name: Upload test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: ubuntu-Unit-Tests
-        path: Unit.Tests.xml
+      - uses: actions/checkout@v2
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
     if: ${{ always() }}
 ```
 {% endraw %}
@@ -240,13 +240,13 @@ jobs:
   publish-to-gallery:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Build and publish
-      env:
-        NUGET_KEY: ${{ secrets.NUGET_KEY }}
-      shell: pwsh
-      run: |
-        ./build.ps1 -Path /tmp/samplemodule
-        Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+      - uses: actions/checkout@v2
+      - name: Build and publish
+        env:
+          NUGET_KEY: ${{ secrets.NUGET_KEY }}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
 ```
 {% endraw %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-python.md b/translations/zh-CN/content/actions/guides/building-and-testing-python.md
index 46766392f2..1b576cc0f3 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-python.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-python.md
@@ -22,7 +22,7 @@ topics:
 
 本指南介绍如何构建、测试和发布 Python 包。
 
-{% if currentversion == "github-ae@latest" %} 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %} 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %} {% data variables.product.prodname_dotcom %} 托管的运行器有工具缓存预安装的软件，包括 Python 和 PyPy。 您无需安装任何项目！ 有关最新版软件以及 Python 和 PyPy 预安装版本的完整列表，请参阅 [{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)。
 {% endif %}
 
@@ -58,25 +58,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Lint with flake8
-      run: |
-        # stop the build if there are Python syntax errors or undefined names
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
-    - name: Test with pytest
-      run: |
-        pytest
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
 ```
 {% endraw %}
 
@@ -123,14 +123,14 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 
 
@@ -156,17 +156,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python 3.x
-      uses: actions/setup-python@v2
-      with:
-        # Semantic version range syntax or exact version of a Python version
-        python-version: '3.x'
-        # Optional - x64 or x86 architecture, defaults to x64
-        architecture: 'x64'
-    # You can test your matrix by printing the current Python version
-    - name: Display Python version
-      run: python -c "import sys; print(sys.version)"
+      - uses: actions/checkout@v2
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
 ```
 
 
@@ -438,25 +438,25 @@ jobs:
         python-version: [2.7, 3.5, 3.6, 3.7, 3.8]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Setup Python # Set Python version
-      uses: actions/setup-python@v2
-      with:
-        python-version: ${{ matrix.python-version }}
-    # Install pip and pytest
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install pytest
-    - name: Test with pytest
-      run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
-    - name: Upload pytest test results
-      uses: actions/upload-artifact@v2
-      with:
-        name: pytest-results-${{ matrix.python-version }}
-        path: junit/test-results-${{ matrix.python-version }}.xml
-      # Use always() to always run this step to publish test results when there are test failures
-      if: ${{ always() }}
+      - uses: actions/checkout@v2
+      - name: Setup Python # Set Python version
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules --junitxml=junit/test-results-${{ matrix.python-version }}.xml
+      - name: Upload pytest test results
+        uses: actions/upload-artifact@v2
+        with:
+          name: pytest-results-${{ matrix.python-version }}
+          path: junit/test-results-${{ matrix.python-version }}.xml
+        # Use always() to always run this step to publish test results when there are test failures
+        if: ${{ always() }}
 ```
 
 
@@ -484,22 +484,22 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install setuptools wheel twine
-    - name: Build and publish
-      env:
-        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
-        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
-      run: |
-        python setup.py sdist bdist_wheel
-        twine upload dist/*
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install setuptools wheel twine
+      - name: Build and publish
+        env:
+          TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: |
+          python setup.py sdist bdist_wheel
+          twine upload dist/*
 ```
 
 
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md
index 6893e41a07..7f598d4c78 100644
--- a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md
@@ -31,7 +31,7 @@ topics:
 
 {% data variables.product.prodname_dotcom %} 提供 Ruby 适用于大多数 Ruby 项目的工作流程模板。 更多信息请参阅 [Ruby 工作流程模板](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml)。
 
-要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。
+要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。 下面显示的工作流假定仓库的默认分支是 `main`。
 
 {% raw %}
 ```yaml
@@ -39,9 +39,9 @@ name: Ruby
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -49,15 +49,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -105,9 +105,9 @@ name: Ruby CI
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -119,15 +119,15 @@ jobs:
         ruby-version: [2.7.x, 2.6.x, 2.5.x]
 
     steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby ${{ matrix.ruby-version }}
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby-version }}
-    - name: Install dependencies
-      run: bundle install
-    - name: Run tests
-      run: bundle exec rake
+      - uses: actions/checkout@v2
+      - name: Set up Ruby ${{ matrix.ruby-version }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
 ```
 {% endraw %}
 
@@ -211,9 +211,9 @@ name: Matrix Testing
 
 on:
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   test:
@@ -225,12 +225,12 @@ jobs:
         ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
     continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-    - run: bundle install
-    - run: bundle exec rake
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+      - run: bundle install
+      - run: bundle exec rake
 ```
 {% endraw %}
 
@@ -248,13 +248,13 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
-    - name: Rubocop
-      run: rubocop
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
 ```
 {% endraw %}
 
@@ -264,7 +264,6 @@ jobs:
 
 您可以使用仓库密码存储发布软件包所需的访问令牌或凭据。 下面的示例创建包并将其发布到 `GitHub Package 注册表`和 `RubyGems`。
 
-{% raw %}
 ```yaml
 
 name: Ruby Gem
@@ -272,46 +271,48 @@ name: Ruby Gem
 on:
   # Manually publish
   workflow_dispatch:
-  # Alternatively, publish whenever changes are merged to the default branch.
+  # Alternatively, publish whenever changes are merged to the `main` branch.
   push:
-    branches: [ $default-branch ]
+    branches: [ main ]
   pull_request:
-    branches: [ $default-branch ]
+    branches: [ main ]
 
 jobs:
   build:
     name: Build + Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
-    - uses: actions/checkout@v2
-    - name: Set up Ruby 2.6
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: 2.6
-    - run: bundle install
+    steps:{% raw %}
+      - uses: actions/checkout@v2
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 2.6
+      - run: bundle install
 
-    - name: Publish to GPR
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
-      env:
-        GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
-        OWNER: ${{ github.repository_owner }}
+      - name: Publish to GPR
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
 
-    - name: Publish to RubyGems
-      run: |
-        mkdir -p $HOME/.gem
-        touch $HOME/.gem/credentials
-        chmod 0600 $HOME/.gem/credentials
-        printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-swift.md b/translations/zh-CN/content/actions/guides/building-and-testing-swift.md
new file mode 100644
index 0000000000..3a8dcef50c
--- /dev/null
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-swift.md
@@ -0,0 +1,127 @@
+---
+title: Building and testing Swift
+intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### 简介
+
+This guide shows you how to build and test a Swift package.
+
+{% if currentVersion == "github-ae@latest" %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. 有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% else %}{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, and the Ubuntu and macOS runners include the dependencies for building Swift packages. For a full list of up-to-date software and the preinstalled versions of Swift and Xcode, see "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %}
+
+### 基本要求
+
+您应该已经熟悉 YAML 语法及其如何与 {% data variables.product.prodname_actions %} 结合使用。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
+
+We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
+
+### Starting with the Swift workflow template
+
+{% data variables.product.prodname_dotcom %} provides a Swift workflow template that should work for most Swift projects, and this guide includes examples that show you how to customize this template. For more information, see the [Swift workflow template](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+要快速开始，请将模板添加到仓库的 `.github/workflows` 目录中。
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+### Specifying a Swift version
+
+To use a specific preinstalled version of Swift on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `fwal/setup-swift` action. This action finds a specific version of Swift from the tools cache on the runner and adds the necessary binaries to `PATH`. These changes will persist for the remainder of a job. For more information, see the [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) action.
+
+If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+
+The examples below demonstrate using the `fwal/setup-swift` action.
+
+#### Using multiple Swift versions
+
+You can configure your job to use a multiple versions of Swift in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: fwal/setup-swift@v1
+        with:
+          swift-version: ${{ matrix.swift }}
+      - uses: actions/checkout@v2
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+{% endraw %}
+
+#### Using a single specific Swift version
+
+You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+### 构建和测试代码
+
+You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: actions/checkout@v2
+  - uses: fwal/setup-swift@v1
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
+{% endraw %}
diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-xamarin-applications.md b/translations/zh-CN/content/actions/guides/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..a9e8f5e63e
--- /dev/null
+++ b/translations/zh-CN/content/actions/guides/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Building and testing Xamarin applications
+intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Xamarin application.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### 简介
+
+This guide shows you how to create a workflow that performs continuous integration (CI) for your Xamarin project. 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。
+
+{% data variables.product.prodname_actions %}-hosted macOS runner stores Xamarin SDK versions and the associated Mono versions as a set of symlinks to Xamarin SDK locations that are available by a single bundle symlink. For a full list of available Xamarin SDK versions and their corresponding bundles, see the runners documentation:
+
+* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md#xamarin-bundles)
+
+{% data reusables.github-actions.macos-runner-preview %}
+
+### 基本要求
+
+We recommend that you have a basic understanding of Xamarin, .NET Core SDK, YAML, workflow configuration options, and how to create a workflow file. 更多信息请参阅：
+
+- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Getting started with .NET](https://dotnet.microsoft.com/learn)"
+- "[Learn Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
+
+### Bulding Xamarin.iOS apps
+
+The example below demonstrates how to change the default Xamarin bundle and build  a Xamarin.iOS application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Set default Xcode 12.3
+        run: |
+          XCODE_ROOT=/Applications/Xcode_12.3.0.app
+          echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+          sudo xcode-select -s $XCODE_ROOT
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+{% endraw %}
+
+### Bulding Xamarin.Android apps
+
+The example below demonstrates how to change default the Xamarin bundle and build a Xamarin.Android application.
+
+{% raw %}
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Select default Xamarin bundle to 6_12_6
+        run: |
+          XAMARIN_SDK=6_12_6
+          $VM_ASSETS/select-xamarin-sdk.sh $XAMARIN_SDK
+
+      - name: Setup .NET Core SDK 5.0.x
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: '5.0.x'
+
+      - name: Install dependencies
+        run: nuget restore <sln_file_path>
+
+      - name: Build
+        run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+{% endraw %}
+
+### 指定 .NET 版本
+
+要在 {% data variables.product.prodname_dotcom %} 托管的运行器上使用预安装的 .NET Core SDK 版本，请使用 `setup-dotnet` 操作。 此操作从每个运行器上的工具缓存中查找特定版本的 .NET，并将必要的二进制文件添加到 `PATH`。 这些更改将持续用于作业的其余部分。
+
+`setup-dotnet` 操作是 .NET 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 .NET 行为一致。 如果使用自托管运行器，则必须安装 .NET 并将其添加到 `PATH`。 更多信息请参阅 [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) 操作。
diff --git a/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index 58f0789d02..b526051c67 100644
--- a/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/zh-CN/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -59,7 +59,16 @@ topics:
 
 - `key`：**必要** 保存缓存时创建的键，以及用于搜索缓存的键。 可以是变量、上下文值、静态字符串和函数的任何组合。 密钥最大长度为 512 个字符，密钥长度超过最大长度将导致操作失败。
 - `path`：**必要** 运行器上缓存或还原的文件路径。 路径可以是绝对路径或相对于工作目录的路径。
-  - 使用 `cache` 操作的 `v2`，可以指定单个路径，或将多个路径指定为列表。 路径可以是目录或单个文件，并且支持 glob 模式。
+  - 路径可以是目录或单个文件，并且支持 glob 模式。
+  - With `v2` of the `cache` action, you can specify a single path, or you can add multiple paths on separate lines. 例如：
+    ```
+    - name: Cache Gradle packages
+      uses: actions/cache@v2
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
   - 对于 `cache` 操作的 `v1`，仅支持单个路径，它必须是一个目录。 您不能缓存单个文件。
 - `restore-keys`：**可选** `key` 没有发生缓存命中时用于查找缓存的其他密钥顺序列表。
 
@@ -82,30 +91,29 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-    - name: Cache node modules
-      uses: actions/cache@v2
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm` on Linux/macOS
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
+      - name: Cache node modules
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+            ${{ runner.os }}-build-
+            ${{ runner.os }}-
 
-    - name: Install Dependencies
-      run: npm install
+      - name: Install Dependencies
+        run: npm install
 
-    - name: Build
-      run: npm build
-
-    - name: Test
-      run: npm test
+      - name: Build
+        run: npm build
 
+      - name: Test
+        run: npm test
 ```
 {% endraw %}
 
diff --git a/translations/zh-CN/content/actions/guides/closing-inactive-issues.md b/translations/zh-CN/content/actions/guides/closing-inactive-issues.md
index 9952101587..5857afdbd3 100644
--- a/translations/zh-CN/content/actions/guides/closing-inactive-issues.md
+++ b/translations/zh-CN/content/actions/guides/closing-inactive-issues.md
@@ -29,7 +29,6 @@ topics:
 2. {% data reusables.actions.make-workflow-file %}
 3. 将以下 YAML 内容复制到工作流程文件中。
 
-    {% raw %}
     ```yaml{:copy}
     name: Close inactive issues
     on:
@@ -38,7 +37,10 @@ topics:
 
     jobs:
       close-issues:
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - uses: actions/stale@v3
             with:
@@ -49,9 +51,9 @@ topics:
               close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
               days-before-pr-stale: -1
               days-before-pr-close: -1
-              repo-token: ${{ secrets.GITHUB_TOKEN }}
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. 自定义工工作流程文件中的参数：
    - 更改 `on.schedule` 的值以指示您希望此工作流程何时运行。 在上面的示例中，工作流将于每天 1:30 UTC 运行。 有关计划工作流程的更多信息，请参阅“[计划的活动](/actions/reference/events-that-trigger-workflows#scheduled-events)”。
    - 将 `days-before-issue-stale` 的值更改为在 `actions/stale` 操作标记议题之前无活动的天数。 如果您不希望此操作标记议题，将此值设置为 `-1`。
diff --git a/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
index ac514ff59f..9f60911cb5 100644
--- a/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md
@@ -29,7 +29,6 @@ topics:
 2. {% data reusables.actions.make-workflow-file %}
 3. 将以下 YAML 内容复制到工作流程文件中。
 
-    {% raw %}
     ```yaml{:copy}
     name: Add comment
     on:
@@ -39,16 +38,18 @@ topics:
     jobs:
       add-comment:
         if: github.event.label.name == 'help-wanted'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Add comment
             uses: peter-evans/create-or-update-comment@v1
             with:
-              issue-number: ${{ github.event.issue.number }}
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
               body: |
                 This issue is available for anyone to work on. **请确保在您的拉请求中引用此议题。** :sparkles: 谢谢您的贡献！ :sparkles:
     ```
-    {% endraw %}
+
 4. 自定义工工作流程文件中的参数：
    - 将 `if: github.event.label.name == 'help-wanted'` 中的 `help-wanted` 替换为您想要操作的标签。 如果您想要操作多个标签，请用 `||` 分隔条件。 例如，只要 `bug` 或 `fix me` 标签添加到议题，`if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` 就会评论。
    - 将 `body` 的值更改为您想要添加的评论。 支持 GitHub Flavored Markdown。 有关 Markdown 的更多信息，请参阅“[基本撰写和格式语法](/github/writing-on-github/basic-writing-and-formatting-syntax)”。
diff --git a/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md
index 8bd3d9335d..73649198cf 100644
--- a/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md
+++ b/translations/zh-CN/content/actions/guides/creating-postgresql-service-containers.md
@@ -22,7 +22,7 @@ topics:
 
 ### 简介
 
-本指南演示了使用 Docker Hub `postgres` 映像配置服务容器的工作流程示例。 工作流程运行脚本来创建 PostgreSQL 客户端并使用数据填充客户端。 要测试工作流程是否创建并填充 PostgreSQL 客户端，脚本会将客户端数据打印到控制台。
+本指南演示了使用 Docker Hub `postgres` 映像配置服务容器的工作流程示例。 The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
@@ -81,10 +81,10 @@ jobs:
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client, populates
-        # the client with data, and retrieves data
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
         run: node client.js
-        # Environment variable used by the `client.js` script to create a new PostgreSQL client.
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
         env:
           # The hostname used to communicate with the PostgreSQL service container
           POSTGRES_HOST: postgres
@@ -141,8 +141,8 @@ steps:
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL client, populates
-    # the client with data, and retrieves data
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
     run: node client.js
     # Environment variable used by the `client.js` script to create
     # a new PostgreSQL client.
@@ -204,11 +204,11 @@ jobs:
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client, populates
-        # the client with data, and retrieves data
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
         run: node client.js
-        # Environment variable used by the `client.js` script to create
-        # a new PostgreSQL client.
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
         env:
           # The hostname used to communicate with the PostgreSQL service container
           POSTGRES_HOST: localhost
@@ -268,11 +268,11 @@ steps:
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL client, populates
-    # the client with data, and retrieves data
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new PostgreSQL client.
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
     env:
       # The hostname used to communicate with the PostgreSQL service container
       POSTGRES_HOST: localhost
@@ -286,9 +286,9 @@ steps:
 
 ### 测试 PostgreSQL 服务容器
 
-您可以使用以下脚本测试工作流程，该脚本将创建 PostgreSQL 客户端，并添加包含某些占位符数据的新表。 然后，脚本将存储在 PostgreSQL 客户端中的值打印到终端。 您的脚本可以使用任何您喜欢的语言，但此示例使用 Node.js 和 `Pg` npm 模块。 更多信息请参阅 [npm pg 模块](https://www.npmjs.com/package/pg)。
+You can test your workflow using the following script, which connects to the PostgreSQL service and adds a new table with some placeholder data. The script then prints the values stored in the PostgreSQL table to the terminal. 您的脚本可以使用任何您喜欢的语言，但此示例使用 Node.js 和 `Pg` npm 模块。 更多信息请参阅 [npm pg 模块](https://www.npmjs.com/package/pg)。
 
-您可以修改 *client.js* 以包含工作流程需要的任何 PostgreSQL 操作。 在此示例中，脚本创建 PostgreSQL 客户端实例、创建表、添加占位符数据，然后检索数据。
+您可以修改 *client.js* 以包含工作流程需要的任何 PostgreSQL 操作。 In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-该脚本创建新的 PostgreSQLL `Client`，接受 `host` 和 `port` 参数。 该脚本使用 `POSTGRES_HOST` 和 `POSTGRES_PORT` 环境变量来设置客户端的 IP 地址和端口。 如果未定义 `host` 和 `port`，则默认主机为 `localhost`，默认端口为 5432。
+The script creates a new connection to the PostgreSQL service, and uses the `POSTGRES_HOST` and `POSTGRES_PORT` environment variables to specify the PostgreSQL service IP address and port. 如果未定义 `host` 和 `port`，则默认主机为 `localhost`，默认端口为 5432。
 
-脚本创建一个表并将用占位符数据添加。 要测试 PostgreSQL 数据库是否包含数据，脚本将会表的内容打印到控制台日志。
+脚本创建一个表并将用占位符数据添加。 To test that the `postgres` database contains the data, the script prints the contents of the table to the console log.
 
-运行此工作流程时，应会在“连接到 PostgreSQL”步骤中看到以下输出，确认您创建了 PostgreSQL 客户端并添加了数据：
+When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
 ```
 null [ { id: 1,
diff --git a/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md
index c2daf51adb..1accc0409c 100644
--- a/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md
+++ b/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md
@@ -71,7 +71,6 @@ The following example workflow demonstrates how to build a container image and p
 
 Ensure that you provide your own values for all the variables in the `env` key of the workflow.
 
-{% raw %}
 ```yaml{:copy}
 name: Deploy to Amazon ECS
 
@@ -96,9 +95,12 @@ defaults:
 jobs:
   deploy:
     name: Deploy
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
 
-    steps:
+    {% raw %}steps:
       - name: Checkout
         uses: actions/checkout@v2
 
@@ -140,9 +142,9 @@ jobs:
           task-definition: ${{ steps.task-def.outputs.task-definition }}
           service: ${{ env.ECS_SERVICE }}
           cluster: ${{ env.ECS_CLUSTER }}
-          wait-for-service-stability: true
+          wait-for-service-stability: true{% endraw %}
 ```
-{% endraw %}
+
 
 ### 其他资源
 
diff --git a/translations/zh-CN/content/actions/guides/index.md b/translations/zh-CN/content/actions/guides/index.md
index 9e4eb08b24..763551b060 100644
--- a/translations/zh-CN/content/actions/guides/index.md
+++ b/translations/zh-CN/content/actions/guides/index.md
@@ -85,7 +85,9 @@ includeGuides:
 <!-- {% link_in_list /building-and-testing-java-with-maven %} -->
 <!-- {% link_in_list /building-and-testing-java-with-gradle %} -->
 <!-- {% link_in_list /building-and-testing-java-with-ant %} -->
+<!-- {% link_in_list /building-and-testing-swift %}-->
 <!-- {% link_in_list /installing-an-apple-certificate-on-macos-runners-for-xcode-development %} -->
+<!-- {% link_in_list /building-and-testing-xamarin-applications %} -->
 <!-- {% link_in_list /about-packaging-with-github-actions %} -->
 <!-- {% link_in_list /publishing-nodejs-packages %} -->
 <!-- {% link_in_list /publishing-java-packages-with-maven %} -->
@@ -107,3 +109,4 @@ includeGuides:
 <!-- {% link_in_list /commenting-on-an-issue-when-a-label-is-added %} -->
 <!-- {% link_in_list /moving-assigned-issues-on-project-boards %} -->
 <!-- {% link_in_list /removing-a-label-when-a-card-is-added-to-a-project-board-column %} -->
+<!-- {% link_in_list /managing-github-actions-with-github-cli %} -->
diff --git a/translations/zh-CN/content/actions/guides/managing-github-actions-with-github-cli.md b/translations/zh-CN/content/actions/guides/managing-github-actions-with-github-cli.md
new file mode 100644
index 0000000000..bc3fb6ad8d
--- /dev/null
+++ b/translations/zh-CN/content/actions/guides/managing-github-actions-with-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: 使用 GitHub CLI 管理 GitHub Actions
+intro: '您可以使用 {% data variables.product.prodname_cli %} 与 {% data variables.product.prodname_actions %} 互动。'
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+type: overview
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+### 设置 {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.download-update-cli %} {% data reusables.cli.actions-cli-version %} {% data reusables.cli.cli-manual %}
+
+{% data reusables.cli.cli-auth %}
+
+{% data reusables.cli.cli-repo %}
+
+### 通过 {% data variables.product.prodname_cli %} 管理 {% data variables.product.prodname_actions %}
+
+要查看所有与 {% data variables.product.prodname_actions %} 相关的可用命令，运行 `gh actions`。
+
+有关在特定情况下使用命令的更多信息，请参阅以下程序：
+
+- ""[重新运行工作流程](/actions/managing-workflow-runs/re-running-a-workflow#re-run-a-workflow-through-github-cli)"
+- "[手动运行工作流程](/actions/managing-workflow-runs/manually-running-a-workflow#running-a-workflow-using-github-cli)"
+- "[下载工作流程构件](/actions/managing-workflow-runs/downloading-workflow-artifacts#download-artifacts-through-github-cli)"
+- "[使用工作流程运行日志](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-through-github-cli)"
+- "[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history#viewing-workflow-run-history-with-github-cli)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+- "[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#disabling-and-enabling-workflows-through-github-cli)"{% endif %}
diff --git a/translations/zh-CN/content/actions/guides/publishing-docker-images.md b/translations/zh-CN/content/actions/guides/publishing-docker-images.md
index 254d43e5ab..3fde5b9957 100644
--- a/translations/zh-CN/content/actions/guides/publishing-docker-images.md
+++ b/translations/zh-CN/content/actions/guides/publishing-docker-images.md
@@ -37,7 +37,7 @@ topics:
 
 - [加密的密码](/actions/reference/encrypted-secrets)"
 - "[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)"
-- "[配置 Docker 用于 {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)"
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"
 
 ### 关于映像配置
 
@@ -98,7 +98,6 @@ jobs:
 * `registry`：必须设置为 `docker.pkg.github.com`。
 * `repository`：必须以 `OWNER/REPOSITORY/IMAGE_NAME` 格式设置。 例如，对于 `http://github.com/octo-org/octo-repo` 上名为 `octo-image` stored on {% data variables.product.prodname_dotcom %} 的映像，`repository` 选项应设置为 `octo-org/octo-repo/octo-image`。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -107,21 +106,23 @@ on:
 jobs:
   push_to_registry:
     name: Push Docker image to GitHub Packages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 
 ```
-{% endraw %}
 
 {% data reusables.github-actions.docker-tag-with-ref %}
 
@@ -131,7 +132,6 @@ jobs:
 
 下面的示例工作流程使用前面章节中的 `build-push-action` 步骤（“[发布映像到 Docker Hub](#publishing-images-to-docker-hub)”和“[发布映像到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”）来创建同时推送到两个注册表的单一工作流程。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish Docker image
 on:
@@ -140,26 +140,28 @@ on:
 jobs:
   push_to_registries:
     name: Push Docker image to multiple registries
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
       - name: Push to Docker Hub
         uses: docker/build-push-action@v1
         with:
-          username: ${{ secrets.DOCKER_USERNAME }}
-          password: ${{ secrets.DOCKER_PASSWORD }}
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
           repository: my-docker-hub-namespace/my-docker-hub-repository
           tag_with_ref: true
       - name: Push to GitHub Packages
         uses: docker/build-push-action@v1
         with:
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
           registry: docker.pkg.github.com
           repository: my-org/my-repo/my-image
           tag_with_ref: true
 ```
-{% endraw %}
 
 上面的工作流程检出 {% data variables.product.prodname_dotcom %} 仓库，并且使用两次 `build-push-action` 操作构建并推送 Docker 映像到 Docker Hub 和 {% data variables.product.prodname_registry %}。 对于这两个步骤， 它设置 `build-pow-action` 选项 [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) 自动使用工作流程事件的 Git 引用标记构建的 Docker 映像。 此工作流程在发布 {% data variables.product.prodname_dotcom %} 版本时触发，因此对两个注册表的引用将是该版本的 Git 标记。
diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md
index c968d70af7..9e7167e771 100644
--- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md
+++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md
@@ -32,7 +32,7 @@ topics:
 
 您可能还发现基本了解以下内容是有帮助的：
 
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[环境变量](/actions/reference/environment-variables)"
 - [加密的密码](/actions/reference/encrypted-secrets)"
 - "[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)"
@@ -108,7 +108,7 @@ jobs:
 
 您可以在 _build.gradle_ 文件的发布块中定义指向 {% data variables.product.prodname_registry %} 的新 Maven 仓库。  在仓库配置中，您也可以利用在 CI 工作流程运行中设置的环境变量。  您可以使用 `GITHUB_ACTOR` 环境变量作为用户名，并且可以使用 `GITHUB_TOKENN` 密码设置 `GITHUB_TOKEN` 环境变量。
 
-`GITHUB_TOKEN` 默认存在于您的仓库中，并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
+{% data reusables.github-actions.github-token-permissions %}
 
 例如，如果组织名为“octocat”且仓库名为“hello-world”，则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
 
@@ -133,7 +133,6 @@ publishing {
 
 使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -141,7 +140,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -151,12 +153,11 @@ jobs:
       - name: Publish package
         run: gradle publish
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. 运行 `gradle published` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。
+1. 运行 `gradle published` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} `permissions` 键指定 `GITHUB_TOKEN` 密钥允许的访问权限。{% endif %}
 
    有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
@@ -199,7 +200,6 @@ publishing {
 
 使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -207,7 +207,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java
@@ -217,14 +220,13 @@ jobs:
           distribution: 'adopt'
       - name: Publish to the Maven Central Repository
         run: gradle publish
-        env:
+        env: {% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. 运行 `gradle published` 命令以发布到 `OSSRH` Maven 仓库和 {% data variables.product.prodname_registry %}。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。
+1. 运行 `gradle published` 命令以发布到 `OSSRH` Maven 仓库和 {% data variables.product.prodname_registry %}。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} `permissions` 键指定 `GITHUB_TOKEN` 密钥允许的访问权限。{% endif %}
 
    有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md
index bdc72ede2a..7819d5771e 100644
--- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md
+++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md
@@ -32,7 +32,7 @@ topics:
 
 您可能还发现基本了解以下内容是有帮助的：
 
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[环境变量](/actions/reference/environment-variables)"
 - [加密的密码](/actions/reference/encrypted-secrets)"
 - "[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)"
@@ -112,9 +112,9 @@ jobs:
 
 每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。 有关 `release` 事件的更多信息，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
 
-在此工作流程中，您可以使用 `setup-java` 操作。 此操作将给定版本的 JDK 安装到 `PATH`，并且设置 Maven _settings.xml_ 以将包发布到 {% data variables.product.prodname_registry %}。 生成的 _settings.xml_ 定义使用 `github` 的 `id` 向服务器验证，使用 `GITHUB_ACTOR` 环境变量作为用户名，`GITHUB_TOKEN` 环境变量作为密码。
+在此工作流程中，您可以使用 `setup-java` 操作。 此操作将给定版本的 JDK 安装到 `PATH`，并且设置 Maven _settings.xml_ 以将包发布到 {% data variables.product.prodname_registry %}。 生成的 _settings.xml_ 定义使用 `github` 的 `id` 向服务器验证，使用 `GITHUB_ACTOR` 环境变量作为用户名，`GITHUB_TOKEN` 环境变量作为密码。 `GITHUB_TOKEN` 环境变量将获分配特殊 `GITHUB_TOKEN` 密钥的值。
 
-`GITHUB_TOKEN` 默认存在于您的仓库中，并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
+{% data reusables.github-actions.github-token-permissions %}
 
 对于基于 Maven的项目，您可以通过在 _pom.xml_ 文件中创建分发仓库来使用这些设置，该文件以 `github` 的 `id` 指向 {% data variables.product.prodname_registry %} 端点。
 
@@ -137,7 +137,6 @@ jobs:
 
 通过此配置，您可以创建一个工作流程，以使用自动生成的 _settings.xml_ 将包发布到 {% data variables.product.prodname_registry %}。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to GitHub Packages
 on:
@@ -145,7 +144,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-java@v2
@@ -155,9 +157,8 @@ jobs:
       - name: Publish package
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 此工作流程执行以下步骤：
 
@@ -173,7 +174,6 @@ jobs:
 
 确保 _pom.xml_ 文件包含用于 {% data variables.product.prodname_dotcom %} 仓库和 Maven 中心仓库提供商的分发管理仓库。 例如，如果您通过 OSSRH 托管项目部署到中心仓库，您可能想通过将 `id` 设置为 `ossrh` 在分发管理仓库中指定它，并且想通过将 `id` 设置为 `github` 在分发管理仓库中指定 {% data variables.product.prodname_registry %}。
 
-{% raw %}
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
 on:
@@ -181,7 +181,10 @@ on:
     types: [created]
 jobs:
   publish:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
       - uses: actions/checkout@v2
       - name: Set up Java for publishing to Maven Central Repository
@@ -194,7 +197,7 @@ jobs:
           server-password: MAVEN_PASSWORD
       - name: Publish to the Maven Central Repository
         run: mvn --batch-mode deploy
-        env:
+        env:{% raw %}
           MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
       - name: Set up Java for publishing to GitHub Packages
@@ -205,9 +208,8 @@ jobs:
       - name: Publish to GitHub Packages
         run: mvn --batch-mode deploy
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 此工作流程将调用 `setup-java` 操作两次。  每次运行 `setup-java` 操作时，都会覆盖 Maven _settings.xml_ 文件以发布包。  为向仓库验证，_settings.xml_ 文件引用分发管理仓库 `id` 以及用户名和密码。
 
diff --git a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md
index a307f9e13e..06e3f1fe68 100644
--- a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md
+++ b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md
@@ -33,7 +33,7 @@ topics:
 
 您可能还发现基本了解以下内容是有帮助的：
 
-- "[配置 npm 用于 {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages)"
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
 - "[环境变量](/actions/reference/environment-variables)"
 - [加密的密码](/actions/reference/encrypted-secrets)"
 - "[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)"
@@ -70,16 +70,16 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -112,7 +112,7 @@ always-auth=true
 
 #### 向目标仓库验证
 
-要向工作流程中的 {% data variables.product.prodname_registry %} 注册表进行验证，您可以使用仓库的 `GITHUB_TOKEN`。 它是自动创建的，对工作流程运行所在仓库中的包具有_读取_和_写入_权限。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)。
+要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 {% data reusables.github-actions.github-token-permissions %}
 
 如果要将包发布到其他仓库，您必须使用对目标仓库中的包具有写入权限的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
 
@@ -120,7 +120,6 @@ always-auth=true
 
 此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
 
-{% raw %}
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -128,22 +127,24 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: npm install
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm install
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
 
 `setup-node` 操作在运行器上创建 *.npmrc* 文件。 使用 `scope` 输入到 `setup-node` 操作时，*.npmrc* 文件包含作用域前缀。 默认情况下，`setup-node` 操作在 *.npmrc* 文件中将作用域设置为包含该工作流程文件的帐户。
 
@@ -167,18 +168,18 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v2
-      with:
-        node-version: '12.x'
-        registry-url: 'https://registry.npmjs.org'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    - run: yarn
-    - run: yarn publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '12.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 {% endraw %}
 
@@ -196,13 +197,13 @@ jobs:
 
 确认 *package.json* 文件包含 {% data variables.product.prodname_dotcom %} 仓库和 npm 注册表的作用域。 例如，如果您计划将 `octocat/npm-hello-world-test` 仓库中的包发布到 {% data variables.product.prodname_dotcom %} 和 https://www.npmjs.com/package/@octocat/npm-hello-world-test，则 *package.json* 文件中的名称将是 `"name": "@octocat/npm-hello-world-test"`。
 
-要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 `GITHUB_TOKEN` 默认存在于您的仓库中，并且对工作流程运行的仓库中的包具有读取和写入权限。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
+要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 {% data reusables.github-actions.github-token-permissions %}
 
 使用 `scope` 输入到 `setup-node` 操作时，操作将创建包含作用域前缀的 *.npmrc* 文件。 默认情况下，`setup-node` 操作在 *.npmrc* 文件中将作用域设置为拥有该工作流程文件的用户或组织。
 
 此工作流程将调用 `setup-node` 操作两次。 每当 `setup-node` 操作运行时，都会覆盖 *.npmrc* 文件。 *.npmrc* 文件引用的令牌允许您对 `NODE_AUTH_TOKEN` 环境变量中的包注册表执行验证的操作。 工作流程在 `npm publish` 命令每次运行时设置 `NODE_AUTH_TOKEN` 环境变量，先通过令牌发布到 npm (`NPM_TOKEN`)，然后通过令牌发布到 {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`)。
 
-{% raw %}
+
 ```yaml{:copy}
 name: Node.js Package
 on:
@@ -210,28 +211,30 @@ on:
     types: [created]
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
     steps:
-    - uses: actions/checkout@v2
-    # Setup .npmrc file to publish to npm
-    - uses: actions/setup-node@v1
-      with:
-        node-version: '10.x'
-        registry-url: 'https://registry.npmjs.org'
-    - run: npm install
-    # Publish to npm
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-    # Setup .npmrc file to publish to GitHub Packages
-    - uses: actions/setup-node@v1
-      with:
-        registry-url: 'https://npm.pkg.github.com'
-        # Defaults to the user or organization that owns the workflow file
-        scope: '@octocat'
-    # Publish to GitHub Packages
-    - run: npm publish
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: actions/checkout@v2
+      # Setup .npmrc file to publish to npm
+      - uses: actions/setup-node@v1
+        with:
+          node-version: '10.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm install
+      # Publish to npm
+      - run: npm publish --access public
+        env:{% raw %}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: actions/setup-node@v1
+        with:
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      # Publish to GitHub Packages
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
-{% endraw %}
diff --git a/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index 77ca00213f..fb34a86ea6 100644
--- a/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -30,7 +30,6 @@ topics:
 3. {% data reusables.actions.make-workflow-file %}
 4. 将以下 YAML 内容复制到工作流程文件中。
 
-    {% raw %}
     ```yaml{:copy}
     name: Remove labels
     on:
@@ -40,14 +39,18 @@ topics:
     jobs:
       remove_labels:
         if: github.event.project_card.column_id == '12345678'
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write
+          pull-requests: write{% endif %}
         steps:
           - name: remove labels
             uses: andymckay/labeler@master
             with:
               remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 5. 自定义工工作流程文件中的参数：
    - 在 `github.event.project_card.column_id = "12345678"`中，将 `12345678` 替换为要取消标记移至其中的议题和拉取请求的列 ID。
 
diff --git a/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md b/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md
index 6afd5fd237..bfd5c6c305 100644
--- a/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md
+++ b/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md
@@ -29,7 +29,6 @@ topics:
 2. {% data reusables.actions.make-workflow-file %}
 3. 将以下 YAML 内容复制到工作流程文件中。
 
-    {% raw %}
     ```yaml{:copy}
     name: Weekly Team Sync
     on:
@@ -39,7 +38,9 @@ topics:
     jobs:
       create_issue:
         name: Create team sync issue
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          issues: write{% endif %}
         steps:
           - name: Create team sync issue
             uses: imjohnbo/issue-bot@v3.0
@@ -62,9 +63,9 @@ topics:
               pinned: false
               close-previous: false
             env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
     ```
-    {% endraw %}
+
 4. 自定义工工作流程文件中的参数：
    - 更改 `on.schedule` 的值以指示您希望此工作流程何时运行。 在上面的示例中，工作流将于每周一 7:20 UTC 运行。 有关计划工作流程的更多信息，请参阅“[计划的活动](/actions/reference/events-that-trigger-workflows#scheduled-events)”。
    - 将 `assignees` 的值更改为您想要分配给此议题的 {% data variables.product.prodname_dotcom %} 用户名。
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 3ae86729cb..e29cdf25e7 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
@@ -11,12 +11,14 @@ versions:
 type: tutorial
 ---
 
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 您可以将自托管的运行器添加到 {{ site.data.variables.product.prodname_actions }}。
 
-If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place.
+如果您是组织或企业管理员，您可能希望在组织或企业级别添加自托管的运行器。 此方法使运行器可用于组织或企业中的多个仓库，还允许您在一个位置管理运行器。
 
 如果需要支持自托管运行器的操作系统的信息，或通过代理服务器的自托管运行器，请参阅“[关于自托管运行器](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
 
@@ -58,7 +60,7 @@ If you are an organization or enterprise administrator, you might want to add yo
 
 {% if currentVersion == "free-pro-team@latest" %}
 要将自托管的运行器添加到企业帐户，您必须是组织所有者。
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%}
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 要在
 {% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。
 {% endif %}
@@ -73,10 +75,10 @@ If you are an organization or enterprise administrator, you might want to add yo
 
 {% data reusables.github-actions.self-hosted-runner-public-repo-access %}
 
-#### Making enterprise runners available to repositories
+#### 让企业运行器可用于仓库
 
-By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization.
+在默认情况下，企业的“默认”自托管运行器组的运行器可用于企业中的所有组织，但不可用于每个组织中的所有仓库。
 
-To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization.
+要让企业级自托管运行器组可用于组织仓库，您可能需要更改组织对运行器组的继承设置，使运行器可用于组织中的仓库。
 
-For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+有关更改运行器组访问设置的更多信息，请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。
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 9ec4cace60..27dd1ddcfa 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
@@ -53,7 +53,7 @@ type: tutorial
 
    **警告**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
@@ -85,7 +85,7 @@ type: tutorial
 
    **警告**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index bfe3d13bea..43547d810b 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -13,8 +13,10 @@ type: tutorial
 defaultPlatform: linux
 ---
 
+{% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### 使用 {{ site.data.variables.product.prodname_dotcom }} 检查自托管运行器的状态
 
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 aa465e5264..0090b37c7f 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
@@ -66,7 +66,7 @@ type: tutorial
 
 {% if currentVersion == "free-pro-team@latest" %}
 要从企业帐户删除自托管运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。
-{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"% or currentVersion == "github-ae@latest" }
+{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 要在
 {% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。 建议您也访问自托管的运行器机器。
 {% endif %}
diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md
index bcc179822f..192e79886d 100644
--- a/translations/zh-CN/content/actions/index.md
+++ b/translations/zh-CN/content/actions/index.md
@@ -47,28 +47,3 @@ versions:
 <!-- {% link_with_intro /using-github-hosted-runners %} -->
 <!-- {% link_with_intro /hosting-your-own-runners %} -->
 <!-- {% link_with_intro /reference %} -->
-
-<!-- Code examples -->
-{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
-{% if actionsCodeExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">代码示例</h2>
-
-  <div class="pr-lg-3 mb-5 mt-3">
-    <input class="js-filter-card-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="搜索代码示例" type="search" autocomplete="off" aria-label="Search code examples"/>
-  </div>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render code-example-card for actionsCodeExamples as example %}
-  </div>
-
-  <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">显示更多 {% octicon "arrow-right" %}</button>
-
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">抱歉，找不到结果 <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">似乎没有适合您的过滤条件的示例。<br>请尝试其他过滤条件或添加代码示例</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">了解如何添加代码示例 {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md
index 3c12ef1484..2280b03f13 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Azure Pipelines to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Azure Pipelines share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: 从 Azure Pelines 迁移到 GitHub Actions
+intro: '{% data variables.product.prodname_actions %} 和 Azure Pipelines 具有一些相似的配置，这使得迁移到 {% data variables.product.prodname_actions %} 很简单。'
 redirect_from:
   - /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions
 versions:
@@ -17,42 +17,43 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### Introduction
+### 简介
 
-Azure Pipelines and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. Azure Pipelines and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+Azure Pipelines 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 Azure Pelines 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处：
 
-- Workflow configuration files are written in YAML and are stored in the code's repository.
-- Workflows include one or more jobs.
-- Jobs include one or more steps or individual commands.
-- Steps or tasks can be reused and shared with the community.
+- 工作流程配置文件以 YAML 编写并存储在代码仓库中。
+- 工作流程包括一项或多项作业。
+- 作业包括一个或多个步骤或单个命令。
+- 步骤或任务可以重复使用并与社区共享。
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。
 
-### Key differences
+### 主要差异
 
-When migrating from Azure Pipelines, consider the following differences:
+从 Azure Pipelines 迁移时，考虑以下差异：
 
-- Azure Pipelines supports a legacy _classic editor_, which lets you define your CI configuration in a GUI editor instead of creating the pipeline definition in a YAML file. {% data variables.product.prodname_actions %} uses YAML files to define workflows and does not support a graphical editor.
-- Azure Pipelines allows you to omit some structure in job definitions. For example, if you only have a single job, you don't need to define the job and only need to define its steps. {% data variables.product.prodname_actions %} requires explicit configuration, and YAML structure cannot be omitted.
-- Azure Pipelines supports _stages_ defined in the YAML file, which can be used to create deployment workflows. {% data variables.product.prodname_actions %} requires you to separate stages into separate YAML workflow files.
-- On-premises Azure Pipelines build agents can be selected with capabilities. {% data variables.product.prodname_actions %} self-hosted runners can be selected with labels.
+- Azure Pelines 支持传统的_经典编辑器_，可让您在 GUI 编辑器中定义 CI 配置，而不是在 YAML 文件中创建管道定义。 {% data variables.product.prodname_actions %} 使用 YAML 文件来定义工作流程，不支持图形编辑器。
+- Azure Pelines 允许您在作业定义中省略一些结构。 例如，如果您只有一个作业，则无需定义作业，只需要定义其步骤。 {% data variables.product.prodname_actions %} 需要明确的配置，且不能省略 YAML 结构。
+- Azure Pipelines 支持 YAML 文件中定义的_阶段_，可用于创建部署工作流程。 {% data variables.product.prodname_actions %} 要求您将阶段分成单独的 YAML 工作流程文件。
+- 可以使用功能选择本地 Azure Pipelines 构建代理。 通过标签可以选择 {% data variables.product.prodname_actions %} 自托管的运行器。
 
-### Migrating jobs and steps
+### 迁移作业和步骤
 
-Jobs and steps in Azure Pipelines are very similar to jobs and steps in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics:
+Azure Pelines 中的作业和步骤非常类似于 {% data variables.product.prodname_actions %} 中的作业和步骤。 在这两个系统中，作业具有以下特征：
 
-* Jobs contain a series of steps that run sequentially.
-* Jobs run on separate virtual machines or in separate containers.
-* Jobs run in parallel by default, but can be configured to run sequentially.
+* 作业包含一系列按顺序运行的步骤。
+* 作业在单独的虚拟机或单独的容器中运行。
+* 默认情况下作业并行运行，但可以配置为按顺序运行。
 
-### Migrating script steps
+### 迁移脚本步骤
 
-You can run a script or a shell command as a step in a workflow. In Azure Pipelines, script steps can be specified using the `script` key, or with the `bash`, `powershell`, or `pwsh` keys. Scripts can also be specified as an input to the [Bash task](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops) or the [PowerShell task](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops).
+可以将脚本或 shell 命令作为工作流程中的步骤运行。 在 Azure Pipelines 中，脚本步骤可以使用 `script` 键指定，或者使用 `bash`、`powershell` 或 `pwsh` 键指定。 脚本也可以指定为 [Bash 任务](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops)或 [PowerShell 任务](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops)的输入。
 
-In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key. To select a particular shell, you can specify the `shell` key when providing the script. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+在 {% data variables.product.prodname_actions %} 中，所有脚本都使用 `run` 键来指定。 要选择特定的 shell，您可以在提供脚本时指定 `shell` 键。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -68,16 +69,16 @@ Azure Pipelines
 {% raw %}
 ```yaml
 jobs:
-- job: scripts
-  pool:
-    vmImage: 'windows-latest'
-  steps:
-  - script: echo "This step runs in the default shell"
-  - bash: echo "This step runs in bash"
-  - pwsh: Write-Host "This step runs in PowerShell Core"
-  - task: PowerShell@2
-    inputs:
-      script: Write-Host "This step runs in PowerShell"
+  - job: scripts
+    pool:
+      vmImage: 'windows-latest'
+    steps:
+      - script: echo "This step runs in the default shell"
+      - bash: echo "This step runs in bash"
+      - pwsh: Write-Host "This step runs in PowerShell Core"
+      - task: PowerShell@2
+        inputs:
+          script: Write-Host "This step runs in PowerShell"
 ```
 {% endraw %}
 </td>
@@ -88,32 +89,32 @@ jobs:
   scripts:
     runs-on: windows-latest
     steps:
-    - run: echo "This step runs in the default shell"
-    - run: echo "This step runs in bash"
-      shell: bash
-    - run: Write-Host "This step runs in PowerShell Core"
-      shell: pwsh
-    - run: Write-Host "This step runs in PowerShell"
-      shell: powershell
+      - run: echo "This step runs in the default shell"
+      - run: echo "This step runs in bash"
+        shell: bash
+      - run: Write-Host "This step runs in PowerShell Core"
+        shell: pwsh
+      - run: Write-Host "This step runs in PowerShell"
+        shell: powershell
 ```
 {% endraw %}
 </td>
 </tr>
 </table>
 
-### Differences in script error handling
+### 脚本错误处理中的差异
 
-In Azure Pipelines, scripts can be configured to error if any output is sent to `stderr`. {% data variables.product.prodname_actions %} does not support this configuration.
+在 Azure Pipelines 中，脚本可配置为有任何输出发送到 `stderr` 时出错。 {% data variables.product.prodname_actions %} 不支持此配置。
 
-{% data variables.product.prodname_actions %} configures shells to "fail fast" whenever possible, which stops the script immediately if one of the commands in a script exits with an error code. In contrast, Azure Pipelines requires explicit configuration to exit immediately on an error. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)."
+{% data variables.product.prodname_actions %} 尽可能将 shell 配置为“快速失败”，如果脚本中的一个命令退出并有错误代码，则会立即停止脚本。 相反，Azure Pipelines 需要明确配置为在出错时立即退出。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)”。
 
-### Differences in the default shell on Windows
+### Windows 上默认 shell 的差异
 
-In Azure Pipelines, the default shell for scripts on Windows platforms is the Command shell (_cmd.exe_). In {% data variables.product.prodname_actions %}, the default shell for scripts on Windows platforms is PowerShell. PowerShell has several differences in built-in commands, variable expansion, and flow control.
+在 Azure Pelines 中，Windows 平台上脚本的默认 shell 是命令 shell (_cmd.exe_)。 在 {% data variables.product.prodname_actions %} 中，Windows 平台上脚本的默认 shell 是 PowerShell 。 PowerShell 在内置命令、变量扩展和流控制方面存在若干差异。
 
-If you're running a simple command, you might be able to run a Command shell script in PowerShell without any changes. But in most cases, you will either need to update your script with PowerShell syntax or instruct {% data variables.product.prodname_actions %} to run the script with the Command shell instead of PowerShell. You can do this by specifying `shell` as `cmd`.
+如果您运行的是简单的命令，则可以在 PowerShell 中运行命令 shell 脚本，而无需进行任何更改。 但在大多数情况下，您需要使用 PowerShell 语法更新脚本，或者指示 {% data variables.product.prodname_actions %} 使用命令 shell 而不是 PowerShell 来运行脚本。 您可以通过将 `shell` 指定为 `Cmd` 来完成。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -129,11 +130,11 @@ Azure Pipelines
 {% raw %}
 ```yaml
 jobs:
-- job: run_command
-  pool:
-    vmImage: 'windows-latest'
-  steps:
-  - script: echo "This step runs in CMD on Windows by default"
+  - job: run_command
+    pool:
+      vmImage: 'windows-latest'
+    steps:
+      - script: echo "This step runs in CMD on Windows by default"
 ```
 {% endraw %}
 </td>
@@ -144,24 +145,24 @@ jobs:
   run_command:
     runs-on: windows-latest
     steps:
-    - run: echo "This step runs in PowerShell on Windows by default"
-    - run: echo "This step runs in CMD on Windows explicitly"
-      shell: cmd
+      - run: echo "This step runs in PowerShell on Windows by default"
+      - run: echo "This step runs in CMD on Windows explicitly"
+        shell: cmd
 ```
 {% endraw %}
 </td>
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)”。
 
-### Migrating conditionals and expression syntax
+### 迁移条件和表达式语法
 
-Azure Pipelines and {% data variables.product.prodname_actions %} can both run steps conditionally. In Azure Pipelines, conditional expressions are specified using the `condition` key. In {% data variables.product.prodname_actions %}, conditional expressions are specified using the `if` key.
+Azure Pipelines 和 {% data variables.product.prodname_actions %} 可以有条件地运行步骤。 在 Azure Pipelines 中，使用 `condition` 键指定条件表达式。 在 {% data variables.product.prodname_actions %} 中，条件表达式使用 `if` 键来指定。
 
-Azure Pipelines uses functions within expressions to execute steps conditionally. In contrast, {% data variables.product.prodname_actions %} uses an infix notation. For example, you must replace the `eq` function in Azure Pipelines with the `==` operator in {% data variables.product.prodname_actions %}.
+Azure Pelines 使用表达式中的函数来有条件地执行步骤。 相反，{% data variables.product.prodname_actions %} 使用 infix 表示法。 例如，必须将 Azure Pipelines 中的 `eq` 函数替换为 {% data variables.product.prodname_actions %} 中的 `==` 运算符。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -177,12 +178,12 @@ Azure Pipelines
 {% raw %}
 ```yaml
 jobs:
-- job: conditional
-  pool:
-    vmImage: 'ubuntu-latest'
-  steps:
-  - script: echo "This step runs with str equals 'ABC' and num equals 123"
-    condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123))
+  - job: conditional
+    pool:
+      vmImage: 'ubuntu-latest'
+    steps:
+      - script: echo "This step runs with str equals 'ABC' and num equals 123"
+        condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123))
 ```
 {% endraw %}
 </td>
@@ -193,21 +194,21 @@ jobs:
   conditional:
     runs-on: ubuntu-latest
     steps:
-    - run: echo "This step runs with str equals 'ABC' and num equals 123"
-      if: ${{ env.str == 'ABC' && env.num == 123 }}
+      - run: echo "This step runs with str equals 'ABC' and num equals 123"
+        if: ${{ env.str == 'ABC' && env.num == 123 }}
 ```
 {% endraw %}
 </td>
 </tr>
 </table>
 
-For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。
 
-### Dependencies between jobs
+### 作业之间的依赖关系
 
-Both Azure Pipelines and {% data variables.product.prodname_actions %} allow you to set dependencies for a job. In both systems, jobs run in parallel by default, but job dependencies can be specified explicitly. In Azure Pipelines, this is done with the `dependsOn` key. In {% data variables.product.prodname_actions %}, this is done with the `needs` key.
+Azure Pipelines 和 {% data variables.product.prodname_actions %} 允许您为作业设置依赖项。 在这两个系统中，默认情况下作业并行运行，但可以明确指定作业依赖项。 在 Azure Pipelines 中，这通过 `dependsOn` 键来完成。 在 {% data variables.product.prodname_actions %} 中，这通过 `needs` 键来完成。
 
-Below is an example of the syntax for each system. The workflows start a first job named `initial`, and when that job completes, two jobs named `fanout1` and `fanout2` will run. Finally, when those jobs complete, the job `fanin` will run.
+下面是每个系统的语法示例： 工作流程启动第一个名为 `initial` 的作业，当该作业完成时，两个分别名为 `fanout1` 和 `fanout2` 的作业将会运行。 最后，当这些作业完成后，作业 `fanin` 将会运行。
 
 <table class="d-block">
 <tr>
@@ -223,29 +224,29 @@ Azure Pipelines
 {% raw %}
 ```yaml
 jobs:
-- job: initial
-  pool:
-    vmImage: 'ubuntu-latest'
-  steps:
-  - script: echo "This job will be run first."
-- job: fanout1
-  pool:
-    vmImage: 'ubuntu-latest'
-  dependsOn: initial
-  steps:
-  - script: echo "This job will run after the initial job, in parallel with fanout2."
-- job: fanout2
-  pool:
-    vmImage: 'ubuntu-latest'
-  dependsOn: initial
-  steps:
-  - script: echo "This job will run after the initial job, in parallel with fanout1."
-- job: fanin:
-  pool:
-    vmImage: 'ubuntu-latest'
-  dependsOn: [fanout1, fanout2]
-  steps:
-  - script: echo "This job will run after fanout1 and fanout2 have finished."
+  - job: initial
+    pool:
+      vmImage: 'ubuntu-latest'
+    steps:
+      - script: echo "This job will be run first."
+  - job: fanout1
+    pool:
+      vmImage: 'ubuntu-latest'
+    dependsOn: initial
+    steps:
+      - script: echo "This job will run after the initial job, in parallel with fanout2."
+  - job: fanout2
+    pool:
+      vmImage: 'ubuntu-latest'
+    dependsOn: initial
+    steps:
+      - script: echo "This job will run after the initial job, in parallel with fanout1."
+  - job: fanin:
+    pool:
+      vmImage: 'ubuntu-latest'
+    dependsOn: [fanout1, fanout2]
+    steps:
+      - script: echo "This job will run after fanout1 and fanout2 have finished."
 ```
 {% endraw %}
 </td>
@@ -256,35 +257,35 @@ jobs:
   initial:
     runs-on: ubuntu-latest
     steps:
-    - run: echo "This job will be run first."
+      - run: echo "This job will be run first."
   fanout1:
     runs-on: ubuntu-latest
     needs: initial
     steps:
-    - run: echo "This job will run after the initial job, in parallel with fanout2."
+      - run: echo "This job will run after the initial job, in parallel with fanout2."
   fanout2:
     runs-on: ubuntu-latest
     needs: initial
     steps:
-    - run: echo "This job will run after the initial job, in parallel with fanout1."
+      - run: echo "This job will run after the initial job, in parallel with fanout1."
   fanin:
     runs-on: ubuntu-latest
     needs: [fanout1, fanout2]
     steps:
-    - run: echo "This job will run after fanout1 and fanout2 have finished."
+      - run: echo "This job will run after fanout1 and fanout2 have finished."
 ```
 {% endraw %}
 </td>
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。
 
-### Migrating tasks to actions
+### 将任务迁移到操作
 
-Azure Pipelines uses _tasks_, which are application components that can be re-used in multiple workflows. {% data variables.product.prodname_actions %} uses _actions_, which can be used to perform tasks and customize your workflow. In both systems, you can specify the name of the task or action to run, along with any required inputs as key/value pairs.
+Azure Pipelines 使用_任务_，这是可在多个工作流程中重复使用的应用程序组件。 {% data variables.product.prodname_actions %} 使用 _操作_，这可用于执行任务和自定义工作流程。 在这两个系统中，您可以指定要运行的任务或操作的名称，以及任何必需的输入作为键/值对。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table>
 <tr>
@@ -300,15 +301,15 @@ Azure Pipelines
 {% raw %}
 ```yaml
 jobs:
-- job: run_python
-  pool:
-    vmImage: 'ubuntu-latest'
-  steps:
-  - task: UsePythonVersion@0
-    inputs:
-      versionSpec: '3.7'
-      architecture: 'x64'
-  - script: python script.py
+  - job: run_python
+    pool:
+      vmImage: 'ubuntu-latest'
+    steps:
+      - task: UsePythonVersion@0
+        inputs:
+          versionSpec: '3.7'
+          architecture: 'x64'
+      - script: python script.py
 ```
 {% endraw %}
 </td>
@@ -319,15 +320,15 @@ jobs:
   run_python:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/setup-python@v2
-      with:
-        python-version: '3.7'
-        architecture: 'x64'
-    - run: python script.py
+      - uses: actions/setup-python@v2
+        with:
+          python-version: '3.7'
+          architecture: 'x64'
+      - run: python script.py
 ```
 {% endraw %}
 </td>
 </tr>
 </table>
 
-You can find actions that you can use in your workflow in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Creating actions](/actions/creating-actions)."
+您可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中找到可用于工作流程的操作，也可以创建自己的操作。 更多信息请参阅“[创建操作](/actions/creating-actions)”。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
index 1053ba2479..64269af290 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md
@@ -35,7 +35,7 @@ CircleCI 和 {% data variables.product.prodname_actions %} 都允许您创建能
 从 CircleCI 迁移时，考虑以下差异：
 
 - CircleCI 的自动测试并行性根据用户指定的规则或历史计时信息自动对测试进行分组。 此功能未内置于 {% data variables.product.prodname_actions %}。
-- 在 Docker 容器中执行的操作对权限问题很敏感，因为容器具有不同的用户映射。 您可以通过在 *Dockerfile* 中不使用 `USER` 指令来避免这些问题。 {% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+- 在 Docker 容器中执行的操作对权限问题很敏感，因为容器具有不同的用户映射。 您可以通过在 *Dockerfile* 中不使用 `USER` 指令来避免这些问题。 {% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}有关 {% data variables.product.product_name %} 托管的运行器上 Docker 文件系统的更多信息，请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。
 {% endif %}
 
@@ -445,7 +445,9 @@ jobs:
           path: vendor/bundle
           key: administrate-${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}
       - name: Install postgres headers
-        run: sudo apt-get install libpq-dev
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
       - name: Install dependencies
         run: bundle install --path vendor/bundle
       - name: Setup environment configuration
diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md
index 00ed3d3b03..9511299614 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -72,7 +72,7 @@ Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工
 | [Jenkins cron syntax](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)                                                                                                                                                                                                                                                           | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule)                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | [`阶段，暂存`](https://jenkins.io/doc/book/pipeline/syntax/#stage)                                                                                                                                                                                                                                                                             | [`jobs.<job_id>`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id) <br> [`jobs.<job_id>.name`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname)                                                                                                                                                                                                                                                                                                       |
 | [`tools`](https://jenkins.io/doc/book/pipeline/syntax/#tools)                                                                                                                                                                                                                                                                             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| {% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。{% else %}[{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software) | {% endif %}
+| {% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。{% else %}[{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software) | {% endif %}
 | [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input)                                                                                                                                                                                                                                                                             | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs)                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when)                                                                                                                                                                                                                                                                               | [`jobs.<job_id>.if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif)                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 
diff --git a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
index b1ee158971..329414a47c 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md
@@ -21,13 +21,13 @@ type: how_to
 
 ### 创建工作流程模板
 
-对组织的 `.github` 仓库具有写入权限的用户可以创建工作流程模板。 然后，有权限创建工作流程的组织成员便可使用这些模板。 工作流程模板可用于在组织的公共仓库中创建新的工作流程；要使用模板在私有仓库中创建工作流程，该组织必须是企业或 GitHub One 计划的一部分。
+对组织的 `.github` 仓库具有写入权限的用户可以创建工作流程模板。 然后，有权限创建工作流程的组织成员便可使用这些模板。 工作流程模板可用于在组织的公共仓库中创建新的工作流程；要使用模板在私有仓库中创建工作流程，该组织必须是企业计划的一部分。
 
 此过程展示如何创建工作流程模板和元数据文件。 元数据文件描述在用户新建工作流程时如何向其显示模板。
 
 1. 如果组织中没有名为 `.github` 的公共仓库，请新建一个。
-1. 创建一个名为 `workflow-templates` 的目录。
-1. 在 `workflow-templates` 目录中创建新的工作流程文件。
+2. 创建一个名为 `workflow-templates` 的目录。
+3. 在 `workflow-templates` 目录中创建新的工作流程文件。
 
    如果需要引用仓库的默认分支，可以使用 `$default-branch` 占位符。 使用模板创建工作流程时，占位符将自动替换为仓库默认分支的名称。
 
@@ -52,7 +52,7 @@ type: how_to
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-1. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名，但扩展名不是 `.yml`，而必须附加 `.properties.json`。 例如，下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据：
+4. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名，但扩展名不是 `.yml`，而必须附加 `.properties.json`。 例如，下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据：
    ```yaml
    {
        "name": "Octo Organization Workflow",
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..21d8278a4a
--- /dev/null
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,19 @@
+---
+title: 批准复刻中的工作流程运行
+intro: 当贡献者第一次向公共仓库提交拉取请求时，拥有写入权限的维护者必须批准任何工作流程运行。
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+---
+
+公共仓库的复刻可以提交拉取请求以提议对仓库的 {% data variables.product.prodname_actions %} 工作流程的更改。 虽然来自复刻的工作流程无法访问敏感数据（如密钥），但如果出于滥用目的进行修改，可能会让维护者感到烦恼。 为了帮助防止这种情况，从首次贡献者收到拉取请求的工作流程不会自动运行，而必须先获得批准。
+
+Maintainers with write access to the repository can use the following procedure to review and run workflows on pull requests from first-time contributors. After a contributor has at least one pull request merged into a project's repository, any future pull requests from that contributor's fork will automatically run workflows.
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
+1. If you are comfortable with running workflows on the pull request branch, return to the {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
+
+   ![Approve and run workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index b8f7ad18fd..12998d41d6 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: 禁用和启用工作流程
-intro: '您可以使用 {% data variables.product.prodname_dotcom %} 或 REST API 禁用和重新启用工作流程。'
+intro: '您可以使用 {% data variables.product.prodname_dotcom %} UI、REST API 或 {% data variables.product.prodname_cli %} 禁用并重新启用工作流程。'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -12,7 +12,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
-禁用工作流程允许您停止触发工作流程，而不必从仓库中删除文件。 您可以轻松地在 {% data variables.product.prodname_dotcom %} 上重新启用工作流程。 您也可以使用 REST API 禁用和启用工作流程。 更多信息请参阅“[操作 REST API](/rest/reference/actions#workflows)”。
+禁用工作流程允许您停止触发工作流程，而不必从仓库中删除文件。 您可以轻松地在 {% data variables.product.prodname_dotcom %} 上重新启用工作流程。
 
 在许多情况下，暂时禁用工作流程可能很有用。 以下是禁用工作流程可能有帮助的几个例子：
 
@@ -27,7 +27,9 @@ versions:
 
 {% endwarning %}
 
-### 禁用工作流程
+### 使用 {% data variables.product.prodname_dotcom %} UI 禁用和启用工作流程
+
+#### 禁用工作流程
 
 您可以手动禁用工作流程，使它不会执行任何工作流程运行。 禁用的工作流程不会删除，可以重新启用。
 
@@ -37,7 +39,7 @@ versions:
 1. 单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 ![操作烤肉串菜单](/assets/images/help/repository/actions-workflow-menu-kebab.png)
 1. 单击 **Disable workflow（禁用工作流程）**。 ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png) 禁用的工作流程标记为 {% octicon "stop" aria-label="The stop icon" %} 来表示其状态。 ![操作列表禁用的工作流程](/assets/images/help/repository/actions-find-disabled-workflow.png)
 
-### 启用工作流程
+#### 启用工作流程
 
 您可以重新启用以前禁用过的工作流程。
 
@@ -45,3 +47,23 @@ versions:
 {% data reusables.repositories.actions-tab %}
 1. 在左侧边栏中，单击您想要启用的工作流程。 ![操作选择禁用的工作流程](/assets/images/help/repository/actions-select-disabled-workflow.png)
 1. 单击 **Enable workflow（启用工作流程）**。 ![操作启用工作流程](/assets/images/help/repository/actions-enable-workflow.png)
+
+### 使用 {% data variables.product.prodname_cli %} 禁用和启用工作流程
+
+{% data reusables.actions.actions-cli %}
+
+要禁用工作流程，请使用 `workflow disable` 子命令。 将 `workflow` 替换为要禁用的工作流程的名称、ID 或文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
+
+```shell
+gh workflow disable <em>workflow</em>
+```
+
+要启用工作流程，请使用 `workflow enable` 子命令。 将 `workflow` 替换为要启用的工作流程的名称、ID 或文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
+
+```shell
+gh workflow enable <em>workflow</em>
+```
+
+### 通过 REST API 禁用和启用工作流程
+
+您也可以使用 REST API 禁用和启用工作流程。 更多信息请参阅“[操作 REST API](/rest/reference/actions#workflows)”。
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index ac9b1b6ca9..23b3b3c2d0 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -15,6 +15,8 @@ versions:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} 默认情况下，{% data variables.product.product_name %} 存储 90 天内的构建日志和构件，并且您可以根据仓库类型自定义此保留期。 更多信息请参阅“[配置 GitHub Actions 构件和日志在您的仓库中的保留期](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”。{% endif %}
 {% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} 存储 90 天的完整构建日志和构件。{% endif %}
 
+### 使用 {% data variables.product.prodname_dotcom %} UI 下载构件
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -27,3 +29,33 @@ versions:
     {% else %}
     ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
+
+### 使用 {% data variables.product.prodname_cli %} 下载构件
+
+{% data reusables.actions.actions-cli %}
+
+{% data variables.product.prodname_cli %} 将根据构件名称将每个构件下载到单独的目录中。 如果只指定了单个构件, 它将被提取到当前目录。
+
+要下载工作流程运行产生的所有构件，请使用 `run download` 子命令。 将 `run-id` 替换为您想要从中下载构件的运行的 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近的运行。
+
+```shell
+gh run download <em>run-id</em>
+```
+
+要从运行中下载特定的构件，请使用 `run download` 子命令。 将 `run-id` 替换为您想要从中下载构件的运行的 ID。 使用要下载的构件名称替换 `artifact-name`。
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name</em>
+```
+
+您可以指定多个构件。
+
+```shell
+gh run download <em>run-id</em> -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
+
+要从仓库的所有运行中下载特定的构件，请使用 `run download` 子命令。
+
+```shell
+gh run download -n <em>artifact-name-1</em> -n <em>artifact-name-2</em>
+```
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/index.md b/translations/zh-CN/content/actions/managing-workflow-runs/index.md
index 26463a2ae1..adc490a8a4 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/index.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/index.md
@@ -26,6 +26,7 @@ versions:
 {% link_in_list /manually-running-a-workflow %}
 {% link_in_list /re-running-a-workflow %}
 {% link_in_list /canceling-a-workflow %}
+{% link_in_list /approving-workflow-runs-from-public-forks %}
 {% link_in_list /reviewing-deployments %}
 {% link_in_list /disabling-and-enabling-a-workflow %}
 {% link_in_list /deleting-a-workflow-run %}
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index 68d4a35698..24714e6a9b 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -1,6 +1,6 @@
 ---
 title: 手动运行工作流程
-intro: '如果工作流程配置为在发生 `workflow_dispatch` 事件时运行，您可以使用 REST API 或从 Actions（操作）选项卡在 {% data variables.product.prodname_dotcom %} 上运行工作流程。'
+intro: '当工作流程配置为在发生 `workflow_dispatch` 事件时运行时，您可以使用 {% data variables.product.prodname_dotcom %}、{% data variables.product.prodname_cli %} 或 REST API 上的 Actions 选项卡运行工作流程。'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'
@@ -28,6 +28,40 @@ versions:
 1. 在工作流程运行列表上方选择 **Run workflow（运行工作流程）**。 ![操作工作流程调度](/assets/images/actions-workflow-dispatch.png)
 1. 选择工作流程将要运行的分支，并键入工作流程使用的输入参数。 单击 **Run workflow（运行工作流程）**。 ![操作手动运行工作流程](/assets/images/actions-manually-run-workflow.png)
 
+### 使用 {% data variables.product.prodname_cli %} 运行工作流程
+
+{% data reusables.actions.actions-cli %}
+
+要运行工作流程，请使用 `workflow run` 子命令。 将 `workflow` 参数替换为要运行的工作流程的名称、ID 或文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
+
+```shell
+gh workflow run <em>workflow</em>
+```
+
+如果您的工作流程接受输入，{% data variables.product.prodname_cli %} 将提示您输入它们。 或者，您可以使用 `-f` 或 `-F` 添加 `key=value` 格式的输入。 使用 `-F` 读取文件。
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+您也可以使用标准输入以 JSON 的身份传递输入。
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+要在仓库默认分支以外的分支上运行工作流程，请使用 `--ref` 标记。
+
+```shell
+gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+```
+
+要查看工作流程运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。
+
+```shell
+gh run watch
+```
+
 ### 使用 REST API 运行工作流程
 
 使用 REST API 时，应将 `inputs` 和 `ref` 配置为请求正文参数。 如果忽略输入，则使用工作流程文件中定义的默认值。
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md
index 6d5d20beb6..d06184df20 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md
@@ -12,6 +12,8 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### 使用 {% data variables.product.prodname_dotcom %} UI 重新运行工作流程
+
 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -19,3 +21,19 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单并选择 **Re-run all jobs（重新运行所有作业）**。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %}
+
+### 使用 {% data variables.product.prodname_cli %} 运行工作流程
+
+{% data reusables.actions.actions-cli %}
+
+要重新运行失败的工作流程运行，请使用 `run rerun` 子命令。 将 `run-id` 替换为您想要重新运行的已失败运行的 ID。  如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近失败的运行。
+
+```shell
+gh run rerun <em>run-id</em>
+```
+
+要查看工作流程运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。
+
+```shell
+gh run watch
+```
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index 8a0add5a2f..d2e64aefda 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -29,7 +29,7 @@ versions:
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 1. 在 **Artifacts（构件）**下，单击
-您要删除的构件旁边的 {% octicon "trashcan" aria-label="The trashcan icon" %}。
+您要删除的构件旁边的 {% octicon "trash" aria-label="The trash icon" %}。
     {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
  ![删除构件下拉菜单](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index d6ef98b540..1e443f91d4 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -107,3 +107,31 @@ versions:
 1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png)
 2. 要删除日志文件，单击 **Delete all logs（删除所有日志）**按钮并审查确认提示。 ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) 删除日志后，**Delete all logs（删除所有日志）**按钮将被删除，以表明工作流程运行中未剩下任何日志文件。
 {% endif %}
+
+### 使用 {% data variables.product.prodname_cli %} 查看日志
+
+{% data reusables.actions.actions-cli %}
+
+要查看特定作业的日志，请使用 `run view` 子命令。 将 `run-id` 替换为您想要查看其日志的运行的 ID。 {% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您从运行中选择作业。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，让您选择最近的运行，然后返回另一个交互式菜单，让您从运行中选择作业。
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+您也可以使用 `--bob` 标记来指定作业 ID。 将 `job-id` 替换为您想要查看其日志的作业的 ID。
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+您可以使用 `grep` 来搜索日志。 例如，此命令将返回所有包含单词 `error` 的日志条目。
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+要过滤日志中任何失败的步骤，请使用 `--log-fail` 而不是 `--log`。
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/viewing-workflow-run-history.md b/translations/zh-CN/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
index acfed50030..3313fde7c8 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/viewing-workflow-run-history.md
@@ -12,9 +12,67 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 {% data reusables.actions.ae-beta %}
 
+### 在 {% data variables.product.prodname_dotcom %} 上查看工作流程运行历史记录
+
 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
+
+### 使用 {% data variables.product.prodname_cli %} 查看工作流程运行历史记录
+
+{% data reusables.actions.actions-cli %}
+
+#### 查看最近的工作流程运行
+
+要列出最近的工作流程运行，请使用 `run list` 子命令。
+
+```shell
+gh run list
+```
+
+要指定返回的最大运行次数，您可以使用 `-L` 或 `--limit` 标记。 默认值为`10`.
+
+```shell
+gh run list --limit 5
+```
+
+要只返回为指定的工作流程的运行，您可以使用 `-w` 或 `--workflow` 标记。  将 `workflow` 替换为工作流名称、工作流程 ID 或工作流程文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+#### 查看特定工作流程运行的详细信息
+
+要显示特定工作流程运行的详细信息，请使用 `run view` 子命令。 将 `run-id` 替换为您想要查看的运行的 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近的运行。
+
+```shell
+gh run view <em>run-id</em>
+```
+
+要在输出中包括作业步骤，请使用 `-v` 或 `--verbose` 标记。
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+要查看运行中特定作业的详细信息，请使用 `-j` 或 `--job` 标记。  将 `job-id` 替换为您想要查看的作业的 ID。
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+要查看作业的完整日志，请使用 `--log` 标记。
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+如果运行失败，请使用 `--exit-status` 标记以非零状态退出。 例如：
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md
index 96eb0cc1ea..95d5b88de5 100644
--- a/translations/zh-CN/content/actions/quickstart.md
+++ b/translations/zh-CN/content/actions/quickstart.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Actions 快速入门
-intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
+intro: '在 5 分钟或更短的时间内尝试 {% data variables.product.prodname_actions %} 的功能。'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates
@@ -19,14 +19,14 @@ topics:
 
 ### 简介
 
-You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}.
+您只需要 {% data variables.product.prodname_dotcom %} 仓库来创建和运行 {% data variables.product.prodname_actions %} 工作流程。 在本指南中，您将添加一个工作流程，演示 {% data variables.product.prodname_actions %} 的一些基本功能。
 
-The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository.
+下面的示例显示 {% data variables.product.prodname_actions %} 作业如何自动触发、在哪里运行及其如何与仓库中的代码交互。
 
 ### 创建第一个工作流程
 
 1. 从 {% data variables.product.prodname_dotcom %} 上的仓库，在 `.github/workflows` 目录中创建一个名为 `github-actions-demo.yml` 的新文件。 更多信息请参阅“[创建新文件](/github/managing-files-in-a-repository/creating-new-files)”。
-2. Copy the following YAML contents into the `github-actions-demo.yml` file:
+2. 将以下 YAML 内容复制到 `github-actions-demo.yml` 文件中：
     {% raw %}
     ```yaml{:copy}
     name: GitHub Actions Demo
@@ -51,7 +51,7 @@ The following example shows you how {% data variables.product.prodname_actions %
     {% endraw %}
 3. 滚动到页面底部，然后选择 **Create a new branch for this commit and start a pull request（为此提交创建一个新分支并开始拉取请求）**。 然后，若要创建拉取请求，请单击 **Propose new file（提议新文件）**。 ![提交工作流程文件](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
 
-Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
+向仓库的分支提交工作流程文件会触发 `push` 事件并运行工作流程。
 
 ### 查看工作流程结果
 
@@ -63,14 +63,14 @@ Committing the workflow file to a branch in your repository triggers the `push`
 1. 从工作流程运行列表中，单击要查看的运行的名称。
 
    ![工作流程运行的名称](/assets/images/help/repository/actions-quickstart-run-name.png)
-1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
+1. 在 **Jobs（作业）**下，单击 **Explore-GitHub-Actions** 作业。
 
-   ![Locate job](/assets/images/help/repository/actions-quickstart-job.png)
-1. The log shows you how each of the steps was processed. Expand any of the steps to view its details.
+   ![查找作业](/assets/images/help/repository/actions-quickstart-job.png)
+1. 日志显示每个步骤的处理方式。 展开任何步骤以查看其细节。
 
-   ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png)
+   ![示例工作流程结果](/assets/images/help/repository/actions-quickstart-logs.png)
 
-   For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png)
+   例如，您可以在仓库中看到文件列表： ![示例操作详细信息](/assets/images/help/repository/actions-quickstart-log-detail.png)
 
 ### 更多工作流程模板
 
@@ -78,12 +78,12 @@ Committing the workflow file to a branch in your repository triggers the `push`
 
 ### 后续步骤
 
-The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}:
+每次将代码推送到分支时，您刚刚添加的示例工作流程都会运行，并显示 {% data variables.product.prodname_actions %} 如何处理仓库的内容。 但是，这只是您可以对 {% data variables.product.prodname_actions %} 执行操作的开始：
 
 - 您的仓库可以包含多个基于不同事件触发不同任务的工作流程。
-- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
+- 您可以使用工作流程安装软件测试应用程序，并让它们自动在 {% data variables.product.prodname_dotcom %} 的运行器上测试您的代码。
 
 {% data variables.product.prodname_actions %} 可以帮助您自动执行应用程序开发过程的几乎每个方面。 准备好开始了吗？ 以下是一些帮助您对 {% data variables.product.prodname_actions %} 执行后续操作的有用资源：
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
-- "[Guides](/actions/guides)" for specific uses cases and examples.
+- “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，以获取深入教程
+- “[指南](/actions/guides)”，以获取特定用例和示例
diff --git a/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md b/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md
index e05e81fbec..b9ff9bff80 100644
--- a/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md
+++ b/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md
@@ -28,44 +28,58 @@ versions:
 
 ### 在工作流程中使用 `GITHUB_TOKEN`
 
-要使用 `GITHUB_TOKEN` 密码，必须在工作流程文件中引用它。 使用令牌可能包括将令牌作为输入传递给需要该令牌的操作，或进行经过身份验证的 {% data variables.product.prodname_dotcom %} API 调用。
+您可以使用标准语法引用密钥以使用 `GITHUB_TOKEN`：{%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}。 使用 `GITHUB_TOKEN` 的示例包括将令牌作为操作的输入，或使用它来建立验证的 {% data variables.product.prodname_dotcom %} API 请求。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+{% note %}
+
+**重要：**即使工作流程没有明确将 `GITHUB_TOKEN` 传递到操作，操作也可以通过 `github.token` 上下文访问 `GITHUB_TOKEN` 。 作为一种良好的安全做法，您应该始终通过限制授予 `GITHUB_TOKEN` 的权限，确保操作只有所需的最低访问权限。 更多信息请参阅“[`GITHUB_TOKEN`](#permissions-for-the-github_token) 的权限”。
+
+{% endnote %}
+{% endif %}
 
 {% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
-#### 将 `GITHUB_TOKEN` 作为输入传递的示例
+#### 示例 1：将 `GITHUB_TOKEN` 作为输入传递
 
 此示例工作流程使用[贴标器操作](https://github.com/actions/labeler)，需要 `GITHUB_TOKEN` 作为 `repo-token` 输入参数的值：
 
-  {% raw %}
-  ```yaml
-  name: Pull request labeler
-  on:
-  - pull_request_target
-  jobs:
-    triage:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Pull request labeler
+
+on: [ pull_request_target ]
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
       - uses: actions/labeler@v2
         with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-  ```
-  {% endraw %}
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
 
-#### 调用 REST API 的示例
+#### 例2：调用 REST API
 
 您可以使用 `GITHUB_TOKEN` 进行经过验证的 API 调用。 此示例工作流程使用 {% data variables.product.prodname_dotcom %} REST API 创建议题：
 
-  {% raw %}
-  ```yaml
-  name: Create issue on commit
-  on:
-  - push
-  jobs:
-    create_commit:
-      runs-on: ubuntu-latest
-      steps:
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_commit:
+    runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      issues: write {% endif %}
+    steps:
       - name: Create issue using REST API
-        run: |
+        run: {% raw %}
           curl --request POST \
           --url https://api.github.com/repos/${{ github.repository }}/issues \
           --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
@@ -74,15 +88,31 @@ versions:
             "title": "Automated issue for commit: ${{ github.sha }}",
             "body": "This issue was automatically created by the GitHub Action workflow **${{ github.workflow }}**. \n\n 提交哈希是： _${{ github.sha }}_"
             }' \
-          --fail
-  ```
-  {% endraw %}
+          --fail{% endraw %}
+```
 
 ### `GITHUB_TOKEN` 的权限
 
 有关 {% data variables.product.prodname_github_apps %} 可通过各种权限访问的 API 端点的信息，请参阅“[{% data variables.product.prodname_github_app %} 权限](/rest/reference/permissions-required-for-github-apps)”。
 
-| 权限   | 访问类型 | 通过复刻的仓库访问 |
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+下表显示默认情况下授予 `GITHUB_TOKEN` 的权限。 拥有企业、组织或仓库管理员权限的人员可以将默认权限设置为允许或限制。 有关如何为您的企业、组织或仓库设置 `GITHUB_TOKEN` 的默认权限的信息，请参阅“[在企业帐户中执行 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)”、“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/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)”或“[禁用或限制仓库的 {% data variables.product.prodname_actions %}](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)”。
+
+| 作用域  | 默认访问<br>（允许） | 默认访问<br>（限制） | 复刻的仓库的最大访问权限<br> |
+| ---- | ------------------ | ------------------ | ---------------------- |
+| 操作   | 读/写                | 无                  | 读取                     |
+| 检查   | 读/写                | 无                  | 读取                     |
+| 内容   | 读/写                | 读取                 | 读取                     |
+| 部署   | 读/写                | 无                  | 读取                     |
+| 议题   | 读/写                | 无                  | 读取                     |
+| 元数据  | 读取                 | 读取                 | 读取                     |
+| 包    | 读/写                | 无                  | 读取                     |
+| 拉取请求 | 读/写                | 无                  | 读取                     |
+| 仓库项目 | 读/写                | 无                  | 读取                     |
+| 安全事件 | 读/写                | 无                  | 读取                     |
+| 状态   | 读/写                | 无                  | 读取                     |
+{% else %}
+| 作用域  | 访问类型 | 通过复刻的仓库访问 |
 | ---- | ---- | --------- |
 | 操作   | 读/写  | 读取        |
 | 检查   | 读/写  | 读取        |
@@ -94,9 +124,32 @@ versions:
 | 拉取请求 | 读/写  | 读取        |
 | 仓库项目 | 读/写  | 读取        |
 | 状态   | 读/写  | 读取        |
+{% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+#### 修改 `GITHUB_TOKEN` 的权限
+
+您可以在个别工作流程文件中修改 `GITHUB_TOKENN` 的权限。 如果 `GITHUB_TOKEN` 的默认权限是限制的，您可能需要提高权限以允许一些操作和命令成功运行。 如果默认权限是允许的，您可以编辑工作流程文件以从 `GITHUB_TOKEN` 中删除某些权限。 作为一种良好的安全做法，您应该授予 `GITHUB_TOKEN` 所需的最小访问权限。
+
+您可以在工作流程运行日志的“设置作业”部分看到 `GITHUB_TOKEN` 对于特定作业的权限。 更多信息请参阅“[使用工作流程运行日志](/actions/managing-workflow-runs/using-workflow-run-logs)”。
+
+您可以在工作流文件中使用 `permissions` 键来修改 `GITHUB_TOKEN` 对于整个工作流或单个作业的权限。 这允许您为工作流程或作业配置所需的最小权限。 使用 `permissions` 键时，所有未指定的权限都设置为没有访问权限，`metadata`范围除外，该范围总是获得读取访问。
+
+{% data reusables.github-actions.forked-write-permission %}
+
+本文前面的两个工作流程示例显示了在工作流程级别和作业级别使用的 `permissions` 键。 在[例 1](#example-1-passing-the-github_token-as-an-input) 中，为整个工作流程指定了两个权限。 在[示例 2](#example-2-calling-the-rest-api) 中，为单个作业的单一范围授予写入访问权限。
+
+有关 `permissions` 键的完整详情，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#permissions)”。
+
+##### 如何计算工作流程作业的权限
+
+`GITHUB_TOKEN` 的权限最初设置为企业、组织或仓库的默认设置。 如果默认设置为这些级别中任何级别的限制权限，这将适用于相关的仓库。 例如，如果您在组织级别选择受限制的默认值，则该组织中的所有仓库将使用限制的权限作为默认值。 然后根据工作流程文件中的任何配置（首先在工作流程级别，然后在作业级别）对权限进行调整。 最后，如果工作流程是由复刻的仓库中的拉取请求触发，并且未选择**从拉取请求发送写入令牌到工作流程**设置，则权限调整为将任何写入权限更改为只读。
+
+#### 授予额外权限
+{% endif %}
+
 如果您需要的令牌需要 `GITHUB_TOKEN` 中未提供的权限，您可以创建个人访问令牌并将其设置为仓库中的密码：
 
 1. 使用或创建具有该仓库适当权限的令牌。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
diff --git a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index bcd0531939..746ea663ce 100644
--- a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -60,7 +60,7 @@ env:
 | 上下文名称      | 类型   | 描述                                                                                                                                  |
 | ---------- | ---- | ----------------------------------------------------------------------------------------------------------------------------------- |
 | `github`   | `对象` | 工作流程运行的相关信息。 更多信息请参阅 [`github` 上下文](#github-context)。                                                                               |
-| `env`      | `对象` | 包含工作流程、作业或步骤中设置的环境变量。 更多信息请参阅 [`env` 上下文](#env-context)。                                                                            |
+| `env`      | `对象` | 包含工作流程、作业或步骤中设置的环境变量。 For more information, see [`env` context](#env-context).                                                      |
 | `作业`       | `对象` | 当前执行的作业相关信息。 更多信息请参阅 [`job` 上下文](#job-context)。                                                                                     |
 | `steps`    | `对象` | 此作业中已经运行的步骤的相关信息。 更多信息请参阅 [`steps` 上下文](#steps-context)。                                                                            |
 | `runner`   | `对象` | 运行当前作业的运行程序相关信息。 更多信息请参阅 [`runner` 上下文](#runner-context)。                                                                           |
@@ -93,11 +93,11 @@ env:
 | `github.action`           | `字符串` | 正在运行的操作的名称。 在当前步骤运行脚本时，{% data variables.product.prodname_dotcom %} 删除特殊字符或使用名称 `run`。  如果在同一作业中多次使用相同的操作，则名称将包括带有序列号的后缀。  例如，运行的第一个脚本名称为 `run1`，则第二个脚本将命名为 `run2`。 同样，`actions/checkout` 第二次调用时将变成 `actionscheckout2`。 |
 | `github.action_path`      | `字符串` | 您的操作所在的路径。 您可以使用此路径轻松访问与操作位于同一仓库中的文件。 此属性仅在复合运行步骤操作中才受支持。                                                                                                                                                               |
 | `github.actor`            | `字符串` | 发起工作流程运行的用户的登录名。                                                                                                                                                                                                        |
-| `github.base_ref`         | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 时才可用。                                                                                                                                                   |
+| `github.base_ref`         | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                           |
 | `github.event`            | `对象`  | 完整事件 web 挂钩有效负载。 更多信息请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows/)”。 您可以使用上下文访问事件的个别属性。                                                                                                                     |
 | `github.event_name`       | `字符串` | 触发工作流程运行的事件的名称。                                                                                                                                                                                                         |
 | `github.event_path`       | `字符串` | 运行器上完整事件 web 挂钩有效负载的路径。                                                                                                                                                                                                 |
-| `github.head_ref`         | `字符串` | 工作流程运行中拉取请求的 `head_ref` 或来源分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 时才可用。                                                                                                                                                   |
+| `github.head_ref`         | `字符串` | 工作流程运行中拉取请求的 `head_ref` 或来源分支。 This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`.                                                           |
 | `github.job`              | `字符串` | 当前作业的 [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。                                                                                                                                     |
 | `github.ref`              | `字符串` | 触发工作流程的分支或标记参考。 对于分支，使用格式 `refs/heads/<branch_name>`，对于标记是 `refs/tags/<tag_name>`。                                                                                                                          |
 | `github.repository`       | `字符串` | 所有者和仓库名称。 例如 `Codertocat/Hello-World`。                                                                                                                                                                                  |
@@ -158,7 +158,7 @@ env:
 | ------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `runner.os`         | `字符串` | 执行作业的运行器的操作系统。 可能的值为 `Linux`、`Windows` 或 `macOS`。                                                                                                                                      |
 | `runner.temp`       | `字符串` | 运行器临时目录的路径。 此目录保证在每个作业开始时为空，即使在自托管的运行器上也是如此。                                                                                                                                           |
-| `runner.tool_cache` | `字符串` | {% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。 |
+| `runner.tool_cache` | `字符串` | {% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。 |
 {% else %}包含 {% data variables.product.prodname_dotcom %} 托管运行器一些预安装工具的目录路径。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。 {% endif %}
 
 #### `needs` 上下文
@@ -381,15 +381,15 @@ jobs:
     outputs:
       matrix: ${{ steps.set-matrix.outputs.matrix }}
     steps:
-    - id: set-matrix
-      run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+      - id: set-matrix
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
   job2:
     needs: job1
     runs-on: ubuntu-latest
     strategy:
       matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
     steps:
-    - run: build
+      - run: build
 ```
 {% endraw %}
 
@@ -408,9 +408,9 @@ jobs:
   job1:
     runs-on: ubuntu-latest
     steps:
-    - continue-on-error: ${{ fromJSON(env.continue) }}
-      timeout-minutes: ${{ fromJSON(env.time) }}
-      run: echo ...
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
 ```
 {% endraw %}
 
diff --git a/translations/zh-CN/content/actions/reference/encrypted-secrets.md b/translations/zh-CN/content/actions/reference/encrypted-secrets.md
index 35a08f867a..825581a7b4 100644
--- a/translations/zh-CN/content/actions/reference/encrypted-secrets.md
+++ b/translations/zh-CN/content/actions/reference/encrypted-secrets.md
@@ -1,6 +1,6 @@
 ---
-title: Encrypted secrets
-intro: 'Encrypted secrets allow you to store sensitive information in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environments{% else %} or repository{% endif %}.'
+title: 加密机密
+intro: '加密密码可让您将敏感信息存储在您的组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、仓库或者仓库环境{% else %} 或仓库{% endif %} 中。'
 product: '{% data reusables.gated-features.actions %}'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
@@ -15,113 +15,118 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.environments-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### About encrypted secrets
+### 关于加密密码
 
-Secrets are encrypted environment variables that you create in an organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environment{% else %} or repository{% endif %}. The secrets that you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to help ensure that secrets are encrypted before they reach {% data variables.product.prodname_dotcom %} and remain encrypted until you use them in a workflow.
+机密是您在组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、仓库或者仓库环境{% else %} 或仓库{% endif %} 中创建的加密环境变量。 您创建的机密可用于 {% data variables.product.prodname_actions %} 工作流程。 在机密到达 {% data variables.product.prodname_dotcom %} 之前，{% data variables.product.prodname_dotcom %} 使用 [libsodium 密封盒](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)对机密加密，并且在您于工作流程中使用它们之前一直保持加密状态。
 
 {% data reusables.github-actions.secrets-org-level-overview %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers.
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+对于存储在环境级别的机密，您可以启用所需的审查者来控制对机密的访问。 在必要的审查者授予批准之前，工作流程作业无法访问环境机密。
 {% endif %}
 
-#### Naming your secrets
+#### 命名您的密码
 
-The following rules apply to secret names:
+{% data reusables.codespaces.secrets-naming %}. 例如，{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}在环境级别创建的机密必须在环境中具有唯一的名称，{% endif %}在仓库级别创建的机密必须在该仓库中具有唯一的名称，而在组织级别创建的机密必须在该级别具有独特的名称。
 
-* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
-* Secret names must not start with the `GITHUB_` prefix.
-* Secret names must not start with a number.
-* Secret names are not case-sensitive.
-* Secret names must be unique at the level they are created at. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. 
-  
-  If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
+  {% data reusables.codespaces.secret-precedence %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
 
-To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs.
+为帮助确保 {% data variables.product.prodname_dotcom %} 在日志中编写密码，请勿将结构化数据用作密码的值。 例如，避免创建包含 JSON 或编码 Git blob 的密码。
 
-#### Accessing your secrets
+#### 访问您的密码
 
-To make a secret available to an action, you must set the secret as an input or environment variable in the workflow file. Review the action's README file to learn about which inputs and environment variables the action expects. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)."
+为使密码用于操作，必须将密码设置为工作流程文件中的输入或环境变量。 查看操作的自述文件以了解操作预期的输入和环境变量。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)”。
 
-You can use and read encrypted secrets in a workflow file if you have access to edit the file. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
+如果您拥有编辑文件的权限，便可在工作流程文件中使用和读取加密密码。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/github/getting-started-with-github/access-permissions-on-github)”。
 
 {% warning %}
 
-**Warning:** {% data variables.product.prodname_dotcom %} automatically redacts secrets printed to the log, but you should avoid printing secrets to the log intentionally.
+**警告：**{% data variables.product.prodname_dotcom %} 自动将密码编写到日志，但您应避免有意将密码打印到日志。
 
 {% endwarning %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+当工作流程运行排队时读取组织和仓库机密，在引用环境的作业开始时读取环境机密。
 {% endif %}
 
-You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)."
+您还可以使用 REST API 管理密码。 更多信息请参阅“[密码](/rest/reference/actions#secrets)”。
 
-#### Limiting credential permissions
+#### 限制凭据权限
 
-When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary.
+生成凭据时，建议尽可能授予最低的权限。 例如，不使用个人凭据，而使用[部署密钥](/developers/overview/managing-deploy-keys#deploy-keys)或服务帐户。 请考虑授予只读权限（如果这是所需的全部权限）并尽可能限制访问。 生成个人访问令牌 (PAT) 时，选择所需的最小范围。
 
-### Creating encrypted secrets for a repository
+### 为仓库创建加密密码
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-secret %}
-1. Click **New repository secret**.
-1. Type a name for your secret in the **Name** input box.
-1. Enter the value for your secret.
-1. Click **Add secret**.
+1. 单击 **New repository secret（新仓库机密）**。
+1. 在 **Name（名称）**输入框中键入密码的名称。
+1. 输入密码的值。
+1. 单击 **Add secret（添加密码）**。
 
-If your repository {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
+如果您的仓库 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0"or currentVersion == "github-ae@latest" %}拥有环境机密或 {% endif %}可以访问父组织中的机密，则这些机密也会列入本页。
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-### Creating encrypted secrets for an environment
+{% note %}
+
+**注意：**具有协作员权限的用户可以使用 REST API 来管理仓库的机密。 更多信息请参阅“[{% data variables.product.prodname_actions %} 密码 API](/rest/reference/actions#secrets)”。
+
+{% endnote %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+
+### 为环境创建加密密码
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-1. Click on the environment that you want to add a secret to.
-1. Under **Environment secrets**, click **Add secret**.
-1. Type a name for your secret in the **Name** input box.
-1. Enter the value for your secret.
-1. Click **Add secret**.
+1. 单击要向其添加机密的环境。
+1. 在 **Environment secrets（环境机密）**下，单击 **Add secret（添加机密）**。
+1. 在 **Name（名称）**输入框中键入密码的名称。
+1. 输入密码的值。
+1. 单击 **Add secret（添加密码）**。
 {% endif %}
 
-### Creating encrypted secrets for an organization
+### 为组织创建加密密码
 
-When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
 
 {% data reusables.github-actions.permissions-statement-secrets-organization %}
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.sidebar-secret %}
-1. Click **New organization secret**.
-1. Type a name for your secret in the **Name** input box.
-1. Enter the **Value** for your secret.
-1. From the **Repository access** dropdown list, choose an access policy.
-1. Click **Add secret**.
+1. 单击 **New organization secret（新组织机密）**。
+1. 在 **Name（名称）**输入框中键入密码的名称。
+1. 输入密码的 **Value（值）**。
+1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。
+1. 单击 **Add secret（添加密码）**。
 
-### Reviewing access to organization-level secrets
+### 审查对组织级别密码的访问权限
 
-You can check which access policies are being applied to a secret in your organization.
+您可以检查哪些访问策略正被应用于组织中的密码。
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.sidebar-secret %}
-1. The list of secrets includes any configured permissions and policies. For example:
-![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
-1. For more details on the configured permissions for each secret, click **Update**.
+1. 密码列表包括任何已配置的权限和策略。 例如： ![密码列表](/assets/images/help/settings/actions-org-secrets-list.png)
+1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。
 
-### Using encrypted secrets in a workflow
+### 在工作流程中使用加密密码
 
-{% data reusables.actions.forked-secrets %}
+{% note %}
 
-To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+**注：**{% data reusables.actions.forked-secrets %}
+
+{% endnote %}
+
+要提供以密码作为输入或环境变量的操作，可以使用 `secrets` 上下文访问您在仓库中创建的密码。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”和“[{% data variables.product.prodname_actions %} 的工作流程语法](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
 
 {% raw %}
 ```yaml
@@ -134,11 +139,11 @@ steps:
 ```
 {% endraw %}
 
-Avoid passing secrets between processes from the command line, whenever possible. Command-line processes may be visible to other users (using the `ps` command) or captured by [security audit events](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). To help protect secrets, consider using environment variables, `STDIN`, or other mechanisms supported by the target process.
+尽可能避免使用命令行在进程之间传递密码。 命令行进程可能对其他用户可见（使用 `ps` 命令）或通过[安全审计事件](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing)获取。 为帮助保护密码，请考虑使用环境变量 `STDIN` 或目标进程支持的其他机制。
 
-If you must pass secrets within a command line, then enclose them within the proper quoting rules. Secrets often contain special characters that may unintentionally affect your shell. To escape these special characters, use quoting with your environment variables. For example:
+如果必须在命令行中传递密码，则将它们包含在适当的引用规则中。 密码通常包含可能意外影响 shell 的特殊字符。 要转义这些特殊字符，请引用环境变量。 例如：
 
-#### Example using Bash
+#### 使用 Bash 的示例
 
 {% raw %}
 ```yaml
@@ -151,7 +156,7 @@ steps:
 ```
 {% endraw %}
 
-#### Example using PowerShell
+#### 使用 PowerShell 的示例
 
 {% raw %}
 ```yaml
@@ -164,7 +169,7 @@ steps:
 ```
 {% endraw %}
 
-#### Example using Cmd.exe
+#### 使用 Cmd.exe 的示例
 
 {% raw %}
 ```yaml
@@ -177,31 +182,31 @@ steps:
 ```
 {% endraw %}
 
-### Limits for secrets
+### 密码的限制
 
-You can store up to 1,000 secrets per organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, 100 secrets per repository, and 100 secrets per environment{% else %} and 100 secrets per repository{% endif %}. A workflow may use up to 100 organization secrets and 100 repository secrets.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Additionally, a job referencing an environment may use up to 100 environment secrets.{% endif %}
+最多可以每个组织存储 1,000 条机密{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}，每个仓库存储 100 条机密，每个环境存储 100 条机密{% else %}，每个仓库存储 100 条机密{% endif %}。 一个工作流程最多可以使用 100 条组织机密和 100 条仓库机密。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 此外，引用环境的作业最多可以使用 100 条环境机密。{% endif %}
 
-Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB, you can store encrypted secrets in your repository and save the decryption passphrase as a secret on {% data variables.product.prodname_dotcom %}. For example, you can use `gpg` to encrypt your credentials locally before checking the file in to your repository on {% data variables.product.prodname_dotcom %}. For more information, see the "[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)."
+密码大小限于 64 KB。 要使用大于 64 KB 的密码，可以将加密的密码存储在仓库中，并将解密短语在 {% data variables.product.prodname_dotcom %} 上存储为密码。 例如，在将文件检入您在 {% data variables.product.prodname_dotcom %} 上的仓库之前，可以使用 `gpg` 在本地对您的凭据加密。 更多信息请参阅“[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)”。
 
 {% warning %}
 
-**Warning**: Be careful that your secrets do not get printed when your action runs. When using this workaround, {% data variables.product.prodname_dotcom %} does not redact secrets that are printed in logs.
+**警告**：请注意，您的密码在操作运行时不会印出。 使用此解决方法时，{% data variables.product.prodname_dotcom %} 不会编写日志中印出的密码。
 
 {% endwarning %}
 
-1. Run the following command from your terminal to encrypt the `my_secret.json` file using `gpg` and the AES256 cipher algorithm.
+1. 从终端运行以下命令，以使用 `gpg` 和 AES256 密码算法对 `my_secret.json` 文件加密。
 
  ``` shell
  $ gpg --symmetric --cipher-algo AES256 my_secret.json
  ```
 
-1. You will be prompted to enter a passphrase. Remember the passphrase, because you'll need to create a new secret on {% data variables.product.prodname_dotcom %} that uses the passphrase as the value.
+1. 将会提示您输入密码短语。 请记住该密码短语，因为需要在使用该密码短语作为值的 {% data variables.product.prodname_dotcom %} 上创建新密码。
 
-1. Create a new secret that contains the passphrase. For example, create a new secret with the name `LARGE_SECRET_PASSPHRASE` and set the value of the secret to the passphrase you selected in the step above.
+1. 创建包含密码短语的新密码。 例如，使用名称 `LARGE_SECRET_PASSPHRASE` 创建新密码，并将密码的值设为上一步所选的密码短语。
 
-1. Copy your encrypted file into your repository and commit it. In this example, the encrypted file is `my_secret.json.gpg`.
+1. 将加密的文件复制到仓库并提交。 在本例中，加密的文件是 `my_secret.json.gpg`。
 
-1. Create a shell script to decrypt the password. Save this file as `decrypt_secret.sh`.
+1. 创建 shell 脚本对密码解密。 将此文件另存为 `decrypt_secret.sh`。
 
   ``` shell
   #!/bin/sh
@@ -214,7 +219,7 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB,
   --output $HOME/secrets/my_secret.json my_secret.json.gpg
   ```
 
-1. Ensure your shell script is executable before checking it in to your repository.
+1. 确保 shell 脚本在检入仓库之前可执行。
 
   ``` shell
   $ chmod +x decrypt_secret.sh
@@ -223,7 +228,7 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB,
   $ git push
   ```
 
-1. From your workflow, use a `step` to call the shell script and decrypt the secret. To have a copy of your repository in the environment that your workflow runs in, you'll need to use the [`actions/checkout`](https://github.com/actions/checkout) action. Reference your shell script using the `run` command relative to the root of your repository.
+1. 从工作流程使用 `step` 调用 shell 脚本并对密码解密。 要在工作流程运行的环境中创建仓库的副本，需要使用 [`actions/checkout`](https://github.com/actions/checkout) 操作。 使用与仓库根目录相关的 `run` 命令引用 shell 脚本。
 
 {% raw %}
   ```yaml
diff --git a/translations/zh-CN/content/actions/reference/environment-variables.md b/translations/zh-CN/content/actions/reference/environment-variables.md
index a0bd076287..454980cd2d 100644
--- a/translations/zh-CN/content/actions/reference/environment-variables.md
+++ b/translations/zh-CN/content/actions/reference/environment-variables.md
@@ -58,6 +58,7 @@ jobs:
 | `GITHUB_RUN_NUMBER`  | {% data reusables.github-actions.run_number_description %}
 | `GITHUB_JOB`         | 当前作业的 [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。                                                                                                                                                 |
 | `GITHUB_ACTION`      | 操作唯一的标识符 (`id`)。                                                                                                                                                                                                                  |
+| `GITHUB_ACTION_PATH` | 您的操作所在的路径。 You can use this path to access files located in the same repository as your action. This variable is only supported in composite run steps actions.                                                                   |
 | `GITHUB_ACTIONS`     | 当 {% data variables.product.prodname_actions %} 运行工作流程时，始终设置为 `true`。 您可以使用此变量来区分测试是在本地运行还是通过 {% data variables.product.prodname_actions %} 运行。                                                                                   |
 | `GITHUB_ACTOR`       | 发起工作流程的个人或应用程序的名称。 例如 `octocat`。                                                                                                                                                                                                  |
 | `GITHUB_REPOSITORY`  | 所有者和仓库名称。 例如 `octocat/Hello-World`。                                                                                                                                                                                               |
@@ -68,9 +69,9 @@ jobs:
 | `GITHUB_REF`         | 触发工作流程的分支或标记参考。 例如 `refs/heads/feature-branch-1`。 如果分支或标记都不适用于事件类型，则变量不会存在。                                                                                                                                                       |
 | `GITHUB_HEAD_REF`    | 仅为拉取请求事件设置。 头部分支的名称。                                                                                                                                                                                                              |
 | `GITHUB_BASE_REF`    | 仅为拉取请求事件设置。 基础分支的名称。                                                                                                                                                                                                              |
-| `GITHUB_SERVER_URL`  | 返回 {% data variables.product.product_name %} 服务器的 URL。 当 {% data variables.product.prodname_actions %} 运行工作流程时，始终设置为 `true`。                                                                                                    |
-| `GITHUB_API_URL`     | 返回 API URL。 返回 {% data variables.product.product_name %} 服务器的 URL。 例如：`https://github.com`。                                                                                                                                       |
-| `GITHUB_GRAPHQL_URL` | 返回 GraphQL API URL。 例如：`https://api.github.com/graphql`。                                                                                                                                                                          |
+| `GITHUB_SERVER_URL`  | 返回 {% data variables.product.product_name %} 服务器的 URL。 For example: `https://{% data variables.product.product_url %}`.                                                                                                           |
+| `GITHUB_API_URL`     | 返回 API URL。 For example: `{% data variables.product.api_url_code %}`.                                                                                                                                                             |
+| `GITHUB_GRAPHQL_URL` | 返回 GraphQL API URL。 For example: `{% data variables.product.graphql_url_code %}`.                                                                                                                                                 |
 
 {% tip %}
 
@@ -84,10 +85,6 @@ jobs:
 
 ### 环境变量命名约定
 
-{% note %}
-
-**注：** {% data variables.product.prodname_dotcom %} 会保留 `GITHUB_` 环境变量前缀供 {% data variables.product.prodname_dotcom %} 内部使用。 设置有 `GITHUB_` 前缀的环境变量或密码将导致错误。
-
-{% endnote %}
+When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
 
 您设置的指向文件系统上某个位置的任何新环境变量都应该有 `_PATH` 后缀。 `HOME` 和 `GITHUB_WORKSPACE` 默认变量例外于此约定，因为 "home" 和 "workspace" 一词已经暗示位置。
diff --git a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md
index 2610cafd7b..4892356a68 100644
--- a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md
+++ b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md
@@ -135,9 +135,9 @@ jobs:
   say_hello:
     runs-on: ubuntu-latest
     steps:
-    - run: |
-        echo "Hello ${{ github.event.inputs.name }}!"
-        echo "- in ${{ github.event.inputs.home }}!"
+      - run: |
+          echo "Hello ${{ github.event.inputs.name }}!"
+          echo "- in ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
@@ -175,18 +175,18 @@ on:
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Web 挂钩事件有效负载                                       | 活动类型                                                                                         | `GITHUB_SHA` | `GITHUB_REF` |
-| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ------------ | ------------ |
-| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>- `requested_action` | 默认分支上的最新提交   | 默认分支         |
+| Web 挂钩事件有效负载                                       | 活动类型                                                          | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------------- | ------------------------------------------------------------- | ------------ | ------------ |
+| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-例如，您可以在检查运行为 `rerequested` 或 `requested_action` 时运行工作流程。
+For example, you can run a workflow when a check run has been `rerequested` or `completed`.
 
 ```yaml
 on:
   check_run:
-    types: [rerequested, requested_action]
+    types: [rerequested, completed]
 ```
 
 #### `check_suite`
@@ -480,7 +480,7 @@ on:
 ```yaml
 on:
   project_card:
-    types: [opened, deleted]
+    types: [created, deleted]
 ```
 
 #### `project_column`
@@ -677,6 +677,12 @@ on:
     types: [published]
 ```
 
+{% note %}
+
+**注意：**`prereleased` 类型不会触发从草稿版本预发布，但 `published` 类型会触发。 如果您希望工作流程在稳定*和*预发布时运行，请订阅 `published` 而不是 `released` 和 `prereleased`。
+
+{% endnote %}
+
 #### `状态`
 
 在 Git 提交的状态发生变化（触发 `status` 事件）的任何时间运行您的工作流程。 有关 REST API 的信息，请参阅“[状态](/rest/reference/repos#statuses)”。
diff --git a/translations/zh-CN/content/actions/reference/index.md b/translations/zh-CN/content/actions/reference/index.md
index 4c6fbb0b2e..aaeb1a45f3 100644
--- a/translations/zh-CN/content/actions/reference/index.md
+++ b/translations/zh-CN/content/actions/reference/index.md
@@ -1,6 +1,6 @@
 ---
-title: Reference
-intro: 'Reference documentation for creating workflows, using GitHub-hosted runners, and authentication.'
+title: 参考
+intro: 使用 GitHub 托管的运行器和身份验证创建工作流程的参考文档。
 redirect_from:
   - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow
 versions:
@@ -11,47 +11,47 @@ versions:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-### Workflow syntax
+### 工作流程语法
 
-The workflow file is written in YAML. In the YAML workflow file, you can use expression syntax to evaluate contextual information, literals, operators, and functions. Contextual information includes workflow, environment variables, secrets, and the events that triggered the workflow. When you use [`run`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun) in a workflow step to run shell commands, you can use specific workflow command syntax to set environment variables, set output parameters for subsequent steps, and set error or debug messages.
+工作流程文件以 YAML 编写。 在 YAML 工作流程文件中，您可以使用表达式语法来评估上下文信息、文字、运算符和函数。 上下文信息包括工作流程、环境变量、密码和触发工作流程的事件。 当您在工作流程步骤中使用 [`run`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun) 运行 shell 命令时，您可以使用特定的工作流程命令语法来设置环境变量、设置后续步骤的输出参数，以及设置错误或调试信息。
 
 {% link_in_list /workflow-syntax-for-github-actions %}
 {% link_in_list /context-and-expression-syntax-for-github-actions %}
 {% link_in_list /workflow-commands-for-github-actions %}
 
-### Events
+### 事件
 
-You can configure workflows to run when specific GitHub events occur, at a scheduled time, manually, or when events outside of GitHub occur.
+您可以配置工作流和在发生特定 GitHub 事件时运行、在计划的时间运行、手动运行、手动或者当 GitHub 外部事件发生时运行。
 
 {% link_in_list /events-that-trigger-workflows %}
 
-### Authentication and secrets
+### 身份验证和密码
 
-{% data variables.product.prodname_dotcom %} provides a token that you can use to authenticate on behalf of {% data variables.product.prodname_actions %}. You can also store sensitive information as a secret in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environments{% else %} or repository{% endif %}. {% data variables.product.prodname_dotcom %} encrypts all secrets.
+{% data variables.product.prodname_dotcom %} 提供一个令牌，可用于代表 {% data variables.product.prodname_actions %} 进行身份验证。 您还可以将敏感信息存储在您的组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、仓库或者环境{% else %} 或仓库{% endif %} 中。 {% data variables.product.prodname_dotcom %} 对所有密码加密。
 
 {% link_in_list /authentication-in-a-workflow %}
 {% link_in_list /encrypted-secrets %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-### Environments
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+### 环境
 
-Workflow jobs can reference environments that have protection rules or environment-specific secrets.
+工作流程作业可以引用具有保护规则或环境特定机密的环境。
 
 {% link_in_list /environments %}
 {% endif %}
 
-### {% data variables.product.prodname_dotcom %}-hosted runners
+### 环境变量
 
-GitHub offers hosted virtual machines to run workflows. The virtual machine contains an environment with tools, packages, and environment variables for GitHub Actions to use.
+{% data variables.product.prodname_dotcom %} 为每个 {% data variables.product.prodname_actions %} 工作流程运行设置默认环境变量。 您也可以在工作流程文件中设置自定义环境变量。
 
 {% link_in_list /environment-variables %}
-{% link_in_list /specifications-for-github-hosted-runners %}
 
 {% if currentVersion == "free-pro-team@latest" %}
-### Administration
+### 管理
 
-When you run workflows on {% data variables.product.prodname_dotcom %}-hosted runners, there are usage limits and potential usage charges. You can also disable or restrict the usage of {% data variables.product.prodname_actions %} in a repository and organization.
+在 {% data variables.product.prodname_dotcom %} 托管的运行器上运行工作流程时，存在使用限制和潜在的使用费用。 您也可以禁用或限制 {% data variables.product.prodname_actions %} 在仓库和组织中的使用。
 
 {% link_in_list /usage-limits-billing-and-administration %}
 
diff --git a/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md
index 0f241782fd..4b60c3acc8 100644
--- a/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md
+++ b/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md
@@ -280,11 +280,11 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo "action_state=yellow" >> $GITHUB_ENV
+      echo "action_state=yellow" >> $GITHUB_ENV
   - name: Use the value
     id: step_two
     run: |
-        echo "${{ env.action_state }}" # This will output 'yellow'
+      echo "${{ env.action_state }}" # This will output 'yellow'
 ```
 {% endraw %}
 
@@ -306,9 +306,9 @@ steps:
   - name: Set the value
     id: step_one
     run: |
-        echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
-        curl https://httpbin.org/json >> $GITHUB_ENV
-        echo 'EOF' >> $GITHUB_ENV
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://httpbin.org/json >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
 ```
 
 ### 添加系统路径
diff --git a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md
index c570057da3..ac938f5f08 100644
--- a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md
@@ -110,8 +110,8 @@ on:
 on:
   push:
     branches:    
-    - 'releases/**'
-    - '!releases/**-alpha'
+      - 'releases/**'
+      - '!releases/**-alpha'
 ```
 
 ### `on.<push|pull_request>.paths`
@@ -128,7 +128,7 @@ on:
 on:
   push:
     paths-ignore:
-    - 'docs/**'
+      - 'docs/**'
 ```
 
 #### 包括路径的示例
@@ -139,7 +139,7 @@ on:
 on:
   push:
     paths:
-    - '**.js'
+      - '**.js'
 ```
 
 #### 排除路径
@@ -160,8 +160,8 @@ on:
 on:
   push:
     paths:
-    - 'sub-project/**'
-    - '!sub-project/docs/**'
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
 ```
 
 #### Git 差异比较
@@ -187,6 +187,32 @@ on:
 
 有关计划任务语法的更多信息请参阅“[触发工作流程的事件](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)”。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `权限`
+
+您可以修改授予 `GITHUB_TOKEN` 的默认权限，根据需要添加或删除访问权限，以便只授予所需的最低访问权限。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。
+
+您可以使用 `permissions` 作为顶级密钥，以应用于工作流程中的所有作业，或特定的作业。 当您在特定作业中添加 `permissions` 键时，该作业中的所有操作和运行命令使用 `GITHUB_TOKEN` 获取您指定的访问权限。  更多信息请参阅 [`jobs.<job_id>.permissions`](#jobsjob_idpermissions)。
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### 示例
+
+此示例显示为将要应用到工作流程中所有作业的 `GITHUB_TOKEN` 设置的权限。 所有权限都被授予读取权限。
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
+{% endif %}
+
 ### `env`
 
 环境变量的 `map` 可用于工作流程中所有作业的步骤。 您还可以设置仅适用于单个作业的步骤或单个步骤的环境变量。 更多信息请参阅 [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv)。
@@ -221,6 +247,18 @@ defaults:
     working-directory: scripts
 ```
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 并发组可以是任何字符串或表达式。 表达式只能使用 `github` 上下文。 有关表达式的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。
+
+您也可以在作业级别指定 `concurrency`。 更多信息请参阅 [`jobs.<job_id>.concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)。
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs`
 
 工作流程运行包括一项或多项作业。 作业默认是并行运行。 要按顺序运行作业，您可以使用 `<job_id>needs` 关键词在其他作业上定义依赖项。
@@ -339,6 +377,34 @@ runs-on: [self-hosted, linux]
 
 更多信息请参阅“[关于自托管的运行器](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)”和“[在工作流程中使用自托管的运行器](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)”。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.permissions`
+
+您可以修改授予 `GITHUB_TOKEN` 的默认权限，根据需要添加或删除访问权限，以便只授予所需的最低访问权限。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。
+
+通过在工作定义中指定权限，您可以根据需要为每个作业的 `GITHUB_TOKEN` 配置一组不同的权限。 或者，您也可以为工作流程中的所有作业指定权限。 有关在工作流程级别定义权限的信息，请参阅 [`permissions`](#permissions)。
+
+{% data reusables.github-actions.github-token-available-permissions %}
+{% data reusables.github-actions.forked-write-permission %}
+
+#### 示例
+
+此示例显示为将要应用到作业 `stale` 的 `GITHUB_TOKEN` 设置的权限。 对于 `issues` 和 `pull-requests` 拉取请求，授予写入访问权限。 所有其他范围将没有访问权限。
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v3
+```
+{% endif %}
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
 ### `jobs.<job_id>.environment`
 
@@ -347,10 +413,11 @@ runs-on: [self-hosted, linux]
 您可以将环境仅作为环境 `name`，或作为具有 `name` 和 `url` 的环境变量。 URL 映射到部署 API 中的 `environment_url`。 有关部署 API 的更多信息，请参阅“[部署](/rest/reference/repos#deployments)”。
 
 ##### 使用单一环境名称的示例
-
+{% raw %}
 ```yaml
 environment: staging_environment
 ```
+{% endraw %}
 
 ##### 使用环境名称和 URL 的示例
 
@@ -372,6 +439,25 @@ environment:
 {% endraw %}
 {% endif %}
 
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+### `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.concurrency-beta %}
+
+{% note %}
+
+**注意：** 在作业级别指定并发时，无法保证在 5 分钟内排队的作业或运行的互相顺序。
+
+{% endnote %}
+
+Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 并发组可以是任何字符串或表达式。 表达式可以使用除 `secrets` 上下文以外的任何上下文。 有关表达式的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。
+
+您也可以在工作流程级别指定 `concurrency`。 更多信息请参阅 [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency)。
+
+{% data reusables.actions.actions-group-concurrency %}
+
+{% endif %}
 ### `jobs.<job_id>.outputs`
 
 作业的输出 `map`。 作业输出可用于所有依赖此作业的下游作业。 有关定义作业依赖项的更多信息，请参阅 [`jobs.<job_id>.needs`](#jobsjob_idneeds)。
@@ -392,15 +478,15 @@ jobs:
       output1: ${{ steps.step1.outputs.test }}
       output2: ${{ steps.step2.outputs.test }}
     steps:
-    - id: step1
-      run: echo "::set-output name=test::hello"
-    - id: step2
-      run: echo "::set-output name=test::world"
+      - id: step1
+        run: echo "::set-output name=test::hello"
+      - id: step2
+        run: echo "::set-output name=test::world"
   job2:
     runs-on: ubuntu-latest
     needs: job1
     steps:
-    - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
 ```
 {% endraw %}
 
@@ -470,14 +556,14 @@ jobs:
     name: My Job
     runs-on: ubuntu-latest
     steps:
-    - name: Print a greeting
-      env:
-        MY_VAR: Hi there! My name is
-        FIRST_NAME: Mona
-        MIDDLE_NAME: The
-        LAST_NAME: Octocat
-      run: |
-        echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
 ```
 {% endraw %}
 
@@ -609,11 +695,11 @@ jobs:
 ```
 
 {% if currentVersion == "free-pro-team@latest" %}
-##### 使用 {% data variables.product.prodname_github_container_registry %} 的示例
+##### 使用 {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} 的示例
 
 `docker://{host}/{image}:{tag}`
 
-{% data variables.product.prodname_github_container_registry %} 中的 Docker 映像。
+{% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} 中的 Docker 映像。
 
 ```yaml
 jobs:
@@ -639,7 +725,9 @@ jobs:
 
 #### 在不同于工作流程的私有仓库中使用操作的示例
 
-您的工作流程必须检出私有仓库，并在本地引用操作。
+您的工作流程必须检出私有仓库，并在本地引用操作。 Generate a personal access token and add the token as an encrypted secret. 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
 
 {% raw %}
 ```yaml
@@ -651,7 +739,7 @@ jobs:
         with:
           repository: octocat/my-private-repo
           ref: v1.0
-          token: ${{ secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
           path: ./.github/actions/my-private-repo
       - name: Run my action
         uses: ./.github/actions/my-private-repo/my-action
@@ -768,7 +856,7 @@ steps:
 此示例中使用的命令 `perl` 必须安装在运行器上。
 
 
-{% if currentversion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}
 有关 GitHub 托管运行器中所包含软件的信息，请参阅“[GitHub 托管运行器的规格](/actions/reference/specifications-for-github-hosted-runners#supported-software)”。
 {% endif %}
@@ -899,7 +987,7 @@ steps:
 
 #### 使用 Node.js 多个版本运行的示例
 
-您可以提供配置选项阵列来指定矩阵。 例如，如果运行器支持 Node.js 版本 6、8 和 10，则您可以在 `matrix` 中指定这些版本的阵列。
+您可以提供配置选项阵列来指定矩阵。 例如，如果运行器支持 Node.js 版本 10、12 和 14，则您可以在 `matrix` 中指定这些版本的阵列。
 
 此示例通过设置三个 Node.js 版本阵列的 `node` 键创建三个作业的矩阵。 为使用矩阵，示例将 `matrix.node` 上下文属性设置为 `setup-node` 操作的输入参数 `node-version`。 因此，将有三个作业运行，每个使用不同的 Node.js 版本。
 
@@ -907,10 +995,10 @@ steps:
 ```yaml
 strategy:
   matrix:
-    node: [6, 8, 10]
+    node: [10, 12, 14]
 steps:
   # Configures the node version used on GitHub-hosted runners
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       # The Node.js version to configure
       node-version: ${{ matrix.node }}
@@ -933,10 +1021,10 @@ steps:
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    os: [ubuntu-16.04, ubuntu-18.04]
-    node: [6, 8, 10]
+    os: [ubuntu-18.04, ubuntu-20.04]
+    node: [10, 12, 14]
 steps:
-  - uses: actions/setup-node@v1
+  - uses: actions/setup-node@v2
     with:
       node-version: ${{ matrix.node }}
 ```
@@ -948,7 +1036,7 @@ steps:
 
 #### 在组合中包含附加值的示例
 
-您可以将额外的配置选项添加到已经存在的构建矩阵作业中。 例如，如果要在作业使用 `windows-latest` 和 `node` 的版本 4 运行时使用 `npm` 的特定版本，您可以使用 `include` 指定该附加选项。
+您可以将额外的配置选项添加到已经存在的构建矩阵作业中。 例如，如果要在作业使用 `windows-latest` 和 `node` 的版本 8 运行时使用 `npm` 的特定版本，您可以使用 `include` 指定该附加选项。
 
 {% raw %}
 ```yaml
@@ -956,29 +1044,29 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 2
+      # includes a new variable of npm with a value of 6
       # for the matrix leg matching the os and version
       - os: windows-latest
-        node: 4
-        npm: 2
+        node: 8
+        npm: 6
 ```
 {% endraw %}
 
 #### 包括新组合的示例
 
-您可以使用 `include` 将新作业添加到构建矩阵中。 任何不匹配包含配置都会添加到矩阵中。 例如，如果您想要使用 `node` 版本 12 在多个操作系统上构建，但在 Ubuntu 上需要一个使用节点版本 13 的额外实验性作业，则可使用 `include` 指定该额外作业。
+您可以使用 `include` 将新作业添加到构建矩阵中。 任何不匹配包含配置都会添加到矩阵中。 例如，如果您想要使用 `node` 版本 14 在多个操作系统上构建，但在 Ubuntu 上需要一个使用节点版本 15 的额外实验性作业，则可使用 `include` 指定该额外作业。
 
 {% raw %}
 ```yaml
 runs-on: ${{ matrix.os }}
 strategy:
   matrix:
-    node: [12]
+    node: [14]
     os: [macos-latest, windows-latest, ubuntu-18.04]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -994,11 +1082,11 @@ runs-on: ${{ matrix.os }}
 strategy:
   matrix:
     os: [macos-latest, windows-latest, ubuntu-18.04]
-    node: [4, 6, 8, 10]
+    node: [8, 10, 12, 14]
     exclude:
-      # excludes node 4 on macOS
+      # excludes node 8 on macOS
       - os: macos-latest
-        node: 4
+        node: 8
 ```
 {% endraw %}
 
@@ -1033,7 +1121,7 @@ strategy:
 
 #### 防止特定失败的矩阵作业导致工作流程运行失败的示例
 
-您可以允许作业矩阵中的特定任务失败，但工作流程运行不失败。 例如， 只允许 `node` 设置为 `13` 的实验性作业失败，而不允许工作流程运行失败。
+您可以允许作业矩阵中的特定任务失败，但工作流程运行不失败。 例如， 只允许 `node` 设置为 `15` 的实验性作业失败，而不允许工作流程运行失败。
 
 {% raw %}
 ```yaml
@@ -1042,11 +1130,11 @@ continue-on-error: ${{ matrix.experimental }}
 strategy:
   fail-fast: false
   matrix:
-    node: [11, 12]
+    node: [13, 14]
     os: [macos-latest, ubuntu-18.04]
     experimental: [false]
     include:
-      - node: 13
+      - node: 15
         os: ubuntu-18.04
         experimental: true
 ```
@@ -1064,7 +1152,7 @@ strategy:
 jobs:
   my_job:
     container:
-      image: node:10.16-jessie
+      image: node:14.16
       env:
         NODE_ENV: development
       ports:
@@ -1079,7 +1167,7 @@ jobs:
 ```yaml
 jobs:
   my_job:
-    container: node:10.16-jessie
+    container: node:14.16
 ```
 
 ### `jobs.<job_id>.container.image`
@@ -1181,7 +1269,7 @@ services:
 {% raw %}
 ```yaml
 services:
-  myservice1: 
+  myservice1:
     image: ghcr.io/owner/myservice1
     credentials:
       username: ${{ github.actor }}
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index cf32cfb83d..5d01541f41 100644
--- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -75,7 +75,6 @@ MacOS 虚拟机的硬件规格：
 
 * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
-* [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
 * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md)
 * [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md)
@@ -91,6 +90,10 @@ MacOS 虚拟机的硬件规格：
 
 如果有您想要请求的工具，请在 [actions/virtual-environments](https://github.com/actions/virtual-environments) 打开一个议题。 此仓库还包含有关运行器上所有主要软件更新的公告。
 
+#### 安装其他软件
+
+您可以在 {% data variables.product.prodname_dotcom %} 托管的运行器上安装其他软件。 更多信息请参阅“[自定义 GitHub 托管的运行器](/actions/using-github-hosted-runners/customizing-github-hosted-runners)”。
+
 ### IP 地址
 
 {% note %}
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..5eeb070493
--- /dev/null
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,90 @@
+---
+title: Customizing GitHub-hosted runners
+intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+product: '{% data reusables.gated-features.actions %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow.
+
+To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+
+This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner.
+
+### Installing software on Ubuntu runners
+
+The following example demonstrates how to install an `apt` package as part of a job.
+
+{% raw %}
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+{% endraw %}
+
+{% note %}
+
+**注意：** 在安装软件包之前务必运行 `sudo apt-get update`。 如果 `apt` 索引已经过时，此命令将获取并重新索引任何可用的软件包，这有助于防止软件包安装失败。
+
+{% endnote %}
+
+### 在 macOS 运行器上安装软件
+
+以下示例演示如何将 Brew 包和桶安装为作业的一部分。
+
+{% raw %}
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+{% endraw %}
+
+### 在 Windows 运行器上安装软件
+
+以下示例演示如何使用 [Chocolatey](https://community.chocolatey.org/packages) 将 {% data variables.product.prodname_dotcom %} CLI 安装为作业的一部分。
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/index.md b/translations/zh-CN/content/actions/using-github-hosted-runners/index.md
index c3ba622f10..d87669d096 100644
--- a/translations/zh-CN/content/actions/using-github-hosted-runners/index.md
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/index.md
@@ -11,6 +11,7 @@ versions:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 {% link_in_list /about-github-hosted-runners %}
+{% link_in_list /customizing-github-hosted-runners %}
 {% link_in_list /about-ae-hosted-runners %}
 {% link_in_list /adding-ae-hosted-runners %}
 {% link_in_list /using-ae-hosted-runners-in-a-workflow %}
diff --git a/translations/zh-CN/content/admin/advanced-security/about-licensing-for-github-advanced-security.md b/translations/zh-CN/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
new file mode 100644
index 0000000000..3a8e12f3dd
--- /dev/null
+++ b/translations/zh-CN/content/admin/advanced-security/about-licensing-for-github-advanced-security.md
@@ -0,0 +1,37 @@
+---
+title: 关于 GitHub 高级安全许可
+intro: 'You need a license to use {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+  - Security
+---
+
+### 关于 {% data variables.product.prodname_GH_advanced_security %} 的许可
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. 有关 {% data variables.product.prodname_GH_advanced_security %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。
+
+{% data reusables.advanced-security.license-overview %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for {% data variables.product.product_name %}, contact {% data variables.contact.contact_enterprise_sales %}. To enable {% data variables.product.prodname_GH_advanced_security %}, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your appliance](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+### 关于 {% data variables.product.prodname_GH_advanced_security %} 的提交者数量
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+### 管理 {% data variables.product.prodname_GH_advanced_security %} 的许可证使用
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+您可以执行策略以允许或不允许企业帐户拥有的组织使用 {% data variables.product.prodname_advanced_security %}。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_advanced_security %} 的策略](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)”。
+
+有关查看许可使用情况的更多信息，请参阅“[查看 {% data variables.product.prodname_GH_advanced_security %} 使用情况](/admin/advanced-security/viewing-your-github-advanced-security-usage)”。
+
+### 充分利用您的 {% data variables.product.prodname_GH_advanced_security %} 许可证
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..c2505ff7ec
--- /dev/null
+++ b/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,79 @@
+---
+title: 为设备配置代码扫描
+shortTitle: 配置代码扫描
+intro: '您可以为 {% data variables.product.product_location %} 启用、配置和禁用 {% data variables.product.prodname_code_scanning %}。 {% data variables.product.prodname_code_scanning_capc %} 允许用户扫描代码以发现漏洞和错误。'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+### 关于 {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+### Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion ver_gt "enterprise-server@3.0" %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+### 使用 {% data variables.product.prodname_actions %} 运行 {% data variables.product.prodname_code_scanning %}
+
+#### 设置自托管运行器
+
+{% data variables.product.prodname_ghe_server %} 可以使用 {% data variables.product.prodname_actions %} 工作流程运行 {% data variables.product.prodname_code_scanning %}。 首先，您需要在环境中预配一个或多个自托管的 {% data variables.product.prodname_actions %} 运行器。 您可以在仓库、组织或企业帐户级别预配自托管运行器。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。
+
+您必须确保 Git 在用于运行 {% data variables.product.prodname_codeql %} 操作的任何自托管运行器上的 PATH 变量中。
+
+#### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+{% data variables.product.prodname_codeql %} 操作包含在您安装的 {% data variables.product.prodname_ghe_server %} 中。 如果 {% data variables.product.prodname_ghe_server %} 可以访问互联网，操作将自动下载进行分析所需的 {% data variables.product.prodname_codeql %} 包。 或者，您也可以使用同步工具使 {% data variables.product.prodname_codeql %} 分析包在本地可用。 更多信息请参阅下面的“[在没有互联网接入的服务器上配置 {% data variables.product.prodname_codeql %} 分析](#configuring-codeql-analysis-on-a-server-without-internet-access)”。
+
+您也可以通过设置 {% data variables.product.prodname_github_connect %}，使第三方操作可供 {% data variables.product.prodname_code_scanning %} 的用户使用。 更多信息请参阅下面的“[配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)”。
+
+#### 在没有互联网接入的服务器上配置 {% data variables.product.prodname_codeql %} 分析
+如果您在上面运行 {% data variables.product.prodname_ghe_server %} 的服务器未连接到互联网，但您要允许用户对其仓库启用 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，则您必须使用 {% data variables.product.prodname_codeql %} 操作同步工具将 {% data variables.product.prodname_codeql %} 分析包从 {% data variables.product.prodname_dotcom_the_website %} 复制到您的服务器。 有关该工具及其使用方法，请参阅 [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/)。
+
+如果您设置了 {% data variables.product.prodname_codeql %} 操作同步工具，您可以使用它来同步最新发布的 {% data variables.product.prodname_codeql %} 操作和相关的 {% data variables.product.prodname_codeql %} 分析包。 这些兼容 {% data variables.product.prodname_ghe_server %}。
+
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" %}
+要在 {% data variables.product.prodname_ghe_server %} 上使用 {% data variables.product.prodname_actions %} 运行 {% data variables.product.prodname_code_scanning %}，必须在本地可以进行适当的操作。 您可以通过三种方式使操作可用。
+
+- **推荐**：您可以使用 [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) 自动从 {% data variables.product.prodname_dotcom_the_website %} 下载操作。 托管实例的机器必须能够访问 {% data variables.product.prodname_dotcom_the_website %}。 此方法可确保自动获取最新软件。 更多信息请参阅“[配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)”。
+- 如果要使用 {% data variables.product.prodname_codeql_workflow %}，可以使用 [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) 上的 {% data variables.product.prodname_codeql %} 操作同步工具将仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到 {% data variables.product.prodname_ghe_server %}。 无论您的 {% data variables.product.product_location %} 或 {% data variables.product.prodname_actions %} 运行器是否可以访问互联网， 只要您可以同时在计算机上访问 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}，您都可以使用此工具。
+- 您可以通过克隆包含操作的 {% data variables.product.prodname_dotcom_the_website %} 仓库，在服务器上创建操作仓库的本地副本。 例如，如果要使用 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 操作，可以在实例中创建一个名为 `github/codeql-action` 的仓库，然后从 {% data variables.product.prodname_dotcom_the_website %} 克隆[仓库](https://github.com/github/codeql-action)，再将该仓库推送到实例的 `github/codeql-action` 仓库。 您还需要从 {% data variables.product.prodname_dotcom_the_website %} 上的仓库下载任何发行版，并将它们作为发行版上传到实例的 `github/codeql-action` 仓库。
+{% endif %}
+
+#### 配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}
+1. 如果要从 {% data variables.product.prodname_dotcom_the_website %} 下载按需操作工作流程，则需要启用 {% data variables.product.prodname_github_connect %}。 更多信息请参阅“[启用 {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)”。
+2. 您还需要为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_actions %}。 更多信息请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)”。
+3. 下一步是使用 {% data variables.product.prodname_github_connect %} 配置对 {% data variables.product.prodname_dotcom_the_website %} 上的操作的访问权限。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。
+4. 将自托管运行器添加到仓库、组织或企业帐户。 更多信息请参阅“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。
+
+### 使用 {% data variables.product.prodname_codeql_runner %} 运行 {% data variables.product.prodname_code_scanning %}
+如果您不想使用 {% data variables.product.prodname_actions %}，您可以使用 {% data variables.product.prodname_codeql_runner %} 运行 {% data variables.product.prodname_code_scanning %}。
+
+该 {% data variables.product.prodname_codeql_runner %} 是一个命令行工具，您可以将其添加到第三方 CI/CD 系统中。 该工具在 {% data variables.product.prodname_dotcom %} 仓库检出时运行 {% data variables.product.prodname_codeql %} 分析。 更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”。
diff --git a/translations/zh-CN/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..387d916d41
--- /dev/null
+++ b/translations/zh-CN/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,75 @@
+---
+title: 为设备配置密码扫描
+shortTitle: 配置密码扫描
+intro: '您可以为 {% data variables.product.product_location %} 启用、配置和禁用 {% data variables.product.prodname_secret_scanning %}。 {% data variables.product.prodname_secret_scanning_caps %} 允许用户扫描代码以寻找意外泄露的密码。'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+versions:
+  enterprise-server: '>=3.0'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+### 关于 {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.secret-scanning.about-secret-scanning %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+
+### Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+
+- [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470)（补充流式传输 SIMD 扩展 3）CPU 标志需要在运行 {% data variables.product.product_location %} 的 VM/KVM 上启用。
+
+- A license for {% data variables.product.prodname_GH_advanced_security %} (see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)")
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### 检查您的 vCPU 上的 SSSE3 标志的支持
+
+SSSE3 指令集是必需的，因为 {% data variables.product.prodname_secret_scanning %} 利用硬件加速模式匹配来查找提交给 {% data variables.product.prodname_dotcom %} 仓库的潜在凭据。 大多数现代 CPU 都启用了 SSSE3。 您可以检查您的 {% data variables.product.prodname_ghe_server %} 实例的可用 vCPU 是否启用了 SSSE3。
+
+1. 连接到 {% data variables.product.prodname_ghe_server %} 实例的管理 shell。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)。”
+2. 输入以下命令：
+
+```shell
+grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+```
+
+如果返回值 `0`，则意味着 SSSE3 标志可用并且已启用。 您现在可以为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_secret_scanning %}。 For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+如果不返回 `0`，则 SSSE3 未在您的 VM/KVM 上启用。 您需要参考硬件/虚拟机监控程序的文档，以了解如何启用该标志，或者如何使其可用于访客 VM。
+
+#### 检查您是否拥有 {% data variables.product.prodname_advanced_security %} 许可
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. 检查左侧边栏中是否有 **{% data variables.product.prodname_advanced_security %}** 条目。 ![高级安全侧边栏](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+
+### 启用 {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. 在“{% data variables.product.prodname_advanced_security %}”下，单击 **{% data variables.product.prodname_secret_scanning_caps %}**。 ![用于启用或禁用 {% data variables.product.prodname_secret_scanning %} 的复选框](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+### 禁用 {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. 在“{% data variables.product.prodname_advanced_security %}”下，取消选择 **{% data variables.product.prodname_secret_scanning_caps %}**。 ![用于启用或禁用 {% data variables.product.prodname_secret_scanning %} 的复选框](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..80f801ef0f
--- /dev/null
+++ b/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,88 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=2.22'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+### About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_advanced_security %} 的策略](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)”。
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% if currentVersion == "enterprise-server@3.0" %}更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %}
+{% endif %}
+
+### Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% if currentVersion ver_gt "enterprise-server@3.0" %} For information about licensing, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
+2. Upload the new license to {% data variables.product.product_location %}. For more information, see "[Managing your GitHub Enterprise license](/admin/overview/managing-your-github-enterprise-license#uploading-a-new-license-to-github-enterprise-server)."{% if currentVersion ver_gt "enterprise-server@2.22" %}
+3. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+
+### Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![高级安全侧边栏](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
+
+{% data reusables.enterprise_management_console.advanced-security-license %}
+{% endif %}
+
+### Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
+1. Under "{% data variables.product.prodname_advanced_security %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png)用于启用 Public Pages 的复选框{% else %}
+1. 在“{% data variables.product.prodname_advanced_security %}”下，单击 **{% data variables.product.prodname_code_scanning_capc %}**。 ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png)用于启用 Public Pages 的复选框{% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. 更多信息请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/admin/advanced-security/configuring-code-scanning-for-your-appliance)”。
+
+### 通过管理 shell (SSH) 启用或禁用 {% data variables.product.prodname_GH_advanced_security %}
+
+You can enable or disable features programmatically on {% data variables.product.product_location %}. 有关 {% data variables.product.prodname_ghe_server %} 的管理 shell 和命令行实用程序的更多信息，请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”和“[命令行实用程序](/admin/configuration/command-line-utilities#ghe-config)”。
+
+例如，当您部署用于暂存或灾难恢复的实例时，可以使用基础架构即代码工具启用 {% data variables.product.prodname_code_scanning %}。
+
+1. SSH 连接到 {% data variables.product.product_location %}。
+1. 启用 {% data variables.product.prodname_code_scanning %}。
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+2. （可选）禁用 {% data variables.product.prodname_code_scanning %}。
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+3. 应用配置。
+    ```shell
+  ghe-config-apply
+  ```
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}To enable and disable {% data variables.product.prodname_secret_scanning %} in the same way, set: `ghe-config app.secret-scanning.enabled` true or false and apply the configuration.{% endif %}
diff --git a/translations/zh-CN/content/admin/advanced-security/index.md b/translations/zh-CN/content/admin/advanced-security/index.md
new file mode 100644
index 0000000000..9d00e5d354
--- /dev/null
+++ b/translations/zh-CN/content/admin/advanced-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Managing GitHub Advanced Security for your enterprise
+shortTitle: Managing GitHub Advanced Security
+intro: 'You can configure {% data variables.product.prodname_advanced_security %} and manage use by your enterprise to suit your organization''s needs.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - Enterprise
+---
+
+### 目录
+
+{% link_in_list /about-licensing-for-github-advanced-security %}
+{% link_in_list /enabling-github-advanced-security-for-your-enterprise %}
+{% link_in_list /configuring-code-scanning-for-your-appliance %}
+{% link_in_list /configuring-secret-scanning-for-your-appliance %}
+{% link_in_list /viewing-your-github-advanced-security-usage %}
diff --git a/translations/zh-CN/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/zh-CN/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..0efbd23943
--- /dev/null
+++ b/translations/zh-CN/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,23 @@
+---
+title: 查看您的 GitHub 高级安全使用情况
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  enterprise-server: '>=3.1'
+topics:
+  - Enterprise
+---
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."
+
+### Viewing license usage for {% data variables.product.prodname_GH_advanced_security %}
+
+You can check how many seats your license includes and how many seats are currently in use.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   “{% data variables.product.prodname_GH_advanced_security %}”部分显示了当前使用详情。 You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. （可选）单击您是所有者的组织的名称，以显示组织的安全和分析设置。 ![在企业帐单设置的 {% data variables.product.prodname_GH_advanced_security %} 部分中拥有的组织](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. 在“Security & analysis（安全性和分析）”设置页面上，滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分以查看此组织的仓库使用明细。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
diff --git a/translations/zh-CN/content/admin/all-releases.md b/translations/zh-CN/content/admin/all-releases.md
new file mode 100644
index 0000000000..08a5bc9420
--- /dev/null
+++ b/translations/zh-CN/content/admin/all-releases.md
@@ -0,0 +1,37 @@
+---
+title: GitHub Enterprise Server 发行版
+intro: '当前支持且先前废弃的 {{ site.data.variables.product.prodname_ghe_server }} 版本的文档。'
+allowTitleToDifferFromFilename: true
+versions:
+  enterprise-server: '*'
+topics:
+  - Enterprise
+---
+
+## 当前支持
+
+请参阅 [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) 以获取最新版本的信息。
+
+{% for supportedRelease in enterpriseServerReleases.supported %}
+- [{% data variables.product.prodname_ghe_server %} {{supportedRelease}}](/enterprise-server@{{supportedRelease}})
+{% endfor %}
+
+## 已废弃
+
+已弃用版本的文档仍然可用，但不再保留。
+
+{% for deprecatedRelease in enterpriseServerReleases.deprecatedReleasesWithNewFormat %}
+- [Enterprise Server {{deprecatedRelease}}](/enterprise-server@{{deprecatedRelease}})
+{% endfor %}
+
+{% for deprecatedReleaseLegacyFormat in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %}
+- [Enterprise Server {{deprecatedReleaseLegacyFormat}}](/enterprise/{{deprecatedReleaseLegacyFormat}})
+{% endfor %}
+
+## 已弃用的开发者文档
+
+已弃用版本的开发者文档仍然可用，但不再保留。
+
+{% for deprecatedDevRelease in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %}
+- [Enterprise Server {{deprecatedDevRelease}}](https://developer.github.com/enterprise/{{deprecatedDevRelease}})
+{% endfor %}
diff --git a/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
index fe64ceb6d2..781dc607b4 100644
--- a/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/authentication/about-identity-and-access-management-for-your-enterprise.md
@@ -5,6 +5,13 @@ intro: '您可以使用 {% if enterpriseServerVersions contains currentVersion %
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
 ---
 
 ### 关于企业的身份和访问管理
diff --git a/translations/zh-CN/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/zh-CN/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
index 1ddff78d36..47371b0aaa 100644
--- a/translations/zh-CN/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
+++ b/translations/zh-CN/content/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 ### 关于对您的身份提供程序覆盖范围外的用户进行内置身份验证
diff --git a/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md b/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md
index f267707b38..4ceaebb618 100644
--- a/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md
+++ b/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/changing-authentication-methods
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 在您更改身份验证方法时，{% data variables.product.product_location %} 上的用户帐户将保留，只要他们的用户名没有发生变化，用户就可以继续登录原来的帐户。
diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index bbba4d21f1..c46c3386be 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure authentication and provisioning fo
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### 关于使用 Azure AD 进行身份验证和用户预配
diff --git a/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
index b173428edb..7028c7bd9f 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -6,6 +6,13 @@ product: '{% data reusables.gated-features.saml-sso %}'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### 关于 SAML SSO
diff --git a/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
index cbc7ddcbc2..bb0d06b58d 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md
@@ -6,6 +6,13 @@ permissions: 'Enterprise owners can configure user provisioning for an enterpris
 product: '{% data reusables.gated-features.saml-sso %}'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
 ---
 
 ### 关于企业的用户预配
diff --git a/translations/zh-CN/content/admin/authentication/disabling-unauthenticated-sign-ups.md b/translations/zh-CN/content/admin/authentication/disabling-unauthenticated-sign-ups.md
index c61cdcf2a9..e4eda88a31 100644
--- a/translations/zh-CN/content/admin/authentication/disabling-unauthenticated-sign-ups.md
+++ b/translations/zh-CN/content/admin/authentication/disabling-unauthenticated-sign-ups.md
@@ -7,7 +7,10 @@ redirect_from:
 intro: 如果您使用的是内置身份验证，可以阻止未经身份验证的人创建帐户。
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/authentication/using-built-in-authentication.md b/translations/zh-CN/content/admin/authentication/using-built-in-authentication.md
index 235c13a748..d8baf31e62 100644
--- a/translations/zh-CN/content/admin/authentication/using-built-in-authentication.md
+++ b/translations/zh-CN/content/admin/authentication/using-built-in-authentication.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/authentication/using-built-in-authentication
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 您可以创建用户将在登录和注销页面上看到的自定义消息。 更多信息请参阅“[自定义您的实例上的用户消息](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)”。
diff --git a/translations/zh-CN/content/admin/authentication/using-cas.md b/translations/zh-CN/content/admin/authentication/using-cas.md
index 2a318af382..946d029dee 100644
--- a/translations/zh-CN/content/admin/authentication/using-cas.md
+++ b/translations/zh-CN/content/admin/authentication/using-cas.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'CAS 是一种适用于多种网络应用程序的单点登录 (SSO) 协议。 在登录之前，CAS 用户帐户不会占用{% if currentVersion ver_gt "enterprise-server@2.16" %}用户许可{% else %}席位{% endif %}。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/zh-CN/content/admin/authentication/using-ldap.md b/translations/zh-CN/content/admin/authentication/using-ldap.md
index bb071dbadf..410dbecb30 100644
--- a/translations/zh-CN/content/admin/authentication/using-ldap.md
+++ b/translations/zh-CN/content/admin/authentication/using-ldap.md
@@ -11,8 +11,12 @@ redirect_from:
 intro: '使用 LDAP，您可以向 {% data variables.product.prodname_ghe_server %} 验证现有帐户的身份和集中管理仓库权限。 LDAP 是一种用于访问和维护目录信息服务的流行应用程序协议，是将第三方软件与大型公司用户目录相集成时使用的最常见协议之一。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/zh-CN/content/admin/authentication/using-saml.md b/translations/zh-CN/content/admin/authentication/using-saml.md
index cca7ef2d23..1e53f76ead 100644
--- a/translations/zh-CN/content/admin/authentication/using-saml.md
+++ b/translations/zh-CN/content/admin/authentication/using-saml.md
@@ -8,8 +8,13 @@ redirect_from:
 intro: 'SAML 是一种基于 XML 的身份验证和授权标准。 {% data variables.product.prodname_ghe_server %} 可以作为您的内部 SAML 身份提供程序 (IdP) 的服务提供程序 (SP)。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Accounts
+  - Authentication
   - Enterprise
+  - Identity
+  - SSO
 ---
 
 {% data reusables.enterprise_user_management.built-in-authentication %}
diff --git a/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md b/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md
index 39c6e82db5..0bf7e5a9dc 100644
--- a/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md
+++ b/translations/zh-CN/content/admin/configuration/about-enterprise-configuration.md
@@ -4,8 +4,11 @@ intro: '您可以使用站点管理员仪表板{% if enterpriseServerVersions co
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
@@ -18,9 +21,7 @@ topics:
 
 {% if currentVersion == "github-ae@latest" %}
 第一次访问您的企业时，您将完成初始配置以获取
-可供使用的 {% data variables.product.product_name %}。 初始配置包括连接您的企业与 idP 连接、通过 SAML SSO 进行身份验证，以及配置企业中仓库和组织的策略。 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)。”
-
-为使用户在初始配置后收到来自 {% data variables.product.product_name %} 的任何电子邮件，您必须要求 {% data variables.contact.github_support %} 配置支持 SMTP 服务器的出站电子邮件。 更多信息请参阅“[配置电子邮件通知](/admin/configuration/configuring-email-for-notifications)”。
+可供使用的 {% data variables.product.product_name %}。 初始配置包括连接您的企业与身份提供程序 (IdP) 连接、通过 SAML SSO 进行身份验证、配置企业中仓库和组织的策略，以及为出站电子邮件配置 SMTP。 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)。”
 
 稍后，您可以使用站点管理员仪表板和企业设置进一步配置企业、管理用户、组织和仓库，并设置可降低风险和提高质量的策略。
 
diff --git a/translations/zh-CN/content/admin/configuration/accessing-the-administrative-shell-ssh.md b/translations/zh-CN/content/admin/configuration/accessing-the-administrative-shell-ssh.md
index 0989c4c2ad..3b44920efd 100644
--- a/translations/zh-CN/content/admin/configuration/accessing-the-administrative-shell-ssh.md
+++ b/translations/zh-CN/content/admin/configuration/accessing-the-administrative-shell-ssh.md
@@ -13,8 +13,11 @@ redirect_from:
 intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - SSH
 ---
 
 ### 关于管理 shell 访问
diff --git a/translations/zh-CN/content/admin/configuration/accessing-the-management-console.md b/translations/zh-CN/content/admin/configuration/accessing-the-management-console.md
index ec96e3f46b..59934b8c41 100644
--- a/translations/zh-CN/content/admin/configuration/accessing-the-management-console.md
+++ b/translations/zh-CN/content/admin/configuration/accessing-the-management-console.md
@@ -12,8 +12,10 @@ redirect_from:
   - /enterprise/admin/configuration/accessing-the-management-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### 关于 {% data variables.enterprise.management_console %}
diff --git a/translations/zh-CN/content/admin/configuration/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/command-line-utilities.md
index 8272681b7e..97a30b04ee 100644
--- a/translations/zh-CN/content/admin/configuration/command-line-utilities.md
+++ b/translations/zh-CN/content/admin/configuration/command-line-utilities.md
@@ -9,8 +9,10 @@ redirect_from:
 miniTocMaxHeadingLevel: 4
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - SSH
 ---
 
 以 SSH 管理员用户身份登录后，您可以在虚拟机上的任何位置执行这些命令。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。
@@ -483,15 +485,21 @@ ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 {% endif %}
 
 要显示交付的完整挂钩有效负载、结果以及任何异常：
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+```shell
+ghe-webhook-logs -g <em>delivery-guid</em>
+```
+{% else %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em> -v
 ```
+{% endif %}
 
 ### 集群
 
 #### ghe-cluster-status
 
-此实用程序可用于管理分配的 {% data variables.product.prodname_pages %} 服务器。
+Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
 
 ```shell
 $ ghe-cluster-status
@@ -644,14 +652,14 @@ git-import-svn-raw
 
 #### git-import-tfs-raw
 
-此实用程序可从 Team Foundation Version Control 导入。 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
+This utility imports from Team Foundation Version Control (TFVC). 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
 ```shell
 git-import-tfs-raw
 ```
 
 #### git-import-rewrite
 
-此实用程序可重写导入的仓库。 这样，您将有机会重命名作者，对于 Subversion 和 TFS，可基于文件夹生成 Git 分支。 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
+此实用程序可重写导入的仓库。 This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. 更多信息请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)。”
 ```shell
 git-import-rewrite
 ```
@@ -756,7 +764,7 @@ $ ghe-upgrade-scheduler -r <em>UPGRADE PACKAGE FILENAME</em>
 
 包含下载状态的文件位于 */var/lib/ghe-updates/ghe-update-check.status*。
 
-要查看最新的 {% data variables.product.prodname_enterprise %} 版本，请使用 `-i` 交换字符。
+要查看最新的 {% data variables.product.prodname_enterprise %} 版本，请使用 `-i` 开关。
 
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-update-check'
diff --git a/translations/zh-CN/content/admin/configuration/configuring-a-hostname.md b/translations/zh-CN/content/admin/configuration/configuring-a-hostname.md
index 1a3f9ea157..bd23d99226 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-a-hostname.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-a-hostname.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-a-hostname
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 如果配置的是主机名，而不是硬编码 IP 地址，您将能够更改运行 {% data variables.product.product_location %} 的物理硬件，而不会影响用户或客户端软件。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md b/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
index 7069b4eb53..8bc989b95e 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-an-outbound-web-proxy-server.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 为 {% data variables.product.product_location %} 启用代理服务器后，除非已将目标主机添加为 HTTP 代理排除项，否则会先通过代理服务器发送由 {% data variables.product.prodname_ghe_server %} 发送的出站消息。 出站消息类型包括传出 web 挂钩、上传包和提取旧头像。 代理服务器的 URL 为协议、域或 IP 地址外加端口号，例如 `http://127.0.0.1:8123`。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-applications.md b/translations/zh-CN/content/admin/configuration/configuring-applications.md
index af8f3252f2..e61e454489 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-applications.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-applications.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-applications
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 ### 调整图像缓存
diff --git a/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md
index f37a370be4..1c51bb9570 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-backups-on-your-appliance.md
@@ -1,5 +1,6 @@
 ---
 title: 在设备上配置备份
+shortTitle: Configuring backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores/
   - /enterprise/admin/articles/backup-and-recovery/
@@ -15,8 +16,12 @@ redirect_from:
 intro: '作为灾难恢复计划的一部分，您可以通过配置自动备份的方式保护 {% data variables.product.product_location %} 中的生产数据。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Backups
   - Enterprise
+  - Fundamentals
+  - Infrastructure
 ---
 
 ### 关于 {% data variables.product.prodname_enterprise_backup_utilities %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-built-in-firewall-rules.md b/translations/zh-CN/content/admin/configuration/configuring-built-in-firewall-rules.md
index b0ad42471e..71dba61345 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-built-in-firewall-rules.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-built-in-firewall-rules.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### 关于 {% data variables.product.product_location %} 的防火墙
diff --git a/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
index eb2434be1c..2bd7d4bc59 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md
@@ -4,6 +4,11 @@ shortTitle: 配置数据加密
 intro: 对于休息时加密，您可以提供自己的加密密钥，以在加密策略下加密数据。
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Security
 ---
 
 {% note %}
@@ -16,56 +21,4 @@ versions:
 
 为了提供高级别的安全性，{% data variables.product.product_name %} 在休息时对数据中心中的数据加密，以及在用户计算机与数据中心之间传输数据时对数据加密。
 
-对于传输中的加密，{% data variables.product.product_name %} 使用传输层安全性 (TLS)。 对于休息时的加密， {% data variables.product.product_name %} 提供默认的 RSA 密钥。 在初始化企业后，您可以选择提供自己的密钥。 密钥应该是采用 PEM 格式的 2048 位 RSA 私钥。
-
-您提供的密钥存储在 {% data variables.product.company_short %} 管理的密钥保管库的 FIPS 140-2 标准硬件安全模块 (HSM) 中。
-
-要配置加密密钥，请使用 REST API。 有许多 API 端点，例如检查加密状态、更新加密密钥以及禁用加密密钥的端点。 请注意，禁用密钥将冻结企业。 有关 API 端点的详细信息，请参阅 REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)”。
-
-### 添加或更新加密密钥
-
-您可以随时随地添加新的加密密钥。 添加新密钥时，旧密钥将被丢弃。 更新密钥时，您的企业不会遇到停机。
-
-您的 2048 位 RSA 私钥应采用 PEM 格式，例如在名为 _private-key.pem_ 的文件中。
-
-   ```
-   -----BEGIN RSA PRIVATE KEY-----
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-   -----END RSA PRIVATE KEY-----
-   ```
-
-1. 要添加密钥，请使用 `PATCH /enterprise/encryption` 端点，将 *~/private-key.pem* 替换为私钥的路径。
-
-   ```shell
-   curl -X PATCH http(s)://<em>hostname</em>/api/v3/enterprise/encryption \
-     -d "{ \"key\": \"$(awk '{printf "%s\\n", $0}' ~/private-key.pem)\" }"
-   ```
-
-2. （可选）检查更新操作的状态。
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-### 禁用加密密钥
-
-要冻结您的企业（例如在出现违规情况下），可以通过将加密密钥标记为禁用来禁用静态加密。
-
-1. 要禁用密钥和静态加密，请使用 `DELETE /enterprise/encryption` 端点。 此操作不会永久删除密钥。
-
-   ```shell
-   curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
-   ```
-
-2. （可选）检查删除操作的状态。 禁用静态加密大约需要十分钟。
-
-   ```shell
-   curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
-   ```
-
-要在禁用加密密钥后解冻企业，请联系支持人员。 更多信息请参阅“[关于 {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)”。
-
-### 延伸阅读
-
-- REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)” 
+对于传输中的加密，{% data variables.product.product_name %} 使用传输层安全性 (TLS)。 对于休息时的加密， {% data variables.product.product_name %} 提供默认的 RSA 密钥。 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-dns-nameservers.md b/translations/zh-CN/content/admin/configuration/configuring-dns-nameservers.md
index 08c69a3942..3aeca63f7b 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-dns-nameservers.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-dns-nameservers.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-dns-nameservers
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 指定的域名服务器必须解析 {% data variables.product.product_location %} 的主机名。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md b/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md
index 3e8a648c21..6402c0fbd5 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-email-for-notifications.md
@@ -10,8 +10,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
 ---
 
 {% if currentVersion == "github-ae@latest" %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
index c5b4777510..1cf0fdb359 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-github-pages-for-your-enterprise.md
@@ -11,8 +11,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Pages
 ---
 
 ### 为 {% data variables.product.prodname_pages %} 启用公共站点
diff --git a/translations/zh-CN/content/admin/configuration/configuring-rate-limits.md b/translations/zh-CN/content/admin/configuration/configuring-rate-limits.md
index a98c7e727b..e4c476d2ca 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-rate-limits.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-rate-limits.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-rate-limits
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 ### 为 {% data variables.product.prodname_enterprise_api %} 启用速率限制
diff --git a/translations/zh-CN/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/zh-CN/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
index 1b6eec3fa3..f4b8948adb 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% note %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-time-synchronization.md b/translations/zh-CN/content/admin/configuration/configuring-time-synchronization.md
index ac0aca213c..1a4ed9aca4 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-time-synchronization.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-time-synchronization.md
@@ -10,8 +10,12 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-time-synchronization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 ### 更改默认 NTP 服务器
diff --git a/translations/zh-CN/content/admin/configuration/configuring-tls.md b/translations/zh-CN/content/admin/configuration/configuring-tls.md
index eec69f8ce0..7e255f8297 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-tls.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-tls.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/configuration/configuring-tls
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### 关于传输层安全
diff --git a/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
index 9b772e5ac0..514835e113 100644
--- a/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud.md
@@ -10,8 +10,12 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
 ---
 
 ### 关于 {% data variables.product.prodname_github_connect %}
diff --git a/translations/zh-CN/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/zh-CN/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
index b4fcbbd3aa..4ec055d57f 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
@@ -8,8 +8,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Security
 ---
 
 ### 关于 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项的警报
diff --git a/translations/zh-CN/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md b/translations/zh-CN/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
index cee37a8f5a..3fecbb4374 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-and-scheduling-maintenance-mode.md
@@ -12,8 +12,12 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
 ---
 
 ### 关于维护模式
diff --git a/translations/zh-CN/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/zh-CN/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
index 4baed099fe..ad5a15f1c0 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -7,8 +7,11 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
+  - Licensing
 ---
 
 ### 关于许可同步
diff --git a/translations/zh-CN/content/admin/configuration/enabling-private-mode.md b/translations/zh-CN/content/admin/configuration/enabling-private-mode.md
index 120971a1b0..00844ae06a 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-private-mode.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-private-mode.md
@@ -9,8 +9,16 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-private-mode
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Authentication
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
 ---
 
 如果 {% data variables.product.product_location %} 可通过 Internet 公开访问，您必须启用私有模式。 在私有模式下，用户不能通过 `git://` 匿名克隆仓库。 如果还启用了内置身份验证，管理员必须邀请新用户在实例上创建帐户。 更多信息请参阅“[使用内置身份验证](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)”。
diff --git a/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md
index 9dfa542837..268b77074c 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-subdomain-isolation.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/configuration/enabling-subdomain-isolation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### 关于子域隔离
@@ -19,7 +24,7 @@ topics:
 
 {% if currentVersion == "enterprise-server@2.22" %}
 要将 Docker 与
-{% data variables.product.prodname_registry %} 一起使用，您还必须启用子域隔离。 更多信息请参阅“[配置 Docker 与 {% data variables.product.prodname_registry %} 一起使用](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)”。
+{% data variables.product.prodname_registry %} 一起使用，您还必须启用子域隔离。 For more information, see "[Working with the Docker registry](/enterprise/{{ currentVersion }}/user/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 |
diff --git a/translations/zh-CN/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/zh-CN/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
index 02bdcbe0b6..89287ca60a 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md
@@ -10,8 +10,10 @@ redirect_from:
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - GitHub Connect
 ---
 
 作为站点管理员，您可以允许最终用户将进行过匿名处理的工作贡献计数从 {% data variables.product.prodname_ghe_server %} 发送到其 {% data variables.product.prodname_dotcom_the_website %} 贡献图。
diff --git a/translations/zh-CN/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/zh-CN/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
index 79fb3e73d8..951d330439 100644
--- a/translations/zh-CN/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
+++ b/translations/zh-CN/content/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom.md
@@ -12,6 +12,8 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - GitHub Connect
+  - GitHub search
 ---
 
 启用统一搜索后，用户可在从 {% data variables.product.product_location_enterprise %} 进行搜索时查看 {% data variables.product.prodname_dotcom_the_website %} 上公共和私有内容的搜索结果。
diff --git a/translations/zh-CN/content/admin/configuration/index.md b/translations/zh-CN/content/admin/configuration/index.md
index 2ed7e100fe..f19d7f5269 100644
--- a/translations/zh-CN/content/admin/configuration/index.md
+++ b/translations/zh-CN/content/admin/configuration/index.md
@@ -33,6 +33,7 @@ topics:
     {% link_in_list /enabling-private-mode %}
     {% link_in_list /managing-github-for-mobile-for-your-enterprise %}
     {% link_in_list /configuring-email-for-notifications %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise %}
     {% link_in_list /configuring-rate-limits %}
     {% link_in_list /configuring-applications %}
     {% link_in_list /troubleshooting-ssl-errors %}
@@ -57,6 +58,3 @@ topics:
     {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %}
     {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %}
     {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %}
-{% topic_link_in_list /configuring-advanced-security-features %}
-    {% link_in_list /configuring-code-scanning-for-your-appliance %}
-    {% link_in_list /configuring-secret-scanning-for-your-appliance %}
diff --git a/translations/zh-CN/content/admin/configuration/initializing-github-ae.md b/translations/zh-CN/content/admin/configuration/initializing-github-ae.md
index 4aa758be8f..d1008a5e13 100644
--- a/translations/zh-CN/content/admin/configuration/initializing-github-ae.md
+++ b/translations/zh-CN/content/admin/configuration/initializing-github-ae.md
@@ -3,6 +3,9 @@ title: 初始化 GitHub AE
 intro: '要让您的企业准备好使用，您可以完成 {% data variables.product.product_name %} 的初始配置。'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Enterprise
 ---
 
 ### 关于初始化
@@ -79,11 +82,11 @@ versions:
 1. 在“Configure email settings（配置电子邮件设置）”右侧，单击 **Configure（配置）**。 ![用于电子邮件设置配置的"Configure（配置）"按钮](/assets/images/enterprise/configuration/ae-email-configure.png)
 2. 选择 **Enable email**。 这将启用出站和入站电子邮件，但是，为使入站电子邮件运行，您还需要配置 DNS 设置。 更多信息请参阅“[配置 DNS 和防火墙设置以允许传入的电子邮件](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)”。 ![用于电子邮件设置配置的"Enable（启用）"复选框](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. 完成电子邮件服务器设置：
-  - 在 **Server address** 字段中，输入您的 SMTP 服务器的地址。
-  - 在 **Port** 字段中，输入 SMTP 服务器用于发送电子邮件的端口。
-  - 在 **Domain** 字段中，输入您的 SMTP 服务器将随 HELO 响应（如有）发送的域名。
-  - 在 **Authentication** 下拉菜单中，选择您的 SMTP 服务器使用的加密类型。
-  - 在 **No-reply email address** 字段中，输入要在所有通知电子邮件的 From 和 To 字段中使用的电子邮件地址。
+    - 在 **Server address** 字段中，输入您的 SMTP 服务器的地址。
+    - 在 **Port** 字段中，输入 SMTP 服务器用于发送电子邮件的端口。
+    - 在 **Domain** 字段中，输入您的 SMTP 服务器将随 HELO 响应（如有）发送的域名。
+    - 在 **Authentication** 下拉菜单中，选择您的 SMTP 服务器使用的加密类型。
+    - 在 **No-reply email address** 字段中，输入要在所有通知电子邮件的 From 和 To 字段中使用的电子邮件地址。
 
 4. 如果您想丢弃发送到无回复电子邮件地址的所有传入电子邮件，请选中 **Discard email addressed to the no-reply email address**。 ![用于电子邮件设置配置的"Discard（放弃）"复选框](/assets/images/enterprise/configuration/ae-discard-email.png)
 5. 单击 **Test email settings（测试电子邮件设置）**。 ![用于电子邮件设置配置的"Test email settings（测试电子邮件设置）"按钮](/assets/images/enterprise/configuration/ae-test-email.png)
diff --git a/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
index 461772d86e..740c855d58 100644
--- a/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/managing-github-for-mobile-for-your-enterprise.md
@@ -4,8 +4,10 @@ intro: '您可以决定经验证的用户是否可以通过 {% data variables.pr
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for an enterprise on {% data variables.product.product_name %}.'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
   - Enterprise
+  - Mobile
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/zh-CN/content/admin/configuration/network-ports.md b/translations/zh-CN/content/admin/configuration/network-ports.md
index 7a3949118f..0a15b5feb2 100644
--- a/translations/zh-CN/content/admin/configuration/network-ports.md
+++ b/translations/zh-CN/content/admin/configuration/network-ports.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: 根据您需要为管理员、最终用户和电子邮件支持显示的网络服务有选择地打开网络端口。
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
 ---
 
 ### 管理端口
diff --git a/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
index 75b8e4b0d5..5663822f3d 100644
--- a/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md
@@ -4,6 +4,13 @@ shortTitle: 限制网络流量
 intro: 您可以使用 IP 允许列表将企业访问权限限制为来自指定 IP 地址的连接。
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
 ---
 
 ### 关于 IP 允许列表
diff --git a/translations/zh-CN/content/admin/configuration/site-admin-dashboard.md b/translations/zh-CN/content/admin/configuration/site-admin-dashboard.md
index c2aa74f272..bbe086d585 100644
--- a/translations/zh-CN/content/admin/configuration/site-admin-dashboard.md
+++ b/translations/zh-CN/content/admin/configuration/site-admin-dashboard.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/configuration/site-admin-dashboard
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Fundamentals
 ---
 
 要访问仪表板，请在任意页面的右上角中单击 {% octicon "rocket" aria-label="The rocket ship" %}。 ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
diff --git a/translations/zh-CN/content/admin/configuration/troubleshooting-ssl-errors.md b/translations/zh-CN/content/admin/configuration/troubleshooting-ssl-errors.md
index 1dfdb1dd5d..00993f4c48 100644
--- a/translations/zh-CN/content/admin/configuration/troubleshooting-ssl-errors.md
+++ b/translations/zh-CN/content/admin/configuration/troubleshooting-ssl-errors.md
@@ -8,8 +8,14 @@ redirect_from:
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
 ---
 
 ### 将密码从密钥文件中移除
diff --git a/translations/zh-CN/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md b/translations/zh-CN/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
index 3e7fcbef7e..64bcc72fea 100644
--- a/translations/zh-CN/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/zh-CN/content/admin/configuration/using-github-enterprise-server-with-a-load-balancer.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
diff --git a/translations/zh-CN/content/admin/configuration/validating-your-domain-settings.md b/translations/zh-CN/content/admin/configuration/validating-your-domain-settings.md
index fe6f7ad8d7..33e72c9d46 100644
--- a/translations/zh-CN/content/admin/configuration/validating-your-domain-settings.md
+++ b/translations/zh-CN/content/admin/configuration/validating-your-domain-settings.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/configuration/validating-your-domain-settings
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
 ---
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/zh-CN/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..e0f984b4e1
--- /dev/null
+++ b/translations/zh-CN/content/admin/configuration/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,34 @@
+---
+title: Verifying or approving a domain for your enterprise
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### About verification of domains
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About approval of domains
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/zh-CN/content/admin/enterprise-management/about-cluster-nodes.md b/translations/zh-CN/content/admin/enterprise-management/about-cluster-nodes.md
index be66aa23ea..1855a601ad 100644
--- a/translations/zh-CN/content/admin/enterprise-management/about-cluster-nodes.md
+++ b/translations/zh-CN/content/admin/enterprise-management/about-cluster-nodes.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-cluster-nodes
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/about-clustering.md b/translations/zh-CN/content/admin/enterprise-management/about-clustering.md
index 4aa542ea13..47e68bcfa0 100644
--- a/translations/zh-CN/content/admin/enterprise-management/about-clustering.md
+++ b/translations/zh-CN/content/admin/enterprise-management/about-clustering.md
@@ -8,7 +8,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-clustering
 versions:
   enterprise-server: '*'
+type: overview
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/about-geo-replication.md b/translations/zh-CN/content/admin/enterprise-management/about-geo-replication.md
index b0266e657f..7b0e9ee2b7 100644
--- a/translations/zh-CN/content/admin/enterprise-management/about-geo-replication.md
+++ b/translations/zh-CN/content/admin/enterprise-management/about-geo-replication.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-geo-replication
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
 ---
 
 多个活动副本可以提供到达最近副本的较短距离。 举例来说，一个在旧金山、纽约和伦敦均设有办事处的组织可以在靠近纽约的数据中心运行主设备，在靠近旧金山和伦敦的数据中心运行两个副本。 利用地理位置感知 DNS，用户可以转到距离最近的可用服务器，并更快地访问仓库数据。 如果将靠近旧金山的设备指定为主设备，则与伦敦的延迟会比较大，相比而言，将靠近纽约的设备指定为主设备有助于减小主机之间的延迟。
diff --git a/translations/zh-CN/content/admin/enterprise-management/about-high-availability-configuration.md b/translations/zh-CN/content/admin/enterprise-management/about-high-availability-configuration.md
index 130c26e4eb..adbbaab7b5 100644
--- a/translations/zh-CN/content/admin/enterprise-management/about-high-availability-configuration.md
+++ b/translations/zh-CN/content/admin/enterprise-management/about-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 配置高可用性时，会自动设置将所有数据存储（Git 仓库、MySQL、Redis 和 Elasticsearch）单向、异步地从主设备复制到副本。
diff --git a/translations/zh-CN/content/admin/enterprise-management/accessing-the-monitor-dashboard.md b/translations/zh-CN/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
index 38de344fd1..25138f9e41 100644
--- a/translations/zh-CN/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
+++ b/translations/zh-CN/content/admin/enterprise-management/accessing-the-monitor-dashboard.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### 访问监视仪表板
diff --git a/translations/zh-CN/content/admin/enterprise-management/cluster-network-configuration.md b/translations/zh-CN/content/admin/enterprise-management/cluster-network-configuration.md
index 47f8981ca1..84a98f58f3 100644
--- a/translations/zh-CN/content/admin/enterprise-management/cluster-network-configuration.md
+++ b/translations/zh-CN/content/admin/enterprise-management/cluster-network-configuration.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/cluster-network-configuration
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
+  - Networking
 ---
 
 ### 网络考虑因素
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md b/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md
index 13a87dadb2..6b5ffe993f 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-collectd.md
@@ -7,8 +7,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-collectd
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### 设置外部 `collectd` 服务器
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
index c632ed5b80..8d58a51d73 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### 关于集群的高可用性复制
@@ -22,7 +26,7 @@ topics:
 
 #### 硬件和软件
 
-对于活动群集中的每个现有节点，都需要预配第二个具有相同硬件资源的虚拟机。 例如，如果您的群集有 11 个节点，并且每个节点有 12 个 vCP、96 GB 的 RAM 和 750 GB 的附加存储，则必须预配 11 个新虚拟机，每个虚拟机具有 12 个 vCP、64 GB 的 RAM 和 750 GB 的附加存储。
+对于活动群集中的每个现有节点，都需要预配第二个具有相同硬件资源的虚拟机。 例如，如果您的群集有 11 个节点，并且每个节点有 12 个 vCP、96 GB 的 RAM 和 750 GB 的附加存储，则必须预配 11 个新虚拟机，每个虚拟机具有 12 个 vCP、96 GB 的 RAM 和 750 GB 的附加存储。
 
 在每个新虚拟机上，安装活动群集的节点上运行的相同版本 {% data variables.product.prodname_ghe_server %}。 您不需要上传许可证或执行任何其他配置。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)”。
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/creating-a-high-availability-replica.md b/translations/zh-CN/content/admin/enterprise-management/creating-a-high-availability-replica.md
index 5bf5e0caf1..11b4099ecd 100644
--- a/translations/zh-CN/content/admin/enterprise-management/creating-a-high-availability-replica.md
+++ b/translations/zh-CN/content/admin/enterprise-management/creating-a-high-availability-replica.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 {% data reusables.enterprise_installation.replica-limit %}
diff --git a/translations/zh-CN/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md b/translations/zh-CN/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
index 85cb60ea6a..33829b677e 100644
--- a/translations/zh-CN/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
+++ b/translations/zh-CN/content/admin/enterprise-management/differences-between-clustering-and-high-availability-ha.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### 故障场景
diff --git a/translations/zh-CN/content/admin/enterprise-management/enabling-automatic-update-checks.md b/translations/zh-CN/content/admin/enterprise-management/enabling-automatic-update-checks.md
index 2b65064f32..6edd2c9bb1 100644
--- a/translations/zh-CN/content/admin/enterprise-management/enabling-automatic-update-checks.md
+++ b/translations/zh-CN/content/admin/enterprise-management/enabling-automatic-update-checks.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 在 {% data variables.product.product_location %} 的升级包自动下载后，您将收到一条消息，通知您可以升级 {% data variables.product.prodname_ghe_server %}。 升级包会下载到 {% data variables.product.product_location %} 上的 `/var/lib/ghe-updates` 目录中。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)”。
diff --git a/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md b/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md
index a092c30095..1a4738d646 100644
--- a/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md
+++ b/translations/zh-CN/content/admin/enterprise-management/evacuating-a-cluster-node.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md b/translations/zh-CN/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
index ebfd9f8c6d..1ac0606b8e 100644
--- a/translations/zh-CN/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
+++ b/translations/zh-CN/content/admin/enterprise-management/increasing-cpu-or-memory-resources.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
diff --git a/translations/zh-CN/content/admin/enterprise-management/increasing-storage-capacity.md b/translations/zh-CN/content/admin/enterprise-management/increasing-storage-capacity.md
index b84824dad1..f8f1d1e5d2 100644
--- a/translations/zh-CN/content/admin/enterprise-management/increasing-storage-capacity.md
+++ b/translations/zh-CN/content/admin/enterprise-management/increasing-storage-capacity.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
 ---
 
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
@@ -32,6 +36,9 @@ topics:
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. 将设备置于维护模式。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 4. 重启设备，以检测新存储分配。
+  ```shell
+  $ sudo reboot
+  ```
 5. 运行 `ghe-storage-extend` 命令以展开 `/data/user` 文件系统：
   ```shell
   $ ghe-storage-extend
@@ -40,7 +47,10 @@ topics:
 ### 使用新设备增加根分区大小
 
 1. 使用版本与当前设备相同的较大根磁盘来设置新的 {% data variables.product.prodname_ghe_server %} 实例。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
-2. 关闭当前设备。
+2. 关闭当前设备：
+  ```shell
+  $ sudo poweroff
+  ```
 3. 使用虚拟平台工具将数据磁盘从当前设备中拆下。
 4. 将数据磁盘安装到根磁盘较大的新设备上。
 
@@ -57,6 +67,9 @@ topics:
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. 关闭设备。
+4. 关闭设备：
+  ```shell
+  $ sudo poweroff
+  ```
 5. 在虚拟机监控程序中，移除旧的根磁盘，并将新的根磁盘连接到旧的根磁盘的位置。
 6. 启动设备。
diff --git a/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md b/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md
index dcd1527a50..cdeeed2935 100644
--- a/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md
+++ b/translations/zh-CN/content/admin/enterprise-management/initializing-the-cluster.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initializing-the-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
index 6c1890d922..137f6a36cf 100644
--- a/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 故障转移所需的时间取决于手动升级副本和重定向流量所需的时长。 平均时间范围为 2-10 分钟。
diff --git a/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md b/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
index fb40603bee..e2409aa43e 100644
--- a/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
+++ b/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
 versions:
   enterprise-server: '>2.21'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 ### 关于到副本群集的故障转移
diff --git a/translations/zh-CN/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md b/translations/zh-CN/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
index 17f0518af6..b5fa0cfa43 100644
--- a/translations/zh-CN/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/zh-CN/content/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123.md
@@ -12,8 +12,11 @@ redirect_from:
 intro: '要从 {% data variables.product.prodname_enterprise %} 11.10.x 迁移到 2.1.23，您需要设置新的设备实例并迁移之前实例中的数据。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
+  - Upgrades
 ---
 
 支持从 {% data variables.product.prodname_enterprise %} 11.10.348 及更高版本进行迁移。 不支持从 {% data variables.product.prodname_enterprise %} 11.10.348 及更低版本进行迁移。 您必须先通过多次升级过程升级到 11.10.348。 更多信息请参阅 11.10.348 升级程序“[升级到最新版本](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)”。
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-cluster-nodes.md
index cc3dc336c7..b7ee521b75 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-cluster-nodes.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-cluster-nodes.md
@@ -6,8 +6,14 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### 手动检查集群状态
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-using-snmp.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-using-snmp.md
index 315b40ce86..24dc3cccde 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-using-snmp.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-using-snmp.md
@@ -7,8 +7,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 SNMP 是一种用于通过网络监视设备的公共标准。 强烈建议启用 SNMP，以便监视 {% data variables.product.product_location %} 的健康状态并了解何时向主机增加更多内存、存储空间或处理器能力。
diff --git a/translations/zh-CN/content/admin/enterprise-management/recommended-alert-thresholds.md b/translations/zh-CN/content/admin/enterprise-management/recommended-alert-thresholds.md
index c033eb0b5b..abc92c91f4 100644
--- a/translations/zh-CN/content/admin/enterprise-management/recommended-alert-thresholds.md
+++ b/translations/zh-CN/content/admin/enterprise-management/recommended-alert-thresholds.md
@@ -8,8 +8,13 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
 ---
 
 ### 监视存储
diff --git a/translations/zh-CN/content/admin/enterprise-management/recovering-a-high-availability-configuration.md b/translations/zh-CN/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
index bf311927bb..ff2150a7da 100644
--- a/translations/zh-CN/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
+++ b/translations/zh-CN/content/admin/enterprise-management/recovering-a-high-availability-configuration.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - High availability
+  - Infrastructure
 ---
 
 如果故障转移是在计划内进行的，或者与设备的健康状态无关，则可以将之前的主设备用作新的副本设备。 如果故障转移与主设备的问题相关，则最好创建新的副本设备。 更多信息请参阅“[创建高可用性副本](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)”。
diff --git a/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md b/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md
index 1e72046322..4ac85520e4 100644
--- a/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md
+++ b/translations/zh-CN/content/admin/enterprise-management/removing-a-high-availability-replica.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
+  - High availability
   - Enterprise
+  - Infrastructure
 ---
 
 ### 暂时停止复制
diff --git a/translations/zh-CN/content/admin/enterprise-management/replacing-a-cluster-node.md b/translations/zh-CN/content/admin/enterprise-management/replacing-a-cluster-node.md
index f70e0ca19e..12d1dc5548 100644
--- a/translations/zh-CN/content/admin/enterprise-management/replacing-a-cluster-node.md
+++ b/translations/zh-CN/content/admin/enterprise-management/replacing-a-cluster-node.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/replacing-a-cluster-node
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Infrastructure
 ---
 
 {% warning %}
diff --git a/translations/zh-CN/content/admin/enterprise-management/setting-up-external-monitoring.md b/translations/zh-CN/content/admin/enterprise-management/setting-up-external-monitoring.md
index 25c87c56e7..c0779d7470 100644
--- a/translations/zh-CN/content/admin/enterprise-management/setting-up-external-monitoring.md
+++ b/translations/zh-CN/content/admin/enterprise-management/setting-up-external-monitoring.md
@@ -6,8 +6,12 @@ redirect_from:
   - /enterprise/admin/enterprise-management/setting-up-external-monitoring
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
 ---
 
 ### 关于 SNMP
diff --git a/translations/zh-CN/content/admin/enterprise-management/upgrade-requirements.md b/translations/zh-CN/content/admin/enterprise-management/upgrade-requirements.md
index 9b75ba6de4..7b1bc0a66f 100644
--- a/translations/zh-CN/content/admin/enterprise-management/upgrade-requirements.md
+++ b/translations/zh-CN/content/admin/enterprise-management/upgrade-requirements.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrade-requirements
 versions:
   enterprise-server: '*'
+type: reference
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 {% note %}
@@ -41,4 +43,8 @@ curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.
 ```
 使用此数字估算 MySQL 审核日志将需要的磁盘空间大小。 该脚本还会在导入过程中监视可用磁盘空间大小。 在可用磁盘空间大小接近于迁移必需的磁盘空间大小时，监视此数字尤为重要。
 
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
+
+### 后续步骤
+
 查看这些建议和要求后，您可以对 {% data variables.product.prodname_ghe_server %} 进行升级。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}”](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)。
diff --git a/translations/zh-CN/content/admin/enterprise-management/upgrading-a-cluster.md b/translations/zh-CN/content/admin/enterprise-management/upgrading-a-cluster.md
index 013573e131..ad979a9636 100644
--- a/translations/zh-CN/content/admin/enterprise-management/upgrading-a-cluster.md
+++ b/translations/zh-CN/content/admin/enterprise-management/upgrading-a-cluster.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-a-cluster
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Clustering
   - Enterprise
+  - Upgrades
 ---
 
 ### 使用热补丁升级
diff --git a/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md
index 87432116fd..ec51a91c8f 100644
--- a/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md
@@ -15,8 +15,10 @@ redirect_from:
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Upgrades
 ---
 
 ### 准备升级
@@ -31,31 +33,7 @@ topics:
 
   {% endnote %}
 
-{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
-
-### 关于 {% data variables.product.prodname_ghe_server %} 3.0 及更高版本的最低要求
-
-升级到 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本之前，请检查您为实例预配的硬件资源。 {% data variables.product.prodname_ghe_server %} 3.0 引入了 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 等新功能，比 2.22 和更早版本需要更多的资源。 更多信息请参阅 [{% data variables.product.prodname_ghe_server %} 3.0 发行说明](/enterprise-server@3.0/admin/release-notes)。
-
-{% data variables.product.prodname_ghe_server %} 3.0 及更高版本的增加要求在下表中以**粗体**表示。
-
-| 用户许可              |                            vCPU |                                      内存 |                                 附加的存储容量 |  根存储容量 |
-|:----------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------:|
-| 试用版、演示版或 10 个轻度用户 |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ | 200 GB |
-| 10-3000           |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ | 200 GB |
-| 3000-5000         |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB | 200 GB |
-| 5000-8000         | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB | 200 GB |
-| 8000-10000+       | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB | 200 GB |
-
-{% if currentVersion ver_gt "enterprise-server@2.21" %}
-
-有关 {% data variables.product.prodname_actions %} 硬件要求的详细信息，请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)”。
-
-{% endif %}
-
-{% data reusables.enterprise_installation.about-adjusting-resources %}
-
-{% endif %}
+{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
 ### 生成快照
 
@@ -81,7 +59,7 @@ topics:
 | Hyper-V               | VM   | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>                                                                                     |
 | Google Compute Engine | 磁盘   | <https://cloud.google.com/compute/docs/disks/create-snapshots>                                                                                                                                         |
 | VMware                | VM   | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) |
-| XenServer             | VM   | <https://support.citrix.com/article/CTX122978>                                                                                                                                                         |
+| XenServer             | VM   | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>                                                                                                                           |
 
 ### 使用热补丁升级
 
@@ -89,7 +67,12 @@ topics:
 
 {% note %}
 
-**注**：无法在集群环境中使用 {% data variables.enterprise.management_console %} 安装热补丁。 要在集群环境中安装热补丁，请参阅“[升级集群](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)”。
+**{% if currentVersion ver_gt "enterprise-server@2.22" %}注释{% else %}注释{% endif %}**：
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+- 如果 {% data variables.product.product_location %} 正在运行发布候选版本，则无法使用热补丁升级。
+
+- {% endif %}无法在集群环境中使用 {% data variables.enterprise.management_console %} 安装热补丁。 要在集群环境中安装热补丁，请参阅“[升级集群](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)”。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md
index a374e72f59..da540da35b 100644
--- a/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md
+++ b/translations/zh-CN/content/admin/enterprise-support/about-github-enterprise-support.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
index 441f74941a..cd39ff5d71 100644
--- a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md
@@ -7,8 +7,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
index f66bab21dd..4a9c3a2ac9 100644
--- a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
+++ b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/zh-CN/content/admin/enterprise-support/about-support-for-advanced-security.md b/translations/zh-CN/content/admin/enterprise-support/about-support-for-advanced-security.md
index 5fd9764cdd..efec6b8b89 100644
--- a/translations/zh-CN/content/admin/enterprise-support/about-support-for-advanced-security.md
+++ b/translations/zh-CN/content/admin/enterprise-support/about-support-for-advanced-security.md
@@ -5,8 +5,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/about-support-for-advanced-security
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Support
 ---
 
 {% note %}
diff --git a/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md b/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
index f71832661b..c89e1fa68b 100644
--- a/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
+++ b/translations/zh-CN/content/admin/enterprise-support/preparing-to-submit-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 在提交事件单之前，您应当：
diff --git a/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md b/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md
index 3337f5e8dc..32bd941ef6 100644
--- a/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md
+++ b/translations/zh-CN/content/admin/enterprise-support/providing-data-to-github-support.md
@@ -8,8 +8,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### 创建和共享诊断文件
diff --git a/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md b/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md
index 74a7f3d69b..064e7aca25 100644
--- a/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md
+++ b/translations/zh-CN/content/admin/enterprise-support/reaching-github-support.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/enterprise-support/reaching-github-support
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### 使用自动事件单系统
diff --git a/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md b/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md
index abaac294a6..1891fb8814 100644
--- a/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md
+++ b/translations/zh-CN/content/admin/enterprise-support/submitting-a-ticket.md
@@ -6,8 +6,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Support
 ---
 
 ### 关于提交事件单
diff --git a/translations/zh-CN/content/admin/github-actions/about-using-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..616bed18a3
--- /dev/null
+++ b/translations/zh-CN/content/admin/github-actions/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: 关于在企业中使用操作
+intro: '{% data variables.product.product_name %} 包含了大多数 {% data variables.product.prodname_dotcom %} 编写的操作，并且有选项允许访问来自 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_marketplace %} 的其他操作。'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+versions:
+  enterprise-server: '>=2.22'
+  github-ae: next
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
+
+{% data variables.product.prodname_actions %} 工作流程可使用_操作_，它们是一些单独的任务，您可以组合这些操作以创建作业并自定义工作流程。 您可以创建自己的操作，或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+### 与您的企业实例捆绑的正式操作
+
+大多数官方 {% data variables.product.prodname_dotcom %} 编写的操作都会自动与 {% data variables.product.product_name %} 捆绑在一起，并且会在某个时间点从 {% data variables.product.prodname_marketplace %} 获取。
+
+捆绑的官方操作包括 `actions/checkout`、`actions/upload-artifact`、`actions/download-artifact`、`actions/labeler` 以及各种 `actions/setup-` 操作等。 要查看您的企业实例中包含的所有官方操作，请在您的实例上浏览到 `actions` 组织：<code>https://<em>HOSTNAME</em>/actions</code>。
+
+每个操作都是 `actions` 组织中的一个仓库，并且每个操作仓库都包含必要的标记、分支和提交 SHA，您的工作流程可以使用它们来引用操作。 有关如何更新捆绑的正式操作的信息，请参阅“[使用最新版本的正式捆绑操作](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)”。
+
+{% note %}
+
+**注：**在包含自托管运行器的 {% data variables.product.product_name %} 上使用设置操作（例如 `actions/setup-LANGUAGE`）时，您可能需要在没有连接互联网的运行器上设置工具缓存。 更多信息请参阅“[在没有互联网连接的自托管运行器上设置工具缓存](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)”。
+
+{% endnote %}
+
+### 配置对 {% data variables.product.prodname_dotcom_the_website %} 上操作的访问权限
+
+如果企业中的用户需要访问来自 {% data variables.product.prodname_dotcom_the_website %} 或 {% data variables.product.prodname_marketplace %} 的其他操作，有几个配置选项。
+
+推荐的方法是启用自动访问来自 {% data variables.product.prodname_dotcom_the_website %} 的所有操作。 通过使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成可实现这一点。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 {% data reusables.actions.enterprise-limit-actions-use %}
+
+或者，如果您想要更严格地控制企业中允许哪些操作，则可以使用 `actions-sync` 工具手动下载并将操作同步到您的企业实例中。 更多信息请参阅“[手动同步来自 {% data variables.product.prodname_dotcom_the_website %} 的操作](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)”。
diff --git a/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 15bb640215..8ebb821351 100644
--- a/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/zh-CN/content/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -4,8 +4,12 @@ shortTitle: 备份和恢复
 intro: '外部存储提供程序上的 {% data variables.product.prodname_actions %} 数据不会包含在常规 {% data variables.product.prodname_ghe_server %} 备份中，必须单独备份。'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
+  - Backups
   - Enterprise
+  - Infrastructure
 ---
 
 {% data reusables.actions.enterprise-storage-ha-backups %}
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index c157c65d0c..f3b4ceb892 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,26 +1,31 @@
 ---
 title: 启用使用 GitHub Connect 自动访问 GitHub.com 操作
-intro: '要允许企业实例上的 {% data variables.product.prodname_actions %} 使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作，您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_ghe_cloud %}。'
+intro: '要允许企业中的 {% data variables.product.prodname_actions %} 使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作，您可以将企业实例连接到 {% data variables.product.prodname_ghe_cloud %}。'
 permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
 redirect_from:
   - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - GitHub Connect
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
+{% data reusables.actions.ae-beta %}
 
-默认情况下，{% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_actions %} 工作流程不能使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 或 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 的操作。
+默认情况下，{% data variables.product.product_name %} 上的 {% data variables.product.prodname_actions %} 工作流程不能使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 或 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 的操作。
 
-要使 {% data variables.product.prodname_dotcom_the_website %} 上的所有操作可用于您的企业实例，您可以使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 集成。 有关访问 {% data variables.product.prodname_dotcom_the_website %} 上操作的其他方式，请参阅“[关于使用 {% data variables.product.prodname_ghe_server %} 上的操作](/admin/github-actions/about-using-actions-on-github-enterprise-server)”。
+要使 {% data variables.product.prodname_dotcom_the_website %} 上的所有操作可用于您的企业实例，您可以使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成。 有关访问来自 {% data variables.product.prodname_dotcom_the_website %} 的操作的其他方式，请参阅“[关于使用企业中的操作](/admin/github-actions/about-using-actions-in-your-enterprise)”。
 
 ### 启用对所有 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问
 
-在 {% data variables.product.product_location_enterprise %} 上启用访问来自 {% data variables.product.prodname_dotcom_the_website %} 的所有操作之前，必须将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
+在企业实例上启用访问来自 {% data variables.product.prodname_dotcom_the_website %} 的所有操作之前，必须将企业连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
index 0367deec7b..c87bed4bfe 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-amazon-s3-storage.md
@@ -14,7 +14,7 @@ topics:
 
 在启用 {% data variables.product.prodname_actions %} 之前，请确保您已完成以下步骤：
 
-* 创建 Amazon S3 存储桶，用于存储工作流程运行生成的构件。 {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* 创建 Amazon S3 存储桶，用于存储工作流程运行生成的构件。 {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index 595e06f05f..1c896bf146 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -15,7 +15,7 @@ topics:
 在启用 {% data variables.product.prodname_actions %} 之前，请确保您已完成以下步骤：
 
 * 为避免设备上的资源争用，我们建议将 MinIO 与 {% data variables.product.product_location %} 分开托管。
-* 创建用于存储工作流程构件的桶。 要设置存储桶和访问密钥，请参阅 [MinIO 文档](https://docs.min.io/docs/minio-gateway-for-nas.html)。 {% indented_data_reference site.data.reusables.actions.enterprise-s3-permission spaces=2 %}
+* 创建用于存储工作流程构件的桶。 要设置存储桶和访问密钥，请参阅 [MinIO 文档](https://docs.min.io/docs/minio-gateway-for-nas.html)。 {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
index 430bd74b9c..ed743594e5 100644
--- a/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
   github-ae: '*'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Policies
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
index 8844a43d87..a75113dcc7 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-ae.md
@@ -1,9 +1,14 @@
 ---
 title: GitHub Actions for GitHub AE 使用入门
+shortTitle: GitHub Actions 使用入门
 intro: '了解在 {% data variables.product.prodname_ghe_managed %} 上配置 {% data variables.product.prodname_actions %}。'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   github-ae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
 ---
 
 {% data reusables.actions.ae-beta %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
index 33a31e8c62..a4b048f410 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -8,6 +8,7 @@ redirect_from:
 versions:
   enterprise-server: '>=2.22'
 topics:
+  - Actions
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md b/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md
index ceabef5346..851b903896 100644
--- a/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md
+++ b/translations/zh-CN/content/admin/github-actions/high-availability-for-github-actions.md
@@ -3,8 +3,13 @@ title: GitHub Actions 的高可用性
 intro: '在高可用性配置中管理 {% data variables.product.prodname_actions %} 有一些特殊注意事项。'
 versions:
   enterprise-server: '>=3.0'
+type: reference
 topics:
+  - Actions
   - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
 ---
 
 ### {% data variables.product.prodname_actions %} 数据的复制或冗余
diff --git a/translations/zh-CN/content/admin/github-actions/index.md b/translations/zh-CN/content/admin/github-actions/index.md
index e718a20fa7..fe1513a56e 100644
--- a/translations/zh-CN/content/admin/github-actions/index.md
+++ b/translations/zh-CN/content/admin/github-actions/index.md
@@ -29,7 +29,7 @@ topics:
 {% link_in_list /enforcing-github-actions-policies-for-your-enterprise %}
 
 {% topic_link_in_list /managing-access-to-actions-from-githubcom %}
-  {% link_in_list /about-using-actions-on-github-enterprise-server %}
+  {% link_in_list /about-using-actions-in-your-enterprise %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
   {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
diff --git a/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
index cf1e42b960..4c16ed66a4 100644
--- a/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
+++ b/translations/zh-CN/content/admin/github-actions/manually-syncing-actions-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
 title: 手动从 GitHub.com 同步操作
-intro: '对于需要访问 {% data variables.product.prodname_dotcom_the_website %} 上操作的用户，您可以将特定操作同步到 {% data variables.product.prodname_ghe_server %} 实例。'
+intro: '对于需要访问 {% data variables.product.prodname_dotcom_the_website %} 上操作的用户，您可以将特定操作同步到企业。'
 redirect_from:
   - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
 versions:
@@ -12,16 +12,17 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-推荐的允许从 {% data variables.product.prodname_dotcom_the_website %} 访问操作的方法是启用自动访问所有操作。 通过使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 集成可实现这一点。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。
+推荐的允许从 {% data variables.product.prodname_dotcom_the_website %} 访问操作的方法是启用自动访问所有操作。 通过使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成可实现这一点。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。
 
-但是，如果您想更严格地控制企业中允许的操作，您可以按照本指南使用 {% data variables.product.company_short %} 的开源 [`actions-sync`](https://github.com/actions/actions-sync) 工具将各个操作仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到企业实例。
+但是，如果您想更严格地控制企业中允许的操作，您可以按照本指南使用 {% data variables.product.company_short %} 的开源 [`actions-sync`](https://github.com/actions/actions-sync) 工具将各个操作仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到企业。
 
 ### 关于 `actions-sync` 工具
 
-`actions-sync` 工具必须在可以访问 {% data variables.product.prodname_dotcom_the_website %} API 和 {% data variables.product.prodname_ghe_server %} 实例的 API 的计算机上运行。 计算机不需要同时连接到两者。
+`actions-sync` 工具必须在可以访问 {% data variables.product.prodname_dotcom_the_website %} API 和 {% data variables.product.product_name %} 实例的 API 的计算机上运行。 计算机不需要同时连接到两者。
 
 如果计算机可以同时访问这两个系统，您可以使用单一 `actions-sync sync` 命令进行同步。 如果您一次只能访问一个系统，您可以使用 `actions-sync pull` 和 `push` 命令。
 
@@ -29,17 +30,17 @@ topics:
 
 ### 基本要求
 
-* 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业实例中。 以下示例演示如何将操作同步到企业实例上名为 `synced-actions` 的组织。 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
-* 您必须在企业实例上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
-* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization.
+* 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业中。 以下示例演示如何将操作同步到名为 `synced-actions` 的组织。 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
+* 您必须在企业上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+* 如果您想同步 {% data variables.product.product_location %} 上 `actions` 组织中的捆绑操作，您必须是 `actions` 组织的所有者。
 
   {% note %}
 
-  **Note:** By default, even site administrators are not owners of the bundled `actions` organization.
+  **注意：** 默认情况下，即使站点管理员也不是捆绑的 `actions` 组织的所有者。
 
   {% endnote %}
 
-  Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)."
+  站点管理员可以在管理 shell 中使用 `ghe-org-admin-promot-promotion` 命令将用户升级为捆绑的 `actions` 组织的所有者。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”和“[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)”。
 
   ```shell
   ghe-org-admin-promote -u <em>USERNAME</em> -o actions
@@ -51,7 +52,7 @@ topics:
 
 {% note %}
 
-**注：**此示例使用 `actions-sync sync` 命令 它要求从您的计算机同时访问 {% data variables.product.prodname_dotcom_the_website %} API 和 {% data variables.product.prodname_ghe_server %} 实例的 API。 如果您一次只能访问一个系统，您可以使用 `actions-sync pull` 和 `push` 命令。 更多信息请参阅 [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances)。
+**注：**此示例使用 `actions-sync sync` 命令 它要求从您的计算机同时访问 {% data variables.product.prodname_dotcom_the_website %} API 和企业实例的 API。 如果您一次只能访问一个系统，您可以使用 `actions-sync pull` 和 `push` 命令。 更多信息请参阅 [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances)。
 
 {% endnote %}
 
@@ -74,10 +75,10 @@ topics:
    * `--destination-url`：目标企业实例的 URL。
    * `--repo-name`：要同步的操作仓库。 这将使用格式 `owner/repository:destination_owner/destination_repository`。
 
-     * 上面的示例将 [`docker/build-push-action`](https://github.com/docker/build-push-action) 仓库同步到目标 {% data variables.product.prodname_ghe_server %} 实例上的 `synced-actions/docker-build-push-action` 仓库。 在运行上述命令之前，您必须在企业实例上创建名为 `synced-actions` 的组织。
-     * 如果您省略 `:destination_owners/destination_repost`，工具将使用企业实例的原始所有者和仓库名称。 在运行命令之前，必须在实例上创建一个与操作的所有者名称匹配的新组织。 考虑使用一个中心组织来存储实例上同步的操作，因为这样在同步来自不同所有者的操作时，将无需创建多个新的组织。
+     * 上面的示例将 [`docker/build-push-action`](https://github.com/docker/build-push-action) 仓库同步到目标企业实例上的 `synced-actions/docker-build-push-action` 仓库。 在运行上述命令之前，您必须在企业中创建名为 `synced-actions` 的组织。
+     * 如果您省略 `:destination_owners/destination_repost`，工具将使用企业的原始所有者和仓库名称。 在运行命令之前，必须在企业中创建一个与操作的所有者名称匹配的新组织。 考虑使用一个中心组织来存储企业中同步的操作，因为这样在同步来自不同所有者的操作时，将无需创建多个新的组织。
      * 将 `--repo-name` 参数替换为 `--repo-name-list` 或 `--repo-name-list-file` 便可同步多个操作。 更多信息请参阅 [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync)。
-1. 在企业实例上创建操作仓库后，企业中的人员可以使用目标仓库在其工作流程中引用操作。 对于上面显示的示例操作：
+1. 在企业中创建操作仓库后，企业中的人员可以使用目标仓库在其工作流程中引用操作。 对于上面显示的示例操作：
 
    ```yaml
    uses: synced-actions/docker-build-push-action@v1
diff --git a/translations/zh-CN/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/zh-CN/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 3117a5208c..c2a72b8ba3 100644
--- a/translations/zh-CN/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/zh-CN/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -12,12 +12,13 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
 ### 关于包含的设置操作和运行器工具缓存
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-大多数官方 {% data variables.product.prodname_dotcom %} 编写的操作都会自动与 {% data variables.product.prodname_ghe_server %} 捆绑在一起。 但是，没有接入互联网的自托管运行器需要进行一些配置，然后才能使用包含的 `actions/setup-LANGUAGE` 操作，例如 `setup-node`。
+大多数官方 {% data variables.product.prodname_dotcom %} 编写的操作都会自动与 {% data variables.product.product_name %} 捆绑在一起。 但是，没有接入互联网的自托管运行器需要进行一些配置，然后才能使用包含的 `actions/setup-LANGUAGE` 操作，例如 `setup-node`。
 
 `actions/setup-LANGUAGE` 操作通常需要接入互联网才能将所需的环境二进制文件下载到运行器的工具缓存。 没有互联网连接的自托管运行器无法下载二进制文件，所以您必须手动填充运行器上的工具缓存。
 
diff --git a/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md b/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md
index 236b6693ec..5837695bab 100644
--- a/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md
+++ b/translations/zh-CN/content/admin/github-actions/using-a-staging-environment.md
@@ -3,8 +3,12 @@ title: 使用暂存环境
 intro: '了解在 {% data variables.product.prodname_ghe_server %} 暂存环境中使用 {% data variables.product.prodname_actions %}。'
 versions:
   enterprise-server: '>=3.0'
+type: how_to
 topics:
+  - Actions
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 为 {% data variables.product.product_location %} 提供临时或测试环境会有用，这样您就可以在生产环境中实施更新或新功能之前进行测试。
diff --git a/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
index 1c7c49f409..442315cea0 100644
--- a/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -1,6 +1,6 @@
 ---
 title: 使用官方捆绑操作的最新版本
-intro: '您可以更新与 {% data variables.product.prodname_ghe_server %} 实例捆绑的操作，或直接从 {% data variables.product.prodname_dotcom_the_website %} 使用操作。'
+intro: '您可以更新与企业捆绑的操作，或直接从 {% data variables.product.prodname_dotcom_the_website %} 使用操作。'
 versions:
   enterprise-server: '>=2.22'
   github-ae: next
@@ -10,37 +10,33 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.ae-beta %}
 
-您的 {% data variables.product.prodname_ghe_server %} 实例包含一些您可以在工作流程中使用的内置操作。 有关捆绑操作的更多信息，请参阅[“与 {% data variables.product.prodname_ghe_server %} 捆绑的正式操作”](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server)。
+您的企业实例包含一些您可以在工作流程中使用的内置操作。 有关捆绑操作的更多信息，请参阅[“与企业实例捆绑的正式操作”](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)。
 
-这些捆绑的操作是在 https://github.com/actions 上找到的正式操作的即时快照；因此，这些操作可能是可以更新的旧版本。 要更新这些操作，您可以使用 `actions-sync` 工具将更新的操作与 {% data variables.product.prodname_dotcom_the_website %} 同步。
+这些捆绑的操作是在 https://github.com/actions 上找到的正式操作的即时快照；因此，这些操作可能有更新的版本。 您可以使用 `actions-sync` 工具更新这些操作，也可以配置 {% data variables.product.prodname_github_connect %} 允许访问 {% data variables.product.prodname_dotcom_the_website %} 上的最新操作。 以下各节介绍了这些选项。
 
-或者，如果您的 {% data variables.product.prodname_ghe_server %} 实例已启用 {% data variables.product.prodname_github_connect %}，则您还有其他选项可以使用来自 {% data variables.product.prodname_dotcom_the_website %} 的最新操作：
+### 使用 `actions-sync` 更新捆绑的操作
 
-- 您的工作流程文件可以直接引用仅存在于 {% data variables.product.prodname_dotcom_the_website %} 上的特定标记。
-- 要强制工作流程文件在 {% data variables.product.prodname_dotcom_the_website %} 上使用操作，您可以编辑分配给捆绑操作的标记。
+要更新捆绑的操作，您可以使用 `actions-sync` 工具来更新快照。 有关使用 `actions-sync` 的更多信息，请参阅“[手动从 {% data variables.product.prodname_dotcom_the_website %} 同步选项](/admin/github-actions/manually-syncing-actions-from-githubcom)”。
 
-以下各节将更详细地介绍这些选项。
+### 使用 {% data variables.product.prodname_github_connect %} 访问最新操作
 
-### 使用操作同步更新捆绑操作
+您可以使用 {% data variables.product.prodname_github_connect %} 允许 {% data variables.product.product_name %} 使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。
 
-要更新捆绑操作，您可以使用 `actions-sync` 工具将操作与 {% data variables.product.prodname_dotcom_the_website %} 同步。 有关使用 `actions-sync` 的更多信息，请参阅“[手动从 {% data variables.product.prodname_dotcom_the_website %} 同步选项](/admin/github-actions/manually-syncing-actions-from-githubcom)”。
+配置 {% data variables.product.prodname_github_connect %} 后，您可以在实例上的 `actions` 组织中删除其本地仓库，以使用最新版本的操作。 例如，如果您的企业实例使用 `actions/checkout@v1` 操作，而且您需要使用在您的企业实例中不可用的 `actions/checkout@v2` ，执行以下步骤便可使用来自 {% data variables.product.prodname_dotcom_the_website %} 的最新 `checkout` 操作：
 
-### 从 {% data variables.product.prodname_dotcom_the_website %} 使用操作
+1. 默认情况下，站点管理员不是捆绑的操作组织的所有者。 要获得删除 `checkout` 仓库所需的访问权限，请使用 `ghe-org-admin-promote` 命令将用户升级为捆绑的 `actions` 组织的所有者。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”和“[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)”。 例如：
 
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-一旦配置，您即可手动指定工作流程文件中所需的版本，从 {% data variables.product.prodname_dotcom_the_website %} 使用操作的新版本。 例如，从 {% data variables.product.prodname_dotcom_the_website %} 使用 `v2.2.` 版的 `actions/setup-python`，您可以在工作流程文件中指定标记 `actions/setup-python@v2.2.1`。
-
-### 删除特定操作的标记以使用最新版本
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-如果您删除之前分配给操作的版本标记，{% data variables.product.prodname_ghe_server %} 将检查 {% data variables.product.prodname_dotcom_the_website %} 是否有所需的标记。 有关使用标记的更多信息，请参阅“[查看标记](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)”。
-
-例如，要从 {% data variables.product.prodname_dotcom_the_website %} 使用 `v2.2.1` 版的 `actions/setup-python`：
-
-1. 在 {% data variables.product.prodname_ghe_server %} 中，从 `actions/setup-python` 仓库中删除 `v2` 标记。
-1. 创建同时使用 `actions/setup-python` 与 `v2` 标记的工作流程。
-
-当工作流程无法在 {% data variables.product.prodname_ghe_server %} 上找到指定的 `v2` 标记时，它会检查 {% data variables.product.prodname_dotcom_the_website %} 是否有所需的标记。 如果找到该操作的标记版本，{% data variables.product.prodname_ghe_server %} 将使用 {% data variables.product.prodname_dotcom_the_website %} 中的版本。
+   ```shell
+   $ ghe-org-admin-promote -u octocat -o actions
+    Do you want to give organization admin privileges for actions to octocat? (y/N) y
+    Making octocat an admin of actions
+     --> Adding octocat as an admin of actions
+     --> octocat is now an admin of the actions organization
+     --> Done.
+   ```
+1. 在您的 {% data variables.product.product_name %} 实例中，删除 `actions` 组织中的 `checkout` 仓库。 有关如何删除仓库的信息，请参阅“[删除仓库](/github/administering-a-repository/deleting-a-repository)”。
+1. 建议您在不再需要管理性访问后离开 `actions` 组织。 更多信息请参阅“[将您自己从组织删除](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)”。
+1. 配置您的工作流程的 YAML 以使用 `actions/checkout@v2`。
+1. 每次您的工作流程运行时，运行器将从 {% data variables.product.prodname_dotcom_the_website %} 中使用 `v2` 版本的 `actions/checkout`。
diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md
new file mode 100644
index 0000000000..541044f8fc
--- /dev/null
+++ b/translations/zh-CN/content/admin/guides.md
@@ -0,0 +1,105 @@
+---
+title: GitHub Enterprise guides
+shortTitle: 指南
+intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  enterprise-server: '*'
+  github-ae: '*'
+learningTracks:
+  - '{% if currentVersion == "github-ae@latest" %}get_started_with_github_ae{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}deploy_an_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}upgrade_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}increase_fault_tolerance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion %}improve_security_of_your_instance{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_actions{% endif %}'
+  - '{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/audited-actions
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/creating-teams
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+---
+
diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md
index be482196b7..6d26928d40 100644
--- a/translations/zh-CN/content/admin/index.md
+++ b/translations/zh-CN/content/admin/index.md
@@ -1,32 +1,49 @@
 ---
-title: 企业管理员
-redirect_from:
-  - /enterprise/admin/hidden/migrating-from-github-fi/
-  - /enterprise/admin
+title: GitHub Enterprise Documentation
+shortTitle: GitHub Enterprise
 intro: '适用于{% if enterpriseServerVersions contains currentVersion %}部署、{% endif %}配置{% if enterpriseServerVersions contains currentVersion %}、{% endif %}和管理 {% data variables.product.product_name %} 的企业管理员、系统管理员及安全专家的文档和指南。'
+introLinks:
+  overview: '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/system-overview{% elsif currentVersion == "github-ae@latest" %}/admin/overview/about-github-ae{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/managing-billing-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/enterprise-management/upgrading-github-enterprise-server{% endif %}'
+  guideCards:
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% if currentVersion ver_gt "enterprise-server@2.22" %} /admin/configuration/configuring-advanced-security-features {% elsif currentVersion ver_lt "enterprise-server@3.0" %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+  popular:
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/github-ae-release-notes{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/installation{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% if currentVersion == "github-ae@latest" %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/overview/managing-your-github-enterprise-license{% endif %}'
+    - '{% if enterpriseServerVersions contains currentVersion %}/admin/configuration/command-line-utilities{% endif %}'
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
 versions:
   enterprise-server: '*'
   github-ae: '*'
 ---
 
-{% link_with_intro /overview %}
-
-{% link_with_intro /installation %}
-
-{% link_with_intro /configuration %}
-
-{% link_with_intro /authentication %}
-
-{% link_with_intro /user-management %}
-
-{% link_with_intro /policies %}
-
-{% link_with_intro /enterprise-management %}
-
-{% link_with_intro /github-actions %}
-
-{% link_with_intro /packages %}
-
-{% link_with_intro /enterprise-support %}
-
-{% link_with_intro /release-notes %}
+<!-- {% link_with_intro /overview %}. -->
+<!-- {% link_with_intro /installation %}. -->
+<!-- {% link_with_intro /configuration %}. -->
+<!-- {% link_with_intro /authentication %}. -->
+<!-- {% link_with_intro /user-management %}. -->
+<!-- {% link_with_intro /policies %}. -->
+<!-- {% link_with_intro /enterprise-management %}. -->
+<!-- {% link_with_intro /github-actions %}. -->
+<!-- {% link_with_intro /packages %}. -->
+<!-- {% link_with_intro /enterprise-support %}. -->
+<!-- {% link_with_intro /release-notes %}. -->
diff --git a/translations/zh-CN/content/admin/installation/index.md b/translations/zh-CN/content/admin/installation/index.md
index 550a1d42ce..36fb546d84 100644
--- a/translations/zh-CN/content/admin/installation/index.md
+++ b/translations/zh-CN/content/admin/installation/index.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/installation
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Fundamentals
+  - Set up
 ---
 
 如需了解更多信息或购买 {% data variables.product.prodname_enterprise %}，请参阅 [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise)。
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md b/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md
index c03d07f414..fdef902e0f 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-staging-instance.md
@@ -5,8 +5,11 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Infrastructure
+  - Upgrades
 ---
 
 {% tip %}
diff --git a/translations/zh-CN/content/admin/overview/about-data-residency.md b/translations/zh-CN/content/admin/overview/about-data-residency.md
index 4fa536fb52..19ed4a67ee 100644
--- a/translations/zh-CN/content/admin/overview/about-data-residency.md
+++ b/translations/zh-CN/content/admin/overview/about-data-residency.md
@@ -3,6 +3,10 @@ title: 关于数据保存
 intro: '您可以选择 {% data variables.product.product_name %} 为您的企业存储所有客户数据的地理位置。'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 {% data reusables.github-ae.github-ae-enables-you %} 您可以选择为 {% data variables.product.product_location %} 存储所有客户数据的地理位置，企业成员可以从世界任何地方访问 {% data variables.product.product_name %}。
diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md
index fdaf0e4c8b..fb7a22c7b0 100644
--- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md
@@ -8,7 +8,9 @@ versions:
   enterprise-server: '>=2.20'
   github-ae: '*'
 topics:
+  - Accounts
   - Enterprise
+  - Fundamentals
 ---
 
 ### About enterprise accounts on {% data variables.product.product_name %}
diff --git a/translations/zh-CN/content/admin/overview/about-github-ae.md b/translations/zh-CN/content/admin/overview/about-github-ae.md
index d912cfbb55..3880a123ec 100644
--- a/translations/zh-CN/content/admin/overview/about-github-ae.md
+++ b/translations/zh-CN/content/admin/overview/about-github-ae.md
@@ -3,6 +3,10 @@ title: 关于 GitHub AE
 intro: '{% data variables.product.prodname_ghe_managed %} 是一种在云端使用 {% data variables.product.prodname_dotcom %} 的安全性更强的标准方法。'
 versions:
   github-ae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
 ---
 
 ### 关于 {% data variables.product.prodname_ghe_managed %}
@@ -21,7 +25,7 @@ versions:
 
 ### 由您加密
 
-所有客户数据都会静态加密，并且您可以提供自己的加密密钥，根据加密策略来加密数据。 您的密钥以及对您所有数据的访问由您控制。 更多信息请参阅“[为企业配置数据加密](/admin/configuration/configuring-data-encryption-for-your-enterprise)”。
+所有客户数据都是加密的。 更多信息请参阅“[为企业配置数据加密](/admin/configuration/configuring-data-encryption-for-your-enterprise)”。
 
 ### 隔离的帐户
 
diff --git a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md
index f9de512538..32cebcb0fa 100644
--- a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md
@@ -5,13 +5,15 @@ intro: '{% if currentVersion == "github-ae@latest" %}您的 {% data variables.pr
 versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
+type: overview
 topics:
   - Enterprise
+  - Upgrades
 ---
 
-{% data variables.product.product_name %} 正在不断改进，通过主要和次要版本引入新功能和漏洞补丁。 {% if currentversion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务，因此 {% data variables.product.company_short %} 可完成企业的升级过程。{% endif %}
+{% data variables.product.product_name %} 正在不断改进，通过主要和次要版本引入新功能和漏洞补丁。 {% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务，因此 {% data variables.product.company_short %} 可完成企业的升级过程。{% endif %}
 
-主要版本包括新功能和功能升级，通常{% if currentVersion == "github-ae@latest" %}每几个星期或几个月{% else %}每季度{% endif %}进行一次。 {% if currentversion == "github-ae@latest" %}{% data variables.product.company_short %} 会将您的企业升级到最新的主要版本。 您的企业如有任何计划内的停机，都会提前通知您。{% endif %}
+主要版本包括新功能和功能升级，通常{% if currentVersion == "github-ae@latest" %}每几个星期或几个月{% else %}每季度{% endif %}进行一次。 {% if currentVersion == "github-ae@latest" %}{% data variables.product.company_short %} 会将您的企业升级到最新的主要版本。 您的企业如有任何计划内的停机，都会提前通知您。{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion %}
 
diff --git a/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md b/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md
index d95eb4005a..00845f5c3f 100644
--- a/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/overview/managing-billing-for-your-enterprise.md
@@ -26,13 +26,13 @@ topics:
 | 用户        | 许可日期                                          | 计入的天数 | 费用     |
 | --------- | --------------------------------------------- | ----- | ------ |
 | @octocat  | 1 月 1 日至 1 月 31 日                             | 31    | $39    |
-| @robocat  | 2 月 1 日至 2 月 28 日                             | 29    | $35.23 |
+| @robocat  | 2 月 1 日至 2 月 28 日                             | 28    | $35.23 |
 | @devtocat | 1 月 15 日至 1 月 31 日                            | 17    | $21.39 |
 | @doctocat | 1 月 1 日至 1 月 15 日                             | 31    | $39    |
 | @prodocat | 1 月 7 日至 1 月 15 日                             | 25    | $31.45 |
 | @monalisa | 1 月 1 日至 1 月 7 日，<br>1 月 15 日至 1 月 31 日 | 31    | $39    |
 
-企业可以包括一个或多个实例。 {% data variables.product.prodname_ghe_managed %} 的每个实例至少 500 个用户。 {% data variables.product.company_short %} 按每个实例至少 500 个用户计费，即使当天拥有许可证的用户少于 500 个也一样。
+{% data variables.product.prodname_ghe_managed %} 的每个实例至少 500 个用户。 {% data variables.product.company_short %} 按每个实例至少 500 个用户计费，即使当天拥有许可证的用户少于 500 个也一样。
 
 您可以在[Azure 帐户门户](https://portal.azure.com)中看到您当前的使用情况。
 
diff --git a/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md b/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md
index 173022f63d..0477409675 100644
--- a/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md
+++ b/translations/zh-CN/content/admin/overview/managing-your-github-enterprise-license.md
@@ -56,7 +56,7 @@ topics:
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
 3. 在左侧边栏中，单击 **Enterprise licensing（企业许可）**。 ![企业帐户设置侧边栏中的"Enterprise licensing（企业许可）"选项卡](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-4. 检查您当前的 {% data variables.product.prodname_enterprise %} 许可，以及已使用和可用的用户许可。
+4. 检查您当前的 {% data variables.product.prodname_enterprise %} 许可，以及已使用和可用的用户许可。 {% if currentVersion ver_gt "enterprise-server@3.0" %}If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
 
 ### 自动将用户许可使用情况同步到 {% data variables.product.prodname_ghe_cloud %}
 
diff --git a/translations/zh-CN/content/admin/overview/system-overview.md b/translations/zh-CN/content/admin/overview/system-overview.md
index cb3778533d..ddc965df51 100644
--- a/translations/zh-CN/content/admin/overview/system-overview.md
+++ b/translations/zh-CN/content/admin/overview/system-overview.md
@@ -6,8 +6,13 @@ redirect_from:
   - /enterprise/admin/overview/system-overview
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
 ---
 
 ### 存储架构
diff --git a/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
index d3c9efdda0..526b86c4b1 100644
--- a/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -6,8 +6,10 @@ redirect_from:
   - /admin/packages/configuring-packages-support-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
index 903fdbee9c..ebc57bbed3 100644
--- a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -1,13 +1,16 @@
 ---
 title: 企业 GitHub Packages 使用入门
+shortTitle: Getting started with GitHub Packages
 intro: '您可以通过启用功能、配置第三方存储、配置您想要支持的生态系统以及更新您的 TLS 证书，开始在 {% data variables.product.product_location %} 上使用 {% data variables.product.prodname_registry %}。'
 redirect_from:
   - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
   - /admin/packages/enabling-github-packages-for-your-enterprise
 versions:
   enterprise-server: '>=2.22'
+type: how_to
 topics:
   - Enterprise
+  - Packages
 ---
 
 {% if currentVersion == "enterprise-server@2.22" %}
diff --git a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
index 9beac566b6..86d73c980a 100644
--- a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
+++ b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -3,8 +3,11 @@ title: 为 GitHub Packages 配置 MinIO 存储桶的快速入门
 intro: '配置您的自定义 MinIO 存储桶，用于 {% data variables.product.prodname_registry %}。'
 versions:
   enterprise-server: '>=2.22'
+type: quick_start
 topics:
+  - Packages
   - Enterprise
+  - Storage
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/zh-CN/content/admin/policies/about-pre-receive-hooks.md b/translations/zh-CN/content/admin/policies/about-pre-receive-hooks.md
index 4898f1de1b..3a266bcea1 100644
--- a/translations/zh-CN/content/admin/policies/about-pre-receive-hooks.md
+++ b/translations/zh-CN/content/admin/policies/about-pre-receive-hooks.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/about-pre-receive-hooks
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 当发生推送时，每个脚本都在隔离的环境中运行，并且可以对推送的内容执行检查。 如果 exit status 为 0，脚本将导致接受推送，如果 exit status 不为零，则会拒绝接受推送。
diff --git a/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-environment.md b/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-environment.md
index 5dcc84acab..1b145b49bf 100644
--- a/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-environment.md
+++ b/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-environment.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 {% data variables.product.prodname_ghe_server %} 的预接收环境是 Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot) 环境。 由于预接收挂钩会在每个推送事件上执行，因此它们应该快速且轻量化。 这类检查需要的环境通常极少。
diff --git a/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md
index bad44481c8..ac01722fb4 100644
--- a/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md
+++ b/translations/zh-CN/content/admin/policies/creating-a-pre-receive-hook-script.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/creating-a-pre-receive-hook-script
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 您可以在 [`github/platform-samples` 仓库](https://github.com/github/platform-samples/tree/master/pre-receive-hooks)中查看 {% data variables.product.prodname_ghe_server %} 的预接收挂钩示例。
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
index be577596b3..6db0613728 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -5,6 +5,13 @@ product: '{% data reusables.gated-features.ghas %}'
 versions:
   enterprise-server: '>=3.1'
   github-ae: next
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Policies
+  - Secret scanning
+  - Security
 ---
 
 ### 关于 {% data variables.product.prodname_GH_advanced_security %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
index 1aaf1258ba..18b63733ed 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-repository-management-policies-in-your-enterprise.md
@@ -28,8 +28,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
 ---
 
 ### 配置企业中新仓库的默认可见性
diff --git a/translations/zh-CN/content/admin/policies/index.md b/translations/zh-CN/content/admin/policies/index.md
index 8efd04b7c0..cd4e3372a6 100644
--- a/translations/zh-CN/content/admin/policies/index.md
+++ b/translations/zh-CN/content/admin/policies/index.md
@@ -16,6 +16,7 @@ topics:
 
 {% topic_link_in_list /enforcing-policies-for-your-enterprise %}
     {% link_in_list /enforcing-repository-management-policies-in-your-enterprise %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise %}
     {% link_in_list /enforcing-policies-for-advanced-security-in-your-enterprise %}
 {% topic_link_in_list /enforcing-policy-with-pre-receive-hooks %}
     {% link_in_list /about-pre-receive-hooks %}
diff --git a/translations/zh-CN/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/zh-CN/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index e4d0bbdc81..28c36984d6 100644
--- a/translations/zh-CN/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/zh-CN/content/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -7,8 +7,11 @@ redirect_from:
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Pre-receive hooks
 ---
 
 ### 创建预接收挂钩
diff --git a/translations/zh-CN/content/admin/policies/restricting-email-notifications-for-your-enterprise.md b/translations/zh-CN/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..5aec7b5c73
--- /dev/null
+++ b/translations/zh-CN/content/admin/policies/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: Restricting email notifications for your enterprise
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  enterprise-server: '>=3.2'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### 关于企业帐户的电子邮件限制
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### 限制企业帐户的电子邮件通知
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/zh-CN/content/admin/release-notes.md b/translations/zh-CN/content/admin/release-notes.md
index 948af3f4e3..e25865b9e5 100644
--- a/translations/zh-CN/content/admin/release-notes.md
+++ b/translations/zh-CN/content/admin/release-notes.md
@@ -6,5 +6,6 @@ versions:
   enterprise-server: '*'
 topics:
   - Enterprise
+  - Upgrades
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/about-migrations.md b/translations/zh-CN/content/admin/user-management/about-migrations.md
index 0aecc1f117..9f74369da9 100644
--- a/translations/zh-CN/content/admin/user-management/about-migrations.md
+++ b/translations/zh-CN/content/admin/user-management/about-migrations.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/about-migrations
 versions:
   enterprise-server: '*'
+type: overview
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### 迁移类型
diff --git a/translations/zh-CN/content/admin/user-management/adding-people-to-teams.md b/translations/zh-CN/content/admin/user-management/adding-people-to-teams.md
index 13806fca46..eba0ebfacb 100644
--- a/translations/zh-CN/content/admin/user-management/adding-people-to-teams.md
+++ b/translations/zh-CN/content/admin/user-management/adding-people-to-teams.md
@@ -8,8 +8,12 @@ redirect_from:
 intro: '创建团队后，组织管理员可以将用户从 {% data variables.product.product_location %} 添加到团队并决定他们可以访问哪些仓库。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 每个团队都有自己单独定义的[组织所拥有仓库的访问权限](/articles/permission-levels-for-an-organization)。
diff --git a/translations/zh-CN/content/admin/user-management/audit-logging.md b/translations/zh-CN/content/admin/user-management/audit-logging.md
index cb2217dcd5..d9e891fa6f 100644
--- a/translations/zh-CN/content/admin/user-management/audit-logging.md
+++ b/translations/zh-CN/content/admin/user-management/audit-logging.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 有关完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。 有关查找特定操作的详细信息，请参阅“[搜索审核日志](/admin/user-management/searching-the-audit-log)”。
diff --git a/translations/zh-CN/content/admin/user-management/audited-actions.md b/translations/zh-CN/content/admin/user-management/audited-actions.md
index b408c302bb..d959936c27 100644
--- a/translations/zh-CN/content/admin/user-management/audited-actions.md
+++ b/translations/zh-CN/content/admin/user-management/audited-actions.md
@@ -9,8 +9,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
+  - Auditing
   - Enterprise
+  - Security
 ---
 
 #### 身份验证
diff --git a/translations/zh-CN/content/admin/user-management/auditing-ssh-keys.md b/translations/zh-CN/content/admin/user-management/auditing-ssh-keys.md
index 6d39914829..0f62bc60fa 100644
--- a/translations/zh-CN/content/admin/user-management/auditing-ssh-keys.md
+++ b/translations/zh-CN/content/admin/user-management/auditing-ssh-keys.md
@@ -7,8 +7,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Security
+  - SSH
 ---
 
 发起后，审计会禁用所有现有的 SSH 密钥并强制用户批准或拒绝它们，然后他们才能克隆、拉取任意仓库或推送至仓库。 审核在员工或合同工离开公司时十分有用，您需要确保所有密钥均已验证。
diff --git a/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md b/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md
index 438d3dfaf2..a3170ef132 100644
--- a/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/auditing-users-across-your-enterprise.md
@@ -8,8 +8,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Organizations
+  - Security
+  - User account
 ---
 
 ### 访问审核日志
diff --git a/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md b/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md
index 3256fe67c6..522b14de88 100644
--- a/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md
+++ b/translations/zh-CN/content/admin/user-management/best-practices-for-user-security.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: reference
 topics:
   - Enterprise
+  - Security
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
index 47dadce6d6..f42766384d 100644
--- a/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/configuring-git-large-file-storage-for-your-enterprise.md
@@ -15,8 +15,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Git
   - Enterprise
+  - LFS
+  - Storage
 ---
 
 ### 关于 {% data variables.large_files.product_name_long %}
diff --git a/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md b/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md
index b474480708..0c19bc204c 100644
--- a/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md
+++ b/translations/zh-CN/content/admin/user-management/configuring-visibility-for-organization-membership.md
@@ -6,8 +6,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 {% if enterpriseServerVersions contains currentVersion %}
diff --git a/translations/zh-CN/content/admin/user-management/continuous-integration-using-jenkins.md b/translations/zh-CN/content/admin/user-management/continuous-integration-using-jenkins.md
index 2195596c30..ed6d0f0f07 100644
--- a/translations/zh-CN/content/admin/user-management/continuous-integration-using-jenkins.md
+++ b/translations/zh-CN/content/admin/user-management/continuous-integration-using-jenkins.md
@@ -6,7 +6,9 @@ redirect_from:
   - /enterprise/admin/user-management/continuous-integration-using-jenkins
 versions:
   enterprise-server: '*'
+type: reference
 topics:
+  - CI
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/creating-teams.md b/translations/zh-CN/content/admin/user-management/creating-teams.md
index 9072c85cef..25bab60f6e 100644
--- a/translations/zh-CN/content/admin/user-management/creating-teams.md
+++ b/translations/zh-CN/content/admin/user-management/creating-teams.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/creating-teams
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Teams
+  - User account
 ---
 
 团队是 {% data variables.product.prodname_dotcom %} 许多协作功能的中心，例如团队 @提及，此功能可以通知相关方您想要请求他们的输入或注意。 更多信息请参阅“[组织仓库的权限级别](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)”。
diff --git a/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
index ae5a75b09c..ac1eb8b39a 100644
--- a/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/customizing-user-messages-for-your-enterprise.md
@@ -1,5 +1,6 @@
 ---
 title: 自定义企业的用户消息
+shortTitle: Customizing user messages
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
@@ -8,8 +9,10 @@ intro: '您可以创建用户将在 {% data variables.product.product_location %
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Maintenance
 ---
 
 ### 关于用户消息
diff --git a/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md b/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
index 4997be6965..66ae6201d4 100644
--- a/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/disabling-git-ssh-access-on-your-enterprise.md
@@ -17,8 +17,12 @@ intro: 您可以阻止用户为企业上的某些仓库或所有仓库使用 Git
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Policies
+  - Security
+  - SSH
 ---
 
 ### 禁止对特定仓库进行 Git SSH 访问
diff --git a/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md b/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md
index 5a9ac344cf..a8f148c0de 100644
--- a/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md
+++ b/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-githubcom.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### 在 {% data variables.product.prodname_dotcom %} 上准备源组织
diff --git a/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-your-enterprise.md b/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
index e2a98bc1d4..bcea93923e 100644
--- a/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/exporting-migration-data-from-your-enterprise.md
@@ -11,8 +11,11 @@ redirect_from:
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - API
   - Enterprise
+  - Migration
 ---
 
 ### 准备 {% data variables.product.prodname_ghe_server %} 源实例
diff --git a/translations/zh-CN/content/admin/user-management/importing-data-from-third-party-version-control-systems.md b/translations/zh-CN/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
index 5d6e2a8bdf..8cab4cd278 100644
--- a/translations/zh-CN/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
+++ b/translations/zh-CN/content/admin/user-management/importing-data-from-third-party-version-control-systems.md
@@ -6,8 +6,10 @@ redirect_from:
   - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### 从 Mercurial 导入项目
diff --git a/translations/zh-CN/content/admin/user-management/log-forwarding.md b/translations/zh-CN/content/admin/user-management/log-forwarding.md
index 015bee895b..f205e76ce4 100644
--- a/translations/zh-CN/content/admin/user-management/log-forwarding.md
+++ b/translations/zh-CN/content/admin/user-management/log-forwarding.md
@@ -9,8 +9,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
+  - Security
 ---
 
 支持使用任何支持 syslog-style 日志流的日志收集系统（例如 [Logstash](http://logstash.net/) 和 [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)）。
diff --git a/translations/zh-CN/content/admin/user-management/managing-dormant-users.md b/translations/zh-CN/content/admin/user-management/managing-dormant-users.md
index 1fa0835076..366b5d29fc 100644
--- a/translations/zh-CN/content/admin/user-management/managing-dormant-users.md
+++ b/translations/zh-CN/content/admin/user-management/managing-dormant-users.md
@@ -9,15 +9,18 @@ intro: '如果用户帐户至少在一个月内未激活，则被视为休眠状
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
   - Enterprise
+  - Licensing
 ---
 
 “活动”包括但不限于：
 - 登录 {% data variables.product.product_name %}。
 - 评论问题和拉取请求。
 - 创建、删除、关注仓库和加星标。
-- 推送提交。{% if currentversion ver_gt "enterprise-server@2.21" or currentversion == "github-ae@latest" %}
+- 推送提交。{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 - 使用个人访问令牌或 SSH 密钥访问资源。{% endif %}
 
 ### 查看休眠用户
diff --git a/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md b/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md
index 810c01bc83..26d148ad05 100644
--- a/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md
+++ b/translations/zh-CN/content/admin/user-management/managing-global-webhooks.md
@@ -7,8 +7,10 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Webhooks
 ---
 
 ### 关于全局 web 挂钩
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md
index 7a4dc868c3..ffc832c08a 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise.md
@@ -5,7 +5,7 @@ redirect_from:
   - /enterprise/admin/categories/admin-bootcamp/
   - /enterprise/admin/user-management/organizations-and-teams
   - /enterprise/admin/user-management/managing-organizations-in-your-enterprise
-intro: '组织适合在您的公司内创建不同的用户组，例如部门或参与相似项目的组。 属于组织的{% if currentversion == "github-ae@latest" %}内部{% else %}公共和内部{% endif %}仓库可供其他组织中的用户访问，而私有仓库只能供被授予访问权限的组织成员访问。'
+intro: '组织适合在您的公司内创建不同的用户组，例如部门或参与相似项目的组。 属于组织的{% if currentVersion == "github-ae@latest" %}内部{% else %}公共和内部{% endif %}仓库可供其他组织中的用户访问，而私有仓库只能供被授予访问权限的组织成员访问。'
 mapTopic: true
 versions:
   enterprise-server: '*'
diff --git a/translations/zh-CN/content/admin/user-management/managing-projects-using-jira.md b/translations/zh-CN/content/admin/user-management/managing-projects-using-jira.md
index 4fc353af1b..bbbd31b3ca 100644
--- a/translations/zh-CN/content/admin/user-management/managing-projects-using-jira.md
+++ b/translations/zh-CN/content/admin/user-management/managing-projects-using-jira.md
@@ -1,6 +1,6 @@
 ---
-title: 使用 JIRA 管理项目
-intro: '您可以将 JIRA 与 {% data variables.product.prodname_enterprise %} 集成以进行项目管理。'
+title: 使用 Jira 管理项目
+intro: '您可以将 Jira 与 {% data variables.product.prodname_enterprise %} 集成以进行项目管理。'
 redirect_from:
   - /enterprise/admin/guides/installation/project-management-using-jira/
   - /enterprise/admin/articles/project-management-using-jira/
@@ -9,38 +9,60 @@ redirect_from:
   - /enterprise/admin/user-management/managing-projects-using-jira
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Project management
 ---
 
-### 将 JIRA 连接到 {% data variables.product.prodname_enterprise %} 组织
+### 将 Jira 连接到 {% data variables.product.prodname_enterprise %} 组织
 
-1. 在 http[s]://[hostname]/login 上登录您的 {% data variables.product.prodname_enterprise %} 帐户。
-1. 在任意页面的右上角，单击帐户设置（齿轮）图标。
-1. 在左侧边栏中，单击您组织的名称。
-1. 在左侧边栏中，单击 **Applications**。
-1. 在 **Organization applications** 框的右上角，单击 **Register new application**。
-1. 填写应用程序设置：
-    - 在 **Application name** 字段中，输入“JIRA”。
-    - 在 **Homepage URL** 字段中，输入 JIRA 实例的完整 URL。
-    - 在 **Authorization callback URL** 字段中，输入 JIRA 实例的完整 URL。
-1. 单击 **Register application（注册应用程序）**。
-1. 在页面顶部，记下 **Client ID** 和 **Client Secret**。 您将需要这些信息来配置 JIRA 实例。
+1. 在 http[s]://[hostname]/login 上登录您的 {% data variables.product.prodname_enterprise %} 帐户。 如果已登录，请单击左上角的 {% data variables.product.prodname_dotcom %} 徽标。
+2. 单击 {% data variables.product.prodname_dotcom %} 徽标下的个人资料图标，然后选择您希望使用 Jira 连接的组织。
 
-### JIRA 实例配置
+  ![选择组织](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-1. 在 JIRA 实例上，登录具有管理访问权限的帐户。
-1. 在页面顶部，单击设置（齿轮）图标。
-1. 在设置下拉列表中，选择 **Add-ons**。
-1. 在左侧边栏的 **Source control** 下，单击 **DVCS accounts**。
-1. 单击 **Link Bitbucket or GitHub account**。
-1. 在 **Add New Account** 模态中，填写您的 {% data variables.product.prodname_enterprise %} 设置：
-    - 从 **Host** 下拉菜单中，选择 **GitHub Enterprise**。
+3. 单击**编辑_组织名称_设置**链接。
+
+  ![编辑组织设置](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. 在左侧边栏的 **Developer settings（开发者设置）**下，单击 **OAuth Apps（OAuth 应用程序）**。
+
+  ![选择 OAuth 应用程序](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. 单击 **Register new application（注册新应用程序）**按钮。
+
+  ![注册新应用程序按钮](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. 填写应用程序设置：
+    - 在 **Application name（应用程序名称）** 字段中，输入 "Jira" 或您想要用来标识 Jira 实例的任何名称。
+    - 在 **Homepage URL（主页 URL）**字段中，输入 Jira 实例的完整 URL。
+    - 在 **Authorization callback URL（授权回叫 URL）**字段中，输入 Jira 实例的完整 URL。
+7. 单击 **Register application（注册应用程序）**。
+8. 在页面顶部，记下 **Client ID** 和 **Client Secret**。 您将需要这些信息来配置 Jira 实例。
+
+### Jira 实例配置
+
+1. 在 Jira 实例上，登录具有管理访问权限的帐户。
+2. 在页面顶部，单击设置（齿轮）图标，然后选择 **Applications（应用程序）**。
+
+  ![选择 Jira 设置中的应用程序](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. 在左侧边栏的 **Integrations（集成）**下，单击 **DVCS accounts（DVCS 帐户）**。
+
+  ![Jira 集成菜单 - DVCS 帐户](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. 单击**链接 Bitbucket Cloud 或 {% data variables.product.prodname_dotcom %} 帐户**。
+
+  ![将 GitHub 帐户链接到 Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. 在 **Add New Account** 模态中，填写您的 {% data variables.product.prodname_enterprise %} 设置：
+    - 从 **Host（主机）**下拉菜单中，选择 **{% data variables.product.prodname_enterprise %}**。
     - 在 **Team or User Account** 字段中，输入 {% data variables.product.prodname_enterprise %} 组织或个人帐户的名称。
     - 在 **OAuth Key** 字段中，输入 {% data variables.product.prodname_enterprise %} 开发者应用程序的客户端 ID。
     - 在 **OAuth Secret** 字段中，输入 {% data variables.product.prodname_enterprise %} 开发者应用程序的客户端密钥。
-    - 如果您不想链接 {% data variables.product.prodname_enterprise %} 组织或个人帐户拥有的新仓库，请取消选择 **Auto Link New Repositories**。
-    - 如果您不想启用智能提交，请取消选择 **Enable Smart Commits**。
+    - 如果您不想链接 {% data variables.product.prodname_enterprise %} 组织或个人帐户拥有的新仓库，请取消选择 **Auto Link New Repositories（自动链接新仓库）**。
+    - 如果您不想启用智能提交，请取消选择 **Enable Smart Commits（启用智能提交）**。
     - 单击 **Add（添加）**。
-1. 查看您要授予 {% data variables.product.prodname_enterprise %} 帐户的权限，然后单击 **Authorize application**。
-1. 如有必要，请输入密码以继续。
+6. 查看您要授予 {% data variables.product.prodname_enterprise %} 帐户的权限，然后单击 **Authorize application**。
+7. 如有必要，请输入密码以继续。
diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md
index 2b306e5c5e..c5a9ed2b6f 100644
--- a/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md
@@ -13,8 +13,10 @@ redirect_from:
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### 在 {% data variables.product.prodname_ghe_server %} 上应用导入的数据
diff --git a/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md b/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md
index 8dab32ba28..4c89464097 100644
--- a/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md
+++ b/translations/zh-CN/content/admin/user-management/migrating-to-internal-repositories.md
@@ -7,8 +7,12 @@ redirect_from:
 permissions: Site administrators can migrate to internal repositories.
 versions:
   enterprise-server: '>=2.20'
+type: how_to
 topics:
   - Enterprise
+  - Privacy
+  - Repositories
+  - Security
 ---
 
 ### 关于内部仓库
@@ -34,6 +38,12 @@ topics:
 ### 运行迁移
 
 1. 连接到管理 shell。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)。”
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+2. 运行迁移命令。
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% else %}
 2. 导航至 `/data/github/current` 目录。
    ```shell
    cd /data/github/current
@@ -42,6 +52,7 @@ topics:
    ```shell
    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
    ```
+{% endif %}
 
 日志输出将显示在终端和 `/tmp/convert_public_ghes_repos_to_internal.log` 中。
 
diff --git a/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
index c27c4f6140..a41fbd619f 100644
--- a/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
+++ b/translations/zh-CN/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md
@@ -6,8 +6,13 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Accounts
+  - Auditing
   - Enterprise
+  - Organizations
+  - User account
 ---
 
 通常情况下，如果有人删除仓库，它将在磁盘上保留 90 天并且可以通过站点管理员仪表板进行恢复。 90 天后，仓库将被永久删除。 如果您合法保留用户或组织，可以随时恢复他们拥有的仓库。
diff --git a/translations/zh-CN/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
index 02f325651a..eaced4bfe6 100644
--- a/translations/zh-CN/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/preparing-to-migrate-data-to-your-enterprise.md
@@ -10,8 +10,10 @@ redirect_from:
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Migration
 ---
 
 ### 准备迁移的数据以导入到 {% data variables.product.prodname_ghe_server %}
diff --git a/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md
index 78ce04f4ef..bd75ff522c 100644
--- a/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md
+++ b/translations/zh-CN/content/admin/user-management/preventing-users-from-creating-organizations.md
@@ -8,8 +8,11 @@ intro: 您可以防止用户在您的企业中创建组织。
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
   - Enterprise
+  - Organizations
+  - Policies
 ---
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/zh-CN/content/admin/user-management/promoting-or-demoting-a-site-administrator.md b/translations/zh-CN/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
index a953c2b2c0..092e0fe04c 100644
--- a/translations/zh-CN/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
+++ b/translations/zh-CN/content/admin/user-management/promoting-or-demoting-a-site-administrator.md
@@ -7,7 +7,11 @@ redirect_from:
 intro: 站点管理员可以将任何普通用户升级为站点管理员，也可以将其他站点管理员降级为普通用户。
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
+  - User account
   - Enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/rebuilding-contributions-data.md b/translations/zh-CN/content/admin/user-management/rebuilding-contributions-data.md
index 565fde46e7..4ea5e19d3b 100644
--- a/translations/zh-CN/content/admin/user-management/rebuilding-contributions-data.md
+++ b/translations/zh-CN/content/admin/user-management/rebuilding-contributions-data.md
@@ -6,8 +6,11 @@ redirect_from:
   - /enterprise/admin/user-management/rebuilding-contributions-data
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
   - Enterprise
+  - Repositories
+  - User account
 ---
 
 将提交推送到 {% data variables.product.prodname_enterprise %} 时，如果新提交和现有提交关联到同一个电子邮件地址，此提交会链接到用户帐户。 不过，在用户注册新电子邮件地址或创建新帐户时，*不会*追溯地链接现有提交。
diff --git a/translations/zh-CN/content/admin/user-management/removing-users-from-teams-and-organizations.md b/translations/zh-CN/content/admin/user-management/removing-users-from-teams-and-organizations.md
index 6e976ee67c..f0e3290aae 100644
--- a/translations/zh-CN/content/admin/user-management/removing-users-from-teams-and-organizations.md
+++ b/translations/zh-CN/content/admin/user-management/removing-users-from-teams-and-organizations.md
@@ -5,8 +5,12 @@ redirect_from:
   - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
+  - Accounts
   - Enterprise
+  - Teams
 ---
 
 只有所有者或团队管理员可以移除组织成员。 从团队或组织中移除用户时，他们在组织仓库中的问题、拉取请求和评论都会保持原样且仍归属于用户。
diff --git a/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
index e9ebabc077..fe6fc8f085 100644
--- a/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
+++ b/translations/zh-CN/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md
@@ -5,8 +5,13 @@ redirect_from:
   - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - 2fa
   - Enterprise
+  - Organizations
+  - Policies
+  - Security
 ---
 
 使用 LDAP 或内置身份验证时，{% data variables.product.product_location %} 将支持双重身份验证。 组织管理员可以要求成员启用双重身份验证。
diff --git a/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md b/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md
index b563951d49..f639d21ecf 100644
--- a/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md
+++ b/translations/zh-CN/content/admin/user-management/searching-the-audit-log.md
@@ -8,8 +8,11 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Logging
 ---
 
 ### 搜索查询语法
diff --git a/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md
index e28fee5439..1c63eb77cc 100644
--- a/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md
+++ b/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md
@@ -10,8 +10,12 @@ redirect_from:
 intro: '如果用户离开公司或者调动到公司的其他部门，您应当移除或修改他们访问 {% data variables.product.product_location %} 的能力。'
 versions:
   enterprise-server: '*'
+type: how_to
 topics:
+  - Access management
   - Enterprise
+  - Security
+  - User account
 ---
 
 如果员工从公司离职，您可以暂停他们的 {% data variables.product.prodname_ghe_server %} 帐户，打开您的 {% data variables.product.prodname_enterprise %} 许可中的用户许可，同时保存他们创建的议题、评论、仓库、Gist 及其他数据。 被挂起的用户既无法登录您的实例，也无法推送或拉取代码。
diff --git a/translations/zh-CN/content/admin/user-management/viewing-push-logs.md b/translations/zh-CN/content/admin/user-management/viewing-push-logs.md
index fb7786872f..586f45056e 100644
--- a/translations/zh-CN/content/admin/user-management/viewing-push-logs.md
+++ b/translations/zh-CN/content/admin/user-management/viewing-push-logs.md
@@ -8,8 +8,12 @@ redirect_from:
 versions:
   enterprise-server: '*'
   github-ae: '*'
+type: how_to
 topics:
+  - Auditing
   - Enterprise
+  - Git
+  - Logging
 ---
 
 推送日志条目会显示：
diff --git a/translations/zh-CN/content/code-security/getting-started/about-securing-your-repository.md b/translations/zh-CN/content/code-security/getting-started/about-securing-your-repository.md
index 24ca2d1610..189085df1a 100644
--- a/translations/zh-CN/content/code-security/getting-started/about-securing-your-repository.md
+++ b/translations/zh-CN/content/code-security/getting-started/about-securing-your-repository.md
@@ -22,11 +22,13 @@ topics:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
 #### 适用于所有仓库
 
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
 - **安全策略**
 
-  让人们能够轻松地秘密报告他们在仓库中发现的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)”。
+  Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. 更多信息请参阅“[添加安全政策到仓库](/code-security/getting-started/adding-a-security-policy-to-your-repository)”。
+{% endif %}
 
+{% if currentVersion == "free-pro-team@latest" %}
 - **安全通告**
 
   私下讨论并修复仓库代码中的安全漏洞。 然后，您可以发布安全通告，提醒您的社区注意漏洞并鼓励他们升级。 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
@@ -78,7 +80,7 @@ topics:
 * 您的仓库依赖的生态系统和包
 * 依赖于您的仓库的仓库和包
 
-必须先启用依赖项图，然后 {% data variables.product.prodname_dotcom %} 才能针对有安全漏洞的依赖项生成 {% data variables.product.prodname_dependabot_alerts %}。 {% if currentversion == "free pro-team@latest" %}启用依赖关系图也会允许 {% data variables.product.prodname_dotcom %} 运行拉取请求的依赖关系审查。{% endif %}
+必须先启用依赖项图，然后 {% data variables.product.prodname_dotcom %} 才能针对有安全漏洞的依赖项生成 {% data variables.product.prodname_dependabot_alerts %}。 {% if currentVersion == "free pro-team@latest" %}启用依赖关系图也会允许 {% data variables.product.prodname_dotcom %} 运行拉取请求的依赖关系审查。{% endif %}
 
 您可以在仓库的 **Insights（洞察）**选项卡上找到依赖项图。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..a6669b9149
--- /dev/null
+++ b/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,57 @@
+---
+title: 添加安全政策到仓库
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+### 关于安全政策
+
+To give people instructions for reporting security vulnerabilities in your project,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% if currentVersion != 'github-ae@next' %}
+<!-- no public repos in GHAE -->
+您可以为组织或用户帐户创建默认的安全政策。 更多信息请参阅“[创建默认社区健康文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”。
+{% endif %}
+
+{% tip %}
+
+**提示：**为帮助人们查找安全政策，您可以从仓库中的其他位置（如自述文件）链接到 _SECURITY.md_ 文件。 更多信息请参阅“[关于自述文件](/articles/about-readmes)”。
+
+{% endtip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+当有人报告您的项目中的安全漏洞后，您可以使用 {% data variables.product.prodname_security_advisories %} 披露、修复和发布关于该漏洞的信息。 有关 {% data variables.product.prodname_dotcom %} 中报告和披露漏洞的过程的更多信息，请参阅“[关于协调披露安全漏洞](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)”。 有关 {% data variables.product.prodname_security_advisories %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+### 添加安全政策到仓库
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**. ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. 单击 **Start setup（开始设置）**。 ![开始设置按钮](/assets/images/help/security/start-setup-security-policy-button.png)
+5. 在新的 _SECURITY.md_ 文件中，添加关于项目受支持版本以及如何报告漏洞的信息。
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+### 延伸阅读
+
+- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% if currentVersion != 'github-ae@next' %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/zh-CN/content/code-security/getting-started/index.md b/translations/zh-CN/content/code-security/getting-started/index.md
index 55205e980a..374656e88f 100644
--- a/translations/zh-CN/content/code-security/getting-started/index.md
+++ b/translations/zh-CN/content/code-security/getting-started/index.md
@@ -13,3 +13,4 @@ topics:
 ### 目录
 
 {% link_in_list /about-securing-your-repository %}
+{% link_in_list /adding-a-security-policy-to-your-repository %}
diff --git a/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md
index 83dc03e318..8879bca3c4 100644
--- a/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md
@@ -45,7 +45,7 @@ topics:
 {% data variables.product.prodname_secret_scanning_caps %} 作为 {% data variables.product.prodname_GH_advanced_security %} 的一部分，在组织拥有的所有仓库上可用。 它不适用于用户拥有的仓库。
 {% endif %}
 
-如果您是仓库管理员或组织所有者，您可以为组织拥有的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_secret_scanning %}。 You can enable  {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} is not available for user-owned private repositories.{% endif %} For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+如果您是仓库管理员或组织所有者，您可以为组织拥有的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_secret_scanning %}。 您可以对您的所有仓库或您组织内的所有新仓库启用 {% data variables.product.prodname_secret_scanning %}。{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} 不适用于用户拥有的私有仓库。{% endif %}更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”和“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
 
 将提交推送到启用了 {% data variables.product.prodname_secret_scanning %} 的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库时，{% data variables.product.prodname_dotcom %} 会扫描提交的内容中是否有密码。
 
diff --git a/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
index c241108712..375515f9e4 100644
--- a/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md
@@ -27,13 +27,19 @@ topics:
 
 ### 为{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_secret_scanning %}
 
+{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization.
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
-4. 您可能需要启用 {% data variables.product.prodname_GH_advanced_security %} 才能对“{% data variables.product.prodname_secret_scanning_caps %}”激活按钮。 在“{% data variables.product.prodname_GH_advanced_security %}”右边单击 **Enable（启用）**。 ![为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-dotcom.png)
-5. 单击**为此仓库启用 {% data variables.product.prodname_GH_advanced_security %}** 以确认操作。 ![确认为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png)
-6. 启用 {% data variables.product.prodname_GH_advanced_security %} 时，可能会自动为仓库启用 {% data variables.product.prodname_secret_scanning %}（这是由组织配置控制的）。 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 显示 **Enable（启用）**按钮，则您仍需通过单击 **Enable（启用）**来启用 {% data variables.product.prodname_secret_scanning %}。 如果您看到 **Disable（禁用）**按钮，则表明 {% data variables.product.prodname_secret_scanning %} 已启用。 ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next"%}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% if currentVersion == "free-pro-team@latest" %}![为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 显示 **Enable（启用）**按钮，则您仍需通过单击 **Enable（启用）**来启用 {% data variables.product.prodname_secret_scanning %}。 如果您看到 **Disable（禁用）**按钮，则表明 {% data variables.product.prodname_secret_scanning %} 已启用。 ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
    {% elsif currentVersion == "enterprise-server@3.0" %}
 7. 在“{% data variables.product.prodname_secret_scanning_caps %}”右边单击 **Enable（启用）**。 ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-ghe.png)
    {% endif %}
@@ -66,7 +72,7 @@ topics:
 
     {% endnote %}
 
-您也可以忽略来自 {% data variables.product.prodname_secret_scanning %} 的个别警报。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)”。
+您也可以忽略来自 {% data variables.product.prodname_secret_scanning %} 的个别警报。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)”。
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/code-security/secret-security/managing-alerts-from-secret-scanning.md b/translations/zh-CN/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
index 97cdc4285b..6499c251ec 100644
--- a/translations/zh-CN/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-security/managing-alerts-from-secret-scanning.md
@@ -14,7 +14,7 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-### 管理警报
+### Managing {% data variables.product.prodname_secret_scanning %} alerts
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
@@ -49,3 +49,11 @@ topics:
 
 - 对于受到威胁的 {% data variables.product.prodname_dotcom %} 个人访问令牌，请删除该令牌，创建新令牌，然后更新使用旧令牌的任何服务。 更多信息请参阅“[创建用于命令行的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)。”
 - 对于所有其他密码，请先确认提交到 {% data variables.product.product_name %} 的密码是有效的。 如果有效，请创建新密码，更新使用旧密码的任何服务，然后删除旧密码。
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.prodname_dotcom %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/secure-coding/about-code-scanning.md b/translations/zh-CN/content/code-security/secure-coding/about-code-scanning.md
index b51285750b..0fc6391229 100644
--- a/translations/zh-CN/content/code-security/secure-coding/about-code-scanning.md
+++ b/translations/zh-CN/content/code-security/secure-coding/about-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -36,7 +38,7 @@ topics:
 
 有关 {% data variables.product.prodname_code_scanning %} 的 API 端点的更多信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)”。
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 更多信息请参阅 {% data variables.product.prodname_codeql %} 文档中的 [{% data variables.product.prodname_codeql %} 查询](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/)。
 
@@ -48,17 +50,14 @@ topics:
 
 {% endif %}
 
-### 关于第三方代码扫描工具
-
-{% data reusables.code-scanning.you-can-upload-third-party-analysis %}
+### About third-party {% data variables.product.prodname_code_scanning %} tools
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-{% data reusables.code-scanning.get-started-uploading-third-party-data %}
+You can run third-party analysis tools within {% data variables.product.product_name %} using actions or within an external CI system. For more information, see "[Setting up code scanning for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
 
 ### 延伸阅读
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
+- “[关于保护仓库](/github/administering-a-repository/about-securing-your-repository)”
 - [{% data variables.product.prodname_security %}](https://securitylab.github.com/)
 - OASIS Committee 网站上的 [OASIS 静态分析结果交换格式 (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif)
diff --git a/translations/zh-CN/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..d67910b1b4
--- /dev/null
+++ b/translations/zh-CN/content/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,62 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %} 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)”。
+
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using actions. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.product.product_location %}.
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+### Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+The {% data variables.product.prodname_codeql_runner %} is a command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. The runner is able to integrate with more complex build environments than the CLI, but this ability makes it more difficult and error-prone to set up. It is also more difficult to debug any problems. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly unless it doesn't support your use case.
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Codebases with a compiled language that can be built with a single command or by running a single script.
+
+更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)”。
+
+{% if currentVersion == "free-pro-team@latest" %}
+If you need to set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis, you must use the {% data variables.product.prodname_codeql_runner %}.
+{% else %}
+You will need to use the {% data variables.product.prodname_codeql_runner %} if you need to:
+- Set up the CI system to orchestrate compiler invocations as well as running {% data variables.product.prodname_codeql %} analysis.
+- Analyze more than one language in a repository.
+{% endif %}
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”。
+
+{% else %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+
+To set up code scanning in your CI system, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/secure-coding/about-integration-with-code-scanning.md b/translations/zh-CN/content/code-security/secure-coding/about-integration-with-code-scanning.md
index 74462f867b..0a764ca42b 100644
--- a/translations/zh-CN/content/code-security/secure-coding/about-integration-with-code-scanning.md
+++ b/translations/zh-CN/content/code-security/secure-coding/about-integration-with-code-scanning.md
@@ -13,6 +13,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/zh-CN/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/zh-CN/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 6b0496a4fe..4cee7a1549 100644
--- a/translations/zh-CN/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/zh-CN/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -14,3 +14,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md b/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md
index 88a106c919..d62d443d23 100644
--- a/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md
+++ b/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring code scanning
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+title: 配置代码扫描
+intro: '您可以配置 {% data variables.product.prodname_dotcom %} 如何扫描项目代码以查找漏洞和错误。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
 miniTocMaxHeadingLevel: 4
@@ -11,55 +11,70 @@ versions:
   enterprise-server: '>=3.0'
   github-ae: '*'
 topics:
-  - security
+  - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About {% data variables.product.prodname_code_scanning %} configuration
+### 关于 {% data variables.product.prodname_code_scanning %} 配置
 
-You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)."
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+"[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+{%- else %}
+"[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+{% endif %}
 
-This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}.
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
 
-Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+在为仓库配置 {% data variables.product.prodname_code_scanning %} 之前，必须将 {% data variables.product.prodname_actions %} 工作流程添加到仓库中以设置 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+您可以为 {% data variables.product.prodname_code_scanning %} 编写配置文件。 {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} 在 {% data variables.product.prodname_dotcom_the_website %} 上，{% endif %}包含您可以使用的其他 {% data variables.product.prodname_code_scanning %} 工作流程。 {% if currentVersion == "free-pro-team@latest" %}您可以在“{% data variables.product.prodname_code_scanning %} 使用入门”页找到这些选项，该页面可从 **{% octicon "shield" aria-label="The shield symbol" %} Security（安全）**选项卡访问。{% endif %}本文给出的具体示例与 {% data variables.product.prodname_codeql_workflow %} 文件相关。
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} 将工作流程文件保存在仓库的 _.github/workflows_ 目录中。 您可以通过搜索其文件名来查找已添加的工作流程。 例如，默认情况下，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的工作流程文件被称为 _codeql-analysis.yml_。
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. 在仓库中，浏览至要编辑的工作流程文件。
+1. 要打开工作流程编辑器，在文件视图右上角单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑工作流程文件按钮](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. 编辑文件后，单击 **Start commit（开始提交）**并完成“Commit changes（提交更改）”表单。 您可以选择直接提交到当前分支，或者创建一个新分支并启动拉取请求。 ![将更新提交到 codeql.yml 工作流程](/assets/images/help/repository/code-scanning-workflow-update.png)
 
-For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+有关编辑工作流程文件的更多信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-### Configuring frequency
+### 配置频率
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+您可以按时间表或在仓库中发生特定事件时扫描代码。
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+每当推送到仓库以及每次创建拉取请求时，时扫描代码可防止开发者在代码中引入新的漏洞和错误。 按时间表扫描可了解 {% data variables.product.company_short %}、安全研究者和社区发现的最新漏洞和错误，即使开发者并未主动维护仓库。
 
-#### Scanning on push
+#### 按推送扫描
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+如果使用默认工作流程，则除了事件触发的扫描之外，{% data variables.product.prodname_code_scanning %} 还会每周扫描一次仓库代码。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#on)”。
 
-#### Scanning pull requests
+如果您在推送时扫描，则结果将出现在仓库的 **Security（安全性）**选项卡中。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+{% note %}
 
-For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+**注意**：如果您希望 {% data variables.product.prodname_code_scanning %} 警报显示为拉取请求检查，则必须使用下述 `pull_request` 事件。
 
-#### Avoiding unnecessary scans of pull requests
+{% endnote %}
 
-You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+#### 扫描拉取请求
+
+默认 {% data variables.product.prodname_codeql_workflow %} 使用 `pull_request` 事件在针对默认分支的拉取请求上触发代码扫描。 {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+
+有关 `pull_request` 事件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)”。
+
+如果您扫描拉取请求，则结果在拉取请求检查中显示为警报。 更多信息请参阅“[对拉取请求中的代码扫描警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”。
+
+#### 避免对拉取请求进行不必要的扫描
+
+您可能希望避免针对默认分支的特定拉取请求触发代码扫描，而不管更改了哪些文件。 可以通过在 {% data variables.product.prodname_code_scanning %} 工作流程中指定 `on:pull_request:paths-ignore` or `on:pull_request:paths` 来进行配置。 例如，如果拉取请求中唯一的更改是文件扩展名为 `.md` 或 `.txt` 的文件，则您可以使用以下 `paths-ignore` 数组。
 
 ``` yaml
 on:
@@ -74,28 +89,28 @@ on:
 
 {% note %}
 
-**Notes**
+**注：**
 
-* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+* `on:pull_request:paths-witch` 和 `on:pull_request:pull_request:path` 设置条件来确定工作流程中的操作是否会在拉取请求上运行。 它们无法确定在操作_运行_时将分析哪些文件。 当拉取请求包含 `on:pull_request:paths-with` 或 `on:pull_request:path:path` 未匹配的任何文件时，工作流程将运行操作并扫描拉取请求中更改的所有文件，包括 `on:pull_request:paths-ignore` 或 `on:pull_request:paths` 匹配的文件，除非文件被排除在外。 有关如何从分析中排除文件的信息，请参阅“[指定要扫描的目录](#specifying-directories-to-scan)”。
+* 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 工作流程文件， 不要对 `on:push` 事件使用 `paths-ignore` 或 `paths` 关键词， 因为这可能导致缺少分析。 为了获得准确的结果，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 需要能够与上次提交的分析比较新的变化。
 
 {% endnote %}
 
-For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+有关使用 `on:pull_request:paths-ignore` 和 `on:pull_request:paths` 确定工作流程何时对拉取请求运行的详细信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。
 
-#### Scanning on a schedule
+#### 按时间表扫描
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+默认 {% data variables.product.prodname_code_scanning %} 工作流程在拉取请求的 `HEAD` 提交时使用 `pull_request` 事件触发代码扫描。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onschedule)”。
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+**注**：{% data variables.product.prodname_dotcom %} 只运行默认分支上工作流程中的预定作业。 在任何其他分支上的工作流程中更改时间表后，需要将该分支合并到默认分支才能使更改生效。
 
 {% endnote %}
 
-#### Example
+#### 示例
 
-The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. You can find the workflow by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
 ``` yaml
 on:
@@ -107,16 +122,16 @@ on:
     - cron: '20 14 * * 1'
 ```
 
-This workflow scans:
-* Every push to the default branch and the protected branch
-* Every pull request to the default branch
-* The default branch every Monday at 14:20 UTC
+此工作流程扫描：
+* 对默认分支和受保护分支的每次推送
+* 对默认分支的每个拉取请求
+* 默认分支（每个星期一 14:20 UTC）
 
-### Specifying an operating system
+### 指定操作系统
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
+如果您的代码需要使用特定的操作系统进行编译，您可以在工作流程中配置它。 编辑 `jobs.analyze.runs-on` 的值以指定运行 {% data variables.product.prodname_code_scanning %} 操作的机器操作系统。 {% if currentVersion ver_gt "enterprise-server@2.21" %}在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% else %}
 
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+如果选择使用自托管的运行器进行代码扫描，可以在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% endif %}
 
 ``` yaml
 jobs:
@@ -125,23 +140,23 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。{% endif %}
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+{% data variables.product.prodname_code_scanning_capc %} 支持 macOS、Ubuntu 和 Windows 的最新版本。 因此，此设置的典型值为：`ubuntu-latest`、`windows-latest` 和 `macos-latest`。 更多信息请参阅 {% if currentVersion ver_gt "enterprise-server@2.21" %}“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)”和“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}”[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}“。
 
 {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
 
-### Changing the languages that are analyzed
+### 更改分析的语言
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
+{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 会自动检测用受支持的语言编写的代码。
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+默认 {% data variables.product.prodname_codeql_workflow %} 文件包含一个名为 `language` 的构建矩阵，其中列出了仓库中被分析的语言。 将 {% data variables.product.prodname_code_scanning %} 添加到仓库时，{% data variables.product.prodname_codeql %} 会自动填充此矩阵。 使用 `language` 矩阵优化 {% data variables.product.prodname_codeql %} 以并行运行每个分析。 由于并行构建的性能优势，我们建议所有工作流程都采用此配置。 有关构建矩阵的更多信息，请参阅“[管理复杂的工作流程](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)”。
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix.
+如果您的工作流程使用 `language` 矩阵，则 {% data variables.product.prodname_codeql %} 会被硬编码为仅分析矩阵中的语言。 如需更改要分析的语言，请编辑矩阵变量的值。 您可以删除某种语言以防止被分析，也可以添加在设置 {% data variables.product.prodname_code_scanning %} 时仓库中不存在的语言。 例如，如果在设置 {% data variables.product.prodname_code_scanning %} 时，仓库最初只包含 JavaScript，但您后来添加了 Python 代码，则需要将 `python` 添加到矩阵中。
 
 ```yaml
 jobs:
@@ -154,7 +169,7 @@ jobs:
         language: ['javascript', 'python']
 ```
 
-If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action.
+如果工作流程中不包含名为 `language` 的矩阵，则 {% data variables.product.prodname_codeql %} 将被配置为按顺序运行分析。 如果您未在工作流程中指定语言，则 {% data variables.product.prodname_codeql %} 将自动检测并尝试分析仓库中所有受支持的语言。 如果不愿意使用矩阵选择要分析的语言，您可以使用 `init` 操作下的 `languages` 参数。
 
 ```yaml
 - uses: github/codeql-action/init@v1
@@ -162,71 +177,103 @@ If your workflow does not contain a matrix called `language`, then {% data varia
     languages: cpp, csharp, python
 ```
 {% if currentVersion == "free-pro-team@latest" %}
-### Analyzing Python dependencies
+### 分析 Python 依赖项
 
-For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
+对于仅使用 Linux 的 GitHub 托管的运行器，{% data variables.product.prodname_codeql_workflow %} 将尝试自动安装 Python 依赖项以提供更多 CodeQL 分析结果。 可通过为“初始化 CodeQL”步骤调用的操作指定 `setup-python-dependencies` 参数来控制此行为。 默认情况下，此参数设置为 `true`：
 
--  If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies.
+-  如果仓库包含用 Python 编写的代码，“初始化 CodeQL”步骤将在 GitHub 托管的运行器上安装必要的依赖项。 如果自动安装成功，该操作还会将环境变量 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件。
 
-- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete.
+- 如果仓库没有任何 Python 依赖项，或者依赖项是以意外方式指定的，您将收到警告，并且该操作会继续执行其余作业。 即使在解释依赖项时出现问题，该操作也可以成功运行，但结果可能不完整。
 
-Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract:
+或者，您也可以在任何操作系统上手动安装 Python 依赖项。 您需要添加 `setup-python-dependencies` 并将其设置为 `false`，以及将 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件，如此工作流程摘要中所示：
 
 ```yaml
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
-### Running additional queries
+{% if currentVersion == "free-pro-team@latest" %}
+### Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+{% raw %}
+``` yaml
+   - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze
+      with:
+      # Optional. Specify a category to distinguish between multiple analyses
+      # for the same tool and ref. If you don't use `category` in your workflow, 
+      # GitHub will generate a default category name for you
+       category: "my_category"
+```
+{% endraw %}
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.prodname_dotcom %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. 例如：
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. 更多信息请参阅“[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)”。
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+{% endif %}
+
+### 运行额外查询
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository.
+要添加一个或多个查询套件，请在配置文件中添加 `queries` 部分。 如果查询在私有仓库中，请使用 `external-repository-token` 参数来指定可以访问私有仓库的令牌。
 
 {% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     queries: COMMA-SEPARATED LIST OF PATHS
-    # Optional. Provide a token to access private repositories.
+    # Optional. 提供令牌来访问私有仓库.
     external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
 {% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+您也可以在配置文件中指定额外查询套件以运行它们。 查询套件是查询的集合，通常按目的或语言分组。
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+如果还使用配置文件进行自定义设置，则将使用工作流程中指定的任何额外查询，而不是配置文件中指定的任何查询。 如果您要运行此处指定的额外查询与配置文件中指定的查询的组合，请在工作流程中的 `queries` 值之前加上前缀 `+` 符号。 有关配置文件的示例，请参阅“[配置文件示例](#example-configuration-files)”。
 
-In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
+在下面的示例中，`+` 符号可确保结合使用额外查询与所引用配置文件中指定的任何查询。
 
 {% raw %}
 ``` yaml
@@ -238,11 +285,11 @@ In the following example, the `+` symbol ensures that the specified additional q
 ```
 {% endraw %}
 
-### Using a custom configuration file
+### 使用第三方代码扫描工具
 
-As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
+除了在工作流程文件中指定要运行的查询之外，您还可以在单独的配置文件中执行此操作。 您还可以使用配置文件禁用默认查询，并指定分析过程中要扫描的目录。
 
-In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+在工作流程文件中，使用 `init` 操作的 `config-file` 参数指定要使用的配置文件的路径。 此示例加载配置文件 _./.github/codeql/codeql-config.yml_。
 
 ``` yaml
 - uses: github/codeql-action/init@v1
@@ -252,7 +299,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp
 
 {% data reusables.code-scanning.custom-configuration-file %}
 
-If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository.
+如果配置文件位于外部私有仓库中，请使用 `init` 操作的 `external-repository-token` 参数来指定可以访问私有仓库的令牌。
 
 {% raw %}
 ```yaml
@@ -262,11 +309,11 @@ with:
 ```
 {% endraw %}
 
-The settings in the configuration file are written in YAML format.
+配置文件中的设置以 YAML 格式编写。
 
-#### Specifying additional queries
+#### 指定额外查询
 
-You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
+您可以在 `queries` 数组中指定额外查询。 数组的每个元素都包含一个 `uses` 参数，该参数的值标识单个查询文件、包含查询文件的目录或查询套件定义文件。
 
 ``` yaml
 queries:
@@ -275,17 +322,17 @@ queries:
   - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls
 ```
 
-Optionally, you can give each array element a name, as shown in the example configuration files below.
+（可选）您可以给每个数组元素一个名称，如下面的示例配置文件所示。
 
-For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
+有关额外查询的更多信息，请参阅上面的“[运行额外查询](#running-additional-queries)”。
 
-#### Disabling the default queries
+#### 禁用默认查询
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+如果只想运行自定义查询，您可以通过在配置文件中添加 `disable-default-queries: true` 来禁用默认安全查询。
 
-#### Specifying directories to scan
+#### 指定要扫描的目录
 
-For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
+对于 {% data variables.product.prodname_codeql %} 支持的解释语言（Python 和 JavaScript/TypeScript），您可以通过在配置文件中添加 `paths` 数组将 {% data variables.product.prodname_code_scanning %} 限制到特定目录中的文件。 添加 `paths-ignore` 数组可从分析排除特定目录中的文件。
 
 ``` yaml
 paths:
@@ -297,27 +344,28 @@ paths-ignore:
 
 {% note %}
 
-**Note**:
+**注**：
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* 在 {% data variables.product.prodname_code_scanning %} 配置文件上下文中使用的 `paths` 和 `paths-ignore` 关键字，不应与用于工作流程中 `on.<push|pull_request>.paths` 的相同关键字相混淆。 当它们用于修改工作流程中的 `on.<push|pull_request>` 时，它们将决定在有人修改指定目录中的代码时是否运行操作。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` 字符只能用在行的开头或结尾，或用斜杠包围，并且不能将 `**` 与其他字符混合在一起。 例如，`foo/**`、`**/foo` 和 `foo/**/bar` 都是允许的语法，但 `**foo` 不是。 但是，可以将单星号与其他字符一起使用，如示例中所示。 您需要引用任何包含 `*` 字符的内容。
 
 {% endnote %}
 
-For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+对于编译的语言，如果要将 {% data variables.product.prodname_code_scanning %} 限制到项目中的特定目录，您必须在工作流程中指定适当的构建步骤。 用于在构建过程中排除目录的命令将取决于您的构建系统。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+在修改特定目录中的代码时，您可以快速分析单个仓库中的小部分。 您需要在构建步骤中排除目录并在工作流程文件中对 [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) 使用 `paths-ignore` 和 `paths` 关键字。
 
-#### Example configuration files
+#### 配置文件示例
 
 {% data reusables.code-scanning.example-configuration-files %}
 
-### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+### 为编译语言配置 {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)."
+{% data reusables.code-scanning.autobuild-add-build-steps %} 有关如何为编译语言配置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)”。
 
-### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+### 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
+{% data variables.product.prodname_dotcom %} 可显示通过第三方工具在外部生成的代码分析数据。 通过在工作流程中添加 `upload-sarif` 操作，您可以在 {% data variables.product.prodname_dotcom %} 中显示第三方工具的代码分析。 更多信息请参阅“[将 SARIF 文件上传到 GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)”。
diff --git a/translations/zh-CN/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..5f5303ab8d
--- /dev/null
+++ b/translations/zh-CN/content/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,204 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configuring CodeQL runner
+intro: '您可以配置 {% data variables.product.prodname_codeql_runner %} 如何扫描项目中的代码并将结果上传到 {% data variables.product.prodname_dotcom %}。'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### 关于在 CI 系统中配置 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %}
+
+要将 {% data variables.product.prodname_code_scanning %} 集成到 CI 系统中，您可以使用 {% data variables.product.prodname_codeql_runner %}。 更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”。
+
+一般情况下，调用 {% data variables.product.prodname_codeql_runner %} 如下所示。
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` 取决于您在 CI 系统上保存 {% data variables.product.prodname_codeql_runner %} 的位置。 `codeql-runner-OS` 取决于您使用的操作系统。
+{% data variables.product.prodname_codeql_runner %} 有三个版本：`codeql-runner-linux`、`codeql-runner-macos` 和 `codeql-runner-win`，分别用于 Linux、macOS 和 Windows 系统。
+
+要自定义 {% data variables.product.prodname_codeql_runner %} 扫描代码的方式，您可以使用 `--languages` 和 `--queries` 等标志，也可以在单独的配置文件中指定自定义设置。
+
+### 扫描拉取请求
+
+每当创建拉取请求时扫描代码可防止开发者在代码中引入新的漏洞和错误。
+
+要扫描拉取请求，请运行 `analyze` 命令，并使用 `--ref` 标记指定拉取请求。 引用是 `refs/pull/<PR-number>/head` 或 `refs/pull/<PR-number>/merge`，具体取决于您是检出拉取请求分支的 HEAD 提交，还是与基础分支合并提交。
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**注意**：如果您用第三方工具分析代码并希望结果显示为拉请求检查， 您必须运行 `upload` 命令，并使用 `--ref` 标志来指定合并请求而不是分支。 引用是 `refs/pull/<PR-number>/head` 或 `refs/pull/<PR-number>/merge`。
+
+{% endnote %}
+
+### 覆盖自动语言检测
+
+{% data variables.product.prodname_codeql_runner %} 自动检测并扫描用支持的语言编写的代码。
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+要覆盖自动语言检测，请运行 `init` 命令：带 `--languages` 标志，后跟以逗号分隔的语言关键字列表。 The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+### 运行额外查询
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+要添加一个或多个查询，请将逗号分隔的路径列表传递给 `init` 命令的 `--queries` 标志。 您也可以在配置文件中指定额外查询。
+
+如果您还使用配置文件进行自定义设置，并且还使用 `--queries` 标志指定额外查询，则 {% data variables.product.prodname_codeql_runner %} 将使用 <nobr>`--queries`</nobr> 标志指定的额外查询，而不是配置文件中的任何查询。 如果您要运行使用标志指定的额外查询与配置文件中指定的查询的组合，请在传递给 <nobr>`--queries`</nobr> 的值之前加上前缀 `+` 符号。 有关配置文件的示例，请参阅“[配置文件示例](#example-configuration-files)”。
+
+在下面的示例中，`+` 符号可确保 {% data variables.product.prodname_codeql_runner %} 结合使用额外查询与所引用配置文件中指定的任何查询。
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+### 使用第三方代码扫描工具
+
+您可以在单独的配置文件中指定自定义设置，而不向 {% data variables.product.prodname_codeql_runner %} 命令传递额外信息。
+
+配置文件为 YAML 文件。 它使用的语法类似于 {% data variables.product.prodname_actions %} 的工作流程语法，如下例所示。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions)”。
+
+使用 `init` 命令的 `--config-file` 标志指定配置文件。 标志 <nobr>`--config-file`</nobr> 的值是您要使用的配置文件的路径。 此示例加载配置文件 _.github/codeql/codeql-config.yml_。
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+#### 配置文件示例
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+### 为编译语言配置 {% data variables.product.prodname_code_scanning %}
+
+对于编译语言 C/C++、C# 和 Java，{% data variables.product.prodname_codeql %} 在分析之前构建代码。 {% data reusables.code-scanning.analyze-go %}
+
+对于许多常见的构建系统，{% data variables.product.prodname_codeql_runner %} 可以自动构建代码。 要尝试自动构建代码，请在 `init` 与 `analyze` 步骤之间运行 `autobuild`。 请注意，如果您的仓库需要特定版本的构建工具，您可能需要先手动安装该构建工具。
+
+`autobuild` 进程仅尝试为仓库构建_一种_编译语言。 自动选择用于分析的语言是涵盖文件最多的语言。 如果您要明确选择某种语言，请使用 `autobuild` 命令的 `--language` 标志。
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+如果 `autobuild` 命令无法构建您的代码，您可以在 `init` 与 `analyze` 步骤之间手动运行构建步骤。 更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)”。
+
+### 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %}
+
+默认情况下，当您运行 `analyze` 命令时，{% data variables.product.prodname_codeql_runner %} 上传来自 {% data variables.product.prodname_code_scanning %} 的结果。 您也可以使用 `upload` 命令单独上传 SARIF 文件。
+
+上传数据后，{% data variables.product.prodname_dotcom %} 将在您的仓库中显示警报。
+- 如果您上传到拉取请求，例如 `--ref refs/pull/42/merge` 或 `--ref refs/pull/42/head`，则结果在拉取请求检查中显示为警报。 更多信息请参阅“[对拉取请求中的代码扫描警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”。
+- 如果您上传到分支，例如 `--ref refs/heads/my-branch`，则结果将显示在仓库的 **Security（安全）**选项卡中。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。
+
+### {% data variables.product.prodname_codeql_runner %} 命令引用
+
+{% data variables.product.prodname_codeql_runner %} 支持以下命令和标志。
+
+#### `init`
+
+为每种要分析的语言初始化 {% data variables.product.prodname_codeql_runner %} 并创建 {% data variables.product.prodname_codeql %} 数据库。
+
+| 标志                               | 必选 | 输入值                                                                                                                                 |
+| -------------------------------- |:--:| ----------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                   | ✓  | 要初始化的仓库名称。                                                                                                                          |
+| `--github-url`                   | ✓  | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。                                                                         |
+| `--github-auth`                  | ✓  | {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。                                                                      |
+| `--languages`                    |    | 要分析的语言列表，以逗号分隔。 默认情况下，{% data variables.product.prodname_codeql_runner %} 检测和分析仓库中所有支持的语言。                                        |
+| `--queries`                      |    | 除了默认的安全查询套件之外，要运行的额外查询列表，以逗号分隔。                                                                                                     |
+| `--config-file`                  |    | 自定义配置文件的路径。                                                                                                                         |
+| `--codeql-path`                  |    | 要使用的 {% data variables.product.prodname_codeql %} CLI 可执行文件副本的路径。 默认情况下，{% data variables.product.prodname_codeql_runner %} 下载副本。 |
+| `--temp-dir`                     |    | 存储临时文件的目录。 默认值为 `./codeql-runner`。                                                                                                  |
+| `--tools-dir`                    |    | 在运行之间存储 {% data variables.product.prodname_codeql %} 工具和其他文件的目录。 默认值为主目录的子目录。                                                       |
+| <nobr>`--checkout-path`</nobr> |    | 检出仓库的路径。 默认值为当前工作目录。                                                                                                                |
+| `--debug`                        |    | 无. 打印更详细的输出。                                                                                                                        |
+| `-h`, `--help`                   |    | 无. 显示命令的帮助。                                                                                                                         |
+
+#### `autobuild`
+
+尝试为编译语言 C/C++、C# 和 Java 构建代码。 对于这些语言，{% data variables.product.prodname_codeql %} 在分析之前构建代码。 在 `init` 与 `analyze` 步骤之间运行 `autobuild`。
+
+| 标志                          | 必选 | 输入值                                                                                |
+| --------------------------- |:--:| ---------------------------------------------------------------------------------- |
+| `--language`                |    | 要构建的语言。 默认情况下，{% data variables.product.prodname_codeql_runner %} 构建涵盖最多文件的编译语言。 |
+| <nobr>`--temp-dir`</nobr> |    | 存储临时文件的目录。 默认值为 `./codeql-runner`。                                                 |
+| `--debug`                   |    | 无. 打印更详细的输出。                                                                       |
+| `-h`, `--help`              |    | 无. 显示命令的帮助。                                                                        |
+
+#### `analyze`
+
+分析 {% data variables.product.prodname_codeql %} 数据库中的代码并将结果上传到 {% data variables.product.product_name %}。
+
+| 标志                                 | 必选 | 输入值                                                                                                                                                                                                                                                                                                                                 |
+| ---------------------------------- |:--:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--repository`                     | ✓  | 要分析的仓库名称。                                                                                                                                                                                                                                                                                                                           |
+| `--commit`                         | ✓  | 要分析的提交的 SHA。 在 Git 和 Azure DevOps 中，这对应于 `git rev-parse HEAD` 的值。 在 Jenkins 中，这对应于 `$GIT_COMMIT`。                                                                                                                                                                                                                                   |
+| `--ref`                            | ✓  | 要分析的引用的名称，例如 `refs/heads/main` 或 `refs/pull/42/merge`。 在 Git 或 Jenkins 中，这对应于 `git symbolic-ref HEAD` 的值。 在 Azure DevOps 中，这对应于 `$(Build.SourceBranch)`。                                                                                                                                                                            |
+| `--github-url`                     | ✓  | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。                                                                                                                                                                                                                                                                         |
+| `--github-auth`                    | ✓  | {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。                                                                                                                                                                                                                                                                      |
+| <nobr>`--checkout-path`</nobr>   |    | 检出仓库的路径。 默认值为当前工作目录。                                                                                                                                                                                                                                                                                                                |
+| `--no-upload`                      |    | 无. 阻止 {% data variables.product.prodname_codeql_runner %} 将结果上传到 {% data variables.product.product_name %}。                                                                                                                                                                                                                       |
+| `--output-dir`                     |    | 存储输出 SARIF 文件的目录。 默认在临时文件目录中。                                                                                                                                                                                                                                                                                                       |
+| `--ram`                            |    | 运行查询时要使用的内存量。 默认使用所有可用的内存。                                                                                                                                                                                                                                                                                                          |
+| <nobr>`--no-add-snippets`</nobr> |    | 无. 从 SARIF 输出排除代码片段。 |{% if currentVersion == "free-pro-team@latest" %}
+| <nobr>`--category`<nobr>           |    | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. 
+{% endif %}
+| `--threads`                        |    | 运行查询时要使用的线程数。 默认使用所有可用的核心。                                                                                                                                                                                                                                                                                                          |
+| `--temp-dir`                       |    | 存储临时文件的目录。 默认值为 `./codeql-runner`。                                                                                                                                                                                                                                                                                                  |
+| `--debug`                          |    | 无. 打印更详细的输出。                                                                                                                                                                                                                                                                                                                        |
+| `-h`, `--help`                     |    | 无. 显示命令的帮助。                                                                                                                                                                                                                                                                                                                         |
+
+#### `上传`
+
+将 SARIF 文件上传到 {% data variables.product.product_name %}。
+
+{% note %}
+
+**注意**：如果您使用 CodeQL 运行器分析代码，则 `analyze` 命令默认会上传结果。 您可以使用 `upload` 命令上传其他工具生成的 SARIF 结果。
+
+{% endnote %}
+
+| 标志                               | 必选 | 输入值                                                                                                                                                      |
+| -------------------------------- |:--:| -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--sarif-file`                   | ✓  | 要上传的 SARIF 文件，或包含多个 SARIF 文件的目录。                                                                                                                         |
+| `--repository`                   | ✓  | 已分析的仓库名称。                                                                                                                                                |
+| `--commit`                       | ✓  | 已分析的提交的 SHA。 在 Git 和 Azure DevOps 中，这对应于 `git rev-parse HEAD` 的值。 在 Jenkins 中，这对应于 `$GIT_COMMIT`。                                                        |
+| `--ref`                          | ✓  | 已分析的引用的名称，例如 `refs/heads/main` 或 `refs/pull/42/merge`。 在 Git 或 Jenkins 中，这对应于 `git symbolic-ref HEAD` 的值。 在 Azure DevOps 中，这对应于 `$(Build.SourceBranch)`。 |
+| `--github-url`                   | ✓  | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。                                                                                              |
+| `--github-auth`                  | ✓  | {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。                                                                                           |
+| <nobr>`--checkout-path`</nobr> |    | 检出仓库的路径。 默认值为当前工作目录。                                                                                                                                     |
+| `--debug`                        |    | 无. 打印更详细的输出。                                                                                                                                             |
+| `-h`, `--help`                   |    | 无. 显示命令的帮助。                                                                                                                                              |
diff --git a/translations/zh-CN/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
index b6a6d3cfbe..8c8b86a1ae 100644
--- a/translations/zh-CN/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/zh-CN/content/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -36,7 +38,7 @@ topics:
 
 {% note %}
 
-{% if currentversion == "github-ae@latest" %} **注意**：有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
+{% if currentVersion == "github-ae@latest" %} **注意**：有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
 {% else %}
 **注**：如果使用 {% data variables.product.prodname_actions %} 的自托管运行器，您可能需要安装其他软件才能使用 `autobuild` 进程。 此外，如果您的仓库需要特定版本的构建工具，您可能需要手动安装它。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/secure-coding/index.md b/translations/zh-CN/content/code-security/secure-coding/index.md
index 5b6fbc21aa..2c3c3a3bca 100644
--- a/translations/zh-CN/content/code-security/secure-coding/index.md
+++ b/translations/zh-CN/content/code-security/secure-coding/index.md
@@ -1,7 +1,7 @@
 ---
 title: 查找代码中的安全漏洞和错误
 shortTitle: 安全编码
-intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.'
+intro: '使用{% data variables.product.prodname_code_scanning %}来识别和修复代码中潜在的安全漏洞和其他错误，以确保代码的安全。'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code
@@ -14,6 +14,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 ### 目录
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
@@ -30,6 +32,8 @@ topics:
     {% link_in_list /uploading-a-sarif-file-to-github %}
     {% link_in_list /sarif-support-for-code-scanning %}
 {% link_in_list /running-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-code-scanning-in-your-ci-system %}
-    {% link_in_list /configuring-the-codeql-action-for-compiled-languages %}
-    {% link_in_list /troubleshooting-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /about-codeql-code-scanning-in-your-ci-system %}
+    {% link_in_list /running-codeql-cli-in-your-ci-system %}
+    {% link_in_list /running-codeql-runner-in-your-ci-system %}
+    {% link_in_list /configuring-codeql-runner-in-your-ci-system %}
+    {% link_in_list /troubleshooting-codeql-runner-in-your-ci-system %}
diff --git a/translations/zh-CN/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/zh-CN/content/code-security/secure-coding/integrating-with-code-scanning.md
index c05470c84f..6149b9c68a 100644
--- a/translations/zh-CN/content/code-security/secure-coding/integrating-with-code-scanning.md
+++ b/translations/zh-CN/content/code-security/secure-coding/integrating-with-code-scanning.md
@@ -15,3 +15,4 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
diff --git a/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
index 83a7b752ed..eb1e52d14e 100644
--- a/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
@@ -1,7 +1,7 @@
 ---
 title: 管理仓库的代码扫描警报
 shortTitle: 管理警报
-intro: '从安全视图中，您可以查看、修复、{% if currentVersion == "enterprise-server@2.22" %}或关闭{% else %}忽略或删除{% endif %}项目代码中潜在漏洞或错误的警报。'
+intro: 从安全的角度，您可以查看、修复、忽略或删除项目代码中潜在漏洞或错误的警报。
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于 {% data variables.product.prodname_code_scanning %} 中的警报
@@ -60,7 +62,7 @@ topics:
 
 任何对仓库具有写入权限的人都可以通过提交对代码的更正来修复警报。 如果仓库已安排对拉取请求运行 {% data variables.product.prodname_code_scanning %}，则最好通过拉取请求提交您的更正。 这将触发对更改的 {% data variables.product.prodname_code_scanning %} 分析，并测试您的修复是否会带来任何新的问题。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)”和“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”。
 
-如果您有仓库的写入权限，您可以通过查看警报摘要并单击 **Closed（已关闭）**来查看已修复的警报。 更多信息请参阅“[查看仓库的警报](#viewing-the-alerts-for-a-repository)”。 “Closed（已关闭）”列表显示已修复的警报和用户{% if currentVersion == "enterprise-server@2.22" %}已关闭{% else %}已忽略{% endif %}的警报。
+如果您有仓库的写入权限，您可以通过查看警报摘要并单击 **Closed（已关闭）**来查看已修复的警报。 更多信息请参阅“[查看仓库的警报](#viewing-the-alerts-for-a-repository)”。 “Closed（已关闭）”列表显示已修复的警报和用户已忽略的警报。
 
 警报只能在一个分支中修复。 您可以在警报摘要上使用“Branch（分支）”下拉菜单检查警报是否是在特定分支中修复的。
 
@@ -70,14 +72,6 @@ topics:
 ![按分支过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 {% endif %}
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-### 关闭警报
-
-关闭警报是解决您认为不需要修复的警报的一种方式。 {% data reusables.code-scanning.close-alert-examples %}
-
-{% else %}
-
 ### 忽略或删除警报
 
 有两种方法可以关闭警报。 您可以修复代码中的问题，也可以忽略警报。 或者，如果您具有仓库的管理员权限，您可以删除警报。 删除警报适用于以下情况：您设置了 {% data variables.product.prodname_code_scanning %} 工具，然后决定删除它，或者您配置了 {% data variables.product.prodname_codeql %} 分析，但查询集超出您的需求，于是您从工具中删除了某些查询。 在这两种情况下，删除警报允许您清理 {% data variables.product.prodname_code_scanning %} 结果。 您可以在 **Security（安全）**选项卡中从摘要列表删除警报。
@@ -101,20 +95,9 @@ topics:
 
 要忽略或删除警报：
 
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
-{% data reusables.code-scanning.click-alert-in-list %}
-1. 选择 **Close（关闭）**下拉菜单，然后单击关闭警报的原因。    
-   ![通过 Close（关闭）下拉菜单选择关闭警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 1. 如果您拥有仓库管理员权限，想要删除此 {% data variables.product.prodname_code_scanning %} 工具的警报，请选中部分或全部复选框，然后单击 **Delete（删除）**。
 
    ![删除警报](/assets/images/help/repository/code-scanning-delete-alerts.png)
@@ -145,8 +128,6 @@ topics:
 
 如果项目有多个由于相同原因要忽略的警报，您可以从警报摘要中批量忽略它们。 通常，您需要过滤列表，然后忽略所有匹配的警报。 例如，您可能想要忽略项目中所有已标记为特定通用缺陷枚举 (CWE) 漏洞的当前警报。
 
-{% endif %}
-
 ### 延伸阅读
 
 - “[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”
diff --git a/translations/zh-CN/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..7e1e4f22c5
--- /dev/null
+++ b/translations/zh-CN/content/code-security/secure-coding/running-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,458 @@
+---
+title: Running CodeQL CLI in your CI system
+shortTitle: Running CodeQL CLI
+intro: '您可以使用 {% data variables.product.prodname_codeql_cli %} 在第三方持续集成系统中执行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.1'
+  github-ae: next
+topics:
+  - Security
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### 关于 {% data variables.product.prodname_codeql_cli %}
+
+您可以使用 {% data variables.product.prodname_codeql_cli %} 在第三方持续集成 (CI) 系统中处理的代码上运行 {% data variables.product.prodname_code_scanning %}。 {% data reusables.code-scanning.about-code-scanning %} 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)”。
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_codeql_runner %} in your CI system, or {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)". For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% note %}
+
+**Note:** {% if currentVersion == "free-pro-team@latest" %}
+The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. 有关信息请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”和“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
+{%- else %}The {% data variables.product.prodname_codeql_cli %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+{% endif %}
+{% endnote %}
+
+### 下载 {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+### Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. 例如：
+
+```shell
+$ wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ../codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/extraction-root/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/extraction-root/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+### Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve languages` if `/extraction-root/codeql` is on the `PATH`.
+- `/extraction-root/codeql/codeql resolve languages` otherwise.
+
+**Example of successful output:**
+```
+cpp (/extraction-root/codeql/cpp)
+csharp (/extraction-root/codeql/csharp)
+csv (/extraction-root/codeql/csv)
+go (/extraction-root/codeql/go)
+html (/extraction-root/codeql/html)
+java (/extraction-root/codeql/java)
+javascript (/extraction-root/codeql/javascript)
+properties (/extraction-root/codeql/properties)
+python (/extraction-root/codeql/python)
+xml (/extraction-root/codeql/xml)
+```
+
+If the {% data variables.product.prodname_codeql_cli %} is unable to resolve the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+### Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. 更多信息请参阅“[构建 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+
+### Using the {% data variables.product.prodname_codeql_cli %} to generate data and upload it to {% data variables.product.product_name %}
+
+You call the {% data variables.product.prodname_codeql_cli %} to analyze the codebase in three steps:
+
+1. Create a {% data variables.product.prodname_codeql %} database to represent a single programming language in the repository using: `codeql database create`
+2. Run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file using: `codeql database analyze`
+3. Upload the SARIF file to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts using: `codeql github upload-results`
+
+Each command has a few mandatory options with additional options that you can use to modify the behavior of the command. You can display the command-line help for any command using the <nobr>`--help`</nobr> 选项.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+#### Creating a {% data variables.product.prodname_codeql %} database to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch checkout the head of the branch that you want to analyze.
+    - For a pull request checkout either the head commit of the pull request, or check out a {% data variables.product.product_name %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Run `codeql database create` from the checkout root of your repository.
+  ```shell
+  codeql database create &lt;database&gt; --language=&lt;language-identifier&gt;
+  ```
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      选项
+    </th>
+    
+    <th align="center">
+      必选
+    </th>
+    
+    <th>
+      用法
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the identifier for the language to create a database for, one of: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> to analyze TypeScript code).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      可选. Use if you run the CLI outside the checkout root of the repository. By default, the <code>database create</code> command assumes that the current directory is the root directory for the source files, use this option to specify a different location.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Optional for compiled languages. Use if you want to override the CLI's automatic build system detection and compilation. Specify the build command or script that invokes the compiler. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Do not use this option for Python and JavaScript/TypeScript analysis.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### 基本示例
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+... 
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+For more information and examples, see [Creating {% data variables.product.prodname_codeql %} databases ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+#### Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  &lt;queries&gt; 
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      选项
+    </th>
+    
+    <th align="center">
+      必选
+    </th>
+    
+    <th>
+      用法
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;database&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;queries&gt;</code>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <code>&lt;language&gt;-code-scanning.qls</code> where <code>&lt;language&gt;</code> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle look in <code>/extraction-root/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. For information about creating your own query suite, see <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Creating CodeQL query suites</a> in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% if currentVersion == "free-pro-team@latest" %}<code>sarif-latest</code>{% else %}<code>sarifv2.1.0</code>{% endif %}. 更多信息请参阅“<a href="/code-security/secure-coding/sarif-support-for-code-scanning">{% data variables.product.prodname_code_scanning %} 的 SARIF 支持</a>”。
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--output`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify where to save the SARIF results file.{% if currentVersion == "free-pro-team@latest" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      可选. Specify a category to include in the SARIF results  file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the <code>&lt;run&gt;.automationId</code> property in SARIF v1, the <code>&lt;run&gt;.automationLogicalId</code> property in SARIF v2, and the <code>&lt;run&gt;.automationDetails.id</code> property in SARIF v2.1.0. |{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      可选. Use if you want to use more than one thread to run queries. The default value is <code>1</code>. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify <code>0</code>.
+    </td>
+  </tr>
+</table>
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### 基本示例
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --format={% if currentVersion == "free-pro-team@latest" %}sarif-latest{% else %}sarifv2.1.0{% endif %} \
+    --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/
+    codeql-javascript/AngularJS/DisablingSce.ql.
+... 
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+#### Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Generating a token for authentication with {% data variables.product.product_name %}](#generating-a-token-for-authentication-with-github) above). We recommend that you review your CI system's guidance on the secure use of the secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on the SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+<table spaces-before="0">
+  <tr>
+    <th>
+      选项
+    </th>
+    
+    <th align="center">
+      必选
+    </th>
+    
+    <th>
+      用法
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--repository`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the <em x-id="3">OWNER/NAME</em> of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% if currentVersion == "free-pro-team@latest" %}, unless the repository is public{% endif %}. 更多信息请参阅“<a href="/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository">管理仓库的安全和分析设置</a>”。
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--ref` 指定拉取请求</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the name of the <code>ref</code> you checked out and analyzed so that the results can be matched to the correct code. For a branch use: <code>refs/heads/BRANCH-NAME</code>, for the head commit of a pull request use <code>refs/pulls/NUMBER/head</code>, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use <code>refs/pulls/NUMBER/merge</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--commit`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the full SHA of the commit you analyzed.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the SARIF file to load.{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Specify the URL for {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      可选. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a <code>GITHUB_TOKEN</code> environment variable set with this token.
+    </td>
+  </tr>
+</table>
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+##### 基本示例
+
+```
+$ echo $UPLOAD_TOKEN | codeql  github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. Alerts are shown directly in the pull request or on the **Security** tab for branches, depending on the code that was checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+### 延伸阅读
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/zh-CN/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
index 2e506426a6..c4f0d38467 100644
--- a/translations/zh-CN/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
+++ b/translations/zh-CN/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md
@@ -13,13 +13,19 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于使用容器化构建的 {% data variables.product.prodname_code_scanning %}
 
 如果为编译语言设置 {% data variables.product.prodname_code_scanning %}，并且在容器化环境中构建代码，则分析可能会失败，并返回错误消息“No source code was seen during the build（在构建过程中没有看到源代码）”。 这表明 {% data variables.product.prodname_codeql %} 在代码编译过程中无法监视代码。
 
-您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 这适用于您使用 {% data variables.product.prodname_codeql_runner %} 或 {% data variables.product.prodname_actions %}。 如果您使用 {% data variables.product.prodname_codeql_runner %}，请在代码构建容器中运行它。 有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)”。 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_cli %}, the {% data variables.product.prodname_codeql_runner %}, or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。
+{% else %}
+You must run {% data variables.product.prodname_codeql %} inside the container in which you build your code. This applies whether you are using the {% data variables.product.prodname_codeql_runner %} or {% data variables.product.prodname_actions %}. For the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" for more information. 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。
+{% endif %}
 
 ### 依赖项
 
@@ -47,7 +53,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -59,16 +68,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/zh-CN/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..cc5307a1e6
--- /dev/null
+++ b/translations/zh-CN/content/code-security/secure-coding/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,161 @@
+---
+title: Running CodeQL runner in your CI system
+shortTitle: Running CodeQL runner
+intro: '您可以使用 {% data variables.product.prodname_codeql_runner %} 在第三方持续集成系统中执行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+<!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### 关于 {% data variables.product.prodname_codeql_runner %}
+
+The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)”。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. The runner is more complex and less forgiving to set up than the CLI, and is recommended only if you need its capability to analyze multiple compiled languages with a single build, or to integrate with complex build processes. For more information, see "[About CodeQL code scanning in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+{% endif %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. 相关信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。
+
+{% data variables.product.prodname_codeql_runner %} 是在 {% data variables.product.prodname_dotcom %} 仓库的检出上运行 {% data variables.product.prodname_codeql %} 分析的命令行工具。 您可以将运行器添加到第三方系统，然后调用运行器以分析代码并将结果上传到 {% data variables.product.product_name %}。 这些结果在仓库中显示为 {% data variables.product.prodname_code_scanning %} 警报。
+
+{% note %}
+
+**注:**
+{% if currentVersion == "free-pro-team@latest" %}
+* {% data variables.product.prodname_codeql_runner %} 使用 {% data variables.product.prodname_codeql %} CLI 来分析代码，因此具有相同的许可条件。 它可自由用于 {% data variables.product.prodname_dotcom_the_website %} 上维护的公共仓库，并且可用于具有 {% data variables.product.prodname_advanced_security %} 许可证的客户所拥有的私有仓库。 有关信息请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”和“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
+{% else %}
+* {% data variables.product.prodname_codeql_runner %} 可用于拥有 {% data variables.product.prodname_advanced_security %} 许可证的客户。
+{% endif %}
+{% if currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}
+* 请勿将 {% data variables.product.prodname_codeql_runner %} 与 {% data variables.product.prodname_codeql %} CLI 混淆。 The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. 更多信息请参阅“[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)”。
+{% endif %}
+{% endnote %}
+
+### 下载 {% data variables.product.prodname_codeql_runner %}
+
+您可以从 https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases 下载 {% data variables.product.prodname_codeql_runner %} 。 在某些操作系统上，您可能需要更改下载文件的权限才能运行它。
+
+在 Linux 上：
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+在 macOS 中:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
+
+### 将 {% data variables.product.prodname_codeql_runner %} 添加到 CI 系统
+
+下载 {% data variables.product.prodname_codeql_runner %} 并确认它可执行后，应将运行器提供给您打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 例如，您可以配置每台服务器从中央内部位置复制运行器。 或者，您也可以使用 REST API 直接从 {% data variables.product.prodname_dotcom %} 获取运行器，例如：
+
+```shell
+wget https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+除此之外，每个 CI 服务器还需要：
+
+- {% data variables.product.prodname_github_app %} 或供 {% data variables.product.prodname_codeql_runner %} 使用的个人访问令牌。 您必须使用范围为 `repo` 的访问令牌，或者具有 `security_events` 写入权限以及 `metadata` 和 `contents` 读取权限的 {% data variables.product.prodname_github_app %}。 更多信息请参阅“[构建 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+- 访问与此 {% data variables.product.prodname_codeql_runner %} 发行版相关联的 {% data variables.product.prodname_codeql %} 包。 此包包含 {% data variables.product.prodname_codeql %} 分析所需的查询和库，以及供运行器内部使用的 {% data variables.product.prodname_codeql %} CLI。 更多信息请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
+
+提供 {% data variables.product.prodname_codeql %} 包访问权限的选项：
+
+1. 允许 CI 服务器访问 https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} 可以自动下载捆绑包。
+1. 手动下载/提取捆绑包，将其与其他中央资源一起存储，并使用 <nobr>`--codeql-path`</nobr> 标记指定捆绑包在调用中的位置，以初始化 {% data variables.product.prodname_codeql_runner %}。
+
+### 调用 {% data variables.product.prodname_codeql_runner %}
+
+您应该从要分析的仓库的检出位置调用 {% data variables.product.prodname_codeql_runner %}。 两个主要命令是：
+
+1. `init` 需要初始化运行器并为需要分析的每种语言创建一个 {% data variables.product.prodname_codeql %} 数据库。 这些数据库由后续命令填充和分析。
+1. `analyze` 需要填充 {% data variables.product.prodname_codeql %} 数据库、进行分析并将结果上传到 {% data variables.product.product_name %}。
+
+对于这两个命令，都必须指定 {% data variables.product.product_name %} 的 URL、仓库 *OWNER/NAME*以及 {% data variables.product.prodname_github_apps %} 或用于身份验证的个人访问令牌。 您还需要指定 CodeQL 捆绑包的位置，除非 CI 服务器能够直接从 `github/codeql-action` 仓库下载它。
+
+您可以配置 {% data variables.product.prodname_codeql_runner %} 存储 CodeQL 包的位置以便将来在服务器上进行分析，使用： <nobr>`--tools-dir`</nobr> 标志；并配置在分析过程中存储临时文件的位置，使用： <nobr>`--temp-dir`</nobr>.
+
+要查看运行器的命令行引用，请使用 `-h` 标志。 例如，要列出所有运行的命令：`codeql-runner-OS -h`，或列出所有可用于 `init` 命令运行的标志：`codeql-runner-OS init -h`（其中 `OS` 因使用的可执行文件而异）。 更多信息请参阅“[在 CI 系统中配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)”。
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+#### 基本示例
+
+此示例在 Linux CI 服务器上对托管在 `{% data variables.command_line.git_url_example %}` 上的 `octo-org/example-repo` 仓库运行 {% data variables.product.prodname_codeql %} 分析。 这个过程非常简单，因为仓库只包含可通过 {% data variables.product.prodname_codeql %} 直接分析的语言，而无需构建（例如 Go、JavaScript、Python 和 TypeScript）。
+
+在此示例中，服务器可以直接从 `github/codeql-action` 仓库下载 {% data variables.product.prodname_codeql %} 捆绑包，因此无需使用 `--codeql-path` 标记。
+
+1. 检出要分析的仓库。
+1. 移至检出仓库的目录。
+1. 初始化 {% data variables.product.prodname_codeql_runner %} 并为检测到的语言创建 {% data variables.product.prodname_codeql %}。
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+#### 编译语言示例
+
+此示例与前面的示例相似，但此例中的仓库含有用 C/C++、C# 或 Java 编写的代码。 要为这些语言创建 {% data variables.product.prodname_codeql %} 数据库，CLI 需要监控构建。 在初始化过程结束时，运行器会报告您需要在构建代码之前设置环境的命令。 您需要在调用正常的 CI 构建进程之前运行此命令，然后运行 `analyze` 命令。
+
+1. 检出要分析的仓库。
+1. 移至检出仓库的目录。
+1. 初始化 {% data variables.product.prodname_codeql_runner %} 并为检测到的语言创建 {% data variables.product.prodname_codeql %}。
+
+    ```shell
+    $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      ```
+
+1. 获取通过 `init` 操作生成的脚本，以设置监控构建的环境。 请注意以下代码片段中的先导点和空间。
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. 构建代码。 在 macOS 上，您需要使用环境变量 `$CODEQL_RUNNER` 构建命令前缀。 For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)#no-code-found-during-the-build)."
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**注：**如果使用容器化构建，您需要在进行构建任务的容器中运行 {% data variables.product.prodname_codeql_runner %}。
+
+{% endnote %}
+
+### 延伸阅读
+
+- "[在 CI 系统中配置 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
+- "[CI 系统中的{% data variables.product.prodname_codeql_runner %} 故障排除](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
diff --git a/translations/zh-CN/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/zh-CN/content/code-security/secure-coding/sarif-support-for-code-scanning.md
index d5ac0dbca9..7a92c98b86 100644
--- a/translations/zh-CN/content/code-security/secure-coding/sarif-support-for-code-scanning.md
+++ b/translations/zh-CN/content/code-security/secure-coding/sarif-support-for-code-scanning.md
@@ -3,6 +3,7 @@ title: 对代码扫描的 SARIF 支持
 shortTitle: SARIF 支持
 intro: '要在 {% data variables.product.prodname_dotcom %} 上的仓库中显示第三方静态分析工具的结果，您需要将结果存储在 SARIF 文件中，以支持用于 {% data variables.product.prodname_code_scanning %} 的 SARIF 2.1.0 JSON 架构的特定子集。 如果使用默认 {% data variables.product.prodname_codeql %} 静态分析引擎，结果将自动显示于您在 {% data variables.product.prodname_dotcom %} 上的仓库中。'
 product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 4
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
@@ -14,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于 SARIF 支持
@@ -22,7 +25,15 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 
 
 要从第三方静态代码分析引擎上传 SARIF 文件，需确保上传的文件使用 SARIF 2.1.0 版本。 {% data variables.product.prodname_dotcom %} 将剖析 SARIF 文件，并在 {% data variables.product.prodname_code_scanning %} 过程中使用仓库中的结果显示警报。 更多信息请参阅“[将 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)”。 有关 SARIF 2.1.0 JSON 架构的更多信息，请参阅 [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json)。
 
-如果您结合使用 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_codeql_workflow %}，或者使用 {% data variables.product.prodname_codeql_runner %}，则 {% data variables.product.prodname_code_scanning %} 结果将自动使用受支持的 SARIF 2.1.0 子集。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”或“[在 CI 系统中运行 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)”。
+如果您结合使用 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_codeql_workflow %}，或者使用 {% data variables.product.prodname_codeql_runner %}，则 {% data variables.product.prodname_code_scanning %} 结果将自动使用受支持的 SARIF 2.1.0 子集。 For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system#uploading-results-to-github)."{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below.
+
+{% endif %}
 
 {% data variables.product.prodname_dotcom %} 使用 SARIF 文件中的属性来显示警报。 例如，`shortDescription` 和 `fullDescription` 出现在 {% data variables.product.prodname_code_scanning %} 警报的顶部。 `location` 允许 {% data variables.product.prodname_dotcom %} 在代码文件中显示注释。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。
 
@@ -122,6 +133,45 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 
 | `region.endLine`       | **必选。**区域中最后一个字符的行号。                                                                                                                                                                                                                                                                                                  |
 | `region.endColumn`     | **必选。**区域结束后字符的列编号。                                                                                                                                                                                                                                                                                                   |
 
+{% if currentVersion == "free-pro-team@latest" %}
+#### `runAutomationDetails` object
+
+The `runAutomationDetails` object contains information that specifies the identity of a run.
+
+{% note %}
+
+**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `<run>.automationId` for SARIF v1 and `<run>.automationLogicalId` for SARIF v2.
+
+{% endnote %}
+
+| 名称   | 描述                                                                                                                                                                                                                                    |
+| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id` | **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. |
+
+The use of the `runAutomationDetails` object is optional.
+
+The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it.
+
+Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run.
+
+`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after.
+
+| `id`                         | 分类                | `run_id`              |
+| ---------------------------- | ----------------- | --------------------- |
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01            |
+| my-analysis/tool1/           | my-analysis/tool1 | _no `run-id`_         |
+| my-analysis for tool1        | _no category_     | my-analysis for tool1 |
+
+- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021.
+- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category.
+- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category.
+
+For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation.
+
+Note that the rest of the supported fields are ignored.
+
+{% endif %}
+
 ### SARIF 输出文件示例
 
 这些示例 SARIF 输出文件显示支持的属性和示例值。
@@ -130,7 +180,6 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 
 
 此 SARIF 输出文件的示例值显示了 {% data variables.product.prodname_code_scanning %} 结果正常运行所需的最少属性。 如果您删除任何属性或不包含值，此数据将无法正确显示或在 {% data variables.product.prodname_dotcom %} 上同步。
 
-
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -181,6 +230,260 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 
 
 此 SARIF 输出文件的示例值显示了 {% data variables.product.prodname_code_scanning %} 的所有受支持 SARIF 属性。
 
+{% if currentVersion == "free-pro-team@latest" %}
+```json
+{
+  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": { 
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+{% else %}
 ```json
 {
   "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
@@ -430,3 +733,4 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 
   ]
 }
 ```
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
index 4da16836ca..461f03140e 100644
--- a/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
+++ b/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md
@@ -17,6 +17,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -33,7 +35,7 @@ topics:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 2" %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %}
+4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-proteam@latest" or currentVersion ver_gt "enterprise-server@2. 2" %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %}
 5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
 
    一般来说，您可以提交 {% data variables.product.prodname_codeql_workflow %} 而不对其做任何更改。 但是，许多第三方工作流程需要额外的配置，因此在提交之前请阅读工作流程中的注释。
diff --git a/translations/zh-CN/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
index c74b542f48..a960b2d7b6 100644
--- a/translations/zh-CN/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/zh-CN/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md
@@ -14,13 +14,15 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于拉取请求上的 {% data variables.product.prodname_code_scanning %} 结果
 
 在仓库中，如果 {% data variables.product.prodname_code_scanning %} 被配置为拉取请求检查，则 {% data variables.product.prodname_code_scanning %} 将检查拉取请求中的代码。 默认情况下，这仅限于针对默认分支的拉取请求，但是您可以在 {% data variables.product.prodname_actions %} 或第三方 CI/CD 系统中更改此配置。 如果合并分支给目标分支带来新的 {% data variables.product.prodname_code_scanning %} 警报，这些警报将在拉取请求中被报告为检查结果。 警报还将在拉取请求的 **Files changed（文件已更改）**选项卡中显示为注释。 如果您拥有仓库的写入权限，您可以在 **Security（安全）**选项卡中查看任何现有的 {% data variables.product.prodname_code_scanning %} 警报。 有关仓库警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。
 
-如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 如果拉取请求针对使用 {% data variables.product.prodname_code_scanning %} 的受保护分支，并且仓库所有者配置了必需状态检查，则您必须修复或{% if currentVersion == "enterprise-server@2.22" %}关闭{% else %}忽略{% endif %}所有错误警报，然后才能合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。
+如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 如果拉取请求针对使用 {% data variables.product.prodname_code_scanning %} 的受保护分支，并且仓库所有者配置了必需状态检查，则您必须修复或忽略所有错误警报，然后才能合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。
 
 ![拉取请求上失败的 {% data variables.product.prodname_code_scanning %} 检查](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -44,18 +46,10 @@ topics:
 
 ![显示更多信息的警报说明和链接](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}解决{% else %}修复{% endif %}拉取请求上的警报
+### 修复拉取请求上的警报
 
 任何对拉取请求具有推送权限的人都可以修复在该拉取请求上已识别的 {% data variables.product.prodname_code_scanning %} 警报。 如果将更改提交到拉取请求，这将触发拉取请求检查的新运行。 如果您的更改修复了问题，则警报将被关闭，注释将被删除。
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
-如果您认为警报不需要修复，则具有写入权限的用户可以手动关闭警报。 {% data reusables.code-scanning.close-alert-examples %} 如果您对仓库有写入权限，则 **Close（关闭）**按钮在注释和警报视图中可用。
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
 ### 忽略拉取请求上的警报
 
 关闭警报的另一种办法是忽略它。 您可以忽略您认为不需要修复的警报。 {% data reusables.code-scanning.close-alert-examples %} 如果您对仓库有写入权限，则 **Dismiss（忽略）**按钮在代码注释和警报摘要中可用。 单击 **Dismiss（忽略）**时，您将被提示选择关闭警报的原因。
@@ -67,5 +61,3 @@ topics:
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
 有关忽略警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。
-
-{% endif %}
diff --git a/translations/zh-CN/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..fe2f6bc004
--- /dev/null
+++ b/translations/zh-CN/content/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,63 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshooting CodeQL runner
+intro: '如果您在 {% data variables.product.prodname_codeql_runner %} 方面遇到问题，可使用这些提示来排除故障。'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.0'
+  github-ae: '*'
+topics:
+  - Security
+---
+
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
+{% data reusables.code-scanning.beta-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+### `init` 命令耗时太长
+
+在 {% data variables.product.prodname_codeql_runner %} 可以构建和分析代码之前，它需要访问 {% data variables.product.prodname_codeql %} 包，其中包含 {% data variables.product.prodname_codeql %} CLI 和 {% data variables.product.prodname_codeql %} 库。
+
+首次在计算机上使用 {% data variables.product.prodname_codeql_runner %} 时，`init` 命令会将 {% data variables.product.prodname_codeql %} 包下载到您的计算机上。 此下载可能需要几分钟时间。
+{% data variables.product.prodname_codeql %} 包在运行之间缓存，因此如果您在同一台计算机上再次使用 {% data variables.product.prodname_codeql_runner %}，它不会再次下载 {% data variables.product.prodname_codeql %} 包。
+
+为避免这种自动下载，您可以手动将 {% data variables.product.prodname_codeql %} 包下载到您的计算机上，并使用 `init` 命令的 `--codeql-path` 标志指定路径。
+
+### 构建过程中找不到代码
+
+如果用于 {% data variables.product.prodname_codeql_runner %} 的 `analyze` 命令失败并返回错误 `No source code was seen during the build`，这表明 {% data variables.product.prodname_codeql %} 无法监视您的代码。 有几个原因可以解释这种失败。
+
+1. 自动语言检测发现了受支持的语言，但仓库中没有该语言的可分析代码。 一个典型的例子是，我们的语言检测服务发现了一个与特定的编程语言相关的文件，例如 `.h` 或 `.gyp` 文件，但仓库中没有相应的可执行代码。 要解决此问题，您可以使用 `init` 命令的 `--languages` 标志，手动定义要分析的语言。 更多信息请参阅“[在 CI 系统中配置 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)”。
+
+1. 您没有使用 `autobuild` 命令分析编译语言，并且在 `init` 步骤后手动运行构建步骤。 For the build to work, you must set up the environment such that the {% data variables.product.prodname_codeql_runner %} can monitor the build process. `init` 命令生成如何导出所需环境变量的指令， 因此您可以在运行 `init` 命令后复制和运行脚本。
+   - 在 macOS 和 Linux 上：
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - 在 Windows 上，使用命令 shell (`cmd`) 或批处理文件 (`.bat`)：
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - 在 Windows 上，使用 PowerShell ：
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   环境变量也存储在文件 `codeql-runner/codeql-env.json` 中。 此文件包含单个 JSON 对象，它将环境变量键映射到值。 如果无法运行由 `init` 命令生成的脚本，您可以改用 JSON 格式的数据。
+
+   {% note %}
+
+   **注：**如果您使用 `init` 命令的 `--temp-dir` 标志来指定临时文件的自定义目录，则 `codeql-env` 文件的路径可能不同。
+
+   {% endnote %}
+
+1. 您没有使用 `autobuild` 命令分析 macOS 上的编译语言，并且在 `init` 步骤后手动运行构建步骤。 如果启用了 SIP（系统完整性保护，OSX 最新版本默认启用），则分析可能会失败。 为解决此问题，将使用 `$CODEQL_RUNNER` 环境变量前缀构建命令。 例如，如果您的构建命令是 `cmd arg1 arg2`，则应运行 `$CODEQL_RUNNER cmd arg1 arg2`。
+
+1. 代码在容器或在单独的计算机上构建。 如果您使用容器化的构建，或者将构建外包给另一台计算机，请确保在容器或您执行构建任务的计算机上运行 {% data variables.product.prodname_codeql_runner %}。 更多信息请参阅“[在容器中运行 CodeQL 代码扫描](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)”。
diff --git a/translations/zh-CN/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
index fb36ebeda5..4905189658 100644
--- a/translations/zh-CN/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
+++ b/translations/zh-CN/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md
@@ -15,6 +15,8 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -24,18 +26,19 @@ topics:
 
 您可以使用许多静态分析安全测试工具来生成 SARIF 文件，包括 {% data variables.product.prodname_codeql %}。 结果必须使用 SARIF 版本 2.1.0。 更多信息请参阅“[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/code-security/secure-coding/sarif-support-for-code-scanning)”。
 
-您可以使用 {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} （如果您的组织正在参与测试计划，则可以使用）{% endif %}、{% data variables.product.prodname_code_scanning %} API 或 {% data variables.product.prodname_codeql_runner %} 上传结果。 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用：
+You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}the {% data variables.product.prodname_codeql_cli %}, {% endif %}or the {% data variables.product.prodname_codeql_runner %}. 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用：
 
 - {% data variables.product.prodname_actions %} 来运行 {% data variables.product.prodname_codeql %} 操作，则无需进一步操作。 {% data variables.product.prodname_codeql %} 操作在完成分析后自动上传 SARIF 文件。
-- "[管理工作流程运行](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)"
-- {% data variables.product.prodname_dotcom %} 将在仓库中显示来自上传的 SARIF 文件的 {% data variables.product.prodname_code_scanning %} 警报。 如果您阻止自动上传，在准备上传结果时可以使用 `upload` 命令（更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)”）。
+- "[管理工作流程运行](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+ - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/running-codeql-cli-in-your-ci-system)").{% endif %}
+- {% data variables.product.prodname_dotcom %} 将在仓库中显示来自上传的 SARIF 文件的 {% data variables.product.prodname_code_scanning %} 警报。 如果您阻止自动上传，在准备上传结果时可以使用 `upload` 命令（更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”）。
 - 作为仓库外部构件生成结果的工具，您可以使用 {% data variables.product.prodname_code_scanning %} API 上传文件（更多信息请参阅“[将分析作为 SARIF 数据上传](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)”）。
 
 {% data reusables.code-scanning.not-available %}
 
 ### 通过 {% data variables.product.prodname_actions %} 上传 {% data variables.product.prodname_code_scanning %} 分析
 
-要将第三方 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}，需要 {% data variables.product.prodname_actions %} 工作流程。 更多信息请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”和“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
+要将第三方 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}，需要 {% data variables.product.prodname_actions %} 工作流程。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
 您的工作流需要使用 `upload-sarif` 操作，该操作包含可用于配置上传的输入参数。 它包含可用于配置上传的输入参数。 您将要使用的主要输入参数是 `sarif-file`，它会配置要上传的文件或 SARIF 文件的目录。 目录或文件路径相对于仓库的根目录。 更多信息请参阅 [`upload-sarif` 操作](https://github.com/github/codeql-action/tree/HEAD/upload-sarif)。
 
@@ -63,20 +66,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 4'
+    - cron: '45 15 * * 4'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### 运行 ESLint 分析工具的示例工作流程
@@ -87,7 +92,7 @@ jobs:
 
 工作流程显示了将 ESLint 静态分析工具作为工作流程中一个步骤运行的示例。 `Run ESLint` 步骤运行 ESLint 工具，输出 `results.sarif` 文件。 然后，工作流程使用 `upload-sarif` 操作将 `results.sarif` 文件上传到 {% data variables.product.prodname_dotcom %}。 有关创建工作流程文件的更多信息，请参阅“[GitHub Actions 简介](/actions/learn-github-actions/introduction-to-github-actions)”。
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -95,28 +100,32 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 3'
+    - cron: '45 15 * * 3'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### 延伸阅读
 
 - "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions)"
-- "[查看工作流程历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)"
-- "[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"
+- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)"{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)"{% else %}
+- "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)"{% endif %}
 - “[将分析作为 SARIF 数据上传](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)”
diff --git a/translations/zh-CN/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/zh-CN/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
index 14244e5a14..52c3982ea3 100644
--- a/translations/zh-CN/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/zh-CN/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -14,3 +14,5 @@ topics:
   - Security
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
+
diff --git a/translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index 04e158fa18..53210b09bf 100644
--- a/translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -43,7 +43,7 @@ versions:
 
 在 {% data variables.product.prodname_dotcom_the_website %} 上报告和披露项目漏洞的流程如下：
 
- 如果您是要报告漏洞的漏洞报告者（例如安全研究人员），请先检查相关仓库是否有安全策略。 更多信息请参阅“[关于安全策略](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果有的话，请先了解该流程，然后再联系该仓库的安全团队。
+ 如果您是要报告漏洞的漏洞报告者（例如安全研究人员），请先检查相关仓库是否有安全策略。 更多信息请参阅“[关于安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果有的话，请先了解该流程，然后再联系该仓库的安全团队。
 
  如果没有安全策略，与维护者建立私人通信手段的最有效办法是制造一个要求优先安全联系的问题。 值得注意的是，这个问题将立即公开可见，所以它不应该包括任何有关漏洞的信息。 建立通信后，您可以建议维护者制定安全策略以供将来使用。
 
@@ -55,7 +55,7 @@ versions:
 
  如果您在 {% data variables.product.prodname_dotcom_the_website %} 中发现了安全漏洞，请通过我们协调的披露流程报告该漏洞。 更多信息请参阅 [{% data variables.product.prodname_dotcom %} 安全漏洞奖金](https://bounty.github.com/)网站。
 
- 如果您是维护者， 您可以在管道开始时通过为您的仓库设置安全策略来掌控这一过程，或者以其他方式使安全报告说明清楚可用，例如在项目的 README 文件中。 有关添加安全策略的更多信息，请参阅“[关于安全策略](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果没有安全策略，漏洞报告者可能会尝试向您发送电子邮件或以其他方式私下与您联系。 或者，有人可能会开一个（公共）议题讨论安全问题的细节。
+ 如果您是维护者， 您可以在管道开始时通过为您的仓库设置安全策略来掌控这一过程，或者以其他方式使安全报告说明清楚可用，例如在项目的 README 文件中。 有关添加安全策略的更多信息，请参阅“[关于安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果没有安全策略，漏洞报告者可能会尝试向您发送电子邮件或以其他方式私下与您联系。 或者，有人可能会开一个（公共）议题讨论安全问题的细节。
 
  作为维护者，要在您的代码中披露漏洞，请先在 {% data variables.product.prodname_dotcom %} 中软件包的仓库内创建安全通告。 {% data reusables.security-advisory.security-advisory-overview %} 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
 
diff --git a/translations/zh-CN/content/code-security/security-advisories/index.md b/translations/zh-CN/content/code-security/security-advisories/index.md
index 80d6765878..fd9f336de9 100644
--- a/translations/zh-CN/content/code-security/security-advisories/index.md
+++ b/translations/zh-CN/content/code-security/security-advisories/index.md
@@ -13,7 +13,6 @@ topics:
 
 ### 目录
 
-{% link_in_list /adding-a-security-policy-to-your-repository %}
 {% link_in_list /about-coordinated-disclosure-of-security-vulnerabilities %}
 {% link_in_list /about-github-security-advisories %}
 {% link_in_list /permission-levels-for-security-advisories %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
index 80f32c2987..5636f31519 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md
@@ -79,14 +79,14 @@ For information about permission requirements for actions related to {% data var
 您可以在{% if currentVersion == "free-pro-team@latest" %} 仓库的 Security（安全）选项卡或{% endif %} 仓库的依赖关系图{% if currentVersion == "free-pro-team@latest" %} 中查看影响特定项目的所有警报。更多信息请参阅“[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)”。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-默认情况下，我们会向对受影响仓库具有管理员权限的人员通知新 {% data variables.product.prodname_dependabot_alerts %}。{% endif %} {% if currentversion == "free proteam@latest" %}{% data variables.product.product_name %} 永远不公开披露任何仓库中已经发现的漏洞。 您也可以将 {% data variables.product.prodname_dependabot_alerts %} 设为对操作您拥有或具有管理员权限的仓库的其他人或团队可见。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。
+默认情况下，我们会向对受影响仓库具有管理员权限的人员通知新 {% data variables.product.prodname_dependabot_alerts %}。{% endif %} {% if currentVersion == "free proteam@latest" %}{% data variables.product.product_name %} 永远不公开披露任何仓库中已经发现的漏洞。 您也可以将 {% data variables.product.prodname_dependabot_alerts %} 设为对操作您拥有或具有管理员权限的仓库的其他人或团队可见。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
 默认情况下，我们会向具有受影响仓库管理员权限的人员发送安全警报。 {% data variables.product.product_name %} 从不公开披露在任何仓库中发现的漏洞。
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServersions contains currentversion and currentver_lt "enterprise-server@2 1" %} 更多信息请参阅“[选择通知的递送方式](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。{% endif %}{% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 0" %} 解更多信息请参阅“[配置漏洞依赖项的通知](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)”。{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServersions contains currentVersion and currentver_lt "enterprise-server@2 1" %} 更多信息请参阅“[选择通知的递送方式](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。{% endif %}{% if currentVersion == "free-proteam@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} 解更多信息请参阅“[配置漏洞依赖项的通知](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)”。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 您还可以查看与 {% data variables.product.prodname_advisory_database %} 中的特定漏洞对应的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)”。
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md
index 41fe770ff6..e78cfdc591 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md
@@ -35,6 +35,7 @@ topics:
 如果您启用了安全更新，有时会看到额外的安全更新拉取请求。 这些由默认分支上依赖项的 {% data variables.product.prodname_dependabot %} 警报所触发。 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以更新有漏洞的依赖项。
 
 ### 支持的仓库和生态系统
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
 
 您可以为包含其中一个受支持包管理器的依赖项清单或锁定文件的仓库配置版本更新。 对于某些软件包管理器，您也可以配置依赖项的供应。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)。”
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md
index 3f516de9cb..3251964b21 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md
@@ -1,13 +1,13 @@
 ---
 title: About the dependency graph
-intro: 'You can use the dependency graph to identify all your project''s dependencies. The dependency graph supports a range of popular package ecosystems.'
+intro: You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems.
 redirect_from:
   - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph
 versions:
   free-pro-team: '*'
   enterprise-server: '>=3.0'
 topics:
-  - repositories
+  - Repositories
 ---
 <!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
index b69ded4ecf..5a9dda6ac6 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md
@@ -164,7 +164,7 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-使用 `allow` 选项自定义更新哪些依赖项。 这对有漏洞的依赖项的安全更新没有影响。 您可以使用以下选项：
+使用 `allow` 选项自定义更新哪些依赖项。 This applies to both version and security updates. 您可以使用以下选项：
 
 - `dependency-name`—用于更新名称匹配的依赖项，可以选择使用 `*` 来匹配零个或更多字符。 对于 Java 依赖项，`dependency-name` 属性的格式为：`groupId:artifactId`，例如：`org.kohsuke:github-api`。
 - `dependency-type`—用于更新特定类型的依赖项。
@@ -445,12 +445,12 @@ updates:
 
 #### `rebase-strategy`
 
-默认情况下，{% data variables.product.prodname_dependabot %} 会在检测到冲突时自动变基打开的拉取请求。 使用 `rebase-strategy` 可禁用此行为。
+默认情况下，{% data variables.product.prodname_dependabot %} 会在检测到拉取请求有任何更改时自动变基打开的拉取请求。 使用 `rebase-strategy` 可禁用此行为。
 
 可用的变基策略
 
 - `disabled` 禁用自动变基。
-- `auto` 在检测到冲突时使用默认行为并且变基打开的拉取请求。
+- `auto` 在检测到更改时使用默认行为并且变基打开的拉取请求。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -473,11 +473,11 @@ updates:
 
 要允许 {% data variables.product.prodname_dependabot %} 使用 `bundler`、`mix` 和 `pip` 包管理器来更新私人注册表中的依赖项，您可以选择允许外部代码执行。 更多信息请参阅 [`insecure-external-code-execution`](#insecure-external-code-execution)。
 
-{% raw %}
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
 # when updating dependency versions for this ecosystem
 
+{% raw %}
 version: 2
 registries:
   maven-github:
@@ -493,11 +493,11 @@ updates:
   - package-ecosystem: "gitsubmodule"
     directory: "/"
     registries:
-    - maven-github
+      - maven-github
     schedule:
       interval: "monthly"
-```
 {% endraw %}
+```
 
 #### `reviewers`
 
@@ -716,7 +716,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/docker-registry/dockerhub"
     registries:
-    - dockerhub # Allow version updates for dependencies in this registry
+      - dockerhub # Allow version updates for dependencies in this registry
     schedule:
       interval: "monthly"
 ```
@@ -730,6 +730,7 @@ updates:
 | `url`                                                                                              | 用于访问此注册表中的依赖项的 URL。 协议是可选的。 如果未指定，则假定是 `https:///`。 {% data variables.product.prodname_dependabot %} 根据需要添加或忽略尾随斜线。                                                              |
 | `用户名`                                                                                              | {% data variables.product.prodname_dependabot %} 用于访问注册表的用户名。                                                                                                                    |
 | `密码`                                                                                               | 引用包含指定用户密码的 {% data variables.product.prodname_dependabot %} 机密。 更多信息请参阅“[管理 Dependabot 的加密密码](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)”。   |
+| `键`                                                                                                | 引用包含此注册表访问密钥的 {% data variables.product.prodname_dependabot %} 机密。 更多信息请参阅“[管理 Dependabot 的加密密码](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)”。 |
 | `令牌`                                                                                               | 引用包含此注册表访问令牌的 {% data variables.product.prodname_dependabot %} 机密。 更多信息请参阅“[管理 Dependabot 的加密密码](/github/administering-a-repository/managing-encrypted-secrets-for-dependabot)”。 |
 | `replaces-base`                                                                                    | 对于具有 `type: python-index` 的注册表，如果布尔值是 `true`，pip 将使用指定的 URL 而不是 Python Package Index 的基础 URL（默认 `https://pypi.org/simple`）来解析依赖项。                                                |
 
@@ -766,6 +767,19 @@ registries:
 ```
 {% endraw %}
 
+`docker-registration` 类型也可以用来使用静态 AWS 凭据从 Amazon ECR 拉取。
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
 #### `git`
 
 `git` 类型支持用户名和密码。
@@ -781,6 +795,20 @@ registries:
 ```
 {% endraw %}
 
+#### `hex-organization`
+
+`hex-organization` 类型支持组织和密钥。
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
 #### `maven-repository`
 
 `maven-reposite` 类型支持用户名和密码或令牌。
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
index 2146911db7..7837c86670 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md
@@ -49,7 +49,7 @@ topics:
 
 您可以对单个仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}（见下文）。
 
-您也可以为用户帐户或组织拥有的所有仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}。 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)."
+您也可以为用户帐户或组织拥有的所有仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}。 更多信息请参阅“[管理用户帐户的安全和分析设置](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)”或“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
 
 {% data variables.product.prodname_dependabot_security_updates %} 需要特定的仓库设置。 更多信息请参阅“[支持的仓库](#supported-repositories)”。
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
index 182e15babb..1695805068 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md
@@ -3,12 +3,12 @@ title: Configuring notifications for vulnerable dependencies
 shortTitle: Configuring notifications
 intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
 redirect_from:
-- /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
+  - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
 versions:
   free-pro-team: '*'
   enterprise-server: '>=3.0'
 topics:
-  - security
+  - Security
 ---
 
 ### About notifications for vulnerable dependencies
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
index 50e00a976d..5c0e6b7205 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md
@@ -18,7 +18,7 @@ topics:
 
 {% data reusables.dependabot.initial-updates %} 更多信息请参阅“[自定义依赖项更新](/github/administering-a-repository/customizing-dependency-updates)。”
 
-{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 更多信息请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)”。
+{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
 
 ### 启用 {% data variables.product.prodname_dependabot_version_updates %}
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
index fe3d39dc85..05cb5f50d7 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md
@@ -15,6 +15,8 @@ topics:
   - Repositories
 ---
 
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
 ### 查看依赖关系图
 
 {% data reusables.repositories.enable-security-alerts %}
@@ -50,19 +52,6 @@ topics:
 
 {% endif %}
 
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-在仓库的清单或锁定文件中指定的任何直接或间接依赖项按生态系统分组列出。 如果在仓库中检测到漏洞，这些漏洞将显示在视图顶部，供有权访问安全警报的用户查看。
-
-![依赖关系图](/assets/images/help/graphs/dependencies_graph_server.png)
-
-{% note %}
-
-**注：**{% data variables.product.prodname_ghe_server %} 不会填充 **Dependents（依赖项）**视图。
-
-{% endnote %}
-
-{% endif %}
-
 {% if currentVersion == "free-pro-team@latest" %}
 #### 依赖项视图
 
@@ -74,7 +63,7 @@ topics:
 
 仓库管理员可以启用或禁用私有仓库的依赖关系图。
 
-您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 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)."
+您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 更多信息请参阅“[管理用户帐户的安全和分析设置](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)”或“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -113,8 +102,8 @@ topics:
 
 ### 延伸阅读
 
-- "[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
+- “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”
+- "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% if currentVersion == "free-pro-team@latest" %}
 - "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
 - "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/github/understanding-how-github-uses-and-protects-your-data)"
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/index.md b/translations/zh-CN/content/code-security/supply-chain-security/index.md
index f6352f57fe..fcc26bbccb 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/index.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/index.md
@@ -20,6 +20,7 @@ topics:
     {% link_in_list /exploring-the-dependencies-of-a-repository %}
 {% topic_link_in_list /keeping-your-dependencies-updated-automatically %}
     {% link_in_list /about-dependabot-version-updates %}
+    {% link_in_list /upgrading-from-dependabotcom-to-github-native-dependabot %}
     {% link_in_list /enabling-and-disabling-version-updates %}
     {% link_in_list /listing-dependencies-configured-for-version-updates %}
     {% link_in_list /managing-pull-requests-for-dependency-updates %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
index ed18d5512e..2f5687dcbc 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -17,18 +17,18 @@ topics:
 
 {% data variables.product.prodname_dotcom %} 生成和显示依赖项数据不同于其他工具。 因此，如果您过去使用其他工具来识别依赖项，则几乎可以肯定您会看到不同的结果。 考虑以下事项：
 
-*   {% data variables.product.prodname_advisory_database %} 是 {% data variables.product.prodname_dotcom %} 用来识别漏洞依赖项的数据源之一。 它是一款免费的、具有整理功能的数据库，用于检测 {% data variables.product.prodname_dotcom %} 上常见软件包生态系统的漏洞信息。 它包括从 {% data variables.product.prodname_security_advisories %} 直接报告给 {% data variables.product.prodname_dotcom %} 的数据，以及官方馈送和社区来源。 这些数据由 {% data variables.product.prodname_dotcom %} 审查和整理，以确保不会与开发社区分享虚假或不可行的信息。 更多信息请参阅“[浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)”和“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
+*   {% data variables.product.prodname_advisory_database %} 是 {% data variables.product.prodname_dotcom %} 用来识别漏洞依赖项的数据源之一。 它是一款免费的、具有整理功能的数据库，用于检测 {% data variables.product.prodname_dotcom %} 上常见软件包生态系统的漏洞信息。 它包括从 {% data variables.product.prodname_security_advisories %} 直接报告给 {% data variables.product.prodname_dotcom %} 的数据，以及官方馈送和社区来源。 这些数据由 {% data variables.product.prodname_dotcom %} 审查和整理，以确保不会与开发社区分享虚假或不可行的信息。 {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   依赖项图解析用户仓库中所有已知的包清单文件。 例如，对于 npm，它将解析 _package-lock.json_ 文件。 它构造所有仓库依赖项和公共依赖项的图表。 当启用依赖关系图时，当任何人推送到默认分支时，都会发生这种情况，其中包括对支持的清单格式进行更改的提交。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
 *   {% data variables.product.prodname_dependabot %} 扫描对包含清单文件的默认分支的任何推送。 添加新的漏洞记录时，它会扫描所有现有仓库，并为每个存在漏洞的仓库生成警报。 {% data variables.product.prodname_dependabot_alerts %} 在仓库级别汇总，而不是针对每个漏洞创建一个警报。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
-*   {% data variables.product.prodname_dependabot_security_updates %} 在您收到关于仓库中漏洞依赖项的警报时触发。 在可能的情况下，{% data variables.product.prodname_dependabot %} 会在您的仓库中创建拉取请求，以将易受攻击的依赖项升级到避免漏洞所需的最低安全版本。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”和“[排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)”。
+*   {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} 在您收到关于仓库中漏洞依赖项的警报时触发。 在可能的情况下，{% data variables.product.prodname_dependabot %} 会在您的仓库中创建拉取请求，以将易受攻击的依赖项升级到避免漏洞所需的最低安全版本。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”和“[排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)”。
 
-    {% data variables.product.prodname_dependabot %} 不会按计划扫描仓库中的漏洞依赖项，而是在发生某些变更时扫描。 例如，当新的依赖项被添加到 {% data variables.product.prodname_dotcom %} 时（对于每次推送都会进行此项检查），或者当新的漏洞被发现并添加到通告数据库时，就会触发扫描。
+    {% endif %}{% data variables.product.prodname_dependabot %} 不会按计划扫描仓库中的漏洞依赖项，而是在发生某些变更时扫描。 例如，新增依赖项（{% data variables.product.prodname_dotcom %} 在每次推送时都会进行此项检查）时，或者当新的漏洞添加到通告数据库 {% if currentVersion ver_gt "enterprise-server@2.22" %} 以及同步到 {% data variables.product.prodname_ghe_server %}{% endif %}时，就会触发扫描。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)”。
 
 ### 为什么我没有收到某些生态系统的漏洞警报？
 
-{% data variables.product.prodname_dotcom %} 对漏洞警报的支持限于一组可提供高质量、可操作数据的生态系统。 {% data variables.product.prodname_advisory_database %} 中经整理的漏洞、依赖关系图、{% data variables.product.prodname_dependabot_alerts %} 和 {% data variables.product.prodname_dependabot %} 安全更新等功能适用于多个生态系统，包括 Java’s Maven、JavaScript’s npm 和 Yarn、.NET’s NuGet、Python’s pip、Ruby's RubyGems 以及 PHP’s Composer。 我们将在今后继续增加对更多生态系统的支持。 有关我们支持的包生态系统的概述，请参阅“[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。
+{% data variables.product.prodname_dotcom %} 对漏洞警报的支持限于一组可提供高质量、可操作数据的生态系统。 {% data variables.product.prodname_advisory_database %} 中经整理的漏洞、依赖关系图、{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot %}安全更新{% endif %} 和 {% data variables.product.prodname_dependabot %} 警报提供用于多个生态系统，包括 Java’s Maven、JavaScript’s npm 和 Yarn、.NET’s NuGet、Python’s pip、Ruby's RubyGems 以及 PHP’s Composer。 我们将在今后继续增加对更多生态系统的支持。 有关我们支持的包生态系统的概述，请参阅“[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。
 
-值得注意的是，[{% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)可能存在于其他生态系统中。 安全通告中的信息由特定仓库的维护员提供。 此数据的整理方式与支持的生态系统整理信息的方式不同。
+值得注意的是，可能存在其他生态系统的 {% data variables.product.prodname_dotcom %} 安全通告。 安全通告中的信息由特定仓库的维护员提供。 此数据的整理方式与支持的生态系统整理信息的方式不同。 {% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。{% endif %}
 
 **检查**：未捕获的漏洞是否适用于不受支持的生态系统？
 
@@ -36,9 +36,9 @@ topics:
 
 依赖项图包含在环境中明确声明的依赖项的信息。 也就是说，在清单或锁定文件中指定的依赖项。 依赖项图通常还包括过渡依赖项，即使它们没有在锁定文件中指定，也可以通过查看清单文件中的依赖项来实现。
 
-{% data variables.product.prodname_dependabot_alerts %} 提醒您应更新的依赖项，包括可从清单或锁定文件确定版本的过渡依赖项。 {% data variables.product.prodname_dependabot %} 安全更新仅在可直接“修复”依赖项的情况下建议更改，即，在以下情况下：
+{% data variables.product.prodname_dependabot_alerts %} 提醒您应更新的依赖项，包括可从清单或锁定文件确定版本的过渡依赖项。 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dependabot_security_updates %} 仅在 {% data variables.product.prodname_dependabot %} 可直接“修复”依赖项时才建议更改，即以下情况：
 * 在清单或锁定文件中明确声明的直接依赖项
-* 在锁定文件中声明的过渡依赖项
+* 在锁定文件中声明的过渡依赖项{% endif %}
 
 依赖项图不包括“宽松”依赖项。 “宽松”依赖项是指从另一个来源复制并直接或在存档文件（例如 ZIP 或 JAR 文件）中检入仓库的单个文件，而不是在包管理器的清单或锁定文件中引用的文件。
 
@@ -84,6 +84,7 @@ topics:
 
 由于 {% data variables.product.prodname_dependabot %} 使用 {% data variables.product.prodname_advisory_database %} 中的精选数据，因此警报量可能较少，但是您收到的警报将是准确和相关的。
 
+{% if currentVersion == "free-pro-team@latest" %}
 ### 是否每个依赖项漏洞都会生成单独的警报？
 
 当一个依赖项有多个漏洞时，只会为该依赖项生成一个汇总警报，而不是针对每个漏洞生成一个警报。
@@ -97,10 +98,11 @@ topics:
 ![{% data variables.product.prodname_dependabot %} 警报的多个漏洞](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
 
 **检查**: 如果您所看到的总数有出入，请检查您是否没有将警报数量与漏洞数量进行比较。
+{% endif %}
 
 ### 延伸阅读
 
 - “[关于有易受攻击依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”
 - "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- [排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"|{% if currentVersion == "free-pro-team@latest" %}
+- [排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/zh-CN/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
new file mode 100644
index 0000000000..7c186aac17
--- /dev/null
+++ b/translations/zh-CN/content/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot.md
@@ -0,0 +1,47 @@
+---
+title: Upgrading from Dependabot.com to GitHub-native Dependabot
+intro: You can upgrade to GitHub-native Dependabot by merging a pull request that will allow your dependencies to continue being updated.
+versions:
+  free-pro-team: '*'
+topics:
+  - Repositories
+---
+
+{% warning %}
+
+Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot before then.
+
+After that date, any open pull requests from Dependabot Preview will remain open, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations.
+
+{% endwarning %}
+
+### About upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Dependabot Preview has been built directly into {% data variables.product.prodname_dotcom %}, so you can use {% data variables.product.prodname_dependabot %} alongside all the other functionality in {% data variables.product.prodname_dotcom %} without having to install and use a separate application. By migrating to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, we can also focus on bringing lots of exciting new features to {% data variables.product.prodname_dependabot %}, including more [ecosystem updates](https://github.com/github/roadmap/issues/150), [improved notifications](https://github.com/github/roadmap/issues/133), and {% data variables.product.prodname_dependabot %} support for [{% data variables.product.prodname_ghe_server %}](https://github.com/github/roadmap/issues/86) and [{% data variables.product.prodname_ghe_managed %}](https://github.com/github/roadmap/issues/135).
+
+### Differences between Dependabot Preview and {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+While most of the Dependabot Preview features exist in {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, a few remain unavailable:
+- **Live updates:** We hope to bring these back in the future. For now, you can run {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} daily to catch new packages within one day of release.
+- **PHP environment variable registries:** For now, you can use {% data variables.product.prodname_actions %} to fetch dependencies from these registries.
+- **Auto-merge:** We always recommend verifying your dependencies before merging them; therefore, auto-merge will not be supported for the foreseeable future. For those of you who have vetted your dependencies, or are only using internal dependencies, we recommend adding third-party auto-merge apps, or setting up GitHub Actions to merge.
+
+In {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, you can configure all version updates using the configuration file. This file is similar to the Dependabot Preview configuration file with a few changes and improvements that will be automatically included in your upgrade pull request. For more information about the upgrade pull request, see "[Upgrading to GitHub-native Dependabot](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)".
+
+To see update logs for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} that were previously on the Dependabot.com dashboard:
+
+  1. Navigate to your repository’s **Insights** page.
+  2. Click **Dependency graph** to the left.
+  3. Click **{% data variables.product.prodname_dependabot %}**.
+
+For more information about version updates with {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}, see "[About Dependabot version updates](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+### Upgrading to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}
+
+Upgrading from Dependabot Preview to {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %} requires you to merge the *Upgrade to GitHub-native Dependabot* pull request in your repository. This pull request includes the updated configuration file needed for {% data variables.product.prodname_dotcom %}-native {% data variables.product.prodname_dependabot %}.
+
+If you are using private repositories, you will have to grant Dependabot access to these repositories in your organization's security and analysis settings. For more information, see "[Allowing Dependabot to access private dependencies](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Previously, Dependabot had access to all repositories within an organization, but we implemented this change because it is much safer to use the principle of least privilege for Dependabot.
+
+If you are using private registries, you will have to add your existing Dependabot Preview secrets to your repository's or organization's "Dependabot secrets". For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot)".
+
+If you have any questions or need help migrating, you can view or open issues in the [dependabot/dependabot-core](https://github.com/dependabot/dependabot-core/issues/new?assignees=%40dependabot%2Fpreview-migration-reviewers&labels=E%3A+preview-migration&template=migration-issue.md&title=) repository.
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index c536fc384b..bc7877dc85 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -13,8 +13,9 @@ topics:
   - Security
 ---
 
-仓库的 {% data variables.product.prodname_dependabot %} 警报选项卡列出所有打开和关闭的 {% data variables.product.prodname_dependabot_alerts %} 以及对应的 {% data variables.product.prodname_dependabot_security_updates %}。 您可以使用下拉菜单对警报列表进行排序，并且可以单击特定警报以获取更多详细信息。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
+仓库的 {% data variables.product.prodname_dependabot %} 警报选项卡列出所有打开和关闭的 {% data variables.product.prodname_dependabot_alerts %}{% if currentVersion == "free-pro-team@latest" %} 以及对应的 {% data variables.product.prodname_dependabot_security_updates %}{% endif %}。 您可以使用下拉菜单对警报列表进行排序，并且可以单击特定警报以获取更多详细信息。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
 
+{% if currentVersion == "free-pro-team@latest" %}
 您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。
 
 {% data reusables.repositories.dependency-review %}
@@ -22,9 +23,11 @@ topics:
 ### 关于仓库中有漏洞的依赖项的更新
 
 {% 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 %} 会创建拉取请求来修复它。 拉取请求会将依赖项升级到避免漏洞所需的最低安全版本。
+{% endif %}
 
 ### 查看和更新有漏洞的依赖项
 
+{% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-dependabot-alerts %}
@@ -34,10 +37,27 @@ topics:
 1. 当您准备好更新依赖项并解决漏洞时，合并拉取请求。 {% data variables.product.prodname_dependabot %} 提出的每个拉取请求都包含可用于控制 {% data variables.product.prodname_dependabot %} 的命令的相关信息。 更多信息请参阅“[管理依赖项更新的拉取请求](/github/administering-a-repository/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 currentVersion ver_gt "enterprise-server@3.0" %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. 单击您想要查看的警报。 ![在警报列表中选择的警报](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. 查看漏洞的详细信息，并确定您是否需要更新依赖项。
+1. 当您合并拉取请求以将清单或锁定文件更新为依赖项的安全版本时，这将解决警报。 或者，如果您决定不更新依赖项，请单击 **Dismiss（忽略）**下拉菜单，并选择忽略警报的原因。 ![选择通过 "Dismiss（忽略）"下拉菜单忽略警报的原因](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+1. 单击有漏洞依赖项的版本号以显示详细信息。 ![关于有漏洞依赖项的详细信息](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. 查看漏洞的详细信息，并确定您是否需要更新依赖项。 当您合并拉取请求以将清单或锁定文件更新为依赖项的安全版本时，这将解决警报。
+1. **Dependencies（依赖项）**选项卡顶部的横幅将会显示，直到解决所有漏洞依赖项或者您忽略该横幅。 单击横幅右上角的 **Dismiss（忽略）**并选择忽略警报的原因。 ![忽略安全横幅](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
+{% endif %}
+
 ### 延伸阅读
 
-- “[关于有易受攻击依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”
-- "[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"
+- "[关于有漏洞依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" {% if currentVersion == "free-pro-team@latest" %}
+- "[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)"{% endif %}
 - "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[漏洞依赖项检测疑难解答](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
-- [排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"
+- "[漏洞依赖项检测疑难解答](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% if currentVersion == "free-pro-team@latest" %}
+- [排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/zh-CN/content/codespaces/about-codespaces.md b/translations/zh-CN/content/codespaces/about-codespaces.md
new file mode 100644
index 0000000000..80a9cd2e87
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/about-codespaces.md
@@ -0,0 +1,67 @@
+---
+title: 关于 Codespaces
+intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 关于 {% data variables.product.prodname_codespaces %}
+
+{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+![开放的代码空间](/assets/images/help/codespaces/codespace-overview.png)
+
+A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings.
+
+Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development.
+
+### A consistent environment
+
+You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)”。
+
+For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials.
+
+While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}.
+
+### Fast and personal onboarding
+
+With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**.
+
+![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature.
+
+Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+
+Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs.
+
+### A secure environment
+
+{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. 开发者可以随时随地任何机器（包括平板电脑或 Chromebooks）上参与项目开发，无需维护知识产权的本地副本。 Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`.
+
+Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)".
+
+### 关于 {% data variables.product.prodname_codespaces %} 的计费
+
+{% data reusables.codespaces.about-billing-for-codespaces %} 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %} 的计费](/github/developing-online-with-codespaces/about-billing-for-codespaces)”。
+
+### 加入公测
+
+将邀请有限数量的人加入公测。 要加入等待列表，请参阅[注册代码空间测试版](https://github.com/features/codespaces/signup)。
+
+### 就 {% data variables.product.prodname_codespaces %} 联系我们
+
+如果在使用 {% data variables.product.prodname_codespaces %} 时遇到问题，请参阅“[代码空间故障排除](/github/developing-online-with-codespaces/troubleshooting-your-codespace)”。
+
+如果您仍需帮助或对 {% data variables.product.prodname_codespaces %} 有反馈，请使用 [Codespaces 反馈](https://github.com/github/feedback/discussions/categories/codespaces-feedback)。
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
new file mode 100644
index 0000000000..ca546890a2
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md
@@ -0,0 +1,18 @@
+---
+title: 关于代码空间的计费
+intro: '当 {% data variables.product.prodname_codespaces %} 公开发布时，将按存储和计算使用情况计费。'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.about-billing-for-codespaces %}
+
+Updates on the billing model for Codespaces will be shared in an upcoming announcement.
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..b8405db9ab
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,29 @@
+---
+title: Allowing your codespace to access a private image registry
+intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+注册表是存储和管理私有容器映像（如 Azure 容器注册表或 DockerHub）的安全空间。 You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry.
+
+When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)."
+
+For example, if you had a private image registry in Azure, you could create the following secrets:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
+```
+![映像注册表密钥示例](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/index.md b/translations/zh-CN/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..ec9ce53e5a
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,14 @@
+---
+title: 参考
+intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /about-billing-for-codespaces %}
+
+{% link_with_intro /troubleshooting-your-codespace %}
+
+{% link_with_intro /allowing-your-codespace-to-access-a-private-image-registry %}
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
new file mode 100644
index 0000000000..189b7e6869
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md
@@ -0,0 +1,68 @@
+---
+title: 代码空间疑难解答
+intro: Use this guide to help you troubleshoot common issues with your codespace.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+versions:
+  free-pro-team: '*'
+type: reference
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### Known Limitations
+
+{% data reusables.codespaces.beta-functionality-limited %}
+
+{% data reusables.codespaces.unsupported-repos %}
+
+### {% data variables.product.prodname_vscode %} troubleshooting
+
+Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.
+
+
+### Configuration troubleshooting
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+由于容器错误，这个代码空间正在恢复模式中运行。
+```
+
+Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)”。
+
+### dotfiles troubleshooting
+
+- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles.
+- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned.
+  - If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
+  - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
+- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**.
+
+
+### Browser troubleshooting
+
+如果在使用非基于 Chromium 的浏览器时遇到问题，请尝试切换到基于 Chromium 的浏览器，或在 `microsoft/vscode` 仓库中搜索标有您的浏览器名称（如 [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) 或 [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari)）的议题，检查浏览器的已知问题。
+
+如果您在使用基于 Chromium 的浏览器时遇到问题，您可以在e [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) 仓库中检查是否遇到 {% data variables.product.prodname_vscode %} 的另一个已知问题。
+
+### Container storage troubleshooting
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.
+
+- Remove packages that are no longer by using `sudo apt autoremove`
+- Clean the apt cache by using `sudo apt clean`
+- Delete unneeded files like build artifacts and logs (these are very project-dependent)
+- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10`
+
+More destructive options:
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes)
+- Remove untracked files from working tree: `git clean -i`
+
+### 联系我们
+
+如果仍需帮助，请联系我们。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)”。
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md
new file mode 100644
index 0000000000..eef3dd5de1
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -0,0 +1,61 @@
+---
+title: 创建代码空间
+intro: 您可以为仓库中的分支创建代码空间以便在线开发。
+permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/creating-a-codespace
+  - /github/developing-online-with-codespaces/creating-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 关于代码空间的创建
+
+You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %}
+
+Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)."
+
+
+When you create a codespace, a number of steps happen to enable full access to your development environment.
+
+- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches.
+- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created.
+- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository.
+- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)”。
+- Your Docker container, `docker-compose`, or other initialization is run.
+- At this point, the codespace is marked as available and you can connect.
+- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up.
+  - The codespace shares ports added in the `devcontainer.json` file.
+  - The codespace runs anything specified in `postCreateCommand`.
+  - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)."
+  - Finally, the codespace does a full clone of the repo so you have full access to it.
+
+
+{% data reusables.codespaces.use-visual-studio-features %}
+
+{% data reusables.codespaces.you-can-see-all-your-codespaces %}
+
+### 创建代码空间
+
+{% data reusables.repositories.navigate-to-repo %}
+2. 在仓库名称下，使用“Branch（分支）”下拉菜单选择您要为其创建代码的分支。
+
+  ![分支下拉菜单](/assets/images/help/codespaces/branch-drop-down.png)
+
+3. 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。
+
+  ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
+
+
+   
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..aa172ad5fe
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,29 @@
+---
+title: 删除代码空间
+intro: 您可以删除不再需要的代码空间。
+permissions: Anyone can delete a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% data reusables.codespaces.concurrent-codespace-limit %}
+
+1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png)
+
+  Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces).
+
+2. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete** ![删除按钮](/assets/images/help/codespaces/delete-codespace.png)
+
+### 在 {% data variables.product.prodname_vscode %} 中删除代码空间
+
+For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)."
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..af77fca7b7
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,55 @@
+---
+title: 在代码空间中开发
+intro: '您可以在 {% data variables.product.product_name %} 上打开代码空间，然后使用 {% data variables.product.prodname_vscode %} 的功能进行开发。'
+permissions: Anyone can develop in a codespace owned by their user account.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 关于 {% data variables.product.prodname_codespaces %} 的开发
+
+{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+1. Side Bar - By default, this area shows your project files in the Explorer.
+2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them.
+3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it.
+4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal.
+5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more.
+
+For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %}
+
+{% data reusables.codespaces.use-chrome %} 更多信息请参阅“[代码空间故障排除](/github/developing-online-with-codespaces/troubleshooting-your-codespace)”。
+
+#### Personalizing your codespace
+
+{% data reusables.codespaces.about-personalization %} 更多信息请参阅“[个性化您帐户的 {% data variables.product.prodname_codespaces %}](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)”。
+
+{% data reusables.codespaces.apply-devcontainer-changes %} 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)”。
+
+#### Running your app from a codespace
+{% data reusables.codespaces.about-port-forwarding %} 更多信息请参阅“[代码空间中的转发端口](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)”。
+
+#### Committing your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### Navigating to an existing codespace
+
+1. {% data reusables.codespaces.you-can-see-all-your-codespaces %}
+2. 单击您要在其中开发的代码空间的名称。 ![代码空间的名称](/assets/images/help/codespaces/click-name-codespace.png)
+
+Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..560ee94a6a
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,61 @@
+---
+title: 代码空间中的转发端口
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 关于转发的端口
+
+通过端口转发，您可以访问在代码空间内运行的 TCP 端口。 例如，如果您在端口 4000 上运行 Web 应用程序，您可以从浏览器访问该应用程序以测试和调试它。
+
+在代码空间内运行的应用程序向控制台输出端口时，{% data variables.product.prodname_codespaces %} 将检测到 localhost URL 模式并自动转发端口。 您可以单击终端中的 URL 在浏览器中打开端口。 例如，如果应用程序向控制台输出 `http://127.0.0.1:4000` 或 `http://localhost:4000`，则日志会自动将输出转换为端口 4000 的可单击 URL。
+
+![自动端口转发](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+您还可以手动转发端口、标记转发的端口、公开共享转发的端口以及将转发的端口添加到代码空间配置中。
+
+### 转发端口
+
+您可以手动转发未自动转发的端口。
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. 在端口列表下，单击 **Add port（添加端口）**。 ![添加端口按钮](/assets/images/help/codespaces/add-port-button.png)
+1. 键入端口编号或地址，然后按 Enter。 ![输入端口按钮的文本框](/assets/images/help/codespaces/port-number-text-box.png)
+
+### 标记端口
+
+您可以标记端口，使端口更容易在列表中识别。
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. 悬停在要标记的端口上，然后单击标签图标。 ![端口的标签图标](/assets/images/help/codespaces/label-icon.png)
+{% data reusables.codespaces.type-port-label %}
+
+### 共享端口
+
+如果您想与他人共享转发的端口，您可以公开该端口。 当您公开端口后，任何拥有端口 URL 的人都可以查看正在运行的应用程序，而无需进行身份验证。
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. 右键单击要共享的端口，然后单击 **Make Public（公开）**。 ![右键菜单中公开端口的选项](/assets/images/help/codespaces/make-public-option.png)
+1. 在端口的本地地址右侧，单击复制图标。 ![端口 URL 的复制图标](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. 将复制的 URL 发送给您想要与其共享端口的人。
+
+### 将端口添加到代码空间配置
+
+您可以将转发的端口添加到仓库的 {% data variables.product.prodname_codespaces %} 配置中，因此该端口将自动为创建自仓库的所有代码空间转发。 更新配置后，必须重建任何以前创建的代码空间以应用更改。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)”。
+
+您可以使用 `forwardPorts` 属性在 `.devcontainer.json` 文件中手动配置转发的端口，也可以使用代码空间中的“端口”面板。
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. 右键单击要添加到代码空间配置的端口，然后单击 **Set Label and Update devcontainer.json（设置标签和更新 devcontainer.json）**。 ![右键菜单中设置标签并将端口添加到 devcontainer.json 的选项](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png)
+{% data reusables.codespaces.type-port-label %}
+
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md
new file mode 100644
index 0000000000..3cdc49441e
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,22 @@
+---
+title: 在代码空间中开发
+intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /creating-a-codespace %}
+
+{% link_with_intro /developing-in-a-codespace %}
+
+{% link_with_intro /using-source-control-in-your-codespace %}
+
+{% link_with_intro /deleting-a-codespace %}
+
+{% link_with_intro /forwarding-ports-in-your-codespace %}
+
+{% link_with_intro /using-codespaces-in-visual-studio-code %}
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..130bbec088
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -0,0 +1,76 @@
+---
+title: 在 Visual Studio Code 中使用代码空间
+intro: '您可以将 {% data variables.product.prodname_github_codespaces %} 扩展连接到您在 {% data variables.product.product_name %} 上的帐户，直接在 {% data variables.product.prodname_vscode %} 代码空间中开发。'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 基本要求
+
+要直接在 {% data variables.product.prodname_vscode %} 中开发代码空间，必须登录到 {% data variables.product.prodname_github_codespaces %} 扩展。 {% data variables.product.prodname_github_codespaces %} 扩展需要 {% data variables.product.prodname_vscode %} 2020 年 10 月 1 日版本 1.51 或更高版本。
+
+使用 {% data variables.product.prodname_vs %} Marketplace 安装 [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 扩展。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的[扩展 Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)。
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. 单击 **Sign in to view {% data variables.product.prodname_dotcom %}...（登录以查看 Codespaces...）**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+3. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户，请单击 **Allow（允许）**。
+4. 登录 {% data variables.product.product_name %} 以审批扩展。
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. 使用“REMOTE EXPLORER（远程资源管理器）”下拉列表，然后单击 **{% data variables.product.prodname_github_codespaces %}**。 ![{% data variables.product.prodname_codespaces %} 标头](/assets/images/help/codespaces/codespaces-header-vscode.png)
+3. 单击 **Sign in to view {% data variables.product.prodname_codespaces %}...（登录以查看 Codespaces...）**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+4. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户，请单击 **Allow（允许）**。
+5. 登录 {% data variables.product.product_name %} 以审批扩展。
+
+{% endwindows %}
+
+### 在 {% data variables.product.prodname_vscode %} 中创建代码空间
+
+将 {% data variables.product.product_name %} 帐户连接到 {% data variables.product.prodname_github_codespaces %} 扩展后，您可以在 {% data variables.product.prodname_vscode %} 或 {% data variables.product.product_name %} 上创建的代码空间中进行开发。
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. 单击 Add（添加）图标，然后单击 **Create New Codespace（创建新代码空间）**。 ![{% data variables.product.prodname_codespaces %} 中的 Create new Codespace（创建新代码空间）选项](/assets/images/help/codespaces/create-codespace-vscode.png)
+3. 键入，然后单击要在其中开发仓库的名称。 ![搜索仓库以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png)
+4. 单击要在其中开发的分支。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png)
+5. Click the machine type you want to develop in. ![新 {% data variables.product.prodname_codespaces %} 的实例类型](/assets/images/help/codespaces/choose-sku-vscode.png)
+### 在 {% data variables.product.prodname_vscode %} 中打开代码空间
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. 在“Codespaces（代码空间）”下，单击您要在其中开发的代码空间。
+3. 单击 Connect to Codespace（连接到代码空间）图标。 ![{% data variables.product.prodname_vscode %} 中的连接到代码空间图标](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+### 在 {% data variables.product.prodname_vscode %} 中更改机器类型
+
+{% data reusables.codespaces.codespaces-machine-types %}
+
+您可以随时更改代码空间的机器类型。
+
+1. 在 {% data variables.product.prodname_vscode %} 中，打开命令调色板 (`shift command P` / `shift control P`)。
+2. 搜索并选择“代码空间：更改机器类型”。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+3. 单击您要更改的代码空间。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+4. 选择您要使用的机器类型。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png)
+
+如果代码空间正在运行，则会显示一条消息，询问您现在是否要重新启动并重新连接到代码空间。 如果您想立即更改用于此代码空间的机器类型，请单击 **Yes（是）** 。 如果您单击 **No（否）**，或者代码空间当前未运行，更改将在代码空间下次重启时生效。
+
+### 在 {% data variables.product.prodname_vscode %} 中删除代码空间
+
+1. 在“Codespaces（代码空间）”下，右键点击您要删除的代码空间。
+2. 在下拉菜单中，单击 **Delete Codespace（删除代码空间）**。 ![在 {% data variables.product.prodname_dotcom %} 中删除代码空间](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..deee125cff
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,81 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About source control in {% data variables.product.prodname_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+### Creating or switching branches
+
+1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**.
+1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png)
+
+{% tip %}
+
+**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace.
+
+{% endtip %}
+
+### Pulling changes from the remote repository
+
+You can pull changes from the remote repository into your codespace at any time.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. In the drop-down menu, click **Pull**.
+
+If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+
+### Setting your codespace to automatically fetch new changes
+
+You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes.
+
+If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy.
+
+1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png)
+1. In the menu, slick **Settings**.
+1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png)
+1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png)
+1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**.
+
+### Committing your changes
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png)
+1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png)
+
+### Raising a pull request
+
+1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. 单击 **Create（创建）**。
+
+### Pushing changes to your remote repository
+
+You can push the changes you've made. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. In the drop-down menu, click **Push**.
diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
new file mode 100644
index 0000000000..06a150203f
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md
@@ -0,0 +1,216 @@
+---
+title: Getting started with your C# (.NET) project in Codespaces
+shortTitle: Getting started with your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 简介
+
+This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 基本要求
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "C# (.NET)",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": { 
+            // Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+            "VARIANT": "5.0",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*",
+            "INSTALL_AZURE_CLI": "false"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [5000, 5001],
+
+    // [Optional] To reuse of your local HTTPS dev cert:
+    //
+    // 1. Export it locally using this command:
+    //    * Windows PowerShell:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    //    * macOS/Linux terminal:
+    //        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+    // 
+    // 2. Uncomment these 'remoteEnv' lines:
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. Do one of the following depending on your scenario:
+    //    * When using GitHub Codespaces and/or Remote - Containers:
+    //      1. Start the container
+    //      2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer
+    //      3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https"
+    //
+    //    * If only using Remote - Containers with a local container, uncomment this line instead:
+    //      "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "dotnet restore",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "dotnet restore",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 后续步骤
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
new file mode 100644
index 0000000000..8cad12e361
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md
@@ -0,0 +1,188 @@
+---
+title: Getting started with your Java project in Codespaces
+shortTitle: Getting started with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 简介
+
+This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 基本要求
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // Update the VARIANT arg to pick a Java version: 11, 14
+            "VARIANT": "11",
+            // Options
+            "INSTALL_MAVEN": "true",
+            "INSTALL_GRADLE": "false",
+            "INSTALL_NODE": "false",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "java.home": "/docker-java-home",
+        "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "vscjava.vscode-java-pack"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "java -version",
+
+    // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 后续步骤
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
new file mode 100644
index 0000000000..bc13f2fe3f
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md
@@ -0,0 +1,174 @@
+---
+title: Getting started with your Node.js project in Codespaces
+shortTitle: Getting started with your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 简介
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 基本要求
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+3. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 10, 12, 14
+        "args": { "VARIANT": "14" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "yarn install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}
+```
+
+- **Name** - You can name your dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+##### Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it.
+
+  ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+  ```json{:copy}
+  "postCreateCommand": "npm install",
+  "forwardPorts": [4000],
+  ```
+
+  For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs.
+
+3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 后续步骤
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces)
+- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
new file mode 100644
index 0000000000..396d3562af
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md
@@ -0,0 +1,207 @@
+---
+title: Getting started with your Python project in Codespaces
+shortTitle: Getting started with your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+versions:
+  free-pro-team: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 简介
+
+This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template.
+
+#### 基本要求
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_codespaces %} enabled for your organization.
+
+### Step 1: Open your project in a codespace
+
+1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}.
+
+  ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed.
+
+{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+### Step 2: Add a dev container to your codespace from a template
+
+The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository.
+
+To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+
+1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+#### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+##### devcontainer.json
+
+```json
+{
+    "name": "Python 3",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "context": "..",
+        "args": { 
+            // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+            "VARIANT": "3",
+            // Options
+            "INSTALL_NODE": "true",
+            "NODE_VERSION": "lts/*"
+        }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": { 
+        "terminal.integrated.shell.linux": "/bin/bash",
+        "python.pythonPath": "/usr/local/bin/python",
+        "python.linting.enabled": true,
+        "python.linting.pylintEnabled": true,
+        "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+        "python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+        "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+        "python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+        "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+        "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+        "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+        "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+        "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "ms-python.python",
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    // "forwardPorts": [],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "vscode"
+}
+```
+
+- **Name** - You can name our dev container anything, this is just the default.
+- **Build** - The build properties.
+  - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template.
+  - **Args**
+    - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **Settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **Terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **Extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically.
+- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+##### Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+### Step 3: Modify your devcontainer.json file
+
+With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy} 
+  "extensions": [
+          "ms-python.python",
+          "cstrap.flask-snippets",
+          "streetsidesoftware.code-spell-checker",
+      ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy} 
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。
+
+  ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+  Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container.
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+### Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+
+### Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+### 后续步骤
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md
new file mode 100644
index 0000000000..013f96d508
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md
@@ -0,0 +1,17 @@
+---
+title: Getting Started with {% data variables.product.prodname_codespaces %}
+intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /getting-started-with-your-nodejs-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-dotnet-project %}
+
+{% link_with_intro /getting-started-with-your-java-project-in-codespaces %}
+
+{% link_with_intro /getting-started-with-your-python-project-in-codespaces %}
+
diff --git a/translations/zh-CN/content/codespaces/guides.md b/translations/zh-CN/content/codespaces/guides.md
new file mode 100644
index 0000000000..a8e1792d82
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/guides.md
@@ -0,0 +1,28 @@
+---
+title: Codespaces guides
+shortTitle: 指南
+intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /codespaces/quickstart
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
diff --git a/translations/zh-CN/content/codespaces/index.md b/translations/zh-CN/content/codespaces/index.md
new file mode 100644
index 0000000000..df9aee66d9
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Codespaces Documentation
+beta_product: true
+shortTitle: GitHub Codespaces
+intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.'
+introLinks:
+  quickstart: /codespaces/quickstart
+  overview: /codespaces/about-codespaces
+featuredLinks:
+  guides:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  guideCards:
+    - /codespaces/developing-in-codespaces/creating-a-codespace
+    - /codespaces/developing-in-codespaces/developing-in-a-codespace
+    - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  popular:
+    - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+    - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+    - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+    - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  popularHeading: Managing GitHub Codespaces
+product_video: https://www.youtube-nocookie.com/embed/_W9B7qc9lVc
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!-- {% link_in_list /about-codespaces %} -->
+<!-- {% link_in_list /quickstart %} -->
+<!-- {% link_in_list /getting-started-with-codespaces %} -->
+<!-- {% link_in_list /setting-up-your-codespace %} -->
+<!-- {% link_in_list /developing-in-codespaces %} -->
+<!-- {% link_in_list /managing-your-codespaces %} -->
+<!-- {% link_in_list /managing-codespaces-for-your-organization %} -->
+<!-- {% link_in_list /codespaces-reference %} -->
\ No newline at end of file
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..1034377b45
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing Codespaces for your organization
+intro: 'You can manange and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-organizations-codespaces %}
+
+{% link_with_intro /managing-user-permissions-for-your-organization %}
+
+{% link_with_intro /reviewing-your-organizations-audit-logs-for-codespaces %}
+
+
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..a6e9139e72
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Managing access and security for your organization's codespaces
+shortTitle: Managing access and security for your organization
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+Organization owners can manage which repositories a codespace can access.
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. 您应该只对您信任的仓库启用访问和安全。
+
+To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. 在“Access and security（访问和安全）”下，为组织选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问组织拥有的其他仓库。 对于您要允许其代码空间访问其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
new file mode 100644
index 0000000000..0e8cc96ebf
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Managing encrypted secrets for your repository and organization for Codespaces
+shortTitle: Managing secrets for your repository and organization
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### 密码的限制
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+密码大小限于 64 KB。
+
+### Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png)
+1. At the top of the page, click **New repository secret**.
+1. 在 **Name（名称）**输入框中键入密码的名称。
+1. 输入密码的值。
+1. 单击 **Add secret（添加密码）**。
+
+### Adding secrets for an organization
+
+在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。
+
+{% data reusables.github-actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png)
+1. At the top of the page, click **New organization secret**.
+1. 在 **Name（名称）**输入框中键入密码的名称。
+1. 输入密码的 **Value（值）**。
+1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。 ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+1. 单击 **Add secret（添加密码）**。
+
+### 审查对组织级别密码的访问权限
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.github-actions.sidebar-secret %}
+1. 密码列表包括任何已配置的权限和策略。 例如： ![密码列表](/assets/images/help/settings/actions-org-secrets-list.png)
+1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
new file mode 100644
index 0000000000..fee663a78c
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md
@@ -0,0 +1,35 @@
+---
+title: Managing user permissions for your organization
+intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Permissions
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About user permissions for {% data variables.product.prodname_codespaces %}
+
+Organization owners can control which users in your organization can create and use codespaces.
+
+To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users.
+
+By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+
+### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "User permissions", select one of the following options:
+
+   * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+
+   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
new file mode 100644
index 0000000000..1dba50d193
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing your organization's audit logs for Codespaces
+shortTitle: Reviewing your organization's audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+审核日志包含操作执行人、操作内容和执行时间等详细信息。 有关 {% data variables.product.prodname_codespaces %} 操作的信息，请参阅“[{% data variables.product.prodname_codespaces %} 类别操作](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)”。
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..5c0336d862
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,20 @@
+---
+title: Managing your codespaces
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /managing-encrypted-secrets-for-your-codespaces %}
+
+{% link_with_intro /managing-access-and-security-for-your-codespaces %}
+
+{% link_with_intro /reviewing-your-security-logs-for-codespaces %}
+
+{% link_with_intro /managing-gpg-verification-for-codespaces %}
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
new file mode 100644
index 0000000000..ed437bb31a
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md
@@ -0,0 +1,17 @@
+---
+title: Managing access and security for your codespaces
+intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. 您应该只对您信任的仓库启用访问和安全。
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. 在“Access and security（访问和安全）”下，为用户帐户选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问您拥有的其他仓库。 对于您要允许其代码空间访问您拥有的其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..688912d752
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,72 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 您可以在代码空间中存储要通过环境变量访问的敏感信息（如令牌）。
+versions:
+  free-pro-team: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+
+### 关于 {% data variables.product.prodname_codespaces %} 的加密密码
+
+您可以将要在代码空间中使用的加密密码添加到您的用户帐户。 例如，您可能想要存储和访问以下敏感信息作为加密密码。
+
+- 对云服务的个人访问令牌
+- 服务主体
+- 订阅标识符
+- [私人映像注册表的凭据](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+您可以选择哪些仓库应有权访问每个密码。 然后，您可以在为有权访问密码的仓库创建的任何代码空间中使用该密码。
+
+{% data reusables.codespaces.secrets-on-start %}
+
+#### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+#### 密码的限制
+
+You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
+
+密码大小限于 64 KB。
+
+### 添加密码
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. 在“Codespaces secrets（代码空间密码）”的右侧，单击 **New secret（新建密码）**。 !["新建密码"按钮](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. 在“Name（名称）”下，输入密码的名称。 !["名称"文本框](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. 单击 **Add secret（添加密码）**。
+
+### 编辑密码
+
+您可以更新现有密码的值，也可以更改哪些仓库可以访问密码。
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. 在“Codespaces secrets（代码空间密码）”下您要编辑的密码右侧，单击 **Update（更新）**。 !["更新" 按钮](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. 在“Value（值）”下，单击 **enter a new value（输入新值）**。 !["输入新值" 链接](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user_settings.codespaces-secret-value %}
+{% data reusables.user_settings.codespaces-secret-repository-access %}
+1. （可选）要删除密码对仓库的访问权限，请取消选择仓库。 ![删除对仓库访问权限的复选框](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. 单击 **Save changes（保存更改）**。
+
+### 删除密码
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. 在“Codespaces secrets（代码空间密码）”下您要删除的密码右侧，单击 **Delete（删除）**。 !["删除" 按钮](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. 阅读警告，然后单击 **OK（确定）**。 ![确认删除密码](/assets/images/help/settings/codespaces-secret-delete-warning.png)
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
new file mode 100644
index 0000000000..4e86415536
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md
@@ -0,0 +1,23 @@
+---
+title: 管理代码空间的 GPG 验证
+intro: '您可以允许 {% data variables.product.company_short %} 自动使用 GPG 对在代码空间中所做的提交进行签名，以便其他人可以确信更改来自受信任的源。'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+启用 GPG 验证后，{% data variables.product.company_short %} 将自动对您在 {% data variables.product.prodname_codespaces %} 中所做的提交进行签名，并且该提交在 {% data variables.product.product_name %} 上具有已验证状态。 默认情况下，GPG 验证对您创建的代码空间禁用。 您可以选择对所有仓库或特定仓库允许 GPG 验证。 仅对您信任的仓库启用 GPG 验证。 有关 {% data variables.product.product_name %} 签名提交的更多信息，请参阅“[关于提交签名验证](/github/authenticating-to-github/about-commit-signature-verification)”。
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.codespaces-tab %}
+1. 在“GPG verification（GPG 验证）”下，选择您想要的 GPG 验证设置。 ![管理 GPG 验证的单选按钮](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png)
+1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击想要启用 GPG 验证的仓库。 对您要启用 GPG 验证的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
new file mode 100644
index 0000000000..5d17d52e66
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -0,0 +1,21 @@
+---
+title: Reviewing your security logs for Codespaces
+shortTitle: Reviewing your security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About security logs for {% data variables.product.prodname_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user account, you can review the actions in the security log. 有关访问日志的信息，请参阅“[查看您的安全日志](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)”。
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+安全日志包括发生了什么操作以及何时执行的操作等详细信息。 有关 {% data variables.product.prodname_codespaces %} 操作的信息，请参阅“[{% data variables.product.prodname_codespaces %} 类别操作](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)”。
diff --git a/translations/zh-CN/content/codespaces/quickstart.md b/translations/zh-CN/content/codespaces/quickstart.md
new file mode 100644
index 0000000000..cf09bffebd
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/quickstart.md
@@ -0,0 +1,84 @@
+---
+title: Quickstart for GitHub Codespaces
+intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### 简介
+
+In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace.
+
+The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles.
+
+### Creating your codespace
+
+1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces).
+
+2. 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。
+
+  ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png)
+
+3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+
+  ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
+
+### Run the application
+
+With your project open in a codespace, you can now run the application and launch it in a browser.
+
+1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository.
+
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses.
+
+  ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+### Personalize with a theme extension
+
+Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+
+2.  In the search bar, enter `fairyfloss` and install the fairyfloss extension.
+
+  ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+3. Select the `fairyfloss` theme by selecting it from the list.
+
+  ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync).
+
+### Personalize with dotfiles
+
+If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation.
+
+This example guides you through creating a dotfiles repository for your codespaces.
+
+1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/).
+
+2. Fork the repository to your account and ensure it's public.
+
+   Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization.
+
+3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text.
+
+  ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png)
+
+### Next Steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_codespaces %}.
+  - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages
+  - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project.
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
new file mode 100644
index 0000000000..3af0009ac8
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md
@@ -0,0 +1,142 @@
+---
+title: 为项目配置 Codespaces
+intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About dev containers
+
+A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.
+
+{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image.
+
+#### devcontainer.json
+
+{% data reusables.codespaces.devcontainer-location %}
+
+You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`.
+
+For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+
+#### Dockerfile
+
+A Dockerfile also lives in the `.devcontainer` folder.
+
+You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image.
+
+```Dockerfile
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
+
+# ** [Optional] Uncomment this section to install additional packages. **
+# USER root
+#
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+#
+# USER codespace
+```
+
+You can use the `RUN` instruction to install any software and `&&` to join commands.
+
+Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Using the default configuration
+
+如果您没有在仓库中定义配置，{% data variables.product.prodname_dotcom %} 将创建一个具有基本 Linux 映像的代码空间。 The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs.
+
+Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository.
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides.
+
+
+### Using a predefined container configuration
+
+Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.
+
+1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+1. 单击要使用的定义。 ![预定义容器定义列表](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. 按照提示自定义您的定义。
+1. 单击 **OK（确定）**。 ![确定按钮](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. 要应用更改，请在屏幕右下角单击 **Rebuild now（立即重建）**。 有关重建容器的更多信息，请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。 ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/rebuild-prompt.png)
+
+
+### 创建自定义代码空间配置
+
+If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %}
+
+In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed.
+
+{% data reusables.codespaces.vscode-settings-order %}
+
+您可以在两个地方定义 {% data variables.product.prodname_vscode %} 的默认编辑器设置。
+
+* `.vscode/settings.json` 中定义的编辑器设置在代码空间中用作 _Workspace_ 范围的设置。
+* `devcontainer.json` 的 `settings` 键中定义的编辑器设置在代码空间中用作 _Remote [Codespaces]_ 范围的设置。
+
+在更新 `devcontainer.json` 文件后，您可以重建代码空间的容器来应用更改。 更多信息请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。
+
+
+<!--
+### Supported codespace configuration keys
+
+You can use configuration keys supported by {% data variables.product.prodname_codespaces %} in `devcontainer.json`.
+
+#### General settings
+
+- `name`
+- `settings`
+- `extensions`
+- `forwardPorts`
+- `postCreateCommand`
+
+#### Docker, Dockerfile, or image settings
+
+- `image`
+- `dockerFile`
+- `context`
+- `containerEnv`
+- `remoteEnv`
+- `containerUser`
+- `remoteUser`
+- `mounts`
+- `runArgs`
+- `overrideCommand`
+- `dockerComposeFile`
+
+For more information about the available settings for `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation.
+-->
+
+### 应用对配置的更改
+
+{% data reusables.codespaces.apply-devcontainer-changes %}
+
+1. {% data reusables.codespaces.rebuild-command %}
+![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/rebuild-container-command.png)
+1. {% data reusables.codespaces.recovery-mode %} 修复配置中的错误。 ![有关恢复模式的错误消息](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - 要通过查看创建日志来诊断错误，请单击 **View creation log（查看创建日志）**。
+   - 要修复日志中发现的错误，请更新您的 `devcontainer.json` 文件。
+   - 要应用更改，请重建容器。 {% data reusables.codespaces.rebuild-command %}
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md b/translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md
new file mode 100644
index 0000000000..89e7f3a776
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md
@@ -0,0 +1,14 @@
+---
+title: Setting up your codespace
+intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.'
+versions:
+  free-pro-team: '*'
+topics:
+  - Codespaces
+---
+
+{% data reusables.codespaces.release-stage %}
+
+{% link_with_intro /configuring-codespaces-for-your-project %}
+
+{% link_with_intro /personalizing-codespaces-for-your-account %}
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
new file mode 100644
index 0000000000..10c67140dd
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md
@@ -0,0 +1,71 @@
+---
+title: 个性化您账户的 Codespaces
+intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+{% data reusables.codespaces.release-stage %}
+
+### About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+
+项目维护员还可以定义默认配置，将应用到任何人创建的仓库的每个代码空间。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)”。
+
+### Settings Sync
+
+Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}.
+
+Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation.
+
+### Dotfiles
+
+Dotfiles 是类似 Unix 的系统上以 `.` 开头的文件和文件夹，用于控制系统上应用程序和 shell 的配置。 您可以在 {% data variables.product.prodname_dotcom %} 上的仓库中存储和管理 dotfiles。 有关 `dotfiles` 仓库中所含内容的建议和教程，请参阅 [GitHub 执行 dotfiles](https://dotfiles.github.io/)。
+
+如果您在 {% data variables.product.prodname_dotcom %} 上的用户帐户拥有名为 `dotfiles` 的公共仓库，{% data variables.product.prodname_dotcom %} 会自动使用这个仓库来个性化设置您的代码空间环境。 私有 `dotfiles` 仓库目前不支持。
+
+`dotfiles` 仓库可能包括 shell 别名和首选项、您想要安装的任何工具或您想要执行的任何其他代码个性化。
+
+创建新的代码空间时，{% data variables.product.prodname_dotcom %} 会将 `dotfile` 仓库克隆到代码空间环境，并查找以下文件之一来设置环境。
+
+* _install.sh_
+* _安装_
+* _bootstrap.sh_
+* _bootstrap_
+* _setup.sh_
+* _setup_
+
+如果未找到这些文件，则 `dotfiles` 中以 `.` 开头的文件或文件夹通过符号链接到代码空间的 `~` 或 `$HOME` 目录。
+
+对 `dotfile` 仓库所做的任何更改只会应用到每个新的代码空间，而不影响任何现有的代码空间。
+
+{% note %}
+
+**注：**目前，{% data variables.product.prodname_codespaces %} 不支持使用 `dotfiles` 仓库个性化 {% data variables.product.prodname_vscode %} 编辑器的_用户_设置。 您可以为项目仓库中的特定项目设置默认的 _Workspace_ 和 _Remote [Codespaces]_ 设置。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)”。
+
+{% endnote %}
+
+您还可以配置用户帐户的设置以添加加密密码、启用 GPG 验证以及允许代码空间访问其他仓库。 更多信息请参阅“[管理 {% data variables.product.prodname_codespaces %} 的加密密码](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)”、“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”以及“[管理 {% data variables.product.prodname_codespaces %} 的访问权限和设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)”。
+
+### 延伸阅读
+
+* "[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md
index ef8517b765..5adcc9532a 100644
--- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md
+++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -22,6 +22,12 @@ topics:
 
 您可以直接在 {% data variables.product.product_name %} 上编辑 wikis，也可在本地编辑 wiki 文件。 默认情况下，只有能够写入仓库的人才可更改 wikis，但您可以允许 {% data variables.product.product_location %} 上的每个人参与{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}仓库中的 wiki。 更多信息请参阅“[更改 wikis 的访问权限](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)”。
 
+{% note %}
+
+**注意：** 搜索引擎不会对维基的内容编制索引。 要通过搜索引擎对内容编制索引，您可以在公共仓库中使用 [{% data variables.product.prodname_pages %}](/pages) 。
+
+{% endnote %}
+
 ### 延伸阅读
 
 - "[添加或编辑 wiki 页面](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index 7089f04f2f..55843780f0 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -50,9 +50,9 @@ topics:
 ### 在组织设置中阻止用户
 
 1. 要阻止组织成员，请先从组织中[删除用户](/articles/removing-a-member-from-your-organization) 。
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 6. 在“Block a user（阻止用户）”下，键入要阻止的用户的用户名。 ![用户名字段](/assets/images/help/organizations/org-block-username-field.png)
 7. 如果要设置阻止的时限，请使用 Block options（阻止选项）下拉菜单，选择要阻止该用户的时间段。 ![阻止选项下拉菜单](/assets/images/help/organizations/org-block-options-menu.png)
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index c76a418a82..0600e66c94 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -28,9 +28,9 @@ topics:
 
 ### 在组织设置中取消阻止用户
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. 在“Blocked users（已阻止的用户）”下您想要取消阻止的用户旁边，单击 **Unblock（取消阻止）**。 ![取消阻止用户按钮](/assets/images/help/organizations/org-unblock-user-button.png)
 
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
index 209eafde70..a265f4db62 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -10,9 +10,9 @@ topics:
   - Community
 ---
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.block_users %}
 5. 在“Blocked users（被阻止的用户）”下，查看被阻止访问组织的用户的列表。 ![被阻止的用户的列表](/assets/images/help/settings/list-of-blocked-users-for-org.png)
 
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index bca6b7c816..f97aea9400 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -28,9 +28,9 @@ topics:
 
 ### 限制组织中的交互
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. 在组织设置侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![组织设置侧边栏中的"Moderation settings（仲裁设置）"](/assets/images/help/organizations/org-settings-moderation-settings.png)
 1. 在“Moderation settings（仲裁设置）”下，单击 **Interaction limits（交互限制）**。 ![组织设置侧边栏中的"Interaction limits（交互限制）"](/assets/images/help/organizations/org-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 9573b315cd..6ae56a41b0 100644
--- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -29,14 +29,14 @@ topics:
 
 您可以在组织{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 或用户帐户{% endif %} 中为以下社区健康文件创建默认内容：
 
-| 社区健康文件                                                                                                                                                                         | 描述                                                                                                                                                                        |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| 社区健康文件                                                                                                                                                                         | 描述                                                                                                                                                                                                                         |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
 | *CODE_OF_CONDUCT.md*                                                                                                                                                         | CODE_OF_CONDUCT 文件定义如何参与社区的标准。 更多信息请参阅“[为项目添加行为准则](/articles/adding-a-code-of-conduct-to-your-project/)”。{% endif %}
 | *CONTRIBUTING.md*                                                                                                                                                              | CONTRIBUTING 文件说明人们应如何参与您的项目。 更多信息请参阅“[设置仓库参与者指南](/articles/setting-guidelines-for-repository-contributors/)”。{% if currentVersion == "free-pro-team@latest" %}
 | *FUNDING.yml*                                                                                                                                                                  | FUNDING 文件在仓库中显示赞助者按钮，以提高开源项目资助选项的可见性。 更多信息请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”。{% endif %}
-| 议题和拉取请求模板{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 和 *config.yml*{% endif %} | 议题和拉取请求模板可自定义和标准化您希望贡献者在您的仓库中打开议题和拉取请求时加入的信息。 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates/)”。{% if currentVersion == "free-pro-team@latest" %}
-| *SECURITY.md*                                                                                                                                                                  | SECURITY 文件说明如何负责任地报告项目中的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/articles/adding-a-security-policy-to-your-repository)”。{% endif %}
-| *SUPPORT.md*                                                                                                                                                                   | SUPPORT 文件告知获取项目相关帮助的方式。 更多信息请参阅“[为项目添加支持资源](/articles/adding-support-resources-to-your-project/)”。                                                                       |
+| 议题和拉取请求模板{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 和 *config.yml*{% endif %} | 议题和拉取请求模板可自定义和标准化您希望贡献者在您的仓库中打开议题和拉取请求时加入的信息。 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates/)”。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| *SECURITY.md*                                                                                                                                                                  | A SECURITY file gives instructions for how to report a security vulnerability in your project. 更多信息请参阅“[添加安全政策到仓库](/code-security/getting-started/adding-a-security-policy-to-your-repository)”。{% endif %}
+| *SUPPORT.md*                                                                                                                                                                   | SUPPORT 文件告知获取项目相关帮助的方式。 更多信息请参阅“[为项目添加支持资源](/articles/adding-support-resources-to-your-project/)”。                                                                                                                        |
 
 您不能创建默认许可文件。 必须将许可文件添加到各个仓库中，以便在克隆、打包或下载项目时包含该文件。
 
diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
index bf28ad37d1..3d20057e24 100644
--- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
+++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -13,7 +13,8 @@ topics:
   - Community
 ---
 
-为帮助项目参与者做好工作，您可以将含有参与指南的文件添加到项目仓库的根目录 `docs` 或 `.github` 文件夹。 有人打开拉取请求或创建议题时，他们将看到指向该文件的链接。
+### About contributing guidelines
+为帮助项目参与者做好工作，您可以将含有参与指南的文件添加到项目仓库的根目录 `docs` 或 `.github` 文件夹。 有人打开拉取请求或创建议题时，他们将看到指向该文件的链接。 The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
 
 ![参与指南](/assets/images/help/pull_requests/contributing-guidelines.png)
 
@@ -39,9 +40,10 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. 决定是在仓库的根目录 `docs` 还是 `.github` 目录中存储您的参与指南。 然后，在文件名字段中，输入文件的名称和扩展名。 参与指南文件名不区分大小写，并且具有 *.md* 或 *.txt* 等扩展名。 ![新文件名](/assets/images/help/repository/new-file-name.png)
+3. 决定是在仓库的根目录 `docs` 还是 `.github` 目录中存储您的参与指南。 然后，在文件名字段中，输入文件的名称和扩展名。 Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)." ![新文件名](/assets/images/help/repository/new-file-name.png)
     - 要使您的参与指南在仓库的根目录中显示，请输入 *CONTRIBUTING*。
     - 要使您的参与指南在仓库的 `docs` 目录中显示，请输入 *docs/* 以创建新目录，然后再输入 *CONTRIBUTING*。
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 4. 在新文件中，添加参与指南。 这些可能包括：
     - 创建良好议题或拉取请求的步骤。
     - 指向外部文档、邮件列表或行为准则的链接。
diff --git a/translations/zh-CN/content/developers/apps/about-apps.md b/translations/zh-CN/content/developers/apps/about-apps.md
index f5abf93e84..b61a648095 100644
--- a/translations/zh-CN/content/developers/apps/about-apps.md
+++ b/translations/zh-CN/content/developers/apps/about-apps.md
@@ -14,7 +14,7 @@ topics:
   - GitHub Apps
 ---
 
-{% data variables.product.prodname_dotcom %} 上的应用程序允许您自动化并改进工作流程。 您可以构建应用程序来改进工作流程。{% if currentversion == "free proteam@latest" %} 您也可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中分享或销售应用程序。 要了解如何在 {% data variables.product.prodname_marketplace %} 上列出应用程序，请参阅“[GitHub Marketplace 使用入门](/marketplace/getting-started/)”。{% endif %}
+{% data variables.product.prodname_dotcom %} 上的应用程序允许您自动化并改进工作流程。 您可以构建应用程序来改进工作流程。{% if currentVersion == "free proteam@latest" %} 您也可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中分享或销售应用程序。 要了解如何在 {% data variables.product.prodname_marketplace %} 上列出应用程序，请参阅“[GitHub Marketplace 使用入门](/marketplace/getting-started/)”。{% endif %}
 
 {% data reusables.marketplace.github_apps_preferred %}，但 GitHub 支持 {% data variables.product.prodname_oauth_app %} 和 {% data variables.product.prodname_github_apps %}。 有关选择应用程序类型的信息，请参阅“[GitHub 应用程序和 OAuth 应用程序之间的差异](/developers/apps/differences-between-github-apps-and-oauth-apps)”。
 
diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md
index d2f80cdb76..72d09b94da 100644
--- a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md
@@ -179,7 +179,7 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app
 {% data reusables.pre-release-program.api-preview-warning %}
 {% endif %}
 
-    POST /app-manifests/:code/conversions
+    POST /app-manifests/{code}/conversions
 
 有关端点响应的更多信息，请参阅[从清单创建 GitHub 应用程序](/rest/reference/apps#create-a-github-app-from-a-manifest)。
 
diff --git a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md
index 6828815f1f..79b2974550 100644
--- a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md
+++ b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md
@@ -140,18 +140,16 @@ GitHub 发送的每个事件都包含一个名为 `HTTP_X_GITHUB_EVENT` 的请
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      accept: 'application/vnd.github.v3+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -159,25 +157,22 @@ end
 ``` ruby
 # Create a new check run with the status queued
 def create_check_run
-  # # At the time of writing, Octokit does not support the Checks API yet, but
-  # it does provide generic HTTP methods you can use:
-  # /rest/reference/checks#create-a-check-run
-  check_run = @installation_client.post(
-    "repos/#{@payload['repository']['full_name']}/check-runs",
-    {
-      # This header allows for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      # The name of your check run.
-      name: 'Octo RuboCop',
-      # The payload structure differs depending on whether a check run or a check suite event occurred.
-      head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha']
-    }
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-此代码使用通用的 [HTTP `POST` 方法](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method)调用“[创建检查运行](/rest/reference/checks#create-a-check-run)”端点。 此方法采用两个参数：端点的 URL 和方法的输入参数。
+此代码使用 [create_check_run 方法](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run)调用“[创建检查运行](/rest/reference/checks#create-a-check-run)”端点。
 
 要创建检查运行，只有两个输入参数是必需的：`name` 和 `head_sha`。 在本快速入门中的稍后部分，我们将使用 [Rubocop](https://rubocop.readthedocs.io/en/latest/) 来实现 CI 测试，这就是在此处使用名称 "Octo Rubocop" 的原因，但是您可以为检查运行选择任何想用的名称。
 
@@ -239,31 +234,22 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.v3+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.v3+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.v3+json'
   )
 end
 ```
@@ -275,40 +261,30 @@ def initiate_check_run
   # to 'in_progress' and run the CI process. When the CI finishes, you'll
   # update the check run status to 'completed' and add the CI results.
 
-  # Octokit doesn't yet support the Checks API, but it does provide generic
-  # HTTP methods you can use:
-  # /rest/reference/checks#update-a-check-run
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-      name: 'Octo RuboCop',
-      status: 'in_progress',
-      started_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 
   # ***** RUN A CI TEST *****
 
   # Mark the check run as complete!
-  updated_check_run = @installation_client.patch(
-    "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-    {
-      # This header is necessary for beta access to Checks API
-      accept: 'application/vnd.github.antiope-preview+json',
-      name: 'Octo RuboCop',
-      status: 'completed',
-      conclusion: 'success',
-      completed_at: Time.now.utc.iso8601
-    }
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github.antiope-preview+json'
   )
 end
 ```
 {% endif %}
 
-上述代码使用通用的 [`patch` HTTP 方法](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method)调用“[更新检查运行](/rest/reference/checks#update-a-check-run)”API 端点，以更新已创建的检查运行。
+上述代码使用 [`update_check_run` Octokit 方法](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) 调用“[更新检查运行](/rest/reference/checks#update-a-check-run)”API 端点，以更新已创建的检查运行。
 
-以下是此代码的作用。 首先，它将检查运行的状态更新为 `in_progress`，并将 `started_at` 时间设置为当前时间。 在本快速入门的[第 2 部分](#part-2-creating-the-octo-rubocop-ci-test)，您将添加代码以在 `***** RUN A CI TEST *****` 下开始真正的 CI 测试。 现在，您将该部分保留为占位符，因此后面的代码将模拟 CI 流程成功并且所有测试都通过。 最后，代码将检查运行的状态再次更新为 `completed`。
+以下是此代码的作用。 首先，它将检查运行的状态更新为 `in_progress`，并默示将 `started_at` 时间设置为当前时间。 在本快速入门的[第 2 部分](#part-2-creating-the-octo-rubocop-ci-test)，您将添加代码以在 `***** RUN A CI TEST *****` 下开始真正的 CI 测试。 现在，您将该部分保留为占位符，因此后面的代码将模拟 CI 流程成功并且所有测试都通过。 最后，代码将检查运行的状态再次更新为 `completed`。
 
 在“[更新检查运行](/rest/reference/checks#update-a-check-run)”文档中，您会注意到，当您提供状态 `completed` 时，`conclusion` 和 `completed_at` 参数是必需的。 `conclusion` 总结检查运行的结果，可以是 `success`、`failure`、`neutral`、`cancelled`、`timed_out` 或 `action_required`。 您将结论设置为 `success`，将 `completed_at` 时间设置为当前时间，并将状态设置为 `completed`。
 
@@ -612,29 +588,23 @@ text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}"
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete!
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: 'success',
-    completed_at: Time.now.utc.iso8601
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github.antiope-preview+json' # This header is necessary for beta access to Checks API
 )
 ```
 {% endif %}
@@ -644,51 +614,45 @@ updated_check_run = @installation_client.patch(
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.v3+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.v3+json'
 )
 ```
 {% else %}
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
-updated_check_run = @installation_client.patch(
-  "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}",
-  {
-    accept: 'application/vnd.github.antiope-preview+json',
-    name: 'Octo RuboCop',
-    status: 'completed',
-    conclusion: conclusion,
-    completed_at: Time.now.utc.iso8601,
-    output: {
-      title: 'Octo RuboCop',
-      summary: summary,
-      text: text,
-      annotations: annotations
-    },
-    actions: [{
-      label: 'Fix this',
-      description: 'Automatically fix all linter notices.',
-      identifier: 'fix_rubocop_notices'
-    }]
-  }
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github.antiope-preview+json'
 )
 ```
 {% endif %}
diff --git a/translations/zh-CN/content/developers/apps/installing-github-apps.md b/translations/zh-CN/content/developers/apps/installing-github-apps.md
index ff98ae8c7a..ae18a3f5cb 100644
--- a/translations/zh-CN/content/developers/apps/installing-github-apps.md
+++ b/translations/zh-CN/content/developers/apps/installing-github-apps.md
@@ -1,6 +1,6 @@
 ---
 title: 安装 GitHub 应用程序
-intro: '当您的应用程序公开时， 任何人都可以使用 {% if currentversion == "free proteam@latest" %} {% data variables.product.prodname_marketplace %} 或 {% endif %}安装 URL 在其仓库中安装该应用程序。 当您的应用程序为私有时，只有您能将该应用程序安装在您自己的仓库中。'
+intro: '当您的应用程序公开时， 任何人都可以使用 {% if currentVersion == "free proteam@latest" %} {% data variables.product.prodname_marketplace %} 或 {% endif %}安装 URL 在其仓库中安装该应用程序。 当您的应用程序为私有时，只有您能将该应用程序安装在您自己的仓库中。'
 redirect_from:
   - /apps/installing-github-apps
 versions:
diff --git a/translations/zh-CN/content/developers/apps/making-a-github-app-public-or-private.md b/translations/zh-CN/content/developers/apps/making-a-github-app-public-or-private.md
index 935c1a57c3..69cb1cec54 100644
--- a/translations/zh-CN/content/developers/apps/making-a-github-app-public-or-private.md
+++ b/translations/zh-CN/content/developers/apps/making-a-github-app-public-or-private.md
@@ -23,7 +23,7 @@ topics:
 
 ### 私有安装流程
 
-私有安装流程只允许 GitHub 应用程序的所有者安装它。 有关 GitHub 应用程序的有限信息仍将存在于公共页面，但 **Install（安装）**按钮仅对组织管理员或用户帐户（如果 GitHub 应用程序由个人帐户所有）可用。 私有或内部 GitHub 应用程序只能安装在所有者的用户或组织帐户上。
+私有安装流程只允许 GitHub 应用程序的所有者安装它。 有关 GitHub 应用程序的有限信息仍将存在于公共页面，但 **Install（安装）**按钮仅对组织管理员或用户帐户（如果 GitHub 应用程序由个人帐户所有）可用。 Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
 
 ### 更改 GitHub 应用程序的安装权限
 
@@ -34,5 +34,5 @@ topics:
 {% data reusables.user-settings.github_apps %}
 3. 选择要更改其安装权限选项的 GitHub 应用程序。 ![应用程序选择](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-5. 根据 GitHub 应用程序的安装选项，单击 **Make public（设为公共）**或 **Make internal（设为内部）**。 ![更改 GitHub 应用程序安装选项的按钮](/assets/images/github-apps/github_apps_make_public.png)
-6. 根据 GitHub 应用程序的安装选项，单击 **Yes, make this GitHub App public（是，将此 GitHub 应用程序设为公共）**或 **Yes, make this GitHub App internal（是，将此 GitHub 应用程序设为内部）**。 ![确认更改安装选项的按钮](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![更改 GitHub 应用程序安装选项的按钮](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**. ![确认更改安装选项的按钮](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md
index 8d7d05a5c5..4c5f1506b6 100644
--- a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md
@@ -30,7 +30,7 @@ topics:
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
-HTTP/1.1 200 OK
+HTTP/2 200
 X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
diff --git a/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
index 486ccf59d0..6951010df2 100644
--- a/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
+++ b/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -370,10 +370,10 @@ $ ruby template_server.rb
 ```shell
 > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
 > D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
-> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
 > D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
 > D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
-> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
 ```
 
 好消息！ 这意味着您的应用程序收到了它已安装在您的 GitHub 帐户上的通知。 如果您看到以下图标，则表明您的应用程序正在服务器上按预期运行。 🙌
diff --git a/translations/zh-CN/content/developers/apps/using-content-attachments.md b/translations/zh-CN/content/developers/apps/using-content-attachments.md
index 2b1cd8026f..0b0b7bc26f 100644
--- a/translations/zh-CN/content/developers/apps/using-content-attachments.md
+++ b/translations/zh-CN/content/developers/apps/using-content-attachments.md
@@ -130,9 +130,8 @@ curl -X "POST" "https://api.github.com/graphql" \
 2. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 订阅 `content_reference` 事件并启用 `content_references` 写入权限：
 
    ``` yml
-
     default_events:
-    - content_reference
+      - content_reference
     # The set of permissions needed by the GitHub App. The format of the object uses
     # the permission name for the key (for example, issues) and the access type for
     # the value (for example, write).
@@ -141,10 +140,10 @@ curl -X "POST" "https://api.github.com/graphql" \
       content_references: write
 
     content_references:
-    - type: domain
-      value: errors.ai
-    - type: domain
-      value: example.org
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
    ```
 
 3. 将此代码添加到 `index.js` 文件以处理 `content_reference` 事件并调用 REST API：
diff --git a/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
index 98f68954c0..d04d7a93b6 100644
--- a/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
+++ b/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md
@@ -15,15 +15,15 @@ topics:
 
 ### 请求发布者验证
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. 在左侧边栏中，单击 **Developer settings**。 ![组织设置侧边栏中的开发者设置选项](/assets/images/marketplace/developer-settings-in-org-settings.png)
 1. 在“Developer settings（开发者设置）”下，单击 **Publisher Verification（发布者验证）**。 ![组织设置侧边栏中的发布者验证选项](/assets/images/marketplace/publisher-verification-settings-option.png)
 1. 在“Publisher Verification（发布者验证）”下，填写检查列表中的信息：
    - 确保您的基本个人资料信息正确无误。 另外，确保您添加了接收 {% data variables.product.company_short %} 的更新和支持信息的最合适电子邮件地址。
    - 确保为您的组织启用双重身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”。
-   - 提交已验证的域名并确保您组织的个人资料页面上显示“已验证”徽章。 相关信息请参阅“[验证组织的域](/organizations/managing-organization-settings/verifying-your-organizations-domain)”。
+   - 提交已验证的域名并确保您组织的个人资料页面上显示“已验证”徽章。 For related information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
   ![发布者验证检查列表](/assets/images/marketplace/publisher-verification-checklist.png)
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
index 6f6328f207..715e8d2455 100644
--- a/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md
@@ -24,7 +24,7 @@ topics:
 
 #### 上架产品名称
 
-应用程序的名称将显示在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上。 名称限制为 255 个字符。
+列表的名称将显示在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上。 名称仅限于 255 个字符，可能与应用名称不同。 您的列表不能与现有 {% data variables.product.product_name %} 用户同名，除非该名称是您自己的用户或组织名称。
 
 #### 简短说明
 
diff --git a/translations/zh-CN/content/developers/overview/secret-scanning.md b/translations/zh-CN/content/developers/overview/secret-scanning.md
index fd142d0baf..40d128cba0 100644
--- a/translations/zh-CN/content/developers/overview/secret-scanning.md
+++ b/translations/zh-CN/content/developers/overview/secret-scanning.md
@@ -15,9 +15,9 @@ topics:
 
 在公共仓库中找到密码格式的匹配项时，将发送有效负载到您选择的 HTTP 端点。
 
-在配置为 {% data variables.product.prodname_secret_scanning %} 的私有仓库中找到密码格式的匹配项时，仓库管理员将收到警报，并且可以查看和管理 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_secret_scanning %} 结果。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。
+在为 {% data variables.product.prodname_secret_scanning %} 配置的私有仓库中找到密码格式的匹配项时，仓库管理员和提交者将收到警报，并且可以查看和管理 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_secret_scanning %} 结果。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。
 
-本文介绍作为服务提供者如何与 {% data variables.product.prodname_dotcom %} 合作并加入 {% data variables.product.prodname_secret_scanning %} 计划。
+本文介绍作为服务提供者如何与 {% data variables.product.prodname_dotcom %} 合作并加入 {% data variables.product.prodname_secret_scanning %} 合作伙伴计划。
 
 ### {% data variables.product.prodname_secret_scanning %} 流程
 
@@ -59,21 +59,15 @@ topics:
 ##### 发送到端点的 POST 示例
 
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 Content-Type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEQCIA6C6L8ZYvZnqgV0zwrrmRab10QmIFV396gsba/WYm9oAiAI6Q+/jNaWqkgG5YhaWshTXbRwIgqIK6Ru7LxVYDbV5Q==
 Content-Length: 0123
 
-[
-  {
-    "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a",
-    "type": "ACompany_API_token",
-    "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"
-  }
-]
+[{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123"}]
 ```
 
 消息正文是一个 JSON 数组，其中包含一个或多个具有以下内容的对象。 找到多个匹配项时，{% data variables.product.prodname_dotcom %} 可能发送一条包含多个密码匹配项的消息。 您的端点应该能够在不超时的情况下处理包含大量匹配项的请求。
@@ -88,19 +82,31 @@ Content-Length: 0123
 
 您可以从 https://api.github.com/meta/public_keys/secret_scanning 检索 {% data variables.product.prodname_dotcom %} 密码扫描公钥，并使用 `ECDSA-NIST-P256V1-SHA256` 算法验证消息。
 
-假设您收到以下消息，下面的代码段演示如何执行签名验证。 该代码还假设您已经使用生成的 PAT 设置了一个名为 `GITHUB_PRODUCTION_TOKEN` 的环境变量 (https://github.com/settings/tokens)。 该令牌不需要设置任何权限。
+{% note %}
+
+**注意**： 当您向上面的公钥端点发送请求时，可能会达到速率限制。 为了避免达到速率限制，您可以使用下面示例建议的个人访问令牌（无需范围），或使用条件请求。 更多信息请参阅“[开始使用 REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)”。
+
+{% endnote %}
+
+假设您收到以下消息，下面的代码段演示如何执行签名验证。 该代码假设您已经使用生成的 PAT 设置了一个名为 `GITHUB_PRODUCTION_TOKEN` 的环境变量 (https://github.com/settings/tokens)，以避免达到速率限制。 PAT 不需要任何范围/权限。
+
+{% note %}
+
+**注意**：签名是使用原始消息正文生成的。 因此，您也必须使用原始消息正文进行签名验证，而不是解析和串联 JSON，以避免重新排列消息或更改间距，这一点很重要。
+
+{% endnote %}
 
 **发送到验证端点的消息示例**
 ```http
-POST / HTTP/1.1
+POST / HTTP/2
 Host: HOST
 Accept: */*
 content-type: application/json
 GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a
-GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc=
 Content-Length: 0000
 
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
 **Go 中的验证示例**
@@ -123,14 +129,14 @@ import (
 )
 
 func main() {
-  payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]`
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url"}]`
 
   kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-  kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+  kSig := "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
   // Fetch the list of GitHub Public Keys
-  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil)
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
   if err != nil {
     fmt.Printf("Error preparing request: %s\n", err)
     os.Exit(1)
@@ -226,47 +232,6 @@ type GitHubSigningKeys struct {
   } `json:"public_keys"`
 }
 
-// asn1Signature is a struct for ASN.1 serializing/parsing signatures.
-type asn1Signature struct {
-  R *big.Int
-  S *big.Int
-}
-    os.Exit(7)
-  }
-
-  // Parse the Webhook Signature
-  parsedSig := asn1Signature{}
-  asnSig, err := base64.StdEncoding.DecodeString(kSig)
-  if err != nil {
-    fmt.Printf("unable to base64 decode signature: %s\n", err)
-    os.Exit(8)
-  }
-  rest, err := asn1.Unmarshal(asnSig, &parsedSig)
-  if err != nil || len(rest) != 0 {
-    fmt.Printf("Error unmarshalling asn.1 signature: %s\n", err)
-    os.Exit(9)
-  }
-
-  // Verify the SHA256 encoded payload against the signature with GitHub's Key
-  digest := sha256.Sum256([]byte(payload))
-  keyOk := ecdsa.Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S)
-
-  if keyOk {
-    fmt.Println("THE PAYLOAD IS GOOD!!")
-  } else {
-    fmt.Println("the payload is invalid :(")
-    os.Exit(10)
-  }
-}
-
-type GitHubSigningKeys struct {
-  PublicKeys []struct {
-    KeyIdentifier string `json:"key_identifier"`
-    Key           string `json:"key"`
-    IsCurrent     bool   `json:"is_current"`
-  } `json:"public_keys"`
-}
-
 // asn1Signature is a struct for ASN.1 serializing/parsing signatures.
 type asn1Signature struct {
   R *big.Int
@@ -283,16 +248,16 @@ require 'json'
 require 'base64'
 
 payload = <<-EOL
-[{"token": "some_token", "type": "some_type", "url": "some_url"}]
+[{"token":"some_token","type":"some_type","url":"some_url"}]
 EOL
 
 payload = payload
 
-signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc="
+signature = "MEUCIQDKZokqnCjrRtw0tni+2Ltvl/uiMJ1EGumEsp1BsNr32AIgQY1YXD2nlj+XNfGK4rBfkMJ1JDOQcYXxa2sY8FNkrKc="
 
 key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a"
 
-url = URI.parse('https://api.github.com/meta/public_keys/token_scanning')
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
 
 raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
 request = Net::HTTP::Get.new(url.path)
@@ -398,4 +363,3 @@ const verify_signature = async (payload, signature, keyID) => {
 **注：**对于提供误报数据的合作伙伴，我们的请求超时设置为更高（即 30 秒）。 如果您需要超过 30 秒的超时设置，请发送电子邮件至 <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>。
 
 {% endnote %}
-
diff --git a/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md b/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md
index 38d365e694..c0444423c0 100644
--- a/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md
@@ -149,7 +149,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-在 Mac OS X 上，一旦在重新引导过程中重新启动 `ssh-agent`，它将“忘记”该密钥。 但是，您可以使用此命令将 SSH 密钥导入密钥链：
+在 MacOS 上，一旦在重新引导过程中重新启动 `ssh-agent`，它将“忘记”该密钥。 但是，您可以使用此命令将 SSH 密钥导入密钥链：
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md b/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md
index 8445d481b1..fbf8c0ec29 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md
@@ -45,7 +45,7 @@ topics:
 此示例显示了使用[事件 API](/rest/reference/activity#events) 时 [WatchEvent](#watchevent) 响应的格式。
 
 ```
-HTTP/1.1 200 OK
+HTTP/2 200
 Link: <https://api.github.com/resource?page=2>; rel="next",
       <https://api.github.com/resource?page=5>; rel="last"
 ```
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md
index b24231e139..61b2fee3a2 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md
@@ -61,7 +61,7 @@ Web 挂钩事件的独特属性与您使用[事件 API](/rest/reference/activity
 #### 递送示例
 
 ```shell
-> POST /payload HTTP/1.1
+> POST /payload HTTP/2
 
 > Host: localhost:4567
 > X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
@@ -200,7 +200,9 @@ Web 挂钩事件的独特属性与您使用[事件 API](/rest/reference/activity
 
 Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如果您注册了一个子域 (`https://subdomain.example.com`)，则只有该子域的 URL 才会触发此事件。 如果您注册了一个域 (`https://example.com`)，则该域及所有子域的 URL 都会触发此事件。 请参阅“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”以创建新的内容附件。
 
-只有 {% data variables.product.prodname_github_app %} 才能接收此事件。 {% data variables.product.prodname_github_app %} 必须具有 `content_references` `write` 权限才能订阅此事件。
+#### 可用性
+
+- 具有 `content_references:write` 权限的 {% data variables.product.prodname_github_app %}
 
 #### Web 挂钩有效负载示例
 
@@ -1010,12 +1012,6 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如
 
 {% endnote %}
 
-{% tip %}
-
-**注**：表格后面的 web 挂钩有效负载示例与表中所述的 Events API 有效负载有显著差异。 其中一项差异是，web 挂钩有效负载包括 `sender` 和 `pusher` 对象。 发送者和推送者是发起 `push` 事件的同一用户，但 `sender` 对象包含更多详细信息。
-
-{% endtip %}
-
 #### 可用性
 
 - 仓库 web 挂钩
@@ -1206,7 +1202,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-您只能在 {% data variables.product.prodname_dotcom %} 上创建赞助 web 挂钩。 更多信息请参阅“[为赞助帐户中的事件配置 web 挂钩](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)”。
+您只能在 {% data variables.product.prodname_dotcom %} 上创建赞助 web 挂钩。 更多信息请参阅“[为赞助帐户中的事件配置 web 挂钩](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)”。
 
 #### 可用性
 
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 48ccf6a213..963ad7bddf 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -12,7 +12,7 @@ versions:
 
 {% data reusables.discussions.about-discussions %} 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
 
-除了开始或查看讨论之外，您还可以对讨论作者的原始评论做出响应。 您还可以通过回复其他社区成员在讨论中进行的个人评论，以及使用表情符号对评论做出反应来创建评论线程。 有关反应的更多信息，请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的对话](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)”。
+除了开始或查看讨论之外，您还可以对讨论作者的原始评论做出响应。 您还可以通过回复其他社区成员在讨论中进行的个人评论，以及使用表情符号对评论做出反应来创建评论线程。
 
 您可以阻止用户并报告破坏性内容，以便自己在 {% data variables.product.product_name %} 上保持一个安全愉快的环境。 更多信息请参阅“[保持您在 {% data variables.product.prodname_dotcom %} 上的安全](/communities/maintaining-your-safety-on-github)”。
 
diff --git a/translations/zh-CN/content/discussions/index.md b/translations/zh-CN/content/discussions/index.md
index 0474c28376..28dc37d486 100644
--- a/translations/zh-CN/content/discussions/index.md
+++ b/translations/zh-CN/content/discussions/index.md
@@ -34,24 +34,3 @@ versions:
 <!-- {% link_with_intro /discussions-guides %} -->
 <!-- {% link_with_intro /collaborating-with-your-community-using-discussions %} -->
 <!-- {% link_with_intro /managing-discussions-for-your-community %} -->
-
-<!-- Community examples -->
-{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %}
-{% if discussionsCommunityExamples %}
-<div class="my-6 pt-6">
-  <h2 class="mb-2 font-mktg h1">使用讨论的社区</h2>
-
-  <div class="d-flex flex-wrap gutter">
-    {% render discussions-community-card for discussionsCommunityExamples as example %}
-  </div>
-  {% if discussionsCommunityExamples.length > 6 %}
-    <button class="js-filter-card-show-more btn btn-outline float-right" data-js-filter-card-max="6">显示更多 {% octicon "arrow-right" %}</button>
-  {% endif %}
-  <div class="js-filter-card-no-results d-none py-4 text-center text-gray font-mktg">
-    <div class="mb-3">{% octicon "search" width="24" %}</div>
-    <h3 class="text-normal">抱歉，找不到结果 <strong class="js-filter-card-value"></strong></h3>
-    <p class="my-3 f4">似乎没有适合您的过滤条件的示例。<br>请尝试其他过滤条件或添加代码示例</p>
-    <a href="https://github.com/github/docs/blob/main/data/variables/discussions_community_examples.yml">添加您的社区 {% octicon "arrow-right" %}</a>
-  </div>
-</div>
-{% endif %}
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
index 777eff84ec..3c6eeee516 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md
@@ -17,7 +17,7 @@ redirect_from:
 
 {% data reusables.classroom.about-assignments %}
 
-您可以决定一个任务可以拥有多少个团队，以及每个团队可以拥有多少成员。 学生为作业创建的每个团队都是 {% data variables.product.product_name %} 上组织内的团队。 团队的可见性是秘密。 您在 {% data variables.product.product_name %} 上创建的团队不会出现在 {% data variables.product.prodname_classroom %} 中。 For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+您可以决定一个任务可以拥有多少个团队，以及每个团队可以拥有多少成员。 学生为作业创建的每个团队都是 {% data variables.product.product_name %} 上组织内的团队。 团队的可见性是秘密。 您在 {% data variables.product.product_name %} 上创建的团队不会出现在 {% data variables.product.prodname_classroom %} 中。 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
 
 有关创建小组作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本知识](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
 
diff --git a/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md b/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md
index e9433a48b1..afc513a275 100644
--- a/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md
+++ b/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md
@@ -47,6 +47,8 @@ topics:
 - [允许强制推送](#allow-force-pushes)
 - [允许删除](#allow-deletions)
 
+有关如何设置分支保护的更多信息，请参阅“[管理分支保护规则](/github/administering-a-repository/managing-a-branch-protection-rule)”。
+
 #### 合并前必需拉取请求审查
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
@@ -100,7 +102,15 @@ remote: error: Changes have been requested.
 
 {% note %}
 
+{% if currentVersion == "free-pro-team@latest" %}
+**注意：**
+
+* 如果您已经启用了警戒模式，这表明您的提交总是会签名，允许在需要签名提交的分支上提交 {% data variables.product.prodname_dotcom %} 识别为“部分验证”的任何提交。 有关警戒模式的更多信息，请参阅“[显示所有提交的验证状态](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)”。
+* 如果协作者将未签名的提交推送到要求提交签名的分支，则协作者需要变基提交以包含验证的签名，然后将重写的提交强制推送到分支。
+
+{% else %}
 **注：**如果协作者将未签名的提交推送到要求提交签名的分支，则协作者需要变基提交以包含验证的签名，然后将重写的提交强制推送到分支。
+{% endif %}
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md b/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md
index 044aeac9d7..2f1617e535 100644
--- a/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md
+++ b/translations/zh-CN/content/github/administering-a-repository/changing-the-default-branch.md
@@ -25,7 +25,7 @@ topics:
 {% endnote %}
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 
 您也可以重命名默认分支。 更多信息请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”。
 
diff --git a/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md b/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md
index cdfb6dfa2c..5c757233ef 100644
--- a/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md
+++ b/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md
@@ -13,7 +13,7 @@ topics:
 
 在添加图像之前，请展开仓库链接以显示关于仓库和所有者头像的基本信息。 为仓库添加图像有助于在各种社交平台上识别您的项目。
 
-{% if currentversion != "github-ae@latest" %}您可以将映像上传到私有仓库，但您的映像只能从公共仓库分享。{% endif %}
+{% if currentVersion != "github-ae@latest" %}您可以将映像上传到私有仓库，但您的映像只能从公共仓库分享。{% endif %}
 
 {% tip %}
 提示：您的图像应为大小在 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获取质量最佳的渲染，建议图像的像素保持在 640 x 320 像素。
diff --git a/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md
index 369cb70d9b..cb65c4004c 100644
--- a/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md
@@ -15,7 +15,7 @@ topics:
 
 {% data reusables.organizations.owners-and-admins-can %} 删除组织仓库。 如果已禁用 **Allow members to delete or transfer repositories for this organization（允许成员删除或转让此组织的仓库）**，仅组织所有者可删除组织仓库。 {% data reusables.organizations.new-repo-permissions-more-info %}
 
-{% if currentversion != "github-ae@latest" %}删除公共仓库不会删除该仓库的任何复刻。{% endif %}
+{% if currentVersion != "github-ae@latest" %}删除公共仓库不会删除该仓库的任何复刻。{% endif %}
 
 {% warning %}
 
diff --git a/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
index ce8d2f74a2..04f9044328 100644
--- a/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md
@@ -26,7 +26,7 @@ topics:
 
 {% note %}
 
-**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
+**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)”或{% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)”。{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)“。{% endif %}
 
 {% endnote %}
 
@@ -47,7 +47,7 @@ topics:
 
 {% note %}
 
-**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)”或{% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)”。{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)“。
 
 {% endif %}
 
@@ -82,3 +82,21 @@ topics:
 {% data reusables.repositories.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### 为您的仓库设置 `GITHUB_TOKENN` 的权限
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+默认权限也可以在组织设置中配置。 如果在组织设置中选择了更受限制的默认值，则在仓库设置中自动选择相同的选项，并禁用许可的选项。
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### 配置默认 `GITHUB_TOKENN` 权限
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions %}
+1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 ![为此仓库设置 GITHUB_TOKENN 权限](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. 单击 **Save（保存）**以应用设置。
+{% endif %}
diff --git a/translations/zh-CN/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
index b3393d7198..d6e1efd5a9 100644
--- a/translations/zh-CN/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -12,7 +12,7 @@ topics:
 
 ### 关于 FUNDING 文件
 
-可通过编辑默认分支上仓库 `.github` 文件夹中的 _FUNDING.yml_ 文件来配置赞助者按钮。 您也可以配置此按钮，以通过 {% data variables.product.prodname_sponsors %}、外部资助平台或自定义资助 URL 来包括被赞助的开发者。 有关 {% data variables.product.prodname_sponsors %} 的更多信息请参阅“[关于 GitHub 赞助者](/articles/about-github-sponsors)”。
+可通过编辑默认分支上仓库 `.github` 文件夹中的 _FUNDING.yml_ 文件来配置赞助者按钮。 您也可以配置此按钮，以通过 {% data variables.product.prodname_sponsors %}、外部资助平台或自定义资助 URL 来包括被赞助的开发者。 有关 {% data variables.product.prodname_sponsors %} 的更多信息请参阅“[关于 GitHub 赞助者](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”。
 
 您也可以每个赞助平台添加一个用户名、包名称或项目名，以及最多四个自定义 URL。 最多可在 {% data variables.product.prodname_sponsors %} 中添加四位被赞助的开发者或组织。 在新行上添加每个平台，使用以下语法：
 
@@ -76,5 +76,5 @@ custom: ["https://www.paypal.me/octocat", octocat.com]
 {% data reusables.files.propose_new_file %}
 
 ### 延伸阅读
-- "[关于开源贡献者的 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- "[关于开源贡献者的 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
 - {% data variables.product.prodname_blog %} 上的“[{% data variables.product.prodname_sponsors %} 团队常见问题](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)”
diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md
index 980b8fef2d..288b1ffdea 100644
--- a/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/managing-releases-in-a-repository.md
@@ -21,7 +21,7 @@ topics:
 
 ### 关于发行版管理
 
-{% if currentversion == "free proteam@latest" %}
+{% if currentVersion == "free proteam@latest" %}
 您也可以在 {% data variables.product.prodname_marketplace %} 中发布特定版本的操作。 更多信息请参阅“<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">在 {% data variables.product.prodname_marketplace %} 中发布操作</a>”。
 {% endif %}
 您可以选择是否
diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
index b50cfdd982..4128cfb0b2 100644
--- a/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -35,10 +35,11 @@ topics:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。
-{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果在您的 {% data variables.product.prodname_GH_advanced_security %} 许可中没有可用的席位，则对“{% data variables.product.prodname_GH_advanced_security %}”的控制会禁用。
-  !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 “
+{% data variables.product.prodname_GH_advanced_security %}”的控制被禁用（如果您的企业没有可用的 {% data variables.product.prodname_advanced_security %} 许可）。{% if currentVersion == "free-pro-team@latest" %}
+  !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% else %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   {% note %}
 **注意：**如果禁用
 
@@ -46,11 +47,11 @@ topics:
   {% endnote %}
   {% endif %}
   {% if currentVersion == "enterprise-server@3.0" %}
-  !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
+4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png)
   {% endif %}
   {% if currentVersion == "github-ae@latest" %}
 4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 在可以为您的仓库启用
-“{% data variables.product.prodname_secret_scanning %}”之前，您必须先启用 {% data variables.product.prodname_GH_advanced_security %}。
+“{% data variables.product.prodname_secret_scanning %}”之前，您可能需要先启用 {% data variables.product.prodname_GH_advanced_security %}。
    ![为您的仓库启用或禁用 {% data variables.product.prodname_GH_advanced_security %} 或 {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
index e9af49e664..32ecf26a5a 100644
--- a/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md
@@ -48,7 +48,7 @@ topics:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. 在“Manage access（管理访问权限）”下，找到要删除其访问权限的团队或人员，然后单击 {% octicon "trashcan" aria-label="The trashcan icon" %}。 ![用于删除访问权限的回收站图标](/assets/images/help/repository/manage-access-remove.png)
+4. 在“Manage access（管理访问权限）”下，找到要删除其访问权限的团队或人员，然后单击 {% octicon "trash" aria-label="The trash icon" %}。 ![用于删除访问权限的回收站图标](/assets/images/help/repository/manage-access-remove.png)
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md b/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md
index 4eb3d5fb9f..764351fe2c 100644
--- a/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md
+++ b/translations/zh-CN/content/github/administering-a-repository/renaming-a-branch.md
@@ -17,6 +17,8 @@ topics:
 
 虽然文件 URL 会自动重定向，但原始文件 URL 未被重定向。 此外，如果用户对前一个分支名称执行 `git pull`，则 {% data variables.product.prodname_dotcom %} 不会执行任何重定向。
 
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+
 ### 重命名分支
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -35,4 +37,10 @@ topics:
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
 $ git fetch origin
 $ git branch -u origin/<em>NEW-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
+$ git remote set-head origin -a
+```
+
+（可选）运行下面的命令来删除对旧分支名称的跟踪引用。
+```
+$ git remote prune origin
 ```
diff --git a/translations/zh-CN/content/github/administering-a-repository/restoring-a-deleted-repository.md b/translations/zh-CN/content/github/administering-a-repository/restoring-a-deleted-repository.md
index 831bceef76..d279695e62 100644
--- a/translations/zh-CN/content/github/administering-a-repository/restoring-a-deleted-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/restoring-a-deleted-repository.md
@@ -31,9 +31,9 @@ topics:
 
 ### 恢复组织所拥有的已删除仓库
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.deleted-repos %}
 {% data reusables.user_settings.restore-repo %}
 {% data reusables.user_settings.restore-confirmation %}
diff --git a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md
index 0b8a0a73dd..2ec433ed09 100644
--- a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md
+++ b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md
@@ -16,14 +16,14 @@ topics:
 
 ### 关于仓库可见性更改
 
-组织所有者可以限制只有组织所有者才能更改仓库可见性。 For more information, 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)”。
 
 我们建议在您更改仓库可见性之前审查以下注意事项。
 
 #### 将仓库设为私有
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 * {% data variables.product.product_name %} 将会分离公共仓库的公共复刻并将其放入新的网络中。 公共复刻无法设为私有。{% endif %}
-* 如果您将仓库的可见性从内部更改为私有， {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}任何复刻的可见性也将更改为私有。{% elsif currentVersion == "github-ae@latest" %}如果内部仓库有任何复刻，则复刻的可见性已经是私有的。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”{% if currentversion == "free proteam@latest" %}
+* 如果您将仓库的可见性从内部更改为私有， {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}任何复刻的可见性也将更改为私有。{% elsif currentVersion == "github-ae@latest" %}如果内部仓库有任何复刻，则复刻的可见性已经是私有的。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”{% if currentVersion == "free proteam@latest" %}
 * 如果对用户帐户或组织使用 {% data variables.product.prodname_free_user %}，有些功能在您将可见性更改为私有后不可用于仓库。 {% data reusables.gated-features.more-info %}{% endif %}
 * 任何已发布的 {% data variables.product.prodname_pages %} 站点将自动取消发布。{% if currentVersion == "free-pro-team@latest" %} 如果将自定义域添加到 {% data variables.product.prodname_pages %} 站点，应先删除或更新 DNS 记录后再将仓库设为私有，以避免域接管的风险。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %}{% if currentVersion == "free-pro-team@latest" %}
 * {% data variables.product.prodname_dotcom %} 不再在 {% data variables.product.prodname_archive %} 中包含该仓库。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上存档内容和数据](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)”。{% endif %}{% if currentVersion == "free-pro-team@latest" %}
diff --git a/translations/zh-CN/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
index 04c9043760..a498188c8a 100644
--- a/translations/zh-CN/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
+++ b/translations/zh-CN/content/github/administering-a-repository/viewing-deployment-activity-for-your-repository.md
@@ -24,7 +24,8 @@ topics:
 ### 查看部署仪表板
 
 {% data reusables.repositories.navigate-to-repo %}
-2. 在文件列表上方，单击 **Environments（环境）**。 ![仓库页面顶部的环境](/assets/images/help/repository/environments.png)
+2. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png){% else %}Above the list of files, click **Environments**. ![Environments on top of repository page](/assets/images/help/repository/environments-top.png){% endif %}
+
 
 ### 延伸阅读
  - "[关于拉取请求](/articles/about-pull-requests)"
diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-urls.md b/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-urls.md
new file mode 100644
index 0000000000..95049a138c
--- /dev/null
+++ b/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-urls.md
@@ -0,0 +1,98 @@
+---
+title: About anonymized URLs
+intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls/
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+为托管您的图像，{% data variables.product.product_name %} 使用 [开源项目 Camo](https://github.com/atmos/camo)。 Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. URL 以 `https:///<subdomain>.githubusercontent.com/` 开头，并且根据您如何上传映像而有不同的子域。
+
+Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
+
+Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
+
+### Camo 问题故障排除
+
+在偶尔的情况下，通过 Camo 处理的图像可能不会出现在 {% data variables.product.prodname_dotcom %} 上。 下面是可用于确定问题位置的一些步骤。
+
+{% windows %}
+
+{% tip %}
+
+Windows 用户需要使用 Git Powershell（随 [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) 一起安装）或下载 [curl for Windows](http://curl.haxx.se/download.html)。
+
+{% endtip %}
+
+{% endwindows %}
+
+#### 图像不显示
+
+If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. 使用 `curl` 请求图像标头。
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. 检查 `Content-Type` 的值。 本例中为 `image/x-png`。
+4. 根据 [Camo 支持的类型列表](https://github.com/atmos/camo/blob/master/mime-types.json)检查内容类型。
+
+如果您的内容类型不受 Camo 支持，可尝试以下几项操作：
+  * 如果您拥有托管该图像的服务器，请修改它以让其返回正确内容类型的图像。
+  * 如果使用外部服务托管图像，请联系该服务的支持。
+  * 建立对 Camo 的拉取请求以将内容类型添加到列表。
+
+#### 最近更改的图像不更新
+
+如果最近更改了图像并且它显示在浏览器中，但未显示在 {% data variables.product.prodname_dotcom %} 上，可尝试重置图像缓存。
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. 使用 `curl` 请求图像标头。
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+检查 `Cache-Control` 的值。 本例中没有 `Cache-Control`。 在这种情况下：
+  * 如果您拥有托管该图像的服务器，请修改它以让其返回图像的 `no-cache` 的 `Cache-Control`。
+  * 如果使用外部服务托管图像，请联系该服务的支持。
+
+ 如果 `Cache-Control` *设置*为 `no-cache`，请联系 {% data variables.contact.contact_support %} 或搜索 {% data variables.contact.community_support_forum %}。
+
+#### 从 Camo 的缓存中删除图像
+
+清除缓存会强制每个 {% data variables.product.prodname_dotcom %} 用户重新请求图像，因此应非常谨慎地使用此操作，仅在上述步骤无效时才使用。
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. 使用 `curl -X PURGE` 在 Camo URL 上清除图像。
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+#### 在私人网络上查看图像
+
+如果图像从私人网络或需要身份验证的服务器提供，则无法通过 {% data variables.product.prodname_dotcom %} 查看。 事实上，未登录服务器的任何用户都无法查看。
+
+要解决此问题，请将图像移至公共的服务。
+
+### 延伸阅读
+
+- {% data variables.product.prodname_blog %} 上的"[代理用户图像](https://github.com/blog/1766-proxying-user-images)"
diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md
index 27ad25e28b..53a18a5a13 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md
@@ -16,7 +16,7 @@ topics:
 
 您可以通过多种方式访问 {% data variables.product.product_name %} 中的资源：浏览器中、通过 {% data variables.product.prodname_desktop %} 或其他桌面应用程序、使用 API 或通过命令行。 每种访问 {% data variables.product.product_name %} 的方式都支持不同的身份验证模式。
 
-- {% if currentversion == "github-ae@latest" %}您的身份提供程序 (IdP){% else %}使用双重身份验证的用户名和密码{% endif %}
+- {% if currentVersion == "github-ae@latest" %}您的身份提供程序 (IdP){% else %}使用双重身份验证的用户名和密码{% endif %}
 - 个人访问令牌
 - SSH 密钥
 
diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
index fd16a10fde..07b5b292c0 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md
@@ -1,47 +1,55 @@
 ---
-title: About authentication with SAML single sign-on
-intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}'
+title: 关于使用 SAML 单点登录进行身份验证
+intro: '您可以通过使用 SAML 单点登录 (SSO) 通过身份提供程序 (IdP)验证 {% if currentVersion == "github-ae@latest" %}，来访问 {% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}使用 SAML 单点登录 (SSO) 的组织{% endif %}。{% if currentVersion == "free-pro-team@latest" %}从 {% data variables.product.product_name %} 使用 IdP 成功验证后，您必须授权要用于访问组织资源的的任何个人访问令牌、SSH 密钥或 {% data variables.product.prodname_oauth_app %}。{% endif %}'
 product: '{% data reusables.gated-features.saml-sso %}'
 redirect_from:
   - /articles/about-authentication-with-saml-single-sign-on
 versions:
   free-pro-team: '*'
   github-ae: '*'
+topics:
+  - SSO
 ---
 
+### 关于使用 SAML SSO 进行身份验证
+
 {% if currentVersion == "github-ae@latest" %}
 
-SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access.
+SAML SSO 允许企业所有者从 SAML IdP 集中控制和安全访问 {% data variables.product.product_name %}。 在浏览器中访问 {% data variables.product.product_location %} 时，{% data variables.product.product_name %} 会将用户重定向到您的 IdP 进行身份验证。 在使用 IdP 上的帐户成功进行身份验证后，IdP 会将您重定向回 {% data variables.product.product_location %}。 {% data variables.product.product_name %} 将验证 IdP 的响应，然后授予访问权限。
 
 {% data reusables.saml.you-must-periodically-authenticate %}
 
-If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. 
+如果您无法访问 {% data variables.product.product_name %}，请与本地企业所有者或 {% data variables.product.product_name %} 的管理员联系。 您可以在 {% data variables.product.product_name %} 上的任何页面底部单击 **Support（支持）**找到企业的联系信息。 {% data variables.product.company_short %} 和 {% data variables.contact.github_support %} 无法访问您的 IdP，并且无法解决身份验证问题。
 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}.
+{% data reusables.saml.dotcom-saml-explanation %} 组织所有者可以邀请您在 {% data variables.product.prodname_dotcom %} 上的用户帐户加入其使用 SAML SSO 的组织，这样您可以对该组织做出贡献，并且保留您在 {% data variables.product.prodname_dotcom %} 上的现有身份和贡献。
 
-When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources.
+在访问使用 SAML SSO 的组织中的资源时，{% data variables.product.prodname_dotcom %} 会将您重定向到组织的 SAML IdP 进行身份验证。 在 IdP 上成功验证您的帐户后，IdP 会将您重定向回到 {% data variables.product.prodname_dotcom %}，您可以在那里访问组织的资源。
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization.
+如果您最近在浏览器中使用组织的 SAML IdP 进行过身份验证，则在访问使用 SAML SSO 的 {% data variables.product.prodname_dotcom %} 组织时会自动获得授权。 如果您最近没有在浏览器中使用组织的 SAML IdP 进行身份验证，则必须在 SAML IdP 进行身份验证后才可访问组织。
 
 {% data reusables.saml.you-must-periodically-authenticate %}
 
-To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default.
+要在命令行上使用 API 或 Git 访问使用 SAML SSO 的组织中受保护的内容，需要使用授权的 HTTPS 个人访问令牌或授权的 SSH 密钥。
 
-If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+如果没有个人访问令牌或 SSH 密钥，可以创建用于命令行的个人访问令牌或生成新的 SSH 密钥。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”或“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。
 
-To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
+要对使用或实施 SAML SSO 的组织使用新的或现有的个人访问令牌或 SSH 密钥，需要授权该令牌或授权 SSH 密钥用于 SAML SSO 组织。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”或“[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。
 
-You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}.
+### 关于 {% data variables.product.prodname_oauth_apps %} 和 SAML SSO
+
+每次授权 {% data variables.product.prodname_oauth_app %} 访问使用或实施 SAML SSO 的组织时，您必须有一个活动的 SAML 会话。
+
+在企业或组织所有者为组织启用或实施 SAML SSO 后，您必须重新授权先前已授权访问组织的任何 {% data variables.product.prodname_oauth_app %}。 要查看您已授权或重新授权 {% data variables.product.prodname_oauth_app %} 的 {% data variables.product.prodname_oauth_apps %}，请访问您的 [{% data variables.product.prodname_oauth_apps %} 页面](https://github.com/settings/applications)。
 
 {% endif %}
 
-### Further reading
+### 延伸阅读
 
-{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
-{% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}- "[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
+{% if currentVersion == "github-ae@latest" %}- "[关于企业的身份和访问权限管理](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md
index cd5b8ca7c0..761064488a 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/about-commit-signature-verification.md
@@ -16,15 +16,35 @@ topics:
 
 ### 关于提交签名验证
 
-您可以本地签名提交和标记，以便其他人确认您的工作来自可信的来源。 如果提交或标记具有密码可验证的 GPG 或 S/MIME 签名，则 {% data variables.product.product_name %} 会将提交或标记标示为已验证。
+您可以在本地签署提交和标签，让其他人对您所做更改的源充满信心。 如果提交或标签具有可加密验证的 GPG 或 S/MIME 签名，GitHub 会对提交或标签标记 {% if currentVersion == "free-pro-team@latest" %}“已验证”或“部分验证”{% else %}“已验证”{% endif %}
 
 ![验证的提交](/assets/images/help/commits/verified-commit.png)
 
-如果提交或标记具有无法验证的签名，则 {% data variables.product.product_name %} 会将提交或标记标示为未验证。
+{% if currentVersion == "free-pro-team@latest" %}
+提交和标签具有以下验证状态，具体取决于您是否启用了警戒模式。 默认情况下未启用警戒模式。 有关如何启用警戒模式的更多信息，请参阅“[显示所有提交的验证状态](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)”。
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+#### 默认状态
+
+| 状态      | 描述             |
+| ------- | -------------- |
+| **已验证** | 提交已签名且签名已成功验证。 |
+| **未验证** | 提交已签名，但签名无法验证。 |
+| 无验证状态   | 提交未签名。         |
+
+#### 启用了警戒模式的状态
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% else %}
+如果提交或标签有无法验证的签名，
+{% data variables.product.product_name %} 将对提交或标签标记“未验证”。
+{% endif %}
 
 仓库管理员可对分析实施必要的提交签名，以阻止未签名和验证的所有提交。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-signed-commits)”。
 
-您可以在 {% data variables.product.product_name %} 上检查已签名提交或标记的验证状态，并查看提交签名未验证的原因。 更多信息请参阅“[检查提交和标记签名验证状态](/articles/checking-your-commit-and-tag-signature-verification-status)”。
+{% data reusables.identity-and-permissions.verification-status-check %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data variables.product.product_name %} 将自动使用 GPG 通过 {% data variables.product.product_name %} web 界面对您创建的提交进行签名，当您压缩且合并您不是其作者的拉取请求时除外。 您可以选择在 {% data variables.product.prodname_codespaces %} 中使用 {% data variables.product.product_name %} 对您的提交进行签名。 由 {% data variables.product.product_name %} 签名的提交在 {% data variables.product.product_name %} 上将具有已验证的状态。 您可以使用 https://github.com/web-flow.gpg 上的公钥本地验证签名。 有关对您的代码空间启用 GPG 验证的更多信息，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”。
diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md b/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md
index 9509091194..6519b89ef3 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/about-ssh.md
@@ -11,11 +11,13 @@ topics:
   - SSH
 ---
 
-在设置 SSH 时，将会[生成 SSH 密钥并将其添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)，然后[将该密钥添加到您的 {% data variables.product.product_name %} 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。 将 SSH 密钥添加到 ssh-agent，通过使用密码确保 SSH 密钥增加一层保护。 更多信息请参阅“[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)”。
+When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
-{% if currentVersion == "free-pro-team@latest" %}要对使用 SAML 单点登录的组织所拥有的仓库使用 SSH 密钥，您需要先授权。 更多信息请参阅“[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。{% endif %}
+You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. 更多信息请参阅“[使用 SSH 密钥密码](/github/authenticating-to-github/working-with-ssh-key-passphrases)”。
 
-建议定期[查阅 SSH 密钥列表](/articles/reviewing-your-ssh-keys)，撤销任何无效或安全受到威胁的密钥。
+{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. 更多信息请参阅“[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。{% endif %}
+
+To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. 更多信息请参阅“[审查 SSH 密钥](/github/authenticating-to-github/reviewing-your-ssh-keys)”。
 
 {% if currentVersion == "free-pro-team@latest" %}
 如果 SSH 密钥一年未使用，则作为安全预防措施，
@@ -28,8 +30,4 @@ topics:
 
 - "[检查现有 SSH 密钥](/articles/checking-for-existing-ssh-keys)"
 - "[测试 SSH 连接](/articles/testing-your-ssh-connection)"
-- "[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)"
 - "[SSH 故障排除](/articles/troubleshooting-ssh)"
-{%- if currentVersion == "free-pro-team@latest" %}
-- "[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"
-{%- endif %}
diff --git a/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
index fa0d811999..ce5f50b628 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md
@@ -19,6 +19,14 @@ topics:
 
 {% data reusables.ssh.dsa-support %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**提示**：您也可以使用 {% data variables.product.prodname_cli %} 添加 SSH 密钥。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh ssh-key add`](https://cli.github.com/manual/gh_ssh-key_add)”。
+
+{% endtip %}
+{% endif %}
+
 {% mac %}
 
 1. 将 SSH 公钥复制到剪贴板。
@@ -80,6 +88,7 @@ topics:
   如果您的 SSH 公钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。
 
   ```shell
+  $ sudo apt-get update
   $ sudo apt-get install xclip
   # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
 
diff --git a/translations/zh-CN/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md b/translations/zh-CN/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
index 5b888aedc2..06e84dc267 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/checking-for-existing-gpg-keys.md
@@ -16,7 +16,7 @@ topics:
 
 {% note %}
 
-**注：**GPG 并未默认安装在 OS X 或 Windows 上。 要安装 GPG 命令行工具，请参阅 [GnuPG 的下载页面](https://www.gnupg.org/download/)。
+**注：**GPG 并未默认安装在 macOS 或 Windows 上。 要安装 GPG 命令行工具，请参阅 [GnuPG 的下载页面](https://www.gnupg.org/download/)。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/zh-CN/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
index 8fda2c39d8..d4dcaa550c 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md
@@ -19,18 +19,16 @@ topics:
 
 {% data variables.product.product_name %} 上，导航到您的拉取请求。
 {% data reusables.repositories.review-pr-commits %}
-3. 在提交的缩写提交哈希旁边有一个框，显示您的提交签名是否经过验证。 ![已签名提交](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
-4. 要查看有关提交签名的更详细信息，请单击 **Verified（已验证）**或 **Unverified（未验证）**。 ![经验证签名提交](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
-
-如果您的提交签名未经验证，可单击 **Unverified（未验证）**框以了解详细原因。 ![未经验证签名提交](/assets/images/help/commits/gpg-signed-commit-unverified-details.png)
+3. Next to your commit's abbreviated commit hash, there is a box that shows whether your commit signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![已签名提交](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. To view more detailed information about the commit signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![经验证签名提交](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
 ### 检查标记签名验证状态
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 2. 在 Releases（版本）页面的顶部，单击 **Tags（标记）**。 ![标记页面](/assets/images/help/releases/tags-list.png)
-3. 在标记说明的旁边有一个框，显示您的标记签名是否经过验证。 ![已验证标记签名](/assets/images/help/commits/gpg-signed-tag-verified.png)
-4. 要查看有关标记签名的更详细信息，请单击 **Verified（已验证）**或 **Unverified（未验证）**。 如果您的标记签名未经验证，可单击 **Unverified（未验证）**框以了解详细原因。 ![经验证签名标记](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+3. Next to your tag description, there is a box that shows whether your tag signature is verified{% if currentVersion == "free-pro-team@latest" %}, partially verified,{% endif %} or unverified. ![已验证标记签名](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. To view more detailed information about the tag signature, click **Verified**{% if currentVersion == "free-pro-team@latest" %}, **Partially verified**,{% endif %} or **Unverified**. ![经验证签名标记](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md
index b776a1679d..4483429de9 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md
@@ -17,13 +17,13 @@ topics:
 
 在使用[GitHub API 或](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)命令[行](#using-a-token-on-the-command-line)时，可使用个人访问令牌 (PAT) 代替密码向 {% data variables.product.product_name %} 进行身份验证。
 
-{% if currentVersion == "free-pro-team@latest" %}如果要使用 PAT 访问使用 SAML SSO 的组织所拥有的资源，则必须授权 PAT。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/articles/about-authentication-with-saml-single-sign-on)”和“[授权个人访问令牌用于 SAML 单点登录](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}如果要使用 PAT 访问使用 SAML SSO 的组织所拥有的资源，则必须授权 PAT。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”和“[授权个人访问令牌用于 SAML 单点登录](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
 ### 创建令牌
 
-{% if currentVersion == "free-pro-team@latest" %}1. [验证您的电子邮件地址](/articles/verifying-your-email-address)（如果尚未验证）。{% endif %}
+{% if currentVersion == "free-pro-team@latest" %}1. [验证您的电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)（如果尚未验证）。{% endif %}
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
@@ -45,13 +45,13 @@ topics:
    {% else %}
    ![新建的令牌](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png)
    {% endif %}
-
    {% warning %}
 
    **警告：** 像对待密码一样对待您的令牌，确保其机密性。 使用 API 时，应将令牌用作环境变量，而不是将其硬编码到程序中。
 
    {% endwarning %}
-{% if currentVersion == "free-pro-team@latest" %}9. 要使用令牌向实施 SAML SSO 的组织验证，[请授权该令牌用于 SAML 单点登录组织](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。{% endif %}
+
+{% if currentVersion == "free-pro-team@latest" %}9. 要使用令牌向实施 SAML SSO 的组织验证，[请授权该令牌用于 SAML 单点登录组织](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。{% endif %}
 
 ### 在命令行上使用令牌
 
@@ -59,7 +59,7 @@ topics:
 
 个人访问令牌只能用于 HTTPS Git 操作。 如果您的仓库使用 SSH 远程 URL，则需要[将远程 URL 从 SSH 切换到 HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https)。
 
-如果没有提示您输入用户名和密码，说明您的凭据可能已缓存在计算机上。 您可以[在密钥链中更新您的凭据](/articles/updating-credentials-from-the-osx-keychain)，用令牌替换您的旧密码。
+如果没有提示您输入用户名和密码，说明您的凭据可能已缓存在计算机上。 您可以[在密钥链中更新您的凭据](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain)，用令牌替换您的旧密码。
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md b/translations/zh-CN/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..47895a80cd
--- /dev/null
+++ b/translations/zh-CN/content/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,36 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  free-pro-team: '*'
+topics:
+  - Identity
+  - Access management
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+### About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
+
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+### Enabling vigilant mode
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/zh-CN/content/github/authenticating-to-github/error-unknown-key-type.md b/translations/zh-CN/content/github/authenticating-to-github/error-unknown-key-type.md
new file mode 100644
index 0000000000..f8d083e0ef
--- /dev/null
+++ b/translations/zh-CN/content/github/authenticating-to-github/error-unknown-key-type.md
@@ -0,0 +1,35 @@
+---
+title: 'Error: Unknown key type'
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+  github-ae: next
+topics:
+  - SSH
+---
+
+### About the `unknown key type` error
+
+When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
+
+### 基本要求
+
+You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+
+### 解决问题
+
+{% warning %}
+
+**Warning:** If you install OpenSSH, your computer will not be able to retrieve passphrases that are stored in the Apple keychain. You will need to enter your passphrase or interact with your hardware security key every time you authenticate with SSH to {% data variables.product.prodname_dotcom %} or another web service.
+
+If you remove OpenSSH, the passphrases that are stored in your keychain will once again be retrievable. You can remove OpenSSH by entering the command `brew uninstall openssh` in Terminal.
+
+{% endwarning %}
+
+1. 打开终端。
+2. Enter the command `brew install openssh`.
+3. Quit and relaunch Terminal.
+4. Try the procedure for generating a new SSH key again. 更多信息请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)”。
+
+{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
diff --git a/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 0cbe67f7bd..0fd988d180 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -13,9 +13,16 @@ topics:
   - SSH
 ---
 
-如果您还没有 SSH 密钥，则必须[生成新 SSH 密钥](#generating-a-new-ssh-key)。 如果您不确定是否已有 SSH 密钥，请检查[现有密钥](/articles/checking-for-existing-ssh-keys)。
+### About SSH key generation
 
-如果不想在每次使用 SSH 密钥时重新输入密码，您可以[将密钥添加到 SSH 代理](#adding-your-ssh-key-to-the-ssh-agent)，让它管理您的 SSH 密钥并记住您的密码。
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+{% endif %}
+If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.
 
 ### 生成新 SSH 密钥
 
@@ -62,7 +69,7 @@ topics:
 
   {% endlinux %}
 
-4. 在提示时输入安全密码。 更多信息请参阅[“使用 SSH 密钥密码”](/articles/working-with-ssh-key-passphrases)。
+4. 在提示时输入安全密码。 For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
@@ -70,7 +77,7 @@ topics:
 
 ### 将 SSH 密钥添加到 ssh-agent
 
-将新 SSH 密钥添加到 ssh-agent 以管理密钥之前，应[检查现有 SSH 密钥](/articles/checking-for-existing-ssh-keys)并[生成新 SSH 密钥](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key)。 <span class="platform-mac">将 SSH 密钥添加到该代理时，应使用默认的 macOS `ssh-add` 命令，而不是使用通过 [macports](https://www.macports.org/), [homebrew](http://brew.sh/) 或某些其他外部来源安装的应用程序。</span>
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">将 SSH 密钥添加到该代理时，应使用默认的 macOS `ssh-add` 命令，而不是使用通过 [macports](https://www.macports.org/), [homebrew](http://brew.sh/) 或某些其他外部来源安装的应用程序。</span>
 
 {% mac %}
 
@@ -91,7 +98,7 @@ topics:
       $ touch ~/.ssh/config
       ```
 
-    * 打开 `~/.ssh/config` 文件，然后修改该文件，如果未使用 `id_ed25519` 键的默认位置和名称，则替换 `~/.ssh/id_ed25519`。
+    * 打开您的 `~/.ssh/config` 文件，然后修改文件以包含以下行。 如果您的 SSH 密钥文件与示例代码具有不同的名称或路径，请修改文件名或路径以匹配您当前的设置。
 
       ```
       Host *
@@ -106,6 +113,25 @@ topics:
 
      {% endnote %}
 
+      {% mac %}
+      {% note %}
+
+      **注意：**如果您看到如下错误
+
+      ```
+      /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
+      ```
+
+      向 `Host *` 部分添加一个额外的配置行：
+
+      ```
+      Host *
+        IgnoreUnknown UseKeychain
+      ```
+
+      {% endnote %}
+      {% endmac %}
+
 3. 将 SSH 私钥添加到 ssh-agent 并将密码存储在密钥链中。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_ed25519
@@ -118,7 +144,7 @@ topics:
 
   {% endnote %}
 
-4. [将 SSH 密钥添加到 GitHub 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endmac %}
 
@@ -136,7 +162,7 @@ topics:
 2. 将 SSH 私钥添加到 ssh-agent。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [将 SSH 密钥添加到 GitHub 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endwindows %}
 
@@ -144,13 +170,76 @@ topics:
 
 1. {% data reusables.command_line.start_ssh_agent %}
 
+  In some Linux environments, you need root access to run the command:
+
+  ```
+  $ sudo -s -H
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+
 2. 将 SSH 私钥添加到 ssh-agent。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
 
-3. [将 SSH 密钥添加到 GitHub 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
 
 {% endlinux %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1"  %}
+### Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+  ```shell
+  $ ssh-keygen -t ed25519-sk -C "<em>your_email@example.com</em>"
+  ```
+  {% note %}
+
+  **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+  ```shell
+   $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+  ```
+
+  {% endnote %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+  {% mac %}
+
+  ```shell
+  > Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endmac %}
+
+  {% windows %}
+
+  ```shell
+  > Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_ed25519_sk):<em>[Press enter]</em>
+  ```
+
+  {% endwindows %}
+
+  {% linux %}
+
+  ```shell
+  > Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_ed25519_sk): <em>[Press enter]</em>
+  ```
+
+  {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+  ```shell
+  > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
+  > Enter same passphrase again: <em>[Type passphrase again]</em>
+  ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endif %}
+
 ### 延伸阅读
 
 - "[关于 SSH](/articles/about-ssh)"
diff --git a/translations/zh-CN/content/github/authenticating-to-github/index.md b/translations/zh-CN/content/github/authenticating-to-github/index.md
index 84b86e9c04..811cb61af4 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/index.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/index.md
@@ -41,7 +41,7 @@ topics:
     {% link_in_list /reviewing-your-authorized-applications-oauth %}
     {% link_in_list /reviewing-your-security-log %}
     {% link_in_list /removing-sensitive-data-from-a-repository %}
-    {% link_in_list /about-anonymized-image-urls %}
+    {% link_in_list /about-anonymized-urls %}
     {% link_in_list /about-githubs-ip-addresses %}
     {% link_in_list /githubs-ssh-key-fingerprints %}
     {% link_in_list /sudo-mode %}
@@ -79,9 +79,11 @@ topics:
     {% link_in_list /error-agent-admitted-failure-to-sign %}
     {% link_in_list /error-ssh-add-illegal-option----k %}
     {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
+    {% link_in_list /error-unknown-key-type %}
     {% link_in_list /error-were-doing-an-ssh-key-audit %}
 {% topic_link_in_list /managing-commit-signature-verification %}
     {% link_in_list /about-commit-signature-verification %}
+    {% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
     {% link_in_list /checking-for-existing-gpg-keys %}
     {% link_in_list /generating-a-new-gpg-key %}
     {% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
diff --git a/translations/zh-CN/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/zh-CN/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
index 32f00bb5de..9d0f2550c9 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -60,7 +60,7 @@ topics:
 5. 在“One-time password（一次性密码）”下，键入恢复电子邮件 {% data variables.product.prodname_dotcom %} 发送的临时密码。 ![一次性密码字段](/assets/images/help/2fa/one-time-password-field.png)
 6. 单击 **Verify email address（验证电子邮件地址）**。
 7. 选择替代验证因素。
-    - 如果您之前已经使用当前设备登录此帐户，并且想使用该设备进行验证，请单击 **Verify this device（验证此设备）**。
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
     - 如果您之前已在此帐户上设置 SSH 密钥，并且想使用此 SSH 密钥进行验证，请单击 **SSH key（SSH 密钥）**。
     - 如果您之前已经设置个人访问令牌，并且想使用个人访问令牌进行验证，请单击 **Personal access token（个人访问令牌）**。 ![替代验证按钮](/assets/images/help/2fa/alt-verifications.png)
 8. {% data variables.contact.github_support %} 的成员将在 3-5 个工作日内审查您的请求并给您发送电子邮件。 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。
diff --git a/translations/zh-CN/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md b/translations/zh-CN/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
index b72f7326fd..df5ddd1615 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/recovering-your-ssh-key-passphrase.md
@@ -15,7 +15,7 @@ topics:
 
 {% mac %}
 
-如果您[使用 OS X 密钥链配置 SSH 密码](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain)，则能够恢复它。
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
 
 1. 在 Finder 中，搜索 **Keychain Access** 应用程序。 ![Spotlight 搜索栏](/assets/images/help/setup/keychain-access.png)
 2. 在 Keychain Access 中，搜索 **SSH**。
diff --git a/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md b/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md
index 52b5252b78..29ae78799e 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/reviewing-your-security-log.md
@@ -38,23 +38,23 @@ topics:
 
 安全日志中列出的事件由您的操作触发。 操作分为以下几类：
 
-| 类别名称                                                                                   | 描述                                                                                                                                                                                                                                                                                                                                               |
-| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %}
-| [`account_recovery_token`](#account_recovery_token-category-actions)                   | 包含与[添加恢复令牌](/articles/configuring-two-factor-authentication-recovery-methods)相关的所有活动。                                                                                                                                                                                                                                                            |
-| [`计费，帐单`](#billing-category-actions)                                                   | 包含与帐单信息相关的所有活动。                                                                                                                                                                                                                                                                                                                                  |
-| [`codespaces`](#codespaces-category-actions)                                           | 包含与 {% data variables.product.prodname_codespaces %} 相关的所有活动。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)”。                                                                                                                                                        |
-| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。                                                                                                                                                                                                                                                                            |
+| 类别名称                                                                                   | 描述                                                                                                                                                                                                                                                                                                                                                                                    |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %}
+| [`account_recovery_token`](#account_recovery_token-category-actions)                   | 包含与[添加恢复令牌](/articles/configuring-two-factor-authentication-recovery-methods)相关的所有活动。                                                                                                                                                                                                                                                                                                 |
+| [`计费，帐单`](#billing-category-actions)                                                   | 包含与帐单信息相关的所有活动。                                                                                                                                                                                                                                                                                                                                                                       |
+| [`codespaces`](#codespaces-category-actions)                                           | 包含与 {% data variables.product.prodname_codespaces %} 相关的所有活动。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)”。                                                                                                                                                                                             |
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。                                                                                                                                                                                                                                                                                                                 |
 | [`marketplace_listing`](#marketplace_listing-category-actions)                         | 包含与 {% data variables.product.prodname_marketplace %} 中列出的应用程序相关的所有活动。{% endif %}
 | [`oauth_access`](#oauth_access-category-actions)                                       | 包含与您已连接的 [{% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps) 相关的所有活动。{% if currentVersion == "free-pro-team@latest" %}
 | [`payment_method`](#payment_method-category-actions)                                   | 包含与 {% data variables.product.prodname_dotcom %} 订阅支付相关的所有活动。{% endif %}
-| [`profile_picture`](#profile_picture-category-actions)                                 | 包含与头像相关的所有活动。                                                                                                                                                                                                                                                                                                                                    |
-| [`project`](#project-category-actions)                                                 | 包含与项目板相关的所有活动。                                                                                                                                                                                                                                                                                                                                   |
-| [`public_key`](#public_key-category-actions)                                           | 包含与[公共 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account)相关的所有活动。                                                                                                                                                                                                                                                                    |
+| [`profile_picture`](#profile_picture-category-actions)                                 | 包含与头像相关的所有活动。                                                                                                                                                                                                                                                                                                                                                                         |
+| [`project`](#project-category-actions)                                                 | 包含与项目板相关的所有活动。                                                                                                                                                                                                                                                                                                                                                                        |
+| [`public_key`](#public_key-category-actions)                                           | 包含与[公共 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account)相关的所有活动。                                                                                                                                                                                                                                                                                                         |
 | [`repo`](#repo-category-actions)                                                       | 包含与您拥有的仓库相关的所有活动。{% if currentVersion == "free-pro-team@latest" %}
-| [`sponsors`](#sponsors-category-actions)                                               | 包含与 {% data variables.product.prodname_sponsors %}和赞助者按钮相关的所有事件（请参阅“[关于 {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)”和“[在仓库中显示赞助者按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+| [`sponsors`](#sponsors-category-actions)                                               | 包含与 {% data variables.product.prodname_sponsors %}和赞助者按钮相关的所有事件（请参阅“[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”和“[在仓库中显示赞助者按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）{% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
 | [`团队`](#team-category-actions)                                                         | 包含与您所在团队相关的所有活动。{% endif %}{% if currentVersion != "github-ae@latest" %}
 | [`two_factor_authentication`](#two_factor_authentication-category-actions)             | 包含与[双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)相关的所有活动。{% endif %}
-| [`用户`](#user-category-actions)                                                         | 包含与您的帐户相关的所有活动。                                                                                                                                                                                                                                                                                                                                  |
+| [`用户`](#user-category-actions)                                                         | 包含与您的帐户相关的所有活动。                                                                                                                                                                                                                                                                                                                                                                       |
 
 {% if currentVersion == "free-pro-team@latest" %}
 
@@ -90,6 +90,10 @@ topics:
 
 | 操作                                   | 描述                                                                                                                                                                |
 | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`                             | 当您[创建代码空间](/github/developing-online-with-codespaces/creating-a-codespace)时触发。                                                                                    |
+| `resume`                             | 恢复暂停的代码空间时触发。                                                                                                                                                     |
+| `delete`                             | 当您[删除代码空间](/github/developing-online-with-codespaces/deleting-a-codespace)时触发。                                                                                    |
+| `manage_access_and_security`         | 当您更新[代码空间可以访问的仓库时](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)触发。                                                      |
 | `trusted_repositories_access_update` | 当您更改用户帐户的 [{% data variables.product.prodname_codespaces %} 访问权限和安全设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)时触发。 |
 
 #### `marketplace_agreement_signature` 类操作
@@ -181,22 +185,24 @@ topics:
 {% if currentVersion == "free-pro-team@latest" %}
 #### `sponsors` 类操作
 
-| 操作                                            | 描述                                                                                                                                                                                                                                                   |
-| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo_funding_link_button_toggle`             | 在仓库中启用或禁用赞助按钮时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）                                                                                                                                                        |
-| `repo_funding_links_file_action`              | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）                                                                                                                                                    |
-| `sponsor_sponsorship_cancel`                  | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                                          |
-| `sponsor_sponsorship_create`                  | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)”）                                                                                                                   |
-| `sponsor_sponsorship_preference_change`       | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/articles/managing-your-sponsorship)”）                                                                                                                                                                           |
-| `sponsor_sponsorship_tier_change`             | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                           |
-| `sponsored_developer_approve`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）     |
-| `sponsored_developer_create`                  | 当您的 {% data variables.product.prodname_sponsors %} 帐户创建时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）      |
-| `sponsored_developer_profile_update`          | 在编辑您的被赞助开发者个人资料时触发（请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)”）                                           |
-| `sponsored_developer_request_approval`        | 提交您对 {% data variables.product.prodname_sponsors %} 的申请以供审批时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）  |
-| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                        |
-| `sponsored_developer_update_newsletter_send`  | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/articles/contacting-your-sponsors)”）                                                                                                                                                                                  |
-| `waitlist_invite_sponsored_developer`         | 当您从等候名单被邀请加入 {% data variables.product.prodname_sponsors %} 时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） |
-| `waitlist_join`                               | 当您加入成为被赞助开发者的等候名单时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）                                            |
+| 操作                                            | 描述                                                                                                                                                                                                                                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | 启用或禁用自定义金额时或更改建议的自定义金额时触发（请参阅“[管理您的赞助级别](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                                                                                   |
+| `repo_funding_links_file_action`              | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）                                                                                                                                                                                                               |
+| `sponsor_sponsorship_cancel`                  | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                                                                                                     |
+| `sponsor_sponsorship_create`                  | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                                                                                                                  |
+| `sponsor_sponsorship_preference_change`       | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”）                                                                                                                                                                                                  |
+| `sponsor_sponsorship_tier_change`             | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                                                      |
+| `sponsored_developer_approve`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）                                                                         |
+| `sponsored_developer_create`                  | 当您的 {% data variables.product.prodname_sponsors %} 帐户创建时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）                                                                          |
+| `sponsored_developer_disable`                 | 帐户 {% data variables.product.prodname_sponsors %} 禁用时触发                                                                                                                                                                                                                                                         |
+| `sponsored_developer_redraft`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户从已批准状态恢复为草稿状态时触发                                                                                                                                                                                                                                           |
+| `sponsored_developer_profile_update`          | 在编辑您的被赞助开发者个人资料时触发（请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)”）                                                                                                               |
+| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
+| `sponsored_developer_tier_description_update` | 当您更改赞助等级的说明时触发（请参阅“[管理赞助等级](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                                                                                                         |
+| `sponsored_developer_update_newsletter_send`  | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)”）                                                                                                                                                                                              |
+| `waitlist_invite_sponsored_developer`         | 当您从等候名单被邀请加入 {% data variables.product.prodname_sponsors %} 时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）                                                                     |
+| `waitlist_join`                               | 当您加入成为被赞助开发者的等候名单时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”）                                                                                                                |
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
@@ -258,4 +264,3 @@ topics:
 | --------- | -------------------------------------------------------------------------------------------- |
 | `update`  | 当您在个人资料中设置或更改状态时触发。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。 |
 | `destroy` | 当您在个人资料中清除状态时触发。                                                                             |
-
diff --git a/translations/zh-CN/content/github/authenticating-to-github/using-ssh-over-the-https-port.md b/translations/zh-CN/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
index 0a1766859a..33d830dcae 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/using-ssh-over-the-https-port.md
@@ -11,7 +11,7 @@ topics:
 
 {% tip %}
 
-**GitHub Enterprise 用户**：目前不支持通过 HTTPS 端口上的 SSH 访问 GitHub Enterprise。
+**{% data variables.product.prodname_ghe_server %} 用户**：目前不支持经 SSH 通过 HTTPS 端口访问 {% data variables.product.prodname_ghe_server %}。
 
 {% endtip %}
 
diff --git a/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
index 215e105b1b..da01420dcf 100644
--- a/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
+++ b/translations/zh-CN/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md
@@ -104,7 +104,7 @@ unset env
 
 ### 在密钥链中保存密码
 
-在 OS X Leopard 上通过 OS X El Capitan，这些默认私钥文件将自动处理：
+On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
index 1e51ea54ef..5de2c72d38 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models.md
@@ -1,6 +1,6 @@
 ---
 title: 关于协作开发模式
-intro: 使用拉取请求的方式取决于项目中使用的开发模型类型。
+intro: 使用拉取请求的方式取决于项目中使用的开发模型类型。 You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /articles/types-of-collaborative-development-models/
   - /articles/about-collaborative-development-models
@@ -12,7 +12,9 @@ topics:
   - Pull requests
 ---
 
-用于拉取请求的开发模型主要有两种。 在*复刻和拉取模型*中，任何人都可以复刻现有仓库并推送对其个人复刻的更改。 不需要对来源仓库的权限即可推送到用户拥有的复刻。 项目维护员可将更改拉入来源仓库。 将提议更改的拉取请求从用户拥有的复刻打开到来源（上游）仓库的分支时，可让对上游仓库具有推送权限的任何人更改您的拉取请求。  此模型常用于开源项目，因为它可减少新贡献者的磨合，让人们独立工作而无需前期协调。
+### Fork and pull model
+
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. 不需要对来源仓库的权限即可推送到用户拥有的复刻。 项目维护员可将更改拉入来源仓库。 将提议更改的拉取请求从用户拥有的复刻打开到来源（上游）仓库的分支时，可让对上游仓库具有推送权限的任何人更改您的拉取请求。  此模型常用于开源项目，因为它可减少新贡献者的磨合，让人们独立工作而无需前期协调。
 
 {% tip %}
 
@@ -20,7 +22,9 @@ topics:
 
 {% endtip %}
 
-在*共享仓库模型*中，协作者被授予单一共享仓库的推送权限，需要更改时可创建主题分支。 拉取请求适用于此模型，因为在更改合并到主要开发分支之前，它们会发起代码审查和关于更改的一般讨论。 此模型更多用于协作处理私有项目的小型团队和组织。
+### Shared repository model
+
+在共享仓库模型中，协作者被授予单一共享仓库的推送权限，需要更改时可创建主题分支。 拉取请求适用于此模型，因为在更改合并到主要开发分支之前，它们会发起代码审查和关于更改的一般讨论。 此模型更多用于协作处理私有项目的小型团队和组织。
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
index 8f0d03d0ab..ec35b82ff4 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-status-checks.md
@@ -53,18 +53,18 @@ _检查_与_状态_的不同之处在于它们提供行注解、更详细的信
 
 要跳过或申请检查提交，请在提交消息末添加以下尾行之一：
 
-- 要_跳过检查_提交，请输入提交消息以及简短、有意义的更改描述。 在提交说明后，不要加上右引号，而是添加两个空行，后接 `skip-checks: true`：
+- 要_跳过检查_提交，请输入提交消息以及简短、有意义的更改描述。 After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`:
   ```shell
-  $ git commit -m "Update README.
+  $ git commit -m "Update README
   >
   >
-  skip-checks: true
+  skip-checks: true"
   ```
-  - 要_申请检查_提交，请输入提交消息以及简短、有意义的更改描述。 在提交说明后，不要加上右引号，而是添加两个空行，后接 `request-checks: true`：
+- 要_申请检查_提交，请输入提交消息以及简短、有意义的更改描述。 After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`:
   ```shell
-  $ git commit -m "Refactor usability tests.
+  $ git commit -m "Refactor usability tests
   >
   >
-  request-checks: true
+  request-checks: true"
   ```
   
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
index 92438e8350..fca54cf9ea 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
@@ -14,7 +14,7 @@ topics:
 
 如果启用拉取请求自动合并，则拉取请求在满足所有必需审查并且状态检查通过时将自动合并。 自动合并使您无需等待满足要求，可以继续执行其他任务。
 
-在使用拉取请求自动合并之前，必需对仓库启用自动合并。 更多信息请参阅“[管理仓库中拉取请求的自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)”。{% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next " or currentversion ver_gt "enterprise-server@3.1" %}
+在使用拉取请求自动合并之前，必需对仓库启用自动合并。 更多信息请参阅“[管理仓库中拉取请求的自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)”。{% if currentVersion == "free-proteam@latest" or currentVersion == "github-ae@next " or currentVersion ver_gt "enterprise-server@3.1" %}
 
 对拉取请求启用自动合并后，如果没有仓库写入权限的人员将新更改推送到头部分支或切换拉取请求的基础分支，则自动合并将被禁用。 例如，如果维护者允许从复刻自动合并拉取请求，则在贡献者推送对拉取请求的新更改后，自动合并将被禁用。{% endif %}
 
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
index 1acadc652c..43ab9d7288 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -17,6 +17,14 @@ topics:
 
 {% data reusables.pull_requests.mark-ready-review %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 {% data reusables.repositories.sidebar-pr %}
 2. 在“Pull Requests（拉取请求）”列表中，单击要标记为可供审查的拉取请求。
 3. 在合并框中，单击 **Ready for review（可供审查）**。 ![可供审查按钮](/assets/images/help/pull_requests/ready-for-review-button.png)
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
index 2a82a5eca3..9eb0f14e75 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md
@@ -18,6 +18,14 @@ topics:
 
   {% endnote %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also check out a pull request locally using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr checkout`](https://cli.github.com/manual/gh_pr_checkout)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### 在本地修改活动的拉取请求
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
index b4e3b7dcec..bbec204bee 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md
@@ -36,7 +36,7 @@ topics:
 
 **提示：**
 - 拉取请求评论支持与 {% data variables.product.product_name %} 上的一般评论相同的[格式](/categories/writing-on-github)，例如 @提及、表情符号和引用。
-- 您可以在 **Files changed（已更改文件）**选项卡中向拉取请求的评论[添加反应](/articles/about-conversations-on-github#reacting-to-ideas-in-comments)。
+- You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
index 5414dc6af0..68cee45f9b 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md
@@ -19,6 +19,14 @@ topics:
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can create a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr create`](https://cli.github.com/manual/gh_pr_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### 更改分支范围和目标仓库
 
 默认情况下，拉取请求基于父仓库的默认分支。 更多信息请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
index 3b2fbe3ea2..e9e5a11fd7 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -34,7 +34,7 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.navigate-to-branches %}
-1. 滚动到要删除的分支，然后单击 {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}。 ![删除分支](/assets/images/help/branches/branches-delete.png)
+1. 滚动到要删除的分支，然后单击 {% octicon "trash" aria-label="The trash icon to delete the branch" %}。 ![删除分支](/assets/images/help/branches/branches-delete.png)
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/getting-started.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
new file mode 100644
index 0000000000..2fb3b805be
--- /dev/null
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/getting-started.md
@@ -0,0 +1,18 @@
+---
+title: 入门指南
+shortTitle: 入门指南
+intro: '了解 {% data variables.product.prodname_dotcom %} 流程以及协作和讨论项目的不同方式。'
+mapTopic: true
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/overview
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md
index bf4f0156ad..35770ed8f9 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: 使用议题和拉取请求进行协作
-intro: '使用 {% data variables.product.prodname_dotcom %} 流跟踪和讨论议题中的更改，然后提出和审查拉取请求中的更改。'
+intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
   - /categories/63/articles/
   - /categories/collaborating/
@@ -18,10 +18,9 @@ topics:
 
 ### 目录
 
-{% topic_link_in_list /overview %}
-    {% link_in_list /github-flow %}
+{% topic_link_in_list /getting-started %}
+    {% link_in_list /quickstart-for-communicating-on-github %}
     {% link_in_list /about-collaborative-development-models %}
-    {% link_in_list /about-conversations-on-github %}
 {% topic_link_in_list /working-with-forks %}
     {% link_in_list /about-forks %}
     {% link_in_list /configuring-a-remote-for-a-fork %}
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
index 4cae14ed63..2cecf4579c 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md
@@ -25,6 +25,14 @@ topics:
 
 如果决定不想让主题分支中的更改合并到上游分支，您可以[关闭拉取请求](/articles/closing-a-pull-request)而不合并。
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
+{% tip %}
+
+**Tip**: You can also merge a pull request using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr merge`](https://cli.github.com/manual/gh_pr_merge)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+{% endif %}
+
 ### 在 {% data variables.product.prodname_dotcom %} 上合并拉取请求
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
new file mode 100644
index 0000000000..69e7c1c257
--- /dev/null
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github.md
@@ -0,0 +1,149 @@
+---
+title: Quickstart for communicating on GitHub
+intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /articles/about-discussions-in-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+---
+
+### 简介
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+{% endif %}
+
+#### 议题
+- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
+- are specific to a repository, and usually have a clear owner.
+- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+
+#### 拉取请求
+- allow you to propose specific changes.
+- allow you comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_discussions %}
+-  are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
+-  may span many repositories.
+-  provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
+-  often don’t have a clear owner.
+-  often do not result in an actionable task.
+{% endif %}
+
+#### 团队讨论
+- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. 不要在仓库中开启一个议题来讨论一个想法，而可以通过在团队讨论中进行对话将整个团队包括在内。
+- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% if currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
+- often don’t have a clear owner.
+- often do not result in an actionable task.{% endif %}
+
+### Which discussion tool should I use?
+
+#### Scenarios for issues
+
+- I want to keep track of tasks, enhancements and bugs.
+- I want to file a bug report.
+- I want to share feedback about a specific feature.
+- I want to ask a question about files in the repository.
+
+##### Issue example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
+
+![Example of issue](/assets/images/help/issues/issue-example.png)
+
+- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
+- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
+- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
+- A contributor can then create a pull request with the fix.
+
+#### Scenarios for pull requests
+
+- I want to fix a typo in a repository.
+- I want to make changes to a repository.
+- I want to make changes to fix an issue.
+- I want to comment on changes suggested by others.
+
+##### Pull request example
+
+This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
+
+In the **Conversation** tab of the pull request, the author explain why they created the pull request. ![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+The **Files changed** tab of the pull request shows the implemented fix. ![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- This contributor notices a typo in the repository.
+- The user creates a pull request with the fix.
+- A repository maintainer reviews the pull request, comments on it, and merges it.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Scenarios for {% data variables.product.prodname_discussions %}
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my community.
+
+##### {% data variables.product.prodname_discussions %} example
+
+This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
+
+![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+
+This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
+
+{% endif %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
+#### Scenarios for team discussions
+
+- I have a question that's not necessarily related to specific files in the repository.
+- I want to share news with my collaborators, or my team.
+- I want to start or participate in an open-ended conversation.
+- I want to make an announcement to my team.
+
+{% if currentVersion == "free-pro-team@latest" %}
+As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
+{% endif %}
+
+##### Team discussion example
+
+This example shows a team post for the `octo-team` team.
+
+![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+
+The `octocat` team member posted a team discussion, informing the team of various things:
+- A team member called Mona started remote game events.
+- There is a blog post describing how the teams uses {% data variables.product.prodname_actions %} to produce their docs.
+- Material about the April All Hands is now available for all team members to view.
+
+{% endif %}
+
+### 后续步骤
+
+These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
+
+For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
+
+For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)”。
+
+{% if currentVersion == "free-pro-team@latest" %}
+For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
+{% endif %}
+
+For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。
diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 7a6ad0b96c..0466657612 100644
--- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -79,5 +79,5 @@ topics:
 - “[设置仓库可见性](/articles/setting-repository-visibility)”
 - "[关于复刻](/articles/about-forks)"
 - "[管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)"
-- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
-- "{% if currentversion == "free-proteam@latest" %}[在企业帐户中执行仓库管理策略](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[在企业中执行仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}"
+- "[管理组织的复刻策略](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
+- "{% if currentVersion == "free-proteam@latest" %}[在企业帐户中执行仓库管理策略](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[在企业中执行仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}"
diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
index de7ec007e6..3bba35bba8 100644
--- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
+++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md
@@ -42,9 +42,21 @@ topics:
 
 {% endif %}
 
+### 为 README 文件自动生成的目录
+
+对于仓库中任何 Markdown 文件（包括 README 文件）的视图，{% data variables.product.product_name %} 将自动生成基于章节标题的目录。 您可以通过单击渲染页面左上侧的 {% octicon "list-unordered" aria-label="The unordered list icon" %}  菜单图标来查看 README 文件的目录。
+
+![自动生成目录的自述文件](/assets/images/help/repository/readme-automatic-toc.png)
+
+自动生成的目录默认对仓库中所有 Markdown 文件启用，但您可以对您的仓库禁用此功能。
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. 在“Features（功能）”下，取消选择 **Table of contents（目录）**。 ![仓库的自动目录设置](/assets/images/help/repository/readme-automatic-toc-setting.png)
+
 ### 自述文件和 blob 页面中的章节链接
 
-许多项目使用目录和自述文件的开头将用户导向文件的不同章节。 {% data reusables.repositories.section-links %}
+{% data reusables.repositories.section-links %}
 
 ### 自述文件中的相对链接和图像路径
 
diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md
index 883a5e8760..5a30d342c2 100644
--- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md
+++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md
@@ -11,11 +11,11 @@ topics:
 
 ### 关于仓库可见性
 
-{% if currentversion == "github-ae@latest" %}当您创建由您的用户帐户拥有的仓库时，仓库始终是私有的。 创建组织拥有的仓库时，可以选择将仓库设为私有或内部。{% else %}创建仓库时，可以选择使仓库成为公共或私有。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 如果要在组织中创建{% if currentVersion == "free-pro-team@latest" %} 由企业帐户拥有的仓库{% endif %}，也可以选择将仓库设为内部。{% endif %}{% endif %}
+{% if currentVersion == "github-ae@latest" %}当您创建由您的用户帐户拥有的仓库时，仓库始终是私有的。 创建组织拥有的仓库时，可以选择将仓库设为私有或内部。{% else %}创建仓库时，可以选择使仓库成为公共或私有。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 如果要在组织中创建{% if currentVersion == "free-pro-team@latest" %} 由企业帐户拥有的仓库{% endif %}，也可以选择将仓库设为内部。{% endif %}{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion %}
 如果
-{% data variables.product.product_location %} 不是私人模式或在防火墙后面，所有人都可以在互联网上访问公共仓库。 或者，使用 {% data variables.product.product_location %} 的每个人都可以使用公共仓库，包括外部协作者。 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 {% if currentversion ver_gt "enterprise-server@2.19" %} 内部仓库可供企业成员访问。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。{% endif %}
+{% data variables.product.product_location %} 不是私人模式或在防火墙后面，所有人都可以在互联网上访问公共仓库。 或者，使用 {% data variables.product.product_location %} 的每个人都可以使用公共仓库，包括外部协作者。 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 {% if currentVersion ver_gt "enterprise-server@2.19" %} 内部仓库可供企业成员访问。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。{% endif %}
 {% elsif currentVersion == "github-ae@latest" %}
 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 所有企业成员均可访问内部仓库。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。
 {% else %}
diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
index ed88573871..24b5023b97 100644
--- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
+++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md
@@ -24,7 +24,7 @@ topics:
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-您可以选择仅包括模板仓库的默认分支中的目录结构和文件，或者包括所有分支。
+您可以选择仅包括模板仓库的默认分支中的目录结构和文件，或者包括所有分支。 Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
 {% endif %}
 
 从模板创建仓库类似于创建仓库的复刻，但存在一些重要差异：
diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
index a80e42e79a..05b6711fbb 100644
--- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
+++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md
@@ -20,7 +20,7 @@ topics:
 
 要创建模板仓库，必须先创建一个仓库，然后将该仓库设置为模板。 关于创建仓库的更多信息，请参阅“[创建新仓库](/articles/creating-a-new-repository)”。
 
-将仓库设置为模板后，有权访问仓库的任何人都可以生成与默认分支具有相同目录结构和文件的新仓库。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} 他们还可以选择包含您的仓库中的所有其他分支。{% endif %} 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。
+After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
index 887b5c5d05..b21b32e9d0 100644
--- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
+++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md
@@ -1,6 +1,6 @@
 ---
 title: 错误：未找到仓库
-intro: '{% if currentversion == "free-proteam@latest" or currentversion == "github-ae@latest" %}如果您在克隆仓库时看到这个错误，意味着仓库不存在或您没有权限访问它。{% else %}如果您在克隆仓库时看到此错误，意味着仓库不存在、您没有访问权限，或者 {% data variables.product.product_location %} 处于隐私模式。{% endif %} 对此错误有一些解决办法，具体取决于错误原因。'
+intro: '{% if currentVersion == "free-proteam@latest" or currentVersion == "github-ae@latest" %}如果您在克隆仓库时看到这个错误，意味着仓库不存在或您没有权限访问它。{% else %}如果您在克隆仓库时看到此错误，意味着仓库不存在、您没有访问权限，或者 {% data variables.product.product_location %} 处于隐私模式。{% endif %} 对此错误有一些解决办法，具体取决于错误原因。'
 redirect_from:
   - /articles/error-repository-not-found
 versions:
@@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > provide shell access.
 ```
 
-如果仓库属于组织，并且您使用的是 OAuth App 生成的 SSH 密钥，则 OAuth App 访问权限可能已被组织所有者限制。 For more information, see "<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">About OAuth App access restrictions</a>."
+如果仓库属于组织，并且您使用的是 OAuth App 生成的 SSH 密钥，则 OAuth App 访问权限可能已被组织所有者限制。 更多信息请参阅“<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">关于 OAuth App 访问限制</a>”。
 
 更多信息请参阅[添加 SSH 密钥到 GitHub 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。
 
diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
index 79aac4cd4a..d24fa7bd65 100644
--- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
+++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md
@@ -13,7 +13,7 @@ topics:
 
 ### 选择合适的许可
 
-我们创建了 [choosealicense.com](http://choosealicense.com)，以帮助您了解如何许可您的代码。 软件许可是告诉其他人，他们能够对您的代码做什么，不能做什么，因此做明智的决定很重要。
+我们创建了 [choosealicense.com](https://choosealicense.com)，以帮助您了解如何许可您的代码。 软件许可是告诉其他人，他们能够对您的代码做什么，不能做什么，因此做明智的决定很重要。
 
 您没有选择许可的义务， 但如果没有许可，就会默认实施版权法，因此您会保留对您的源代码的所有权利，任何人都不能复制、分发您的工作或创建其派生作品。 如果您创建开源项目，强烈建议您包含开源许可。 [开源指南](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project)提供为项目选择正确许可的附加指导。
 
@@ -76,7 +76,7 @@ topics:
 
 ### 检测许可
 
-[开源 Ruby gem 被许可人](https://github.com/licensee/licensee)比较仓库的 *LICENSE* 文件与已知许可短列表。 被许可人还提供[许可 API](/rest/reference/licenses) 并[向我们提供如何许可 {% data variables.product.product_name %} 上的仓库的洞见](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果您的仓库使用的许可未列在[选择许可网站](http://choosealicense.com/appendix/)中，您可以[申请包含该许可](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。
+[开源 Ruby gem 被许可人](https://github.com/licensee/licensee)比较仓库的 *LICENSE* 文件与已知许可短列表。 被许可人还提供[许可 API](/rest/reference/licenses) 并[向我们提供如何许可 {% data variables.product.product_name %} 上的仓库的洞见](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果您的仓库使用的许可未列在[选择许可网站](https://choosealicense.com/appendix/)中，您可以[申请包含该许可](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。
 
 如果您的仓库使用的许可列在“选择许可”网站中，但未明确显示在仓库页面顶部，其中可能包含多个许可或存在其他复杂性。 为使您的许可被检测到，请简化*许可*文件，并在其他位置注明复杂性，例如在仓库的*自述文件*中。
 
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
index 9684696ef4..e8b73edede 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md
@@ -5,8 +5,7 @@ product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/managing-security-vulnerabilities/about-automated-code-scanning
 versions:
-  free-pro-team: '*'
-  enterprise-server: '>=2.22'
+  enterprise-server: '2.22'
 ---
 
 {% data reusables.code-scanning.beta %}
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
index e75e219844..00b2be98cd 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
index 5a9e36cf28..b832c7a036 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
index 612c2f6227..a6cbb46797 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md
@@ -1,60 +1,61 @@
 ---
-title: Configuring code scanning
-intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+title: 配置代码扫描
+intro: '您可以配置 {% data variables.product.prodname_dotcom %} 如何扫描项目代码以查找漏洞和错误。'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
 miniTocMaxHeadingLevel: 4
 versions:
-  free-pro-team: '*'
-  enterprise-server: '>=2.22'
+  enterprise-server: '2.22'
+topics:
+  - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-### About {% data variables.product.prodname_code_scanning %} configuration
+### 关于 {% data variables.product.prodname_code_scanning %} 配置
 
-You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+您可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 中运行 {% data variables.product.prodname_code_scanning %}，或使用 {% data variables.product.prodname_codeql_runner %} 从持续集成 (CI) 系统运行它。 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。 有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”。
 
-This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}.
+本文说明在 {% data variables.product.product_name %} 上运行 {% data variables.product.prodname_code_scanning %}。
 
-Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)."
+在为仓库配置 {% data variables.product.prodname_code_scanning %} 之前，必须将 {% data variables.product.prodname_actions %} 工作流程添加到仓库中以设置 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)”。
 
 {% data reusables.code-scanning.edit-workflow %}
 
-{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file.
+您可以为 {% data variables.product.prodname_code_scanning %} 编写配置文件。 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_marketplace %} 包含您可以使用的其他 {% data variables.product.prodname_code_scanning %} 工作流程。 此文章中提供的具体示例与 {% data variables.product.prodname_codeql_workflow %} 文件有关。
 
-### Editing a {% data variables.product.prodname_code_scanning %} workflow
+### Editing a code scanning workflow
 
-{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+{% data variables.product.prodname_dotcom %} 将工作流程文件保存在仓库的 _.github/workflows_ 目录中。 您可以通过搜索其文件名来查找已添加的工作流程。 例如，默认情况下，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的工作流程文件被称为 _codeql-analysis.yml_。
 
-1. In your repository, browse to the workflow file you want to edit.
-1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
-1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
-![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+1. 在仓库中，浏览至要编辑的工作流程文件。
+1. 要打开工作流程编辑器，在文件视图右上角单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑工作流程文件按钮](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. 编辑文件后，单击 **Start commit（开始提交）**并完成“Commit changes（提交更改）”表单。 您可以选择直接提交到当前分支，或者创建一个新分支并启动拉取请求。 ![将更新提交到 codeql.yml 工作流程](/assets/images/help/repository/code-scanning-workflow-update.png)
 
-For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+有关编辑工作流程文件的更多信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-### Configuring frequency
+### 配置频率
 
-You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+您可以按时间表或在仓库中发生特定事件时扫描代码。
 
-Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+每当推送到仓库以及每次创建拉取请求时，时扫描代码可防止开发者在代码中引入新的漏洞和错误。 按时间表扫描可了解 {% data variables.product.company_short %}、安全研究者和社区发现的最新漏洞和错误，即使开发者并未主动维护仓库。
 
-#### Scanning on push
+#### 按推送扫描
 
-By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+如果使用默认工作流程，则除了事件触发的扫描之外，{% data variables.product.prodname_code_scanning %} 还会每周扫描一次仓库代码。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#on)”。
 
-#### Scanning pull requests
+#### 扫描拉取请求
 
-The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+默认 {% data variables.product.prodname_codeql_workflow %} 使用 `pull_request` 事件在针对默认分支的拉取请求上触发代码扫描。 如果从私有复刻打开拉取请求，`pull_request` 事件不会触发。
 
-For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+有关 `pull_request` 事件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)”。
 
-#### Avoiding unnecessary scans of pull requests
+#### 避免对拉取请求进行不必要的扫描
 
-You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+您可能希望避免针对默认分支的特定拉取请求触发代码扫描，而不管更改了哪些文件。 可以通过在 {% data variables.product.prodname_code_scanning %} 工作流程中指定 `on:pull_request:paths-ignore` or `on:pull_request:paths` 来进行配置。 例如，如果拉取请求中唯一的更改是文件扩展名为 `.md` 或 `.txt` 的文件，则您可以使用以下 `paths-ignore` 数组。
 
 ``` yaml
 on:
@@ -69,28 +70,28 @@ on:
 
 {% note %}
 
-**Notes**
+**注：**
 
-* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
-* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+* `on:pull_request:paths-witch` 和 `on:pull_request:pull_request:path` 设置条件来确定工作流程中的操作是否会在拉取请求上运行。 它们无法确定在操作_运行_时将分析哪些文件。 当拉取请求包含 `on:pull_request:paths-with` 或 `on:pull_request:path:path` 未匹配的任何文件时，工作流程将运行操作并扫描拉取请求中更改的所有文件，包括 `on:pull_request:paths-ignore` 或 `on:pull_request:paths` 匹配的文件，除非文件被排除在外。 有关如何从分析中排除文件的信息，请参阅“[指定要扫描的目录](#specifying-directories-to-scan)”。
+* 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 工作流程文件， 不要对 `on:push` 事件使用 `paths-ignore` 或 `paths` 关键词， 因为这可能导致缺少分析。 为了获得准确的结果，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 需要能够与上次提交的分析比较新的变化。
 
 {% endnote %}
 
-For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+有关使用 `on:pull_request:paths-ignore` 和 `on:pull_request:paths` 确定工作流程何时对拉取请求运行的详细信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。
 
-#### Scanning on a schedule
+#### 按时间表扫描
 
-If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+默认 {% data variables.product.prodname_code_scanning %} 工作流程在拉取请求的 `HEAD` 提交时使用 `pull_request` 事件触发代码扫描。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onschedule)”。
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+**注**：{% data variables.product.prodname_dotcom %} 只运行默认分支上工作流程中的预定作业。 在任何其他分支上的工作流程中更改时间表后，需要将该分支合并到默认分支才能使更改生效。
 
 {% endnote %}
 
-#### Example
+#### 示例
 
-The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. You can find the workflow by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`.
 
 ``` yaml
 on:
@@ -99,19 +100,17 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 15 * * 0'
+    - cron: '40 7 * * 2'
 ```
 
-This workflow scans:
-* Every push to the default branch and the protected branch
-* Every pull request to the default branch
-* The default branch at 3 P.M. every Sunday
+此工作流程扫描：
+* 对默认分支和受保护分支的每次推送
+* 对默认分支的每个拉取请求
+* 默认分支（每个星期二 7:40 UTC）
 
-### Specifying an operating system
+### 指定操作系统
 
-If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
-
-If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+如果您的代码需要使用特定的操作系统进行编译，您可以在工作流程中配置它。 编辑 `jobs.analyze.runs-on` 的值以指定运行 {% data variables.product.prodname_code_scanning %} 操作的机器操作系统。 在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。
 
 ``` yaml
 jobs:
@@ -120,23 +119,21 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
+{% data variables.product.prodname_code_scanning_capc %} 支持 macOS、Ubuntu 和 Windows 的最新版本。 因此，此设置的典型值为：`ubuntu-latest`、`windows-latest` 和 `macos-latest`。 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)”和和“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)”。
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
+您必须确保 Git 位于自托管运行器上的 PATH 变量中。
 
-{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
+### 更改分析的语言
 
-### Changing the languages that are analyzed
+{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 会自动检测用受支持的语言编写的代码。
 
-{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
-{% data reusables.code-scanning.supported-languages %}
-
-The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+默认 {% data variables.product.prodname_codeql_workflow %} 文件包含一个名为 `language` 的构建矩阵，其中列出了仓库中被分析的语言。 将 {% data variables.product.prodname_code_scanning %} 添加到仓库时，{% data variables.product.prodname_codeql %} 会自动填充此矩阵。 使用 `language` 矩阵优化 {% data variables.product.prodname_codeql %} 以并行运行每个分析。 由于并行构建的性能优势，我们建议所有工作流程都采用此配置。 有关构建矩阵的更多信息，请参阅“[管理复杂的工作流程](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)”。
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix.
+如果您的工作流程使用 `language` 矩阵，则 {% data variables.product.prodname_codeql %} 会被硬编码为仅分析矩阵中的语言。 如需更改要分析的语言，请编辑矩阵变量的值。 您可以删除某种语言以防止被分析，也可以添加在设置 {% data variables.product.prodname_code_scanning %} 时仓库中不存在的语言。 例如，如果在设置 {% data variables.product.prodname_code_scanning %} 时，仓库最初只包含 JavaScript，但您后来添加了 Python 代码，则需要将 `python` 添加到矩阵中。
 
 ```yaml
 jobs:
@@ -149,7 +146,7 @@ jobs:
         language: ['javascript', 'python']
 ```
 
-If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action.
+如果工作流程中不包含名为 `language` 的矩阵，则 {% data variables.product.prodname_codeql %} 将被配置为按顺序运行分析。 如果您未在工作流程中指定语言，则 {% data variables.product.prodname_codeql %} 将自动检测并尝试分析仓库中所有受支持的语言。 如果不愿意使用矩阵选择要分析的语言，您可以使用 `init` 操作下的 `languages` 参数。
 
 ```yaml
 - uses: github/codeql-action/init@v1
@@ -157,80 +154,90 @@ If your workflow does not contain a matrix called `language`, then {% data varia
     languages: cpp, csharp, python
 ```
 {% if currentVersion == "free-pro-team@latest" %}
-### Analyzing Python dependencies
+### 分析 Python 依赖项
 
-For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
+对于仅使用 Linux 的 GitHub 托管的运行器，{% data variables.product.prodname_codeql_workflow %} 将尝试自动安装 Python 依赖项以提供更多 CodeQL 分析结果。 可通过为“初始化 CodeQL”步骤调用的操作指定 `setup-python-dependencies` 参数来控制此行为。 默认情况下，此参数设置为 `true`：
 
--  If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies.
+-  如果仓库包含用 Python 编写的代码，“初始化 CodeQL”步骤将在 GitHub 托管的运行器上安装必要的依赖项。 如果自动安装成功，该操作还会将环境变量 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件。
 
-- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete.
+- 如果仓库没有任何 Python 依赖项，或者依赖项是以意外方式指定的，您将收到警告，并且该操作会继续执行其余作业。 即使在解释依赖项时出现问题，该操作也可以成功运行，但结果可能不完整。
 
-Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract:
+或者，您也可以在任何操作系统上手动安装 Python 依赖项。 您需要添加 `setup-python-dependencies` 并将其设置为 `false`，以及将 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件，如此工作流程摘要中所示：
 
 ```yaml
 jobs:
   CodeQL-Build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: '3.x'
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ];
-        then pip install -r requirements.txt;
-        fi
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
-    - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
-      with:
-        languages: python
-        # Override the default behavior so that the action doesn't attempt
-        # to auto-install Python dependencies
-        setup-python-dependencies: false
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
 ```
 {% endif %}
 
-### Running additional queries
+### 运行额外查询
 
 {% data reusables.code-scanning.run-additional-queries %}
 
-To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow.
+要添加一个或多个查询套件，请在配置文件中添加 `queries` 部分。 如果查询在私有仓库中，请使用 `external-repository-token` 参数来指定可以访问私有仓库的令牌。
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     queries: COMMA-SEPARATED LIST OF PATHS
+    # Optional. 提供令牌来访问私有仓库.
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
-You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+您也可以在配置文件中指定额外查询套件以运行它们。 查询套件是查询的集合，通常按目的或语言分组。
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+如果还使用配置文件进行自定义设置，则将使用工作流程中指定的任何额外查询，而不是配置文件中指定的任何查询。 如果您要运行此处指定的额外查询与配置文件中指定的查询的组合，请在工作流程中的 `queries` 值之前加上前缀 `+` 符号。 有关配置文件的示例，请参阅“[配置文件示例](#example-configuration-files)”。
 
-In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file.
+在下面的示例中，`+` 符号可确保结合使用额外查询与所引用配置文件中指定的任何查询。
 
+{% raw %}
 ``` yaml
 - uses: github/codeql-action/init@v1
   with:
     config-file: ./.github/codeql/codeql-config.yml
     queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+    external-repository-token: ${{ secrets.ACCESS_TOKEN }}
 ```
+{% endraw %}
 
-### Using a custom configuration file
+### 使用第三方代码扫描工具
 
-As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis.
+除了在工作流程文件中指定要运行的查询之外，您还可以在单独的配置文件中执行此操作。 您还可以使用配置文件禁用默认查询，并指定分析过程中要扫描的目录。
 
-In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+在工作流程文件中，使用 `init` 操作的 `config-file` 参数指定要使用的配置文件的路径。 此示例加载配置文件 _./.github/codeql/codeql-config.yml_。
 
 ``` yaml
 - uses: github/codeql-action/init@v1
@@ -238,13 +245,23 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp
     config-file: ./.github/codeql/codeql-config.yml
 ```
 
-The configuration file can be located within the local repository, or in a remote, public repository. Using a remote, public repository allows you to specify configuration options for multiple repositories in a single place. When you reference a configuration file located in a remote repository, you can use the _OWNER/REPOSITORY/FILENAME@BRANCH_ syntax. For example, _monacorp/shared/codeql-config.yml@main_. 
+{% data reusables.code-scanning.custom-configuration-file %}
 
-The settings in the file are written in YAML format.
+如果配置文件位于外部私有仓库中，请使用 `init` 操作的 `external-repository-token` 参数来指定可以访问私有仓库的令牌。
 
-#### Specifying additional queries
+{% raw %}
+```yaml
+uses: github/codeql-action/init@v1
+with:
+  external-repository-token: ${{ secrets.ACCESS_TOKEN }}
+```
+{% endraw %}
 
-You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
+配置文件中的设置以 YAML 格式编写。
+
+#### 指定额外查询
+
+您可以在 `queries` 数组中指定额外查询。 数组的每个元素都包含一个 `uses` 参数，该参数的值标识单个查询文件、包含查询文件的目录或查询套件定义文件。
 
 ``` yaml
 queries:
@@ -253,17 +270,17 @@ queries:
   - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls
 ```
 
-Optionally, you can give each array element a name, as shown in the example configuration files below.
+（可选）您可以给每个数组元素一个名称，如下面的示例配置文件所示。
 
-For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
+有关额外查询的更多信息，请参阅上面的“[运行额外查询](#running-additional-queries)”。
 
-#### Disabling the default queries
+#### 禁用默认查询
 
-If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+如果只想运行自定义查询，您可以通过在配置文件中添加 `disable-default-queries: true` 来禁用默认安全查询。
 
-#### Specifying directories to scan
+#### 指定要扫描的目录
 
-For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
+对于 {% data variables.product.prodname_codeql %} 支持的解释语言（Python 和 JavaScript/TypeScript），您可以通过在配置文件中添加 `paths` 数组将 {% data variables.product.prodname_code_scanning %} 限制到特定目录中的文件。 添加 `paths-ignore` 数组可从分析排除特定目录中的文件。
 
 ``` yaml
 paths:
@@ -275,46 +292,28 @@ paths-ignore:
 
 {% note %}
 
-**Note**:
+**注**：
 
-* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
-* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+* 在 {% data variables.product.prodname_code_scanning %} 配置文件上下文中使用的 `paths` 和 `paths-ignore` 关键字，不应与用于工作流程中 `on.<push|pull_request>.paths` 的相同关键字相混淆。 当它们用于修改工作流程中的 `on.<push|pull_request>` 时，它们将决定在有人修改指定目录中的代码时是否运行操作。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` 字符只能用在行的开头或结尾，或用斜杠包围，并且不能将 `**` 与其他字符混合在一起。 例如，`foo/**`、`**/foo` 和 `foo/**/bar` 都是允许的语法，但 `**foo` 不是。 但是，可以将单星号与其他字符一起使用，如示例中所示。 您需要引用任何包含 `*` 字符的内容。
 
 {% endnote %}
 
-For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+对于编译的语言，如果要将 {% data variables.product.prodname_code_scanning %} 限制到项目中的特定目录，您必须在工作流程中指定适当的构建步骤。 用于在构建过程中排除目录的命令将取决于您的构建系统。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。
 
-You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow.
+在修改特定目录中的代码时，您可以快速分析单个仓库中的小部分。 您需要在构建步骤中排除目录并在工作流程文件中对 [`on.<push|pull_request>`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) 使用 `paths-ignore` 和 `paths` 关键字。
 
-#### Example configuration files
+#### 配置文件示例
 
 {% data reusables.code-scanning.example-configuration-files %}
 
-### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+### 为编译语言配置 {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
 
-{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)."
+{% data reusables.code-scanning.autobuild-add-build-steps %} 有关如何为编译语言配置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)”。
 
-### Accessing private repositories
+### 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %}
 
-If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs.<job_id>.steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
-
-For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable.
-
-{% raw %}
-```yaml
-steps:
-- name: Configure access to private repositories
-  env:
-    TOKEN: ${{ secrets.ACCESS_TOKEN }}
-  run: |
-    git config --global url."https://${TOKEN}@github.com/ghost/foo".insteadOf "https://github.com/ghost/foo"
-    git config --global url."https://${TOKEN}@github.com/ghost/bar".insteadOf "https://github.com/ghost/bar"
-    git config --global url."https://${TOKEN}@github.com/ghost/baz".insteadOf "https://github.com/ghost/baz"
-```
-{% endraw %}
-
-### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
-
-{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)."
+{% data variables.product.prodname_dotcom %} 可显示通过第三方工具在外部生成的代码分析数据。 通过在工作流程中添加 `upload-sarif` 操作，您可以在 {% data variables.product.prodname_dotcom %} 中显示第三方工具的代码分析。 更多信息请参阅“[将 SARIF 文件上传到 GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)”。
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
index 33bb286901..7506a3bd69 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -49,11 +51,11 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
 
 {% data variables.product.prodname_codeql_runner %} 自动检测并扫描用支持的语言编写的代码。
 
-{% data reusables.code-scanning.supported-languages %}
+{% data reusables.code-scanning.codeql-languages-bullets %}
 
 {% data reusables.code-scanning.specify-language-to-analyze %}
 
-要覆盖自动语言检测，请运行 `init` 命令：带 `--languages` 标志，后跟以逗号分隔的语言关键字列表。 受支持语言的关键字是 `cpp`、`csharp`、`go`、`java`、`javascript` 和 `python`。
+要覆盖自动语言检测，请运行 `init` 命令：带 `--languages` 标志，后跟以逗号分隔的语言关键字列表。 The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
 
 ```shell
 $ /path/to-runner/codeql-runner-linux init --languages cpp,java
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
index e6dd5a5057..43cc378716 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -31,11 +33,7 @@ topics:
 
 {% note %}
 
-{% if currentversion == "github-ae@latest" %} **注意**：有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。
-{% else %}
-**注意**：如果您将自托管运行器用于
-{% data variables.product.prodname_actions %}，您可能需要安装其他软件才能使用`自动构建`流程。 此外，如果您的仓库需要特定版本的构建工具，您可能需要手动安装它。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
-{% endif %}
+**注**：如果使用 {% data variables.product.prodname_actions %} 的自托管运行器，您可能需要安装其他软件才能使用 `autobuild` 进程。 此外，如果您的仓库需要特定版本的构建工具，您可能需要手动安装它。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
index deb6411f18..bdd9b6c21c 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md
@@ -8,6 +8,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 ### 目录
 
 {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
index 65b12aa674..8e086eb76b 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
index e309089df0..124d38a632 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
@@ -1,13 +1,15 @@
 ---
 title: 管理仓库的代码扫描警报
 shortTitle: 管理警报
-intro: '从安全视图中，您可以查看、修复、{% if currentVersion == "enterprise-server@2.22" %}或关闭{% else %}忽略或删除{% endif %}项目代码中潜在漏洞或错误的警报。'
+intro: 从安全的角度，您可以查看、修复或关闭项目代码中潜在漏洞或错误的警报。
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
 versions:
   enterprise-server: '2.22'
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于 {% data variables.product.prodname_code_scanning %} 中的警报
@@ -45,81 +47,25 @@ versions:
 
 任何对仓库具有写入权限的人都可以通过提交对代码的更正来修复警报。 如果仓库已安排对拉取请求运行 {% data variables.product.prodname_code_scanning %}，则最好通过拉取请求提交您的更正。 这将触发对更改的 {% data variables.product.prodname_code_scanning %} 分析，并测试您的修复是否会带来任何新的问题。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”和“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。
 
-如果您有仓库的写入权限，您可以通过查看警报摘要并单击 **Closed（已关闭）**来查看已修复的警报。 更多信息请参阅“[查看仓库的警报](#viewing-the-alerts-for-a-repository)”。 “Closed（已关闭）”列表显示已修复的警报和用户{% if currentVersion == "enterprise-server@2.22" %}已关闭{% else %}已忽略{% endif %}的警报。
+如果您有仓库的写入权限，您可以通过查看警报摘要并单击 **Closed（已关闭）**来查看已修复的警报。 更多信息请参阅“[查看仓库的警报](#viewing-the-alerts-for-a-repository)”。 “Closed（已关闭）”列表显示已修复的警报和用户已关闭的警报。
 
 警报只能在一个分支中修复。 您可以在警报摘要上使用“Branch（分支）”下拉菜单检查警报是否是在特定分支中修复的。
 
 ![按分支过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png)
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 ### 关闭警报
 
 关闭警报是解决您认为不需要修复的警报的一种方式。 {% data reusables.code-scanning.close-alert-examples %}
 
-{% else %}
-
-### 忽略或删除警报
-
-有两种方法可以关闭警报。 您可以修复代码中的问题，也可以忽略警报。 或者，如果您具有仓库的管理员权限，您可以删除警报。 删除警报适用于以下情况：您设置了 {% data variables.product.prodname_code_scanning %} 工具，然后决定删除它，或者您配置了 {% data variables.product.prodname_codeql %} 分析，但查询集超出您的需求，于是您从工具中删除了某些查询。 在这两种情况下，删除警报允许您清理 {% data variables.product.prodname_code_scanning %} 结果。 您可以在 **Security（安全）**选项卡中从摘要列表删除警报。
-
-忽略警报是关闭您认为不需要修复的警报的一种方式。 {% data reusables.code-scanning.close-alert-examples %} 您可以从代码中的 {% data variables.product.prodname_code_scanning %} 注释忽略警报，或者从 **Security（安全）**选项卡中的摘要列表忽略警报。
-
-当您忽略警报时：
-
-- 它在所有分支中被忽略。
-- 警报将从项目的当前警报数中删除。
-- 警报被移动到警报摘要中的“Closed（已关闭）”列表，需要时您可以在其中重新打开它。
-- 将记录您关闭警报的原因。
-- {% data variables.product.prodname_code_scanning %} 下次运行时，相同的代码将不会生成警报。
-
-当您删除警报时：
-
-- 它在所有分支中被删除。
-- 警报将从项目的当前警报数中删除。
-- 它_不会_添加到警报摘要中的“Closed（已关闭）”列表。
-- 如果生成警报的代码保持不变，并且相同的 {% data variables.product.prodname_code_scanning %} 工具在不更改任何配置的情况下再次运行，则该警报将再次显示在您的分析结果中。
-
-要忽略或删除警报：
-
-{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
-{% if currentVersion == "enterprise-server@2.22" %}
 {% data reusables.code-scanning.click-alert-in-list %}
 1. 选择 **Close（关闭）**下拉菜单，然后单击关闭警报的原因。    
    ![通过 Close（关闭）下拉菜单选择关闭警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
 
-{% else %}
-
-1. 如果您拥有仓库管理员权限，想要删除此 {% data variables.product.prodname_code_scanning %} 工具的警报，请选中部分或全部复选框，然后单击 **Delete（删除）**。
-
-   ![删除警报](/assets/images/help/repository/code-scanning-delete-alerts.png)
-
-   （可选）您可以使用过滤器显示警报子集，然后一次删除所有匹配的警报。 例如，如果您从 {% data variables.product.prodname_codeql %} 分析中删除了查询，您可以使用“Rule（规则）”过滤器仅列出该查询的警报，然后选择并删除所有这些警报。
-
-  ![按规则过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
-
-1. 如果要忽略警报，请务必先了解警报，以便选择正确的忽略原因。 单击要了解的警报。
-
-  ![从摘要列表中打开警报](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png)
-
-1. 查看警报，然后单击 **Dismiss（忽略）**并选择关闭警报的原因。 ![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-   {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-#### 一次忽略多个警报
-
-如果项目有多个由于相同原因要忽略的警报，您可以从警报摘要中批量忽略它们。 通常，您需要过滤列表，然后忽略所有匹配的警报。 例如，您可能想要忽略项目中所有已标记为特定通用缺陷枚举 (CWE) 漏洞的当前警报。
-
-{% endif %}
-
 ### 延伸阅读
 
 - “[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
index 02308deb91..49881d6910 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于使用容器化构建的 {% data variables.product.prodname_code_scanning %}
@@ -43,7 +45,10 @@ on:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest 
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write
+      actions: read{% endif %}
 
     strategy:
       fail-fast: false
@@ -55,16 +60,16 @@ jobs:
       image: codeql-container:f0f91db
 
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
-      with:
-        languages: {% raw %}${{ matrix.language }}{% endraw %}
-    - name: Build
-      run: |
-        ./configure
-        make
-    - name: Perform {% data variables.product.prodname_codeql %} Analysis
-      uses: github/codeql-action/analyze@v1
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: github/codeql-action/analyze@v1
 ```
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
index 0e7c2076ef..356950afd0 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
 <!--UI-LINK: When GitHub Enterprise Server doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% data reusables.code-scanning.beta-codeql-runner %}
@@ -30,17 +31,13 @@ topics:
 {% note %}
 
 **注意：**
-{% if currentVersion == "free-pro-team@latest" %}
-* {% data variables.product.prodname_codeql_runner %} 使用 {% data variables.product.prodname_codeql %} CLI 来分析代码，因此具有相同的许可条件。 它可自由用于 {% data variables.product.prodname_dotcom_the_website %} 上维护的公共仓库，并且可用于具有 {% data variables.product.prodname_advanced_security %} 许可证的客户所拥有的私有仓库。 有关信息请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”和“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
-{% else %}
 * {% data variables.product.prodname_codeql_runner %} 可用于拥有 {% data variables.product.prodname_advanced_security %} 许可证的客户。
-{% endif %}
 * 请勿将 {% data variables.product.prodname_codeql_runner %} 与 {% data variables.product.prodname_codeql %} CLI 混淆。 {% data variables.product.prodname_codeql %} CLI 是一个交互式命令行接口，允许您创建用于安全研究的 {% data variables.product.prodname_codeql %} 数据库并运行 {% data variables.product.prodname_codeql %} 查询。 更多信息请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。
 {% endnote %}
 
 ### 下载 {% data variables.product.prodname_codeql_runner %}
 
-您可以从 https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases 下载 {% data variables.product.prodname_codeql_runner %} 。 在某些操作系统上，您可能需要更改下载文件的权限才能运行它。
+您可以从 https://github.com/github/codeql-action/releases 下载 {% data variables.product.prodname_codeql_runner %}。 在某些操作系统上，您可能需要更改下载文件的权限才能运行它。
 
 在 Linux 上：
 
@@ -62,7 +59,7 @@ You should call the {% data variables.product.prodname_codeql_runner %} from the
 下载 {% data variables.product.prodname_codeql_runner %} 并确认它可执行后，应将运行器提供给您打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 例如，您可以配置每台服务器从中央内部位置复制运行器。 或者，您也可以使用 REST API 直接从 {% data variables.product.prodname_dotcom %} 获取运行器，例如：
 
 ```shell
-wget https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
 chmod +x codeql-runner-linux
 ```
 
@@ -73,9 +70,8 @@ chmod +x codeql-runner-linux
 
 提供 {% data variables.product.prodname_codeql %} 包访问权限的选项：
 
-1. 允许 CI 服务器访问 https://{% if currentVersion == "enterprise-server@2.22" or currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} 可以自动下载捆绑包。
-{% if currentVersion == "enterprise-server@2.22" %}
-1. 在 {% data variables.product.product_name %} 上镜像 `github/codeql-action` 仓库。 除非您指定 <nobr>`--codeql-path`</nobr> 标志，否则运行器将在此位置和 {% data variables.product.prodname_dotcom_the_website %}上自动检查包。{% endif %}
+1. 允许 CI 服务器访问 https://github.com/github/codeql-action，以便 {% data variables.product.prodname_codeql_runner %} 可以自动下载包。
+1. 在 {% data variables.product.product_name %} 上镜像 `github/codeql-action` 仓库。 除非您指定 <nobr>`--codeql-path`</nobr> 标志，否则运行器将在此位置和 {% data variables.product.prodname_dotcom_the_website %}上自动检查包。
 1. 手动下载/提取捆绑包，将其与其他中央资源一起存储，并使用 <nobr>`--codeql-path`</nobr> 标记指定捆绑包在调用中的位置，以初始化 {% data variables.product.prodname_codeql_runner %}。
 
 ### 调用 {% data variables.product.prodname_codeql_runner %}
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
index f6ac8bb839..af9273295d 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于 SARIF 支持
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
index 4ab4b97f3f..1697280c90 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
@@ -21,12 +23,10 @@ topics:
 
 ### 使用操作设置 {% data variables.product.prodname_code_scanning %}
 
-{% if currentVersion == "free-pro-team@latest" %}使用操作运行 {% data variables.product.prodname_code_scanning %} 需时数分钟。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).”{% endif %}
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
-4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 2" %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %}
+3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with code scanning" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)
 5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
 
    一般来说，您可以提交 {% data variables.product.prodname_codeql_workflow %} 而不对其做任何更改。 但是，许多第三方工作流程需要额外的配置，因此在提交之前请阅读工作流程中的注释。
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
index f378117504..35b591ac74 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md
@@ -10,13 +10,15 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 
 ### 关于拉取请求上的 {% data variables.product.prodname_code_scanning %} 结果
 
 在仓库中，如果 {% data variables.product.prodname_code_scanning %} 被配置为拉取请求检查，则 {% data variables.product.prodname_code_scanning %} 将检查拉取请求中的代码。 默认情况下，这仅限于针对默认分支的拉取请求，但是您可以在 {% data variables.product.prodname_actions %} 或第三方 CI/CD 系统中更改此配置。 如果合并分支给目标分支带来新的 {% data variables.product.prodname_code_scanning %} 警报，这些警报将在拉取请求中被报告为检查结果。 警报还将在拉取请求的 **Files changed（文件已更改）**选项卡中显示为注释。 如果您拥有仓库的写入权限，您可以在 **Security（安全）**选项卡中查看任何现有的 {% data variables.product.prodname_code_scanning %} 警报。 有关仓库警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。
 
-如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 如果拉取请求针对使用 {% data variables.product.prodname_code_scanning %} 的受保护分支，并且仓库所有者配置了必需状态检查，则您必须修复或{% if currentVersion == "enterprise-server@2.22" %}关闭{% else %}忽略{% endif %}所有错误警报，然后才能合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。
+如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 如果拉取请求针对使用 {% data variables.product.prodname_code_scanning %} 的受保护分支，并且仓库所有者配置了必需状态检查，则您必须修复或关闭所有错误警报，然后才能合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。
 
 ![拉取请求上失败的 {% data variables.product.prodname_code_scanning %} 检查](/assets/images/help/repository/code-scanning-check-failure.png)
 
@@ -40,28 +42,10 @@ topics:
 
 ![显示更多信息的警报说明和链接](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-### {% if currentVersion == "enterprise-server@2.22" %}解决{% else %}修复{% endif %}拉取请求上的警报
+### 解决关于拉取请求的警报
 
 任何对拉取请求具有推送权限的人都可以修复在该拉取请求上已识别的 {% data variables.product.prodname_code_scanning %} 警报。 如果将更改提交到拉取请求，这将触发拉取请求检查的新运行。 如果您的更改修复了问题，则警报将被关闭，注释将被删除。
 
-{% if currentVersion == "enterprise-server@2.22" %}
-
 如果您认为警报不需要修复，则具有写入权限的用户可以手动关闭警报。 {% data reusables.code-scanning.close-alert-examples %} 如果您对仓库有写入权限，则 **Close（关闭）**按钮在注释和警报视图中可用。
 
 {% data reusables.code-scanning.false-positive-fix-codeql %}
-
-{% else %}
-
-### 忽略拉取请求上的警报
-
-关闭警报的另一种办法是忽略它。 您可以忽略您认为不需要修复的警报。 {% data reusables.code-scanning.close-alert-examples %} 如果您对仓库有写入权限，则 **Dismiss（忽略）**按钮在代码注释和警报摘要中可用。 单击 **Dismiss（忽略）**时，您将被提示选择关闭警报的原因。
-
-![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
-
-{% data reusables.code-scanning.choose-alert-dismissal-reason %}
-
-{% data reusables.code-scanning.false-positive-fix-codeql %}
-
-有关忽略警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。
-
-{% endif %}
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
index 65e79ea709..548c101cff 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system.md
@@ -9,6 +9,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta-codeql-runner %}
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
index 1ace4a373a..5e58843666 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md
@@ -1,32 +1,39 @@
 ---
-title: Troubleshooting the CodeQL workflow
-shortTitle: Troubleshooting CodeQL
-intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.'
+title: CodeQL 工作流程疑难解答
+shortTitle: CodeQL 疑难解答
+intro: '如果您在 {% data variables.product.prodname_code_scanning %} 方面遇到问题，可使用这些提示来解决问题。'
 product: '{% data reusables.gated-features.code-scanning %}'
-redirect_from:
-  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning
 versions:
   enterprise-server: '2.22'
 topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.not-available %}
 
-### Automatic build for a compiled language fails
+### 生成详细的调试日志
 
-If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps.
+要生成更详细的日志输出，您可以启用步骤调试日志记录。 更多信息请参阅“[启用调试日志记录](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)”。
 
-- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+### 编译语言的自动构建失败
 
-- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. 
+如果项目中编译语言的代码自动构建失败，请尝试以下疑难解答步骤。
 
-  The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
+- 从 {% data variables.product.prodname_code_scanning %} 工作流程中删除 `autobuild` 步骤，并添加特定构建步骤。 有关编辑工作流程的信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)”。 有关替换 `autobuild` 步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。
+
+- 如果您的工作流程未明确指定要分析的语言，则 {% data variables.product.prodname_codeql %} 会隐式检测代码库中支持的语言。 在此配置中，对于编译语言 C/C++、C# 和 Java，{% data variables.product.prodname_codeql %} 只分析涵盖最多源文件的语言。 编辑工作流程并添加一个构建矩阵，以指定要分析的语言。 默认的 CodeQL 分析工作流程使用这种矩阵。
+
+  以下工作流程摘录显示了如何在作业策略中使用矩阵来指定语言，然后在“初始化 {% data variables.product.prodname_codeql %}”步骤中引用每种语言：
 
   ```yaml
   jobs:
-    analyze:
+    analyze:{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions:
+        security-events: write
+        actions: read{% endif %}
       ...
       strategy:
         fail-fast: false
@@ -40,14 +47,14 @@ If an automatic build of code for a compiled language within your project fails,
         with:
           languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
-   
-  For more information about editing the workflow, see "[Configuring code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
 
-### No code found during the build
+  有关编辑工作流程的更多信息，请参阅“[配置代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”。
 
-If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure:
+### 构建过程中找不到代码
 
-1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. For example, the following configuration will analyze only Go, and JavaScript.
+如果工作流程失败，出现错误 `No source code was seen during the build` 或 `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`，则表明 {% data variables.product.prodname_codeql %} 无法监控您的代码。 有几个原因可以解释这种失败：
+
+1. 自动语言检测发现了受支持的语言，但仓库中没有该语言的可分析代码。 一个典型的例子是，我们的语言检测服务发现了一个与特定的编程语言相关的文件，例如 `.h` 或 `.gyp` 文件，但仓库中没有相应的可执行代码。 要解决此问题，您可以通过更新 `language` 矩阵中的语言列表来手动定义要分析的语言。 例如，以下配置将仅分析 Go 和 JavaScript。
 
   ```yaml
   strategy:
@@ -58,81 +65,70 @@ If your workflow fails with an error `No source code was seen during the build`
       # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python']
       language: ['go', 'javascript']
   ```
-For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
-1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually.  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. 
-1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. 
-1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are:
+更多信息请参阅上面“[编译语言的自动构建失败](#automatic-build-for-a-compiled-language-fails)”中的工作流程摘要。
+1. {% data variables.product.prodname_code_scanning %} 工作流程在分析一种已编译的语言（C、C++、C# 或 Java），但代码尚未编译。 默认情况下，{% data variables.product.prodname_codeql %} 分析工作流程包含 `autobuild` 步骤，但是，此步骤是一个尽力而为的过程，可能无法成功构建您的代码，具体取决于您的特定构建环境。 如果您删除了 `autobuild` 步骤但没有手动添加构建步骤，编译也可能会失败。  有关指定构建步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。
+1. 工作流程在分析一种编译语言（C、C++、C# 或 Java），但构建的一部分被缓存以提高性能（最有可能发生在 Gradle 或 Bazel 等构建系统中）。 因为 {% data variables.product.prodname_codeql %} 观察编译器的活动以了解仓库中的数据流，因此 {% data variables.product.prodname_codeql %} 需要进行完整的构建才能执行分析。
+1. 工作流程在分析编译语言（C、C++、C# 或 Java），但工作流程中的 `init` 与 `analyze` 步骤之间不发生编译。 {% data variables.product.prodname_codeql %} 需要这两个步骤之间发生构建以观察编译器的活动并执行分析。
+1. 您的编译代码（使用 C、C ++、C＃ 或 Java）已成功编译，但 {% data variables.product.prodname_codeql %} 无法检测到编译器调用。 最常见的原因是：
 
-   * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)."
-   * Building using a distributed build system external to GitHub Actions, using a daemon process.
-   * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
+   * 在独立于 {% data variables.product.prodname_codeql %} 的容器中运行构建过程。 更多信息请参阅“[在容器中运行 CodeQL 代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)”。
+   * 使用 GitHub Actions 外部的分布式构建系统，使用守护进程构建。
+   * {% data variables.product.prodname_codeql %} 不知道您使用的特定编译器。
 
-  For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later.
-  
-  For example, the following configuration for C# will pass the flag during the first build step.
+  对于 .NET Framework 项目以及使用 `dotnet build` 或 `msbuild`（目标 .NET Core 2）的 C# 项目，在构建代码时，您应该在工作流程的 `run` 步骤中指定 `/p:UseSharedCompilation=false`。 .NET Core 3.0 及更高版本不需要 `UseSharedCompilation` 标志。
+
+  例如，以下 C# 的配置将在第一个构建步骤中传递标志。
 
    ``` yaml
    - run: |
        dotnet build /p:UseSharedCompilation=false 
    ```
 
-  If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
+  如果您在特定编译器或配置方面遇到其他问题，请联系 {% data variables.contact.contact_support %}。
 
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." 
+有关指定构建步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。
 
-### Portions of my repository were not analyzed using `autobuild`
+### 我的仓库中有部分内容未使用 `autobuild` 进行分析
 
-The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+{% data variables.product.prodname_codeql %} `autobuild` 功能使用启发式方法在仓库中构建代码，但有时这种方法会导致对仓库的分析不完整。 例如，当单个仓库中存在多个 `build.sh` 命令时，分析可能不完整，因为 `autobuild` 步骤将只执行其中一个命令。 解决方案是将 `autobuild` 步骤替换为可构建要分析的所有源代码的构建步骤。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。
 
-### The build takes too long
+### 构建耗时过长
 
-If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. 
+如果使用 {% data variables.product.prodname_codeql %} 分析进行的构建花费的时间太长，则可以尝试几种方法来减少构建时间。
 
-#### Increase the memory or cores
-
-If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners.
-
-#### Use matrix builds to parallelize the analysis
-
-The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
-
-#### Reduce the amount of code being analyzed in a single workflow
+#### 增加内存或内核
 
 Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time.
 
-For compiled languages like Java, C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build only the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)."
+#### 使用矩阵构建来并行化分析
 
-For interpreted languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without a specific build, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)."
+默认 {% data variables.product.prodname_codeql_workflow %} 使用语言的构建矩阵，这会导致每种语言的分析并行运行。 如果在“初始化 CodeQL”步骤中指定了要直接分析的语言，则将依次进行每种语言的分析。 要加快对多种语言的分析，请修改工作流程以使用矩阵。 更多信息请参阅上面“[编译语言的自动构建失败](#automatic-build-for-a-compiled-language-fails)”中的工作流程摘要。
 
-If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build. 
+#### 减少单个工作流程中要分析的代码量
 
-#### Run only during a `schedule` event
+分析时间通常与要分析的代码量成正比。 您可以通过减少一次分析的代码量来缩短分析时间，例如，排除测试代码，或将分析分解为多个工作流程，这些工作流程一次只分析一部分代码。
 
-If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
+对于 Java、C、C++ 和 C# 等编译语言，{% data variables.product.prodname_codeql %} 分析在工作流程运行过程中构建的所有代码。 要限制要分析的代码量，请通过在 `run` 块中指定自己的构建步骤，仅构建您要分析的代码。 您可以通过对 `pull_request` 和 `push` 事件使用 `paths` 或 `paths-ignore` 过滤器来组合指定自己的构建步骤，以确保工作流程仅在特定代码发生更改时运行。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Results differ between analysis platforms
+对于 Go、JavaScript、Python 和 TypeScript 等解释性语言，{% data variables.product.prodname_codeql %} 无需特定构建即可进行分析，您可以指定额外配置选项以限制要分析的代码量。 更多信息请参阅“[指定要扫描的目录](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)”。
 
-If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
+如果您按上文所述将分析拆分为多个工作流程，我们仍然建议您至少保留一个按 `schedule` 运行的工作流程分析仓库中的所有代码。 因为 {% data variables.product.prodname_codeql %} 分析组件之间的数据流量，所以某些复杂的安全行为只能在完整的构建中检测到。
 
-On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)."
+#### 仅在 `schedule` 事件期间运行
 
-{% endif %}
+如果分析速度仍然太慢，无法在 `push` 或 `pull_request` 事件期间运行，则您可能需要设置仅在 `schedule` 事件期间运行。 更多信息请参阅“[事件](/actions/learn-github-actions/introduction-to-github-actions#events)”。
 
-### Error: "Server error"
+### 错误：“Server error（服务器错误）”
 
-If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
+如果 {% data variables.product.prodname_code_scanning %} 的工作流程运行因服务器错误而失败，请尝试再次运行工作流程。 如果问题仍然存在，请联系 {% data variables.contact.contact_support %}。
 
-### Error: "Out of disk" or "Out of memory"
+### 错误：“Out of disk（磁盘空间不足）”或“Out of memory（内存不足）”
 
-On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
-{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the hosted {% data variables.product.prodname_actions %} runner. If you encounter this issue, contact {% data variables.contact.contact_support %} so that we can investigate the problem. 如果您遇到此问题，请尝试增加运行器的内存。
 
-### Warning: "git checkout HEAD^2 is no longer necessary"
+### 警告：“git checkout HEAD^2 is no longer necessary（不再需要 Git 检出头^2）”
 
-If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action:
+如果您使用的是旧 {% data variables.product.prodname_codeql %} 工作流程，您可能会在输出中收到来自“初始化 {% data variables.product.prodname_codeql %}”操作的以下警告：
 
 ```
 Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer 
@@ -140,32 +136,32 @@ necessary. Please remove this step as Code Scanning recommends analyzing the mer
 commit for best results.
 ```
 
-Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
+通过从 {% data variables.product.prodname_codeql %} 工作流程中删除以下行来修复此问题。 这些行包含在 {% data variables.product.prodname_codeql %} 工作流程初始版本中 `Analyze` 作业的 `steps` 部分。
 
 ```yaml
-      with:
-        # We must fetch at least the immediate parents so that if this is
-        # a pull request then we can checkout the head.
-        fetch-depth: 2
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
 
-    # If this run was triggered by a pull request event, then checkout
-    # the head of the pull request instead of the merge commit.
-    - run: git checkout HEAD^2
-      if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
-```      
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+```
 
-The revised `steps` section of the workflow will look like this:
+修订后的工作流程 `steps` 部分将如下所示：
 
 ```yaml
     steps:
-    - name: Checkout repository
-      uses: actions/checkout@v2
+      - name: Checkout repository
+        uses: actions/checkout@v2
 
-    # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
-    - name: Initialize {% data variables.product.prodname_codeql %}
-      uses: github/codeql-action/init@v1
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: github/codeql-action/init@v1
 
-    ...
+      ...
 ```
 
-For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)."
+有关编辑 {% data variables.product.prodname_codeql %} 工作流程文件的更多信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)”。
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
index e861848033..d219c55e1a 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md
@@ -10,6 +10,8 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
+
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
@@ -19,7 +21,7 @@ topics:
 
 您可以使用许多静态分析安全测试工具来生成 SARIF 文件，包括 {% data variables.product.prodname_codeql %}。 结果必须使用 SARIF 版本 2.1.0。 更多信息请参阅“[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)”。
 
-您可以使用 {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} （如果您的组织正在参与测试计划，则可以使用）{% endif %}、{% data variables.product.prodname_code_scanning %} API 或 {% data variables.product.prodname_codeql_runner %} 上传结果。 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用：
+您可以使用 {% data variables.product.prodname_actions %}（如果您的组织正在参与测试计划，则可以使用）、{% data variables.product.prodname_code_scanning %} API 或 {% data variables.product.prodname_codeql_runner %} 上传结果。 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用：
 
 - {% data variables.product.prodname_actions %} 来运行 {% data variables.product.prodname_codeql %} 操作，则无需进一步操作。 {% data variables.product.prodname_codeql %} 操作在完成分析后自动上传 SARIF 文件。
 - "[管理工作流程运行](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)"
@@ -58,20 +60,22 @@ name: "Upload SARIF"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 5'
+    - cron: '45 15 * * 5'
 
 jobs:
   build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    # This step checks out a copy of your repository.
-    - name: Checkout repository
-      uses: actions/checkout@v2
-    - name: Upload SARIF file
-      uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - name: Upload SARIF file
+        uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 #### 运行 ESLint 分析工具的示例工作流程
@@ -82,7 +86,7 @@ jobs:
 
 工作流程显示了将 ESLint 静态分析工具作为工作流程中一个步骤运行的示例。 `Run ESLint` 步骤运行 ESLint 工具，输出 `results.sarif` 文件。 然后，工作流程使用 `upload-sarif` 操作将 `results.sarif` 文件上传到 {% data variables.product.prodname_dotcom %}。 有关创建工作流程文件的更多信息，请参阅“[GitHub Actions 简介](/actions/learn-github-actions/introduction-to-github-actions)”。
 
-```yml
+```yaml
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
@@ -90,23 +94,26 @@ name: "ESLint analysis"
 on:
   push:
   schedule:
-  - cron: '45 15 * * 1'
+    - cron: '45 15 * * 1'
 
 jobs:
   build:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      security-events: write{% endif %}
     steps:
-    - uses: actions/checkout@v2
-    - name: Run npm install
-      run: npm install
-    # Runs the ESlint code analysis
-    - name: Run ESLint
-      # eslint exits 1 if it finds anything to report
-      run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
-    # Uploads results.sarif to GitHub repository using the upload-sarif action
-    - uses: github/codeql-action/upload-sarif@v1
-      with:
-        # Path to SARIF file relative to the root of the repository
-        sarif_file: results.sarif
+      - uses: actions/checkout@v2
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: github/codeql-action/upload-sarif@v1
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
 ```
 
 ### 延伸阅读
diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
index 7534ea39ee..d9697e27d0 100644
--- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
+++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system.md
@@ -10,3 +10,4 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/secure-coding for the latest version of this article -->
diff --git a/translations/zh-CN/content/github/getting-started-with-github/about-git-subtree-merges.md b/translations/zh-CN/content/github/getting-started-with-github/about-git-subtree-merges.md
index c29a255921..ac7508c1df 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/about-git-subtree-merges.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/about-git-subtree-merges.md
@@ -12,6 +12,8 @@ versions:
   github-ae: '*'
 ---
 
+### About subtree merges
+
 通常，子树合并用于在仓库中包含仓库。 “子仓库”存储在主仓库的文件夹中。
 
 解释子树合并的最佳方式是举例说明。 我们将：
diff --git a/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md b/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md
index e7ec13e326..fca2bf4f57 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/about-github-advanced-security.md
@@ -38,7 +38,7 @@ topics:
 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_advanced_security %}，您才能使用这些功能。 更多信息请参阅“[配置高级安全功能](/admin/configuration/configuring-advanced-security-features)”。
 {% endif %}
 
-设置系统后，您可以在组织或仓库级别启用和禁用这些功能。 For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+设置系统后，您可以在组织或仓库级别启用和禁用这些功能。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。
 
 {% endif %}
 
@@ -47,7 +47,7 @@ topics:
 
 对于 {% data variables.product.prodname_dotcom_the_website %} 上的公共仓库，这些功能是永久性的，仅当您更改项目的可见性使代码不再公开时才会禁用。
 
-对于其他仓库，一旦您拥有企业帐户的许可，就可以在组织或仓库级别启用和禁用这些功能。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+对于其他仓库，一旦您拥有企业帐户的许可，就可以在组织或仓库级别启用和禁用这些功能。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %}
 
 {% endif %}
 
diff --git a/translations/zh-CN/content/github/getting-started-with-github/be-social.md b/translations/zh-CN/content/github/getting-started-with-github/be-social.md
index 3c1076d1b0..62b75934c5 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/be-social.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/be-social.md
@@ -38,6 +38,10 @@ topics:
 
 {% data reusables.support.ask-and-answer-forum %}
 
+### Communicating on {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
+
 ### 更多功能
 
 #### 创建拉取请求
@@ -68,8 +72,8 @@ topics:
 
 ![用星号标记项目](/assets/images/help/stars/star-a-project.png)
 
-- [设置 Git](/articles/set-up-git)
-- [创建仓库](/articles/create-a-repo)
-- [复刻仓库](/articles/fork-a-repo)
+- “[设置 Git](/articles/set-up-git)”
+- “[创建仓库](/articles/create-a-repo)”
+- “[复刻仓库](/articles/fork-a-repo)”
 - **社交化**
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/zh-CN/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md b/translations/zh-CN/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
index 73a0274d9d..529e567ce9 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/configuring-git-to-handle-line-endings.md
@@ -15,7 +15,7 @@ versions:
 
 每次按键盘上的 <kbd>return</kbd> 时，会插入一个称为行结束符的不可见字符。 不同的操作系统处理行结束符的方式不同。
 
-在使用 Git 和 {% data variables.product.product_name %} 协作处理项目时，Git 可能产生意外结果，例如，您在 Windows 计算机上操作，而您的协作者是在 OS X 中做的更改。
+When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
 
 您可以将 Git 配置为自动处理行结束符，以便与使用不同操作系统的人员有效地协作。
 
@@ -25,11 +25,11 @@ versions:
 
 {% mac %}
 
-在 OS X 上，只需将 `input（输入）`传递给配置。 例如：
+On macOS, you simply pass `input` to the configuration. 例如：
 
 ```shell
 $ git config --global core.autocrlf input
-# Configure Git to ensure line endings in files you checkout are correct for OS X
+# Configure Git to ensure line endings in files you checkout are correct for macOS
 ```
 
 {% endmac %}
diff --git a/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md b/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md
index f6b3eda8f4..0201fd956c 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md
@@ -15,6 +15,8 @@ topics:
   - Accounts
 ---
 
+### 创建仓库
+
 {% if currentVersion == "free-pro-team@latest" %}
 
 您可以在 {% data variables.product.product_name %} 仓库中存储各种项目，包括开源项目。 通过[开源项目](http://opensource.org/about)，您可以共享代码以开发更好、更可靠的软件。
@@ -29,7 +31,7 @@ topics:
 
 {% note %}
 
-**注：**您可以为开源项目创建公共仓库。 创建公共仓库时，请确保包含[许可文件](http://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
+**注：**您可以为开源项目创建公共仓库。 创建公共仓库时，请确保包含[许可文件](https://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md b/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md
index 291174a97b..cf18b40c29 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md
@@ -16,6 +16,8 @@ topics:
   - Accounts
 ---
 
+### 关于复刻
+
 复刻最常见的用法是对其他人的项目提出更改或将其他人的项目用作自己创意的起点。
 
 #### 对其他人的项目提出更改
@@ -34,7 +36,7 @@ topics:
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-从其他人的项目复刻创建公共仓库时，请确保包含许可文件以确定您希望与其他人共享项目。 更多信息请参阅 choosealicense.com 上的“[选择开源许可](http://choosealicense.com/)”。
+从其他人的项目复刻创建公共仓库时，请确保包含许可文件以确定您希望与其他人共享项目。 更多信息请参阅 choosealicense.com 上的“[选择开源许可](https://choosealicense.com/)”。
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
@@ -154,5 +156,6 @@ topics:
 
 - “[设置 Git](/articles/set-up-git)”
 - “[创建仓库](/articles/create-a-repo)”
+- **复刻仓库**
 - “[社交化](/articles/be-social)”
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/zh-CN/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md b/translations/zh-CN/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
index 85c4011fcf..7737f3fef2 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/getting-changes-from-a-remote-repository.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Options for getting changes
+
 与[远程仓库](/github/getting-started-with-github/about-remote-repositories)交互时，这些命令非常有用。 `clone` 和 `fetch` 用于从仓库的远程 URL 将远程代码下载到您的本地计算机，`merge` 用于将其他人的工作与您的工作合并在一起，而 `pull` 是 `fetch` 和 `merge` 的组合。
 
 ### 克隆仓库
diff --git a/translations/zh-CN/content/github/getting-started-with-github/git-workflows.md b/translations/zh-CN/content/github/getting-started-with-github/git-workflows.md
index b765d11dcd..28d97afc22 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/git-workflows.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/git-workflows.md
@@ -11,4 +11,4 @@ versions:
   github-ae: '*'
 ---
 
-您可以采用 {% data variables.product.prodname_dotcom %} 流方法标准化 {% data variables.product.prodname_dotcom %} 上团队的运作和协作方式。 更多信息请参阅 {% data variables.product.prodname_dotcom %} 指南中的“[GitHub 流](/github/collaborating-with-issues-and-pull-requests/github-flow)”和“[了解 GitHub 流](http://guides.github.com/overviews/flow/)”。
+您可以采用 {% data variables.product.prodname_dotcom %} 流方法标准化 {% data variables.product.prodname_dotcom %} 上团队的运作和协作方式。 For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
diff --git a/translations/zh-CN/content/github/getting-started-with-github/github-flow.md b/translations/zh-CN/content/github/getting-started-with-github/github-flow.md
new file mode 100644
index 0000000000..c2c7797bea
--- /dev/null
+++ b/translations/zh-CN/content/github/getting-started-with-github/github-flow.md
@@ -0,0 +1,99 @@
+---
+title: GitHub 流程
+intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository/
+  - /articles/github-flow-in-the-browser/
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+versions:
+  free-pro-team: '*'
+  enterprise-server: '*'
+  github-ae: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 4
+---
+
+### 简介
+
+{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
+
+### 基本要求
+
+To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% if currentVersion == "free-pro-team@latest" %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+
+### Following {% data variables.product.prodname_dotcom %} flow
+
+{% tip %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface, command line and [{% data variables.product.prodname_cli %}](https://cli.github.com), or [{% data variables.product.prodname_desktop %}](/desktop).
+{% else %}
+**Tip:** You can complete all steps of {% data variables.product.prodname_dotcom %} flow through {% data variables.product.prodname_dotcom %} web interface or through the command line and [{% data variables.product.prodname_cli %}](https://cli.github.com).
+{% endif %}
+
+{% endtip %}
+
+#### Create a branch
+
+  Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. 更多信息请参阅“[创建和删除仓库中的分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)”。
+
+  By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
+
+#### Make changes
+
+On your branch, make any desired changes to the repository. For more information, see "[Creating new files](/articles/creating-new-files)," "[Editing files](/articles/editing-files)," "[Renaming a file](/articles/renaming-a-file)," "[Moving a file to a new location](/articles/moving-a-file-to-a-new-location)," or "[Deleting files in a repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository)."
+
+Your branch is a safe place to make changes. If you make a mistake, you can revert your changes or push additional changes to fix the mistake. Your changes will not end up on the default branch until you merge your branch.
+
+Commit and push your changes to your branch. Give each commit a descriptive message to help you and future contributors understand what changes the commit contains. For example, `fix typo` or `increase rate limit`.
+
+Ideally, each commit contains an isolated, complete change. This makes it easy to revert your changes if you decide to take a different approach. For example, if you want to rename a variable and add some tests, put the variable rename in one commit and the tests in another commit. Later, if you want to keep the tests but revert the variable rename, you can revert the specific commit that contained the variable rename. If you put the variable rename and tests in the same commit or spread the variable rename across multiple commits, you would spend more effort reverting your changes.
+
+By committing and pushing your changes, you back up your work to remote storage. This means that you can access your work from any device. It also means that your collaborators can see your work, answer questions, and make suggestions or contributions.
+
+Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+
+{% tip %}
+
+**Tip:** Make a separate branch for each set of unrelated changes. This makes it easier for reviewers to give feedback. It also makes it easier for you and future collaborators to understand the changes and to revert or build on them. Additionally, if there is a delay in one set of changes, your other changes aren't also delayed.
+
+{% endtip %}
+
+#### 创建拉取请求
+
+Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. 更多信息请参阅“[创建拉取请求](/articles/creating-a-pull-request)”。
+
+When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
+
+![pull request body](../../../assets/images/help/pull_requests/pull-request-body.png)
+
+In addition to filling out the body of the pull request, you can add comments to specific lines of the pull request to explicitly point something out to the reviewers.
+
+![pull request comment](../../../assets/images/help/pull_requests/pull-request-comment.png)
+
+Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
+
+If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. 更多信息请参阅“[关于状态检查](/github/collaborating-with-issues-and-pull-requests/about-status-checks)”。
+
+#### Address review comments
+
+Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
+
+You can continue to commit and push changes in response to the reviews. 您的拉取请求将自动更新。
+
+#### Merge your pull request
+
+Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. 更多信息请参阅“[合并拉取请求](/articles/merging-a-pull-request)”。
+
+{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. 更多信息请参阅“[解决合并冲突](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)”。
+
+Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。
+
+#### Delete your branch
+
+After you merge your pull request, delete your branch. This indicates that the work on the branch is complete and prevents you or others from accidentally using old branches. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)."
+
+Don't worry about losing information. Your pull request and commit history will not be deleted. You can always restore your deleted branch or revert your pull request if needed.
diff --git a/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md b/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md
index cc545b33c0..86ca180fbf 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md
@@ -40,7 +40,7 @@ topics:
 
 您必须在设备上安装 {% data variables.product.prodname_mobile %} 1.4 或更高版本，才能使用 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}。
 
-要使用 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}，{% data variables.product.product_location %} 必须为 3.0 或更高版本，并且企业所有者必须为企业启用移动版支持。 更多信息请参阅“[发行说明](/enterprise-server/admin/release-notes)”和“[管理企业的 {% data variables.product.prodname_mobile %}](/admin/configuration/managing-github-for-mobile-for-your-enterprise)”。
+要使用 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}，{% data variables.product.product_location %} 必须为 3.0 或更高版本，并且企业所有者必须为企业启用移动版支持。 For more information, see {% if enterpriseServerVersions contains currentVersion %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/managing-github-for-mobile-for-your-enterprise)."
 
 在 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %} 测试期间，您必须使用 {% data variables.product.prodname_dotcom_the_website %} 上的用户帐户登录。
 
diff --git a/translations/zh-CN/content/github/getting-started-with-github/github-language-support.md b/translations/zh-CN/content/github/getting-started-with-github/github-language-support.md
new file mode 100644
index 0000000000..529b989ad6
--- /dev/null
+++ b/translations/zh-CN/content/github/getting-started-with-github/github-language-support.md
@@ -0,0 +1,39 @@
+---
+title: GitHub language support
+intro: 'An overview of the programming languages supported by {% data variables.product.prodname_dotcom %} features.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+topics:
+  - GitHub
+---
+
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+### About supported languages
+
+Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[Searching code](/github/searching-for-information-on-github/searching-code#search-by-language)" or "[Creating and highlighting code blocks](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)."
+
+Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.
+
+### Core languages supported by {% data variables.product.prodname_dotcom %} features
+
+Core languages for {% data variables.product.prodname_dotcom %} features include C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and TypeScript. For features that support package managers, the currently supported package managers are included in the table with their relevant languages.
+
+Some features are supported for additional languages or package managers. If you want to know whether another language is supported for a feature or to request support for a language, visit the [Community Forum](https://github.community/).
+
+| Language {% data reusables.supported-languages.products-table-header %}
+{% data reusables.supported-languages.C %}
+{% data reusables.supported-languages.Cpp %}
+{% data reusables.supported-languages.Cs %}
+{% data reusables.supported-languages.go %}
+{% data reusables.supported-languages.java %}
+{% data reusables.supported-languages.javascript %}
+{% data reusables.supported-languages.php %}
+{% data reusables.supported-languages.python %}
+{% data reusables.supported-languages.ruby %}
+{% data reusables.supported-languages.scala %}
+{% data reusables.supported-languages.typescript %}
+
+[1] These languages are supported for {% data variables.product.prodname_code_scanning %} by third-party actions.
diff --git a/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md b/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md
index e19116fd64..efcfbb4bc6 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/githubs-products.md
@@ -16,6 +16,8 @@ topics:
   - Security
 ---
 
+### About {% data variables.product.prodname_dotcom %}'s products
+
 {% data variables.product.prodname_dotcom %} 提供免费和付费产品。 您可以在 <{% data variables.product.pricing_url %}> 上查看每款产品的价格和完整功能列表。 {% data reusables.products.product-roadmap %}
 
 ### 用户帐户的 {% data variables.product.prodname_free_user %}
@@ -99,14 +101,3 @@ topics:
 您可以设置试用版来评估 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">设置 {% data variables.product.prodname_ghe_cloud %} 的试用</a>”。
 
 有关托管理您自己的 [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com) 实例的更多信息，请联系 {% data variables.contact.contact_enterprise_sales %}。 {% data reusables.enterprise_installation.request-a-trial %}
-
-### {% data variables.product.prodname_ghe_one %}
-
-{% data variables.product.prodname_ghe_one %} 包括 [{% data variables.product.prodname_enterprise %}](#github-enterprise)，加上：
-
-- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
-- {% data variables.product.prodname_insights %}
-- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}。 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)“。{% endif %}
-- [组织的 {% data variables.product.prodname_learning %}](https://lab.github.com/organizations)
-
-有关注册 {% data variables.product.prodname_ghe_one %} 的更多信息，请联系 {% data variables.contact.contact_enterprise_sales %}。
diff --git a/translations/zh-CN/content/github/getting-started-with-github/index.md b/translations/zh-CN/content/github/getting-started-with-github/index.md
index e2d278e2be..10b93eb67e 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/index.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/index.md
@@ -52,13 +52,13 @@ topics:
 <!-- {% link_with_intro /exploring-projects-on-github %} -->
 <!-- {% link_with_intro /using-github %} -->
 
-
 ### Table of Contents
 
 {% topic_link_in_list /quickstart %}
     {% link_in_list /set-up-git %}
     {% link_in_list /create-a-repo %}
     {% link_in_list /fork-a-repo %}
+    {% link_in_list /github-flow %}
     {% link_in_list /be-social %}
     {% link_in_list /github-glossary %}
     {% link_in_list /git-cheatsheet %}
@@ -66,6 +66,7 @@ topics:
 
 {% topic_link_in_list /learning-about-github %}
     {% link_in_list /githubs-products %}
+    {% link_in_list /github-language-support %}
     {% link_in_list /about-github-advanced-security %}
     {% link_in_list /types-of-github-accounts %}    
     {% link_in_list /access-permissions-on-github %}    
diff --git a/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md b/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md
index 2621099678..5ef919f2de 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/keyboard-shortcuts.md
@@ -36,12 +36,16 @@ versions:
 | <kbd>g</kbd> <kbd>p</kbd> | 转到 **Pull requests（拉取请求）**选项卡。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
 | <kbd>g</kbd> <kbd>a</kbd> | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %}
 | <kbd>g</kbd> <kbd>b</kbd> | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。                                                                                                           |
-| <kbd>g</kbd> <kbd>w</kbd> | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wikis](/communities/documenting-your-project-with-wikis/about-wikis)”。                                                                                 |
+| <kbd>g</kbd> <kbd>w</kbd> | 转到 **Wiki** 选项卡。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% if currentVersion == "free-pro-team@latest" %}
+| <kbd>g</kbd> <kbd>g</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
 
 ### 源代码编辑
 
 | 键盘快捷键                                                          | 描述                                                       |
 | -------------------------------------------------------------- | -------------------------------------------------------- |
+| <kbd>control b</kbd> 或 <kbd>command b</kbd>                    | 插入 Markdown 格式用于粗体文本                                     |
+| <kbd>control i</kbd> 或 <kbd>command i</kbd>                    | 插入 Markdown 格式用于斜体文本                                     |
+| <kbd>control k</kbd> 或 <kbd>command k</kbd>                    | 插入 Markdown 格式用于创建链接                                     |
 | <kbd>e</kbd>                                                   | 在 **Edit file（编辑文件）**选项卡中打开源代码文件                         |
 | <kbd>control f</kbd> 或 <kbd>command f</kbd>                    | 开始在文件编辑器中搜索                                              |
 | <kbd>control g</kbd> 或 <kbd>command g</kbd>                    | 查找下一个                                                    |
diff --git a/translations/zh-CN/content/github/getting-started-with-github/learning-about-github.md b/translations/zh-CN/content/github/getting-started-with-github/learning-about-github.md
index f85c450358..e5d83407b2 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/learning-about-github.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/learning-about-github.md
@@ -1,6 +1,6 @@
 ---
 title: 了解 GitHub
-intro: ''
+intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
 mapTopic: true
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md b/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md
index 9daf828eae..3cc18a28fa 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md
@@ -22,6 +22,8 @@ topics:
   - Accounts
 ---
 
+### 使用 Git
+
 要在命令行中使用 Git，您将需要在计算机上下载、安装和配置 Git。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 您也可以从命令行安装 {% data variables.product.prodname_cli %} 以使用 {% data variables.product.product_name %}。 有关 {% data variables.product.prodname_cli %} 的更多信息，请参阅 [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) 文档。{% endif %}
 
 如果要在本地使用 Git，但不想使用命令行，您可以下载并安装 [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) 客户端。  更多信息请参阅“[安装和配置 {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)”。
diff --git a/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
index da2a0a5e0f..920f2ee32b 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -50,10 +50,10 @@ topics:
 
 对于组织来说，降级到 {% data variables.product.prodname_free_team %} 还会禁用试用期间配置的任何 SAML 设置。 购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} 后，您的 SAML 设置将再次启用，以便您组织中的用户进行身份验证。
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. 在“{% data variables.product.prodname_ghe_cloud %} Free Trial（GitHub Enterprise Cloud 免费试用）”下，单击 **Buy Enterprise（购买 Enterprise 版）**或 **Downgrade to Team（降级到 Team 版）**。 ![购买 Enterprise 版和降级到 Team 版按钮](/assets/images/help/organizations/finish-trial-buttons.png)
 6. 按照提示输入付款方式，然后单击 **Submit（提交）**。
 
diff --git a/translations/zh-CN/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md b/translations/zh-CN/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
index e2a65be904..48e979ee57 100644
--- a/translations/zh-CN/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
+++ b/translations/zh-CN/content/github/getting-started-with-github/using-git-rebase-on-the-command-line.md
@@ -11,6 +11,8 @@ versions:
   github-ae: '*'
 ---
 
+### Using Git rebase
+
 在本例中，我们将涵盖所有可用的 `git rebase` 命令，`exec` 除外。
 
 我们将通过在终端上输入 `git rebase --interactive HEAD~7` 开始变基。 首选的文本编辑器将显示以下行：
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/about-github-importer.md b/translations/zh-CN/content/github/importing-your-projects-to-github/about-github-importer.md
index 2cbc6ce2b8..e91ef2e7c2 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/about-github-importer.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/about-github-importer.md
@@ -1,6 +1,6 @@
 ---
 title: 关于 GitHub 导入工具
-intro: 如果您在 Subversion、Mercurial、Team Foundation Server 或其他 Git 仓库中有源代码，可使用 GitHub 导入工具将其移至 GitHub。
+intro: 如果您在 Subversion、Mercurial、Team Foundation Version Control (TFVC) 或其他 Git 仓库中有源代码，可使用 GitHub 导入工具将其移至 GitHub。
 redirect_from:
   - /articles/about-github-importer
 versions:
@@ -13,12 +13,12 @@ GitHub 导入工具是一种可快速将源代码仓库（包括提交和修订
 
 在导入过程中，根据导入来源的版本控制系统，您可以向远程仓库进行身份验证，更新提交作者属性，以及导入包含大文件的仓库（如果不想使用 Git Large File Storage，也可删除大文件）。
 
-| 导入操作                                                                          |  子版本  | Mercurial | Team Foundation Server |  Git  |
-|:----------------------------------------------------------------------------- |:-----:|:---------:|:----------------------:|:-----:|
-| 向远程仓库进行身份验证                                                                   | **X** |   **X**   |         **X**          | **X** |
-| [更新提交作者属性](/articles/updating-commit-author-attribution-with-github-importer) | **X** |   **X**   |         **X**          |       |
-| 将大文件移至 [Git Large 文件存储](/articles/about-git-large-file-storage)               | **X** |   **X**   |         **X**          |       |
-| 从仓库删除大文件                                                                      | **X** |   **X**   |         **X**          |       |
+| 导入操作                                                                          |  子版本  | Mercurial | TFVC  |  Git  |
+|:----------------------------------------------------------------------------- |:-----:|:---------:|:-----:|:-----:|
+| 向远程仓库进行身份验证                                                                   | **X** |   **X**   | **X** | **X** |
+| [更新提交作者属性](/articles/updating-commit-author-attribution-with-github-importer) | **X** |   **X**   | **X** |       |
+| 将大文件移至 [Git Large 文件存储](/articles/about-git-large-file-storage)               | **X** |   **X**   | **X** |       |
+| 从仓库删除大文件                                                                      | **X** |   **X**   | **X** |       |
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/source-code-migration-tools.md b/translations/zh-CN/content/github/importing-your-projects-to-github/source-code-migration-tools.md
index d507f9d801..cf1271af26 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/source-code-migration-tools.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/source-code-migration-tools.md
@@ -12,7 +12,7 @@ versions:
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-我们建议使用 [GitHub 导入工具](/articles/about-github-importer)从 Subversion、Mercurial、Team Foundation Server 或其他 Git 仓库导入项目。 您还可以使用这些外部工具将项目转换为 Git。
+我们建议使用 [GitHub 导入工具](/articles/about-github-importer)从 Subversion、Mercurial、Team Foundation Version Control (TFVC) 或其他 Git 仓库导入项目。 您还可以使用这些外部工具将项目转换为 Git。
 
 {% endif %}
 
@@ -32,12 +32,9 @@ versions:
 
 我们建议使用 [hg-fast-export](https://github.com/frej/fast-export) 将 Mercurial 仓库转换为 Git。
 
-### 从 Team Foundation Server 导入
+### 从 TFVC 导入
 
-我们建议使用以下工具在 Team Foundation Server 与 Git 之间移动更改：
-
-- [git-tfs](https://github.com/git-tfs/git-tfs)
-- [Git-TF](https://gittf.codeplex.com/)
+我们建议 [git-tfs](https://github.com/git-tfs/git-tfs) 用于在TFVC 和 Git 之间移动更改。
 
 {% tip %}
 
diff --git a/translations/zh-CN/content/github/index.md b/translations/zh-CN/content/github/index.md
index b4dd354422..ae8c690a26 100644
--- a/translations/zh-CN/content/github/index.md
+++ b/translations/zh-CN/content/github/index.md
@@ -36,7 +36,6 @@ versions:
 {% link_in_list /collaborating-with-issues-and-pull-requests %}
 
 {% link_in_list /managing-your-work-on-github %}
-{% link_in_list /developing-online-with-codespaces %}
 
 {% link_in_list /searching-for-information-on-github %}
 
@@ -57,7 +56,6 @@ versions:
 
 {% link_in_list /extending-github %}
 
-{% link_in_list /supporting-the-open-source-community-with-github-sponsors %}
 {% link_in_list /finding-talent-with-github-jobs %}
 {% link_in_list /working-with-github-support %}
 {% link_in_list /understanding-how-github-uses-and-protects-your-data %}
diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md b/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
index 0433e81ac9..391a66f712 100644
--- a/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
+++ b/translations/zh-CN/content/github/managing-files-in-a-repository/deleting-files-in-a-repository.md
@@ -26,7 +26,7 @@ topics:
 
 1. 浏览到要删除仓库中的文件。
 2. 在文件顶部，单击
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md b/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md
index b373ef1785..00de26831b 100644
--- a/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md
+++ b/translations/zh-CN/content/github/managing-files-in-a-repository/navigating-code-on-github.md
@@ -9,6 +9,8 @@ topics:
   - Repositories
 ---
 
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+
 ### 关于在 {% data variables.product.prodname_dotcom %} 上导航代码
 
 代码导航使用开源库 [`tree-sitter`](https://github.com/tree-sitter/tree-sitter)。 支持以下语言：
diff --git a/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md b/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md
index b04c985005..1cd84afd85 100644
--- a/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md
+++ b/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md
@@ -1,6 +1,6 @@
 ---
-title: Conditions for large files
-intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories, and will block a push to a repository if the files are larger than the maximum file limit.'
+title: 大文件的条件
+intro: '{% data variables.product.product_name %} 限制了仓库允许的文件大小，如果文件大于最大文件限制，将会阻止推送到仓库。'
 redirect_from:
   - /articles/conditions-for-large-files
 versions:
@@ -11,10 +11,10 @@ versions:
 
 {% data reusables.large_files.use_lfs_tip %}
 
-### Warning for files larger than {% data variables.large_files.warning_size %}
+### 文件大于 {% data variables.large_files.warning_size %} 时的警告
 
-If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](/github/managing-large-files/removing-files-from-a-repositorys-history)."
+如果尝试添加或更新大于 {% data variables.large_files.warning_size %} 的文件，您将从 Git 收到警告。 更改仍将成功推送到仓库，但您可以考虑删除提交，以尽量减少对性能的影响。 更多信息请参阅“[从仓库的历史记录中删除文件](/github/managing-large-files/removing-files-from-a-repositorys-history)”。
 
-### Blocked pushes for large files
+### 阻止大文件的推送
 
-{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %}
+{% if enterpriseServersions contained currentVersion or currentVersion == "github-ae@latest" %}默认情况下，{% endif %}{% data variables.product.product_name %} 会阻止超过 {% data variables.large_files.max_github_size %} 的推送。 {% if enterpriseServersions contained currentVersion or currentVersion == "github-ae@latest" %}但站点管理员可为 {% data variables.product.product_location %} 配置不同的限制。 更多信息请参阅“[设置 Git 推送限制](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)”。{% endif %}
diff --git a/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
index 36789be6e5..cf7a9bc8db 100644
--- a/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
+++ b/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -38,7 +38,7 @@ versions:
 
 从 {% data variables.large_files.product_name_short %} 中删除文件后，{% data variables.large_files.product_name_short %} 对象仍存在于远程存储中{% if currentVersion == "free-pro-team@latest" %} 并将继续计入您的 {% data variables.large_files.product_name_short %} 存储配额{% endif %}。
 
-要从仓库中删除 {% data variables.large_files.product_name_short %} 对象，请{% if currentVersion == "free-pro-team@latest" %}删除并重新创建仓库。 删除仓库时，所有关联的议题、星标和复刻也会被删除。 更多信息请参阅“[删除仓库](/github/administering-a-repository/deleting-a-repository)”。{% else %}请联系 {% data variables.product.prodname_enterprise %} 管理员以存档对象。 存档的对象将在三个月后清除。{% endif %}
+要从仓库中删除 {% data variables.large_files.product_name_short %} 对象，请{% if currentVersion == "free-pro-team@latest" %}删除并重新创建仓库。 删除仓库时，所有关联的议题、星标和复刻也会被删除。 For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." If you need to purge a removed object and you are unable to delete the repository, please [contact support](/github/working-with-github-support) for help.{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. 存档的对象将在三个月后清除。{% endif %}
 
 {% note %}
 
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
index 67f9613edb..980b06c46b 100644
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md
@@ -1,90 +1,72 @@
 ---
-title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.'
-redirect_from:
-  - /articles/about-security-alerts-for-vulnerable-dependencies
-  - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
+title: 关于易受攻击的依赖项的警报
+intro: '当我们检测到影响仓库的漏洞时，{% data variables.product.product_name %} 将会发送 {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。'
 versions:
-  free-pro-team: '*'
-  enterprise-server: '*'
+  enterprise-server: <=2.22
+topics:
+  - Security
 ---
- 
-### About vulnerable dependencies
+
+<!--See /content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies for the current version of this article -->
+
+### 关于易受攻击的依赖项
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it.
+当代码依赖于具有安全漏洞的包时，这种易受攻击的依赖项可能会导致项目或使用它的人遇到一系列问题。
 
-### Detection of vulnerable dependencies
+### 有漏洞依赖项的检测
 
- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when:
+ {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} 在以下情况下检测有漏洞的依赖项并发送 {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %}检测有漏洞的依赖项并发送安全警报{% endif %}：
 
-{% if currentVersion == "free-pro-team@latest" %}
-- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."
-- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %}
-- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+- 新公告数据每小时从 {% data variables.product.prodname_dotcom_the_website %} 同步到 {% data variables.product.prodname_ghe_server %}。 {% data reusables.security-advisory.link-browsing-advisory-db %}
+- 仓库的依赖关系图发生更改。 例如，当贡献者推送提交以更改其所依赖的包或版本时。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
 
 {% data reusables.repositories.dependency-review %}
 
-For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+有关 {% data variables.product.product_name %} 可以检测到漏洞和依赖项的生态系统列表，请参阅“[支持的包生态系统](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。
 
 {% note %}
 
-**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use.
+**注：**保持清单和锁定文件为最新状态非常重要。 如果依赖关系图不能准确反映您当前的依赖项和版本，则可能错过有关您使用的有漏洞依赖项的警报。 您还可以收到不再使用的依赖项的警报。
 
 {% endnote %}
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %}
-### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies
+{% if currentVersion ver_gt "enterprise-server@2.21" % %}
+### 有漏洞依赖项的 {% data variables.product.prodname_dependabot %} 警报
 {% else %}
-### Security alerts for vulnerable dependencies
+### 对有漏洞的依赖项发出安全警报
 {% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% if currentVersion == "free-pro-team@latest" %}{% 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.
-
-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](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
-
-{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
-{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+当
+{% data variables.product.product_name %} 发现易受攻击的依赖项时，我们会生成 {% data variables.product.prodname_dependabot %} 警报，并显示在仓库的 Security（安全）选项卡上。 该警报包括指向项目中受影响的文件的链接，以及有关修复的版本的信息。 {% data variables.product.product_name %} 还根据受影响仓库的管理员的通知首选项向他们通知新的警报。 更多信息请参阅“[为易受攻击的依赖项配置通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。
 {% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. 
+当
+{% data variables.product.product_name %} 发现有漏洞的依赖项时， 我们会发送安全警报给受影响仓库的维护员，其中包含该漏洞的详细说明、项目中受影响文件的链接以及有关修复版本的信息。
 {% endif %}
 
 {% warning %}
 
-**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.
+**注**：{% data variables.product.product_name %} 的安全功能并不要求捕获所有漏洞。 虽然我们一直在努力更新漏洞数据库，生成包含最新信息的警报，但我们无法捕获一切或在保证的时间范围内向您警示已知的漏洞。 这些功能不是要替代人工检查每个依赖项的潜在漏洞或任何其他问题，并且我们建议在必要时咨询安全服务或全面检查漏洞。
 
 {% endwarning %}
 
-### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
+### 访问 {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报
 
-You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
+您可以在仓库的依赖关系图中看到影响特定项目的所有警报。
 
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
-{% endif %}
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+默认情况下，我们会通知受影响仓库中具有管理权限的人有新的
+{% data variables.product.prodname_dependabot_alerts %}.{% endif %}
 
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
-We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.
+默认情况下，我们会向具有受影响仓库管理员权限的人员发送安全警报。
+{% data variables.product.product_name %} 从不公开披露在任何仓库中发现的漏洞。
 {% endif %}
 
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
-
-{% if currentVersion == "free-pro-team@latest" %}
-### Further reading
-
-- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
-- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} 更多信息请参阅“[选择通知的递送方式](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.20" %}更多信息请参阅“[配置漏洞依赖项的通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。{% endif %}
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
index b1097a9342..0003b6eb0b 100644
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
@@ -3,8 +3,7 @@ title: Configuring notifications for vulnerable dependencies
 shortTitle: Configuring notifications
 intro: 'Optimize how you receive notifications about  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.'
 versions:
-  free-pro-team: '*'
-  enterprise-server: '>=2.21'
+  enterprise-server: '>=2.21 <=2.22'
 ---
 
 ### About notifications for vulnerable dependencies
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md
index 9fc78d10c8..90fbf8e937 100644
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md
+++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md
@@ -6,6 +6,7 @@ topics:
   - Security
 ---
 
+<!--See /content/code-security/supply-chain-security for the current version of this article -->
 
 ### 目录
 {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %}
diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
index ff844186e5..c851ea432e 100644
--- a/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
+++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md
@@ -8,3 +8,4 @@ topics:
   - Security
 ---
 
+<!--See content/code-security/supply-chain-security for the current version of this article -->
diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
index 3faa6a29bc..5d97f3c31f 100644
--- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
+++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md
@@ -26,13 +26,9 @@ topics:
 您可以选择订阅关于以下内容的通知：
 - 关于特定议题、拉取请求或 Gist 的对话。
 - 仓库或团队讨论中的所有活动。
-- CI 活动，例如仓库中使用 {% data variables.product.prodname_actions %} 设置的工作流程的状态。
-{% if currentVersion == "free-pro-team@latest" %}
-- 仓库中的议题、提取请求、发行版和讨论（如有启用）。
-{% endif %}
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
-- 仓库中的发行版。
-{% endif %}
+- CI 活动，例如仓库中使用 {% data variables.product.prodname_actions %} 设置的工作流程的状态。 {% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+- Releases in a repository.{% endif %}
 
 您也可以选择自动关注所有您有推送访问权限的仓库，但复刻除外。 您可以通过单击 **Watch（关注）**来手动关注您有权访问的任何其他仓库。
 
diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
index ce9490a93d..39e3801dd4 100644
--- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
+++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/configuring-notifications.md
@@ -73,7 +73,7 @@ topics:
 #### 配置通知
 {% endif %}
 您可以在仓库页面上或关注页面上为仓库配置通知。
-{% if currentversion == "github-ae@latest" or currentversion ver_gt "enterprise-server@2. 0" %} 您可以选择仅接收仓库中发布的通知，或忽略仓库的所有通知。{% endif %}{% if currentversion == "free proteam@latest" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} 您可以选择仅接收仓库中发布的通知，或忽略仓库的所有通知。{% endif %}{% if currentVersion == "free proteam@latest" %}
 
 #### 关于自定义通知
 {% data reusables.notifications-v2.custom-notifications-beta %}
diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
index 1a6df1fb9d..3167812c00 100644
--- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
+++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md
@@ -57,13 +57,13 @@ topics:
 {% data reusables.notifications.access_notifications %}
 1. 在左侧边栏中的仓库列表下，使用“Manage notifications（管理通知）”下拉按钮单击 **Watched repositories（已关注的仓库）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. 在关注的仓库页面上，评估您关注的仓库后，选择是否：
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+  {% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
     - 取消关注仓库
-    - 只关注某仓库的发行版
-    - 忽略某仓库的所有通知
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+    - Only watch releases for a repository
+    - Ignore all notifications for a repository
+  {% endif %}
+  {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
     - 取消关注仓库
-    - 忽略某仓库的所有通知
-    - 自定义接收通知的事件类型（议题、拉取请求、发布或讨论，如有启用）
-{% endif %}
+    - Ignore all notifications for a repository
+    - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
+  {% endif %}
diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
index 1f528b4e37..da3a98014f 100644
--- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
+++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md
@@ -35,10 +35,10 @@ topics:
 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)”。
 
 To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
-{% if currentVersion == "free-pro-team@latest" %}
+{% if currentVersion == "free-pro-team@latest" or  currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 {% tip %}
 
-**提示：**您可以在[关注页面](https://github.com/watching)或 {% data variables.product.prodname_dotcom_the_website %} 上的任何仓库页面，使用 **Watch/Unwatch（关注/取消关注）**下拉列表中的 **Custom（自定义）**选项选择要通知的事件类型。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)”。
+**提示：**您可以在[关注页面](https://github.com/watching)或 {% data variables.product.product_name %} 上的任何仓库页面，使用 **Watch/Unwatch（关注/取消关注）**下拉列表中的 **Custom（自定义）**选项选择要通知的事件类型。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)”。
 
 {% endtip %}
 {% endif %}
@@ -67,16 +67,15 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie
 
 1. 在左侧边栏中的仓库列表下，使用“Manage notifications（管理通知）”下拉菜单单击 **Watched repositories（已关注的仓库）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png)
 2. 评估您正在关注的仓库，确定它们更新是否仍然相关和有用。 关注某仓库后，您将收到该仓库所有对话的通知。
-{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
+{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.1" %}
   ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications.png)
-{% endif %}
-{% if currentVersion == "free-pro-team@latest" %}
+{% elsif currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
   ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% endif %}
 
   {% tip %}
 
-  **提示：**不关注仓库， 而是考虑仅{% if currentversion == "free-proteam@latest" %}在议题、拉取请求、版本或讨论（如已对仓库启用）或其任何组合有更新时，{% else %}仓库中有发布，{% endif %} 或完全取消关注仓库时才接收通知。
+  **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository.
 
   取消关注仓库后，当您被@提及或参与帖子时仍然会收到通知。 当您配置接收某些事件类型的通知时，仅在仓库中有这些事件类型的更新、您参与了线程或者您或您所在团队被 @提及时才收到通知。
 
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/zh-CN/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
index d18784e8f6..b46550ab58 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters.md
@@ -21,7 +21,7 @@ topics:
 
 必须具有适当的权限才可执行使用相关查询参数的操作。 例如，必须具有向议题添加标签的权限才可使用 `labels` 查询参数。
 
-如果使用查询参数创建无效的 URL，或者没有适当的权限，URL 将返回 404 错误页。
+如果使用查询参数创建无效的 URL，或者没有适当的权限，URL 将返回 `404 未找到`错误页。 如果您创建的 URL 超过服务器限制，URL 将返回 `414 URI 过长`错误页面。
 
 ### 支持的查询参数
 
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
index 33b0755e83..4931015126 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -18,7 +18,7 @@ topics:
 4. 选择以下选项之一：
     - 要创建新里程碑，请单击 **New Milestone（新建里程碑）**。 ![新建里程碑按钮](/assets/images/help/repository/new-milestone.png)
     - 要编辑里程碑，请在要编辑的里程碑旁边，单击 **Edit（编辑）**。 ![编辑里程碑选项](/assets/images/help/repository/edit-milestone.png)
-5. 键入里程碑的标题、说明或其他更改，然后单击 **Create milestone（创建里程碑）**或 **Save changes（保存更改）**。
+5. 键入里程碑的标题、说明或其他更改，然后单击 **Create milestone（创建里程碑）**或 **Save changes（保存更改）**。 里程碑将呈现 Markdown 语法。 有关 Markdown 语法的更多信息，请参阅“[基本撰写和格式语法](/github/writing-on-github/basic-writing-and-formatting-syntax)”。
 
 ### 删除里程碑
 
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md b/translations/zh-CN/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
index 9d5bca6eb9..826f8e7dbe 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/disabling-project-boards-in-your-organization.md
@@ -17,9 +17,9 @@ topics:
 
 禁用项目板后，在时间表或[审核日志](/articles/reviewing-the-audit-log-for-your-organization/)中将不再看到项目板信息。
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 决定是否禁用组织范围的项目板，禁用组织中的仓库项目板，或两者均禁用。 然后，在“项目”（项目）下：
     - 要禁用组织范围的项目板，请取消选择 **Enable projects for the organization（启用组织的项目）**。
     - 要在组织中禁用仓库项目板，请取消选择 **Enable projects for all repositories（启用所有仓库的项目）**。 ![用于禁用单个组织或单个组织所有仓库的项目的复选框](/assets/images/help/projects/disable-org-projects-checkbox.png)
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
index e2181822b4..6a693b7d65 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
 title: 议题和拉取请求中的文件附件
-intro: 在打开议题或更新拉取请求时，您可以使用议题附件上传提议功能的图像或漏洞的屏幕截图。
+intro: You can convey information by attaching a variety of file types to your issues and pull requests.
 redirect_from:
   - /articles/issue-attachments/
   - /articles/file-attachments-on-issues-and-pull-requests
@@ -14,7 +14,7 @@ topics:
 
 {% warning %}
 
-**警告：**如果您在拉取请求或议题评论中添加了图像，则任何人都可以查看匿名图像 URL，无需身份验证，即使该拉取请求位于私有仓库中{% if enterpriseServerVersions contains currentVersion %}或者启用了私有模式{% endif %}。 要对敏感图像保密，请从需要身份验证的私有网络或服务器提供它们。 {% if currentVersion == "free-pro-team@latest" %}有关匿名 URL 的更多信息，请参阅“[关于匿名图像 URL](/articles/about-anonymized-image-urls)”。{% endif %}
+**Warning:** If you add an image {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% if enterpriseServerVersions contains currentVersion %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
@@ -28,17 +28,11 @@ topics:
 
 {% endtip %}
 
-文件大小不得超过 25MB，图像大小不得超过 10MB。
-{% if currentVersion == "free-pro-team@latest" %}
-如果仓库由付费 GitHub 计划的用户或组织拥有，则视频大小可达 100 MB。
-
-{% note %}
-
-**注意：**视频附件支持目前处于测试阶段，可能会更改。
-
-{% endnote %}
-
-{% endif %}
+The maximum file size is:
+- 10MB for images and gifs{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+- 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan
+- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %}
+- 25MB for all other files
 
 我们支持这些文件：
 
@@ -49,7 +43,7 @@ topics:
 * Microsoft Word (*.docx*)、Powerpoint (*.pptx*) 和 Excel (*.xlsx*) 文档
 * 文本文件 (*.txt*)
 * PDF (*.pdf*)
-* ZIP（*.zip*、*.gz*）{% if currentVersion == "free-pro-team@latest" %}
+* ZIP（*.zip*、*.gz*）{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 * 视频（*.mp4*、*.mov*）{% endif %}
 
 ![附件动画 GIF](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md b/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md
index 87a747d0f8..d67852345a 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/managing-labels.md
@@ -49,6 +49,8 @@ topics:
 
 创建仓库时，每个新仓库中均包含默认标签，但您稍后可以编辑或删除标签。
 
+Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
+
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
 组织所有者可以自定义其组织中仓库的默认标签。 更多信息请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”。
 {% endif %}
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
index e85a79b430..bc5e09c489 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/sorting-issues-and-pull-requests.md
@@ -19,11 +19,11 @@ topics:
 * 评论最少的议题或拉取请求
 * 最新更新的议题或拉取请求
 * 最早更新的议题或拉取请求
-* 添加[反应](/articles/about-conversations-on-github#reacting-to-ideas-in-comments)最多的议题或拉取请求
+* The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. 在右上角，选择 Sort（排序）下拉菜单。 ![使用排序下拉菜单选项卡](/assets/images/help/issues/issues_sort_dropdown.png)
+1. 在右上角，选择 Sort（排序）下拉菜单。 ![使用排序下拉菜单选项卡](/assets/images/help/issues/issues_sort_dropdown.png)
 
 要清除您的排序选择，请单击 **Sort（排序）<**>**Newest（最新）**。
 
diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md
index 09ed106248..3bef9b43cb 100644
--- a/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md
+++ b/translations/zh-CN/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md
@@ -13,7 +13,7 @@ topics:
 
 要将打开的议题转让给另一个仓库，必须对议题所在的仓库以及议题要转让到的仓库都有写入权限。 更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)”。
 
-您只能在同一用户或组织帐户拥有的仓库之间转让议题。 {% if currentversion == "free proteam@latest" or enterpriseServersions contains currentversion %} 您不能将议题从私有仓库转移到公共仓库。{% endif %}
+您只能在同一用户或组织帐户拥有的仓库之间转让议题。 {% if currentVersion == "free proteam@latest" or enterpriseServersions contains currentVersion %} 您不能将议题从私有仓库转移到公共仓库。{% endif %}
 
 转让议题时，评论和受理人将保留。 不会保留议题的标签和里程碑。 此议题将留在任何用户拥有或组织范围的项目板上，并从任何仓库项目板中删除。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。
 
diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md
index 14bcb73dd0..2c99ffcb6a 100644
--- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md
+++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-code.md
@@ -66,8 +66,9 @@ topics:
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) 匹配 <em>app/public</em> 目录或其任何子目录（即使其位于 <em>app/public/js/form-validators</em> 中）中且含有 "console" 字样的 JavaScript 文件。 |
 
 ### 按语言搜索
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
-您可以基于所编写的语言搜索代码。
+您可以基于所编写的语言搜索代码。 The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the \[github/linguist repository\]((https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
 | 限定符                        | 示例                                                                                                                                                               |
 | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
index 709b6ca721..b8dc148fbd 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md
@@ -14,7 +14,11 @@ topics:
 
 {% data reusables.package_registry.packages-spending-limit-brief %} 更多信息请参阅“[关于支出限制](#about-spending-limits)”。
 
-{% data reusables.package_registry.container-registry-beta-billing-note %}
+{% note %}
+
+**Billing update for container image storage:** During the beta phase of the {% data variables.product.prodname_container_registry %}, Docker image storage and bandwidth are free for both the previous `docker.pkg.github.com` and current `ghcr.io` hosting services. 更多信息请参阅“[{% data variables.product.prodname_registry %} 简介](/packages/learn-github-packages/introduction-to-github-packages)”。
+
+{% endnote %}
 
 如果您通过 Microsoft 企业协议购买 {% data variables.product.prodname_enterprise %}，可以将 Azure 订阅 ID 连接到您的企业帐户，以便启用并支付超出您的帐户金额的 {% data variables.product.prodname_registry %} 使用费用。 更多信息请参阅“[将 Azure 订阅连接到您的企业](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)”。
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
index 487a4f2d8a..56d97b3dc7 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md
@@ -17,5 +17,5 @@ topics:
 
 ### 延伸阅读
 
-- "[关于 {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)"
-- "[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)"
+- "[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors)"
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
index 175ec0c4f4..1207c027b8 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md
@@ -16,26 +16,11 @@ versions:
 
 ### 关于 {% data variables.product.prodname_GH_advanced_security %} 的提交者数量
 
-我们在 {% data variables.product.prodname_dotcom_the_website %}上记录并显示 {% data variables.product.prodname_GH_advanced_security %} 的两个提交者：
-
-- **提交者**是指在组织中参与至少一个私有仓库并在您的许可证中使用一个席位的提交者数量。 也就是说，他们也是组织成员、外部协作者，或者具有待处理的企业帐户中组织加入邀请。
-- **对此仓库/组织唯一**是只参与该仓库或该组织中仓库的提交者数量。 此数字显示您可以通过禁用该仓库或组织的 {% data variables.product.prodname_GH_advanced_security %} 来释放多少许可证席位。
-
-如果没有唯一的提交者，这意味着所有活跃的提交者也参与其他使用 {% data variables.product.prodname_GH_advanced_security %} 的仓库或组织。 禁用该仓库或组织的功能将不会在您的许可证上腾出任何席位。
-
-{% note %}
-
-**注意：**许可证中使用的座位总数不是每个仓库或组织的提交者或唯一提交者之和。 这是因为有人参与多个仓库或组织。 使用的席位数是在整个企业帐户中计量的，以确保每个人只计算一次，而不论他们参与多少个仓库或组织。
-
-{% endnote %}
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
 ### 管理 {% data variables.product.prodname_GH_advanced_security %} 的许可证使用
 
-当您为单个仓库或组织中的所有仓库启用 {% data variables.product.prodname_GH_advanced_security %} 时，{% data variables.product.company_short %} 将显示这要使用多少额外的席位，并提示您确认。 如果您禁用对 {% data variables.product.prodname_GH_advanced_security %} 的访问，任何被“唯一”提交者使用的席位都将释放。 这使我们更容易理解更改对许可证使用的影响。
-
-如果您超过了许可证限制，{% data variables.product.prodname_GH_advanced_security %} 将继续在所有已启用的仓库中工作。 但是，在为新仓库启用 {% data variables.product.prodname_GH_advanced_security %} 的组织中，将会创建禁用该功能的仓库。 此外，对现有仓库启用 {% data variables.product.prodname_GH_advanced_security %} 的选项将不可用。 如果您将公共仓库的可见性更改为私有，则将对该仓库禁用 {% data variables.product.prodname_GH_advanced_security %}。
-
-一旦您释放一些席位，通过对某些仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 或通过增加您的许可证大小，用于启用 {% data variables.product.prodname_GH_advanced_security %} 的选项将继续正常工作。
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
 
 您可以执行策略以允许或不允许企业帐户拥有的组织使用 {% data variables.product.prodname_advanced_security %}。 更多信息请参阅“[在企业帐户中执行 {% data variables.product.prodname_advanced_security %} 的策略](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)”。
 
@@ -43,9 +28,4 @@ versions:
 
 ### 充分利用您的 {% data variables.product.prodname_GH_advanced_security %} 许可证
 
-当您决定哪些仓库和组织优先用于 {% data variables.product.prodname_GH_advanced_security %} 时，应该查看它们并识别：
-
-- 对公司成功至关重要的代码库。 在这些项目中，引入了易受攻击代码、硬编码的密钥或易受攻击的依赖项，将对您的公司将产生最大的影响。
-- 提交频率最高的代码库。 这些是最积极开发的项目，因此出现安全问题的风险较高。
-
-当您为这些组织或仓库启用 {% data variables.product.prodname_GH_advanced_security %} 时，应该评估您可以添加哪些其它代码，而无需添加任何额外的唯一提交者以及使用您许可证上的更多席位。 在此之后，查看下一个最重要和最繁忙的代码库。 如果您想增加许可证中的席位数，请联系 {% data variables.contact.contact_enterprise_sales %}。
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
index ee93f5a74c..f84530a973 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts.md
@@ -28,8 +28,8 @@ topics:
 ### 添加信息到个人帐户的收据
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
 
 ### 添加信息到组织的收据
@@ -40,9 +40,9 @@ topics:
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
index 42073a32bd..c6d764941e 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method.md
@@ -28,8 +28,9 @@ topics:
 ### 更新个人帐户的付款方式
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![计费新卡按钮](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
 ### 更新组织的付款方式
@@ -38,9 +39,10 @@ topics:
 
 如果组织在美国之外，或者您使用公司支票帐户支付 {% data variables.product.product_name %}，PayPal 可能是一种有用的付款方式。
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
+1. If your account has an existing credit card that you want to update, click **New Card**. ![计费新卡按钮](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
index 99e6742c8b..02088ed221 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app.md
@@ -20,16 +20,14 @@ topics:
 ### 取消个人帐户的应用程序
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
 ### 取消个人帐户的应用程序免费试用
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -37,11 +35,10 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
@@ -49,10 +46,9 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
index fa95b49fc2..36b7ffc7c7 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle.md
@@ -17,7 +17,7 @@ topics:
 ### 更改个人帐户结算周期的时长
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -29,7 +29,7 @@ topics:
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
@@ -37,6 +37,6 @@ topics:
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.billing %}
+{% data reusables.organizations.billing_plans %}
 4. 在“Billing overview（帐单概览）”下，单击 **Change plan（更改计划）**。 ![帐单概览更改计划按钮](/assets/images/help/billing/billing_overview_change_plan.png)
 5. 在右上角，单击 **Switch to monthly billing（切换为月度结算）** or **Switch to yearly billing（切换为年度结算）**。 ![帐单信息部分](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
index bb1196504f..a36dfe4d80 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -42,25 +42,21 @@ topics:
 
 ### 第 3 步：将组织升级到年度付费订阅
 
-{% data reusables.profile.access_profile %}
+
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %} （在下一步可向组织添加更多席位。）
 6. 在“Upgrade summary（升级摘要）”下，选择 **Pay yearly（年度付款）**以每年为组织支付一次。 ![用于年度计费的单选按钮](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
-{% data reusables.dotcom_billing.show-plan-details %}
-{% data reusables.dotcom_billing.add-payment-method %}
-1. 在“Pay with（付款方式）”下，键入您的信用卡信息。 ![用于输入信用卡信息的表单](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png)
-1. 单击 **Update credit card（更新信用卡）**。
+{% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
 ### 第 4 步：升级组织中的付费席位数
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
index 2ef504b1d2..993f9b54f6 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md
@@ -20,11 +20,11 @@ topics:
 
 ### 个人帐户折扣
 
-拥有 {% data variables.product.prodname_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 更多信息请参阅“[申请学生开发包](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)”。
+拥有 {% data variables.product.prodname_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 更多信息请参阅“[申请学生开发包](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)”。
 
 ### 学校和大学折扣
 
-经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 更多信息请参阅“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)”。 更多信息请参阅“[在课堂和研究中使用 {{ site.data.variables.product.prodname_dotcom }}](/articles/using-github-in-your-classroom-and-research)”。 更多信息请访问 [{% data variables.product.prodname_education %}](https://education.github.com/)。
+经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 更多信息请参阅“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)”。 更多信息请参阅“[在课堂和研究中使用 {{ site.data.variables.product.prodname_dotcom }}](/articles/using-github-in-your-classroom-and-research)”。 更多信息请访问 [{% data variables.product.prodname_education %}](https://education.github.com/)。
 
 ### 非赢利组织和图书馆折扣
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
index 7bbf1d48c4..646f62e39b 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage.md
@@ -16,8 +16,7 @@ topics:
 ### 降级个人帐户的存储和带宽
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
@@ -25,10 +24,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 0768c52b1d..797d9a2623 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -18,7 +18,7 @@ topics:
 ### 降级个人帐户的应用程序
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -28,10 +28,9 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.downgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
index f3cd2dca62..8eaea75c12 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription.md
@@ -30,9 +30,8 @@ topics:
 如果您将您的用户帐户从 {% data variables.product.prodname_pro %} 降级为 {% data variables.product.prodname_free_user %}，该帐户将失去对私有仓库中高级代码审查工具的访问权限。 {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. 使用 **Edit（编辑）**下拉菜单并单击 **Downgrade to Free（降级到免费 ）**。 ![降级到免费按钮](/assets/images/help/billing/downgrade-to-free.png)
+{% data reusables.user_settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. ![降级到免费按钮](/assets/images/help/billing/downgrade-to-free.png)
 5. 阅读有关信息，了解您的用户帐户在下一个结算日期将不再拥有访问权限的功能，然后单击 **I understand. Continue with downgrade（我明白。继续降级）**。 ![继续降级按钮](/assets/images/help/billing/continue-with-downgrade.png)
 
 如果您在私有仓库中发布了 {% data variables.product.prodname_pages %} 站点，并添加了自定义域，在从 {% data variables.product.prodname_pro %} 降级至 {% data variables.product.prodname_free_user %} 前，请删除或更新您的 DNS 记录，以避免域接管的风险。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
@@ -45,12 +44,10 @@ topics:
 
 如果将您的组织从 {% data variables.product.prodname_ghe_cloud %} 降级到 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_free_team %}，该帐户将失去对高级安全性、合规性和部署控件的访问权限。 {% data reusables.gated-features.more-info %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. 使用 **Edit（编辑）**下拉菜单，单击您想要的降级选项。 ![降级按钮](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. ![降级按钮](/assets/images/help/billing/downgrade-option-button.png)
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
 
 ### 降级采用传统的按仓库定价模式的组织订阅
@@ -59,10 +56,9 @@ topics:
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} 更多信息请参阅“[将组织从按仓库定价切换为按用户定价](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. 在“Subscriptions（订阅）”下，选择“Edit（编辑）”下拉菜单，然后单击 **Edit plan（编辑计划）**。 ![编辑计划下拉菜单](/assets/images/help/billing/edit-plan-dropdown.png)
 1. 在“Billing/Plans（计费/计划）”下您要更改的计划旁边，单击 **Downgrade（降级）**。 ![降级按钮](/assets/images/help/billing/downgrade-plan-option-button.png)
 1. 输入要降级帐户的原因，然后单击 **Downgrade plan（降级计划）**。 ![降级原因文本框和降级按钮](/assets/images/help/billing/downgrade-plan-button.png)
@@ -74,12 +70,10 @@ topics:
 - "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)"
 - "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-6. 使用 **Edit（编辑）**下拉菜单并单击 **Remove seats（删除席位）**。 ![删除席位下拉菜单](/assets/images/help/billing/remove-seats-dropdown.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. ![删除席位下拉菜单](/assets/images/help/billing/remove-seats-dropdown.png)
 1. 在“Remove seats”（删除席位）下，选择要降级的席位数。 ![删除席位选项](/assets/images/help/billing/remove-seats-amount.png)
 1. 审查有关在下一个结算日期执行新付款方式的信息，然后单击 **Remove seats（删除席位）**。 ![删除席位按钮](/assets/images/help/billing/remove-seats-button.png)
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
index 44c1c5637b..662985a857 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md
@@ -27,8 +27,8 @@ topics:
 任何人都可管理其用户帐户的 {% data variables.product.prodname_actions %} 支出限额。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ topics:
 
 组织所有者和帐单管理员可管理组织的 {% data variables.product.prodname_actions %} 支出限额。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ topics:
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. 在“
-{% data variables.product.prodname_actions %} and Packages monthly usage（GitHub Actions 和包每月使用）”下，单击 **Cost management（成本管理）**。
-  ![成本管理选项卡](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
index 2b4ebba9f5..75afc8c23a 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md
@@ -27,8 +27,8 @@ topics:
 任何人都可管理其用户帐户的 {% data variables.product.prodname_registry %} 支出限额。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -36,11 +36,10 @@ topics:
 
 组织所有者和帐单管理员可管理组织的 {% data variables.product.prodname_registry %} 支出限额。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.cost-management-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -51,8 +50,8 @@ topics:
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. 在“
-{% data variables.product.prodname_actions %} and Packages monthly usage（GitHub Actions 和包每月使用）”下，单击 **Cost management（成本管理）**。
-  ![成本管理选项卡](/assets/images/help/settings/cost-management-tab-enterprise.png)
+1. Above "
+{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
index f929aec768..d22e46db07 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md
@@ -26,8 +26,8 @@ topics:
 ### 删除个人帐户的付款方式
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.user_settings.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
 
@@ -35,10 +35,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.payment-info-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.user_settings.payment-info-link %}
 {% data reusables.dotcom_billing.remove-payment-method %}
 {% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
index f1df60a8e8..97138626fa 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization.md
@@ -20,10 +20,9 @@ topics:
 
 ### 更新组织的信用卡
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. 在安全的表单中输入您的新信用卡信息。 ![信用卡信息表单](/assets/images/help/settings/creditcard-billing-form.png)
-1. 单击 **Update credit card（更新信用卡）**或 **Save credit card（保存信用卡）**。
+1. Under "Payment method", click **New Card**. ![计费新卡按钮](/assets/images/help/billing/billing-new-card-button.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
index 58cf5a9954..5177c8abdd 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email.md
@@ -27,9 +27,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 在 **Billing email（帐单邮箱）**下，输入有效的电子邮件地址。 该邮箱不需要是组织帐户唯一的邮箱。 ![帐单邮箱文本框](/assets/images/help/settings/org-billing-email.png)
 5. 要确认您的更改，请单击 **Update profile（更新个人资料）**。 ![更新个人资料按钮](/assets/images/help/settings/update-profile-button.png)
 
@@ -40,8 +39,8 @@ topics:
 #### 添加帐单通知的收件人
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. 在“Billing management（帐单管理）”下，在“Email recipients（电子邮件收件人）”的右侧，单击 **Add（添加）**。 ![添加收件人](/assets/images/help/billing/billing-add-email-recipient.png)
 1. 输入收件人的电子邮件地址，然后单击 **Add（添加）**。 ![添加收件人模式](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
@@ -50,17 +49,17 @@ topics:
 必须始终将一个地址指定为主要收件人。 在选择新的主要收件人之前，无法删除带有此指定地址。
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. 在“Billing management（帐单管理）”下，找到要设置为主要收件人的电子邮件地址。
 1. 在电子邮件地址的右侧，使用“Edit（编辑）”下拉菜单，然后单击 **Mark as primary（标记为主要收件人）**。 ![标记主要收件人](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
 #### 从帐单通知中删除收件人
 
 {% data reusables.organizations.navigate-to-org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 1. 在“Email recipients（电子邮件收件人）”下，找到要删除的电子邮件地址。
 1. 针对列表中的用户条目，单击 **Edit（编辑）**。 ![编辑收件人](/assets/images/help/billing/billing-edit-email-recipient.png)
-1. 在电子邮件地址的右侧，使用“Edit（编辑）”下拉菜单，然后单击 *Remove（删除）**。 ![删除收件人](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. To the right of the email address, use the "Edit" drop-down menu, and click **Remove**. ![删除收件人](/assets/images/help/billing/billing-remove-email-recipient.png)
 1. 查看确认提示，然后单击 **Remove（删除）**。
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
index 02d5d4c530..6c8959a9f6 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage.md
@@ -14,8 +14,7 @@ topics:
 ### 为个人帐户购买额外的存储空间和带宽
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
@@ -24,11 +23,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-add-data %}
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
index 65ce42a7df..841fee631a 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -22,11 +22,9 @@ topics:
 
 ### 升级组织的付费席位数量
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -35,10 +33,8 @@ topics:
 
 ### 将组织的付费席位数量降级为免费
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.downgrade-org-to-free %}
 {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 659efc9227..0460494f95 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -16,8 +16,7 @@ topics:
 ### 升级个人帐户的应用程序
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
@@ -27,11 +26,9 @@ topics:
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.marketplace.upgrade-app-billing-settings %}
 {% data reusables.marketplace.choose-new-plan %}
 {% data reusables.marketplace.choose-new-quantity %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
index 1daca134c3..dd79192ec3 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md
@@ -28,11 +28,9 @@ topics:
 您可以将个人帐户从 {% data variables.product.prodname_free_user %} 升级到 {% data variables.product.prodname_pro %}，以获得私有仓库中的高级代码审查工具。 {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
-4. 在“
-{% data variables.product.prodname_free_user %}”旁边，单击 **Upgrade（升级）**。
-  ![升级按钮](/assets/images/help/billing/settings_billing_user_upgrade.png)
+{% data reusables.user_settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**. ![升级按钮](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-payment-info %}
@@ -44,11 +42,9 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.upgrade_org %}
 {% data reusables.dotcom_billing.choose_org_plan %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
@@ -67,11 +63,9 @@ topics:
 
 如果希望其他用户能够访问您 {% data variables.product.prodname_team %} 组织的私有仓库，您可以随时购买更多席位。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
@@ -80,10 +74,9 @@ topics:
 
 {% data reusables.dotcom_billing.switch-legacy-billing %} 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 5. 在计划名称的右侧，使用 **Edit（编辑）**下拉菜单，然后选择 **Edit plan（编辑计划）**。 ![编辑下拉菜单](/assets/images/help/billing/per-user-upgrade-button.png)
 6. 在“Advanced tools for teams（团队的高级工具）”右侧，单击 **Upgrade now（立即升级）**。 ![立即升级按钮](/assets/images/help/billing/per-user-upgrade-now-button.png)
 {% data reusables.dotcom_billing.choose_org_plan %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
index fe64e43118..f891f7032a 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -19,19 +19,16 @@ topics:
 ### 查看和管理对个人帐户订阅的待定更改
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
 ### 查看和管理对组织订阅的待定更改
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
index 070728f338..5a1bb6e60e 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage.md
@@ -16,19 +16,16 @@ topics:
 ### 查看个人帐户的存储空间和带宽使用情况
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### 查看组织的存储空间和带宽使用情况
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-{% data reusables.user_settings.subscriptions-tab %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
 ### 延伸阅读
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
index d31fd12498..e88a4f2504 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage.md
@@ -15,7 +15,7 @@ topics:
 任何人都可以查看自己用户帐户的 {% data variables.product.prodname_actions %} 使用情况。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -24,10 +24,9 @@ topics:
 
 组织所有者和帐单管理员可查看组织的 {% data variables.product.prodname_actions %} 使用情况。 对于由企业帐户管理的组织，只有组织所有者可以在组织的帐单页面中查看 {% data variables.product.prodname_actions %} 使用情况。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.actions-minutes %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
index 3fe842da42..03398f2ed1 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md
@@ -1,24 +1,24 @@
 ---
 title: 查看您的 GitHub 高级安全使用情况
-intro: '您可以查看和管理 {% data variables.product.prodname_GH_advanced_security %} 许可证的使用情况。'
-permissions: 'Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
+intro: 'You can view usage of your {% data variables.product.prodname_GH_advanced_security %} license.'
+permissions: 'Enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations.'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
 versions:
   free-pro-team: '*'
 ---
 
-{% data variables.product.prodname_GH_advanced_security %} 的每个许可证都规定了可以使用这些功能的最大帐户或席位数量。 您应该定期检查您的使用是否在许可范围之内。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 企业许可证的许可](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)”。
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."
 
-### 查看和管理企业帐户的 {% data variables.product.prodname_GH_advanced_security %} 许可证使用情况
+### Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
 
-您可以检查您的许可证包含多少个席位，以及其中多少席位目前在“企业许可”页面上使用。
+You can check how many seats your license includes and how many of them are currently used.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-   “{% data variables.product.prodname_GH_advanced_security %}”部分显示了当前使用详情。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) 如果您的席位用完了，该部分将为红色。 您应该减少您对 {% data variables.product.prodname_GH_advanced_security %} 的使用，或者购买更多席位。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 企业许可证的许可](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)”。 ![企业许可设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
-4. （可选）要查看每个组织的使用详情，请在左侧边栏中单击 **Billing（计费）**。 ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) 在“{% data variables.product.prodname_GH_advanced_security %}”部分，您可以查看每个组织的提交者和唯一提交者数量。 ![企业计费设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/billing/ghas-orgs-list-enterprise.png)
+   “{% data variables.product.prodname_GH_advanced_security %}”部分显示了当前使用详情。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) 如果您的席位用完了，该部分将为红色。 您应该减少您对 {% data variables.product.prodname_GH_advanced_security %} 的使用，或者购买更多席位。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的许可](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)”。 ![企业许可设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. （可选）要查看每个组织的使用详情，请在左侧边栏中单击 **Billing（计费）**。 ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) 在“{% data variables.product.prodname_GH_advanced_security %}”部分，您可以查看每个组织的提交者和唯一提交者数量。 ![企业计费设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
 5. （可选）单击您是所有者的组织的名称，以显示组织的安全和分析设置。 ![在企业帐单设置的 {% data variables.product.prodname_GH_advanced_security %} 部分中拥有的组织](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
 6. 在“Security & analysis（安全性和分析）”设置页面上，滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分以查看此组织的仓库使用明细。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
index dc82f8a8e7..6f20a082ff 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage.md
@@ -13,7 +13,7 @@ topics:
 任何人都可以查看自己用户帐户的 {% data variables.product.prodname_registry %} 使用情况。
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
@@ -22,10 +22,9 @@ topics:
 
 组织所有者和帐单管理员可查看组织的 {% data variables.product.prodname_registry %} 使用情况。 对于由企业帐户管理的组织，只有组织所有者可以在组织的帐单页面中查看 {% data variables.product.prodname_registry %} 使用情况。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.packages-data %}
 {% data reusables.dotcom_billing.actions-packages-storage %}
 {% data reusables.dotcom_billing.actions-packages-report-download %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
index 317179377d..f6eab57549 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts.md
@@ -15,7 +15,7 @@ topics:
 ### 查看个人帐户的收据
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
@@ -23,9 +23,8 @@ topics:
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
index b97cbfccc2..28f8e4ba4b 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date.md
@@ -16,17 +16,16 @@ topics:
 ### 查找个人帐户的下一个结算日期
 
 {% data reusables.user_settings.access_settings %}
-{% data reusables.user_settings.billing %}
+{% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### 查找组织的下一个结算日期
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
 ### 延伸阅读
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md
index d674710b77..914e1bdac6 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md
@@ -33,7 +33,7 @@ topics:
 
 {% if currentVersion ver_gt "enterprise-server@3.0" %}如果您具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
 
-{% if currentversion == "github-ae@latest" %}该页面还将包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。{% endif %}
+{% if currentVersion == "github-ae@latest" %}该页面还将包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。{% endif %}
 
 ### 为所有现有仓库启用或禁用功能
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md
index d16765468d..3e374ad3ff 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md
@@ -122,7 +122,7 @@ topics:
 | [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                       | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 | 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                          | **X** |                                           
 {% endif %}
-{% if currentversion == "github-ae@latest" %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %}
+{% if currentVersion == "github-ae@latest" %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %}
 
 {% endif %}
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md
index 989b08ed6e..e543b8d9d5 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group.md
@@ -17,9 +17,9 @@ topics:
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
-{% if currentversion == "free proteam@latest" %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif currentVersion == "github-ae@latest" %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。
+{% if currentVersion == "free proteam@latest" %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif currentVersion == "github-ae@latest" %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。
 
-{% if currentversion == "free-proteam@latest" %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %}
+{% if currentVersion == "free-proteam@latest" %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %}
 
 {% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您不能在 {% data variables.product.product_name %} 上{% if currentVersion == "free-pro-team@latest" %}或使用 API{% endif %} 管理团队成员资格。
 
@@ -38,7 +38,7 @@ topics:
 
 要管理 {% data variables.product.prodname_dotcom %} 团队（包括连接到 IdP 组的团队）的仓库访问权限，您必须使用 {% data variables.product.product_name %} 进行更改。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。
 
-{% if currentversion == "free proteam@latest" %}您也可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %}
+{% if currentVersion == "free proteam@latest" %}您也可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### 已同步团队成员的要求
@@ -78,7 +78,7 @@ topics:
 
 ### 将 IdP 组连接到团队
 
-将 IdP 组连接到 {% data variables.product.product_name %} 团队时，组中的所有用户都会自动添加到团队中。 {% if currentversion == "github-ae@latest" %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %}
+将 IdP 组连接到 {% data variables.product.product_name %} 团队时，组中的所有用户都会自动添加到团队中。 {% if currentVersion == "github-ae@latest" %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %}
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
@@ -91,7 +91,7 @@ topics:
 
 ### 断开 IdP 组与团队的连接
 
-如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接，则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% if currentversion == "github-ae@latest" %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %}
+如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接，则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% if currentVersion == "github-ae@latest" %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %}
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
index 3d2a40ec3f..80b20a4a23 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md
@@ -36,5 +36,5 @@ versions:
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
 {% data reusables.enterprise-accounts.payment-information-tab %}
-1. 在“Azure subscription（Azure 订阅）”下您要断开连接的订阅 ID 右侧，单击 **{% octicon "trashcan" aria-label="The trashcan icon" %}**。
+1. 在“Azure subscription（Azure 订阅）”下您要断开连接的订阅 ID 右侧，单击 **{% octicon "trash" aria-label="The trash icon" %}**。
 1. 查看提示，然后单击 **Remove（删除）**。
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
index 94c796399e..55c650be66 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md
@@ -48,3 +48,19 @@ topics:
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.github-actions.private-repository-forks-configure %}
+
+### 为您的企业设置 `GITHUB_TOKENN` 的权限
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+您可以在企业、组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在企业设置中选择受限制的选项为默认值，这将防止在组织或仓库设置中选择更多的允许设置。
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### 配置默认 `GITHUB_TOKENN` 权限
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 ![为此企业设置 GITHUB_TOKENN 权限](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. 单击 **Save（保存）**以应用设置。
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md
index 51d958643a..d8ea22db29 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md
@@ -18,6 +18,7 @@ topics:
 
 {% topic_link_in_list /managing-your-enterprise-account %}
     {% link_in_list /about-enterprise-accounts %}
+    {% link_in_list /verifying-or-approving-a-domain-for-your-enterprise-account %}
     {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
     {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
     {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
@@ -42,8 +43,7 @@ topics:
     {% link_in_list /enforcing-project-board-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
     {% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
-    {% link_in_list /verifying-your-enterprise-accounts-domain %}
-    {% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
+    {% link_in_list /restricting-email-notifications-for-your-enterprise-account %}
     {% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
     {% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
     {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
new file mode 100644
index 0000000000..5b90849fb9
--- /dev/null
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account.md
@@ -0,0 +1,23 @@
+---
+title: 限制企业帐户的电子邮件通知
+intro: You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise account.
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Policy
+---
+
+### 关于企业帐户的电子邮件限制
+
+{% data reusables.enterprise-accounts.email-restrictions-about %}
+
+### 限制企业帐户的电子邮件通知
+
+{% data reusables.enterprise-accounts.email-restrictions-restricting %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
new file mode 100644
index 0000000000..f8f29ccfd6
--- /dev/null
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account.md
@@ -0,0 +1,38 @@
+---
+title: Verifying or approving a domain for your enterprise account
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of organizations owned by your enterprise account.'
+product: '{% data reusables.gated-features.enterprise-accounts %}'
+versions:
+  free-pro-team: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### 关于域验证
+
+{% data reusables.enterprise-accounts.domains-about-verification %}
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.domains-about-approval %}
+
+### Verifying a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-verifying %}
+
+### Approving a domain for your enterprise account
+
+{% data reusables.enterprise-accounts.domains-approving %}
+
+### Removing an approved or verified domain
+
+{% data reusables.enterprise-accounts.domains-removing %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index c4f9b76a97..459b6c559f 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -20,6 +20,15 @@ topics:
 
 {% data reusables.saml.about-linked-identities %}
 
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs.
+
+{% endwarning %}
+
 {% data reusables.identity-and-permissions.revoking-identity-team-sync %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
index 00b83bf904..ea1f5b79e0 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md
@@ -14,7 +14,7 @@ topics:
 
 您可以选择为组织添加说明、地点、网站和电子邮件地址，以及将重要仓库固定于页面顶部。
 
-{% if currentVersion == "free-pro-team@latest" %}要确认组织的身份并在组织资料页面显示“已验证”徽章，必须使用 {% data variables.product.product_name %} 验证组织的域。 更多信息请参阅“[验证组织的域](/organizations/managing-organization-settings/verifying-your-organizations-domain)”。
+{% if currentVersion == "free-pro-team@latest" %}要确认组织的身份并在组织资料页面显示“已验证”徽章，必须使用 {% data variables.product.product_name %} 验证组织的域。 For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 ![验证过的组织资料页面示例](/assets/images/help/profile/org_profile_verified.png)
 {% else %}
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
index eeecbc10fb..264443bc7a 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/personalizing-your-profile.md
@@ -104,23 +104,99 @@ topics:
 
 当您参与某些计划时， {% data variables.product.prodname_dotcom %} 会自动在您的个人资料中显示徽章。
 
-| 徽章                                                              | 计划                                                           | 描述                                                                                                                                                                                                                                                  |
-| --------------------------------------------------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| {% octicon "north-star" aria-label="The North Star icon" %}     | **{% data variables.product.prodname_arctic_vault %} 贡献者** | 如果您在存档于 2020 Arctic Vault 计划的仓库默认分支上编写了任何提交，您的个人资料上会获得一个 {% data variables.product.prodname_arctic_vault %} 贡献者徽章。 有关该计划的更多信息，请参阅 [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com)。                             |
-| {% octicon "cpu" aria-label="The Developer Program icon" %}     | **开发者计划成员**                                                  | 如果您是 GitHub 开发者计划的注册成员，使用 GitHub API 构建应用程序后，您的个人资料上将获得开发者计划成员徽章。 有关 GitHub 开发者计划的更多信息，请参阅 [GitHub 开发者](/program/)。                                                                                                                                 |
-| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **GitHub 赞助者**                                               | 如果您通过 {% data variables.product.prodname_sponsors %} 赞助了开源贡献者，您的个人资料中将获得一个 GitHub Sponge 徽章。 更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”。                             |
-| {% octicon "star-fill" aria-label="The star icon" %}            | **Pro**                                                      | 如果您使用 {% data variables.product.prodname_pro %}，您的个人资料中将获得一个 PRO 徽章。 有关 {% data variables.product.prodname_pro %} 的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products#github-pro)”。 |
+| 徽章                                                                                                            | 计划                                                           | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter 贡献者徽章图标](/assets/images/help/profile/badge-mars-2020-small.png)                        | **Mars 2020 Helicopter 贡献者**                                 | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. 悬停在徽章上会显示您参与的任务中使用的几个仓库。 要查看符合您徽章资格的完整仓库列表，请参阅“[Mars 2020 Helicopter 贡献者徽章的合格仓库列表](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)”。 |
+| ![Arctic Code Vault 贡献者徽章图标](/assets/images/help/profile/badge-arctic-code-vault-small.png)                   | **{% data variables.product.prodname_arctic_vault %} 贡献者** | 如果您在存档于 2020 Arctic Vault 计划的仓库默认分支上编写了任何提交，您的个人资料上会获得一个 {% data variables.product.prodname_arctic_vault %} 贡献者徽章。 悬停在徽章上显示您参与的属于计划一部分的几个仓库。 有关该计划的更多信息，请参阅 [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com)。                                                                                                                                                                                                                         |
+| ![{% data variables.product.prodname_dotcom %} 赞助者徽章图标](/assets/images/help/profile/badge-sponsors-small.png) | **{% data variables.product.prodname_dotcom %} 赞助者**         | 如果您通过 {% data variables.product.prodname_sponsors %} 赞助了开源贡献者，您的个人资料中将获得一个 {% data variables.product.prodname_dotcom %} 赞助者徽章。 单击徽章将带您到个人资料的 **Sponsoring（赞助）**选项卡。 更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”。                                                                                                                                                                          |
+| {% octicon "cpu" aria-label="The Developer Program icon" %}                                                   | **开发者计划成员**                                                  | 如果您是 {% data variables.product.prodname_dotcom %} 开发者计划的注册成员，使用 {% data variables.product.prodname_dotcom %} API 构建应用程序，您的个人资料上将获得开发者计划成员徽章。 有关 {% data variables.product.prodname_dotcom %} 开发者计划的更多信息，请参阅 [GitHub 开发者](/program/)。                                                                                                                                                                                                                                    |
+| {% octicon "star-fill" aria-label="The star icon" %}                                                          | **Pro**                                                      | 如果您使用 {% data variables.product.prodname_pro %}，您的个人资料中将获得一个 PRO 徽章。 有关 {% data variables.product.prodname_pro %} 的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products#github-pro)”。                                                                                                                                                                                                                       |
 
 ### 在个人资料中禁用徽章
 
-您可以对您参与的 {% data variables.product.prodname_dotcom %} 计划禁用某些徽章，包括 PRO 和 {% data variables.product.prodname_arctic_vault %} 徽章。
+您可以对您参与的 {% data variables.product.prodname_dotcom %} 计划禁用某些徽章，包括 PRO、{% data variables.product.prodname_arctic_vault %} 和 Mars 2020 Helicopter 贡献者徽章。
 
 {% data reusables.user_settings.access_settings %}
-2. 在“Profile settings（个人资料设置）”下，取消选择您想要禁用的徽章。 ![不再在个人资料中显示徽章的复选框](/assets/images/help/profile/display-pro-badge-checkbox.png)
+2. 在“Profile settings（个人资料设置）”下，取消选择您想要禁用的徽章。 ![不再在个人资料中显示徽章的复选框](/assets/images/help/profile/profile-badge-settings.png)
 3. 单击 **Update preferences（更新首选项）**。
 
 {% endif %}
 
+### Mars 2020 Helicopter 贡献者徽章的合格仓库列表
+
+如果您为下面一个或多个仓库列出的标记撰写了提交历史记录中的任何提交，您的个人资料中将获得 Mars 2020 Helicopter 贡献者徽章。 撰写的提交必须有验证过的电子邮件地址，该电子邮件地址在 {% data variables.product.prodname_dotcom %} 确定符合条件的贡献时与您帐户关联，表示该贡献归属于您。 将来对经过验证的电子邮件的更改不会对徽章产生影响。 我们根据从美国航天局喷气推进实验室获得的资料编制了清单。
+
+| {% data variables.product.prodname_dotcom %} 仓库                               | 版本        | 标记                                                                                                         |
+| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| [torvalds/linux](https://github.com/torvalds/linux)                           | 3.4       | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4)                                                |
+| [python/cpython](https://github.com/python/cpython)                           | 3.9.2     | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2)                                            |
+| [boto/boto3](https://github.com/boto/boto3)                                   | 1.17.17   | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17)                                              |
+| [boto/botocore](https://github.com/boto/botocore)                             | 1.20.11   | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11)                                           |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi)           | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05)                            |
+| [chardet/chardet](https://github.com/chardet/chardet)                         | 4.0.0     | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0)                                             |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler)                     | 0.10.0    | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0)                                       |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py)       | 6.8.1     | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1)                                    |
+| [ianare/exif-py](https://github.com/ianare/exif-py)                           | 2.3.2     | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2)                                              |
+| [kjd/idna](https://github.com/kjd/idna)                                       | 2.10      | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10)                                                    |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py)               | 0.10.0    | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0)                                      |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi)                               | 1.3.1     | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1)                                                |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib)             | 3.3.4     | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4)                                     |
+| [numpy/numpy](https://github.com/numpy/numpy)                                 | 1.20.1    | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1)                                             |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python)               | 4.5.1.48  | [48](https://github.com/opencv/opencv-python/releases/tag/48)                                              |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow)               | 8.1.0     | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0)                                        |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl)                             | 7.43.0.6  | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6)                             |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.7     | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7)                     |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial)                     | 3.5       | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5)                                             |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil)                     | 2.8.1     | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1)                                           |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml)                                | 5.4.1     | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1)                                                 |
+| [psf/requests](https://github.com/psf/requests)                               | 2.25.1    | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1)                                            |
+| [boto/s3transfer](https://github.com/boto/s3transfer)                         | 0.3.4     | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4)                                             |
+| [enthought/scimath](https://github.com/enthought/scimath)                     | 4.2.0     | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0)                                           |
+| [scipy/scipy](https://github.com/scipy/scipy)                                 | 1.6.1     | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1)                                               |
+| [benjaminp/six](https://github.com/benjaminp/six)                             | 1.15.0    | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0)                                             |
+| [enthought/traits](https://github.com/enthought/traits)                       | 6.2.0     | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0)                                            |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3)                         | 1.26.3    | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3)                                           |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs)                   | 19.3.0    | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0)                                        |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/)    | 3.2.4     | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4)                                   |
+| [pallets/click](https://github.com/pallets/click)                             | 7.0       | [7.0](https://github.com/pallets/click/releases/tag/7.0)                                                   |
+| [pallets/flask](https://github.com/pallets/flask)                             | 1.1.1     | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1)                                               |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7     | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7)                                 |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig)               | 1.0.0     | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0)                                      |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous)               | 1.1.0     | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0)                                        |
+| [pallets/jinja](https://github.com/pallets/jinja)                             | 2.10.3    | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3)                                             |
+| [lxml/lxml](https://github.com/lxml/lxml)                                     | 4.4.1     | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1)                                         |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown)       | 3.1.1     | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1)                                    |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe)                   | 1.1.1     | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1)                                          |
+| [pypa/packaging](https://github.com/pypa/packaging)                           | 19.2      | [19.2](https://github.com/pypa/packaging/releases/tag/19.2)                                                |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect)                         | 4.7.0     | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0)                                             |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy)                     | 0.13.0    | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0)                                         |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess)                   | 0.6.0     | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0)                                          |
+| [pytest-dev/py](https://github.com/pytest-dev/py)                             | 1.8.0     | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0)                                               |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing)                 | 2.4.5     | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5)                     |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest)                     | 5.3.0     | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0)                                           |
+| [stub42/pytz](https://github.com/stub42/pytz)                                 | 2019.3    | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3)                               |
+| [uiri/toml](https://github.com/uiri/toml)                                     | 0.10.0    | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0)                                                 |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug)                       | 0.16.0    | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0)                                          |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable)         | 1.2       | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2)                                       |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic)   | 2.9.1.1   | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1)                    |
+| [nasa/fprime](https://github.com/nasa/fprime)                                 | 1.3       | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3)                                         |
+| [nucleic/cppy](https://github.com/nucleic/cppy)                               | 1.1.0     | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0)                                                |
+| [opencv/opencv](https://github.com/opencv/opencv)                             | 4.5.1     | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1)                                               |
+| [curl/curl](https://github.com/curl/curl)                                     | 7.72.0    | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0)                                     |
+| [madler/zlib](https://github.com/madler/zlib)                                 | 1.2.11    | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11)                                             |
+| [apache/lucene](https://github.com/apache/lucene)                             | 7.7.3     | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml)                               | 0.2.5     | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5)                                                |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch)             | 6.8.1     | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1)                                     |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap)                           | 4.3.1     | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1)                                            |
+| [vuejs/vue](https://github.com/vuejs/vue)                                     | 2.6.10    | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10)                                               |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc)                     | 0.7.1     | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1)                                           |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time)                     | 2.10.1    | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1)                                       |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest)                     | 3.2       | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2)                             |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram)     | 2.1.9     | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9)         |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j)           | 0.7       | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7)                      |
+| [locationtech/jts](https://github.com/locationtech/jts)                       | 1.15.0    | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0)                                  |
+| [apache/log4j](https://github.com/apache/log4j)                               | 2.11      | [v1_2_11](https://github.com/apache/log4j/releases/tag/v1_2_11)                                          |
+
 ### 延伸阅读
 
 - "[关于个人资料](/articles/about-your-profile)"
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
index d24cff4d9f..ff746fa377 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address.md
@@ -22,7 +22,7 @@ topics:
 3. 如果要添加新电子邮件地址以设置为您的主电子邮件地址，请在“Add email address（添加电子邮件地址）”下，键入新的电子邮件地址，然后单击 **Add（添加）**。 ![添加其他电子邮件地址按钮](/assets/images/help/settings/add_another_email_address.png)
 4. 在“Primary email address（主电子邮件地址）”下，使用下拉菜单，单击要设为主电子邮件地址的电子邮件地址，然后单击 **Save（保存）**。 ![设为主电子邮件地址按钮](/assets/images/help/settings/set_as_primary_email.png)
 5. 要从帐户中删除旧电子邮件地址，请在旧电子邮件地址旁边单击
-{% octicon "trashcan" aria-label="The trashcan symbol" %}.
+{% octicon "trash" aria-label="The trash symbol" %}。
 {% if currentVersion == "free-pro-team@latest" %}
 6. 验证新的主电子邮件地址。 如果没有经验证的电子邮件地址，您将无法使用所有
 {% data variables.product.product_name %} 的功能。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md
index 4f2333fc86..e4c7b3f125 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md
@@ -58,5 +58,5 @@ topics:
 
 ### 延伸阅读
 - "[设置团队](/articles/setting-up-teams)"
-{% if currentversion == "free proteam@latest" %}-"[邀请用户加入您的组织](/articles/inviting-users-to-join-your-organization)"{% endif %}
+{% if currentVersion == "free proteam@latest" %}-"[邀请用户加入您的组织](/articles/inviting-users-to-join-your-organization)"{% endif %}
 - “[访问组织](/articles/accessing-an-organization)”
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md
index eaf71cb8cb..acaf387fd0 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md
@@ -25,4 +25,4 @@ topics:
 
 ### 延伸阅读
 
-- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)"
+- "[管理组织中仓库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)"
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
index 831eb37c90..c320f960bc 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md
@@ -7,17 +7,14 @@ topics:
   - Accounts
 ---
 
-{% note %}
-
-**注意：**主题设置目前处于测试阶段，可能会更改。
-
-{% endnote %}
-
-为了选择和灵活地使用 {% data variables.product.product_name %}，您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择，也可以配置 {% data variables.product.product_name %} 遵循系统设置。 有些开发者出于个人喜好使用深色主题，以减少某些设备的功耗，或者在低光条件下减少眼睛疲劳。
+为了选择和灵活地使用 {% data variables.product.product_name %}，您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择，也可以配置 {% data variables.product.product_name %} 遵循系统设置。 您可能需要使用深色主题来减少某些设备的功耗，以在低光条件下减小眼睛的压力，或者因为您更喜欢主题的外观。
 
 {% data reusables.user_settings.access_settings %}
 1. 在用户设置侧边栏中，单击 **Appearance（外观）**。 ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png)
-1. 在“Theme（主题）”下，选择主题首选项。 ![主题设置的单选按钮](/assets/images/help/settings/theme-settings-radio-buttons.png)
+1. 在“Theme mode（主题模式）”下，选择下拉菜单，然后单击主题首选项。 !["主题模式"下的下拉菜单用于选择主题首选项](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. 单击想要使用的主题。
+    - 如果您选择单个主题，请单击一个主题。 ![用于选择单个主题的单选按钮](/assets/images/help/settings/theme-choose-a-single-theme.png)
+    - 如果您选择遵循系统设置，请单击白天主题和夜间主题。 ![用于选择主题以与系统设置同步的按钮](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png)
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
index 108ae83fed..f3ea8b3ea4 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md
@@ -32,7 +32,7 @@ topics:
 | {% if currentVersion == "free-pro-team@latest" %}邀请协作者{% else %}添加协作者{% endif %}                                                                                                            |                                                                                                                                                                                                                                                                                             |
 | "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)"                                                                    |                                                                                                                                                                                                                                                                                             |
 | 更改仓库的可见性                                                                                                                                                                                    | “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” |{% if currentVersion == "free-pro-team@latest" %}
-| 限制与仓库的交互                                                                                                                                                                                    | “[限制仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”|{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| 限制与仓库的交互                                                                                                                                                                                    | “[限制仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”|{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | 重命名分支，包括默认分支                                                                                                                                                                                | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | 合并受保护分支上的拉取请求（即使没有批准审查）                                                                                                                                                                     | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)"                                                                                                                                                                                                                    |
@@ -70,7 +70,7 @@ topics:
 
 | 操作                          | 更多信息                                                                                                                                                                                                                                                                  |
 |:--------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 复刻仓库                        | “[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)”|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| 复刻仓库                        | “[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)”|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | 重命名除默认分支以外的分支               | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" 
 {% endif %}
 | 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 | <ul><li>"[关于议题](/github/managing-your-work-on-github/about-issues)"</li><li>"[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                                                                             |
diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
index 99393c930b..6d16ef7108 100644
--- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository.md
@@ -29,7 +29,7 @@ topics:
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.repositories.navigate-to-manage-access %}
 4. 在要删除的协作者右边，单击
-{% octicon "trashcan" aria-label="The trashcan icon" %}.
+{% octicon "trash" aria-label="The trash icon" %}.
   ![用于删除协作者的按钮](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
 3. 在左侧边栏中，单击 **Collaborators & teams（协作者和团队）**。 ![协作者选项卡](/assets/images/help/repository/repo-settings-collaborators.png)
diff --git a/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md b/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md
index 07338d7a21..e7dc10f66b 100644
--- a/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md
+++ b/translations/zh-CN/content/github/site-policy/github-corporate-terms-of-service.md
@@ -9,6 +9,8 @@ topics:
   - Legal
 ---
 
+_这些条款适用于 1) 已接受《公司服务条款》的 GitHub.com（非企业）客户，以及 2) 在 2021 年 1 月 4 日之前已获得服务许可的企业客户。 在此日期之后购买产品或服务的企业客户将被定向至 https://github.com/enterprise-legal 了解当前条款。_
+
 感谢您选择 GitHub 满足贵公司的业务需求。 请仔细阅读本协议，因为它管辖对产品（定义如下）的使用，除非 GITHUB 在这方面与客户签订了单独的书面协议。 单击“I AGREE（我同意）”或类似按钮或者使用产品，即表示客户接受本协议的所有条款和条件。 如果客户代表公司或其他法律实体签订本协议，则表示其拥有让该公司或其他法律实体受本协议约束的法律权限。
 
 ### GitHub 公司服务条款
diff --git a/translations/zh-CN/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/zh-CN/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
index 2fcc792aab..fe27ae122c 100644
--- a/translations/zh-CN/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
+++ b/translations/zh-CN/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md
@@ -1,7 +1,6 @@
 ---
 title: 组织的 GitHub Insights 和数据保护
 intro: '{% data variables.product.prodname_insights %} 会分析您的 {% data variables.product.prodname_ghe_server %} 数据。 这些数据可能包括贵组织中有权了解如何使用个人数据之人的个人数据。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
   - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
@@ -14,8 +13,6 @@ topics:
   - Legal
 ---
 
-有关 {% data variables.product.prodname_insights %} 管制条款的更多信息，请参阅您的 {% data variables.product.prodname_ghe_one %} 订阅协议。
-
 为了避免产生疑问，上述任何信息都不应被视为 {% data variables.product.prodname_dotcom %} 提供的法律建议。 您有责任对这里提供的信息进行法律分析，并遵守隐私和数据保护法律。 是否使用 {% data variables.product.prodname_insights %} 来处理您的员工和用户的数据，完全由您决定，如果您选择处理，则要自行负责按照适用的法律进行处理。
 
 ### 组织的角色和责任
diff --git a/translations/zh-CN/content/github/site-policy/github-privacy-statement.md b/translations/zh-CN/content/github/site-policy/github-privacy-statement.md
index fad82bfbdd..91e0f6a68e 100644
--- a/translations/zh-CN/content/github/site-policy/github-privacy-statement.md
+++ b/translations/zh-CN/content/github/site-policy/github-privacy-statement.md
@@ -64,7 +64,7 @@ topics:
 ##### 支付信息
 如果您注册我们的付费帐户、通过 GitHub 赞助计划汇款或在 GitHub Marketplace 上购买应用程序，我们将收集您的全名、地址和信用卡信息或 PayPal 信息。 请注意，GitHub 不会处理或存储您的信用卡信息或 PayPal 信息，但我们的第三方付款处理商会这样做。
 
-如果您在 [GitHub Marketplace](https://github.com/marketplace) 上列出并销售应用程序，我们需要您的银行信息。 如果您通过 [GitHub 赞助计划](https://github.com/sponsors)筹集资金，我们需要您在注册过程中提供一些[其他信息](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information)，以便您参与这些服务并通过这些服务获取资金以及满足合规要求。
+如果您在 [GitHub Marketplace](https://github.com/marketplace) 上列出并销售应用程序，我们需要您的银行信息。 如果您通过 [GitHub 赞助计划](https://github.com/sponsors)筹集资金，我们需要您在注册过程中提供一些[其他信息](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information)，以便您参与这些服务并通过这些服务获取资金以及满足合规要求。
 
 ##### 个人资料信息
 您可以选择在帐户个人资料中向我们提供更多信息，例如您的全名、头像等，可包括照片、简历、地理位置、公司和第三方网站的 URL。 此类信息可能包括用户个人信息。 请注意，您的个人资料信息可能对我们服务的其他用户显示。
diff --git a/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md
index c3b8961b3f..84283ee2fd 100644
--- a/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md
+++ b/translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md
@@ -13,7 +13,7 @@ topics:
   - Legal
 ---
 
-Effective date: **April 2, 2021**
+生效日期：**2021 年 4 月 2 日**
 
 GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享您的数据方面提供很大的透明度。 为此，我们提供此页面，以详细介绍了我们的[子处理商](#github-subprocessors)，以及我们如何使用 [cookie](#cookies-on-github)。
 
diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
index 1a66878f1a..db59c3b20b 100644
--- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
+++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md
@@ -1,89 +1,76 @@
 ---
-title: About the dependency graph
-intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.'
+title: 关于依赖项图
+intro: 有关依赖关系图、它支持的生态系统及其如何确定仓库所依赖的软件包的详细信息。
 versions:
-  free-pro-team: '*'
-  enterprise-server: '*'
+  enterprise-server: <=2.22
+topics:
+  - Repositories
 ---
 
-### Dependency graph availability
+<!--See /content/code-security/supply-chain-security/about-the-dependency-graph for the latest version of this article -->
 
-The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+### 依赖关系图可用性
+
+依赖关系图可用于使用支持的文件格式在支持的包生态系统中定义依赖关系的每个仓库。
 
 {% data reusables.repositories.enable-security-alerts %}
 
-### About the dependency graph
+### 关于依赖项图
 
-The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}:
+依赖项图是存储在仓库中的清单和锁定文件的摘要。 对于每个仓库，它会显示依赖项，即它所依赖的生态系统和包。 {% data variables.product.prodname_ghe_server %} 不计算有关依赖项、仓库和依赖于仓库的包的信息。
 
-- Dependencies, the ecosystems and packages it depends on
-- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+当您将提交推送到 {% data variables.product.product_name %} 以更改或添加受支持的清单或锁定文件到默认分支时，依赖关系图将自动更新。 有关受支持的生态系统和清单文件的信息，请参阅下面的“["支持的包生态系统](#supported-package-ecosystems)”。
 
-When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+### 包含的依赖项
 
-{% if currentVersion == "free-pro-team@latest" %}
-When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
-{% endif %}
+依赖关系图包括清单和锁定文件中详述的所有依赖项，或支持的生态系统的同等项。 这包括：
 
-### Dependencies included
+- 在清单或锁定文件中明确定义的直接依赖项
+- 这些直接依赖项的间接依赖项，也称为过渡依赖项或子依赖项
 
-The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
+依赖关系图可识别间接依赖项。
 
-- Direct dependencies, that are explicitly defined in a manifest or lock file
-- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+### 使用依赖关系图
 
-The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+您可以使用依赖关系图：
 
-{% if currentVersion == "free-pro-team@latest" %}
-### Dependents included
+- 浏览代码所依赖的仓库。 更多信息请参阅“[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)”。
+- 查看和更新仓库中有漏洞的依赖项。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
 
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+### 启用依赖关系图
 
-### Using the dependency graph
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}如果依赖项图在系统中不可用，则站点管理员可以启用依赖项图和 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上的有漏洞依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。{% endif %}
 
-You can use the dependency graph to:
-
-- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %}
-- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
-- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
-
-### Enabling the dependency graph
-
-{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
-
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
-
-{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 如果依赖项图在系统中不可用，则站点管理员可以启用依赖项图和安全警报。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。
 
 {% endif %}
 
-When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}.
+首次启用依赖关系图时，将立即剖析受支持的生态系统的任何清单和锁定文件。 依赖关系图通常在几分钟之内填充，但对于依赖项很多的仓库，可能需要更长时间。 启用后，每次推送到仓库时，依赖关系图都会自动更新。
 
-### Supported package ecosystems
+### 支持的包生态系统
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported packages. -->
 
-The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %}
+建议的格式明确定义哪些版本用于所有直接和所有间接依赖项。 如果使用这些格式，则依赖关系图更准确。 它还会反映当前的构建设置，使依赖关系图能够报告直接和间接依赖项中的漏洞。
 
-| Package manager | Languages | Recommended formats | All supported formats |
-| --- | --- | --- | ---|
-| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
-| `dotnet` CLI | .NET languages (C#, C++, F#, VB)  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
-| 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.lock`, `setup.py`* |
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+下面列出的生态系统支持依赖关系图和 {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。
+
+| 包管理器         | 语言                    | 建议的格式                                              | 所有支持的格式                                                              |
+| ------------ | --------------------- | -------------------------------------------------- | -------------------------------------------------------------------- |
+| Composer     | PHP                   | `composer.lock`                                    | `composer.json`、`composer.lock`                                      |
+| `dotnet` CLI | .NET 语言（C#、C++、F#、VB） | `.csproj`、`.vbproj`、`.nuspec`、`.vcxproj`、`.fsproj` | `.csproj`、`.vbproj`、`.nuspec`、`.vcxproj`、`.fsproj`、`packages.config` |
+| 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`*              |
+| RubyGems     | Ruby                  | `Gemfile.lock`                                     | `Gemfile.lock`、`Gemfile`、`*.gemspec`                                 |
+| Yarn         | JavaScript            | `yarn.lock`                                        | `package.json`、`yarn.lock`                                           |
 
 {% note %}
 
-**Note:** 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.
+**注：**如果在 `setup.py` 文件中列出 Python 依赖项，我们可能无法剖析和列出项目中的每个依赖项。
 
 {% endnote %}
 
-### Further reading
+### 延伸阅读
 
-- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
-- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %}
-- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)"
-- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %}
+- 维基百科上的“[依赖关系图](https://en.wikipedia.org/wiki/Dependency_graph)”
+- "[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
index e8b1718a86..4247595c3f 100644
--- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
+++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md
@@ -7,29 +7,20 @@ topics:
   - Repositories
 ---
 
+<!--See /content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository for the latest version of this article -->
+
 ### 查看依赖关系图
 
 {% data reusables.repositories.enable-security-alerts %}
 
-依赖项图显示仓库的依赖项{% if currentVersion == "free-pro-team@latest" %}和依赖关系{% endif %}。 有关依赖项检测以及支持哪些生态系统的信息，请参阅“[关于依赖关系图”](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)。
+依赖关系图显示仓库的依赖项。 有关依赖项检测以及支持哪些生态系统的信息，请参阅“[关于依赖关系图”](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %}
-4. （可选）在 "Dependency graph"（依赖关系图）下，单击 **Dependents（依赖项）**。 ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+{% data reusables.repositories.click-dependency-graph %}
 
 #### 依赖项视图
 
-{% if currentVersion == "free-pro-team@latest" %}
-依赖项按生态系统分组。 您可以展开依赖项以查看其依赖项。 对于托管在
-{% data variables.product.product_name %} 上的公共仓库中的依赖项，您也可以单击依赖来查看仓库。 私有仓库、私有包或无法识别文件上的依赖项以纯文本显示。
-
-如果在仓库中检测到漏洞，这些漏洞将显示在视图顶部，供有权访问 {% data variables.product.prodname_dependabot_alerts %} 的用户查看。
-
-![依赖关系图](/assets/images/help/graphs/dependencies_graph.png)
-
-{% endif %}
-
 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
 在仓库的清单或锁定文件中指定的任何直接或间接依赖项按生态系统分组列出。 如果在仓库中检测到漏洞，这些漏洞将显示在视图顶部，供有权访问的用户查看
 {% data variables.product.prodname_dependabot_alerts %} 的通知。
@@ -57,59 +48,8 @@ topics:
 
 {% endif %}
 
-{% if currentVersion == "free-pro-team@latest" %}
-#### 依赖项视图
-
-对于公共仓库，依赖项视图显示其他仓库如何使用该仓库。 要在包管理器中仅显示包含存储库的仓库，请单击依赖的仓库列表正上方的**编号包**。 依赖项计数是近似值，不一定与列出的依赖项匹配。
-
-![从属者图](/assets/images/help/graphs/dependents_graph.png)
-
-### 为私有仓库启用或禁用依赖关系图
-
-仓库管理员可以启用或禁用私有仓库的依赖关系图。
-
-您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 更多信息请参阅“[管理用户帐户的安全和分析设置](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)”或“[管理组织的安全和分析设置](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)”。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. 阅读有关授予 {% data variables.product.product_name %} 只读访问仓库数据的消息，以启用依赖关系图，然后在“Dependency Graph（依赖关系图）”旁边单击 **Enable（启用）**。 ![依赖关系图的"启用"按钮](/assets/images/help/repository/dependency-graph-enable-button.png)
-
-您可以随时单击 Security & analysis（安全性和分析）选项卡上“Dependency Graph（依赖关系图）”旁边的 **Disable（禁用）**来禁用依赖关系图。
-
-### 更改“Used by（使用者）”包
-
-如果启用了依赖项图，并且您的仓库包含已发布在受支持包生态系统上的包，则 {% data variables.product.prodname_dotcom %} 将在仓库的 **Code（代码）**选项卡的边栏中显示“Used by（使用者）”部分。 有关受支持包生态系统的更多信息，请参阅“[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。
-
-“Used by（使用者）”部分显示已发现对包的公开引用数量，并显示某些依赖项所有者的头像。
-
-!["使用者"边栏部分](/assets/images/help/repository/used-by-section.png)
-
-单击此部分的任何项都会转到依赖项图的 **Dependents（依赖项）**选项卡。
-
-“Used by（使用者）”部分表示仓库中的单个包。 如果您对包含多个包的仓库拥有管理员权限，您可以选择“Used by（使用者）”部分表示哪个包。
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
-4. 在“Configure security and analysis features（配置安全和分析功能）”下，单击“Used by counter（使用者计数）”部分中的下拉菜单并选择一个包。 ![选择"使用者"包](/assets/images/help/repository/choose-used-by-package.png)
-
-{% endif %}
-
 ### 依赖项图疑难排解
 
 如果依赖关系图为空，则包含依赖项的文件可能有问题。 检查该文件以确保其格式对文件类型是正确的。
 
-{% if currentVersion == "free-pro-team@latest" %}
-如果文件格式正确，请检查文件大小。 依赖项图忽略单个清单并锁定超过 0.5 Mb 的文件，除非您是
-{% data variables.product.prodname_enterprise %} 用户。 默认情况下，每个仓库最多处理 20 个清单或锁定文件，因此您可以在仓库子目录中将依赖项拆分为较小的文件。{% endif %}
-
 如果清单或锁定文件未获处理，其依赖项将从依赖关系图中省略，而不能接受有漏洞依赖项的检查。
-
-### 延伸阅读
-
-- "[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %}
-- "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"
-- "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"
-- "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/github/understanding-how-github-uses-and-protects-your-data)"
-{% endif %}
diff --git a/translations/zh-CN/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/zh-CN/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
index b847adec32..74d2358e12 100644
--- a/translations/zh-CN/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
 title: 关于 GitHub Enterprise Cloud 的 GitHub 高级支持
-intro: '{% data variables.contact.premium_support %} 是向 {% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_one %} 客户提供的一种付费、补充支持服务。'
+intro: '{% data variables.contact.premium_support %} 是向 {% data variables.product.prodname_ghe_cloud %} 客户提供的一种付费、补充服务。'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
diff --git a/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md b/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md
index 46448e0eaa..63c3e9370c 100644
--- a/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md
+++ b/translations/zh-CN/content/github/writing-on-github/autolinked-references-and-urls.md
@@ -21,7 +21,7 @@ versions:
 
 ### 议题和拉取请求
 
-在 {% data variables.product.product_name %} 上的对话中，对议题和拉取请求的引用将自动转换为缩短的链接。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的对话](/articles/about-conversations-on-github)”。
+在 {% data variables.product.product_name %} 上的对话中，对议题和拉取请求的引用将自动转换为缩短的链接。
 
 {% note %}
 
diff --git a/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
index 31a30f81c6..35d7c237a0 100644
--- a/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/zh-CN/content/github/writing-on-github/basic-writing-and-formatting-syntax.md
@@ -23,7 +23,7 @@ versions:
 
 ### 样式文本
 
-您可以使用粗体、斜体或删除线文本来表示强调。
+您可以在评论字段和 `.md` 文件中以粗体、斜体或删除线的文字表示强调。
 
 | 样式       | 语法                | 键盘快捷键      | 示例                 | 输出               |
 | -------- | ----------------- | ---------- | ------------------ | ---------------- |
@@ -205,6 +205,10 @@ git commit
 
 有关构建使用内容附件的 {% data variables.product.prodname_github_app %} 的详细信息，请参阅“[使用内容附件](/apps/using-content-attachments)”。
 
+### 上传资产
+
+您可以通过拖放、从文件浏览器中选择或粘贴来上传图像等资产。 您可以将资产上传到议题、拉取请求、评论和仓库中的 `.md` 文件。
+
 ### 使用表情符号
 
 通过键入 `:EMOJICODE:` 可在您的写作中添加表情符号。
diff --git a/translations/zh-CN/content/github/writing-on-github/creating-and-highlighting-code-blocks.md b/translations/zh-CN/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
index a59b4eb925..b6f9656884 100644
--- a/translations/zh-CN/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
+++ b/translations/zh-CN/content/github/writing-on-github/creating-and-highlighting-code-blocks.md
@@ -30,6 +30,7 @@ function test() {
 {% endtip %}
 
 ### 语法突显
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
 您可以添加可选的语言标识符，以在围栏代码块中启用语法突显。
 
diff --git a/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md
index fd66d4cbef..1458118011 100644
--- a/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -1081,4 +1081,4 @@ mutation {
 
 ## 搜索
 
-讨论可从顶层`搜索`字段返回。 要搜索讨论，请将`类型`指定为 `DISCUSSION`。 `SearchResultItemConnect` 类型有一个 `discussionCount` 字段来报告返回的讨论数。`讨论`类型已添加到 `SearchResultItem` 并集。 更多信息请参阅“[查询](/graphql/reference/queries#searchresultitemconnection)”。
+讨论可从顶层`搜索`字段返回。 要搜索讨论，请将`类型`指定为 `DISCUSSION`。 `SearchResultItemConnect` 类型有一个 `discussionCount` 字段来报告返回的讨论数。`讨论`类型已添加到 `SearchResultItem` 并集。 For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)."
diff --git a/translations/zh-CN/content/graphql/overview/breaking-changes.md b/translations/zh-CN/content/graphql/overview/breaking-changes.md
index 0c7ae4afcd..f2755c46dc 100644
--- a/translations/zh-CN/content/graphql/overview/breaking-changes.md
+++ b/translations/zh-CN/content/graphql/overview/breaking-changes.md
@@ -27,7 +27,7 @@ topics:
 
 {% for change in date[1] %}
 <ul>
-<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}border-red bg-red-light{% else %}border-purple bg-purple-light{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> 将对 <code>{{ change.location }}</code> 进行变更。.
+<li><span class="border rounded-1 m-1 p-1 {% if change.criticality == 'breaking' %}color-border-danger color-bg-danger{% else %}color-border-info color-bg-info{% endif %}">{% if change.criticality == 'breaking' %}Breaking{% else %}Dangerous{% endif %}</span> 将对 <code>{{ change.location }}</code> 进行变更。.
 
 <p><b>描述：</b> {{ change.description }}</p>
 
diff --git a/translations/zh-CN/content/graphql/overview/explorer.md b/translations/zh-CN/content/graphql/overview/explorer.md
index b4d07c0939..1d2d21729a 100644
--- a/translations/zh-CN/content/graphql/overview/explorer.md
+++ b/translations/zh-CN/content/graphql/overview/explorer.md
@@ -9,6 +9,6 @@ versions:
   github-ae: '*'
 layout: graphql-explorer
 topics:
-  - api
+  - API
 ---
 
diff --git a/translations/zh-CN/content/graphql/reference/input-objects.md b/translations/zh-CN/content/graphql/reference/input-objects.md
index c5eaf11525..998e367e41 100644
--- a/translations/zh-CN/content/graphql/reference/input-objects.md
+++ b/translations/zh-CN/content/graphql/reference/input-objects.md
@@ -19,6 +19,5 @@ topics:
 
 更多信息请参阅“[关于突变](/graphql/guides/forming-calls-with-graphql#about-mutations)。”
 
-{% for item in graphql.schemaForCurrentVersion.inputObjects %}
-  {% include graphql-input-object %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-input-objects.json -->
diff --git a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
index ea23817aa8..4c52dd9541 100644
--- a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
+++ b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights.md
@@ -1,6 +1,5 @@
 ---
 title: GitHub Insights 可用的指标
-product: '{% data reusables.gated-features.github-insights %}'
 intro: '{% data variables.product.prodname_insights %} 包括各种指标，便于您了解团队的软件交付流程。'
 redirect_from:
   - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
diff --git a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
index f136c42ff4..4e3f369c60 100644
--- a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
+++ b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 在 GitHub Enterprise 与 GitHub Insight 之间导航
 intro: ''
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can navigate between {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_insights %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
index e25ecece41..d222fcbf3c 100644
--- a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
+++ b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 设置 GitHub Insights 的时区
 intro: '您可以设置您在 {% data variables.product.prodname_insights %} 中查看的指标的时区。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can set their own timezone.'
 versions:
   enterprise-server: '*'
diff --git a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
index 130b6275fe..c4e1190c68 100644
--- a/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
+++ b/translations/zh-CN/content/insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: 查看关键指标和报告
 intro: 您可以查看和过滤关键指标和报告，帮助了解并改进通过数据交付软件的过程。
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can view key metrics and reports.'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
index 756b96bf66..4976d25016 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-data-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 关于 GitHub Insights
 intro: '{% data variables.product.prodname_insights %} 指标中包含的数据可高度自定义。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: ''
 versions:
   enterprise-server: '*'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-github-insights.md
index d81df195e9..0c77bfb9f2 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-github-insights.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/about-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 关于 GitHub Insights
 intro: '{% data variables.product.prodname_insights %} 提供指标和分析报告，帮助工程团队了解和改进其软件交付流程。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/about-github-insights
 versions:
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
index 63fd2ec47b..52110d008d 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: 配置 GitHub Insights 与 GitHub Enterprise 之间的连接
 intro: '您可以管理 {% data variables.product.prodname_insights %} 如何连接到 {% data variables.product.prodname_enterprise %}。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can configure the connection to {% data variables.product.prodname_enterprise %}.'
 versions:
   enterprise-server: '*'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
index c4311b322a..35c14cccdf 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: 启用 GitHub Insights 与 GitHub Enterprise 之间的链接
 intro: '您可以启用一个允许用户从 {% data variables.product.prodname_ghe_server %} 导航到 {% data variables.product.prodname_insights %} 的链接。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} can enable a link between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_insights %}.'
 redirect_from:
   - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
index c07147d139..76c29cc7d8 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/installing-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 安装 GitHub Insights
 intro: '您可以安装 {% data variables.product.prodname_insights %} 并将独立应用程序连接到 {% data variables.product.prodname_ghe_server %}。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/installing-github-insights
 permissions: 'Organization owners in {% data variables.product.prodname_enterprise %} with read permissions to the `github/insights-releases` repository and administrative access to the application server can install {% data variables.product.prodname_insights %}.'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
index 70e4f08c38..30fa64d944 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md
@@ -1,7 +1,6 @@
 ---
 title: 管理可用指标和报告
 intro: '您可以在整个 {% data variables.product.prodname_insights %} 中启用和禁用特定指标。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
index eba79c5b93..00adfcae40 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-contributors-and-teams.md
@@ -1,7 +1,6 @@
 ---
 title: 管理贡献者和团队
 intro: 您可以管理指标和报告中包含的人员和团队。
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage contributors and teams.'
@@ -98,7 +97,7 @@ versions:
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.teams-tab %}
 {% data reusables.github-insights.edit-team %}
-3. 在要删除的贡献者的右侧，单击 {% octicon "trashcan" aria-label="The trashcan icon" %}。 ![回收站按钮](/assets/images/help/insights/contributor-trashcan.png)
+3. 在要删除的贡献者的右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 ![回收站按钮](/assets/images/help/insights/contributor-trashcan.png)
 
 #### 重命名自定义团队
 
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-events.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-events.md
index 9be5438fa5..5e9f3a1e5e 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-events.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-events.md
@@ -1,7 +1,6 @@
 ---
 title: 管理事件
 intro: '{% data reusables.github-insights.events %}'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-events
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage events.'
@@ -29,5 +28,5 @@ versions:
 
 {% data reusables.github-insights.settings-tab %}
 {% data reusables.github-insights.events-tab %}
-3. 在要删除的事件的右侧，单击 **{% octicon "trashcan" aria-label="The trashcan icon" %}**。 ![回收站按钮](/assets/images/help/insights/trashcan-button.png)
+3. 在要删除的事件的右侧，单击 **{% octicon "trash" aria-label="The trash icon" %}**。 ![回收站按钮](/assets/images/help/insights/trashcan-button.png)
 4. 单击 **Confirm（确认）**。
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-goals.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-goals.md
index 17437d2aad..7222b49b69 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-goals.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-goals.md
@@ -1,7 +1,6 @@
 ---
 title: 管理目标
 intro: 您可以使用“目标”为关键指标设定目标并衡量实现这些目标的成功率。
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/creating-and-managing-goals
 permissions: 'Anyone with access to {% data variables.product.prodname_insights %} can manage goals.'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-organizations.md
index 9ae7bee640..1c8d8a548d 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-organizations.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-organizations.md
@@ -1,7 +1,6 @@
 ---
 title: 管理组织
 intro: '您可以管理指标中包含的 {% data variables.product.prodname_enterprise %} 组织。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-organizations
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage organizations.'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
index 129324664d..2befed0e7d 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 管理 GitHub Insights 中的权限
 intro: '您可以在 {% data variables.product.prodname_insights %} 中更新用户的权限。'
-product: '{% data reusables.gated-features.github-insights %}'
 permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage permissions.'
 versions:
   enterprise-server: '*'
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-repositories.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-repositories.md
index 8eaf8c80c4..3f2ffd12a1 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-repositories.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/managing-repositories.md
@@ -1,7 +1,6 @@
 ---
 title: 管理仓库
 intro: '您可以管理连接到 {% data variables.product.prodname_insights %} 的仓库以及每个仓库的指标中包含的数据。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/managing-repositories
 permissions: 'People with admin permissions in {% data variables.product.prodname_insights %} can manage repositories. '
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
index 1e59932555..6f7b842f2f 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/system-overview-for-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub Insights 系统概述
 intro: '{% data variables.product.prodname_insights %} 是一款与 {% data variables.product.prodname_enterprise %} 交互的独立应用程序。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
 versions:
diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/updating-github-insights.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
index 1234288853..6d53ea2e0c 100644
--- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
+++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/updating-github-insights.md
@@ -1,7 +1,6 @@
 ---
 title: 更新 GitHub Insights
 intro: '您可以更新到 {% data variables.product.prodname_insights %} 的最新版本，体验功能改进和漏洞修复的好处。'
-product: '{% data reusables.gated-features.github-insights %}'
 redirect_from:
   - /github/installing-and-configuring-github-insights/updating-github-insights
 permissions: 'People with read permissions to the `github/insights-releases` repository and administrative access to the application server can update {% data variables.product.prodname_insights %}.'
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index 936f06e2fd..1ed0df28bc 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -29,6 +29,5 @@ topics:
 
 {% endif %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md
index 80141ee067..64ee4d5706 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -43,7 +43,7 @@ topics:
 
 ### 延伸阅读
 
-- "[关于 {% data variables.product.prodname_dotcom %} 中的对话](/articles/about-conversations-on-github)"
+- "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
 - "[关于团队](/articles/about-teams)"
 - "[创建团队讨论](/organizations/collaborating-with-your-team/creating-a-team-discussion)"
 - "[编辑或删除团队讨论](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)"
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md
index 60aa6b7349..7baa9d264b 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md
@@ -19,6 +19,6 @@ topics:
 {% link_in_list /requiring-two-factor-authentication-in-your-organization %}
 {% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
 {% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
-{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
+{% link_in_list /restricting-email-notifications-for-your-organization %}
 {% link_in_list /reviewing-the-audit-log-for-your-organization %}
 {% link_in_list /reviewing-your-organizations-installed-integrations %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
index 207c5d49e6..e836468c93 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md
@@ -26,9 +26,8 @@ topics:
 
 ### 添加允许的 IP 地址
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
@@ -36,18 +35,16 @@ topics:
 
 ### 启用允许的 IP 地址
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 3. 在“IP allow list（IP 允许列表）”下，选择 **Enable IP allow list（启用 IP 允许列表）**。 ![允许 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
 4. 单击 **Save（保存）**。
 
 ### 编辑允许的 IP 地址
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
@@ -56,9 +53,8 @@ topics:
 
 ### 删除允许的 IP 地址
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
index 6bff69d274..ac6f21b8a8 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### 显示安全和分析设置
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
 显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。
@@ -34,7 +33,7 @@ topics:
 
 {% if currentVersion ver_gt "enterprise-server@3.0" %}如果您具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
 
-{% if currentversion == "github-ae@latest" %}该页面还将包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。{% endif %}
+{% if currentVersion == "github-ae@latest" %}该页面还将包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。{% endif %}
 
 ### 为所有现有仓库启用或禁用功能
 
@@ -50,33 +49,38 @@ topics:
 
 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
 2. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果您的 {% data variables.product.prodname_GH_advanced_security %} 许可中没有可用的席位，对“{% data variables.product.prodname_GH_advanced_security %}”的控制将会禁用。{% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png)
+   {% if currentVersion ver_gt "enterprise-server@3.0" %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 3. （可选）为组织中的新仓库默认启用该功能。
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png)
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![新仓库的"Enable by default（默认启用）"选项](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
+   {% endif %}
+   {% if currentVersion == "free-pro-team@latest" or currentVersion == "enterprise-server@3.0" %}
 4. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+   {% if currentVersion == "free-pro-team@latest" %}
    ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
-    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![用于禁用或启用功能的按钮](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
-   {% if currentVersion == "github-ae@latest" %}
-3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![用于为组织中所有符合条件的仓库启用功能的按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change. ![用于为组织中所有符合条件的仓库启用功能的按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
@@ -84,12 +88,15 @@ topics:
 ### 添加新仓库时自动启用或禁用功能
 
 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
-2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
-   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+2. 在功能右边的“Configure security and analysis features（配置安全性和分析功能）”下，默认为组织中的新仓库{% if currentVersion == "free-pro-team@latest" %} 或所有私有仓库{% endif %} 启用或禁用该功能。
+   {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
    ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
    {% endif %}
-   {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
-   ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png)
+   {% if currentVersion == "enterprise-server@3.1" %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   {% if currentVersion == "enterprise-server@3.0" %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% if currentVersion == "github-ae@latest" %}
    ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
@@ -112,7 +119,7 @@ topics:
 1. 开始键入要允许的仓库的名称。 ![添加仓库按钮](/assets/images/help/organizations/dependabot-private-repo-choose.png)
 1. 单击您想要允许的仓库。
 
-1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. !["X" 按钮来删除仓库。](/assets/images/help/organizations/dependabot-private-repository-list.png)
+1. （可选）要从列表中删除仓库，在仓库右侧单击 {% octicon "x" aria-label="The X icon" %}。 !["X" 按钮来删除仓库。](/assets/images/help/organizations/dependabot-private-repository-list.png)
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
@@ -122,7 +129,7 @@ topics:
 您可以从仓库的“Settings（设置）”选项卡管理对仓库 {% data variables.product.prodname_GH_advanced_security %} 功能的访问。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 但您也可以从“Settings（设置）”选项卡对仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 功能。
 
 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
-1. 要查看您组织中启用 {% data variables.product.prodname_GH_advanced_security %} 的所有仓库的列表，请滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) 表格列出了每个仓库的唯一提交者数量。 这是您可以通过移除 {% data variables.product.prodname_GH_advanced_security %} 访问权限释放的席位数。 您的许可证大小显示在组织级许可证中。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的许可](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)”。
+1. 要查看您组织中启用 {% data variables.product.prodname_GH_advanced_security %} 的所有仓库的列表，请滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) 表格列出了每个仓库的唯一提交者数量。 这是您可以通过移除 {% data variables.product.prodname_GH_advanced_security %} 访问权限释放的席位数。 {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)."{% else %}For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/about-licensing-for-github-advanced-security)."{% endif %}
 1. 要从仓库删除对 {% data variables.product.prodname_GH_advanced_security %} 的访问，并释放任何提交者使用的对仓库唯一的席位，请单击相邻的 {% octicon "x" aria-label="X symbol" %}。
 1. 在确认对话框中，单击击 **Remove repository（移除仓库）** 以移除对 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限。
 
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
index d439836423..e1c864f0e0 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md
@@ -42,9 +42,8 @@ topics:
 
 ### 您的组织中需要双重身份验证
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..e292c742bc
--- /dev/null
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,46 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### 关于电子邮件限制
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. 有关外部协作者的更多信息，请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)”。
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index c428a012be..b1bd6b981a 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -10,8 +10,8 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - organizations
-  - teams
+  - Organizations
+  - Teams
 ---
 
 ### Accessing the audit log
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
index fef74ae8c6..9697df3bb5 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md
@@ -14,9 +14,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 在左侧边栏中，单击 **Installed {% data variables.product.prodname_github_app %}s（安装的 GitHub 应用程序）**。 ![组织设置边栏中安装的 {% data variables.product.prodname_github_app %}选项卡](/assets/images/help/organizations/org-settings-installed-github-apps.png)
 5. 在您要审查的 {% data variables.product.prodname_github_app %} 旁边，单击 **Configure（配置）**。 ![配置按钮](/assets/images/help/organizations/configure-installed-integration-button.png)
 6. 审查 {% data variables.product.prodname_github_app %} 的权限和仓库访问权限。 ![授予 {% data variables.product.prodname_github_app %}所有仓库或特定仓库访问权限的选项](/assets/images/help/organizations/toggle-integration-repo-access.png)
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
index 8288c54399..8a3be4853a 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md
@@ -17,17 +17,15 @@ topics:
 
 ### 授权某人管理组织拥有的所有 {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. 在“Management（管理）”下，输入您要指定为组织中 {% data variables.product.prodname_github_app %} 管理员的人员，然后单击 **Grant（授权）**。 ![添加 {% data variables.product.prodname_github_app %} 管理员](/assets/images/help/organizations/add-github-app-manager.png)
 
 ### 授权某人管理个别 {% data variables.product.prodname_github_app %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. 在 "{% data variables.product.prodname_github_app %}" 下，单击要为其添加 {% data variables.product.prodname_github_app %} 管理员的应用程序的头像。 ![选择 {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
index a3fb940168..6b57b4dcdf 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md
@@ -17,17 +17,15 @@ topics:
 
 ### 删除整个组织的 {% data variables.product.prodname_github_app %}管理员权限
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. 在“Management（管理）”下，找到您要从其删除 {% data variables.product.prodname_github_app %}管理员权限的人员的用户名，然后单击 **Revoke（撤销）**。 ![撤销 {% data variables.product.prodname_github_app %}管理员权限](/assets/images/help/organizations/github-app-manager-revoke-permissions.png)
 
 ### 删除单个 {% data variables.product.prodname_github_app %}的 {% data variables.product.prodname_github_app %}管理员权限
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
 1. 在 "{% data variables.product.prodname_github_app %}" 下，单击要从其删除 {% data variables.product.prodname_github_app %}管理员的应用程序的头像。 ![选择 {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png)
 {% data reusables.organizations.app-managers-settings-sidebar %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index e920d523f2..f5a69e3649 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -49,4 +49,4 @@ topics:
 {% data reusables.profile.access_org %}
 {% data reusables.organizations.specific_team %}
 4. 在团队的对话上方，单击 {% octicon "project" aria-label="The Projects icon" %} **Projects（项目）**。 ![团队仓库选项卡](/assets/images/help/organizations/team-project-board-button.png)
-5. 要更改权限级别，在要更新的项目板右侧使用下拉列表。 要删除项目板，请单击 **{% octicon "trashcan" aria-label="The trashcan icon" %}**。 ![从团队删除项目板的垃圾桶按钮](/assets/images/help/organizations/trash-button.png)
+5. 要更改权限级别，在要更新的项目板右侧使用下拉列表。 要删除项目板，请单击 **{% octicon "trash" aria-label="The trash icon" %}**。 ![从团队删除项目板的垃圾桶按钮](/assets/images/help/organizations/trash-button.png)
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
index f29a4fcad3..d00e7a518f 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md
@@ -18,7 +18,7 @@ topics:
 如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 {% data reusables.organizations.org-invite-expiration %}{% endif %}
 
 {% if currentVersion != "github-ae@latest" %}
-If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users {% if currentVersion == "free-pro-team@latest" %}you invite must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before they can accept the invitation.{% else %}must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization.{% endif %}
+如果您的组织[要求成员使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)，则{% if currentVersion == "free-pro-team@latest" %}您邀请的用户必须[启用双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)之后才能接受邀请。{% else %}要添加的用户必须[启用双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)之后您才能将其添加到组织。{% endif %}
 {% endif %}
 
 {% data reusables.profile.access_profile %}
@@ -26,7 +26,7 @@ If your organization [requires members to use two-factor authentication](/articl
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
 {% if currentVersion == "free-pro-team@latest" %}
-5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![邀请外部协作者加入组织](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
+5. 在您希望其成为成员的外部协作者姓名右侧，使用 {% octicon "gear" aria-label="The gear icon" %} 下拉菜单，然后单击 **Invite to organization（邀请加入组织）**。![邀请外部协作者加入组织](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
 {% else %}
 5. 在您希望其成为成员的外部协作者姓名右侧，单击 **Invite to organization（邀请加入组织）**。![邀请外部协作者加入组织](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
 {% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
index 4fd3c13620..be22a672e1 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
@@ -119,7 +119,7 @@ topics:
 | 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”）                                                                                                                                                                                                                                                                                  |       |       |       |       |                                                                       **X**                                                                        |
 | 更改仓库设置                                                                                                                                                                                                                                                                                                                                            |       |       |       |       |                                                                       **X**                                                                        |
 | 管理团队和协作者对仓库的权限                                                                                                                                                                                                                                                                                                                                    |       |       |       |       |                                                                       **X**                                                                        |
-| 编辑仓库的默认分支                                                                                                                                                                                                                                                                                                                                         |       |       |       |       |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
+| 编辑仓库的默认分支                                                                                                                                                                                                                                                                                                                                         |       |       |       |       |                     **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
 | 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”）                                                                                                                                                                                                                                                                    |       |       |       |       |                                                                       **X**                                                                        |
 | 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”）                                                                                                                                                                                                                                                                |       |       | **X** | **X** |                                                                 **X** 
 {% endif %}
@@ -142,7 +142,8 @@ topics:
 | [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                            |       | **X** | **X** | **X** |                                                                       **X**                                                                        |
 | [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                         |       | **X** | **X** | **X** |                                                                       **X**                                                                        |
 | [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                                | **X** | **X** | **X** | **X** |                                                                       **X**                                                                        |
-| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                        |       |       |       | **X** |                                                                 **X** 
+| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                        |       |       |       | **X** |                                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| Create [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                 |       |       | **X** | **X** |                                                                 **X** 
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
@@ -152,12 +153,13 @@ topics:
 
 | 仓库操作                                                                                                                                                                                                               |  读取   |  分类   |         写入          |         维护          |                                                                              管理员                                                                              |
 |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-----:|:-----:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| {% if currentVersion == "free-pro-team@latest" %}                                                                                                                                                                  |       |       |                     |                     |                                                                                                                                                               |
-| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)                                                     |       |       |                     |                     |                                                                             **X**                                                                             |
-| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                          |       |       |                     |                     |                                                                             **X**                                                                             |
-| [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |       |       |                     |                     |                                                                             **X**                                                                             |
-| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)                                                                                                                               |       |       |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
-| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）        |       |       |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}                                                                                                                |       |       |                     |                     |                                                                                                                                                               |
+| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)                                                          |       |       |                     |                     |                                                                             **X**                                                                             |
+| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)                                               |       |       |                     |                     |                                                                             **X**                                                                             |
+| [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |       |       |                     |                     |                                              **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
+| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                      |       |       |                     |                     | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）        |       |       |                     |                     |                        **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}<!--Set at site-level for GHES-->
+|
 | 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)                                                                                                                    |       |       |                     |                     |                                                                             **X**                                                                             |
 | [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                            | **X** | **X** |        **X**        |        **X**        | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
 | [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)                               | **X** | **X** |        **X**        |        **X**        |                                                                             **X**                                                                             |
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
index 5f2a8d5fa1..c2b197da89 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### 设置基本权限
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Base permissions（基本权限）”下，使用下拉菜单选择新的基本权限。 ![从基本权限下拉菜单中选择新的权限级别](/assets/images/help/organizations/base-permissions-drop-down.png)
 6. 审查更改。 要确认，请单击 **Change default permission to PERMISSION（将默认权限更改为所设权限）**。 ![审查并确认基本权限的更改](/assets/images/help/organizations/base-permissions-confirm.png)
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index eebebf30e1..ffcb40952a 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -22,17 +22,15 @@ topics:
 
 {% data reusables.organizations.add-extension-to-cert %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
 ### 删除 SSH 认证中心
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
index d1f098d25a..0536ffd6e4 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 在启用后，组织所有者以及在组织拥有的仓库中具有管理员权限的人员便可删除议题。 在仓库中具有管理员权限的人员包括具有管理员权限的组织成员以及外部协作者。 更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization/)”和“[删除议题](/articles/deleting-an-issue)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在 "Issue deletion"（删除议题）下，选择 **Allow members to delete issues for this organization（允许成员删除此组织的议题）**。 ![允许人们删除议题的复选框](/assets/images/help/settings/issue-deletion.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index 357bb80936..fdb7057138 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,9 +16,8 @@ topics:
 
 企业所有者可设置企业帐户中所有组织的查看组织依赖项洞察图限制。 更多信息请参阅“[在企业帐户中实施关于依赖项洞察的策略](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Member organization permissions（成员组织权限）”下，选中或取消选中 **Allow members to view dependency insights（允许成员查看依赖项洞察图）**。 ![允许成员查看洞察图的复选框](/assets/images/help/organizations/allow-members-to-view-insights.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md
index 13f9d57c34..2662556029 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -28,7 +28,6 @@ topics:
 
 ### 2. 删除组织
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 在组织设置页面底部附近，单击 **Delete this Organization（删除此组织）**。 ![删除此组织按钮](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index dfcb6b06ea..81af2bd41a 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -27,9 +27,8 @@ topics:
 
 ### 管理组织的 {% data variables.product.prodname_actions %} 权限
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. 在 **Local and third-party Actions（本地和第三方操作）**下，选择一个选项。 ![启用、禁用或限制此组织的操作](/assets/images/help/repository/enable-org-actions.png)
 1. 单击 **Save（保存）**。
@@ -50,9 +49,8 @@ topics:
 
 {% endnote %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. 在 **Policies（策略）**下，选择一个选项。 ![设置此组织的操作策略](/assets/images/help/organizations/actions-policy.png)
 1. 单击 **Save（保存）**。
@@ -61,9 +59,8 @@ topics:
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png)
 1. 单击 **Save（保存）**。
@@ -77,9 +74,27 @@ topics:
 
 #### 为组织配置私有复刻策略
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions %}
 {% data reusables.github-actions.private-repository-forks-configure %}
 {% endif %}
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+### 为您的组织设置 `GITHUB_TOKENN` 的权限
+
+{% data reusables.github-actions.workflow-permissions-intro %}
+
+您可以在组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在组织设置中选择受限制的选项为默认值，则在您的组织内仓库的设置中，自动选择相同的选项，允许选项也会被禁用。 如果您的组织属于 {% data variables.product.prodname_enterprise %} 帐户，并且在企业设置中选择了更受限制的默认值，则您将无法在组织设置中选择更宽松的默认值。
+
+{% data reusables.github-actions.workflow-permissions-modifying %}
+
+#### 配置默认 `GITHUB_TOKENN` 权限
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions %}
+1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 ![为此组织设置 GITHUB_TOKENN 权限](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. 单击 **Save（保存）**以应用设置。
+{% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/index.md b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
index a0a039fa5e..76210abf78 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/index.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
@@ -13,7 +13,7 @@ topics:
   - Teams
 ---
 
-{% link_in_list /verifying-your-organizations-domain %}
+{% link_in_list /verifying-or-approving-a-domain-for-your-organization %}
 {% link_in_list /renaming-an-organization %}
 {% link_in_list /transferring-organization-ownership %}
 {% link_in_list /restricting-repository-creation-in-your-organization %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
index 779515caa8..f14cfe3f64 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -19,9 +19,8 @@ topics:
 
 ### 创建默认标签
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -35,9 +34,8 @@ topics:
 
 ### 编辑默认标签
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
@@ -51,9 +49,8 @@ topics:
 
 ### 删除默认标签
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
 {% data reusables.organizations.repository-defaults %}
 {% else %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index f12481a941..5ff78e9e60 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 默认情况下，如果仓库管理员或组织所有者为组织拥有的仓库启用了讨论，则具有读取权限的组织成员可以创建讨论。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Repository discussions（仓库讨论）”下，选择或取消选择 **Allow users with read access to create discussions（允许有读权限的用户创建讨论）**。 ![允许有读取权限的人创建讨论的复选框](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
 6. 单击 **Save（保存）**。 ![讨论设置的"保存"按钮](/assets/images/help/discussions/click-save.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
index cd5093d5ce..dff8828258 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -19,9 +19,8 @@ topics:
 {% data reusables.reminders.scheduled-reminders-limitations %}
 
 ### 为组织创建预定提醒
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.add-reminder %}
@@ -43,9 +42,8 @@ topics:
 {% data reusables.reminders.create-reminder %}
 
 ### 管理组织的预定提醒
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.edit-existing %}
@@ -53,9 +51,8 @@ topics:
 {% data reusables.reminders.update-buttons %}
 
 ### 删除组织的预定提醒
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.reminders.scheduled-reminders %}
 ![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png)
 {% data reusables.reminders.delete %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
index 1d40eaacce..7ba2053be5 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 ### 设置默认分支名称
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.repository-defaults %}
 3. 在“Repository default branch（仓库默认分支）”下，单击 **Change default branch name now（立即更改默认分支名称）**。 ![覆盖按钮](/assets/images/help/organizations/repo-default-name-button.png)
 4. 键入要用于新分支的默认名称。 ![输入默认名称的文本框](/assets/images/help/organizations/repo-default-name-text.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 0346eb84ed..c11df0b6f8 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -20,9 +20,8 @@ topics:
 
 每个组织成员在自己的设置中选择自己的个人资料名称。 更多信息请参阅“[个性化您的个人资料](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Admin repository permissions（管理仓库权限）”下，选中或取消选中 **Allow members to see comment author's profile name in private repositories（允许成员在私有仓库中查看评论作者的个人资料名称）**。 ![允许成员在私有仓库中查看评论作者的全名复选框](/assets/images/help/organizations/allow-members-to-view-full-names.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
index 06991cd90c..f9c7b1a061 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -21,9 +21,8 @@ topics:
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Repository forking（仓库复刻）”下，选择 **Allow forking of private repositories（允许复刻私有仓库）**或 **Allow forking of private and internal repositories（允许复刻私有和内部仓库）**。 ![允许或禁止组织复刻的复选框](/assets/images/help/repository/allow-disable-forking-organization.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
index 2849b93502..11b1132362 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -15,14 +15,13 @@ topics:
 
 组织赞助的开发者和组织可向您发送有关其工作的更新。 您可以管理用于接收这些更新的电子邮件地址。
 
-您也可以禁用组织赞助帐户的更新。 更多信息请参阅“[管理您的赞助](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)”。
+您也可以禁用组织赞助帐户的更新。 更多信息请参阅“[管理您的赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 1. 在“Sponsors update email (Private)（赞助更新电子邮件（私有））”下，输入要用于接收组织赞助帐户更新的电子邮件地址。 ![输入用于接收被赞助帐户更新的电子邮件地址的文本框](/assets/images/help/sponsors/organization-update-email-textbox.png)
 1. 单击 **Update profile（更新个人资料）**。 ![更新个人资料按钮](/assets/images/help/organizations/update-profile-button.png)
 
 ### 延伸阅读
 
-- "[使用 {% data variables.product.prodname_sponsors %} 支持开源社区](/github/supporting-the-open-source-community-with-github-sponsors)"
+- "[{% data variables.product.prodname_sponsors %}](/sponsors)"
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md
index 6161a21ebf..39358cd1c8 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -35,14 +35,13 @@ topics:
 更改组织的名称后：
 - 指向以前组织资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previousorgname`）将返回 404 错误。 我们建议您更新从其他站点指向组织的链接{% if currentVersion == "free-pro-team@latest" %}，例如 LinkedIn 或 Twitter 个人资料{% endif %}。
 - 使用旧组织名称的 API 请求将返回 404 错误。 我们建议您更新 API 请求中的旧组织名称。
-- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %}
-- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %}
+- 对于使用旧组织名称的团队，没有自动[@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)重定向。{% if currentVersion == "free-pro-team@latest" %}
+- 如果为组织启用了 SAML 单点登录 (SSO)，则必须在身份提供商 (IdP) 上更新 {% data variables.product.prodname_ghe_cloud %} 的应用程序中的组织名称。 如果您不更新 IdP 上的组织名称，组织成员将无法使用您的 IdP 身份验证来访问组织的资源。 更多信息请参阅“[将身份提供程序连接到组织](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)”。{% endif %}
 
 ### 更改组织的名称
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 4. 在设置页面底部附近的“Rename organization（重命名组织）”下，单击 **Rename Organization（重命名组织）**。 ![重命名组织按钮](/assets/images/help/settings/settings-rename-organization.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 ffb23d1282..d4375b597f 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
@@ -27,9 +27,8 @@ topics:
 
 {% data reusables.organizations.internal-repos-enterprise %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Repository creation（仓库创建）”下，选择一个或多个选项。 ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
index 836b504186..517a32732a 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -22,9 +22,8 @@ topics:
 {% endwarning %}
 
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Repository visibility change（仓库可见性更改）”下，取消选择 **Allow members to change repository visibilities for this organization（允许成员为此组织更改仓库可见性）**。 ![允许成员更改仓库可见性的复选框](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index 8afae8896f..277de36a53 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -19,9 +19,8 @@ topics:
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Repository invitations（仓库邀请）”下，选择 **Allow members to invite outside collaborators to repositories for this organization（允许成员邀请外部协作者访问本组织的仓库）**。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %}
 ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
index 84daaa1ea2..dd0ddfecf3 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -16,9 +16,8 @@ topics:
 
 所有者可以设置删除或转让组织中仓库的权限。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在 Repository deletion and transfer（仓库删除和转让）下，选择或取消选择 **Allow members to delete or transfer repositories for this organization（允许成员删除或转让此组织的仓库）**。 ![允许成员删除仓库的复选框](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
index a5d627cd02..12bfdbe3ea 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -17,9 +17,8 @@ topics:
 
 如果您没有设置团队创建权限，默认情况下所有组织成员都能够创建团队。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
 5. 在“Team creation rules（团队创建规则）”下，选择或取消选择 **Allow members to create teams（允许成员创建团队）**。 ![允许成员创建团队的复选框](/assets/images/help/organizations/allow-members-to-create-teams.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..658a230ed7
--- /dev/null
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=3.2'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+---
+
+### 关于域验证
+
+验证组织域的所有权后，将在组织的资料中显示“Verified（已验证）”徽章。 如果您的组织位于 {% data variables.product.prodname_ghe_cloud %} 上并且已同意公司服务条款，则组织所有者将能够通过查看验证域内每个成员的电子邮件地址来验证组织成员的身份。 更多信息请参阅“[关于组织的资料页面](/articles/about-your-organization-s-profile/)”和“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。
+
+如果您的组织由企业帐户拥有，则“已验证”徽章将显示在组织的基本资料上，除了显示组织的任何已验证域之外，还能够显示企业帐户的任何已验证域。 Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.organizations.verified-domains-details %}
+
+在 {% data variables.product.prodname_ghe_cloud %} 上，验证组织域的所有权后，您可以将组织的电子邮件通知限制为该域。 For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+### About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+### Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. 等待 DNS 配置更改，最多可能需要 72 小时。 您可以通过在命令行上运行 `dig` 命令来确认您的 DNS 配置已更改，将 `ORGANIZATION` 替换为您组织的名称，将 `example.com` 替换为要验证的域。 您应看到命令输出中列出的新 TXT 记录。
+   ```shell
+   $ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. （可选）组织的资料页面中显示“Verified（已验证）”徽章后，您可以从域托管服务的 DNS 记录中删除 TXT 条目。 ![已验证徽章](/assets/images/help/organizations/verified-badge.png)
+
+### Approving a domain for your organization
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+### Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index fb4a63e409..968bb78c40 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -49,9 +49,8 @@ topics:
 
 受邀人员将会收到邀请电子邮件，邀请他们成为您的组织的帐单管理员。 在受邀人员单击其邀请电子邮件中的接受链接后，他们会自动加入组织成为帐单管理员。 如果他们还没有 GitHub 帐户，将被重定向到注册页面注册一个，在创建帐户后会自动加入组织成为帐单管理员。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. 在帐单管理员旁边，单击 **Add a billing manager（添加帐单管理员）**。 ![邀请帐单管理员](/assets/images/help/billing/settings_billing_managers_list.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Under "Billing management", next to "Billing managers", click **Add**. ![邀请帐单管理员](/assets/images/help/billing/settings_billing_managers_list.png)
 6. 输入您要添加的人员的用户名或电子邮件地址，然后单击 **Send invitation（发送邀请）**。 ![邀请帐单管理员页面](/assets/images/help/billing/billing_manager_invite.png)
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
index 0d1c48a0ea..ce6c6c97b5 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -23,6 +23,12 @@ topics:
 
 组织所有者对组织具有完全管理权限。 {% data reusables.organizations.new-org-permissions-more-info %}
 
+{% note %}
+
+**注意**：作为组织所有者，您可以更改其他组织成员和所有者的角色。 您不能改变自己的角色。
+
+{% endnote %}
+
 ### 任命组织所有者
 
 {% data reusables.profile.access_profile %}
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
index 053fbdacac..1c67789c07 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md
@@ -43,7 +43,7 @@ topics:
 | 访问组织审核日志                                                                                                                                                                                                                                            | **X** |       |       |
 | 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”）                                                                                                                                                                          | **X** |       |       |
 | 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |       |       |
-| 将电子邮件通知限制为经验证的域（更多信息请参阅“[将电子邮件通知限制为经批准的域](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)”）                                                                                                  | **X** |       |       |
+| Restrict email notifications to verified or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details)     | **X** |       |       |
 | 删除**所有团队**                                                                                                                                                                                                                                          | **X** |       |       |
 | 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |       |       |
 | 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** | **X** |       |
@@ -60,9 +60,9 @@ topics:
 | 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                         | **X** |       |       |
 | 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”）                                                                                                                                 | **X** |       |       |
 | 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                  | **X** |       |       |
-| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”）                                                                                                             | **X** | **X** |       |
+| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors)”）                                                                                                                                                                     | **X** | **X** |       |
 | 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)”）                                                                                                      | **X** |       |       |
-| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)”）                                                                                                 | **X** |       |       |
+| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)”）                                                                                                                     | **X** |       |       |
 | 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** |       |       |
 | 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）                                                                                                   | **X** |       |       |
 | 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                          | **X** |       |       |
@@ -79,7 +79,7 @@ topics:
 | 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                             | **X** |       |       |
 | [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                         | **X** |       |       |
 | [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                             | **X** |       |       |
-| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)")               | **X** |       |       |
+| 管理默认分支名称（请参阅“[管理组织中仓库的默认标签](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”）                                                                                                 | **X** |       |       |
 | 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |       |       |
 | 启用团队同步（详情请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”）                                                                                                   | **X** |       |       |
 
@@ -123,7 +123,7 @@ topics:
 | [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                             | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 | 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |                                           
 {% endif %}
-{% if currentversion == "github-ae@latest" %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %}
+{% if currentVersion == "github-ae@latest" %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %}
 
 {% endif %}
 
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
index c84c22034c..2c42a6b463 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -18,8 +18,7 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
-{% data reusables.organizations.billing %}
-5. 在 Billing managers（帐单管理员）列表中您要删除的人员姓名旁边，单击 {% octicon "x" aria-label="X symbol" %}。 ![删除帐单管理员](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**. ![删除帐单管理员](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
index a508a2db26..1418efa10d 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -15,9 +15,8 @@ topics:
 
 恢复代码不应共享或分发。 我们建议使用一个密码管理器保存它们，例如 [LastPass](https://lastpass.com/)、 [1Password](https://1password.com/) 或 [Keeper](https://keepersecurity.com/)。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. 在“SAML single sign-on”（SAML 单点登录）下，在有关恢复代码的注释中，单击 **Save your recovery codes（保存恢复代码）**。 ![查看和保存恢复代码的链接](/assets/images/help/saml/saml_recovery_codes.png)
 6. 通过单击 **Download（下载）**、**Print（打印）** 或 **Copy（复制）**保存恢复代码。 ![下载、打印或复制恢复代码的按钮](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index 1f1cdc2465..01483802be 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -20,9 +20,8 @@ topics:
 
 在组织中实施 SAML SSO 之前，请确保已设置身份提供程序 (IdP)。 更多信息请参阅“[准备在组织中实施 SAML 单点登录](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. 在“SAML single sign-on”（SAML 单点登录）下，选择 **Enable SAML authentication（启用 SAML 身份验证）**。 ![用于启用 SAML SSO 的复选框](/assets/images/help/saml/saml_enable.png)
 
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index 7744844082..8d4fa1898e 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -46,9 +46,8 @@ topics:
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-azure %}
@@ -59,9 +58,8 @@ topics:
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
@@ -72,8 +70,7 @@ topics:
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
 5. 在“Team synchronization（团队同步）”下，单击 **Disable team synchronization（禁用团队同步）**。 ![禁用团队同步](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
index 1f549627d8..c0156479ea 100644
--- a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
+++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -29,9 +29,8 @@ topics:
 
 ### 迁移所有组织的旧管理员团队
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 1. 检查组织的旧管理员团队，然后单击 **Migrate all teams（迁移所有团队）**。 ![迁移所有团队按钮](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
 1. 阅读这些团队成员的可能权限更改的信息，然后单击 **Migrate all teams（迁移所有团队）**。 ![确认迁移按钮](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
index d2341e18e3..d763d8c045 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -15,9 +15,8 @@ topics:
 
 {% data reusables.organizations.team-discussions-default %} 有关团队讨论的更多信息，请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.teams_sidebar %}
 5. 在“Team discussions”（团队讨论）下，取消选择 **Enable team discussions for this organization（启用本组织的团队讨论）**。 ![用于启用或禁用组织的团队讨论的复选框](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
 6. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
index 29ab94a1b7..a68a7b0ff6 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
@@ -19,9 +19,9 @@ topics:
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
-{% if currentversion == "free proteam@latest" %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif currentVersion == "github-ae@latest" %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。
+{% if currentVersion == "free proteam@latest" %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif currentVersion == "github-ae@latest" %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。
 
-{% if currentversion == "free-proteam@latest" %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %}
+{% if currentVersion == "free-proteam@latest" %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %}
 
 {% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您不能在 {% data variables.product.product_name %} 上{% if currentVersion == "free-pro-team@latest" %}或使用 API{% endif %} 管理团队成员资格。
 
@@ -30,14 +30,14 @@ topics:
 {% endif %}
 
 {% if currentVersion == "github-ae@latest" %}
-When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. 更改 {% data variables.product.prodname_dotcom %} 团队或组织成员资格的任何请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。 有关此帐户的更多信息，请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 有关 SCIM 请求计划的更多信息，请参阅 Microsoft 文档中的“[检查用户预配状态](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)”。
+当 Idp 上的组成员身份发生变化时，您的 IdP 会根据 IdP 确定的时间表发送 SCIM 请求，请求更改 {% data variables.product.product_name %}。 更改 {% data variables.product.prodname_dotcom %} 团队或组织成员资格的任何请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。 有关此帐户的更多信息，请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 有关 SCIM 请求计划的更多信息，请参阅 Microsoft 文档中的“[检查用户预配状态](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)”。
 {% endif %}
 
 父团队无法与 IdP 组同步。 如果要连接到 IdP 组的团队是父团队，我们建议您创建一个新团队或删除使团队成为父团队的嵌套关系。 更多信息请参阅“[关于团队](/articles/about-teams#nested-teams)”、“[创建团队](/organizations/organizing-members-into-teams/creating-a-team)”和“[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organizations-hierarchy)”。
 
 要管理 {% data variables.product.prodname_dotcom %} 团队（包括连接到 IdP 组的团队）的仓库访问权限，您必须使用 {% data variables.product.product_name %} 进行更改。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。
 
-{% if currentversion == "free proteam@latest" %}您也可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %}
+{% if currentVersion == "free proteam@latest" %}您也可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 ### 已同步团队成员的要求
@@ -47,7 +47,7 @@ When group membership changes on your IdP, your IdP sends a SCIM request with th
 - 此人已使用 {% data variables.product.product_name %} 上的用户帐户登录，并且至少一次通过 SAML 单点登录向组织或企业帐户验证。
 - 此人的 SSO 身份是 IdP 组的成员。
 
-不符合这些条件的现有团队或组成员将被从 {% data variables.product.product_name %} 团队中自动删除，并失去对仓库的访问权限。 撤销用户关联的身份也会将用户从映射到 IdP 组的任何团队中删除。 For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."
+不符合这些条件的现有团队或组成员将被从 {% data variables.product.product_name %} 团队中自动删除，并失去对仓库的访问权限。 撤销用户关联的身份也会将用户从映射到 IdP 组的任何团队中删除。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”和“[查看和管理用户对企业的 SAML 访问](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)”。
 
 删除后的团队成员在使用 SSO 向组织或企业帐户进行身份验证后可以自动添加回团队，并移动到已连接的 IdP 组。
 
@@ -60,21 +60,21 @@ When group membership changes on your IdP, your IdP sends a SCIM request with th
 ### 基本要求
 
 {% if currentVersion == "free-pro-team@latest" %}
-Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)."
+在连接 {% data variables.product.product_name %} 团队与身份提供程序组之前，组织或企业所有者必须为组织或企业帐户启用团队同步。 更多信息请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”和“[管理企业帐户中组织的团队同步](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。
 
 为避免无意中删除团队成员，请访问 IdP 的管理门户，并确认每个当前团队成员也位于要连接到此团队的 IdP 组中。 如果您没有身份提供程序的这一访问权限，在可以联系 IdP 管理员。
 
 您必须使用 SAML SSO 进行身份验证。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。
 
 {% elsif currentVersion == "github-ae@latest" %}
-Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。
+在连接 {% data variables.product.product_name %} 团队与 IdP 组时，您必须先使用支持的跨域身份管理系统(SCIM) 配置 {% data variables.product.product_location %} 的用户预配。 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。
 
-Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. 更多信息请参阅 Microsoft 文档中的[配置 GitHub AE 的自动用户预配](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae)。
+在使用 SCIM 配置 {% data variables.product.product_name %} 的用户预配后，您可以将 {% data variables.product.product_name %} 应用程序分配到您想要在 {% data variables.product.product_name %} 上使用的每个 IdP 组。 更多信息请参阅 Microsoft 文档中的[配置 GitHub AE 的自动用户预配](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae)。
 {% endif %}
 
 ### 将 IdP 组连接到团队
 
-将 IdP 组连接到 {% data variables.product.product_name %} 团队时，组中的所有用户都会自动添加到团队中。 {% if currentversion == "github-ae@latest" %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %}
+将 IdP 组连接到 {% data variables.product.product_name %} 团队时，组中的所有用户都会自动添加到团队中。 {% if currentVersion == "github-ae@latest" %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %}
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
@@ -87,7 +87,7 @@ Once user provisioning for {% data variables.product.product_name %} is configur
 
 ### 断开 IdP 组与团队的连接
 
-如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接，则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% if currentversion == "github-ae@latest" %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %}
+如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接，则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% if currentVersion == "github-ae@latest" %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %}
 
 {% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
index d1b8056b58..9921034211 100644
--- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md
@@ -14,9 +14,8 @@ topics:
 
 当 {% data variables.product.prodname_oauth_app %} 访问限制启用后，组织成员必须向组织所有者[申请批准](/articles/requesting-organization-approval-for-oauth-apps)，然后才可授权对组织资源具有访问权限的 {% data variables.product.prodname_oauth_app %}。
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. 在要批准的应用程序的旁边，单击 **Review（审查）**。 ![审查申请链接](/assets/images/help/settings/settings-third-party-approve-review.png)
 6. 在审查申请的应用程序相关信息后，单击 **Grant access（授予访问）**。 ![授予访问按钮](/assets/images/help/settings/settings-third-party-approve-grant.png)
diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
index 47440d870f..be3c503360 100644
--- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md
@@ -12,9 +12,8 @@ topics:
   - Teams
 ---
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. 在要禁用的应用程序旁边，单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑图标](/assets/images/help/settings/settings-third-party-deny-edit.png)
 6. 单击 **Deny access（拒绝访问）**。 ![拒绝确认按钮](/assets/images/help/settings/settings-third-party-deny-confirm.png)
diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
index a99fb90312..616710b60f 100644
--- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md
@@ -18,9 +18,8 @@ topics:
 
 {% enddanger %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. 单击 **Remove restrictions（删除限制）**。 ![删除限制按钮](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. 审查有关禁用第三方应用程序限制的信息后，请单击 **Yes, remove application restrictions（是，删除应用程序限制）**。 ![删除确认按钮](/assets/images/help/settings/settings-third-party-confirm-disable.png)
diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
index 4fce51028e..94698cb9b4 100644
--- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md
@@ -23,9 +23,8 @@ topics:
 
 {% endwarning %}
 
-{% data reusables.profile.access_profile %}
 {% data reusables.profile.access_org %}
-{% data reusables.organizations.org_settings %}
+{% data reusables.profile.org_settings %}
 {% data reusables.organizations.oauth_app_access %}
 5. 在“Third-party application access policy”（第三方应用程序访问策略）下，单击 **Setup application access restrictions（设置应用程序访问限制）**。 ![设置限制按钮](/assets/images/help/settings/settings-third-party-set-up-restrictions.png)
 6. 审查有关第三方访问限制的信息后，单击 **Restrict third-party application access（限制第三方应用程序访问）**。 ![限制确认按钮](/assets/images/help/settings/settings-third-party-restrict-confirm.png)
diff --git a/translations/zh-CN/content/packages/index.md b/translations/zh-CN/content/packages/index.md
index 0b72619b19..ff70c832a5 100644
--- a/translations/zh-CN/content/packages/index.md
+++ b/translations/zh-CN/content/packages/index.md
@@ -33,7 +33,8 @@ versions:
   github-ae: '*'
 ---
 
+<!--This section is needed to determine the order of the left sidebar for now-->
 <!-- {% link_with_intro /quickstart %}  -->
-<!-- {% link_with_intro /guides %} -->
 <!-- {% link_with_intro /learn-github-packages %} -->
-<!-- {% link_with_intro /manage-packages %} -->
+<!-- {% link_with_intro /working-with-a-github-packages-registry %} -->
+<!-- {% link_with_intro /managing-github-packages-using-github-actions-workflows %} -->
diff --git a/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..19d5f2c220
--- /dev/null
+++ b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,83 @@
+---
+title: About permissions for GitHub Packages
+intro: 'Learn about how to manage permissions for your packages.'
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% if currentVersion == "free-pro-team@latest" %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+### Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page.
+
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+
+  - Docker registry (`docker.pkg.github.com`)
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+### Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### About scopes and permissions for package registries
+
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
+
+For example:
+-  To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
+- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted.{% elsif currentVersion == "github-ae@latest" %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+
+| Scope | Description | Required permission |
+| --- | --- | --- |
+|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read |
+|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write |
+| `delete:packages` | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Delete packages from {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin |
+| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin |
+
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
+
+For more information, see:{% if currentVersion == "free-pro-team@latest" %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+### Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+#### Access tokens  
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..6bcd648bbf
--- /dev/null
+++ b/translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,135 @@
+---
+title: Configuring a package's access control and visibility
+intro: '选择谁对容器映像具有读取、写入或管理员访问权限，以及容器映像在 {% data variables.product.prodname_dotcom %} 上的可见性。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+### 容器映像的可见性和访问权限
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+### 为个人帐户配置对容器映像的访问
+
+If you have admin permissions to a container image that's owned by a user account, you can assign read, write, or admin roles to other users. 有关这些权限角色的更多信息，请参阅“[容器映像的可见性和访问权限](#visibility-and-access-permissions-for-container-images)”。
+
+如果您的软件包是私人或内部的并且由组织拥有，则您只能向其他组织成员或团队授予访问。
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. 在软件包设置页面上，单击 **Invite teams or people（邀请团队或人员）**，然后输入名称、用户名或您想要授予访问权限的人员的电子邮件地址。 不能授予团队访问用户帐户拥有的容器映像。 ![容器访问邀请按钮](/assets/images/help/package-registry/container-access-invite.png)
+1. 在用户名或团队名称旁边，使用“Role（角色）”下拉菜单选择所需的权限级别。 ![容器访问选项](/assets/images/help/package-registry/container-access-control-options.png)
+
+所选用户将自动被授予访问权限，不需要先接受邀请。
+
+### 为企业配置对容器映像的访问
+
+如果您对组织拥有的容器映像具有管理员权限，您可以向其他用户和团队分配读取、写入或管理员角色。 有关这些权限角色的更多信息，请参阅“[容器映像的可见性和访问权限](#visibility-and-access-permissions-for-container-images)”。
+
+如果您的软件包是私人或内部的并且由组织拥有，则您只能向其他组织成员或团队授予访问。
+
+对于组织映像容器，组织管理员必须先启用包，然后才能将可见性设置为公共。 For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. 在软件包设置页面上，单击 **Invite teams or people（邀请团队或人员）**，然后输入名称、用户名或您想要授予访问权限的人员的电子邮件地址。 您还可以从组织输入团队名称，以允许所有团队成员访问。 ![容器访问邀请按钮](/assets/images/help/package-registry/container-access-invite.png)
+1. 在用户名或团队名称旁边，使用“Role（角色）”下拉菜单选择所需的权限级别。 ![容器访问选项](/assets/images/help/package-registry/container-access-control-options.png)
+
+所选用户或团队将自动被授予访问权限，不需要先接受邀请。
+
+### 从仓库继承容器映像的访问权限
+
+要通过 {% data variables.product.prodname_actions %} 工作流程简化包管理，您可以让容器映像默认继承仓库的访问权限。
+
+如果您继承了存储包工作流程的仓库的访问权限，则可以通过仓库的权限调整对包的访问权限。
+
+仓库一旦同步，您就无法访问包的精细访问设置。 要通过精细的包访问设置自定义包的权限，您必须先删除同步的仓库。
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+2. 在“Repository source（仓库来源）”下，选择 **Inherit access from repository (recommended)（从仓库继承访问权限 [推荐]）**。 ![继承仓库访问权限复选框](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+### 确保工作流程访问您的包
+
+为确保 {% data variables.product.prodname_actions %} 工作流程能访问您的包，您必须授予存储工作流程的仓库以明确的访问权限。
+
+指定的仓库不需要是保存包源代码的仓库。 您可以授予多个仓库工作流程对包的访问权限。
+
+{% note %}
+
+**注意：**通过 **Actions access（操作访问）**菜单选项同步容器映像与仓库不同于将容器连接到仓库。 For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+#### {% data variables.product.prodname_actions %} access for user-account-owned container images
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+1. 在左侧边栏中，单击 **Actions access（操作访问）**。 ![左侧菜单中的"Actions access（操作访问）"选项](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. 单击 **Add repository（添加仓库）**并搜索要添加的仓库。 !["添加仓库"按钮](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![授予仓库的权限访问级别](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+#### {% data variables.product.prodname_actions %} access for organization-owned container images
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+1. 在左侧边栏中，单击 **Actions access（操作访问）**。 ![左侧菜单中的"Actions access（操作访问）"选项](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. 单击 **Add repository（添加仓库）**并搜索要添加的仓库。 !["添加仓库"按钮](/assets/images/help/package-registry/add-repository-button.png)
+3. 使用“role（角色）”下拉菜单，选择您希望仓库成员访问您的容器映像所必须拥有的默认访问权限。 外部协作者将不包括在内。 ![授予仓库的权限访问级别](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+要进一步自定义对容器映像的访问，请参阅“[配置对组织的容器映像的访问](#configuring-access-to-container-images-for-an-organization)”。
+
+### 为个人帐户配置容器映像的可见性
+
+首次发布包时，默认可见性是私有的，只有您才能看到包。 您可以通过更改访问设置来修改私有或公共容器映像的访问权限。
+
+公共包可以匿名访问，无需身份验证。 包一旦被设为公共，便无法再次将其设为私有。
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+5. 在“Danger Zone（危险区域）”下，选择可见性设置：
+    - 要使容器映像对任何人都可见，请单击“**Make public（设为公共）**”。
+    {% warning %}
+
+    **警告：**包一旦被设为公共，便无法再次将其设为私有。
+
+    {% endwarning %}
+    - 要使容器映像只对选择的人员可见，请单击“**Make private（设为私有）**”。 ![容器可见性选项](/assets/images/help/package-registry/container-visibility-option.png)
+
+### 组织成员的容器创建可见性
+
+您可以选择组织成员默认可以发布的容器的可见性。
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. 在左侧，单击 **Packages（包）**。
+6. 在“Container creation（容器创建）”下，选择是要启用公共、私有或内部容器映像。
+    - 要让组织成员创建公共容器映像，请单击 **Public（公共）**。
+    - 要让组织成员创建只对其他组织成员可见的私有容器映像，请单击 **Private（私有）**。 您可以进一步自定义私有容器映像的可见性。
+    - **仅适用于 {% data variables.product.prodname_ghe_cloud %} ：**要让组织成员创建仅供其他组织成员可见的内部容器映像，请单击 **Internal（内部）**。 ![组织成员发布的容器图像的可见性选项](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+### 为组织配置容器映像的可见性
+
+首次发布包时，默认可见性是私有的，只有您才能看到包。 您可以通过访问设置授予用户或团队对容器映像的不同访问角色。
+
+公共包可以匿名访问，无需身份验证。 包一旦被设为公共，便无法再次将其设为私有。
+
+对于组织映像容器，组织管理员必须先启用公共包，然后才能将可见性设置为公共。 For more information, see "[Enabling improved container support with the Container registry](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+5. 在“Danger Zone（危险区域）”下，选择可见性设置：
+    - 要使容器映像对任何人都可见，请单击“**Make public（设为公共）**”。
+    {% warning %}
+
+    **警告：**包一旦被设为公共，便无法再次将其设为私有。
+
+    {% endwarning %}
+    - 要使容器映像只对选择的人员可见，请单击“**Make private（设为私有）**”。 ![容器可见性选项](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..f7a2b53921
--- /dev/null
+++ b/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,76 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  free-pro-team: '*'
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+### Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+### Connecting a repository to a container image using the command line
+
+1. 在 Dockerfile 中添加此行，将 `OWNER` 和 `REPO` 替换为您的详细信息：
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
+ ```
+ 例如，如果您是用户 `monalisa` 并且拥有 `my-repo`，您会将此行添加到 Dockerfile：
+ ```shell
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
+ ```
+ 更多信息请参阅官方 Docker 文档中的“[LABEL](https://docs.docker.com/engine/reference/builder/#label)”，以及 `opencontainers/image-spec` 仓库中的“[预定义的标注键](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)”。
+
+2. 构建容器映像。 此示例从当前目录的 Dockerfile 构建映像，并分配映像名称 `hello_docker`。
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. （可选）查看您想要标记的 Docker 映像的详细信息。
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. 使用所需的映像名称和托管目标标记 Docker 映像。
+  ```shell
+  $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  例如：
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG
+  ```
+  例如：
+  ```shell
+  $ docker push ghcr.io/monalisa/hello_docker:latest
+  ```
diff --git a/translations/zh-CN/content/packages/learn-github-packages/index.md b/translations/zh-CN/content/packages/learn-github-packages/index.md
index 21feea4267..31c673432f 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/index.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/index.md
@@ -1,7 +1,7 @@
 ---
 title: 了解 GitHub Packages
 shortTitle: 了解 GitHub Packages
-intro: '您可以找到更多关于 GitHub Packages 的信息，包括发布新包到 {% data variables.product.prodname_registry %}。'
+intro: 'You can find out more about using packages in GitHub, including publishing new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.'
 redirect_from:
   - /packages/getting-started-with-github-container-registry
   - /github/managing-packages-with-github-packages/publishing-and-managing-packages
@@ -17,8 +17,12 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% link_in_list /about-github-packages %}
-{% link_in_list /core-concepts-for-github-packages %}
+{% link_in_list /introduction-to-github-packages %}
+{% link_in_list /about-permissions-for-github-packages %}
+{% link_in_list /configuring-a-packages-access-control-and-visibility %}
+{% link_in_list /connecting-a-repository-to-a-package %}
 {% link_in_list /publishing-a-package %}
+{% link_in_list /viewing-packages %}
+{% link_in_list /installing-a-package %}
 {% link_in_list /deleting-and-restoring-a-package %}
 {% link_in_list /deleting-a-package %}
diff --git a/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..d22a3d43d9
--- /dev/null
+++ b/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,32 @@
+---
+title: 安装包
+intro: '您可以从 {% data variables.product.prodname_registry %} 安装包，并将包用作自己项目中的依赖项。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### 关于包的安装
+
+您可以搜索 {% data variables.product.product_name %}，在 {% data variables.product.prodname_registry %} 中找到可安装在自己项目中的包。 更多信息请参阅“[搜索 {% data variables.product.prodname_registry %} 中的包](/github/searching-for-information-on-github/searching-for-packages)”。
+
+找到包后，您可以在包页面上阅读包的说明以及安装和使用说明。
+
+### 安装包
+
+您可以按照一般准则，使用任何 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}支持的包客户端{% else %}为您的实例启用的包类型{% endif %}从 {% data variables.product.prodname_registry %} 安装包。
+
+1. 按照包客户端的说明，向 {% data variables.product.prodname_registry %} 验证。 For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. 按照包客户端的说明安装包。
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..57e2495a26
--- /dev/null
+++ b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,133 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} 是一项软件包托管服务，允许您私下为指定的用户托管您的软件包{% if currentVersion == "github-ae@latest" %}，或在内部为您的企业{% else %}或公开{% endif %}托管，以及在您的项目中使用软件包作为依赖项。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### 关于 {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} 是一种包托管服务，与 {% data variables.product.prodname_dotcom %} 完全集成。 {% data variables.product.prodname_registry %} 将您的源代码和软件包组合在一起，以提供集成的权限管理{% if currentVersion != "github-ae@latest" %}和计费{% endif %}，使您能够在 {% data variables.product.product_name %} 上专注于软件开发。
+
+您可以将 {% data variables.product.prodname_registry %} 与 {% data variables.product.product_name %} API、{% data variables.product.prodname_actions %} 以及 web 挂钩集成在一起，以创建端到端的 DevOps 工作流程，其中包括您的代码、CI 和部署解决方案。
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% if currentVersion == "free-pro-team@latest" %}The {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. 更多信息请参阅“[查看包](/packages/manage-packages/viewing-packages)”。
+
+#### Overview of package permissions and visibility
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| 权限                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |                                                                  |
+| {% if currentVersion == "free-pro-team@latest" %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.product.prodname_container_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |                                                                  |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                                                                  |
+| 可见性                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | {% data reusables.package_registry.public-or-private-packages %}
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+### 关于 {% data variables.product.prodname_registry %} 的计费
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} 更多信息请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)”。
+
+{% endif %}
+
+### 支持的客户端和格式
+<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+
+{% data variables.product.prodname_registry %} 使用您已经熟悉的原生包工具命令来发布和安装包版本。
+#### 对包注册表的支持
+
+| 语言         | 描述                     | 包格式                                 | 包客户端         |
+| ---------- | ---------------------- | ----------------------------------- | ------------ |
+| JavaScript | 节点包管理器                 | `package.json`                      | `npm`        |
+| Ruby       | RubyGems 包管理器          | `Gemfile`                           | `gem`        |
+| Java       | Apache Maven 项目管理和理解工具 | `pom.xml`                           | `mvn`        |
+| Java       | Java 的 Gradle 构建自动化工具  | `build.gradle` 或 `build.gradle.kts` | `gradle`     |
+| .NET       | .NET 的 NuGet 包管理       | `nupkg`                             | `dotnet` CLI |
+| 不适用        | Docker 容器管理平台          | `Dockerfile`                        | `Docker`     |
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+{% note %}
+
+**注：**禁用子域隔离时，不支持 Docker。
+
+{% endnote %}
+
+有关子域隔离的更多信息，请参阅“[启用子域隔离](/enterprise/admin/configuration/enabling-subdomain-isolation)”。
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% if currentVersion == "free-pro-team@latest" %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+{% endif %}
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### 管理包
+
+{% if currentVersion == "free-pro-team@latest" %}
+You can delete a package in the {% data variables.product.product_name %} user interface or using the REST API. 更多信息请参阅“[{% data variables.product.prodname_registry %} API](/rest/reference/packages)”。
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@3.0" %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. 或者对 repo-scoped 包，您可以使用 GraphQL 删除私有包的版本。
+{% endif %}
+
+{% if currentVersion ver_lt "enterprise-server@3.1" %}
+您可以在 {% data variables.product.product_name %} 用户界面中或使用 GraphQL API 删除私有包的版本。
+{% endif %}
+
+{% if currentVersion == "github-ae@latest" %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}”和“[使用 GraphQL 建立呼叫](/graphql/guides/forming-calls-with-graphql)”。
+
+您可以配置 web 挂钩来订阅与包相关的事件，例如包的发布或更新等事件。 更多信息请参阅“[`package` web 挂钩事件](/webhooks/event-payloads/#package)”。
+
+### 联系支持
+
+{% if currentVersion == "free-pro-team@latest" %}
+如果您对 {% data variables.product.prodname_registry %} 有反馈或功能请求，请使用 [{% data variables.product.prodname_registry %} 反馈表](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages)。
+
+如果在 {% data variables.product.prodname_registry %} 方面遇到以下问题，请使用[我们的联系表](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages)联系 {% data variables.contact.github_support %}：
+
+* 遇到任何与文档相矛盾的事情
+* 遇到模糊或不清楚的错误
+* 发布的包中含有敏感数据，例如违反 GDPR、API 密钥或个人身份信息
+
+{% else %}
+如果您需要对 {% data variables.product.prodname_registry %} 的支持，请联系网站管理员。
+
+{% endif %}
diff --git a/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md
index 92596382c0..cef1a07af0 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md
@@ -19,7 +19,7 @@ versions:
 
 您可以在包页面上提供说明和其他详细信息，例如安装和使用说明，以帮助他人了解和使用您的包。 {% data variables.product.product_name %} 提供每个版本的元数据，例如发布日期、下载活动和最新版本。 要查看示例包页面，请参阅 [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1)。
 
-{% data reusables.package_registry.public-or-private-packages %} 一个仓库可包含多个包。 为避免混淆，请确保使用自述文件和说明清楚地阐明每个包的相关信息。
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. 为避免混淆，请确保使用自述文件和说明清楚地阐明每个包的相关信息。
 
 {% if currentVersion == "free-pro-team@latest" %}
 如果软件包的新版本修复了安全漏洞，您应该在仓库中发布安全通告。
@@ -30,10 +30,10 @@ versions:
 
 您可以按照一般准则，使用任何 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}支持的包客户端{% else %}为您的实例启用的包类型{% endif %}将包发布到 {% data variables.product.prodname_registry %}。
 
-1. 针对要完成的任务，创建具有适当作用域的访问令牌或使用现有的此类令牌。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。
+1. 针对要完成的任务，创建具有适当作用域的访问令牌或使用现有的此类令牌。 For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 2. 按照包客户端的说明，使用访问令牌向 {% data variables.product.prodname_registry %} 验证。
 3. 按照包客户端的说明发布包。
 
-有关包客户端的具体说明，请参阅“[将 {% data variables.product.prodname_registry %} 用于项目的生态系统](/packages/using-github-packages-with-your-projects-ecosystem)”。
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
 
-在发布包后，您可以在 {% data variables.product.prodname_dotcom %} 上查看该包。 更多信息请参阅“[查看包](/packages/publishing-and-managing-packages/viewing-packages)”。
+在发布包后，您可以在 {% data variables.product.prodname_dotcom %} 上查看该包。 更多信息请参阅“[查看包](/packages/learn-github-packages/viewing-packages)”。
diff --git a/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md b/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..102460aacf
--- /dev/null
+++ b/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,56 @@
+---
+title: 查看包
+intro: 您可以查看已发布到仓库的包的详细信息，也可以按组织或用户缩小结果范围。
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+### 查看仓库的包
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+{% data reusables.package_registry.repo-scoped-and-granular-permissions-packages %}
+
+{% data reusables.package_registry.package-page-info %}
+
+### 查看仓库的包
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+### 查看组织的包
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+3. 在组织名称下，单击 {% octicon "package" aria-label="The package icon" %} **Packages（包）**。
+{% data reusables.package_registry.navigate-to-packages %}
+
+### 查看您的包
+
+You can find and view any package you've published across all organizations and repositories.
+
+{% data reusables.profile.access_profile %}
+2. 在个人资料页面顶部的主导航栏中，单击 **Packages（包）**。 ![项目选项卡](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+### 延伸阅读
+
+- “[搜索包](/github/searching-for-information-on-github/searching-for-packages)”
diff --git a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..db022b22ec
--- /dev/null
+++ b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,13 @@
+---
+title: About GitHub Packages and GitHub Actions
+intro: Learn the fundamentals of managing packages through your {% data variables.product.prodname_actions %} workflows.
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..9d5bc2361d
--- /dev/null
+++ b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,18 @@
+---
+title: Example workflows for publishing a package
+intro: 'To help you get started with your own custom workflows, review some example workflows for publishing packages.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+You can find example workflows in "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" or in any of these {% data variables.product.prodname_actions %} guides:
+
+  - [发布 Node.js 包](/actions/guides/publishing-nodejs-packages)
+  - [发布 Docker 映像](/actions/guides/publishing-docker-images)
+  - [使用 Maven 发布 Java 包](/actions/guides/publishing-java-packages-with-maven)
+  - [使用 Gradle 发布 Java 包](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..790a661916
--- /dev/null
+++ b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,16 @@
+---
+title: Managing GitHub packages using GitHub Actions workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'You can safely publish and consume packages by building custom workflows that can also build, test, and deploy your code.'
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% link_in_list /publishing-and-installing-a-package-with-github-actions %}
+{% link_in_list /example-workflows-for-publishing-a-package %}
+{% link_in_list /about-github-packages-and-github-actions %}
diff --git a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..a370519036
--- /dev/null
+++ b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,455 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+{% data reusables.actions.ae-beta %}
+{% data reusables.actions.ae-self-hosted-runners-notice %}
+
+### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+#### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)."
+
+{% endif %}
+
+#### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+
+{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}It has read and write permissions for packages in the repository where the workflow runs. {% endif %}For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+### About permissions and package access for repository-owned packages
+
+{% note %}
+
+**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.
+
+{% endnote %}
+
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
+
+{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+
+{% if currentVersion == "free-pro-team@latest" %}
+### About permissions and package access for {% data variables.product.prodname_container_registry %}
+
+The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions.
+
+All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+### Default permissions and access settings for containers modified through workflows
+
+When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
+
+For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
+- The container inherits the visibility and permissions model of the repository where the workflow is run.
+- Repository admins where the workflow is run become the admins of the container once the container is created.
+
+These are more examples of how default permissions work for workflows that manage packages.
+
+| {% data variables.product.prodname_actions %} workflow task | Default permissions and access |
+|----|----|
+| Download an existing container | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br>
+| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.
+| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.
+
+You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+### Publishing a package using an action
+
+You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build and test your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}:
+
+- Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
+  ```yaml{:copy}
+  name: Create and publish a package
+  on:
+    push:
+      branches: ['release']
+  jobs:
+    run-npm-build:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v2
+        - name: npm install and build webpack
+          run: |
+            npm install
+            npm run build
+        - uses: actions/upload-artifact@main
+          with:
+            name: webpack artifacts
+            path: public/
+
+    run-npm-test:
+      runs-on: ubuntu-latest
+      needs: run-npm-build
+      strategy:
+        matrix:
+          os: [ubuntu-latest]
+          node-version: [12.x, 14.x]
+      steps: {% raw %}
+        - uses: actions/checkout@v2
+        - name: Use Node.js ${{ matrix.node-version }}
+          uses: actions/setup-node@v1
+          with:
+            node-version: ${{ matrix.node-version }}{% endraw %}
+        - uses: actions/download-artifact@main
+          with:
+            name: webpack artifacts
+            path: public
+        - name: npm install, and test
+          run: |
+            npm install
+            npm test
+          env:
+            CI: true
+
+    build-and-push-image:
+      runs-on: ubuntu-latest {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+      permissions: 
+        contents: read
+        packages: write {% endif %}
+      needs: run-npm-test
+      steps:
+        - name: Checkout
+          uses: actions/checkout@v2
+        - name: Build container image
+          uses: docker/build-push-action@v1
+          with: {% raw %}
+            username: ${{ github.actor }}
+            password: ${{ secrets.GITHUB_TOKEN }}
+            registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+            repository: ${{ github.repository }}/octo-image {% endraw %}
+            tag_with_sha: true
+            tag_with_ref: true 
+  ```
+
+  The relevant settings are explained in the following table:
+
+  <table>
+  <tr>
+  <td>
+
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+  </td>
+  <td>
+    Configures the <code>Create and publish a package</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: actions/upload-artifact@main
+        with:
+          name: webpack artifacts
+          path: public/
+  ```
+  {% endraw %}
+  </td>
+  <td>
+    This job installs NPM and uses it to build the app.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [14.x]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - uses: actions/download-artifact@main
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
+  </td>
+  </tr> {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  permissions: 
+    contents: read
+    packages: write 
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  </td>
+  </tr> {% endif %}
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+  - name: Build container image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Creates a new step called <code>Build container image</code>. This step runs as part of the <code>build-and-push-image</code> job. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+uses: docker/build-push-action@v1
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+with:
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Sends the required parameters to the <code>build-push-action</code> action. This are defined in the subsequent lines.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+username: ${{ github.actor }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+password: ${{ secrets.GITHUB_TOKEN }}
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines the password that is used to access {% data variables.product.prodname_registry %}.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+  ```yaml
+registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+  ```
+  </td>
+  <td>
+    Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace <code>YOUR-HOSTNAME</code> with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use <code>ghcr.io</code> as the hostname.{% endif %}
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+repository: ${{ github.repository }}/octo-image
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Defines which repository will host the resulting package, and sets the name of the published package. Replace <code>octo-image</code> with the name you want for your package.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_sha: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the first seven characters of the commit's SHA. For example, <code>sha-2f2d842</code>.
+  </td>
+  </tr>
+  <tr>
+  <td>
+
+{% raw %}
+  ```yaml
+tag_with_ref: true
+  ```
+{% endraw %}
+  </td>
+  <td>
+    Tags the published package with the git ref. This can be the name of the branch used to create the package.
+  </td>
+  </tr>
+  </table>
+
+- This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
+- A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
+
+
+### Installing a package using an action
+
+You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+### Upgrading a workflow that accesses `ghcr.io`
+
+{% data reusables.package_registry.github-token-security-over-pat %}
+
+Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**.
+  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add.
+   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image.
+  ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+    permissions:
+      packages: write
+      contents: read{% endif %}
+
+    {% raw %}steps:
+      - uses: actions/checkout@v2
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log into registry
+        # This is where you will update the PAT to GITHUB_TOKEN
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION{% endraw %}
+```
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md
index f870f1e73b..419900faae 100644
--- a/translations/zh-CN/content/packages/quickstart.md
+++ b/translations/zh-CN/content/packages/quickstart.md
@@ -18,7 +18,7 @@ versions:
 
 ### 发布包
 
-1. 在 {% data variables.product.prodname_dotcom %} 上创建新仓库，为节点添加 `.gitignore`。 {% if currentversion ver_lt "enterprise-server@3.1" %} 如果您希望以后删除这个软件包，请创建私有仓库，公共软件包不能删除。{% endif %} 更多信息请参阅“[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)”。
+1. 在 {% data variables.product.prodname_dotcom %} 上创建新仓库，为节点添加 `.gitignore`。 {% if currentVersion ver_lt "enterprise-server@3.1" %} 如果您希望以后删除这个软件包，请创建私有仓库，公共软件包不能删除。{% endif %} 更多信息请参阅“[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)”。
 2. 将仓库克隆到本机。
     ```shell
     $ git clone https://{% if currentVersion == "github-ae@latest" %}<em>YOUR-HOSTNAME</em>{% else %}github.com{% endif %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
@@ -71,7 +71,10 @@ versions:
 
       publish-gpr:
         needs: build
-        runs-on: ubuntu-latest
+        runs-on: ubuntu-latest{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+        permissions:
+          packages: write
+          contents: read{% endif %}
         steps:
           - uses: actions/checkout@v2
           - uses: actions/setup-node@v1
@@ -95,7 +98,7 @@ versions:
 
 ### 查看已发布的包
 
-包在仓库级别发布。 您可以查看仓库中的所有包，也可以搜索特定的包。
+You can view all of the packages you have published.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
@@ -104,14 +107,14 @@ versions:
 
 ### 安装已发布的包
 
-现在，您已发布包，您需要使用它作为项目之间的依赖项。 更多信息请参阅"[配置 npm 用于 {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)"。
+现在，您已发布包，您需要使用它作为项目之间的依赖项。 For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
 
 ### 后续步骤
 
-您刚刚添加的基本工作流程在仓库中创建新版本时运行。 但是，这只是您可以对 {% data variables.product.prodname_registry %} 执行操作的开始。 您可以使用单个工作流和将包发布到多个注册表，触发工作流程以在发生不同事件（如合并拉取请求、管理容器等）时运行。
+您刚刚添加的基本工作流程在仓库中创建新版本时运行。 But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. 您可以使用单个工作流和将包发布到多个注册表，触发工作流程以在发生不同事件（如合并拉取请求、管理容器等）时运行。
 
 合并 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 可以帮助您实现应用程序开发过程几乎每个方面的自动化。 准备好开始了吗？ 以下是一些有用的资源，可用于执行 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 的后续步骤：
 
 - “[了解 {% data variables.product.prodname_registry %}](/packages/learn-github-packages)”，以获取 GitHub Packages 的深入教程
 - “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，以获取 GitHub Actions 的深入教程
-- “[指南](/packages/guides)”，以获取特定用例和示例
+- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
new file mode 100644
index 0000000000..7a5381ba34
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry.md
@@ -0,0 +1,41 @@
+---
+title: Enabling improved container support with the Container registry
+intro: 'To use the {% data variables.product.prodname_container_registry %}, you must enable it for your user or organization account.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  free-pro-team: '*'
+---
+
+{% note %}
+
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. 在测试阶段，存储和带宽是免费的。 更多信息请参阅“[{% data variables.product.prodname_registry %} 简介](/packages/learn-github-packages/introduction-to-github-packages)”。
+
+{% endnote %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your personal account
+
+Once the {% data variables.product.prodname_container_registry %} is enabled for your personal user account, you can publish containers to the {% data variables.product.prodname_container_registry %} owned by your user account.
+
+To use the {% data variables.product.prodname_container_registry %} within an organization, the organization owner must enable the feature for organization members.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. 在左侧，选择“Improved container support（改进的容器支持）”，然后单击 **Enable（启用）**。 ![改进的容器支持](/assets/images/help/settings/improved-container-support.png)
+
+### Enabling the {% data variables.product.prodname_container_registry %} for your organization account
+
+Before organization owners or members can publish container images to the {% data variables.product.prodname_container_registry %}, an organization owner must enable the feature preview for the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. 在左侧，单击 **Packages（包）**。
+5. 在“Improved container support（改进的容器支持）”下，选择“Enable improved container support（启用改进的容器支持）”，然后单击 **Save（保存）**。 ![启用容器注册表支持选项和保存按钮](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png)
+6. 在“Container creation（容器创建）”下，选择是要启用公共、私有或内部容器映像。
+    - To enable organization members to create public container images, select **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, select **Private**. 您可以进一步自定义私有容器映像的可见性。 For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+    - **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, select **Internal**. ![组织成员发布的容器图像的可见性选项](/assets/images/help/package-registry/container-creation-org-settings.png)
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/index.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..985d92ed0d
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with a GitHub Packages registry
+shortTitle: Working with a GitHub Packages registry
+intro: 'Learn how to use a supported {% data variables.product.prodname_registry %} registry.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% if currentVersion == "free-pro-team@latest" %}
+
+![Diagram showing packages support for Docker, Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for Docker, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+### 目录
+
+{% link_in_list /working-with-the-npm-registry %}
+{% link_in_list /working-with-the-rubygems-registry %}
+{% link_in_list /working-with-the-apache-maven-registry %}
+{% link_in_list /working-with-the-gradle-registry %}
+{% link_in_list /working-with-the-nuget-registry %}
+{% link_in_list /working-with-the-docker-registry %}
+{% link_in_list /working-with-the-container-registry %}
+{% link_in_list /enabling-improved-container-support-with-the-container-registry %}
+{% link_in_list /migrating-to-the-container-registry-from-the-docker-registry %}
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..173a509330
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,124 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate your images to the new {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  free-pro-team: '*'
+---
+
+### Key differences between the {% data variables.product.prodname_container_registry %} and the Docker registry
+
+{% data reusables.package_registry.container-registry-beta %}
+
+The {% data variables.product.prodname_container_registry %} supersedes the existing {% data variables.product.prodname_registry %} Docker registry and is optimized to support some of the unique needs of containers.
+
+With the {% data variables.product.prodname_container_registry %} you can:
+- 将容器映像存储在组织和用户帐户中，而不是仓库中。
+- Set granular permissions and visibility independently of repository permissions and visibility.
+- 匿名访问公共容器映像。
+
+|      | Docker registry                                                                                                                                          | {% data variables.product.prodname_container_registry %}
+| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
+| 托管位置 | You can host multiple Docker images in one repository.                                                                                                   | 您可以在一个组织或用户帐户中托管多个容器映像。                                    |
+| 权限   | Each image inherits the permissions of the repository where the image is hosted. <br><br>例如，对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | 对于每个容器映像，您可以选择其他人具有的访问权限级别。 容器映像访问的权限与组织和仓库权限不同。           |
+ Visibility          | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. 私有容器映像仅对组织内被授予访问权限的人员或团队可见。 公共容器映像对任何人都可见。 | Anonymous access    | N/A | You can access public container images anonymously. Foreign layer support | Doesn't support foreign layers, such as Windows images. | Supports foreign layers, such as Windows images.
+
+### 计费更改
+
+During the {% data variables.product.prodname_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and the existing {% data variables.product.prodname_registry %} Docker registry are free of charge. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)."
+
+After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the {% data variables.product.prodname_container_registry %}. 更多信息请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)”。
+
+### 域更改
+
+{% data variables.product.prodname_container_registry %} 的域是 `ghcr.io`。
+
+| 注册表                                                        | 示例 URL                                              |
+| ---------------------------------------------------------- | --------------------------------------------------- |
+| {% data variables.product.prodname_registry %} Docker 注册表  | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` |
+| {% data variables.product.prodname_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME`                          |
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+您需要使用基本 URL `ghcr.io` 向 {% data variables.product.prodname_container_registry %} 验证。 我们建议创建新的访问令牌以使用 {% data variables.product.prodname_container_registry %}。
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### 使用 Docker CLI 迁移 Docker 映像
+
+要移动您在 {% data variables.product.prodname_registry %} Docker 注册表上托管的 Docker 映像，您必须将映像重新发布到 {% data variables.product.prodname_container_registry %}。 我们建议在本地计算机上使用命令行重新发布现有的 Docker 映像。
+
+1. 使用作用域至少为 `read:packages` 的临时 PAT 登录到 Docker 注册表。 此 PAT 将仅用于登录到 Docker 注册表以下拉映像，然后可以删除。
+  {% raw %}
+  ```shell
+  $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+2. 下拉要迁移的映像，将 OWNER 替换为拥有仓库的用户或组织帐户的名称，将 REPOSITORY 替换为包含项目的仓库，将 IMAGE_NAME 替换为包或映像的名称，将 VERSION 替换为要安装的映像的标记。 例如，`docker ull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` 拉取 octo-org 组织中 `octoshift/octoshift` 映像的最新标记。
+  ```shell
+  $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+
+3. 使用新域和新映像名称重新标记映像。 更多信息请参阅 Docker 文档中的“[Docker 标记](https://docs.docker.com/engine/reference/commandline/tag/)”。 使用在上一步中用于 SOURCE URL 同一个URL。 将 TARGET_OWNER 替换为要将容器映像迁移到其中的用户或组织，将 TARGET_IMAGE_NAME 替换为新 {% data variables.product.prodname_container_registry %} 映像名称。
+  ```shell
+  $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION
+  ```
+
+4. 登录到新的 {% data variables.product.prodname_container_registry %}。 我们建议创建限于 `read:packages` 和 `write:packages` 范围的新 PAT，因为您不再需要 `repo` 范围，并且您之前的 PAT 不能具有 `write:packages` 范围。
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
+  ```
+  {% endraw %}
+5. 将重新标记的映像推送到 {% data variables.product.prodname_container_registry %}。
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION
+  ```
+
+### 更新 {% data variables.product.prodname_actions %} 工作流程
+
+{% data reusables.package_registry.feature-preview-for-container-registry %}
+
+如果您有 {% data variables.product.prodname_actions %} 工作流程使用来自 {% data variables.product.prodname_registry %} Docker 注册表的 Docker 映像，则可能需要将工作流程更新到 {% data variables.product.prodname_container_registry %}，以允许匿名访问公共容器映像、更细致的访问权限以及更好的容器存储和带宽兼容性。
+
+1. 将 Docker 映像迁移到 `ghcr.io` 上的新 {% data variables.product.prodname_container_registry %}。 例如，请参阅“[使用 Docker CLI 迁移 Docker 映像](#migrating-a-docker-image-using-the-docker-cli)”。
+
+2. 在 {% data variables.product.prodname_actions %} 工作流程文件中，将包 url 从 `https://docker.pkg.github.com` 更新到 `ghcr.io`。
+
+3. 将新的 {% data variables.product.prodname_container_registry %} 身份验证个人访问令牌 (PAT) 添加为 GitHub ACtions 密码。 The {% data variables.product.prodname_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. 更多信息请参阅“[创建和存储加密密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)”。
+
+4. 在 {% data variables.product.prodname_actions %} 工作流程文件中更新身份验证 PAT，将 Docker 注册表 PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) 替换为 {% data variables.product.prodname_container_registry %} PAT 的新变量，例如 {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}。
+
+#### 更新的工作流程示例
+
+如果工作流程的一部分访问由 Docker 注册表托管的 Docker 映像，如：
+
+{% raw %}
+```yaml
+echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin
+docker pull docker.pkg.github.com/github/octoshift/octoshift:latest
+docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest
+docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA
+```
+{% endraw %}
+
+然后，您需要使用新的 URL 和 PAT {% data variables.product.prodname_container_registry %} 更新工作流程，如：
+
+{% raw %}
+```yaml
+# new login with new container registry url and PAT
+echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
+# new container registry urls added
+docker pull ghcr.io/github/octoshift:latest
+docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest
+docker push ghcr.io/github/octoshift:$GITHUB_SHA
+```
+{% endraw %}
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..fc40dc7474
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,192 @@
+---
+title: Working with the Apache Maven registry
+intro: '您可以配置 Apache Maven 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 Java 项目中的依赖项。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。
+
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 使用个人访问令牌进行身份验证
+
+{% data reusables.package_registry.required-scopes %}
+
+通过编辑 *~/.m2/settings.xml* 文件以包含个人访问令牌，您可以使用 Apache Maven 向 {% data variables.product.prodname_registry %} 验证。 如果 *~/.m2/settings.xml* 文件不存在，请新建该文件。
+
+在 `servers` 标记中，添加带 `id` 的子 `server` 标记，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌。
+
+在 `repositories` 标记中，通过将仓库的 `id` 映射到您在包含凭据的 `server` 标记中添加的 `id` 来配置仓库。 Replace {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* with the host name of {% data variables.product.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. 由于不支持大写字母，因此，即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母，也必须对仓库所有者使用小写字母。
+
+如果要与多个仓库交互，您可以将每个仓库添加到 `repository` 标记中独立的子 `repositories`，将每个仓库的 `id` 映射到 `servers` 标记中的凭据。
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% if enterpriseServerVersions contains currentVersion %}
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://maven.pkg.github.com/OWNER/*</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+### 发布包
+
+{% data reusables.package_registry.default-name %} 例如，{% data variables.product.prodname_dotcom %} 将名为 `com.example:test` 的包发布到名为 `OWNER/test` 的仓库中。
+
+如果要将多个包发布到同一个仓库，您可以在 `pom.xml` 文件的 `<distributionManagement>` 元素中包含该仓库的 URL。 {% data variables.product.prodname_dotcom %} 将根据该字段匹配仓库。 由于仓库名称也是 `distributionManagement` 元素的一部分，因此将多个包发布到同一个仓库无需额外步骤、
+
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+
+1. 编辑位于包目录中的 *pom.xml* 文件的 `distributionManagement` 元素，将 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名，将 {% endif %}`OWNER` 替换为拥有该仓库的用户或组织帐户的名称，并且将 `REPOSITORY` 替换为包含项目的仓库的名称。{% if enterpriseServerVersions contains currentVersion %}
+
+  如果您的实例启用了子域隔离功能：{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% if enterpriseServerVersions contains currentVersion %}
+  如果您的实例禁用了子域隔离：
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. 发布包。
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### 安装包
+
+要从 {% data variables.product.prodname_registry %} 安装 Apache Maven 包，请编辑 *pom.xml* 文件以包含该包作为依赖项。 如果要从多个仓库安装包，请为每个仓库添加 `repository` 标记。 有关在项目中使用 *pom.xml* 文件的更多信息，请参阅 Apache Maven 文档中的“[POM 简介](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)”。
+
+{% data reusables.package_registry.authenticate-step %}
+2. 将包依赖项添加到项目 *pom.xml* 文件的 `dependencies` 元素，将 `com.example:test` 替换为您的包。
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. 安装包。
+
+  ```shell
+  $ mvn install
+  ```
+
+### 延伸阅读
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..24cf1abfe2
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,121 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://ghcr.io`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+versions:
+  free-pro-team: '*'
+---
+
+{% data reusables.package_registry.container-registry-beta %}
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About {% data variables.product.prodname_container_registry %} support
+
+To push and pull container images, an organization admin or the owner of a personal account must enable the {% data variables.product.prodname_container_registry %}. 更多信息请参阅“[使用 {% data variables.product.prodname_container_registry %} 启用改进的容器支持](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)”。
+
+When installing or publishing a Docker image, the Container registry supports foreign layers, such as Windows images.
+
+{% data variables.product.prodname_container_registry %} 目前支持以下容器映像格式：
+
+* [Docker 映像清单 V2，架构 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) 规格](https://github.com/opencontainers/image-spec)
+
+### Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+### 推送容器映像
+
+此示例推送最新版本的 `IMAGE-NAME`。
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+此示例推送 `2.5` 版的映像。
+  ```shell
+  $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5
+  ```
+
+首次发布包时，默认可见性是私有的。 To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+### 拉取容器映像
+
+#### 通过摘要拉取
+
+为了确保始终使用相同的映像，您可以通过 `digest` SHA 值指定要拉取的准确容器映像版本。
+
+1. 要查找摘要 SHA 值，请使用 `docker inspect` 或 `docker pull`，并复制 `Digest:` 后的 SHA 值
+  ```shell
+  $ docker inspect ghcr.io/OWNER/IMAGE_NAME
+  ```
+2. 按需要在本地删除映像。
+  ```shell
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
+  ```
+
+3. 拉取图像名称后有 `@YOUR_SHA_VALUE` 的容器映像。
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+#### 按名称拉取
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME
+  ```
+
+#### 按名称和版本拉取
+
+显示按名称和 `1.14.1` 版本标记拉取映像的 Docker CLI 示例：
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1
+  > ghcr.io/orgname/image-name/release:1.14.1
+  ```
+
+#### 按名称和最新版本拉取
+
+  ```shell
+  $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for ghcr.io/user/image-name:latest
+  > ghcr.io/user/image-name:latest
+  ```
+
+### 构建容器映像
+
+此示例构建 `hello_docker` 映像：
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+### 标记容器映像
+
+1. 找到要标记的 Docker 映像的 ID。
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > ghcr.io/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > ghcr.io/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. 使用映像 ID 以及所需的映像名称和托管目标标记 Docker 映像。
+  ```shell
+  $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest
+  ```
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..ad58d3ba37
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,262 @@
+---
+title: Working with the Docker registry
+intro: 'You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry, which uses the package namespace `https://docker.pkg.github.com`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。
+
+{% data reusables.package_registry.docker-vs-container-registry %}
+
+### About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+{% if currentVersion == "enterprise-server@2.22" %}
+
+必须在 {% data variables.product.product_location %} 的网站管理员为您的实例启用 Docker 支持和子域隔离后，您才可在 {% data variables.product.prodname_registry %} 上使用 Docker 注册表。 更多信息请参阅“[为企业管理 GitHub Packages](/enterprise/admin/packages)”。
+
+{% endif %}
+
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 使用个人访问令牌进行身份验证
+
+{% data reusables.package_registry.required-scopes %}
+
+您可以使用 `docker` 登录命令，通过 Docker 向 {% data variables.product.prodname_registry %} 验证。
+
+为确保凭据安全，我们建议您将个人访问令牌保存在您计算机上的本地文件中，然后使用 Docker 的 `--password-stdin` 标志从本地文件读取您的令牌。
+
+{% if currentVersion == "free-pro-team@latest" %}
+{% raw %}
+  ```shell
+  $ cat <em>~/TOKEN.txt</em> | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+{% endif %}
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login docker.HOSTNAME -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+{% raw %}
+ ```shell
+ $ cat <em>~/TOKEN.txt</em> | docker login <em>HOSTNAME</em> -u <em>USERNAME</em> --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+要使用此示例登录命令，请将 `USERNAME` 替换为您的 {% data variables.product.product_name %} 用户名{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}，将 `HOSTNAME` 替换为 {% data variables.product.product_location %},{% endif %} 的 URL，并将 `~/TOKEN.txt` 替换为您用于 {% data variables.product.product_name %} 的个人访问令牌的文件路径。
+
+更多信息请参阅“[Docker 登录](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)”。
+
+### 发布映像
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**注：**映像名称只能使用小写字母。
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} 支持每个仓库的多个顶层 Docker 镜像。 仓库可以拥有任意数量的映像标记。 在发布或安装大于 10GB 的 Docker 映像（每个图层上限为 5GB）时，可能会遇到服务降级的情况。 更多信息请参阅 Docker 文档中的“[Docker 标记](https://docs.docker.com/engine/reference/commandline/tag/)”。
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. 使用 `docker images` 确定 docker 映像的名称和 ID。
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > <em>IMAGE_NAME</em>        <em>VERSION</em>    <em>IMAGE_ID</em>       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+  {% endif %}
+  ```shell
+  如果尚未为包构建 docker 映像，请构建映像，将 <em x-id="3">OWNER</em> 替换为拥有仓库的用户或组织帐户的名称，将 <em x-id="3">REPOSITORY</em> 替换为包含项目的仓库的名称，将 <em x-id="3">IMAGE_NAME</em> 替换为包或映像的名称，将 <em x-id="3">VERSION</em> 替换为构建时的包版本，将 <em x-id="3">PATH</em> 替换为映像路径（如果映像未在当前工作目录中）。
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+  ```shell
+  $ docker tag <em>IMAGE_ID</em> <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+  {% endif %}
+  ```shell
+  $ docker build -t docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+  ```shell
+  $ docker build -t <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em> <em>PATH</em>
+  ```
+  {% endif %}
+  {% endif %}
+4. 将映像发布到 {% data variables.product.prodname_registry %}。
+  {% if currentVersion == "free-pro-team@latest" %}
+  ```shell
+  $ docker push docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% else %}
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+  {% endif %}
+  ```shell
+  $ docker push docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% if currentVersion ver_gt "enterprise-server@2.22" %}
+  例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+  ```shell
+  $ docker push <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **注：**必须使用 `IMAGE_NAME:VERSION` 推送映像，而不能使用 `IMAGE_NAME:SHA`。
+
+  {% endnote %}
+
+#### 发布 Docker 映像的示例
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+这些示例假设您的实例已启用子域隔离。
+{% endif %}
+
+您可以使用映像 ID 将 `monalisa` 映像的 1.0 版本发布到 `octocat/octo-app` 仓库。
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+您可能首次发布新的 Docker 映像并将其命名为 `monalisa`。
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.<em>HOSTNAME</em>/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+### 下载映像
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+您可以使用 `docker pull` 命令从 {% data variables.product.prodname_registry %} 安装 Docker 映像，将 *OWNER* 替换为拥有仓库的用户或组织帐户的名称，将 *REPOSITORY* 替换为包含项目的仓库的名称，将 *IMAGE_NAME* 替换为包或映像的名称，{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名称，{% endif %}并将 *TAG_NAME* 替换为要安装的映像的标记。
+
+{% if currentVersion == "free-pro-team@latest" %}
+```shell
+$ docker pull docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+{% endif %}
+```shell
+$ docker pull docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+```shell
+$ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**注：**必须使用 `IMAGE_NAME:VERSION` 推送映像，而不能使用 `IMAGE_NAME:SHA`。
+
+{% endnote %}
+
+### 延伸阅读
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..caa50144e5
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,211 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。
+
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+#### 使用个人访问令牌进行身份验证
+
+{% data reusables.package_registry.required-scopes %}
+
+您可以使用 Gradle Groovy 或 Kotlin DSL，通过 Gradle 向 {% data variables.product.prodname_registry %} 验证，方法是编辑 *build.gradle* 文件 (Gradle Groovy) 或 *build.gradle.kts* 文件 (Kotlin DSL) 以包含您的个人访问令牌。 您还可以配置 Gradle Groovy 和 Kotlin DSL 以识别仓库中的一个或多个包。
+
+{% if enterpriseServerVersions contains currentVersion %}
+将 *REGISTRY-URL* 替换为您实例的 Maven 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `maven.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/maven`。 在任一情况下，都将 *HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。
+{% elsif currentVersion == "github-ae@latest" %}
+将 *REGISTRY-URL* 替换为企业的 Maven 注册表 `maven.HOSTNAME` 的 URI。 Replace *HOSTNAME* with the host name of {% data variables.product.product_location %}.
+{% endif %}
+
+将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *REPOSITORY* 替换为要发布的包所在仓库的名称，将 *OWNER* 替换为 {% data variables.product.prodname_dotcom %} 上拥有该仓库的用户或组织帐户的名称。 由于不支持大写字母，因此，即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母，也必须对仓库所有者使用小写字母。
+
+{% note %}
+
+**注：**{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} 关于示例，请参阅“[配置 Apache Maven 用于 {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)”。
+
+{% endnote %}
+
+##### 将 Gradle Groovy 用于一个仓库中单个包的示例
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+##### 将 Gradle Groovy 用于同一个仓库中多个包的示例
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+##### 将 Kotlin DSL 用于同一个仓库中单个包的示例
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+            }
+        }
+    }
+    publications {
+        register<MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+##### 将 Kotlin DSL 用于同一个仓库中多个包的示例
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure<PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}<em>REGISTRY-URL</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("<em>USERNAME</em>")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("<em>TOKEN</em>")
+                }
+            }
+        }
+        publications {
+            register<MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+### 发布包
+
+{% data reusables.package_registry.default-name %} 例如，{% data variables.product.prodname_dotcom %} 将名为 `com.example.test` 的包发布到 `OWNER/test` {% data variables.product.prodname_registry %} 仓库中。
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. 创建包后，您可以发布包。
+
+  ```shell
+   $ gradle publish
+  ```
+
+### 安装包
+
+通过添加包作为您项目中的依赖项，您可以安装包。 更多信息请参阅 Gradle 文档中的“[声明依赖项](https://docs.gradle.org/current/userguide/declaring_dependencies.html)”。
+
+{% data reusables.package_registry.authenticate-step %}
+2. 将包依赖项添加到您的 *build.gradle* 文件 (Gradle Groovy) 或 *build.gradle.kts* 文件 (Kotlin DSL)。
+
+  使用 Gradle Groovy 的示例：
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  使用 Kotlin DSL 的示例：
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. 将 maven 插件添加到您的 *build.gradle* 文件 (Gradle Groovy) 或 *build.gradle.kts* 文件 (Kotlin DSL)。
+
+  使用 Gradle Groovy 的示例：
+  ```shell
+  plugins {
+      id 'maven'
+  }
+  ```
+  使用 Kotlin DSL 的示例：
+  ```shell
+  plugins {
+      `maven`
+  }
+  ```
+
+  3. 安装包。
+
+  ```shell
+  $ gradle install
+  ```
+
+### 延伸阅读
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..9f086379e5
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,218 @@
+---
+title: Working with the npm registry
+intro: '您可以配置 npm 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 npm 项目中的依赖项。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+### 已发布 npm 版本的限制
+
+如果您发布超过 1,000npm 软件包版本到 {% data variables.product.prodname_registry %}，在使用过程中可能会出现性能问题和超时。
+
+将来，为了提高服务的性能，您将无法在 {% data variables.product.prodname_dotcom %} 上发布超过 1，000 个版本的包。 在达到此限制之前发布的任何版本仍将是可读的。
+
+如果达到此限制，请考虑删除包版本或联系支持人员寻求帮助。 实施此限制后，我们的文档将就此限制进行更新。 更多信息请参阅“{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}”或“[联系支持](/packages/learn-github-packages/about-github-packages#contacting-support)”。
+
+{% endif %}
+
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 使用个人访问令牌进行身份验证
+
+{% data reusables.package_registry.required-scopes %}
+
+通过编辑您的每用户 *~/.npmrc* 文件以包含个人访问令牌，或者在命令行上使用用户名和个人访问令牌登录 npm，您可以使用 npm 向 {% data variables.product.prodname_registry %} 验证。
+
+要通过将个人访问令牌添加到 *~/.npmrc* 文件进行身份验证，请编辑项目的 *~/.npmrc* 文件以包含以下行，将 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名，并将 {% endif %}*TOKEN* 替换为您的个人访问令牌。 如果 *~/.npmrc* 文件不存在，请新建该文件。
+
+{% if enterpriseServerVersions contains currentVersion %}
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+{% endif %}
+
+```shell
+//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}/:_authToken=<em>TOKEN</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+```shell
+$ npm login --registry=https://npm.pkg.github.com
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+要通过登录到 npm 进行身份验证，请使用 `npm login` 命令，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *PUBLIC-EMAIL-ADDRESS* 替换为您的电子邮件地址。
+
+如果 {% data variables.product.prodname_registry %} 不是使用 npm 的默认包注册表，并且您要使用 `npm audit` 命令，我们建议您在对 {% data variables.product.prodname_registry %} 进行身份验证时，将 `--scope` 标志与包的所有者一起使用。
+
+{% if enterpriseServerVersions contains currentVersion %}
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+{% endif %}
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}
+
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+```shell
+$ npm login --scope=@<em>OWNER</em> --registry=https://<em>HOSTNAME</em>/_registry/npm/
+> Username: <em>USERNAME</em>
+> Password: <em>TOKEN</em>
+> Email: <em>PUBLIC-EMAIL-ADDRESS</em>
+```
+{% endif %}
+
+### 发布包
+
+{% note %}
+
+**注：**包名称和作用域只能使用小写字母。
+
+{% endnote %}
+
+默认情况下，{% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的名称字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如，您要发布一个名为 `@my-org/test` 的包到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。 通过在包目录中包含 *README.md* 文件，您可以添加包列表页面的摘要。 更多信息请参阅 npm 文档中的“[使用 package.json](https://docs.npmjs.com/getting-started/using-a-package.json)”和“[如何创建 Node.js 模块](https://docs.npmjs.com/getting-started/creating-node-modules)”。
+
+通过在 *package.json* 文件中包含 `URL` 字段，您可以将多个包发布到同一个 {% data variables.product.prodname_dotcom %} 仓库。 更多信息请参阅“[将多个包发布到同一个仓库](#publishing-multiple-packages-to-the-same-repository)”。
+
+您可以使用项目中的本地 *.npmrc* 文件或使用 *package.json* 中的 `publishConfig` 选项来设置项目的作用域映射。 {% data variables.product.prodname_registry %} 只支持作用域内的 npm 包。 作用域内的包具有名称格式 `@owner/name`。 作用域内的包总是以 `@` 符号开头。 您可能需要更新 *package.json* 中的名称以使用作用域内的名称。 例如，`"name": "@codertocat/hello-world-npm"`。
+
+{% data reusables.package_registry.viewing-packages %}
+
+#### 使用本地 *.npmrc* 文件发布包
+
+您可以使用 *.npmrc* 文件来配置项目的作用域映射。 在 *.npmrc* 文件中，使用 {% data variables.product.prodname_registry %} URL 和帐户所有者，使 account owner so {% data variables.product.prodname_registry %} 知道将包请求路由到何处。 使用 *.npmrc* 文件防止其他开发者意外地将包发布到 npmjs.org 而不是 {% data variables.product.prodname_registry %}。
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. 验证项目的 *package.json* 中包的名称。 `name` 字段必须包含包的作用域和名称。 例如，如果您的包名为 "test"，并且要发布到 "My-org" {% data variables.product.prodname_dotcom %} 组织，则 *package.json* 中的 `name` 字段应为 `@my-org/test`。
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+#### 使用 *package.json* 文件中的 `publishConfig` 发布包
+
+您可以使用 *package.json* 文件中的 `publishConfig` 元素来指定要发布包的注册表。 更多信息请参阅 npm 文档中的“[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)”。
+
+1. 编辑包的 *package.json* 文件并包含 `publishConfig` 条目。
+  {% if enterpriseServerVersions contains currentVersion %}
+  有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>/{% endif %}"
+  },
+  ```
+  {% if enterpriseServerVersions contains currentVersion %}
+  例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+   ```shell
+   "publishConfig": {
+     "registry":"https://<em>HOSTNAME</em>/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### 将多个包发布到同一个仓库
+
+要将多个包发布到同一个仓库，您可以在每个包的 *package.json* 文件的 `repository` 字段中包含 {% data variables.product.prodname_dotcom %} 仓库的 URL。
+
+为确保仓库的 URL 正确，请将 REPOSITORY 替换为要发布的包所在仓库的名称，将 OWNER 替换为拥有该仓库的 {% data variables.product.prodname_dotcom %} 用户或组织帐户的名称。
+
+{% data variables.product.prodname_registry %} 将根据该 URL 匹配仓库，而不是根据包名称。
+
+```shell
+"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/<em>OWNER</em>/<em>REPOSITORY</em>",
+```
+
+### 安装包
+
+通过在项目的 *package.json* 文件中将包添加为依赖项，您可以从 {% data variables.product.prodname_registry %} 安装包。 有关在项目中使用 *package.json* 的更多信息，请参阅 npm 文档中的“[使用 package.json](https://docs.npmjs.com/getting-started/using-a-package.json)”。
+
+默认情况下，您可以从一个组织添加包。 更多信息请参阅“[从其他组织安装包](#installing-packages-from-other-organizations)”。
+
+还需要将 *.npmrc* 文件添加到项目，使所有安装包的请求都会通过 {% data variables.product.prodname_registry %}。 通过 {% data variables.product.prodname_registry %} 路由所有包请求时，您可以使用 *npmjs.com* 作用域内和作用域外的包。 更多信息请参阅 npm 文档中的“[npm 作用域](https://docs.npmjs.com/misc/scope)”。
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+4. 配置项目中的 *package.json* 使用要安装的包。 要将包依赖项添加到 {% data variables.product.prodname_registry %} 的 *package.json* 文件，请指定完整的作用域内包名称，例如 `@my-org/server`。 对于来自 *npmjs.com* 的包，请指定全名，例如 `@babel/core` 或 `@lodash`。 例如，以下 *package.json* 将 `@octo-org/octo-app` 包用作依赖项。
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the @octo-org/octo-app package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "@octo-org/octo-app": "1.0.0"
+    }
+  }
+  ```
+5. 安装包。
+
+  ```shell
+  $ npm install
+  ```
+
+#### 从其他组织安装包
+
+默认情况下，您只能使用来自一个组织的 {% data variables.product.prodname_registry %} 包。 如果想将包请求传送到多个组织和用户，您可以添加额外行到 *.npmrc* 文件，将 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}*HOSTNAME* 替换为 {% data variables.product.product_location %} 实例的主机名，并{% endif %}将 *OWNER* 替换为拥有项目所在仓库的用户或组织帐户的名称。
+
+{% if enterpriseServerVersions contains currentVersion %}
+有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。
+{% endif %}
+
+```shell
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+@<em>OWNER</em>:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.<em>HOSTNAME</em>{% endif %}
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+```shell
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+@<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+```
+{% endif %}
+
+{% if currentVersion ver_gt "enterprise-server@2.22" %}
+### 使用官方 NPM 注册表
+
+{% data variables.product.prodname_registry %} 允许您访问 `registry.npmjs.com` 上的官方 NPM 注册表，前提是您的 {% data variables.product.prodname_ghe_server %} 管理员已启用此功能。 更多信息请参阅[连接到官方 NPM 注册表](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry)。
+{% endif %}
+
+### 延伸阅读
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..3c8687665b
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,237 @@
+---
+title: Working with the NuGet registry
+intro: '您可以配置 `dotnet` 命令行接口 (CLI) 以将 NuGet 包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 .NET 项目中的依赖项。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。
+
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+#### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a token in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 使用个人访问令牌进行身份验证
+
+{% data reusables.package_registry.required-scopes %}
+
+要使用 `dotnet` 命令行接口 (CLI) 向 {% data variables.product.prodname_registry %} 验证，请在项目目录中创建一个 *nuget.config* 文件，将 {% data variables.product.prodname_registry %} 指定为 `dotnet` CLI 客户端的 `packageSources` 下的源。
+
+必须：
+- 将 `USERNAME` 替换为您在 {% data variables.product.prodname_dotcom %} 上的用户帐户的名称。
+- 将 `TOKEN` 替换为您的个人访问令牌。
+- 将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称。{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+- 将 `HOSTNAME` 替换为 {% data variables.product.product_location %} 的主机名。{% endif %}
+
+{%if enterpriseServerVersions contains currentVersion %}如果您的实例启用了子域隔离：
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% if currentVersion == "free-pro-team@latest" %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% if enterpriseServerVersions contains currentVersion %}
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+```xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://github.com/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+{% endif %}
+
+### 发布包
+
+您可以通过使用 *nuget.config* 文件进行身份验证{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest"%}或使用包含 {% data variables.product.prodname_dotcom %} 个人访问令牌 (PAT) 的 `--api-key` 命令行选项，向 {% data variables.product.prodname_registry %} 发布包{% endif %}。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+#### 使用 GitHub PAT 作为 API 密钥发布包
+
+如果您还没有用于 {% data variables.product.prodname_dotcom %} 帐户的 PAT，请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+
+1. 创建一个新项目。
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. 打包项目。
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. 使用您的 PAT 作为 API 密钥发布包。
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key <em>YOUR_GITHUB_PAT</em> --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% endif %}
+
+#### 使用 *nuget.config* 文件发布包
+
+发布时，您需要将 *csproj* 文件中的 `OWNER` 值用于您的 *nuget.config* 身份验证文件。 在 *.csproj* 文件中指定或增加版本号，然后使用 `dotnet pack` 命令创建该版本的 *.nuspec* 文件。 有关创建包的更多信息，请参阅 Microsoft 文档中的“[创建和发布包](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)”。
+
+{% data reusables.package_registry.authenticate-step %}
+2. 创建一个新项目。
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. 将项目的特定信息添加到以 *.csproj* 结尾的项目文件中。  必须：
+    - 将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称。
+    - 将 `REPOSITORY` 替换为要发布的包所在仓库的名称。
+    - `1.0.0` 替换为包的版本号。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
+    - 将 `HOSTNAME` 替换为 {% data variables.product.product_location %} 的主机名。{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. 打包项目。
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. 使用您在 *nuget.config* 文件中指定的 `key` 发布包。
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### 将多个包发布到同一个仓库
+
+要将多个包发布到同一个仓库，您可以在所有 *.csproj* 项目文件的 `RepositoryURL` 字段中包含相同的 {% data variables.product.prodname_dotcom %} 仓库 URL。 {% data variables.product.prodname_dotcom %} 根据该字段匹配仓库。
+
+例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库：
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+### 安装包
+
+在项目中使用来自 {% data variables.product.prodname_dotcom %} 的包类似于使用来自 *nuget.org* 的包。 将包依赖项添加到 *.csproj* 文件以指定包名称和版本。 有关在项目中使用 *.csproj* 文件的更多信息，请参阅 Microsoft 文档中的“[使用 NuGet 包](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)”。
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. 要使用包，请添加 `ItemGroup` 并配置 *.csproj* 项目文件中的 `PackageReference` 字段，将 `OctokittenApp` 包替换为您的包依赖项，将 `1.0.0` 替换为您要使用的版本：
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. 使用 `restore` 命令安装包。
+  ```shell
+  dotnet restore
+  ```
+
+### 疑难解答
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+### 延伸阅读
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..f88212b2bb
--- /dev/null
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,151 @@
+---
+title: Working with the RubyGems registry
+intro: '您可以配置 RubyGems 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作带 Bundler 的 Ruby 项目中的依赖项。'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  free-pro-team: '*'
+  enterprise-server: '>=2.22'
+  github-ae: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。
+
+### 基本要求
+
+- 必须拥有 rubygems 2.4.1 或更高版本. 要查找您的 rubygems 版本：
+
+  ```shell
+  $ gem --version
+  ```
+
+  - 必须拥有 bundler 1.6.4 或更高版本. 要查找您的 Bundler 版本：
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+  - 安装 keycutter 以管理多个凭据. 要安装 keycutter：
+  ```shell
+  $ gem install keycutter
+  ```
+
+### 向 {% data variables.product.prodname_registry %} 验证
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+#### 使用个人访问令牌进行身份验证
+
+{% data reusables.package_registry.required-scopes %}
+
+通过编辑用于发布 gem 的 *~/.gem/credentials* 文件、编辑用于安装单个 gem 的 *~/.gemrc* 文件或使用用于跟踪和安装一个或多个 gem 的 Bundler，使用 RubyGems 向 {% data variables.product.prodname_registry %} 验证。
+
+要发布新的 gem，您需要通过编辑 *~/.gem/credentials* 文件以包含您的个人访问令牌，使用 RubyGems 向 {% data variables.product.prodname_registry %} 验证。  如果 *~/.gem/credentials* 文件不存在，请新建该文件。
+
+例如，您要创建或编辑 *~/.gem/credentials* 以包含以下内容，将 *TOKEN* 替换为您的个人访问令牌。
+
+```shell
+gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" }
+```
+
+要安装 gem，您需要通过编辑项目的 *~/.gemrc* 文件以包含 `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`，向 {% data variables.product.prodname_registry %} 验证。 必须：
+  - 将 `USERNAME` 替换为您的 {% data variables.product.prodname_dotcom %} 用户名。
+  - 将 `TOKEN` 替换为您的个人访问令牌。
+  - 将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称。{% if enterpriseServerVersions contains currentVersion %}
+  - `REGISTRY-URL` 替换为您实例的 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，都将 *HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。
+{% elsif currentVersion == "github-ae@latest" %}
+  - `REGISTRY-URL` 替换为您实例的 Rubygems 注册表的 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。
+{% endif %}
+
+如果您没有 *~/.gemrc* 文件，请使用此示例创建新的 *~/.gemrc* 文件。
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+要使用 Bundler 进行身份验证，请配置 Bundler 使用您的个人访问令牌，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *OWNER* 替换为拥有项目所在仓库的用户或组织帐户的名称。{% if enterpriseServerVersions contains currentVersion %}将 `REGISTRY-URL` 替换为实例 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif currentVersion == "github-ae@latest" %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。{% endif %}
+
+```shell
+$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER USERNAME:TOKEN</em>
+```
+
+### 发布包
+
+{% data reusables.package_registry.default-name %} 例如，您将 `octo-gem` 发布到 `octo-org` 组织时，{% data variables.product.prodname_registry %} 将 gem 发布到 `octo-org/octo-gem` 仓库。 有关创建 gem 的更多信息，请参阅 RubyGems 文档中的“[创建自己的 gem](http://guides.rubygems.org/make-your-own-gem/)”。
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. 从 *gemspec* 构建包以创建 *.gem* 包。
+  ```shell
+  gem build OCTO-GEM.gemspec
+  ```
+3. 将包发布到 {% data variables.product.prodname_registry %}，将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称，将 `OCTO-GEM` 替换为 gem 包的名称。{% if enterpriseServerVersions contains currentVersion %}将 `REGISTRY-URL` 替换为实例 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif currentVersion == "github-ae@latest" %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。{% endif %}
+
+  ```shell
+  $ gem push --key github \
+  --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/<em>OWNER</em> \
+  <em>OCTO-GEM-0.0.1</em>.gem
+  ```
+
+### 将多个包发布到同一个仓库
+
+要将多个 gem 发布到同一个仓库，您可以在 `gem.metadata` 的 `github_repo` 字段中包含 {% data variables.product.prodname_dotcom %} 仓库的 URL。 如果您包含此字段，则 {% data variables.product.prodname_dotcom %} 根据此值匹配仓库，而不使用 gem 名称。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名称。{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+### 安装包
+
+您可以使用来自 {% data variables.product.prodname_registry %} 的 gem，就像使用来自 *rubygems.org* 的 gem 一样。 You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. 对于 Bundler，请将您的 {% data variables.product.prodname_dotcom %} 用户或组织添加为 *Gemfile* 中的源，以便从这个新源获取 gem。 例如，您可以将新的 `source` 块添加到仅对您指定的包使用 {% data variables.product.prodname_registry %} 的 *Gemfile*，将 *GEM NAME* 替换为要从 {% data variables.product.prodname_registry %} 安装的包，将 *OWNER* 替换为拥有要安装的 gem 所在仓库的用户或组织。{% if enterpriseServerVersions contains currentVersion %}将 `REGISTRY-URL` 替换为实例 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif currentVersion == "github-ae@latest" %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. 对于 1.7.0 之前的 Bundler 版本，您需要增加新的全局 `source`。 有关使用 Bundler 的更多信息，请参阅 [bundler.io 文档](http://bundler.io/v1.5/gemfile.html)。
+
+  ```ruby
+  source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. 安装包：
+  ```shell
+  $ gem install octo-gem --version "0.1.1"
+  ```
+
+### 延伸阅读
+
+- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
index eb73fc46a0..b73c5ed79f 100644
--- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
+++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
@@ -24,9 +24,9 @@ topics:
 | 自定义子域     | `blog.example.com` |
 | Apex 域    | `example.com`      |
 
-You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)."
+您可以为您的网站设置 apex 和 `www` 子域配置。 有关 apex 域的更多信息，请参阅“[对您的 {% data variables.product.prodname_pages %} 网站使用 apex 域](#using-an-apex-domain-for-your-github-pages-site)”。
 
-建议始终使用 `www` 子域名，即使您也同时使用 apex 域。 When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
+建议始终使用 `www` 子域名，即使您也同时使用 apex 域。 当您创建具有 apex 域的新站点时，我们会自动尝试保护 `www` 子域以供在提供网站内容时使用。 如果您配置 `www` 子域，我们会自动尝试保护相关的 apex 域。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
 
 在配置用户或组织网站的自定义域后，自定义域名将替换未配置自定义域的帐户所拥有的任何项目网站 URL 的 `<user>.github.io` 或 `<organization>.github.io` 部分。 例如，如果您的用户网站的自定义域名为 `www.octocat.com`，并且您拥有一个未自定义域名的项目网站，该网站从名为 `octo-project` 的仓库发布，则该仓库的 {% data variables.product.prodname_pages %} 网站将在 `www.octocat.com/octo-project` 上提供。
 
@@ -44,7 +44,7 @@ You can set up either or both of apex and `www` subdomain configurations for you
 
 #### 自定义子域
 
-A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. 自定义子域主要在您需要将网站分为两个不同的部分时使用。 例如，您可以创建一个名为 `blog.example.com` 并自定义该部分与 `www.example.com` 分开。
+自定义子域是一种不使用标准 `www` 变体的子域。 自定义子域主要在您需要将网站分为两个不同的部分时使用。 例如，您可以创建一个名为 `blog.example.com` 并自定义该部分与 `www.example.com` 分开。
 
 ### 对您的 {% data variables.product.prodname_pages %} 网站使用 apex 域
 
diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index a9effa7ddf..617f53a62b 100644
--- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -46,7 +46,7 @@ topics:
 4. 在 "Custom domain（自定义域）"下，输入自定义域，然后单击 **Save（保存）**。 这将创建一个在发布源根目录中添加 _CNAME _ 文件的提交。 ![保存自定义域按钮](/assets/images/help/pages/save-custom-subdomain.png)
 5. 导航到您的 DNS 提供程序并创建 `CNAME` 记录，使子域指向您站点的默认域。 例如，如果要对您的用户站点使用子域 `www.example.com`，您可以创建 `CNAME` 记录，使 `www.example.com` 指向 `<user>.github.io`。 如果要对您的组织站点使用子域 `www.anotherexample.com`，您可以创建 `CNAME` 记录，使 `www.anotherexample.com` 指向 `<organization>.github.io`。 `CNAME` 记录应该始终指向 `<user>.github.io` 或 `<organization>.github.io`，不包括仓库名称。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _WWW.EXAM.COM_ 替换为您的子域。
 ```shell
@@ -79,7 +79,7 @@ topics:
       185.199.111.153
       ```
 
-{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 6. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _EXAM.COM_ 替换为您的 apex 域。 确认结果与上面 {% data variables.product.prodname_pages %} 的 IP 地址相匹配。
   ```shell
@@ -92,16 +92,16 @@ topics:
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
 
-### Configuring an apex domain and the `www` subdomain variant
+### 配置 apex 域和 `www` 子域变种
 
-When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant.
+使用 apex 域时，我们建议配置您的 {% data variables.product.prodname_pages %} 站点，以便在 apex 域和该域的 `www` 子域变体中托管内容。
 
-To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
+要与 apex 域一起设置 `www` 子域，您必须先配置 apex 域，这将通过您的 DNS 提供商创建 `ALIAS`、`ANAME` 或 `A` 记录。 更多信息请参阅“[配置 apex 域](#configuring-an-apex-domain)”。
 
-After you configure the apex domain, you must to configure a CNAME record with your DNS provider.
+配置 apex 域后，您必须通过 DNS 提供商配置 CNAME 记录。
 
-1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
-2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
+1. 导航到您的 DNS 提供商，并创建一个 `CNAME` 记录，指向您网站的默认域名 `www.example.com` ：`<user>.github.io` 或 `<organization>.github.io`。 不要包括仓库名称。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
+2. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _WWW.EXAM.COM_ 替换为您的 `www` 子域变体。
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -109,12 +109,12 @@ After you configure the apex domain, you must to configure a CNAME record with y
     > <em>YOUR-USERNAME</em>.github.io.      43192   IN      CNAME   <em> GITHUB-PAGES-SERVER </em>.
     > <em> GITHUB-PAGES-SERVER </em>.         22      IN      A       192.0.2.1
 ```
-### Removing a custom domain
+### 删除自定义域
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-4. Under "Custom domain," click **Remove**. ![保存自定义域按钮](/assets/images/help/pages/remove-custom-domain.png)
+4. 在“Custom domain（自定义域）”下，单击 **Remove（删除）**。 ![保存自定义域按钮](/assets/images/help/pages/remove-custom-domain.png)
 
 ### 延伸阅读
 
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
index fee13c6083..359e96d7e4 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -19,7 +19,7 @@ topics:
 
 ### 选择发布源
 
-Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} For example, before you can publish your project site from the `/docs` folder on the `master` branch of your repository, you or a collaborator must create a `/docs` folder on the default `master` branch of your repository.{% endif %}
+在配置发布源之前，请确保要用作发布源的分支{% if currentVersion ver_lt "enterprise-server@3.0" %} 或文件夹{% endif %} 已存在于您的仓库中。{% if currentVersion ver_lt "enterprise-server@3.0" %} 例如，从仓库的 `master` 分支上的 `/docs` 文件夹中发布项目站点之前，您或协作者必须在仓库的默认 `master` 分支上创建 `/docs` 文件夹。{% endif %}
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index 64915cbecb..32c4a4c0a9 100644
--- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -87,7 +87,12 @@ topics:
 10. 保存并关闭 Gemfile。
 11. 从命令行运行 `bundle update`。
 11. （可选）在本地测试您的站点。 更多信息请参阅“[使用 Jekyll 在本地测试 {% data variables.product.prodname_pages %} 站点](/articles/testing-your-github-pages-site-locally-with-jekyll)”。
-12. 将您的 {% data variables.product.product_name %} 仓库添加为远程仓库，将 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ 替换为您企业的主机名，将 {% endif %} _USER_ 替换为拥有该仓库的帐户{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}，{% endif %}并将 _REPOSITORY_ 替换为仓库名称。
+12. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+14. 将您的 {% data variables.product.product_name %} 仓库添加为远程仓库，将 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ 替换为您企业的主机名，将 {% endif %} _USER_ 替换为拥有该仓库的帐户{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}，{% endif %}并将 _REPOSITORY_ 替换为仓库名称。
 ```shell
 {% if currentVersion == "free-pro-team@latest" %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md
index c6ee45a94a..8a777ae877 100644
--- a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md
@@ -53,7 +53,7 @@ $ curl https://api.github.com/users/defunkt
 ```shell
 $ curl -i https://api.github.com/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > Server: GitHub.com
 > Date: Sun, 11 Nov 2012 18:43:28 GMT
 > Content-Type: application/json; charset=utf-8
@@ -216,7 +216,7 @@ $ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest
     {% data variables.product.api_url_pre %}/user/repos
 ```
 
-在这个最小的示例中，我们为博客（也许要在 [GitHub Pages][pages] 上提供）创建了一个新的私有仓库。 虽然博客 {% if currentversion != "github-ae@latest" %}将是公开的{% else %}可供所有企业成员访问{% endif %}，但我们已经将仓库设置为私有。 在这一步中，我们还将使用自述文件和 [nanoc][nanoc] 风格的 [.gitignore 模板][gitignore templates]对其进行初始化。
+在这个最小的示例中，我们为博客（也许要在 [GitHub Pages][pages] 上提供）创建了一个新的私有仓库。 虽然博客 {% if currentVersion != "github-ae@latest" %}将是公开的{% else %}可供所有企业成员访问{% endif %}，但我们已经将仓库设置为私有。 在这一步中，我们还将使用自述文件和 [nanoc][nanoc] 风格的 [.gitignore 模板][gitignore templates]对其进行初始化。
 
 生成的仓库可在 `https://github.com/<your_username>/blog` 上找到。 要在您拥有的组织下创建仓库，只需将 API 方法从 `/user/repos` 更改为 `/orgs/<org_name>/repos`。
 
@@ -225,7 +225,7 @@ $ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 
-> HTTP/1.1 404 Not Found
+> HTTP/2 404
 
 > {
 >    "message": "Not Found"
@@ -266,7 +266,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 
 > ...
 > Link: &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2&gt;; rel="next", &lt;{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30&gt;; rel="last"
@@ -290,7 +290,7 @@ $         "labels": ["design"] \
 $       }' \
 $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 
-> HTTP/1.1 201 Created
+> HTTP/2 201
 > Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17
 > X-RateLimit-Limit: 5000
 
@@ -340,7 +340,7 @@ JSON 响应的 `Location` 响应标头和 `url` 字段为我们提供了一些
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6"
 ```
 
@@ -350,7 +350,7 @@ $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 $ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \
 $    {% data variables.product.api_url_pre %}/users/defunkt
 
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 ```
 
 `304` 状态表示该资源自上次请求以来没有发生改变，该响应将不包含任何正文。 另外，`304` 响应不计入您的[速率限制][rate-limiting]。
diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md
index 22f213d6fd..15cf24889c 100644
--- a/translations/zh-CN/content/rest/overview/libraries.md
+++ b/translations/zh-CN/content/rest/overview/libraries.md
@@ -19,7 +19,7 @@ topics:
   <div class="octokit-links"><br/>
      <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
-     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/rest.js">octokit/rest.js</a></div><br/>
+     <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
diff --git a/translations/zh-CN/content/rest/overview/media-types.md b/translations/zh-CN/content/rest/overview/media-types.md
index d2536e7e34..ca2cf19885 100644
--- a/translations/zh-CN/content/rest/overview/media-types.md
+++ b/translations/zh-CN/content/rest/overview/media-types.md
@@ -43,17 +43,17 @@ API 支持的最基本媒体类型是：
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 
 $ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \
 $  -H "Accept: application/vnd.github.v3.full+json"
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-GitHub-Media-Type: github.v3; param=full; format=json
 ```
 
diff --git a/translations/zh-CN/content/rest/reference/activity.md b/translations/zh-CN/content/rest/reference/activity.md
index 0da3f2eb07..58d1cae6e0 100644
--- a/translations/zh-CN/content/rest/reference/activity.md
+++ b/translations/zh-CN/content/rest/reference/activity.md
@@ -24,14 +24,14 @@ topics:
 
 ``` shell
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events
-> HTTP/1.1 200 OK
+> HTTP/2 200
 > X-Poll-Interval: 60
 > ETag: "a18c3bded88eb5dbb5c849a489412bf3"
 
 # The quotes around the ETag value are important
 $ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
 $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
@@ -56,7 +56,7 @@ $    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
 #### 响应
 
 ```shell
-HTTP/1.1 200 OK
+HTTP/2 200
 ```
 
 ```xml
@@ -122,14 +122,14 @@ HTTP/1.1 200 OK
 ``` shell
 # Add authentication to your requests
 $ curl -I {% data variables.product.api_url_pre %}/notifications
-HTTP/1.1 200 OK
+HTTP/2 200
 Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
 X-Poll-Interval: 60
 
 # Pass the Last-Modified header exactly
 $ curl -I {% data variables.product.api_url_pre %}/notifications
 $    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
-> HTTP/1.1 304 Not Modified
+> HTTP/2 304
 > X-Poll-Interval: 60
 ```
 
diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md
index d60e7dca4f..3eb1c82d00 100644
--- a/translations/zh-CN/content/rest/reference/enterprise-admin.md
+++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md
@@ -151,19 +151,6 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id}
 {% endfor %}
 
 {% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
-
-## 休息时加密
-
-您可以使用休息时加密 API 来管理用于对 {% data variables.product.product_name %} 上的数据进行加密的密钥。 更多信息请参阅“[为企业配置数据加密](/admin/configuration/configuring-data-encryption-for-your-enterprise)”。
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## 管理统计
 
@@ -388,7 +375,7 @@ $ curl -L 'https://api_key:<em>your-amazing-password</em>@<em>hostname</em>:<em>
 {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}
 ## 用户
 
-用户管理 API 允许您暂停{% if enterpriseServerVersions contains currentVersion %}、取消暂停、升级和降级{% endif %}{% if currentversion == "github-ae@latest" %} 以及取消暂停{% endif %} 企业上的用户。 *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `403` 响应。
+The User Administration API allows you to suspend{% if enterpriseServerVersions contains currentVersion %}, unsuspend, promote, and demote{% endif %}{% if currentVersion == "github-ae@latest" %} and unsuspend{% endif %} users on your enterprise. *它只适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)站点管理员。*普通用户尝试访问它时会收到 `403` 响应。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
diff --git a/translations/zh-CN/content/rest/reference/git.md b/translations/zh-CN/content/rest/reference/git.md
index acea517880..bd8358707e 100644
--- a/translations/zh-CN/content/rest/reference/git.md
+++ b/translations/zh-CN/content/rest/reference/git.md
@@ -19,7 +19,7 @@ Git 数据库 API 使您能够在 {% data variables.product.product_name %} 上
 
 ## Blob
 
-Git Blob（二进制大对象）是用于将每个文件的内容存储在仓库中的对象类型。 文件的 SHA-1 哈希在 Blob 对象中计算和存储。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入 [blob 对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)。 Blob 使用[这些自定义媒体类型](#custom-media-types)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
+Git Blob（二进制大对象）是用于将每个文件的内容存储在仓库中的对象类型。 文件的 SHA-1 哈希在 Blob 对象中计算和存储。 这些端点允许您在 {% data variables.product.product_name %} 上的 Git 数据库中读取和写入 [blob 对象](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects)。 Blob 使用[这些自定义媒体类型](#custom-media-types-for-blobs)。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
 
 ### Blob 的自定义媒体类型
 
diff --git a/translations/zh-CN/content/rest/reference/markdown.md b/translations/zh-CN/content/rest/reference/markdown.md
index e978876791..1d5c33f371 100644
--- a/translations/zh-CN/content/rest/reference/markdown.md
+++ b/translations/zh-CN/content/rest/reference/markdown.md
@@ -7,7 +7,7 @@ versions:
   enterprise-server: '*'
   github-ae: '*'
 topics:
-  - api
+  - API
 ---
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/zh-CN/content/rest/reference/migrations.md b/translations/zh-CN/content/rest/reference/migrations.md
index be2c989047..1711dee1fc 100644
--- a/translations/zh-CN/content/rest/reference/migrations.md
+++ b/translations/zh-CN/content/rest/reference/migrations.md
@@ -16,7 +16,7 @@ topics:
 
 ## 组织
 
-迁移 API 仅适用于经过身份验证的组织所有者。 For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)."
+迁移 API 仅适用于经过身份验证的组织所有者。 更多信息请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)”和“[其他身份验证方法](/rest/overview/other-authentication-methods)”。
 
 {% data variables.migrations.organization_migrations_intro %}
 
diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
index 1b6b7af027..62db6a8f8b 100644
--- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
+++ b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md
@@ -120,6 +120,9 @@ _搜索_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
+{% endif %}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
@@ -160,6 +163,9 @@ _搜索_
 {% if currentVersion == "free-pro-team@latest" %}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif %}
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
 {% if currentVersion == "free-pro-team@latest" %}
@@ -678,6 +684,9 @@ _团队_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/repos#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/repos#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/repos#get-latest-pages-build) (:read)
+{% if currentVersion == "free-pro-team@latest" %}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+{% endif %}
 
 ### 有关“拉取请求”的权限
 
@@ -767,6 +776,10 @@ _审查_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (:read)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (:write)
 
+### Permission on "profile"
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
+
 ### 有关“仓库挂钩”的权限
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md
index 6276be0804..824dc229d9 100644
--- a/translations/zh-CN/content/rest/reference/repos.md
+++ b/translations/zh-CN/content/rest/reference/repos.md
@@ -155,7 +155,8 @@ topics:
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
 ## 环境
 
-环境 API 允许您创建、配置和删除环境。 有关环境的更多信息，请参阅“[环境](/actions/reference/environments)”。
+环境 API 允许您创建、配置和删除环境。 有关环境的更多信息，请参阅“[环境](/actions/reference/environments)”。 To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
diff --git a/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..2e38526ac1
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,50 @@
+---
+title: 关于 GitHub 赞助商
+intro: '{% data variables.product.prodname_sponsors %} 允许开发者社区直接在 {% data variables.product.product_name %} 上为他们设计、构建和维护所需开源项目的人员及组织提供经济支持。'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### 关于 {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %}更多信息请参阅“[关于开源贡献者的 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)”和“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”。
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} 更多信息请参阅“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。
+
+当您成为受赞助的开发者或组织时，{% data variables.product.prodname_sponsors %} 的附加条款适用。 更多信息请参阅“[GitHub Sponsors 附加条款](/github/site-policy/github-sponsors-additional-terms)”。
+
+### 关于 {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**注：**{% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+{% data variables.product.prodname_matching_fund %} 旨在使 {% data variables.product.prodname_dotcom %} 社区开发开源软件的成员获益，宣传 [{% data variables.product.prodname_dotcom %} 社区指导方针](/github/site-policy/github-community-guidelines)。 对被赞助组织的付款和来自组织的付款均不符合 {% data variables.product.prodname_matching_fund %} 资格。
+
+若要符合 {% data variables.product.prodname_matching_fund %} 的资格，您必须创建吸引社区长期维持您发展的个人资料。 有关创建有吸引力的个人资料的更多信息，请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)”。
+
+被赞助开发者之间的捐赠将不匹配。
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+### 共享关于 {% data variables.product.prodname_sponsors %} 的反馈
+
+{% data reusables.sponsors.feedback %}
+
+### 延伸阅读
+- "[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors)"
+- "[通过 {% data variables.product.prodname_sponsors %} 接受赞助](/sponsors/receiving-sponsorships-through-github-sponsors)"
+- {% data variables.product.prodname_blog %} 上的“[{% data variables.product.prodname_sponsors %} 团队常见问题](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)”
diff --git a/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..4fe7ac1481
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,10 @@
+---
+title: GitHub Sponsors 使用入门
+intro: '了解 {% data variables.product.prodname_sponsors %} 以及您如何作为赞助者或开源贡献者参与其中。'
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors %}
+
+{% link_with_intro /quickstart-for-finding-contributors-to-sponsor %}
diff --git a/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..fe4ebe8330
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,51 @@
+---
+title: 查找要赞助的贡献者快速入门
+intro: 了解一些查找要赞助的开源贡献者的最佳实践。
+versions:
+  free-pro-team: '*'
+type: quick_start
+topics:
+  - Open Source
+---
+
+### 探索您依赖的项目
+
+当您考虑在哪里查找要赞助的开源贡献者时，请考虑从 https://github.com/sponsors/community 开始。
+
+如果您已登录，赞助者结果将从仓库所依赖的公共依赖项开始。
+
+![Babel 开源项目使用的高亮文本表示"您有 4 个仓库依赖于此项目"](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+您还可以切换查看哪个帐户的结果，并进一步过滤或搜索。
+
+![赞助者社区搜索页面上的搜索选项](/assets/images/help/sponsors/sponsors-search-options.png)
+
+### 了解其他人赞助谁
+
+您可以在其 {% data variables.product.prodname_dotcom %} 个人资料页面上查看用户或组织赞助者。
+
+### 考虑您如何从不同的贡献中获益
+
+考虑您是否受益于开源贡献的工作，例如：
+ - 文档
+ - 设计
+ - 翻译
+ - 时事通讯
+ - 代码审查
+ - 教程
+ - 指导
+ - 对议题分类和帮助项目管理
+ - 回答问题
+ - 活动策划
+
+有关不同类型开源贡献的更多信息，请参阅[开源指南](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code)。
+
+您可以在 https://github.com/sponsors/community 上搜索来检查您从 {% data variables.product.prodname_sponsors %} 个人资料中获益的贡献者。
+
+### 搜索特定项目或贡献者
+
+在 https://github.com/sponsors/community 上，您可以按生态系统、最常用、最近更新等搜索。 您可以筛选个人用户帐户或您是其成员的组织的搜索结果。
+
+### 后续步骤
+
+有关开始赞助的更多信息，请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”。
diff --git a/translations/zh-CN/content/sponsors/guides.md b/translations/zh-CN/content/sponsors/guides.md
new file mode 100644
index 0000000000..79a072acce
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/guides.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Sponsors 指南
+shortTitle: 指南
+intro: '学习如何充分利用 {% data variables.product.prodname_sponsors %}。'
+allowTitleToDifferFromFilename: true
+layout: product-sublanding
+versions:
+  free-pro-team: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+---
+
diff --git a/translations/zh-CN/content/sponsors/index.md b/translations/zh-CN/content/sponsors/index.md
new file mode 100644
index 0000000000..5f8395f8b2
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/index.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Sponsors 文档
+shortTitle: GitHub 赞助者
+intro: '投资于您依赖的开源项目，支持数字基础设施，并通过赞助开放源码贡献者及其项目实现开放源码事业。 创建 {% data variables.product.prodname_sponsors %} 个人资料并为您的开源工作获得补偿。'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: sponsors
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  free-pro-team: '*'
+---
+
+<!--{% link_with_intro /getting-started-with-github-sponsors %}-->
+<!--{% link_with_intro /sponsoring-open-source-contributors %}-->
+<!--{% link_with_intro /receiving-sponsorships-through-github-sponsors%}-->
+<!--{% link_with_intro /integrating-with-github-sponsors %}-->
diff --git a/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..123dc7ce9d
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,29 @@
+---
+title: 为赞助帐户中的事件配置 web 挂钩
+intro: 您可以配置 web 挂钩以在您获得新的赞助或现有赞助者更改其赞助时收到提醒。
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+---
+
+### 关于被赞助帐户中事件的 web 挂钩
+
+要监视赞助变更，例如在付款期结束时取消，您可以为被赞助的用户或组织帐户创建 web 挂钩。 为被赞助帐户创建 web 挂钩后，在创建、编辑或删除赞助时您将会收到更新消息。 更多信息请参阅 [`sponsorship` web 挂钩事件](/webhooks/event-payloads/#sponsorship)。
+
+### 管理被赞助帐户中事件的 web 挂钩
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-webhooks-tab %}
+{% data reusables.sponsors.add-webhook %}
+{% data reusables.sponsors.add-payload-url %}
+{% data reusables.sponsors.webhook-content-formatting %}
+{% data reusables.sponsors.webhook-secret-token %}
+{% data reusables.sponsors.add-active-triggers %}
+{% data reusables.sponsors.confirm-add-webhook %}
+{% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..6f4613dbc0
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,14 @@
+---
+title: Sponsors GraphQL API 使用入门
+intro: 使用 GraphQL API，您可以构建自定义集成来管理或审查您的赞助。
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+---
+
+要开始使用 GraphQL API，请参阅 [GraphQL 简介](/graphql/guides/introduction-to-graphql)。
+
+您可以在参考文档中查找关于 Sponsors GraphQL API 的详细信息。 更多信息请参阅“[GraphQL 参考](/graphql/reference)”。 我们建议使用 GraphQL 浏览器来构建您的 GraphQL 调用。 更多信息请参阅“[使用浏览器](/graphql/guides/using-the-explorer)”。
diff --git a/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/index.md b/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..9fd169da61
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,9 @@
+---
+title: 与 GitHub Sponsors 集成
+intro: 作为开源贡献者，您可以建立自定义工具来管理您的 GitHub 赞助。
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /configuring-webhooks-for-events-in-your-sponsored-account %}
+{% link_with_intro /getting-started-with-the-sponsors-graphql-api %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..e2e2be7645
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,46 @@
+---
+title: 关于开源贡献者的 GitHub Sponsors
+intro: 如果您为开源项目提供价值，可以成为被赞助的贡献者，您的工作将获得付款。
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+---
+
+### 加入 {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} 更多信息请参阅“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”。
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} 更多信息请参阅“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。
+
+加入 {% data variables.product.prodname_sponsors %} 之后，您可以为您参与的开源项目添加赞助按钮，以提高您的 {% data variables.product.prodname_sponsors %} 个人资料及其他资助平台的可见性。 更多信息请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”。
+
+您可以为赞助设定目标。 更多信息请参阅“[管理您的赞助目标](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal)”。
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+### 赞助级别
+
+{% data reusables.sponsors.tier-details %} 更多信息请参阅“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”、“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”和“[管理赞助级别](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)”。
+
+最好设置一系列不同的赞助选项，包括每月和一次性等级，使任何人都能轻松地支持您的工作。 特别是，一次性付款使人们能够在不担心他们的财务是否会支持定期付款时间表的情况下奖励您的努力。
+
+### 赞助付款
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+更多信息请参阅“[从 {% data variables.product.prodname_sponsors %} 管理您的付款](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors)”。
+
+### 共享关于 {% data variables.product.prodname_sponsors %} 的反馈
+
+{% data reusables.sponsors.feedback %}
+
+### 延伸阅读
+- {% data variables.product.prodname_blog %} 上的“[{% data variables.product.prodname_sponsors %} 团队常见问题](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)”
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..c7a77f1a86
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,28 @@
+---
+title: 联系赞助者
+intro: 您可以向选择接收有关您工作更新的赞助者发送电子邮件。
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+---
+
+### 关于赞助升级
+
+您的赞助者可选择是否接收有关您工作更新的电子邮件。 更多信息请参阅“[管理您的赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”。
+
+对于被赞助开发者帐户，更新将来自您用户帐户的主电子邮件地址。 如果您对用户帐户启用了电子邮件地址保密，则更新邮件将从 `noreply@github.com` 发出。 对于被赞助的组织，更新将来自组织的 `noreply@github.com` 电子邮件地址。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。
+
+### 联系赞助者
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.sponsors-updates-tab %}
+{% data reusables.sponsors.draft-new-update %}
+{% data reusables.sponsors.send-update-to-sponsors %}
+{% data reusables.sponsors.write-sponsor-update %}
+{% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..ecb55d1eba
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,24 @@
+---
+title: Disabling your GitHub Sponsors account
+intro: 'If you no longer want to participate in {% data variables.product.prodname_sponsors %}, you can disable your {% data variables.product.prodname_sponsors %} account.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you are receiving sponsorship payments, you'll need to contact GitHub Support to disable your {% data variables.product.prodname_sponsors %} account.
+
+If you don't have any sponsors, then you can disable your {% data variables.product.prodname_sponsors %} account on GitHub.
+
+If you decide to create a {% data variables.product.prodname_sponsors %} account again, you'll need to reapply.
+
+Alternatively, you can unpublish your sponsors profile and then republish the account without reapplying again. For more information, see "[Unpublishing your {% data variables.product.prodname_sponsors %} profile](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile)."
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+1. Under "Disable GitHub Sponsors account", click **Disable account**.  
+   !["Disable your account" button](/assets/images/help/sponsors/disable-your-account-button.png)
+2. To confirm, click **Disable GitHub Sponsors account**. !["Disable GitHub Sponsors account" button](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..223cb0ccdc
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,31 @@
+---
+title: 编辑您用于 GitHub Sponsors 的个人资料详细信息
+intro: 您可以更新潜在赞助者看到的有关您工作的信息。
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+---
+
+### 关于赞助者个人资料
+
+您的 {% data variables.product.prodname_sponsors %} 个人资料会告诉潜在的赞助者，他们为什么应该支持您。 用户单击您个人资料上的 **Sponsor（赞助）** 按钮，就会看到您的赞助个人资料。 我们建议个人资料中包括以下信息。
+
+- 您参与的开源工作
+- 您为什么致力于开源开发
+
+### 编辑您的个人资料详细信息
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..8e4901dc7e
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,24 @@
+---
+title: 通过 GitHub Sponsors 接受赞助
+shortTitle: 接受赞助
+intro: 您或您的组织可以成为被赞助的开源贡献者，从而接受对您工作的付款、更新您的赞助详细信息以及查看和联系您的赞助者。
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /about-github-sponsors-for-open-source-contributors %}
+{% link_with_intro /setting-up-github-sponsors-for-your-user-account %}
+{% link_with_intro /setting-up-github-sponsors-for-your-organization %}
+{% link_with_intro /editing-your-profile-details-for-github-sponsors %}
+{% link_with_intro /managing-your-sponsorship-goal %}
+{% link_with_intro /managing-your-sponsorship-tiers %}
+{% link_with_intro /viewing-your-sponsors-and-sponsorships %}
+{% link_with_intro /managing-your-payouts-from-github-sponsors %}
+{% link_with_intro /contacting-your-sponsors %}
+{% link_with_intro /tax-information-for-github-sponsors %}
+{% link_with_intro /disabling-your-github-sponsors-account %}
+{% link_with_intro /unpublishing-your-github-sponsors-profile %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..94bf71bc7a
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: 从 GitHub Sponsors 管理您的付款
+intro: '您可以从 {% data variables.product.prodname_sponsors %} 查看有关过去和未来付款的信息，并且编辑您的银行信息。'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+---
+
+### 关于 {% data variables.product.prodname_sponsors %} 中的付款
+
+如果是通过 Stripe Connect 付款，只能从 {% data variables.product.prodname_sponsors %} 管理您的支出。 如果是赞助用户帐户通过 ACH 转账或电汇付款，则在赞助的开源贡献者仪表板上看不到 **Payouts（付款）**选项卡。 赞助的组织只能使用 Stripe Connect 进行付款。 更多信息请参阅“[关于开源贡献者的 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)”。
+
+{% data reusables.sponsors.payout-info %}
+
+### 查看和编辑付款信息
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-payouts-tab %}
+{% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..3fdc6223da
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,46 @@
+---
+title: 管理您的赞助目标
+intro: 您可以为被赞助开发者或被赞助组织帐户设置目标，以帮助社区了解赞助您的影响。
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### 关于赞助目标
+
+您可以为被赞助帐户设置一个融资目标，并与您的社区共享该目标。 目标可帮助您了解您在开源社区中的影响，并扩大您在 {% data variables.product.prodname_sponsors %} 计划中的影响力。
+
+您的目标可设为您想要的赞助者数量或您希望每月赚取的金额。 每次只能设置一个目标。 一个目标达成后，可以设置另一个目标。
+
+### 设置目标
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.set-a-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### 编辑目标
+
+编辑目标时，无法选择已实现的目标。 例如，如果您已经有 5 个赞助者，您无法将目标编辑为针对 4 个赞助者。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.select-goal-type %}
+{% data reusables.sponsors.publish-goal %}
+
+### 取消目标
+
+取消的目标无法重新激活， 而必须创建新目标。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-your-goals-tab %}
+{% data reusables.sponsors.edit-goal %}
+{% data reusables.sponsors.retire-goal %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..0537a2a687
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,48 @@
+---
+title: 管理赞助等级
+intro: 您可以添加新的赞助等级，也可以编辑或撤销现有等级。
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+---
+
+### 关于赞助等级
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+### 添加等级
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+### 编辑或撤销等级
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+### 启用具有自定义金额的等级
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.enable-custom-amounts %}
+
+### 禁用具有自定义金额的等级
+
+您可以通过在 **Sponsor tiers（赞助者等级）**选项卡中取消选择 **Enable custom amounts（启用自定义金额）**选项来禁用具有自定义金额的等级。 如果您禁用自定义金额，所有自定义等级都将退出。
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..7009028e47
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,91 @@
+---
+title: 为您的组织设置 GitHub Sponsors
+intro: '您的组织可以加入 {% data variables.product.prodname_sponsors %} 以接受对您工作的付款。'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+---
+
+### 加入 {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+收到邀请您的组织加入 {% data variables.product.prodname_sponsors %} 的邀请后，您可以完成以下步骤以成为被赞助的组织。
+
+要作为组织外部的个人贡献者加入 {% data variables.product.prodname_sponsors %}，请参阅“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”。
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. 在组织的右侧，单击 **Join the waitlist（加入等待列表）**。
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+### 填写被赞助组织资料
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### 创建赞助等级
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### 提交您的银行信息
+
+作为被赞助组织，您必须在受支持的区域接收支付到组织专用银行帐户的赞助款。 您可以通过如 [Open Collective](https://opencollective.com/) 和 [Stripe Atlas](https://stripe.com/atlas) 之类的服务获得企业银行帐户。 您的组织合法经营的区域与您银行帐户所在的区域必须匹配。 为组织设置 {% data variables.product.prodname_sponsors %} 的人员也必须居住在同一受支持的区域。 {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+有关使用 Open Collective 设置 Stripe Connect 的更多信息，请参阅 Open Collective 文档中的[设置 {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors)。
+
+### 提交您的税务信息
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### 在您的 {% data variables.product.prodname_dotcom %} 帐户上启用双重身份验证 (2FA)。
+
+在您的组织成为被赞助的组织之前，您必须在 {% data variables.product.product_name %} 帐户上启用 2FA。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
+
+### 向 {% data variables.product.prodname_dotcom %} 提交申请以请求批准
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+### 延伸阅读
+- "[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[通过 {% data variables.product.prodname_sponsors %} 接受赞助](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
new file mode 100644
index 0000000000..1b56726104
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
@@ -0,0 +1,84 @@
+---
+title: 为您的用户帐户设置 GitHub Sponsors
+intro: '要成为被赞助的开发者，请加入 {% data variables.product.prodname_sponsors %}、填写被赞助开发者个人资料、创建赞助等级、提交您的银行和税务信息并在您的 {% data variables.product.prodname_dotcom %} 帐户上启用双重身份验证。'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+---
+
+### 加入 {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+要作为组织加入 {% data variables.product.prodname_sponsors %}，请参阅“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. 如果您是组织所有者，则有多个符合条件的帐户。 单击 **View your eligible accounts（查看符合条件的帐户）**，然后在帐户列表中找到您的用户帐户。
+3. 单击 **Join the waitlist（加入等待列表）**。
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.accept-legal-terms %}
+
+如果您在受支持的区域有银行帐户， {% data variables.product.prodname_dotcom %} 将在两周内审核您的申请。
+
+### 填写被赞助开发者个人资料
+
+在 {% data variables.product.prodname_dotcom %} 审核您的申请后，您可以设置您的被赞助开发者个人资料，以便人们可以开始赞助您。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+### 创建赞助等级
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+### 提交您的银行信息
+
+如果您居住在受支持的区域，可以按照这些说明创建 Stripe Connect 帐户来提交银行信息。 您居住的区域与您的银行帐户所在区域必须匹配。 {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+### 提交您的税务信息
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+{% data reusables.sponsors.country-of-residence %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+### 在您的 {% data variables.product.prodname_dotcom %} 帐户上启用双重身份验证 (2FA)。
+
+在成为被赞助的开发者之前，您必须在 {% data variables.product.product_name %} 帐户上启用 2FA。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
+
+### 向 {% data variables.product.prodname_dotcom %} 提交申请以请求批准
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. 单击 **Request approval（请求批准）**。 ![请求批准按钮](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..8d6133fd1b
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,25 @@
+---
+title: GitHub Sponsors 的税务信息
+intro: '被赞助的开发者和组织必须向 {% data variables.product.prodname_dotcom %} 提交税务信息，并负责计算和支付自己的税款。'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  free-pro-team: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+如果您是美国的纳税人，则必须提交 W-9，然后才能收到付款。 如果您是美国以外任何其他地区的纳税人，则必须提交 W-8BEN，然后才能收到付款。 更多信息请参阅“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)”和“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)”。 {% data variables.product.prodname_dotcom %} 将向您发送适当的表格，在到期时通知您，并给您合理的时间填写和发送表格。
+
+如果您是美国的纳税人并且在一个纳税年度内的收入超过 600 美元，{% data variables.product.prodname_dotcom %} 将在下一个日历年的 1 月 31 日之前向您发送 1099。 我们不为国际纳税人提供税表。
+
+{% data variables.product.prodname_dotcom %} 不会从 {% data variables.product.prodname_sponsors %} 付款中代扣税款。 被赞助的开发者须负责计算和支付自己的税款。
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+### 延伸阅读
+
+- [查看您的赞助者和赞助](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..7112b5b16d
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,21 @@
+---
+title: Unpublishing your GitHub Sponsors profile
+intro: 'If you don''t have any sponsors, you can unpublish your {% data variables.product.prodname_sponsors %} profile.'
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+If you have sponsors, you'll need to contact GitHub Support to help you unpublish your {% data variables.product.prodname_sponsors %} account.
+
+After your {% data variables.product.prodname_sponsors %} account is unpublished:
+- You'll no longer receive sponsorship payments.
+- You can request to re-publish your profile.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.settings-tab %}
+3. Under "Unpublish your GitHub Sponsors profile", click **Unpublish profile**. !["Unpublish profile" button](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. To confirm, click "Unpublish GitHub Sponsors account". !["Unpublish GitHub Sponsors profile" button](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..20b759a7e2
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,36 @@
+---
+title: 查看您的赞助者和赞助
+intro: 您可以查看和导出有关您的赞助者和赞助的详细信息与分析。
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+---
+
+### 关于赞助者和赞助
+
+您可以查看有关您当前和过去的赞助、从赞助者收到的付款以及事件（例如赞助取消和赞助等级变更）的分析。 您还可以查看新的赞助、赞助变更和赞助取消等活动。 您可以按日期过滤活动列表。 您还可以导出帐户的赞助数据以 CSV 或 JSON 格式查看。
+
+### 查看您的赞助者和赞助
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. （可选）要按等级过滤赞助者，请使用 **Filter（过滤）**下拉菜单，单击 **Active tiers（活动等级）**或 **Retired tiers（已撤销等级）**，然后选择一个等级。 ![按等级过滤的下拉菜单](/assets/images/help/sponsors/filter-drop-down.png)
+
+### 查看最近的赞助活动
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+
+### 导出赞助数据
+
+您可以按月导出赞助事务。 {% data variables.product.company_short %} 将向您发送一封电子邮件，其中包含您所选月份所有赞助者的事务数据。 导出完成后，您可以导出另一个月的数据。 对于您的任何被赞助帐户，您每小时最多可以导出 10 组数据。
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.activity-tab %}
+1. 单击 {% octicon "download" aria-label="The download icon" %} **Export（导出）**。 ![导出按钮](/assets/images/help/sponsors/export-all.png)
+1. 选择您想导出的数据的时间范围和格式，然后单击 **Start export（开始导出）**。 ![数据导出选项](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..a6dcc5fe57
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,20 @@
+---
+title: 将赞助归因于组织
+intro: 您可以将您某个组织支付的赞助归因于另一个组织。
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  free-pro-team: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+---
+
+1. 导航到要将其赞助归因于另一个组织的组织。
+2. 在组织名称下，单击 {% octicon "heart" aria-label="The heart icon" %} **Sponsoring（赞助）**。 !["赞助" 选项卡](/assets/images/help/sponsors/sponsoring-tab.png)
+1. 在右上角，单击 {% octicon "gear" aria-label="The gear icon" %} **Settings（设置）**。 !["设置"按钮](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. 在“Link sponsorships to another account（将赞助链接到另一个帐户）”下，使用下拉菜单，然后单击要将此组织的赞助归因到的组织。 ![选择帐户的下拉菜单](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. 单击 **Link account（链接帐户）**。 !["链接帐户"按钮](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..2d217ae761
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,14 @@
+---
+title: 赞助开源贡献者
+intro: '您可以赞助贡献者、接收有关您赞助的开发者和组织的更新，以及在整个 {% data variables.product.product_name %} 内显示赞助者徽章。'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  free-pro-team: '*'
+---
+
+{% link_with_intro /sponsoring-an-open-source-contributor %}
+{% link_with_intro /managing-your-sponsorship %}
+{% link_with_intro /attributing-sponsorships-to-your-organization %}
diff --git a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..525cd8ebd6
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,41 @@
+---
+title: 管理赞助
+intro: 您可以管理谁能看到您的赞助，以及您是否要接收来自被赞助帐户的电子邮件更新。
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  free-pro-team: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### 管理赞助的隐私设置
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### 管理赞助的电子邮件更新
+
+您可以选择您赞助的帐户能否以电子邮件向您发送其工作的更新。 被赞助帐户无法访问您的电子邮件地址。
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %}
+{% data reusables.sponsors.sponsorship-dashboard %}
+{% data reusables.sponsors.manage-sponsorship %}
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.update-sponsorship %}
+
+### 延伸阅读
+
+- "[升级赞助](/articles/upgrading-a-sponsorship)"
+- "[降级赞助](/articles/downgrading-a-sponsorship)"
diff --git a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..4213224ef4
--- /dev/null
+++ b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,66 @@
+---
+title: 赞助开源贡献者
+intro: 您可以向设计、创建或维护您所依赖的开源项目的开发者或组织每月定期付款。
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  free-pro-team: '*'
+permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+---
+
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+### 关于赞助
+
+{% data reusables.sponsors.sponsorship-details %}
+
+您可以代表您的用户帐户赞助一个帐户，以投资您个人受益的项目。 您可以代表您的组织赞助帐户，原因有很多。
+- 维护组织工作所依赖的特定库
+- 投资于作为一个组织所依赖的生态系统（如区块链）
+- 作为重视开源的组织，培养品牌知名度
+- 感谢开源开发者构建库来补充您的组织提供的产品
+
+您可以使用信用卡赞助 {% data variables.product.product_name %} 上的帐户。 如果您的组织希望按发票付款，请[联系我们](https://support.github.com/contact/org-sponsors-waitlist)。
+
+{% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。
+
+使用信用卡赞助帐户后，更改将立即生效。 {% data reusables.sponsors.prorated-sponsorship %}
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+如果被赞助帐户撤销的等级，您将仍保留在该等级，直到您选择其他等级或取消订阅。 更多信息请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。
+
+如果您要赞助的帐户在 {% data variables.product.prodname_sponsors %} 上还没有个人资料，您可以建议该帐户加入。 更多信息请参阅“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”和“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**注：**{% data variables.product.prodname_dotcom %} 对开发者如何介绍自己概不负责，{% data variables.product.prodname_dotcom %} 也不为任何被赞助的开源项目背书。 索赔由接受资助的开发者自行负责。 请确保在建立信任之后提供赞助。 更多信息请参阅 [{% data variables.product.prodname_sponsors %} 附加条款](/github/site-policy/github-sponsors-additional-terms)。
+
+{% endnote %}
+
+### 赞助帐户
+
+在赞助帐户之前，您必须拥有经过验证的电子邮件地址。 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。
+
+1. 在 {% data variables.product.product_name %} 上，导航到您要赞助的用户或组织的个人资料。
+1. 导航到帐户的赞助仪表板。
+   - 要赞助开发者，请在开发者的名称下单击 **Sponsor（赞助）**。 ![赞助按钮](/assets/images/help/profile/sponsor-button.png)
+   - 要赞助组织，请在组织名称的右侧单击 **Sponsor（赞助）**。 ![赞助按钮](/assets/images/help/sponsors/sponsor-org-button.png)
+1. （可选），在页面的右侧，要代表您的组织赞助帐户，请使用 **Sponsor as（赞助者）**下拉菜单，然后单击组织。 ![选择将作为赞助者的帐户](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png)
+{% data reusables.sponsors.select-a-tier %}
+{% data reusables.sponsors.pay-prorated-amount %}
+{% data reusables.sponsors.select-sponsorship-billing %}
+  ![编辑付款按钮](/assets/images/help/sponsors/edit-sponsorship-payment-button.png)
+{% data reusables.sponsors.who-can-see-your-sponsorship %}
+  ![用于选择谁可以查看您的赞助的单选按钮](/assets/images/help/sponsors/who-can-see-sponsorship.png)
+{% data reusables.sponsors.choose-updates %}
+{% data reusables.sponsors.sponsor-account %}
diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml
index 38eee4caa4..96d439b749 100644
--- a/translations/zh-CN/data/glossaries/external.yml
+++ b/translations/zh-CN/data/glossaries/external.yml
@@ -181,7 +181,7 @@
 - 
   term: 默认分支
   description: >-
-    仓库中新拉取请求和代码提交的基本分支。每个仓库至少有一个分支，Git 会在您初始化仓库时创建该分支。第一个分支通常称为"main"，并且通常是默认分支。
+    仓库中新拉取请求和代码提交的基本分支。每个仓库至少有一个分支，Git 会在您初始化仓库时创建该分支。第一个分支通常称为 {% if currentVersion ver_lt "enterprise-server@3.2" %}`master`{% else %}`main`{% endif %}，并且通常是默认分支。
 - 
   term: 从属者图
   description: >-
@@ -390,11 +390,11 @@
 - 
   term: main
   description: >-
-    默认开发分支。只要创建 Git 仓库，就会创建一个名为 "main" 的分支，并且它会变为活动的分支。大多数情况下，这包含本地开发，但纯属惯例，而非必需。
+    {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} 默认开发分支。每当您创建 Git 仓库时，都会创建名为 `main` 的分支，它将成为活动分支。在大多数情况下，它包含本地开发内容，但这完全是就惯例而言，并不是必需的。{% else %}通常选择名称替代仓库默认分支的名称 `master`。{% endif %}
 - 
   term: master
   description: >-
-    许多 Git 存储库中的默认分支。默认情况下，在命令行上创建新的 Git 仓库时，将创建一个名为 "master" 的分支。许多工具现在对默认分支使用替代名称。例如，在 GitHub 上创建新仓库时，默认分支称为 "main"。
+    许多 Git 仓库中的默认分支。默认情况下，在命令行上创建新的 Git 仓库时，将创建一个名为 "master" 的分支。许多工具现在对默认分支使用替代名称。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %} 例如，在 GitHub 上创建新仓库时，默认分支称为 "main"。{% endif %}
 - 
   term: 成员图
   description: 显示仓库所有分叉的仓库图。
diff --git a/translations/zh-CN/data/glossaries/internal.yml b/translations/zh-CN/data/glossaries/internal.yml
index f951d1f08c..5e5e22ab40 100644
--- a/translations/zh-CN/data/glossaries/internal.yml
+++ b/translations/zh-CN/data/glossaries/internal.yml
@@ -60,6 +60,10 @@
 - 
   term: Azure
   description: 一个 Microsoft 云计算平台。
+- 
+  term: Azure DevOps
+  description: >-
+    提供源代码托管、议题、CI/CD 管道和其他开发者服务的 Microsoft 产品。本地版本以前称为 Team Foundation Server。云托管版本以前称为 Visual Studio Team Services。
 - 
   term: 裸仓库
   description: >-
@@ -648,7 +652,7 @@
 - 
   term: Team Foundation Server
   description: >-
-    一种 Microsoft 产品，提供源代码管理和其他团队服务。
+    提供源代码管理和其他团队服务的 Microsoft 产品的前名称。现在称为 Azure DevOps Server。
 - 
   term: Textile
   description: >-
diff --git a/translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..ede543a19a
--- /dev/null
+++ b/translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml
@@ -0,0 +1,134 @@
+---
+- 
+  title: 使用包版本删除
+  description: >-
+    此预览支持允许删除私有包版本 DeletePackageVersion 突变。
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: 部署
+  description: >-
+    此预览支持部署突变和新部署功能。
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/ecosystem-api'
+- 
+  title: >-
+    MergeInfoPreview - 有关拉取请求合并状态的更多详细信息。
+  description: >-
+    此预览支持访问提供有关拉取请求合并状态的更多详细信息的字段。
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - 在单个操作中更新多个 ref。
+  description: 此预览支持在单个操作中更新多个 ref。
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: 项目事件详细信息
+  description: >-
+    此预览将项目、项目卡和项目列详细信息添加到与项目相关的议题事件。
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: 创建内容附件
+  description: 此预览支持创建内容附件。
+  toggled_by: ':corsair-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createContentAttachment
+  owning_teams:
+    - '@github/feature-lifecycle'
+- 
+  title: 标签预览
+  description: >-
+    此预览支持添加、更新、创建和删除标签。
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: 导入项目
+  description: 此预览增加了对导入项目的支持。
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: 团队审查任务预览
+  description: >-
+    此预览支持更新团队审查任务的设置。
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/zh-CN/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..6f16748e78
--- /dev/null
+++ b/translations/zh-CN/data/graphql/ghes-3.1/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,114 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate` 将被删除。使用 `uploadUrl` 代替。'
+    reason: '`uploadUrlTemplate` 正在被删除，因为它不是标准的 URL，并且增加了一个额外的用户步骤。'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: 重大
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user` 将被删除。使用 `assignee` 字段代替。'
+    reason: 受理人现在可以作为人体模型。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: tambling
+  - 
+    location: EnterpriseBillingInfo.availableSeats
+    description: '`availableSeats` 将被删除。使用 EnterpriseBillingInfo.totalAvailableLicenses 代替。'
+    reason: '`availableSeats` 将被替换为 `totalAvailableLicenses`，以便更明确地表示要返回的值'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: BlakeWilliams
+  - 
+    location: EnterpriseBillingInfo.seats
+    description: '`seats` 将被删除。使用 EnterpriseBillingInfo.totalLicenses 代替。'
+    reason: '`seats` 将被替换为 `totalLicenses`，以便更明确地表示要返回的值'
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: BlakeWilliams
+  - 
+    location: UnassignedEvent.user
+    description: '`user` 将被删除。使用 `assignee` 字段代替。'
+    reason: 受理人现在可以作为人体模型。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: tambling
+  - 
+    location: Sponsorship.maintainer
+    description: '`maintainer` 将被删除。使用 `Sponsorship.sponsorable` 代替。'
+    reason: '`Sponsorship.maintainer` 将被删除。'
+    date: '2020-04-01T00:00:00+00:00'
+    criticality: 重大
+    owner: antn
+  - 
+    location: EnterprisePendingMemberInvitationEdge.isUnlicensed
+    description: '`isUnlicensed` 将被删除。'
+    reason: 所有挂起的成员都会使用许可证
+    date: '2020-07-01T00:00:00+00:00'
+    criticality: 重大
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOwnerInfo.pendingCollaborators
+    description: '`pendingCollaborators` 将被删除。改用 `pendingCollaboratorInvitations` 字段。'
+    reason: 仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: jdennes
+  - 
+    location: Issue.timeline
+    description: '`timeline` 将被删除。使用 Issue.timelineItems 代替。'
+    reason: '`timeline` 将被删除'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline` 将被删除。使用 PullRequest.timelineItems 代替。'
+    reason: '`timeline` 将被删除'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: mikesea
+  - 
+    location: RepositoryInvitationOrderField.INVITEE_LOGIN
+    description: '`INVITEE_LOGIN` 将被删除。'
+    reason: '`INVITEE_LOGIN` 不再是有效字段值。仓库邀请此时可与电子邮件关联，而不仅仅是被邀请者。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: jdennes
+  - 
+    location: Sponsorship.sponsor
+    description: '`sponsor` 将被删除。改用 `Sponsorship.sponsorEntity`。'
+    reason: '`Sponsorship.sponsor` 将被删除。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 重大
+    owner: nholden
+  - 
+    location: EnterpriseMemberEdge.isUnlicensed
+    description: '`isUnlicensed` 将被删除。'
+    reason: 所有成员都会使用许可证
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: BrentWheeldon
+  - 
+    location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` 将被删除。'
+    reason: 所有外部协作者使用许可证
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: BrentWheeldon
+  - 
+    location: EnterprisePendingCollaboratorEdge.isUnlicensed
+    description: '`isUnlicensed` 将被删除。'
+    reason: 所有挂起的协作者使用许可证
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: BrentWheeldon
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT` 将被删除。改为使用 PullRequest.isDraft。'
+    reason: DRAFT 状态将从这个枚举中删除，应改用 `isDraft`
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 重大
+    owner: nplasterer
diff --git a/translations/zh-CN/data/learning-tracks/README.md b/translations/zh-CN/data/learning-tracks/README.md
index f7d4b7cb9a..88076f5733 100644
--- a/translations/zh-CN/data/learning-tracks/README.md
+++ b/translations/zh-CN/data/learning-tracks/README.md
@@ -1,3 +1,30 @@
 # 学习轨迹（又名学习路径）
 
-学习轨迹是一系列帮助您掌握特定主题的文章。 学习轨迹按每个产品定义。
\ No newline at end of file
+学习轨迹是一系列帮助您掌握特定主题的文章。 学习轨迹按每个产品定义。 有关示例，请参阅 https://docs.github.com/en/actions/guides。
+
+产品的学习轨迹数据在两个地方定义：
+
+1. 简单的学习轨迹名称数组在产品分类索引页面前缀中定义。
+
+    例如，在 `content/actions/guides/index.md` 中：
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. 每个轨迹的额外数据在 `data` 目录中为**产品**命名的 YAML 文件中定义。
+
+    例如，在 `data/learning-tracks/actions.yml` 中，内容文件的 `learningTracks` 数组中每个项都用 `title`、`description` 和 `guides` 链接数组等额外数据来表示。
+
+    在此 YAML **每个版本**中，必须通过 `featured_track: true` 指定一个学习轨迹为“特色”学习轨迹，这将设置它出现在产品分类页面的顶部。 如果缺少此属性，测试将失败。
+
+    `featured_track` 属性可以是简单的布尔值（例如 `featured_track: true`），也可以是包含版本控制语句的字符串（例如 `featured_track: '{% if currentVersion == "free-pro-team@latest" %}true{% else %}false{% endif %}'`）。 如果您使用版本控制，每个 YML 文件将有多个 `featured_track`，但请确保每个当前支持的版本中只有一个版本会呈现。 如果每个版本的特色链接多于或少于一个，测试将失败。
+
+学习轨迹的版本控制在页面渲染时进行处理。 代码位于 [`lib/learning-tracks.js`](lib/learning-tracks.js) 中，通过 `page.render()` 调用。 然后通过 `layouts/product-sublanding.html` 渲染处理后的学习轨迹。
+
+验证学习轨迹的架构 YAML 位于 [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) 中，通过 [`tests/content/lint-files.js`](tests/content/lint-files.js) 执行。
diff --git a/translations/zh-CN/data/learning-tracks/actions.yml b/translations/zh-CN/data/learning-tracks/actions.yml
index b6f917b826..c822aea047 100644
--- a/translations/zh-CN/data/learning-tracks/actions.yml
+++ b/translations/zh-CN/data/learning-tracks/actions.yml
@@ -8,6 +8,7 @@ getting_started:
     - /actions/learn-github-actions/essential-features-of-github-actions
     - /actions/learn-github-actions/managing-complex-workflows
     - /actions/learn-github-actions/security-hardening-for-github-actions
+  featured_track: true
 continuous_integration:
   title: '构建和测试代码'
   description: '您可以在仓库中创建自定义的持续集成 (CI) 工作流程。'
diff --git a/translations/zh-CN/data/learning-tracks/admin.yml b/translations/zh-CN/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..60a30201b4
--- /dev/null
+++ b/translations/zh-CN/data/learning-tracks/admin.yml
@@ -0,0 +1,72 @@
+---
+get_started_with_github_ae:
+  title: '开始使用 {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}.'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
diff --git a/translations/zh-CN/data/release-notes/2-21/19.yml b/translations/zh-CN/data/release-notes/2-21/19.yml
new file mode 100644
index 0000000000..5af2366476
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/2-21/19.yml
@@ -0,0 +1,18 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - '警告消息 `jq: error (at <stdin>:0): Cannot index number with string "settings"` 可能在副本升级期间出现。'
+    - 访问 `/settings/email` 页面会存储状态，在登出并重新登录时可能导致错误的重定向。
+    - 对于其通告在 `vulnerable_version_ranges` 中具有大写包名称的组件，未显示依赖项图警报。
+    - 用户在使用 LDAP 身份验证配置的实例上执行 git 操作时看到 500 错误。
+    - 当 ghe-migrator 遇到导入错误时，它有时会中止整个过程，但日志中没有包含足够的上下文。
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - 推送到命令行上的仓库时不报告安全警报。
diff --git a/translations/zh-CN/data/release-notes/2-21/20.yml b/translations/zh-CN/data/release-notes/2-21/20.yml
new file mode 100644
index 0000000000..e67267abaf
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/2-21/20.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - 在 MySQL 副本上运行的安装脚本可能导致数据库故障转移期间不必要的数据库重新播种。
+    - '由于不必要地调用 `rake db:migrate`，`config-apply` 可能需要更长的时间。'
+    - Orchestrator 可能已故障转移到 MySQL 副本，当主数据库无法连接时，它无法在播种阶段从主数据库复制。
+    - 出现错误的组织或项目阻止了迁移，无法排除。
+  changes:
+    - 默认情况下，预运行检查允许所有 AWS 实例类型。
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - 推送到命令行上的仓库时不报告安全警报。
diff --git a/translations/zh-CN/data/release-notes/2-21/21.yml b/translations/zh-CN/data/release-notes/2-21/21.yml
new file mode 100644
index 0000000000..aecbf42dc9
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/2-21/21.yml
@@ -0,0 +1,15 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - 推送到命令行上的仓库时不报告安全警报。
diff --git a/translations/zh-CN/data/release-notes/2-22/11.yml b/translations/zh-CN/data/release-notes/2-22/11.yml
new file mode 100644
index 0000000000..70eaa95b9d
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/2-22/11.yml
@@ -0,0 +1,19 @@
+---
+date: '2021-04-14'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - '警告消息 `jq: error (at <stdin>:0): Cannot index number with string "settings"` 可能在副本升级期间出现。'
+    - 由于 MySQL 副本无法连接到主数据库，因此将备份连续还原到集群可能会失败。
+    - 由于 Treelights 容器内存不足，语法高亮可能失败。
+    - 访问 `/settings/email` 页面会存储状态，在登出并重新登录时可能导致错误的重定向。
+    - 对于其通告在 `vulnerable_version_ranges` 中具有大写包名称的组件，未显示依赖项图警报。
+    - 在议题评论中通过提及功能直接提及团队时，GitHub 集成应用程序无法通知团队。
+    - 当 ghe-migrator 遇到导入错误时，它有时会中止整个过程，但日志中没有包含足够的上下文。
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
diff --git a/translations/zh-CN/data/release-notes/2-22/12.yml b/translations/zh-CN/data/release-notes/2-22/12.yml
new file mode 100644
index 0000000000..9d93c33bbb
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/2-22/12.yml
@@ -0,0 +1,22 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - 在升级过程中，进程将在 `cleanup nomad job` 之后无限期暂停。
+    - '`ghe-cluster-failover` 失败，出现错误消息 `Trilogy::Error: trilogy_connect`。'
+    - '`ghe-cluster-status-mysql` 将有关故障转移的警告显示为错误。'
+    - 在 MySQL 副本上运行的安装脚本可能导致数据库故障转移期间不必要的数据库重新播种。
+    - '由于不必要地调用 `rake db:migrate`，`config-apply` 可能需要更长的时间。'
+    - Orchestrator 可能已故障转移到 MySQL 副本，当主数据库无法连接时，它无法在播种阶段从主数据库复制。
+    - 出现错误的组织或项目阻止了迁移，无法排除。
+    - 由于选择了最完整的磁盘而不是空节点，存储主机超过三个的客户无法恢复到其灾难恢复集群。
+  changes:
+    - 默认情况下，预运行检查允许所有 AWS 实例类型。
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
diff --git a/translations/zh-CN/data/release-notes/2-22/13.yml b/translations/zh-CN/data/release-notes/2-22/13.yml
new file mode 100644
index 0000000000..338b6768e1
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/2-22/13.yml
@@ -0,0 +1,20 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
diff --git a/translations/zh-CN/data/release-notes/3-0/0.yml b/translations/zh-CN/data/release-notes/3-0/0.yml
index bb64e619ff..6e1131d267 100644
--- a/translations/zh-CN/data/release-notes/3-0/0.yml
+++ b/translations/zh-CN/data/release-notes/3-0/0.yml
@@ -134,6 +134,7 @@ sections:
     - 竞争条件可能导致依赖关系图数据库迁移失败。
     - 自定义时区从较早发布的 GitHub Enterprise Server 升级的实例可能在 web UI 中有不正确的时间戳。
     - Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。
+    - 在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。
   deprecations:
     - 
       heading: 弃用 GitHub Enterprise Server 2.19
diff --git a/translations/zh-CN/data/release-notes/3-0/1.yml b/translations/zh-CN/data/release-notes/3-0/1.yml
index 1f4433e088..729affd983 100644
--- a/translations/zh-CN/data/release-notes/3-0/1.yml
+++ b/translations/zh-CN/data/release-notes/3-0/1.yml
@@ -45,6 +45,7 @@ sections:
     - '依赖关系图无法解析 `yarn.lock` Javascript 清单文件，导致日志中的 HTTP 500 错误。'
     - '自定义时区从较早发布的 GitHub Enterprise Server 升级的实例可能在 web UI 中有不正确的时间戳。'
     - 'Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。'
+    - '在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。'
     - |
       用户可能会遇到一些资产（如头像）不加载，或者无法推送/拉取代码。这可能是由于 `haproxy-cluster-proxy` 服务中的 PID 不匹配造成的。要确定您是否有受影响的实例：
 
diff --git a/translations/zh-CN/data/release-notes/3-0/2.yml b/translations/zh-CN/data/release-notes/3-0/2.yml
index 13f80e8c55..8b9d0bf94b 100644
--- a/translations/zh-CN/data/release-notes/3-0/2.yml
+++ b/translations/zh-CN/data/release-notes/3-0/2.yml
@@ -31,6 +31,7 @@ sections:
     - 如果笔记本包含非 ASCII UTF-8 字符，网页界面中的 Jupyter Notebook 渲染可能会失败。
     - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。
     - Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。
+    - 在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。
     - |
       用户可能会遇到一些资产（如头像）不加载，或者无法推送/拉取代码。这可能是由于 `haproxy-cluster-proxy` 服务中的 PID 不匹配造成的。要确定您是否有受影响的实例：
 
diff --git a/translations/zh-CN/data/release-notes/3-0/3.yml b/translations/zh-CN/data/release-notes/3-0/3.yml
index b9a10a27e2..5d94135de5 100644
--- a/translations/zh-CN/data/release-notes/3-0/3.yml
+++ b/translations/zh-CN/data/release-notes/3-0/3.yml
@@ -30,6 +30,7 @@ sections:
     - 如果笔记本包含非 ASCII UTF-8 字符，网页界面中的 Jupyter Notebook 渲染可能会失败。
     - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。
     - Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。
+    - 在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。
     - |
       日志旋转可能无法指示服务过渡到新日志文件，导致继续使用旧日志文件，最终根磁盘空间耗尽。
       为了补救和/或防止这个问题，请在 [管理 shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-sh) (SSH) 中运行以下命令或联系 [GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) 寻求协助：
diff --git a/translations/zh-CN/data/release-notes/3-0/4.yml b/translations/zh-CN/data/release-notes/3-0/4.yml
index d9a22f1fb0..a2cf976b3c 100644
--- a/translations/zh-CN/data/release-notes/3-0/4.yml
+++ b/translations/zh-CN/data/release-notes/3-0/4.yml
@@ -23,3 +23,4 @@ sections:
     - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
     - 如果笔记本包含非 ASCII UTF-8 字符，网页界面中的 Jupyter Notebook 渲染可能会失败。
     - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。
+    - 在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。
diff --git a/translations/zh-CN/data/release-notes/3-0/5.yml b/translations/zh-CN/data/release-notes/3-0/5.yml
new file mode 100644
index 0000000000..41cf48e220
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/3-0/5.yml
@@ -0,0 +1,27 @@
+---
+date: '2021-04-14'
+intro: '对于 {% data variables.product.prodname_ghe_server %} 3.0+ 的最低基础设施要求已经增加。更多信息请参阅“[关于GitHub Enterprise Server 3.0 及更高版本的最低要求](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)”。'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - 有些日志未包含在日志转发配置中。
+    - '警告消息 `jq: error (at <stdin>:0): Cannot index number with string "settings"` 可能在副本升级期间出现。'
+    - 由于 MySQL 副本无法连接到主数据库，因此将备份连续还原到集群可能会失败。
+    - 使用自定义 CA 证书时页面未发布。
+    - 与子域相关的包未显示在“测试域设置”提示中以进行子域隔离。
+    - 通过 web 挂钩发送的 `X-GitHub-Enterprise-Host` 标头包含一个随机字符串，而不是发送 HTTP POST 有效负载的 GitHub Enterprise Server 实例的主机名。
+    - 如果先前启用了 GitHub Actions，但在升级之前被禁用，则从 2.22.x 升级到 3.0.x 将会失败。
+    - 访问 `/settings/email` 页面会存储状态，在登出并重新登录时可能导致错误的重定向。
+    - 在议题评论中通过提及功能直接提及团队时，GitHub 集成应用程序无法通知团队。
+    - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。
+    - 如果未完全启用依赖项图，则不会将密码扫描警报的电子邮件通知发送给授权用户。
+    - 当 ghe-migrator 遇到导入错误时，它有时会中止整个过程，但日志中没有包含足够的上下文。
+    - 具有非 ASCII 字符的 Jupyter notebook 可能无法渲染。
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+    - 在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。
diff --git a/translations/zh-CN/data/release-notes/3-0/6.yml b/translations/zh-CN/data/release-notes/3-0/6.yml
new file mode 100644
index 0000000000..1432f95e25
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/3-0/6.yml
@@ -0,0 +1,30 @@
+---
+date: '2021-04-28'
+sections:
+  security_fixes:
+    - 包已更新到最新的安全版本。
+  bugs:
+    - 在升级过程中，进程将在 `cleanup nomad job` 之后无限期暂停。
+    - '`ghe-cluster-failover` 失败，出现错误消息 `Trilogy::Error: trilogy_connect`。'
+    - '`ghe-cluster-status-mysql` 将有关故障转移的警告显示为错误。'
+    - 在 MySQL 副本上运行的安装脚本可能导致数据库故障转移期间不必要的数据库重新播种。
+    - 升级未包括正确安装的 Actions 运行器最新版本。
+    - '`github-env` 配置可能导致僵尸进程。'
+    - '由于不必要地调用 `rake db:migrate`，`config-apply` 可能需要更长的时间。'
+    - Orchestrator 可能已故障转移到 MySQL 副本，当主数据库无法连接时，它无法在播种阶段从主数据库复制。
+    - 出现错误的组织或项目阻止了迁移，无法排除。
+    - 对于所属组织超过 50 个的用户禁用了“Create Repository（创建仓库）”按钮。
+    - 删除分支会临时闪烁一条错误消息，指示删除成功时出错。
+    - '`rms-packages` 索引显示在站点管理员仪表板中。'
+    - 由于表单上未显示正确的可见性选项，因此组织所有者无法创建内部仓库。
+    - 在操作启动工作流程配置错误的情况下，仓库操作选项卡显示 500。
+    - 由于选择了最完整的磁盘而不是空节点，存储主机超过三个的客户无法恢复到其灾难恢复集群。
+    - 应用热补丁后，代码扫描后端服务无法可靠启动。
+  changes:
+    - 默认情况下，预运行检查允许所有 AWS 实例类型。
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
diff --git a/translations/zh-CN/data/release-notes/3-0/7.yml b/translations/zh-CN/data/release-notes/3-0/7.yml
new file mode 100644
index 0000000000..0f75383d7e
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/3-0/7.yml
@@ -0,0 +1,23 @@
+---
+date: '2021-05-13'
+sections:
+  security_fixes:
+    - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)."
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Quotes included in Actions or Packages storage configuration could cause errors.
+    - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits.
+    - Orchestrator auto failover could be enabled during the phase of config apply.
+    - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page.
+    - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path.
+    - OpenAPI documentation referred to an invalid header.
+    - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.
+  changes:
+    - Added logging for config change on HAProxy reload.
+    - Added logging for repository creation.
+  known_issues:
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
diff --git a/translations/zh-CN/data/release-notes/3-1/0-rc1.yml b/translations/zh-CN/data/release-notes/3-1/0-rc1.yml
new file mode 100644
index 0000000000..a5648b72fb
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/3-1/0-rc1.yml
@@ -0,0 +1,130 @@
+---
+date: '2021-05-06'
+release_candidate: true
+intro: 如果 {% data variables.product.product_location %} 正在运行候选版本，则无法使用热补丁进行升级。我们建议仅在测试环境中运行候选版本。
+sections:
+  features:
+    - 
+      heading: GitHub Advanced Security 密码扫码
+      notes:
+        - |
+          [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository.
+
+          This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}:
+
+          - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37
+          - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert)
+          - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets
+          - Updated the index view to made it easy to triage secrets in bulk
+          - Reduced the false positive rate on many patterns
+
+          Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning.
+    - 
+      heading: GitHub Advanced Security billing improvements
+      notes:
+        - |
+          This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}:
+
+          - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)."
+          - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+    - 
+      heading: Dependabot improvements
+      notes:
+        - |
+          This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}:
+
+          - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)."
+          - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository).
+          - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."'
+    - 
+      heading: GitHub Actions Workflow Visualization beta
+      notes:
+        - |
+
+          GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can:
+          - View and understand complex workflows
+          - Track progress of workflows in real-time
+          - Troubleshoot runs quickly by easily accessing logs and jobs metadata
+          - Monitor progress of deployment jobs and easily access deployment targets
+
+          For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)."
+    - 
+      heading: OAuth 2.0 Device Authorization Grant
+      notes:
+        - |
+          [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser.
+
+          Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow.
+    - 
+      heading: 拉取请求自动合并
+      notes:
+        - |
+          With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+    - 
+      heading: 自定义通知
+      notes:
+        - |
+          You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+  changes:
+    - 
+      heading: 管理更改
+      notes:
+        - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.
+        - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+        - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.
+        - Check annotations older than four months will be archived.
+    - 
+      heading: 安全性更改
+      notes:
+        - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).'
+        - SARIF upload support increased to a maximum of 5000 results per upload.
+    - 
+      heading: 开发者更改
+      notes:
+        - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to.
+        - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)."
+        - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list.
+        - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."'
+        - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.'
+        - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.'
+    - 
+      heading: API 更改
+      notes:
+        - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning).
+        - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints.
+  known_issues:
+    - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
+    - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
+    - 自定义防火墙规则在升级期间不会保持。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.20
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 2.21
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: 弃用旧版的 GitHub App web 挂钩事件
+      notes:
+        - '从 {% data variables.product.prodname_ghe_server %} 2.21.0 开始，两个旧的 GitHub 应用程序相关的 web 挂钩事件已弃用，并将在 {% data variables.product.prodname_ghe_server %} 3.2.0 中删除。弃用的事件 `integration_installation` 和 `integration_installation_repositories` 都有受支持的相应事件。更多信息请见[弃用公告博文](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/)。'
+    - 
+      heading: 弃用旧版 GitHub Apps 端点
+      notes:
+        - 从 {% data variables.product.prodname_ghe_server %} 2.21.0 开始，用于创建安装访问令牌的旧 GitHub 应用程序端点已弃用，并将在 {% data variables.product.prodname_ghe_server %} 3.2.0 中删除。更多信息请见[弃用公告博文](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/)。
+    - 
+      heading: 弃用 OAuth Application API
+      notes:
+        - 'GitHub 不再支持包含 `access_token` 作为路径参数的 OAuth 应用程序端点。我们引入了新的端点，允许您通过将 `access_token` 移动到请求正文来安全地管理 OAuth 应用程序的令牌。虽然已弃用，但这些端点仍然可以在这个版本中访问。我们打算在 {% data variables.product.prodname_ghe_server %} 3.4 中删除这些端点。更多信息请参阅[弃用公告博文](https://developer.github.com/changes/2020-02-14-decreasating-oauth-app-endpoint/)。'
+    - 
+      heading: Deprecation of GitHub Actions short SHA support
+      notes:
+        - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."'
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).'
diff --git a/translations/zh-CN/data/reusables/actions/actions-cli.md b/translations/zh-CN/data/reusables/actions/actions-cli.md
new file mode 100644
index 0000000000..db297bcbab
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/actions-cli.md
@@ -0,0 +1 @@
+有关设置 {% data variables.product.prodname_cli %} 的信息，请参阅“[使用 GitHub CLI 管理 GitHub Actions](/actions/guides/managing-github-actions-with-github-cli#setting-up-github-cli)”。
diff --git a/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md b/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..10e79e7f0c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,25 @@
+当并发作业或工作流程排队时，如果仓库中使用同一并发组的其他作业或工作流程正在运行，则排队的作业或工作流程将 `pending`。 在并发组中任何先前挂起的作业或工作流程都将被取消。 如果还要取消同一并发组中任何当前运行的作业或工作流程，请指定 `cancel-in-progress: true`。
+
+##### 使用并发和默认行为的示例
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+##### 使用并发取消任何当前作业或运行的示例
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
diff --git a/translations/zh-CN/data/reusables/actions/concurrency-beta.md b/translations/zh-CN/data/reusables/actions/concurrency-beta.md
new file mode 100644
index 0000000000..2d10ac2f23
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/concurrency-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**注：**并发目前处于测试阶段，可能会更改。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/actions/enterprise-github-connect-warning.md b/translations/zh-CN/data/reusables/actions/enterprise-github-connect-warning.md
new file mode 100644
index 0000000000..f62957f7d7
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/enterprise-github-connect-warning.md
@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}
+{% note %}
+
+**注：**启用 {% data variables.product.prodname_github_connect %} 后，{% data variables.product.prodname_actions %} 将尝试在您的 {% data variables.product.prodname_ghe_server %} 实例上查找仓库，然后返回到 {% data variables.product.prodname_dotcom %}。 如果用户在企业中创建的组织和仓库与 {% data variables.product.prodname_dotcom %} 上的组织和仓库名称匹配，则将使用企业上的仓库代替 {% data variables.product.prodname_dotcom %} 仓库。 恶意用户可能利用此行为在工作流程中运行代码。
+
+{% endnote %}
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/actions/enterprise-no-internet-actions.md b/translations/zh-CN/data/reusables/actions/enterprise-no-internet-actions.md
index b589b76048..eeb87e4c66 100644
--- a/translations/zh-CN/data/reusables/actions/enterprise-no-internet-actions.md
+++ b/translations/zh-CN/data/reusables/actions/enterprise-no-internet-actions.md
@@ -1 +1 @@
-{% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_actions %} 设计为在没有互联网连接的环境中工作。 默认情况下，工作流程不能使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 和 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 的操作。
+{% data variables.product.product_name %} 上的 {% data variables.product.prodname_actions %} 设计为在无法完全访问互联网的环境中工作。 默认情况下，工作流程不能使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 和 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 的操作。
diff --git a/translations/zh-CN/data/reusables/actions/forked-secrets.md b/translations/zh-CN/data/reusables/actions/forked-secrets.md
index b294a32b2f..3b155ebd96 100644
--- a/translations/zh-CN/data/reusables/actions/forked-secrets.md
+++ b/translations/zh-CN/data/reusables/actions/forked-secrets.md
@@ -1 +1 @@
-除了 `GITHUB_TOKEN` 以外，从复刻的仓库触发工作流程时密码不会传递给运行程序。
+除了 `GITHUB_TOKEN` 以外，从复刻的仓库触发工作流程时密码不会传递给运行程序。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..16e9a8d4a6
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+我们在 {% data variables.product.product_location %}上记录并显示 {% data variables.product.prodname_GH_advanced_security %} 的两个提交者：
+
+- **提交者**是指参与组织中至少一个{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库并且占用企业许可中一个席位的提交者数量。 也就是说，他们也是组织成员、外部协作者，或者具有待处理的企业帐户中组织加入邀请。
+- **对此仓库/组织唯一**是只参与该仓库或该组织中仓库的提交者数量。 此数字显示您可以通过禁用该仓库或组织的 {% data variables.product.prodname_GH_advanced_security %} 来释放多少许可证席位。
+
+如果没有唯一的提交者，则意味着所有活跃的提交者也参与其他使用 {% data variables.product.prodname_GH_advanced_security %} 的仓库或组织。 禁用该仓库或组织的功能将不会在您的许可证上腾出任何席位。
+
+从企业帐户中删除用户后，用户的许可证在 24 小时内被释放。
+
+{% note %}
+
+**注：**用户可以参与多个仓库或组织。 使用数是在整个企业帐户中计量的，确保每个成员使用一个席位，无论该用户参与多少个仓库或组织。
+
+{% endnote %}
diff --git a/translations/zh-CN/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/zh-CN/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..7e681acf77
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_GH_advanced_security %} 的每个许可证都规定了可以使用这些功能的最大帐户或席位数量。 您应该定期检查您的使用是否在许可范围之内。
diff --git a/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md
index 83453db412..17d0ac2d17 100644
--- a/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md
+++ b/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -1,4 +1,4 @@
-{% data variables.product.company_short %} 按提交者对 {% data variables.product.prodname_advanced_security %} 计费。 {% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[管理 {% data variables.product.prodname_GH_advanced_security %} 的许可](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)”。{% endif %}
+{% data variables.product.company_short %} 按提交者对 {% data variables.product.prodname_advanced_security %} 计费。 {% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[管理 {% data variables.product.prodname_GH_advanced_security %} 的许可](/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security)”。{% elsif currentVersion ver_gt "enterprise-server@3.0" %}更多信息请参阅“[管理企业的 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security)”。{% endif %}
 
 您可以执行策略来控制仓库管理员是否被允许在组织的仓库中为 {% data variables.product.prodname_advanced_security %} 启用功能。 您可以为企业帐户拥有的所有组织或您选择的单个组织配置策略。
 
diff --git a/translations/zh-CN/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/zh-CN/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..176cb24c87
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,6 @@
+当您决定哪些仓库和组织优先用于 {% data variables.product.prodname_GH_advanced_security %} 时，应该查看它们并识别：
+
+- 对公司成功至关重要的代码库。 在这些项目中，引入了易受攻击代码、硬编码的密钥或易受攻击的依赖项，将对您的公司将产生最大的影响。
+- 提交频率最高的代码库。 这些是最积极开发的项目，因此出现安全问题的风险较高。
+
+当您为这些组织或仓库启用 {% data variables.product.prodname_GH_advanced_security %} 时，应该评估您可以添加哪些其它代码，而无需添加任何额外的唯一提交者以及使用您许可证上的更多席位。 在此之后，查看下一个最重要和最繁忙的代码库。 如果您想增加许可证中的席位数，请联系 {% data variables.contact.contact_enterprise_sales %}。
diff --git a/translations/zh-CN/data/reusables/advanced-security/ghas-helps-developers.md b/translations/zh-CN/data/reusables/advanced-security/ghas-helps-developers.md
index 66b4a4d199..4cab9d9ec9 100644
--- a/translations/zh-CN/data/reusables/advanced-security/ghas-helps-developers.md
+++ b/translations/zh-CN/data/reusables/advanced-security/ghas-helps-developers.md
@@ -1 +1,2 @@
-{% data variables.product.prodname_GH_advanced_security %} 帮助开发者改善和维护代码的安全性和质量。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。
+{% data variables.product.prodname_GH_advanced_security %} 帮助开发者改进和维护代码的安全性和质量。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/zh-CN/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..9fdaa69351
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,5 @@
+为仓库启用或禁用 {% data variables.product.prodname_advanced_security %} 时，{% data variables.product.prodname_dotcom %} 将显示许可证使用情况变化的概况。 如果您禁用对 {% data variables.product.prodname_GH_advanced_security %} 的访问，任何被“唯一”提交者使用的席位都将释放。
+
+如果您超过了许可证限制，{% data variables.product.prodname_GH_advanced_security %} 将继续在所有已启用的仓库中工作。 但是，在为新仓库启用 {% data variables.product.prodname_GH_advanced_security %} 的组织中，将会创建禁用该功能的仓库。 此外，对现有仓库启用 {% data variables.product.prodname_GH_advanced_security %} 的选项将不可用。{% if currentVersion == "free-pro-team@latest" %}如果将公共仓库的可见性更改为私有，则 {% data variables.product.prodname_GH_advanced_security %} 将对该仓库禁用。{% endif %}
+
+一旦您释放一些席位，通过对某些仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 或通过增加您的许可证大小，用于启用 {% data variables.product.prodname_GH_advanced_security %} 的选项将继续正常工作。
diff --git a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md
index 26ea19355f..122204805a 100644
--- a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md
+++ b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md
@@ -1,9 +1,9 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
 {% warning %}
 
-**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %}  For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/).
+**弃用通知：** {% data variables.product.prodname_dotcom %} 将停止使用查询参数向 API 验证。 向 API 验证应使用 [HTTP 基本身份验证](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)完成。{% if currentVersion == "free-pro-team@latest" %} 使用查询参数向 API 验证在 2021 年 5 月 5 日将不再有效。 {% endif %}有关详细信息，包括预定的限电，请参阅[博客文章](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)。
 
-{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %}
+{% if enterpriseServersions contained currentVersion or currentVersion == "github-ae@latest" %} 使用查询参数向 API 验证仍然可用，但出于安全考虑不再支持。 相反，我们建议集成商在标头中移动其访问令牌 `client_id` 或 `client_secret`。 {% data variables.product.prodname_dotcom %} 将宣布删除通过查询参数进行身份验证，并且会提前通知。 {% endif %}
 
 {% endwarning %}
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/branches/set-default-branch.md b/translations/zh-CN/data/reusables/branches/set-default-branch.md
index d4ca85049c..8faac7b12d 100644
--- a/translations/zh-CN/data/reusables/branches/set-default-branch.md
+++ b/translations/zh-CN/data/reusables/branches/set-default-branch.md
@@ -1 +1 @@
-您可以为新仓库设置默认分支名称。 For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)," "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)," and {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)."{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)."{% endif %}
+您可以为新仓库设置默认分支名称。 更多信息请参阅“[管理仓库的默认分支](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)”、“[管理组织中仓库的默认分支](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”和 {% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施仓库管理策略](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)”。{% else %}“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)”。{% endif %}
diff --git a/translations/zh-CN/data/reusables/cli/actions-cli-version.md b/translations/zh-CN/data/reusables/cli/actions-cli-version.md
new file mode 100644
index 0000000000..956dcc250b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/cli/actions-cli-version.md
@@ -0,0 +1 @@
+要访问所有与 {% data variables.product.prodname_actions %} 相关的命令，您必须使用版本 1.9.0 或更高版本。
diff --git a/translations/zh-CN/data/reusables/cli/cli-auth.md b/translations/zh-CN/data/reusables/cli/cli-auth.md
new file mode 100644
index 0000000000..738d9787cf
--- /dev/null
+++ b/translations/zh-CN/data/reusables/cli/cli-auth.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} 可以使用您的 {% data variables.product.prodname_dotcom %} 帐户进行身份验证。 在运行 {% data variables.product.prodname_cli %} 命令之前，您需要通过运行 `gh auth login` 进行身份验证。 有关命令行身份验证的更多信息，请参阅 "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)"。
diff --git a/translations/zh-CN/data/reusables/cli/cli-manual.md b/translations/zh-CN/data/reusables/cli/cli-manual.md
new file mode 100644
index 0000000000..615b177b27
--- /dev/null
+++ b/translations/zh-CN/data/reusables/cli/cli-manual.md
@@ -0,0 +1 @@
+有关 {% data variables.product.prodname_cli %} 的更多信息，请参阅 [{% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/)。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/cli/cli-repo.md b/translations/zh-CN/data/reusables/cli/cli-repo.md
new file mode 100644
index 0000000000..72cb97ead3
--- /dev/null
+++ b/translations/zh-CN/data/reusables/cli/cli-repo.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_cli %} 命令必须在要与之交互的仓库内运行，因此您必须先导航到包含仓库本地副本的目录。 或者，您可以通过传递 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}`-R HOSTNAME/OWNER/REPOSITORY` 或 `--repo HOSTNAME/OWNER/REPOSITORY`{% else %}`-R OWNER/REPOSITORY` 或 `--repo OWNER/REPOSITORY`{% endif %} 来指定仓库。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}将 `HOSTNAME` 替换为 {% data variables.product.product_location %} 的名称。 {% endif %}将 `OWNER` 替换为仓库所有者。 将 `REPOSITORY` 替换为仓库名称。
diff --git a/translations/zh-CN/data/reusables/cli/download-update-cli.md b/translations/zh-CN/data/reusables/cli/download-update-cli.md
new file mode 100644
index 0000000000..f9f0ebc3c1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/cli/download-update-cli.md
@@ -0,0 +1 @@
+要下载或升级 {% data variables.product.prodname_cli %}，请遵循 [{% data variables.product.prodname_cli %} 自述文件](https://github.com/cli/cli#installation)中的说明。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..5936d964b2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,7 @@
+<!-- If you update the list of supported languages for CodeQL, update /github/getting-started-with-github/github-language-support to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python
diff --git a/translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..9e1a3f8256
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`、`csharp`、`go`、`java`、`javascript` 和 `python`。
diff --git a/translations/zh-CN/data/reusables/code-scanning/enabling-options.md b/translations/zh-CN/data/reusables/code-scanning/enabling-options.md
index daae4bac93..d6c0303885 100644
--- a/translations/zh-CN/data/reusables/code-scanning/enabling-options.md
+++ b/translations/zh-CN/data/reusables/code-scanning/enabling-options.md
@@ -11,21 +11,18 @@
   
   <tr>
     <td>
-      {% data variables.product.prodname_codeql %}
     </td>
     
     <td>
-      使用 {% data variables.product.prodname_actions %}（请参阅“<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">使用操作设置 {% data variables.product.prodname_code_scanning %}</a>”）或使用第三方持续集成 (CI) 系统中的 {% data variables.product.prodname_codeql_runner %}（请参阅“<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system">在 CI 系统中运行 {% data variables.product.prodname_codeql %}</a>”）。
-    </td>
-  </tr>
-  
-  <tr>
-    <td>
-      第三方
-    </td>
-    
-    <td>
-      使用 {% data variables.product.prodname_actions %}（请参阅“<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">使用操作设置 {% data variables.product.prodname_code_scanning %}</a>”）或在外部生成并上传到 {% data variables.product.product_name %}（请参阅“<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">将 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}</a>”）。
     </td>
   </tr>
 </table>
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+|
+{% data variables.product.prodname_codeql %} | 使用 {% data variables.product.prodname_actions %}（请参阅“[使用操作设置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)”）或在第三方持续集成 (CI) 系统中运行 {% data variables.product.prodname_codeql %} 分析（请参阅“[关于 CI 系统中的 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)”）。
+{%- else %}
+|
+{% data variables.product.prodname_codeql %} | 使用 {% data variables.product.prodname_actions %}（请参阅“[使用操作设置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)”）或使用第三方持续集成 (CI) 系统中的 {% data variables.product.prodname_codeql_runner %}（请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql %} 代码扫码](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”）。
+{%- endif %}
+| 第三&#8209;方 | 使用
+{% data variables.product.prodname_actions %}（请参阅“[使用操作设置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)”）或在外部生成并上传到 {% data variables.product.product_name %}（请参阅“[将 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)”）。|
diff --git a/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md
index 7d4bbf6eff..883fcaf72d 100644
--- a/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**注：** SAIF 上传支持每次上传最多 1000 个结果。 超过此限制的任何结果均被忽略。 如果工具产生太多结果，则应更新配置，以专注于最重要的规则或查询的结果。
+**注：**SARIF 上传支持每次上传最多 {% if currentVersion == "github-ae@next" or currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}5000{% else %}1000{% endif %} 个结果。 超过此限制的任何结果均被忽略。 如果工具产生太多结果，则应更新配置，以专注于最重要的规则或查询的结果。
 
 {% endnote %}
diff --git a/translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..fb2e63ad93
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
+
+{% note %}
+
+**注：**上传 SARIF 数据以显示为 {% data variables.product.product_name %} 中的 {% data variables.product.prodname_code_scanning %} 结果适用于启用了 {% data variables.product.prodname_GH_advanced_security %} 的组织拥有的仓库{% if currentVersion == "free-pro-team@latest" %}和 {% data variables.product.prodname_dotcom_the_website %} 上的公共仓库{% endif %}。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..6a2dd745e1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1,3 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+{% data variables.product.prodname_codeql_cli %} 是一个可用来分析代码的独立产品。 其主要用途是生成代码空间的数据库表示形式，即 {% data variables.product.prodname_codeql %} 数据库。 数据库准备就绪后，您可以进行交互式查询，或者运行一系列查询以生成一组 SARIF 格式的结果，然后将结果上传到 {% data variables.product.product_location %}。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/codespaces/about-personalization.md b/translations/zh-CN/data/reusables/codespaces/about-personalization.md
index 5bd8f40144..d761204b51 100644
--- a/translations/zh-CN/data/reusables/codespaces/about-personalization.md
+++ b/translations/zh-CN/data/reusables/codespaces/about-personalization.md
@@ -1 +1 @@
-也可为您的帐户创建的任何代码空间个性化代码空间环境的各个方面。 个性化可以包括 shell 首选项和其他工具。
+您还可以使用 [dotfiles](https://dotfiles.github.io/tutorials/) 仓库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来针对您创建的任何代码空间而个性化代码空间环境的各个方面。 个性化可以包括 shell 首选项和其他工具。
diff --git a/translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md b/translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..3befc07c9d
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1 @@
+您可以转发代码空间中的端口以测试和调试应用程序。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md
new file mode 100644
index 0000000000..a60d164f36
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md
@@ -0,0 +1 @@
+在仓库的 {% data variables.product.prodname_codespaces %} 配置更改后，您可以通过重建代码空间的容器来将更改应用于现有代码空间。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index 157489ba84..c9ee5e8bfe 100644
--- a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1 +1 @@
-1. 在 {% data variables.product.prodname_vscode %} 中，从左侧边栏单击 Remote Explorer 图标。 ![{% data variables.product.prodname_vscode %} 中的 Remote Explorer 图标](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+1. 在 {% data variables.product.prodname_vscode %} 中，从左侧边栏单击 Remote Explorer 图标。 ![{% data variables.product.prodname_vscode %} 中的 Remote Explorer 图标](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md b/translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..3790918bb6
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+您可以在三种类型的远程机器上运行代码空间：基本、标准或高级。 每种类型都有不同的资源水平和不同的计费等级。<!-- For information, see "\[About billing for Codespaces\](/github/developing-online-with-codespaces/about-billing-for-codespaces)." -->{% note %}
+
+**注：**{% data reusables.codespaces.about-billing-for-codespaces %}
+
+{% endnote %}
+
+切换机器类型使您可以灵活地选择最适合您工作的资源。 某些任务可能需要不同的机器类型：
+
+* **基本**，适用于更新文件和提出拉取请求
+* **标准**，适用于编辑网站
+* **高级**，适用于数据分析等高计算任务
diff --git a/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md b/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..90ff81bb48
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,3 @@
+在对代码空间进行更改（无论是添加新代码还是更改配置）之后，您需要提交更改。 将更改提交到仓库可确保从此仓库创建代码空间的其他任何人都具有相同的配置。 This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users.
+
+For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..f0295e7701
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1 @@
+1. 在代码空间中的文本编辑器下，单击“Ports（端口）”。 ![端口选项卡](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/zh-CN/data/reusables/codespaces/rebuild-command.md b/translations/zh-CN/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..71e4f05ade
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1 @@
+访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "Codespaces: Rebuild Container"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/recovery-mode.md b/translations/zh-CN/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..f2b5bae88a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1 @@
+如果对代码空间的配置的更改导致容器错误，则代码空间将在恢复模式下运行，并且您将看到错误消息。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/release-stage.md b/translations/zh-CN/data/reusables/codespaces/release-stage.md
index 19663149e6..3220d5951c 100644
--- a/translations/zh-CN/data/reusables/codespaces/release-stage.md
+++ b/translations/zh-CN/data/reusables/codespaces/release-stage.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**注：**{% data variables.product.prodname_codespaces %} 目前是有限公测版，可能会有变动。 在公测期间，{% data variables.product.prodname_dotcom %} 不对 {% data variables.product.prodname_codespaces %} 的可用性做任何保证。 有关加入公测的更多信息，请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)”。
+**注：**{% data variables.product.prodname_codespaces %} 目前是有限公测版，可能会有变动。 有关加入公测的更多信息，请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)”。
 
 {% endnote %}
diff --git a/translations/zh-CN/data/reusables/codespaces/secret-precedence.md b/translations/zh-CN/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..759d24005c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1 @@
+如果具有相同名称的机密存在于多个级别，则较低级别的机密优先。 For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/secrets-naming.md b/translations/zh-CN/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..a1a55d82be
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,7 @@
+以下规则适用于密码名称：
+
+* 密码名称只能包含字母数字字符（`[a-z]`、`[A-Z]`、`[0-9]`）或下划线 (`_`)。 不允许空格。
+* 密码名称不能以 `GITHUB_` 前缀开头。
+* 密码名称不能以数字开头。
+* 机密名称不区分大小写。
+* 密码名称在所创建的级别上必须是唯一的。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/secrets-on-start.md b/translations/zh-CN/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..c4a5bf3b41
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md b/translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..d70b9ac93e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1 @@
+1. 在活动栏中，单击 **Source Control（源控制）**视图。 ![源控制视图](/assets/images/help/codespaces/source-control-activity-bar-button.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/source-control-display.md b/translations/zh-CN/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..e2a8cb8c77
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,3 @@
+1. 在活动栏中，单击 **Source Control（源控制）**视图。
+
+  ![源控制视图](/assets/images/help/codespaces/codespaces-commit-activity.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/type-port-label.md b/translations/zh-CN/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..150b8007e4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1 @@
+1. 键入端口的标签，然后按 enter。 ![输入端口标签的文本框](/assets/images/help/codespaces/label-text-box.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md
index 89ca2ae45c..7ed08ce28a 100644
--- a/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md
+++ b/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -1 +1 @@
-在 [github.com/codespaces](https://github.com/codespaces)上可以查看您的用户帐户拥有的每个代码空间。
+您可以在 [github.com/codespaces](https://github.com/codespaces) 上查看您创建的每一个可用代码空间。
diff --git a/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..1d02c80a2e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,3 @@
+1. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Your codespaces（您的代码空间）**。
+
+  ![“您的代码空间”菜单选项](/assets/images/help/codespaces/your-codespaces-option.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md
index 58e340711a..e624b1e7e5 100644
--- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md
@@ -11,7 +11,7 @@
 | Composer       | `composer`       | v1, v2                 | **✓** | **✓** |       |
 | Docker         | `docker`         | v1                     | **✓** | **✓** |       |
 | Hex            | `混合`             | v1                     |       | **✓** |       |
-| elm-package    | `elm`            | v0.18, v0.19           | **✓** | **✓** |       |
+| elm-package    | `elm`            | v0.19                  | **✓** | **✓** |       |
 | git submodule  | `gitsubmodule`   | N/A（无版本）               | **✓** | **✓** |       |
 | GitHub Actions | `github-actions` | N/A（无版本）               | **✓** | **✓** |       |
 | Go 模块          | `gomod`          | v1                     | **✓** | **✓** | **✓** |
diff --git a/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md
index 33b34c6d0f..3c5db28ab8 100644
--- a/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md
+++ b/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -10,6 +10,10 @@
 
 默认情况下，工作流程不在复刻仓库上运行。 您必须在复刻仓库的 **Actions（操作）**选项卡中启用 GitHub Actions。
 
+{% if currentVersion == "free-pro-team@latest"%}
+当贡献者第一次向公共仓库提交拉取请求时，拥有写入权限的维护者必须批准拉取请求上运行的工作流程。 更多信息请参阅“[批准公共复刻中的工作流程运行](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks)”。
+{% endif %}
+
 {% data reusables.actions.forked-secrets %} 对复刻仓库中 `GITHUB_TOKEN` 的权限是只读的。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
 
 {% note %}
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download.md
index 0fa8c4c5c4..5f99ef099a 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -1 +1 @@
-1. （可选）单击 **Get usage report（获取使用报告）**向帐户主电子邮件地址发送关于 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 存储使用情况的 CSV 报告。 ![下载 CSV 报告](/assets/images/help/billing/actions-packages-report-download.png)
+1. （可选）在“Usage this month（本月使用情况）”旁边，单击 **Get usage report（获取使用报告）**向帐户主电子邮件地址发送关于 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 存储使用情况的 CSV 报告。 ![下载 CSV 报告](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/change_plan_duration.md b/translations/zh-CN/data/reusables/dotcom_billing/change_plan_duration.md
index 49af88a9e9..bf3a49d827 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/change_plan_duration.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/change_plan_duration.md
@@ -1 +1 @@
-1. 在“Billing overview（帐单概览）”下，单击 **Change to yearly billing（切换至年度帐单）**或 **Change to monthly billing（切换至月度帐单）**。 ![帐单概览更改计划按钮](/assets/images/help/billing/change-plan-duration-link.png)
+1. 在“Current monthly bill（本月帐单）”或“Current yearly bill（本年帐单）”下，单击 **Change to yearly billing（切换至年度帐单）**或 **Change to monthly billing（切换至月度帐单）**。 ![帐单概览更改计划按钮](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/choose_org_plan.md b/translations/zh-CN/data/reusables/dotcom_billing/choose_org_plan.md
index 830c60c8d8..812403272e 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/choose_org_plan.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/choose_org_plan.md
@@ -1 +1 @@
-1. 如果从 {% data variables.product.prodname_free_team %} 升级，在“Upgrading to（升级到）”下选择一个产品。 ![升级按钮](/assets/images/help/billing/upgrade-to-product.png)
+1. 在“Compare plans（比较计划）”下，您可以比较每个计划的功能。 根据您当前的计划和您选择的计划，单击 **Upgrade to Team（升级到团队）**或 **Upgrade to Enterprise（升级到企业）**。 ![比较计划和升级](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/enter-payment-info.md b/translations/zh-CN/data/reusables/dotcom_billing/enter-payment-info.md
index 252faed642..b52c9a2746 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/enter-payment-info.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/enter-payment-info.md
@@ -1,2 +1,2 @@
-1. 在“Billing information（帐单信息）”下，选择使用信用卡或 PayPal 支付。 ![切换帐单支付方式](/assets/images/help/billing/billing_switch_payments.png)
+1. 在“Payment method（付款方式）”下，选择使用信用卡或 PayPal 支付。 ![切换帐单支付方式](/assets/images/help/billing/billing_switch_payments.png)
 1. 填写付款信息表，然后单击 **Submit（提交）**。
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/lfs-add-data.md b/translations/zh-CN/data/reusables/dotcom_billing/lfs-add-data.md
index ff35484483..3698fa721d 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/lfs-add-data.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/lfs-add-data.md
@@ -1 +1 @@
-1. 在"{% data variables.large_files.product_name_short %} 数据"旁边，单击 **Add more data（添加更多数据）**或使用 Edit（编辑）下拉菜单，然后单击 **Add more data packs（添加更多数据包）**。 ![添加更多数据按钮](/assets/images/help/billing/data-pack-purchase-more.png)
+1. 在"{% data variables.large_files.product_name_short %} 数据"旁边，单击 **Add more data（添加更多数据）**或使用 **Edit（编辑）**下拉菜单，然后单击 **Add more data packs（添加更多数据包）**。 ![添加更多数据按钮](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/zh-CN/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..4d105de9f4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1 @@
+1. 在页面顶部的“Payment information（付款信息）”下，单击 **Manage spending limit（管理支出限制）**。 ![管理支出限制链接](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/next_billing_date.md b/translations/zh-CN/data/reusables/dotcom_billing/next_billing_date.md
index 1430194a92..63cfa523c6 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/next_billing_date.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/next_billing_date.md
@@ -1 +1 @@
-1. 在“Billing overview（帐单概览）”下，查看下次付款到期时间。 ![下一个帐单日期](/assets/images/help/billing/settings_billing_next_payment.png)
+1. 在页面顶部的“Next payment due（下一次付款到期）”下，检查下次付款何时到期。 ![下一个帐单日期](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/review-pending-changes.md b/translations/zh-CN/data/reusables/dotcom_billing/review-pending-changes.md
index fa18595f2e..a5cfd047bb 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/review-pending-changes.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/review-pending-changes.md
@@ -1 +1 @@
-1. 在“Subscriptions（订阅）”下，审查您的待定更改。 ![帐单设置的订阅部分会列出任何待定订阅更改](/assets/images/help/billing/review-pending-subscription-changes.png)
+1. 在“Current plan（当前计划）”下，审查您的待定更改。 ![帐单设置的订阅部分会列出任何待定订阅更改](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/update_payment_method.md b/translations/zh-CN/data/reusables/dotcom_billing/update_payment_method.md
index 1dc9b88f56..9d36e0d26b 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/update_payment_method.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/update_payment_method.md
@@ -1 +1 @@
-1. 在“Billing overview（帐单概览）”下，单击 **Update payment method（更新付款方式）**。 ![Update payment method（更新付款方式）按钮](/assets/images/help/billing/update_payment_method.png)
+1. 在页面顶部的在“Payment information（付款信息）”下，单击 **Update payment method（更新付款方式）**。 ![Update payment method（更新付款方式）按钮](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/upgrade_org.md b/translations/zh-CN/data/reusables/dotcom_billing/upgrade_org.md
index 2d5e2486dc..c07aac572c 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/upgrade_org.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/upgrade_org.md
@@ -1 +1 @@
-1. 如果您要从 {% data variables.product.prodname_free_team %} 升级，请单击 **Upgrade options（升级选项）**。 如果您要从 {% data variables.product.prodname_team %} 升级，请使用 **Edit（编辑）**下拉菜单，然后单击 **Upgrade（升级）**。 ![升级选项按钮](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
+1. 单击“ Current plan（当前计划）”旁边的 **Upgrade（升级）**。
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/view-payment-history.md b/translations/zh-CN/data/reusables/dotcom_billing/view-payment-history.md
index 6aa5297023..ff8ec38a02 100644
--- a/translations/zh-CN/data/reusables/dotcom_billing/view-payment-history.md
+++ b/translations/zh-CN/data/reusables/dotcom_billing/view-payment-history.md
@@ -1 +1 @@
-1. 在“Billing overview（帐单概览）”下，单击 **View payment history（查看付款历史记录）**。 ![查看付款历史记录链接](/assets/images/help/billing/view-payment-history-link.png)
+1. 在页面顶部的“Next payment due（下次付款到期时间）”下，单击 **View payment history（查看付款历史记录）**。 ![查看付款历史记录链接](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/add-a-domain.md b/translations/zh-CN/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..f267fc93f0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1 @@
+1. 单击 **Add a domain（添加域）**。 ![添加域按钮](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..69bac4cd81
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1 @@
+If you want to allow members to receive email notifications at a domain you don't own, you can approve the domain, then allow {% data variables.product.prodname_dotcom %} to send email notifications to addresses within the domain. For example, you can allow a contractor who doesn't have an email address within your own domain to receive email notifications at a domain you feel comfortable with.
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..6b7ba3162e
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+{% note %}
+
+**Note**: Domain approval is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/zh-CN/data/reusables/enterprise-accounts/domains-about-approval.md
new file mode 100644
index 0000000000..fa9ad29df1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/domains-about-approval.md
@@ -0,0 +1,13 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your enterprise account, you can restrict email notifications for activity within your enterprise account to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。
+
+Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+
+Organization owners can also approve additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/zh-CN/data/reusables/enterprise-accounts/domains-about-verification.md
new file mode 100644
index 0000000000..73ef0801ed
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/domains-about-verification.md
@@ -0,0 +1,11 @@
+您可以通过验证域，确认企业控制的企业帐户所拥有的任何组织资料中列出的网站和电子邮件地址。 Verified domains for an enterprise account apply to every organization owned by the enterprise account.
+
+验证企业帐户域的所有权后，每个在其资料中列出域的组织资料中将显示"已验证"徽章。 {% data reusables.organizations.verified-domains-details %}
+
+组织所有者将能够通过查看已验证域中的每个成员的电子邮件地址来验证组织成员的身份。
+
+验证企业帐户的域后，您可以将企业帐户拥有的所有组织的电子邮件通知限制为已验证域。 For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."
+
+Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications at any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Organization owners can also verify additional domains for their organizations. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/domains-approving.md b/translations/zh-CN/data/reusables/enterprise-accounts/domains-approving.md
new file mode 100644
index 0000000000..188594d654
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/domains-approving.md
@@ -0,0 +1,9 @@
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/domains-removing.md b/translations/zh-CN/data/reusables/enterprise-accounts/domains-removing.md
new file mode 100644
index 0000000000..063a655c33
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/domains-removing.md
@@ -0,0 +1,4 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/domains-verifying.md b/translations/zh-CN/data/reusables/enterprise-accounts/domains-verifying.md
new file mode 100644
index 0000000000..2143c55630
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/domains-verifying.md
@@ -0,0 +1,15 @@
+要验证企业帐户的域，您必须具有使用域托管服务修改域记录的权限。
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.enterprise-accounts.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. 等待 DNS 配置更改，最多可能需要 72 小时。 您可以通过在命令行上运行 `dig` 命令来确认您的 DNS 配置已更改，将 `ENTERPRISE-ACCOUNT` 替换为您企业帐户的名称，将 `example.com` 替换为要验证的域。 您应看到命令输出中列出的新 TXT 记录。
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+1. （可选）组织的资料上显示“Verified（已验证）”徽章后，从域托管服务的 DNS 记录中删除 TXT 条目。 ![已验证徽章](/assets/images/help/organizations/verified-badge.png)
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-about.md
new file mode 100644
index 0000000000..dc6af33613
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-about.md
@@ -0,0 +1,9 @@
+When you restrict email notifications, enterprise members can only use an email address in a verified or approved domain to receive email notifications about activity in organizations owned by your enterprise account.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+可以从企业帐户继承域，也可以为特定组织配置域。 For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+如果对企业帐户启用了电子邮件限制，则组织所有者无法禁用该企业帐户拥有的任何组织的电子邮件限制。 If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-restricting.md
new file mode 100644
index 0000000000..6ac3287e50
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/email-restrictions-restricting.md
@@ -0,0 +1,7 @@
+Before you can restrict email notifications for your enterprise account, you must verify or approve at least one domain for the enterprise account. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+{% data reusables.organizations.restrict-email-notifications %}
+1. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md
index 6f35bb03df..67158a9e51 100644
--- a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md
@@ -1 +1 @@
-{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServersions contained currentversion or currentversion == "free promo-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。
+{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServersions contained currentVersion or currentVersion == "free promo-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/verified-domains-tab.md
index 5f2b524453..85644af45c 100644
--- a/translations/zh-CN/data/reusables/enterprise-accounts/verified-domains-tab.md
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -1 +1 @@
-1. 在“Settings（设置）”下，单击 **Verified domains（已验证的域名）**。 !["已验证的域名"选项卡](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
+1. Under "Settings", click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/enterprises/verified-domains-tab.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/zh-CN/data/reusables/enterprise_deprecation/deprecation_details.md
index bd98744536..08b5c24e83 100644
--- a/translations/zh-CN/data/reusables/enterprise_deprecation/deprecation_details.md
+++ b/translations/zh-CN/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -1 +1 @@
-即使针对重大安全问题，也不会发布补丁。 要获得更好的性能、改进的安全性和新功能，<a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'upgrade-link']);">请升级到 GitHub Enterprise 的最新版本</a>。 如需升级方面的帮助，<a href="https://enterprise.github.com/support" onClick="_gaq.push(['_trackEvent', 'Help Deprecation Notice', 'Click', 'contact-support']);">请联系 GitHub Enterprise 支持</a>。
+即使针对重大安全问题，也不会发布补丁。 要获得更好的性能、改进的安全性和新功能，<a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">请升级到 GitHub Enterprise 的最新版本</a>。 如需升级方面的帮助，<a href="https://enterprise.github.com/support">请联系 GitHub Enterprise 支持</a>。
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md
index 7654a52a92..abc68e0a99 100644
--- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md
+++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md
@@ -1,4 +1,4 @@
-- [最低要求](#minimum-requirements){% if currentversion == "enterprise-server@2.22" %}
+- [最低要求](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %}
 - [{% data variables.product.prodname_ghe_server %} 2.22 中的测试功能](#beta-features-in-github-enterprise-server-222){% endif %}
 - [存储器](#storage)
 - [CPU 和内存](#cpu-and-memory)
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md b/translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
new file mode 100644
index 0000000000..a19af3e7f2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md
@@ -0,0 +1,25 @@
+{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
+
+### 关于 {% data variables.product.prodname_ghe_server %} 3.0 及更高版本的最低要求
+
+升级到 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本之前，请检查您为实例预配的硬件资源。 {% data variables.product.prodname_ghe_server %} 3.0 引入了 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 等新功能，比 2.22 和更早版本需要更多的资源。 更多信息请参阅 [{% data variables.product.prodname_ghe_server %} 3.0 发行说明](/enterprise-server@3.0/admin/release-notes)。
+
+{% data variables.product.prodname_ghe_server %} 3.0 及更高版本的增加要求在下表中以**粗体**表示。
+
+| 用户许可              |                            vCPU |                                      内存 |                                 附加的存储容量 |  根存储容量 |
+|:----------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------:|
+| 试用版、演示版或 10 个轻度用户 |   **4**<br/>_Up from 2_ |   **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ | 200 GB |
+| 10-3000           |   **8**<br/>_Up from 4_ |   **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ | 200 GB |
+| 3000-5000         |  **12**<br/>_Up from 8_ |                                   64 GB |                                  500 GB | 200 GB |
+| 5000-8000         | **16**<br/>_Up from 12_ |                                   96 GB |                                  750 GB | 200 GB |
+| 8000-10000+       | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ |                                 1000 GB | 200 GB |
+
+{% if currentVersion ver_gt "enterprise-server@2.21" %}
+
+有关 {% data variables.product.prodname_actions %} 硬件要求的详细信息，请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)”。
+
+{% endif %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md
index a82992ae56..48d44c8c9e 100644
--- a/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md
+++ b/translations/zh-CN/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**警告**：更改此设置将导致 {% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} 重启。 您应谨慎安排更改时间，以尽量减少停机时间。
+**警告**：更改此设置将导致 {% data variables.product.prodname_ghe_server %} 上面向用户的服务重新启动。 您应谨慎安排更改时间，以尽量减少用户的停机时间。
 
 {% endwarning %}
diff --git a/translations/zh-CN/data/reusables/gated-features/actions-shared.md b/translations/zh-CN/data/reusables/gated-features/actions-shared.md
index 55832340ac..aeb154cc41 100644
--- a/translations/zh-CN/data/reusables/gated-features/actions-shared.md
+++ b/translations/zh-CN/data/reusables/gated-features/actions-shared.md
@@ -1 +1 @@
-{% data variables.product.prodname_actions %} 可用于 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、组织的 {% data variables.product.prodname_free_team %}，{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %} 、{% data variables.product.prodname_ghe_one %} 及 {% data variables.product.prodname_ghe_managed %}。 {% data variables.product.prodname_actions %} 不适用于使用旧版按仓库计划的帐户所拥有的私有仓库。 
+{% data variables.product.prodname_actions %} 可用于 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、组织的 {% data variables.product.prodname_free_team %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_managed %}。 {% data variables.product.prodname_actions %} 不适用于使用旧版按仓库计划的帐户所拥有的私有仓库。 
diff --git a/translations/zh-CN/data/reusables/gated-features/code-scanning.md b/translations/zh-CN/data/reusables/gated-features/code-scanning.md
index e6bff5cfbb..5518fff7f2 100644
--- a/translations/zh-CN/data/reusables/gated-features/code-scanning.md
+++ b/translations/zh-CN/data/reusables/gated-features/code-scanning.md
@@ -1,5 +1,5 @@
 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} 适用于所有公共仓库以及启用了 {% data variables.product.prodname_GH_advanced_security %} 的组织拥有的私有仓库。
-{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} 在对仓库启用了 {% data variables.product.prodname_GH_advanced_security %} 时可用。
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %} 适用于启用了 {% data variables.product.prodname_GH_advanced_security %} 的组织拥有的仓库。
 {%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_code_scanning_capc %} 可用作 {% data variables.product.prodname_GH_advanced_security %} 的一部分，在测试期间免费使用。
 {%- else %}
diff --git a/translations/zh-CN/data/reusables/gated-features/ghas.md b/translations/zh-CN/data/reusables/gated-features/ghas.md
index d8dc3d1162..b151afaae1 100644
--- a/translations/zh-CN/data/reusables/gated-features/ghas.md
+++ b/translations/zh-CN/data/reusables/gated-features/ghas.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} 许可证可用于 {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_server %} 上的企业帐户。 {% data variables.product.prodname_GH_advanced_security %} 也包含在 {% data variables.product.prodname_ghe_one %}{% if currentVersion == "free-pro-team@latest" %} 以及 {% data variables.product.prodname_dotcom_the_website %}{% endif %} 上的所有公共仓库中。 更多信息请参阅“[关于 GitHub 的产品](/github/getting-started-with-github/githubs-products)”。
\ No newline at end of file
+{% data variables.product.prodname_GH_advanced_security %} 许可适用于 {% data variables.product.prodname_ghe_cloud %}{% if currentVersion == "github-ae@latest" %}、{% data variables.product.prodname_ghe_managed %}{% endif %} 和 {% data variables.product.prodname_ghe_server %} 上的企业帐户。{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_GH_advanced_security %} 也包含在 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共仓库中。{% endif %}更多信息请参阅“[关于 GitHub 的产品](/github/getting-started-with-github/githubs-products)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/gated-features/github-insights.md b/translations/zh-CN/data/reusables/gated-features/github-insights.md
index aee41905dc..05e7933a10 100644
--- a/translations/zh-CN/data/reusables/gated-features/github-insights.md
+++ b/translations/zh-CN/data/reusables/gated-features/github-insights.md
@@ -1 +1 @@
-{% data variables.product.prodname_insights %} 可用于 {% data variables.product.prodname_ghe_one %}。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。
+{% data variables.product.prodname_insights %} 可用于 {% data variables.product.prodname_ghe_one %}。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/gated-features/packages.md b/translations/zh-CN/data/reusables/gated-features/packages.md
index 3d52092bf8..8017cc4089 100644
--- a/translations/zh-CN/data/reusables/gated-features/packages.md
+++ b/translations/zh-CN/data/reusables/gated-features/packages.md
@@ -1,5 +1,5 @@
-{% data variables.product.prodname_registry %} 可用于 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、组织的 {% data variables.product.prodname_free_team %}，{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %} 2.22、{% data variables.product.prodname_ghe_one %} 及 {% data variables.product.prodname_ghe_managed %}。
+{% data variables.product.prodname_registry %} 可用于 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、组织的 {% data variables.product.prodname_free_team %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_managed %}。
 {% if currentVersion == "free-pro-team@latest" %}
 <br>
-{% data variables.product.prodname_registry %} 不适用于使用旧版按仓库计划的帐户所拥有的私有仓库。 {% data variables.product.prodname_registry %} 可用于 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、组织的 {% data variables.product.prodname_free_team %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_one %}。 {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_registry %} 不适用于使用旧版按仓库计划的帐户所拥有的私有仓库。 此外，使用旧版按仓库计划的帐户无法访问 {% data variables.product.prodname_container_registry %}，因为这些帐户是按仓库计费的。 {% data reusables.gated-features.more-info %}
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/gated-features/pages.md b/translations/zh-CN/data/reusables/gated-features/pages.md
index f3410c13ed..21bfb6507f 100644
--- a/translations/zh-CN/data/reusables/gated-features/pages.md
+++ b/translations/zh-CN/data/reusables/gated-features/pages.md
@@ -1 +1 @@
-{% if currentversion == "github-ae@latest" %}{% data variables.product.prodname_pages %} 适用于具有 {% data variables.product.prodname_ghe_managed %} 的内部和私有仓库。 {% endif %}{% data variables.product.prodname_pages %} 适用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %} 的公共仓库，以及具有 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
+{% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_pages %} 适用于具有 {% data variables.product.prodname_ghe_managed %} 的内部和私有仓库。 {% endif %}{% data variables.product.prodname_pages %} 适用于具有 {% data variables.product.prodname_free_user %} 和组织的 {% data variables.product.prodname_free_team %} 的公共仓库，以及具有 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、{% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %} 的公共和私有仓库。 {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/zh-CN/data/reusables/gated-features/secret-scanning.md b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md
index 707e4a08cf..e804bdad2e 100644
--- a/translations/zh-CN/data/reusables/gated-features/secret-scanning.md
+++ b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md
@@ -1,7 +1,6 @@
-{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
-{% data variables.product.prodname_secret_scanning_caps %} 可用于{% if currentVersion == "free-pro-team@latest" %}公共仓库，以及具有{% else %}您有{% endif %} {% data variables.product.prodname_advanced_security %} 许可的组织拥有的私有仓库。 {% data reusables.advanced-security.more-info-ghas %}
-{% endif %}
-
-{% if currentVersion == "github-ae@latest" %}
+{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_secret_scanning_caps %} 适用于所有公共仓库以及启用了 {% data variables.product.prodname_GH_advanced_security %} 的组织拥有的私有仓库。
+{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_secret_scanning_caps %} 适用于启用了 {% data variables.product.prodname_GH_advanced_security %} 的组织拥有的仓库。
+{%- elsif currentVersion == "github-ae@latest" %}
 {% data variables.product.prodname_secret_scanning_caps %} 可用作 {% data variables.product.prodname_GH_advanced_security %} 的一部分，在测试期间免费使用。
-{% endif %}
\ No newline at end of file
+{%- else %}
+{% data variables.product.prodname_secret_scanning_caps %} 在您拥有 {% data variables.product.prodname_GH_advanced_security %} 的许可证时可用。{% endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/forked-write-permission.md b/translations/zh-CN/data/reusables/github-actions/forked-write-permission.md
new file mode 100644
index 0000000000..6aa1249c51
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/forked-write-permission.md
@@ -0,0 +1 @@
+您可以使用 `permissions` 键来添加和删除复刻仓库的读取权限，但通常不能授予写入权限。 此行为的例外情况是，管理员在 {% data variables.product.prodname_actions %} 设置中选择了 **Send write tokens to workflows from pull requests（从拉取请求发送写入令牌到工作流程）**选项。 更多信息请参阅“[禁用或限制仓库的 {% data variables.product.prodname_actions %}](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)”。
\ No newline at end of file
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
new file mode 100644
index 0000000000..45ea675286
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/github-token-available-permissions.md
@@ -0,0 +1,23 @@
+可用的作用域和访问权限值：
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none
+  issues: read|write|none
+  packages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+如果您指定其中任何作用域的访问权限，则所有未指定的作用域都被设置为 `none`。
+
+您可以使用以下语法来定义所有可用作用域的读取或写入权限：
+
+```yaml
+permissions: read-all|write-all
+```
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/github-token-permissions.md b/translations/zh-CN/data/reusables/github-actions/github-token-permissions.md
new file mode 100644
index 0000000000..2bb7be7bd3
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/github-token-permissions.md
@@ -0,0 +1 @@
+每当工作流程中的作业开始时，都会将 `GITHUB_TOKEN` 密钥设置为仓库的访问令牌。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}您应该在工作流程文件中设置此访问令牌的权限，以授予 `contents` 范围的读取访问权限，并授予 `packages` 范围的写入访问权限。 {% else %}它对工作流程运行的仓库中的包具有读取和写入权限。 {% endif %} 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md
index 04aeb59a73..30481f3a32 100644
--- a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md
+++ b/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md
@@ -1 +1 @@
-运行 `mvn --batch-mode deploy` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。
+运行 `mvn --batch-mode deploy` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} `permissions` 键指定授予 `GITHUB_TOKEN` 的访问权限。{% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
index eba8f92c98..41f1b7367c 100644
--- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
+++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md
@@ -5,7 +5,7 @@
 
    **警告**
 
-   {% indented_data_reference site.data.reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
 
    更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
diff --git a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md b/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
index 9261101f5e..07da3d9dc3 100644
--- a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
+++ b/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md
@@ -1,8 +1,14 @@
+{% warning %}
+
+**警告**：Ubuntu 16.04 即将被启用。 如果您的任何工作流程使用 Ubuntu 16.04，请迁移到 Ubuntu 20.04 或 18.04。 更多信息请参阅[博客帖子](https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021)。
+
+{% endwarning %}
+
 | 虚拟环境                 | YAML 工作流程标签                       |
 | -------------------- | --------------------------------- |
 | Windows Server 2019  | `windows-latest` 或 `windows-2019` |
+| Windows Server 2016  | `windows-2016`                    |
 | Ubuntu 20.04         | `ubuntu-latest` 或 `ubuntu-20.04`  |
 | Ubuntu 18.04         | `ubuntu-18.04`                    |
-| Ubuntu 16.04         | `ubuntu-16.04`                    |
 | macOS Big Sur 11.0   | `macos-11.0`                      |
 | macOS Catalina 10.15 | `macos-latest` 或 `macos-10.15`    |
diff --git a/translations/zh-CN/data/reusables/github-actions/workflow-permissions-intro.md b/translations/zh-CN/data/reusables/github-actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..4b4a0973b8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/workflow-permissions-intro.md
@@ -0,0 +1 @@
+您可以设置授予 `GITHUB_TOKEN` 的默认权限。 有关 `GITHUB_TOKEN` 的更多信息，请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)”。 您可以选择一组有限的权限作为默认或权限设置。 
diff --git a/translations/zh-CN/data/reusables/github-actions/workflow-permissions-modifying.md b/translations/zh-CN/data/reusables/github-actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..17ae3a6688
--- /dev/null
+++ b/translations/zh-CN/data/reusables/github-actions/workflow-permissions-modifying.md
@@ -0,0 +1 @@
+任何拥有仓库写入权限的人都可以通过编辑工作流程文件中的 `permissions` 键来修改授予 `GITHUB_TOKEN` 的权限，或者根据需要添加或删除权限。 更多信息请参阅 [`permissions`](/actions/reference/workflow-syntax-for-github-actions#permissions)。 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/verification-status-check.md b/translations/zh-CN/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..c659c27fcb
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1 @@
+您可以在 {% data variables.product.product_name %} 上检查已签名提交或标记的验证状态，并查看提交签名未验证的原因。 更多信息请参阅“[检查提交和标记签名验证状态](/articles/checking-your-commit-and-tag-signature-verification-status)”。
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..041b9c6101
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**注：**警戒模式目前处于测试阶段，可能会更改。
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..a623c3d060
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,5 @@
+| 状态             | 描述                                                                                                      |
+| -------------- | ------------------------------------------------------------------------------------------------------- |
+| **已验证**        | 提交已签名，签名已成功验证，并且提交者是启用警戒模式的唯一作者。                                                                        |
+| **部分&nbsp;验证** | 提交已签名，签名已成功验证，但提交的作者：a) 不是提交者，并且 b) 已启用警戒模式。 在这种情况下，提交签名并不保证作者的同意，因此提交只得到部分验证。                          |
+| **未验证**        | 适用于以下任何情况：<br>- 提交已签名，但无法验证签名。<br>- 提交未签名，提交者启用了警戒模式。<br>- 提交未签名，作者启用了警戒模式。<br> |
diff --git a/translations/zh-CN/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/zh-CN/data/reusables/marketplace/cancel-app-billing-settings.md
index c2a9365b91..8309dcc82d 100644
--- a/translations/zh-CN/data/reusables/marketplace/cancel-app-billing-settings.md
+++ b/translations/zh-CN/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -1 +1 @@
-1. 使用 **Edit（编辑）**下拉菜单并单击 **Cancel plan（取消计划）**。 ![个人帐户帐单设置中“市场购买”部分的 Cancel（取消）链接](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. 在要取消的应用程序旁边，使用 **Edit（编辑）**下拉菜单，然后单击 **Cancel plan（取消计划）**。 ![个人帐户帐单设置中“市场购买”部分的 Cancel（取消）链接](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/zh-CN/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/zh-CN/data/reusables/marketplace/cancel-free-trial-billing-settings.md
index eacce66fe2..9d9a86220f 100644
--- a/translations/zh-CN/data/reusables/marketplace/cancel-free-trial-billing-settings.md
+++ b/translations/zh-CN/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -1 +1 @@
-1. 在“Subscriptions（订阅）”下，在要取消的免费试用旁边，使用 Edit（编辑）下拉菜单并单击 **Cancel plan（取消计划）**。
+1. 在要取消的免费试用版旁边，使用 **Edit（编辑）**下拉菜单，然后单击 **Cancel plan（取消计划）**。
diff --git a/translations/zh-CN/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/zh-CN/data/reusables/marketplace/downgrade-app-billing-settings.md
index cb9658ab57..63f1093351 100644
--- a/translations/zh-CN/data/reusables/marketplace/downgrade-app-billing-settings.md
+++ b/translations/zh-CN/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -1 +1 @@
-1. 在“Your subscriptions（您的订阅）”下，在您想要降级的应用程序旁边，使用 Edit（编辑）下拉菜单，单击 **Change plan（更改计划）**或 **Cancel plan（取消计划）**。 ![个人帐户帐单设置中“市场购买”部分的 Edit（编辑）链接](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. 在要降级的应用程序旁边，使用 **Edit（编辑）**下拉菜单，然后单击 **Change plan（更改计划）**或 **Cancel plan（取消计划）**。 ![个人帐户帐单设置中“市场购买”部分的 Edit（编辑）链接](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/zh-CN/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/zh-CN/data/reusables/marketplace/upgrade-app-billing-settings.md
index e448e781c2..8f05b77df4 100644
--- a/translations/zh-CN/data/reusables/marketplace/upgrade-app-billing-settings.md
+++ b/translations/zh-CN/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -1 +1 @@
-1. 使用 **Edit（编辑）**下拉菜单并单击 **Change plan（更改计划）**。 ![个人帐户帐单设置中“市场购买”部分的 Edit（编辑）下拉菜单](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
+1. 在要升级的应用程序旁边，使用 **Edit（编辑）**下拉菜单，然后单击 **Change plan（更改计划）**。 ![个人帐户帐单设置中“市场购买”部分的 Edit（编辑）下拉菜单](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md b/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..a3d5892801
--- /dev/null
+++ b/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,2 @@
+{%- if currentVersion == "free-pro-team@latest" %}议题、拉取请求、发行版、安全警报或讨论{% endif %}
+{%- if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}议题、拉取请求、发行版或讨论{% endif %}
diff --git a/translations/zh-CN/data/reusables/notifications/email-restrictions-verification.md b/translations/zh-CN/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..1671963330
--- /dev/null
+++ b/translations/zh-CN/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1 @@
+After you enable email restrictions, members can receive email notifications at verified email addresses within domains that you've verified or approved. 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。
diff --git a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
index 34c20a5bf7..9f52cf5f42 100644
--- a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
+++ b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -1,3 +1,7 @@
-您可以选择传送您所关注的仓库中{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}的方式，以及您接收通知的频率。
-
-
+{% if currentVersion == "free-pro-team@latest" %}
+您可以选择
+您关注或已订阅安全警报通知的仓库中 {% data variables.product.prodname_dependabot_alerts %} 通知的递送方式和频率。
+{% else %}
+您可以选择
+您关注的仓库中{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}通知的递送方式，以及您接收通知的频率。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/add-a-domain.md b/translations/zh-CN/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..d836fc86f2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1 @@
+1. 单击 **Add a domain（添加域）**。 ![添加域按钮](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/zh-CN/data/reusables/organizations/billing_plans.md b/translations/zh-CN/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..32b13ca571
--- /dev/null
+++ b/translations/zh-CN/data/reusables/organizations/billing_plans.md
@@ -0,0 +1 @@
+1. 在组织的 Settings（设置）侧边栏中，单击 **Billing & plans（帐单和计划）**。 ![帐单设置](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
diff --git a/translations/zh-CN/data/reusables/organizations/continue-verifying-domain.md b/translations/zh-CN/data/reusables/organizations/continue-verifying-domain.md
index 632d34b7dd..a98a66e520 100644
--- a/translations/zh-CN/data/reusables/organizations/continue-verifying-domain.md
+++ b/translations/zh-CN/data/reusables/organizations/continue-verifying-domain.md
@@ -1,2 +1,2 @@
 9. 在待验证的域右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Continue verifying（继续验证）**。 ![继续验证域按钮](/assets/images/help/organizations/continue-verifying-domain.png)
-10. 单击 **Verify domain（验证域）**。 ![验证域按钮](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
+10. 单击 **Verify（验证）**。 ![Verify button](/assets/images/help/organizations/verify-domain-final-button.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/organizations/domains-approve-domain.md b/translations/zh-CN/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..49348133df
--- /dev/null
+++ b/translations/zh-CN/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1 @@
+1. Read the information about domain approval, then click **Approve _DOMAIN_**. !["Approve DOMAIN" button in confirmation dialog](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/zh-CN/data/reusables/organizations/domains-approve-it-instead.md b/translations/zh-CN/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..a92fff88be
--- /dev/null
+++ b/translations/zh-CN/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1 @@
+1. To the right of "Can't verify this domain?", click **Approve it instead**. !["Approve it instead" text when verifying a domain](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/zh-CN/data/reusables/organizations/verified-domains.md b/translations/zh-CN/data/reusables/organizations/verified-domains.md
index c53200ff05..9714304429 100644
--- a/translations/zh-CN/data/reusables/organizations/verified-domains.md
+++ b/translations/zh-CN/data/reusables/organizations/verified-domains.md
@@ -1 +1 @@
-1. 在左侧边栏中，单击 **Verified domains（已验证的域名）**。 ![已验证的域名按钮](/assets/images/help/organizations/verified-domains-button.png)
+1. In the left sidebar, click **Verified & approved domains**. !["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
diff --git a/translations/zh-CN/data/reusables/package_registry/about-packaging-and-actions.md b/translations/zh-CN/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..4d8d762977
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,30 @@
+### 持续集成工作流程中的打包
+
+打包步骤是持续集成或持续交付工作流程的常见部分。 在持续集成工作流程结束时创建包有助于拉取请求的代码审查。
+
+构建并测试代码后，打包步骤可以生成可运行或可部署的构件。 根据您构建的应用程序类型，此包可本地下载以进行手动测试、可供用户下载或部署到暂存或生产环境。
+
+例如，Java 项目的连续集成工作流程可能运行 `mvn package` 来生成 JAR 文件。 或者，Node.js 应用程序的 CI 工作流程可能会创建 Docker 容器。
+
+现在，在审查拉取请求时，您将能够查看工作流程运行并下载生成的构件。
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}
+![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down-updated.png)
+{% else %}
+![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png)
+{% endif %}
+
+这将允许您在计算机上运行拉取请求中的代码，有助于调试或测试拉取请求。
+
+### 发布包的工作流程
+
+除了上传打包构件以测试持续集成工作流程之外， 您还可以创建工作流程来构建项目并发布包到软件包注册表。
+
+* **发布软件包到 {% data variables.product.prodname_registry %}**
+  {% data variables.product.prodname_registry %} 可以作为多种类型包的包托管服务。 您可以选择与所有 {% data variables.product.prodname_dotcom %} 共享您的软件包，或者与合作者或组织共享私有软件包。 更多信息请参阅“[GitHub Packages 简介](/packages/learn-github-packages/introduction-to-github-packages)”。
+
+  每次推送到默认分支，您可能想将软件包发布到 {% data variables.product.prodname_registry %}。 这可让项目开发者始终能够通过从 {% data variables.product.prodname_registry %} 安装，很容易地运行和测试默认分支中的最新构建版本。
+
+* **将软件包发布到软件包注册表** 对于许多项目，每当发布项目的新版本时，都会执行发布到软件包注册表。 例如，生成 JAR 文件的项目可能会将新版本上传到 Maven Central 仓库。 或者，.NET 项目可能会生成一个微件包并上传到 Nuget Gallery。
+
+  您可以创建一个工作流程来自动执行此操作，在每次创建版本时将软件包发布到软件包注册表。 更多信息请参阅“[创建发行版](/github/administering-a-repository/creating-releases)”。
diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/zh-CN/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..a02c0f89d8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1 @@
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md b/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md
index 871ef95380..fef01bc087 100644
--- a/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md
+++ b/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md
@@ -1,14 +1,7 @@
-您需要访问令牌才能发布、安装和删除 {{ site.data.variables.product.prodname_registry }} 中的包。 您可以使用个人访问令牌直接向 {% data variables.product.prodname_registry %} 或 {% data variables.product.prodname_dotcom %} API 验证您的用户名。 创建个人访问令牌时，可根据需要为令牌分配不同的作用域。
+您需要访问令牌才能发布、安装和删除 {% data variables.product.prodname_registry %} 中的包。
 
-{% if currentVersion == "free-pro-team@latest" %}
-要使用
-{% data variables.product.prodname_actions %} 工作流程验证：
-- 对于包注册表 (`PACKAGE-REGISTRY.pkg.github.com`)，您可以使用 `GITHUB_TOKEN`。
-- 对于容器注册表 (`ghcr.io/OWNER/IMAGE-NAME`)，可以使用`GITHUB_TOKEN` 或个人访问令牌。 我们强烈建议您使用 `GITHUB_TOKEN` 来避免对仓库的不必要访问。
+您可以使用个人访问令牌 (PAT) 向 {% data variables.product.prodname_registry %} 或 {% data variables.product.prodname_dotcom %} API 验证。 创建个人访问令牌时，可根据需要为令牌分配不同的作用域。 有关 PAT 与包相关的域的更多信息，请参阅“[关于 GitHub Packages 的权限](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)”。
 
-有关 {% data variables.product.prodname_actions %} 工作流程中使用的 `GITHUB_TOKEN` 的更多信息，请参阅“[加密密钥](/actions/reference/encrypted-secrets)”和“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)”。
-
-{% else %}
-要
-使用 {% data variables.product.prodname_actions %} 工作流程向 {% data variables.product.prodname_registry %} 验证，必须使用 `GITHUB_TOKEN`。
-{% endif %}
+要在 {% data variables.product.prodname_actions %} 工作流程内向 {% data variables.product.prodname_registry %} 注册表验证，您可以使用：
+- `GITHUB_TOKEN` 来发布与工作流程仓库相关联的包。
+- PAT 来安装与其他私有仓库（`GITHUB_TOKEN` 无法访问）相关联的包。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md
index 47359eeafc..fe5dcf1281 100644
--- a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md
+++ b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -16,7 +16,7 @@
   $ export CR_PAT=YOUR_TOKEN
   ```
 3. 使用您的容器类型的 CLI 登录到
-`ghcr.io` 上的 {% data variables.product.prodname_github_container_registry %} 服务。
+`ghcr.io` 上的 {% data variables.product.prodname_container_registry %} 服务。
   {% raw %}
   ```shell
   $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin
diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
index 1f80199d66..7e94c3c219 100644
--- a/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
+++ b/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
@@ -2,9 +2,9 @@
 
 PAT 可以授予对您的帐户的广泛访问权限。 在创建 PAT 以向 {% data variables.product.prodname_container_registry %} 验证时，您应该只选择必要的 `read:packages`、`write:packages` 或 `delete:packages` 范围。
 
-要在 {% data variables.product.prodname_actions %} 工作流程中向 {% data variables.product.prodname_github_container_registry %} 验证，请使用 `GITHUB_TOKEN` 以获得最佳的安全性和体验。
+要在 {% data variables.product.prodname_actions %} 工作流程中向 {% data variables.product.prodname_container_registry %} 验证，请使用 `GITHUB_TOKEN` 以获得最佳的安全性和体验。
 
-有关更新使用个人访问令牌向 `ghcr.io` 验证的工作流程的指南，请参阅“[升级访问 `ghcr.io` 的工作流程](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)”。
+有关更新使用个人访问令牌向 `ghcr.io` 验证的工作流程的指南，请参阅“[升级访问 `ghcr.io` 的工作流程](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)”。
 
 {% data reusables.package_registry.github-token-security-over-pat %}
 
diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md b/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md
index 3f255bab1b..22ce98040e 100644
--- a/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md
+++ b/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 要使用 {% data variables.product.prodname_github_container_registry %}，您必须启用功能预览。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)”和“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。
+**Note:** The {% data variables.product.prodname_container_registry %} is currently in public beta and subject to change. 在测试阶段，存储和带宽是免费的。 要使用 {% data variables.product.prodname_container_registry %}，您必须启用功能预览。 更多信息请参阅“[{% data variables.product.prodname_registry %} 简介](/packages/learn-github-packages/introduction-to-github-packages)”和“[使用 {% data variables.product.prodname_container_registry %} 启用改进的容器支持](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)”。
 
 {% endnote %}
diff --git a/translations/zh-CN/data/reusables/package_registry/docker-vs-container-registry.md b/translations/zh-CN/data/reusables/package_registry/docker-vs-container-registry.md
new file mode 100644
index 0000000000..fcc72414c2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/docker-vs-container-registry.md
@@ -0,0 +1,9 @@
+{% if currentVersion == "free-pro-team@latest" %}
+{% note %}
+
+**比较 Docker 注册表和 {% data variables.product.prodname_container_registry %}：**
+- {% data variables.product.prodname_container_registry %} (`https://ghcr.io`) 可提供更好的容器性能，将来会取代 Docker 注册表。
+- 您可以将 Docker 映像和工作流程从 Docker 注册表  (`docker.pkg.github.com`)  迁移到 {% data variables.product.prodname_container_registry %} (`https://ghcr.io`)，以实现精细权限、容器存储优化等。 更多信息请参阅“[从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)”。
+
+{% endnote %}
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md
index a23fdc598b..ef48e1de96 100644
--- a/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md
+++ b/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -1,5 +1,5 @@
 {% warning %}
 
-**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/guides/migrating-to-github-container-registry-for-docker-images)" and "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)."{% endif %}
+**注：**{% data variables.product.prodname_registry %} Docker 注册表 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 将在未来的 {% data variables.product.product_name %} 版本中被 {% data variables.product.prodname_container_registry %} 取代，后者将提供更好的容器支持。{% elsif currentVersion == "free-pro-team@latest" %} 被 {% data variables.product.prodname_container_registry %} 取代，后者提供更好的容器支持。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} 要了解如何迁移现有的 Docker 映像以及任何使用它们的工作流程，请参阅“[从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)”。 {% endif %}
 
 {% endwarning %}
diff --git a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md
index 6ccacc726b..f75a97e3dd 100644
--- a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md
+++ b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**注：**要使用 {% data variables.product.prodname_github_container_registry %}，您必须为您的帐户启用该功能。 更多信息请参阅“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。
+**注：**要使用 {% data variables.product.prodname_container_registry %}，您必须为您的帐户启用该功能。 更多信息请参阅“[使用 {% data variables.product.prodname_container_registry %} 启用改进的容器支持](/packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry)”。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/zh-CN/data/reusables/package_registry/github-token-security-over-pat.md b/translations/zh-CN/data/reusables/package_registry/github-token-security-over-pat.md
index d9425a7e12..51a599c08f 100644
--- a/translations/zh-CN/data/reusables/package_registry/github-token-security-over-pat.md
+++ b/translations/zh-CN/data/reusables/package_registry/github-token-security-over-pat.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_github_container_registry %} 现在支持 `GITHUB_TOKEN` 在您的工作流中进行简单和安全的认证。 如果您的工作流程使用个人访问令牌 (PAT) 向 `ghcr.io` 验证，我们强烈建议您更新工作流程以使用 `GITHUB_TOKEN`。
+{% data variables.product.prodname_container_registry %} 现在支持 `GITHUB_TOKEN` 在您的工作流程中进行简单和安全的身份验证。 如果您的工作流程使用个人访问令牌 (PAT) 向 `ghcr.io` 验证，我们强烈建议您更新工作流程以使用 `GITHUB_TOKEN`。
 
-有关 `GITHUB_TOKEN` 的更多信息，请参阅“[加密密钥](/actions/reference/encrypted-secrets)”和“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)”。
\ No newline at end of file
+有关 `GITHUB_TOKEN` 的更多信息，请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)”。
diff --git a/translations/zh-CN/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md b/translations/zh-CN/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
new file mode 100644
index 0000000000..e56d7b1496
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/repo-scoped-and-granular-permissions-packages.md
@@ -0,0 +1,12 @@
+仓库作用域的包从拥有该包的仓库继承权限和可见性。 下面的注册表使用此类权限：
+- Docker registry (`docker.pkg.github.com`)
+- npm registry
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% if currentVersion == "free-pro-team@latest" %}
+容器注册表 (`ghcr.io`) 提供精细权限和可见性设置，可针对个人用户或组织帐户拥有的每个包进行自定义。
+{% endif %}
+
+更多信息请参阅“[关于 GitHub Packages 的权限](/packages/learn-github-packages/about-permissions-for-github-packages)”{% if currentVersion == "free-pro-team@latest" %} 或“[配置包的访问控制和可见性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)”。{% endif %}
diff --git a/translations/zh-CN/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/zh-CN/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..10af4c6fb4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,13 @@
+{% if currentVersion == "free-pro-team@latest" %}
+如果您对容器映像具有管理员权限，可以将容器映像的访问权限设置为私有或公有。 公有映像允许匿名访问，无需身份验证或通过 CLI 登录即可进行拉取。
+
+作为管理员，您还可以授予容器映像的访问权限，该权限与在组织和仓库级别设置的权限不同。
+
+对于由用户帐户发布和拥有的容器映像，您可以向任何人授予访问角色。 对于组织发布和拥有的容器映像，您可以为组织中的任何人或团队授予访问角色。
+
+| 权限  | 访问描述                                                         |
+| --- | ------------------------------------------------------------ |
+| 读取  | 可以下载包。 <br> 可以读取包元数据。                                  |
+| 写入  | 可以上传和下载此包。 <br> 可以读取和写入包元数据。                           |
+| 管理员 | 可以上传、下载、删除和管理此包。 <br> 可以读取和写入包元数据。 <br> 可以授予包权限。 |
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md b/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md
index d20e0ba800..b86b16b8c8 100644
--- a/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md
+++ b/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md
@@ -1,5 +1,5 @@
 如果站点是一个独立的项目，您可以创建新仓库来存储站点源代码。 如果您的站点与现有的项目关联，您可以添加站点的源代码添加{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}到该项目仓库的默认分支或其他分支上的 `/docs` 文件夹中。{% else %}到 `gh-pages` 分支或该项目仓库 `master` 分支上的 `docs` 文件夹中。{% endif %} 例如，如果您创建站点来发布已经在 {% data variables.product.product_name %} 中的项目文档， 您可能想要将站点的源代码存储在与项目相同的仓库中。
 
-{% if currentversion == "free-proteam@latest" %}如果拥有仓库的帐户使用组织的 {% data variables.product.prodname_free_user %} 或 {% data variables.product.prodname_free_team %}，仓库必须是公共的。{% endif %}
+{% if currentVersion == "free-proteam@latest" %}如果拥有仓库的帐户使用组织的 {% data variables.product.prodname_free_user %} 或 {% data variables.product.prodname_free_team %}，仓库必须是公共的。{% endif %}
 
 如果要在现有仓库中创建站点，请跳至“[创建站点](#creating-your-site)”一节。
diff --git a/translations/zh-CN/data/reusables/pages/sidebar-pages.md b/translations/zh-CN/data/reusables/pages/sidebar-pages.md
index 371201ab38..260476ce71 100644
--- a/translations/zh-CN/data/reusables/pages/sidebar-pages.md
+++ b/translations/zh-CN/data/reusables/pages/sidebar-pages.md
@@ -1,3 +1,3 @@
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}
-1. 在左侧边栏中，单击 **Pages（页面）**。 ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png)
+1. 在左侧边栏中，单击 **Pages（页面）**。 ![左侧边栏中的页面选项卡](/assets/images/help/pages/pages-tab.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/profile/access_org.md b/translations/zh-CN/data/reusables/profile/access_org.md
index b3746bd00a..e6326cd1d3 100644
--- a/translations/zh-CN/data/reusables/profile/access_org.md
+++ b/translations/zh-CN/data/reusables/profile/access_org.md
@@ -1 +1 @@
-1. 在您的个人资料页面左侧的“Organizations（组织）”下，单击组织的图标。 ![组织图标](/assets/images/help/profile/profile_orgs_box.png)
+1. 在 {% data variables.product.prodname_dotcom %} 的右上角，单击您的个人资料照片，然后单击 **Your organizations（您的组织）**。 ![个人资料菜单中的组织](/assets/images/help/profile/your-organizations.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/profile/org_settings.md b/translations/zh-CN/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..b8e5049d1b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/profile/org_settings.md
@@ -0,0 +1 @@
+2. 单击组织旁边的 **Settings（设置）** 。 ![设置按钮](/assets/images/help/organizations/settings-button.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/profile/user_profile_page_block_or_report.md b/translations/zh-CN/data/reusables/profile/user_profile_page_block_or_report.md
index cea65b694f..01c96d734d 100644
--- a/translations/zh-CN/data/reusables/profile/user_profile_page_block_or_report.md
+++ b/translations/zh-CN/data/reusables/profile/user_profile_page_block_or_report.md
@@ -1 +1 @@
-1. 在左侧边栏中，在用户的个人资料图片下，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Block or report user（阻止或报告用户）**。 ![阻止或举报用户链接](/assets/images/help/profile/profile-block-or-report-button.png)
+1. 在左侧边栏中的用户个人资料信息下，单击 **Block or report（阻止或举报）**。 ![阻止或举报链接](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md
index 1e30bd5780..3ca34e4405 100644
--- a/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md
+++ b/translations/zh-CN/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -6,6 +6,6 @@
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/30 5,17 * * *'
+    - cron:  '30 5,17 * * *'
 
 ```
diff --git a/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
index d05d123825..7a90f305cb 100644
--- a/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
+++ b/translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
@@ -6,6 +6,6 @@
 - 当 [LDAP 同步启用](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync)后，如果从仓库删除某用户，此用户将失去访问权，但其复刻不会被删除。 如果此用户在三个月内被加入具有原组织仓库访问权限的团队，则其对复刻的访问权限将在下次同步时自动恢复。{% endif %}
 - 您负责确保无法访问仓库的人员删除任何机密信息或知识产权。
 
-- 对私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库拥有管理员权限的人可以禁止对该仓库进行复刻，组织所有者可以禁止对组织中的任何私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库进行复刻。 For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+- 对私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库拥有管理员权限的人可以禁止对该仓库进行复刻，组织所有者可以禁止对组织中的任何私有{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 或内部{% endif %} 仓库进行复刻。 更多信息请参阅“[管理组织的复刻政策](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)”和“[管理仓库的复刻政策](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)”。
 
 {% endwarning %}
diff --git a/translations/zh-CN/data/reusables/repositories/request-changes-tips.md b/translations/zh-CN/data/reusables/repositories/request-changes-tips.md
index c3b442cc09..b8ea59eb8e 100644
--- a/translations/zh-CN/data/reusables/repositories/request-changes-tips.md
+++ b/translations/zh-CN/data/reusables/repositories/request-changes-tips.md
@@ -5,5 +5,6 @@
 - 即使没有获得批准审查，或者请求更改的审查者离开了组织或者联系不上，仓库所有者和管理员也可合并拉取请求。
 - 如果同时启用了必需审查和过期审查，并且代码修改提交已推送到批准的拉取请求分支，则批准将予驳回。 拉取请求必须经过再次审查和批准才可合并。
 - 当多个打开的拉取请求时分别有指向同一提交的头部分支时，如果一个或两者有待定或被拒绝的审查，您将无法合并它们。
+- 拉取请求作者无法批准自己的拉取请求。
 
 {% endtip %}
diff --git a/translations/zh-CN/data/reusables/repositories/security-guidelines.md b/translations/zh-CN/data/reusables/repositories/security-guidelines.md
index a51f837c8c..b87d707d22 100644
--- a/translations/zh-CN/data/reusables/repositories/security-guidelines.md
+++ b/translations/zh-CN/data/reusables/repositories/security-guidelines.md
@@ -1,3 +1,3 @@
-{% if currentVersion == "free-pro-team@latest" %}
-您可以制定安全政策，要求们负责任地报告您项目中的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/articles/adding-a-security-policy-to-your-repository)”。
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %}
+您可以创建安全策略，向人们提供有关报告项目中安全漏洞的说明。 更多信息请参阅“[添加安全政策到仓库](/code-security/getting-started/adding-a-security-policy-to-your-repository)”。
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md
index 100ac3c323..7796267d52 100644
--- a/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md
+++ b/translations/zh-CN/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -1 +1 @@
-1. 在安全侧边栏中，单击 **{% data variables.product.prodname_dependabot_alerts %}**。 ![{% data variables.product.prodname_dependabot_alerts %} 选项卡](/assets/images/help/repository/dependabot-alerts-tab.png)
+1. 在安全侧边栏中，点击 **{% data variables.product.prodname_dependabot_alerts %}**。{% if currentVersion == "free-pro-team@latest" %} ![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/repository/dependabot-alerts-tab.png){% elsif %}![{% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/zh-CN/data/reusables/repositories/you-can-fork.md b/translations/zh-CN/data/reusables/repositories/you-can-fork.md
index 4d7a785609..2c95bedfb4 100644
--- a/translations/zh-CN/data/reusables/repositories/you-can-fork.md
+++ b/translations/zh-CN/data/reusables/repositories/you-can-fork.md
@@ -2,6 +2,6 @@
 
 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
 
-如果您可以访问私有仓库且所有者允许复刻，则您可以将该仓库复刻到您的用户帐户或者 {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} 上您具有仓库创建权限的任何组织。 {% if currentversion == "free proteam@latest" %}您不能将私有仓库复刻到使用 {% data variables.product.prodname_free_team %} 的组织。 更多信息请参阅“[GitHub 的产品](/articles/githubs-products)”。{% endif %}
+如果您可以访问私有仓库且所有者允许复刻，则您可以将该仓库复刻到您的用户帐户或者 {% if currentVersion == "free-pro-team@latest"%}{% data variables.product.prodname_team %}{% else %}{% data variables.product.product_location %}{% endif %} 上您具有仓库创建权限的任何组织。 {% if currentVersion == "free proteam@latest" %}您不能将私有仓库复刻到使用 {% data variables.product.prodname_free_team %} 的组织。 更多信息请参阅“[GitHub 的产品](/articles/githubs-products)”。{% endif %}
 
 {% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md b/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md
index 359c8d3e18..a3abbdc0cd 100644
--- a/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md
+++ b/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md
@@ -1 +1 @@
-您必须定期向 SAML IdP 身份验证并访问 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %} 上的组织资源 {% elsif currentversion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}。 此登录期的持续时间由 IdP 指定，一般为 24 小时。 此定期登录要求会限制访问的时长，您必须重新验证身份后才可继续访问。 {% if currentversion == "free proteam@latest" %}您可以在安全设置中查看和管理正在进行的 SAML 会话。 更多信息请参阅“[查看和管理活动的 SAML 会话](/articles/viewing-and-managing-your-active-saml-sessions)”。{% endif %}
+您必须定期向 SAML IdP 身份验证并访问 {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %} 上的组织资源 {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% endif %}。 此登录期的持续时间由 IdP 指定，一般为 24 小时。 此定期登录要求会限制访问的时长，您必须重新验证身份后才可继续访问。 {% if currentVersion == "free proteam@latest" %}您可以在安全设置中查看和管理正在进行的 SAML 会话。 更多信息请参阅“[查看和管理活动的 SAML 会话](/articles/viewing-and-managing-your-active-saml-sessions)”。{% endif %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/beta.md b/translations/zh-CN/data/reusables/secret-scanning/beta.md
index 3ad90c6c8c..18caa58d51 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/beta.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/beta.md
@@ -10,7 +10,7 @@
 
 {% note %}
 
-**注：** {% data variables.product.prodname_secret_scanning_caps %} 正在测试用于 {% data variables.product.prodname_ghe_server %} 3.0。 对于机密扫描的一般可用版本，请升级到最新版本的 {% data variables.product.prodname_ghe_server %}。
+**注：** {% data variables.product.prodname_secret_scanning_caps %} 是 {% data variables.product.prodname_ghe_server %} 3.0 中的测试版功能。 对于 {% data variables.product.prodname_secret_scanning %} 的一般可用版本，请升级到 {% data variables.product.prodname_ghe_server %} 的最新版本。
 
 
 {% endnote %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 1839a08f29..3f77aec78a 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -1,79 +1,171 @@
-| 合作伙伴                      | 支持的密钥                               | API slug                                 |
-| ------------------------- | ----------------------------------- | ---------------------------------------- |
-| n/a                       | JSON Web 令牌                         | json_web_token                         |
-| n/a                       | OAuth 客户端凭据                         | api_credential_assignment              |
-| Adafruit IO               | Adafruit IO 密钥                      | adafruit_io_key                        |
-| Alibaba Cloud             | Alibaba 云访问密钥 ID                    | alibaba_cloud_access_key_id          |
-| Alibaba Cloud             | Alibaba 云访问密钥机密                     | alibaba_cloud_access_key_secret      |
-| Amazon Web Services (AWS) | Amazon AWS 访问密钥 ID                  | aws_access_key_id                      |
-| Amazon Web Services (AWS) | Amazon AWS 机密访问密钥                   | aws_secret_access_key                  |
-| Asana                     | Asana 个人访问令牌                        | asana_personal_access_token            |
-| Atlassian                 | Atlassian API 令牌                    | atlassian_api_token                    |
-| Atlassian                 | Atlassian JSON Web 令牌               | atlassian_jwt                            |
-| Azure                     | Azure DevOps 个人访问令牌                 | azure_devops_personal_access_token   |
-| Azure                     | Azure SAS 令牌                        | azure_sas_token                        |
-| Azure                     | Azure 服务管理证书                        | azure_management_certificate           |
-| Azure                     | Azure SQL 连接字符串                     | azure_sql_connection_string            |
-| Azure                     | Azure 存储账户密钥                        | azure_storage_account_key              |
-| Clojars                   | Clojars 部署令牌                        | clojars_deploy_token                   |
-| CloudBees CodeShip        | CloudBees CodeShip 凭据               | codeship_credential                      |
-| Databricks                | Databricks 访问令牌                     | databricks_access_token                |
-| Discord                   | Discord 自动程序令牌                      | discord_bot_token                      |
-| Doppler                   | Doppler 个人令牌                        | doppler_personal_token                 |
-| Doppler                   | Doppler 服务令牌                        | doppler_service_token                  |
-| Doppler                   | Doppler CLI 令牌                      | doppler_cli_token                      |
-| Doppler                   | Doppler SCIM 令牌                     | doppler_scim_token                     |
-| Dropbox                   | Dropbox 访问令牌                        | dropbox_access_token                   |
-| Dropbox                   | Dropbox 短暂访问令牌                      | dropbox_short_lived_access_token     |
-| Dynatrace                 | Dynatrace 访问令牌                      | dynatrace_access_token                 |
-| Dynatrace                 | Dynatrace 内部令牌                      | dynatrace_internal_token               |
-| Facebook                  | Facebook Access Token               | facebook_access_token                  |
-| Finicity                  | Finicity App 密钥                     | finicity_app_key                       |
-| Frame.io                  | Frame.io JSON Web 令牌                | frameio_jwt                              |
-| Frame.io                  | Frame.io Developer 令牌               | frameio_developer_token                |
-| GitHub                    | GitHub SSH 私钥                       | github_ssh_private_key                 |
-| GitHub                    | GitHub 个人访问令牌                       | github_personal_access_token           |
-| GitHub                    | GitHub App 安装访问令牌                   | github_app_installation_access_token |
-| GoCardless                | GoCardless 实时访问令牌                   | gocardless_live_access_token           |
-| GoCardless                | GoCardless Sandbox 访问令牌             | gocardless_sandbox_access_token        |
-| Google Cloud              | Google API 密钥                       | google_api_key                         |
-| Google Cloud              | Google Cloud 私钥 ID                  | google_cloud_private_key_id          |
-| Grafana                   | Grafana API 密钥                      | grafana_api_key                        |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API 令牌 | terraform_api_token                    |
-| Hubspot                   | Hubspot API 密钥                      | hubspot_api_key                        |
-| Intercom                  | Intercom 访问令牌                       | intercom_access_token                  |
-| Lob                       | Lob Live API 密钥                     | lob_live_api_key                       |
-| Lob                       | Lob Test API 密钥                     | lob_test_api_key                       |
-| Mailchimp                 | Mailchimp API 密钥                    | mailchimp_api_key                      |
-| Mailgun                   | Mailgun API 密钥                      | mailgun_api_key                        |
-| npm                       | npm 访问令牌                            | npm_access_token                       |
-| NuGet                     | NuGet API 密钥                        | nuget_api_key                          |
-| Palantir                  | Palantir JSON Web 令牌                | palantir_jwt                             |
-| Postman                   | Postman API 密钥                      | postman_api_key                        |
-| Proctorio                 | Proctorio 消费者密钥                     | proctorio_consumer_key                 |
-| Proctorio                 | Proctorio 链接密钥                      | proctorio_linkage_key                  |
-| Proctorio                 | Proctorio 注册密钥                      | proctorio_registration_key             |
-| Proctorio                 | Proctorio 密钥                        | proctorio_secret_key                   |
-| Pulumi                    | Pulumi 访问令牌                         | pulumi_access_token                    |
-| PyPI                      | PyPI API 令牌                         | pypi_api_token                         |
-| RubyGems                  | RubyGems API 密钥                     | rubygems_api_key                       |
-| Samsara                   | Samsara API 令牌                      | samsara_api_token                      |
-| Samsara                   | Samsara OAuth 访问令牌                  | samsara_oauth_access_token             |
-| SendGrid                  | SendGrid API Key                    | sendgrid_api_key                       |
-| Shopify                   | Shopify App 共享密钥                    | shopify_app_shared_secret              |
-| Shopify                   | Shopify 访问令牌                        | shopify_access_token                   |
-| Shopify                   | Shopify 自定义应用访问令牌                   | shopify_custom_app_access_token      |
-| Shopify                   | Shopify 私人应用密码                      | shopify_private_app_password           |
-| Slack                     | Slack API 令牌                        | slack_api_token                        |
-| Slack                     | Slack 传入 web 挂钩 URL                 | slack_incoming_webhook_url             |
-| Slack                     | Slack 工作流程 web 挂钩 URL               | slack_workflow_webhook_url             |
-| SSLMate                   | SSLMate API 密钥                      | sslmate_api_key                        |
-| SSLMate                   | SSLMate 集群密钥                        | sslmate_cluster_secret                 |
-| Stripe                    | Stripe API Key                      | stripe_api_key                         |
-| Stripe                    | Stripe Live API 密钥                  | stripe_live_secret_key                 |
-| Stripe                    | Stripe 测试 API 密钥                    | stripe_test_secret_key                 |
-| Stripe                    | Stripe Live API 限制密钥                | stripe_live_restricted_key             |
-| Stripe                    | Stripe 测试 API 限制密钥                  | stripe_test_restricted_key             |
-| Tencent Cloud             | 腾讯云密钥 ID                            | tencent_cloud_secret_id                |
-| Twilio                    | Twilio 帐户字符串标识符                     | twilio_account_sid                     |
-| Twilio                    | Twilio API 密钥                       | twilio_api_key                         |
+| 合作伙伴 | 支持的密钥 | API slug |
+| ---- | ----- | -------- |
+|      |       |          |
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Device Token | adobe_device_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Service Token | adobe_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Adobe | Adobe JSON Web Token | adobe_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Asana | Asana Personal Access Token | asana_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian API Token | atlassian_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SAS Token | azure_sas_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Service Management Certificate | azure_management_certificate{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Databricks | Databricks Access Token | databricks_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Discord | Discord Bot Token | discord_bot_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Personal Token | doppler_personal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler Service Token | doppler_service_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler CLI Token | doppler_cli_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Doppler | Doppler SCIM Token | doppler_scim_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Access Token | dropbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Facebook | Facebook Access Token | facebook_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Fastly | Fastly API Token | fastly_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Finicity | Finicity App Key | finicity_app_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub Refresh Token | github_refresh_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google API Key | google_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Google Cloud | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Grafana | Grafana API Key | grafana_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Hubspot | Hubspot API Key | hubspot_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Intercom | Intercom Access Token | intercom_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Live API Key | lob_live_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+Lob | Lob Test API Key | lob_test_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Mailgun | Mailgun API Key | mailgun_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+npm | npm Access Token | npm_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+NuGet | NuGet API Key | nuget_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+OpenAI | OpenAI API Key | openai_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Palantir | Palantir JSON Web Token | palantir_jwt{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Postman | Postman API Key | postman_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Pulumi | Pulumi Access Token | pulumi_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+PyPI | PyPI API Token | pypi_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+RubyGems | RubyGems API Key | rubygems_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara API Token | samsara_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}
+SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Access Token | shopify_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Shopify | Shopify Private App Password | shopify_private_app_password{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack API Token | slack_api_token{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate API Key | sslmate_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Stripe | Stripe API Key | stripe_api_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %}
+{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@next" %}
+Twilio | Twilio API Key | twilio_api_key{% endif %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md
index 9de42cb5f0..33de5353af 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -1,71 +1,79 @@
-| 合作伙伴                      | 支持的密钥                                                        |
-| ------------------------- | ------------------------------------------------------------ |
-| Adafruit IO               | Adafruit IO 密钥                                               |
-| Alibaba Cloud             | Alibaba 云端访问密钥 ID 和访问密钥对                                     |
-| Amazon Web Services (AWS) | Amazon AWS 访问密钥 ID 和秘密访问密钥对                                  |
-| Atlassian                 | Atlassian API 令牌                                             |
-| Atlassian                 | Atlassian JSON Web 令牌                                        |
-| Azure                     | Azure DevOps 个人访问令牌 | azure_devops_personal_access_token |
-| Azure                     | Azure SAS Token | azure_sas_token                          |
-| Azure                     | Azure 服务管理证书 | azure_management_certification              |
-| Azure                     | Azure SQL 连接字符串 | azure_sql_connection_string              |
-| Azure                     | Azure 存储帐户密钥 | azure_storage_account_key                   |
-| Clojars                   | Clojars 部署令牌                                                 |
-| CloudBees CodeShip        | CloudBees CodeShip 凭据                                        |
-| Databricks                | Databricks 访问令牌                                              |
-| Datadog                   | Datadog API 密钥                                               |
-| Discord                   | Discord 自动程序令牌                                               |
-| Doppler                   | Doppler 个人令牌                                                 |
-| Doppler                   | Doppler 服务令牌                                                 |
-| Doppler                   | Doppler CLI 令牌                                               |
-| Doppler                   | Doppler SCIM 令牌                                              |
-| Dropbox                   | Dropbox 访问令牌                                                 |
-| Dropbox                   | Dropbox 短暂访问令牌                                               |
-| Dynatrace                 | Dynatrace 访问令牌                                               |
-| Dynatrace                 | Dynatrace 内部令牌                                               |
-| Finicity                  | Finicity App 密钥                                              |
-| Frame.io                  | Frame.io JSON Web 令牌                                         |
-| Frame.io                  | Frame.io Developer 令牌                                        |
-| GitHub                    | GitHub SSH 私钥                                                |
-| GitHub                    | GitHub 个人访问令牌                                                |
-| GitHub                    | GitHub App 安装访问令牌                                            |
-| GoCardless                | GoCardless 实时访问令牌                                            |
-| GoCardless                | GoCardless Sandbox 访问令牌                                      |
-| Google Cloud              | Google API 密钥                                                |
-| Google Cloud              | Google Cloud 私钥 ID                                           |
-| Hashicorp Terraform       | Terraform Cloud / Enterprise API 令牌                          |
-| Hubspot                   | Hubspot API 密钥                                               |
-| Mailchimp                 | Mailchimp API 密钥                                             |
-| Mailchimp                 | Mandril API 密钥                                               |
-| Mailgun                   | Mailgun API 密钥                                               |
-| MessageBird               | MessageBird API 密钥                                           |
-| npm                       | npm 访问令牌                                                     |
-| NuGet                     | NuGet API 密钥                                                 |
-| Palantir                  | Palantir JSON Web 令牌                                         |
-| Plivo                     | Plivo 验证令牌                                                   |
-| Postman                   | Postman API 密钥                                               |
-| Proctorio                 | Proctorio 消费者密钥                                              |
-| Proctorio                 | Proctorio 链接密钥                                               |
-| Proctorio                 | Proctorio 注册密钥                                               |
-| Proctorio                 | Proctorio 密钥                                                 |
-| Pulumi                    | Pulumi 访问令牌                                                  |
-| PyPI                      | PyPI API 令牌                                                  |
-| RubyGems                  | RubyGems API 密钥                                              |
-| Samsara                   | Samsara API 令牌                                               |
-| Samsara                   | Samsara OAuth 访问令牌                                           |
-| Shopify                   | Shopify App 共享密钥                                             |
-| Shopify                   | Shopify 访问令牌                                                 |
-| Shopify                   | Shopify 自定义应用访问令牌                                            |
-| Shopify                   | Shopify 私人应用密码                                               |
-| Slack                     | Slack API 令牌                                                 |
-| Slack                     | Slack 传入 web 挂钩 URL                                          |
-| Slack                     | Slack 工作流程 web 挂钩 URL                                        |
-| SSLMate                   | SSLMate API 密钥                                               |
-| SSLMate                   | SSLMate 集群密钥                                                 |
-| Stripe                    | Stripe Live API 密钥                                           |
-| Stripe                    | Stripe 测试 API 密钥                                             |
-| Stripe                    | Stripe Live API 限制密钥                                         |
-| Stripe                    | Stripe 测试 API 限制密钥                                           |
-| Tencent Cloud             | 腾讯云密钥 ID                                                     |
-| Twilio                    | Twilio 帐户字符串标识符                                              |
-| Twilio                    | Twilio API 密钥                                                |
+| 合作伙伴                      | 支持的密钥                               |
+| ------------------------- | ----------------------------------- |
+| Adafruit IO               | Adafruit IO 密钥                      |
+| Adobe                     | Adobe 设备令牌                          |
+| Adobe                     | Adobe 服务令牌                          |
+| Adobe                     | Adobe 短暂访问令牌                        |
+| Adobe                     | Adobe JSON Web 令牌                   |
+| Alibaba Cloud             | Alibaba 云端访问密钥 ID 和访问密钥对            |
+| Amazon Web Services (AWS) | Amazon AWS 访问密钥 ID 和秘密访问密钥对         |
+| Atlassian                 | Atlassian API 令牌                    |
+| Atlassian                 | Atlassian JSON Web 令牌               |
+| Azure                     | Azure DevOps 个人访问令牌                 |
+| Azure                     | Azure SAS 令牌                        |
+| Azure                     | Azure 服务管理证书                        |
+| Azure                     | Azure SQL 连接字符串                     |
+| Azure                     | Azure 存储账户密钥                        |
+| Clojars                   | Clojars 部署令牌                        |
+| CloudBees CodeShip        | CloudBees CodeShip 凭据               |
+| Databricks                | Databricks 访问令牌                     |
+| Datadog                   | Datadog API 密钥                      |
+| Discord                   | Discord 自动程序令牌                      |
+| Doppler                   | Doppler 个人令牌                        |
+| Doppler                   | Doppler 服务令牌                        |
+| Doppler                   | Doppler CLI 令牌                      |
+| Doppler                   | Doppler SCIM 令牌                     |
+| Dropbox                   | Dropbox 访问令牌                        |
+| Dropbox                   | Dropbox 短暂访问令牌                      |
+| Dynatrace                 | Dynatrace 访问令牌                      |
+| Dynatrace                 | Dynatrace 内部令牌                      |
+| Finicity                  | Finicity App 密钥                     |
+| Frame.io                  | Frame.io JSON Web 令牌                |
+| Frame.io                  | Frame.io Developer 令牌               |
+| GitHub                    | GitHub 个人访问令牌                       |
+| GitHub                    | GitHub OAuth 访问令牌                   |
+| GitHub                    | GitHub 刷新令牌                         |
+| GitHub                    | GitHub App 安装访问令牌                   |
+| GitHub                    | GitHub SSH 私钥                       |
+| GoCardless                | GoCardless 实时访问令牌                   |
+| GoCardless                | GoCardless Sandbox 访问令牌             |
+| Google Cloud              | Google API 密钥                       |
+| Google Cloud              | Google Cloud 私钥 ID                  |
+| Hashicorp Terraform       | Terraform Cloud / Enterprise API 令牌 |
+| Hubspot                   | Hubspot API 密钥                      |
+| Mailchimp                 | Mailchimp API 密钥                    |
+| Mailchimp                 | Mandril API 密钥                      |
+| Mailgun                   | Mailgun API 密钥                      |
+| MessageBird               | MessageBird API 密钥                  |
+| npm                       | npm 访问令牌                            |
+| NuGet                     | NuGet API 密钥                        |
+| OpenAI                    | OpenAI API 密钥                       |
+| Palantir                  | Palantir JSON Web 令牌                |
+| Plivo                     | Plivo 验证令牌                          |
+| Postman                   | Postman API 密钥                      |
+| Proctorio                 | Proctorio 消费者密钥                     |
+| Proctorio                 | Proctorio 链接密钥                      |
+| Proctorio                 | Proctorio 注册密钥                      |
+| Proctorio                 | Proctorio 密钥                        |
+| Pulumi                    | Pulumi 访问令牌                         |
+| PyPI                      | PyPI API 令牌                         |
+| RubyGems                  | RubyGems API 密钥                     |
+| Samsara                   | Samsara API 令牌                      |
+| Samsara                   | Samsara OAuth 访问令牌                  |
+| SendGrid                  | SendGrid API Key                    |
+| Shopify                   | Shopify App 共享密钥                    |
+| Shopify                   | Shopify 访问令牌                        |
+| Shopify                   | Shopify 自定义应用访问令牌                   |
+| Shopify                   | Shopify 私人应用密码                      |
+| Slack                     | Slack API 令牌                        |
+| Slack                     | Slack 传入 web 挂钩 URL                 |
+| Slack                     | Slack 工作流程 web 挂钩 URL               |
+| SSLMate                   | SSLMate API 密钥                      |
+| SSLMate                   | SSLMate 集群密钥                        |
+| Stripe                    | Stripe Live API 密钥                  |
+| Stripe                    | Stripe 测试 API 密钥                    |
+| Stripe                    | Stripe Live API 限制密钥                |
+| Stripe                    | Stripe 测试 API 限制密钥                  |
+| Tencent Cloud             | 腾讯云密钥 ID                            |
+| Twilio                    | Twilio 帐户字符串标识符                     |
+| Twilio                    | Twilio API 密钥                       |
diff --git a/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..a615b11be2
--- /dev/null
+++ b/translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,5 @@
+{% if currentVersion == "free-pro-team@latest" %}
+更多信息请参阅“[浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)”和“[关于 {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)”。
+{% else %}
+有关公告数据的更多信息，请参阅“<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞</a>”。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/security/displayed-information.md b/translations/zh-CN/data/reusables/security/displayed-information.md
index 6fef92be5d..1c8b4fe237 100644
--- a/translations/zh-CN/data/reusables/security/displayed-information.md
+++ b/translations/zh-CN/data/reusables/security/displayed-information.md
@@ -1,7 +1,7 @@
 当您为现有仓库启用一个或多个安全和分析功能时，您将在几分钟内看到 {% data variables.product.prodname_dotcom %} 上显示的任何结果：
 
 - 所有现有仓库将具有选定的配置。
-- 如果您已为新仓库启用复选框，新仓库将使用选定的配置。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+- 如果您已为新仓库启用复选框，新仓库将使用选定的配置。{% if currentVersion == "free-pro-team@latest" %}
 - 我们使用权限扫描清单文件以应用相关服务。
 - 您将看到有关您的依赖关系图的信息。
-- {% data variables.product.prodname_dotcom %} 将生成 {% data variables.product.prodname_dependabot_alerts %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} 并提出拉取请求{% endif %}。 
+- {% data variables.product.prodname_dotcom %} 将生成 {% data variables.product.prodname_dependabot_alerts %} 并创建拉取请求{% endif %}。 
diff --git a/translations/zh-CN/data/reusables/sponsors/choose-updates.md b/translations/zh-CN/data/reusables/sponsors/choose-updates.md
index 6f452d58ff..2ec18f2030 100644
--- a/translations/zh-CN/data/reusables/sponsors/choose-updates.md
+++ b/translations/zh-CN/data/reusables/sponsors/choose-updates.md
@@ -1 +1 @@
-4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![接收来自赞助帐户的更新的复选框](/assets/images/help/sponsors/updates-checkbox-manage.png)
+4. 决定是否要接收来自被赞助帐户的电子邮件更新，然后选择或取消选择“Receive email updates from _ACCOUNT_（接收来自 ACCOUNT 的电子邮件更新）”。 ![接收来自赞助帐户的更新的复选框](/assets/images/help/sponsors/updates-checkbox-manage.png)
diff --git a/translations/zh-CN/data/reusables/sponsors/click-add-tier.md b/translations/zh-CN/data/reusables/sponsors/click-add-tier.md
index 427804a96d..2f9c9b0c9e 100644
--- a/translations/zh-CN/data/reusables/sponsors/click-add-tier.md
+++ b/translations/zh-CN/data/reusables/sponsors/click-add-tier.md
@@ -1 +1 @@
-1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![添加等级按钮](/assets/images/help/sponsors/add-a-tier-button.png)
+1. 要创建月度等级，请在页面右侧单击 **Add a monthly tier（添加月度等级）**。 或者，要创建一次性付款等级，请单击 **One-time tiers（一次性等级）**，然后单击 **Add a one-time tier（添加一次性等级）**。 ![添加等级按钮](/assets/images/help/sponsors/add-a-tier-button.png)
diff --git a/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md b/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md
index 1889367cb9..bfc5c674a9 100644
--- a/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md
+++ b/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md
@@ -1,2 +1,2 @@
-1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png)
-1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png)
+1. 当您至少有一个等级时，您将在月度和一次性等级之上看到一个可启用自定义金额的选项。 如果您要允许赞助者设置其付款金额，请选择 **Enable custom amounts（启用自定义金额）**。 ![启用自定义金额](/assets/images/help/sponsors/enable-custom-amounts.png)
+1. （可选）如果启用自定义金额，您可以设置针对自定义等级显示的默认金额。 指定整美元金额，然后单击 **Set default amount（设置默认金额）**。 ![设置默认金额](/assets/images/help/sponsors/set-default-amount.png)
diff --git a/translations/zh-CN/data/reusables/sponsors/feedback.md b/translations/zh-CN/data/reusables/sponsors/feedback.md
index e5cb6b1814..971520f781 100644
--- a/translations/zh-CN/data/reusables/sponsors/feedback.md
+++ b/translations/zh-CN/data/reusables/sponsors/feedback.md
@@ -1 +1 @@
-您可以与 {% data variables.product.company_short %} 分享您对 {% data variables.product.prodname_sponsors %} 的反馈。 To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)."
+您可以与 {% data variables.product.company_short %} 分享您对 {% data variables.product.prodname_sponsors %} 的反馈。 要加入对话，请参阅“[赞助者反馈](https://github.com/github/feedback/discussions/categories/sponsors-feedback)”。
diff --git a/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md b/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md
index 598554d9d7..a33e3be95b 100644
--- a/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md
+++ b/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md
@@ -1 +1 @@
-1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![链接到支付按比例计算的金额](/assets/images/help/sponsors/pay-prorated-amount-link.png)
\ No newline at end of file
+1. （可选）如果您是组织赞助者，要支付按时间比例分摊的金额而不是支付整月金额，请在“Total due now（现在应付款总额）”下，单击 **Pay prorated $X.XX instead（按比例支付 $X.XX）**。 ![链接到支付按比例计算的金额](/assets/images/help/sponsors/pay-prorated-amount-link.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md
index 66e270e6c9..e54c7d255c 100644
--- a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md
+++ b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md
@@ -1 +1 @@
-If you're starting a monthly sponsorship on behalf of your user account, you'll immediately be charged a prorated amount for the time until your next regular billing date. 如果您代表组织进行赞助，可以选择按比例支付金额或按月全额付款。
+如果您代表您的用户帐户开始月度赞助，将立即向您收取按时间比例分摊的金额，直到您的下一个常规计费日期。 如果您代表组织进行赞助，可以选择按比例支付金额或按月全额付款。
diff --git a/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md b/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md
index a84fd2930a..7d8831cd9c 100644
--- a/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md
+++ b/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md
@@ -1 +1 @@
-1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png)
+1. 校对您的等级，然后单击 **Publish _TYPE_ tier（发布 TYPE 等级）**。 ![发布月度等级按钮](/assets/images/help/sponsors/publish-tier-button.png)
diff --git a/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md b/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md
index 2c1f976a93..77deba8010 100644
--- a/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md
+++ b/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md
@@ -1 +1 @@
-1. 在页面右侧的“Select a tier（选择等级）”下，审查可用的赞助等级。 If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png)
+1. 在页面右侧的“Select a tier（选择等级）”下，审查可用的赞助等级。 如果有多个类型的等级，且当前显示“Monthly（月度）”等级，请单击 **One-time（一次性）**以显示一次性付款的等级。 ![显示"一次性"等级](/assets/images/help/sponsors/show-one-time-tiers.png)
diff --git a/translations/zh-CN/data/reusables/sponsors/select-a-tier.md b/translations/zh-CN/data/reusables/sponsors/select-a-tier.md
index 64dd7ffa1c..81e056b8ca 100644
--- a/translations/zh-CN/data/reusables/sponsors/select-a-tier.md
+++ b/translations/zh-CN/data/reusables/sponsors/select-a-tier.md
@@ -1 +1 @@
-1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![选择等级框](/assets/images/help/sponsors/select-a-tier-box.png)
+1. 在您需要的等级右侧，单击 **Select（选择）**。 如果要选择自定义金额，请在单击“Select（选择）”之前输入赞助金额。 ![选择等级框](/assets/images/help/sponsors/select-a-tier-box.png)
diff --git a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md
index 9b3e361810..cb0ffdaa86 100644
--- a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md
+++ b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md
@@ -1 +1 @@
-您可以代表您的用户帐户或组织赞助具有被赞助的开发者配置文件或赞助组织配置文件的任何人。 You can choose from multiple sponsorship tiers, with one-time or monthly payment amounts and benefits that are set by the sponsored account. 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。
+您可以代表您的用户帐户或组织赞助具有被赞助的开发者配置文件或赞助组织配置文件的任何人。 有多个赞助等级可供选择，一次性或月度支付金额和福利由被赞助帐户设定。 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。
diff --git a/translations/zh-CN/data/reusables/sponsors/tier-details.md b/translations/zh-CN/data/reusables/sponsors/tier-details.md
index c5cbaf2eba..df575dcf2f 100644
--- a/translations/zh-CN/data/reusables/sponsors/tier-details.md
+++ b/translations/zh-CN/data/reusables/sponsors/tier-details.md
@@ -1,3 +1,3 @@
-您最多可以创建十个赞助等级供赞助者选择。 Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time).
+您最多可以创建十个赞助等级供赞助者选择。 每个等级都有自己的月度或一次性付款额（美元）和福利，如提早访问新版本或出现在项目的自述文件中。 此外，您可以选择为自定义金额启用等级（月度和一次性）。
 
-一旦您发布某个等级，便不能编辑这个等级的价格。 而只能撤销该等级并新建一个等级。 Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires.
+一旦您发布某个等级，便不能编辑这个等级的价格。 而只能撤销该等级并新建一个等级。 现有赞助者将保留在已撤销的等级中，直到他们更改其赞助等级、取消其赞助或其一次性赞助期满。
diff --git a/translations/zh-CN/data/reusables/supported-languages/C.md b/translations/zh-CN/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..116f934d56
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/C.md
@@ -0,0 +1 @@
+| C |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/Cpp.md b/translations/zh-CN/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..89f786756b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1 @@
+| C++ |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/Cs.md b/translations/zh-CN/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..c6dc8162ff
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/Cs.md
@@ -0,0 +1 @@
+| C# |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/go.md b/translations/zh-CN/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..65bd3364a1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/go.md
@@ -0,0 +1 @@
+| Go |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<br> Go 模块 | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/java.md b/translations/zh-CN/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..adeecae15f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/java.md
@@ -0,0 +1 @@
+| Java |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/javascript.md b/translations/zh-CN/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..f62027ecb8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/javascript.md
@@ -0,0 +1 @@
+| JavaScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/php.md b/translations/zh-CN/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..cbe731322d
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/php.md
@@ -0,0 +1 @@
+| PHP |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/products-table-header.md b/translations/zh-CN/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..f59565ec01
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,2 @@
+{% if currentVersion == "free-pro-team@latest" %}| [代码导航](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依赖项图、{% data variables.product.prodname_dependabot_alerts %}、{% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依赖项图、{% data variables.product.prodname_dependabot_alerts %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: |{% elsif currentVersion == "github-ae@latest" %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/python.md b/translations/zh-CN/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..eb470c453a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/python.md
@@ -0,0 +1 @@
+| Python |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/ruby.md b/translations/zh-CN/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..971f7cace1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/ruby.md
@@ -0,0 +1 @@
+| Ruby |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/scala.md b/translations/zh-CN/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..2f62ed9f33
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/scala.md
@@ -0,0 +1 @@
+| Scala |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %}| |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/supported-languages/typescript.md b/translations/zh-CN/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..66d95da108
--- /dev/null
+++ b/translations/zh-CN/data/reusables/supported-languages/typescript.md
@@ -0,0 +1 @@
+| TypeScript |{% if currentVersion == "free-pro-team@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion ver_gt "enterprise-server@2.21" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif currentVersion == "github-ae@latest" %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}| | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %} 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/user_settings/billing_plans.md b/translations/zh-CN/data/reusables/user_settings/billing_plans.md
index 8d26ab1479..704e61bc4d 100644
--- a/translations/zh-CN/data/reusables/user_settings/billing_plans.md
+++ b/translations/zh-CN/data/reusables/user_settings/billing_plans.md
@@ -1 +1 @@
-1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png)
+1. 在用户设置侧边栏中，单击 **Billing & plans（帐单与计划）**。 ![帐单与计划设置](/assets/images/help/settings/settings-sidebar-billing-plans.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/zh-CN/data/reusables/user_settings/keeping_your_email_address_private.md
index 8c8d6c7c2c..efab7389d8 100644
--- a/translations/zh-CN/data/reusables/user_settings/keeping_your_email_address_private.md
+++ b/translations/zh-CN/data/reusables/user_settings/keeping_your_email_address_private.md
@@ -1 +1 @@
-5. 要在执行基于 web 的 Git 操作时对您的电子邮件地址保密，请单击 **Keep my email address private（对我的电子邮件地址保密）**。 ![对电子邮件地址保密的复选框图像](/assets/images/help/settings/email_privacy.png)
+5. 要在执行基于 web 的 Git 操作时对您的电子邮件地址保密，请单击 **Keep my email addresses private（对我的电子邮件地址保密）**。 ![对电子邮件地址保密的复选框图像](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/zh-CN/data/reusables/user_settings/payment-info-link.md b/translations/zh-CN/data/reusables/user_settings/payment-info-link.md
new file mode 100644
index 0000000000..133dc101bb
--- /dev/null
+++ b/translations/zh-CN/data/reusables/user_settings/payment-info-link.md
@@ -0,0 +1 @@
+1. 在页面顶部，单击 **Payment information（付款信息）**。 ![付款信息链接](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/zh-CN/data/reusables/webhooks/create_properties.md b/translations/zh-CN/data/reusables/webhooks/create_properties.md
index da37606191..1079d5e46a 100644
--- a/translations/zh-CN/data/reusables/webhooks/create_properties.md
+++ b/translations/zh-CN/data/reusables/webhooks/create_properties.md
@@ -1,6 +1,6 @@
-| 键               | 类型    | 描述                                                                                                                                                                                             |
-| --------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ref`           | `字符串` | The [`git ref`](/rest/reference/git#get-a-reference) 资源。                                                                                                                                       |
-| `ref_type`      | `字符串` | 在仓库中创建的 Git ref 对象的类型。 可以是 `branch` 或 `tag`。                                                                                                                                                   |
-| `master_branch` | `字符串` | 仓库默认分支的名称（通常是 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.23" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}）。 |
-| `说明`            | `字符串` | 仓库的当前描述。                                                                                                                                                                                       |
+| 键               | 类型    | 描述                                                                                                                                                                                            |
+| --------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ref`           | `字符串` | The [`git ref`](/rest/reference/git#get-a-reference) 资源。                                                                                                                                      |
+| `ref_type`      | `字符串` | 在仓库中创建的 Git ref 对象的类型。 可以是 `branch` 或 `tag`。                                                                                                                                                  |
+| `master_branch` | `字符串` | 仓库默认分支的名称（通常是 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}）。 |
+| `说明`            | `字符串` | 仓库的当前描述。                                                                                                                                                                                      |
diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md
index 7058d497ad..1e73e8edd8 100644
--- a/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md
+++ b/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -1,3 +1,3 @@
-| 键        | 类型    | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action` | `字符串` | 执行的操作内容. 可以是以下之一：`opened`、`edited`、`closed`、`assigned`、`unassigned`、`review_requested`、`review_request_removed`、`ready_for_review`、`converted_to_draft`、`labeled`、`unlabeled`、`synchronize`、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}`auto_merge_enabled`、`auto_merge_disabled`、{% endif %} `locked`、`unlocked` 或 `reopened`。 如果操作为 `closed`，并且 `merged` 键为 `false`，则拉取请求随未合并的提交而关闭。 如果操作为 `closed`，并且 `merged` 键为 `true`，则拉取请求被合并。 |
+| 键        | 类型    | 描述                                           |
+| -------- | ----- | -------------------------------------------- |
+| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：<ul><li>`assigned`</li>{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}<li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li>{% endif %}<li>`closed`：如果操作为 `closed`，并且 `merged` 键为 `false`，则拉取请求随未合并的提交而关闭。 如果操作为 `closed`，并且 `merged` 键为 `true`，则拉取请求被合并。</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`：当拉取请求的跟踪分支与拉动请求的源分支同步时触发，在更新源分支时会发生这种情况。</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul> |
diff --git a/translations/zh-CN/data/reusables/webhooks/sponsorship_short_desc.md b/translations/zh-CN/data/reusables/webhooks/sponsorship_short_desc.md
index bae71f4f5f..a7834f5324 100644
--- a/translations/zh-CN/data/reusables/webhooks/sponsorship_short_desc.md
+++ b/translations/zh-CN/data/reusables/webhooks/sponsorship_short_desc.md
@@ -1 +1 @@
-与赞助列表相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[关于 GitHub 赞助者](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)”。
+与赞助列表相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[关于 GitHub 赞助者](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”。
diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml
index 16297966f4..6b2f44468f 100644
--- a/translations/zh-CN/data/ui.yml
+++ b/translations/zh-CN/data/ui.yml
@@ -20,7 +20,7 @@ homepage:
   version_picker: 版本
 toc:
   getting_started: 入门指南
-  popular_articles: 热门
+  popular: 热门
   guides: 指南
   whats_new: 新增内容
 pages:
@@ -54,14 +54,6 @@ contribution_cta:
   button: 做出贡献
   or: 或,
   to_guidelines: 了解如何参与。
-enterprise_releases_list:
-  title: Enterprise Server 发行版
-  currently_supported: 当前支持
-  currently_supported_message: 请参阅 <a href="https://github.com/enterprise">GitHub Enterprise</a> 以获取最新版本的信息。
-  deprecated: 已废弃
-  deprecated_message: '这些文档仍然可用，但不再维护：'
-  deprecated_developer: 在 developer.github.com 上已废弃
-  deprecated_developer_message: '这些文档在旧<a href="https://developer.github.com">开发者站点</a>上仍然可用，但不再维护：'
 products:
   graphql:
     reference:
@@ -127,19 +119,36 @@ footer:
       press: 新闻
       shop: 商店
 product_landing:
-  quick_start: 快速入门
-  reference_guides: 参考指南
+  quickstart: 快速入门
+  reference: 参考
   overview: 概览
+  guides: 指南
+  code_examples: 代码示例
+  search_code_examples: 搜索代码示例
+  show_more: 显示更多
+  explore_people_and_projects: 探索人员和项目
+  sorry: 抱歉，找不到结果
+  no_example: 看起来我们没有适合您的过滤器的示例。
+  try_another: 请尝试另一个过滤器或添加您的代码示例。
+  no_result: 抱歉，没有与过滤条件匹配的指南。
+  learn: 了解如何添加代码示例
+  communities_using_discussions: 使用讨论的社区
+  add_your_community: 添加您的社区
+  sponsor_community: GitHub Sponsors 社区
+  supported_releases: 支持的版本
+  release_notes_for: 发行说明
+  upgrade_from: 升级自
+  browse_all_docs: 浏览所有文档
+  explore_release_notes: 浏览发行说明
 product_sublanding:
   start: 开始
   start_path: 开始路径
-  learning_paths: '{{ allProducts[currentProduct].name }} 学习路径'
+  learning_paths: '{{ productMap[currentProduct].name }} 学习路径'
   learning_paths_desc: 学习路径是一系列帮助您掌握特定主题的指南。
-  guides: '{{ allProducts[currentProduct].name }} 指南'
+  guides: '{{ productMap[currentProduct].name }} 指南'
   more_guides: 更多指南
   load_more: 加载更多指南
-  all_guides: '所有 {{ allProducts[currentProduct].name }} 指南'
-  no_result: 抱歉，没有与过滤条件匹配的指南。
+  all_guides: '所有 {{ productMap[currentProduct].name }} 指南'
   filters:
     type: 类型
     topic: 主题
@@ -154,3 +163,10 @@ learning_track_nav:
   prevGuide: 上一个指南
   nextGuide: 下一个指南
 contributor_callout: 这篇文章的参与者和维护者是
+toggle_images:
+  off: 图像已关闭，点击显示
+  on: 图像已打开，点击隐藏
+  hide_single: 隐藏图像
+  show_single: 显示图像
+scroll_button:
+  scroll_to_top: 滚动到顶部
diff --git a/translations/zh-CN/data/variables/codespaces_code_examples.yml b/translations/zh-CN/data/variables/codespaces_code_examples.yml
new file mode 100644
index 0000000000..00958245ab
--- /dev/null
+++ b/translations/zh-CN/data/variables/codespaces_code_examples.yml
@@ -0,0 +1,43 @@
+---
+- 
+  title: Node.js sample project
+  description: Try a Node.js project with a custom dev container
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - development containers
+- 
+  title: Python sample project
+  description: Try a Python project with a custom dev container
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - development containers
+- 
+  title: Java sample project
+  description: Try a Java project with a custom dev container
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - development containers
+- 
+  title: Go sample project
+  description: Try a Go project with a custom dev container
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - development containers
+- 
+  title: Rust sample project
+  description: Try a Rust project with a custom dev container
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - development containers
+- 
+  title: PHP sample project
+  description: Try a PHP project with a custom dev container
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - development containers
diff --git a/translations/zh-CN/data/variables/migrations.yml b/translations/zh-CN/data/variables/migrations.yml
index f8ec258fd1..e5d457614d 100644
--- a/translations/zh-CN/data/variables/migrations.yml
+++ b/translations/zh-CN/data/variables/migrations.yml
@@ -4,4 +4,4 @@ user_migrations_intro: >-
 organization_migrations_intro: >-
   组织迁移 API 可让您将仓库从 GitHub 移动到 {% data variables.product.prodname_ghe_server %}。
 source_imports_intro: >-
-  源导入 API 可让您从 Git、Subversion、Mercurial 或 Team Foundation Server 源仓库开始导入。这是与 {% data variables.product.prodname_dotcom %} Importer 相同的功能。更多信息请参阅“[使用 {% data variables.product.prodname_dotcom %} Importer 导入仓库](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)”。
+  源导入 API 可让您从 Git、Subversion、Mercurial 或 Team Foundation Version Control 源仓库开始导入。这是与 {% data variables.product.prodname_dotcom %} Importer 相同的功能。更多信息请参阅“[使用 {% data variables.product.prodname_dotcom %} Importer 导入仓库](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)”。
diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml
index 36cce5086d..591b231719 100644
--- a/translations/zh-CN/data/variables/product.yml
+++ b/translations/zh-CN/data/variables/product.yml
@@ -56,6 +56,7 @@ prodname_pages: 'GitHub Pages'
 #CodeQL
 prodname_codeql: 'CodeQL'
 prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
 #Apps, GitHub Marketplace, and integrations
 prodname_marketplace: 'GitHub Marketplace'
 prodname_github_app: 'GitHub 应用程序'
@@ -77,8 +78,7 @@ prodname_debug: 'GitHub Debug'
 prodname_discussions: 'GitHub Discussions'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
-prodname_github_container_registry: 'GitHub Container Registry'
-prodname_container_registry: 'container registry'
+prodname_container_registry: 'Container registry'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
@@ -91,7 +91,6 @@ prodname_advanced_security: 'Advanced Security'
 prodname_security_center: '安全中心'
 #Codespaces
 prodname_codespaces: 'Codespaces'
-prodname_vs_codespaces: 'Visual Studio 代码空间'
 prodname_github_codespaces: 'GitHub Codespaces'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'GitHub Community Support'
diff --git a/translations/zh-CN/data/variables/release_candidate.yml b/translations/zh-CN/data/variables/release_candidate.yml
index ec65ef6f94..c231c1ce14 100644
--- a/translations/zh-CN/data/variables/release_candidate.yml
+++ b/translations/zh-CN/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.1
diff --git a/translations/zh-CN/data/variables/sponsors_user_examples.yml b/translations/zh-CN/data/variables/sponsors_user_examples.yml
new file mode 100644
index 0000000000..b63daef474
--- /dev/null
+++ b/translations/zh-CN/data/variables/sponsors_user_examples.yml
@@ -0,0 +1,20 @@
+---
+- 
+  #Images and descriptions are pulled directly from the repo
+  user: chaynHQ
+  description: Chayn 帮助遭受虐待的妇女找到掌握自己生活所需的正确信息和支持。
+- 
+  user: foosel
+  description: '👋 我叫 Gina，是 OctoPrint 🐙 的创作者和主要开发者。'
+- 
+  user: dayhaysoos
+  description: What's up? I'm Nick. I'm an engineer who has a new-found passion for removing friction from the e-commerce developer experience.
+- 
+  user: yyx990803
+  description: I'm working fulltime on Vue.js, a frontend JavaScript framework for building web applications, and Vite, a modern web build tool.
+- 
+  user: calebporzio
+  description: '🚶‍♂️I left my day job in Jan 2019 to pursue open-source. Since then, I''ve built Laravel Livewire, AlpineJS, and a bunch of other stuff.'
+- 
+  user: kjaymiller
+  description: Hi Y'all I'm Jay! 👋 I'm a Marine Corps Veteran turned developer that's been actively coding since 2014. I'm also involved in the productivity space where I can be found helping people with automations for some of their favorite apps and tools.